Data processing method and system, electronic device and storage medium

CN117118842BActive Publication Date: 2026-09-22CHINA TELECOM CORP LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202310899511.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-07-20
Publication Date
2026-09-22
Estimated Expiration
2043-07-20

AI Technical Summary

Technical Problem

[0003]本发明实施例是提供一种业务开通过程中的数据处理方法、系统、电子设备以及计算机可读存储介质,以解决或部分解决业务出现逻辑错乱的问题

Benefits of technology

[0053]在本发明实施例中,对于云网运营业务系统,云网运营业务系统至少包括编排系统、与编排系统通信连接的采控平台系统,云网运营业务系统与若干个不同的网元平台通信连接;其中,采控平台系统中配置有网元平台、调用动作以及接口信息对应的映射关系表,在业务开通过程中,编排系统响应于用户终端发送的业务需求信息,并生成与业务需求信息对应的报文信息,并向采控平台系统发送报文信息,报文信息至少包括节点标识与调用动作标识,接着采控平台系统根据节点标识与调用动作标识判断映射关系表中是否存在与业务需求信息对应的至少一个目标网元平台,若映射关系表中存在对应的至少一个目标网元平台,则将报文信息转换为目标网元平台支持的目标接口信息,并分别按照目标接口信息调用目标网元平台,从而通过将报文信息作为编排系统与采控平台系统之间的交互内容,减少交互两者之间的数据交互次数,降低业务逻辑的混乱性以及资源消耗,同时通过采控平台系统专注地对一组交互内容对网元平台并行进行调用,进一步减少了系统之间的数据交互,以及提高了业务开通的效率。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117118842B_ABST
    Figure CN117118842B_ABST
Patent Text Reader

Abstract

Embodiments of the present application provide a data processing method and system, electronic equipment and storage medium, which are applied to the technical field of IT and software development, and the method is applied to a cloud network operation business system, and the method comprises the following steps: a scheduling system responds to service demand information sent by a user terminal, generates message information corresponding to the service demand information, and sends the message information to a control platform system, wherein the message information at least comprises a node identifier and a calling action identifier; the control platform system judges whether at least one target network element platform corresponding to the service demand information exists in a mapping relationship table according to the node identifier and the calling action identifier, if the target network element platform exists in the mapping relationship table, the message information is converted into target interface information supported by the target network element platform, and the target network element platform is called according to the target interface information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the fields of IT and software development technology, and in particular to a data processing method in the process of service activation, a cloud network operation business system, an electronic device, and a computer-readable storage medium. Background Technology

[0002] For network elements, they are generally not directly associated with services and are only responsible for the simplest on / off command operations. Service parsing is handled by the upstream system. While this ensures the stability of network elements, it actually puts considerable pressure on the interfaces. Moreover, as the direct dependencies between service products continue to increase, command execution will have certain logical order requirements. Completely severing the connection with services often leads to errors in service activation logic. Summary of the Invention

[0003] This invention provides a data processing method, system, electronic device, and computer-readable storage medium during the service activation process to solve or partially solve the problem of logical errors in services.

[0004] This invention discloses a data processing method during service activation, applied to a cloud network operation business system. The cloud network operation business system includes at least an orchestration system and a data acquisition and control platform system communicatively connected to the orchestration system. The cloud network operation business system is communicatively connected to several different network element platforms. The data acquisition and control platform system is configured with a mapping table corresponding to network element platforms, invocation actions, and interface information. The method includes:

[0005] The orchestration system responds to the service requirement information sent by the user terminal, generates message information corresponding to the service requirement information, and sends the message information to the acquisition and control platform system. The message information includes at least a node identifier and a call action identifier.

[0006] The data acquisition and control platform system determines whether there is at least one target network element platform corresponding to the business requirement information in the mapping relationship table based on the node identifier and the call action identifier. If the target network element platform exists in the mapping relationship table, the message information is converted into target interface information supported by the target network element platform, and the target network element platform is called according to the target interface information.

[0007] Optionally, the data acquisition and control platform system determines whether there is at least one target network element platform corresponding to the business requirement information in the mapping relationship table based on the node identifier and the call action identifier, including:

[0008] If both the node identifier and the calling action identifier exist in the mapping table, the acquisition and control platform system selects the target network element platform corresponding to the node identifier from a number of network element platforms;

[0009] If the node identifier does not exist in the mapping table, the acquisition and control platform system generates a first return message for the message information. The first return message indicates that there is no information indicating that the network element platform called by the network element call instruction does not exist.

[0010] If the node identifier exists in the mapping table, and the calling action identifier does not exist in the mapping relationship to which the node identifier belongs, then the acquisition and control platform system generates a second return message for the message information. The second return message is information indicating that the network element platform called by the network element calling instruction does not support the calling action corresponding to the calling action identifier.

[0011] Optionally, the orchestration system responds to service requirement information sent by the user terminal and generates message information corresponding to the service requirement information, including:

[0012] The orchestration system responds to the service requirement information sent by the user terminal, inputs the service requirement information into a classification model for classification, and extracts key information from the service requirement information based on the classification results. The key information includes at least one of the following: user information, order information, terminal device information, and network port information.

[0013] The orchestration system uses at least one of the user information, the order information, the terminal device information, and the network port information to generate message information corresponding to the business requirement information.

[0014] Optionally, before the orchestration system generates message information corresponding to the business requirement information using at least one of the user information, the order information, and the terminal device information, the method further includes:

[0015] The orchestration system performs blockchain encryption verification on one of the user information, the order information, and the terminal device information to obtain the corresponding verification result.

[0016] Optionally, converting the message information into target interface information supported by the target network element platform includes:

[0017] Obtain the parameter conversion rules for the message information;

[0018] According to the type corresponding to the parameter conversion rule, the message information is converted into target interface information supported by the target network element platform.

[0019] Optionally, converting the message information into target interface information supported by the target network element platform according to the type corresponding to the parameter conversion rule includes:

[0020] If the parameter conversion rule is an encoding conversion, then the message information is converted into the target interface information supported by the target network element platform through regular expression conversion or fixed information addition.

[0021] If the parameter conversion rule is a script conversion rule, then the target script corresponding to the script conversion rule is obtained, and the message information is converted into target interface information supported by the target network element platform through the target exchange;

[0022] The target script includes one of the following: a Perl script, a Python script, and a FreeMarker script.

[0023] Optionally, it also includes:

[0024] The acquisition and control platform system sends a call message to the target network element platform, the call message being an instruction to the target service platform to perform an activation operation for the service requirement information;

[0025] The acquisition and control platform system receives the activation result sent by the target network element platform in response to the service requirement information.

[0026] This invention also discloses a cloud network operation business system, which includes at least an orchestration system and a data acquisition and control platform system communicatively connected to the orchestration system. The cloud network operation business system is communicatively connected to several different network element platforms. The data acquisition and control platform system is configured with a mapping table corresponding to network element platforms, invocation actions, and interface information. The device includes:

[0027] The message processing module located in the orchestration system is used to respond to the service requirement information sent by the user terminal, generate message information corresponding to the service requirement information, and send the message information to the acquisition and control platform system. The message information includes at least a node identifier and a call action identifier.

[0028] The data processing module located in the acquisition and control platform system is used to determine whether there is at least one target network element platform corresponding to the business requirement information in the mapping relationship table based on the node identifier and the call action identifier. If the target network element platform exists in the mapping relationship table, the message information is converted into target interface information supported by the target network element platform, and the target network element platform is called according to the target interface information.

[0029] Optionally, the data processing module is specifically used for:

[0030] If both the node identifier and the calling action identifier exist in the mapping table, the acquisition and control platform system selects the target network element platform corresponding to the node identifier from a number of network element platforms;

[0031] If the node identifier does not exist in the mapping table, the acquisition and control platform system generates a first return message for the message information. The first return message indicates that there is no information indicating that the network element platform called by the network element call instruction does not exist.

[0032] If the node identifier exists in the mapping table, and the calling action identifier does not exist in the mapping relationship to which the node identifier belongs, then the acquisition and control platform system generates a second return message for the message information. The second return message is information indicating that the network element platform called by the network element calling instruction does not support the calling action corresponding to the calling action identifier.

[0033] Optionally, the message processing module is specifically used for:

[0034] In response to the service request information sent by the user terminal, the service request information is input into a classification model for classification, and key information is extracted from the service request information based on the classification results. The key information includes at least one of user information, order information, terminal device information, and network port information.

[0035] The message information corresponding to the business requirement information is generated using at least one of the user information, the order information, the terminal device information, and the network port information.

[0036] Optionally, the cloud network operation business system further includes:

[0037] The verification module located in the acquisition and control platform system is used by the orchestration system to perform blockchain encryption verification on one of the user information, the order information, and the terminal device information to obtain the corresponding verification result.

[0038] Optionally, the message processing module is specifically used for:

[0039] Obtain the parameter conversion rules for the message information;

[0040] According to the type corresponding to the parameter conversion rule, the message information is converted into target interface information supported by the target network element platform.

[0041] Optionally, the data processing module is specifically used for:

[0042] If the parameter conversion rule is an encoding conversion, then the message information is converted into the target interface information supported by the target network element platform through regular expression conversion or fixed information addition.

[0043] If the parameter conversion rule is a script conversion rule, then the target script corresponding to the script conversion rule is obtained, and the message information is converted into target interface information supported by the target network element platform through the target exchange;

[0044] The target script includes one of the following: a Perl script, a Python script, and a FreeMarker script.

[0045] Optionally, it also includes:

[0046] The work order sending module located in the acquisition and control platform system is used to send a call message to the target network element platform. The call message is an instruction to the target service platform to perform an activation operation for the service requirement information.

[0047] The result receiving module located in the acquisition and control platform system is used to receive the activation result sent by the target network element platform for the service requirement information.

[0048] This invention also discloses an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0049] The memory is used to store computer programs;

[0050] When the processor executes a program stored in the memory, it implements the method described in the embodiments of the present invention.

[0051] This invention also discloses a computer-readable storage medium storing instructions that, when executed by one or more processors, cause the processors to perform the methods described in this invention.

[0052] The embodiments of the present invention have the following advantages:

[0053] In this embodiment of the invention, the cloud network operation business system includes at least an orchestration system and a data acquisition and control platform system that communicates with the orchestration system. The cloud network operation business system communicates with several different network element platforms. The data acquisition and control platform system is configured with a mapping table corresponding to network element platforms, call actions, and interface information. During the service activation process, the orchestration system responds to the service requirement information sent by the user terminal, generates message information corresponding to the service requirement information, and sends the message information to the data acquisition and control platform system. The message information includes at least a node identifier and a call action identifier. Then, the data acquisition and control platform system determines the mapping based on the node identifier and the call action identifier. If the mapping relationship table contains at least one target network element platform corresponding to the business requirement information, then the message information is converted into target interface information supported by the target network element platform, and the target network element platform is called according to the target interface information. In this way, by using the message information as the interaction content between the orchestration system and the acquisition and control platform system, the number of data interactions between the two is reduced, the confusion of business logic and resource consumption are reduced, and the acquisition and control platform system focuses on calling the network element platform in parallel for a set of interaction content, which further reduces the data interaction between systems and improves the efficiency of business activation. Attached Figure Description

[0054] Figure 1 This is a flowchart of the steps of a data processing method in the service activation process provided in an embodiment of the present invention;

[0055] Figure 2 This is a schematic diagram of the system communication architecture provided in an embodiment of the present invention;

[0056] Figure 3 This is a schematic diagram of the interactive interface provided in an embodiment of the present invention;

[0057] Figure 4 This is a structural block diagram of a cloud network operation business system provided in an embodiment of the present invention;

[0058] Figure 5 This is a block diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0059] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0060] As an example, network elements are generally not directly associated with services; they are primarily responsible for the simplest on / off command operations, while the interpretation of services is handled by the upstream system. While this ensures the stability of network elements, it actually puts significant pressure on the interfaces. Moreover, as the direct dependencies between services and products increase, command execution will have certain logical order requirements, and completely severing the connection with services often leads to errors in service activation logic.

[0061] To address this, this invention improves network element activation efficiency during service activation by associating simple instructions with business information and performing simple business parsing and merging. Specifically, it supports simultaneous invocation of network elements from multiple platforms, enabling rapid service activation and reducing interactions with the orchestration system. Compared to previous atomic capability scheduling, it allows for faster interaction between the orchestration system and the acquisition and control platform system, significantly improving service activation efficiency. The "new" aspect refers to the shift from the old atomic API (Application Programming Interface) capability scheduling between the orchestration system and the acquisition and control system. In this latter system, the orchestration system could only call the business platform capabilities encapsulated by the acquisition and control platform system one by one. The numerous atomic API capabilities led to frequent and repetitive calls, easily causing business logic chaos and significant system overhead, and in severe cases, even system crashes.

[0062] Reference Figure 1 This document illustrates a flowchart of a data processing method for service activation provided in an embodiment of the present invention. The method is applied to a cloud network operation service system, which includes at least an orchestration system and a data acquisition and control platform system communicatively connected to the orchestration system. The cloud network operation service system also communicates with several different network element platforms. The data acquisition and control platform system is configured with a mapping table corresponding to network element platforms, invocation actions, and interface information, and may specifically include the following steps:

[0063] Step 101: The orchestration system responds to the service requirement information sent by the user terminal, generates message information corresponding to the service requirement information, and sends the message information to the acquisition and control platform system. The message information includes at least a node identifier and a call action identifier.

[0064] Reference Figure 2For a cloud network operation business system, it can include an orchestration system and a data acquisition and control platform system that communicates with the orchestration system. The orchestration system is used to receive and process business requirement information, generate corresponding message information based on the business requirement information, and interact with the data acquisition and control platform system through the message information. The data acquisition and control platform system is used to determine and call the corresponding network element platform to perform the same operation for service activation. The cloud network operation business system can communicate with several different network element platforms. Different network element platforms can provide different business functions. For example, network element platforms can include PON (Passive Optical Network) network element platforms, BIMS (Business Information Management System) network element platforms, and ITMS (IT Management System) network element platforms, etc.

[0065] Optionally, for a PON network element platform, it can be a network element device used to process the network during service processing; for a BIMS network element platform, it can be a network element device used to process user information, order information, etc. during service processing; for an ITMS network element platform, it can be a network element device used to process terminal information during service processing.

[0066] In some feasible implementations, users can initiate corresponding business requests on their user terminals. After receiving the corresponding business request information, the cloud network operation business system generates corresponding message information based on the business request information through the orchestration system, and then transmits the message information to the acquisition and control platform system. The acquisition and control platform system determines whether it supports calling the corresponding network element platform based on the content recorded in the message information, and if it supports calling, it calls the corresponding network element platform to execute the corresponding business operation.

[0067] The business requirement information may include user information, order information, main product information attributes, sales item information attributes, auxiliary products and attributes, terminal device information attributes, resource information, and network element organization information. User information may include user-related information such as account and password; order information may include information corresponding to the services the user needs to activate, such as fixed-line, broadband, and mobile networks; main product information attributes may include the attributes of the main products corresponding to the activated services, such as the product attributes corresponding to fixed-line, broadband, and mobile networks; sales item information attributes may include the attributes of the sales items corresponding to the activated services; auxiliary products and attributes may include the auxiliary products corresponding to the activated services and their corresponding attributes; terminal device information attributes may include the relevant terminal parameters corresponding to the user's terminal; resource information may include equipment resources and network resources; and network element organization information may include information related to network elements, such as node identifiers and call action identifiers, which are not limited in this invention.

[0068] In its implementation, the orchestration system responds to service requirement information sent by user terminals by inputting the service requirement information into a classification model for classification. Based on the classification results, it extracts key information from the service requirement information, which includes at least one of user information, order information, terminal device information, and network interface information. Then, it uses at least one of these information to generate a message corresponding to the service requirement information. By classifying the service requirement information and filtering out irrelevant information, the system can determine the network element platform to be invoked based on the classified information. For example, user information and order information can be used to invoke the BINS network element platform, terminal device information can be used to invoke the ITMS network element platform, and network interface information can be used to invoke the PON network element platform. Thus, the system focuses on a single set of service requirement information and can identify multiple network element platforms to be invoked at once, allowing for parallel invocation of these platforms, reducing data interaction between systems and lowering system resource consumption.

[0069] In addition, for the categorized business information, the orchestration system can perform blockchain-encrypted verification on one of the user information, order information, and terminal device information to obtain the corresponding verification result, thereby ensuring data security through the corresponding encryption verification process.

[0070] In one example, a dataset is generated from historical database data for each category of business requirement information involved in the user's service activation process. This dataset is then combined with a classification prediction model to predict the probability that the dataset belongs to the current category. This is data filtering and optimization. Bayes' theorem is the foundation of the Naive Bayesian Classifier. If a given dataset has M categories, the Naive Bayesian Classifier can predict whether a given observation belongs to the category with the highest posterior probability. In other words, the Naive Bayesian Classifier predicts that X belongs to category C if and only if:

[0071] P(C i |X)>P(C j |X)1≤j≤m,j≠i

[0072] At this point, if we maximize P(X|C) i ), its P(X|C i The largest class C i This is known as the maximum a posteriori hypothesis, according to Bayes' theorem:

[0073]

[0074] It can be seen that since P(X) is equal for all categories, it is only necessary to have P(X|C) i )P(C i Take the maximum value.

[0075] To predict the class of an unknown sample X, we can perform a search on each class C. i Estimate the corresponding P(X|C) i )P(C i ).

[0076] P(C i |X)>P(C j |X)1≤j≤m,j≠i

[0077] Secondly, for high-weight information such as user information, order information, terminal device information, and network interface information in the set of business requirement information involved in the user's service activation process, blockchain encryption verification can be performed. Specifically, the integrity verification of a set of information data can be composed of the following five algorithms:

[0078] (1) Generate public / private key pair: KeyGen(1 k )->(pk, sk).

[0079] (2) Generate numeric tags: TagBlock(pk, sk, m)->T m .

[0080] (3) Generating challenge information: GenChal(c, r)->chal.

[0081] (4) Generating evidence: GenProof(pk, F, chal, ∑)->V.

[0082] (5) Verifying evidence: CheckProof(sk, V)->result.

[0083] After processing the service information based on the foregoing process, the corresponding message information can be generated, where the format of the message information can be as follows:

[0084]

[0085]

[0086] In the foregoing message information, "KTDKKT" may represent a PON network element platform, "BBMS" may represent a BIMS network element platform, and "ITMS" may represent an ITMS network element platform, etc., which is not limited in the present invention. In addition, for an acquisition and control platform system, it can be configured with a corresponding mapping relationship table, where the mapping relationship table includes the corresponding mapping relationship among node identifiers corresponding to different network element platforms, call action identifiers corresponding to call actions supported by the network element platforms, and API information, as shown in the following table:

[0087] BIMS 10000 RES_BIMS_Install_API BIMS 10001 RES_BIMS_Delete_API BIMS 10002 RES_BIMS_Modify_API ITMS 10000 RES_ITMS_Install_API ITMS 10001 RES_ITMS_Delete_API ITMS 10002 RES_ITMS_Modify_API KTDKKT 10000 RES_KTDKKT_Install_API KTDKKT 10001 RES_KTDKKT_Delete_API KTDKKT 10002 RES_KTDKKT_Modify_API

[0088] Wherein, 10000, 10001, and 10002 represent different call actions, for example, new service installation, service deletion, and service modification, etc. "BIMS-10000-RES_BIMS_Installation_API" represents information corresponding to an installation interface in a BIMS network element platform. When it is necessary to call the BIMS network element platform for new service registration, the BIMS network element platform can be called through the API information, and the service registration operation is performed. Optionally, services may include fixed network, broadband, mobile network and other services, and the call actions of the network element platform may include new service installation, service deletion, and service modification for the foregoing services, etc.

[0089] Step 102: the acquisition and control platform system determines, according to the node identifier and the call action identifier, whether there is at least one target network element platform corresponding to the service requirement information in the mapping relationship table, and if the target network element platform exists in the mapping relationship table, converts the message information into target interface information supported by the target network element platform, and calls the target network element platform according to the target interface information.

[0090] After receiving the message information sent by the orchestration system, the acquisition and control platform system can parse the message information to obtain the node identifier and call action identifier corresponding to the business requirement information. The node identifier can determine at least one target network element platform that needs to be called, and the call action identifier can determine the call action to be performed by the target network element platform corresponding to the business requirement, such as installing a new service, deleting a service, or modifying a service.

[0091] Specifically, the acquisition and control platform system can search the mapping table for the existence of a corresponding target network element platform based on the node identifier and the call action identifier. This allows the system to determine whether the orchestration system supports calling the corresponding network element platform. If the target network element platform exists in the mapping table, the acquisition and control platform system can convert the message information into target interface information supported by the target network element platform. Then, it can call the target network element platform according to the target interface information to execute the corresponding business operation. By using the message information as the interaction content between the orchestration system and the acquisition and control platform system, the number of data interactions between the two systems is reduced, thus reducing the confusion of business logic and resource consumption. At the same time, by focusing the acquisition and control platform system on calling the network element platform for a set of interaction content, the data interaction between systems is further reduced, and the efficiency of service activation is improved.

[0092] In some feasible implementations, if both a node identifier and a call action identifier exist in the mapping relationship table, the acquisition and control platform system selects the target network element platform corresponding to the node identifier from several network element platforms. If no node identifier exists in the mapping relationship table, the acquisition and control platform system generates a first receipt for the message information, which indicates that no network element platform is called by the network element call instruction. If a node identifier exists in the mapping relationship table, and no call action identifier exists in the mapping relationship to which the node identifier belongs, the acquisition and control platform system generates a second receipt for the message information, which indicates that the network element platform called by the network element call instruction does not support the call action corresponding to the call action identifier.

[0093] For example, in one example, assuming the node identifier is ITMS and the call action identifier is 10001, the corresponding "ITMS" and "10001" can be found in the mapping table, meaning the orchestration system supports calling the ITMS network element platform for new service installations. In another example, assuming the mapping table does not contain any information corresponding to KTDKKT, and the node identifier is KTDKKT, it can be determined that the orchestration system does not support calling the PON network element platform. The acquisition and control platform system can then generate the corresponding first receipt information to inform the orchestration system that the network element platform is not supported. In yet another example, assuming the node identifier is BIMS and the call action identifier is 10004, the corresponding "BIMS" can be found in the mapping table, but the call action "10004" corresponding to BIMS cannot be found. Therefore, it can be determined that the orchestration system does not support calling the BIMS network element platform to execute the service action corresponding to 10004, and a second receipt information is generated to inform the orchestration system that the corresponding network element platform does not support the service operation.

[0094] When the data acquisition and control platform system detects at least one target network element platform that meets business requirements, it can obtain parameter conversion rules for the message information. Then, according to the type corresponding to the parameter conversion rules, the message information is converted into target interface information supported by the target network element platform. Optionally, different conversion methods can be used for different parameter conversion rules. For example, if the parameter conversion rule is encoding conversion, the message information is converted into target interface information supported by the target network element platform through regular expression conversion or fixed information addition. If the parameter conversion rule is script conversion, the target script corresponding to the script conversion rule is obtained, and the message information is converted into target interface information supported by the target network element platform through target exchange. By converting the parameters in the message information into interface information supported by the network element platform, point-to-point network element platform calls can be achieved, improving the accuracy of network element platform calls. Furthermore, parameter conversion according to the corresponding parameter conversion rules effectively improves data processing efficiency, further improving the efficiency of parallel network element platform calls and reducing system resource overhead. The target script includes one of the following: Perl script, Python script, and FreeMarker script.

[0095] Optionally, Perl is a feature-rich computer programming language that runs on over 100 computer platforms and has wide applicability. Originally developed for text processing, it is now used for various tasks, including system administration, web development, network programming, GUI development, etc.; FreeMarker is a template engine: a general-purpose tool that uses templates and data to be modified to generate output text (HTML web pages, emails, configuration files, source code, etc.); Python provides efficient high-level data structures and also enables simple and effective object-oriented programming.

[0096] In one example, such as Figure 3 As shown, the parameter conversion rules can be configured by the user, and the specific configuration rules can be as follows:

[0097] a. When adding new data, the required elements are validated. The parameters marked with an asterisk (*) are required parameters.

[0098] b. Use the general major selection option. When a general major is selected, the parameter coding rules apply to all major parameter values ​​or conversion logic.

[0099] c. Among the parameters of real instructions, virtual instructions, virtual instruction sets, and APIs, the parameter encoding carried upstream is preferred. For example, if there is a servcode parameter transmitted northward, and the parameter conversion rule includes servcode encoding conversion logic, the servcode parameter value transmitted northward is preferred, and no parameter conversion is required.

[0100] d. When the parameter rule is encoding conversion, the parameter conversion rule is to add regular expressions or fixed information to the original parameter to convert it into a new parameter code. For example, if the original parameter is vc110 = 1000, the parameter conversion rule is servcode = abc${vc110}, and the final parameter is used as servcode = abc1000.

[0101] e. The parameter rules are converted using script rules. The parameter conversion rules are to convert the original parameters into new parameter codes using Perl, Python, or FreeMarker scripts.

[0102] After the parameter conversion operation is completed, the corresponding target interface information is generated, and work orders are invoked for all relevant target network element platforms according to the target interface information. If there are multiple network element platforms, multiple platforms are invoked simultaneously. The example of the invocation message information is as follows:

[0103]

[0104]

[0105] Among them, "DeviceIP" can be an IP address, "svlanCode" can be the corresponding code; "TASKTYPE" indicates that the task type is to view configuration items; "UpPort" can be the uplink port; "SWPort" can be the downlink port. Thus, the acquisition and control platform system can call the network element platform through the corresponding call message information, and further reduce the data interaction between the acquisition and control platform system and the orchestration system by focusing on calling the network element platform for a set of interactive content, and improve the efficiency of service activation.

[0106] Optionally, for the calling process of the network element platform, the acquisition and control platform system can send a calling message to the target network element platform. The calling message instructs the target service platform to perform an activation operation for the service requirement information, and then receives the activation result sent by the target network element platform in response to the calling message.

[0107] It should be noted that the embodiments of the present invention include, but are not limited to, the examples described above. It is understood that those skilled in the art can make further settings according to actual needs under the guidance of the ideas in the embodiments of the present invention, and the present invention does not limit such settings.

[0108] In this embodiment of the invention, the cloud network operation business system includes at least an orchestration system and a data acquisition and control platform system that communicates with the orchestration system. The cloud network operation business system also communicates with several different network element platforms. The data acquisition and control platform system is configured with a mapping table corresponding to network element platforms, invocation actions, and interface information. During the service activation process, the orchestration system responds to network element invocation instructions, obtains message information corresponding to the network element invocation instructions, and sends the message information to the data acquisition and control platform system. The message information includes at least a node identifier and an invocation action identifier. The data acquisition and control platform system then determines the appropriate information based on the node identifier and the invocation action identifier. The system determines whether a target network element platform corresponding to the network element call instruction exists in the mapping table. If a target network element platform exists in the mapping table, the message information is converted into target interface information supported by the target network element platform, and the target network element platform is called according to the target interface information. By using the message information as the interaction content between the orchestration system and the acquisition and control platform system, the number of data interactions between the two is reduced, the confusion of business logic and resource consumption are reduced, and the acquisition and control platform system focuses on calling the network element platform for a set of interaction content, which further reduces the data interaction between systems and improves the efficiency of service activation.

[0109] To enable those skilled in the art to better understand the technical solutions in the embodiments of the present invention, an example is provided below for illustration:

[0110] When a user initiates a broadband installation application through a user terminal, the user terminal can send the corresponding service requirement information to the cloud network operation service system. The service requirement information includes at least user information, order information, main product information attributes, sales product information attributes, auxiliary products and attributes, terminal equipment information, resource information, and network element organization information.

[0111] The orchestration system within the cloud network operation business system categorizes business requirement information and extracts key information based on a classification model, including user information, order information, terminal device information, and network element organization information. This information is then verified using blockchain. Assuming successful verification, user information is used to invoke the BIMS network element platform to activate user accounts and passwords; order information is used to invoke the BIMS network element platform to activate new broadband; and terminal device information is used to invoke ITMS to authenticate and activate user terminals. The network element organization information can include the platform identifiers of the network element platforms invoked for this information, as well as the corresponding invocation action identifiers. For example, in broadband installation services, the network element platforms involved include at least the aforementioned BIMS and ITMS network element platforms, and the invocation actions include the BIMS network element platform activating new installation services and the ITMS network element platform activating terminal devices. Once the network element platform to be invoked is determined through the acquisition and control platform system, the acquisition and control platform system can further convert parameters through the corresponding conversion rules, generate corresponding invocation message information, and send the invocation message information to the BIMS network element platform and the ITMS network element platform respectively, and invoke both in parallel to complete the broadband installation service.

[0112] Through the above process, by using message information as the interaction content between the orchestration system and the acquisition and control platform system, the number of data interactions between the two is reduced, the confusion of business logic and resource consumption are reduced, and at the same time, the acquisition and control platform system focuses on calling the network element platform for a set of interaction content, which further reduces the data interaction between systems and improves the efficiency of service activation.

[0113] It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0114] Reference Figure 4This diagram illustrates a structural block diagram of a cloud network operation service system provided in an embodiment of the present invention. The cloud network operation service system includes at least an orchestration system and a data acquisition and control platform system communicatively connected to the orchestration system. The cloud network operation service system is communicatively connected to several different network element platforms. The data acquisition and control platform system is configured with a mapping table corresponding to network element platforms, invocation actions, and interface information, and may specifically include the following modules:

[0115] The message processing module 401 located in the orchestration system is used to respond to the service requirement information sent by the user terminal, generate message information corresponding to the service requirement information, and send the message information to the acquisition and control platform system. The message information includes at least a node identifier and a call action identifier.

[0116] The data processing module 402 located in the acquisition and control platform system is used to determine whether there is at least one target network element platform corresponding to the business requirement information in the mapping relationship table based on the node identifier and the call action identifier. If the target network element platform exists in the mapping relationship table, the message information is converted into target interface information supported by the target network element platform, and the target network element platform is called according to the target interface information.

[0117] In some feasible implementations, the data processing module 402 is specifically used for:

[0118] If both the node identifier and the calling action identifier exist in the mapping table, the acquisition and control platform system selects the target network element platform corresponding to the node identifier from a number of network element platforms;

[0119] If the node identifier does not exist in the mapping table, the acquisition and control platform system generates a first return message for the message information. The first return message indicates that there is no information indicating that the network element platform called by the network element call instruction does not exist.

[0120] If the node identifier exists in the mapping table, and the calling action identifier does not exist in the mapping relationship to which the node identifier belongs, then the acquisition and control platform system generates a second return message for the message information. The second return message is information indicating that the network element platform called by the network element calling instruction does not support the calling action corresponding to the calling action identifier.

[0121] In some feasible implementations, the message processing module 401 is specifically used for:

[0122] In response to the service request information sent by the user terminal, the service request information is input into a classification model for classification, and key information is extracted from the service request information based on the classification results. The key information includes at least one of user information, order information, terminal device information, and network port information.

[0123] The message information corresponding to the business requirement information is generated using at least one of the user information, the order information, the terminal device information, and the network port information.

[0124] In some feasible implementations, the cloud network operation business system further includes:

[0125] The verification module located in the acquisition and control platform system is used by the orchestration system to perform blockchain encryption verification on one of the user information, the order information, and the terminal device information to obtain the corresponding verification result.

[0126] In some feasible implementations, the message processing module 401 is specifically used for:

[0127] Obtain the parameter conversion rules for the message information;

[0128] According to the type corresponding to the parameter conversion rule, the message information is converted into target interface information supported by the target network element platform.

[0129] In some feasible implementations, the data processing module 402 is specifically used for:

[0130] If the parameter conversion rule is an encoding conversion, then the message information is converted into the target interface information supported by the target network element platform through regular expression conversion or fixed information addition.

[0131] If the parameter conversion rule is a script conversion rule, then the target script corresponding to the script conversion rule is obtained, and the message information is converted into target interface information supported by the target network element platform through the target exchange;

[0132] The target script includes one of the following: a Perl script, a Python script, and a FreeMarker script.

[0133] In some feasible implementations, it also includes:

[0134] The work order sending module located in the acquisition and control platform system is used to send a call message to the target network element platform. The call message is an instruction to the target service platform to perform an activation operation for the service requirement information.

[0135] The result receiving module located in the acquisition and control platform system is used to receive the activation result sent by the target network element platform for the service requirement information.

[0136] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0137] In addition, this invention also provides an electronic device, including: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the various processes of the data processing method embodiment in the above-described service activation process and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0138] This invention also provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the various processes of the data processing method embodiments described above for the service activation process, achieving the same technical effects. To avoid repetition, these will not be elaborated upon here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0139] Figure 5 A schematic diagram of the hardware structure of an electronic device for implementing various embodiments of the present invention.

[0140] The electronic device 500 includes, but is not limited to, components such as: a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, a memory 509, a processor 510, and a power supply 511. Those skilled in the art will understand that the electronic device structure involved in the embodiments of the present invention does not constitute a limitation on the electronic device. An electronic device may include more or fewer components than illustrated, or combine certain components, or have different component arrangements. In the embodiments of the present invention, the electronic device includes, but is not limited to, mobile phones, tablet computers, laptops, PDAs, in-vehicle terminals, wearable devices, and pedometers.

[0141] It should be understood that, in this embodiment of the invention, the radio frequency unit 501 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink data from the base station and processes it with the processor 510; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 501 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc. Furthermore, the radio frequency unit 501 can also communicate with networks and other devices through a wireless communication system.

[0142] The electronic device provides users with wireless broadband internet access through the network module 502, such as helping users send and receive emails, browse web pages, and access streaming media.

[0143] The audio output unit 503 can convert audio data received by the radio frequency unit 501 or the network module 502 or stored in the memory 509 into audio signals and output them as sound. Furthermore, the audio output unit 503 can also provide audio output related to specific functions performed by the electronic device 500 (e.g., call signal reception sound, message reception sound, etc.). The audio output unit 503 includes a speaker, a buzzer, and a receiver, etc.

[0144] Input unit 504 is used to receive audio or video signals. Input unit 504 may include a graphics processing unit (GPU) 5041 and a microphone 5042. The GPU 5041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on display unit 506. The image frames processed by GPU 5041 can be stored in memory 509 (or other storage medium) or transmitted via radio frequency unit 501 or network module 502. Microphone 5042 can receive sound and process such sound into audio data. The processed audio data can be converted into a format that can be transmitted to a mobile communication base station via radio frequency unit 501 in telephone call mode.

[0145] The electronic device 500 also includes at least one sensor 505, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 5061 according to the ambient light level, and the proximity sensor can turn off the display panel 5061 and / or backlight when the electronic device 500 is moved to the ear. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used to identify the posture of the electronic device (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. The sensor 505 may also include a fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared sensor, etc., which will not be described in detail here.

[0146] The display unit 506 is used to display information input by the user or information provided to the user. The display unit 506 may include a display panel 5061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0147] User input unit 507 can be used to receive input numerical or character information, and to generate key signal inputs related to user settings and function control of electronic devices. Specifically, user input unit 507 includes a touch panel 5071 and other input devices 5072. Touch panel 5071, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 5071). Touch panel 5071 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to the processor 510, which receives and executes commands from the processor 510. In addition, touch panel 5071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. Besides touch panel 5071, user input unit 507 may also include other input devices 5072. Specifically, other input devices 5072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, joysticks, etc., which will not be described in detail here.

[0148] Furthermore, the touch panel 5071 can cover the display panel 5061. When the touch panel 5071 detects a touch operation on or near it, it transmits the information to the processor 510 to determine the type of touch event. Subsequently, the processor 510 provides corresponding visual output on the display panel 5061 according to the type of touch event. It is understood that in one embodiment, the touch panel 5071 and the display panel 5061 are implemented as two independent components to realize the input and output functions of the electronic device. However, in some embodiments, the touch panel 5071 and the display panel 5061 can be integrated to realize the input and output functions of the electronic device. The specific implementation is not limited here.

[0149] Interface unit 508 serves as an interface for connecting external devices to electronic device 500. For example, external devices may include a wired or wireless headphone port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and so on. Interface unit 508 can be used to receive input from external devices (e.g., data, power, etc.) and transmit the received input to one or more components within electronic device 500, or it can be used to transmit data between electronic device 500 and external devices.

[0150] The memory 509 can be used to store software programs and various data. The memory 509 may primarily include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). Furthermore, the memory 509 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0151] The processor 510 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 509, and by calling data stored in the memory 509, it performs various functions and processes data, thereby providing overall monitoring of the electronic device. The processor 510 may include one or more processing units; preferably, the processor 510 may integrate an application processor and a modem processor. The application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 510.

[0152] The electronic device 500 may also include a power supply 511 (such as a battery) for supplying power to various components. Preferably, the power supply 511 can be logically connected to the processor 510 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system.

[0153] In addition, the electronic device 500 includes some functional modules not shown, which will not be described in detail here.

[0154] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0155] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0156] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of the present invention.

[0157] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this invention can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0158] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0159] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0160] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0161] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0162] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0163] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A data processing method during service activation, characterized in that, The method is applied to a cloud network operation business system, which includes at least an orchestration system and a data acquisition and control platform system communicatively connected to the orchestration system. The cloud network operation business system is communicatively connected to several different network element platforms. The data acquisition and control platform system is configured with a mapping table corresponding to network element platforms, invocation actions, and interface information. The method includes: The orchestration system responds to the service requirement information sent by the user terminal, generates message information corresponding to the service requirement information, and sends the message information to the acquisition and control platform system. The message information includes at least a node identifier and a call action identifier. The acquisition and control platform system determines whether there is at least one target network element platform corresponding to the business requirement information in the mapping relationship table based on the node identifier and the call action identifier. If the target network element platform exists in the mapping relationship table, the message information is converted into target interface information supported by the target network element platform according to the type corresponding to the parameter conversion rule of the message information, and the target network element platform is called according to the target interface information. The interaction content between the orchestration system and the acquisition and control platform system is message information. The orchestration system responds to service request information sent by the user terminal and generates message information corresponding to the service request information, including: The orchestration system responds to the service requirement information sent by the user terminal, inputs the service requirement information into a classification model for classification, and extracts key information from the service requirement information based on the classification results. The key information includes at least one of the following: user information, order information, terminal device information, and network port information. The orchestration system uses at least one of the user information, the order information, the terminal device information, and the network port information to generate message information corresponding to the business requirement information.

2. The method according to claim 1, characterized in that, The data acquisition and control platform system determines whether there is at least one target network element platform corresponding to the business requirement information in the mapping table based on the node identifier and the call action identifier, including: If both the node identifier and the calling action identifier exist in the mapping table, the acquisition and control platform system selects the target network element platform corresponding to the node identifier from a number of network element platforms; If the node identifier does not exist in the mapping table, the acquisition and control platform system generates a first return message for the message information. The first return message is information indicating that there is no network element platform called by the network element call instruction. If the node identifier exists in the mapping table, and the calling action identifier does not exist in the mapping relationship to which the node identifier belongs, then the acquisition and control platform system generates a second return message for the message information. The second return message is information indicating that the network element platform called by the network element calling instruction does not support the calling action corresponding to the calling action identifier.

3. The method according to claim 1, characterized in that, Before the orchestration system generates message information corresponding to the business requirement information using at least one of the user information, the order information, and the terminal device information, the method further includes: The orchestration system performs blockchain encryption verification on one of the user information, the order information, and the terminal device information to obtain the corresponding verification result.

4. The method according to claim 1, characterized in that, The step of converting the message information into target interface information supported by the target network element platform according to the type corresponding to the parameter conversion rules of the message information includes: Obtain the parameter conversion rules for the message information; According to the type corresponding to the parameter conversion rule, the message information is converted into target interface information supported by the target network element platform.

5. The method according to claim 4, characterized in that, The step of converting the message information into target interface information supported by the target network element platform according to the type corresponding to the parameter conversion rule includes: If the parameter conversion rule is an encoding conversion, then the message information is converted into the target interface information supported by the target network element platform through regular expression conversion or fixed information addition. If the parameter conversion rule is a script conversion rule, then obtain the target script corresponding to the script conversion rule, and convert the message information into target interface information supported by the target network element platform through the target script; The target script includes one of the following: a Perl script, a Python script, and a FreeMarker script.

6. The method according to any one of claims 1-5, characterized in that, Also includes: The acquisition and control platform system sends a call message to the target network element platform, the call message instructing the target network element platform to perform an activation operation for the service requirement information; The acquisition and control platform system receives the activation result sent by the target network element platform in response to the service requirement information.

7. A cloud network operation business system, characterized in that, The cloud network operation business system includes at least an orchestration system and a data acquisition and control platform system communicatively connected to the orchestration system. The cloud network operation business system also communicates with several different network element platforms. The data acquisition and control platform system is configured with a mapping table corresponding to network element platforms, invocation actions, and interface information. The cloud network operation business system includes: The message processing module located in the orchestration system is used to respond to the service requirement information sent by the user terminal, generate message information corresponding to the service requirement information, and send the message information to the acquisition and control platform system. The message information includes at least a node identifier and a call action identifier. The data processing module located in the acquisition and control platform system is used to determine whether there is at least one target network element platform corresponding to the business requirement information in the mapping relationship table based on the node identifier and the call action identifier. If the target network element platform exists in the mapping relationship table, the message information is converted into target interface information supported by the target network element platform according to the type corresponding to the parameter conversion rule of the message information, and the target network element platform is called according to the target interface information. The interaction content between the orchestration system and the acquisition and control platform system is message information. Specifically, the message processing module is used for: In response to the service request information sent by the user terminal, the service request information is input into a classification model for classification, and key information is extracted from the service request information based on the classification results. The key information includes at least one of user information, order information, terminal device information, and network port information. The message information corresponding to the business requirement information is generated using at least one of the user information, the order information, the terminal device information, and the network port information.

8. An electronic device, characterized in that, It includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; The memory is used to store computer programs; When the processor executes a program stored in the memory, it implements the method as described in any one of claims 1-6.

9. A computer-readable storage medium having instructions stored thereon that, when executed by one or more processors, cause the processors to perform the method as described in any one of claims 1-6.

Citation Information

Patent Citations

  • Service calling method and system

    CN111722947A

  • Service calling method and system based on access gateway

    CN112243032A