CN113867988A

CN113867988A - Universal remote communication calling architecture and method

Info

Publication number: CN113867988A
Application number: CN202111155629.XA
Authority: CN
Inventors: 周卫
Original assignee: Spreadtrum Communications Shenzhen Co ltd
Current assignee: Spreadtrum Communications Shenzhen Co ltd
Priority date: 2021-09-29
Filing date: 2021-09-29
Publication date: 2021-12-31

Abstract

A universal telecommunications invocation architecture and method, the architecture comprising: the remote procedure register comprises an RPC kernel, an IPC interface mapping module and an operating system packaging module; the operating system packaging module is used for packaging different types of operating system interfaces into a uniform interface so as to provide an RTOS standard interface for the RPC kernel; the IPC interface mapping module is used for packaging the IPC object into a modular structure and establishing a corresponding relation between an RPC kernel and the IPC object; and the RPC kernel is used for realizing communication among different operating systems according to the corresponding relation between the RPC kernel and the IPC object established by the IPC interface mapping module and the RTOS standard interface provided by the operating system packaging module. By using the scheme of the invention, the dependence of the remotely called communication flow code on the physical communication link and the RTOS can be reduced, so that the method can be quickly adapted to various different product forms.

Description

Universal remote communication calling architecture and method

Technical Field

The invention relates to the technical field of communication, in particular to a universal remote communication calling architecture and a universal remote communication calling method.

Background

In an existing remote call implementation scheme, an inter-core communication remote call code has strong dependency on a diversity of a bottom layer physical communication link and an RTOS (Real Time Operation System), and if bottom layer communication is CMUX (Connection Multiplexing), an API (Application Programming Interface) function of the CMUX is called; if the bottom layer communication is UART (Universal Asynchronous Receiver Transmitter), the API function of the UART is called; for another example, when the RTOS is rthread, an API function of the RTOS is called. Because the interfaces have differences, when the inter-core communication flow is written, software codes adaptive to the application environment need to be written, and the dependency relationship not only makes the codes under different application environments not universal and poor in maintainability, but also brings impact to the portability, reliability and the like of the codes.

Disclosure of Invention

The embodiment of the invention provides a universal remote communication calling architecture and a universal remote communication calling method, which are used for reducing the dependency of a remotely called communication flow code on a physical communication link and an RTOS (real time operating system), so that the remote communication calling architecture and the method can be quickly adapted to various different product forms.

Therefore, the embodiment of the invention provides the following technical scheme:

the embodiment of the invention provides a universal remote communication calling architecture, which comprises: the remote procedure register comprises an RPC kernel, an IPC interface mapping module and an operating system packaging module;

the operating system packaging module is used for packaging different types of operating system interfaces into a unified interface so as to provide an RTOS standard interface for the RPC kernel;

the IPC interface mapping module is used for packaging the IPC object into a modular structure and establishing a corresponding relation between an RPC kernel and the IPC object;

and the RPC kernel is used for realizing communication among different operating systems according to the corresponding relation between the RPC kernel and the IPC object established by the IPC interface mapping module and the RTOS standard interface provided by the operating system packaging module.

Optionally, the IPC interface mapping module establishes a correspondence between the RPC kernel and the IPC object through a pointer.

Optionally, the IPC object includes any one of: CMUX, SOCKET, SIPC, UART, USB, SPI.

Optionally, the operating system comprises any one of: MOCOR, RT-Thread, WIN 32.

Optionally, the RPC kernel includes any one or more of the following methods: opening a window, reading, writing, input and output control and releasing.

The embodiment of the invention also provides a universal remote communication calling method, which comprises the following steps:

packaging different types of operating system interfaces into a uniform interface so as to provide an RTOS standard interface for the RPC kernel;

packaging the IPC object into a modular structure, and establishing a corresponding relation between an RPC kernel and the IPC object;

and realizing communication among different operating systems according to the corresponding relation between the RPC kernel and the IPC object and the RTOS standard interface.

Optionally, the IPC interface establishes a correspondence between the RPC kernel and the IPC object through a pointer.

An embodiment of the present invention further provides a computer-readable storage medium, which is a non-volatile storage medium or a non-transitory storage medium, and on which a computer program is stored, where the computer program is executed by a processor to perform the steps of the above method.

The embodiment of the present invention further provides an electronic device, which includes a memory and a processor, where the memory stores a computer program that can be executed on the processor, and the processor executes the steps of the method when executing the computer program.

According to the universal remote communication calling framework and the universal remote communication calling method, the operating system packaging modules package different types of operating system interfaces into a unified interface to provide an RTOS standard interface for the RPC kernel, the IPC object is packaged into a modular structure through the IPC interface mapping module, the corresponding relation between the RPC kernel and the IPC object is established, and the RPC kernel realizes communication among different operating systems by using the corresponding relation between the RPC kernel and the IPC object and the RTOS standard interface, so that a core code of the RPC kernel can be suitable for any combination of various chips, IPCs and RTOSs, and is quickly suitable for product forms needing IPC communication. Even if the IPC object and/or the bottom operating system are changed, the RPC kernel code does not need to be modified, and the product transplantation work can be well completed only by changing and replacing corresponding components and modules. The product can be transplanted to different chip modules and different RTOS systems quickly and conveniently in different hardware environments.

Drawings

FIG. 1 is a block diagram of a generic telecommunications invocation architecture in accordance with an embodiment of the present invention;

FIG. 2 is a diagram illustrating the software directory structure of the RPC kernel in an embodiment of the present invention;

fig. 3 is a flow chart of a generic telecommunications invocation method of an embodiment of the present invention.

Detailed Description

In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in detail below.

RPC is a communication technology used by programs and processes running between networked computers, and the whole process of RPC involves four classes of objects: the system comprises a client, a client agent, a server and a server agent. RPC requires that a calling interface and a transmission format (such as JSON, Xml and the like) are defined between a client and a server, and when the client calls the interface, a proxy object of the client is responsible for carrying out format conversion on called parameters (including information such as called function names and parameters) so as to enable the called parameters to conform to the defined transmission format and transmit the called parameters to the server through a network. And after the data is transmitted to the server, the server proxy object is subjected to format decoding to obtain a called interface and parameters, and finally a corresponding method of the server object is called to obtain a result and returns the result to the client.

In the prior art, the communication flow codes of RPC usually depend on specific RTOS and physical communication links, that is, the RPC core codes based on different RTOS and communication interfaces are different, so that they cannot be used in different hardware environments, and once the hardware environment is adjusted, the codes need to be modified again. Therefore, the embodiment of the invention provides a universal remote communication calling architecture and a universal remote communication calling method, when a remote call is used, a communication flow code is not influenced by changes of a physical communication link and an RTOS, and the consistency of the communication flow code can be kept no matter what the physical communication link and the RTOS are.

Fig. 1 is a schematic structural diagram of a generic remote call architecture according to an embodiment of the present invention.

The generic telecommunications invocation architecture includes: the IPC interface comprises an RPC kernel, an IPC interface mapping module and an operating system encapsulation module. Wherein:

the operating system encapsulation module is used for encapsulating different types of operating system interfaces into a unified interface so as to provide an RTOS standard interface for the RPC kernel, namely, the encapsulated unified interface is used as the RTOS standard interface;

the IPC interface mapping module is used for packaging the IPC object into a modular structure and establishing a corresponding relation between the RPC kernel and the IPC object;

the RPC kernel is used for realizing the communication between different operating systems according to the corresponding relation between the RPC kernel and the IPC object established by the IPC interface mapping module and the RTOS standard interface provided by the operating system packaging module.

The universal remote communication calling framework provided by the embodiment of the invention adopts a modular design to carry out standardized modular design on Application Program Interfaces (API) of IPC and RTOS, and the code of a core framework is not changed. The entire universal telecommunications call system is divided into several modules that can be combined. The method is suitable for any combination of various chips, various IPCs and various RTOSs, and is quickly suitable for various IPC communication product forms.

The operating system encapsulation module provides an RTOS standard interface for the RPC kernel, encapsulates the operating interfaces of the operating systems into a uniform interface aiming at different operating systems, such as MOCOR, RT-Thread, WIN32 and the like, and enables the RPC kernel to be realized by adopting the same code aiming at different operating systems.

For example, a thread generic interface is created, the implementation is different in different RTOSs, and the functions are the same, and the operating system encapsulation module can provide an RTOS standard interface in the following form:

int rpc_pthread_create(rpc_pthread_t*tidp,const rpc_pthread_pthread_attr_t*attr,(void*)(*start_rtn)(void*),void*arg)

the code is a function that abstracts the RPC into a uniform created thread, and its function is to create a thread, i.e., to determine the entry point to call the function of the thread. After the thread is created, the associated thread function can begin to run.

Accordingly, the implementation in the RT-Thread system is as follows:

accordingly, the implementation in the WIN32 system is as follows:

accordingly, the implementation in other RTOS systems is as follows:

the bold face portions are the specific code of the various RTOS created threads, which may vary due to the different operating systems. After the scheme of the embodiment of the invention is utilized, the RPC kernel is packaged into a uniform interface, so that the RPC kernel does not need to be concerned about which specific operating system the RTOS is, and the universality of the RPC kernel is improved.

In the embodiment of the present invention, the IPC objects may be, for example, but not limited to, the following: CMUX, SOCKET, SIPC (shared Inter-Processor Comm), UART (Universal Asynchronous Receiver/Transmitter), USB (Universal Serial Bus), SPI (Serial Peripheral Interface). CMUX is a serial multiplexing protocol that enables a serial interface to transmit data to four different client applications; socks are abstractions of endpoints that communicate bi-directionally between application processes on different hosts in a network. One socket is one end of process communication on the network, and provides a mechanism for the application layer process to exchange data by using a network protocol; SIPC is an interprocess communication mechanism based on a Spreadtrum multi-processor system; CMUX converts data to be transmitted between serial communication and parallel communication, and transmits each character of the transmission data bit by bit; the USB is a serial port bus standard and is also a technical specification of an input/output interface, and is widely applied to information communication products such as personal computers, mobile equipment and the like; SPI is a high-speed, full-duplex, synchronous communication bus.

For these different IPC objects, the IPC interface mapping module encapsulates the IPC objects into a modular structure, and establishes a corresponding relationship between the RPC kernel and the IPC objects, for example, the corresponding relationship between the RPC kernel and the IPC objects can be established by using a pointer, so that the corresponding IPC interface can be used by the RPC kernel according to the corresponding relationship.

The corresponding relation between the RPC kernel and the IPC object is established by using the pointer as follows:

in the embodiment of the present invention, the RPC kernel may implement various methods of the existing RPC, such as but not limited to any one or more of the following methods: open window, read, write, ioctl, release, etc.

Taking write as an example, it needs to send the specified content and length to the opposite end, and the opposite end receives it to achieve the purpose, if the underlying drivers are not consistent, such as UART, USB, SPI, socket, etc., the called interface and the internal implementation mode are different, but they all have similar functions. The scheme of the invention aims at different interfaces and unifies the same input and output modes, such as the functions of writing equipment, the specific equipment needing to be indicated, a data buffer needing to be written, the length of writing, the state of returning to writing and the like.

In the following, UART/socket writing devices are taken as examples, respectively, and the interfaces thereof are the same, and the implementation manners are different, specifically as follows:

implementation of/write UART device

int write(int ipc,char*buf,int len)

{

V/calling the UART's associated write API to implement, write successfully return the length of content that write succeeded, write fail return-1

}

Implementation of/write socket device

int write(int ipc,char*buf,int len)

{

v/Call socket's associated write API to implement, write successfully return write successful content length, write fail return-1

}

Based on the universal remote communication call architecture provided by the embodiment of the invention, the software directory structure of the RPC kernel is shown in FIG. 2 and comprises the RPC kernel, an RTOS adaptation layer and an IPC adaptation layer, and the RPC kernel can be kept unchanged no matter how the IPC object is changed and based on what operating system through the hierarchical structure.

The scheme of the invention provides a registration mechanism, and different IPC components are unified with an interface standard for scanning registration processing when the system is started.

The registration mechanism is to form an object from connection information related to a CP (Content Processor) when an AP (Application Processor) needs to connect to the CP using an RPC, and place the object in a management linked list of the RPC. When a plurality of APs are connected to a CP, a plurality of IPC objects need to be registered. The specific connection information is put in a structure (ipc _ operations) in advance, after the registration is completed, the RPC kernel calls an open pointer to indicate that the connection with the opposite-end CP is established, and then the read/write operation can be carried out through the pointer to execute the sending and receiving processing of the AP and the CP.

Correspondingly, an embodiment of the present invention further provides a universal remote communication invoking method, as shown in fig. 3, which is a flowchart of the method, and includes the following steps:

step 301, packaging different types of operating system interfaces into a unified interface to provide an RTOS standard interface for the RPC kernel;

step 302, packaging the IPC object into a modular structure, and establishing a corresponding relation between an RPC kernel and the IPC object;

and 303, realizing communication among different operating systems according to the corresponding relation between the RPC kernel and the IPC object and the RTOS standard interface.

It should be noted that, in this embodiment, the sequence numbers of the respective steps do not represent a limitation on the execution order of the respective steps.

According to the universal remote communication calling method provided by the embodiment of the invention, different types of operating system interfaces are packaged into a unified interface to provide an RTOS standard interface for the RPC kernel, the IPC object is packaged into a modular structure, the corresponding relation between the RPC kernel and the IPC object is established, and the RPC kernel realizes communication among different operating systems by using the corresponding relation between the RPC kernel and the IPC object and the RTOS standard interface, so that a core code of the RPC kernel can be suitable for any combination of various chips, various IPCs and various RTOSs, and can be quickly adapted to product forms needing various IPC communication. Even if the IPC object and/or the bottom operating system are changed, the RPC kernel code does not need to be modified, and the product transplantation work can be well completed only by changing and replacing corresponding components and modules. The product can be transplanted to different chip modules and different RTOS systems quickly and conveniently in different hardware environments.

In a specific implementation, the generic remote communication invocation architecture may be applied to a Chip in a network device, such as a System-On-a-Chip (SoC), a baseband Chip, a Chip module, and the like.

In a specific implementation, each module/unit included in each apparatus and product described in the foregoing embodiments may be a software module/unit, may also be a hardware module/unit, or may also be a part of a software module/unit and a part of a hardware module/unit.

For example, for each device or product applied to or integrated into a chip, each module/unit included in the device or product may be implemented by hardware such as a circuit, or at least a part of the module/unit may be implemented by a software program running on a processor integrated within the chip, and the rest (if any) part of the module/unit may be implemented by hardware such as a circuit; for each device or product applied to or integrated with the chip module, each module/unit included in the device or product may be implemented by using hardware such as a circuit, and different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components of the chip module, or at least some of the modules/units may be implemented by using a software program running on a processor integrated within the chip module, and the rest (if any) of the modules/units may be implemented by using hardware such as a circuit; for each device and product applied to or integrated in the terminal, each module/unit included in the device and product may be implemented by using hardware such as a circuit, and different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components in the terminal, or at least part of the modules/units may be implemented by using a software program running on a processor integrated in the terminal, and the rest (if any) part of the modules/units may be implemented by using hardware such as a circuit.

An embodiment of the present invention further provides a computer-readable storage medium, which is a non-volatile storage medium or a non-transitory storage medium, and a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program performs the steps of the method provided in the embodiment corresponding to fig. 3.

The embodiment of the present invention further provides another generic remote communication invocation architecture, which includes a memory and a processor, where the memory stores a computer program that can be executed on the processor, and the processor executes the steps of the method provided by the embodiment corresponding to fig. 3 when executing the computer program.

An embodiment of the present invention further provides an electronic device, which includes a memory and a processor, where the memory stores a computer program that can be executed on the processor, and the processor executes the steps of the method provided in the embodiment corresponding to fig. 3 when executing the computer program.

In the embodiments provided in the present invention, it should be understood that the disclosed method, apparatus and system can be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative; for example, the division of the unit is only a logic function division, and there may be another division manner in actual implementation; for example, various elements or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be physically included alone, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

Although the present invention is disclosed above, the present invention is not limited thereto. Various changes and modifications may be effected therein by one skilled in the art without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A universal telecommunications invocation architecture, said architecture comprising: the remote procedure register comprises an RPC kernel, an IPC interface mapping module and an operating system packaging module;

2. The universal remote communication call architecture of claim 1, wherein the IPC interface mapping module establishes a correspondence between the RPC kernel and the IPC object via a pointer.

3. The universal telecommunications invocation architecture according to claim 1, wherein the IPC object includes any one of: CMUX, SOCKET, SIPC, UART, USB, SPI.

4. The universal telecommunications invocation architecture according to claim 1, wherein the operating system includes any one of: MOCOR, RT-Thread, WIN 32.

5. The universal telecommunications call architecture according to any one of claims 1 to 4, wherein the RPC kernel includes any one or more of the following methods: opening a window, reading, writing, input and output control and releasing.

6. A universal telecommunications invocation method, characterized in that said method comprises:

7. The universal remote communication call method as claimed in claim 6, wherein the IPC interface establishes the corresponding relationship between the RPC kernel and the IPC object through a pointer.

8. The universal telecommunications call method in accordance with claim 6, wherein the IPC object includes any of: CMUX, SOCKET, SIPC, UART, USB, SPI.

9. The universal telecommunications invocation method according to claim 6, wherein said operating system includes any one of: MOCOR, RT-Thread, WIN 32.

10. The universal remote communication call method according to any of claims 6 to 9, wherein the RPC kernel comprises any one or more of the following methods: opening a window, reading, writing, input and output control and releasing.

11. A computer-readable storage medium, being a non-volatile storage medium or a non-transitory storage medium, having a computer program stored thereon, the computer program, when being executed by a processor, performing the steps of the method according to any one of the claims 6 to 10.

12. An electronic device comprising a memory and a processor, the memory having stored thereon a computer program being executable on the processor, wherein the processor, when executing the computer program, performs the steps of the method of any of claims 6 to 10.