JP2007226783A - Apparatus and related method for facilitating delivery and processing of push content - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an apparatus for a communication device operable complying with a push content communication scheme. <P>SOLUTION: The apparatus for the communication device operable complying with the push content communication scheme comprises: a notification processing attribute identifier configured to identify at least a first selected notification processing attribute; and a push content operator adapted to receive instruction of the first selected notification processing attribute and to receive push content, the push content operator configured to operate upon the push content in a manner corresponding at least to an appropriate notification attribute of the first selected notification processing attribute. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention generally relates to a method for facilitating delivery and processing of push content. More specifically, the present invention relates to an apparatus that operates on content and related methods, so that the amount of expired content communicated is reduced and the application to which the push content is associated is active. Processing of content that does not require is provided.

  When implemented in a mobile communication system or other wireless communication system, the content is efficiently distributed and processed. Both the distribution and the processing are performed in a timely manner, and the amount of radio resources required for content communication is smaller.

  Technological advances in communication technology have enabled the development, deployment and dissemination of many new types of communication systems. For example, significant growth has been shown in the field of mobile communications. In addition, mobile communication systems utilizing advancements in communication technology have been deployed and used by many people for both telephone and data communications. Email messages communicated in accordance with both a storage management scheme and an instant messaging scheme have historically been provided from and to mobile communication stations by communication of alphanumeric text messages. . As the capabilities of mobile communication systems increase and continue to improve, mobile communication systems are increasingly capable of communicating larger amounts of content.

  Push message services, including the instant message scheme described above, offer unique communication benefits. The advantage is that even if the content being communicated is delivered to a communication device, the device does not require any specific action to retrieve that content. When content is distributed more timely, the utility of a communication service through which push content is communicated is improved. In contrast, request response type data communication schemes typically require a user to generate a request, and a single response is made to the request.

  Various proposals are currently under consideration to standardize various aspects of push content communication. For example, Open Mobile Alliance (OMA) Limited has published a document titled “Dynamic Content Delivery Requirements” regarding requests and protocols related to communication content in mobile communication systems. The content delivery scheme introduced in that document is intended to be usable in various network technology categories and in various aspects, enhancing applications and their delivery, and providing for asynchronous push content Is intended to be able to be done.

  In one scheme, a content push is generally initiated by a data server where the content resides or a data server to which the content is routed. The content push trigger is triggered asynchronously, for example, by a content provider, by a device client, or by a third party. A push event is typically the result of a content subscription that receives specific content initiated by a content provider, device client, or third party. In addition, push events are also sometimes performed as a result of data broadcasts to selected groups of client devices.

  Due to the limited bandwidth available for communication over the wireless interface in mobile communication systems, efforts are made to efficiently utilize this available bandwidth. Efforts are also being made to perform timely delivery and display of push content in order to maximize the end user experience.

  Any additional method that can further reduce the communication bandwidth required to communicate push content and process and display push content in a more timely manner is advantageous. When viewing a display based on push content or a display using push content, the end user experience is improved if update information is displayed in a timely manner without displaying expiration information.

  In light of this background information related to push content communication, significant improvements of the present invention are developed.

  The present invention thus advantageously provides an apparatus and associated method that facilitates the distribution and processing of push content.

  The operations of the embodiments of the present invention provide a method for operating on push content, resulting in a reduction in the amount of expired data communicated and without requiring an application with which the push content is associated. Processing of the data is provided.

  When implemented in wireless mobile or other communication systems, push content is efficiently communicated and processed, eg, displayed by viewing or playback, or displayed by end users of mobile stations or other communication stations It becomes possible. Also, the bandwidth required for the communication can be reduced relative to conventional mechanisms and procedures, while push data is communicated in a timely manner.

  In one aspect of the invention, special attributes are introduced. This special attribute enhances push content delivery and processing.

  Replacement attributes have special attributes when operating on notifications (ie, content data), and expiration information that forms part of this notification can be sent, processed, and viewed as needed. To be prevented. When a notification is operated with this attribute, only the latest update data for each contract is queued and delivered to the application that uses the notification.

  The background processing attribute is another special attribute. The background processing attribute, when operating on a notification, allows the notification to be processed even if the target application is not running, i.e. not active. A dedicated device agent updates the persistent store. This is performed in background mode rather than active mode, so operations can be performed even when the application is not in an active state.

  In another aspect of the invention, special attribute operations are performed on the notification at a network device (eg, an application server or a proxy server) before the notification is communicated to the mobile communication station via the wireless interface. . When embodied in a network device, operations are performed on the notification before communicating the notification to the mobile communication station over the wireless interface, eg, for replacement attributes, before communicating on the wireless interface. It becomes possible to remove the expiration notification. Notifications can be, for example, time stamped or ordered in time, thereby identifying which notifications are timely and which notifications are out of date. By removing expiration notifications prior to communication over the wireless interface, wireless bandwidth consumption is reduced.

  According to another aspect of the invention, special attribute operations are performed at the mobile communication station. When a replacement operation is performed on a notification, once provided to the mobile communication station, the replacement operation removes the expiration notification and the notification is not displayed and seen by the communication station end user. Do not. Only timely notifications can be seen. Again, the notifications are ordered in time or time stamped to identify at least the relative timeliness of the notifications. Then, by removing the expiration notification at the mobile station, the limited storage space of the mobile station queue is not used beyond its capacity.

  When the background processing attribute is operated at the mobile communication station, the operation is performed for notifications queued at the mobile communication station. By performing the background processing operation, the application associated with the notification need not be active. Thus, delay is avoided. If it is necessary to be active, processing operations need to be delayed until the associated application becomes active.

  The identification and operation of special attributes on notifications communicated within the push content communication scheme enhances the end-user experience associated with communication services associated with push content communication.

  Thus, in these and other aspects, an apparatus and related methods are provided for communication devices operable in accordance with a push content communication scheme. The notification processing attribute identifier is configured to identify at least a first selected notification processing attribute. The push content operator receives an indication of the first selected notification attribute and receives the push content. The push content operator is configured to operate on the push content in a manner corresponding to the appropriate notification attribute of the at least first selected notification processing attribute.

The present invention further provides the following means.
(Item 1)
An apparatus for a communication device operable in accordance with a push content communication scheme, the apparatus comprising:
A notification processing attribute identifier configured to identify at least a first selected notification processing attribute;
A push content operator adapted to receive an indication of the first selected notification processing attribute and receive push content, the push content operator comprising the at least first selected notification processing attribute A push content operator configured to operate on the push content in a manner corresponding to the appropriate notification attribute.
(Item 2)
The first selected notification processing attribute identified by the notification processing attribute identifier comprises an expiration replacement attribute;
The apparatus according to item 1, wherein the push content operator operates on the push content and replaces an expired portion of the push content according to a replacement rule set.
(Item 3)
The apparatus according to item 2, wherein the push content operator arranges the push content in time order, and the expired portion of the push content is replaced according to the time order of the push content.
(Item 4)
The push content operator further identifies each portion of the push content using a unique message identifier,
The apparatus of item 2, wherein the expired portion of the push content is replaced according to a value of the unique message identifier associated with the portion of the push content.
(Item 5)
The first selected notification processing attribute identified by the identification processing attribute identifier comprises a background processing attribute,
The apparatus of item 1, wherein the push content operator operates on the push content in a background mode.
(Item 6)
The communication device comprises a content client and updatable application internal data,
The apparatus of item 3, wherein the push content operator operates on the push content while the content client is closed.
(Item 7)
The communication device further comprises an application message store configured to store content data messages,
The apparatus of item 6, wherein the push content operator operates on the push content message stored in the application message store.
(Item 8)
8. The apparatus of item 7, wherein push content delivered to the communication device is queued in the application message store when the content client is closed.
(Item 9)
The apparatus according to item 1, wherein the communication device includes a mobile station having a content client, and the notification processing identifier includes content metadata stored in the mobile station.
(Item 10)
The apparatus of item 9, wherein the push content operator is implemented in the mobile station and configured to access the metadata stored in the mobile station and receive the push content.
(Item 11)
The communication device includes a network server having available push content,
The apparatus according to item 1, wherein the notification process identifier includes content metadata stored in the network server.
(Item 12)
Item 12. The device of item 11, wherein the push content operator is implemented in the network server and configured to access the metadata stored in the network server and receive the push content.
(Item 13)
The communication device includes a proxy server to which the push content is routed,
The apparatus according to item 1, wherein the notification process identifier includes content metadata usable in the proxy server.
(Item 14)
14. The apparatus of item 13, wherein the push content operator is implemented in the proxy server and configured to access the metadata stored in the proxy server and receive the push content.
(Item 15)
A method of utilizing push content in a communication device operable in accordance with a push content communication scheme, the method comprising:
An operation identifying at least a first selected notification processing attribute;
An operation that operates on the push content in a manner corresponding to an appropriate notification attribute of the at least the first selected notification processing attribute.
(Item 16)
16. The method of item 15, wherein the first selected notification processing attribute identified during the identifying operation comprises an expire replacement attribute.
(Item 17)
The method of item 16, wherein the operating operation comprises replacing an expired portion of the push content.
(Item 18)
16. The method of item 15, wherein the first selected notification processing attribute identified during the identifying operation comprises a background processing attribute.
(Item 19)
19. The method of item 18, wherein the operating operation comprises operating on the push content in a background mode.
(Item 20)
The communication device includes a mobile station,
The method further includes an operation of pushing the push content to the mobile station,
16. The method of item 15, wherein the identifying operation and the operating operation are performed at the mobile station.
(Item 21)
A device for a mobile station operable to receive push content communicated to itself, the device comprising:
A notification processing attribute identifier configured to identify at least a first selected notification processing attribute;
A push content operator adapted to receive the indication of the first selected notification attribute and the push content received at the mobile station, wherein the push content operator is the at least the first A push content operator configured to operate on the push content in a manner corresponding to the appropriate notification attribute of the selected notification processing attribute.
(Item 22)
The mobile station further comprises a user display,
Item 22. The device of item 21, wherein the push content operator is configured to operate on the push content prior to display by the user display.
(Item 23)
The first selected notification processing attribute identified by the notification processing attribute identifier comprises an expiration replacement attribute;
Item 22. The apparatus of item 21, wherein the push content operator operates on the push content and replaces an expired portion of the push content according to a replacement rule set.
(Item 24)
24. The apparatus of item 23, wherein the push content operator arranges the push content in time order, and the expired portion of the push content is replaced according to the time order of the push content.
(Item 25)
The push content operator further identifies each portion of the push content using a unique message identifier,
24. The apparatus of item 23, wherein the expired portion of the push content is replaced according to a value of the unique message identifier associated with the portion of the push content.
(Item 26)
The first selected notification processing attribute identified by the identification processing attribute identifier comprises a background processing attribute,
Item 22. The device of item 21, wherein the push content operator operates on the push content in a background mode.
(Item 27)
The mobile station includes a content client and updatable application internal data,
The apparatus of item 24, wherein the push content operator operates on the push content while the content client is closed.
(Item 28)
The mobile station further comprises an application message store configured to store content data messages,
27. The apparatus of item 26, wherein the push content operator operates on the push content stored in the application message store.
(Item 29)
28. Apparatus according to item 27, wherein the push content delivered to the mobile station is queued in the application message store when the content client is closed.
(Item 30)
An apparatus for a network device operable according to a push content communication scheme in which push content is pushed asynchronously, the apparatus comprising:
A notification processing attribute identifier configured to identify at least a first selected notification processing attribute;
A push content operator adapted to receive an indication of the first selected notification attribute and receive push content that is pushed asynchronously, the push content operator comprising the at least first selection A push content operator configured to operate on the push content in a manner corresponding to an appropriate notification attribute of the notified notification processing attribute.
(Item 31)
The first selected notification processing attribute identified by the notification processing attribute identifier comprises an expiration replacement attribute;
The apparatus of item 30, wherein the push content operator operates on the push content and replaces expired portions of the push content according to a replacement rule set.
(Item 32)
32. The apparatus of item 31, wherein the push content operator arranges the push content in time order, and the expired portion of the push content is replaced according to the time order of the push content.
(Item 33)
The push content operator further identifies each portion of the push content using a unique message identifier,
The apparatus of item 32, wherein the expired portion of the push content is replaced according to a value of the unique message identifier associated with the portion of the push content.
(Item 34)
The apparatus of item 30, further comprising a push handler configured to push the push content once actuated by the push content operator.

(Summary)
An apparatus and associated method for facilitating distribution and processing of asynchronous push content communicated to a mobile station of a wireless communication system. Expired replacement attributes and background processing attributes are defined and operated on the content being communicated. Using an expiry replacement attribute avoids display of anything other than recent content, and using a background processing attribute should be performed on the push content even when the application with which the push content is associated is not active Operation becomes possible.

  Thus, referring first to FIG. 1, a communication system, generally designated 10, provides wireless communication between the network portion 12 and the mobile station 14 via the wireless interface 16. In this exemplary implementation, content is communicated both to the mobile station by the network portion and to the network portion by the mobile station. For the purpose of describing exemplary operations of embodiments of the present invention, communication of push content generated or provided at a network portion to a mobile station 14 is described. Such a description is by way of example. Communication of content from the mobile station to the network portion is performed in the same way.

  The network portion is shown here including an access network (AN) 18 and a data network 22 suitably connected therewith with communication connectivity. The data network 22 here forms a packet data network such as the Internet and a communication device such as an application server 24. The communication server 24 contains or generates content and is sometimes referred to herein as a content provider.

  The network portion also includes a proxy server 26. This proxy server 26 is here connected to the access network 18 and to the data network 22. Content sourced from the application server is routed to the proxy server by the data network in accordance with conventional operations. The proxy server then performs a wireless push directly to the mobile station via the access network and wireless interface. This is for subsequent transfer over the mobile station by the wireless interface 16.

  Content data (referred to herein as notification) is pushed to the mobile station and delivers the notification to the mobile station. This does not require a separate request to be made by the mobile station. The mobile station includes a transmit and receive network, represented here by a transmit portion 32 and a receive portion 34. The mobile station also includes a content client 36 (representing an application, application environment, or generically a push agent that consumes content pushed to the mobile station). And the content data 38 associated with the content client and metadata is further shown.

  A content provider embodied in or forming the application server 24 provides dynamic content (eg, pushable XML web service) and is either by an end user of the mobile station 14 or on its behalf. Support content contracts. When the content is to be communicated to the mobile station, the content provider sends the content to the proxy server 26. The proxy server 26 then distributes the content using a notification mechanism.

  Proxy server 26 interacts with an external content provider, such as a content provider formed from application server 24, and also interacts with a mobile station, such as mobile station 14, and an application that resides at that mobile station. In operation, the proxy server further mediates the contract and notification workflow between the content provider and the mobile station, and miscellaneous wireless optimization services (protocol and format conversion, scheduled delivery, when the mobile station is out of range) Providing temporary storage of content, broadcast services, group contracts, and other services).

  In the exemplary implementation, the mobile station further includes apparatus 42 of an embodiment of the present invention. The device is functionally expressed and formed of functional elements that can be implemented in any desired manner. Such methods are, for example, hardware implementation, software implementation, use of algorithms executable by processing circuitry, and firmware methods.

  The device further includes metadata indicated at 40. This metadata is associated with the content data 36. According to an embodiment of the present invention, the metadata includes attributes that form notification processing attributes that are added during application development, for example. Alternatively, the notification processing attribute is loaded into the content client 36, for example, at the application provision stage. Alternatively, the notification providing attribute is added to an application deployment descriptor or content manifest that is made available for the mobile station.

  The device further includes an identifier 46 and an operator 48. The identifier identifies the notification processing attribute, and the operator is coupled to the identifier to be provided with the network-provided attribute, and is coupled to the receiving portion 34 that receives the notification (ie, content data) pushed to the mobile station. The In the exemplary implementation, similar content metadata, identifiers, and operational elements are implemented at proxy server 26 and at application server 24. The device that includes these elements in the proxy server 26 is referenced 54, and the device that implements these elements in the application server 24 is referenced 58. In an exemplary implementation, different operations are performed at the proxy server and at the mobile station. However, different operations serve the same purpose of removing expired content in a timely manner and preventing the wireless transmission of such content and / or display of such content at the end user of the mobile station. Also, in one implementation that uses the final retention scheme described below, the use of the device 58 embodied in the application server 24 is eliminated.

  Here, the device 54 embodied in a proxy server is shown to include a delivery queue 55 and a push handler 56, as well as content data 38 and metadata 40.

  In an exemplary embodiment of the invention, the expire replacement attribute forms a notification processing attribute. The expire replacement attribute is used to instruct the content client 36 or the proxy server 26 to replace the expired content or a part of the expired content with new content. In this exemplary implementation, the replacement is performed by the operator 48 wherever the content is not yet reached the final processing stage (eg, display for viewing by the end user). By doing this, the end user experience is improved.

  In another exemplary implementation, background processing attributes form notification processing attributes. This is also identified in the content metadata or elsewhere such as an application deployment descriptor or content manifest. The background processing attribute is used by the content client when acted on by the operator, processes the content when its associated target application is inactive or dormant, and is processed in background and foreground modes Adjust between content.

  In one implementation, properties (ie, notification processing attributes) are added to the content metadata and loaded into the server proxy or content client as shown in the application provisioning phase. Alternatively, the information is added to the application deployment descriptor or content manifest and made available on the device or software component.

  In an exemplary operation of the communication system, the delivery and processing of notifications related to the same dynamic content is performed. Notifications related to the same dynamic content are sometimes referred to herein as like notifications. When a large number of notifications are maintained in a delivery queue or application message store, the available storage capacity is exploited inefficiently. This is because a notification having the latest updated content overwrites data included in all other notification types. The notification with the latest updated content is typically the most recent notification. Examples of notifications are a weather forecast associated with a specific area to be updated, a stock price for a specific stock to be updated, and the like.

  In an expired replacement delivery mode of operation, an expired replacement notification processing attribute (sometimes referred to herein as RO) provides a mechanism and technique for replacing notifications that include expired content. In systems that experience raw notifications in one or more application message stores, such as in any element of communication system 10 elements (particularly content providers, proxy servers, and mobile stations), the expire replacement attribute is , Advantageously realized. Unprocessed occurs, for example, when the content processing speed is slower than the content distribution speed. Further, unprocessing occurs when a low control rule interrupts the content distribution process. Unprocessed occurs when the targeted content customer is unavailable for a long period of time. And unprocessed sometimes occurs when the content source generates messages in bursts. Both of these situations are susceptible to the effects that occur in wireless or mobile communication systems. For example, the mobile station 14 may be placed out of range from time to time while moving, or it may receive data while operating in other modes (eg, when operated in accordance with a voice telephone call). You may not be able to receive. As a result, in the emergency situation that occurs at the peak of traffic, unprocessed notifications are likely to occur. Even in such a case, using RO processing related to the expired replacement attribute prevents or limits communication failure. it can.

  When performing an expire replacement operation, the notifications are ordered, for example, in association with the dynamic content timestamps included in the notifications. Providing a time stamp identifies the latest update notification from the set of notifications. Operation by an operator, or time stamp and ordering, provides identification of the latest update notification. In addition, tracking of notifications associated with the unique message identifier (ID) is also provided by the operator. Using unambiguous message identification, the operator can use the identification information from the expiration replacement attribute of the replacement notification to replace the expiration notification or a portion thereof.

  Additionally, a correlation notification is provided regarding the dynamic content included in the notification. Notification grouping is facilitated. Then, in one implementation, the operator executes a replacement algorithm that replaces the expiration notification. The execution of the algorithm provides a way to replace expired notifications with updated notifications. The replacement algorithm can be implemented, for example, on a time basis, on an identification basis, or on a transformation basis. And in an alternative implementation, a rule-based algorithm is used. For example, in one implementation, the metadata 40 carries rule information or provides links or references to external rules. In one implementation, when conversion based, the expiration replacement attribute includes a conversion script (eg, XSLT) or references or links to the conversion to be applied to the expiration notification message. Wireless communication systems can take advantage of the expiration replacement mechanism particularly advantageously. The content processing speed of a wireless communication system can sometimes be slower than the content delivery speed. This is because sometimes the resources available to a mobile station are limited when operating on a high speed wireless network. In addition, since the operating characteristics of the wireless network are volatilized and the mobile station moves, the link defined on the wireless interface between the mobile station and the wireless network is susceptible to disconnection. When a link is broken, content delivery is interrupted until the link is restored. Also, in order to avoid content overflow at the mobile station, various wireless transport protocols control content delivery by temporarily interrupting content delivery.

  Through the operation of the expire replacement attribute, either in the mobile station or in the network part (eg, at the proxy server or application server), the unhandled notification is mitigated or less prone to problems. When out-of-date replacement is provided for notification ordering, the most recent notification is generally the latest update notification. As a result, ordering is performed based on the notification arrival time, and the notifications are sorted. Alternative ordering procedures can of course also be performed to order the notifications. In other exemplary implementations, the notification is correlated to the dynamic content included within the notification. Correlation includes the generation of a final ID hold. This final ID retention uniquely identifies the data record set (and hence the group of notifications) affected by the notification. The final ID holding is formed by, for example, a pairing of a data recording type and a data recording holding, and each pairing is for the data field of each key field specified by the notification. Keyed data fields include fields that are mapped to some data records in the application data store. In an exemplary implementation, for simplification purposes, the order of pairing within the final ID hold is defined according to the depth first order traversal of the notification data structure. Other orderings of pairing within the final ID hold are also possible. The resulting final ID hold describes all of the keyed data components that can be updated or inserted as a result of the notification process.

  In various implementations, various expiration replacement attribute values are provided. First, in a mode where expired replacement is equal to previous replacement, only the end of the notification class is replaced with a new notification message. In the previous full replacement mode of operation, all previous notifications are removed and a new notification message is added to the message store. When the expiration replacement is equal to replacing the ID with ID = “##”, the notification identified by the ID attribute is replaced with a new notification message. In the operation mode of the replacement fragment, the structure of the notification message corresponds to the XML or other element to be replaced. The notification identified by the ID attribute is pulled from the message store, and the identified element is replaced with the content of the new notification. The content of XML, or else, the element includes any data type, such as a binary value, or a link to any data (eg, a video stream). In the replacement conversion mode, the notification message includes conversion information to be applied to a specific expiration notification. Alternatively, if an ID attribute is specified, it applies to all previous notifications. The conversion information is represented, for example, as an attached XSLT document, a link to an XSLT document, or a link to a conversion handler.

  When the expired replacement attribute is operated in all previous replacement modes, the replacement algorithm is executed, the oldest notification class is replaced, and the rest of the notification class is discarded. By executing this algorithm, the distribution speed of the dynamic content can be reserved. An additional replacement algorithm is used alternatively. When executed, new notifications are added to the application message store according to the ordering rules, and all notifications are discarded. When this replacement algorithm is used, the delivery rate of dynamic content is preserved.

  The following examples illustrate the application of the expiration replacement mechanism for different content types and how the expiration replacement operator identifies notifications using various identification calculation procedures.

The following method defines the following XML definitions for data and messages:
Application: SomeApp
<Data name = "DataTypeA" key = "intField">
<Field name = "intField" type = "int">
<Field name = "stringField" type = "DataTypeB">
</ Data>

<Data name = "DataTypeB" key = "strField">
<Field name = “stringField2” type = “string”>
</ Data>

<Message name = "MyNotification1">
<Field name = "myField" type = "DataTypeA">
</ Message>
think of.

Then MyNotification1 is the following:
MyNotification1 RO = “replace-all-previous”>
<MyField>
<IntField> 1234 </ intField>
<StringField>
<StringField2> foo </ stringField2>
</ StringField>
</ MyField>
</ MyNotification1>
It seems like.

Here, intField uniquely identifies the data included in the notification message. For example, see the value of the key attribute in the definition of “DataTypeA”. The expire replacement mechanism uses a combination of application name, message name, and key attribute value to identify the replacement identification. In this example, the replacement identification is calculated as <someapp :: MyNotification1 :: 1234>. In another example, a given XML element can be used for identification calculation as follows:
<Data expire = “02/13/06 12:00 am” RO = “replace-previous”>
<App> StockQuotes </ app>
<Type> StockInfo </ type>
<Token> RIMM </ token>
<Payload>. . . </ Payload>
</ Data>
Used like

  Here, the XML elements <app>, <type>, and <token> uniquely identify the data content. In this XLM notification message example, the replacement identification is calculated as <StockQuotes :: SockInfo :: RIMM>. As a result of this message, all previous RIMM stock prices in the message store are replaced with the information contained in the payload.

In an alternative implementation, this message has the following structure:
<Data expire = “02/13/06 12:00 am” RO = “replace-fragment”
ID = “StockQuotes :: StockInfo :: RIMM”>
<Payload>. . . </ Payload>
</ Data>
Have

As another example, the replacement ID is the value of the XML element:
<Data RO = “replace-by-id” ID = “1D23AC17”>
<App> StockQuotes </ app>
<Type> StockInfo </ type>
<ID> 12564BF2 </ ID>
<Payload>. . .
Form.

  In this example, the XML document includes an <ID> element that uniquely identifies the notification message. In this XML notification message, the expire replacement processor finds a notification with an identification element value that matches a specific identification attribute, ie, finds “1D23AC17” and replaces the notification with a new notification.

  When background processing attributes are activated, a notification delivered to a mobile application residing at the mobile station allows the application's internal data to be updated. When the notification arrives at the mobile station, the mobile application may be active (i.e., active) or, alternatively, not. If the application is running, each notification is processed when the notification arrives. Any necessary internal data is then updated and, if appropriate, the content is displayed to the end user. When the application is running, foreground processing is performed in the manner just described. When an application is closed (ie, not active), the basic way to handle a notification is to queue the notification when it arrives. Subsequently, when the application is started, it processes the notifications stored in its queue.

  Through the operation of the background processing attribute of the embodiment of the present invention, an update to the internal data of the application is performed while the application is closed, ie, not active. This means that notification background processing is performed. In operation, an application can still release all of its resources when closed. When it is required to process notifications by obtaining only minimal resources, when it is needed, the data remains continuously updated and the end user can The data is ready for the end user when it continues or when it causes the start of the operation.

  FIG. 2 shows the portion of the mobile station 14 shown in FIG. 1 and the application that forms its content client 36. This portion likewise forms part of the network, such as application server 24 or proxy server 26. Here, an application 68, an application definition store 72, an application data store 74, and an application message store 76 are shown. The application message store includes a message router 78, which is coupled to the communication layer 84 by a line 82 represented here.

  The application definition store 72 includes data definitions, message definitions, and executable scripts. A data definition exists for each unique data type in the application and is given a unique data identifier. The data definition specifies the order and type of fields within the data type. A message definition exists for a unique type of application and is given a unique message identifier. The message definition specifies the order and type of fields in the message. A message includes one or more data types. The script is, for example, an executable Java (registered trademark) script and operates on one or more data types. Message arrival and processing triggers script processing. The script has access to the data contained in the message, for example. The script association for the message is specified by the application developer.

The following exemplary data types are referred to as simple data types, but simple data includes two fields (integer and string). Here is the simple data:
<Data name = "SimpleData" key = "intField">
<Field name = "intField" type = "int">
<Field name = “stringField” type = “string”>
Is provided.

  All of the simple data type data is included in the set belonging to the application. When a simple data component is inserted into a set, the key identified as the field “intField” for this type determines whether an existing component in the set should be updated or whether the component is new. Used to do.

Another example of a simple message is:
<Message name = "SimpleMessage">
<Field name = “simpleDataField” type = “SimpleData”>
</ Message>
As shown.

This message definition preferably specifies whether background processing properties have been set. In this exemplary embodiment, the background processing property is relevant only if the message is a notification. In this example, the definition is as follows:
<Message name = “SimpleMessage” Background Processing = “true”>
<Field name = “simpleDataField” type = “SimpleData”>
</ Message>
To be expanded.

  A simple script called SimpleScript is associated with a simple message. When processing a simple message, SimpleScript is also executed. SimpleScript, for example, performs some data operation and displays the data present in the message to the end user, or requests some other input. While processing the message, data updates from the message including the notification occur in the same way, both in the foreground mode and in the background mode, where the mobile station is operational. The presence of a particular data type in the message indicates how the message data to application data mapping should be performed. Using the simple message example, a field of type SimpleData is read from the message, and the component is automatically stored in the set of SimpleData types by the application. If the key of a component in the message matches an existing key in the set, the component in the set is updated. If not, the component from the message is added as a new component to the set. Application data store 74 contains stored data for the application.

  This application message store points to two queues (foreground queue 86 and background queue 88). When the application is running, only messages from the foreground queue are processed. When the application is closed, only messages from the background queue 88 are processed. The message router 78 in the application message store receives any incoming message (here received by line 82) based on the application status and background processing properties of the notification message to apply to the appropriate queue 86 or 88. Routed messages). The message router becomes aware of the state of the application depending on the operation time of the application. The operating time environment notifies the message router 78 when the application 68 is started or closed.

  Each message entering the device includes an application identification and a message identification. Communication layer 84 uses the application identification to place the message in the appropriate message store 76. In this message store, the message is retrieved by message router 78. If the application is running, the message is routed to the foreground queue 86. However, if the application is closed, the message router 78 retrieves the appropriate message definition from the definition store 72 using the message identification. If the message definition indicates that a background processing property has been set for the message, the notification is routed to the background queue. If not indicated, notifications are routed to the foreground queue.

  In this mode, the running application requests all of the resources to display all user interface definitions, user events, and messages and scripts, as well as all definitions and data in memory. To do.

  FIG. 3 shows elements similar to those shown in FIG. However, here, the background queue 88 and the line 94 shown here show the combined background processor 92. The background processor 92 is central to all applications in one embodiment. Alternatively, the background processor is dedicated to a specific application. And in the extended implementation, the application registers a runtime environment with its custom background processor to handle background notifications. In this implementation, the background processor is central to all applications. The message router notifies the background processor of the new notification. The background processor removes the first message from the head of the background queue 88. The background processor then accesses the application definition store to obtain the appropriate message definition and any associated scripts. The processor also accesses the application data store 74 to update and store the data.

  In this background operation mode, the background processor is idle and consumes little resources when there is no background notification to process. When it is required to process a notification, the background processor temporarily loads only the necessary definitions and data from the application store 74.

  Foreground rules allow unlimited script execution, including both data and user interface operations. If the application is running but the application is not currently in use, script execution with a user interface operation that requires user input will block further message processing, for example, until input is received. In contrast, background rules limit the operations that can be performed from a script. For example, user interface operations cannot be performed when the application is closed. During development, the developer is given the option to identify two scripts to be associated with the message, one for foreground execution and the other for background execution. An alternative provides access to application status flags in the script. UI (user interface) operations are wrapped by the developer within the scope of a check that asserts that the application is saved to a running application.

  Message order is maintained in background mode. The message protocol includes, for example, a request for ordering message processing for an application. Typically, the communication layer includes appropriate logic at the transport level to support ordered messages. In the foreground mode, message ordering at the application level is maintained by queuing messages in the order received at the communication layer and processing the messages in that same order. Introducing a background queue for processing in background mode breaks strict ordering.

  FIG. 4 is an exemplary queue structure in which an application is running. The application has messages A and B and notification messages C, D and E. When the application is closed, the message router filters the notification using the background processing property set and newly routes the notification to the background queue.

  FIG. 5 shows the resulting queue structure. Notifications using the background processing property set do not remain ordered for non-background messages. This is suggested by the nature of this property. However, all notifications using background processing steps remain ordered relative to each other. When the application is started, the message router again routes any outstanding messages in the background back to the top of the foreground queue.

  Flow control is further provided. When the application is running, flow control is managed for the application as a whole. When the foreground queue size reaches the maximum threshold, all messages for the application are suspended. When the foreground queue size falls below the minimum threshold, delivery of all messages to the application resumes.

  When the application is closed, flow control is managed separately in the foreground and background queues. That is, while the background message is being delivered, the foreground message is interrupted and vice versa. A separate threshold for the interruption and resumption of the foreground message versus background message flow may also be set.

  FIG. 6 illustrates a method, indicated generally at 102, that represents the method of operation of an embodiment of the present invention. This message uses push content in a communication device that can operate in accordance with the push content communication scheme.

  Initially, as indicated by block 104, at least a first selection notification attribute is identified. The push content is then operated in a manner corresponding to the appropriate notification attribute of the at least first selected notification processing attribute, as indicated by block 108.

  Therefore, this method facilitates the delivery and processing of asynchronous push content.

  The above description is a preferred example for implementing the present invention, and the scope of the present invention should not necessarily be limited by this description. The scope of the present invention is defined by the following claims.

1 shows a functional block diagram of a wireless communication system in which an embodiment of the present invention can operate. FIG. FIG. 2 shows a functional block diagram of a portion of a communication device operable in accordance with an embodiment of the present invention. A functional block diagram similar to the functional block diagram shown in FIG. 2 is shown, but here represents an alternative operation of an embodiment of the present invention. FIG. 3 is a diagram of a queue structure in an application message store during a first exemplary operation of a communication device of an embodiment of the present invention. FIG. 4 shows a diagram similar to that shown in FIG. 4, but here shows a diagram of the queuing structure when the communication device is operated in another way. 2 shows a flow chart of a method listing methods of operation of an embodiment of the present invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Communication system 12 Network part 14 Mobile station 16 Wireless interface 18 Access network (AN)
22 data network 24 application server 26 proxy server 32 transmission part 34 reception part 36 content client 38 content data 40 metadata 46 identifier 48 operator 55 delivery queue 56 push handler

Claims (34)

An apparatus for a communication device operable in accordance with a push content communication scheme, the apparatus comprising:
A notification processing attribute identifier configured to identify at least a first selected notification processing attribute;
A push content operator adapted to receive an indication of the first selected notification processing attribute and to receive push content, the push content operator comprising the at least first selected notification processing attribute A push content operator configured to operate on the push content in a manner corresponding to the appropriate notification attribute. The first selected notification processing attribute identified by the notification processing attribute identifier comprises an expiration replacement attribute;
The apparatus of claim 1, wherein the push content operator operates on the push content and replaces expired portions of the push content according to a replacement rule set.   The apparatus of claim 2, wherein the push content operator arranges the push content in chronological order, and the expired portion of the push content is replaced according to the chronological order of the push content. The push content operator further identifies each portion of the push content using a unique message identifier;
The apparatus of claim 2, wherein the expired portion of the push content is replaced according to a value of the unique message identifier associated with the portion of the push content. The first selected notification processing attribute identified by the identification processing attribute identifier comprises a background processing attribute;
The apparatus of claim 1, wherein the push content operator operates on the push content in a background mode. The communication device comprises a content client and updatable application internal data,
The apparatus of claim 3, wherein the push content operator operates on the push content while the content client is closed. The communication device further comprises an application message store configured to store content data messages;
The apparatus of claim 6, wherein the push content operator operates on the push content message stored in the application message store.   8. The apparatus of claim 7, wherein push content delivered to the communication device is queued at the application message store when the content client is closed.   The apparatus of claim 1, wherein the communication device comprises a mobile station having a content client, and wherein the notification processing identifier comprises content metadata stored in the mobile station.   The apparatus of claim 9, wherein the push content operator is implemented in the mobile station and configured to access the metadata stored in the mobile station and receive the push content. The communication device includes a network server having push content available;
The apparatus of claim 1, wherein the notification processing identifier comprises content metadata stored in the network server.   The apparatus of claim 11, wherein the push content operator is implemented on the network server and configured to access the metadata stored on the network server and receive the push content. The communication device includes a proxy server to which the push content is routed,
The apparatus according to claim 1, wherein the notification processing identifier comprises content metadata usable by the proxy server.   The apparatus of claim 13, wherein the push content operator is implemented in the proxy server and configured to access the metadata stored in the proxy server and receive the push content. A method of utilizing push content in a communication device operable in accordance with a push content communication scheme, the method comprising:
An operation identifying at least a first selected notification processing attribute;
An operation that operates on the push content in a manner corresponding to an appropriate notification attribute of the at least the first selected notification processing attribute.   The method of claim 15, wherein the first selected notification processing attribute identified during the identifying operation comprises an expire replacement attribute.   The method of claim 16, wherein the operating operation comprises replacing an expired portion of the push content.   The method of claim 15, wherein the first selected notification processing attribute identified during the identifying operation comprises a background processing attribute.   The method of claim 18, wherein the operating operation comprises operating on the push content in a background mode. The communication device comprises a mobile station,
The method further includes an operation of pushing the push content to the mobile station;
The method of claim 15, wherein the identifying operation and the operating operation are performed at the mobile station. A device for a mobile station operable to receive push content communicated to itself, the device comprising:
A notification processing attribute identifier configured to identify at least a first selected notification processing attribute;
A push content operator adapted to receive an indication of the first selected notification attribute and the push content received at the mobile station, wherein the push content operator is the at least the first A push content operator configured to operate on the push content in a manner corresponding to the appropriate notification attribute of the selected notification processing attribute. The mobile station further comprises a user display,
The apparatus of claim 21, wherein the push content operator is configured to operate on the push content prior to display by the user display. The first selected notification processing attribute identified by the notification processing attribute identifier comprises an expiration replacement attribute;
The apparatus of claim 21, wherein the push content operator operates on the push content and replaces expired portions of the push content according to a replacement rule set.   24. The apparatus of claim 23, wherein the push content operator orders the push content in chronological order and the expired portion of the push content is replaced according to the chronological order of the push content. The push content operator further identifies each portion of the push content using a unique message identifier;
24. The apparatus of claim 23, wherein the expired portion of the push content is replaced according to a value of the unique message identifier associated with the portion of the push content. The first selected notification processing attribute identified by the identification processing attribute identifier comprises a background processing attribute;
The apparatus of claim 21, wherein the push content operator operates on the push content in a background mode. The mobile station comprises a content client and updatable application internal data,
25. The apparatus of claim 24, wherein the push content operator operates on the push content while the content client is closed. The mobile station further comprises an application message store configured to store content data messages;
27. The apparatus of claim 26, wherein the push content operator operates on the push content stored in the application message store.   28. The apparatus of claim 27, wherein push content delivered to the mobile station is queued at the application message store when the content client is closed. An apparatus for a network device operable according to a push content communication scheme in which push content is pushed asynchronously, the apparatus comprising:
A notification processing attribute identifier configured to identify at least a first selected notification processing attribute;
A push content operator adapted to receive an indication of the first selected notification attribute and to receive push content pushed asynchronously, the push content operator comprising the at least first selection A push content operator configured to operate on the push content in a manner corresponding to an appropriate notification attribute of the notified notification processing attribute. The first selected notification processing attribute identified by the notification processing attribute identifier comprises an expiration replacement attribute;
31. The apparatus of claim 30, wherein the push content operator operates on the push content and replaces expired portions of the push content according to a replacement rule set.   32. The apparatus of claim 31, wherein the push content operator arranges the push content in chronological order, and the expired portion of the push content is replaced according to the chronological order of the push content. The push content operator further identifies each portion of the push content using a unique message identifier;
35. The apparatus of claim 32, wherein the expired portion of the push content is replaced according to a value of the unique message identifier associated with the portion of the push content.   32. The apparatus of claim 30, further comprising a push handler configured to push the push content once operated by the push content operator.

Images