Link configuration method, device and equipment for network element and base station of core network

Abstract

The invention relates to a link configuration method and device for a network element of a core network and a base station, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: in response to a configuration request of a new network element of a core network, allocating an identifier and an IP address to the new network element; according to the identifier and the IP address of the new network element and a preset operator deployment mode, a new link configuration strategy between the core network and the base station is generated, and the new link configuration strategy comprises a security strategy for encrypting transmission data by applying a post-quantum cryptography scheme; uploading the new link configuration strategy to the alliance chain; and under the condition that no abnormal event exists, acquiring configuration information issued by the alliance chain based on the new link configuration strategy, and performing link configuration on the network element side and the base station side of the core network according to the configuration information. By adopting the method, the deployment efficiency, the test flexibility and the security can be improved in the process of deploying and testing the new network element of the core network.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, apparatus, computer equipment, computer-readable storage medium, and computer program product for configuring a link between a network element of a core network and a base station. Background Art

[0002] With the rapid development of 5G technology, its application scenarios are becoming increasingly diverse, and service demands are also growing. To meet the personalized network requirements of different users and services, operators need to provide differentiated services. This requires operators to be able to quickly deploy new core network element versions and conduct effective testing to ensure the stability and performance of the new versions.

[0003] However, the deployment and testing of existing core network element versions presents numerous challenges. First, deploying new NE versions requires complex configuration, including setting key parameters such as the NE identifier (ID) and IP address. This configuration not only needs to be completed on the core network NEs, but may also require corresponding adjustments at the base stations. Given the large number of base stations, modifying the configurations of multiple test base stations is a tedious and time-consuming process. The commissioning of new links requires cross-departmental collaboration between wireless and core network departments, further increasing deployment complexity and costs. Existing deployment verification processes are long and labor-intensive, severely hindering the implementation of agile deployment.

[0004] Therefore, there is an urgent need for a link configuration method, device, computer equipment, computer-readable storage medium and computer program product for the core network's network elements and base stations, which can improve deployment efficiency, testing flexibility and security during the deployment and testing of new network elements in the core network. Summary of the Invention

[0005] Based on this, it is necessary to provide a method, device, computer equipment, computer-readable storage medium and computer program product for link configuration between core network network elements and base stations, which can improve deployment efficiency, testing flexibility and security during the deployment and testing of new network elements in the core network, in order to address the above technical problems.

[0006] In a first aspect, the present application provides a method for configuring a link between a network element of a core network and a base station, comprising:

[0007] In response to a configuration request for a newly created network element of the core network, allocating an identifier and an IP address to the newly created network element;

[0008] Generate a new link configuration policy between the core network and the base station based on the identifier and IP address of the newly created network element and the preset operator deployment method, wherein the new link configuration policy includes a security policy for encrypting transmitted data using a post-quantum cryptography scheme;

[0009] If the new link configuration policy complies with the preset link upload rules of the alliance chain, uploading the new link configuration policy to the alliance chain;

[0010] Monitor the status events of the new link configuration strategy in the alliance chain to see if there are any abnormal events;

[0011] When there is no abnormal event in the status event, the configuration information issued by the alliance chain based on the new link configuration strategy is obtained, and the link configuration is performed on the network element side and the base station side of the core network respectively according to the configuration information.

[0012] In one embodiment, before responding to the configuration request of the new network element of the core network, the method further includes:

[0013] Setting an interface between a newly created network element of the core network and the server, an interface between a base station and the server, and an interface between the server and a link information system;

[0014] The authorization functions of the network element side and the base station side are set respectively, and the authorization functions include supporting access to the server through the corresponding interface, supporting receiving the new link configuration policy, and supporting link configuration of the network element side and the base station side of the core network according to the configuration information.

[0015] In one embodiment, the new link configuration policy includes the base station to be configured, base station configuration information, test deployment time, and the identifier and IP address of the newly created network element;

[0016] When the new link configuration policy complies with the preset link upload rule of the alliance chain, before uploading the new link configuration policy to the alliance chain, the method further includes:

[0017] The new link configuration strategy is uploaded to the link information system, and the smart contract in the alliance chain is used to verify whether the new link configuration strategy complies with the preset link upload rules of the alliance chain.

[0018] In one embodiment, the generating of a new link configuration policy between the core network and the base station, wherein the new link configuration policy includes a security policy for applying a post-quantum cryptography scheme to encrypt and transmit data, further includes:

[0019] When the new link configuration strategy complies with the preset link upload rule of the alliance chain, obtaining error information of not complying with the preset link upload rule of the alliance chain, and returning the error information to the new network element requester;

[0020] A new configuration request for a new network element in the core network is received again from a new network element requester, and an identifier and an IP address are allocated to the new network element in response to the new configuration request.

[0021] In one embodiment, matters for verifying whether the new link configuration strategy complies with the preset link upload rules of the alliance chain include: detecting the legitimacy of the new network element requester, verifying the format specifications of the identifier and IP address, detecting conflicts between the identifier and IP address, and checking whether the new link configuration content is compliant.

[0022] In one embodiment, the status events of the new link configuration strategy include a transaction submission event, a transaction confirmation event, and a verification pass event; wherein, the transaction submission event is triggered when the new link configuration strategy is submitted to the alliance chain; the transaction confirmation event is based on the smart contract, and is triggered when the new link configuration strategy is confirmed by the consensus mechanism of the alliance chain and written into the alliance chain; the verification pass event is based on the smart contract, and is triggered when the preset conditions of the new link configuration strategy are verified.

[0023] In a second aspect, the present application further provides a link configuration device for a core network network element and a base station, including:

[0024] an identifier and IP address allocation module, configured to allocate an identifier and an IP address to a newly created network element in response to a configuration request of a newly created network element of the core network;

[0025] A configuration policy generation module is configured to generate a new link configuration policy between the core network and the base station based on the identifier and IP address of the newly created network element and the preset operator deployment method, wherein the new link configuration policy includes a security policy for encrypting transmitted data using a post-quantum cryptography scheme;

[0026] An uplink module, configured to upload the new link configuration policy to the alliance chain if the new link configuration policy complies with the preset link upload rules of the alliance chain;

[0027] The monitoring module is used to monitor whether there are any abnormal events in the status events of the new link configuration strategy in the alliance chain;

[0028] The link configuration module is used to obtain the configuration information issued by the alliance chain based on the new link configuration strategy when there is no abnormal event in the status event, and perform link configuration on the network element side and the base station side of the core network respectively according to the configuration information.

[0029] In a third aspect, the present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0030] In response to a configuration request for a newly created network element of the core network, allocating an identifier and an IP address to the newly created network element;

[0031] Generate a new link configuration policy between the core network and the base station based on the identifier and IP address of the newly created network element and the preset operator deployment method, wherein the new link configuration policy includes a security policy for encrypting transmitted data using a post-quantum cryptography scheme;

[0032] If the new link configuration policy complies with the preset link upload rules of the alliance chain, uploading the new link configuration policy to the alliance chain;

[0033] Monitor the status events of the new link configuration strategy in the alliance chain to see if there are any abnormal events;

[0034] When there is no abnormal event in the status event, the configuration information issued by the alliance chain based on the new link configuration strategy is obtained, and the link configuration is performed on the network element side and the base station side of the core network respectively according to the configuration information.

[0035] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0036] In response to a configuration request for a newly created network element of the core network, allocating an identifier and an IP address to the newly created network element;

[0037] Generate a new link configuration policy between the core network and the base station based on the identifier and IP address of the newly created network element and the preset operator deployment method, wherein the new link configuration policy includes a security policy for encrypting transmitted data using a post-quantum cryptography scheme;

[0038] If the new link configuration policy complies with the preset link upload rules of the alliance chain, uploading the new link configuration policy to the alliance chain;

[0039] Monitor the status events of the new link configuration strategy in the alliance chain to see if there are any abnormal events;

[0040] When there is no abnormal event in the status event, the configuration information issued by the alliance chain based on the new link configuration strategy is obtained, and the link configuration is performed on the network element side and the base station side of the core network respectively according to the configuration information.

[0041] In a fifth aspect, the present application further provides a computer program product, comprising a computer program, which, when executed by a processor, implements the following steps:

[0042] In response to a configuration request for a newly created network element of the core network, allocating an identifier and an IP address to the newly created network element;

[0043] Generate a new link configuration policy between the core network and the base station based on the identifier and IP address of the newly created network element and the preset operator deployment method, wherein the new link configuration policy includes a security policy for encrypting transmitted data using a post-quantum cryptography scheme;

[0044] If the new link configuration policy complies with the preset link upload rules of the alliance chain, uploading the new link configuration policy to the alliance chain;

[0045] Monitor the status events of the new link configuration strategy in the alliance chain to see if there are any abnormal events;

[0046] When there is no abnormal event in the status event, the configuration information issued by the alliance chain based on the new link configuration strategy is obtained, and the link configuration is performed on the network element side and the base station side of the core network respectively according to the configuration information.

[0047] The aforementioned method, apparatus, computer device, computer-readable storage medium, and computer program product for configuring links between core network elements and base stations significantly improve the efficiency, flexibility, and security of core network element and base station link configuration by automatically allocating ID / IP addresses, generating new link configuration policies, and uploading them to the consortium chain. This significantly reduces labor costs. Automated configuration reduces manual operations, simplifies the link configuration process, significantly shortens deployment time, and enables agile deployment. Leveraging the distributed nature of the consortium chain, configuration policies can be quickly adjusted, enabling a wider testing scope and comprehensive verification of user needs, increasing testing flexibility. The consortium chain's immutability and permission management ensures the security of configuration policies and data privacy, enhancing system security. Real-time monitoring and distributed verification mechanisms ensure the correct execution of configuration policies, improving system stability and reliability. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following briefly introduces the drawings required for use in the embodiments of the present application or related technical descriptions. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying any creative work.

[0049] Figure 1 This is an application scenario diagram of a link configuration method between a core network element and a base station in one embodiment;

[0050] Figure 2 1 is a flow chart of a method for configuring a link between a network element of a core network and a base station in one embodiment;

[0051] Figure 31 is a flow chart of a method for configuring a link between a network element of a core network and a base station in another embodiment;

[0052] Figure 4 is a structural block diagram of a link configuration device between a network element of a core network and a base station in one embodiment;

[0053] Figure 5 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0055] It should be noted that the terms "first", "second", etc. used in this application may be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "including" and "having" used in this application and any variations thereof are intended to cover non-exclusive inclusions. The term "plurality" used in this application refers to two or more. The term "and / or" used in this application refers to one of the solutions or any combination of multiple solutions.

[0056] like Figure 1 As shown, the newly created network element in this application can directly access the (ID / IP allocation and link dynamic orchestration policy) server through the interface to request relevant configurations. The server can directly transmit the new link configuration policy to the network function entity and base station through the interface. The server uploads the new link configuration policy to the (network element ID / IP and) link information system based on the alliance chain and supports monitoring feedback information from the link information system based on the alliance chain. The link information system supports receiving new link configuration policies from the server, verifying them, and then uploading them to the chain, and supports feedback of verification results to the server.

[0057] In an exemplary embodiment, Figure 2 As shown, a method for configuring a link between a core network element and a base station is provided, and the method is applied to Figure 1 The server in the example is used to illustrate the method, which includes the following steps S202 to S210.

[0058] Step S202: In response to the configuration request of the newly-built network element of the core network, an identifier and an IP address are allocated to the newly-built network element.

[0059] Specifically, in the 5G network architecture, core network elements (such as the AMF, SMF, and UPF) are core components of the network, responsible for handling core network functions such as user access management, session management, and data forwarding. A new network element (NE) is a newly added NE instance in the network used to expand network capacity or introduce new functionality. When a new NE is needed, the requester sends a configuration request to the system. This request includes basic NE information (such as NE type and functional requirements) as well as configuration requirements (such as allocating an ID and IP address).

[0060] Assigning an identifier (ID) and IP address: An identifier (ID) is a code that uniquely identifies a network element, while an IP address is required for network elements to communicate within the network. These assignments are a prerequisite for network elements to properly access the network and communicate with other network elements.

[0061] More specifically, a newly created network element (such as an AMF or SMF) sends a configuration request to the ID / IP allocation and dynamic link orchestration policy server through a predefined interface. The request includes: the network element type (such as AMF, SMF), deployment requirements (such as the region and functional requirements), and other necessary information, such as testing requirements and expected link connectivity.

[0062] Upon receiving a configuration request for a new NE, the ID / IP allocation and link dynamic orchestration policy server initiates the configuration process. Using AI technology (e.g., graph neural networks (GNNs)), the server dynamically generates IDs and IP addresses suitable for the new NE, taking into account the current network topology. GNNs analyze the network topology to ensure that the assigned IDs and IP addresses are compatible with the existing network structure, avoiding conflicts.

[0063] Step S204: Generate a new link configuration strategy between the core network and the base station based on the identifier, IP address, and preset operator deployment method of the newly created network element. The new link configuration strategy includes a security strategy for encrypting and transmitting data using a post-quantum cryptography scheme.

[0064] The default operator deployment method is a deployment strategy predefined by the operator based on service requirements, network topology, and test scope. It includes, but is not limited to, the selection of test base stations; the number of links required; the link connection method (e.g., control plane links, user plane links); and the test user's characteristic requirements (e.g., bandwidth, latency, QoS, etc.). The new link configuration strategy refers to a specific configuration plan generated based on this information, which is used to guide the link connection and configuration between core network elements and base stations.

[0065] Specifically, based on service requirements and network topology, select appropriate base stations as test targets. Determine the number of links required and the specific connection method for each link (e.g., control plane link, user plane link, etc.). Based on service requirements, determine the characteristics that the test users must meet (e.g., bandwidth, latency, QoS, etc.).

[0066] The server combines the ID and IP address of the newly created network element and the analyzed operator deployment intention to generate a new link configuration policy between the core network and the base station. The server automatically submits the generated new link configuration policy to the network element ID / IP and link information system based on the alliance chain. The new link configuration policy specifically includes:

[0067] Base station configuration content: Base station configuration parameters that need to be modified, such as IP address, port number, routing information, etc.

[0068] Link connection information: The connection information between the newly created network element and the base station, including the link's starting point, end point, bandwidth, latency, and other parameters.

[0069] Test user selection: Select test users from a wider range to ensure diversity and comprehensiveness of the test.

[0070] Security strategy: Apply post-quantum cryptography schemes (such as CRYSTALS-Kyber) to encrypt and transmit configuration content to ensure data security.

[0071] Step S206: If the new link configuration policy complies with the preset link upload rule of the alliance chain, the new link configuration policy is uploaded to the alliance chain.

[0072] Specifically, before submitting a configuration policy to the consortium chain, the server first checks whether the configuration policy complies with the consortium chain's preset link upload rules. The consortium chain's preset link upload rules refer to a series of rules set by the consortium chain system to ensure the compliance, security, and consistency of on-chain data. These rules define which configuration policies can be accepted and uploaded to the consortium chain. Compliance with the rules means that the new link configuration policy has passed a series of verifications of the consortium chain system, including but not limited to the following aspects:

[0073] Legality verification: Verify whether the requester who submits the configuration policy has legal authority.

[0074] Format verification: Checks whether information such as identifiers and IP addresses in the configuration policy conforms to the preset format specifications.

[0075] Conflict detection: Ensures that newly assigned identifiers and IP addresses do not conflict with existing configurations on the chain.

[0076] Compliance verification: Verify whether the content of the configuration policy meets the operator's deployment intentions and business requirements.

[0077] If the verification passes, the server submits the new link configuration policy to the consortium chain-based network element ID / IP and link information system. The smart contract within the consortium chain automatically performs further verification on the submitted configuration information, automatically executing pre-set verification rules to ensure the compliance and consistency of the configuration information. The smart contract checks whether the new configuration conflicts with existing configurations on the chain. The smart contract verifies the legitimacy of the submitter, ensuring that only authorized nodes can submit configuration information. If the smart contract verification passes, the configuration information is recorded on the consortium chain and an event is triggered to notify the server. After the server monitors the feedback event from the consortium chain, it confirms that the configuration information has been successfully uploaded to the chain.

[0078] If the verification fails, the smart contract will refuse to upload to the chain and return an error message to the server, which will then feed back the error message to the party requesting the new network element.

[0079] Step S208: monitor whether there are any abnormal events in the status events of the new link configuration policy in the alliance chain.

[0080] Specifically, the ID / IP allocation and link dynamic orchestration policy server deploys a monitoring mechanism to monitor the status events on the alliance chain in real time. The monitoring content includes:

[0081] Verification passed event: indicates that the configuration information has been successfully uploaded to the chain and the subsequent configuration distribution operation can continue.

[0082] Verification failure event: indicates that there is a problem with the configuration information and it needs to be adjusted or regenerated.

[0083] Other abnormal events: such as data conflicts, illegal chain uploads (insufficient permissions), etc. These events may affect the correct execution of the configuration strategy.

[0084] When a status event is detected, the server analyzes it. If it's a "verification passed event," the server confirms that the configuration information has been successfully uploaded to the blockchain and can proceed to the next step (such as distributing the configuration policy to the network element and base station). If it's a "verification failed event," the server records the error and feeds it back to the newly created network element (the requester) for adjustments. If it's another abnormal event, the server records the event details and handles it according to pre-set rules (such as triggering an alarm, logging, or resubmitting the request).

[0085] Step S210: When there are no abnormal events in the status events, obtain the configuration information issued by the alliance chain based on the new link configuration strategy, and perform link configuration on the network element side and the base station side of the core network respectively according to the configuration information.

[0086] Specifically, after confirming that there are no abnormal events in the status events, the server obtains the configuration information issued based on the new link configuration policy from the consortium chain. This configuration information includes: the ID and IP address of the newly created network element; the link connection information between the core network element and the base station (such as the link's starting point, end point, bandwidth, and latency); and the selection and configuration modification details of the test base station (such as the IP address, port number, and routing information). The server then distributes this configuration information to the core network network element and base station.

[0087] The content sent includes: On the core network element side: the ID and IP address of the newly created element, as well as the link connection information between it and the base station. On the base station side: configuration parameters that need to be modified, such as the IP address, port number, and routing information, to ensure that the base station can correctly connect to the newly created element.

[0088] The core network's network elements (NEs) update their network parameters based on the delivered configuration information to ensure a correct link connection with the base station. The base station also modifies its own network parameters based on the delivered configuration information to ensure a correct link connection with the core network's NEs. After the configuration is complete, the core network's NEs and base stations can communicate normally, ensuring a correct link connection.

[0089] The aforementioned link configuration method for core network elements and base stations significantly improves the efficiency, flexibility, and security of core network element and base station link configuration by automating the allocation of ID / IP addresses, generating new link configuration policies, and uploading them to the consortium chain. This significantly reduces labor costs. Automated configuration reduces manual operations, simplifies the link configuration process, significantly shortens deployment time, and enables agile deployment. Leveraging the distributed nature of the consortium chain, configuration policies can be quickly adjusted, enabling a wider testing scope and comprehensive verification of user needs, increasing testing flexibility. The consortium chain's immutability and permission management ensures the security of configuration policies and data privacy, enhancing system security. Real-time monitoring and distributed verification mechanisms ensure the correct execution of configuration policies, improving system stability and reliability.

[0090] In an exemplary embodiment, Figure 3 As shown, before responding to the configuration request of the new network element of the core network, the following is also included:

[0091] Step S302: Setting the interface between the newly created network element of the core network and the server, the interface between the base station and the server, and the interface between the server and the link information system;

[0092] Step S304, setting the respective authorization functions of the network element side and the base station side. The authorization functions include supporting access to the server through the corresponding interface, supporting receiving new link configuration policies, and supporting link configuration of the network element side and the base station side of the core network according to the configuration information.

[0093] Specifically, for the interface between the new NE and the server, a standardized communication protocol (such as HTTP / HTTPS or gRPC) should be defined for communication between the new NE and the ID / IP allocation and link dynamic orchestration policy server. This ensures that the new NE can send configuration requests and receive responses from the server through this interface.

[0094] Interface between base stations and servers: This defines a standardized communication protocol for communication between base stations and the ID / IP allocation and link dynamic orchestration policy server. This ensures that base stations can receive configuration information from the server and provide status feedback through this interface.

[0095] Interface between the server and the link information system: Defines a standardized communication protocol for communication between the ID / IP allocation and link dynamic orchestration policy server and the network element ID / IP and link information system based on the consortium chain. Ensure that the server can submit configuration information to the consortium chain through this interface and receive feedback from the consortium chain.

[0096] Permitted functions on the NE side: Accessing the server: New NEs must be configured with corresponding network parameters (such as IP address and port number) to ensure they can access the server through their interfaces. Receiving configuration policies: New NEs must support receiving new link configuration policies issued by the server, including ID / IP address and link connection information. Link configuration: New NEs must support automatically completing their own link configuration based on the received configuration information, such as modifying network parameters and establishing communication links.

[0097] Permissioned functions on the base station side: Accessing the server: The base station needs to configure the corresponding network parameters to ensure that it can access the server through the interface. Receiving configuration policies: The base station needs to support receiving new link configuration policies issued by the server, including configuration parameters that need to be modified (such as IP address, port number, routing information, etc.). Link configuration: The base station needs to support automatically completing its own link configuration based on the received configuration information, such as modifying network parameters and establishing communication links.

[0098] In this embodiment, standardized interfaces are set up to ensure smooth communication between newly built network elements, base stations, and servers, preventing system failures caused by interface incompatibility. Permission functions are set up to ensure that network elements and base stations can automatically complete link configuration based on configuration information, supporting flexible system expansion and dynamic adjustment. The interface and permission functions ensure that only authorized system components can access the server and receive configuration information, reducing security risks. Automated configuration and link orchestration reduce manual intervention, improve deployment efficiency, and shorten deployment cycles.

[0099] In an exemplary embodiment, the new link configuration policy includes the base station to be configured, base station configuration information, test deployment time, and the identifier and IP address of the newly created network element;

[0100] When the new link configuration policy complies with the preset link upload rules of the consortium chain, before uploading the new link configuration policy to the consortium chain, the following steps are also required:

[0101] Upload the new link configuration strategy to the link information system, and use the smart contract in the alliance chain to verify whether the new link configuration strategy complies with the preset link upload rules of the alliance chain.

[0102] Specifically, smart contracts are automated programs deployed on the consortium blockchain that automatically perform verification operations based on pre-set rules. Smart contracts perform the following verifications on new link configuration policies:

[0103] Format specification: Check whether the format of the configuration policy meets the requirements of the alliance chain.

[0104] Submitter legitimacy: Verify whether the server submitting the configuration policy has legal authority.

[0105] Conflict detection: Checks whether the newly assigned ID and IP address conflict with the existing configuration.

[0106] Compliance verification: Ensures that the configuration content meets the operator's deployment intentions and business requirements.

[0107] Time validity: Verify whether the test deployment time is reasonable and ensure that the configuration policy takes effect at the correct time.

[0108] If the smart contract verification passes, it indicates that the new link configuration policy complies with the consortium chain's pre-set link upload rules, and you can proceed to the next step (uploading the configuration policy to the consortium chain). If the smart contract verification fails, an error message will be returned, indicating the problem with the configuration policy. In this case, the configuration policy needs to be adjusted until verification passes.

[0109] In this embodiment, automated verification via smart contracts ensures that all configuration policies uploaded to the consortium chain comply with pre-set rules, preventing human error and illegal operations. Leveraging the consortium chain's immutability and transparency, the security and traceability of configuration information are ensured, mitigating security risks. Automated verification mechanisms ensure the correct execution of configuration policies, reducing system failures caused by configuration errors. By sharing configuration data via the consortium chain, wireless departments, core network departments, and operations and maintenance teams can access consistent configuration information in real time, reducing the complexity and time costs of cross-departmental collaboration.

[0110] In an exemplary embodiment, a new link configuration policy is generated between a core network and a base station. The new link configuration policy includes a security policy for applying a post-quantum cryptography scheme to encrypt transmitted data and further includes:

[0111] When the new link configuration strategy complies with the preset link upload rule of the alliance chain, an error message of not complying with the preset link upload rule of the alliance chain is obtained, and the error message is returned to the new network element requester;

[0112] A new configuration request for a new network element in the core network is received again from a new network element requester, and an identifier and an IP address are allocated to the new network element in response to the new configuration request.

[0113] The error information refers to the information containing the specific error cause generated by the system when the new link configuration policy does not comply with the preset link upload rules.

[0114] Specifically, if the smart contract fails verification, it indicates that the new link configuration policy does not comply with the preset rules. In this case, the smart contract generates an error message, indicating the specific non-compliance. The server retrieves the error message returned by the smart contract from the consortium chain. The server returns the error message to the requester of the new network element, informing them of the specific reasons why the configuration policy does not comply with the rules.

[0115] Based on the returned error information, the requester adjusts the configuration request and corrects any non-compliant parts. The requester then resubmits a new configuration request to the ID / IP allocation and link dynamic orchestration policy server. Upon receiving the new configuration request, the server reassigns an identifier (ID) and IP address to the newly created network element. Based on the new configuration request, the server regenerates a new link configuration policy and submits it to the consortium chain for verification.

[0116] In this embodiment, automatic verification by smart contracts ensures that all configuration policies uploaded to the consortium chain comply with preset rules, preventing system failures caused by configuration errors. New network element requesters are allowed to adjust configuration requests based on error information and resubmit them, ensuring the system can flexibly respond to configuration errors. This automated verification mechanism ensures the correct execution of configuration policies and reduces system failures caused by configuration errors.

[0117] In an exemplary embodiment, matters for verifying whether the new link configuration strategy complies with the preset link upload rules of the alliance chain include: detecting the legitimacy of the new network element requester, verifying the format specifications of the identifier and IP address, detecting conflicts between the identifier and IP address, and checking whether the new link configuration content is compliant.

[0118] Specifically, the legitimacy of the requester for new network elements is checked to ensure that only authorized entities can submit configuration policies, preventing unauthorized operations. This is achieved by verifying the identity information (such as digital certificates and signatures) of the requester for new network elements. The requester is checked to see if it is in the authorized list. The requester is also confirmed to have permission to perform configuration operations.

[0119] Verify the format specifications of identifiers and IP addresses to ensure they conform to pre-set format requirements and avoid configuration failures due to format errors. Implementation: Verify that the identifier (ID) conforms to the pre-set format (such as length and character type). Verify that the IP address conforms to the standard IP address format (such as IPv4 or IPv6). Check that the IP address is within a pre-set range (such as a specific IP segment).

[0120] Conflict detection for identifiers and IP addresses is performed to ensure that newly assigned identifiers and IP addresses do not conflict with existing configurations, thus avoiding address conflicts within the network. Implementation: Check whether the newly assigned identifier already exists in the consortium chain's records. Check whether the newly assigned IP address has already been assigned to other network elements or base stations. Ensure that the newly assigned IP address does not conflict with any existing IP addresses in the network.

[0121] Checking the compliance of new link configurations ensures they meet the operator's deployment intent and business requirements, preventing system failures caused by configuration errors. Implementation: Verify that the configuration complies with pre-set business rules (such as number of links, bandwidth, and latency). Check that the configuration is compatible with the existing network topology. Confirm that the configuration meets the test deployment timeline.

[0122] In this embodiment, a strict verification mechanism ensures that all configuration policies uploaded to the consortium chain comply with pre-set rules, preventing system failures caused by configuration errors. By verifying the legitimacy of the party requesting the creation of a new network element, only authorized entities can submit configuration policies, preventing illegal operations. An automated verification mechanism ensures the correct execution of configuration policies, reducing system failures caused by configuration errors.

[0123] In an exemplary embodiment, the status events of the new link configuration policy include a transaction submission event, a transaction confirmation event, and a verification pass event; wherein, the transaction submission event is triggered when the new link configuration policy is submitted to the alliance chain; the transaction confirmation event is based on a smart contract and is triggered when the new link configuration policy is confirmed by the consensus mechanism of the alliance chain and written into the alliance chain; the verification pass event is based on a smart contract and is triggered when the preset conditions of the new link configuration policy are verified.

[0124] Specifically, a transaction submission event is triggered when a new link configuration policy is submitted to the consortium chain. Triggering conditions: The new link configuration policy is generated and submitted to the consortium chain by the ID / IP allocation and link dynamic orchestration policy server. The server sends the configuration policy to the consortium chain's smart contract.

[0125] Purpose: Notifies the system that the configuration policy has been submitted but not yet confirmed. Triggers the subsequent verification and confirmation process.

[0126] A transaction confirmation event occurs when a new link configuration policy is confirmed by the consortium chain's consensus mechanism and written to the consortium chain. Triggering conditions: The smart contract receives the submitted configuration policy. The consortium chain's consensus mechanism (such as PBFT or Raft) verifies and confirms the configuration policy. The configuration policy is successfully written to the consortium chain.

[0127] Function: Notify the system that the configuration policy has been confirmed and recorded on the chain. Ensure the configuration policy is tamper-proof and consistent.

[0128] A verification pass event is triggered when the pre-defined conditions of a new link configuration policy are verified. Triggering condition: The smart contract verifies the submitted configuration policy. Verification includes legality checks, format verification, conflict detection, and compliance checks. The configuration policy passes all pre-defined conditions.

[0129] Purpose: Notifies the system that the configuration policy has passed verification and that subsequent operations can proceed. Ensures the correctness and consistency of the configuration policy.

[0130] In this embodiment, through status events, the system can monitor the submission, confirmation, and verification of new link configuration policies in real time to ensure their correct execution. Smart contracts and consensus mechanisms ensure a secure and reliable verification and validation process for configuration policies, preventing illegal operations. Through the triggering mechanism of status events, the system can promptly detect and address anomalies, reducing system failures caused by configuration errors.

[0131] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0132] Based on the same inventive concept, an embodiment of the present application further provides a core network network element and base station link configuration device for implementing the above-mentioned core network network element and base station link configuration method. The implementation solution provided by the device is similar to the implementation solution described in the above-mentioned method. Therefore, the specific limitations of the embodiments of one or more core network network element and base station link configuration devices provided below can be found in the above-mentioned limitations of the core network network element and base station link configuration method, and will not be repeated here.

[0133] In an exemplary embodiment, Figure 4 As shown, a link configuration device for a network element of a core network and a base station is provided, comprising:

[0134] An identifier and IP address allocation module 402 is configured to allocate an identifier and an IP address to a newly created network element in response to a configuration request of a newly created network element in the core network;

[0135] A configuration policy generation module 404 is configured to generate a new link configuration policy between the core network and the base station based on the identifier and IP address of the newly created network element and the preset operator deployment method. The new link configuration policy includes a security policy for encrypting transmitted data using a post-quantum cryptography scheme.

[0136] The uplink module 406 is used to upload the new link configuration policy to the alliance chain if the new link configuration policy complies with the preset link upload rules of the alliance chain;

[0137] The monitoring module 408 is used to monitor whether there are abnormal events in the status events of the new link configuration policy in the alliance chain;

[0138] The link configuration module 410 is used to obtain the configuration information issued by the alliance chain based on the new link configuration strategy when there are no abnormal events in the status events, and perform link configuration on the network element side and the base station side of the core network according to the configuration information.

[0139] In an exemplary embodiment, the setting module is configured to set an interface between a newly created network element of the core network and a server, an interface between a base station and a server, and an interface between a server and a link information system;

[0140] Set the respective permission functions of the network element side and the base station side. The permission functions include supporting access to the server through the corresponding interface, supporting receiving new link configuration policies, and supporting link configuration on the network element side and the base station side of the core network according to the configuration information.

[0141] In an exemplary embodiment, the new link configuration strategy includes the base station to be configured, base station configuration information, test deployment time, and the identifier and IP address of the newly created network element; the verification module is used to upload the new link configuration strategy to the link information system, and use the smart contract in the alliance chain to verify whether the new link configuration strategy complies with the preset link upload rules of the alliance chain.

[0142] In an exemplary embodiment, the identifier and IP address allocation module 402 is used to obtain error information that does not comply with the preset link upload rules of the alliance chain when the new link configuration strategy complies with the preset link upload rules of the alliance chain, and return the error information to the new network element requester; re-receive the new configuration request for the new network element of the core network sent by the new network element requester, and allocate an identifier and IP address to the new network element in response to the new configuration request.

[0143] In an exemplary embodiment, matters for verifying whether the new link configuration strategy complies with the preset link upload rules of the alliance chain include: detecting the legitimacy of the new network element requester, verifying the format specifications of the identifier and IP address, detecting conflicts between the identifier and IP address, and checking whether the new link configuration content is compliant.

[0144] In an exemplary embodiment, the status events of the new link configuration policy include a transaction submission event, a transaction confirmation event, and a verification pass event; wherein, the transaction submission event is triggered when the new link configuration policy is submitted to the alliance chain; the transaction confirmation event is based on a smart contract and is triggered when the new link configuration policy is confirmed by the consensus mechanism of the alliance chain and written into the alliance chain; the verification pass event is based on a smart contract and is triggered when the preset conditions of the new link configuration policy are verified.

[0145] Each module in the aforementioned apparatus for configuring links between a core network element and a base station may be implemented in whole or in part through software, hardware, or a combination thereof. Each module may be embedded in or independent of a processor in a computer device in the form of hardware, or may be stored in a memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each module.

[0146] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 5 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O) and a communication interface. The processor, memory and input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store new link configuration policy data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a link configuration method for a network element and a base station of a core network is implemented.

[0147] Those skilled in the art will understand that Figure 5 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0148] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0149] In response to a configuration request for a newly created network element of the core network, allocating an identifier and an IP address to the newly created network element;

[0150] Generate a new link configuration policy between the core network and the base station based on the identifier and IP address of the newly created network element and the pre-set operator deployment method. The new link configuration policy includes a security policy that uses a post-quantum cryptography scheme to encrypt transmitted data.

[0151] If the new link configuration policy complies with the preset link upload rules of the alliance chain, the new link configuration policy is uploaded to the alliance chain;

[0152] Monitor the status events of the new link configuration strategy in the alliance chain to see if there are any abnormal events;

[0153] In the absence of abnormal events in the status events, the configuration information issued by the alliance chain based on the new link configuration strategy is obtained, and the links are configured on the network element side and the base station side of the core network respectively according to the configuration information.

[0154] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0155] Set up interfaces between newly built network elements of the core network and servers, interfaces between base stations and servers, and interfaces between servers and link information systems;

[0156] Set the respective permission functions of the network element side and the base station side. The permission functions include supporting access to the server through the corresponding interface, supporting receiving new link configuration policies, and supporting link configuration on the network element side and the base station side of the core network according to the configuration information.

[0157] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0158] The new link configuration policy includes the base station to be configured, base station configuration information, test deployment time, and the identifier and IP address of the new network element;

[0159] Upload the new link configuration strategy to the link information system, and use the smart contract in the alliance chain to verify whether the new link configuration strategy complies with the preset link upload rules of the alliance chain.

[0160] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0161] When the new link configuration strategy complies with the preset link upload rule of the alliance chain, an error message of not complying with the preset link upload rule of the alliance chain is obtained, and the error message is returned to the new network element requester;

[0162] A new configuration request for a new network element in the core network is received again from a new network element requester, and an identifier and an IP address are allocated to the new network element in response to the new configuration request.

[0163] In one embodiment, matters for verifying whether the new link configuration strategy complies with the preset link upload rules of the alliance chain include: detecting the legitimacy of the new network element requester, verifying the format specifications of the identifier and IP address, detecting conflicts between the identifier and IP address, and checking whether the new link configuration content is compliant.

[0164] In one embodiment, the status events of the new link configuration policy include a transaction submission event, a transaction confirmation event, and a verification pass event; among which, the transaction submission event is triggered when the new link configuration policy is submitted to the alliance chain; the transaction confirmation event is based on a smart contract and is triggered when the new link configuration policy is confirmed by the consensus mechanism of the alliance chain and written into the alliance chain; the verification pass event is based on a smart contract and is triggered when the preset conditions of the new link configuration policy are verified.

[0165] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0166] In response to a configuration request for a newly created network element of the core network, allocating an identifier and an IP address to the newly created network element;

[0167] Generate a new link configuration policy between the core network and the base station based on the identifier and IP address of the newly created network element and the pre-set operator deployment method. The new link configuration policy includes a security policy that uses a post-quantum cryptography scheme to encrypt transmitted data.

[0168] If the new link configuration policy complies with the preset link upload rules of the alliance chain, the new link configuration policy is uploaded to the alliance chain;

[0169] Monitor the status events of the new link configuration strategy in the alliance chain to see if there are any abnormal events;

[0170] In the absence of abnormal events in the status events, the configuration information issued by the alliance chain based on the new link configuration strategy is obtained, and the links are configured on the network element side and the base station side of the core network respectively according to the configuration information.

[0171] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0172] Set up interfaces between newly built network elements of the core network and servers, interfaces between base stations and servers, and interfaces between servers and link information systems;

[0173] Set the respective permission functions of the network element side and the base station side. The permission functions include supporting access to the server through the corresponding interface, supporting receiving new link configuration policies, and supporting link configuration on the network element side and the base station side of the core network according to the configuration information.

[0174] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0175] The new link configuration policy includes the base station to be configured, base station configuration information, test deployment time, and the identifier and IP address of the new network element;

[0176] Upload the new link configuration strategy to the link information system, and use the smart contract in the alliance chain to verify whether the new link configuration strategy complies with the preset link upload rules of the alliance chain.

[0177] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0178] When the new link configuration strategy complies with the preset link upload rule of the alliance chain, an error message of not complying with the preset link upload rule of the alliance chain is obtained, and the error message is returned to the new network element requester;

[0179] A new configuration request for a new network element in the core network is received again from a new network element requester, and an identifier and an IP address are allocated to the new network element in response to the new configuration request.

[0180] In one embodiment, matters for verifying whether the new link configuration strategy complies with the preset link upload rules of the alliance chain include: detecting the legitimacy of the new network element requester, verifying the format specifications of the identifier and IP address, detecting conflicts between the identifier and IP address, and checking whether the new link configuration content is compliant.

[0181] In one embodiment, the status events of the new link configuration policy include a transaction submission event, a transaction confirmation event, and a verification pass event; among which, the transaction submission event is triggered when the new link configuration policy is submitted to the alliance chain; the transaction confirmation event is based on a smart contract and is triggered when the new link configuration policy is confirmed by the consensus mechanism of the alliance chain and written into the alliance chain; the verification pass event is based on a smart contract and is triggered when the preset conditions of the new link configuration policy are verified.

[0182] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0183] In response to a configuration request for a newly created network element of the core network, allocating an identifier and an IP address to the newly created network element;

[0184] Generate a new link configuration policy between the core network and the base station based on the identifier and IP address of the newly created network element and the pre-set operator deployment method. The new link configuration policy includes a security policy that uses a post-quantum cryptography scheme to encrypt transmitted data.

[0185] If the new link configuration policy complies with the preset link upload rules of the alliance chain, the new link configuration policy is uploaded to the alliance chain;

[0186] Monitor the status events of the new link configuration strategy in the alliance chain to see if there are any abnormal events;

[0187] In the absence of abnormal events in the status events, the configuration information issued by the alliance chain based on the new link configuration strategy is obtained, and the links are configured on the network element side and the base station side of the core network respectively according to the configuration information.

[0188] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0189] Set up interfaces between newly built network elements of the core network and servers, interfaces between base stations and servers, and interfaces between servers and link information systems;

[0190] Set the respective permission functions of the network element side and the base station side. The permission functions include supporting access to the server through the corresponding interface, supporting receiving new link configuration policies, and supporting link configuration on the network element side and the base station side of the core network according to the configuration information.

[0191] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0192] The new link configuration policy includes the base station to be configured, base station configuration information, test deployment time, and the identifier and IP address of the new network element;

[0193] Upload the new link configuration strategy to the link information system, and use the smart contract in the alliance chain to verify whether the new link configuration strategy complies with the preset link upload rules of the alliance chain.

[0194] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0195] When the new link configuration strategy complies with the preset link upload rule of the alliance chain, an error message of not complying with the preset link upload rule of the alliance chain is obtained, and the error message is returned to the new network element requester;

[0196] A new configuration request for a new network element in the core network is received again from a new network element requester, and an identifier and an IP address are allocated to the new network element in response to the new configuration request.

[0197] In one embodiment, matters for verifying whether the new link configuration strategy complies with the preset link upload rules of the alliance chain include: detecting the legitimacy of the new network element requester, verifying the format specifications of the identifier and IP address, detecting conflicts between the identifier and IP address, and checking whether the new link configuration content is compliant.

[0198] In one embodiment, the status events of the new link configuration policy include a transaction submission event, a transaction confirmation event, and a verification pass event; among which, the transaction submission event is triggered when the new link configuration policy is submitted to the alliance chain; the transaction confirmation event is based on a smart contract and is triggered when the new link configuration policy is confirmed by the consensus mechanism of the alliance chain and written into the alliance chain; the verification pass event is based on a smart contract and is triggered when the preset conditions of the new link configuration policy are verified.

[0199] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0200] Those skilled in the art will understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. In particular, any reference to memory, database, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the various embodiments provided herein may be, but are not limited to, general-purpose processors, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), programmable logic devices (PLDs), quantum computing-based data processing logic devices, artificial intelligence (AI) processors, and the like.

[0201] The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0202] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A method for configuring a link between a network element of a core network and a base station, characterized in that: Applied to a server, the method includes: In response to a configuration request for a newly created network element of the core network, allocating an identifier and an IP address to the newly created network element; Generate a new link configuration policy between the core network and the base station based on the identifier and IP address of the newly created network element and the preset operator deployment method, wherein the new link configuration policy includes a security policy for encrypting transmitted data using a post-quantum cryptography scheme; If the new link configuration policy complies with the preset link upload rules of the alliance chain, uploading the new link configuration policy to the alliance chain; Monitor the status events of the new link configuration strategy in the alliance chain to see if there are any abnormal events; When there is no abnormal event in the status event, the configuration information issued by the alliance chain based on the new link configuration strategy is obtained, and the link configuration is performed on the network element side and the base station side of the core network respectively according to the configuration information.

2. The method according to claim 1, characterized in that Before responding to the configuration request of the new network element of the core network, the method further includes: Setting an interface between a newly created network element of the core network and the server, an interface between a base station and the server, and an interface between the server and a link information system; The authorization functions of the network element side and the base station side are set respectively, and the authorization functions include supporting access to the server through the corresponding interface, supporting receiving the new link configuration policy, and supporting link configuration of the network element side and the base station side of the core network according to the configuration information.

3. The method according to claim 2, characterized in that The new link configuration strategy includes the base station to be configured, base station configuration information, test deployment time, and the identifier and IP address of the newly-built network element; When the new link configuration policy complies with the preset link upload rule of the alliance chain, before uploading the new link configuration policy to the alliance chain, the method further includes: The new link configuration strategy is uploaded to the link information system, and the smart contract in the alliance chain is used to verify whether the new link configuration strategy complies with the preset link upload rules of the alliance chain.

4. The method according to claim 1, wherein The generating of a new link configuration strategy between the core network and the base station, wherein the new link configuration strategy includes a security strategy for encrypting and transmitting data using a post-quantum cryptography scheme, further includes: When the new link configuration strategy complies with the preset link upload rule of the alliance chain, obtaining error information of not complying with the preset link upload rule of the alliance chain, and returning the error information to the new network element requester; A new configuration request for a new network element in the core network is received again from a new network element requester, and an identifier and an IP address are allocated to the new network element in response to the new configuration request.

5. The method according to claim 1, characterized in that Matters for verifying whether the new link configuration strategy complies with the preset link upload rules of the alliance chain include: detecting the legitimacy of the new network element requester, verifying the format specifications of the identifier and IP address, detecting conflicts between the identifier and IP address, and checking whether the new link configuration content is compliant.

6. The method according to claim 3, characterized in that The status events of the new link configuration strategy include transaction submission events, transaction confirmation events, and verification pass events; among which, the transaction submission event is triggered when the new link configuration strategy is submitted to the alliance chain; the transaction confirmation event is based on the smart contract and is triggered when the new link configuration strategy is confirmed by the consensus mechanism of the alliance chain and written into the alliance chain; the verification pass event is based on the smart contract and is triggered when the preset conditions of the new link configuration strategy are verified.

7. A link configuration device for a core network element and a base station, characterized in that: The device comprises: an identifier and IP address allocation module, configured to allocate an identifier and an IP address to a newly created network element in response to a configuration request of a newly created network element of the core network; A configuration policy generation module is configured to generate a new link configuration policy between the core network and the base station based on the identifier and IP address of the newly created network element and the preset operator deployment method, wherein the new link configuration policy includes a security policy for encrypting transmitted data using a post-quantum cryptography scheme; An uplink module, configured to upload the new link configuration policy to the alliance chain if the new link configuration policy complies with the preset link upload rules of the alliance chain; The monitoring module is used to monitor whether there are any abnormal events in the status events of the new link configuration strategy in the alliance chain; The link configuration module is used to obtain the configuration information issued by the alliance chain based on the new link configuration strategy when there is no abnormal event in the status event, and perform link configuration on the network element side and the base station side of the core network respectively according to the configuration information.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images