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: 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: A policy enhancement for mixed capabilities of devices may include a first User Equipment (UE) that publishes to a presence server via an IP Multimedia Subsystem (IMS) Core network and a Rich Communication Services (RCS) node. A second UE may subscribe to the first UE by requesting information about the first UE from the presence server. The presence server may determine that the first UE is one of multiple instantiations of a same device. The presence server may determine that a third UE is another instantiation of the same device as the first UE, and that the third UE is a lesser-capable device (e.g., non-Universal Profile enabled) with respect to the first UE. The presence server may send a notify message including a capability indicator associated with the third UE to the second UE, and/or the notify message may omit a capability indicator associated with the first UE.

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: A policy enhancement for mixed capabilities of devices may include a first User Equipment (UE) that publishes to a presence server via an IP Multimedia Subsystem (IMS) Core network and a Rich Communication Services (RCS) node. A second UE may subscribe to the first UE by requesting information about the first UE from the presence server. The presence server may determine that the first UE is one of multiple instantiations of a same device. The presence server may determine that a third UE is another instantiation of the same device as the first UE, and that the third UE is a lesser-capable device (e.g., non-Universal Profile enabled) with respect to the first UE. The presence server may send a notify message including a capability indicator associated with the third UE to the second UE, and/or the notify message may omit a capability indicator associated with the first UE.

Abstract: Techniques are described herein for implementing a presence application server to handle Universal Profile (UP) transfers over roaming. The presence application server may receive a Session Initiation Protocol (SIP) request from a user device. The SIP request can include presence information of the user device, P-Access-Network-Info (PANI), and a subscriber identifier of a subscriber associated with the user device. Based at least on the presence information, the presence application server can determine whether the user device is UP capable. Additionally, the presence application server can determine whether the user device is roaming based at least on the PANI. If the user device is roaming, the presence application server can indicate that the user device is roaming and remove a tuple associated with the presence information indicating the UP capabilities of the user device in a SIP response. Removing the tuple suspends the user device's UP capabilities.

Abstract: Techniques are described herein for implementing a presence application server to handle Universal Profile (UP) transfers over roaming. The presence application server may receive a Session Initiation Protocol (SIP) request from a user device. The SIP request can include presence information of the user device, P-Access-Network-Info (PANI), and a subscriber identifier of a subscriber associated with the user device. Based at least on the presence information, the presence application server can determine whether the user device is UP capable. Additionally, the presence application server can determine whether the user device is roaming based at least on the PANI. If the user device is roaming, the presence application server can indicate that the user device is roaming and remove a tuple associated with the presence information indicating the UP capabilities of the user device in a SIP response. Removing the tuple suspends the user device's UP capabilities.