RU2666240C1 - System and method of controlling push-notifications - Google Patents

Abstract

FIELD: communication equipment.

SUBSTANCE: invention relates to the field of messaging. Technical result is achieved by obtaining: through the system of Internet-based services of individuals from the user's communication device a request for transactions in the automated system of the bank, as well as security token parameters, which includes a push address assigned to the user's communication device by the cloud data store; through the system of Internet-based services for individuals generating parameters and text of short and complete push notifications and standby CMCs, that inform the user that it is not possible to send push notifications to the user's device, depending on the operations performed in the automated system of the bank based on the received request from the user's communication device; transmitting the generated parameters and the text of short and complete push notifications and standby CMCs through the push gateway to the push platform connected to the cloud data store containing the profile of the user communication device.

EFFECT: technical result is to increase the efficiency of delivering messages to the client with information about banking events and transactions.

5 cl, 1 dwg

Description

FIELD OF TECHNOLOGY

[001] This technical solution generally relates to the field of messaging, and in particular to a system and method for managing push notifications for informing customers about banking events and transactions occurring with their accounts, cards, products and offers from the bank.

BACKGROUND

[002] Currently, the existing push notification technology has a number of significant disadvantages. The size of the transmitted data is very limited, in particular, for devices with the iOS operating system, it is only 256 bytes. There is no guarantee that the delivered notification will be available to the mobile application, since the initial processing of push notifications is performed by the operating system, without launching the application. The application is launched either by pressing the function button at the time of viewing the received message by the user, or by clicking on the message in the general list of push notifications received by the mobile device. If the user deletes the notification from the list, or after viewing the notification just received, it simply closes it without launching the application, then in the mobile application no data for this notification will be available. Additionally, with the help of push notifications, it is impossible to transfer closed data, which should be available to the client only after authorization in the mobile application.

[003] A technical solution is known from the prior art that discloses a method and message management system described in US Patent Application No. 2015106456 (A1), patent holder: JVL Ventures, LLC, published: 04/16/2015. In this solution, messaging is carried out between service providers and mobile devices equipped with messaging software, including push notifications. This solution is the closest analogue.

[004] The disadvantages of the known solution are the inability to promptly inform customers about banking events and operations through push notifications.

SUMMARY OF THE INVENTION

[005] The technical task to which the claimed technical solution is directed is to increase the efficiency of message delivery to the client with information about banking events and operations.

[006] The technical result achieved in the implementation of this technical task is to increase the speed and reliability of delivery of the text of notifications from the Internet service system of individuals to the user's communication device.

[007] To ensure the above result, a push notification management system has been developed comprising:

[008] a cloud data storage, configured to:

[009] - determine at least one user communication device for sending push notifications;

[0010] - send a short push notification received from the push platform to at least one user communication device;

[0011] a push platform connected to a cloud data storage containing a profile of at least one user communication device configured to send short and full push notifications and backup SMS generated by an individual’s Internet service system in accordance with a request by at least one user communication device and Security Token parameters;

[0012] a push gateway for connecting a push platform to an individual’s Internet service system and a bank automated server system;

[0013] an Internet service system for individuals, configured to receive Security Token parameters from at least one user communication device and generate short and full push notifications and backup SMS parameters and text depending on the operations that have been performed in an automated banking system based on a request from a user’s communication device, for sending them to at least one user’s communication device.

[0014] A push notification management method has also been developed, comprising the steps of:

[0015] receive, through the Internet service system of individuals, from a user’s communication device, a request for operations in the bank’s automated system, as well as Security Token parameters, which include the push address assigned by the cloud storage to the user's communication device;

[0016] through the Internet service system of individuals generate parameters and text of short and full push notifications and backup SMS depending on the operations that are performed in the automated system of the bank based on the received request from the user’s communication device;

[0017] transmit the generated parameters and text of short and full push notifications and standby SMS via a push gateway to a push platform connected to a cloud data storage containing a profile of at least one user communication device configured to send short and full push - notifications and backup SMS to at least one user’s communication device, and short push notifications to at least one user’s communication device are transmitted via a cloud data storage.

BRIEF DESCRIPTION OF THE DRAWING

[0018] For a better understanding of the essence of the invention, and to more clearly show how it can be implemented, hereinafter, reference will be made, only as an example, to the attached drawing, on which:

[0019] FIG. 1 is a diagram of an interaction system of an Internet service system of individuals and a user communication device.

DETAILED DESCRIPTION OF THE TECHNICAL SOLUTION

[0020] In accordance with the circuit of FIG. 1, the interaction system of the Internet service system of individuals and the user's communication device comprises: at least one user communication device 100, a push notification management system 110, and at least one server 107 of an automated bank system responsible for processing an incoming SMS message stream from customers. The user communication device 100 may be any computing device configured for wired or wireless communication with elements of the push notification management system 110, for example, a mobile phone, tablet, desktop or laptop computer, laptop, etc.

[0021] The push notification management system 110 includes:

[0022] - cloud data storage 120, which may be such platforms or push notification providers as GCM, APNS, WNS, for example, which are servers, but not limited to;

[0023] a push platform 130 comprising a data storage unit 130.1;

[0024] - push gateway 140, providing a connection of the push platform with the system 150 of Internet services for individuals and the server 107 of the automated banking system responsible for processing the incoming stream of sms messages from clients, as well as containing a data storage unit 140.1;

[0025] - an individual Internet service system 150 comprising a network adapter 150.1 for interacting with a push gateway 140, a notification generation unit 150.2, a mAPI interface 150.3, a data storage unit 150.4;

[0026] - SMS gateway 160.

[0027] All elements of the system 110 can be implemented on the basis of at least one processor or microcontroller, modified in the firmware, in such a way as to ensure the fulfillment of the functions assigned to them below.

[0028] After installing the mobile application 100.1 on the user communication device 100 (or mobile device) and activating the push notification settings, the user communication device 100 sends a request for a push address to the cloud data storage 120, the request containing data identifying the device 100 user communications, such as a device identifier, and used to register a device, as shown in Appendix 1. A request can be sent using the XMPP, HTTP / 2, HTTP messaging protocol, but not og scolding them. In response to the request, the cloud data storage 120 generates a unique push address and sends the generated push address to the user communication device 100, which assigns the received push address to the installed instance of the mobile application 100.1. The push address identifier is generated automatically and must be globally unique throughout the entire interaction between the system and the push gateway. In some embodiments, the identifier may have a numerical or symbolic value. Also, the user communication device 100 generates a Security Token, which includes the assigned push address. The security token may be a Base64-encoded JSON string containing information about the user communication device 100. This information may contain the hash value (SHA1) from the user authentication data, the identifier of the device, which is generated by default at the time of application installation, but can be assigned via API, the serial number of the device, the address of the device in the Push network, the IP address of the device , device model, GPS coordinates of the device, device locale name, and so on, without limitation.

[0029] The generation of push addresses is as follows.

[0030] For the client’s login on the installed instance of the mobile application, the rights are checked to enable push notifications. If rights are not granted, the mobile application does not initiate verification. If granted, the mobile application registers a specific instance of the mobile application in the cloud storage 120 data. Upon registration, a specific instance of the mobile application is assigned a push address that is generated based on the identifier of the instance of the mobile application.

[0031] In order to send a request in the form of POST data to the system of Internet services for individuals 150 from the user’s communication device 100 to perform any operations in the automated system of the bank, the user must log in to application 100.1. After the user goes through the authorization steps, the application 100.1 requests the Security Token parameters from the user’s communication device 100 and transmits them together with the request to the individual Internet service system 150 via the mAPI interface via the HTTPS / XML protocol. To enter the application, the client needs to log in (authenticate). Authentication can be considered completed if, as a result of the execution of an authentication step, a successful status was obtained (for example, status code 0), as well as the login element of the mobile application is confirmed. The application on the mobile device must support cookies. Cookies are required to store the session identifier JSESSIONID, which can be changed several times in the same session.

[0032] Depending on the operations that are performed in the automated system of the bank based on the request received from the user’s communication device 100, the Internet service system for individuals 150 generates, via the notification generation unit 150.2, the parameters and text of short and full push notifications, as well as the text backup SMS, as shown in Appendix 3. The response can come in XML format. In each response, the status of the response, by which the user device can determine the presence of an error in the response, necessarily comes. To control the time after which the backup SMS will be sent, a tag is used, in the value of which the time of sending the backup SMS in minutes is transmitted. To obtain the status of sending backup SMS, a service is used in which to display the status in this call of the backup SMS, the phone number to which the message is sent and the status of the backup SMS are used.

[0033] In some embodiments, the push messages are grouped by type according to the type of event that triggered the sending of the message.

[0034] In some embodiments, push notifications can be either of an informational nature (notification of authorization in a mobile application, as an analogue of an SMS notification), or request the client to perform certain actions (confirm operations, specify operation parameters).

[0035] In some embodiments, the short push notification has a size of 2 KB (in Unicod / UTF-8, 1000 characters) or 4 KB (in Unicod / UTF-8, 2000 characters). A short push notification is sent via a push network and can be displayed as a system message (Alert), and this notification is intended to be displayed on the mobile device in the message list as a header. Short push notifications contain the text that should be displayed to the user, service data for the operating system, as well as a unique identifier for all push notifications (using the identifier you can link short and complete messages). Upon receipt of a push notification, a sound signal may be emitted on the mobile device, the icon of the recipient application may change, the text from the notifications may be displayed in a window with two buttons. When the first button is pressed, the notification window closes; when the other button is pressed, the application that is intended to receive the push notification is launched.

[0036] In some embodiments, the full push notification is uploaded to a mobile application, for example, in XML format. Unloading takes place upon special request from a mobile application, and the push notification identifier is used for the request. A full push notification can contain notification text, service data, privacy type, push notification identifier, maximum sending time if not delivered, and additional data. Full push notifications can be divided by type (purpose). Each type has a defined type of privacy. To view the secret part of the message data with the privacy type “Closed”, authorization in the mobile application will be required.

[0037] Push notifications can be of the following types: notification of entry into the automated system of the bank, notification of assistance services, notification of acceptance for execution, one-time password to enter, one-time password to confirm the operation, notification of fundraising, notification of the invoice, transactional notifications, notifications from the messenger. Accordingly, if the request received from the user’s communication device 100 is a request for authorization in the bank’s automated system, then the notification generation unit 150.2 generates a notification of entry into the bank’s automated system when the user successfully passes the authorization steps in the bank’s automated system. Similarly, the other types of notifications mentioned above are generated for the corresponding operations, which can be performed in the automated system of the bank based on the request received from the user communication device 100.

[0038] The Security Token parameters are saved by the Internet service system 150 of individuals in the user profile 150.4 in the storage unit, and also transmits them via the network adapter 150.1 via the push gateway 140 to the push platform 130. The interaction between the push- The gateway and push platform are implemented using the TCP / IP protocol. Between the push gateway and the push platform, a TCP / IP session is supported, within which data is exchanged in a predetermined format. The push gateway in this interaction from a network point of view is a TCP server, and the push platform is a client. That is, the push gateway connects to the dedicated TCP port and accepts the connection from the push platform.

[0039] Implementation of the protocol of interaction between the push gateway and the push platform described in this technical solution provides the following features:

• monitoring the state of the TCP session between the push gateway and the push platform, and control should be carried out both from the push gateway and from the push platform;

• transmission of push notifications and backup SMS notifications from the push gateway to the push platform;

• transmission of push notification delivery statuses from the push platform to the push gateway;

• transfer of delivery status of backup SMS notifications from the push platform to the push gateway;

• information transfer for registering devices receiving push notifications from a push gateway to a push platform;

• transfer of information for updating data on devices receiving recipients of push notifications from a push gateway to a push platform;

• updating information about devices that receive push notifications from the push platform to the push gateway.

[0040] If the received request to complete the operation in the automated system of the bank from the user’s communication device 100 does not contain information about the security token parameters (Security Token), the Internet service system for individuals 150 through the notification generation unit 150.2 generates a backup SMS, as shown in Appendix 5, which is routed to the user communication device 100. This message informs the user that sending push notifications to the user communication device 100 is not possible. In some embodiments, the fallback message has a unique identifier as well as priority. The priority of backup SMS can take the following possible values:

[0041] LOW (1) - low;

[0042] NORMAL (2) is normal;

[0043] HIGH (3) is high;

[0044] REALTIME (4) is the maximum.

[0045] In some embodiments, message processing uses preemptive priority processing logic. Dynamic priority reduction is used when sending a message again if the previous attempt to send a message was unsuccessful.

[0046] In additional embodiments, the backup SMS has a status that can take the following possible values:

[0047] ENQUEUED (1) - queued for dispatch;

[0048] SENT (2) - message notification sent;

[0049] DELIVERED (3) - the user has downloaded the message;

[0050] READ (4) - the user has read the message;

[0051] FAILED (5) - sending error.

[0052] The security token parameters are encoded before being sent to increase the reliability of data transmission. The push platform 130 decodes the Security Token parameters to obtain the push address of the application 100.1 and determines whether the application 100.1 is registered in the storage unit 130.1.

[0053] The Security Token in decoded form may have the following form:

[0054] {"appPackage": "ru.sberbankmobile", "IMSI": "250018524041548", "screenResolutionY": "1776", "locale": "ru_RU", "memorySize": "1144", "screenResolutionX": "1080", "deviceUid": "290887d10c70003069087f4025564e63a7ad0000", "userSecurityHash": "fscUTfRH0JtAOv27TJz3y18LG \ / M =", "IMEI": "865800025607067", "timeZoneUTo00ms00setmsffsoffsetoffsetoffset ":" AndroidMSM8974 "," pushAddress ":" cJeVXjBl3zo: APA91bGDQr6BU1H8aTQQQQG6fpSB58FH5mnCmcZn3VaN5jecpsTXzWCHNbSH5OqKCOzXwKQnM450fthTEnc1DdLALZ1lAILvQQQ9FZzKwne6X5mREZZ4zMbYQZ_jYTJUwHMIIEUbls "," deviceSerialNumber ":" 4e1b955b "," macAddress ":" 36: 53: 9A: 2E: 4B: F4 "," version ":" 1.0 ", "osVersion": "6.0.1", "deviceModel": "OnePlusA0001", "providerUid": "PH47YU5vTjY6IkA + P1ZqYSQ4LiN + Pgo", "routerMacAddress": "02: 00: 00: 00: 00: 00", "deviceName ":" jenkinsinternal "," generationTime ":" 2017.09.2711: 22: 54 + 0300 "," ipAddress ":" fe80 :: fabc: 169d: 28: 2e8% rmnet0 "}.

[0055] If the application 100.1 corresponding to the received push address is not registered in the data storage unit 130.1, then the push platform 130 creates a profile of the device for sending push notifications, which includes information about the security token parameters and the push address. If the application 100.1 is already registered in the data storage unit 130.1, then the push platform 130 overwrites the changed security token settings in the corresponding device profile to ensure sending push notifications in accordance with the changed settings.

[0056] In addition to the Security Token parameters, from the individual Internet service system 150 to the push platform 130, the generated parameters and the text of the short and full push notification and the text of the backup SMS, which must be sent to the user communication device 100 in in accordance with the operation performed in the automated system of the bank and the device profile. The short push notification push platform 130 transmits to the cloud storage 120 data that defines at least one user communication device 100 to send a push notification and sends a short push notification to the user communication device 100 in accordance with the security token settings to display it text to the user, for example, in the banner area of a mobile application.

[0057] In addition to the text, the short push notification also contains the identifier of the push platform 130, for example, the URL and the identifier of the push notification. Thus, the user can start the application 100.1 and, based on the data of the short push notification received, send a direct request to the corresponding push platform 130 to receive the text of the full push notification corresponding to the received short push notification. Additionally, the push platform 130 can be configured to send a backup SMS corresponding to the text of the full push notification to the user’s communication device 100 via the SMS gateway 160, if the push platform 130 does not receive a request to download the full push text -notifications during a given time interval.

[0058] After receiving a full push notification, the application 100.1 sends a confirmation of the receipt of content to the push platform 130, which sets the reading status of the sent push notification, as shown in Appendix 4. The sending history and status of the push notification are stored in the data storage unit 130.1. Also, the reading statuses can be transferred upon request to the system 150 Internet services for individuals for storage in block 150.4 data storage.

[0059] Additionally, cloud data storage 120 may be configured to verify the validity of push addresses on user communication devices 100. In order to verify the validity of the assigned push addresses, the cloud storage 120 sends corresponding requests to the corresponding user communication devices 100, and if the user’s communication device 100 to which the push address is assigned does not receive a corresponding response to the request after a predetermined period of time, this push address is added to the list of invalid push addresses. The list of invalid push addresses is transmitted to the data storage unit 130.1 of the push platform 130 and, upon request from the system 150 of Internet services for individuals, can be transferred to this system. System 150 Internet services for individuals removes invalid push addresses from block 150.4 data storage and sends a deletion report to the push platform 130 to remove the corresponding addresses from the data storage unit 130.1.

[0060] In order to notify the user of operations performed outside the automated system of the bank, for example, about changing the balance of the card, the push gateway 140 is additionally connected to the server 170 of the automated system of the bank and configured to receive parameters and text of short and full push- notifications and backup SMS text generated by the server 170 of the automated system of the bank, as well as with the possibility of transmitting information received from the server 170 of the automated system of the bank to the push platform 130. Received mention s parameters and text from gateway 140 push-push-processed platform 130 as previously described method. The history of the notifications received by the push gateway 140 is stored in the data storage unit 140.1. The interaction of the system 150 Internet services for individuals and push-gateway 140 can be carried out through a web service, and if the web service is unavailable, integration via Open Database Connectivity (ODBC) can be used.

[0061] Thus, by distributing the request processing functions from the user communication devices 100, generating and delivering push notifications between the elements of the push notification management system 110 in the manner described above, the computational load on the personal Internet service system 150 is reduced. Additionally, the bandwidth of the data transmission channel between the Internet service system 150 for individuals and the user communication device 100 for exchanging data, as well as between the push platform 130, the cloud storage 120 data and the communication device 100 of the user, thereby increasing the speed of delivery of text notifications from systems 150 of the Internet service of individuals to the user communication device 100, and data loss resulting from congestion of the data transmission channel is reduced, i.e. increased reliability of data exchange.

[0062] Applications:

[0063] Appendix 1 - shows an example of registering applications on a push server;

[0064] Appendix 2 - shows an example of the implementation of sending push notifications to a mobile application;

[0065] Appendix 3 - shows an example of the delivery of push message content to a mobile application and receiving delivery statuses;

[0066] Appendix 4 - shows an example of the implementation of the reservation of delivery of push messages via SMS.

Claims (17)

1. A push notification management system comprising:

Cloud data storage, configured to:

determine at least one user communication device for sending push notifications;

send a short push notification received from the push platform to at least one user communication device;

a push platform connected to a cloud data storage containing a profile of at least one user communication device configured to send short and full push notifications and backup CMCs that inform the user that sending push notifications to the user device is not possible, generated by the Internet service system for individuals in accordance with the request of at least one user communication device and Security Token parameters;

a push-gateway for connecting a push-platform with an Internet service system for individuals and a server of an automated banking system;

an individual internet service system configured to receive Security Token parameters from at least one user communication device and generate short and full push notification and backup CMC parameters and text that inform the user that sending push - notifications to the user's device are not possible, depending on the operations that are performed in the automated system of the bank on the basis of the received request from the user's communication device, for sending them via push-pl tformu on at least one user communication device. 2. The system according to claim 1, characterized in that the cloud data storage is additionally configured to:

receive a push address request from at least one user communication device;

generate a unique push address for at least one user communication device and forward the generated address in accordance with the received request;

check the validity of push addresses. 3. The system according to claim 1, characterized in that the push platform is configured to receive a single text of short push notifications and backup CMCs that inform the user that sending push notifications to the user's device is not possible, from at least one server automated banking system. 4. A method for managing push notifications, comprising the steps of:

receive, through the Internet service system of individuals, from a user’s communication device, a request to perform operations in the bank’s automated system, as well as Security Token parameters, which include the push address assigned by the cloud data storage to the user's communication device;

via the Internet service system of individuals, parameters and text of short and full push notifications and backup CMCs are generated that inform the user that sending push notifications to the user's device is not possible, depending on the operations performed in the bank's automated system based on a received request from a user communication device;

transmit the generated parameters and text of short and full push notifications and backup CMCs, which inform the user that sending push notifications to the user's device is not possible, through a push gateway to a push platform connected to the cloud data storage containing a profile of at least at least one user communication device configured to send short and full push notifications and standby CMCs to at least one user communication device, wherein short push notifications to at least one User communication devices are transmitted through a cloud data storage. 5. The method according to p. 1, characterized in that they additionally receive a single text of short push notifications and backup CMCs, which inform the user that sending push notifications to the user's device is impossible, from at least one server of the automated banking system for sending it to at least one user communication device.

Images