Communication method, communication device, communication system, storage medium, and program product

Abstract

The present disclosure relates to a communication method, a communication device, a communication system, a storage medium, and a program product. The communication method may be executed by a first device or a second device. The method executed by a first device comprises: receiving a subscription request sent by a second device, the subscription request being used for indicating an attribute and / or an event to which the second device subscribes; and sending a subscription report to the second device, the subscription report being used for indicating information related to the attribute and / or the event, wherein both the first device and the second device are power line communication (PLC) devices.

Description

Communication methods, communication equipment, communication systems, storage media and software products

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202510187635.5, filed in China on February 19, 2025, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to the field of communication technology, and in particular to communication methods, communication devices, communication systems, storage media, and program products. Background Technology

[0004] Power line communication (PLC) is a communication technology that transmits data and voice signals over power lines. Data transmission can occur between different appliances connected to the same electricity meter, or it can be transmitted remotely over the power grid. PLCs can be used to connect various smart devices in the home, such as smart switches, smart sockets, smart light bulbs, and temperature controllers. Summary of the Invention

[0005] This disclosure provides a communication method, communication device, communication system, storage medium, program product, and computer program.

[0006] In a first aspect, embodiments of this disclosure provide a communication method executed by a first device, the method comprising:

[0007] Receive a subscription request sent by a second device, the subscription request being used to indicate the attributes and / or events that the second device is subscribing to;

[0008] Send a subscription report to the second device, the subscription report being used to indicate information related to the attribute and / or the event;

[0009] Both the first device and the second device are power line carrier communication PLC devices.

[0010] Secondly, embodiments of this disclosure provide a communication method executed by a second device, the method comprising:

[0011] Send a subscription request to the first device, the subscription request being used to indicate the attributes and / or events that the second device is subscribing to;

[0012] Receive a subscription report sent by the first device, the subscription report being used to indicate information related to the attribute and / or the event;

[0013] Both the first device and the second device are power line carrier communication PLC devices.

[0014] Thirdly, embodiments of this disclosure provide a first device, comprising:

[0015] A transceiver module is used to receive a subscription request sent by a second device, the subscription request being used to indicate the attributes and / or events subscribed to by the second device;

[0016] The transceiver module is further configured to send a subscription report to the second device, the subscription report being used to indicate information related to the attribute and / or the event;

[0017] Both the first device and the second device are power line carrier communication PLC devices.

[0018] Fourthly, embodiments of this disclosure provide a second device, comprising:

[0019] A transceiver module is used to send a subscription request to a first device, the subscription request being used to indicate the attributes and / or events subscribed to by the second device;

[0020] The transceiver module is configured to receive a subscription report sent by the first device, the subscription report being used to indicate information related to the attribute and / or the event;

[0021] Both the first device and the second device are power line carrier communication PLC devices.

[0022] Fifthly, embodiments of this disclosure provide a communication device, comprising:

[0023] One or more processors;

[0024] The communication device is used to perform the method described in the first aspect or the second aspect.

[0025] In a sixth aspect, embodiments of this disclosure provide a communication system including a first device and a second device, wherein the first device is configured to implement the method described in the first aspect, and the second device is configured to implement the method described in the second aspect.

[0026] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the communication method as described in the first or second aspect.

[0027] Eighthly, embodiments of this disclosure provide a computer program product including a computer program and / or instructions, which, when executed by a communication device, implement the communication method as described in the first or second aspect.

[0028] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the communication method as described in the embodiments of the first or second aspect.

[0029] In this embodiment of the disclosure, a PLC device can subscribe to corresponding attributes and / or events by sending subscription requests to other PLC devices. Through the subscription request and reporting mechanism, an interactive framework for dynamic subscription between PLC devices is defined, which effectively improves the flexibility and practicality of PLC communication. Attached Figure Description

[0030] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0031] Figure 1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0032] Figure 2 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0033] Figure 3A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0034] Figure 3B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0035] Figure 3C is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0036] Figure 3D is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0037] Figure 3E is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0038] Figure 4 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0039] Figure 5A is a schematic diagram of the structure of the first device proposed in an embodiment of this disclosure.

[0040] Figure 5B is a schematic diagram of the structure of the second device proposed in an embodiment of this disclosure.

[0041] Figure 6A is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure.

[0042] Figure 6B is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0043] This disclosure provides embodiments of communication methods, communication devices, communication systems, storage media, program products, and computer programs.

[0044] In a first aspect, embodiments of this disclosure provide a communication method executed by a first device, the method comprising:

[0045] Receive a subscription request sent by a second device, the subscription request being used to indicate the attributes and / or events that the second device is subscribing to;

[0046] Send a subscription report to the second device, the subscription report being used to indicate information related to the attribute and / or the event;

[0047] Both the first device and the second device are power line carrier communication PLC devices.

[0048] In the above embodiments, PLC devices can subscribe to corresponding attributes and / or events by sending subscription requests to other PLC devices. Through the subscription request and reporting mechanism, an interactive framework for dynamic subscription between PLC devices is defined, which effectively improves the flexibility and practicality of PLC communication.

[0049] In conjunction with some embodiments of the first aspect, in some embodiments, the subscription request includes at least one of the following:

[0050] Subscription identifier;

[0051] Reporting interval, used to indicate the reporting time interval of the subscribed report;

[0052] The first quantity indicates the number of attributes subscribed to by the second device;

[0053] The second quantity indicates the number of events subscribed to by the second device;

[0054] The service identifier of the service corresponding to each of the aforementioned attributes;

[0055] The attribute identifier for each of the aforementioned attributes under the corresponding service;

[0056] The service identifier for the service corresponding to each event;

[0057] The event identifier for each event under the corresponding service.

[0058] In the above embodiments, by defining the fields included in the subscription request, the subscription request is ensured to be compatible with the PLC object model specification, the versatility of the technical solution is enhanced, and multiple attributes / events can be subscribed to on demand to adapt to complex scenarios.

[0059] In conjunction with some embodiments of the first aspect, in some embodiments, sending a subscription report to the second device includes:

[0060] If the reporting interval is determined to be 0 or default, and in response to a change in the attribute value of the attribute and / or a change in the event state, the subscription report is sent to the second device; and / or,

[0061] If the reporting interval is determined to be non-zero, the subscription report is sent to the second device according to the reporting interval.

[0062] In the above embodiments, when the reporting interval is 0 or default, reporting is only performed when the attribute / event changes. When the reporting interval is not 0, periodic reporting is supported. This not only effectively ensures that status changes are synchronized in real time, but also reduces the load on the PLC network.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the subscription report includes at least one of the following:

[0064] The subscription identifier;

[0065] The second device subscribes to the service identifier, attribute identifier, and attribute value corresponding to each attribute;

[0066] The second device subscribes to each event, including the service identifier, event identifier, and event status.

[0067] The service identifier, attribute identifier, and attribute value corresponding to the changed attribute;

[0068] The service identifier, event identifier, and event status corresponding to the event that has changed.

[0069] In the above embodiments, the subscription report, by including service identifier, attribute identifier and specific value, can effectively ensure that the subscriber accurately parses the data to avoid ambiguity, and supports reporting only the changed attributes / events, reducing redundant data transmission and improving PLC network efficiency.

[0070] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0071] If the subscription identifier in the subscription request is determined to be 0, delete all subscription configurations of the second device on the first device.

[0072] In the above embodiments, the subscription configuration can be deleted when the subscription identifier is 0, which avoids invalid subscriptions occupying device resources for a long time and improves the storage and computing efficiency of PLC devices.

[0073] In conjunction with some embodiments of the first aspect, in some embodiments, sending a subscription report to the second device includes:

[0074] In response to receiving the subscription request, a first subscription report is sent to the second device, the first subscription report indicating the attribute value of each attribute subscribed by the second device, and / or the event status of each event subscribed by the second device.

[0075] In the above embodiments, the first device can immediately send the status of all currently subscribed attributes / events after receiving the subscription request, which can effectively avoid inconsistencies that may occur due to status delays during subscription. In scenarios such as network disconnection and reconnection, data consistency can be quickly restored through the first subscription report.

[0076] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0077] Send a subscription response to the second device, the subscription response indicating whether the subscription was successful.

[0078] In the above embodiments, the subscription operation result is explicitly stated through response messages (such as ACK / NACK), thereby improving system reliability.

[0079] Secondly, embodiments of this disclosure provide a communication method executed by a second device, the method comprising:

[0080] Send a subscription request to the first device, the subscription request being used to indicate the attributes and / or events that the second device is subscribing to;

[0081] Receive a subscription report sent by the first device, the subscription report being used to indicate information related to the attribute and / or the event;

[0082] Both the first device and the second device are power line carrier communication PLC devices.

[0083] In conjunction with some embodiments of the second aspect, in some embodiments, the subscription request includes at least one of the following:

[0084] Subscription identifier;

[0085] Reporting interval, used to indicate the reporting time interval of the subscribed report;

[0086] The first quantity indicates the number of attributes subscribed to by the second device;

[0087] The second quantity indicates the number of events subscribed to by the second device;

[0088] The service identifier of the service corresponding to each of the aforementioned attributes;

[0089] The attribute identifier for each of the aforementioned attributes under the corresponding service;

[0090] The service identifier for the service corresponding to each event;

[0091] The event identifier for each event under the corresponding service.

[0092] In conjunction with some embodiments of the second aspect, in some embodiments, the subscription report is sent by the first device in response to a change in the attribute value of the attribute and / or a change in the event state of the event; or,

[0093] The subscription report is sent to the second device according to the reporting interval.

[0094] In conjunction with some embodiments of the second aspect, in some embodiments, the subscription report includes at least one of the following:

[0095] The subscription identifier;

[0096] The second device subscribes to the service identifier, attribute identifier, and attribute value corresponding to each attribute;

[0097] The second device subscribes to each event, including the service identifier, event identifier, and event status.

[0098] The service identifier, attribute identifier, and attribute value corresponding to the changed attribute;

[0099] The service identifier, event identifier, and event status corresponding to the event that has changed.

[0100] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0101] The first subscription report is received from the first device in response to receiving the subscription request. The first subscription report is used to indicate the attribute value of each attribute subscribed by the second device, and / or the event status of each event subscribed by the second device.

[0102] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0103] Receive a subscription response sent by the first device, the subscription response being used to indicate whether the subscription was successful.

[0104] Thirdly, embodiments of this disclosure provide a first device, comprising:

[0105] A transceiver module is used to receive a subscription request sent by a second device, the subscription request being used to indicate the attributes and / or events subscribed to by the second device;

[0106] The transceiver module is further configured to send a subscription report to the second device, the subscription report being used to indicate information related to the attribute and / or the event;

[0107] Both the first device and the second device are power line carrier communication PLC devices.

[0108] Fourthly, embodiments of this disclosure provide a second device, comprising:

[0109] A transceiver module is used to send a subscription request to a first device, the subscription request being used to indicate the attributes and / or events subscribed to by the second device;

[0110] The transceiver module is configured to receive a subscription report sent by the first device, the subscription report being used to indicate information related to the attribute and / or the event;

[0111] Both the first device and the second device are power line carrier communication PLC devices.

[0112] Fifthly, embodiments of this disclosure provide a communication device, comprising:

[0113] One or more processors;

[0114] The communication device is used to perform the method described in the first aspect or the second aspect.

[0115] In a sixth aspect, embodiments of this disclosure provide a communication system including a first device and a second device, wherein the first device is configured to implement the method described in the first aspect, and the second device is configured to implement the method described in the second aspect.

[0116] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the communication method described in the first or second aspect.

[0117] Eighthly, embodiments of this disclosure provide a computer program product including a computer program and / or instructions, which, when executed by a communication device, implement the communication method as described in the first or second aspect.

[0118] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the communication method as described in the embodiments of the first or second aspect.

[0119] It is understood that the aforementioned communication equipment, communication system, storage medium, program product, computer program, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0120] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0121] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0122] In this disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular or a plural expression.

[0123] In the embodiments of this disclosure, "multiple" refers to two or more.

[0124] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0125] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0126] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0127] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0128] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0129] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0130] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0131] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0132] In some embodiments, "network" can be interpreted as devices included in the network (e.g., PLC gateway, PLC sub-device, access network device, core network device, etc.).

[0133] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0134] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0135] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0136] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0137] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0138] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0139] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0140] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 includes a first device 101 and a second device 102.

[0141] In some embodiments, the first device 101 and the second device 102 may be PLC sub-devices in a PLC network or PLC gateways.

[0142] In some embodiments, the PLC gateway may include a Central Coordinator (CCO). In some embodiments, the PLC gateway includes a master control device and a central coordinator. In some embodiments, the master control device can communicate with the central coordinator via a PLC module serial port.

[0143] In some embodiments, a PLC gateway (or central coordinator) can be used for terminal nodes to access a PLC network.

[0144] In some embodiments, the first device 101 and the second device 102 may be provided as PLC sub-devices, or as part of a PLC sub-device. In some embodiments, the PLC sub-device includes a master control device (such as an MCU) and a terminal node. In some embodiments, the master control device may communicate with the terminal node via a PLC module serial port, or via inter-process communication through shared memory.

[0145] In some embodiments, a user device, such as a mobile phone, can communicate with a central coordinator or a PLC gateway. In some embodiments, a user can use the user device to schedule the central coordinator, for example, instructing the central coordinator to add terminal nodes to the PLC network.

[0146] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0147] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0148] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0149] Figure 2 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2, the embodiments of the present disclosure relate to a communication method, which includes:

[0150] Step S2101: The second device sends a subscription request to the first device.

[0151] In some embodiments, both the first device and the second device are PLC devices. In some embodiments, the second device is a PLC gateway and the first device is a PLC sub-device; or, the first device is a PLC gateway and the second device is a PLC sub-device; or, both the first device and the second device are PLC sub-devices.

[0152] In some embodiments, a subscription request includes at least one of the following: a subscription identifier; a reporting interval, used to indicate the reporting time interval of a subscription report; a first quantity, used to indicate the number of attributes subscribed to by the second device; a second quantity, used to indicate the number of events subscribed to by the second device; a service identifier for the service corresponding to each attribute; an attribute identifier for each attribute under the corresponding service; a service identifier for the service corresponding to each event; and an event identifier for each event under the corresponding service.

[0153] In some embodiments, the subscription request is used to indicate the attributes and / or events subscribed to by the second device. In some embodiments, the attributes and / or events subscribed to by the second device are attributes and / or events under the services of the first device.

[0154] In some embodiments, a subscription request is used to subscribe to one or more attributes and / or one or more events under at least one service in the first device.

[0155] In some embodiments, a subscription request is used to indicate a set of subscription configurations on a first device by a second device. In some embodiments, the first device determines and stores the subscription configuration corresponding to the subscription request based on the subscription request. For example, the first device may generate and maintain a corresponding subscription configuration for each subscription request it receives. A subscription configuration may correspond to a subscription request or a subscription identifier. The first device may send corresponding subscription reports to other devices based on the subscription configuration it maintains.

[0156] In some embodiments, either the first quantity or the second quantity may have a value of 0, or the subscription request may include only one of the first quantity or the second quantity. For example, if the second device subscribes to only one or more attributes under a service of the first device, the second quantity may be equal to 0 or the second quantity may be omitted.

[0157] In some embodiments, the first quantity and / or the second quantity may be omitted, and the first device may determine the first quantity based on the quantity identified by the attribute in the subscription request, and / or determine the second quantity based on the event identifier in the subscription request.

[0158] In some embodiments, the functionality of a PLC sub-device can be provided as various services. In some embodiments, a service can represent a set of functions, and the attributes under the service represent specific function values; events under the service can represent specific function operations, such as button clicks, brightness changes, and other events.

[0159] For example, the first device is a smart light. The smart light's on / off function can be provided as a switch service (e.g., SIID=0). Under the switch service, it can have switch attributes (e.g., CIID=0). When the data value of this attribute is 0, the smart light is in an off state; when the data value is 1, the smart light is in an on state. Additionally, the smart light's brightness adjustment function can be provided as a brightness adjustment service (e.g., SIID=1). This service can have brightness change events (e.g., EIID=1), and the event status under these events can indicate the current brightness of the smart light. The second device can then subscribe to the first device by sending a subscription request. This subscription request could, for example, request to subscribe to the attributes "SIID=0, CIID=0" and the events "SIID=1, EIID=1" to subscribe to the switch attributes under the switch service and the brightness change events under the brightness adjustment service, thereby obtaining the smart light's on / off state and brightness value.

[0160] In some embodiments, the first device determines that the subscription identifier is not 0 and performs step S2102.

[0161] In some embodiments, the first device determines that the subscription identifier is 0 and deletes all subscription configurations of the second device on the first device. In some embodiments, the first device determines that the subscription identifier is 0 and deletes all subscription configurations on the first device. In this case, steps S2102 to S2104 can be omitted.

[0162] In step S2102, the first device sends a first subscription report to the second device.

[0163] In some embodiments, the first device responds to a subscription request and performs step S2102. In some embodiments, the first device agrees to the second device's subscription request and performs step S2102.

[0164] In some embodiments, the first subscription report is used to indicate the attribute value of each attribute subscribed to by the second device, and / or the event status of each event subscribed to by the second device.

[0165] In some embodiments, the first subscription report is used to indicate the initial attribute value of each attribute subscribed to by the second device, and / or the initial event state of each event subscribed to by the second device.

[0166] In some embodiments, the first subscription report is used to synchronize the first device and the second device for each attribute and / or each event subscribed to by the second device.

[0167] For example, if the second device subscribes to the on / off attribute under the on / off service and the brightness change event under the brightness adjustment service of the first device (such as a smart light) through a subscription request, the first device can respond to the subscription request by sending a first subscription report to the second device to indicate the current on / off state and brightness value of the smart light.

[0168] In step S2103, the first device sends a subscription response to the second device.

[0169] In some embodiments, the subscription response is used to indicate whether the subscription was successful.

[0170] In some embodiments, the first device determines that the subscription is successful and sends a subscription response to the second device.

[0171] In some embodiments, steps S2102 and S2103 may be interchanged or performed simultaneously. In some embodiments, the first device determines that the subscription is successful, for example by accurately identifying each attribute and each event requested in the subscription request, and sends a subscription response to the second device while simultaneously sending a first subscription report. In some embodiments, the first subscription report and the subscription response may be carried by the same signaling or may be sent separately, for example, the first subscription report may be sent first and then the subscription response may be sent; this disclosure does not limit this approach.

[0172] In step S2104, the first device sends a subscription report to the second device.

[0173] In some embodiments, the first device sends a subscription report to the second device based on a subscription request. In some embodiments, the first device sends the subscription report to the second device according to the reporting interval indicated in the subscription request.

[0174] In some embodiments, a subscription report is sent by the first device in response to a change in the attribute value of an attribute subscribed to by the second device and / or a change in the event state of an event subscribed to by the second device.

[0175] In some embodiments, the subscription report is sent by the first device at reporting intervals.

[0176] In some embodiments, the first device determines that the reporting interval is equal to 0 or the default, and sends a subscription report to the second device in response to a change in the attribute value of an attribute and / or a change in the event state of an event. That is, when the reporting interval indicated in the subscription request is 0 or the reporting interval in the subscription request is the default, the subscription report may be sent when the attribute value of the attribute subscribed by the second device changes, or when the event state of the event subscribed by the second device changes.

[0177] In some embodiments, the first device determines that the reporting interval is not equal to 0 and sends a subscription report to the second device according to the reporting interval. That is, when the reporting interval indicated by the subscription request is not 0, the first device may periodically send a subscription report to the second device.

[0178] In some embodiments, when the reporting interval indicated by the subscription request is not 0, the first device may still send a subscription report to the second device when the attribute value of the attribute subscribed by the second device changes, or when the event status of the event subscribed by the second device changes.

[0179] In some embodiments, a subscription report periodically sent by the first device according to a reporting interval may be referred to as a periodic report, and a subscription report sent by the first device in response to a change in the attribute value of an attribute and / or a change in the event state of an event may be referred to as a change-triggered report.

[0180] In some embodiments, the subscription report is used to indicate information related to the attributes and / or events subscribed to by the second device.

[0181] In some embodiments, the subscription report includes at least one of the following: a subscription identifier; a service identifier, an attribute identifier, and an attribute value corresponding to each attribute subscribed by the second device; a service identifier, an event identifier, and an event status corresponding to each event subscribed by the second device; a service identifier, an attribute identifier, and an attribute value corresponding to an attribute that has changed; and a service identifier, an event identifier, and an event status corresponding to an event that has changed.

[0182] In some embodiments, the subscription identifier included in the subscription report is used to indicate which subscription request (or subscription configuration) the subscription report is sent to.

[0183] In some embodiments, the content included in the subscription report may be related to the way the first device sends the subscription report. For example, if the subscription report is a subscription report that the first device sends periodically according to the reporting interval (such as a periodic report), the subscription report may include the service identifier, attribute identifier, and attribute value corresponding to each attribute subscribed by the second device, and the service identifier, event identifier, and event status corresponding to each event subscribed by the second device; if the subscription report is a subscription report sent by the first device in response to a change in the attribute value of an attribute and / or a change in the event status of an event (such as a change-triggered report), the subscription report may include the service identifier, attribute identifier, and attribute value corresponding to the changed attribute; and the service identifier, event identifier, and event status corresponding to the changed event.

[0184] It is understood that the service identifier, attribute identifier, and attribute value corresponding to each attribute can be associated, that is, an attribute value is associated with an attribute, and an attribute is associated with a service identifier. The first device can send the associated service identifier, attribute identifier, and attribute value so that the second device can accurately determine the attribute value of the attribute it subscribes to. The same applies to service identifiers, event identifiers, and event states. This disclosure embodiment will not elaborate on this.

[0185] For example, if a second device subscribes to the switch attribute under the switch service and the brightness change event under the brightness adjustment service of a first device (such as a smart light) through a subscription request, the first device can periodically send a subscription report to the second device. This subscription report can be represented, for example, as: {"Subscription ID":1,{"SIID"=0,"CIID=0","Datavalue"=1},{"SIID"=1,"EIID=1","Datavalue"=80}}. This subscription report can be used to indicate that the subscription report corresponds to a subscription request with a subscription identifier of 1. The second device can, for example, determine the sender of the subscription report based on the subscription identifier, and then determine, based on the subscription report, that the attribute value of the switch attribute in the switch service of the first device is 1, i.e., the light is on, and the event status value of the brightness change event in the brightness adjustment service is 80, i.e., the brightness is 80%.

[0186] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0187] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0188] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0189] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transmit,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0190] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0191] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0192] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0193] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2104. For example, step S2101 may be implemented as a standalone embodiment, step S2102 may be implemented as a standalone embodiment, step S2104 may be implemented as a standalone embodiment, and step S2101 + step S2104 may be implemented as a standalone embodiment, but is not limited thereto.

[0194] In some embodiments, steps S2102 to S2104 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0195] In some embodiments, steps S2101 to S2103 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0196] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0197] Figure 3A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3A, the embodiments of the present disclosure relate to a communication method, which includes:

[0198] Step S3101: The second device sends a subscription request to the first device.

[0199] In step S3102, the first device sends a subscription report to the second device.

[0200] In some embodiments, a subscription request is used to indicate the attributes and / or events subscribed to by the second device; a subscription report is used to indicate information related to the attributes and / or events;

[0201] Both the first and second devices are power line carrier communication PLC devices.

[0202] In some embodiments, a subscription request includes at least one of the following:

[0203] Subscription identifier;

[0204] Reporting interval, used to indicate the reporting time interval for subscribed reports;

[0205] The first quantity indicates the number of attributes subscribed to by the second device;

[0206] The second quantity indicates the number of events subscribed to by the second device;

[0207] The service identifier for each attribute;

[0208] The attribute identifier for each attribute under the corresponding service;

[0209] The service identifier for each event;

[0210] The event identifier for each event under the corresponding service.

[0211] In some embodiments, the first device sends a subscription report to the second device, including:

[0212] The first device determines that the reporting interval is 0 or the default value, and in response to changes in the attribute value and / or changes in the event state, sends a subscription report to the second device; and / or,

[0213] The first device determines that the reporting interval is not equal to 0, and sends the subscription report to the second device according to the reporting interval.

[0214] In some embodiments, the subscription report includes at least one of the following:

[0215] Subscription identifier;

[0216] The service identifier, attribute identifier, and attribute value corresponding to each attribute subscribed to by the second device;

[0217] The service identifier, event identifier, and event status corresponding to each event subscribed to by the second device;

[0218] The service identifier, attribute identifier, and attribute value corresponding to the changed attribute;

[0219] The service identifier, event identifier, and event status corresponding to the event that has changed.

[0220] In some embodiments, the method includes:

[0221] The first device determines that the subscription identifier in the subscription request is 0, and deletes all subscription configurations of the second device on the first device.

[0222] In some embodiments, the first device sends a subscription report to the second device, including:

[0223] In response to receiving a subscription request, the first device sends a first subscription report to the second device. The first subscription report indicates the attribute value of each attribute subscribed by the second device, and / or the event status of each event subscribed by the second device.

[0224] In some embodiments, after the first device sends the first subscription report to the second device, the method further includes:

[0225] The first device sends a subscription response to the second device, which indicates whether the subscription was successful.

[0226] In some embodiments, the subscription report is sent by the first device in response to a change in the attribute value of an attribute and / or a change in the event state of an event;

[0227] The subscription report is sent to the second device according to the reporting interval.

[0228] In some embodiments, the method includes:

[0229] The second device determines that the subscription identifier in the subscription request is 0, and deletes all subscription configurations of the second device on the first device.

[0230] In some embodiments, the method includes:

[0231] The second device receives a first subscription report sent by the first device. The first subscription report is sent by the first device in response to receiving a subscription request. The first subscription report is used to indicate the attribute value of each attribute subscribed by the second device, and / or the event status of each event subscribed by the second device.

[0232] In some embodiments, the method further includes:

[0233] The second device receives the subscription response sent by the first device. The subscription response is used to indicate whether the subscription was successful.

[0234] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0235] Figure 3B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, the present disclosure relates to a communication method, which includes:

[0236] Step S3201: The second device sends a subscription request to the first device.

[0237] In step S3202, the first device sends a subscription report to the second device in response to a change in the attribute value of an attribute and / or a change in the event state of an event.

[0238] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0239] Figure 3C is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3C, the embodiments of the present disclosure relate to a communication method, which includes:

[0240] Step S3301: The second device sends a subscription request to the first device.

[0241] Step S3302: The first device sends a subscription report to the second device according to the reporting interval.

[0242] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0243] Figure 3D is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3D, the embodiments of the present disclosure relate to a communication method, which includes:

[0244] Step S3401: The second device sends a subscription request to the first device.

[0245] In step S3402, the first device sends a first subscription report to the second device.

[0246] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0247] Figure 3E is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3E, the embodiments of the present disclosure relate to a communication method, which includes:

[0248] Step S3501: The second device sends a subscription request to the first device.

[0249] In some embodiments, the subscription identifier of the subscription request is equal to 0. In some embodiments, the subscription request may also be referred to as an unsubscribe request.

[0250] Step S3502: The first device deletes the subscription configuration.

[0251] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0252] Figure 4 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 4, the embodiments of the present disclosure relate to a communication method, which includes:

[0253] Step S4101: The subscribing device sends a subscription command to the subscribed device.

[0254] In this context, the subscribing device can also be referred to as the subscriber or the device subscriber end, and the subscribed device can also be referred to as the subscribed party or the device subscribed end.

[0255] In some embodiments, a subscription command may be referred to as a "subscription request".

[0256] In some embodiments, the data format of the subscription command may be as shown in Table 1:

[0257] Table 1

[0258] In some embodiments, a subscription ID should be maintained on the subscribed device.

[0259] In some embodiments, modifications to the operation of reporting device attributes and events require adding a subscription ID to the reported device attributes and reported device events to indicate which subscription the event and attribute reporting is for.

[0260] In some embodiments, a subscription may consist of two parts:

[0261] Subscription: The subscription command is sent from the device subscriber to the device subscriber, carrying data as shown in Table 1.

[0262] Cancel subscription: The subscription command is sent from the device subscriber to the device subscriber, carrying the subscription ID. When the subscription ID = 0, it means that all subscriptions are deleted.

[0263] Step S4102: The subscribed party reports the status of the subscribed data to the subscribing device once.

[0264] In some embodiments, the purpose of the subscribed party reporting attributes / events immediately after receiving a subscription request is to perform state synchronization and prevent the subscriber from being notified in a timely manner if the state of the subscribed party changes when the subscriber sends a subscription request.

[0265] In step S4103, the subscribed device returns a subscription response to the subscribing device.

[0266] In step S4104, the subscribed device sends a subscription report to the subscribing device according to the subscription command.

[0267] In some embodiments, if the Interval in the subscription command received by the subscribed device is 0, it means that the event / attribute reporting operation will only be performed when the CIID attribute or EIID event status of the subscribed device changes; if the Interval is non-zero, the attribute / event needs to be reported according to the defined time interval, for example, Interval=2 means that the subscribed device reports the attribute / event at 2-second intervals.

[0268] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0269] This disclosure also provides an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the first device in any of the above methods. Furthermore, another apparatus is provided that includes units or modules for implementing the steps performed by the second device in any of the above methods.

[0270] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0271] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0272] Figure 5A is a schematic diagram of the structure of a first device according to an embodiment of this disclosure. The first device 5100 is used to perform any of the above methods. In some embodiments, as shown in Figure 5A, the first device 5100 may include at least one of a transceiver module 5101, a processing module 5102, etc.

[0273] In some embodiments, the transceiver module 5101 described above is configured to receive a subscription request sent by a second device, the subscription request being used to indicate the attributes and / or events subscribed to by the second device;

[0274] The transceiver module 5101 is further configured to send a subscription report to the second device, the subscription report being used to indicate information related to the attribute and / or the event;

[0275] Both the first device and the second device are power line carrier communication PLC devices.

[0276] In some embodiments, the transceiver module 5101 is used to perform at least one of the communication steps (but not limited to) performed by the first device in any of the above methods, such as sending and / or receiving, which will not be described in detail here. In some embodiments, the processing module 5102 is used to perform at least one of the other steps performed by the first device in any of the above methods, which will not be described in detail here.

[0277] Figure 5B is a schematic diagram of the structure of the second device proposed in an embodiment of this disclosure. The second device 5200 is used to perform any of the above methods. In some embodiments, as shown in Figure 5B, the second device 5200 may include at least one of a transceiver module 5201, a processing module 5202, etc.

[0278] In some embodiments, the transceiver module 5201 described above is configured to send a subscription request to a first device, the subscription request being used to indicate the attributes and / or events subscribed to by the second device;

[0279] The transceiver module 5201 is used to receive a subscription report sent by the first device, wherein the subscription report is used to indicate information related to the attribute and / or the event;

[0280] Both the first device and the second device are power line carrier communication PLC devices.

[0281] In some embodiments, the transceiver module 5201 is used to perform at least one of the communication steps (but not limited to) performed by the second device in any of the above methods, such as sending and / or receiving, which will not be described in detail here. In some embodiments, the processing module 5202 is used to perform at least one of the other steps performed by the second device in any of the above methods, which will not be described in detail here.

[0282] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated together. In some embodiments, the transceiver module may be interchangeable with a transceiver.

[0283] In some embodiments, the processing module may be a single module or may include multiple sub-modules. In some embodiments, the multiple sub-modules respectively perform all or part of the steps required by the processing module.

[0284] In some embodiments, the processing module can be interchanged with the processor, and the transceiver module can be interchanged with the transceiver.

[0285] Figure 6A is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 can be a network device (e.g., a terminal node, a central coordinator, a PLC sub-device, etc.), a terminal device (e.g., a user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0286] As shown in Figure 6A, the communication device 6100 is used to execute any of the above methods. In some embodiments, the communication device 6100 includes one or more processors 6101. The processor 6101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, while the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. In some embodiments, the communication device 6100 is used to execute any of the above methods. In some embodiments, one or more processors 6101 are used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0287] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps such as sending and / or receiving in the above-described method, and the processor 6101 performs at least one of the other steps. In some embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. In some embodiments, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0288] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data and / or instructions. In some embodiments, one or more processors 6101 are used to invoke instructions stored in the memory 6103 to cause the communication device 6100 to perform any of the above methods. In some embodiments, all or part of the memory 6103 may also be located outside the communication device 6100. In some embodiments, the communication device 6100 may include one or more interface circuits 6104. In some embodiments, the interface circuit 6104 is connected to the memory 6103 and can be used to receive data and / or instructions from the memory 6103 or other devices, and can be used to send data and / or instructions to the memory 6103 or other devices. For example, the interface circuit 6104 can read data and / or instructions stored in the memory 6103 and send the data and / or instructions to the processor 6101.

[0289] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, in some embodiments, the above IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0290] Figure 6B is a schematic diagram of the structure of chip 6200 according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of chip 6200 shown in Figure 6B, but it is not limited thereto.

[0291] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

[0292] In some embodiments, chip 6200 further includes one or more interface circuits 6202. In some embodiments, the terms interface circuit, interface, transceiver pin, etc., can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data and / or instructions. In some embodiments, all or part of the memories 6203 may be located outside of chip 6200. In some embodiments, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data and / or instructions from memory 6203 or other devices, and interface circuit 6202 can be used to send data and / or instructions to memory 6203 or other devices. For example, interface circuit 6202 can read data and / or instructions stored in memory 6203 and send the data and / or instructions to processor 6201.

[0293] In some embodiments, the interface circuit 6202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 6202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 6202 performs data and / or instruction interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of the other steps.

[0294] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. In some embodiments, some or all steps may also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0295] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. In some embodiments, the storage medium is an electronic storage medium. In some embodiments, the storage medium is a computer-readable storage medium, but is not limited thereto; it may also be a storage medium readable by other devices. In some embodiments, the storage medium may be a non-transitory storage medium, but is not limited thereto; it may also be a temporary storage medium.

[0296] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. In some embodiments, the program product is a computer program product. In some embodiments, the program product is stored on the storage medium.

[0297] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods. In some embodiments, the computer program includes computer program code that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method, performed by a first device, the method comprising: Receive a subscription request sent by a second device, the subscription request being used to indicate the attributes and / or events that the second device is subscribing to; Send a subscription report to the second device, the subscription report being used to indicate information related to the attribute and / or the event; Both the first device and the second device are power line carrier communication PLC devices.

2. The method of claim 1, wherein, The subscription request includes at least one of the following: Subscription identifier; Reporting interval, used to indicate the reporting time interval of the subscribed report; The first quantity indicates the number of attributes subscribed to by the second device; The second quantity indicates the number of events subscribed to by the second device; The service identifier of the service corresponding to each of the aforementioned attributes; The attribute identifier for each of the aforementioned attributes under the corresponding service; The service identifier for the service corresponding to each event; The event identifier for each event under the corresponding service.

3. The method of claim 2, wherein, Send a subscription report to the second device, including: If the reporting interval is determined to be 0 or default, and in response to a change in the attribute value of the attribute and / or a change in the event state, the subscription report is sent to the second device; and / or, If the reporting interval is determined to be non-zero, the subscription report is sent to the second device according to the reporting interval.

4. The method of claim 2 or 3, wherein, The subscription report includes at least one of the following: The subscription identifier; The second device subscribes to the service identifier, attribute identifier, and attribute value corresponding to each attribute; The second device subscribes to each event, including the service identifier, event identifier, and event status. The service identifier, attribute identifier, and attribute value corresponding to the changed attribute; The service identifier, event identifier, and event status corresponding to the event that has changed.

5. The method of any one of claims 2 to 4, wherein, The method includes: If the subscription identifier in the subscription request is determined to be 0, delete all subscription configurations of the second device on the first device.

6. The method of any one of claims 1 to 5, wherein, Send a subscription report to the second device, including: In response to receiving the subscription request, a first subscription report is sent to the second device, the first subscription report indicating the attribute value of each attribute subscribed by the second device, and / or the event status of each event subscribed by the second device.

7. The method of any one of claims 1 to 6, wherein, The method further includes: Send a subscription response to the second device, the subscription response indicating whether the subscription was successful.

8. A communication method performed by a second device, the method comprising: Send a subscription request to the first device, the subscription request being used to indicate the attributes and / or events that the second device is subscribing to; Receive a subscription report sent by the first device, the subscription report being used to indicate information related to the attribute and / or the event; Both the first device and the second device are power line carrier communication PLC devices.

9. The method of claim 8, wherein, The subscription request includes at least one of the following: Subscription identifier; Reporting interval, used to indicate the reporting time interval of the subscribed report; The first quantity indicates the number of attributes subscribed to by the second device; The second quantity indicates the number of events subscribed to by the second device; The service identifier of the service corresponding to each of the aforementioned attributes; The attribute identifier for each of the aforementioned attributes under the corresponding service; The service identifier for the service corresponding to each event; The event identifier for each event under the corresponding service.

10. The method of claim 9, wherein, The subscription report is sent by the first device in response to a change in the attribute value of the attribute and / or a change in the event status of the event; or, The subscription report is sent by the first device according to the reporting interval.

11. The method of claim 9 or 10, wherein, The subscription report includes at least one of the following: The subscription identifier; The second device subscribes to the service identifier, attribute identifier, and attribute value corresponding to each attribute; The second device subscribes to each event, including the service identifier, event identifier, and event status. The service identifier, attribute identifier, and attribute value corresponding to the changed attribute; The service identifier, event identifier, and event status corresponding to the event that has changed.

12. The method of any one of claims 8-11, wherein, The method further includes: The first subscription report is received from the first device in response to receiving the subscription request. The first subscription report is used to indicate the attribute value of each attribute subscribed by the second device, and / or the event status of each event subscribed by the second device.

13. The method of any one of claims 8 to 12, wherein, The method further includes: Receive a subscription response sent by the first device, the subscription response being used to indicate whether the subscription was successful.

14. A first device, comprising: A transceiver module is used to receive a subscription request sent by a second device, the subscription request being used to indicate the attributes and / or events subscribed to by the second device; The transceiver module is further configured to send a subscription report to the second device, the subscription report being used to indicate information related to the attribute and / or the event; Both the first device and the second device are power line carrier communication PLC devices.

15. A second device, comprising: A transceiver module is used to send a subscription request to a first device, the subscription request being used to indicate the attributes and / or events subscribed to by the second device; The transceiver module is configured to receive a subscription report sent by the first device, the subscription report being used to indicate information related to the attribute and / or the event; Both the first device and the second device are power line carrier communication PLC devices.

16. A communication device, comprising: One or more processors; The communication device is used to perform the method of any one of claims 1-7 or any one of claims 8-13.

17. A communication system comprising a first device and a second device, the first device being configured to implement the method of any one of claims 1-7, and the second device being configured to implement the method of any one of claims 8-13.

18. A storage medium storing instructions, wherein, When the instruction is executed on the communication device, the communication device performs the communication method as claimed in any one of claims 1-7 or any one of claims 8-13.

19. A computer program product comprising a computer program and / or instructions, wherein, When the computer program and / or the instructions are executed by the communication device, they implement the communication method as described in any one of claims 1-7 or any one of claims 8-13.

20. A computer program, when run on a computer, causes the computer to perform the communication method as claimed in any one of claims 1 to 7, or the communication method as claimed in any one of claims 8 to 13.

Images