ASSISTANCE TO MOBILE OPERATORS IN THE PROVISION OF DATA SERVICES IN THE VISITED MOBILE NETWORK

20200314605 ยท 2020-10-01

    Inventors

    Cpc classification

    International classification

    Abstract

    This invention refers to a field of mobile communication, in particular to the mechanism developed to encourage mobile subscribers located in the coverage area of a visited mobile network (while roaming) to use data services provided by a visited mobile operator.

    The claimed invention is the mechanism of assistance to mobile operators in the provision of data services in the visited mobile network, which implementation could ensure achievement of the technical result allowing to involve more mobile subscribers to use data services in the visited mobile network, as well as the mobile app built-in software module, the computer readable medium, the user mobile device and hardware and software package that can implement the stages of this mechanism.

    Claims

    1. The mechanism of assistance to mobile operators in the provision of data services in the visited mobile network includes: identify a mobile subscriber and/or mobile app user; find an opportunity to offer to the mobile subscriber to use a data service package in the visited network; generate the data service package in the visited network and agree it with home and visited operators and third-party services; offer to use the data service package in the visited network on the terms other than standard terms of data services in the visited network:, activate the visited network data service package provided to the mobile subscriber on the offered terms; maintain mobile subscriber's use of the visited network data service package provided to the mobile subscriber on the offered terms; deactivate the visited network data service package provided to the mobile subscriber on the offered terms and activate the visited network data service package on standard terms.

    2. The mechanism according to claim 1, characterized in that the mobile subscriber and mobile app user identification includes searching mobile app user identifiers and binding them to the mobile network identifiers and/or mobile subscriber identity.

    3. The mechanism according to claim 1, characterized in that the finding of an opportunity to offer the mobile subscriber to use the data service package in the visited network includes receiving a tag of mobile subscriber's availability in the visited network, determining a status of the mobile data services, and/or identifying a user need to use the data services when using mobile applications.

    4. The mechanism according to claim 1, characterized in that the mutual settlement between the mobile subscriber, the visited and home networks and third-party services shall be performed before activation or after deactivation of the visited network data service package provided to the mobile subscriber on the offered terms.

    5. The mechanism according to claim 4, characterized in that the mutual settlement between the mobile subscriber, the visited and home networks and third-party services shall be performed after the mobile subscribers confirmation of the offered terms to use the data service package in the visited network.

    6. The mechanism according to claim 1, characterized in that the generation of the data service package includes definition of its parameters and provision conditions.

    7. The mechanism according to claim 1, characterized in that the maintaining of the visited network data service package provided to the mobile subscriber on the offered terms includes sending the mobile subscriber at least one advertising offer.

    8. Mobile app built-in software module containing program instructions that can implement the following: identify a mobile subscriber and/or mobile app user; find an opportunity to offer to the mobile subscriber to use a data service package in the visited network; offer to use the data service package in the visited network on the terms other than standard terms of data services in the visited network; activate/deactivate the visited network data service package provided to the mobile subscriber on the offered terms.

    9. The software module, according to claim 8, characterized in that the identification of the mobile subscriber and mobile app user includes searching mobile app user identifiers and binding them to the mobile network identifiers and/or mobile subscriber identity.

    10. The software module according to claim 8, characterized in that the finding of an opportunity to offer the mobile subscriber to use the data service package in the visited network includes receiving a tag of mobile subscriber's availability in the visited network, determining a status of the mobile data services, and/or identifying a user need to use the data services when using mobile applications.

    11. The software module according to claim 8, characterized in that it contains program instructions implementing the subscriber's confirmation of the offered terms to use the data service package in the visited network.

    12. Computer readable medium containing the stored software module containing program instructions that can implement the following: identify a mobile subscriber and/or mobile app user; find an opportunity to offer to the mobile subscriber to use a data service package in the visited network; offer to use the data service package in the visited network on the terms other than standard terms of data services in the visited network; activate/deactivate the visited network data service package provided to the mobile subscriber on the offered terms.

    13. Computer readable medium according to claim 12, characterized in that the identification of the mobile subscriber and mobile app user includes searching mobile app user identifiers and binding them to the mobile network identifiers and/or mobile subscriber identity.

    14. Computer readable medium according to claim 12, characterized in that the finding of an opportunity to offer the mobile subscriber to use the data service package in the visited network includes receiving a tag of mobile subscriber's availability in the visited network, determining a status of the mobile data services, and/or identifying a user need to use the data services when using mobile applications.

    15. Computer readable medium according to claim 12, characterized in that the software module contains program instructions implementing the subscriber's confirmation of the offered terms to use the data service package in the visited network.

    16. User mobile device containing the computer readable medium containing the stored software module containing program instructions that can implement the following: identify a mobile subscriber and/or mobile app user; find an opportunity to offer to the mobile subscriber to use a data service package in the visited network; offer to use the data service package in the visited network on the terms other than standard terms of data services in the visited network; activate/deactivate the visited network data service package provided to the mobile subscriber on the offered terms.

    17. User mobile device according to claim 16, characterized in that the identification of the mobile subscriber and mobile app user includes searching .mobile app user identifiers and binding them to the mobile network identifiers and/or mobile subscriber identity.

    18. User mobile device according to claim 16, characterized in that the finding of an opportunity to offer the mobile subscriber to use the data service package in the visited network includes receiving a tag of mobile subscriber's availability in the visited network, determining. a status of the mobile data services, and/or identifying a user need to use the data services when using mobile applications.

    19. User mobile device according to claim 16, characterized in that the software module contains program instructions implementing the subscriber's confirmation of the offered terms to use the data service package in the visited network.

    20. The hardware and software package containing at least two mobile networks providing the data services, traffic management server implemented with the possibility to distribute traffic, monitor subscriber traffic use prioritizing and manage subscriber access to Internet, at least one user mobile device, characterized in that the traffic management server is configured to perform functions of telecommunication equipment logging, Internet traffic billing between the mobile networks; both the traffic management server and user mobile device are configured with the possibility of joint implementation of all stages of a mechanism of assistance to mobile operators in the provision of data services in the visited mobile network including: identify a mobile subscriber and/or mobile app user; find an opportunity to offer to the mobile subscriber to use a data service package in the visited network; generate the data service package in the visited network and agree it with home and visited operators and third-party services; offer to use the data service package in the visited network on the terms other than standard terms of data services in the visited network; activate the visited network data service package provided to the mobile subscriber on the offered terms; maintain mobile subscriber's use of the visited network data service package provided to the mobile subscriber on the offered terms; deactivate the visited network data service package provided to the mobile subscriber on the offered terms and activate the visited network data service package on standard terms; wherein one of the mobile networks is a home network and the other one is a visited network.

    21. The hardware and software package according to claim 20, characterized in that the traffic management server and/or user mobile device are configured with the possibility to perform identification of the mobile subscriber and mobile app user by searching mobile app user identifiers and binding them to the mobile network identifiers and/or mobile subscriber identity.

    22. The hardware and software package according to claim 20, characterized in that the traffic management server and/or user mobile device are configured with the possibility to find an opportunity to offer the mobile subscriber to use the data service package in the visited network by receiving a tag of mobile subscriber's availability in the visited network, determining a status of the mobile data services, and/or identifying a user need to use the data services when using mobile applications.

    23. The hardware and software package according to claim 20, characterized in that the traffic management server and/or user mobile device are configured with the possibility to perform the mutual settlement between the mobile subscriber, the visited and home networks and third-party services before activation or after deactivation of the visited network data service package provided to the mobile subscriber on the offered terms.

    24. The hardware and software package according to claim 23, characterized in that the traffic management server and/or user mobile device are configured with the possibility to perform the mutual settlement between the mobile subscriber, the visited and home networks and third-party services after the mobile subscriber's confirmation of the offered terms to use the data service package in the visited network.

    25. The hardware and software package according to claim 20, characterized in that the traffic management server and/or user mobile device are configured with the possibility to generate the data service package by defining its parameters and provision conditions.

    26. The hardware and software package according to claim 20, characterized in that the traffic management server and/or user mobile device are configured with the possibility to maintain the mobile subscriber's use of the visited network data service package provided to the mobile subscriber on the offered terms, including sending the mobile subscriber at least one advertising offer.

    Description

    [0026] The claimed invention is shown in the Figures explained below.

    [0027] The FIG. 1 is a block diagram of the hardware and software package according to one of the preferred invention embodiment options. According to this preferred invention embodiment option, the hardware and software package contains two mobile networks providing data services: home mobile network 1 of home mobile operator and visited mobile network 2 of visited mobile operator, system 3 implementing the mechanism of assistance to mobile operators in the provision of data services in the visited mobile network, and user mobile device 4. Visited network 2 is represented by the following interrelated elements: base station 5, base station controller 6 that manages operation of multiple base stations, GPRS (SGSN) subscriber servicing node 7 that implements packet data processing functions GPRS Core network, node 8 of data routing between GPRS Core network and external IP networks (GGSN), in particular with system 3, home mobile subscriber database 9, mobile switch 10 that provides common call and Internet traffic routing. To simplify the block diagram home network 1 is represented by home mobile subscriber database 11 only. System 3 is represented by the following elements: traffic management server 12 that performs traffic distribution, monitoring of subscriber traffic use prioritizing and management of the subscriber access to the Internet as well as in this preferred invention embodiment option provides communications with gateway 13, analyzes information received from mobile subscribers and initiates service-related activities; gateway 13 that provides data routing and mobile network communication with Internet network 14; system 15 of targeting and display of advertising offers for mobile subscribers. The user mobile device 4 contains an installed mobile application 16 with built-in software module 17 implemented according to this invention. System 15 is connected with third-party services 18 (in particular, with advertising platforms) and server 12 is connected with e-payment services 19.

    [0028] FIG. 2 is a block diagram illustrating a preferred invention embodiment option with reference to the technical equipment of the software and hardware package shown in FIG. 1. The diagram shows the following data nodes of the hardware and hardware package: mobile app 16 with built-in software module 17 implemented according to this invention, user mobile device 4 in which the app 16 is installed, visited network 2, traffic management server 12, home network 1, third-party services 18 (in particular, advertising platforms). The illustrated preferred invention embodiment option can be divided into the following successive stages: Block 20Register mobile subscriber in visited network 2; Block 21Identify mobile subscriber (mobile app user); Block 22Find an opportunity to offer to mobile subscriber to use data service package in visited network 2; Block 23Generate data service package in visited network 2 and agree it with home and visited operators and third-party services 18; Block 24Offer to use data service package in visited network on terms other than standard terms of data services in visited network Block 25Activate visited network data service package provided to mobile subscriber on offered terms; Block 26Maintain mobile user's use of visited network data service package provided to mobile subscriber on offered terms; Block 27Deactivate visited network data service package provided to mobile subscriber on offered terms and activate data service package in visited network on standard terms.

    [0029] Initially, system 3 lacks CDR data and/or TAP data, or other data used for traffic billing. At the first stage, mobile subscriber, mobile app user 16 with built-in software module 17 installed on mobile device 4 enters the coverage area of visited network 2, mobile subscriber is automatically registered in visited network 2, wherein at first, request 28 is sent to register in visited network 2 from mobile device user 4, then relevant request 29 is transferred from visited network 2 to home network 1, home network 1 sends relevant confirmation 30 to visited network 2, then relevant confirmation 31 is transmitted to user mobile device 4, and notice 32 of registration in network 2 is sent to traffic management server 12. At the next step (Block 21), mobile subscriber and mobile app user identification procedures 33, 34, 35 are executed both locally in software module 17 and server 12, and exchange 36 of identification data between them, data exchange 37 between user mobile app 16 and third-party services 18, and data exchange 38 between server 12 and third-party services 18 occur. Data exchange 36 and 37 can be performed if mobile data services are deactivated in user mobile device 4 (or data services via Wi-Fi or other comm links using no mobile network are activated). Block 21 procedures perform searching mobile user identifiers and binding them to mobile network IDs and mobile subscriber identity (IMSI/MSISDN), it should be clear as well that the identification procedures can use identification information previously obtained, e. g., when a mobile subscriber was in the home network. At the next stage (Block 22), server 12 sends to visited network 2 a request 39 related to the subscriber's use of data services in the visited network and receives a respective response 40. Then, server 12 sends a request 41 to home network 1 about whether it is possible to offer the use of data service package in visited network 2 on terms other than standard terms of data service in visited network 2 and receives a respective response 42. The next stage (Block 23) includes data exchange procedures 43, 44 and 45 aimed to generate data service package in visited network 2 and agree it with home network 1, visited network 2 and third-party services 18. Then (Block 24), server 12 sends an offer 46 of the generated and agreed data service package in visited network 2 that the user receives, for example, by push notification via the claimed software module. Then (Block 25), 47 and 48 package activation procedures are started up, for example, by changing the packet data network identifier (APN), respective information 49 is sent to traffic management server 12 and activation data 50 is sent from server 12 to visited network 2. At the stage of package use maintenance (Block 26), data transfer 51 between user mobile device 4 and visited network 2 as well as data transfer 52 from user mobile app 16 of visited network 2 take place. Also, server 12 performs data exchange 53 with visited network 2, in particular provides traffic use data to node 8, which is a part of visited network 2, for correct generation of CDR and TAP files, thus allowing to avoid incorrect billing, and exchanges information on data service usage and scope limit, billing, data service quality control, and billing information. Thus, double billing can be avoided, and billing is performed on the terms agreed between the system 3, visited network 2, home network 1 and third-party services 18. Server 12 exchanges data 54 with third-party services 18 to generate advertising offers and sends a mobile subscriber advertising offer data 55. Block 27 performs data exchange 56, 57, 58 to deactivate the data service, package and data exchange 59, 60 and 61 to execute the mutual settlement between the parties. It should be clear that at this stage server 12 can also interact with e-payment services 19 (not shown in FIG. 2).

    [0030] Thus, the claimed invention is the mechanism of assistance to mobile operators in the provision of data services in the visited mobile network, which implementation could ensure achievement of the technical result allowing to involve more mobile subscribers to use data services in the visited mobile network, as well as the mobile app built-in software module, the computer readable medium, the user mobile device and hardware and software package that can implement the stages of this mechanism.

    [0031] You should appreciate that the claimed invention as defined in the attached Claim shall not be compulsorily limited to the specific features and embodiment options described above. On the contrary, the specific features and embodiment options described above are disclosed as the Claim implementation examples but other equivalent features can be covered by the Claim as well.