Verizon Patent and Licensing Inc.

Cellco Partnership

Sethumadhav Bendi

Lodema Margaret Steinbach

Jerry M Kupsh

Mingxing Li

Kumar Sanjeev

Amir Mayblum

Bradley D Cooper

Amol Tuli

Yousef Abdelmalek

G Lance Lockhart

Hesham Elbatouti

Zohar Fuchs

Kenneth M Potas

Lalit R Kotecha

Priscilla Lau

Zhijian Lin

Brian Libonate

Alice Yuan Bain

Paul H Prehn

Eliezer K Pasetes

Craig A Barth

Guangxin Frank Liu

Chi Kit Ben Lo

Susan S Marion

Trevor A MacDonald

A messaging platform may send, based on a query, information identifying one or more virtual assistants to a user device. The messaging platform may receive, from the user device, a response identifying a particular virtual assistant, of the one or more virtual assistants, wherein the virtual assistant is associated with an organization. The monitoring platform may send, to the user device, information related to the particular virtual assistant and may communicate, via the particular virtual assistant, with the user device via a rich communications services (RCS) communication session. The messaging platform may receive, from another device associated with the organization, a request to communicate with the user device and may convert the request into an RCS message. The messaging platform may send, via a server device, the RCS message to the user device to allow the user device to perform one or more actions.

Systems and methods for including enriched calling information in rich communications services (RCS) messaging

A user device may receive an instruction to generate a shortcut associated with a rich communication services (RCS) messaging session that is associated with a RCS application. The user device may generate, based on receiving the instruction, a snapshot of the RCS messaging session, and may transmit, based on generating the snapshot of the RCS messaging session, the snapshot of the RCS messaging session to an application server. The user device may generate, based on transmitting the snapshot of the RCS messaging session to the application server, the shortcut associated with the RCS messaging session, where the shortcut associated with the RCS messaging session is linked to the snapshot of the RCS messaging session. The user device may display, on a display of the device, the shortcut associated with the RCS messaging session.

Systems and methods for generating a shortcut associated with a rich communication services messaging session

A device may receive a message from a source. The device may send, to a server device, a request for classification information that identifies a classification of the message after receiving the message. The device may receive a response message to the request for the classification information after sending the request. The response message may include the classification information identifying the classification. The device may dynamically provide the message to a channel based on the classification identified by the classification information after receiving the response message.

Systems and methods for classification and/or transmission of messages

A device may receive a message from a third party messaging server device. The message may be destined for one or more user devices. The message may include a parameter that includes information related to the message. The device may determine that the message is an application-to-person ('A2P') message type based on the message being received from the third party messaging server device. The device may configure a value of the parameter based on determining that the message is the A2P message type. The device may provide the message to a user device, of the one or more user devices, or an inter-carrier server device after configuring the value of the parameter.

Method and device for differentiating third party messaging services

A method, a device, and a non-transitory storage medium provide for receiving registration information during a registration with a network, wherein the registration information includes a user identifier of a user registering with another network device of the network and an identifier of the other network device; determining whether registration information pertaining to a previous registration by the user with the network is stored; determining that the registration information pertaining to the previous registration is not stored; storing the received registration information based on determining that the registration information pertaining to the previous registration is not stored; selecting which application server of the network to transmit the received registration information; transmitting the received registration information to the application server based on the selecting; and using the received registration information to provide a service by the application server.

Disbursement of registration information to application/service layer at time of registration with a network

A device may receive an encrypted short message service (SMS) message en route from an originating device to a recipient device, the encrypted SMS message to be encrypted by the originating device using a key. The device may identify a flag associated with the encrypted SMS message. The device may determine, based on the flag, that the SMS message is encrypted. The device may provide the encrypted SMS message to the recipient device.

System and methods for secure short message service encryption and provisioning

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

Distinct user devices may sometimes share a telephone number. Techniques described herein may provide for the assigning of a temporary telephone number for a user device, which shares a telephone number with other user devices, in certain situations, such as when the user device places a call to an emergency call center. The temporary telephone number may allow the user device to be reached and/or located by the emergency call center.

Emergency call service for groups of devices with a shared number

A server device may receive a message from a first user device, the message being destined for a second user device; determine a call session control function (CSCF) server device associated with the second user device; and output, based on the determining, the message to the CSCF server device.

Centralized short message service center server for messaging

An approach for coordinating a communication response is described. A response coordination platform determines delivery of a notification to at least one device associated with a user. The response coordination platform further determines, based on the delivery, messaging content, a user specified response time, or a combination thereof for generating a message for responding to the notification. The response coordination platform then generates, based on the response time, at least one instruction for triggering an alert, a communication session, or a combination thereof by the at least one device associated with the user, other devices associated with the user, a device that sent the notification, or a combination thereof.

Method and system for coordinating a communication response

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 first device may receive an indication that a multimedia message service (MMS message) message has been sent from a first user device to a second user device; obtain, from a second device, the roaming status of the first user device at a time that the MMS message was sent by the first user device; generate a call details record (CDR) indicating the obtained roaming status of the first user device at the time the MMS message was sent by the first user device; and store or output the CDR to a billing system that charges an account, associated with the first user device, for sent MMS message. An amount charged by the billing system may be based on the roaming status of the first user device at the time at which MMS message are sent by the first user device.

Growing community of inventors

Walnut Creek, CA, United States of America

Sethumadhav Bendi