Abstract: Automated unavailability response for call handling is used to notify an incoming caller that a subscriber is unavailable to answer the incoming call. An incoming call that is initiated from an originating caller device is received at a network server for routing to a terminating user device of a specific subscriber. A user profile of the specific subscriber that includes one or more unavailability notification settings for the incoming call is retrieved from a user profile database. An unavailability notification message is selected from a data store based at least on the one or more unavailable notification settings. The unavailability notification message is sent from the network server to the originating caller device.

Abstract: Techniques are described herein for providing call logs for cellular and internet calls that are rerouted to one or more terminating caller devices. The techniques include: organizing a call routing scheme based on call routing configuration settings, the call routing scheme directing routing of incoming calls to one or more user devices that receives service from a telecommunications network; receiving a call log request from a user device that includes a unique identifier of the user device or a user; transmitting the call log request to a database server of the telecommunications network to obtain a call log for an incoming call to the one or more user devices, the incoming call being routed according to the call routing scheme; and sending the call log to the user device to display the call log information at the user device.

Abstract: Techniques are described herein for implementing a conference management tool to start, schedule, and manage conferences. The techniques include receiving a scheduling request to schedule a conference from a user device via a communication channel. The communication channel can include a chatbot that is configured to access a calendar and an address book to fulfill the scheduling request. The chatbot may add a calendar association comprising the conference information to the calendar and retrieve contact information associated with one or more participants of the conference from the address book. The chatbot may also send a conference notification to the one or more participants, wherein the conference notification includes conference information that is associated with a conference code that may be presented to the user device.

Abstract: The use of application servers to publish the social presence information of users to a presence server of the wireless carrier network may reduce signaling and communication traffic between user devices and the wireless carrier network. The use of application servers may also provide social presence information publishing capabilities when user devices of users do not have such publishing capabilities or are otherwise unable to do so. An application server may receive one or more user-defined social presence settings of a user from an access portal provided by the application server. Social presence information is generated for the user based on the one or more user-defined social presence settings at the application server. The social presence information for the user is sent from the application server to a presence server of a wireless carrier network.

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 providing call logs for cellular and internet calls that are rerouted to one or more terminating caller devices. The techniques include: organizing a call routing scheme based on call routing configuration settings, the call routing scheme directing routing of incoming calls to one or more user devices that receives service from a telecommunications network; receiving a call log request from a user device that includes a unique identifier of the user device or a user; transmitting the call log request to a database server of the telecommunications network to obtain a call log for an incoming call to the one or more user devices, the incoming call being routed according to the call routing scheme; and sending the call log to the user device to display the call log information at the user device.

Abstract: The use of application servers to publish the social presence information of users to a presence server of the wireless carrier network may reduce signaling and communication traffic between user devices and the wireless carrier network. The use of application servers may also provide social presence information publishing capabilities when user devices of users do not have such publishing capabilities or are otherwise unable to do so. An application server may receive one or more user-defined social presence settings of a user from an access portal provided by the application server. Social presence information is generated for the user based on the one or more user-defined social presence settings at the application server. The social presence information for the user is sent from the application server to a presence server of a wireless carrier network.

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 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 and examples pertaining to identifying a participant of a teleconference using a telephone number or an Internet protocol (IP) address are described. A method for teleconferencing participant identification may involve receiving an IP-based telephone call that includes a telephone number or an IP address. The method may also involve querying databases with the telephone number or the IP address to obtain identifications associated with the telephone number or the IP address. The method may also involve determining a display name for the IP-based telephone call based on the identifications, as well as connecting the IP-based telephone call as a participant to a teleconference that includes other participants. The method may further involve transmitting the display name to a device associated with at least one of the other participants of the teleconference.

Abstract: Methods and computing systems for SIP backend polling based on nonzero SIP subscribe expiration are described. A SIP server receives from a SIP client a Session Initiation Protocol (SIP) subscribe message indicating a nonzero expiration time. Based at least on receipt of the subscribe message indicating a nonzero expiration time, the SIP server initiates a backend polling session to a backend server. The SIP server receives, via the backend polling session, state information and provides the state information to the SIP client.

Abstract: Automated unavailability response for call handling is used to notify an incoming caller that a subscriber is unavailable to answer the incoming call. An incoming call that is initiated from an originating caller device is received at a network server for routing to a terminating user device of a specific subscriber. A user profile of the specific subscriber that includes one or more unavailability notification settings for the incoming call is retrieved from a user profile database. An unavailability notification message is selected from a data store based at least on the one or more unavailable notification settings. The unavailability notification message is sent from the network server to the originating caller device.

Abstract: Systems and methods directed to discovery by a user equipment (UE) of a bot functionality available from an entity during a call set up between the UE and the entity are provided. The UE may initiate call the entity, for example a business, using a session initiation protocol (SIP) in a communication network, and, as a part of SIP signaling, an operator of the communication network may add to a SIP header a profile of the bot functionality offered by the business, which is forwarded to the UE. Once the UE processes the information included in the profile, the UE and the business may communicate using the bot functionality.

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: Methods and computing systems may cause SIP backend polling based on nonzero SIP subscribe expiration. A SIP server receives from a SIP client a Session Initiation Protocol (SIP) subscribe message indicating a nonzero expiration time. Based at least on receipt of the subscribe message indicating a nonzero expiration time, the SIP server initiates a backend polling session to a backend server. The SIP server receives, via the backend polling session, state information and provides the state information to the SIP client.

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: In an IMS communications infrastructure, RCS communications may be received from originating devices and forwarded to receiving devices. Specifically, RCS provides for geolocation messages to allow an originating user to send his or her location to a receiving user. In certain cases, however, the receiving user may have a device that does not support RCS. In this case, the IMS infrastructure extracts location coordinates from the XML content of the RCS geolocation message and uses them to construct an HTML hyperlink to an online mapping service. The hyperlink is then sent as part of an SMS or MMS message to the legacy device of the receiving user. Upon selecting the hyperlink, the receiving user is taken to a web page or other resource that shows a map of the location indicated by the RCS geolocation message.

Abstract: In an IMS (IP multimedia system) and/or RCS (rich communication services) environment, devices that support origination forking of various message types are configured to register with an IMS network and to provide an indication that they support origination forking. The IMS network is configured to record this information for its subscribing devices. When the IMS network receives a message request from an origination device, the message request is forwarded to termination devices as well as to other supporting devices that are associated with the user of the origination device.

Abstract: Systems and methods directed to discovery by a user equipment (UE) of a bot functionality available from an entity during a call set up between the UE and the entity are provided. The UE may initiate call the entity, for example a business, using a session initiation protocol (SIP) in a communication network, and, as a part of SIP signaling, an operator of the communication network may add to a SIP header a profile of the bot functionality offered by the business, which is forwarded to the UE. Once the UE processes the information included in the profile, the UE and the business may communicate using the bot functionality.

Abstract: In an IMS (IP multimedia system) and/or RCS (rich communication services) environment, devices that support origination forking of various message types are configured to register with an IMS network and to provide an indication that they support origination forking. The IMS network is configured to record this information for its subscribing devices. When the IMS network receives a message request from an origination device, the message request is forwarded to termination devices as well as to other supporting devices that are associated with the user of the origination device.