T-mobile Usa, Inc.

Kameswaran Arunachalam

Karunakalage Viraj Rakitha Silva

Rahul Pal

Ramesh Kalathur

Aziz Motiwala

Jeffery A Smith

Ruchir Sinha

Kunal Prakash Barawkar

Rushabhkumar Patel

Saravana Velusamy

Praveen Singaram Muthukumar

Anandajothi Muttayane

Rajesh Gulati

Zenaida Castro Canlas-Factora

Samir Ramesh Shura

Solutions for providing a data traffic session for a user equipment (UE) over a wireless network comprises: receiving, by a session management node (e.g., a session management function, SMF), for a packet routing node (e.g., a user plane function, UPF), an indication of supported interne protocol (IP) traffic type (e.g., IPv4 or IPv6), wherein the indication of supported IP traffic type indicates support for a first IP traffic type or support for a second IP traffic type; allocating, by the session management node, to the packet routing node, a set of IP addresses based on at least the indication of supported IP traffic types, wherein allocating the set of IP addresses comprises allocating only supported IP addresses and withholding allocation of unsupported IP addresses; and providing, to the UE, using an IP address of the set of IP addresses, the data traffic session through the packet routing node.

Advertisement of supported ip version by packet routing nodes

The authorized IP addresses configured at components in an IMS network may become out of sync with a first pool of IP addresses provided by a core network to UEs. This may result in emergency communications being received at the IMS network from a UE using a first IP address of the first pool of IP addresses that is not recognized by the IMS network. A session management component of the core network may automatically assign a second IP address from a second pool of IP addresses based on determining the session management component has not received an update notification from the IMS network within a threshold time (e.g., 500 milliseconds, 1000 milliseconds, etc.) from transmitting a request to establish a packet data communications session to the IMS network using the first IP address. The IMS network may then receive packets from the second IP address.

Efficient emergency communications fallback

Systems and methods discussed herein are directed to method for connecting a communication device to a data network via a network, e.g., a wireless communication network, and preventing the communication device from overriding a DNS selection by an operator of the network. The method includes receiving, from a communication device, e.g., an electronic device, a request to connect to a data network, e.g., the Internet, via a wireless communication network. A response message may be provided to the communication device, where the response message comprises (i) a configuration setting for the communication device to use domain name system (DNS) internet protocol (IP) addresses provided by an operator of the wireless communication network when accessing the data network and (ii) a data bit disabling the communication device from overriding the configuration setting. Connection of the communication device to the data network is then facilitated via the wireless communication network.

Wireless communication network operator defined DNS server selection

A carrier network may provide connection establishment and routing optimization for Service Capability Exposure Function (SCEF). For example, a Mobility Management Entity (MME) component may transmit, to a SCEF, a connection request to establish a session, the request using a first SCEF identifier (ID). The MME may receive, from a particular SCEF instance of the SCEF, an answer for the session, the answer including an identifier that is different from the first SCEF-ID, the identifier associated with the particular SCEF instance. The MME may transmit, to the particular SCEF instance, a subsequent message for the session, wherein a second SCEF-ID of the subsequent message is associated with the identifier and is different from the first SCEF-ID.

Routing optimization for service capability exposure

A first time that a Domain Name System (DNS) response message is sent by the gateway server of a network to a user device may be determined, the DNS response message being generated by a Local DNS server of the network in response to a DNS request message from the user device for routing via the gateway server to the user device. A second time that a client handshake message for an external server identified by a network address in the DNS response is received at the gateway server may be determined, in which the client handshake message is sent by the user device. A roundtrip time for the network that is a time difference between the first time and the second time is calculated. The roundtrip trip time is then halved to obtain a network latency time measurement for the network.

Network latency time measurement using DNS and web server messages

Growing community of inventors

Redmond, WA, United States of America

Kameswaran Arunachalam