GB2445003A

GB2445003A - Communication device and method for arranging a meeting.

Info

Publication number: GB2445003A
Application number: GB0625546A
Authority: GB
Inventors: Cristina Chesta
Original assignee: Motorola Inc
Current assignee: Motorola Solutions Inc
Priority date: 2006-12-22
Filing date: 2006-12-22
Publication date: 2008-06-25
Also published as: GB0625546D0

Abstract

A communication device comprising a transceiver operably coupled to a signal processor comprising a meeting application program the transceiver receives a location communication associated with arranging a meeting and in response thereto. The meeting application program to determine the location(s) of the sender(s) of the at least one location communication based on information provided within the at least one location communication and determine the current location of the communication device. The code also determine a preferred meeting location and/or meeting time, based on the location(s) of the sender(s) of the at least one location communication and the location of the communication device and generate a confirmation communication to the sender(s) of the at least one location communication, the confirmation communication comprising information relating to the preferred meeting location or meeting time.

Description

COMMUNICATION DEVICE AND METHOD FOR ARRANGING A MEETING

Field of the Invention

This invention relates to a method and apparatus for arranging a meeting, and in particular to a method and apparatus for arranging a meeting between two or more mobile devices.

Background of the Invention

In the field of this invention, it is known to use

computer tools to facilitate the planning of meetings between two or more people. Well known computer tools include Lotus Notes and Microsoft Outlook'TM, both of which allow a user to identify prospective invitees for a meeting, and then query the tool regarding the availability of the invitees.

However, these tools suffer from the problem that they are incapable of determining the actual location of invitees. In general, such tools work on the basis that invitees are located within a specific locale, such as within an office building. Consequently, even though a prospective invitee may appear to be available for a meeting (i.e. has no other meetings scheduled), it is not possible to determine whether that invitee is located, for example, in the office, and thus physically available to attend a meeting.

As mobile communication technology advances, people are becoming more and more mobile in both their working and personal lives. Consequently, it is no longer appropriate when arranging a meeting to assume that invitees are located within a specific locale, such as an office. This is particularly important when arranging a meeting at relatively short notice, since there may not be enough time for an invitee to reach a proposed meeting location.

Furthermore, such tools require the person arranging the meeting to have access to their computer, and for their computer to be connected to the company's network. This may not be practical, or indeed, possible if the person is away from the office.

Various methods and systems have been proposed to address this problem. Such methods involve the use of a central computer system that monitors the location of communication devices associated with, for example, employees or registered users. In this way, when one employee or registered user (organiser) desires to arrange a meeting with one or more other employees or registered users (invitees), the organiser is able to use the central system to determine the location of the required invitees. Consequently, the organiser is able to schedule a meeting at an appropriate location and time based on the current location of the invitees.

The inventor of the present invention has recognised that such methods suffer from the problem that they rely on a central server or similar system to locate the prospective invitees, and co-ordinate the meeting.

In order for the server to locate an invitee, it is necessary for the server to have some means of identifying an invitee, and subsequently to determine the location of that invitee. This inherently requires the server to have previously been provided with such a means of identifying each invitee, and for the method of determining the location to be available to the server.

In a situation whereby all invitees are, for example, employees of the same company, then this may not be a problem since, for example, the server may comprise details of the mobile phone numbers etc. of each employee, and can subsequently use this to determine the location of any employee's mobile phone.

However, if it is desired to arrange a meeting between prospective invitees who are not all associated with a common organisation, such as a company, this approach is not practical.

Such a scenario might be when a person attending a conference desires to meet up with various other attendees from different organisations, either before or after the conference.

Alternatively, a group of friends may desire to meet up for an impromptu social gathering.

In either scenario, being reliant on a single central server to be able to determine the location of such a group of people is impractical.

Furthermore, for such a system to be effective, it is necessary for the central server to continuously (or at least frequently) monitor the location of all users in order to prevent any significant delay occurring when the organiser is trying to arrange the meeting. Constantly monitoring the whereabouts of a person raises security issues, and is likely to be considered by many as an infringement of that person's rights.

There is therefore a need for an improved method for arranging a meeting.

Summary of the Invention

In accordance with a first aspect of the present invention, there is provided a communication device, as claimed in Claim 1.

In accordance with a second aspect of the present invention, there is provided a method of arranging a meeting, as claimed in Claim 24.

In accordance with a third aspect of the present invention, there is provided a computer program product, as claimed in Claim 29.

Further aspects of the present invention are as claimed in the dependent claims.

Brief Description of the Drawings

FIG. 1 illustrates a block diagram of a radiotelephone adapted to support the inventive concept of the invention.

FIG's 2 to 5 illustrate a process for arranging a meeting according to a first embodiment of the invention.

FIG's 6 to 10 illustrate a process for arranging a meeting according to an alternative embodiment of the invention.

FIG. 11 illustrates a process for arranging a meeting according to a further alternative embodiment of the invention.

FIG. 12 illustrates an example of fields and field values that could be added to/adapted to multimedia message service (MMS) formats to implement the concepts of the invention.

Description of Embodiments of the Invention

Referring first to FIG. 1, there is shown a block diagram of a radiotelephone 100 adapted to support the inventive concept of the invention. The radiotelephone 100 includes circuitry to allow the radiotelephone 100 to provide wireless telephony capability, which in this embodiment includes an antenna 102 preferably coupled to a duplex filter or antenna switch 104 that provides isolation between receiver and transmitter chains within the radiotelephone 100.

The receiver chain, as known in the art, includes receiver front-end circuit 106 (effectively providing reception, filtering and intermediate or base-band frequency conversion). The front-end circuit 106 is serially coupled to signal processing logic (generally realised by a digital signal processor (DSP)) 108. The receiver chain also includes received signal strength indicator (RSSI) circuitry 112, which in turn is coupled to a controller 114 for maintaining overall control of the telephony capabilities. A timer 118 is operably coupled to the controller 114 to control the timing of operations (including transmission or reception of time-dependent signals) within the radiotelephone 100. The controller 114 is also coupled to the receiver front-end circuitry 106 and the signal processing logic 108 for receiving a transmitted data signal.

The controller 114 may therefore receive bit error rate (BER) or frame error rate (FER) data from recovered information. The signal processing logic 108 is coupled to a memory element 140.

The transmitter chain, as known in the art, includes a transmitter/modulation circuitry 122 and a power amplifier 124. For simplicity, the transmitter chain and receiver chain will hereinafter be referred to collectively as transceiver circuitry.

An output from the signal processing logic 108 is provided to a display 110, such as a screen or flat panel liquid crystal display. The screen or flat panel display includes a display driver circuit 111. Additionally, a keypad 130 is coupled to the signal processing logic 108 to allow a user to interact with the radiotelephone 100 via the signal processing logic 108.

In accordance with embodiments of the invention, the signal processing logic 108 of the radiotelephone 100 is adapted to execute a meeting application stored in the memory element 140.

It will be appreciated by a skilled artisan that the invention is not limited to a radiotelephone. Any suitable communication device may be adapted to support the inventive concept of the invention. Such communication devices include, by way of example only: i) radiotelephone handsets; ii) personal digital assistants (PDAs); iii) portable computers, such as laptops, tablets, etc; and iv) desktop computers.

Referring now to FIG. 2, FIG. 3 and FIG. 4 there is illustrated a process 200 for arranging a meeting according to a first embodiment of the invention.

The process 200 is initiated by the generation and sending of a location communication 230 by a client communication device 210 to a server communication device 220.

A method 300 of generating the location communication is illustrated in FIG. 3. The method 300 starts at step 310, by starting a meeting application program. This may be achieved in any suitable manner, as would be appreciated by a skilled artisan. For example, a user of the client communication device 210 may select an icon or menu option relating to the meeting application program by way of a user interface of the communication device 210.

Next, in step 320, the meeting application program determines the current location of the client communication device 210. This may be achieved by any suitable manner, as would be appreciated by a skilled artisan. For example, the communication device may comprise global position satellite (GPS) technology, or be operably coupled to an external GPS module, which the meeting application program is arranged to use to determine its current location.

Alternatively, for communication devices operating within a cellular network, the meeting application program may be adapted to determine the current location by way of identifying the current network cell in which it is operating, and thereby determine its approximate geographical location.

Alternatively yet, a user of the communication device may enter, by way of a user interface of the communication device, a location identifier, such as a post code, longitudinal and/or latitudinal coordinates, or a street name, etc. The meeting application program then identifies one or more invitee(s) to whom the location communication is to be sent, in step 330. For example, the meeting application program may be adapted to access entries stored within an address book or contact list of the communication device. In this way, a user may select the one or more invitee(s) from the entries stored on the device.

Alternatively, a user may simply enter the details of an invitee, for example a name and contact information such as a telephone number or email address, by way of the user interface of the communication device.

Next, in step 340, the meeting application program then generates the location communication comprising information relating to the location of the client communication device. Finally, in step 350, the location communication is sent to the invitee.

Referring back to FIG. 2, upon receipt of the location communication 230, the server communication device 220 generates a confirmation communication 240, which it sends back to the client communication device 210.

Referring now to FIG. 4, a method 400 of generating the confirmation communication 240 is illustrated. The method 400 starts at step 410, with the receipt of the location communication 230. The next step 420 comprises starting a meeting application program. The meeting application program may be started automatically upon the user of the server communication device 220 opening the received location communication 230, which may be, by way of example, in a multimedia messaging system (MMS) format.

Alternatively, the user may manually start the meeting application program. The meeting application program then extracts location information relating to the sender of the location communication, in step 430, which for this embodiment is the client communication device 210.

-10 -Next, in step 440, the meeting application program determines the current location of the server communication device 220. In the same way as for the client communication device 210, this may be achieved by any suitable means. For example, the communication device may comprise global position satellite (GPS) technology, which the meeting application program is adapted to use to determine its current location.

Alternatively yet, a user of the communication device may enter, by way of a user interface of the communication device, a location identifier, such as a post code, longitudinal and/or latitudinal coordinates, or a street name etc. In step 450, the meeting application program then determines a preferred meeting location. The determination of a preferred meeting location is described in further detail below.

The meeting application subsequently generates a confirmation communication comprising information relating to the preferred meeting location, in step 460.

Finally, in step 470, the confirmation communication is sent. The sending of the confirmation communication may -11 -be dependent upon authorisation by the user of the communication device.

Referring back to FIG. 2, upon receipt of the confirmation communication 240, the client communication device 210 generates an acknowledgement communication 250, which it sends back to the server communication device 220.

Referring now to FIG. 5, a method 500 of generating the acknowledgement communication 250 is illustrated. The method 500 starts at step 510, with the receipt of the confirmation communication 240. The next step 520 comprises starting the meeting application program. Once again, this may be automatic upon receipt of the confirmation communication, or require a user to manually start the meeting application program.

The meeting application program then extracts the information relating to the preferred meeting location, in step 530. Next, in step 540, the meeting application determines whether or not the preferred meeting location is to be accepted. The acceptance of the meeting location may be by way of user input, whereby the user manually accepts or declines the location.

Alternatively, the meeting application program may automatically accept or decline based on certain criteria, such as travel distance, undesirable locations, etc. If the preferred meeting location is to be accepted, the next step 550 is to generate an acknowledgement -accept' communication. Alternatively, if the preferred -12 -meeting location is to be declined, the next step 560 is to generate an acknowledgement - decline' communication.

Finally, the acknowledgement communication (whether accept or decline) is sent, in step 570.

As will be appreciated by a skilled artisan, the use of the terms "client communication device" and "server communication device" are not intended to be limiting, and are used to clarify the roles of the devices. That is to say, the server communication device provides the service of determining a preferred meeting location.

In determining the preferred meeting location, the meeting application program estimates the most convenient location at which the users of the client communication device and the server communication device may meet. For example, the most convenient location will most likely be substantially half way between the two, or some preferred location near the half way location based on user profile.

This may be achieved by way of geocoding and geodata.

Geocoding refers to the assignment of alphanumeric codes or coordinates to geographical reference data. Geodata refers to digital data that represents the geographical location and characteristics of natural or man-made features, phenomena and/or boundaries of the Earth.

Further information regarding geocoding and geodata may be found at Ilttp://www.opengeospatiai.ocg.

It is further envisaged that the meeting application program may also determine a preferred meeting time.

-13 -This may be based on an estimated travel time to the preferred location.

In addition, or alternatively, the meeting application program may be able to access a calendar application, or similar organiser application, on the communication device to determine the user's availability.

In this manner, when generating a location communication, the meeting application program running on the client communication device may include information relating to the availability of the user, for example during that day or over the coming week.

Thus, when the meeting application program running on the server communication device determines a preferred time, it may determine the preferred time based on the availability of the invitees, including the availability of the organiser.

In an alternative embodiment of the invention, a user of the client communication device 210 may provide information relating to a desired meeting location and/or meeting time within the location communication 230. In this way, the meeting application program running on the server communication device 220 takes such a desired meeting location and/or time into account when determining the preferred meeting location and/or time.

Referring now to FIG. 6, FIG. 7, FIG. 8, FIG. 9 and FIG. 10, there is illustrated a process for arranging a meeting according to an alternative embodiment of the invention. A process 600 in FIG. 6 is initiated by the -14 -generation and sending of a proposal communication 625 by a server communication device 620 to a client communication device 610.

A method 700 of generating the proposal communication 625 is illustrated in FIG. 7. The method 700 starts at step 710, by starting a meeting application program. Next, in step 720, the meeting application program identifies one or more meeting invitee(s). For example, the meeting application may access an address book or contacts list and display such to a user in the form of a list. The user may then select from the list those people they wish to invite.

Alternatively, the user may simply enter details of one or more invitee(s) manually by way of a keypad or the like of the server communication device. The meeting application then generates a proposal communication, in step 730. Finally, the meeting application program sends the proposal communication to the one or more identified invitee (s).

Referring back to FIG. 6, upon receipt of the proposal communication 625, the client communication device 610 generates a location communication 630, which it sends back to the server communication device 620.

A method 800 of generating the location communication is illustrated in FIG. 8. The method 810 starts at step 805, with the receipt of the proposal communication, followed by starting a meeting application program in step 820. Next, in step 830, the meeting application program determines the current location of the client communication device 610. This may be achieved by any suitable means, as hereinbefore indicated.

For example, the communication device may comprise global position satellite (GPS) technology, which the meeting application program is arranged to use to determine its current location.

Alternatively yet, a user of the communication device may enter, by way of a user interface of the communication device, a location identifier, such as a post code, longitudinal and/or latitudinal coordinates, or a street name etc. Next, in step 840, the meeting application program then generates a location communication comprising information relating to the location of the client communication device. Finally, in step 850, the location communication is sent back to the sender of the received proposal communication.

Referring back to FIG. 6, upon receipt of the location communication 630, the server communication device 620 generates a confirmation communication 640, which it sends back to the client communication device 610.

-16 -Referring now to FIG. 9, a method 900 of generating the confirmation communication 640 is illustrated. The method 900 starts at step 910, with the receipt of the location communication 630. The next step 920 comprises starting a meeting application program. The meeting application program then extracts location information relating to the sender of the location communication, in step 930, which for this embodiment is the client communication device 610.

Next, in step 935, the meeting application program identifies the sender of the location communication. The meeting application then determines whether the sender of the location communication is the last invitee to send a location communication, in step 980.

For example, when the server communication device 620 sends out a proposal communication 625, as illustrated in FIG. 7, the meeting application saves a list of invitees to whom the proposal communication 625 was sent. For example, for a device such as the radiotelephone 100 illustrated in FIG. 1, the list of invitees is saved within the memory element 140.

Subsequently, when the server communication device 620 receives a location communication, the meeting application identifies the sender of the location communication, and confirms that the sender is listed as one of the invitees to whom a proposal communication was sent. Once the sender has been confirmed, an indication that a location communication has been received from the sender is saved.

-17 -The meeting application program then determines whether a location communications have been received from all invitees, or whether a meeting confirmation is still required from one or more invitees. If a meeting confirmation is still required from one or more invitees, then the location information relating to the sender of the received confirmation is saved, in step 990.

It is within the contemplation of the invention that a user of the server communication device 620 may be prompted as to whether they wish to send a reminder to any invitees from whom a location communication is required.

If location communications have been received from all invitees, then the meeting application program retrieves the saved location information for the invitees, in step 985. Next, in step 940, the meeting application program determines the current location of the server communication device 620.

In the same way as for the client communication device 610, this may be achieved by any suitable means. For example, the communication device may comprise global position satellite (GPS) technology, which the meeting application program is adapted to use to determine its current location.

Alternatively, for communication devices operating within a cellular network, the meeting application program may be configured to determine the current location by way of identifying the current network cell in which it is -18 -operating, and thereby determine its approximate geographical location.

Alternatively yet, a user of the communication device may enter, by way of a user interface of the communication device, a location identifier, such as a post code, longitudinal and/or latitudinal coordinates, or a street name etc. In step 950, the meeting application program then determines a preferred meeting location. The determination of a preferred meeting location is described in further detail below.

The meeting application subsequently generates a confirmation communication comprising information relating to the preferred meeting location, in step 960.

Finally, in step 970, the confirmation communication is sent.

Referring back to FIG. 6, upon receipt of the confirmation communication 640, the client communication device 610 generates an acknowledgement communication 650, which it sends back to the server communication device 620.

The process of generating the acknowledgement communication may be the same as that for the previous embodiment, namely that illustrated in FIG. 5.

In the case where the meeting location is declined, it is within the contemplation of the present invention that the acknowledgement communication may further comprise -19 -information relating to the reason for the declination, and/or a proposal for an alternative location.

Referring back to FIG. 6, upon receipt of the acknowledgement communication 650, the server communication device 620 processes the acknowledgement communication 650.

Referring now to FIG. 10, there is illustrated a method 1000 for processing the acknowledgement communication 650. The method 1000 starts as step 1010 with the receipt of an acknowledgement communication. The next step 1020 comprises starting the meeting application program. The meeting application program then extracts the acknowledgement information from the acknowledgement communication, in step 1030.

In step 1040, the meeting application determines whether the meeting has been accepted, based on the extracted information. If the meeting has been accepted, the meeting application program saves the acknowledgement information, in step 1050.

Alternatively, if the meeting has been declined, the meeting application program retrieves saved location information for invitees, in step 1060. Next, in step 1070, the meeting application program determines the current location of the server communication device 620.

In the case where the acknowledgement communication comprises information relating to the reason for the declination and/or information relating to a proposed alternative location, this may be taken into account by the meeting application program. The meeting application -20 -program then determines an alternative meeting location, in step 1080. In step 1090, the meeting application program then generates a confirmation communication.

Finally, the confirmation communication is sent to all invitees, in step 1095.

In the case where the meeting has been declined, and a confirmation communication is sent, client communication devices to which the confirmation communication is sent are required to send acknowledgement communications in response to the new confirmation communication.

As previously mentioned, in an alternative embodiment of the invention, a user of the client communication device 610 may provide information relating to a desired meeting location and/or meeting time within the location communication 630. In this way, the meeting application program running on the server communication device 620 takes such a desired meeting location and/or time into account when determining the preferred meeting location and/or time.

As will be appreciated by a skilled artisan, the invention provides the advantage that a meeting can be scheduled based on the location of one or more invitees without the need for a dedicated central server. This substantially alleviates the problems and costs

experienced by prior art methods of invitees being

required to be part of a single organisation, such as a company, or to have previously registered with a central server.

-21 -Furthermore, the invention provides for increased portability, since a user is not required to be at their desk, or connected to a corporate network etc. Also, improved security is provided, since it is not necessary for a user to be continuously tracked by a central system.

Referring now to FIG. 11, there is illustrated a process 1100 of arranging a meeting according to a still further embodiment of theinvention. The process 1100 comprises a client communication device 1110, a server communication device 1120 and a geocoding system 1145, for example an OpenLS (TM) compliant GeoMobility server.

Detailed information regarding OpenLS compliant GeoMobility servers can be found at http://www.opengeospatial.org.

The process starts with the server communication device 1120 sending a proposal communication 1125 to one or more client communication devices 1110, in the same way as described with reference to FIG. 6 and FIG. 7.

Next, the or each client communication device 1110 responds by sending a location communication 1130 to the server communication device 1120, in the same way as described with reference to FIG. 6 and FIG. 8.

On receipt of the meeting request 1130, the server communication device 1120 sends a geocoding request 1135 to the geocoding system 1145.

-22 -The geocoding request 1135 is preferably sent once a location communication 1130 has been received from each client communication device 1110. The geocoding request comprises information relating to the location, etc. of the, or each, client communication device 1110 and the server communication device 1120.

The geocoding system 1145, upon receipt of the geocoding request 1135, determines a substantially central location based on the location of the plurality of communication devices.

It is also envisaged, in one embodiment of the invention, that the geocoding system 1145 may also simply send back the geocoded location to the organizer device that determines the central location.

The geocoding system 1145 then sends a geocoding response 1137 back to the server communication device 1120, the geocoding response 1137 comprising information relating to the substantially central location. The geocoding system 1145 may further determine an estimate of the travel times between the locations of the communication devices and the substantially central location. Where this is the case, the geocoding response 1137 further comprises information relating to such travel times.

Following the receipt of the geocoding response 1137, the server communication device 1120 determines a preferred meeting location, based on the information relating to the substantially central location, provided by the geocoding response 1137. This may involve simply using the substantially central location as the preferred -23 -meeting location. Alternatively, the server communication device 1120 may use the information relating to the substantially central location to determine a suitable meeting location in the vicinity of the substantially central location. For example, the server communication device 1120 may determine a coffee shop, bar, cinema or the like in the vicinity thereof.

The server communication device 1120 then sends a confirmation communication 1140 to the, or each, client communication device 1110, containing information relating to the preferred meeting location.

The confirmation communication 1140 may also comprise information relating to a preferred meeting time, determined by the server communication device 1120. For example, a preferred meeting time may be based on travel times for each communication device to the preferred meeting location. As previously mentioned, such travel times may be determined by the geocoding system 1145.

Alternatively, travel times may be determined by the server communication device 1120 itself.

Additionally or alternatively, the preferred meeting time may be determined based on the availability of the one or more invitee(s), including the availability of the organiser.

As mentioned in relation to a previous embodiment of the invention, the communication devices may each comprise a meeting application program able to access a calendar application, or similar organiser application, on the -24 -communication device to determine the user's availability.

In this manner, the, or each, client communication device 1110 provides information relating to the availability of the user within the location communication 1130. Thus, the server communication device 1120 is able to determine a preferred meeting time based on the availability of the one or more invitee(s), including the availability of the organiser.

Following receipt of the confirmation communication 1140, the, or each, client communication device 1110 sends an acknowledgement communication 1150, in the same way as described with reference to FIG. 5.

As an optional part of the process 1100, once a meeting has been arranged, including a preferred meeting location, a communication device may send a directions request 1155 to the geocoding system 1145. For example, the direction request 1155 may comprise information relating to the current location of the communication device, and information relating to the preferred meeting location.

Following receipt of a directions request, the geocoding system 1145 determines directions from the current location of the communication device to the preferred meeting location. The geocoding system 1145 then sends a directions response 1160 back to the communication device comprising information relating to the directions.

-25 -Alternatively, it is within the contemplation of the invention that the geocoding system 1145 may determine directions following receipt of the geocoding request 1135, and that information relating to directions for each communication device is provided within the geocoding response 1137. The server communication device 1120 may then provide information relating to appropriate directions for client communication devices 1110 in the confirmation communication 1140.

Although the embodiment of the invention illustrated in FIG. 11 utilises a geocoding server system, unlike the prior art, it is not necessary for a communication device to be part of a single organisation, such as a company, or to have previously registered with a central server.

This is the case since the geocoding system is provided with the necessary information by the server communication device.

It is envisaged that the various communications may be achieved using any suitable format, for example by way of Multimedia Messaging Service (MMS) messages, email, etc. FIG. 12 illustrates an example of fields and field values that could be added to/adapted to MMS message formats, as would be appreciated by a skilled artisan.

It will be appreciated that any suitable distribution of functionality between different functional units or elements may be used without detracting from the inventive concept herein described. Hence, references to specific functional devices or elements are only to be seen as references to suitable means for providing the -26 -described functionality, rather than indicative of a strict logical or physical structure or organization.

Aspects of the invention may be implemented in any suitable form including hardware, software, firmware or any combination of these. The elements and components of an embodiment of the invention may be physically, functionally and logically implemented in any suitable way. Indeed, the functionality may be implemented in a single unit or IC, in a plurality of units or ICs or as part of other functional units.

Although the invention has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the invention is limited only by the accompanying claims. Additionally, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognize that various features of the described embodiments may be combined in accordance with the invention. In the claims, the term comprising' does not exclude the presence of other elements or steps.

Furthermore, although individual features may be included in different claims, these may possibly be advantageously combined, and the inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. Also, the inclusion of a feature in one category of claims does not imply a limitation to this category, but rather indicates that the feature is equally applicable to other claim categories, as appropriate.

-27 -Furthermore, the order of features in the claims does not imply any specific order in which the features must be performed and in particular the order of individual steps in a method claim does not imply that the steps must be performed in this order. Rather, the steps may be performed in any suitable order. In addition, singular references do not exclude a plurality. Thus, references to "a", "an", "first", "second" etc. do not preclude a plurality.

Thus, an improved communication device, method for arranging a meeting and computer program product comprising an application program have been described wherein the aforementioned disadvantages associated with

prior art arrangements have been substantially

alleviated.

Claims

-28 -Claims 1. A communication device comprising a transceiver operably

coupled to a signal processor comprising a meeting application program for execution by a signal processing function of a communication device, characterised in that, the transceiver receives a location communication associated with arranging a meeting and in response thereto the meeting application program comprises code that: determines a location(s) of a sender of the location communication based on information provided within the location communication; determines a current location of the communication device; identifies a meeting location and/or meeting time, based on the location of the sender of the location communication and the location of the communication device; and generates a confirmation communication to the sender(s) of the at least one location communication, the confirmation communication comprising information relating to the identified meeting location and/or meeting time.
2. The communication device of Claim 1 further characterised in that the meeting application program determines the meeting location by estimating a convenient location for a plurality of invitees, including the organiser identified in the location communication.

-29 -
3. The communication device of Claim 2, characterised in that the convenient location is substantially a central location between the plurality of invitees, including the organiser, or a central location determined from one or more sender preferences.
4. The communication device of any preceding Claim further characterised in that the meeting application program determines a meeting location by way of geocoding and geodata.
5. The communication device of any preceding Claim further characterised in that the meeting time is based at least in part on estimated travel times for each invitee, including the organiser, to the location.
6. The communication device of Claim 5 further characterised in that the meeting time is based at least in part on an indicated availability of one or more of the invitees, including the organiser.
7. The communication device of any preceding Claim further characterised in that the meeting application program is adapted to access a calendar application, or similar organiser application, on the communication device, from which the meeting application is able to determine a user's availability.
8. The communication device of any preceding Claim further characterised in that the location communication further comprises information relating to a desired meeting location and/or time.

-30 -
9. The communication device of any preceding Claim further characterised in that the location communication is a response to a proposal communication generated by the meeting application program.
10. The communication device of Claim 9 further characterised in that the meeting application program is configured to identify invitees to whom the proposal communication is to be sent.
11. The communication device of Claim 9 or Claim 10 further characterised in that the meeting application program determines a meeting location and/or meeting time upon receipt of a plurality of location communications from all invitees to whom a proposal communication was previously sent.
12. The communication device of Claim 11 further characterised in that upon receipt of a location communication. The meeting application program saves information, and/or any other information provided in the received location communication if a further location communication is still required from a further invitee
13. The communication device of any preceding Claim, further characterised in that upon receipt of the or each location communication the meeting application program sends a geocoding request to a geocoding system, and upon receipt of a response from the geocoding system, determines a meeting location and/or meeting time.
14. The communication device to any preceding Claim further characterised in that the meeting application -31 -program comprises code to generate a location communication.
15. The communication device of Claim 14 further characterised in that the meeting application program determines a current location of the communication device and provides information relating to the current location of the communication device within the location communication.
16. The communication device of Claim 14 or Claim 15 further characterised in that the code of the meeting application program determines one or more invitees to whom the location communication is to be sent.
17. The communication device of any preceding Claim further characterised in that the code of the meeting application program generates an acknowledgement communication in response to receiving a confirmation communication.
18. The communication device of any preceding Claim further characterised in that the communication device comprises global positioning satellite (GPS) logic operably coupled to the transceiver, which the meeting application program is adapted to use to determine its current location.
19. The communication device of any preceding Claim further characterised in that the communication device operates within a cellular network; the meeting application program being configured to determine the current location of the communication device by way of -32 -identifying a current network cell in which it is operating, and thereby determine its approximate geographical location.
20. The communication device of any preceding Claim further characterised in that the meeting program application determines the current location of the communication device by way of a user entering one or more of the following: i.a post code; ii.longitudinal and/or latitudinal coordinates; iii.a street name.
21. The communication device of any preceding Claim further characterised in that the meeting application program is configured to access entries stored within an address book or contact list from which a user is able to select invitees.
22. The communication device of any preceding Claim further characterised in that the meeting application program sends a directions request to a geocoding system; and the transceiver receives a response from the geocoding system providing information relating to directions from the current location of the communication device to the meeting location.
23. The communication device of any preceding Claim further characterised in that the various communications generated by the meeting application program comprise either a multimedia messaging service (MNS) format or an email format.

-33 -
24. A method of arranging a meeting between a server communication device and one or more client communication devices, the method comprising the steps of: sending a location communication from the or each client communication device to the server communication device; upon receipt of the or each location communication by the server communication device, determining the current location of the server communication device; determining a meeting location and/or meeting time based at least in part on location information provided in the or each location communication and the current location of the server communication device; and generating a confirmation communication comprising information relating to the meeting location and/or meeting time.
25. The method of arranging a meeting of Claim 24 further characterised in that prior to sending a location communication from the or each client communication device, the server communication device sends a proposal communication to the or each client communication device.
26. The method of arranging a meeting of Claim 24 or Claim 25 further characterised by sending a geocoding request to a geocoding system by the server communication device and receiving a geocoding response from the geocoding system and determining a meeting location and/or time in response thereto.
27. The method of arranging a meeting of any of preceding Claims 24 to 26 further characterised in that -34 -the server communication device determines a preferred meeting time based on one or more of the following: i. travel times ii. availability of invitees
28. The method of arranging a meeting of any one of preceding Claims 24 to 27, characterised by method sending a directions request to a geocoding system, and receiving a response therefrom comprising directions to the meeting location.
29. A computer program product comprising program code for arranging a meeting according to any of preceding Claims 24 to 28.
30. A meeting application program as hereinbefore described, with reference to and as shown in the accompanying drawings.
31. A method of arranging a meeting as hereinbefore described with reference to and as shown in the accompanying drawings.
32. A communication device as hereinbefore described with reference to and as shown in the accompanying drawings.