CN116418669A - Processing method of network slice, network element and storage medium - Google Patents
Processing method of network slice, network element and storage medium Download PDFInfo
- Publication number
- CN116418669A CN116418669A CN202111659100.1A CN202111659100A CN116418669A CN 116418669 A CN116418669 A CN 116418669A CN 202111659100 A CN202111659100 A CN 202111659100A CN 116418669 A CN116418669 A CN 116418669A
- Authority
- CN
- China
- Prior art keywords
- network slice
- network
- modification
- slice
- nsi
- 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.)
- Pending
Links
- 238000003860 storage Methods 0.000 title claims abstract description 14
- 238000003672 processing method Methods 0.000 title abstract description 8
- 230000004048 modification Effects 0.000 claims abstract description 229
- 238000012986 modification Methods 0.000 claims abstract description 229
- 238000000034 method Methods 0.000 claims abstract description 70
- 238000012545 processing Methods 0.000 claims abstract description 19
- 230000004044 response Effects 0.000 claims description 42
- 238000004590 computer program Methods 0.000 claims description 11
- 230000008569 process Effects 0.000 claims description 11
- 230000001960 triggered effect Effects 0.000 abstract description 15
- 238000012423 maintenance Methods 0.000 abstract description 3
- 238000004458 analytical method Methods 0.000 description 30
- 238000010586 diagram Methods 0.000 description 14
- 230000006870 function Effects 0.000 description 12
- 238000000354 decomposition reaction Methods 0.000 description 10
- 230000008859 change Effects 0.000 description 9
- 238000009826 distribution Methods 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
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/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- 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/0803—Configuration setting
- H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
-
- 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/12—Discovery or management of network topologies
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Lift-Guide Devices, And Elevator Ropes And Cables (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a processing method of a network slice, a network element and a storage medium, comprising the following steps: the method comprises the steps that a first network element receives a first message, wherein the first message is used for indicating modification of network slice requirements; the first network element decides to perform a corresponding network management operation. The invention provides a technical scheme for increasing network management or operation and maintenance flows triggered by service level protocol modification or update, provides a processing technical scheme for network management triggered by user demand modification in aspects of network slice modification, network slice reassignment and management of up-and-down pipes, and integrates the original flows of modification, assignment and the like.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method for processing a network slice, a network element, and a storage medium.
Background
The prior art has the following defects: only basic network slice allocation flow and network slice modification flow are defined in the existing technical scheme.
Disclosure of Invention
The invention provides a processing method of a network slice, a network element and a storage medium, which are used for solving the problem of missing a network slice processing flow triggered by modification.
The invention provides the following technical scheme:
a method of processing a network slice, comprising:
the method comprises the steps that a first network element receives a first message, wherein the first message is used for indicating modification of network slice requirements;
the first network element decides to perform a corresponding network management operation.
In practice, deciding to perform the corresponding network management operation includes:
modifying the network slice; and/or the number of the groups of groups,
network slice allocation.
In practice, the method further comprises:
if the modification of the existing network slice can meet the new network slice related requirements, the modification of the existing network slice is performed.
In practice, the method further comprises:
if the modification of the existing network slice cannot meet the related requirements of the new network slice and the existing network slice is not shared by other services, terminating the existing network slice and distributing the new network slice; and/or the number of the groups of groups,
if the modification of an existing network slice fails to meet the new network slice related requirements and the existing network slice is shared by other services, then the new network slice is allocated.
In implementations, the first message is a network slice related requirement including a generic network slice template GST.
In practice, the method further comprises:
After receiving the first message, obtaining a new service profile from the network slice related requirements;
and according to the new service description file, determining to execute corresponding network management operation.
In practice, deciding to perform the corresponding network management operation includes:
it is decided to perform a modification and/or allocation of the network slice instance NSI and/or the network slice subnet instance NSI.
In an implementation, a network slice modification includes:
the first network element sends a second message, wherein the second message comprises an identification of an NSI to be modified and a modification operation of the NSI to be modified; and/or the first network element receives the second response.
In an implementation, network slice allocation includes:
the first network element sends a third message, wherein the third message is used for representing that a new slice is allocated; and/or the number of the groups of groups,
the first network element receives the third response.
In practice, the third response further includes identification information of the newly allocated NSI.
In practice, the method further comprises:
the first network element sends a first response, which is a modified response of the network slice requirement.
A network element, comprising:
a processor for reading the program in the memory, performing the following process:
Receiving a first message, wherein the first message is used for indicating modification of network slice requirements;
determining to execute corresponding network management operation;
and a transceiver for receiving and transmitting data under the control of the processor.
In practice, deciding to perform the corresponding network management operation includes:
modifying the network slice; and/or the number of the groups of groups,
network slice allocation.
In practice, the method further comprises:
if the modification of the existing network slice can meet the new network slice related requirements, the modification of the existing network slice is performed.
In practice, the method further comprises:
if the modification of the existing network slice cannot meet the related requirements of the new network slice and the existing network slice is not shared by other services, terminating the existing network slice and distributing the new network slice; and/or the number of the groups of groups,
if the modification of an existing network slice fails to meet the new network slice related requirements and the existing network slice is shared by other services, then the new network slice is allocated.
In implementations, the first message is a network slice related requirement including a generic network slice template GST.
In practice, the method further comprises:
after receiving the first message, obtaining a new service profile from the network slice related requirements;
And according to the new service description file, determining to execute corresponding network management operation.
In practice, deciding to perform the corresponding network management operation includes:
it is decided to perform a modification and/or allocation of the network slice instance NSI and/or the network slice subnet instance NSI.
In an implementation, a network slice modification includes:
transmitting a second message, wherein the second message comprises an identification of an NSI to be modified and a modification operation of the NSI to be modified; and/or receiving a second response.
In an implementation, network slice allocation includes:
transmitting a third message, the third message being indicative of allocation of a new slice; and/or the number of the groups of groups,
a third response is received.
In practice, the third response further includes identification information of the newly allocated NSI.
In practice, the method further comprises:
and sending a first response, wherein the first response is a modified response of the network slice requirement.
A network element, comprising:
a receiving module, configured to receive a first message, where the first message is used to indicate modification of a network slice requirement;
and the execution module is used for deciding to execute corresponding network management operation.
In implementation, the execution module is further configured to, when determining to perform the corresponding network management operation, include:
Modifying the network slice; and/or the number of the groups of groups,
network slice allocation.
In practice, the execution module is further configured to modify the existing network slice if the modification of the existing network slice can meet the new network slice related requirements.
In implementation, the execution module is further configured to terminate the existing network slice and allocate the new network slice if the modification of the existing network slice fails to meet the new network slice related requirements and the existing network slice is not shared by other services; and/or the number of the groups of groups,
if the modification of an existing network slice fails to meet the new network slice related requirements and the existing network slice is shared by other services, then the new network slice is allocated.
In implementations, the first message is a network slice related requirement including a generic network slice template GST.
In an implementation, the receiving module is further configured to obtain a new service profile from the network slice related requirement after receiving the first message;
the execution module is further configured to determine to execute a corresponding network management operation according to the new service description file.
In implementation, the execution module is further configured to, when determining to perform the corresponding network management operation, include:
It is decided to perform a modification and/or allocation of the network slice instance NSI and/or the network slice subnet instance NSI.
In an implementation, the execution module is further configured to, when the network slice is modified, include:
transmitting a second message, wherein the second message comprises an identification of an NSI to be modified and a modification operation of the NSI to be modified; and/or receiving a second response.
In an implementation, the execution module is further configured to, when allocating the network slice, include:
transmitting a third message, the third message being indicative of allocation of a new slice; and/or the number of the groups of groups,
a third response is received.
In practice, the third response further includes identification information of the newly allocated NSI.
In an implementation, the execution module is further configured to send a first response, the first response being a modified response of the network slice requirement.
A method of processing a network slice, comprising:
the method comprises the steps that a first network element receives a network slice demand modification request sent by a user;
after the first network element analyzes the network slice demand modification request, triggering corresponding operation according to the analysis result.
In practice, the triggering of the corresponding operation is as follows:
triggering network slice modification; or alternatively, the first and second heat exchangers may be,
triggering network slice allocation.
In practice, the network slice requirement modification request triggers a network slice modification when it requests modification of one or a combination of the following:
Network capacity, network topology, network configuration, network performance parameters, and traffic demands.
In practice, the network slice requirement modification request is embodied by the user's network slice requirement template GST.
In practice, network slice allocation is triggered when a network slice demand modification request results in a final network topology or a final network deployment change.
In an implementation, a network slice modification includes:
the modified requirements are modified after corresponding to corresponding ServiceProfile parameters, or the modified is performed after generating new ServiceProfile parameters based on new network slice requirements;
the demand decomposition is performed based on the relevant parameters and is embodied in the modification of the whole NSI network slice instance and NSSI sub-network slice instance.
In an implementation, a network slice modification includes:
the method comprises the steps that a first network element determines a network slice parameter request to be modified, wherein the parameter request is determined by a management identifier of NSI carried in a network slice demand modification request Modifi sent by a second network element and a new network slice demand;
the first network element determines whether the parameter request can be modified through a feasibility check program;
when the parameter request can be modified, decomposing the parameter request into NSSI modification requests;
The first network element carries out NSSI modification in a third network element role;
the first network element sends the NSI modification result to the second network element;
and when the NSI can not be modified, the first network element transmits the NSI modification result to the second network element.
In an implementation, network slice allocation includes:
reuse existing network slices or newly created network slices.
In practice, further comprising:
when an existing network slice instance is modified to be able to meet new network slice requirements, the existing network slice is reused by modifying the existing network slice instance.
In practice, when an existing network slice instance does not contribute to other network services, the network slice instance is newly created after terminating the existing network slice instance.
In an implementation, after reusing an existing network slice or a newly created network slice, further comprising:
when reusing the existing network slice or newly-built network slice successfully, the first network element informs the user of a successful result or management identification of a network slice instance NSI; or, the first network element informs the user of the failure result when reusing the existing network slice or newly creating the network slice fails.
In an implementation, network slice allocation includes:
the method comprises the steps that a first network element determines a network slice parameter request to be modified, wherein the parameter request is determined by a management identifier of NSI carried in a network slice demand modification request AllocateNSi sent by a second network element and a new network slice demand;
The first network element determines to reuse the existing network slice or newly-built network slice according to the parameter request and the existing deployment network slice capability;
if the existing network slice is reused, the first network element requests the calling program to modify NSI according to the parameters;
if a network slice is newly established, the first network element performs NSSI distribution after determining the network slice subnet requirement according to the parameter request;
the first network element creates MOI for NSI and configures DN of MOI for NSSI;
the first network element sends the NSI allocation result to the second network element.
In practice, further comprising:
the modification result sent by the first network element to the second network element comprises relevant network slice instance information if the existing NSI is modified or a new NSI is successfully created.
A network element, comprising:
a processor for reading the program in the memory, performing the following process:
receiving a network slice demand modification request sent by a user;
after analyzing the network slice demand modification request, triggering corresponding operation according to an analysis result;
and a transceiver for receiving and transmitting data under the control of the processor.
In practice, the triggering of the corresponding operation is as follows:
triggering network slice modification; or alternatively, the first and second heat exchangers may be,
triggering network slice allocation.
In practice, the network slice requirement modification request triggers a network slice modification when it requests modification of one or a combination of the following:
Network capacity, network topology, network configuration, network performance parameters, and traffic demands.
In practice, the network slice requirement modification request is embodied by the user's network slice requirement template GST.
In practice, network slice allocation is triggered when a network slice demand modification request results in a final network topology or a final network deployment change.
In an implementation, a network slice modification includes:
the modified requirements are modified after corresponding to corresponding ServiceProfile parameters, or the modified is performed after generating new ServiceProfile parameters based on new network slice requirements;
the demand decomposition is performed based on the relevant parameters and is embodied in the modification of the whole NSI network slice instance and NSSI sub-network slice instance.
In an implementation, a network slice modification includes:
determining a network slice parameter request to be modified, wherein the parameter request is determined by a management identifier of an NSI carried in a network slice demand modification request ModifyNSi sent by a second network element and a new network slice demand;
determining, by a feasibility check program, whether the parameter request can be modified;
when the parameter request can be modified, decomposing the parameter request into NSSI modification requests;
Performing NSSI modification in a third network element role;
transmitting the NSI modification result to a second network element;
and when the NSI modification is not possible, transmitting an NSI modification result to the second network element.
In an implementation, network slice allocation includes:
reuse existing network slices or newly created network slices.
In practice, further comprising:
when an existing network slice instance is modified to be able to meet new network slice requirements, the existing network slice is reused by modifying the existing network slice instance.
In practice, when an existing network slice instance does not contribute to other network services, the network slice instance is newly created after terminating the existing network slice instance.
In an implementation, after reusing an existing network slice or a newly created network slice, further comprising:
when reusing the existing network slice or newly-built network slice successfully, the first network element informs the user of a successful result or management identification of a network slice instance NSI; or, the first network element informs the user of the failure result when reusing the existing network slice or newly creating the network slice fails.
In an implementation, network slice allocation includes:
determining a network slice parameter request to be modified, wherein the parameter request is determined by a management identifier of an NSI carried in a network slice demand modification request AllocateNSi sent by a second network element and a new network slice demand;
Determining to reuse an existing network slice or a newly built network slice according to the parameter request and the existing deployment network slice capability;
if the existing network slice is reused, requesting a calling program to modify NSI according to the parameters;
if a network slice is newly built, NSSI distribution is carried out after the network slice subnet requirement is determined according to the parameter request;
creating MOI for NSI and configuring DN of MOI for NSSI;
and sending the NSI allocation result to the second network element.
In practice, further comprising:
the modification result sent to the second network element includes relevant network slice instance information if the existing NSI is modified or a new NSI is successfully created.
A network element, comprising:
the receiving module is used for receiving a network slice demand modification request sent by a user;
and the analysis triggering module is used for triggering corresponding operation according to the analysis result after analyzing the network slice demand modification request.
In implementation, the analysis triggering module is further configured to trigger the corresponding operation to:
triggering network slice modification; or alternatively, the first and second heat exchangers may be,
triggering network slice allocation.
In implementations, the analysis triggering module is further configured to trigger the network slice modification when the network slice requirement modification request is requesting modification of one or a combination of the following:
Network capacity, network topology, network configuration, network performance parameters, and traffic demands.
In an implementation, the receiving module is further configured to receive a network slice requirement modification request embodied by the network slice requirement template GST of the user.
In practice, the analysis triggering module is further configured to trigger the network slice allocation when the network slice requirement modification request causes a final network topology or a final network deployment change.
In an implementation, the analysis triggering module is further configured to trigger a network slice modification, including:
the modified requirements are modified after corresponding to corresponding ServiceProfile parameters, or the modified is performed after generating new ServiceProfile parameters based on new network slice requirements;
the demand decomposition is performed based on the relevant parameters and is embodied in the modification of the whole NSI network slice instance and NSSI sub-network slice instance.
In an implementation, the analysis triggering module is further configured to trigger a network slice modification, including:
determining a network slice parameter request to be modified, wherein the parameter request is determined by a management identifier of an NSI carried in a network slice demand modification request ModifyNSi sent by a second network element and a new network slice demand;
Determining, by a feasibility check program, whether the parameter request can be modified;
when the parameter request can be modified, decomposing the parameter request into NSSI modification requests;
performing NSSI modification in a third network element role;
transmitting the NSI modification result to a second network element;
and when the NSI modification is not possible, transmitting an NSI modification result to the second network element.
In an implementation, the analysis triggering module is further configured to trigger network slice allocation, including:
reuse existing network slices or newly created network slices.
In implementations, the analysis triggering module is further configured to reuse an existing network slice by modifying the existing network slice instance when the modification of the existing network slice instance is capable of meeting new network slice requirements.
In an implementation, the analysis triggering module is further configured to create a new network slice instance after terminating the existing network slice instance when the existing network slice instance does not contribute to other network services.
In implementation, the analysis triggering module is further used for notifying the user of a successful result or a management identifier of the network slice instance NSI when the reuse of the existing network slice or the newly-built network slice is successful after the reuse of the existing network slice or the newly-built network slice; or, the first network element informs the user of the failure result when reusing the existing network slice or newly creating the network slice fails.
In an implementation, the analysis triggering module is further configured to trigger network slice allocation, including:
determining a network slice parameter request to be modified, wherein the parameter request is determined by a management identifier of an NSI carried in a network slice demand modification request AllocateNSi sent by a second network element and a new network slice demand;
determining to reuse an existing network slice or a newly built network slice according to the parameter request and the existing deployment network slice capability;
if the existing network slice is reused, requesting a calling program to modify NSI according to the parameters;
if a network slice is newly built, NSSI distribution is carried out after the network slice subnet requirement is determined according to the parameter request;
creating MOI for NSI and configuring DN of MOI for NSSI;
and sending the NSI allocation result to the second network element.
In practice, the analysis triggering module is further configured to trigger that the modification result sent to the second network element comprises relevant network slice instance information if the existing NSI is modified or a new NSI is successfully created.
A computer readable storage medium storing a computer program which when executed by a processor implements the method of processing a network slice as described above.
The invention has the following beneficial effects:
in the technical solution provided in the embodiments of the present invention, since the execution of the corresponding network management operation is determined according to the modification of the network slicing requirement, the technical solution for increasing the network management or operation and maintenance flow triggered by the modification or update of the SLA (service level agreement ) is provided.
Furthermore, the processing technical scheme of network management triggered by user demand modification in aspects of network slice modification, network slice reassignment and management of line and line management is provided, and the original processes of modification, assignment and the like are integrated.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and do not constitute a limitation on the invention. In the drawings:
FIG. 1 is a schematic diagram of a flow chart of an embodiment of a method for processing a network slice;
FIG. 2 is a second flow chart of an embodiment of a method for processing a network slice;
FIG. 3 is a schematic diagram of a network slice requirement modification process according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a network element structure in an embodiment of the present invention;
Fig. 5 is a schematic diagram of a network element structure in the embodiment of the present invention.
Detailed Description
The inventors noted during the course of the invention that:
the modification to NSI (network slice instance ) in the currently existing solutions only involves the implementation method, and specific network slice flows triggered by user demand modification are not discussed.
And network management triggered by user demand modification not only relates to network slice modification, but also can have network slice reassignment and online and offline management, so the current existing technical scheme is in a missing state.
Based on this, the embodiment of the present invention provides a technical solution for adding a network management or operation and maintenance procedure triggered by modification or update of SLA (service level agreement ), and the following description of the specific embodiments of the present invention will be given with reference to the accompanying drawings.
In the description, the description will be made from the implementation of the plurality of network element sides, respectively, and then an example of their cooperation implementation will be also given to better understand the implementation of the scheme given in the embodiment of the present invention. Such description does not mean that they must be carried out in cooperation or must be carried out separately, in fact, they each solve the problem on their own side when they are carried out separately, while they are used in combination with better technical results.
FIG. 1 is a schematic flow diagram of an implementation of a processing method of a network slice, which may include:
In particular, the first network element may be a service provider, or NFFMF (network management function, network fuction management fuction), or NSSMF (sub-network slice management function, network slice subnet management fuction), or NSMF (network slice management function, network slice management fuction).
In practice, deciding to perform the corresponding network management operation includes:
modifying the network slice; and/or network slice allocation.
In practice, it may further comprise:
if the modification of the existing network slice can meet the new network slice related requirements, the modification of the existing network slice is performed.
In practice, it may further comprise:
if the modification of the existing network slice cannot meet the related requirements of the new network slice and the existing network slice is not shared by other services, terminating the existing network slice and distributing the new network slice; and/or the number of the groups of groups,
If the modification of an existing network slice fails to meet the new network slice related requirements and the existing network slice is shared by other services, then the new network slice is allocated.
In an implementation, the first message is one or a combination of the following:
network capacity, network topology, network configuration, network performance parameters, and traffic demands.
Specifically, the first message may be a change to the user, for example, adding a UPF (user plane function ). The Provider, i.e. the first network element, maps the requirements in the first message into a service profile, i.e. generates a new service profile. The service profile has a plurality of parameters, and the first network element judges whether the slice currently providing the service for the user can meet the requirement according to each parameter in the new service profile. For example, a bandwidth item in the new service profile is 12G, the bandwidth of the slice currently providing the service for the user is set to 10G, but the capability of the UPF can reach 12G, and the slice is modified directly, and the result of modifying the slice is represented by expanding the network capacity. Network capacity, network topology, network configuration, network performance parameters, and traffic demands are one result of implementation of the modified/newly allocated slices after judgment.
In implementations, the first message is a network slice related requirement including GST (generic slice template ).
In practice, it may further comprise:
after receiving the first message, obtaining a new service profile (service profile) from the network slice related requirements;
and according to the new service description file, determining to execute corresponding network management operation.
Specifically, the resulting process may include: and extracting key information from the related requirements, filling the key information into the values of the corresponding parameters in the service profile according to the key information, and generating a new service profile after filling.
In practice, deciding to perform the corresponding network management operation includes:
it is decided to perform a modification and/or allocation of the network slice instance NSI and/or the network slice subnet instance NSI.
In an implementation, a network slice modification includes:
the first network element sends a second message, wherein the second message comprises an identification of an NSI to be modified and a modification operation of the NSI to be modified; and/or the first network element receives the second response.
Specifically, the second response is used for indicating that the modification is successful and/or the modification is failed;
NSI is composed of one or more NSIs. The transmitted request carries the NSI identification and the corresponding modification operation, and the final modified object is NSSI.
In an implementation, network slice allocation includes:
the first network element sends a third message, wherein the third message is used for representing that a new slice is allocated; and/or the number of the groups of groups,
the first network element receives the third response.
In particular, the third response is used to indicate that the slice allocation was successful and/or failed.
In practice, the third response further includes identification information of the newly allocated NSI.
In practice, it may further comprise:
the first network element sends a first response, which is a modified response of the network slice requirement.
Specifically, when reusing the existing network slice or newly-built network slice successfully, notifying the user of a successful result or management identification of the network slice instance NSI; and/or, the first network element informs the user of the failure result when reusing the existing network slice or newly-built network slice fails.
Fig. 2 is a second schematic flow chart of an implementation of a processing method of a network slice, which may include:
In practice, the triggering of the corresponding operation is as follows:
triggering network slice modification; or alternatively, the first and second heat exchangers may be,
Triggering network slice allocation.
In particular, an end-to-end oriented network slice service client may actively initiate updates or changes to network SLA requirements at any time, the end result of which may include, but is not limited to, the following classes:
directly modifying the existing network slice;
the existing slice is taken off line, and a new network slice is allocated;
existing slices are taken offline and existing/existing network slices are reused.
In practice, the network slice requirement modification request triggers a network slice modification when it requests modification of one or a combination of the following:
network capacity, network topology, network configuration, network performance parameters, and traffic demands.
In practice, the network slice requirement modification request is embodied by the user's network slice requirement template GST.
Specifically, a user initiates a request for network slice demand modification: the modification can be the modification of network capacity, network topology, network configuration and other related modification requirements, network related performance parameters or service requirements and the like; further, the corresponding modification may also be embodied in the network slice requirement template GST (generic slice template ) of the user.
In practice, network slice allocation is triggered when a network slice demand modification request results in a final network topology or a final network deployment change.
Specifically, if the modification requirement affects aspects such as final network topology or network deployment, the network slice needs to be reassigned to the modified network slice requirement.
In an implementation, a network slice modification includes:
the modified requirements are modified after corresponding to corresponding ServiceProfile parameters, or the modified is performed after generating new ServiceProfile parameters based on new network slice requirements;
the demand decomposition is performed based on the relevant parameters and is embodied in the modification of the whole NSI network slice instance and NSSI sub-network slice instance.
Specifically, for modification of network related performance parameters or service requirements (such as the maximum number of access users, etc.), the first network element (such as nsms_provider) first corresponds the modified requirements to corresponding ServiceProfile parameter modifications, then performs requirement decomposition based on the related parameters and reflects the requirement decomposition into modifications for the whole NSI network slice instance and NSSI (network slice subnet instance ) sub-network slice instance.
In an implementation, a network slice modification includes:
the method comprises the steps that a first network element determines a network slice parameter request to be modified, wherein the parameter request is determined by a management identifier of NSI carried in a network slice demand modification request Modifi sent by a second network element and a new network slice demand;
The first network element determines whether the parameter request can be modified through a feasibility check program;
when the parameter request can be modified, decomposing the parameter request into NSSI modification requests;
the first network element carries out NSSI modification in a third network element role;
the first network element sends the NSI modification result to the second network element;
and when the NSI can not be modified, the first network element transmits the NSI modification result to the second network element.
In an implementation, network slice allocation includes:
reuse existing network slices or newly created network slices.
In a specific implementation, the method further comprises:
when an existing network slice instance is modified to be able to meet new network slice requirements, the existing network slice is reused by modifying the existing network slice instance.
In practice, when an existing network slice instance does not contribute to other network services, the network slice instance is newly created after terminating the existing network slice instance.
Specifically, if modifying an existing network slice instance can meet the new network slice requirement, modifying the existing network slice instance;
if the existing network slice instance is not contributed by other network services, the existing network slice instance is terminated. Then, newly creating a new network slice instance;
In an implementation, after reusing an existing network slice or a newly created network slice, further comprising:
when reusing the existing network slice or newly-built network slice successfully, the first network element informs the user of a successful result or management identification of a network slice instance NSI; or, the first network element informs the user of the failure result when reusing the existing network slice or newly creating the network slice fails.
Specifically, the user may be informed of the completion of the modification procedure through a response. After all flows are completed, information of the network slice instance, such as management identification of the network slice instance NSI, may be notified.
Specifically, the network slice instance de-allocation and allocation flow is triggered. In the network slice allocation flow, there are two options of using an existing network slice and re-instantiating a new network slice.
If the de-allocation and allocation flow needs to be triggered, in the flow of judging whether to reuse the existing network slice or newly-built network slice, the de-allocation is needed according to the modification requirement, for example, if the user accepts network sharing and the existing network slice of the current network can serve the network sharing, the re-use is selected, and the ServiceProfile of the original slice is unchanged; if the user does not accept the network sharing or the network slice requirement modification involves a huge change of the network topology, a new network slice creation process needs to be executed to construct a new ServiceProfile.
In an implementation, network slice allocation includes:
the method comprises the steps that a first network element determines a network slice parameter request to be modified, wherein the parameter request is determined by a management identifier of NSI carried in a network slice demand modification request AllocateNSi sent by a second network element and a new network slice demand;
the first network element determines to reuse the existing network slice or newly-built network slice according to the parameter request and the existing deployment network slice capability;
if the existing network slice is reused, the first network element requests the calling program to modify NSI according to the parameters;
if a network slice is newly established, the first network element performs NSSI distribution after determining the network slice subnet requirement according to the parameter request;
the first network element creates MOI for NSI and configures DN of MOI for NSSI;
the first network element sends the NSI allocation result to the second network element.
In a specific implementation, the method may further include:
the modification result sent by the first network element to the second network element comprises relevant network slice instance information if the existing NSI is modified or a new NSI is successfully created.
The following description is made with reference to an example, where specific implementation network elements corresponding to each network element are as follows:
a first network element: nsms_p (network slice management service provider );
A second network element: nsms_c (network slice management service consumer );
third network element: nssms_c (network slice subnet management service consumer );
fourth network element: nfms_p (network function entity management service provider, network Function Management Service Provider).
FIG. 3 is a schematic flow diagram of an implementation of the network slice demand modification process, which may include:
1. the user initiates a demand modification request.
A user initiates a request for network slice demand modification: the modification may be a modification requirement related to network capacity, network topology, network configuration, etc. Further, the corresponding modification may also be embodied in the network slice requirement template GST of the user.
2. Analyzing/translating user requests, judging network solutions, selecting 1: triggering a network slice modification flow, selecting 2: triggering network slice de-allocation and allocation flow.
Nsms_provider analyzes or translates the network slice requirement modification request, determines and triggers the relevant network flows. If the modification requirement only affects network-related capacity or network configuration, then network slice modification can be satisfied; if the modification requirement affects aspects of the final network topology or network deployment, etc., then the network slices need to be reassigned to the modified network slice requirements.
3a, scheme 1: triggering a modified Network Slice (NSI) modification procedure;
and updating Service Profile and modifying Network Slice (NSI) flow.
If scheme 1 is adopted, triggering a network slice instance modification flow:
for the modification of network related performance parameters or service requirements (such as the maximum access user number, etc.), the NSMS_provider firstly corresponds to the modification of corresponding ServiceProfile parameters, then carries out the requirement decomposition based on the related parameters, and reflects the requirement decomposition into the modification of the whole NSI network slice example and NSSI sub-network slice example;
the internal flow may be as follows:
a) The network slice management service provider (nsms_p) receives a modification NSI request from the network slice management service consumer (nsms_c) containing a management identifier of the NSI and new network slice related requirements.
b) Based on the new network slice related requirements, nsms_p invokes the feasibility check program. If the modification requirement can be met, go to step c), otherwise go to step e).
c) The sms_p breaks up the NSI modification request into NSSI modification requests, i.e., generates new network slice subnet related requirements for each NSSI as needed.
d) Nsms_p, as a role of network slice subnet management service consumer (nssms_c), invokes the NSSI modification procedure.
e) Nsms_p sends the NSI modification result to nsms_c.
And 3b, triggering network slice de-allocation and allocation flow.
Network Slice (NSI) de-allocation procedure;
network Slice (NSI) allocation procedure, newly created or reused Service Profile.
If scheme 2 is adopted, triggering network slice instance de-allocation and allocation flow. In the network slice allocation flow, there are two options of using an existing network slice and re-instantiating a new network slice.
If the de-allocation and allocation flow needs to be triggered, in the flow of judging whether to reuse the existing network slice or newly-built network slice, the de-allocation is needed according to the modification requirement, for example, if the user accepts network sharing and the existing network slice of the current network can serve the network sharing, the re-use is selected, and the ServiceProfile of the original slice is unchanged; if the user does not accept the network sharing or the network slice requirement modification involves a huge change of the network topology, a new network slice creation process needs to be executed to construct a new ServiceProfile.
The internal flow may be as follows:
a) The network slice management service Provider (nsms_provider) receives an AllocateNsi (allocation NSI) request from a network slice management service Consumer (nsms_consumer) with network slice related requirements.
b) Nsms_provider compares/matches the provided requirements with all candidate NetworkSlice instances based on the network slice related requirements and knowledge of the existing deployment network slice capabilities, and then decides whether to use the existing NSI or create a new NSI. If the network slice related requirements allow the requested NSI to be shared, and if the existing appropriate NSI can be reused, then NSMS _ Provider may decide to use the existing NSI.
c) If an existing NSI is used and needs to be modified to meet network slice related requirements, then the nsms_provider caller modifies the existing NSI.
d) If a new NSI is created, NSMS_Provider derives network slice subnet related requirements from the received network slice related requirements. The nsms_provider may invoke a corresponding network slice subnet capability information query procedure before the nsms_provider derives network slice subnet related requirements.
e) Nsms_provider invokes the NSSI allocation procedure.
f) Nsms_provider creates an MOI (management object instance, manage Object Instance) for the NSI and configures the DN (Data Network) of the MOI for the NSI, but may also configure other configuration information (embodied in a specific NRM (Network resource management, networkResource Management)) for the created MOI.
g) Nsms_provider sends the NSI allocation result to nsms_consumer. If an existing NSI is modified or a new NSI is successfully created to meet the network slice related requirements, the result includes related network slice instance information.
Based on the same inventive concept, the embodiment of the invention also provides a network element and a computer readable storage medium, and because the principle of solving the problems of the devices is similar to that of processing network slices, the implementation of the devices can refer to the implementation of the method, and the repetition is omitted.
In implementing the technical scheme provided by the embodiment of the invention, the method can be implemented as follows.
Fig. 4 is a schematic diagram of a network element, where as shown in the drawing, the network element includes:
the processor 400 is configured to read the program in the memory 420, and execute the following procedures:
receiving a network slice demand modification request sent by a user;
after analyzing the network slice demand modification request, triggering corresponding operation according to an analysis result;
a transceiver 410 for receiving and transmitting data under the control of the processor 400.
In practice, the triggering of the corresponding operation is as follows:
triggering network slice modification; or alternatively, the first and second heat exchangers may be,
triggering network slice allocation.
In practice, the network slice requirement modification request triggers a network slice modification when it requests modification of one or a combination of the following:
Network capacity, network topology, network configuration, network performance parameters, and traffic demands.
In practice, the network slice requirement modification request is embodied by the user's network slice requirement template GST.
In practice, network slice allocation is triggered when a network slice demand modification request results in a final network topology or a final network deployment change.
In an implementation, a network slice modification includes:
the modified requirements are modified after corresponding to corresponding ServiceProfile parameters, or the modified is performed after generating new ServiceProfile parameters based on new network slice requirements;
the demand decomposition is performed based on the relevant parameters and is embodied in the modification of the whole NSI network slice instance and NSSI sub-network slice instance.
In an implementation, a network slice modification includes:
determining a network slice parameter request to be modified, wherein the parameter request is determined by a management identifier of an NSI carried in a network slice demand modification request ModifyNSi sent by a second network element and a new network slice demand;
determining, by a feasibility check program, whether the parameter request can be modified;
when the parameter request can be modified, decomposing the parameter request into NSSI modification requests;
Performing NSSI modification in a third network element role;
transmitting the NSI modification result to a second network element;
and when the NSI modification is not possible, transmitting an NSI modification result to the second network element.
In an implementation, network slice allocation includes:
reuse existing network slices or newly created network slices.
In practice, further comprising:
when an existing network slice instance is modified to be able to meet new network slice requirements, the existing network slice is reused by modifying the existing network slice instance.
In practice, when an existing network slice instance does not contribute to other network services, the network slice instance is newly created after terminating the existing network slice instance.
In an implementation, after reusing an existing network slice or a newly created network slice, further comprising:
when reusing the existing network slice or newly-built network slice successfully, the first network element informs the user of a successful result or management identification of a network slice instance NSI; or, the first network element informs the user of the failure result when reusing the existing network slice or newly creating the network slice fails.
In an implementation, network slice allocation includes:
determining a network slice parameter request to be modified, wherein the parameter request is determined by a management identifier of an NSI carried in a network slice demand modification request AllocateNSi sent by a second network element and a new network slice demand;
Determining to reuse an existing network slice or a newly built network slice according to the parameter request and the existing deployment network slice capability;
if the existing network slice is reused, requesting a calling program to modify NSI according to the parameters;
if a network slice is newly built, NSSI distribution is carried out after the network slice subnet requirement is determined according to the parameter request;
creating MOI for NSI and configuring DN of MOI for NSSI;
and sending the NSI allocation result to the second network element.
In practice, further comprising:
the modification result sent to the second network element includes relevant network slice instance information if the existing NSI is modified or a new NSI is successfully created.
Wherein in fig. 4, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 400 and various circuits of memory represented by memory 420, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. Transceiver 410 may be a number of elements, including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 400 is responsible for managing the bus architecture and general processing, and the memory 420 may store data used by the processor 400 in performing operations.
The embodiment of the invention also provides a network element, which comprises:
the receiving module is used for receiving a network slice demand modification request sent by a user;
and the analysis triggering module is used for triggering corresponding operation according to the analysis result after analyzing the network slice demand modification request.
In implementation, the analysis triggering module is further configured to trigger the corresponding operation to:
triggering network slice modification; or alternatively, the first and second heat exchangers may be,
triggering network slice allocation.
In implementations, the analysis triggering module is further configured to trigger the network slice modification when the network slice requirement modification request is requesting modification of one or a combination of the following:
network capacity, network topology, network configuration, network performance parameters, and traffic demands.
In an implementation, the receiving module is further configured to receive a network slice requirement modification request embodied by the network slice requirement template GST of the user.
In practice, the analysis triggering module is further configured to trigger the network slice allocation when the network slice requirement modification request causes a final network topology or a final network deployment change.
In an implementation, the analysis triggering module is further configured to trigger a network slice modification, including:
the modified requirements are modified after corresponding to corresponding ServiceProfile parameters, or the modified is performed after generating new ServiceProfile parameters based on new network slice requirements;
The demand decomposition is performed based on the relevant parameters and is embodied in the modification of the whole NSI network slice instance and NSSI sub-network slice instance.
In an implementation, the analysis triggering module is further configured to trigger a network slice modification, including:
determining a network slice parameter request to be modified, wherein the parameter request is determined by a management identifier of an NSI carried in a network slice demand modification request ModifyNSi sent by a second network element and a new network slice demand;
determining, by a feasibility check program, whether the parameter request can be modified;
when the parameter request can be modified, decomposing the parameter request into NSSI modification requests;
performing NSSI modification in a third network element role;
transmitting the NSI modification result to a second network element;
and when the NSI modification is not possible, transmitting an NSI modification result to the second network element.
In an implementation, the analysis triggering module is further configured to trigger network slice allocation, including:
reuse existing network slices or newly created network slices.
In implementations, the analysis triggering module is further configured to reuse an existing network slice by modifying the existing network slice instance when the modification of the existing network slice instance is capable of meeting new network slice requirements.
In an implementation, the analysis triggering module is further configured to create a new network slice instance after terminating the existing network slice instance when the existing network slice instance does not contribute to other network services.
In implementation, the analysis triggering module is further used for notifying the user of a successful result or a management identifier of the network slice instance NSI when the reuse of the existing network slice or the newly-built network slice is successful after the reuse of the existing network slice or the newly-built network slice; or, the first network element informs the user of the failure result when reusing the existing network slice or newly creating the network slice fails.
In an implementation, the analysis triggering module is further configured to trigger network slice allocation, including:
determining a network slice parameter request to be modified, wherein the parameter request is determined by a management identifier of an NSI carried in a network slice demand modification request AllocateNSi sent by a second network element and a new network slice demand;
determining to reuse an existing network slice or a newly built network slice according to the parameter request and the existing deployment network slice capability;
if the existing network slice is reused, requesting a calling program to modify NSI according to the parameters;
if a network slice is newly built, NSSI distribution is carried out after the network slice subnet requirement is determined according to the parameter request;
creating MOI for NSI and configuring DN of MOI for NSSI;
and sending the NSI allocation result to the second network element.
In practice, the analysis triggering module is further configured to trigger that the modification result sent to the second network element comprises relevant network slice instance information if the existing NSI is modified or a new NSI is successfully created.
For convenience of description, the parts of the above apparatus are described as being functionally divided into various modules or units, respectively. Of course, the functions of each module or unit may be implemented in the same piece or pieces of software or hardware when implementing the present invention.
Fig. 5 is a second schematic diagram of a network element, where as shown in the drawing, the network element includes:
the processor 500, configured to read the program in the memory 520, performs the following procedures:
receiving a first message, wherein the first message is used for indicating modification of network slice requirements;
determining to execute corresponding network management operation;
a transceiver 510 for receiving and transmitting data under the control of the processor 500.
In practice, deciding to perform the corresponding network management operation includes:
modifying the network slice; and/or the number of the groups of groups,
network slice allocation.
In practice, the method further comprises:
if the modification of the existing network slice can meet the new network slice related requirements, the modification of the existing network slice is performed.
In practice, the method further comprises:
if the modification of the existing network slice cannot meet the related requirements of the new network slice and the existing network slice is not shared by other services, terminating the existing network slice and distributing the new network slice; and/or the number of the groups of groups,
If the modification of an existing network slice fails to meet the new network slice related requirements and the existing network slice is shared by other services, then the new network slice is allocated.
In implementations, the first message is a network slice related requirement including a generic network slice template GST.
In practice, the method further comprises:
after receiving the first message, obtaining a new service profile from the network slice related requirements;
and according to the new service description file, determining to execute corresponding network management operation.
In practice, deciding to perform the corresponding network management operation includes:
it is decided to perform a modification and/or allocation of the network slice instance NSI and/or the network slice subnet instance NSI.
In an implementation, a network slice modification includes:
transmitting a second message, wherein the second message comprises an identification of an NSI to be modified and a modification operation of the NSI to be modified; and/or receiving a second response.
In an implementation, network slice allocation includes:
transmitting a third message, the third message being indicative of allocation of a new slice; and/or the number of the groups of groups,
a third response is received.
In practice, the third response further includes identification information of the newly allocated NSI.
In practice, the method further comprises:
and sending a first response, wherein the first response is a modified response of the network slice requirement.
Wherein in fig. 5, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 500 and various circuits of memory represented by memory 520, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 510 may be a number of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 may store data used by the processor 500 in performing operations.
The embodiment of the invention also provides a network element, which comprises:
a receiving module, configured to receive a first message, where the first message is used to indicate modification of a network slice requirement;
and the execution module is used for deciding to execute corresponding network management operation.
In implementation, the execution module is further configured to, when determining to perform the corresponding network management operation, include:
modifying the network slice; and/or the number of the groups of groups,
network slice allocation.
In practice, the execution module is further configured to modify the existing network slice if the modification of the existing network slice can meet the new network slice related requirements.
In implementation, the execution module is further configured to terminate the existing network slice and allocate the new network slice if the modification of the existing network slice fails to meet the new network slice related requirements and the existing network slice is not shared by other services; and/or the number of the groups of groups,
if the modification of an existing network slice fails to meet the new network slice related requirements and the existing network slice is shared by other services, then the new network slice is allocated.
In implementations, the first message is a network slice related requirement including a generic network slice template GST.
In an implementation, the receiving module is further configured to obtain a new service profile from the network slice related requirement after receiving the first message;
the execution module is further configured to determine to execute a corresponding network management operation according to the new service description file.
In implementation, the execution module is further configured to, when determining to perform the corresponding network management operation, include:
it is decided to perform a modification and/or allocation of the network slice instance NSI and/or the network slice subnet instance NSI.
In an implementation, the execution module is further configured to, when the network slice is modified, include:
transmitting a second message, wherein the second message comprises an identification of an NSI to be modified and a modification operation of the NSI to be modified; and/or receiving a second response.
In an implementation, the execution module is further configured to, when allocating the network slice, include:
transmitting a third message, the third message being indicative of allocation of a new slice; and/or the number of the groups of groups,
a third response is received.
In practice, the third response further includes identification information of the newly allocated NSI.
In an implementation, the execution module is further configured to send a first response, the first response being a modified response of the network slice requirement.
For convenience of description, the parts of the above apparatus are described as being functionally divided into various modules or units, respectively. Of course, the functions of each module or unit may be implemented in the same piece or pieces of software or hardware when implementing the present invention.
The embodiment of the invention also provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program realizes the processing method of the network slice when being executed by a processor.
Specific implementations can be seen in the implementation of the processing method of the network slice.
In summary, in the technical solution provided by the embodiment of the present invention, nsms_p has the decision capability of decomposing SLA requirements and judging a specific solution;
further provides modification and processing schemes for ServiceProfile in different flows.
The processing scheme for modifying the whole requirement in the prior art is supplemented, and the original processes of modification, distribution and the like are integrated.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
Claims (14)
1. A method for processing a network slice, comprising:
the method comprises the steps that a first network element receives a first message, wherein the first message is used for indicating modification of network slice requirements;
the first network element decides to perform a corresponding network management operation.
2. The method of claim 1, wherein deciding to perform a corresponding network management operation comprises:
modifying the network slice; and/or the number of the groups of groups,
network slice allocation.
3. The method of claim 2, wherein the method further comprises:
if the modification of the existing network slice can meet the new network slice related requirements, the modification of the existing network slice is performed.
4. The method of claim 2, wherein the method further comprises:
if the modification of the existing network slice cannot meet the related requirements of the new network slice and the existing network slice is not shared by other services, terminating the existing network slice and distributing the new network slice; and/or the number of the groups of groups,
if the modification of an existing network slice fails to meet the new network slice related requirements and the existing network slice is shared by other services, then the new network slice is allocated.
5. The method of claim 1, wherein the first message is a network slice related requirement comprising a generic network slice template GST.
6. The method of claim 5, wherein the method further comprises:
after receiving the first message, obtaining a new service profile from the network slice related requirements;
and according to the new service description file, determining to execute corresponding network management operation.
7. The method of claim 1 or 2, wherein deciding to perform the corresponding network management operation comprises:
it is decided to perform a modification and/or allocation of the network slice instance NSI and/or the network slice subnet instance NSI.
8. The method of claim 7, wherein network slice modification comprises:
the first network element sends a second message, wherein the second message comprises an identification of an NSI to be modified and a modification operation of the NSI to be modified; and/or the first network element receives the second response.
9. The method of claim 7, wherein network slice allocation comprises:
the first network element sends a third message, wherein the third message is used for representing that a new slice is allocated; and/or the number of the groups of groups,
the first network element receives the third response.
10. The method of claim 9 wherein said third response further comprises identification information of the newly allocated NSI.
11. The method of claim 1 or 2, wherein the method further comprises:
the first network element sends a first response, which is a modified response of the network slice requirement.
12. A network element, comprising:
a processor for reading the program in the memory, performing the following process:
receiving a first message, wherein the first message is used for indicating modification of network slice requirements;
determining to execute corresponding network management operation;
and a transceiver for receiving and transmitting data under the control of the processor.
13. A network element, comprising:
a receiving module, configured to receive a first message, where the first message is used to indicate modification of a network slice requirement;
and the execution module is used for deciding to execute corresponding network management operation.
14. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when executed by a processor, implements the method of any of claims 1 to 11.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111659100.1A CN116418669A (en) | 2021-12-31 | 2021-12-31 | Processing method of network slice, network element and storage medium |
| PCT/CN2022/140294 WO2023125139A1 (en) | 2021-12-31 | 2022-12-20 | Network slice processing method, network element, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111659100.1A CN116418669A (en) | 2021-12-31 | 2021-12-31 | Processing method of network slice, network element and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116418669A true CN116418669A (en) | 2023-07-11 |
Family
ID=86997751
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111659100.1A Pending CN116418669A (en) | 2021-12-31 | 2021-12-31 | Processing method of network slice, network element and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN116418669A (en) |
| WO (1) | WO2023125139A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117081945A (en) * | 2023-10-12 | 2023-11-17 | 南京中科境远科技有限公司 | Core network slicing subnet instance deployment method and device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109474449A (en) * | 2017-09-08 | 2019-03-15 | 华为技术有限公司 | A kind of method and device of processing network slice example |
| CN109874143B (en) * | 2017-12-04 | 2022-02-25 | 华为技术有限公司 | Network slice modification method and device |
| US11115826B2 (en) * | 2018-06-18 | 2021-09-07 | Electronics And Telecommunications Research Institute | Method for managing network slicing resources in communication system and apparatus for the same |
-
2021
- 2021-12-31 CN CN202111659100.1A patent/CN116418669A/en active Pending
-
2022
- 2022-12-20 WO PCT/CN2022/140294 patent/WO2023125139A1/en unknown
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117081945A (en) * | 2023-10-12 | 2023-11-17 | 南京中科境远科技有限公司 | Core network slicing subnet instance deployment method and device |
| CN117081945B (en) * | 2023-10-12 | 2024-01-09 | 南京中科境远科技有限公司 | Core network slicing subnet instance deployment method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023125139A1 (en) | 2023-07-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3648401B1 (en) | Method, device, and computer readable storage medium for managing network slice | |
| CN110447208B (en) | Network slice management method, unit and system | |
| CN110226308B (en) | Network slice management method, management unit and system | |
| CN109391490B (en) | Network slice management method and device | |
| US10993127B2 (en) | Network slice instance management method, apparatus, and system | |
| CN112789832B (en) | Dynamic slice priority handling | |
| US20200014589A1 (en) | Network slice configuration method, apparatus, and system | |
| CN108337110B (en) | Virtual resource management method and device and computer readable storage medium | |
| CN109600768A (en) | Management method, equipment and the system of network slice | |
| US11240745B2 (en) | Network slice instance processing method and apparatus, and system | |
| CN109391498B (en) | Management method of network component and network equipment | |
| EP3657861A1 (en) | Method and device for deploying network slice | |
| CN113596863B (en) | Method, equipment and medium for determining user plane function and providing information | |
| CN109600769B (en) | Communication method and device | |
| US20190260636A1 (en) | Method and apparatus for managing network slice instance | |
| CN109842507B (en) | Network slice management method and equipment | |
| CN109314696B (en) | Method and device for managing network slices | |
| CN109391503B (en) | Network slice management method and device | |
| CN107332814B (en) | Request message transmission method and device | |
| CN112839339A (en) | System information sending method, network equipment, base station and storage medium | |
| CN116418669A (en) | Processing method of network slice, network element and storage medium | |
| CN110417876A (en) | Node server and main control device in session method, distributed system | |
| CN112311567B (en) | Communication method and device | |
| CN114080016A (en) | Method and device for synchronizing context information of user equipment and network side equipment | |
| CN109526032B (en) | Method and device for modifying network slice example |
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 |