Patent Application
20080062893
The present invention relates generally to a method and apparatus for exchanging information in a communication system. More specifically, the invention relates to a communication system, which connects to a private or public data communication network and to a public or private telecommunication network.
The present evolution of data-communication is such that more and more users gain access to the Internet worldwide. The Internet has become both a source of knowledge but also a marketplace for business, and it is attracting more and more users. Currently there is a high pressure on the data-communications industry to provide solutions that allow everyone to gain access to Internet. Broadband solutions are continuously developed and both local as well as national access networks are planned and launched. The presently most common method of modem access through the telecommunications network (e.g., the Public Switched Telecommunication Network, PSTN provider) is being replaced by other ways of access with a possibility to higher data rates, e.g., through electric power and cable TV providers.
At the same time, the telecommunications industry is struggling another battle; that of providing mobility to each and every user. Traditionally, telecommunication has been focused on voice communication. With the increase of data communication however, other demands are arising (e.g., higher data rate transfer), but also new possibilities. Evolutions of mobile systems are presently in a period when more and more packet-based systems will be deployed. Packet switched systems have, in contrast to circuit switched systems, certain advantages when it comes to transfer of data-communication. In a packet switched system, a user is only utilizing a transmission resource when system control signaling or user information is transmitted. In a circuit switched system, a user is allocated a transmission resource continuously, even though no current transfer is active. Circuit switched systems have some obvious advantages in real-time voice communication, since it is difficult to predict the communication. For data-communication, it is not as important to predict the transmission resources required, since the demands on delay and delay variations are not as crucial to the communication quality as for voice. It is therefore possible to allow more users onto the transmission resources by allowing usage thereof only when there is something to transmit and leave the channel available for additional users otherwise.
One such system is the packet data evolution of the mobile communication system pursuant to the ETSI GSM specification, called General Packet Radio Service (GPRS). With GPRS, higher bit rates and more users may be allowed than what is possible today, when data communication is deployed on a circuit switched channel. GPRS is a step towards mobility for data communication users, in contrast to GSM, which is optimized for mobility for “traditional” telecommunication users, i.e., real-time voice communication users.
The data-communication run over the telecommunications networks today is usually initiated by an access to an Internet- or a mail server. A user logs on to a distant server and accesses the data-communications network through, e.g., modem pools. The user dials up the modem pool and is therefore connected to a server, from which access can be made to both local as well as global networks. Browsers like e.g., Microsoft Explorer or Netscape Navigator are used to navigate on the Internet and switch between Internet pages or addresses. Users and institutions usually design their own data objects, or homepages, on an internal or external network that provides personal information or any other kind of information. Once connected to the data network a user may access these data objects by entering the correct address. The address is often selected by combining a node name in the network (e.g., server name) and an arbitrary text-string. Typically, it is not trivial to find a desired data object, since the text strings and server names are not obvious.
Addressing in a telecommunications network, e.g., when engaging in a voice communication is usually performed by entering a telephone number on a User Equipment (UE), like a mobile telephone. A telephone number is a world-wide, unique addressing string. A calling party (A-party) dials the addressing string (B-number) to the called party (B-party). Dependent on what type of network the A-party is a subscriber on, the call request is routed through one or several public telecommunication networks to the correct addressee and the communication may begin.
The above principle also applies when a user wishes to connect to the Internet from a computer connected to a telecommunications network. The user connects to a data-communications network by dialing a B-number to a modem pool, from which accessing the data-communications network is possible. There are no information or interaction possibilities with the called server other than this access opportunity.
Applicants have identified that there is a problem in the present way of accessing the Internet for specific data objects because of the non-obvious way of addressing data objects. There is further a need in the telecommunications industry to provide a simpler way of accessing the Internet and to guide a user by other means than a modem number to call, from where the user is left on her own to be further guided to the desired homepage or data object.
Relatedly, Applicants have also identified that there is a problem with current systems and methods. In particular, current systems and methods do not provide the ability to condition secondary information exchanged between two mobile devices that are engaged in a primary communication, based on both a particular call event and calendar information that is personal to one or more of the users of the devices.
The present invention overcomes the above identified deficiencies of providing the ability to condition secondary information exchanged between two mobile devices that are engaged in a primary communication, based on both a particular call event and calendar information that is personal to one or more of the users of the devices.
According to one embodiment of the systems and methods described herein, a method for supplying a data object to a user of a communication device is provided. The method comprises the steps of: receiving a call or session request from a first communication device seeking to initiate a call or session with a second communication device; determining whether the second communication device has authorized the receipt of calls from or sessions with the first communication device; establishing the call or session between the first communication device and the second communication if the first communication device is authorized; and transferring, in a first transferring step, a data object to the first communication device if the first communication device is not authorized.
In another embodiment of the various systems and methods described herein, a method for supplying a data object to a user of a communication device is provided. The method comprising the steps of: generating a first data object at least a first predetermined period of time prior to an event associated with a first communication, wherein the first communication device is in an established call or session with a second communication device; transferring, in a first transferring step, the first data object to the first communication device; generating a second data object at least a second predetermined period of time prior to the event associated with the first communication device; transferring, in a second transferring step, the second data object to the first communication device or the second communication device; generating a third data object at least a first predetermined period of time after the event associated with the first communication device; and transferring, in a third transferring step, the third data object to the first communication device, the second communication device or a third communication device.
In yet another embodiment of the various systems and methods described herein, a device for supplying a data object to a user of a communication device is provided. The device comprising computer software stored on a computer-readable media executable to perform: (i) determining a period of time prior to or after an event associated with a second communication device; and (ii) logic for transferring a request for a first, second and third data objects from the first communication device to a data object server, wherein the first, second and third data objects are associated with the event and are to be rendered at the device, the second device or a third device.
In still another embodiment of the various systems and methods described herein, a downloadable application or module for supplying a data object to a user of a communication device is provided. The downloadable application or module being stored on a computer-readable media executable to perform: (i) determining a period of time prior to or after an event associated with a second communication device; and (ii) logic for transferring a request for a first, second and third data objects from the first communication device to a data object server, wherein the first, second and third data objects are associated with the event and are to be rendered at the device, the second device or a third device.
The invention will now be more thoroughly described and features and advantages will become readily apparent by reading the following detailed description, where references will be made to the accompanying figures, where:
First a network overview. The present invention will now be described with references to a telecommunications system based on GSM as a circuit switched communication system and GPRS as a packet switched communications system. It should however be noted that the embodiments described are to be considered exemplary and that other packet and circuit switched systems may equally well be considered, both fixed—as well as mobile—and with any access technology, e.g., Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Time Division Duplex (TDD), Frequency Division Duplex (FDD) or any combinations thereof. The invention is not restricted to any specific type of communications network or access technology.
The data network, 120, typically includes one or several routers (not illustrated) and data bridges such that several nodes may be interconnected and communicate with each other. The data network used in connection with the present invention includes also a data object server, 130. Typically, pluralities of data object servers are included in a data network, although, for reasons of explanation and clarity, only one data object server, 130, is illustrated in
Element 140 can in some embodiments be a PSTN/ISDN, and then element 150 could also be a mobile phone. In other embodiments there can also exist the case of all IP, i.e., UE 100 has real-time voice communication with a packet data device.
Now for subscriber description. According to one aspect of the present invention a data object server, 130, includes graphical information objects, i.e., phonepages, associated to a telephone number. The telephone number is identical to a subscriber number, i.e., an A- or B-number, addressing an originating user equipment or a terminating user equipment, respectively. The A-party, upon dialing a B-number, connects to a data object server, 130, by way of PS communication channel and receives a data object, i.e., a “phonepage” stored in a memory position in the data object server, with a memory address corresponding to the B-number dialed. The phonepage may consist of information about the B-party, or it may simply provide an immediate access to an internal or external data network as maintained by the B-party subscriber. Alternatively, the B-party phonepage may consist of information regarding a B-party user, e.g., phone number, address and other information. After having received the B-party phonepage, one or several procedures may follow. If the B-number is addressing a POT, 150, a circuit switched voice connection may be setup. If the B-number is addressing another device, other events may occur. This is of course also dependent upon the A-party device, UE, 100, used.
In a variant of the present invention, the UE, 100, does not support the use of a PS communication channel whereby data objects can be retrieved by other means, such as a Short Message Service (SMS) or a temporary CS communication channel. In a variant of the present invention, a PS communication channel, for example having a particular QoS, is used for conveying speech within the communication system 10 whereby the PSTN, 140, and the data network, 120, is interconnected by some means (not shown in
And now protocol functionality. According to one aspect of the present invention a data object server, 130, includes graphical information objects, i.e., phonepages, associated with an address indication such as a telephone number, or an Internet address such as an IPv6 address. The telephone number is identical to a subscriber number, i.e., an A- or B-number, addressing originating user equipment or a terminating user equipment, respectively. The A-party, upon dialing a B-number, connects to a data object server, 130, by way of PS communication channel and receives a data object, i.e., a “phonepage” stored in a memory position in the data object server, with a memory address corresponding to the B-number dialed. The data object server may comprise the phonepage with information about the B-party directly, or it may simply provide an immediate access to a location in an internal or external data network as maintained by the B-party subscriber, i.e., the object server 130 first functions as a number server providing a translation of the provided B-number to a corresponding URI where the phonepage resides, which may be at a physically separate phonepage object server. The translation and provision of the actual requested phonepage can be either transparent, i.e., the phonepage number server forwards, or dispatches, the phonepage request to an appropriate phonepage object server, which phonepage object server communicates directly, or indirectly via the name server, to the requester, or the phonepage number server returns the URI of the requested phonepage to the requester after which the requester will be redirected by using the URI to request the desired phonepage.
The B-party phonepage may comprise information regarding a B-party user, e.g., phone number, address and/or other information. The B-party phonepage may also comprise information regarding the addressed B-party's user equipment, which, for example, can be a fax. After having received the B-party phonepage, one or several procedures may follow. If the B-number is addressing a POT, 150, a circuit switched voice connection may be setup. If the B-number is addressing another device, other events, such as when a pay service is used, may occur. This is of course also dependent upon the A-party device, UE, 100, used.
According to another aspect of the present invention a phonepage can be associated with an Internet address such as an IPv6 address, SIP address or an email address. For example, an A-party, upon setting up a communication link with a web-page to a thermostat of his or her summer house to thereby control/check the temperature, will receive a data object which, for example, identifies the thermostat and comprises a link to the manufacturer's home page, and/or other communication means to the manufacturer. In another example, an A-party desires to set up a conference call by means of a conference telephone located in a conference room. Upon initiation of the communication, the A-party will receive a data object which is linked to the conference telephone by means of its telephone number, http address or IP address. The data object, the conference telephone's phonepage, can suitably comprise information concerning the locality of the conference phone, the size of the conference room, and/or a booking schedule. In still another example, an A-party desires to transfer a facsimile. Upon choosing or initiating transmission to a fax-machine, the phonepage of the fax machine is requested and returned to the A-party. A phonepage of a fax machine might comprise information concerning the locality of the fax, whose fax machine it is, and/or who has access to the fax machine. In still a further example, an A-party desires to transfer an email to a B-party. Then, upon choosing or writing the email address, i.e. perhaps even before a message is composed, the phonepage of the email address is requested and returned to the A-party. A phonepage of an email address might comprise information concerning the owner, the B-party user, of the email address, other means of communication with the owner, and/or schedule or availability of the owner. A phonepage is a data object that is linked to a unique identifier such as a telephone number or an internet address such as an IPv6 address, but not located or retrieved from the place that the unique identifier identifies.
The A-party initiates a request in step 230, possibly after encryption in step 220, and sends this request via a communication channel, (e.g., packet switched as illustrated in
The data object request in 230 may, according to a variant of the invention, be answered by the data object server in an encrypted format, in which case a decryption in step 250 follows the reception of the response in the user equipment.
In the next step follows a rendering procedure in step 260, where the data objects are displayed according to the capability of the UE after which the procedure is ended in step 299. Typically after step 299, there will follow one or several procedures according to the capability of the A-party UE or the type of equipment addressed by a B-number. For example, a call may be setup or a call may be disconnected. According to one of the above mentioned embodiments, where a continuous triggering event is that a call is conducted, special advantages may be relevant (e.g., commercial information may be sold in response to a dialed B-number allowing easy payment for such information).
The above described general solution to obtain a data object connected to an address indication may of course be varied in a number of different ways, depending on, e.g., the capabilities of communication of the UEs involved. For example, a method of simultaneously requesting, encrypting, obtaining, decrypting and rendering a sequence of data objects can also be applied in a variant of the present invention.
User equipment, like mobile stations, is today developed to handle both packet switched and circuit switched communication simultaneously. These are generally referred to as class A mobile stations. Other mobile station designs allow packet switched and circuit switched communication alternatively, i.e., no simultaneous PS and CS transmission and reception. These are generally referred to as class B mobile stations.
In
For the circuit switched procedures, a voice connection with a B-party is initiated in step 430, a communication recourse is assigned by a mobile network over which a telephone conversation may take place. The telephone conversation is ended in step 440 as any ordinary voice call, for example by pressing a designated button on the mobile station or hanging up a handheld part of a fixed network telephone. Ending the call also involves de-allocation of relevant communication resources within the circuit switched part of the mobile communication network as well as e.g., any PSTN resources involved in the connection.
Now follows an example of a protocol implementation between the UE (100) and the Data Object Server (130).
The phonepage service relies on the following components:
The PhonePage Number Service (PNS) is implemented using two node types: local and root PNS. The root PNS receives registrations from PWSs and keeps the local PNS updated. The local PNS acts as a kind of “proxy” between the terminal and the PWSs. In one aspect of the invention a local PNS contains an update client that regularly checks for updates with the root PNS. If there are entries more recent than the last successful local PNS update time, the new entries are conveyed from the root PNS to the local PNS. If communication is performed over the open Internet, information may be encrypted (e.g., using the https: or IPSec protocol). There are other means for keeping the different databases up to date. For example, the root PNS may, upon changes in its database, contact a plurality of local PNS's and, based on their individual update status, convey any changes to the local PNS's. Again information may be protected as described above.
An MT—PNS PROTOCOL, first the PNS REQUEST. In general when the Mobile Terminal (MT) detects an event, the MT send a PNS Request to the Local PNS. The PNS Request from a MT client to the PNS is implemented as a HTTP request using the GET method. The URI used in the HTTP request is denoted request URI. The request URI is a URI identifying the resource upon which to apply the request. The request URI contains the host name of the Local PhonePages Number Server (PNS), a host path (e.g., denoting an appropriate server) and a parameter list. No specific header information in the HTTP request is required.
Two alternatives for the parameter list are defined. In the first alternative, the parameters are binary coded and the corresponding binary string is then Base64 encoded. In the second alternative the parameters are given using the standard URL encoding scheme for passing parameters. Below the parameter list when using the URL encoding scheme is described.
The request URI (Req_URI) is as follows:
The op_code is used to enable distributed PNS service. The op_code has the following value:
Parameter Values
The contenttype_value is coded as follows:
All other values are reserved.
The eventnumber_value is coded as follows:
All other values are reserved.
The domain field is coded as follows:
The id field indicates a public identification of a peer user (e.g. telephone number) that is relevant for the particular event.
The id field indicates a public identification of the mobile terminal user (e.g., telephone number) that is relevant for the particular event.
The id field indicates a private identification of the mobile terminal user (e.g., IMSI) that is relevant for the particular event.
Example: grc=640—480—8
The coding of the audiocap_value is for further study.
This parameter indicates the country where the PMT is currently registered. The country code is given according to GSM 03.03.
This parameter indicates the PLMN where the PMT is currently registered. The operator code is given according to GSM 03.03.
This parameter indicates the country where the PMT has a subscription. The country code is given according to GSM 03.03.
This parameter indicates the PLMN where the PMT has a subscription. The operator code is given according to GSM 03.03.
All other values are reserved.
All other values are reserved.
All other values are reserved.
The terminaltype_value is coded as follows:
All other values are reserved
Local PNS Response. After receiving and interpreting a PP Request message, a Local PNS server responds with a standard HTTP response message containing the phonepage content. Note that part of the phonepage content may be references (e.g., links) to resources located on other servers (e.g., the PWS) than the Local PNS. In such cases, the actual transfer of the referenced data will be carried out between the MT and the servers hosting the references resources and not pass through the Local PNS.
A L-PNS—PWS PROTOCOL. When the Local PNS receives a PNS Request from the MT, the Local PNS looks up the address to the PWS where the requested phonepage is located. The Local PNS then requests the phonepage from the PWS by sending a HTTP request equal to the PNS Request message as described above. Note that the host_name and host_path parts of the request URI in this case are equal to the host name and path of the PWS. The PWS responds with a standard HTTP response message containing the phonepage content.
A PWS—Root PNS PROTOCOL. The protocol between the PWS and the Root PNS is based on HTTP and is used for registration and management of phonepage entries in the PNS. In order to provide a secure transport mechanism the HTTPS (Secure Hypertext Transfer Protocol) can be used.
In abnormal cases. If the PWS issuing the request is not authorized, the root PNS responds with status code 401. If the information in the message body of the request message is empty or not complete the root PNS responds with status code 204. If the information in the message body of the request message is unreadable or not understandable the root. PNS responds with status code 400. If the identity of the entry (entry-id) in the request message is found to be invalid (e.g., not a valid identity for the domain given in the domain element), the root PNS responds with status code 406. If a root PNS entry already exists for the requested identity (entity-id), the root PNS responds with status code 409.
In abnormal cases. If the PWS issuing the request is not authorized or if the PWS is not the same as the one that previously registered the entry, the root PNS responds with status code 401. If the information in the message body of the request message is empty or not complete, the root PNS responds with status code 204. If the information in the message body of the request message is unreadable or not understandable, the root PNS responds with status code 400. If the identity of the entry (entry-id) in the request message is found to be invalid (e.g., not a valid identity for the domain given in the domain element), the root PNS responds with status code 406.
In abnormal cases. If the PWS issuing the request is not authorized, the root PNS responds with status code 401. If the information in the message body of the request message is empty or not complete, the root PNS responds with status code 204. If the information in the message body of the request message is unreadable or not understandable, the root PNS responds with status code 400. If the identity of the entry (entry-id) in the request message is found to be invalid (e.g., not a valid identity for the domain given in the domain element), the root PNS responds with status code 406.
Messages
Register Request
General
This message is sent by PWS to root PNS whenever a new root PNS entry is registered.
Syntax
The message body contains form data, encoded using the ‘application/x-www-form-urlencode’ format as specified in the Hypertext Markup Language—2.0 RFC 1866 with the following fields:
Register Response
General
This message is sent by the root PNS to PWS as a response to a REGISTER REQUEST message.
Syntax
The Status-Code in the response message indicates the result of a request to register a new entry in the root PNS. The root PNS responds with one of the following status codes.
UNRegister Request
General
This message is sent by the PWS to root PNS whenever a root PNS entry is to be removed.
Syntax
The message body contains form data, encoded using the ‘application/x-www-form-urlencode’ format as specified in Hypertext Markup Language—2.0 RFC 1866, with the following fields:
UnRegister Response
General
This message is sent by root to PNS to PWS as a response to a UNREGISTER REQUEST message.
Syntax
The Status-Code in the response message indicates the result of a request to register a new entry in the root PNS. The root PNS responds with one of the following status codes.
Status Request
General
This message is sent by the PWS to the root PNS to check the status of a root PNS entry.
The PWS may use the STATUS REQUEST message to retrieve information on a certain root PNS entry, e.g., upon reception of a REGISTER RESPONSE message with status code 409 (Conflict, entry already exists).
Syntax
The STATUS REQUEST is implemented as a HTTPS request using the POST method.
The message body contains form data, encoded using the ‘application/x-www-form-urlencode’ format as specified in Hypertext Markup Language—2.0 RFC 1866, with the following fields:
Status Response
General
This message is sent by root PNS to PWS as a response to a STATUS REQUEST message.
Syntax
The Status-Code in the response message indicates the result of a status request. The root PNS responds with one of the following status codes.
If, and only if, the status code is 200, the message body of the response contains form data, encoded using the ‘application/x-www-form-urlencode’ format as specified in Hypertext Markup Language—2.0 RFC 1866, with the following fields:
Terminal Capability.
The packet switched procedures basically follow the procedures described in connection to
As mentioned above, a class B type mobile station cannot handle two simultaneous connections, one packet and one circuit switched, so another approach to retrieve a phonepage is then necessary when setting up a circuit switched voice connection
If it is indicated that a phonepage is desired, then the following steps are to encrypt, 930, and send, 935, a data object request on a packet switched communication channel. As long as the packet session is not interrupted, 940, the download of data object continues to the A-party. Data objects are received in step 970, decrypted, if encrypted, in step 980 and rendered in step 990. In step 995 the data objects are detected and as long as there is more information to receive, step 995, and there is no interruptions in step 940, the data download continues. A possible interrupt may occur, e.g., when a user wishes to no longer wait for a complete download of a phonepage and instead initiates the circuit switched communication in step 950. This may be initiated by a time expiring or by manually indicating on a man-machine interface (MMI). At the latest, the circuit switched communication is initiated when there is no more phonepage data to download. According to another embodiment of the present invention the phonepage for a class B UE is obtained from the data object server, 130, upon call completion or whenever the UE is not involved in a call, and is stored locally in the UE being readily available upon a next triggering event.
So far, the retrieval of phonepages to display in A-party equipment has been addressed. It should be recognized that a B-party may similarly also display a phonepage related to a connection, preferably a phonepage identified with the A-party number. In
If the call is answered in 1030, the voice connection may follow the same procedures as those described in relation to
For reasons of clarification, several steps in the signaling between the UE 100 and the communication infrastructure 110; between the UE 100 and the data object server 130; have been omitted in several embodiments above, and focus has been put on the necessary and novel steps according to the invention, in the aforementioned signaling. It should be understood that other procedures (e.g., authentication, channel assignment and charging) might occur in addition to what has been described in the aforementioned signaling.
Terminal Implementation.
According to a variant of the invention the blocks 1210, 1220, 1230, 1240, 1250 and 1260 may be implemented on a plurality of computers. According to another variant of the present invention, the said plurality of computers may be located at a substantial distance.
B-number indication involves any means of indicating a B-number in an A-party UE. A first example of B-number indication procedure is described with reference to
A second example of B-number indication is by means of voice detection, whereby an incoming talk spurt is successfully matched with an entry in an internal database contained in a UE 100, whereby a valid B-number could be obtained in response to the aforementioned talk spurt.
A-number indication involves any means of indicating an A-number to a said UE 100. A first example of an A-number indication procedure is described with reference to
A second example of A-number indication is by means of sending an A-number or data objects in response to an A-number directly on a logical data communication link 161.
There are a number of possible technologies available that are suitable for implementing phonepage functionality in the UE (phonepage client). Examples of such technologies in the context of GSM include:
Independent of implementation, the main function of the client is to detect call events and launch the browser to the appropriate URL determined by event type, content type, other party's identity, own identity, HPLMN, VPLMN, visiting country code, terminal capability, and other parameters as described in this document. Additionally the client could provide functions for, e.g., activation and configuration of service, security, soft-keys and menus.
As an alternative to directly launching the browser the client may send an SMS to the server which would respond with a push message (e.g., WAP push) containing the phonepage.
Now follows a description of a possible implementation based on SIM toolkit (STK). The phonepage solution can be implemented in various ways with STK. It can be achieved by combining WAP with STK. It can also be done as a stand-alone solution without connections to WAP. A phonepage application can be divided into two parts, one that is menu driven and one that is event driven. The two parts of the application will remain integrated on the SIM. The event driven part handles functions for, e.g., automatic downloading of phonepages triggered by certain call events; the phonepage format may be WAP, SMS or similar. The menu driven part of the application handles functions for, e.g., service configuration, and manual user-friendly downloading of phonepages.
The SIM hosts several parameters that can be utilized for the PP services. This adds value to the solution both for WAP and non-WAP based solution. Example of such parameters are: event type, other party's identity, own identity, visiting country code, visiting operator code, and home operator code. Additional parameters such as content type, device capability, device type and data bearer can be obtained for example by UAProf (WAP) or native in the device.
STK Combined with WAP Browser in the Phone.
The WAP solution can be combined with phonepage-WAP specific parameters and content stored to be accessible on the SIM. This means that parameters that are not supported by WAP could be provided this way. The method can be applied in two ways to implement the phonepage solution. One is to use SMS for the request response in which the URLs will be downloaded or pushed from the PNS. The other (launch browser method) is to define the URL directly locally on the SIM without any preceding server communication. With the launch browser method, the SIM specifies browser, URL, gateway address and bearer among other parameters. This makes it possible for the SIM to define which WAP application that shall be addressed as well as how this shall be done. There is a standardized possibility in STK to start a WAP browser from the SIM. The solution would require support of the launch browser STK command. An overview of the corresponding signalling in the system is shown in
Another solution that requires a server request from the SIM could be implemented as a work-around if the launch browser STK command is not supported. An overview of the corresponding signalling is shown in
WAP Similar Browser on the SIM (Stand-Alone Solution).
There is also a possibility to implement the phonepage application with a WAP similar STK browser. This could be done based on the same principles as sketched for the real WAP case above. There are two different methods to implement this. With a stand alone STK application that is not integrated with the micro browser a network request would apply before the micro browser is launched. An overview of the corresponding system signalling is shown in
The phonepage application could also be fully integrated into the micro browser. This solution would require implementation in the micro browser to support event handling. The system signalling for this scenario is shown in the
Menu Driven Part.
Menus for, e.g., service configuration and manual phonepage download could be implemented using STK. Menus could be used both for the case of using a WAP browser in the phone and for the case of a micro browser on the SIM card.
Event Driven Part.
STK supports detection of several call events including: an outgoing call is initiated, an incoming call, a call is answered, and a call is disconnected. There are several methods to implement the event driven part using STK:
With this method the STK application would automatically be launched via an STK event. It can be combined with call control to add the outgoing call event. The STK application would be launched slightly after the call is set up or when the call is terminated.
Call Control Managed Solution without STK EVENT Handling.
With this method the STK application would be automatically launched every time a call is to be set up. The STK application would be launched slightly after the call is set up or when the call is terminated. Nevertheless, with this method the event for the outgoing call could be handled to give the possibility for the user to download a phonepage at the outgoing call event.
STK Menu Managed Solution with Call Set Up and no STK EVENT Handling.
With this method the STK application would be launched from the ME menu when the user selects to set up a call this way. This means that there would be a specific set up call application on the SIM. This could be combined with access to the phone book on the SIM. Also, with this method the event for the outgoing call could be handled to give the possibility for the user to download a phonepage at the outgoing call event.
According to a variant of the present invention, the required software that needs to be added in the UE 100 may be conveyed on a SIM card. This allows implementation of the invention after it has been sold and/or without modifying the firmware of the UE 100. One apparent way of doing this is to utilize SIM Tool Kit (STK) functions using “proactive SIM” as described in the specification ETSI GSM 11.14. Some of the possible triggering events disclosed here may be mapped directly to a corresponding SIM event.
Having detected a triggering event as described above, the application residing on the SIM may invoke several actions. According to a first variant of the invention, the application sends an SMS to a data object server 130. In response to this, the data object server 130 sends a response to the UE 100 using an SMS message that is shown on the UE 100. According to a second variant of the invention, the data object server 130 sends a response using WAP Push technology as described in the WAP standard (www.wapforum.org, WAP-165, Push Architectural Overview).
According to another variant of the invention, the required software that needs to be added in the UE 100 may be conveyed in the “repository” as described in the WAP standard (www.wapforum.org, WAP-169, Wireless Telephony Application Specification (WTA)). This allows implementation of the invention after it has been sold and/or without modifying the firmware of the UE 100. Different triggering events are mapped to different “channels” (e.g., the triggering event “incoming call” is mapped to a channel connected to the event “wtaev-cc/ic”, other mappings include the WTA events “wtaev-cc/cl”, “wtaev-cc/oc” and “wtaev-cc/cc”.)
WAP/WTA constitutes a toolbox for creating telephony related services. This toolbox provides suitable support allowing a phonepage client to be implemented. The client resides in a socalled WTA repository in the UE. The data object server is in this case WTA compatible and would among other things enable downloading of the client over-the-air.
Another technology suitable for implementing a phonepage client in the UE is Java. Using, for example, JavaPhone functionality for automatic phonepage download over, e.g., WAP, HTML or SMS can be obtained. Moreover, functionality such as a context sensitive phonepage soft-key can also be obtained. The soft-key could, e.g., automatically appear after a call, in phone address book, and in a call log. When pressing the soft-key a phonepage associated with the telephone number on the display is automatically downloaded.
Network Implementation.
The data network, 120, typically includes one or several routers (not illustrated) and data bridges such that several nodes may be interconnected and communicate with each other. The data network used in connection with the present invention also includes a data object server, 130. Typically, a plurality of data object servers are included in a data network, although, for reasons of explanation and clarity, only one data object server, 130, is illustrated in
Alternatively, a dispatch can be described as:
A redirect can be described as
The request in step 310 may also include an indication of a UE display capability, in which case the data object may be adapted in the data object server to a specific rendering capability, step 340, of the receiving UE. The request in step 310 may also include an indication of an identity, e.g., a telephone number, of the requester, in which case a returned phonepage or phonepages can be from a selection of phonepages dependent of the identity of the requester. If the request was encrypted, or if requested for some other reason, the data object will be encrypted in step 350 before it is returned to the requesting UE, in step 360 and then the procedure is ended in the data object server in step 399.
Below follows an exemplary implementation of the procedure between the UE and the data object server.
PMT-PNS/PWS Signaling.
Redirection Scheme.
Dispatch Scheme.
The PNS relays HTTP requests to the appropriate PWS. The PWS on the other hand, may send HTTP messages directly to the PMT. This depends on the IP network architecture, interconnection, web service requested (e.g. http: or https:) and software configuration at PNS and PWS. Special security means must also be installed. Because the phonepage service is typically highly asymmetrical, the PWS will absorb most of the extra load involved with this scheme.
GSM Call Illustration.
N.B. The procedure is exemplary and can only be viewed as an illustration.
PNS Node.
The PNS is logically separated into two entities: a root and a local PNS. These may physically be implemented as separate nodes or integrated into one. The root PNS performs the following functions:
The root PNS could be implemented in a hierarchical structure enabling high performance service on a global basis.
The local PNS contains a local database of phonepage links and performs the following functions:
For capacity and coverage reasons local PNS's will exist in multiple instances. Moreover, to further improve security, availability and performance, a mobile operator may want to have a local PNS directly attached to his backbone.
An individual local PNS node may need to handle thousands of requests per second in a high availability fashion. For this reason a clustered solution with load sharing and redundancy may be employed.
PWS Nodes.
The PNS allows any number of PWSs (c.f. the DNS service that allows any number of homepage servers on the Internet). Thus, there are no limitations on how the load is distributed over actors and geography.
The PWS (phonepage web server) has the following main functions:
In the context of WAP, the adaptation of phonepages to the user's device can be handled according to the mechanisms defined in UAProf.
Typically, a PWS may be implemented using standard web servers (e.g., Apache) with tailor-made servlets that may parse the phonepage parameter lists and that generate phonepages that are suitable for the recipient's phonepage device.
Peer to Peer Phonepage.
According to a variant of the invention, translation of numbers and events to URLs can be made in the UE itself. Upon detection of a triggering event, the UE looks in a memory position (e.g., SIM card or address book) and retrieves or computes a URL corresponding to a particular other party and event. The URL is then conveyed to the other party via SMS. Upon reception of the URL by the other part, the data objects are automatically retrieved.
In another variant of the present invention, USSD or UUI (User-User Information) according to the GSM standard can be used to convey an URL instead of an SMS. In yet another variant, IP signaling between two UIs can be used for conveying the SMS instead of using SMS.
Event-Based Exchange of Information Between Communication Devices Conditioned on Personal Calendar Information
According to a variant of the present invention, the various systems and methods described herein may provide the ability to condition secondary information exchanged between two communication devices that are engaged in a primary communication, based on both a particular call event and calendar information that is personal to one or more of the users of the devices.
In some embodiments, the various systems and methods described herein may enable the user of communication device B 2410 to transmit phone pages that include data and information about the user of communication device B 2405. In some embodiments, such data and information may comprise data and information about the user's current availability to engage in a call or other type of communication activity, such as indication of an upcoming meeting or other event scheduled on the user's personal calendar.
As shown in
In some embodiments, call filtering module 2420 may maintain a listing of individuals or communication devices, for example, that are authorized to communicate with the user of communication device B 2410. Such a listing may be composed by the user of communication device B 2410 and may include the names of individuals, telephone numbers, or any other data or information that may be used by call filtering module 2420 to identify the user or communication device that seeks to communicate with the user of communication device B 2410. For example, the user of communication device B 2410 may designate that he is currently busy and wishes to receive calls either from no one or only from some specific person(s), such as, for example, his or her spouse, kids, or boss. In some embodiments, such designations may be made by the user of communication device B 2410 by interacting with call filtering module 2420 through communication device B 2410 or other appropriate terminal, such as, for example, a computer or other device, and may be stored and maintained as a personal calendar of the user of communication device B 2410. In some embodiments, interaction with the personal calendar may be aided with a graphical user interface (GUI) or other form of data input guide. In some embodiments, call filtering module 2420 may reside within communication device B 2410 or data object server 2415 or other remote server (not shown). In some embodiments, hosting the call filtering module 2420 within data object server 2415 or other remote server may ensure that its filtering functionality will be performed even when communication device B 2410 is powered off.
In some embodiments, when an incoming communication request from communication device A 2405 is received by call filtering module 2420, the identity of the user of communication device A 2405 is compared to a group of authorized persons derived, for example, from the personal calendar of the user of communication device B 2410. For instance, a particular type of calendar event (e.g., meeting with customer) may produce a particular authorized group of persons. If the user of communication device A 2405 is within the authorized group, then the communication is established. If, however, the user of or communication device A 2405 is not within the authorized group, then communication device B 2410 or call filtering module 2420 may transmit or request transmission (by data object server 2415, for example) to communication device A 2405 of a data object 2418 that informs the user of communication device A 2405 that the user of communication device B 2410 is unavailable to take the call or communicate in some other manner. In some embodiments, the data object may indicate that the user of communication device B 2410 is simply unavailable, that user of communication device B 2410 is likely to be available at some future time, that the user of communication device B 2410 may be contacted by other means, or other such message. In some embodiments, the data object may comprise an audio or video clip, a message and may include a link to the user of communication device B's web site, for example, or other forms or combinations.
In some embodiments, the user of communication device A 2405 may be reminded when communication device B 2410 is available again following a period of unavailability. For example, whenever communication device B 2410 was called by the user of communication device A 2405 and was blocked, communication device B 2410 (or the filtering application or module) may inform communication device A 2405 that the user of communication device B 2410 is now available again. In some embodiments, such notification may be accomplished through IM, SMS, MMS or otherwise.
In some embodiments, the incoming call from communication device A 2405 may be redirected to an answering machine or other recording device whenever B is unavailable. More generally, communication device B 2410 may, in some embodiments, deploy an application or module that is able to receive data objects (e.g. voice, video, data objects) from communication device A 2405 while communication device B 2410 is unavailable.
Moreover, in some embodiments, whenever an incoming call from the user of communication device A 2405 is blocked, the filtering application may inform communication device B 2410 (discretely or otherwise depending on the cause of blocking) that the call from A was rejected. The user of communication device B 2410 may then opt to take the communication session anyway or may decide to initiate communication with A at a later, more convenient time.
In some embodiments, when the identity of the user of communication device A 2405 is unknown, the various systems and methods described herein may limit the amount of PIM information that may be given (e.g. to avoid thieves learning that B is on vacation). For example, in some embodiments, users that pertain to the same group as the PIM relates to may be given transparent access to particular information, whereas unknown subscribers only will get a generic “I am unavailable” message.
As shown in
The following is an exemplary process flow of the types of events and data objects that can be processed by the various systems and methods described herein (assume an upcoming call between the users of communication devices A 2505 and D 2520):
In some embodiments, other process flows may be performed by the various systems and methods described herein in connection with the overall functionality of
In some embodiments, the various features and functionality described above may be performed by a downloadable module or application that may be installed on a communication device, such as a mobile communication device, for example.
The invention is not restricted to the above described embodiments, but may be varied within the scope of the following claims.
The present application claims priority under 35 U.S.C. Section 120 as a continuation-in-part of U.S. application Ser. No. 11/272,059, filed Nov. 14, 2005, Attorney Docket 57926.000011, entitled “System and Method for Exchange of Information in a Communication Network,” which was a continuation of Ser. No. 09/906,621, filed Jul. 18, 2001, Attorney Docket 57926.000008, entitled “System and Method for Exchange of Information in a Communication Network,” and which issued on Dec. 20, 2005 as U.S. Pat. No. 6,977,909, and which was a continuation-in-part of application Ser. No. 09/644,307, filed Aug. 23, 2000, Attorney Docket 57926.000002, entitled “Method and Apparatus for Exchange of Information in a Communication Network,” and which issued on Feb. 7, 2006 as U.S. Pat. No. 6,996,072, and which asserted priority under 35 U.S.C. Section 119 to U.S. Prov. App. Ser. No. 60/176,806, filed Jan. 19, 2000. Each of the aforementioned applications and patents is hereby incorporated by reference in its entirety. The present application also claims priority under 35 U.S.C. Section 120 as a continuation-in-part of U.S. application Ser. No. 11/140,742, filed Jun. 1, 2005, Attorney Docket 57926.000009, entitled “Exchange of Information in a Communication System,” which was a continuation of Ser. No. 09/686,990, filed Oct. 17, 2000, Attorney Docket 57926.000005, entitled “Exchange of Information in a Communication System,” and which issued on Jul. 26, 2005 as U.S. Pat. No. 6,922,721. Each of the aforementioned applications and patents is hereby incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 60176806 | Jan 2000 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 09906621 | Jul 2001 | US |
| Child | 11272059 | Nov 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11272059 | Nov 2005 | US |
| Child | 11711617 | Feb 2007 | US |
| Parent | 09644307 | Aug 2000 | US |
| Child | 09906621 | Jul 2001 | US |
