A non-unified architecture application communication platform

Abstract

This invention relates to a communication platform for non-uniform architecture applications, belonging to the field of information communication. Relying on a protocol adapter, this invention achieves protocol conversion between non-uniform architecture communication applications through simple configuration, as well as adaptive conversion between audio / video and messaging protocols. An API gateway provides unified service registration management and access control for application-related services in non-uniform architectures. Simultaneously, based on microservice management technology, communication management services and data forwarding services are built to enable connectivity between non-uniform architecture applications for text, media message communication, audio / video multimedia streams, and control information streams. This invention improves the flexibility and scalability of message connectivity between non-uniform architecture applications.

Description

Technical Field

[0001] This invention belongs to the field of information and communication, and specifically relates to a non-unified architecture application communication platform. Background Technology

[0002] With the development of internet and mobile communication technologies, messaging and audio / video communication tools have become an indispensable part of daily life and corporate office work. Currently, various messaging and audio / video application systems based on different implementation methods have emerged, each with its own characteristics in terms of functionality, user groups, and usage scenarios, becoming important tools for users' daily work communication. However, communication application systems with non-unified architectures often use different communication protocols and technical standards, creating "information silos" between these systems and limiting users' communication experience across different application systems. In some large-scale group enterprises, each level of unit has built its own communication application system, but the selected technical routes and products are different, and they are independent of each other, making it impossible to achieve user and message connectivity. For the needs of messaging and audio / video data connectivity between different units, it is necessary to build a new unified architecture communication application system at the higher-level unit and distribute it to the lower-level units, resulting in redundant construction and wasted resources. Alternatively, a unified messaging and audio / video protocol and interface can be specified, requiring each unit's communication application system to be adapted, but this is costly and consumes a lot of human resources. Summary of the Invention

[0003] (a) Technical problems to be solved

[0004] The technical problem this invention aims to solve is how to provide a non-unified architecture application communication platform to address the issue of the inability to connect message and audio / video data between communication application systems with non-unified architectures.

[0005] (II) Technical Solution

[0006] To address the aforementioned technical problems, this invention proposes a non-unified architecture application communication platform, which includes: a communication management service, a user management center, an API gateway, a message forwarding service, and a protocol adapter; the platform provides non-unified architecture application service registration and non-unified architecture application data connectivity functions;

[0007] The message forwarding service is used to bind with non-unified architecture communication application systems, including: the interface center management unit, the node and user relationship information management unit, and the message routing and forwarding unit;

[0008] The communication management service provides functions for non-unified architecture application service registration, node location query service, message forwarding service information management, and node user relationship management, including: non-unified architecture application service registration unit, message forwarding service information management unit, message forwarding service location query unit, and node user relationship management unit;

[0009] API gateway provides a unified entry and exit point for non-unified architecture application system services, communication management services, message forwarding services, user management center, and protocol adapter services accessed in non-unified architecture application communication platforms. It performs authentication and access control on call requests between services, provides traffic auditing and link tracing functions, and provides basic data for the auditing, recording, and analysis of data flow and link quality of non-unified architecture application communication platforms.

[0010] The User Management Center is used to manage and maintain user information of non-unified architecture applications accessing the non-unified architecture application communication platform. After the non-unified architecture application registers with the communication management service, the User Management Center obtains and maintains the user information of the non-unified architecture application system. At the same time, it can connect to the unified user identity authentication system to obtain the user information of personnel for non-unified architecture applications. By maintaining the user information involved in the non-unified architecture application communication platform, the user information is synchronized to the communication management service in a timely manner, and the communication management service distributes the user information.

[0011] Protocol adapters provide protocol analysis and conversion functions, parsing the communication protocols of non-uniform architecture application systems and converting them into a unified communication protocol and data format; at the same time, they convert the data information of the unified communication protocol and data format to the corresponding data format of non-uniform architecture application systems, realizing mutual conversion between the communication protocols of their respective architectures and the unified communication protocol.

[0012] (III) Beneficial Effects

[0013] This invention proposes a non-unified architecture application communication platform. Relying on a protocol adapter, it enables protocol conversion for non-unified architecture communication applications through simple configuration, as well as adaptive conversion between audio / video and messaging protocols. An API gateway provides unified service registration management and access control for non-unified architecture application-related services. Simultaneously, based on microservice management technology, it constructs communication management and data forwarding services to achieve connectivity between non-unified architecture applications for text, media message communication, audio / video multimedia streams, and control message streams. This non-unified architecture application communication platform eliminates the need for deep modification and adaptation of individual non-unified architecture communication application systems; only simple interface files and system integration are required. Deployed in a cloud architecture, the platform is suitable for connectivity between non-unified architecture communication application systems in large-scale, complex network environments.

[0014] This invention proposes a non-unified architecture application communication platform. Relying on microservice management technology, it constructs a non-unified architecture application communication platform to achieve user sharing and message interoperability between non-unified architecture communication application systems. This platform allows for message interoperability and audio / video conferencing data interoperability between non-unified architecture communication application systems in a plug-and-play manner, without requiring protocol modifications. It also provides unified management of communication between non-unified architecture communication application systems, reducing the difficulty of interaction and improving the flexibility and scalability of interoperability. Attached Figure Description

[0015] Figure 1 This invention relates to a non-unified architecture application communication platform technical architecture.

[0016] Figure 2 A flowchart for cross-network communication platforms for applications with non-unified architectures;

[0017] Figure 3 Cloud deployment architecture diagram for non-unified architecture application communication platform;

[0018] Figure 4 This is a business process diagram for a non-unified architecture application communication platform. Detailed Implementation

[0019] To make the objectives, contents, and advantages of the present invention clearer, the specific embodiments of the present invention will be described in further detail below with reference to the accompanying drawings and examples.

[0020] The purpose of this invention is to propose a non-unified architecture application communication platform. By constructing a communication management service and message forwarding service architecture, based on the service bus technology route, and using protocol adapters to adapt and convert message-type and audio / video-type protocols, and deploying it in the cloud, the platform solves the problem of message connectivity between non-unified architecture communication application systems and reduces the connectivity cost between them.

[0021] 1. Non-unified architecture application communication platform technical architecture

[0022] The underlying layer of a non-unified architecture application communication platform is based on basic hardware and software devices such as computing, networking, databases, operating systems, and middleware. It relies on open-source basic service components such as Redis, MongoDB, Nginx, Spring Cloud, Docker, Kafka, Sentinel, Elasticsearch, and Nacos to build platform services including communication management services, user management center, API gateway, message forwarding service, and protocol adapters. This enables the communication of audio / video, text, and control messages, and supports communication between non-unified architecture application systems. The technical architecture of the non-unified architecture application communication platform is as follows: Figure 1 As shown.

[0023] 2. Functions and business processes of non-unified architecture application communication platforms

[0024] 2.1 Functionality of Non-Unified Architecture Application Communication Platform

[0025] like Figure 1 , 2 As shown, a non-unified architecture application communication platform includes: communication management service, user management center, API gateway, message forwarding service, protocol adapter, etc.

[0026] The message forwarding service is used to bind with non-unified architecture communication application systems, including: a central management unit, a node and user relationship information management unit, and a message routing and forwarding unit.

[0027] The interface center management unit is used to keep the message forwarding service list and user information synchronized between the message forwarding service and the communication management service. When the message forwarding service and user relationship information maintained in the communication management service changes, it is updated to each message forwarding service in a timely manner.

[0028] The node and user relationship information management unit is used to maintain a cache list of node and user relationships. When forwarding a message, it first queries the cache list of the message forwarding service to find the message forwarding service where the destination user is located. If the message forwarding service cannot be found in the cache list, it calls the communication management service to query the message forwarding service address information corresponding to the destination user and caches it in the message forwarding service.

[0029] The message routing and forwarding unit is used to send the transmitted data to the destination message forwarding service by calling the message sending interface based on the destination user in the parsed transmitted data and the destination user's message forwarding service location parameters.

[0030] The communication management service provides functions for non-unified architecture application service registration, node location query service, message forwarding service information management, and node user relationship management. It includes: a non-unified architecture application service registration unit, a message forwarding service information management unit, a message forwarding service location query unit, and a node user relationship management unit.

[0031] The non-unified architecture application service registration unit is used to enable non-unified architecture applications to report application type, transmission protocol, interface information, data format, etc. when accessing the non-unified architecture application communication platform. The communication management service is based on the Nacos registration center for service registration.

[0032] The message forwarding service information management unit is used to manage and maintain the service information of non-unified architecture applications, and supports the protocol adapter and message forwarding service to query information of non-unified architecture application services.

[0033] The node location query unit is used to query the corresponding message forwarding service information based on user information. The communication management service maintains a list of relationships between user and message forwarding service information. The message forwarding service can call the message forwarding service address query service to obtain the message forwarding service address information corresponding to the user in a timely manner.

[0034] The User Relationship Management Unit for Non-Unified Architecture Application Systems is used to maintain the list of user and message forwarding service information relationships and to aggregate user and message forwarding service relationship data involved in the non-unified architecture application communication platform.

[0035] API gateways provide a unified entry and exit point for services such as non-unified architecture application systems, communication management services, message forwarding services, user management centers, and protocol adapters accessed in non-unified architecture application communication platforms. They perform authentication and access control on call requests between services, provide functions such as traffic auditing and link tracing, and provide basic data for the auditing, recording, and analysis of data flow and link quality of non-unified architecture application communication platforms.

[0036] The User Management Center is used to manage and maintain user information for non-unified architecture applications accessing the non-unified architecture application communication platform. After a non-unified architecture application registers with the communication management service, the User Management Center obtains and maintains the user information of the non-unified architecture application system. At the same time, it can connect to a unified user identity authentication system to obtain user information for personnel in non-unified architecture applications. By maintaining the user information involved in the non-unified architecture application communication platform, the user information is synchronized to the communication management service in a timely manner, and the communication management service distributes the user information.

[0037] Protocol adapters provide protocol analysis and conversion functions, parsing the communication protocols of messages and audio / video from non-unified architecture communication application systems and converting them into unified communication protocols and data formats. At the same time, they convert the data information of the unified communication protocol and data format to the corresponding data formats of their respective architectures, realizing mutual conversion between communication protocols of non-unified architecture application systems and unified communication protocols.

[0038] like Figure 3 As shown, the non-unified architecture application communication platform of this invention adopts a cloud-edge-device deployment architecture, possessing cloud-edge collaboration and edge autonomy capabilities. The non-unified architecture application communication platform is implemented based on a microservice architecture. Communication management services and message forwarding services provide open service interfaces, supporting data sharing and synchronization between different levels of communication management services. This enables management of the location and user information of message forwarding services at different levels, and facilitates message forwarding service routing and data forwarding across multi-level data centers and edge clouds. The non-unified architecture application communication platform provides interconnectivity services for non-unified architecture applications by deploying in distributed, multi-regional, and multi-scenario environments such as primary data centers, secondary data centers, and edge clouds. For the non-unified architecture application communication platform deployed in the primary data center, data interaction occurs between the primary data center cloud communication gateway and the secondary data center's non-unified architecture application communication platform. The secondary data center's non-unified architecture application communication platform interacts with the edge cloud's non-unified architecture application communication platform through the edge cloud communication gateway. When the connection between the edge cloud and the secondary data center is lost, the non-unified architecture application communication platform can independently provide non-unified architecture application communication services, flexibly adapting to different network environments.

[0039] 2.2 Business Processes of Non-Unified Architecture Application Communication Platform

[0040] The non-unified architecture application communication platform provides functions such as non-unified architecture application service registration and non-unified architecture application data connectivity. Business process relationships are as follows: Figure 4 As shown.

[0041] Business process diagram of non-unified architecture application communication platform as follows Figure 2 ,4 As shown.

[0042] 1) Non-unified architecture applications accessing a non-unified architecture application communication platform

[0043] S11. When a non-unified architecture application accesses a non-unified architecture application communication platform, the non-unified architecture application authenticates with the API gateway of the non-unified architecture application communication platform and obtains authentication information.

[0044] S12. Non-unified architecture applications register with the communication management service and report relevant information about the non-unified architecture application, including the non-unified architecture application category, non-unified architecture application interface information, and message data format information, to the communication management service.

[0045] S13. The communication management service obtains the reported non-unified architecture application category, non-unified architecture application interface information, non-unified architecture application protocol information, message data format and other information, and creates a message forwarding service based on the above content. The message forwarding service creates a protocol adapter service based on the application category, protocol, interface, data format and other information, and pre-sets the above information into the protocol adapter service.

[0046] S14. After a non-unified architecture application is connected, the user information is reported to the user management center. The communication management service calls the user management center to obtain the user data of the currently connected non-unified architecture application, and maintains the information of the currently connected non-unified architecture application, message forwarding service and user relationship data, and distributes the message forwarding service and user relationship data to other message forwarding services.

[0047] 2) Data Interoperability in Non-Unified Architecture Applications

[0048] S21. Non-unified architecture applications send data information through the API gateway, and the API gateway sends the data information to the protocol adapter of the message forwarding service corresponding to this non-unified architecture application.

[0049] S22. The protocol adapter performs data parsing and protocol conversion according to the pre-configuration, and encapsulates the data into a unified data format according to the unified transmission protocol.

[0050] S23. The protocol adapter calls the API gateway to send unified data format information to the message forwarding service corresponding to this non-unified architecture application.

[0051] S24. The message forwarding service queries the message forwarding service list according to the destination user to obtain the message forwarding service location information of the destination user. If the message forwarding service cannot find the destination message forwarding service, it calls the location query service in the communication management service to obtain the message forwarding service location information corresponding to the destination user.

[0052] S25. The message forwarding service calls the API gateway to send information to the message forwarding service where the destination user is located, and sends the data information in a unified format to the protocol adapter corresponding to the destination message forwarding service for data format conversion and data encapsulation.

[0053] S26. The destination user's message forwarding service calls the API gateway to send the data information encapsulated according to the destination non-unified architecture application protocol to the destination non-unified architecture application system service. The non-unified architecture application system service then sends the data information to the corresponding destination user client, thereby completing the data transmission.

[0054] The above is the overall content of a non-unified architecture application communication platform architecture proposed in this invention. The technical route and data flow of the non-unified architecture application communication platform architecture are within the scope of protection of this invention.

[0055] This invention proposes a non-unified architecture application communication platform. Relying on a protocol adapter, it enables protocol conversion between heterogeneous instant messaging systems and adaptive conversion of heterogeneous audio and video protocols through simple configuration. An API gateway provides unified service registration management and access control for related services of non-unified architecture communication application systems. Simultaneously, based on microservice management technology, it constructs communication management services and message forwarding services to achieve connectivity between non-unified architecture communication systems for text, media message communication, audio and video media streams, and control information streams. Using this non-unified architecture application communication platform, no deep modification or adaptation is required for each non-unified architecture communication application system; only simple interface files and system integration are needed. The non-unified architecture application communication platform is deployed in a cloud architecture and is suitable for connectivity between non-unified architecture communication application systems in large-scale, complex network environments.

[0056] This invention proposes a non-unified architecture application communication platform. Relying on microservice management technology, it constructs a non-unified architecture application communication platform to achieve user sharing and message interoperability between non-unified architecture communication application systems. It does not require protocol modification of non-unified architecture communication application systems, and enables message communication and audio / video conferencing between users of non-unified architecture communication application systems in a plug-and-play manner. It also provides unified management of communication between non-unified architecture communication application systems, reduces the difficulty of interaction between non-unified architecture systems, and improves the flexibility and scalability of connectivity between non-unified architecture communication application systems.

[0057] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the technical principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A non-unified architecture application communication platform, characterized in that, The platform includes: communication management service, user management center, API gateway, message forwarding service, and protocol adapter; the platform provides registration of non-unified architecture application services and data communication functions for non-unified architecture applications; The message forwarding service is used to bind with non-uniform architecture applications, including: interfacing with the communication management unit, user relationship information management unit, and message routing and forwarding unit; The communication management service provides functions for non-unified architecture application service registration, relay address query service, message forwarding service information management, and non-unified architecture application user relationship management, including: non-unified architecture application service registration unit, message forwarding service information management unit, message forwarding service location query unit, and node user relationship management unit; API gateway provides a unified entry and exit point for non-unified architecture application system services, communication management services, message forwarding services, user management center, and protocol adapter services accessed in non-unified architecture application communication platforms. It performs authentication and access control on call requests between services, provides traffic auditing and link tracing functions, and provides basic data for the auditing, recording, and analysis of data flow and link quality of non-unified architecture application communication platforms. The User Management Center is used to manage and maintain user information of non-unified architecture applications accessing the non-unified architecture application communication platform. After the non-unified architecture application registers with the communication management service, the User Management Center obtains and maintains the user information of the non-unified architecture application system. At the same time, it can connect to the unified user identity authentication system to obtain the user information of personnel for non-unified architecture applications. By maintaining the user information involved in the non-unified architecture application communication platform, the user information is synchronized to the communication management service in a timely manner, and the communication management service distributes the user information. Protocol adapters provide protocol analysis and conversion functions, parsing the communication protocols of non-uniform architecture application systems and converting them into a unified communication protocol and data format; at the same time, they convert the data information of the unified communication protocol and data format to the corresponding data format of non-uniform architecture application systems, realizing mutual conversion between the communication protocols of their respective architectures and the unified communication protocol.

2. The non-unified architecture application communication platform as described in claim 1, characterized in that, The underlying layer of the non-unified architecture application communication platform is based on computing, network, database, operating system, middleware hardware and software devices. Relying on open source basic service components, it constructs platform services in the non-unified architecture application communication platform to realize the connection of audio and video, text and control information, and support the connection between non-unified architecture application systems.

3. The non-unified architecture application communication platform as described in claim 1, characterized in that, The docking center management unit is used to keep the message forwarding service list and user information synchronized between the message forwarding service and the communication management service. When the message forwarding service and user relationship information maintained in the communication management service changes, it is updated to each message forwarding service in a timely manner. The message forwarding service and user relationship information management unit is used to maintain a cache list of message forwarding services and user relationships. When forwarding a message, it first queries the cache list of the message forwarding service to find the message forwarding service where the destination user is located. If the message forwarding service cannot be found in the cache list, it calls the communication management service to query the location information of the message forwarding service corresponding to the destination user and caches it in the message forwarding service. The message routing and forwarding unit is used to send the transmitted data to the destination message forwarding service by calling the message sending interface based on the destination user in the parsed transmitted data and the destination user's message forwarding service location parameters.

4. The non-unified architecture application communication platform as described in claim 1, characterized in that, The non-unified architecture application service registration unit is used to enable non-unified architecture applications to report application type, transmission protocol, interface information, and data format when accessing the non-unified architecture application communication platform. The communication management service registers services based on the Nacos registration center. The message forwarding service information management unit is used to manage and maintain the service information of non-unified architecture applications, and supports the protocol adapter and message forwarding service to query information of non-unified architecture application services. The message forwarding service address query unit is used to query the corresponding message forwarding service information based on user information. The communication management service maintains a list of relationships between users and message forwarding service information. The message forwarding service can call the node location query service to obtain the location information of the message forwarding service corresponding to the user in a timely manner. The Non-Unified Architecture Application User Relationship Management Unit is used to maintain the list of user and message forwarding service information relationships and to aggregate user and message forwarding service relationship data involved in the communication platform of the entire non-unified architecture application.

5. The non-unified architecture application communication platform as described in any one of claims 1-4, characterized in that, The non-unified architecture application communication platform adopts a cloud-edge-device deployment architecture, and has cloud-edge collaboration and edge autonomy capabilities.

6. The non-unified architecture application communication platform as described in claim 5, characterized in that, The non-unified architecture application communication platform is implemented based on a microservice architecture. The communication management service and message forwarding service provide open service interfaces. Data sharing and synchronization are supported between different levels of communication management services, enabling the management of the location and user information of message forwarding services at different levels, and realizing message forwarding service routing and data forwarding across multi-level data centers and edge nodes.

7. The non-unified architecture application communication platform as described in claim 6, characterized in that, By deploying a non-unified architecture application communication platform in multi-level data centers and edge node environments, it provides interconnection services for non-unified architecture applications.

8. The non-unified architecture application communication platform as described in claim 7, characterized in that, For non-unified architecture application communication platforms deployed in Tier 1 data centers, data interaction occurs between Tier 1 data center cloud communication gateways and Tier 2 data center non-unified architecture application communication platforms. Tier 2 data center non-unified architecture application communication platforms interact with edge cloud non-unified architecture application communication platforms via edge cloud communication gateways. When the connection between edge cloud and Tier 2 data centers is lost, the non-unified architecture application communication platform can independently provide non-unified architecture application communication services, thus flexibly adapting to different network environments to provide non-unified architecture application communication services.

9. The non-unified architecture application communication platform as described in any one of claims 1-4, characterized in that, The steps for non-unified architecture applications to access a non-unified architecture application communication platform are as follows: S11. When a non-unified architecture application accesses the non-unified architecture application communication platform, the non-unified architecture application authenticates with the API gateway of the non-unified architecture application communication platform and obtains authentication information. S12. Non-unified architecture applications register with the communication management service and report relevant information about the non-unified architecture application, including the non-unified architecture application category, non-unified architecture application interface information, and message data format information, to the communication management service. S13. The communication management service obtains the reported non-unified architecture application category, non-unified architecture application interface information, non-unified architecture application protocol information, and message data format information, and creates a message forwarding service based on the above content. The message forwarding service creates a protocol adapter service based on the application category, protocol, interface, and data format information, and pre-sets the above information into the protocol adapter service. S14. After a non-unified architecture application is connected, it reports user information to the user management center. The communication management service calls the user management center to obtain the user data of the currently connected non-unified architecture application, maintains the information of the currently connected non-unified architecture application, message forwarding service and user relationship data, and distributes the message forwarding service and user relationship data to other message forwarding services.

10. The non-unified architecture application communication platform as described in claim 9, characterized in that, Interoperability of data between applications with non-unified architectures includes the following steps: S21. Non-unified architecture applications send data information through the API gateway, and the API gateway sends the data information to the protocol adapter of the message forwarding service corresponding to this non-unified architecture application. S22. The protocol adapter performs data parsing and protocol conversion according to the pre-configuration, and encapsulates the data into a unified data format according to the unified transmission protocol. S23. The protocol adapter calls the API gateway to send unified data format information to the message forwarding service corresponding to this non-unified architecture application. S24. The message forwarding service queries the message forwarding service list according to the destination user to obtain the message forwarding service address information of the destination user. If the message forwarding service cannot find the destination message forwarding service, it calls the address query service in the communication management service to obtain the message forwarding service address information corresponding to the destination user. S25. The message forwarding service calls the API gateway to send information to the message forwarding service where the destination user is located, and sends the data information in a unified format to the protocol adapter corresponding to the destination message forwarding service for data format conversion and data encapsulation. S26. The destination user's message forwarding service calls the API gateway to send the data information encapsulated according to the destination non-unified architecture application protocol to the destination non-unified architecture application system service. The non-unified architecture application system service then sends the data information to the corresponding destination user client, thereby completing the data transmission.

Images