Data acquisition method and related device

Abstract

The invention provides a data acquisition method and a related device, and the method comprises the steps: a first sub-management site receives first information from a management site, the first information is used for a plurality of sub-management sites to indicate to obtain acquisition data in a first time slot, and the plurality of sub-management sites comprise the first sub-management site; and the first sub-management site receives the first information and sends a first scheduling message for indicating at least one sub-site to report the collected data in the first time slot. By adopting the method, a plurality of sub-management sites with non-conflict resources can concurrently acquire the acquired data within the time slot level, the data acquisition efficiency is improved, meanwhile, message collision and data loss possibly caused by concurrently acquiring the acquired data by the plurality of sub-management sites are avoided, and the reliability of data transmission is improved.

Description

Technical Field

[0001] The present application relates to the field of smart grid technology, and in particular to a data collection method and related devices. Background Art

[0002] In the construction of smart grid, remote data collection and interaction of smart meters are important parts in the field of electricity consumption. The electricity consumption information collection system of power users consists of: master station, concentrator (field terminal), and electric meter. The channels between the master station and the concentrator are wireless public network general packet radio service (GPRS) or code division multiple access (CDMA), optical fiber, etc. The local meter reading channels of the concentrator are mainly carrier, wired 485, micro-power wireless, etc., of which more than 90% are carrier channels.

[0003] In addition, a central coordinator (CCO) is installed inside the concentrator, and a station (STA) is installed inside the collector or the electric energy meter. Both the CCO and the STA are physically connected to the power line to form a communication network based on the power line carrier (PLC). The concentrator directly communicates with the carrier meter through the PLC communication network, or communicates with the 485 meter through the collector.

[0004] PLC technology has been widely used in low-voltage substations. However, with the business expansion and deepening of technical applications of new power systems such as user electricity collection, photovoltaics, and charging piles, there is an increasing demand for full collection of data at the end of the data grid and real-time data at the "minute level". The current high-speed power line carrier (HPLC) communication technology has become increasingly difficult to achieve, becoming a bottleneck for the access of new equipment and the development of new businesses. Summary of the invention

[0005] The embodiment of the present application provides a data collection method and related devices. By configuring the site with instructions for reporting the collected data at the time slot level, each site can report the electricity consumption collection data efficiently and without collision, fully utilizing the channel resources and improving the speed of reading the electricity meter.

[0006] In a first aspect, the present application provides a data collection method, which is applied to a first sub-management site, and the method includes: receiving first information from the management site, the first information is used to instruct multiple sub-management sites to obtain collected data within a first time slot; sending a scheduling message, the scheduling message is used to instruct at least one sub-site to report the collected data within the first time slot.

[0007] In an embodiment of the present application, a collaborative scheduling indication is sent by a management site to multiple sub-management sites whose resources do not conflict. The indication can enable multiple sub-management sites to obtain the collected data of the sub-sites using different frequency domain resources or spatial domain resources in the same time slot, thereby improving data collection efficiency and avoiding possible message collisions or channel interference when the sub-sites report collected data, thereby improving data transmission reliability.

[0008] In some possible implementations, the at least one sub-site includes a first sub-site, and the method further includes: receiving first data reported by the first sub-site in a first time slot.

[0009] In some possible implementations, the at least one sub-site includes a second sub-site, and the method further includes: receiving first feedback information reported by the second sub-site in a first time slot, wherein the first feedback information does not include the collected data.

[0010] In some possible implementations, after receiving the first data reported by the first sub-station in the first time slot, the method further includes: sending second feedback information to the first sub-station, where the second feedback information is used to indicate that the first data has been received.

[0011] The above-mentioned interactive process setting ensures the integrity of the communication interaction between the management site and the sub-management site, and avoids the communication process stagnation or signaling waste caused by the management site or the sub-management site not receiving feedback information, thereby improving communication efficiency.

[0012] In some possible implementations, the first information is further used to instruct the second sub-management site not to acquire the collected data in the first time slot.

[0013] In some possible implementations, the method further includes: receiving second information from the management site, the second information being used to instruct the third sub-management site to acquire collected data in a second time slot, the second time slot being earlier than the first time slot; and forwarding the second information to the third sub-management site.

[0014] In an embodiment of the present application, for a sub-management site directly connected to a management site, or a sub-management site connected through multiple layers of subordinate management sites, the time slot for obtaining collected data set for the latter is earlier than the time slot for obtaining collected data set for the former. This ensures that whether it is a STA that directly obtains collected data or a subordinate PCO that needs to summarize the collected data of the STA, the management sub-site can obtain the collected data in time within the first time slot, thereby ensuring the effectiveness of the management site's scheduling of the sub-management site.

[0015] In some possible implementations, the management site is a central coordinator CCO, the sub-management site is a proxy coordinator PCO, and the sub-site is a PCO or a site STA.

[0016] In some possible implementations, the management site, the sub-management site and the sub-site support Orthogonal Frequency Division Multiple Access (OFDMA) technology.

[0017] In a second aspect, the present application provides a data collection method, applied to a first sub-site, the method comprising: receiving a first scheduling message, the first scheduling message being used to indicate acquisition of collected data within a first time slot; and reporting first data to the sub-management site within the first time slot.

[0018] In some possible implementations, reporting the first data to the first sub-management site includes: reporting the first data to the first sub-management site via a first message, wherein the first message also includes second data reported by the third sub-site.

[0019] In the embodiment of the present application, different resource units uploaded by multiple sub-sites are combined into a first message and uploaded to the sub-management site. This can save time for reporting collected data to the sub-management site and improve data collection efficiency. In addition, since the sub-site aggregates multiple data reported to the sub-management site into one message, the probability of conflict between messages sent to the sub-management site is further reduced, thereby improving the reliability of data transmission.

[0020] According to a third aspect, a communication device is provided, the device comprising:

[0021] A transceiver unit, configured to receive first information from a management site, wherein the first information is used to instruct a plurality of sub-management sites to acquire collected data in a first time slot, wherein the plurality of sub-management sites include a first sub-management site;

[0022] The transceiver unit is further used to send a first scheduling message, where the first scheduling message is used to instruct at least one sub-station to report collected data within a first time slot.

[0023] In some possible implementations, the at least one sub-site includes a first sub-site, and the transceiver unit is further configured to: receive first data reported by the first sub-site in a first time slot.

[0024] In some possible implementations, at least one sub-site includes a second sub-site, and the transceiver unit is further configured to: receive first feedback information reported by the second sub-site in a first time slot, wherein the first feedback information does not include the collected data.

[0025] In some possible implementations, after receiving the first data reported by the first sub-station in the first time slot, the transceiver unit is further used to: send second feedback information to the first sub-station, where the second feedback information is used to indicate that the first data has been received.

[0026] In some possible implementations, the first information is further used to instruct the second sub-management site not to acquire the collected data in the first time slot.

[0027] In some possible implementations, the transceiver unit is also used to: receive second information from the management site, the second information is used to instruct the third sub-management site to obtain collected data in a second time slot, the second time slot is earlier than the first time slot; and forward the second information to the third sub-management site.

[0028] In some possible implementations, the management site is a central coordinator CCO, the sub-management site is a proxy coordinator PCO, and the sub-site is a PCO or a site STA.

[0029] In some possible implementations, the management site, the sub-management site and the sub-site support Orthogonal Frequency Division Multiple Access (OFDMA) technology.

[0030] In a fourth aspect, a communication device is provided, the device comprising:

[0031] A transceiver unit, used to receive a first scheduling message, where the first scheduling message is used to instruct to report the collected data in a first time slot;

[0032] The transceiver unit is further configured to report first data to the first sub-management site within a first time slot.

[0033] In some possible implementations, reporting the first data to the first sub-management site includes: reporting the first data to the first sub-management site via a first message, wherein the first message also includes second data reported by the third sub-site.

[0034] In a fifth aspect, the present application provides a communication device, comprising a processor, wherein the processor is coupled to a memory, and when the processor executes a computer program or instruction in the memory, the method of any embodiment of the first aspect above is executed, or the method of any embodiment of the second aspect above is executed.

[0035] Optionally, the device also includes a memory.

[0036] Optionally, the device further includes a communication interface, and the processor is coupled to the communication interface.

[0037] Optionally, there are one or more processors and one or more memories.

[0038] Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0039] Optionally, the transceiver may include a transmitter (transmitter) and a receiver (receiver).

[0040] In one implementation, the communication device is a terminal device. When the communication device is a terminal device, the communication interface may be a transceiver, or an input / output interface. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0041] In another implementation, the communication device is a chip or a chip system. When the device is a chip or a chip system, the communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip or the chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0042] In a sixth aspect, the present application provides a communication system, the communication system comprising the data acquisition device of the third aspect and the transmission device of the fourth aspect.

[0043] In the seventh aspect, the present application provides a computer program product, which includes: a computer program (also referred to as code, or instructions), which, when executed, enables a computer to execute a method in any possible implementation of the first aspect or the second aspect.

[0044] In an eighth aspect, the present application provides a computer-readable storage medium, which stores a computer program (also referred to as code, or instructions). When the computer program is run on a computer, the computer executes a method in any possible implementation of the first to fourth aspects above.

[0045] In a ninth aspect, the present application further provides a circuit, comprising: a processor and an interface, for executing a computer program or instruction stored in a memory, and executing a method in any possible implementation of the first to second aspects above. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 A schematic diagram of the power system architecture used in the embodiments of the present application;

[0047] Figure 2 A schematic diagram of a communication architecture provided for an embodiment of the present application;

[0048] Figure 3A A flow chart of electric power meter reading provided in an embodiment of the present application;

[0049] Figure 3B Another electric power meter reading flow chart provided in an embodiment of the present application;

[0050] Figure 4A A data collection method flow chart is provided for an embodiment of the present application;

[0051] Figure 4BA schematic diagram of a power communication system divided into management blocks according to an embodiment of the present application;

[0052] Figure 4C A schematic diagram of a time slot setting provided in an embodiment of the present application;

[0053] Figure 4D A flowchart of the interaction process between PCO and STA provided in an embodiment of the present application;

[0054] Figure 4E A schematic diagram of a communication link of a power system provided in an embodiment of the present application;

[0055] Figure 4F A schematic diagram of the structure of a first message provided in an embodiment of the present application;

[0056] Figure 5 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0057] Figure 6 A schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0058] The embodiments of the present invention are described below in conjunction with the accompanying drawings in the embodiments of the present invention.

[0059] The terms "first", "second", "third" and "fourth" etc. in the specification and claims of the present application and the drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

[0060] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0061] "Multiple" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent three situations: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions are used to indicate any combination of the listed items; for example, at least one of A, B and / or C can represent the following situations: A exists alone, B exists alone, C exists alone, A and B exist at the same time, B and C exist at the same time, A and C exist at the same time, and A, B and C exist at the same time, where A, B, and C can be single or multiple.

[0062] Figure 1 This is a schematic diagram of the power system architecture used in the embodiment of this application. Figure 1 As shown, the user electricity information collection system includes a concentrator and an electric meter, wherein the electric meter may include a carrier meter and a 485 meter. A CCO is installed in the concentrator, and an STA is installed in the collector or the carrier meter. CCO and STA communicate with each other through the PLC communication network, or communicate with the 485 meter through the collector. The concentrator collects data from the carrier meter or the 485 meter, which is called the power meter reading process. This process can be used for: equipment status monitoring. Specifically, for example, on-site calculation and analysis, statistics on equipment operation status, such as meter inaccuracy, module in-place detection, etc.; support collector access to sensors, real-time understanding of working condition information, etc. This process can also be used for: power quality monitoring. Specifically, for example, real-time statistics of voltage, current, and three-phase unbalanced over-limit; support load imbalance, timely phase change load balancing adjustment; statistics on voltage qualification rate information, and low voltage alarm reporting, etc.

[0063] Figure 2 A communication architecture diagram provided in an embodiment of the present application. Figure 2 As shown, the communication architecture includes devices (or modules) that communicate using a PLC communication network. Specifically, it includes CCO, proxy coordinator (PCO), and STA. Among them, STA can communicate directly with CCO, for example, STA7 is connected to CCO. It can also communicate with CCO through PCO, for example, STA1 and STA2 are connected to CCO through PCO1. PCO can be connected to CCO directly, or it can be connected to CCO through multiple levels of PCO, for example, PCO4 is connected to CCO through PCO3.

[0064] The prior art is introduced below.

[0065] See also Figure 3A , Figure 3A A flow chart of electric power meter reading provided in the embodiment of the present application is as follows: Figure 3AAs shown, in this technical solution, the process of the concentrator reading the meter through the power line carrier is:

[0066] (1) The concentrator sends a meter reading command to the CCO.

[0067] It should be noted that the CCO is a communication module in the concentrator, and the concentrator performs carrier communication with the STA through the CCO.

[0068] (2) The CCO forwards the command to the STA via the power line.

[0069] The STA may be a communication module in a collector or a carrier table, and is used for performing carrier communication with the CCO.

[0070] (3) After receiving the command from CCO, STA sends the meter reading message to the meter.

[0071] The electric meter can be the aforementioned Figure 1 458 meter in. At this time, the STA is located in the collector, and the collector sends the meter reading message to the 485 meter through the 485 bus. Or the electric meter can also be a carrier meter. At this time, the STA located in the carrier meter sends the meter reading message to the carrier meter where it is located.

[0072] (4) After the meter responds, it sends the message to the STA.

[0073] (5) STA sends the meter's response message to CCO.

[0074] (6) The CCO sends the response message to the concentrator.

[0075] The concentrator needs to go through the above process to read a data item of the meter, and can only read one data item at a time, and the reading speed is very slow. It can only guarantee the most basic meter reading functions such as daily frozen electricity, and cannot meet the expansion of multiple businesses.

[0076] See also Figure 3B , Figure 3B Another electric power meter reading flow chart provided in the embodiment of the present application is as follows: Figure 3B As shown, in this technical solution, the process of the concentrator reading the meter through the power line carrier is:

[0077] (1) The concentrator sends a meter reading command to the CCO, but does not wait for the meter reading result response. Instead, it continues to send multiple meter reading frames until it receives a negative response from the CCO because the concurrent pool is full and cannot be processed. Then it stops sending meter reading frames to the CCO.

[0078] (2) The CCO temporarily stores the received meter reading commands from the concentrator in its own concurrent pool, and then encapsulates multiple messages into HPLC protocol frames and sends them to multiple different STAs at the same time, or to the PCO, which then sends them to one or more STAs under its management.

[0079] (3) After receiving the command from CCO, STA sends the meter reading message to the meter.

[0080] (4) After the meter responds, it sends the message to the STA.

[0081] (5) STA sends the meter response message to CCO. Assuming that STA is connected to CCO through PCO, STA sends the meter response message to PCO, which then sends it to CCO.

[0082] (6) The CCO sends the response message to the concentrator.

[0083] (7) At this time, the concentrator sends a new meter reading frame to fill the vacant position in the CCO concurrent pool to reach the maximum concurrent number.

[0084] The concentrator reads the meter data items through the above process. It can read the data of multiple meters concurrently in the same time period, greatly improving the reading speed. Figure 3A The technology in the paper can greatly improve the speed of the technology; however, it also has obvious disadvantages and shortcomings:

[0085] 1. When scheduling message sending, the above steps (2) and (5) do not have a scheduling mechanism that adapts to the channel characteristics, do not take into account the conflict domain relationship of multiple STAs, and completely rely on the conflict detection mechanism. The probability of collision is high during concurrent reading, and the bandwidth cannot be fully utilized. The channel utilization rate is not high, and minute-level collection is very difficult.

[0086] 2. When transmitting messages between STA and PCO, multiple points queue up and compete for transmission in series, which does not fully utilize spectrum resources and leads to low channel utilization.

[0087] Based on this, see Figure 4A , Figure 4A A data collection method flow chart is provided for an embodiment of the present application, and the method comprises the following steps:

[0088] 101. A first sub-management site receives first information from a management site, where the first information is used to instruct a plurality of sub-management sites to acquire collected data in a first time slot.

[0089] The multiple sub-management sites include a first sub-management site.

[0090] In the embodiment of the present application, the management site refers to a site used for general manager scheduling, which may specifically refer to a CCO. A sub-management site refers to a site that receives the general manager scheduling information and schedules other sub-sites according to the scheduling information, which may be a PCO. A sub-site refers to a site STA that specifically collects meter data, or it may also refer to a lower-level PCO that has collected meter data in advance and is waiting to be scheduled by the PCO. The management site sends a first message to multiple sub-management sites that it manages (directly connected) to instruct the multiple sub-management sites to report the collected data within the first time slot. Specifically, Figure 2 As shown in , when CCO is a management site, the corresponding multiple sub-management sites are PCO1, PCO2, and PCO3, and the sub-sites corresponding to PCO1 include STA1 and STA2. The sub-sites corresponding to PCO3 include STA4 and PCO4.

[0091] The first information sent by the management site may be information sent specifically to certain specific sites among the multiple sub-management sites connected to the management site. Alternatively, the first information may be information sent to all sub-management sites connected to the management site. Assuming that the first information is information sent to all sub-management sites, the sub-management site that receives the first information can read the indication information related to itself from it.

[0092] The first information indicates that multiple sub-management sites acquire collected data in the first time slot, that is, the management site can schedule non-conflicting sub-management sites in parallel. In addition, the first information can indicate that other sub-management sites acquire collected data in other time slots, that is, the management site can schedule conflicting sub-management sites sequentially. Non-conflict means that the airspace resources between multiple sub-management sites do not overlap, and conflict means that the airspace resources of the sub-management sites overlap.

[0093] In addition, the same sub-management site manages multiple sub-sites, and the same sub-management site and the multiple sub-sites it manages can be divided into a management block. Figure 4B , Figure 4B A schematic diagram of a power communication system divided into management blocks provided in an embodiment of the present application, such as Figure 4BAs shown, the blocks divided by the matrix are a management block, and one management block may include a sub-management block. For example, the management block corresponding to PCO3 includes a sub-management block corresponding to PCO4. If there is no conflict between multiple STAs in the same management block, the STA supports orthogonal frequency division multiple access (OFDMA) technology, and the frequency domain resources between multiple STAs in the same management block do not overlap. Therefore, (strong) conflict between management blocks may also refer to the overlap of spatial domain resources of management blocks, and a large amount of overlap of frequency domain resources. Weak conflict may refer to the overlap of spatial domain resources of multiple management blocks, and a small amount of overlap of frequency domain resources of some STAs. No conflict may also refer to the overlap of spatial domain resources of management blocks, but the complete non-overlap of frequency domain resources.

[0094] The management site may send the first information to indicate that multiple management blocks that do not conflict or that have weak conflicts are scheduled in parallel; and multiple management blocks that have strong conflicts are scheduled sequentially, not concurrently.

[0095] The first sub-management site is included in the multiple sub-management sites indicated by the first information. The first information can be used to indicate that the first sub-management site acquires collected data within the first time slot. On the other hand, the first information can be used to indicate that the second sub-management site does not acquire collected data within the first time slot. The indication method includes explicit indication and implicit indication. Among them, explicit indication means that the first information includes clear information indicating that the second sub-management site does not acquire collected data within the first time slot. Implicit indication means that the first information does not have a clear information indication, but it is inferred through existing information that the second sub-management site does not acquire collected data within the first time slot. For example, the second sub-management site receives the first information and reads that the second sub-management site is not included in the multiple sites that acquire collected data within the first time slot indicated by the first information. Or, for example, the first information is only sent to multiple sites that acquire collected data within the first time slot, and the fourth sub-management site is not included in the multiple sites.

[0096] In the above description, the first information is used to indicate that a sub-management site reports collected data, which can be specifically referred to by the terminal equipment identity (TEI) of the sub-management site. Alternatively, the inherent identifier of other terminal devices or a newly named logical identifier can be used to refer to the site, which is not limited in the embodiments of the present application.

[0097] Optionally, the management site and the sub-management site can agree on a group time slot beacon entry to indicate that the management site will send a reservation time slot for the sub-management site to schedule the sub-management site to report the collected data (hereinafter, the management site is CCO and the sub-management site is PCO for example). The beacon entry is the information included in the beacon frame sent by the management site. If the beacon frame includes a group time slot beacon entry, other PCOs can read the group time slot beacon entry when establishing a communication connection with the CCO. The group time slot beacon entry is used to allocate group time slots, so it can also be called a group time slot allocation entry.

[0098] Please refer to Table 1:

[0099] Table 1

[0100] value definition 0x00 Site Capability Items 0x01 Route parameter entry 0x02 Frequency band change entry 0x03-0xBF reserve 0xC0 Time slot allocation entry 0xC1 Group Slot Assignment Entries 0xC2-0xFF reserve

[0101] As shown in Table 1, it is a schematic table of information included in a beacon frame provided in an embodiment of the present application. The table includes a newly added group time slot allocation entry, which is represented by the value 0xC1.

[0102] Further, see Table 2:

[0103] Table 2

[0104]

[0105]

[0106] Table 2 is a message setting method for a group time slot allocation entry provided in an embodiment of the present application. As shown in Table 2, the fields that may be included in the message include: time slot start, time slot end, number of TEI groups, and specific TEI groups. In addition, the definition description in the table is a description of the message field setting, which is not included in the message content.

[0107] The "Time Slot Start" field and the "Time Slot End" field are used to define the start and end positions of the time slots for the site to acquire collected data. The time slots for acquiring collected data are referred to as reserved time slots. For example, the first time slot indicated in the aforementioned first information is a reserved time slot. In addition, a reserved time slot (or first time slot) does not necessarily refer to a complete time slot, but refers to the duration of the reserved time slot at the time slot level (or it can be said that the duration of the reserved time slot is less than or equal to the duration of a time slot). The units corresponding to the time slot start position and the time slot end position can be microseconds (us) or milliseconds (ms), etc.

[0108] For the "TEI Group Number" field, for example, the binary value of this field is 00000010, which means that there are 2 TEI groups that can use the reserved time slot defined by this message (acquire collected data in the reserved time slot). Each TEI group has a corresponding reserved time slot. Each TEI group can include TEIs of multiple PCOs, which have no conflict or weak conflict with each other. For example, the TEI group is Figure 4B The corresponding reservation time slots of PCO1 and PCO2 in the table are the first time slots, indicating that the management blocks corresponding to PCO1 and PCO2 both obtain the collected data in the first time slot. If this field is empty (null), it means that the PCO connected to the CCO will not actively obtain the collected data in the reservation time slot.

[0109] For the "TEI Group" field, this field is used to indicate the TEI corresponding to the sub-management site specifically included in the TEI group. For example, the TEI corresponding to PCO1 is 1, and the bit corresponding to each TEI is 8, then the TEI Group field includes the binary 00000001, which is used to indicate that PCO1 can obtain the collected data within the reserved time slot.

[0110] 102. The first sub-management site sends a first scheduling message, where the first scheduling message is used to instruct at least one sub-site to report collected data in the first time slot, and the at least one sub-site includes the first sub-site.

[0111] After the first PCO receives the first information sent by the CCO, it can directly obtain the collected data in the first time slot, specifically, obtain the collected data from the STA connected to itself, or obtain the collected data from the lower-level PCO connected to itself (not directly connected to the CCO, but connected to the CCO through the first PCO). Figure 4B The acquisition data obtained by PCO3 also comes from PCO4.

[0112] Optionally, the method may further include step 103: the first sub-site receives a first scheduling message, and reports first data to the first sub-management site in a first time slot.

[0113] After receiving the scheduling message, STA can report the collected data. As described above, STA can be located in the carrier table, then STA obtains the meter data of the carrier table and reports it. Or STA can be located in the collector, then STA obtains the meter data from the 485 table through the 485 bus and reports it. The lower-level PCO can also report the collected data after receiving the scheduling message. The collected data in the lower-level PCO can be obtained in advance from the STA connected to it.

[0114] After the first PCO obtains the collected data reported by the sub-station, it can send it to the CCO after receiving the scheduling message from the CCO. Alternatively, assuming that the airspace resources between PCOs do not overlap, the PCO can also actively send it to the CCO after obtaining the collected data. This embodiment of the application is not limited.

[0115] It can be seen that in the embodiment of the present application, the management site sends a collaborative scheduling indication to multiple sub-management sites whose resources do not conflict, so that the multiple sub-management sites obtain the collected data of the sub-sites through different frequency domain resources or spatial domain resources in the same time slot, thereby improving data collection efficiency and avoiding possible message collisions or channel interference when the sub-sites report the collected data, thereby improving data transmission reliability.

[0116] Optionally, the method also includes: 104. The third sub-management site receives second information from the management site, and the second information is used to instruct the third sub-management site to obtain collected data within a second time slot, and the second time slot is earlier than the first time slot; 105. The third sub-management site sends a second scheduling message, and the second scheduling message instructs at least one sub-site to report collected data to the second sub-management site within the second time slot.

[0117] 106. The third sub-site receives the second scheduling message, and reports the collected data to the second sub-management site in the second time slot.

[0118] As described above, a third PCO (which may be called a subordinate PCO of the first PCO) connected to the CCO via the first PCO may be included. In order to enable the first PCO to acquire the collected data of the third PCO in the first time slot, the CCO needs to instruct the third PCO to acquire the collected data in advance.

[0119] See also Figure 4C , Figure 4C A schematic diagram of a time slot setting provided in an embodiment of the present application is shown in FIG. Figure 4C As shown, assuming that PCO3 is the first PCO and PCO4 is the third PCO, CCO first sends a second message to PCO4, instructing PCO4 to obtain the collected data in the second time slot. PCO4 obtains and stores the collected data from STA5 and STA6 in the second time slot. Then CCO sends a first message to PCO3, instructing PCO3 to obtain the collected data in the first time slot. Then PCO3 obtains and summarizes the collected data from STA4 and PCO4 in the first time slot, and reports it to CCO according to CCO's scheduling, or actively reports it to CCO. The second time slot is earlier than the first time slot. In other words, the farther the communication distance between the sub-management site and the top-level management site is, the earlier the corresponding time slot for obtaining the collected data is.

[0120] It can be seen that in the embodiment of the present application, for the sub-management site directly connected to the management site, or the sub-management site connected through multiple layers of subordinate management sites, the time slot for obtaining the collected data set for the latter is earlier than the time slot for obtaining the collected data set for the former. This ensures that whether it is the STA that directly obtains the collected data or the subordinate PCO that needs to summarize the collected data of the STA, the management sub-site can obtain the collected data from it in time within the first time slot, thereby ensuring the effectiveness of the management site's scheduling of the sub-management site.

[0121] Optionally, the at least one sub-site includes a second sub-site, and the method further includes: the first sub-management site receives first feedback information reported by the second sub-site in a first time slot, wherein the first feedback information does not include the collected data.

[0122] Optionally, after receiving the first data reported by the first sub-station in the first time slot, the method further includes: the first sub-management station sending second feedback information to the first sub-station, where the second feedback information is used to indicate that the first data has been received.

[0123] As described above, the same management block may include a PCO and multiple sub-stations (STAs) connected to the PCO.

[0124] See also Figure 4D , Figure 4D A flowchart of the interaction process between PCO and STA provided in the embodiment of the present application is as follows: Figure 4D As shown in the figure, the interaction process between PCO and STA includes the following steps:

[0125] 1031. The PCO sends a scheduling message to the STA.

[0126] The PCO may send a scheduling message to the STA after receiving the time slot reservation message from the CCO (such as the first information received by the first PCO mentioned above).

[0127] 1032. STA sends a data collection message to PCO.

[0128] Assuming that the STA collects meter data, it can report it to the PCO through the data collection message.

[0129] 1033. The PCO sends a data acquisition reception confirmation message to the STA.

[0130] After receiving the first acquisition data reported by the STA, the PCO can send a selective acknowledgement character (SACK) message to the STA to indicate that it has received the acquisition message. Assuming that the PCO only receives part of the acquisition message, the PCO can send a retransmission instruction to the STA. Alternatively, after receiving the first acquisition data reported by the STA, the PCO can also send the next scheduling message to the STA to obtain the next acquisition data.

[0131] 1034. STA sends the next data acquisition message or the no data acquisition message to PCO.

[0132] Assuming that the PCO sends the next scheduling message to the STA, the STA can send the next data collection message to the PCO. Or assuming that the STA does not collect meter data, it can send a no data collection message to the PCO. The no data collection message can be expressed in the following ways: a. Not sending any message; b. Sending a message indicating that there is no data to report; c. Sending an empty data collection message, that is, there is no load data in the data collection message.

[0133] It should be noted that the above steps 1031 to 1034 are only examples. In the implementation process of the method, only some of the above steps may be included. For example, after step 1032, the PCO receives the data acquisition message reported by the STA and may no longer send SACK, etc. This embodiment of the present application is not limited to this. The above interaction process may also be an interaction process between the CCO and the directly connected STA, which will not be described in detail here.

[0134] It can be seen that the above-mentioned interactive process setting ensures the integrity of the communication interaction between the sub-management site and the sub-site, and avoids the sub-management site or the sub-site from causing the communication process to stagnate or signaling to be wasted due to the failure to receive feedback information, thereby improving communication efficiency.

[0135] Optionally, the first sub-site reporting the first data to the first sub-management site includes: the first sub-site reporting the first data to the first sub-management site through a first message, wherein the first message also includes second data reported by the third sub-site.

[0136] The frequency domain resources of multiple sub-sites connected to the PCO do not overlap. Figure 4E , Figure 4E A communication link diagram of a power system provided in an embodiment of the present application is shown in FIG. Figure 4E As shown, the CCO or PCO sends a message to the STA via a downlink (DL) OFDMA link, and the STA sends a message via an uplink (UL) OFDMA link. Alternatively, the link between the CCO and the relay PCO may also be an OFDMA link, which is not specifically limited in the embodiments of the present application.

[0137] In an OFDMA link, STAs occupying different frequency domain resources can be time-division multiplexed. Figure 4E As shown in , STA1 reports first data (referred to as the first RU message in the figure) through the first resource unit (RU), and STA2 reports second data (referred to as the second RU message in the figure) through the second RU. The first RU message and the second RU message form a first message reported to PCO1.

[0138] See also Figure 4F , Figure 4F A schematic diagram of the structure of a first message provided in an embodiment of the present application, such as Figure 4F After receiving the first information, the first sub-management site sends a first scheduling message (trigger message) to the multiple sub-sites, corresponding to Figure 4F The triggering stage in the process is that the first sub-management site performs sub-site access processing and frame control (FC) detection through the preamble. Then comes the inter-frame space (IFS) stage. After that, multiple sub-sites perform UL OFDMA transmission. Including RUs transmitted by multiple sub-sites (U0~U3) on different frequency bands, whose payload (PL) is the collected data reported by the sub-site. These different RUs transmitted in the same time slot are combined into the first message and sent to the first PCO.

[0139] Optionally, the multiple sub-sites of the first sub-management site include a third sub-management site, and the first message also includes collected data reported by the third sub-management site.

[0140] As described above, the third PCO has acquired the collected data in the second time slot. Then the first PCO can schedule the third PCO to report the collected data in the first time slot. The collected data reported by the third PCO and the collected data reported by other STAs are combined into a first message for uploading.

[0141] It can be seen that in the embodiment of the present application, different resource units uploaded by multiple sub-sites are combined into a first message and uploaded to the sub-management site. This can save time for reporting collected data to the sub-management site and improve data collection efficiency. In addition, since the multiple data reported by the sub-site to the sub-management site are aggregated into one message, the probability of conflict in the message sent to the sub-management site is further reduced, and the reliability of data transmission is improved.

[0142] Optionally, the format of the scheduling message sent by the CCO or PCO in the embodiment of the present application can be referred to Table 3:

[0143] Table 3

[0144]

[0145] As described above, the terminal device for collecting data is STA, which can be directly connected to CCO or PCO. CCO or PCO can send a scheduling message to STA to obtain collected data. The message format sent to STA can be as shown in Table 3.

[0146] The "Type" field is included, which is used to indicate the corresponding message type. The value of this field can be fixed to "2", indicating that the corresponding message type is "confirmation frame". Of course, this field can also be other values, which are not specifically limited in the embodiments of the present application.

[0147] A "link access type" field may also be included, which may be used to indicate the link access type between the PCO and the STA. In the embodiment of the present application, the value of this field may include "0" to indicate a MAC protocol data unit (MPDU).

[0148] A "network identifier (NID)" field may also be included to identify devices and information flows in the network. For example, in an embodiment of the present application, the NID of the network may represent a PCO and a STA and an information flow in the communication network.

[0149] A "source TEI" field may also be included, indicating the TEI of the site that sends the message.

[0150] A "target TEI" field may also be included to indicate the TEI of the station of the message. The source TEI or target TEI field may be the TEI corresponding to the PCO or STA.

[0151] The "message type" field may also be included to define the type of the scheduling message. A value of "0" indicates a scheduling message sent to the destination TEI site. A value of "1" indicates a data collection reception confirmation message sent by the source TEI site. A value of "2" indicates a non-data collection message sent by the target TEI site, etc.

[0152] The above message may also include other fields, which are not limited in the embodiment of the present application.

[0153] The embodiment of the present application sets the format of the dispatch message sent to the sub-site through the above Table 3, so that the dispatch message can carry the key information required to represent when acquiring the collected data from the sub-site, thereby ensuring the effectiveness of the communication process.

[0154] In addition, in the above embodiment, when the management site schedules the sub-management site to report the collected data, it corresponds to the first time slot, that is, the scheduling of the management site is at the time slot level. However, it can be understood that the time slot level is just an example of a smaller time unit. Therefore, the time slot in the above embodiment can also be replaced by other smaller time units, such as minutes, seconds, milliseconds, microseconds, etc., or symbol level, etc.

[0155] In the above embodiment, STA is a station that supports OFDMA technology, and each station can be scheduled in parallel. When STA does not support OFDMA technology, each station can be scheduled in series, and the PCO that manages multiple STAs can also be scheduled in parallel by the CCO through reserved time slots. That is, the above embodiment can also be used in STAs that do not support OFDMA technology. The relevant description can be found above and will not be repeated here.

[0156] like Figure 5 The present application also provides a communication device 1100, which may be a terminal device, or may be used for but not limited to a terminal device. The communication device 1100 includes a device for performing the above Figure 4A to Figure 4F Specifically, the communication device 1100 may include a transceiver unit 1101, which is applied to a first sub-management site, and can be specifically applied to a proxy coordinator PCO.

[0157] The transceiver unit 1101 is used to receive first information from a management site, where the first information is used to instruct multiple sub-management sites to obtain collected data in a first time slot;

[0158] The transceiver unit 1101 is further used to send a first scheduling message, where the first scheduling message is used to instruct at least one sub-station to report collected data in a first time slot.

[0159] Optionally, the at least one sub-site includes a first sub-site, and the transceiver unit 1101 is further configured to: receive first data reported by the first sub-site in a first time slot.

[0160] Optionally, the at least one sub-site includes a second sub-site, and the transceiver unit 1101 is further configured to: receive first feedback information reported by the second sub-site in a first time slot, wherein the first feedback information does not include the collected data.

[0161] Optionally, after receiving the first data reported by the first sub-station in the first time slot, the transceiver unit 1101 is further used to: send second feedback information to the first sub-station, where the second feedback information is used to indicate that the first data has been received.

[0162] Optionally, the first information is also used to instruct the second sub-management site not to acquire the collected data in the first time slot.

[0163] Optionally, the transceiver unit 1101 is further used to: receive second information from the management site, the second information is used to instruct the third sub-management site to obtain collected data in a second time slot, the second time slot is earlier than the first time slot; and forward the second information to the third sub-management site.

[0164] Optionally, the management site is a central coordinator CCO, the sub-management site is a proxy coordinator PCO, and the sub-site is a PCO or a site STA.

[0165] Optionally, the management site, the sub-management site and the sub-site support Orthogonal Frequency Division Multiple Access OFDMA technology.

[0166] Alternatively, the communication device 1100 may be applied to a first sub-site, wherein:

[0167] The transceiver unit 1101 is used to receive a first scheduling message, where the first scheduling message is used to instruct to report the collected data in a first time slot;

[0168] The transceiver unit 1101 is further configured to report first data to the first sub-management site in a first time slot.

[0169] Optionally, reporting the first data to the first sub-management site includes: reporting the first data to the first sub-management site through a first message, wherein the first message also includes second data reported by the third sub-site.

[0170] Optionally, the transceiver unit 1101 may be deployed in a unit or module capable of implementing information transceiver functions, such as a transceiver, a transceiver antenna, an input / output interface, etc. The communication device 1100 may further include a processing unit 1102, which may be or may be deployed in a processor.

[0171] like Figure 6 As shown, Figure 6 FIG. 1 is a schematic diagram showing the hardware structure of a communication device 1300 in an embodiment of the present application. The structure of the communication device 1100 can be referred to Figure 6 The communication device 1300 includes: a processor 111 and a transceiver 112, wherein the processor 111 and the transceiver 112 are electrically coupled;

[0172] The processor 111 is configured to execute part or all of the computer program instructions in the memory. When the part or all of the computer program instructions are executed, the device executes the method described in any one of the above embodiments.

[0173] The transceiver 112 is used to communicate with other devices; for example, the central coordinator CCO sends first information, and the first information is used to instruct multiple sites to report collected data in a first time slot, and the multiple sites include the first site.

[0174] Optionally, a memory 113 is also included for storing computer program instructions. Optionally, the memory 113 (memory #1) is located within the device, the memory 113 (memory #2) is integrated with the processor 111, or the memory 113 (memory #3) is located outside the device.

[0175] It should be understood that Figure 6 The communication device 1300 shown may be a chip or a circuit. For example, a chip or a circuit may be provided in a terminal device or a communication device. The transceiver 112 may also be a communication interface. The transceiver includes a receiver and a transmitter. Furthermore, the communication device 1300 may also include a bus system.

[0176] Among them, the processor 111, the memory 113, and the transceiver 112 are connected through a bus system, and the processor 111 is used to execute the instructions stored in the memory 113 to control the transceiver to receive signals and send signals, and complete the steps of the transmitting end or the receiving end in the implementation method involved in this application. The memory 113 can be integrated in the processor 111, or it can be set separately from the processor 111.

[0177] As an implementation method, the function of the transceiver 112 can be considered to be implemented by a transceiver circuit or a dedicated transceiver chip. The processor 111 can be considered to be implemented by a dedicated processing chip, a processing circuit, a processor or a general chip. The processor can be a central processing unit (CPU), a network processor (NP) or a combination of a CPU and an NP. The processor can further include a hardware chip or other general processors. The above-mentioned hardware chip can be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) and other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. or any combination thereof. The general processor can be a microprocessor or the processor can also be any conventional processor, etc.

[0178] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus random access memory (DR RAM). It should be noted that the memory described in this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0179] An embodiment of the present application provides a computer storage medium storing a computer program, wherein the computer program includes a method for executing the method corresponding to the first device or the second device in the above embodiment.

[0180] An embodiment of the present application provides a computer program product including instructions, which, when executed on a computer, enables the computer to execute the method in the above embodiment corresponding to the first device or the second device.

[0181] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0182] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0183] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0184] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as 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 devices or units, which can be electrical, mechanical or other forms.

[0185] 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 of this embodiment.

[0186] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0187] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0188] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A data collection method, It is characterized in that Applied to the first sub-management site, the method includes: Receiving first information from a management site, the first information is used to instruct multiple sub-management sites to acquire collected data in a first time slot, the multiple sub-management sites including a first sub-management site; A first scheduling message is sent, where the first scheduling message is used to instruct at least one sub-station to report collected data in the first time slot.

2. The method according to claim 1, It is characterized in that The at least one sub-site includes a first sub-site, and the method further includes: receiving first data reported by the first sub-site in the first time slot.

3. The method according to claim 1 or 2, It is characterized in that The at least one sub-site includes a second sub-site, and the method further includes: receiving first feedback information reported by the second sub-site in the first time slot, wherein the first feedback information does not include the collected data.

4. The method according to claim 2, It is characterized in that After receiving the first data reported by the first sub-station in the first time slot, the method further includes: Second feedback information is sent to the first sub-station, where the second feedback information is used to indicate that the first data has been received.

5. The method according to any one of claims 1 to 4, It is characterized in that The first information is also used to instruct the second sub-management site not to acquire collected data within the first time slot.

6. The method according to any one of claims 1 to 5, It is characterized in that The method further comprises: receiving second information from the management site, where the second information is used to instruct the third sub-management site to acquire collected data in a second time slot, where the second time slot is earlier than the first time slot; The second information is forwarded to the third sub-management site.

7. The method according to any one of claims 1 to 6, It is characterized in that The management site is a central coordinator CCO, the sub-management site is a proxy coordinator PCO, and the sub-site is a PCO or a site STA.

8. The method according to any one of claims 1 to 7, It is characterized in that The management site, the sub-management site and the sub-site support Orthogonal Frequency Division Multiple Access (OFDMA) technology.

9. A data collection method, It is characterized in that Applied to the first subsite, the method includes: receiving a first scheduling message, wherein the first scheduling message is used to instruct to report collected data in a first time slot; Report first data to the first sub-management site within the first time slot.

10. The method according to claim 9, It is characterized in that The reporting the first data to the first sub-management site includes: The first data is reported to the first sub-management site through a first message, and the first message also includes the second data reported by the third sub-site.

11. A data acquisition device, It is characterized in that Applied to the first sub-management site, the device comprises: a transceiver unit, configured to receive first information from a management site, wherein the first information is used to instruct a plurality of sub-management sites to acquire collected data in a first time slot, wherein the plurality of sub-management sites include the first sub-management site; The transceiver unit is further used to send a first scheduling message, where the first scheduling message is used to instruct at least one sub-station to report collected data within the first time slot.

12. The device according to claim 11, It is characterized in that The at least one sub-site includes a first sub-site, and the transceiver unit is further used to: receive first data reported by the first sub-site in the first time slot.

13. The device according to claim 11 or 12, It is characterized in that The at least one sub-site includes a second sub-site, and the transceiver unit is further used to: receive first feedback information reported by the second sub-site in the first time slot, wherein the first feedback information does not include the collected data.

14. The device according to any one of claims 11 to 13, It is characterized in that After receiving the first data reported by the first sub-station in the first time slot, the transceiver unit is further used to: Second feedback information is sent to the first sub-station, where the second feedback information is used to indicate that the first data has been received.

15. The device according to any one of claims 11 to 14, It is characterized in that The first information is also used to instruct the second sub-management site not to acquire collected data within the first time slot.

16. The device according to any one of claims 11 to 15, It is characterized in that The transceiver unit is also used for: receiving second information from the management site, where the second information is used to instruct the third sub-management site to acquire collected data in a second time slot, where the second time slot is earlier than the first time slot; The second information is forwarded to the third sub-management site.

17. The device according to any one of claims 11 to 16, It is characterized in that The management site is a central coordinator CCO, the sub-management site is a proxy coordinator PCO, and the sub-site is a PCO or a site STA.

18. The device according to any one of claims 11 to 17, It is characterized in that The management site, the sub-management site and the sub-site support Orthogonal Frequency Division Multiple Access (OFDMA) technology.

19. A data acquisition device, It is characterized in that Applied to the first sub-site, the device includes: receiving a first scheduling message, wherein the first scheduling message is used to instruct to report collected data in a first time slot; Report first data to the first sub-management site within the first time slot.

20. The device according to claim 19, It is characterized in that The reporting the first data to the first sub-management site includes: The first data is reported to the first sub-management site through a first message, and the first message also includes the second data reported by the third sub-site.

21. A communication device, It is characterized in that The method comprises a processor configured to execute the method according to any one of claims 1 to 8, or configured to execute the method according to any one of claims 9 to 10.

22. A computer-readable storage medium, It is characterized in that The computer-readable storage medium comprises instructions, which, when executed, enable the method according to any one of claims 1 to 8 to be implemented, or enable the method according to any one of claims 9 to 10 to be implemented.

23. A computer program product, It is characterized in that The computer program product comprises instructions, which, when executed, enable the method according to any one of claims 1 to 8 to be implemented, or enable the method according to any one of claims 9 to 10 to be implemented.

Images