CN114513378B - Local scene linkage gateway realization method and device based on slicing - Google Patents
Local scene linkage gateway realization method and device based on slicing Download PDFInfo
- Publication number
- CN114513378B CN114513378B CN202111665008.6A CN202111665008A CN114513378B CN 114513378 B CN114513378 B CN 114513378B CN 202111665008 A CN202111665008 A CN 202111665008A CN 114513378 B CN114513378 B CN 114513378B
- Authority
- CN
- China
- Prior art keywords
- linkage
- scene
- gateway
- data
- trigger source
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 63
- QVFWZNCVPCJQOP-UHFFFAOYSA-N chloralodol Chemical compound CC(O)(C)CC(C)OC(O)C(Cl)(Cl)Cl QVFWZNCVPCJQOP-UHFFFAOYSA-N 0.000 claims abstract description 35
- 230000003993 interaction Effects 0.000 claims abstract description 29
- 230000001960 triggered effect Effects 0.000 claims abstract description 21
- 238000012795 verification Methods 0.000 claims abstract description 19
- 230000003068 static effect Effects 0.000 claims abstract description 9
- 230000010365 information processing Effects 0.000 claims description 31
- 238000012545 processing Methods 0.000 claims description 27
- 230000005540 biological transmission Effects 0.000 claims description 23
- 238000012217 deletion Methods 0.000 claims description 18
- 230000037430 deletion Effects 0.000 claims description 18
- 230000008569 process Effects 0.000 claims description 16
- 230000004044 response Effects 0.000 claims description 14
- 230000009471 action Effects 0.000 claims description 9
- 230000003111 delayed effect Effects 0.000 claims description 8
- 230000006870 function Effects 0.000 claims description 8
- 230000004048 modification Effects 0.000 claims description 6
- 238000012986 modification Methods 0.000 claims description 6
- 230000001360 synchronised effect Effects 0.000 claims description 6
- 238000004891 communication Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000011144 upstream manufacturing Methods 0.000 description 3
- 239000002699 waste material Substances 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 230000003252 repetitive effect Effects 0.000 description 2
- 101150098958 CMD1 gene Proteins 0.000 description 1
- 101100382321 Caenorhabditis elegans cal-1 gene Proteins 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000004321 preservation Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L12/2807—Exchanging configuration information on appliance services in a home automation network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
Abstract
The invention discloses a method and a device for realizing a local scene linkage gateway based on slice type, wherein the method comprises the following steps: when the gateway receives the uplink data of the terminal through the LoRa, triggering and inquiring a local scene and a linkage trigger source list, inquiring if new trigger source information exists, extracting parent class and related information in the trigger source into a temporary trigger source queue, correcting the uplink data of the terminal into triggered local linkage or scene, and reporting to a server; if the gateway inquires the temporary queue of the trigger source and has data, extracting a cmd instruction for verification, and if the verification is successful, merging the packed data into a terminal queue for downlink, and waiting for local linkage interaction; the gateway supports the server to acquire or delete local scene linkage or scene interaction. The device comprises a main control unit, a static memory connected with the main control unit, an external expansion FLASH module, an Ethernet module and a LoRa module. The invention can realize the local scene and linkage of the intelligent home gateway.
Description
Technical Field
The invention relates to the field of intelligent home, in particular to a method and a device for realizing a local scene linkage gateway based on a slice type.
Background
The existing part of intelligent home gateways do not support local scenes and linkage, the scenes and the linkage are transmitted through a cloud end server, so that if the network is disconnected, namely the gateways and the server cannot communicate, the scenes and the linkage can fail, and the intelligent home is not intelligent.
Other gateways supporting local scenes and linkage have high requirements on storage and operation of hardware RAM or SRAM, and waste of storage space is caused due to inconsistent sizes of each scene and linkage, so that market competitiveness of the intelligent home gateway is not facilitated.
The existing LoRaWAN gateway only carries out transparent transmission on data, network support is needed, and the link of the LoRaWAN gateway system is long, so that the LoRaWAN gateway is not suitable for being applied to intelligent home products if introduced directly.
Disclosure of Invention
In view of the above problems, the present invention aims to provide a method and a device for implementing a local scene linkage gateway based on slicing, which implement local scene and linkage of an intelligent home gateway, solve the problem that no network exists, and enable a localized key scene to be effective for old, so that the intelligent home is not limited by the network.
The invention provides a local scene linkage gateway realization method based on a slice type, which comprises the following steps:
Triggering matching and enqueuing: when the gateway receives the uplink data of the terminal through the LoRa, the gateway can trigger and inquire a local scene and a linkage trigger source list, inquire whether new trigger source information exists, if so, the parent class in the trigger source is extracted into a trigger source temporary queue, and the uplink data of the terminal is corrected to be triggered to the local linkage or scene (used for distinguishing whether the command needs a server to trigger the linkage or scene) and then is reported to the server;
instruction information processing: the gateway inquires whether the temporary queue of the triggering source has data, if so, the gateway indicates that the corresponding local scene or linkage needs to be triggered; extracting a cmd instruction for verification, correcting the sequence number of the data packet after the cmd instruction is successfully verified, merging the packed data into a queue of a terminal, and waiting for local linkage or scene interaction;
local linkage or scene interaction: whether the gateway is networked or not, the gateway performs data control interaction with the terminal according to the data descending to the terminal queue; if the gateway is networked at this time, all the uplink data of the terminals in the interaction process are synchronized to the server.
Local linkage and deletion, modification and acquisition of scenes: after the gateway is networked, a request for acquiring a local scene and linkage is initiated to a server, and the server splits a parent scene or parent linkage into a plurality of sub scenes or sub linkages according to the byte size of each scene and linkage and predetermined rules and transmits the sub scenes or sub linkages to the gateway;
The gateway judges whether the transmission is repeated or not according to a scene and linkage triggering source storage table, a scene and linkage normal execution information storage table, a scene and linkage delay execution information table, a downlink equipment list information storage table and a scene and linkage CMD command storage table, and if the transmission is new, the transmission is stored in the corresponding positions in the five tables; until the server pushes all sub-scenes and sub-links;
meanwhile, when the server finds that the scene is updated, the gateway is informed to delete the corresponding sub-scene, after receiving the response of the completion of the deletion of the gateway, the corresponding sub-scene is issued to the gateway to update the sub-scene;
similarly, when the server finds that linkage update exists, the gateway is informed to delete the corresponding sub-linkage, after receiving the response of the completion of the gateway deletion, the corresponding sub-linkage is issued to the gateway to update the sub-linkage.
In this scheme, trigger matching and enqueuing specifically are:
the gateway checks the LoRa received data, if the received data, the local scene and the linked trigger source list are inquired, whether the data equipment ID is the trigger source ID is compared, if not, the data equipment ID is reported to the server, if yes, whether the data equipment ID is the trigger action is judged, if not, the data equipment ID is reported to the server, if yes, the data equipment ID is returned to the triggered scene or the linked parent class and other information;
And then modifying the frame head and frame tail fields of the trigger command, modifying all uplink serial numbers which are the same as the trigger source ID, returning information to enqueue the trigger source temporary queue, and reporting to the server.
In this scheme, instruction information processing specifically includes:
the gateway inquires whether the temporary queue of the trigger source has data or not;
inquiring all subclasses of which the field parent class is the same as the field parent class in the trigger source temporary queue in the execution information table according to the field parent class in the trigger source temporary queue, and extracting cmd storage position location, cmd instruction number cmd_num and cmd instruction total length corresponding to the corresponding subclasses;
judging whether the cmd instruction is delayed to descend, if so, carrying out delay processing, and returning to inquire whether the temporary queue of the receiving trigger source has data again; if not, different cmd instructions are respectively intercepted according to the data protocol format, verification processing is respectively carried out, and if the verification is successful, the packed data are merged into a queue and are sent down to a terminal queue, and the downlink processing is waited. If the delay flag in the trigger source is set, the delay time delay of the corresponding instruction is also required to be extracted, and the data is enqueued in delay instruction information processing. Delaying other processes is consistent with normal processes.
In this scheme, delay instruction information processing specifically is:
and triggering one inquiry after each time of delay for 1s, inquiring whether the delay time in the delay array is 0 if the delay cmd instruction exists, re-inquiring if the delay time is 0, subtracting 1s from the delay time of the cmd instruction with the delay requirement in the delay array if the delay time is not 0, re-inquiring if the delay time of the cmd is not 0 at the moment, indicating that the instruction needs to be downlink at the moment if the delay time of the cmd is 0, taking out the corresponding cmd instruction in the array, queuing the packaged data into a downlink terminal queue, and delivering downlink program processing.
The invention provides a local scene linkage gateway realization device based on a slice type, which comprises a main control unit, a static memory, an external expansion FLASH module, an Ethernet module and a LoRa module, wherein the static memory, the external expansion FLASH module, the Ethernet module and the LoRa module are connected with the main control unit;
the main control unit is connected with the server through the Ethernet module and communicated with the terminal through the LoRa module;
the main control unit controls the device;
and the FLASH module realizes code storage, local linkage and scene storage. .
In this scheme, the FLASH module of expanding has five tables to store, is respectively:
A scene and linkage trigger source storage table, a scene and linkage normal execution information storage table, a scene and linkage delay execution information table, a downlink equipment list information storage table, and a scene and linkage CMD command storage table;
the scene and linkage trigger source storage table is used for storing the scene or linkage trigger source and the information corresponding to the trigger source; the method is used for comparing the received data and extracting corresponding information; corresponding to the scene and the linkage normal execution information storage table;
the scene and linkage normal execution information storage table stores the position information location, the instruction quantity cmd_num and the total length of each sub-class stored in the FLASH module; the intermediaries are used for scene and linkage trigger source storage tables and scene and linkage CMD command storage table storage tables;
the scene and linkage delay execution information storage table has the same functions as the scene and linkage normal execution information storage table, and one more field delay time delay is used for scenes and linkages with requirements on delay processing;
the downlink equipment list information storage table stores an equipment list of a downlink terminal, and is used for distinguishing whether single fire equipment or zero fire equipment and a multicast instruction according to a field type and notifying a downlink Cheng Cai to take different downlink strategies;
The scenario and linkage CMD command storage table stores instructions for the scenario or linkage for all subclasses.
In this scheme, the model of the main control chip of main control unit is: STM32H750ZBT6; the model of the LoRa chip of the LoRa module is ZM470SX-M; the type of the memory chip of the static memory is as follows: CY62157EV30LL-45ZSXI; the model of the external expansion chip of the external expansion FLASH module is as follows: W25Q128 ffsg; the main chip model of the Ethernet is as follows: LAN8720A.
In this scheme, the device can implement the following method:
triggering matching and enqueuing: when the gateway receives the uplink data of the terminal through the LoRa, the gateway can trigger and inquire a local scene and a linkage trigger source list, inquire whether new trigger source information exists, if so, the parent class in the trigger source is extracted into a trigger source temporary queue, and the uplink data of the terminal is corrected to be triggered to the local linkage or scene (used for distinguishing whether the command needs a server to trigger the linkage or scene) and then is reported to the server;
instruction information processing: the gateway inquires whether the temporary queue of the triggering source has data, if so, the gateway indicates that the corresponding local scene or linkage needs to be triggered; extracting a cmd instruction for verification, correcting the sequence number of the data packet after the cmd instruction is successfully verified, merging the packed data into a queue of a terminal, and waiting for local linkage or scene interaction;
Local linkage or scene interaction: whether the gateway is networked or not, the gateway performs data control interaction with the terminal according to the data descending to the terminal queue; if the gateway is networked at this time, all the uplink data of the terminals in the interaction process are synchronized to the server.
Local linkage and deletion, modification and acquisition of scenes: after the gateway is networked, a request for acquiring a local scene and linkage is initiated to a server, and the server splits a parent scene or parent linkage into a plurality of sub scenes or sub linkages according to the byte size of each scene and linkage and predetermined rules and transmits the sub scenes or sub linkages to the gateway;
the gateway judges whether the transmission is repeated or not according to a scene and linkage triggering source storage table, a scene and linkage normal execution information storage table, a scene and linkage delay execution information table, a downlink equipment list information storage table and a scene and linkage CMD command storage table, and if the transmission is new, the transmission is stored in the corresponding positions in the five tables; until the server pushes all sub-scenes and sub-links;
meanwhile, when the server finds that the scene is updated, the gateway is informed to delete the corresponding sub-scene, after receiving the response of the completion of the deletion of the gateway, the corresponding sub-scene is issued to the gateway to update the sub-scene;
Similarly, when the server finds that linkage update exists, the gateway is informed to delete the corresponding sub-linkage, after receiving the response of the completion of the gateway deletion, the corresponding sub-linkage is issued to the gateway to update the sub-linkage.
In this scheme, trigger matching and enqueuing specifically are:
the gateway checks the LoRa received data, if the received data, the local scene and the linked trigger source list are inquired, whether the data equipment ID is the trigger source ID is compared, if not, the data equipment ID is reported to the server, if yes, whether the data equipment ID is the trigger action is judged, if not, the data equipment ID is reported to the server, if yes, the data equipment ID is returned to the triggered scene or the linked parent class and other information;
then, modifying the frame head and frame tail fields of the trigger command, modifying all uplink serial numbers which are the same as the trigger source ID, returning information to enqueue the trigger source temporary queue, and reporting to a server;
the instruction information processing specifically comprises the following steps:
the gateway inquires whether the temporary queue of the trigger source has data or not;
inquiring all subclasses of which the field parent class is the same as the field parent class in the trigger source temporary queue in the execution information table according to the field parent class in the trigger source temporary queue, and extracting cmd storage position location, cmd instruction number cmd_num and cmd instruction total length corresponding to the corresponding subclasses;
Judging whether the cmd instruction is delayed to descend, if so, carrying out delay processing, and returning to inquire whether the temporary queue of the receiving trigger source has data again; if not, different cmd instructions are respectively intercepted according to the data protocol format, verification processing is respectively carried out, and if the verification is successful, the packed data are merged into a queue and are sent down to a terminal queue, and the downlink processing is waited. If the delay flag in the trigger source is set, the delay time delay of the corresponding instruction is also required to be extracted, and the data is enqueued in delay instruction information processing. Delaying other processes is consistent with normal processes.
In this scheme, delay instruction information processing specifically is:
and triggering one inquiry after each time of delay for 1s, inquiring whether the delay time in the delay array is 0 if the delay cmd instruction exists, re-inquiring if the delay time is 0, subtracting 1s from the delay time of the cmd instruction with the delay requirement in the delay array if the delay time is not 0, re-inquiring if the delay time of the cmd is not 0 at the moment, indicating that the instruction needs to be downlink at the moment if the delay time of the cmd is 0, taking out the corresponding cmd instruction in the array, queuing the packaged data into a downlink terminal queue, and delivering downlink program processing.
The invention discloses a method and a device for realizing a local scene linkage gateway based on a slice type, wherein the method realizes the local scene and linkage of an intelligent home gateway, solves the problem that a network does not exist, and ensures that a localized key pressing scene is old and effective, so that the intelligent home is not limited by the network.
According to the method, the scene and the linkage are subjected to slicing processing, one parent scene or parent linkage can be sliced into sub-scenes or sub-linkages with response lengths, so that all sub-scenes and sub-linkages cannot be excessively long in bytes, space waste is caused, and the requirements of local scenes and linkage on hardware are reduced. The market competitiveness and the practicability of the intelligent gateway are enhanced.
The device corrects the LoRaWAN, and the disadvantages of the LoRaWAN are not limited in transmission speed, namely, the disadvantages are converted into advantages. Meanwhile, the requirements of long-distance transmission and full house coverage can be met.
The local scene and linkage of the method can independently distinguish whether the controlled equipment is powered by single fire or zero fire and whether a multicast mode is adopted, and different communication modes are executed according to the characteristics of the terminal.
According to the method, through field processing, a local scene and a linked trigger source can be reported to a server and are different from other trigger sources, so that the method is a root source of terminal equipment control and is plastic.
The method uses a multi-table storage mode, so that the gateway has higher efficiency in executing.
The method has a serial number identification function, and can identify whether to filter the retransmission data. Local scene and linkage repetitive motion due to retransmission is prevented.
The method supports delay instruction operation in a local scene and a linkage instruction.
The method supports the update of local sub-scenes and sub-links of the gateway at any time when the gateway is connected, and synchronizes the sub-scenes and the sub-links into the latest sub-scenes and sub-links under the condition of the network.
Drawings
FIG. 1 shows a flow chart of a method for implementing a slice-based local scene linkage gateway of the present application;
FIG. 2 illustrates a trigger matching and enqueuing flow chart in accordance with the present application;
fig. 3 shows a normal instruction information processing flowchart according to the present application.
Fig. 4 shows a delay instruction information processing flow according to the present application.
Fig. 5 shows a block diagram of a slice-based local scene linkage gateway implementation device of the present application.
Fig. 6 shows a schematic diagram of correspondence of five large tables according to the present application.
Fig. 7 shows a flow chart of the coordinated interaction of the present application.
Detailed Description
So that the manner in which the above recited objects, features and advantages of the present application can be understood in detail, a more particular description of the application, briefly summarized below, may be had by reference to the appended drawings. It should be noted that, without conflict, the embodiments of the present application and features in the embodiments may be combined with each other.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application, however, the present application may be practiced in other ways than those described herein, and therefore the scope of the present application is not limited to the specific embodiments disclosed below.
Fig. 1 shows a flow chart of a method for implementing a slice-based local scene linkage gateway according to the present application.
As shown in fig. 1, the application discloses a local scene linkage gateway implementation method based on slice type, which comprises the following steps:
s102: triggering matching and enqueuing: when the gateway receives the uplink data of the terminal through the LoRa, the gateway triggers and inquires a local scene and a linkage trigger source list, inquires whether new trigger source information exists, extracts the father class in the trigger source into a trigger source temporary queue if the new trigger source information exists, corrects the uplink data of the terminal into triggered local linkage or scene (used for distinguishing whether the command needs a server to trigger the linkage or scene) and reports the triggered local linkage or scene to the server;
s104: instruction information processing: the gateway inquires whether the temporary queue of the triggering source has data, and if so, the gateway indicates that the corresponding local scene or linkage needs to be triggered; extracting cmd instructions for verification, and merging the packed data into a terminal queue to be downlink after verification success, wherein local linkage or scene interaction is performed;
S106: local linkage or scene interaction: and whether the gateway is networked or not, the gateway performs data control interaction with the terminal according to the data which is downwards transmitted to the terminal queue. If the gateway is networked at this time, all the uplink data of the terminals in the interaction process are synchronized to the server.
Local linkage and deletion, modification and acquisition of scenes: after the gateway is networked, a request for acquiring a local scene and linkage is initiated to a server, and the server splits a parent scene or parent linkage into a plurality of sub scenes or sub linkages according to the byte size of each scene and linkage and predetermined rules and transmits the sub scenes or sub linkages to the gateway;
the gateway judges whether the transmission is repeated or not according to a scene and linkage triggering source storage table, a scene and linkage normal execution information storage table, a scene and linkage delay execution information table, a downlink equipment list information storage table and a scene and linkage CMD command storage table, and if the transmission is new, the transmission is stored in the corresponding positions in the five tables; until the server pushes all sub-scenes and sub-links;
meanwhile, when the server finds that the scene is updated, the gateway is informed to delete the corresponding sub-scene, after receiving the response of the completion of the deletion of the gateway, the corresponding sub-scene is issued to the gateway to update the sub-scene;
Similarly, when the server finds that linkage update exists, the gateway is informed to delete the corresponding sub-linkage, after receiving the response of the completion of the gateway deletion, the corresponding sub-linkage is issued to the gateway to update the sub-linkage.
According to an embodiment of the present invention, as shown in fig. 2, fig. 2 shows a trigger matching and enqueuing flowchart, where the trigger matching and enqueuing is specifically:
the gateway checks the LoRa received data, if the received data, the local scene and the linked trigger source list are inquired, whether the data equipment ID is the trigger source ID is compared, if not, the data equipment ID is reported to the server, if yes, whether the data equipment ID is the trigger action is judged, if not, the data equipment ID is reported to the server, if yes, the data equipment ID is returned to the triggered scene or the linked parent class and other information;
and then modifying the frame head and frame tail fields of the trigger command, modifying all uplink serial numbers which are the same as the trigger source ID, returning information to enqueue the trigger source temporary queue, and reporting to the server.
When the gateway receives the uplink data of the terminal through the LoRa, the gateway triggers the inquiry of the local scene and the linkage trigger source list, and compares the local scene and the linkage trigger source list with the corresponding information of the uplink data. If the upstream device ID is the same, updating all upstream serial numbers of the same ID as the upstream device in the trigger source list, namely source_id. At this time and comparing whether the source and action in the trigger source list are the same. And if the terminal data bit local scene and the linkage trigger source data are the same, indicating the terminal data bit local scene and the linkage trigger source data. At this time, it is also necessary to compare whether the uplink sequence numbers up_old_serial in the trigger source are the same, and the same indicates that the command is a terminal retransmission command, and the trigger information is not entered into the trigger source temporary queue. If the trigger source information is different, the trigger source information is new, and the father class in the trigger source needs to be extracted into a temporary trigger source queue.
According to an embodiment of the present invention, as shown in fig. 3, fig. 3 shows a normal instruction information processing flowchart, and the instruction information processing specifically includes:
the gateway inquires whether the temporary queue of the trigger source has data or not; inquiring all subclasses of which the field parent class is the same as the field parent class in the trigger source temporary queue in the execution information table according to the field parent class in the trigger source temporary queue, and extracting cmd storage position location, cmd instruction number cmd_num and cmd instruction total length corresponding to the corresponding subclasses;
judging whether the cmd instruction is delayed to descend, if so, carrying out delay processing, and returning to inquire whether the temporary queue of the receiving trigger source has data again; if not, different cmd instructions are respectively intercepted according to the data protocol format, verification processing is respectively carried out, and if the verification is successful, the packed data are merged into a queue and are sent down to a terminal queue, and the downlink processing is waited. If the delay flag in the trigger source is set, the delay time delay of the corresponding instruction is also required to be extracted, and the data is enqueued in delay instruction information processing. Delaying other processes is consistent with normal processes.
It should be noted that the thread is always querying whether the trigger source temporary queue has data. If there is data indicating that the corresponding local scene or linkage needs to be triggered. Inquiring all the sub-classes son of which the fields father are the same as the fields father in the trigger source temporary queue in the execution information table according to the fields father in the trigger source temporary queue, extracting cmd storage positions location, cmd instruction number cmd_num and cmd instruction total length corresponding to the corresponding sub-classes son, extracting cmd according to the storage information, respectively performing verification processing, merging packed data into a terminal queue to be downlink after verification success, and waiting for downlink stroke processing. If the delay flag in the trigger source is set, the delay time delay of the corresponding instruction is also required to be extracted, and the data is enqueued in delay instruction information processing. Delaying other processes is consistent with normal processes.
According to an embodiment of the present application, as shown in fig. 4, fig. 4 shows a delay instruction information processing flow, where the delay instruction information processing specifically includes:
and triggering one inquiry after each time of delay for 1s, inquiring whether the delay time in the delay array is 0 if the delay cmd instruction exists, re-inquiring if the delay time is 0, subtracting 1s from the delay time of the cmd instruction with the delay requirement in the delay array if the delay time is not 0, re-inquiring if the delay time of the cmd is not 0 at the moment, indicating that the instruction needs to be downlink at the moment if the delay time of the cmd is 0, taking out the corresponding cmd instruction in the array, queuing the packaged data into a downlink terminal queue, and delivering downlink program processing.
Fig. 5 shows a block diagram of a slice-based local scene linkage gateway implementation device of the present application.
As shown in fig. 5, the application discloses a local scene linkage gateway implementation device based on a slice, wherein the local scene linkage gateway implementation device 5 based on the slice comprises a main control unit 51, a static memory 52, an external expansion FLASH module 53, an ethernet module 54 and a LoRa module 55 which are connected with the main control unit 51;
the main control unit 51 is in communication with a server through the Ethernet module 54 and is in communication with a terminal through the LoRa module 55;
The main control unit 51 controls and realizes the control of the local scene linkage gateway realizing device 5 based on the slice type;
the FLASH module 53 realizes code storage, local linkage and scene preservation. .
According to the embodiment of the present invention, the FLASH module 53 stores five tables, which are respectively:
the scene and linkage trigger source stores a table, a scene and linkage normal execution information storage table, a scene and linkage delay execution information table, a downlink equipment list information storage table, and a scene and linkage CMD command storage table.
The scene and linkage trigger source storage table is used for storing the scene or linkage trigger source and the information corresponding to the trigger source; the method is used for comparing the received data and extracting corresponding information; corresponding to the scene and the linkage normal execution information storage table.
The scene and linkage normal execution information storage table stores the position information location, the instruction quantity cmd_num and the total length of each sub-class stored in the FLASH module; the intermediary is used for scene and linkage trigger source storage tables and scene and linkage CMD command storage table storage tables.
The scene and linkage delay execution information storage table has the same functions as the scene and linkage normal execution information storage table, and one more field delay time delay is used for scenes and linkages with requirements on delay processing.
The downlink equipment list information storage table stores an equipment list of a downlink terminal, and can distinguish whether single fire equipment or zero fire equipment and a multicast instruction according to field type, so that different downlink strategies can be notified to downlink courses.
The scenario and linkage CMD command storage table stores instructions for the scenario or linkage for all subclasses.
(1) The scene and linkage trigger source store tables are shown in table 1.
Table 1 scenario and linked trigger Source storage Table
Field description:
source_id: triggering a source address;
source: triggering source;
action: triggering actions;
father: a parent class;
up_old_serial: the uplink old serial number is used for comparing whether the command is repeated or not;
delay_type: the data is stored in the delayed or non-delayed region. 0x01: only in the non-delay region; 0x02: only in the delay region; 0x03: both regions are present.
The scene and linkage trigger source storage table is used for storing the scene or linkage trigger source and information corresponding to the trigger source. The method is used for comparing the received data and extracting corresponding information. Corresponding to the scene and the linkage normal execution information storage table.
This embodiment takes linkage and scene and requires each to create a table.
(2) The scene and linkage normal execution information storage table is shown in table 2.
Table 2 scenario and linkage normal execution information storage table
| Sequence number | father | son | cmd_num | location | length |
| 1 | …… | …… | …… | …… | …… |
| 2 | …… | …… | …… | …… | …… |
| …… | …… | …… | …… | …… | …… |
Field description:
father: a parent class;
son: a subclass;
cmd_num: the total number of commands for the subclass;
positioning: storing the position serial number;
length: the subclass commands total length.
The scene and linkage normal execution information storage table stores the position information location, the instruction number cmd_num and the total length of each subclass son stored in Flash. The intermediary is used for scene and linkage trigger source storage tables and scene and linkage CMD command storage table storage tables.
This embodiment takes linkage and scene and requires each to create a table.
(3) The scene and linkage delay execution information storage table is shown in table 3.
Table 3 scenario and linkage delay execution information store table
| Sequence number | father | son | cmd_num | location | length | delay |
| 1 | …… | …… | …… | …… | …… | …… |
| 2 | …… | …… | …… | …… | …… | …… |
| …… | …… | …… | …… | …… | …… | …… |
Field description:
father: a parent class;
son: a subclass;
cmd_num: the total number of commands for the subclass;
positioning: storing the position serial number;
length: the total length of the subclass command;
delay: the instruction delays the issue time.
The scene and linkage delay execution information storage table has the same function as the scene and linkage normal execution information storage table, and a field delay time delay is added for scenes and linkage with requirements on delay processing.
Currently taking linkage and scene requires each creating a table.
(4) The downlink device list information storage table is shown in table 4.
Table 4 downlink device list information storage table
| Sequence number | down_id | type | down_old_num |
| 1 | …… | …… | …… |
| 2 | …… | …… | …… |
| …… | …… | …… | …… |
Field description:
down_id: executing the terminal address;
type: the terminal type is performed. 0: zero fire equipment; 1: single fire type equipment; 2: multicasting an instruction;
down_old_num: and the downlink old serial number is used for comparing whether the command is repeated or not.
The downlink equipment list information storage table stores an equipment list of a downlink terminal, and can distinguish whether single fire equipment or zero fire equipment and a multicast instruction according to a field type, so that different downlink strategies can be notified to downlink procedures.
In this embodiment, linkage, scene and voice centering require a table to be created together.
(5) The scenario and linkage CMD command memory tables are shown in table 5.
Table 5 scenario and linkage CMD command storage table
| Sequence number | cmd |
| 1 | …… |
| 2 | …… |
| …… | …… |
Field description:
cmd: subclass scenes or linked instruction stores. Instructions of the scene or linkage of all subclasses are stored.
Taking linkage and scene in this embodiment requires each creation of a table.
The relation among the five large tables is shown in fig. 6, fig. 6 shows a relation diagram corresponding to the five large tables, when the LoRa receives data, the LoRa enters the trigger source table for identification, if the LoRa is an effective trigger source, all parent classes which are the same as the LoRa are searched in the normal execution information table and the field father in the delay execution information table according to the field father in the trigger source table, and whether the execution information table exists in the delay table is judged according to the field delay_type in the trigger source table. And then reading out a downlink sub-scene or linkage to be executed in a cmd command table according to a field cmd_ num, location, length in an execution table, finally identifying a specific command type in a field type in a downlink equipment information list table, updating a field down_old_num, and packaging a corresponding terminal downlink command.
According to the embodiment of the invention, the model of the main control chip of the main control unit is as follows: STM32H750ZBT6; the model of the LoRa chip of the LoRa module is ZM470SX-M; the type of the memory chip of the static memory is as follows: CY62157EV30LL-45ZSXI; the model of the external expansion chip of the external expansion FLASH module is as follows: W25Q128 ffsg; the main chip model of the Ethernet is as follows: LAN8720A.
In this embodiment, STM32H750ZBT6 is used as a main control chip to control the function implementation of the whole device. ZM470SX-M is a LoRa chip, and realizes LoRa communication with a terminal. The LAN8720A is an ethernet implementation chip, and is configured to implement data interaction with a server through an ethernet port. W25Q128FVSG is an outward expansion FLASH, and code storage is realized. The hardware adopted by the implementation method of the device of the embodiment has no high requirement, and the local scene and linkage of the gateway are realized in an economic and reliable mode.
According to the embodiment of the invention, the device can realize the following methods:
triggering matching and enqueuing: when the gateway receives the uplink data of the terminal through the LoRa, the gateway can trigger and inquire a local scene and a linkage trigger source list, inquire whether new trigger source information exists, if so, the parent class in the trigger source is extracted into a trigger source temporary queue, and the uplink data of the terminal is corrected to be triggered to the local linkage or scene (used for distinguishing whether the command needs a server to trigger the linkage or scene) and then is reported to the server;
Instruction information processing: the gateway inquires whether the temporary queue of the triggering source has data, if so, the gateway indicates that the corresponding local scene or linkage needs to be triggered; extracting a cmd instruction for verification, correcting the sequence number of the data packet after the cmd instruction is successfully verified, merging the packed data into a queue of a terminal, and waiting for local linkage or scene interaction;
local linkage or scene interaction: whether the gateway is networked or not, the gateway performs data control interaction with the terminal according to the data descending to the terminal queue; if the gateway is networked at this time, all the uplink data of the terminals in the interaction process are synchronized to the server.
Local linkage and deletion, modification and acquisition of scenes: as shown in fig. 7, fig. 7 shows a flow chart of the coordinated interaction. After the gateway is networked, a request for acquiring a local scene and linkage is initiated to a server, and the server splits a parent scene or parent linkage into a plurality of sub scenes or sub linkages according to the byte size of each scene and linkage and predetermined rules and transmits the sub scenes or sub linkages to the gateway;
the gateway judges whether the transmission is repeated or not according to a scene and linkage triggering source storage table, a scene and linkage normal execution information storage table, a scene and linkage delay execution information table, a downlink equipment list information storage table and a scene and linkage CMD command storage table, and if the transmission is new, the transmission is stored in the corresponding positions in the five tables; until the server pushes all sub-scenes and sub-links;
Meanwhile, when the server finds that the scene is updated, the gateway is informed to delete the corresponding sub-scene, after receiving the response of the completion of the deletion of the gateway, the corresponding sub-scene is issued to the gateway to update the sub-scene;
similarly, when the server finds that linkage update exists, the gateway is informed to delete the corresponding sub-linkage, after receiving the response of the completion of the gateway deletion, the corresponding sub-linkage is issued to the gateway to update the sub-linkage.
In this scheme, trigger matching and enqueuing specifically are:
the gateway checks the LoRa received data, if the received data, the local scene and the linked trigger source list are inquired, whether the data equipment ID is the trigger source ID is compared, if not, the data equipment ID is reported to the server, if yes, whether the data equipment ID is the trigger action is judged, if not, the data equipment ID is reported to the server, if yes, the data equipment ID is returned to the triggered scene or the linked parent class and other information;
then, modifying the frame head and frame tail fields of the trigger command, modifying all uplink serial numbers which are the same as the trigger source ID, returning information to enqueue the trigger source temporary queue, and reporting to a server;
the instruction information processing specifically comprises the following steps:
The gateway inquires whether the temporary queue of the trigger source has data or not;
inquiring all subclasses of which the field parent class is the same as the field parent class in the trigger source temporary queue in the execution information table according to the field parent class in the trigger source temporary queue, and extracting cmd storage position location, cmd instruction number cmd_num and cmd instruction total length corresponding to the corresponding subclasses;
judging whether the cmd instruction is delayed to descend, if so, carrying out delay processing, and returning to inquire whether the temporary queue of the receiving trigger source has data again; if not, different cmd instructions are respectively intercepted according to the data protocol format, verification processing is respectively carried out, and if the verification is successful, the packed data are merged into a queue and are sent down to a terminal queue, and the downlink processing is waited. If the delay flag in the trigger source is set, the delay time delay of the corresponding instruction is also required to be extracted, and the data is enqueued in delay instruction information processing. Delaying other processes is consistent with normal processes.
According to the embodiment of the invention, the delay instruction information processing specifically comprises the following steps:
and triggering one inquiry after each time of delay for 1s, inquiring whether the delay time in the delay array is 0 if the delay cmd instruction exists, re-inquiring if the delay time is 0, subtracting 1s from the delay time of the cmd instruction with the delay requirement in the delay array if the delay time is not 0, re-inquiring if the delay time of the cmd is not 0 at the moment, indicating that the instruction needs to be downlink at the moment if the delay time of the cmd is 0, taking out the corresponding cmd instruction in the array, queuing the packaged data into a downlink terminal queue, and delivering downlink program processing.
The invention discloses a method and a device for realizing a local scene linkage gateway based on a slice type, wherein the method realizes the local scene and linkage of an intelligent home gateway, solves the problem that a network does not exist, and ensures that a localized key pressing scene is old and effective, so that the intelligent home is not limited by the network.
According to the method, the scene and the linkage are subjected to slicing processing, one parent scene or parent linkage can be sliced into sub-scenes or sub-linkages with response lengths, so that all sub-scenes and sub-linkages cannot be excessively long in bytes, space waste is caused, and the requirements of local scenes and linkage on hardware are reduced. The market competitiveness and the practicability of the intelligent gateway are enhanced.
The device corrects the LoRaWAN, and the disadvantages of the LoRaWAN are not limited in transmission speed, namely, the disadvantages are converted into advantages. Meanwhile, the requirements of long-distance transmission and full house coverage can be met.
The local scene and linkage of the method can independently distinguish whether the controlled equipment is powered by single fire or zero fire and whether a multicast mode is adopted, and different communication modes are executed according to the characteristics of the terminal.
According to the method, through field processing, a local scene and a linked trigger source can be reported to a server and are different from other trigger sources, so that the method is a root source of terminal equipment control and is plastic.
The method uses a multi-table storage mode, so that the gateway has higher efficiency in executing.
The method has a serial number identification function, and can identify whether to filter the retransmission data. Local scene and linkage repetitive motion due to retransmission is prevented.
The method supports delay instruction operation in a local scene and a linkage instruction.
The method supports the update of local sub-scenes and sub-links of the gateway at any time when the gateway is connected, and synchronizes the sub-scenes and the sub-links into the latest sub-scenes and sub-links under the condition of the network.
In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above described device embodiments are only illustrative, e.g. the division of the units is only one logical function division, and there may be other divisions in practice, such as: multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. In addition, the various components shown or discussed may be coupled or directly coupled or communicatively coupled to each other via some interface, whether indirectly coupled or communicatively coupled to devices or units, whether electrically, mechanically, or otherwise.
The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units; can be located in one place or distributed to a plurality of 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.
In addition, each functional unit in each embodiment of the present invention may be integrated in one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated in one unit; the integrated units can be realized in a form of hardware or a form of hardware plus a form of software functional units.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, where the program when executed performs steps including the above method embodiments; and the aforementioned storage medium includes: a mobile storage device, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk or an optical disk, or the like, which can store program codes.
Alternatively, the above-described integrated units of the present invention may be stored in a computer-readable storage medium if implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, the technical solutions of the embodiments of the present invention may be embodied essentially or in part in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a removable storage device, ROM, RAM, magnetic or optical disk, or other medium capable of storing program code.
Claims (7)
1. The implementation method of the local scene linkage gateway based on the slicing type is characterized by comprising the following steps of:
triggering matching and enqueuing: when the gateway receives the uplink data of the terminal through the LoRa, the gateway can trigger and inquire a local scene and a linkage trigger source list, inquire whether new trigger source information exists, if so, the parent class in the trigger source is extracted into a trigger source temporary queue, and the uplink data of the terminal is corrected to be triggered local linkage or scene and then reported to the server;
Instruction information processing: the gateway inquires whether the temporary queue of the triggering source has data, if so, the gateway indicates that the corresponding local scene or linkage needs to be triggered; extracting a cmd instruction for verification, correcting the sequence number of the data packet after the cmd instruction is successfully verified, merging the packed data into a queue of a terminal, and waiting for local linkage or scene interaction;
local linkage or scene interaction: whether the gateway is networked or not, the gateway performs data control interaction with the terminal according to the data descending to the terminal queue; if the gateway is networked at the moment, all the uplink data of the terminals in the interaction process are synchronized to the server;
local linkage and deletion, modification and acquisition of scenes: after the gateway is networked, a request for acquiring a local scene and linkage is initiated to a server, and the server splits a parent scene or parent linkage into a plurality of sub scenes or sub linkages according to the byte size of each scene and linkage and predetermined rules and transmits the sub scenes or sub linkages to the gateway;
the gateway judges whether the transmission is repeated or not according to a scene and linkage triggering source storage table, a scene and linkage normal execution information storage table, a scene and linkage delay execution information table, a downlink equipment list information storage table and a scene and linkage CMD command storage table, and if the transmission is new, the transmission is stored in the corresponding positions in the five tables; until the server pushes all sub-scenes and sub-links;
Meanwhile, when the server finds that the scene is updated, the gateway is informed to delete the corresponding sub-scene, after receiving the response of the completion of the deletion of the gateway, the corresponding sub-scene is issued to the gateway to update the sub-scene;
similarly, when the server finds that linkage update exists, the gateway is informed to delete the corresponding sub-linkage, after receiving the response of the completion of the gateway deletion, the corresponding sub-linkage is issued to the gateway to update the sub-linkage.
2. The implementation method of the local scene linkage gateway based on the slicing type according to claim 1, wherein the trigger matching and enqueuing are specifically as follows:
the gateway checks the LoRa received data, if the received data, the local scene and the linkage trigger source list are inquired, whether the data equipment ID is the trigger source ID is compared, if not, the data equipment ID is reported to the server, if yes, whether the data equipment ID is the trigger action is judged, if not, the data equipment ID is reported to the server, if yes, the data equipment ID is the trigger source, and if yes, the data equipment ID is returned to the triggered scene or the parent class of the linkage and other information; and then modifying the frame head and frame tail fields of the trigger command, modifying all uplink serial numbers which are the same as the trigger source ID, returning information to enqueue the trigger source temporary queue, and reporting to the server.
3. The implementation method of the slice-based local scene linkage gateway according to claim 1 or 2, wherein the instruction information processing is specifically:
the gateway inquires whether the temporary queue of the trigger source has data or not;
inquiring all subclasses of which the field parent class is the same as the field parent class in the trigger source temporary queue in the execution information table according to the field parent class in the trigger source temporary queue, and extracting cmd storage position location, cmd instruction number cmd_num and cmd instruction total length corresponding to the corresponding subclasses;
judging whether the cmd instruction is delayed to descend, if so, carrying out delay processing, and returning to inquire whether the temporary queue of the receiving trigger source has data again; if not, intercepting different cmd instructions according to the data protocol format, and checking the cmd instructions respectively, and if the cmd instructions are checked successfully, merging the packed data into a terminal queue for downlink processing;
if the delay mark in the trigger source is set, the delay time delay of the corresponding instruction is required to be extracted, and the data is enqueued in the delay instruction information processing to carry out the delay instruction information processing.
4. The implementation method of the local scene linkage gateway based on the slicing type according to claim 3, wherein the delay instruction information processing specifically comprises the following steps:
And if the delay time is not 0, the inquiry is repeated, if the delay time is 0, the corresponding cmd instruction in the array is taken out, and the packed data is enqueued to a downlink terminal queue for downlink program processing.
5. The local scene linkage gateway realization device based on the slicing type is characterized by comprising a main control unit, a static memory, an external expansion FLASH module, an Ethernet module and a LoRa module, wherein the static memory, the external expansion FLASH module, the Ethernet module and the LoRa module are connected with the main control unit;
the main control unit is connected with the server through the Ethernet module and is communicated with the terminal through the LoRa module;
the main control unit controls the device;
the external FLASH module realizes code storage, local linkage and scene storage;
the FLASH module of expanding has five tables to store, is respectively:
a scene and linkage trigger source storage table, a scene and linkage normal execution information storage table, a scene and linkage delay execution information table, a downlink equipment list information storage table, and a scene and linkage CMD command storage table;
The scene and linkage trigger source storage table is used for storing the scene or linkage trigger source and the information corresponding to the trigger source; the method is used for comparing the received data and extracting corresponding information; corresponding to the scene and the linkage normal execution information storage table;
the scene and linkage normal execution information storage table stores the position information location, the instruction quantity cmd_num and the total length of each sub-class stored in the FLASH module; the intermediaries are used for scene and linkage trigger source storage tables and scene and linkage CMD command storage table storage tables;
the scene and linkage delay execution information storage table has the same functions as the scene and linkage normal execution information storage table, and one more field delay time delay is used for scenes and linkages with requirements on delay processing;
the downlink equipment list information storage table stores an equipment list of a downlink terminal, and is used for distinguishing single fire equipment or zero fire equipment and a multicast instruction according to a field type and notifying a downlink path to adopt different downlink strategies;
the scene and linkage CMD command storage table stores the instructions of scenes or linkage of all subclasses;
the model of the main control chip of the main control unit is as follows: STM32H750ZBT6; the model of the LoRa chip of the LoRa module is ZM470SX-M; the type of the memory chip of the static memory is as follows: CY62157EV30LL-45ZSXI; the model of the external expansion chip of the external expansion FLASH module is as follows: W25Q128 ffsg; the main chip model of the Ethernet is as follows: LAN8720A;
The device can realize the following method:
triggering matching and enqueuing: when the gateway receives the uplink data of the terminal through the LoRa, the gateway can trigger and inquire a local scene and a linkage trigger source list, inquire whether new trigger source information exists, if so, the parent class in the trigger source is extracted into a trigger source temporary queue, and the uplink data of the terminal is corrected to be triggered local linkage or scene and then reported to the server;
instruction information processing: the gateway inquires whether the temporary queue of the triggering source has data, if so, the gateway indicates that the corresponding local scene or linkage needs to be triggered; extracting a cmd instruction for verification, correcting the sequence number of the data packet after the cmd instruction is successfully verified, merging the packed data into a queue of a terminal, and waiting for local linkage or scene interaction;
local linkage or scene interaction: whether the gateway is networked or not, the gateway performs data control interaction with the terminal according to the data descending to the terminal queue; if the gateway is networked at the moment, all the uplink data of the terminals in the interaction process are synchronized to the server;
local linkage and deletion, modification and acquisition of scenes: after the gateway is networked, a request for acquiring a local scene and linkage is initiated to a server, and the server splits a parent scene or parent linkage into a plurality of sub scenes or sub linkages according to the byte size of each scene and linkage and predetermined rules and transmits the sub scenes or sub linkages to the gateway;
The gateway judges whether the transmission is repeated or not according to a scene and linkage triggering source storage table, a scene and linkage normal execution information storage table, a scene and linkage delay execution information table, a downlink equipment list information storage table and a scene and linkage CMD command storage table, and if the transmission is new, the transmission is stored in the corresponding positions in the five tables; until the server pushes all sub-scenes and sub-links;
meanwhile, when the server finds that the scene is updated, the gateway is informed to delete the corresponding sub-scene, after receiving the response of the completion of the deletion of the gateway, the corresponding sub-scene is issued to the gateway to update the sub-scene;
similarly, when the server finds that linkage update exists, the gateway is informed to delete the corresponding sub-linkage, after receiving the response of the completion of the gateway deletion, the corresponding sub-linkage is issued to the gateway to update the sub-linkage.
6. The slice-based local scene linkage gateway implementation device according to claim 5, wherein the trigger matching and enqueuing specifically comprises:
the gateway checks the LoRa received data, if the received data, the local scene and the linkage trigger source list are inquired, whether the data equipment ID is the trigger source ID is compared, if not, the data equipment ID is reported to the server, if yes, whether the data equipment ID is the trigger action is judged, if not, the data equipment ID is reported to the server, if yes, the data equipment ID is the trigger source, the data equipment ID is returned to the triggered scene or the parent class of the linkage and related information of the scene or the parent class of the linkage;
Then, modifying the frame head and frame tail fields of the trigger command, modifying all uplink serial numbers which are the same as the trigger source ID, returning information to enqueue the trigger source temporary queue, and reporting to a server;
the instruction information processing specifically comprises the following steps:
the gateway inquires whether the temporary queue of the trigger source has data or not;
inquiring all subclasses of which the field parent class is the same as the field parent class in the trigger source temporary queue in the execution information table according to the field parent class in the trigger source temporary queue, and extracting cmd storage position location, cmd instruction number cmd_num and cmd instruction total length corresponding to the corresponding subclasses;
judging whether the cmd instruction is delayed to descend, if so, carrying out delay processing, and returning to inquire whether the temporary queue of the receiving trigger source has data again; if not, intercepting different cmd instructions according to the data protocol format, and checking the cmd instructions respectively, and if the cmd instructions are checked successfully, merging the packed data into a terminal queue for downlink processing;
if the delay mark in the trigger source is set, the delay time delay of the corresponding instruction is required to be extracted, and the data is enqueued in the delay instruction information processing to carry out the delay instruction information processing.
7. The local scene linkage gateway implementation device based on the slice type according to claim 6, wherein the delay instruction information processing specifically comprises:
and if the delay time is not 0, the inquiry is repeated, if the delay time is 0, the corresponding cmd instruction in the array is taken out, and the packed data is enqueued to a downlink terminal queue for downlink program processing.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111665008.6A CN114513378B (en) | 2021-12-31 | 2021-12-31 | Local scene linkage gateway realization method and device based on slicing |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111665008.6A CN114513378B (en) | 2021-12-31 | 2021-12-31 | Local scene linkage gateway realization method and device based on slicing |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114513378A CN114513378A (en) | 2022-05-17 |
| CN114513378B true CN114513378B (en) | 2023-12-01 |
Family
ID=81547924
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111665008.6A Active CN114513378B (en) | 2021-12-31 | 2021-12-31 | Local scene linkage gateway realization method and device based on slicing |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114513378B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115437268A (en) * | 2022-11-08 | 2022-12-06 | 深圳市海曼科技股份有限公司 | Scene linkage method and device |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107124698A (en) * | 2017-04-28 | 2017-09-01 | 深圳市亿兆互联技术有限公司 | A kind of vertical space positioner based on LoRa technologies, method and system |
| CN107204979A (en) * | 2017-05-25 | 2017-09-26 | 京信通信系统（中国）有限公司 | A kind of information processing method and gateway device |
| CN109639497A (en) * | 2018-12-28 | 2019-04-16 | 万能 | A kind of LoRa gateway |
| CN110100416A (en) * | 2016-12-22 | 2019-08-06 | 华为技术有限公司 | Select the method, apparatus and system of gateway |
| CN110190986A (en) * | 2019-05-07 | 2019-08-30 | 深圳绿米联创科技有限公司 | Method, apparatus, system, electronic equipment and the storage medium of device configuration |
| CN110866713A (en) * | 2019-09-25 | 2020-03-06 | 上海优链供应链管理有限公司 | Logistics system based on LoRa technology and logistics supervision method |
| CN111007814A (en) * | 2019-11-21 | 2020-04-14 | 时拓(嘉兴)智能科技有限公司 | LoRaWAN wireless intelligent home local area network system |
| WO2020192871A1 (en) * | 2019-03-22 | 2020-10-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Network slice configuration |
| WO2020228032A1 (en) * | 2019-05-16 | 2020-11-19 | 深圳市欢太科技有限公司 | Scene pushing method, apparatus and system, and electronic device and storage medium |
| CN113011473A (en) * | 2021-03-02 | 2021-06-22 | 中国工商银行股份有限公司 | Model optimization method, model optimization device and electronic equipment |
| CN113190519A (en) * | 2021-04-23 | 2021-07-30 | 中国铁道科学研究院集团有限公司通信信号研究所 | Driving log compression method based on railway driving scene template |
| CN214045670U (en) * | 2020-12-31 | 2021-08-24 | 泉州睿泽恒创物联网科技有限公司 | Intelligent edge computing gateway |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10613213B2 (en) * | 2016-05-13 | 2020-04-07 | Google Llc | Systems, methods, and devices for utilizing radar with smart devices |
-
2021
- 2021-12-31 CN CN202111665008.6A patent/CN114513378B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110100416A (en) * | 2016-12-22 | 2019-08-06 | 华为技术有限公司 | Select the method, apparatus and system of gateway |
| CN107124698A (en) * | 2017-04-28 | 2017-09-01 | 深圳市亿兆互联技术有限公司 | A kind of vertical space positioner based on LoRa technologies, method and system |
| CN107204979A (en) * | 2017-05-25 | 2017-09-26 | 京信通信系统（中国）有限公司 | A kind of information processing method and gateway device |
| CN109639497A (en) * | 2018-12-28 | 2019-04-16 | 万能 | A kind of LoRa gateway |
| WO2020192871A1 (en) * | 2019-03-22 | 2020-10-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Network slice configuration |
| CN110190986A (en) * | 2019-05-07 | 2019-08-30 | 深圳绿米联创科技有限公司 | Method, apparatus, system, electronic equipment and the storage medium of device configuration |
| WO2020228032A1 (en) * | 2019-05-16 | 2020-11-19 | 深圳市欢太科技有限公司 | Scene pushing method, apparatus and system, and electronic device and storage medium |
| CN110866713A (en) * | 2019-09-25 | 2020-03-06 | 上海优链供应链管理有限公司 | Logistics system based on LoRa technology and logistics supervision method |
| CN111007814A (en) * | 2019-11-21 | 2020-04-14 | 时拓(嘉兴)智能科技有限公司 | LoRaWAN wireless intelligent home local area network system |
| CN214045670U (en) * | 2020-12-31 | 2021-08-24 | 泉州睿泽恒创物联网科技有限公司 | Intelligent edge computing gateway |
| CN113011473A (en) * | 2021-03-02 | 2021-06-22 | 中国工商银行股份有限公司 | Model optimization method, model optimization device and electronic equipment |
| CN113190519A (en) * | 2021-04-23 | 2021-07-30 | 中国铁道科学研究院集团有限公司通信信号研究所 | Driving log compression method based on railway driving scene template |
Non-Patent Citations (4)
| Title |
|---|
| The design and implementation of NAPT function in border gateway based on LKM;Feng Liu;《2016 6th International Conference on Electronics Information and Emergency Communication (ICEIEC)》;全文 * |
| 基于SDN理念的分组域核心网网关设备的优化研究与设计;陈纪好;《中国优秀硕士论文全文数据库》;全文 * |
| 嵌入式物联网智能网关的设计与实现;陈乐庚;洪志鹏;崔更申;;通信技术(第12期);全文 * |
| 面向雾计算的LoRaWAN网关设计与实现;黄亚辉;《中国优秀硕士论文全文数据库》;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114513378A (en) | 2022-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100368998C (en) | Multiple data base data syne method | |
| WO2017067391A1 (en) | Data sharing method and device for virtual machines | |
| CN114513378B (en) | Local scene linkage gateway realization method and device based on slicing | |
| CN103647869B (en) | A kind of matching method of terminal, terminal and system | |
| GB2589211A (en) | Methods and systems of using remote subscriber identification modules at device | |
| CN110807063B (en) | Substation real-time data rapid distribution synchronization system and method based on edge calculation | |
| CN111045806A (en) | Method and system for realizing delay message queue | |
| CN112769939B (en) | Big data reliable transmission method for real-time communication | |
| CN110831168B (en) | Communication method, system, internet of things platform and computer readable storage medium | |
| CN102629944B (en) | Method and device as well as system for network acceleration | |
| CN109688208B (en) | Data loading method based on FC-AE-ASM message | |
| CN112491990B (en) | Hybrid cloud network data transmission method and device, electronic equipment and storage medium | |
| CN110996268A (en) | SIG mesh-based broadcast bearer layer message filtering strategy method | |
| CN113179304B (en) | Message issuing method, system, device and storage medium | |
| CN110912766B (en) | Communication network multi-plane data consistency checking method | |
| CN105939293A (en) | SKB (Struct sk_buff) recycling method and device | |
| CN112565105A (en) | Method, device and equipment for reducing time-sensitive frame forwarding time delay | |
| US7865175B2 (en) | Apparatus, system and method for forwarding data sent to a wireless device to another address | |
| CN113179229A (en) | Verification method, verification device, storage medium and electronic equipment | |
| CN112969198A (en) | Data transmission method, terminal and storage medium | |
| CN109526017B (en) | Distributed small base station upgrading method and system | |
| CN116233148A (en) | Cloud edge data synchronization method, system, device and computer storage medium | |
| CN110708676B (en) | S1 port cluster message processing method, network node and base station | |
| CN111064674B (en) | Data transmission method, device and system | |
| CN113794620A (en) | Message sending method, device, equipment, system and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230106 Address after: 311121 Room 711-3, Building 7, No. 1, Cangxing Street, Cangqian Street, Yuhang District, Hangzhou City, Zhejiang Province Applicant after: Green Carbon Intelligent Building (Hangzhou) Co.,Ltd. Applicant after: Zhejiang Huiju intelligent Internet of things Co.,Ltd. Address before: 310000 room 206, building 15, No. 1818-2, Wenyi West Road, Yuhang street, Yuhang District, Hangzhou City, Zhejiang Province Applicant before: Zhejiang Huiju intelligent Internet of things Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |