Business processing method and device and electronic equipment

Abstract

The invention provides a service processing method and device and electronic equipment, and relates to the technical field of infrastructure and IT supporting, and the method comprises the steps: adding the information of service capability; according to a business object in a pre-constructed business object model and a business scene in a business scene model, establishing an association relationship among the business capability, the business object and the business scene; the business object model comprises a mapping relationship among a plurality of business objects in at least two business systems; the business scene model comprises an association relationship among a plurality of business scenes. According to the embodiment of the invention, the mapping relationship is established among the plurality of business objects, so that different systems can be mapped according to capabilities, meaning confirmation caused by parameter differences among the business objects can be reduced, and the development efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of infrastructure and IT support, and particularly relates to a service processing method and device and electronic equipment. BACKGROUND

[0002] With the support capabilities of various systems and services being successively accessed to the platform, information including applicable scene description and capability parameter description has been deposited in the service capability registration process, and the point-to-point function service support between systems is realized through the standardized subscription process.

[0003] However, due to the large number of operator support manufacturers, the development standards and naming specifications of various manufacturers are not unified, which leads to the lack of consistency of the capability description for the same object. This makes the capability subscriber and provider need to repeatedly communicate and confirm the parameter meaning before calling the capability, which leads to low development efficiency. SUMMARY

[0004] Embodiments of the present application provide a service processing method and device and electronic equipment to solve the problem that the capability subscriber and provider need to repeatedly communicate and confirm the parameter meaning, which leads to low development efficiency.

[0005] To solve the above technical problems, the present application is implemented as follows:

[0006] In a first aspect, the embodiments of the present application provide a service processing method, executed by a first device, and the method comprises:

[0007] adding information of a service capability;

[0008] establishing an association relationship among the service capability, a service object in a service object model and a service scene in a service scene model according to the service object and the service scene;

[0009] The service object model comprises a mapping relationship among a plurality of service objects in at least two service systems.

[0010] The service scene model comprises information of a service scene corresponding to at least part of the service objects, the at least part of the service objects being at least part of the plurality of service objects, and the service scene model comprises an association relationship among a plurality of service scenes.

[0011] In a second aspect, the embodiments of the present application provide a service processing method, executed by a second device, and the method comprises:

[0012] In a case where first information input by a user is received, service information is identified based on the first information, the service information comprising at least one of the following: information of a service object, information of a service scene.

[0013] According to the pre-established association relationship among the business capability, the business object and the business scenario, output information of the business capability matched with the business information.

[0014] In a third aspect, an embodiment of the present application provides a business processing method, executed by a third device, and the method comprises:

[0015] Constructing a business object model of network objects, the business object model comprising mapping relationships among a plurality of business objects in at least two business systems;

[0016] Constructing a business scenario model based on the plurality of business objects, wherein the business scenario model comprises information of business scenarios corresponding to at least part of the business objects, the at least part of the business objects being at least part of the plurality of business objects, and the business scenario model comprises association relationships among a plurality of business scenarios.

[0017] In a fourth aspect, an embodiment of the present application provides a business processing apparatus, applied to a first device, and the apparatus comprises:

[0018] An adding module, configured to add information of a business capability;

[0019] An establishing module, configured to establish an association relationship among the business capability, the business object and the business scenario according to a business object in a pre-constructed business object model and a business scenario in a business scenario model;

[0020] The business object model comprises mapping relationships among a plurality of business objects in at least two business systems;

[0021] The business scenario model comprises information of business scenarios corresponding to at least part of the business objects, the at least part of the business objects being at least part of the plurality of business objects, and the business scenario model comprises association relationships among a plurality of business scenarios.

[0022] In a fifth aspect, an embodiment of the present application provides a business processing apparatus, applied to a second device, and the apparatus comprises:

[0023] An identifying module, configured to, in a case where first information input by a user is received, identify business information based on the first information, the business information comprising at least one of the following: information of a business object, information of a business scenario;

[0024] An outputting module, configured to, according to a pre-established association relationship among the business capability, the business object and the business scenario, output information of the business capability matched with the business information.

[0025] Sixthly, embodiments of this application provide a service processing apparatus applied to a third device, the apparatus comprising:

[0026] The first construction module is used to construct a business object model of network objects, wherein the business object model includes the mapping relationship between multiple business objects in at least two business systems;

[0027] The second construction module is used to construct a business scenario model based on the plurality of business objects, wherein the business scenario model includes information on business scenarios corresponding to at least some of the business objects, the at least some of the business objects being at least some of the plurality of business objects, and the business scenario model includes the association relationships between the plurality of business scenarios.

[0028] In a seventh aspect, embodiments of this application provide an electronic device, including: a processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, it implements the steps of the business processing method described in the first aspect, the second aspect, or the third aspect.

[0029] Eighthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the business processing method described in the first, second, or third aspects.

[0030] A ninth aspect provides a computer program product, including computer instructions that, when executed by a processor, implement the steps of the business processing method described in the first, second, or third aspect.

[0031] In this embodiment, a mapping relationship is established between multiple business objects, enabling different systems to map according to their capabilities. This reduces the need for interpretation due to parameter differences between business objects and improves development efficiency. Attached Figure Description

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

[0033] Figure 1 This is one of the flowcharts of a business processing method provided in the embodiments of this application;

[0034] Figure 2 This is a flowchart illustrating a method for constructing a business object model according to an embodiment of this application;

[0035] Figure 3 This is a flowchart illustrating a method for constructing a business scenario model according to an embodiment of this application;

[0036] Figure 4 This is a flowchart illustrating a method for visually displaying a business object model and a business scenario model, as provided in an embodiment of this application.

[0037] Figure 5 This is a flowchart of a service capability registration method provided in an embodiment of this application;

[0038] Figure 6 This is a flowchart of a business capability parameter conversion method provided in an embodiment of this application;

[0039] Figure 7 This is a second flowchart of a business processing method provided in an embodiment of this application;

[0040] Figure 8 This is a flowchart illustrating a business capability demonstration provided in an embodiment of this application;

[0041] Figure 9 This is a flowchart of a service capability aggregation method provided in an embodiment of this application;

[0042] Figure 10 This is the third flowchart of a business processing method provided in the embodiments of this application;

[0043] Figure 11 This is the fourth flowchart of a business processing method provided in the embodiments of this application;

[0044] Figure 12 This is one of the structural schematic diagrams of a business processing device provided in the embodiments of this application;

[0045] Figure 13 This is a second schematic diagram of the structure of a business processing device provided in an embodiment of this application;

[0046] Figure 14 This is the third schematic diagram of a business processing device provided in the embodiments of this application;

[0047] Figure 15 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

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

[0049] Currently, there are numerous systems developed for this platform, each with its own standards and naming conventions for the same object. Furthermore, there is a lack of unified standards for vendor-registered capabilities for the same object, and capability subscription and development models can only support specialized development groups. In addition, during development, the capability subscriber and capability provider need to communicate and confirm the true meaning of the capability parameters before they can be correctly invoked.

[0050] However, the current approach of developing features based on subscription capabilities after point-to-point communication results in low development efficiency.

[0051] To address the aforementioned issues, this application takes a specific business model as its core and uses a visualized and intuitive business model as a medium to standardize the parameters of cross-system capabilities. Based on this, through the intent recognition of business requirements and combined with capability business scenarios and usage information, it can quickly achieve intelligent recommendation of cross-system capabilities, intelligent weaving of cross-system capability parameters, and rapid transformation and regeneration of capabilities.

[0052] This application provides a business processing method, apparatus, and electronic device to solve the problem that the need for repeated communication and confirmation between the capability subscriber and the provider regarding the meaning of parameters leads to low development efficiency.

[0053] See Figure 1 , Figure 1 This is a flowchart of a business processing method provided in an embodiment of this application, which is executed by a first device. Figure 1 As shown, the method includes the following steps:

[0054] Step 101: Add information about business capabilities;

[0055] Step 102: Based on the business objects in the pre-built business object model and the business scenarios in the business scenario model, establish the association between the business capabilities, the business objects, and the business scenarios;

[0056] The business object model includes mapping relationships between multiple business objects in at least two business systems;

[0057] The business scenario model includes information about business scenarios corresponding to at least some business objects, wherein the at least some business objects are at least some of the multiple business objects, and the business scenario model includes the association relationships between multiple business scenarios.

[0058] The information for business capabilities includes the input of basic information about the business capability. This includes, for example, the capability name (e.g., user information query), capability code, description of the capability's purpose (e.g., querying basic user information), the business domain to which the capability belongs, and the capability priority. In addition, attribute parameters of the capability can also be entered, such as business operation information, installation services, and installation time.

[0059] The platform's registrant (also known as the provider) can (i.e., the first device) bind and associate the registered business capabilities with the corresponding business objects and business scenarios, thereby achieving the integration of business capabilities with business objects and business scenarios. Each system registers capabilities according to the accumulated capability list, based on business objects and business object scenarios.

[0060] The above process may include the following steps:

[0061] 1) Input of basic competency information

[0062] 2) Business Object Selection. Determine the scope of business objects that the capability can operate on, and establish a binding relationship with the business object model.

[0063] 3) Select a scenario. Based on the selected scope of business object scenarios, determine the business object scenarios for which capabilities are adapted, and establish a binding relationship with the selected business scenario model.

[0064] The platform (i.e., the third-party device) can pre-build business object models and business scenario models based on network objects. The business object model includes multiple business objects from different systems, as well as the relationships between these business objects. Since multiple business objects come from different systems, and the naming or names of the same business object may differ between systems, a mapping relationship can be established between these multiple business objects.

[0065] In some implementations, a mapping relationship is established between parameters of multiple business objects.

[0066] For example, the "cell ID" in system A and the "cell code" in system B are both named after cells, and a mapping relationship is established between the "cell ID" and the "cell code".

[0067] In some implementations, a mapping relationship can be established for two business objects that have different descriptions but are essentially the same object.

[0068] Business object models include, for example, building network object models, including cells, network resources, and resource pre-coverage. Information for each object model is shown in the table below:

[0069] Community object model

[0070]

[0071] Optical Splitter (POS) Object Model

[0072]

[0073] POS Port Object Model

[0074]

[0075] Standard address object information

[0076]

[0077] Relationship between address and resource coverage

[0078]

[0079] Furthermore, the parameters of business objects can be displayed in layers to provide a more detailed description of the business object's information, facilitating its understanding.

[0080] The establishment of the business object model can be achieved by designing the core model and extended model of the network object, thereby realizing the creation of the business model and completing the full coverage of the information of the business object.

[0081] like Figure 2 As shown, the process of building a business object model includes:

[0082] 1) Management of basic information of business object model.

[0083] 2) Management of parameter fields in business object models.

[0084] 3) Business object model relationship management: The business object model is managed through the management of business objects and their relationships.

[0085] Based on the business objects in the business object model, business scenario models can be defined according to the covered network scenarios, such as resource integration, network cutover, and network inspection. Information about the resource object scenario model is shown in the table below:

[0086]

[0087] The business scenario model includes the business objects involved in the business scenario and the relationships between business scenarios, as well as the relationships between different business object scenarios.

[0088] The establishment of a business scenario model can be achieved by designing the core model and extended models of the business scenario model. The core model can be created, and extended model designs can be provided to address the differences between various systems and manufacturers. This will enable the integration of common and personalized models and achieve full coverage of business scenario information.

[0089] Based on the business object model and the business object business scenario model, a business model visualization is constructed to realize the hierarchical display of business objects and the concrete display of abstract information, thereby reducing the threshold of professional knowledge domains. At the same time, scenario operations are loaded on each layer of business objects to achieve the organic integration of business objects and scenario capabilities.

[0090] The establishment of the business scenario model (also known as the business object scenario model) is as follows: Figure 3 As shown, business object scenario management involves selecting a business object model and the corresponding business object scenario, which may include the following process:

[0091] 1) Select the business object model.

[0092] 2) Enter the business object scenario model information.

[0093] 3) Enter the field information of the business object scenario model.

[0094] 4) Business object scenario model relationship management.

[0095] In some implementations, after the business object model and its relationships are generated, a visual topology for the business object model and a visual topology for the business scenario model are constructed based on these relationships, as well as the relationships between the business scenario models. This visually presents the relationships between the business object models and the relationships between the business scenario models. For example... Figure 4 As shown, the process includes the following:

[0096] 1. Visual topology construction for business objects

[0097] a) Read the business object model.

[0098] b) Read the relationship between business object associated sub-models based on the business object model.

[0099] c) Based on the business object model and the relationship between the business object associated sub-models, as well as the corresponding topology visualization template, construct the business object model visualization topology.

[0100] 2. Visual construction of business object scenarios

[0101] a) Select the business object model.

[0102] b) Based on the selected business object model, traverse the business scenario model.

[0103] c) Based on the business scenario model, traverse the business scenario relationship model.

[0104] Based on the business scenario model and the relationships between business scenario models, as well as the corresponding topology visualization template, construct a business object relationship model.

[0105] In this embodiment of the application, since the business object model includes multiple business objects from different systems and a mapping relationship is established between the multiple business objects, different systems can be mapped according to their capabilities, which can reduce the need for meaning confirmation due to parameter differences between business objects and improve development efficiency.

[0106] Optionally, the information of the business capability includes parameter information of the business capability; the step of establishing the association between the business capability, the business object, and the business scenario based on the business objects in the pre-built business object model and the business scenarios in the business scenario model includes:

[0107] The parameter information of the business capabilities is parsed to obtain the parsing results;

[0108] Based on the parsing results, as well as the business objects in the pre-built business object model and the business scenarios in the business scenario model, the association between the parameter information of the business capability, the information of the business object, and the information of the business scenario is established.

[0109] The capability registrant can operate on the first device to complete the registration of business capabilities. For example, in a scenario where the capability registrant is registering capabilities related to home customer services, the registration of business capabilities may include the following operations:

[0110] a. Display the list of residential communities

[0111] b. Click on the community to display the community topology, including buildings, entrances, floors, and door numbers within the community.

[0112] c. Click on a specific address to display the POS resources and port information pre-covered for that address.

[0113] d. Click on the covered resource to display the network topology relationship of the covered resource.

[0114] e. Clicking on each object in the topology will display a list of scenes.

[0115] f. Click "Add Capability" and enter the basic information about the capability.

[0116] Based on the newly added business capabilities, parameter information for those capabilities can be entered.

[0117] Registration process as follows Figure 5 As shown, the process includes the following:

[0118] 1. Input of basic competency information;

[0119] 2. Select the business object;

[0120] 3. Select the business scenario;

[0121] 4. Select capability parameter conversion. Convert the native parameters of the capability to the standard format.

[0122] 5. Capability Parameter Input. Generate capability parameters based on the converted standard message.

[0123] 6. Topological integration of capabilities and business scenarios.

[0124] In some implementations, the parameter information of the business capability (including input and output parameter message information) and the capability parsing package are imported. By calling the capability parsing package, the parameter message of the capability is parsed, the parsing result is obtained, and the result is displayed on the interface.

[0125] In some implementations, standardized content can be generated based on the parsing results, making it easier for the registrant to understand;

[0126] In some implementations, descriptive information about business capabilities can be generated based on the parsing results, including attributes, uses, associated business objects, business scenarios, and other information, making it easier for the registrant to quickly obtain relevant content.

[0127] For example, based on the message protocol and message parsing plugin of the capability input parameters and output parameters, the capability's input and output parameters are converted into a standard parsable JSON format, which facilitates quick registration.

[0128] The registrant can perform operations based on the parsing results displayed on the interface to establish associations between business capabilities and related business objects and scenarios.

[0129] In some implementations, based on the business object, scenario object, and basic information of the registered capability selected during capability registration, the capability weaving designer presents a business object model, an object scenario model, and business capabilities. The registrant user can click on a business object to display all its fields. The user can select the fields of the business object to which a relationship needs to be established and the parameter information of the capability model, and weave the relationship between the business object and the business capability by connecting them. This achieves automatic mapping of different capabilities across systems based on the same object's business information based on the business model.

[0130] For the capability parameters and the weaving process of the model, please refer to [link / reference].Figure 6 As shown, the process includes:

[0131] 1) Filter the data and obtain capability parameters based on the mapping relationship between business capabilities, business object models, and business object scenario models.

[0132] 2) Visualize the capability parameters registered for capability registration, and select the business model objects and business object scenario models involved in the capability parameters.

[0133] 3) Establish a mapping relationship between the capability parameters and the fields of the business object model and business scenario model.

[0134] 4) For fields whose capability parameters are of enumeration type, establish a conversion mapping relationship with common enumeration fields.

[0135] In this way, registered users can quickly understand and operate on business capabilities based on the parsing results, lowering the operational threshold. Through standardized parameter mapping, subscribers do not need to understand the meaning of underlying system parameters.

[0136] By linking business capabilities with information about business objects and business scenarios, the communication costs caused by different systems' differentiated descriptions of the same object are reduced when business objects and business scenarios involve different systems.

[0137] Optionally, the method further includes:

[0138] Based on the association between the business capability and the business object and the business scenario, the format of the target object's information is converted into a target format, wherein the target object includes at least one of the business object, the business scenario, and the business capability.

[0139] The target object can be determined based on actual needs.

[0140] For example, when different systems use different expressions for the same business object, or when the expressions for the business object are not standardized, the format of the business object is converted into a target format. This target format can be a unified standardized format for multiple different business systems to eliminate misunderstandings caused by different formats. Based on the converted standard message generation capability parameters, notes can also be added to each parameter for easier understanding.

[0141] For business capabilities, the parameters of the original business capabilities are standardized through business models, reducing the cost of communication between different systems or manufacturers.

[0142] Based on the binding relationship between business capabilities, business objects, and business object scenarios, the data can be presented according to the display format of the topology data, making it easier for registration personnel to operate.

[0143] Optionally, the method further includes:

[0144] Receive the user's first input;

[0145] In response to the first input, information about the business object is added to the business object model, and the business object model is updated.

[0146] If a business object in the business object model lacks a business field, the registrant can create an extended model by entering the first input and selecting the business object. The extended model adds information about the business object to the original business object model, resulting in an expanded business object model.

[0147] After creating the information for the business object, the relationship between the business object and the business capability can be woven in the manner described in the above implementation method.

[0148] For example, the information of the cell extension model for the cell information object is shown in the table below:

[0149]

[0150] Through the above methods, registered users can create models of business objects based on actual business needs, thereby improving the comprehensiveness of business objects.

[0151] In this embodiment, by binding business capabilities with business object models and business scenario models, and by visually displaying the fields of the business object model, the discrepancies in the understanding of the same object by different systems and different operators are effectively reduced.

[0152] By visualizing the way business capabilities are woven, the ease of use of capability orchestration is enhanced, and the efficiency of capability weaving is improved.

[0153] By using the business object model as a medium, it enables rapid association of different business capabilities across manufacturers and systems. Furthermore, through intelligent orchestration technology, it effectively reduces the difficulty of capability orchestration and capability weaving, and improves the efficiency of capability orchestration.

[0154] See Figure 7 , Figure 7 This is a flowchart of a business processing method provided in an embodiment of this application, which is executed by a second device. The method includes:

[0155] Step 701: Upon receiving the first information input by the user, identify business information based on the first information, wherein the business information includes at least one of the following: information about the business object and information about the business scenario;

[0156] Step 702: Based on the pre-established relationship between business capabilities, business objects, and business scenarios, output information about business capabilities that match the business information.

[0157] The first piece of information can be input by the subscriber user. Based on this first piece of information, the business object and business scenario can be automatically identified. This identification can be performed using an intelligent agent or a large language model, or through other methods. In some implementations, the intent can also be identified based on contextual information or historical records.

[0158] The first piece of information includes information about the business object and the business scenario, which can quickly identify the business object and the business scenario.

[0159] If the first information does not contain information about the business object and business scenario, intent recognition can be performed based on the first information, and business capabilities can be recommended based on the intent recognition of the business object and business scenario.

[0160] For example, a subscriber inputs: "I need to provide broadband installation services for users in XX community." The service object is identified as "community" and the service scenario as "broadband installation."

[0161] After identifying business objects and business scenarios, one or more relevant business capabilities can be recommended based on the pre-established association between business capabilities and business objects and business scenarios.

[0162] When outputting business capabilities, you can output the parameter information of the business capability, including the name of the business capability, its purpose description, etc. And the parameter information of the business capability is displayed in the converted standardized format (i.e., the target format).

[0163] The above process can be found in [reference]. Figure 8 As shown, the process includes the following:

[0164] 1) User inputs business requirements.

[0165] 2) Identify customer needs.

[0166] a. The second device identifies key information based on the context of the user's needs. If no key information is found, the platform will guide the user to input the key information.

[0167] b. After the user inputs information in accordance with the platform's agreement, the platform identifies key information in the input requirements, including the business object, the business object scenario, and the purpose of the capability.

[0168] 3) The second device outputs capability recommendations based on the identified key information.

[0169] 4) The second device displays the output results in a structured manner. For example, it uses a visual interface to show the relationship between business capabilities, business objects, and business scenarios. Since the parameters of business capabilities, business objects, and business scenarios are all presented in a standardized format, it is easy for users to understand and operate.

[0170] In this embodiment, by recognizing the intent of business needs and combining capability business scenarios and usage information, intelligent recommendations for cross-system capabilities can be quickly achieved, reducing manual communication and improving the accuracy and efficiency of capability recommendations.

[0171] Optionally, when outputting information on N business capabilities, and N is greater than 1, the method further includes:

[0172] Combine M of the N business capabilities to obtain a combined business capability, where M is an integer greater than 0 and M≤N;

[0173] Based on the information of the business object and the information of the business scenario, the parameter information of the combined business capabilities is generated.

[0174] When recommending multiple business capabilities, at least some of these capabilities can be combined to obtain new business capabilities, i.e., combined business capabilities.

[0175] In some implementations, multiple business capabilities are combined according to the business scenarios of each capability and the order in which the capabilities are executed;

[0176] In some implementations, the execution order of business capabilities is determined based on the dependencies between multiple business capabilities;

[0177] In some implementations, the execution order of service capabilities is determined based on routing conditions among multiple service capabilities.

[0178] In some implementations, the execution order of multiple service capabilities is determined based on user actions.

[0179] Users can also select field information from the business object model and business scenario model, and generate parameter information for combined business capabilities based on the user-selected field information. Users can also manipulate this parameter information to adjust or add parameters.

[0180] The process of combining business capabilities can be found in [reference needed]. Figure 9 As shown, the process includes the following:

[0181] 1) Definition of aggregation capability (i.e., combined business capability)

[0182] Define the basic information of the combined capabilities, such as name, code, user, business object, and business object scenario.

[0183] 2) Parameter definition of aggregation capability: Select the corresponding model according to the business object and business scenario, and define the input and output parameter information of the aggregation capability.

[0184] 3) Aggregation capability design. Define the aggregation capability scenario process based on the scenario requirements.

[0185] 4) Aggregator Node Capability Selection. Based on the aggregation node and the recommended business capabilities according to user needs, select the required business capabilities.

[0186] 5) Weaving of aggregated capability input parameters and node capability (i.e., business capability) input parameters. Based on the order of selected business capabilities and the relationship between business capabilities and business models, the mapping relationship between aggregated capability input parameters and node capability parameters is automatically generated, realizing automatic weaving of capability parameters. For personalized parameters of business capabilities, rule configuration methods are provided to enable on-demand design of all capability input and output parameter information before the node, meeting actual business needs.

[0187] 6) Node Capability Input Parameter Weaving. Based on the node's location, obtain the input and output parameter information of all business capabilities and aggregated capability input parameter information of the node's preceding routing nodes, using them as input capability parameters for the current node's weaving. Furthermore, based on the correlation between business capabilities and model parameters, automatically complete the loading and mapping of configurable node capability parameters, and implement the weaving of business parameters according to actual business logic.

[0188] 7) Aggregator node capability routing configuration. Based on the routing rule configuration designer, load all capability input / output parameter information and global variable information before the node, and configure the conditional rules for the route through the rule designer.

[0189] 8) Aggregation capability output parameter weaving. Based on the relationship between the aggregation capability output parameter information and the business model, load the output and input parameters of all capabilities involved in the aggregation capability, and perform parameter weaving according to the actual business requirements of the aggregation capability output parameters.

[0190] 9) Aggregation Capability Test. The test input / output message structure is automatically generated based on the aggregation capability output parameters. The user inputs relevant business information according to the message structure. The test starts, and the aggregation capability drives the flow of data based on the input values ​​and the mapping relationship between each node, outputting the mapping relationship at each step, and finally outputting the aggregation capability output parameters.

[0191] The above methods enable us to quickly obtain parameter information about business capabilities and improve operational efficiency.

[0192] Optionally, combining M of the N business capabilities to obtain a combined business capability includes:

[0193] Based on the execution order of M business capabilities among the N business capabilities, the M business capabilities are combined to obtain the combined business capabilities.

[0194] In some implementations, a capability aggregation designer is used to orchestrate capability logic. Users can select the corresponding business capabilities for each node.

[0195] Based on the relationships between business capabilities and the associations between business capabilities and business object models, the system can automatically determine the order of nodes corresponding to each business capability, thus completing the orchestration of capability parameters. If there are additional adjustments to the relationships between business capabilities, the nodes of the business capabilities that need to be adjusted can be selected for orchestration.

[0196] In some implementations, the parameter dependencies of M service capabilities are obtained to determine the order of these capabilities; alternatively, the order of these capabilities can be determined based on user actions; or the order can be determined based on service rules or capability priorities. The aforementioned order can include parallel relationships and sequential relationships.

[0197] When combining M business capabilities, you can first select the business object and business scenario corresponding to the combined capability, select the corresponding model field as the output parameter and input parameter, and extend the newly generated business field based on the business scenario.

[0198] Based on the contextual relationships of each business capability, determine the sequential and parallel relationships of the M business capabilities.

[0199] Based on the parameter information and model relationship of the business capabilities, as well as the order in which the business capabilities are implemented, the parameter mapping relationship between the business capabilities is automatically generated. The extended field information for each business capability can be configured according to the data algorithm relationship of the fields, ensuring that each business capability receives the necessary parameters.

[0200] By combining the M business capabilities in the above manner, the accuracy of the business capability sequence can be improved, and the execution effect of the business capabilities can be enhanced.

[0201] Optionally, the method further includes:

[0202] Based on the parameter information of the M business capabilities, configure the execution conditions between at least some of the M business capabilities;

[0203] The execution order of the M business capabilities is determined based on the execution conditions.

[0204] The execution conditions of business capabilities can be predefined, and the subsequent business capabilities can be determined based on the execution conditions.

[0205] If the conditions are met, business capability B will be executed after business capability A; if the conditions are not met, business capability C will be executed after business capability A.

[0206] For example, in a scenario providing broadband installation services for "XX Community," the business scenario is broadband installation. In this scenario, different broadband configuration capabilities are executed based on the community's coverage type.

[0207] If the coverage type is coverage, then execute the standard broadband configuration.

[0208] If the coverage type is not covered, then the basic broadband configuration will be executed.

[0209] By using the above method, the execution order of business capabilities can be dynamically adjusted through the configuration of execution conditions to adapt to different business scenarios.

[0210] See Figure 10 , Figure 10 This is a flowchart of a business processing method provided in this application, applied to a third device. As shown in the figure, the method includes:

[0211] Step 1001: Construct a business object model for network objects, wherein the business object model includes mapping relationships between multiple business objects in at least two business systems;

[0212] Step 1002: Construct a business scenario model based on the multiple business objects, wherein the business scenario model includes information about business scenarios corresponding to at least some of the business objects, the at least some of the business objects being at least some of the multiple business objects, and the business scenario model including the association relationships between the multiple business scenarios.

[0213] The third device can be a device belonging to the platform provider. The construction of the business object model and business scenario model can be found in the descriptions of the above embodiments.

[0214] By using business object models and business scenario models as mediums, the mapping and transformation of different capability parameters across manufacturers and systems are realized, solving the problem of weaving and mapping capability parameters from different sources and the problem of different providers' differentiated descriptions of the same object during the use of capabilities.

[0215] Optionally, the method further includes:

[0216] A topology graph is established based on the multiple business objects and the multiple business scenarios. The topology graph is used to visually display the relationships between the multiple business objects and the multiple business scenarios.

[0217] By displaying multiple business objects and scenarios in a topological structure, it facilitates quick operation for users and lowers the professional knowledge threshold, enabling cross-professional and cross-platform personnel to quickly understand the meaning of capability parameters during use.

[0218] Optionally, the business object model further includes information about each business object, which is used to describe the corresponding business object;

[0219] The information of the business object includes at least one of the following: first parameter information, second parameter information;

[0220] The first parameter information is common information corresponding to the at least two business systems;

[0221] The second parameter information is information corresponding to the first business system in the at least two business systems, and the first business system is the business system in which the second parameter information is located.

[0222] The first parameter information can be understood as the core field information of the business object. The core field is the unified business model field of the entire system. The first parameter information can be used by at least two business systems.

[0223] The second parameter information can be information about special business fields. For business object extended model fields, special common business fields of this system can be extended outside the business object according to the needs of each system, as the information corresponding to the first business system.

[0224] Each business system may include business objects and corresponding parameter information. In the case where the first business system includes the second parameter information of the business object, the first business system can be understood as the business system where the second parameter information is located.

[0225] As a specific embodiment, the business processing method of this application is as follows: Figure 11 As shown, the corresponding structure includes modules such as business object model creation, business scenario model management, business model visualization, capability registration, capability parameter business model weaving, capability subscription, and capability aggregation design.

[0226] The technical means employed include:

[0227] 1) Create network objects and object scene models through unified modeling methods.

[0228] 2) Based on object models and scenario models, construct a visualized business topology. Through visualization, improve subscribers' and registrants' understanding of business models, capabilities, and capability parameters, and reduce discrepancies.

[0229] 3) At each system capability registration node, based on the above method, the conversion of registration service parameters for each system is realized.

[0230] 4) In terms of parameter information standardization, capability weaving methods are introduced to achieve rapid mapping of cross-system capability parameters.

[0231] 5) Standardize the management of capability usage based on business type, business scenario, and specific purpose, and gradually revise capability usage labels based on the data referenced by the capability.

[0232] 6) Within the platform, the business models, capabilities, and functions of the management units can be isolated by version.

[0233] Using the above methods, business requirements can be automatically matched with the service capabilities registered by each system in the platform; under the premise of the manufacturer's capability registration specifications and standards, cross-system capability parameters can be quickly woven into application functions, and the normal operation of existing functions can still be guaranteed when business capabilities are upgraded.

[0234] See Figure 12 , Figure 12 This is a schematic diagram of the structure of a service processing device provided in an embodiment of this application, as shown below. Figure 12 As shown, the service processing device 1200 includes:

[0235] Add module 1201 to add information about business capabilities;

[0236] The module 1202 is used to establish the association between the business capabilities, the business objects, and the business scenarios based on the business objects in the pre-built business object model and the business scenarios in the business scenario model.

[0237] The business object model includes mapping relationships between multiple business objects in at least two business systems;

[0238] The business scenario model includes information about business scenarios corresponding to at least some business objects, wherein the at least some business objects are at least some of the multiple business objects, and the business scenario model includes the association relationships between multiple business scenarios.

[0239] Optionally, the information of the business capability includes parameter information of the business capability; the establishment module is specifically used for:

[0240] The parameter information of the business capabilities is parsed to obtain the parsing results;

[0241] Based on the parsing results, as well as the business objects in the pre-built business object model and the business scenarios in the business scenario model, the association between the parameter information of the business capability, the information of the business object, and the information of the business scenario is established.

[0242] Optionally, the device further includes:

[0243] The conversion module is used to convert the format of the target object's information into a target format based on the association between the business capability, the business object, and the business scenario. The target object includes at least one of the business object, the business scenario, and the business capability.

[0244] Optionally, the device further includes:

[0245] The receiving module is used to receive the user's initial input;

[0246] An update module is used to add business object information to the business object model and update the business object model in response to the first input.

[0247] The business processing unit 1200 can achieve Figure 1 The various processes implemented in the method embodiments can achieve the same technical effect, and will not be described again here to avoid repetition.

[0248] See Figure 13 , Figure 13 This is a schematic diagram of the structure of a service processing device provided in an embodiment of this application, as shown below. Figure 13 As shown, the service processing device 1300 includes:

[0249] The identification module 1301 is used to identify business information based on the first information input by the user, wherein the business information includes at least one of the following: information about the business object and information about the business scenario;

[0250] The output module 1302 is used to output information of business capabilities that match the business information based on the pre-established business capabilities, the association between the business object and the business scenario.

[0251] Optionally, when outputting information on N service capabilities, and N is greater than 1, the device further includes:

[0252] The combination module is used to combine M business capabilities from the N business capabilities to obtain a combined business capability, where M is an integer greater than 0 and M≤N;

[0253] The generation module is used to generate parameter information for the combined business capabilities based on the information of the business object and the information of the business scenario.

[0254] Optionally, the combined module is specifically used for:

[0255] Based on the execution order of M business capabilities among the N business capabilities, the M business capabilities are combined to obtain the combined business capabilities.

[0256] Optionally, the combined module is specifically used for:

[0257] Based on the parameter information of the M business capabilities, configure the execution conditions between at least some of the M business capabilities;

[0258] The execution order of the M business capabilities is determined based on the execution conditions.

[0259] The business processing unit 1300 is capable of achieving Figure 7 The various processes implemented in the method embodiments can achieve the same technical effect, and will not be described again here to avoid repetition.

[0260] See Figure 14 , Figure 14 This is a schematic diagram of the structure of a service processing device provided in an embodiment of this application, as shown below. Figure 14 As shown, the service processing device 1400 includes:

[0261] The first construction module 1401 is used to construct a business object model of network objects, wherein the business object model includes a mapping relationship between multiple business objects in at least two business systems;

[0262] The second construction module 1402 is used to construct a business scenario model based on the plurality of business objects, wherein the business scenario model includes information on business scenarios corresponding to at least some of the business objects, the at least some of the business objects being at least some of the plurality of business objects, and the business scenario model includes the association relationship between the plurality of business scenarios.

[0263] Optionally, the device further includes:

[0264] A module is established to create a topology graph based on the multiple business objects and the multiple business scenarios. The topology graph is used to visually display the relationships between the multiple business objects and the multiple business scenarios.

[0265] Optionally, the business object model further includes information about each business object, which is used to describe the corresponding business object;

[0266] The information of the business object includes at least one of the following: first parameter information, second parameter information;

[0267] The first parameter information is common information corresponding to the at least two business systems;

[0268] The second parameter information is dedicated information corresponding to the first business system in the at least two business systems, and the first business system is the business system in which the second parameter information is located.

[0269] The business processing unit 1400 is capable of achieving Figure 10 The various processes implemented in the method embodiments can achieve the same technical effect, and will not be described again here to avoid repetition.

[0270] like Figure 15 As shown, this application embodiment also provides an electronic device 1500, including: a processor 1501, a memory 1502, and a program stored in the memory 1502 and executable on the processor 1501. When the program is executed by the processor 1501, it implements the various processes of the above-described business processing method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0271] This application 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 above-described business processing method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again 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.

[0272] This application also provides a computer program product, including computer instructions, which, when executed by a processor, implement the above-described... Figure 1 , Figure 7 , Figure 10 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0273] 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.

[0274] 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 this application, 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 this application.

[0275] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application 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 this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A business processing method, characterized in that, Performed by a first device, the method includes: Add information about business capabilities; Based on the business objects in the pre-built business object model and the business scenarios in the business scenario model, establish the association between the business capabilities, the business objects, and the business scenarios; The business object model includes mapping relationships between multiple business objects in at least two business systems; The business scenario model includes information about business scenarios corresponding to at least some business objects, wherein the at least some business objects are at least some of the multiple business objects, and the business scenario model includes the association relationships between multiple business scenarios.

2. The method according to claim 1, characterized in that, The information about the business capabilities includes parameter information of the business capabilities; the step of establishing the association between the business capabilities, the business objects, and the business scenarios based on the pre-built business object model and the business scenarios in the business scenario model includes: The parameter information of the business capabilities is parsed to obtain the parsing results; Based on the parsing results, as well as the business objects in the pre-built business object model and the business scenarios in the business scenario model, the association between the parameter information of the business capability, the information of the business object, and the information of the business scenario is established.

3. The method according to claim 1, characterized in that, The method further includes: Based on the relationship between the business capabilities, the business objects, and the business scenarios, the information of the target object is converted into a target format, wherein the target object includes at least one of the business objects, the business scenarios, and the business capabilities.

4. The method according to claim 3, characterized in that, The method further includes: Receive the user's first input; In response to the first input, information about the business object is added to the business object model, and the business object model is updated.

5. A business processing method, characterized in that, Performed by a second device, the method includes: Upon receiving first information input by the user, business information is identified based on the first information, wherein the business information includes at least one of the following: information about the business object and information about the business scenario; Based on the pre-established relationships between business capabilities, business objects, and business scenarios, information on business capabilities that match the business information is output.

6. The method according to claim 5, characterized in that, When outputting information on N business capabilities, where N is greater than 1, the method further includes: Combine M of the N business capabilities to obtain a combined business capability, where M is an integer greater than 0 and M≤N; Based on the information of the business object and the information of the business scenario, the parameter information of the combined business capabilities is generated.

7. The method according to claim 6, characterized in that, The step of combining M of the N business capabilities to obtain combined business capabilities includes: Based on the execution order of M business capabilities among the N business capabilities, the M business capabilities are combined to obtain the combined business capabilities.

8. The method according to claim 7, characterized in that, The method further includes: Based on the parameter information of the M business capabilities, configure the execution conditions between at least some of the M business capabilities; The execution order of the M business capabilities is determined based on the execution conditions.

9. A business processing method, characterized in that, Performed by a third device, the method includes: Construct a business object model for network objects, wherein the business object model includes the mapping relationship between multiple business objects in at least two business systems; A business scenario model is constructed based on the multiple business objects, wherein the business scenario model includes information about business scenarios corresponding to at least some of the business objects, the at least some of the multiple business objects, and the business scenario model includes the association relationships between the multiple business scenarios.

10. The method according to claim 9, characterized in that, The method further includes: A topology graph is established based on the multiple business objects and the multiple business scenarios. The topology graph is used to visually display the relationships between the multiple business objects and the multiple business scenarios.

11. The method according to claim 10, characterized in that, The business object model also includes information for each business object, which is used to describe the corresponding business object. The information of the business object includes at least one of the following: first parameter information, second parameter information; The first parameter information is common information corresponding to the at least two business systems; The second parameter information is information corresponding to the first business system in the at least two business systems, and the first business system is the business system in which the second parameter information is located.

12. A business processing apparatus, characterized in that, Applied to a first device, the device includes: Add a module to add information about business capabilities; The module is used to establish the association between the business capabilities, the business objects, and the business scenarios based on the business objects in the pre-built business object model and the business scenarios in the business scenario model. The business object model includes mapping relationships between multiple business objects in at least two business systems; The business scenario model includes information about business scenarios corresponding to at least some business objects, wherein the at least some business objects are at least some of the multiple business objects, and the business scenario model includes the association relationships between multiple business scenarios.

13. A business processing apparatus, characterized in that, Applied to a second device, the device includes: The identification module is used to identify business information based on the first information input by the user, wherein the business information includes at least one of the following: information about the business object and information about the business scenario; The output module is used to output information about the business capabilities that match the business information, based on the pre-established relationship between the business capabilities, the business objects, and the business scenarios.

14. A business processing apparatus, characterized in that, Applied to a third device, the device includes: The first construction module is used to construct a business object model of network objects, wherein the business object model includes the mapping relationship between multiple business objects in at least two business systems; The second construction module is used to construct a business scenario model based on the plurality of business objects, wherein the business scenario model includes information on business scenarios corresponding to at least some of the business objects, the at least some of the business objects being at least some of the plurality of business objects, and the business scenario model includes the association relationships between the plurality of business scenarios.

15. An electronic device, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the business processing method as described in any one of claims 1 to 4; or implements the steps of the business processing method as described in any one of claims 5 to 8; or implements the steps of the business processing method as described in any one of claims 9 to 11.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the business processing method as described in any one of claims 1 to 4; or implements the steps of the business processing method as described in any one of claims 5 to 8; or implements the steps of the business processing method as described in any one of claims 9 to 11.

17. A computer program product, characterized in that, It includes computer instructions that, when executed by a processor, implement the steps of the business processing method as described in any one of claims 1 to 4; or implement the steps of the business processing method as described in any one of claims 5 to 8; or implement the steps of the business processing method as described in any one of claims 9 to 11.

Images