CN114168137A - Internet of things system and method adaptive to multiple platforms - Google Patents
Internet of things system and method adaptive to multiple platforms Download PDFInfo
- Publication number
- CN114168137A CN114168137A CN202111494862.0A CN202111494862A CN114168137A CN 114168137 A CN114168137 A CN 114168137A CN 202111494862 A CN202111494862 A CN 202111494862A CN 114168137 A CN114168137 A CN 114168137A
- Authority
- CN
- China
- Prior art keywords
- platform
- interface
- layer
- internet
- target
- 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.)
- Pending
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/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration 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)
- Computer Security & Cryptography (AREA)
- Human Computer Interaction (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the application discloses an Internet of things system and a method adaptive to multiple platforms, wherein a source code layer is used for storing source codes corresponding to the operation process of the Internet of things system. The interface layer is provided with platform interfaces adapted to different platform types. The functional layer is connected with the interface layer and used for forwarding the platform access request to the interface layer under the condition of receiving the platform access request. And the interface layer calls a corresponding target interface according to the target platform type pointed by the platform access request so as to realize the connection with the target platform corresponding to the target platform type. The functions required to be realized by the Internet of things system are hierarchically divided, so that independence among different functions is realized, and the system can be adapted to various platform types. If a new project or platform type needs to be adapted, only the work of developing an interface layer is needed, so that the development labor and development period are greatly shortened, and the difficulty of adapting to different system platforms by LWM2M is reduced.
Description
Technical Field
The application relates to the technical field of platform management, in particular to an Internet of things system and method adaptive to multiple platforms.
Background
LWM2M (Lightweight Machine to Machine) is an internet of things protocol that can be used primarily on resource-constrained embedded devices.
There are many platforms for current modular projects, such as the high-throughput X24, X55, X12, X65 platforms, the T750 platform of MTK (MediaTek), and so on. Each system platform differs, and to enable the interaction of LWM2M with the system platform, different configurations of LWM2M need to be performed for different system platforms. Maintenance of versions, labor costs can be significant if LWM2M certification requirements are developed for each system platform.
It can be seen that how to reduce the difficulty of adapting LWM2M to different system platforms is a problem to be solved by those skilled in the art.
Disclosure of Invention
The embodiment of the application aims to provide an Internet of things system and a method for adapting multiple platforms, which can reduce the difficulty of adapting LWM2M to different system platforms.
In order to solve the technical problem, an embodiment of the present application provides an internet of things system adapted to multiple platforms, including a source code layer, a functional layer, and an interface layer; the interface layer is provided with platform interfaces adaptive to different platform types;
the source code layer is used for storing source codes corresponding to the operation flow of the Internet of things system;
the functional layer is connected with the interface layer and used for forwarding the platform access request to the interface layer under the condition of receiving the platform access request;
and the interface layer is used for calling a corresponding target interface according to the target platform type pointed by the platform access request so as to realize the connection with the target platform corresponding to the target platform type.
Optionally, an adaptation layer is further included;
and the interface layer is connected with the adaptation layer and used for calling task processing logic matched with the system type from the adaptation layer based on the system type corresponding to the platform access request, so that the interaction with the target platform is realized through the target interface based on the task processing logic.
Optionally, in a case that the platform type is a high-pass platform, the interface layer is configured to configure parameters for the target platform and/or obtain data from the target platform in a QMI message manner.
Optionally, in a case that the platform type is an MTK platform, the interface layer is configured to configure parameters for the target platform and/or obtain data from the target platform in a JSON API message manner.
Optionally, the interface layer includes any combination of a device information interface, a dial-up interface, an APN configuration interface, a network information interface, a short message interface, an FOTA upgrade interface, a LOG print interface, a system time interface, and a backup interface.
Optionally, the functional layer is configured to add a corresponding service function in the functional layer when a function expansion instruction is received.
Optionally, the interface layer is configured to add a corresponding platform interface in the interface layer when a platform type extension instruction is received.
Optionally, the functional layers include objects layers, application layers, and generic layers;
the objects layer is used for providing a plurality of functional services for the Internet of things system;
the application layer is used for managing functions required by the operation of the Internet of things system;
the general layer is used for providing general functions of the Internet of things system.
Optionally, the common functions of the common layer include generating a linked list, storing data, and outputting data.
The embodiment of the application also provides a method for adapting to multiple platforms, which comprises the following steps:
under the condition of receiving a platform access request, forwarding the platform access request to an interface layer; the interface layer is provided with platform interfaces adaptive to different platform types;
and calling a corresponding target interface of the interface layer according to the target platform type pointed by the platform access request so as to realize the connection with the target platform corresponding to the target platform type.
According to the technical scheme, the multi-platform-adaptive Internet of things system comprises a source code layer, a functional layer and an interface layer; wherein, the interface layer is provided with platform interfaces adapted to different platform types. And the source code layer is used for storing source codes corresponding to the operation flow of the Internet of things system. The functional layer is connected with the interface layer and used for forwarding the platform access request to the interface layer under the condition of receiving the platform access request. In order to realize the adaptation to different platform types, a plurality of platform interfaces are arranged in an interface layer, and the interface layer can call a corresponding target interface according to the target platform type pointed by the platform access request so as to realize the connection with the target platform corresponding to the target platform type. In the technical scheme, the functions required to be realized by the Internet of things system are hierarchically divided, so that independence among different functions can be realized, and the system can be adapted to various platform types. Compared with the traditional mode, the whole framework version of the Internet of things system needs to be modified and adjusted when one platform type is adapted, the Internet of things system provided by the application adapts to different platform types through the interface layer, and the purpose that one framework version can be specific to a plurality of platform systems is achieved. And if a new project or platform type needs to be adapted, only the work of developing an interface layer is needed, so that the development labor and development period are greatly shortened, and the difficulty of adapting to different system platforms by LWM2M is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present application, the drawings needed for the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained by those skilled in the art without inventive effort.
Fig. 1 is a schematic structural diagram of an internet of things system adapted to multiple platforms according to an embodiment of the present application;
fig. 2 is a schematic diagram of a framework of an internet of things system adapted to multiple platforms according to an embodiment of the present application;
fig. 3 is a flowchart of a method for adapting multiple platforms according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without any creative effort belong to the protection scope of the present application.
The terms "including" and "having," and any variations thereof, in the description and claims of this application and the drawings described above, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may include other steps or elements not expressly listed.
In order that those skilled in the art will better understand the disclosure, the following detailed description will be given with reference to the accompanying drawings.
Next, a multi-platform-adaptive internet of things system provided in an embodiment of the present application is described in detail. Fig. 1 is a schematic structural diagram of an internet of things system adapted to multiple platforms according to an embodiment of the present application, where the system includes a source code layer 11, a functional layer 12, and an interface layer 13.
The internet of things system in the application can be a client based on LWM 2M.
In the embodiment of the application, the functions required to be realized by the internet of things system are hierarchically divided, so that independence between different functions can be realized, and the interface layer 13 for adapting to different platform types can be independently arranged.
And the source code layer 11 is used for storing source codes corresponding to the operation flow of the internet of things system.
The source code stored in the source code layer 11 belongs to an open source code, and is the same as the source code set in the conventional LWM2M, and is not described herein again.
The functional layer 12 is connected to the interface layer 13, and configured to forward the platform access request to the interface layer 13 when the platform access request is received.
The functional layer 12 is configured to provide basic functional services of the internet of things system, and may invoke relevant business functions according to current business requirements.
In the embodiment of the present application, the functional layer 12 may be further divided in detail according to the difference of the functions implemented by the functional layer 12, so as to facilitate the subsequent implementation of independent modification or adjustment of different functions.
In a particular implementation, the functional layer 12 may be divided into objects, application, and generic layers.
The object layer can provide multiple functional services for the internet of things system, including security object, server object, ac object, device object, contact monitor object, firmware object, location object, Connectivity status object, etc., and each object implements corresponding functions.
The application layer can be used for managing functions required by the operation of the internet of things system, is mainly responsible for an operation framework of lwm2m clients, and comprises modules for file system management, equipment state query, operation condition judgment, dialing control, lwm2m operator version configuration, socket management, data processing and the like.
The common layer can be used for providing common functions of the internet of things system. The general functions may include generating a linked list, storing data, and printing data.
For example, assuming that after the application layer executes the function of querying the device status, the queried device status information needs to be generated into a linked list, the function of generating the linked list of the general layer may be invoked, so as to obtain the linked list recorded with the device status information. Or if the inquired device status information needs to be output, the print data function of the general layer can be called, so that the device status information is output.
The functional layer 12 is mainly directed to functions required by the internet of things system and related functions in operation, and the functional layer 12 does not have a function of interacting with different platforms.
In the embodiment of the present application, the functions of interacting with different platforms may be separately divided into the interface layer 13. The interface layer 13 may call a corresponding target interface according to the target platform type to which the platform access request is directed, so as to implement connection with the target platform corresponding to the target platform type.
The interface layer 13 is provided with platform interfaces adapted to different platform types. Common platform types may include a high-pass platform and an MTK platform, and accordingly, the interface layer 13 may include a platform interface adapted to the high-pass platform and a platform interface adapted to the MTK platform.
The interface layer 13 is mainly used to adapt to different platforms, and perform parameter reading and platform configuration operations of the internet of things system. The data processing modes corresponding to different platform types are different. In a specific implementation, in the case that the platform type is a high-pass platform, the interface layer 13 may configure parameters for the target platform and/or obtain data from the target platform in a QMI message manner.
In the case that the platform type is the MTK platform, the interface layer 13 may configure parameters for the target platform and/or obtain data from the target platform in a JSON API message manner.
The interface layer 13 may include any combination of a device information interface, a dial interface, an APN configuration interface, a network information interface, a short message interface, a FOTA upgrade interface, a LOG print interface, a system time interface, and a backup interface, according to the different functions to be implemented.
In the embodiment of the application, different functions of the internet of things system are divided independently, and each function module is independent, so that later-period source code maintenance, function framework modification and adaptation, object function development and the like can be facilitated.
It is contemplated that the same platform may simultaneously support different systems, such as linux systems, FreeRTOS systems, etc. In the embodiment of the present application, in order to adapt to different systems, an adaptation layer may be set in the internet of things system.
The interface layer 13 is connected to the adaptation layer, and is configured to invoke, from the adaptation layer, a task processing logic matched with the system type based on the system type corresponding to the platform access request, thereby implementing, based on the task processing logic, interaction with the target platform through the target interface.
The adaptation layer may include a socket, a thread, and a file system. The socket comprises data exchange modes corresponding to different systems, and the thread comprises task creation modes corresponding to different systems. The file system is used for storing data corresponding to different systems.
In practical applications, when the business function of the functional layer 12 needs to be modified or expanded, a manager or a user can input related instructions through a user interface provided by the internet of things system.
Taking function expansion as an example, when a certain service function needs to be added to the functional layer 12, a user may input basic information corresponding to the service function on the user interface, and click a confirmation option on the user interface, which is equivalent to receiving a function expansion instruction for the internet of things system, and the functional layer 12 may add the corresponding service function to the functional layer 12 when receiving the function expansion instruction.
For example, assuming that the object layer does not initially include a function of acquiring base station information, when the base station information needs to be acquired, an object for acquiring the base station information, such as a server object, may be added to the object layer.
In the embodiment of the present application, if a new project or platform type needs to be adapted, only the work of developing the interface layer 13 of the internet of things system is needed. The interface layer 13 may add a corresponding platform interface to the interface layer 13 when the platform type extension instruction is received.
Fig. 2 is a schematic diagram of a framework of an internet of things system adapted to multiple platforms according to an embodiment of the present disclosure, where the framework includes an active code layer, object layers, an application layer, a generic layer, an interface layer, and an adaptation layer. The source code Layer contains LWM2M Libs, DTLS (packet Transport Layer Security Protocol), TLV (Type-length-value), COAP (computer Protocol), and Json function. The Object layer can provide a plurality of functional services for the internet of things system, such as Object security, Object server, Object device, and the like. The application layer can be used for managing functions required by the operation of the internet of things system, and can comprise server information configuration, APN management, a file system, dial management, LOG printing, other modules, LWM2M version control, socket management and the like. The general layer can be used for providing general functions of the Internet of things system, including linked list, LOG and JSON. Among them, LOG is used to support data printing and JSON is used to support data storage. The interface layer is provided with platform interfaces adapted to different platform types, and can comprise a device information interface, a dialing interface, an APN configuration interface, a network information interface, a short message interface, an FOTA upgrading interface, a LOG printing interface, a system time interface, other interfaces and the like according to functions required by a platform required to be adapted. The adaptation layer may include a socket, a thread, and a file system.
In the embodiment of the application, each functional module is independent, so that the maintenance of later source codes, the modification and adaptation of a functional framework, the development of object functions and the like can be facilitated. The interface layer can be adapted to different module software platforms, and the adaptation layer can be adapted to different module operating systems.
According to the technical scheme, the multi-platform-adaptive Internet of things system comprises a source code layer, a functional layer and an interface layer; wherein, the interface layer is provided with platform interfaces adapted to different platform types. And the source code layer is used for storing source codes corresponding to the operation flow of the Internet of things system. The functional layer is connected with the interface layer and used for forwarding the platform access request to the interface layer under the condition of receiving the platform access request. In order to realize the adaptation to different platform types, a plurality of platform interfaces are arranged in an interface layer, and the interface layer can call a corresponding target interface according to the target platform type pointed by the platform access request so as to realize the connection with the target platform corresponding to the target platform type. In the technical scheme, the functions required to be realized by the Internet of things system are hierarchically divided, so that independence among different functions can be realized, and the system can be adapted to various platform types. Compared with the traditional mode, the whole framework version of the Internet of things system needs to be modified and adjusted when one platform type is adapted, the Internet of things system provided by the application adapts to different platform types through the interface layer, and the purpose that one framework version can be specific to a plurality of platform systems is achieved. And if a new project or platform type needs to be adapted, only the work of developing an interface layer is needed, so that the development labor and development period are greatly shortened, and the difficulty of adapting to different system platforms by LWM2M is reduced.
Fig. 3 is a flowchart of a method for adapting multiple platforms according to an embodiment of the present application, where the method includes:
s301: and forwarding the platform access request to the interface layer under the condition of receiving the platform access request.
In the embodiment of the application, the functions required to be realized by the internet of things system are divided into levels, so that independence among different functions can be realized, and interface layers for adapting to different platform types can be independently arranged. The interface layer is provided with platform interfaces adapted to different platform types.
In particular implementations, the functionality for interacting with different platforms may be divided separately into interface layers. The interface layer can call a corresponding target interface according to the target platform type pointed by the platform access request so as to realize the connection with the target platform corresponding to the target platform type.
S302: and calling a corresponding target interface of the interface layer according to the target platform type pointed by the platform access request so as to realize the connection with the target platform corresponding to the target platform type.
The interface layer is provided with platform interfaces adapted to different platform types. Common platform types may include a high-pass platform and an MTK platform, and accordingly, the interface layer may include a platform interface adapted to the high-pass platform and a platform interface adapted to the MTK platform.
The interface layer is mainly used for adapting to different platforms, and executing parameter reading, platform configuration operation and the like of the Internet of things system. The data processing modes corresponding to different platform types are different. In a specific implementation, in the case that the platform type is a high-pass platform, the interface layer may configure parameters for the target platform and/or obtain data from the target platform in a QMI message manner.
Under the condition that the platform type is the MTK platform, the interface layer can configure parameters for the target platform and/or acquire data from the target platform in a JSON API message mode.
The interface layer can comprise any combination of a device information interface, a dialing interface, an APN configuration interface, a network information interface, a short message interface, an FOTA upgrading interface, a LOG printing interface, a system time interface and a standby interface according to different functions to be realized.
In the embodiment of the application, different functions of the internet of things system are divided independently, and each function module is independent, so that later-period source code maintenance, function framework modification and adaptation, object function development and the like can be facilitated.
The description of the features in the embodiment corresponding to fig. 3 may refer to the related description of the embodiment corresponding to fig. 1, and is not repeated here.
According to the technical scheme, the multi-platform-adaptive Internet of things system comprises a source code layer, a functional layer and an interface layer; wherein, the interface layer is provided with platform interfaces adapted to different platform types. And the source code layer is used for storing source codes corresponding to the operation flow of the Internet of things system. The functional layer is connected with the interface layer and used for forwarding the platform access request to the interface layer under the condition of receiving the platform access request. In order to realize the adaptation to different platform types, a plurality of platform interfaces are arranged in an interface layer, and the interface layer can call a corresponding target interface according to the target platform type pointed by the platform access request so as to realize the connection with the target platform corresponding to the target platform type. In the technical scheme, the functions required to be realized by the Internet of things system are hierarchically divided, so that independence among different functions can be realized, and the system can be adapted to various platform types. Compared with the traditional mode, the whole framework version of the Internet of things system needs to be modified and adjusted when one platform type is adapted, the Internet of things system provided by the application adapts to different platform types through the interface layer, and the purpose that one framework version can be specific to a plurality of platform systems is achieved. And if a new project or platform type needs to be adapted, only the work of developing an interface layer is needed, so that the development labor and development period are greatly shortened, and the difficulty of adapting to different system platforms by LWM2M is reduced.
The internet of things system and method adapted to multiple platforms provided by the embodiments of the present application are described in detail above. The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The internet of things system and method adapted to multiple platforms provided by the present application are described in detail above. The principles and embodiments of the present invention are explained herein using specific examples, which are presented only to assist in understanding the method and its core concepts. It should be noted that, for those skilled in the art, it is possible to make various improvements and modifications to the present invention without departing from the principle of the present invention, and those improvements and modifications also fall within the scope of the claims of the present application.
Claims (10)
1. An Internet of things system adaptive to multiple platforms is characterized by comprising a source code layer, a functional layer and an interface layer; the interface layer is provided with platform interfaces adaptive to different platform types;
the source code layer is used for storing source codes corresponding to the operation flow of the Internet of things system;
the functional layer is connected with the interface layer and used for forwarding the platform access request to the interface layer under the condition of receiving the platform access request;
and the interface layer is used for calling a corresponding target interface according to the target platform type pointed by the platform access request so as to realize the connection with the target platform corresponding to the target platform type.
2. The adaptive multi-platform internet of things system of claim 1, further comprising an adaptation layer;
and the interface layer is connected with the adaptation layer and used for calling task processing logic matched with the system type from the adaptation layer based on the system type corresponding to the platform access request, so that the interaction with the target platform is realized through the target interface based on the task processing logic.
3. The system of claim 1, wherein the interface layer is configured to configure parameters for the target platform and/or obtain data from the target platform via QMI messaging in the case that the platform type is a high-pass platform.
4. The multi-platform adapted internet of things system of claim 1, wherein in case the platform type is MTK platform, the interface layer is configured to configure parameters for the target platform and/or obtain data from the target platform in JSON API messaging.
5. The multi-platform adaptable internet of things system of claim 1, wherein the interface layer comprises any combination of a device information interface, a dial-up interface, an APN configuration interface, a network information interface, a short message interface, a FOTA upgrade interface, a LOG print interface, a system time interface, and a backup interface.
6. The system of claim 1, wherein the functional layer is configured to add a corresponding service function to the functional layer when a function expansion instruction is received.
7. The system of claim 1, wherein the interface layer is configured to add a corresponding platform interface to the interface layer when a platform type extension instruction is received.
8. The system of claim 1, wherein the functional layers include objects layers, application layers, and generic layers;
the objects layer is used for providing a plurality of functional services for the Internet of things system;
the application layer is used for managing functions required by the operation of the Internet of things system;
the general layer is used for providing general functions of the Internet of things system.
9. The system of adapting a multi-platform internet of things of claim 8, wherein the common functions of the common layer include generating a linked list, storing data, and outputting data.
10. A method of adapting multiple platforms, comprising:
under the condition of receiving a platform access request, forwarding the platform access request to an interface layer; the interface layer is provided with platform interfaces adaptive to different platform types;
and calling a corresponding target interface of the interface layer according to the target platform type pointed by the platform access request so as to realize the connection with the target platform corresponding to the target platform type.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111494862.0A CN114168137A (en) | 2021-12-08 | 2021-12-08 | Internet of things system and method adaptive to multiple platforms |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111494862.0A CN114168137A (en) | 2021-12-08 | 2021-12-08 | Internet of things system and method adaptive to multiple platforms |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114168137A true CN114168137A (en) | 2022-03-11 |
Family
ID=80484605
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111494862.0A Pending CN114168137A (en) | 2021-12-08 | 2021-12-08 | Internet of things system and method adaptive to multiple platforms |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114168137A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115103042A (en) * | 2022-05-07 | 2022-09-23 | 深圳市广和通无线股份有限公司 | System based on CPE wide area network management protocol and wireless communication module |
-
2021
- 2021-12-08 CN CN202111494862.0A patent/CN114168137A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115103042A (en) * | 2022-05-07 | 2022-09-23 | 深圳市广和通无线股份有限公司 | System based on CPE wide area network management protocol and wireless communication module |
| CN115103042B (en) * | 2022-05-07 | 2024-01-05 | 深圳市广和通无线股份有限公司 | System based on CPE wide area network management protocol and wireless communication module |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8139509B2 (en) | Installation and management of mobile device [{S]} configuration | |
| CN102790781B (en) | The M2M system of a kind of middleware, band sector application middleware and application process thereof | |
| CN101848107B (en) | SNMP (Simple Network Management Protocol) network element and communication method of SNMP network element and proprietary protocol network element | |
| CN102713871A (en) | Client-server system | |
| CN101160563A (en) | Method and system for hosting and executing a component application | |
| US11726808B2 (en) | Cloud-based managed networking service that enables users to consume managed virtualized network functions at edge locations | |
| JP2012053882A (en) | Method and system for processing a scheduling task in device management | |
| CN101895900A (en) | Device and method for managing/controlling terminal based on M2M application platform | |
| CN103812838A (en) | Service calling method and device and system | |
| CN113626002A (en) | Service execution method and device | |
| CN111049930A (en) | IOT agent layer and communication method | |
| CN111147314A (en) | Switch upgrading method, device and storage medium | |
| CN110324193A (en) | A kind of terminal upgrade management method and device | |
| US8457030B2 (en) | Mobile phone and method for receiving calls | |
| WO2023083038A1 (en) | Multi-registration center data processing method and apparatus, device, and storage medium | |
| CN111970359A (en) | Front-end non-service architecture system based on node | |
| CN114168137A (en) | Internet of things system and method adaptive to multiple platforms | |
| CN115248692A (en) | Device and method for supporting cloud deployment of multiple deep learning framework models | |
| CN102281197A (en) | Radio frequency identification (RFID) router architecture system | |
| CN101551758B (en) | System and method for implementing paralleling work of device management and tasks | |
| KR100818962B1 (en) | Method for managing remote mobile device | |
| CN112217845B (en) | Data transmission method based on Netconf protocol and related equipment | |
| CN102819455B (en) | A kind of method process being managed in application layer and management system | |
| CN100502301C (en) | Node controlling method in network management system | |
| CN101521592B (en) | Method and device for establishing the SNMP agent of printer |
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 |