CN112887389B - Version-based equipment interoperation method, system, device and storage medium - Google Patents
Version-based equipment interoperation method, system, device and storage medium Download PDFInfo
- Publication number
- CN112887389B CN112887389B CN202110074235.5A CN202110074235A CN112887389B CN 112887389 B CN112887389 B CN 112887389B CN 202110074235 A CN202110074235 A CN 202110074235A CN 112887389 B CN112887389 B CN 112887389B
- Authority
- CN
- China
- Prior art keywords
- version
- interoperation
- format
- target
- supportable
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a version-based equipment interoperation method, a version-based equipment interoperation system, a version-based equipment interoperation device and a version-based equipment interoperation storage medium, wherein the version-based equipment interoperation method comprises the following steps: acquiring a target service type; obtaining an interoperation request format and a version number; obtaining supportable service types and supportable service versions of target equipment; acquiring a corresponding interoperation request format according to the target service type, the version number, the supportable service type and the supportable service version; and initiating an operation request to the target equipment according to the interoperation request format. The invention has the technical effects that: by exchanging the capability information between the source device initiating the interoperation and the destination device, the version number of each capability is obtained, so that the source device can identify the version of the service provided by the destination device, and a correct interoperation request is dynamically sent.
Description
Technical Field
The invention relates to the field of Internet of things, in particular to a version-based equipment interoperation method, system, device and storage medium.
Background
The rapid development of the internet of things enables more and more devices in an IoT network and the requirement for interoperation among the devices to be stronger and stronger, and the interoperation is communicated through an "interoperation command". Along with the iteration of the IoT device software, the problem of updating the interoperation instructions also exists, and if any upgrade is not supposed to be performed on the interoperation instructions, it is likely to happen that in the same IoT network, the destination device is not matched with the interoperation instructions, for example, two IoT destination devices of the same type caused by software design reasons have different interfaces for providing the same service due to different firmware versions.
Disclosure of Invention
In order to solve the above technical problems, the present invention provides a version-based device interoperation method, system, apparatus and storage medium, and the specific technical solution is as follows:
a version-based device interoperation method, comprising:
acquiring a target service type;
obtaining an interoperation request format and a version number;
obtaining supportable service types and supportable service versions of target equipment;
acquiring a corresponding interoperation request format according to the target service type, the version number, the supportable service type and the supportable service version;
and initiating an operation request to the target equipment according to the interoperation request format.
Preferably, the obtaining of the format and version number of the interoperation request specifically includes:
the source equipment initiates a service request to the server according to the target service type so as to obtain a format version relation table of the server;
and the source equipment updates the format version relation table of the source equipment according to the format version relation table of the server.
Preferably, the obtaining of the supportable service type and the supportable service version of the target device specifically includes:
the source equipment acquires an interoperable capacity set from the target equipment; the interoperable capability includes a supportable service type of the target device and a corresponding supportable service version.
Preferably, the obtaining of the corresponding interoperation request format according to the target service type, the version number, the supportable service type, and the supportable service version specifically includes:
and judging whether the target equipment supports the target service type or not according to the interoperable capability set, if so, acquiring the interoperable request format from the source equipment format version relation table according to the target service type and the supportable service version.
In another aspect, there is provided a version-based device interoperation system including:
the format acquisition module is used for acquiring the format and the version number of the interoperation request;
the supportable obtaining module is used for obtaining the supportable service type and the supportable service version of the target equipment;
an interoperability request format obtaining module, configured to obtain a corresponding interoperability request format according to the target service type, the version number, the supportable service type, and the supportable service version;
and the operation request module is used for initiating an operation request to the target equipment according to the interoperation request format.
Preferably, the format obtaining module specifically includes:
the format version relation table acquisition module is used for initiating a service request to the server according to the target service type so as to acquire a format version relation table of the server;
and the format version relation table updating module updates the source equipment format version relation table according to the server format version relation table.
Preferably, the supportable obtaining module specifically includes:
a capability set obtaining module, configured to obtain an interoperable capability set from the target device; the interoperable capability includes a supportable service type of the target device and a corresponding supportable service version.
Preferably, the interoperation request format obtaining module specifically includes:
and judging whether the target equipment supports the target service type or not according to the interoperable capability set, if so, acquiring the interoperable request format from the source equipment format version relation table according to the target service type and the supportable service version.
In another aspect, an electronic apparatus is provided, which includes a processor, a memory, and a computer program stored in the memory and executable on the processor, and the processor is configured to execute the computer program stored in the memory, so as to implement the version-based device interoperation method.
In another aspect, a storage medium is provided having at least one instruction stored therein, the instruction being loaded and executed by a processor to implement the version-based device interoperation method.
The invention at least comprises the following technical effects:
(1) The method comprises the steps that capability information is exchanged between source equipment initiating interoperation and target equipment, and the version number of each capability is obtained, so that the source equipment can identify the version of a service provided by the target equipment, and a correct interoperation request is dynamically sent;
(2) And constructing a corresponding interoperation request through a data format corresponding to the prefabricated interoperation capability version, wherein the interoperation request can be updated in a mode of equipment upgrading or cloud pushing and the like, so that the system can be updated in time.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
FIG. 1 is a schematic flow chart of example 1 of the present invention;
FIG. 2 is a schematic flow chart of example 2 of the present invention;
fig. 3 is a schematic diagram of the actual operation of the present invention.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. However, it will be apparent to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
For the sake of simplicity, the drawings only schematically show the parts relevant to the present invention, and they do not represent the actual structure as a product. In addition, in order to make the drawings concise and understandable, components having the same structure or function in some of the drawings are only schematically depicted, or only one of them is labeled. In this document, "one" means not only "only one" but also a case of "more than one".
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items and includes such combinations.
In addition, in the description of the present application, the terms "first," "second," and the like are used only for distinguishing the description, and are not intended to indicate or imply relative importance.
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following description will be made with reference to the accompanying drawings. It is obvious that the drawings in the following description are only some examples of the invention, and that for a person skilled in the art, without inventive effort, other drawings and embodiments can be derived from them.
Example 1:
as shown in fig. 1, the present embodiment provides a version-based device interoperation method, including:
s1: acquiring a target service type;
s2: obtaining an interoperation request format and a version number;
s3: obtaining supportable service types and supportable service versions of target equipment;
s4: acquiring a corresponding interoperation request format according to the target service type, the version number, the supportable service type and the supportable service version;
s5: and initiating an operation request to the target equipment according to the interoperation request format.
The rapid development of the internet of things enables more and more devices in an IoT network and the requirement for interoperation among the devices to be stronger and stronger, and the interoperation is communicated through an "interoperation command". Along with the iteration of the IoT device software, the problem of updating the interoperation instructions also exists, and if any upgrade is not supposed to be performed on the interoperation instructions, it is likely to happen that in the same IoT network, the target device and the interoperation instructions are not matched, for example, two IoT target devices of the same type caused by software design reasons have different interfaces for providing the same service due to different firmware versions.
In order to solve the above technical problem, conventionally, a capability set mode is generally adopted, and a device capability set is used to indicate whether the device can provide a certain service, for example, a field support _ disk exists in the device capability set to indicate whether storage formatting is supported, if the field support _ disk is 0, that is, not supported, and if the field support _ disk is 1, that is, supported.
However, in the actual using process, it cannot be simply performed through 0,1, in the actual operating process, for example, whether to support the storage format or not, it is not possible to simply perform only the difference of 0,1, and it may also be possible to perform the difference of which formatting method, etc., and if simply perform the difference through 0,1, because of insufficient enumeration amount, it is necessary to increase the fields to achieve the corresponding effect, which results in an increasingly large capability set, and further results in an excessively large number of final fields.
In this embodiment, a version number is used to establish a correlation between an interoperation request format of a service and a device, and a source device initiating interoperation exchanges capability information with a target device to obtain a version number of each capability, so that the source device can identify a version of a service provided by the target device, and then send a correct interoperation request to implement a corresponding operation.
The invention exchanges the capability information with the destination device by the source device initiating the interoperation to obtain the version number of each capability, so that the source device can identify the version of the service provided by the destination device, thereby dynamically sending a correct interoperation request.
Example 2:
as shown in fig. 2, the present embodiment provides a version-based device interoperation method, including:
s1: acquiring a target service type;
s2-1: the source equipment initiates a service request to the server according to the target service type so as to obtain a format version relation table of the server;
s2-2: and the source equipment updates the format version relation table of the source equipment according to the format version relation table of the server.
S3-1: the source equipment acquires an interoperable capacity set from the target equipment; the interoperable capability comprises a supportable service type of the target equipment and a corresponding supportable service version;
s4-1: judging whether the target equipment supports the target service type or not according to the interoperable capability set, if so, acquiring the interoperable request format from the source equipment format version relation table according to the target service type and the supportable service version;
s5: and initiating an operation request to the target equipment according to the interoperation request format.
In this embodiment, specifically, a data format and a corresponding version of a service that the source device needs to maintain interested in are first obtained, and these correspondence relationships may be placed in a cloud or in an upgrade firmware of the source device. The corresponding relation is generally set in the cloud, in specific implementation, a source device stores a default interoperation request format and version relation table in general firmware according to needs, an old corresponding relation table is used all the time without updating, and a new corresponding relation table is pushed by the cloud or pulled from the cloud at regular time and updated; before sending an interoperation request, a source device needs to know the service supported by a target device and the version of the service interested by the source device; the method comprises the steps that a source device obtains an interoperable capability set from a target device, each capability in the capability set represents services supported by the target device, and the services are provided with version information; the source device obtains the interested service and the version thereof, and then compares the interoperation request format and the version corresponding relation table which are stored in the source device and supported by the source device, so as to obtain the interoperation request format of the service supported by the target device; finally, the source device constructs and sends different interoperation requests according to the capability versions of different devices, and the corresponding target device replies the interoperation response, namely, the interoperation of the source device and the target devices with different versions on the same service is completed.
According to the embodiment, the problem of resource consumption caused by the problem of frequently tracking version synchronization of the source equipment, the destination equipment and the mobile phone App when a plurality of interoperation equipment in the IoT network are provided is solved by updating and acquiring the format version relation table;
meanwhile, the problem that the interoperation versions are asynchronous because the software automatic update is not started for each device and the software cannot be updated immediately after the devices off-line for a long time are on-line again is solved, and even some low-power-consumption IoT devices do not have the OTA (over the air) upgrading function but issue various software and hardware versions of the same type of devices, so that inconvenience in operation is brought.
Example 3:
as shown in fig. 3, the present embodiment provides a version-based device interoperation system, including:
the format acquisition module is used for acquiring the format and the version number of the interoperation request;
the supportable obtaining module is used for obtaining the supportable service type and the supportable service version of the target equipment;
an interoperation request format obtaining module, configured to obtain a corresponding interoperation request format according to the target service type, the version number, the supportable service type, and the supportable service version;
and the operation request module is used for initiating an operation request to the target equipment according to the interoperation request format.
With the rapid development of the internet of things, more and more devices are provided in an IoT network, and the requirement for interoperation between the devices is stronger and stronger, and the interoperation is performed through "interoperation instructions". Along with the iteration of the IoT device software, the problem of updating the interoperation instructions also exists, and if any upgrade is not supposed to be performed on the interoperation instructions, it is likely to happen that in the same IoT network, the target device and the interoperation instructions are not matched, for example, two IoT target devices of the same type caused by software design reasons have different interfaces for providing the same service due to different firmware versions.
In order to solve the above technical problem, conventionally, a capability set manner is generally adopted, and a device capability set is used to indicate whether the device can provide a certain service, for example, a field support _ disk exists in the device capability set to indicate whether storage formatting is supported, if so, that indicates that the device is not supported, and if so, that indicates that the device is supported.
However, in the actual using process, it cannot be simply performed through 0,1, in the actual operating process, for example, whether to support the storage format or not, it is not possible to simply perform only the difference of 0,1, and it may also be possible to perform the difference of which formatting method, etc., and if simply perform the difference through 0,1, because of insufficient enumeration amount, it is necessary to increase the fields to achieve the corresponding effect, which results in an increasingly large capability set, and further results in an excessively large number of final fields.
In this embodiment, a version number is used to establish a correlation between an interoperation request format of a service and a device, and specifically, a source device initiating interoperation exchanges capability information with a target device to obtain a version number of each capability, so that the source device can identify a version of a service provided by the target device, and then send a correct interoperation request to implement a corresponding operation.
Example 4:
as shown in fig. 3, in this embodiment, based on embodiment 3, the format obtaining module specifically includes: the format version relation table acquisition module is used for initiating a service request to the server according to the target service type so as to acquire a format version relation table of the server; and the format version relation table updating module updates the source equipment format version relation table according to the server format version relation table.
The supportable acquisition module specifically comprises: a capability set obtaining module, configured to obtain an interoperable capability set from the target device; the interoperable capability includes a supportable service type of the target device and a corresponding supportable service version.
The interoperation request format obtaining module specifically includes: and judging whether the target equipment supports the target service type or not according to the interoperable capability set, if so, acquiring the interoperable request format from the source equipment format version relation table according to the target service type and the supportable service version.
In this embodiment, specifically, a data format and a corresponding version of a service that the source device needs to maintain interested in are first obtained, and these correspondence relationships may be placed in a cloud or in an upgrade firmware of the source device. The corresponding relation is generally set in the cloud, in the specific implementation, a source device stores a default interoperation request format and a version relation table in general firmware according to needs, the old corresponding relation table is used all the time without updating, and a new corresponding relation table is pushed by the cloud or pulled from the cloud at regular time and updated; before sending an interoperation request, a source device needs to know the service supported by a target device and the version of the service interested by the source device; the method comprises the steps that a source device obtains an interoperable capability set from a target device, each capability in the capability set represents services supported by the target device, and the services are provided with version information; the source device obtains the interested service and the version thereof, and then compares the interoperation request format and the version corresponding relation table which are stored in the source device and supported by the source device, so as to obtain the interoperation request format of the service supported by the target device; finally, the source device constructs and sends different interoperation requests according to the capability versions of different devices, and the corresponding target device replies the interoperation response, namely, the interoperation of the source device and the target devices with different versions on the same service is completed.
Example 5:
this embodiment provides an electronic apparatus, which includes a processor, a memory, and a computer program stored in the memory and executable on the processor, where the processor is configured to execute the computer program stored in the memory, and implement the version-based device interoperation method described in embodiment 1 or 2.
The device can be a desktop computer, a notebook, a palm computer, a tablet computer, a mobile phone, a man-machine interaction screen and the like. The apparatus may include, but is not limited to, a processor, a memory. Those skilled in the art will appreciate that the device is merely an example of a device and is not meant to be limiting, and may include more or fewer components than those shown, or some components may be combined, or different components, and that: the device may also include input/output interfaces, display devices, network access devices, communication buses, communication interfaces, and the like. A communication interface and a communication bus, and may further comprise an input/output interface, wherein the processor, the memory, the input/output interface and the communication interface complete communication with each other through the communication bus. The memory stores a computer program, and the processor is configured to execute the computer program stored in the memory to implement the method in the above embodiment.
The Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory may be an internal storage unit of the device, exemplary: hard disk or memory of the device. The memory may also be an external storage device of the device, for example: the equipment comprises a plug-in hard disk, an intelligent memory Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) and the like. Further, the memory may also include both internal storage units of the device and external storage devices. The memory is used for storing the computer program and other programs and data required by the device. The memory may also be used to temporarily store data that has been output or is to be output.
A communication bus is a circuit that connects the described elements and enables transmission between the elements. Illustratively, the processor receives commands from other elements via the communication bus, decrypts the received commands, and performs calculations or data processing based on the decrypted commands. The memory may include program modules, illustratively, a kernel (kernel), middleware (middleware), an Application Programming Interface (API), and applications. The program modules may be comprised of software, firmware or hardware, or at least two of the same. The input/output interface forwards commands or data input by a user via the input/output interface (e.g., sensor, keypad, touch screen). The communication interface connects the device with other network devices, user equipment, networks. Illustratively, the communication interface may be connected to the network by wire or wirelessly to connect to external other network devices or user devices. The wireless communication may include at least one of: wireless fidelity (WiFi), bluetooth (BT), near Field Communication (NFC), global Positioning Satellite (GPS) and cellular communications, among others. The wired communication may include at least one of: universal Serial Bus (USB), high-definition multimedia interface (HDMI), asynchronous transfer standard interface (RS-232), and the like. The network may be a telecommunications network and a communications network. The communication network may be a computer network, the internet of things, a telephone network. The device may connect to the network through the communication interface, and a protocol by which the device communicates with other network devices may be supported by at least one of an application, an Application Programming Interface (API), middleware, a kernel, and a communication interface.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/device and method may be implemented in other ways. The above-described apparatus/device embodiments are merely exemplary, and the division of the modules or units is merely an example of a logical division, and there may be other divisions in actual implementation, and it is exemplary that a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may also be implemented in the form of a software functional unit.
The integrated modules/units may be stored in a medium if implemented in the form of software functional units and sold or used as separate products. Based on such understanding, all or part of the flow in the method according to the above embodiments may be implemented by sending instructions to relevant hardware through a computer program, where the computer program may be stored in a medium, and when the computer program is executed by a processor, the steps of the above method embodiments may be implemented. Wherein the computer program may be in source code form, object code form, an executable file or some intermediate form, etc. The medium may include: any entity or device capable of carrying the computer program, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, read-Only Memory (ROM), random Access Memory (RAM), electrical carrier wave signal, telecommunication signal, software distribution medium, etc. It should be noted that the content contained in the medium can be increased or decreased as appropriate according to the requirements of legislation and patent practice in the jurisdiction, and the following are exemplary: in some jurisdictions, in accordance with legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunications signals. It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of program modules is illustrated, and in practical applications, the above-described distribution of functions may be performed by different program modules, that is, the internal structure of the apparatus may be divided into different program units or modules to perform all or part of the above-described functions. Each program module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one processing unit, and the integrated unit may be implemented in a form of hardware, or may be implemented in a form of software program unit. In addition, the specific names of the program modules are only used for distinguishing the program modules from one another, and are not used for limiting the protection scope of the application.
Example 6:
this embodiment provides a storage medium, where at least one instruction is stored, and the instruction is loaded and executed by a processor to implement the version-based device interoperation method described in embodiment 1 or 2.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including the preferred embodiment and all changes and modifications that fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (6)
1. A version-based device interoperation method, comprising:
acquiring a target service type;
obtaining an interoperation request format and a version number;
obtaining supportable service types and supportable service versions of target equipment;
acquiring a corresponding interoperation request format according to the target service type, the version number, the supportable service type and the supportable service version;
initiating an operation request to the target equipment according to the interoperation request format;
the obtaining of the format and version number of the interoperation request specifically includes:
the source equipment initiates a service request to the server according to the target service type so as to obtain a format version relation table of the server;
the source equipment updates a source equipment format version relation table according to the server format version relation table;
the obtaining of the supportable service type and the supportable service version of the target device specifically includes:
the source equipment acquires an interoperable capacity set from the target equipment; the interoperable capability includes a supportable service type of the target device and a corresponding supportable service version.
2. The version-based device interoperation method according to claim 1, wherein obtaining a corresponding interoperation request format according to the target service type, the version number, the supportable service type, and the supportable service version specifically comprises:
and judging whether the target equipment supports the target service type or not according to the interoperable capability set, if so, acquiring the interoperable request format from the source equipment format version relation table according to the target service type and the supportable service version.
3. A version-based device interoperation system, comprising:
the format acquisition module is used for acquiring the format and the version number of the interoperation request;
the supportable obtaining module is used for obtaining the supportable service type and the supportable service version of the target equipment;
an interoperation request format obtaining module, configured to obtain a corresponding interoperation request format according to a target service type, the version number, the supportable service type, and the supportable service version;
an operation request module, configured to initiate an operation request to the target device according to the interoperation request format;
the format obtaining module specifically comprises:
the format version relation table acquisition module is used for initiating a service request to the server according to the target service type so as to acquire a format version relation table of the server;
the format version relation table updating module updates a source equipment format version relation table according to the server format version relation table;
the supportable acquisition module specifically comprises: a capability set acquiring module, configured to acquire an interoperable capability set from the target device; the interoperable capability includes a supportable service type of the target device and a corresponding supportable service version.
4. The version-based device interoperation system according to claim 3, wherein the interoperation request format obtaining module specifically includes:
and judging whether the target equipment supports the target service type or not according to the interoperable capability set, if so, acquiring the interoperable request format from the source equipment format version relation table according to the target service type and the supportable service version.
5. An electronic apparatus comprising a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the processor is configured to execute the computer program stored in the memory to implement the version-based device interoperation method according to any one of claims 1 to 2.
6. A storage medium having stored therein at least one instruction that is loaded and executed by a processor to implement a version based device interoperation method according to any one of claims 1-2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110074235.5A CN112887389B (en) | 2021-01-20 | 2021-01-20 | Version-based equipment interoperation method, system, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110074235.5A CN112887389B (en) | 2021-01-20 | 2021-01-20 | Version-based equipment interoperation method, system, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112887389A CN112887389A (en) | 2021-06-01 |
| CN112887389B true CN112887389B (en) | 2022-12-23 |
Family
ID=76050444
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110074235.5A Active CN112887389B (en) | 2021-01-20 | 2021-01-20 | Version-based equipment interoperation method, system, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112887389B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111225018A (en) * | 2019-10-23 | 2020-06-02 | 上海艾融软件股份有限公司 | Request message processing method and device and electronic equipment |
| CN111666166A (en) * | 2020-06-03 | 2020-09-15 | 中国建设银行股份有限公司 | Service providing method, device, equipment and storage medium |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7370118B2 (en) * | 2004-02-04 | 2008-05-06 | International Business Machines Corporation | Methods, systems, and computer program products for dynamic inter-operability of nodes in service grids |
| CN101719162A (en) * | 2009-11-27 | 2010-06-02 | 武汉大学 | Multi-version open geographic information service access method and system based on fragment pattern matching |
| KR20130092281A (en) * | 2012-02-10 | 2013-08-20 | 삼성전자주식회사 | Method for updating the latest service category table in device and the device therefor |
| CN103780685A (en) * | 2014-01-10 | 2014-05-07 | 清华大学 | Method for adaptive data sharing among diversified intelligent equipment |
| US10397306B2 (en) * | 2015-12-22 | 2019-08-27 | American Express Travel Related Services Company, Inc. | System and method for translating versioned data service requests and responses |
| CN108366120A (en) * | 2018-02-13 | 2018-08-03 | 宁夏灵智科技有限公司 | A kind of internet-of-things terminal management method and device |
| US10686882B2 (en) * | 2018-05-18 | 2020-06-16 | Sap Se | Change management using a thing-model on an internet-of-things platform |
| CN111026408A (en) * | 2019-10-25 | 2020-04-17 | 上海商米科技集团股份有限公司 | Method and device for managing application and computer storage medium |
| CN110971614A (en) * | 2019-12-17 | 2020-04-07 | 软通动力信息技术（集团）有限公司 | Internet of things adaptation method and system, computer equipment and storage medium |
-
2021
- 2021-01-20 CN CN202110074235.5A patent/CN112887389B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111225018A (en) * | 2019-10-23 | 2020-06-02 | 上海艾融软件股份有限公司 | Request message processing method and device and electronic equipment |
| CN111666166A (en) * | 2020-06-03 | 2020-09-15 | 中国建设银行股份有限公司 | Service providing method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112887389A (en) | 2021-06-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102255887B (en) | Method and system for providing online services corresponding to multiple mobile devices | |
| US20230350872A1 (en) | Updating method of citation document, apparatus, electronic device and storage medium | |
| CN110209315B (en) | Method and device for displaying characters in user interface, electronic equipment and storage medium | |
| CN110909521B (en) | Online document information synchronous processing method and device and electronic equipment | |
| EP2320690A2 (en) | Interworking system between user terminal and smart card for executing widget, and method thereof | |
| CN112130475B (en) | Equipment control method, device, terminal and storage medium | |
| CN101626339A (en) | Method and system for downloading network data | |
| CN110619096A (en) | Method and apparatus for synchronizing data | |
| AU2016259289A1 (en) | Method and apparatus for managing content in a processing device | |
| US10078532B2 (en) | Resource management method and device for terminal system among multiple operating systems | |
| CN112887389B (en) | Version-based equipment interoperation method, system, device and storage medium | |
| CN115756544A (en) | Equipment updating method and device, electronic equipment and storage medium | |
| CN107743151B (en) | Content pushing method and device, mobile terminal and server | |
| CN114610366A (en) | Difference package upgrading method and system, intelligent electronic equipment and storage medium | |
| CN111290812B (en) | Display method, device, terminal and storage medium of application control | |
| CN111258810A (en) | Method, system, terminal equipment and storage medium for realizing data source switching | |
| CN112835962A (en) | Information display method and device, electronic equipment and storage medium | |
| CN106068506B (en) | Apparatus and method for increasing loading time in an electronic device | |
| CN112199132A (en) | Page layout method and device | |
| CN112685075A (en) | Gray scale distribution method and device, electronic equipment and computer readable medium | |
| CN113157365B (en) | Program running method, program running device, electronic equipment and computer readable medium | |
| KR101418038B1 (en) | Method and apparatus for providing web contents | |
| CN110099122B (en) | Method and apparatus for sending network request | |
| CN109086066B (en) | Application program updating method and device, computer equipment and storage medium | |
| CN113612676B (en) | Social group message synchronization method, device, equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |