A communication method, carrier proxy module and station area fusion terminal

Abstract

The present invention provides a communication method, a carrier proxy module and a station fusion terminal, the method comprising: receiving forwarding requests sent by multiple carrier service applications; storing the data to be sent sent by each carrier service application in a queue to be sent; and sending the data to be sent in the queue to be sent to a carrier communication device one by one according to the order of forwarding priority. In this scheme, when forwarding requests sent by multiple carrier service applications are received, the data to be sent sent by each carrier service application is stored in the queue to be sent. The data to be sent in the queue to be sent is sent to the carrier communication device one by one according to the order of forwarding priority, so as to avoid communication conflicts between multiple carrier service applications and the carrier communication device and improve the stability of communication.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a communication method, a carrier proxy module and a station area fusion terminal. Background Art

[0002] In the station area fusion terminal, the carrier service application (application, APP) communicates with the carrier communication device in the form of a serial port and a general purpose input / output port (General Purpose Input Output, GPIO).

[0003] Currently, the communication mode between the carrier service APP and the carrier communication device is a master-slave communication mode. However, when multiple carrier service APPs communicate with the carrier communication device (multi-master-one-slave communication mode), communication conflicts will occur and the communication stability is poor. Summary of the invention

[0004] In view of this, the embodiments of the present invention provide a communication method, a carrier proxy module and a station fusion terminal to solve the problems of poor communication stability in current communication methods.

[0005] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0006] A first aspect of an embodiment of the present invention discloses a communication method, the method comprising:

[0007] receiving forwarding requests sent by multiple carrier service applications, wherein the forwarding requests at least include data to be sent and a forwarding priority;

[0008] storing the to-be-sent data sent by each of the carrier service applications in a to-be-sent queue;

[0009] The data to be sent in the queue to be sent are sent to the carrier communication device one by one according to the order of forwarding priority.

[0010] Preferably, storing the to-be-sent data sent by each of the carrier service applications in a to-be-sent queue includes:

[0011] For each of the data to be sent sent by the carrier service application, parse the data to be sent to obtain JSON data information corresponding to the data to be sent;

[0012] The json data information corresponding to the data to be sent sent by each of the carrier service applications is stored in the queue to be sent.

[0013] Preferably, the process of sending the data to be sent in the queue to be sent to the carrier communication device includes:

[0014] For each piece of data to be sent in the queue to be sent, the data to be sent is packaged using a preset communication protocol;

[0015] According to the preset communication mode, the packaged data to be sent is sent to the carrier communication device.

[0016] Preferably, after sending the data to be sent in the to-be-sent queue to the carrier communication device one by one according to the order of forwarding priority, the method further includes:

[0017] For each to-be-sent data sent to the carrier communication device, receiving feedback data information corresponding to the to-be-sent data fed back by the carrier communication device;

[0018] For each piece of feedback data information, the feedback data information is sent to the carrier service application corresponding to the corresponding data to be sent.

[0019] Preferably, before sending the data to be sent in the to-be-sent queue to the carrier communication device one by one according to the order of forwarding priority, the method further includes:

[0020] Acquiring operation status information of the carrier communication device, wherein the operation status information is used to indicate whether the operation status of the carrier communication device is a normal state or an abnormal state;

[0021] If the operation status information indicates that the operation status of the carrier communication device is normal, the step of sending the to-be-sent data in the to-be-sent queue to the carrier communication device one by one is performed.

[0022] A second aspect of an embodiment of the present invention discloses a carrier proxy module, the carrier proxy module comprising:

[0023] A communication unit, configured to receive forwarding requests sent by a plurality of carrier service applications, and store the to-be-sent data sent by each of the carrier service applications in a to-be-sent queue, wherein the forwarding request at least includes the to-be-sent data and a forwarding priority;

[0024] The carrier interaction unit is used to send the to-be-sent data in the to-be-sent queue to the carrier communication device one by one according to the order of forwarding priority.

[0025] Preferably, the communication unit is used to store the data to be sent sent by each of the carrier service applications in the queue to be sent, and is specifically used to: parse the data to be sent for each of the carrier service applications, obtain the json data information corresponding to the data to be sent, and store the json data information corresponding to the data to be sent sent by each of the carrier service applications in the queue to be sent.

[0026] Preferably, the carrier interaction unit is specifically used for: for each data to be sent in the queue to be sent, packaging the data to be sent using a preset communication protocol, and sending the packaged data to be sent to the carrier communication device according to a preset communication method.

[0027] Preferably, the carrier interaction unit is further used to: for each data to be sent to the carrier communication device, receive feedback data information corresponding to the data to be sent fed back by the carrier communication device;

[0028] Correspondingly, the communication unit is further used for: for each piece of feedback data information, sending the feedback data information to the carrier service application corresponding to the corresponding data to be sent.

[0029] The third aspect of the embodiment of the present invention discloses a station area fusion terminal, the station area fusion terminal comprises: an application layer, a carrier proxy module disclosed in the second aspect of the embodiment of the present invention, a driver layer and a hardware layer;

[0030] The application layer is connected to the carrier proxy module, the carrier proxy module is connected to the driver layer, and the driver layer is connected to the hardware layer.

[0031] Based on a communication method, a carrier proxy module and a station fusion terminal provided by the above-mentioned embodiment of the present invention, the method is: receiving forwarding requests sent by multiple carrier service applications; storing the data to be sent sent by each carrier service application in a queue to be sent; and sending the data to be sent in the queue to be sent to the carrier communication device one by one according to the order of forwarding priority. In this scheme, when forwarding requests sent by multiple carrier service applications are received, the data to be sent sent by each carrier service application is stored in the queue to be sent. The data to be sent in the queue to be sent is sent to the carrier communication device one by one according to the order of forwarding priority, so as to avoid communication conflicts between multiple carrier service applications and the carrier communication device and improve the stability of communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0033] Figure 1 A structural block diagram of a station area fusion terminal provided by an embodiment of the present invention;

[0034] Figure 2 A schematic diagram of the architecture of a station area fusion terminal provided in an embodiment of the present invention;

[0035] Figure 3 A flow chart of a communication method provided by an embodiment of the present invention;

[0036] Figure 4 A schematic diagram of carrier communication between a station area fusion terminal and other devices provided in an embodiment of the present invention;

[0037] Figure 5 Another flow chart of a communication method provided by an embodiment of the present invention;

[0038] Figure 6 A structural block diagram of a carrier proxy module provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0039] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0040] In this application, the terms "comprises", "comprising" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprising a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element.

[0041] As can be seen from the background technology, in a station area fusion terminal, when multiple carrier service APPs communicate with a carrier communication device, communication conflicts will occur and the stability of communication will be poor.

[0042] Therefore, the embodiment of the present invention provides a communication method, a carrier proxy module and a station area fusion terminal, which stores the to-be-sent data sent by multiple carrier service applications in a to-be-sent queue. The to-be-sent data in the to-be-sent queue are sent to the carrier communication device one by one according to the order of forwarding priority, so as to avoid communication conflicts between multiple carrier service applications and the carrier communication device, so as to improve the stability of communication.

[0043] It should be noted that the carrier communication device (also called carrier module) is a modem for power line carrier communication, and the carrier communication device in the substation fusion terminal (also called substation intelligent fusion terminal) exchanges information with the carrier communication devices of other devices through the power line.

[0044] See also Figure 1 , shows a structural block diagram of a station area fusion terminal provided by an embodiment of the present invention, the station area fusion terminal includes: an application layer 100, a carrier proxy module 200, a driver layer 300 and a hardware layer 400, the application layer 100 is connected to the carrier proxy module 200, the carrier proxy module 200 is connected to the driver layer 300, and the driver layer 300 is connected to the hardware layer 400.

[0045] It can be understood that a communication interface is abstracted in the application layer 100 , and the communication interface is composed of a carrier proxy module 200 , and the carrier proxy module 200 interacts with the application layer 100 via a message queuing telemetry transport (MQTT) protocol.

[0046] The carrier proxy module 200 calls the driver layer 300 and performs data exchange with the hardware layer 400 through the 1376.2 (Q / GDW 1376.2) protocol.

[0047] To better explain the above Figure 1 The specific content in the integrated terminal of the station area is Figure 2 The schematic diagram of the architecture of the station area fusion terminal is used as an example. It should be noted that: Figure 2 For illustration purposes only.

[0048] exist Figure 2 In the application layer 100, multiple carrier service applications ( Figure 2 The carrier service APPs in the figure are carrier service APP1, carrier service APP2 and carrier service APP3 respectively.

[0049] The abstract communication interface is composed of the carrier proxy module 200 ( Figure 2 The carrier agent module 200 is composed of a carrier agent APP200, wherein the carrier agent module 200 interacts with the application layer 100 through an MQTT agent (MQTT Broker).

[0050] The driver layer 300 at least includes a serial port and a GPIO.

[0051] The hardware layer 400 includes at least a carrier module (carrier communication device).

[0052] According to the above Figure 2In the content, the carrier proxy module 200 is north-facing to each carrier service APP in the application layer 100 and south-facing to the driver layer 300, and can call the application programming interface (Application Programming Interface, API) of the serial port and GPIO.

[0053] It should be noted that the above-mentioned “carrier proxy module 200 northbound facing the application layer 100” means: for example, the upper-level device of the carrier proxy module 200 is the application layer 100, and the above-mentioned “carrier proxy module 200 southbound facing the driver layer 300” means: for example, the lower-level device of the carrier proxy module 200 is the driver layer 300.

[0054] See also Figure 3 , showing a flow chart of a communication method provided by an embodiment of the present invention, the communication method is applied to the above-mentioned embodiment of the present invention Figure 1 The carrier proxy module of the station area fusion terminal in the communication method comprises the following steps:

[0055] Step S301: receiving forwarding requests sent by multiple carrier service applications.

[0056] It should be noted that the forwarding request at least includes but is not limited to: data to be sent, forwarding priority, data length, timestamp and target carrier communication device.

[0057] It can be understood that from the foregoing content, the carrier communication device in the substation fusion terminal exchanges information with the carrier communication devices of other devices through power lines. For a carrier service application, the carrier service application sends the data to be sent to the carrier communication device of other devices (called the target carrier communication device) through the carrier communication device of the substation fusion terminal where it is located.

[0058] In the specific implementation of step S301, when data concurrency occurs in multiple carrier service applications, forwarding requests sent by multiple carrier service applications are received simultaneously.

[0059] It should be noted that the aforementioned simultaneous reception of forwarding requests sent by multiple carrier service applications refers to: receiving forwarding requests sent by multiple carrier service applications within a preset time.

[0060] Preferably, when receiving a forwarding request sent by a carrier service application, the fault status information of the carrier proxy module is obtained. If the carrier proxy module fails, the abnormal result is fed back to the carrier service application. If the carrier proxy module does not fail, the subsequent process is continued.

[0061] Step S302: storing the to-be-sent data sent by each carrier service application in a to-be-sent queue.

[0062] It should be noted that the data items in json format of the data to be sent are preset, and the carrier service application and the carrier proxy module perform data exchange in json format, that is, the data to be sent sent by the carrier service application is in json format.

[0063] In the process of specifically implementing step S302, for the data to be sent sent by each carrier service application, the data to be sent is parsed according to the preset json format data items of the data to be sent to obtain the json data information corresponding to the data to be sent.

[0064] The json data information corresponding to the data to be sent sent by each carrier service application is stored in the queue to be sent.

[0065] Step S303: sending the data to be sent in the queue to be sent to the carrier communication device one by one according to the order of forwarding priority.

[0066] It should be noted that, from the foregoing content, a corresponding forwarding priority is set in advance for the data to be sent by each carrier service application, that is, the json data information corresponding to the data to be sent in the queue to be sent has a corresponding forwarding priority.

[0067] The data to be sent are extracted from the queue to be sent one by one in the order of forwarding priority from high to low, and the extracted data to be sent are sent to the carrier communication device.

[0068] For example, assuming that there are data A to be sent, data B to be sent, and data C to be sent in the queue to be sent, the order of forwarding priority from high to low is data A to be sent, data B to be sent, and data C to be sent. First, data A to be sent is extracted from the queue to be sent, and data A to be sent is sent to the carrier communication device, then data B to be sent is extracted from the queue to be sent, and data B to be sent is sent to the carrier communication device, and finally data C to be sent is extracted from the queue to be sent, and data C to be sent is sent to the carrier communication device.

[0069] It can be understood that, for the to-be-sent data with the same forwarding priority, the to-be-sent data first stored in the to-be-sent queue will be sent to the carrier communication device according to the first-come-first-sent rule.

[0070] In the specific implementation of step S303, for each data to be sent in the to-be-sent queue, the data to be sent is packaged using a preset communication protocol, and the packaged data to be sent is sent to the carrier communication device according to a preset communication method.

[0071] That is to say, for each piece of data to be sent to the carrier communication device in the queue to be sent, the data to be sent is packaged according to the preset communication protocol (such as the 1376.2 protocol), and then the packaged data to be sent is sent to the carrier communication device using the preset communication method (serial port and GPIO).

[0072] It can be understood that after the data to be sent is sent to the carrier communication device, the carrier communication device sends the data to be sent to the target carrier communication device (carrier communication device of other equipment) corresponding to the data to be sent.

[0073] When the 1376.2 protocol is used to package the data to be sent, the destination address (the address information of the target carrier communication device) is added to the address information field of the 1376.2 protocol frame format, that is, the packaged data to be sent carries the destination address. After receiving the packaged data to be sent, the carrier communication device sends the data to be sent to the corresponding target carrier communication device according to the destination address corresponding to the packaged data to be sent.

[0074] To better explain the carrier communication device that sends the data to be sent to other devices through the carrier communication device in the station area fusion terminal, Figure 4 To illustrate with an example, it should be noted that Figure 4 For illustration purposes only.

[0075] exist Figure 4 In the embodiment, the carrier communication device in the area fusion terminal is connected to the carrier communication device of each device (device 1 to device N) through the power line. After receiving the data to be sent, the carrier communication device in the area fusion terminal sends the data to be sent to the corresponding target carrier communication device according to the destination address of the data to be sent.

[0076] From the contents of the above steps, it can be seen that when multiple carrier service applications communicate with the carrier communication device concurrently (many-to-one communication mode), the many-to-one communication mode is converted into a one-to-one communication mode through the contents of the above steps S301 to S303, thereby avoiding communication conflicts between multiple carrier service applications and the carrier communication device.

[0077] Preferably, before executing step S303, operation status information of the carrier communication device is acquired, where the operation status information is used to indicate whether the operation status of the carrier communication device is a normal state or an abnormal state.

[0078] Based on the operating status information of the carrier communication device, determine whether the operating status of the carrier communication device is in a normal state. If the operating status information indicates that the operating status of the carrier communication device is in a normal state, execute step S303. If the operating status information indicates that the operating status of the carrier communication device is in a fault state, feedback fault alarm information indicating that a fault has occurred in the carrier communication device is provided to the carrier service application.

[0079] Preferably, after the data to be sent in the to-be-sent queue is sent to the carrier communication device, the carrier communication device feeds back feedback data information corresponding to the data to be sent.

[0080] In a specific implementation, for each to-be-sent data sent to the carrier communication device, feedback data information corresponding to the to-be-sent data fed back by the carrier communication device is received.

[0081] For each feedback data information, the feedback data information is sent to the carrier service application corresponding to the corresponding data to be sent. That is, after the data to be sent of a carrier service application is sent to the carrier communication device, the carrier communication device feeds back the feedback data information corresponding to the data to be sent and sends it to the carrier service application.

[0082] It is understandable that after receiving the feedback data information sent by the carrier communication device, the feedback data information is parsed, and the parsed feedback data information is organized into a json message format according to the preset json format data items. The mqtt publishing function is called to send the parsed feedback data information in the json message format to the corresponding carrier service application.

[0083] For example, for meter reading applications (meter reading APP), the meter reading APP collects meter information through carrier mode, packages the meter information (data to be sent) in 645 protocol format, and then packages the meter information according to the preset json format data items. The meter information in json format is sent to the carrier proxy module through mqtt.

[0084] The carrier proxy module parses the meter information in the 645 protocol format according to the preset json format data items, and stores the meter information in the queue to be sent. The carrier proxy module extracts the meter information in the 645 protocol format in the queue to be sent according to the content in the aforementioned step S303 (sending the data to be sent according to the forwarding priority), and packages the meter information in the 645 protocol format into the meter information in the 1376.2 protocol format. The carrier proxy module sends the meter information in the 1376.2 protocol format to the carrier communication device, and receives the feedback data information corresponding to the meter information fed back by the carrier communication device, and feeds the feedback data information back to the meter reading APP.

[0085] It should be noted that the process of feeding back the feedback data information to the meter reading APP is the reverse process of sending the meter information to the carrier communication device in the above example, and will not be described in detail here.

[0086] In the embodiment of the present invention, when forwarding requests sent by multiple carrier service applications are received, the data to be sent sent by each carrier service application is stored in a queue to be sent. The data to be sent in the queue to be sent is sent to the carrier communication device one by one according to the order of forwarding priority, thereby avoiding communication conflicts between multiple carrier service applications and the carrier communication device and improving the stability of communication.

[0087] According to the above-mentioned embodiments of the present invention Figure 3 According to the contents of each step in the above, the carrier proxy module can realize the serialization of the data to be sent, thereby solving the problem that multiple carrier service applications cannot use the carrier communication device (the carrier communication device in the station area fusion terminal) in parallel.

[0088] To better explain the above embodiments of the present invention Figure 3 The content in Figure 5 To illustrate with an example, it should be noted that Figure 5 For illustration purposes only.

[0089] See also Figure 5 , shows another flow chart of a communication method provided by an embodiment of the present invention, the communication method comprising the following steps:

[0090] Step S501: Determine the operating status of the carrier communication device.

[0091] It can be understood that the carrier proxy module communicates with the carrier communication device through the 1376.2 protocol, and step S501 includes sub-steps S5011 to S5012.

[0092] Sub-step S5011: start the carrier communication device identification process to obtain the operating status information of the carrier communication device.

[0093] Sub-step S5012: Determine whether the operating state of the carrier communication device is a normal state or an abnormal state according to the operating state information.

[0094] Step S502: receiving a forwarding request sent by a carrier service application, and storing the to-be-sent data included in the forwarding request into a to-be-sent queue.

[0095] It is understandable that the carrier proxy module communicates with the carrier service application through MQTT Broker, and the carrier proxy module receives the data to be sent in json format sent by the carrier service application through MQTT Broker by subscribing to topics related to carrier communication. Step S502 includes sub-steps S5021 to S5023.

[0096] Sub-step S5021: upon receiving a forwarding request sent by a carrier service application, determining whether the operation state of the carrier communication device is normal. If the operation state of the carrier communication device is normal, executing sub-step S5022, if the operation state of the carrier communication device is abnormal, feeding back a response result including fault alarm information to the carrier service application.

[0097] Sub-step S5022: Determine whether there is free space in the linked list. If there is free space in the linked list, execute sub-step S5023. If there is no free space in the linked list, feed back a response result including abnormal information indicating insufficient space to the carrier service application.

[0098] It can be understood that the queue to be sent exists in a linked list data structure, that is, the linked list in sub-step S5022 is the queue to be sent.

[0099] Sub-step S5023: storing the to-be-sent data corresponding to the forwarding request in a linked list.

[0100] From the above content, it can be seen that after sending the data to be sent to the carrier communication device, the feedback data information fed back by the carrier communication device needs to be sent to the carrier business application. The carrier agent module processes the feedback data information according to the 1376.2 protocol and the preset json format data items, and calls the mqtt API function to publish the processed feedback data information to the MQTTBroker.

[0101] Preferably, step S502 also includes sub-step S5024.

[0102] Sub-step S5024: Send feedback data information corresponding to the data to be sent to the carrier service application.

[0103] In the specific implementation, the carrier business application receives the feedback data information pushed by MQTT Broker by subscribing to the relevant topics of the carrier proxy module.

[0104] Step S503: sending the data to be sent in the queue to be sent to the carrier communication device one by one in the order of forwarding priority.

[0105] It is understandable that the carrier proxy module calls the API of the serial port and GPIO through the 1376.2 protocol to send the data to be sent in the waiting queue to the carrier communication device one by one. Step S503 includes sub-steps S5031 to S5033.

[0106] Sub-step S5031: Determine whether the linked list is idle. If the linked list is not idle, execute sub-step S5032.

[0107] It can be understood that if the linked list (queue to be sent) is idle, it indicates that there is no data to be sent in the linked list, and if the linked list is not idle, it indicates that there is data to be sent in the linked list.

[0108] Sub-step S5032: Start the copying process and send the data to be sent in the linked list to the carrier communication device one by one.

[0109] It should be noted that the specific process of the copying process can be found in the specific content of Agreement 1376.2.

[0110] Sub-step S5033: Delete the linked list nodes that have been clicked.

[0111] It is understandable that the queue to be sent is a linked list data structure. When the data to be sent is sent one by one using the copy process, after each piece of data to be sent is sent, the linked list node corresponding to the data to be sent needs to be deleted to avoid repeated sending of the data to be sent.

[0112] It should be noted that Figure 5 The feedback data information is transmitted between step S502 and step S503 in the form of a message queue.

[0113] In the embodiment of the present invention, the carrier proxy module communicates with the carrier service application through the MQTT Broker. When receiving a forwarding request from the carrier service application, the data to be sent corresponding to the forwarding request is stored in a linked list. According to the order of forwarding priority, the data to be sent in the linked list are sent to the carrier communication device one by one, and the linked list nodes corresponding to the data to be sent that have been sent are deleted, so as to avoid communication conflicts between multiple carrier service applications and the carrier communication device and improve the stability of communication.

[0114] Corresponding to a communication method provided by the above embodiment of the present invention, see Figure 6 The embodiment of the present invention also provides a structural block diagram of a carrier proxy module, and the carrier proxy module includes: a communication unit 601 and a carrier interaction unit 602.

[0115] The communication unit 601 is used to receive forwarding requests sent by multiple carrier service applications, and store the to-be-sent data sent by each carrier service application into a to-be-sent queue, wherein the forwarding request at least includes the to-be-sent data and a forwarding priority.

[0116] Preferably, the communication unit 601 is further used for: upon receiving a forwarding request, if the carrier interaction unit 602 fails, sending abnormal fault information indicating that the carrier interaction unit 602 fails to the carrier service application.

[0117] In a specific implementation, the communication unit 601 is used to store the data to be sent sent by each carrier service application in the queue to be sent, and is specifically used to: parse the data to be sent sent by each carrier service application, obtain the json data information corresponding to the data to be sent, and store the json data information corresponding to the data to be sent sent by each carrier service application in the queue to be sent.

[0118] The carrier interaction unit 602 is used to send the to-be-sent data in the to-be-sent queue to the carrier communication device one by one according to the order of forwarding priority.

[0119] In a specific implementation, the carrier interaction unit 602 is specifically used to: for each data to be sent in the queue to be sent, package the data to be sent using a preset communication protocol, and send the packaged data to be sent to the carrier communication device according to a preset communication method.

[0120] Preferably, the carrier interaction unit 602 is further used for: for each data to be sent to the carrier communication device, receiving feedback data information corresponding to the data to be sent fed back by the carrier communication device.

[0121] Correspondingly, the communication unit 601 is further configured to: for each piece of feedback data information, send the feedback data information to the carrier service application corresponding to the corresponding data to be sent.

[0122] Preferably, the communication unit 601 is also used to: obtain the operating status information of the carrier communication device, if the operating status information indicates that the operating status of the carrier communication device is normal, execute the carrier interaction unit 602, the operating status information is used to indicate that the operating status of the carrier communication device is normal or abnormal.

[0123] In summary, an embodiment of the present invention provides a communication method, a carrier proxy module, and a station fusion terminal. The method is: receiving forwarding requests sent by multiple carrier service applications; storing the data to be sent sent by each carrier service application in a queue to be sent; and sending the data to be sent in the queue to be sent to a carrier communication device one by one according to the order of forwarding priority. In this solution, when forwarding requests sent by multiple carrier service applications are received, the data to be sent sent by each carrier service application is stored in the queue to be sent. The data to be sent in the queue to be sent is sent to the carrier communication device one by one according to the order of forwarding priority, so as to avoid communication conflicts between multiple carrier service applications and the carrier communication device and improve the stability of communication.

[0124] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without creative work.

[0125] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0126] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A communication method, characterized in that: The method comprises: receiving forwarding requests sent by multiple carrier service applications, wherein the forwarding requests at least include data to be sent and a forwarding priority; storing the to-be-sent data sent by each of the carrier service applications in a to-be-sent queue; According to the order of forwarding priority, the data to be sent in the queue to be sent are sent to the carrier communication device one by one; The storing the to-be-sent data sent by each of the carrier service applications into a to-be-sent queue comprises: For each of the data to be sent sent by the carrier service application, parse the data to be sent to obtain JSON data information corresponding to the data to be sent; The JSON data information corresponding to the data to be sent sent by each of the carrier service applications is stored in a queue to be sent; The process of sending the data to be sent in the to-be-sent queue to the carrier communication device includes: For each piece of data to be sent in the queue to be sent, the data to be sent is packaged using a preset communication protocol; According to a preset communication method, the packaged data to be sent is sent to the carrier communication device; After sending the data to be sent in the queue to be sent to the carrier communication device one by one according to the order of forwarding priority, the method further includes: For each to-be-sent data sent to the carrier communication device, receiving feedback data information corresponding to the to-be-sent data fed back by the carrier communication device; For each piece of feedback data information, the feedback data information is sent to the carrier service application corresponding to the corresponding data to be sent.

2. The method according to claim 1, characterized in that Before sending the data to be sent in the queue to be sent to the carrier communication device one by one according to the order of forwarding priority, the method further includes: Acquiring operation status information of the carrier communication device, wherein the operation status information is used to indicate whether the operation status of the carrier communication device is a normal state or an abnormal state; If the operation status information indicates that the operation status of the carrier communication device is normal, the step of sending the to-be-sent data in the to-be-sent queue to the carrier communication device one by one is performed.

3. A carrier proxy module, characterized in that: The carrier proxy module includes: A communication unit, configured to receive forwarding requests sent by a plurality of carrier service applications, and store the to-be-sent data sent by each of the carrier service applications in a to-be-sent queue, wherein the forwarding request at least includes the to-be-sent data and a forwarding priority; A carrier interaction unit, configured to send the data to be sent in the queue to be sent to the carrier communication device one by one according to the order of forwarding priority; The carrier proxy module is used to store the data to be sent sent by each carrier service application in the communication unit in the queue to be sent, and is specifically used to: for each data to be sent sent by the carrier service application, parse the data to be sent, obtain the json data information corresponding to the data to be sent, and store the json data information corresponding to the data to be sent sent by each carrier service application in the queue to be sent; The carrier interaction unit is specifically used to: for each data to be sent in the to-be-sent queue, package the data to be sent using a preset communication protocol, and send the packaged data to be sent to the carrier communication device according to a preset communication method; The carrier interaction unit is further used to: for each data to be sent to the carrier communication device, receive feedback data information corresponding to the data to be sent fed back by the carrier communication device; Correspondingly, the communication unit is further used for: for each piece of feedback data information, sending the feedback data information to the carrier service application corresponding to the corresponding data to be sent.

4. A station area fusion terminal, characterized in that: The station area fusion terminal comprises: an application layer, a carrier proxy module as claimed in claim 3, a driver layer and a hardware layer; The application layer is connected to the carrier proxy module, the carrier proxy module is connected to the driver layer, and the driver layer is connected to the hardware layer.

Images