CN1441366A - Communication method and its device during process - Google Patents
Communication method and its device during process Download PDFInfo
- Publication number
- CN1441366A CN1441366A CN 02154551 CN02154551A CN1441366A CN 1441366 A CN1441366 A CN 1441366A CN 02154551 CN02154551 CN 02154551 CN 02154551 A CN02154551 A CN 02154551A CN 1441366 A CN1441366 A CN 1441366A
- Authority
- CN
- China
- Prior art keywords
- task
- message
- communication
- rup
- layer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Communication Control (AREA)
Abstract
An interprocess communication method for transporting messages from an originating place to a terminating place, the method including the steps of: providing an operating system-unified interface function, at an operating system independent access (OIA) layer, which is independently accessible to operating systems of a communication apparatus; providing a device-unified interface function, at a device independent access (DIA) layer, which is independently accessible to physical devices of the communication apparatus; and transporting messages, at a unified interprocess communication (UIPC) layer, from the originating place to the terminating place through at least one of the operating system independent access layer and the device independent access layer, using information about the terminating place that is provided by a terminating place task, and using a common task architecture based on the task's basic common control flow.
Description
Technical field
The present invention relates to the communication system of communication (IPC) between implementation. More particularly, the present invention relates to method and the equipment thereof of communication (UIPC) between RUP, they are independent of communication physical equipment and operating system.
Background technology
Interprocedual communication makes and ins all sorts of ways message communicating between implementation procedure, for example, and pipeline, semaphore (semaphore), message queue, or the memory of sharing. These methods all are based on operating system. So, provide that to have based on communication means between the various procedures of operating system be possible. In other words, the interprocedual communication means is decided according to operating system. Therefore, communication and during process between every less important implementation procedure, according to the operating system of using in the communication system, application software will be made corresponding change. Equally, suppose between hardware device, to carry out interprocedual communication, for the different physical equipment that provides, use different PDDs. Like this, for the process of a use device driver, the interprocedual communication functions will change according to the kind of the device driver that uses.
This interprocedual communication means in the communication system is according to operating system and physical equipment. As a result, when the operating system in the communication system and physical equipment variation, overhead (overhead) just repeatedly occurs. So not only worsen reusability and the portability of software, and increased the burden on time and cost when relevant industries are developed new communication system.
Summary of the invention
Therefore, an object of the present invention is to provide method and the equipment thereof of communicating by letter between RUP flexibly, they are to be independent of the operating system of communication system and physical equipment.
Another object of the present invention provides communication means and equipment thereof between a kind of RUP, no matter the operating system of using in the communication system how, can both be communicated by letter between high repeatable and high portable ground implementation.
Again another purpose of the present invention just provides method and the equipment thereof of communicating by letter between a kind of RUP of the physical equipment that is independent of communication system,
How and the communicator from starting point to terminal point pass-along message the kind that again another order of the present invention provides a kind of no matter the communication means used in communicator (for example: asynchronous transfer mode (ATM), Internet Protocol (IP), Synchronous Digital Hierarchy (SDH), etc.).
For achieving the above object, a kind of communication means from starting point to terminal point pass-along message is provided, the method comprising the steps of: provide a unified operation system interface function at operating system independent access (0IA) layer, but this unified operation system interface function is independent access to the operating system of communicator; Provide an equipment unified interface function at equipment independent access (DIA) layer, but this equipment unified interface function is independent access to the physical equipment of communicator; Communication layers between RUP, by in the middle of operating system independent access layer and the equipment independent access layer at least one, the information about terminal point that use is provided by a terminal point task, and use is based on a public task structure of the substantially public control flow (flow) of task, from starting point to terminal point pass-along message.
Another aspect of the present invention provides a kind of communicator from starting point to terminal point pass-along message, this device comprises: be used for providing the operating system independent access layer of operating system unified interface function, but this operating system unified interface function is independent access to the operating system of communicator; Provide the equipment independent access layer of equipment unified interface function, but this equipment unified interface function is independent access to the physical equipment of communicator; Communication layers between RUP, be used at least one by operating system independent access layer and equipment independent access layer, the information about terminal point that use is provided by a terminal point task, and use is based on a public task structure of the substantially public control flow of task, from starting point to terminal point pass-along message.
The something that should be noted that in an embodiment of the present invention is: resembling " process ", " application " or " task " these terms can Alternate, and they refer to be present in the task on the top of communication layers between RUP.
Description of drawings
By the detailed description below in conjunction with accompanying drawing, above-mentioned and other purpose, characteristics and advantage of the present invention will become more apparent.
Fig. 1 is the schematic diagram of the network that exchanges messages between each frame according to a preferred embodiment of the present invention;
Fig. 2 be according to a preferred embodiment of the invention application the exemplary view of detailed configuration of the communication system of communicating by letter between RUP;
Fig. 3 is the structure chart that comprises the public software platform of communicating by letter between RUP as an assembly according to a preferred embodiment of the invention;
Fig. 4 is the block diagram of communicating by letter and disposing between the RUP of each card of expression (each unit) according to a preferred embodiment of the invention;
Fig. 5 is the flow chart that uses the process of public task structure, that is, and and the basic controlling flow process figure of a task;
Fig. 6 is the block diagram of MAPI Messaging Application Programming Interface between the RUP of explaining according to a preferred embodiment of the invention (API) configuration and public task structure.
The specific embodiment
Below with reference to accompanying drawings, at this a preferred embodiment of the present invention is described. In the description below, well-known function or structure just are not described in detail, because they may allow the present invention become unclear in unnecessary details.
Below the foreign language document illustration background of the present invention and additional information, helpful to understanding principle of the present invention.
Open Systems Interconnection, Basic Reference Model (open system interconnection, Basic Reference Model), ITU-T is X.200;
Open Systems Interconnection, Data Link Service Definition (open system interconnection, data link traffic definition), ITU-T is X.212;
Open Systems Interconnection, Network Service Definition (open system interconnection, Network definition), ITU-T is X.213; And
Open Systems Interconnection, Transport Service Definition (open system interconnection, transport service definition), ITU-T is X.214.
Fig. 1 is the schematic diagram of the network that exchanges messages between each frame, has embodied principle of the present invention. The network topology of describing among the figure comprises element management system (EMS) 8, equipped the system controller frame 10 of a plurality of cards that comprise card 12, be equipped with smart machine 6 and comprise a plurality of cards of card 22a the first extension support on front 201, be equipped with a plurality of cards that comprise card 22b the second extension support on front 20b, be equipped with the 3rd extension support on front 30c of a plurality of cards that comprise card 22c.
With reference to figure 1, since the 3rd extension support on front 20c can and system controller frame 10 between communicate, although the second extension support on front 20b can be physically passed through in the communication between the 3rd extension support on front 20c and the system controller frame 10, but according to principle of the present invention, there is a virtual direct channels between the 3rd extension support on front 20c and the system controller frame 10.
Fig. 1 mainly is the network configuration of having used communication function between RUP of the present invention in order to explain. Although do detailed description with reference to Fig. 2 after a while, the rough description communicated by letter between RUP of the present invention exactly: it supports the message exchange between the upper task of each card, message exchange between the task of same upper different cards, and the message exchange between the task of a certain specific and attached smart machine 6 (for example, digital subscriber link modem and unify access means). Should be noted that above-described function is based on such hypothesis, that is, if necessary, system controller frame 10 determines the path of the message that will transmit between two framves. Simplified like this all accord, reduced with the protocol-dependent Internet Protocol that resembles and processed a more generally overhead the network topology structure. Equally, message can send on the path between the particular card on element management system 8 and the frame. As for communicating by letter between the RUP that relates to, element management system 8 is worked as another.
Fig. 2 has illustrated the detailed configuration of the communication system of using communication function between RUP of the present invention.
Extension support on front 20i among Fig. 2 is in a plurality of extension support on fronts of describing among Fig. 1, and system controller frame 10 is framves of controlling a plurality of extension support on front 20a, 20b and 20c. Each frame 10,20i comprise a plurality of control cards 14,16,24 and 26, and are used for controlling a plurality of control cards 14,16,24 and 26 main controller 12,22. The 30 part assemblies as the public software platform 32 of interprocedual message communicating of communicating by letter between RUP are provided to each control card 14,16,24,26 with main controller 12,22. Communication 30 is devices that a channel is provided for the interprocedual message communicating between RUP, and these message communicatings are between the interprocedual on the card, card, carry out on the frame and between the frame. Communication 30 resembles and is connected on the process (application task) the P1 shown in Fig. 2, the P2 between each RUP.
As shown in Figure 2, communication 30 has three kinds of forms between RUP: " procedure communication (processor intercommunication) in the card ", " procedure communication (inter-processor communication) between the card in frame ", " procedure communication between the frame (inter-processor communication) ". Especially, " procedure communication (inter-processor communication) between the card in frame " and independent PDD of " procedure communication between the frame (inter-processor communication) " needs.
Fig. 3 is that part comprises the block diagram that embodies the public software platform 32 of communication 30 between the RUP of principle of the present invention as an assembly.
The public software platform 32 of describing among Fig. 3 is the general and public functions that may be used on a lot of different communication systems be used to providing. Public software platform 32 is present in each in the card 12,14,16,22,24 and 26 in the unit illustrated in fig. 2 10,20, and its assembly is divided into a plurality of functional units.
As shown in Figure 3, public software platform 32 can be divided into horizontal assembly (being called horizontal assembly thereafter) and assembly (being called vertical component thereafter) arranged vertically haply. More specifically, administer and maintain such as public agency 40, public operation and to communicate by letter 30 between (OAM) 42, RUP, the horizontal assembly equipment independent access layer 46, PDD 48, real time operating system (RTOS) 50 and the hardware 52, all be the needed public function pieces of various communication systems, their specific technical functionalitys are all provided by vertical component. On the other hand, vertical component such as asynchronous transfer mode (ATM) 56, Synchronous Digital Hierarchy (SDH)+Plesiochronous Digital hierarchy (PDH) 58, packet voice (VoP) 160 all is according to the needed technical functionality piece of the kind of communication system. Similar with the front, the technical functionality of vertical component is provided by horizontal assembly, and they are according to the kind of communication system and difference. For example, to administer and maintain 42 be warning to be provided especially, to collect operation (performance) data, bookkeeping data for administering and maintaining of communication system to the public operation in other horizontal assembly. So, if public operation administers and maintains 42 and does some processing relevant with asynchronous transfer mode, for example the relevant alarm of an asynchronous transfer mode is provided or collects operating data for the relevant communication system of an asynchronous transfer mode, vertical equipment so, speaking by the book is that asynchronous transfer mode 56 provides these data. Using or increasing in the situation of a business software, just using among Fig. 2 the functional block 50,162,164,166,168 and 170 with oblique line.
Upper module namely, all depends on the application of software to " public operation administers and maintains 42 " from " the public agency 40 " shown in Fig. 3.
Normally, various communication systems comprise a public software platform 32 as shown in Figure 3, and communication system is endeavoured in all application that realize in the future, and the form of the function that all will combine with horizontal assembly with the vertical component that public software platform 32 provides is developed.
Explained later the concrete function of horizontal assembly of the public software platform 32 shown in Fig. 3:
1. operating system independent access layer 54
It provides operating system unified interface function, be used for to use with RUP between communicate by letter 30 realization so that can independent access operating system (OS) and any operating system of operating system 50 when not relying on strictly according to the facts. As a result, strengthened 30 the portability of communicating by letter between application and RUP. In other words, communicate by letter between software application and RUP and 30 can in different communication systems, be reused by different operating system.
2. equipment independent access layer 46
By hiding the more specifically part of PDD 48, for various device provides a kind of common model, that is exactly, equipment unified interface function, and this makes it possible to achieve the independent access of distinct device is not relied on this equipment. This is the benefit of equipment independent access layer 46, now, even change the such hardware chip of hardware 52 that resembles shown in Fig. 3, also can reuse the 30/ operating system independent access layer 54 of communicating by letter between this application and RUP.
3. communicate by letter 30 between RUP
According to the operating system that is used for interprocedual communication, such as bottom software and the bottom hardware 52 of real-time operating system 50, by hiding the detailed information about the interprocedual communication mechanism, when changing operating system in order to realize an application, do not need especially independent task.
4. public operation administers and maintains 42
For the Operations, Administration and Maintenance of various types of communication systems provides a kind of public method.
5, public agent software 40
For the more effective network operation in the communication system, for external network operating system provides an interface.
In brief, by the public function that does not need to be engaged in specific function is provided, the existence of public software platform 32 mainly is in order to realize a kind of software configuration, and this software configuration is can be reusable to different types of communication system, and is independent of operating system and hardware device. And communication 30 is assemblies of the public software platform 32 of information communication method between implementation procedure between RUP.
So far, for a better understanding of the present invention, public software platform 32 has been described. To the configuration of between RUP communication 30 and its function carry out detailed explanation from now on.
To similar among Fig. 2, communicate by letter 30 between RUP at each control module, i.e. control card 12,14,16,22,24 and 26 interior work. Mainly be in a card, on frame or the interprocedual in the different framves provides a Message Communication Function.
Message communicating by communication 30 between RUP of the present invention needs application identifier (ID) APP_ID and network address N_ADDR. Application identifier APP_ID is an identifier that is used for to communication difference relative process, and network address N_ADDR is an address value of the physical address of expression relative process. Network address N_ADDR is of a size of 4 bytes, and comprises cabinet-frame-groove-port (rack-shelf-slot-port) information. So, just can easily obtain the physical address of corresponding process by using network address N_ADDR. Network address N_ADDR only gives communication frame of 30 uses and groove (card just is fixed on here) identifier between RUP, and cabinet and port identification symbol are used for other purpose. With reference to figure 2, give one example, a message is delivered to the process 1 (P1) of the main controller 22 of extension support on front 20i from the process 1 (P1) of the main controller 12 of system master device frame 10 processed again. The identifier of supposing the system controller bay 10 is " 1 ", and the identifier of extension support on front 20 is " 2 ", and main controller 12,22 groove identifier are " 22 ". At first, starting point and terminal point application identifier APP_ID are respectively P1. Then, initial network address N_ADDR is 16 system numbers " 0x00010200 " (cabinet-frame-groove-port), and terminal point network address N_ADDR also is 16 system numbers " 0x00020200 " (cabinet-frame-groove-port). When network address N_ADDR and application identifier APP_ID are compared with procotol, will be similar to corresponding to an Internet Protocol address by discovering network address N_ADDR, and application identifier APP_ID is corresponding to the port numbers of a transmission control protocol (TCP).
The below is the function that embodies communication 30 between the RUP of principle of the present invention.
A two-way message Anywhere task in the networking component is transmitted in communication 30 between RUP.
Communication 30 allows to use asynchronous pass-along message between RUP. Application programming interfaces provide making an immediate response of not blocking.
Communication 30 permission tasks are when temporarily quitting work between RUP, pass-along message and synchronously responding.
Communication 30 extracts a bottom physical transfer mechanism between RUP.
Communication 30 is provided for the mechanism of broadcast between RUP.
Communication 30 between RUP so that between the RUP of low layer communication protocol variable and do not change upper-layer protocol, vice versa.
Communication 30 detects based on the error of transmission that is linked to link between RUP, and the grouping of mistake is chosen again. This means for the data link layer of the agreement of controlling each link and should do reliable link.
MAPI Messaging Application Programming Interface is to be used in the processor intercommunication to communicate by letter with external procedure between public RUP.
Communication 30 is cut apart and is re-assemblied jumbo message between public RUP.
Communication 30 provides the mechanism that can export error correction between RUP.
Communicating protocol parameter also can dispose at run duration between RUP.
Communication 30 provides to assign the mechanism of maximum transmission unit to each link between RUP.
The link that communication 30 supports have variable MTU between RUP.
The message priority that communication 30 is supported about real-time sensitive message between RUP.
Communication 30 is independent of operating system between RUP.
Communication 30 between RUP is so that message is passed through and the final equipment that is fixed on the card that arrives pellucidly from controller.
Although communication 30 is from starting point to terminal point pass-along message between RUP, as long as relate to the content of message, it just serves as an application. Like this, for specific system message, do not provide expression mechanism. The similar presentation layer of expression mechanism of system message, but do not comprise presentation layer according to communication 30 between RUP of the present invention, because communication 30 is for real-time protocol (RTP) between RUP.
Fig. 4 is the figure of communication 30 configuration between the RUP of each card of expression (each unit), has embodied principle of the present invention. Should be appreciated that in the drawings, " task " and " process " can Alternate.
With reference to Fig. 4, be included between the RUP in each card (unit) communication 30 and can roughly be divided between RUP communication protocol stack 70 between MAPI Messaging Application Programming Interface 60 and RUP. So just can more effectively distinguish communicating by letter of the communication between the processor that needs communication protocol stack 70 between RUP and the processor inside that does not need communication protocol stack 70 between RUP. Specifically, inter-processor communication is a kind of situation, wherein, its network address N_ADDR is not it self, like this, message should be delivered to from its card on the other card, and the processor intercommunication is another kind of situation, and wherein, its network address N ADDR is exactly itself, like this, message is directly delivered to the task of the inner correspondence of card. Simultaneously, MAPI Messaging Application Programming Interface 60 provides with a kind of form of storehouse between RUP, from a task call. Substantially, MAPI Messaging Application Programming Interface 60 comes messaging between the task call RUP, communicates by letter with communication protocol stack between RUP 70, with the message of communicating by letter between control processor.
At first, be further explained in detail MAPI Messaging Application Programming Interface 60 between according to a preferred embodiment of the invention RUP with reference to Fig. 4.
MAPI Messaging Application Programming Interface 60 between RUP
MAPI Messaging Application Programming Interface 60 is public libraries between RUP, can be shared by the task of any kind (, process), and provide with RUP between the relevant interface of communication 30 each built-in function that provides. In other words, MAPI Messaging Application Programming Interface 60 provides an interface between RUP, so that the application task of any type can both use communication function between RUP. In addition, MAPI Messaging Application Programming Interface 60 has determined interprocedual and the process internal communication path of address N ADDR Network Based and application software identifier APP_ID between RUP. In the meantime, communication protocol stack 70 between RUP is not used in 60 pairs of processor intercommunications of MAPI Messaging Application Programming Interface between RUP. And, MAPI Messaging Application Programming Interface 60 searches out network address N ADDR between RUP, attempt to find out the physical address of corresponding application task (process), and, if relate to the processor intercommunication, the operating system independent access application programming interfaces that so message provided by the operating system independent access layer 54 by Fig. 3 are directly delivered to the message queue of a corresponding task (process). On the other hand, if relate to inter-processor communication, MAPI Messaging Application Programming Interface 60 is delivered to a message queue of communication protocol stack 70 between RUP to message between RUP, comes the selected path that arrives the destination.
60 pairs of tasks of MAPI Messaging Application Programming Interface (application) provide between RUP, and to have one in the important function most be exactly a public task structure of public software platform 32, and it is so that task can be used between RUP communicates by letter. According to the major function of public task structure of the present invention such as following listed:
1. the developer does not need to redesign the task structure again.
2. carry out asynchronous callback facility in a caller's task.
3. the developer needn't be devoted to the integrated of common component (for example, public operation administers and maintains) and application.
4. become now possibility based on the communication between the task of message queue method, because communication mechanism between this public procedure that to be all operations system all provide.
In the assembly of public software platform 32 (horizontal assembly+vertical component), the software application of the upper strata piece of communication layers 30 between RUP particularly, for example, public proxy task 40, public operation administer and maintain task 42 etc., successfully realize by using the public task structure that embodies principle of the present invention. Fig. 5 is the basic public control flow that uses a task (process) of the public task structure with those above-mentioned four functions.
With reference to Fig. 5, task is waited for a message of using formation. Task is receipt message (S100) asynchronously, and the message that receives is decoded and analyzed (S102), carries out Message Processing (S104). If need independent processing, then task is just processed other specific use (S106), then waits for the message that turns back to step 100.
Table 1 and table 2 show traditional succession task structure and the comparative result that has according to the public task structure of the task of a substantially public control flow as shown in Figure 5 of the present invention. As illustrated in the table 1, because traditional succession task is not a public structure, it will be designed to separately different forms with task operating according to the developer. So even task is considerable overhead between development period, but it must redesign. On the contrary, as shown in following table 2, public task structure according to the present invention has realized having the basic public control flow of such as shown in Figure 5 task, has avoided overhead here. In this way, can greatly shorten the development time.
[table 1]
(inherit the task structure 〉
[table 2]＜public task structure 〉
| performanceTaskMain() { / *Task initialization and Component Gallery initialize*/ performanceTaskInit()； / *Message is accepted in circulation forever on major queue*/ |
| FOREVER rcvMsg (myQ ， ﹠pMsg) switch (msgType) case PERFORMANCE_TYPE_MSG call the executive module storehouse with processing messages case MY_MSGS processing messages end switch/*Receive other processing before of lower a piece of news*/ }/ *TaskMain finishes*/ |
| taskMain() { / *Task initialization and Component Gallery initialize*/ Uipc_InitTaskContext()； / *Create a message queue that can be used for by a task UIPC*/ Uipc_CreateQueue(MY_APP_ID，&hMyQueue)； / *The Uipc_RcvLoop () of a task is in this formation message first-class to be received*/ Uipc_SetmainQueue(hMyQueue)； / *Will receive the register of the message of a certain kinds*/ Uipc_RegisterMsgHandler(MY_MSG_CLASS，&MyMessageHandler)； / *Uipc_RcvLoop () will after handling message, when not having message in the formation, call the idle processor (handler) of depositing*/ Uipc_RegisterIdleHandler(&MyIdleHandler) / *Eternal circulation receipt message on major queue*/ Uipc_RcvLoop()； } |
Be described in detail referring now to the public task structure of describing in Fig. 6 his-and-hers watches 2.
Fig. 6 is an exemplary view according to the configuration of MAPI Messaging Application Programming Interface between RUP of the present invention and public task structure. With reference to Fig. 6, the inside that the main task of each card is communicated by letter between RUP produces the information table of an overall situation shown in the similar table 3, and generation service role, task 1 and task 2, their own specific functions (for example: warning task, operation task etc.) of these tasks carryings.
[table 3]
| The task recognition symbol | Application identifier | The pointer that is used for the dynamic message processor table of task | The pointer that is used for the static message processor table of task | The pointer that is used for the dynamic message class table of task | The idle message processor pointer that is used for task | The stand-by period of using in the Uipc_RcvLoop () | |
For the global information table of communicating by letter between the RUP of explaining more communication inside between RUP, this global information table comprises the information about all tasks on a particular card. Each entrance of global information table is a task control block (TSB). Suppose that each task control block has the information of unified appointment.
The first field of task control block is ' task recognition symbol '. The second field of task control block is ' application identifier ', " application identifier " of " major queue " of task that Here it is.
Each task has a dynamic message processor table, a static message processor table and a dynamic message class table. Whenever task call Uipc RegisterOneTimeApi (), just in dynamic message processor table, create an entrance. This task in the dynamic message processor table is not fixed. In fact, as long as receive response from application programming interfaces, this entrance is just deleted. By the binary tree of balance, can realize this dynamic message processor table. No matter when, when a task creation Uipc_RegisterMsgHandler (), just in this static message processor table, create an entrance. Here, this static message processor table is exclusively used in the application programming interfaces of a monitoring programme (supervisor). Different with the entrance in the dynamic message processor table, the entrance in the static message processor table is fixed. Like this, this static message processor table can be realized by using array.
No matter when, when a task call Uipc GenerateTempMsgClass (), this classes of messages turns back to above-mentioned task, and carry out in dynamic message class table in more new capital of any necessity, so that a specific classes of messages is in busy state (busy). Equally, no matter when, when this task call Uipc_FreeTempMsgClass (), communication is to doing necessary correction, so that specific classes of messages is obtainable to a use of back between RUP in the dynamic message class table. Dynamic message class table is implemented as an other array.
Global information table comprises the pointer for each above-mentioned table. And global information table comprises the pointer for ' idle message processor ' function of task. Global information table also comprises (latency) time of hiding, and is assumed that this latent time for the Uipc_RcvLoop () of each task only. In Uipc_RcvLoop_API, will examine latent time to global information table. Since each task is addressable to global information table, the semaphore code of an appointment is just protected this global information table. This semaphore code produces during Uipc_InitCardContext ().
With reference to figure 6, in the MAPI Messaging Application Programming Interface, Uipc_InitCardContext () is assumed to be it is to carry out initialized according to the present invention to communication 30 between RUP between RUP again. Uipc_InitCardContext () by the main task operation specifies a block storage to communicate by letter 30 to use between RUP, and produces a data internal structure. Here, Uipc_InitCardContext () should block (unit) and only calls once for each.
Public task structure about attached task task1 and task2 will explain further that task1 and task2 are produced by main task.
In the public task structure, no matter when, help many tasks when producing a task, when enabling to use between RUP communication 30 to intercom mutually, Uipc_InitTaskContext () just specifies a global information table, and deposits the global information table that is assigned to the global table entrance. Equally, Uipc_InitTaskContext () should be called once for each task.
Uipc_CreateQueue (TASK1_APP_ID) creates a formation and helps each task, to make it and can come receipt message with communication between RUP. Uipc_CreateQueue (TASK1_APP_ID ， ﹠Task1Queue) deposits the formation identifier of an establishment queue table of the application identifier that is used for task.
Corresponding formation of Uipc_SetmainQueue (hTask1Queue) is set to a major queue for receipt message. In case deposited as major queue, it will be used as the Messages-Waiting formation in Uipc_RcvLoop () inside.
The processor function (handler function) that Uipc_RegisterMsgHandler (TASK1_MSG_CLASS ， ﹠Task1MessageHandler) will be used for processing the message (classes of messages) of the message that receives from a task and be used for Message Processing is deposited a global information table. They are for the treatment of the message of receiving in Uipc_RcvLoop () internal interface.
When a task will be carried out except Message Processing other function, Uipc_RegisterIdleHandler (﹠Task1IdleHander) the processor function is deposited in the global information table, when not receiving any message from Uipc_RcvLoop (), carry out a given other job.
Task is carried out among Uipc_RcvLoop () from major queue receipt message and the process of processing these message that receive. It is never responded, but unlimited circulation of inner execution. And it is carried out and resembles the such thing of message sink/source codec/Message Processing/additional work.
Referring now to Fig. 4 communication protocol stack 70 between the RUP of communication 30 between RUP is described in detail.
The operation of those three layers will be done after a while detailed explanation. Yet, before every layer being done further details description, be necessary to introduce some General Requirements that are applied to every layer. The purpose of doing like this is in order to realize above-mentioned layer.
At first, the head (header) of every one deck should comprise a protocol discriminator. Whether this discriminator shows has the combination of a specific agreement or an agreement to be accompanied by this message. Usually, this protocol discriminator comprises 2 bits or 3 bits at head. This realization does not need to change other agreement and just can carry out. For example, the message that receives of being processed by Internet 74 has a protocol discriminator at the head of its Internet, and this protocol discriminator indicates next step that protocol module will process this message. If communication wants to support similar transmission control protocol or the such transport layer protocol of UDP (UDP) between RUP, then whether protocol discriminator will be delivered to transmission control protocol or UDP module with regard to informing network layer 74 this message. At this moment, UDP is just with reference to Internet Standard Internet, transport layer and session-layer protocol that datagram service is provided. Similar with transmission control protocol, UDP also is a connectionless agreement of the top layer of Internet Protocol.
Some protocol layer depends on other layer, and they can not independently use in other words. For example, D channel link access process (LAPD), a kind of data link layer protocol depends on physics High-Level Data Link Control (HDLC) layer. Here, " D channel link access process " meaning is a links and accesses process on the D channel.
Every layer all has a message priority. So message or section (section: if a message long enough will carry out segmentation to it) with high priority were just transmitted before other message and section. Preferably, two priority namely, have been introduced " common " and " senior " priority among the present invention, can make more chaotic to thing because further only divide. But, if necessary, at any time can divide in addition priority.
In addition, every one deck can define concrete control message, and these control messages exchange between the identical layer of an end points. These control messages and a layer agreement protocol parameter or allow a layer to carry out the control of flow process.
The below will describe feature and the responsibility of each protocol layer. A primitive that is provided by every one deck (primitive) tabulation is provided every part. These primitive are that supposition is used for showing the external interface (that is, next protocol layer) that other software is provided. They needn't explain the real messages of communicating by letter between two end points. They equally, for the definition of these message and their state machine, do not need to explain, because when one design was set up more specifically, will be defined yet.
These primitive will be named according to the term system of International Telecommunication Association (ITU), and will be by as follows being divided into " request ", " response ", " indication " and " affirmation ".
Request: its meaning is the function that a layer should be supported, normally lower one deck of this layer calls it and asks some operations.
Response: when receiving the order that a request is responded, it is called by a distant place or long-range terminal. Thereby, above the requestor of ' request ' will receive this affirmation.
Indication: it is a notice, is used for informing that something has occured. Usually, its indication is lower one deck of number upwards, or expression receives this order by the code that produces after a while. Most ' indication ' all is that (long-range) terminal is passed through the result that ' request ' initializes an operation at a distance.
Confirm: it is a confirmation of response ' request '.
Each primitive has such data, and these data have the associated primitive of an appointment. For the mechanism by the primitive between the layer, because it is the part of the detailed design of layer, here will not be described in detail.
On the other hand, recognize that the necessity that defines a MTU (MTU) is very important. MTU has defined a maximum message size. Any than full-size little message can transmit as single message.
In fact, determine that MTU is exactly a part of using design. So it is not to define as a part of communicating by letter between RUP. Yet, specify MTU, between RUP communication definitions one only to the visible internal applications interface of communications component between RUP. The determining of MTU is based on the communication linkage speed for the number of the request of carrying out an application, jumping (hop) that message is assumed to be employing (jump: between a router and another router section) and current use.
The problem that may have a lot of complexity at the network that is used for the guide message pathway from a node to next node. For example, if the MTU of every jumping is different, just must takes some measures and solve this imbalance. Problem is, when a node transmission has the message of large MTU, and this message is when exceeding another node after jumping and broadcast with a little MTU, often can go wrong. Certainly, for a specific node, the MTU that know each link of message process is very difficult. In fact, an initial node even may not know that this message will be passed to the link of which bar. Known to all start nodes is how message to be sent to next node. So the protocol stack of each node should overcome in the difference that is connected on the MTU size of a link on the corresponding node. Internet 74 has fragmentation feature, will describe in " Internet 74 " part after a while. It will be used to a large MTU is segmented into little MTU. If Internet is not carried out segmentation, one connects end to end and can be used as one and select and attempt, and wherein, all nodes all participate in determining the discussion of MTU. Yet unfortunately, this method can produce overhead, and does not have what effect for connectionless message.
In three layers that communication protocol stack 70 is supported between RUP, at first data link layer 72 is made an explanation. A data link between data link layer 72 connection end points, and the error-free data transmission between being responsible for linking, and these following operations are provided.
1, by providing high priority data power to rank.
2, the steady transmitting-receiving of supported data by a flow process control is provided.
3, support the error-free data transmission.
4, provide connectionless pattern and towards connection mode, and under connection-oriented pattern, carry out the connection of data link/release.
5, when having mistake, can retransmit corresponding data.
Table 4 is a content and their descriptions of the primitive of the connection-oriented pattern on data link layer 72, and this data link layer needs connection-oriented data link at least. Shown in the table 5 is a content and their description of the primitive of the connectionless-mode on data link layer 72, and this data link layer needs connectionless data link at least.
[table 4]
The primitive of the connection-oriented pattern the on＜data link layer 72 and their description 〉
The primitive of the connectionless-mode on [table 5]＜data link layer 72 and their description 〉
| Service | Primitive | Describe |
| Link is set up | The DL-CONNECT request | It is initialised to a remote endpoint or to the connection of a physical channel. |
| The DL-CONNECT indication | When a remote endpoint initialized a connection of arriving here, it just was received | |
| DL-CONNECT replys | It is called by DL-CONNECT indication receiver, to accept this connection | |
| DL-CONNECT confirms | The initiation point that notice connects, a long-range end points has been accepted this connection. | |
| Normal data transfer | The DL-DATA request | Be used for the transmission of data by transmitter. |
| The DL-DATA indication | Be sent to receiver and be used for data receiver | |
| Link discharges | The DL-DISCONNECT request | Transmitter or receiver can initialize Connection Release. Need not respond. |
| The DL-DISCONNECT indication | When the remote endpoint release connection, just receive it. |
| Service | Primitive | Describe |
| Link is set up | The DL-DATA request | Transmitter carries out the data transmission with it. |
| The DL-DATA indication | Receiver carries out data receiver with it. |
Explained later be Internet 74 in three layers being supported by communication protocol stack between RUP 70. Internet 74 is responsible for the route of message between the processor of inter-processor communication. The function of Internet 72 is described below.
1, it provides a message routing functionality.
Its address N ADDR Network Based determines the message route. More particularly, Internet determines that a message is be sent to a transport layer as the message of a process, still should arrive final destination through another interface transmission.
2, it supports message fragment and restructuring.
When message is carried out route, be sent in message in the situation of the interface with MTU different with this data link layer, will carry out Segmentation and Reassembly to message.
3, it carries out a stateless operation.
Because Internet 74 is not supported the retransmitting message function, it carries out a stateless operation that does not have status mechanism. When a message was sent out, no matter whether receiver had received this message, and the message of this transmission is not saved, and will disappear at last. If need to be between end points sending/receiving message more reliably, it need to be placed transport layer 76.
Communication 30 has defined the relevant primitive in additional address between RUP, in order to have the interface of the operation that can carry out above-mentioned Internet 74. Following table 6 is content and the description thereof of the primitive of Internet 74.
[table 6]
＜primitive and description thereof on Internet 74 〉
| Service | Primitive | Describe |
| The general data transmission | The N-DATA request | Transmitter carries out data with it and sends |
| The N-DATA indication | Receiver carries out data receiver with it |
At last, the transport layer 76 in three layers of 70 supports of communication protocol stack between RUP is made an explanation. Substantially, the end to end communication between transport layer 76 responsible tasks. The below does more explanation about the function of transport layer 76.
1, its routing function that gives information.
It sends to purpose with the message that receives and uses. At last, transport layer 76 is responsible for setting up a routing table based on application identifier APP_ID. This routing table can form by the internal applications interface that MAPI Messaging Application Programming Interface between a RUP 60 uses.
2, it provides connectionless-mode and towards connection mode. Ensure that in lower floor's (for example, data link layer) reliability reduces under the condition of the overhead in the communication process end to end, just use connectionless-mode. So, under connectionless pattern, as in data link layer 72, do not check whether target application has received message. On the other hand, under connection mode, the connection of using end to end be established, so that can sending/receiving message, in function aspects, a socket (socket) of it and transmission control protocol be similar. In addition, because connection-oriented pattern has extra overhead, and unusual complexity in foundation/release connection, had better not use too frequently this pattern, especially have lower reliability and when not a lot of to the requirement of real-time Communication for Power request the time when low layer.
3, its multiplex function that gives information.
When receiving a large amount of message there from many application, transport layer 76 makes up these message based on the network address N ADDR of starting point, and the message of these combinations is delivered to a corresponding application.
Table 7 is that it is that an external interface function is desired in the content of the primitive of the connection-oriented pattern of transport layer 76 and its description. Table 8 is content and descriptions thereof of the primitive of the connectionless pattern in transport layer 76, and it is that an external interface function is desired.
[table 7]
＜the primitive of connection-oriented pattern in transport layer 76 and their description 〉
Primitive and the description thereof of the connectionless pattern of [table 8]＜in transport layer 76)
| Service | Primitive | Describe |
| Link is set up | The T-CONNECT request | It is initialised to the connection of an application. Its response and queue processor interrelate. |
| The T-CONNECT indication | When a remote endpoint was initialised to an application connection, it was just received. | |
| The T-CONNECT response | It is called by T-CONNECT indication receiver, to accept this connection. | |
| T-CONNECT confirms | The initiation point that its notice connects, a remote endpoint has been accepted this connection. | |
| Normal data is transmitted | The T-DATA request | It is used for carrying out data by transmitter and sends. |
| The T-DATA indication | Its received device is used for carrying out data receiver. | |
| Link discharges | The T-DISCONNECT request | Transmitter or receiver can initialize Connection Release. Need not respond |
| The T-DISCONNECT indication | When remote endpoint discharged this connection, it was just received. |
| Service | Primitive | Describe |
| Normal data transfer | The T-DATA request | Transmitter carries out data with it and sends. |
| The T-DATA indication | Receiver carries out data receiver with it. |
The below illustrates the general process from from initial task to terminated task pass-along message data of being used for that embodies the principle of the invention with reference to Fig. 1 to Fig. 6.
For transmitting a piece of news to a purpose task, initial task is with regard to call function Uipc_SendMsg (data, destination address), this function can provide from MAPI Messaging Application Programming Interface between RUP network address N_ADDR, application identifier APP_ID and the message data of purpose task. Thereafter, this task is loaded into function Uipc_SendMsg (data with network address N_ADDR, application software identifier APP_ID and the message data of purpose task, destination address), MAPI Messaging Application Programming Interface 60 determines this destination address between RUP, that is, whether network address N_ADDR is the same with the network address on it oneself card. If the same, that is to say, if destination address, or the network address, be exactly the network address on it blocks itself, so, communication is delivered to the destination to message between processor intercommunication RUP. But if the network address on the card of destination address and it oneself is different, so, communication is delivered to the destination to message between the communication RUP between processor. If be loaded into function Uipc_SendMsg (data, destination address) network address N_ADDR is the network address on it blocks itself, namely, for communicating by letter between processor intercommunication RUP, so, MAPI Messaging Application Programming Interface 60 directly is delivered to message a message queue of the purpose task in the card by operating system independent access application programming interfaces storehouse between RUP, and this operating system independent access application programming interfaces storehouse is provided by the operating system independent access layer 54 among Fig. 3. Relating in the situation of communicating by letter between processor intercommunication RUP, protocol stack 70 does not just need at all. Simultaneously, owing to received message, by using Uipc_RcvLoop () function, based on the substantially public control flow of the public task structure shown in Fig. 5 and Fig. 6, the purpose task is with regard to control such as message sink, source codec, Message Processing and the relevant operation according to other processing of asking to be carried out separately by task.
On the other hand, if destination address, or network address N_ADDR, the network address of oneself blocking with it is different, that is to say, if communicate by letter between the communication RUP between processor, so, MAPI Messaging Application Programming Interface 60 is delivered to a message queue of communication protocol stack 70 between RUP to message between RUP, is used for proceeding to the route search of an outside destination. More particularly, MAPI Messaging Application Programming Interface 60 is delivered to of communication protocol stack 70 between RUP to message and transmits formation between RUP. Then, transport layer 76 is with regard to the concrete operations of guide needle to the transport layer that sends to the message of transmitting formation, and processes these message, and a network queue that the message of processing is sent to Internet 74. Internet 74 guide needle are to sending to the concrete operations of the Internet in the network queue, and these message are delivered to a data linked queue of data link layer 72. Similarly, data link layer 72 guide needle are to the concrete operations of the data link layer that sends to the message in the data link formation, and these message are delivered to equipment independent access layer (please refer to 46 among Fig. 3), send to device driver 48 on the purpose card, send to device driver 48 by equipment independent access layer (please refer to 46 among Fig. 3).
After, data link layer 72, Internet 74 and the transport layer 76 of message by protocol layer 70 that sends to equipment independent access layer (please refer to Fig. 3 46), the device driver 48 of purpose card is sent to the purpose task. Equally, network address N_ADDR and application identifier APP_ID can be used to identifying purpose card and purpose task. Accordingly, by the Uipc_RcvLoop () function that is provided by MAPI Messaging Application Programming Interface storehouse between RUP is provided, based on the basic controlling flow process of the public task structure shown in Fig. 5 and Fig. 6, purpose task control such as message sink, source codec, Message Processing and the relevant operation according to other processing of asking to be carried out separately by task.
Following table 9 has illustrated that this section program is carried out about one section program of Uipc_SendMsg (data, destination address) function in a task, this function has been unified interprocedual MAPI Messaging Application Programming Interface 60 and has called. [table 91
| Uipc_SendMsg(data，destinationAddress) { if(destinationAddress＝＝myAddress)/ *Communication { 1. obtains destination queue identifier-〉 DestQueue 2. and with DestQueue data is sent to another one task-〉 Oia_WriteQByld (DestQueue, AppDAta) by the operating system independent access between the RUP of the task in the card (unit); Else/*Between the RUP of task communication the card (unit) between |
| Data are delivered to " communication stack transmission tasks formation between RUP "-〉 us_AL_Transmit_TL (AppData) { Oia_WriteQByld (TransportQueue, AppData); |
Similarly, following table 10 has illustrated one section program about Uipc RcvLoop () function, and this section program is carried out in a task, has been unified interprocedual MAPI Messaging Application Programming Interface 60 and has called. Table 10
| Uipc_RcvLoop () { Uipc_Rcv () { Oia_ReadQByld (AppQueue, AppData)-〉 receives a piece of news } Uipc_ProcessMsg (AppData) { to source codec and processing } } |
At last, communicate by letter so that all application (process) can have a public structure by a structure that is called the public task structure between RUP of the present invention, and finally alleviated the burden of exploitation new communication system and shortened its development time. In addition, the benefit of the benefit of public software platform, horizontal assembly and vertical component combination be not can because of future operating system and equipment change do other work.
Although with reference to the preferred embodiments of the present invention the present invention is showed and describes, those it should be appreciated by those skilled in the art, under the prerequisite of the spirit and scope of the present invention that in not breaking away from by appended claims, define, can carry out on the various forms with details on change.
Claims (17)
1. interprocedual communication means that is used for from starting point to terminal point pass-along message, the method comprising the steps of:
At operating system independent access (OIA) layer, an interface function that operating system is unified is provided, the unified interface function of this operating system can independent access for the operating system of communicator;
At equipment independent access (DIA) layer, an interface function that equipment is unified is provided, the unified interface function of this equipment can independent access for the physical equipment of communicator; And
Communication (UIPC) layer between RUP, by in operating system independent access layer and the equipment independent access layer at least one, the information about terminal point that use is provided by the terminal point task, and use is based on a public task structure of the substantially public control flow (flow) of this task, from starting point to terminal point pass-along message.
2. method as claimed in claim 1, wherein, communication layers comprises between RUP:
MAPI Messaging Application Programming Interface between RUP (API) is used for providing an interface, so that task can be used communication functions between RUP, also is used for based on the path of determining processor intercommunication and inter-processor communication about the information of terminal point; And
Communication protocol stack between RUP be used for to be used the message of being determined its current path by MAPI Messaging Application Programming Interface between RUP, for route between the unit is carried out in the communication of processor inside.
3. method as claimed in claim 1, wherein, communication protocol stack comprises between RUP:
Data link layer is used for a data link between the connection end point, and transmits error-free data between link;
Internet is used for the communication period in processor inside, carries out the message route between task;
Transport layer is used for the end-to-end communication between task.
4. method as claimed in claim 1, wherein, information about terminal point comprises an application discriminator and a network address, and this is used discriminator and is used for differentiating the with it corresponding task of communication, and this network address is used for locating a physical address of corresponding task.
5. method as claimed in claim 4, wherein, the network address comprises cabinet-frame-groove-port (Rack-Shelf-Slot-Port) information.
6. method as claimed in claim 4, wherein, MAPI Messaging Application Programming Interface is the public library that can use the task of any kind between RUP.
7. method as claimed in claim 1, wherein, the substantially public control flow of public task structure comprises other relevant function that message sink, source codec, Message Processing and a task will be carried out according to request.
8. device that is used for the inter-processor communication from starting point to terminal point pass-along message, this device comprises:
Operating system independent access layer is used for providing an operating system unified interface function, and this operating system unified interface function can independent access for the operating system of communicator;
Equipment independent access layer is used for providing an equipment unified interface function, and this equipment unified interface function can independent access for the physical equipment of communicator; And
Communication layers between RUP, be used at least one by operating system independent access layer and equipment independent access layer, the information about terminal point that use is provided by the terminal point task, and use is based on a public task structure of the substantially public control flow of this task, from starting point to terminal point pass-along message.
9. device as claimed in claim 8, wherein, communication layers comprises between RUP:
MAPI Messaging Application Programming Interface between RUP is used for providing an interface, so that task can be used communication function between RUP, also is used for based on the path of determining processor intercommunication and inter-processor communication about the information of terminal point;
Communication protocol stack between RUP be used for to be used the message of being determined its current path by MAPI Messaging Application Programming Interface between RUP, for route between the unit is carried out in the processor intercommunication.
10. device as claimed in claim 8, wherein, communication protocol stack comprises between RUP:
Data link layer is used for connecting a data link, and is used for transmitting error-free data between link between end points;
Internet is used for carrying out the route of message between task during the processor intercommunication;
Transport layer is used for the end to end communication between task.
11. device as claimed in claim 8, wherein, information about terminal point comprises an application discriminator and a network address, and this is used discriminator and is used for differentiating the with it corresponding task of communication, and this network address is used for locating a physical address of corresponding task.
12. such as the device of claim 11, wherein, the network address comprises cabinet-frame-groove-port information.
13. device as claimed in claim 9, wherein, MAPI Messaging Application Programming Interface is the public library that can use the task of any kind between RUP.
14. device as claimed in claim 8, wherein, the substantially public control flow of public task structure comprises other relevant function that message sink, source codec, Message Processing and a task will be carried out according to request.
15. a method that is used for the inter-processor communication from starting point to terminal point pass-along message, the step that the method comprises:
Provide a public task structure of the substantially public control flow with a task, as an interface of communicating by letter between RUP;
If initial task provides a piece of news with the public task structure and about the information of terminal point, just based on the information about terminal point, determine that this message is the inter-processor communication message in the card (card), or the processor intercommunication message between the card;
If this message belongs to the processor intercommunication message between the card, so this message is delivered between RUP a formation of communication protocol stack and carries out route;
If this message belongs to the inter-processor communication message in the card, application programming interfaces storehouse by being provided by operating system independent access layer so is delivered to message a message queue of the interior corresponding task of card.
16. such as the method for claim 15, wherein, communication protocol stack comprises between RUP:
Data link layer is used for connecting a data link, and is used for transmitting error-free data between link between end points;
Internet is used for carrying out the route of message between task during the processor intercommunication;
Transport layer is used for the end to end communication between task.
17. a device that is used for the inter-processor communication from starting point to terminal point pass-along message, this device comprises:
The operating system piece is used for processing independently intercommunication at device; And
Hardware block is used for processing from the outside to PERCOM peripheral communication this device or from this device to the outside independently.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US31630101P | 2001-09-04 | 2001-09-04 | |
| US60/316,301 | 2001-09-04 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1441366A true CN1441366A (en) | 2003-09-10 |
| CN1326066C CN1326066C (en) | 2007-07-11 |
Family
ID=27788885
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB021545510A Expired - Fee Related CN1326066C (en) | 2001-09-04 | 2002-09-04 | Communication method and its device during process |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1326066C (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100432944C (en) * | 2005-09-30 | 2008-11-12 | 中国科学院研究生院 | Computer system |
| CN106293957A (en) * | 2015-06-24 | 2017-01-04 | 帕洛阿尔托研究中心公司 | Order flexibly in content center network and control |
| CN107204908A (en) * | 2016-03-17 | 2017-09-26 | 阿里巴巴集团控股有限公司 | A kind of message sending, receiving method and device based on interface communication protocol frame |
| CN107766077A (en) * | 2017-10-18 | 2018-03-06 | 张洋 | A kind of multiple external device control methods and device |
| CN113032166A (en) * | 2021-03-26 | 2021-06-25 | 黑芝麻智能科技(上海)有限公司 | Inter-core communication method, processor, inter-core communication system, and computer-readable storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TW439380B (en) * | 1995-10-09 | 2001-06-07 | Hitachi Ltd | Terminal apparatus |
| SE9804391L (en) * | 1998-12-17 | 2000-06-18 | Ericsson Telefon Ab L M | Method and device in communication networks |
-
2002
- 2002-09-04 CN CNB021545510A patent/CN1326066C/en not_active Expired - Fee Related
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100432944C (en) * | 2005-09-30 | 2008-11-12 | 中国科学院研究生院 | Computer system |
| CN106293957A (en) * | 2015-06-24 | 2017-01-04 | 帕洛阿尔托研究中心公司 | Order flexibly in content center network and control |
| CN106293957B (en) * | 2015-06-24 | 2021-07-06 | 思科技术公司 | Flexible command and control in content-centric networks |
| CN107204908A (en) * | 2016-03-17 | 2017-09-26 | 阿里巴巴集团控股有限公司 | A kind of message sending, receiving method and device based on interface communication protocol frame |
| US10848595B2 (en) | 2016-03-17 | 2020-11-24 | Alibaba Group Holding Limited | Method and device for message sending and receiving based on a communication interface framework |
| CN107766077A (en) * | 2017-10-18 | 2018-03-06 | 张洋 | A kind of multiple external device control methods and device |
| CN113032166A (en) * | 2021-03-26 | 2021-06-25 | 黑芝麻智能科技(上海)有限公司 | Inter-core communication method, processor, inter-core communication system, and computer-readable storage medium |
| US20220308947A1 (en) * | 2021-03-26 | 2022-09-29 | Black Sesame Technologies Inc. | Method for inter-core communication, processor, inter-core communication system and computer readable storage medium |
| US11948021B2 (en) * | 2021-03-26 | 2024-04-02 | Black Sesame Technologies Inc. | Method for inter-core communication, processor, inter-core communication system and computer readable storage medium |
| CN113032166B (en) * | 2021-03-26 | 2024-05-24 | 黑芝麻智能科技(上海)有限公司 | Inter-core communication method, processor, inter-core communication system, and computer-readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1326066C (en) | 2007-07-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1404264A (en) | Unified intra-process communication | |
| CN1294727C (en) | Expandable communication system | |
| CN1742473A (en) | Common protocol layer architecture and methods for transmitting data between different network protocols and a common protocol packet | |
| CN1292566C (en) | Router and address identification information management server | |
| US6667972B1 (en) | Method and apparatus providing multi-service connections within a data communications device | |
| CN102339234B (en) | Device for operating protocol stack and method | |
| CN101047714A (en) | Apparatus and method for processing network data | |
| CN1864397A (en) | Supporting enhanced media communications | |
| CN1723439A (en) | An apparatus and method for configuring data plane behavior on network forwarding elements | |
| CN1993961A (en) | Method and device for session control in hybrid telecommunication networks | |
| CN1652561A (en) | Call processing system and method in a voice and data integrated switching system | |
| CN1617526A (en) | Method and device for emulating multiple logic port on a physical poet | |
| CN1889464A (en) | Method and apparatus for realizing communication take-over and control | |
| CN1812397A (en) | Network management interface adapter and information interacting method | |
| US7263701B2 (en) | Interprocess communication method and apparatus | |
| US20010046224A1 (en) | Radio data communication system and method thereof | |
| CN102413147A (en) | Agent server | |
| CN1301096A (en) | Control and distribution protocol for implantable router frame | |
| CN1313693A (en) | Device and method for automatic terminal identification discovery in hierarchy different machines system | |
| CN1946060A (en) | Method for realizing re-oriented message correctly repeat and first-part and second-part | |
| CN101076791A (en) | Dynamic special purpose processors communication network capable of providing port | |
| CN1441366A (en) | Communication method and its device during process | |
| EP2005726B1 (en) | Method for call setup time improvement | |
| CN1906954A (en) | Signaling transport converter | |
| KR20060027352A (en) | Method and system for establishing a data link layer protocol on a i2c physical layer connection |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20070711 Termination date: 20091009 |