CN104348874B - The method and apparatus that message is transmitted between cloud platform component - Google Patents
The method and apparatus that message is transmitted between cloud platform component Download PDFInfo
- Publication number
- CN104348874B CN104348874B CN201310337934.XA CN201310337934A CN104348874B CN 104348874 B CN104348874 B CN 104348874B CN 201310337934 A CN201310337934 A CN 201310337934A CN 104348874 B CN104348874 B CN 104348874B
- Authority
- CN
- China
- Prior art keywords
- message
- cloud platform
- platform component
- middleware
- queue
- 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 24
- 238000012790 confirmation Methods 0.000 claims abstract description 42
- 230000005540 biological transmission Effects 0.000 claims abstract description 37
- 238000010586 diagram Methods 0.000 description 11
- 238000012545 processing Methods 0.000 description 6
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Landscapes
- Communication Control (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
This disclosure relates to the method and apparatus that message is transmitted between a kind of cloud platform component.This method includes any message A that reception source cloud platform component is sent；Any message A is transmitted to purpose cloud platform component, while starting timer；By any message A storage into message queue；In the case where timer has not timed out, if receiving the confirmation message from purpose cloud platform component feedback, any message A in message queue is removed；In the case where timer expiry, if not receiving the confirmation message from purpose cloud platform component feedback yet, any message A in message queue is retransmitted until receiving the confirmation message from purpose cloud platform component feedback or meeting the re-transmission termination condition of setting.The disclosure can effectively improve the message efficiency of transmission of message-oriented middleware.
Description
Technical Field
The present disclosure relates to the field of computers, and in particular, to a method and an apparatus for transmitting messages between cloud platform components.
Background
The inside of a resource pool in the cloud management platform and the resource pools in different regions are communicated through message middleware. The cloud platform components in the resource pool are directly communicated through message middleware; in addition, the message communication mode among the resource pools in different regions is that the sending end transfers the message to the message middleware of the resource point for transmission, the local message middleware transfers the message to the remote message middleware of the resource point where the receiving end is located, and finally the remote message middleware transfers the message to the receiving end.
At present, when a cloud management platform carries out message transmission, because a message middleware does not support a retransmission function, an upper cloud platform component application program needs extra codes to carry out message confirmation and retransmission operations, computing resources of upper application are consumed, meanwhile, more retransmission messages are possibly transmitted in a network to cause network blockage, and a large number of retransmission messages can increase the processing load of the message middleware and influence the transmission of normal messages.
Fig. 1 is a schematic diagram of a message retransmission mechanism between cloud platform components in the prior art.
As shown in fig. 1, each cloud platform component needs to process message acknowledgement and retransmission respectively, which consumes a large amount of computing resources, and because the retransmitted messages are transmitted from the source cloud platform to the message middleware and then are forwarded to the destination cloud platform by the message middleware, the number of retransmitted messages is too large, which may cause network congestion, and the retransmitted messages need to be received and forwarded by the message middleware, which increases the load of the message middleware.
Disclosure of Invention
The present disclosure proposes a new technical solution in view of at least one of the above problems.
The present disclosure provides, in one aspect thereof, a method for message transmission between cloud platform components, which effectively improves message transmission efficiency of message middleware.
The present disclosure provides, in another aspect thereof, an apparatus for message transmission between cloud platform components, which effectively improves message transmission efficiency of message middleware.
According to the present disclosure, there is provided a method for message transmission between cloud platform components, comprising:
receiving any message A sent by a source cloud platform component;
any message A is forwarded to a target cloud platform component, and meanwhile, a timer is started;
storing any message A into a message queue;
under the condition that the timer is not overtime, if confirmation information fed back by a target cloud platform assembly is received, any message A in the message queue is cleared;
and under the condition that the timer is overtime, if the confirmation message fed back by the target cloud platform component is not received, retransmitting any message A in the message queue until the confirmation message fed back by the target cloud platform component is received or the set retransmission ending condition is met.
In some embodiments of the present disclosure, an acknowledgement field is included in any message a.
In some embodiments of the present disclosure, the acknowledgement field in any message a from the source cloud platform component is FALSE.
In some embodiments of the disclosure, the method further comprises:
judging the value of the confirmation field in any received message A;
and if the value is FLASE, storing any message A in the message queue, otherwise, not storing any message A in the message queue.
In some embodiments of the disclosure, the method further comprises:
and after receiving the confirmation message fed back from the target cloud platform component, setting the confirmation field in any message A as TRUE.
In some embodiments of the present disclosure, the source cloud platform component and the destination cloud platform component are within the same resource pool or between different resource pools.
According to the present disclosure, there is also provided an apparatus for message transmission between cloud platform components, including:
the system comprises a transmission message receiving unit, a source cloud platform assembly and a message processing unit, wherein the transmission message receiving unit is used for receiving any message A sent by the source cloud platform assembly;
the message forwarding unit is used for forwarding any message A to the target cloud platform assembly and starting the timer at the same time;
the message storage unit is used for storing any message A into the message queue;
the message clearing unit is used for clearing any message A in the message queue if receiving confirmation information fed back by the target cloud platform component under the condition that the timer is not overtime;
and the message retransmission unit is used for retransmitting any message A in the message queue until the acknowledgement message fed back by the target cloud platform component is received or the set retransmission ending condition is met under the condition that the timer is overtime and if the acknowledgement message fed back by the target cloud platform component is not received yet.
In some embodiments of the present disclosure, an acknowledgement field is included in any message a.
In some embodiments of the present disclosure, the acknowledgement field in any message a from the source cloud platform component is FALSE.
In some embodiments of the present disclosure, the apparatus further comprises:
and the judging unit is used for judging the value of the confirmation field in any received message A, if the value is FLASE, storing any message A in the message queue, otherwise, not storing any message A in the message queue.
In some embodiments of the present disclosure, the apparatus further comprises:
and the confirmation field modification unit is used for setting the confirmation field in any message A to TRUE after receiving the confirmation message fed back from the target cloud platform component.
In some embodiments of the present disclosure, the source cloud platform component and the destination cloud platform component are within the same resource pool or between different resource pools.
In the technical scheme of the disclosure, since the message middleware stores the message in the message queue after receiving the message from the source cloud platform assembly, after the confirmation information from the target cloud platform assembly cannot be received within the set time, the original message does not need to be acquired from the source cloud platform assembly, and the message to be retransmitted is directly taken out from the message queue.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure, are incorporated in and constitute a part of this application. In the drawings:
fig. 1 is a schematic diagram of a message retransmission mechanism between cloud platform components in the prior art.
Fig. 2 is a flowchart illustrating a method for message transmission between cloud platform components according to an embodiment of the present disclosure.
Fig. 3 is a schematic diagram of a format of a message forwarded by the message middleware of the present disclosure.
Fig. 4 is a schematic diagram of message transmission between cloud platform components according to another embodiment of the present disclosure.
Fig. 5 is a schematic structural diagram of an apparatus for message transmission between cloud platform components according to an embodiment of the present disclosure.
Fig. 6 is a schematic structural diagram of an apparatus for message transmission between cloud platform components according to another embodiment of the present disclosure.
Fig. 7 is a schematic structural diagram of an apparatus for message transmission between cloud platform components according to yet another embodiment of the present disclosure.
Detailed Description
The present disclosure will be described below with reference to the accompanying drawings. It is to be noted that the following description is merely illustrative and exemplary in nature and is in no way intended to limit the disclosure, its application, or uses. Unless specifically stated otherwise, the relative arrangement of components and steps and numerical expressions and values set forth in the embodiments do not limit the scope of the present disclosure. Additionally, techniques, methods, and apparatus known to those skilled in the art may not be discussed in detail but are intended to be part of the specification where appropriate.
In order to solve the problems in the prior art, in the following embodiments of the present disclosure, a retransmission mechanism is transferred from each cloud platform component to a message middleware, and since the message middleware is located between a source cloud platform component and a destination cloud platform component and is a necessary path for the two components to transmit messages, the retransmission mechanism is arranged on the message middleware, so that the message retransmission efficiency can be significantly improved.
Fig. 2 is a flowchart illustrating a method for message transmission between cloud platform components according to an embodiment of the present disclosure.
This embodiment may be performed by message middleware, and in particular, as shown in fig. 2, may include the steps of:
s202, any message A sent by the source cloud platform assembly is received.
And S204, forwarding any received message A to a target cloud platform assembly, and starting a timer to judge whether confirmation information fed back by the target cloud platform assembly can be received within a set time, namely, whether retransmission of any message A is required can be determined according to the timer.
S206, storing any received message a in the message queue, so that when the destination cloud platform component does not receive any message a, any message a stored in the message queue can be used to implement retransmission of any message a, and it is not necessary to obtain any message a to be retransmitted from the source cloud platform component.
S208, if the timer is not overtime, if the acknowledgement information fed back from the destination cloud platform component is received, that is, the destination cloud platform component has received any message a, then any message a in the message queue may be cleared because retransmission of any message a is not required.
S210, if the timer is overtime, if the acknowledgement message fed back from the target cloud platform component is not received yet, it indicates that the target cloud platform component does not receive any message a, and at this time, any message a in the message queue needs to be retransmitted until the acknowledgement message fed back from the target cloud platform component is received or a set retransmission end condition is met.
In the embodiment, the message middleware stores the message in the message queue after receiving the message from the source cloud platform assembly, and after the confirmation information from the target cloud platform assembly cannot be received within the set time, the original message does not need to be acquired from the source cloud platform assembly, and the message to be retransmitted is directly taken out from the message queue.
To facilitate the above embodiments, an Acknowledgement field, i.e., an Acknowledgement field, may be included in any message a sent by the source cloud platform component to the destination platform component.
Specifically, a field indicating retransmission meaning is added to a message format used by the message middleware to implement a message confirmation and retransmission mechanism of the message middleware, and the message confirmation and retransmission operations are executed by the message middleware instead of upper layer applications (i.e., each cloud platform component), so that the upper layer applications are free from the complexity of processing messages of the bottom layer.
In one example, as shown in fig. 3, a Boolean type Acknowledgement field is added to the existing message structure, and the Boolean type Acknowledgement field is used to identify whether retransmission is needed. If the field is FALSE, it indicates that retransmission is required, otherwise it indicates that retransmission is not required.
For example, when the source platform component sends any message a to the destination cloud platform component through the message middleware, since it is uncertain whether the destination cloud platform component can receive the message, it is necessary to set the acknowledgement field in any message a to FALSE, so that the message middleware stores the message into the message queue considering that the message needs to be retransmitted, and if the message middleware receives the acknowledgement message fed back by the destination cloud platform component within the set time, the acknowledgement field is set to TRUE again, which indicates that the message has been received, and no retransmission is necessary, so that the message can be cleared from the message queue.
Further, after step S202, when the message middleware receives any message a, it determines a value of a confirmation field in the received any message a;
if the value is FLASE, the message is required to be retransmitted by the message middleware under the condition that the target cloud platform assembly cannot receive the message, otherwise, if the value is TRUE, the message is not required to be retransmitted by the message middleware even under the condition that the target cloud platform assembly cannot receive the message, so that any received message A is required to be stored in the message queue under the condition that the value is FALSE, and the message A is not required to be stored under the condition that the value is TRUE;
whether the value is TRUE or FALSE, the message middleware forwards any message a to the target cloud platform component.
If the message middleware receives the acknowledgement message fed back by the destination cloud platform component before the timer expires, which indicates that the destination cloud platform component receives any message a sent by the source platform component, the acknowledgement field in any message a may be set to TRUE at this time.
Before the turn of forwarding any message A pre-stored in the message queue, judging the value of the confirmation field, if the value is FALSE, indicating that the message needs to be retransmitted, otherwise, if the value is TRUE, indicating that the message process does not need to be retransmitted, and further clearing the message from the message queue.
In addition, it should be noted that the source cloud platform component and the destination cloud platform component in the foregoing embodiment may be located in the same resource pool, or may be located between different resource pools.
Fig. 4 is a schematic diagram of message transmission between cloud platform components according to another embodiment of the present disclosure.
As shown in fig. 4, an Acknowledgement and retransmission component may be added to the message middleware, and a Boolean (Boolean) type Acknowledgement field may be added to the message format, where the default value of the field is FALSE.
When the cloud platform component 2 and the cloud platform component 3 communicate with each other, the cloud platform component 2 first transmits the message a to the message middleware, and then the message middleware transmits the message a to the cloud platform component 3. Meanwhile, since the Acknowledgement field in message a passed by component 2 is FALSE, the message middleware will continue to retain message a and put message a at the end of the message queue.
Assuming that the cloud platform component 3 does not return an Acknowledgement to the message a, the message a gradually faces transmission by the message middleware again along with the advance of the message queue, and at this time, the message middleware finds that the Acknowledgement field of the reserved message a is still FALSE, and then sends the message a to the cloud platform component 3 again, thereby implementing retransmission of the message a.
After the cloud platform component 3 returns the Acknowledgement information of the message a, the message middleware modifies the Acknowledgement field of the message a to TRUE. And the message middleware has a background process to clean the message with the acknowledgment element being True at regular time.
It should be noted that the retransmission of the message a is not limited to one time, and the upper limit of the retransmission number may be set, or the retransmission may be continued until the cloud platform component 3 returns the acknowledgement information for the message a.
It will be understood by those skilled in the art that all or part of the steps of implementing the above method embodiments may be implemented by hardware associated with program instructions, the program may be stored in a storage medium readable by a computing device, and the program may execute the steps of the above method embodiments when executed, and the storage medium may include various media capable of storing program codes, such as ROM, RAM, magnetic disk and optical disk.
Fig. 5 is a schematic structural diagram of an apparatus for message transmission between cloud platform components according to an embodiment of the present disclosure.
As shown in fig. 5, the apparatus 50 in this embodiment may include a transmission message receiving unit 502, a message forwarding unit 504, a message storing unit 506, a message clearing unit 508, and a message retransmitting unit 510. Wherein,
a transmission message receiving unit 502, configured to receive any message a sent by a source cloud platform component;
a message forwarding unit 504, configured to forward any message a to a target cloud platform component, and start a timer at the same time;
a message storage unit 506, configured to store any message a in a message queue;
a message clearing unit 508, configured to clear any message a in the message queue if receiving acknowledgement information fed back from the target cloud platform component if the timer is not expired;
a message retransmitting unit 510, configured to, if the timer expires, if the acknowledgement message fed back from the destination cloud platform component is still not received, retransmit any message a in the message queue until the acknowledgement message fed back from the destination cloud platform component is received or a set retransmission end condition is met.
In the embodiment, the message middleware stores the message in the message queue after receiving the message from the source cloud platform assembly, and after the confirmation information from the target cloud platform assembly cannot be received within the set time, the original message does not need to be acquired from the source cloud platform assembly, and the message to be retransmitted is directly taken out from the message queue.
Further, an Acknowledgement field, i.e., an Acknowledgement field, is included in any message a.
The device for message transmission between the cloud platform components determines whether to discard or forward the message in the message queue according to the value of the field, and when the confirmation field in the message is FALSE, the message is forwarded, otherwise, when the confirmation field in the message is TRUE, the message is discarded. The content of the message may also be written to a message processing success log and some processing operations. After the message is forwarded by the device for message transmission between the cloud platform components, the message is placed in the message queue again for retransmission of the message, and the purpose is to temporarily store the message, wait for the confirmation message of the opposite terminal and not retransmit the message after confirmation. When the target cloud platform component to which the message is delivered has successfully received the message and returns "Acknowledgement" information, the message middleware sets the Acknowledgement field of the corresponding message to TRUE.
Further, the acknowledgement field in any message a from the source cloud platform component may be initially set to FALSE to prevent the destination from receiving the message correctly.
Fig. 6 is a schematic structural diagram of an apparatus for message transmission between cloud platform components according to another embodiment of the present disclosure.
As shown in fig. 6, compared to the embodiment in fig. 5, the apparatus 60 in this embodiment may further include:
a determining unit 602, configured to determine a value of a confirmation field in any received message a, if the value is FLASE, store the message a in a message queue, otherwise, store the message a in the message queue.
Fig. 7 is a schematic structural diagram of an apparatus for message transmission between cloud platform components according to yet another embodiment of the present disclosure.
As shown in fig. 7, compared to the embodiment in fig. 5, the apparatus 70 in this embodiment may further include:
and an acknowledgement field modifying unit 702, configured to set the acknowledgement field in any message a to TRUE after receiving the acknowledgement message fed back from the destination cloud platform component.
In addition, the source cloud platform component and the target cloud platform component are located in the same resource pool or between different resource pools.
It should be noted that, in practical applications, the device for message transmission between cloud platform components may be provided in the message middleware.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments can be mutually referred to. For the apparatus embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and reference may be made to the description of the method embodiment section for the relevant points.
The method for adding the confirmation field in the message format used by the message middleware in the embodiment of the disclosure realizes the message confirmation and retransmission mechanism of the message middleware, and the message confirmation and retransmission operations are executed by the message middleware instead of the upper layer application, so that the upper layer application is free from the complexity of processing the bottom layer message, and the message transmission efficiency of the message middleware is effectively improved.
While the present disclosure has been described with reference to exemplary embodiments, it should be understood that the present disclosure is not limited to the exemplary embodiments described above. It will be apparent to those skilled in the art that the above-described exemplary embodiments may be modified without departing from the scope and spirit of the disclosure. The scope of the following claims is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structures and functions.
Claims (4)
1. A method for message transmission between cloud platform components is characterized by comprising the following steps:
the method comprises the steps that a message middleware receives any message A sent by a source cloud platform assembly, wherein the message A comprises a confirmation field;
the message middleware forwards any message A to a target cloud platform component and starts a timer at the same time;
the message middleware stores the any message A into a message queue;
if the timer is not overtime, if the message middleware receives confirmation information fed back from the target cloud platform component, clearing any message A in the message queue; after receiving the confirmation information of the message A returned by the target cloud platform component, the message middleware modifies the confirmation field in the message A into TRUE and regularly cleans the message with the confirmation field being TRUE;
under the condition that the timer is overtime, if the message middleware still does not receive the acknowledgement message fed back by the target cloud platform component, retransmitting the any message A in the message queue until the acknowledgement message fed back by the target cloud platform component is received or a set retransmission ending condition is met;
the message middleware judges the value of the received confirmation field in any message A;
if the value is FALSE, the message middleware stores any message A in a message queue and puts the message A at the tail of the message queue; otherwise, the message middleware does not store any message A in the message queue.
2. The method for message transmission between cloud platform components according to claim 1, wherein the source cloud platform component and the destination cloud platform component are within the same resource pool or between different resource pools.
3. An apparatus for message transmission between cloud platform components, comprising:
the system comprises a transmission message receiving unit, a source cloud platform component and a source cloud platform component, wherein the transmission message receiving unit is used for receiving any message A sent by the source cloud platform component, and the any message A comprises a confirmation field;
the message forwarding unit is used for forwarding any message A to the target cloud platform assembly and starting a timer at the same time;
the message storage unit is used for storing any message A into a message queue;
a message clearing unit, configured to clear any message a in the message queue if receiving acknowledgement information fed back from the target cloud platform component when the timer is not overtime; after the transmission message receiving unit receives the confirmation information of the message A returned by the target cloud platform assembly, the message clearing unit modifies the confirmation field in the message A into TRUE and regularly clears the message with the confirmation field being TRUE;
a message retransmission unit, configured to, if the timer is overtime, if an acknowledgement message fed back by the destination cloud platform component is still not received, retransmit the any message a in the message queue until an acknowledgement message fed back by the destination cloud platform component is received or a set retransmission end condition is met;
a judging unit, configured to judge a value of a confirmation field in any received message a, and if the value is FALSE, store the message a in a message queue, and place the message a at the end of the message queue; otherwise, none of the messages A are stored in the message queue.
4. The apparatus for message transmission between cloud platform components according to claim 3, wherein the source cloud platform component and the destination cloud platform component are within the same resource pool or between different resource pools.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310337934.XA CN104348874B (en) | 2013-08-06 | 2013-08-06 | The method and apparatus that message is transmitted between cloud platform component |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310337934.XA CN104348874B (en) | 2013-08-06 | 2013-08-06 | The method and apparatus that message is transmitted between cloud platform component |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104348874A CN104348874A (en) | 2015-02-11 |
| CN104348874B true CN104348874B (en) | 2019-04-05 |
Family
ID=52503663
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310337934.XA Active CN104348874B (en) | 2013-08-06 | 2013-08-06 | The method and apparatus that message is transmitted between cloud platform component |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104348874B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105262801A (en) * | 2015-09-24 | 2016-01-20 | 广东亿迅科技有限公司 | Method and system for message distribution of cloud platform |
| CN107317745A (en) * | 2017-06-06 | 2017-11-03 | 山东中创软件商用中间件股份有限公司 | Method for message transmission and device between a kind of consumption terminal and Message Agent |
| CN108712475A (en) * | 2018-04-27 | 2018-10-26 | 深圳市元征科技股份有限公司 | Message method, device, electronic equipment and computer readable storage medium |
| CN109714409B (en) * | 2018-12-21 | 2021-09-14 | 优估（上海）信息科技有限公司 | Message management method and system |
| CN109951261B (en) * | 2019-03-20 | 2021-09-28 | 江苏满运软件科技有限公司 | Middleware message transmission compensation method and device, electronic equipment and storage medium |
| CN113890878A (en) * | 2021-09-30 | 2022-01-04 | 河北云智慧信息科技有限公司 | Edge computing system for transformer substation monitoring data |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102368700A (en) * | 2011-10-25 | 2012-03-07 | 曙光信息产业(北京)有限公司 | Transmission method of massages in distributed system |
| CN103024060A (en) * | 2012-12-20 | 2013-04-03 | 中国科学院深圳先进技术研究院 | Open type cloud computing monitoring system for large scale cluster and method thereof |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FI102346B (en) * | 1996-02-05 | 1998-11-13 | Nokia Telecommunications Oy | Short message queuing mechanism |
| CN101056194B (en) * | 2006-06-30 | 2011-04-06 | 华为技术有限公司 | A SNMP message transfer method and device |
-
2013
- 2013-08-06 CN CN201310337934.XA patent/CN104348874B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102368700A (en) * | 2011-10-25 | 2012-03-07 | 曙光信息产业(北京)有限公司 | Transmission method of massages in distributed system |
| CN103024060A (en) * | 2012-12-20 | 2013-04-03 | 中国科学院深圳先进技术研究院 | Open type cloud computing monitoring system for large scale cluster and method thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104348874A (en) | 2015-02-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104348874B (en) | The method and apparatus that message is transmitted between cloud platform component | |
| CN103138905B (en) | The confirmation method of RLC packet transmission and RLC AM entity sender | |
| US10284340B2 (en) | Multicast sending apparatus, multicast receiving apparatus, and multicast transmission determining method | |
| US9037935B2 (en) | Apparatus and method for retransmitting message in message transmission system | |
| CN109743143B (en) | Data retransmission method, device and computer readable storage medium | |
| CN101340268B (en) | Implementing method and system for inter-node communication confirming mechanism | |
| EP3235271A1 (en) | Methods for enabling delay-awareness in the constrained application protocol (coap) | |
| CN102685204A (en) | Method and equipment for transmitting data resource | |
| US20100217889A1 (en) | Accelerated block option for trivial file transfer protocol (tftp) | |
| KR101931858B1 (en) | Methods for receiving response information in M2M system and Apparatuses thereof | |
| CN101753277A (en) | Method for transmitting message status report of radio link control layer | |
| CN105162706B (en) | Multicast transmission method, apparatus and system | |
| JP6745821B2 (en) | Method and device for resending hypertext transfer protocol request, and client terminal | |
| US9456325B2 (en) | Transmission of a multimedia message doubled with the transmission of a text message | |
| WO2019062074A1 (en) | Method and apparatus for transmitting on-board device data | |
| CN103973414A (en) | Data transmission method and device | |
| US8149830B2 (en) | Efficient light-weight multicasting communication protocol | |
| US20150063352A1 (en) | Wireless networking with flexibly-ordered relayers | |
| US8370443B2 (en) | Reliable messaging using publish subscribe mechanism | |
| CN107786607B (en) | Message retransmission method, message retransmission server and user equipment | |
| CN117040692A (en) | Method and device for transmitting service data, electronic equipment and storage medium | |
| CN107566291B (en) | Multicast transmission method, device, electronic equipment and storage medium | |
| KR101611663B1 (en) | Data communications using connectionless-oriented protocol | |
| CN112187408B (en) | Data processing method, system, device, storage medium and processor | |
| US10003470B2 (en) | Method and terminal for transmitting and receiving data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |