CN114731302A - Information transmission method and related equipment - Google Patents

Information transmission method and related equipment Download PDF

Info

Publication number
CN114731302A
CN114731302A CN202080081299.1A CN202080081299A CN114731302A CN 114731302 A CN114731302 A CN 114731302A CN 202080081299 A CN202080081299 A CN 202080081299A CN 114731302 A CN114731302 A CN 114731302A
Authority
CN
China
Prior art keywords
service
data
command
calling
capability
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.)
Granted
Application number
CN202080081299.1A
Other languages
Chinese (zh)
Other versions
CN114731302B (en
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of CN114731302A publication Critical patent/CN114731302A/en
Application granted granted Critical
Publication of CN114731302B publication Critical patent/CN114731302B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]

Abstract

An information transmission method, comprising: the calling equipment acquires the capability information of each service equipment in at least one service equipment based on a first command, wherein the at least one service equipment comprises first service equipment; under the condition that the capability information of the first service device, which is determined to be acquired by the calling device, includes a target Artificial Intelligence (AI) function, the calling device establishes a connection channel with the first service device based on a second command, and the target AI function is an AI function which the calling device wishes to remotely call; the calling device remotely calls the target AI function of the first service device based on a third command; and the calling equipment receives result data sent by the first service equipment, wherein the result data comprises data generated after the first service equipment runs a target AI function according to the third command.

Description

Information transmission method and related equipment Technical Field
The present application relates to the field of artificial intelligence, and in particular, to an information transmission method and related devices.
Background
With the development of chip technology, the processing capability of proprietary chips with specific functions in their respective fields is getting stronger and with the maturity of technology, the cost for developing proprietary chips is also gradually decreasing, so manufacturers can realize the development of specific services for existing main products by adding an accessory device with proprietary chips, taking a domestic television manufacturer as an example, manufacturers can introduce a video acquisition function for a television by adding a camera device, and the camera as the accessory device may have various capabilities, such as a video acquisition function, a basic encoding and decoding capability, and some Artificial Intelligence (AI) capabilities.
A host product may be equipped with multiple accessory devices, and an accessory device may have multiple functions, and there has been no effective and standardized solution for how to share the various specific functions of the accessory device.
Disclosure of Invention
In view of the foregoing technical problems, embodiments of the present application provide an information transmission method, so that data communication is performed between a control device and a calling device.
A first aspect of an embodiment of the present application provides an information transmission method, including:
the calling device acquires capability information of the service device, the calling device can inquire the capability information of each service device which can carry out data communication with the calling device, the service devices comprise a first service device, the capability information of the first service device comprises a target AI function, the target AI function is an AI function which the calling device wants to remotely call, the calling device acquires the capability information of the service device based on a first command, in the case where the calling device determines that the target AI function is included in the acquired capability information of the first serving device, the calling device may establish a connection channel with the first service device based on the second command, the calling device remotely calls a target AI function of the first service device based on the third command, and receives result data fed back by the first service device, the result data comprises data generated after the first service equipment operates the target AI function according to the third command;
in the embodiment of the present application, an information transmission method is provided, where a device without a target AI function, that is, a calling device, may access capability information of other devices in a related network through the information transmission method provided in the embodiment of the present application, and establish a connection channel with the device with the target AI function based on the information transmission method provided in the embodiment of the present application, thereby implementing remote calling of the target AI function. For example, the calling device may be a sweeping robot, the sweeping robot does not have an AI function such as a sweeping route calculation function, the corresponding target AI function is the sweeping route calculation function, the sweeping robot may sense the AI function of other devices associated therewith based on the information transmission method provided by the present application, for example, the sweeping route calculation function of the home intelligent calculation center, if the sweeping robot needs to call the sweeping route calculation function, the sweeping robot obtains the capability information of the home intelligent calculation center based on the first command, on the premise that it is determined that the home intelligent calculation center has the target AI function, a communication connection is established with the home intelligent calculation center based on the second command, and then the sweeping route calculation function of the home intelligent calculation center is remotely called based on the third command, so that the sweeping robot obtains a planned driving route.
The information transmission method provided by the embodiment of the application can use a lightweight protocol architecture, can realize flexible intercommunication of the capabilities of the devices, and can realize capability cooperation among the devices of different platforms. And various AI services can be expanded for equipment without AI function, the cost is low, and the flexibility is high.
In a possible implementation, based on the information transmission method provided by the application, dynamic update of the AI capability model of the accessory service device can also be realized.
In a possible implementation scheme, firmware upgrading can be carried out on the accessory service device based on the information transmission method provided by the application.
In a possible implementation scheme, the information transmission method provided by the application provides a command channel and two data channels, and the command channel can transmit various self-defined control commands, wherein one data channel is a channel for calling equipment to send data to service equipment, and can be used for transmitting firmware upgrade data and capability upgrade data, and transmitting the data of the calling equipment to the service equipment; the other channel is a channel for sending data to the calling device by the service device, and can be used for returning result data of the remote capability calling.
In a possible implementation, the same calling device may have multiple different calling services, and the multiple calling services may call the same AI function or multiple different AI functions of the service device at the same time; or a plurality of calling devices can simultaneously call the AI function of the same service device.
In a possible implementation scheme, the information transmission method provided by the application is suitable for IOT devices with insufficient resources, such as IOT devices like intelligent doorbells limited by memory, resources, processing capabilities, and the like.
Based on the first aspect of the present application, in the first implementation manner of the first aspect of the present application, before the invoking device obtains the capability information of the service device based on the first command, the invoking device may receive device information multicast by the service device through a Simple Service Discovery Protocol (SSDP), so as to obtain a service device list, where the service device list stores device information of each service device, and the device information of the service device includes a device name, an Internet Protocol (IP) address, and a port number of the service device.
In the embodiment of the application, the calling device may receive device information of each service device, determine, according to the device information, a service device that the calling device can call, and in an achievable situation, if a device name in the device information and a target AI function have an association relationship, if the target AI function is face recognition, the calling device may select the service device whose device name is associated with the image pickup device to obtain capability information of the service device. Based on the first aspect of the present application or the first implementation of the first aspect, in a second implementation manner of the first aspect of the present application, the first command may be a capability information obtaining command such as a restricted application protocol (COAP), where the capability information obtaining command may include an IP address, a port number, and an information obtaining command field of the service device, where the information obtaining command field is used to indicate to obtain capability information of the service device, and a specific implementation manner of the calling device obtaining the capability information of the service device based on the first command may include: the calling device sends a capability information acquisition command to each service device with a device name meeting the requirement in the service device list, the calling device receives capability information returned by the service device in response to the capability information acquisition command and indicates the AI function of the service device, the capability information can be in a lightweight data exchange format such as c-java-script-object-notification (cjsson), the capability information comprises a capability name, namely the name of the AI function supported by the service device, such as face recognition or skeleton detection, and the capability information can also comprise a transmission mode, and/or an output data length.
Based on the first aspect of the present application to the second implementation of the first aspect, in a third implementation manner of the first aspect of the present application, the second command may be a connection setup command of the COAP, where the connection setup command includes a service device IP address, a port number, a connection setup command field, and a load variable, where the load variable includes a data channel type, a service device IP address, and a data channel port, and the invoking device establishes a connection channel with the first service device based on the second command, where the connection channel includes a first data channel and a second data channel, the first data channel is used for the invoking device to send data to the first service device, the second data channel is used for the invoking device to receive result data returned by the first service device, a data channel port included in the load variable is used for indicating a port of the first data channel, and a port of the second data channel may be determined according to the first data channel, such as adding one to the first data port to obtain the port for the second data channel.
In this embodiment of the application, the connection channel established by the calling device and the first service device based on the second command may include two channels in opposite directions, and a bidirectional connection channel is formed between the calling device and the service device, so as to implement bidirectional transmission of data between the calling device and the service device.
Based on the first aspect of the present application to the third implementation of the first aspect, in a fourth implementation manner of the first aspect of the present application, the third command may be a capability call command, where the capability call command includes a caller service identification number (ID), a capability call command field, and a subscription information packet, the subscription information packet includes a called capability name, the called capability name is a function name of a target AI function, and the calling device may include one or more caller services. Specifically, the calling device sends the capability calling commands of the caller services to the first service device, so that the first service device runs the corresponding target AI function according to the called capability names included in the plurality of capability calling commands.
It can be understood that when only one caller service in the calling device calls the target AI function of the first service device, the calling device sends the capability calling command of the caller service to the first service device, when the calling device includes two or more caller services calling the target AI function of the first service device, the calling device sends the capability calling command of each caller service to the first service device respectively, and the caller service and the capability calling command thereof are in a mapping relationship and are in one-to-one correspondence. Similarly, the calling device receives result data sent by the first service device, and specifically, the multiple caller services of the calling device respectively receive result data processed by target AI functions corresponding to the multiple caller services in the first service device.
Based on the fourth implementation of the first aspect of the present application, in the fifth implementation of the first aspect of the present application, the subscription information packet further includes a data source identifier, where the data source identifier is used to indicate that data to be processed by the target AI function of the first service device comes from the first service device or the remote device, and it can be understood that the remote device includes the invoking device.
In the embodiment of the application, after the service device receives the data source identifier, the service device may determine the source of the data to be processed, and if the service device is from the remote device, prepare to receive the data to be processed.
Based on the fifth implementation of the first aspect of the embodiment of the present application, in a sixth implementation of the first aspect of the embodiment of the present application, when the to-be-processed data indicated by the data source identifier is data from a calling device, the calling device may send the to-be-processed data to the first service device through the first data channel.
In the embodiment of the application, when the to-be-processed data comes from the calling device, the calling device transmits the to-be-processed data to the first service device through the connection channel, and therefore the realizability of the scheme is improved.
Based on the third implementation to the sixth implementation of the first aspect of the embodiment of the present application, in a seventh implementation of the first aspect of the embodiment of the present application, the invoking device sends upgrade data to the first service device, where the upgrade data is used to upgrade firmware in the first service device or an AI function that can be executed by the first service device, the upgrade data is used as data to be processed, the data source identifier indicates that the data source is from the invoking device in the remote device, and the invoking device sends the upgrade data to the service device through the first data channel.
In the embodiment of the application, the calling device can send the upgrade data to the service device, so that the service device can upgrade the firmware or the executable AI function according to the upgrade data, and an implementation mode for upgrading the service device is provided.
Based on the first aspect of the present application to the seventh implementation manner of the first aspect, in an eighth implementation manner of the first aspect of the present application, when it is determined that the service device does not have the target AI function, the invoking device sends capability model data corresponding to the target AI function to the service device, where the capability model data enables the service device to have the target AI function.
Based on the first aspect of the present application to the eighth implementation manner of the first aspect, in the ninth implementation manner of the first aspect of the present application, a specific process of the calling device receiving the result data sent by the first service device may include that the calling device receives a capability data return message returned by the first service device, and the calling device sends load data in the capability data return message to a caller service in the calling device, where the caller service remotely calls the target AI function, where the capability data return message includes: the system comprises at least one caller service ID, a function name and load data, wherein the function name is used for indicating the name of an AI function for processing obtained load data, and the at least one caller service ID is used for indicating at least one caller service for receiving the load data in calling equipment.
In the embodiment of the application, an implementation mode that each caller service receives result data respectively is provided, and the flexibility of the scheme is improved.
Based on the first aspect of the present application to the ninth implementation manner of the first aspect, in the tenth implementation manner of the first aspect of the present application, the invoking device may be at least one of a television, a Set Top Box (STB), a sweeping robot, or an intelligent sound box.
Based on the first aspect of the present application to the tenth implementation manner of the first aspect, in the eleventh implementation manner of the first aspect of the present application, the service device may be at least one of a camera device, an intelligent doorbell, or a home intelligent computing center.
A second aspect of the embodiments of the present application provides an information transmission method, including:
the first service device responds to a first command sent by the calling device, and sends capability information of the first service device to the calling device, wherein the capability information includes an AI function which can be executed by the first service device, the first service device responds to a second command sent by the calling device to establish a connection channel with the calling device, the connection channel is a bidirectional channel between the first service device and the calling device in general, the first service device responds to a third command of the calling device to run a target AI function to obtain result data, the third command includes a function name of the target AI function, the target AI function is a capability name of an AI function which the calling device desires to remotely call, and the first service device sends the result data obtained by running the target AI function to the calling device.
In the embodiment of the present application, an information transmission method is provided, where a device with a target AI function, that is, a service device, may provide capability information to a device without a target AI function, that is, a calling device, in a related network through the information transmission method provided in the embodiment of the present application, and establish a connection channel with the calling device based on the information transmission method provided in the embodiment of the present application, thereby providing remote calling of the target AI function to the calling device.
The information transmission method provided by the embodiment of the application can use a lightweight protocol architecture, can realize flexible intercommunication of the capabilities between the devices, and can realize capability cooperation between the devices of different platforms. And various AI services can be expanded for equipment without AI function, the cost is low, and the flexibility is high.
Based on the second aspect of the present application, in the first implementation manner of the second aspect of the present application, the first command may be a capability information obtaining command of the COAP, where the capability information obtaining command includes an IP address, a port number, and an information obtaining command field of the service device, where the information obtaining command field is used to indicate to obtain the capability information of the first service device.
Based on the second aspect of the present application or the first implementation of the second aspect, in a second implementation manner of the second aspect of the present application, before the first service device sends the capability information of the first service device to the calling device in response to the first command sent by the calling device, the method further includes, after the first service device is online, registering device information to an SSDP, where the device information includes a device name, an IP address, and a port number, the first service device multicasts the device information of the first service device to a network where the first service device is located through the SSDP, and the network where the first service device is located includes the calling device.
In the embodiment of the application, an implementation manner is provided in which the calling device can acquire device information of each service device, the calling device can determine the service device that can be called by the calling device according to the device information, and in an implementation case, if a device name in the device information and a target AI function are associated, and if the target AI function is face recognition, the calling device can select the service device whose device name is associated with the camera device to acquire capability information of the service device.
Based on the second implementation of the second aspect to the second aspect of the embodiments of the present application, in a third implementation manner of the second aspect of the embodiments of the present application, the second command may be a connection establishment command of the COAP, where the connection establishment command includes a first service device IP address, a port number, a connection establishment command field, and a load variable, the load variable includes a data channel type, a first service device IP address, and a data channel port, and a process of the first service device establishing a connection channel with the invoking device in response to the second command sent by the invoking device may be specifically such that the first service device establishes a first data channel and a second data channel between the first service device and the invoking device based on the connection establishment command, the first data channel is used for the first service device to receive data sent by the invoking device, and the second data channel is used for the first service device to send the result data to the invoking device, the data channel port is used to indicate a port of a first data channel, and a port of a second data channel may be determined according to the first data channel, for example, by adding one to the first data port to obtain a port of the second data channel.
In this embodiment of the application, the connection channel established by the first service device and the calling device in response to the second command may include two channels in opposite directions, and a bidirectional connection channel is formed between the calling device and the service device, so that bidirectional transmission of data between the calling device and the service device is realized.
Based on the second aspect to the third implementation of the second aspect of the present embodiment, in a fourth implementation manner of the second aspect of the present embodiment, the third command may be a capability call command, where the capability call command includes a caller service ID, a capability call command field, and a subscription information packet, where the subscription information packet includes a called capability name, the called capability name is a function name of a target AI function, the caller device may include one or more caller services, and a process of the first service device executing the target AI function in response to the third command of the caller device may specifically be that the first service device receives the capability call command of at least one caller service sent by the caller device, and the first service device executes the corresponding target AI function according to the called capability names included in each capability call command to obtain result data, and the first service equipment feeds back the result data to the calling equipment, and respectively sends the result data obtained by processing the target AI function corresponding to the calling service to each calling service calling the target AI function.
Based on the fourth implementation of the second aspect of the embodiment of the present application, in a fifth implementation manner of the second aspect of the embodiment of the present application, the subscription information packet includes a data source identifier, where the data source identifier is used to indicate that the data to be processed by the target AI function of the first service device is from the first service device or the remote device, that is, the data to be processed is from the data source identifier of the first service device and the data source identifier from the remote device may be distinguished by different symbols, and it can be understood that the remote device includes the invoking device.
In the embodiment of the application, after the service device receives the data source identifier, the service device may determine the source of the data to be processed, and if the service device is from the remote device, prepare to receive the data to be processed.
Based on the third implementation manner to the fifth implementation manner of the second aspect of the embodiment of the present application, in a sixth implementation manner of the second aspect of the embodiment of the present application, when the to-be-processed data indicated by the data source identifier is data from a calling device, the first service device may receive the to-be-processed data through the first data channel.
Based on the second aspect to the sixth implementation manner of the second aspect of the embodiment of the present application, in the seventh implementation manner of the second aspect of the embodiment of the present application, when the first service device needs to be upgraded, the first service device may receive upgrade data sent by the invoking device, the first service device upgrades the firmware of the first service device or an AI function that the first service device can execute according to the upgrade data, at this time, the upgrade data is used as data to be processed, the data source identifier indicates that the data source is from the invoking device in the remote device, and the first service device may receive the upgrade data sent by the invoking device through the first data channel.
In the embodiment of the application, the calling device can send the upgrade data to the service device, so that the service device can upgrade the firmware or the executable AI function according to the upgrade data, and an implementation mode for upgrading the service device is provided.
Based on the second aspect to the seventh implementation manner of the second aspect of the embodiment of the present application, in the eighth implementation manner of the second aspect of the embodiment of the present application, if the first service device does not have the target AI function, the first service device may receive capability model data corresponding to the target AI function sent by the calling device, perform capability upgrade according to the capability model data by the first service device, so that the first service device has the target AI function, after the capability upgrade is completed by the first service device, update capability information of the first service device, for example, add an AI function corresponding to the capability model data, and feed back the updated capability information to the calling device.
Based on the second aspect of the present application to the seventh implementation manner of the second aspect, in an eighth implementation manner of the second aspect of the present application, a specific process in which the first service device sends the result data to the invoking device may be that the first service device sends a capability data return message to the invoking device, where the capability data return message includes: the system comprises at least one caller service ID, a function name and load data, wherein the function name is used for indicating the name of an AI function for processing the obtained load data, and the at least one caller service ID is used for indicating at least one caller service for receiving the load data in calling equipment.
Based on the second aspect of the present application to the ninth implementation manner of the second aspect, the invoking device in the tenth implementation manner of the second aspect of the present application may be at least one of a television, a Set Top Box (STB), a sweeping robot, or an intelligent sound box.
Based on the second aspect of the present application to the tenth implementation manner of the second aspect, in an eleventh implementation manner of the second aspect of the present application, the service device may be at least one of a camera device, a smart door bell, or a home smart computing center.
A third aspect of the present application provides an apparatus for information transmission, which can be used as a calling device and has a function of implementing the method in the first aspect and its implementation manners. The device comprises a processor and a transmission interface, wherein the transmission interface is used for receiving or sending data, and the processor is used for calling software instructions stored in a memory so as to execute the information transmission method in the first aspect and the implementation manners thereof.
A fourth aspect of the present application provides an apparatus for information transmission, which can be used as a calling device, and includes:
an obtaining unit, configured to obtain capability information of each service device of at least one service device based on a first command, where the at least one service device includes a first service device; the establishing unit is used for establishing a connection channel with the first service equipment based on a second command under the condition that the acquired capability information of the first service equipment comprises a target AI function, wherein the target AI function is an AI function which is expected to be remotely called by the calling equipment; a calling unit for remotely calling a target AI function of the first service device based on the third command; and the receiving unit is used for receiving result data sent by the first service equipment, wherein the result data comprises data generated after the first service equipment runs the target AI function according to the third command.
The units in the calling device of the present application may be configured to perform the functions of the methods in the first aspect and the implementations thereof.
A fifth aspect of the present application provides a service apparatus with AI processing capability, which can be used as a service device and has a function of implementing the method in the second aspect and the implementation manners thereof. The service device comprises a processor and a transmission interface, wherein the transmission interface is used for receiving or sending data, and the processor is used for calling software instructions stored in a memory so as to execute the information transmission method in the second aspect and the implementation modes thereof.
A sixth aspect of the present application provides a service apparatus having an AI processing capability, which can be used as a service device, the service apparatus including:
the first sending unit is used for responding to a first command sent by the calling equipment and sending capability information to the calling equipment, wherein the capability information comprises AI functions which can be executed by the service equipment; the establishing unit is used for responding to a second command sent by the calling equipment and establishing a connecting channel with the calling equipment; the operation unit is used for responding to a third command of the calling equipment to operate the target AI function and obtain result data; the third command comprises a function name of a target AI function, wherein the target AI function is the capability name of the AI function which the calling equipment wants to remotely call; and the second sending unit is used for sending the result data to the calling equipment.
The units in the service device of the present application may be configured to perform the functions of the methods in the second aspect and its implementations.
A seventh aspect of the present application provides a computer storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform the method as in the first or second aspect and its implementations.
An eighth aspect of the present application provides a computer program product, which, when run on a computer, causes the computer to perform the method as in the first or second aspect and its implementations.
Drawings
FIG. 1 is a schematic diagram of a system framework in an embodiment of the present application;
FIG. 2 is a schematic diagram illustrating functions of a calling device and a service device in an embodiment of the present application;
fig. 3 is a schematic flowchart of an information transmission method in an embodiment of the present application;
fig. 4 is a schematic data structure diagram of result data replied by the service device in the embodiment of the present application;
fig. 5 is another schematic flow chart illustrating an information transmission method according to an embodiment of the present application;
fig. 6 is a schematic diagram of a data structure of data sent by a calling device in an embodiment of the present application;
fig. 7 is another schematic flow chart illustrating an information transmission method according to an embodiment of the present application;
FIG. 8 is a schematic diagram of a cross-platform interconnect architecture in an embodiment of the present application;
FIG. 9 is a diagram illustrating an intelligent home architecture according to an embodiment of the present application;
FIG. 10 is a diagram illustrating a calling device in an embodiment of the present application;
FIG. 11 is a schematic structural diagram of a service device in an embodiment of the present application;
FIG. 12 is a schematic structural diagram of a calling device in an embodiment of the present application;
fig. 13 is a schematic structural diagram of a service device in the 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 of the embodiments.
The terms "first," "second," "third," "fourth," and the like in the description and claims of this application and in the above-described drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. The term "and/or" means either or both
Referring to fig. 1, the system framework of the embodiment of the present application includes:
calling devices 101 to 102, and servicing devices 103 to 104.
The calling devices 101 to 102 may perform information transmission with the service devices 103 to 104 through a connection channel, where the connection channel may be a data channel or a command channel, the data channel is a bidirectional channel for performing information transmission between the calling devices 101 to 102 and the service devices 103 to 104, and the command channel is a unidirectional channel for performing information transmission between the calling devices 101 to 102 and the service devices 103 to 104.
The calling devices 101 to 102 may instruct the service devices 103 to 104 to perform various operations through the connection channels, for example, the calling devices 101 to 102 may determine AI functions that the service devices 103 to 104 can perform, such as a face detection function, a bone recognition function, and the like, and select an appropriate service device 103 to 104 for AI function calling according to the operation conditions, and control the service devices 103 to 104 to perform a target AI function required by the calling devices 101 to 102.
Alternatively, when the service devices 103 to 104 need firmware upgrade, the calling devices 101 to 102 may send firmware upgrade data to the service devices 103 to 104, and the service devices 103 to 104 may perform firmware upgrade according to the firmware upgrade data.
Or, when the calling devices 101 to 102 need to perform capability upgrade on the service devices 103 to 104, the calling devices 101 to 102 may send capability upgrade data to the service devices 103 to 104, and the service devices 103 to 104 may perform capability upgrade according to the capability upgrade data.
In this embodiment, only two calling devices and two service devices are taken as examples for description, and it should be understood that in this embodiment of the application, the number of the calling devices and the number of the service devices are not limited.
Referring to fig. 2, in this embodiment, both the calling device and the service device may support a hisming protocol (hism), specifically, the protocols supported by the calling device and the service device may include a constrained application protocol (COAP), a Simple Service Discovery Protocol (SSDP), and the like, and the calling device and the service device may perform corresponding information transmission based on the commonly supported protocols.
The function call of the calling device to the service device may be a device-level call, for example, one calling device may call the functions of multiple service devices at the same time, and one service device may also be called by multiple calling devices at the same time.
It should be noted that the call of the calling device to the function of the service device may also be a call of a service level, one or more services may be run on the calling device, multiple services may call one function of the service device at the same time, and one service may call multiple functions of the service device at the same time.
In this embodiment, the information transmission between the calling device and the service device may include different processes, which are described below:
firstly, a function calling process:
referring to fig. 3, in this embodiment, the invoking device may invoke the AI function provided by the service device through the connection channel, which is described in detail below:
301. the HISTM Server equipment sends equipment information to the HISTM Client equipment;
in this embodiment, an HISTM Server device is taken as an example of a service device, and an hism Client device is taken as an example of a call device.
It is understood that, in practical applications, the invoking device and the service device may also be other types of devices, for example, the invoking device may be a television, a set-top box, a sweeping robot, or an intelligent sound box, and the service device may be a camera device, an intelligent doorbell, or a home intelligent computing center, and the details are not limited herein.
After the HISTM Server equipment is online, registering equipment information into the HISTM (specifically, SSDP), after the registration is completed, multicasting the equipment information to the network where the HISTM (specifically, SSDP) is located, and then the HISTM Client equipment in the network can acquire the equipment information and perceive that the HISTM Server equipment is online.
It should be noted that the HISTM Server device may multicast the device information of itself in the network directly through the HISTM, or may register the device information of itself to a certain Server in the network through the HISTM, and multicast the device information in the network by the Server, which is not limited herein.
In this embodiment, the device information of the HISTM Server device may include information used to identify the HISTM Server device, such as a device name, Internet Protocol (IP) address information, and an access Port number (Port).
When a plurality of HISTM Server devices are online, each HISTM Server device can send device information according to the flow.
302. The HISTM Client equipment stores the acquired equipment information to an SSDP equipment list;
when the HISTM Client device senses that the HISTM Server device is on-line, the acquired device information of the HISTM Server device can be stored in a locally stored device list.
303. The method comprises the steps that the HISTM Client equipment acquires capability information of HISTM Server equipment;
after the HISTM Client device receives the device information of a plurality of HISTM Server devices, the HISTM Client device can poll the capability information of each HISTM Server device in the locally stored device list through the COAP.
In an optional case, before the hism Client device acquires the capability information of the hism Server device, the hism Client device determines the device name of the hism Server device to be searched first, and then determines all the hism Server devices whose device names meet the requirements in the device list, and further, the hism Client device polls all the hism Server devices whose device names meet the requirements through the COAP, and acquires the capability information of the hism Server devices whose device names meet the requirements.
For example, if the hism Client device determines that the device name of the hism Server device to be searched is a name containing CameraVideo, the hism Client device may select a hism Server device from the device list, which may be, for example, CameraVideo0, CameraVideo3, or the like, and whose device name contains CameraVideo.
After all the HISTM Server devices with the device names meeting the requirements are selected, the HISTM Client devices poll the selected HISTM Server devices through the COAP, and acquire the capability information of the HISTM Server devices.
In an optional case, after the hism Client device receives the capability information of one hism Server device having an AI function which is expected to be called, the hism Client device stops acquiring the capability information of other hism Server devices; in another possible case, the hism Client device acquires the capability information of all hism Server devices with the AI function which the hism Client device wishes to call, and selects the hism Server device with better capability according to the preset rule.
Specifically, the hism Client device may send a first command CMD1 to the hism Server device through the COAP, where the CMD1 includes a device name, an IP address, a port number, and an information acquisition command of the hism Server device, and the information acquisition command is used to indicate to acquire capability information of the hism Server device.
In practical applications, the specific form of CMD1 can be as follows:
Send:coap://192.168.1.155:50614/CameraVideo0ServiceInfo(value=Hi_STM_Test:11)
wherein 192.168.1.155 is the IP address of a certain HISTM Server device, 50614 is the port number of the HISTM Server device, Camera video0 is the device name of the HISTM Server device, ServiceInfo is the information acquisition command, and Hi _ STM _ Test:11 is the command parameter and length.
304. The HISTM Server device replies capability information to the HISTM Client device;
after receiving CMD1, the HISTM Server equipment acquires the capability information thereof and feeds the capability information back to the HISTM Client equipment through a first Reply message Reply 1.
In this embodiment, the format of the Reply1 message may be as follows:
"DevServiceType": "Server device name",
"ServiceNum": the amount of callable capabilities supported by current devices,
"capability 1 information": { "Name": "capability name 1", "transport": transmission mode, "output-len-bytes": length of output data },
"capability 2 information": { "Name": "capability name 2", "transport": transmission mode, "output-len-bytes": length of output data },
"capability N information": { "Name": "capability name N", "transport": transmission mode, "output-len-bytes": output data length }
Wherein, the callable capability number is used to represent the number of the capability supported by the HISTMS Server device.
The capability name is used for representing the name of an AI function supported by the HISTMS Server equipment, such as face recognition or skeleton detection.
The transmission mode is used to indicate which transmission mode the Reply1 message is sent through, or through which transmission mode the hism Client device can invoke the capability, or to indicate which transmission mode the hism Server device can invoke the result data through after the capability is invoked, which specific use case depends on the requirement of the actual application environment, and is not limited here.
The output data length is used for indicating the length of result data returned by the HISTMS Server equipment after the capability is called.
In this embodiment, the capability information may be stored in a lightweight data exchange format, such as c-based (CJSON), but it is understood that the capability information may also be stored in other formats, and the specific details are not limited herein.
305. The HISTM Client equipment determines first HISTM Server equipment meeting the requirements according to the capability information;
after the HISTM Client equipment receives Reply1 messages sent by the HISTM Client equipment, first HISTM Server equipment meeting requirements can be determined according to capacity information in the Reply1 messages, the capacity information of the first HISTM Server equipment comprises a target AI function, and the target AI function is an AI function which the HISTM Client equipment wants to remotely call.
It should be noted that if the hism Client device does not find a hism Server device meeting the requirement according to the capability information in the currently acquired Reply1 message, the hism Client device will continue to wait for the next hism Server device.
306. The HISTM Client equipment sends a connection establishment request to first HISTM Server equipment;
after the HISTM Client device determines the first HISTM Server device, a second command CMD2 can be sent to the first HISTM Server device through the COAP to request for connection establishment.
The CMD2 includes the device name, IP address, port number, connection setup command, and load variables of the first hism Server device, where the load variables include the data channel type, the IP address, and the data channel port of the first hism Server device.
In practical applications, the specific form of CMD2 can be as follows:
Send:coap://192.168.1.155:50614/CameraVideo0?.sys.mediaservice.setup(value={“p”:2,“ep”:{“addr”:“192.168.1.155”,“port”:6666}})
wherein 192.168.1.155 is an IP address of the first hism Server device, 50614 is a port number of the first hism Server device, it should be understood that the hism Client device sends a command, such as the above connection establishment request, to the first hism Server device through a port indicated by the port number, CameraVideo0 is a device name of the first hism Server device, the connection establishment command is sys.
It should be noted that a port of the data channel is generally a port through which the hism Client device sends data to the first hism Server device, and a port through which the first hism Server device sends data to the hism Client device may be confirmed according to a port included in the load variable, for example, when the port through which the hism Client device sends data to the first hism Server device is 6666, the port through which the first hism Server device sends data to the hism Client device may be configured to be 6666 plus 1, that is, 6667.
307. The method comprises the steps that a first HISTM Server device establishes a data channel;
after receiving CMD2 sent by the hism Client device, the first hism Server device sends a second Reply message Reply2 to the hism Client device, and creates a receive data channel and a send data channel.
The sending data channel is used for transmitting result data back to the HISTM Client device, and the receiving data channel is used for receiving data, such as firmware upgrading data, from the HISTM Client device.
After the data channel is established, the HISTM Client equipment and the first HISTM Server equipment realize bidirectional data intercommunication.
It should be noted that the first hism Server device may selectively establish the receive data channel and the transmit data channel according to actual requirements, and if operations such as firmware upgrade are not required or source data to be processed by an AI function are all from a local end of the first hism Server device and other scenes that do not need to receive external data, the receive data channel may not be established, and the specific details are not limited herein.
308. The HISTM Client equipment sends a calling instruction to first HISTM Server equipment;
in this embodiment, the hism Client device may send a third command CMD3 to the first hism Server device through the COAP to request to call a target AI function of the first hism Server device.
The CMD3 can include caller ID, capability call command, and call information message, wherein the call information message includes called capability name, data source, and transport mode.
The CMD3 can take a variety of different forms depending on the source of the data:
1. the data source is a first HISTM Server device:
in this embodiment, the data source may be the first hism Server device, that is, data to be processed by the AI function of the first hism Server device is from the local end of the first hism Server device, or the AI function uses data in the first hism Server device for processing, for example, based on video stream information acquired by an AI camera in the first hism Server device.
At this time, the specific form of CMD3 can be as follows:
send: cover:// 192.168.1.155:50614/CameraVideo0command (value { "ClientID": 1, "cmd": descriptor "," descriptor ": message { call } })
The specific form of the calling information message may be as follows:
{ "Service": capability name "," DataSource ": 0", "TrastType": 2}
Wherein 192.168.1.155 is an IP address of the first hisms Server device, 50614 is a port number of the first hisms Server device, CameraVideo0 is a device name of the first hisms Server device, ClientID is caller id, "cmd" is "describe," and "describe" is a capability call command.
It should be noted that the ClientID may have multiple presentation forms, and if the call is at a device level, the ClientID may be an identifier of the hism Client device, and if the call is at a service level, the ClientID may be an identifier of a certain service of the hism Client device, which is not limited herein.
"Service" is a called capability name that must be consistent with the capability name provided by the first histserver device.
The "DataSource" is a data source, and in this embodiment, the data source is a first histserver device.
"TrasType" is a transmission mode, and is used to indicate that the invocation information packet is sent through which transmission mode, or is used to indicate that the first hisstmerver device uploads the result data back through which transmission mode after the capability is invoked, where which case is specifically used depends on the requirement of the actual application environment, and is not limited here.
2. The data source is HISTM Client equipment:
in this embodiment, the data source may be an hism Client device, that is, it indicates that the first hism Server device uses data transmitted by the hism Client device to perform processing.
At this time, the specific form of CMD3 can be as follows:
send: cover:// 192.168.1.155:50614/CameraVideo0command (value { "ClientID": 1, "cmd": descriptor "," descriptor ": message { call } })
The specific form of the calling information message may be as follows:
{ "Service": capability name "," DataSource ": 1", "TrastType": 2}
At this time, each parameter in CMD3 is substantially similar to the content described above, and similar parts are not described again, but the difference mainly lies in "DataSource", and in this embodiment, the data source is a hism Client device.
It should be noted that the specific value of the "DataSource" is not limited in practical application, as long as different data sources can be distinguished.
309. The first HISTMS Server device processes according to the call instruction;
after receiving the call instruction, the first histserver device may perform corresponding processing, such as running a target AI function, according to the call instruction.
It should be noted that, if the CMD3 indicates that the data source is the first histserver device, the first histserver device uses local data for processing.
If the CMD3 indicates that the data source is the hism Client device, the first hism Server device first needs to receive data to be processed from the hism Client device through the established data receiving channel, and when a data transmission completion command sent by the hism Client device is received, the first hism Server device may use the received data to be processed for processing.
310. And the first HISTM Server equipment sends result data to the HISTM Client equipment.
After the first HISTM Server device performs corresponding processing according to the call instruction, result data can be sent to the HISTM Client device, wherein the result data comprises data generated after the first HISTM Server device runs the target AI function according to CMD 3.
In this embodiment, the specific form of the result data may be as shown in fig. 4.
The result data can be divided into two parts of a message header and load data.
The information meanings of each part of the message header are as follows:
head Length (Length of header): 8bits, which is used to represent the sum of the lengths of the load length field, the caller number field, the caller ID field, the capability name length field and the capability name field.
Payload Length (Payload Length field): 32bits, which represents the length of the actual payload data.
ClientNum (caller number field): 8bits to indicate the number of current capabilities called by the HISTM Client device.
ClientID0 (caller ID field): and 8bits for representing the service ID of the HISTM Client equipment for calling the current capability, distinguishing different service calls and reporting data.
ServiceNameLen (capability name length field): to indicate the capability name length of the data transmission.
ServiceName (capability name domain): and the ServiceNameLen 8bits is used for representing the capability name of the AI function for processing the obtained load data, and the HISTM Client equipment performs service processing according to the capability name.
The load data part:
payload (Payload data field): and the Payload Length × 8bits is used for representing real load data, namely data generated after the first HISTMS Server device performs corresponding processing according to the call instruction.
It should be noted that, if the call is a service level call, the caller ID is used to indicate the service ID of the hism Client device that receives the load data, and if the call is a device level call, the caller ID is used to indicate the ID of the hism Client device that receives the load data; or multiple caller IDs may indicate multiple service IDs from multiple hism Client devices.
In this embodiment, if the call is a service level call, after the hism Client device receives the result data, the real load data and the capability name are called back to each service of the hism Client device according to the header, for example, the face detection data is transmitted to each face detection service application (intelligent push service, distance reminding service, etc.).
II, equipment control flow:
in this embodiment, the calling device may perform various forms of control on the service device through the connection channel, which is described below:
1. calling equipment control service equipment to perform firmware upgrading:
referring to fig. 5, in this embodiment, the calling device may control the service device to perform firmware upgrade through the connection channel:
501. and the HISTM Server equipment establishes connection with the HISTM Client equipment.
In this embodiment, an HISTM Server device is taken as an example for description, and an hism Client device is taken as an example for description, it is understood that in practical application, the invoking device and the service device may also be other types of devices, and the specific details are not limited herein.
In this embodiment, the process of establishing a connection between the hisstm Server device and the hisstm Client device may be similar to steps 301 to 307 in the embodiment shown in fig. 3, and is not described herein again.
It can be understood that, in this embodiment, the hism Server device and the hism Client device may also establish a connection in other manners, for example, the hism Client device establishes a connection with all online hism Server devices, which is not limited herein.
No matter what kind of mode is adopted by the HISTM Server equipment and the HISTM Client equipment to establish connection, the HISTM Server equipment needs to establish a data receiving channel to prepare for receiving firmware upgrading data from the HISTM Client equipment.
502. The HISTM Client equipment sends a firmware upgrading starting command to the HISTM Server equipment;
when the HISTM Client device determines that the HISTM Server device needs to perform firmware upgrading, a firmware upgrading starting command can be sent to the HISTM Server device through the HISTM command channel.
Specifically, the HISTM Client device can query the current firmware version of the HISTM Server device, query whether the updated firmware version is stored locally or in a cloud, and if yes, determine that the HISTM Server device needs to be upgraded, and understand that the HISTM Client device can also judge whether the HISTM Server device needs to be upgraded by other modes, and the specific situation is not limited.
In this embodiment, the hism Client device may send a firmware upgrade start command to the hism Server device through the COAP, and the specific form may be as follows:
send: coat:// 192.168.1.155:50614/CameraVideo0command (value { "ClientID": 1, "cmd": firmware upgrade "," param ": command parameter" }: 38)
Wherein 192.168.1.155 is the IP address of the HISTM Server device, 50614 is the port number of the HISTM Server device, CameraVideo0 is the device name of the HISTM Server device, ClientID is the controller identification, "cmd": firmware upgrade "is the command, and" command argument "is the command argument.
503. Upgrading and preparing HISTM Server equipment;
when the histserver device receives the firmware upgrade start command, it needs to prepare for the upgrade, for example, prepare enough available memory space, suspend the currently ongoing work, and the like, which is not limited herein.
504. The HISTM Server equipment sends a reply message to the HISTM Client equipment;
and after completing the updating preparation, the HISTM Server equipment sends a reply message to the HISTM Client equipment.
505. The HISTM Client equipment sends firmware upgrading data to the HISTM Server equipment;
and the HISTM Client equipment can send firmware upgrading data to the HISTM Server equipment through the established data channel.
In this embodiment, data sent by the hism Client device may be as shown in fig. 6, where the data includes two parts, namely a header and payload data.
The information meanings of each part of the message header are as follows:
head Length (Length of header): 8bits, which is used to represent the sum of the lengths of the load length field and the sender ID field.
Payload Length (Payload Length field): 32bits, which represents the length of the actual payload data.
ClientID (sender ID field): and 8bits, which is used for indicating the ID of the HISTM Client equipment for sending data or the ID of the service of the HISTM Client equipment and distinguishing different data sources from the HISTM Server equipment.
The load data part:
payload (Payload data field): payload Length 8bits to represent the real load data, the data actually sent by the hism Client device to the hism Server device, etc.
506. The HISTM Client equipment sends a data sending completion command to the HISTM Server equipment;
after the HISTM Client device sends the firmware upgrading data, a data sending completion command can be sent to the HISTM Server device.
507. And the HISTM Server equipment performs firmware upgrade.
After the HISTM Server equipment receives the data sending completion command, the real load data can be used for firmware upgrading according to the message header.
2. Calling equipment control service equipment to upgrade the capacity:
referring to fig. 7, in this embodiment, the calling device may control the service device to perform capability upgrade through the connection channel:
701. and the HISTM Server equipment establishes connection with the HISTM Client equipment.
Step 701 in this embodiment is similar to step 501 in the embodiment shown in fig. 5, and is not described here again.
702 to 703, acquiring the capability information of the HISTM Server equipment by the HISTM Client equipment;
in this embodiment, the hism Client device may acquire capability information of the hism Server device, and a specific acquisition process may be similar to that in embodiments 303 to 304 shown in fig. 3, which is not described herein again.
704. The HISTM Client equipment sends a capability upgrading starting command to the HISTM Server equipment;
after the HISTM Client device obtains the capability information of the HISTM Server device, if the HISTM Server device is found not to support certain target capability, a capability upgrade starting command is sent to the HISTM Server device.
It should be noted that the target capability may be an upgrade capability of a certain capability currently supported by the histserver device, or a capability that the histserver device hardware can support but is not actually supported yet, and is not limited herein.
In this embodiment, the hism Client device may send the capability update start command to the hism Server device through the COAP, and the specific form may be as follows:
send: coat:// 192.168.1.155:50614/CameraVideo0command (value { "ClientID": 1, "cmd": capability upgrade "," param ": command parameter" }: 38)
Wherein 192.168.1.155 is the IP address of the HISTM Server device, 50614 is the port number of the HISTM Server device, CameraVideo0 is the device name of the HISTM Server device, ClientID is the controller identification, "cmd": capability upgrade "is the command, and" command argument "is the command argument.
705. Upgrading and preparing HISTM Server equipment;
when the histserver device receives the capability upgrade start command, it needs to prepare for upgrading, for example, prepare enough available storage space, suspend the currently ongoing related capability, and the like, which is not limited herein.
706. The HISTM Server equipment sends a reply message to the HISTM Client equipment;
and after completing the updating preparation, the HISTM Server equipment sends a reply message to the HISTM Client equipment.
707. The HISTM Client equipment sends capacity upgrading data to the HISTM Server equipment;
the HISTM Client equipment can send the capability upgrading data to the HISTM Server equipment through the established data channel.
In this embodiment, data sent by the hism Client device may be as shown in fig. 6, which is not described herein again.
708. The HISTM Client equipment sends a data sending completion command to the HISTM Server equipment;
after the HISTM Client device sends the capability upgrading data, a data sending completion command can be sent to the HISTM Server device.
709. The HISTM Server equipment carries out capability upgrading;
after the HISTM Server device receives the data sending completion command, the real load data can be used for capacity upgrading according to the message header, for example, the original face recognition capacity information is changed into human shape matting.
710. The histserver device re-registers the capability information.
After the HISTM Server equipment carries out capability upgrading, capability information can be registered to the HISTM again, and when the HISTM Client equipment acquires the capability information to the HISTM Server equipment again, the HISTM Server equipment can provide the updated capability information.
It should be noted that, in the above embodiments, SSDP and COAP are taken as examples for explanation, and since SSDP and COAP both belong to lightweight interconnection protocols, they can operate in an internet of things device with limited resources, thereby improving the application range of the embodiments of the present application.
It is to be understood that the embodiments of the present application do not necessarily need to use SSDP and COAP, and may also be implemented by using other protocols in HISTM, which is not limited herein.
In this embodiment of the application, the hism Client device and the hism Server device may be devices on the same platform (for example, both belong to an Android platform or a Linux platform), or may be cross-platform devices (for example, one of them is an Android platform, and the other is a Linux platform), and the following describes a cross-platform situation:
referring to fig. 8, the entire interconnection device is divided into a hism Client device (Android device) and a hism Server device (Linux device).
The interconnection framework can be used for Android TV equipment or set top box equipment to remotely call AI capabilities (face detection, face recognition and the like) of AI Camera, and the product form of AI business expansion is realized.
In the interconnection architecture, the hism Client device can be divided into three layers: an Application (APP) layer, a HISTM Service layer (HISTM Service layer), and a HISTM protocol layer. Each APP is an independent process, and the HISTMs Service and the HISTM protocol belong to the same process. The APP process is communicated with the HISTM Service process through the Android C/S Binder, and calling of a bottom HISTM protocol is achieved. The HISTM Service layer belongs to the middle layer, transfers the calling information of the APP on the upper layer to the protocol layer, supports multi-instance access, and each APP process has unique HISTM Server correspondence inside the HISTM Service.
The bottom layer is an HISTM protocol layer, which comprises protocols such as COAP, SSDP and the like, and simultaneously supports multi-instance calling and can support simultaneous calling of a plurality of HISTM servers.
In this interconnection architecture, the histsmtserver device may be divided into two layers: the APP layer and the HISTM protocol layer. The APP layer and the HISTM protocol belong to the same process.
And after the APP runs, reading the locally stored capability information configuration file, registering the capability information into an HISTM protocol, and waiting for capability calling of an HISTM Client device.
Based on the above framework, the following describes the data interaction process between the hism Client device and the hism Server device under the cross-platform:
taking AI face detection APP1 and bone recognition APP2 of the HISTM Client device as examples, after the system is started, the HISTMService runs in the background, APP1 and APP2 inquire an SSDP device list of an HISTM protocol layer through HISTM JNI and Binder modules, and then poll the device capability supported by each HISTM Server device through a command channel.
And after receiving the query information, the HISTM Server equipment returns the capability information of the home terminal to the HISTM protocol layer of the HISTM Client equipment, and then returns the capability information to the APP through a Binder Notify mechanism.
If the capability information returned by the HISTM Server equipment comprises the capabilities of 'face detection' and 'bone recognition', APP1 and APP2 respectively send a remote capability calling command to the HISTM Server equipment to call the face detection capability and the bone recognition capability.
And after the HISTM Server equipment receives the capability calling command, starting the processing of the corresponding capability in the capability information according to the capability name, and sending the result data back to the HISTM Client equipment through the data channel.
After the HISTM Client equipment receives the data, the data are transmitted back to the APP layer through the shared memory, and the APP uses the actual data for specific services to complete the whole process.
The information transmission method in the embodiment can realize the capability of the HISTM Client device to call the HISTMServer device under a cross-platform scene, so that the application range is expanded.
It should be noted that the hism can be widely applied to the field of smart homes besides the above-mentioned scenario, and the following introduces the application of the hism in the field of smart homes:
referring to fig. 9, a general sweeping robot (hism Client device) establishes a network connection with a home intelligent computing center (hism Server device) through WiFi.
After the HISTM module of the common sweeping robot is operated, the sweeping route calculation capability of the family intelligent calculation center is remotely called, and the sweeping route information acquired in real time is transmitted back to the sweeping control application, so that the intelligent control of the sweeping route is realized.
The above describes the method for information transmission in the embodiment of the present application, and the following describes the device in the embodiment of the present application.
Referring to fig. 10, an invoking device 1000 according to an embodiment of the present application is provided, where the invoking device 1000 may include one or more processors 1001 and a memory 1005, where the memory 1005 stores program codes, and further, the memory 1005 may further store data.
The memory 1005 may be a volatile memory or a nonvolatile memory or a persistent memory, among others. The program code stored in the memory 1005 may include one or more modules, each of which may include a sequence of instructions operating on a calling device. Still further, the processor 1001 may be configured to communicate with the memory 1005 to execute a series of instruction operations in the memory 1005 on the calling device 1000.
The calling device 1000 may also include one or more power supplies 1002, one or more wired or wireless network interfaces 1003, one or more input-output interfaces 1004, and/or one or more operating systems, such as Windows, Android, Mac OS, IOS, Unix, Linux, FreeBSD, etc.
The processor 1001 may perform the operations performed by the calling device in the embodiments shown in fig. 3, 5, and 7, which are not described herein again.
Referring to fig. 11, an embodiment of the present application provides a service apparatus 1100, where the service apparatus 1100 may include one or more processors 1101 and a memory 1105, where the memory 1105 may store program codes and further may store data in the memory 1105.
The memory 1105 may be a volatile memory or a non-volatile memory or a persistent memory, among others. The program code stored in the memory 1105 may include one or more modules, each of which may include a sequence of instruction operations for a service device. Still further, the processor 1101 may be configured to communicate with the memory 1105 to perform a series of instruction operations in the memory 1105 on the service device 1100.
The service apparatus 1100 may also include one or more power supplies 1102, one or more wired or wireless network interfaces 1103, one or more input-output interfaces 1104, and/or one or more operating systems, such as Windows, Android, Mac OS, IOS, Unix, Linux, FreeBSD, etc.
The processor 1101 may perform the operations performed by the service device in the embodiments shown in fig. 3, 5, and 7, which are not described herein again.
Referring to fig. 12, an embodiment of the present application provides a calling device, where the calling device includes:
an obtaining unit 1201, configured to obtain capability information of each service device in at least one service device based on a first command, where the at least one service device includes a first service device;
an establishing unit 1202, configured to establish a connection channel with the first service device based on the second command when it is determined that the acquired capability information of the first service device includes the target AI function, where the target AI function is an AI function that the calling device desires to remotely call;
an invoking unit 1203, configured to remotely invoke a target AI function of the first service device based on the third command;
a receiving unit 1204, configured to receive result data sent by the first service device, where the result data includes data generated after the first service device runs the target AI function according to the third command.
In this embodiment, each unit in the calling device may perform the operation performed by the calling device in the embodiments shown in fig. 3, 5, and 7, which is not described herein again.
Referring to fig. 13, an embodiment of the present application provides a service device, where the service device includes:
a first sending unit 1301, configured to send capability information to the calling device in response to a first command sent by the calling device, where the capability information includes an AI function that can be executed by the service device;
an establishing unit 1302, configured to establish a connection channel with a calling device in response to a second command sent by the calling device;
an operation unit 1303, configured to operate the target AI function in response to the third command of the calling device, and obtain result data; the third command comprises a function name of a target AI function, wherein the target AI function is the capability name of the AI function which the calling equipment wants to remotely call;
a second sending unit 1304, configured to send the result data to the calling device.
In this embodiment, each unit in the service device may perform the operations performed by the service device in the embodiments shown in fig. 3, 5, and 7, which are not described herein again.
It should be understood that the first and second transmission units may be physically implemented by one and the same transmission unit, e.g. both may be implemented by a transceiver or a transmission interface.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.
The computer program product includes one or more computer instructions. The procedures or functions according to the embodiments of the invention are brought about in whole or in part when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. A computer-readable storage medium may be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium, or a semiconductor medium such as a Solid State Disk (SSD), etc.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a unit is only a logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may also be implemented in the form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method of the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Claims (46)

  1. An information transmission method, characterized in that the method comprises:
    the calling equipment acquires the capability information of each service equipment in at least one service equipment based on a first command, wherein the at least one service equipment comprises first service equipment;
    under the condition that the capability information of the first service device, which is determined to be acquired by the calling device, includes a target Artificial Intelligence (AI) function, the calling device establishes a connection channel with the first service device based on a second command, and the target AI function is an AI function which the calling device wishes to remotely call;
    the calling device remotely calls the target AI function of the first service device based on a third command;
    and the calling equipment receives result data sent by the first service equipment, wherein the result data comprises data generated after the first service equipment runs a target AI function according to the third command.
  2. The method of claim 1, wherein before the invoking device obtains the capability information of each of the at least one service device based on the first command, the method further comprises:
    and the calling equipment receives equipment information multicast by the at least one service equipment through a Simple Service Discovery Protocol (SSDP) to obtain a service equipment list, wherein the equipment information comprises an equipment name, an Internet Protocol (IP) address and a port number.
  3. The method according to claim 1 or 2, wherein the first command is a capability information obtaining command of a restricted application protocol COAP, the capability information obtaining command includes an IP address, a port number, and an information obtaining command field of a serving device, the information obtaining command field is used to instruct to obtain capability information of the serving device, and the invoking device obtains capability information of each of at least one serving device based on the first command, and specifically includes:
    the calling equipment sends the capability information acquisition command to each service equipment with the equipment name meeting the requirement in the service equipment list;
    and the calling equipment receives the capability information returned by the at least one service equipment in response to the capability information acquisition command.
  4. The method according to any one of claims 1 to 3, wherein the second command is a connection establishment command of the COAP, the connection establishment command includes a service device IP address, a port number, a connection establishment command field, and a load variable, the load variable includes a data channel type, the service device IP address and a data channel port, and the invoking device establishes a connection channel with the first service device based on the second command, specifically including:
    the calling device establishes a first data channel and a second data channel between the calling device and the first service device based on the connection establishment command, the first data channel is used for the calling device to send data to the first service device, the second data channel is used for the calling device to receive result data returned by the first service device, and the data channel port is used for indicating a port of the first data channel.
  5. The method according to any one of claims 1 to 4, wherein the third command is a capability call command, the capability call command includes a caller service identification number ID, a capability call command field, and a subscription information packet, the subscription information packet includes a called capability name, the called capability name is a function name of the target AI function, the calling device includes a plurality of caller services, and the calling device remotely calls the target AI function of the first service device based on the third command, which specifically includes:
    the calling device sends a capability calling command of at least one caller service to the first service device, so that the first service device runs corresponding target AI functions according to called capability names contained in the capability calling commands respectively;
    the receiving, by the calling device, the result data sent by the first service device specifically includes:
    the plurality of caller services of the calling device respectively receive result data processed by target AI functions corresponding to the plurality of caller services in the first service device.
  6. The method of claim 5, wherein the subscription information packet further comprises: a data source identifier for indicating that data to be processed by a target AI function of the first service device comes from the first service device or a remote device, the remote device including the invoking device.
  7. The method of claim 6, wherein when the data source identifier indicates that the data to be processed is from the calling device, the method further comprises: and the calling equipment sends the data to be processed to the first service equipment through the first data channel.
  8. The method according to any one of claims 4 to 7, further comprising:
    the calling device sends upgrade data to the first service device, where the upgrade data is used to upgrade firmware in the first service device or an AI function that can be executed by the first service device.
  9. The method according to any one of claims 1 to 8, further comprising:
    and the calling equipment sends capability model data corresponding to the target AI function to the service equipment under the condition that the service equipment is determined not to have the target AI function, wherein the capability model data can enable the service equipment to have the target AI function.
  10. The method according to any one of claims 1 to 9, wherein the receiving, by the calling device, the result data sent by the first service device specifically includes:
    the calling device receives a capability data return message returned by the first service device, where the capability data return message includes: the system comprises at least one caller service ID, a function name and load data, wherein the function name is used for indicating an AI function name of the load data obtained by processing, and the at least one caller service ID is used for indicating at least one caller service receiving the load data in the calling equipment;
    and the calling equipment sends the load data in the capability data return message to the caller service indicated by each caller service ID.
  11. The method of any one of claims 1 to 10, wherein the invoking device comprises at least one of a television, a set-top box, a sweeping robot, or a smart stereo.
  12. The method of any of claims 1-11, wherein the service device comprises at least one of a camera device, a smart doorbell, or a home smart computing center.
  13. An information transmission method, characterized in that the method comprises:
    the method comprises the steps that a first service device responds to a first command sent by a calling device, and sends capability information of the first service device to the calling device, wherein the capability information comprises AI functions which can be executed by the first service device;
    the first service equipment responds to a second command sent by the calling equipment to establish a connection channel with the calling equipment;
    the first service equipment responds to a third command of the calling equipment to operate a target AI function, and result data are obtained; the third command includes a function name of the target AI function, where the target AI function is a capability name of an AI function that the calling device desires to remotely call;
    and the first service equipment sends the result data to the calling equipment.
  14. The method of claim 13, wherein the first command is a capability information acquisition command of a restricted application protocol COAP, and wherein the capability information acquisition command includes an IP address, a port number, and an information acquisition command field of a serving device, and wherein the information acquisition command field is used to indicate acquisition of capability information of the first serving device.
  15. The method according to claim 13 or 14, wherein before the first service device sends the capability information of the first service device to the calling device in response to the first command sent by the calling device, the method further comprises:
    after the first service equipment is online, registering equipment information to SSDP, wherein the equipment information comprises an equipment name, an IP address and a port number;
    the first service device multicasts the device information of the first service device to a network where the first service device is located through the SSDP, and the network where the first service device is located includes the calling device.
  16. The method according to any one of claims 13 to 15, wherein the second command is a connection setup command of COAP, the connection setup command includes a first service device IP address, a port number, a connection setup command field, and a load variable, the load variable includes a data channel type, the first service device IP address, and a data channel port, and the first service device establishes a connection channel with the invoking device in response to the second command sent by the invoking device, specifically including:
    and the first service equipment establishes a first data channel and a second data channel between the first service equipment and the calling equipment based on the connection establishment command, wherein the first data channel is used for the first service equipment to receive data sent by the calling equipment, the second data channel is used for the first service equipment to send the result data to the calling equipment, and the data channel port is used for indicating a port of the first data channel.
  17. The method according to any one of claims 13 to 16, wherein the third command is a capability call command, the capability call command includes a caller service ID, a capability call command field, and a subscription information packet, the subscription information packet includes a called capability name, the called capability name is a function name of the target AI function, the caller device includes a plurality of caller services, and the first service device executes the target AI function in response to the third command of the caller device, including:
    the first service equipment receives a capability calling command of at least one caller service sent by the calling equipment;
    the first service equipment runs corresponding target AI functions according to called capability names contained in the at least one capability caller command respectively;
    the sending, by the first service device, the result data to the calling device specifically includes:
    and the first service equipment respectively sends result data obtained by processing the target AI function corresponding to the at least one caller service.
  18. The method of claim 17, wherein the subscription information packet further comprises: a data source identifier for indicating that data to be processed by a target AI function of the first service device comes from the first service device or a remote device, the remote device including the invoking device.
  19. The method of claims 16 to 18, wherein when the data source identifier indicates that the data to be processed is from the calling device, the method further comprises:
    and the first service equipment receives the data to be processed sent by the calling equipment through the first data channel.
  20. The method of any one of claims 13 to 19, further comprising:
    the first service equipment receives upgrade data sent by the calling equipment;
    and the first service equipment upgrades the firmware or the AI function which can be executed by the first service equipment according to the upgrading data.
  21. The method of any one of claims 13 to 20, further comprising:
    when the first service device does not have the target AI function, the first service device receives capability model data corresponding to the target AI function sent by the calling device;
    and the first service equipment performs capacity upgrading according to the capacity model data so as to enable the first service equipment to have the target AI function.
  22. The method according to any one of claims 13 to 21, wherein the sending, by the first service device, the result data to the invoking device specifically includes:
    the first service device sends a capability data return message to the calling device, where the capability data return message includes: the system comprises at least one caller service ID, a function name and load data, wherein the function name is used for indicating an AI function name of the load data obtained by processing, and the at least one caller service ID is used for indicating at least one caller service receiving the load data in the calling equipment.
  23. The method of any one of claims 13 to 22, wherein the invoking device comprises at least one of a television, a set-top box, a sweeping robot, or a smart stereo.
  24. The method of any of claims 13 to 23, wherein the service device comprises at least one of a camera device, a smart doorbell, or a home smart computing center.
  25. An apparatus for information transmission, the apparatus comprising: a processor and a transmission interface, the transmission interface for receiving or transmitting data, the processor for invoking software instructions stored in a memory to perform the steps of:
    acquiring capability information of each service device in at least one service device based on a first command, wherein the at least one service device comprises a first service device;
    under the condition that the acquired capability information of the first service equipment comprises a target AI function, establishing a connection channel with the first service equipment based on a second command, wherein the target AI function is an AI function which the information transmission device wishes to remotely call;
    and receiving result data sent by the first service device, wherein the result data comprises data generated after the first service device runs a target AI function according to the third command.
  26. The apparatus of claim 25, wherein before the obtaining the capability information of each of the at least one service device based on the first command, the processor is further configured to:
    and receiving the device information multicast by the at least one service device through SSDP to obtain a service device list, wherein the device information comprises a device name, an Internet Protocol (IP) address and a port number.
  27. The apparatus according to claim 25 or 26, wherein the first command is a capability information acquisition command of a restricted application protocol COAP, the capability information acquisition command includes an IP address, a port number, and an information acquisition command field of a serving device, the information acquisition command field is used to indicate to acquire capability information of the serving device, and the processor is specifically configured to:
    sending the capability information acquisition command to each service device of which the device name meets the requirement in the service device list;
    and receiving the capability information returned by the at least one service device in response to the capability information acquisition command.
  28. The apparatus according to any one of claims 25 to 27, wherein the second command is a connection setup command of COAP, the connection setup command includes a serving device IP address, a port number, a connection setup command field, and a load variable, the load variable includes a data channel type, the serving device IP address and a data channel port, and the processor is specifically configured to:
    and establishing a first data channel and a second data channel between the connection establishment command and the first service equipment, wherein the first data channel is used for sending data to the first service equipment by the information transmission device, the second data channel is used for receiving result data returned by the first service equipment by the information transmission device, and the data channel port is used for indicating a port of the first data channel.
  29. The apparatus of any one of claims 25 to 28,
    the third command is a capability call command, where the capability call command includes a caller service ID, a capability call command field, and a subscription information packet, the subscription information packet includes a called capability name, the called capability name is a function name of the target AI function, the calling device includes multiple caller services, and the processor is specifically configured to:
    sending at least one capability calling command for calling a service to the first service device, so that the first service device runs corresponding target AI functions according to the called capability names contained in the plurality of capability calling commands respectively;
    the processor is specifically configured to:
    and receiving result data processed by the target AI function corresponding to the plurality of caller services in the first service device and respectively sending the result data to the plurality of caller services.
  30. The apparatus of claim 29, wherein the subscription information message further comprises: a data source identifier for indicating that data to be processed by a target AI function of the first serving device is from the first serving device or a remote device, the remote device including the means for information transfer.
  31. The apparatus of claim 30, wherein when the data source identifier indicates that the data to be processed is from the calling device, the processor is further configured to: and sending the data to be processed to the first service equipment through the first data channel.
  32. The apparatus of any one of claims 25 to 31, wherein the processor is further configured to:
    sending upgrade data to the first service device, where the upgrade data is used to upgrade firmware in the first service device or an AI function that can be executed by the first service device.
  33. The apparatus of any one of claims 25 to 32, wherein the processor is further configured to:
    and sending capability model data corresponding to the target AI function to the service equipment under the condition that the service equipment is determined not to have the target AI function, wherein the capability model data can enable the service equipment to have the target AI function.
  34. The apparatus according to any one of claims 25 to 33, wherein the processor is specifically configured to:
    receiving a capability data return message returned by the first service device, where the capability data return message includes: the system comprises at least one caller service ID, a function name and load data, wherein the function name is used for indicating an AI function name of the load data obtained by processing, and the at least one caller service ID is used for indicating at least one caller service for receiving the load data;
    and sending the load data in the capability data feedback message to the caller service indicated by each caller service ID.
  35. A service apparatus having AI processing capability, the apparatus comprising: a processor and a transmission interface, the transmission interface to receive or transmit data, the processor to invoke software instructions stored in a memory to perform the steps of:
    sending capability information of the service device to a calling device in response to a first command sent by the calling device, wherein the capability information comprises AI functions which can be executed by the service device;
    responding to a second command sent by the calling equipment to establish a connection channel with the calling equipment;
    responding to a third command of the calling equipment to operate a target AI function, and obtaining result data; the third command includes a function name of the target AI function, where the target AI function is a capability name of an AI function that the calling device desires to remotely call;
    and sending the result data to the calling equipment.
  36. The apparatus of claim 35, wherein the first command is a capability information acquisition command of a restricted application protocol COAP, the capability information acquisition command includes an IP address, a port number, and an information acquisition command field of a serving device, and the information acquisition command field is used to indicate to acquire capability information of the serving apparatus.
  37. The apparatus according to claim 35 or 36, wherein before the sending of the capability information of the service apparatus to the invoking device in response to the first command sent by the invoking device, the processor is further configured to:
    after the service device is online, registering equipment information to SSDP, wherein the equipment information comprises an equipment name, an IP address and a port number;
    and multicasting the equipment information of the service device to a network where the service device is located through the SSDP, wherein the network where the service device is located comprises the calling equipment.
  38. The apparatus according to any one of claims 35 to 37, wherein the second command is a connection setup command of COAP, the connection setup command includes a serving device IP address, a port number, a connection setup command field, and a load variable, the load variable includes a data channel type, the serving device IP address and a data channel port, and the processor is specifically configured to:
    and establishing a first data channel and a second data channel between the connection establishment command and the calling equipment, wherein the first data channel is used for the service device to receive data sent by the calling equipment, the second data channel is used for the service device to send the result data to the calling equipment, and the data channel port is used for indicating the port of the first data channel.
  39. The apparatus of any one of claims 35 to 38, wherein the third command is a capability call command, the capability call command comprises a caller service ID, a capability call command field, and a subscription information packet, the subscription information packet comprises a called capability name, the called capability name is a function name of the target AI function, the caller device comprises a plurality of caller services, and the processor is specifically configured to:
    receiving a capability calling command of at least one caller service sent by the calling equipment;
    respectively operating corresponding target AI functions according to called capability names contained in the at least one capability caller command;
    the processor is further specifically configured to:
    and respectively sending result data obtained by processing the target AI function corresponding to the at least one caller service.
  40. The apparatus of claim 39, wherein the subscription information message further comprises: a data source identifier for indicating that the data to be processed by the target AI function is from the service apparatus or a remote device, the remote device including the invoking device.
  41. The apparatus of any of claims 38 to 40, wherein when the data source identifier indicates that the data to be processed is from the calling device, the processor is further configured to:
    and receiving the data to be processed sent by the calling equipment through the first data channel.
  42. The apparatus according to any one of claims 35 to 41, wherein the processor is further configured to:
    receiving upgrade data sent by the calling equipment;
    and upgrading the AI function which can be executed by the firmware or the service device according to the upgrading data.
  43. The apparatus according to any one of claims 35 to 42, wherein the processor is further configured to:
    when the service device does not have the target AI function, receiving capability model data corresponding to the target AI function, which is sent by the calling equipment;
    and upgrading the capacity of the service device according to the capacity model data so as to enable the service device to have the target AI function.
  44. The apparatus according to any one of claims 35 to 43, wherein the processor is specifically configured to:
    sending a capability data return message to the calling device, the capability data return message including: the system comprises at least one caller service ID, a function name and load data, wherein the function name is used for indicating an AI function name of the load data obtained by processing, and the at least one caller service ID is used for indicating at least one caller service receiving the load data in the calling equipment.
  45. A computer-readable storage medium for storing a computer program, characterized in that the computer program comprises instructions for implementing the method of any of the preceding claims 1 to 12 or 13 to 24.
  46. A computer program product comprising instructions which, when run on a computer or processor, cause the computer or processor to carry out the method of any one of claims 1 to 12 or 13 to 24.
CN202080081299.1A 2020-01-23 2020-01-23 Information transmission method and related equipment Active CN114731302B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/074036 WO2021147109A1 (en) 2020-01-23 2020-01-23 Information transmission method and related device

Publications (2)

Publication Number Publication Date
CN114731302A true CN114731302A (en) 2022-07-08
CN114731302B CN114731302B (en) 2023-06-06

Family

ID=76991651

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202080081299.1A Active CN114731302B (en) 2020-01-23 2020-01-23 Information transmission method and related equipment

Country Status (2)

Country Link
CN (1) CN114731302B (en)
WO (1) WO2021147109A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024077546A1 (en) * 2022-10-13 2024-04-18 华为技术有限公司 Capability calling method and communication apparatus

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1466324A (en) * 2002-09-06 2004-01-07 联想(北京)有限公司 Method for realixing dynamic networking connection and resource sharing in equipment of home backbone network
US20050267935A1 (en) * 1999-06-11 2005-12-01 Microsoft Corporation Data driven remote device control model with general programming interface-to-network messaging adaptor
CN101102248A (en) * 2007-08-16 2008-01-09 四川长虹电器股份有限公司 Service collaboration method between devices in home network
CN101640601A (en) * 2008-07-30 2010-02-03 Tcl集团股份有限公司 Management method for intelligent device
CN103379107A (en) * 2012-04-26 2013-10-30 中兴通讯股份有限公司 Method and device for sharing network device capacity and network devices
CN103685372A (en) * 2012-09-10 2014-03-26 联想(北京)有限公司 Equipment management method and information distribution equipment
CN104601351A (en) * 2013-10-30 2015-05-06 华为技术有限公司 Method for capacity allocation of network equipment, network equipment and system
CN104935484A (en) * 2015-05-28 2015-09-23 北京海尔广科数字技术有限公司 Method and apparatus for calling appliance service via gateways
CN105681137A (en) * 2014-11-20 2016-06-15 北京海尔广科数字技术有限公司 Method and device for invoking services

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8555406B2 (en) * 2009-10-06 2013-10-08 At&T Intellectual Property I, L.P. Remote viewing of multimedia content
CN101951335A (en) * 2010-09-29 2011-01-19 广州市聚晖电子科技有限公司 System and method for realizing interconnection and interworking protocol stack between digital home network devices
CN103905511A (en) * 2012-12-30 2014-07-02 青岛海尔软件有限公司 Point-to-point service discovering and calling system and method based on wide area network
CN107566314B (en) * 2016-06-30 2021-05-14 斑马智行网络(香港)有限公司 Data transmission system, method and equipment
CN107888551A (en) * 2016-09-30 2018-04-06 北京神州泰岳软件股份有限公司 A kind of remote service calling method, device and system

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050267935A1 (en) * 1999-06-11 2005-12-01 Microsoft Corporation Data driven remote device control model with general programming interface-to-network messaging adaptor
CN1466324A (en) * 2002-09-06 2004-01-07 联想(北京)有限公司 Method for realixing dynamic networking connection and resource sharing in equipment of home backbone network
CN101102248A (en) * 2007-08-16 2008-01-09 四川长虹电器股份有限公司 Service collaboration method between devices in home network
CN101640601A (en) * 2008-07-30 2010-02-03 Tcl集团股份有限公司 Management method for intelligent device
CN103379107A (en) * 2012-04-26 2013-10-30 中兴通讯股份有限公司 Method and device for sharing network device capacity and network devices
CN103685372A (en) * 2012-09-10 2014-03-26 联想(北京)有限公司 Equipment management method and information distribution equipment
CN104601351A (en) * 2013-10-30 2015-05-06 华为技术有限公司 Method for capacity allocation of network equipment, network equipment and system
CN105681137A (en) * 2014-11-20 2016-06-15 北京海尔广科数字技术有限公司 Method and device for invoking services
CN104935484A (en) * 2015-05-28 2015-09-23 北京海尔广科数字技术有限公司 Method and apparatus for calling appliance service via gateways

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
曹志杰: "信息设备资源共享协同服务模式研究", 《现代图书情报技术》 *

Also Published As

Publication number Publication date
CN114731302B (en) 2023-06-06
WO2021147109A1 (en) 2021-07-29

Similar Documents

Publication Publication Date Title
CN105577736A (en) Power line carrier communication terminal control device, system and method
CN113411215B (en) Time-sensitive network centralized user configuration method and system based on OPC UA
US8285828B2 (en) Method and system for platform level data model for indications based event control and data transfer
KR20100050517A (en) Data stream control for network devices
CN109996260B (en) Configuration system, client device, embedded device configuration method and storage medium
US6775244B1 (en) Gathering of device discovery information
CN112838940B (en) Network controller frame and data processing method
CN112448873B (en) Binding method and device for equipment and computer readable storage medium
CN108494637B (en) Method for intelligent household equipment to be in butt joint with Control4 system
US20160165303A1 (en) Signal transmission device and method for controlling same
CN110830841A (en) Screen projection method, system and intelligent device under different local area networks
WO2018176244A1 (en) Data collection method, device, and dynamic environment network management system
CN113196721B (en) Method and device for discovering Internet of things equipment and terminal equipment
CN114731302B (en) Information transmission method and related equipment
WO2021253221A1 (en) Role control method, apparatus and device
CN107801253A (en) Device pairing method, apparatus and computer-readable recording medium
CN112953992A (en) Network system, communication and networking method, device and storage medium
CN114338383B (en) Simplified configuration method and system for video equipment
CN113242313B (en) Data synchronization method, system, device, server and storage medium
CN115225482A (en) Method and device for configuring Pod network based on Kubernetes
CN101465783A (en) Connection method, device and connection network bridge for isomery household network appliances
CN112422565A (en) Message processing method and device, storage medium and electronic device
US11337041B2 (en) Methods and apparatus for distributing publish-subscribe messages
CN112333237A (en) 5G industrial module and electronic equipment
CN112511528B (en) Streaming media distribution method, system, server and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant