CN109067892A - Big data transmission method, terminal and server in a kind of Lora communication system - Google Patents
Big data transmission method, terminal and server in a kind of Lora communication system Download PDFInfo
- Publication number
- CN109067892A CN109067892A CN201810958128.7A CN201810958128A CN109067892A CN 109067892 A CN109067892 A CN 109067892A CN 201810958128 A CN201810958128 A CN 201810958128A CN 109067892 A CN109067892 A CN 109067892A
- Authority
- CN
- China
- Prior art keywords
- fragment
- terminal
- lora
- message
- big data
- 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.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
- H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
-
- 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/104—Peer-to-peer [P2P] networks
- H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
- H04L67/1078—Resource delivery mechanisms
- H04L67/108—Resource delivery mechanisms characterised by resources being split in blocks or fragments
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Big data transmission method, terminal and server in a kind of Lora communication system, in this method, in the upstream direction, big data fragment is regular length by Lora terminal, the short message that Lora communication system can be transmitted, it continuously transmits to server end, after fragment completely receives, server end carries out message reassembly.In the downstream direction, big data fragment is regular length by server end, the short message that Lora communication system can be transmitted, and is transferred to Lora terminal in a continuous manner by SX1301, after terminal is completely received the subpackage from server end, message reassembly is carried out.The present invention is realized transmits big data in Lora communication system, while avoiding generating big interference to the transmission of normal use message.
Description
Technical field
The present invention relates to big data transmission methods, terminal in Lora technical field more particularly to a kind of Lora communication system
And server.
Background technique
LoRaWAN is a set of communications protocol and system architecture for the design of LoRa electric communication network.Lora communication system
System generally comprises terminal, base station, network server, this four parts of application server.Star network is used between base station and terminal
Network topology is able to due to the long range characteristic of LoRa, between them using single-hop transmission.Terminal node can be issued multiple simultaneously
Forward process is then done to the LoRaWAN protocol data between network server and terminal in base station, base station, by LoRaWAN data point
It has not been carried on LoRa radio frequency transmission and TCP/IP.
Terminal in Lora communication system is divided into three classes: Class A, Class B, Class C.The terminal of Class A is adopted
With the on-demand reported data of ALOHA agreement.Two of short duration downlink reception windows can be all closely followed after each uplink, realized with this double
To transmission.This operation is most power saving.The terminal of Class A could issue number to it after having to wait for terminal reported data
According to application scenarios are usually dustbin monitoring, smoke alarm, gas-monitoring etc..For the terminal of Class B, in addition to
The random reception window of Class A, can also at the appointed time open reception window.In order to which terminal can at the appointed time be opened
Window is received, terminal needs the beacon synchronous from gateway receiving time.The terminal of Class B is in terminal fixed reception window
Data are issued to it, the delay issued increases, and application scenarios are usually valve control aqueous vapor ammeter etc..The terminal of Class C
Substantially always on reception window, is only momentarily closed when sending.Shape is persistently received since the terminal of Class C is in
State can issue data to terminal at any time.Its application scenarios is usually Street lamps control etc..The terminal of Class C can compare
Class A and Class B more power consumption.
Fig. 1 and Fig. 2 respectively illustrates the timing diagram of the uplink and downlink of the terminal of Class A and Class C.Class C and
Class A is substantially identical, and only during Class A suspend mode, it, which is all opened, receives window RX2.
Fig. 3 shows the timing diagram of the uplink and downlink of the terminal of Class B.The time slot of Class B is then more complex, it has one
A synchronization time slot beacon, there are one the reception window ping time slots of fixed cycle.As Fig. 3 example in, the beacon period
It is 128 seconds, the ping period is 32 seconds.
LoRaWAN regulation data frame type has Confirmed or two kinds of Unconfirmed, that is, needs response and be not required to
Want acknowledgement type.Manufacturer can need to select suitable type according to application.There are two types of data packet formats by LoRa: showing and hidden
Whether formula mainly comprising byte number, encoding rate and uses the information such as CRC wherein the header of display data packet is shorter.Such as Fig. 4,
LoRa data packet includes: Preamble (lead code), Header (header of optional type), Payload (Data payload).
What is transmitted under the environment of internet of things of the workshop Lora mainly includes the transmission of switching value and quantity of state using data, these
It can be transmitted in Lora communication system by way of short message using data.
But there is also the needs of some big datas transmission, these, since the scale of construction is larger, can not disposably lead to using data
The short message for crossing Lora is transmitted, therefore big data how is transmitted in Lora communication system, and when transmitting big data
It avoids generating big interference to the transmission of normal use message, is a urgent need to solve the problem.
Summary of the invention
In view of the drawbacks of the prior art, the present invention propose big data transmission method in a kind of Lora communication system, terminal and
Server, in this method, in up-downlink direction, transmitting terminal passes big data fragment at short message in Lora communication system
It is defeated, message reassembly is carried out in receiving end, transmits big data in Lora communication system to realize, while avoiding to normally answering
Big interference is generated with the transmission of message.
To achieve the above object, the present invention provides big data transmission method in a kind of Lora communication system, in this method,
In the upstream direction, big data fragment is regular length by Lora terminal, and the short message that Lora communication system can be transmitted connects
It resumes and is defeated by server end, after fragment completely receives, server end carries out message reassembly.In the downstream direction, server end will
Big data fragment is regular length, the short message that Lora communication system can be transmitted, and in a continuous manner by SX1301
It is transferred to Lora terminal, after terminal is completely received the subpackage from server end, carries out message reassembly.
According to another aspect of the present invention, after uplink fragment short message is sent completely, server end is sent out to Lora terminal
Reception confirmation message is sent, wherein carrying the subpackage sequence that server end has been received.
According to another aspect of the present invention, after downlink fragment short message is sent completely, Lora terminal to server end hair
Reception confirmation message is sent, wherein carrying Lora terminal received subpackage sequence.
According to another aspect of the present invention, if packet loss occurs in transmission process, the fragment data of loss is retransmitted, if retransmitting
Receiving end can not receive the fragment data yet after up to pre-determined number, then this big data transmission failure.
It according to another aspect of the present invention, include: using 64 bytes as fragment for regular length using big data fragment
Fixed payload length, by application layer by big data according to fixed payload length fragment at several short messages.
According to another aspect of the present invention, whether each fragment message includes following information: being fragment, have more later
More fragments, fragment deviate ID, application of electronic report type, message identification.
According to another aspect of the present invention, in up direction, the data of transmission are using KB as unit length, in down direction,
The data of transmission are using MB as unit length.
According to another aspect of the present invention, the present invention also provides be used for transmission big data in a kind of Lora communication system
Lora terminal, the Lora terminal includes processor, the processor is configured to the method for executing big data transmission.
According to another aspect of the present invention, the present invention also provides be used for transmission big data in a kind of Lora communication system
Server, the server include processor, the processor is configured to the method for executing big data transmission.
Big data transmission method, terminal and server in Lora communication system provided by the invention, can be realized in Lora
Big data is transmitted in communication system, while avoiding generating big interference to the transmission of normal use message.
By referring to the following drawings and to the detailed description of a specific embodiment of the invention, feature and advantage of the invention
It will become apparent.
Detailed description of the invention
Fig. 1 and Fig. 2 is the timing diagram of the uplink and downlink of the terminal of Class A and Class C in the prior art；
Fig. 3 is the timing diagram of the uplink and downlink of the terminal of Class B in the prior art；
Fig. 4 is the structural schematic diagram of data frame in the prior art；
Fig. 5 is big data transmission method flow diagram in one embodiment of the present of invention；
Fig. 6 is the flow diagram that transmitting terminal and receiving end carry out big data transmission in the present invention.
Specific embodiment
In order to keep technical solution of the present invention clearer, clear, it is described in further detail, should manages below in conjunction with attached drawing
Solution, the specific embodiments described herein are merely illustrative of the present invention, is not intended to limit the present invention.
For convenience, it is also indicated using transmitting terminal other than indicating server end and Lora terminal in the present invention
One of server end and Lora terminal indicate another using receiving end, and even server is transmitting terminal, then Lora terminal is exactly
Receiving end, if Lora terminal is transmitting terminal, server is exactly receiving end.
As shown in figure 5, the present invention provides big data transmission method in a kind of Lora communication system, in this method, upper
On line direction, big data fragment is regular length by Lora terminal, and the short message that Lora communication system can be transmitted is continuous to pass
It is defeated by server end, after fragment completely receives, server end carries out message reassembly.In the downstream direction, server end will count greatly
According to fragment for regular length, the short message that Lora communication system can be transmitted, and transmitted in a continuous manner by SX1301
After giving Lora terminal, terminal to be completely received the subpackage from server end, message reassembly is carried out.
Specifically, big data transmission is realized in the application layer of Lora in principle, and unified interface is provided to upper layer application.
Big data is transmitted in the upstream direction, it is desirable that big data fragment is regular length, Lora platform by terminal device
The short message that can be transmitted, and server end is passed in continuous and as fast as possible mode by Lora terminal module.It can be with
In Lora terminal node, by the way of closing downlink reception window, continuous uplink transmission is carried out.After being sent completely,
It asks server end to carry out reception confirmation, informs the subpackage sequence that transmitting terminal has been received.It, must if packet loss occurs in transmission process
It must be retransmitted by terminal device.If repeatedly retransmitting failure, that is, think the transmission failure of this big data.Fragment completely receives
Afterwards, message reassembly work is completed by server.
Big data is transmitted in down direction, it is desirable that big data fragment is regular length, Lora platform energy by server end
The short message enough transmitted, and Lora terminal node is passed in continuous and as fast as possible mode by SX1301.Wherein, consider
There must be the case where uplink that could receive downlink data, this side for transmitting big message in down direction to Class A equipment
Formula is not suitable for Class A equipment, is more suitable for Class C equipment.It is recommended that the RX2 window using Class C is continuously transmitted.Clothes
Device be engaged in after being sent completely, it is desirable that terminal device carries out reception confirmation, informs transmitting terminal received subpackage sequence.If passed
Occurs packet loss during defeated, it is necessary to be retransmitted by server.If repeatedly retransmitting failure, that is, think that the transmission of this big data is lost
It loses.After terminal device is completely received the subpackage from server, reset.
This system once only carries out the sliced transmission and re-installation effort of a big data in principle.Transmitting terminal must wait first
The fragment that second big data could be sent after the completion of the sliced transmission of a big data and refitting or after time-out, if receiving end
The fragment of two big datas from the same transmitting terminal is received simultaneously, and receiving end should not reset successfully big number for upper one
According to fragment abandon.
1, the regular length of fragment
In order to simplify the fragment and refitting process of big data, need for the length of message fragment to be fixed.This is fixed
Length limited is in LoRa minimum data rate (SF12) and standardizes defined maximum airborne period (5 seconds).
By measuring and calculating, in the case where data rate SF12, one byte of every hair needs 56.8ms.That is most
Big airborne period can at most send 88 bytes in the case where 5 seconds, remove the Lora heading of 13 bytes, and maximum is supported to answer
It is 75 bytes with payload.In order to retain certain surplus, at the same be ensured of 2 multiple, using 64 bytes consolidating as fragment
Fixed payload length (being defined as FragmentLength=64).
2, the format of fragment message
Terminal device passes through Lora application layer for big data according to FragmentLength, and fragment is at several.Each point
Whether piece or non-fragment message should include following information: being fragment, whether there is more fragments later, fragment deviates id, report
Literary application type, message identification.Specific composition is as follows:
Low 5 bit0-bit4 of Byte0 indicate application of electronic report type, indicate the purposes of the data message.Byte0's
Bit5 indicates the whether last fragment of message.The bit6 of Byte0 indicates whether message is fragment.Byte1 indicates message identification, indicates
This be transmitting terminal issued to specific receiving end which using data, be used to one uplink and downlink application number of unique identification
According to.
If message is fragment, next two Byte are fragment offset id.If not fragment, without the two words
Section.Fragment offset indicates serial number of the fragment in entire big data.
The application type of message, which can according to need, to be defined, such as the application type of message can indicate: 1: data；
2: fragment refitting complete or unsuccessfully confirm (issuing fragment transmitting terminal in fragment receiving end), to transmitting terminal confirmation fragment finish receiving or
Person's failure；3: fragment retransmits request (issuing fragment transmitting terminal in fragment receiving end), and request transmitting terminal retransmits specific fragment；4: point
Piece refitting request (fragment transmitting terminal issues fragment receiving end), it is desirable that receiving end resets fragment.
On up direction, terminal node needs a string of display character informations continuously passing to server, needs uplink
Data volume is totally little, considers KB level length；On down direction, server needs online upgrading terminal firmware, needs terminal
Firmware data sliced transmission is reset to terminal device, and on the terminal device.Firmware size is larger, to consider MB grades of data
Measure the demand of transmission.
3, the Slicing procedure of uplink message
Terminal device passes through Lora application layer for big data according to FragmentLength, and (uplink is big at several for fragment
The length of data should consider KB rank), it is then transferred to Lora terminal hardware and is sent.
Assuming that the data of 150 bytes need uplink, data are first divided into 3 short messages by terminal device needs,
It gives Lora terminal hardware to be sent, specific fragment is as follows:
4, the transmission of uplink fragment message Lora terminal hardware
Terminal device by big data fragment at multiple fragments after, fragment data is successively given to Lora terminal hardware SX1276
It is sent.
Lora terminal node receives the data of terminal device delivery, if it find that being fragment.It has to try to fragment is continuous
With quickly send.This is that the software to Lora terminal node is needed to do following setting:
1, IsRxWindowsEnabled mark is closed, Lora terminal node is opened should not in fragment transmission process and connects
Window is received, is continuously transmitted convenient for fragment；
2, the timing of MacStateCheckTimer is shortened simultaneously, message is enable to send as early as possible；
If 3, data are the last one refitting request messages or are not fragments, reopen
IsRxWindowsEnabled mark enables to receive window, while the original timing for restoring MacStateCheckTimer is long
Degree.
5, request message is reset
Transmitting terminal can also continuously transmit 3 refitting request messages after distributing the last one fragment.Receiving end is receiving most
The latter fragment or receive refitting request message after begin to try refitting fragment.
In this method, using 3 refitting request messages of continuous retransmission, rather than 3 the last one fragments of continuous retransmission
Mode starts the refitting of receiving end, is that longer may take a long time because of the last one message, and resetting request message can use up
It may be short.Retransmitting 3 the last one messages may take a long time.
It is as follows to reset request message format:
The meaning of Byte0, Byte1 are identical as the meaning in fragment message format
Byte2-3: indicating current big data transmission, the fragment sum for needing to transmit.
Which wheel refitting request Byte4: being for identifying this, tell duplicate refitting request message for receiving end,
Carry out deduplication operation.
6, the refitting of fragment message
The refitting of upper layer fragment is responsible for by network server NS, and NS is receiving the last one fragment or refitting request message
After start carry out data refitting.
If reset successfully, NS sends fragment refitting to terminal device and completes confirmation message.In order to ensure transmitting terminal can
It receives refitting and completes confirmation message, it is necessary to continuously transmit message 3 times.
If refitting time-out, NS sends fragment to terminal device and resets failure message, while the fragment of preservation being deleted.For
Ensure that transmitting terminal can receive refitting failure message, it is necessary to continuously transmit message 3 times.
Confirmation message format is as follows:
After fragment transmitting terminal receives fragment refitting confirmation (success or failure) message, the fragment message in caching is deleted
It removes, terminates this sliced transmission.
Equally, in down direction, the process that Lora terminal resets short message is docked with server described above
The process that the short message received is reset is similar, and details are not described herein.
7, the retransmission request of fragment message
Network server NS begins to try refitting fragment after receiving the last one fragment.If it find that a large amount of fragments do not have
There is reception, NS sends fragment to terminal device and resets failure message.If it find that wherein there is a small amount of fragment not receive, Ke Yixiang
Terminal device sends fragment and retransmits request message.Request message is retransmitted in order to ensure transmitting terminal can receive fragment, needs to divide
Piece is retransmitted request and is continuously transmitted 3 times.Format is as follows:
Wherein Byte2: expression is that request is retransmitted in which time, is in order to which duplicate removal uses.Terminal device receives fragment re-transmission
After request, the fragment of request repeat is retransmitted again.Fragment also needs continuous 3 repeating transmission fragments refitting request report after the completion of retransmitting
Text.The transmission of these messages all must be continuous, this process and the described repeating transmission of Lora terminal transmission uplink fragment message
Process is similar.
Equally, in down direction, the process of Lora terminal request server re-transmission short message and server described above
The process for requesting Lora terminal to retransmit short message is similar, and details are not described herein.
8, the abnormal timeout treatment mechanism of fragment refitting
Terminal device starts timeout mechanism, the fragment of NS is waited to reset after having sent the last one refitting request message
Confirmation message.If receiving fragment refitting confirmation message message in time-out time, the transmission of this fragment terminates.
If receiving the retransmission request of NS uplink fragment message in time-out time, overtime timer is reset, by request retransmission
After message is sent again, refitting request message is sent again, restarts timeout mechanism.
If time-out does not receive NS fragment refitting confirmation message or fragment refitting request message.Think that this fragment passes
Defeated failure abandons fragment, returns to sliced transmission result and exits this transmission.
NS is also provided with timeout mechanism, when resetting primary time-out after receiving a fragment or refitting request message every time
Between, if failing to complete fragment refitting after overtime a period of time, fragment refitting failure message is issued, then release has been received by point
Piece terminates this refitting.
Wherein, the length of time-out time, it is contemplated that the maximum transmitted duration of 3 transmission fragments, in addition the regular hour
Surplus.
Fig. 6 is the flow diagram that transmitting terminal and receiving end carry out big data transmission in the present invention.Wherein, transmitting terminal can be with
It is server or Lora terminal, correspondingly, receiving end can be Lora terminal or server.
The process that transmitting terminal carries out big data transmission is as follows:
Step 1: big data transmission starts；
Step 2: message carries out fragment with regular length and is carried out continuously transmission；
Step 3: after fragment is sent, then continuously transmitting 3 refitting request messages；
Step 4: starting overtime timer waits the response of receiving end；If time-out receives refitting failure message, hold
Row step 5, it is no to then follow the steps 6；
Step 5: returning to failure, discharge fragment, exit this sliced transmission；
Step 6: the fragment for receiving receiving end retransmits request, and pause timer continuously issues the fragment of request, and continuous
Issue 3 refitting request messages；
Step 7: starting overtime timer waits the response of receiving end；If overtime, step 5 is executed, it is no to then follow the steps
8；
Step 8: receiving and reset successfully confirmation message, Off Timer；
Step 9: release fragment returns successfully, exits this sliced transmission.
The process that receiving end carries out big data transmission is as follows:
Step 1: receiving end receives fragment；
Step 2: starting overtime timer after receiving first fragment, often receive a fragment or refitting request later
Message all resets an overtime timer；When judging whether the timer expires or not, if it is overtime, step 3 is executed, otherwise, executes step
4；
Step 3: continuous 3 transmissions reset failure message, and release fragment exits refitting；
Step 4: receiving the last one fragment or receive refitting request message, pause timeout timer begins trying weight
Dress；And judge whether fragment is lost excessive, and then follow the steps 3, it is no to then follow the steps 5；
Step 5: discovery fragment is lost but is not very much, to the continuous 3 transmissions fragment retransmission request message of transmitting terminal, and to open
Dynamic overtime timer；
Step 6: receiving re-transmission fragment, often receive a fragment or refitting request message all resets primary time-out timing
Device；
Step 7: receiving fragment and save fragment, receive refitting request message, pause timer again attempts to reset；
Step 8: resetting successfully, reset successfully message to continuous 3 transmissions of transmitting terminal；.
Step 9: release fragment returns to data after refitting, exits refitting.
The above description is only a preferred embodiment of the present invention, is not intended to limit the scope of the invention, all at this
Under the design of invention, using equivalent structure transformation made by description of the invention and accompanying drawing content, or directly/it is used in it indirectly
He is included in scope of patent protection of the invention relevant technical field.
Claims (9)
1. big data transmission method in a kind of Lora communication system, which is characterized in that in the upstream direction, Lora terminal will count greatly
It is regular length according to fragment, the short message that Lora communication system can be transmitted is continuously transmitted to server end, and fragment completely connects
After receipts, server end carries out message reassembly.In the downstream direction, big data fragment is regular length, Lora by server end
The short message that communication system can be transmitted, and Lora terminal is transferred to by SX1301 in a continuous manner, terminal completely receives
To after the subpackage of server end, message reassembly is carried out.
2. transmission method according to claim 1, which is characterized in that after uplink fragment short message is sent completely, service
Device end transmits and receives confirmation message to Lora terminal, wherein carrying the subpackage sequence that server end has been received.
3. transmission method according to claim 1, which is characterized in that after downlink fragment short message is sent completely, Lora
Terminal to server end transmits and receives confirmation message, wherein carrying Lora terminal received subpackage sequence.
4. transmission method according to claim 1, which is characterized in that if packet loss occurs in transmission process, retransmit loss
Fragment data, if the fragment data can not received yet by retransmitting up to receiving end after pre-determined number, the transmission of this big data
Failure.
5. transmission method according to claim 1, which is characterized in that by big data fragment be regular length include: use
Payload length of 64 bytes as the fixation of fragment, by application layer by big data according to fixed payload length fragment
At several short messages.
6. transmission method according to claim 1 or 5, which is characterized in that each fragment message includes following information: whether
For fragment, whether there are more fragments later, fragment deviates ID, application of electronic report type, message identification.
7. transmission method according to claim 1, which is characterized in that in up direction, the data of transmission are as unit of KB
Length, in down direction, the data of transmission are using MB as unit length.
8. being used for transmission the Lora terminal of big data in a kind of Lora communication system, which is characterized in that the Lora terminal includes
Processor, the processor is configured to executing such as the big number as performed by the Lora terminal in claim any one of 1-7
According to the method for transmission.
9. being used for transmission the server of big data in a kind of Lora communication system, which is characterized in that the server includes processing
Device, the processor is configured to executing as the big data as performed by the server is transmitted in claim any one of 1-7
Method.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810958128.7A CN109067892A (en) | 2018-08-22 | 2018-08-22 | Big data transmission method, terminal and server in a kind of Lora communication system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810958128.7A CN109067892A (en) | 2018-08-22 | 2018-08-22 | Big data transmission method, terminal and server in a kind of Lora communication system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109067892A true CN109067892A (en) | 2018-12-21 |
Family
ID=64686908
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810958128.7A Pending CN109067892A (en) | 2018-08-22 | 2018-08-22 | Big data transmission method, terminal and server in a kind of Lora communication system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109067892A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109450714A (en) * | 2018-12-28 | 2019-03-08 | 万能 | A kind of LoRa terminal node and its data transmission method |
| CN109526041A (en) * | 2018-12-28 | 2019-03-26 | 万能 | A kind of LoRa terminal node |
| CN109587023A (en) * | 2018-12-28 | 2019-04-05 | 万能 | A kind of LoRa ad hoc network method and system |
| CN109586976A (en) * | 2018-12-28 | 2019-04-05 | 万能 | A kind of LoRa server |
| CN109639497A (en) * | 2018-12-28 | 2019-04-16 | 万能 | A kind of LoRa gateway |
| CN110995956A (en) * | 2019-12-06 | 2020-04-10 | 深圳大学 | Image transmission method and device based on LoRa and computer equipment |
| CN112105008A (en) * | 2020-08-21 | 2020-12-18 | 云南瀚哲科技有限公司 | LoRaWAN gateway node data interaction method based on data unit |
| CN112118085A (en) * | 2020-09-01 | 2020-12-22 | 中国电子科技集团公司第二十八研究所 | Reliable transmission device and method under short wave channel |
| CN114020304A (en) * | 2022-01-06 | 2022-02-08 | 杭州字节信息技术有限公司 | LoRaWan-based OTA implementation method, terminal device and computer storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107612668A (en) * | 2017-09-06 | 2018-01-19 | 深圳天珑无线科技有限公司 | Communication means, device, terminal, server and storage medium based on LoRa |
| CN108111576A (en) * | 2017-12-01 | 2018-06-01 | 中国铁道科学研究院电子计算技术研究所 | A kind of car-ground radio transmission method and device |
| CN108173920A (en) * | 2017-12-22 | 2018-06-15 | 成都博高信息技术股份有限公司 | Document transmission method based on LORAWAN |
| CN108306711A (en) * | 2018-01-02 | 2018-07-20 | 重庆邮电大学 | A kind of data frame based on LoRa quickly continuously transmits method |
-
2018
- 2018-08-22 CN CN201810958128.7A patent/CN109067892A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107612668A (en) * | 2017-09-06 | 2018-01-19 | 深圳天珑无线科技有限公司 | Communication means, device, terminal, server and storage medium based on LoRa |
| CN108111576A (en) * | 2017-12-01 | 2018-06-01 | 中国铁道科学研究院电子计算技术研究所 | A kind of car-ground radio transmission method and device |
| CN108173920A (en) * | 2017-12-22 | 2018-06-15 | 成都博高信息技术股份有限公司 | Document transmission method based on LORAWAN |
| CN108306711A (en) * | 2018-01-02 | 2018-07-20 | 重庆邮电大学 | A kind of data frame based on LoRa quickly continuously transmits method |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109450714A (en) * | 2018-12-28 | 2019-03-08 | 万能 | A kind of LoRa terminal node and its data transmission method |
| CN109526041A (en) * | 2018-12-28 | 2019-03-26 | 万能 | A kind of LoRa terminal node |
| CN109587023A (en) * | 2018-12-28 | 2019-04-05 | 万能 | A kind of LoRa ad hoc network method and system |
| CN109586976A (en) * | 2018-12-28 | 2019-04-05 | 万能 | A kind of LoRa server |
| CN109639497A (en) * | 2018-12-28 | 2019-04-16 | 万能 | A kind of LoRa gateway |
| CN110995956A (en) * | 2019-12-06 | 2020-04-10 | 深圳大学 | Image transmission method and device based on LoRa and computer equipment |
| CN110995956B (en) * | 2019-12-06 | 2021-11-09 | 深圳大学 | Image transmission method and device based on LoRa, computer equipment and storage medium |
| CN112105008A (en) * | 2020-08-21 | 2020-12-18 | 云南瀚哲科技有限公司 | LoRaWAN gateway node data interaction method based on data unit |
| CN112105008B (en) * | 2020-08-21 | 2023-02-17 | 云南瀚哲科技有限公司 | LoRaWAN gateway node data interaction method based on data unit |
| CN112118085A (en) * | 2020-09-01 | 2020-12-22 | 中国电子科技集团公司第二十八研究所 | Reliable transmission device and method under short wave channel |
| CN112118085B (en) * | 2020-09-01 | 2023-03-03 | 中国电子科技集团公司第二十八研究所 | Reliable transmission device and method under short wave channel |
| CN114020304A (en) * | 2022-01-06 | 2022-02-08 | 杭州字节信息技术有限公司 | LoRaWan-based OTA implementation method, terminal device and computer storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109067892A (en) | Big data transmission method, terminal and server in a kind of Lora communication system | |
| WO2020206616A1 (en) | Method and device for retransmitting feedback for direct-connection communication, and storage medium | |
| US8930569B2 (en) | Methods and apparatus for optimum file transfers in a time-varying network emvironment | |
| EP2119171B1 (en) | Improved data transfer method, system and protocol | |
| US10284340B2 (en) | Multicast sending apparatus, multicast receiving apparatus, and multicast transmission determining method | |
| JP2004221681A (en) | System, apparatus and method for radio communication and computer program | |
| EP4002926A1 (en) | Data transmission method, terminal, and ran device | |
| AU2003286662B2 (en) | Method for acknowledging messages in a communication system | |
| CN109039551A (en) | A kind of Lora message reassembly abnormality eliminating method, transmitting terminal and receiving end | |
| CN109587023A (en) | A kind of LoRa ad hoc network method and system | |
| JP2002135357A (en) | Control method for data flow in communication system | |
| CN108923890A (en) | A kind of data transmission method, user equipment, base station and system | |
| CN108650688A (en) | A kind of method and Lora gateways of sweep check | |
| CN109151904A (en) | A kind of Lora message reassembly and repeating method, transmitting terminal and receiving end | |
| WO2016087331A1 (en) | Method for operating a communication device. | |
| CN106789916A (en) | Network transmission method and device based on UDP (user Datagram protocol), and network transmission method and device | |
| CN109450714A (en) | A kind of LoRa terminal node and its data transmission method | |
| Malinowsky et al. | Timed broadcast via off-the-shelf WLAN distributed coordination function for safety-critical systems | |
| CN108965063A (en) | A kind of abnormality eliminating method of sweep check, gateway and server | |
| CN116963175A (en) | Data transmission method, device and system | |
| WO2015096089A1 (en) | Fault-tolerance method and device for phich channel transmission information | |
| CN113132367A (en) | Data transmission self-adaption method and device for engineering monitoring Internet of things acquisition terminal | |
| WO2017075857A1 (en) | Information transmission method, terminal and base station | |
| EP3089396A1 (en) | Method and system for sending transmission acknowledgement information | |
| CN108650686A (en) | A kind of Ping-Pong test methods, terminal and the server of frequency sweep |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20181221 |