Abstract: In a system and a method for providing authentication for Rich Communication Services (RCS) application on a user equipment (UE), a Proxy Call Session Control Function (P-CSCF) of the IMS receives a SIP REGISTER request message sent from an IMS Session Initiation Protocol (SIP) client on the UE as part of an authentication of the IMS SIP client. A Serving Call Session Control Function (S-CSCF) of the IMS or a registration service performs an Authentication and Key Agreement (AKA) challenge with the IMS SIP client as part of the authentication. A Home Subscriber Server (HSS) of the IMS or a Unified Data Management (UDM) function provides, upon successful authentication of the IMS SIP client, an initial authorization grant for the IMS SIP client. The RCS application, after obtaining the initial authorization grant, registers for RCS service with the RCS network, via RCS Application Programming Interface Gateway (API GW).

Abstract: In a system and a method for providing communication within IP Multimedia Subsystem (IMS) using a connectionless communication protocol, an IMS access layer, an IMS service layer, a common service utilities layer, a unified data repository layer, and an IMS network repository function (NRF) are provided. The IMS access layer terminates incoming communication that uses connection-oriented communication protocol. The IMS service layer is operatively connected to the IMS access layer and includes at least one micro-service implementing IMS service. The common service utilities layer is operatively connected to the IMS service layer and includes at least one utility accessible to the at least one micro-service. The unified data repository layer is operatively connected to, and accessible by, the common service utilities layer, the IMS service layer and the IMS access layer. The IMS NRF enables a network function (NF) or the micro-service to discover another NF or micro-service.

Abstract: In a system and a method for providing communication within IP Multimedia Subsystem (IMS) using a connectionless communication protocol, an IMS access layer, an IMS service layer, a common service utilities layer, a unified data repository layer, and an IMS network repository function (NRF) are provided. The IMS access layer terminates incoming communication that uses connection-oriented communication protocol. The IMS service layer is operatively connected to the IMS access layer and includes at least one micro-service implementing IMS service. The common service utilities layer is operatively connected to the IMS service layer and includes at least one utility accessible to the at least one micro-service. The unified data repository layer is operatively connected to, and accessible by, the common service utilities layer, the IMS service layer and the IMS access layer. The IMS NRF enables a network function (NF) or the micro-service to discover another NF or micro-service.

Abstract: In a system and a method for providing authentication for Rich Communication Services (RCS) application on a user equipment (UE), a Proxy Call Session Control Function (P-CSCF) of the IMS receives a SIP REGISTER request message sent from an IMS Session Initiation Protocol (SIP) client on the UE as part of an authentication of the IMS SIP client. A Serving Call Session Control Function (S-CSCF) of the IMS or a registration service performs an Authentication and Key Agreement (AKA) challenge with the IMS SIP client as part of the authentication. A Home Subscriber Server (HSS) of the IMS or a Unified Data Management (UDM) function provides, upon successful authentication of the IMS SIP client, an initial authorization grant for the IMS SIP client. The RCS application, after obtaining the initial authorization grant, registers for RCS service with the RCS network, via RCS Application Programming Interface Gateway (API GW).

Abstract: A system, method, and network node for synchronizing supplementary services settings between a database in a circuit-switched network and a database in a packet-switched network are disclosed. An exemplary communication system synchronization node is configured to receive a message containing a change to a supplementary service setting associated with a user equipment (UE) connected to a circuit-switched (CS) network or a packet-switched (PS) network, and communicate the change to the supplementary service setting to one or both of the HLR and the HSS, so that the supplementary service settings in both the HLR and the HSS are updated to reflect the change to the supplementary service setting.

Abstract: Communication systems and methods suitable for use in a Multiple Line Multiple Device service environment, involving a native line and a second shared line, are disclosed. Logic at one or more nodes and application servers is configured to ensure that network handover data, or other information, is only updated for the native line registration but not the shared line. Then when a call is placed or received on the shared line, the call is anchored to the native line based on that network handover data. If, during that call, a request is received to handover the call from a first network having a first communication protocol to a second network having a second communication protocol, the handover occurs based on the anchored native line. In one example embodiment the first network is a Packet Switched network and the second network is a Circuit Switched network.

Abstract: A method for switch user equipment from a Long Term Evolution system to a Circuit Switched system when receiving a voice call is disclosed. The method may comprise: receiving, at an IWF (Internet Working Function) network node, a Mobility Application Part Unstructured Supplementary Service Data (MAP USSD) message identifying a User Equipment (UE) originated from a USSD application, the UE associated with a first Mobile Switching Center (MSC); initiating Circuit Switched Fallback (CSFB) by sending a paging request to the UE; receiving a Cancel Location message associated with the UE from a Home Location Register (HLR) indicative of the UE being associated with a second MSC; forwarding the MAP USSD message to the UE via the HLR and the second MSC; receiving a MAP USSD response message from the UE via the HLR; and forwarding the MAP USSD response message to the USSD application.

Abstract: Communication systems and methods suitable for use with multiple lines associated with one or more devices are disclosed. Exemplary systems and methods provide multi-line, multi-device device capability discovery that allow capability discovery of devices with shared lines.

Abstract: Communication systems and methods suitable for use with multiple lines associated with one or more devices are disclosed. Exemplary systems include a proxy service node to enable registration of multiple lines associated with a device. Exemplary systems can also include a converged database to store and provide access to service-related data.

Abstract: A method for switch user equipment from a Long Term Evolution system to a Circuit Switched system when receiving a voice call is disclosed. The method may comprise: receiving, at an IWF (Internet Working Function) network node, a Mobility Application Part Unstructured Supplementary Service Data (MAP USSD) message identifying a User Equipment (UE) originated from a USSD application, the UE associated with a first Mobile Switching Center (MSC); initiating Circuit Switched Fallback (CSFB) by sending a paging request to the UE; receiving a Cancel Location message associated with the UE from a Home Location Register (HLR) indicative of the UE being associated with a second MSC; forwarding the MAP USSD message to the UE via the HLR and the second MSC; receiving a MAP USSD response message from the UE via the HLR; and forwarding the MAP USSD response message to the USSD application.

Abstract: A Packet Data Network Gateway (PGW) network node of an Evolved Packet Core (EPC) for interfacing with an IP Multimedia Core Network Subsystem (IMS) comprises an IP address assignment functionality module configured to assign both IPv4 and IPv6 addresses to a User Equipment (UE) requesting an IPv6 address, a Network Address Translation-Application Layer Gateway (NAT64-ALG) functionality module and PGW configured to translate between IPv4 and IPv6 addresses, a Gx interface toward a Policy Control and Charging Rules Function (PCRF) network node configured to transmit the UE's IPv4 address to the PCRF, and an SGi interface toward an application node of the IMS configured the UE's IPv4 address to the application node, and to transmit and receive IP media packets between the IMS and the UE after IPv4 and IPv6 address translation.

Abstract: Communication systems and methods suitable for use with multiple lines associated with one or more devices are disclosed. Exemplary systems and methods provide multi-line, multi-device device capability discovery that allow capability discovery of devices with shared lines.

Abstract: A system, method, and network node for synchronizing supplementary services settings between a database in a circuit-switched network and a database in a packet-switched network are disclosed. An exemplary communication system synchronization node is configured to receive a message containing a change to a supplementary service setting associated with a user equipment (UE) connected to a circuit-switched (CS) network or a packet-switched (PS) network, and communicate the change to the supplementary service setting to one or both of the HLR and the HSS, so that the supplementary service settings in both the HLR and the HSS are updated to reflect the change to the supplementary service setting.

Abstract: Communication systems and methods suitable for use in a Multiple Line Multiple Device service environment, involving a native line and a second shared line, are disclosed. Logic at one or more nodes and application servers is configured to ensure that network handover data, or other information, is only updated for the native line registration but not the shared line. Then when a call is placed or received on the shared line, the call is anchored to the native line based on that network handover data. If, during that call, a request is received to handover the call from a first network having a first communication protocol to a second network having a second communication protocol, the handover occurs based on the anchored native line. In one example embodiment the first network is a Packet Switched network and the second network is a Circuit Switched network.

Abstract: Communication systems and methods suitable for use with multiple lines associated with one or more devices are disclosed. Exemplary systems include a proxy service node to enable registration of multiple lines associated with a device. Exemplary systems can also include a converged database to store and provide access to service-related data.

Abstract: A Packet Data Network Gateway (PGW) network node of an Evolved Packet Core (EPC) for interfacing with an IP Multimedia Core Network Subsystem (IMS) comprises an IP address assignment functionality module configured to assign both IPv4 and IPv6 addresses to a User Equipment (UE) requesting an IPv6 address, a Network Address Translation-Application Layer Gateway (NAT64-ALG) functionality module and PGW configured to translate between IPv4 and IPv6 addresses, a Gx interface toward a Policy Control and Charging Rules Function (PCRF) network node configured to transmit the UE's IPv4 address to the PCRF, and an SGi interface toward an application node of the IMS configured the UE's IPv4 address to the application node, and to transmit and receive IP media packets between the IMS and the UE after IPv4 and IPv6 address translation.

Abstract: A co-located ePDG and PGW system comprises an ePDG (Evolved Packet Data Gateway) functionality module, a PGW (Packet Data Network (PDN) Gateway) functionality module co-located with the ePDG functionality module, where the ePDG functionality module has an SWn interface configured for interfacing with an untrusted non-3GPP network, the ePDG functionality module has an interface toward the PGW functionality module configured for transporting control signaling data, and the ePDG functionality module has an S2b-U? interface toward the PGW functionality module configured for transporting IP packet data.

Abstract: A method for switch user equipment from a Long Term Evolution system to a Circuit Switched system when receiving a voice call is disclosed. The method may comprise: receiving, at an IWF (Internet Working Function) network node, a Mobility Application Part Unstructured Supplementary Service Data (MAP USSD) message identifying a User Equipment (UE) originated from a USSD application, the UE associated with a first Mobile Switching Center (MSC); initiating Circuit Switched Fallback (CSFB) by sending a paging request to the UE; receiving a Cancel Location message associated with the UE from a Home Location Register (HLR) indicative of the UE being associated with a second MSC; forwarding the MAP USSD message to the UE via the HLR and the second MSC; receiving a MAP USSD response message from the UE via the HLR; and forwarding the MAP USSD response message to the USSD application.

Abstract: An IP Multimedia Subsystem (IMS) Centralized Services (ICS) Interworking Function (IWF) element comprises an i2 interface to an IMS core network, an i3 interface to a Telephony Application Server (TAS), a Mobile Applications Part-G (MAP-G) interface to a Mobile Switching Center (MSC) for retrieving subscriber identity, a MAP interface to a Home Location Register (HLR) for location management, subscriber management and call handling procedures, and an Sv interface to a Mobility Management Entity (MME) for appearing as a Visitor Location Register (VLR).

Abstract: Described are methods and apparatuses, for selectively terminated custom application in a telecommunications network. A Gateway Mobile Switching Center (GMSC) receives a request to initiate a call session to a subscriber device in a service area of a first Mobile Switching Center (MSC). The GMSC established a dialogue to implement the custom application on the subscriber device. The GMSC receives a message indicating that the subscriber device is moving from the first MSC to a second MSC. The GMSC analyzes a service key of the custom application to determine if the dialogue should be terminated and determines that the dialogue should be terminated so that the custom application is continued on the subscriber device.