[go: up one dir, main page]

WO2022041279A1 - Procédé et appareil de gestion de dispositif dans l'internet des objets, dispositif informatique, et support de stockage - Google Patents

Procédé et appareil de gestion de dispositif dans l'internet des objets, dispositif informatique, et support de stockage Download PDF

Info

Publication number
WO2022041279A1
WO2022041279A1 PCT/CN2020/112730 CN2020112730W WO2022041279A1 WO 2022041279 A1 WO2022041279 A1 WO 2022041279A1 CN 2020112730 W CN2020112730 W CN 2020112730W WO 2022041279 A1 WO2022041279 A1 WO 2022041279A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
request
identifier
server device
target service
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.)
Ceased
Application number
PCT/CN2020/112730
Other languages
English (en)
Chinese (zh)
Inventor
吕小强
曾春亮
黄翔文
翟召轩
张军
吴泰月
杨启昌
陈泽春
余振荣
陈钊
茹昭
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to PCT/CN2020/112730 priority Critical patent/WO2022041279A1/fr
Priority to CN202080102965.5A priority patent/CN115836511B/zh
Publication of WO2022041279A1 publication Critical patent/WO2022041279A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2807—Exchanging configuration information on appliance services in a home automation network
    • H04L12/281—Exchanging configuration information on appliance services in a home automation network indicating a format for calling an appliance service function in a home automation network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H04L63/123—Applying verification of the received information received data contents, e.g. message integrity
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting

Definitions

  • the present application relates to the technical field of the Internet of Things, and in particular, to a device management method, apparatus, computer equipment and storage medium in the Internet of Things.
  • IOT Internet of Things
  • the identifier usually consists of two part strings, the service type and the service name.
  • Embodiments of the present application provide a device management method, apparatus, computer device, and storage medium in the Internet of Things.
  • the technical solution is as follows:
  • an embodiment of the present application provides a device management method in the Internet of Things, the method is executed by a cloud platform in the Internet of Things, and the method includes:
  • an embodiment of the present application provides a device management method in the Internet of Things, the method is executed by an Internet of Things device in the Internet of Things, and the method includes:
  • Processing obtaining the service universal unique identifier of the target service, querying the model description file of the target service based on the service universal unique identifier of the target service, based on the model description file of the target service and the service element identifier Verifying the validity of the first request, and passing the verification in response to the first request, and performing a management operation on the server device based on the first request;
  • a management operation response to the first request sent by the cloud platform is received.
  • an embodiment of the present application provides a device management method in the Internet of Things, the method is executed by a server device in the Internet of Things, and the method includes:
  • an embodiment of the present application provides a device management device in the Internet of Things, the device is used in a cloud platform in the Internet of Things, and the device includes:
  • a first request receiving module configured to receive a first request sent by an IoT device, where the first request includes a service instance identifier and a service element identifier of the target service in the server device;
  • an identification processing module configured to process the service instance identification to obtain the service universal unique identification code of the target service
  • a file query module for querying the model description file of the target service based on the service universal unique identifier of the target service
  • a verification module configured to verify the validity of the first request based on the model description file of the target service and the service element identifier
  • a management execution module configured to perform a management operation on the server device based on the first request when the first request passes the verification.
  • an embodiment of the present application provides a device management device in the Internet of Things, the device is used in the device of the Internet of Things, and the device includes:
  • a first request sending module configured to send a first request to the cloud platform, where the first request includes the service instance identifier and service element identifier of the target service in the server device; the first request is used to indicate the cloud platform
  • the platform processes the service instance identifier, obtains the service universal unique identifier of the target service, queries the model description file of the target service based on the service universal unique identifier of the target service, and queries the model description file of the target service based on the service universal unique identifier of the target service.
  • the description file and the service element identifier verify the validity of the first request, and in response to the first request passing the verification, perform a management operation on the server device based on the first request;
  • a response receiving module configured to receive a management operation response to the first request sent by the cloud platform.
  • an embodiment of the present application provides a device management device in the Internet of Things, the device is used in a server device in the Internet of Things, and the device includes:
  • a first request receiving module configured to receive a first request sent by the management device, where the first request includes a service instance identifier and a service element identifier of the target service in the server device;
  • a verification module configured to verify the validity of the first request according to the service instance identifier and the service element identifier
  • a management execution module configured to perform a management operation on the server device based on the first request when the first request passes the verification.
  • an embodiment of the present application provides a computer device, the computer device includes a processor, a memory, and a transceiver, the memory stores a computer program, and the computer program is configured to be executed by the processor to The device management method in the above-mentioned Internet of Things is implemented.
  • an embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is loaded and executed by a processor to implement the above device management method in the Internet of Things.
  • a computer program product or computer program comprising computer instructions stored in a computer-readable storage medium.
  • the processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the above-mentioned device management method in the Internet of Things.
  • the target service is indicated by the service instance identifier obtained by processing on the basis of the service universal unique identifier of the target service, so that the cloud platform can determine the service instance identifier through the service instance identifier.
  • the target service and the model description file corresponding to the target service so as to realize the subsequent validity check and management operations. Since the data volume of the service instance identifier is lower than the data volume of the model type and model name string, the above The scheme can significantly reduce the amount of data in the request.
  • FIG. 1 is a schematic diagram of a network architecture of the Internet of Things provided by an embodiment of the present application.
  • Fig. 2 is the frame diagram of the device model involved in the embodiment shown in Fig. 1;
  • FIG. 3 is a flowchart of a device management method in the Internet of Things provided by an embodiment of the present application.
  • FIG. 4 is a flowchart of a device management method in the Internet of Things provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of an event reporting involved in the embodiment shown in FIG. 4;
  • FIG. 6 is a schematic diagram of a device control involved in the embodiment shown in FIG. 4;
  • FIG. 7 is a flowchart of a device management method in the Internet of Things provided by an embodiment of the present application.
  • FIG. 8 is a flowchart of a first request processing involved in the embodiment shown in FIG. 7;
  • FIG. 9 is a block diagram of a device management apparatus in the Internet of Things provided by an embodiment of the present application.
  • FIG. 10 is a block diagram of a device management apparatus in the Internet of Things provided by an embodiment of the present application.
  • FIG. 11 is a block diagram of a device management apparatus in the Internet of Things provided by an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a computer device provided by an embodiment of the present application.
  • the network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application.
  • the evolution of new business scenarios and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • FIG. 1 shows a schematic diagram of a network architecture of the Internet of Things provided by an embodiment of the present application.
  • the network architecture of the Internet of Things may include: a server device 110, a cloud platform 120, and a client device 130;
  • the server device 110 may be a device for providing Internet of Things functional services.
  • the server device 110 may be a smart home device, such as a smart TV, a smart air conditioner, a smart refrigerator, a smart microwave oven, a smart rice cooker, a cleaning robot, and the like.
  • the server device 110 may be an industrial production device such as a lathe, an industrial robot, a solar panel, a wind turbine, and the like.
  • the server device 110 may be a commercial service device, such as a vending machine or the like.
  • the server device 110 may be an intelligent monitoring device, such as a monitoring camera, an infrared sensor, a sound sensor, a temperature sensor, and the like.
  • the cloud platform 120 is a cloud service platform deployed on the network side.
  • the cloud platform 120 may be a cloud service platform implemented based on a single or multiple servers.
  • the client device 130 is a user device for managing the server device 110 .
  • client device 130 is a computer device with built-in management software, eg, a smartphone, tablet, smart watch, personal computer, such as a desktop computer, a laptop computer, a personal workstation, and the like.
  • the cloud platform 120 is connected to the server device 110 and the client device 130 through a wired or wireless network, respectively.
  • the server device 110 and the client device 130 are connected through a wired or wireless network.
  • the above wired or wireless network uses standard communication technologies and/or protocols.
  • the above wired or wireless network may be a communication network based on the IoT protocol of the Internet of Things.
  • the above-mentioned server device 110, cloud platform 120, and client device 130 may be IoT devices that meet industry specifications, for example, may be IoT devices that meet Open Connectivity Foundation (OCF) specifications Internet-connected devices.
  • OCF Open Connectivity Foundation
  • OCF is an emerging IoT application layer technical standard organization. OCF formulates a RESTful (a design style and development method for network applications) service framework for the interconnection between IoT devices.
  • RESTful a design style and development method for network applications
  • the IoT terminal device that provides resources is the OCF server (that is, the above-mentioned server-side device), and the control terminal that accesses resources is the OCF client (that is, the above-mentioned client). end device).
  • control terminal that obtains the indoor environment state data is the client device
  • the sensor device that monitors the indoor environment state data is the server device
  • the business interaction between the client device and the server device is through the creation, reading, updating, It is implemented by deleting or notifying these resource operation methods.
  • Standard schemas are used to describe the interoperability abstraction of devices.
  • Each device schema can contain multiple services.
  • Each service contains properties, actions, and events.
  • Devices can be learned through standard schema files. standard description information, so as to achieve the purpose of device self-description and interoperability. in:
  • a physical device corresponds to a device abstract device, such as a light corresponds to an abstract light
  • a physical device has multiple services, and each service is an independent meaningful functional group
  • a service contains multiple properties, actions and events
  • Each event needs to have a clear event meaning and a list of output parameters.
  • the definition of the device model is to abstract the attributes, operations, events and other elements of the device according to the capabilities of the device; through the operation of the above elements, the acquisition of the device state, or the start or end of the device function, etc. is completed.
  • FIG. 2 shows a frame diagram of a device model involved in an embodiment of the present application.
  • a device 21 includes one or more services 22, and the services 22 correspond to several operations 22a, attributes 22b and/or events 22c.
  • the device refers to the above-mentioned server device in the Internet of Things, also known as the application terminal, and its function set can be described through different service sets;
  • Service refers to an independent and meaningful functional group, which can be reused among different types of application terminals;
  • Attribute is the smallest unit that describes the state and function of the application terminal
  • the operation is used to realize the specific function of the service, and this kind of function generally cannot be completed by the operation of a single attribute;
  • the solutions shown in the subsequent embodiments of the present application provide a solution for device management through a request with a low data volume, which can simplify the parameter content in the request and save network resources.
  • the service type and service name of the target service can be replaced by the service instance identifier of the target service in the server device, wherein the service instance identifier is a digital identifier, which can significantly reduce the The amount of data in the request.
  • the name of the attribute/operation/event in the request is also replaced by an instance identifier in the form of a digital identifier, thereby further reducing the amount of data in the request.
  • FIG. 3 shows a flowchart of a device management method in the Internet of Things provided by an embodiment of the present application.
  • the method can be executed by a cloud platform in the Internet of Things and an Internet of Things device, wherein the cloud platform can be In the cloud platform 120 in the network architecture shown in FIG. 1 , the above-mentioned IoT device may be the server device 110 or the client device 130 in the network architecture shown in FIG. 1 .
  • the method may include the following steps:
  • Step 301 the IoT device sends a first request to the cloud platform, and the cloud platform receives the first request; the first request includes the service instance identifier and the service element identifier of the target service in the server device.
  • the service instance identifier is a digital identifier obtained by digitally changing the service universal unique identifier of the target service.
  • the above-mentioned IoT device is a client device
  • the first request is a control request or an attribute value query request sent by the client device.
  • the above-mentioned IoT device is a server device
  • the first request is an event reporting request sent by the server device.
  • the above service instance ID (Service Instance ID, SIID) is an instantiation ID generated for the corresponding service during the instantiation of the device, and is used to identify the corresponding service in the device model after instantiation.
  • Service-UUID Service-Universally Unique Identifier
  • the service universal unique identifier is a digital identifier
  • the service instance identifier of the target service is obtained by digitally changing the service universal unique identifier of the service. Therefore, the service instance identifier of the target service can be simultaneously Alternate service type and service name.
  • the above-mentioned first request further includes the device identifier of the server device; in an exemplary solution, the first request further includes the device type of the server device.
  • Step 302 the cloud platform processes the service instance identifier to obtain the service universal unique identifier of the target service.
  • the cloud platform performs inverse digital change processing on the service instance identifier to obtain the service of the target service.
  • Universal Unique Identifier if the above-mentioned service instance identifier is a digital identifier obtained by performing digital change processing on the service universal unique identifier of the target service; then the cloud platform performs inverse digital change processing on the service instance identifier to obtain the service of the target service.
  • Universal Unique Identifier if the above-mentioned service instance identifier is a digital identifier obtained by performing digital change processing on the service universal unique identifier of the target service.
  • the service instance identifier of the target service is obtained by digitally changing the service universal unique identification code of the service, as long as the rule for inverse digital transformation of the service universal unique identification code is determined, it can be
  • the service universal unique identifier of the target service is inversely derived from the service instance identifier by means of inverse number change.
  • Step 303 the cloud platform queries the model description file of the target service based on the service universal unique identifier of the target service.
  • Step 304 the cloud platform verifies the validity of the first request based on the model description file of the target service and the service element identifier.
  • Step 305 when the first request passes the verification, the cloud platform performs a management operation on the server device based on the first request.
  • the cloud platform may send a corresponding device control request to the server device to instruct the server device to perform a corresponding control operation.
  • the cloud platform may query the attribute value of the service element of one or more attribute types of the target service in the server device.
  • the cloud platform may record the corresponding event.
  • Step 306 the cloud platform sends a management operation response to the first request to the IoT device, and accordingly, the IoT device receives the management operation response.
  • the cloud platform when the first request is a control request for the server device, the cloud platform returns to the client device a response of whether the server device successfully performs the corresponding control operation.
  • the cloud platform may return the queried attribute values of one or more attribute types of service elements to the client device.
  • the cloud platform may return a response to the server device indicating whether the event is recorded successfully.
  • the service instance identifier obtained by processing on the basis of the service universal unique identifier of the target service is used to indicate
  • the target service enables the cloud platform to determine the target service and the model description file corresponding to the target service through the service instance identifier, so as to realize the subsequent validity check and management operations.
  • the data volume of the model name string is lower, so the above solution can significantly reduce the data volume in the request.
  • the above request in addition to the service instance identifier of the target service, also includes related information of service elements in the target service.
  • the cloud platform performs legality verification in combination with service instance identifiers and related information of service elements.
  • FIG. 4 shows a flowchart of a device management method in the Internet of Things provided by an embodiment of the present application.
  • the method can be executed by a cloud platform in the Internet of Things and an Internet of Things device, wherein the cloud platform can be In the cloud platform 120 in the network architecture shown in FIG. 1 , the above-mentioned IoT device may be the server device 110 or the client device 130 in the network architecture shown in FIG. 1 .
  • the method may include the following steps:
  • Step 401 the IoT device sends a first request to the cloud platform, and the cloud platform receives the first request; the first request includes the service instance identifier and the service element identifier of the target service in the server device.
  • the service instance identifier is an identifier obtained by processing the service universal unique identifier of the target service.
  • the service instance identifier is a digital identifier obtained by digitally changing the service universal unique identifier of the target service.
  • the service element identifier includes an element name of at least one service element in the target service; or, the service element identifier includes an instance identifier of at least one service element in the target service; wherein the service element Include at least one of operations, properties, and events.
  • the element name of the at least one service element may be implemented as a list of attribute names or a list of method names.
  • the element name of the at least one service element may be implemented as a list of attribute names.
  • the element name of the at least one service element may be implemented as an event name list.
  • the first request further includes a management parameter (payload) of at least one service element.
  • the above-mentioned management parameter may be an updated attribute value (changes) or an action parameter (action).
  • the element name of the at least one service element may be implemented as event information.
  • the service universal unique identifier service-UUID of the target service, the service instance identifier siid, and the instance identifier iid of the service element may be set by the management device of the cloud platform.
  • the setting process of the above siid and iid is as follows:
  • the management device displays a service setting interface, where the service setting interface is used to set the services supported by the cloud platform.
  • the management device obtains the service universal unique identifier of the candidate service and the instance identifier of each service element in the candidate service according to the setting operation in the service setting interface.
  • the solutions shown in the above steps S1 and S2 are only introduced by setting the service universal unique identifier of various services supported by the cloud platform and the instance identifier of each candidate service element through the service setting interface as an example.
  • the service universal unique identifier of the various services supported by the cloud platform and the instance identifier of each candidate service element can also be directly updated by the developer to the management device through code.
  • This embodiment of the present application does not limit the setting manner of the service universal unique identifier of the service and the instance identifier of each candidate service element.
  • the general lamp device model is shown in Table 1 below:
  • the device type column indicates the device type of the lamp device.
  • Each row in the Device Description column represents the various services available in the lamp device. Take “service.light.100002” as an example, where “service.light” is the service type, and the last 5 digits in "100002" are the service universal unique identification code of the service.
  • a service-UUID is assigned to each service (Service), and an iid is assigned to each attribute, method, and event in a specific service; in the product application scheme , the above model needs to be instantiated in order to generate an instantiation file of the device model that matches the real product.
  • the light Service needs to be instantiated twice.
  • the requesting terminal sends an instantiation request for the target device product to the management device; correspondingly, the management device receives the instantiation request.
  • the instantiation request indicates that the target device product corresponds to a target service.
  • the requesting terminal after the manager of the requesting terminal selects the target service in the above-mentioned service selection interface, and selects the service element of the target service in the service element selection interface, the requesting terminal can send an instantiation request to the management device.
  • the instantiation request includes the service type of the target service and the element type of each service element of the target service.
  • the management device obtains instantiation order information of the target service, where the instantiation order information is used to indicate that the target service is the ith service of the same type in the target device product; i ⁇ 1, and i is an integer.
  • the management device generates a service instance identifier of the target service according to the identifier generation rule according to the instantiation order information;
  • the identifier generation rule is a rule for identifying services in a digital form.
  • the service instance identifier of the target service when generating the service instance identifier of the target service according to the identifier generation rule, it may be generated on the basis of the Service-UUID of the target service.
  • the step of generating the service instance identifier of the target service by the management device according to the identifier generation rule according to the instantiation order information may include the following steps:
  • the management device obtains the service type of the target service from the above instantiation request.
  • the universal unique identification code of the service is a digital identification.
  • the management device after creating a candidate service, stores the service type of the candidate service in correspondence with the service universal unique identification code.
  • the management device locally queries the service universal unique identifier corresponding to the service type according to the above service type, that is, the digital identifier set for the service by the operator of the management device when creating the service.
  • S5c perform digital change processing on the universal unique identification code of the service to obtain a processed digital identification.
  • the management device when performing digital change processing on the service universal unique identification code according to the identification generation rule, performs the processing of left-shifting the service universal unique identification code by a specified number of digits in binary to obtain the processing followed by the digital ID.
  • the service universal unique identification code of the target service is a digital identification
  • the service universal unique identification code of the target service can be left-shifted by a specified number of digits by processing binary numbers to obtain the processed digital identity.
  • shifting to the left by n bits in binary is equivalent to multiplying 2 to the nth power in decimal.
  • the specified number of digits is 8, and the service general identifier of the target service is 2 as an example, the target service is left-shifted by 8 bits for the service general unique identifier in binary, which is equivalent to 2 times 2 8 times. square (i.e. 2 times 256).
  • the management device obtains the corresponding service instance identifier in combination with the instantiation order of each service of the same type, that is, to achieve Different services of the same type are distinguished by service instance identifiers.
  • the management device when acquiring the service instance identifier of the target service according to the processed digital identifier and the instantiation order information, the management device can add i to the processed digital identifier and then subtract 1 to obtain The digital ID of the target service is used as the service instance ID of the target service.
  • the service instance identifier of the first service is 2*256; when the second service among the multiple services of the same type is instantiated, the service instance identifier of the second service is 2*256+1; When a third service among multiple services of the same type is instantiated, the service instance identifier of the third service is 2*256+2, and so on.
  • the service instance identifier is obtained by processing the universal unique identifier of the service to obtain the processed digital identifier, and combining the digital identifier and the instantiation order information to obtain the service instance identifier. It can not only indicate the identity of the corresponding service, but also implicitly identify the type of the service.
  • the management device when generating the service instance identifier of the target service according to the identifier generation rule according to the instantiation order information, may add i to the specified digital identifier and then subtract 1 to obtain the The digital identifier, as the service instance identifier of the target service; the specified digital identifier is an integer greater than or equal to 1.
  • the service instance ID of the first service is 1; when instantiating the second service among the multiple services of the same type, the service instance identifier of the second service is 2; when instantiating the third service among the multiple services of the same type, The service instance ID of the third service is 3, and so on.
  • the management device acquires the element type of each service element in the target service; and acquires the instance identifier of each service element according to the element type of each service element.
  • the management device may also generate a device model instantiation file containing the service instance identifier of the target service and the instance identifiers of the above-mentioned respective service elements.
  • Step 402 the cloud platform shifts the service instance identifier to the right by the specified number of digits in binary to obtain the service universal unique identifier of the target service.
  • the above service instance identifier is obtained by shifting the service universal unique identifier of the target service to the left by a specified number of digits.
  • the cloud platform shifts the service instance identifier to the right by a specified number of bits in binary.
  • shifting the specified number of digits to the right in binary means dividing the digital identification by 2 to the power of the specified number of digits.
  • the siid of the target service is shifted to the right by the specified number of digits in binary, which is siid/256.
  • Step 403 the cloud platform queries the model description file of the target service based on the service universal unique identifier of the target service.
  • the above-mentioned model description file may be a protobuf file of a service type to which the target service belongs, which contains definitions of service elements such as attributes, operations, and events of the type of service.
  • the definition includes the name, identifier, value range, and the like of the corresponding service element.
  • the identifier of the above service element may be an instance identifier (Instance ID, IID).
  • Step 404 the cloud platform verifies the validity of the first request based on the model description file of the target service and the service element identifier.
  • the cloud platform verifies the content of the first request based on the model description file of the target service, so as to verify the legitimacy of the first request.
  • the cloud platform may compare the service element in the first request with the service element in the model description file, for example, compare the name of the service element in the first request with the service element in the model description file Compare the name of the service element in the first request with the iid of the service element in the model description file to determine whether the service element in the first request exists in the model description file, If the first request also includes the parameters of the service element, it is further judged whether the parameters of the service element in the first request satisfy the value range defined in the model description file, and if the service element in the first request exists in the model description file , and the parameter of the service element in the first request also satisfies the value range defined in the model description file, the first request is determined to be legal; in a possible implementation, if the service element in the first request does not If the parameter exists in the model description file, or the parameter of the service element in the first request also satisfies the value range defined in the model description file, it is determined that the first request is invalid.
  • Step 405 when the first request passes the verification, perform a management operation on the server device based on the first request.
  • the IoT device when the IoT device is a client device, the first request is a control request for the server device, and the service element identifier includes an element name of the at least one service element, the cloud The platform replaces the element name of the at least one service element in the first request with the instance identifier of the at least one service element, and obtains a device control request; sends the device control request to the server device, and the device device control request is used for Instructing the server device to perform a control operation on the server device based on the instance identifier of the at least one service element.
  • the above control request may be implemented by modifying one or more attribute values of the target service in the server device, or by controlling one or more operations of the target service in the server device to realise.
  • the cloud platform queries the attribute value of the at least one service element.
  • the IoT device when the IoT device is a client device, before sending the first request to the cloud platform, the IoT device sends a device information acquisition request to the cloud platform, and the device information acquisition request includes User ID, correspondingly, the cloud platform receives the device information acquisition request sent by the IoT device, and sends the device information of the server device corresponding to the user ID to the IoT device, and the device information contains the target.
  • the service instance identifier and service element identifier of the service correspondingly, the client device receives the device information sent by the cloud platform.
  • the IoT device before the IoT device sends a device control request or a query request, it first needs to obtain the siid of the target service in the server device from the cloud platform, so that the service type and service name of the target service can be replaced by the siid subsequently.
  • the cloud platform records the event corresponding to the event reporting request.
  • the recording of the event corresponding to the above-mentioned event reporting request may include storing the reported event in the event list, and updating the attribute value of the corresponding attribute according to the reported event, and so on.
  • Step 406 the cloud platform sends a management operation response to the first request to the IoT device, and accordingly, the IoT device receives the management operation response.
  • FIG. 5 shows a schematic diagram of an event reporting involved in an embodiment of the present application.
  • the process for the server device to report events to the cloud platform is as follows:
  • the above-mentioned time notification message may be the above-mentioned event reporting request.
  • the payload is the attribute value corresponding to the iid list; the iid and payload can also be carried in the event notification message in the order of "iid-attribute value".
  • the above iid and payload are optional, that is, there may be no iid list and payload in the above message.
  • the cloud platform calculates the service-UUID according to the siid.
  • the method for calculating the service-UUID according to the siid may be: siid/256.
  • the cloud platform obtains the model description file of the target service according to the service-UUID.
  • the model description file contains the description language of the service model, which contains the description of the target service: that is, the definition of attributes, events, and operations.
  • the cloud platform parses the attribute corresponding to the iid and the validity of the attribute value according to the obtained model description file.
  • the so-called legality includes: whether the iid exists, whether the attribute value is correct, and so on.
  • the cloud platform records the above event (device event list). And obtain the user and client device associated with the event, and push the message to the corresponding client device.
  • the cloud platform may return an event reporting response message (ie, the above-mentioned response to the first request) to the server device.
  • FIG. 6 shows a schematic diagram of a device control involved in an embodiment of the present application.
  • the process for the client device to control the server device through the cloud platform is as follows:
  • the voice input device sends voice to the voice platform.
  • the voice platform analyzes whether the above-mentioned voice confirms whether the voice is in the field of the Internet of Things; if so, determines whether the device information corresponding to the server device is cached.
  • the service description information here may be the device information of the above-mentioned server device.
  • the voice platform obtains service description information of the server device from the cloud platform, including: DID (device ID), siid, attribute list and/or operation list.
  • the foregoing service description information further includes an event list.
  • the voice platform generates a device control request message according to the service description information and the analyzed voice keywords, including Did, siid, attribute name list or operation name list, and parameter payload.
  • the above-mentioned device identification is optional content.
  • the cloud platform calculates the service-UUID according to the siid.
  • the cloud platform parses the validity of the attribute name and the attribute value according to the acquired model description file.
  • the cloud platform generates a new device control request according to the received request message: the new control device request uses iid instead of the attribute name/operation name, that is, contains siid, iids, and payload.
  • the cloud platform pushes the new control device request to the corresponding server device according to Did.
  • the cloud platform after the cloud platform pushes the new control device request to the corresponding server device, it can return a device control response message to the voice platform.
  • the attribute name or operation name in the device control request message sent by the voice platform to the cloud platform, can be replaced by iid, so that the cloud platform does not need to convert the attribute name/operation name to iid once, that is, it can be After the validity verification is passed, the device control request message is directly forwarded to the corresponding server device.
  • the target service in the first request sent by the IoT device to the cloud platform, is indicated by a digital identifier obtained by processing on the basis of the service universal unique identifier of the target service service, so that the cloud platform can determine the target service and the model description file corresponding to the target service through the digital identification, so as to realize the subsequent legality verification and management operations. Since the data volume of the digital identification is compared with the model type and model name The amount of data in the string is lower, so the above solution can significantly reduce the amount of data in the request.
  • the attribute name, operation name, and event name are also replaced by iid, so as to further reduce the data volume of the management message.
  • the above solution of the present application can simplify the content transmission load during device control, and only use siid and iid to point to specific service instances, attributes, operations, and event instances, thereby reducing network load.
  • the server device when the server device receives the first request sent by the management device, it may also perform legality verification in combination with the service instance identifier and the related information of the service element.
  • FIG. 7 shows a flowchart of a device management method in the Internet of Things provided by an embodiment of the present application.
  • the method may be executed by a management device and a server device in the Internet of Things, wherein the management device may be In the cloud platform 120 or the client device 130 in the network architecture shown in FIG. 1 , the above server device may be the server device 110 in the network architecture shown in FIG. 1 .
  • the method may include the following steps:
  • Step 701 The management device sends a first request to the server device, and the server device receives the first request; the first request includes the service instance identifier and the service element identifier of the target service in the server device.
  • the service instance identifier is a digital identifier obtained by processing the service universal unique identifier of the target service.
  • the service element identifier includes an instance identifier of at least one service element in the target service; wherein the service element includes at least one of an operation, an attribute, and an event.
  • the above management device may be a cloud platform.
  • the client device sends a first request (such as a control request to the server device) to the cloud platform, and the cloud platform replaces the attribute name or operation name in the first request with the corresponding After iid, send it to the server device.
  • a first request such as a control request to the server device
  • the cloud platform replaces the attribute name or operation name in the first request with the corresponding After iid, send it to the server device.
  • the above management device may also be a client device.
  • the client device when the client device is directly connected to the server device without going through the cloud platform, the client device directly sends the first request to the server device (for example, to the server device). device control request or query request).
  • Step 702 the server device verifies the validity of the first request according to the service instance identifier and the service element identifier.
  • the server device may compare the siid of the target service in the first request with the siid of the service it supports. If the siid of the target service exists in the siid supported by the server device, the siid of the target service in the first request is valid.
  • the server device When the iid is included in the first request, the server device also compares the iid included in the first request with the iid supported by the target service. If the iid included in the first request exists in the siid of the service element of the target service supported by the server device, the iid in the first request is valid.
  • the server device When the first request further includes the parameter corresponding to the iid, the server device further determines whether the parameter of the iid in the first request satisfies the value range of the corresponding iid. If the parameter of iid in the first request satisfies the value range of the corresponding iid, it is determined that the parameter of iid in the first request is valid.
  • Step 703 when the first request passes the verification, the server device performs a management operation on the server device based on the first request.
  • the server device When the above-mentioned first request is a control request to the server device, the server device performs a corresponding control operation according to the control request.
  • the server device queries the attribute value corresponding to the iid in the first request.
  • Step 704 the server device sends a management response to the management device.
  • the server device When the above-mentioned first request is a control request to the server device, the server device returns the execution result of the control operation to the management device.
  • the server device When the above-mentioned first request is a query request, the server device returns the queried attribute value to the management device.
  • FIG. 8 shows a flowchart of a first request processing involved in an embodiment of the present application.
  • the first request processing process is as follows:
  • the client device obtains a device model instance of the server device through a service discovery mechanism.
  • the device model instance includes the siid of the target service provided by the server device, and the iid of the operations, attributes, and events contained in the target service.
  • the client device sends an attribute reading request to the server device according to the information in the service model instance of the server device, and the request carries siid and iid.
  • the server device checks the validity of the siid and the iid.
  • the server device checks whether its own service instance supports the above siid (that is, whether the siid is correct), whether the iid in the request exists in the siid, and whether the attribute corresponding to the iid in the request is readable.
  • the client device sends an attribute modification request to the server device according to the information in the service model instance, and the request carries the siid and iid and the changed content changes (which may be bytes or delimiter).
  • the client device controls the server device by modifying the attribute value of the attribute.
  • the server device checks the validity of the siid and the iid.
  • the server device checks whether its own service instance supports the above siid (that is, whether the siid is correct), whether the iid in the request exists in the siid, whether the attribute corresponding to the iid in the request is writable, and whether the content of changes conforms to the attribute definition.
  • the server device updates the corresponding attribute value, generates an attribute modification response message, and sends it to the client device.
  • the client device sends an operation (or method) invocation request to the server device according to the information in the service model instance, where the request carries siid, iid and/or input parameters.
  • the client device controls the server device by invoking operations/methods.
  • the server device checks the validity of the siid and the iid after receiving the above request.
  • the server device checks whether its own service instance supports the above siid (that is, whether the siid is correct), whether there is the iid in the request in the siid, whether the method/operation corresponding to the iid has input parameters, and whether the input parameters meet the requirements of the method definition.
  • the server device invokes the operation/method; checks whether there are output parameters, and if so, completes the configuration of the output parameters and generates a call response message, which is sent to the client device.
  • the target service in the first request sent by the management device to the server device, is indicated by a digital identifier obtained by processing on the basis of the service universal unique identifier of the target service service, so that the server device can complete the legality check through the digital ID. Since the data volume of the digital ID is lower than the data volume of the model type and model name string, the above solution can significantly reduce the amount of data in the request. amount of data.
  • the attribute name, operation name, and event name are also replaced by iid, so as to further reduce the data volume of the management message.
  • FIG. 9 shows a block diagram of a device management apparatus in the Internet of Things provided by an embodiment of the present application.
  • the device has the function of implementing the steps performed by the cloud platform in the above-mentioned device management method in the Internet of Things.
  • the apparatus may include:
  • a first request receiving module 901 configured to receive a first request sent by an IoT device, where the first request includes a service instance identifier and a service element identifier of a target service in the server device;
  • An identification processing module 902 configured to process the service instance identification to obtain the service universal unique identification code of the target service
  • a file query module 903, configured to query the model description file of the target service based on the service universal unique identifier of the target service;
  • a verification module 904 configured to verify the validity of the first request based on the model description file of the target service and the service element identifier;
  • the management execution module 905 is configured to perform a management operation on the server device based on the first request when the first request passes the verification.
  • the service instance identifier is a digital identifier obtained by digitally changing the service universal unique identifier of the target service
  • the identification processing module is configured to perform inverse digital change processing on the service instance identification to obtain the service universal unique identification code of the target service.
  • the service instance identifier is obtained by shifting the service universal unique identifier of the target service to the left by a specified number of digits;
  • the identification processing module is configured to right-shift the service instance identification by the specified number of digits in binary to obtain the service universal unique identification code of the target service.
  • the service element identifier includes an element name of at least one service element in the target service; or, the service element identifier includes an instance identifier of at least one service element in the target service ;
  • the service element includes at least one of operation, attribute and event.
  • the management execution module 905 is configured to, when the first request is a control request to the server device, and the service element identifier includes the at least one service element When replacing the element name of the at least one service element in the first request with the instance identifier of the at least one service element, a device control request is obtained;
  • the device control request is sent to the server device, where the device control request is used to instruct the server device to perform a control operation on the server device based on the instance identifier of the at least one service element.
  • the management execution module 905 is configured to query the attribute value of the at least one service element when the first request is a query request or a control request to the server device.
  • the apparatus further includes:
  • an information acquisition request receiving module configured to receive a device information acquisition request sent by the Internet of Things device before the first request receiving module receives the first request sent by the Internet of Things device, where the device information acquisition request includes the user identification;
  • an information sending module configured to send the device information of the server device corresponding to the user identifier to the Internet of Things device, where the device information includes the service instance identifier of the target service and the service element logo.
  • the management execution module 905 is configured to, when the IoT device is the server device, the first request is an event reporting request, and the event reporting request passes the verification , record the event corresponding to the event reporting request.
  • the target service in the first request sent by the IoT device to the cloud platform, is indicated by a digital identifier obtained by processing on the basis of the service universal unique identifier of the target service service, so that the cloud platform can determine the target service and the model description file corresponding to the target service through the digital identification, so as to realize the subsequent legality verification and management operations. Since the data volume of the digital identification is compared with the model type and model name The amount of data in the string is lower, so the above solution can significantly reduce the amount of data in the request.
  • the attribute name, operation name, and event name are also replaced by iid, so as to further reduce the data volume of the management message.
  • FIG. 10 shows a block diagram of a device management apparatus in the Internet of Things provided by an embodiment of the present application.
  • the device has the function of implementing the steps performed by the Internet of Things device (ie, the client device or the server device) in the above-mentioned device management method in the Internet of Things.
  • the apparatus may include:
  • a first request sending module 1001 configured to send a first request to the cloud platform, where the first request includes a service instance identifier and a service element identifier of a target service in a server device; the first request is used to indicate the
  • the cloud platform processes the service instance identifier, obtains the service universal unique identifier of the target service, queries the model description file of the target service based on the service universal unique identifier of the target service, and queries the model description file of the target service based on the service universal unique identifier of the target service.
  • the model description file and the service element identifier verify the validity of the first request, and in response to the first request passing the verification, perform management operations on the server device based on the first request;
  • the response receiving module 1002 is configured to receive a management operation response to the first request sent by the cloud platform.
  • the service instance identifier is a digital identifier obtained by digitally changing the service universal unique identifier of the target service.
  • the service instance identifier is obtained by shifting the service universal unique identifier of the target service to the left by a specified number of bits.
  • the service element identifier includes an element name of at least one service element in the target service; or, the service element identifier includes an instance identifier of at least one service element in the target service ;
  • the service element includes at least one of operation, attribute and event.
  • the first request is a control request or a query request to the server device
  • the first request is an event reporting request.
  • the apparatus further includes:
  • an information obtaining request sending module configured to send a device information obtaining request to the cloud platform before the first request sending module sends the first request to the cloud platform, where the device information obtaining request includes a user identifier;
  • an information receiving module configured to receive the device information of the server device corresponding to the user identifier sent by the cloud platform, where the device information includes the service instance identifier of the target service and the service element logo.
  • the target service in the first request sent by the IoT device to the cloud platform, is indicated by a digital identifier obtained by processing on the basis of the service universal unique identifier of the target service service, so that the cloud platform can determine the target service and the model description file corresponding to the target service through the digital identification, so as to realize the subsequent legality verification and management operations. Since the data volume of the digital identification is compared with the model type and model name The amount of data in the string is lower, so the above solution can significantly reduce the amount of data in the request.
  • the attribute name, operation name, and event name are also replaced by iid, so as to further reduce the data volume of the management message.
  • FIG. 11 shows a block diagram of a device management apparatus in the Internet of Things provided by an embodiment of the present application.
  • the device has the function of implementing the steps performed by the server device in the device management method in the Internet of Things.
  • the apparatus may include:
  • the first request receiving module 1101 is configured to receive a first request sent by the management device, where the first request includes the service instance identifier and the service element identifier of the target service in the server device;
  • a verification module 1102 configured to verify the validity of the first request according to the service instance identifier and the service element identifier
  • the management execution module 1103 is configured to perform a management operation on the server device based on the first request when the first request passes the verification.
  • the service element identifier includes an instance identifier of at least one service element in the target service
  • the service element includes at least one of operation, attribute and event.
  • the target service in the first request sent by the management device to the server device, is indicated by a digital identifier obtained by processing on the basis of the service universal unique identifier of the target service service, so that the server device can complete the legality check through the digital ID. Since the data volume of the digital ID is lower than the data volume of the model type and model name string, the above solution can significantly reduce the amount of data in the request. amount of data.
  • the attribute name, operation name, and event name are also replaced by iid, so as to further reduce the data volume of the management message.
  • the device provided in the above embodiment realizes its functions, only the division of the above functional modules is used as an example for illustration. In practical applications, the above functions can be allocated to different functional modules according to actual needs. That is, the content structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • FIG. 12 shows a schematic structural diagram of a computer device 1200 provided by an embodiment of the present application.
  • the computer device 1200 may include: a processor 1201 , a receiver 1202 , a transmitter 1203 , a memory 1204 and a bus 1205 .
  • the processor 1201 includes one or more processing cores, and the processor 1201 executes various functional applications and information processing by running software programs and modules.
  • the receiver 1202 and the transmitter 1203 may be implemented as a communication component, which may be a communication chip.
  • the communication chip may also be referred to as a transceiver.
  • the memory 1204 is connected to the processor 1201 through the bus 1205 .
  • the memory 1204 can be used to store a computer program, and the processor 1201 is used to execute the computer program to implement each step performed by the server device, configuration device, cloud platform or account server in the above method embodiments.
  • memory 1204 may be implemented by any type or combination of volatile or non-volatile storage devices including, but not limited to, magnetic or optical disks, electrically erasable programmable Read Only Memory, Erasable Programmable Read Only Memory, Static Anytime Access Memory, Read Only Memory, Magnetic Memory, Flash Memory, Programmable Read Only Memory.
  • the computer device includes a processor, a memory, and a transceiver (the transceiver may include a receiver for receiving information and a transmitter for transmitting information) and a transmitter.
  • the transceiver may include a receiver for receiving information and a transmitter for transmitting information
  • the transceiver is configured to receive a first request sent by the IoT device, where the first request includes a service instance identifier and a service element identifier of the target service in the server device;
  • the processor configured to process the service instance identifier to obtain the service universal unique identifier of the target service
  • the processor configured to query the model description file of the target service based on the service universal unique identifier of the target service
  • the processor configured to verify the validity of the first request based on the model description file of the target service and the service element identifier
  • the processor is configured to perform a management operation on the server device based on the first request when the first request passes the verification.
  • the processor and transceiver in the computer device involved in the embodiments of the present application may perform the steps performed by the cloud platform in the method shown in FIG. 3 or FIG. No longer.
  • the computer device when the computer device is implemented as an IoT device (ie, a client device or a server device),
  • the transceiver is configured to send a first request to the cloud platform, where the first request includes a service instance identifier and a service element identifier of the target service in the server device; the first request is used to indicate the cloud platform Process the service instance identifier to obtain the service universal unique identifier of the target service, query the model description file of the target service based on the service universal unique identifier of the target service, and describe the model based on the target service.
  • the file and the service element identifier verify the validity of the first request, and in response to the first request passing the verification, perform a management operation on the server device based on the first request;
  • the transceiver is further configured to receive a management operation response to the first request sent by the cloud platform.
  • the processor and transceiver in the computer device involved in the embodiments of the present application may perform the steps performed by the Internet of Things device in the method shown in FIG. 3 or FIG. 4 , It will not be repeated here.
  • the transceiver is configured to receive a first request sent by the management device, where the first request includes a service instance identifier and a service element identifier of the target service in the server device;
  • the processor configured to verify the validity of the first request according to the service instance identifier and the service element identifier;
  • the processor is configured to perform a management operation on the server device based on the first request when the first request passes the verification.
  • the processor and transceiver in the computer device involved in the embodiments of the present application may perform the steps performed by the server device in the method shown in FIG. Repeat.
  • Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is loaded and executed by a processor to realize the above-mentioned thing shown in FIG. 3 , FIG. 4 or FIG. 7 .
  • Various steps in a device management method in networking are described in detail below.
  • the application also provides a computer program product or computer program, the computer program product or computer program comprising computer instructions stored in a computer-readable storage medium.
  • the processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes each of the device management methods in the Internet of Things shown in the above 3, FIG. 4 or FIG. 7 . step.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Automation & Control Theory (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Computer And Data Communications (AREA)

Abstract

La présente demande concerne un procédé et un appareil de gestion de dispositif dans l'internet des objets, un dispositif informatique et un support de stockage, appartenant au domaine technique de l'internet des objets. Le procédé consiste à : recevoir une première demande envoyée par un dispositif de l'internet des objets, la première demande comportant une identification d'instance de service et une identification d'élément de service d'un service cible ; traiter l'identification d'instance de service pour obtenir un identifiant unique universel de service, interroger un fichier de description de modèle et vérifier la légitimité de la première demande ; et lorsque la première demande réussit la vérification, effectuer une opération de gestion sur un dispositif serveur sur la base de la première demande. La solution décrite peut réduire de manière significative la quantité de données dans la première demande et alléger la charge de réseau de l'internet des objets.
PCT/CN2020/112730 2020-08-31 2020-08-31 Procédé et appareil de gestion de dispositif dans l'internet des objets, dispositif informatique, et support de stockage Ceased WO2022041279A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2020/112730 WO2022041279A1 (fr) 2020-08-31 2020-08-31 Procédé et appareil de gestion de dispositif dans l'internet des objets, dispositif informatique, et support de stockage
CN202080102965.5A CN115836511B (zh) 2020-08-31 2020-08-31 物联网中的设备管理方法、装置、计算机设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/112730 WO2022041279A1 (fr) 2020-08-31 2020-08-31 Procédé et appareil de gestion de dispositif dans l'internet des objets, dispositif informatique, et support de stockage

Publications (1)

Publication Number Publication Date
WO2022041279A1 true WO2022041279A1 (fr) 2022-03-03

Family

ID=80354427

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/112730 Ceased WO2022041279A1 (fr) 2020-08-31 2020-08-31 Procédé et appareil de gestion de dispositif dans l'internet des objets, dispositif informatique, et support de stockage

Country Status (2)

Country Link
CN (1) CN115836511B (fr)
WO (1) WO2022041279A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115002146A (zh) * 2022-03-25 2022-09-02 冶金自动化研究设计院有限公司 一种物模型在工业物联网的应用方法
CN115967472A (zh) * 2022-12-29 2023-04-14 天翼物联科技有限公司 一种物联网终端物模型自适应编解码方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103905511A (zh) * 2012-12-30 2014-07-02 青岛海尔软件有限公司 基于广域网的点对点服务发现及服务调用系统及方法
WO2017007510A1 (fr) * 2014-07-07 2017-01-12 Symphony Teleca Corporation Appareils, procédés, et systèmes pour plate-forme de mise à jour de dispositif intégré distant
WO2019236157A1 (fr) * 2018-06-07 2019-12-12 Spatika Technologies Inc. Transport de données dynamique entre des systèmes informatiques commerciaux et d'entreprise
CN111211908A (zh) * 2019-12-25 2020-05-29 深圳供电局有限公司 访问控制方法、系统、计算机设备和存储介质

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107911337A (zh) * 2017-10-11 2018-04-13 海信集团有限公司 一种设备绑定方法、服务器及设备
US10652249B2 (en) * 2017-10-31 2020-05-12 Microsoft Technology Licensing, Llc Remote locking a multi-user device to a set of users
CN111274268B (zh) * 2020-01-15 2023-09-05 平安科技（深圳）有限公司 物联网数据传输方法、装置、介质及电子设备
CN111475523A (zh) * 2020-04-10 2020-07-31 得到(天津)文化传播有限公司 请求响应方法、装置、设备和存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103905511A (zh) * 2012-12-30 2014-07-02 青岛海尔软件有限公司 基于广域网的点对点服务发现及服务调用系统及方法
WO2017007510A1 (fr) * 2014-07-07 2017-01-12 Symphony Teleca Corporation Appareils, procédés, et systèmes pour plate-forme de mise à jour de dispositif intégré distant
WO2019236157A1 (fr) * 2018-06-07 2019-12-12 Spatika Technologies Inc. Transport de données dynamique entre des systèmes informatiques commerciaux et d'entreprise
CN111211908A (zh) * 2019-12-25 2020-05-29 深圳供电局有限公司 访问控制方法、系统、计算机设备和存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CMCC: "Overhead reduction on WLAN/Bluetooth measurement reporting", 3GPP DRAFT; R2-1805510, vol. RAN WG2, 6 April 2018 (2018-04-06), Sanya, China, pages 1 - 3, XP051415985 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115002146A (zh) * 2022-03-25 2022-09-02 冶金自动化研究设计院有限公司 一种物模型在工业物联网的应用方法
CN115967472A (zh) * 2022-12-29 2023-04-14 天翼物联科技有限公司 一种物联网终端物模型自适应编解码方法及系统

Also Published As

Publication number Publication date
CN115836511A (zh) 2023-03-21
CN115836511B (zh) 2025-04-25

Similar Documents

Publication Publication Date Title
US20160179840A1 (en) Cloud bursting a database
US11303583B2 (en) Resource trees by management controller
CN111880948A (zh) 数据刷新方法、装置、电子设备及计算机可读存储介质
US20230045914A1 (en) Method and apparatus for controlling device in internet of things, and gateway device and storage medium
CN113381870A (zh) 报文处理方法和设备
WO2021232860A1 (fr) Procédé, appareil et système de communication
CN112084006B (zh) 一种镜像包处理方法、装置及电子设备
CN108415909A (zh) 一种访问不同数据库的系统及方法
WO2022041279A1 (fr) Procédé et appareil de gestion de dispositif dans l'internet des objets, dispositif informatique, et support de stockage
WO2022041280A1 (fr) Procédé et appareil de génération de fichier dans l'internet des objets, dispositif informatique et support de stockage
WO2023029881A1 (fr) Procédé et appareil de commande de dispositif
US20110153787A1 (en) Information technology asset management
CN113572630B (zh) 网络配置信息的生成方法、装置、电子设备、介质和产品
EP3923538A1 (fr) Procédé et appareil de vérification d'informations et dispositif
US20170302764A1 (en) Unifying realtime and static data for presenting over a web service
CN116436989B (zh) 报文转换方法、装置、设备以及存储介质
WO2025025812A1 (fr) Procédé, appareil et système de gestion de serveur, ainsi que dispositif électronique et support de stockage
WO2025001183A1 (fr) Procédé de traitement de données, dispositif électronique et support d'enregistrement
US11216424B2 (en) Dynamically rendering an application programming interface for internet of things applications
CN109960695B (zh) 云计算系统中数据库的管理方法和装置
CN115935101A (zh) 一种关于MQTT-Topic的数据处理方法
CN115033510A (zh) 组件通信方法、装置、电子设备及存储介质
CN112612789B (zh) 数据存取方法、装置、电子设备及存储介质
JP7700279B2 (ja) 構成更新方法、装置、およびシステム、ならびにコンピュータ可読記憶媒体
CN113452536B (zh) 一种原子对象的管理方法及装置

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20950948

Country of ref document: EP

Kind code of ref document: A1

WWG Wipo information: grant in national office

Ref document number: 202080102965.5

Country of ref document: CN