CN109525409B - Processing method and management equipment of network slice template - Google Patents

Processing method and management equipment of network slice template Download PDF

Info

Publication number
CN109525409B
CN109525409B CN201710847660.7A CN201710847660A CN109525409B CN 109525409 B CN109525409 B CN 109525409B CN 201710847660 A CN201710847660 A CN 201710847660A CN 109525409 B CN109525409 B CN 109525409B
Authority
CN
China
Prior art keywords
network slice
management entity
information
template
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201710847660.7A
Other languages
Chinese (zh)
Other versions
CN109525409A (en
Inventor
孙文琦
陆伟
谭巍
倪麦尔·伽米尼·瑟纳瑞斯
杨水根
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201710847660.7A priority Critical patent/CN109525409B/en
Priority to PCT/CN2018/106018 priority patent/WO2019057011A1/en
Publication of CN109525409A publication Critical patent/CN109525409A/en
Application granted granted Critical
Publication of CN109525409B publication Critical patent/CN109525409B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Abstract

The application relates to the technical field of networks, in particular to a processing method and management equipment of a network slice template. The method comprises the steps that a first management entity receives first network slice template information sent by a second management entity; the first network slice template information is a subset of all information contained in a first network slice template determined by the second management entity according to a preset management strategy; the first management entity is used for managing communication services, and the second management entity is used for managing network slice instances. The method of the embodiment can make the management more flexible when using NST, and realize the goal of appropriately opening network information; in addition, communication resources between the first management entity and the second management entity are greatly saved due to the fact that part of the information of the NST can be sent.

Description

Processing method and management equipment of network slice template
Technical Field
The application relates to the technical field of networks, in particular to a processing method and management equipment of a network slice template.
Background
With the rapid development of mobile communication, digital transformation has involved almost all the conventional industries. However, the conventional cellular network architecture can only provide uniform network services, and it is difficult to satisfy the very different communication requirements, including functional differences and performance differences, caused by the digitalized transition wave. In the next Generation mobile network, the network will be abstracted as "network slice", one network slice satisfies the connection communication service requirement of a certain type or one use case, and the whole fifth Generation mobile communication technology (5th-Generation, abbreviated as 5G) system is composed of a large number of network slices satisfying different connection capabilities. A unified network platform, which supports connection communication services with different functions and quality of service (QoS) by using a dynamic and secure network slice, is one of the basic capabilities of a 5G network.
The network slice refers to different logical networks customized according to different service requirements on the basis of physical or virtual network infrastructure. A network slice may be a complete end-to-end network comprising a terminal, an access network, a transport network, a core network and an application server, capable of providing complete telecommunication services, having a certain network capability; a network slice may also be any combination of the above terminals, access networks, transport networks, core networks and application servers. For example, for an access network, the access network may or may not be sliced; the access network may be common to multiple network slices.
A network slice instance (NSI for short) is a real operating logic network and can satisfy certain network characteristics or service requirements. One network slice instance may provide one or more services. The network slice instance can be created by a network management system, and one network management system can create a plurality of network slice instances and manage the network slice instances simultaneously, including performance monitoring, fault management and the like in the operation process of the network slice instances. The NSI is created by a network management system, and one network management system may create a plurality of NSIs and manage the NSIs simultaneously, including performance monitoring, fault management and modification in the operation process of the network slice instance.
However, since the NSI is a real operating logical network, the network construction and management thereof may have multiple network performances and network related parameters, and the network performances and network related parameters of the NSI required by different business entities are different, so the process of creating the NSI is complicated, and the creation may be completed by manually performing a large number of settings.
Disclosure of Invention
The embodiment of the application provides a processing method and management equipment for a network slice template, which simplify the process of creating NSI by using and managing the network slice template.
A first aspect of the embodiments of the present application provides a method for processing a network slice template, in which a first management entity is an entity for managing communication services, that is, an entity that proposes a need to use an NSI; the second management entity is an entity for managing a network slice instance, and can acquire and manage a Network Slice Template (NST); the first management entity receives first NST information sent by the second management entity, where the first NST information is a subset of all information included in the first NST determined by the second management entity according to a preset management policy.
It can be seen that, in the embodiment of the present application, when receiving the information of the NST, the first management entity receives a subset of all information included in the first NST, which is determined by the second management entity according to the preset management policy, that is, according to the preset management policy, the information of the NST acquired by the first management entity is not necessarily all information of one NST, but may be partial information, that is, the second management entity may open the NST information to the first management entity as needed. Therefore, when NST is used, the management is more flexible, and the aim of appropriately opening network information is fulfilled; in addition, communication resources between the first management entity and the second management entity are greatly saved due to the fact that part of the information of the NST can be sent.
With reference to the first aspect of the embodiment of the present application, in a first implementation manner of the first aspect of the embodiment of the present application, the first NST information may specifically be a first NST that is determined by the second management entity first among all NSTs supported by the second management entity, and may be sent to the first management entity, where the first NST may be one or more NSTs, and then a subset of all information included in the first NST is determined according to the open information of the first NST; the NSTs that the second management entity can acquire and manage all have corresponding open information, and for one NST, different open information corresponds to different subsets of all information contained in the NST. Therefore, the NST information can be managed in a distinguishing mode, different parts of the NST information are opened to the first management entity according to the requirement of the first management entity and the network opening strategy, and the NST information management is more flexible and efficient. Specifically, as an example, the opening information of the NST may indicate whether the NST allows opening, which is a part of the content that is allowed to be opened.
In some embodiments, the first management entity has at least one of a corresponding level, type and identification, and the at least one of the level, type and identification of the first management entity has a corresponding relationship with the open information; at this time, the second management entity may determine the opening information of the first NST according to at least one of the class, the type, and the identifier of the first management entity. In this way, the information of the first management entity is associated with the opening information, so that different first management entities may correspond to different opening information of the first NST for the same first NST, so that the received information may be different when different first management entities receive the information of the first NST. Therefore, hierarchical management of the entities requiring network slices, such as the first management entity corresponding to the NST, can be realized, different parts of the information of the NST are opened according to different levels, and the NST is more flexible and effective in management.
In some embodiments, the first NST comprises at least one NST, in which case the method may comprise the first management entity determining a target NST from the at least one NST according to its service requirements and the first NST information; and then the first management sends a first creation request to the second management entity by the target NST, wherein the first creation request uses the second management entity to create the NSI, and the request carries a first identifier for determining the target NST. Namely, the first management entity can select the required NST from different NSTs in the first NST information and send the first creation request according to the selected NST; enabling the second management entity to confirm the corresponding NST according to the first identification and create the corresponding NSI according to the NST.
In some embodiments, the first NST information further carries an adjustable parameter of the first NST and a corresponding parameter adjustment range, and at this time, before the first management entity sends the first creation request to the second management entity, the first management entity determines a parameter value of the adjustable parameter of the target NST according to the adjustable parameter of the first NST and the corresponding parameter adjustment range, and carries the parameter value in the first creation request; that is, some of the information of the first NST are tunable parameters, and the first NST information also carries these tunable parameters, so that the first management entity needs to determine not only the target NST but also the parameter values of the tunable parameters, and the second management entity can create the NSI that meets the requirements of the first management entity according to these parameter values.
In some embodiments, the adjustable parameter of NST is a network characteristic parameter of the NSI created by the second management entity according to the first creation request, where the network characteristic parameter is used to indicate a network characteristic of the NSI and/or a network characteristic of NSSI, and the network characteristic parameter may include at least one of a number of connections, a delay, a bandwidth, and a packet loss rate. These parameters are mainly used to describe the relevant quality of the network.
In some embodiments, the tunable parameter may be a Life Cycle Management (LCM) parameter of the NSI created by the second management entity according to the first creation request, where the life cycle management parameter is an action parameter corresponding to some first actions involved in the operation of the NSI, where the first actions may be actions generated during the lifetime of the NSI, such as creating, activating, modifying, performance monitoring, fault monitoring, deactivating, and terminating, and the action parameter corresponding to the first actions in this embodiment may include the following cases: first, whether a first action is supported; second, the order of execution between the first action and the other actions; thirdly, the specific execution time of the first action, which may be the duration of the execution of the first action or the time when the first action is triggered; fourth, the action parameter may also be a parameter for triggering the first action, i.e. the first action is triggered when the parameter reaches a preset parameter threshold. The management of the NSI is detailed to each action of the life cycle of the NSI, so that the first management entity can carry parameter values of some life cycle management parameters in the creation request on the premise of knowing the life cycle management parameters, and the generated NSI can better correspond to the requirement of the first management entity.
In some embodiments, before the first management entity receives the first NST information sent by the second management entity, the first management entity further sends an acquisition request to the second management entity, where the acquisition request is used to acquire the first NST information.
In some embodiments, after receiving the first NST information, the first management entity sends the first NST information to the NSI subscriber, receives a target NST sent by the NSI subscriber and selected by the NSI subscriber, and may also receive a parameter value of an adjustable parameter determined by the NSI subscriber and corresponding to the target NST selected by the NSI subscriber, and after sending the target NST and the parameter value to the first management entity, the first management entity may send a creation request for creating the NSI to the second management entity according to the target NST or the target NST and the parameter value.
A second aspect of the present embodiment further provides a method for processing a network slice template, where in the method, a second management entity receives a first creation request sent by a first management entity, where the first creation request is used to create an NST, and the first creation request carries an identifier of a second NST; then, the second management entity creates the first NSI according to the second NST corresponding to the identifier, where the second NST is a target NST selected by the second management entity from the obtained NSTs, that is, the second NST is an NST that the second management entity can support.
It can be seen that in the case where the second management entity is capable of supporting the second NST, the first NSI created by the second management entity is created according to the second NST specified by the first management entity, so that, on the one hand, compared to the current manual creation of an NSI, the creation of the first NSI according to the second NST can simplify the creation process of the first NSI, and multiple NSIs of the same type can be created using the same NST. In addition, since the created first NSI is an NST specified by the first management entity (determined by the first management entity itself or by tenant information received by the first management entity), the first NSI better meets the requirements of the first management entity.
In some embodiments, the process of the second management entity creating the first NSI according to the NST corresponding to the identifier of the second NST may be that, first, the second management entity determines, according to the first NST, a Network Slice Subnet Instance (NSSI) included in the first NSI, and for an NSI, the NSI may include at least one NSSI, and thus, the first NSI may include at least one first network slice subnet instance; then, the second management entity sends a second creation request to the third management entity, where the second creation request includes requirement information of the NSSI, and the requirement information enables the third management entity to create the NSSI included in the first NSI according to the requirement information, where the NSSI are NSSI that the third management entity can support.
In some embodiments, the method further comprises the second management entity determining a connection relationship between the NSSIs comprised by said first NSI, by which it can be uniquely determined how the NSSIs constitute an NSI; in this case, the connection relationship is notified to the third management entity in two ways, the first is that the requirement information of the NSSI further includes the connection relationship between the NSSIs included in the first NSI, and the third management entity can acquire the connection relationships after receiving the requirement information; the second is that the second management entity sends a first message to the third management entity, and the first message carries the connection relationship between the NSSIs contained in the first NSI; the first message may be a message sent by the second management entity to the third management entity alone, or the first message may be sent to the third management entity along with the demand information. With this connection relationship, the third management entity can configure the NSSIs according to the connection requirements, so as to form a connection relationship between the NSSIs to form an NSI.
In some embodiments, the second management entity further determines network characteristic parameters of the first NSSI comprised by the first NSI, which may include at least one of a number of connections, a delay, a bandwidth, and a packet loss rate; specifically, the network characteristic parameter of the first NSSI may be carried in the requirement information of the NSSI and sent to the third management entity. With this network characteristic parameter, the third management entity is able to create a more accurate first NSSI.
In some embodiments, the specific process of determining the network characteristic parameter of the first NSSI included in the first NSI by the second management entity is in at least two ways, one of which may be that the second management entity determines the network characteristic parameter of the first NSI according to the network characteristic parameter of the first NSI and a decomposition policy of the network characteristic parameter of the first NSI, where the decomposition policy is used to decompose the network characteristic parameter of the first NSI into at least one network characteristic parameter of the first NSSI; the second management entity may determine to decompose the network characteristic parameter of the first NSI into the network characteristic parameter of the at least one first network slice subnet instance according to the decomposition policy carried in the first NSI template. The resolution policy of the network characteristic parameter may be preset locally at the second management entity or carried directly in the second NST.
In some embodiments, the method may further include determining, by the second management entity, a first Network Slice Subnet Template (NSST) according to the description information of the first NSSI, where the first NST also carries description information of the first NSSI, and the description information includes at least one of an NSSI type, an identifier of the NSST, and a network characteristic parameter of the NSSI, and the second management entity may directly obtain the identifier of the first NSST through the first NST, or determine to select one NSST as the first NSST according to the description information of the first NSSI; the requirement information of the NSSI sent by the second management entity to the third management entity further includes an identifier of the first NSST, or all/part of information of the first NSST.
In some embodiments, the description information includes a network characteristic parameter of the NSSI, and is used as a third way for the second management entity to determine the network characteristic parameter of the NSSI, and the requirement information of the NSSI sent by the second management entity to the third management entity further includes the network characteristic parameter. In some embodiments, the second management entity further generates first NST information according to a preset management policy, where the first NST information includes a subset of all information included in the first NST, where the NST is an NST that the second management entity acquires and can support, and then the second management entity sends the first NST information to the first management entity or the first device, where the first management entity is configured to manage the communication service, and the first device is configured to store the first NST information. It can be seen that the second management entity can selectively provide the first management entity with a subset of all information in the NST supported by the second management entity, which is more flexible in management, and besides, communication resources between the first management entity and the second management entity are greatly saved due to the fact that part of information of the NST can be sent.
In some embodiments, the process of generating, by the second management entity, the first network slice template information according to the preset management policy may be that the second management entity determines, according to the open information of the first NST, a subset of all information included in the first NST; the NST in the second management entity has corresponding open information, and different open information corresponds to different subsets of all information contained in the first NST. For an NST, different open messages correspond to different subsets of the total information contained in the NST. Therefore, the NST information can be managed in a distinguishing mode, different parts of the NST information are opened to the first management entity according to the requirement of the first management entity, or network information is opened moderately according to a local strategy stored by the second management entity, and the NST information management is more flexible and efficient.
In some embodiments, a second management entity determines the opening information of the first network slice template according to at least one of a rank, a type, and an identification of the first management entity, the first management entity having at least one of a corresponding rank, type, and identification; at least one of the level, the type and the identification of the first management entity has a corresponding relationship with the open information. The first management entity has at least one of a corresponding grade, type and identification, and the at least one of the grade, type and identification of the first management entity has a corresponding relation with the open information; at this time, the second management entity may determine the opening information of the first NST according to at least one of the class, the type, and the identifier of the first management entity. In this way, the information of the first management entity is associated with the opening information, so that different first management entities may correspond to different opening information of the first NST for the same first NST, so that the received information may be different when different first management entities receive the information of the first NST. Therefore, hierarchical management of the entities requiring network slices, such as the first management entity corresponding to the NST, can be realized, different parts of the information of the NST are opened according to different levels, and the NST is more flexible and effective in management.
In some embodiments, the first NST includes at least one NST, and the first NST information carries an adjustable parameter of the first NST and a corresponding parameter adjustment range, where the method may further include: a second management entity receives a first creation request sent by a first management entity, where the first creation request carries an identifier of a second network slice template, an adjustable parameter of the second NST and a corresponding parameter value, and the second NST is a target NST determined by the first management entity to be used from at least one NST included in the first NST according to a service requirement of the first management entity and the first NST information. Since the first management entity obtains the tunable parameter of the first NST and the corresponding parameter tuning range through the first NST information, after the first management entity selects the corresponding target NST, the parameter value of the tunable parameter is also determined, so that the second management entity creates an NSI that better meets the requirements of the first management entity.
In some embodiments, the adjustable parameter of the NST is a network characteristic parameter of the network slice instance created by the second management entity according to the first creation request, the network characteristic parameter is used to indicate a network characteristic of the network slice instance and/or a network characteristic of the network slice subnet instance, and the network characteristic parameter may include at least one of latency, bandwidth, and packet loss rate. These parameters are mainly used to describe the relevant quality of the network.
In some embodiments, the tunable parameter may be a lifecycle management parameter of the NSI created by the second management entity according to the first creation request, and the tunable parameter of the NST is a lifecycle management parameter of the network slice instance created by the second management entity according to the first creation request, where the lifecycle management parameter is an action parameter of some first actions involved in the operation of the NSI, where the first actions may be actions generated during the lifetime of the NSI, such as creating, activating, modifying, performance monitoring, fault monitoring, deactivating, and terminating, and the action parameters corresponding to the first actions in this embodiment may include the following cases: first, whether a first action is supported; second, the order of execution between the first action and the other actions; thirdly, the specific execution time of the first action, which may be the duration of the execution of the first action or the time when the first action is triggered; fourth, the action parameter may also be a parameter for triggering the first action, i.e. the first action is triggered when the parameter reaches a preset parameter threshold. The management of the NSI is detailed to each action of the life cycle of the NSI, so that the first management entity can carry parameter values of some life cycle management parameters in the creation request on the premise of knowing the life cycle management parameters, and the generated NSI can better correspond to the requirement of the first management entity.
In some embodiments, before the second management entity sends the first NST information to the first management entity, the method may further include:
and the second management entity receives an acquisition request sent by the first management entity, wherein the acquisition request is used for acquiring the first NST information.
In some embodiments, the method may further comprise:
the second management entity generates first NSI description information and/or a first network slice instance operation record according to the used template information and the created NSI; then, the second management entity stores the identity of the NSI and the corresponding first NSI description information and/or first NSI operation record to the first device. Through the description information and the operation record, the state of the NSI in the existing process and the latest state can be known.
In some embodiments, the method may further comprise: firstly, the second management entity generates second NSI description information and/or a second network slice example operation record according to the current operation state of the NSI at regular intervals or when the operation parameters of the NSI change; then, the second management entity updates the first NSI description information and/or the first network slice instance operation record corresponding to the identification of the NSI in the first device into second NSI description information and/or a second network slice instance operation record.
The third aspect of the present embodiment further provides a method for processing a network slice template, where the method may include:
firstly, a first management entity sends a first reading request to a first device, wherein the first reading request carries an identifier of a second management entity; then, the first management entity obtains the first NST information from the first device, where the first NST information is a subset of all information included in the first NST determined by the second management entity according to a preset management policy and stored on the first device; the first management entity is for managing communication traffic and the second management entity is for managing NSI. The first device is used for storing various types of information sent by the second management entity. The first device is arranged, so that the second management entity can store the information of the first NST information on the first device, when other entities with NSI use requirements need to acquire the relevant information of the NST, the information does not need to be sent to the second management entity, and only the relevant information needs to be acquired from the first device, so that the load of the second management entity is reduced, and communication resources are saved because the process does not need to establish connection with the first management entity.
In some embodiments, the first read request further carries at least one of a level, a type, and an identifier of the first management entity, where the first management entity may specifically acquire the first network slice template information from the first device, and the first management entity acquires the first network slice template information corresponding to at least one of the level, the type, and the identifier of the first management entity from the first device; at least one of the level, the type and the identification of the first management entity has a corresponding relationship with the opening information, the first network slice template has corresponding opening information, and different opening information corresponds to different subsets of all information contained in the first network slice template.
In some embodiments, the first NST includes at least one NST, and the method may further include, first, the first management entity determining a target NST from the at least one NST according to its service requirement and the first NST information; then, the first management entity sends a first creation request to the second management entity, where the first creation request is used to create an NSI, and the first creation request carries a first identifier used to determine the target NST.
In some embodiments, the first NST information carries an adjustable parameter of the first NST and a corresponding parameter adjustment range, and at this time, before the first management entity sends the first creation request to the second management entity, the method may further include, first, the first management entity determines a parameter value of the adjustable parameter of the target NST according to its service requirement, the adjustable parameter of the target NST, and the parameter adjustment range; the first creation request also carries an adjustable parameter and a corresponding parameter value of the target NST.
In some embodiments, the tunable parameter of the NST is a network characteristic parameter of the NSI created by the second management entity according to the first creation request, the network characteristic parameter is used to indicate a network characteristic of the network slice instance and/or a network characteristic of the network slice subnet instance, and the network characteristic parameter may include at least one of a number of connections, a delay, a bandwidth, and a packet loss rate.
In some embodiments, the tunable parameter of the NST is a lifecycle management parameter of the NSI created by the second management entity according to the first creation request, the lifecycle management parameter including an action parameter corresponding to a first action of the NSI, the first action including at least one of creation, activation, modification, performance monitoring, fault monitoring, deactivation, and termination; the action parameters comprise different execution sequences of the first action, execution time of the first action and a first parameter for triggering the first action, wherein the first parameter is used for triggering the first action when the first parameter reaches a preset parameter threshold value.
In some embodiments, the method may further include, first, the first management entity sends a second read request to the first device, where the second read request carries an identifier of the NSI, and the second read request is used to read the NSI description information and/or the NSI operation record of the NSI; the NSI description information and/or the NSI operation record are generated by the second management entity according to the NSI; then, the first management entity reads the stored NSI description information and/or NSI running record corresponding to the NSI in the first device according to the identification of the NSI.
The fourth aspect of the present embodiment also provides a method for processing a network slice template, where the method may include: the first device receives first NST information sent by a second management entity, where the first NST information is a subset of all NSTs acquired by the second management entity, the first NST information has corresponding open information, and different open information of the NST corresponds to different subsets of all information included in the network slice template.
In some embodiments, the method may further include the first device receiving a first read request sent by the first management entity, where the first read request is used to obtain the first NST information, and the first read request carries an identifier of the second management entity; then, the first device determines the first NST information sent to the first management entity according to the identifier of the second management entity and the corresponding open information of the first NST information.
In some embodiments, at least one of the level, the type and the identification of the first management entity has a correspondence with the opening information of the NST, and the method may further include:
the opening information of the NST is determined according to at least one of a class, a type and an identity of the first management entity.
In some embodiments, the method further includes the first device receiving NSI description information and/or an NSI operation record generated by the second management entity according to the information of the created NSI, and the first device further receiving an identification of the NSI.
In some embodiments, the method further includes, first, receiving, by the first device, a second read request sent by the first management entity, where the second read request is used to read NSI description information and/or an NSI operation record of the NSI, and the second read request also carries an identifier of the NSI, and then, the first device determines, according to the NSI and at least one of the class, the type, and the identifier of the first management entity, and sends, to the first device, the NSI description information and/or the NSI operation record generated by information of the NSI.
A fifth aspect of embodiments of the present application further provides a management device, where the management device includes at least one unit configured to execute the processing method for a network slice template provided in the first aspect or any implementation manner of the first aspect.
A sixth aspect of embodiments of the present application further provides a management device, where the management device includes at least one unit configured to execute the processing method for a network slice template provided in the second aspect or any implementation manner of the second aspect.
A seventh aspect of the present embodiment further provides a management device, where the management device includes at least one unit configured to execute the processing method for the network slice template provided in the third aspect or any three implementation manners of the first aspect.
An eighth aspect of embodiments of the present application further provides a storage device, where the storage device includes at least one unit configured to execute the processing method for a network slice template provided in the second aspect or any implementation manner of the second aspect.
Yet another aspect of the present application provides a computer-readable storage medium having stored therein program code, which when executed by a terminal, causes a computer to perform the method of the above-described aspects. The storage medium includes, but is not limited to, a flash memory (flash memory), a Hard Disk Drive (HDD) or a Solid State Drive (SSD).
Yet another aspect of the present application provides a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of the above-described aspects.
Drawings
Fig. 1 is a schematic architecture diagram of a processing method of a network slice template according to an embodiment of the present application;
fig. 2 is a schematic architecture diagram of a processing method of a network slice template according to an embodiment of the present application;
FIG. 3 is a diagram illustrating an embodiment of a method for processing a network slice template according to an embodiment of the present application;
FIG. 4 is a diagram illustrating an embodiment of a method for processing a network slice template according to an embodiment of the present application;
fig. 5 is a schematic diagram illustrating the creation of an NSI in the processing method of the network slice template according to the embodiment of the present application;
FIG. 6 is a diagram illustrating an embodiment of a method for processing a network slice template according to an embodiment of the present application;
FIG. 7 is a diagram illustrating an embodiment of a method for processing a network slice template according to an embodiment of the present application;
FIG. 8 is a diagram of one embodiment of a management device according to an embodiment of the present application;
FIG. 9 is a diagram of one embodiment of a management device according to an embodiment of the present application;
FIG. 10 is a diagram of one embodiment of a memory device of an embodiment of the present application;
FIG. 11 is a diagram of one embodiment of a management device according to an embodiment of the present application;
fig. 12 is a diagram of an embodiment of a memory device according to an embodiment of the present application.
Detailed Description
The embodiment of the application provides a processing method and management equipment for a network slice template, which simplify the process of creating NSI by using and managing the network slice template.
In order to make the technical field better understand the scheme of the present application, the following description will be made on the embodiments of the present application with reference to the attached drawings.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," or "having," and any variations thereof, are intended to cover non-exclusive inclusions, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In a 5G network, one network slice (network slice) meets the requirement of a certain type or one use case of connection communication service, and the 5G network itself is composed of a large number of network slices meeting different connection capabilities, thereby meeting various services, and the service that one network slice can provide can be composed of multiple functions. The network slice itself is a different logical network customized to different service requirements. The network slice can be a complete end-to-end network comprising a terminal, an access network, a transmission network, a core network and an application server, can provide complete telecommunication service and has certain network capacity; the network slice may also be any combination of the above terminals, access networks, transport networks, core networks and application servers. A network slice may have one or more of the following characteristics: the access network may or may not be sliced. The access network may be common to multiple network slices. The characteristics of different network slices and the network functions that make up them may be different.
A Network Function (NF) is a processing function in a network, defines functional behaviors and interfaces, and may be implemented by dedicated hardware, software running on the dedicated hardware, or a virtual function on a general hardware platform. Thus, from an implementation point of view, network functions may be divided into physical network functions and virtual network functions. From the usage perspective, the network functions may be divided into a dedicated network function and a shared network function, and specifically, for a plurality of (sub) network slice instances, different network functions may be independently used, such a network function is referred to as a dedicated network function, and may also share the same network function, such a network function is referred to as a shared network function.
The NSI corresponding to a network slice is a logical network that operates truly and can meet certain network characteristics or service requirements. One network slice instance may provide one or more services. The network slice instance can be created by a network management system, and one network management system can create a plurality of network slice instances and manage the network slice instances simultaneously, including performance monitoring, fault management and the like in the operation process of the network slice instances. When multiple network slice instances coexist, portions of the network resources and network functions may be shared between the network slice instances. The network slice instance may or may not be created from a network slice template. A complete network slice instance is capable of providing a complete end-to-end network service, and what constitutes the network slice instance may be NSSI and/or network functions. The network functions may include physical network functions and/or virtual network functions. In the embodiments of the present application, a physical network function and/or a virtual network function are collectively referred to as a network function.
For creating the NSI, the NSI is generally created by a network management system/network slice management system at present, and one way of creating the NSI is to directly create the NSI according to networking requirements and network resources, and design the structure and network characteristics of the network slice. In order to make the creation process more convenient, one considered feasible way is to generate each NSI one by a manual editing way, or generate a template corresponding to the NSI by a manual editing way to adapt to different types of NSIs, when creating the NSI, the NSI can be quickly created according to the template as long as the template is manually selected, that is, for a type of similar NSI, a model which can be used commonly can be created, and different NSIs can be generated only by setting different parameters of the model, so that the creation process of the NSI can be more convenient. This way of using a common model, that is, NST according to the embodiment of the present application, different NSIs with the same characteristics may be generated according to one NST, and these NSIs may be substantially the same in function, but may be applicable to different network scenarios due to different network characteristics.
Currently, for such a model or template as NST, a default mode is generated manually or selected manually, and an automated management and use process is lacking, and the NST is not defined uniformly at present, so that what content a NST specifically needs to contain, how the NST is specifically used, what entity in a network is used for management, and what entity is used for use, there is no corresponding description. In view of the above, embodiments of the present application provide a processing method, a management device, and a storage device for a network slice template to solve the processing procedure of NST, including a procedure how to generate an NSI using NST, a procedure how to manage NST, and the like.
Referring to fig. 1, a framework for processing NST according to an embodiment of the present application is shown, and fig. 1 is a schematic framework diagram of a processing method of a network slice template according to an embodiment of the present application. Including a first management entity 101 that requires or uses an NSI and a second management entity 102 that manages the NSI. Specifically, the first management entity 101 may use various entities of NSI, and the second entity may be a management entity for managing NSI and supporting some NST. For example, the first management entity 101 may be a Communication Service Management Function (CSMF), and the second management entity 102 may be a Network Slice Management Function (NSMF). The CSMF is mainly responsible for converting communication service requirements of an operator and/or a third party customer into requirements for a network (slicing), sending the requirements for the network slicing (such as creating an NSI request, terminating the NSI request, modifying the NSI request, and the like) to an NSMF through an interface with an entity for managing the NSI, such as the NSMF, acquiring management data (such as performance, fault data, and the like) of the network slicing from the NSMF, generating management data of communication services running on an instance of the network slicing, receiving subscription requirements of the operator and/or the third party customer for the network slicing management data and/or the management data of the communication services, and the like. The NSMF is mainly responsible for receiving the network slice requirement sent by the CSMF, managing the life cycle, performance, and failure of the network slice instance (hereinafter, life cycle, performance, and failure management are simply referred to as management), arranging the composition of the network slice instance, decomposing the requirement of the network slice instance into the requirement of each network slice subnet instance and/or network function, and sending a network slice subnet instance management request to each NSSMF.
In addition, for an example of a network slice, since the network slice may be composed of an NSSI and a network function, when an NSI is generated, a requirement of the NSI needs to be decomposed to obtain an NSSI required for generating the NSI, and then, the NSSI is generated, and then, the combination of the NSSI completes the generation of the NSI. Specifically, referring to fig. 2, fig. 2 is a schematic diagram of an architecture of a method for processing a network slice template according to an embodiment of the present application, which is different from the architecture shown in fig. 1 in that a third management entity 103 is added, where the third management entity 103 is mainly used for managing NSSI, and supports NSSI generation according to NSSTs. For example, the third management entity 103 may be a Network Slice Subnet Management Function (NSSMF), where the NSSMF is mainly responsible for receiving a network slice subnet requirement sent by the NSMF, managing a network slice subnet instance, arranging the components of the network slice subnet instance, decomposing the requirement of the network slice subnet instance into the requirements of each network function and/or a nested network slice subnet instance, and possibly sending a nested network slice subnet instance management request to other NSSMFs.
Furthermore, it should be noted that although the NSI may be composed of a plurality of NSSIs, the life cycles of the NSI and the NSSI are independent, that is, terminating an NSI does not equal to terminating an NSSI, but there is an administrative association between the NSI and the NSSI, for example, creating an NSI may require creating a new NSSI, and modifying an NSI may require modifying an NSSI.
The following describes the content of NST used in the present application, that is, NST description.
The NST in the embodiments of the present application may include various contents, for example, the NST in the embodiments of the present application may include:
1. the NST identifier, which may be a number or a character description, indexes a certain NST, and for the management entity supporting the NST, the corresponding NST may be obtained according to the NST representation.
2. Types of the NSI include various types, such as mass Internet of Things (MIoT), enhanced mobile broadband (eMBB), low latency and high reliability connectivity (URLLC), wttx (wireless to the x), and so on. WTx is a technology for providing home broadband service through a wireless broadband technology, the WTx utilizes a deployed 4G base station, operators do not need to install the WTx at home, users can get terminal equipment at business halls by themselves, and users can enjoy high-speed broadband access service through the 4G base station after going home, so that the operation and maintenance cost is greatly reduced.
NST in the present application may also include the following:
1. constituent of NSI: for example, description information about NSSI (e.g., NSST, NSSI type, network characteristic parameters of NSSI, etc.), description information about NF.
2. Connection relationships between components of NSI: for example, the connection relationship between NSSI and the connection relationship between NF.
3. Characteristics of the NSI (which may also be referred to as attributes, configurations, parameters, etc.): i.e. some network characteristics and related parameters. For example, the bandwidth range supported by the NSI, the data transmission delay (unidirectional, bidirectional) range supported by the NSI, the data transmission reliability range supported by the NSI, and the mobility type supported by the NSI (e.g., the correspondence between the mobility speed and the transmission rate/bandwidth).
4. NSI lifecycle related information: the lifecycle management flow of the NSI includes creation, activation, modification (volume expansion, add/delete function, etc.), logout, termination, etc.; the execution policy of the NSI lifecycle management process, for example: and the activation action is executed after the creation action, whether the expansion and contraction capacity is supported or not is judged, and the expansion and contraction capacity and other information are started after the capacity reaches a certain threshold value.
It should be noted that, part of the information contained in the NST may not be changed, and part may be set. Inherent properties such as the identity, type, etc. of the NSI are not changeable; still other information may be set as desired: the nature (configuration) of the NSI may allow changes, for example, the NST states that the bandwidth range supported by the NSI is < x-y >, and indicates that the parameter is configurable so that it can be configured to a value between x-y, and as another example, the type of mobility supported by the NSI is A, B, C class, and is a by default, but one of the classes may be selected. The life cycle related information of the NS I can set the threshold value of the extended capacity, the time of activation/logoff and the like.
Example 1
Referring to fig. 3, fig. 3 is a diagram of an embodiment of a method for processing a network slice template according to an embodiment of the present application, and as shown in fig. 3, the method includes a first management entity and a second management entity, and the method may include:
301. the first management entity sends a first acquisition request to the second management entity.
The acquiring request is used for acquiring first NST information, the first acquiring request is sent when a first management entity needs to request to create an NSI, and the second management entity is an entity capable of performing NSI management, so that the corresponding first NST information can be acquired by sending the first acquiring request to the second entity. Wherein the first NST information may comprise a subset of the total information for each of the at least one first NST.
It should be noted that the step 301 is only one way for the second management entity to execute the steps 302 and 303, and the second management entity may also determine when to execute the step 302 by itself, for example, the step 302 and the step 303 are executed by itself in the process of initialization after completing networking, that is, the steps are different according to different actual usage scenarios, and whether to execute the step 301 is not limited specifically.
302. And the second management entity generates first NST information according to a preset management strategy.
The first NST information includes a subset of all information of each NST in at least one first NST, and for an NST, all information included in the NST may refer to the description of the NST in the embodiment of the present application. The subset of the total information of an NST may be a part of the total information, or the total information, and may be different according to a policy implemented by the second management entity.
The following describes an embodiment of the present application in which a second management entity generates first NST information according to a preset management policy. In this embodiment of the application, the second management entity aims at the NST that the second management entity can obtain, and the NST that the second management entity can obtain from other entities or networks or directly from its own storage, and these NSTs are all the NSTs that the second management entity can support. For such NST, the second management entity sets corresponding opening information, which means the opening degree of the information that can be given to other NSTs such as the first management entity for the NST. For example, one NST may include 6 kinds of information, information 1, information 2, information 3, information 4, information 5, and information 6, respectively. The open information includes, for example, three types, the first open information corresponds to information 1 and information 2; the second open information corresponds to information 1, information 2, information 3, and information 5; the third open information includes information 1, information 2, information 5, and information 6. It can be seen that for an NST, different open messages can correspond to different subsets of all 6 messages of an NST. For example, the preset management policy of the second management entity is opened according to an open message, that is, in this case, each NST in the first NST message includes only message 1 and message 2. Of course, the second management entity may open the information according to other opening information. The openness information may also indicate that the NST information is not allowed in its entirety, or may be allowed to be opened in its entirety.
For example, the identification of NST included in NST in the embodiment of the present application, the type of NSI, components of NSI, connection relationships between components of NSI, characteristics of NSI, and information related to the life cycle of NSI are taken as examples. The subset of the total information for the NST may be one of a number of cases:
(1) NST identity and NSI type.
(2) NST identity, type of NSI, and NSSI comprised by the NSI.
(3) NST identity, type of NSI, and connection relationship between NSSI and NSSI comprised by the NSI.
(4) NST identity, type of NSI, NSI comprised by the NSI, connection between NSSIs, and characteristics of the NSI.
(5) NST identity, type of NSI, NSI contained by the NSI, connections between NSIs, characteristics of the NSI, and lifecycle management flow information of the NSI.
It should be noted that the above situations are not all situations in the present application, and various information included in the NST in the present application may set corresponding opening information as needed to open different portions of all information, which is not described herein again. In addition, the second management entity may also set a fixed open message to the NST, i.e. the fixed open message is already set from the beginning when the second management entity supports the NST.
Optionally, for the first management entities, each of the first management entities may have at least one parameter among a corresponding level, type, and identifier, and the opening information may further correspond to at least one of the parameters. The level of the first management entity may be determined according to the network in which it is specifically located and the hierarchy in the network, or may be determined by the second management entity; the type of the first management entity is determined, among other things, by the function it has; the identifier of the first management entity is an identifier having a unique correspondence relationship in the second management entity, so that the second management entity can set different open information for different first management entities according to the identifier. In this case, before generating the first NST information, the second management entity may further determine the opening information corresponding to the first management entity, and specifically, before step 302, the method may further include:
the second management entity determines the opening information of the first management entity according to at least one of the grade, the type and the identification of the first management entity.
In this case, in step 302, the opening information of the first network slice template may specifically determine a subset of all information included in the first network slice template.
303. The second management entity sends the first NST information to the first management entity.
After the second management entity generates the first NST information according to the preset management policy, the first NST information is sent to the first management entity.
304. The first management entity sends a first creation request to the second management entity according to the first NST information.
Wherein the first create request is for creating an NSI. The first management entity sends different first creation requests according to different contents contained in the first NST information.
Optionally, the first NST information includes a subset of all information of at least one first NST, that is, the second management entity provides information of a plurality of NSTs to the first management entity; at this point, the step 304 may include:
the first management entity determines a target NST, i.e. one of the multiple NSTs provided by the second management entity, from the first NST included in the first NST information.
The first management entity sends the first creation request to the second management entity, wherein the first creation request comprises the identification of the target NST. Therefore, after receiving the first creation request, the second management entity can find a corresponding network slice template according to the identification of the target NST to create the NSI.
Optionally, since there may be some adjustable parameters and corresponding adjustable parameter ranges in the information included in the NST, the adjustable parameters may be determined by the first management entity, and at this time, the information of the first NST in the first NST information includes the adjustable parameters and the adjustable parameter ranges. In this case, step 304 may specifically be to first determine the target NST from the first NST included in the first NST information;
then, the first management entity determines the parameter value of the adjustable parameter of the target NST according to the adjustable parameter of the target NST and the corresponding adjustable parameter range;
and finally, when the first creation request is generated, carrying the parameter value of the adjustable parameter in the first creation request and sending the parameter value to the second management entity. The second management entity is thus able to create an NSI that is more satisfactory to the first management entity based on these parameter values. The NSI creating efficiency is improved.
It should be noted that, if the parameter values of the adjustable parameters are not set by the first management entity, the second management entity creates the NSI according to the default values.
These adjustable parameters may be, for example, at least one of the following parameters.
(1) Parameters are as follows: mobility support (support mobility), i.e., the speed at which the service provided by the network slice instance can support mobility; the attributes are as follows: can be set; defaulting: 0 km/h; the adjustable range is as follows: 500km/h,100km/h,20km/h, 0 km/h.
(2) Parameters are as follows: number of connections/number of users supported; the attributes are as follows: can be set; defaulting: n; the adjustable range is as follows: n is 2N, and N is a positive integer.
(3) Parameters are as follows: isolating services; the attributes are as follows: can be set; defaulting: non-isolated; the adjustable range is as follows: isolated, not isolated.
(4) Parameters are as follows: a security level; the attributes are as follows: can be set; defaulting: level 1; the adjustable range is as follows: 1 to M, wherein M is an integer.
(5) Parameters are as follows: an NSI total bandwidth; the attributes are as follows: can be set; defaulting: x; the adjustable range is as follows: x to y Mbps, and x and y are positive numbers.
(6) Parameters are as follows: a method of decomposing a Service Level Agreement (SLA) or a Service Level Requirement (SLR) into NSSIs, taking time delay as an example; the attributes are as follows: can be set; defaulting: the Radio Access Network (RAN) portion accounts for 50% plus the Core Network (CN) portion accounts for 50%. The adjustable range is as follows: RAN accounts for 20-80%, CN accounts for 20-80%, and CN plus RAN accounts for 100%.
Optionally, the adjustable parameters may also be adjustable parameters in the lifecycle management parameters, and at this time, the first NST information further includes the lifecycle management parameters and a corresponding adjustable parameter range. When the adjustable parameter is an adjustable parameter in the lifecycle management parameters, the operation performed by the first management entity after receiving the first NST information is similar to the operation of the adjustable parameter, and is not described herein again.
It should be noted that the adjustable parameters in the lifecycle management parameters may be included in the first NST information together with the adjustable parameters, or only the adjustable parameters in the lifecycle management parameters may be included in the first NST without the adjustable parameters in the lifecycle management parameters, or only the adjustable parameters in the lifecycle management parameters without the adjustable parameters.
It should be noted that the lifecycle management parameter is an action parameter corresponding to some first actions involved in the operation of the NSI, where the first actions may be actions generated during the lifetime of the NSI, such as creating, activating, modifying, performance monitoring, fault monitoring, deactivating, and terminating, and the action parameter corresponding to the first actions in this embodiment may include the following cases: first, whether a first action is supported; second, the order of execution between the first action and the other actions; thirdly, the specific execution time of the first action, which may be the duration of the execution of the first action or the time when the first action is triggered; fourth, the action parameter may also be a parameter for triggering the first action, i.e. the first action is triggered when the parameter reaches a preset parameter threshold. The management of the NSI is detailed to each action of the life cycle of the NSI, so that the first management entity can carry parameter values of some life cycle management parameters in the creation request on the premise of knowing the life cycle management parameters, and the generated NSI can better correspond to the requirement of the first management entity.
The action parameters of the creating, activating, modifying, canceling, deactivating and terminating actions of the NSI may be corresponding times, the times may be set by themselves, and the modifying parameters may further include operations of expanding or deleting the NSI or NF in the NSI, or modifying the topology of the NSI. For example, the support of the expansion/contraction capacity may be that the expansion/contraction capacity is performed after the capacity reaches a corresponding threshold value T, which may be set by itself, and the expansion operation may be performed after the capacity reaches the threshold value T if the T is the upper limit value of the capacity, and the reduction operation may be performed after the capacity reaches the threshold value T if the T is the lower limit value of the capacity. A monitoring period and the like may be set for the actions of performance monitoring and failure monitoring. It can be seen that setting the parameters for lifecycle management enables detailed management of the NSI to the actions of the lifecycle of the NSI, so that the first management entity can create the NSI that better meets the requirements of the first management entity on the premise of knowing the lifecycle management parameters.
It should be noted that, in step 304, although the first creation request sent by the first management entity to the second management entity is generated by the first management entity, the target NST included in the first creation request and the parameter value of the tunable parameter that may also be included are not necessarily determined by the first management entity, but are obtained by the first management entity from other NSI users; specifically, the process of acquiring the target NST and the parameter value may be that, after the first management entity sends the first NST information to the other NSI users, the NSI user reads the content in the first NST information, and after determining the target NST or the target NST and the parameter value, feeds back the target NST or the target NST and the parameter value to the first management entity.
For example, in the case of an NSI subscriber being a tenant who wants to purchase an NSI, the tenant is, for example, a virtual operator, and the tenant wants to rent from the operator to a logical network, that is, an NSI, and a management system of the operator may include a first management entity; the specific process may be that, firstly, the tenant notifies the operator that a logical network needs to be leased, then, after acquiring the first NST information, the first management entity of the operator may provide the first NST information to the tenant, and the tenant may select a corresponding target NST from multiple NSTs included in the first NST information according to a target requirement, and meanwhile, if the first NST information further includes an adjustable parameter and an adjustment range of the adjustable parameter, the tenant may determine a parameter value of the adjustable parameter; then, the tenant may send the selected target NST or target NST and the parameter value to the first management entity, and the first management entity may further generate a first creation request according to the target NST or target NST and the parameter value, and send the first creation request to the second management entity to create the NSI.
Example 2
While the use of partial information of all the information of the NST in the processing method of the network slice template according to the embodiment of the present application has been described above, the processing method of the network slice template according to the embodiment of the present application will be described below, and a process of creating an NSI using the NST will be described. In this embodiment, the first management entity and the second management entity are similar to the embodiment shown in fig. 3, that is, the first management entity is a management entity requiring NSI, and the second management entity is an entity for managing NSI and supported NST. Referring to fig. 4, fig. 4 is a diagram illustrating an embodiment of a method for processing a network slice template according to an embodiment of the present application, and as shown in fig. 4, the method may include:
401. the first management entity sends a first create request to the second management entity.
The first creation request includes an NST identifier, where the NST identifier may be a target NST identifier obtained after NST information acquired by a first management entity, and the NST identifier may uniquely identify an NST on a second management entity, so that the second management entity may acquire a corresponding NST according to the NST identifier.
It should be noted that the first creation request may further include the parameter value of the adjustable parameter in the embodiment shown in fig. 3 and/or the parameter value of the adjustable parameter in the lifecycle management parameter. For the setting process of the parameter value of the adjustable parameter and the parameter value of the adjustable parameter in the lifecycle management parameter, refer to the description of step 304 in the embodiment shown in fig. 3, and are not described herein again. These set parameter values are used in the process of creating an NSI by the second management entity in step 402.
402. And the second management entity creates the NSI according to the NST corresponding to the NST identification in the first creation request.
After acquiring the NST identifier from the first creation request, the second management entity searches for the corresponding NST according to the NST identifier, and for the NST identifier, the NST identifier needs to be an NST identifier of an NST that the second management entity can support, and for the NST that the second management entity supports, the second management entity may acquire the NST from its own storage or a network or other devices, and may generate an NSI according to the NST.
It should be noted that the process of creating the NSI according to the NST by the second management entity may include some or all of the following steps. Specifically, the step 402 may include part or all of the steps shown in fig. 5, please refer to fig. 5, fig. 5 is a schematic diagram of creating an NSI in the processing method of the network slice template according to the embodiment of the present application; wherein, this process includes:
501. the second management entity determines the NSSI and/or NF that make up the NSI from the NST and the first create request.
Wherein, for an NSI, the NSI may comprise at least one NSSI, and thus, the first NSI may comprise at least one NSSI, and of course, may also comprise at least one NF, or an NSI may consist of only NFs. In the embodiment of the present application, an example is given in which a component of an NSI includes NSSI.
It should be noted that, in practice, an NSI is composed of a collection of NFs, and thus an NSI includes one or more NFs, while an NSSI is essentially composed of one or more NFs as well. Therefore, after determining the NST and the first creation request, the second management entity may decompose the NSI corresponding to the NST into several NSSIs and/or NFs. After determining the NSSI/NF necessary for forming the NSI, the second management entity may initiate a request for creating the NSSI or reusing the NSSI to the corresponding third management entity, for example, if it is determined that the NSI needs to be formed by the RAN NSSI managed by the 3GPP, the AN NSSI of the non-3 GPP, and the RAN NSSI managed by the 3GPP, the second management entity sends the request to the appropriate third management entity.
502. The second management entity determines the connection relationship between the NSSI and/or NF.
After the second management entity obtains the NST and the first creation request, the connection relationship may be obtained by appropriately decomposing the structure of the NSI, for example, what NSSIs are needed to form a network formed by the RAN and the CN, and what topology the NSSIs are connected to. After the third management entity completes the creation of the NSSI, the connection can be performed in this manner to form the corresponding NSI.
503. The second management entity determines network characteristic parameters for the NSI based on the NST and the first create request.
The types of the network characteristic parameters include various parameters, such as time delay, bandwidth, packet loss rate, mobility support (supported mobility rate, or high, medium, and low mobility), and the network characteristic parameters can correspondingly limit the function and performance of the NSI.
504. The second management entity determines the requirement information for the NSSI.
Wherein, the requirement may include description information of NSSI and/or network characteristic parameter of NSSI; for the second management entity to obtain the description information of the NSSI from the NST, the description information of the NSSI may include one or more of the following items, a type of the NSSI, an identifier of the NSST, or all/part information of the NSST, a network characteristic parameter of the NSSI; the second management entity may generate the requirement information of the NSSI according to the description information of the NSSI.
The generation of the requirement information may specifically include generating one or more of the following aspects:
the second management entity obtains the NSST identifier, or all/part of the NSST information, and the NSST identifier or all/part of the NSST information may be directly included in the NSSI description information of the NST, and the NSSI description information may be directly included in the NST, or may locally perform calculation and selection according to the NSSI description information included in the NST.
It should be noted that, specifically, the second management entity may determine the network characteristic of the NSSI after determining the network characteristic parameter of the NSI and the decomposed NSSI, where the network characteristic parameter of the NSSI needs to be finally combined with the network characteristic parameter of the NSI, so that the network characteristic parameter of the NSSI needs to be determined according to a preset algorithm and a decomposition policy, and the decomposition policy may be included in the NST or may be preset locally. This determination requires that the NSSI be set separately for each parameter. The appropriate NSSI may be selected based on the analyzed network characteristic parameters of the NSSI. For example, the appropriate NSSI is selected based on its capabilities or capacity or bandwidth. For another example, a network characteristic parameter of each NSSI is obtained, which may be, for example, a delay parameter, and if the NSI is decomposed into NSSIs of one RAN and NSSIs of one CN, the delay of the RAN may be required to be 40% of the total delay, and the delay of the CN may be required to be 60% of the total delay. In this case, each NSSI of the RAN is selected according to the delay requirement of the RAN, and each NSSI of the CN is selected according to the delay requirement of the CN, so that the final delay reaches the total delay requirement. For another example, if the network characteristic parameters of each NSSI are directly given in the NST, the above-described decomposition process is not required.
505. The second management entity sends a second creation request to the third management entity.
After determining the connection relationship between the NSSI and the NSSI, the NSST identifier, or all/part of the NSST information and the network characteristic parameter of the NSSI partially or completely through steps 501 to 504, the second management entity generates a second creation request, where the second creation request may send the NSSI type, the connection relationship between the NSSIs, the NSST identifier, or all/part of the NSST information and the network characteristic parameter of the NSSI to the third management entity as the NSSI requirement information.
It should be noted that the requirement information of the NSSI may also directly include the NSST, so that the third management entity may directly extract the NSST from the requirement information to create the NSSI in combination with the description information. Of course, the third management entity may not include NSST, but the third management entity is local to the third management entity according to the description of NSSI, or the third management entity may acquire NSST from a channel where the third management entity can acquire NSST and create NSSI according to the description information of NSST and NSSI.
It should be noted that there are two ways for the connection relationship between the NSSIs to be notified to the third management entity, the first is that the description information of the NSSI further includes the connection relationship between the NSSIs included in the first NSI, and the third management entity can learn the connection relationships after receiving the description information; the second is that the second management entity sends a first message to the third management entity, and the first message carries the connection relationship between the NSSIs contained in the first NSI; the first message may be a message sent by the second management entity to the third management entity alone, or the first message may be sent to the third management entity along with the demand information. With this connection relationship, the third management entity can create the first NSSI more smoothly.
506. The third management entity determines the NSST based on the second creation request.
After receiving the second creation request, the third management entity may directly extract the NSST according to the NSSI requirement information in the second creation request; or selecting an NSST according to the requirement information of the NSSI, for example, matching an appropriate NSST according to the type of the NSSI and the network characteristic parameters of the NSSI; alternatively, the NSSI identification may be obtained from the second create request, by which the NSSTs are obtained from a channel local to the third management entity, or from which the third management entity can obtain NSSTs.
507. The third management entity generates the NSSI according to the description information of the NSST and the NSSI.
After acquiring the NSST and the description information of the NSSI, the third management entity obtains information sufficient for generating the NSSI, and for the NSST that the third management entity can support, that is, the NSST corresponding to the manageable NSSI, the third management entity can generate the corresponding NSSI according to the NSST and the description information of the NSSI.
Example 3
With reference to fig. 6, fig. 6 is a diagram illustrating an embodiment of a method for processing a network slice template according to an embodiment of the present application, where the method includes a first management entity, a second management entity, and a first device; the first management entity is a management entity requiring NSI; the second management entity is a management entity that manages the NSI, and of course, the second management entity also supports some NSTs and can generate the NSI according to the supported NSTs. The first device may actually be a storage device, the first device providing connectivity to other entities requiring NSI, both the other entities requiring NSI and the second management entity, which may access content stored on the first device through connectivity to the first device. The specific process of the second management entity monitoring the running NSI may include:
601. the second management entity generates first NSI description information and/or a first NSI operation record according to the created NSI.
The NSI is an NSI managed by a second management entity, and the second management entity can read various information of the NSI, such as a parameter of a network characteristic of the NSI and a lifecycle management parameter, and for example, various information included in the NST corresponding to the NSI and described in the NST description of the embodiment of the present application. By monitoring the first action and parameters in the lifecycle management parameters, for example, the operation condition of the entire NSI can be determined, and by corresponding the NSI to the content in the NST description, the NSI description information can be determined.
602. And the second management entity stores the identification of the NSI and the corresponding first NSI description information and/or the first NSI operation record to the first equipment.
After the first NSI description information and/or the first NSI operation record is generated, the second management entity stores the identifier of the NSI corresponding to the first NSI description information and/or the first NSI operation record, together with the first NSI description information and/or the first NSI operation record, into the first device, and the identifier of the NSI is associated with the first NSI description information and/or the first NSI operation record. So that a device such as the first management entity can read the first NSI description information and/or the first NSI running record through the identity of the NSI, and thus the situation of the entire life cycle of the NSI can be known.
It should be noted that, while the identity of the NSI and the first NSI description information and/or the first NSI operation record are stored, authentication may also be set according to the setting for the first NST information as in embodiment 1. For example, the first NSI description information and/or the first NSI operation record is set as the opening information, and different opening information may be set for different NSIs; of course, at least one of the type, the identifier, and the level of the first management entity may also be bound with the open information, so that only the first device that conforms to the binding relationship can read the first NSI description information and/or the first NSI running record from the first device.
603. The first management entity sends a first read request to the first device.
The first management entity determines the identity of the NSI after determining the NSI to be read, and then sends the first read request to the first device with the identity of the NSI.
604. The first device sends first NSI description information and/or a first NSI operation record of the corresponding NSI to the first management entity.
After receiving the first read request, the first device searches for corresponding first NSI description information and/or first NSI running record according to the NSI identifier carried in the first read request, and returns the first NSI description information and/or the first NSI running record to the first management entity. Of course, if the first NSI description information and/or the first NSI operation record is authenticated, the open information corresponding to the first management entity needs to be determined first, and only if the open information matches, the first NSI description information and/or the first NSI operation record will be returned to the first management entity.
It should be noted that, for the first device, storing the first NSI description information and/or the first network slice instance operation record corresponding to a certain NSI, the second management entity may also periodically detect the operation state of the NSI, generate the second NSI description information and/or the second network slice instance operation record of the NSI, and send the second NSI description information and/or the second network slice instance operation record to the first device, so as to update the first NSI description information and/or the first NSI operation record on the first device. The NSI description information and/or the NSI operational record for the NSI stored on the first device can be made to reflect the current operational state of the NSI, as well as the previous operational state.
In the case of the example 4, the following examples are given,
the monitoring process of the created NSI according to the embodiment of the present application is described above, and an embodiment of the method for processing the network slice template according to the embodiment of the present application is described below. In this embodiment, different from embodiment 1, a first device is added to a first management entity and a second management entity as an intermediate device, a first NST information generated by the second management entity is not directly sent to the first management entity any more, but is sent to the first device for storage, and then the first management entity reads the first NST information from the first device to generate a first creation request. Specifically, referring to fig. 7, fig. 7 is a diagram illustrating an embodiment of a method for processing a network slice template according to an embodiment of the present application, where a first management entity and a second management entity are both connected to a first device, and the method may include:
701. the second management entity generates first NST information.
The first NST information may include an identifier of the second management entity, and a subset of all information of at least one NST, and for an NST, all information included in the NST may refer to the description of the NST in the embodiment of the present application. The subset of the total information of an NST may be a part of the total information, or the total information, and may be different according to a policy implemented by the second management entity.
Similarly to setting corresponding openness information for the first NST information in step 302 in embodiment 1, the corresponding openness information may be generated for the first NST information in this embodiment. On the other hand, the open information may correspond to a certain parameter of the first management entity, and only the first management entity having a corresponding relationship with the open information may read the first NST information corresponding to the open information corresponding to the first management entity from the first device. And the first management entity which does not correspond to the opening information cannot read the first NST information from the first equipment.
702. The second management entity stores the first NST information to the first device.
After the second management entity completes the generation of the first NST information, the second management entity stores the first NST information to the first device, and associates and stores the first NST information and the identifier of the second management entity.
703. The first management entity sends a first read request to the first device.
Wherein, the first read request carries the identifier of the second management entity. Of course, at least one of the type, level and identity of the first management entity may also be included.
704. The first device sends the first NST information stored by the second management entity to the first management entity.
After receiving the first read request, the first device first obtains an identifier of the second management entity from the first read request, then searches for first NST information corresponding to the identifier in the first device according to the identifier of the second management entity, and sends the first NST information to the first management entity.
It should be noted that before sending the first NST information to the first management entity, the identity of the first management entity may also be verified. The verification method includes the steps of obtaining at least one of the type, the level and the identification of the first management entity, then conducting binding search on the information and the open information bound by the first NST information, determining that the first management entity is legal only if at least one of the type, the level and the identification of the first management entity can correspond to the open information, and sending the first NST information to the first management entity according to the open information.
It should be noted that, after the above steps are completed, steps 501 to 507 shown in fig. 5 in embodiment 2 may be executed to complete the creation of the NSI, and of course, after the creation of the NSI is completed, the step of monitoring the created NSI in embodiment 3 shown in fig. 6 may also be executed.
Example 5
The above describes a method for managing a network slice template according to an embodiment of the present application, and a management apparatus according to an embodiment of the present application is described below. Referring to fig. 8, fig. 8 is a diagram of an embodiment of a management device according to an embodiment of the present application, where the management device is a first management entity in embodiments 1 to 4, and the management device 8 includes:
a transceiver module 801, configured to receive first NST information sent by a second management entity; the first NST information is a subset of all information contained in the first NST determined by the second management entity according to a preset management strategy; the second management entity is for managing NSI.
For specific functions of the first NST information received by the transceiver module 801, reference may be made to the description related to the first NST information in steps 301 to 303 in embodiment 1, which is not described herein again.
It can be seen that, in the embodiment of the present application, when receiving the information of the NST, the first management entity receives a subset of all information included in the first NST, which is determined by the second management entity according to the preset management policy, that is, according to the preset management policy, the information of the NST acquired by the first management entity is not necessarily all information of one NST, but may be partial information, that is, the second management entity may open the NST information to the first management entity as needed. Therefore, when NST is used, the management is more flexible, and the aim of appropriately opening network information is fulfilled; in addition, communication resources between the first management entity and the second management entity are greatly saved due to the fact that part of the information of the NST can be sent.
Optionally, the second management entity is configured to determine a first NST sent to the first management entity, and determine, according to the open information of the first NST, a subset of all information included in the first NST; different open information of the NST can be used to determine different subsets of the total information contained by the NST.
Optionally, the second management entity is further configured to determine the opening information of the first NST according to at least one of a level, a type, and an identifier of the first management entity, where the first management entity has at least one of a corresponding level, a corresponding type, and an identifier; at least one of the level, the type and the identification of the first management entity has a corresponding relation with the open information.
It should be noted that, regarding the first NSTs carried in the first NST information and which part of the NSTs determined by the second management entity, refer to the NST description and the description of embodiment 1 for step 302, which is not described herein again.
Optionally, the first NST includes at least one NST, and the management apparatus further includes:
a processing module 802, configured to determine a target NST from at least one NST according to a service requirement of the processing module and the first NST information;
the transceiver module 801 is further configured to send a first creation request to the second management entity, where the first creation request is used to request the second management entity to create an NSI, and the first creation request carries a first identifier used to determine the target NST.
It should be noted that, for the process of selecting and sending the first creation request, reference may be made to the relevant descriptions in embodiment 1 and embodiment 2, and details are not described here again.
Optionally, the first NST information carries an adjustable parameter of the first NST and a corresponding parameter adjustment range, and the processing module 802 is specifically configured to:
determining the parameter value of the adjustable parameter of the target NST according to the self service requirement and the adjustable parameter and the parameter adjusting range of the target NST; the first creation request also carries an adjustable parameter and a corresponding parameter value of the target NST.
It should be noted that, for the determination process of the adjustment parameter, reference may be made to the relevant description of step 304 in embodiment 1, and details are not described here.
Optionally, the adjustable parameter of the NST is a network characteristic parameter of the NSI created by the second management entity according to the first creation request, where the network characteristic parameter is used to indicate a network characteristic of the NSI and/or a network characteristic of the NSSI, and the network characteristic parameter includes at least one of a connection number, a time delay, a bandwidth, and a packet loss rate.
It should be noted that, the process can refer to the related description of embodiment 1 for step 304, and is not described herein again.
Optionally, the adjustable parameter of the NST is a lifecycle management parameter of the NSI created by the second management entity according to the first creation request, where the lifecycle management parameter is an action parameter corresponding to some first actions involved in the operation of the NSI, where the first actions may be actions generated during the lifetime of the NSI, such as creating, activating, modifying, performance monitoring, fault monitoring, deactivating, and terminating, and the action parameter corresponding to the first actions in this embodiment may include the following cases: first, whether a first action is supported; second, the order of execution between the first action and the other actions; thirdly, the specific execution time of the first action, which may be the duration of the execution of the first action or the time when the first action is triggered; fourth, the action parameter may also be a parameter for triggering the first action, i.e. the first action is triggered when the parameter reaches a preset parameter threshold. The management of the NSI is detailed to each action of the life cycle of the NSI, so that the first management entity can carry parameter values of some life cycle management parameters in the creation request on the premise of knowing the life cycle management parameters, and the generated NSI can better correspond to the requirement of the first management entity.
It should be noted that, the process can refer to the related description of embodiment 1 for step 304, and is not described herein again.
Optionally, the transceiver module 801 is further configured to:
and sending a first acquisition request to the second management entity, wherein the acquisition request is used for acquiring the first NST information.
It should be noted that, the process may refer to the related description of embodiment 1 for step 301, and is not described herein again.
Optionally, the transceiver module 801 sends a first read request to the first device (storage device), where the first read request carries an identifier of the second management entity;
the transceiver module 801 is further configured to acquire the first NST information from the first device, where the first NST information is a subset of all information included in the first NST that is determined by the second management entity according to a preset management policy and is stored in the first device; the first management entity is for managing communication traffic and the second management entity is for managing NSI. The first device is used for storing various types of information sent by the second management entity. The first device is arranged, so that the second management entity can store the information of the first NST information on the first device, when other NSI (non-subsampled aggregation) requiring entities need to acquire the relevant information of the NST, the information does not need to be sent to the second management entity, and only the relevant information needs to be acquired from the first device, so that the load of the second management entity is reduced, and communication resources are saved because the process does not need to establish connection with the first management entity.
Optionally, the first read request further carries at least one of a class, a type, and an identifier of the first management entity, at this time, the transceiver module 801 may specifically acquire the first network slice template information from the first device,
acquiring the first network slice template information corresponding to at least one of a class, a type and an identification of the first management entity from the first device; at least one of the level, the type and the identification of the first management entity has a corresponding relationship with the opening information, the first network slice template has corresponding opening information, and different opening information corresponds to different subsets of all information contained in the first network slice template.
Optionally, the transceiver module 801 is further configured to send a second read request to the first device, where the second read request carries an identifier of an NSI, and the second read request is used to read NSI description information and/or an NSI operation record of the NSI; the NSI description information and/or the NSI operation record are generated by the second management entity according to the NSI; then, the first management entity reads the stored NSI description information and/or NSI running record corresponding to the NSI in the first device according to the identification of the NSI.
Example 6
The method for managing NST according to the embodiment of the present application is described above, and the management apparatus according to the embodiment of the present application is described below. Referring to fig. 9, fig. 9 is a diagram of an embodiment of a management apparatus in an embodiment of the present application, where the management apparatus is a second management entity in embodiments 1 to 4, and the management apparatus 9 includes:
a transceiver module 901, configured to receive a first creation request sent by a first management entity, where the first creation request carries an identifier of a second NST, and the first creation request is used to create an NSI;
a processing module 902, configured to create a first NSI according to a second NST corresponding to the identifier, where the second NST is a target NST selected by the second management entity.
It should be noted that, for the functions of the transceiver module 901 and the processing module 902, reference may be made to fig. 4 and fig. 5 and related descriptions in embodiment 2, and details are not repeated here.
It can be seen that in the case where the second management entity is capable of supporting the second NST, the first NSI created by the second management entity is created according to the second NST specified by the first management entity, so that, on the one hand, compared to the current manual creation of an NSI, the creation of the first NSI according to the second NST can simplify the creation process of the first NSI, and multiple NSIs of the same type can be created using the same NST. In addition, since the created first NSI is the NST specified by the first management entity, the first NSI may better meet the requirements of the first management entity.
Optionally, the processing module 902 is specifically configured to:
determining the NSSI contained in the first NSI according to the first NST, wherein the NSSI contains at least one first NSSI;
and sending a second creation request to a third management entity, wherein the second creation request comprises the requirement information of the NSSI, so that the third management entity creates the NSSI contained in the first NSI according to the requirement information of the NSSI.
It should be noted that, for the relevant functions of the processing module 902, reference may be made to fig. 4 and fig. 5 and the relevant descriptions in embodiment 2, and details are not described here again.
Optionally, the processing module 902 is further configured to:
determining a connection relationship between NSSIs contained in the first NSI;
the requirement information of the NSSI also comprises the connection relation between NSSIs contained in the first NSI; or the like, or, alternatively,
and sending a first message to the third management entity, wherein the first message carries the connection relationship between the NSSIs contained in the first NSI.
It should be noted that, for the relevant functions of the processing module 902, reference may be made to fig. 4 and fig. 5 and the relevant descriptions in embodiment 2, and details are not described here again.
Optionally, the processing module 902 is further configured to:
determining a network characteristic parameter of a first NSSI (network service information) contained in the first NSI, wherein the network characteristic parameter comprises at least one of connection number, time delay, bandwidth and packet loss rate; the requirement information of the NSSI further includes the network characteristic parameter.
It should be noted that, for the relevant functions of the processing module 902, reference may be made to fig. 4 and fig. 5 and the relevant descriptions in embodiment 2, and details are not described here again.
Optionally, the processing module 902 is specifically configured to:
determining a network characteristic parameter of a first NSSI according to the network characteristic parameter of the first NSI and a decomposition strategy of the network characteristic parameter of the first NSI, wherein the decomposition strategy is used for decomposing the network characteristic parameter of the first NSI into at least one network characteristic parameter of the first NSSI;
or the like, or, alternatively,
and determining to decompose the network characteristic parameter of the first NSI into the network characteristic parameter of at least one first network slice subnet according to a decomposition strategy carried in the first NSI template.
It should be noted that, for the relevant functions of the processing module 902, reference may be made to fig. 4 and fig. 5 and the relevant descriptions in embodiment 2, and details are not described here again.
Optionally, the processing module 902 is further configured to:
determining a first NSST according to the description information of the first NSSI, wherein the first NSST carries the description information of the first NSSI, the description information comprises at least one of NSSI type, NSST and network characteristic parameters of NSSI, and the requirement information of the NSSI further comprises the identification of the first NSST.
It should be noted that, for the relevant functions of the processing module 902, reference may be made to fig. 4 and fig. 5 and the relevant descriptions in embodiment 2, and details are not described here again.
Optionally, the description information includes a network characteristic parameter of the NSSI, and the requirement information of the NSSI further includes the network characteristic parameter.
For the description of the description information, reference may be made to fig. 5 and the related description of embodiment 2, which are not repeated herein.
Optionally, the processing module 902 is further configured to:
generating first NST information according to a preset management strategy, wherein the first NST information comprises a subset of all information contained in first NST, and the first NST is NST acquired by the second management entity;
and sending the first NST information to the first management entity or first equipment, wherein the first management entity is used for managing communication services, and the first equipment is used for storing the first NST information.
It should be noted that, for the relevant functions of the processing module 902, reference may be made to fig. 4 and fig. 5 and the relevant descriptions in embodiment 2, and details are not described here again.
Optionally, the processing module 902 is specifically configured to:
determining a subset of all information contained in the first NST according to the open information of the first NST; the NST in the management device has corresponding open information, with different open information corresponding to different subsets of all information contained by the first NST.
It should be noted that, for the relevant functions of the processing module 902, reference may be made to fig. 4 and fig. 5 and the relevant descriptions in embodiment 2, and details are not described here again.
Optionally, the processing module 902 is configured to:
determining the opening information of the first NST according to at least one of the grade, the type and the identification of the first management entity, wherein the first management entity has at least one of the corresponding grade, the type and the identification; at least one of the level, the type and the identification of the first management entity has a corresponding relationship with the open information.
It should be noted that, for the relevant functions of the processing module 902, reference may be made to fig. 4 and fig. 5 and the relevant descriptions in embodiment 2, and details are not described here again.
Optionally, the first NST includes at least one NST, and the transceiver module 901 is specifically configured to:
receiving a first creation request sent by the first management entity, where the first creation request carries an identifier of a second NST, an adjustable parameter of the second NST and a corresponding parameter value, and the second NST is an NST determined by the first management entity from at least one NST included in the first NST according to a service requirement of the first management entity and the first NST information.
It should be noted that, the relevant content of the first creation request can refer to the relevant description in embodiment 1, and is not described herein again.
Optionally, the adjustable parameter of the NST is a network characteristic parameter of the NSI created by the management device according to the first creation request, where the network characteristic parameter is used to indicate a network characteristic of the NSI and/or a network characteristic of the NSSI, and the network characteristic parameter may include at least one of a delay, a bandwidth, and a packet loss rate.
Optionally, the adjustable parameter of the NST is a lifecycle management parameter of the NSI created by the management device according to the first creation request, where the lifecycle management parameter includes an action parameter of a first action corresponding to the NSI, and the first action includes at least one of creation, activation, modification, performance monitoring, fault monitoring, deactivation, and termination; the action parameters comprise different execution sequences of the first action, execution time of the first action and a first parameter for triggering the first action, and the first parameter is used for triggering the first action when the first parameter reaches a preset parameter threshold value.
Optionally, the transceiver module 901 is further configured to:
and receiving an acquisition request sent by the first management entity, wherein the acquisition request is used for acquiring the first NST information.
It should be noted that, for the relevant functions of the transceiver module 901, reference may be made to the relevant description in embodiment 1, and details are not described here again.
Optionally, the processing module 902 is further configured to:
generating first NSI description information and/or NSI operation records according to the created NSI;
and storing the identification of the NSI and the corresponding first NSI description information and/or NSI operation record to the first equipment.
It should be noted that, the relevant functions of the processing module 902 can refer to the relevant descriptions in embodiment 3, and are not described herein again.
Example 7
Having described the management device of the present application, a storage device of an embodiment of the present application is described below, please refer to fig. 10, where fig. 10 is a diagram of an embodiment of a storage device of an embodiment of the present application, and the storage device 10 includes:
a transceiver module 1001, configured to receive first NST information sent by a second management entity, where the first NST information is a subset of all NSTs acquired by the second management entity, the first NST information has corresponding open information, and different open information of the NST corresponds to different subsets of all NSTs included in the NST;
a storage module 1002, configured to store the first NST information.
It should be noted that, for specific functions of the transceiver module 1001 and the storage module 1002, reference may be made to embodiment 4 and related descriptions, and details are not described herein again. It can be seen that, in the embodiment of the present application, similar to the first NST information in embodiment 5, the NST information is not necessarily all information of one NST, but may be partial information, that is, the second management entity may open the NST information to the first management entity as needed. Therefore, when NST is used, the management is more flexible, and the aim of appropriately opening network information is fulfilled; in addition, communication resources between the first management entity and the second management entity are greatly saved due to the fact that part of the information of the NST can be sent.
Optionally, the transceiver module 1002 is further configured to receive a first read request sent by the first management entity, where the first read request is used to obtain the first NST information, and the first read request carries an identifier of the second management entity; then, the first device determines the first NST information sent to the first management entity according to the identifier of the second management entity and the corresponding open information of the first NST information.
It should be noted that specific functions of the transceiver module 1001 may refer to embodiment 4 and related descriptions, which are not described herein again.
Optionally, at least one of the class, the type and the identifier of the first management entity has a corresponding relationship with the open information of the NST, and the storage device 10 further includes an authentication module:
the authentication module 1003 is configured to determine the opening information of the NST according to at least one of the class, the type, and the identifier of the first management entity.
It should be noted that, the authentication process can refer to the description of the process for determining the open information in embodiment 4, and details are not described here.
Optionally, the transceiver module 1001 is further configured to receive NSI description information and/or an NSI operation record generated by the second management entity according to the created information of the NSI, and the transceiver module 1001 further receives an identifier of the NSI and an identifier of the second management entity;
the storage module 1002 is further configured to store the NSI description information and/or the NSI operation record, and an identifier of the corresponding NSI and an identifier of the second management entity.
It should be noted that, for specific functions of the transceiver module 1001, reference may be made to embodiment 3 and related descriptions, which are not described herein again.
Optionally, the transceiver module 1001 is further configured to receive a second read request sent by the first management entity, where the second read request is used to read NSI description information and/or an NSI operation record of the NSI, and the second read request further carries an identifier of the NSI, and then the authentication module 1003 determines, according to the NSI and at least one of the class, the type, and the identifier of the first management entity, open information of the NST, and finally, the transceiver module 1001 sends, to the first device, the NSI description information and/or the NSI operation record generated by the information of the NSI.
It should be noted that, the processing system of the network slice template in the embodiment of the present application may have a plurality of composition manners, where the first composition manner is the composition manner of embodiment 1 or embodiment 2, and the processing system may include two management devices, that is, one management entity for managing the NSI and one management instance requiring the NSI, which may be, for example, a communication service management entity. The second form is that a storage device is added to a management device, the storage device may store first NST information, the first NST information may be first NST information pre-stored in the storage device, or acquired from other devices or networks, and the management device may require a management device of the NSI, such as a communication service management entity. And thirdly, a storage device is added to a management device, which is different from the second one, the management device is a device generating the first NST information, and the management device may store the generated first NST information into the storage device and may add some authentication information such as open information, so that management entities with different NSI requirements can obtain different information. The fourth way, two management entities plus storage, which is a combination of the first three ways, is to complete the process from the generation of the first NST information to the completion of the creation of the NSI using the NST. Of course, in the second and third configurations, in addition to processing the first NST information, the NSI description information and/or the NSI operation record of the ongoing NSI may be processed, the NSI management entity stores the NSI description information and/or the NSI operation record, and the NSI management entity requiring the NSI reads the NSI description information and/or the NSI operation record.
While the storage device of the embodiment of the present application has been described above, the structure of the management device in the embodiment of the present application is described below, please refer to fig. 11, fig. 11 is a diagram of an embodiment of the management device of the embodiment of the present application, where the management device 11 may include at least one processor 1102, at least one transceiver 1101 and a memory 1103 that are connected, the management device 11 related to the embodiment of the present application may have more or less components than those shown in fig. 11, may combine two or more components, or may have different configurations or arrangements of components, and each component may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and/or application specific integrated circuits. For example, the processor 1102, the transceiver 1101, and the memory 1103 may be implemented by a chip.
Specifically, for the embodiment shown in fig. 8, the processor 1102 can implement the functions of the processing module 802 of the management device in the embodiment shown in fig. 8, the transceiver 1101 can implement the functions of the transceiver module 801 of the management device in the embodiment shown in fig. 8, and the memory 1103 is configured to store program instructions, and implement the processing method of the network slicing template in embodiments 1 to 4 by executing the program instructions.
In embodiment 1, the transceiver 1101 is configured to receive a first NST message sent by a second management entity; the first NST information is a subset of all information included in the first NST determined by the second management entity according to a preset management policy, and the second management entity is configured to manage the NSI, where specific functions of the first NST information may refer to descriptions related to the first NST information in steps 301 to 303 in embodiment 1. The transceiver 1101 is further configured to send a first acquisition request to the second management entity, the first acquisition request being used to acquire the first NST information. The transceiver 1101 is further configured to send a first create request to the second management entity based on the first NST information, the first create request being for creating an NSI. The processor 1102 is configured to generate a first create request based on the first NST information.
In embodiment 2, the transceiver 1101 may be configured to send a first creation request to a second management entity. The processor 1102 is accordingly operable to generate the first create request.
In embodiment 3, the transceiver 1101 may be configured to send a first read request to the first device, where the first read request is used to read the first NSI description information and/or the first NSI running record of the NSI; the first read request carries the identity of the NSI. The transceiver 1101 is further configured to receive a first NSI description information and/or a first NSI operation record that the first device sends to the first management entity a corresponding NSI. The processor 1102 is configured to generate the first read request.
In embodiment 4, the transceiver 1101 may be configured to send a first read request to the first device, where the first read request is different from the first read request in embodiment 3 in that the first read request in embodiment 4 is used to read the first NST information, and the first read request further carries an identifier of the second management entity, and may further include at least one of a type, a class, and an identifier of the first management entity. The transceiver 1101 is also operable to receive first NST information stored by the second management entity sent by the first device to the first management entity. The processor 1102 is configured to generate the first read request.
Specifically, for the embodiment shown in fig. 9, the processor 1102 can implement the functions of the processing module 902 of the management device in the embodiment shown in fig. 9, the transceiver 1101 can implement the functions of the transceiver module 901 of the management device in the embodiment shown in fig. 9, and the memory 1103 is configured to store program instructions, and implement the processing method of the network slicing template in embodiments 1 to 4 by executing the program instructions.
In embodiment 1, the transceiver 1101 is configured to issue a first NST message to a first management entity; the first NST information is a subset of all information included in the first NST determined by the second management entity according to a preset management policy, and the second management entity is configured to manage the NSI, where specific functions of the first NST information may refer to descriptions related to the first NST information in steps 301 to 303 in embodiment 1. The transceiver 1101 is also configured to receive a first create request sent by a first management entity to a second management entity, the first create request being for creating an NSI. The processor 1102 is configured to generate the first NST information.
In embodiment 2, the transceiver 1101 is configured to receive a first creation request sent by a first management entity; the processor 1102 is configured to create an NSI according to the NST identifier in the first creation request; the specific creation process of creating an NSI according to NST can be seen in steps 501 to 507 in fig. 5, where steps 501 to 504 are executed by the processor 1102, and step 505 is executed by the transceiver 1101.
In embodiment 3, the transceiver 1101 is configured to store the identity of the NSI and the corresponding first NSI description information and/or first NSI operation record to the first device. The processor 1102 is configured to generate a first NSI description information and/or a first NSI run record based on the created NSI. The description of the first NSI description information and/or the first NSI operation record may refer to the description of step 601 and step 602 in fig. 6.
In embodiment 4, the transceiver 1101 is configured to store the first NST information in the first device. The processor 1102 is configured to generate first NST information. For the specific function of the first NST information, reference may be made to the description related to the first NST information in steps 301 to 303 in embodiment 1.
Having described the management device of the embodiment of the present application, the structure of the storage device in the embodiment of the present application is described below, please refer to fig. 12, fig. 12 is a diagram of an embodiment of the device of the embodiment of the present application, wherein the storage device 11 may include at least one processor 1201, at least one transceiver 1202 and a memory 1203 connected, the device related to the embodiment of the present application may have more or less components than those shown in fig. 12, may combine two or more components, or may have different configurations or arrangements of components, and each component may be implemented in hardware, software or a combination of hardware and software including one or more signal processing and/or application specific integrated circuits. For example, the processor 1201, the transceiver 1202, and the memory 1203 may be implemented in a chip.
Specifically, for the embodiment shown in fig. 10, the processor 1201 can implement the function of the authentication module 1003 of the storage device 10 in the embodiment shown in fig. 10, the transceiver 1202 can implement the function of the transceiver module 1001 of the storage device 10 in the embodiment shown in fig. 10, and the memory 1203 is used for storing program instructions, and the processing method of the network slicing template in embodiments 3 and 4 is implemented by executing the program instructions.
In embodiment 3, the processor 1201 is configured to determine, according to a first read request sent by a first management entity, to send first NSI description information and/or a first NSI running record of a corresponding NSI to the first management entity. The transceiver 1201 is configured to receive a first read request sent by a first management entity. The transceiver 1201 is further configured to send first NSI description information and/or a first NSI operation record of a corresponding NSI to the first management entity. The memory 1203 is used for storing the identity of the NSI sent by the second management entity to the transceiver 1101 and the corresponding first NSI description information and/or first NSI operation record.
In embodiment 4, the processor 1201 is configured to determine, according to a first read request sent by a first management entity, to send, to the first management entity, first NST information stored by a second management entity. The transceiver 1201 is configured to receive a first read request sent by a first management entity. The transceiver 1201 is also configured to send the first NST information stored by the second management entity to the first management entity. The memory 1203 is used for storing the first NST information generated by the second management entity and sent to the transceiver 1101.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, 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 loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims (38)

1. A method for processing a network slice template is characterized by comprising the following steps:
a first management entity receives first network slice template information sent by a second management entity; the first network slice template information is a subset of all information contained in a first network slice template determined by the second management entity according to a preset management strategy; the first management entity is used for managing communication services, and the second management entity is used for managing network slice instances;
the preset management policy is the opening information of the first management entity, and the opening information of the first management entity is determined according to at least one parameter in the grade, the type or the identification corresponding to the first management entity;
the first network slice template information is partial information of all information included in the first network slice template.
2. The method of processing a network slice template of claim 1, wherein the first network slice template comprises at least one network slice template, the method further comprising:
the first management entity determines a target network slice template from at least one network slice template according to the self service requirement and the first network slice template information;
the first management entity sends a first creation request to the second management entity, where the first creation request is used to request the second management entity to create a network slice instance, and the first creation request carries a first identifier used to determine the target network slice template.
3. The method for processing the network slice template of claim 1 or 2, wherein before the first management entity receives the first network slice template information sent by the second management entity, the method further comprises:
and the first management entity sends an acquisition request to the second management entity, wherein the acquisition request is used for acquiring the first network slice template information.
4. A method for processing a network slice template is characterized by comprising the following steps:
a second management entity receives a first creation request sent by a first management entity, wherein the first creation request carries an identifier of a second network slice template, and the first creation request is used for creating a network slice instance;
the second management entity creates a first network slice example according to a second network slice template corresponding to the identifier, wherein the second network slice template is a target network slice template selected by the second management entity;
before the second management entity receives the first creation request, the second management entity sends first network slice template information to the first management entity, wherein the first network slice template information is a subset of all information contained in a first network slice template determined by the second management entity according to a preset management policy, the first network slice template information comprises a subset of all information contained in the second network slice template, the first management entity is used for managing communication services, and the second management entity is used for managing network slice instances;
the preset management policy is the opening information of the first management entity, and the opening information of the first management entity is determined according to at least one parameter in the grade, the type or the identification corresponding to the first management entity;
the first network slice template information is partial information of all information included in the first network slice template.
5. The method for processing the network slice template of claim 4, wherein the second management entity creating the first network slice instance according to the network slice template corresponding to the identifier of the second network slice template comprises:
the second management entity determines the network slice subnet instances contained in the first network slice instances according to the first network slice template, wherein the network slice subnet instances at least contain one first network slice subnet instance;
and the second management entity sends a second creation request to a third management entity, wherein the second creation request comprises the requirement information of the network slice subnet instance, so that the third management entity creates the network slice subnet instance contained in the first network slice instance according to the requirement information of the network slice subnet instance.
6. The method of processing a network slice template of claim 5, further comprising:
the second management entity determines the connection relation between the network slice subnet instances contained in the first network slice instance;
the requirement information of the network slice subnet instances also comprises the connection relation among the network slice subnet instances contained in the first network slice instance; or the like, or, alternatively,
and the second management entity sends a first message to the third management entity, wherein the first message carries the connection relationship between the network slice subnet instances contained in the first network slice instance.
7. The method of processing a network slice template of claim 5, further comprising:
the second management entity determines a network characteristic parameter of a first network slice subnet instance contained in the first network slice instance, wherein the network characteristic parameter comprises at least one of connection number, time delay, bandwidth and packet loss rate;
the requirement information of the network slice subnet instance also comprises the network characteristic parameter.
8. The method of processing the network slice template of claim 7, wherein the determining, by the second management entity, the network characteristic parameters of the first network slice subnet instance included in the first network slice instance comprises:
the second management entity determines the network characteristic parameters of the first network slice subnet instance according to the network characteristic parameters of the first network slice instance and a decomposition strategy of the network characteristic parameters of the first network slice instance, wherein the decomposition strategy is used for decomposing the network characteristic parameters of the first network slice instance into at least one network characteristic parameter of the first network slice subnet instance;
or the like, or, alternatively,
and the second management entity determines to decompose the network characteristic parameters of the first network slice example into the network characteristic parameters of at least one first network slice subnet according to the decomposition strategy carried in the first network slice example template.
9. The method of processing a network slice template of claim 5, further comprising:
the second management entity determines a first network slice subnet template according to the description information of the first network slice subnet instance, the first network slice template carries the description information of the first network slice subnet instance, the description information includes at least one of a type of the network slice subnet instance, the network slice subnet template and a network characteristic parameter of the network slice subnet instance, and the requirement information of the network slice subnet instance further includes an identifier of the first network slice subnet template.
10. The method for processing the network slice template of claim 9, wherein the description information comprises network characteristic parameters of the network slice subnet instances, and the requirement information of the network slice subnet instances further comprises the network characteristic parameters.
11. The method of processing a network slice template of any of claims 5 to 10, the method further comprising:
the second management entity generates the first network slice template information according to a preset management strategy, wherein the first network slice template information comprises a subset of all information contained in a first network slice template, and the first network slice template is a network slice template acquired by the second management entity;
and the second management entity sends the first network slice template information to the first management entity or first equipment, wherein the first management entity is used for managing communication services, and the first equipment is used for storing the first network slice template information.
12. The method for processing the network slice template of claim 1 or 11, wherein the second management entity generating the first network slice template information according to the preset management policy comprises:
the second management entity determines a subset of all information contained in the first network slice template according to the opening information of the first network slice template; the network slice template in the second management entity has corresponding open information, and different open information corresponds to different subsets of all information contained in the first network slice template.
13. The method of processing a network slice template of claim 12, the method further comprising:
the second management entity determines the opening information of the first network slice template according to at least one of the grade, the type and the identification of the first management entity, and the first management entity has at least one of the corresponding grade, the type and the identification; at least one of the level, the type and the identification of the first management entity has a corresponding relationship with the open information.
14. The method for processing the network slice template according to any one of claims 11 to 13, wherein the first network slice template includes at least one network slice template, and the first network slice template information carries adjustable parameters and corresponding parameter adjustment ranges of the first network slice template, the method further comprising:
the second management entity receives a first creation request sent by the first management entity, wherein the first creation request carries an identifier of a second network slice template, an adjustable parameter of the second network slice template and a corresponding parameter value, and the second network slice template is a network slice template determined by the first management entity from at least one network slice template included in the first network slice template according to self service requirements and the first network slice template information.
15. The method according to claim 2 or 14, wherein the adjustable parameter of the network slice template is a network characteristic parameter of the network slice instance created by the second management entity according to the first creation request, the network characteristic parameter is used to indicate a network characteristic of the network slice instance and/or a network characteristic of a network slice subnet instance, and the network characteristic parameter may include at least one of latency, bandwidth and packet loss rate.
16. The method for processing the network slice template of claim 2 or 14, wherein the adjustable parameter of the network slice template is a lifecycle management parameter of the network slice instance created by the second management entity according to the first creation request, the lifecycle management parameter includes an action parameter corresponding to a first action of the network slice instance, the first action includes at least one of creation, activation, modification, performance monitoring, fault monitoring, deactivation and termination; the action parameters comprise different execution sequences of the first action, execution time of the first action and a first parameter for triggering the first action, and the first parameter is used for triggering the first action when the first parameter reaches a preset parameter threshold value.
17. The method for processing network slice templates of any of claims 11 to 15, wherein before the second management entity sends the first network slice template information to the first management entity, the method further comprises:
and the second management entity receives an acquisition request sent by the first management entity, wherein the acquisition request is used for acquiring the first network slice template information.
18. The method of processing a network slice template of any of claims 11 to 17, the method further comprising:
the second management entity generates first network slice instance description information and/or network slice instance operation records according to the created network slice instances;
and the second management entity stores the identification of the network slice instance and the corresponding first network slice instance description information and/or network slice instance operation record to the first device.
19. A management device, acting as a first management entity, the first management entity comprising:
the receiving and sending module is used for receiving first network slice template information sent by a second management entity; the first network slice template information is a subset of all information contained in a first network slice template determined by the second management entity according to a preset management strategy; the second management entity is used for managing the network slice instance;
the preset management policy is the opening information of the first management entity, and the opening information of the first management entity is determined according to at least one parameter in the grade, the type or the identification corresponding to the first management entity;
the first network slice template information is partial information of all information included in the first network slice template.
20. The management device of claim 19, wherein the first network slice template comprises at least one network slice template, the management device further comprising:
the processing module is used for determining a target network slice template from at least one network slice template according to the self service requirement and the first network slice template information;
the transceiver module is further configured to send a first creation request to the second management entity, where the first creation request is used to request the second management entity to create a network slice instance, and the first creation request carries a first identifier used to determine the target network slice template.
21. The management device according to claim 19 or 20, wherein the transceiver module is further configured to:
and sending an acquisition request to the second management entity, wherein the acquisition request is used for acquiring the first network slice template information.
22. A management device, acting as a second management entity, the second management entity comprising:
a transceiver module, configured to receive a first creation request sent by a first management entity, where the first creation request carries an identifier of a second network slice template, and the first creation request is used to create a network slice instance;
the processing module is used for creating a first network slice example according to a second network slice template corresponding to the identifier, wherein the second network slice template is a target network slice template selected by the second management entity;
the transceiver module is further configured to send first network slice template information to the first management entity, where the first network slice template information is a subset of all information included in a first network slice template determined by the second management entity according to a preset management policy, the first network slice template information includes a subset of all information included in the second network slice template, the first management entity is configured to manage a communication service, and the second management entity is configured to manage a network slice instance;
the preset management policy is the opening information of the first management entity, and the opening information of the first management entity is determined according to at least one parameter in the grade, the type or the identification corresponding to the first management entity;
the first network slice template information is partial information of all information included in the first network slice template.
23. The management device according to claim 22, wherein the processing module is specifically configured to:
determining the network slice subnet instances contained in the first network slice instance according to the first network slice template, wherein the network slice subnet instances at least contain one first network slice subnet instance;
and sending a second creation request to a third management entity, wherein the second creation request comprises the requirement information of the network slice subnet instance, so that the third management entity creates the network slice subnet instance contained in the first network slice instance according to the requirement information of the network slice subnet instance.
24. The management device of claim 23, wherein the processing module is further configured to:
determining a connection relationship between the network slice subnet instances contained in the first network slice instance;
the requirement information of the network slice subnet instances also comprises the connection relation among the network slice subnet instances contained in the first network slice instance; or the like, or, alternatively,
and sending a first message to the third management entity, wherein the first message carries the connection relationship between the network slice subnet instances contained in the first network slice instance.
25. The management device of claim 23, wherein the processing module is further configured to:
determining a network characteristic parameter of a first network slice subnet instance contained in the first network slice instance, wherein the network characteristic parameter comprises at least one of connection number, time delay, bandwidth and packet loss rate; the requirement information of the network slice subnet instance also comprises the network characteristic parameter.
26. The management device according to claim 25, wherein the processing module is specifically configured to:
determining the network characteristic parameters of the first network slice subnet instance according to the network characteristic parameters of the first network slice instance and a decomposition strategy of the network characteristic parameters of the first network slice instance, wherein the decomposition strategy is used for decomposing the network characteristic parameters of the first network slice instance into the network characteristic parameters of at least one first network slice subnet instance;
or the like, or, alternatively,
and determining to decompose the network characteristic parameters of the first network slice example into the network characteristic parameters of at least one first network slice subnet according to a decomposition strategy carried in the first network slice example template.
27. The management device of claim 23, wherein the processing module is further configured to:
determining a first network slice subnet template according to the description information of the first network slice subnet instance, wherein the first network slice template carries the description information of the first network slice subnet instance, the description information includes at least one of a type of the network slice subnet instance, the network slice subnet template and a network characteristic parameter of the network slice subnet instance, and the requirement information of the network slice subnet instance further includes an identifier of the first network slice subnet template.
28. The management device of claim 27, wherein the description information includes network characteristic parameters of the network slice subnet instance, and the requirement information of the network slice subnet instance further includes the network characteristic parameters.
29. The management device according to any of claims 22 to 28, wherein the processing module is further configured to:
generating the first network slice template information according to a preset management strategy, wherein the first network slice template information comprises a subset of all information contained in a first network slice template, and the first network slice template is a network slice template acquired by the second management entity;
and sending the first network slice template information to the first management entity or first equipment, wherein the first management entity is used for managing communication services, and the first equipment is used for storing the first network slice template information.
30. The management device according to claim 19 or 29, wherein the processing module of the second management entity is specifically configured to:
determining a subset of all information contained in the first network slice template according to the opening information of the first network slice template; the network slice template in the management device has corresponding open information, and different open information corresponds to different subsets of all information contained in the first network slice template.
31. The management device according to claim 30, wherein the processing module of the second management entity is configured to:
determining opening information of the first network slice template according to at least one of a grade, a type and an identification of the first management entity, wherein the first management entity has at least one of a corresponding grade, type and identification; at least one of the level, the type and the identification of the first management entity has a corresponding relationship with the open information.
32. The management device according to any of claims 29 to 31, wherein the first network slice template comprises at least one network slice template, and the transceiver module is specifically configured to:
receiving a first creation request sent by the first management entity, where the first creation request carries an identifier of a second network slice template, and an adjustable parameter and a corresponding parameter value of the second network slice template, and the second network slice template is a network slice template determined by the first management entity according to its own service requirement and the first network slice template information from at least one network slice template included in the first network slice template.
33. The management device according to claim 20 or 32, wherein the adjustable parameter of the network slice template is a network characteristic parameter of a network slice instance created by the management device according to the first creation request, the network characteristic parameter is used to indicate a network characteristic of the network slice instance and/or a network characteristic of a network slice subnet instance, and the network characteristic parameter may include at least one of latency, bandwidth and packet loss rate.
34. The management device according to claim 20 or 32, wherein the adjustable parameter of the network slice template is a lifecycle management parameter of a network slice instance created by the management device according to the first creation request, the lifecycle management parameter includes an action parameter corresponding to a first action of the network slice instance, the first action includes at least one of creating, activating, modifying, performance monitoring, fault monitoring, deactivating, and terminating; the action parameters comprise different execution sequences of the first action, execution time of the first action and a first parameter for triggering the first action, and the first parameter is used for triggering the first action when the first parameter reaches a preset parameter threshold value.
35. The management device according to any of claims 29 to 34, wherein the transceiver module is further configured to:
and receiving an acquisition request sent by the first management entity, wherein the acquisition request is used for acquiring the first network slice template information.
36. The management device according to any one of claims 29 to 35, wherein the processing module is further configured to:
generating first network slice instance description information and/or network slice instance operation records according to the created network slice instances;
and storing the identification of the network slice instance and the corresponding first network slice instance description information and/or network slice instance operation record to the first device.
37. A system for processing a network slice template, comprising a management device according to any one of claims 19 to 21 and a management device according to any one of claims 22 to 36.
38. A computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method of processing a network slice template as claimed in any one of claims 1-3 or 4-18.
CN201710847660.7A 2017-09-19 2017-09-19 Processing method and management equipment of network slice template Active CN109525409B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201710847660.7A CN109525409B (en) 2017-09-19 2017-09-19 Processing method and management equipment of network slice template
PCT/CN2018/106018 WO2019057011A1 (en) 2017-09-19 2018-09-17 Method for processing network slice template, and management device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710847660.7A CN109525409B (en) 2017-09-19 2017-09-19 Processing method and management equipment of network slice template

Publications (2)

Publication Number Publication Date
CN109525409A CN109525409A (en) 2019-03-26
CN109525409B true CN109525409B (en) 2021-07-20

Family

ID=65768533

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710847660.7A Active CN109525409B (en) 2017-09-19 2017-09-19 Processing method and management equipment of network slice template

Country Status (2)

Country Link
CN (1) CN109525409B (en)
WO (1) WO2019057011A1 (en)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11444835B2 (en) * 2019-09-06 2022-09-13 Wipro Limited System and method of maintenance of network slice templates for slice orchestration
CN110753277B (en) * 2019-10-24 2022-01-04 烽火通信科技股份有限公司 Method and system for configuration management in OLT network slice
CN111555911B (en) * 2020-04-23 2022-09-30 北京思特奇信息技术股份有限公司 5G network slicing product rapid design method based on product service template
CN117118841A (en) * 2020-06-28 2023-11-24 中兴通讯股份有限公司 Network slice connection management method, terminal and computer readable storage medium
CN114051279A (en) * 2020-07-23 2022-02-15 华为技术有限公司 Service processing method and network equipment
CN114071657A (en) * 2020-07-31 2022-02-18 中移(苏州)软件技术有限公司 Network slice processing method and device and storage medium
AU2020462418A1 (en) * 2020-08-06 2023-03-16 Huawei Technologies Co., Ltd. Access network management and configuration method, system and apparatus
CN114640580A (en) * 2020-12-15 2022-06-17 ***通信有限公司研究院 NSSI (network spanning and shrinking) capacity expansion and contraction method for network slice subnet example and related equipment
CN112819054B (en) * 2021-01-25 2023-06-30 中国联合网络通信集团有限公司 Method and device for configuring slicing template

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102891789B (en) * 2011-07-20 2015-08-05 北京华为数字技术有限公司 VPN (virtual private network) exemplary configuration method and device, router and network system
JP2018517340A (en) * 2015-06-01 2018-06-28 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． System and method for virtualized functions in control plane and data plane
US10644955B2 (en) * 2015-08-21 2020-05-05 Huawei Technologies Co., Ltd. Method and apparatus for network slicing
US10129108B2 (en) * 2015-11-13 2018-11-13 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing
CN106713406B (en) * 2015-11-18 2020-01-24 ***通信集团公司 Method and system for accessing slice network
CN106998338A (en) * 2016-01-22 2017-08-01 中兴通讯股份有限公司 A kind of method and device for realizing VNF deployment
CN107040481A (en) * 2016-02-04 2017-08-11 中兴通讯股份有限公司 A kind of network section system of selection, strategy-generating method and network node
CN106412905A (en) * 2016-12-12 2017-02-15 中国联合网络通信集团有限公司 Network slice selection method, UE, MME and system
CN106792692B (en) * 2016-12-27 2019-11-05 兴唐通信科技有限公司 A kind of physics dicing method based on SDN technology

Also Published As

Publication number Publication date
CN109525409A (en) 2019-03-26
WO2019057011A1 (en) 2019-03-28

Similar Documents

Publication Publication Date Title
CN109525409B (en) Processing method and management equipment of network slice template
US10827421B2 (en) Network slice selection method, user equipment, and network device
CN108282352B (en) Method, device and system for managing network slice instances
CN109600768B (en) Method, device and system for managing network slices
US10791507B1 (en) Facilitating reservation and use of remote radio units (RRUs) of radio providers for mobile service providers in virtualized radio access network (vRAN) environments
CN110447208B (en) Network slice management method, unit and system
US11425225B2 (en) Method, apparatus, and equipment for exposing edge network capability, and storage medium
KR102144430B1 (en) Method for selecting mobile network operator using provisioning profile and apparatus using the method
CN105162748B (en) The processing of electronic user identification module application identifier
US20170366972A1 (en) Terminal device having subscriber identity device and method for selecting profile thereof
EP3827554A1 (en) Methods and apparatus for providing information associated with network function (nf) instances of a 5g mobile network
CN110326345B (en) Method, device and system for configuring network slice
CN111436160A (en) Local area network communication method, device and system
CN109391498B (en) Management method of network component and network equipment
CN110226308B (en) Network slice management method, management unit and system
CN109787803B (en) Method and device for managing shared network function
CN109547231B (en) Network slice management method and device
CN105340306A (en) Provisioning wireless subscriptions using software-based subscriber identity modules
CN112449315A (en) Network slice management method and related device
CN104902547A (en) WiFi (wireless fidelity) network connection method and WiFi network connection device
CN109314696B (en) Method and device for managing network slices
US20110295947A1 (en) Communication apparatus and method thereof
JP2017528074A (en) Establishing and setting up dynamic subscriptions
CN108632848B (en) Network slice self-optimization coordination method and device
CN112087779A (en) Network slice priority management method, device and system and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant