Abstract: Various embodiments provide systems and methods for connecting wireless-enabled products to wireless networks. Customer network credentials may be stored in a server along with a customer identifier (“customer ID”) during one-time registration. When a wireless-enabled product is purchased, a product identifier (“product ID”) and the customer's ID are forwarded to the server, which correlates the two identifiers, linking the purchased product to the customer. When the wireless-enabled product is powered on, the product accesses the server via a public network connection, and sends the product ID and a security token to the server. The server uses the product ID and the security token to authenticate the product. Once authenticated, the server uses the correlated customer ID to look up the network credentials for the customer's private network, and provides the network credentials to the wireless-enabled product.

Abstract: Various embodiments provide systems and methods for connecting wireless-enabled products to wireless networks. Customer network credentials may be stored in a server along with a customer identifier (“customer ID”) during one-time registration. When a wireless-enabled product is purchased, a product identifier (“product ID”) and the customer's ID are forwarded to the server, which correlates the two identifiers, linking the purchased product to the customer. When the wireless-enabled product is powered on, the product accesses the server via a public network connection, and sends the product ID and a security token to the server. The server uses the product ID and the security token to authenticate the product. Once authenticated, the server uses the correlated customer ID to look up the network credentials for the customer's private network, and provides the network credentials to the wireless-enabled product.

Abstract: In an embodiment, a connection is established between first and second Internet of Things (IoT) devices. After a determination is made to execute a proximity detection procedure, the second IoT device outputs an audio emission and a data packet at substantially the same time. The first IoT device detects the audio emission via a microphone and receives the data packet. The first IoT device uses correlation information to correlate the detected audio emission with the data packet, whereby the correlation information is contained in the detected audio emission, the data packet or both. The first IoT device uses the correlation between the detected audio emission and the data packet to calculate a distance estimate between the first and second IoT devices.

Abstract: A communication session between a node seeking network access and a NAS (Network Access Server) is established by having only few exchanges of messages. Upon detecting a physical link between the node and the NAS, the NAS immediately sends an authentication request message to the node. In response, the node sends a request message which includes all parameters options, in addition to responding to the authentication request message, for link configuration and network access control. The NAS then picks and chooses the parameter options and sends back the selected options in a reply message to the node. If the selected options in the reply message meet a threshold, the node straightforwardly transmits user data for network access via the NAS.

Abstract: In an embodiment, a connection is established between first and second Internet of Things (IoT) devices. After a determination is made to execute a proximity detection procedure, the second IoT device outputs an audio emission and a data packet at substantially the same time. The first IoT device detects the audio emission via a microphone and receives the data packet. The first IoT device uses correlation information to correlate the detected audio emission with the data packet, whereby the correlation information is contained in the detected audio emission, the data packet or both. The first IoT device uses the correlation between the detected audio emission and the data packet to calculate a distance estimate between the first and second IoT devices.

Abstract: A generic quality of service (QoS) model that is not dependent on network technology is used to support QoS for communication networks utilizing different network technologies. The generic QoS model may include a superset of all QoS parameters for all network technologies being supported, e.g., 3GPP and 3GPP2. An application at a device may specify QoS for a traffic flow based on the generic QoS parameters in the superset. The generic QoS parameters may be converted to QoS parameters that are specific to a serving network. The converted QoS parameters are exchanged with the serving network and are used while exchanging traffic with the serving network.

Abstract: An apparatus and method for determining an authorized IP service for an access terminal during an establishment of a PPP connection. In an aspect of the disclosure, a data link is established with the access terminal, and a request to authenticate the access terminal is provided to an authentication/authorization server. During authentication, an IP Service Authorized Parameter is provided by the authentication/authorization server, the IP Service Authorized Parameter for indicating the authorized IP service for the access terminal. Thereby, a network layer protocol and a mobility protocol are each configured according to the authorized IP service that corresponds to the IP Service Authorized Parameter.

Abstract: Systems and methodologies are described that facilitate enhanced data service functionality for data services operating in a multi-processor computing environment. As described herein, respective processors and/or other components can be utilized to form a Smart Peripheral Subsystem (SPS). As further described herein, the SPS can operate in association with a modem processor and an application processor at a mobile computing device in order to reduce loading at the application processor and improve memory usage efficiency. In the case of a mobile computing device sharing a network connection with a tethered computing device, the SPS can couple a modem interface associated with the mobile computing device and an interface through which the disparate computing device is tethered to the mobile computing device such that operations such as Layer 2 (L2) framing and/or de-framing, Network Address Translation (NAT), or the like can be offloaded to the SPS under various circumstances.

Abstract: The packets generated by each of multiple packet data applications are provided to a single Point-to-Point Protocol (PPP) stack and a single High-level Data Link Control (HDLC) framing layer to convert data packets into byte streams suitable for transmission through Radio Link Protocol (RLP) connections. Each of the resultant multiple byte streams is then provided to one of multiple RLP connections having different retransmission and delay properties. The RLP connection selected for sending data from each application is based on the grade of service most appropriate for the application. At the receiver, the data from the multiple RLP connections is provided to a single PPP stack.

Abstract: Packet filtering is performed to detect for and discard malformed data packets that would be discarded by a wireless network if received from a wireless device. A cdma2000 network may restart a PPP session upon receiving (1) malformed data packets with source IPv4 addresses different from IPv4 addresses (if any) assigned to the wireless device or (2) malformed data packets with source IPv6 addresses having prefixes different from prefixes (if any) associated with the PPP session. The wireless device may receive data packets from a terminal equipment coupled to the wireless device and/or applications running at the wireless device. The wireless device may filter these data packets with packet filters to detect for malformed data packets with invalid IPv4 addresses, invalid IPv6 address prefixes, and so on. The wireless device discards malformed data packets and sends the remaining data packets to the wireless network.

Abstract: The disclosure is directed to techniques for supporting failover between different network protocol addressing families in a wireless communication network. The techniques may be implemented in a mobile wireless communication device. A logical interface selects a physical interface for access to the network in response to a request from an application module. The network access request issued by the application module need not specify a network protocol type. Instead, upon selection of the physical interface, the logical interface notifies the application of the network protocol type associated with the physical interface. The logical interface may select a physical interface corresponding to a particular network protocol when available, based on connection preferences specified by the application module or a global setting within the device.

Abstract: A method for generating privacy IP address includes pregenerating a first privacy address and generating a second privacy address when the first privacy address is allocated to an application. Addresses may be shared by applications or unique to a single application. A deprecation timer is started when an application binds to an allocated privacy address, now when the privacy address is generated. To minimize traffic flow disruptions a deprecated address is not deleted while the address remains in use. By pregenerating privacy addresses, an address can be promptly allocated to an application with out delays incurred by confirming that a new address is not a duplicate on the system. The method can be implicated on any device using privacy addresses, including mobile handset devices.

Abstract: To initiate dormancy early, a wireless device receives an IP packet from a wireless network and determines whether the received IP packet is an unsolicited IP packet. An unsolicited IP packet may be declared if the received IP packet causes the wireless device to reactivate from dormancy or is not delivered to an application or service running at the wireless device. The wireless device transitions to dormancy early if the received IP packet is deemed to be an unsolicited IP packet and no other events prevent transition to dormancy. The wireless device may use (1) a shortened value for an inactivity timer for a predetermined time duration if an unsolicited IP packet is detected and (2) a nominal value for the inactivity timer thereafter. The wireless device resets the inactivity timer whenever an IP packet is sent or received and transitions to dormancy upon expiration of the inactivity timer.

Abstract: A generic quality of service (QoS) model that is not dependent on network technology is used to support QoS for communication networks utilizing different network technologies. The generic QoS model may include a superset of all QoS parameters for all network technologies being supported, e.g., 3GPP and 3GPP2. An application at a device may specify QoS for a traffic flow based on the generic QoS parameters in the superset. The generic QoS parameters may be converted to QoS parameters that are specific to a serving network. The converted QoS parameters are exchanged with the serving network and are used while exchanging traffic with the serving network.

Abstract: In a communication system in which a roaming node seeking network access among different networks which are implemented with different network interface layer protocols, handoff schemes are instituted whereby the node may freely move from one network to another with reduced levels of interruptions with respect to the network access. Prior to and at the onset of a handoff, the node receives an indication for the handoff. The indication may be embodied in various forms such as a signal message indicating a change of the SID (System Identification), NID (Network Identification), or PZID (Packet Zone Identification). Alternatively, the indication can be in the form of information straightforwardly included in a data packet sent to the roaming node prior to the handoff. As another alternative, the indication can be implemented as distinguishable message patterns sent to the node in which different message patterns can be sent by different networks supporting different network interface layer protocols.

Abstract: This disclosure describes a key update scheme for use in a mobile IP network. The update scheme may be implemented to facilitate key updates between a mobile device and a server computer that authenticates the mobile device. The techniques described herein can facilitate key updates in a manner that accounts for potential message loss during the update routine, mobile device failure during the update routine, or other problems typically encountered in a mobile network settings. In this manner, the techniques can provide a robust scheme for key updates and may improve network security.

Abstract: A method for configuring an IP address to receive broadcast or multicast data flow which modifies the bind( ) Application Programming Interface (API) to survey available local interfaces to determine their ability to be configured to receive data from a particular IP address, configure a interface to receive the IP address if it is so configurable, bind the IP address to that interface. The modified bind*( ) API may interact with one or more interfaces to see if each interface is capable of being configured to the IP address. Alternatively, the modified bind*( ) API determines the configurability of interfaces by consulting the access control list. Policy based routing rules may be implemented so that the modified bind*( ) operation configures the highest priority interface based upon policy parameters.

Abstract: Methods and apparatus for communicating IP datagrams efficiently within communication links employing variable frame sizes bundles IP datagrams into data payloads. The number of datagrams that can fit within a current frame size is determined, a bundle header indicating that the bundle header is associated with a bundled IP datagram is generated that includes information for unpacking bundled IP datagrams. The bundle header is joined to one or more IP datagrams to form a data payload that is communicated as a frame payload without indicating in a frame header that the frame includes bundled IP datagrams. Information in the bundle header enables a receiver processor to extract the IP datagrams from the frame payload without requiring modifications to the frame header. A bundle header may precede each IP datagram, or one bundle header may include a map IP datagrams in the frame payload.

Abstract: Techniques to efficiently filter fragmented datagrams and route fragments are described. For each fragmented datagram, a filtering node obtains filter parameters as fragments for the datagram are received. When all filter parameters are available, the node applies one or more filters on the filter parameters to obtain a filter result for the datagram and stores the filter result in an entry in a routing table. Prior to obtaining the filter result, the node stores all fragments received for the datagram in a memory. When the filter result becomes available, the node processes all fragments already received for the datagram in accordance with the filter result. As each remaining fragment for the datagram is received, the node immediately processes the fragment in accordance with the filter result. When the last fragment is received, the node clears the memory and the routing table entry for the datagram.

Abstract: A method and system that provides for efficient re-synchronization of a PPP link on a Um interface is provided. When the PPP link is connected, if an indication that the communications of the mobile station is associated with a new network server is detected, only the Um interface will undergo PPP configuration renegotiation. The method and system does not require the examination of all data packets for determining whether PPP configuration renegotiation is required.