Method, system and related devices for network resource management

Abstract

The application discloses a method for network resource management, comprising: a resource information server receiving a query request sent by a resource scheduling server, the query request carrying a performance requirement for a first network resource, so as to determine a first network resource (referred to as a matched first network resource) meeting the performance requirement according to an available capacity of an existing first network resource, and returning an identifier of the matched first network resource. Wherein, the first network resource is any one of CSI, NSI, NSSI or NF. Then, the resource information server also receives an update request carrying an identifier of an allocated first network resource, and updates the available capacity of the allocated first network resource. The allocated first network resource is in the matched first network resource. The method makes the allocation of the first network resource based on the available capacity of the existing first network resource, and updates the available capacity of the allocated first network resource in time after the allocation, thereby improving the feasibility and efficiency of the network resource management.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, system and related apparatus for network resource management. Background Technology

[0002] With the rapid development of mobile communications, the differentiation of communication service demands is becoming increasingly significant. In 5G (5th Generation) networks, from a performance perspective, communication services can be categorized into several types, such as Enhanced Mobile Broadband (EMBB), Ultra High-Reliability and Low-Latency Communication (URLLC), and Massive Internet of Things (MIoT). EMBB aims to support high data rates and high traffic density, and can be applied to applications such as ultra-high-definition video and virtual reality (VR). URLLC aims to support low latency and high reliability, and can be applied to applications such as autonomous driving and industrial control. MIoT aims to support the communication requirements of a large number of high-density servers, and can be applied to applications such as wearable servers and smart grids.

[0003] To meet the needs of different types of communication services, the physical network can be divided at the end-to-end level to form network slices, enabling traffic packetization, tenant isolation, and macro-level resource allocation. Essentially, a network slice is a logical network running on top of a shared physical network infrastructure. A network slice can be further divided into one or more network slice subnets (NSS), such as core network slices, radio access network slices, etc.

[0004] When a user sends a service request, a Communication Service Instance (CSI) is allocated based on the service requirements to provide the communication service that meets those requirements. CSI is implemented by deploying Network Slice Instances (NSIs), where an NSI is a running instance of a network slice. NSI is implemented by deploying Network Slice Subnet Instances (NSSIs), where an NSSI is a running instance of a network slice subnet. NSSI is implemented by deploying Network Functions (NFs), where an NF is a defined processing function within the network, possessing functional behavior and interfaces.

[0005] Currently, the network resource model only includes demand-related information, such as third-generation partners (3). rd The Network Resource Model (NRM) in the 3GPP (3G Generation Partnership Project) technical standard TS23.541 only defines the requirements model, such as Service Profiles and Slice Profiles. The Service Profile describes the network slice-related requirements that the Network Resource Injection (NSI) should support, while the Slice Profile describes the network slice subnet-related requirements that the Network Resource Injection System (NSSI) should support. Correspondingly, network resource management primarily involves network resource allocation, and this allocation is based on the resource requirements carried in the allocation request. For example, NSI allocation is based on the Service Profile carried in the NSI allocation request, and NSSI allocation is based on the Slice Profile carried in the NSSI allocation request, and so on. Summary of the Invention

[0006] This application provides a method, system, and related apparatus for network resource management, which can improve the feasibility and efficiency of network resource management.

[0007] Firstly, this application provides a method for network resource management, which is executed by a resource information server, wherein the resource information server is centrally deployed or distributed.

[0008] The resource information server receives a query request from the resource scheduling server. This query request carries performance requirements for a first network resource, and is used to query available network resources whose capabilities meet these requirements. The first network resource can be any one of CSI, NSI, NSSI, or NF. In response to the query request, the resource information server determines a matching first network resource based on the available capabilities of existing first network resources in its storage database. This matching first network resource is one whose available capabilities meet the performance requirements, and returns an identifier of the matching first network resource to the resource scheduling server. In this application, the available capabilities of network resources are introduced during network resource management. When allocating first network resources, based on the available capabilities of existing first network resources, the first network resource whose available capabilities match the performance requirements can be quickly and effectively determined.

[0009] Furthermore, the resource information server also receives an update request carrying an identifier for the allocated first network resource. This allocated first network resource is one or more network resources among the matched first network resources; that is, the allocated first network resource is the one ultimately allocated to meet the aforementioned performance requirements. Subsequently, the resource information server updates the availability of the allocated first network resource. By promptly updating the availability of the allocated first network resource after its allocation, the effectiveness of the stored availability of existing first network resources is improved. This also facilitates efficient and accurate subsequent allocation of first network resources based on availability, enhancing the feasibility and efficiency of network resource management.

[0010] In one implementation, the resource information server obtains the remaining available capacity of the allocated first network resource after the allocation from the management data analysis server, and updates the available capacity of the allocated first network resource to the remaining available capacity. Optionally, the update request may also carry the remaining available capacity of the allocated first network resource.

[0011] In this embodiment, the data analysis server has strong data analysis capabilities. By using the data analysis server, the remaining available capacity of the allocated first network resource can be obtained. This will not occupy the computing resources of the resource information server, and it will also help to quickly and accurately calculate the remaining available capacity.

[0012] In one implementation, the resource information server sends a resource change notification to the management data analysis server. This notification carries an identifier for the allocated first network resource, indicating a change in the resource information of that resource. The resource information server receives information from the management data analysis server regarding the remaining available capacity of the allocated first network resource after this allocation. This resource change notification triggers the management data analysis server to re-determine the available capacity of the allocated first network resource to obtain the remaining available capacity.

[0013] In one implementation, the resource information server sends an availability capability update request to the management data analysis server. This request carries an identifier of the allocated first network resource, requesting the management data analysis server to re-determine the availability capability of the allocated first network resource. The resource information server receives information from the management data analysis server regarding the remaining availability capability of the allocated first network resource after this allocation. The resource information server proactively requests this remaining availability capability from the management data analysis server.

[0014] Optionally, the resource information server also obtains the load information of the first allocated network resource after this allocation from the network data analysis server in a timely manner, and provides the load information of the first allocated network resource after this allocation to the management data analysis server to determine the remaining available capacity.

[0015] In this application, the load information of the first network resource allocated will also change after the allocation. By first obtaining the load information of the first network resource allocated after the allocation, the remaining available capacity can be determined based on the load information after the allocation, making the determined remaining available capacity more accurate and effective.

[0016] In one implementation, the remaining available capacity is determined based on the resource information of the allocated first network resource. This resource information includes one or more of the following: planning information for the allocated first network resource, load information for the allocated first network resource after this allocation, demand information for the allocated first network resource, the available capacity of the allocated first network resource determined before this allocation, alarm information for the allocated first network resource, and the correspondence between the allocated first network resource and other network resources. Therefore, the remaining available capacity is determined based on multiple pieces of information, making the determined remaining available capacity more accurate and effective.

[0017] Optionally, the resource information server can also store and provide the resource information of the first network resource allocated to the management data analysis server to determine the remaining available capacity, thereby avoiding the management data analysis server from collecting resource information from different devices to determine the remaining available capacity and improving the efficiency of determining the remaining available capacity.

[0018] Optionally, the availability of existing first network resources stored on the resource information server is periodically updated by the management data analysis server. Since the availability of existing first network resources can change due to various reasons, such as sudden alarms, failures, or the expansion or contraction of the first network resources themselves, periodically updating the availability of existing first network resources is beneficial to improving the effectiveness of the availability of existing first network resources.

[0019] Optionally, when allocating a first network resource for a second network resource to be deployed, the performance requirement for the first network resource is the performance requirement of the second network resource to be deployed relative to the first network resource. The update request received by the resource information server also carries the identifier of the second network resource to be deployed. In response to the update request, the resource information server also establishes a correspondence between the second network resource to be deployed and the allocated first network resource (e.g., establishing a topology edge), and this correspondence indicates that the second network resource to be deployed is deployed on the allocated first network resource.

[0020] In one implementation, when a first network resource is reallocated to a second network resource to be deployed, the second network resource was previously deployed on the initial first network resource, and the allocated first network resource is the one reallocated to the second network resource to be deployed. The resource information server updates the correspondence between the second network resource to be deployed and the initial first network resource to the correspondence between the second network resource to be deployed and the allocated first network resource; and may further update the available capacity of the initial first network resource.

[0021] In one implementation, the resource scheduling server is deployed on the first management device, and the update request is also received from the first management device. In this case, the first management device interacts directly with the resource information server to query for matching first network resources.

[0022] In one implementation, the first network resource is a communication service instance, and the first management device is a communication service management server. The resource information server receiving the update request specifically involves the resource information server receiving the update request sent by the communication service management server. Furthermore, the second network resource is specifically a tenant instance.

[0023] In one implementation, the first network resource is a network slice instance, and the first management device is a network slice management server. The resource information server receiving the update request specifically involves the resource information server receiving the update request sent by the network slice management server. Furthermore, the second network resource is specifically a communication service instance.

[0024] In one implementation, the first network resource is a network slice subnet instance, and the first management device is a network slice subnet management server. The resource information server receiving the update request specifically involves the resource information server receiving the update request sent by the network slice subnet management server. Furthermore, the second network resource is specifically a network slice instance.

[0025] In one implementation, the first network resource is a network function, and the first management device is a network function management server. The resource information server receiving the update request specifically means that the resource information server receives the update request sent by the network function management server. Furthermore, the second network resource is specifically a network slice subnet instance.

[0026] Secondly, this application provides a method for network resource management, which is executed jointly by multiple devices.

[0027] The first management server sends a performance requirement for a first network resource to the resource information query server. This first network resource can be any one of CSI, NSI, NSSI, or NF. Upon receiving the performance requirement, the resource information query server determines a matching first network resource based on the available capabilities of existing first network resources stored in the resource information database and returns an identifier of the allocated first network resource to the first management server. The matching first network resource refers to a first network resource whose available capabilities meet the performance requirement, and the allocated first network resource is one or more of the matching first network resources. Therefore, the first management server determines to use the allocated first network resource; that is, the allocated first network resource is the first network resource ultimately allocated to meet the aforementioned performance requirement. In this application, the available capabilities of network resources are introduced during the network resource management process. When allocating the first network resource, based on the available capabilities of existing first network resources, the first network resource whose available capabilities match the performance requirement can be quickly and effectively determined.

[0028] Furthermore, the first management server sends an update request to the resource information management server, which carries the identifier of the allocated first network resource; the resource information management server updates the availability of the allocated first network resource stored in the resource information database. By promptly updating the availability of the allocated first network resource after its allocation, the effectiveness of the stored availability of the existing first network resource is improved. This also facilitates efficient and accurate allocation of the first network resource based on its availability in the future, thereby enhancing the feasibility and efficiency of network resource management.

[0029] In one implementation, the resource information management server obtains the remaining available capacity of the allocated first network resource after this allocation from the management data analysis server, and updates the available capacity of the allocated first network resource stored in the resource information database to the remaining available capacity.

[0030] In this embodiment, the data analysis server has strong data analysis capabilities. By using the data analysis server, the remaining available capacity of the allocated first network resource can be obtained. This will not occupy the computing resources of the resource information server, and it will also help to quickly and accurately calculate the remaining available capacity.

[0031] In one implementation, the resource information management server sends a resource change notification to the management data analysis server. This notification carries an identifier for the allocated first network resource, indicating a change in the resource information of that resource. The resource information management server receives information from the management data analysis server regarding the remaining available capacity of the allocated first network resource after this allocation. This resource change notification triggers the management data analysis server to re-determine the available capacity of the allocated first network resource, i.e., the remaining available capacity.

[0032] In one implementation, the resource information management server sends an availability update request to the management data analysis server. This availability update request carries an identifier of the allocated first network resource to request the remaining availability of that allocated first network resource after the current allocation. The resource information management server receives the remaining availability of the allocated first network resource from the management data analysis server after the current allocation. The resource information management server proactively requests this remaining availability from the management data analysis server.

[0033] Optionally, the resource information management server also promptly obtains the load information of the allocated first network resource after this allocation from the network data analysis server, and updates the load information of the allocated first network resource stored in the resource information database to the load information of the allocated first network resource after this allocation; then, the resource information management server or the resource information query server sends the load information of the allocated first network resource after this allocation to the management data analysis server. The remaining available capacity is determined based on the load information of the allocated first network resource after this allocation. In this application, the load information of the allocated first network resource will also change after this allocation. By first obtaining the load information of the allocated first network resource after this allocation, the remaining available capacity can be determined based on the load information after this allocation, making the determined remaining available capacity more accurate and effective.

[0034] In one implementation, the management data analysis server determines the remaining available capacity based on the resource information of the allocated first network resource. The resource information of the allocated first network resource includes one or more of the following: planning information of the allocated first network resource, load information of the allocated first network resource after this allocation, demand information for the allocated first network resource, the available capacity of the allocated first network resource determined before this allocation, alarm information of the allocated first network resource, and the correspondence between the allocated first network resource and other network resources. Therefore, the remaining available capacity is determined based on multiple pieces of information, making the determined remaining available capacity more accurate and effective.

[0035] Optionally, the resource information of the allocated first network resource is stored in a resource information database. The resource information management server or resource information query server also sends the resource information of the allocated first network resource to the management data analysis server, thereby avoiding the management data analysis server from collecting resource information from different devices to determine the remaining available capacity, thus improving the efficiency of determining the remaining available capacity.

[0036] Optionally, the management data analysis server periodically updates the availability of existing first network resources to the resource information management server. Thus, the availability of existing first network resources stored in the resource information database can be updated periodically. Since the availability of existing first network resources can change due to various reasons, such as sudden alarms, failures, or the expansion and contraction of the first network resources themselves, periodically updating the availability of existing first network resources helps improve the effectiveness of their availability.

[0037] In one implementation, the first management server sends performance requirements for the first network resource to the resource information query server via a resource scheduling server. For example, the first management server sends a resource scheduling request to the resource scheduling server, carrying the performance requirements for the first network resource; subsequently, the resource scheduling server sends a query request to the resource information query server, carrying the performance requirements. The resource information query server determines the first network resource whose available capacity matches the performance requirements based on the available capacity of existing first network resources stored in the resource information database, and returns a query response to the resource scheduling server, carrying the identifier of the matching first network resource and its available capacity; then, the resource scheduling server determines the allocated first network resource based on a scheduling algorithm and the available capacity of the matching first network resource, and returns the identifier of the allocated first network resource to the first management server.

[0038] In one implementation, the resource scheduling server is deployed on a first management device, meaning the first management device provides resource scheduling functionality. Specifically, the resource information query server returns the identifier of a matching first network resource and the available capacity of the matching first network resource to the first management device; then, the first management device determines the allocated first network resource from the matching first network resources based on the scheduling algorithm and the available capacity of the matching first network resource, thereby determining which allocated first network resource to use.

[0039] In both of the above implementations, the first network resource allocated is selected based on a scheduling algorithm, which can ensure that the allocated first network resource is the optimal first network resource, which is beneficial to optimizing the overall network resource scheduling, such as improving network resource utilization.

[0040] Optionally, when allocating a first network resource for a second network resource to be deployed, the performance requirement for the first network resource is the performance requirement of the second network resource to be deployed relative to the first network resource. The update request received by the resource information management server also carries the identifier of the second network resource to be deployed. In response to the update request, the resource information management server further establishes a correspondence between the second network resource to be deployed and the allocated first network resource (e.g., establishing a topology edge), and this correspondence indicates that the second network resource to be deployed is deployed on the allocated first network resource.

[0041] In one implementation, when the first management device reallocates the first network resource to be deployed as a second network resource, the second network resource to be deployed was previously deployed on the initial first network resource, and the allocated first network resource is reallocated to the second network resource to be deployed. The resource information management server updates the correspondence between the second network resource to be deployed and the initial first network resource to the correspondence between the second network resource to be deployed and the allocated first network resource; and further updates the available capabilities for managing the initial first network resource.

[0042] Optionally, the second management server sends an allocation request to the first management server, the allocation request carrying the performance requirements of the second network resource to be deployed for the first network resource, in order to request the allocation of the first network resource from the first management server; after the first management server determines to use the allocated first network resource, the first management server also sends an allocation response to the second management server, the allocation response carrying the identifier of the allocated first network resource, in order to notify the second management server that the allocation was successful and which specific first network resource was allocated.

[0043] In one implementation, the first network resource is a communication service instance, and the first management device is a communication service management server. The resource information server receiving the update request specifically involves the resource information server receiving the update request sent by the communication service management server. Furthermore, the second network resource is specifically a tenant instance.

[0044] In one implementation, the first network resource is a network slice instance, and the first management device is a network slice management server. The resource information server receiving the update request specifically involves the resource information server receiving the update request sent by the network slice management server. Furthermore, the second network resource is specifically a communication service instance.

[0045] In one implementation, the first network resource is a network slice subnet instance, and the first management device is a network slice subnet management server. The resource information server receiving the update request specifically involves the resource information server receiving the update request sent by the network slice subnet management server. Furthermore, the second network resource is specifically a network slice instance.

[0046] In one implementation, the first network resource is a network function, and the first management device is a network function management server. The resource information server receiving the update request specifically means that the resource information server receives the update request sent by the network function management server. Furthermore, the second network resource is specifically a network slice subnet instance.

[0047] The first and second aspects above explain the different implementations of the network resource management method of this application. These implementations can be achieved using devices of different types.

[0048] Thirdly, this application provides a resource information server. This resource information server includes functional modules that execute the network resource management method provided in the first aspect or any possible design of the first aspect. This application does not limit the division of functional modules; the functional modules can be divided according to the process steps of the network resource management method in the first aspect, or according to specific implementation needs. The functional modules can be implemented in hardware, or they can be implemented by hardware executing corresponding software.

[0049] Fourthly, this application provides a resource information server. The resource information server includes a memory and a processor. The memory stores program code and resource information (such as available capabilities) of network resources. The processor invokes the program code and, in conjunction with the resource information, implements the network resource management method of the first aspect of this application and any possible design thereof.

[0050] Fifthly, this application provides a system for network resource management. The system includes: a first management server and a resource information server. The first management server is used to execute the method performed by the first management server in the second aspect of this application and any possible design thereof; the resource information server is used to execute the methods performed by the resource information query server, resource information database, and resource information management server in the second aspect of this application and any possible design thereof.

[0051] Optionally, the system further includes: a management data analysis server for executing the method performed by the management data analysis server in the second aspect of this application and any possible design thereof.

[0052] Optionally, the system further includes: a network data analysis server for executing the method performed by the network data analysis server in the second aspect of this application and any possible design thereof.

[0053] Optionally, the system further includes a resource scheduling server for executing the method performed by the resource scheduling server in the second aspect of this application and any possible design thereof.

[0054] Optionally, the system further includes: a second management server for executing the method performed by the second management server in the second aspect of this application and any possible design thereof.

[0055] Sixthly, this application provides a system for network resource management. The system includes: a first management server, a resource information query server, a resource information database, and a resource information management server. The first management server is used to execute the method executed by the first management server in the second aspect of this application and any possible design thereof; the resource information query server is used to execute the method executed by the resource information query server in the second aspect of this application and any possible design thereof; the resource information database is used to execute the method executed by the resource information database in the second aspect of this application and any possible design thereof; and the resource information management server is used to execute the method executed by the resource information management server in the second aspect of this application and any possible design thereof.

[0056] Optionally, the system further includes: a management data analysis server for executing the method performed by the management data analysis server in the second aspect of this application and any possible design thereof.

[0057] Optionally, the system further includes: a network data analysis server for executing the method performed by the network data analysis server in the second aspect of this application and any possible design thereof.

[0058] Optionally, the system further includes a resource scheduling server for executing the method performed by the resource scheduling server in the second aspect of this application and any possible design thereof.

[0059] Seventhly, this application provides a method for network resource management, characterized in that the method includes:

[0060] Receive a resource change notification, which carries an identifier of a first network resource whose resource information has changed. The first network resource is a network resource among a communication service instance, a network slice instance, a network slice subnet instance, or a network function.

[0061] The remaining available capacity of the first network resource is determined based on its resource information.

[0062] Send the remaining available capacity of the first network resource to the resource information management server to update the available capacity of the first network resource.

[0063] In one implementation, the resource information of the first network resource includes one or more of the following: planning information of the first network resource, load information of the first network resource, demand information for the first network resource, available capacity of the first network resource determined before the resource information change, alarm information of the first network resource, and the correspondence between the first network resource and other network resources. Therefore, the remaining available capacity is determined based on multiple pieces of information, making the determined remaining available capacity more accurate and effective.

[0064] In one implementation, the resource change notification is sent by either a first management server or a resource information management server. The device performing the method is a management data analysis server.

[0065] Optionally, the method further includes obtaining resource information of the first network resource from a resource information management server or a resource information query server.

[0066] Optionally, the method further includes: receiving a performance requirement for a first network resource sent by a first management server; obtaining a matching first network resource based on the performance requirement for the first network resource, wherein the available capacity of the matching first network resource meets the performance requirement for the first network resource; and returning an identifier of the matching first network resource to the first management server, wherein the first network resource whose resource information has changed is an allocated first network resource, and the allocated first network resource is one or more network resources among the matching first network resources.

[0067] Optionally, the method further includes: receiving performance requirements for a first network resource sent by a first management server; obtaining a matching first network resource based on the performance requirements for the first network resource, wherein the available capacity of the matching first network resource meets the performance requirements for the first network resource; determining an allocated first network resource from the matching first network resource based on a scheduling algorithm; returning an identifier of the allocated first network resource to the first management server, wherein the first network resource whose resource information has changed is the allocated first network resource, and the allocated first network resource is one or more network resources among the matching first network resources.

[0068] In one implementation, the resource information of the first network resource includes one or more of the following: planning information of the allocated first network resource, load information of the allocated first network resource after this allocation, demand information for the allocated first network resource, available capacity of the allocated first network resource determined before this allocation, alarm information of the allocated first network resource, and the correspondence between the allocated first network resource and other network resources. Therefore, the remaining available capacity is determined based on multiple pieces of information, making the determined remaining available capacity more accurate and effective.

[0069] In one implementation, obtaining a matching first network resource based on the performance requirements of the first network resource includes: sending a query request to a resource information query server, the query request carrying the performance requirements of the first network resource, the query request being used to query the available first network resources whose capabilities meet the performance requirements; and receiving information on the matching first network resources returned by the resource information query server. Specifically, the matching first network resource is determined based on the available capabilities of the existing first network resources. Further, the management data analysis server periodically updates the available capabilities of the existing first network resources to the resource information management server.

[0070] Eighthly, this application provides a management data analysis server. This management data analysis server includes functional modules that execute the network resource management method provided in the seventh aspect or any possible design of the seventh aspect. This application does not limit the division of functional modules; the functional modules can be divided according to the process steps of the network resource management method in the seventh aspect, or according to specific implementation needs. The functional modules can be implemented in hardware or by hardware executing corresponding software. For example, they include: a receiving module, a sending module, and a processing module.

[0071] Ninthly, this application provides a management data analysis server. The management data analysis server includes a memory for storing program code, and a processor for calling the program code to implement the network resource management method of the seventh aspect of this application and any possible design thereof.

[0072] In a tenth aspect, this application provides a readable storage medium storing instructions that, when executed, enable a device executing the instructions (such as a resource information server) to implement any of the network resource management methods of the first or seventh aspect of this application.

[0073] In the eleventh aspect, this application provides a computer program product containing instructions that, when run on a computer, cause the computer to implement any network resource management method of the first or seventh aspect of this application.

[0074] In a twelfth aspect, this application provides a chip that, when running, can implement any of the network resource management methods of the first or seventh aspect of this application.

[0075] In a thirteenth aspect, this application provides a method for network resource management, which is performed jointly by multiple devices.

[0076] The first management server sends a performance requirement for a first network resource to the management data analysis server. This first network resource can be any one of CSI, NSI, NSSI, or NF. Upon receiving the performance requirement, the management data analysis server obtains a matching first network resource and returns its identifier to the first management server. The available capacity of this matching first network resource satisfies the performance requirement. The first management server then determines which first network resource to use, which is one or more of the matching first network resources.

[0077] Furthermore, the first management server triggers an update to the availability of the first allocated network resources.

[0078] In one implementation, the management data analysis server acquiring a matching first network resource includes: the management data analysis server sending a query request to a resource information query server, the query request carrying the performance requirements for the first network resource; and receiving an identifier of the matching first network resource returned by the resource information query server, the matching first network resource being determined based on the available capabilities of existing first network resources.

[0079] Optionally, the management data analysis server periodically updates the availability of the existing first network resources to the resource information management server.

[0080] Optionally, the method further includes: after receiving the query request, the resource information query server determines a matching first network resource based on the available capabilities of existing first network resources stored in the resource information database, and returns the identifier of the matching first network resource to the management data analysis server. It should be understood that the resource information query server may return information about the matching first network resource to the management data analysis server, including the identifier, available capabilities, and / or load of the matching first network resource, etc.

[0081] In one implementation, the first management server triggers an update on the availability of the allocated first network resource, including:

[0082] The first management server sends an update request to the resource information management server. This update request carries the identifier of the allocated first network resource and is used to trigger an update of the available capacity of the allocated first network resource. Further, the management data analysis server receives a resource change notification, which carries the identifier of the allocated first network resource to indicate a change in the resource information of the allocated first network resource. This resource change notification is sent after the resource information management server receives the update request. The management data analysis server determines the remaining available capacity of the allocated first network resource after this allocation and sends this remaining available capacity to the resource information management server. This remaining available capacity is used to update the available capacity of the allocated first network resource.

[0083] In one implementation, the first management server triggers an update on the availability of the allocated first network resource, including:

[0084] The first management server sends a resource change notification, which carries the identifier of the allocated first network resource to indicate that the resource information of the allocated first network resource has changed. After receiving the resource change notification, the management data analysis server determines the remaining available capacity of the allocated first network resource after this allocation and sends the remaining available capacity to the resource information management server. The remaining available capacity is used to update the available capacity of the allocated first network resource.

[0085] In one implementation, the management data analysis server determines the remaining available capacity of the first network resource allocated after this allocation, including:

[0086] The management data analysis server determines the remaining available capacity of the allocated first network resource after this allocation based on the resource information of the first network resource. The resource information of the allocated first network resource includes one or more of the following: planning information of the allocated first network resource, load information of the allocated first network resource after this allocation, demand information for the allocated first network resource, available capacity of the allocated first network resource determined before this allocation, alarm information of the allocated first network resource, and the correspondence between the allocated first network resource and other network resources.

[0087] Optionally, the management data analysis server obtains the resource information of the first network resource allocated from the resource information management server or the resource information query server.

[0088] In one implementation, the first management server determines the use of the allocated first network resource by selecting the allocated first network resource from the matched first network resources based on a scheduling algorithm.

[0089] Optionally, the method further includes: the resource information management server receiving the remaining available capacity of the allocated first network resource after this allocation from the management data analysis server, and updating the available capacity of the allocated first network resource stored in the resource information database to the remaining available capacity.

[0090] Optionally, the method further includes: the resource information management server obtaining the load information of the allocated first network resource after the allocation from the network data analysis server, and updating the load information of the allocated first network resource stored in the resource information database to the load information of the allocated first network resource after the allocation. Further, the resource information management server or the resource information query server sends the load information of the allocated first network resource after the allocation to the management data analysis server, wherein the remaining available capacity is determined based on the load information of the allocated first network resource after the allocation.

[0091] It should be understood that this aspect may also include any of the above-mentioned options, which will not be elaborated here.

[0092] In a fourteenth aspect, this application provides a system for network resource management. The system includes: a first management server and a management data analysis server, wherein the first management server is used to execute the method executed by the first management server in the thirteenth aspect of this application and any possible design thereof; and the management data analysis server is used to execute the method executed by the management data analysis server in the thirteenth aspect of this application and any possible design thereof.

[0093] Optionally, the system further includes: a resource information query server, a resource information database, and / or a resource information management server, wherein the resource information query server, the resource information database, and / or the resource information management server are respectively used to execute the method executed by the resource information query server, the resource information database, and / or the resource information management server in the thirteenth aspect of this application and any possible design thereof.

[0094] In a fifteenth aspect, this application provides a method for network resource management, which is performed jointly by multiple devices.

[0095] The first management server sends a performance requirement for a first network resource to the management data analysis server. Here, the first network resource is any one of CSI, NSI, NSSI, or NF. After receiving the performance requirement, the management data analysis server obtains the allocated first network resource and returns the identifier of the allocated first network resource to the first management server. The available capacity of the allocated first network resource meets the performance requirement.

[0096] Furthermore, the first management server determines to use the allocated first network resource and triggers an update on the availability of the allocated first network resource.

[0097] In one implementation, the management data analysis server obtains the allocated first network resource by: the management data analysis server obtaining an identifier of a matching first network resource based on the performance requirements for the first network resource, the matching first network resource being determined based on the available capacity of existing first network resources; and determining the allocated first network resource from the matching first network resource.

[0098] In one implementation, the management data analysis server obtains the identifier of the matching first network resource based on the performance requirements for the first network resource by: sending a query request to a resource information query server, the query request carrying the performance requirements for the first network resource; and receiving the identifier of the matching first network resource returned by the resource information query server.

[0099] In one implementation, the management data analysis server determines the allocated first network resource from the matched first network resources by: the management data analysis server determining the allocated first network resource from the matched first network resources based on a scheduling algorithm.

[0100] Optionally, the management data analysis server periodically updates the availability of the existing first network resource to the resource information management server.

[0101] Optionally, the method further includes: after receiving the query request, the resource information query server determines a matching first network resource based on the available capabilities of existing first network resources stored in the resource information database, and returns the identifier of the matching first network resource to the management data analysis server. It should be understood that the resource information query server may return information about the matching first network resource to the management data analysis server, including the identifier, available capabilities, and / or load of the matching first network resource, etc. Further, the management data analysis server determines the allocated first network resource based on a scheduling algorithm and the information of the matching first network resource.

[0102] In one implementation, the first management server triggers an update on the availability of the allocated first network resource, including:

[0103] The first management server sends an update request to the resource information management server. This update request carries the identifier of the allocated first network resource and is used to trigger an update of the available capacity of the allocated first network resource. Further, the management data analysis server receives a resource change notification, which carries the identifier of the allocated first network resource to indicate that the resource information of the allocated first network resource has changed. This resource change notification is sent after the resource information management server receives the update request. The management data analysis server determines the remaining available capacity of the allocated first network resource after this allocation, and this remaining available capacity is used to update the available capacity of the allocated first network resource.

[0104] In one implementation, the first management server triggers an update on the availability of the allocated first network resource, including:

[0105] The first management server sends a resource change notification, which carries the identifier of the allocated first network resource to indicate that the resource information of the allocated first network resource has changed. After receiving the resource change notification, the management data analysis server determines the remaining available capacity of the allocated first network resource after this allocation and sends the remaining available capacity to the resource information management server. The remaining available capacity is used to update the available capacity of the allocated first network resource.

[0106] In one implementation, the management data analysis server determines the remaining available capacity of the first network resource allocated after this allocation, including:

[0107] The management data analysis server determines the remaining available capacity of the allocated first network resource after this allocation based on the resource information of the first network resource. The resource information of the allocated first network resource includes one or more of the following: planning information of the allocated first network resource, load information of the allocated first network resource after this allocation, demand information for the allocated first network resource, available capacity of the allocated first network resource determined before this allocation, alarm information of the allocated first network resource, and the correspondence between the allocated first network resource and other network resources.

[0108] Optionally, the management data analysis server obtains the resource information of the first network resource allocated from the resource information management server or the resource information query server.

[0109] Optionally, the method further includes: the resource information management server receiving the remaining available capacity of the allocated first network resource after this allocation from the management data analysis server, and updating the available capacity of the allocated first network resource stored in the resource information database to the remaining available capacity.

[0110] Optionally, the method further includes: the resource information management server obtaining the load information of the allocated first network resource after the allocation from the network data analysis server, and updating the load information of the allocated first network resource stored in the resource information database to the load information of the allocated first network resource after the allocation. Further, the resource information management server or the resource information query server sends the load information of the allocated first network resource after the allocation to the management data analysis server, wherein the remaining available capacity is determined based on the load information of the allocated first network resource after the allocation.

[0111] It should be understood that this aspect may also include any of the above-mentioned options, which will not be elaborated here.

[0112] In a sixteenth aspect, this application provides a system for network resource management. The system includes: a first management server and a management data analysis server, wherein the first management server is used to execute the method executed by the first management server in the fifteenth aspect of this application and any possible design thereof; and the management data analysis server is used to execute the method executed by the management data analysis server in the fifteenth aspect of this application and any possible design thereof.

[0113] Optionally, the system further includes: a resource information query server, a resource information database, and / or a resource information management server, wherein the resource information query server, the resource information database, and / or the resource information management server are respectively used to execute the method executed by the resource information query server, the resource information database, and / or the resource information management server in the fifteenth aspect of this application and any possible design thereof. Attached Figure Description

[0114] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application or the background art will be described below.

[0115] Figure 1 A system architecture diagram for network resource management provided in the embodiments of this application;

[0116] Figure 2 Another system architecture diagram for network resource management provided in this application embodiment;

[0117] Figure 3 A schematic diagram of the network resource topology provided in the embodiments of this application;

[0118] Figure 4 A flowchart illustrating a method for network resource management provided in this application embodiment;

[0119] Figure 5 A flowchart illustrating a method for managing the availability of network resources provided in an embodiment of this application;

[0120] Figure 6 A flowchart illustrating another method for managing the availability of network resources provided in an embodiment of this application;

[0121] Figure 7 A flowchart illustrating another method for network resource management provided in this application embodiment;

[0122] Figure 8 This is a schematic diagram of the structure of the resource information server provided in the embodiments of this application;

[0123] Figure 9 Schematic diagrams of the structures of various devices provided in the embodiments of this application;

[0124] Figure 10 This is a schematic diagram of the structure of the management data analysis server provided in an embodiment of this application. Detailed Implementation

[0125] The embodiments of this application are described below with reference to the accompanying drawings.

[0126] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0127] This application can be applied to 5G mobile communication network architecture or future networks.

[0128] like Figure 1 The diagram shown is a system architecture diagram applied in an embodiment of this application. The following is a brief description of the devices in the system applied in this embodiment, and their main functions. Further detailed descriptions will follow in subsequent embodiments of this application.

[0129] The system includes a first management server 101 for deploying and managing first network resources. Specifically, the first management server 101 receives performance requirements for the first network resources and allocates the first network resources according to these requirements, ensuring that the available capacity of the allocated first network resources meets the performance requirements. The first management server 101 further sends an update message to a resource information server 103 to trigger the resource information server 103 to update the available capacity of the allocated first network resources. Thus, when the first network resources are shared, the available capacity of the first network resources is updated promptly after allocation. The performance requirements for the first network resources can originate from user 107 or from the second management server 102. User 107 has a need for the first network resources, specifically a user who has subscribed to the first network resources or a network maintenance personnel, etc. It should be understood that user 107 interacts with the first management server 101 through a user device (not shown in the figure). The user device is a device with communication capabilities, specifically a mobile phone, desktop computer, tablet computer, or laptop computer, etc.

[0130] The system may further include a second management server 102 for deploying and managing the second network resource. The second network resource is deployed on the first network resource. In this application, the second network resource is also referred to as the superior network resource of the first network resource. Similarly, if the first network resource is deployed on a third network resource, the third network resource is referred to as the subordinate network resource of the first network resource (the management server of the third network resource is not shown in the figure).

[0131] When the second management server 102 needs to deploy a second network resource, it requests the first network resource from the first management server 101 to deploy the second network resource. Specifically, the second management server 102 sends the performance requirements of the second network resource to be deployed on the first network resource to the first management server 101, and receives the identifier of the allocated first network resource returned by the first management server 101. Thus, the second network resource to be deployed is deployed on the allocated first network resource.

[0132] Accordingly, the performance requirements for the first network resource received by the first management server 101 are specifically the performance requirements of the second network resource to be deployed on the first network resource, sent by the second management server 102. Furthermore, the first management server 101 also triggers the resource information server 103 to establish a correspondence (also called a mapping relationship) between the second network resource to be deployed and the allocated first network resource. Thus, it is clear which second network resources the first network resource has been deployed on, which is beneficial for maintaining information on the availability of the first network resource.

[0133] If the second network resource to be deployed was already deployed on a first network resource (referred to as the initial first network resource) before this allocation, meaning this allocation is a reallocation, then the first management server 101 also triggers the resource information server 103 to update the correspondence between the second network resource to be deployed and the initial first network resource to the correspondence between the second network resource to be deployed and the allocated first network resource. Furthermore, the first management server 101 also triggers the resource information server 103 to update the available capacity of the initial first network resource. Thus, the correspondence between the first network resource and the second network resource is dynamically updated, and because the resources of the initial first network resource occupied by the second network resource to be deployed are released, the timely update of the available capacity of the initial first network resource is beneficial for subsequent resource allocation.

[0134] The system may further include a resource information server 103, used to store and manage resource information of network resources and provide query services for resource information of network resources. The resource information of the network resources includes one or more of the following: attribute information of a first network resource, relationships between first network resources, attribute information of a second network resource, the correspondence between the first and second network resources, and relationships between second network resources. The attribute information may include one or more of the following: available capacity, load information, demand information, planning information, alarm information, etc., which will be further described in detail in subsequent embodiments of this application. Specifically, the resource information server 103 may include a resource information database 1031, a resource information query server 1032, and a resource information management server 1033.

[0135] The resource information database 1031 is used to store resource information of network resources, and the resource information database 1031 can be centralized or distributed. Resource information is stored in the form of a topology. Each topology node stores the attribute information of the network resources of that node. Topology nodes are connected by topology edges to represent the correspondence between nodes. It should be understood that the topology edges can be directed edges, such as the edge between the first network resource node and the second network resource node, which is used to describe the correspondence between the second network resource deployed on the first network resource; the topology edges can also be undirected, such as the edge between the first network resource nodes is an undirected edge, which is used to describe the correspondence between multiple first network resources deployed on the same second network resource. Of course, the correspondence between network resources can also be stored as attribute information in the topology nodes, in which case topology edges are not needed, and this application does not limit this. It should be understood that resource information can also be stored in other forms, such as tables, etc. This application uses topology as an example for illustration.

[0136] The resource information query server 1032 is used to query resource information, such as querying information about a first network resource based on its identifier, or obtaining a set of first network resources that meet certain conditions. Specifically, the resource information query server 1032 receives a query request carrying performance requirements for the first network resources. Based on the available capabilities of existing first network resources stored in the resource information database 1031, it determines the first network resource whose available capabilities meet the performance requirements (referred to as the matched first network resource) and returns the identifier of the matched first network resource. Thus, when first network resources are shared, the available capabilities of existing first network resources are used to match performance requirements, efficiently and accurately determining the first network resource that can meet those requirements.

[0137] The resource information management server 1033 is used to manage the resource information, such as performing operations like adding, updating, and deleting the resource information. Specifically, the resource information management server 1033 can be used to update the availability of the first network resource stored in the resource information database 1031, and / or the correspondence between the first network resource and the second network resource. The first management server 101 is used to send an update request carrying the identifier of the allocated first network resource to the resource information management server, thereby triggering the resource information management server 1033 to update the availability of the allocated first network resource stored in the resource information database 1031. The update request further carries the identifier of the second network resource to be deployed, thereby triggering the resource information management server 1033 to establish a correspondence between the second network resource to be deployed and the allocated first network resource in the resource information database 1031. Therefore, the first management server 101 can trigger the resource information management server 1033 to update the availability of the first network resource and the correspondence between the first network resource and the second network resource in a timely manner.

[0138] It should be understood that the resource information server 103 can be centrally deployed, for example, the resource information database 1031, the resource information query server 1032, and the resource information management server 1033 can be deployed together; the resource information server 103 can also be distributed, for example, the resource information database 1031, the resource information query server 1032, and the resource information management server 1033 can be deployed on different physical devices. Furthermore, the functions of the resource information server 103 can be deployed on one or more separate physical devices, or it can be deployed together with one or more other servers, for example, the resource information server 103 and the MDAS 104 device can be deployed together, etc. This application embodiment does not limit this aspect.

[0139] The system may further include a Management Data Analytics Server (MDAS) 104, which is a device for providing Management Data Analytics Function (MDAF). In this application, MDAS 104 is used to provide the resource information server 103 with the availability of network resources. Specifically, MDAS 104 periodically determines the availability of a first network resource, thereby periodically providing the availability of the first network resource to the resource information management server 103 (periodic update).

[0140] In addition, MDAS104 can also redetermine and update the available capabilities in the resource information database 1031 based on changes in the resource information stored therein (event-triggered update). For example, after receiving the update request carrying the identifier of the allocated first network resource, the resource information management server 1033 sends a resource change notification to MDAS104 to notify MDAS104 that the available capability of the allocated first network resource has changed, thereby triggering MDAS104 to redetermine the remaining available capability of the allocated first network resource after this allocation and provide the remaining available capability to the resource information management server 1033.

[0141] It should be understood that the functionality of MDAS104 can be deployed in one or more separate physical devices, or it can be deployed together with one or more other servers. This application does not limit this.

[0142] The system may also include a Network Data Analytics Server (NWDAS) 105, which is a device for providing Network Data Analytics Function (NWDAF). In this application, NWDAS 105 is used to provide load information of network resources to resource information server 103. Specifically, NWDAS 105 periodically determines and provides load information of the first network resource to resource information management server 1033 (periodic update). In addition, NWDAS 105 also updates the load information in the resource information database 1031 in a timely manner based on changes in the resource information stored therein (event-triggered update). For example, after receiving the update request carrying the identifier of the allocated first network resource, resource information management server 1033 sends a resource change notification to NWDAS 105, thereby triggering NWDAS 105 to re-determine the load information of the allocated first network resource after this allocation, and provide the load information of the allocated first network resource after this allocation to resource information management server 1033.

[0143] It should be understood that the functionality of NWDAS105 can be deployed in one or more separate physical devices, or it can be deployed together with one or more other servers. This application does not limit this.

[0144] The system may further include a resource scheduling server 106. The resource scheduling server 106 is used to perform resource scheduling on the first network resources based on a scheduling algorithm, such as selecting suitable first network resources. Specifically, after receiving the performance requirements for the first network resources sent by the first management server 101, the resource scheduling server 106 queries the resource information query server 1032 for available first network resources (hereinafter referred to as matched first network resources) that meet the performance requirements. Then, based on the scheduling algorithm, it determines the allocated first network resource from the matched first network resources and returns the allocated first network resource to the first management server 101. Thus, the allocated first network resource not only meets the performance requirements but also other resource scheduling requirements, such as Quality of Service (QoS) requirements, which is beneficial for optimizing resource scheduling.

[0145] The resource scheduling server 106 is used to store one or more scheduling algorithms, and can be further configured with algorithm plugins for uploading, updating, or deleting scheduling algorithms. When multiple scheduling algorithms are used for resource scheduling, the resource scheduling server 106 is also used to configure the weights of the scheduling algorithms to determine the final result based on the results of multiple scheduling algorithms and the corresponding weights of each scheduling algorithm.

[0146] It should be understood that the functions of the resource scheduling server 106 can be deployed in one or more separate physical devices, or co-deployed with one or more other servers, and the functions of the resource scheduling server 106 can be deployed in multiple physical devices. This application embodiment does not limit this. In one possible implementation, the resource scheduling server 106 and the first management server 101 are co-deployed. In this case, the first management server 101 can also be considered to provide the functions of the resource scheduling server 106. In one possible implementation, the resource scheduling server 106 and the MDAS 104 are co-deployed. In this case, the MDAS 104 can also be considered to provide the functions of the resource scheduling server 106. In one possible implementation, a portion of the functions of the resource scheduling server 106 are deployed in the first management server 101, and another portion of the functions are deployed in the MDAS 104. For example, the function of the resource scheduling server 106 to query matching first network resources is deployed in the MDAS 104, and the function to determine the allocated first network resources from the matching first network resources is deployed in the first management server 101.

[0147] like Figure 2The diagram shown is another system architecture diagram applied in an embodiment of this application. Further explanation will follow. Figure 1 The document specifies which existing servers the first management server 101 and the second management server 102 are, what the network resources specifically include, and what the available capabilities of the network resources are. Furthermore, this application embodiment further provides definitions of the capacity model and load model in the network resource model, as well as a definition of the network resource topology.

[0148] The Communication Service Management Server (CSMS) 202 is a device used to provide Communication Service Management Function (CSMF). CSMS 202 is used for the deployment and management of CSI.

[0149] Specifically, CSMS202 is used to receive performance requirements for CSI. These performance requirements originate from Communication Service User 207. These requirements are defined in the Service Level Agreement (SLA). Communication Service User 207 is a user with communication service needs, such as a subscriber to a communication service, like an operator. Communication Service User 207 can submit CSI performance requirements to CSMS202 through the Business Support System (BSS). For example, Company A (Communication Service User 207) has expanded its autonomous driving business and therefore has the following requirements for communication services supporting autonomous driving: low latency, so that control commands sent by the driving controller can be quickly transmitted to the vehicle. Therefore, Company A logs into the BSS through its user equipment and negotiates the SLA with CSMS202, i.e., submitting its CSI performance requirements (low latency) to CSMS202. Additionally, the SLA may include other requirements, such as signal coverage area, stability, etc.

[0150] When CSIs are shareable and available, CSMS202 is used to obtain the identifier of an assigned CSI from existing CSIs based on the performance requirements for the CSI, and the available capabilities of the assigned CSI meet the performance requirements. For details, please refer to the descriptions of other embodiments in this application; simply replace the first management server 101 with CSMS202 and the first network resource with a CSI, which will not be repeated here. In this case, Figure 1 User 107 in the text is specifically communication service user 207.

[0151] In cases where CSI is not shared or no CSI is available, CSMS202 is used to create a new CSI. Specifically, CSMS202 translates the performance requirements for the CSI into performance requirements for the Network Slice Instance (NSI), and sends these performance requirements for the NSI to NSMS203 through the interface with the Network Slice Management Server (NSMS) 203, requesting NSMS203 to allocate an NSI for deploying the CSI.

[0152] Continuing with the example of autonomous driving services, if Company A (a car transport company) does not agree to share a CSI, or if no available CSI meets Company A's SLA (Service Level Agreement), then CSMS202 will create a new CSI to provide services to Company A. The new CSI is deployed on an NSI (Network Slice Injection). The NSI encapsulates network slice resources to support the operation of the CSI. Correspondingly, the low latency requirement for the CSI in the SLA translates into performance requirements for the NSI, such as URLLC-type NSIs, minimum NSI latency, etc. Therefore, CSMS202 requests NSMS203 to allocate an NSI to deploy the new CSI.

[0153] Considering the scenario where CSIs can be shared, the communication service user 207 sharing the CSI is referred to as tenant 206. Tenant instances (TIs) are abstracted on a per-tenant basis, and a tenant management server 201 is set up to manage the TIs uniformly. Therefore, the performance requirements for the CSI can also be received from the tenant management server 201, specifically the performance requirements of the TI for the CSI. In this case, the tenant management server 201 is used to implement the function of the second management server 102, and correspondingly, the second network resource is the TI. Continuing with the example of the aforementioned autonomous driving service, if car transport company A and car transport company B share a certain CSI, such as CSI-1, then the communication service provided by CSI-1 for car transport company A can be abstracted as TI-A, and the communication service provided by CSI-1 for car transport company B can be abstracted as TI-B. The tenant management server 201 manages TI-A and TI-B uniformly.

[0154] Tenant Management Server 201 is a device used to provide tenant management functions. Tenant Management Server 201 can be deployed in the BSS or on a separate physical device. Specifically, Tenant Management Server 201 receives performance requirements for TI from tenant 206 and translates these requirements into performance requirements for CSI. It should be understood that the performance requirements for TI and CSI can be the same, in which case no performance requirement translation is performed. Tenant Management Server 201 also sends the performance requirements for CSI to CSMS202 through its interface with CSMS202, requesting CSMS202 to allocate CSI to deploy the TI.

[0155] The Network Slice Management Server (NSMS) 203 is a device used to provide Network Slice Management Function (NSMF). The NSMS 203 is used for the deployment and management of NSI (Network Slice Management).

[0156] Specifically, NSMS203 is used to receive performance requirements for NSI, which may be a service profile or a key performance indicator (KPI) within the service profile. These performance requirements originate from network slicing user 208. Network slicing user 208 is a user with network slicing needs, specifically a user who has subscribed to network slices, or network maintenance personnel, etc. In this case, Figure 1 User 107 in this context is specifically network slice user 208. It should be understood that authorized access to NSMS203 can be granted to network slice user 208, thereby allowing network slice user 208 to request NSI from NSMS203 and use the obtained NSI for its own communication services.

[0157] The performance requirements for NSI can also come from CSMS202, specifically the performance requirements of CSI for NSI. In this case, CSMS202 is used to implement the functions of the second management server 102, and correspondingly, the second network resource is CSI.

[0158] When NSIs are shareable and available, NSMS203 is used to obtain the identifier of an assigned NSI from existing NSIs based on the performance requirements for the NSIs, and the available capabilities of the assigned NSIs meet the performance requirements. For details, please refer to the descriptions of other embodiments of this application; simply replace the first management server 101 with NSMS203 and the first network resource with an NSI, which will not be elaborated further here.

[0159] In the event that an NSI is not shared, or that no NSI is available, NSMS203 is used to create a new NSI. Specifically, NSMS203 translates the performance requirements for the NSI into performance requirements for the Network Slice Subnet Instance (NSSI), and sends these performance requirements to NSSMS204 through the interface with the Network Slice Subnet Management Server (NSSMS) 204, requesting NSSMS204 to allocate an NSSI for deployment. It should be understood that the performance requirements for the NSI can be translated into multiple performance requirements for the NSSI, and these multiple performance requirements for the NSSI can be sent to multiple different Network Slice Subnet Management Servers 204.

[0160] Using the aforementioned autonomous driving service as an example, when CSMS202 requests an NSI to deploy a new CSI, NSMS203 determines that no NSI is available, so NSMS203 needs to create a new NSI. Network slicing can be divided into multiple network slice subnets, such as access network slices, core network slices, etc. Correspondingly, NSIs can be divided into RadioAccess Network-Network Slice Subnet Instances (RAN-NSSI), Core Network-Network Slice Subnet Instances (CN-NSSI), etc. Therefore, NSMS203 needs to allocate an NSSI for the new NSI request. First, the performance requirements for the NSI are converted into performance requirements for the NSSI itself, for example, into performance requirements for RAN-NSSI and CN-NSSI. Then, NSMS203 requests the allocation of an NSSI from NSSMS204 to deploy the new NSI based on the performance requirements for the NSSI.

[0161] The Network Slice Subnet Management Server (NSSMS) 204 is a device used to provide Network Slice Subnet Management Function (NSSMF). Specifically, the NSSMS 204 is used for the deployment and management of NSSI.

[0162] Specifically, NSSMS204 is used to receive performance requirements for NSSI. These performance requirements can be either from a slice profile or KPIs within the slice profile. These performance requirements originate from network slice subnet user 209. Network slice subnet user 209 is a user with network slice subnet requirements, specifically a user who has subscribed to network slice subnets, or network maintenance personnel, etc. In this case, Figure 1 User 107 in the above context is specifically network slice subnet user 209. It should be understood that authorized access from NSSMS204 can be granted to network slice subnet user 209, thereby allowing network slice subnet user 209 to request NSSI from NSSMS204 and use the obtained NSSI for its own NSI or CSI deployment.

[0163] The performance requirements for NSSI can also come from NSMS203, specifically the performance requirements of NSI for NSSI. In this case, NSMS203 is used to implement the functions of the second management server 102, and correspondingly, the second network resource is NSI.

[0164] When NSSIs are shareable and available, NSMS203 is used to obtain the identifier of an assigned NSSI from existing NSSIs based on the performance requirements for the NSSIs, and the available capabilities of the assigned NSSIs meet the performance requirements. For details, please refer to the descriptions of other embodiments of this application; simply replace the first management server 101 with NSSMS204 and the first network resource with an NSSI, which will not be elaborated further here.

[0165] In the event that the NSSI is not shared, or there is no available NSSI, NSSMS204 is used to create a new NSSI. Specifically, NSSMS204 translates the performance requirements for the NSSI into performance requirements for the Network Function (NF), and sends these performance requirements for the NF to NFMS205 through the interface with the Network Function Management Server (NFMS)205, requesting NFMS205 to allocate an NF to deploy the NSSI.

[0166] Using the aforementioned autonomous driving service as an example, when NSMS203 requests an NSSI to deploy a new NSSI, if NSSMS204 determines that no NSSI is available, then NSSMS204 must create a new NSSI. A network slice subnet is composed of various network elements, and the functions provided by these elements (such as functional behaviors and interfaces) are collectively referred to as NFs. Correspondingly, an NSSI can be divided into multiple NFs. For example, CN-NSSI includes Session Management Functions (SMF) for providing session management services, User Plane Functions (UPF) for providing user plane services, and driving control functions for providing autonomous driving control, etc.; RAN-NSSI includes 5G base stations (New Radio NodeBs, gNBs) for providing radio access services, etc. Therefore, NSSMS204 must allocate NFs for new NSSI requests. First, the performance requirements for the NSSI are transformed into performance requirements for the NFs. For example, the performance requirements for CN-NSSI are decomposed into performance requirements for SMF, UPF, driving control functions, etc., and the performance requirements for RAN-NSSI are decomposed into performance requirements for multiple gNBs. Next, NSSMS 204 requests NFMS205 to allocate an NF to deploy a new NSSI based on the performance requirements of the NF.

[0167] The Network Function Management Server (NFMS) 205 is a device used to provide network function management capabilities. Specifically, NFMS 205 is used for the deployment and management of Network Functions (NFs), either deployed within the Element Management System (EMS) or on a separate physical device. NFs can be implemented through dedicated hardware, software instances running on dedicated hardware, or virtual functions instantiated on a virtual platform (such as a cloud platform), etc.

[0168] Specifically, NFMS205 is used to receive performance requirements for NFs. These performance requirements for NFs come from Network Function User 210. Network Function User 210 is a user with network function requirements, specifically a user who has subscribed to network functions, or network maintenance personnel, etc. In this case, Figure 1 User 107 in this context is specifically Network Function User 210. It should be understood that authorized access to NFMS 205 can be granted to Network Function User 210, thereby allowing Network Function User 210 to request an NF from NFMS 205 and use the obtained NF for its own NSI, NSSI, or CSI deployment.

[0169] The performance requirements for NF can also come from NSSMS204, specifically the performance requirements of NSSI for NF. In this case, NSSMS204 is used to implement the functions of the second management server 102, and correspondingly, the second network resource is NSSI.

[0170] When NFs are shareable and available, NSSMS204 is used to obtain the identifier of an allocated NF from existing NFs based on the performance requirements for the NF, and the available capabilities of the allocated NF meet the performance requirements. For details, please refer to the descriptions of other embodiments of this application; simply replace the first management server 101 with NFMS205 and the first network resource with an NF, which will not be elaborated further here.

[0171] When an NF is not shared, or when no NF is available, NFMS 205 is used to create a new NF. Specifically, NFMS 205 selects suitable physical resources from its managed pool of physical resources to create a new NF.

[0172] Resource information server 103 is used to store and manage resource information of one or more network resources and to provide resource information querying. The network resources here include at least one of TI, CSI, NSI, NSSI, and NF mentioned above. The resource information includes available capacity, load information, demand information, planning information, alarm information, and / or the correspondence between network resources, etc. Resource information server 103 includes resource information database 1031, resource information query server 1032, and resource information management server 1033.

[0173] In one implementation, the resource information database 1031 is deployed at different levels to store resource information for each network resource. For example, the resource information database 1031 is deployed at the communication service level to store CSI resource information, and at the network slice level to store NSI resource information. Optionally, the resource information databases 1031 at each level are deployed on the management server of the corresponding network resource, and the management server of each network resource is also used to store the resource information of that network resource. That is, the resource information of the first network resource is stored in the first network management server 101. For example, the resource information of CSI is stored in CSMS202, and the resource information of NSI is stored in NSMS203.

[0174] Correspondingly, the resource information query server 1032 and the resource information management server 1033 can also be deployed at different levels. In this case, the resource information servers 103 at each level are deployed on the management servers of the corresponding network resources. That is, the resource information server 103 of the first network resource is deployed on the first network management server 101. For example, the resource information server 103 at the communication service level is deployed on CSMS202, meaning that CSMS202 also provides the functions of storing, managing, and querying CSI resource information; the resource information server 103 at the network slice level is deployed on NSMS203, meaning that NSMS203 also provides the functions of storing, managing, and querying NSI resource information, and so on.

[0175] Of course, the resource information query server 1032 can still be centrally deployed to uniformly provide resource information queries for various network resources, thereby improving the efficiency of resource information queries. The centralized resource information query server 1032 is used to access resource information databases 1031 at various levels to obtain the required resource information for each network resource. The resource information management server 1033 is similar and will not be described further. Furthermore, the resource information query server 1032 and the resource information management server 1033 can be deployed separately or together; this application does not limit this.

[0176] In another implementation, the resource information database 1031 is centrally deployed to store resource information for each network resource. The resource information database 1031 interacts with the management servers of each network resource through the resource information management server 1033 to obtain the latest resource information for each network resource. For example, after allocating an NSI, the NSMS 203 sends an update message carrying the identifier of the allocated NSI to the resource information management server 1033, so that the resource information management server 1033 updates the availability of the allocated NSI stored in the resource information database 1031. See the descriptions of other embodiments in this application for details. Accordingly, both the resource information query server 1032 and the resource information management server 1033 can be centrally deployed, and will not be described further.

[0177] The definition of a Network Resource Model (NRM) facilitates the management of information about various network resources. For situations where network resources are shareable, extending the capability model within the NRM is beneficial, enabling the rapid determination of allocated network resources based on their available capabilities during resource allocation. The extended capability model within the NRM defines the available capabilities of network resources. This capability model is referred to as the NRM Capability Profile, and this application uses this name as an example, without limiting the use of other names to represent the network resource capability model. Broadly speaking, network resource planning information (total network resource capacity, i.e., the maximum planned capacity of the network resource), network resource load information (used capacity, i.e., the capacity of the network resource that has been occupied), and network resource availability (the capacity of the network resource that can still be allocated) can all be considered network resource capability information. In this embodiment, the definition of the available capabilities of network resources using a capability model is used as an example. The capability model can further define network resource planning information and network resource load information, which is not limited in this application.

[0178] For example, the parameters that an NRM Capability Profile may include are shown in Table 1:

[0179] Table 1

[0180]

[0181] The identifier (ID) identifies the available capabilities of the network resource. The description adds descriptive information about the available capabilities. Capability attributes are a collection of available capabilities across various dimensions, specifically an array type, inherited and extended by subclasses. Support Qualifier indicates whether the parameter is a required parameter (M for required, C for optional). isReadable indicates whether the parameter is readable (T for readable, F for unreadable). isWritable indicates whether the parameter is writable (T for writable, F for unwritable). isInvariant indicates whether the parameter is immutable (T for immutable, F for mutable). isNotifyable indicates whether the parameter is notifyable (T for notifyable, F for unnotifyable). It should be understood that the SupportQualifier, isReadable, isWritable, isInvariant, and isNotifyable properties of each parameter in Table 1 are exemplary, and those skilled in the art can set them according to their needs; this application does not limit this.

[0182] Therefore, each network resource can inherit the NRM Capability Profile and derive its own capability model. First, we introduce the NSI capability model (called the NSI Capability Profile). The NSI Capability Profile defines the available capabilities of NSI, specifically describing the capabilities that NSI can still allocate without affecting the operation of CSIs already deployed on NSI or meeting the needs of users to whom NSI has been allocated. The NSI Capability Profile may specifically include: 1) NSI capability identifier, used to identify the available capabilities of NSI, which can be an NSI ID or an ID corresponding to an NSI ID, where the NSI ID is used to identify the NSI; 2) NSI description; 3) NSI capability attributes, which may include one or more of the following parameters:

[0183] a. The maximum number of user devices that NSI can support can be represented by NSIMaxNumberofUEsCap;

[0184] b. The maximum number of connections that NSI can support can be represented by NSIMaxNumberofConnsCap;

[0185] c. The uplink traffic that NSI can also support can be represented by NSIULThptCap;

[0186] d. The downlink traffic that NSI can also support can be represented by NSIDLhptCap;

[0187] e. The lowest latency that NSI can support can be represented by NSI LatencyCap;

[0188] f. The coverage area that NSI can also support can be represented by NSICoverageAreaCap;

[0189] g. The maximum data packet that NSI can support for transmission can be represented by NSIMaxPktSizeCap;

[0190] h. NSI also supports the mobile speed of user devices, which can be represented by NSIUEVelocityCap.

[0191] It should be understood that NSI capability attributes may also include other parameters representing NSI capabilities. Furthermore, the parameters of NSI capability attributes can also be represented by parameter identifiers, such as "101" indicating the maximum number of user devices NSI can still support, and "102" indicating the maximum number of connections NSI can still support.

[0192] The CSI capability model (called the CSI Capability Profile) also inherits from the NRM Capability Profile. The CSI Capability Profile is similar to the NSI Capability Profile; please refer to the description of the NSI Capability Profile for details, which will not be repeated here.

[0193] The NSSI capability model (called the NSSI Capability Profile) also inherits from the NRM Capability Profile. The NSSI Capability Profile is similar to the NSI Capability Profile; simply replace NSI with NSSI in the NSI Capability Profile. Further details will not be provided here.

[0194] The NF capability model (called the NF Capability Profile) also inherits from the NRM Capability Profile. The NF Capability Profile is similar to the NSI Capability Profile; see the description of the NSI Capability Profile for details, which will not be repeated here. Optionally, the NF capability attributes also include parameters describing uplink and downlink data transmission capabilities. Taking uplink data transmission capability parameters as an example, the downlink parameters are similar. For example:

[0195] a. The uplink bandwidth guarantee that NF can also support can be represented by NFULGRBCap;

[0196] b. The uplink latency that NF can also support can be represented by NFULLatencyCap;

[0197] c. The uplink data transfer rate that NF can also support can be represented by NFULDataRateCap;

[0198] d. The uplink transmission interval that NF can also support can be represented by NFULTransIntervalCap;

[0199] e. The uplink receive power that NF can also support can be expressed as NFULRecPowerCap;

[0200] f. The uplink signal-to-noise ratio that NF can also support can be represented by NFULSNRCap.

[0201] The values ​​of each parameter in the network resource availability capability are obtained through calculation. Specifically, MDAS104 is used to calculate and provide the network resource availability capability to the resource information server 103, as detailed in other embodiments of this application. MDAS104 can be deployed centrally to provide the availability capability of each network resource, or deployed at different levels to provide the availability capability of each network resource separately. For example, MDAS104 can be deployed at the network slice level to provide NSI availability capability, and at the communication service level to provide CSI availability capability.

[0202] Load information of network resources can be used to determine the availability of network resources. Therefore, extending the load model in NRM facilitates the determination of network resource availability. The extended load model in NRM is used to define the load information of network resources. This load model is called the NRM Performance Profile, and this application uses this name as an example for illustration, without limiting the use of other names to represent the load model of network resources.

[0203] For example, the parameters that an NRM Performance Profile may include are shown in Table 2:

[0204] Table 2

[0205]

[0206] The identifier (ID) identifies the load information of network resources. It should be understood that for the same network resource, the ID of the NRM Load Profile can be the same as the ID of the NRM Capability Profile, facilitating the maintenance and querying of information for the same network resource; for example, both IDs can be the network resource ID. The description adds descriptive information about the load. Load attributes are a collection of load information across various dimensions, specifically an array type, inherited and extended by subclasses. Load attributes include load statistics attributes and / or load prediction attributes. Load statistics attributes are attribute parameters that statistically analyze the load of network resources within a historical time range. Load prediction attributes are attribute parameters that predict the load of network resources within an expected time range. Furthermore, explanations of Support Qualifier, isReadable, isWritable, isInvariant, and isNotifyable can be found in Table 1 and will not be repeated here.

[0207] Therefore, each network resource inherits the NRM Performance Profile and develops its own load model. First, we introduce the NSI load model (called the NSI Performance Profile). The NSI Performance Profile defines the load information of NSI, specifically including: 1) An NSI load identifier, used to identify the NSI load information, specifically an NSI ID, or an ID corresponding to an NSI ID; 2) An NSI description; 3) NSI load attributes, specifically including one or more of the following parameters:

[0208] A. Load statistics attributes:

[0209] a. The usage of NSI's Central Processing Unit (CPU) can be represented by NSICPUUsageStaLoad.

[0210] b. The statistical NSI memory usage can be represented by NSIMemoryUsageLoad;

[0211] c. The statistical disk usage of NSI can be represented by NSIDiskUsageLoad;

[0212] d. The maximum number of user devices in NSI can be represented by NSIMaxNumberofUEsLoad;

[0213] e. The maximum number of connections in NSI can be represented by NSIMaxNumberofConnsLoad;

[0214] f. The uplink traffic of NSI can be represented by NSIULThptLoad.

[0215] g. The downlink traffic of NSI is statistically analyzed and can be represented by NSIDLhptLoad;

[0216] h, the lowest latency of statistical NSI, can be represented by NSILatencyLoad;

[0217] i. The coverage area of ​​the statistical NSI can be represented by NSICoverageAreaLoad;

[0218] j. The maximum data packet transmitted by NSI is statistically represented by NSIMaxPktSizeLoad;

[0219] k, the mobile speed of user equipment in NSI statistics, can be represented by NSIUEVelocityLoad.

[0220] B. Load expectation attributes: The specific parameters are similar to those of load statistics attributes. Simply replace the statistics with the expectation, which will not be elaborated here.

[0221] It should be understood that the NSI load attribute may also include other parameters representing the NSI load, which are not limited in this application. Optionally, the load statistics attribute may also include statistical time to indicate the aforementioned historical time range; the load expectation attribute may also include expected time to indicate the aforementioned expected time range. In addition, each parameter of the NSI load attribute may also be represented by a parameter identifier.

[0222] The CSI load model (called the CSI Perfload Profile) also inherits from the NRM Perfload Profile. The CSI Perfload Profile is similar to the NSI Perfload Profile; please refer to the description of the NSI Perfload Profile for details, which will not be repeated here.

[0223] The NSSI load model (called the NSIPerfload Profile) also inherits from the NRM Perfload Profile. The NSSIPerfload Profile is similar to the NSIPerfload Profile; simply replace NSI with NSSI in the NSIPerfload Profile. Further details will not be provided here.

[0224] The NF load model (which can be called the NF Perfload Profile) can also inherit from the NRM PerfloadProfile. The NF Perfload Profile is similar to the NSIPerfload Profile; see the description of the NSIPerfloadProfile for details, which will not be repeated here. Optionally, the NF load attributes also include parameters describing the uplink and downlink data transmission load, such as the statistical uplink latency of the NF (which can be represented by NFULLatencyLoad). See the parameters describing the uplink and downlink data transmission capabilities in the NF capability model; simply replace the capability description with a load description, which will not be repeated here.

[0225] NWDAS105 is used to provide network resource load information to resource information server 103, as detailed in other embodiments of this application. NWDAS105 can be deployed centrally to provide load information for each network resource, or it can be deployed at different levels to provide load information for each network resource separately. For example, NWDAS105 can be deployed at the network slice level to provide NSI load information, and at the communication service level to provide CSI load information.

[0226] In addition to the available capacity and load information mentioned above, demand information, planning information, alarm information and their corresponding relationships can also be defined in NRM, which will not be elaborated in this application.

[0227] Figure 1 In the illustrated embodiment, as previously described, network resource information can be stored in the form of a topology. Figure 3 In conjunction with specific network resources, a topology diagram of the network resources is further provided to more clearly illustrate the correspondence between various network resources.

[0228] To facilitate unified management of the topology, topology nodes can be defined. For example, the parameters for defining topology nodes are shown in Table 3:

[0229] Table 3

[0230]

[0231] The identifier (ID) is used to identify the topology node; specifically, it is the ID of the network resource of that topology node, or an ID that corresponds to the ID of that network resource, such as... Figure 3 The topology nodes are named TI-1, TI-2, CSI-1, CSI-2, etc. Labels are used to add descriptive information about the topology node, which can be defined by the topology node creator, such as the purpose of creation, aliases, etc. Type indicates the type of the topology node, such as NSINode for NSI nodes. Properties represent the attribute information of the topology node. Attributes can include various capability attributes and / or load attributes mentioned above, as well as planning attributes (for planning information), demand attributes (for demand information), alarm attributes (for alarm information), and / or relationship attributes (for the correspondence between topology nodes), etc. Specific parameters can be found above and will not be repeated here. The demand information of a topology node can include the demand information of the parent topology node for this topology node, and / or the demand information of this topology node for its subordinate topology nodes.

[0232] Figure 3 The circles shown represent topological nodes. The correspondence between topological nodes can be described using topological edges. In this application, the description of the correspondence between topological nodes using topological edges is used as an example. For example, the parameters of the topological edges are defined as shown in Table 4 below:

[0233] Table 4

[0234]

[0235] The identifier (ID) identifies the topological edge. The label describes the correspondence between the two nodes of the topological edge, for example, a CSI-1 node is deployed on top of an NSI-1 node, or an identical CSI node (CSI-1) is deployed on top of both NSI-1 and NSI-2 nodes. The start node and target node represent the two nodes of the topological edge, and can be represented by "From" and "To" respectively. For directed edges ( Figure 3 In a topological edge (represented by a straight line with an arrow), the parent node can be used as the starting node and the child node as the target node. The topological edge between the starting and target nodes indicates that the starting node is deployed on the target node. The reverse is also possible, such as using the child node as the starting node and the parent node as the target node. For undirected edges (…),… Figure 3 Undirected edges are represented by dashed lines, and the starting and destination nodes are arbitrarily determined. Multiplicity describes the mapping relationship between nodes on the topological edge, and can include: ManyToOne (many-to-one mapping); OneToMany (one-to-many mapping); OneToOne (one-to-one mapping); ManyToMany (many-to-many mapping). Properties represent the attribute information of the topological edge; it is an array type that is inherited and expanded by subclasses.

[0236] For example, the following is Figure 3 Description of a topological edge in a given region:

[0237] ID: CSIToNSIA

[0238] From: CSI-1

[0239] To: NSI-1

[0240] Label:the edge between CSI-1and NSI-1

[0241] Multiplicity:OneToMany / / Indicates that CSI-1 is not only deployed on NSI-1

[0242] Properties:

[0243] DeploymentDate: 20200412 / / Indicates the deployment time

[0244] CreatedBy:TI-1 / / Indicates that the creator is TI-1

[0245] From the preceding description or Figure 3As can be seen, TI is deployed on CSI, CSI is deployed on NSI, NSI is deployed on NSSI, and NSSI is deployed on NF. In reality, NSI can also be deployed on NSSI and NF, or even on nested NSIs; this application does not impose any limitations. Furthermore, the network resource topology can describe the resource information of one or more network resources. Figure 3 The resource information for five types of network resources is described as an example.

[0246] Figure 1 In the illustrated embodiment, the resource scheduling server 106 has been described in detail, and similar content will not be repeated here. It should be understood that: 1) The resource scheduling server 106 can be deployed at different levels to perform resource scheduling for each network resource. Thus, the management servers of each network resource interact with their respective resource scheduling servers 106 to achieve resource scheduling. In this case, the resource scheduling server 106 can also be deployed on the management servers of each network resource, i.e., the management servers of each network resource are used to provide resource scheduling functions. For example, NSMS203 is also used to perform resource scheduling for NSI based on a scheduling algorithm; CSMS202 is also used to perform resource scheduling for CSI based on a scheduling algorithm. 2) The resource scheduling server 106 can also be centrally deployed, so that the management servers of each network resource interact with this centrally deployed resource scheduling server.

[0247] like Figure 4 The diagram shown is a flowchart of a network resource management method provided in an embodiment of this application. This method is based on... Figure 1 and / or Figure 2 The architecture shown is implemented as follows. In this method, the resource information server 103 queries the availability of existing first network resources to find first network resources that can meet the requirements. Then, the resource scheduling server 106 selects and allocates first network resources from the first network resources that meet the requirements based on a scheduling algorithm. Thus, the first management server 101 obtains the allocated first network resource and further triggers the resource information server 103 to update the availability of the allocated first network resource. Specifically, it includes the following steps:

[0248] S400, the first management server 101 receives the performance requirements for the first network resources.

[0249] The performance requirement for the first network resource is used to request the first management server 101 to allocate the first network resource, specifically for initial allocation or reallocation. The first network resource referred to here specifically refers to one of the following network resources: CSI, NSI, NSSI, or NF.

[0250] Optionally, the performance requirement for the first network resource originates from user 107 (not shown in the figure). Specifically, user 107 submits this performance requirement for the first network resource to the first management server 101 via user equipment. Alternatively, user 107 can also negotiate with the first management server 101 via user equipment to determine the performance requirement for the first network resource. The following briefly describes possible reallocation scenarios:

[0251] If user 107 has previously requested a first network resource from the first management server 101, and the first management server 101 has already allocated a first network resource (hereinafter referred to as the initial first network resource) to user 107, when user needs change, user 107 can send the changed performance requirements for the first network resource to the first management server 101, thereby requesting the first management server 101 to reallocate it. It should be understood that in this case, user 107 can also send the identifier of the initial first network resource to the first management server 101 so that the first management server 101 can determine the initial first network resource.

[0252] Alternatively, the initial first network resource allocated to user 107 by the first management server 101 may have changed: for example, due to a failure, deactivation, or scaling up or down. Therefore, the first management server 101 determines that the first network resource needs to be reallocated to user 107. The first management server 101 obtains the performance requirements for this initial first network resource, specifically from user 107, the resource information server 103, or from its local memory. Then, the first management server 101 performs subsequent allocation steps based on these performance requirements for the initial first network resource.

[0253] Optionally, the performance requirement for the first network resource is the performance requirement of the second network resource to be deployed on the first network resource, and is used to request the allocation of the first network resource for the second network resource to be deployed. The following discussion covers two cases: 1) Initial allocation: creating a mapping between the second network resource to be deployed and the first network resource; 2) Reallocation: updating the mapping between the second network resource to be deployed and the first network resource. It should be understood that when the first network resource is CSI, the second network resource refers to TI; when the first network resource is NSI, the second network resource refers to CSI; when the first network resource is NSSI, the second network resource refers to NSI; and when the first network resource is NF, the second network resource refers to NSSI. In practice, the same type of network resource can be nested, for example, the second network resource NSI can be deployed on the first network resources NSI and NSSI; or network resources can be deployed across levels, for example, the second network resource NSI can be deployed on the first network resources NSSI and NF. This application does not limit this.

[0254] In scenario 1), the second management server 102 determines that a new second network resource needs to be deployed (i.e., a second network resource needs to be created). It should be understood that in this application, this new second network resource is referred to as the second network resource to be deployed, or it can also be referred to as the second network resource to be created. Specifically, after receiving an allocation request for the second network resource to be deployed, the second management server 102 determines that a new second network resource needs to be deployed based on the absence of available second network resources or the inability to share the second network resource. Therefore, the second management server 102 requests the first management server 101 to create a correspondence between the second network resource and the first network resource. In this case, the second management server 102 can also request the resource information server 103 to create the topology nodes of the second network resource, specifically including the following steps:

[0255] S400a, the second management server 102 generates an identifier for the second network resource to be deployed and sends a creation request to the resource information server 103, the creation request carrying the identifier of the second network resource to be deployed.

[0256] The creation request is used to request the resource information server 103 to create a topology node for the second network resource to be deployed. Specifically, the creation request includes an object of the second network resource to be deployed, used to create the topology node. This object is generated by the second management server 102 and includes an identifier for the second network resource to be deployed. It should be understood that the object may also include other information (such as the second network resource's requirement information for the first network resource). If it is not stored in topology form, the creation request can be considered as requesting the resource information server 103 to store information about the second network resource to be deployed. This application uses topology-based storage as an example for illustration, but it is not limited thereto; the remaining steps are similar and will not be repeated.

[0257] Specifically, the second management server 102 sends the creation request to the resource information management server 1033.

[0258] S400b, Resource Information Server 103 creates the topology node for the second network resource to be deployed.

[0259] Specifically, the identifier of the topology node is either the identifier of the second network resource to be deployed, or an identifier that corresponds to the identifier of the second network resource to be deployed. The type is "second network resource". Attributes include information from the object of the second network resource to be deployed (such as the performance requirements of the second network resource for the first network resource); or they may be temporarily empty and will be added after the second network resource is successfully deployed.

[0260] Specifically, in response to the creation request, the resource information management server 1033 creates the topology node of the second network resource to be deployed in the resource information database 1031 according to the creation request.

[0261] S400c, resource information server 103 returns a creation response to the second management server 102.

[0262] If the topology node for the second network resource to be deployed is created successfully, a creation success response is returned. Furthermore, if the identifier of the topology node corresponds to the identifier of the second network resource to be deployed, the creation response also includes the identifier of the topology node, so that the second management server 102 can subsequently maintain and query the topology node.

[0263] If creation fails, a creation failure response is returned, which may also include the reason for the failure.

[0264] It should be understood that S400a-S400c can also be performed during or after S400d, that is, the creation of the topology node for the second network resource to be deployed by the second management server 102 occurs before, during, or after the second management server 102 requests the allocation of the first network resource from the first management server 101. Figure 4 The order shown is merely illustrative and does not limit the order in which these steps are performed.

[0265] S400d, the second management server 102 sends an allocation request to the first management server 101, the allocation request carrying the performance requirements of the second network resource for the first network resource.

[0266] The performance requirements of the second network resource for the first network resource are either derived by the second management server 102 itself (e.g., by converting the performance requirements for the second network resource into performance requirements for the first network resource), or negotiated by the second management server 102 with other devices. These other devices specifically include the first management server 101, and / or MDAS 104, etc.

[0267] The allocation request also carries instructions to create a correspondence between the second network resource and the first network resource, or the allocation request is specifically a request to create the second network resource. Therefore, the first management server 101 determines, based on the allocation request, that it will create a correspondence between the second network resource and the first network resource.

[0268] Optionally, the allocation request also carries an identifier of the second network resource to be deployed, so that the first management server 101 can determine which second network resource the first network resource will be allocated to.

[0269] In scenario 2), when the second network resource has been created and deployed on top of the initial first network resource, certain events may trigger its redeployment, i.e., updating the correspondence between the second and first network resources. It should be understood that in this application, the second network resource is also referred to as the second network resource to be deployed, or it can also be called the second network resource to be redeployed. The possible triggering events are described below:

[0270] a. If the performance requirements of the second network resource to be deployed for the first network resource change, the second management server 102 sends an allocation request to the first management server 101. This allocation request carries the changed performance requirements of the second network resource to be deployed for the first network resource, as well as the identifier of the second network resource. The allocation request may also carry indication information for updating the correspondence between the second and first network resources, or it may specifically be a request to update the second network resource. Therefore, the first management server 101 determines, based on this allocation request, that it will update the correspondence between the second and first network resources.

[0271] b. The initial first network resource itself has changed (see above for details), or other second network resources sharing the initial first network resource have changed, etc. Therefore, the first management server 101 determines that the first network resource needs to be reallocated to the second network resource deployed on the initial first network resource (i.e., the second network resource to be deployed). The first management server 101 then obtains the performance requirements of the second network resource to be deployed for the first network resource, specifically from the second management server 102, the resource information server 103, or from local memory.

[0272] S401, the first management server 101 sends a resource scheduling request to the resource scheduling server 106, which carries the performance requirements for the first network resource.

[0273] The resource scheduling request is used to request the resource scheduling server 106 to select a suitable first network resource as the first network resource for allocation based on the performance requirements.

[0274] It should be understood that if the performance requirement for the first network resource is a performance requirement for a non-shared first network resource (for example, the allocation request in S400d also carries indication information indicating a request for a non-shared first network resource), then S401-S407 are not executed. The first management server 101 creates a new first network resource based on the performance requirement for the first network resource, and this new first network resource is a non-shared first network resource. Correspondingly, if the allocation request in S400d carries indication information indicating a request for a shared first network resource or does not carry indication information indicating a request for a non-shared first network resource, then the first management server 101 executes S401-S407 to determine the allocated first network resource from the existing first network resources.

[0275] S402, the resource scheduling server 106 sends a query request to the resource information server 103, which carries the performance requirements for the first network resource.

[0276] This query request is used to find the first available network resource (referred to as the first matching network resource) that meets the performance requirement.

[0277] Specifically, the resource scheduling server 106 sends the query request to the resource information query server 1032.

[0278] S403, Resource Information Server 103 determines the first network resource that is matched.

[0279] Resource information server 103 determines the first network resource whose available capacity can meet the performance requirement based on the existing first network resource availability. Specifically, "meeting" means that the available capacity is greater than or equal to the performance requirement.

[0280] It should be understood that the existing first network resource in this application refers to the deployed first network resource, specifically the deployed shareable first network resource.

[0281] As an optional approach, the resource information server 103 stores the available capabilities of the deployed, shareable first network resources, but does not store the available capabilities of the non-shared first network resources. The resource information server 103 then determines the matching first network resources based on the existing available capabilities of the first network resources and the performance requirements for those resources.

[0282] As an alternative approach, resource information server 103 stores the available capabilities of deployed shareable first network resources, as well as the available capabilities of deployed non-shared first network resources. If a deployed non-shared first network resource has not yet been allocated to a user or a second network resource, its available capabilities represent its planning information. If a deployed non-shared first network resource has been allocated to a user or a second network resource, it has no available capabilities or its available capabilities are zero. In this case, resource information server 103 can first determine the deployed shareable first network resources (e.g., by determining whether a resource is shareable based on its stored sharing attributes), and then determine the matching first network resource based on its available capabilities.

[0283] Specifically, the resource information query server 1032 searches for the matching first network resource in the information of the first network resource stored in the resource information database 1031 based on the performance requirements for the first network resource.

[0284] It should be understood that multiple first network resources can form a group of first network resources. Therefore, when the available capacity of a group of first network resources can meet the performance requirement, the group of first network resources is also considered a matching group of first network resources. This application does not limit this.

[0285] The availability of existing first network resources is determined and provided by MDAS104, see details below. Figure 5 , Figure 6 The description of the illustrated embodiment will not be repeated here.

[0286] For details regarding available capabilities, please refer to [link / reference]. Figure 2 The NRM Capability Profile mentioned in the illustrated embodiment, as well as the load models derived from various network resources (such as NSI Capability Profile, NSSICapability Profile, etc.), will not be elaborated here.

[0287] If the information of network resources is stored in the form of topology, the resource information server 103 traverses the topology nodes of type first network resource, compares the performance requirements with the values ​​of the corresponding capability attributes in the topology nodes, selects the topology nodes whose capability attribute values ​​can meet the performance requirements, and determines the identifier of the first network resource corresponding to these topology nodes (i.e. the identifier of the matched first network resource).

[0288] It should be understood that the resource information server 103 may store the performance requirements for the first network resource. For example, in S400b, the topology node of the second network resource to be deployed, created by the resource information server 103, contains the performance requirements of the second network resource to be deployed for the first network resource; or the second network resource to be deployed was originally deployed on the initial first network resource, and the topology node of the second network resource to be deployed or the topology node of the initial first network resource stores the performance requirements of the second network resource to be deployed for the first network resource. In this case, the resource information server 103 can obtain the performance requirements for the first network resource on its own, without the resource scheduling server 106 needing to transmit them. Therefore, the query request in S402 and the resource scheduling request in S401 do not need to carry the performance requirements; instead, they can carry the identifier of the second network resource to be deployed. Of course, the query request in S402 and the resource scheduling request in S401 can still carry the performance requirements to improve query efficiency.

[0289] S404, Resource Information Server 103 sends a query response to Resource Scheduling Server 106, the query response carrying the identifier of the first matching network resource.

[0290] Specifically, the query response is a query success response. It should be understood that the query response carries the identifiers of all first network resources in the matched first network resources, or carries the identifiers of some of the first network resources, such as the first network resources with the top N available capabilities, where N is a positive integer, N is a preset value stored in the resource information server 103, or is carried in the query request of S402.

[0291] If, in S403, the resource information server 103 does not find a first network resource with the capability to meet the performance requirement (i.e., no matching first network resource), it returns a query failure response. This response carries a failure reason value to indicate that no first network resource is available. Query failure and query success responses can be distinguished by the message itself, by the indication information carried in the message, or by whether or not the identifier of the matching first network resource is included. The same applies to the resource scheduling and allocation responses below, and will not be elaborated further.

[0292] Specifically, the resource information query server 1032 returns the query response to the resource scheduling server 106.

[0293] S405, Resource scheduling server 106 determines the first network resource to be allocated from the matched first network resources.

[0294] The first network resource allocated here refers to one or more of the first network resources in the matched first network resources.

[0295] Optionally, the resource scheduling server 106 may arbitrarily determine the first network resource to be allocated. Alternatively, if the matched first network resource happens to be one or a group of first network resources, then the matched first network resource may be directly used as the first network resource to be allocated.

[0296] Optionally, the resource scheduling server 106 determines the allocated first network resource from the matched first network resources based on a scheduling algorithm. There are many scheduling algorithms, and this application does not limit them, such as Gang Scheduling, Dominant Resource Fairness (DRF), Bin Packing, or queueing algorithms, etc. When the resource scheduling server 106 is configured with multiple scheduling algorithms, algorithm weights can be further configured to determine the final result (i.e., the allocated first network resource) based on the results of multiple scheduling algorithms and the corresponding weights of each algorithm. The scheduling algorithm takes the available capacity of the matched first network resource as input and outputs the allocated first network resource. Therefore, the query response in S404 further carries the available capacity of the matched first network resource. Specifically, the resource scheduling server 106 determines the allocated first network resource from the matched first network resources based on the scheduling algorithm and the available capacity of the matched first network resource. Of course, the scheduling algorithm can also take other information about the matched first network resource as input, such as load information or planning information, etc. Therefore, the query response in S404 further carries this additional information about the matched first network resource. The allocated first network resource is the optimal first network resource obtained based on the scheduling algorithm, which can optimize the overall network resource scheduling, such as improving network resource utilization.

[0297] S406, the resource scheduling server 106 sends a resource scheduling response to the first management server 101, the resource scheduling response carrying the identifier of the allocated first network resource.

[0298] Specifically, the resource scheduling response is a successful resource scheduling response.

[0299] If, in step S405, the resource scheduling server 106 fails to determine a suitable first network resource for allocation (e.g., the result obtained based on the scheduling algorithm is empty), it returns a resource scheduling failure response carrying a failure reason value to indicate that no first network resource is available. Furthermore, if, in step S404, the resource information server 103 returns a query failure response, step S405 is not executed, and in step S406, the resource scheduling server 106 also returns a resource scheduling failure response.

[0300] It should be understood that the resource scheduling server 106 can be deployed together with the resource information server 103, or in other words, the resource information server 103 can provide the functions of the resource scheduling server 106. As one implementation, the query request in S402 and the query response in S404 are not sent. Then, in S401, the first management server 101 sends a resource scheduling request to the resource information server 103; in S403, after the resource information server 103 determines the matching first network resource, it further executes the action performed by the resource scheduling server 106 in S405, that is, it further determines the allocated first network resource from the matching first network resource; in S406, the resource information server 103 returns a resource scheduling response to the first management server 101. As another implementation, the communication between the resource scheduling server 106 and the resource information server 103 in S402 and S404 is communication between different functional modules within the resource information server 103. For example, the query request and query response are communication messages between the module in the resource information server 103 that provides resource information query functions and the module that provides resource scheduling functions. Specifically, the resource scheduling server 106 can be deployed together with the resource information query server 1032, and the details will not be elaborated further.

[0301] The resource scheduling server 106 can also be deployed together with the first management server 101, or in other words, the first management server 101 can provide the functions of the resource scheduling server 106. In one implementation, the resource scheduling request in S401 and the resource scheduling response in S406 are not sent. Then, in S402, the first management server 101 sends a query request to the resource information server 103; in S403, the resource information server 103 determines the matching first network resource; in S404, the resource information server 103 sends a query response to the first management server 101; and in S405, the first management server 101 determines the allocated first network resource from the matching first network resource. In another implementation, the communication between the first management server 101 and the resource scheduling server 106 in S401 and S406 is communication between different functional modules within the first management server 101. For example, the resource scheduling request and resource scheduling response are communication messages between the module in the first management server 101 that provides the deployment and management functions of the first network resource and the module that provides the resource scheduling function.

[0302] Resource scheduling server 106 can also be deployed together with MDAS 104, or MDAS 104 can provide the functions of resource scheduling server 106. In this embodiment of the application, resource scheduling server 106 can be replaced by MDAS 104.

[0303] The function of the resource scheduling server 106 can be deployed in MDAS 104 and the first management server 101. In one implementation, in S401, the first management server 101 sends a performance requirement for a first network resource to MDAS 104. MDAS 104 obtains a matching first network resource based on this performance requirement. For example, MDAS 104 executes the action performed by the resource scheduling server 106 in S402: In S402, MDAS 104 sends a query request to the resource information server 103, carrying the performance requirement for the first network resource; in S404, the resource information server 103 sends a query response to MDAS 104, carrying the identifier of the matching first network resource. Alternatively, S402 may not be executed; MDAS 104 executes the action performed by the resource information server 103 in S403, specifically, MDAS 104 executes the action performed by the resource information query server 1032 in S403. Then, MDAS 104 or the first management server 101 determines the allocated first network resource from the matching first network resources. For example, MDAS104 returns the identifier and other information of the matched first network resource to the first management server 101; the first management server 101 executes the action performed by the resource scheduling server 106 in S405: in S405, the first management server 101 determines the allocated first network resource; S406 is not executed. Another example is that MDAS104 executes the actions performed by the resource scheduling server 106 in S405 and S406: in S405, MDAS104 determines the allocated first network resource; in S406, MDAS104 returns the identifier and other information of the allocated first network resource to the first management server 101. S407, the first management server 101 configures the allocated first network resource.

[0304] The first management server 101 receives a resource scheduling response, thereby determining whether to use the allocated first network resource. This allocated first network resource is the one ultimately assigned to meet the aforementioned performance requirements. Specifically, the first management server 101 determines to allocate the allocated first network resource carried in the resource scheduling response to user 107 or the second network resource to be deployed. Specifically, the first management server 101 modifies the configuration of the allocated first network resource so that it can be used by user 107 or the second network resource to be deployed.

[0305] If, in S400, the performance requirement for the first network resource originates from user 107, the first management server 101 also returns a successful allocation response (not shown in the figure) to user 107 via the user equipment. This response carries the identifier of the allocated first network resource. In the case of a reallocation, the response may also carry the identifier of the initial first network resource previously (before this allocation) allocated to user 107, so that user 107 is more aware of the reallocation of the first network resource. Additionally, the first management server 101 modifies the configuration of the initial first network resource so that it is no longer used by user 107. Of course, the above describes a successful allocation (e.g., a successful resource scheduling response returned in S406). If the allocation fails, such as a resource scheduling failure response returned in S406, the first management server 101 either creates a new first network resource or returns an allocation failure message to user 107, thus determining whether to create a new first network resource based on user 107's choice.

[0306] If, in S400, the performance requirement for the first network resource is the same as the performance requirement of the second network resource to be deployed for the first network resource, then the first management server 101 notifies the second management server 102 of the identifier of the allocated first network resource assigned to the second network resource to be deployed. As shown in S408, the first management server 101 returns an allocation response to the second management server 102, which carries the identifier of the allocated first network resource. Specifically, this allocation response is a successful allocation response. The successful allocation response may also carry the identifier of the second network resource to be deployed, in order to indicate the correspondence between the second network resource to be deployed and the allocated first network resource, thereby facilitating the second management server 102 in establishing the correspondence between the second network resource to be deployed and the allocated first network resource. It should be understood that at this time, the second network resource to be deployed has already been deployed on the allocated first network resource; it is still referred to as the second network resource to be deployed for consistency with the preceding text. Here, "to be deployed" is used to distinguish the second network resource and does not limit its deployment status.

[0307] In the case of a reallocation, the allocation response may also carry the identifier of the initial first network resource originally deployed for the second network resource to be deployed, so that the second management server 102 can delete the correspondence between the second network resource to be deployed and the initial first network resource. Additionally, the first management server 101 modifies the configuration of the initial first network resource so that it is no longer used by the second network resource to be deployed.

[0308] Of course, the above describes a successful allocation. If the allocation fails, a failure response is returned to the second management server 102. Alternatively, the first management server 101 may create a new first network resource for the second network resource to be deployed, and notify the second management server 102 upon successful creation. If no new first network resource is created after the allocation failure, or if creating a new first network resource also fails, the second management server 102 may send a deletion request to the resource information server 103. This deletion request carries the identifier of the second network resource to be deployed or the identifier of the topology node of the second network resource to be deployed, so that the resource information server 103 deletes the topology node of the second network resource to be deployed.

[0309] It should be understood that the execution order of S400b-S400c is optional. For example, after S408, that is, after the second management server 102 determines that the second network resource to be deployed has been successfully created, the topology node of the second network resource to be deployed will be created.

[0310] Optionally, the first management server 101 and / or the second management server 102 establish a correspondence between the second network resource to be deployed and the allocated first network resource to facilitate subsequent resource management.

[0311] Following this allocation, the resource information of the first network resource changed, such as available capabilities and mapping relationships. Furthermore, the first management server 101 triggered the resource information server 103 to update the network resource topology, for example, updating the available capabilities of the allocated first network resource and / or establishing the mapping relationship between the allocated first network resource and the second network resource to be deployed. Specifically:

[0312] S409, the first management server 101 sends an update request to the resource information server 103, the update request carrying the identifier of the allocated first network resource.

[0313] Specifically, the update request instructs the updating of the resource information of the allocated first network resource, such as load information, available capacity, correspondence, etc. The resource information server 103 determines that the resource information of the allocated first network resource has changed based on the update request, and then updates the resource information of the allocated first network resource.

[0314] If the allocated first network resource is assigned to user 107, the update request further carries the identifier of user 107, thereby enabling resource information server 103 to establish a correspondence between user 107 and the allocated first network resource (e.g., storing the correspondence in the topology node of the allocated first network resource, or establishing a topology edge between user 107 and the allocated first network resource). In the case of reallocation, the update request may also carry the identifier of the initial first network resource for user 107, thereby triggering resource information server 103 to update the availability of the initial first network resource. Furthermore, since resource information server 103 may store the correspondence between user 107 and the initial first network resource, even if the update request does not carry the identifier of the initial first network resource, resource information server 103 can still determine the initial first network resource and update its availability. Further, resource information server 103 may also delete the correspondence between user 107 and the initial first network resource.

[0315] If the allocated first network resource is allocated to the second network resource to be deployed, the update request further carries the identifier of the second network resource to be deployed, thereby enabling the resource information server 103 to establish a correspondence between the second network resource to be deployed and the allocated first network resource (e.g., storing the correspondence in the topology nodes of the allocated first network resource, or establishing a topology edge between the second network resource to be deployed and the allocated first network resource). In the case of reallocation, the update request may also carry the identifier of the initial first network resource of the second network resource to be deployed, thereby triggering the resource information server 103 to update the available capabilities of the initial first network resource. Since the resource information server 103 may store the correspondence between the second network resource to be deployed and the initial first network resource, even if the update request does not carry the identifier of the initial first network resource, the resource information server 103 can still determine the initial first network resource of the second network resource to be deployed, thereby updating its available capabilities. Furthermore, the resource information server 103 also deletes the correspondence between the second network resource to be deployed and the initial first network resource.

[0316] This update request also triggers resource information server 103 to update the availability of the allocated first network resource. Specific steps for updating resource information server 103 can be found in [link to documentation]. Figure 6 The description of the illustrated embodiment will not be repeated here.

[0317] It should be understood that after receiving the update message, the resource information server 103 has no restrictions on the order in which it updates the available capabilities (topology attributes) and establishes the corresponding relationships (topology edges).

[0318] Specifically, the first management server 101 sends the update message to the resource information management server 1033, and the resource information management server 1033 updates the resource topology stored in the resource information database 1031. The specific details will not be repeated here.

[0319] S410, Resource Information Server 103 updates network resource topology.

[0320] For details, please refer to S409, which will not be repeated here.

[0321] S411, Resource Information Server 103 returns an update response to First Management Server 101.

[0322] It should be noted that the order of steps in the embodiments of this application is exemplary and not limited. For example, S408 can be executed before, during, or after S407, and the same applies to S409-S411. Furthermore, the message names in the embodiments of this application are exemplary and not limited. For example, the allocation request in S400d can also be called a creation request; the resource scheduling request in S401 can also be called an allocation request, or a resource mapping request, etc.; the query request in S402 can also be called an available capability matching request, an available capability query request, or a KPI query request, etc.; the update request in S409 can also be called a topology update request, a resource mapping update request, or an available capability update request, etc. The response messages are similar and will not be described in detail here.

[0323] It should be understood that the resource information database 1031 at the first network resource level (used to store resource information of the first network resource) can be deployed together with the first management server 101, or in other words, the first management server 101 is used to store resource information of the first network resource. Correspondingly, the resource information database 1031 at the second network resource level (used to store resource information of the second network resource) can be deployed together with the second management server 102. Therefore, in S400b, the resource information management server 1033 generates the topology node of the second network resource to be deployed in the second management server 102 according to the creation request. In S403, the resource information query server 1032 searches for the matching first network resource in the information of the first network resource stored in the first management server 101. In S409 and S410, the resource information management server 1033 updates the resource topology stored in the first management server 101; the specific details are as described above and will not be repeated here.

[0324] The resource information server 103 at the first network resource level (used for storing, managing, and querying resource information of the first network resources) can be deployed together with the first management server 101. Correspondingly, the resource information server 103 at the second network resource level (used for storing, managing, and querying resource information of the second network resources) can be deployed together with the second management server 102. 1) As one implementation, the creation request in S400a may not be sent, S400b may be executed by the second management server 102, and S400c may not be executed. The update request in S409 and the update response in S411 may not be sent. The resource information server 103 in S402, S403, S404, S409, and S410 is replaced by the first management server 101, as detailed above. 2) As another implementation, the communication between the first management server 101 and the resource information server 103 in S409 and S411 is the communication between different functional modules within the first management server 101. For example, the update request and update response are communication messages between the module in the first management server 101 that provides resource information management functions and the module that provides first network resource management functions. 3) As another implementation, the creation request in S400a may not be sent, S400b may be executed by the second management server 102, and S400c may not be executed. Before S401 is executed, the first management server 101 executes the step in S403 of determining the matching first network resource based on the available capacity of the existing first network resource, and then sends a resource scheduling request to the resource scheduling server 106. This resource scheduling request carries resource information such as the identifier and available capacity of the matching first network resource. Then S402 and S404 are not executed, and the resource scheduling request can be found in the description of the query response in S404. The query response in S405 is replaced by this resource scheduling request. Furthermore, the update request in S409 and the update response in S411 do not need to be sent, and the resource information server 103 in S409 and S410 is replaced by the first management server 101. For details, please refer to the above text and will not be repeated here.

[0325] The resource information server 103, the first management server 101, and the resource scheduling server 106 at the first network resource level can be deployed together. Correspondingly, the resource information server 103 at the second network resource level can be deployed together with the second management server 102. 1) As one implementation, the creation request in S400a may not be sent, S400b may be executed by the second management server 102, and S400c may not be executed. The messages in S401, S402, S404, S406, S409, and S411 may not be sent, and the resource scheduling server 106 and the resource information server 103 in the above embodiments can be replaced by the first management server 101. For details, please refer to the above text and will not be repeated here. 2) As another implementation, the communication between the first management server 101, the resource scheduling server 106, and the resource information server 103 in the above embodiments is the communication between different functional modules within the first management server 101.

[0326] Figure 4 In the corresponding network resource management method, the first network resource that can be allocated is obtained by matching performance requirements with available capabilities. After allocation, the available capabilities of the allocated first network resource are updated in a timely manner. This enables accurate and efficient allocation of the first network resource based on available capabilities when the first network resource can be shared, which helps to improve the feasibility and efficiency of network resource management.

[0327] like Figure 5 The diagram shown is a flowchart of a method for managing the availability of network resources according to an embodiment of this application. This method is based on... Figure 1 and / or Figure 2 The illustrated architecture is described. This method flow explains how the availability capabilities of the resource information server 103 are periodically updated and maintained. Periodic updates to the availability capabilities of network resources help improve the effectiveness of network resource availability. The method flow specifically includes the following steps:

[0328] S501 and NWDAS105 send a load update request to the resource information server 103, which carries the load information of the existing first network resources.

[0329] NWDAS105 periodically calculates the load information of the existing first network resources and updates it to the resource information server 103. For details of the load information, please refer to [link to relevant documentation]. Figure 2 The NRM Perfload Profile mentioned in the illustrated embodiment, as well as the load models derived from various network resources (such as NSIPerfload Profile, NSIPerfload Profile, etc.), will not be elaborated here.

[0330] Specifically, NWDAS105 sends the load information of all existing first network resources to resource information server 103, or sends the load information of some existing first network resources (such as the load information of existing first network resources that have changed compared with the previous calculation result). That is, the load update request can carry all or part of the load information of existing first network resources.

[0331] Specifically, NWDAS105 sends the load update request to the resource information management server 1033.

[0332] S502, Resource Information Server 103 updates the load information of the existing first network resources.

[0333] Specifically, after receiving the load update request, the resource information server 103 updates the load information of the existing first network resources stored in the resource information database 1031 based on the load information of the existing first network resources carried in the load update request.

[0334] Alternatively, the resource information server 103 can periodically and proactively request load information of existing first network resources from the NWDAS 105. The resource information server 103 periodically sends a load information request to the NWDAS 105, which carries the identifier of the existing first network resources (this could be all or part of the identifier of the existing first network resources). After receiving the load information request, the NWDAS 105 determines the load information of the corresponding existing first network resource based on the identifier of the existing first network resource carried in the request, and returns the load information of the existing first network resource to the resource information server 103 through a load information response. The resource information server 103 then updates the load information of the existing first network resources. For details, please refer to the above; further explanation is unnecessary.

[0335] S503, Resource Information Server 103 returns a load update response to NWDAS105.

[0336] It should be understood that if the resource information database 1031 does not store the load information of network resources, then steps S501-S503 will not be executed, and the steps such as the resource information server 103 periodically and actively requesting the load information of the existing first network resources from the NWDAS 105 will also not be executed.

[0337] S504 and MDAS104 send query requests to resource information server 103.

[0338] MDAS104 periodically sends the query request to the resource information server 103 to obtain resource information of the existing first network resources.

[0339] Optionally, the query request carries an identifier of the existing first network resource to be queried to indicate which existing first network resources to query. Alternatively, if the query request does not carry an identifier, it indicates that all existing first network resources stored by the resource information server 103 should be queried.

[0340] Optionally, the query request may also carry attribute parameters of the resource information to be queried to indicate which resource information to query. Alternatively, if the query request does not carry attribute parameters, it may indicate that all resource information of the existing first network resources stored by the resource information server 103 is to be queried (i.e., all attribute information of the topology nodes of the existing first network resources, and / or all topology edge information of the existing first network resources). The resource information of the existing first network resources includes one or more of the following: planning information of the existing first network resources, load information of the existing first network resources, demand information for the existing first network resources (including performance requirements of the second network resources deployed on the existing first network resources, and / or performance requirements of users sharing the existing first network resources), the availability of the existing first network resources as determined last time, alarm information of the existing first network resources, and the correspondence between the existing first network resources and other network resources.

[0341] The correspondence between existing first network resources and other network resources includes one or more of the following: the correspondence between an existing first network resource and a first network resource that has deployed the same second network resource as that existing first network resource; the correspondence between an existing first network resource and a second network resource deployed on that existing first network resource (also known as a superior network resource of the existing first network resource); the correspondence between an existing first network resource and a user sharing that existing first network resource; the correspondence between an existing first network resource and a third network resource deployed on that existing first network resource (also known as a subordinate network resource of the existing first network resource), etc. It should be understood that the query request may carry the identifier of the existing first network resource to be queried and attribute parameters of the resource information to be queried, indicating which resource information of which existing first network resources to query. The specific content is the same as above and will not be repeated here.

[0342] Optionally, the query request may also carry a query depth to indicate how many levels of network resources correspond to the existing first network resource. For example, when the query depth is 1, it indicates querying the resource information of the parent network resources, the existing first network resource, and the child network resources of the existing first network resource. When the query depth is 0, it indicates querying the resource information of the existing first network resource. Alternatively, if the query request does not carry a query depth, it defaults to querying the resource information of the existing first network resource. Furthermore, the query request may also carry the direction of the query depth to indicate querying the parent network resources and / or child network resources of the existing first network resource.

[0343] Specifically, MDAS104 sends the query request to resource information query server 1032.

[0344] S505, Resource Information Server 103 sends a query response to MDAS 104, which carries resource information of the existing first network resources.

[0345] Resource information server 103 returns the corresponding resource information to MDAS 104 based on the query request.

[0346] Specifically, the resource information query server 1032 queries the corresponding resource information in the resource information database 1031 according to the query request and sends it to the MDAS 104.

[0347] S506 and MDAS104 determine the availability of existing first network resources.

[0348] MDAS104 determines the availability of existing first network resources based on the resource information of existing first network resources.

[0349] Specifically, the availability of existing first network resources is determined based on the resource information of existing first network resources. See S504 for details. It should be understood that if some information is not stored in the resource information server 103, MDAS 104 can obtain the necessary information from other devices. For example, if the load information of existing first network resources is not stored in the resource information server 103, MDAS 104 will also obtain the load information of existing first network resources from NWDAS 105; or if the alarm information of existing first network resources is not stored in the resource information server 103, MDAS 104 will also obtain the alarm information of existing first network resources from the alarm information database, and so on.

[0350] There are various methods for determining the available capacity of existing first network resources, and this application is not limited to any one of them. One possible method is described below: MDAS104 subtracts the values ​​of the corresponding attributes in the performance requirements of the existing first network resources from the values ​​of each attribute in the planning information of the existing first network resources to obtain the difference. Then, it adjusts this difference based on the alarm information and load information of the existing first network resources. For example, in some cases, the values ​​of attributes in the performance requirements are much greater than the values ​​of the corresponding attributes in the actual runtime load information. In this case, some resources can be released as available capacity. However, if an alarm is generated due to equipment failure or other reasons, the above difference cannot be used as available capacity. Adjusting the difference based on alarm information and load information is beneficial, as the adjusted available capacity is closer to the true available capacity of the existing first network resources, which is conducive to effective resource allocation and the normal operation of the allocated resources. Of course, MDAS104 may also choose not to refer to alarm information and / or load information. It should be understood that the subtraction operation mentioned above is an exemplary operation. In actual execution of the calculation between the planning information and the performance requirements of the existing first network resources, the calculation method can also be selected based on specific attributes.

[0351] As another possible approach: MDAS104 subtracts the values ​​of the corresponding attributes in the load information of the existing first network resource from the values ​​of each attribute in the planning information of the existing first network resource to obtain the difference, and then adjusts the difference based on the alarm information of the existing first network resource and the performance requirements of the existing first network resource. Similarly, MDAS104 may also disregard alarm information and / or performance requirements.

[0352] MDAS104 can also determine the availability of existing first network resources based on resource information of network resources that correspond to existing first network resources. For example, resource information of the superior network resources and / or subordinate network resources of existing first network resources.

[0353] As one possible method: MDAS104 determines the available capabilities of the existing first network resource based on the resource information of the lower-level network resources (third network resources) of the existing first network resource, for example, by adding the available capabilities of multiple third network resources of the existing first network resource, which is not limited in this application.

[0354] It should be understood that for details regarding available capabilities, please refer to [link / reference]. Figure 2 The NRM Capability Profile mentioned in the illustrated embodiment, as well as the capability models derived from various network resources (such as NSI Capability Profile, NSSICapability Profile, etc.), will not be elaborated here.

[0355] S507 and MDAS104 send a capability update request to the resource information server 103, which carries the available capabilities of the existing first network resources.

[0356] Specifically, MDAS104 sends the availability of all existing first network resources determined in S506 to the resource information server 103, or sends the availability of some of the existing first network resources (such as the availability of existing first network resources that have changed compared with the previous determination).

[0357] Specifically, MDAS104 sends the capability update request to the resource information management server 1033.

[0358] S508, Resource Information Server 103 updates the availability of existing first network resources.

[0359] Specifically, the resource information management server 1033 updates the availability of existing first network resources stored in the resource information database 1031.

[0360] S509, Resource Information Server 103 returns a capability update response to MDAS 104.

[0361] It should be understood that when the availability of the existing first network resource is determined based on its load information, executing S502 before S505 ensures that the updated load information is used when determining the availability of the existing first network resource, thereby guaranteeing a more accurate determination of availability. Of course, for certain situations (such as when the availability of the existing first network resource does not need to be determined based on load information, or when the update cycle of the load information is shorter than the update cycle of the availability), the order of execution of each step is not limited. Furthermore, after executing S502, the resource information server 103 can send a load change notification (e.g., broadcast or unicast to MDAS 104), thereby triggering the execution of S504-S509. In this case, the update of availability can also be considered event-triggered, and this application does not impose any limitations on this.

[0362] Alternatively, the resource information server 103 may periodically and proactively request the availability of existing first network resources from the MDAS 104. The resource information server 103 periodically sends an availability request to the MDAS 104, which carries the identifier of the existing first network resource and / or its resource information. The MDAS 104 determines the availability of the existing first network resource and returns the availability of the existing first network resource to the resource information server 103 via an availability response. The resource information server 103 then updates the availability of the existing first network resource. Specific details (such as what the resource information of the existing first network resource includes and how the availability of the existing first network resource is determined) are described above and will not be repeated here.

[0363] It should be noted that the message names in the embodiments of this application are exemplary and not limited. For example, the load update request in S501 can also be called a topology update request, etc.; the query request in S504 can also be called a topology query request, etc.; the capability update request in S507 can also be called a topology update request, or an available capability update request, etc. The response messages are similar and will not be described in detail.

[0364] It should be understood that the resource information database 1031 at the first network resource level (used to store resource information of the first network resources) can be deployed together with the first management server 101. In this case, Figure 5 In the illustrated embodiment, the resource information database 1031 can be replaced with the first management server 101; specific details will not be elaborated further. As an optional approach, the resource information server 103 at the first network resource level (used for storing, managing, and querying resource information of the first network resources) can be deployed jointly with the first management server 101. Figure 5 In the embodiment shown, the resource information server 103 is replaced by the first management server 101, and the specific details will not be repeated.

[0365] like Figure 6 The diagram shown is a flowchart of another method for managing the availability of network resources provided in an embodiment of this application. This method is based on... Figure 1 and / or Figure 2 The architecture implementation is shown. The method flow illustrates how the available capabilities in resource information server 103 are updated and maintained upon event triggering.

[0366] Event-triggered updates are also crucial for maintaining the availability of network resources, ensuring timely updates. Various events can trigger updates, such as changes to the network resource itself (failure, deactivation, scaling up or down, etc.) or changes to the mapping relationships of network resources (initial allocation or reallocation). When an update-triggered event occurs, the resource information of some network resources in the resource information server 103 changes accordingly. For example, if a first network resource is expanded, the first management server 101 updates the expanded planning information of the first network resource to the resource information server 103; if a first network resource is allocated to a second resource network, the first management server 101 updates the mapping relationship between the first and second resource networks to the resource information server 103. Subsequently, the resource information server 103 sends a resource change notification, triggering the MDAS 104 to re-determine the availability of these network resources whose resource information has changed. The following is an example... Figure 4 The illustrated embodiment uses the allocation of the first network resource as an example to introduce how the event triggers the update of available capabilities. The specific steps of this method include:

[0367] S600, the first management server 101 sends an update request to the resource information server 103, the update request carrying the identifier of the allocated first network resource.

[0368] If the allocated first network resource is assigned to user 107, the update request also carries the identifier of user 107, thereby establishing a correspondence between user 107 and the allocated first network resource. If the allocated first network resource is assigned to a second network resource to be deployed, the update request also carries the identifier of the second network resource to be deployed, and the resource information server 103 establishes a correspondence between the second network resource to be deployed and the allocated first network resource. See S409 for details, which will not be repeated here.

[0369] Resource information server 103 also returns an update response (not shown in the figure) to first management server 101. It should be understood that the update response may be returned after resource information server 103 receives the update request, or after the above-mentioned correspondence is established, or after S610.

[0370] The correspondence of the first network resource allocated has changed, and the availability of the first network resource allocated will also change. Therefore, the update request is also used to trigger the resource information server 103 to update the remaining availability of the first network resource allocated after this allocation.

[0371] It should be understood that if user 107 or the second network resource to be deployed originally corresponded to the initial first network resource, then resource information server 103 must also delete the correspondence between user 107 and the initial first network resource, or between the second network resource to be deployed and the initial first network resource. Furthermore, resource information server 103 also updates the available capabilities of the initial first network resource after this allocation. The method for updating the available capabilities of the initial first network resource is similar to the method for updating the available capabilities of the allocated first network resource, and will not be described in detail in this embodiment.

[0372] S601, Resource Information Server 103 broadcasts resource change notification.

[0373] The resource change notification carries an identifier for the allocated first network resource to indicate that the resource information of the allocated first network resource has changed. Optionally, the resource change notification also carries indication information indicating which resource information of the allocated first network resource has changed, such as indication information indicating that a mapping relationship has been established between the allocated first network resource and user 107, or indication information indicating that a mapping relationship has been established between the allocated first network resource and a second network resource to be deployed, etc. Further, the resource change notification is also used to indicate which resource information of the allocated first network resource needs to be re-determined, such as indicating that the load information and / or availability of the allocated first network resource needs to be re-determined. NWDAS 105 and MDAS 104 receive the resource change notification.

[0374] It should be understood that the resource information server 103 can also send resource change notifications to NWDAS 105 and MDAS 104 respectively via unicast. Alternatively, the resource change notification sent to NWDAS 105 may also instruct NWDAS 105 to re-determine the load information of the allocated first network resource; the resource change notification sent to MDAS 104 may also instruct MDAS 104 to re-determine the availability of the allocated first network resource.

[0375] Specifically, the resource information management server 1033 sends the resource change notification.

[0376] S602 and NWDAS105 send a load update request to the resource information server 103. The load update request carries the load information of the first network resource after this allocation.

[0377] NWDAS105 receives the resource change notification. This notification indicates a change in the resource information of the allocated first network resource and / or instructs NWDAS105 to re-determine the load information of the allocated first network resource. Thus, NWDAS105 determines the load information of the allocated first network resource after this allocation. It should be understood that the load information of the allocated first network resource after this allocation specifically refers to the load information after the allocated first network resource is used by user 107 or the second network resource to be deployed. Taking the second network resource to be deployed as an example, if the allocated first network resource is used by the second network resource to be deployed after this allocation, i.e., the second network resource to be deployed is deployed on the allocated first network resource, and thus the load information of the allocated first network resource changes due to the deployment of the second network resource to be deployed, then in this case, the load information of the allocated first network resource after this allocation specifically refers to the load information of the allocated first network resource after the second network resource to be deployed is deployed on the allocated first network resource. In this application, the interpretation of "after this allocation" is similar and will not be repeated here.

[0378] S603, Resource Information Server 103 updates the load information of the first network resource allocated.

[0379] Specifically, the resource information management server 1033 updates the load information of the first network resource allocated in the resource information database 1031 to the load information of the first network resource after this allocation.

[0380] S604, Resource Information Server 103 returns a load update response to NWDAS 105.

[0381] Alternatively, after S600, the resource information server 103 may proactively request the load information of the allocated first network resource from the NWDAS 105 after this allocation. The resource information server 103 sends a load information request to the NWDAS 105, which carries the identifier of the allocated first network resource. The NWDAS 105 determines the load information of the allocated first network resource after this allocation and returns the load information to the resource information server 103 via a load information response. The resource information server 103 then updates the load information of the allocated first network resource after this allocation.

[0382] It should be understood that if the resource information database 1031 does not store the load information of network resources, then steps S601a and S602-S604 may not be executed, and the steps such as the resource information server 103 actively requesting the load information of the first allocated network resource after this allocation from the NWDAS 105 may also not be executed.

[0383] S605 and MDAS104 send query requests to resource information server 103.

[0384] MDAS104 receives the resource change notification from S601b. This notification indicates a change in the resource information of the allocated first network resource, and / or instructs MDAS104 to re-determine the availability of the allocated first network resource. Therefore, MDAS104 will determine the remaining availability of the allocated first network resource after this allocation.

[0385] Before determining the remaining available capacity, MDAS104 sends the query request to resource information server 103 to obtain resource information for the allocated first network resource. See details below. Figure 5 In the illustrated embodiment, S504 simply involves replacing the existing first network resource with the allocated first network resource, which will not be described in detail here.

[0386] S606, Resource Information Server 103 sends a query response to MDAS 104, the query response carrying the resource information of the allocated first network resource.

[0387] For details, please refer to [link / details]. Figure 5 In the illustrated embodiment, S505 simply involves replacing the existing first network resource with the allocated first network resource, which will not be described in detail here.

[0388] Specifically, the resource information of the allocated first network resource refers to the updated resource information after this allocation. For example, the performance requirements for the allocated first network resource include the performance requirements related to this allocation (i.e., the performance requirements for the first network resource in S400). The load information of the allocated first network resource is the load information of the allocated first network resource after this allocation. The correspondence between the allocated first network resource and the second network resource deployed on the allocated first network resource includes the correspondence between the allocated first network resource and the second network resource to be deployed in this allocation (i.e., the correspondence between the second network resource to be deployed and the allocated first network resource established in S600 or S410). The correspondence between the allocated first network resource and the user sharing the allocated first network resource includes the correspondence between the allocated first network resource and user 107 in this allocation (i.e., the correspondence between user 107 and the allocated first network resource established in S600 or S410). Although the availability of the first network resource allocated has changed, the resource information server 103 has not yet received the updated results. Therefore, the availability of the first network resource allocated is still the availability determined before this allocation.

[0389] It should be understood that if, in S601, the resource information server 103 sends a resource change notification via broadcast, the execution order of S602 and S605 is uncertain; S602 may execute before, after, or simultaneously with S605. When the remaining available capacity is determined based on load information, S606 executes after S603. The same applies if, in S601, the resource information server 103 sends resource change notifications separately via unicast. Alternatively, the resource information server 103 may first send a resource change notification to NWDAS 105, and then, after S603, send a resource change notification to MDAS 104.

[0390] S607 and MDAS104 determine the remaining available capacity of the first network resource allocated after this allocation.

[0391] Similar content can be found in S506; simply replace the existing first network resource with the allocated first network resource, which will not be elaborated further. Furthermore, the resource information of this allocated first network resource is specifically the resource information updated after this allocation; see S606 for details.

[0392] S608 and MDAS104 send a capability update request to the resource information server 103. The capability update request carries the remaining available capability of the allocated first network resource after this allocation. The capability update request also carries the identifier of the allocated first network resource.

[0393] Specifically, MDAS104 sends the capability update request to the resource information management server 1033.

[0394] S609, Resource Information Server 103 updates the remaining available capacity of the first network resource allocated after this allocation.

[0395] Specifically, the resource information management server 1033 updates the available capacity of the first network resource allocated (determined before this allocation) previously stored in the resource information database 1031 to the remaining available capacity after this allocation.

[0396] S610, Resource Information Server 103 returns a capability update response to NWDAS 105.

[0397] Alternatively, after S600, the resource information server 103 may proactively request the MDAS 104 to determine the remaining available capacity of the allocated first network resource after this allocation. The resource information server 103 sends an availability request to the MDAS 104, carrying the identifier of the allocated first network resource and / or its resource information, to instruct the MDAS 104 to re-determine the available capacity of the allocated first network resource. The MDAS 104 determines the remaining available capacity of the allocated first network resource after this allocation and returns the remaining available capacity of the allocated first network resource to the resource information server 103 via an availability response. The resource information server 103 then updates the remaining available capacity of the allocated first network resource. Details are as described above and will not be repeated here.

[0398] As an optional approach, when the resource information of a network resource changes, the management device of that network resource can also send a resource change notification to trigger MDAS104 to re-determine the availability of the network resources whose resource information has changed. For example, in the above embodiment, S600 and S601 are no longer executed; instead, the first management server 101 broadcasts a resource change notification. The specific content and function of this resource change notification are described in S601. Furthermore, the specific content of S602-610 is also described above and will not be repeated here.

[0399] It should be noted that the message names in the embodiments of this application are exemplary and not limited. See details below. Figure 5 The description of the illustrated embodiments will not be repeated.

[0400] It should be understood that the resource information database 1031 at the first network resource level (used to store resource information of the first network resources) can be deployed together with the first management server 101. In this case, Figure 6 In the illustrated embodiment, the resource information database 1031 can be replaced with the first management server 101; specific details will not be elaborated further. As an optional approach, the resource information server 103 (used for storing, managing, and querying resource information of the first network resources) at the first network resource level can be deployed together with the first management server 101. In this case, the update request in S600 may not be sent, and... Figure 6 In the embodiment shown, the resource information server 103 is replaced by the first management server 101, and the specific details will not be repeated.

[0401] To make the embodiments of this application clearer, as follows: Figure 7As shown, taking NSMS203 as the first management server 101 and NSI as the first network resource, and CSMS202 as the second management server 102 and CSI as the second network resource as an example, the method for network resource management provided in this application is described in detail. The method includes the following steps:

[0402] S700 and CSMS202 receive service requests from communication service user 207 and negotiate SLAs with communication service user 207.

[0403] Communication service user 207 logs into the BSS through user equipment to negotiate the SLA with CSMS 202. The SLA includes performance requirements for the CSI, and may also include user information of communication service user 207, etc.

[0404] In the event that the CSI is not shared or there is no available CSI, CSMS202 determines that a new CSI will be created to provide services to communication service user 207. This new CSI is also referred to as the CSI to be created or the CSI to be deployed. For the sake of brevity, this new CSI will be referred to as the first CSI below.

[0405] CSMS202 creates an object for the first CSI, which includes generating an identifier for the first CSI, namely the first CSI ID. The object for the first CSI includes information related to the first CSI, such as the first CSI ID or SLA.

[0406] Next, CSMS202 requests NSI from NSMS203 to deploy the first CSI, i.e., to create the mapping between CSI and NSI. CSMS202 also requests the resource information server 103 to create the topology node for the first CSI. The creation of the topology node for the first CSI will be described below.

[0407] S701a and CSMS202 send a topology node creation request to the resource information management server 1033, which carries the first CSI ID.

[0408] Specifically, the topology node creates an object that carries a first CSI, and the first CSI object carries a first CSIID.

[0409] S701b, Resource Information Management Server 1033 creates the topology node of the first CSI.

[0410] Specifically, in response to the topology node creation request, the resource information management server 1033 creates the first CSI topology node in the resource information database 1031.

[0411] Specifically, the identifier of the topology node is either the identifier of the first CSI or an identifier that corresponds to the identifier of the first CSI. The type of the topology node is CSI. The attributes of the topology node include information from the object of the first CSI (such as the SLA of the first CSI, the performance requirements of the first CSI for the NSI, etc.).

[0412] As an optional approach, CSMS202 requests the creation of the topology node for the first CSI from the resource information management server 1033 after the first CSI is successfully deployed. That is, S701a-S701c are executed after S710.

[0413] The S701c resource information management server 1033 returns a topology node creation response to the CSMS202.

[0414] It should be understood that when the CSI-level resource information database 1031 is deployed on CSMS202, CSMS202 can automatically create the topology node for the first CSI, while S701a-S701c do not require this. Of course, to improve the efficiency of resource information query and management, CSMS202 can still create the topology node for the first CSI through the resource information management server 1033. Since the resource information management server 1033 can create indexes for network resources at various levels, it facilitates unified querying and maintenance of resource information for network resources at all levels in the future.

[0415] The following section describes how to create the correspondence between CSI and NSI.

[0416] CSMS202 obtains the corresponding Service Profile (including the performance requirements for the NSI) based on the SLA (including the performance requirements for the CSI) of the first CSI. Specifically, CSMS202 automatically converts the SLA of the first CSI into the corresponding Service Profile, or performs the above conversion through other devices (such as MDAS104, NSMS203).

[0417] S702 and CSMS202 send an allocation request to NSMS203, which carries the Service Profile.

[0418] Optionally, the allocation request may also carry a first CSI ID, and / or instruction information indicating the creation of a mapping between CSI and NSI.

[0419] After receiving the allocation request, NSMS203 needs to allocate an NSI for the first CSI. When a separate resource scheduling server 106 is deployed to perform resource scheduling, NSMS203 requests the allocation of an NSI from the resource scheduling server 106. Then, S703 is executed:

[0420] S703 and NSMS203 send a resource scheduling request to the resource scheduling server 106, which carries a Service Profile.

[0421] The resource scheduling request is used to request the resource scheduling server 106 to select a suitable NSI from the existing NSIs to deploy the first CSI. Optionally, the resource scheduling request also carries the first CSI ID, and / or indication information indicating the creation of a mapping relationship between CSIs and NSIs.

[0422] S704, Resource scheduling server 106 sends a query request to resource information query server 1032, the query request carrying Service Profile.

[0423] Optionally, the resource scheduling server 106 determines the KPIs (i.e., identifies key performance requirements) from the Service Profile and queries using these KPIs (i.e., the query request carries the KPIs), which can improve query efficiency. It should be understood that both the Service Profile and the KPIs indicate the performance requirements of the first CSI for the NSI.

[0424] This query request is used to find the NSI (referred to as the matching NSI) whose available capabilities meet the performance requirements of the first CSI for the NSI. For the sake of brevity, the matching NSI will be referred to as the first NSI below.

[0425] S705, Resource Information Query Server 1032 determines the first NSI that the available capabilities meet the requirements in the Service Profile.

[0426] Resource information database 1031 stores the available capabilities of existing NSIs, which are obtained from MDAS. MDAS periodically recalculates the available capabilities of existing NSIs and provides the calculated available capabilities of existing NSIs to resource information database 1031 through resource information query server 1032. Furthermore, when the resource information of any existing NSI changes, MDAS recalculates the available capabilities of the changed NSI and similarly provides the calculated available capabilities of the changed NSI to resource information database 1031 through resource information query server 1032. See details below. Figure 5 , Figure 6 The illustrated embodiment.

[0427] Resource information query server 1032 determines the first NSI based on the available capabilities of existing NSIs. The following example illustrates this. The Service Profile includes the following requirement parameters:

[0428] a. maxNumberofUEs (maximum number of user devices): 1000;

[0429] b. Latency (Minimum Latency): 1ms;

[0430] c. Coverage Area: Cell A.

[0431] The resource information query server 1032 then queries the resource information database 1031 to determine the available capabilities of existing NSIs, thereby identifying the first NSI that meets the aforementioned requirements. Assume the available capabilities of existing NSIs are as follows:

[0432] 1) NSI-1: NSIMaxNumberofUEsCap: 1000; NSILatencyCap: 2ms; CoverageArea: B cell.

[0433] 2) NSI-2: NSIMaxNumberofUEsCap: 1500; NSILatencyCap: 0.8ms; CoverageArea: Cell A + Cell B.

[0434] 3) NSI-3: NSIMaxNumberofUEsCap: 500; NSILatencyCap: 0.5ms; CoverageArea: Cell A.

[0435] 4) NSI-4: NSIMaxNumberofUEsCap: 3000; NSILatencyCap: 0.5ms; CoverageArea: Cell A.

[0436] 5) NSI-5: NSIMaxNumberofUEsCap: 2000; NSILatencyCap: 1ms; CoverageArea: Cell A.

[0437] The first NSI determined by the resource information query server 1032 includes: NSI-2, NSI-4 and NSI-5.

[0438] S706, the resource information query server 1032 returns a query success response to the resource scheduling server 106, which carries the first NSI ID.

[0439] A successful query response can also carry the availability of the first NSI.

[0440] If no NSI that meets the requirements is found in S705, a query failure response is returned.

[0441] S707, Resource scheduling server 106 determines the allocated second NSI from the first NSI.

[0442] For ease of description, the assigned NSI will be referred to as the second NSI. The second NSI is one or a group of NSIs in the first NSI.

[0443] Resource scheduling server 106 determines the allocated second NSI from the first NSI based on the scheduling algorithm and the available capabilities of the first NSI. For example, resource information query server 1032 determines the optimal NSI as NSI-4 (the second NSI) from the aforementioned first NSI.

[0444] When the resource scheduling server 106 runs multiple scheduling algorithms, it may obtain multiple results. For example, the optimal NSI determined based on the DRF algorithm is NSI-2, and the optimal NSI determined based on the Bin Packing algorithm is NSI-4. Then, the resource scheduling server 106 further determines the final result based on the algorithm weights, thereby determining the second NSI.

[0445] S708, Resource Scheduling Server 106 returns a resource scheduling success response to NSMS203, which carries a second NSI ID.

[0446] If there is no suitable NSI to serve as the second NSI (e.g., the query failure response is returned in S706 or the scheduling algorithm result is empty in S707), the resource scheduling server 106 returns a resource scheduling failure response.

[0447] The S709 and NSMS203 are configured with this second NSI.

[0448] Upon receiving a successful resource scheduling response, NSMS203 assigns the second NSI to the first CSI. Specifically, NSMS203 modifies the second NSI (e.g., by issuing configuration parameters) to deploy the first CSI on the second NSI.

[0449] If a resource scheduling failure response is received, it means that there is no existing NSI available, and NSMS203 creates a new NSI.

[0450] S710 and NSMS203 send an allocation success response to CSMS202, which carries a second NSI ID.

[0451] The successful allocation response may also carry the first CSI ID. Based on this successful allocation response, CSMS202 determines that the first CSI has been successfully deployed and deployed to the second NSI.

[0452] Furthermore, CSMS202 sends a service allocation success response message to communication service user 207.

[0453] It should be noted that if NSMS203 creates a new NSI in S709, the allocation success response carries the ID of the new NSI. If creating a new NSI fails, NSMS203 returns an allocation failure response message to CSMS202, and CSMS202 sends a service allocation failure response message to communication service user 207 to refuse to provide service to communication service user 207. Furthermore, CSMS202 also sends a deletion request to resource information management server 1033, which carries the first CSI ID, so that resource information management server 1033 deletes the topology node of the first CSI.

[0454] S711 and NSMS203 send an update request to the resource information management server 1033, which carries the first CSI ID and the second NSI ID.

[0455] When the first CSI is deployed on the second NSI, a correspondence is established between the first CSI and the second NSI, and the available capabilities of the second NSI also change. Therefore, NSMS203 sends an update request to the resource information server 103, which is beneficial for the timely updating of the resource topology.

[0456] This update request is used to trigger updates to topology edges, and also to trigger updates to the attribute information (such as available capabilities) of topology nodes.

[0457] S712 and Resource Information Management Server 1033 establish the topological edge of the first CSI ID and the second NSI.

[0458] After receiving the update request, the resource information management server 1033 establishes a correspondence (topological edge) between the first CSI and the second NSI in the resource information database 1031, or stores the correspondence as attribute information (relationship attribute) of the topological nodes of the first CSI and / or the second NSI in the corresponding node.

[0459] The resource information management server also updates the attribute information of topology nodes, such as the load information and available capabilities of the first CSI, and / or the load information and available capabilities of the second NSI, etc. The update methods include: 1. The resource information management server broadcasts a resource change notification, thereby triggering NWDAS105 to determine the load information and request an update, and triggering MDAF 104 to determine the available capabilities and request an update. 2. The resource information management server actively requests load information from NWDAS105 and actively requests available capabilities from MDAF 104. The information updates for the first CSI and the second NSI are similar; the following description uses the information update for the second NSI as an example to illustrate the two possible methods.

[0460] Method 1:

[0461] S713, Resource Information Management Server 1033 broadcasts resource change notifications.

[0462] The resource change notification carries a second NSI ID to indicate that the resource information of the second NSI has changed. Optionally, the resource change also carries indication information to establish a correspondence between the first CSI ID and the second NSI ID.

[0463] NWDAS105 and MDAS104 receive this resource change notification. It should be understood that broadcasting is an optional method, and unicasting is also possible.

[0464] S714 and NWDAS105 send a load update request to the resource information management server 1033. The load update request carries the load information of the second NSI ID after this allocation.

[0465] After receiving the aforementioned resource change notification, NWDAS105 calculates and determines the load information of the second NSI ID after this allocation. This allocation refers to assigning the second NSI to the first CSI, or deploying the first CSI on the second NSI.

[0466] S715, Resource Information Management Server 1033 updates the load information of the second NSI ID.

[0467] Resource information management server 1033 updates the load information of the second NSI ID previously stored in resource information database 1031 to the load information of the second NSI ID after this allocation.

[0468] S716, Resource Information Management Server 1033 returns a load update response to NWDAS105.

[0469] S717 and MDAS104 send a query request to the resource information query server 1032, which carries a second NSI ID.

[0470] MDAS104 receives the resource change notification from S713 and determines that the resource information of the second NSI has changed based on the notification. Therefore, MDAS104 determines the remaining available capacity of the second NSI after this allocation. This remaining available capacity is determined based on the resource information of the second NSI. The resource information database 1031 stores the resource information of the second NSI, and thus MDAS104 sends this query request to request the resource information of the second NSI. It is evident that the resource information database 1031, which stores network resource information, not only facilitates the rapid and efficient determination of available existing NSIs based on their available capacity during resource allocation, but also helps to accurately determine the available capacity of existing NSIs based on various other information (such as planning information, load information, demand information, etc.).

[0471] Optionally, the query request may also carry attribute parameters indicating which resource information of the second NSI to query. The query request may also carry a query depth indicating how many levels of network resources corresponding to the second NSI are being queried. For example, when the query depth is 1, it indicates that resource information of the CSI deployed on the second NSI, the second NSI, and the NSSI on which the second NSI is deployed are being queried. See the descriptions in S504 and S605 for details, which will not be repeated here.

[0472] S718, Resource Information Query Server 1032 returns a query response to MDAS 104, which carries the resource information of the second NSI.

[0473] Resource information query server 1032 queries the corresponding resource information in resource information database 1031 based on the query request and sends it to MDAS 104. For example, the resource information of the second NSI includes one or more of the following: planning information of the second NSI, load information of the second NSI, demand information of the second NSI, the previously determined availability of the second NSI, alarm information of the second NSI, the correspondence between the second NSI and other network resources, etc.

[0474] The resource information of the second NSI carried in the query response is used to determine the remaining available capacity of the second NSI after this allocation. Therefore, if other information in the resource information of the second NSI, besides the available capacity, changes after this allocation, the query response carries the changed resource information, making the determination of the remaining available capacity more accurate. For example, the load information of the second NSI mentioned above specifically includes the load information of the second NSI after this allocation, the demand information of the second NSI including the performance requirements of the first CSI for the second NSI, and the correspondence between the second NSI and other network resources, including the correspondence between the first CSI and the second NSI, etc.

[0475] It should be understood that when the resource information database 1031 is deployed in a distributed manner and the query request carries a query depth of 1, the resource information query server 1032 retrieves the corresponding resource information from each resource information database 1031 according to the index. For example, it retrieves CSI resource information from the CSI-level resource information database 1031 and NSSI resource information from the NSSI-level resource information database 1031.

[0476] S719 and MDAS104 determine the remaining available capacity of the second NSI after this allocation.

[0477] MDAS104 determines the remaining available capacity based on the resource information of the second NSI. The resource information of the second NSI is detailed in S718 and will not be repeated here. It should be understood that if MDAS104 requires other information to determine the remaining available capacity, or if some information in the resource information of the second NSI is not stored in the resource information server 103, MDAS104 can obtain the necessary information from other devices. For example, if the attribute information of the topology node of the second NSI does not include load information, MDAS104 obtains the load information of the second NSI from NWDAS105. It should be understood that in this case, steps 714-716 are not executed.

[0478] The following uses the `maxNumberofUEs` parameter (maximum number of user devices) as an example to illustrate a method for determining the remaining available capacity. First, the resource information of the second NSI is introduced: 1. In the planning information of the second NSI, `maxNumberofUEs` is 5000. 2. In the load information of the second NSI, `maxNumberofUEsLoad` is 2400. 3. The performance requirements of the second NSI: In the performance requirements of the first CSI, `maxNumberofUEsReq` is 1000; in the performance requirements of the second CSI, `maxNumberofUEsReq` is 2500. 4. The alarm information of the second NSI: None. 5. The correspondence of the second NSI: The first CSI and the second CSI are deployed in the second NSI; the second NSI is deployed in the first NSSI, the second NSSI, and the third NSSI.

[0479] MDAS104 first calculates the planning information and load information of the second NSI. For the maximum number of user devices, a subtraction operation is performed to obtain a difference of 2600. Then, adjustments are made based on the demand and alarm information of the second NSI. The maximum number of user devices in the load information is 2400, but the sum of the maximum number of user devices in the performance requirements of the first and second CSIs is 3500. Since the load information changes over time, and the performance requirements of the first and second CSIs are much greater than the current load, the difference of 2600 is adjusted upwards from 3500, for example, to the median value: 3050. Since there is no alarm information, no further adjustments are made. Therefore, MDAS104 obtains a value of maxNumberofUEsCap of 3050 for the remaining available capacity of the second NSI.

[0480] There are multiple methods for determining the remaining available capacity of the second NSI, and this application does not limit them. For details, please refer to [link / reference needed]. Figure 5 The description of S506 in the illustrated embodiment will not be repeated here.

[0481] S720 and MDAS104 will send a capability update request to the resource information management server 1033. This capability update request carries the remaining available capabilities of the second NSI after this allocation.

[0482] S721, Resource Information Management Server 1033 updates the availability of the second NSI.

[0483] Resource information management server 1033 updates the previously determined available capacity of the second NSI stored in resource information database 1031 to the remaining available capacity of the second NSI after this allocation.

[0484] S722, Resource Information Management Server 1033 returns a capability update response to MDAS104.

[0485] It should be understood that the resource information management server 1033 also sends an update response (not shown in the figure) to the NSMS 101. This update response can be sent after receiving the update request in S711, or after establishing the topology edge in S712, or after updating the available capabilities of the second NSI in S721. Furthermore, after S715 and S721, the resource information management server 1033 can further send resource change notifications to indicate changes in the load information of the second NSI and changes in the available capabilities of the second NSI, respectively.

[0486] Method 2:

[0487] S723, Resource Information Management Server 1033 sends a load update request to NWDAS105, which carries a second NSI ID.

[0488] S724 and NWDAS105 return a load update response to the resource information management server 1033, which carries the load information of the second NSI after this allocation.

[0489] After receiving the load update request, the NWDAS105 calculates and determines the load information of the second NSI ID after this allocation.

[0490] S725, Resource Information Management Server 1033 updates the load information of the second NSI ID.

[0491] See S715 for details.

[0492] S726, Resource Information Management Server 1033 sends an Available Capability Update Request to MDAS 104, which carries the resource information of the second NSI.

[0493] In another implementation, the availability update request carries only the second NSI ID. After receiving the availability update request, MDAS104 sends a query request to the resource information query server 1032 to obtain the resource information of the second NSI, as detailed in S717-718, which will not be repeated here.

[0494] S727 and MDAS104 determine the remaining available capacity of the second NSI after this allocation.

[0495] For details, please refer to S719, which will not be repeated here.

[0496] S728 and MDAS104 return an availability update response to the resource information management server 1033, which carries the remaining availability of the second NSI after this allocation.

[0497] S729, Resource Information Management Server 1033 updates the availability of the second NSI.

[0498] For details, please refer to S721, which will not be repeated here.

[0499] Similar to Method 1, in the scenario of Method 2, the resource information management server 1033 also sends an update response to the NSMS 203. This update response can be sent after receiving the update request in S711, after establishing the topology edge in S712, or after updating the availability of the second NSI in S729. The resource information management server 1033 can also broadcast resource change notifications after S712, S725, and S729 to promptly notify other devices of changes in resource information.

[0500] like Figure 8As shown, a resource information server 103 provided in this application embodiment includes a first receiving module 801, a query module 802, a first sending module 803, a second receiving module 804, and an update module 805.

[0501] The first receiving module 801 is used to receive a query request sent by the resource scheduling server 106. This query request carries performance requirements for a first network resource, and is used to query available first network resources whose capabilities meet these performance requirements. Specifically, the first network resource refers to one of CSI, NSI, NSSI, or NF network resources. For details, please refer to the step description of the resource information server 103 (specifically, resource information query server 1032) in the above embodiments, such as steps 402 and 704.

[0502] The query module 802 is used to determine the first network resource whose available capacity meets the performance requirements (hereinafter referred to as the matched first network resource) based on the available capacity of the existing first network resources. For details, please refer to the step description of the resource information server 103 (specifically, resource information query server 1032, resource information database 1031) in the above embodiment, such as steps 403, 705, etc.

[0503] The first sending module 803 is used to return the identifier of the matching first network resource to the resource scheduling server 106. For details, please refer to the step description of the resource information server 103 (specifically, the resource information query server 1032) in the above embodiment, such as steps 404, 705, etc.

[0504] The second receiving module 804 is used to receive an update request. The update request carries an identifier of the allocated first network resource. The allocated first network resource is one or more network resources among the matched first network resources, that is, the allocated first network resource is the first network resource that is finally allocated to meet the above performance requirements. For details, please refer to the step description of the resource information server 103 (specifically, resource information query server 1032) in the above embodiment, such as steps 409, 600, 711, etc.

[0505] The update module 805 is used to update the availability of the allocated first network resource. For details, please refer to the step description of the resource information server 103 (specifically, resource information management server 1033, resource information database 1031) in the above embodiment, such as steps 410, 601-609, 713-729, etc.

[0506] Optionally, the resource information server 103 further includes a first storage module for storing the availability of existing first network resources. Furthermore, the update module 805 is specifically used to update the availability of the allocated first network resources stored in the first storage module.

[0507] In one implementation, the update module 805 includes a first obtaining module and an update submodule. The first obtaining module is used to obtain from the management data analysis server 104 the remaining available capacity of the allocated first network resource after this allocation; the update submodule is used to update the previously stored available capacity of the allocated first network resource to the remaining available capacity. For details, please refer to the step description of the resource information server 103 (specifically, resource information database 1031, resource information query server 1032, and resource information management server 1033) in the above embodiments, such as steps 601, 605-609, 713, 711-721, 726-729, etc. Optionally, the resource information server 103 further includes a second obtaining module, used to obtain the load information of the allocated first network resource after this allocation from the network data analysis server 105; and a second sending module, used to send the load information of the allocated first network resource after this allocation to the management data analysis server 104. The remaining available capacity is determined based on the load information of the allocated first network resource after this allocation. For details, please refer to the step description of the resource information server 103 (specifically, resource information database 1031, resource information management server 1033) in the above embodiments, such as steps 601-607, 713-719, 723-727, etc.

[0508] Optionally, the resource information server 103 further includes a second storage module and a third sending module. The second storage module stores the resource information of the allocated first network resource; the third sending module sends the resource information of the allocated first network resource to the management data analysis server, whereby the remaining available capacity is determined based on the resource information of the allocated first network resource. For details, please refer to the step descriptions of the resource information server 103 (specifically, resource information database 1031, resource information query server 1032, and resource information management server 1033) in the above embodiments, such as steps 605-607, 717-719, 726-727, etc. It should be understood that the second storage module includes the aforementioned first storage module.

[0509] In this embodiment, the resource information server 103 is presented in the form of a functional module. Here, "module" can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory executing one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above-mentioned functions. In a simple embodiment, those skilled in the art will understand that the resource information server 103 can adopt... Figure 9 It is implemented in the form shown.

[0510] like Figure 9 The diagram shown is a schematic representation of a computer device provided in an embodiment of this application. The computer device includes at least one processor 901, a communication bus 902, and a memory 903, and may also include at least one communication interface 904 and an I / O interface 905. The processor may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program according to the present application.

[0511] The communication bus may include a path for transmitting information between the aforementioned components. The communication interface, using any transceiver-like device, is used to communicate with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc.

[0512] The memory can be read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions, random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited thereto. The memory can exist independently and be connected to the processor via a bus. The memory can also be integrated with the processor.

[0513] The memory is used to store program code that executes the solution of this application, and its execution is controlled by a processor. The processor is used to execute the program code stored in the memory.

[0514] In a specific implementation, a processor may include one or more CPUs, each of which may be a single-core processor or a multi-core processor. Here, "processor" can refer to one or more devices, circuits, and / or processing cores used to process data (such as computer program instructions).

[0515] In a specific implementation, as one example, the computer device may also include an input / output (I / O) interface. For example, the output device may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device may be a mouse, keyboard, touch screen device, or sensing device, etc.

[0516] The aforementioned computer device can be a general-purpose computer device or a special-purpose computer device. In specific implementations, the computer device can be a desktop computer, a portable computer, a network server, a PDA (Personal Digital Assistant), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, or something similar. Figure 9 Devices with similar structures. This application does not limit the type of computer device to the embodiments described herein.

[0517] The devices in this application embodiment, such as the first management server 101, the second management server 102, the resource information server 103, the management data analysis server 104, the network data analysis server 105, and the resource scheduling server 106, can all adopt... Figure 9 The diagram shows the structure of a general-purpose computer device.

[0518] For example, when the processor of the first management server 101 executes the executable code or application stored in the memory, the first management server 101 can execute the method steps corresponding to the first management server 101 in all the above embodiments. The specific execution process is described in the above embodiments and will not be repeated here.

[0519] For example, when the processor of the resource scheduling server 106 executes the executable code or application stored in the memory, the resource scheduling server 106 can execute the method steps corresponding to the resource scheduling server 106 in all the above embodiments. The specific execution process is described in the above embodiments and will not be repeated here.

[0520] For example, when the processor in MDAS104 executes the executable code or application stored in the memory, MDAS104 can execute the method steps corresponding to MDAS104 in all the above embodiments. The specific execution process is described in the above embodiments and will not be repeated here.

[0521] For example, regarding resource information server 103, when its processor executes executable code or application programs stored in the memory, resource information server 103 can execute the method steps corresponding to resource information server 103 in all the above embodiments. The specific execution process is described in the above embodiments and will not be repeated here. It should be understood that the memory can also store resource information (such as available capabilities) of the first network resource.

[0522] In another implementation, the resource information server 103 includes a resource information database 1031, a resource information query server 1032, and a resource information management server 1033. The resource information database 1031, resource information query server 1032, and resource information management server 1033 can all be implemented using... Figure 9 The diagram illustrates the structure of a general-purpose computer device. For example, regarding the resource information database 1031, when its processor executes executable code or application programs stored in the memory, the resource information database 1031 can execute the method steps corresponding to the resource information database 1031 in all the above embodiments. The specific execution process is detailed in the above embodiments and will not be repeated here. Furthermore, the memory of the resource information database 1031 also stores resource information (such as available capabilities) of the first network resource.

[0523] This application also provides a computer-readable storage medium for storing the above-described... Figure 9 The computer software instructions used by the device shown (such as resource information server 103) include a program designed to execute the method embodiments described above. The above method can be implemented by executing the stored program.

[0524] like Figure 10 As shown, an MDAS104 provided in an embodiment of this application includes a receiving module 1001, a processing module 1002, and a sending module 1003.

[0525] The receiving module 1001 is used to receive a resource change notification. The resource change notification carries the identifier of the first network resource whose resource information has changed. For details, please refer to step 601 in the above embodiment.

[0526] The processing module 1002 is used to determine the remaining available capacity of the first network resource based on the resource information of the first network resource. For details, please refer to steps 605-607 in the above embodiments.

[0527] The sending module 1003 is used to send the remaining available capacity of the first network resource to the resource information management server to update the available capacity of the first network resource. For details, please refer to step 608 in the above embodiment.

[0528] Optionally, the receiving module 1001 and / or the sending module 1003 are further configured to obtain resource information of the first network resource from the resource information management server or the resource information query server. For details, please refer to steps 605-606 in the above embodiments.

[0529] Optionally, the receiving module 1001 is further configured to receive the performance requirements for the first network resource sent by the first management server, as detailed in step 401 of the above embodiments; the processing module 1002 is further configured to obtain a matching first network resource based on the performance requirements for the first network resource, wherein the available capacity of the matching first network resource meets the performance requirements for the first network resource, as detailed in steps 402-404 of the above embodiments; the sending module 1003 is further configured to return the identifier of the matching first network resource to the first management server, wherein the first network resource whose resource information has changed is the allocated first network resource, and the allocated first network resource is one or more network resources among the matching first network resources.

[0530] Optionally, the receiving module 1001 is further configured to receive performance requirements for the first network resource sent by the first management server, as detailed in step 401 of the above embodiments; the processing module 1002 is further configured to obtain a matching first network resource based on the performance requirements for the first network resource, wherein the available capacity of the matching first network resource meets the performance requirements for the first network resource, as detailed in steps 402-404 of the above embodiments; the processing module 1002 is further configured to determine the allocated first network resource from the matching first network resource based on a scheduling algorithm, as detailed in step 405 of the above embodiments; the sending module 1003 is further configured to return the identifier of the allocated first network resource to the first management server, as detailed in step 406 of the above embodiments. The first network resource whose resource information has changed is the allocated first network resource, and the allocated first network resource is one or more network resources among the matching first network resources.

[0531] In one embodiment, the processing module 1002 is used to determine the matching first network resource based on the performance requirements of the first network resource, including: the processing module 1002 sending a query request to the resource information query server using the sending module 1003. The query request carries the performance requirements of the first network resource and is used to query the available first network resource whose capabilities meet the performance requirements. For details, please refer to step 402 in the above embodiment; the receiving module 1001 is used to receive the identifier of the matching first network resource returned by the resource information query server. For details, please refer to step 404 in the above embodiment.

[0532] It should be understood that MDAS104 can also perform the methods executed by MDAS104 in the above embodiments, which will not be elaborated here.

[0533] In this embodiment, the MDAS104 is presented as a functional module. Here, "module" can refer to an ASIC circuit, a processor and memory executing one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the aforementioned functions. In a simple embodiment, those skilled in the art will understand that the MDAS104 can adopt... Figure 9 It is implemented in the form shown.

[0534] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and "first" and "second" do not necessarily imply differences. The word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other module can implement several functions listed in the claims. Different dependent claims may describe certain measures, but this does not mean that these measures cannot be combined to produce good results.

[0535] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art 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.

[0536] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and modules described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0537] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the division of modules is merely a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be indirect couplings or communication connections through interfaces, devices, or modules, or they may be electrical, mechanical, or other forms of connection.

[0538] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of the embodiments of this application, depending on actual needs.

[0539] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0540] If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a computer program product, which includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program product is stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. 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 wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid state disks (SSDs)).

[0541] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method of network resource management, characterized by, The method comprises: receiving a query request sent by a resource scheduling server, the query request carrying a performance requirement for a first network resource, the first network resource being one of a communication service instance, a network slice instance, a network slice subnet instance, or a network function; determining a matched first network resource according to available capacity of an existing first network resource, the available capacity of the matched first network resource meeting the performance requirement; returning an identifier of the matched first network resource to the resource scheduling server; receiving an update request, the update request carrying an identifier of an allocated first network resource, the allocated first network resource being one or more of the matched first network resources; updating available capacity of the allocated first network resource.

2. The method of claim 1, wherein, The updating of the available capacity of the allocated first network resource comprises: obtaining, from a management data analysis server, residual available capacity of the allocated first network resource after this allocation; updating the available capacity of the allocated first network resource to the residual available capacity.

3. The method of claim 2, wherein, Further comprising: obtaining, from a network data analysis server, load information of the allocated first network resource after this allocation; sending, to the management data analysis server, the load information of the allocated first network resource after this allocation, the residual available capacity being determined based on the load information of the allocated first network resource after this allocation.

4. The method according to claim 2 or 3, characterized in that, The residual available capacity is determined based on resource information of the allocated first network resource, the resource information of the allocated first network resource comprising one or more of the following: planning information of the allocated first network resource, load information of the allocated first network resource after this allocation, requirement information for the allocated first network resource, available capacity of the allocated first network resource determined before this allocation, alarm information of the allocated first network resource, and a correspondence between the allocated first network resource and other network resources.

5. The method of claim 4, wherein, The method further comprises: sending, to the management data analysis server, stored resource information of the allocated first network resource.

6. The method according to any one of claims 1 to 3, characterized in that, The available capacity of the existing first network resource is periodically updated by a management data analysis server.

7. The method of any one of claims 1-3, wherein, The performance requirement for the first network resource is a performance requirement for the first network resource by a to-be-deployed second network resource, the update request further carrying an identifier of the to-be-deployed second network resource, the method further comprising: in response to the update request, establishing a correspondence between the to-be-deployed second network resource and the allocated first network resource, the correspondence indicating that the to-be-deployed second network resource is deployed on the allocated first network resource.

8. A method of network resource management, characterized by, The method comprises: a first management server sending, to a management data analysis server, a performance requirement for a first network resource, the first network resource being one of a communication service instance, a network slice instance, a network slice subnet instance, or a network function; The management data analysis server acquires matched first network resources according to the performance requirement, and returns identifiers of the matched first network resources to the first management server, wherein available capacities of the matched first network resources meet the performance requirement; The first management server determines to use allocated first network resources, the allocated first network resources being one or more network resources in the matched first network resources; The first management server sends an update request to a resource information management server, the update request carrying an identifier of the allocated first network resources, the update request being used to trigger updating of available capacities of the allocated first network resources.

9. The method of claim 8, wherein, The management data analysis server acquires matched first network resources according to the performance requirement comprises: The management data analysis server sends a query request to a resource information query server, the query request carrying the performance requirement for the first network resources; and receives information of the matched first network resources returned by the resource information query server, the matched first network resources being determined according to available capacities of existing first network resources.

10. The method of claim 8, wherein, Further comprising: The management data analysis server receives a resource change notification, the resource change notification carrying an identifier of the allocated first network resources, to indicate that resource information of the allocated first network resources has changed, and the resource change notification being sent after the resource information management server receives the update request; The management data analysis server determines remaining available capacities of the allocated first network resources after this allocation, the remaining available capacities being used to update available capacities of the allocated first network resources.

11. The method of claim 8, wherein, The first management server triggers updating of available capacities of the allocated first network resources comprises: The first management server sends a resource change notification, the resource change notification carrying an identifier of the allocated first network resources, to indicate that resource information of the allocated first network resources has changed; After the management data analysis server receives the resource change notification, the management data analysis server determines remaining available capacities of the allocated first network resources after this allocation, and sends the remaining available capacities to a resource information management server, the remaining available capacities being used to update available capacities of the allocated first network resources.

12. The method according to claim 10 or 11, characterized in that, The management data analysis server determines remaining available capacities of the allocated first network resources after this allocation comprises: The management data analysis server determines the remaining available capacities based on resource information of the allocated first network resources, wherein the resource information of the allocated first network resources comprises one or more of the following information: planning information of the allocated first network resources, load information of the allocated first network resources after this allocation, requirement information for the allocated first network resources, available capacities of the allocated first network resources determined before this allocation, alarm information of the allocated first network resources, and a corresponding relationship between the allocated first network resources and other network resources.

13. The method of claim 12, wherein, Further comprising: The management data analysis server obtains resource information of the allocated first network resource from a resource information management server or a resource information query server.

14. The method of claim 9, wherein, Further comprising: The management data analysis server periodically updates available capacity of the existing first network resource to the resource information management server.

15. The method according to any of claims 8-11, 14, characterized by, The first management server determines to use the allocated first network resource includes: The first management server determines the allocated first network resource from the matched first network resource based on a scheduling algorithm.

16. A resource information server, characterized by Comprising: A first receiving module, configured to receive a query request sent by a resource scheduling server, the query request carrying a performance requirement for a first network resource, the first network resource being one of a communication service instance, a network slice instance, a network slice subnet instance, or a network function; A query module, configured to determine a matched first network resource according to available capacity of an existing first network resource stored in a first storage module, the available capacity of the matched first network resource meeting the performance requirement; A first sending module, configured to return an identifier of the matched first network resource to the resource scheduling server; A second receiving module, configured to receive an update request, the update request carrying an identifier of an allocated first network resource, the allocated first network resource being one or more network resources in the matched first network resource; An update module, configured to update available capacity of the allocated first network resource stored in the first storage module.

17. The server of claim 16, wherein, The update module, configured to update the available capacity of the allocated first network resource stored in the first storage module, specifically includes: A first obtaining module, configured to obtain, from a management data analysis server, remaining available capacity of the allocated first network resource after this allocation; An update submodule, configured to update the available capacity of the allocated first network resource stored in the first storage module to the remaining available capacity.

18. The server of claim 17, wherein, Further comprising: A second obtaining module, configured to obtain, from a network data analysis server, load information of the allocated first network resource after this allocation; A second sending module, configured to send, to the management data analysis server, the load information of the allocated first network resource after this allocation, the remaining available capacity being determined based on the load information of the allocated first network resource after this allocation.

19. The server of claim 17 or 18, wherein, Further comprising: A second storage module, configured to store resource information of the allocated first network resource, wherein the resource information of the allocated first network resource includes one or more of the following information: planning information of the allocated first network resource, load information of the allocated first network resource after this allocation, requirement information for the allocated first network resource, available capacity of the allocated first network resource determined before this allocation, alarm information of the allocated first network resource, and a correspondence between the allocated first network resource and other network resources. A third sending module, configured to send resource information of the allocated first network resource to the management data analysis server, and the remaining available capacity is determined based on the resource information of the allocated first network resource.

20. The server of any of claims 16-18, wherein, The available capacity of the existing first network resource stored in the first storage module is periodically updated by the management data analysis server.

21. A system of network resources, characterized by The system comprises a first management server and a management data analysis server, The first management server and the management data analysis server are respectively configured to perform the method in any one of claims 8-15.

22. The system of claim 21, wherein, Further comprising: A resource information server, wherein the resource information server is configured to perform the method in any one of claims 1-7.

23. A computer readable storage medium, comprising instructions stored thereon, wherein the instructions, when executed by a processor, cause the processor to perform the method in any one of claims 1-7.

24. A computer program product, comprising instructions executable by a processor, wherein the instructions, when executed by the processor, cause the processor to perform the method in any one of claims 1-7. ​ ​

Images