Cross-domain network slice resource coordination method and device, and storage medium

Abstract

This application provides a method, apparatus, and storage medium for coordinating cross-domain network slice resources. The method includes: broadcasting a slice resource request message through a blockchain network to trigger a first smart contract; obtaining a contract template for the first smart contract, the contract template being used to characterize the resource distribution of resource providers; selecting a contract template based on a second smart contract, writing the selected contract template into the first smart contract, and storing it in the blockchain network; and coordinating cross-domain network slice resources based on the selected contract template. This application avoids third-party intervention in coordination by broadcasting the resource request message of the resource requester through a blockchain network, achieving decentralization and cross-domain resource sharing; obtaining contract templates representing the resource distribution of all parties involved in resource coordination based on the first smart contract shortens the iterative coordination process; and using the second smart contract to select the contract template accelerates the resource coordination process.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus and storage medium for coordinating cross-domain network slice resources. Background Technology

[0002] The essence of network slicing is to divide the infrastructure network into multiple independent and isolated logical networks based on the different service needs of different users.

[0003] The construction of end-to-end network slicing requires resource sharing support, often necessitating cross-domain implementation at the underlying level. Cross-domain means that the underlying infrastructure consists of multiple infrastructure providers, with information not shared between domains and different resource prices. A multi-domain edge coordinator network architecture is used to achieve cross-domain resource coordination. Single-domain orchestrators are responsible for resource coordination within their own domain and report resource information within their own domain to the multi-domain orchestrators via the blockchain. The multi-domain orchestrators, based on the resource information reported by each single-domain orchestrator, guide the single-domain orchestrators to instantiate resources within their own domains, thus achieving the goal of cross-domain resource coordination.

[0004] However, the blockchain network deployed between the multi-domain orchestrator and the single-domain orchestrator is only used for security between nodes. In reality, it still relies on the central node "multi-domain orchestrator" to achieve global resource coordination, which fails to achieve decentralization and is difficult to resist the occurrence of single points of failure. Summary of the Invention

[0005] To address the problems existing in related technologies, embodiments of this application provide a method, apparatus, and storage medium for coordinating cross-domain network slice resources.

[0006] In a first aspect, embodiments of this application provide a method for coordinating cross-domain network slice resources, including:

[0007] The first smart contract is triggered by broadcasting a slice resource request message through the blockchain network.

[0008] Obtain a contract template for the first smart contract, the contract template being used to characterize the resource distribution of the resource provider;

[0009] A contract template is selected based on the second smart contract. The selected contract template is written into the first smart contract and stored in the blockchain network. The first smart contract and the second smart contract are smart contracts of different types.

[0010] Coordinating cross-domain network slice resources based on the selected contract template.

[0011] Optionally, obtaining the contract template for the first smart contract includes:

[0012] Retrieve the contract template already written into the first smart contract; or,

[0013] Obtain the contract template generated by the resource provider based on the first smart contract.

[0014] Optionally, obtaining the contract template for the first smart contract includes:

[0015] Obtain contract templates generated by different resource providers for the first smart contract; or,

[0016] Obtain a contract template jointly generated by multiple resource providers for the first smart contract.

[0017] Optionally, the method further includes:

[0018] Based on the selected contract template, establish point-to-point communication with the corresponding resource provider.

[0019] Optionally, the method further includes:

[0020] Based on the selected contract template and the broadcast message of the blockchain network, the first public key of the corresponding resource provider in the blockchain network is determined;

[0021] The first public key is used to encrypt the first Internet Protocol address, a random number and a second public key, and then the encrypted data is sent to the corresponding resource provider. The second public key is the public key of the resource requester in the Internet Protocol network.

[0022] The system receives the random number encrypted with the second public key sent by the resource provider and authenticates the identity of the resource provider.

[0023] Optionally, establishing peer-to-peer communication with the corresponding resource provider based on the selected contract template includes:

[0024] Based on the selected contract template and the broadcast message of the blockchain network, the first public key of the corresponding resource provider in the blockchain network is determined;

[0025] A session key is generated using the first public key and a first private key that is randomly generated by itself, and then the session key is used to establish peer-to-peer communication with the corresponding resource provider.

[0026] Optionally, the session key is determined using the ephemeral-elliptic-Diffie-Hellman algorithm.

[0027] Optionally, the method further includes:

[0028] Based on point-to-point communication with the resource provider to negotiate the service level agreement;

[0029] The agreed-upon service level agreement will be broadcast and stored on the blockchain network.

[0030] Optionally, triggering the first smart contract includes:

[0031] The first smart contract is triggered based on a first condition parameter array, which is a quantitative representation of the resource distribution and expected value of the resource price of the resource requester.

[0032] Optionally, the contract template selected by the second smart contract is a contract template whose approximation of the second condition parameter array and the first condition parameter array meets a preset condition, and the second condition parameter array is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template.

[0033] Optionally, the contract template may include at least one of the following:

[0034] The identifier of the resource provider;

[0035] Resources that the resource provider can offer;

[0036] The resource provider can offer the price of the resource;

[0037] The preferential policies of resource providers;

[0038] Resource providers can offer preferential prices for resources;

[0039] Punishment strategies for resource providers.

[0040] Secondly, embodiments of this application also provide a method for coordinating cross-domain network slice resources, including:

[0041] The first smart contract initiated by the resource requester through the blockchain network;

[0042] A contract template is generated based on the first smart contract, and the contract template is used to represent the resource distribution of the resource provider;

[0043] The network slice resources are coordinated by executing the contract template selected based on the second smart contract. The selected contract template is written into the first smart contract and stored in the blockchain network. The first smart contract and the second smart contract are smart contracts of different types.

[0044] Optionally, generating a contract template based on the first smart contract includes:

[0045] A contract template is generated jointly with other resource providers based on the first smart contract.

[0046] Optionally, the method further includes:

[0047] Establish point-to-point communication with the resource requester.

[0048] Optionally, the method further includes:

[0049] Based on the selected contract template and the broadcast message of the blockchain network, the first public key of the corresponding resource provider in the blockchain network is determined;

[0050] The first public key is used to encrypt the first Internet Protocol address, a random number and a second public key, and then the encrypted data is sent to the corresponding resource provider. The second public key is the public key of the resource requester in the Internet Protocol network.

[0051] The system receives the random number encrypted with the second public key sent by the resource provider and authenticates the identity of the resource provider.

[0052] Optionally, establishing point-to-point communication with the resource requester includes:

[0053] The resource requester's third public key in the blockchain network is determined based on broadcast messages in the blockchain network;

[0054] A session key is generated using the third public key and a randomly generated second private key, and then the session key is used to establish peer-to-peer communication with the resource requester.

[0055] Optionally, the session key is determined using the ephemeral-elliptic-Diffie-Hellman algorithm.

[0056] Optionally, the method further includes:

[0057] Based on point-to-point communication with the resource requester to negotiate the service level agreement;

[0058] The agreed-upon service level agreement will be broadcast and stored on the blockchain network.

[0059] Optionally, the contract template selected by the second smart contract is a contract template whose approximation of the second condition parameter array and the first condition parameter array meets a preset condition. The second condition parameter array is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template, and the first condition parameter array is a quantitative representation of the resource distribution and expected resource price of the resource requester.

[0060] Optionally, the contract template may include at least one of the following:

[0061] The identifier of the resource provider;

[0062] Resources that the resource provider can offer;

[0063] The resource provider can offer the price of the resource;

[0064] The preferential policies of resource providers;

[0065] Resource providers can offer preferential prices for resources;

[0066] Punishment strategies for resource providers.

[0067] Thirdly, embodiments of this application also provide a first network functional entity, including a memory, a transceiver, and a processor;

[0068] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and executing the cross-domain network slice resource coordination method provided in the first aspect as described above.

[0069] Fourthly, embodiments of this application also provide a second network functional entity, including a memory, a transceiver, and a processor;

[0070] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and executing the cross-domain network slice resource coordination method provided in the second aspect as described above.

[0071] Fifthly, embodiments of this application also provide a cross-domain network slice resource coordination device, comprising:

[0072] The smart contract triggering unit is used to broadcast a slice resource request message through the blockchain network to trigger the first smart contract.

[0073] A contract template acquisition unit is used to acquire a contract template for the first smart contract, wherein the contract template is used to characterize the resource distribution of the resource provider;

[0074] The contract template selection unit is used to select a contract template based on the second smart contract, write the selected contract template into the first smart contract and store it in the blockchain network. The first smart contract and the second smart contract are smart contracts of different types.

[0075] The slice resource coordination unit is used to coordinate cross-domain network slice resources based on a selected contract template.

[0076] Sixthly, embodiments of this application also provide a cross-domain network slice resource coordination device, including:

[0077] The smart contract acquisition unit is used to acquire the first smart contract initiated by the resource requester through the blockchain network.

[0078] A contract template generation unit generates a contract template based on the first smart contract. The contract template is used to represent the resource distribution of the resource provider.

[0079] The contract template execution unit is used to execute a contract template selected based on a second smart contract, coordinate network slice resources, and write the selected contract template into the first smart contract and store it in the blockchain network. The first smart contract and the second smart contract are smart contracts of different types.

[0080] In a seventh aspect, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing the processor to execute the cross-domain network slice resource coordination method provided in the first or second aspect as described above.

[0081] Eighthly, embodiments of this application also provide a computer-readable storage medium storing a computer program for causing a computer to execute the cross-domain network slice resource coordination method provided in the first or second aspect as described above.

[0082] In a ninth aspect, embodiments of this application also provide a communication device readable storage medium storing a computer program for causing the communication device to execute the cross-domain network slice resource coordination method provided in the first or second aspect as described above.

[0083] In a tenth aspect, embodiments of this application also provide a chip product readable storage medium storing a computer program for causing the chip product to execute the cross-domain network slice resource coordination method provided in the first or second aspect as described above.

[0084] The cross-domain network slice resource coordination method, apparatus, and storage medium provided in this application broadcast the slice resource request message of the resource requester through the blockchain network, avoiding the involvement of third parties in the coordination and realizing decentralization and cross-domain resource sharing; based on the first smart contract, the contract template used by the parties to coordinate the resource to represent the resource distribution is obtained, shortening the repeated coordination process; and the second smart contract is used to select the contract template, which speeds up the resource coordination process. Attached Figure Description

[0085] To more clearly illustrate the technical solutions in the embodiments or related technologies of this application, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0086] Figure 1 This is a schematic diagram of a network architecture for multi-domain edge coordination provided by related technologies;

[0087] Figure 2 This is one of the scenario diagrams illustrating the cross-domain network slice resource coordination method provided in the embodiments of this application;

[0088] Figure 3 This is a second scenario illustration of the cross-domain network slice resource coordination method provided in the embodiments of this application;

[0089] Figure 4 This is one of the flowcharts illustrating the cross-domain network slice resource coordination method provided in the embodiments of this application;

[0090] Figure 5 This is a schematic diagram of the process of negotiating a key using the ECDHE algorithm provided in an embodiment of this application;

[0091] Figure 6 This is the second flowchart illustrating the cross-domain network slice resource coordination method provided in this application embodiment;

[0092] Figure 7 This is the third scenario illustration of the cross-domain network slice resource coordination method provided in the embodiments of this application;

[0093] Figure 8 This is a schematic diagram of the structure of the first network functional entity provided in the embodiments of this application;

[0094] Figure 9 This is a schematic diagram of the structure of the second network functional entity provided in the embodiments of this application;

[0095] Figure 10 This is one of the structural schematic diagrams of the cross-domain network slice resource coordination device provided in the embodiments of this application;

[0096] Figure 11 This is the second schematic diagram of the cross-domain network slice resource coordination device provided in the embodiments of this application. Detailed Implementation

[0097] To better describe the technical solutions in the embodiments of this application, relevant knowledge is introduced below.

[0098] Network operators expand network capacity through collaboration and resource sharing among multiple infrastructure networks, thereby reducing deployment costs and increasing return on investment. To provide users with differentiated and customized services, the concept of network slicing was proposed. Essentially, it involves dividing the infrastructure network into multiple independent and isolated logical networks based on service requirements.

[0099] End-to-end network slicing requires resource sharing to support slice construction, often necessitating cross-domain implementation at the underlying level. Cross-domain means the underlying infrastructure consists of multiple infrastructure providers, with information not shared between domains and varying resource prices. Therefore, how virtual network providers can collaborate across these underlying domains to achieve rapid deployment is a key challenge in cross-domain implementation.

[0100] Meanwhile, the underlying infrastructure spans multiple infrastructure providers. When multiple providers participate in the co-construction and sharing of network infrastructure, consideration should be given to how to accurately, efficiently, in real time, and reliably settle the resource service contributions and consumption of each provider in this distributed architecture. Key parameters and operation and maintenance information should be stored for post-event traceability or auditing to avoid disputes.

[0101] Figure 1 This is a schematic diagram of a network architecture for multi-domain edge coordination provided by related technologies, such as... Figure 1 As shown, a single-domain orchestrator is responsible for coordinating resources within its own domain and reports resource information within its own domain to the multi-domain orchestrator via the blockchain. The multi-domain orchestrator uses the resource information reported by each single-domain orchestrator to guide the single-domain orchestrator to instantiate resources within its own domain, thereby achieving the purpose of cross-domain resource coordination.

[0102] However, the blockchain network deployed between the multi-domain orchestrator and the single-domain orchestrator is only used for security between nodes. In reality, it still relies on the central node "multi-domain orchestrator" to achieve global resource coordination, which fails to achieve decentralization and is difficult to resist the occurrence of single points of failure.

[0103] A single point of failure refers to a situation where the failure of any single point in a system renders the entire system inoperable. For example, if the multi-domain orchestrator fails, the entire multi-domain edge coordination system will cease to function. A single point of failure is essentially a system-wide failure.

[0104] Decentralization does not mean eliminating the center, but rather allowing nodes to freely choose and determine the center.

[0105] To address the aforementioned problems in related technologies, this application provides a cross-domain network slice resource coordination method, apparatus, and storage medium. It broadcasts resource request messages from resource requesters through a blockchain network, avoiding third-party intervention in coordination and achieving decentralization and cross-domain resource sharing. A first smart contract is used to obtain contract templates representing resource distribution from all parties involved in resource coordination, shortening the iterative coordination process. A second smart contract is used to select contract templates, accelerating the resource coordination process.

[0106] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0107] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0108] The technical solutions provided in this application can be applied to various systems, especially 5G systems. For example, applicable systems include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), and 5G New Radio (NR). All of these systems include terminal equipment and network equipment. The system may also include a core network component, such as the Evolved Packet System (EPS) or the 5G system (5GS).

[0109] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0110] The cross-domain network slice resource coordination method provided in this application embodiment can be applied in the following scenarios:

[0111] Figure 2 This is one of the scenario illustrations of the cross-domain network slice resource coordination method provided in the embodiments of this application, such as... Figure 2 As shown, each square represents a blockchain node. Infrastructure Providers (InPs) achieve collaboration between infrastructure networks through resource sharing to reduce operation and maintenance costs and increase revenue sources, providing resource support to users based on the collaborative joint infrastructure network.

[0112] In the technical solution provided in this application embodiment, blockchain is deployed among different infrastructure providers, and the available resources among different infrastructure providers are collected through blockchain. The blockchain network is used to realize resource negotiation and sharing among different infrastructure providers. At the same time, the immutable characteristics of blockchain are used to record transaction information, and auditing and billing are carried out based on the transaction information records, avoiding the intervention of third parties.

[0113] End-to-end network slicing requires resource sharing across the radio access network, bearer network, and core network. However, logical isolation between different network slices is also necessary. In the radio access network, virtualization technology can be used to construct network slices across multiple heterogeneous networks and achieve isolation between slices.

[0114] Figure 3 This is a second scenario illustration of the cross-domain network slice resource coordination method provided in this application embodiment, such as... Figure 3 As shown, dashed lines represent logical connections, and wireless infrastructure is shared among multiple infrastructure providers. Figure 3 The document lists wireless networks belonging to different infrastructure providers (InP1 and InP2), namely, a 5G network and a WiFi network. It should be noted that the technical solutions provided in this application are not limited to these two network standards; multiple access networks of different standards may exist.

[0115] InP1 is the infrastructure provider for 5G networks, where 5G base stations (gNBs) establish connections with the core network to access the internet. InP2 is the infrastructure provider for WiFi networks, where wireless access points (APs) establish connections with WiFi access gateways (WAGs) to access the internet.

[0116] To facilitate the sharing of wireless resources among different infrastructure providers, Network Function Virtualization (NFV) technology has been introduced between gNBs and access points (APs), enabling some gNBs or APs to have virtualization capabilities. This involves using a hypervisor to create software instances—virtual base stations (VgNBs) and virtual access points (VAPs). The VgNB or VAP emulates the basic functions of other infrastructure providers. The hypervisor allows gNBs to virtualize their physical (PHY) wireless resources and enables sharing among multiple software instances running above the physical layer.

[0117] The Software Defined Network (SDN) controllers in InP1 and InP2 are logical modules that orchestrate and manage software instances VgNB and VAP to ensure intelligent networking.

[0118] The management module within the InP1 domain is a logical function module. It establishes a logical connection with the SDN controller in InP1 and is responsible for sending network performance and resource information to the SDN controller so that the SDN controller can have a comprehensive understanding of the network. In turn, InP1 can share its underutilized resources based on this information. Here, gNB-DU represents the Distributed Unit (DU) of the base station, and AMF and UPF represent the Access and Mobility Management Function (AMF) and User Plane Function (UPF), respectively.

[0119] The WiFi gateway within the InP2 domain is responsible for aggregating traffic from multiple WiFi APs and handling internet connections across the entire WiFi network. The WAG plays the same role as the InP1 management module, establishing a logical connection with the SDN controller in InP2 and sending network performance and resource information to the SDN controller. This allows the SDN controller to have a comprehensive understanding of the network, enabling InP2 to share its underutilized resources based on this information.

[0120] When an infrastructure provider has resource needs, it is a resource requester; when the infrastructure provider provides resources, it is a resource provider.

[0121] Figure 4 This is one of the flowcharts illustrating the cross-domain network slice resource coordination method provided in this application embodiment, such as... Figure 4 As shown, the method includes at least the following steps:

[0122] Step 401: Broadcast the slice resource request message through the blockchain network to trigger the first smart contract.

[0123] Specifically, for the resource requester, when there is a resource demand, the resource request message is broadcast through the blockchain, triggering the first smart contract.

[0124] Blockchain is a novel application model encompassing distributed data storage, peer-to-peer transmission, consensus mechanisms, and cryptographic algorithms. In this application, blockchain is deployed across different infrastructure providers, and resources available among these providers are collected via blockchain, enabling resource negotiation and sharing among them through the blockchain network.

[0125] A smart contract is a mechanism that uses code deployed on a blockchain to perform specified functions on-chain without supervision. Once a clause in the smart contract is triggered at a certain time, the code executes automatically. The first smart contract executes functions such as generating and invoking contract templates.

[0126] Step 402: Obtain a contract template for the first smart contract. The contract template is used to represent the resource distribution of the resource provider.

[0127] Specifically, the resource requester obtains at least one contract template for the first smart contract through the blockchain network. The contract template is used to characterize the resource distribution of the resource provider, etc.

[0128] Step 403: Select a contract template based on the second smart contract, write the selected contract template into the first smart contract and store it in the blockchain network. The first smart contract and the second smart contract are smart contracts of different types.

[0129] Specifically, when multiple contract templates are available, a selection process needs to be performed. This selection is led by the second smart contract, which, based on the resource requester's needs, chooses the most suitable template. The selected template is then written into the first smart contract and stored on the blockchain network. The first and second smart contracts are different types of smart contracts. The first smart contract performs functions such as generating and calling contract templates, while the second smart contract performs the function of selecting a contract template.

[0130] Optionally, the contract template can be reselected before the transaction is recorded on the blockchain.

[0131] Step 404: Coordinate cross-domain network slice resources based on the selected contract template.

[0132] Specifically, after selecting a contract template, the selected contract template is used to coordinate cross-domain network slice resources.

[0133] The cross-domain network slice resource coordination method provided in this application broadcasts the slice resource request message of the resource requester through the blockchain network, avoiding the involvement of third parties in the coordination and realizing decentralization and cross-domain resource sharing; it obtains contract templates representing the resource distribution of all parties involved in resource coordination based on a first smart contract, shortening the iterative coordination process; and it accelerates the resource coordination process by using a second smart contract to select the contract template.

[0134] Optionally, obtaining the contract template for the first smart contract includes:

[0135] Retrieve the contract template already written into the first smart contract; or,

[0136] Obtain the contract template generated by the resource provider based on the first smart contract.

[0137] Specifically, the contract template for the first smart contract obtained by the resource requester can be distinguished as follows based on the timing of the contract template's generation:

[0138] ① The contract template has been written into the first smart contract.

[0139] ②The resource provider generates a new contract template based on the first smart contract.

[0140] The contract template already written into the first smart contract can be a contract template stored in the blockchain during the historical resource coordination process, or a contract template that the resource provider pre-generates and stores in the blockchain based on its own resource distribution and resource price information.

[0141] Optionally, obtaining the contract template for the first smart contract includes:

[0142] Obtain contract templates generated by different resource providers for the first smart contract; or,

[0143] Obtain a contract template jointly generated by multiple resource providers for the first smart contract.

[0144] Specifically, for the contract template obtained by the resource requester for the first smart contract, the following distinctions can be made based on the number of resource providers corresponding to the contract template:

[0145] ① Different resource providers generate contract templates for the first smart contract, and there can be multiple contract templates.

[0146] ② A contract template jointly generated by multiple resource providers for the first smart contract. In this case, the number of contract templates can be one.

[0147] In both cases, the type of the first smart contract is also different.

[0148] The cross-domain network slice resource coordination method provided in this application uses a contract template to represent the resource distribution and resource prices of each resource provider, which can effectively shorten the resource negotiation process.

[0149] Optionally, the method further includes:

[0150] Based on the selected contract template, establish point-to-point communication with the corresponding resource provider.

[0151] Specifically, after selecting a contract template, the resource requester establishes point-to-point communication with the corresponding resource provider based on the selected contract template.

[0152] After the resource requester selects a contract template, they can determine the location of one or more corresponding resource providers on the blockchain, but they cannot obtain the actual communication addresses of the resource providers. Therefore, peer-to-peer encrypted communication is required between the resource requester and the resource provider to achieve mutual identity verification and information exchange, thereby ensuring the security of the transaction.

[0153] Optionally, the method further includes:

[0154] Based on the selected contract template and the broadcast message of the blockchain network, the first public key of the corresponding resource provider in the blockchain network is determined;

[0155] The first public key is used to encrypt the first Internet Protocol address, a random number and a second public key, and then the encrypted data is sent to the corresponding resource provider. The second public key is the public key of the resource requester in the Internet Protocol network.

[0156] The system receives the random number encrypted with the second public key sent by the resource provider and authenticates the identity of the resource provider.

[0157] Specifically, in the blockchain network, the blockchain node address corresponding to each basic provider is its private key, and the public key certificate is issued by a trusted third-party Certificate Authority (CA) to each participant in the blockchain network, so that resource requesters and resource providers can use asymmetric keys to verify each other's identities to ensure that each other's identities are trustworthy.

[0158] In Internet Protocol (IP) networks, each infrastructure provider also has its own corresponding IP address and public key.

[0159] In this embodiment of the application, the first public key is the public key of the resource provider in the blockchain network, the second public key is the public key of the resource requester in the IP network, and the third public key is the public key of the resource requester in the blockchain network.

[0160] For the resource requester, after selecting a contract template, the blockchain address of the corresponding resource provider is determined based on the selected contract template, and the first public key of the resource provider is obtained through the broadcast message of the blockchain network.

[0161] The resource requester uses the resource provider's first public key in the blockchain network to encrypt its own first IP address, random number N, and second public key. This encrypted message is then broadcast to the resource provider via the blockchain network. Only the resource provider can decrypt the message encrypted using its first public key.

[0162] After decrypting the broadcast message, the resource provider obtains the resource requester's first IP address, a random number N, and the resource requester's second public key in the IP network. The resource provider then sends the random number N, encrypted with the second public key, to the resource requester's first IP address. After the resource requester decrypts and authenticates the random number, the two parties can subsequently negotiate session keys and establish peer-to-peer communication. Only the resource requester can decrypt the random number encrypted with the second public key. Therefore, authentication occurs within the IP network, not the blockchain network.

[0163] The cross-domain network slice resource coordination method provided in this application involves the resource requester determining the first public key of the corresponding resource provider in the blockchain network based on the selected contract template. The resource requester uses the first public key to encrypt its own IP address, random number, and second public key in the IP network, and informs the resource provider of its own IP address, random number, and second public key. This allows the resource provider to use the second public key to encrypt the obtained random number and send it back to the resource requester. This completes the identity authentication of both parties in the IP network, realizes the information exchange between the two parties, and ensures the security of cross-domain network slice resource coordination.

[0164] Optionally, establishing peer-to-peer communication with the corresponding resource provider based on the selected contract template includes:

[0165] Based on the selected contract template and the broadcast message of the blockchain network, the first public key of the corresponding resource provider in the blockchain network is determined;

[0166] A session key is generated using the first public key and a first private key that is randomly generated by itself, and then the session key is used to establish peer-to-peer communication with the corresponding resource provider.

[0167] Specifically, for the resource requester, after selecting a contract template, the first blockchain address of the corresponding resource provider is determined based on the selected contract template, and the first public key of the resource provider is obtained through a broadcast message on the blockchain network. Correspondingly, the resource requester also broadcasts its third public key in the blockchain network, enabling the resource provider to obtain the third public key. In the blockchain network, after selecting a contract template, the resource requester cannot directly obtain the communication address of the resource provider, but can determine its corresponding first blockchain address, thereby determining its first public key in the blockchain network.

[0168] The resource requester uses the resource provider's first public key in the blockchain network and its own randomly generated first private key to generate a session key. Using this session key, the requester and resource provider negotiate key information within the blockchain network, establishing peer-to-peer communication. At this point, both authentication and session key negotiation take place within the blockchain network.

[0169] The cross-domain network slice resource coordination method provided in this application embodiment involves the resource requester determining the first public key of the corresponding resource provider in the blockchain network based on the selected contract template, generating a session key using the first public key of the resource provider and its own first private key, realizing key negotiation in the blockchain network, establishing peer-to-peer communication between the two parties, realizing information exchange between the two parties, and ensuring the security of cross-domain resource coordination.

[0170] Optionally, the session key is determined using the ephemeral-elliptic-Diffie-Hellman algorithm.

[0171] Specifically, the session key between the resource requester and the resource provider can be determined using the Elliptic Curve Diffie–Hellman key exchange (ECDHE) algorithm.

[0172] Figure 5 This is a schematic diagram of the process for negotiating a key using the ECDHE algorithm, as provided in an embodiment of this application. Figure 5 As shown, in the ECDHE key negotiation algorithm, the negotiating parties pre-determine which elliptic curve to use and the base point G on the curve; both parameters are publicly available. In this application, the determined elliptic curve and corresponding base point G are broadcast via the blockchain network for use in the subsequent key negotiation process.

[0173] The resource requester randomly generates a random number r as its first private key SK1, and generates a third public key PK1 = rG based on its first private key; similarly, the resource provider randomly generates a random number q as its second private key SK2, and generates a first public key PK2 = qG based on its second private key.

[0174] Both the resource requester and the resource provider broadcast their public keys through the blockchain network. Based on the received public key and their own private key, the resource requester and provider generate a session key K = r * PK2 = q * PK1 = rqG. The two parties then use this session key to establish peer-to-peer encrypted communication.

[0175] In the process of determining the session key using the ECDHE key negotiation algorithm, the private keys of both parties are random, temporarily generated and not disclosed. Even with public information (including elliptic curves and base points G), it is difficult to generate the discrete logarithm (i.e., the private key) on the elliptic curve.

[0176] The cross-domain network slice resource coordination method provided in this application uses the ECDHE key negotiation algorithm to determine the session key and establish encrypted communication between the resource requester and the resource provider, thus ensuring the security of resource negotiation.

[0177] Optionally, the method further includes:

[0178] Based on point-to-point communication with the resource provider to negotiate the service level agreement;

[0179] The agreed-upon service level agreement will be broadcast and stored on the blockchain network.

[0180] Specifically, after the resource requester and the resource provider establish peer-to-peer communication, they negotiate a peer-to-peer Service-Level Agreement (SLA). Once an agreement is reached, the SLA is broadcast in the blockchain network and recorded therein for subsequent SLA violation processing and auditing.

[0181] The cross-domain network slice resource coordination method provided in this application utilizes SLA on-chain to facilitate subsequent SLA violation handling and auditing by all parties involved in resource coordination.

[0182] Optionally, triggering the first smart contract includes:

[0183] The first smart contract is triggered based on a first condition parameter array, which is a quantitative representation of the resource distribution and expected value of the resource price of the resource requester.

[0184] Specifically, after a resource requester broadcasts its resource request through the blockchain network, it triggers the corresponding first smart contract based on its own resource situation. Triggering the first smart contract can be achieved through condition parameters. The resource requester triggers the first smart contract based on its own first condition parameter array, which is a quantitative representation of the resource requester's resource distribution and expected resource price, etc.

[0185] Assume the first condition parameter array σ is:

[0186] σ=[σ1,σ2,σ3,...,σ n ]

[0187] Where, σ i This represents an array element. For example, σ1 represents the proportion of a certain resource, σ2 represents the expected price of a certain resource, and σ3 represents network performance.

[0188] Optionally, the contract template selected by the second smart contract is a contract template whose approximation of the second condition parameter array and the first condition parameter array meets a preset condition, and the second condition parameter array is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template.

[0189] Specifically, the selection of contract templates is primarily driven by the second smart contract. After the resource requester broadcasts its resource request through the blockchain network, the corresponding first smart contract is triggered based on its resource situation. The resource distribution and expected resource price of the resource requester are represented by a first condition parameter array. Correspondingly, each contract template also has a second condition parameter array, which is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template.

[0190] The second conditional parameter array μ is:

[0191] μ = [μ1, μ2, μ3, ..., μ n ]

[0192] Where, μ i Represents an array element.

[0193] In the first and second condition parameter arrays, the names of array elements with the same index should be consistent. That is, when i = 1, σ1 and μ1 both represent the proportion of a certain resource; when i = 2, σ2 represents the expected price of a certain resource, and μ2 represents the price of that resource; when i = 3, σ3 and μ3 both represent network performance.

[0194] After obtaining the first condition parameter array σ, the second smart contract compares it with the second condition parameter array μ corresponding to each contract template. It iteratively compares each parameter within the array to obtain the array approximation ω. It then selects the second parameter array whose approximation ω satisfies a preset condition and chooses the corresponding contract template. For example, it selects the contract template corresponding to the second condition parameter array with the smallest array approximation. The array approximation is used to characterize the degree of difference between the second parameter array and the first parameter array.

[0195] Optionally, the contract template may include at least one of the following:

[0196] The identifier of the resource provider;

[0197] Resources that the resource provider can offer;

[0198] The resource provider can offer the price of the resource;

[0199] The preferential policies of resource providers;

[0200] Resource providers can offer preferential prices for resources;

[0201] Punishment strategies for resource providers.

[0202] Specifically, the contract template should include at least one of the following:

[0203] ① Resource provider identifier. This identifier is used to determine the blockchain node address where the resource provider is located.

[0204] ② Resources available from the resource provider. This indicates the distribution of resources provided by the resource provider.

[0205] ③ The price at which the resource provider can offer the resource.

[0206] ④ The resource provider's preferential policies. This indicates the preferential pricing policies offered by the resource provider for the resources.

[0207] ⑤ The resource provider can offer a preferential price for the resource. In this case, there is no need to calculate the preferential price based on the preferential policy; the preferential price is given directly.

[0208] ⑥ The resource provider's penalty strategy. This mainly outlines the penalties for violating the terms of the contract template.

[0209] Optionally, the contract template in the first smart contract can be dynamically adjusted based on the resource provider's resource availability.

[0210] The cross-domain network slice resource coordination method provided in this application uses a contract template to express the resource status and needs of the parties involved in resource negotiation, thereby shortening the iterative negotiation process and reducing the communication costs of resource coordination.

[0211] Figure 6 This is a second flowchart illustrating the cross-domain network slice resource coordination method provided in this application embodiment, as follows: Figure 6 As shown, the method includes at least the following steps:

[0212] Step 601: Obtain the first smart contract initiated by the resource requester through the blockchain network.

[0213] Specifically, the resource provider receives the slice resource request message sent by the resource requester through blockchain broadcast and obtains the first smart contract triggered by the resource requester.

[0214] Step 602: Generate a contract template based on the first smart contract. The contract template is used to represent the resource distribution of the resource provider.

[0215] Specifically, the resource provider generates a contract template based on the first smart contract. The contract template is used to represent the resource distribution of the resource provider, etc.

[0216] Step 603: Execute the network slice resources coordination based on the contract template selected by the second smart contract. The selected contract template is written into the first smart contract and stored in the blockchain network. The first smart contract and the second smart contract are smart contracts of different types. The first smart contract performs functions such as generating and calling contract templates, and the second smart contract performs the function of selecting contract templates.

[0217] Specifically, when there are multiple contract templates, the resource provider executes the contract template selected based on the second smart contract to coordinate network slice resources. The selected contract template is written into the first smart contract and stored in the blockchain network.

[0218] The selection of the contract template is led by the second smart contract. Starting from the resource requester's resource needs, the most suitable contract template is selected from the available templates. The selected template is then written into the smart contract and stored on the blockchain network. Optionally, the contract template can be reselected before the transaction is recorded on the blockchain.

[0219] The cross-domain network slice resource coordination method provided in this application embodiment allows the resource provider to obtain the slice resource request message from the resource requester through blockchain network broadcast, avoiding the involvement of third parties in coordination and realizing decentralization and cross-domain resource sharing. The resource provider provides a contract template to represent the resource distribution based on the first smart contract triggered by the resource requester, shortening the iterative coordination process. The second smart contract is used to select the contract template, which speeds up the resource coordination process.

[0220] Optionally, generating a contract template based on the first smart contract includes:

[0221] A contract template is generated jointly with other resource providers based on the first smart contract.

[0222] Specifically, the contract template can be a template already stored in the first smart contract, or it can be a newly generated template based on the current resource requirements. Different resource providers can generate different contract templates, or multiple resource providers can jointly generate a single contract template.

[0223] The cross-domain network slice resource coordination method provided in this application uses a contract template to represent the resource distribution and resource prices of each resource provider, which can effectively shorten the resource negotiation process.

[0224] Optionally, the method further includes:

[0225] Establish point-to-point communication with the resource requester.

[0226] Specifically, after the resource requester selects a contract template based on the second smart contract, the resource provider and the resource requester need to establish peer-to-peer communication to complete the exchange of information.

[0227] After the resource requester selects a contract template, they can determine the location of one or more corresponding resource providers on the blockchain, but they cannot obtain the actual communication addresses of the resource providers. Therefore, peer-to-peer encrypted communication is required between the resource requester and the resource providers to facilitate information exchange.

[0228] Optionally, the method further includes:

[0229] The system receives a first Internet Protocol address, a random number, and a second public key encrypted with a first public key from the resource requester. The first public key is the public key of the resource provider in the blockchain network, the first Internet Protocol address is the Internet Protocol address corresponding to the resource requester, and the second public key is the public key of the resource requester in the Internet Protocol network.

[0230] After decryption, the first network protocol address, the random number, and the second public key are determined.

[0231] Send the random number encrypted with the second public key to the first Internet Protocol address to perform identity authentication with the resource requester.

[0232] Specifically, the resource provider broadcasts its first public key within the blockchain network. After the contract template is selected, the resource provider receives a broadcast message from the resource requester, which encrypts a first IP address, a random number N, and a second public key using the first public key. Only the resource provider corresponding to the first public key can decrypt this broadcast message. The first public key is the resource provider's public key in the blockchain network, and the second public key is the resource requester's public key in the IP network.

[0233] After decrypting the encrypted broadcast message, the resource provider obtains the first IP address, a random number N, and a second public key corresponding to the resource requester. It then sends the random number N, encrypted with the second public key, to the first IP address. The resource requester decrypts this random number, completing the authentication process. Once authentication is complete, session key negotiation can proceed, establishing peer-to-peer communication.

[0234] The cross-domain network slice resource coordination method provided in this application embodiment involves the resource provider receiving a first IP address, a random number, and a second public key encrypted by the resource provider using the first public key in the blockchain network. After decryption, the resource provider obtains the first IP address, random number, and second public key of the resource requester. Then, the resource provider uses the second public key to encrypt the random number and sends it to the first IP address. This completes the identity authentication of both parties in the IP network, realizes the information exchange between the two parties, and ensures the security of cross-domain resource coordination.

[0235] Optionally, establishing point-to-point communication with the resource requester includes:

[0236] The resource requester's third public key in the blockchain network is determined based on broadcast messages in the blockchain network;

[0237] A session key is generated using the third public key and a randomly generated second private key, and then the session key is used to establish peer-to-peer communication with the resource requester.

[0238] Specifically, resource providers broadcast their corresponding first public key in the blockchain network; similarly, resource requesters broadcast their corresponding third public key in the blockchain network.

[0239] Once the contract template is finalized, the resource provider uses the resource requester's third public key in the blockchain network and its own randomly generated second private key to generate a session key. The resource provider then uses this session key to negotiate the key with the resource requester within the blockchain network, establishing peer-to-peer communication. At this point, both identity authentication and session key negotiation take place within the blockchain network.

[0240] The cross-domain network slice resource coordination method provided in this application embodiment involves the resource provider corresponding to the selected contract template generating a session key using the public key of the resource requester in the blockchain network and its own private key. Key negotiation is then implemented in the blockchain network to establish peer-to-peer communication between the two parties, enabling information exchange and ensuring the security of cross-domain resource coordination.

[0241] Optionally, the session key is determined using the ephemeral-elliptic-Diffie-Hellman algorithm.

[0242] Specifically, the session key between the resource requester and the resource provider can be determined using the ECDHE key negotiation algorithm. For detailed implementation steps and benefits, please refer to [link / reference needed]. Figure 5 The descriptions in the corresponding embodiments are not repeated here.

[0243] Optionally, the method further includes:

[0244] Based on point-to-point communication with the resource requester to negotiate the service level agreement;

[0245] The agreed-upon service level agreement will be broadcast and stored on the blockchain network.

[0246] Specifically, after the resource requester and the resource provider establish peer-to-peer communication, they conduct peer-to-peer SLA negotiation. Once an agreement is reached, the SLA protocol is broadcast in the blockchain network and recorded therein for subsequent SLA violation processing and auditing.

[0247] The cross-domain network slice resource coordination method provided in this application utilizes SLA on-chain to facilitate subsequent SLA violation handling and auditing by all parties involved in resource coordination.

[0248] Optionally, the contract template selected by the second smart contract is a contract template whose approximation of the second condition parameter array and the first condition parameter array meets a preset condition. The second condition parameter array is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template, and the first condition parameter array is a quantitative representation of the resource distribution and expected resource price of the resource requester.

[0249] Specifically, the selection of contract templates is primarily driven by the second smart contract. After the resource requester broadcasts its resource request through the blockchain network, the corresponding first smart contract is triggered based on its resource situation. The resource distribution and expected resource price of the resource requester are represented by a first condition parameter array. Correspondingly, each contract template also has a second condition parameter array, which is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template.

[0250] The first conditional parameter array σ is:

[0251] σ=[σ1,σ2,σ3,...,σ n ]

[0252] Where, σ i Represents an array element.

[0253] The second conditional parameter array μ is:

[0254] μ = [μ1, μ2, μ3, ..., μ n ]

[0255] Where, μ i Represents an array element.

[0256] In the first and second condition parameter arrays, the names of array elements with the same index should be consistent. That is, when i = 1, σ1 and μ1 both represent the proportion of a certain resource; when i = 2, σ2 represents the expected price of a certain resource, and μ2 represents the price of that resource; when i = 3, σ3 and μ3 both represent network performance.

[0257] After obtaining the first condition parameter array σ, the second smart contract compares it with the second condition parameter array μ corresponding to each contract template. It iteratively compares each parameter within the array to obtain the array approximation ω. It then selects the second parameter array whose approximation ω satisfies a preset condition and chooses the corresponding contract template. For example, it selects the contract template corresponding to the second condition parameter array with the smallest array approximation. The array approximation is used to characterize the degree of difference between the second parameter array and the first parameter array.

[0258] Optionally, the contract template may include at least one of the following:

[0259] The identifier of the resource provider;

[0260] Resources that the resource provider can offer;

[0261] The resource provider can offer the price of the resource;

[0262] The preferential policies of resource providers;

[0263] Resource providers can offer preferential prices for resources;

[0264] Punishment strategies for resource providers.

[0265] Specifically, the contract template should include at least one of the following:

[0266] ① Resource provider identifier. This identifier is used to determine the blockchain node address where the resource provider is located.

[0267] ② Resources available from the resource provider. This indicates the distribution of resources provided by the resource provider.

[0268] ③ The price at which the resource provider can offer the resource.

[0269] ④ The resource provider's preferential policies. This indicates the preferential pricing policies offered by the resource provider for the resources.

[0270] ⑤ The resource provider can offer a preferential price for the resource. In this case, there is no need to calculate the preferential price based on the preferential policy; the preferential price is given directly.

[0271] ⑥ The resource provider's penalty strategy. This mainly outlines the penalties for violating the terms of the contract template.

[0272] Optionally, the contract template in the first smart contract can be dynamically adjusted according to the resource provider's resource situation.

[0273] The cross-domain network slice resource coordination method provided in this application uses a contract template to express the resource status and needs of the parties involved in resource negotiation, thereby shortening the iterative negotiation process and reducing the communication costs of resource coordination.

[0274] The technical solutions of the embodiments of this application are further described below through several specific examples.

[0275] Example 1:

[0276] Reference Figure 3 InP1's SDN controller broadcasts the required resources to the blockchain network. Based on the resource requirements published by InP1, other infrastructure providers can generate contract templates (multiple providers can collaborate to provide resources and write them into the contract templates); or, InP1 can trigger existing contract templates based on its own needs.

[0277] A standard contract template must include the provider's identification, the resources the provider can offer, and the corresponding prices. Optionally, other details may be included, such as incentive policies and penalties.

[0278] After InP1 identifies the provider (there may be multiple providers, but we assume it is only InP2 here) through the contract template, InP1 uses InP2's first public key in the blockchain network to encrypt InP1's IP address, a random number, and InP1's second public key in the IP network, and broadcasts it to InP2 (the message encrypted with InP2's second public key in the IP network can only be decrypted by InP2 using its private key).

[0279] After receiving the message, InP2 decrypts it using its private key to obtain InP1's IP address, random number, and InP1's second public key in the IP network. Then, it uses InP1's second public key in the IP network to encrypt the random number and sends it back to InP1 for mutual authentication, and then establishes point-to-point communication between the two.

[0280] InP1 and InP2 negotiate a peer-to-peer SLA agreement. Once an agreement is reached, the SLA agreement is broadcast and recorded in the blockchain network for future SLA violation processing.

[0281] After identifying the infrastructure providers (InP1 and InP2) who will participate in sharing wireless resources, the underlying infrastructure resources will be shared. For example, InP2's VAP will emulate the function of a gNB for wireless communication.

[0282] Example 2:

[0283] Figure 7 This is a third scenario illustration of the cross-domain network slice resource coordination method provided in this application embodiment, such as... Figure 7 As shown, in addition to resource request and resource provision scenarios, the cross-domain network slice resource coordination method provided in this application embodiment is also applicable to resource construction and resource sharing scenarios.

[0284] Different operators share slice resource management. From the perspective of resource management, operator A and operator B share network slice resources. Operator A is the contractor, and operator B is the sharer. The contractor manages the network slices and network resource usage through its own slice management module.

[0285] The sharing party negotiates with the contractor through the blockchain network to conduct inquiries and network maintenance, such as the maintenance status of network resources and the deployment status of network slices. The contractor exclusively builds and manages the wireless network and bearer network resources, while sharing the core network resources built by both parties.

[0286] The specific implementation process is as follows:

[0287] Step a: The sharing party broadcasts its service request on the blockchain network. The slice management module of sharing party operator B receives user slice order requests and broadcasts these requests via the blockchain network.

[0288] Step b: Identify the contractor who meets the business requirements. The sharing operator B, based on its own resource needs, executes a smart contract for the contractor operator A. The contract template contains the available resources and corresponding prices for the business requirements.

[0289] Step c: After identifying the contractor that meets the requirements, deploy a blockchain-based smart contract between the sharing operator B and the contractor operator A, and allocate network resources based on the smart contract.

[0290] The cross-domain network slicing resource coordination method provided in this application utilizes a blockchain network to achieve decentralized resource coordination and cross-domain information sharing; it introduces a contract template for resource coordination based on smart contracts, thereby improving the speed of cross-domain resource negotiation.

[0291] Figure 8 This is a schematic diagram of the structure of the first network functional entity provided in the embodiments of this application, such as... Figure 8 As shown, the first network function entity may include a memory 801, a transceiver 802, and a processor 803.

[0292] The memory 801 is used to store computer programs; the transceiver 802 is used to send and receive data under the control of the processor 803.

[0293] Specifically, transceiver 802 is used to receive and send data under the control of processor 803.

[0294] Among them, Figure 8 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 803 and memory represented by memory 801 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface.

[0295] The transceiver 802 may consist of multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media. The processor 803 is responsible for managing the bus architecture and general processing, and the memory 801 can store data used by the processor 803 during operation.

[0296] The processor 803 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0297] Processor 803 is used to read the computer program in memory 801 and perform the following operations:

[0298] The first smart contract is triggered by broadcasting a slice resource request message through the blockchain network.

[0299] Obtain a contract template for the first smart contract, the contract template being used to characterize the resource distribution of the resource provider;

[0300] Based on the second smart contract, a contract template is selected, written into the smart contract, and stored in the blockchain network;

[0301] Coordinating cross-domain network slice resources based on the selected contract template.

[0302] Optionally, obtaining the contract template for the first smart contract includes:

[0303] Retrieve the contract template already written into the first smart contract; or,

[0304] Obtain the contract template generated by the resource provider based on the first smart contract.

[0305] Optionally, obtaining the contract template for the first smart contract includes:

[0306] Obtain contract templates generated by different resource providers for the first smart contract; or,

[0307] Obtain a contract template jointly generated by multiple resource providers for the first smart contract.

[0308] Optionally, the processor, when reading the computer program from the memory, further performs the following operations:

[0309] Based on the selected contract template, establish point-to-point communication with the corresponding resource provider.

[0310] Optionally, the processor, when reading the computer program from the memory, further performs the following operations:

[0311] Based on the selected contract template and the broadcast message of the blockchain network, the first public key of the corresponding resource provider in the blockchain network is determined;

[0312] The first public key is used to encrypt the first Internet Protocol address, a random number and a second public key, and then the encrypted data is sent to the corresponding resource provider. The second public key is the public key of the resource requester in the Internet Protocol network.

[0313] The system receives the random number encrypted with the second public key sent by the resource provider and authenticates the identity of the resource provider.

[0314] Optionally, establishing peer-to-peer communication with the corresponding resource provider based on the selected contract template includes:

[0315] Based on the selected contract template and the broadcast message of the blockchain network, the first public key of the corresponding resource provider in the blockchain network is determined;

[0316] A session key is generated using the first public key and a first private key that is randomly generated by itself, and then the session key is used to establish peer-to-peer communication with the corresponding resource provider.

[0317] Optionally, the session key is determined using the ephemeral-elliptic-Diffie-Hellman algorithm.

[0318] Optionally, the processor, when reading the computer program from the memory, further performs the following operations:

[0319] Based on point-to-point communication with the resource provider to negotiate the service level agreement;

[0320] The agreed-upon service level agreement will be broadcast and stored on the blockchain network.

[0321] Optionally, triggering the first smart contract includes:

[0322] The first smart contract is triggered based on a first condition parameter array, which is a quantitative representation of the resource distribution and expected value of the resource price of the resource requester.

[0323] Optionally, the contract template selected by the second smart contract is a contract template whose approximation of the second condition parameter array and the first condition parameter array meets a preset condition, and the second condition parameter array is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template.

[0324] Optionally, the contract template may include at least one of the following:

[0325] The identifier of the resource provider;

[0326] Resources that the resource provider can offer;

[0327] The resource provider can offer the price of the resource;

[0328] The preferential policies of resource providers;

[0329] Resource providers can offer preferential prices for resources;

[0330] Punishment strategies for resource providers.

[0331] It should be noted that the first network function entity provided in this application embodiment can implement all the method steps implemented in the method embodiment with the resource requester as the execution subject, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0332] Figure 9 This is a schematic diagram of the structure of the second network functional entity provided in the embodiments of this application, such as... Figure 9 As shown, the second network function entity may include a memory 901, a transceiver 902, and a processor 903.

[0333] The memory 901 is used to store computer programs; the transceiver 902 is used to send and receive data under the control of the processor 903.

[0334] Specifically, transceiver 902 is used to receive and send data under the control of processor 903.

[0335] Among them, Figure 9 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 903 and memory represented by memory 901 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface.

[0336] The transceiver 902 may consist of multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media. The processor 903 is responsible for managing the bus architecture and general processing, and the memory 901 can store data used by the processor 903 during operation.

[0337] The processor 903 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0338] Processor 903 is used to read the computer program in memory 901 and perform the following operations:

[0339] The first smart contract initiated by the resource requester through the blockchain network;

[0340] A contract template is generated based on the first smart contract, and the contract template is used to represent the resource distribution of the resource provider;

[0341] The network slice resources are coordinated by executing the contract template selected based on the second smart contract. The selected contract template is written into the first smart contract and stored in the blockchain network. The first smart contract and the second smart contract are smart contracts of different types.

[0342] Optionally, generating a contract template based on the first smart contract includes:

[0343] A contract template is generated jointly with other resource providers based on the first smart contract.

[0344] Optionally, the processor, when reading the computer program from the memory, further performs the following operations:

[0345] Establish point-to-point communication with the resource requester.

[0346] Optionally, the processor, when reading the computer program from the memory, further performs the following operations:

[0347] Based on the selected contract template and the broadcast message of the blockchain network, the first public key of the corresponding resource provider in the blockchain network is determined;

[0348] The first public key is used to encrypt the first Internet Protocol address, a random number and a second public key, and then the encrypted data is sent to the corresponding resource provider. The second public key is the public key of the resource requester in the Internet Protocol network.

[0349] The system receives the random number encrypted with the second public key sent by the resource provider and authenticates the identity of the resource provider.

[0350] Optionally, establishing point-to-point communication with the resource requester includes:

[0351] The resource requester's third public key in the blockchain network is determined based on broadcast messages in the blockchain network;

[0352] A session key is generated using the third public key and a randomly generated second private key, and then the session key is used to establish peer-to-peer communication with the resource requester.

[0353] Optionally, the session key is determined using the ephemeral-elliptic-Diffie-Hellman algorithm.

[0354] Optionally, the processor, when reading the computer program from the memory, further performs the following operations:

[0355] Based on point-to-point communication with the resource requester to negotiate the service level agreement;

[0356] The agreed-upon service level agreement will be broadcast and stored on the blockchain network.

[0357] Optionally, the contract template selected by the second smart contract is a contract template whose approximation of the second condition parameter array and the first condition parameter array meets a preset condition. The second condition parameter array is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template, and the first condition parameter array is a quantitative representation of the resource distribution and expected resource price of the resource requester.

[0358] Optionally, the contract template may include at least one of the following:

[0359] The identifier of the resource provider;

[0360] Resources that the resource provider can offer;

[0361] The resource provider can offer the price of the resource;

[0362] The preferential policies of resource providers;

[0363] Resource providers can offer preferential prices for resources;

[0364] Punishment strategies for resource providers.

[0365] It should be noted that the second network functional entity provided in this application embodiment can implement all the method steps implemented in the method embodiment with the resource provider as the execution subject, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0366] Figure 10 This is one of the structural schematic diagrams of the cross-domain network slice resource coordination device provided in the embodiments of this application, such as... Figure 10 As shown, the device includes at least:

[0367] Resource request broadcasting unit 1001 is used to broadcast slice resource request messages through the blockchain network and trigger the first smart contract;

[0368] The contract template acquisition unit 1002 is used to acquire a contract template for the first smart contract, wherein the contract template is used to characterize the resource distribution of the resource provider;

[0369] The contract template selection unit 1003 is used to select a contract template based on the second smart contract, write the selected contract template into the first smart contract and store it in the blockchain network. The first smart contract and the second smart contract are smart contracts of different types.

[0370] The slice resource coordination unit 1004 is used to coordinate cross-domain network slice resources based on a selected contract template.

[0371] Optionally, the contract template acquisition unit is specifically used for:

[0372] Retrieve the contract template already written into the first smart contract; or,

[0373] Obtain the contract template generated by the resource provider based on the first smart contract.

[0374] Optionally, the contract template acquisition unit is specifically used for:

[0375] Obtain contract templates generated by different resource providers for the first smart contract; or,

[0376] Obtain a contract template jointly generated by multiple resource providers for the first smart contract.

[0377] Optionally, the device further includes:

[0378] The communication unit is used to establish point-to-point communication with the corresponding resource provider based on the selected contract template.

[0379] Optionally, the device further includes:

[0380] The first public key determination unit is used to determine the first public key of the corresponding resource provider in the blockchain network based on the selected contract template and the broadcast message of the blockchain network.

[0381] The encryption unit is used to encrypt its own first Internet Protocol address, random number and second public key using the first public key, and then send the encrypted data to the corresponding resource provider. The second public key is the public key of the resource requester in the Internet Protocol network.

[0382] The first identity authentication unit is used to receive the random number encrypted with the second public key sent by the resource provider and to authenticate the identity of the resource provider.

[0383] Optionally, the communication unit is specifically used for:

[0384] Based on the selected contract template and the broadcast message of the blockchain network, the first public key of the corresponding resource provider in the blockchain network is determined;

[0385] A session key is generated using the first public key and a first private key that is randomly generated by itself, and then the session key is used to establish peer-to-peer communication with the corresponding resource provider.

[0386] Optionally, the session key is determined using the ephemeral-elliptic-Diffie-Hellman algorithm.

[0387] Optionally, the device further includes:

[0388] Protocol negotiation unit, used to negotiate service level agreements based on point-to-point communication with resource providers;

[0389] The protocol broadcasting unit is used to broadcast the agreed-upon service level agreement and store it in the blockchain network.

[0390] Optionally, the resource request broadcasting unit is specifically used for:

[0391] The first smart contract is triggered based on a first condition parameter array, which is a quantitative representation of the resource distribution and expected value of the resource price of the resource requester.

[0392] Optionally, the contract template selected by the second smart contract is a contract template whose approximation of the second condition parameter array and the first condition parameter array meets a preset condition, and the second condition parameter array is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template.

[0393] Optionally, the contract template may include at least one of the following:

[0394] The identifier of the resource provider;

[0395] Resources that the resource provider can offer;

[0396] The resource provider can offer the price of the resource;

[0397] The preferential policies of resource providers;

[0398] Resource providers can offer preferential prices for resources;

[0399] Punishment strategies for resource providers.

[0400] Figure 11 This is a second schematic diagram of the cross-domain network slice resource coordination device provided in the embodiments of this application, as shown below. Figure 11 As shown, the device includes at least:

[0401] The smart contract acquisition unit 1101 is used to acquire the first smart contract initiated by the resource requester through the blockchain network.

[0402] The contract template generation unit 1102 is used to generate a contract template based on the first smart contract, wherein the contract template is used to characterize the resource distribution of the resource provider;

[0403] The contract template execution unit 1103 is used to execute a contract template selected based on the second smart contract to coordinate network slice resources. The selected contract template is written into the first smart contract and stored in the blockchain network. The first smart contract and the second smart contract are smart contracts of different types.

[0404] Optionally, the contract template generation unit is specifically used for:

[0405] A contract template is generated jointly with other resource providers based on the first smart contract.

[0406] Optionally, the device further includes:

[0407] A communication unit is used to establish point-to-point communication with the resource requester.

[0408] Optionally, the device further includes:

[0409] The broadcast message receiving unit is used to receive the first Internet Protocol address, a random number, and a second public key encrypted with the first public key sent by the resource requester. The first public key is the public key of the resource provider in the blockchain network, the first Internet Protocol address is the Internet Protocol address corresponding to the resource requester, and the second public key is the public key of the resource requester in the Internet Protocol network.

[0410] A decryption unit is used to determine the first network protocol address, the random number, and the second public key after decryption.

[0411] The second authentication unit is used to send the random number encrypted with the second public key to the first Internet Protocol address to perform authentication with the resource requester.

[0412] Optionally, the communication unit is specifically used for:

[0413] The resource requester's third public key in the blockchain network is determined based on broadcast messages in the blockchain network;

[0414] A session key is generated using the third public key and a randomly generated second private key, and then the session key is used to establish peer-to-peer communication with the resource requester.

[0415] Optionally, the session key is determined using the ephemeral-elliptic-Diffie-Hellman algorithm.

[0416] Optionally, the device further includes:

[0417] Protocol negotiation unit, used to negotiate service level agreement based on point-to-point communication with the resource requester;

[0418] The protocol broadcasting unit is used to broadcast the agreed-upon service level agreement and store it in the blockchain network.

[0419] Optionally, the contract template selected by the second smart contract is a contract template whose approximation of the second condition parameter array and the first condition parameter array meets a preset condition. The second condition parameter array is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template, and the first condition parameter array is a quantitative representation of the resource distribution and expected resource price of the resource requester.

[0420] Optionally, the contract template may include at least one of the following:

[0421] The identifier of the resource provider;

[0422] Resources that the resource provider can offer;

[0423] The resource provider can offer the price of the resource;

[0424] The preferential policies of resource providers;

[0425] Resource providers can offer preferential prices for resources;

[0426] Punishment strategies for resource providers.

[0427] The methods and apparatuses provided in the various embodiments of this application are based on the same concept. Since the methods and apparatuses solve problems in similar ways, the implementations of the apparatuses and methods can refer to each other, and repeated details will not be repeated.

[0428] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0429] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to related technologies, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0430] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0431] On the other hand, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing the processor to execute the cross-domain network slice resource coordination method provided in the above embodiments, such as including:

[0432] A slice resource request message is broadcast through the blockchain network, triggering a first smart contract; a contract template for the first smart contract is obtained, the contract template being used to characterize the resource distribution of the resource provider; a contract template is selected based on a second smart contract, the selected contract template is written into the first smart contract and stored in the blockchain network, the first smart contract and the second smart contract being smart contracts of different types; cross-domain network slice resources are coordinated based on the selected contract template;

[0433] or,

[0434] The system obtains a first smart contract initiated by the resource requester through the blockchain network; generates a contract template based on the first smart contract, the contract template being used to characterize the resource distribution of the resource provider; and executes the contract template selected based on the second smart contract to coordinate network slice resources, the selected contract template being written into the first smart contract and stored in the blockchain network.

[0435] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0436] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0437] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0438] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0439] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0440] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for coordinating cross-domain network slice resources, characterized in that, include: The resource slice request message is broadcast through the blockchain network, and the first smart contract is triggered based on the first condition parameter array, which is a quantitative representation of the resource distribution and expected value of the resource price of the resource requester. Obtain the contract template that has been written into the first smart contract, or obtain the contract template generated by the resource provider based on the first smart contract. The contract template is used to characterize the resource distribution of the resource provider. Based on the second smart contract, a contract template whose approximation of the second condition parameter array and the first condition parameter array meets the preset conditions is selected. The selected contract template is written into the first smart contract and stored in the blockchain network. The first smart contract and the second smart contract are smart contracts of different types. The second condition parameter array is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template. Coordinating cross-domain network slice resources based on the selected contract template.

2. The cross-domain network slice resource coordination method according to claim 1, characterized in that, The contract template generated by the resource provider based on the first smart contract includes: Obtain contract templates generated by different resource providers for the first smart contract; or, Obtain a contract template jointly generated by multiple resource providers for the first smart contract.

3. The cross-domain network slice resource coordination method according to claim 1, characterized in that, The method further includes: Based on the selected contract template, establish point-to-point communication with the corresponding resource provider.

4. The cross-domain network slice resource coordination method according to claim 3, characterized in that, The method further includes: Based on point-to-point communication with the resource provider to negotiate the service level agreement; The agreed-upon service level agreement will be broadcast and stored on the blockchain network.

5. A method for coordinating cross-domain network slice resources, characterized in that, include: The resource requester initiates a first smart contract through the blockchain network, which is triggered by a first condition parameter array. The first condition parameter array is a quantitative representation of the resource distribution and expected value of the resource price of the resource requester. A contract template can be generated independently based on the first smart contract, or a contract template can be generated jointly based on the first smart contract and other resource providers. The contract template is used to characterize the resource distribution of the resource providers. The network slice resources are coordinated by executing the contract template selected based on the second smart contract. The selected contract template is written into the first smart contract and stored in the blockchain network. The first smart contract and the second smart contract are smart contracts of different types. The contract template selected by the second smart contract is a contract template whose approximation of the second condition parameter array and the first condition parameter array meets the preset conditions. The second condition parameter array is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template.

6. The cross-domain network slice resource coordination method according to claim 5, characterized in that, The method further includes: Establish point-to-point communication with the resource requester.

7. The cross-domain network slice resource coordination method according to claim 6, characterized in that, The method further includes: Based on point-to-point communication with the resource requester to negotiate the service level agreement; The agreed-upon service level agreement will be broadcast and stored on the blockchain network.

8. A first network functional entity, comprising a memory, a transceiver, and a processor; characterized in that: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: The resource slice request message is broadcast through the blockchain network, and the first smart contract is triggered based on the first condition parameter array, which is a quantitative representation of the resource distribution and expected value of the resource price of the resource requester. Obtain the contract template that has been written into the first smart contract, or obtain the contract template generated by the resource provider based on the first smart contract. The contract template is used to characterize the resource distribution of the resource provider. Based on the second smart contract, a contract template whose approximation of the second condition parameter array and the first condition parameter array meets the preset conditions is selected. The selected contract template is written into the first smart contract and stored in the blockchain network. The first smart contract and the second smart contract are smart contracts of different types. The second condition parameter array is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template. Coordinating cross-domain network slice resources based on the selected contract template.

9. The first network functional entity according to claim 8, characterized in that, The contract template generated by the resource provider based on the first smart contract includes: Obtain contract templates generated by different resource providers for the first smart contract; or, Obtain a contract template jointly generated by multiple resource providers for the first smart contract.

10. The first network functional entity according to claim 8, characterized in that, The processor, for reading the computer program in the memory, also performs the following operations: Based on the selected contract template, establish point-to-point communication with the corresponding resource provider.

11. The first network functional entity according to claim 10, characterized in that, The processor, for reading the computer program in the memory, also performs the following operations: Based on point-to-point communication with the resource provider to negotiate the service level agreement; The agreed-upon service level agreement will be broadcast and stored on the blockchain network.

12. A second network functional entity, comprising a memory, a transceiver, and a processor; characterized in that: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: The resource requester initiates a first smart contract through the blockchain network, which is triggered by a first condition parameter array. The first condition parameter array is a quantitative representation of the resource distribution and expected value of the resource price of the resource requester. A contract template can be generated independently based on the first smart contract, or a contract template can be generated jointly based on the first smart contract and other resource providers. The contract template is used to characterize the resource distribution of the resource providers. The network slice resources are coordinated by executing the contract template selected based on the second smart contract. The selected contract template is written into the first smart contract and stored in the blockchain network. The first smart contract and the second smart contract are smart contracts of different types. The contract template selected by the second smart contract is a contract template whose approximation of the second condition parameter array and the first condition parameter array meets the preset conditions. The second condition parameter array is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template.

13. The second network functional entity according to claim 12, characterized in that, The processor, for reading the computer program in the memory, also performs the following operations: Establish point-to-point communication with the resource requester.

14. The second network functional entity according to claim 13, characterized in that, The processor, for reading the computer program in the memory, also performs the following operations: Based on point-to-point communication with the resource requester to negotiate the service level agreement; The agreed-upon service level agreement will be broadcast and stored on the blockchain network.

15. A cross-domain network slice resource coordination device, characterized in that, include: The resource request broadcasting unit is used to broadcast slice resource request messages through the blockchain network and trigger a first smart contract based on a first condition parameter array, wherein the first condition parameter array is a quantitative representation of the resource distribution and expected value of the resource price of the resource requester. The contract template acquisition unit is used to acquire a contract template that has been written into the first smart contract, or to acquire a contract template generated by the resource provider based on the first smart contract. The contract template is used to characterize the resource distribution of the resource provider. The contract template selection unit is used to select a contract template whose approximation of the second condition parameter array and the first condition parameter array meets a preset condition based on the second smart contract, write the selected contract template into the first smart contract and store it in the blockchain network. The first smart contract and the second smart contract are smart contracts of different types. The second condition parameter array is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template. The slice resource coordination unit is used to coordinate cross-domain network slice resources based on a selected contract template.

16. A cross-domain network slice resource coordination device, characterized in that, include: The smart contract acquisition unit is used to acquire the first smart contract initiated by the resource requester through the blockchain network and triggered by the first condition parameter array, wherein the first condition parameter array is a quantitative representation of the resource distribution and the expected value of the resource price of the resource requester. The contract template generation unit generates a contract template based on the first smart contract alone, or generates a contract template jointly with other resource providers based on the first smart contract. The contract template is used to characterize the resource distribution of the resource providers. The contract template execution unit is used to execute a contract template selected based on a second smart contract to coordinate network slice resources. The selected contract template is written into the first smart contract and stored in the blockchain network. The first smart contract and the second smart contract are smart contracts of different types. The contract template selected by the second smart contract is a contract template whose approximation of the second condition parameter array and the first condition parameter array meets preset conditions. The second condition parameter array is a quantitative representation of the resource distribution and resource price of the resource provider corresponding to the contract template.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that causes a computer to perform the method according to any one of claims 1 to 4, or the method according to any one of claims 5 to 7.

Images