Abstract:
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.
Abstract:
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.
Abstract:
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.
Abstract:
A device may receive, from a user device, a group text message. The device may identify a group of recipients associated with the group text message. The device may determine that the group of recipients includes an emergency services recipient and a non-emergency services recipient. The device may generate an emergency call text message based on the group of recipients including the emergency services recipient and the non-emergency services recipient. The device may send the emergency call text message to the emergency services recipient without sending the emergency call text message to the non-emergency services recipient. The device may send the group text message to the non-emergency services recipient without sending the group text message to the emergency services recipient.
Abstract:
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.
Abstract:
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.
Abstract:
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.
Abstract:
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.
Abstract:
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.
Abstract:
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.