Information processing method and device, equipment and storage medium

Abstract

The application discloses an information processing method, device and equipment and a storage medium. The method comprises the following steps: receiving a uniform resource identifier (URI) message sent by a previous network device; the URI message comprises a first field, a second field, a third field and a fourth field; the first field represents host information, the host information is composed of the identifiers of at least two network devices hung under a second network device described in a hierarchical manner; the second field represents a resource path, the resource path is used to acquire resource data; the third field represents a device identifier, the device identifier is the identifier of a subordinate device managed by a target network device hung under the second network device; the fourth field represents a resource attribute, the resource attribute is the attribute of the resource data under the resource path; if it is determined according to the first field that the URI message is not locally processed, the URI message is forwarded to a next network device.

Description

Technical Field

[0001] This invention relates to the field of wireless communication technology, and in particular to an information processing method, apparatus, device, and storage medium. Background Technology

[0002] Currently, in real-world IoT environments, IoT platforms typically support multiple layers of network devices. Managing communication between these multiple layers is becoming increasingly important. However, these devices can be of different hardware types and network architectures. Therefore, communication between these devices requires various types of gateways to facilitate communication between higher-level and lower-level devices. Currently, however, there is a lack of a unified and effective resource information access solution for such multi-layered, heterogeneous devices. Summary of the Invention

[0003] In view of this, embodiments of the present invention aim to provide an information processing method, apparatus, device, and storage medium.

[0004] The technical solution of this invention is implemented as follows:

[0005] At least one embodiment of the present invention provides an information processing method applied to a first network device, the method comprising:

[0006] The system receives a Uniform Resource Identifier (URI) message sent by a higher-level network device. The URI message includes a first field, a second field, a third field, and a fourth field. The first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device. The second field represents a resource path used to obtain resource data. The third field represents a device identifier, which is the identifier of a lower-level device managed by the target network device connected to the second network device. The fourth field represents resource attributes, which are the attributes of the resource data under the resource path.

[0007] Based on the first field, determine whether to perform local processing on the URI message;

[0008] If it determines that it will not process the URI message locally, it will forward the URI message to the next-level network device; wherein the previous-level network device, the first network device, and the next-level network device are heterogeneous devices.

[0009] Furthermore, according to at least one embodiment of the present invention, determining whether to perform local processing on the URI message based on the first field includes:

[0010] Match its own network device identifier with at least two network device identifiers described hierarchically in the first field;

[0011] If its own network device identifier does not match the last of the at least two network device identifiers described hierarchically in the first field, then it will not perform local processing on the URI message.

[0012] Furthermore, according to at least one embodiment of the present invention, forwarding the URI message to the next-level network device includes:

[0013] Remove the network device identifier belonging to itself from the first field of the URI message, and forward the URI message to the next level network device.

[0014] Furthermore, according to at least one embodiment of the present invention, the method further includes:

[0015] Receive a response message sent by the next-level network device; the response message carries resource data;

[0016] The resource data is determined by a third network device that performs local processing of the URI message based on the second, third, and fourth fields.

[0017] Furthermore, according to at least one embodiment of the present invention, the method further includes:

[0018] Receive session messages sent by the next-level network device;

[0019] The routing table is updated based on the session messages sent by the next-level network device; the routing table stores the status of the first network device and the next-level network device of the first network device.

[0020] The routing table is sent to the next higher-level network device.

[0021] At least one embodiment of the present invention provides an information processing method applied to a second network device, the method comprising:

[0022] A URI message is generated; the URI message includes a first field, a second field, a third field, and a fourth field; the first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device; the second field represents a resource path, which is used to obtain resource data; the third field represents a device identifier, which is the identifier of the subordinate device managed by the target network device connected to the second network device; the fourth field represents resource attributes, which are the attributes of the resource data under the resource path.

[0023] The URI message is sent to the next-level network device; the first field is used for the next-level network device to determine whether it will process the URI message locally. If it determines that it will not process the URI message locally, it will forward the URI message to the next-level network device; wherein, the second network device and the next-level network device are heterogeneous devices.

[0024] Furthermore, according to at least one embodiment of the present invention, the method further includes:

[0025] The system receives a response message from a next-level network device; the response message carries resource data; wherein the resource data is determined by a third network device that performs local processing of the URI message based on the second, third, and fourth fields.

[0026] Furthermore, according to at least one embodiment of the present invention, the method further includes:

[0027] Receive routing tables sent by the next-level network devices; the routing tables contain the status of network devices at each level;

[0028] Based on the routing table, at least two network device identifiers described hierarchically in the first field are determined.

[0029] At least one embodiment of the present invention provides an information processing method applied to a third network device, the method comprising:

[0030] The system receives a URI message sent by a higher-level network device. The URI message includes a first field, a second field, a third field, and a fourth field. The first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device. The second field represents a resource path used to obtain resource data. The third field represents a device identifier, which is the identifier of a lower-level device managed by the target network device connected to the second network device. The fourth field represents resource attributes, which are the attributes of the resource data under the resource path.

[0031] Based on the first field, determine whether to perform local processing on the URI message;

[0032] If it is determined that it will process the URI message locally, then the resource data is obtained based on the second, third, and fourth fields;

[0033] The response message is sent to the next higher-level network device; the response message carries the resource data.

[0034] Among them, the third network device and the previous level network device are heterogeneous devices.

[0035] Furthermore, according to at least one embodiment of the present invention, determining whether to perform local processing on the URI message based on the first field includes:

[0036] Match its own network device identifier with at least two network device identifiers described hierarchically in the first field;

[0037] If its own network device identifier matches the last of at least two network device identifiers described hierarchically in the first field, then it performs local processing on the URI message.

[0038] Furthermore, according to at least one embodiment of the present invention, the method further includes:

[0039] Send session messages to the next higher-level network device;

[0040] The session message is used to update the routing table of the upstream network device; the routing table stores the status of the third network device and the upstream network device of the third network device.

[0041] At least one embodiment of the present invention provides an information processing apparatus, comprising:

[0042] The first receiving unit is configured to receive a URI message sent by a higher-level network device. The URI message includes a first field, a second field, a third field, and a fourth field. The first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device. The second field represents a resource path, which is used to obtain resource data. The third field represents a device identifier, which is the identifier of a lower-level device managed by the target network device connected to the second network device. The fourth field represents resource attributes, which are the attributes of the resource data under the resource path.

[0043] The first processing unit is configured to determine, based on the first field, whether it will perform local processing on the URI message; if it determines that it will not perform local processing on the URI message, it will forward the URI message to the next-level network device; wherein the next-level network device, the first network device, and the next-level network device are heterogeneous devices.

[0044] At least one embodiment of the present invention provides an information processing apparatus, comprising:

[0045] The second processing unit is used to generate a URI message; the URI message includes a first field, a second field, a third field, and a fourth field; the first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device; the second field represents a resource path, which is used to obtain resource data; the third field represents a device identifier, which is the identifier of a subordinate device managed by the target network device connected to the second network device; the fourth field represents resource attributes, which are the attributes of the resource data under the resource path.

[0046] The first sending unit is used to send the URI message to the next-level network device; the first field is used for the next-level network device to determine whether it will process the URI message locally. If it determines that it will not process the URI message locally, it will forward the URI message to the next-level network device.

[0047] Among them, the second network device and the next-level network device are heterogeneous devices.

[0048] At least one embodiment of the present invention provides an information processing apparatus, comprising:

[0049] The second receiving unit is used to receive a URI message sent by the upper-level network device. The URI message includes a first field, a second field, a third field, and a fourth field. The first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device. The second field represents a resource path, which is used to obtain resource data. The third field represents a device identifier, which is the identifier of a lower-level device managed by the target network device connected to the second network device. The fourth field represents resource attributes, which are the attributes of the resource data under the resource path.

[0050] The third processing unit is used to determine whether it will perform local processing on the URI message based on the first field; if it determines that it will perform local processing on the URI message, it will obtain resource data based on the second, third and fourth fields.

[0051] The second sending unit is used to send a response message to the upper-level network device; the response message carries the resource data.

[0052] Among them, the third network device and the previous level network device are heterogeneous devices.

[0053] At least one embodiment of the present invention provides a first network device, including a first processor and a first memory for storing a computer program capable of running on the processor.

[0054] Wherein, when the first processor is used to run the computer program, it executes the steps of any one of the methods described above on the first network device side.

[0055] At least one embodiment of the present invention provides a second network device, including a second processor and a second memory for storing a computer program capable of running on the processor.

[0056] Wherein, when the second processor is used to run the computer program, it executes the steps of any one of the methods described above on the second network device side.

[0057] At least one embodiment of the present invention provides a third network device, including a third processor and a third memory for storing a computer program capable of running on the processor.

[0058] When the third processor runs the computer program, it executes the steps of any one of the methods described above on the third network device side.

[0059] At least one embodiment of the present invention provides a storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the above methods.

[0060] The information processing method, apparatus, device, and storage medium provided in this invention embodiment receive a URI message sent by a higher-level network device. The URI message includes a first field, a second field, a third field, and a fourth field. The first field represents host information, which consists of the identifiers of at least two network devices connected to a hierarchically described second network device. The second field represents a resource path used to acquire resource data. The third field represents a device identifier, which is the identifier of a lower-level device managed by a target network device connected to the second network device. The fourth field represents resource attributes, which are the attributes of the resource data under the resource path. Based on the first field, the system determines whether to process the URI message locally. If it determines that it will not process the URI message locally, it forwards the URI message to the next-level network device. The higher-level network device, the first network device, and the next-level network device are heterogeneous devices. Using the technical solution provided in this invention embodiment, resource information access is achieved between multiple levels of network devices in an IoT scenario using URI messages, thereby realizing unified resource information interaction between multiple levels and heterogeneous devices, and achieving communication management between multiple levels of network devices. Attached Figure Description

[0061] Figure 1 This is a schematic diagram of the implementation flow of the information processing method according to an embodiment of the present invention. Figure 1 ;

[0062] Figure 2 This is a schematic diagram of the implementation flow of the information processing method according to an embodiment of the present invention. Figure 2 ;

[0063] Figure 3 This is a schematic diagram of the implementation flow of the information processing method according to an embodiment of the present invention. Figure 3 ;

[0064] Figure 4 This is a schematic diagram of the system architecture for the application of the information processing method in this embodiment of the invention;

[0065] Figure 5 This is a schematic diagram of multiple layers of network devices attached to the Internet of Things platform in an embodiment of the present invention;

[0066] Figure 6 This is a schematic diagram of the various functional modules included in the URI parser device according to an embodiment of the present invention;

[0067] Figure 7 This is a schematic diagram of the routing table in an embodiment of the present invention;

[0068] Figure 8 This is a schematic diagram illustrating the specific implementation flow of the information processing method according to an embodiment of the present invention;

[0069] Figure 9 This is a schematic diagram of the composition structure of the information processing device according to an embodiment of the present invention. Figure 1 ;

[0070] Figure 10 This is a schematic diagram of the composition structure of the information processing device according to an embodiment of the present invention. Figure 2 ;

[0071] Figure 11 This is a schematic diagram of the composition structure of the information processing device according to an embodiment of the present invention. Figure 3 ;

[0072] Figure 12 This is a schematic diagram of the composition structure of the first network device according to an embodiment of the present invention;

[0073] Figure 13 This is a schematic diagram of the composition structure of the second network device according to an embodiment of the present invention;

[0074] Figure 14 This is a schematic diagram of the composition structure of the third network device according to an embodiment of the present invention. Detailed Implementation

[0075] Before introducing the technical solutions of the embodiments of the present invention, the relevant technologies will be explained first.

[0076] In related technologies, Uniform Resource Identifiers (URIs) are used to uniquely identify the numbers or names of elements or attributes. Uniform Resource Locators (URLs) are a subset of URIs. URLs are strings describing information resources on the Internet, primarily used in various WWW client and server programs. Using URLs allows for a unified format to describe various information resources, including files, server addresses, and directories. A URL is one implementation of the URI concept. The general format of a URL is protocol: / / hostname[:port] / path / [;parameters][?query]#fragment; where items enclosed in square brackets [] are optional.

[0077] In an IoT environment, IoT platforms access terminals by initiating requests to the terminals over the network and obtaining response data, completing data interaction during the request and response process. The universality, scalability, and content of the request and response interactions between the IoT platform and terminals directly impact network communication efficiency. In IoT technology, attributes, services, and events are fundamental resources defined by the object model. Initially, a unique numerical value or string can represent an attribute, service, or event, allowing the platform to match terminal resources using these unique values.

[0078] In a real-world IoT environment, terminals need to have multi-level description capabilities, meaning that multiple layers of network devices are connected to the IoT platform. The need for communication management of these multi-level network devices is very common in IoT environments. However, due to the high complexity of IoT requirements, different types of devices on different networks need to coordinate with each other to complete their respective tasks. This necessitates unified management through various gateway devices, enabling communication with lower-level devices through different types of gateways.

[0079] However, currently, there is a lack of a unified and effective method for accessing resource information between diverse, multi-level, heterogeneous, and cross-network devices. For example, in a real-world local area network (LAN) environment, an IoT platform connects to multiple levels of network devices. An IoT gateway, as the first-level network device, connects to the IoT platform via a wide area network (WAN), local area network (LAN), or cellular network. Second-level network devices connected to this gateway communicate with it via Wi-Fi, LAN, serial ports, etc. Third-level network devices connect to the second-level devices via serial ports, and fourth-level network devices connect to the third-level devices through other means, and so on. Furthermore, communication between upper and lower level devices requires adherence to the same physical links and interfaces. However, in multi-level, heterogeneous, and cross-network scenarios, it is impossible to achieve command transmission across different physical links using a unified command method.

[0080] Based on this, in this embodiment of the invention, a URI message sent by a higher-level network device is received; the URI message includes a first field, a second field, a third field, and a fourth field; the first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device; the second field represents a resource path, which is used to obtain resource data; the third field represents a device identifier, which is the identifier of a lower-level device managed by the target network device connected to the second network device; the fourth field represents resource attributes, which are the attributes of the resource data under the resource path; based on the first field, it is determined whether to process the URI message locally; if it is determined that it will not process the URI message locally, the URI message is forwarded to the next-level network device; wherein, the higher-level network device, the first network device, and the next-level network device are heterogeneous devices.

[0081] Figure 1 This is a schematic diagram illustrating the implementation flow of the information processing method according to an embodiment of the present invention, applied to a first network device, such as... Figure 1 As shown, the method includes steps 101 to 103:

[0082] Step 101: Receive a URI message sent by the upstream network device; the URI message includes a first field, a second field, a third field, and a fourth field; the first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device; the second field represents a resource path, which is used to obtain resource data; the third field represents a device identifier, which is the identifier of the downstream device managed by the target network device connected to the second network device; the fourth field represents resource attributes, which are the attributes of the resource data under the resource path.

[0083] It is understood that the URI message can be generated by the second network device and forwarded by the second network device to the next level network device.

[0084] It is understood that the at least two network devices connected to the second network device can refer to multiple first network devices and third network devices.

[0085] It is understood that the second network device is used to generate the URI message and forward it to the first network device at the next level; the first network device at the next level is used to forward the URI message level by level; and the third network device is used as the last-level network device to obtain resource data.

[0086] It is understood that the third network device can also forward the acquired resource data to the previous level network device; the previous level first network device is also used to forward the resource data level by level; and the second network device is also used to receive the resource data.

[0087] It should be noted that the second network device, multiple first network devices, and the third network device can be heterogeneous devices. That is, the interfaces between the upper-level devices and the lower-level devices can be different, or the upper-level devices and the lower-level devices can belong to different networks.

[0088] For example, the second network device is represented by device 1, multiple first network devices are represented by device 2, device 3, and device 4, and the third network device is represented by device 5. Among them, device 1 and device 2 belong to the Internet of Things (IoT) devices, device 3 and device 4 belong to the Wi-Fi network devices, and device 5 belongs to the 5G network devices. Moreover, the communication interface between device 1 and device 2 is WLAN, the communication interface between device 2 and device 3 is serial port, the communication interface between device 3 and device 4 is serial port, and the communication interface between device 4 and device 5 is LAN.

[0089] Table 1 illustrates the four types of fields included in the URI message. As shown in Table 1, the URI message includes a first field, a second field, a third field, and a fourth field. The first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchical second network device. The second field represents a resource path, which is used to obtain resource data. The third field represents a device identifier, which is the identifier of the subordinate device managed by the target network device connected to the second network device. The fourth field represents resource attributes, which are the attributes of the resource data under the resource path.

[0090] URI message illustrate First field (HOST) Indicates host information The second field (PATH) Indicates resource path The third field (ID) Indicates device identification The fourth field (PROPERTY) Indicates resource attributes

[0091] Table 1

[0092] Here, assuming the first field is represented by HOST, the second field by PATH, the third field by ID, and the fourth field by PROPERTY, then the URI message can be represented as: [HOST] / PATH / [@[ID]] / #[PROPERTY].

[0093] The HOST field describes the routing information of network devices (also called hosts) at various levels connected to the second network device, and is used to set the resource location of the target network devices connected to the second network device.

[0094] The PATH (resource path) field is used to describe the resource path.

[0095] The ID (Device Identifier) ​​field is used to describe the specific identification information of the subordinate devices managed by the target network device connected to the second network device.

[0096] The PROPERTY field is used to describe the attribute information of the specified resource data.

[0097] Here, the HOST field can be defined using a "." to represent the identification information of network devices at various levels connected to the second network device. It should be noted that when the host information only pertains to the next-level receiving device, the content of this field can be omitted.

[0098] Here, PATH can be defined using "." to define hierarchical descriptions. It is required that no other special characters be included besides the hierarchical descriptor. For example: "Device.WiFi". Resource paths can be used to describe multi-level device paths.

[0099] Here, the ID can be a string starting with the @ character. It must not contain the special characters "@", " / ", or "#". In the URI message description of the ID (device identifier), there are two possible omissions: First, it indicates that under the specified resource path, it refers to "all devices", for example: "Subdev.WiFi / @ / #State"; second, it indicates that under the specified resource path, no subordinate network devices are defined, referring to "the device itself", for example: "DeviceInfo / #State".

[0100] Here, PROPERTY can be represented by a string that begins with the # character. It must not contain any special characters other than underscores. In the description of resource attributes in the URI message, omissions are allowed, including: information representing all resources under the resource path, such as "DeviceInfo / #". The URI message supports retrieving single or multiple attributes of resources under the PATH path.

[0101] Table 2 shows the representation of the first field (HOST). As shown in Table 2, assuming the first field (HOST) is represented by "DeviceA.DeviceB.DeviceC", where "DeviceA" is the identifier of the highest-level network device connected to the second network device, "DeviceB" is the identifier of the next-level network device of "DeviceA", and "DeviceC" is the identifier of the next-level network device of "DeviceB".

[0102]

[0103] Table 2

[0104] Table 3 shows the representation and combined meanings of the second field (PATH), the third field (ID), and the fourth field (PROPERTY).

[0105]

[0106] Table 3

[0107] Step 102: Based on the first field, determine whether to perform local processing on the URI message.

[0108] In practical applications, since the first field in the URI message uses a hierarchical description to represent the network device identifiers at each level, the first network device, after receiving the URI message, can determine whether to treat the URI message as a local message for local processing based on the first field.

[0109] Based on this, in one embodiment, determining whether to perform local processing on the URI message based on the first field includes:

[0110] Match its own network device identifier with at least two network device identifiers described hierarchically in the first field;

[0111] If its own network device identifier does not match the last of the at least two network device identifiers described hierarchically in the first field, then it will not perform local processing on the URI message.

[0112] For example, as shown in Table 4, suppose the first field (HOST) in the URI message is represented by "DeviceA.DeviceB.DeviceC", where "DeviceA" is the identifier of the highest-level network device under the second network device, "DeviceB" is the identifier of the next-level network device of "DeviceA" and the identifier of the upper-level network device of "DeviceC", and "DeviceC" is the identifier of the next-level network device of "DeviceB". Assuming the identifier of the first network device is the identifier of the highest-level network device, DeviceA, since the identifier of the first network device does not match the last network device identifier among the at least two network device identifiers described hierarchically in the first field, it will not process the URI message locally and will forward the URI message to the next-level network device. Similarly, when a next-level network device receives a URI message, if its own network device identifier does not match the last network device identifier among the at least two network device identifiers described hierarchically in the first field, it will not process the URI message locally and will forward the URI message to the next-level network device, thus achieving hierarchical matching and forwarding.

[0113] The identifier of the first network device First field (HOST) DeviceA "DeviceA.DeviceB.DeviceC" DeviceB "DeviceA.DeviceB.DeviceC"

[0114] Table 4

[0115] Step 103: If it is determined that the device does not perform local processing on the URI message, then the URI message is forwarded to the next-level network device; wherein the previous-level network device, the first network device, and the next-level network device are heterogeneous devices.

[0116] In practical applications, since the first field in the URI message uses a hierarchical description to represent the network device identifiers at each level, the first network device, upon receiving the URI message, can determine whether it will treat the URI message as a local message for local processing based on the first field. If it determines that it will not treat the URI message as a local message for local processing, it forwards the URI message to the next-level network device for further judgment. To facilitate the next-level network device's judgment, the network device identifier belonging to itself in the first field can be removed from the network device identifiers in the hierarchical description.

[0117] Based on this, in one embodiment, forwarding the URI message to the next-level network device includes:

[0118] Remove the network device identifier belonging to itself from the first field of the URI message, and forward the URI message to the next level network device.

[0119] For example, as shown in Table 5, suppose the first field (HOST) in the URI message is represented by "DeviceA.DeviceB.DeviceC", where "DeviceA" is the identifier of the highest-level network device under the second network device, "DeviceB" is the identifier of the next-level network device of "DeviceA" and the identifier of the upper-level network device of "DeviceC", and "DeviceC" is the identifier of the next-level network device of "DeviceB". If the identifier of the first network device is the identifier of the highest-level network device, DeviceA, since the identifier of the first network device does not match the last network device identifier among the at least two network device identifiers described hierarchically in the first field, it will not perform local processing on the URI message. Instead, it will remove the network device identifier belonging to itself from the first field of the URI message and forward it to the next-level network device. Similarly, when a next-level network device receives a URI message, if its own network device identifier does not match the last of the at least two network device identifiers described hierarchically in the first field, it will not process the URI message locally, but will remove the network device identifier belonging to itself in the first field of the URI message and forward it to the next-level network device, thereby achieving hierarchical matching and hierarchical forwarding.

[0120]

[0121] Table 5

[0122] In practical applications, since the first field in the URI message uses a hierarchical description to represent the network device identifiers at each level, after receiving the URI message, the first network device can determine whether it will treat the URI message as a local message for local processing based on the first field. If it determines that it will not treat the URI message as a local message for local processing, it forwards the URI message to the next-level network device. If the next-level network device determines that it will treat the URI message as a local message for local processing, it can obtain resource data based on the other fields in the URI message besides the first field.

[0123] Based on this, in one embodiment, the method further includes:

[0124] Receive a response message sent by the next-level network device; the response message carries resource data;

[0125] The resource data is determined by a third network device that performs local processing of the URI message based on the second, third, and fourth fields.

[0126] Here, the response message may also carry the identification information of the second network device, so that the first network devices at each level can forward the response message level by level and finally send the response message to the second network device.

[0127] Here, the response message for a request to retrieve resource data with multiple attributes needs to include the attribute name information and the corresponding attribute value.

[0128] For example, as shown in Table 6, in the case of various URI message descriptions, a specific attribute identifier (response KEY) is set in the response message.

[0129]

[0130]

[0131] Table 6

[0132] In practical applications, network devices at each level can send session messages upwards one by one. Each network device can update its own routing table based on the session messages and send the routing table upwards one by one. In this way, after the second network device receives the routing table, it can determine the first field in the URI message based on the status of the network devices at each level in the routing table.

[0133] Based on this, in one embodiment, the method further includes:

[0134] Receive session messages sent by the next-level network device;

[0135] The routing table is updated based on the session messages sent by the next-level network device; the routing table stores the status of the first network device and the next-level network device of the first network device.

[0136] The routing table is sent to the next higher-level network device.

[0137] It is understandable that session messages are initiated by the next-level network device and sent to the next-level network device, containing information such as registration, offline status, heartbeat, and device changes. When a device receives a registration or offline message, it needs to maintain and update the routing table of the next-level device and forward the status information to the next-level network device, which then processes it (updates the routing table). This enables the next-level device to manage its next-level devices.

[0138] The embodiments of the present invention have the following advantages:

[0139] (1) By using URI messages, resource information can be obtained between multiple network devices in the Internet of Things scenario. This avoids the problem that the communication methods and protocols are not uniform between devices of different hardware types and networks, which leads to the inability to achieve message transmission between multiple levels of devices. It can realize unified resource information interaction between multiple levels and heterogeneous devices, and realize communication management between multiple levels of network devices.

[0140] (2) Set the format of URI message and response message to optimize the semantics and data description of resource requests and matching in the Internet of Things field, better solve the problem of resource access between multi-level heterogeneous and cross-network terminals, realize the resource management capability of multi-level devices, and the resource request capability for lower-level devices, and realize the return of determined resource data to the network device that initiated the URI message.

[0141] Figure 2 This is a schematic diagram illustrating the implementation flow of the information processing method according to an embodiment of the present invention, applied to a second network device, such as... Figure 2 As shown, the method includes steps 201 to 202:

[0142] Step 201: Generate a URI message; the URI message includes a first field, a second field, a third field, and a fourth field; the first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device; the second field represents a resource path, which is used to obtain resource data; the third field represents a device identifier, which is the identifier of the subordinate device managed by the target network device connected to the second network device; the fourth field represents resource attributes, which are the attributes of the resource data under the resource path.

[0143] It is understood that the URI message can be generated by the second network device and forwarded by the second network device to the next level network device.

[0144] It is understood that the at least two network devices connected to the second network device can refer to multiple first network devices and third network devices.

[0145] It is understood that the second network device is used to generate the URI message and forward it to the first network device at the next level; the first network device at the next level is used to forward the URI message level by level; and the third network device is used as the last-level network device to obtain resource data.

[0146] It is understood that the third network device can also forward the acquired resource data to the previous level network device; the previous level first network device is also used to forward the resource data level by level; and the second network device is also used to receive the resource data.

[0147] It should be noted that the second network device, multiple first network devices, and the third network device can be heterogeneous devices.

[0148] Step 202: Send the URI message to the next-level network device; the first field is used for the next-level network device to determine whether it will process the URI message locally. If it determines that it will not process the URI message locally, it will forward the URI message to the next-level network device; wherein, the second network device and the next-level network device are heterogeneous devices.

[0149] In practical applications, since the first field in the URI message uses a hierarchical description to represent the network device identifiers at each level, after receiving the URI message, the first network device can determine whether it will process the URI message locally based on the first field. If it determines that it will not process the URI message locally, it forwards the URI message to the next-level network device. If the next-level network device determines that it will process the URI message locally, it can obtain resource data based on the other fields in the URI message besides the first field, and forward it to the second network device through the first network device at each level.

[0150] Based on this, in one embodiment, the method further includes:

[0151] Receive a response message sent by the next-level network device; the response message carries resource data;

[0152] The resource data is determined by the network device that performs local processing of the URI message based on the second field, and the third and / or fourth field.

[0153] In practical applications, network devices at each level can send session messages upwards one by one. Each network device can update its own routing table based on the session messages and send the routing table upwards one by one. In this way, after the second network device receives the routing table, it can determine the first field in the URI message based on the status of the network devices at each level in the routing table.

[0154] Based on this, in one embodiment, the method further includes:

[0155] Receive routing tables sent by the next-level network devices; the routing tables contain the status of network devices at each level;

[0156] Based on the routing table, at least two network device identifiers described hierarchically in the first field are determined.

[0157] It is understandable that session messages are initiated by the next-level network device and sent to the next-level network device, containing information such as registration, offline status, heartbeat, and device changes. When a device receives a registration or offline message, it needs to maintain and update the routing table of the next-level device and forward the status information to the next-level network device, which then processes it (updates the routing table). This enables the next-level device to manage its next-level devices.

[0158] The embodiments of the present invention have the following advantages:

[0159] (1) By using URI messages, resource information can be obtained between multiple network devices in the Internet of Things scenario. This avoids the problem that the communication methods and protocols are not uniform between devices of different hardware types and networks, which leads to the inability to achieve message transmission between multiple levels of devices. It can realize unified resource information interaction between multiple levels and heterogeneous devices, and realize communication management between multiple levels of network devices.

[0160] (2) Set the format of URI message and response message to optimize the semantics and data description of resource requests and matching in the Internet of Things field, better solve the problem of resource access between multi-level heterogeneous and cross-network terminals, realize the resource management capability of multi-level devices, and the resource request capability for lower-level devices, and realize the return of determined resource data to the network device that initiated the URI message.

[0161] Figure 3 This is a schematic diagram illustrating the implementation flow of the information processing method according to an embodiment of the present invention, applied to a third network device, such as... Figure 3 As shown, the method includes steps 301 to 303:

[0162] Step 301: Receive a URI message sent by the upstream network device; the URI message includes a first field, a second field, a third field, and a fourth field; the first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device; the second field represents a resource path, which is used to obtain resource data; the third field represents a device identifier, which is the identifier of the downstream device managed by the target network device connected to the second network device; the fourth field represents resource attributes, which are the attributes of the resource data under the resource path.

[0163] It is understood that the URI message can be generated by the second network device and forwarded by the second network device to the next level network device.

[0164] It is understood that the at least two network devices connected to the second network device can refer to multiple first network devices and third network devices.

[0165] It is understood that the second network device is used to generate the URI message and forward it to the first network device at the next level; the first network device at the next level is used to forward the URI message level by level; and the third network device is used as the last-level network device to obtain resource data.

[0166] It is understood that the third network device can also forward the acquired resource data to the previous level network device; the previous level first network device is also used to forward the resource data level by level; and the second network device is also used to receive the resource data.

[0167] It should be noted that the second network device, multiple first network devices, and the third network device can be heterogeneous devices.

[0168] Step 302: Determine whether to perform local processing on the URI message based on the first field; if it is determined that it will perform local processing on the URI message, obtain resource data based on the second, third, and fourth fields.

[0169] In practical applications, since the first field in the URI message uses a hierarchical description to represent the network device identifiers at each level, the first network device, after receiving the URI message, can determine whether to treat the URI message as a local message for local processing based on the first field.

[0170] Based on this, in one embodiment, determining whether to perform local processing on the URI message based on the first field includes:

[0171] Match its own network device identifier with at least two network device identifiers described hierarchically in the first field;

[0172] If its own network device identifier matches the last of at least two network device identifiers described hierarchically in the first field, then it performs local processing on the URI message.

[0173] Step 303: Send the response message to the upstream network device; the response message carries the resource data; wherein the third network device and the upstream network device are heterogeneous devices.

[0174] In practical applications, network devices at each level can send session messages upwards one by one. Each network device can update its own routing table based on the session messages and send the routing table upwards one by one. In this way, after the second network device receives the routing table, it can determine the first field in the URI message based on the status of the network devices at each level in the routing table.

[0175] Based on this, in one embodiment, the method further includes:

[0176] Send session messages to the next higher-level network device;

[0177] The session message is used to update the routing table of the upstream network device; the routing table stores the status of the third network device and the upstream network device of the third network device.

[0178] Here, the upstream network device can report session messages level by level, update its own routing table according to the session messages, and send the routing table upwards level by level. In this way, after the second network device receives the routing table, it can determine the first field in the URI message according to the status of the network devices at each level in the routing table.

[0179] The embodiments of the present invention have the following advantages:

[0180] (1) By using URI messages, resource information can be obtained between multiple network devices in the Internet of Things scenario. This avoids the problem that the communication methods and protocols are not uniform between devices of different hardware types and networks, which leads to the inability to achieve message transmission between multiple levels of devices. It can realize unified resource information interaction between multiple levels and heterogeneous devices, realize communication management between multiple levels of network devices and routing capabilities on multiple levels of downstream devices.

[0181] (2) Set the format of URI message and response message to optimize the semantics and data description of resource requests and matching in the Internet of Things field, better solve the problem of resource access between multi-level heterogeneous and cross-network terminals, realize the resource management capability of multi-level devices, and the resource request capability for lower-level devices, and realize the return of determined resource data to the network device that initiated the URI message.

[0182] Figure 4 This is a schematic diagram of the system architecture for the application of the information processing method in this embodiment of the invention, such as... Figure 4 As shown, the system includes:

[0183] A first network device is used to generate a URI message; the URI message includes a first field, a second field, a third field, and a fourth field; the first field represents host information, which consists of the identifiers of at least two network devices connected to the second network device in a hierarchical description; the second field represents a resource path, which is used to obtain resource data; the third field represents a device identifier, which is the identifier of a lower-level device managed by the target network device connected to the second network device; the fourth field represents resource attributes, which are the attributes of the resource data under the resource path; and the device sends the URI message to the next-level network device.

[0184] The second network device is used to receive URI messages sent by the upper-level network device; determine whether it should process the URI message locally based on the first field; if it determines that it will not process the URI message locally, it forwards the URI message to the next-level network device.

[0185] The third network device is used to receive URI messages sent by the upper-level network device; determine whether it should process the URI message locally based on the first field; if it determines that it should process the URI message locally, it obtains resource data based on the second, third, and fourth fields; and sends a response message to the upper-level network device; the response message carries the resource data.

[0186] Among them, the first network device, the second network device, and the third network device are heterogeneous devices.

[0187] It should be noted that the second network device can specifically refer to the Internet of Things (IoT) platform, and the multiple first network devices and the third network device can refer to multiple layers of network devices attached to the IoT platform.

[0188] here, Figure 5 This is a diagram illustrating multiple layers of network devices connected to an IoT platform, such as... Figure 5 As shown, URI resolver devices can be set up in the network devices of multiple layers under the IoT platform to complete the parsing and distribution of URI messages, and realize the transmission of command messages (carrying URI messages) and resource acquisition to multi-level devices.

[0189] here, Figure 6 This is a schematic diagram of the various functional modules included in a URI resolver device, such as... Figure 6 As shown, a URI resolver apparatus may include:

[0190] The instruction message receiving module is responsible for receiving instruction messages sent by the upstream network device. These instruction messages carry a URI message. The URI message is used to request resource data to be reported by the target network device connected to the second network device; and to forward the URI message to the HOST resolution module.

[0191] The HOST resolution module parses the first field (HOST host information) of the URI message. If the URI message is not processed locally as a local message, it matches the identifier of the next-level network device in the first field (HOST) of the URI message with the identifier of the next-level network device in the routing table to find the physical communication module and physical address of the corresponding next-level network device, and sends the command message through the command message sending module. If the URI message is processed locally as a local message, it sends the URI message to the URI local resolution module.

[0192] The instruction message sending module is used to forward instruction messages to the next-level network device.

[0193] The URI local parsing module is used to parse the second field (PATH), the third field (ID), and the fourth field (PROPERTY) in the URI message, excluding the first field (HOST), and send the parsing results to the resource data acquisition module.

[0194] The resource data acquisition module is used to match and call the local resource data acquisition interface based on the parsing result of the URI message, obtain resource data, package the obtained resource data, and transfer it to the data message sending module.

[0195] The data message sending module is used to send the resource data to the next-level network device in the form of a response message.

[0196] The data message receiving module is used to receive response messages sent by the next-level network device; the response messages carry resource data; and forward the response messages to the previous-level network device.

[0197] The session message sending module is used to send session messages to the next higher-level network device.

[0198] Session messages are initiated by lower-level network devices and sent to higher-level network devices, containing information such as registration, offline status, heartbeats, and device changes. Upon receiving registration or offline messages, a device needs to maintain and update its lower-level device routing table and forward the status information to the higher-level network device, which then processes the information (updates its routing table), thus enabling the higher-level device to manage its lower-level devices. Heartbeat messages are initiated periodically by lower-level network devices. Upon receiving a heartbeat message, the device updates its lifetime. When the time since the last heartbeat of a lower-level network device exceeds a threshold, the device's status in the lower-level device's routing table is updated.

[0199] The session message receiving module is used to receive session messages sent by the next-level network device and forward the session messages to the session management module.

[0200] The session management module receives session messages such as deregistration and heartbeats from lower-level network devices to maintain, manage, and update their routing tables. When a lower-level network device has a physical channel, it registers its identification information with the registration management module, generating a routing table. Data communication is initiated by the lower-level network device and uses an agreed-upon communication protocol.

[0201] It should be noted that the URI resolver device is characterized by being suitable for hierarchical Internet of Things (IoT) networks, solving the message passing problem between multi-level network devices, and the physical channels and transmission protocols between devices at different levels do not affect the technical solution provided by this invention.

[0202] here, Figure 7 This is a diagram of the routing table, such as... Figure 7 As shown, the routing table is used to record the type of the lower-level device, physical module information, lower-level device identifier, lower-level device physical address information, etc.

[0203] Figure 8 This is a schematic diagram illustrating the specific implementation flow of the information processing method according to an embodiment of the present invention, such as... Figure 8 As shown, the method includes steps 801 to 808:

[0204] Step 801: The second network device generates an instruction message; the instruction message carries a URI message; the URI message includes a first field, a second field, a third field, and a fourth field; and forwards the instruction information to the next-level network device.

[0205] Here, the first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device; the second field represents a resource path, which is used to obtain resource data; the third field represents a device identifier, which is the identifier of the subordinate device managed by the target network device connected to the second network device; and the fourth field represents a resource attribute, which is the attribute of the resource data under the resource path.

[0206] Here, if the second network device determines that the highest-level network device identifier described by the first field (HOST) belongs to the lower-level device identifier, and can match the corresponding device identifier in the lower-level device routing table, and can obtain its corresponding physical link information, then it will forward the instruction message carrying the URI message through the specified physical link.

[0207] For example, the first field (HOST) identifies three network devices in a hierarchical manner as "DeviceA.DeviceB.DeviceC". The highest-level network device, "DeviceA", is its subordinate device and forwards the instruction message to "DeviceA" through the matched physical link.

[0208] Step 802: The first network device determines whether it has received instruction information sent by the upper-level network device; if it has received instruction information sent by the upper-level network device, then proceed to step 803.

[0209] Step 803: Parse the first field in the URI message.

[0210] Step 804: Based on the result of parsing the first field in the URI message, determine whether to perform local processing on the URI message; if it is determined that it will not perform local processing on the URI message, then proceed to step 805; otherwise, proceed to step 806.

[0211] Step 805: Locate the physical link recorded in the routing table and forward the URI message to the next-level network device.

[0212] Here, "DeviceA," as the next-level network device, receives this instruction message. It parses the URI information in the message to verify if its own network device identifier matches the last network device identifier in the first field (HOST), thus verifying the target network device in the URI message. If it determines that it will not process the URI message locally, it removes its own network device identifier from the first field (HOST) of the URI information. For example, assuming the first field (HOST) describes three network device identifiers hierarchically as "DeviceA.DeviceB.DeviceC," removing its highest-level network device identifier "DeviceA" results in "DeviceB.DeviceC." Since network device identifier "DeviceB" is a subordinate device of "DeviceA," the instruction message is forwarded to "DeviceB" by looking up the physical link of the next-level network device recorded in the routing table; if no physical link of the next-level network device is found, the instruction message is discarded.

[0213] Here, "DeviceB," as the next-level network device, will receive this instruction message and perform a second parsing of the updated URI information. Specifically, it will retrieve the highest-level network device identifier from the first field (HOST) to verify whether its own network device identifier matches the last network device identifier in the first field (HOST), thus validating the target network device in the URI message. If it determines that it will not process the URI message locally, it will remove its own network device identifier from the first field (HOST) of the URI information.

[0214] Repeat the above process to achieve a cyclical approach of matching and forwarding network device identifiers at multiple levels described by the hierarchical structure of the first field (HOST) until there is a lower-level device identifier in the first field (HOST). If so, the instruction message is considered a local message, and the other fields in the URI message other than the first field are further parsed and processed.

[0215] Step 806: The third network device determines that it will perform local processing on the URI message and parse the second, third, and fourth fields in the URI message.

[0216] Step 807: Obtain resource data based on the second, third, and fourth fields.

[0217] Step 808: Send a response message to the upstream network device; the response message carries the resource data.

[0218] Here, the response message is initiated by a third network device. After obtaining resource data according to the resource acquisition interface specified in the URI message, the data is packaged and sent to the next higher-level network device.

[0219] Here, the response message may also contain the identifier (ID) information of the second network device, so that the response message can be forwarded to the second network device level by level.

[0220] To implement the information processing method of the present invention, the present invention also provides an information processing device. Figure 9 This is a schematic diagram of the composition structure of the information processing device according to an embodiment of the present invention, such as... Figure 9 As shown, the device includes:

[0221] The first receiving unit 91 is configured to receive a URI message sent by a higher-level network device. The URI message includes a first field, a second field, a third field, and a fourth field. The first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device. The second field represents a resource path, which is used to obtain resource data. The third field represents a device identifier, which is the identifier of a lower-level device managed by the target network device connected to the second network device. The fourth field represents a resource attribute, which is the attribute of the resource data under the resource path.

[0222] The first processing unit 92 is configured to determine, based on the first field, whether it will perform local processing on the URI message; if it determines that it will not perform local processing on the URI message, it will forward the URI message to the next-level network device.

[0223] Among them, the upstream network device, the first network device, and the downstream network device are heterogeneous devices.

[0224] In one embodiment, the first processing unit 92 is specifically used for:

[0225] Match its own network device identifier with at least two network device identifiers described hierarchically in the first field;

[0226] If its own network device identifier does not match the last of the at least two network device identifiers described hierarchically in the first field, then it will not perform local processing on the URI message.

[0227] In one embodiment, the first processing unit 92 is specifically used for:

[0228] Remove the network device identifier belonging to itself from the first field of the URI message, and forward the URI message to the next level network device.

[0229] In one embodiment, the device is further configured to:

[0230] Receive a response message sent by the next-level network device; the response message carries resource data;

[0231] The resource data is determined by a third network device that performs local processing of the URI message based on the second, third, and fourth fields.

[0232] In one embodiment, the device is further configured to:

[0233] Receive session messages sent by the next-level network device;

[0234] The routing table is updated based on the session messages sent by the next-level network device; the routing table stores the status of the first network device and the next-level network device of the first network device.

[0235] The routing table is sent to the next higher-level network device.

[0236] In practical applications, the first receiving unit 91 can be implemented by the communication interface in the information processing device; the first processing unit 92 can be implemented by the processor in the information processing device.

[0237] It should be noted that the information processing device provided in the above embodiments is only illustrated by the division of the above program modules. In practical applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the information processing device and the information processing method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0238] To implement the information processing method of the present invention, the present invention also provides an information processing device. Figure 10 This is a schematic diagram of the composition structure of the information processing device according to an embodiment of the present invention, such as... Figure 10 As shown, the device includes:

[0239] The second processing unit 101 is used to generate a URI message; the URI message includes a first field, a second field, a third field, and a fourth field; the first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device; the second field represents a resource path, which is used to obtain resource data; the third field represents a device identifier, which is the identifier of a subordinate device managed by the target network device connected to the second network device; the fourth field represents a resource attribute, which is the attribute of the resource data under the resource path.

[0240] The first sending unit 102 is used to send the URI message to the next-level network device; the first field is used for the next-level network device to determine whether it will process the URI message locally. If it determines that it will not process the URI message locally, it will forward the URI message to the next-level network device.

[0241] Among them, the second network device and the next-level network device are heterogeneous devices.

[0242] In one embodiment, the device is further configured to:

[0243] Receive a response message sent by the next-level network device; the response message carries resource data;

[0244] The resource data is determined by a third network device that performs local processing of the URI message based on the second, third, and fourth fields.

[0245] In one embodiment, the device is further configured to:

[0246] Receive routing tables sent by the next-level network devices; the routing tables contain the status of network devices at each level;

[0247] Based on the routing table, at least two network device identifiers described hierarchically in the first field are determined.

[0248] In practical applications, the first sending unit 102 can be implemented by the communication interface in the information processing device; the second processing unit 101 can be implemented by the processor in the information processing device.

[0249] It should be noted that the information processing device provided in the above embodiments is only illustrated by the division of the above program modules. In practical applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the information processing device and the information processing method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0250] To implement the information processing method of the present invention, the present invention also provides an information processing device. Figure 11 This is a schematic diagram of the composition structure of the information processing device according to an embodiment of the present invention, such as... Figure 11 As shown, the device includes:

[0251] The second receiving unit 111 is used to receive a URI message sent by the upper-level network device; the URI message includes a first field, a second field, a third field, and a fourth field; the first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device; the second field represents a resource path, which is used to obtain resource data; the third field represents a device identifier, which is the identifier of the lower-level device managed by the target network device connected to the second network device; the fourth field represents a resource attribute, which is the attribute of the resource data under the resource path.

[0252] The third processing unit 112 is configured to determine whether it will perform local processing on the URI message based on the first field; if it determines that it will perform local processing on the URI message, it will obtain resource data based on the second, third and fourth fields.

[0253] The second sending unit 113 is used to send a response message to the upper-level network device; the response message carries the resource data.

[0254] Among them, the third network device and the previous level network device are heterogeneous devices.

[0255] In one embodiment, the third processing unit 112 is specifically used for:

[0256] Match its own network device identifier with at least two network device identifiers described hierarchically in the first field;

[0257] If its own network device identifier matches the last of at least two network device identifiers described hierarchically in the first field, then it performs local processing on the URI message.

[0258] In one embodiment, the second transmitting unit 113 is further configured to:

[0259] Send session messages to the next higher-level network device;

[0260] The session message is used to update the routing table of the upstream network device; the routing table stores the status of the third network device and the upstream network device of the third network device.

[0261] In practical applications, the second receiving unit 111 and the second sending unit 113 can be implemented by the communication interface in the information processing device; the third processing unit 112 can be implemented by the processor in the information processing device.

[0262] It should be noted that the information processing device provided in the above embodiments is only illustrated by the division of the above program modules. In practical applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the information processing device and the information processing method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0263] This invention also provides a first network device, such as... Figure 12 As shown, it includes:

[0264] The first communication interface 121 is capable of exchanging information with other devices;

[0265] The first processor 122, connected to the first communication interface 121, is used to execute the methods provided by one or more technical solutions on the first network device side when running a computer program. The computer program is stored in the first memory 123.

[0266] It should be noted that the specific processing procedures of the first processor 122 and the first communication interface 121 are detailed in the method embodiment and will not be repeated here.

[0267] Of course, in practical applications, the various components in the first network device 120 are coupled together via a bus system 124. It can be understood that the bus system 124 is used to implement communication between these components. In addition to a data bus, the bus system 124 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 12 The general labeled all buses as Bus System 124.

[0268] The first memory 123 in this embodiment is used to store various types of data to support the operation of the first network device 120. Examples of such data include any computer program used to operate on the first network device 120.

[0269] The methods disclosed in the above embodiments of this application can be applied to the first processor 122, or implemented by the first processor 122. The first processor 122 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the first processor 122. The first processor 122 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 122 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly reflected as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the first memory 123. The first processor 122 reads the information in the first memory 123 and completes the steps of the aforementioned method in combination with its hardware.

[0270] This invention also provides a second network device, such as... Figure 13 As shown, it includes:

[0271] The second communication interface 131 is capable of exchanging information with other devices;

[0272] The second processor 132, connected to the second communication interface 131, is used to execute the methods provided by one or more technical solutions on the second network device side when running a computer program. The computer program is stored in the second memory 133.

[0273] It should be noted that the specific processing procedures of the second processor 132 and the second communication interface 131 are detailed in the method embodiment and will not be repeated here.

[0274] Of course, in practical applications, the various components in the second network device 130 are coupled together via a bus system 134. It is understood that the bus system 134 is used to implement communication between these components. In addition to a data bus, the bus system 134 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 13 The general labeled all buses as Bus System 134.

[0275] The second memory 133 in this embodiment is used to store various types of data to support the operation of the second network device 130. Examples of such data include any computer programs used to operate on the second network device 130.

[0276] The methods disclosed in the embodiments of this application can be applied to, or implemented by, the second processor 132. The second processor 132 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the integrated logic circuitry of the hardware or by instructions in the form of software within the second processor 132. The second processor 132 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The second processor 132 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, specifically a second memory 133. The second processor 132 reads information from the second memory 133 and, in conjunction with its hardware, completes the steps of the aforementioned method.

[0277] This invention also provides a third network device, such as... Figure 14 As shown, it includes:

[0278] The third communication interface 141 is capable of exchanging information with other devices;

[0279] The third processor 142, connected to the third communication interface 141, is used to execute the methods provided by one or more technical solutions on the third network device side when running a computer program. The computer program is stored in the third memory 143.

[0280] It should be noted that the specific processing procedures of the third processor 142 and the third communication interface 141 are detailed in the method embodiment and will not be repeated here.

[0281] Of course, in practical applications, the various components in the third network device 140 are coupled together via a bus system 144. It can be understood that the bus system 144 is used to implement communication between these components. In addition to a data bus, the bus system 144 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 14The general labeled all buses as Bus System 144.

[0282] The third memory 143 in this embodiment is used to store various types of data to support the operation of the third network device 140. Examples of such data include any computer program used to operate on the third network device 140.

[0283] The methods disclosed in the embodiments of this application can be applied to, or implemented by, the third processor 142. The third processor 142 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the integrated logic circuitry of the hardware or by instructions in the software form of the third processor 142. The third processor 142 may be a general-purpose third processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The third processor 142 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose third processor may be a micro third processor or any conventional third processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as hardware decoding by the third processor, or as a combination of hardware and software modules in the decoding third processor. The software modules may be located in a storage medium, specifically a third memory 143. The third processor 142 reads information from the third memory 143 and, in conjunction with its hardware, completes the steps of the aforementioned method.

[0284] In an exemplary embodiment, the first network device 120, the second network device 130, and the third network device 140 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned method.

[0285] It is understood that the memories (first memory 123, second memory 133, and third memory 143) in the embodiments of this application can be volatile memories or non-volatile memories, or both. Non-volatile memories can be read-only memories (ROM), programmable read-only memories (PROM), erasable programmable read-only memories (EPROM), electrically erasable programmable read-only memories (EEPROM), magnetic random access memories (FRAM), flash memories, magnetic surface memories, optical discs, or compact disc read-only memories (CD-ROM); magnetic surface memories can be disk storage or magnetic tape storage. Volatile memories can be random access memories (RAM), which are used as external caches. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0286] In an exemplary embodiment, the present invention also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a third memory including a computer program. This computer program can be executed by a third processor 142 of a third network device 140 to complete the steps described in the aforementioned third network device-side method. The computer-readable storage medium may be a third memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface third memory, optical disc, or CD-ROM.

[0287] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0288] Furthermore, the technical solutions described in the embodiments of the present invention can be combined arbitrarily without conflict.

[0289] The above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention.

Claims

1. An information processing method, characterized in that, Applied to a first network device, the method includes: The system receives a Uniform Resource Identifier (URI) message sent by a higher-level network device. The URI message includes a first field, a second field, a third field, and a fourth field. The first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device. The second field represents a resource path used to acquire resource data. The third field represents a device identifier, which is the identifier of a lower-level device managed by the target network device connected to the second network device. The fourth field represents resource attributes, which are the attributes of the resource data under the resource path. Based on the first field, determine whether to perform local processing on the URI message; If it determines that it will not process the URI message locally, it will forward the URI message to the next-level network device. Among them, the upstream network device, the first network device, and the downstream network device are heterogeneous devices.

2. The method according to claim 1, characterized in that, The step of determining whether to perform local processing on the URI message based on the first field includes: Match its own network device identifier with at least two network device identifiers described hierarchically in the first field; If its own network device identifier does not match the last of the at least two network device identifiers described hierarchically in the first field, then it will not perform local processing on the URI message.

3. The method according to claim 1, characterized in that, The step of forwarding the URI message to the next-level network device includes: Remove the network device identifier belonging to itself from the first field of the URI message, and forward the URI message to the next level network device.

4. The method according to claim 1, characterized in that, The method further includes: Receive a response message sent by the next-level network device; the response message carries resource data; The resource data is determined by a third network device that performs local processing of the URI message based on the second, third, and fourth fields.

5. The method according to claim 1, characterized in that, The method further includes: Receive session messages sent by the next-level network device; The routing table is updated based on the session messages sent by the next-level network device; the routing table stores the status of the first network device and the next-level network device of the first network device. The routing table is sent to the next higher-level network device.

6. An information processing method, characterized in that, Applied to a second network device, the method includes: A URI message is generated; the URI message includes a first field, a second field, a third field, and a fourth field; the first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device; the second field represents a resource path, which is used to obtain resource data; the third field represents a device identifier, which is the identifier of the subordinate device managed by the target network device connected to the second network device; the fourth field represents resource attributes, which are the attributes of the resource data under the resource path. The URI message is sent to the next-level network device; the first field is used for the next-level network device to determine whether it will process the URI message locally. If it determines that it will not process the URI message locally, it will forward the URI message to the next-level network device. Among them, the second network device and the next-level network device are heterogeneous devices.

7. The method according to claim 6, characterized in that, The method further includes: Receive a response message sent by the next-level network device; the response message carries resource data; The resource data is determined by a third network device that performs local processing of the URI message based on the second, third, and fourth fields.

8. The method according to claim 6, characterized in that, The method further includes: Receive routing tables sent by the next-level network devices; the routing tables contain the status of network devices at each level; Based on the routing table, at least two network device identifiers described hierarchically in the first field are determined.

9. An information processing method, characterized in that, Applied to a third network device, the method includes: The system receives a URI message sent by a higher-level network device. The URI message includes a first field, a second field, a third field, and a fourth field. The first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device. The second field represents a resource path used to obtain resource data. The third field represents a device identifier, which is the identifier of a lower-level device managed by the target network device connected to the second network device. The fourth field represents resource attributes, which are the attributes of the resource data under the resource path. Based on the first field, determine whether to perform local processing on the URI message; If it is determined that it will process the URI message locally, then the resource data is obtained based on the second, third, and fourth fields; The response message is sent to the next higher-level network device; the response message carries the resource data. Among them, the third network device and the previous level network device are heterogeneous devices.

10. The method according to claim 9, characterized in that, The step of determining whether to perform local processing on the URI message based on the first field includes: Match its own network device identifier with at least two network device identifiers described hierarchically in the first field; If its own network device identifier matches the last of at least two network device identifiers described hierarchically in the first field, then it performs local processing on the URI message.

11. The method according to claim 9, characterized in that, The method further includes: Send session messages to the next higher-level network device; The session message is used to update the routing table of the upstream network device; the routing table stores the status of the third network device and the upstream network device of the third network device.

12. An information processing device, characterized in that, Applied to a first network device, the device includes: The first receiving unit is configured to receive a URI message sent by a higher-level network device. The URI message includes a first field, a second field, a third field, and a fourth field. The first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device. The second field represents a resource path, which is used to obtain resource data. The third field represents a device identifier, which is the identifier of a lower-level device managed by the target network device connected to the second network device. The fourth field represents resource attributes, which are the attributes of the resource data under the resource path. The first processing unit is configured to determine, based on the first field, whether it will perform local processing on the URI message; if it determines that it will not perform local processing on the URI message, it will forward the URI message to the next-level network device. Among them, the upstream network device, the first network device, and the downstream network device are heterogeneous devices.

13. An information processing device, characterized in that, Applied to a second network device, the device includes: The second processing unit is used to generate a URI message; the URI message includes a first field, a second field, a third field, and a fourth field; the first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device; the second field represents a resource path, which is used to obtain resource data; the third field represents a device identifier, which is the identifier of a subordinate device managed by the target network device connected to the second network device; the fourth field represents resource attributes, which are the attributes of the resource data under the resource path. The first sending unit is used to send the URI message to the next-level network device; the first field is used for the next-level network device to determine whether it will process the URI message locally. If it determines that it will not process the URI message locally, it will forward the URI message to the next-level network device. Among them, the second network device and the next-level network device are heterogeneous devices.

14. An information processing device, characterized in that, Applied to a third network device, the device includes: The second receiving unit is used to receive a URI message sent by the upper-level network device. The URI message includes a first field, a second field, a third field, and a fourth field. The first field represents host information, which consists of the identifiers of at least two network devices connected to the hierarchically described second network device. The second field represents a resource path, which is used to obtain resource data. The third field represents a device identifier, which is the identifier of a lower-level device managed by the target network device connected to the second network device. The fourth field represents resource attributes, which are the attributes of the resource data under the resource path. The third processing unit is used to determine whether it will perform local processing on the URI message based on the first field; if it determines that it will perform local processing on the URI message, it will obtain resource data based on the second, third and fourth fields. The second sending unit is used to send a response message to the upper-level network device; the response message carries the resource data. Among them, the third network device and the previous level network device are heterogeneous devices.

15. A first network device, characterized in that, It includes a first processor and a first memory for storing computer programs that can run on the first processor. Wherein, when the first processor is used to run the computer program, it performs the steps of the method according to any one of claims 1 to 5.

16. A second network device, characterized in that, It includes a second processor and a second memory for storing computer programs that can run on the second processor. Wherein, when the second processor is used to run the computer program, it performs the steps of the method according to any one of claims 6 to 8.

17. A third network device, characterized in that, This includes a third processor and a third memory for storing computer programs that can run on the third processor. When the third processor runs the computer program, it performs the steps of the method according to any one of claims 9 to 11.

18. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5, or implements the steps of the method according to any one of claims 6 to 8, or implements the steps of the method according to any one of claims 9 to 11.

Images