394 results about "Point-to-Point Protocol" patented technology

A method of operating a data network may include establishing a data path through the data network between a routing gateway for a subscriber of the data network and a service provider providing a data service. Moreover, the data service may be provided for use at the routing gateway over the data path during a data session. A request may be received from the service provider wherein the request defines a data flow characteristic for the data path between the routing gateway and the service provider providing the data service during the data session. The data flow characteristic may then be transmitted to a node along the data path between the routing gateway and the service provider for enforcement of the data flow characteristic for the data path at the node. More particularly, the data session may be a point-to-point protocol data session. Related methods, data networks, data service providers, routing gateways, and computer program products are also discussed.

A method of operating a data network may include establishing a data path through the data network between a routing gateway for a subscriber of the data network and a service provider providing a data service. Moreover, the data service may be provided for use at the routing gateway over the data path during a data session. A request may be received from the service provider wherein the request defines a data flow characteristic for the data path between the routing gateway and the service provider providing the data service during the data session. The data flow characteristic may then be transmitted to a node along the data path between the routing gateway and the service provider for enforcement of the data flow characteristic for the data path at the node. More particularly, the data session may be a point-to-point protocol data session. Related methods, data networks, data service providers, routing gateways, and computer program products are also discussed.

Methods and apparatus for sending a registration request packet on behalf of a node that supports PPP but does not support Mobile IP is implemented in a Foreign Agent. The method comprises accepting a call from the node and receiving authentication information associated with a PPP authentication protocol from the node, the authentication information enabling a PPP node to be authenticated. From this authentication information, a PPP node profile is obtained. The PPP node profile includes registration information associated with the node that enables proxy registration to be performed by the Foreign Agent on behalf of the node, where the registration information associated with the node identifies a Home Agent associated with the node. The registration information may also include other information that may be pertinent to the composition of a registration request packet. A registration request packet including the registration information associated with the node is then composed and sent to the Home Agent on behalf of the node. The registration request packet that is sent by the Foreign Agent also may include a registration indicator indicating whether registration being performed by the Foreign Agent on behalf of the node is a re-registration by the Foreign Agent or an initial registration by the Foreign Agent. More particularly, in accordance with one embodiment, the registration request packet includes a sequence number indicating an order within a sequence of one or more registrations performed by one or more Foreign Agents on behalf of the node. From the sequence number, a Home Agent receiving the registration request packet may determine whether the Foreign Agent is performing a re-registration or an initial registration on behalf of the node.

A radio link protocol (RLP) / point-to-point protocol (PPP) design is disclosed for wireless multimedia packet networks that passes corrupted packet data and error location information among OSI layers. The RLP layer provides erasure data frames and optionally error location indicators to the PPP layer. When the PPP layer has access to the erasure data frames, the data frames can be padded with a predefined value, such as all zeroes “0” to prevent error propagation from one data frame (or octet) to the following data frames (or octets). When the PPP layer has access to the error location information, the PPP layer can detect if the PPP packet header is corrupted. When a valid header is detected, the PPP layer forwards the packet payload to the higher layers (TCP, UDP) whether or not the payload is properly received. Thus, the application has access to all the usable information, so the application can determine whether and how to utilize the information. The RLP / PPP design of the present invention allows packets with partially corrupted payloads to still be forwarded to the UDP layer and then to the application layer.

A PCIe fabric includes at least one PCIe switch. The fabric may be used to connect multiple hosts. The PCIe switch implements security and segregation measures for host-to-host message communication. A management entity defines a Virtual PCIe Fabric ID (VPFID). The VPFID is used to enforce security and segregation. The fabric ID may be extended to be used in switch fabrics with other point-to-point protocols.

Method and apparatus are disclosed for flow control over Point-to-Point Protocol (PPP) data links. A method of negotiating such flow control between two PPP peers is disclosed, along with methods for operating flow control across a PPP link. In one embodiment, flow control frames carry an IEEE802.3x MAC control frame payload—the PPP implementation repackages such frames as MAC control frames and passes them to a MAC, which performs flow control. In another embodiment, flow control frames allow flow control commands to be applied differently to different service classes such that PPP flow can be controlled on a per-class basis.

The Aircraft IP Subnet System provides wireless communication services to passengers located onboard an aircraft by storing data indicative of individually identified wireless devices that are located onboard the aircraft. The Aircraft IP Subnet System assigns a single IP address to each Point-to-Point Protocol link connecting the aircraft network to the ground-based communication network and creates an IP subnet onboard the aircraft. The IP subnet utilizes a plurality of IP addresses for each Point-to-Point link, thereby to enable each passenger wireless device to be uniquely identified with their own IP address. This is enabled since both Point-to-Point Protocol IPCP endpoints have pre-defined IP address pools and / or topology configured, so each Point-to-Point Protocol endpoint can utilize a greater number of IP addresses than one per link. Such an approach does not change IPCP or other EVDO protocols / messaging but allows this address to be directly visible to the ground-based communication network.