EP3148157B1 - Verfahren und system zur identifizierung einer zugriffsanforderung einer anwendung auf einer mobilen vorrichtung in einem telekommunikationsnetz - Google Patents

Verfahren und system zur identifizierung einer zugriffsanforderung einer anwendung auf einer mobilen vorrichtung in einem telekommunikationsnetz Download PDF

Info

Publication number
EP3148157B1
EP3148157B1 EP15186238.0A EP15186238A EP3148157B1 EP 3148157 B1 EP3148157 B1 EP 3148157B1 EP 15186238 A EP15186238 A EP 15186238A EP 3148157 B1 EP3148157 B1 EP 3148157B1
Authority
EP
European Patent Office
Prior art keywords
mobile device
network
user interaction
interaction process
user
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Not-in-force
Application number
EP15186238.0A
Other languages
English (en)
French (fr)
Other versions
EP3148157A1 (de
Inventor
Rami Alisawi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Comptel Corp
Original Assignee
Comptel Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Comptel Corp filed Critical Comptel Corp
Priority to ES15186238.0T priority Critical patent/ES2659582T3/es
Priority to PL15186238T priority patent/PL3148157T3/pl
Priority to EP15186238.0A priority patent/EP3148157B1/de
Priority to PCT/FI2016/050632 priority patent/WO2017051069A1/en
Priority to MX2018003460A priority patent/MX2018003460A/es
Priority to US15/762,014 priority patent/US20180248979A1/en
Publication of EP3148157A1 publication Critical patent/EP3148157A1/de
Application granted granted Critical
Publication of EP3148157B1 publication Critical patent/EP3148157B1/de
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/75—Indicating network or usage conditions on the user display
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3438—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment monitoring of user actions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service

Definitions

  • the invention is concerned with a method and system for identifying an application executed on a mobile device to a telecommunication network.
  • Mobile devices such as smart phones, mobile phones, tablet computers, feature phones, computers, smart watches, and other handheld devices or in general any electronic device with processor, UI, input device and radio capability usually allow access to a variety of application programs.
  • Application programs also known as just applications or apps, are usually designed to help users to perform a specific task.
  • the applications communicate over the Internet independently of any other application executed on the mobile device such as a browser, an e-mail program, a Facebook® app, or a Skype® app that communicates independently with a remote server.
  • Such technical features demands intercepting mobile data traffic, which is possible on e.g. user-space application programs, like iptables, which allows a system administrator to configure the tables of rules in devices using the Linux kernel operating system.
  • user-space application programs like iptables, which allows a system administrator to configure the tables of rules in devices using the Linux kernel operating system.
  • the Android operating system for tablet computers and smartphones is based atop the Linux kernel.
  • the iptables program requires rooting the mobile device, which is not feasible for commercial launch, since rooting gives the ability (or permission) to alter or replace system applications and settings, run specialized apps that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user.
  • Another method for intercepting mobile traffic is to make use of Virtual Private Network (VPN) implementations.
  • VPN Virtual Private Network
  • Implementing VPN involves high degree of complexity, introduces limitations, alters the data traffic, and is not user friendly due to VPN setup.
  • Such VPN implementations may also prevent using the key services offered by a VPN connection, which is to connect privately and securely to a site, service or Internet.
  • EP patent application EP 2346211 discloses The list of wireless local area network (WLAN) available to WLAN client device is displayed on the WLAN client device.
  • the WLAN currently connected to client device is displayed first in the list regardless of received signal strength.
  • the list of other WLAN is displayed in decreasing order of received signal strength.
  • US patent application 2014/0214921 mentioned as prior art discloses a solution for allowing identification of mobile applications being executed on a mobile device.
  • a request to execute an application by the mobile device is captured by an agent that generates metadata of the application and identifies the internet resource destination. All requests captured by the agent are forwarded to a proxy server or sent directly to their destination.
  • the solution is constructed to follow up applications executed via an established internet connection in order to help application developers in identifying the type of applications executed on mobile phones since they are interested in e.g. determining which of their applications have been accessed versus the applications of their competitors.
  • US patent application 2012/0254285 discloses a method for management of communication from a mobile device capable of multitasking.
  • the method includes an agent, which captures a request from at least one application executed on the mobile device for data communication through a network interface of the mobile device.
  • the application is identified and the access rights of the identified application are determined.
  • the agent is responsible to communicate with the network interface.
  • the solution is constructed to follow up applications executed via an established internet connection in order to manage and reduce the amount of data and bandwidth.
  • the methods require capturing and forwarding or re-routing the traffic.
  • the task of identifying the type of applications on a mobile device requires e.g. mapping of each packet opened to the Process Identifier (Process ID), a number used by most operating system kernels to uniquely identify an active process. This number may be used as a parameter in various function calls allowing processes to be manipulated.
  • Process ID Process Identifier
  • the invention is concerned with a method of identifying access request of an application on a mobile device in a telecommunication network.
  • the method comprises steps as performed by an agent in the mobile device.
  • On-going processes in the mobile device are detected with respect to detecting one or more of the on-going processes to involve traffic over the telecommunication network.
  • a user interaction process is identified from all the on-going processes. It is then confirmed that the identified user interaction process is the same as said process that involves traffic over the telecommunication network. Information of the identified user interaction process is then collected regarding network access needs.
  • the user interaction with the process/application's interface might require generation of traffic over the telecommunication network. Therefore, the process is preferably monitored and analyzed with respect to factors to evaluate network access needs.
  • the system of the invention comprises an agent in a mobile device with means for performing the steps of the method of the invention.
  • the invention can successfully be used to generate a real-time trigger for contextual data access offers without actually intercepting the traffic, but rather monitoring different processes in a mobile device including incoming and outgoing traffic and communication.
  • the monitoring is an on-going processes, wherein additional steps will be taken when a foreground process in a mobile device attempts for network access while the user is interacting with an application.
  • An agent monitors e.g. byte and/or packet counts, radio state, data flow (or data activity), foreground processes and optionally device screen state and filters out any background data that is not based on user interactions.
  • the method may be enhanced by analyzing the device screen state and performing the method only when the mobile device screen is on.
  • Network access can be provided and the invention is in the first hand meant for offering a connection of the mobile device to the Internet or to a specific application or group of applications or service to the Internet by requiring the user to pay for the connection as a condition for providing the access.
  • the technology of the invention can be used to present advertisements, offer sponsored data or collect application analytics.
  • a third party may e.g. sponsor or pay a specific Internet application or Internet service when a user tries to access it, or when the user performs a certain action, like for example clicking on a link, watching a video or downloading an application as required by the third party.
  • the Internet uses the standard Internet protocol suite comprising the Transmission Control Protocol (TCP) and the Internet protocol (IP) to interconnect computers and computer networks worldwide.
  • TCP Transmission Control Protocol
  • IP Internet protocol
  • OSI Model Open Systems Interconnection model
  • the original version of the model defines seven layers, consisting of three media layers and four host layers, i.e. the 1) the physical layer (communicating with bits over a physical medium), 2) the data link layer (transmission of bits/data frames between two nodes), 3) the network layer (managing packets and datagrams including addressing, routing and traffic control), (examples IPv4, IPv6, IPsec, AppleTalk), 4) the transport layer protocols (reliable transmission of data segments between points on a network) (examples TCP, UDP), 5) the session layer (managing data in communication sessions, i.e.
  • the presentation layer (translation of data between a networking service and an application; including character encoding, data compression and encryption/decryption), and 7) the application layer (High-level APIs, like HTTP FTP, SMTP, Secure Shell).
  • IP Internet Protocol
  • IP has the task of delivering packets, where data is formatted into packets (instead of bit streams), and having a payload with user data and a header for control information, from a source to a destination solely based on the IP addresses in the packet headers.
  • the monitoring operation in the invention notes the size of and counts the number of IP packets, and works on the network layer (OSI layer 3). It is not dependent on any layer above it since it does not read or parse the payload, so it will work for all the transport layer protocols (e.g. TCP, UDP in OSI layer 4). It is also agnostic to and works for application layer protocols (e.g. HTTP, HTTPS, FTP, SMTP in OSI layer 7), and naturally all other layers above it. Naturally, the detection is not dependent on the process or application content or payload.
  • byte count or packet count monitored in the invention is meant a measure of the quantity of the traffic going out from the mobile device. Also inbound traffic can be monitored. Usually quantity is measured, but also packet loss rate could be followed. The byte count or packet count also shows the number of bytes or packets having been sent in total at a given point or interval of time. The total byte count is what is followed in the first hand in the invention.
  • the radio state and/or the data activity of the on-going process is monitored.
  • the radio state is monitored in the invention to detect if the device is sending out data to the network on OSI layer 3 (the network layer), i.e. if any traffic is generated to the network at all.
  • the data activity is associated with a given process or all processes, i.e. if a given process or some of the processes produce(s) data to the network on OSI layer 7 (the application layer).
  • the data sent out based on the monitored radio state and data activity can then be used to identify if one or more of the on-going processes involves traffic over the telecommunication network. This can be identified by means of the data activity only.
  • the radio state is monitored to identify any activity and state of the modem in the mobile device that modulates signals for transmitting over the network.
  • the change in the state indicates that the mobile device is transmitting data. It is an indication of the uplink or downlink traffic taking (to or from the mobile device). Monitoring both of these indications, and listening if either one takes place, will secure that any traffic can be detected with high reliability and with minimal latency.
  • Monitoring the mobile radio state and data activity can be an indication of uplink or downlink traffic and/or about packet access technology of the radio.
  • radio communication technology e.g. UMTS / 3G (Universal Telecommunications System/3rd generation), HSDPA (High-Speed Data Packet Access) or 4G (4 th generation).
  • the agent also monitors whether the process in the mobile device is a foreground or background process.
  • a process that is currently accepting input from the user of the mobile device is called a foreground process so it is the program that the user is interacting with at the present time (for example, data entry).
  • a background process is a computer process that runs "behind the scenes" (i.e. in the background) and without direct user intervention. Typical tasks for these processes include logging, system monitoring, scheduling, and user notification. Also the user initiated processes that the user is not currently interacting with are considered background processes.
  • the different programs can be in the foreground at different times because all processes, after using all of their execution time in foreground, are moved to background.
  • the screen state may be monitored in the invention, i.e. whether the screen is on or off. If the screen is off, it can be assumed that there is no on-going foreground process taking place.
  • the screen of the mobile device is the user interface, for human-machine interaction, and is the space where interactions between humans and machines occur.
  • the screen has a display as an output device for presentation of information. On display screens, the foreground consists of the characters and pictures that appear on the screen.
  • Mobile devices usually have a feature that allows showing a list of running process in the mobile device.
  • the tasklist command displays a list of applications and services for all tasks running on the computer and different factors can be monitored e.g by means of Task Manager used to monitor a computer's performance that shows the programs, processes, and services that are currently running on a computer.
  • Task Manager is included with Microsoft Windows systems and provides limited information about e.g. computer performance and running applications, processes, network activity and statistics, logged-in users, and system services.
  • the ps command In Linus and UNIX, which are other operating systems, the ps command is used. It provides information about the currently running processes, including their process identification numbers (PIDs). Both Linux and UNIX support the ps command to display information about all running process. The ps command gives a snapshot of the current processes.
  • the 'toolbox' command encapsulates the functionality of many common Linux commands, such as the ps command.
  • the toolbox versions of this command has less functionality than its full-sized Linux counterpart.
  • other task manager applications for Android exist, which can be used via different Activity Manager functions that interact with the overall activities running in the system, such as:
  • Figures 1a -1e constitute an architectural view of the telecommunication network environment in which the invention can be implemented.
  • FIG. 1e The architectural view of the environment in which the invention can be implemented is according to figures 1a - 1e a client-server architecture, which is a telecommunication network architecture, wherein one or more mobile devices 1 (only one shown) are clients and reference number 2 is a server responsible for connecting an agent in the mobile device to the mobile network.
  • the mobile device 1 is in communication with the server 2 over the operator radio network 8 and further through the Internet 10.
  • the operator network 8 is a cellular radio network, which is a mobile network or wireless network distributed over land areas called cells, each served by at least one fixed-location transceiver, known as base station 11.
  • the Internet 10 is a global system of interconnected computer networks that use the Internet protocol suite (Transmission Control Protocol / Internet Protocol, TCP/IP).
  • TCP/IP Transmission Control Protocol / Internet Protocol
  • An operator server 9 is connected to those network components responsible for managing network connections for the services, offered by a service provider, which the users of the mobile devices 1 are using.
  • the operator server 9 is also connected to other components in the mobile network 8, e.g. components handling Policy Control and Charging (PCC), Customer Relationship Management (CRM), Subscriber Profile Management (SPR), Policy and Charging Rules Function (PCRF) and Online Charging System (OCS).
  • PCC Policy Control and Charging
  • CRM Customer Relationship Management
  • SPR Subscriber Profile Management
  • PCRF Policy and Charging Rules Function
  • OCS Online Charging System
  • the server 2 can also be part of the mobile network 8. Then the connection between the server 2 and the mobile device 1 can directly be connected through the mobile network 8. In that situation, the server 2 can also act as the operator server 9.
  • a mobile network operator or MNO provides the services of wireless communications to the mobile device 1 over the mobile network 8 including e.g. radio spectrum allocation, wireless network infrastructure, and back haul infrastructure (the portion of the network comprising the intermediate links between the core network, or backbone network).
  • the mobile device 1 has access to the Internet via the mobile network 8.
  • the base station 11 connects directly to the mobile network 8, which is both the internet service provider and a mobile phone operator or wireless provider that provides services for mobile phone users.
  • the mobile phone operator gives a SIM card to the user of the mobile phone, who inserts it into the mobile phone to gain access to the cellular network 8.
  • the mobile device 1 uses a modem to communicate over the radio network 8 and the Internet 10.
  • the modem modulates signals to encode digital information and demodulates signals to decode the transmitted information.
  • the modulated signal is transmitted easily over the networks and is decoded to reproduce the original digital data.
  • the modem inside the mobile device 1 uses the radio network 8 (which can be e.g. General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), High-Speed Packet Access (HSPA), Evolution-Data Optimized (EVDO), or Worldwide Interoperability for Microwave Access (WiMax).
  • GPRS General Packet Radio Service
  • UMTS Universal Mobile Telecommunications System
  • HSPA High-Speed Packet Access
  • EVDO Evolution-Data Optimized
  • WiMax Worldwide Interoperability for Microwave Access
  • the faster data rates of the newest wireless modem technologies are also considered to be broadband wireless modems.
  • mobile broadband modems can be SIM locked to a particular network provider.
  • Reference numbers 12 and 13 represent services that can be accessed via the Internet 10.
  • reference number 12 is Facebook, which is an online social networking service, in which after registering to use the site, users can create a user profile, add other users as "friends", exchange messages, post status updates and photos, share videos and receive notifications when others update their profiles.
  • Reference number 13 is Twitter, which is another online social networking service that enables users to send and read short 140-character messages called "tweets”. Registered users can read and post tweets, but unregistered users can only read them. Users can access Twitter through the website interface, SMS, or a mobile device app.
  • Figure 1 a shows a "data-off" situation, wherein the mobile network operator has blocked all internet traffic and there is no connection from the mobile device 1 to Facebook 12 or Twitter 13 or any other internet service.
  • the dotted bidirectional arrow 14 shows that there is an available connection from the mobile device 1 to the server 2 in the form of e.g. a subscription and the dotted bidirectional arrow 15 shows that there is an available connection further to the operator server 9 from the server 2.
  • the dotted bidirectional arrow 15 shows that there is an available connection further to the operator server 9 from the server 2.
  • Applications are installed for running in the mobile device 1.
  • the applications might require generation of traffic over the telecommunication network.
  • Figure 1b shows a situation, wherein such an application in the mobile device 1 attempts for network access, while the user is interacting with that specific application, i.e. the Facebook app 12', which is installed in the mobile device as shown by reference number 12'.
  • the user interaction with the process/application's interface 12' is here assumed to require generation of traffic over the telecommunication network and the application therefore attempts to transfer data to the network.
  • the interaction generates radio traffic to the base station, which is indicated by the bidirectional arrow 17.
  • the processes and traffic of the applications running on the mobile device 1 is monitored and analyzed with respect to factors to evaluate network access needs by a client-side software agent running on the mobile device 1.
  • the agent in the mobile device 1 detects that there is one or more of the on-going processes that involve traffic over the telecommunication network, the process name is identified in a way described in figure 3 or figure 4 and the agent also selects offers for network access.
  • the mobile device 1 then presents the offer(s) on the screen of the mobile device 1.
  • the agent After the user of the mobile device 1 has accepted an offer, it is forwarded to the server 2 as a purchase request and the agent asks the server to turn data between the mobile device 1 and the requested service on (i.e. to open the internet connection between them).
  • the communication between mobile device 1 and the server is indicated by the bidirectional arrow 16.
  • the server 2 also asks the operator server 9 to make additional modifications to user information (for example in PCC, CRM, SPR, PCRF) based on the offer selected.
  • the network 8 still blocks the internet traffic to Facebook 12, which is indicated by the dotted arrow 18 between Facebook 12 and the mobile device 1.
  • Figure 1c shows a situation, wherein the server 2 approves the purchase request and instructs the operator server 9 to open the internet connection between the mobile device 1 and the requested service 12 and to turn on other functions of the procedures they need to take.
  • This communication between the server 2 and the operator server 9 is indicated by the bidirectional arrow 19.
  • the operator server 9 turns the internet connection between the mobile device 1 and the requested service 12 on and this opened connection is indicated by the bidirectional arrow 20.
  • this opened connection is indicated by the bidirectional arrow 20.
  • an internet connection can be created also to other individual services, e.g. to Twitter 13, or e.g. to allow all internet traffic to any services, including potentially access with specific Quality Of Service (QoS) parameters.
  • QoS Quality Of Service
  • Figure 1e shows a situation, wherein internet traffic to the service requested by the application in the mobile device 1 is still enabled but as only control communication with the server 2 is needed, there is no need for constant communication between the agent on the mobile device 1 and the server 2, or between the server 2 and the operator server(s) 9, hence the communication is done for control purposes, similar to that of the situation before creating the connection to internet service(s) 12 (and 13), which is indicated with control connection dotted lines 14 and 15 respectively.
  • Figure 2 presents the functional blocks in the mobile device 1 belonging to the telecommunication network used in the method and system of the invention.
  • the mobile device 1 is presented by reference number 1 and the server 2 with reference number 2 as in figures 1a - 1e .
  • the mobile device 1 of the invention has an agent running in the mobile device 1.
  • the agent is configured to monitor (follow-up) all communications to and from any of the applications in the mobile device 1 to any Internet resources by taking snapshots of all on-going processes and data communication taking place in the mobile device 1. Thus, all communication to and from any of the applications is monitored via the agent.
  • the agent is communicatively connected to the server 2.
  • the agent maybe an application installed on the mobile device 1 and executed thereon.
  • the agent can note a request to access an Internet resource by some of the other applications on the mobile device 1.
  • the agent does, however, not intercept (capture, analyse, or send forward) the traffic.
  • the functionality of the agent is divided over different modules 3, 4, 5 and 6 performing the detecting, identifying, analyzing and mapping an identified user interaction process and finally selecting one or more of available network access offers and presenting them on the screen of the mobile device.
  • the modem is not part of the agent, but the agent uses the modem to contact the network.
  • the mobile device 1 When the mobile device 1 sends a resource or process request to the server 2 through the net service 7 over the network connection, it is then processed and the requested access rights are granted or denied for the mobile device 1 as presented in connection with figures 1a - 1e .
  • the processes and traffic of the applications running on the mobile device 1 is monitored and analyzed with respect to factors to evaluate network access needs by the client-side software agent running on the mobile device 1.
  • the data sensor 3 of the agent in the mobile device 1 monitors on-going processes in the mobile device 1 and detects them with respect to factors as network traffic, byte/packet counts, radio state, flows in data activity, foreground processes and screen state as was explained in the summary section.
  • the on-going process is a user interaction process and determine whether it is a process for network communication needing internet access and find the type of process and process name, e.g. if it is a browser, an e-mail program, a Facebook® app, a Skype® app, etc.
  • the data sensor 3 then communicates the process/application name to other modules in the mobile device 1 and/or in the agent.
  • One of the destination modules is the User Interface Manager 4 to which the name of the user interaction process is sent.
  • the data sensor 3 can be used by other applications as well.
  • the offer manager 5 After that the data sensor 3 has identified the user interaction process for generating the data, the offer manager 5 will decide next steps.
  • the offer manager 5 will thus know the name of the traffic generating the user interaction process from the data sensor 3. After that the offer manager 5 analyses the process in question, e.g. with respect to historical click through rates and use/purchase of that process for this user, other previous information of the history of the process, and other factors that will impact the decision on whether to show or not to show an offer for the user and which offer. Additionally, the user context and the history of that user to that process with respect to earlier behavior will impact on the decision whether an offer is to be made. Finally, the result of the analysis is mapped to suitable available offers stored in the database 6 and the offer manager 5 then selects the best offer(s) to allocate.
  • the offers are offers for internet access but could also include offers for downloading an app (which would require connectivity) or consume content (if it is promoted etc.) or serve an advertisement and being in the form of e.g. a banner, picture, video, or audio.
  • the offer manager 5 retrieves the selected offers from the database 6 and presents them to the User Interface (UI) Manager 4.
  • UI User Interface
  • the UI manager 4 presents the selected offers to the user to select and buy an offer. If the user chooses one of the shown offers, the User Interface Manager 4 will push the purchase request to the Net Service module 7 where it gets forwarded to the server 2.
  • the Net Service module 7 is responsible for forwarding user requests to the server.
  • the user requests can for example be about, querying balance or submitting purchase orders.
  • the Net Service module 7 is also responsible for requesting new offers from the server 2, or receiving and handling the offers pushed by the server 2.
  • the Net Service module 7 saves the new offers to the database 6.
  • the Net Service module 7 is also responsible for removing obsolete offers from the database 6.
  • the Server 2 provides offers and communicates with the operator network to activate an internet connection, once the user has made a successful purchase.
  • FIG. 3 is a detailed flow scheme of an embodiment of the invention.
  • step 1 a mobile device is powered on by a user (or wherein the mobile device is booted) upon which the screen of the mobile device is turned on and some processes in the mobile device are started automatically.
  • an agent in the mobile device takes a snapshot of the on-going processes of the mobile device and stores the snapshot as a data activity state of the processes in the mobile device at this particular point in time.
  • the snapshot describes a situation of a data activity moment of the on-going processes in the mobile device and is stored in an in-memory database (IMDB) of the mobile device.
  • IMDB in-memory database
  • step 3 the agent monitors the data activity and the radio state of the on-going process(es).
  • a user initiates an app in the mobile device, whereby a user interaction starts.
  • step 4 on the basis of data activity and/or radio state, it is identified whether the on-going process involves traffic over the telecommunication network. It is identified on the basis of the radio state and/or data activity whether the process in the mobile device is cellular and uses a mobile or wireless network served by at least one fixed-location transceiver (a base station) and/or whether it is Internet traffic (such as Wifi) or whether there is no communication with a network at all.
  • UMTS/3G Universal Telecommunications System/3rd generation
  • HSDPA High-Speed Data Packet Access
  • 4G 4 th generation
  • radio state of the mobile device is low (RRC_IDLE (in 4G), RRC_IDLE and PCH as LOW (in 3G) for example), the agent continues monitoring in step 3. If the radio state of the mobile device is high (RRC_CONNECTED (in 4G), RRC_DCH (HSDPA, HSPAP) and FACH as HIGH (in 3G) for example), the on-going process is identified to involve traffic over the telecommunication network.
  • the agent then continues monitoring on the radio state and data activity starts the identification of the active on-going process, which either can be generated by the mobile device automatically or it can be a user generated process or a user interaction process.
  • the Radio Resource Control (RRC) protocol belongs to the Universal Mobile Telecommunication System, Wideband Code Division Multiple Access (W-CDMA (UMTS)) stack and handles the control plane signalling of Layer 3 between the User Equipment (UE) and the UMTS Terrestrial Radio Access Network (UTRAN).
  • RRC Radio Resource Control
  • the major functions of the RRC protocol include connection establishment and release functions, broadcast of system information, radio bearer establishment, reconfiguration and release, RRC connection mobility procedures, paging notification and release and outer loop power control.
  • connection establishment and release functions include connection establishment and release functions, broadcast of system information, radio bearer establishment, reconfiguration and release, RRC connection mobility procedures, paging notification and release and outer loop power control.
  • the RRC configures the user and control planes according to the network status and allows for Radio Resource Management strategies to be implemented.
  • step 5 the identification of a user interaction process is started. First it is stated whether there is an on-going user interaction process, which is queryable.
  • the user interaction process can be identified directly from the snapshot and the process continues with step 7.
  • An indication of this in e.g. an Android device can be that the ActivityManager.RunningServicelnfo, which gives information of the running processes, has a FLAG_FOREGROUND set on to indicate if it is a foreground process that the user is interacting with.
  • step 6 a list of all running processes in the mobile device is queried in step 6. This can be done with e.g. the windows command, the UNIX or LINUX ps command or some Android command as was explained in the summary section.
  • step 6 involves foreground process identification.
  • the foreground process identification network comprises detection of the user interaction process.
  • An indication of a user interaction process is for example an uplink network packet is sent from the mobile device in attempting network access.
  • step 7 the identified user interaction process is queried for additional information, for example detection of values for byte count detection, and/or packet count. This one is done directly if the process is queryable. If it is not queryable, then the information is gathered by for example taking a new snapshot of all the ongoing processes.
  • step 8 the packet or byte count of the on-going identified user interaction process is queried from the stored snapshot.
  • step 9 it is stated whether the (total) packet or byte count value is bigger than the one in the stored snapshot.
  • a new snapshot is stored as a situation report of a data activity moment of the process as in step 2, since this is an ongoing process, and the user could at some point switch on using some other application which might not have a specific network access offer.
  • step 10 If this is the case, then the process continues in step 10. If the identified user interaction process data flow or activity has not increased, the process returns to step 4 to monitor data activity and/or radio state.
  • step 10 it is stated whether the identified user interaction process is in a list of processes decided to be ignored in the method.
  • step 11 If it is not in the list, then it is stated in step 11 whether the user interface process has been processed already.
  • step 13 the process name and information is broadcasted to other systems.
  • one of the receiving systems is User Interface Manager 4 for processing and selecting offers for network access.
  • FIG. 4 is a detailed flow scheme of an other embodiment of the invention.
  • Steps 1 - 4 of figure 4 are equal to steps 1 - 4 of figure 3 .
  • step 5 a new snapshot of the on-going processes of the mobile device are obtained and stored.
  • step 6 it is stated whether there are processes with packet or byte count values in the new snapshot that are bigger than the ones in the snapshot stored in step 2.
  • step 8 the identification of a user interaction process is started.
  • an on-going user interaction process which is queryable like in step 5 of figure 3 .
  • One indication of this in e.g. an Android operating system can be that the ActivityManager.RunningServicelnfo, giving information of the running processes, has a FLAG_FOREGROUND set on to indicate if it is a foreground process that the user is interacting with.
  • step 9 If the process is not queryable, the process continues with step 9.
  • step 9 a number of processes from the top of the list of all running processes is detected.
  • the number of processes can be for example related to the number of processes known to be started by the user. These processes can also be chosen from those processes where the foreground flag has been turned on recently or which have been started recently.
  • step 10 it is stated whether there is more than one process.
  • the one with the maximum generated traffic is selected in step 11 and the name of the networking service that the user is trying to access in the user interaction process is identified.
  • step 10 If it is stated in step 10, that there is only one process, the method continues directly in step 12.
  • step 8 If it was stated in step 8 that there was a queryable user interaction process, it can be identified directly and the process continues with step 12.
  • step 12 it is stated whether the identified user interaction process is in the list of processes requiring access.
  • step 13 the user interaction process is marked on the list of processes requiring access created in step 7.
  • step 14 the list of process names and information is broadcasted to other systems.
  • one of the receiving systems is User Interface Manager 4 for processing and selecting offers for network access.
  • the ability to show offers and sell data upon opening apps with data consumption is a useful approach in the invention.
  • Network access can be provided and the invention is in the first hand meant for offering connecting the mobile device to the Internet.
  • Figure 5 shows an example of a signal diagram for such a scenario.
  • the Net Service Module 7 of the mobile device 1 requests offers from the server 2 in signal 1.
  • the Server 2 sends the current offers to the Net Service Module 7.
  • the Net Service module 7 stores the offers to the database 6 after that an application in the mobile device 1 has attempted for network access while the user is interacting with the application.
  • step 4 the data sensor of the agent monitors the data activity of the on-going process in the mobile device, detects the on-going process to be a user interaction process, identifies the user interaction process to involve traffic over the telecommunication network, and analyzes the identified user interaction process with respect to the name of the process and factors for network access needs.
  • the data sensor of the agent monitors the data activity of the on-going process in the mobile device, detects the on-going process to be a user interaction process, identifies the user interaction process to involve traffic over the telecommunication network, and analyzes the identified user interaction process with respect to the name of the process and factors for network access needs.
  • the process name is sent to the User Interface Manager 4 in signal 5 and further to the offer manager 5 in signal 6 for processing and selecting offers for network access.
  • the offer manager 5 fetches the stored offers from the database 6 for mapping in step 9, the analyzed network access needs, (which are analysed from the process name and other information like the data profile of that process, and/or contextual and historical user/usage information that has been stored to database from the server, net service and the offer manager), to available offers stored in a database, and for selecting one or more of the available network access offers.
  • the offer manager presents them to the User Interface Manager (UI) 4 in signal 10.
  • UI User Interface Manager
  • the UI manager 4 presents the offer(s) on the screen of the mobile device in step 11.
  • the UI manager pushes the selected purchase request of that offer to the Net Service module 7 in signal 12 where it gets forwarded to the server 2 in signal 13.
  • the Net Service module 7 is responsible for making requests to server.
  • step 14 the server 2 approves the purchase request and sends instructions to all the appropriate components.
  • these components include for example a charging entity, gateways, a Subscriber Profile Repository (SPR), the Policy and Charging Rules Function (PCRF), and Customer relationship management (CRM).
  • SPR Subscriber Profile Repository
  • PCRF Policy and Charging Rules Function
  • CRM Customer relationship management

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Computing Systems (AREA)
  • Computer Hardware Design (AREA)
  • Mathematical Physics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Claims (23)

  1. Verfahren zur Identifizierung einer Zugriffsanforderung einer Anwendung (12') auf einer mobilen Vorrichtung (1) in einem Telekommunikationsnetz (8, 10), wobei das Verfahren die folgenden Schritte aufweist, die von einem Agenten in der mobilen Vorrichtung durchgeführt werden, gekennzeichnet durch
    a) Erfassen, ob einer oder mehrere laufende Prozesse in der mobilen Vorrichtung Datenverkehr über das Telekommunikationsnetz einbeziehen,
    b) Identifizieren eines Benutzerinteraktionsprozesses aus allen laufenden Prozessen,
    c) Bestätigen, dass der identifizierte Benutzerinteraktionsprozess der Prozess ist, der Datenverkehr über das Telekommunikationsnetz einbezieht, und
    d) Sammeln von Informationen über den identifizierten Benutzerinteraktionsprozess bezüglich Netzzugriffsanforderungen.
  2. Verfahren nach Anspruch 1, ferner gekennzeichnet durch
    e) Analysieren des identifizierten Benutzerinteraktionsprozesses in Bezug auf Faktoren für Netzzugriffsanforderungen,
    f) Abbilden der analysierten Netzzugriffsanforderungen auf verfügbare Angebote, die in einer Datenbank gespeichert sind, und
    g) Auswählen eines oder mehrerer der verfügbaren Netzzugriffsangebote und Darstellen dieser auf dem Bildschirm der mobilen Vorrichtung.
  3. Verfahren nach Anspruch 1 oder 2, dadurch gekennzeichnet, dass dem Erfassen in Schritt a) ein Aufnehmen eines Schnappschusses der laufenden Prozesse der mobilen Vorrichtung und Speichern des Schnappschusses als Situationsbericht eines Moments der Datenaktivität der Prozesse folgt.
  4. Verfahren nach Anspruch 1, 2 oder 3, dadurch gekennzeichnet, dass, bei der Erfassung des Datenverkehrs des Netzes von Schritt a), identifiziert wird, ob der laufende Prozess, der in der mobilen Vorrichtung stattfindet, ein Telefonnetz und/oder das Internet oder ein anderes Datennetz verwendet.
  5. Verfahren nach Anspruch 1, 2, 3 oder 4, dadurch gekennzeichnet, dass die Erfassung des Datenverkehrs des Netzes von Schritt a) durch Überwachen des Funkzustands und/oder der Datenaktivität des laufenden Prozesses in der mobilen Vorrichtung durchgeführt wird.
  6. Verfahren nach Anspruch 5, dadurch gekennzeichnet, dass die Erfassung der Datenaktivität eine Erfassung, dass der Benutzerinteraktionsprozess ein Aufwärtsstrecken-Netzpaket von der mobilen Vorrichtung sendet, um einen Netzzugriff zu versuchen, aufweist.
  7. Verfahren nach Anspruch 3, dadurch gekennzeichnet, dass die Benutzerinteraktionsidentifikation in Schritt b) direkt aus dem Schnappschuss identifiziert wird, wenn der in den Benutzerinteraktionsprozess einbezogene Netzdienst abfragbar ist.
  8. Verfahren nach Anspruch 1, 2, 3, 4, 5, 6 oder 7, gekennzeichnet durch Identifizieren eines in den Benutzerinteraktionsprozess einbezogenen Netzdienstes unter Verwendung einer Liste eines laufenden Prozesses und Erfassen einer Anzahl von Prozessen von oben auf der Liste und Auswählen desjenigen mit dem maximalen generierten Datenverkehr.
  9. Verfahren nach Anspruch 5, dadurch gekennzeichnet, dass die Benutzerinteraktionsidentifikation in Schritt b) eine Vordergrundprozessidentifikation einbezieht.
  10. Verfahren nach Anspruch 8 oder 9, ferner gekennzeichnet durch Identifizieren des Namens des Netzdienstes, auf den der Benutzer versucht, im Benutzerinteraktionsprozess zuzugreifen.
  11. Verfahren nach Anspruch 1, 2, 3, 4, 5, 6, 7, 8, 9 oder 10, gekennzeichnet durch Ignorieren eines identifizierten Benutzerinteraktionsprozesses, wenn er sich auf einer Liste von Prozessen befindet, über die entschieden wurde, in dem Verfahren ignoriert zu werden.
  12. Verfahren nach Anspruch 1, 2, 3, 4, 5, 6, 7, 8, 9 oder 10, gekennzeichnet durch Ignorieren eines Benutzerinteraktionsprozesses, der erfasst wurde, bereits verarbeitet zu sein.
  13. Verfahren nach Anspruch 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 oder 12, gekennzeichnet durch Abfragen des Paket-oder Byte-Zählwerts des laufenden identifizierten Benutzerinteraktionsprozesses.
  14. Verfahren nach Anspruch 13, dadurch gekennzeichnet, dass die Bestätigung in Schritt c) durch Vergleichen des abgefragten Paket- oder Byte-Zählwerts und des entsprechenden Werts in dem gespeicherten Schnappschuss erfolgt.
  15. Verfahren nach Anspruch 14, ferner gekennzeichnet durch Entscheiden, den Benutzerinteraktionsprozess zu verarbeiten, wenn der abgefragte Paket- oder Byte-Zählwert größer als der in dem gespeicherten Schnappschuss ist.
  16. Verfahren nach Anspruch 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14 oder 15, dadurch gekennzeichnet, dass das Analysieren ferner durch Analysieren des Benutzungskontextes und/oder Benutzerverhaltens in Verbindung mit dem identifizierten Netzdienst als Faktoren, die eine Entscheidung über die Art des Netzzugriffsangebots beeinflussen, durchgeführt wird.
  17. Verfahren nach Anspruch 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 oder 16, dadurch gekennzeichnet, dass das Netzzugriffsangebot in Form eines Echtzeit-Triggers auf dem Bildschirm der mobilen Vorrichtung realisiert wird.
  18. Verfahren nach Anspruch 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16 oder 17, dadurch gekennzeichnet, dass das Verfahren ferner aufweist
    h) der Benutzer akzeptiert ein zugewiesenes Angebot über den Bildschirm, und
    i) die Anwendung sendet, für Aktivierungs- und Ladezwecke, die Information des akzeptierten Netzzugriffsangebots an den Betreiber des Abonnements der mobilen Vorrichtung.
  19. Verfahren nach Anspruch 18, dadurch gekennzeichnet, dass, wenn der Benutzer das Angebot in Schritt h) akzeptiert hat, der Netzzugriff für den Benutzer unter der Bedingung bereitgestellt wird, dass eine bestimmte Benutzeraktion auf der mobilen Vorrichtung durchgeführt wird, wobei erforderlich ist, dass die Benutzeraktion als eine spezifizierte Benutzeraktion auf der Vorrichtung durchgeführt wird, die darin besteht, für den Netzzugriff zu bezahlen, auf einen Link zu klicken, ein Video anzusehen, oder eine App herunterzuladen.
  20. System zum Identifizieren einer Zugriffsanforderung einer Anwendung (12') auf einer mobilen Vorrichtung (1) in einer Telekommunikation (8,10), wobei das System einen Agenten in einer mobilen Vorrichtung aufweist, der Mittel aufweist zum
    dadurch gekennzeichnet
    Erfassen, ob einer oder mehrere der laufenden Prozesse Datenverkehr über das Telekommunikationsnetz einbeziehen,
    Identifizieren eines Benutzerinteraktionsprozesses von allen laufenden Prozessen,
    Bestätigen, dass der identifizierte Benutzerinteraktionsprozess der Prozess ist, der Datenverkehr über den Datenverkehr über das Telekommunikationsnetz einbezieht, und
    Sammeln von Informationen über den identifizierten Benutzerinteraktionsprozess bezüglich Netzzugriffsanforderungen.
  21. System nach Anspruch 20, ferner gekennzeichnet durch Mittel zum
    Analysieren des identifizierten Benutzerinteraktionsprozesses in Bezug auf Faktoren für Netzzugriffsanforderungen,
    Abbilden des analysierten Netzzugriffs auf verfügbare Angebote, die in einer Datenbank gespeichert sind, und,
    Auswählen eines oder mehrerer verfügbarer Netzzugriffsangebote und Darstellen dieser auf dem Bildschirm der mobilen Vorrichtung zur Auswahl durch den Benutzer für eine Netzverbindung.
  22. System nach Anspruch 21, dadurch gekennzeichnet, dass die Mittel in dem Agenten einen Datensensor aufweisen, der einen Algorithmus aufweist zum Detektieren eines Benutzerinteraktionsprozesses in der mobilen Vorrichtung, zum Identifizieren des Benutzerinteraktionsprozesses, um Datenverkehr über das Telekommunikationsnetz einzubeziehen, zum Bestätigen, dass der identifizierte Benutzerinteraktionsprozess der Prozess ist, der Datenverkehr über den Datenverkehr des Telekommunikationsnetzes einbezieht, und zum Sammeln und Analysieren von Informationen des Benutzerinteraktionsprozesses bezüglich Faktoren für Netzzugriffsanforderungen.
  23. System nach Anspruch 22, dadurch gekennzeichnet, dass die Mittel in dem Agenten einen Angebotsmanager aufweisen, der Software aufweist zum Abbilden der analysierten Netzzugriffsanforderungen auf verfügbare Angebote, die in einer Datenbank gespeichert sind, und
    zum Auswählen eines oder mehrerer der verfügbaren Netzzugriffsangebote und Darstellen von diesen auf dem Bildschirm der mobilen Vorrichtung.
EP15186238.0A 2015-09-22 2015-09-22 Verfahren und system zur identifizierung einer zugriffsanforderung einer anwendung auf einer mobilen vorrichtung in einem telekommunikationsnetz Not-in-force EP3148157B1 (de)

Priority Applications (6)

Application Number Priority Date Filing Date Title
ES15186238.0T ES2659582T3 (es) 2015-09-22 2015-09-22 Procedimiento y sistema de identificación de una petición de acceso de una aplicación en un dispositivo móvil en una red de telecomunicación
PL15186238T PL3148157T3 (pl) 2015-09-22 2015-09-22 Sposób i system identyfikowania żądania dostępu aplikacji na urządzeniu mobilnym w sieci telekomunikacyjnej
EP15186238.0A EP3148157B1 (de) 2015-09-22 2015-09-22 Verfahren und system zur identifizierung einer zugriffsanforderung einer anwendung auf einer mobilen vorrichtung in einem telekommunikationsnetz
PCT/FI2016/050632 WO2017051069A1 (en) 2015-09-22 2016-09-13 Method and system of identifying an access request of an application on a mobile device in a telecommunication network
MX2018003460A MX2018003460A (es) 2015-09-22 2016-09-13 Metodo y sistema de identificacion de una solicitud de acceso de una aplicacion en un dispositivo movil en una red de telecomunicaciones.
US15/762,014 US20180248979A1 (en) 2015-09-22 2016-09-13 Method and system of identifying an access request of an application on a mobile device in a telecommunication network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP15186238.0A EP3148157B1 (de) 2015-09-22 2015-09-22 Verfahren und system zur identifizierung einer zugriffsanforderung einer anwendung auf einer mobilen vorrichtung in einem telekommunikationsnetz

Publications (2)

Publication Number Publication Date
EP3148157A1 EP3148157A1 (de) 2017-03-29
EP3148157B1 true EP3148157B1 (de) 2017-12-06

Family

ID=54198980

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15186238.0A Not-in-force EP3148157B1 (de) 2015-09-22 2015-09-22 Verfahren und system zur identifizierung einer zugriffsanforderung einer anwendung auf einer mobilen vorrichtung in einem telekommunikationsnetz

Country Status (6)

Country Link
US (1) US20180248979A1 (de)
EP (1) EP3148157B1 (de)
ES (1) ES2659582T3 (de)
MX (1) MX2018003460A (de)
PL (1) PL3148157T3 (de)
WO (1) WO2017051069A1 (de)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3176704A1 (de) * 2009-09-18 2017-06-07 Telesocial, Inc. Telekommunikationsdienst mit einem elektronischen informations-repository zur speicherung von informationen über benutzer eines sozialen netzwerks, entwickler und betreiber mobiler netzwerke
US10361859B2 (en) 2017-10-06 2019-07-23 Stealthpath, Inc. Methods for internet communication security
US10374803B2 (en) 2017-10-06 2019-08-06 Stealthpath, Inc. Methods for internet communication security
WO2019071131A1 (en) * 2017-10-06 2019-04-11 Stealthpath, Inc. INTERNET COMMUNICATION SECURITY METHODS
US10397186B2 (en) 2017-10-06 2019-08-27 Stealthpath, Inc. Methods for internet communication security
US10630642B2 (en) 2017-10-06 2020-04-21 Stealthpath, Inc. Methods for internet communication security
US10375019B2 (en) 2017-10-06 2019-08-06 Stealthpath, Inc. Methods for internet communication security
US10367811B2 (en) 2017-10-06 2019-07-30 Stealthpath, Inc. Methods for internet communication security
US10931768B2 (en) 2018-08-28 2021-02-23 Cujo LLC Determining active application usage through a network traffic hub
CN110020530B (zh) * 2018-12-24 2023-07-04 中国银联股份有限公司 用于确定应用程序在运行时的安全性的方法及其装置
US11558423B2 (en) 2019-09-27 2023-01-17 Stealthpath, Inc. Methods for zero trust security with high quality of service

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1974505B1 (de) * 2006-11-21 2012-08-01 Research In Motion Limited Anzeige einer liste verfügbarer drahtloser lokaler netzwerke
US9179399B2 (en) * 2008-05-12 2015-11-03 Blackberry Limited Methods and apparatus for use in facilitating access to a communication service via a WLAN hotspot
US8589541B2 (en) * 2009-01-28 2013-11-19 Headwater Partners I Llc Device-assisted services for protecting network capacity
US9152650B1 (en) * 2010-03-31 2015-10-06 Emc Corporation Mobile device data recovery
WO2012024030A2 (en) * 2010-07-26 2012-02-23 Seven Networks, Inc. Context aware traffic management for resource conservation in a wireless network
GB2499747B (en) * 2010-11-22 2014-04-09 Seven Networks Inc Aligning data transfer to optimize connections established for transmission over a wireless network
US9264868B2 (en) * 2011-01-19 2016-02-16 Qualcomm Incorporated Management of network access requests
US10481945B2 (en) 2011-04-01 2019-11-19 Facebook, Inc. System and method for communication management of a multi-tasking mobile device
US8560021B2 (en) * 2011-08-02 2013-10-15 Cellco Partnership Mobile device integration with WLAN functionality
US8838086B2 (en) * 2011-08-29 2014-09-16 Qualcomm Incorporated Systems and methods for management of background application events
US9230260B2 (en) * 2011-12-02 2016-01-05 Yellowpages.Com Llc System and method for instant deals in a mobile communication network
US9374476B2 (en) * 2012-02-24 2016-06-21 Alcatel Lucent System and method for network access vending
US9690635B2 (en) * 2012-05-14 2017-06-27 Qualcomm Incorporated Communicating behavior information in a mobile computing device
US8868025B2 (en) * 2012-08-14 2014-10-21 Qualcomm Incorporated Methods, systems and devices for prioritizing access to wireless networks
US10412550B2 (en) * 2012-10-29 2019-09-10 T-Mobile Usa, Inc. Remote driving of mobile device diagnostic applications
US20140214921A1 (en) 2013-01-31 2014-07-31 Onavo Mobile Ltd. System and method for identification of an application executed on a mobile device
US9826464B2 (en) * 2013-03-26 2017-11-21 Bandwidthx Inc. Systems and methods for establishing wireless connections based on access conditions
US9277444B2 (en) * 2013-12-17 2016-03-01 Verizon Patent And Licensing Inc. Restriction of background application data during congestion
US20160302144A1 (en) * 2015-04-08 2016-10-13 Nokia Technologies Oy Method, apparatus, and computer program product for efficient use of frequency bands and channels in wireless environment

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
PL3148157T3 (pl) 2018-04-30
EP3148157A1 (de) 2017-03-29
WO2017051069A1 (en) 2017-03-30
MX2018003460A (es) 2018-09-06
ES2659582T3 (es) 2018-03-16
US20180248979A1 (en) 2018-08-30

Similar Documents

Publication Publication Date Title
EP3148157B1 (de) Verfahren und system zur identifizierung einer zugriffsanforderung einer anwendung auf einer mobilen vorrichtung in einem telekommunikationsnetz
US20210176166A1 (en) Mtc service selection in the (s)gi-lan
US11937127B2 (en) Systems and methods for exposing custom per flow descriptor attributes
KR102264437B1 (ko) 웹 서비스 제공 방법 및 장치
US10432535B2 (en) Performing a specific action on a network packet identified as a message queuing telemetry transport (MQTT) packet
US10924903B2 (en) Software defined IoT service network architecture
US8873753B2 (en) Analysis of network operation
US10686854B2 (en) Streaming content using ad hoc networks of user devices
US9392025B2 (en) Subscriber dependent redirection between a mobile packet core proxy and a cell site proxy in a network environment
EP2629554B1 (de) Dienststeuerungsverfahren und -system, enodeb und paketdaten-netzwerkgateway
US20220030117A1 (en) Systems and methods to enable programmable xhaul transport
US20220191664A1 (en) Optimization of services applied to data packet sessions
US11102116B2 (en) Method and device for hosting application by access node
US20210368315A1 (en) LTE Gateways For Home And Commercial Sensor Data
US20140310371A1 (en) Cache and delivery based application data scheduling
EP3262807A1 (de) Mechanismus zur unterstützung einer bedienerunterstützten kindersicherung
US8605612B2 (en) Method and apparatus for extracting QoS parameters in mobile device
EP3777464B1 (de) Verfahren, vorrichtungen, system und computerprogramm zum zugriff auf einen dienst ausserhalb eines mobilkommunikationsnetzes in einer mehrweg-verbindung
KR102120869B1 (ko) 액세스 노드에 의한 애플리케이션 호스팅 방법 및 장치
WO2023213133A1 (zh) 一种通信方法和装置
US20230327997A1 (en) Methods and Apparatuses for Providing Quality of Service Handling of User Traffic Transmitted by a Content Provider
KR20200067800A (ko) 액세스 노드에 의한 애플리케이션 호스팅 방법 및 장치
JP2020042360A (ja) 通信装置、制御方法、およびプログラム

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20150922

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20170721

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 953341

Country of ref document: AT

Kind code of ref document: T

Effective date: 20171215

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602015006455

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2659582

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20180316

REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1236294

Country of ref document: HK

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180306

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 953341

Country of ref document: AT

Kind code of ref document: T

Effective date: 20171206

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180306

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

REG Reference to a national code

Ref country code: HK

Ref legal event code: GR

Ref document number: 1236294

Country of ref document: HK

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602015006455

Country of ref document: DE

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 4

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20180907

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20180625

Year of fee payment: 17

Ref country code: FI

Payment date: 20180917

Year of fee payment: 4

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20181127

Year of fee payment: 5

Ref country code: ES

Payment date: 20181001

Year of fee payment: 4

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20180930

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180922

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180922

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180930

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180930

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180930

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20190912

Year of fee payment: 5

Ref country code: DE

Payment date: 20190910

Year of fee payment: 5

Ref country code: IT

Payment date: 20190917

Year of fee payment: 5

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180922

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

REG Reference to a national code

Ref country code: FI

Ref legal event code: MAE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190922

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

Ref country code: MK

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20171206

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20150922

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171206

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180406

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180922

REG Reference to a national code

Ref country code: ES

Ref legal event code: FD2A

Effective date: 20210127

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602015006455

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MM

Effective date: 20201001

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20200922

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190923

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201001

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200930

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210401

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200922

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200922

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190922