Apparatus, and associated method, for providing a client with out-of-band messages

[0002] The present invention relates generally to communications between a client and a content source in a communication system which includes a radio part, such as a radio part employing the WAP (Wireless Application Protocol) standard and more particularly, to an apparatus and an associated method for providing OOB (Out-of-Band) messages to the client.

[0003] Advancements in communication technologies have permitted the introduction and popularization of new types of communication systems. As a result of such advancements, e.g., significant increases in the rates of data transmission have been permitted and new types of communication services have also been made possible. Advancements in digital communication techniques are amongst the advancements in communication technologies which have permitted the introduction of new types of communication systems.

[0004] A radio communication system is exemplary of a type of communication system which has benefited from advancements in communication technologies and the use of digital communication techniques.

[0005] In a radio communication system, at least a portion of a communication path formed during communications therein includes a radio-link. Improvements in communication mobility are provided through use of a radio communication system as communication channels defined upon the radio-link in such a system are formed of radio channels and do not require wireline connections for their formation. The portion of the communication system which includes the radio-link is sometimes referred to as the radio part of the communication system.

[0006] Digital communication techniques have- been utilized in radio communication systems, thereby permitting improvement of communication capacities in such systems as well as permitting the implementation of new communication services. For instance, packet radio services are possible through the use of digital communication techniques. Such packet radio services have been proposed for several radio communication systems to permit the communication of packet data. The communication of packet data, in general, involves the formatting of groups of digital bits into packets to form packets of data. The packets of data are communicated, either individually, or in groups, at discrete intervals. Once received, the packets of data are concatenated together to recreate the informational content of the digital bit of which the packets are formed.

[0007] Examples of packet radio services which have been proposed, or already implemented, include multi-media services, messaging services, distribution services, dispatching services, and retrieval services. Retrieval of content provided pursuant to the World Wide Web (www) of the Internet is exemplary of a retrieval service.

[0008] Revenues which support the content providers of content retrievable pursuant to the www are typically generated through subscription payment, service charges, click fees, and advertising. In a subscription payment, a user pays a cyclic, for example, monthly, quarterly, yearly, etc., fee in order to access the services and contents that are retrieved. Service charge is referred to charges paid by a user to receive performance of a service. Click fees refer to charges accruing to a user based upon simple metrics, such as links followed, duration of contact, or other measurable use of a content source.

[0009] And, advertising refers to third party payments to a content provider for the display of promotional messages, typically including the links which permit a user to follow the links to obtain additional content regarding the advertised material.

[0010] Generally, existing retrieval services over the www are effectuated by a user of a conventional computer, such as a personal computer. Content is displayed in the form of screens displayable upon a conventional computer screen, or the like. Both desired informational content as well as advertising regularly forms a single screen. Therefore, when a user uses the desired content, the advertising message is also displayed.

[0011] However, in a radio communication system, the client, that is, the mobile station or other device utilized by a user, shall not necessarily, and perhaps shall likely not, have a display element of dimensions permitting the display of a screen containing both the informational content and the advertising. Network systems employing the WAP (Wireless Application Protocol) standard utilizing OOB (Out-of-Band) messaging have been proposed. When using OOB messaging, advertising is displayed on the display element of the mobile station, sometimes hereinafter referred to as a “client,” and thereafter display the informational content on the display element of the mobile station.

[0012] Push messages, that is, a synchronous notifications, as well as alerts, and notification are also exemplary OOB messages. While the aforementioned WAP standard is permitting of the transport of OOB messages, such as push messages, the existing WAP standard fails to define a push mechanism.

[0013] Difficulties are, however, associated with retrieval services, in which content is to be provided to a portable mobile station. That is to say, in a conventional system, a content provider provides both the content as well as the advertising. Special hardware and software for the computer server from which the content and advertising originates is required. The need for such special hardware and software at the computer server used by the content provider increases its complexity.

[0014] It would be advantageous, therefore, if a manner could be devised which could better provide OOB messages to the client pursuant to retrieval services.

[0015] It would be further advantageous if a manner could be devised which could better provide a synchronous communications, such as push messages, alerts, and notifications.

[0016] It is in light of this background information related to the communication of OOB messages that the significant improvements of the present invention have evolved.

[0017] The present invention, accordingly, advantageously provides an apparatus and an associated method for providing OOB (Out-of-Band) messages to a client in a communication system which includes a radio part.

[0018] The OOB messages are provided to the client by a radio part gateway which forms at least part of the communication path upon which communications with the client are effectuated. In a communication system which employs the WAP (Wireless Application Protocol) standard, the gateway may be a WAP gateway.

[0019] In one aspect of the present invention, a synchronous, OOB messages are provided to the client. Alerts, notifications, and push messages are exemplary of a synchronous messages. PIM notifications, paging services, and location-based notifications all are exemplary of services possible pursuant to operation of an embodiment of the present invention.

[0020] In another aspect of the present invention, OOB messages are provided by the gateway to the client responsive to requests made by the client for content from a content provider. When an initial request is made for initial content, the request is communicated by way of the gateway to the content source. When the content is returned by the content source, the content is provided to a filter which at least selectably parses the content to detect links in the content selectable by a user, when displayed at the client, or additional content. The links identify URLs of locations at which the additional content is sourced. The filter flags URLs within the content so that the gateway is aware that OOB messages can be provided when selection is made at the client to request such additional content. The original, initial content is then provided to the client together with URL modifications to permit flagging of possible OOB message URLs. When selection is made at the client to request such additional content, the request is provided to a gateway.

[0021] When detected at the gateway, an OOB message, such as an advertising display, is returned to the client and, the gateway generates a substitute request which is forwarded to the content source at which the additional content is sourced. The OOB message is thereby displayed at the client during the pendency of the substitute request for the additional content generated by the gateway.

[0022] In one embodiment, the OOB message is displayed at the client for at least a minimum, selected time period, subsequent to which the client generates a new request for the additional content, which, if necessary, is stored at the gateway subsequent to retrieval from the content source of the additional content. Filtering of the additional content further permits additional OOB messages to be provided to the client in analogous manners during pendency of subsequent requests. In an exemplary implementation, the communication system can include a radio part which is operable pursuant to the WAP (Wireless Application Protocol) standard. The radio part interfaces with a WAP gateway through which all communications with the client are routed. However, a radio part is not necessary for routing client communications. Other communication paths can include for example POTS and PSTN and other known mediums and protocols.

[0023] An embodiment of the present invention forms additional apparatus for a gateway through which an owner, or operator, of the gateway is provided with the capability to send OOB messages to a client which utilizes the gateway for communications. OOB messages are displayed, e.g., during an interval between a request originating from the client and a reply returning from the content source, typically an origin server. The OOB messages can contain any type of content and can be used for any application in which OOB messaging is appropriate. An OOB message forming an advertising display is an exemplary message which is communicated to the client during operation of an embodiment of the present invention. In alternate implementations, asynchronous messages, such as push messages, are provided to the client.

[0024] In an embodiment of the present invention, advantage is made of the communication path which extends between the client and content source of the communication system which may include a WAP, or other wireless-protocol, part. All communications with the client in such a communication system typically must pass through the gateway. Wireless communication system implementation is predicated on the traditional, narrow bandwidth of wireless connections, in contrast to conventional wireline communication paths. Because of the narrow band width, the rate of data transfer on a wireless-link is relatively slow. The WAP standard requires that all content communicated upon the wireless-link be encoded prior to its transmission to the client. And, when a request is originated at a client and communicated upon a wireless-link, request headers of the request must be decoded prior to forwarding of the request by the gateway to the content source. In other words, the WAP, or other gateway, forms a central point of contact between client and content source during operation of the system. Advantage is taken of the fact that the gateway is the central point of contact during operation of the various embodiments of the present invention.

[0025] In these and other aspects, therefore, an apparatus, and an associated method, is provided for a gateway of a communication system in which data is communicated between a client and at least a first content source upon a communication path. The gateway provides an Out-of-Band message to the client. An Out-of-Band message source is coupled to receive at least one Out-of-Band message, the at least one Out-of-Band message selectably to be communicated to the client. A selector is coupled to the Out-of-Band message source. The selector selects whether to communicate to the client a selected Out-of-Band message to which the Out-of-Band message source is coupled to receive.

[0026] A more complete description of the present invention and the scope thereof can be obtained from the accompanying drawings which are briefly summarized below, the following detailed description of the presently-preferred embodiments of the invention, and the appended claims.

[0027] FIG. 1 illustrates a functional block diagram of a communication system in which an embodiment of the present invention is operable.

[0028] FIG. 2 illustrates a sequence diagram listing the sequence of signal generation during operation of the communication system shown in FIG. 1.

[0029] FIG. 3 illustrates a sequence diagram, similar to that shown in FIG. 2, also listing the sequence of signal generation during operation of the communication system shown in FIG. 1.

[0030] FIG. 4 illustrates a sequence diagram, similar to those shown in FIGS. 2-3, also listing the sequence of signal generation during operation of the communication system shown in FIG. 1.

[0031] Referring first to FIG. 1, a communication system, shown generally at 10, provides for the communication of packet data between a client 12 and a selected origin server 14. The communication system includes a wireline portion, including a packet data network 16 to which the origin servers 14 are connected. In the embodiment shown in FIG. 1, the communication system includes a radio part including a radio-link 18 by which to effectuate radio communications with the client. A WAP (Wireless Application Protocol) gateway 22 also forms a portion of the communication system. All communications between the client 12 and an origin server 14 pass through the gateway 22. While, in the exemplary implementation, the radio part of the radio communication system is constructed to be operable pursuant to a WAP standard, in other implementations the communication system is operable pursuant to other standards.

[0032] While the embodiment discussed uses a wireless link to a mobile station, neither a wireless link nor a mobile station are necessary to realize the advantages of the present disclosure. For example, other clients can be substituted for the mobile station described in FIG. 1. Such clients can include, for example, a computer. For another example, other communication links can be used in place of the radio part described. Such communication channels can include, for example, POTS PSTN, ISDN, ADSL, XDSL, PLMN, WLAN, or other appropriate communication schemes can be used.

[0033] In addition to apparatus required for conventional operation of the WAP gateway to perform encoding and decoding operations of content to be provided to the client 12 and signals received by the client, the gateway is operable pursuant to an embodiment of the present invention to provide OOB (Out-of-Band) messages to the client. The apparatus, shown at 26, includes a request handler 28, a transaction cache 30, and an HTTP client 32. Functions performed by the handler, transaction cache, and HTTP client are shown in block form in the Figure. Such functions are exemplary, and operation of an embodiment of the present invention can alternately be implemented in other manners. And, while in the exemplary implementation, the WAP gateway 22 and apparatus 26 thereof are shown to be physically separated from the origin servers 14, such devices can also be co-located. However, the functionality of such separate devices remain distinguishable.

[0034] The request handler 28 is here shown to include a selector 34. The selector is here shown to be coupled to a radio transceiver 36 capable of transceiving communication signals with the client 12 on the radio-link 18. The radio-link 18 is shown to include a forward link 38 and a reverse link 42. The selector is further coupled to an OOB message cache 44. The selector is operable to select whether to provide an OOB message stored at the cache 44 to the client 12. The OOB messages are permanently stored at the message cache, or are provided thereto from an external location, here indicated by way of the line 46.

[0035] When selection is made by the selector 34 to provide the client with an OOB message, the OOB message is communicated to the client on the forward link 38 by the radio transceiver 36 which, for instance, is formed of a radio base station. The link from the radio transceiver to the gateway transports digital data. The digital data can be either streaming or packetized with protocols such as TCP/IP, SMS, PCS, WAP, or other suitable protocol. The OOB message selected to be communicated to the client may, for instance, be an asynchronous message, such as a push message, and alert, or other notification. Once provided to the client, the OOB message is displayed upon a display element 48 of the client. In one implementation, the asynchronous OOB message remains displayed at the display element of the client until a user actuates an appropriate user actuation key 52 of the client to remove the OOB message from the display.

[0036] In a further embodiment of the present invention, a user of the client is able to request content stored at an origin server 14 to be retrieved therefrom and displayed at the display element 48 of the client. When the content is requested, a request is generated on the reverse link channel 42 and detected at the gateway. Retrieval services pursuant to the World Wide Web/Intranet are exemplary of this operation when the PDN 16 is representative of the Internet backbone. When a request is an initial request for content, the request is forwarded to the appropriate origin server. The origin server and the contents therein are identified, for instance, by a URL. Responsive to the request, the content is retrieved from the origin server and returned to the HTTP client 28 of the gateway 22.

[0037] The content is provided to a filter 56 which is selectably operable to pass the retrieved content to identify hyperlinks contained in the retrieved content which form links to other content. When the hyperlinks are detected, the filter flags the URLs within the content. Thereby the gateway is able to provide OOB messages when the client subsequently requests the additional content identified by the hyperlinks. The filter generates an output which is formed of the original content, together with URL modifications needed to flag possible OOB message URLs. Then, the content is forwarded to the client.

[0038] When the user of the client requests additional content, an additional request is generated on the reverse link 42 for such additional content. When the additional request is detected at the gateway, the URL identified in the additional request contains a flagged URL. The selector of the gateway is able to select an OOB message from the message cache 44 to be returned to the client to be displayed at the display element 48. And a substitute request is generated by the substitute request generator to be communicated to the appropriate origin server to retrieve the additional content. During pendency of the retrieval of the actual content, the OOB message is displayed at the display element of the client. If, conversely, a selection is made not to send any OOB messages to the client, the request process is started over again, such process described previously.

[0039] When the substitute request is generated, a new request ID unique to this request is created and the OOB message is immediately provided to the client as a reply to the additional request. The OOB message includes an anchor or action that requests a URL pointing to an entry in the transaction cache of the gateway which is identified by the unique request identification.

[0040] As the OOB message is provided on the forward link 38 to the client, the substitute request is forwarded to the appropriate origin server 14 to retrieve the contents stored thereat. When the additional content is returned, the additional content.is filtered by the filter 56 of the HTTP client to flag additional, relevant URLs for subsequent OOB messaging. The output generated by the filter is stored, if necessary, at a content memory cache 58 of the transaction cache.

[0041] In the exemplary implementation, the OOB message displayed at the display element 48 during performance of such retrieval service is displayed thereat for at least a selected time period. When such time period times out, a request is automatically generated by the client for the actual content. The request is communicated over the reverse link 42 of the radio-link 18. And, responsive thereto, the content stored at the memory cache is retrieved and provided to the client. Thereby, the initial content and the additional content is displayed at the display element, interspersed with an OOB message. Subsequent fetches repeat the same process.

[0042] The disclosed innovations may be implemented without modifying the URL with a flag. By a lookup table method within the gateway, the same results may be achieved without modifying the URLs received from the content source other similar methods can be used.

[0043] A manner is thereby provided by which to provide OOB messages to the client whenever the client connects to the Internet. Applications at the respective origin servers need not be aware of the operation of the apparatus 26 of the gateway for either the application or the OOB mechanism to function. A number of services are thereby able to be provided seamlessly and independently of the provider of the content stored at the origin server or the origin server.

[0044] For instance, advertising and promotional messages form the OOB messages stored at the message cache 44. Such advertising and promotional messages are independent decks that contain any legal WAP content, such as WML, WML script, etc. Complex advertising messages, such as images, animations, and other multi-media, can thereby be transferred to the client as an OOB message.

[0045] As the content of the OOB message is controlled by the owner or operator of the WAP gateway 22, assurances can be made as to how often, and with what duration, the OOB message shall be displayed at the display element 48 of the client. By forming the advertising messages to be separate WML decks, problems associated with bloating of the content decks is avoided. Such is particularly important in WAP where devices typically have limits on their permitted deck sizes. Also, a developer and content provider need not exert effort on incorporating revenue-generating messages into their application and content as such efforts are performed by the operator of the WAP gateway.

[0046] A number of different strategies for providing advertising and promotional messages are permitted. For instance, autonomous control is permitted. In autonomous control, the WAP gateway operator controls, signs, and regulates autonomously all advertising and promotional messages. That is to say, the WAP gateway operator decides what advertisers are permitted, and how frequently messages are permitted to be shown. Revenues generated by such advertising accrues to the WAP gateway operator. In this scheme, the WAP gateway operator need not differentiate the target origin server of the client in selecting which message to promote. The WAP gateway operator is, however, permitted to make such selections. For instance, sponsors of some advertising messages may not want their advertising message associated with certain content.

[0047] Another strategy is a content selective strategy. Here, the WAP gateway operator is able to target individual WAP service in content providers to offer such providers the advertising and promotional messages for an appropriate fee. The system would then only display advertising and messages specific to a particular origin server pursuant to agreement between the WAP gateway operator and the operator of the appropriate origin server.

[0048] Also, a user profile strategy is possible. The WAP gateway owner is able to create user profiles of users of the client in order to tailor messages to a specific target group. Such strategy would permit the WAP gateway operator to provide sponsors the additional guarantee of reaching a desired target market. Such a strategy would also have the benefit of not inconveniencing users of the clients with irrelevant messages. Combinations of the strategies are also possible.

[0049] Through operation of an embodiment of the present invention, a push mechanism is provided for communicating asynchronous messages to the client. In the existing WAP standard, a push mechanism is not yet implemented. Although the push mechanism envisioned for the WAP standard is a true asynchronous push because there is no push mechanism set forth in the WAP standard yet, the functionality provided by the apparatus 26 encompasses a significant number of applications utilizing the push mechanism.

[0050] Analogously, alerts and notifications, also storable at the message cache 44 can be provided to the client. Alerts and notifications include, for instance, PIM notifications in which appointment messages can be sent to the client during a time leading up to a scheduled meeting, thereby providing a constant reminder of an upcoming event. Also, pages and messages from other users can also be transmitted to the client utilizing an embodiment of the present invention. And location-based notifications to provide location-based information to a user of the client, such as road conditions, can also be provided to the client. In addition, OOB messages forming news bulletins, humorous, or motivational messages can also be provided to the client during pendency of a request for content.

[0051] FIG. 2 illustrates a sequence diagram, shown generally at 82, in which signaling between the client 12, WAP gateway 22, and origin server is shown. Here, the WAP gateway is shown to include the request handler 28, the transaction cache 30, and HTTP client 32. The sequence diagram 82 illustrates the generation of a generic request by the client without the return by the WAP gateway of an OOB message.

[0052] First, and as indicated by the segment 84, a WSP request is generated by the client and delivered to the request handler 28. Responsive thereto, a load resource (URL) call and request ID is caused to be generated, indicated by the segment 86. Thereafter, a request resource signal including a URL is generated, indicated by the segment 88. Such request is provided to the HTTP client 32 which, in turn generates an HTTP request indicated by the segment 92 and provided to the origin server 14. The content is returned as part of an HTTP reply, indicated by the line segment 94.

[0053] The HTTP reply is passed by the client 32 to the transaction cache 30 indicated by the segment 96 and the transaction cache forwards the HTTP reply to the request handler 28 here indicated by the segment 98. Filtering is selectably performed at the filter 56, and the content, here in the form of a WSP reply, indicated by the segment 102 is provided to the client.

[0054] FIG. 3 illustrates a sequence diagram, shown generally at 104, here representing the sequencing of signals during operation of an embodiment of the present invention in which an OOB message is provided to the client. The OOB message is provided to the client responsive to an additional request by the client for additional content.

[0055] First, a WSP request, indicated by the segment 106, including a flagged URL is generated by the client and provided to the request handler 28. The request handler causes a WSP reply formed of the OOB message to be provided to the client, indicated by the segment 108. And, the request handler causes generation of a load resource (URL): request ID signal indicated by the segment 112. Such signal is provided to the transaction cache 30 which generates a request resource (URL) signal, indicated by the segment 114 to the HTTP client 32. The HTTP client generates, in response thereto, an HTTP request here indicated by the segment 116 which is provided to the origin server 14. The origin server generates an HTTP reply, indicated by the segment 118 to the HTTP client which passes the reply, indicated by the segment 122, to the transaction cache 30 which, in turn, parses the reply, indicated by the segment 124, to the requesting handler.

[0056] During the request and reply for the content from the origin server, the client generates a WSP request for actual content, indicated by the line 126 which is provided to the request handler. Responsive thereto, the request handler generates a fetch resource (request ID) signal indicated by the segment 128 which is provided to the transaction cache. In the sequencing shown in the Figure, display of the OOB message at the client is completed prior to the availability of the requested content. As shown, the signals represented by the segments 126 and 128 are generated prior to return of the requested content, indicated by the segments 118 and 122. When the content is provided to the request handler 28, the content is selectably parsed by the filter 56. Thereafter, the actual content is provided to the client as a WSP reply indicated by the segment 132.

[0057] FIG. 4 illustrates a sequence diagram, shown generally at 134, here also representing the sequencing of signals during operation of an embodiment of the present invention in which an OOB message is provided to the client. In contrast to the sequence diagram shown in FIG. 3, the sequence diagram represents a situation in which delivery of the requested content is provided to the WAP gateway prior to completion of an OOB message at the client. Again, however, the OOB message is provided to the client responsive to an additional request by the client for additional content.

[0058] First, and as indicated by the segment 136, a WSP request, including a flagged URL, is generated by the client and provided to the request handler 28. The request handler returns a WSP reply formed of an OOB message to the client indicated by the segment 138. And, the request handler causes generation of a load resource (URL): request ID signal, indicated by the segment 142. Such signal is provided to the transaction cache 30 which generates a request resource (URL) signal indicated by the segment 144, to the HTTP client 32. The HTTP client generates, in response thereto, an HTTP request, here indicated by the segment 146, which is provided to the origin server 14. The origin server generates an HTTP reply, indicated by the segment 148, to the HTTP client. The reply includes the content requested by the client. The HTTP client 32, in turn, parses the reply, indicated by the segment 152, to the transaction cache, here to be stored at the content memory cache thereof.

[0059] When the display period of the OOB message is completed, the client generates a WSP request, indicated by the segment 156, for delivery thereto of the actual content. The request is provided to the request handler 28 which, in turn, generates a fetch resource (request ID) signal indicated by the segment 158. The content, already stored at the content memory cache is retrieved therefrom, and returned, in the form of an HTTP reply, indicated by the segment 162, to the request handler. The content is selectably parsed by the filter 56, and the actual content is thereafter provided to the client 12 in the form of a WSP reply, indicated by the segment 164.

[0060] Thereby, through operation of various embodiments of the present invention, an OOB message is provided to a mobile client. The OOB message can take almost any form, such as an alert, notification, a push message, an advertising message, or the like. A WAP compliant manner is provided by which to display such messages without the need of special hardware or software at either the client or the origin server. Seamless operation with the use of existing client devices and content providers-origin servers is possible. Also, the size required of the existing content is not increased. Therefore, operation of an embodiment of the present invention does not cause working content to fail when loaded by the client. Content providers and service developers are able to create their content and services without being required to be aware of the operation of an embodiment of the present invention.

[0061] The previous descriptions are of preferred examples for implementing the invention, and the scope of the invention should not necessarily be limited by this description. For example, the disclosed embodiments describe flagging the URLs prior to sending them to a mobile station. However, the gateway can be used to track URLs sent to a mobile station without the need to modify URLs.