CN107329762B - Method and system for describing and integrating software service - Google Patents
Method and system for describing and integrating software service Download PDFInfo
- Publication number
- CN107329762B CN107329762B CN201710525621.5A CN201710525621A CN107329762B CN 107329762 B CN107329762 B CN 107329762B CN 201710525621 A CN201710525621 A CN 201710525621A CN 107329762 B CN107329762 B CN 107329762B
- Authority
- CN
- China
- Prior art keywords
- modules
- module
- interface
- software
- driver
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention discloses a method and a system for describing and integrating software services, wherein the method comprises the steps of determining a plurality of software services to be integrated and a calling sequence among the plurality of software services; respectively packaging a plurality of software services into corresponding modules, drivers and logic processing through predefined module interfaces, driver interfaces and logic processing interfaces; generating a module chain from a plurality of modules through a module chain interface, and generating a configuration file of the module chain; when the software is applied, the configuration file is used for loading an external system, and the external system creates an instance of the module, the driver, the logic processing and the module chain according to the configuration file and runs the instance so as to realize corresponding software service. The embodiment of the invention can realize the consistent treatment of various function calls, particularly the consistent treatment of operating system calls, the consistent treatment of logic processing in hardware or software components, the consistent treatment of the same type of hardware or software components, the consistent treatment of different hardware or software components and the minimized development cost.
Description
Technical Field
Embodiments of the present invention relate to computer technologies, and in particular, to a method and system for describing and integrating software services.
Background
In software integration related development, the following problems are common:
(1) one or more types of hardware may be used to provide a business service. The same type of hardware may have multiple suppliers, and even the same supplier may have product lines formed by products with multiple specifications of the same type of hardware, which all provide approximately the same functions, although there are differences in specific standards, implementations, data formats, performance, configurations, unique functions, software calling interfaces (some of which may be related to the hardware and operating system on which they depend).
(2) The same class of software components that provide substantially the same functionality is similar to that described above, but may vary in implementation, data format, configuration, and invocation interface.
(3) Some providers offer a variety of services that need to be controlled uniformly, e.g. logged in, logged out, but which may be referenced in their entirety or only partially by different services.
(4) When custom development is performed for a client, a hardware or software provider may need to be changed on a certain basic version in consideration of factors such as cost and cooperation, and direct use of a calling interface provided by the provider usually results in more modifications to enable the hardware or software provider to be on-line again due to differences between the calling interface and the like used before.
(5) Some modifications are also typically incurred to migrate to a different operating system platform.
Therefore, based on the above problems, the time and cost of software integration development are greatly increased.
Disclosure of Invention
The invention provides a method and a system for describing and integrating software services, which can reduce the time and cost of software integration development.
In a first aspect, an embodiment of the present invention provides a method for describing and integrating software services, including:
determining a plurality of software services to be integrated and a calling sequence among the plurality of software services;
respectively packaging the plurality of software services into corresponding modules, drivers and logic processing through predefined module interfaces, driver interfaces and logic processing interfaces;
generating a module chain from the modules through a module chain interface, and generating a configuration file of the module chain;
when the software is applied, the configuration file is used for loading an external system, the external system creates an instance of the module, the driver, the logic processing and the module chain according to the configuration file, and the instance is operated so as to realize corresponding software service.
In a second aspect, an embodiment of the present invention provides a system for describing and integrating software services, including:
a module interface that is an abstraction of a hardware or software component, partitioned into drive-related components and drive-unrelated components to describe specifications of the component, wherein the drive-unrelated components include attributes, functions and processing logic;
a driver interface for packaging the product characteristics of the supplier and the components related to the operating system, for managing the bottom driver packaging example, or for uniformly controlling a plurality of services;
a logic processing interface which is a unified interface of logic processing and is used for realizing various data processing in the plurality of modules;
and the module chain interface is used for managing modules with data transmission processing logical relation among the modules, describing and solidifying the transmission and calling sequence of data and control among the modules, and connecting the modules in series according to the form of a linked list.
The embodiment of the invention realizes that various function calls are treated in a consistent way, particularly the operating system calls are treated in a consistent way, the logic processing in hardware or software components is treated in a consistent way, the same type of hardware or software components are treated in a consistent way, and different hardware or software components are treated in a consistent way by pre-packaging and defining the module interface, the driving interface, the logic processing interface and the module link interface, and can completely solve the problems in the prior art, thereby minimizing the time and the cost of related development.
Drawings
FIG. 1 is a flow chart of a method for describing and integrating software services in accordance with a first embodiment of the present invention;
fig. 2 is a block diagram of a system for describing and integrating software services according to a second embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a flowchart of a method for describing and integrating software services according to an embodiment of the present invention, as shown in the figure, the method specifically includes the following steps:
s101, determining a plurality of software services to be integrated and a calling sequence among the plurality of software services;
s102, respectively packaging the plurality of software services into corresponding modules, drivers and logic processing through predefined module interfaces, driver interfaces and logic processing interfaces;
s103, generating a module chain from the modules through module chain interfaces, and generating a configuration file of the module chain;
and the external system creates an instance of the module, the driver, the logic processing and the module chain according to the configuration file and runs the instance so as to realize corresponding software service.
Specifically, a plurality of software services may constitute a service, where the service may refer to services related in different industries and different fields, such as balance inquiry and card swiping and account transfer in the banking field; queuing and appointment physical examination in the medical field; check-in, empty room inquiry and the like in the hotel field. Each service comprises at least one service state, each service state can comprise one or more different services, and the states and the switching among the states form a set of service processes.
Here, the operation of inquiring balance of bank card provided by the service robot in bank hall is taken as an example for explanation, and the robot is provided with the infrastructure such as display, touch screen, all-in-one bank card reader, password keyboard and network, etc. for completing the operation.
When a user needs to perform balance inquiry, the following operations are required under normal conditions, namely a business process:
(1) and entering a balance inquiry UI through voice interaction or point touch on a touch screen.
(2) And the bank card is inserted according to voice or indication lamp prompt.
(3) And prompting to input the password according to voice or an indicator light.
(4) And submitting a balance inquiring transaction request.
(5) And after the balance is inquired, taking the bank card away.
Accordingly, the robot should accomplish the following:
(0) and a designated area in front of the video monitoring robot.
(1) And switching to a UI (user interface) for inquiring balance of the bank card. Initializing a card reader, a password keyboard and the like, informing a background if the initialization fails, and prompting a user.
(2) The card reader tries to read the information in the bank card, if the information is successful, part of the information is extracted and is processed and then presented to a user or stored for later use; otherwise, the background is informed and the user is prompted.
(3) The password keyboard tries to acquire the password input by the user, if the password input by the user succeeds, part of information is extracted, processed and presented to the user or stored for later use; otherwise, the background is informed and the user is prompted.
(4) And packaging necessary terminal information, stored bank card information, passwords and transaction types (balance inquiry) into a service request, and sending the service request to a transaction background to wait for a result. And after the result is taken, presenting the result to the user.
(5) And after the balance is inquired, the card reader pops up the bank card and prompts the user to take the bank card away.
(6) The UI switches to the home page.
Then in the above example, the touch screen, the bank card reader or the password keypad, etc., all provide the corresponding software service. In the process of implementing one business process, different software services need to be described and implemented, and the calling sequence among a plurality of software services is determined according to the business process.
The module interface, the drive interface, the logic processing interface and the module link interface are packaged and defined in advance and used for uniformly treating various function calls, particularly uniformly treating operating system calls, uniformly treating logic processing in hardware or software components, uniformly treating the same type of hardware or software components and uniformly treating different hardware or software components. These interfaces are described in detail below:
1. module interface
A module interface is an abstraction of a hardware or software component through which multiple software service wrappers may be implemented as corresponding modules.
Specifically, according to different requirements of the component, a module interface (ModuleInterface) can be divided into a component related to a driver and a component unrelated to the driver to describe the specification of the component, which can be regarded as a basic computing unit inside the system. The above-mentioned drive-related components are implemented by associating a drive interface (DriverInterface), but for some software components, the former may not be needed; the drive-independent components include properties, functions, and processing logic, where the properties are accessed through GetProperty and SetProperty in the base class interface (BaseInterface), and initial property values are specified in the configuration file; the function is accessed through a configuration function Ioctl (Ioctl is the short hand of I/O Control and is a function provided in the Control interface) in another base class interface (Control interface), and lists a function set of the component visible to the outside in a configuration file; processing logic is implemented by associated 2 logic processing queues (CallbackQueue) (PrevCallbackQueue and nextcackqueue), and can implement logic processing (Callback) for processing no input, input data or multiple types of input data and no output, output data or multiple types of output data for a Module (Module), each Module adds Callback to its PrevCallbackQueue according to its own processing logic and sets nextcalback of an upstream Module if any; NextCallbackQueue is used to call downstream modules in the Module chain (ModuleLink). In this way, the external system can create the relevant modules in a factory-like consistent manner, and access the homogeneous software product functions and/or services of the various vendors in a consistent manner. Modules can be classified into Source (as the most upstream module in a ModuleLink), Destination (as the tail end module in a ModuleLink), Transform (not the most upstream and not the tail end module), and Repeater (a module for monitoring other modules).
The Module may be implemented as a plug-in that, when released, provides an instance profile template, such as a Module profile in xml.
The ModuleInterface providing basic attributes comprises:
the roles played in the module chain (source, switch, destination, repeater),
the type of the I/O data,
a dispenser is provided for dispensing the liquid to the container,
the maximum length/prefix length/number of buffers,
whether the downstream module modifies the data when sharing the allocator,
the maximum number of modules that can be processed synchronously.
The following methods are provided:
open, Open;
close, Close;
AddCallback, add the logic and process the call-back function;
RemoveCallback, delete logical process callback function.
2. Module chain interface
The module chain interface is used for managing modules with data transmission processing logical relation, describing and solidifying the transmission and calling sequence of data and control among the modules, and connecting the modules in series according to the form of a linked list. Generating a module chain from the plurality of modules according to a module chain interface.
Specifically, the input data type of the downstream module should be matched with the output data type of the upstream module, the Repeater module is inserted after the module needing monitoring, and the Repeater module sends the monitoring result to the external system for comprehensive analysis and processing, so that the upper layer can be unified to form the service capability. In particular, a module chain may contain only one module. This enables the integration of several services offered by several suppliers, the management and access of the various modules being possible in a completely consistent way and the integration being obviously multiplexed.
Similarly, an instance profile template, e.g., in the form of xml, should be provided when the module chain is released for configuring the execution logic and basic configuration information between modules. When the software is applied, the configuration file is used for loading an external system, the external system creates an instance of the module, the driver, the logic processing and the module chain according to the configuration file, and the instance is operated so as to realize corresponding software service.
The ModulLinkInterface provides basic attributes including:
intrinsic;
autorun, Run immediately after Open in initialization;
depth, chain Depth.
The following methods are provided:
AddModule, add modules to the chain of modules;
removeModule, removing modules from the chain of modules by module name;
findsoduleByName, searching a module from the module chain according to the module name;
and finding the module from the module chain according to the module type by the FindModuleByType.
3. Drive interface
The driver interface is used to package the vendor's product features and operating system related components, to manage the underlying driver package instance, or to control the unified control of multiple services.
The OsHal (OS and hard Abstract layer) component can be called by a driving interface (DriverInterface), the product characteristics of a packaging supplier and components related to an operating system, the characteristics of a function calling interface and the uniform control of a plurality of services are placed in a configuration file for description and are realized in a specific example, and therefore the difference of Hardware, the operating system and the software specification is shielded. The OsHal is a hardware abstraction layer of an external system, realizes the abstraction of an operating system and hardware through open source libraries such as standard C + + and boost, and supports mainstream operating system platforms such as Linux/Windows/Android.
The driver interface is implemented as a plug-in, which should provide an instance profile template at the time of release, e.g., a driver instance profile in the form of xml.
Specifically, the driverInterface can provide basic attributes including:
information, drive Information;
OnRead, read callback function;
OnWrite, write callback function;
protocol, Protocol required.
Meanwhile, the following methods may be provided:
read, reading data from the bottom drive;
write, writing data into the underlying drive;
ioctl, I/O control, such as configuring parameters to drive, reading status, etc.;
open, opening the bottom layer drive according to the input parameters;
close, turn off the underlying drive according to the input parameters.
Implementing the driving according to the driverInterface may employ the following steps:
(1) the functions and/or services that may be used by the software products are collected and categorized into collective public, partially public, unique, and related data formats, as well as basic information of the software products such as description, provider, version number, and the like.
(2) For each same kind of software product of a supplier, a specific driving class for realizing the driverInterface is established.
(3) The basic information of the software product and the attribute acquisition or setting in the function and/or service are respectively realized in GetProperty/SetProperty, the acquisition corresponds to GetProperty, the setting corresponds to SetProperty, and the attribute needs to disclose the number and the data format.
(4) Of these functions and/or services, those used for initialization are implemented in Open; for the anti-initialization, is implemented in its Close.
(5) Of these functions and/or services, those used to Read data are implemented in their Read; for writing data, is implemented in its Write.
(6) Other functions and/or services, are implemented in its Ioctl, and various control commands and data formats are disclosed.
(7) When the related functions and/or services need to be referred to, an instance corresponding to the specific driver class is created and the related functions and/or services are called.
4. Logical processing interface
The logic processing interface is a unified interface of logic processing, and is used for realizing various data processing in the plurality of modules. Implemented as a plug-in, an instance profile template should be provided at the time of publication, e.g. a logical process instance profile in the form of xml.
CallbackInterface provides the following methods:
callback, calling back the implementation function of the interface;
the SetType sets the input and output data type of the callback;
GetType, acquiring the input and output data type of callback;
IsReady, whether callback processing is ready.
CallbackQueueInterface provides the following methods:
addCallback, add Callback to the queue;
RemoveCallback, removing the pointer to the CallbackInterface from the queue;
and FindCallback, acquiring the Callback matched with the Key, the first Callback or the next Callback according to the input parameters.
The embodiment of the invention realizes that various function calls are treated in a consistent way, particularly the operating system calls are treated in a consistent way, the logic processing in hardware or software components is treated in a consistent way, the same type of hardware or software components are treated in a consistent way, and different hardware or software components are treated in a consistent way by pre-packaging and defining the module interface, the driving interface, the logic processing interface and the module link interface, and can completely solve the problems in the prior art, thereby minimizing the time and the cost of related development.
Example two
Fig. 2 is a block diagram of a system for describing and integrating software services according to a second embodiment of the present invention, and as shown in fig. 2, the system according to the second embodiment of the present invention specifically includes:
a module interface that is an abstraction of a hardware or software component, partitioned into components related to a driver and components unrelated to the driver to describe a specification of the component, wherein the components unrelated to the driver include attributes, functions and processing logic;
a driver interface for packaging the product characteristics of the supplier and the components related to the operating system, for managing the bottom driver packaging example, or for uniformly controlling a plurality of services;
a logic processing interface which is a unified interface of logic processing and is used for realizing various data processing in the plurality of modules;
and the module chain interface is used for managing modules with data transmission processing logical relation among the modules, describing and solidifying the transmission and calling sequence of data and control among the modules, and connecting the modules in series according to the form of a linked list.
The system for describing and integrating software services provided by the embodiment of the invention can execute the method for describing and integrating software services provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (5)
1. A method of describing and integrating software services, comprising:
determining a plurality of software services to be integrated and a calling sequence among the plurality of software services;
respectively packaging the plurality of software services into corresponding modules, drivers and logic processing through predefined module interfaces, driver interfaces and logic processing interfaces;
generating a module chain from the modules through a module chain interface, and generating a configuration file of the module chain;
when the software is applied, the configuration file is used for loading an external system, the external system creates an instance of the module, the driver, the logic processing and the module chain according to the configuration file, and the instance is operated so as to realize corresponding software service;
the module interface is an abstraction of a hardware or software component, split into driver-related and driver-independent components to describe the specification of the component, where the driver-independent components include attributes, functions and processing logic.
2. The method of claim 1, wherein the driver interface is used to package vendor product characteristics and operating system related components, to manage underlying driver package instances, or to unify control over multiple services.
3. The method of claim 1, wherein the logical processing interface is a unified interface of logical processing for implementing various data processing in the plurality of modules.
4. The method of claim 1, wherein the module chain interface is configured to manage modules having a logical relationship with each other for data transmission processing, describe and solidify the transmission and calling order of data and control between the modules, and connect the modules in series in a linked list.
5. A system for describing and integrating software services, the system comprising:
a module interface that is an abstraction of a hardware or software component, partitioned into drive-related components and drive-unrelated components to describe specifications of the component, wherein the drive-unrelated components include attributes, functions and processing logic;
a driver interface for packaging the product characteristics of the supplier and the components related to the operating system, for managing the bottom driver packaging example, or for uniformly controlling a plurality of services;
a logic processing interface which is a unified interface of logic processing and is used for realizing various data processing in the plurality of modules;
and the module chain interface is used for managing modules with data transmission processing logical relation among the modules, describing and solidifying the transmission and calling sequence of data and control among the modules, and connecting the modules in series according to the form of a linked list.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710525621.5A CN107329762B (en) | 2017-06-30 | 2017-06-30 | Method and system for describing and integrating software service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710525621.5A CN107329762B (en) | 2017-06-30 | 2017-06-30 | Method and system for describing and integrating software service |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107329762A CN107329762A (en) | 2017-11-07 |
| CN107329762B true CN107329762B (en) | 2020-09-08 |
Family
ID=60199671
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710525621.5A Active CN107329762B (en) | 2017-06-30 | 2017-06-30 | Method and system for describing and integrating software service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107329762B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107809332A (en) * | 2017-11-10 | 2018-03-16 | 中国民生银行股份有限公司 | Compound interface configures and compound interface call method, device |
| CN109995817A (en) * | 2017-12-29 | 2019-07-09 | 中移信息技术有限公司 | A kind of service scheduling method and device |
| CN111258674B (en) * | 2020-01-14 | 2021-01-01 | 清华大学 | Software module integration system and operation method of numerical application program |
| CN111309387B (en) * | 2020-01-22 | 2023-04-18 | 阿里巴巴集团控股有限公司 | Method and device for loading drive, electronic equipment and storage medium |
| CN114567667B (en) * | 2022-03-04 | 2024-03-15 | 深圳前海环融联易信息科技服务有限公司 | Service processing assembly system based on responsibility chain design mode |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101799764A (en) * | 2009-12-31 | 2010-08-11 | 芯通科技（成都）有限公司 | Realization method of instrument module common port |
| CN102054219A (en) * | 2009-11-09 | 2011-05-11 | 通用汽车环球科技运作公司 | Product-line based content management system and method thereof |
| CN103455339A (en) * | 2012-05-29 | 2013-12-18 | 北京神州普惠科技股份有限公司 | Execution method of general simulation assemblies |
| CN103529821A (en) * | 2013-09-29 | 2014-01-22 | 重庆邮电大学 | Configurable method and device for diagnostic protocol stack system based on CAN (controller area network) bus |
| CN103677842A (en) * | 2013-12-18 | 2014-03-26 | 工业和信息化部电子第五研究所 | Software tool configuration type integrated expansion calling method and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160055263A1 (en) * | 2014-08-22 | 2016-02-25 | Successfactors, Inc. | Providing Action Search and Quick Action Cards |
-
2017
- 2017-06-30 CN CN201710525621.5A patent/CN107329762B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102054219A (en) * | 2009-11-09 | 2011-05-11 | 通用汽车环球科技运作公司 | Product-line based content management system and method thereof |
| CN101799764A (en) * | 2009-12-31 | 2010-08-11 | 芯通科技（成都）有限公司 | Realization method of instrument module common port |
| CN103455339A (en) * | 2012-05-29 | 2013-12-18 | 北京神州普惠科技股份有限公司 | Execution method of general simulation assemblies |
| CN103529821A (en) * | 2013-09-29 | 2014-01-22 | 重庆邮电大学 | Configurable method and device for diagnostic protocol stack system based on CAN (controller area network) bus |
| CN103677842A (en) * | 2013-12-18 | 2014-03-26 | 工业和信息化部电子第五研究所 | Software tool configuration type integrated expansion calling method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107329762A (en) | 2017-11-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107329762B (en) | Method and system for describing and integrating software service | |
| CN111279321B (en) | Binding backend service endpoints to API functions in an API registry | |
| US9110654B2 (en) | Dynamically building locale objects or subsections of locale objects based on historical data | |
| US6003094A (en) | Generic Java Gateway for connecting a client to a transaction processing system | |
| US7756751B2 (en) | Architecture for business process integration | |
| US20070050751A1 (en) | Automatic interoperation with legacy POS service and control objects | |
| US20170329659A1 (en) | Linux system-based cen/xfs standard architecture and implementation method | |
| US20210397604A1 (en) | Computerized implementation framework to abstract data object definitions across multiple computing environments | |
| EP1906305B1 (en) | Method and system for data preparation and communication between software applications | |
| WO2008037662A2 (en) | Generic sequencing service for business integration | |
| CN111026367A (en) | Micro-service arranging method and device, terminal equipment and storage medium | |
| CN106796521B (en) | API version control independent of product release | |
| US9141353B2 (en) | Dynamically building locale objects at run-time | |
| CN114661375A (en) | Application integration method and device | |
| CN114489954A (en) | Tenant creation method based on virtualization platform, tenant access method and equipment | |
| US7739690B2 (en) | Meta-container for model-based distributed applications | |
| US10002007B2 (en) | Operating system (OS) independent device drivers | |
| US8745620B2 (en) | Software tool and method for updating a virtual appliance | |
| US20080098355A1 (en) | Integrated configuration of cross organizational business processes | |
| CN114579334A (en) | Communication method, communication device, electronic equipment and storage medium | |
| CN112667441A (en) | Service module scheduling method, system and storage medium based on fault-tolerant function | |
| US20090044203A1 (en) | Apparatus and Method for Generating Programming Interactions for a Computer Program from an Incoming Data Structure | |
| CN108804236B (en) | AIDL file sharing method and system | |
| CN111597784A (en) | Information sending method, device, terminal equipment and medium | |
| US10698746B1 (en) | Systems, methods and computer program products for controlling a field device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20190513 Address after: Room 109, Room No. 2, Tushan Yilang, East Huancheng Road, Shangcheng District, Hangzhou City, Zhejiang 310000 Applicant after: Zhejiang Fubao Intelligent Technology Co., Ltd. Address before: 201203 14 blocks 22301-1544, 498 Guoshoujing Road, Pudong New Area Free Trade Pilot Area, Shanghai Applicant before: SHANGHAI TANGDI INFORMATION TECHNOLOGY CO., LTD. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |