WO2022047890A1

WO2022047890A1 - Blockchain-based sd-wan service system, and implementation method for same

Info

Publication number: WO2022047890A1
Application number: PCT/CN2020/120651
Authority: WO
Inventors: 黄韬; 张晨; 汪硕; 庄丽婉; 金韬; 霍如
Original assignee: 网络通信与安全紫金山实验室
Priority date: 2020-09-04
Filing date: 2020-11-06
Publication date: 2022-03-10
Also published as: CN112235239B; CN112235239A

Abstract

Disclosed is a blockchain-based SD-WAN service system, and an implementation method therefor. The system includes three roles, i.e. a user, an operator and a third-party platform, wherein each of the user and the operator comprises an administrator and a device; the third-party platform comprises an SD-WAN controller, a platform serving end and an authentication platform; and a blockchain platform is maintained by the user, the operator and the third-party platform together. A system service process can be divided into five main parts, i.e. registration, subscription, scheduling, collection and settlement, the customized network service requirements of a user in a wide area network are met, a preferable choice among a plurality of operators can be automatically made for the user, and automatic settlement between the operator and the user can be realized by using the blockchain technology.

Description

Blockchain-based SD-WAN business system and its implementation method

technical field

The invention relates to a blockchain-based SD-WAN business system and an implementation method thereof, belonging to the technical field of blockchain.

Background technique

Software-defined wide area network (SD-WAN) is a typical application of software-defined network (SDN) in WAN private network business scenarios. Combined with the automatic configuration and scheduling capabilities of network controllers, enterprise users can use the Internet to build tunnels to flexibly access. Compared with the traditional physical private line access method, the operator's WAN private network can greatly improve the efficiency of WAN private network service provisioning, and at the same time reduce the WAN private network service provisioning cost. However, in this scenario, the current SD-WAN network controller is usually provided by the operator, and the operator will uniquely schedule the traffic of enterprise users to its own WAN private network for its own commercial interests. Therefore, enterprise users are using SD-WAN faces the problem of single operator lock-in, which restricts the development of SD-WAN to a certain extent.

SUMMARY OF THE INVENTION

The purpose of the present invention is to overcome the defects of the prior art, and to provide an improved mode of traditional operator user settlement, so that users can customize network services and automatic settlement can be performed between operators and users.

The present invention is a blockchain-based SD-WAN business system, and the business system includes

a blockchain node module, where the blockchain node module includes device nodes, and the device nodes are divided into third-party platform-side nodes, user-side nodes, and operator-side nodes;

A smart contract module, the smart contract module is used to realize the functions of signing, accounting, settlement and punishment among third-party platforms, users and operators;

a blockchain user module, the blockchain user module is used to provide users with a client that interacts with the blockchain;

SD-WAN service module, the SD-WAN service module is responsible for intelligent network scheduling according to contract data and network quality;

a platform server module, the platform server module is used to perform registration and signing functions for users and operators;

Authentication platform service module, the authentication platform service module is responsible for providing operation and maintenance functions for the blockchain, responsible for member identity authentication, license access management, and issuing signature certificates, communication certificates, and service certificates to accounts or nodes that are successfully authenticated, and is responsible for Management of certificates.

Further, the SD-WAN service module is divided into four units: scheduling, collection, network probe and scheduling agent, wherein,

The scheduling unit is responsible for network traffic scheduling, and the collection unit is responsible for real-time traffic collection at both ends;

The network probe and the scheduling agent unit are both deployed on user and operator equipment.

Further, the smart contract modules are divided into:

Identity verification, authorization and authentication module: responsible for identifying the user's read and write permissions;

Signing module: responsible for all signing processes;

Accounting module: responsible for obtaining traffic usage records from the acquisition system during the scheduling process;

Settlement module: responsible for clearing the billing process between users and operators;

Punishment module: responsible for recording the violations of operators, third parties and users, and use it as a certificate for later punishment.

The present application also provides a blockchain-based SD-WAN service implementation method, which includes the following steps:

Step 1, the operator and the user respectively register and sign in the service module of the blockchain authentication platform;

Step 2, the SD-WAN controller performs intelligent network scheduling according to the contract data and network quality;

Step 3, the smart contract module implements accounting and settlement for the traffic generated by the user according to the method specified in the contract.

Further, the signing by the user in the service module of the blockchain authentication platform includes the following two modes:

Direct signing mode: The contracting parties of the direct signing mode are the operator and the user. In this mode, the third-party platform provides different operators for the user to choose, and does not participate in the contract signing process;

Proxy signing mode: The contracting parties of the proxy signing mode are the third-party platform and the user. When the third-party platform signs the contract with the operator, the operator signs a contract that agrees to be freely scheduled, and can be freely scheduled during the network traffic scheduling process.

Further, the step 2 is specifically:

Step 2.1, the SD-WAN controller first identifies the form that the user signs in the blockchain authentication platform service module. If it is a direct sign mode, the blockchain scheduling unit sends a scheduling instruction to the user and the operator scheduling agency unit, and the user Establish a connection with the operator to start communication;

If it is an agent signing mode, the blockchain scheduling unit searches for an operator that matches the traffic parameters in the contract, and then sends a scheduling instruction to the user and the operator's scheduling agent, and the user and the operator establish a connection to start communication;

Step 2.2, the user and the operator equipment network probe pushes the traffic record to the collection unit of the SD-WAN controller;

Step 2.3, when the user equipment probe detects that the network quality is degraded, it feeds back the network quality to the collection unit, and in the proxy sign mode, the user requests the scheduling unit for traffic scheduling;

Step 2.4, the scheduling unit sends a scheduling instruction to the user scheduling agent unit according to the user's subscription status.

Further, the step 3 is specifically:

In the direct-signature mode, the settlement is in accordance with the method stipulated in the contract. The user directly settles with the operator, and the operator clears the payment record on the chain after settlement.

The step 3 is specifically: in the proxy sign mode,

Step 3.1, at the time agreed in the contract, the platform server submits a settlement application to the blockchain;

Step 3.2, the blockchain platform generates the user's bill according to the contract, the bill enters the pending settlement state, and then sends the bill back to the platform server;

Step 3.3, the platform server sends the bill to the corresponding user;

Step 3.4, the user conducts offline settlement with the third-party platform;

Step 35: After the offline settlement is completed, the platform server submits the bill-settled transaction to the blockchain platform;

Step 3.6, the blockchain platform updates the bill status and informs the user that the bill has been settled.

As a preferred embodiment of the present application, the method further includes:

The operator's contract change process is as follows:

In the direct-signature mode, the operator's contract is changed according to the operator's regulations. If the user is not satisfied with the change result, he chooses to terminate the contract with the operator and re-select a new operator;

In the proxy signing mode, the operator first submits a change application to the blockchain platform, and then the blockchain records the change application and sends a message of the operator's contract change to the SD-WAN scheduling module, and then the SD-WAN scheduling module will The operator's equipment is disconnected. After the blockchain changes the contract status and sends the contract template to the operator administrator, the operator administrator affixes the electronic signature and submits the contract to the blockchain; The stamped electronic contract is stamped with an electronic signature and uploaded to the blockchain. After the blockchain changes the contract status, the SD-WAN scheduling module will be notified of the operator's new service parameters and tariffs.

The user change contract process is as follows:

In the direct signing mode, the user requests to change the contract to negotiate directly with the operator, and upload the new contract to the blockchain after completion;

In the proxy signing mode, the enterprise user submits a contract change application to the blockchain platform, and the blockchain records the change application and sends a message to the SD-WAN scheduling module to notify the user that the contract will be changed, and the SD-WAN scheduling module will change the contract. The user's device is disconnected; then, the blockchain changes the contract status and sends the contract template to the corresponding user, and the user affixes the electronic signature and submits the contract to the blockchain; after the platform server finds the electronic contract to be sealed The electronic signature is affixed and uploaded to the blockchain; finally, the blockchain notifies the SD-WAN scheduling module, the user, and the platform that the contract change is completed after receiving the contract signed by both parties, and the SD-WAN controller starts scheduling.

Compared with the prior art, the blockchain-based SD-WAN service system and its implementation method of the present invention have the following beneficial effects:

(1) Introduce a third party as a neutral SD-WAN platform, and realize the dynamic scheduling of enterprise user traffic between multiple operators' wide area private networks through the third-party network controller, giving full play to the last mile of SD-WAN through the Internet The flexibility of tunnel access removes the problem of single operator lock-in, and at the same time enables enterprise users to automatically optimize among multiple operators.

(2) Using blockchain and smart contract technology, the business processes of SD-WAN platform such as signing, scheduling, collection, settlement, etc. are designed, which can realize the non-tampering of data in the process of SD-WAN traffic optimization and scheduling, which can effectively solve the problem of enterprises. The mutual distrust between users when faced with multiple operators provides an important guarantee mechanism for the operation of the SD-WAN platform business system.

Description of drawings

In order to illustrate the technical solutions in the present invention more clearly, the following briefly introduces the drawings required in the present invention. Obviously, the drawings in the following description are only some embodiments of the present invention, which are common in the art. As far as technical personnel are concerned, other drawings can be obtained according to these drawings without any creative effort.

Fig. 1 is the overall architecture diagram of the SD-WAN business system based on the blockchain of the present invention;

Fig. 2 is the flow chart of operator signing in the present invention;

Fig. 3 is the flow chart of the direct sign mode of user contract in the present invention;

Fig. 4 is the flow chart of the user's signing agent signing mode among the present invention;

Fig. 5 is the flow chart under the conventional dispatch direct sign mode of the present invention;

Fig. 6 is the flow chart under the conventional dispatching agent sign mode of the present invention;

Fig. 7 is the data acquisition flow chart;

Fig. 8 is the flow chart in the data feedback direct sign mode;

Fig. 9 is the flow chart under the data feedback proxy sign mode;

Figure 10 is a flow chart of the settlement process under the agent signing mode;

Fig. 11 is the flow chart of the operator's change contract under the agent signing mode;

Fig. 12 is the flow chart of the user change contract process flow under the proxy signing mode;

13 is a schematic diagram of a network scene structure in an embodiment;

Figure 14 is a schematic diagram of the structure of the Web terminal and the authentication platform in the third-party platform deployment;

15 is a schematic diagram of the structure of the dispatching proxy client and the acquisition proxy client in the third-party platform deployment;

Figure 16 is a schematic diagram of the fabric node structure in third-party platform deployment;

17 is a schematic diagram of the structure of an operator organization authentication server in an operator deployment;

Figure 18 is a schematic diagram of the data structure of the device client and the operator's SD-WAN probe binding in the operator's deployment;

FIG. 19 is a schematic diagram of the structure of the operator fabric node in the operator deployment.

detailed description

In order to make the objectives, technical solutions and advantages of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

The present invention actually proposes a blockchain-based SD-WAN business system and an implementation method thereof, which can realize the customized network service requirements of users under the WAN, and can automatically optimize users among multiple operators, and at the same time utilize blockchain technology. Realize automatic settlement between operators and users.

Example 1 Overall architecture of the system

The system includes three roles: users, operators, and third-party platforms. Users and operators include administrators and devices. The third-party platform includes SD-WAN controllers, platform servers, and authentication platforms. The blockchain platform is jointly operated by the three Maintenance, the system function modules are mainly divided into blockchain part and non-blockchain part:

1. Blockchain part

Blockchain node module: This module includes all nodes in the blockchain network, which are provided by third-party platforms, users and operators.

Smart Contract Module: This module is divided by function, as follows:

Identity verification, authorization and authentication module: responsible for identifying the user's read and write permissions.

Signing module: responsible for all signing processes.

Accounting module: responsible for obtaining traffic usage records from the acquisition system during the scheduling process.

Settlement module: responsible for settlement of billing process between users and operators.

2. Non-blockchain part

Blockchain user module: It is used to provide users with a client that interacts with the blockchain. User modules are divided into ordinary users and device users. Common users are user administrator clients, operator administrator clients, and platform clients. A device user refers to a device that registers as a blockchain user and interacts with the blockchain through the provided SDK. For example, user equipment clients, carrier equipment clients, SD-WAN equipment clients, etc.

SD-WAN service module: Responsible for intelligent network scheduling according to contract data and network quality. The components can be divided into four parts: scheduling, collection, network probe and scheduling agent. The scheduling module is responsible for network scheduling; the collection module is responsible for real-time traffic collection at both ends. In addition, network probes and scheduling agents are deployed on user and operator equipment.

Authentication platform service module: a centralized platform, responsible for providing operation and maintenance functions for the blockchain, responsible for membership authentication, license access management, and issuing signature certificates, communication certificates, service certificates to accounts or nodes that are successfully authenticated, and responsible for the certification of certificates. manage.

Platform server module: It mainly has the functions of business display, registration, signing, etc., and the general C/S structure.

Example 2 System business process

The system business process can be divided into five parts: registration, contract signing, scheduling, collection, and settlement:

1. Operator and user registration

1) The operator or user administrator submits data application and registration through the platform business server.

2) The platform reviews the qualification information of the operator or user.

3) Submit the certificate application to the certification platform after the platform has passed the review.

4) The certification platform issues certificates.

Since then, users or operators can interact with the platform and blockchain.

2. Operator signing process

The operator contract flow chart is as follows:

1) The operator administrator initiates a subscription request to the platform service server (the service quality, tariff and other information that the operator can provide is included in the subscription request).

2) After verifying the signing request, the platform business server requests a contract template from the blockchain platform and generates a contract (in this case, the contract includes Party A and Party B, service parameters, etc.) and then sends it to the operator administrator.

3) The operator administrator affixes an electronic signature after confirming that it is correct, and then sends it to the blockchain platform.

4) Store and initialize the contract state on-chain.

5) After the initialization is completed, send it to the platform business server and wait for a third-party electronic signature.

6) The third party affixes the electronic signature and submits it to the blockchain.

7) The contract status is updated on the chain and the contract takes effect.

8) Broadcast to third parties and operators after the contract takes effect.

3. User signing process

User signing can be divided into two modes: direct signing mode and proxy signing mode.

Direct signing mode: The contracting parties of the direct signing mode are operators and enterprise users. In this mode, the third-party platform only provides a series of operators for enterprise users to choose, and does not participate in the contract signing process.

1) The enterprise user administrator initiates a direct subscription request (the service quality required by the enterprise user, the expected tariff and other information are included in the subscription request), or the operator is screened by the specified operator name.

2) The platform server verifies the contract request and returns a list of qualified operators.

3) The enterprise user administrator selects an operator and submits it to the platform server.

4) The platform server requests a contract template from the blockchain platform and generates a contract (in this case, the contract contains Party A and Party B, demand parameters, etc.) and then sends it to the enterprise user administrator.

5) The enterprise user administrator affixes an electronic signature after confirming that it is correct, and then sends it to the blockchain platform.

6) Store and initialize the contract state on-chain.

7) After the initialization is completed, send it to the operator's administrator, and wait for the operator's electronic signature to be affixed.

8) The operator administrator affixes the electronic signature and submits it to the blockchain.

9) The contract status is updated on the chain, and the contract takes effect.

10) Broadcast to third parties, enterprise users and operators after the contract takes effect.

11) SD-WAN scheduling system starts.

Proxy signing mode: The contracting parties of the proxy signing mode are third-party platforms and enterprise users. When the platform side signs a contract with an operator, the operator needs to sign a contract that agrees to be freely dispatched. All operators who have signed the contract are in the proxy mode contract. within the scheduling options.

1) The enterprise user administrator initiates a proxy subscription request (information such as the quality of service required by the enterprise user and the expected tariff are included in the subscription request).

2) After verifying the signing request, the platform business server requests a contract template from the blockchain platform and generates a contract (in this case, the contract includes Party A and Party B, demand parameters, etc.), and then sends it to the enterprise user administrator.

3) The enterprise user administrator affixes an electronic signature after confirming that it is correct, and then sends it to the blockchain platform.

4) Store and initialize the contract state on-chain.

5) After the initialization is completed, send it to the third-party platform server, and wait for the third-party electronic signature to be affixed.

7) The contract status is updated on the chain and the contract takes effect.

8) Broadcast to third parties and enterprise users after the contract takes effect.

9) SD-WAN scheduling system starts.

4. Initial scheduling process

Direct sign mode:

1) After the direct signing contract is signed, the blockchain platform informs the SD-WAN scheduling module that the contract takes effect.

2) The scheduling module sends scheduling instructions to the user and the operator's scheduling agent.

3) Communication starts after the user establishes a connection with the operator.

Proxy sign mode:

1) After the agency contract is signed, the blockchain platform informs the SD-WAN scheduling module that the contract takes effect, with user demand parameters attached.

2) The scheduling module searches for a matching operator, and then sends a scheduling instruction to the user and the operator's scheduling agent.

5. Collection process

Direct sign mode/agent sign mode:

1) User and operator equipment network probes push traffic records to the collection module.

2) The acquisition module verifies and organizes the flow records, and uploads the flow records to the chain.

3) After the acquisition module uploads the data to the chain, the operator's equipment client reads the data on the chain, and checks whether there is any error with the local.

4) After the operator's equipment finds obvious errors, it submits the error record and enters the adjustment and arbitration process.

5) After the acquisition system uploads the data to the chain, the enterprise user equipment client reads the data on the chain, and checks whether there is any error with the local.

6) After the enterprise user equipment finds obvious errors, it submits the error records and enters the adjustment and arbitration process.

The adjustment arbitration process involved in step 4) and step 6) is as follows:

1. After the operator or user equipment finds the error, submit the error record to the blockchain platform through the device client.

2. After the third-party platform obtains the error record, check the traffic record in the SD-WAN acquisition module. If there is no error, the adjustment request will be rejected. If there is any error, the new traffic record will be submitted to the blockchain platform and notified to the operator or user equipment.

3. After receiving the notification, the operator or user equipment will check the data on the chain with the local data again. If there is still an error, repeat the above process until the data is correct.

6. Collection feedback process

Direct sign mode:

1) When enterprise users find that the network quality has deteriorated, they will report network quality problems to the blockchain platform.

2) The blockchain platform generates feedback records and feeds them back to the collection module.

3) The acquisition module searches for network quality data records, analyzes and finds the corresponding records, and then uploads the corresponding records to the chain.

4) The blockchain writes the record to the ledger and returns the feedback result to the enterprise user.

Proxy sign mode:

1) When the user equipment probe detects that the network quality is degraded, it feeds back the network quality to the acquisition module and requests scheduling.

2) The scheduling module obtains the quality detection parameters from the acquisition module, and then the acquisition module uploads the network quality information to the chain.

3) The scheduling module sends scheduling instructions to the user scheduling agent.

4) After the scheduling of the user equipment is completed, the scheduling result is pushed to the collection module.

7. Settlement process

Direct sign mode:

In the direct-signing mode settlement, the user settles directly with the operator according to the method stipulated in the contract. After settlement, the operator will clear the pending payment records on the chain.

Proxy sign mode:

1) At a specific time, the platform server submits a settlement application to the blockchain.

2) The blockchain platform generates a bill for a specific enterprise user, and the bill enters the pending settlement state. Then send the bill back to the platform server.

3) The platform server sends the bill to the enterprise user.

4) Offline settlement between corporate users and third-party platforms.

5) After the offline settlement is completed, the platform server submits the bill-settled transaction to the blockchain.

6) The blockchain platform updates the bill status and informs the enterprise user that the bill has been settled.

The settlement process between the operator and the third party is the same as above, and the process is as follows:

2) The blockchain platform generates a bill for a specific operator, the bill enters the pending settlement state, and then sends the bill back to the platform server.

3) The platform server sends the bill to the operator.

4) The operator conducts offline settlement with the third-party platform.

6) The blockchain platform updates the bill status and informs the operator that the bill has been settled.

8. Operator change contract process

Direct sign mode:

Direct signing process operator contract change According to the operator's regulations, if the user is not satisfied with the change result, he can choose to terminate the contract with the operator and re-select a new operator.

Proxy sign mode:

1) The operator submits a change application (including contract data).

2) The third party submits the change request to the blockchain.

3) After the blockchain records the change application, a message is sent to the SD-WAN scheduling module to notify the operator that the contract will be changed.

4) The SD-WAN scheduling module disconnects the operator's equipment.

5) After the disconnection is successful, the SD-WAN controller will upload the disconnection information to the blockchain.

6) The blockchain changes the contract status and sends the contract template to the platform server.

7) The platform server sends the contract to the operator administrator.

8) The operator administrator affixes the electronic signature and submits the contract to the blockchain.

9) After the third-party platform finds the electronic contract to be sealed, it will be electronically signed and uploaded to the blockchain.

10) After the blockchain changes the contract status, it notifies the SD-WAN scheduling module of the operator's new service parameters and tariffs.

9. User change contract process

Direct sign mode:

In the direct signing process, the user requests to change the contract and directly negotiate with the operator, and the new contract can be uploaded to the chain after completion.

Proxy sign mode:

1) Enterprise users submit a contract change application (including demand parameters) to the platform.

2) After the platform verification requirements are reasonable, submit a change application to the blockchain.

3) After the blockchain records the change application, a message is sent to the SD-WAN scheduling module to notify the user that the contract will be changed.

4) The SD-WAN scheduling module disconnects the user's device.

5) After the disconnection is successful, the SD-WAN scheduling module will upload the disconnection information to the blockchain.

6) The blockchain changes the contract state and sends the contract template to the platform server.

7) The platform server sends the contract to the enterprise user.

8) The enterprise user submits the contract to the blockchain after stamping the electronic signature.

9) After the platform server finds the electronic contract to be sealed, it will be electronically signed and uploaded to the blockchain.

10) After receiving the contract signed and completed by both parties, the blockchain notifies the SD-WAN scheduling module, enterprise user, and platform party that the contract change has been completed.

11) The SD-WAN controller starts scheduling.

Take the following implementation scenario as an example:

Blockchain part:

The blockchain platform uses hyperledger fabric, which includes three types of organizations: third-party platforms, operators, and users. Each organization needs to deploy peer nodes, and all organizations belong to the same channel. The Orderer nodes are provided by third-party platforms and operators, and are optional for users. Each module of the smart contract is implemented by chaincode.

Non-blockchain part:

Device client: user devices, carrier devices, and SD-WAN controllers need to deploy fabric clients.

User client: User administrators, operator administrators, and platform administrators interact with the fabric through the fabric client on the platform web side (the platform server uses the web to implement).

The SD-WAN components, authentication platform, and platform web end are maintained and managed by a third party. The fabric supports secondary authentication, the root authentication platform is maintained by a third party, and the organization authentication platform is maintained by each organization.

The specific deployment is as follows:

1. Schematic of third-party platform deployment

1) Web and authentication platform deployment (non-blockchain part)

The web terminal has the following functions:

Web function backend: registration/login page (need to distinguish users and operators), operator registration, all user registrations.

Root authentication platform: Operators gain access, and enterprise users gain access.

fabric client: operator contracts, all users contract, all users authorize third-party agency contracts, operators and users settle settlements, all user traffic queries, all users submit work orders for traffic quality problems (adjustment/punishment), all users/operators Change the contract.

Third-party organization authentication platform: internal members of third-party organizations obtain access, and independent users obtain access (independent users refer to individual users or enterprises who do not set up an organization authentication server and cannot be authenticated by the blockchain).

2) SD-WAN equipment (non-blockchain part)

The SD-WAN device deployed by the third party includes a scheduling and collection module responsible for the intelligent scheduling of the network. In addition, the SD-WAN device client is divided into a scheduling proxy client and a collection proxy client. Figure 15 shows the deployment locations of the scheduling proxy client and the acquisition proxy client.

Scheduling agent client: It is mainly responsible for recording the scheduling records of the scheduling system, sorting them into the format specified by the fabric network, submitting them to the blockchain platform, and recording them on the blockchain as a certificate for later punishment. At the same time, the demand parameters signed by the user are obtained from the blockchain for initial scheduling by the scheduling module.

Acquisition agent client: It is mainly responsible for recording the data of the acquisition system, sorting it into the format specified by the fabric network, and submitting it to the blockchain platform to form billing data on the chain.

3) Fabric node deployment (blockchain part)

In the initial state, there is no operator platform to provide a complete blockchain structure. The specific structure is shown in Figure 16.

As a platform, you need to provide 3 Orderer nodes at the beginning (the number of Orderer nodes required for each channel of raft consensus is odd), and 2 Peer nodes (avoiding single points) to ensure that the blockchain system can operate normally. In the later stage, the platform side can appropriately reduce the holdings of Orderer nodes and Peer nodes, and at the same time install and instantiate the initial chaincode.

2. Operator deployment instructions

1) Operator organization authentication server deployment (non-blockchain part)

The operator's organizational authentication server shall have the following functions:

Web backend: Provides operators with the management function of their own internal member groups.

Operator organization certification platform: the internal members of the operator obtain access, the operator's own equipment obtains access, and the operator node obtains access.

2) Operator equipment deployment (non-blockchain part)

The operator's device client requires the operator to give it a certificate through its own organizational certification platform for submitting transactions on the blockchain. The device client is bound with the carrier's SD-WAN probe. The schematic diagram is as follows:

Operator equipment client functions: obtain scheduling records and traffic usage and write them into the blockchain, and obtain network quality and write them into the blockchain.

3) Operator fabric node deployment (blockchain part)

An operator is regarded as an organization in the fabric network. Therefore, the operator needs to deploy the following servers: Peer node Orderer node The number of Peer nodes is determined by the operator itself. The operator installs the chaincode through the fabric cli, and the steps are the same as the platform synchronization chaincode.

3. User deployment instructions

1) User organization authentication server deployment (non-blockchain part)

The user's organization authentication server should have the following functions:

Web backend: Provide users with the management function of their own internal member groups.

User organization authentication platform: internal members of users obtain access, users' own devices obtain access, and user nodes obtain access.

2) User equipment deployment (non-blockchain part)

The user equipment client requires the user to give it a certificate through its own organization authentication platform, which is used to submit transactions on the blockchain. The device client is bound to the user's SD-WAN probe. The schematic diagram is as follows:

User equipment client functions: obtain scheduling records and traffic usage and write them into the blockchain, and obtain network quality and write them into the blockchain.

3) User fabric node deployment (blockchain part)

An enterprise user is regarded as an organization in the fabric network. Users can deploy Peer nodes according to the actual situation, or they can choose to provide Orderer nodes (not deployed by default). The user installs the chaincode through the fabric cli, and the steps are the same as the platform synchronization chaincode.

System startup process

1. Initial start of the platform

1) Deploy SD-WAN controller appliance

2) Web and authentication platform deployment

3) Generate organizational relationship and identity certificate

4) The Ordering service starts the initial block

5) Peer node startup

6) Create application channel

7) Install and instantiate the project chaincode

8) Upload the preliminary contract template

2. Operator joins

1) Deploy SD-WAN carrier equipment

2) Web-side and organization authentication platform deployment

3) Generate organizational relationship and identity certificate

4) Ordering service starts and joins

5) Peer node startup

6) Peer node joins application channel

7) Install the project chaincode

3. User join

1) Deploy SD-WAN user equipment

2) Web-side and organization authentication platform deployment

3) Generate organizational relationship and identity certificate

4) Peer node startup

5) Peer node joins application channel

6) Install the project chaincode

Since then, the deployment of users, operators and third-party platforms has been completed, and the system startup has been completed, and business processes such as registration, contract signing, scheduling, collection, and settlement can be performed.

The network quality involved in this application is reflected by the network quality data. There are contracts signed between users and third parties, contracts signed between operators and third parties, and contracts signed between operators and users. The agreement is embodied in traffic parameters, demand parameters, service parameters, etc. In the acquisition unit, it is the quality detection parameter, which is used to describe the network performance indicators within a period of time, and usually includes the following parameters: recording start time begintime, recording end time endtime, maximum jitter maxShake, average rate rate, delay delay, bandwidth bandwidth, packet loss rate packetLoss, etc.

The above are only preferred embodiments of the present application, and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application. Inside.

Claims

A blockchain-based SD-WAN business system, characterized in that the business system includes

a blockchain node module, where the blockchain node module includes device nodes, and the device nodes are divided into third-party platform-side nodes, user-side nodes, and operator-side nodes;

A smart contract module, which is used to realize the functions of contract signing, bookkeeping, settlement and punishment among third-party platforms, users and operators;

a blockchain user module, the blockchain user module is used to provide users with a client that interacts with the blockchain;

SD-WAN service module, the SD-WAN service module is responsible for intelligent network scheduling according to contract data and network quality;

a platform server module, the platform server module is used to perform registration and signing functions for users and operators;

Authentication platform service module, the authentication platform service module is responsible for providing operation and maintenance functions for the blockchain, responsible for member identity authentication, license access management, and issuing signature certificates, communication certificates, and service certificates to accounts or nodes that are successfully authenticated, and is responsible for Management of certificates.
The blockchain-based SD-WAN business system according to claim 1, wherein the SD-WAN service module is divided into four units: scheduling, collection, network probe and scheduling agent, wherein,

The scheduling unit is responsible for network traffic scheduling, and the collection unit is responsible for real-time traffic collection at both ends;

The network probe and the scheduling agent unit are both deployed on user and operator equipment.
The blockchain-based SD-WAN business system according to claim 1, wherein the smart contract module is divided into:

Identity verification, authorization and authentication module: responsible for identifying the user's read and write permissions;

Signing module: responsible for all signing processes;

Accounting module: responsible for obtaining traffic usage records from the acquisition system during the scheduling process;

Settlement module: responsible for clearing the billing process between users and operators;

Punishment module: responsible for recording the violations of operators, third parties and users, and use it as a certificate for later punishment.
A blockchain-based SD-WAN service implementation method, characterized in that the method includes the following steps:

Step 1, the operator and the user respectively register and sign in the service module of the blockchain authentication platform;

Step 2, the SD-WAN controller performs intelligent network scheduling according to the contract data and network quality;

Step 3, the smart contract module implements accounting and settlement for the traffic generated by the user according to the method specified in the contract.
The service implementation method according to claim 4, wherein the signing by the user in the service module of the blockchain authentication platform includes the following two modes:

Direct signing mode: The contracting parties of the direct signing mode are the operator and the user. In this mode, the third-party platform provides different operators for the user to choose, and does not participate in the contract signing process;

Proxy signing mode: The contracting parties of the proxy signing mode are the third-party platform and the user. When the third-party platform signs the contract with the operator, the operator signs a contract that agrees to be freely scheduled, and can be freely scheduled during the network traffic scheduling process.
The service implementation method according to claim 4, wherein the step 2 is specifically:

Step 2.1, the SD-WAN controller first identifies the form that the user signs in the blockchain authentication platform service module. If it is a direct sign mode, the blockchain scheduling unit sends a scheduling instruction to the user and the operator scheduling agency unit, and the user Establish a connection with the operator to start communication;

If it is an agent signing mode, the blockchain scheduling unit searches for an operator that matches the traffic parameters in the contract, and then sends a scheduling instruction to the user and the operator's scheduling agent, and the user and the operator establish a connection to start communication;

Step 2.2, the user and the operator equipment network probe pushes the traffic record to the collection unit of the SD-WAN controller;

Step 2.3, when the user equipment probe detects that the network quality is degraded, it feeds back the network quality to the collection unit, and in the proxy sign mode, the user requests the scheduling unit for traffic scheduling;

Step 2.4, the scheduling unit sends a scheduling instruction to the user scheduling agent unit according to the user's subscription status.
The service implementation method according to claim 4, wherein the step 3 is specifically:

In the direct signing mode, the settlement is based on the method stipulated in the contract, the user directly settles with the operator, and the operator clears the payment record on the chain after settlement.
The service implementation method according to claim 4, wherein the step 3 is specifically: in the proxy signing mode,

Step 3.1, at the time agreed in the contract, the platform server submits a settlement application to the blockchain;

Step 3.2, the blockchain platform generates the user's bill according to the contract, the bill enters the pending settlement state, and then sends the bill back to the platform server;

Step 3.3, the platform server sends the bill to the corresponding user;

Step 3.4, the user conducts offline settlement with the third-party platform;

Step 35: After the offline settlement is completed, the platform server submits the bill-settled transaction to the blockchain platform;

Step 3.6, the blockchain platform updates the bill status and informs the user that the bill has been settled.
The service implementation method according to claim 4, wherein the method further comprises:

The operator's contract change process is as follows:

In the direct-signature mode, the operator's contract is changed according to the operator's regulations. If the user is not satisfied with the change result, choose to terminate the contract with the operator and re-select a new operator;

In the proxy signing mode, the operator first submits a change application to the blockchain platform, and then the blockchain records the change application and sends a message of the operator's contract change to the SD-WAN scheduling module, and then the SD-WAN scheduling module will The operator's equipment is disconnected. After the blockchain changes the contract status and sends the contract template to the operator administrator, the operator administrator affixes the electronic signature and submits the contract to the blockchain; The stamped electronic contract is stamped with an electronic signature and uploaded to the blockchain. After the blockchain changes the contract status, the SD-WAN scheduling module will be notified of the operator's new service parameters and tariffs.
The service implementation method according to claim 4, wherein the method further comprises:

The user change contract process is as follows:

In the direct signing mode, the user requests to change the contract to negotiate directly with the operator, and upload the new contract to the blockchain after completion;

6. In the proxy signing mode, the enterprise user submits a contract change application to the blockchain platform, and the blockchain records the change application and sends a message to the SD-WAN scheduling module to notify the user that the contract will be changed. The SD-WAN scheduling module The user's device is disconnected; then, the blockchain changes the contract status and sends the contract template to the corresponding user, and the user affixes the electronic signature and submits the contract to the blockchain; the platform server finds the electronic signature to be sealed After the contract is affixed with an electronic signature and uploaded to the blockchain; finally, the blockchain notifies the SD-WAN scheduling module, the user, and the platform that the contract change is completed after receiving the contract signed by both parties, and the SD-WAN controller starts scheduling.