CN101917394A - Middleware system and working method for data sharing on mobile devices - Google Patents

Abstract

The invention discloses a middleware system and a working method for data sharing on a mobile phone device. The system is applied to a system composed of at least one server and more than two clients running on the mobile phone; the client includes a client Project management unit, client message conversion unit, client cache unit, client communication unit, client DOM operation unit, client resolution strategy unit, client conflict resolution unit; the server has: server message queue management unit, server The storage unit on the server side, the communication unit on the server side, the policy resolution unit on the server side, the DOM operation unit on the server side, and the conflict resolution unit on the server side. Through the data transmission and processing of the above-mentioned units, the two terminals can send messages to each other, process the received messages, and then continue to send the processed messages, and the program can be rolled back, which also ensures the communication between the two terminals. Two-way synchronization of messages between

Description

Middleware system and working method for data sharing on mobile devices

technical field

The invention relates to a middleware system running on a mobile phone device, more specifically to a computer software system and a working method in a distributed environment composed of mobile phones.

Background technique

Wired network, also known as fixed network, is a relatively persistent physical network composed of a series of fixed hosts connected together through high-bandwidth network cables and networking equipment. Such an operating environment requires distributed applications to consider: (1) scalability, which refers to the ability to accommodate higher loads for a period of time in the future; (2) openness, which refers to the ability to update when functional requirements change Easy to expand and modify the system; (3) Heterogeneity means that the different components integrated in the distributed system are written in different programming languages, run on different operating systems, and run on different hardware (4) fault tolerance, which means that when the system fails, it can automatically recover without stopping the operation of the entire system; (5) resource sharing and access control, that is, both hardware and software resources can be used by different systems of users conditionally share. Middleware is created to solve these problems. It is on top of the network operating system and hides the complexity of distributed systems from developers. The middleware systems that should succeed in fixed network environments include OMG CORBA, Microsoft COM, Sun Java/RMI and IBM MQSeries, etc.

In recent years, due to the popularity of mobile devices such as PDAs, mobile phones, and notebook computers, as well as the rapid development of wireless networks, mobile applications are constantly approaching people's work and life. Due to the mobility of equipment and limited resources, mobile wireless networks are different from traditional fixed networks in that the network structure is not fixed and the network connectivity is poor. Coupled with the limited computing power of mobile devices and strong device heterogeneity, middleware systems on fixed networks are completely unsuitable for mobile wireless networks.

Lightweight mobile middleware is produced under this background. Mobile middleware is located between the mobile network, operating system, and mobile application software. It uses the basic functions and services provided by the underlying operating system, and provides the upper mobile application system with abstracted from general application requirements and required by mobile network applications through APIs. Higher-level, general-purpose functions and services required.

More mature mobile middleware includes context-aware middleware and data sharing middleware. Context-aware middleware enables mobile applications to be aware of contextual information such as location, device status, and user behavior. Location information is the most researched aspect of context-aware middleware. There are many mature applications, such as CyberGuide that provides travel guides, Object Pager that can send advertisements, and Conference Assistant that sends messages to anyone in a specific area. Data sharing middleware allows users to work offline and share data when they are connected again. More excellent data sharing middleware include Coda, Odyssey, Bayou and Xmiddle. They both maximize data availability, but their mechanisms for detecting and resolving conflicts differ. Odyssey is more suitable for mobile environments than its predecessor Coda, but because it requires greater computing power; Bayou uses application-related knowledge for dependency checking, which may be affected by cascading conflict resolution; Xmiddle uses XML to describe information, using DOM to operate on the data. Other data sharing middleware such as Coda and Odyssey need to copy the entire file once when copying data, while Xmiddle can simply adjust the copy unit to meet different needs, and is more suitable for mobile devices with limited storage capacity.

Message is an effective way for heterogeneous systems to exchange data, which can be understood by different applications, and heterogeneous systems can communicate by exchanging messages. Messaging middleware (MOM) supports cross-platform message delivery between distributed application software through message queue and subscribe/publish mode. Compared with remote procedure call (RPC), PRC is like making a phone call, while MOM is like sending an email. It does not need to be instant, but can be processed intermittently and afterwards in batches. MOM has the characteristics of loose coupling and asynchronous communication, which makes it especially suitable for the mobile network environment with poor network connectivity. However, the existing message middleware (such as IBM MQSeries, etc.) all run on a fixed host on a fixed network, which requires high equipment capabilities and is not suitable for mobile devices. They only perform simple one-way replacement for messages with the same keyword, so they do not support data sharing.

Contents of the invention

In view of the above problems, the present invention develops a set of mobile message middleware system and method that can run on mobile phone equipment. The technical means adopted in the present invention are as follows:

A middleware system for data sharing on mobile devices, characterized in that the system is applied to a system composed of at least one server and more than two clients running on mobile devices;

The clients include:

The client project management unit is used for users to edit messages, configure communication objects and communication mode parameters;

The client message conversion unit is used to convert the message edited by the user into a message in XML format, and continue to convert the message into a tree form;

The client cache unit is used to store the user's local data, so that the user can operate and modify the data offline, and store the server-side data frequently accessed by the client locally;

The client communication unit is used to enable the user to communicate with other clients or servers;

The client DOM operation unit is used to add and modify messages in the tree structure in XML format, and to parse messages sent by other terminals;

The client resolution strategy unit is used to define a conflict resolution strategy for the conflict nodes in the message converted by the message conversion unit into a tree form;

The client-side conflict resolution unit is used to call the client-side DOM operation unit to process the XML message, and then call the client-side resolution strategy unit to resolve the conflict according to the previously defined conflict resolution strategy;

a display unit, configured to display the result to the user;

The server side has:

The server-side message queue management unit is used to manage the messages of the server and control the sending and receiving of messages between the server and other terminals;

A server-side storage unit for storing messages in a database;

a server-side communication unit for enabling the server to communicate with other clients or servers;

The server-side resolution strategy unit is used to define a conflict resolution strategy for the conflict nodes in the message in the form of a tree;

The server-side DOM operation unit is used to add and modify messages in a tree structure in XML format, and to parse messages sent by other terminals;

The server-side conflict resolution unit is used to call the server-side DOM operation unit to process the XML message, and then call the server-side resolution strategy unit to resolve the conflict according to the previously defined conflict resolution strategy;

A client of the middleware system is used as the sender of the message, and its client message conversion unit converts the message into XML format after receiving the message edited by the user using the project management unit of the client, and then uses the client to digest the message. The strategy unit adds a conflict resolution strategy for nodes that may cause conflicts, and then sends messages through the client communication unit; the server or another client receives the message, and the server or another client’s DOM operation unit responds to the message Perform related DOM operations, that is, the DOM operation unit of the receiver compares two XML messages with different tree structures to generate a diff tree to record the conflicts generated by the two different messages; then the conflict resolution unit in the receiver resolve the conflict, generate a new tree without conflict, and then send the tree to the sender; if this process occurs between two mobile clients, store the result in the client cache unit, and Displayed by the display unit; if this process occurs between the mobile client and the server, the server stores the message in the database of the server-side storage unit, and the server-side message queue management unit stores the message Messages are sent to all subscribers via the server-side communication unit.

The client cache unit includes a temporary message queue, and the client puts messages into the message queue, so that the message queue actively sends or receives messages according to the protocol set by the client communication unit; each message A sending terminator is attached to each of them. When the message is sent to the terminator, it is considered that the message is sent successfully, otherwise it is considered that the message is sent as a failure, and the message is resent or processed in the next step.

The server message queue management unit includes a thread pool and a work queue, and the work queue listens to the received request, and then takes out a thread from the thread pool to communicate with the corresponding terminal according to the priority; each thread communicates with the terminal When communicating, it includes a message queue similar to the client, which is used to actively send or receive messages, and save the received messages in the database; when the confirmation information is not received within a given time, the processing method of the server Yes: For persistent subscribers, if the terminal is disconnected, the server will store the message, and when he connects again, the server will send the message to the subscriber again; for non-persistent subscribers, disconnection is means failure, the server deletes the subscription information, and if the subscriber wants to continue receiving messages, he needs to send the subscription information again.

The sender communicates with the receiver through the communication unit, and the sender first sends a discovery request message. If the receiver receives this message, it will return a confirmation code to the sender, and the sender will send all versions of the message stored by itself. Both are sent to the receiver; if the receiver does not receive the discovery request message or the sender does not receive the confirmation code, the sender needs to resend the discovery request message to the receiver.

A kind of working method of the middleware system that carries out data sharing on mobile phone equipment, it is characterized in that comprising the following steps:

Step 1: According to the specific application, the user edits the message through the project management unit of the client, and designs the configuration information accordingly;

Step 2 The client converts the message edited by the user into a message in XML format through the client message conversion unit, and stores the message in the client cache unit; then continues to convert the message into a tree form, and then according to the specific application, Define a conflict resolution strategy for each node that may cause conflicts through the client resolution strategy unit, and add a node to the tree through the client DOM operation unit, which records the conflict resolution strategy; when a conflict occurs, the application The conflict resolution strategy defined by this node should be adopted to resolve conflicts;

Step 3 When the client as the sender starts to communicate with another terminal as the receiver through the client communication unit, the sender first sends a discovery request message, and if the receiver receives this message, it will return a confirmation code to the sender, indicating At this time, the sender and the receiver can communicate, and the sender will send all versions of the messages stored by itself to the receiver; if the receiver does not receive the discovery request message or the sender does not receive the confirmation code, it needs to re- Send a discovery request message;

Step 4 After receiving all versions of the messages stored by the sender, the receiver parses these messages through the DOM operation unit of the server or another client, and compares them with the messages stored by itself. At this time, if the sender and the receiver If one of the parties has modified the message, a conflict will be found during comparison, and the receiver will record these conflicts;

Step 5. According to the resolution strategy node of the conflict node defined in step 2, the receiver calls the resolution strategy defined in advance through the resolution strategy unit of the server or another client, and the conflict resolution unit of the server or another client The conflict is resolved, and the new message after the conflict is recorded;

Step 6 If the receiver is a mobile client, the receiver stores the new message in the cache through the client cache unit, and returns the new message to the sender through the client communication unit, and the sender records the conflict resolution and stored in the cache, and then handed over to the client display unit to display the results;

Step 7: If the recipient is a server, the recipient processes the message through the server-side message queue management unit, packs the message into a message recognizable by the server, and then stores the message in the database through the server-side storage unit;

Step 8 Then the server sends the updated message to all subscribers through the server-side communication unit, so that the messages in all subscribers are kept synchronized.

Compared with the prior art, the middleware system and working method for data sharing provided by the present invention are obvious, as follows:

(1) Make the message middleware support the mobile distributed environment. Different from the traditional message middleware, the present invention supports the mobile network environment. Aiming at the particularity of the mobile network and the characteristics of the mobile phone device, it can run on the real hardware environment of the mobile phone device and the Java virtual operating environment. It provides a reliable means of data communication for mobile applications under continuous network connection conditions.

(2) Effectively ensure the successful sending and receiving of shared data and the consistency of data, and support data sharing. The two terminals send messages to each other, process the received messages, and then continue to send the processed messages, and when there is a problem in this process, the program rolls back accordingly, which also ensures the two-way message between the two terminals Synchronization, not simple message replacement.

Description of drawings

Fig. 1 is the overall structure schematic diagram of the system of the present invention;

Fig. 2 is a schematic structural diagram of a mobile client of the system of the present invention;

Fig. 3 is a schematic diagram of the server-side structure of the system of the present invention;

Fig. 4 is the work flowchart of system of the present invention;

Fig. 5 is a working flow chart of the implementation device of the system design of the present invention.

Detailed ways

The invention provides an implementation system of message middleware for supporting mobile environment. Physically, this system can be divided into server end (background computer) and client (mobile phone equipment) two parts, both are connected together by communication protocols such as wireless network, bluetooth, wherein the message middleware of the present invention is running on the background computer The server part and the mobile client part run on the mobile device. Data sharing between two mobile devices can be implemented, and they can directly communicate point-to-point without going through a server; data sharing between a server and multiple mobile devices can also be implemented, which is combined with message middleware Completed by the publish/subscribe method above. You can choose to communicate with the mobile application on the mobile device through protocols such as TCP/IP, HTTP or Bluetooth.

As shown in Figure 1, the middleware system for data sharing on the mobile device is applied to a system consisting of at least one server and more than two clients running on the mobile device;

As shown in Figure 2, the client includes:

The client project management unit 100 is used for users to edit messages, configures communication objects and communication mode parameters, and is composed of PanelManager and ClientEdit classes; the client message conversion unit 101 is used to convert the messages edited by users into messages in XML format, and Continue to convert this message into a tree form, which is composed of TransformMessage and ExportLink; the client cache unit 102 is used to enable the user to modify the data offline, and store the server-side data frequently accessed by the client locally. To prevent the client from frequently accessing the server and saving network bandwidth, it is composed of the RecordStoreOperation class; the client resolution strategy unit 103 is used to define a conflict resolution strategy for the conflict nodes in the message that the message conversion unit converts into a tree form, that is, according to the specific The application to define different conflict resolution strategies, such as adding, modifying, replacing, etc., is composed of TreeDiff, TreeMerge, TreeReplica, and ListEntry classes; the client DOM operation unit 104 is used for adding and Modify the operation, and analyze the messages sent by other terminals, such as comparing the differences between the two trees, modifying the nodes, etc.; by XMLTranslator, MessageHead, MessageBody, Message, NeedToShare, DiscoveryRequest, AgentConnected, AgentDisconnected, EditionIdentifier, LinkedTableMessage , LinkedFrom, ConfirmMessage, TlistOfEI, NewChanges, and Acknowledge classes; the client conflict resolution unit 105 is used to call the client DOM operation unit to process the XML message, and then call the client resolution strategy unit to resolve conflicts according to the pre-defined conflicts Strategies to resolve conflicts, composed of Reconcile, ReplaceStrategy, MinusStrategy, AddStrategy classes; client communication unit 106, used to enable users to use certain communication protocols, such as Http, bluetooth, etc., to communicate with other clients or servers, by Observer , Protocol, Subject interface, Transport, ProSocket, ProHttp, ProBluetooth, Agent, ConnectAgent, ReconcileAgent, ExchangeInfoAgent, ConfirmChangesAgent, ListEIAgent, NewCha Composed of ngesAgent, AckAgent, and Terminate classes; on-board application program management unit 107, provided by mobile device manufacturers, for managing the download, decompression, installation, deletion, and operation of Java Me mobile applications; display unit 108, for displaying the results to the user .

As shown in Figure 3, the server side includes:

The server-side communication unit 206 is used to enable the server to communicate with other clients or servers; the server-side resolution strategy unit 205 is used to define a conflict resolution strategy for the conflicting nodes in the message of the tree form; the server-side DOM operation unit 204, It is used to add and modify the message of the tree structure in XML format, and parse the message sent by other terminals; the server-side conflict resolution unit 203 is used to call the server-side DOM operation unit to process the XML message, and then The server-side resolution strategy unit is invoked to resolve conflicts according to the pre-defined conflict resolution strategy; the components of the above-mentioned units are basically the same as those of the client, and will not be repeated here. Wherein the server-side storage unit 202 is used to store the message in the database, and supports the operation of the message in the database; it is composed of class FileOperation and DatabaseOperation; the server-side message queue management unit 201 is used to manage the messages of the server, and The control server sends and receives messages with other terminals, and consists of classes Start, Init, StartXMLTranslator, and ThreadPool.

A client of the middleware system is used as the sender of the message, and its client message conversion unit converts the message into XML format after receiving the message edited by the user using the project management unit of the client, and then uses the client to digest the message. The strategy unit adds a conflict resolution strategy for nodes that may cause conflicts, and then sends messages through the client communication unit; the server or another client receives the message, and the server or another client’s DOM operation unit responds to the message Perform related DOM operations, that is, the DOM operation unit of the receiver compares two XML messages with different tree structures to generate a diff tree to record the conflicts generated by the two different messages; then the conflict resolution unit in the receiver resolve the conflict, generate a new tree without conflict, and then send the tree to the sender; if this process occurs between two mobile clients, store the result in the client cache unit, and Displayed by the display unit; if this process occurs between the mobile client and the server, the server stores the message in the database of the server-side storage unit, and the server-side message queue management unit stores the message Messages are sent to all subscribers via the server-side communication unit.

In addition, the client cache unit includes a temporary message queue, and the client puts messages into this message queue, so that the message queue actively sends or receives messages according to the protocol set by the client communication unit, so as to prevent When the condition is not good, the client blocks and waits; each message is attached with a sending terminator. When the message is sent to the terminator, it is considered that the message is sent successfully, otherwise it is considered that the message is sent as failed, and the message is resent or processed in the next step. The server message queue management unit includes a thread pool and a work queue. The work queue monitors the received request, and then takes out a thread from the thread pool to communicate with the responding terminal according to the priority, so that the server can be used in multiple In the case of a thread, it communicates messages with multiple terminals at the same time; when each thread communicates with a terminal, it contains a message queue similar to the client, which is used to actively send or receive messages, but the received messages will not Then save it in the cache, but in the database; when the confirmation message is not received within a given time, the processing method of the server is: for persistent subscribers, if the terminal is disconnected, the server will store the message, When he connects again, the server will send the message to the subscriber again; for non-durable subscribers, disconnection means failure, and the server will delete the subscription information. If the subscriber wants to continue to receive messages, then he Subscription information needs to be sent again. The sender communicates with the receiver through the communication unit, and the sender first sends a discovery request message. If the receiver receives this message, it will return a confirmation code to the sender, and the sender will send all versions of the message it has stored. To the receiver; if the receiver does not receive the discovery request message or the sender does not receive the confirmation code, the sender needs to resend the discovery request message to the receiver.

The present invention is used to support the working method of the message middleware system design of mobile environment in conjunction with Fig. 4, specifically as follows:

First, according to the specific application, the user edits the message through the client project management unit 100, and correspondingly designs the configuration information, such as which terminal to communicate with, the communication mode and the port (step S301);

The client converts the message edited by the user into a message in XML format through the client message conversion unit 101, and stores the message in the client cache unit 102; then continues to convert the message into a tree form, and then according to specific applications, Define a conflict resolution strategy for each node that may generate conflicts through the client resolution strategy unit 105, and add a node to the tree through the client DOM operation unit 104, which records the conflict resolution strategy; when a conflict occurs, The application program should adopt the conflict resolution strategy defined by this node to resolve the conflict (step S302);

When the client A as the sender starts to communicate with another terminal B as the receiver through the client communication unit 106, the client A (the sender) first sends a discovery request message, and if B (the receiver) receives this message, it will Return a confirmation code to A (sender), indicating that A (sender) and B (receiver) can communicate at this time, and A (sender) sends all versions of the messages stored by itself to B (receiver) If B (receiver) does not receive the discovery request message or A (transmitter) does not receive the confirmation code, it means that the network condition is bad at this time, and then the discovery request message needs to be resent (step S303);

After B (receiver) receives all versions of the messages stored by A (sender), these messages are parsed by the DOM operation unit 104 of the server or another client, and compared with the messages stored by itself, at this time If one of A (sender) and B (receiver) has modified the message, conflicts will be found during comparison, and B (receiver) will record these conflicts (step S304);

B (receiver) calls the resolution strategy defined in advance through the resolution strategy unit of the server end or another client according to the resolution strategy node of the conflict node defined in step S302, and the conflict resolution unit of the server end or another client The conflict is resolved, and the new message after the conflict is recorded (step S305);

If B (receiver) is a mobile client, then B (receiver) stores this new message in the cache through the client cache unit 102, and returns this new message to A (sender) through the client communication unit, A (sender) records the message after the conflict is resolved, and stores it in the cache, and then submits the result to the client display unit 108 to display (step S306);

If B (receiver) is a server, then B (receiver) performs certain processing on the message through the server-side message queue management unit 201, packs the message into a message recognizable by the server, and then stores the message in the server-side storage unit 202. database step 307);

Step 8 Then the server sends the updated message to all subscribers through the server-side communication unit 206, so that the messages in all subscribers are kept synchronized (step 308).

Fig. 5 shows the flowchart of the implementation device of the present invention. The device can be divided into an initiator and a receiver. The initiator is a mobile smart phone, and the receiver can be a mobile smart phone or a message middleware server. The initiator and the receiver communicate via Bluetooth, TCP/IP or HTTP protocol for communication connection.

For convenience, the judgment conditions in Figure 5 are abbreviated as identifiers, where X1 means "whether the receiving end is a server", X2 means "whether the receiving end has received a discovery request message", and X3 means "whether the initiator has received a confirmation code ", X4 means "whether the confirmation code for the successful sending of the new message has been received". As shown in Figure 3, the concrete steps of device of the present invention are:

1. If the user wants to communicate with the server through a mobile smartphone (X1 is true), the server needs to perform a series of initializations, including synchronizing the database with real-time information, setting up the work queue and thread pool. The originator subscribes to the messages it is interested in, or publishes some messages to the server. If the user wants to communicate with another mobile phone through a mobile smart phone (X1 is false), the receiving end and the initiator will edit the message together, and the program will convert the edited message into a machine-recognizable XML format information.

2. The receiving end monitors the port to see if there is any input flow flowing in. The initiator sends a discovery request message. If the receiving end receives the message (X2 is true), it returns a confirmation code after receiving the message, otherwise the receiving end is always in monitoring The state of the port. Similarly, after the initiator sends the discovery request message, it is always in the state of listening to the port until it receives the confirmation code returned by the receiver (X3 is true). Here, if the initiator and the receiver have not received the message for a period of time, it is determined that the current network is not good, and this step needs to be performed again after a period of time.

3. The initiator sends a message that needs to be shared. After receiving the message, the receiving end processes it together with the local message, finds out the conflicts between two different messages, and resolves these conflicts. Then return the new message after the conflict is resolved to the initiator. At this time, the two terminals will send each other a confirmation code for the successful reception of the new message. If the confirmation code is not received within the predetermined time (X4 is false), the program needs to be rolled back, and the execution is restarted from step 2.

4. If the confirmation code is successfully received (X4 is true), the initiator must store the new message in the cache for continued use next time. Similarly, if the receiving end is a mobile smart phone (X1 is false), the receiving end also needs to store the new message in the cache. If the receiving end is a server (X1 is true), the new message needs to be stored in the database, and the server notifies other hosts who subscribe to this message that the data has changed, so that their data is synchronized with the data in the server.

[first embodiment]

The first preferred embodiment of the present invention takes a cooperative electronic shopping system as an example. Many members of a family shop online, each of them has a mobile smart phone, they choose the goods they need individually, and record the selected goods on their personal smart phones, and when they finally pay the bill, they pay together, so it is necessary "Merge" the goods purchased by individuals together, and then use one of the smartphones to make online payments. For example, member A buys 1 bottle of milk and 2 apples, and member B buys 2 bottles of milk. They record these information on their personal smartphones independently. When they want to pay, they first send these goods through the phone " Merge" together, the program merges the messages in the two mobile phones, and the result is 3 bottles of milk and 2 apples, and then A makes the final network payment. The program is mainly composed of Merchandise, Milk, Apple, Parser, ClientPanel, and UploadToPay classes. The purpose of this example implementation is to check whether the execution result of data sharing on the target model SonyEricsson K700C is correct. The specific implementation steps are as follows:

1. Users A and B respectively edit messages under the wizard panel of the client project management unit 100, A edits the message 1 milk and 2 apple, B edits the message 2 milk, and then sets the other party as the communication object, and sets the communication protocol as Bluetooth, After submitting the message, the user can go to other things, such as calling, sending text messages, etc., without waiting.

2. After the program receives the message, it uses the client message conversion unit 101 to parse the message, and the parsed result is {milk: 1, apple: 2} and {milk: 2}, and then converts the message into a message in XML format , the root node is basket, and the message of A is <basket><order><product>milk</product><quantity><howmuch>1</howmuch></quantity></order><order><product>apple </product><quantity><howmuch>2</howmuch></quantity></order></basket>, B's message is <basket><order><product>milk</product><quantity>< howmuch>2</howmuch></quantity></order></basket>, they both store the message in the cache. Afterwards, a conflict resolution strategy add is defined for the quantity node through the client resolution strategy unit 105, which means that when a conflict occurs at the quantity node, the system should adopt an additive strategy to resolve the conflict. Afterwards, a node add is added to each quantity node through the client DOM operation unit 104, which is used for the displayed labeling conflict resolution strategy.

3. Client A starts a communication connection with another terminal B through the client communication unit 106. The local host A first sends a "Discovery Request" message <DiscoveryRequest/>. When the network condition is good, B will receive this message , and return a confirmation code <ConnectAgent/> to A, A will send the stored message to B; when the network condition is bad or the device has a hardware failure, B will not receive the discovery request message or A will not receive the confirmation code, the hardware needs to be processed or the communication connection should be reconnected after a period of time.

4. After B receives A's message, it analyzes these messages through the client DOM operation unit 104, and compares them with the messages stored by itself. B will find that the two messages are different, and at this time a conflict occurs. For: B's milk quantity is 2, A's milk quantity is 1, and B has 2 apples less than A. B records these conflicts.

5. B resolves the conflict at the client conflict resolution unit 103 . First resolve the first half of the conflict, and add the quantity of milk according to the solution strategy node add defined by the quantity node, which is 2+1=3. Then resolve the second half of the conflict, because B has 2 apples less than A, so the apple branch of A is copied to B's message as a whole. The content after the final conflict resolution is 3 milk and 2 apples, which is <basket><order><product>milk</product><quantity><howmuch>1</howmuch></quantity></order>< order><product>apple</product><quantity><howmuch>2</howmuch></quantity></order></basket>.

6. B stores the new message in the cache through the client cache unit 102, so as to be used for subsequent online payment or data sharing with other terminals again, and returns the new message to A through the client communication unit 106, A Record this resolved conflict message and store it in the cache. The system displays the results to the two users respectively through the display unit 108 .

7. A uploads the final result of 3 milks and 2 apples to the Internet via the Internet for online payment.

[Second Embodiment]

The second preferred embodiment of the present invention takes a stock trading system as an example. The user first connects to the message server through the mobile smart phone, and through the mobile phone device to buy and sell stocks, the trading result is notified to the server, and the server further processes this. When there are some major changes in the stock, such as daily limit, lower limit, or dividends, the user can also receive a notification from the server, so that the user can process the change in a timely manner. The program is mainly composed of ClientPanel, StockOperation, Subscribe, and SendToClient. The implementation purpose of this example is to check the completion of the entire stock trading system on the target model SonyEricsson K700C, and whether data sharing can be realized. Whether you can receive the notification from the server in time when the change is made. The specific implementation steps are as follows:

1. Initialize the server first, set up the work queue and thread pool, and combine it with real-time stocks. The server manager will enter the stock information into the server. When the stock information is sent and changed, the stock information in the server will make corresponding changes in time.

2. The user subscribes to the server for the stocks he is interested in through the wizard panel of the project management unit 100 on the project client side, and the server returns the information of these stocks to the user through the server-side communication unit 206. The user can view the stock information on the wizard panel. When the information changes, the server will notify the user in real time, so that the user can further operate on the stock.

3. When the user wants to further operate the stock on the mobile phone, for example, the user already has 200 shares of stock a and buys another 100 shares without changing the price, the user edits through the wizard panel of the project management unit 100 of the client terminal For the corresponding stock information buy 100 for a, select the HTTP method to communicate with the server, and then submit the message.

4. After the program receives the message, it uses the client message conversion unit 101 to parse the message, and the parsed result is {<a, 100, buy>}, and then converts the message into an XML format message, with the root node being stock, , the conversion result is <stock><order><ID>a</ID><quantity><howmuch>100</howmuch></quantity><style>buy</style></order></stock>, Afterwards, a conflict resolution strategy add is defined for the quantity node through the client resolution strategy unit 105, which means that when the user's original stock quantity stored in the server conflicts with the current newly purchased stock quantity, the program will take the method of adding the quantity way to resolve conflicts. Afterwards, a node add is added to each quantity node through the client DOM operation unit 104, which is used for the displayed labeling conflict resolution strategy.

5. The user uses the mobile phone to communicate with the server through the client communication unit 106. The mobile phone first sends a "discovery request" message <DiscoveryRequest/>. When the network condition is good, the server will receive this message and return it to A confirmation code <ConnectAgent/> on the mobile phone, and the mobile phone will send the stored message to the server; when the network condition is not good or the device has a hardware failure, the server will not receive the discovery request message, or the mobile terminal will not receive the confirmation code , then the hardware needs to be processed or the communication connection needs to be reconnected after a period of time.

6. After the server receives the user messages, it parses these messages through the server-side DOM operation unit 204, and compares them with the messages stored in the database. The server will find that the two messages are different, and a conflict occurs at this time. The conflict is: the number of a shares purchased by the user in the server is 200, and the number of a shares newly submitted by the user is 100. B records these conflicts.

7. B resolves the conflict at the server-side conflict resolution unit 203 . According to the solution strategy node add defined by the quantity node, the quantity of a is added, which is 200+100=300. After the final conflict is resolved, the content is 300 shares of a stock, which is <stock><order><ID>a</ID><quantity><howmuch>300</howmuch></quantity></order></stock> .

8. The server processes the message through the server-side message queue management unit 201, packs the message into a message recognizable by the server, and then stores the message in the database through the server-side storage unit 202.

9. If the server receives new news such as dividends or daily limit of this a stock, the server sends the updated message to all subscribers who subscribe to this a stock through the server-side communication unit 206, so that the user can process the stock in real time .

By using the method provided by the invention, data sharing between clients can be supported without going through a server. The invention allows clients to share data when they are connected, and when they reconnect, resolve conflicts caused by offline data operations when they were disconnected. The invention also supports data-sharing communication between the mobile device and the server, allowing users to modify the information they have published and subscribe to corresponding information, and the server will notify the user of changes in the information subscribed by the user.

The above is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto, any person familiar with the technical field within the technical scope disclosed in the present invention, according to the technical solution of the present invention Any equivalent replacement or change of the inventive concepts thereof shall fall within the protection scope of the present invention.

Claims (5)

1. middleware system of sharing at the enterprising line data of cell phone apparatus is characterized in that this system applies is at least one server end with run on more than two in the system that the client of cell phone apparatus forms;

Described client comprises:

The client item administrative unit is used for user's edit messages, configuration communication object and communication mode parameter;

The client message converting unit is used for the message conversion that the user edits is become the message of XML form, and this message is continued to convert to the form of tree;

The client-cache unit, the data that are used to store subscriber's local, what make that the user can off-line operates modification to data, and with client often the storage of the server end of visit in this locality;

The client communication unit is used to make the user to communicate with other clients or server;

Client DOM operating unit is used for the message of the tree structure of XML form is added and retouching operation, and the message that other-end sends over is resolved;

Client is cleared up policy unit, is used for the message converting unit is converted to the conflicting nodes definition conflict-solving strategy of the message of tree-like formula;

Client conflict resolution unit is used to call client DOM operating unit XML message is handled, and calls described client afterwards and clears up policy unit, solves conflict according to the Strategy of Conflict Resolution of predefined;

Display unit is used for the result is shown to the user;

Server end has:

Server end message queue administrative unit is used for the message of server is managed, and Control Server is with carrying out messaging between the other-end;

The server end memory cell is used for message stores at database;

The server end communication unit is used to make this server and other clients or server to communicate;

Server end is cleared up policy unit, is used for the conflicting nodes definition conflict-solving strategy to the message of tree-like formula;

Server end DOM operating unit is used for the message of the tree structure of XML form is added and retouching operation, and the message that other-end sends over is resolved;

Server end conflict resolution unit is used for invoking server end DOM operating unit XML message is handled, and calls described server end afterwards and clears up policy unit, solves conflict according to the Strategy of Conflict Resolution of predefined;

A client of described middleware system is as the transmit leg of message, its client message converting unit is after receiving that the user utilizes this client item administrative unit editor's message, this message conversion is become the XML form, utilize client to clear up policy unit then, outwards send message by the client communication unit again for the node that may produce conflict adds conflict-solving strategy; Receive message by server end or another client, the DOM operating unit of server end or another client is to be correlated with DOM operation of message, being recipient DOM operating unit compares the XML message of two different trees, produce the diff tree, to write down by two conflicts that different messages was produced; Conflict resolution unit among the recipient liquidates to advance by leaps and bounds to go and clears up then, produces a not new tree of conflict, again this tree is sent to transmit leg; If this process occurs between two mobile clients, then the result is stored in the described client-cache unit, and transfers to described display unit demonstration; If this process occurs between mobile client and the server, then server is kept at this message in the database of server end memory cell, and by described server end message queue administrative unit this message is sent to all subscribers by the server end communication unit.

2. the middleware system of sharing at the enterprising line data of cell phone apparatus according to claim 1, it is characterized in that described client-cache unit comprises an interim message queue, client is put into message in this message queue, and the agreement that initiatively sets according to this client communication unit of message queue sends or receive message thus; Each message is all added one and is sent end mark, when message sends to end mark, thinks that then message sends successfully, otherwise thinks that message sends failure, resends this message or carries out back one step processing.

3. the middleware system of sharing at the enterprising line data of cell phone apparatus according to claim 1, it is characterized in that described server message queue management unit comprises a thread pool and work queue, by work queue the request that receives is monitored, the terminal of taking out a thread and response according to priority in thread pool communicates then; When each thread and terminal communication, all comprise one and the similar message queue of client, be used for transmission initiatively or receive message, and the message that receives is kept in the database; When confiscating confirmation in preset time, the processing method of server is: for lasting subscriber, if terminal broken string, server gets up message stores, when he once more during line, server can be issued the subscriber once more with message; For non-persistent subscriber, broken string just means failure, and server is with this subscription information deletion, if the subscriber wants to continue to receive message, he need send subscription information once more so.

4. the middleware system of sharing at the enterprising line data of cell phone apparatus according to claim 1, it is characterized in that described transmit leg communicates by letter with the recipient by communication unit, send one earlier by transmit leg and find request message, if the recipient receives this message, can return to confirmation code of transmit leg, then transmit leg all sends to the recipient with all versions of own institute storing message; If the recipient does not receive discovery request message or transmit leg and do not receive confirmation code, then need transmit leg to resend and find that request message is to the recipient.

5. the method for work at the shared middleware system of the enterprising line data of cell phone apparatus is characterized in that comprising the steps:

Step 1 according to concrete application, is come edit messages by the client item administrative unit by the user, and configuration information is carried out respective design;

The message conversion that step 2 client is edited the user by the client message converting unit becomes the message of XML form, with this message stores in the client-cache unit; Afterwards this message is continued to convert to the form of tree, then according to concrete application, clear up policy unit by client and may produce conflict-solving strategy of node definition of conflict for each, and be node of this tree interpolation by client DOM operating unit, this nodes records conflict-solving strategy; When clashing, application program should take the conflict-solving strategy of this node definition to solve conflict;

Step 3 is worked as client and is begun to communicate by letter as the recipient with another terminal by the client communication unit as transmit leg, transmit leg sends one earlier and finds request message, if the recipient receives this message, can return to confirmation code of transmit leg, illustrate that this moment, transmit leg and recipient can communicate, transmit leg all sends to the recipient with all versions of own institute storing message; If the recipient does not receive discovery request message or transmit leg and does not receive confirmation code, then needs to resend the discovery request message;

After step 4 recipient receives all versions of transmit leg institute storing message, DOM operating unit by server end or another client is resolved these message, and with oneself the storage message compare, this moment is if having a side to revise message among transmit leg and the recipient, can find conflict when then comparing, the recipient notes these conflicts;

Step 5 recipient is according to the resolution policy node of the defined conflicting nodes of step 2, by server end or another client clear up policy unit call predefined good clear up strategy, clear up by the liquidate row of advancing by leaps and bounds of the conflict resolution unit of server end or another client, and note new information after managing conflict;

Step 6 is if the recipient is a mobile client, then the recipient is stored in this new information in the buffer memory by the client-cache unit, and this new information returned to transmit leg by the client communication unit, message after transmit leg is noted this and managed conflict, and be stored in the buffer memory, transfer to client display unit display result then;

Step 7 if the recipient be server, then the recipient necessarily handles message by server end message queue administrative unit, and message is packaged into the discernible message of server, afterwards by the server end memory cell with message stores in database;

Step 8 message that will upgrade of server then sends to all subscribers by the server end communication unit, makes that the message among all subscribers keeps synchronously.

Images