GB2463028A

GB2463028A - A method of operating an offline mobile sales service logistics system

Info

Publication number: GB2463028A
Application number: GB0815645A
Authority: GB
Inventors: Michael Patrick Brooks; Neill Anthony Ryan; David John Costello
Original assignee: CR SYSTEMS Ltd
Current assignee: CR SYSTEMS Ltd
Priority date: 2008-08-28
Filing date: 2008-08-28
Publication date: 2010-03-03
Also published as: GB0815645D0

Abstract

A method of operating an offline mobile sales service logistics system comprising a server and a plurality of remote mobile user devices (MUDs), in which the server and the remote MUDS communicate with each other over a wireless communication network over wireless links. The server has memory with sales service information stored thereon and each of the MUDS have memory with MUD sales service information stored thereon. The MUD sales service information is segmented into a plurality of configuration features and the configuration features are each given a synchronisation programme which forms part of a synchronisation schedule for that MUD. Uploading and downloading of information to and from the MUD and the server is carried out in a very structured manner according to the synchronisation schedule. Furthermore, there is provided a method of pushing data from a server to a remote mobile device and a method of displaying content on the mobile device.

Description

"A Method of Operating an Offline Mobile Sales Service Logistics System"

Introduction

This invention relates to a method of operating an offline mobile sales service logistics system comprising a server and a plurality of remote mobile user devices (MUDs), the server and the remote MUDs each having means to communicate with the other over a wireless communications network, the server having memory with sales service information stored thereon, the MUDs each having memory with MUD sales service information stored thereon.

In an increasingly competitive marketplace, many companies are adopting more proactive selling strategies in an attempt to gain a competitive edge over their competitors. One approach that has been taken for some time now has been to facilitate the ordering process for existing and potential customers by sending a sales representative to the premises of the customer. The sales representative may discuss the specific needs of the customer on-site and provide them with detailed information concerning new products or services offered by their company. One tool that has been particularly useful to the companies and the sales representatives in particular is a so-called mobile sales service logistics system. Typically, the sales service logistics system comprises a server containing a great deal of information relating to the products and services of the company, and a mobile communication device in the possession of the sales representative that may be used to access the product information in the server. In this way, sales representatives may access detailed information relating to the company's products and services, as well as other information relevant to the potential sale. In certain instances, the mobile sales service logistics system enables detailed quotations to be given and often can help to close a sale.

Generally speaking, the existing mobile sales service logistic systems may be divided into two distinct categories: web based systems and offline systems. Web-based systems comprise a web server with information relating to the products of a company as well as other relevant sales information such as client details and the like. The web server is accessible by a remote mobile communications device, such as a laptop or a mobile telephone, in the possession of the sales representative. In order to access the web server, the sales representative must establish an internet connection with the web server and retrieve the required information from the web server. The advantage of this system is that mobile communication devices with relatively limited memory capacity can be used by the sales representatives as the vast majority of information does not have to be stored on the mobile communications device. There are, however, several disadvantages with the web-based systems, the most notable of which being that an internet connection must be established and maintained for the duration of the sales representative obtaining information from the web server. However, it is often the case that the sales representative will be located in a remote location with the client where there is poor or no coverage, thereby preventing the sales representative from establishing an internet connection and contacting the web server. Furthermore, it is not uncommon for the coverage to be transient in nature, often resulting in slow connections or b connections that fail midway through a session, again hampering the ability of the sales representative to make a sale. A further disadvantage of the known online systems is that they typically must download all the data required while executing the business transaction, this can be slow and expensive The second category of mobile sales service logistic systems are offline systems.

The offline mobile sales service logistic systems also typically comprise a web server and a mobile communication device that accesses the web server over an internet connection. However, the offline sales service logistic systems operate by downloading the company product and service information from the web server to the mobile communication device in its entirety every day. In this way, all of the information relating to the products and services of a company as well as information that may be useful to facilitate a sale such as client details, is downloaded directly onto the mobile communication device of the sales representative. Often, this information is downloaded first thing in the morning when the sales representative turns on their device. The advantage of the offline sales service logistics system is that the user does not have to rely on an internet connection when they are with a customer, but rather they only have to rely on the internet connection for the initial download period once they turn their device on. There are, however, problems with the known offline mobile sales service logistics systems. First of all, the amount of information that must be downloaded can be substantial and the task of downloading the entire information onto the mobile communication device can take a number of hours to complete. Secondly, the information contained on the mobile communications device is practically out of date as soon as it has been downloaded, particularly if there are a number of sales representatives using the system. For example, available stock levels may change on an hourly basis and a sales representative, without knowledge of the fact, may accept an order for goods that he does not in fact have. This is highly undesirable. However, if the sales representative was to update the data on their device on a more frequent basis, this would render their device inaccessible for large periods throughout the day which is also disadvantageous. A further problem with the known offline mobile sales service logistic systems is that a large amount of information is downloaded onto a number of mobile communications devices each day which can be expensive to do, particularly if the users of the system pay on a bandwidth usage tariff. This cost is often ohibitive to implementing such offline systems.

EP1632852 and EP1632894 both disclose a method of synchronizing databases in which different types of data is synchronized at different times. The synchronization can be performed by a local machine communicating wirelessly with a remote machine. W002/25403 discloses a method of synchronizing contact information across different devices. In this specification, only some of the contact information is synchronized and the devices are not wireless devices communicating with a remote server.

W003/036520, US2004/024910 and W002/13464 all disclose examples of systems featuring a plurality of remote mobile client devices which synchronize local copies of a database storing sales service data with a central server. However, the synchronisation is carried out in the same manner for all parts of the database.

It is an object, therefore, of the present invention to provide an offline mobile sales service logistics system that overcomes at least some of the difficulties with the known mobile sales service logistic systems.

Statements of the Invention

According to the invention there is provided a method of operating an offline mobile sales service logistics system comprising a server and a plurality of remote mobile user devices (MUDs), the server and the remote MUDs each having means to communicate with the other over a wireless communications network, the server having memory with sales service information stored thereon, the MUDs each having memory with MUD sales service information stored thereon, the method comprising the initial configuration steps of: segmenting the MUD sales service information into a plurality of configuration features; assigning a synchronisation program to each of the configuration features specific to the configuration feature, each of the synchronisation programs including a set-time synchronisation sub-program, a periodic synchronisation sub-program and a curfew synchronisation sub-program; storing the synchronisation programs in MUD memory as an MUD synchronisation schedule; the method comprising the subsequent steps of: the MUD generating a synchronisation request for submission to the server in accordance with the synchronisation schedule, the synchronisation request relating to one or more configuration features; the MUD establishing a temporary communication link over the wireless communication network with the server and transmitting the synchronisation request to the server; the server receiving the synchronisation request from the MUD; the server processing the synchronisation request and depending on the content of the synchronisation request, the server performing one of the synchronisation actions of: retrieving a portion of the up-to-date sales service information, specified in the synchronisation request, from the server memory and transmitting only that portion of up-to-date sales service information to the MUD; and updating a portion of the sales service information, specified in the synchronisation request, in server memory; terminating the temporary communications link between the MUD and the server on completion of the synchronisation action.

By having such an offline mobile sales service logistics system, only data that is essential for the successful operation of the system is downloaded to the MUD. The MUD makes synchronisation requests in accordance with the synchronisation schedule which has a synchronisation programme for each of the configuration features. Therefore, it may be determined that some of the configuration features, for example those relating to stock levels, must be kept up to date on a very frequent basis, eg. every five minutes, whereas other configuration features such as client contact data only needs to be updated once a day.

The synchronisation programme assigned to each configuration feature includes a set-time synchronisation sub-programme, a period synchronisation sub-programme nd a curfew synchronisation sub-programme. This is most advantageous as the set-time synchronisation sub-programme allows for a synchronisation request specific to that configuration feature to be made at specified times during the day. For example, the client contact details may be updated every day at 8 am when it is known that the sales representative is normally in a good reception area. Furthermore, a periodic synchronisation sub-programme allows for a configuration feature to be updated a number of times at regular intervals throughout the day. For example, stock level data may be updated every five minutes so that highly accurate stock levels information is provided to the sales representative. Finally, the curfew synchronisation sub-programme allows the operators of the system to control when certain configuration features cannot be updated to a device. For example, configuration features requiring large downloads of data that may not be essential to the operation of the device can have a curfew synchronisation sub-programme that ensures that data is only synchronised between the hours of 8 pm and 6 am when bandwidth tariffs may be at a substantially lower rate than at other times throughout the day.

Combined together, the synchronisation programme optimises the MUD sales service information and allows the system to operate in a relatively seamless manner.

Furthermore, by having such an offline sales service logistics system, it is possible to coordinate all of the devices so that data is transferred throughout the system in an orderly and predictable manner. This is highly advantageous. The system according I to the present invention facilitates operation and furthermore assists in reducing overhead costs.

in another embodiment of the invention there is provided a method in which the method further comprises the step of on the MUD being temporarily unable to establish a communication link with the server in order to transmit a synchronisation request to the server, the MUD storing the synchronisation request in cache memory and transmitting the stored synchronisation request with the next synchronisation request made by the MUD. In this way, if it is not possible to transfer a synchronisation request to the server, the synchronisation request will be handled subsequently so that information on the MUDs and the server is kept up to date.

In a further embodiment of the invention there is provided a method in which the method further comprises the additional initial configuration step of the MUD establishing a device context with the server unique to that MUD, and the server storing the device context for each MUD in server memory.

In one embodiment of the invention there is provided a method in which the step of the MUD transmitting a synchronisation request further comprises the MUD transmitting a current lP address of the MUD to the server and the method comprises the intermediate step of the server updating the unique device context of the MUD stored in server memory with the current IP address of the MUD. This is seen as a highly advantageous aspect of the present invention. By having a current P address of the MUD, the server is able to push messages to the MUD using the current IP address of the MUD. Therefore, urgent messages including personalised messages or updates to the system, including special offers or like information, may be pushed directly from the server out to one or more MUDs. This is highly advantageous and the messages may be transmitted over the internet at a very low cost to the company implementing such a system.

In another embodiment of the invention there is provided a method in which on the MUD successfully receiving a message pushed from the server, the MUD transmitting a confirmation receipt back to the server.

In a further embodiment of the invention there is provided a method in which on the server not receiving a confirmation receipt from the MUD within a predetermined period of time, the method comprises the step of the server storing the message in memory and the next time the MUD makes a synchronisation request to the server, the server re-transmits the message to the MUD using the current lP address of the MUD.

In one embodiment of the invention there is provided a method in which the method comprises the steps of the MUD storing the device context in MUD memory, agreeing a device identifier indicative of the device context with the server, both the MUD and the server storing the device identifier in memory and the MUD and server use that device identifier for subsequent communications with each other.

This is seen as a highly advantageous aspect of the present invention. By agreeing a device identifier, the device identifier may be transmitted with communications between the two parties instead of the entire device context. This reduces the amount of information being transmitted with each communication thereby reducing the bandwidth requirement of the system and further reducing the costs of implementing such a system. Furthermore, the security of such a system is greatly enhanced as data which would normally be sent in internet communications such as the IP address, machine information, machine address and the like, does not necessarily have to be transmitted each time which greatly enhances the security of such a system. Furthermore, a username and password do not have to be transmitted each time in addition to IP Address.

In another embodiment of the invention there is provided a method in which the MUD transmits the device identifier with any subsequent synchronisation request to the server and the MUD only transmits the device context to the server on the device context changing.

In a further embodiment of the invention there is provided a method in which the additional initial configuration step is carried out of storing program code on the MUD, the program code being divided into common code, customer code and customer configuration, the customer code having user interface (UI) information and the configuration code having MUD sales service information, the method comprises the step of the server transmitting UI information to the MUD as part of a response to a synchronisation request and the MUD using both the UI information from the customer code and the UI information from the server to generate the user interface. This is another particularly preferred embodiment of the present invention. In this way, the user interface on the MUD will be generated from a hybrid of a database system and a web based system. Certain information regarding display of information will be contained in data received from the server, whereas other information regarding the display of information will already be stored on the MUD, thereby reducing the amount of information that must be transmitted between the devices whilst also allowing for more flexible user interface presentation to be achieved.

In a further embodiment of the invention there is provided a method in which the method further comprises the step of assigning an accessibility control, an up-synchronisation control and a down synchronisation control to each of the configuration features.

Detailed Description of the Invention

The invention will be more clearly understood from the following description of some embodiments thereof, given by way of example only, in which: -Fig. I is a diagrammatic representation of an offline mobile sales service logistics system according to the present invention; Fig. 2 is a flow diagram of the method of operating an offline mobile sales service logistics system according to the present invention; and Fig. 3 is a diagrammatic representation of the software programming structure to be loaded onto an MUD.

Referring to the drawings, and initially to Fig. 1 thereof, there is shown an offline mobile sales service logistics system, indicated generally by the reference numeral 1.

The ofl9ine mobile sales service logistics system 1 comprises a server 3 and a plurality of mobile user devices (MUDs), in this instance provided by a number of mobile telephones 5, a number of personal digital assistants (PDAs) 7 and a laptop computer 9. The server 3 and the MUDs 5, 7, 9, each have means to communicate with each other (not shown), over a plurality of wireless links 11 through a wireless communications network 13. The server 3 has memory 15 with sales service information stored thereon and each of the MUDs 5, 7, 9 has memory (not shown) with MUD sales service information stored thereon.

In use, the MUDs are used by sales representatives when discussing orders with customers at the customers' premises. The offline MUDs have sales service information stored thereon which includes product information, pricing information, client information and other information that may be relevant to completing a sale.

The sales representatives may consult their MUD when making a sales pitch and provide accurate information to the customer while doing so. However, rather than accessing the server 3 and relying on a potentially unreliable connection to the server, the offline MUDs have sales service information stored thereon.

Referring to Fig. 2 of the drawings, there is shown a flow diagram of the method of operating an offline mobile sales service logistics system according to the present invention, indicated generally by the reference numeral 21. In step 23, the MUD sales service information is segmented into a plurality of configuration features. The configuration features include, but are not limited to, information under the headings of customers, registered customers, products, product stock levels, product groups, customer groups, customer debt, reports, customer product pricing, customer group product pricing, customer product group pricing, customer group product group pricing, product pricing, customer templates, customer group templates, job details, customer notes and surveys, It will be understood that these configuration features are not exhaustive and other or different configuration features may be provided as desired. In step 24, each of the configuration features is assigned a synchronisation programme specific to the configuration feature. This further comprises the individual steps of assigning a set-time synchronisation sub-programme in step 25, assigning a ft periodic synchronisation sub-programme in step 27 and assigning a curfew synchronisation sub-programme in step 29. In step 31, the synchronisation programmes are stored in MUD memory as an MUD synchronisation schedule. This completes the initialisation steps of the MUD.

In step 33, the MUD generates a synchronisation request for submission to the server in accordance with the synchronisation schedule and in step 35 the MUD establishes a temporary communication link and transmits a synchronisation request to the server 3 via the wireless communications network 13 and the communication links 11. The synchronisation request sent to the server is transmitted in accordance with the set-time synchronisation sub-programme, the periodic synchronisation sub-programme and the curfew synchronisation sub-programme of each synchronisation programme in the synchronisation schedule. In step 37, the server receives the synchronisation request and in step 38 the server 3 processes the synchronisation request. Depending on the content of the synchronisation request, the server will perform one of the synchronisation actions of retrieving a portion of the up-to-date sales service information, specified in the synchronisation request, from the server memory and transmitting only that portion of up-to-date sales service information to the MUD, in steps 39 and 41, and updating a portion of the sales service information in server memory in step 43. Finally, once the sales service information has been updated and/or the sales service information necessary has been transmitted to the MUD, the process ends in step 45 by the temporary communications link between the server and the MUD being terminated.

In this way, only the updates of the sales service information are transmitted to the MUD. Furthermore, and most importantly, the updates are only sent in accordance with the synchronisation schedule and the synchronisation schedule is configured so that certain sales service information is sent to the MUD at specified times and the entire sales service information does not have to be downloaded onto the device each time. By dividing the MUD sales service information into a plurality of configuration features, it is possible to determine how essential it is to have the sales service information relating to that configuration feature updated on an MUD. For example, product information including product category, may change very rarely, once a month or so, in which case it may be sufficient to download this information to a device every week. Similarly, new customer details may be uploaded to the sales service information stored in the server at the end of every working day, however, it may be essential to update stock information every few minutes. By separating the sales service information into a plurality of configuration features, it is possible to determine exactly when the information is updated on the machine, Information that must be updated regularly can be updated at regular intervals and information that does not require frequent updates may be updated at pre-determined times everyday.

The configuration features are each assigned a synchronisation programme which further comprises a set-time synchronisation sub-programme, a period synchronisation sub-programme and a curfew synchronisation sub-programme. The set-time synchronisation sub-programme may determine that certain information is downloaded to an MUD at 7 am, 12 pm and 5 pm each day, although these times are given for exemplary purposes only and are not intended to be limiting, It would be possible to have a set-time synchronisation sub-programme that uploads information to an MUD before the start of a working day. This could be while the sales representative is travelling into work in their car when they know that they have good reception and the information is not so vital that it must be updated more than once or a few times each day. The periodic synchronisation sub-programme will allow for -12-updates to be downloaded after a pre-determined time, for example, every five minutes or every hour. Again, these are not intended to be limiting and are used for exemplary purposes only. For example, in certain businesses, it may be essential to keep very accurate stock information on hand and this may need to be uploaded every five minutes onto a MUD.

Finally, the curfew synchronisation programme may be used to ensure that certain data is not downloaded to the MUD at certain times during the day or night. For txampe, data which it is not essential to have up to date, may be downloaded onto a user's device every night between the hours of 3 am and 5 am when the device is usually out of commission and the cheaper nocturnal rates and tariffs for use of the wireless communication network may apply. This will also prevent large amounts of data being downloaded during times when tariffs are at their most expensive. There a significant advantage resulting from carrying out synchronisations at night for the wireless operator. This is due to the fact that the resources in the wireless network are not highly utHised at night and therefore the present invention allows the Wireless Operators to sell resources that would normally go unused. Furthermore the synchronisation schedule may be tailored for each individual device and can be useful for user preferences, e.g. if a user knows they have wireless reception at a certain period in the morning they may configure the device to perform the synchronisation of one or more of the features at this time It is envisaged that in certain circumstances, the MUD will be unable to establish a communication link with the server in order to transmit a synchronisation request to the server. In such circumstances, the MUD will store the synchronisation request in cache memory and transmit the stored synchronisation request with the next synchronisation request from the MUD.

In a particularly preferred embodiment of the invention, the MUD establishes a device context with the server 3 and the server stores the device context for each MUD 5, 7, 9 in server memory 15. The device context preferably includes user name, password, a MUD location, a MUD sub-location, an application detail, a machine information (such as a MAC address), a user info, an international mobile equipment identity (IMEI), an international mobile subscriber identity (IMSI), and an IP address.

It is envisaged that when the MUD transmits a synchronisation request to the server, the synchronisation request comprises the current IP address of the MUD and the server updates the device context of the MUD with the current IP address of the MUD each time it receives the synchronisation request. In this way, the server may push the message to the MUD using the current IP address of the MUD stored as part of the device context. If the MUD successfully receives a message pushed from the server, the MUD will transmit a confirmation receipt back to the server.

If the server does not receive a confirmation receipt from the MUD within a pre-determined period of time, the server will know that the MUD has not received the message and the server will store the message in memory until the next time the MUD makes a synchronisation request to the server. When the synchronisation request is received by the server, the server will update the (P address of the MUD in the device context and retransmit the previous message to the MUD. This is a very 15,owerful aspect of the present invention as it is now possible to push information from the server out to each of the MUDs. Previously, for web based systems, these systems operated on a pull basis whereby a request was made by a device to a server and the information was sent directly back to the server. However, now it is possible for the server to transmit messages such as special offers or up-to-date information that it feels essential to notify the sales representative of without delay.

Furthermore, it is envisaged that each MUD stores the device context in MUD memory and agrees a device identifier indicative of the device context with the server.

Both the MUD and the server store the device identifier in memory and the MUD uses that device identifier for subsequent communications with the server.

Therefore, the MUD need only transmit the device identifier with any synchronisation request to the server and only transmits a device context to the server on the device context changing. This will significantly reduce the amount of information being transmitted and, furthermore, will provide a more secure system as valuable information relevant to the MUD will not be transmitted each time any information is sent. Furthermore, this reduces the amount of bandwidth being taken up and reduces the cost of operating the system. It is only necessary to retransmit a device context once information, such as the IP address of the MUD, changes.

In addition to the above, it is envisaged that the additional initial step is carried out of storing programme code on the MUD. The programme code is divided into common code, customer code and customer configuration. The customer code has user information and the configuration has MUD sales service information. The server transmits user interface information to the MUD as part of a response to a synchronisation request and the MUD uses both the user interface information from the customer code and the user interface information from the server to generate the user interface. In this way, the user interface is a hybrid of a web type model where the device receives all information and also how to display that information and a data model where only data is sent and no display information is sent.

Referring to Fig. 3 of the drawings, there is shown a diagrammatic representation of the software programming structure loaded onto a client device, indicated generally by the reference numeral 51. The software structure comprises a core 53 which has Hnks to a common model code 55, a data access layer 57, a billing agent 59, a general logic component 61, a plurality of user interface layers 63(a), 63(b), 63(c) and a plurality of proxy service layers 65(a), 65(b) and 65(c) through a service layer interface 67.

Throughout this specification reference has been made to an offline mobile sales service logistics system. It will be understood that this will include not solely sales service logistics systems but is also envisaged to comprise other offline mobile service logistics systems such as those used for gathering survey data, namely offline mobile survey service logistics systems. Essentially therefore, what is important is that mobile devices may be used by individuals and those individuals update the information on their mobile devices periodically and the system may be implemented in the manner described.

A further aspect of the present invention is that although typically the communication link will be a wireless link, the devices will have the option of connecting up to a docking station or the like when a user is in their office and downloading information directly to the device. Similarly, a USB cable could be used to connect to a PC with information thereon or access to information that can be downloaded onto the device.

However, these are to be understood as exceptional cases and the basis of the present invention is concerned with devices that must normally operate over a wireless communication link although the temporary communication link can in certain instances be established over other connections.

It is envisaged that the server may in certain cases be selective about when an update is sent in order to limit the traffic on the network. For example, it is possible for the server to cancel an update session if the previous value to be updated was within a specified range of the current value. For example, assume that the stock level for a specific product is 200 items at the start of the day. Furthermore, assume that the stock level for that product changes during the day to 199. Normally, if an MUD made a request for stock level update the figure of 199 would be sent down to the MUD. However, the server has the facility apply a Throttle" and not respond to the MUD with the information unless the stock level falls a certain amount below the previous value. In this case, that amount may be 10 items below or above the previous amount as the minimum change in stock before the server sends the new value to the MUD. If this was the case, no new stock levels would be sent unless the stock level went to 190 or lower.

In this specification the terms "comprise, comprises, comprised and comprising" and the terms "include, includes, included and including" are all deemed totally interchangeable and should be afforded the widest possible interpretation.

The invention is in no way Jimited to the embodiment hereinbefore described and may be varied in both construction and detail within the scope of the claims.

Claims

-16 -CLAIMS1) A method of operating an offline mobile sales service logistics system comprising a server and a plurality of remote mobile user devices (MUDs), the server and the remote MUDs each having means to communicate with the other over a wireless communications network, the server having memory with sales service information stored thereon, the MUDs each having memory with MUD sales service information stored thereon, the method comprising the initial configuration steps of: segmenting the MUD sales service information into a plurality of configuration features; assigning a synchronisation program to each of the configuration features specific to the configuration feature, each of the synchronisation programs including a set-time synchronisation sub-program, a periodic synchronisation sub-program and a curfew synchronisation sub-program; storing the synchronisation programs in MUD memory as an MUD synchronisation schedule; the method comprising the subsequent steps of: the MUD generating a synchronisation request for submission to the server in accordance with the synchronisation schedule, the synchronisation request relating to one or more configuration features; the MUD establishing a temporary communication link over the wireless communication network with the server and transmitting the synchronisation request to the server; the server receiving the synchronisation request from the MUD; the server processing the synchronisation request and depending on the content of the synchronisation request, the server performing one of the synchronisation actions of: retrieving a portion of the up-to-date sales service information, specified in the synchronisation request, from the server memory and transmitting only that portion of up-to-date sales service information to the MUD; and updating a portion of the sales service information, specified in the synchronisation request, in server memory; terminating the temporary communications link between the MUD and the server on completion of the synchronisation action; and in which the method further comprises the additional initial configuration step of: the MUD establishing a device context with the server unique to that MUD, and the server storing the device context for each MUD in server memory and in which the step of the MUD transmitting a synchronisation request further comprises the MUD transmitting a current IP address of the MUD to the server and the method comprises the intermediate step of the server updating the unique device context of the MUD stored in server memory with the current lP address of the MUD and in which the method further comprises the step of the server pushing a message to the MUD using the current lP address of the MUD stored as part of the device context.
2) A method as claimed in claim I in which the method further comprises the step of on the MUD being temporarily unable to establish a communication link with the server in order to transmit a synchronisation request to the server, the MUD storing the synchronisation request in cache memory and -18-transmitting the stored synchronisation request with the next synchronisation request made by the MUD.
3) A method of as claimed in claim 1 or 2 in which on the MUD successfully receiving a message pushed from the server, the MUD transmitting a confirmation receipt back to the server.
4) A method as claimed in claim 3 in which on the server not receiving a confirmation receipt from the MUD within a predetermined period of time, the method comprises the step of the server storing the message in memory and the next time the MUD makes a synchronisation request to the server, the server re-transmits the message to the MUD using the current IP address of the MUD.
5) A method as claimed in any preceding claim in which the method comprises the steps of the MUD storing the device context in MUD memory, agreeing a device identifier indicative of the device context with the server, both the MUD and the server storing the device identifier in memory and the MUD and server use that device identifier for subsequent communications with each other.
6) A method as claimed in claim 5 in which the MUD transmits the device identifier with any subsequent synchronisation request to the server and the MUD only transmits the device context to the server on the device context changing.
7) A method as claimed in any preceding claim in which the additional initial configuration step is carried out of storing program code on the MUD, the program code being divided into common code, customer code and customer configuration, the customer code having user interface (UI) information and the configuration code having MUD sales service information, the method comprises the step of the server transmitting UI information to the MUD as part of a response to a synchronisation request and the MUD using both the UI information from the server and the UI -19 -information from one or more of the customer code, common code and the customer configuration to generate the user interface.
8) A method as claimed in any preceding claim in which the method further comprises the step of assigning an accessibility control, an up-synchronisation control and a down synchronisation control to each of the configuration features.
9) A method of operating an offline mobile sales service logistics system substantially as hereinbefore described with reference to and as illustrated by the accompanying drawings.