5G public network and power enterprise collaborative management and control method

Abstract

The invention belongs to the technical field of 5G public network and power enterprise collaborative management and control, and particularly relates to a 5G public network and power enterprise collaborative management and control method. Comprising the following steps: S1, a power enterprise submits a registration application through a capability open platform of a 5G public network operator, and the registration application is legally called after being published by a power management and control platform; s2, the power management and control platform performs two-factor authentication operation on the API caller; s3, the API charging process charges the API caller according to the agreed multi-dimensional dynamic charging rule; and S4, the power management and control platform receives an API access request from the power service system, obtains and applies an access control strategy in combination with the current network slice load rate, the charging level label and the historical delay reward and punishment record, generates a response with a block chain evidence storage code after the strategy is applied, and completes processing and response to the request. According to the invention, the opening efficiency of the API service can be obviously improved, the cross-system security authentication process is optimized, and the access control of refined dynamic charging is realized.

Description

Technical Field

[0001] This invention belongs to the field of collaborative management and control technology of 5G public network and power enterprise, and specifically relates to a method for collaborative management and control of 5G public network and power enterprise. Background Technology

[0002] With the accelerated construction of power systems, power companies' reliance on 5G public networks is deepening from the basic communication layer to the business collaboration layer. Current mainstream technical solutions include: operator capability open platforms, providing standardized network APIs, but lacking customized interfaces for the power industry; power private cloud platforms, deployed within enterprise intranets, making wide-area resource scheduling difficult; and hybrid networking modes, combining 5G public networks with power private networks, but suffering from low protocol conversion efficiency and high operation and maintenance costs. However, traditional operator capability open platforms only support standardized communication APIs, requiring power companies to customize and develop adaptable interfaces, with development cycles as long as 2-3 months. Furthermore, power business systems require separate authentication via operator SIM cards and power PKI systems, resulting in authentication latency exceeding 100ms, failing to meet the ≤20ms requirement for distribution network automation. Operators' unified billing based on traffic leads to excessively high costs for control APIs, while monitoring APIs suffer from insufficient resource utilization. Operator policy libraries are based solely on network layer parameters and cannot identify power business scenarios. Therefore, the technical problem that this invention needs to solve is whether it can provide a collaborative management method for 5G public networks and power companies that can significantly improve the efficiency of API service opening, optimize cross-system security authentication processes, and achieve refined dynamic billing access control. Summary of the Invention

[0003] In view of this, the present invention provides a method for collaborative management and control of 5G public network and power enterprise.

[0004] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is as follows: The collaborative management and control method between 5G public networks and power companies includes the following steps: Step S1: Power companies submit a registration application for management and control capability APIs through the capability open platform of 5G public network operators. After being published by the power management and control platform, the APIs are legally invoked. The application includes service type identifiers and network slice SLA requirements. Service type identifiers include control type and monitoring type. Control type APIs are bound to URLLC slices and have a latency of ≤10ms. Monitoring type APIs are bound to eMBB slices and have a bandwidth of ≥50Mbps. Step S2: The power management platform performs two-factor authentication on the API caller. The operator verifies the 5G SIM card identifier, and the power side verifies the digital certificate of the power business system. The API caller who passes the identity authentication obtains API call authorization. After the authentication is passed, the access token generated embeds a billing level tag. The API caller is the power business system. Step S3: The API billing process bills API callers according to the agreed multi-dimensional dynamic billing rules, which include basic call fees, latency surcharges, and reliability surcharges. The billing results are sent back to the operator's policy library in real time and trigger the adjustment of slice parameters. Step S4: After receiving the API access request from the power business system, the power management and control platform combines the current network slice load rate provided by the operator capability open platform, the billing level label provided in step S2, and the historical latency reward and punishment records in the billing result database in step S3. It then obtains and applies the business-aware access control policy from the operator capability open platform, generates a response with blockchain-based notarized encoding after applying the policy, and completes the processing and response to the request.

[0005] Furthermore, in step S1, the registration and release steps for managing open capabilities include: S11. The power management and control platform sends a registration or release request for the management and control capability API to the operator's capability open platform. The request includes the power service level identifier, SLA indicators, and blockchain storage public key. S12. Upon receiving the request, the operator capability open platform will store the API information in a distributed database. The API information includes the IP address and port number, API category, interface protocol type, and environment variable parameters. At the same time, it will create initialization information for the management and control service API. S13. In its own network management capability system, the operator selects a matching configuration template from the pre-set network slice template library based on the SLA index in the API registration request. The template includes slice type identifier, latency guarantee parameters and bandwidth guarantee parameters. The selected template is encapsulated with power service characteristics into a power service-specific 5G management and control capability. S14. The operator capability open platform sends a registration or release response for the management and control open API to the power management and control platform. The response message includes a globally unique identifier for the API and network slicing configuration parameters, notifying the power management and control platform that the API has been registered and releasing the API. S15. The API release process is completed simultaneously: the API digital fingerprint is recorded on the power blockchain evidence storage platform; an API security label is generated according to the IEC62351-3 standard; and the interface parameters are filed with the National Energy Administration's regulatory platform.

[0006] Furthermore, in step S2, the API caller authentication and authorization steps include: S21. The API caller initiates a management API authorization request to the power management platform. This request contains the API caller's identity identifier and authentication information, specifically including the operator's 5G SIM card encryption identifier and the power business system digital certificate. S22. The power management platform begins two-factor authentication based on the contract information stored in the database. The operator verifies the validity of the SUCI identifier through the 5G AKA protocol, while the power side verifies the digital certificate chain and checks the matching between the business scenario code and the certificate permission scope. If authentication fails, an authentication failure message is returned, and access to the management API is denied. S23. If authentication is successful, the power management platform forwards the request to the operator's capability open platform. The operator's capability open platform generates a slice access certificate and performs a billing level assessment. S24. The power management platform returns an authorization request response to the API caller. The authorization response includes a dynamic access token and a blockchain notarization index value. The dynamic access token includes the operator slice access certificate, the power business permission level code, and the billing level label.

[0007] Furthermore, in step S3, the API billing process includes: S31. When the power management and control platform detects a management and control API call event, it generates a billing request message in real time and sends the billing request to the operator capability open platform. The billing request message includes the API caller's digital identity, service type code, actual call latency and reliability index data. After receiving the request, the S32 operator capability open platform will find the corresponding billing template and initiate the billing process: A pre-set billing template is matched based on the business type code. The template includes a basic call rate, a latency reward / penalty coefficient, and a reliability surcharge rate. The billing engine is invoked to calculate the current cost, where the latency penalty coefficient is calculated according to the formula: Rate adjustment value = (Actual latency - SLA latency) * Base coefficient; S33. The operator capability open platform returns a billing response to the power management and control platform and generates a billing list with a digital signature. The billing list is then reported to the power management and control platform through an encrypted communication protocol.

[0008] Furthermore, in step S4, the API gateway access control flow includes: S41. The API caller sends an access request to the power management platform. The access request includes the API caller's digital identity credentials and the service level identifier of the requested API. S42. The power management and control platform initiates a policy query request to the operator capability open platform through the 5G network slicing dedicated channel, and obtains the corresponding API access control policy from the operator capability open platform. The request includes power business scenario code, network load status parameters and blockchain storage index value. S43. The power management platform performs the following controls on the API call based on the obtained access control policy: Basic controls are used to verify whether the frequency of API calls exceeds a dynamic threshold. Enhanced control measures include limiting the flow of non-critical APIs when a red typhoon warning is issued by the National Meteorological Center or when the regional power load rate exceeds 90%. Emergency control: When a fault code defined by the IEC 61850-7-420 standard is identified, switch to the power line carrier communication backup channel, i.e., activate the PCL backup channel; S44. The power management platform returns an API access response to the API caller. When returning the response, it needs to generate an SM2 signature log, update the operator policy weight, and write the event hash into the blockchain.

[0009] Compared with the prior art, the beneficial effects of the present invention are as follows: This invention can significantly improve the efficiency of API service opening. Traditional operator capability opening platforms only provide standardized communication APIs, requiring power companies to develop additional adaptation interfaces, with development cycles lasting 2-3 months. In contrast, this invention, through deep coupling between the power management platform and the operator platform, enables one-click registration and automatic publishing of power-specific APIs, reducing deployment time to within 24 hours and improving efficiency by over 90%.

[0010] In existing technologies, power business systems need to submit independent authentication requests to the operator authentication system and the power PKI system respectively; however, this application receives requests uniformly through the power management and control platform, triggering verification on both the operator side and the power side in parallel, thus eliminating redundant communication overhead.

[0011] Existing billing models used by telecom operators charge a uniform price based on data usage, resulting in excessively high costs for control APIs and insufficient resource utilization for monitoring APIs. This invention introduces a multi-dimensional dynamic billing model into its technical solution, reducing the overall cost of API calls for power companies while improving resource utilization for telecom operators. Furthermore, this invention utilizes a joint power and communications strategy engine to automatically allocate high-priority slices to emergency command APIs during typhoon warnings and to limit the flow of non-critical APIs during peak electricity consumption periods. Attached Figure Description

[0012] Figure 1 This is a flowchart of the registration and release process for the control and open capabilities of this invention.

[0013] Figure 2 This is a flowchart of the API authentication and authorization process of this invention.

[0014] Figure 3 This is a flowchart of the API access billing process of the present invention.

[0015] Figure 4 This is the API access control flowchart of the present invention. Detailed Implementation

[0016] To further illustrate the technical means and effects of the present invention in order to achieve the intended purpose, the following detailed description of the specific implementation methods, structures, features and effects of the present invention, in conjunction with the accompanying drawings and preferred embodiments, is provided below.

[0017] Example like Figure 1-4 As shown in the figure, this embodiment discloses a method for collaborative management and control of 5G public network and power company, including steps S1-S4.

[0018] Step S1: Power companies submit a registration application for management and control capability APIs through the 5G public network operator's capability open platform. After being published by the power management and control platform, the APIs are legally invoked. The application includes a service type identifier and network slicing SLA requirements. The service type identifier includes control and monitoring categories. The network slicing SLA requirements are: control APIs are bound to URLLC slices with latency ≤10ms, and monitoring APIs are bound to eMBB slices with bandwidth ≥50Mbps.

[0019] Step S2: The power management platform performs two-factor authentication on the API caller. The operator verifies the 5G SIM card identifier, and the power company verifies the digital certificate of the power business system. The API caller who passes the authentication obtains API call authorization. After successful authentication, the access token generated embeds a billing level tag. The API caller is the power business system.

[0020] Step S3: The API billing process bills API callers according to the agreed multi-dimensional dynamic billing rules, which include a basic call fee, a latency surcharge, and a reliability surcharge. The billing results are sent back to the operator's policy database in real time and trigger slice parameter adjustments. The basic call fee is a benchmark unit price divided according to API category.

[0021] Step S4: After receiving the API access request from the power business system, the power management and control platform combines the current network slice load rate provided by the operator capability open platform, the billing level label provided in step S2, and the historical latency reward and punishment records in the billing result database in step S3. It then obtains and applies the business-aware access control policy from the operator capability open platform, generates a response with blockchain-based notarized encoding after applying the policy, and completes the processing and response to the request.

[0022] In step S1, the registration and release steps for managing open capabilities include steps S11-S15.

[0023] S11. The power management and control platform sends a registration or release request for the management and control capability API to the operator's capability open platform. The request includes the power service level identifier, SLA indicators, and blockchain-based notarized public key. For the power service level, control-type services are automatically marked as Level I, while monitoring-type services are classified as Level II or Level III based on data importance.

[0024] S12. Upon receiving the request, the operator capability open platform will store the API information in a distributed database. The API information includes the IP address and port number, API category, interface protocol type, and environment variable parameters. At the same time, it will create initialization information for the management and control service API.

[0025] S13. In its own network management capability system, the operator selects a matching configuration template from the pre-set network slice template library based on the SLA indicators in the API registration request. The template includes slice type identifier, latency guarantee parameters and bandwidth guarantee parameters. The selected template is then encapsulated with power service characteristics into a dedicated 5G management and control capability for power services.

[0026] S14. The operator capability open platform sends a registration or release response for the management and control open API to the power management and control platform. The response message includes a globally unique identifier for the API and network slicing configuration parameters, notifying the power management and control platform that the API has been registered and releasing the API.

[0027] S15. The API release process is completed simultaneously: the API digital fingerprint is recorded on the power blockchain evidence storage platform; an API security label is generated according to the IEC62351-3 standard; and the interface parameters are filed with the National Energy Administration's regulatory platform.

[0028] In step S2, the API caller authentication and authorization steps include S21-S24. This application achieves a single authentication latency of ≤5ms by integrating 5G SUCI and power digital certificates through a two-factor parallel authentication mechanism and supports automatic refresh of dynamic tokens.

[0029] S21. The API caller initiates a management API authorization request to the power management platform. This request contains the API caller's identity identifier and authentication information, specifically including the operator's 5G SIM card encryption identifier and the power business system digital certificate. S22. The power management platform begins two-factor authentication based on the contract information stored in the database. The operator verifies the validity of the SUCI identifier through the 5G AKA protocol, while the power side verifies the digital certificate chain and checks the matching between the business scenario code and the certificate permission scope. If authentication fails, an authentication failure message is returned, and access to the management API is denied. S23. If authentication is successful, the power management platform forwards the request to the operator's capability open platform. The operator's capability open platform generates a slice access certificate and performs a billing level assessment. S24. The power management platform returns an authorization request response to the API caller. The authorization response includes a dynamic access token and a blockchain notarization index value. The dynamic access token includes the operator slice access certificate, the power business permission level code, and the billing level label.

[0030] In step S3, the API billing process includes S31-S33.

[0031] S31. When the power management and control platform detects a management and control API call event, it generates a billing request message in real time and sends the billing request to the operator's capability open platform. The billing request message includes the API caller's digital identity, service type code, actual call latency and reliability index data.

[0032] After receiving the request, the S32 operator capability open platform will find the corresponding billing template and initiate the billing process: A pre-set billing template is matched based on the business type code. The template includes a basic call rate, a latency reward / penalty coefficient, and a reliability surcharge rate. The billing engine is invoked to calculate the current cost, where the delay penalty coefficient is calculated according to the formula: Rate adjustment value = (Actual delay - SLA delay) * Base coefficient.

[0033] In this embodiment, the control fee is set at 0.6 yuan / time, and the monitoring fee is set at 0.01 yuan / time. The latency surcharge is the deviation rate of the actual latency from the SLA multiplied by a base coefficient. For example, a bonus of 0.2 yuan is awarded for every 1ms reduction, in which case the base coefficient is 0.2 yuan / ms. The reliability surcharge is priced according to availability levels, such as no charge below 99%, and a 20% premium for above 99%.

[0034] S33. The operator capability open platform returns a billing response to the power management and control platform and generates a billing list with a digital signature. The billing list is then reported to the power management and control platform through an encrypted communication protocol.

[0035] In step S4, the API gateway access control flow includes S41-S44.

[0036] S41. The API caller sends an access request to the power management platform. The access request includes the API caller's digital identity credentials and the service level identifier of the requested API.

[0037] S42. The power management and control platform initiates a policy query request to the operator capability open platform through the 5G network slicing dedicated channel, and obtains the corresponding API access control policy from the operator capability open platform. The request includes power service scenario code, network load status parameters and blockchain storage index value. The power service scenario code is taken from the SCADA system real-time event library, and the network load status parameters include base station utilization and slice latency.

[0038] S43. The power management platform performs the following controls on the API call based on the obtained access control policy: Basic controls are used to verify whether the frequency of API calls exceeds a dynamic threshold. Enhanced control measures include limiting the flow of non-critical APIs when a red typhoon warning is issued by the National Meteorological Center or when the regional power load rate exceeds 90%. Emergency control: When a fault code defined in the IEC 61850-7-420 standard is identified, switch to the power line carrier communication backup channel, i.e., activate the PCL backup channel.

[0039] S44. The power management platform returns an API access response to the API caller. When returning the response, it needs to generate an SM2 signature log, update the operator policy weight, and write the event hash into the blockchain.

[0040] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any way. Although the present invention has been disclosed above with reference to preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art can make some modifications or alterations to the above-disclosed technical content to create equivalent embodiments without departing from the scope of the present invention. Any simple modifications, equivalent changes and alterations made to the above embodiments based on the technical essence of the present invention without departing from the scope of the present invention shall still fall within the scope of the present invention.

Claims

1. A method for collaborative management and control of 5G public networks and power enterprises, characterized in that, Comprise the following steps: Step S1, the power enterprise submits the control capability API registration application through the 5G public network operator's capability opening platform, and is called legally after being released by the power control platform, the application includes business type identification and network slice SLA requirement, the business type identification includes control class and monitoring class, the control class API binds URLLC slice and the time delay is less than or equal to 10 ms, the monitoring class API binds eMBB slice and the bandwidth is greater than or equal to 50 Mbps; Step S2, the power control platform carries out two-factor authentication operation to API invoker, the operator side verifies 5G SIM card identification, the power side checks the digital certificate of power business system, the API invoker obtains API calling authorization through identity authentication, the access token generated after authentication passes is embedded with charging level label, and the API invoker is a power business system; Step S3, the API charging process charges the API invoker according to the agreed multi-dimensional dynamic charging rule, the rule includes basic calling fee, time delay additional fee and reliability additional fee, and the charging result is returned to the operator policy library in real time and triggers slice parameter adjustment; Step S4, after the power control platform receives the API access request from the power business system, combines the current network slice load rate provided by the operator capability opening platform, the charging level label provided in step S2 and the historical time delay reward and punishment record in the charging result library of step S3, obtains and applies the business-aware access control strategy from the operator capability opening platform, generates a response with a block chain storage code after applying the strategy, and completes the processing and response to the request.

2. The 5G public network and power enterprise collaborative management method according to claim 1, characterized in that, In step S1, the registration and release steps of the control opening capability include: S11, the power control platform sends the registration or release request of the control capability API to the capability opening platform of the operator, and the request contains the power business level identification, SLA index and block chain storage public key; S12, after receiving the request, the operator capability opening platform will store the API information into the distributed database, the API information includes IP address and port number, API category, interface protocol type, environment variable parameter, and initialization information is created for the control service API at the same time; S13, the operator selects the matching configuration template from the preset network slice template library based on the SLA index in the API registration request in the network management capability system of the operator, the template includes slice type identification, time delay guarantee parameter and bandwidth guarantee parameter, and the selected template and power business characteristics are packaged as power business special 5G control capability; S14, the operator capability opening platform sends the control opening API registration or release response to the power control platform, the response message contains API global unique identifier and network slice configuration parameter, informs the power control platform that the API has been registered, and the API is published; S15, the API publishing process is completed synchronously: the API digital fingerprint is recorded in the power block chain storage platform;According to IEC62351-3 standard, API security label is generated;The interface parameters are recorded to the national energy bureau supervision platform.

3. The 5G public network and power enterprise collaborative management method according to claim 2, characterized in that, In step S2, the API caller authentication and authorization step includes: S21, the API caller initiates a management and control API authorization request to the power management and control platform, which contains the API caller identity and authentication information, including the 5G SIM card encryption identifier on the operator side and the digital certificate of the power business system on the power side; S22, the power management and control platform starts to perform two-factor authentication according to the subscription information stored in the database. The operator side verifies the validity of the SUCI identifier through the 5G AKA protocol, and the power side verifies the matching of the business scenario code and the certificate authority range by verifying the digital certificate chain. If the authentication fails, a message of authentication failure is returned, and access to the management and control API is denied; S23, if the authentication is passed, the power management and control platform forwards the request to the operator capability exposure platform, which generates a slice access credential and performs charging level evaluation, S24, the power management and control platform returns an authorization request response to the API caller, which contains a dynamic access token and a blockchain storage index value, wherein the dynamic access token includes the operator slice access credential, the power business permission level code and the charging level label.

4. The 5G public network and power enterprise collaborative management method according to claim 3, characterized in that, In step S3, the API charging process includes: S31, when the power management and control platform detects a management and control API calling event, it generates a charging request message in real time and sends a charging request to the operator capability exposure platform. The charging request message includes the API caller digital identity, the business type code, the actual calling delay and the reliability index data; S32, after receiving the request, the operator capability exposure platform finds the corresponding charging template and starts the charging process: According to the business type code, the pre-set charging template is matched, which includes the basic calling rate, the time delay reward and punishment coefficient, and the reliability additional rate; Call the charging engine to calculate the current fee, wherein the time delay reward and punishment coefficient is calculated according to the formula: rate adjustment value = (actual time delay-SLA time delay) * baseline coefficient; S33, the operator capability exposure platform returns a charging response to the power management and control platform and generates a charging list with a digital signature, which is reported to the power management and control platform through an encrypted communication protocol.

5. The 5G public network and power enterprise collaborative management method according to claim 4, characterized in that, In step S4, the API gateway access control process includes: S41, the API caller sends an access request to the power management and control platform, which includes the digital identity credential of the API caller and the service level identifier of the requested API; S42, the power management and control platform initiates a policy query request to the operator capability exposure platform through the 5G network slice special channel, and obtains the responding API access control policy from the operator capability exposure platform, wherein the request includes the power business scenario code, the network load state parameter and the blockchain storage index value; S43, the power management and control platform performs the following control on the API call according to the obtained access control policy: Basic control, used to check whether the API calling frequency exceeds the dynamic threshold; Enhanced control, when the Central Meteorological Observatory issues a red typhoon warning or the regional power load rate is greater than 90%, limit the flow of non-critical API; Emergency control, when the fault code defined in IEC 61850-7-420 standard is identified, switch to the power carrier communication backup channel, that is, start the PCL backup channel; S44, the power management platform returns the API access response to the API invoker, generates an SM2 signature log when returning, updates the operator policy weight, and writes the event hash into the blockchain.

Images