CN102833080A - Process-to-process communication method of application software and system - Google Patents
Process-to-process communication method of application software and system Download PDFInfo
- Publication number
- CN102833080A CN102833080A CN2011101602851A CN201110160285A CN102833080A CN 102833080 A CN102833080 A CN 102833080A CN 2011101602851 A CN2011101602851 A CN 2011101602851A CN 201110160285 A CN201110160285 A CN 201110160285A CN 102833080 A CN102833080 A CN 102833080A
- Authority
- CN
- China
- Prior art keywords
- client
- module
- finger daemon
- client process
- services request
- 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.)
- Pending
Links
Images
Landscapes
- Computer And Data Communications (AREA)
Abstract
The invention relates to a process-to-process communication method of application software and a system. The method comprises receiving registration information of a client through a daemon module; and monitoring, forwarding and responding to service request information of the client, and comprises the specific steps of a client A sending a service request to the daemon module to request the daemon module to return one or more services provided by a client B; the daemon module forwarding the service request of the client A to the client B after receiving the service request sent by the client A; the client B processing the service request of the client A, and returning the processing result to the daemon module; and the daemon module returning the processing result of the client B to the client A. The process-to-process communication method provided by the invention is independent of the operation system, and the same software can be operated on different operation systems, thereby facilitating quick software project development by technicians, and reducing the software development and maintenance cost.
Description
Technical field
The present invention relates to computer realm, relate in particular to a kind of inter-process communication methods and system of application software, specifically, the present invention relates to a kind of communication software and inter-process communication methods operating system independent and system.
Background technology
Process is the elementary cell that operating system is dynamically carried out, and is the program implementation process.Sometimes need communicate for collaborative work between process and the process.
In the most widely used operating system such as Windows and linux system at present; The method that has multiple interprocess communication; Specifically; There are anonymous pipeline, named pipes, mailslot and shared drive in the Windows system, and linux system then has pipeline, named pipes, message queue, shared drive and semaphore.Although so pipeline and shared drive are all arranged in Window and the linux system, they also have some differences in the use.For example, the named pipes of Windows is supported full duplex, can across a network, and the named pipes of Linux is only supported half-duplex, can not across a network.The technical staff is when one of exploitation relates to the software project of communication like this; If want to let this project support a plurality of operating systems simultaneously; Just have to write a cover software code respectively according to the bottom API (Application Programming Interface, API) that each operating system provides.The complexity that this not only can increase item code also can increase the project maintenance cost.
Summary of the invention
Main purpose of the present invention is to provide a kind of inter-process communication methods and system of application software, makes communication and operating system independent between the process.
The invention discloses a kind of inter-process communication methods of application software, be used for the communication between client process A and the client process B, perhaps client process A and the client process B broadcast service that will respond respectively; May further comprise the steps:
Steps A: client process A sends services request to the finger daemon module, requires to return one or more services that client process B provides;
Step B: said finger daemon module is transmitted to said client process B after receiving the services request that said client process A sends;
Step C: said client process B receives and handles the services request of said client process A, and result is returned to said finger daemon module;
Step D: said finger daemon module returns to said client process A with the result of said client process B.
Before said steps A, can also may further comprise the steps:
Said finger daemon module starts and sets up a socket, is used to monitor and wait for client's register requirement and services request;
Said client process A sends register requirement to said finger daemon module, comprises client's log-on message in the request;
Said finger daemon module monitors is saved in the log-on message of said client process A in the database and returns the message that succeeds in registration after the register requirement of client process A.
Can comprise in the said log-on message service that customer name, client provide and client the broadcast that will respond.
Said finger daemon module monitors checks at first whether the customer name of said client process A registration exists, if there has been information from registration failure to said client process A that then return after the register requirement of client process A.
In said step B; After said finger daemon module is received the services request that said client process A sends; At first check the log-on message that whether has client process B in the data,, otherwise get into following steps if there is not the information of then returning the services request failure to said client process A:
Further whether there is said client process A requested service in the log-on message of inspection client process B; If exist the services request of then said client process A being sent to be transmitted to said client process B, otherwise return the information of services request failure to said client process A.
The invention also discloses a kind of interprocess communication system of application software, comprise the finger daemon module, be used to receive client's log-on message, the service request information of monitoring, forwarding and customer in response; Said finger daemon module further comprises:
The services request receiver module is used to receive one or more services request that the client sends;
The services request forwarding module is used for one or more services request that said client sends are transmitted to the ISP;
The service result receiver module is used to receive the service response result that said ISP provides;
Service result is returned module, is used for the service response result that said ISP provides is returned to said client;
Said services request module, said services request forwarding module and said service requester are linked in sequence, and said service requester also returns sequence of modules with said service result receiver module, said service result and is connected.
Said finger daemon module can also comprise:
The socket module is used to monitor and wait for register requirement and the services request that the client sends;
The register requirement receiver module is used to receive the register requirement that the client sends.
Said finger daemon module can further include:
The log-on message processing module is used to check whether the customer name of client enrollment exists, and then returns the information of registration failure to said client if exist, otherwise preserves said client's log-on message and return the message that succeeds in registration.
Said finger daemon module can further include:
Services request inspection module is used for checking whether database exists specified ISP of client and service content.
The inter-process communication methods of a kind of application software disclosed by the invention and system because have the finger daemon module, utilize the network service API of operating system bottom, for carrying out the communication of operating system independent between different client processes; When the technical staff relates to the software project of communication in exploitation, needn't be every kind of operating system stand-alone development one cover code all, reduce the complexity of code, reduce Development of Software and maintenance cost.
Description of drawings
Fig. 1 is the flow chart of inter-process communication methods of the present invention.
Fig. 2 is the data structure sketch map of finger daemon module of the present invention.
Fig. 3 is the register requirement method flow diagram afterwards of finger daemon resume module client process of the present invention.
Fig. 4 is the method flow diagram of the register requirement of finger daemon resume module client process of the present invention.
Fig. 5 is the method flow diagram of finger daemon resume module user's of the present invention services request.
Fig. 6 is the block diagram of the interprocess communication system of application software of the present invention.
Embodiment
Below in conjunction with accompanying drawing and embodiment the present invention is done further explain.
Each different operating systems is basically all followed the Unix network communications standards at present, though may there be different encapsulation in different operating systems, the network service API of bottom is basic identical.The present invention has utilized the consistent situation of the bottom-layer network of different operating system communication API, through the encapsulation of inside, has formed and the irrelevant convenient and practical inter-process communication mechanisms of underlying operating system.At first introduce the interprocess communication system of operating system independent of the present invention below.
The present invention adopts as gives a definition: finger daemon, this process are responsible for receiving client enrollment/cancel, forwards, system message broadcasting and are realized client's monitoring.Client process, the promoter or the recipient of representative communication.
The present invention discloses a kind of inter-process communication methods of operating system independent, not direct communication between the client process, but through the finger daemon forwarding information, the network service API through bottom between finger daemon and the client process gets in touch.The finger daemon module is used to receive client's log-on message, the service request information of monitoring, forwarding and customer in response; In order to make the present invention be convenient to understand, below earlier the finger daemon module is elaborated.
As shown in Figure 1 is the flow chart of inter-process communication methods of the present invention, and as one embodiment of the present of invention, the communication between client process A and the client process B may further comprise the steps:
1, client process A carries out client enrollment to the finger daemon module;
2, the finger daemon module is returned the client process A information that succeeds in registration;
3, client process A proposes services request to the finger daemon module;
4, the finger daemon module proposes services request to client process B;
5, client process B returns result to the finger daemon module;
6, the finger daemon module is returned result to client process A.
As shown in Figure 2 is the data structure sketch map of finger daemon module of the present invention; Said finger daemon module stores has client's log-on message, the number of users of current register and the system broadcast message number of current register, said client's log-on message comprise service that customer name, client provide, client the broadcast that will respond.Each client can be with the title of oneself, own available service and own will corresponding broadcast being registered in the finger daemon module; Thereby the finger daemon module can start the supervision to client's behavior; When a client need use the service of another client enrollment, the finger daemon module can provide related service for this client.
The finger daemon module starts and sets up a socket, is used to monitor and wait for client's register requirement and services request.
There is client process A to send register requirement among Fig. 2, comprises client's log-on message in the request to said finger daemon module.
Client process A when registration, the log-on message that needs to submit to comprise customer name, the available service of client self and client the broadcast that will respond, this service that can provide is a kind of incessantly, more than one of the broadcast that respond.The finger daemon module can be according to the information of client process A registration, for client process A sends its broadcast that need listen to like this.Simultaneously, when other clients needed client process A that service is provided, the finger daemon module can be transmitted the service content of client A for other clients.
Said finger daemon module monitors is saved in the log-on message of said client A in the database and returns the message that succeeds in registration after the register requirement of client A.
Understand easily, the above-mentioned functions of finger daemon module can realize through various programming languages, is example with the JAVA programming language below, introduces the implementation method of finger daemon module.The implementation method of said finger daemon module is following:
At first define the data structure that is used to receive and store client enrollment information in the finger daemon module, concrete JAVA code is:
Struct?client_register
{
String?registerName;
Unsigned int registerID; // finger daemon distributes
。。。。。。。。。// other data members
List < struct server*>listServer; The service chained list that // client registered
List < struct signal*>listSignal; The broadcast chained list of the needs response that // client registered
};
Struct?daemon_register
{
String version; // current version
Unsigned int startTime; // finger daemon start-up time
Unsigned int clientNum; The number of users of // current register
Unsigned int signalNum; The system broadcast message number of // current register
List < struct client_register*>listClient; // current client enrollment information chained list
// other data members
}
Define each basic interface in the finger daemon module then; Comprise customer information registration interface, broadcast registration interface, broadcast transmission interface, message request interface, message sink interface, message transmission interface; Be used to monitor, the service request information of forwarding and customer in response, perhaps the log-on message according to the client directly sends the needed broadcast of client for the client.The define method of described each interface is following:
Int?register(const?char*?pRegisterName)
Function: customer information registration
Parameter: const char* pRegisterName representes login name
Return value: 0 representes successfully, greater than 0 expression error code;
Int?register_signal(const?char*?pRegisterName)
Function: broadcast registration
Parameter: const char* pRegisterName representes the broadcast name
Return value: 0 representes successfully, greater than 0 expression error code;
Int?register_call(const?char*?pRegisterName)
Function: message request
Parameter: const char* pRegisterName representes message name
Return value: 0 representes successfully, greater than 0 expression error code;
Int?message_receive(MESSAGE*?pMsg)
Function: message sink
Parameter: MESSAGE* pMsg representes the message that receives
Return value: 0 representes successfully, greater than 0 expression error code;
Void?signal_send(MESSAGE*?pMsg)
Function: broadcast is sent
Parameter: the broadcast that MESSAGE* pMsg indicates to take place
Return value: do not have;
MESSAGE*?call_send(MESSAGE*?pMsg)
Function: message is sent
Parameter: the message that MESSAGE* pMsg indicates to send
Return value: the result of returning;
The data structure and the interface definition of finger daemon module of the present invention have below been introduced in detail; Through the finger daemon module; No matter client A and client process B can communicate, and that is to say that the process of client A can directly carry out communicating by letter of operating system independent with the process of client process B.Data structure is a term in the software; The data structure definition of finger daemon module is the key that its function realizes.
Shown in Figure 3 is the method flow diagram of finger daemon module of the present invention monitor communication demand after client A registration connects; After client A registration is accomplished, the finger daemon module keep watch on through socket and etc. to be connected, judge whether new client requests repeatedly, have and then create new thread, and through this new thread of finger daemon resume module.
Shown in Figure 4 is the flow chart of the thread of finger daemon resume module registration request from user of the present invention; The finger daemon module monitors can be created a new thread after have a client to send register requirement, and simultaneously said socket continues the register requirement that other clients of monitoring send.After said new thread is created; Whether the customer name of at first checking said client A registration exists; If had information from registration failure to said client A that then return, otherwise the log-on message of client A is added in the database, the log-on data that renewal is relevant is simultaneously also returned and is succeeded in registration.In the embodiment of the invention, database can realize that for example, the service of client enrollment (being the available service of client self) can be kept in the service chained list with the structure chained list, and the client wants corresponding broadcast then to be kept in the broadcast chained list.
Shown in Figure 5 is the method flow diagram of finger daemon resume module user's of the present invention services request.Client A sends services request to said finger daemon module, requires to return one or more services that client B provides.
Said finger daemon module checks at first whether client B exists, and does not exist, and then returns failure information.And then check that whether client B exists this service, does not exist and then returns failure information.
Said finger daemon module is transmitted the services request that said client A sends to said client B after receiving the services request that said client A sends.
Said client B handles the services request that said client A sends, and result is returned to said finger daemon module.
If said client B need not to handle the services request of said client A, then flow process finishes.
Said finger daemon module returns to said client A with the result of said client B.
As shown in Figure 6 is the block diagram of the interprocess communication system of application software of the present invention.Comprise the steps:
The finger daemon module starts and sets up a socket, is used to monitor and wait for client's register requirement and services request.
Client A sends register requirement to said finger daemon module, comprises client's log-on message in the request.
Said finger daemon module monitors is saved in the log-on message of said client A in the database and returns the message that succeeds in registration after the register requirement of client A.
Client A sends services request to said finger daemon module, requires to return one or more services that client B provides.
Said finger daemon module is transmitted the services request that said client A sends to said client B after receiving the services request that said client A sends.
Said client B handles the services request that said client A sends, and result is returned to said finger daemon module
Said finger daemon module returns to said client A with the result of said client B.
In sum; The present invention can establish a communications link for the client who is positioned at different operating system through finger daemon module of definition, that is to say between different clients' process and can carry out the communication of operating system independent; Thereby the technical staff is when exploitation communication class project; Needn't be every kind of operating system exploitation one cover code, can reduce the complexity of code, reduce development and maintenance cost.
The above is merely preferred embodiment of the present invention, not in order to restriction the present invention, all any modifications of within spirit of the present invention and principle, being done, is equal to and replaces and improvement etc., all should be included within protection scope of the present invention.
Claims (9)
1. the inter-process communication methods of an application software is used for the communication between client process A and the client process B, perhaps client process A and the client process B broadcast service that will respond respectively; It is characterized in that: may further comprise the steps:
Steps A: client process A sends services request to the finger daemon module, requires to return one or more services that client process B provides;
Step B: said finger daemon module is transmitted to said client process B after receiving the services request that said client process A sends;
Step C: said client process B receives and handles the services request of said client process A, and result is returned to said finger daemon module;
Step D: said finger daemon module returns to said client process A with the result of said client process B.
2. the inter-process communication methods of operating system independent according to claim 1 is characterized in that, and is further comprising the steps of before said steps A:
Said finger daemon module starts and sets up a socket, is used to monitor and wait for client's register requirement and services request;
Said client process A sends register requirement to said finger daemon module, comprises client's log-on message in the request;
Said finger daemon module monitors is saved in the log-on message of said client process A in the database and returns the message that succeeds in registration after the register requirement of client process A.
3. the inter-process communication methods of operating system independent according to claim 2 is characterized in that: comprise in the said log-on message service that customer name, client provide and client the broadcast that will respond.
4. the inter-process communication methods of operating system independent according to claim 2; It is characterized in that: said finger daemon module monitors is after the register requirement of client process A; Whether the customer name of at first checking said client process A registration exists, if there has been information from registration failure to said client process A that then return.
5. the inter-process communication methods of operating system independent according to claim 1; It is characterized in that: in said step B; After said finger daemon module is received the services request that said client process A sends; At first check the log-on message that whether has client process B in the data,, otherwise get into following steps if there is not the information of then returning the services request failure to said client process A:
Further whether there is said client process A requested service in the log-on message of inspection client process B; If exist the services request of then said client process A being sent to be transmitted to said client process B, otherwise return the information of services request failure to said client process A.
6. the interprocess communication system of an application software is characterized in that: comprise the finger daemon module, be used to receive client's log-on message, the service request information of monitoring, forwarding and customer in response; Said finger daemon module further comprises:
The services request receiver module is used to receive one or more services request that the client sends;
The services request forwarding module is used for one or more services request that said client sends are transmitted to the ISP;
The service result receiver module is used to receive the service response result that said ISP provides;
Service result is returned module, is used for the service response result that said ISP provides is returned to said client;
Said services request module, said services request forwarding module and said service requester are linked in sequence, and said service requester also returns sequence of modules with said service result receiver module, said service result and is connected.
7. interprocess communication according to claim 6 system, it is characterized in that: said finger daemon module also comprises:
The socket module is used to monitor and wait for register requirement and the services request that the client sends;
The register requirement receiver module is used to receive the register requirement that the client sends.
8. interprocess communication according to claim 7 system, it is characterized in that: said finger daemon module also comprises:
The log-on message processing module is used to check whether the customer name of client enrollment exists, and then returns the information of registration failure to said client if exist, otherwise preserves said client's log-on message and return the message that succeeds in registration.
9. according to each described interprocess communication system of claim 6 to 8, it is characterized in that: said finger daemon module also comprises:
Services request inspection module is used for checking whether database exists specified ISP of client and service content.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011101602851A CN102833080A (en) | 2011-06-15 | 2011-06-15 | Process-to-process communication method of application software and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011101602851A CN102833080A (en) | 2011-06-15 | 2011-06-15 | Process-to-process communication method of application software and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102833080A true CN102833080A (en) | 2012-12-19 |
Family
ID=47336060
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2011101602851A Pending CN102833080A (en) | 2011-06-15 | 2011-06-15 | Process-to-process communication method of application software and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102833080A (en) |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104852931A (en) * | 2015-06-12 | 2015-08-19 | 北京京东尚科信息技术有限公司 | Communication method and device |
| WO2015135221A1 (en) * | 2014-03-12 | 2015-09-17 | 深圳创维－Rgb电子有限公司 | Inter-process communication method based on application layer of android and basic application communication system |
| CN105068870A (en) * | 2015-09-29 | 2015-11-18 | 北京网诺星云科技有限公司 | Method and device for multi-language information switching |
| CN105471718A (en) * | 2015-12-22 | 2016-04-06 | 积成电子股份有限公司 | Realization method of full duplex message queue |
| CN106776063A (en) * | 2016-11-29 | 2017-05-31 | 北京元心科技有限公司 | Mobile terminal, container telephonic communication function realizing method and across container communication means |
| CN107070670A (en) * | 2017-03-10 | 2017-08-18 | 广东欧珀移动通信有限公司 | Broadcast transmission person is controlled to send method, device and the terminal device of broadcast message |
| CN107135251A (en) * | 2017-04-18 | 2017-09-05 | 北京思特奇信息技术股份有限公司 | A kind of home location register instruction agency retransmission method and system |
| CN107665148A (en) * | 2016-07-28 | 2018-02-06 | 中国科学院声学研究所 | A kind of name pipeline Way of Process Communication based on Chromium |
| CN108833578A (en) * | 2018-06-30 | 2018-11-16 | 武汉斗鱼网络科技有限公司 | The method and relevant device of duplex communication are carried out based on FIFO name pipeline |
| CN110691002A (en) * | 2018-07-05 | 2020-01-14 | 武汉斗鱼网络科技有限公司 | Interrupt detection method and device |
| CN113032170A (en) * | 2021-05-31 | 2021-06-25 | 天地伟业技术有限公司 | Multi-module communication processing method of network camera and electronic equipment |
| CN113032161A (en) * | 2019-12-25 | 2021-06-25 | 北京比特大陆科技有限公司 | Process communication method and related product |
| CN113722128A (en) * | 2021-07-12 | 2021-11-30 | 北京鲸鲮信息系统技术有限公司 | Method and device for acquiring positioning information, electronic equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101419535A (en) * | 2008-11-19 | 2009-04-29 | 北京航空航天大学 | Distributed virtual magnetic disc system of virtual machine |
| CN101739300A (en) * | 2008-11-18 | 2010-06-16 | 中兴通讯股份有限公司 | Method and system for inter-process communication of multimedia terminal |
-
2011
- 2011-06-15 CN CN2011101602851A patent/CN102833080A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101739300A (en) * | 2008-11-18 | 2010-06-16 | 中兴通讯股份有限公司 | Method and system for inter-process communication of multimedia terminal |
| CN101419535A (en) * | 2008-11-19 | 2009-04-29 | 北京航空航天大学 | Distributed virtual magnetic disc system of virtual machine |
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015135221A1 (en) * | 2014-03-12 | 2015-09-17 | 深圳创维－Rgb电子有限公司 | Inter-process communication method based on application layer of android and basic application communication system |
| CN103902390B (en) * | 2014-03-12 | 2017-04-19 | 深圳创维－Rgb电子有限公司 | Inter-process communication method based on Android application layer and basis application communication system |
| US9923992B2 (en) | 2014-03-12 | 2018-03-20 | Shenzhen Chuangwei-Rgb Electronic Co., Ltd. | Inter-process communication method based on application layer of android and basic application communication system |
| CN104852931A (en) * | 2015-06-12 | 2015-08-19 | 北京京东尚科信息技术有限公司 | Communication method and device |
| CN105068870A (en) * | 2015-09-29 | 2015-11-18 | 北京网诺星云科技有限公司 | Method and device for multi-language information switching |
| CN105068870B (en) * | 2015-09-29 | 2019-07-26 | 北京网诺星云科技有限公司 | The method and device of multilingual information switching |
| CN105471718B (en) * | 2015-12-22 | 2018-10-19 | 积成电子股份有限公司 | A kind of implementation method of full duplex message queue |
| CN105471718A (en) * | 2015-12-22 | 2016-04-06 | 积成电子股份有限公司 | Realization method of full duplex message queue |
| CN107665148B (en) * | 2016-07-28 | 2020-06-16 | 中国科学院声学研究所 | Named pipeline process communication method based on Chromium |
| CN107665148A (en) * | 2016-07-28 | 2018-02-06 | 中国科学院声学研究所 | A kind of name pipeline Way of Process Communication based on Chromium |
| CN106776063A (en) * | 2016-11-29 | 2017-05-31 | 北京元心科技有限公司 | Mobile terminal, container telephonic communication function realizing method and across container communication means |
| CN106776063B (en) * | 2016-11-29 | 2020-12-01 | 北京元心科技有限公司 | Mobile terminal, container telephone communication function implementation method and cross-container communication method |
| CN107070670A (en) * | 2017-03-10 | 2017-08-18 | 广东欧珀移动通信有限公司 | Broadcast transmission person is controlled to send method, device and the terminal device of broadcast message |
| CN107135251A (en) * | 2017-04-18 | 2017-09-05 | 北京思特奇信息技术股份有限公司 | A kind of home location register instruction agency retransmission method and system |
| CN108833578A (en) * | 2018-06-30 | 2018-11-16 | 武汉斗鱼网络科技有限公司 | The method and relevant device of duplex communication are carried out based on FIFO name pipeline |
| CN108833578B (en) * | 2018-06-30 | 2021-07-23 | 武汉斗鱼网络科技有限公司 | Method and related equipment for duplex communication based on FIFO named pipeline |
| CN110691002A (en) * | 2018-07-05 | 2020-01-14 | 武汉斗鱼网络科技有限公司 | Interrupt detection method and device |
| CN110691002B (en) * | 2018-07-05 | 2021-07-23 | 武汉斗鱼网络科技有限公司 | Interrupt detection method and device |
| CN113032161A (en) * | 2019-12-25 | 2021-06-25 | 北京比特大陆科技有限公司 | Process communication method and related product |
| CN113032161B (en) * | 2019-12-25 | 2024-06-04 | 北京比特大陆科技有限公司 | Process communication method and related product |
| CN113032170A (en) * | 2021-05-31 | 2021-06-25 | 天地伟业技术有限公司 | Multi-module communication processing method of network camera and electronic equipment |
| CN113722128A (en) * | 2021-07-12 | 2021-11-30 | 北京鲸鲮信息系统技术有限公司 | Method and device for acquiring positioning information, electronic equipment and storage medium |
| CN113722128B (en) * | 2021-07-12 | 2024-08-13 | 北京字节跳动网络技术有限公司 | Method and device for acquiring positioning information, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102833080A (en) | Process-to-process communication method of application software and system | |
| CN103927218B (en) | Event distributing method and system | |
| US10673969B2 (en) | Scalable data feed system | |
| JP2022104926A (en) | System for and method of initiating external action through group-based communication system | |
| CN101689169B (en) | Management of external hardware appliances in a distributed operating system | |
| US20120016999A1 (en) | Context for Sharing Data Objects | |
| JP2005539298A (en) | Method and system for remotely and dynamically configuring a server | |
| US9053444B2 (en) | Deploying applications in a smart thin client server | |
| CN103580937A (en) | Web service simulating method and system and service agent system thereof | |
| EP3436935A1 (en) | Pre-formed instructions for a mobile cloud service | |
| WO2013023095A2 (en) | Smart thin client server | |
| CN112689020B (en) | Message transmission method, message middleware, electronic equipment and storage medium | |
| US20030208537A1 (en) | Real-time data collection and distribution among office productivity software applications | |
| US8271574B1 (en) | Content sharing and collaboration | |
| US10489179B1 (en) | Virtual machine instance data aggregation based on work definition metadata | |
| US8694462B2 (en) | Scale-out system to acquire event data | |
| CN112838935B (en) | Electronic data exchange method and system | |
| CN114416169A (en) | Data processing method, medium, device and computing equipment based on micro front end | |
| JP5961471B2 (en) | Output comparison method in multiple information systems | |
| US20080071916A1 (en) | System and method for requesting a web service from a network server | |
| CN113472638B (en) | Edge gateway control method, system, device, electronic equipment and storage medium | |
| CN112511636B (en) | Data transmission system, method, device, computer equipment and storage medium | |
| CN107330089B (en) | Cross-network structured data collection system | |
| US10733002B1 (en) | Virtual machine instance data aggregation | |
| US20070005728A1 (en) | System and method of queued web services |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20121219 |