Abstract: An example method is performed by a rich communications services (RCS) server. The RCS server maintains metadata and RCS messages associated with a message thread, where the message thread provides open group chat (OGC) communications among a plurality of participants. The RCS server receives a lock request from a participant of the message thread to lock the message thread and in response thereto modifies the metadata associated with the message thread to indicate that the message thread is locked. A request to join the message thread is then received by the RCS server, where the request is rejected in response to the RCS server determining that the metadata associated with the message thread indicates that the message thread is locked.

Abstract: One or more timers can be used by an originating UE during setup of a communication session. The timer(s) can be triggered by an originating UE sending a request or receiving a response that uses a first signaling protocol. The timer(s) can further be terminated by the originating UE sending a request or receiving a response that uses a second signaling protocol different from the first signaling protocol, so long as the request/response using the second signaling protocol occurs before timeout of the timer(s).

Abstract: In some implementations, a core network device can receive an initiation request of a communication session to an alias number. The core network device can retrieve from a registration database one or more destination number(s) corresponding to the alias number. The core network device can transmit respective indication(s) of the alias number to destination(s) corresponding to the retrieved destination number(s). The core network device can initiate the communication session to one of the destination(s) using the respective one of the retrieved destination number(s). A destination number can correspond to a computing device, e.g.

Abstract: A network terminal, e.g., a smartphone, can retrieve, from a datastore, a cryptographically-signed configuration record including a device identifier of the terminal. The terminal can transmit a request message comprising the configuration record and the device identifier. A network device can verify authenticity of the device identifier and a match between the identifier in the record and the identifier in the message. In response to confirmation of the request by a policy engine, the network device can determine a reply message comprising a cryptographically-signed second configuration record that includes a second device identifier. The terminal can verify that the signature is valid and that the second device identifier matches the device identifier. In response, the terminal can modify data in the datastore according to the second configuration record. The configuration record can lock or unlock the terminal, or determine permitted services or network peers.

Abstract: An example method is performed by a rich communications services (RCS) server. The RCS server receives a business chat message and corresponding token from a business chat server. The business chat message is formatted according to a third-party proprietary protocol to include a plurality of message attributes. At least one of the message attributes is associated with an intended recipient of the business chat message. The RCS server is configured to convert the business chat message into an RCS message, where converting the business chat message into the RCS message includes mapping the plurality of message attributes to a plurality of message parameters included in the RCS message. The RCS server is also configured to query a profile database with the at least one message attribute to obtain an identification (ID) of the intended recipient and to send the RCS message to the intended recipient based on the ID.

Abstract: In some implementations, a core network device can receive an initiation request of a communication session to an alias number. The core network device can retrieve from a registration database one or more destination number(s) corresponding to the alias number. The core network device can transmit respective indication(s) of the alias number to destination(s) corresponding to the retrieved destination number(s). The core network device can initiate the communication session to one of the destination(s) using the respective one of the retrieved destination number(s). A destination number can correspond to a computing device, e.g.

Abstract: A network terminal, e.g., a smartphone, can retrieve, from a datastore, a cryptographically-signed configuration record including a device identifier of the terminal. The terminal can transmit a request message comprising the configuration record and the device identifier. A network device can verify authenticity of the device identifier and a match between the identifier in the record and the identifier in the message. In response to confirmation of the request by a policy engine, the network device can determine a reply message comprising a cryptographically-signed second configuration record that includes a second device identifier. The terminal can verify that the signature is valid and that the second device identifier matches the device identifier. In response, the terminal can modify data in the datastore according to the second configuration record. The configuration record can lock or unlock the terminal, or determine permitted services or network peers.

Abstract: An example method is performed by a rich communications services (RCS) server. The RCS server maintains metadata and RCS messages associated with a message thread, where the message thread provides open group chat (OGC) communications among a plurality of participants. The RCS server receives a lock request from a participant of the message thread to lock the message thread and in response thereto modifies the metadata associated with the message thread to indicate that the message thread is locked. A request to join the message thread is then received by the RCS server, where the request is rejected in response to the RCS server determining that the metadata associated with the message thread indicates that the message thread is locked.

Abstract: Techniques are described for delivering subscriber information of a subscriber of a wireless carrier network to an authorized partner. The techniques include receiving, from a requesting entity device, a request for subscriber information of a subscriber, the request comprising a public Internet Protocol (IP) address of a user device associated with the subscriber, determining whether the requesting entity device is associated with an authorized partner based at least on one or more credentials associated with the requesting entity device, in response to determining that the requesting entity device is associated with the authorized partner, routing the request to at least one subscriber database of a plurality of subscriber databases to obtain the subscriber information using the public IP address of the user device, and transmitting the subscriber information of the subscriber to the requesting entity device.

Abstract: The disclosure provides a solution to dynamically configure a connected device using a stock keeping unit (“SKU”) element associated with the connected device. A connected device includes a SKU element which stores identification of multiple service providers. The service provider IDs are associated with configuration templates which facilitate updating a configuration of the connected device with the service providers.

Abstract: A communication device may transmit messages to an Internet Protocol Multimedia Subsystem (IMS) network through an untrusted non-3GPP radio access network (RAN). A process to be implemented on a communication device may include generating a message having a location identifier (ID) that is indicative of a current location of the communication device, and transmitting the message, through an untrusted non-3GPP RAN, to a node within the IMS network. A process to be implemented on one or more nodes of the IMS network may include receiving, from a communication device and via an untrusted non-3GPP RAN, a message having a location ID, and in response to receiving the message, estimating a current location of the communication device based at least in part on the location ID.

Abstract: In some implementations, a core network device can receive an initiation request of a communication session to an alias number. The core network device can retrieve from a registration database one or more destination number(s) corresponding to the alias number. The core network device can transmit respective indication(s) of the alias number to destination(s) corresponding to the retrieved destination number(s). The core network device can initiate the communication session to one of the destination(s) using the respective one of the retrieved destination number(s). A destination number can correspond to a computing device, e.g.

Abstract: The disclosure provides a solution to dynamically configure a connected device using a stock keeping unit (“SKU”) element associated with the connected device. A connected device includes a SKU element which stores identification of multiple service providers. The service provider IDs are associated with configuration templates which facilitate updating a configuration of the connected device with the service providers.

Abstract: When authorized, a user of a computing device, such as a smart phone, may associate a telephone number that is assigned to a computing device with other computing devices. The other computing devices may or may not have an assigned device number. A user may also select to use the same number as the originating number of an electronic device. For example, a user may specify that each computing device associated with the user utilizes the same telephone number. The user may also specify that a computing device not utilize an assigned number. The associations of a device number with the computing devices may be stored as implicit registration data and/or as hunt groups.

Abstract: One or more timers can be used by an originating UE during setup of a communication session. The timer(s) can be triggered by an originating UE sending a request or receiving a response that uses a first signaling protocol. The timer(s) can further be terminated by the originating UE sending a request or receiving a response that uses a second signaling protocol different from the first signaling protocol, so long as the request/response using the second signaling protocol occurs before timeout of the timer(s).

Abstract: A system and method that allows a mobile device to register for IMS services while the mobile device is roaming in a visited telecommunications network is disclosed. The system receives a request for multiple IMS services from a mobile device while the mobile device is roaming in a foreign network. The system uses an identifier of the foreign network and an associated RAT type to query a policy table containing a list of whitelisted IMS services for the foreign network and associated RAT type. The system processes the requested IMS registrations for services that are whitelisted and does not process requested IMS registrations for services that are not on the whitelist.

Abstract: One or more timers can be used by an originating UE during setup of a communication session. The timer(s) can be triggered by an originating UE sending a request or receiving a response that uses a first signaling protocol. The timer(s) can further be terminated by the originating UE sending a request or receiving a response that uses a second signaling protocol different from the first signaling protocol, so long as the request/response using the second signaling protocol occurs before timeout of the timer(s).

Abstract: In some aspects, a Session Initiation Protocol (SIP) proxy server of an Internet Protocol Multimedia Subsystem (IMS) infrastructure is configured to process SIP registration requests. In operation, the SIP proxy server receives a single SIP registration request that includes a plurality of IMS Public User Identities (IMPUs). The SIP proxy server then authenticates the plurality of IMPUs to determine which of the plurality of IMPUs are authorized IMPUs. A plurality of SIP registrations are then performed by the SIP proxy server, wherein each SIP registration of the plurality of SIP registrations is a SIP registration of a respective authorized IMPU.

Abstract: In some implementations, a computing device may determine a location of the computing device. The computing device may have an associated first phone number. The computing device may determine that the location of the computing device is outside a geographic area in which a carrier associated with the first phone number provides service. The computing device may send a registration request to a local network indicating that the computing device is operating in an over the top mode. The computing device may originate an outgoing call from the computing device. The outgoing call appears to a called party to originate from a second phone number that is different from the first phone number.

Abstract: Network-based device management is described. In an example, a server may receive, from a device, a request to change from a first, locked state to a second state. The server may access data associated with at least one of the device or an account associated with the device, and may compare the data with one or more predetermined rules. Satisfaction of the one or more predetermined rules may be necessary to effectuate a change from the first, locked state to the second state. The server may determine that the data satisfies the one or more predetermined rules and the server may send, to the device, an instruction to enable the device to change from the first, locked state to the second state. The instruction may direct an application on the device to effectuate a change to the subscriber identity module (SIM) card associated with the device.