WO2019047769A1 - 一种处理网络切片实例的方法、装置及*** - Google Patents
一种处理网络切片实例的方法、装置及*** Download PDFInfo
- Publication number
- WO2019047769A1 WO2019047769A1 PCT/CN2018/103344 CN2018103344W WO2019047769A1 WO 2019047769 A1 WO2019047769 A1 WO 2019047769A1 CN 2018103344 W CN2018103344 W CN 2018103344W WO 2019047769 A1 WO2019047769 A1 WO 2019047769A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- nssi
- network device
- message
- network
- related requirement
- Prior art date
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/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
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/18—Selecting a network or a communication service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- 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/06—Management of faults, events, alarms or notifications
-
- 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/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- 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/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/08—Configuration management of networks or network elements
- H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow 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/08—Configuration management of networks or network elements
- H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
- H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
-
- 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
-
- 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
-
- 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
- H04L41/5025—Ensuring fulfilment of SLA by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
-
- 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/0876—Aspects of the degree of configuration automation
- H04L41/0886—Fully automatic configuration
-
- 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/0894—Policy-based network configuration management
Definitions
- the present application relates to the field of communications technologies, and in particular, to a method, an apparatus, and a system for processing an instance of a network slice.
- the present application provides a method, an apparatus, and a system for processing a network slice instance, which are used to solve the problem of how to modify a shared NSSI, thereby implementing modification of one of the NSIs to which the shared NSSI belongs.
- the present application provides a method for processing an instance of a network slice, the method comprising: receiving, by a first network device, a first message sent by a second network device, wherein the first message is used to request the first
- the network device modifies the first network slice subnet instance NSSI managed by the first network device, where the first NSSI is shared by multiple network slice instances managed by different network devices; the first network device determines Whether to modify the first NSSI; the first network device performs subsequent processing according to the result of the determining.
- the first network device determines whether the first NSSI can be modified according to the received first message, and performs subsequent processing according to the determination result, and the process of determining can avoid directly modifying the first when the first NSSI is shared by multiple NSIs.
- the NSSI has a problem of negatively affecting the NSI managed by other NSMFs sharing the first NSSI.
- the first network device determines that the first NSSI is allowed to be modified, the first network device performs subsequent processing according to the result of the determining, where the first network device is The first NSSI is modified.
- the first network device determines that the first NSSI can be modified after modifying the first NSSI, thereby improving the modification speed.
- the first network device determines that the first NSSI is not allowed to be modified, the first network device performs subsequent processing according to the result of the determining, where the first network device is created. a second NSSI; the first network device configuring the second NSSI.
- the second NSSI that belongs to the first network device itself is created, and the parameters of the second NSSI are configured, and the first NSSI is implemented.
- the revision of NSI will not have a negative impact on other NSIs.
- the first network device after the first network device performs subsequent processing according to the result of the determining, the first network device sends a second message to the second network device, where the second message is directed to The response of the first message.
- the modification of the first network device of the second network device is notified.
- the first network device after the first network device determines that the first NSSI is not allowed to be modified, the first network device sends a third message to the second network device, where the The third message carries the related requirement information that needs to create the second NSSI, and is used to indicate the support situation of the first network device for the related requirement of the second NSSI; the first network device receives the second network device to send The fourth message, wherein the fourth message carries indication information, configured to indicate whether the first network device is allowed to create the second NSSI, or whether to accept the creation of the third message Two NSSI related demand information.
- the related information about creating the second NSSI is determined by using the third message and the fourth message, so as to improve the creation speed of the second NSSI.
- the fourth message further includes the second network device recommendation Creating related requirement information of the second NSSI.
- the first message includes identification information of the first NSSI, and updated related requirement information of the first NSSI, where the related requirement information includes a service level agreement, key performance At least one of a parameter, a type of network slice subnet, a quality of service, a network topology, a resource requirement, and a network function related requirement.
- the first message further includes identifier information of the NSI to which the first NSSI belongs.
- the second message includes the second NSSI identification information.
- the second message includes the identifier information of the NSI to which the second NSSI belongs.
- the first network device configures the second NSSI, including: the first network device adds the second NSSI to an NSI to which the first NSSI belongs, and Deleting the NSI of the first NSSI.
- the NSSI included in the NSI is updated to reduce the redundancy of the NSI.
- the present application provides a method for processing a network slice instance, the method comprising: a second network device sending a first message to a first network device, wherein the first message is used to request the first network The device modifies the first network slice subnet instance NSSI managed by the first network device, where the first NSSI is shared by multiple network slice instances managed by different network devices; the second network device receiving station And a second message sent by the first network device, where the second message is a response to the first message.
- the first network device sends a first message according to the foregoing method, and the first network device determines, according to the received first message, whether the first NSSI can be modified, and performs subsequent processing according to the determination result, and the first module can avoid
- the first NSSI is shared by multiple NSIs, directly modifying the problem that the first NSSI adversely affects the NSIs managed by other NSMFs sharing the first NSSI.
- the method further includes: the second network device receiving the third message sent by the first network device, where And the third message carries the related requirement information that is required to create the second NSSI, and is used to indicate that the first network device supports the related requirement of the second NSSI; Receiving, by the network device, a fourth message, where the fourth message carries indication information, used to indicate whether the first network device is allowed to create the second NSSI, or whether to accept the third message Creating related requirement information of the second NSSI.
- the indication information of the related requirement for the second NSSI carried by the fourth message sent by the second network device to the first network device is a negative indication
- the fourth message further includes The second network device proposes to create related requirement information of the second NSSI.
- the application provides an apparatus for processing an instance of a network slice, the apparatus comprising: a receiving unit, configured to receive a first message sent by a second network device, where the first message is used to request a location Modifying, by the first network device to which the receiving unit belongs, the first network slice subnet instance NSSI managed by the first network device, where the first NSSI is shared by multiple network slice instances managed by different network devices;
- the processing unit is configured to determine whether the first NSSI is allowed to be modified, and perform subsequent processing according to the result of the determining.
- the method when the processing module performs subsequent processing according to the result of the determining, the method is specifically configured to modify the first NSSI if it is determined that the first NSSI is allowed to be modified.
- the method when the processing module performs subsequent processing according to the result of the determining, the method is specifically configured to: if it is determined that the first NSSI is not allowed to be modified, create a second NSSI.
- the processing module is further configured to: after the second NSSI is created, the second NSSI is configured.
- the apparatus further includes a transmitting unit, configured to send the second message to the second network device.
- the sending unit is further configured to: after determining that the first NSSI does not allow modification, send a third message to the second network device, where the third message is carried
- the related information about the second NSSI needs to be created to indicate the support situation of the first network device for the related requirement of the second NSSI; the receiving unit receives the fourth message sent by the second network device, where The fourth message carries the indication information, which is used to indicate whether the first network device is allowed to create the second NSSI, or whether to receive the related requirement information for creating the second NSSI carried in the third message.
- the fourth message further includes the creation of the second network device recommendation.
- Related demand information for the second NSSI if the indication information of the related requirement for the second NSSI carried by the fourth message is a negative indication, the fourth message further includes the creation of the second network device recommendation. Related demand information for the second NSSI.
- the first message includes identification information of the first NSSI, and updated related requirement information of the first NSSI, where the related requirement information includes a service level agreement, key performance At least one of a parameter, a type of network slice subnet, a quality of service, a network topology, a resource requirement, and a network function related requirement.
- the first message further includes identifier information of the NSI to which the first NSSI belongs.
- the second message includes the second NSSI identification information.
- the second message includes the identifier information of the NSI to which the second NSSI belongs.
- the application provides an apparatus for processing an instance of a network slice, the apparatus comprising: a sending unit, configured to send a first message to a first network device, where the first message is used to request the The first network device modifies the first network slice subnet instance NSSI managed by the first network device, where the first NSSI is shared by multiple network slice instances managed by different network devices; and the receiving unit is configured to: Receiving a second message sent by the first network device.
- the receiving unit is further configured to: receive a third message sent by the first network device, where the third message carries related requirement information that needs to create a second NSSI, and is used to: And indicating that the first network device supports the related requirement of the second NSSI; the sending unit is further configured to send a fourth message to the first network device, where the fourth message carries the indication information And indicating whether the first network device is allowed to create the second NSSI, or whether to accept related requirement information for creating the second NSSI carried in the third message.
- the fourth message further includes the creation of the second network device recommendation.
- Related demand information for the second NSSI if the indication information of the related requirement for the second NSSI carried by the fourth message is a negative indication, the fourth message further includes the creation of the second network device recommendation. Related demand information for the second NSSI.
- the present application provides an apparatus for processing a network slice instance, including a communication interface, a processor, and a memory, wherein: a communication interface, a memory, and a processor, the memory is configured to store a program code to be executed by the processor .
- the communication interface is used to receive user tasks sent by the client.
- the processor is configured to execute the program code stored in the memory, and is specifically configured to perform the method in any one of the first to second aspects or the first to the second aspects.
- the embodiment of the present application further provides a system.
- the system includes the first network device and the second network device.
- the second network device is configured to send a first message to the first network device, where the first message is used to request that the first network device manages the first network device Modifying a network sliced subnet instance NSSI, the first NSSI being shared by multiple network slice instances managed by different network devices;
- the first network device is configured to receive the first message, determine whether to permit modification of the first NSSI, and perform subsequent processing according to the result of the determining.
- the first network device may perform the subsequent processing according to the result of the determining, and may perform the first NSSI. to modify.
- the first network device may create a second NSSI when performing subsequent processing according to the result of the determining.
- the first network device may further send a second message to the second network device, where the second message is a response to the first message; and the second network device is The second message can be received.
- the first network device may further configure the second NSSI after creating the second NSSI.
- the third network message may be sent to the second network device, where the third message carries And the related requirement information of the second NSSI is used to indicate the support situation of the first network device for the related requirement of the second NSSI.
- the second network device receives the third message, and may further send a fourth message to the first network device, where the fourth message carries indication information, used to indicate the first network device Whether the second NSSI is allowed to be created, or whether the related requirement information for creating the second NSSI carried in the third message is accepted;
- the first network device can receive the fourth message.
- the fourth message in the case that the second network device does not accept the related requirement information for creating the second NSSI carried in the third message, the fourth message carries the second NSSI
- the indication information of the related requirement is a negative indication, and the fourth message further includes related requirement information that is suggested by the second network device to create the second NSSI.
- the present application further provides a computer readable storage medium for storing functions for performing the functions designed in any of the first to second aspects or the first to second aspects of the possible implementations.
- Computer software instructions comprising a program for performing the design in any of the possible implementations of the first to second aspects or the first to second aspects described above.
- the present application further provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform any of the first to second aspects or any of the first to second aspects of the possible implementations The method in .
- FIG. 1 is a schematic diagram of an NSSI sharing scenario provided by the present application.
- FIG. 2 is a schematic diagram of another NSSI sharing scenario provided by the present application.
- FIG. 3 is a schematic structural diagram of a system provided by the present application.
- FIG. 4 is a flowchart of a method for processing a network slice instance according to the present application.
- FIG. 5 is a flowchart of another method for processing a network slice instance according to the present application.
- FIG. 6 is a flowchart of still another method for processing a network slice instance provided by the present application.
- FIG. 7 is a flowchart of still another method for processing a network slice instance according to the present application.
- FIG. 8 is a schematic diagram of an apparatus for processing an instance of a network slice according to the present application.
- FIG. 9 is a schematic diagram of another apparatus for processing a network slice instance according to the present application.
- FIG. 10 is a hardware structural diagram of an apparatus for processing a network slice instance according to the present application.
- the present application provides a method and apparatus for processing a network sharding instance to solve the problem of how to modify a shared NSSI when at least two NSI shared NSSIs managed by different NSMFs exist in the prior art, without causing negative effects on other NSIs.
- the method and the device are based on the same inventive concept. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and the repeated description is not repeated.
- the second network device is mainly responsible for managing the life cycle, performance, faults, and the like of the network segment instance, and compiling the composition of the network slice instance, and the requirement for decomposing the network slice instance is an instance of each network sliced subnet and/or
- the network function requires sending a network slice subnet instance management request to the management entity of each network slice subnet.
- the second network device can be a network slice management function (NSMF).
- NSMF network slice management function
- the first network device is mainly responsible for receiving the network slice subnet requirement sent by the second network device, managing the network slice subnet instance, and compiling the NSSI component.
- the first network device may be a network slice subnet management function (NSSMF).
- the second network device may further include other functional modules, and the NSMF is only a part of the second network device; the first network device may further include other functional modules, and the NSSMF is only a part of the first network device.
- the NSI identified as A has three NSSIs, namely NSSI1, NSSI2, and NSSI3, and the NSI identified as B has three NSSIs, which are respectively NSSI1.
- NSSI1 is shared by multiple network slice instances managed by the same NSMF.
- the NSMF knows in advance that all the NSIs sharing the NSSI belong to the same NSMF.
- the NSMF will modify the NSSI.
- the message is sent to the NSSMF corresponding to the NSSI, and the NSSMF modifies the NSSI according to the modification request message, but may have a negative impact on other NSIs sharing the NSSI.
- Scenario 2 As shown in FIG.
- the NSI identified as A has NSSI1, NSSI2, and NSSI3, and the NSI identified as B has NSSI1, NSSI4, and NSSI5; wherein NSSI1 is shared by NSI A and NSI B.
- NSI A is managed by NSMF1
- NSI B is managed by NSMF2.
- NSSI1 is shared by multiple network slice instances managed by different NSMFs.
- the NSMF managing the NSI to be modified does not know the sharing condition of the NSSI, that is, the NSMF considers the NSSI to be unique to the NSI, thereby sending a modification request to the NSSMF.
- the NSSMF modifies the NSSI according to the modification request. However, since the NSSI is shared by multiple NSIs, when the other NSIs are not allowed to modify the NSSI, and the NSSMF modifies the NSSI according to the modification request, it may have a negative impact on other NSIs sharing the NSSI.
- Figure 3 shows a system architecture diagram between NSMF and NSSMF.
- the plurality referred to in the present application means two or more.
- the first network device determines, according to the received first message, whether the first NSSI can be modified, and performs subsequent processing according to the determination result, and the first module can prevent the first NSSI from being shared by multiple NSIs through the process of determining.
- the problem that the first NSSI adversely affects other NSIs other than the NSI managed by the second network device is directly modified.
- FIG. 4 is a flowchart of a method for processing a network slice instance according to the present application, where the method includes:
- the first network device receives the first message sent by the second network device, where the first message is used to request the first network device to modify the first NSSI managed by the first network device, where The first NSSI is shared by multiple network slice instances managed by different network devices.
- the first message includes the first NSSI identification information, and the updated first NSSI related requirement information, where the related requirement information includes a service level agreement (SLA), At least one of a network key performance indicator (network KPI), a type of network slice subnet, a quality of service, a network topology, a resource requirement, and a network function related requirement.
- the first message is referred to as a modification request message.
- the modification request message may further include identifier information of the NSI to which the first NSSI belongs.
- the network KPI includes: a latency, a coverage, a capacity, a throughput, a reliability, a report success ratio, and a success rate ( At least one parameter in command success ratio).
- the reporting success rate may refer to the proportion of successful uplink packet transmission; the delivery success rate may refer to the proportion of successful downlink packet transmission; the coverage may refer to the segmentation area of the terminal; and the capacity may refer to the number of terminals that can be accommodated.
- the types of network slicing subnets include enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC, Ultra-Reliable Low Latency Communications), massive Internet of Things (MIoT, Massive Internet of Things), etc.
- Network function related requirements include type, capacity, location, capability, and the like.
- the first network device determines whether to modify the first NSSI.
- the first network device determines that the first NSSI is allowed to be modified, or the first network device determines that the first NSSI is not allowed to be modified.
- the first network device performs subsequent processing according to the result of the determining.
- the first network device modifies the first NSSI; if the first network device determines that the modification is not allowed a first NSSI, the first network device creates a second NSSI, and the first network device configures the second NSSI. Specifically, the first network device adds the second NSSI to the first An NSI to which an NSSI belongs, and deleting the first NSSI from the NSI.
- the method further includes: the first network device sending a second message to the second network device to respond to the first message.
- the second message is called a modification response message.
- the first network device determines whether the first NSSI can be modified according to the received first message, and performs subsequent processing according to the determination result, and the process of determining can avoid directly when the first NSSI is shared by multiple NSIs. Modifying the problem that the first NSSI adversely affects the NSI managed by other SMFs sharing the first NSSI.
- the method further includes: the first network device sending a third message to the second network device
- the third message carries the related requirement information that needs to create a second NSSI, and is used to indicate that the first network device supports the related requirement of the second NSSI;
- the first network device receives the a fourth message sent by the second network device, where the fourth message carries indication information, configured to indicate whether the first network device is allowed to create the second NSSI, or whether to accept the third message.
- the third message is called a negotiation request message
- the fourth message is called a negotiation response message.
- the negotiation response message further includes a related requirement that the second network device proposes to create the second NSSI. information.
- the second message includes the second NSSI identifier information and the identifier information of the NSI to which the second NSSI belongs.
- Embodiment 1 is as shown in FIG. 5:
- the NSMF sends a modification request message to the NSSMF, requesting to modify the first NSSI.
- the modification request message includes the following parameters: a first network slice subnet instance identifier to be modified, for example, an NSSI ID, and an updated NSSI related requirement.
- the network slice instance identifier to which the first NSSI belongs for example, an NSI ID, may also be included.
- the factor that triggers the NSMF to modify the first NSSI may be that the NSMF receives the external request, for example, receives the relevant network slice instance modification request from the user service management function, or may be the NSMF according to the running condition of the network slice instance and the preset rule policy.
- the self-determination needs to modify the network slice instance; and further determines that the network slice subnet instance in the network slice instance needs to be modified.
- the NSSMF determines to modify the first NSSI, and the NSSMF modifies the first NSSI.
- the NSSMF determines to allow modification.
- the first NSSI since the first NSSI belongs to multiple NSIs, the NSSMF managing the first NSSI may receive management of multiple NSMFs, and the NSSMF determines that the related requirements of the updated first NSSI are in the settings of the multiple NSIs. In the range, modifying the first NSSI does not adversely affect the multiple NSIs, and the NSSMF determines that the first NSSI is allowed to be modified. In the case that the NSSI is allowed to be modified, the NSSMF modifies the NSSI according to the updated network slice subnet requirement in the modification request message.
- the NSSMF After modifying the first NSSI, the NSSMF sends a modification response message to the NSMF.
- the modification response message may carry indication information indicating whether the modification is successful. For example, carrying “1" means that the modification is successful, and carrying "0" means that the modification failed.
- the NSMF sends a modification request message to the NSSMF, requesting to modify the first NSSI.
- the parameter included in the modification request message is as shown in Embodiment 1, and is not described here.
- the NSSMF determines that the modification of the first NSSI is not allowed.
- the NSSMF judges that the modification of the first NSSI is not allowed.
- the NSSMF managing the first NSSI may receive management of multiple NSMFs, and the NSSMF determines that the related requirement of the updated first NSSI exceeds at least one of the multiple NSIs.
- the modification of the first NSSI may adversely affect at least one of the plurality of NSIs, and the NSSMF determines that the first NSSI is not allowed to be modified.
- the NSSMF creates a second NSSI according to the updated network slice subnet related requirement in the modification request message.
- the NSSMF performs related configuration on the second NSSI.
- the NSSMF adds the newly created second NSSI to the first NSI according to the first NSI ID to which the first NSSI belongs. For example, the NSSMF configures a mapping relationship between the second NSSI ID and the first NSI ID for the newly created second NSSI, and adds the second NSSI to the first NSI. Optionally, the NSSMF deletes the mapping relationship between the first NSSI ID and the first NSI ID, and removes the first NSSI from the first NSI.
- the newly created second NSSI belongs only to the first NSI, and does not belong to other NSIs that share the first NSSI.
- the NSSMF sends a modification response message to the NSMF.
- the modification response message includes a newly created second NSSI identifier, for example, a second NSSI ID.
- the modification response message may further include a network slice instance identifier to which the second NSSI belongs, for example, a first NSI ID.
- the NSMF sends a modification request message to the NSSMF, requesting to modify the first NSSI.
- the parameter included in the modification request message is as shown in Embodiment 1, and is not described here.
- the NSSMF determines that the modification of the first NSSI is not allowed.
- the NSSMF It is judged that the modification of the first NSSI is not allowed.
- the NSSMF sends a negotiation request message to the NSMF.
- the negotiation request message carries the relevant requirement information of the NSSI, and is used to indicate that the NSSMF supports the related requirements of the NSSI.
- the negotiation request message further carries indication information about whether to allow creation of a new network slice subnet instance.
- the NSMF sends a negotiation response message to the NSSMF.
- the negotiation response message carries related indication information. If the indication information about the NSSI related requirement carried in the negotiation response message is a positive indication, the NSMF accepts the network slice subnet related requirement reported by the NSSMF, if When the indication information of the related requirement for the NSSI carried in the negotiation response message is a negative indication, the NSMF does not accept the network slice subnet related requirement reported by the NSSMF. Further, if the NSMF does not accept the network slice subnet related requirement reported by the NSSMF, the indication information carried in the negotiation response message may further include the network slice subnet related requirement information recommended by the NSMF. Optionally, the NSSMF and the NSMF may perform the multiple negotiation, that is, repeat steps S703 and S704 to determine the relevant requirement information of the final network slice subnet.
- the negotiation request message in step S703 carries the indication information of whether to allow the creation of a new subnet instance
- the NSMF and the NSSMF perform the foregoing negotiation process in this step for the allowed case;
- the NSMF does not allow the NSSMF to create a new NSSI
- the negotiation response message may carry the indication that the modification fails.
- the NSSMF creates a new second NSSI according to the updated network slice subnet related requirement in the negotiation response message.
- the NSSMF performs related configuration on the second NSSI.
- the NSSMF adds the newly created second NSSI to the first NSI according to the first NSI ID to which the first NSSI belongs. For example, the NSSMF configures a mapping relationship between the second NSSI ID and the first NSI ID for the newly created second NSSI, and adds the second NSSI to the first NSI. Optionally, the NSSMF deletes the mapping relationship between the first NSSI ID and the first NSI ID, and removes the first NSSI from the first NSI.
- the newly created second NSSI belongs only to the first NSI, and does not belong to other NSIs that share the first NSSI.
- the NSSMF sends a modification response message to the NSMF.
- the modification response message includes a newly created second NSSI identifier, for example, a second NSSI ID.
- the modification response message may further include a network slice instance identifier to which the second NSSI belongs, for example, a first NSI ID.
- the negotiation request message in step S703 carries the indication information that does not allow the creation of a new subnet instance, the modification response message is negative.
- the present application further provides an apparatus for processing an instance of a network slice.
- the apparatus includes:
- the receiving unit 801 is configured to receive a first message sent by the second network device, where the first message is used to request the first network device to which the receiving unit belongs to the first network managed by the first network device.
- the sliced subnet instance NSSI is modified, and the first NSSI is shared by multiple network slice instances managed by different network devices.
- the processing unit 802 is configured to determine whether the first NSSI is allowed to be modified, and perform subsequent processing according to the result of the determining.
- the first network device determines, according to the received first message, whether the first NSSI can be modified, and performs subsequent processing according to the determination result, and the first module can avoid, when the first NSSI is multiple, When the NSI is shared, the problem that the first NSSI adversely affects other NSIs other than the NSI managed by the second network device is directly modified.
- the processing module when the processing module performs subsequent processing according to the result of the determining, specifically, if it is determined that the first NSSI is allowed to be modified, or the processing module is configured according to the When the result of the judgment is performed, the second NSSI is created after the second NSSI is created. If the second NSSI is created, the second NSSI is configured.
- the processing unit adds the second NSSI to the NSI to which the first NSSI belongs, and deletes the NSI in the first NSSI.
- the apparatus further includes a sending unit, configured to send the second message to the second network device.
- the sending unit is further configured to: after the first NSSI is not allowed to be modified, send a third message to the second network device, where the third message carries a second The NSSI related requirement information is used to indicate the support situation of the first network device for the related requirement of the second NSSI; the receiving unit receives the fourth message sent by the second network device, where the The fourth message carries the indication information, which is used to indicate whether the first network device is allowed to create the second NSSI, or whether to accept the related requirement information for creating the second NSSI carried in the third message.
- the negotiation response message further includes a related requirement that the second network device proposes to create the second NSSI. information.
- the first message includes identification information of the first NSSI, and updated related requirement information of the first NSSI, where the related requirement information includes a service level agreement, key performance At least one of a parameter, a type of network slice subnet, a quality of service, a network topology, a resource requirement, and a network function related requirement.
- the first message further includes identifier information of the NSI to which the first NSSI belongs.
- the second message includes the second NSSI identifier information.
- the second message includes the identifier information of the NSI to which the second NSSI belongs.
- the present application further provides another apparatus for processing an instance of a network slice.
- the apparatus includes:
- the sending unit 901 is configured to send a first message to the first network device, where the first message is used to request the first network slice subnet instance NSSI managed by the first network device by the first network device The modification is performed, and the first NSSI is shared by multiple network slice instances managed by different network devices.
- the receiving unit 902 is configured to receive a second message sent by the first network device.
- the receiving unit is further configured to: receive the third message sent by the first network device, where the third The message carries the related requirement information that needs to be used to create the second NSSI, and is used to indicate the support situation of the first network device for the related requirement of the second NSSI.
- the sending unit is further configured to receive the first network device. Sending a fourth message, where the fourth message carries indication information, which is used to indicate whether the first network device is allowed to create the second NSSI, or whether to accept the creation of the third message Two NSSI related demand information.
- each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
- the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
- the device for modifying the network slice instance may include the processor 1002.
- the hardware of the entity corresponding to the above module may be the processor 1002.
- the processor 1002 can be a central processing unit (English: central processing unit, CPU for short), or a digital processing module or the like.
- the apparatus for modifying the network slice instance may further include a communication interface 1001, and the processor 1002 transmits and receives data through the communication interface 1001.
- the apparatus also includes a memory 1003 for storing a program executed by the processor 1002.
- the memory 1003 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid state drive (SSD), or a volatile memory (English: volatile) Memory), such as random access memory (English: random-access memory, abbreviation: RAM).
- Memory 1003 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
- the processor 1002 is configured to execute the program code stored in the memory 1003, and may be specifically used to execute the method described in the embodiment shown in FIG.
- connection medium between the communication interface 1001, the processor 1002, and the memory 1003 is not limited in the embodiment of the present application.
- the memory 1003, the processor 1002, and the communication interface 1001 are connected by a bus 1004 in FIG. 10, and the bus is indicated by a thick line in FIG. 10, and the connection manner between other components is only schematically illustrated. , not limited to.
- the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 10, but it does not mean that there is only one bus or one type of bus.
- the embodiment of the invention further provides a computer readable storage medium for storing computer software instructions required to execute the above-mentioned processor, which comprises a program for executing the above-mentioned processor.
- embodiments of the present application can be provided as a method, system, or computer program product.
- the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
- the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Quality & Reliability (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Small-Scale Networks (AREA)
Abstract
一种处理网络切片实例的方法、装置及***,用以解决现有技术中存在两个由不同NSMF所管理的NSI共享NSSI时,如何对其中一个NSI进行修改,而对其他NSI造成负面影响的问题。该方法包括:第一网络设备接收第二网络设备发送的第一消息,其中,所述第一消息用于请求所述第一网络设备对所述第一网络设备所管理的第一网络切片子网实例NSSI进行修改;所述第一网络设备判断是否允许修改所述第一NSSI;所述第一网络设备根据所述判断的结果进行后续处理。
Description
本申请要求2017年9月8日提交中国专利局、申请号为201710807964.0、发明名称为“一种处理网络切片实例的方法及装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请文件中。仅仅是为了简洁表述,其全部内容不在本申请文件中再原文重复一遍。
本申请涉及通信技术领域,尤其涉及一种处理网络切片实例的方法、装置及***。
本申请提供一种处理网络切片实例的方法、装置及***,用以解决如何对共享NSSI进行修改,进而实现对共享NSSI所属的其中一个NSI进行修改的问题。
第一方面,本申请提供了一种处理网络切片实例的方法,该方法包括:第一网络设备接收第二网络设备发送的第一消息,其中,所述第一消息用于请求所述第一网络设备对所述第一网络设备所管理的第一网络切片子网实例NSSI进行修改,所述第一NSSI是不同网络设备管理的多个网络切片实例所共享的;所述第一网络设备判断是否允许修改所述第一NSSI;所述第一网络设备根据所述判断的结果进行后续处理。
通过上述方法,第一网络设备根据接收的第一消息判断是否可以修改第一NSSI,根据判断结果进行后续处理,通过判断的过程可以避免当第一NSSI是多个NSI共享时,直接修改第一NSSI对共享第一NSSI的由其他NSMF管理的NSI造成负面影响的问题。
在一种可能的设计中,若所述第一网络设备判断出允许修改所述第一NSSI,所述第一网络设备根据所述判断的结果进行后续处理包括:所述第一网络设备对所述第一NSSI进行修改。
通过该方法,第一网络设备判断可以修改第一NSSI后直接对所述第一NSSI进行修改,提高了修改速度。
在一种可能的设计中,若所述第一网络设备判断出不允许修改所述第一NSSI,所述第一网络设备根据所述判断的结果进行后续处理包括:所述第一网络设备创建第二NSSI;所述第一网络设备对所述第二NSSI进行配置。
通过该方法,当第一网络设备判断出不允许修改第一NSSI后,创造属于第一网络设备自身的第二NSSI,并对第二NSSI的参数进行了配置,既实现了对第一NSSI所属的NSI的修改,又不会对其他NSI造成负面影响。
在一种可能的设计中,所述第一网络设备根据所述判断的结果进行后续处理之后,所述第一网络设备向所述第二网络设备发送第二消息,所述第二消息为针对所述第一消息的响应。
通过该方法,告知第二网络设备所述第一网络设备的修改情况。
在一种可能的设计中,所述第一网络设备判断出所述第一NSSI不允许进行修改之后,所述第一网络设备向所述第二网络设备发送第三消息,其中,所述第三消息中携带需要创建第二NSSI的相关需求信息,用于指示所述第一网络设备对所述第二NSSI的相关需求的支持情况;所述第一网络设备接收所述第二网络设备发送的第四消息,其中,所述第四消 息中携带指示信息,用于指示所述第一网络设备是否允许创建所述第二NSSI,或者是否接受所述第三消息中携带的创建所述第二NSSI的相关需求信息。
通过该方法,通过第三消息与第四消息确定出创建第二NSSI的相关需求信息,以便于提高第二NSSI的创建速度。
在一种可能的设计中,若所述第四消息指示消息中携带的针对第二NSSI的相关需求的指示信息为否定指示,则所述第四消息中还包括所述第二网络设备建议的创建所述第二NSSI的相关需求信息。
在一种可能的设计中,所述第一消息中包括所述第一NSSI的标识信息、以及更新后的所述第一NSSI的相关需求信息,所述相关需求信息包括服务水平协议、关键绩效指标、网络切片子网的类型、服务质量、网络拓扑、资源需求以及网络功能相关需求等参数中的至少一个。
在一种可能的设计中,所述第一消息中还包括所述第一NSSI所属的NSI的标识信息。
在一种可能的设计中,所述第二消息中包括所述第二NSSI标识信息。
在一种可能的设计中,所述第二消息中包括所述第二NSSI所属的NSI的标识信息。
在一种可能的设计中,所述第一网络设备对所述第二NSSI进行配置,包括:所述第一网络设备将所述第二NSSI加入到所述第一NSSI所属的NSI中,并将所述第一NSSI所述NSI中删除。
通过该方法,更新NSI所包含的NSSI,减少NSI的冗余。
第二方面,本申请提供了一种处理网络切片实例的方法,该方法包括:第二网络设备向第一网络设备发送第一消息,其中,所述第一消息用于请求所述第一网络设备对所述第一网络设备所管理的第一网络切片子网实例NSSI进行修改,所述第一NSSI是不同网络设备管理的多个网络切片实例所共享的;所述第二网络设备接收所述第一网络设备发送的第二消息,所述第二消息为针对所述第一消息的响应。
通过上述方法,第二网络设备发送第一消息,第一网络设备根据接收的第一消息判断是否可以修改第一NSSI,根据判断结果进行后续处理,所述第一模块通过判断的过程可以避免当第一NSSI是多个NSI共享时,直接修改第一NSSI对共享第一NSSI的由其他NSMF管理的NSI造成负面影响的问题。
在一种可能的设计中,所述第二网络设备向第一网络设备发送第一消息之后,该方法还包括:所述第二网络设备接收所述第一网络设备发送的第三消息,其中,所述第三消息中携带需要创建第二NSSI的相关需求信息,用于指示所述第一网络设备对所述第二NSSI的相关需求的支持情况;所述第二网络设备向所述第一网络设备接收发送第四消息,其中,所述第四消息中携带指示信息,用于指示所述第一网络设备是否允许创建所述第二NSSI,或者是否接受所述第三消息中携带的创建所述第二NSSI的相关需求信息。
在一种可能的设计中,所述第二网络设备向所述第一网络设备发送的第四消息携带的针对第二NSSI的相关需求的指示信息为否定指示,所述第四消息中还包括所述第二网络设备建议的创建所述第二NSSI的相关需求信息。
第三方面,本申请提供了一种用于处理网络切片实例的装置,该装置包括:接收单元,用于接收第二网络设备发送的第一消息,其中,所述第一消息用于请求所述接收单元所属的第一网络设备对所述第一网络设备所管理的第一网络切片子网实例NSSI进行修改,所述第一NSSI是不同网络设备管理的多个网络切片实例所共享的;处理单元,用于判断是 否允许修改所述第一NSSI,并根据所述判断的结果进行后续处理。
在一种可能的设计中,所述处理模块在根据所述判断的结果进行后续处理时,具体用于:若判断出允许修改所述第一NSSI,对所述第一NSSI进行修改。
在一种可能的设计中,所述处理模块在根据所述判断的结果进行后续处理时,具体用于:若判断出不允许修改所述第一NSSI,创建第二NSSI。
在一种可能的设计中,所述处理模块还用于:在创建第二NSSI之后,所述第二NSSI进行配置。
在一种可能的设计中,该装置还包括发送单元,用于向所述第二网络设备发送第二消息。
在一种可能的设计中,所述发送单元还用于:判断出所述第一NSSI不允许进行修改之后,向所述第二网络设备发送第三消息,其中,所述第三消息中携带需要创建第二NSSI的相关需求信息,用于指示所述第一网络设备对所述第二NSSI的相关需求的支持情况;所述接收单元接收所述第二网络设备发送的第四消息,其中,所述第四消息中携带指示信息,用于指示所述第一网络设备是否允许创建所述第二NSSI,或者是否接受所述第三消息中携带的创建所述第二NSSI的相关需求信息。
在一种可能的设计中,若所述第四消息携带的针对第二NSSI的相关需求的指示信息为否定指示,则所述第四消息中还包括所述第二网络设备建议的创建所述第二NSSI的相关需求信息。
在一种可能的设计中,所述第一消息中包括所述第一NSSI的标识信息、以及更新后的所述第一NSSI的相关需求信息,所述相关需求信息包括服务水平协议、关键绩效指标、网络切片子网的类型、服务质量、网络拓扑、资源需求以及网络功能相关需求等参数中的至少一个。
在一种可能的设计中,所述第一消息中还包括所述第一NSSI所属的NSI的标识信息。
在一种可能的设计中,所述第二消息中包括所述第二NSSI标识信息。
在一种可能的设计中,所述第二消息中包括所述第二NSSI所属的NSI的标识信息。
在一种可能的设计中,所述处理单元对所述第二NSSI进行配置时,具体用于:
将所述第二NSSI加入到所述第一NSSI所属的NSI中,并将所述第一NSSI从所述NSI中删除。
第四方面,本申请提供了一种用于处理网络切片实例的装置,该装置包括:发送单元,用于向第一网络设备发送第一消息,其中,所述第一消息用于请求所述第一网络设备对所述第一网络设备所管理的第一网络切片子网实例NSSI进行修改,所述第一NSSI是不同网络设备管理的多个网络切片实例所共享的;接收单元,用于接收所述第一网络设备发送的第二消息。
在一种可能的设计中,所述接收单元还用于:接收所述第一网络设备发送的第三消息,其中,所述第三消息中携带需要创建第二NSSI的相关需求信息,用于指示所述第一网络设备对所述第二NSSI的相关需求的支持情况;所述发送单元还用于向所述第一网络设备发送第四消息,其中,所述第四消息中携带指示信息,用于指示所述第一网络设备是否允许创建所述第二NSSI,或者是否接受所述第三消息中携带的创建所述第二NSSI的相关需求信息。
在一种可能的设计中,若所述第四消息携带的针对第二NSSI的相关需求的指示信息 为否定指示,则所述第四消息中还包括所述第二网络设备建议的创建所述第二NSSI的相关需求信息。
第五方面,本申请提供了一种用于处理网络切片实例的装置,包括通信接口、处理器和存储器,其中:通信接口、存储器以及处理器,存储器用于存储处理器所需执行的程序代码。通信接口用于接收客户端发送的用户任务。处理器用于执行存储器所存储的程序代码,具体用于执行上述第一至第二方面或第一至第二方面的任一种可能的实现方式中的方法。
第六方面,本申请实施例还提供了一种***,有益效果可以参见上个各个方面的描述此处不再赘述,所述***包括第一网络设备和第二网络设备。
其中,所述第二网络设备,用于向所述第一网络设备发送第一消息,其中,所述第一消息用于请求所述第一网络设备对所述第一网络设备所管理的第一网络切片子网实例NSSI进行修改,所述第一NSSI是不同网络设备管理的多个网络切片实例所共享的;
所述第一网络设备,用于接收所述第一消息;判断是否允许修改所述第一NSSI;以及根据所述判断的结果进行后续处理。
在一种可能的设计中,若所述第一网络设备判断出允许修改所述第一NSSI,所述第一网络设备在根据所述判断的结果进行后续处理时,可以对所述第一NSSI进行修改。
在一种可能的设计中,若所述第一网络设备判断出不允许修改所述第一NSSI,所述第一网络设备在根据所述判断的结果进行后续处理时,可以创建第二NSSI。
在一种可能的设计中,所述第一网络设备还可以向所述第二网络设备发送第二消息,所述第二消息为针对所述第一消息的响应;所述第二网络设备则可以接收所述第二消息。
在一种可能的设计中,所述第一网络设备在创建第二NSSI之后,还可以对所述第二NSSI进行配置。
在一种可能的设计中,所述第一网络设备判断出所述第一NSSI不允许进行修改之后,可以向所述第二网络设备发送第三消息,其中,所述第三消息中携带需要创建第二NSSI的相关需求信息,用于指示所述第一网络设备对所述第二NSSI的相关需求的支持情况。
之后,所述第二网络设备接收所述第三消息;还可以向所述第一网络设备发送第四消息,其中,所述第四消息中携带指示信息,用于指示所述第一网络设备是否允许创建所述第二NSSI,或者是否接受所述第三消息中携带的创建所述第二NSSI的相关需求信息;
所述第一网络设备可以接收所述第四消息。
在一种可能的设计中,在所述第二网络设备不接受所述第三消息中携带的创建所述第二NSSI的相关需求信息的情况下,所述第四消息携带的针对第二NSSI的相关需求的指示信息为否定指示,所述第四消息中还包括所述第二网络设备建议的创建所述第二NSSI的相关需求信息。
第七方面,本申请还提供了一种计算机可读存储介质,用于存储为执行上述第一至第二方面或第一至第二方面的任一种可能的实现方式中设计的功能所用的计算机软件指令,其包含用于执行上述第一至第二方面或第一至第二方面的任一种可能的实现方式中设计的程序。
第八方面,本申请还提供一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述第一至第二方面或第一至第二方面的任一种可能的实现方式中的方法。
图1为本申请提供的一种NSSI共享场景示意图;
图2为本申请提供的另一种NSSI共享场景示意图;
图3为本申请提供的一种***架构示意图;
图4为本申请提供的一种处理网络切片实例的方法流程图;
图5为本申请提供的另一种处理网络切片实例的方法流程图;
图6为本申请提供的又一种处理网络切片实例的方法流程图;
图7为本申请提供的再一种处理网络切片实例的方法流程图;
图8为本申请提供的一种用于处理网络切片实例的装置示意图;
图9为本申请提供的另一种用于处理网络切片实例的装置示意图;
图10为本申请提供的一种用于处理网络切片实例的装置的硬件结构图。
为了使本申请的目的、技术方案和优点更加清楚,下面将结合附图对本申请作进一步地详细描述。
本申请提供一种处理网络切片实例的方法及装置,用以解决现有技术中存在的至少两个由不同NSMF所管理的NSI共享NSSI时,如何对共享NSSI进行修改,而不对其他NSI造成负面影响的问题。其中,方法和装置是基于同一发明构思的,由于方法及装置解决问题的原理相似,因此装置与方法的实施可以相互参见,重复之处不再赘述。
本申请实施例中,第二网络设备主要负责对网络切片实例的生命周期、性能、故障等进行管理,编排网络切片实例的组成,分解网络切片实例的需求为各网络切片子网实例和/或网络功能的需求,向各网络切片子网的管理实体发送网络切片子网实例管理请求。示例性地,第二网络设备可以是网络切片管理功能(network slice management function,NSMF)。第一网络设备主要负责接收第二网络设备发送的网络切片子网需求,对网络切片子网实例进行管理,编排NSSI的组成。示例性地,第一网络设备可以是网络切片子网管理功能(network slice subnet management function,NSSMF)。可选的,所述第二网络设备还可以包含其他功能模块,NSMF只是第二网络设备的一部分;所述第一网络设备还可以包含其他功能模块,NSSMF只是第一网络设备的一部分。现有技术中有两种场景,场景一、如图1所示,标识为A的NSI具有三个NSSI,分别是NSSI1、NSSI2和NSSI3,标识为B的NSI具有三个NSSI,分别是NSSI1、NSSI4和NSSI5;其中NSSI1为NSI A和NSI B所共享,并且NSI A和NSI B都被NSMF所管理。换言之,NSSI1是同一NSMF管理的多个网络切片实例所共享的。此时,NSMF预先知道NSSI的所有共享情况下,即共享该NSSI的所有NSI都属于同一个NSMF所管理,当共享该NSSI的任一NSI需要修改该NSSI时,NSMF将对该NSSI的修改请求消息发送给该NSSI所对应的NSSMF,该NSSMF依据该修改请求消息修改该NSSI,但可能会对其它共享该NSSI的NSI造成负面的影响。场景二、如图2所示,标识为A的NSI具有NSSI1、NSSI2和NSSI3,标识为B的NSI具有NSSI1、NSSI4和NSSI5;其中NSSI1为NSI A和NSI B所共享。NSI A被NSMF1管理,NSI B被NSMF2管理。换言之,NSSI1是不同NSMF管理的多个网络切片实例所共享的。此时,当共享该NSSI的NSI属于不同NSMF所管理时,管理该待修改NSI的NSMF不知道该 NSSI的共享情况,即NSMF认为该NSSI是NSI所特有的,从而向NSSMF发送修改请求,该NSSMF依据该修改请求修改该NSSI。但由于该NSSI是多个NSI共享的,当其它NSI不允许修改该NSSI,而该NSSMF依据该修改请求修改了该NSSI,会对其它共享该NSSI的NSI造成负面的影响。图3示出了NSMF与NSSMF之间的***架构图。
本申请中所涉及的多个,是指两个或两个以上。
另外,需要理解的是,在本申请的描述中,“第一”、“第二”等词汇,仅用于区分描述的目的,而不能理解为指示或暗示相对重要性,也不能理解为指示或暗示顺序。
本申请实施例中第一网络设备根据接收的第一消息判断是否可以修改第一NSSI,根据判断结果进行后续处理,所述第一模块通过判断的过程可以避免当第一NSSI是多个NSI共享时,直接修改第一NSSI对第二网络设备管理的NSI之外的其他NSI造成负面影响的问题。
下面结合附图对本申请提供的修改网络切片实例的方案进行具体说明。
参见图4,为本申请提供的一种处理网络切片实例的方法流程图,该方法包括:
S401,第一网络设备接收第二网络设备发送的第一消息,其中,所述第一消息用于请求所述第一网络设备对所述第一网络设备所管理的第一NSSI进行修改,所述第一NSSI是不同网络设备管理的多个网络切片实例所共享的。
具体的,所述第一消息中包括所述第一NSSI的标识信息、以及更新后的所述第一NSSI的相关需求信息,所述相关需求信息包括服务水平协议(service level agreement,SLA)、网络关键性能指标(network KPI)、网络切片子网的类型、服务质量(quality of service)、网络拓扑(network topology)、资源需求(resource requirements)以及网络功能相关需求等参数中的至少一个。可选的,所述第一消息称为修改请求消息。所述修改请求消息中还可包括所述第一NSSI所属的NSI的标识信息。其中,所述Network KPI包括:时延(latency),覆盖(coverage),容量(capacity),吞吐量(throughput),可靠性(reliability),上报成功率(report success ratio),下发成功率(command success ratio)中的至少一个参数。其中,上报成功率可以指上行包发送成功的比例;下发成功率可以指下行包发送成功的比例;覆盖可以指终端的分部区域;容量可以指可容纳的终端数量。所述网络切片子网的类型,包括增强移动宽带(eMBB,enhanced Mobile Broadband),超可靠低时延通信(URLLC,Ultra-Reliable Low Latency Communications),海量物联网(MIoT,Massive Internet of Things)等;网络功能相关需求包括类型(type),容量(capacity),位置(location),能力(capability)等。
S402,所述第一网络设备判断是否允许修改所述第一NSSI。
可选的,所述第一网络设备判断出允许修改所述第一NSSI,或者,所述第一网络设备判断出不允许修改所述第一NSSI。
S403,所述第一网络设备根据所述判断的结果进行后续处理。
可选的,若所述第一网络设备判断出允许修改所述第一NSSI,所述第一网络设备对所述第一NSSI进行修改;若所述第一网络设备判断出不允许修改所述第一NSSI,所述第一网络设备创建第二NSSI;所述第一网络设备对所述第二NSSI进行配置,具体的,所述第一网络设备将所述第二NSSI加入到所述第一NSSI所属的NSI中,并将所述第一NSSI从所述NSI中删除。
在一种可能的实现方式中,在步骤S403之后,该方法还包括:所述第一网络设备向所述第二网络设备发送第二消息,以对第一消息作出响应。可选的,所述第二消息称为修 改响应消息。
通过本申请提供的方案,第一网络设备根据接收的第一消息判断是否可以修改第一NSSI,根据判断结果进行后续处理,通过判断的过程可以避免当第一NSSI是多个NSI共享时,直接修改第一NSSI对共享第一NSSI的由其他SMF管理的NSI造成负面影响的问题。
在一种可能的实现方式中,所述第一网络设备判断出所述第一NSSI不允许进行修改之后,该方法还包括:所述第一网络设备向所述第二网络设备发送第三消息,其中,所述第三消息中携带需要创建第二NSSI的相关需求信息,用于指示所述第一网络设备对所述第二NSSI的相关需求的支持情况;所述第一网络设备接收所述第二网络设备发送的第四消息,其中,所述第四消息中携带指示信息,用于指示是否允许所述第一网络设备创建所述第二NSSI,或者是否接受所述第三消息中携带的创建所述第二NSSI的相关需求信息。可选的,所述第三消息称为协商请求消息,第四消息称为协商响应消息。
可选的,若所述协商响应消息携带的针对NSSI的相关需求的指示信息为否定指示,则所述协商响应消息中还包括所述第二网络设备建议的创建所述第二NSSI的相关需求信息。
可选的,所述第二消息中包括所述第二NSSI标识信息、所述第二NSSI所属的NSI的标识信息。
下面通过三个具体实施例,对本申请实施例进行详细的说明。
具体实施例一,如图5所示:
S501、NSMF向NSSMF发送修改请求消息,请求对第一NSSI进行修改。
具体的,该修改请求消息中包括如下参数:待修改的第一网络切片子网实例标识,例如,NSSI ID,更新后的NSSI的相关需求。可选地,还可以包括该第一NSSI所属的网络切片实例标识,例如,NSI ID。触发所述NSMF修改第一NSSI的因素既可以是NSMF接收外部请求,例如从用户服务管理功能接收相关网络切片实例修改请求,也可以是NSMF依据网络切片实例的运行状况和预先设定的规则策略,自主判断需修改网络切片实例;并且进一步地判断需要修改该网络切片实例中的网络切片子网实例。
S502、该NSSMF接收该修改请求消息后,该NSSMF判断允许修改所述第一NSSI,该NSSMF对第一NSSI进行修改。
可选的,若第一NSSI只属于一个NSI,或者如背景技术中场景一和场景二中所描述的情况,共享该第一NSSI的所有NSI都允许修改该第一NSSI,则NSSMF判断允许修改第一NSSI。示例性地,由于第一NSSI属于多个NSI,因此管理第一NSSI的NSSMF可以接收多个NSMF的管理,当NSSMF判断出更新后的第一NSSI的相关需求在所述多个NSI的设定范围内时,修改所述第一NSSI不会对所述多个NSI造成负面影响,则NSSMF判断允许修改第一NSSI。在允许修改NSSI的情况下,NSSMF根据修改请求消息中更新后的网络切片子网需求,对该NSSI进行修改。
S503、该NSSMF对该第一NSSI修改完成后,向NSMF发送修改响应消息。
可选地,该修改响应消息中可以携带有是否修改成功的指示信息。例如,携带“1”代表修改成功,携带“0”代表修改失败。
具体实施例二,如图6所示:
S601、NSMF向NSSMF发送修改请求消息,请求对第一NSSI进行修改。
具体的,该修改请求消息包括的参数如实施例1所示,此处不再敷述。
S602、该NSSMF接收修改请求消息后,NSSMF判断不允许修改第一NSSI。
可选的,若更新后的网络切片子网相关需求超过了该第一NSSI所允许的修改范围,或者共享该第一NSSI的由其他NSMF管理的一个或多个NSI不允许修改该NSSI,则NSSMF判断不允许修改该第一NSSI。示例性地,由于第一NSSI属于多个NSI,因此管理第一NSSI的NSSMF可以接收多个NSMF的管理,当NSSMF判断出更新后的第一NSSI的相关需求超出所述多个NSI中至少一个NSI的设定范围时,修改所述第一NSSI会对所述多个NSI中至少一个NSI造成负面影响,则所述NSSMF判断不允许修改所述第一NSSI。
S603、该NSSMF根据修改请求消息中的更新后的网络切片子网相关需求,创建一个第二NSSI。
S604、该NSSMF对第二NSSI进行相关配置。
具体的,根据第一NSSI所属的第一NSI ID,该NSSMF将新创建的第二NSSI加入到所述第一NSI中。例如,NSSMF对新创建的第二NSSI配置第二NSSI ID和第一NSI ID的映射关系,将该第二NSSI加入到第一NSI中。可选地,NSSMF删除第一NSSI ID和第一NSI ID的映射关系,将第一NSSI从第一NSI中删除。该新创建的第二NSSI只属于第一NSI,而不属于共享第一NSSI的其他NSI。
S605、该NSSMF向NSMF发送修改响应消息。
具体的,该修改响应消息中包含新创建的第二NSSI标识,例如,第二NSSI ID。可选地,该修改响应消息中还可以包括该第二NSSI所属的网络切片实例标识,例如,第一NSI ID。
具体实施例三,如图7所示:
S701、NSMF向NSSMF发送修改请求消息,请求对第一NSSI进行修改。
具体的,该修改请求消息包括的参数如实施例1所示,此处不再敷述。
S702、该NSSMF接收修改请求消息后,NSSMF判断不允许修改第一NSSI。
具体的,若更新后的网络切片子网相关需求超过了该第一NSSI所允许的修改范围,或者共享该第一NSSI的由其他NSMF管理的一个或多个NSI不允许修改该NSSI,则NSSMF判断不允许修改该第一NSSI。
S703、该NSSMF向该NSMF发送协商请求消息。
具体的,该协商请求消息中携带NSSI的相关需求信息,用于指示该NSSMF对NSSI的相关需求的支持情况。可选地,该协商请求消息还携带有是否允许创建新的网络切片子网实例的指示信息。
S704、该NSMF向该NSSMF发送协商响应消息。
具体的,该协商响应消息中携带有相关的指示信息,若该协商响应消息中携带的针对NSSI的相关需求的指示信息为肯定指示时,该NSMF接受NSSMF上报的网络切片子网相关需求,若该协商响应消息中携带的针对NSSI的相关需求的指示信息为否定指示时,该NSMF不接受NSSMF上报的网络切片子网相关需求。进一步地,如果该NSMF不接受NSSMF上报的网络切片子网相关需求,则该协商响应消息中携带的指示信息中还可以包含有NSMF所建议的网络切片子网相关需求信息。可选的,NSSMF和NSMF可以经过多次的协商,即重复步骤S703与S704,以确定最终的网络切片子网的相关需求信息。
可选地,当在步骤S703的协商请求消息携带有是否允许创建新的子网实例的指示信 息时,对于允许的情况,在本步骤中该NSMF和该NSSMF执行上述的协商过程;对于不允许的情况,该NSMF不允许该NSSMF创建新的NSSI,协商响应消息中可以携带修改失败的指示信息。
S705、该NSSMF根据协商响应消息中的更新后的网络切片子网相关需求,创建一个新的第二NSSI。
S706、该NSSMF对第二NSSI进行相关配置。
具体的,根据第一NSSI所属的第一NSI ID,该NSSMF将新创建的第二NSSI加入到第一NSI中。例如,NSSMF对新创建的第二NSSI配置第二NSSI ID和第一NSI ID的映射关系,将该第二NSSI加入到第一NSI中。可选地,NSSMF删除第一NSSI ID和第一NSI ID的映射关系,将第一NSSI从第一NSI中删除。该新创建的第二NSSI只属于需第一NSI,而不属于共享第一NSSI的其他NSI。
S707、该NSSMF向NSMF发送修改响应消息。
具体的,该修改响应消息中包含新创建的第二NSSI标识,例如,第二NSSI ID。可选地,该修改响应消息中还可以包括该第二NSSI所属的网络切片实例标识,例如,第一NSI ID。可选地,当在步骤S703的协商请求消息携带不允许创建新的子网实例的指示信息时,该修改响应消息为否定。
基于与方法实施例同样的发明构思,本申请还提供了一种用于处理网络切片实例的装置,如图8所示,该装置包括:
接收单元801,用于接收第二网络设备发送的第一消息,其中,所述第一消息用于请求所述接收单元所属的第一网络设备对所述第一网络设备所管理的第一网络切片子网实例NSSI进行修改,所述第一NSSI是不同网络设备管理的多个网络切片实例所共享的。
处理单元802,用于判断是否允许修改所述第一NSSI,并根据所述判断的结果进行后续处理。
通过本申请提供的方案,第一网络设备根据接收的第一消息判断是否可以修改第一NSSI,根据判断结果进行后续处理,所述第一模块通过判断的过程可以避免当第一NSSI是多个NSI共享时,直接修改第一NSSI对第二网络设备管理的NSI之外的其他NSI造成负面影响的问题。
在一种可能的实现方式中,所述处理模块在根据所述判断的结果进行后续处理时,具体用于:若判断出允许修改所述第一NSSI,或者,所述处理模块在根据所述判断的结果进行后续处理时,具体用于:若判断出不允许修改所述第一NSSI,创建第二NSSI;在创建第二NSSI之后,对所述第二NSSI进行配置。
具体的,所述处理单元将所述第二NSSI加入到所述第一NSSI所属的NSI中,并将所述第一NSSI所述NSI中删除。
在一种可能的实现方式中,该装置还包括发送单元,用于向所述第二网络设备发送第二消息。
可选的,所述发送单元还用于:判断出所述第一NSSI不允许进行修改之后,向所述第二网络设备发送第三消息,其中,所述第三消息中携带需要创建第二NSSI的相关需求信息,用于指示所述第一网络设备对所述第二NSSI的相关需求的支持情况;所述接收单元接收所述第二网络设备发送的第四消息,其中,所述第四消息中携带指示信息,用于指示所述第一网络设备是否允许创建所述第二NSSI,或者是否接受所述第三消息中携带的创 建所述第二NSSI的相关需求信息。
可选的,若所述协商响应消息携带的针对NSSI的相关需求的指示信息为否定指示,则所述协商响应消息中还包括所述第二网络设备建议的创建所述第二NSSI的相关需求信息。
在一种可能的情况下,所述第一消息中包括所述第一NSSI的标识信息、以及更新后的所述第一NSSI的相关需求信息,所述相关需求信息包括服务水平协议、关键绩效指标、网络切片子网的类型、服务质量、网络拓扑、资源需求以及网络功能相关需求等参数中的至少一个。所述第一消息中还包括所述第一NSSI所属的NSI的标识信息。
可选的,所述第二消息中包括所述第二NSSI标识信息。
可选的,所述第二消息中包括所述第二NSSI所属的NSI的标识信息。
基于与方法实施例同样的发明构思,本申请还提供了另一种用于处理网络切片实例的装置,如图9所示,该装置包括:
发送单元901,用于向第一网络设备发送第一消息,其中,所述第一消息用于请求所述第一网络设备对所述第一网络设备所管理的第一网络切片子网实例NSSI进行修改,所述第一NSSI是不同网络设备管理的多个网络切片实例所共享的。
接收单元902,用于接收所述第一网络设备发送的第二消息。
在一种可能的情况下,所述发送单元向第一网络设备发送第一消息之后,所述接收单元还用于:接收所述第一网络设备发送的第三消息,其中,所述第三消息中携带需要创建第二NSSI的相关需求信息,用于指示所述第一网络设备对所述第二NSSI的相关需求的支持情况;所述发送单元还用于向所述第一网络设备接收发送第四消息,其中,所述第四消息中携带指示信息,用于指示所述第一网络设备是否允许创建所述第二NSSI,或者是否接受所述第三消息中携带的创建所述第二NSSI的相关需求信息。
本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,另外,在本申请各个实施例中的各功能模块可以集成在一个处理器中,也可以是单独物理存在,也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。
其中,集成的模块既可以采用硬件的形式实现时,如图10所示,修改网络切片实例的装置可以包括处理器1002。上述模块对应的实体的硬件可以为处理器1002。处理器1002,可以是一个中央处理模块(英文:central processing unit,简称CPU),或者为数字处理模块等等。修改网络切片实例的装置还可以包括通信接口1001,处理器1002通过通信接口1001收发数据。该装置还包括:存储器1003,用于存储处理器1002执行的程序。存储器1003可以是非易失性存储器,比如硬盘(英文:hard disk drive,缩写:HDD)或固态硬盘(英文:solid-state drive,缩写:SSD)等,还可以是易失性存储器(英文:volatile memory),例如随机存取存储器(英文:random-access memory,缩写:RAM)。存储器1003是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。处理器1002用于执行存储器1003存储的程序代码,具体可以用于执行图4所示实施例所述的方法。
本申请实施例中不限定上述通信接口1001、处理器1002以及存储器1003之间的具体连接介质。本申请实施例在图10中以存储器1003、处理器1002以及通信接口1001之间通过总线1004连接,总线在图10中以粗线表示,其它部件之间的连接方式,仅是进行示 意性说明,并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示,图10中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
本发明实施例还提供了一种计算机可读存储介质,用于存储为执行上述处理器所需执行的计算机软件指令,其包含用于执行上述处理器所需执行的程序。
本领域内的技术人员应明白,本申请的实施例可提供为方法、***、或计算机程序产品。因此,本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然,本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样,倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。
Claims (34)
- 一种处理网络切片实例的方法,其特征在于,该方法包括:第一网络设备接收第二网络设备发送的第一消息,其中,所述第一消息用于请求所述第一网络设备对所述第一网络设备所管理的第一网络切片子网实例NSSI进行修改,所述第一NSSI是不同网络设备管理的多个网络切片实例所共享的;所述第一网络设备判断是否允许修改所述第一NSSI;以及所述第一网络设备根据所述判断的结果进行后续处理。
- 如权利要求1所述的方法,其特征在于,若所述第一网络设备判断出允许修改所述第一NSSI,所述第一网络设备根据所述判断的结果进行后续处理包括:所述第一网络设备对所述第一NSSI进行修改。
- 如权利要求1或2所述的方法,其特征在于,若所述第一网络设备判断出不允许修改所述第一NSSI,所述第一网络设备根据所述判断的结果进行后续处理包括:所述第一网络设备创建第二NSSI。
- 如权利要求1所述的方法,其特征在于,所述第一网络设备根据所述判断的结果进行后续处理之后,该方法还包括:所述第一网络设备向所述第二网络设备发送第二消息,所述第二消息为针对所述第一消息的响应。
- 如权力要求3所述的方法,其特征在于,若所述第一网络设备创建第二NSSI之后,该方法还包括:所述第一网络设备对所述第二NSSI进行配置。
- 如权利要求3所述的方法,其特征在于,所述第一网络设备判断出所述第一NSSI不允许进行修改之后,该方法还包括:所述第一网络设备向所述第二网络设备发送第三消息,其中,所述第三消息中携带需要创建第二NSSI的相关需求信息,用于指示所述第一网络设备对所述第二NSSI的相关需求的支持情况;所述第一网络设备接收所述第二网络设备发送的第四消息,其中,所述第四消息中携带指示信息,用于指示所述第一网络设备是否允许创建所述第二NSSI,或者是否接受所述第三消息中携带的创建所述第二NSSI的相关需求信息。
- 如权利要求6所述的方法,其特征在于,若所述第四消息携带的针对第二NSSI的相关需求的指示信息为否定指示,则所述第四消息中还包括所述第二网络设备建议的创建所述第二NSSI的相关需求信息。
- 如权利要求1所述的方法,其特征在于,所述第一消息中包括所述第一NSSI的标识信息、以及更新后的所述第一NSSI的相关需求信息,所述相关需求信息包括服务水平协议、关键绩效指标、网络切片子网的类型、服务质量、网络拓扑、资源需求以及网络功能相关需求等参数中的至少一个。
- 如权利要求5所述的方法,其特征在于,所述第一网络设备对所述第二NSSI进行配置,包括:所述第一网络设备将所述第二NSSI加入到所述第一NSSI所属的NSI中,并将所述第一NSSI从所述NSI中删除。
- 一种处理网络切片实例的方法,其特征在于,该方法包括:第二网络设备向第一网络设备发送第一消息,其中,所述第一消息用于请求所述第一网络设备对所述第一网络设备所管理的第一网络切片子网实例NSSI进行修改,所述第一NSSI是不同网络设备管理的多个网络切片实例所共享的;所述第二网络设备接收所述第一网络设备发送的第二消息,所述第二消息为针对所述第一消息的响应。
- 如权利要求10所述的方法,其特征在于,所述第二网络设备向第一网络设备发送第一消息之后,该方法还包括:所述第二网络设备接收所述第一网络设备发送的第三消息,其中,所述第三消息中携带需要创建第二NSSI的相关需求信息,用于指示所述第一网络设备对所述第二NSSI的相关需求的支持情况;所述第二网络设备向所述第一网络设备发送第四消息,其中,所述第四消息中携带指示信息,用于指示所述第一网络设备是否允许创建所述第二NSSI,或者是否接受所述第三消息中携带的创建所述第二NSSI的相关需求信息。
- 如权利要求11所述的方法,其特征在于,所述第二网络设备不接受所述第三消息中携带的创建所述第二NSSI的相关需求信息时,该方法还包括:所述第二网络设备向所述第一网络设备发送的第四消息携带的针对第二NSSI的相关需求的指示信息为否定指示,所述第四消息中还包括所述第二网络设备建议的创建所述第二NSSI的相关需求信息。
- 一种用于处理网络切片实例的装置,其特征在于,该装置包括:接收单元,用于接收第二网络设备发送的第一消息,其中,所述第一消息用于请求所述接收单元所属的第一网络设备对所述第一网络设备所管理的第一网络切片子网实例NSSI进行修改,所述第一NSSI是不同网络设备管理的多个网络切片实例所共享的;处理单元,用于判断是否允许修改所述第一NSSI,并根据所述判断的结果进行后续处理。
- 如权利要求13所述的装置,其特征在于,所述处理模块在根据所述判断的结果进行后续处理时,具体用于:若判断出允许修改所述第一NSSI,对所述第一NSSI进行修改。
- 如权利要求13或14所述的装置,其特征在于,所述处理模块在根据所述判断的结果进行后续处理时,具体用于:若判断出不允许修改所述第一NSSI,创建第二NSSI。
- 如权利要求13所述的装置,其特征在于,该装置还包括发送单元,用于向所述第二网络设备发送第二消息,所述第二消息为针对所述第一消息的响应。
- 如权利要求15所述的装置,其特征在于,所述处理模块还用于:在创建第二NSSI之后,对所述第二NSSI进行配置。
- 如权利要求15所述的装置,其特征在于,所述发送单元还用于:判断出所述第一NSSI不允许进行修改之后,向所述第二网络设备发送第三消息,其中,所述第三消息中携带需要创建第二NSSI的相关需求信息,用于指示所述第一网络设备对所述第二NSSI的相关需求的支持情况;所述接收单元接收所述第二网络设备发送的第四消息,其中,所述第四消息中携带指 示信息,用于指示所述第一网络设备是否允许创建所述第二NSSI,或者是否接受所述第三消息中携带的创建所述第二NSSI的相关需求信息。
- 如权利要求18所述的装置,其特征在于,若所述第四消息携带的针对第二NSSI的相关需求的指示信息为否定指示,则所述第四消息中还包括所述第二网络设备建议的创建所述第二NSSI的相关需求信息。
- 如权利要求13所述的装置,其特征在于,所述第一消息中包括所述第一NSSI的标识信息、以及更新后的所述第一NSSI的相关需求信息,所述相关需求信息包括服务水平协议、关键绩效指标、网络切片子网的类型、服务质量、网络拓扑、资源需求以及网络功能相关需求等参数中的至少一个。
- 如权利要求15所述的装置,其特征在于,所述第一网络设备对所述第二NSSI进行配置,包括:所述第一网络设备将所述第二NSSI加入到所述第一NSSI所属的NSI中,并将所述第一NSSI从所述NSI中删除。
- 一种用于处理网络切片实例的装置,其特征在于,该装置包括:发送单元,用于向第一网络设备发送第一消息,其中,所述第一消息用于请求所述第一网络设备对所述第一网络设备所管理的第一网络切片子网实例NSSI进行修改,所述第一NSSI是不同网络设备管理的多个网络切片实例所共享的;接收单元,用于接收所述第一网络设备发送的第二消息,所述第二消息为针对所述第一消息的响应。
- 如权利要求22所述的装置,其特征在于,所述接收单元还用于接收所述第一网络设备发送的第三消息,其中,所述第三消息中携带需要创建第二NSSI的相关需求信息,用于指示所述第一网络设备对所述第二NSSI的相关需求的支持情况;所述发送单元还用于向所述第一网络设备发送第四消息,其中,所述第四消息中携带指示信息,用于指示所述第一网络设备是否允许创建所述第二NSSI,或者是否接受所述第三消息中携带的创建所述第二NSSI的相关需求信息。
- 如权利要求23所述的装置,其特征在于,所述第二网络设备不接受所述第三消息中携带的创建所述第二NSSI的相关需求信息时,还包括:所述第二网络设备向所述第一网络设备发送的第四消息携带的针对第二NSSI的相关需求的指示信息为否定指示,所述第四消息中还包括所述第二网络设备建议的创建所述第二NSSI的相关需求信息。
- 一种用于处理网络切片实例的装置,其特征在于,包括通信接口、处理器和存储器,其中:所述存储器,存储有软件程序;所述处理器,用于调用并执行所述存储器中存储的软件程序,通过所述通信接口收发数据来实现如权利要求1至12中任一项所述的方法。
- 一种***,其特征在于,所述***包括第一网络设备和第二网络设备;所述第二网络设备,用于向所述第一网络设备发送第一消息,其中,所述第一消息用于请求所述第一网络设备对所述第一网络设备所管理的第一网络切片子网实例NSSI进行修改,所述第一NSSI是不同网络设备管理的多个网络切片实例所共享的;所述第一网络设备,用于接收所述第一消息;判断是否允许修改所述第一NSSI;以及备根据所述判断的结果进行后续处理。
- 如权利要求26所述的***,其特征在于,若所述第一网络设备判断出允许修改所述第一NSSI,所述第一网络设备在根据所述判断的结果进行后续处理时,具体用于:对所述第一NSSI进行修改
- 如权利要求26或27所述的***,其特征在于,若所述第一网络设备判断出不允许修改所述第一NSSI,所述第一网络设备在根据所述判断的结果进行后续处理时,具体用于:创建第二NSSI。
- 如权利要求26所述的***,其特征在于,所述第一网络设备,还用于:向所述第二网络设备发送第二消息,所述第二消息为针对所述第一消息的响应;所述第二网络设备,还用于接收所述第二消息。
- 如权利要求28所述的***,其特征在于,所述第一网络设备在创建第二NSSI之后,还用于:对所述第二NSSI进行配置。
- 如权利要求28所述的***,其特征在于,所述第一网络设备判断出所述第一NSSI不允许进行修改之后,还用于:向所述第二网络设备发送第三消息,其中,所述第三消息中携带需要创建第二NSSI的相关需求信息,用于指示所述第一网络设备对所述第二NSSI的相关需求的支持情况;所述第二网络设备,还用于接收所述第三消息;以及向所述第一网络设备发送第四消息,其中,所述第四消息中携带指示信息,用于指示所述第一网络设备是否允许创建所述第二NSSI,或者是否接受所述第三消息中携带的创建所述第二NSSI的相关需求信息;所述第一网络设备,还用于接收所述第四消息。
- 如权利要求31所述的***,其特征在于,所述第二网络设备不接受所述第三消息中携带的创建所述第二NSSI的相关需求信息时,所述第四消息携带的针对第二NSSI的相关需求的指示信息为否定指示,所述第四消息中还包括所述第二网络设备建议的创建所述第二NSSI的相关需求信息。
- 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质存储有计算机指令,当所述指令在计算机上运行时,使得计算机执行如权利要求1至12中任一项所述的方法。
- 一种包含指令的计算机程序产品,其特征在于,当其在计算机上运行时,使得计算机执行如权利要求1至12中任一项所述的方法。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP18854430.8A EP3664373A4 (en) | 2017-09-08 | 2018-08-30 | PROCESS, DEVICE AND SYSTEM FOR PROCESSING NETWORK TRENCH INSTANCE |
US16/811,810 US11240745B2 (en) | 2017-09-08 | 2020-03-06 | Network slice instance processing method and apparatus, and system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710807964.0A CN109474449A (zh) | 2017-09-08 | 2017-09-08 | 一种处理网络切片实例的方法及装置 |
CN201710807964.0 | 2017-09-08 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/811,810 Continuation US11240745B2 (en) | 2017-09-08 | 2020-03-06 | Network slice instance processing method and apparatus, and system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019047769A1 true WO2019047769A1 (zh) | 2019-03-14 |
Family
ID=65634730
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/103344 WO2019047769A1 (zh) | 2017-09-08 | 2018-08-30 | 一种处理网络切片实例的方法、装置及*** |
Country Status (4)
Country | Link |
---|---|
US (1) | US11240745B2 (zh) |
EP (1) | EP3664373A4 (zh) |
CN (1) | CN109474449A (zh) |
WO (1) | WO2019047769A1 (zh) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3534567B1 (en) | 2016-10-31 | 2021-12-15 | Huawei Technologies Co., Ltd. | Network slice management method, management unit, and system |
WO2018094667A1 (zh) * | 2016-11-24 | 2018-05-31 | 华为技术有限公司 | 一种管理方法、管理单元及*** |
EP3721662B1 (en) * | 2017-12-06 | 2023-07-05 | Telefonaktiebolaget LM Ericsson (publ) | First node, second node, and methods performed thereby for managing a network slice instance |
US11070997B2 (en) * | 2018-02-22 | 2021-07-20 | Intel Corporation | Performance measurement job control for 5G networks and network slicing |
CN112105026B (zh) * | 2019-06-17 | 2022-07-12 | 华为技术有限公司 | 一种授权控制的方法、装置以及存储介质 |
US11201783B2 (en) * | 2019-06-26 | 2021-12-14 | Vmware, Inc. | Analyzing and configuring workload distribution in slice-based networks to optimize network performance |
CN114827980B (zh) * | 2021-01-21 | 2024-06-07 | ***通信有限公司研究院 | Nssi更新方法、装置及nssmf实体 |
US11743125B2 (en) * | 2021-05-12 | 2023-08-29 | DISH Wireless L.L.C | Cellular network cloud application controlled slice management |
CN116418669A (zh) * | 2021-12-31 | 2023-07-11 | ***通信有限公司研究院 | 一种网络切片的处理方法、网元及存储介质 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170257870A1 (en) * | 2016-03-04 | 2017-09-07 | Huawei Technologies Co., Ltd. | Systems and methods for performing traffic engineering through network slices |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4696027A (en) * | 1986-08-01 | 1987-09-22 | Motorola, Inc. | Handoff apparatus and method with interference reduction for a radio system |
US5821821A (en) * | 1997-02-24 | 1998-10-13 | Ati Technologies Incorporated | ICO based linear gain VCO with non-linear V/I converter |
US6614781B1 (en) * | 1998-11-20 | 2003-09-02 | Level 3 Communications, Inc. | Voice over data telecommunications network architecture |
EP1328890A2 (de) * | 2000-10-20 | 2003-07-23 | Siemens Aktiengesellschaft | System und verfahren zum verwalten von softwareapplikationen, insbesondere mes-applikationen |
US9171271B2 (en) * | 2010-01-15 | 2015-10-27 | New York University | Computer system, client device and method |
US9832684B2 (en) * | 2013-04-08 | 2017-11-28 | Nokia Solutions And Networks Oy | Control of offloading by the network |
WO2018008629A1 (ja) * | 2016-07-08 | 2018-01-11 | 株式会社Nttドコモ | 無線通信システム及び通信方法 |
CN107071799B (zh) * | 2017-02-16 | 2019-12-06 | 北京小米移动软件有限公司 | 网络切片配置方法及装置、无线接入网ran节点和终端 |
CN106982458B (zh) * | 2017-03-09 | 2019-12-17 | 华为技术有限公司 | 一种网络切片的选择方法及装置 |
KR102620149B1 (ko) * | 2017-05-08 | 2024-01-03 | 모토로라 모빌리티 엘엘씨 | 데이터 접속을 재구성하기 위한 방법들 및 장치들 |
US11284374B2 (en) * | 2017-06-15 | 2022-03-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for managing wireless communications network |
US11026106B2 (en) * | 2018-11-09 | 2021-06-01 | Huawei Technologies Co., Ltd. | Method and system of performance assurance with conflict management in provisioning a network slice service |
-
2017
- 2017-09-08 CN CN201710807964.0A patent/CN109474449A/zh active Pending
-
2018
- 2018-08-30 EP EP18854430.8A patent/EP3664373A4/en not_active Withdrawn
- 2018-08-30 WO PCT/CN2018/103344 patent/WO2019047769A1/zh unknown
-
2020
- 2020-03-06 US US16/811,810 patent/US11240745B2/en active Active
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170257870A1 (en) * | 2016-03-04 | 2017-09-07 | Huawei Technologies Co., Ltd. | Systems and methods for performing traffic engineering through network slices |
Non-Patent Citations (2)
Title |
---|
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Study on management and orchestration of network slicing for next generation network (Release 15)", 3GPP STANDARD ; TECHNICAL REPORT ; 3GPP TR 28.801, vol. SA WG5, no. V1.2.0, 31 May 2017 (2017-05-31), pages 1 - 79, XP051298434 * |
See also references of EP3664373A4 |
Also Published As
Publication number | Publication date |
---|---|
US11240745B2 (en) | 2022-02-01 |
EP3664373A4 (en) | 2020-08-19 |
EP3664373A1 (en) | 2020-06-10 |
CN109474449A (zh) | 2019-03-15 |
US20200213937A1 (en) | 2020-07-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019047769A1 (zh) | 一种处理网络切片实例的方法、装置及*** | |
US20190230004A1 (en) | Network slice management method and management unit | |
CN110012437B (zh) | 一种组播报文的发送方法、装置及*** | |
EP3557818A1 (en) | Method, device and system for managing network slice instance | |
WO2018153346A1 (zh) | 一种网络切片的选择方法及装置 | |
US10924966B2 (en) | Management method, management unit, and system | |
WO2019062994A1 (zh) | 网络切片的管理方法、设备及*** | |
KR102424658B1 (ko) | 디폴트 서비스 품질(QoS) 제어 방법 및 장치 | |
WO2017036288A1 (zh) | 一种网元升级方法及设备 | |
US10993127B2 (en) | Network slice instance management method, apparatus, and system | |
US20200177473A1 (en) | Network component management method and network device | |
US11057309B2 (en) | Management method, management unit, and system | |
EP3713282A1 (en) | Management method, device and system for network service | |
US11088924B2 (en) | Network management method, device, and system | |
WO2019029268A1 (zh) | 网络切片的部署方法和装置 | |
WO2019062830A1 (zh) | 实例业务拓扑的生成方法及装置 | |
WO2018090191A1 (zh) | 网络功能的管理方法、管理单元及*** | |
CN107222321B (zh) | 一种配置报文发送方法及装置 | |
WO2018024121A1 (zh) | 一种网络功能nf管理方法及nf管理设备 | |
WO2019057015A1 (zh) | 一种网络切片管理方法及装置 | |
WO2018086412A1 (zh) | 一种时延控制方法、装置及*** | |
CN109391503B (zh) | 一种网络切片管理方法及装置 | |
WO2019062634A1 (zh) | 通信方法及装置 | |
WO2019100924A1 (zh) | 一种网络性能保障方法及装置 | |
CN109526032B (zh) | 修改网络切片实例的方法及装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18854430 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2018854430 Country of ref document: EP Effective date: 20200306 |