Method and system for creating a functional service, electronic device and computer storage medium

Abstract

The application provides a function service creation method and system, an electronic device and a computer storage medium, comprising: configuring an access interface of a function module; acquiring module type and capability description information of the function module; constructing a service capability relationship table corresponding to the function module according to the module type and the capability description information; and creating a function service corresponding to the function module by using the service capability relationship table. By configuring the access interface of the function module, the corresponding service capability relationship is constructed according to the module type and the capability description information of the function module, and the function service is created based on the service capability relationship, so that the function module is taken as the service creation center, the service creation logic is consistent with the service target, the effectiveness of the function service creation is effectively improved, the function module corresponds to the service capability relationship, the efficiency of the function service creation is effectively improved, and the problem of how to improve the efficiency and effectiveness of the function service creation is solved.

Description

Technical Field

[0001] This invention relates to the field of software design technology, and in particular to a method and system for creating functional business processes, an electronic device, and a computer storage medium. Background Technology

[0002] Functional modules are used to implement corresponding business functions. For example, a testing module is used to execute related testing tasks. Therefore, the creation of a functional business function is the starting point for implementing that function, and the quality of its creation significantly affects the efficiency and effectiveness of subsequent functional business execution.

[0003] Current functional service creation focuses primarily on communication protocols, treating functional modules merely as interfaces for data interaction. This leads to unclear binding relationships between creation logic and functional module types. Furthermore, access methods differ for functional modules with different encapsulations and management protocols, but existing functional service creation methods lack configuration for relevant parameters. Accessing functional modules of different models or protocols results in access failures, leading to unrecognized module types and the inability to create and execute services. In addition, different functional modules support different service types, and the current functional service creation method fails to effectively obtain the association information between functional modules and their supported service types, nor does it verify the compatibility between functional modules and service types. Incompatibility is only discovered after service creation, resulting in high trial-and-error costs and low service creation efficiency. Summary of the Invention

[0004] The purpose of this invention is to provide a method and system for creating functional services, an electronic device, and a computer storage medium, so as to at least solve the problem of how to improve the efficiency and effectiveness of creating functional services.

[0005] To solve the above-mentioned technical problems, the present invention provides a method for creating functional services, comprising: Configure the access interface of the functional module so that the functional module can be accessed; Obtain the module type and capability description information of the functional modules; Based on the module type and capability description information, construct a business capability relationship table corresponding to the functional modules; Use the business capability relationship table to create the functional business corresponding to the functional module.

[0006] Optionally, in the functional service creation method, the method for configuring the access interface of the functional module includes: Based on the encapsulation interface of the functional module, determine the access interface of the functional module and configure the access type and related setting parameters of the functional module. The encapsulation interface includes QSFP-DD interface, OSFP interface, CFP2 interface, and SFP-DD interface. The access type includes I2C and MDIO. The related setting parameters include access rate and access latency.

[0007] Optionally, in the functional service creation method, the method for obtaining the module type and capability description information of the functional module includes: The module type of the functional module is confirmed by combining hardware packaging identification and protocol identification. Based on the module type of the functional module, load the corresponding module management protocol parser to parse the capability description information of the functional module.

[0008] Optionally, in the aforementioned functional service creation method, the method for confirming the module type of the functional module through a combination of hardware packaging identification and protocol identification includes: Based on the encapsulation type of the physical port into which the functional module is inserted, determine the major encapsulation category of the functional module; Using the hardware signals corresponding to the package category, the presence information of the functional module and the related hardware pins are identified to initialize the module to an accessible state; The module type is determined by reading the identification field of the functional module through the protocol. The identification field includes one or more of the following: module type identifier, manufacturer name, model number, and serial number.

[0009] Optionally, in the functional service creation method, the module management protocol includes one of SFF-8472, SFF-8636, CMIS, and C-CMIS; the capability description information includes one or more of the following: supported rate level, number of channels, supported service type, and diagnostic monitoring capabilities.

[0010] Optionally, in the aforementioned functional business creation method, the method for constructing a business capability relationship table corresponding to a functional module based on the module type and capability description information includes: Based on the module type and capability description information, obtain the set of business types supported by the functional module; Construct a business capability relationship table containing a set of business types, using module type as the key.

[0011] Optionally, in the aforementioned functional service creation method, the method for obtaining the set of service types supported by the functional module based on the module type and capability description information includes: By using capability-business mapping rules, the set of business types supported by the functional module is derived, wherein the capability-business mapping rules map to the executable business types using the capability description information of the functional module as an index.

[0012] Optionally, in the functional business creation method, the business capability relationship table includes at least one of the following fields: module type identifier, protocol identifier, module capability summary, supported business type set, and business parameter constraint field.

[0013] Optionally, in the aforementioned method for creating functional services, the method for creating functional services corresponding to functional modules using a business capability relationship table includes: Using functional modules as the operation center, the business types supported by the functional modules are displayed in the business capability relationship table; Hide or gray out business types that are not in the business capability relationship table; Based on the supported business types, create the corresponding functional business for each functional module.

[0014] Optionally, in the above method for creating functional services, the method of creating functional services corresponding to functional modules using a business capability relationship table further includes: When a user triggers a business type that a functional module does not support via an unconventional path, a preliminary check is performed based on the business capability relationship table to prevent the creation of the business function and to indicate the business types that the functional module supports.

[0015] To address the aforementioned technical problems, the present invention also provides a functional service creation system for implementing the functional service creation method described in any of the preceding claims, wherein the functional service creation system comprises: The function configuration module is used to configure the access interface of the function module so that the function module can be accessed; The information acquisition module is used to acquire information about the module type and capability description of the functional modules. The form building module is used to build a business capability relationship table corresponding to the functional modules based on the module type and capability description information; The business creation module is used to create functional business corresponding to a functional module by utilizing the business capability relationship table.

[0016] To address the aforementioned technical problems, the present invention also provides an electronic device, including a memory, a processor, and an executable program stored in the memory and capable of being run by the processor; when the processor runs the executable program, it executes the functional service creation method as described in any of the preceding claims.

[0017] To address the aforementioned technical problems, the present invention also provides a computer storage medium storing an executable program; when the executable program is executed, it implements the functional service creation method described in any of the preceding claims.

[0018] The present invention provides a method and system for creating functional services, an electronic device, and a computer storage medium, comprising: configuring access interfaces for functional modules to enable access to the functional modules; obtaining module type and capability description information of the functional modules; constructing a business capability relationship table corresponding to the functional modules based on the module type and capability description information; and creating functional services corresponding to the functional modules using the business capability relationship table. By configuring access interfaces for functional modules, constructing corresponding business capability relationships based on module type and capability description information, and creating functional services based on these relationships, the invention uses functional modules as the center for service creation. This not only effectively improves the effectiveness of functional service creation because the service creation logic aligns with business objectives, but also effectively improves the efficiency of functional service creation because the functional modules correspond to the business capability relationships. This solves the problem of how to improve the efficiency and effectiveness of functional service creation. Attached Figure Description

[0019] Figure 1 A flowchart of the functional service creation method provided in this embodiment; Figure 2 This is a table showing the service capability relationships of the optical module provided in this embodiment; Figure 3 This embodiment provides a structural block diagram of the system for creating functional services. Detailed Implementation

[0020] The functional service creation method and system, electronic device, and computer storage medium proposed in this invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that the drawings are all in a very simplified form and use non-precise scales, used only to facilitate and clarify the illustration of the embodiments of this invention. Furthermore, the structures shown in the drawings are often part of the actual structure. In particular, different figures may emphasize different aspects and sometimes use different scales.

[0021] It should be noted that the terms "first," "second," etc., used in the specification, claims, and drawings of this invention are used to distinguish similar objects in order to describe embodiments of the invention, and are not used to describe a specific order or sequence. It should be understood that such uses of terminology are interchangeable where appropriate. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0022] This embodiment provides a method for creating functional services, such as Figure 1 As shown, it includes: S1, Configure the access interface of the functional module so that the functional module can be accessed; S2, obtain the module type and capability description information of the functional module; S3, construct a business capability relationship table corresponding to the functional module based on the module type and capability description information; S4. Using the business capability relationship table, create the functional business corresponding to the functional module.

[0023] The functional business creation method provided in this embodiment configures the access interface of the functional module, constructs the corresponding business capability relationship according to the module type and capability description information of the functional module, and creates functional businesses based on the business capability relationship. This makes the functional module the center of business creation, which not only effectively improves the effectiveness of functional business creation because the business creation logic is consistent with the business objectives, but also effectively improves the efficiency of functional business creation because the functional module corresponds to the business capability relationship. This solves the problem of how to improve the efficiency and effectiveness of functional business creation.

[0024] Specifically, in this embodiment, step S1 involves configuring the access interface of the functional module so that the functional module can be accessed.

[0025] In practical applications, the access interface of a functional module can be determined and the access type and related settings parameters can be configured based on the encapsulation interface of the functional module.

[0026] When the functional module is an optical module, the packaging interface may specifically include a QSFP-DD (four-channel small form factor pluggable dual-density) interface, an OSFP (eight-channel small form factor pluggable) interface, a CFP2 (a standardized pluggable optical module packaging specification in optical communication) interface, or an SFP-DD (dual-density small form factor pluggable) interface. Correspondingly, the access type may include I2C (integrated circuit bus) or MDIO (management data input / output), and the relevant setting parameters may include access rate and access latency.

[0027] Specifically, when the encapsulation interface is a QSFP-DD interface, OSFP interface, or SFP-DD interface, the access type is I2C; when the encapsulation interface is a CFP2 interface, the access type is MDIO.

[0028] Furthermore, in this embodiment, default interface settings are preset: I2C access rate is 400kHz, MDIO access rate is 4MHz, and access latency is 100µs. In practical applications, corresponding custom configurations can also be provided to prevent functional modules from being unable to recognize the interface.

[0029] Of course, those skilled in the art can reasonably determine the access type and related setting parameters corresponding to the encapsulated interface based on the above examples and the actual functional module requirements, and this application does not impose any restrictions on this.

[0030] Furthermore, in this embodiment, step S2, the method for obtaining the module type and capability description information of the functional module, includes: S21 uses a combination of hardware packaging identification and protocol identification to confirm the module type of the functional module.

[0031] Specifically, in this embodiment, firstly, the package type of the functional module is determined according to the package type of the physical port into which the functional module is inserted; then, the presence information of the functional module and related hardware pins are identified and the module is initialized to an accessible state using the hardware signals corresponding to the package type; after that, the identification field of the functional module is read through the protocol to determine the module type of the functional module, wherein the identification field includes one or more of the following: module type identifier, manufacturer name, model and serial number.

[0032] Taking the optical module as an example, in practical applications, after the optical module is inserted into the interface, the optical module is first identified using hardware signals and initialized. Specifically, the insertion of the optical module can be identified by detecting changes in corresponding hardware signals, such as PRSL (Presence Detection Signal). If the optical module is inserted, it can be reset and initialized using hardware signals, such as RESL (Reset Signal).

[0033] Then, based on the access type and related setting parameters provided in step S1, an access test is performed on the optical module. If access is unsuccessful, a prompt will be given. If the access test is successful, the contents of the internal EEPROM (Electrically Erasable Programmable Read-Only Memory) of the optical module are read according to the package type. For optical modules with QSFP-DD, OSFP, or SFP package interfaces, the module type can be further subdivided according to the SFF-8024 protocol. For optical modules with CFP2 package interfaces, the module type can be determined as CFP2 or CFP2-DCO module based on the specific address 0x8000 of the CFP2 optical module.

[0034] S22, based on the module type of the functional module, load the corresponding module management protocol parser to parse the capability description information of the functional module.

[0035] Specifically, in this embodiment, based on the module type of the functional module, the corresponding capability description information, management protocol, and related version information of the functional module can be found through an internally established correspondence table between functional modules and module management protocols. The capability description information includes one or more of the following: supported rate levels, number of channels, supported service types, and diagnostic monitoring capabilities.

[0036] Taking optical modules as an example, the module management protocols may include SFF-8472 (Optical Module Digital Diagnostic Monitoring Interface Protocol), SFF-8636 (QSFP Series Pluggable Optical Module Core Management Protocol), CMIS (Content Management Interoperability Service Standard Protocol), C-CMIS (Extended Management Specification for Digital Coherent Optical Modules), CFP MSA (Multi-Source Protocol for High-Speed ​​Optical Communication Modules Supporting Hot-Swapping), etc.

[0037] In one specific embodiment, if the optical module type is SFP, SFP+, SFP28, or SFP56, the corresponding module management protocol is SFF-8472; if the optical module type is QSFP-DD, the corresponding module management protocol is CMIS; if the optical module type is QSFP or QSFP28, the corresponding module management protocol is SFF-8636; and if the optical module type is CFP2, the corresponding module management protocol is CFP MSA.

[0038] Of course, those skilled in the art can reasonably determine the corresponding capability description information and management protocol based on the above examples and the module type of the actual functional module, and this application does not impose any restrictions on this.

[0039] Furthermore, in this embodiment, step S3, the method for constructing the business capability relationship table corresponding to the functional module based on the module type and capability description information, includes: S31. Based on the module type and capability description information, obtain the set of business types supported by the functional module.

[0040] Specifically, in this embodiment, the set of service types supported by the functional module is derived using the capability-service mapping rule, wherein the capability-service mapping rule maps to the executable service type using the capability description information of the functional module as an index.

[0041] Taking the optical module as an example again, based on the module type, management protocol, and capability description information obtained in step S2, and according to the relevant parameters defined in the management protocol, the types of services supported by the optical module are analyzed as follows: For module types SFP, SFP+, SFP28, and SFP56, the supported service types are parsed according to the protocol content in SFF-8472: First, obtain Byte 3-10 (standard compatibility code), Byte 36 (extended compatibility code), Byte 12 (nominal rate, 100 MBd unit), Byte 62 (FC Speed ​​2, 64GFC) + Byte 11 (encoding method) from each byte of Page A0h; then, summarize the set of service types supported by the optical module.

[0042] For module types QSFP and QSFP28, the supported service types are analyzed based on the relevant content of SFF-8636: First, obtain Byte 131-138 (standard compatibility code), Byte 140 / Byte 222 (rate), Byte 164 (IB rate code), and Byte 192 / Byte 116 (extended compliance code) from each byte of Page 00h; then, summarize the set of service types supported by the optical module.

[0043] For module type QSFP-DD, the supported service types are parsed according to the relevant CMIS content: First, obtain Byte 85 (the resolution table for determining Media Interface ID) and Bytes 86-117 (the AppSel) from Page 00h. Then, obtain Bytes 176-190 (the resolution table for determining Media Lane Assignment Options) and Bytes 223-250 (the App Sel) from Page 01h. Next, parse each item: Host Interface ID (check the host interface specification using SFF-8024), Media Interface ID (check the media interface specification using SFF-8024), and Lane Counts / Assignment (the lane instantiation method of this application) until Host Interface ID=FFh is encountered (end of list). Finally, summarize the set of service types supported by the optical module.

[0044] For module types CFP2 and CFP2-DCO, the supported service types are analyzed based on the relevant content of the CFP MSA: First, read 8000h (Module Identifier) ​​to confirm that 11h = CFP2 or 19h = CFP2-DCO; then, read 8003h (Ethernet service), 8007h (OTN / Coherent service), 8006h (SONET service), and 8008h (Supplemental Rate) in sequence; next, read 800Ah (Media Attributes) and 8009h (Number of Channels); then, read 801Ah (Coherent Module Mode Switched to: DPQPSK / 16QAM); finally, summarize the set of service types supported by the optical module.

[0045] S32, using module type as the key, construct a business capability relationship table containing a set of business types.

[0046] Specifically, in this embodiment, the business capability relationship table includes at least one of the following fields: module type identifier, protocol identifier, module capability summary, supported business type set, and business parameter constraint field. In practical applications, the business capability relationship table can be constructed through automatic generation and / or configuration maintenance.

[0047] Taking optical modules as an example, the constructed service capability relationship table is as follows: Figure 2 As shown, each module type is listed in turn with the module type as the key, including the management protocol, business domain, supported services under each business domain, number of service channels, service rate, number of single service channels, SerDes mode, and SerDes rate.

[0048] Furthermore, in this embodiment, step S4 involves using the business capability relationship table to create the functional business corresponding to the functional module.

[0049] Specifically, in this embodiment, a graphical user interface for the functional modules can be constructed based on the business capability relationship table, with the functional modules as the operation center. This interface displays the business types supported by the functional modules in the business capability relationship table and provides the business paths that can be created (supported) according to the functional modules, so that users can create functional services of the business types supported by the functional modules according to the prompted business paths.

[0050] Furthermore, in this embodiment, service types that are not in the service capability relationship table can be hidden or grayed out in the graphical user interface.

[0051] Furthermore, in this embodiment, when a user triggers a service type that the functional module does not support through an unconventional path, a preliminary verification is performed based on the service capability relationship table to prevent the creation of the service and to indicate the service type supported by the functional module.

[0052] The functional service creation method provided in this embodiment takes the functional module as the center for creating services. Users directly face the functional module and its capabilities. The process of creating a service is "selecting a functional module → selecting the services supported by the functional module". There is no need to configure protocol parameters unrelated to the functional module in advance. The operation path is greatly shortened and is fully aligned with the essential requirements of the functional module, ensuring that the creation logic is consistent with the functional goals.

[0053] The functional service creation method provided in this embodiment enables reliable access to functional modules with different encapsulations and management protocols through configurable adaptation of interface parameters. This provides underlying protection for functional modules to become service creation centers, solves the pain point of traditional instruments becoming inaccessible when the model is changed, and ensures the accessibility of functional modules.

[0054] The functional service creation method provided in this embodiment automatically completes module type identification, protocol parsing, and service identification, automatically constructs and visualizes the capability relationship table, significantly improves configuration accuracy during multi-product parallel testing, and effectively enhances service creation efficiency.

[0055] The functional service creation method provided in this embodiment can automatically obtain the service creation capability of a new functional module by simply updating the service capability relationship table when adding a new module type. This method has low expansion costs for new models and new protocols and enhances the scalability of service creation.

[0056] This embodiment also provides a functional service creation system for implementing the functional service creation method described above, such as... Figure 3 As shown, the functional business creation system includes: The function configuration module is used to configure the access interface of the function module so that the function module can be accessed; The information acquisition module is used to acquire information about the module type and capability description of the functional modules. The form building module is used to build a business capability relationship table corresponding to the functional modules based on the module type and capability description information; The business creation module is used to create functional business corresponding to a functional module by utilizing the business capability relationship table.

[0057] The functional business creation system provided in this embodiment configures the access interfaces of functional modules through a functional configuration module, constructs corresponding business capability relationships based on the module type and capability description information of the functional modules, and creates functional businesses based on the business capability relationships. This makes the functional modules the center of business creation, which not only effectively improves the effectiveness of functional business creation because the business creation logic is consistent with the business objectives, but also effectively improves the efficiency of functional business creation because the functional modules correspond to the business capability relationships. This solves the problem of how to improve the efficiency and effectiveness of functional business creation.

[0058] Furthermore, this embodiment also provides an electronic device, including a memory, a processor, and an executable program stored in the memory and capable of being run by the processor; when the processor runs the executable program, it performs the functional service creation method described above.

[0059] Furthermore, this embodiment also provides a computer storage medium storing an executable program; when the executable program is executed, it implements the functional service creation method described above.

[0060] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between embodiments can be referred to mutually. In addition, different parts between embodiments can also be combined with each other, and this invention does not limit this.

[0061] This embodiment provides a method and system for creating functional services, an electronic device, and a computer storage medium. The method includes: configuring access interfaces for functional modules to enable access; obtaining module type and capability description information for the functional modules; constructing a business capability relationship table corresponding to the functional modules based on the module type and capability description information; and creating functional services corresponding to the functional modules using the business capability relationship table. By configuring access interfaces for functional modules, constructing corresponding business capability relationships based on module type and capability description information, and creating functional services based on these relationships, the method uses functional modules as the center for service creation. This not only effectively improves the effectiveness of functional service creation because the service creation logic aligns with business objectives, but also effectively improves the efficiency of functional service creation because the functional modules correspond to the business capability relationships. This solves the problem of how to improve the efficiency and effectiveness of functional service creation.

[0062] The above description is merely a description of preferred embodiments of the present invention and is not intended to limit the scope of the present invention in any way. Any changes or modifications made by those skilled in the art based on the above disclosure shall fall within the protection scope of the claims.

Claims

1. A method for creating functional services, characterized in that, include: Configure the access interface of the functional module so that the functional module can be accessed, including: determining the access interface of the functional module according to the encapsulation interface of the functional module and configuring the access type and related setting parameters of the functional module; Obtain the module type and capability description information of the functional modules; Based on the module type and capability description information, construct a business capability relationship table corresponding to the functional modules; Use the business capability relationship table to create the functional business corresponding to the functional module.

2. The functional service creation method according to claim 1, characterized in that, The encapsulation interfaces include QSFP-DD, OSFP, CFP2, and SFP-DD interfaces. The access types include I2C and MDIO. The relevant setting parameters include access rate and access latency.

3. The functional service creation method according to claim 1, characterized in that, The method for obtaining the module type and capability description information of the functional modules includes: The module type of the functional module is confirmed by combining hardware packaging identification and protocol identification. Based on the module type of the functional module, load the corresponding module management protocol parser to parse the capability description information of the functional module.

4. The functional service creation method according to claim 3, characterized in that, The method for confirming the module type of a functional module by combining hardware packaging identification and protocol identification includes: Based on the encapsulation type of the physical port into which the functional module is inserted, determine the major encapsulation category of the functional module; Using the hardware signals corresponding to the package category, the presence information of the functional module and the related hardware pins are identified to initialize the module to an accessible state; The module type is determined by reading the identification field of the functional module through the protocol. The identification field includes one or more of the following: module type identifier, manufacturer name, model number, and serial number.

5. The functional service creation method according to claim 3, characterized in that, The module management protocol includes one of SFF-8472, SFF-8636, CMIS, and C-CMIS; the capability description information includes one or more of the following: supported rate level, number of channels, supported service type, and diagnostic monitoring capabilities.

6. The functional service creation method according to claim 1, characterized in that, The method for constructing a business capability relationship table corresponding to a functional module based on module type and capability description information includes: Based on the module type and capability description information, obtain the set of business types supported by the functional module; Construct a business capability relationship table containing a set of business types, using module type as the key.

7. The functional service creation method according to claim 6, characterized in that, The method for obtaining the set of business types supported by a functional module based on module type and capability description information includes: By using capability-business mapping rules, the set of business types supported by the functional module is derived, wherein the capability-business mapping rules map to the executable business types using the capability description information of the functional module as an index.

8. The functional service creation method according to claim 1, characterized in that, The business capability relationship table includes at least one of the following fields: module type identifier, protocol identifier, module capability summary, set of supported business types, and business parameter constraint field.

9. The method for creating functional services according to claim 1, characterized in that, The method for creating functional business corresponding to a functional module using a business capability relationship table includes: Using functional modules as the operation center, the business types supported by the functional modules are displayed in the business capability relationship table; Hide or gray out business types that are not in the business capability relationship table; Based on the supported business types, create the corresponding functional business for each functional module.

10. The method for creating functional services according to claim 1, characterized in that, The method for creating functional business corresponding to a functional module using a business capability relationship table also includes: When a user triggers a business type that a functional module does not support via an unconventional path, a preliminary check is performed based on the business capability relationship table to prevent the creation of the business function and to indicate the business types that the functional module supports.

11. A functional service creation system, used to implement the functional service creation method as described in any one of claims 1 to 10, characterized in that, The functional business creation system includes: The function configuration module is used to configure the access interface of the function module so that the function module can be accessed; The information acquisition module is used to acquire information about the module type and capability description of the functional modules. The form building module is used to build a business capability relationship table corresponding to the functional modules based on the module type and capability description information; The business creation module is used to create functional business corresponding to a functional module by utilizing the business capability relationship table.

12. An electronic device, characterized in that, It includes a memory, a processor, and an executable program stored in the memory and capable of being run by the processor; when the processor runs the executable program, it performs the functional service creation method as described in any one of claims 1 to 10.

13. A computer storage medium, characterized in that, The computer storage medium stores an executable program; when the executable program is executed, it implements the functional service creation method as described in any one of claims 1 to 10.

Images