WO2001019027A9 - Procedes de detection rapide d'un protocole - Google Patents

Procedes de detection rapide d'un protocole

Info

Publication number
WO2001019027A9
WO2001019027A9 PCT/US2000/024623 US0024623W WO0119027A9 WO 2001019027 A9 WO2001019027 A9 WO 2001019027A9 US 0024623 W US0024623 W US 0024623W WO 0119027 A9 WO0119027 A9 WO 0119027A9
Authority
WO
WIPO (PCT)
Prior art keywords
contents
bytes
communication device
information
byte
Prior art date
Application number
PCT/US2000/024623
Other languages
English (en)
Other versions
WO2001019027A2 (fr
WO2001019027A8 (fr
WO2001019027A3 (fr
Inventor
Nischal Abrol
Marcello Lioy
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to CA2384162A priority Critical patent/CA2384162C/fr
Priority to DE60040916T priority patent/DE60040916D1/de
Priority to EP00961656A priority patent/EP1210829B1/fr
Priority to AU73578/00A priority patent/AU7357800A/en
Priority to JP2001522721A priority patent/JP4472228B2/ja
Publication of WO2001019027A2 publication Critical patent/WO2001019027A2/fr
Publication of WO2001019027A3 publication Critical patent/WO2001019027A3/fr
Publication of WO2001019027A9 publication Critical patent/WO2001019027A9/fr
Priority to HK03108209A priority patent/HK1056073A1/xx
Publication of WO2001019027A8 publication Critical patent/WO2001019027A8/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/204—Multiple access
    • H04B7/216—Code division or spread-spectrum multiple access [CDMA, SSMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation

Definitions

  • This invention generally relates to the field of wireless communications. More particularly, the present invention relates to a novel method and system for performing early protocol and configuration message detection without having to unframe entire PPP packets.
  • CDMA Code Division Multiple Access
  • CDMA is a digital radio-frequency (RF) channelization technique defined in the Telecommunications Industry Association/Electronics Industries Association Interim Standard-95 (TIA/EIA IS-95), entitled “MOBILE STATION-BASE STATION COMPATIBILITY STANDARD FOR DUAL- MODE WIDEBAND SPREAD SPECTRUM CELLULAR SYSTEM", pubHshed in July 1993 and herein incorporated by reference.
  • Wireless communication systems employing this technology assign a unique code to communication signals an d spread these communication signals across a common (wideband) spread spectrum bandwidth.
  • CDMA Code Division Multiple Access
  • FIG. 1 illustrates the basic elements of such a wireless data communication system 100.
  • System 100 allows a mobile terminal equipment, TE2 device 102 (e.g., the terminal equipment such as laptop or palmtop computer) to communicate with an Interworking Function (IWF) 108.
  • System 100 includes a wireless communication device, MT2 device 104 (e.g., wireless telephone), and a Base Station/Mobile Switching Center (BS/MSC) 106.
  • TE2 device 102 e.g., the terminal equipment such as laptop or palmtop computer
  • IWF Interworking Function
  • System 100 includes a wireless communication device, MT2 device 104 (e.g., wireless telephone), and a Base Station/Mobile Switching Center (BS/MSC) 106.
  • BS/MSC Base Station/Mobile Switching Center
  • the IWF 108 serves as a gateway between the wireless network and other networks, such as the Public Switched Telephone Network or wireline packet data networks providing Internet- or Intranet-based access. As shown in FIG. 1, the IWF 108 is coupled to the BS/MSC 106, via the L interface. Often the IWF 108 will be co-located with the BS/MSC 106.
  • the TE2 device 102 is electronically coupled to the MT2 device 104 via the R m interface.
  • the MT2 device 104 communicates with the BS/MSC 106 via the wireless interface U m .
  • the TE2 device 102 and the MT2 device 104 may be integrated into a single unit or may be separated out, as in the case of an installed mobile phone unit in which a laptop is the TE2 device 102 and the transceiver is the MT2 device 104. It is important to note that, as indicated by FIG. 2, the combination of the TE2 device 102 and the MT2 device 104, whether integrated or separate, is generally referred to as a mobile station (MS) 103.
  • MS mobile station
  • IP Internet Protocol
  • RRC 791 Request For Comment 791 entitled, "INTERNET PROTOCOL DARPA INTERNET PROGRAM PROTOCOL SPECIFICATION,” published September 1981, and herein incorporated by reference.
  • the IP protocol is a network layer protocol that encapsulates data into IP packets for transmission. Addressing information is affixed to the header of the packet.
  • TP headers e.g., TP version 4
  • TP version 4 contains 32-bit addresses that identify the sending and receiving hosts. These addresses are used by intermediate routers to select a path through the network for the packet towards its ultimate destination at the intended address.
  • the TP protocol allows packets originating at any Internet node in the world to be routed to any other Internet node in the world, given that the originating party knows the IP address of the destination party.
  • PPP Point-to-Point Protocol
  • RRC 1661 Request for Comments 1661
  • PPP PPP
  • the PPP protocol spedfies a method for transporting multiprotocol datagrams over point-to-point links and contains three main components: a method of encapsulating multi-protocol datagrams over serial links; a Link Control Protocol (LCP) for establishing, testing, configuring, and maintaining a data link connection; and a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols.
  • LCP Link Control Protocol
  • NCPs Network Control Protocols
  • the TIA/EIA IS-707.5 standard entitled “DATA SERVICE OPTIONS FOR WIDEBAND SPREAD SPECTRUM SYSTEMS: PACKET DATA SERVICES,” published February 1998, and herein incorporated by reference, defines requirements for support oi packet data transmission capability on TIA/EIA IS-95 systems and specifies a suite of packet data bearer services.
  • TIA/EIA IS-707-A.5 standard entitled “DATA SERVICE OPTIONS FOR SPREAD SPECTRUM SYSTEMS: PACKET DATA SERVICES”
  • TIA/EIA IS-707-A.9 standard entitled “DATA SERVICE OPTIONS FOR SPREAD SPECTRUM SYSTEMS: HIGH-SPEED PACKET DATA SERVICES”
  • IS-707.5 introduces the Network Model, which details the packet data protocol requirements for the R m interface, U m interface, and the L interface.
  • PPP R first PPP link
  • PPPu second PPP link
  • the separate and independent PPP links help support "transparent mobility"; that is, the TE2 device 102 should experience seamless and transparent service, regardless of time and its current IWF 108 point-of- attachment. As such, the TE2 device 102 should not be affected by location changes. For example, the TE2 device 102 should not be affected from PPP renegotiations occurring on the U m link, such as when MT2 device 104 attempts to attach to a different IWF 108.
  • the Network Model operates to isolate the PPP R link from the PPPu link in order to prevent changes on the U m link from affecting the P ⁇ link. In other words, the PPPu link can be renegotiated without forcing the PPP R link to be renegotiated.
  • FIG. 2 illustrates the protocol stacks in each entity of the IS-707.5 Network Model.
  • a protocol stack shown in conventional vertical format, depicting the protocol layers running on the TE2 device 102 (e.g., the mobile terminal, laptop or palmtop computer).
  • the TE2 device 104 protocol stack is illustrated as being logically connected to the MT2 device 104 protocol stack over the P ⁇ interface.
  • the MT2 device 104 is illustrated as being logically connected to the BS/MSC 106 protocol stack over the U m interface.
  • the BS/MSC 106 protocol stack is, in turn, shown as being logically connected to the IWF 108 protocol stack over the L interface.
  • the protocols depicted in FIG. 2 operate as follows: the PPP R protocol 208 on the TE2 102 device encodes packets from the upper layer protocols 204, and the network layer IP protocol 206. The PPP R protocol 208 then transmits the packets across the P ⁇ interface using the TIA/EIA 232- F protocol 210 to the TIA/EIA-232-F-compatible port on the MT2 device 104 running the TIA/EIA 232-F protocol 212.
  • the TIA/EIA-232-F standard is defined in "INTERFACE BETWEEN DATA TERMINAL EQUIPMENT AND DATA CIRCUIT-TERMINATING EQUIPMENT EMPLOYING SERIAL BINARY DATA INTERCHANGE", published in October 1997 and herein incorporated by reference. It is to be understood that other standards or protocols known to artisans of ordinary skill in the art may be used to define the transmission across the R m interface. For example, other applicable R m interface standards include, the "UNIVERSAL SERIAL BUS (USB) SPECIFICATION, Revision 1.1", published in September 1998, and the "BLUETOOTH SPECIFICATION VERSION 1.0 A CORE, published in July 1999, both incorporated by reference.
  • the TIA/EIA 232-F protocol 212 on the MT2 device 104 receives the packets from the TE2 device 102 and passes them to the PFP R protocol 213.
  • the PPP R protocol 213 unframes the packets encapsulated in the PPP frames and typically, when a data connection is up, the protocol 213 transfers the packets to PPPu protocol 217.
  • Protocol 217 essentially re-frames the packets for transmission to a PPPy peer located in the IWF 108.
  • the Radio Link Protocol (RLP) 216 and IS-95 protocol 214 both of which are well known in the art, are used to transmit the packet-encapsulated PPP frames to the BS/MSC 106 over the U m interface.
  • the RLP protocol 216 is defined in the IS-707.2 standard, entitled “DATA SERVICE OPTIONS FOR WIDEBAND SPREAD SPECTRUM SYSTEMS: RADIO LINK PROTOCOL", published in February 1998 and herein incorporated by reference, as well as the IS-707-A.2 standard, entitled “DATA SERVICE OPTIONS FOR SPREAD SPECTRUM SYSTEMS: RADIO LINK PROTOCOL", published in March 1999 and also incorporated by reference.
  • a corresponding RLP protocol 220 and IS-95 protocol 222 in the BS/MSC 106 transfer the packets to the relay layer protocol 224 for transmission across the L interface to the relay layer protocol 224 on the IWF 108.
  • the PPPy protocol 232 then unframes the received packets and transfers them to the network layer protocol IP 230, which in turn passes them to the upper layer protocols 228 or forwards them to the Internet.
  • the PPP R protocol 213 transfers the packets to the PPPu protocol 217 when a data link connection is established.
  • RFC 1661 provides that Link Control Protocol (LCP) packets must be exchanged and negotiated over each PPP link (i.e., PPP R and PPPy) in order to estabHsh, configure, and test the data link connection.
  • LCP packets comprise Configure-Request, Configure-Ack, Configure-Nak, Protocol-Reject, and Configure-Reject messages to negotiate various options and operate as follows: the Configure-Request packet is used to negotiate configuration options.
  • the Configuration-Ack packet is only transmitted if every configuration option in a received Configuration-Request packet is recognizable and all values are acceptable.
  • the Configure-Nak packet is sent when the requested configuration options in a Configuration-Request packet are recognizable but contain values that are not acceptable and the Configure-Nak Options field is filled with the unacceptable Configure- Request configuration options and suggested values that will work.
  • the Configure-Reject packet is sent when the requested configuration options in a Configure-Request includes configuration options that are not understood by the receiver and the Configure-Reject Options field contains the unrecognized Configure-Request configuration options.
  • IPCP Internet Protocol Control Protocol
  • NCPs Network Control Protocols
  • the TPCP protocol uses the same configuration option negotiation mechanism as the LCP protocol and, much like the LCP protocol, TPCP negotiations occur separately for both the R m interface and the U m interface.
  • the Configuration-Ack packet contains a list of the options, which the Sender is acknowledging.
  • the MT2 device 104 monitors the received and transmitted Configuration-Ack packets over the R m and U m interfaces and stores the value of each option in a storage device, such as a computer memory. All configuration options have default values, defined by RFC 1661, which are used when the corresponding configuration option is not negotiated. It is to be noted that the configuration option default values may be defined by other RFCs, such as, for example, RFC 1877 entitled "PPP Internet Protocol Control Protocol Extensions for Name Server Addresses" published in December 1995 and incorporated by reference.
  • the PPPu link can be renegotiated without forcing the PPP R link to be renegotiated.
  • the MT2 device 104 generally unframes and reframes received PPP packets. Unless packets received by the MT2 device 104 are to be passed to an executing upper layer protocol within the MT2 device 104, the PPP packets are unframed only to be reframed for subsequent transmission to a PPP peer protocol. This unframing/reframing occurs even when the packets require no further processing in the MT2 device 104.
  • the LCP and IPCP mechanisms can negotiate to establish identical configuration options for both the U m and R ⁇ , interfaces.
  • all of the PPP data packets could "pass through", from one interface to the other, without the MT2 device 104 unframing/reframing the packets.
  • the MT2 device 104 performs too many unnecessary PPP packet unframing/reframing operations. Such operations adversely affect the processing resources and throughput latency of the MT2 device 104.
  • the configuration options change, they must be renegotiated, which militates in favor of unframing/reframing the PPP packets.
  • the MT2 device 104 is mobile, it is capable of moving to an area that is served by an IWF 108 that is different from the original IWF 108. When this happens, the MT2 device 104 will be "handed off" to the new IWF 108 for service. This handoff requires the renegotiation of particular LCP and IPCP configuration options over the U m interface as well as the intervention of the MT2 device 104.
  • the packets containing the configuration option messages e.g., Configure- Request, Configure- Ack, Configure-Nak, etc.
  • the packets containing the configuration option messages were simply "passed through", without unframing or examining the contents of the packets, the packets would force the end-to-end resynchronization of the entire link which would terminate the independence of the R m and U m links.
  • the present invention addresses the need identified above by providing a method and system that detects protocol and configuration messages in a PPP packet without having to unframe the entire packet.
  • Methods and systems consistent with the principles of the present invention as embodied and broadly described herein include a communication device that receives a plurality data frames, wherein the communication device is capable of ascertaining the beginning of an information portion within the received frames.
  • the communications device detects whether the information portion contains configuration information, such as protocol and configuration messages of a predetermined type. In a first embodiment, the detection is achieved by the communication device unescaping the contents of a plurality of bytes and determining whether the escaped bytes contains the desired configuration information.
  • the communication device determines whether the contents of a particular byte contain the desired configuration information, in escaped or unescaped form, and the communication device continues to sequentially process the bytes within the information portion until the bytes typically containing the desired configuration information are processed or it is determined that the information does not exist.
  • FIG. 1 is a high level block diagram depicting various elements of a wireless communication system.
  • FIG. 2 schematically describes the protocol stacks of a wireless communication system.
  • FIG. 3 is a flow-chart diagrams describing a first embodiment of the invention.
  • FIGS. 4A, 4B are flow-chart diagrams describing a second embodiment of the invention.
  • FIG. 5 describes the general format of a packet encapsulated in a PPP frame.
  • FIG. 5 illustrates the various attributes of such packets.
  • the beginning (and end) of the frame is demarcated by a 1-byte framing flag represented by the hexadecimal character "7E".
  • the following two bytes indicate the protocol address and control field which, for standard PPP packets, are typically designated as the hexadecimal characters "FF" and "03", respectively.
  • the next two bytes indicate the protocol type, such as, for example, the LCP protocol, denoted by the hexadecimal characters "CO” and "21”; the IPCP protocol, indicated by the hexadecimal characters "80” and “21”; or the Van Jacobson protocol compressed state, indicated by the hexadecimal characters "00" (which may be compressed out) and "2D”.
  • the subsequent byte indicates the code or the configuration message, such as Configure-Request, denoted by the hexadecimal character "01”; Configure- Ack, indicated by the hexadecimal character "02”; or Configure-Nak, indicated by the hexadecimal character "03".
  • FIG. 3 is a flow-chart diagram depicting a first embodiment of the present invention. As such, FIG. 3 details the operation of the MT2 device 104 for performing early protocol and configuration message detection in PPP packets.
  • step S305 the MT2 device 104, first scans an incoming data stream to detect the framing flag, indicated by the hexadecimal character "7E". This flag demarcates a frame and can, therefore, be used to indicate the beginning and/or end of packets encapsulated in PPP frames. If the MT2 device 104 has not detected a "7E" framing flag, it keeps scanning the incoming data, as indicated by step S306, until it detects the flag. Once the MT2 device 104 detects the "7E" framing flag, it progresses to step S310.
  • the framing flag indicated by the hexadecimal character "7E”.
  • the MT2 device 104 After detecting a "7E" flag, the MT2 device 104, in step S310, determines whether the next byte is also a "7E” flag. If so, the MT2 device 104 skips that particular byte, as indicated in step S320, and returns back to step S310 to apply the "7E" flag test to the next byte. If the next byte is not a "7E” flag, the MT2 device 104 progresses to step S315. It is important to note that the incoming data stream may contain consecutive "7E" flags, as in the case of back-to-back packets where a "7E" flag, indicating the end of a frame, is juxtaposed to a subsequent "7E” flag, indicating the beginning of a new frame. Steps S310 and S320 operate to filter out the framing flags, enabling the MT2 device 104 to discern where the information portion of the framed packet begins.
  • the MT2 device 104 in step S315, "unescapes” the next X number of bytes, where X corresponds to the relative position of the information sought within the framed-packet.
  • This unescaping is performed because, as is well known in the art, when the PPP protocol is transmitted with asynchronous, HDLC-like framing (i.e., as per RFC 1662), the protocol employs an "escaping technique" to mask certain characters within the information portion of a packet that also function as special control characters. Such characters include the aforementioned "7E" flag as well as the escape flag "7D".
  • the escaping technique stuffs the escape flag "7D" in front of the character and modifies the character in order to neutralize its control function. Therefore, in seeking to detect certain protocol or configuration information from an incoming data stream, the MT2 device 104, in step S315, unescapes the number of bytes necessary to access the information sought in order to uncover its true identity. After unescaping X bytes, the MT2 device 104 proceeds to step S325.
  • step S325 the MT2 device 104 determines whether the unescaped X bytes include the standard PPP address and control field characters "FF" and "03", respectively. Although these characters typically comprise the first and second bytes of the information portion of a PPP packet (see, e.g., FIG. 5), these characters may be compressed out of the packet, thereby affecting the location of the ensuing information bytes. Therefore, the MT2 device 104 must check whether these characters are included within the unescaped bytes of the packet in order to make the necessary adjustments later.
  • these characters typically comprise the first and second bytes of the information portion of a PPP packet (see, e.g., FIG. 5)
  • these characters may be compressed out of the packet, thereby affecting the location of the ensuing information bytes. Therefore, the MT2 device 104 must check whether these characters are included within the unescaped bytes of the packet in order to make the necessary adjustments later.
  • the MT2 device 104 checks to see whether these bytes contain the protocol or configuration message information being sought. If they do, then the MT2 device 104, in step S340, forwards the entire packet to the MT2 device 104 unframer, in order to unframe the packet and engage in the processing indicated by the detected information. If the bytes do not contain the information being sought, the MT2 device 104 sends the entire packet to the MT2 device 104 transmit portion to be forwarded across the pertinent interface, as indicated by step S345.
  • step S335 if the unescaped X bytes include "FF" and "03", the MT2 device 104, in step S335, compensates by unescaping another 2 bytes, in addition to the specified X bytes. This adjusts for the inclusion of the "FF" and "03" characters within the X bytes.
  • the MT2 device 104 then submits the X + 2 unescaped bytes to step S330, where, as stated above, it checks to see whether the unescaped bytes contain the desired information. If they do, then the MT2 device 104, in step S340, forwards the entire packet to the MT2 device 104 unframer. If the bytes do not contain the protocol or configuration message information being sought, the MT2 device 104, in step S345, sends the entire packet to the MT2 device 104 transmit portion to forward the packet across the pertinent interface.
  • the LCP protocol specification is provided within the protocol information portion of a PPP- framed packet.
  • the protocol information is 2 bytes long, typically occupying byte positions 3 and 4 of the information portion of a standard PPP-framed packet.
  • the MT2 device 104 After scanning the incoming data stream and discerning where the information bytes begin (i.e., steps S305, S310, and S320), the MT2 device 104 unescapes the next two bytes (i.e., X equal to 2), as indicated by step S315.
  • step S325 If, in step S325, the first 2 bytes do not include the "FF" and "03" characters, then the MT2 device 104 checks to see whether these bytes contain the LCP information being sought. If it does, then the MT2 device 104, in step S340, forwards the entire packet to the MT2 device 104 unframer, in order to unframe the packet and engage in the processing required by the LCP protocol information. If the bytes do not contain the LCP information, the MT2 device 104 sends the entire packet to the MT2 device 104 transmit portion to be forwarded across the pertinent interface, as indicated by step S345.
  • the MT2 device 104 in step S335, compensates by unescaping the next 2 bytes, in addition to the first two bytes.
  • the MT2 device 104 then submits all four unescaped bytes to step S330, where, as stated above, it checks to see whether these bytes contain the LCP information being sought. If they do, then the MT2 device 104, in step S340, forwards the entire packet to the MT2 device 104 unframer. If the bytes do not contain the LCP information, the MT2 device 104, in step S345, sends the entire packet to the MT2 device 104 transmit portion.
  • this embodiment detects protocol and configuration messages within a PPP packet stream without having to unframe the entire packets. Rather, by unescaping certain bytes within the information portion of the packets, this embodiment provides a system and method that efficiently detects protocol and configuration messages without performing unnecessary PPP packet unframing/reframing operations.
  • FIGS. 4A, 4B are flow-chart diagrams depicting a second embodiment of the present invention.
  • This embodiment detects protocol and configuration messages contained within the information portion of a PPP- framed packet by scanning the incoming data stream and mechanically checking the information bytes in stages, without unframing the packets.
  • the first stage specifically detects the content of the 1-byte address field, contained within the information portion of the packet.
  • the second stage is directed to detecting the contents of the 1-byte control field, which follows the address field. Accordingly, this embodiment is capable of advancing the stages, and detecting the contents of all information fields, until the end of the information portion.
  • a third stage could be directed to detecting the contents of the 2-byte protocol field, which follow the control field.
  • information contained in the later fields of the frame is generally detected after processing and detecting information contained in the preceding fields.
  • the MT2 device 104 To access this field and detect the pertinent information from an incoming data stream, the MT2 device 104 must first identify the beginning of the information portion of the PPP packet and then access and detect the information in the address field. Only after processing the address field information, is the MT2 device 104 ready to access and detect the control field information.
  • FIG. 4A illustrates the first stage of this embodiment.
  • the MT2 device 104 first scans the incoming data stream to detect the framing flag "7E". After detecting the "7E" flag, the MT2 device 104, in step S410, determines whether the next byte is also a "7E" flag. If it is, the MT2 device 104 moves to the next byte, as indicated in step S415, and returns back to step S410 to apply the "7E" flag test to the next byte. If the next byte is not a "7E” flag, the MT2 device 104 progresses to step S420. As stated above with respect to the first embodiment, steps S410 and S415 operate to filter out the framing flags, allowing the MT2 device 104 to identify the beginning of the information portion of the PPP-framed packet.
  • the MT2 device 104 exploits the format of PPP packets to detect the information in stages. As stated above, the first stage of this embodiment is to detect the character "FF".
  • step S420 the MT2 device 104 checks to see whether the first information byte is the escape character "7D". As indicated above, the escaping technique stuffs the escape flag "7D" in front of certain characters and masks them. If the first information byte is not "7D" (i.e., the first information byte is not escaped), the MT2 device 104, in step S425, checks to see if the first information byte is the "FF" character (i.e., in unescaped form). If it is, the MT2 device 104 proceeds to step S435.
  • the MT2 device 104 determines, in step S426, whether there is more information within the framed-packet to be sought, and if there is, the MT2 device 104 moves onto the next stage in step S427. If there is no additional desired information, the MT2 device 104, in step S428, sends the entire packet to the MT2 device 104 transmit portion to forward the packet across the pertinent interface.
  • the MT2 device 104 checks to see whether the next byte is the "FF" character in the escaped format (i.e., hexadecimal character "DF"). If it is, the MT2 device 104 proceeds to step S435. If the next byte is not the "DF" character, the MT2 device 104 proceeds to step S426 where, as stated above, the MT2 device 104 checks to see whether there is more desired information. If there is, the MT2 device 104 moves onto the next stage in step S427. If there is no additional desired information, the MT2 device 104, in step S428, sends the entire packet to the MT2 device 104 transmit portion to forward the packet across the pertinent interface.
  • step S430 the next byte is the "FF" character in the escaped format (i.e., hexadecimal character "DF")
  • step S435 it checks to see whether there is more information to be sought. If there is, the MT2 device 104 moves onto the next stage in step S427. If there is no additional desired information, the MT2 device 104, in step S437, forwards the entire packet to the MT2 device 104 unframer, in order to unframe the packet and engage in the processing indicated by the detected information.
  • the MT2 device 104 After completing the first stage of the embodiment (i.e., the detection of the "FF" character in the protocol address field), the MT2 device 104 must, consistent with the object of the representative example, endeavor to detect the "03" character in the control field. As noted above, this detection is referred to as the second stage detection for this embodiment and is depicted in FIG. 4B.
  • the MT2 device 104 determines, once again, whether the next byte is the "7D" character. As stated above, this determination is used in case the characters within the relevant information field were escaped. If the next byte is not the "7D" character, the MT2 device 104, in step S445, determines whether the byte is the "03" character (i.e., in unescaped format). If it is, the MT2 device 104 progresses to step S435 where, as previously noted, the MT2 device 104 determines whether there is additional information being sought, and if there is the MT2 device 104 moves onto the next stage, as per step S427.
  • the MT2 device 104 in step S428, forwards the entire packet to the MT2 device 104 transmit portion to forward the packet across the relevant interface.
  • the MT2 device 104 determines that the following byte is the "7D" character, it checks to see, in step S450, whether the subsequent byte is the "03" character in the escaped format (i.e., hexadecimal character "23"). If the subsequent byte is not the "23" character, the MT2 device 104 proceeds to step S426, to determine whether to move onto the next stage, as in step S427, or send the entire packet to the MT2 device 104 transmit portion to forward the packet across the pertinent interface, as in step S428.
  • step S435 determines whether to move onto the next stage, as in step S427, or forward the entire packet to the MT2 device 104 unframer, as in step S437.
  • this embodiment detects protocol and configuration messages within a PPP packet stream without having to unframe the packets. Rather, this embodiment scans the incoming data stream and mechanically checks the information bytes in stages. These stages correspond to the information fields of the PPP-framed packets and, therefore, this embodiment detects the desired information sequentially without performing unnecessary PPP packet unframing/reframing operations and without ignoring messages affecting link configurations.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Communication Control (AREA)

Abstract

L'invention concerne un procédé et un système de détection de protocole et de messages de configuration dans un paquet PPP ne nécessitant pas le retrait du cadre de l'ensemble du paquet. Le procédé comprend un dispositif de communication (MT2) qui reçoit une pluralité de trames de données (S306) et qui est conçu pour contrôler le début d'une portion (S305) d'informations dans les trames reçues. Le dispositif de communication détermine si la portion d'informations contient des informations de configuration, telles que le protocole et les messages de configuration de type prédéterminé. Dans un premier mode de réalisation, le dispositif de communication effectue la détection en retenant (S315) le contenu d'une pluralité d'octets et en déterminant (S325, S330, S335) si les octets échappés contiennent les informations de configuration désirées. Dans un second mode de réalisation, le dispositif de communication détermine si le contenu d'un octet particulier présente les informations de configuration désirées, sous une forme échappée ou retenue, le dispositif poursuit alors le traitement des octets par séquences dans ladite portion d'informations jusqu'à ce que les octets contenant généralement les informations de configuration désirées soient traités.
PCT/US2000/024623 1999-09-08 2000-09-07 Procedes de detection rapide d'un protocole WO2001019027A2 (fr)

Priority Applications (6)

Application Number Priority Date Filing Date Title
CA2384162A CA2384162C (fr) 1999-09-08 2000-09-07 Procedes de detection rapide d'un protocole
DE60040916T DE60040916D1 (de) 1999-09-08 2000-09-07 Verfahren zur protokoll-früherkennung
EP00961656A EP1210829B1 (fr) 1999-09-08 2000-09-07 Procedes de detection rapide d'un protocole
AU73578/00A AU7357800A (en) 1999-09-08 2000-09-07 Methods for efficient early protocol detection
JP2001522721A JP4472228B2 (ja) 1999-09-08 2000-09-07 効率的な早期プロトコル検出方法
HK03108209A HK1056073A1 (en) 1999-09-08 2003-11-12 Method and system for early detection of configuration information of predetermined type

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US39234299A 1999-09-08 1999-09-08
US09/828,623 1999-09-08

Publications (4)

Publication Number Publication Date
WO2001019027A2 WO2001019027A2 (fr) 2001-03-15
WO2001019027A3 WO2001019027A3 (fr) 2002-01-17
WO2001019027A9 true WO2001019027A9 (fr) 2002-10-03
WO2001019027A8 WO2001019027A8 (fr) 2003-12-31

Family

ID=23550209

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/US2000/024622 WO2001019099A2 (fr) 1999-09-08 2000-09-07 Systeme et procede permettant de determiner automatiquement a quel moment repondre a des communications de donnees en paquets entrantes dans un reseau de communication sans fil
PCT/US2000/024623 WO2001019027A2 (fr) 1999-09-08 2000-09-07 Procedes de detection rapide d'un protocole

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/US2000/024622 WO2001019099A2 (fr) 1999-09-08 2000-09-07 Systeme et procede permettant de determiner automatiquement a quel moment repondre a des communications de donnees en paquets entrantes dans un reseau de communication sans fil

Country Status (7)

Country Link
JP (2) JP4846948B2 (fr)
KR (1) KR20020029783A (fr)
CN (2) CN1387732A (fr)
AU (1) AU7357700A (fr)
CA (2) CA2384162C (fr)
IL (1) IL148477A0 (fr)
WO (2) WO2001019099A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8983065B2 (en) 2001-10-09 2015-03-17 Qualcomm Incorporated Method and apparatus for security in a data processing system

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8121296B2 (en) 2001-03-28 2012-02-21 Qualcomm Incorporated Method and apparatus for security in a data processing system
US9100457B2 (en) * 2001-03-28 2015-08-04 Qualcomm Incorporated Method and apparatus for transmission framing in a wireless communication system
US7649829B2 (en) 2001-10-12 2010-01-19 Qualcomm Incorporated Method and system for reduction of decoding complexity in a communication system
US7616637B1 (en) 2002-04-01 2009-11-10 Cisco Technology, Inc. Label switching in fibre channel networks
US7406034B1 (en) 2002-04-01 2008-07-29 Cisco Technology, Inc. Methods and apparatus for fibre channel frame delivery
US7433326B2 (en) 2002-11-27 2008-10-07 Cisco Technology, Inc. Methods and devices for exchanging peer parameters between network devices
US7599655B2 (en) 2003-01-02 2009-10-06 Qualcomm Incorporated Method and apparatus for broadcast services in a communication system
US8098818B2 (en) 2003-07-07 2012-01-17 Qualcomm Incorporated Secure registration for a multicast-broadcast-multimedia system (MBMS)
US8718279B2 (en) 2003-07-08 2014-05-06 Qualcomm Incorporated Apparatus and method for a secure broadcast system
US8724803B2 (en) 2003-09-02 2014-05-13 Qualcomm Incorporated Method and apparatus for providing authenticated challenges for broadcast-multicast communications in a communication system
EP2074712B1 (fr) * 2006-10-03 2012-04-11 ViaSat, Inc. Préattribution de transfert web/en masse de ressources en liaison ascendante dans un système de communication satellite
JP5172447B2 (ja) * 2008-04-23 2013-03-27 京セラ株式会社 データ転送システム及び無線通信機器

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2802188B2 (ja) * 1992-02-04 1998-09-24 シャープ株式会社 変復調装置
JPH07322045A (ja) * 1994-05-20 1995-12-08 Matsushita Electric Ind Co Ltd 通信制御装置及び通信制御方法
FI98027C (fi) * 1995-01-10 1997-03-25 Nokia Telecommunications Oy Pakettiradiojärjestelmä ja päätelaitteisto pakettiradiojärjestelmää varten
US6108704A (en) * 1995-09-25 2000-08-22 Netspeak Corporation Point-to-point internet protocol
US5699350A (en) * 1995-10-06 1997-12-16 Canon Kabushiki Kaisha Reconfiguration of protocol stacks and/or frame type assignments in a network interface device
US5940383A (en) * 1996-01-29 1999-08-17 Qualcomm Incorporated Automatic data service selection
JPH10285361A (ja) * 1997-04-08 1998-10-23 Ricoh Co Ltd 通信装置
US6512754B2 (en) * 1997-10-14 2003-01-28 Lucent Technologies Inc. Point-to-point protocol encapsulation in ethernet frame
US20030156571A1 (en) * 1998-06-05 2003-08-21 Hans-Ake Lund Communications network and method for framing point-to-point frame structures
US6765901B1 (en) * 1998-06-11 2004-07-20 Nvidia Corporation TCP/IP/PPP modem

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8983065B2 (en) 2001-10-09 2015-03-17 Qualcomm Incorporated Method and apparatus for security in a data processing system

Also Published As

Publication number Publication date
CA2384162C (fr) 2011-01-04
CN1437829A (zh) 2003-08-20
JP2003509917A (ja) 2003-03-11
WO2001019099A2 (fr) 2001-03-15
KR20020029783A (ko) 2002-04-19
WO2001019027A2 (fr) 2001-03-15
WO2001019027A8 (fr) 2003-12-31
JP4846948B2 (ja) 2011-12-28
CA2384162A1 (fr) 2001-03-15
CN100361541C (zh) 2008-01-09
CA2384168A1 (fr) 2001-03-15
AU7357700A (en) 2001-04-10
WO2001019099A9 (fr) 2002-10-03
WO2001019027A3 (fr) 2002-01-17
IL148477A0 (en) 2002-09-12
CN1387732A (zh) 2002-12-25
WO2001019099A3 (fr) 2002-01-17
JP2011055528A (ja) 2011-03-17

Similar Documents

Publication Publication Date Title
EP1247385B1 (fr) Procede de suppression des temporisations ppp durant des negociations ipcp
US8098617B2 (en) Method and apparatus for selective examination of PPP packets for renegotiation of a PPP link on a Um interface
US6909714B2 (en) Method and apparatus for determining configuration options negotiated for a communications link employing a network model
CA2384162C (fr) Procedes de detection rapide d'un protocole
EP1155551B1 (fr) Installation simultanee d'un protocole de point a point sur des interfaces um et rm
EP1192826B1 (fr) Synchronisation independante de liaisons a protocole de liaison point a point sur une interface u m? et sur une interface r m?
EP1596554B1 (fr) Maintenir et appliquer sélectivement une compression PPP dans un système de communication sans fil
EP1192827B1 (fr) VERROUILLAGE ET DEVERROUILLAGE SELECTIFS DE TRAMES DE PAQUETS PPP DEPENDANT DES OPTIONS NEGOCIEES SUR LES INTERFACES Um ET Rm
EP1210829B1 (fr) Procedes de detection rapide d'un protocole

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

WWE Wipo information: entry into national phase

Ref document number: 2384162

Country of ref document: CA

ENP Entry into the national phase

Ref country code: JP

Ref document number: 2001 522721

Kind code of ref document: A

Format of ref document f/p: F

WWE Wipo information: entry into national phase

Ref document number: 1020027003102

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 2000961656

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 008154457

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 2000961656

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 1020027003102

Country of ref document: KR

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

AK Designated states

Kind code of ref document: C2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: C2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

COP Corrected version of pamphlet

Free format text: PAGES 1/6-6/6, DRAWINGS, REPLACED BY NEW PAGES 1/6-6/6; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE