Cellco Partnership

Verizon Patent and Licensing Inc.

Cellco Partnership D/b/a Verizon Wireless

Jerry M Kupsh

Amir Mayblum

Zhijian Lin

Biren A Patel

Xuming Chen

Ye Huang

Sethumadhav Bendi

Kumar Sanjeev

Lodema Margaret Steinbach

Syed Haider

Thaddeus Jude Dudziak

Wei Guang Tan

Bradley D Cooper

Alice Yuan Bain

Brandie Roberts

Ian Lynn

Kim M Gutierrez

Keith P Lampron

Adrian Carlton Velthuis

Ning-Chia Yeh

Eli Pasetes

Robert Martin Ephraim

Manjari Asawa

Kevin Lim

Ratna S Desai

Sanjeevan Sivalingham

Hugh Herrick Fletcher

Eric Brady Burns

Eliezer K Pasetes

Kenneth M Potas

Mahendra Tharshanan

Ben Chen

Heather Lynne Goodson

Guangxin Frank Liu

Brian F Meehan

Lutz Ehrlich

Chi Kit Lo

Chong Wang

Fred Bierhaus

Kyle Hoyt

Joseph P Goldbach

Reuben G Martindale

John A Provinsal

A device may be configured to receive a message from a user device; and determine whether the message includes a parameter. When the message does not include the loop indicator parameter, the device may add the loop indicator parameter to the message to generate a first modified message, and output the first modified message toward an intended recipient of the message. When the message includes the loop indicator parameter, the device may determine whether a value of the loop indicator parameter exceeds a threshold value. When the value of the loop indicator parameter does not exceed the threshold value, the device may discard the message. When the value of the loop indicator parameter exceeds the threshold value, the device may modify the value of the loop indicator parameter value to generate a second modified message, and output the second modified message toward the intended recipient of the message.

Preventing SMS message forwarding loops

To control secondary devices of a subscriber whose primary device is subscribed to a mobile network, a secondary mobile directory number ('MDN') and secondary device identifiers are employed. After the primary device is rung, an Authentication and Call Waiting Engine receives a request from a Telephony Gateway to retrieve identifiers of any secondary devices that are linked to a primary MDN of the primary device. Next, the Authentication and Call Waiting Engine retrieves a secondary device identifier for each secondary device that is paired with the primary device by searching a secondary device identifier database with the primary MDN to find all linked secondary device identifiers. A rules database may be applied to exclude secondary device identifiers based on time of day and day of the week. The Authentication and Call Waiting Engine transmits the list of qualified secondary device identifiers to the Telephony Gateway for ringing.

Multiple secondary device call controls and protocols

A system includes a gateway and a verification server. The gateway is configured to receive a first message from a client over a network; send a request to a verification server to generate a first credential based on the first message; and route the first message toward a remote device. The verification server is configured to receive the request from the gateway; generate the first credential in response to the request; store the first credential; receive a second message from the remote device, the message requesting the verification server to validate a second credential; determine whether the second credential is valid based on the first credential; and send a notification to the remote device indicating whether the second credential is valid.

Verifying an identity of a message sender

A device may receive a text message or a multimedia message to be received by a receiving device. The message may be stored by one or more storage devices. The device may determine that the message is to be received by the receiving device via a wireless local area network (WLAN). The device may send, to the receiving device, a notification associated with the message. The device may identify a storage device, of the one or more storage devices, to provide the message to the receiving device. The device may manage a synchronization between the receiving device and the storage device via the WLAN. The synchronization may cause the message to be received by the receiving device. The device may receive an indication that the receiving device has received the message, and may provide closure information. The closure information may prevent the message from being delivered via a cellular network.

Sending and receiving messages over wireless local area networks

Systems and methods for message timestamp re-alignment for message thread consistency across multiple devices are disclosed. In some implementations, an outbound message originating at a mobile phone is received at an integrated messaging server. The outbound message is associated with a messaging protocol. A timestamp representing a send time for the outbound message associated with the messaging protocol at the mobile phone is determined, at the integrated messaging server, by receiving an indication of the send time from the mobile phone. The outbound message and the timestamp are stored at the integrated messaging server. The outbound message and the timestamp representing the send time for the outbound message are provided from the integrated messaging server to a client computing device different from the mobile phone.

Message timestamp re-alignment for message thread consistency across multiple devices

An approach is provided for messaging gateway services. It is determined whether a user profile specifies opting to receive content. The content is selectively forwarded, according to a multimedia protocol, to a device of a user as a multimedia messaging service (MMS) message or a short messaging service (SMS) message based on the determination, wherein the multimedia protocol supports both MMS messaging and SMS messaging.

Method and system for providing messaging gateway services

A user device may be configured to generate a multipart message (e.g., a multimedia messaging service ('MMS') message). A message part of the multipart message may include conversation metadata that includes information regarding a messaging conversation between the user device and at least one other user device. The message part may include a multipart type indicator (e.g., a Multipurpose Internet Mail Extensions ('MIME') type indicator) that indicates that a type of the at least one part is a type associated with conversation metadata. The user device may output the multipart message to the other user device.

Multipurpose internet mail extensions ('MIME') metadata for group messaging

A device may receive, from a first user device, a request to transmit a message to a user of a second user device. The request may include particular information indicating that content of the message is to be displayed to the user for a particular amount of time. The device may encrypt, based on receiving the request and using a key, the content of the message to obtain an encrypted message. The device may transmit the encrypted message to the second user device and receive, from the second user device, a request for the key. The device may transmit, to the second user device, the key and information identifying the particular amount of time to cause the second user device to decrypt the encrypted message, using the key, to obtain a decrypted message and cause the second user device to delete the decrypted message after the particular amount of time.

Transmitting and receiving self-destructing messages

A message server may establish an internet message access protocol ('IMAP') IDLE session with a first client device. The IMAP IDLE session may be used to transmit one or more notifications to the first client device. The message server may determine a status notification associated with a second client device. The status notification may include information associated with an action being performed using the second client device. The message server may determine that the first client device is an intended recipient of the status notification. The message server may transmit the status notification, toward the first client device, via the IMAP IDLE session, based on determining that the first client device is the intended recipient of the status notification.

Typing indicator for IMAP messaging

A first mobile device may receive, via a text messaging application, first location information from a second mobile device. The first location information may indicate a first geographic location of the second mobile device. The first mobile device may receive, via the text messaging application, second location information from the second mobile device. The second location information may indicate a second geographic location of the second mobile device. The first mobile device may generate, based on the first location information and the second location information, a graphical representation. The graphical representation may represent a movement of the second mobile device from the first geographic location to the second geographic location. The first mobile device may provide the graphical representation for display via a display associated with the first mobile device.

Text message location tracking using comet trail representing speed and direction

A conversion device may receive a first message in a Telelocator Alphanumeric Protocol (TAP) format. The first message may include information that identifies a user device as an intended recipient of the first message. The first message may not be transmissible over a wireless connection. The conversion device may convert the first message into a second message in a first format capable of being transmitted over the wireless connection. The second message may include information that identifies the user device. The conversion device may provide the second message, using the wireless connection, to a messaging device. The wireless message may cause the messaging device to convert the second message into a third message in a second format that is capable of being delivered to the identified user device. The wireless message may further cause the messaging device to provide the third message to the user device.

Wireless delivery of telelocator alphanumeric protocol (TAP) messages

A device receives an indication that a user of the device wishes to share media content with another user. The device identifies a size associated with the media content and an acceptable media content size for successful transmission over a communication network. The size associated with the media content is compared with the acceptable media content size to determine whether the size associated with the media content exceeds the acceptable media content size. Upon determining that the size associated with the media content exceeds the acceptable media content size, the device enables the user of the device to reduce the size of the media content to the acceptable media content size. The user is enabled to graphically determine when the media content is reduced to the acceptable media content size.

Reducing media content size for transmission over a network

A method performed by a network device may include receiving a mobile directory number (MDN) that has been identified as a mobile spam originator and generating a query for attributes of a mobile device registered with the MDN. The method also includes receiving a query response that include attributes of the mobile device and determining to block the mobile device from access to a network associated with the network device. The method further includes providing, by the network device and to a blacklist system, one or more of the device attributes.

Disabling mobile devices that originate message service spam

A server receives encrypted information for an intended recipient. The server determines, based on recipient information, whether the recipient's device is able to decrypt the encrypted information. If so, the encrypted information is provided to the device. Upon determining that the device is unable to decrypt the encrypted information, the server sends a notification message to the device. The notification message indicates that the encrypted message has been received. In response to the notification message, the server receives a response from the device. If the device is successfully authenticated, based on the response, the server decrypts the encrypted information and provides the decrypted information to the device for presentation to the recipient.

Method of decrypting encrypted information for unsecure phone

Systems and techniques are provided for transmitting a secured message from an originating device to a recipient mobile device through a mobile communication network. A secure communication channel to the recipient mobile device is established via the mobile communication network based on a request for transmission of a secured message from the originating device. A notification of the secured message including instructions for retrieving the secured message is sent to the recipient mobile device through the established secured communication channel. The recipient mobile device is authenticated based on authentication credentials associated with the recipient mobile device. The recipient mobile device is allowed to retrieve the secured message via the secure data channel of the mobile communication network using the instructions included in the notification.

Modified messaging server call flow for secured mobile-to-mobile messaging

Growing community of inventors

Concord, CA, United States of America

Jerry M Kupsh