WO2019029704A1

WO2019029704A1 - Network object management method and apparatus therefor

Info

Publication number: WO2019029704A1
Application number: PCT/CN2018/099974
Authority: WO
Inventors: 陆伟; 杨水根; 孙文琦; 谭巍
Original assignee: 华为技术有限公司
Priority date: 2017-08-11
Filing date: 2018-08-10
Publication date: 2019-02-14
Also published as: CN109379208B; CN109379208A

Abstract

The embodiments of the present application provide a network object management method and an apparatus therefor, the method comprising the following steps: a second device determining resource usage priority information concerning a first network object, the first network object being a network object to be managed; the second device sending, to a first device, a management instruction concerning the first network object, the management instruction carrying the resource usage priority information concerning the first network object; the first device receiving, from the second device, a management instruction concerning the first network object, and determining, according to the resource usage priority information concerning the first network object and resource information concerning a second network object, a resource required by the first network object, the second network object being an existing network object; and the first device managing the first network object according to the resource required by the first network object. The embodiments of the present application can implement, in the case where system resources are limited, the management of network objects, and can flexibly and minutely manage network objects.

Description

Network object management method and device thereof

The present application claims the priority of the Chinese Patent Application, filed on Aug. 11, 2017, the application number of .

Technical field

The technical field of the present application relates to the field of communications technologies, and in particular, to a network object management method and apparatus thereof.

Background technique

With the emergence of a variety of communication services, there is a significant difference in the network performance requirements of different communication services. The fifth generation mobile communication (the 5th-generation, 5G) system introduces network slice (NS). The concept of dealing with the differences in network communication performance requirements of different communication services.

Network slicing refers to the customization of different logical networks based on different service requirements on a physical or virtual network infrastructure. The network slice can be a complete end-to-end network including terminal equipment, access network, transmission network, core network and application server, which can provide complete communication services and have certain network capabilities. The network slice can also be any combination of a terminal device, an access network, a transport network, a core network, and an application server.

A network slice instance (NSI) is a real-world logical network that can meet certain network characteristics or service requirements. A network slice instance may provide one or more network services (NS). A network snippet instance can be created by the network management system. A network management system may create multiple network shard instances and manage them at the same time, including performance monitoring, fault management, and modification during the running of the network snippet instance. A complete network sharding instance can provide a complete end-to-end network service. The network sharding instance can be at least one of a network slice subnet instance (NSSI) and a network function (NF). .

Compared with the fourth-generation mobile communication (4G) system, the 5G system has significantly increased in terms of resources and capacity, but the number and types of communication services have also increased significantly, and the required system resources have also increased. Lead to limited system resources. How to manage network objects in the case of limited system resources is a technical problem to be solved in 5G systems, such as how to create/update network slice instances, how to create/update network slice subnet instances, and so on.

Summary of the invention

The technical problem to be solved by the embodiments of the present application is to provide a network object management method and a device thereof. When the system resources are limited, the network object can be managed, and the network object can be managed flexibly and finely.

A first aspect of the embodiments of the present application provides a network object management method, including:

Step 1: The first device receives, from the second device, a management instruction for the first network object, where the management command carries resource usage priority information of the first network object, where the first network object is a network object to be managed;

Step 2: The first device determines, according to the resource usage priority information of the first network object and the resource information of the second network object, the second network object is an existing network object;

Step 3: The first device manages the first network object according to resources required by the first network object.

The first network object/second network object includes at least one of a network slice instance, a network slice subnet instance, or a network function.

In a second aspect, the embodiment of the present application provides a first device, including a unit or a means for performing the foregoing steps of the first aspect.

In a third aspect, an embodiment of the present application provides a first device, including at least one processing element and at least one storage element, wherein at least one storage element is configured to store a program and data, and at least one processing element is configured to perform the first aspect of the present application. The method provided.

In a fourth aspect, an embodiment of the present application provides a first device, including at least one processing element (or chip) for performing the method of the above first aspect.

In a fifth aspect, an embodiment of the present application provides a program, when executed by a processor, for performing the method of the above first aspect.

In a sixth aspect, an embodiment of the present application provides a program product, such as a computer readable storage medium, including the program of the fifth aspect.

It can be seen that, in the foregoing aspects, in a case where the system resources are limited, the first device determines, according to the resource usage priority information of the first network object and the resource information of the second network object, the resources required by the first network object, thereby Realize the management of network objects, and can manage network objects flexibly and finely.

In a possible implementation manner, the resource information of the second network object includes the resource occupied by the second network object and the resource usage priority information of the second network object, so that the first device preempts the resource occupied by the second network object. The resources required for the first network object.

In a possible implementation manner, the resource usage priority information includes a feature identifier, a resource preemption capability level corresponding to the feature identifier, or a feature identifier, a resource preemption capability level corresponding to the feature identifier, and a resource preemption capability level corresponding to the feature identifier. . The feature identifier includes at least one of a network slice type identifier, a network slice instance identity, a network slice subnet instance identity, a network function identity, a tenant identity, or a service identity. Prioritizing the feature identifiers helps the network slicing network system to flexibly allocate resources. For example, the sender can assign higher priority to important network slicing subnet instances/network functions that have a greater impact on communication services. H.

In a possible implementation manner, the preemptive capability level of the resource corresponding to the feature identifier includes a preemptive capability level of a plurality of preset proportions, and the preemptive capability level of the preset proportion of resources is used to indicate that x% of the resources in the resource are The possibility of preemption of other network objects, so that resources of a predetermined proportion of a certain network object are preempted from the network object to preempt a predetermined proportion of resources.

In a possible implementation, when the first device determines the resources required by the first network object according to the resource usage priority information of the first network object and the resource information of the second network object, first determining to manage the first network object The quantity of resources required, that is, the quantity of resources required to execute the foregoing management instruction; and then determining the first network object according to the resource preemption capability corresponding to the feature identifier of the first network object and the resource corresponding to the feature identifier of the second network object being preempted Whether the resources occupied by the second network object can be preempted, and in the case that the preemption is determined, the resources required by the first network object are determined from the resources occupied by the second network object according to the required number of resources.

In a possible implementation manner, the resource preemption capability level and/or the resource preemption capability level corresponding to the feature identifier are determined according to the resource preemption capability level and/or the resource preemption capability level corresponding to the performance indicator; At least one of delay, throughput, simultaneous support of the number of access users, simultaneous support of the number of sessions, geographic coverage, packet loss rate, dropped call rate, user cell handover success rate, or single user throughput. Prioritization according to performance indicators is conducive to improving the security of important performance indicators.

In a possible implementation manner, the feature identifier corresponding to the resource preemption capability level and/or the resource preemption capability level of the first network object is a resource preemption capability corresponding to the performance indicator of the first network object and/or the third network object. Levels and/or resources are determined by the preemption capability level. The first network object is a component of the third network object, for example, the first network object is NF, the third network object is NSSI, the first network object is NSSI, and the third network object is NSI.

In a possible implementation manner, in a case that the first network object can preempt the resources occupied by the second network object, the first device shrinks/terminates the second network object to release part/all resources occupied by the second network object. So that other network objects can take advantage of the released resources, thereby improving resource utilization.

In a possible implementation manner, the resource usage priority information of the first network object further includes priority change policy information of the first network object, and the resource usage priority information of the first network object needs to be according to the first network object. When the priority change policy information is adjusted, the first device adjusts the resource usage priority information of the first network object according to the priority change policy information of the first network object, which is beneficial to adjust flexibly and in real time according to the network and the service state. Resources use priority information to provide limited resources to services that require more protection.

In a possible implementation manner, the first device receives the priority change policy information of the first network object from the second device; the resource usage priority information of the first network object needs to be according to the priority change policy of the first network object When the information is adjusted, the resource usage priority information of the first network object is adjusted according to the priority change policy information of the first network object, which facilitates flexible and real-time adjustment of the resource usage priority information according to the network and the service state. Limited resources are available to businesses that need more protection.

A seventh aspect of the embodiments of the present application provides a network object management method, including:

Step 1: The second device determines resource usage priority information for the first network object, where the first network object is a to-be-managed network object;

Step 2: The second device sends a management instruction for the first network object to the first device, where the management command carries resource priority information of the first network object.

In an eighth aspect, the embodiment of the present application provides a second device, including a unit or a means for performing the foregoing steps of the seventh aspect.

In a ninth aspect, the embodiment of the present application provides a second device, including at least one processing element and at least one storage element, wherein at least one storage element is used to store a program and data, and at least one processing element is used to execute the seventh aspect of the present application. The method provided.

In a tenth aspect, the embodiment of the present application provides a second device, including at least one processing element (or chip) for performing the method of the above seventh aspect.

In an eleventh aspect, an embodiment of the present application provides a program, when executed by a processor, for performing the method of the above seventh aspect.

In a twelfth aspect, the embodiment of the present application provides a program product, such as a computer readable storage medium, including the program of the eleventh aspect.

It can be seen that, in the above aspects, the second device carries the resource usage priority information in the management instruction, so that the first device preempts the required resource from the resources occupied by the existing network object according to the resource usage priority information, thereby implementing Management of network objects in the case of limited system resources.

In a possible implementation manner, the resource usage priority information includes a feature identifier, a resource preemption capability level corresponding to the feature identifier, and a resource preemption capability level corresponding to the feature identifier; the feature identifier includes a network slice type identifier and a network slice instance identifier. At least one of a network slice subnet instance identity, a network function identity, a tenant identity, or a service identity. Prioritizing the feature identifiers is beneficial to the network slicing network system to flexibly arrange resources.

In a possible implementation, the resource usage priority information of the first network object further includes priority change policy information of the first network object, and the priority change policy information of the first network object is used by the first device to adjust the first The resource usage priority information of the network object is beneficial for the first device to flexibly adjust the resource usage priority information.

In a possible implementation, the second device sends the priority change policy information of the first network object to the first device, where the priority change policy information of the first network object is used by the first device to adjust resources of the first network object. Using the priority information facilitates the first device to flexibly adjust the resource usage priority information.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background art, the drawings to be used in the embodiments of the present application or the background art will be described below.

1 is a schematic diagram of a network architecture to which an embodiment of the present application is applied;

2 is a schematic flowchart of a network object management method according to an embodiment of the present application;

3 is a diagram showing an example of a process of an NSI management method according to an embodiment of the present application;

4 is a schematic diagram of a logical structure of a device provided by an embodiment of the present application;

FIG. 5 is a simplified schematic diagram of a physical structure of a device provided by an embodiment of the present application.

Detailed ways

Embodiments of the present application relate to network slicing technology. The network slicing technology logically abstracts the network into one or more isolated network slices, each of which contains a series of logical network functions to specifically meet the differentiated requirements of different service types. For example, in the fifth generation mobile communication ^(the 5 ^th -generation, simply referred to as "5G") system, the network is a slice-demand networking, operators can bring a can be adjusted to changing user demand, And new services that quickly meet the needs of new applications.

The network slicing technology abstracts the 5G network physical infrastructure resources into a plurality of independent parallel network slice instances according to the scene requirements. Each network segment instance performs customized tailoring of network functions and management of corresponding network functions according to the needs of the business scenario and the business model. A network slice instance can be thought of as an instantiated 5G network. Such a network structure allows operators to provide the network as a service to users, and can freely combine physical networks according to indicators such as rate, capacity, coverage, delay, reliability, security, and availability to meet different users. Claim.

It should be noted that the terms “network management architecture”, “network management system” and the like in the embodiments of the present application may be mutually replaced. For ease of understanding, some terms appearing in the embodiments of the present application are first introduced.

Network slicing: refers to the customization of different logical networks based on different service requirements on a physical or virtual network infrastructure. The network slice can be a complete end-to-end network including terminal equipment, access network, transmission network, core network and application server, which can provide complete communication services and have certain network capabilities. The network slice can also be any combination of a terminal device, an access network, a transport network, a core network, and an application server. A network slice may have one or more of the following characteristics: the access network may or may not slice. The access network may be shared by multiple network slices. The characteristics and composition of different network slices may be different for their network functions.

A network slicing instance is a real-world logical network that meets certain network characteristics or service requirements. A network slice instance may provide one or more network services. A network sharding instance can be created by the network management system. A network management system may create multiple network shard instances and manage them at the same time, including performance monitoring and fault management during network snippet instance running. When multiple network slice instances coexist, at least one of partial network resources, network functions, and network slice subnet instances may be shared between network slice instances. A network tile instance may or may not be created from a network tile template.

A complete network slicing instance is capable of providing complete end-to-end network services, and the network slicing instances may be network slicing subnet instances and/or network functions. The network slice subnet instance may not need to provide a complete network service end-to-end. The network slice subnet instance may be a network function component set of the same device vendor in the network slice instance, or may be a collection of network functions divided by domain. For example, the core network network slice subnet instance and the access network network slice subnet instance. A network sliced subnet instance may be shared by multiple network slice instances. The network slice subnet instance is proposed to facilitate network management system management. A network slice instance may consist of several network slice subnet instances, each network slice subnet instance consisting of several network functions and/or other network slice subnet instances; one network slice instance may be composed of several network slice subnet instances and none The network functions that are divided into network slice subnet instances are directly composed; a network slice instance may also consist of only a few network functions.

Network functions, a processing function in the network, define functional behaviors and interfaces. Network functions can be implemented by dedicated hardware, by running software on dedicated hardware, or as virtual functions on a common hardware platform. Therefore, from the perspective of implementation, network functions can be divided into physical network functions and virtual network functions. From the perspective of use, network functions can be divided into dedicated network functions and shared network functions. Specifically, for multiple (sub)network slice instances, different network functions can be used independently. This network function is called exclusive. Network function; can also share the same network function, this network function is called shared network function. The following are collectively referred to as physical network functions and/or virtual network functions as network functions.

Referring to FIG. 1 , it is a schematic diagram of a network architecture that is applied to an embodiment of the present application. The network architecture includes a communication service management function (CSMF) entity, a network slice management function (NSMF) entity, and a network slice. Network slice subnet management function (NSSMF) entity. It should be noted that the number of CSMF entities, NSMF entities, and NSSMF entities included in the network architecture is not limited to that shown in FIG. 1 . In actual applications, multiple CSMF entities, multiple NSMF entities, and multiple NSSMF entities may be included. It should be noted that the above three management entities may be described by other names, which are not limited in this embodiment of the present application.

The CSMF entity is primarily responsible for translating the communication service requirements of the operator and/or third party customers into requirements for network or network slicing; sending the requirements for network slicing to the NSMF entity through an interface with the NSMF entity (eg, creation, termination, Modify network slice instance request, etc.; acquire management data (such as performance, fault data, etc.) of the network slice from the NSMF entity; generate management data of the communication service running on the network slice instance; receive the operator and/or the third party client Subscription requirements for management data of network slice management data and/or communication services, and the like.

The NSMF entity is mainly responsible for receiving the network slicing requirements sent by the CSMF entity; managing the life cycle, performance, faults, etc. of the network slicing instance (hereinafter, the life cycle, performance, fault management is referred to as management); composing the composition of the network slicing instance; decomposing the network The requirements of the slice instance are requirements for each network slice subnet instance and/or network function; a network slice subnet instance management request is sent to each NSSMF entity.

The NSSMF entity is mainly responsible for receiving the network slice subnet requirement sent by the NSMF entity; managing the network slice subnet instance; orchestrating the composition of the sub-network segment instance; and decomposing the network slice subnet instance requirements for each network function and/or nesting The requirements for the network slicing subnet instance; it is possible to send nested network slicing subnet instance management requests to other NSSMF entities, and so on.

The interface between the CSMF entity and the NSMF entity is interface 1, which is used by the CSMF entity to send network slice management instructions and resource usage priority information to the NSMF entity; for the NSMF entity to feed back the management instruction execution result to the CSMF entity; The CSMF entity reports management data.

The interface between the NSMF entity and the NSSMF entity is interface 2, which is used by the NSMF entity to send a network slice subnet and/or network function management command and resource usage priority information to the NSSMF entity; and is used for the NSSMF entity to feed back the management instruction execution to the NSMF entity. Result; used by the NSSMF entity to report management data to the NSMF entity.

Based on the network architecture shown in Figure 1, the following describes the network slice management process. The network slice management process is divided into three processes: network slice instance creation, network slice instance adjustment, and network slice instance termination.

Network slice instance creation process:

1) The CSMF entity receives a communication service request, which includes a service requirement, such as a geographic range that the communication service needs to cover, a network isolation requirement, a security requirement, an application requirement, and a key performance indicator of the network (key performance indicator, KPI), etc.

2) The CSMF entity translates the received communication service request into a network slice related requirement, which includes whether the network slice instance serving the above communication service can be shared with other communication services;

3) The CSMF entity sends the network slice related requirement to the NSMF entity for requesting the NSMF entity to allocate or create a network slice instance;

4) When the network slice related requirement cannot be satisfied, the NSMF entity rejects the request and sends rejection feedback to the CSMF entity; when the network slice related requirement can be satisfied, the NSMF entity determines whether the existing NSI can be reused to satisfy the The request, if applicable, the NSMF entity orchestrate the adjustment requirements of the existing NSI, and perform a network slice adjustment process. If not, the NSMF entity creates a new NSI to meet network slice related requirements;

5) The NSMF entity orchestrate the NSI and decompose the NSI requirements into NSSI requirements, including whether the required NSSI can be shared with other NSIs, and the NSMF entity identifies NSSIs that need to be newly created and reusable;

6) For the newly created NSSI, the NSMF entity sends the NSSI requirement to the corresponding NSSMF entity; the NSSMF entity creates a new NSSI and configures the NSSI to meet the relevant requirements;

7) For NSSI that can be reused, the NSMF entity sends the NSSI requirement to the corresponding NSSMF entity; the NSSMF entity adjusts and/or reconfigures the existing NSSI to meet the relevant requirements;

8) The NSMF entity combines several newly created and/or reused NSSIs into one NSI.

Network slice instance adjustment process:

1) The NSMF entity receives the NSI adjustment request, or the NSMF entity determines the NSI according to the policy decision. The adjustment of the NSI may include increasing/decreasing the capacity of the NSI, changing the topology in the NSI, and adding/deleting network functions in the NSI;

2) The NSMF entity determines the NSSI of the required adjustment according to the NSI adjustment request, and sends the adjustment request to the corresponding NSSMF entity;

3) The NSSMF entity determines whether the adjustment request is achievable. If the adjustment request cannot be implemented, the NSSMF entity rejects the request and feeds back to the NSMF entity; if the adjustment request can be implemented, the NSSMF entity determines which NSSI components need to be adjusted. The components of the NSSI can be network functions or nested NSSIs;

4) If the component is shared with other NSSIs, the NSSMF entity needs to determine whether the adjustment has an adverse effect on other NSSIs. If there is no adverse effect, the NSSMF entity performs adjustment and/or configuration of the target component; If there is a negative impact, the NSSMF entity may decide not to perform the adjustment, or the NSSMF entity creates a new NSSI component to meet the NSSI adjustment requirements, at which point the old shared NSSI component will be reconfigured and associated with the NSSI. Decoupled, the new NSSI component is associated with the NSSI.

5) If the component is exclusive to the NSSI, the NSSMF entity adjusts and configures the target NSSI component according to the adjustment request.

Network slice instance termination process:

1) The NSMF entity receives the NSI termination request, or the NSMF entity decides to terminate the NSI according to the policy, and the NSI is no longer needed;

2) The NSMF entity deregisters the NSI, and the NSI that needs to be terminated is in the logout state;

3) The NSMF entity determines which of the NSSIs constituting the NSI are terminated and which are to be reserved;

4) If the NSSI needs to be terminated, the NSMF entity sends an NSSI termination request to the corresponding NSSMF entity, and the NSSMF entity performs a termination NSSI command;

5) If the NSSI entity does not need to be terminated, the NSMF entity sends an NSSI adjustment and/or reconfiguration request to the corresponding NSSMF entity, and the NSSMF entity performs an adjustment or reconfiguration command;

6) The NSMF entity deletes the terminated NSI related information.

In the case of limited system resources, how to manage network objects is a technical problem to be solved in 5G systems, such as how to create/update network slice instances, how to create/update network slice subnet instances, and so on.

In view of this, the embodiments of the present application provide a network object management method and device thereof, which can implement management of network objects in a limited system resource, and can manage network objects flexibly and finely, thereby improving high priority. Resource protection for network objects.

The network object involved in the embodiment of the present application may include at least one of a network slice instance, a network slice subnet instance, or a network function. The network object can also be replaced by a network slice, the network slice is implemented by a network slice instance, and the network slice instance is composed of a network sliced subnet instance and/or a network function. The network object management method in the embodiment of the present application can also be referred to as a network slice management method, which involves a process of creating and adjusting a network slice instance, and creating and adjusting a network sliced subnet instance.

The first device in the embodiment of the present application is an entity that receives a management instruction, and the second device is an entity that sends a management instruction. The first device may be an NSMF entity or an NSSMF entity, and the second device may be a CSMF entity or an NSMF entity.

When the first device is an NSMF entity, the second device is a CSMF entity. In this case, the management command may be: creating a network slice instance instruction, adjusting a network slice instance instruction, etc.; when the first device is an NSSMF entity, the second device is an NSMF. Entity, at this time, the management instruction may be to create an NSSI and/or NF instruction, adjust an NSSI and/or NF instruction, and the like.

The network object management method provided by the embodiment of the present application will be described in detail below with reference to FIG. 2 and FIG.

FIG. 2 is a schematic flowchart of a network object management method according to an embodiment of the present disclosure. The method is introduced from the perspective of interaction between the first device and the second device, and may include, but is not limited to, the following steps:

Step S201: The second device determines resource usage priority information for the first network object.

The first network object is a network object to be managed, and the to-be-managed can be understood as being to be created or to be adjusted. To be created, a new network object needs to be created in the network architecture, and the to-be-adjusted refers to the need to exist in the network architecture ( Already existing) network objects are adjusted.

If the second device is a CSMF entity and the first device is an NSMF entity, the to-be-managed network object may be an NSI to be created and an NSI to be adjusted; if the second device is an NSMF entity and the first device is an NSSMF entity, the to-be-managed The network object can be the NSSI to be created, the NSSI to be adjusted, the NF to be created, and the NF to be adjusted.

The resource usage priority information may be used to describe a resource preemption capability level of the network object, and may also be used to describe a capability level of the network object's resources being preempted by other network objects. In other words, the resource usage priority information is used to describe its ability to preempt other network objects, and is also used to describe the capability level of some or all of its own resources being preempted by other network objects.

In a possible implementation manner, the capability level of the network object's resources being preempted by other network objects may be composed of a plurality of preset proportions of resources being preempted by other network objects. For example, a capability level at which 10% of resources of a network object are preempted by other network objects, a capability level at which 20% of resources of a network object are preempted by other network objects, and the like. The preemption capability levels of resources with different preset ratios may be the same or different.

In another possible implementation manner, the capability level of the network object being preempted by other network objects is only a single resource preemption capability level, and the number of preempted resources is not distinguished. It can be understood that in the implementation manner, The preempted capability level is equivalent to the capability level at which 100% of the network objects are preempted by other network objects.

In another possible implementation manner, the resource preemption capability level and the resource preemption capability level are represented by a resource priority level, that is, the preemption capability and the preemption capability are not distinguished. When a network object preempts the resources of other network objects, the resource priority level is used to determine the preemption capability; when the resources of the network object are preempted by other network objects, the resource priority level is used to determine the preemption capability.

It should be understood that the resource preemptive capability level and the resource preempted capability level in the example of the present application include at least one of all possible implementation manners described above.

In an implementation manner, the resource usage priority information is divided according to the feature identifier granularity, and the feature identifier may include a network slice type identifier, a network slice instance identity identifier, a network slice subnet instance identity identifier, a network function identity identifier, a tenant identity identifier, or At least one of the service identities. The prioritization of feature identification facilitates the flexible scheduling of resources by the network slice management system. For example, the sender can assign a higher priority to important NSSI/NFs that have a greater impact on communication services, and can reasonably utilize limited resources. In addition, when the receiver is unable to complete the sender's instruction due to insufficient resources, the sender can learn from the receiver's feedback which NSSI/NF resource cannot be satisfied, thereby making targeted deployment adjustments.

The network slice type identifier is used to identify different types of network slices, one network slice type corresponds to one identity identifier, and the network slice type identifier may also be used to identify different network slices. Network slice type identifiers may include, but are not limited to, ultra-reliable and low latency communications (URLLC), machine type communication (MTC), meter reading, video browsing, and the like. When the resource usage priority information is divided by the network slice type identifier, if the network slice type identifiers of any two network objects are the same, the two network objects have the same priority, and resource competition does not occur. The resource competition occurs between network objects identified by different network slice types. For example, the network slice type identifier of the network object 1 is URLLC, and the network slice type identifier of the network object 2 is video browsing, and the network object 1 and the network object 2 are Resource competition occurs.

The network slice instance identity is used to identify different network slice instances, and one network slice instance corresponds to one identity identifier. When resource usage priority information is partitioned using the network slice instance identity, resource contention occurs between different network slice instances.

The network slice subnet instance identity is used to identify different network slice subnet instances, and one network slice subnet instance corresponds to one identity. When the resource usage priority information is divided by the network slice subnet instance identity, the resource contention occurs between different network slice subnet instances. These different network slice subnet instances may belong to the same network slice instance or may be different. Network slice instance.

The network function identity is used to identify different network functions, and one network function corresponds to one identity. When resource usage priority information is divided by network function identity, resource contention occurs between different network functions. These different network functions may belong to the same network slice instance/network slice subnet instance, or may belong to different network slices. Instance/network slice subnet instance.

The same network slice instance may provide services for several tenants at the same time. The same network slice instance may also provide multiple different services at the same time. One tenant corresponds to one identity, and one service corresponds to one identity. When the resource usage priority information is divided by using the tenant identity, the resource contention occurs between multiple tenants of the same network slice instance or between multiple tenants of different network slice instances. Similarly, when using service identity for partitioning, resource contention occurs between multiple services of the same network slice instance or between multiple services of different network slice instances.

In an implementation manner, the resource usage priority information is divided according to the performance indicator granularity, and the performance indicators may include delay, throughput, simultaneous support access users, simultaneous support sessions, geographic coverage, packet loss rate, and dropped calls. At least one of a rate, a user cell handover success rate, or a single user throughput rate. The prioritization of performance indicators helps to improve the security of important performance indicators. When the receiver cannot complete the management instruction of the sender, the sender can know from the feedback message sent by the receiver which performance indicators cannot be achieved.

The delay is the time required for a message or packet data to be transmitted from one end of the network to the other. The throughput rate refers to the average rate of communication through a communication channel per unit time. The throughput here can be the system throughput rate. Single-user throughput refers to the average rate at which a single user travels through a communication channel per unit of time.

The resource usage priority information carries the priority level corresponding to the feature identifier/performance indicator in addition to the feature identifier/performance identifier. The priority level may include a resource preemption capability level and a resource preemption capability level.

The resource preemption capability level may be a form representation of a number, a form of a letter, or a description of a high, a medium, or a low, and a specific number of levels and a correspondence between the level and the expressed ability. The relationship is not limited in the embodiment of the present application. For example, the level is divided into three files, where 1 indicates that the resource preemption capability is the strongest, and 3 indicates that the resource preemption capability is the weakest. It can be understood that the stronger the resource preemption capability, the easier it is to seize resources.

For example, the network slice type identifier of the network object 1 is the URLLC, the resource preemption capability level corresponding to the URLLC is the strongest, the network slice type identifier of the network object 2 is the video browsing, and the resource corresponding to the video browsing is the strongest, and the network object is the strongest. 1 can seize the resources of network object 2.

The resource preemption capability level corresponding to the performance indicator of a network object may be converted into a resource preemption capability level corresponding to the network object and/or the feature identifier of the sub-network object constituting the network object, and the specific conversion method is not implemented in the embodiment of the present application. limited. It can be understood that the resource preemption capability level corresponding to the feature identifier of a certain network object and/or the sub-network object constituting the network object may be determined according to the resource preemption capability level corresponding to the performance indicator of the network object. The sub-network object is a part that constitutes a network object. For example, the network object is NSI, the sub-network object constituting the network object is NSSI, the network object is NSSI, and the sub-network object constituting the network object is NF. The embodiment of the present application is mainly introduced by using a resource preemption capability level corresponding to a performance indicator of a network object to be a resource preemption capability level corresponding to the feature identifier of the network object, and the conversion process may be performed on the first device, or may be performed. Executed at the second device.

The resource is preempted by the capability level. In one possible implementation manner, the capability level may be included in one or more preset proportions of resources being preempted. The capability level of the preempted resource being preempted can be understood as the probability level of x% being preempted in the resource, x% is the preset ratio, the specific value of the preset ratio, the number of levels of the priority level, and the priority. The correspondence between the level and the indicated capability is not limited in the embodiment of the present application. For example, the capability level of 10% of resources being preempted is divided into 3 files, 1 means that 10% of resources are most likely to be preempted, and 3 means 10 % of resources are the least likely to be preempted. Understandably, the weaker the resource is preempted, the less likely it is to be preempted. This competency level helps to protect the basic needs of low priority services. In another possible implementation manner, the resource preemption capability level is composed only of the individual resource preemption capability level, for example, the level is divided into three files, 1 indicates that the resource is most likely to be preempted, and 3 indicates that the resource is preempted to be the lowest. . Understandably, the stronger the ability of resources to be preempted, the easier it is to seize resources. It should be understood that the resource is preempted by the level of capability, which may be in the form of a number, in the form of a letter, or in the form of a description of high, medium, or low, depending on how many levels and between the level and the expressed ability. The corresponding relationship is not limited in the embodiment of the present application.

Similarly, the preemptive capability level of the resource corresponding to the performance indicator of a network object may be converted into a preemptive capability level of the resource corresponding to the network object and/or the feature identifier of the sub-network object that constitutes the network object.

The resource or system resource involved in the embodiment of the present application may include at least one of a computing resource, a storage resource, or a network resource.

If the second device is a CSMF entity, the second device may determine, according to the communication service request sent by the operator and/or the third-party client, the first network object and the resource usage priority information of the first network object, where the specific determining method is in the present application. The examples are not limited.

If the second device is an NSMF entity, the second device may determine the resource usage priority information of the first network object and the first network object according to the request sent by the CSMF entity, and the specific determining method is not limited in the embodiment of the present application.

Step S202: The second device sends a management instruction for the first network object to the first device, where the management command carries resource usage priority information of the first network object; correspondingly, the first device receives the management instruction from the second device;

If the second device is a CSMF entity, and the first device is an NSMF entity, the management command is to create an NSI or adjust an NSI command; if the second device is an NSMF entity and the first device is an NSSMF entity, the management command is to create an NSSI and / or NF instructions, or to adjust NSSI and / or NF instructions.

It should be noted that the number of the foregoing first network objects is at least one, and the first network object is assumed to be NSI. If the quantity is one, the management instruction is to create or adjust an NSI; if the quantity is multiple, the management instruction To create or adjust multiple NSIs.

When receiving the management instruction, the first device may determine, according to the available resources in the current network, whether the management requirement of the first network object is met, and if yes, the existing network slice instance/network slice subnet instance may be used. The creation/adjustment process is performed; if not, the process may be performed in accordance with step S203 and step S204. It can be understood that, for the management requirements of any one of the first network objects, the satisfaction is processed according to the existing process, and if not, the processing is performed according to steps S203 and S204.

Step S203: The first device determines, according to the resource usage priority information of the first network object and the resource information of the second network object, the resources required by the first network object;

The second network object is an existing existing network object in the network architecture, and may be a network object that has been created or has been adjusted. It can be understood that the second network object has acquired the required resources in the network architecture and occupies these resources. It should be noted that the number of second network objects is also at least one.

The resource information of the second network object includes resources occupied by the second network object and resource usage priority information of the second network object. The resource usage priority information of the second network object includes a feature identifier of the second network object, a resource preemption capability level corresponding to the feature identifier of the second network object, and a resource preemption capability level corresponding to the feature identifier of the second network object. Since the second network object is an existing network object, the resource usage priority information of the second network object already exists in the first device or in the network architecture, and the first device can directly acquire.

It is assumed that the management instruction is a management instruction for a certain first network object, and when receiving the management instruction, the first device determines the quantity of resources required to manage the first network object, that is, determines how much resources are needed to execute the management instruction. Then, the first device determines, according to the resource usage priority information of the first network object and the resource usage priority information of the second network object, whether the first network object can preempt the resources occupied by the second network object. Specifically, the first device may determine that the resource preemption capability level corresponding to the feature identifier of the first network object is higher than which or which resource corresponding to the feature identifier of the second network object is preempted.

In an implementation manner, the first device may be configured to determine that the resource preemption capability level corresponding to the feature identifier of the first network object is higher than the resource preemption capability level corresponding to the feature identifier of the second network object. Preempting resources from resources occupied by the second network object. In another implementation manner, the resource preemption capability level corresponding to the feature identifier of the first network object is determined to be higher than the preset ratio of the resources of the second network object corresponding to the feature identifier of the second network object. In the case, the first device may preempt the resources from the resources occupied by the second network object according to the preset ratio.

In an implementation manner, in a case where it is determined that a resource preemption capability level corresponding to a feature identifier of the first network object is higher than a resource preemption capability level corresponding to a feature identifier of a plurality of second network objects, the first device is configured according to The resources corresponding to the feature identifiers of the second network objects are selected by the second network object from the second network objects, and the resources corresponding to the feature identifiers of the second network objects are most easily preempted, and then The first device may preempt resources from resources occupied by the second network object.

In the case that the first network object can preempt part or all of the resources from the resources occupied by the second network object, the first device can determine whether the preempted resource meets the required number of resources of the first network object, and if so, Therefore, the resources occupied by the other second network objects are not required to be preempted; if not, the first device continues to preempt the resources occupied by the other second network objects until the content is satisfied.

If the resource preemption capability level corresponding to the feature identifier of the first network object is lower than the resource preemption capability level corresponding to the feature identifier of each second network object, the first network object cannot preempt any of the resources of the second network object. The first device may send a feedback message to the second device, where the feedback message is used to indicate that the management command cannot be completed, and the reason for carrying the message is that the resource is insufficient, and the priority corresponding to the specific feature identifier is insufficient to preempt the resource indication. In order for the second device to know which feature identified resource cannot be satisfied, a targeted deployment adjustment is made.

If the resource usage priority information of the first network object includes the resource preemption capability level corresponding to the performance indicator of the first network object, the priority of the feedback message carrying the specific performance indicator is insufficient to preempt the resource indication.

For the case where the management instruction is a management instruction for a plurality of first network objects, resources required for each first network object may be determined according to processing for one first network object.

In a case where a certain first network object needs to preempt part/all resources of a certain second network object, the first device may shrink/terminate the second network object to release part/all resources occupied by the second network object. . It can be understood that the second network object is contracted to release part of resources occupied by the second network object; the second network object is terminated to release all resources occupied by the second network object. Terminating the second network object may also include logging out (deactivating) the second network object. The specific contraction/finalization process is not limited in the embodiment of the present application.

Step S204: The first device manages the first network object according to resources required by the first network object.

The first device may create or adjust the first network object according to the resources required by the first network object, and the specific creation or adjustment process is not limited in the embodiment of the present application.

In the embodiment described in FIG. 2, the first device determines resources required by the first network object from resources occupied by the second network object according to resource usage priority information of the first network object, and manages the first network object. Therefore, when the system resources are limited, the management of the network objects can be realized, and the preemption is performed according to the priorities, so that the network objects can be managed flexibly and finely.

In an implementation manner, after the first network object is preempting the part/all resources of the second network object, the first device may send the execution result feedback to the second device, where the feedback message includes a certain network object preemption. How many resources of a certain second network object and/or management actions for the second network object, so that the second device knows the resource preemption situation.

In an implementation manner, the foregoing management instruction further includes priority change policy information of the first network object, where the priority change policy information is used to instruct the first device to adjust resource usage priority information of the first network object. The priority change policy information may be applied to scenarios that are prioritized according to feature identifiers, and may also be applied to scenarios that are prioritized according to performance indicators.

Exemplarily, the priority change policy information indicates that the resource preemption capability level changes with time, for example, during the daytime, the resource preemption capability level is the highest, and at night, the resource preemption capability level is the lowest. Illustratively, the priority change policy information indicates that the resource preemption capability level varies with the number of users. For example, if the number of users is greater than the threshold, the resource preemption capability level is the highest, and when the number of users is less than or equal to the threshold, the resource preemption capability level is the lowest. .

The first device determines, according to the priority change policy information of the first network object, whether the resource usage priority information of the first network object needs to be adjusted, and if it is determined that the adjustment needs to be performed, according to the priority change policy information of the first network object The resource of the first network object is adjusted using the priority information. Correspondingly, in the case that the resource usage priority information of the first network object is adjusted, the first device adaptively re-determines the resources required by the first network object.

The priority change policy information of the first network object may not be carried in the management command, and the second device separately sends the priority change policy information of the first network object to the first device, and the embodiment may not limit the step and the step S202. In order.

Adjusting the resource usage priority information through the priority change policy information is beneficial to adjusting the priority indication in real time according to the network and the service status, and providing limited resources to the services that need more protection.

FIG. 3 is a schematic diagram of a flow of an NSI management method according to an embodiment of the present application. The figure is introduced from the perspective of interaction between a CSMF entity and an NSMF entity, and the number of the first NSI and the second NSI is one and the first. The resources occupied by the two NSIs can satisfy the resource requirements for creating the first NSI. The processes shown in the figure may include but are not limited to:

Step S301: The CSMF entity determines resource usage priority information for the first NSI;

The resource usage priority information of the first NSI includes an NSI identity identifier of the first NSI, a resource preemption capability level corresponding to the NSI identity identifier, and a resource preemption capability level corresponding to the NSI identity identifier.

The CSMF entity may convert the resource preemption capability level and/or the resource preemption capability level corresponding to the performance indicator of the first NSI into a resource preemption capability level and/or a resource preemption capability level corresponding to the NSI identity identifier of the first NSI.

If the resource usage priority information of the first NSI includes the performance indicator of the first NSI, the resource preemption capability level corresponding to the performance indicator, and the preemption capability level corresponding to the performance indicator, the NSMF entity may preempt the resource corresponding to the performance indicator. The capability level and/or the resource preempted capability level are converted into a resource preemption capability level and/or a resource preemption capability level corresponding to the NSI identity of the first NSI.

Step S302: The CSMF entity sends a creation instruction for the first NSI to the NSMF entity, where the creation instruction carries the resource usage priority information of the first NSI; correspondingly, the NSMF entity receives the creation instruction from the CSMF entity;

Step S303: The NSMF entity determines, according to the resource usage priority information of the first NSI and the resource information of the second NSI, the resources required by the first NSI;

The NSMF entity determines whether the resource preemption capability level corresponding to the NSI identifier of the first NSI is higher than the resource preemption capability level corresponding to the NSI identifier of the second NSI.

If yes, the NSMF entity may preempt part or all of the resources occupied by the second NSI, thereby determining resources required by the first NSI, and performing steps S304, S305.

If not, the NSMF entity sends a feedback message to the CSMF entity, where the feedback message is used to indicate that the management command cannot be completed, because the resource is insufficient, and the priority of the first NSI is insufficient to preempt the resource, so that the CSMF entity knows the first NSI. The resources corresponding to the NSI identity cannot be met, so that targeted deployment adjustments can be made.

Step S304: The NSMF entity shrinks/terminates the second NSI;

The NSMF entity shrinks/terminates the second NSI to release some/all of the resources of the second NSI.

Step S305: The NSMF entity creates a first NSI according to resources required by the first NSI.

The example diagrams described in FIG. 3 are for example only and do not constitute a limitation on the embodiments of the present application.

The above describes the method of the embodiment of the present application in detail, and the apparatus of the embodiment of the present application is provided below.

FIG. 4 is a schematic diagram of a logical structure of a device provided by an embodiment of the present application. The device 40 may include a processing unit 401 and a transceiver unit 402. The device 40 may be the first device or the second device in the embodiment shown in FIG. 2, and may be a CSMF entity, an NSMF entity, or an NSSMF entity.

If the device 40 is the first device in the embodiment shown in FIG. 2, the transceiver unit 402 can be configured to communicate with the second device, for example, performing step S202 in the embodiment shown in FIG. a management instruction of the first network object, the management instruction carries resource usage priority information of the first network object, where the first network object is a network object to be managed; and the processing unit 401 is configured to perform an operation of controlling the first device, for example, FIG. 2 Step S203 and step S204 in the illustrated embodiment, that is, determining resources required by the first network object according to resource usage priority information of the first network object and resource information of the second network object, according to required by the first network object The resource manages the first network object, and the second network object is an existing network object. For details, refer to the corresponding description in the embodiment shown in FIG. 2, and details are not described herein again.

The resource information of the second network object includes resources occupied by the second network object and resource usage priority information of the second network object.

The resource usage priority information includes a feature identifier, a resource preemption capability level corresponding to the feature identifier, and a resource preemption capability level corresponding to the feature identifier; the feature identifier includes a network slice type identifier, a network slice instance identity identifier, and a network slice subnet instance identity. At least one of an identity, a network function identity, a tenant identity, or a service identity.

The resource preemption capability level and/or the resource preemption capability level corresponding to the feature identifier are determined according to the resource preemption capability level and/or the resource preemption capability level corresponding to the performance indicator; the performance indicators include delay, throughput, and simultaneous support. At least one of the number of access users, the number of supported sessions, the geographic coverage, the packet loss rate, the dropped call rate, the user cell handover success rate, or the single-user throughput rate.

In an implementation manner, in a case that the first network object can preempt the resources occupied by the second network object, the processing unit 401 is further configured to shrink/terminate the second network object to release the portion occupied by the second network object. /All resources. For details, refer to the corresponding description in the embodiment shown in FIG. 2, and details are not described herein again.

In an implementation manner, the resource usage priority information of the first network object further includes priority change policy information of the first network object, and the processing unit 401 is further configured to: adjust the policy information according to the priority of the first network object. In the case of the resource usage priority information of the first network object, the resource usage priority information of the first network object is adjusted according to the priority change policy information of the first network object. For details, refer to the corresponding description in the embodiment shown in FIG. 2, and details are not described herein again.

In an implementation manner, the transceiver unit 402 is further configured to receive the priority change policy information of the first network object from the second device, where the processing unit 402 is further configured to: adjust the policy information according to the priority of the first network object. When the resource usage priority information of the network object is used, the resource usage priority information of the first network object is adjusted according to the priority change policy information of the first network object. For details, refer to the corresponding description in the embodiment shown in FIG. 2, and details are not described herein again.

If the device 40 is the second device in the embodiment shown in FIG. 2, the processing unit 401 can be configured to perform an operation of controlling the second device, for example, performing step S201 in the embodiment shown in FIG. 2, that is, determining for the first network. The resource usage priority information of the object; the transceiver unit 402 can be configured to communicate with the first device, for example, performing step S202 in the embodiment shown in FIG. 2, that is, sending a management instruction for the first network object to the first device, the management The instruction carries resource usage priority information of the first network object. For details, refer to the corresponding description in the embodiment shown in FIG. 2, and details are not described herein again.

FIG. 5 is a simplified schematic diagram of a physical structure of a device according to an embodiment of the present disclosure. The device 50 may be a first device or a second device in the embodiment shown in FIG. 2, and may be a CSMF entity, an NSMF entity, or an NSSMF entity. . The device 50 includes a transceiver 501, a processor 502, and a memory 503. The transceiver 501, the processor 502, and the memory 503 may be connected to one another via a bus 504, or may be connected in other manners. Related functions implemented by the processing unit 401 shown in FIG. 4 may be implemented by one or more processors 502. The related functions implemented by the transceiver unit 402 shown in FIG. 4 can be implemented by the transceiver 501.

The memory 503 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read only memory (EPROM), or A compact disc read-only memory (CD-ROM) for use in related instructions and data.

The transceiver 501 is configured to transmit data and/or signaling, as well as receive data and/or signaling.

The processor 502 may include one or more processors, for example, including one or more central processing units (CPUs). In the case where the processor 502 is a CPU, the CPU may be a single core CPU, It can be a multi-core CPU.

If the device 50 is the first device, the processor 502 is configured to support the first device to perform steps S203 and S204 in the embodiment shown in FIG. 2, according to the resource usage priority information of the first network object and the second network object. The resource information determines resources required by the first network object, and manages the first network object according to resources required by the first network object.

If the device 50 is the second device, the processor 502 is configured to support the second device to perform step S201 in the example shown in FIG. 2, and determine resource usage priority information for the first network object.

The memory 503 is used to store program codes and data of the device 50.

The transceiver 501 is configured to communicate with other devices. If the device 50 is a CSMF entity, the transceiver 501 is configured to communicate with an NSMF entity, an operator, or a third party client; if the device is an NSMF entity, the transceiver 501 is used with the CSMF entity. The NSSMF entity communicates; if the device is an NSSMF entity, the transceiver is configured to communicate with the NSMF entity or other device.

If the device 50 is the first device, the transceiver 501 is configured to receive, from the second device, a management instruction for the first network object, where the management command carries resource usage priority information of the first network object; if the device is the second device The device, the transceiver 501 is configured to send a management instruction for the first network object to the first device.

For details about the steps performed by the processor 502 and the transceiver 501, refer to the description of the embodiment shown in FIG. 2, and details are not described herein again.

It will be appreciated that Figure 5 only shows a simplified design of the device. In practical applications, the device may also include other necessary components, including but not limited to any number of transceivers, processors, controllers, memories, communication units, etc., and all devices that can implement the present application are in the present application. Within the scope of protection.

One of ordinary skill in the art can understand all or part of the process of implementing the above embodiments, which can be completed by a computer program to instruct related hardware, the program can be stored in a computer readable storage medium, when the program is executed The flow of the method embodiments as described above may be included. The foregoing storage medium includes various media that can store program codes, such as a ROM or a random access memory RAM, a magnetic disk, or an optical disk. Accordingly, a further embodiment of the present invention provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the methods described in the various aspects above.

Yet another embodiment of the present invention also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the various aspects above.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in or transmitted by a computer readable storage medium. The computer instructions may be from a website site, computer, server or data center via a wired (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Another website site, computer, server, or data center for transmission. The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)) or the like.

Claims

A network object management method, comprising:

Receiving, by the first device, a management instruction for the first network object, where the management instruction carries resource usage priority information of the first network object, where the first network object is a to-be-managed network object;

Determining, by the first device, resources required by the first network object according to resource usage priority information of the first network object and resource information of the second network object, where the second network object is an existing network object;

The first device manages the first network object according to resources required by the first network object;

The first network object/the second network object includes at least one of a network slice instance, a network slice subnet instance, or a network function.
The method according to claim 1, wherein the resource information of the second network object comprises a resource occupied by the second network object and resource usage priority information of the second network object.
The method according to claim 1 or 2, wherein the resource usage priority information includes a feature identifier, a resource preemption capability level corresponding to the feature identifier, and a resource preemption capability level corresponding to the feature identifier; The feature identifier includes at least one of a network slice type identifier, a network slice instance identity, a network slice subnet instance identity, a network function identity, a tenant identity, or a service identity.
The method according to claim 3, wherein the first device determines resources required by the first network object according to resource usage priority information of the first network object and resource information of the second network object. ,include:

The first device determines a quantity of resources required to manage the first network object;

Determining that the first network object can preempt the second network object according to a resource preemption capability level corresponding to the feature identifier of the first network object and a resource preemption capability level corresponding to the feature identifier of the second network object In the case of the occupied resource, the first device determines the resource required by the first network object from the resources occupied by the second network object according to the quantity of the resource.
The method according to claim 4, wherein the resource preemption capability level and/or the resource preemption capability level corresponding to the feature identifier are determined according to a resource preemption capability level and/or a resource preemption capability level corresponding to the performance indicator. The performance indicators include delay, throughput, simultaneous support of access users, simultaneous support of sessions, geographic coverage, packet loss rate, dropped call rate, user cell handover success rate, or single-user throughput rate. At least one.
The method of claim 4, wherein the method further comprises:

In a case that the first network object can preempt the resources occupied by the second network object, the first device shrinks/terminates the second network object to release part/all occupied by the second network object. Resources.
The method according to any one of claims 1-6, wherein the resource usage priority information of the first network object further includes priority change policy information of the first network object;

The method further includes:

The first device according to the priority change policy of the first network object, where the resource usage priority information of the first network object needs to be adjusted according to the priority change policy information of the first network object The information adjusts resource usage priority information of the first network object.
The method according to any one of claims 1 to 6, wherein the method further comprises:

Receiving, by the first device, priority change policy information of the first network object from the second device;

The first device according to the priority change policy of the first network object, where the resource usage priority information of the first network object needs to be adjusted according to the priority change policy information of the first network object The information adjusts resource usage priority information of the first network object.
A network slice management method, comprising:

The second device determines resource usage priority information for the first network object, where the first network object is a network object to be managed;

The second device sends a management instruction for the first network object to the first device, where the management instruction carries resource priority information of the first network object;

The first network object includes at least one of a network slice instance, a network slice subnet instance, or a network function.
The method according to claim 9, wherein the resource usage priority information comprises a feature identifier, a resource preemption capability level corresponding to the feature identifier, and a resource preemption capability level corresponding to the feature identifier; The identifier includes at least one of a network slice type identifier, a network slice instance identity, a network slice subnet instance identity, a network function identity, a tenant identity, or a service identity.
The method according to claim 10, wherein the resource preemption capability level and/or the resource preemption capability level corresponding to the feature identifier are determined according to a resource preemption capability level and/or a resource preemption capability level corresponding to the performance indicator. The performance indicators include delay, throughput, simultaneous support of access users, simultaneous support of sessions, geographic coverage, packet loss rate, dropped call rate, user cell handover success rate, or single-user throughput rate. At least one.
The method according to any one of claims 9 to 11, wherein the resource usage priority information of the first network object further includes priority change policy information of the first network object, the first network The priority change policy information of the object is used by the first device to adjust resource usage priority information of the first network object.
The method of any of claims 9-11, wherein the method further comprises:

The second device sends the priority change policy information of the first network object to the first device, where the priority change policy information of the first network object is used by the first device to adjust the first network The resource usage priority information of the object.
A first device, comprising a processor and a transceiver,

The transceiver is configured to receive, from the second device, a management instruction for the first network object, where the management instruction carries resource usage priority information of the first network object, where the first network object is a network object to be managed ;

The processor is configured to determine resources required by the first network object according to resource usage priority information of the first network object and resource information of a second network object, where the second network object is an existing network Object

The processor is further configured to manage the first network object according to resources required by the first network object;

The first network object/the second network object includes at least one of a network slice instance, a network slice subnet instance, or a network function.
The first device according to claim 14, wherein the resource information of the second network object comprises resources occupied by the second network object and resource usage priority information of the second network object.
The first device according to claim 14 or 15, wherein the resource usage priority information comprises a feature identifier, a resource preemption capability level corresponding to the feature identifier, and a resource preemption capability level corresponding to the feature identifier. The feature identifier includes at least one of a network slice type identifier, a network slice instance identity, a network slice subnet instance identity, a network function identity, a tenant identity, or a service identity.
The first device according to claim 16, wherein the processor is configured to determine, according to resource usage priority information of the first network object and resource information of a second network object, the first network object The resource is specifically used to determine the number of resources required to manage the first network object; and the resource preemption capability level corresponding to the feature identifier of the first network object and the feature identifier of the second network object If the resource is preempted, the first network object can preempt the resources occupied by the second network object, and the first network is determined from the resources occupied by the second network object according to the quantity of the resource. The resources required by the object.
The first device according to claim 17, wherein the resource preemption capability level and/or the resource preemption capability level corresponding to the feature identifier are resource preemption capability levels and/or resource preemption capabilities according to performance indicators. The performance indicators include delay, throughput, simultaneous access users, simultaneous support sessions, geographic coverage, packet loss rate, dropped call rate, user cell handover success rate, or single-user throughput rate. At least one of them.
A first device according to claim 17, wherein

The processor is further configured to shrink/terminate the second network object to release the second network object when the first network object can preempt the resources occupied by the second network object. Some/all resources.
The first device according to any one of claims 14 to 19, wherein the resource usage priority information of the first network object further includes priority change policy information of the first network object;

The processor is further configured to: according to the priority of the first network object, if the resource usage priority information of the first network object needs to be adjusted according to the priority change policy information of the first network object The level change policy information adjusts resource usage priority information of the first network object.
A first device according to any one of claims 14-19, wherein

The transceiver is further configured to receive, from the second device, priority change policy information of the first network object;

The processor is further configured to: according to the priority of the first network object, if the resource usage priority information of the first network object needs to be adjusted according to the priority change policy information of the first network object The level change policy information adjusts resource usage priority information of the first network object.
A second device, comprising a processor and a transceiver,

The processor is configured to determine resource usage priority information for the first network object, where the first network object is a to-be-managed network object;

The transceiver is configured to send, to the first device, a management instruction for the first network object, where the management instruction carries resource priority information of the first network object;

The first network object includes at least one of a network slice instance, a network slice subnet instance, or a network function.
The second device according to claim 22, wherein the resource usage priority information comprises a feature identifier, a resource preemption capability level corresponding to the feature identifier, and a resource preemption capability level corresponding to the feature identifier; The feature identifier includes at least one of a network slice type identifier, a network slice instance identity, a network slice subnet instance identity, a network function identity, a tenant identity, or a service identity.
The second device according to claim 23, wherein the resource preemption capability level and/or the resource preemption capability level corresponding to the feature identifier is a resource preemption capability level and/or a resource preemption capability according to the performance indicator. The performance indicators include delay, throughput, simultaneous access users, simultaneous support sessions, geographic coverage, packet loss rate, dropped call rate, user cell handover success rate, or single-user throughput rate. At least one of them.
The second device according to any one of claims 22 to 24, wherein the resource usage priority information of the first network object further includes priority change policy information of the first network object, where The priority change policy information of the network object is used by the first device to adjust resource usage priority information of the first network object.
A second device according to any one of claims 22-24, wherein

The transceiver is further configured to send priority change policy information of the first network object to the first device, where priority change policy information of the first network object is used by the first device to adjust the The resource usage priority information of the first network object.
A first device, comprising: a memory and one or more processors, the memory being coupled to the one or more processors, the one or more processors for performing The method of any of claims 1-8.
A first device, comprising: a memory and one or more processors, the one or more processors coupled to a memory, reading instructions in the memory and in accordance with the instructions Performing the method of any of claims 1-8.
A second device, comprising: a memory and one or more processors coupled to the one or more processors, the one or more processors for performing The method of any of claims 9-13.
A second device, comprising: a memory and one or more processors, the one or more processors coupled to a memory, reading instructions in the memory and in accordance with the instructions Performing the method of any of claims 9-13.
A computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform the network object management method of any of claims 1-8, or perform any of claims 9-13 The network object management method described.
A computer program product comprising instructions, when executed on a computer, causing a computer to perform the method of any of claims 1-8, or to perform the network object of any of claims 9-13 Management method.