US9270772B2 - System and method for providing access to presence status for mobile devices - Google Patents
System and method for providing access to presence status for mobile devices Download PDFInfo
- Publication number
- US9270772B2 US9270772B2 US13/408,891 US201213408891A US9270772B2 US 9270772 B2 US9270772 B2 US 9270772B2 US 201213408891 A US201213408891 A US 201213408891A US 9270772 B2 US9270772 B2 US 9270772B2
- Authority
- US
- United States
- Prior art keywords
- network
- application
- data
- mobile device
- device presence
- 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.)
- Active, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/50—Service provisioning or reconfiguring
-
- 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/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
-
- H04L67/24—
-
- H04W4/001—
-
- H04W4/003—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
Definitions
- the following relates to systems and methods for providing access to presence status for mobile devices.
- a server may also wish to send data to a mobile device based on presence information, for example, only when that mobile device is in coverage.
- a mobile device may also wish to know the coverage status of another device.
- client side applications may be relied upon to report device presence information to a server associated with the particular client application.
- relying on the client application to determine device presence information and provide this information to the server can be inefficient and/or require complex low-level programming on the part of the application developer.
- FIG. 1 is a schematic diagram of a communication system having a network infrastructure
- FIG. 2 is a schematic diagram of a communication system having a network infrastructure
- FIG. 3 is a schematic diagram of a communication system having a network infrastructure
- FIG. 4 is a block diagram of an example of a configuration for a device presence proxy
- FIG. 5 is a block diagram of an example of a configuration for an application server
- FIG. 6 is a block diagram of an example of a configuration for a mobile device
- FIG. 7 is a flow chart illustrating an example of a set of computer executable operations that may be performed in obtaining device presence information determined from a network infrastructure
- FIG. 8 is a schematic diagram of a communication system having a network infrastructure including multiple infrastructure nodes
- FIG. 9 is a sequence diagram illustrating operations performed in obtaining presence information.
- FIG. 10 is a sequence diagram illustrating operations performed in determining presence information using network data.
- APIs application programming interfaces
- the device presence proxy, the application server, or both the device presence proxy and application server may be hosted by a cloud-based platform to enable applications and application servers to be developed using the cloud-based platform with such application servers hosted in the cloud. In this way, rapid application development can be supported by reducing the low-level programming required to obtain network presence information concerning one or more mobile devices.
- the device presence information mined from the network infrastructure may include coverage status, roaming status, transport type, date of a previous transport change, time of a previous transport change, last authentication result for the mobile device, last time of authentication, etc.
- a mobile device e.g., 12 A and 12 B, each of which may be referred to generically in this disclosure as mobile device 12
- the mobile device 12 A includes an application 18 that may operate with an associated application server 16 .
- the application server 16 may be hosted by any suitable network- or cloud-based system, or may be custom built and hosted by a particular entity.
- Application Server 1 is associated with a client application, such as Application 1 .
- Application Server 1 may be communicable with client applications installed on more than one mobile device, e.g., Mobile Device 12 A and Mobile Device 12 B.
- the application server 16 may be associated with copies of the application 18 on multiple mobile devices 12 A, 12 B.
- Application Server 1 may utilize a single query to the device presence proxy 20 to obtain device presence information for a plurality of mobile devices.
- an Application 2 which does not have a corresponding application server 16 .
- the application server 16 is operable to communicate with a device presence proxy 20 by having access to a device presence API 22 .
- the device presence proxy 20 is included in or otherwise in communication with the network infrastructure 14 for obtaining device presence information and exposing that device presence information via the device presence API 22 made available to the application server 16 .
- the mobile device 12 A may also include a device presence API 22 for communicating with the application server 16 in obtaining device presence information exposed by the device presence proxy 20 .
- the device presence API 22 may also provide programming instructions to enable particular applications 18 (e.g., Application 2 ) to communicate directly with the device presence API 22 in the device presence proxy 20 in order to obtain network data exposed by the device presence proxy 20 directly as illustrated in dashed lines in FIG. 1 .
- the device presence API 22 is shown using a common reference numeral for the sake of illustration and that this API may differ depending on which device contains it.
- instructions included in the device presence API 22 on the mobile device 12 may differ from those included in an application server 16 .
- the configuration shown in FIG. 1 enables applications 18 and application servers 16 to determine a device's network-related presence without having to query the mobile device 12 or rely on reports from the mobile device 12 .
- Exposing data provided by the network infrastructure 14 can minimize the low-level programming required by the application developer to obtain presence information for a particular mobile device 12 that is required or otherwise utilized by an application client 18 and/or application server 16 .
- applications 18 deployed on the mobile device 12 do not need to have knowledge of the particular device type, OS version or memory location in order to determine network-based device presence since the device presence API 22 provides a network- or cloud-based source for such information.
- the device presence proxy 20 may be hosted on or otherwise provided by a server apparatus or network component having a processor or processing capabilities. Although the device presence proxy 20 shown in FIG. 1 is part of the network infrastructure 14 , it can be appreciated that the device presence proxy 20 may instead be independent of and communicable with the network infrastructure 14 .
- the device presence proxy 20 has access to, for example, network infrastructure nodes in the network infrastructure 14 that can determine various device presence status types based on interactions between the mobile device 12 and the network infrastructure 14 , e.g., where the network infrastructure nodes are associated with providing network services to the mobile device 12 .
- the device presence information mined from the network infrastructure 14 may include coverage status, roaming status, transport type, date of a previous transport change, time of a previous transport change, last authentication result for the mobile device, last time of authentication, etc.
- the device presence proxy 20 and the application server 16 may be hosted or otherwise provided by a cloud-based application development platform (cloud platform 24 hereinafter).
- the cloud platform 24 provides a central resource for applications that are deployed on to mobile devices 12 .
- the cloud platform 24 may be accessed by a developer to obtain a programming toolkit for developing an application 18 that can be deployed to various mobile device 12 , and for hosting an application server 16 corresponding to the application 18 .
- the cloud platform 24 may be part of a wider cloud-based environment that provides other services.
- the cloud platform 24 may include a cloud gateway 26 that provides an access point for interfacing with the network infrastructure 14 .
- the cloud gateway 26 may be used to query domains within the network infrastructure 14 that are different from those relied upon for mining device presence information.
- the cloud gateway 26 may also be used to obtain device billing information by accessing a provisioning server.
- the cloud gateway 26 includes the device presence API 22 for communicating with the device presence proxy 20 which, in FIG. 3 is in the network infrastructure 14 .
- the cloud gateway 26 may be responsible for managing queries to the network infrastructure 14 and thus may be used to authenticate and authorize requests, perform throttling and filtering, and to route requests to appropriate data providers (e.g., to specific domains and/or nodes within the network infrastructure 14 ).
- the cloud gateway 26 may therefore be an existing cloud platform component that is provided the device presence API 22 in order to enable device presence requests to be authorized and routed to the device presence proxy 20 , among other requests.
- the device presence API 22 provided to the cloud gateway 26 may differ from the device presence API 22 made available to the mobile devices 12 and application servers 16 .
- the mobile devices 12 and application servers 16 may have an API that includes program instructions for communicating with the cloud gateway 26 rather than directly with the device presence proxy 20 in a “two-tiered” configuration.
- the device presence API 22 will be considered any API that provides the ability to obtain device presence information, whether directly from the device presence proxy 20 (e.g., as shown in FIGS. 1 and 2 ), or via another agent or service or entity such as the cloud gateway 26 shown in FIG. 3 .
- FIG. 4 illustrates an example of a configuration for the device presence proxy 20 .
- the device presence proxy 20 includes a processor 30 for processing application inquiries 36 from applications 18 and/or application servers 16 requesting presence data for at least one mobile device 12 ; and for obtaining network data from, for example, network infrastructure nodes associated with network services provided to the mobile device 12 , in order to respond to the application inquires 36 .
- the application inquiries 36 and inquiry responses 42 may be formatted according to message syntax associated with the the device presence API 22 .
- the device presence proxy 20 includes a network infrastructure interface 32 for communicating with the network infrastructure 14 in order to, for example, participate in a request-response exchange with one or more network infrastructure nodes.
- the network infrastructure interface 32 generally represents any software, hardware, or combination thereof, used or required to connect and communicate with the network infrastructure 14 .
- the device presence proxy 20 also includes a network interface 34 for communicating via one or more networks within the communication system 8 (e.g., via the Internet, a cellular network, etc.).
- the device presence proxy 20 may also communicate with one or more of the cloud gateway 26 ( FIG. 3 ) in the cloud platform 24 , application servers 16 ( FIGS. 1-3 ), and mobile devices 12 ( FIGS. 1-3 ).
- the device presence API 22 provided to the cloud gateway 26 and/or application servers 16 and/or mobile devices 12 , enables the application 18 and/or application server 16 to obtain data exposed by the network infrastructure 14 .
- the network interface 34 generally represents any software, hardware, or combination thereof, used or required to connect and communicate with the cloud gateway 26 , application server 16 and mobile device 12 .
- the processor 30 receives an application inquiry 36 from the cloud gateway 26 , mobile device 12 , or application server 16 via the network interface 34 , the application inquiry 36 requesting a presence data for at least one mobile device 12 . Based on the application inquiry 36 , the processor 30 sends a network data request 38 to the network infrastructure 14 via the network infrastructure interface 32 , to obtain network data from one or more network infrastructure nodes associated with providing service to the at least one mobile device 12 . The processor 30 receives or otherwise obtains a network data response 40 from the network infrastructure 14 , which includes the requested network data.
- the processor 30 uses the obtained network data to determine an application inquiry response 42 to the application inquiry 36 and sends the inquiry response 42 to the requestor, e.g., the cloud gateway 26 , mobile device 12 , or application server 16 , depending on from where the application inquiry 36 originated, via the network interface 34 .
- the requestor e.g., the cloud gateway 26 , mobile device 12 , or application server 16 , depending on from where the application inquiry 36 originated, via the network interface 34 .
- FIG. 5 illustrates an example of a configuration for the application server 16 . It can be appreciated that various components of the application server 16 are omitted for brevity.
- the application server 16 includes one or more network interfaces 46 for communicating with one or more mobile devices 12 and for communicating with the cloud gateway 26 or device presence proxy 20 using the device presence API 22 .
- the application server 16 also includes a processor 44 for handling requests from mobile devices 12 , providing responses to the mobile devices 12 , and for exchange request and responses with the cloud gateway 26 or device presence proxy 20 , among other things.
- the mobile device 12 also includes one or more network interfaces 50 for accessing and utilizing the network services and for enabling the application 18 to communicate with the application server 16 , device presence proxy 20 and/or cloud gateway 26 .
- the mobile device 12 also includes a processor 48 for executing program instructions, e.g., for utilizing the device presence API 22 , enabling the application 18 to be used, etc.
- FIG. 7 illustrates several operations that may be performed by various components in obtaining device presence information from exposed data from the network infrastructure 14 .
- the operations described in FIG. 7 represent processes that may be performed by each of the Network Infrastructure, Device Presence Proxy, Application Server, and Mobile Device. While they are shown together in FIG. 7 , it should be understood that the process illustrated within each of the four columns may be independently described and claimed for each device. Furthermore, the operations described with regard to FIG. 7 may be embodied at each device using a variety of alternatives, as described in this disclosure. In the example shown in FIG. 7 , it is assumed that the device presence data is being requested by the application server 16 . However, as shown in dashed lines in FIG.
- the request for device presence data may also originate from the application 18 on the mobile device 12 .
- the presence data being requested by the application server 16 may relate to a plurality of mobile devices 12 and presence information requested by one mobile device 12 may relate to other mobile devices (not shown) running the application 18 .
- the application server 16 uses the device presence API 22 to send an application inquiry 36 to the device presence proxy 20 at 58 , either directly or via the cloud gateway 26 .
- the application inquiry 36 may originate at the application server 16 , or may be facilitated by or forwarded on behalf of the mobile device 12 .
- the application 18 on the mobile device 12 may send a presence request to the application server 16 at 54 , which is received by the application server 16 at 56 . It can also be appreciated that the presence request may also be sent by the mobile device 12 directly to the device presence proxy 20 in other examples.
- the device presence proxy 20 receives the application inquiry 36 at 60 and obtains network data at 62 based on a request-response mechanism employed in communicating with one or more components or nodes within the network infrastructure 14 .
- the network data is provided by the network infrastructure 14 at 64 and this data may be mined or otherwise found or determined by the network infrastructure 14 at 66 depending on the nature of the application inquiry 36 , etc.
- the device presence proxy 20 may determine a type of presence data from the application inquiry 36 and generate a network data request 38 that can be sent directly to a particular node in the network infrastructure 14 .
- more complicated request-response mechanisms may be employed in order to obtain the network data response 40 required to generate the application inquiry response 42 .
- One such example is described below.
- the device presence proxy 20 determines a response to the application inquiry 36 at 68 based on the nature of the data exposed by the network infrastructure 14 and sends an inquiry response 42 to the application server 16 directly or via the cloud gateway 26 at 70 .
- the application server 16 receives the inquiry response 42 at 72 and utilizes the presence data at 74 , e.g., to update a presence database or to perform a server-based operation such as updating a presence server (not shown). It can be appreciated that, as shown in dashed lines, the application server 16 may also provide presence data to the application 18 at 76 , which is received by the mobile device 12 at 78 .
- an application 18 A of a first mobile device 12 A places a request for device presence information to an associated application server 16 ′.
- the application 18 A may place the request for device presence information directly to the device presence proxy 20 .
- the requested device presence information may pertain to the presence information of the first mobile device 12 A, a second mobile device 12 B, or any other mobile devices (not shown) having an application client 18 .
- the application client 18 A of the first mobile device 12 A identifies the mobile device 12 (e.g. second mobile device 12 B) for which the presence information is being requested by providing identifying information corresponding to that mobile device.
- a personal identification number (PIN) associated with that mobile device 12 may be provided by the first mobile device 12 A.
- the PIN may be a sequence of alphanumeric characters uniquely identifying a mobile device.
- the request for device presence data which includes the supplied PIN, is received by the application server 16 and passed to the cloud gateway 26 ′ for authorization and routing, using the device presence API 22 in the application server 16 ′.
- the cloud gateway 26 ′ routes the request to the device presence proxy 20 , which in this example includes a global device presence web service 20 ′ in the network infrastructure 14 ′, and node device presence web services 85 in respective nodes 84 of a first domain (Domain 1 ) 91 in the network infrastructure 14 ′, e.g., a relay domain.
- the cloud gateway 26 ′ may also be configured to route other requests or otherwise communicate with other domains within the network infrastructure 14 ′, e.g., a second domain (Domain 2 ) 93 having a device provisioning state web server 95 for providing device billing information for a particular mobile device 12 .
- the global device presence web service 20 ′ identifies, from a plurality of infrastructure nodes 84 , the node containing presence information of the mobile device 12 for which the presence information is being requested.
- the first mobile device 12 A may receive network service(s) 94 A provided by a first infrastructure node 84 A.
- the global device presence web service 20 ′ identifies the first infrastructure node 84 A to retrieve presence information relevant to the first mobile device 12 A.
- the application client 18 A of the first mobile device 12 A may want to determine presence information of the second mobile device 12 B.
- the second mobile device 12 B in this example receives network service(s) 94 B provided by a second infrastructure node 84 B.
- the global device presence web service 20 ′ identifies the second infrastructure node 84 B to retrieve presence information relevant to the second mobile device 12 B.
- the global device presence web service 20 ′ may access a route service 80 or a relay database 82 in a storage element 81 .
- the route service 80 and the relay database 82 are complementary services which both provide PIN routing information that can used to match the supplied PIN to a corresponding node ID.
- the node ID identifies the infrastructure node 84 which can handle discovery of the relevant presence information. For example, the node ID may identify one of a plurality of infrastructure node elements 86 in the corresponding infrastructure node 84 .
- Current routing information from the relay database 82 may also be included in the route service 80 . If the route service 80 is not available, the relay database 82 can be used to look up the current node ID of the PIN.
- FIG. 8 illustrates further detail of the first infrastructure node 84 A and the second infrastructure node 84 B.
- the first infrastructure node 84 A includes one or more node elements 86 A which handle requests for device presence information.
- the node elements 86 A may include, among other things, a server or other network infrastructure element.
- the first infrastructure node 84 A also includes a route service 88 A and a relay database 90 A in a storage element 89 A, and various other mobile device information sources 92 A, e.g., a wireless transport.
- the first infrastructure node 84 A also includes a node device presence web service 85 A for receiving and processing requests from the global device presence web service 20 ′ It can be appreciated that the second infrastructure node 84 B includes similar components identified using the suffix “B”.
- the node device presence web service 85 proxies the request to the identified node element 86 . If the request to the node element 86 times out, the request is resubmitted to another node element 86 within the same infrastructure node 84 .
- the node element 86 may, for example, identify a wireless transport handling the mobile device 12 , and query that wireless transport for the presence data. The node element 86 may alternatively mine data from the local route service 88 and the local relay database 90 to extract presence information.
- the cloud gateway 26 ′ shown in FIG. 8 may communicate with the global device presence web service 20 ′ using a Simple Object Access Protocol (SOAP).
- SOAP Simple Object Access Protocol
- the global device presence web service 20 ′ may also communicate with the plurality of infrastructure nodes 84 using SOAP.
- the infrastructure node elements 86 may communicate with the local wireless transports through an Inter Relay Protocol (IRP) communication. Communication between the global device presence web service 20 ′ and the route server 80 may be handled through IRP communications.
- the relay database 82 may be, for example, an SQL database.
- FIG. 9 a sequence diagram is provided illustrating a process by which the cloud gateway 26 ′ may forward a request for presence information for a mobile device 12 on behalf of an application server 16 .
- the cloud gateway 26 ′ places a request for presence information at 100 to the global device presence web service 20 ′.
- the cloud gateway 26 ′ provides a PIN corresponding to the mobile device 12 for which the presence information is being requested.
- the global device presence web service 20 ′ places a request to the relay database 82 or route server 80 at 102 , to determine PIN routing information.
- the PIN routing information is obtained by the global device presence web service 20 ′ at 104 .
- the global device presence web service 20 ′ Based on the obtained routing information, the global device presence web service 20 ′ identifies the node element 86 corresponding to the one or more identified node IDs at 106 , and selects the node element 86 at 108 . Once the appropriate node element 86 has been identified, the global device presence web service 20 ′ may then send a request for network data to the node element 86 at 110 via the respective node device presence web service 85 . The global device presence web service 20 ′ receives the presence information from the node element 86 at 112 . The global device presence web service 20 ′ may then return the presence information to the cloud gateway 26 ′ at 114 , which may be passed back to the application server 16 ′ or application 18 .
- the global device presence web service 20 ′ is provided with the flexibility of having alternative sources of information to identify the infrastructure node 84 corresponding to the mobile device 12 associated with the presence information request.
- the infrastructure nodes 84 having access to both local route services 88 and local relay databases 90 are provided with the flexibility of having alternative sources of information to identify the appropriate mobile device information sources, such as a wireless transport, for determining the appropriate network data.
- FIG. 10 a sequence diagram is provided illustrating one way in which the node element 86 may handle the request provided by the global device presence web service 20 ′ to the node device presence web service 85 at 110 .
- the request sent at 110 may be translated by a SOAP server 120 in the node element 86 from a request for presence information to a request for network data at 116 .
- the request for network data sent at 116 is then processed by a server engine 122 .
- the server engine 120 determines the network data relevant to the presence information at 118 by mining the appropriate wireless transport 92 ′.
- the network data is obtained by the server engine 122 at 120 , and then obtained by the SOAP server 120 at 122 . At this point, the network data may be converted back into presence information. This presence information is then sent to the global device presence web service 20 ′ at 112 as shown in FIG. 9 .
- transport type and coverage status of a mobile device 12 can be identified.
- the mobile device transport type can, for example, be cellular or WiFi.
- the coverage status can, for example, be “in coverage,” “out of coverage,” or “having uncertain coverage.”
- Transport type and coverage status can be mined from the wireless transport 92 ′.
- transport type and coverage status of a mobile device 12 can be identified by having the global device presence web service 20 ′ select an appropriate node element 86 , issue a “GetPinCoverage” SOAP request to the identified node element 86 , and wait for a response.
- the SOAP request issued by the global device presence web service 20 ′ may include the request entity, request ID and mobile device PIN as inputs.
- the node element 86 identifies the appropriate wireless transport 92 ′ where the coverage status and transport type can be found, and extracts the relevant information.
- the response from the node element 86 may include a request/response header which include the request entity, request ID, mobile device PIN and result status code; the coverage state (in, our, or uncertain), a coverage timestamp indicating the time of last coverage state change) and a transport type (cellular or WiFi).
- Roaming status of a mobile device 12 can also be identified.
- the mobile device 12 may be roaming, not roaming, or of an unknown roaming status.
- Roaming status can be mined from the local relay database 90 of the infrastructure node 84 being queried.
- roaming status of a mobile device 12 can be identified by having the global device presence web service 20 ′ or node device presence web service 85 select an appropriate node element 86 , issue a “GetPinRoaming” SOAP request to the identified node element 86 , and wait for a response.
- the SOAP request issued by the global device presence web service 20 ′ may include the request entity, request ID and mobile device PIN as inputs.
- the node element 86 queries, e.g., the local relay database 90 for the roaming status of the mobile device 12 .
- the response from the node element 86 may include a request/response header which include the request entity, request ID, mobile device PIN and result status code; and the roaming status (roaming, not roaming, or unknown).
- a method comprising: receiving, via an application programming interface, an application inquiry, the application inquiry requesting a presence data for at least one mobile device; responsive to receiving said inquiry, obtaining network data from one or more network infrastructure nodes associated with providing service to the at least one mobile device; determining a response to the application inquiry based upon the network data; and providing the response via the application programming interface.
- a device presence proxy apparatus comprising a processor and a memory, the memory comprising computer executable instructions for: receiving, via an application programming interface, an application inquiry, the application inquiry requesting a presence data for at least one mobile device; responsive to receiving said inquiry, obtaining network data from one or more network infrastructure nodes associated with providing service to the at least one mobile device; determining a response to the application inquiry based upon the network data; and providing the response via the application programming interface.
- a computer readable medium comprising computer executable instructions for: receiving, via an application programming interface, an application inquiry, the application inquiry requesting a presence data for at least one mobile device; responsive to receiving said inquiry, obtaining network data from one or more network infrastructure nodes associated with providing service to the at least one mobile device; determining a response to the application inquiry based upon the network data; and providing the response via the application programming interface.
- any module or component exemplified herein that executes instructions may include or otherwise have access to computer readable media such as storage media, computer storage media, or data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape.
- Computer storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data.
- Examples of computer storage media include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by an application, module, or both. Any such computer storage media may be part of the device presence proxy 20 , application server 16 , cloud platform 24 , cloud gateway 26 , or mobile device 12 , etc., or accessible or connectable thereto. Any application or module herein described may be implemented using computer readable/executable instructions that may be stored or otherwise held by such computer readable media.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (30)
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/408,891 US9270772B2 (en) | 2012-02-29 | 2012-02-29 | System and method for providing access to presence status for mobile devices |
US13/439,688 US9264504B2 (en) | 2012-02-29 | 2012-04-04 | System and method for providing access to presence status for mobile devices |
CA2805686A CA2805686C (en) | 2012-02-29 | 2013-02-11 | System and method for providing access to presence status for mobile devices |
EP13154956.0A EP2635001B1 (en) | 2012-02-29 | 2013-02-12 | System for providing access to presence status for mobile devices |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/408,891 US9270772B2 (en) | 2012-02-29 | 2012-02-29 | System and method for providing access to presence status for mobile devices |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/439,688 Continuation-In-Part US9264504B2 (en) | 2012-02-29 | 2012-04-04 | System and method for providing access to presence status for mobile devices |
Publications (2)
Publication Number | Publication Date |
---|---|
US20130227118A1 US20130227118A1 (en) | 2013-08-29 |
US9270772B2 true US9270772B2 (en) | 2016-02-23 |
Family
ID=49004528
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/408,891 Active 2032-04-04 US9270772B2 (en) | 2012-02-29 | 2012-02-29 | System and method for providing access to presence status for mobile devices |
Country Status (1)
Country | Link |
---|---|
US (1) | US9270772B2 (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10218700B2 (en) * | 2015-02-23 | 2019-02-26 | Ca, Inc. | Authorizations for computing devices to access a protected resource |
US10200288B2 (en) * | 2015-12-18 | 2019-02-05 | Xerox Corporation | Shaping data traffic within a local area network |
US11290425B2 (en) * | 2016-02-01 | 2022-03-29 | Airwatch Llc | Configuring network security based on device management characteristics |
Citations (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020083127A1 (en) * | 2000-11-20 | 2002-06-27 | At&T Wireless Services, Inc. | Methods and systems for providing application level presence information in wireless communication |
US20030073440A1 (en) * | 2001-06-26 | 2003-04-17 | Versada Networks, A Washington Corporation | Detecting and transporting dynamic pressence information over a wireless and wireline communications network |
US20030217099A1 (en) | 2002-05-15 | 2003-11-20 | Microsoft Corporation | Method and system for supporting the communication of presence information among computing devices of a network |
US20060149814A1 (en) | 2004-12-30 | 2006-07-06 | Utstarcom, Inc. | Method and apparatus for presence status facilitation by an access gateway in a mobile communications system |
US20080249997A1 (en) | 2005-12-17 | 2008-10-09 | Huawei Technologies Co., Ltd. | Method and system for querying user information and search proxy, client and user |
US7493390B2 (en) | 2002-05-15 | 2009-02-17 | Microsoft Corporation | Method and system for supporting the communication of presence information regarding one or more telephony devices |
US20090070410A1 (en) | 2007-09-12 | 2009-03-12 | International Business Machines Corporation | Managing Presence Information Of A Presentity |
US7545762B1 (en) | 2002-08-20 | 2009-06-09 | Sprint Spectrum L.P. | Method and system for network presence notification |
US20090275314A1 (en) * | 2006-04-21 | 2009-11-05 | Telecom Italia S.P.A. | Method and System for Providing Presence Information |
US20100094993A1 (en) | 2008-10-15 | 2010-04-15 | Research In Motion Limited | Use of Persistent Sessions by a Presence Access Layer |
US20110032896A1 (en) * | 2008-05-12 | 2011-02-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Tracking Network Resources |
US20110066688A1 (en) | 2009-09-14 | 2011-03-17 | Armo Pinding | Presence information |
US20110153782A1 (en) | 2009-12-17 | 2011-06-23 | David Zhao | Coding data streams |
US20110202641A1 (en) * | 2010-02-12 | 2011-08-18 | Colin Kahn | Method and apparatus providing access network aware presence to applications |
US20110199962A1 (en) * | 2010-02-12 | 2011-08-18 | Colin Kahn | Method and apparatus for controlling access technology selection |
US20110280196A1 (en) | 2010-05-17 | 2011-11-17 | Qualcomm Incorporated | Optimization of the presence information refresh for a wireless device |
US20110314482A1 (en) * | 2010-06-18 | 2011-12-22 | Microsoft Corporation | System for universal mobile data |
US20120084344A1 (en) * | 2010-10-05 | 2012-04-05 | Research In Motion Limited | Method, server and system for propogating a wireless communication device state |
-
2012
- 2012-02-29 US US13/408,891 patent/US9270772B2/en active Active
Patent Citations (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020083127A1 (en) * | 2000-11-20 | 2002-06-27 | At&T Wireless Services, Inc. | Methods and systems for providing application level presence information in wireless communication |
US20030073440A1 (en) * | 2001-06-26 | 2003-04-17 | Versada Networks, A Washington Corporation | Detecting and transporting dynamic pressence information over a wireless and wireline communications network |
US20030217099A1 (en) | 2002-05-15 | 2003-11-20 | Microsoft Corporation | Method and system for supporting the communication of presence information among computing devices of a network |
US7493390B2 (en) | 2002-05-15 | 2009-02-17 | Microsoft Corporation | Method and system for supporting the communication of presence information regarding one or more telephony devices |
US7545762B1 (en) | 2002-08-20 | 2009-06-09 | Sprint Spectrum L.P. | Method and system for network presence notification |
US20060149814A1 (en) | 2004-12-30 | 2006-07-06 | Utstarcom, Inc. | Method and apparatus for presence status facilitation by an access gateway in a mobile communications system |
US20080249997A1 (en) | 2005-12-17 | 2008-10-09 | Huawei Technologies Co., Ltd. | Method and system for querying user information and search proxy, client and user |
US20090275314A1 (en) * | 2006-04-21 | 2009-11-05 | Telecom Italia S.P.A. | Method and System for Providing Presence Information |
US20090070410A1 (en) | 2007-09-12 | 2009-03-12 | International Business Machines Corporation | Managing Presence Information Of A Presentity |
US20110032896A1 (en) * | 2008-05-12 | 2011-02-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Tracking Network Resources |
US20100094993A1 (en) | 2008-10-15 | 2010-04-15 | Research In Motion Limited | Use of Persistent Sessions by a Presence Access Layer |
US20110066688A1 (en) | 2009-09-14 | 2011-03-17 | Armo Pinding | Presence information |
US20110153782A1 (en) | 2009-12-17 | 2011-06-23 | David Zhao | Coding data streams |
US20110202641A1 (en) * | 2010-02-12 | 2011-08-18 | Colin Kahn | Method and apparatus providing access network aware presence to applications |
US20110199962A1 (en) * | 2010-02-12 | 2011-08-18 | Colin Kahn | Method and apparatus for controlling access technology selection |
US20110280196A1 (en) | 2010-05-17 | 2011-11-17 | Qualcomm Incorporated | Optimization of the presence information refresh for a wireless device |
US20110314482A1 (en) * | 2010-06-18 | 2011-12-22 | Microsoft Corporation | System for universal mobile data |
US20120084344A1 (en) * | 2010-10-05 | 2012-04-05 | Research In Motion Limited | Method, server and system for propogating a wireless communication device state |
Non-Patent Citations (5)
Title |
---|
Debbabi et al. (NPL: The war of Presence and Instant Messaging: Right Protocols and APIs, Panasonic Information and Networking Technologies Laboratory, pp. 341-346, Jan. 2004. * |
Extended European Search report mailed Apr. 9, 2013, in corresponding European patent application No. 13154956.0. |
Final Office Action mailed Feb. 27, 2014; in U.S. Appl. No. 13/439,688. |
Non-Final Office Action mailed Aug. 5, 2013; in U.S. Appl. No. 13/439,688. |
Non-Final Office Action mailed Oct. 8, 2014; in U.S. Appl. No. 13/439,688. |
Also Published As
Publication number | Publication date |
---|---|
US20130227118A1 (en) | 2013-08-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20230413024A1 (en) | Method of Discovering Services Provided by a Network Repository Function | |
KR102046700B1 (en) | Message bus service directory | |
US11589298B2 (en) | Methods, systems, and computer readable media for selecting multiple network function types using a single discovery request | |
US10015684B2 (en) | Method and apparatus for managing specific resource in wireless communication system | |
US9867164B2 (en) | Method and device for processing a specific request message in wireless communication system | |
EP3962002B1 (en) | Communication optimization systems of blockchain network, registration methods and message forwarding methods | |
CN109618005A (en) | Method for calling server and proxy server | |
KR20180082555A (en) | Cross-resource subscription to the M2M service layer | |
US9984158B2 (en) | Finding services in a service-oriented architecture (SOA) network | |
JP6599546B2 (en) | How to enable unroot resource discovery in the service layer | |
JP2019525604A (en) | Network function NF management method and NF management apparatus | |
US11671514B2 (en) | Service layer message templates in a communications network | |
CN110958180B (en) | Gateway routing method, intelligent gateway, electronic device and computer storage medium | |
US9264504B2 (en) | System and method for providing access to presence status for mobile devices | |
CN114363173A (en) | Communication method, device and readable storage medium | |
US9270772B2 (en) | System and method for providing access to presence status for mobile devices | |
WO2018209189A1 (en) | Enable reliable and distributed m2m/iot services | |
US11323868B2 (en) | Serverless core network architecture | |
KR20120047350A (en) | Methods of discovering communication entity using discovery gateway and systems for discovering communication entity | |
US20150282121A1 (en) | Local resource sharing method of machine to machine component and apparatus thereof | |
KR20200130151A (en) | Method and apparatus for identifying service entity in machine to machine system | |
Namiot et al. | On Proximity Application Server | |
WO2023148124A1 (en) | Session management for redundant pdu sessions | |
CN116743840A (en) | Method, system and computer readable medium for discovering network function service producers in a hierarchical network | |
KR20200046348A (en) | Method and apparatus for performing group management in m2m system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: RESEARCH IN MOTION LIMITED, CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SIMEN, SILVIU FLORIAN;CLAYTON, DONALD SCOTT;KUSHNIR, ALINA;AND OTHERS;SIGNING DATES FROM 20120319 TO 20120717;REEL/FRAME:028776/0759 Owner name: RESEARCH IN MOTION CORPORATION, DELAWARE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CUI, TAO;REEL/FRAME:028776/0618 Effective date: 20120709 Owner name: RESEARCH IN MOTION UK LIMITED, UNITED KINGDOM Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BILDOY, LEIF EDVARD;REEL/FRAME:028776/0585 Effective date: 20120309 |
|
AS | Assignment |
Owner name: RESEARCH IN MOTION LIMITED, ONTARIO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RESEARCH IN MOTION UK LIMITED;REEL/FRAME:029323/0022 Effective date: 20121119 Owner name: RESEARCH IN MOTION LIMITED, ONTARIO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RESEARCH IN MOTION CORPORATION;REEL/FRAME:029321/0670 Effective date: 20121119 |
|
AS | Assignment |
Owner name: BLACKBERRY LIMITED, ONTARIO Free format text: CHANGE OF NAME;ASSIGNOR:RESEARCH IN MOTION LIMITED;REEL/FRAME:034143/0567 Effective date: 20130709 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: MALIKIE INNOVATIONS LIMITED, IRELAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BLACKBERRY LIMITED;REEL/FRAME:064104/0103 Effective date: 20230511 |
|
AS | Assignment |
Owner name: MALIKIE INNOVATIONS LIMITED, IRELAND Free format text: NUNC PRO TUNC ASSIGNMENT;ASSIGNOR:BLACKBERRY LIMITED;REEL/FRAME:064271/0199 Effective date: 20230511 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |