Fusion terminal communication resource allocation method and system based on multi-application collaboration

Abstract

The invention discloses a fusion terminal communication resource allocation method and system based on multi-application collaboration, and is applied to the technical field of Internet of Things communication, and the method comprises the steps: generating a priority identifier of each application program; receiving an external communication request task of the application program, and adding the external communication request task into a queue; sorting the external communication request tasks, combining the external communication request tasks with the same communication path, and updating the queue; the same communication path comprises the same communication frequency band; and packaging the external communication request tasks into communication data frames in sequence according to the updated sequence of the queues, and sending the communication data frames to the outside. A centralized communication manager is introduced, a unified and controlled communication service entry is provided for multiple applications on the upper layer, disordered direct access is changed into ordered indirect access based on requests, and resource conflicts are eliminated fundamentally; and meanwhile, the occupation of a communication frequency band can be reduced under the condition that the communication information amount is not changed.

Description

Technical Field

[0001] The present invention relates to the field of Internet of Things communication technology, and in particular to a method and system for allocating communication resources of a converged terminal based on multi-application collaboration. Background Art

[0002] In current IoT edge computing scenarios, such as "converged terminal" devices, multiple independent applications (APPs) typically run on them. Each APP may need to communicate with external sensor or actuator nodes through the underlying physical communication module (such as LoRa, Zigbee, NB-IoT, etc.). In traditional implementations, each APP has direct and exclusive access to the physical communication module. When an APP uses a LoRa module, it typically takes full control of the module, including configuring channels and frequency bands, managing subnode profiles, and sending and receiving data. If another APP also wants to use the LoRa module, it must wait for the previous APP to release resources, or developers must write complex inter-application coordination logic to avoid conflicts.

[0003] In summary, the existing technology has the following shortcomings: serious resource conflicts and competition: multiple APPs directly and disorderly access the same physical communication node, which is prone to configuration conflicts (such as one APP sets the A band and the other changes it to the B band), data transmission and reception interference, and confusion in the ownership of sub-nodes, resulting in instability or even paralysis of the entire communication system; high degree of application development coupling: the developer of each upper-level APP must be concerned with the specific communication protocol, networking process, heartbeat maintenance and other complex details of the underlying LoRa module, which greatly increases the complexity and workload of application development, and also makes the APP highly coupled with specific hardware and protocol stacks, making it difficult to port and reuse; lack of unified management and security isolation: there is no centralized mechanism to manage sub-node files, allocate network resources and isolate data flows of different APPs. This makes it easy for sub-node files to be lost or modified incorrectly, and a communication failure or abnormal behavior of one app may affect the normal operation of all other apps, lacking security and robustness; poor scalability: every time a new application that needs to use LoRa functions is added, the existing coordination logic needs to be modified, and even all related apps may need to be modified, making the system expansion and maintenance costs extremely high; apps taking turns to seize the communication module can easily cause communication frequency band congestion. Summary of the Invention

[0004] In order to at least overcome the above-mentioned deficiencies in the prior art, the purpose of the present application is to provide a method and system for allocating communication resources of a converged terminal based on multi-application collaboration.

[0005] In a first aspect, an embodiment of the present application provides a method for allocating communication resources of a converged terminal based on multi-application collaboration, including: Prioritizing the applications configured on the target converged terminal to generate a priority identifier for each application; receiving an external communication request task from the application program, and adding the external communication request task to a queue; According to the priority identifier, the external communication request tasks are sorted in the queue from high to low priority, and the external communication request tasks with the same communication path are merged and then updated in the queue; the same communication path includes the same communication frequency band; According to the updated sequence of the queuing queues, the external communication request tasks are sequentially encapsulated into communication data frames and sent to the outside.

[0006] In a possible implementation, the method further includes: receiving a response data frame from an external device in response to the communication data frame; After unpacking the response data frame, the data requested by each application is obtained, and the data is sent to the corresponding application.

[0007] In a possible implementation, merging the external communication request tasks with the same communication path and then updating the queue includes: Merge the external communication request tasks with the same communication path to form a new external communication request task; The priority identifier of the external communication request task with the highest priority before the merger is used as the priority identifier of the new external communication request task, and the sequence of the queues is re-sorted from high to low according to the priority.

[0008] In a possible implementation, encapsulating the external communication request tasks into communication data frames in sequence according to the updated sequence of the queuing queues includes: Select the external communication request task with the highest priority in the current queue as the current task; Arrange all destination addresses of the current task in a preset order to form an address code, and form each task content of the current task in the form of command + content to form a command subcode; Arranging all command subcodes in the preset order to form a command code, and arranging the command code after the address code to form a valid content field of the communication data frame; A frame header and a check segment are generated, and the communication data frame is generated in the order of frame header-effective content field-check segment.

[0009] In a possible implementation, the method further includes: When the external device receives the communication data frame, it extracts the valid content field; If the address code of the valid content field includes the external device, the external device extracts the command subcode corresponding to the external device from the command code according to the position of its own address in the address code and executes the command corresponding to the command subcode.

[0010] In a second aspect, an embodiment of the present application provides a converged terminal communication resource allocation system based on multi-application collaboration, including: Target fusion terminal; A communication manager configured on the target converged terminal; A communication module configured in the target fusion terminal; The communication manager is further configured to: Prioritizing the applications configured on the target converged terminal to generate a priority identifier for each application; receiving an external communication request task from the application program, and adding the external communication request task to a queue; According to the priority identifier, the external communication request tasks are sorted in the queue from high to low priority, and the external communication request tasks with the same communication path are merged and then updated in the queue; the same communication path includes the same communication frequency band; Encapsulating the external communication request tasks into communication data frames in sequence according to the updated sequence of the queuing queues; The communication module is further configured to: send the communication data frame to the outside.

[0011] In a possible implementation, the communication module is further configured to: receiving a response data frame from an external device in response to the communication data frame; The communication manager is further configured to: After unpacking the response data frame, the data requested by each application is obtained, and the data is sent to the corresponding application.

[0012] In a possible implementation, the communication manager is further configured to: Merge the external communication request tasks with the same communication path to form a new external communication request task; The priority identifier of the external communication request task with the highest priority before the merger is used as the priority identifier of the new external communication request task, and the sequence of the queues is re-sorted from high to low according to the priority.

[0013] In a possible implementation, the communication manager is further configured to: Select the external communication request task with the highest priority in the current queue as the current task; Arrange all destination addresses of the current task in a preset order to form an address code, and form each task content of the current task in the form of command + content to form a command subcode; Arranging all command subcodes in the preset order to form a command code, and arranging the command code after the address code to form a valid content field of the communication data frame; A frame header and a check segment are generated, and the communication data frame is generated in the order of frame header-effective content field-check segment.

[0014] In a possible implementation, the external device is also included: The external device is configured as: extracting the valid content field when receiving the communication data frame; If the address code of the valid content field includes the external device, the command subcode corresponding to the external device is extracted from the command code according to the position of its own address in the address code, and the command corresponding to the command subcode is executed.

[0015] Compared with the prior art, the present invention has the following advantages and beneficial effects: The present invention is based on a multi-application collaborative converged terminal communication resource allocation method and system. By introducing a centralized communication manager, it provides a unified and controlled communication service entrance for multiple upper-layer applications, transforming disordered direct access into orderly, request-based indirect access, and fundamentally eliminating resource conflicts. At the same time, it can also reduce the communication frequency band occupancy without changing the amount of communication information. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings described herein are used to provide a further understanding of the embodiments of the present invention, constitute a part of this application, and do not constitute a limitation of the embodiments of the present invention. In the drawings: Figure 1 This is a schematic diagram of the method steps of an embodiment of the present application. DETAILED DESCRIPTION

[0017] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of illustration and description and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate the operations implemented according to some embodiments of the embodiments of the present application. It should be understood that the operations of the flowcharts can be implemented out of sequence, and steps without logical context can be reversed or implemented simultaneously. In addition, those skilled in the art, under the guidance of the contents of this application, can add one or more other operations to the flowchart, or remove one or more operations from the flowchart.

[0018] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the claimed application, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of the present application.

[0019] Please refer to Figure 1 , which is a flow chart of the method for allocating communication resources of a fusion terminal based on multi-application collaboration provided by an embodiment of the present invention. Furthermore, the method for allocating communication resources of a fusion terminal based on multi-application collaboration may specifically include the contents described in the following steps S1 to S4.

[0020] S1: Prioritize the applications configured on the target converged terminal and generate a priority identifier for each application; S2: receiving an external communication request task from the application, and adding the external communication request task to a queue; S3: sorting the external communication request tasks in the queue from high to low priority according to the priority identifier, and merging the external communication request tasks with the same communication path and updating the queue; the same communication path includes the same communication frequency band; S4: encapsulating the external communication request tasks into communication data frames in sequence according to the updated sequence of the queuing queues and sending them to the outside.

[0021] When implementing the embodiment of the present application, a communication manager needs to be configured in the target fusion terminal, which needs to aggregate the communication requests of various applications of the fusion terminal and sort and encode the communication requests by priority. This can effectively avoid the system stability and robustness risks brought by a large number of applications preempting the communication module. Among them, it is necessary to prioritize the applications first. It can be sorted according to the urgency of the communication tasks provided by the applications. The embodiment of the present application does not make many restrictions. The priority level of the application can be seen through the generated priority identifier. If the priority identifier is a number, it can be carried out in the form of 01, 02, or 03, with 01 being the highest priority and 03 being the lowest priority.

[0022] In an embodiment of the present application, when the communication manager receives an external communication request task from an application, it can sort these tasks in a queue by priority identifier. It should be understood that the external communication request task needs to include the destination address of the requested communication, the command of the request, and the content of the request. In order to reduce the signal congestion in the frequency band caused by the excessive number of data frames brought about by the number of communication request tasks of different applications and the data transmission and reception interference caused by too frequent frequency band switching, the embodiment of the present application adopts a task merging method to reduce the tasks that need to be sent, wherein it is necessary to first find at least two tasks with the same communication path to merge, wherein one of the situations in which the communication path is the same refers to the same communication frequency band, and it can also be the same path or the same destination address in the topological network. Generally speaking, the same path and the same destination address in the topological network will be reflected in the signal sending end as the same communication frequency band, unless the transceiver has a frequency hopping design. After the merger is completed, the external communication request tasks can be encapsulated and sent in order according to the priority according to the sequence of the updated queue.

[0023] This embodiment addresses conflicts and competition for physical communication resources by introducing a centralized communication manager that provides a unified, controlled communication service portal for multiple upper-layer applications. This transforms unordered direct access into ordered, request-based indirect access, fundamentally eliminating resource conflicts. It also addresses the tight coupling between upper-layer applications and underlying hardware by encapsulating complex underlying operations such as LoRa networking, data transmission and reception, and link maintenance within the communication manager, providing upper-layer applications with standardized, high-level APIs (such as JSON-formatted topic subscription and publishing). Upper-layer application developers need not worry about underlying details; they can simply call simple APIs to achieve communication, effectively decoupling software and hardware. It also addresses the lack of unified management and security isolation by establishing a centralized subnode profile database, which is maintained by the communication manager. Each application can only operate on the subnode profiles under its name, achieving logical isolation between applications. Furthermore, a priority mechanism is introduced to schedule communication tasks for different applications, ensuring communication quality for critical services. It also addresses poor system scalability by providing a standardized application registration and profile management interface. New applications only need to follow this interface specification to seamlessly connect to the management system without modifying other applications, achieving plug-and-play application expansion capabilities.

[0024] In a possible implementation, the method further includes: receiving a response data frame from an external device in response to the communication data frame; After unpacking the response data frame, the data requested by each application is obtained, and the data is sent to the corresponding application.

[0025] When the embodiment of the present application is implemented, since the communication request tasks with the same communication path will be encapsulated in the same communication data frame during the data sending phase on the fusion terminal side, the same response data frame received by the same external device may correspond to commands issued by two or more applications, so when feedback is given, the corresponding data will also be fed back in the response data frame; at this time, the communication manager needs to split these data and forward the data to the corresponding application.

[0026] In a possible implementation, merging the external communication request tasks with the same communication path and then updating the queue includes: Merge the external communication request tasks with the same communication path to form a new external communication request task; The priority identifier of the external communication request task with the highest priority before the merger is used as the priority identifier of the new external communication request task, and the sequence of the queues is re-sorted from high to low according to the priority.

[0027] During implementation of the present application, when merging external communication request tasks, in order to ensure that the originally high-priority tasks maintain the same priority, the highest priority identifier of the merged external communication request task is used as the priority identifier of the subsequent task, and then the queue is reordered. It should be understood that merging and reordering tasks is a dynamic process, and in actual operation, corresponding cycles can be set to perform these operations.

[0028] In a possible implementation, encapsulating the external communication request tasks into communication data frames in sequence according to the updated sequence of the queuing queues includes: Select the external communication request task with the highest priority in the current queue as the current task; Arrange all destination addresses of the current task in a preset order to form an address code, and form each task content of the current task in the form of command + content to form a command subcode; Arranging all command subcodes in the preset order to form a command code, and arranging the command code after the address code to form a valid content field of the communication data frame; A frame header and a check segment are generated, and the communication data frame is generated in the order of frame header-effective content field-check segment.

[0029] When implementing the embodiment of the present application, a special encapsulation method is used when encapsulating data frames, so that in the case of multiple destination addresses and / or multiple commands, the external device that receives the communication data frame can accurately identify the information and send the correct information for recognition by the application of the fusion terminal.

[0030] In an embodiment of the present application, there may be more than one destination address for the current task. The reason is that there may be multiple external devices in the same frequency band, and each external device must correspond to a unique destination address. Therefore, all destination addresses need to be arranged in a certain predetermined order to form an address code. It should be understood that the number of bits corresponding to the destination address when encoding must be fixed, so when the external device receives the communication data frame, the number and value of the destination address can be determined by the number of bits.

[0031] In an embodiment of the present application, the current task will also include multiple commands that need to be executed. There will be two situations. The first is that there is only one destination address but multiple commands; the second is that there are multiple destination addresses and multiple commands at the same time; during actual encoding, a task issued by an application often corresponds to only one command, and multiple command applications will be divided into multiple tasks for sending; so for the first situation, it is generally composed of tasks initiated by multiple applications to the same destination address merged; and the second situation is generally composed of tasks initiated by multiple applications to different destination addresses merged, and these destination addresses will be in the same frequency band.

[0032] Based on the above process, an embodiment of the present application provides a method for generating command codes, wherein each task content needs to form a command subcode in the form of command + content. The command can be used as an instruction to inform the external device that an operation needs to be performed, and a specific separator can be added to serve as a separator between different command codes; the command subcodes are then sorted in the same sorting method as the address code to form a command code. At this time, the address code is placed at the head of the code, and the command code is placed at the end of the code to form a valid content field.

[0033] In the embodiments of the present application, a frame header and a check segment are added to the payload field to form a complete communication data frame. It should be understood that different communication modes may have different corresponding frame structures. As long as the functions of the frame portions are the same as those of the frame header, payload field, and check segment, they can be considered the same parts; the embodiments of the present application do not impose any restrictions.

[0034] For example, a substation is equipped with multiple leakage indicators on the user side, and a target converged terminal is installed in the substation's power distribution room. These leakage indicators and the target converged terminal are networked via LoRa communication. Two applications, APP1 and APP2, in the target converged terminal issue external communication request tasks, which are received by the communication manager. The communication manager then inserts these external communication request tasks into the queue and queries the priority tags of APP1 and APP2. The query results show that APP1 has a priority tag of 1 and APP2 has a priority tag of 8. At this time, APP1's external communication request task is placed at the head of the queue, and APP2's external communication request task is placed at the end of the queue.

[0035] The communication manager begins to merge the external communication request tasks with the same communication path in the queue, and finds that the external communication request task of APP1 is to send a time synchronization maintenance instruction to leakage indicator A, while the external communication request task of APP2 is to send a request instruction for phase B leakage data to leakage indicator B. At the same time, leakage indicator A and leakage indicator B are in the same communication frequency band of 480Mhz.

[0036] The communication manager executes the task merging instruction, merges the external communication request tasks of APP1 and APP2 into the same external communication request task, and assigns the priority identifier 1 of APP1 to the task, so that the task continues to remain at the head of the queue.

[0037] When encoding the external communication request task, the communication manager obtains the destination address of APP1's external communication request task, namely, the address 08 of leakage indicator A, the maintenance command 55, and the time synchronization content 03. It also obtains the destination address of APP2's external communication request task, namely, the address 11 of leakage indicator B, the data request command 01, and the request for phase B content 02. The communication manager encodes these contents, using the default priority encoding order. The address code is 08 11. The command subcode of APP1's external communication request task is FF 55 03, and the command subcode of APP2's external communication request task is FF 01 02. FF is a command identification code, which can be added to the header of each command subcode. The resulting valid content field is 08 11 FF 55 03 FF 01 02. Add a frame header. In this embodiment of the present application, the frame header consists of two parts. The first part is the dominant header, which indicates the number of bytes in the payload field, and the last part is the dominant header identifier. Therefore, the frame header format is 08 48 00. Add a check segment. This embodiment of the present application uses CRC check. After performing a CRC check on the payload field, the check code is E8 8A. The assembled frame according to the protocol is 08 48 00 08 11 FF 55 03 FF01 02 E88A; where 08 48 00 is in the PHY Header position; 08 11 FF 55 03 FF 01 02 is in the Payload position; and E88A is in the CRC position. There is a significant difference between the arrangement of the Payload position in the embodiment of the present application and the arrangement of conventional LoRa communication. The main difference is that all destination addresses are displayed in the header of the Payload, and the command is identified by the FF command identification code for command identification. Since the encoding order of the address code and the valid content field is consistent, the receiving device can easily find the corresponding command to be executed; at the same time, since the data of LoRa communication is often stored and identified through the FIFO register, when encoding is performed in the manner of the embodiment of the present application, the receiving device can know whether it should respond to this section of the code after receiving only a few bytes of the Payload header, which effectively reduces the communication delay in the case of multi-task and multi-target encoding.

[0038] In a possible implementation, the method further includes: When the external device receives the communication data frame, it extracts the valid content field; If the address code of the valid content field includes the external device, the external device extracts the command subcode corresponding to the external device from the command code according to the position of its own address in the address code and executes the command corresponding to the command subcode.

[0039] When the embodiment of the present application is implemented, leakage indicator A, leakage indicator B and leakage indicator C are all in 480Mhz, so they will simultaneously receive the code 08 48 00 08 11 FF 55 03 FF 01 02 E8 8A in the above embodiment; leakage indicator A, leakage indicator B and leakage indicator C will respectively unpack and identify the address code 0811 through the first FF code. At this time, leakage indicator C finds that it is not in the address code, and it will discard the code; after receiving the code, leakage indicator A and leakage indicator B find that they are in the address code. At this time, the position of the Payload part and the position of the CRC are determined according to the dominant header of the frame header. After verifying the Payload through CRC, it is determined that the received content is correct.

[0040] If leakage indicator A finds that it is in the first position of the address code, it can identify its command subcode as 55 03 based on the command identification code FF, and then it sends its current time data to the target fusion terminal; if leakage indicator B finds that it is in the second position of the address code, it can identify its command subcode as 01 02 based on the command identification code FF, and then it sends the B-phase leakage data detected by itself to the target fusion terminal.

[0041] Based on the same inventive concept, the embodiment of the present application also provides a converged terminal communication resource allocation system based on multi-application collaboration, including: Target fusion terminal; A communication manager configured on the target converged terminal; A communication module configured in the target fusion terminal; The communication manager is further configured to: Prioritizing the applications configured on the target converged terminal to generate a priority identifier for each application; receiving an external communication request task from the application program, and adding the external communication request task to a queue; According to the priority identifier, the external communication request tasks are sorted in the queue from high to low priority, and the external communication request tasks with the same communication path are merged and then updated in the queue; the same communication path includes the same communication frequency band; Encapsulating the external communication request tasks into communication data frames in sequence according to the updated sequence of the queuing queues; The communication module is further configured to: send the communication data frame to the outside.

[0042] In a possible implementation, the communication module is further configured to: receiving a response data frame from an external device in response to the communication data frame; The communication manager is further configured to: After unpacking the response data frame, the data requested by each application is obtained, and the data is sent to the corresponding application.

[0043] In a possible implementation, the communication manager is further configured to: Merge the external communication request tasks with the same communication path to form a new external communication request task; The priority identifier of the external communication request task with the highest priority before the merger is used as the priority identifier of the new external communication request task, and the sequence of the queues is re-sorted from high to low according to the priority.

[0044] In a possible implementation, the communication manager is further configured to: Select the external communication request task with the highest priority in the current queue as the current task; Arrange all destination addresses of the current task in a preset order to form an address code, and form each task content of the current task in the form of command + content to form a command subcode; Arranging all command subcodes in the preset order to form a command code, and arranging the command code after the address code to form a valid content field of the communication data frame; A frame header and a check segment are generated, and the communication data frame is generated in the order of frame header-effective content field-check segment.

[0045] In a possible implementation, the external device is also included: The external device is configured as: extracting the valid content field when receiving the communication data frame; If the address code of the valid content field includes the external device, the command subcode corresponding to the external device is extracted from the command code according to the position of its own address in the address code, and the command corresponding to the command subcode is executed.

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

[0047] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.

[0048] The units described as separate components may or may not be physically separated. As units, it is obvious that a person of ordinary skill in the art can realize 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 terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0049] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

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

[0051] The specific implementation methods described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific implementation method of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for allocating communication resources of a converged terminal based on multi-application collaboration, characterized in that: include: Prioritizing the applications configured on the target converged terminal to generate a priority identifier for each application; receiving an external communication request task from the application program, and adding the external communication request task to a queue; According to the priority identifier, the external communication request tasks are sorted in the queue from high to low priority, and the external communication request tasks with the same communication path are merged and then updated in the queue; the same communication path includes the same communication frequency band; According to the updated sequence of the queuing queues, the external communication request tasks are sequentially encapsulated into communication data frames and sent to the outside.

2. The method for allocating communication resources of a converged terminal based on multi-application collaboration according to claim 1, characterized in that: Also includes: receiving a response data frame from an external device in response to the communication data frame; After unpacking the response data frame, the data requested by each application is obtained, and the data is sent to the corresponding application.

3. The method for allocating communication resources of a converged terminal based on multi-application collaboration according to claim 1, characterized in that: Merging the external communication request tasks with the same communication path and then updating the queue includes: Merge the external communication request tasks with the same communication path to form a new external communication request task; The priority identifier of the external communication request task with the highest priority before the merger is used as the priority identifier of the new external communication request task, and the sequence of the queues is re-sorted from high to low according to the priority.

4. The method for allocating communication resources of a converged terminal based on multi-application collaboration according to claim 1, characterized in that: Encapsulating the external communication request tasks into communication data frames in sequence according to the updated queue sequence includes: Select the external communication request task with the highest priority in the current queue as the current task; Arrange all destination addresses of the current task in a preset order to form an address code, and form each task content of the current task in the form of command + content to form a command subcode; Arranging all command subcodes in the preset order to form a command code, and arranging the command code after the address code to form a valid content field of the communication data frame; A frame header and a check segment are generated, and the communication data frame is generated in the order of frame header-effective content field-check segment.

5. The method for allocating communication resources of a converged terminal based on multi-application collaboration according to claim 4, characterized in that: Also includes: When the external device receives the communication data frame, it extracts the valid content field; If the address code of the valid content field includes the external device, the external device extracts the command subcode corresponding to the external device from the command code according to the position of its own address in the address code and executes the command corresponding to the command subcode.

6. A converged terminal communication resource allocation system based on multi-application collaboration, characterized in that: include: Target fusion terminal; A communication manager configured on the target converged terminal; A communication module configured in the target fusion terminal; The communication manager is further configured to: Prioritizing the applications configured on the target converged terminal to generate a priority identifier for each application; receiving an external communication request task from the application program, and adding the external communication request task to a queue; According to the priority identifier, the external communication request tasks are sorted in the queue from high to low priority, and the external communication request tasks with the same communication path are merged and then updated in the queue; the same communication path includes the same communication frequency band; Encapsulating the external communication request tasks into communication data frames in sequence according to the updated sequence of the queuing queues; The communication module is further configured to: send the communication data frame to the outside.

7. The multi-application collaboration-based converged terminal communication resource allocation system according to claim 6, characterized in that: The communication module is further configured to: receiving a response data frame from an external device in response to the communication data frame; The communication manager is further configured to: After unpacking the response data frame, the data requested by each application is obtained, and the data is sent to the corresponding application.

8. The multi-application collaboration-based converged terminal communication resource allocation system according to claim 6, characterized in that: The communication manager is further configured to: Merge the external communication request tasks with the same communication path to form a new external communication request task; The priority identifier of the external communication request task with the highest priority before the merger is used as the priority identifier of the new external communication request task, and the sequence of the queues is re-sorted from high to low according to the priority.

9. The multi-application collaboration-based converged terminal communication resource allocation system according to claim 6, characterized in that: The communication manager is further configured to: Select the external communication request task with the highest priority in the current queue as the current task; Arrange all destination addresses of the current task in a preset order to form an address code, and form each task content of the current task in the form of command + content to form a command subcode; Arranging all command subcodes in the preset order to form a command code, and arranging the command code after the address code to form a valid content field of the communication data frame; A frame header and a check segment are generated, and the communication data frame is generated in the order of frame header-effective content field-check segment.

10. The multi-application collaboration-based converged terminal communication resource allocation system according to claim 9, characterized in that: Also includes external devices: The external device is configured as: extracting the valid content field when receiving the communication data frame; If the address code of the valid content field includes the external device, the command subcode corresponding to the external device is extracted from the command code according to the position of its own address in the address code, and the command corresponding to the command subcode is executed.

Images