CN110086662B - Method for implementing demand definition network and network architecture - Google Patents
Method for implementing demand definition network and network architecture Download PDFInfo
- Publication number
- CN110086662B CN110086662B CN201910324639.8A CN201910324639A CN110086662B CN 110086662 B CN110086662 B CN 110086662B CN 201910324639 A CN201910324639 A CN 201910324639A CN 110086662 B CN110086662 B CN 110086662B
- Authority
- CN
- China
- Prior art keywords
- network
- user
- demand
- layer
- meta
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- 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
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/80—Actions related to the user profile or the type of traffic
- H04L47/805—QOS or priority aware
Abstract
A method for realizing a demand definition network and a network architecture relate to the field of network architectures, and the method comprises the following steps: collecting and classifying user requirements, dividing each type of user requirements into a user requirement set, and adjusting the user requirement set in real time according to the user requirements; judging the satisfiability of each user demand set according to all available network resources, and establishing a meta-slice for each satisfiable user demand set; and establishing mapping between each meta-slice and the required network resources, and configuring and executing the network resources corresponding to the meta-slices. The invention can make the network dynamically adapt according to the dynamically changing, discrete and differentiated user requirements.
Description
Technical Field
The invention relates to the field of network architecture, in particular to a method for realizing a demand definition network and a network architecture.
Background
The basic capabilities of a network include three dimensions of transmission, computation and storage, and the functions of the network are mainly expressed in three aspects of hardware resource sharing, software resource sharing and information exchange among users, however, the ultimate goal of the network is to meet various demands of all users in the network, which is also the power of meaning and development of the network, and therefore, the demands are the factors determining the fundamental nature of the network architecture and properties.
The current network meets the requirements of users and is realized by two stages of network design and network operation and maintenance. Network design provides a basic network construction scheme, and network operation and maintenance configures the network based on the constructed network and user requirements collected by network operators. Neither of these two phases is centered on dynamic, discrete user demand, but rather is targeted to meet predicted overall network traffic needs. Thus, the degree of matching of network architecture design and construction to dynamic, discrete user requirements is difficult to say. On the other hand, the requirement processing of the dynamic change in the network operation and maintenance stage is mainly realized by manpower, and the method has the advantages of low instantaneity, insufficient requirement satisfaction accuracy, poor matching degree with the network real-time state and poor utilization rate of network resources. Meanwhile, the user requirements may also change with time, and if the user relies on manual work to realize the adaptation to the requirement changes, the method is neither real-time nor accurate enough, and the realization cost is high.
The change of the network architecture brought by the software defined network has a great positive influence on the development of the network, but because the software defined network focuses on the upper architecture of the network, the consideration on the implementation and application aspects is not fine enough, and the problem that who defines the network is reasonable and how to implement the definition efficiently is not solved clearly, so that the application on the product faces some obstacles.
Disclosure of Invention
In view of the defects in the prior art, an object of the present invention is to provide a method for implementing a demand definition network and a network architecture, so that the network can be dynamically adapted according to dynamically changing, discrete, and differentiated user demands.
In order to achieve the above object, in one aspect, a method for implementing a requirement definition network is adopted, including the steps of:
collecting and classifying user requirements, dividing each type of user requirements into a user requirement set, and adjusting the user requirement set in real time according to the user requirements;
judging the satisfiability of each user demand set according to all available network resources, and establishing a meta-slice for each satisfiable user demand set;
and establishing mapping between each meta-slice and the required network resources, and configuring and executing the network resources corresponding to the meta-slices.
Preferably, the same or similar user requirements are classified into one category, and the similar user requirements refer to user requirements that have the same content and can share the same network resource.
Preferably, the adjusting the user requirement set in real time according to the user requirement includes: and deleting the user requirements exceeding the effective time period from the user requirement set when the last user requirement in the user requirement set is deleted.
Preferably, a priority is set for the user requirements in each user requirement set, and for the user requirement sets which cannot be met by the network resources, the user requirements are sequentially deleted from the user requirement sets according to the sequence of the priorities from low to high until the network resources meet the user requirement sets; setting a priority for each user demand set, and sequentially judging the satisfiability of each user demand set according to the sequence of the priority from high to low.
Preferably, each meta-slice is the smallest independent logical partition in the network, and is established based on a policy, where the policy is a corresponding operation executed after a user requirement set corresponding to the meta-slice is satisfied.
In another aspect, a network architecture of a demand-defined network is also provided, including:
a requirement layer for receiving user requirements through a user terminal device or a system of a network service provider;
the demand broker layer is used for collecting and classifying user demands and dividing each type of user demands into a user demand set; the system is also used for adjusting the user demand set in real time;
the network intelligent layer is used for judging the satisfiability of each user demand set according to all available network resources and establishing a meta-slice for each user demand set which can be satisfied; the system is also used for managing the life cycle of the meta-slice and establishing the mapping between the meta-slice and the required network resources; the system is also used for configuring network resources corresponding to the meta-slice;
the control layer is used for controlling network resources in a network and configuring the network resources corresponding to the meta-slice;
a network layer for providing network resources for the meta-slice and performing configuration of a control layer;
and the network management system is used for monitoring the states of the demand layer, the demand broker layer, the network intelligent layer, the network layer and the control layer and performing daily management.
Preferably, the demand broker layer comprises an independent server or a cluster of multiple servers, and is further configured to convert the user demand into a form of network smart layer identification.
Preferably, the network smart layer is further configured to report the user demand set that cannot be met to the demand brokerage layer, and the demand brokerage layer is further configured to adjust the user demand set reported by the network smart layer.
Preferably, the requirement brokerage layer sets priorities for the user requirements in each user requirement set, and for the user requirement sets that the network resources cannot meet, the user requirements are sequentially deleted from the user requirement sets according to the sequence of the priorities from low to high until the network intelligent layer judges that the network resources meet the user requirement sets.
Preferably, the network layer comprises a plurality of network devices, and the network resource mapped by each meta-slice is implemented by one or more network devices in the network layer.
Preferably, the control layer comprises one or more controllers, the network intelligent layer comprises a network intelligent system, and the network intelligent system is realized by one or more servers.
Preferably, the network smart layer sets a user requirement template for building the meta-slice, wherein the user requirement template is a two-dimensional structure, and one dimension is time, and the other dimension is user requirement which changes along with time.
Preferably, the controller and the network intelligent system are independent of each other, and the network intelligent system is directly communicated with the network equipment, or the network intelligent system is communicated with the network equipment through the controller.
At least one of the above technical solutions has the following beneficial effects:
1. the user requirements change along with time, and have the characteristics of dynamic change, dispersion and differentiation, so the user requirement set is constantly changed and can be changed according to addition, change or deletion of the user requirements, the network realizes automatic adaptation to the user requirements according to the meta slice established by the user requirement set, and compared with the manual adjustment of the network requirements, the network demand adjustment method has the advantages of good real-time performance, high accuracy in demand realization and low realization cost.
2. The meta-slice is established according to each user requirement set which can be satisfied, the meta-slices of different user requirement sets are isolated from each other, and the security and the privacy of the user requirements in the different requirement sets are enhanced.
3. The meta slice is established on the premise that network resources can be satisfied, user requirements and corresponding network resources can be accurately matched, and the network resources comprise network equipment resources and network logic resources, so that the utilization rate of the network resources is improved.
Drawings
FIG. 1 is a flow chart of a method for implementing a requirement definition network according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a network architecture for a requirement definition network according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating a physical architecture of a requirement definition network according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a requirement broker function according to an embodiment of the invention;
FIG. 5 is a diagram illustrating a network intelligence system generating meta-slices according to an embodiment of the present invention;
FIG. 6 is a diagram illustrating a network demand agent function according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention.
As shown in fig. 1, the present embodiment provides a method for implementing a requirement definition network, including the steps of:
s101, collecting and classifying user requirements, dividing each type of user requirements into a user requirement set, and adjusting the user requirement set in real time according to the user requirements. The user requirements may be collected from the user terminal equipment or from a system of the network service provider, such as a BOSS system. Then, the same or similar user requirements are classified into a category to form a set of user requirements, namely a user requirement set. Wherein, the same user requirement means that the required contents are completely the same; the similar user requirements mean that the required contents are partially the same, but the same network resources can be commonly used; there are substantial differences in user needs from one user need set to another.
For example: a, a user needs a bandwidth of 100M at time T1, and the time delay requirement is 1 s; at time T2, bandwidth 5M is required, with a latency requirement of 20 ms. The user B needs the bandwidth of 100M at the time T1, and the time delay requirement is 1 s; at time T2, bandwidth 5M is required, with a latency requirement of 20 ms. The user C needs 50M of bandwidth at time T1, and the time delay requirement is 1 s; at time T2, bandwidth 10M is required, with a latency requirement of 20 ms. D, the user needs 1000M of bandwidth at time T1, and the time delay requirement is 100 ms; at time T2, bandwidth 1M is required, with a 2ms latency requirement.
Then the user requirements for a and B are the same; the user requirements of A and C are similar; the user requirements for a and D are different. Thus, the user requirements of A, B and C fall into the same user requirement set, and the user requirements of D fall into another user requirement set.
S102, judging the satisfiability of each user requirement set according to all available network resources in the jurisdiction range, establishing a meta slice for each user requirement set which can be satisfied, and generating an operation instruction which is sent to the network equipment according to the network resources required by the meta slice.
The network resources include physical resources and logical resources of the network device, which can be obtained according to the states of all network devices in the jurisdiction, such as VLAN, IP address, four-layer port, etc. For a set of user requirements that can be met, a meta-slice is created based on the policy. And, this meta-slice is also updated in real-time as the user demand set changes. If the network resources are unable to meet a set of user requirements, problems with the unsatisfiable resources are reported to other systems, such as the network service provider's systems.
The above strategy for creating meta-slices refers to: after the network resources can meet a certain user requirement set, corresponding operations can be executed. For example, the terminal name is "IPhoneX Zhang", and the MAC address is AA: BB: CC: DD: EE: FF, having a bandwidth requirement of 100M at 9 am, is an example of a user requirement set, and only if a network resource has a premise of satisfying the example, a corresponding meta-slice can be established, that is, a meta-slice is established based on a policy.
The meta-slice is the smallest unit of a slice, i.e., the smallest and independent logical partition of the network, and a network slice of a user demand set is a meta-slice. The meta-slices may be generated using a unified meta-slice template, represented by a logical data structure that describes the meta-slices. For example, a meta-slice requires port M of device a to reserve 10M bandwidth and port N of device B to reserve 10M bandwidth …, and the logical data structure is: M10M for A, N10M … for B
And S103, establishing mapping between each meta-slice and the required network resource, namely, the meta-slice in the step S102 is only designed and not physically realized, and needs to correspond to the physical resource or the network virtual resource of the network equipment. By establishing the mapping, the meta-slice can be mapped to the required network resources. And then configuring and executing the network resources corresponding to the meta-slice according to the operation instruction and the configuration method of the network equipment.
Based on the above embodiments, this embodiment details how the user requirement set is adjusted in real time according to the user requirement.
And when receiving a new user demand, distributing the newly added user demand into the user demand set, and if the newly added user demand does not belong to any user demand set, establishing a new user demand set for the newly added user demand.
Each user requirement carries an effective time period, the effective time period is regarded as an effective user requirement, and if the user requirement exceeds the effective time period, the user requirements exceeding the effective time period are deleted from the user requirement set; when the last user requirement in the user requirement set is deleted, the user requirement set is deleted.
Each time the user requirement set changes, such as adding or deleting a user requirement, the meta-slice corresponding to the user requirement set is updated accordingly. If the user requirement set is newly established, the corresponding meta-slice is also newly generated. If the user requirement set is deleted, the corresponding meta-slice is also deleted. After the meta-slice is changed, the mapping corresponding to the meta-slice is also changed, so as to ensure the real-time performance of network resource allocation.
Based on the foregoing embodiment, in another embodiment, different priorities may be set for a plurality of user demand sets in step S101, and in step S102, the satisfiability of each user demand set is determined one by one according to the order of priority from high to low, so as to ensure that the user demand set with high priority preferentially allocates network resources.
In addition, a priority is set for the user requirements in each user requirement set, in step S102, if the network resource cannot meet a certain user requirement set, the resource is reported to other systems that the resource cannot be met, and at this time, the user requirements can be deleted from the user requirement set in sequence from low to high according to the priority until the network resource meets the user requirement set. For the deleted user requirement, the network service provider or the network operation and maintenance unit is automatically notified that the network resource is insufficient to meet the user set, and in this case, the user requirement is handled separately, for example, manually.
As shown in fig. 2, the present embodiment provides a network architecture of a demand definition network, which includes a demand layer, a demand broker layer, a network agent layer, a network layer, a control layer, and a Network Management System (NMS) for controlling each layer.
The demand layer is used for receiving discrete, dynamically-changed and differentiated user demands, and is a source of the user demands. The various graphs of the requirements layer in FIG. 2, each representing a user requirement. Typically, the requirements layer receives user requirements through a user terminal device or a network service provider's system.
The requirement broker layer is used for collecting and classifying user requirements, dividing each type of user requirements into a user requirement set, adjusting the user requirement set in real time according to the user requirements, and converting the user requirements into a form recognized by the network intelligent layer. The same graphs in the requirement broker layer in fig. 2 represent the same or similar user requirements, and the same graphs are divided into a group, which represents that the same or similar user requirements form a user requirement set. The requirement brokering layer comprises a requirement brokering component, and the requirement brokering component can be an independent server or a cluster consisting of a plurality of servers.
The network intelligent layer is used for analyzing according to the conditions of all available network resources, judging the satisfiability of each user demand set, establishing a meta-slice for each satisfiable user demand set and managing the life cycle of the meta-slice. The network intelligence layer is also used to establish a mapping of meta-slices to the required network resources, i.e. mapping the user demand set to the final network resource configuration based on the current conditions of the network. For example: the user demand set 1 needs 100M bandwidth to transmit data from the network node A to the network node B, and the end-to-end time delay is 1 ms; the network smart layer needs to find a route from the network node a to the network node B, the bandwidth of the route is not less than 100M, the total delay of the route is not more than 1ms, and then the 100M bandwidth of the route is corresponding to the user demand set 1.
And the control layer is used for controlling network resources in the network and configuring the network resources corresponding to the meta-slice.
A network layer for providing network resources for the meta-slice, the network resources including physical resources and logical resources of a network device; and also for performing configuration of the control layer. The network layer comprises resource agents and a multi-layer network (such as L2, L3 and L4), the resource agents are components for realizing resource scheduling and configuration in each layer of the multi-layer network, for example, a two-layer (L2) resource agent is a two-layer logic resource corresponding to a VLAN, a three-layer (L3) resource agent is a three-layer logic resource corresponding to an IP route, and a four-layer (L4) resource agent is a four-layer logic resource corresponding to a four-layer port.
The network management system is a management entity of the whole network and is used for monitoring the state of the whole network comprising a demand layer, a demand broker layer, a network intelligent layer, a network layer and a control layer and implementing daily management on the network.
In addition to the above functions, the network intelligent layer is further configured to report the user demand sets that cannot be met to the demand brokerage layer, the demand brokerage layer sets priorities for the user demands in each user demand set, and for the user demand sets that cannot be met by the network resources, the user demands are sequentially deleted from the user demand sets according to a sequence of priorities from low to high until the network intelligent layer judges that the network resources meet the user demand sets.
In another embodiment, the network smart layer may configure the network resource corresponding to the meta-slice by itself without passing through the control layer, and issue the operation instruction corresponding to the configuration to the network layer, in which case, the control layer is not used to configure the function of the network resource corresponding to the meta-slice.
As shown in fig. 3, the present embodiment provides the physical architecture of the previous embodiment, wherein the requirement layer includes a plurality of user terminals, and the requirement brokering layer includes a stand-alone server.
The network layer comprises a plurality of network devices such as routers, switches and the like; the network resources mapped per meta-slice are implemented by one or more network devices in the network layer. The control layer comprises a controller, and the network intelligent layer comprises a network intelligent system and is realized by one or more servers.
In this embodiment, the network intelligent system is implemented by one server, and since the input interface of the server has its own rule, the user requirement brokering component needs to convert the user requirement set into the rule of the network intelligent system. For example, the user requirement brokering component collects natural language descriptions and the network intelligence system requires machine language descriptions, and the user requirement brokering component converts the set of user requirements described in natural language into machine language descriptions.
The relationship among the network intelligent system, the controller and the network equipment has three conditions:
1. the controller and the network intelligence system are logically independent of each other and are co-located in a physical platform, such as a server or a server group, in which case the network intelligence system communicates with the network device via an interface between the logical platform and the network device.
2. The controller and the network intelligent system are mutually independent, and the network intelligent system is directly communicated with the network equipment.
3. The controller and the network intelligent system are mutually independent, and the network intelligent system is communicated with the network equipment through the controller. In this case, the operation of the network intelligent system is first sent to the controller, and then sent to the network device by the controller.
The network layer comprises a demand agent and a resource agent which are all components embedded into the network equipment, the basic function of the network demand agent is to execute an operation instruction issued by the network intelligent system, the operation instruction is generated by the network intelligent system according to network resources required by the meta slice and needs to be executed by the network equipment, and the operation instruction can be issued directly by the network intelligent system or issued by the network intelligent system through a controller.
The demand agent judges that the network resource corresponding to the operation instruction is a physical resource and/or a logic resource according to the operation instruction:
if the physical resource is the physical resource, the demand agent completes the conversion from the operation instruction to the network resource configuration, and the network equipment executes the conversion.
If the operation instruction is a logic resource, the demand agent converts the network resource configuration of the operation instruction through the resource agent, and the operation instruction converted by the resource agent is executed by the network equipment.
If the resource is the physical resource and the logical resource, the network device executes the resource after the conversion is respectively completed according to the mode.
The size of the network demand agent depends on the application scenario and the network resource condition of the network device, and if the network resource is in short supply or the network device in the application scenario cannot be substantially changed, the network demand agent can be designed to be simple and only realize the conversion from the operation instruction to the network configuration. If the network resources can support the network demand broker to implement more complex functions and the network devices in the application scenario can be substantially upgraded, the mapping function and even other functions in the network intelligent system can be sunk to the network devices for implementation. As shown in the lower part of fig. 6, the converted network configuration can be directly executed by the network device.
The network intelligent layer sets a user demand template for establishing the meta-slice, and the user demand template can be arbitrarily expanded according to the application scene. The system is a two-dimensional structure, one dimension is time, and the user requirements of the same user can be different essentially at different times; another dimension is the user demand that changes over time, which may be bandwidth, latency, packet loss rate, jitter, path, environment, etc.
TABLE 1
Based on the above embodiments, the present embodiment describes the requirements brokering component functionality through FIG. 4, which is responsible for the collection, transformation, and categorization of discrete, dynamic user requirements. In FIG. 4, the top part is the various user requirements, the middle is the requirement broker component, and the bottom part is the user requirements that have been transformed and categorized, wherein the transformation is to transform the user requirements obtained from the requirements layer into requirements that can be understood by the network intelligence system.
As shown in fig. 5, a schematic diagram of a network intelligence system generating meta-slices, whose basic functions are to correspond a user requirement set with policy-based meta-slices, complete meta-slice lifecycle management, and map the meta-slices into operations that a network device can perform. The life cycle management of the meta-slice is adjusted in real time according to the user demand set, when the last user demand in the user demand set is deleted, and if the user demand set is deleted, the corresponding meta-slice is also deleted. The upper part of FIG. 5 is the user demand sets output by the demand broker layer, and the user demands in each user demand set are the same or similar, but there is a substantial difference in user demands between different user demand sets. In the middle of fig. 5 is the network intelligence system, and in the lower part is the meta-slice that needs to be established to implement the user requirement set.
As shown in fig. 6, the upper part of the system is various operations issued by the network intelligent system, and the execution logic of these instructions is equivalent to the physical instantiation of a meta-slice, in other words, after the network operation corresponding to each meta-slice is successfully implemented, the meta-slice is implemented. The middle part of fig. 6 is a demand agent, and the lower part of fig. 6 is a converted network configuration, which can be directly executed by a network device.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may 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, and the like) having computer-usable program code embodied therein.
The present invention is not limited to the above-described embodiments, and it will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the principle of the present invention, and such modifications and improvements are also considered to be within the scope of the present invention. Those not described in detail in this specification are within the skill of the art.
Claims (12)
1. A method for implementing a demand definition network, comprising the steps of:
receiving dynamically changing, discrete and differentiated user requirements through user terminal equipment;
collecting and classifying user requirements, dividing each type of user requirements into a user requirement set, and adjusting the user requirement set in real time according to the user requirements;
judging the satisfiability of each user demand set according to all available network resources, and establishing a meta-slice for each satisfiable user demand set;
establishing mapping between each meta-slice and required network resources, and configuring and executing the network resources corresponding to the meta-slices;
the network resources comprise physical resources and logical resources of the network equipment;
each meta-slice is the smallest independent logical partition in the network and is established based on a strategy, wherein the strategy is a corresponding operation executed after a user requirement set corresponding to the meta-slice is met;
the method for implementing the requirement definition network further comprises managing the life cycle of the meta-slice.
2. The method of claim 1, wherein: the same or similar user requirements are classified into one class, and the similar user requirements refer to the user requirements that part of contents are the same and can share the same network resources.
3. The method of claim 1, wherein adjusting the set of user requirements in real-time according to the user requirements comprises:
and deleting the user requirements exceeding the effective time period from the user requirement set when the last user requirement in the user requirement set is deleted.
4. The method of claim 1, wherein:
setting priorities for user requirements in each user requirement set, and deleting the user requirements from the user requirement sets in sequence from low to high according to the priorities for the user requirement sets which cannot be met by the network resources until the network resources meet the user requirement sets;
setting a priority for each user demand set, and sequentially judging the satisfiability of each user demand set according to the sequence of the priority from high to low.
5. A network architecture for a demand-defined network, comprising:
a requirement layer for receiving dynamically changing, discrete, differentiated user requirements through a user terminal device;
the demand broker layer is used for collecting and classifying user demands and dividing each type of user demands into a user demand set; the system is also used for adjusting the user demand set in real time;
the network intelligent layer is used for judging the satisfiability of each user demand set according to all available network resources and establishing a meta-slice for each user demand set which can be satisfied; the system is also used for managing the life cycle of the meta-slice and establishing the mapping between the meta-slice and the required network resources; the system is also used for configuring network resources corresponding to the meta-slice;
the control layer is used for controlling network resources in a network and configuring the network resources corresponding to the meta-slice;
a network layer for providing network resources for the meta-slice and performing configuration of a control layer;
the network management system is used for monitoring the states of the demand layer, the demand broker layer, the network intelligent layer, the network layer and the control layer and performing daily management;
the network resources comprise physical resources and logical resources of the network equipment;
each meta-slice is the largest independent logical partition in the network, and is established based on a policy, wherein the policy is a corresponding operation executed after a user requirement set corresponding to the meta-slice is met.
6. The network architecture of the demand-defined network of claim 5, wherein: the demand broker layer comprises an independent server or a plurality of server clusters, and is also used for converting the user demands into a form identified by the network intelligent layer.
7. The network architecture of the demand-defined network of claim 5, wherein: the network intelligent layer is also used for reporting the user demand set which cannot be met to the demand brokerage layer, and the demand brokerage layer is also used for adjusting the user demand set reported by the network intelligent layer.
8. The network architecture of the demand-defined network of claim 7, wherein: the requirement brokerage layer sets priorities for the user requirements in each user requirement set, and deletes the user requirements from the user requirement set in sequence from low to high according to the priorities for the user requirement sets which cannot be met by the network resources until the network intelligent layer judges that the network resources meet the user requirement set.
9. The network architecture of the demand-defined network of claim 5, wherein: the network layer includes a plurality of network devices, and the network resources mapped by each meta-slice are implemented by one or more network devices in the network layer.
10. The network architecture of the demand-defined network of claim 5, wherein: the control layer comprises one or more controllers, the network intelligent layer comprises a network intelligent system, and the network intelligent system is realized by one or more servers.
11. The network architecture of the demand-defined network of claim 5, wherein: the network intelligent layer is provided with a user demand template for establishing the meta-slice, the user demand template is of a two-dimensional structure, one dimension is time, and the other dimension is user demand changing along with time.
12. The network architecture of the demand-defined network of claim 10, wherein: the controller and the network intelligent system are independent from each other, and the network intelligent system is directly communicated with the network equipment or is communicated with the network equipment through the controller.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910324639.8A CN110086662B (en) | 2019-04-22 | 2019-04-22 | Method for implementing demand definition network and network architecture |
| PCT/CN2019/096636 WO2020215504A1 (en) | 2019-04-22 | 2019-07-19 | Method for implementing requirement defined network and network architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910324639.8A CN110086662B (en) | 2019-04-22 | 2019-04-22 | Method for implementing demand definition network and network architecture |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110086662A CN110086662A (en) | 2019-08-02 |
| CN110086662B true CN110086662B (en) | 2020-09-01 |
Family
ID=67415933
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910324639.8A Active CN110086662B (en) | 2019-04-22 | 2019-04-22 | Method for implementing demand definition network and network architecture |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN110086662B (en) |
| WO (1) | WO2020215504A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115632925B (en) * | 2022-12-26 | 2023-03-14 | 北京交通大学 | Time-certainty fusion network architecture and data communication method |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101102483A (en) * | 2007-08-24 | 2008-01-09 | 北京市朝阳区信息网络中心 | User classification management system of image information management system |
| CN105989450A (en) * | 2015-03-23 | 2016-10-05 | 埃森哲环球服务有限公司 | Automated, accelerated prototype generation system |
| CN106549806A (en) * | 2016-10-26 | 2017-03-29 | 清华大学 | A kind of network section manager and its management method |
| CN109219020A (en) * | 2018-09-14 | 2019-01-15 | 云迅智能科技南京有限公司 | A kind of network dicing method and system |
| CN109218047A (en) * | 2017-06-30 | 2019-01-15 | 中国移动通信有限公司研究院 | Network sliced sheet processing method and device, communication system and storage medium |
| CN109218046A (en) * | 2017-06-30 | 2019-01-15 | 中国移动通信有限公司研究院 | The management method and system and storage medium of network slice |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106657194B (en) * | 2015-11-02 | 2020-05-08 | 中兴通讯股份有限公司 | Method, device and system for opening network slicing capability |
| CN107566145B (en) * | 2016-06-30 | 2020-11-10 | 华为技术有限公司 | Method and apparatus for managing network slices |
| CN108933686B (en) * | 2017-05-25 | 2022-12-20 | 中兴通讯股份有限公司 | Network slicing method, computer equipment and storage medium |
| CN109600246B (en) * | 2017-09-30 | 2021-09-21 | 华为技术有限公司 | Network slice management method and device |
-
2019
- 2019-04-22 CN CN201910324639.8A patent/CN110086662B/en active Active
- 2019-07-19 WO PCT/CN2019/096636 patent/WO2020215504A1/en active Application Filing
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101102483A (en) * | 2007-08-24 | 2008-01-09 | 北京市朝阳区信息网络中心 | User classification management system of image information management system |
| CN105989450A (en) * | 2015-03-23 | 2016-10-05 | 埃森哲环球服务有限公司 | Automated, accelerated prototype generation system |
| CN106549806A (en) * | 2016-10-26 | 2017-03-29 | 清华大学 | A kind of network section manager and its management method |
| CN109218047A (en) * | 2017-06-30 | 2019-01-15 | 中国移动通信有限公司研究院 | Network sliced sheet processing method and device, communication system and storage medium |
| CN109218046A (en) * | 2017-06-30 | 2019-01-15 | 中国移动通信有限公司研究院 | The management method and system and storage medium of network slice |
| CN109219020A (en) * | 2018-09-14 | 2019-01-15 | 云迅智能科技南京有限公司 | A kind of network dicing method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110086662A (en) | 2019-08-02 |
| WO2020215504A1 (en) | 2020-10-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2020258920A1 (en) | Network slice resource management method and apparatus | |
| EP3526933B1 (en) | Method and system for monitoring performance of slices | |
| CN108259367B (en) | Service-aware flow strategy customization method based on software defined network | |
| EP3072260B1 (en) | Methods, systems, and computer readable media for a network function virtualization information concentrator | |
| US10135753B2 (en) | System to share network bandwidth among competing applications | |
| CN102739507B (en) | Router for sensing bearing state and service flow bandwidth distribution method thereof | |
| CN107659419A (en) | Network dicing method and system | |
| CN106533806B (en) | Method for providing cross-layer QoS based on application awareness in multi-tenant SDN network | |
| US20120195324A1 (en) | Sharing bandwidth among multiple users of network applications | |
| Keat et al. | Scheduling framework for bandwidth-aware job grouping-based scheduling in grid computing | |
| Din et al. | Sdiot: Software defined internet of thing to analyze big data in smart cities | |
| CN110086662B (en) | Method for implementing demand definition network and network architecture | |
| Basu et al. | Drive: Dynamic resource introspection and vnf embedding for 5g using machine learning | |
| Hassan et al. | PlanIoT: a framework for adaptive data flow management in IoT-enhanced spaces | |
| CN117395251A (en) | Resource scheduling method, device and computer readable storage medium | |
| CN110971532B (en) | Network resource management method, device and equipment | |
| Li et al. | Optimal service selection and placement based on popularity and server load in multi-access edge computing | |
| Zeydan et al. | A multi-criteria decision making approach for scaling and placement of virtual network functions | |
| Siapoush et al. | Software-defined networking enabled big data tasks scheduling: A tabu search approach | |
| US10986036B1 (en) | Method and apparatus for orchestrating resources in multi-access edge computing (MEC) network | |
| Pang et al. | Research on dynamic load balancing of data center network based on SDN architecture | |
| Tolosana-Calasanz et al. | Revenue-based resource management on shared clouds for heterogenous bursty data streams | |
| CN112579293A (en) | Comprehensive verification method of distributed computing system | |
| CN105847172B (en) | Job flow control method and device | |
| CN117097681B (en) | Scheduling method and device of network resources, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |