JPWO2017193515A5

JPWO2017193515A5 -

Info

Publication number: JPWO2017193515A5
Application number: JP2019511902A
Authority: JP
Publication date: 2023-04-03
Anticipated expiration: 2036-09-09

Description

一部の特定のシナリオによる実施形態において、イベント情報は、イベントの発生時刻、発生場所、関係者情報、サービス内容情報などを含んでよい。例えば、航空券予約イベントの時間情報は、航空機の出発時刻、到着時刻、出発地、及び到着地、並びに乗客の名前、身分証明書番号、及びパスポート番号などを含む。サービス内容情報は、全ての段階に関する情報を含む。例えば、航空券関連イベントは、チェックイン、出発、空港到着、荷物預かりなどを含む。さらに、サービス内容情報は、チェックインの準備及びロック解除キーの提供などを含むホテル関連イベントであってもよい。鉄道乗車券関連イベントは、「出発待ち」、「間もなく出発」、及び「間もなく到着」などを含んでよい。映画チケット関連イベントは、引き換え番号及び座席案内などを含んでよい。配送関連イベントは、「収集済み」、「配達中」、「受け取り前」、及び「受け取りサイン済み」などを含んでよい。タクシー配車関連イベントは、「タクシーの手配を準備」、「運転手出発」、「タクシー到着」、「タクシー出発」、「移動開始」、及び「支払い」などを含んでよい。 In some specific scenario embodiments, the event information may include the time of occurrence of the event, location of occurrence, party information, service content information, and the like. For example, the time information of an airline ticket booking event includes flight departure time, arrival time, departure and arrival locations, as well as passenger names, identification numbers, passport numbers, and the like. Service content information includes information about all stages. For example, airline ticket related events include check-in, departure, airport arrival, luggage storage, and the like. Further, the service content information may be hotel-related events including preparation for check-in and provision of an unlock key. Rail ticket related events may include "waiting to depart", "departing soon", and "arriving soon". Movie ticket-related events may include redemption numbers, seat directions, and the like. Delivery-related events may include "collected", "delivery", "before receipt ", and "signed for receipt", and the like. Taxi dispatch related events may include "prepare for taxi", "driver departure", "taxi arrival", "taxi departure", "start of trip", and "payment".

現在の環境情報は、限定されるものではないが、現在時刻、現在地、光センサにより提供された情報に基づく分析によって認識される周囲の明るさ、ユーザのＧＰＳ情報が位置に変換されたことを示す情報、自宅のキーワードが特定の住所に変換されたことを示す情報、及び現在の交通手段（前もって設定されたルールを用いて、ユーザの速度及び姿勢に基づいて決定される）を含む。ユーザの運動情報は、限定されるものではないが、分析によって方向センサにより認識されたユーザの運動方向、加速度に基づく分析によって認識されたユーザの速度、及びユーザ運動状況（ウォーキング、ランニング、サイクリング、睡眠、静止、バス乗車、又はドライブ）を含む。サービス情報は、限定されるものではないが、チケット情報（乗車券、航空券、及び映画チケットなどのチケットに関連したメッセージ及び電子メールなど）、目的地（ユーザが地図分析プログラムに入力する目的地、航空券予約及びホテル予約に関連したＳＭＳメッセージに含まれる場所、又は自宅若しくは通勤する会社の場所などを含む）、目的地の到着時刻（現在のユーザ位置と目的地との間の距離及び交通状況に基づいて推定される）、及びサービス状況（航空券の場合は、チェックイン、空港出発、空港到着、及び荷物預かりなど。ホテルの場合は、チェックイン及び解錠など。鉄道乗車券の場合は、出発待ち、間もなく出発、出発、及び到着など。映画チケットの場合は、引き換え及び座席案内など。配送状況の場合は、収集済み、配達中、受け取り前、及び受け取りサイン済みなど。タクシー配車の場合は、手配中、運転手出発、タクシー到着、移動開始、及び支払いなど）を含む。さらに、ユーザ属性情報は、限定されるものではないが、ユーザの特徴（性別、年齢、身長、体重、及び国籍など）などを含む。 Current environmental information includes, but is not limited to, the current time, current location, ambient brightness as perceived by analysis based on information provided by the light sensor, information that the user's GPS information has been converted to location. information indicating that the home keyword has been translated to a specific address, and the current mode of transportation (determined based on the user's speed and posture using preset rules). The user's exercise information includes, but is not limited to, the user's movement direction recognized by the direction sensor from the analysis, the user's speed recognized by the acceleration-based analysis, and the user's exercise status (walking, running, cycling, sleep, rest, bus ride, or drive). Service information includes, but is not limited to, ticket information (such as messages and emails related to tickets such as train tickets, airline tickets, and movie tickets), destinations (such as destinations entered by users into map analysis programs), , locations included in SMS messages related to flight and hotel reservations, or the location of your home or business where you commute), destination arrival time (including the distance and traffic between your current location and your destination) (estimated based on the situation) and service status (for airline tickets, check-in, airport departure, airport arrival, luggage storage, etc. For hotels, check-in and unlocking, etc. For train tickets) is awaiting departure, soon to depart, depart, and arrive, etc. For movie tickets, redemption and seating information, etc. Delivery status, such as collected, delivered, not picked up, and signed for receipt, etc. Taxi dispatch (cases being arranged, driver departure, taxi arrival, movement start, payment, etc.). Furthermore, user attribute information includes, but is not limited to, user characteristics (gender, age, height, weight, nationality, etc.).

段階３０３において、判定エンジンモジュールは、サービス通知更新条件が満たされたかどうかを判定する。輸送情報に変化があった場合、判定エンジンモジュールは通知をプッシュする。図１３（ａ）に示すように、配送情報に関する複数の通知ＳＭＳメッセージが通知リスト形式で表示される。ユーザがこれらの通知のそれぞれをタップすると、図１３（ｂ）、図１３（ｃ）、図１３（ｄ）、図１３（ｅ）、図１３（ｆ）、及び図１３（ｇ）に別々に示すように、対応するイベント表示ページが、収集された配送状況に基づいてジャンプすることにより表示される。イベント表示ページに表示される内容は、配送サービス会社、配送進捗、物品配達詳細、受け取り場所、及びキーなどの情報を含む。さらに、操作可能なサービス、例えば、顧客サービス責任者に連絡する、メッセージを無視する、配送会社に連絡するなどがアクション領域に提供される。 At step 303, the decision engine module determines whether the service notification update condition is met. The decision engine module pushes a notification when there is a change in shipping information. As shown in FIG. 13(a), multiple notification SMS messages regarding delivery information are displayed in a notification list format. When the user taps on each of these notifications, they are shown separately in Figures 13(b), 13(c), 13(d), 13(e), 13(f), and 13(g). As shown, a corresponding event display page is displayed by jumping to based on the collected delivery status. The content displayed on the event display page includes information such as the delivery service company, delivery progress, item delivery details, pick-up location, and key. Additionally, operable services such as contact customer service representative, ignore message, contact shipping company, etc. are provided in the action area.

Claims

A method of pushing notifications on a mobile terminal with a display displaying a notification interface, comprising:
obtaining an event to be notified;
displaying first relevant information related to the notifiable event on a first notification page present in the form of a sub-page on the notification interface if the notifiable event is in a first event development stage; wherein the first relevant information includes first event context information corresponding to the first event development stage;
If the notifiable event progresses to a second event progress stage after the first relevant information is displayed, a second notification page existing in the form of a sub-page on the notification interface displays the notifiable event displaying second relevant information related to the , said second relevant information including second event context information corresponding to said second event development stage.

the event to be notified is a delivery event corresponding to delivery by the user;
the first event progress stage is a first delivery status, the first delivery status includes at least one of collected, in-delivery, or before receipt ;
the second event progress stage is a second delivery status, the second delivery status includes at least one of being delivered, not received , or signed for receipt;
if the first delivery status is Collected, the second delivery status is one of In progress, Pre-received, or Signed for receipt;
if the first delivery status is in delivery, the second delivery status is pre-received or signed for receipt;
If the first delivery status is pre-received, then the second delivery status is signed for receipt.
The method of claim 1.

a plurality of notification pages displayed in the form of sub-pages in the notification interface on the display for displaying a plurality of notifiable events, each of the plurality of notification pages corresponding to an event type;
3. The method of claim 2, wherein the subpage of the first notification page is displayed on one of the subpages of the plurality of notification pages, the first notification page corresponding to a delivery event type.

The method includes:
The method further comprising deleting the currently displayed first notification page or the currently displayed second notification page of the delivery event if the second delivery status is received and signed. The method according to 2 or 3.

The step of obtaining notifiable events includes:
obtaining at least one of a push message or a user action record;
analyzing whether the content of at least one of the push message and the user operation record is related to the notification target event, and whether the content of at least one of the push message and the user operation record is related to the notification target event; 2. The method of claim 1, comprising determining the event to be notified, if any.

6. The method of any one of claims 1-5 , wherein the notification interface is a lock screen.

The method further comprises:
determining a notification deletion condition based on the notification target event, wherein the notification deletion condition includes at least one of a deletion time condition, a deletion location condition, and a deletion user behavior condition; ,
and deleting the currently displayed first notification page or the currently displayed second notification page of the notifiable event if the notification deletion condition is satisfied. 7. The method of any one of 6 .

a display;
one or more processors;
memory;
A mobile terminal comprising a plurality of application programs and
the memory is configured to store a computer program;
said one or more processors launching said computer program to perform the method of any one of claims 1 to 7 ,
mobile terminal.

A computer-readable storage medium storing one or more programs, said one or more programs comprising instructions, said instructions being executed by a mobile terminal having a display and a plurality of application programs, said A computer readable storage medium enabling a mobile terminal to perform the method of any one of claims 1 to 7 , wherein the display comprises a touch sensitive surface and screen.

A graphical user interface for a mobile terminal with a display, comprising:
a notification interface displayed on the display device;
if the notifiable event is in a first event development stage, first relevant information related to the notifiable event is displayed on a first notification page present in the form of a sub-page in the notification interface; 1 related information includes first event status information corresponding to the first event progress stage;
When the notifiable event progresses to a second event progress stage after the first relevant information is displayed, a second notification page existing in the form of a subpage in the notification interface displays the notifiable event. A graphical user interface wherein associated second relevant information is displayed, said second relevant information including second event context information corresponding to said second event development stage.

the event to be notified is a delivery event corresponding to delivery by the user;
the first event progress stage is a first delivery status, the first delivery status includes at least one of collected, in-delivery, or before receipt ;
the second event progress stage is a second delivery status, the second delivery status includes at least one of being delivered, not received , or signed for receipt;
if the first delivery status is Collected, the second delivery status is one of In progress, Pre-received, or Signed for receipt;
if the first delivery status is in delivery, the second delivery status is pre-received or signed for receipt;
If the first delivery status is pre-received, then the second delivery status is signed for receipt.
A graphical user interface according to claim 10 .

a plurality of notification pages displayed in the form of sub-pages in the notification interface on the display for displaying a plurality of notifiable events, each of the plurality of notification pages corresponding to an event type;
12. The graphical user of Claim 11 , wherein said sub-page of said first notification page is displayed in one of said sub-pages of said plurality of notification pages, said first notification page corresponding to a delivery event type. interface.

13. The currently displayed first notification page or the currently displayed second notification page of the delivery event is deleted if the second delivery status is received and signed. The graphical user interface described in .

A graphical user interface according to any one of claims 10 to 13 , wherein said notification interface is a lock screen.

A program configured to cause a computer to execute the method according to any one of claims 1 to 7 .

A communication device comprising one or more processors, said one or more processors having at least one processor for causing said communication device to perform the method according to any one of claims 1 to 7 . A communications device that runs computer programs stored in one memory.