TWI376919B - Fast link establishment for network access - Google Patents

Description

IX. INSTRUCTIONS: FIELD OF THE INVENTION The present invention relates generally to packet data communication and, more particularly, to an initial communication session prior to establishing packet data communication for network access. [Prior Art] Global network interconnection allows for fast access to information regardless of geographic distance. 1 shows a simplified diagram of a global network connection, commonly referred to as the Internet, and is indicated by reference numeral 20. Internet 20 is essentially a network of different levels that are linked together. Internet 20 operates under the Ip (Internet Protocol) published by the IETF (Internet Engineering Task Force). The details of the IP can be found in the RFC (Request for Amendment) 791 published by the IETF. A variety of individual networks are connected to the Internet 2, sometimes referred to as LAN (Regional Network) or WAN (Wide Area Network) depending on the size of the network. The figure shows some of the 22, 24 and 26 of these networks. Within each of these networks 22, 24, and 26, there may be multiple pieces of equipment that are interconnected and communicated, such as computers, printers, and printers commonly referred to as nodes (here only proposed - some ). When a node communicates outside its own network via the Internet, an IP address needs to be assigned to this node. The assignment of this IP address can be manual or automatic. For example, manual assignment of the ιρ address can be performed by a network administrator. More often, automatically refers to (four) (four), for example by a dedicated server assignment in the LAN. The examples are illustrated below. Suppose one of the nodes in the network 22 attempts to send a 103860.doc 1376919 packet to another node 34 in the network 24. Under the IP, each data packet needs to have a source address and a destination address. . In this case, the source address is the address of node 3 in network 22. The destination address is the address of node 34 in network 24. Often, node-to-node communication is required prior to network access (e.g., Internet 2). For example, assume that node 3 in network 22 is a laptop. The laptop node 30 does not have direct access to the network 22. However, the laptop node 30 can reach one of the networks 22 (network access server) via some other method of dialing a cable modem over a telephone line, for example. In this case, node 3A typically establishes a ppp (point-to-point protocol) session with the \8 (network access server) 32 in network 22. The packet that is then established between node 30 and network 22 (or any other network via the Internet 2) will be exchanged with the telephone line via the cable modem. The data modem transmits and receives signals asynchronously and continuously via the telephone line, and the data packets exchanged via the telephone line must also be constructed accordingly to be suitable for continuous and non-synchronized data machine links. The advent of wireless technology allows nodes to leave their networks from their original registration to another network. For example, referring back to Figure i, node 3A can be a wireless device such as a pDA (Personal Device Assistant), a cellular phone, or a mobile computer, rather than permanently connecting to the network 22. Wireless node 30 can travel beyond the boundaries of its home network 22. Thus, node 30 can roam away from its home network 22 to an external 'road 26 to gain access to the network 26, or to connect to other networks via the Internet 2' node 30 is also typically associated with the network 26 - (d) (network access server) 33 establishes a ppp session. In this case, the communication between the node and 33 103860.doc is achieved via the air link. On the other hand, the parent data packet between the node 30 and the wireless network must also be constructed to suit the format negotiated during the ρρρ session between the node 3 〇 and the NAS 33 via the air link. Most of the defects are described in RFCs 1661 and 1662 published by the IETF. PPP is a point-to-point protocol in which two nodes are peer-to-peer. That is, neither party assumes the role of a client or assumes the role of a server. Each party may request action from another party' or perform an action to the other party. Essentially, a 'probe and negotiated session between ρρρ-systems' nodes during this session's nodes are identified based on performance and availability from each other's resources and eventually converge into a set of mutuals before any network traffic flows. Acceptable parameter options. 2 shows a sequence flow diagram of an exemplary ppp communication session 34 in which node 30 in the network 26 searches for a link to the NAS 32 to gain access to the Internet. Ppp has a large number of contract components. In the exemplary ppp session shown in Figure 2, 'PPP has one of the components as LCP (Link Control Protocol, One CHAP (Interrogation Signal Exchange Authentication Protocol) 38 and one lpc:p (Internet Protocol Configuration Protocol). First, 'once the physical link is completed, meaning that node 3〇 and NAS 33 can reach each other on the hardware level, for example, need to go through LCP 36. LCP 36 acts as the basis between establishing node 3〇 and NAS 33. The purpose of the communication link. During the LCP36, the node 3〇 exchanges with the NAS33 and negotiates the necessary communication parameter options. The options include: the maximum size of the data packet via the link, 103860.doc 1376919 'step and quality 1 control parameters, Use the ship (high-order data link control) header to block the compression scheme and whether the point is willing to be recognized. The process of LCP 3 6 operates more or less under a signal exchange rule. First, the requester sends by configuration Request message proposal - one or more parameters. The right receiver does not have any parameters 'The receiver responds _ configuration reject message. If the rejected parameter is fatal to the searched key, then The requester must terminate the ppp session. If the parameters are tolerated but the options involving the parameters are not accepted, the responder sends back a configuration denial message. The requestor can terminate the ppp session again or send a different option for the same parameter. Another configuration request message. As mentioned above, PPP is a point-to-point protocol. Node 3〇 or 1^八3 33 can be the requester. This also applies to the role of the responder. All parameters with associated options. It must be negotiated and resolved as described above. As shown in Figure 2, several rounds of negotiation may be required. The general negotiation scheme is basically a simplex process. If the requesting party determines that all required parameters are acceptable to the respondent, then the requesting party Send a final configuration confirmation message to the responder. Once both parties have sent the configuration confirmation message, they transition to the authentication phase. To ensure that both parties are authorized, they must be authenticated. A method of performing authentication is used. Another PPP component CHAP 38. It is typically the nas 33 that initiates the cHAP 38 to verify the identity of the node 3. During the CHAP 38, the NAS 33 sends a message called Interrogation. The message message to node 30. Under CHAP, there is a shared secret used with the challenge message, which is used to calculate a response message using a pre-agreed algorithm. Then section 103860.doc 1376919 point 30 is sent The response message generated by the secret algorithm is sent to the NAS 33. Thereafter, the NAS 33 compares the received response message with the message calculated by the NAS itself. If there is a comparison match, the node 30 is said to pass the CHAP 38, wherein the NAS 33 sends a CHAP. Success message to node 30. No Bay ij, NAS 33 sends a CHAP failure message. Alternatively, authentication can be accomplished by experiencing a PAP (Password Authentication Protocol) without being completed by CHAP 38. In PAP, the node sends only one of the usernames and passwords used to authenticate to the NAS 33. If the verification is passed, the node 30 is said to pass the PAP. If the node 30 requires IP access, it also needs to exchange and negotiate the information related to the IP. For example, where, depending on the IP, node 30 may require an IP address assignment to access Internet 20 (Fig. 1). To accomplish this goal, negotiation and exchange of parameter options is initiated under IPCP 40. In the exemplary PPP session 34, node 30 initially requests an IP address of 0.0.0.0 from NAS 33. In response, NAS 33 sends a configuration denial message suggesting that node 30 uses the IP address a.b.c.d. If accepted, the node 30 will send a message for confirmation to the NAS 33 to affirm the use of the IP address abcd. Finally, when the node 30 agrees to all parameters negotiated during the IPCP 40, the node 30 sends a confirmation message. To NAS 33. Thereafter, the exchange network accesses the user data of the session. The IP data of the sealed network traffic is encapsulated into a PPP framework with parameters and previously negotiated during LCP36. At the end of the network access, node 30 or NAS 33 may send a termination request message to each other, which thereafter responds with a termination confirmation message and ends the communication session 0 103860.doc -10· 1376919 as in Figure 2 and above. It can be seen that there is a significant amount of exchanged messages between node 3 and NAS 33 during ppp session 34. Similarly it takes up a lot! Duration. This is especially true if the PPP session 34 is negotiated via a slow link with a high latency of data. Therefore, there is a need to provide a faster and more efficient way to establish an initial communication link before any next level of data traffic. SUMMARY OF THE INVENTION A communication session between a node searching for network access and a NAS (network access server) is established by only a small number of message exchanges. First, once a physical link is established 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 that includes all other parameter options for link configuration and network access control, in addition to the authentication response. The NAS then collects and selects a set of parameters in a number of parameter options, and then sends the selected option back to the node in a reply message. If the selected option in the reply message satisfies a threshold, the node directly transmits the user data for network access via the NAS. Additionally, a fault tolerant transfer feature can be implemented in which a conventional ppp (point-to-point protocol) can be substituted to continue a communication session if an exemplary embodiment cannot be established in accordance with an exemplary embodiment of the present invention. A method, apparatus, and media for a node for searching for network access is disclosed in accordance with an aspect of the present invention, which includes providing a set of parameter options for authentication, link configuration, and network access in a message The steps or components, and the steps or components for sending this message to a network access node. Another aspect for a network access node is disclosed in accordance with another aspect of the present invention.

103860.doc -11 - 1376919 Method apparatus and media, comprising a step of receiving a message from a node of a search network that includes a set of parameters for authentication, link configuration, and network access Or a component, and a step or component for sending another message relating to the identification of the set of parameter options to the node that is searching for network access. These and other features and advantages will be apparent to those skilled in the art from the following detailed description and the accompanying drawings. [Embodiment] The following description is provided to enable any person skilled in the art to make or use the invention. The details are set forth in the following description for purposes of explanation. It will be appreciated that those skilled in the art will recognize that the invention may be practiced without departing from the scope of the invention. Therefore, the present invention is not intended to be limited by the embodiments shown, but rather in the broadest scope of the principles and features disclosed herein. Figure 3 shows a simplified schematic showing an exemplary implementation of the invention. The entire communication system is indicated by reference numeral 42. here

A wired link, for example, a _ ^zhizhi telephone line link, a node involved in a coaxial cable example. In the embodiment, the communication bar 103860.doc 8 12 1376919 link, or a cable link (only a few are proposed). In addition, the link 45 may also be a wireless link. In that case, the link 45 is an empty interfacing plane. It is assumed in this embodiment that the link 45 is an empty interfacing plane. Node 44 is a mobile device that wirelessly communicates with NAS 46. Network 48 supports wireless technologies such as the cdnia2 standard proposed by tla/eia (Electric K Industry Association/Electronic Industries Association). In this case, the NAS 46 is a PDSN (Packet Data Service Node) coupled to a RAN (Radio Access Network) that communicates with the node 44 via an air link 45 via an RF (Radio Frequency) signal. The PDSN and RAN are known in the art and are not shown in Figure 3 for reasons of clarity and simplicity. Before describing the operational details of the communication system 42, it is helpful to first interpret the various types of different levels of associations and their interrelationships. According to ISO (International Organization for Standardization) and in the network communication technology, ITU-T (International Telecommunication Union Telecommunications Standards Department) proposed 〇si (open system to promote multi-vendor equipment)

Layer 1 begins to layer 5. Thus, the models are interconnected by a hierarchy such as nodes 44 or 46 as shown in Figure 3. Interoperability. That is, each of the agreed classes. Similarly, as long as one of the nodes of the specific order eyebrows 103860.doc is sent out, one of the data twists. ^ eu ^ poor material packets must be processed via the protocol stack 52. In the node, the protocol stack 52 0 is constructed in the form of a combination of software or hardware n n ^ L 4/. Similarly, one of the data packets of the same ridge must be processed in reverse order via the protocol stack 52. For example, suppose that a processing packet is sent to send the resource from a node such as node 44 or 46 (Fig.).

# L ) One of the associations created this data package &. Layer 5 includes HTTP » text transfer protocol, SMTp (service mail transfer protocol), ρτρ (file transfer protocol), and RTP (immediate transfer protocol). Further assume that the data packet is the product of a V〇IP (Internet Voice Protocol) session. Therefore, the data packet must be formatted according to the RTP in layer 5. Need to process time sensitive data privately 7 ^

"Shuanghuan Gonko Packet" is a data packet such as that generated from the rTP agreement in Layer 5. Specific today. Usually, the defective packet is not resent, but only the drop basin, v ± ^ makes the transmission of other subsequent data packets unobstructed. Therefore, the RTp prudential packet is usually transmitted via UDP (user data block statement ~, 钌 钌 G association) in layer 4 (transport layer). Therefore, the data packet from the RTP of layer 5 must be further adapted according to the layer 4 coffee. On the other hand, if the data packet originates from other protocols such as layer 5 of the claws, the data packet is typically sent via TCP (Transmission Control Protocol) in layer 4. Under TCP, the slogan of the data packet is not affected by the tongue. Similarly, always resending a defective packet', although it is possible to slow down the entire data transfer process. Information such as the number of sources and destinations is added to the asset I packet after passing through this transport layer (layer 4). 103860.doc 1376919 Then send the data packet through the transport layer (layer 4) to the network layer (layer 3) for processing. In this particular case, the data packet generated from layer 4 shall be formatted according to IP (eg, based on the source and purpose of the added data packet. It should be noted that for simplicity reasons, only Figure 4 shows Ιρ in layer 3. There are also other ips in addition to ip that perform supplementary functions in layer 3. t. An instance is 1CMP (Internet Control Message Protocol), which is used to send error messages for undelivered data packets. Thereafter, the Bellow packet must be constructed to suit any protocol suitable for the network interface layer (+ layer 2). The previously described ppp (point-to-point association is a layer 2 protocol. According to an exemplary embodiment of the present invention in the network The communication protocol session before the access also involves the network interface layer. The lowest layer of the protocol stack 52 in Figure 4 is the physical layer (layer), which is the entity construction of the data processing transmission. For example, if the communication link 45 (Fig. 3) is a conventional wired link, and the physical layer (layer) relates to the hardware circuit on the nodes 44 and 46 (Fig. 3) via the wire driving signals constituting the link 45. 45 series of empty intermediaries 'the physical layer ( Layer 丨) relates to the air space and hardware circuits that transmit and receive signals via air space on both points 44 and 46 (Fig. 3). For data packets received by nodes such as nodes 44 and 46 (Fig. 3), this The billet packets must be processed in the reverse order (i.e., from layer 1 to layer 5) via the same protocol stack 52. Referring now back to Figure 3. It is assumed that node 44 searches for the withered access via NAS 46 in this example. Before the exchange, the entity link 4 5 must be ready for the 103860.doc 15 1376919 carrier signal. In other words, the physical layer (layer i) of nodes 44 and 45 must exist physically and establish β as mentioned earlier, in this embodiment The communication link 45 is an empty intermediation plane, and the wireless technology supported by the network 48 is cdma2000. The physical layer refers to the radio circuit in the node 44 and the RAN inside the NAS 46. The RAN may include at least one BSC (base station controller) and a plurality of bs (Base station). The RAN, BSC, and BS are not shown in Fig. 3. According to the present embodiment, once the physical layer (layer 1} is established, that is, both nodes 44 and 46 detect mutual entities of each other, then Nas 46 immediately sent A first message is sent to node 44. Figure 5 is a flow diagram showing a communication sequence of messages between node 44 and NAS 46. The entire process is indicated by reference numeral 54. The first message is referred to as a synchronization message and is referenced by reference numeral 56. Representation. Synchronization message 56 includes all possible authentication options available for selection by node 44. These options may include an interrogation message under CHAP (Interrogation Signal Exchange Authentication Protocol) and a PAP (Password Authentication Protocol). Requests for passwords and users are required. In addition to CHAP and PAP, the synchronization message 56 also includes other authentication protocols defined or supported in ppp. As shown in Figure 5, upon receipt of the synchronization message 56, the node 44 responds with a request message 58. In the request message 58, the node 44 includes the necessary authentication information in response to the request made in the synchronization message 56. In addition, node 44 also includes in the request message 58 all of the parameter options required for node 44 to establish a link to the network access via *NAS 46. Whether these parameters with related options involve 103860.doc

-16- 1376919 There is no difference in link configuration, authentication or network access control. That is, the parameters are not based on the functions of the agreement components (such as the LCP (Link Control Coordination) chap (Interrogation Signal Exchange Authentication Protocol) and ipcp (Internet Protocol Control Protocol) described in the PPP. Classification, but in the request message 58 of this embodiment, all parameters with options are included regardless of the function. More specifically, the parameter with the option in the request message 58 may include - a response to the challenge message, or a user name and password (if applicable) 'such as packet size and HDLC (high-level data link control) Link configuration parameters for link 45 of the header blocking compression scheme, as well as parameters for network access such as IP address, DNS (Domain Name System) configuration, and π header compression protocol (if applicable). It should be appreciated that the request message 58 is preferably formatted according to the selection using intentional redundancy to allow the NAS 46 to select options supported by both nodes 30 and 46, thereby allowing both nodes 44 and 46 to quickly end the initial The entire process of link building. In addition to a variety of options, the NAS 46 can selectively select parameters with associated options that are clearly supported by the purpose of increasing the chances of a successful link, thereby reducing the lead time. In other words, the request message 58 essentially acts as an "announcement message with all available parameter options supported by the node material" where the subset of options selected by the NAS 46 should allow the linking process to complete. Therefore, as shown in FIG. 5, once the NAS 46 receives the request message, it immediately responds with a response Λ - reply message 6G. In the reply message (9), nas selects options among various options. The reply message 6 contains the selected parameter options with the relevant configuration values. Frequently, the reply message 60 is connected to the network. 103860.doc

-17· 1376919 The last message required by node 44 before the start. Unlike other agreed methods such as the peer-to-peer PPP protocol described previously, according to this embodiment, no confirmation message is required to confirm or deny. Similarly, the response can be any of the messages of the sync message 56, the request message 58, or the reply message 60, without the need for a confirmation message or a denial message. Responding to the node Only proceed to the next step. Response to any specific requested terms does not imply that this provision is not available or supported. Returning to Figure 5', upon receipt of the reply message 60, if the option selected by the NAS 46 satisfies a certain threshold 'e.g., all of the selected options allow the node 44 to establish a communication link for network access, then the node 44 Transfer user data 62 directly to NAS 46. Moreover, node 44 does not send an acknowledgment message. At the end of the network access, node 44 or NAS 46 may send a termination request message 64 to each other, which thereafter responds with a termination confirmation message 66 and ends the communication session. In the rare case, there may be insufficient configuration options in the request message 58 for the NAS 46 to establish a link for the network access searched by the node 44. That is, the option selected by NAS 46 in reply message 60 may not be sufficient to satisfy the threshold required by node 44 to establish a network access link. The nas 46 still sends a reply message 58 with only the accepted option to ignore the unaccepted option. No message is not necessary. As mentioned earlier, including the proposed option “Ignore 58 + rfij ignored in reply message 6 () is implicitly sloppy”. The option is lacking support. In this case, the NAS 46 cannot establish a network communication' and waits for the node 44 to send a new request message. 103860.doc -18- 1376919 For node 44, if it chooses the link regardless of the parameter option ignored in the reply message 6〇 due to lack of support, for example, the option of ignoring is not fatal, node 44 starts the transmission network. Road communication. On the other hand, if the establishment of the network access link absolutely requires the ignored parameters, for example, in the reply message 6 〇 the center appoints the IP address requested by the defect 44, the network communication cannot be established, and the link is said to be Failure β also shows the entire process 54 in the flow chart of Figure 6.

The link establishment process of the present invention is also configured to have fault tolerant transfer characteristics to other link agreements. In this embodiment, if the section s44*NAS 46 (Fig. 3) does not support the linking process 54 shown in Figures 5 and 6, the conventional PPP step as in the fallback protocol is continued to cause the linking process to be directed to node 44. The final network access for the search.

Essentially, there are two possibilities, which will be described separately below. The first case occurs when node 44 supports the link process 46 not supporting. Reference is now made to Figures 7 and 3 directly. Figure 7 is a flow chart showing the communication sequence of messages between node 44 and NAS 46 in this case. The overall process of the message is indicated by reference numeral 68. Since the node is supposed to link the process 54, once the physical layer (layer is established between the nodes 44 and 46, the node 44 immediately waits for the synchronization message 56. However, since the nas46 does not support the linking process 54, the NAS 46 Synchronous message % is not sent. Conversely, nas 46 sends an Lcp configuration request message 7 under PPP to node 1 and receives LCP configuration request message 7〇, node 44 immediately learns that NAS is lax (four) process 54, and Act quickly to communicate with the NAS 46 via the conventional PPP. Specifically, as shown in Figure 7, back 103860.doc • 19-1376919 豢* - The LCP configuration request message 70, node 44 sends an LCP group State confirmation message 72. Or 'If the LCP option proposed in the configuration request message 70 is not desired, the node may send a configuration message in a manner similar to the conventional PPP. It should be noted that In this embodiment, node 44 or node 46 recognizes whether the received message is a PPP message. As will be described later, the data frame format used in this embodiment is the same as that used by PPP, thereby allowing faster ^Message identification and differentiation. The remainder of the process is generally similar to the process 34 shown in Figure 2. That is, after the successful link, a data communication is established between node 44 and NAS 46. Node 44 or nas 46 may send a termination request message 7 6 ' to each other, thereafter responding with a termination confirmation message 7 8 and ending communication session 68. The flowchart corresponding to process 68 is shown in Figure 8. For simplicity, The conventional PPP step is not shown in Figure 8. The second case occurs when the NAS 46 supports the linking process 54 but the node 44 does not support it. Reference is now made directly to Figures 9 and 3. Figure 9 shows the node 44 in this case. Flowchart of the communication sequence of the message with the NAS 46. The reference number. Word 70 indicates the overall process of the message. It is assumed that the NAS 46 supports the linking process.

'54, so once the physical layer (layer) is established between nodes 44 and 46, the NAS-46 immediately sends a synchronization message 56 to node 44. Since it is also assumed that the node 44 does not support the linking process 54, the node 44 does not recognize the synchronization message 56 once the synchronization message % is received. As previously mentioned and will be explained further below, node 44 can distinguish between a PPP message and a non-ppp message. 103860.doc -20· 1376919 Thus, because the sync message 56 is not recognized, the node 44 rejects the unrecognized sync message 56 using the standard PPP procedure. Conversely, once the physical link between node 44 and NAS 46 is established, the node sends an LCp configuration request message 72. If the NAS 46 receives the LCP configuration request message 72 or one of the synchronization messages % PPP rejection, the NAS 46 immediately goes to all the features related to the linking process 54 (Figs. 5 and 6), and as previously described and in Fig. 2 The conventional PPP process shown is 34 ° • After a successful link, the data communication 74 can be exchanged between node 44 and ]8 848. At the end of the network access, node 444 NAS 46 may send a termination request message 76 to each other, which thereafter responds with a termination confirmation message 78 and ends communication session 70. A flow chart corresponding to process 70 is shown in FIG. For reasons of simplicity and clarity, the conventional PPP step is not shown in FIG. Figure 11 shows the data frame format used in Flow 54 (Figure 5). The frame template for the data packet of process 54 is indicated by reference numeral 80. In essence, template 80 is similar to the corresponding data packet template used by PPP proposed under RFC 1662. In particular, the data frame 8 includes a flag bar U, a bit field bar 84, a control port 86' - agreement number block, a data block 90, and an FCS (frame check sequence) column 92. The flag bar 82 is a bit length and indicates the beginning of a data packet frame. As required by RFC 1662, flag column 82 is typically assumed to be a hexadecimal value of 7E and is used for link process 54 and ? 151> the same value. As also required in RFC 1662, the address field 84 is also a byte length, 103860.doc 8 • 21 · and is typically set to a hexadecimal value of FF. As also entrusted by RFC 1662, control bar 86 is a byte length and is fixed to a hexadecimal value of 03 » In the agreement number block 88, the value in this field indicates what the data packet is. The length of the agreement number column 88 is two bytes. For example, as defined in RFc 1661 and 1662, each Lcp message such as the configuration request message 7 has a hexadecimal value of C021. In this embodiment, each of the messages, such as synchronization message 56, request message 58, or reply message 6 for linking process 54 (Fig. 5), has a unique agreement value that is different from any of the agreed values in PPP. Similarly, it simply distinguishes whether the data packet 8 is a ρρρ packet. The length of the data field 90 is in the range from zero to a larger number of bytes containing the payload of the data or control information. For example, if the value of the protocol number column 88 with a value indicates that the data packet 8 is a request message 58, the data field includes all of the information relating to the parameter options described above. In another example, if the value of the agreement number field 88 has a value indicating the data packet 8 (Fig. 5), the ip data packets generated from the layer 3 are all sealed into the data block 90. The length of the FCS field 92 varies from two bytes to four bytes and contains a code such as a CRC (Cyclic Redundancy Code) to enable the frame 80 to provide basic protection for errors during transmission. In addition to the synchronization message 56, the request message 58, the reply message 6, the termination request 64, and the termination confirmation message (see, for example, FIG. 5) mentioned above, other types of messages may be implemented in the link establishment process 54. Figure 12 shows a few examples 〇103860.doc •22-1376919 Referring now directly to Fig. 3 and Fig. 12», for example, after the extension period of one of the inactive communications is represented by reference numeral 94 in Fig. 12, node 44 *nas μ can send a response request message 96 to other parties to ask about the status of the other party or link 45. For example, if an entity link is not established for link 45 due to a power failure, the sender will not be able to receive a response from response request message 96. Accordingly, the sender may wish to terminate the communication session 54. On the other hand, if the link 45 is still valid, the recipient can respond to the response request message 96 by sending a response reply message 98. Thereafter, the sender can abandon the decision to terminate the communication session 54. The duration of the time interval may be pre-determined. In the exchange user profile 62, the NAS 46 may send an authentication message 99 to the node 44 to request information for further authentication. For example, during the data communication of the rules, node 44 may need to access sensitive information that is only available to certain users. Similarly, NAS 46 can send an authentication message 99 to node 44 for further authentication. In addition to the above-mentioned authentication protocols such as pAp and CHAP, other more elaborate protocol schemes known in the art may be used. An example may be an EAP (Extensible Authentication Protocol) that uses an external server such as an authentication (authorization, authorization, and auditing) server located inside or outside of the network 48 for authentication. Figure 13 is a schematic illustration of a hardware embodiment of an apparatus in accordance with an exemplary embodiment of the present invention, such as node 44 shown in Figure 3, designated by reference numeral 100. It can be built in a variety of forms and incorporated into a device, such as a laptop, PDA, or cellular phone. Apparatus 100 includes a central data stream 103860.doc • 23 - 1376919 row 102 that links several circuits together. The circuits include a cpu (central processing unit) or a controller 104 receiving circuit 106, a transmission circuit 1〇8, and a memory unit 110° right device 100-wireless device, and the receiving and transmitting circuit 106 can be 108 is connected to an RF (Radio Frequency) circuit but is not shown in the figure. The receiving circuit 处理 processes and buffers the signals before sending the received signals to the data bus 1 ° 2. On the other hand, the transmitting circuit 108 sends the data from the data bus 1 〇 2 out of the device 1 Process and buffer this data beforehand. The CPU/controller 104 performs the function of data management of the data bus 1 2 and further performs a function of performing main data processing of the contents of the instruction of the execution of the memory unit. Instead of separately arranging the transmission circuit 1 as shown in FIG. 〇8 and receiving circuit 106' transmission circuit 1〇8 and receiving circuit can be part of CPU/controller 104. The memory unit 110 includes a set of instructions collectively indicated by reference numeral 112. In this embodiment, the instructions include, inter alia, portions such as portions of the agreement stacking function 114, the link establishment client 116, and the ppp function 118. The protocol stacking function 114 performs a protocol stack similar to the stack 52 previously shown and described in FIG. Link establishment client 116 includes a set of instructions in accordance with the processes of such processes as those described in Figures 5-10 described above. The ppp function 118 includes a set of instructions for allowing the device 102 to perform a PPP process. The PPP function 118 can be used independently or as a self-link setup user 116 as described previously. In this embodiment, the 's memory unit 110 is a RAM (random access memory 103860.doc -24·1376919 body) circuit. Illustrative refers to a part of the first part, the first part of the 114, 116 and 118 series of software or modules. The memory unit 11 can be connected to another memory: the memory unit can be volatile or non-volatile Sexual replacement, memory circuit u. Can be composed of other circuit types as: EEPROM (Electrically Erasable Programmable Read Only Memory), Occupation (10) (Electronic Program Read Only Memory), R0M (Read Only Memory), a Integrated Electrical W, optical discs, and other objects well known in the art. The figure Μ schematically shows a hardware implementation of a device according to the invention, such as that shown in Figure 3, which is referenced by reference. The device 120 includes a central data busbar U2 that couples a plurality of circuits together. The circuits include a CPU (Central Processing Unit) or two controllers 124, a receiving circuit 126, a transmission circuit 128, and A memory unit 130. The receiving and transmitting circuits 126 and 128 can be connected to a network data bus φ (not shown), and the device 120 is linked to the network data sink. The receiving circuit 126 is in the network data. Busbar (not shown) The signals are processed and buffered before being sent to the internal data bus 122. The transmission circuit 128 processes and buffers the data from the data bus 122 before it is sent out of the device 12. The CPU/controller 1 24 The responsibility for data management of the data bus i 22 is performed, and the function of processing the main tribute including the contents of the instructions of the execution memory unit 13 is performed. Also, instead of separately arranging the transmission circuit 128 and receiving as shown in FIG. The circuit 126, the transmission circuit 128 and the receiving circuit 126 can be part of the CPU/control I03860.doc -25-8 1376919*. The memory unit 130 includes a set of instructions integrally indicated by reference numeral 134. The shot's instructions include, inter alia, the following sections: protocol stacking function (3), keying server 138, and port function 13. The protocol stacking function 136 performs a protocol stack similar to the stack 52 previously shown and described in FIG. The setup server 138 includes an instruction set βρρρ function 14 根据 according to the process of the processes shown in Figure 5_ι〇 described above, including for allowing The instruction set is executed 120. The ΡΡΡ function 14G can be executed independently or as the self-link establishment server 138 as described previously. The memory unit 130 can be composed of the memory 豸 circuit type mentioned in the _L text, and Further repetitions. It should be noted that the processes ^, 68 and 70 as described and illustrated in Figure 5_1 can also be stored or transmitted on any computer readable medium well known in the art. In the context of the patent, the term "computer" read media" refers to any medium that participates in providing instructions to the CPU/controller just shown and described in Figures 12 and 13 for execution. Such a computer readable medium, if stored, may be in the form of a volatile or non-volatile storage medium similar to the circuit types of memory units 110 and 130 described above. Such computer readable media, if of transmission type, may include coaxial power, metal wire, light and air interfacing surfaces that carry acoustic or electromagnetic waves capable of carrying signals such as machine or computer readable signals. Finally, as described in this embodiment, the layer 3 agreement is described as IP. Khan can be a different version such as IPv4 (Internet Protocol Version 4) and IPv6 (Internet Protocol Edition I03860.doc • 26-1376919). Furthermore, it should be noted that other layer 3 agreements are equally applicable. For example, Layer 3 protocols can be implemented (Internet Protocol Packet Exchange Protocol), Apple-Talk, and various other network protocols of different versions. Further in the exemplary embodiment, node 44 is depicted as a mobile device in wireless communication with ^^8 46. It should be understood that the 'node 44 is preferably stationary. In addition, link 45 need not be an air link. The truth is, link 45 can be a wired link. Further, any of the logic blocks, circuits, and algorithm steps described in connection with the embodiments can be implemented in hardware, software, firmware, or a combination thereof. It will be appreciated by those skilled in the art that these and other changes can be made in the form and details without departing from the spirit and scope of the invention. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic diagram of a global network connection; FIG. 2 is a communication sequence diagram of a communication session of a conventional protocol; FIG. 3 is a schematic diagram of a node involved in an exemplary embodiment of the present invention; 4 is a schematic diagram showing one of the protocol stacks arranged in a hierarchical order; FIG. 5 is a communication sequence diagram of a communication session according to an exemplary embodiment of the present invention; FIG. 6 is a diagram showing an exemplary implementation according to the present invention. FIG. 7 is a communication sequence diagram showing an exemplary embodiment of implementing a fault-tolerant transfer characteristic to a conventional protocol; FIG. 8 is a corresponding flowchart of the communication sequence diagram of FIG. 7. FIG. An example of a fault-tolerant transfer characteristic to a conventional agreement 103860.doc -27- @· 1376919 Another communication sequence of a sexual embodiment. FIG. 10 is a corresponding flowchart of the communication sequence diagram of FIG. 9. FIG. 11 is an illustration according to an illustration. 1 is a schematic diagram of a circuit portion of a node searching for network access; FIG. 12 is a general production sequence diagram of a communication session implementing an additional message type; FIG. 13 is an exemplary embodiment in accordance with an exemplary embodiment A schematic view of a portion of the node search circuit network access points; and FIG. 14 is not intended to be part of the circuit network access node according to one of the embodiments of the exemplary embodiment shown. [Main component symbol description] 20 Internet 22 Network 24 Network 26 Network 30 Node 32 Network Access Server (NAS) 33 Network Access Server (NAS) 34 Node 36 Link Control Protocol (LCP) 38 Interrogation Signal Exchange Authentication Protocol (CHAP) 40 Internet Protocol Configuration Protocol (IPCP) 42 Communication System 44 Node 103860.doc -28- 1376919

45 Communication Link 46 Network Access Server (NAS) 48 Network 50 Backbone Network 52 Protocol Stack 54 Link Process/Communication Session 56 Synchronization Message 58 Request Message 60 Reply Message 62 User Profile 64 Termination Request Message 66 Termination Confirmation Message 68 Communication session 70 LCP configuration request message 72 LCP configuration confirmation message 74 Data communication 76 Termination request message 78 Termination confirmation message 80 Data packet 82 Flag column 84 Address 襕 86 Control shed 88 Agreement number block 90 Poor material shelf 103860. Doc -29-

FCS (frame check sequence) column time interval response request message response reply message authentication message device central data bus CPU (central processing unit) / controller receiving circuit transmission circuit memory unit command protocol stack function link establishment user terminal PPP function Device t data bus CPU (central processing unit) / controller receiving circuit transmission circuit memory unit command protocol stacking function stitching establishment server PPP function

-30-

Claims (1)

1376919 X. Patent Application Scope: A method for a communication session between a node and a search network access node, comprising: receiving, by a network access node, a first message comprising a set of parameter options from the node The set of parameter options defines a plurality of configurations supported by the node for establishing network access, wherein the set of parameter options includes at least one parameter option for authentication, and a plurality of parameter options for link configuration And a plurality of parameter options for network access; selecting a subgroup of the level parameter option for providing network access to the node, wherein the subset of the set of parameter options corresponds to the network Accessing an option supported by the node; and transmitting a second message to the node for establishing the network access, wherein the first message includes the set of parameter options corresponding to an option supported by the network access node The subgroup selected. 2. The method of claim 1 wherein the step further comprises receiving from the node when the selected one of the set of parameter options satisfies a threshold for the node to establish the network access. User data accessed by the network. 3. The method of claim 1, wherein the method further comprises, upon receiving the message from the node, establishing a physical link with the node, and transmitting a synchronization message including the request from the node. 4 _ If the claim 3 is ancient, the land method's further includes, after the link to establish the entity, receives a ppp (point-to-point message) from the node via the link that is fascinating, and borrows double, y ^ } Send another _ message to return ρρρ to communicate with the node. 4 Turning to I03860-1010628.doc 5. The method of claim 1, further comprising, after inactive communication with a predetermined period of the node, The node exchanges a response message. 6' The method of claim 1, further comprising communicating with the node the user profile for the network access and transmitting an authentication message to the node in the network access 7. The method of claim 1, wherein the plurality of configurations further comprises each configuration having respective parameters, wherein at least a portion of the plurality of configurations is redundant in at least a portion of the respective parameters. The method of claim 1, wherein the receiving the set of parameter options further comprises receiving all available parameter options supported by the node. 9. The method of claim 1, wherein the parameter is selected Further comprising selecting the at least one parameter option for authentication, at least one of the plurality of parameter options for link configuration, and at least one of the plurality of parameter options for network access. The method further includes receiving, when the selected one of the set of parameter options, the subgroup for the node to establish a threshold for the network access, receiving a second set of parameter options from the node a second message, the second set of parameter options being different from the set of parameter options in the first message. Μ η. The method of claim 3, wherein the sending the synchronization message further comprises including a plurality of possible authentication options For the node to select from the plurality of possible authentication options. 12. A communication session for a node with a search network access, comprising: < 103860-1010628.doc for Receiving, from the node, a component of a first message comprising a set of parameter options, the set of parameter options defining a plurality of configurations supported by the node for establishing network access, wherein the set of parameter options comprises One less parameter option for authentication, a plurality of parameter options for link configuration, and a plurality of parameter options for network access; a subgroup for selecting one of the set of parameter options for providing a component of network access of the node, wherein the subset of the set of parameter options corresponds to an option supported by the device; and a means for transmitting a first message to the node for establishing the network access Wherein the first message includes the selected subset of the set of parameter options corresponding to the option supported by the component. 13. 14. 15. 16. The device of claim 12, further comprising the group The selected subset of parameter options satisfy the component of the user data received from the node when the node is used to establish a threshold for the network access. The apparatus of claim 12, further comprising, if a physical link is established with the node prior to receiving the first message from the node, transmitting a synchronization message including the authentication request from the node. The device of claim 12, which further includes means for receiving the entity from the node via the entity key after receiving the entity, and for transmitting another PPP by transmitting another PPP The message is directed to the component that communicates with the node in response to the PPP message. The apparatus of claim 12 wherein the plurality of configurations further comprises each '··~'/, having respective parameters, wherein at least a portion of the plurality of configurations are redundant in at least a portion of the respective parameters . Knife 103860-1010628.doc 17. The apparatus of claim 12, wherein the synchronization message further comprises a plurality of possible authentication options for the node to select from the plurality of possible authentication options. 18. A device for a communication session for network access via a network access node, comprising: a memory unit including computer readable instructions for providing a A first message of the group parameter option defining a plurality of configurations supported by the device for establishing a network access, wherein the set of parameter options includes at least one parameter option for authentication - a plurality of a parameter option for link configuration and a plurality of parameter options for network access i send the first message to the network access node; and receive a second message from the network access node to the network a path access node for establishing the network access, wherein the second message includes a selected one of the set of parameter items corresponding to an option supported by the network access node and a pure A processor circuit of a memory unit for processing the computer readable instructions. 19. The device of claim 18, wherein the memory unit further comprises computer readable instructions for the selected subset of the set of parameter options to satisfy the attack for establishing the network access The threshold is initiated when the device is accessed, such as the device of claim 18, wherein the memory unit further includes computer readable instructions for the selected subset of the set of parameter options not being used for When the device establishes the threshold of the network access, send a third message with a second set of parameter options to the network access J03860-10iQ628.doc -4-~--one month The group of parameters of the page is replaced by a parameter that is different from the item in the first message, such as the device of claim 18, and the step is included in the establishment-physical key ^ After the 'received from the network access node' - ρρρ (point-to-point protocol) message center's memory unit step-by-step includes the purpose of redirecting to the network by sending another message Node brain readable instructions. A device of the present invention, wherein the plurality of configurations are configured to have respective parameters, wherein at least a portion of the respective parameters of the plurality of configurations are redundant. One step includes at least a portion of the device as claimed in claim 18, wherein the synchronization message further includes a plurality of possible forging options 'for the node to select from the plurality of possible authentication options, and the memory The volume unit further includes computer readable instructions for selecting one of the plurality of possible authentication options for inclusion in the first message; > a parameter option for authentication. 24 - (d) - means for searching a communication session of a node for accessing a network - comprising: - a memory unit containing computer readable instructions for receiving a set of parameter options from the node 2 First message, The set of parameter options defines a plurality of configurations supported by the node for establishing network access, wherein the set of parameter options includes at least one parameter option for authentication, and a plurality of parameters for keying configuration Option and a plurality of parameters for network access, the item 'used to select a subgroup of the set of parameter options for providing network access to the node' I03860-I0i0628.doc 6919 η is an option supported by the device and is used to send a second message to the node for establishing the network access, wherein the second message includes an option corresponding to the device support a selected subset of the set of parameter options; and a processor circuit coupled to the memory unit for processing the computer readable instructions. 25. The device of claim 24, wherein the memory The body unit further includes computer readable instructions for receiving from the node for the selected subset of the set of parameter options for the node to establish a threshold for the network access Road access information . . 26. The device of claim 24, wherein the memory unit further comprises computer readable instructions for transmitting a reference from the node upon establishment of a physical link with the node prior to receiving the first message from the node Confirm the request synchronization message. 27. The device of claim 24, further comprising, after the establishing the entity link, receiving a ρρρ (point-to-point agreement) message via the entity link, and the memory unit further comprises computer readable instructions to transmit another The ρρρ message turns to communicate with the node in response to the ρρρ message. 28. The device of claim 27, wherein the memory unit further comprises computer readable instructions for providing a data packet to the second message, the data packet having a corresponding data packet substantially similar to the ρρρ message Format data package format. The apparatus of claim 24, wherein the plurality of configurations further comprises each configuration having respective parameters, wherein at least a portion of the plurality of configurations is in 103860-1010628.doc 30. at least a portion of the respective parameters With redundancy. The apparatus of claim 24, wherein the synchronization message further comprises a plurality of possible authentication options 'for the node to select from the plurality of possible authentication options 〃 31. 32. 33. A method for a communication session The communication session is for network access via a network access node, comprising: providing, by a node, a first message comprising a set of parameter options, the set of parameter options defining a plurality of groups supported by the device State for establishing network access, wherein the set of parameter options includes at least one parameter option for authentication, a plurality of parameter options for link configuration, and a plurality of parameter options for network access; Receiving a second message to the network access node; and receiving a second message from the remote access node to the network access node for establishing the network access, wherein the second message includes a corresponding The selected subgroup of the parameter options for the options supported by the network access node. The method of claim 31, further comprising initiating the network access when the selected one of the set of parameter options is for the device to establish a value of the network access. The method of claim 31, wherein the step further comprises: transmitting the second set of parameters when the selected subset of the set of parameter options fails to satisfy the threshold for the device to establish the network access The set of parameter options in the access section H. Parameter option W first message 103860-10l0628.doc 13169\ie.^ κ «/ > » , * I » _ ^ r a sentence, 'j 34. The method of claim 31, further comprising establishing an entity in the After the link, a ppp (point-to-point protocol) message is received from the network access node, and communication with the network access node is made by sending another PPP message to return the ppp message. 35. The method of claim 31, wherein the plurality of configurations further comprises each configuration having a respective parameter, wherein at least a portion of the plurality of configurations has redundancy in at least a portion of the respective parameters. 36. The method of claim 31, wherein the subgroup providing the parameter option further comprises all available parameter options for the keyed configuration, and all available parameter options for network access. 37. The method of claim 31, wherein receiving the synchronization message further comprises receiving a plurality of possible authentication options 'for the node to select from the plurality of possible authentication options, and further comprising selecting the plurality of possible authentications One of the options is as a parameter option for the at least one of the first messages for the clock. 38. A device for a communication session for network access via a network access node, comprising: means for providing a first message comprising a set of parameter options, The group parameter option defines a plurality of configurations supported by the device for establishing network access, wherein the set of parameter options includes at least one parameter option for authentication, a plurality of parameter options for link configuration, and a plurality of parameters a parameter option for network access; means for transmitting the first message to the network access node; and for receiving a second message from the network access node to the network access 103860 -10l0628.doc i1376919 ^ Line: a * ' i; t · point is used to establish the network access component, wherein the second message includes the group corresponding to the option supported by the network access node The subgroup selected by one of the parameter options. 39. The apparatus of claim 38, further comprising: initiating the network access when the selected subset of the set of parameter options meets a threshold for the device to establish the network access member. 40. The apparatus of claim 38, wherein the plurality of configurations further comprises each configuration having a respective parameter, wherein at least a portion of the plurality of configurations has redundancy in at least a portion of the respective parameters. Knife 41. The apparatus of claim 38, wherein the receiving the synchronization message further comprises a plurality of possible authentication options for selecting the node from the plurality of possible authentication options and further comprising selecting the plurality of possible One of the authentication options is used as a component for the at least one parameter option for authentication included in the first message. 42. A computer readable storage medium for use by a device in a communication session for accessing a network via a network access node in a communication system, comprising: At least one instruction of a first message of a set of parameter options defining a plurality of configurations supported by the device to establish network access with θ, wherein the set of parameter options includes at least one for authentication Parameter options, a plurality of parameter options for link configuration, and a plurality of parameter options for network access; at least - instructions for transmitting the first message to the network access node; and 103860-1010628 .doc -9- 1376919 r*· at least one instruction for receiving a second message from the network access node to the network access node for establishing the network access, wherein the second message includes A subgroup selected corresponding to one of the set of parameter options selected by the network access node. 43. The computer readable storage medium of claim 42, further comprising: the selected subset of the set of parameter options for satisfying the device for establishing the network access At the limit, at least the instruction to start the network access begins. The computer readable storage medium of claim 42, wherein the plurality of configurations further comprises each configuration having a respective parameter, wherein at least a portion of the plurality of configurations is redundant in at least a portion of the respective parameters. The computer readable storage medium of claim 42, wherein receiving the synchronization message further comprises a plurality of possible authentication options 'for the node to select from the plurality of possible authentication options, and further comprising selecting the plurality of It is possible to identify one of the options as at least one instruction for the at least one parameter option for authentication included in the first message. A computer readable storage medium for use by a network access node in a communication session for accessing a node using a network in a communication system, the method comprising: At least one instruction of a first message comprising a set of parameter options 'The set of parameter options defines a plurality of configurations supported by the node for establishing network access, wherein the set of parameter options includes at least one for authentication Parameter options, a plurality of parameter options for link configuration, and a plurality of parameter options for network access; a subgroup for selecting one of the set of parameter options for providing the node 103860-1010628.doc • 10· 1376919 47. 48. 49. 胤 6. At least one instruction for network access, one of the beans, and the sub-group of the number of options corresponds to the option supported by the device; The second message in the at least -instruction of the sending-second message to the node for establishing the network access includes the selected subset of the set of parameter options corresponding to the options supported by the device. The computer readable storage medium of claim 46, further comprising: receiving from the node when the selected subset of the set of parameter options satisfies a threshold for the node to establish a network access At least one instruction for user data accessed by the network. The computer readable storage medium of claim 46, wherein the plurality of configurations further comprises each configuration having a respective parameter, wherein at least a portion of the plurality of configurations is redundant in at least a portion of the respective parameters. The computer readable storage medium of claim 46, wherein the synchronization message further comprises a plurality of possible authentication options for the node to select from the plurality of possible authentication options. 103860-1010628.doc