WO2024092941A1 - Procédé et appareil de traitement d'informations de composant, support de stockage et appareil électronique - Google Patents

Procédé et appareil de traitement d'informations de composant, support de stockage et appareil électronique Download PDF

Info

Publication number
WO2024092941A1
WO2024092941A1 PCT/CN2022/135690 CN2022135690W WO2024092941A1 WO 2024092941 A1 WO2024092941 A1 WO 2024092941A1 CN 2022135690 W CN2022135690 W CN 2022135690W WO 2024092941 A1 WO2024092941 A1 WO 2024092941A1
Authority
WO
WIPO (PCT)
Prior art keywords
subscription
subscription information
message
information
component
Prior art date
Application number
PCT/CN2022/135690
Other languages
English (en)
Chinese (zh)
Inventor
魏志远
Original Assignee
海尔优家智能科技（北京）有限公司
青岛海尔科技有限公司
海尔智家股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 海尔优家智能科技（北京）有限公司, 青岛海尔科技有限公司, 海尔智家股份有限公司 filed Critical 海尔优家智能科技（北京）有限公司
Publication of WO2024092941A1 publication Critical patent/WO2024092941A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services

Definitions

  • the present disclosure relates to the field of smart home/intelligent family technology, and in particular to a component information processing method and device, a storage medium, and an electronic device.
  • messages can be delivered between different components through message delivery components.
  • the message delivery component delivers the message to another component that pays attention to the message, and the sender of the message does not need to pay attention to the interface code of the message receiver.
  • the message delivery component needs to know the messages that different components are concerned about from different components in advance. If the component that pays attention to a certain message cannot be known in time, it is easy to fail to deliver the message to the component that pays attention to the message after receiving the message, resulting in poor accuracy of message delivery. It can be seen from this that the processing method of component information in the related art has the problem of poor accuracy of message delivery due to the inability to know the component to which the message needs to be delivered in time.
  • Embodiments of the present disclosure provide a method and device for processing component information, a storage medium, and an electronic device.
  • a method for processing component information including: obtaining first request information passed in by a first component of a target device, wherein the first request information is used to request a subscription to a message identified by a first message identifier in a message published to a message passing component of the target device, the message passing component being used to pass messages between different components of the target device according to the message identifier; in response to the first passed in request information, saving first subscription information corresponding to the first component, wherein the first subscription information is used to record a subscription relationship between the message identified by the first message identifier and the first component.
  • a component information processing device including: a first acquisition unit, configured to acquire first request information passed in by a first component of a target device, wherein the first request information is used to request subscription to a message identified by a first message identifier in a message published to a message passing component of the target device, wherein the message passing component is used to pass messages between different components of the target device according to the message identifier; and a saving unit, configured to save first subscription information corresponding to the first component in response to the first request information passed in, wherein the first subscription information is used to record the subscription relationship between the message identified by the first message identifier and the first component.
  • a computer-readable storage medium in which a computer program is stored, wherein the computer program is configured to execute the above-mentioned component information processing method when running.
  • an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the component information processing method through the computer program.
  • a method of completing message subscription by actively transmitting subscription request information to a messaging component through a component to obtain first request information transmitted by a first component of a target device, wherein the first request information is used to request subscription to a message identified by a first message identifier in a message published to the messaging component of the target device, and the messaging component is used to transmit messages between different components of the target device according to the message identifier; in response to the transmitted first request information, first subscription information corresponding to the first component is saved, wherein the first subscription information is used to record the subscription relationship between the message identified by the first message identifier and the first component.
  • FIG1 is a schematic diagram of a hardware environment of a method for processing component information according to an embodiment of the present disclosure
  • FIG2 is a flow chart of an optional component information processing method according to an embodiment of the present disclosure.
  • FIG3 is a flow chart of another optional component information processing method according to an embodiment of the present disclosure.
  • FIG4 is a schematic diagram of an optional component information processing method according to an embodiment of the present disclosure.
  • FIG5 is a structural block diagram of an optional device for processing component information according to an embodiment of the present disclosure.
  • FIG. 6 is a structural block diagram of an optional electronic device according to an embodiment of the present disclosure.
  • a method for processing component information is provided.
  • the method for processing component information is widely used in whole-house intelligent digital control application scenarios such as smart home, smart home, smart home device ecology, and smart house ecology.
  • the above-mentioned method for processing component information can be applied to a hardware environment composed of a terminal device 102 and a server 104 as shown in Figure 1.
  • the server 104 is connected to the terminal device 102 through a network, and can be used to provide services (such as application services, etc.) for the terminal or a client installed on the terminal.
  • a database can be set on the server or independently of the server to provide data storage services for the server 104.
  • Cloud computing and/or edge computing services can be configured on the server or independently of the server to provide data computing services for the server 104.
  • the above network may include but is not limited to at least one of the following: wired network, wireless network.
  • the above wired network may include but is not limited to at least one of the following: wide area network, metropolitan area network, local area network, and the above wireless network may include but is not limited to at least one of the following: WIFI (Wireless Fidelity), Bluetooth.
  • WIFI Wireless Fidelity
  • the terminal device 102 may be but is not limited to a PC, a mobile phone, a tablet computer, a smart air conditioner, a smart range hood, a smart refrigerator, a smart oven, a smart stove, a smart washing machine, a smart water heater, a smart washing equipment, a smart dishwasher, a smart projection equipment, a smart TV, a smart clothes drying rack, a smart curtain, a smart audio and video, a smart socket, a smart speaker, a smart speaker, a smart fresh air equipment, a smart kitchen and bathroom equipment, a smart bathroom equipment, a smart sweeping robot, a smart window cleaning robot, a smart mopping robot, a smart air purification equipment, a smart steamer, a smart microwave oven, a smart kitchen treasure, a smart purifier, a smart water dispenser, a smart door lock and other equipment.
  • the component information processing method of the embodiment of the present disclosure may be executed by the server 104, or by the terminal device 102, or by both the server 104 and the terminal device 102.
  • the component information processing method of the embodiment of the present disclosure may be executed by the terminal device 102 or by a client installed thereon.
  • FIG. 2 is a flow chart of an optional method for processing component information according to an embodiment of the present disclosure. As shown in FIG. 2, the flow of the method may include the following steps:
  • Step S202 obtaining the first request information transmitted by the first component of the target device, wherein the first request information is used to request subscription to the message identified by the first message identifier in the message published to the message transmission component of the target device, and the message transmission component is used to transmit messages between different components of the target device according to the message identifier.
  • the component information processing method in this embodiment can be applied to the scenario of message transmission between different business components in the terminal device through the message transmission component in the target device (i.e., the terminal device 102).
  • the operating system running on the target device here can be an operating system of an embedded system, which can include non-real-time operating systems and real-time operating systems, for example, an ecological operating system for a smart home in the field of smart home.
  • the embedded system can include a hardware part and a software part.
  • the operating system of the embedded system can have the core functions of a general operating system and is responsible for the allocation of all software and hardware resources of the embedded system, scheduling work control, and coordinating concurrent activities.
  • the target device can be a smart home device or other types of terminal devices.
  • the channels used can be local sockets (local "sockets", that is, interfaces for local network communication), message queues, etc.
  • local sockets local "sockets", that is, interfaces for local network communication
  • message queues etc.
  • each has its own message queue and a lock mechanism that can ensure the atomicity of the read and write process; provide an interface for writing message queues (that is, writing message queue interface) to the outside world, so that the other party can complete the operation of other components writing message queues to their own components by calling this interface, and the writing message queue interface is protected by atomic operations through locking; each has a poll mechanism (equivalent to a timer, used to wake up the process) to read their own queues cyclically, and if there is a message written, read the message for processing.
  • Component 1 can send a message to component 2 by calling the writing message queue interface of component 2.
  • the message publishing end (component 1) needs to call the write message queue interface of the message receiving end (module 2) to send messages to the message receiving end. Therefore, it is necessary to pay attention to the interface code of the message receiving end.
  • the coupling degree between components is high, and it is impossible to achieve complete independence between components. Due to the coupling relationship between components, the trimming of components requires the simultaneous update of the component that calls the write message queue interface of the component, resulting in high complexity of component trimming.
  • a message transmission component can be set up to implement message distribution and transmission between the message publisher and the message receiver.
  • the message publisher and the message receiver do not need to pay attention to each other's interface information, but only pay attention to the corresponding interface of the message transmission component to implement message publishing and reception, thereby achieving independence in message transmission between the message publisher and the message receiver.
  • the message passing component can pass the message to another component that is interested in the message.
  • the message passing component needs to know the messages that different components are interested in from different components in advance. If the component that is interested in a message cannot be informed in time, it is easy to fail to pass the message to the component that is interested in the message after receiving the message, resulting in poor accuracy of message passing.
  • the distribution and delivery of messages can be performed based on subscription and publishing.
  • Components in the device e.g., business components
  • the messaging component After receiving the message subscription request, the messaging component saves the subscription relationship between the component and the message of interest based on the message identifier, so that after receiving the message published by the message publishing end, the message can be accurately published to the component that has subscribed to the message based on the saved subscription relationship.
  • the component can actively pass subscription request information to the messaging component to subscribe to the messages of interest according to the message identifier. After obtaining the incoming subscription request information, the messaging component can save the subscription relationship between the component and the message of interest based on the message identifier. Therefore, after obtaining the published message, the message can be accurately published to the component that has subscribed to the message based on the saved subscription relationship, thereby achieving the purpose of timely knowing the component to which the message needs to be delivered and improving the accuracy of message delivery.
  • the component that publishes a message is a message publisher, which can be a message publisher of a specific message type, and can be called a message publishing component, publisher, publisher, etc.
  • the component that subscribes to a message is a message subscriber, which can be a message receiver of a specific message type, or a subscriber of a specific message type, and can be called a message subscription component, subscriber, subscriber, etc.
  • the message subscriber can be an independent component or a component that relies on a certain RTE environment (Run-Time Environment).
  • the RTE environment refers to a specific, independent context environment when a piece of code is about to be executed, which is equivalent to an independent thread; the message agent is also called a messaging component, a publish-subscribe component, etc.
  • the first component of the target device can pass the first request information to the messaging component of the target device to request to subscribe to the message identified by the first message identifier in the message published to the messaging component of the target device, and the messaging component can obtain the above-mentioned first request information passed by the first component.
  • the first request information can be passed in by calling the message subscription interface (or subscription interface) of the messaging component to pass the information related to the subscription to the message identified by the first message identifier to the messaging component to request to subscribe to the message identified by the first message identifier.
  • the first request information can be obtained by obtaining the above-mentioned information related to the subscription to the message identified by the first message identifier passed by the first component through the message subscription interface.
  • the information related to subscribing to the message identified by the first message identifier may include multiple information, including but not limited to at least one of the following: the first message identifier, the component identifier of the first component, and may also include other information, such as the RTE operating environment, the message processing function, the parameters of the message processing function, etc.
  • the first message identifier may be a message event number, which may be expressed as msg-id (message identifier), or other identifiers that can identify different messages. Different messages may correspond to different message identifiers or to the same message identifier.
  • the message delivery component may be used to deliver messages between different components of the target device according to the message identifier.
  • msg_id is the message id that the subscriber cares about.
  • This message id is a message event number defined according to the specific business logic needs. This message event number can match a message body as needed (or not need a message body).
  • the definition of the message body is a structured message content; msg_id and the associated message body definition are placed in the subscription and publishing component.
  • the RTE operating environment can be specified through the RTE handle.
  • the RTE handle is used to specify an operating environment, that is, the context environment of program execution; it can be limited to specify whether the message processing function is to be executed in a specific operating environment after a message is sent.
  • the RTE operating environment can be specified as needed.
  • the operating environment can be the operating environment of the message publisher.
  • the message processing function will be called by the agent when the message agent publishes msg_id and the corresponding information data; the message related content will be passed to this function in the form of parameters, and the internal processing implementation of the function obtains the message and makes corresponding business logic processing.
  • the parameters of the message processing function are customized by the subscriber and can be used or not as needed. If this parameter is passed in, the message agent will take it in when calling the message processing function to meet the special needs of message subscribers.
  • Step S204 in response to the incoming first request information, save the first subscription information corresponding to the first component, wherein the first subscription information is used to record the subscription relationship between the message identified by the first message identifier and the first component.
  • the first subscription information corresponding to the first component can be saved according to the first message identifier in the first request information.
  • the first subscription information can be used to indicate the subscription relationship between the message identified by the first message identifier and the first component. It can include information extracted from the first request information, or information generated by the message subscription component for the first request information or the first component.
  • the first subscription information is the incoming information related to the subscription to the message identified by the first message identifier.
  • the form of the first subscription information is not limited.
  • saving the first subscription information can be achieved by applying for a storage space (for example, a node), and caching the first subscription information in the applied storage space.
  • the first subscription information can be stored in the messaging component, or in other memory resources outside the messaging component, but the address information of the corresponding memory resource can be stored in the messaging component to ensure that the messaging component can search for the stored subscription information at any time.
  • the first component can transmit subscription request information to the message subscription component multiple times, and each transmitted subscription request information can be used to request subscription to a message identified by a message identifier.
  • the first component can also transmit subscription request information only once, and the subscription request information can be used to request subscription to messages identified by each message identifier in multiple message identifiers.
  • it can be determined whether it is a repeated subscription by searching all the saved subscription information.
  • the step of determining whether a subscription is repeated may be: after (or before) saving the first subscription information, comparing the first subscription information with the pre-stored subscription information to determine whether the same subscription information exists; when it is determined that the same subscription information exists, it can be determined as a repeated subscription, and the messaging component can ignore the repeated subscription information, delete the repeated subscription information, and release the corresponding storage resources.
  • the first request information transmitted by the first component of the target device is obtained, wherein the first request information is used to request subscription to the message identified by the first message identifier in the message published to the message transmission component of the target device, and the message transmission component is used to transmit the message between different components of the target device according to the message identifier; in response to the transmitted first request information, the first subscription information corresponding to the first component is saved, wherein the first subscription information is used to record the subscription relationship between the message identified by the first message identifier and the first component, thereby solving the problem of poor accuracy of message transmission due to the inability to timely know the component to which the message needs to be transmitted in the component information processing method in the related art, thereby improving the accuracy of information transmission.
  • the method further includes:
  • the pre-stored subscription information that is, a group of subscription information
  • the pre-stored subscription information can be searched based on the first subscription information to determine whether there is subscription information in the group of subscription information that is identical to the first subscription information.
  • each subscription information in the group of subscription information is used to record the subscription relationship between a message and a subscription component of a message.
  • the above subscription relationship can be represented by a message identifier and a component identifier (which may also include other information).
  • a subscription information matching the first subscription information is found from a group of subscription information, it can be determined to be a duplicate subscription.
  • the messaging component can delete the cached first subscription information and release the corresponding memory resources.
  • a subscription information matching the first subscription information is not found from a group of subscription information, it can be determined that it is not a duplicate subscription.
  • the saved first subscription information can be retained.
  • an association between the first subscription information and a group of subscription information can be established. For example, a node that saves the first subscription information is associated with a node that saves a group of subscription information to facilitate the management of subscription information.
  • the currently stored subscription information is deleted, which can improve the utilization of storage resources, avoid repeated sending of messages, and improve the accuracy of message publishing.
  • searching a pre-stored set of subscription information using the first subscription information includes:
  • the subscription information can be saved based on the subscription table.
  • the subscription table can be a memory-based container, which can be used to record the correspondence between the message identifier of the subscribed message and the location indication of the storage location of the subscription information of the subscribed message.
  • the validity of the subscription table can be determined first. If it is determined that the subscription table is valid, it can be determined that the system initialization is normal, and subsequent operations such as saving and searching can continue to be performed. If it is determined that the subscription table is invalid, it can be determined that the system initialization is abnormal, and the message transmission component will no longer perform subsequent operations.
  • the correspondence between the message identifier of the subscribed message and the location indication of the storage location of the subscription information of the subscribed message can be saved in the form of key-value, wherein the key (keyword) is the message identifier of the subscribed message, and the value (retrieval value) is the location indication of the storage location of the subscription information of the subscribed message.
  • the above location indication can be used to indicate the storage location of the subscription information of the subscribed message, which can point to a pointer to the storage address of the subscription information of the subscribed message. If the number of subscription information of the subscribed message is multiple, the number of location indications can be multiple, that is, there is a one-to-one correspondence between the two.
  • one or more subscription information of a subscribed message can be stored in the form of a linked list, and each linked list node in the linked list can store a subscription information of the corresponding subscribed message.
  • the location indication of the storage location of the subscription information of the subscribed message can be the linked list head of the information linked list corresponding to the subscribed message. That is, in the subscription table, the message identifier of the subscribed message and the linked list head address of the corresponding linked list can be recorded in a key-value manner.
  • the subscribed component information can be hung at the end of the linked list in sequence.
  • the address of the linked list head and the record of the message identifier in the subscription table can be implemented by hash mapping.
  • the corresponding relationship in the subscription table can be a mapping relationship.
  • the subscription table can be indexed with msg_id as the key and the list header (uhos_list_t) as the value.
  • the list header is the head node of a bidirectional circular linked list, which is used to associate all subscriber information (ie, subscription information) with the same msg_id.
  • the subscription information of the message identified by the first message identifier can be searched at the storage location indicated by the first location indication.
  • the first location indication can be the address information of the storage location of the subscription information of the subscribed message corresponding to the first message identifier.
  • the first message identifier may be used to search the subscription table to obtain a linked list header corresponding to the first message identifier, and then the subscription information of the message identified by the first message identifier may be traversed in the corresponding linked list according to the linked list header.
  • the subscription table records the correspondence between the message identifier and the location indication of the storage location of the corresponding subscription information. It is only necessary to traverse the subscription information corresponding to the current message identifier to complete the determination of duplicate subscriptions, which can improve the efficiency of searching for subscription information.
  • the method further comprises:
  • the message identified by the first message identifier may not have been subscribed to any component, may have been subscribed to components other than the first component, or may have been subscribed to by the first component.
  • the location indication corresponding to the first message identifier is not found in the subscription table, it means that the message identified by the first message identifier is not subscribed by any component. Then, it can be determined that the subscription information matching the first subscription information is not found in a group of subscription information.
  • a group of subscription information can be subscription information corresponding to all message identifiers. If the subscription information corresponding to the first message identifier does not have subscription information matching the first subscription information, it can be directly determined that a group of subscription information does not have subscription information matching the first subscription information.
  • a location indication corresponding to the first message identifier is found in the subscription table, but subscription information matching the first subscription information is not found in the storage location indicated by the first location indication, it can be determined that the message identified by the first message identifier has been subscribed to by the first component or other components other than the first component. In the case that subscription information matching the first subscription information is not found in the storage location indicated by the first location indication, it can be determined that subscription information matching the first subscription information is not found in a group of subscription information.
  • subscription information matching the first subscription information is found at the storage location indicated by the first position indication, it means that the message identified by the first message identifier has been subscribed to by the first component (using the same subscription information), and it can be determined that subscription information matching the first subscription information is found from a set of subscription information.
  • the method further comprises:
  • the location indication corresponding to the first message identifier is not found in the subscription table, it can be explained that no component has subscribed to the message identified by the first message identifier, and a corresponding relationship between the first message identifier and the second location indication can be added in the subscription table.
  • the second location indication can be used to indicate the storage location of the first subscription information.
  • the above-mentioned adding method can be determined according to the recording method in the subscription table.
  • a combination of the first message identifier and the location indication of the storage location of the processing information of the first component information can be added to the subscription table.
  • the subscription table stores a mapping relationship between a message identifier and a linked list header. If a linked list header corresponding to the first message identifier is not found in the subscription table, the process of adding a corresponding relationship between the first message identifier and the second position indication may be: first apply for a section of memory to record the linked list header corresponding to the first message identifier; then map the first message identifier and the linked list header in the subscription table; finally, add a node storing the first subscription information at the end of the linked list.
  • subscription information of subscribed messages is recorded in the form of a linked list
  • subscription information matching the first subscription information is not found from the storage location indicated by the first position indication, it means that there is a linked list corresponding to the first message identifier, but there is no linked list node storing subscription information matching the first subscription information in the linked list.
  • a node storing the first subscription information can be directly added to the end of the linked list.
  • a node can be applied for to cache the subscription information. If the subscription table is valid, search in the subscription table to confirm whether the subscribed msg_id exists. If not, it means that the msg_id has not been subscribed. You can apply for a section of memory to record the header of the subscription to this msg_id (here, it is uniformly identified by the label uhos_list_t); perform a hash calculation on the msg_id and the uhos_list_t header, and map it to the subscription table; hang the applied node at the end of the uhos_list_t linked list.
  • the location indication corresponding to the current message identifier is not found, it is directly determined that it is not a repeated subscription, and the corresponding relationship between the current message identifier and the location indication of the storage location of the current subscription information is added to the subscription table, which can improve the efficiency of message subscription.
  • searching a pre-stored set of subscription information using the first subscription information includes:
  • the first message identifier, the component identifier of the first component and the preset subscription parameters search for a set of pre-stored subscription information
  • the first subscription information includes the first message identifier, the component identifier of the first component and the preset subscription parameters
  • the preset subscription parameters include at least one of the following: a message processing function of the message identified by the first message identifier, and an operating environment for executing the message processing function of the message identified by the first message identifier.
  • the message identifier and component identifier can be used as the basis for judgment.
  • duplicate subscription judgments are made in combination with preset subscription parameters, and the preset subscription parameters include at least one of the following: the message processing function of the message identified by the first message identifier, and the operating environment for executing the message processing function of the message identified by the first message identifier (such as the aforementioned RTE operating environment).
  • the message processing function and the operating environment are similar to those in the aforementioned embodiments and are not described in detail here.
  • the message processing function of the message can be used as a condition for repeated subscription determination.
  • it can be determined whether to assign the message processing function to the RTE operating environment of the message subscription component for execution according to the requirements.
  • the operating environment for executing the message processing function can be used as a condition for repeated subscription determination.
  • the first message identifier, the component identifier of the first component, and the above-mentioned preset subscription parameters can be used to search for a set of pre-stored subscription information.
  • the first subscription information may include the first message identifier, the component identifier of the first component, and the preset subscription parameters.
  • the node information comparison may include RTE operating environment information, msg_id, corresponding processing method (ie, message processing function), component information (which may include component identification), and only when all information is the same will it be determined as a duplicate subscription.
  • the method further comprises:
  • a message subscription component no longer needs to pay attention to a message that has been successfully subscribed, it can use the message identifier to cancel the subscription message.
  • the process of unsubscribing can be similar to the process of subscribing.
  • the subscription can be cancelled by passing the unsubscribe request information to the message delivery component, and the message delivery component deletes the corresponding subscription information saved.
  • the message delivery component can be provided with an unsubscribe interface, and the unsubscribe request information can be passed in by calling the unsubscribe interface.
  • the unsubscription process may be triggered when a component cancels the subscription of a msg_id according to its own needs, which means that the component no longer pays attention to the message of the msg_id and can no longer receive and process the message of the msg_id.
  • a second request message may be transmitted to the messaging component.
  • the second request message is used to request the cancellation of the message identified by the second message identifier subscribed by the second component.
  • the second request message may be transmitted through the unsubscribe interface of the messaging component.
  • the messaging component may obtain the transmitted second request message.
  • the second component may be the same component as the first component or a different component from the first component.
  • the second message identifier may be the same message identifier as the first message identifier or a different message identifier.
  • the second request message may include the same content information as the first request message, for example, the second message identifier, the component identifier of the second component, etc.
  • the messaging component can determine whether there is second subscription information corresponding to the second component in the saved set of subscription information, the second subscription information being used to indicate the subscription relationship between the message identified by the second message identifier and the second component. If so, the second subscription information can be deleted, otherwise, the unsubscription process can be terminated.
  • the second request information may include a second message identifier and a component identifier of the second component. Based on the second message identifier and the component identifier of the second component, it may be determined whether second subscription information corresponding to the second component exists in a set of subscription information. Alternatively, it may be determined whether second subscription information corresponding to the second component exists in a set of subscription information in combination with other information (for example, subscription parameters corresponding to the above-mentioned preset subscription parameters, such as the message processing function of the message identified by the second message identifier, and at least one of the operating environments for executing the message processing function of the message identified by the second message identifier).
  • subscription parameters corresponding to the above-mentioned preset subscription parameters such as the message processing function of the message identified by the second message identifier, and at least one of the operating environments for executing the message processing function of the message identified by the second message identifier.
  • the comparison with the parameters of unsubscribing mainly includes the following: RTE operating environment, msg_id, and message processing function. Only when all the parameters are the same can they be considered as the same subscription information and the information matching is successful. If all the subscription information and the subscription information to be unsubscribed do not match successfully, it means that the subscription information to be unsubscribed has been deleted or has not been subscribed. If there is a subscription information that matches the subscription information to be unsubscribed, delete the matched subscription information.
  • the second request information for unsubscribing is sent to trigger the message delivery component to delete the corresponding subscription information, thereby completing the unsubscribing process, which can increase the speed of unsubscribing and improve resource utilization.
  • the method further includes:
  • S72 use the subscription information to be canceled to search a pre-stored set of subscription information to obtain a subscription information search result, wherein each subscription information in the set of subscription information is used to record the subscription relationship between a message and a subscription component of a message, and the subscription information search result is used to indicate whether subscription information matching the subscription information to be canceled is found from the set of subscription information.
  • the subscription information to be canceled can be determined based on the information contained in the second request information.
  • the subscription information to be canceled can be used to indicate the subscription relationship between the message identified by the second message identifier and the second component.
  • the subscription information to be canceled can be similar to the aforementioned first subscription information, which has been explained and will not be repeated here.
  • the subscription information to be canceled can be saved by temporarily caching it in the memory, so as to facilitate the use of the subscription information to be canceled for subsequent search and deletion operations.
  • the pre-stored subscription information i.e., a set of subscription information
  • the pre-stored subscription information can be searched based on it to obtain the subscription information search result, and then it can be determined whether there is the same subscription information as the subscription information to be canceled in the set of subscription information based on the subscription information search result.
  • the set of subscription information is similar to that in the aforementioned embodiment, and will not be described in detail here.
  • the set of subscription information can be the currently saved and valid subscription information. Since the timing of obtaining the first subscription information and the second subscription information is different, the set of subscription information in this embodiment and the set of subscription information in the aforementioned embodiment are both pre-stored subscription information, but the two are not necessarily completely consistent.
  • the subscription information search result can be used to indicate whether the subscription information matching the subscription information to be canceled is found from a set of subscription information. If the subscription information search result indicates that the subscription information matching the subscription information to be canceled is found from a set of subscription information, that is, the second subscription information, the second subscription information can be deleted. If the subscription information search result indicates that the subscription information matching the subscription information to be canceled is not found from a set of subscription information, the subscription cancellation process can be terminated.
  • the subscription information to be canceled is used to search for a set of pre-stored subscription information to obtain a subscription information search result, including:
  • the subscription information can be saved based on the subscription table.
  • the meaning of the subscription table is similar to that in the previous embodiment and will not be repeated here.
  • the validity of the subscription table can be determined first. If the subscription table is determined to be valid, it can be determined that the system is initialized normally, and subsequent search, deletion and other operations can be continued. If the subscription table is determined to be invalid, it can be determined that the system is initialized abnormally, and the message transmission component will no longer perform subsequent operations.
  • the method of using the subscription information to be canceled to search for a pre-stored set of subscription information can be: use the second message identifier to search the subscription table, and determine whether the position indication corresponding to the second message identifier exists in the subscription table; if the second message identifier and the position indication corresponding to the second message identifier are not found in the subscription table, it can be said that the message identified by the second message identifier has not been subscribed by the component, and the search process can be directly ended; if the second message identifier and the third position indication corresponding to the second message identifier are found in the subscription table, it can be said that the message identified by the second message identifier has been subscribed by the component, and the subscribed component may be the second component or other components in the target device.
  • the subscription information of the message identified by the second message identifier can continue to be searched at the storage location indicated by the third location indication, and it is determined whether there is subscription information matching the subscription information to be canceled in the subscription information of the message identified by the second message identifier, thereby obtaining the above-mentioned subscription information search result.
  • the third position indication may be a header address of the linked list corresponding to the second message identifier. Based on the found header address, the linked list corresponding to the second message identifier may be traversed to determine whether the subscription information in each linked list node is the same as the subscription information to be canceled, and the subscription information search result may be obtained.
  • the information associated with the message to be unsubscribed can be cached.
  • the content of this information is the same as the information content during subscription, mainly including: RTE operating environment, msg_id, message processing function, and parameters of the message processing function (optional and not required information).
  • the subscription table is searched through the msg_id passed by the caller to check whether the msg_id has been subscribed. If it has been subscribed, the uhos_list_t linked list header information can be retrieved according to the msg_id, and the uhos_list_t linked list is traversed to compare with the parameters of the unsubscription.
  • the main comparison contents include: RTE operating environment, msg_id, and message processing function. Only when all parameters are the same can it be determined as the same subscription information and the information matching is successful.
  • the method further comprises:
  • the message identified by the second message identifier may not have been subscribed to any component, may have been subscribed to components other than the second component, or may have been subscribed to by the second component.
  • the location indication corresponding to the second message identifier is not found in the subscription table, it means that the message identified by the second message identifier is not subscribed by any component. Then, it can be determined that no subscription information matching the to-be-unsubscribed information is found in the set of subscription information.
  • the third position indication corresponding to the second message identifier is found in the subscription table, it means that the message identified by the second message identifier has been subscribed by other components except the second component. If the subscription information matching the subscription information to be cancelled is not found in the storage location indicated by the third position indication, it can be determined that the subscription information matching the subscription information to be cancelled is not found in the set of subscription information.
  • subscription information matching the subscription information to be canceled is found at the storage location indicated by the third position indication, it means that the message identified by the second message identifier has been subscribed to by the second component and has not been unsubscribed, and it can be determined that subscription information matching the subscription information to be canceled is found from a set of subscription information.
  • the efficiency of subscription information matching can be improved by searching the subscription table for a location indication corresponding to the current message identifier and searching for subscription information matching the current subscription information to be canceled at the storage location indicated by the location indication.
  • the method further comprises:
  • the second subscription information matching the subscription information to be cancelled is found at the storage location indicated by the third position indicator, the second subscription information can be deleted from the storage location and the memory resources can be released.
  • the corresponding relationship between the second message identifier and the third position indicator can be deleted from the subscription table to ensure that all message identifiers in the subscription table are message identifiers of subscribed messages (currently having a subscriber).
  • the matched node information can be deleted from the linked list and the memory can be released; check the depth of the uhos_list_t linked list associated with msg_id. If the depth is not 0 (indicating that there are remaining linked list nodes), if the depth is 0, it means that this msg_id has no component subscription, delete the linked list head uhos_list_t from the subscription table, and release the memory of uhos_list_t.
  • the mapping relationship between the message identifier of the subscribed message and the subscription information of the subscribed message is recorded in a linked list
  • the message delivery component is a subscription publishing component
  • the message identifier is msg_id
  • the position indication is the header address of the linked list.
  • This optional example provides a message subscription mechanism between message components within the OS system.
  • Components within the system can complete message subscription by calling the subscription interface of the subscription publishing component, and the subscription publishing component records the message identifier and component information to complete the message subscription. Because the subscription is completed by calling the subscription publishing component interface and the subscription publishing component adds the message identifier and its corresponding subscription information, the subscription publishing component can timely manage all component information that is concerned about a certain message, thereby ensuring the accuracy of message delivery.
  • the message subscription process in the component information processing method in this optional example may include the following steps:
  • Step 1 When the subscription interface is called, determine the validity of the subscription table (subscribe_map_init).
  • Step 2 If the subscription table (map) is valid, apply for a new node (new node) to cache subscription data (i.e., subscription information).
  • Step 3 Search the subscription table to determine whether the subscribed msg_id (ie, message ID) exists.
  • Step 4 If it does not exist, first apply for a section of memory to record the uhos_list_t header that subscribes to this msg_id (i.e., apply for a uhos_list_t storage area and format the data); perform hash calculation on the msg_id and the uhos_list_t header, map them to the subscription table, and hang the new node information (i.e., the subscription information stored in the new node) at the end of the uhos_list_t linked list, and the process ends; if the memory application fails, release the new node memory and return failure.
  • a section of memory to record the uhos_list_t header that subscribes to this msg_id (i.e., apply for a uhos_list_t storage area and format the data); perform hash calculation on the msg_id and the uhos_list_t header, map them to the subscription table, and hang the new node information (i.e., the subscription
  • Step 5 If it exists, obtain the uhos_list_t header address information (value, uhos_list_t area address) corresponding to the msg_id (key), check for duplicates, traverse the uhos_list_t table, compare with the new node information, and determine whether this message is subscribed repeatedly by the same component.
  • uhos_list_t header address information value, uhos_list_t area address
  • msg_id key
  • Step 6 If there is no duplicate subscription, insert the new node information into the end of the uhos_list_t linked list and the process ends.
  • Step 7 If there is a duplicate subscription, the memory of the new node information is released and the process ends.
  • This optional example also provides a message unsubscription mechanism between message components within the OS system.
  • Components within the system can complete the message unsubscription by calling the unsubscribe interface of the subscription and publishing component.
  • the subscription and publishing component deletes the message identifier and its corresponding component information to complete the message unsubscription. Because the subscription and publishing component adds/deletes the message identifier and its corresponding component information by calling the subscription and publishing component interface to complete the message unsubscription, the subscription and publishing component can timely manage all component information that is concerned about a certain message, thereby ensuring the accuracy of message delivery.
  • the process of canceling message subscription in the component information processing method in this optional example may include the following steps:
  • Step 1 When the unsubscribe interface is called, determine the validity of the subscription table.
  • Step 2 If the subscription table is valid, retrieve the subscription table by calling the msg_id passed in by the component of the interface to check whether the msg_id has been subscribed.
  • Step 3 If you have not been subscribed, end the unsubscription process directly.
  • Step 4 If it has been subscribed, get the uhos_list_t list header information according to msg_id.
  • Step 5 traverse the uhos_list_t linked list and compare it with the parameters of the unsubscription. If all the parameters are the same, it is determined to be the same subscription information and the information matches successfully.
  • Step 6 If after traversal, all subscription information and the subscription information to be unsubscribed are not matched successfully, the unsubscription process is terminated directly.
  • Step 7 If there is node information matching the subscription information to be canceled, delete the matching node information from the linked list to release memory.
  • Step 8 check whether the depth of the uhos_list_t linked list associated with msg_id is 0. If it is 0, delete the linked list head uhos_list_t from the subscription table and release the memory of uhos_list_t.
  • This optional example can effectively solve the problem of poor accuracy of message delivery due to the inability to timely know the component to which the message needs to be delivered. Since the message delivery component can timely grasp the information of all components that are concerned about a certain message, the accuracy of message delivery can be guaranteed.
  • the computer software product is stored in a storage medium (such as ROM (Read-Only Memory)/RAM (Random Access Memory), a disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods of the various embodiments of the present disclosure.
  • a storage medium such as ROM (Read-Only Memory)/RAM (Random Access Memory), a disk, or an optical disk
  • a terminal device which can be a mobile phone, a computer, a server, or a network device, etc.
  • FIG5 is a structural block diagram of an optional component information processing device according to an embodiment of the present disclosure. As shown in FIG5, the device may include:
  • a first acquisition unit 502 is configured to acquire first request information transmitted by a first component of a target device, wherein the first request information is used to request a subscription to a message identified by a first message identifier in a message published to a message delivery component of the target device, and the message delivery component is used to deliver messages between different components of the target device according to the message identifier;
  • the saving unit 504 is connected to the first obtaining unit 502, and is configured to save the first subscription information corresponding to the first component in response to the incoming first request information, wherein the first subscription information is used to record the subscription relationship between the message identified by the first message identifier and the first component.
  • first acquisition unit 502 in this embodiment can be used to execute the above step S202
  • storage unit 504 in this embodiment can be used to execute the above step S204.
  • the first request information transmitted by the first component of the target device is obtained, wherein the first request information is used to request subscription to the message identified by the first message identifier in the message of the message transmission component published to the target device, and the message transmission component is used to transmit the message between different components of the target device according to the message identifier; in response to the first request information transmitted, the first subscription information corresponding to the first component is saved, wherein the first subscription information is used to record the subscription relationship between the message identified by the first message identifier and the first component, thereby solving the problem of poor accuracy of message transmission due to the inability to timely know the component to which the message needs to be transmitted in the component information processing method in the related technology, thereby improving the accuracy of information transmission.
  • the apparatus further comprises:
  • a first search unit is configured to, after saving the first subscription information corresponding to the first component in response to the incoming first request information, use the first subscription information to search for a set of pre-stored subscription information, wherein each subscription information in the set of subscription information is used to record a subscription relationship between a message identified by a message identifier and a subscription component of the message identified by the message identifier;
  • the first deleting unit is configured to delete the saved first subscription information when subscription information matching the first subscription information is found from a group of subscription information.
  • the first search unit includes:
  • a first search module is configured to use the first message identifier to search a subscription table, wherein the subscription table is used to record a correspondence between a message identifier of a subscribed message and a location indication of a storage location of subscription information of the subscribed message;
  • the second search module is configured to search for subscription information of the message identified by the first message identifier at the storage location indicated by the first location indicator when the first location indicator corresponding to the first message identifier is found in the subscription table.
  • the apparatus further comprises:
  • a first determining unit configured to determine that no subscription information matching the first subscription information is found from a group of subscription information when no location indication corresponding to the first message identifier is found from the subscription table
  • a second determining unit configured to determine that no subscription information matching the first subscription information is found from a group of subscription information if no subscription information matching the first subscription information is found from the storage location indicated by the first location indication;
  • the third determining unit is configured to determine to find subscription information matching the first subscription information from a group of subscription information when subscription information matching the first subscription information is found at the storage location indicated by the first location indication.
  • the apparatus further comprises:
  • the adding unit is configured to add a correspondence between the first message identifier and the second location indication in the subscription table when the location indication corresponding to the first message identifier is not found in the subscription table, wherein the second location indication is used to indicate the storage location of the first subscription information.
  • the first search unit includes:
  • the third search module is configured to use the first message identifier, the component identifier of the first component and the preset subscription parameters to search for a set of pre-stored subscription information, wherein the first subscription information includes the first message identifier, the component identifier of the first component and the preset subscription parameters, and the preset subscription parameters include at least one of the following: a message processing function of the message identified by the first message identifier, and an operating environment for executing the message processing function of the message identified by the first message identifier.
  • the apparatus further comprises:
  • a second acquisition unit is configured to acquire second request information transmitted by a second component of the target device, wherein the second request information is used to request cancellation of a message identified by a second message identifier subscribed by the second component;
  • the second deletion unit is configured to delete the second subscription information in response to the incoming second request information if there is second subscription information corresponding to the second component, wherein the second subscription information is used to indicate the subscription relationship between the message identified by the second message identifier and the second component.
  • the apparatus further comprises:
  • a fourth determining unit configured to determine the subscription information to be canceled after obtaining the second request information transmitted by the second component of the target device, wherein the subscription information to be canceled is used to indicate a subscription relationship between the message identified by the second message identifier and the second component;
  • the second search unit is configured to use the subscription information to be canceled to search a set of pre-stored subscription information to obtain a subscription information search result, wherein each subscription information in the set of subscription information is used to record a subscription relationship between a message and a subscription component of a message, and the subscription information search result is used to indicate whether subscription information matching the subscription information to be canceled is found from the set of subscription information.
  • the second search unit includes:
  • a fourth search module is configured to use the second message identifier to search a subscription table, wherein the subscription table is used to record a correspondence between a message identifier used by the subscription table to record a subscribed message and a location indication of a storage location of subscription information of the subscribed message;
  • the fifth search module is configured to search for processing information of the component information identified by the second message identifier at the storage location indicated by the third position indication when the third position indication corresponding to the second message identifier is found in the subscription table, so as to obtain the subscription information search result.
  • the apparatus further comprises:
  • a fifth determining unit configured to determine that no subscription information matching the to-be-unsubscribed information is found from a group of subscription information when no location indication corresponding to the second message identifier is found from the subscription table;
  • a sixth determining unit configured to determine that no subscription information matching the subscription information to be canceled is found from a set of subscription information if no subscription information matching the subscription information to be canceled is found from the storage location indicated by the third location indication;
  • the seventh determining unit is configured to determine to find subscription information matching the subscription information to be canceled from a group of subscription information when second subscription information matching the subscription information to be canceled is found at the storage location indicated by the third location indication.
  • the apparatus further comprises:
  • the third deletion unit is configured to delete the correspondence between the second message identifier and the third position indication from the subscription table when the second subscription information matching the to-be-unsubscribed information is found at the storage location indicated by the third position indication and there is no subscription information at the storage location indicated by the third position information after the subscription information is deleted.
  • a storage medium is further provided.
  • the storage medium can be used to execute the program code of any of the component information processing methods in the embodiments of the present disclosure.
  • the above-mentioned storage medium may be located on at least one network device among a plurality of network devices in the network shown in the above-mentioned embodiment.
  • the storage medium is configured to store program codes for executing the following steps:
  • S1 obtaining first request information transmitted by a first component of a target device, wherein the first request information is used to request to subscribe to a message identified by a first message identifier in a message published to a message transmission component of the target device, and the message transmission component is used to transmit messages between different components of the target device according to the message identifier;
  • the storage medium may include but is not limited to: a U disk, a ROM, a RAM, a mobile hard disk, a magnetic disk or an optical disk, and other media that can store program codes.
  • an electronic device for implementing the above-mentioned component information processing method is also provided.
  • the electronic device may be a server, a terminal, or a combination thereof.
  • FIG6 is a structural block diagram of an optional electronic device according to an embodiment of the present disclosure.
  • the electronic device includes a processor 602, a communication interface 604, a memory 606, and a communication bus 608, wherein the processor 602, the communication interface 604, and the memory 606 communicate with each other through the communication bus 608.
  • Memory 606 used for storing computer programs
  • the processor 602 is used to implement the following steps when executing the computer program stored in the memory 606:
  • S1 obtaining first request information transmitted by a first component of a target device, wherein the first request information is used to request to subscribe to a message identified by a first message identifier in a message published to a message delivery component of the target device, and the message delivery component is used to deliver messages between different components of the target device according to the message identifier;
  • the communication bus may be a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc.
  • the communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in FIG6 , but it does not mean that there is only one bus or one type of bus.
  • the communication interface is used for communication between the above-mentioned electronic device and other devices.
  • the memory may include RAM, or may include non-volatile memory, such as at least one disk storage.
  • the memory may also be at least one storage device located away from the aforementioned processor.
  • the memory 606 may include but is not limited to the first acquisition unit 502 and the storage unit 504 in the resource information push device. In addition, it may also include but is not limited to other module units in the resource information push device, which will not be repeated in this example.
  • the above-mentioned processor can be a general-purpose processor, which can include but not be limited to: CPU (Central Processing Unit), NP (Network Processor), etc.; it can also be DSP (Digital Signal Processing), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • CPU Central Processing Unit
  • NP Network Processor
  • DSP Digital Signal Processing
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • other programmable logic devices discrete gates or transistor logic devices, discrete hardware components.
  • the structure shown in FIG. 6 is for illustration only, and the device for implementing the above-mentioned component information processing method may be a terminal device, and the terminal device may be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (Mobile Internet Devices, MID), a PAD, and other terminal devices.
  • FIG. 6 does not limit the structure of the above-mentioned electronic device.
  • the electronic device may also include more or fewer components (such as a network interface, a display device, etc.) than those shown in FIG. 6, or have a configuration different from that shown in FIG. 6.
  • a person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, which can include: a flash drive, ROM, RAM, a magnetic disk or an optical disk, etc.
  • the integrated units in the above embodiments are implemented in the form of software functional units and sold or used as independent products, they can be stored in the above computer-readable storage medium.
  • the technical solution of the present disclosure, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling one or more computer devices (which can be personal computers, servers, or network devices, etc.) to execute all or part of the steps of the methods of various embodiments of the present disclosure.
  • the disclosed client can be implemented in other ways.
  • the device embodiments described above are only schematic, for example, the division of units is only a logical function division, and there may be other division methods in actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution provided in this embodiment.
  • each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or at least two units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware or in the form of software functional units.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un procédé et un appareil de traitement d'informations de composant, un support de stockage et un appareil électronique, qui se rapportent au domaine technique des maisons intelligentes/maisons intelligentes. Le procédé consiste en : l'acquisition de premières informations de demande transmises à partir d'un premier composant d'un dispositif cible, les premières informations de demande étant utilisées pour demander un abonnement à un message, qui est identifié au moyen d'un premier identifiant de message, parmi des messages émis vers un composant de transfert de message du dispositif cible, et le composant de transfert de message étant utilisé pour transférer des messages entre différents composants du dispositif cible selon des identifiants de message (S202) ; et en réponse aux premières informations de demande transmises, le stockage de premières informations d'abonnement correspondant au premier composant, les premières informations d'abonnement étant utilisées pour enregistrer une relation d'abonnement entre le message, qui est identifié au moyen du premier identifiant de message, et le premier composant (S204).
PCT/CN2022/135690 2022-10-31 2022-11-30 Procédé et appareil de traitement d'informations de composant, support de stockage et appareil électronique WO2024092941A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211349532.7A CN115766315A (zh) 2022-10-31 2022-10-31 组件信息的处理方法和装置、存储介质及电子装置
CN202211349532.7 2022-10-31

Publications (1)

Publication Number Publication Date
WO2024092941A1 true WO2024092941A1 (fr) 2024-05-10

Family

ID=85356012

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/135690 WO2024092941A1 (fr) 2022-10-31 2022-11-30 Procédé et appareil de traitement d'informations de composant, support de stockage et appareil électronique

Country Status (2)

Country Link
CN (1) CN115766315A (fr)
WO (1) WO2024092941A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102859541A (zh) * 2010-04-19 2013-01-02 国际商业机器公司 在发布/订阅通讯中控制消息传递
CN106101178A (zh) * 2016-05-30 2016-11-09 海尔优家智能科技（北京）有限公司 一种订阅消息分发、接收方法、装置及相关系统
WO2017128713A1 (fr) * 2016-01-29 2017-08-03 中兴通讯股份有限公司 Procédé et dispositif permettant de publier un message d'abonnement
CN107111565A (zh) * 2014-11-21 2017-08-29 国际商业机器公司 使用消息结构来发布/订阅消息传递
CN112422684A (zh) * 2020-11-18 2021-02-26 青岛海尔科技有限公司 目标消息的处理方法及装置、存储介质、电子装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102859541A (zh) * 2010-04-19 2013-01-02 国际商业机器公司 在发布/订阅通讯中控制消息传递
CN107111565A (zh) * 2014-11-21 2017-08-29 国际商业机器公司 使用消息结构来发布/订阅消息传递
WO2017128713A1 (fr) * 2016-01-29 2017-08-03 中兴通讯股份有限公司 Procédé et dispositif permettant de publier un message d'abonnement
CN106101178A (zh) * 2016-05-30 2016-11-09 海尔优家智能科技（北京）有限公司 一种订阅消息分发、接收方法、装置及相关系统
CN112422684A (zh) * 2020-11-18 2021-02-26 青岛海尔科技有限公司 目标消息的处理方法及装置、存储介质、电子装置

Also Published As

Publication number Publication date
CN115766315A (zh) 2023-03-07

Similar Documents

Publication Publication Date Title
WO2024092939A1 (fr) Procédé et appareil de transmission de message inter-composants, support d'enregistrement et appareil électronique
JP2019533235A5 (fr)
CN113326155B (zh) 一种信息处理方法、装置、系统和存储介质
CN106021327B (zh) 一种支持多用户同时读写的网盘系统及其读文件方法、写文件方法
WO2019174523A1 (fr) Système et appareil de transmission de demande d'interface de programmation d'application (api)
JP2011520169A (ja) ディレクトリへのアクセスのための方法及びデバイス
CN112202674B (zh) 一种组播报文的转发处理方法、装置、设备及存储介质
CN107797859B (zh) 一种定时任务的调度方法及一种调度服务器
CN110781149A (zh) 管理直播间信息的方法、装置、设备及存储介质
CN114090623A (zh) 一种缓存资源的创建方法、装置、电子设备及存储介质
WO2018129956A1 (fr) Procédé et dispositif d'exploitation de ressources d'instance
WO2024160193A1 (fr) Procédé et appareil de planification de demande de réseau cdn, dispositif électronique et support de stockage
CN111282263A (zh) 事件消息的处理方法、装置、电子设备及可读存储介质
CN111355765A (zh) 一种网络请求的处理、发送方法及装置
CN108132836B (zh) 一种任务分发方法、装置及电子设备
WO2024092940A1 (fr) Procédé et dispositif de transmission de message entre composants, support de stockage et dispositif électronique
WO2024092941A1 (fr) Procédé et appareil de traitement d'informations de composant, support de stockage et appareil électronique
CN110309028B (zh) 监控信息获取方法、服务监控方法、装置及系统
WO2023134247A1 (fr) Procédé de gestion de conteneur, et système de gestion de conteneur
KR101027590B1 (ko) 멀티캐스트 데이터의 수신 중 데이터 다운로드의 최적화
WO2024092938A1 (fr) Procédé et appareil de transmission de message inter-composants, support de stockage et appareil électronique
TW201006191A (en) UPnP/DLNA device support apparatus, system, and method
WO2017097027A1 (fr) Procédé, appareil et système de traitement de données basé sur un protocole d'adaptation de contenu internet
CN114979985A (zh) 一种间接通信消息传递方法、系统及网关设备
WO2017107762A1 (fr) Procédé et dispositif de traçage d'application

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22964236

Country of ref document: EP

Kind code of ref document: A1