Abstract: Techniques for caller verification in Rich Communication Services (RCS) for text messaging are discussed herein. A communication client can be the communication client designated to receive incoming communications for the user equipment. The user equipment may use the communication client to send, to a network device, a Session Initiation Protocol (SIP) instance to set communication client. The SIP instance may include a primary designator and a Universally Unique Identifier (UUID) associated with the client. The network device may store the information for the user equipment including the UUID and capability set. A second user equipment may poll the network device for the communications capabilities of the first user equipment before establishing a connection.

Abstract: An emergency route back number (ERBN) may be assigned for use in emergency calls. A telecommunication network associated that may be associated with a wireless service provider, may identify an emergency call directed to an emergency number (e.g., 9-1-1) that originated from a device that is not associated with a unique phone number such as a shared line, or a communication that utilizes some other indicator to establish the emergency call (e.g., an email address, or some other identifier). When an emergency call is detected that does not have a dedicated phone number, an ERBN is assigned to the communication. This ERBN may be reserved for some period of time after the emergency call ends such that emergency contact centers are able to reach callers back in case of dropped calls, fails, and/or additional emergency services that may need to reach the callers directly.

Abstract: An emergency route back number (ERBN) may be assigned for use in emergency calls. A telecommunication network associated that may be associated with a wireless service provider, may identify an emergency call directed to an emergency number (e.g., 9-1-1) that originated from a device that is not associated with a unique phone number such as a shared line, or a communication that utilizes some other indicator to establish the emergency call (e.g., an email address, or some other identifier). When an emergency call is detected that does not have a dedicated phone number, an ERBN is assigned to the communication. This ERBN may be reserved for some period of time after the emergency call ends such that emergency contact centers are able to reach callers back in case of dropped calls, fails, and/or additional emergency services that may need to reach the callers directly.

Abstract: A carrier network may provide for asymmetric key exchange for end to end encryption between user equipment utilizing capability upload and discovery messages of the carrier network. For example, a carrier network may receive a capability upload message from a first user equipment. The carrier network may determine that the capability upload message includes a key bundle for end to end (E2E) encryption of communications. In response, the carrier network may store the key bundle in a key distribution center (KDC). The carrier network may also receive, from a second user equipment, a capability discovery message requesting capability information for the first user equipment. In response, the carrier network may request and receive the key bundle from the KDC and transmit the key bundle to the second user equipment.

Abstract: When a Rich Communications Services (RCS) data file is to be provided to a terminating user equipment (UE) that is on a different mobile communications network than an originating UE, the network address, or uniform resource locator (URL), of the RCS data file may be modified to indicate that the RCS data file is to traverse a network-to-network interface (NNI). An RCS system on the originating mobile communications network may identify if the terminating UE is on the same or different mobile communications network. If the terminating UE is on a different mobile communications network, then the RCS system may modify the URL to indicate the originating and terminating mobile communications networks and send the URL to an RCS system of the terminating mobile communications network. The modified URL enables retrieval of the RCS data file network by a content system of the terminating mobile communications network.

Abstract: Techniques for caller verification in Rich Communication Services (RCS) for text messaging are discussed herein. A communication client can be the communication client designated to receive incoming communications for the user equipment. The user equipment may use the communication client to send, to a network device, a Session Initiation Protocol (SIP) instance to set communication client. The SIP instance may include a primary designator and a Universally Unique Identifier (UUID) associated with the client. The network device may store the information for the user equipment including the UUID and capability set. A second user equipment may poll the network device for the communications capabilities of the first user equipment before establishing a connection.

Abstract: Systems, methods and apparatuses for implementing enriched calling services for devices may include a first User Equipment (UE) that sends a call request to an IP Multimedia Subsystem (IMS) Core network and a presence server. The IMS core network may determine that the first UE supports enriched calling services and may enable the first UE to perform an enriched calling operation. The IMS core network may forward the call request to a terminating device, such as a second UE and/or a computing device, with the enriched calling operation.

Abstract: Techniques for caller verification in Rich Communication Services (RCS) for text messaging are discussed herein. A communication client can be the communication client designated to receive incoming communications for the user equipment. The user equipment may use the communication client to send, to a network device, a Session Initiation Protocol (SIP) instance to set communication client. The SIP instance may include a primary designator and a Universally Unique Identifier (UUID) associated with the client. The network device may store the information for the user equipment including the UUID and capability set. A second user equipment may poll the network device for the communications capabilities of the first user equipment before establishing a connection.

Abstract: When a Rich Communications Services (RCS) data file is to be provided to a terminating user equipment (UE) that is on a different mobile communications network than an originating UE, the network address, or uniform resource locator (URL), of the RCS data file may be modified to indicate that the RCS data file is to traverse a network-to-network interface (NNI). An RCS system on the originating mobile communications network may identify if the terminating UE is on the same or different mobile communications network. If the terminating UE is on a different mobile communications network, then the RCS system may modify the URL to indicate the originating and terminating mobile communications networks and send the URL to an RCS system of the terminating mobile communications network. The modified URL enables retrieval of the RCS data file network by a content system of the terminating mobile communications network.

Abstract: When a Rich Communications Services (RCS) data file is to be provided to a terminating user equipment (UE) that is on a different mobile communications network than an originating UE, the network address, or uniform resource locator (URL), of the RCS data file may be modified to indicate that the RCS data file is to traverse a network-to-network interface (NNI). An RCS system on the originating mobile communications network may identify if the terminating UE is on the same or different mobile communications network. If the terminating UE is on a different mobile communications network, then the RCS system may modify the URL to indicate the originating and terminating mobile communications networks and send the URL to an RCS system of the terminating mobile communications network. The modified URL enables retrieval of the RCS data file network by a content system of the terminating mobile communications network.

Abstract: Systems, methods and apparatuses for implementing enriched calling services for devices may include a first User Equipment (UE) that sends a call request to an IP Multimedia Subsystem (IMS) Core network and a presence server. The IMS core network may determine that the first UE supports enriched calling services and may enable the first UE to perform an enriched calling operation. The IMS core network may forward the call request to a terminating device, such as a second UE and/or a computing device, with the enriched calling operation.

Abstract: A carrier network may provide for asymmetric key exchange for end to end encryption between user equipment utilizing capability upload and discovery messages of the carrier network. For example, a carrier network may receive a capability upload message from a first user equipment. The carrier network may determine that the capability upload message includes a key bundle for end to end (E2E) encryption of communications. In response, the carrier network may store the key bundle in a key distribution center (KDC). The carrier network may also receive, from a second user equipment, a capability discovery message requesting capability information for the first user equipment. In response, the carrier network may request and receive the key bundle from the KDC and transmit the key bundle to the second user equipment.

Abstract: A telecommunication network provides telecommunication service to a user equipment (UE) and a communication device that is connected to the telecommunication network via a private branch exchange. Both the UE and the communication device utilizing a Mobile Station International Subscriber Directory Number (MSISDN) for the telecommunication service, and the telecommunication network stores a profile associating both the UE and the communication device with the MSISDN. Additionally, the telecommunication network enables communication between the communication device and a communication partner device and notifies the UE of the communication.

Abstract: Techniques for designating non-native communication clients as the primary client for user equipment are discussed herein. A primary client can be the communication client designated to receive incoming communications for the user equipment. The user equipment may use the primary client to send, to a network device, a Session Initiation Protocol (SIP) instance to set primary client. The SIP instance may include a primary designator and a Universally Unique Identifier (UUID) associated with the client. The network device may store the information for the user equipment including the UUID and capability set. A second user equipment may poll the network device for the communications capabilities of the first user equipment before establishing a connection.

Abstract: Techniques for designating non-native communication clients as the primary client for user equipment are discussed herein. A primary client can be the communication client designated to receive incoming communications for the user equipment. The user equipment may use the primary client to send, to a network device, a Session Initiation Protocol (SIP) instance to set primary client. The SIP instance may include a primary designator and a Universally Unique Identifier (UUID) associated with the client. The network device may store the information for the user equipment including the UUID and capability set. A second user equipment may poll the network device for the communications capabilities of the first user equipment before establishing a connection.

Abstract: Systems, methods and apparatuses for implementing enriched calling services for devices may include a first User Equipment (UE) that sends a call request to an IP Multimedia Subsystem (IMS) Core network and a presence server. The IMS core network may determine that the first UE supports enriched calling services and may enable the first UE to perform an enriched calling operation. The IMS core network may forward the call request to a terminating device, such as a second UE and/or a computing device, with the enriched calling operation.

Abstract: Systems, methods and apparatuses for implementing enriched calling services for devices may include a first User Equipment (UE) that sends a call request to an IP Multimedia Subsystem (IMS) Core network and a presence server. The IMS core network may determine that the first UE supports enriched calling services and may enable the first UE to perform an enriched calling operation. The IMS core network may forward the call request to a terminating device, such as a second UE and/or a computing device, with the enriched calling operation.

Abstract: Techniques for caller verification in Rich Communication Services (RCS) for text messaging are discussed herein. A communication client can be the communication client designated to receive incoming communications for the user equipment. The user equipment may use the communication client to send, to a network device, a Session Initiation Protocol (SIP) instance to set communication client. The SIP instance may include a primary designator and a Universally Unique Identifier (UUID) associated with the client. The network device may store the information for the user equipment including the UUID and capability set. A second user equipment may poll the network device for the communications capabilities of the first user equipment before establishing a connection.

Abstract: An emergency route back number (ERBN) may be assigned for use in emergency calls. A telecommunication network associated that may be associated with a wireless service provider, may identify an emergency call directed to an emergency number (e.g., 9-1-1) that originated from a device that is not associated with a unique phone number such as a shared line, or a communication that utilizes some other indicator to establish the emergency call (e.g., an email address, or some other identifier). When an emergency call is detected that does not have a dedicated phone number, an ERIIN is assigned to the communication. This ERBN may be reserved for some period of time after the emergency call ends such that emergency contact centers are able to reach callers back in case of dropped calls, fails, and/or additional emergency services that may need to reach the callers directly.

Abstract: An emergency route back number (ERBN) may be assigned for use in emergency calls. A telecommunication network associated that may be associated with a wireless service provider, may identify an emergency call directed to an emergency number (e.g., 9-1-1) that originated from a device that is not associated with a unique phone number such as a shared line, or a communication that utilizes some other indicator to establish the emergency call (e.g., an email address, or some other identifier). When an emergency call is detected that does not have a dedicated phone number, an ERBN is assigned to the communication. This ERBN may be reserved for some period of time after the emergency call ends such that emergency contact centers are able to reach callers back in case of dropped calls, fails, and/or additional emergency services that may need to reach the callers directly.