Source: https://patents.google.com/patent/US9473912B2/en
Timestamp: 2019-03-20 11:48:24
Document Index: 174693724

Matched Legal Cases: ['Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62']

US9473912B2 - SMS proxying - Google Patents
US9473912B2
US9473912B2 US14/475,042 US201414475042A US9473912B2 US 9473912 B2 US9473912 B2 US 9473912B2 US 201414475042 A US201414475042 A US 201414475042A US 9473912 B2 US9473912 B2 US 9473912B2
US20150350856A1 (en
This Application is related to the following U.S. Patent Applications: U.S. Provisional Application No. 62/005,550 filed May 30, 2014 and entitled “ANSWER AND HOLD WITH CLIENT AND HOST” by Rauenbuehler et al.; U.S. Provisional Application No. 62/005,534 filed May 30, 2014 and entitled “ANSWERING A CALL WITH CLIENT THROUGH A HOST” by Rauenbuehler et al.; U.S. Provisional Application No. 62/005,606 filed May 30, 2014 and entitled “CLIENT APPLICATIONS COMMUNICATING VIA A USER TUNNEL” by Tung et al.; U.S. Provisional Application No. 62/005,325, filed May 30, 2014 and entitled “PROXIED PUSH” by Pollack et al.; U.S. Provisional Application No. 62/005,505 filed May 30, 2014 and entitled “MANAGING CONNECTIONS OF A USER DEVICE” by Schobel et al.; U.S. Provisional Application No. 62/005,565 filed May 30, 2014 and entitled “APPLICATION-LEVEL ACKNOWLEDGEMENTS” by Pollack et al.; U.S. Provisional Application No. 62/005,586 filed May 30, 2014 and entitled “MESSAGES WITH ATTENUATING RETRANSMIT IMPORTANCE” by Pollack et al.; U.S. Provisional Application No. filed May 30, 2014 and entitled “UNIFIED MESSAGE DELIVERY BETWEEN PORTABLE ELECTRONIC DEVICES” by Pollack et al.; U.S. Provisional Application No. 62/005,990 filed May 30, 2014 and entitled “USER INTERFACE FOR PHONE CALL ROUTING AMONG DEVICES” by Coffman et al.; and U.S. Provisional Application No. 62/505,799 filed May 30, 2014 and entitled “PROTOCOL SWITCHING IN INTER-DEVICE COMMUNICATION” by Prats et al., which are commonly owned and are hereby incorporated by reference for all purposes. The present application is also related to U.S. Provisional Application 61/953,591, entitled “DYNAMIC LINK ADAPTATION FOR IMPROVED LINK MARGIN,” by Liu et al., filed Mar. 14, 2014, which is hereby incorporated by reference for all purposes.
When the provider sends a notification message to the particular application on user device 250, the provider connects to PNS 220 using provider interface 225 and sends the message to gateway 230. Even if user device 250 is associated with a particular zone, the provider does not need to connect to any particular gateway of PNS 220 to successfully push a notification message to user device 250. For example, if gateway 230 receives content from provider interface 225 and the content has a device token, gateway 230 will look at the token and either route the message to an appropriate server of PNS 220 (which may route the message to device interface 240 or another courier of PNS 220) or route the message directly to device interface 240.
FIG. 4 is a block diagram illustrating how identity management server 215 manages device profiles according to one embodiment. In this example, companion device 120 includes processor 402 having connection module 404, memory 406 in which a UID, device token, or other identifier T1 is stored, one or more applications 408, transmitter 410, and receiver 412. Processor 402 includes connection module 404 for managing connections. Memory 406 stores device token T1. Upon initial connection with identity management server 215 at the request of one or more applications 408 in order to register companion device 120 with a user profile, connection module 404 can transmit using transmitter 410 registration information and receive device token T1 from identity management server 215 using receiver 412. Once device token T1 has been generated, transmitter 410 transmits, or sends, device token T1 to various services allowing those services to send content, messages, notifications, etc. to companion device 120. As discussed above, provider applications can use device token T1, or include the token, with any notification message so that it can be appropriately forwarded back to companion device 120.
Wireless circuitry 1108 is used to send and receive information over a wireless link or network to one or more other devices' conventional circuitry such as an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, memory, etc. In some embodiments, wireless circuitry 1108 is capable of establishing and maintaining communications with other devices using one or more communication protocols, including time division multiple access (TDMA), code division multiple access (CDMA), global system for mobile communications (GSM), Enhanced Data GSM Environment (EDGE), wideband code division multiple access (W-CDMA), Long Term Evolution (LTE), LTE-Advanced, WiFi (such as IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), Bluetooth, Wi-MAX, voice over Internet Protocol (VoIP), near field communication protocol (NFC), a protocol for email, instant messaging, and/or a short message service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document. A mobile device can include wireless circuitry that can communicate over several different types of wireless networks depending on the range required for the communication. For example, a short-range wireless transceiver (e.g., Bluetooth), a medium-range wireless transceiver (e.g., WiFi), and/or a long range wireless transceiver (e.g., GSM/GPRS, UMTS, CDMA2000 1×/EV-DO and LTE/LTE-Advanced) can be used depending on the type of communication or the range of the communication.
receiving profile information corresponding to a plurality of devices associated with a user of the first device, the profile information indicating that a second device of the plurality of devices has short messaging service (SMS)/multimedia messaging service (MMS) capabilities;
receiving, at the user interface, data to form a payload;
generating a message comprising the payload, an address of a recipient device, and a flag indicating that the second device is to send the payload to the recipient device;
sending the message to the second device using the communications interface, the message instructing the second device to send the payload to the recipient device as an SMS/MMS message; and
sending the message to the plurality of devices associated with the user of the first device, the message informing the plurality of devices that the second device has sent the payload to the recipient device as the SMS/MMS message.
4. The method of claim 1 wherein receiving the data to form the payload at the user interface comprises receiving text data.
5. The method of claim 1 wherein receiving the data to form the payload at the user interface comprises receiving multimedia data.
7. The method of claim 1 wherein the flag indicating that the second device is to send the payload to the recipient device comprises a push topic associated with a push notification service.
8. A computer program product embodied within a non-transitory computer-readable medium storing code executable by one or more processors of a first device having a user interface and a communications interface for proxied communications, the non-transitory computer-readable medium comprising:
code for receiving profile information corresponding to a plurality of devices associated with a user of the first device, the profile information indicating that a second device of the plurality of devices has short messaging service (SMS)/multimedia messaging service (MMS) capabilities;
code for generating a message comprising the payload, an address of a recipient device, and a flag indicating that the second device is to send the payload to the recipient device;
code for sending the message to the second device using the communications interface, the message instructing the second device to send the payload to the recipient device as an SMS/MMS message; and
code for sending the message to the plurality of devices associated with the user of the first device, the message informing at least a subset of the plurality of devices that the second device has been instructed to send the payload to the recipient device.
9. The non-transitory computer-readable medium of claim 8 wherein the code for sending the message to the second device comprises code for sending the message as a non-SMS/MMS message.
10. The non-transitory computer-readable medium of claim 8 wherein the code for receiving the profile information comprises code for receiving one or more attributes of the second device indicative of device capabilities to send SMS/MMS messages.
11. The non-transitory computer-readable medium of claim 8 wherein the code for receiving the data to form the message at the user interface comprises code for receiving text data.
12. The non-transitory computer-readable medium of claim 8 wherein the code for receiving the data to form the message at the user interface comprises code for receiving multimedia data.
a second type of communications interface that is different from the first type of communications interface; and
provide profile information to an identity management service that enables a proxied device to identify the mobile device as being capable of sending a short messaging service (SMS)/multimedia messaging service (MMS) message;
receive, from the identity management service, a message using the first type of communications interface, the message being received based at least in part on the profile information and comprising a payload generated by the proxied device, an address of a recipient device, and a flag indicating that the mobile device is to send the payload to the recipient device using the second type of communications interface;
generate an indication that the mobile device sent the payload to the recipient device as the SMS/MMS message; and
send the indication to the identity management service for transmission to the proxied device by the identity management service.
15. The mobile device of claim 14 wherein, to determine whether the message is authorized to be sent to the recipient device, the set of instructions causes the processor to determine whether the proxied device is authorized to instruct the mobile device to send messages using SMS/MMS capabilities of the mobile device.
16. The mobile device of claim 14 wherein, to determine whether the message is restricted from being sent to the recipient device, the set of instructions causes the processor to determine whether the recipient device is authorized to receive messages sent using SMS/MMS capabilities of the mobile device.
17. The mobile device of claim 14 wherein the set of instructions further causes the processor to output a request to a user of the mobile device to authorize sending of the payload in the message received from the identity management service.
18. The mobile device of claim 14 wherein the payload comprises text data received at a user interface of the proxied device.
19. The mobile device of claim 14 wherein the payload comprises multimedia data selected at a user interface of the proxied device.
20. The mobile device of claim 14 wherein the set of instructions further causes the processor to send information to one or more devices associated with the user in response to sending the SMS/MMS message.
21. The mobile device of claim 14 wherein the set of instructions further causes the processor to at least one of:
send, to the identity management service, a failed indicator when the payload is not sent, or
send, to the identity management service, an unauthorized indicator when the payload is not authorized to be sent to the recipient device.
US20150350856A1 US20150350856A1 (en) 2015-12-03
US9473912B2 true US9473912B2 (en) 2016-10-18
US20120063385A1 (en) 2009-05-22 2012-03-15 Hui Yang Method, apparatus and system for pushing information, and method and apparatus for obtaining information
WO2015183829A1 (en) 2014-05-30 2015-12-03 Apple Inc. Proxied push
International Search Report and Written Opinion mailed Sep. 2, 2015 in PCT/US2015/032477, 10 pages.
US20150350856A1 (en) 2015-12-03