Link negotiation control method, device, apparatus and computer storage medium

Abstract

This application provides a link negotiation control method, apparatus, device, and computer storage medium. The method obtains the current operating phase of a target access device; if the target access device is currently in a session phase, it generates a request message corresponding to the current link negotiation and sends the request message to the target host; after receiving the request message, the target host obtains the corresponding first configuration parameters and determines whether the first configuration parameters can satisfy the second configuration parameters; if the first configuration parameters can satisfy the second configuration parameters, it generates a return message and sends the return message to the target access device; if the target access device receives the return message within a preset time period, it determines that the link negotiation with the target host was successful; otherwise, the link negotiation failed. This method reduces the complexity of the calculation process, reduces network bandwidth consumption caused by frequent signaling interactions between devices, and improves the user experience.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a link negotiation control method, apparatus, device, and computer storage medium. Background Technology

[0002] PPPoE (Point-to-Point Protocol Over Ethernet) is a network tunneling protocol that encapsulates the Point-to-Point Protocol (PPP) within the Ethernet framework; that is, PPP carried over Ethernet. Through PPPoE, multiple hosts on a shared Ethernet network can establish multiple PPP sessions with one or more simple access devices.

[0003] PPPoE comprises two important phases: discovery and session. During the discovery phase, the host can discover one or more access devices. The host will select one of these devices, exchange information to obtain each other's MAC addresses, and establish a PPPoE Session ID. Once the discovery phase is complete, both the host and the access device have the information to establish a PPP connection over Ethernet. The discovery phase remains stateless until the PPP session is established. Once the PPP session is established, both the host and the access device must allocate resources for the PPP virtual interface.

[0004] For LCP authentication, the negotiation process defined by traditional protocols is relatively complex. Considering the large number of users connected to each access device and the different user login and logout behaviors, this process introduces high network complexity. In other words, the excessively frequent signaling interactions between the host and access device not only consume network bandwidth but also increase the computing and forwarding resources of various devices. Summary of the Invention

[0005] This application provides a link negotiation control method, apparatus, device, and computer storage medium to address the shortcomings of excessively frequent signaling interactions between the host and access device, which lead to increased network bandwidth consumption and computational complexity.

[0006] Firstly, this application provides a link negotiation control method, including:

[0007] Obtain the current operating stage of the target access device;

[0008] If the target access device is currently in the session phase, a request message corresponding to the current link negotiation is generated and the request message is sent to the target host;

[0009] Determine whether a return message corresponding to the request message has been received within a preset time period;

[0010] If the return message is received within the preset time period, it is determined that the link negotiation with the target host was successful.

[0011] Optionally, generating a request message corresponding to the current link negotiation includes:

[0012] Obtain the first configuration parameters of the target access device, wherein the first configuration parameters are used to instruct the target access device to perform link negotiation.

[0013] Store the first configuration parameter into the corresponding message information field;

[0014] Based on the message information field, a request message corresponding to the current link negotiation is generated.

[0015] Optionally, determining whether a return message corresponding to the request message has been received within a preset time period includes:

[0016] Real-time monitoring of message reception for current link negotiation, and start a timer;

[0017] The detection duration for the message reception status is determined based on the timer.

[0018] Determine whether the detection duration is greater than the preset duration;

[0019] If the detection duration is not greater than the preset duration, then determine whether a return message has been received within the preset duration;

[0020] If the detection duration exceeds the preset duration, the detection of message reception will be stopped.

[0021] Optionally, the operation phase further includes a discovery phase, and the method further includes:

[0022] If the target access device is currently in the discovery phase, it will interact with the target host.

[0023] Based on the results of the information exchange, a session address is generated between the host and the target host, and the current running phase is updated from the discovery phase to the session phase.

[0024] Optionally, after stopping the detection of message reception, the method further includes:

[0025] If the link negotiation with the target host fails, the communication connection with the target host will be interrupted.

[0026] Delete the currently stored session address, generate a prompt message corresponding to the current link negotiation, and send the prompt message to the target user.

[0027] Secondly, this application provides a link negotiation control method, which further includes:

[0028] Obtain the request message sent by the target access device;

[0029] Based on the request message, determine the first configuration parameters of the target access device;

[0030] Determine whether the first configuration parameter can satisfy the second configuration parameter, the second configuration parameter being used to instruct the target host on parameter information for link negotiation;

[0031] If the first configuration parameter can satisfy the second configuration parameter, then a return message corresponding to the request message is generated;

[0032] The return message is sent to the target access device, and it is confirmed that the link negotiation with the target access device was successful this time.

[0033] Optionally, the method further includes:

[0034] If the first configuration parameter cannot satisfy the second configuration parameter, then the second configuration parameter shall be adjusted according to the first configuration parameter;

[0035] Based on the adjustment results, reassess whether the first configuration parameter can satisfy the new second configuration parameter;

[0036] If the first configuration parameter can satisfy the new second configuration parameter, then a return message corresponding to the request message is generated;

[0037] The return message is sent to the target access device, and it is confirmed that the link negotiation was successful.

[0038] If the first configuration parameter cannot satisfy the new second configuration parameter, then no return message corresponding to the request message will be generated, and the link negotiation for this time will be determined to have failed.

[0039] Thirdly, this application provides a link negotiation control device, comprising:

[0040] The acquisition module is used to obtain the current operating stage of the target access device.

[0041] If the target access device is currently in the session phase, the generation module is used to generate a request message corresponding to the current link negotiation.

[0042] The sending module is used to send the request message to the target host.

[0043] The judgment module is used to determine whether a return message corresponding to the request message has been received within a preset time period.

[0044] If the return message is received within a preset time period, the determination module is used to determine that the link negotiation with the target host was successful in this instance.

[0045] Optionally, the acquisition module is further configured to acquire first configuration parameters of the target access device, wherein the first configuration parameters are used to instruct the target access device on parameter information for link negotiation.

[0046] Optionally, the link negotiation control device further includes a processing module.

[0047] The processing module is used to store the first configuration parameters into the corresponding message information field.

[0048] The generation module is further configured to generate a request message corresponding to the current link negotiation based on the message information field.

[0049] Optionally, the processing module is also used to detect the message reception status of the current link negotiation in real time and start a timer.

[0050] The determining module is further configured to determine the detection duration of the message reception status based on the timer.

[0051] The judgment module is also used to determine whether the detection duration is greater than the preset duration.

[0052] If the detection duration is not greater than the preset duration, then the judgment module is specifically used to determine whether a return message has been received within the preset duration.

[0053] If the detection duration exceeds the preset duration, the processing module is further configured to stop detecting the message reception status.

[0054] Optionally, if the target access device is currently in the discovery phase, the processing module is further configured to interact with the target host.

[0055] The generation module is also used to generate a session address with the target host based on the result of the information interaction.

[0056] The processing module is also used to update the current running stage from the discovery stage to the session stage.

[0057] Optionally, the determining module is further configured to determine that the link negotiation with the target host failed in the current instance.

[0058] The processing module is also used to interrupt the communication connection with the target host.

[0059] The processing module is also used to delete the currently stored session address.

[0060] The generation module is also used to generate prompt information corresponding to the current link negotiation.

[0061] The sending module is also used to send the prompt information to the target user.

[0062] Fourthly, this application provides a link negotiation control device, which further includes:

[0063] The acquisition module is used to acquire request messages sent by the target access device.

[0064] The determination module is used to determine the first configuration parameters of the target access device based on the request message.

[0065] The judgment module is used to determine whether the first configuration parameter can satisfy the second configuration parameter, which is used to instruct the target host to perform link negotiation.

[0066] If the first configuration parameter can satisfy the second configuration parameter, then the generation module is used to generate a return message corresponding to the request message.

[0067] The sending module is used to send the return message to the target access device.

[0068] The determining module is also used to determine that the link negotiation with the target access device was successful in this instance.

[0069] Optionally, the link negotiation control device further includes a processing module.

[0070] If the first configuration parameter cannot satisfy the second configuration parameter, the processing module is used to adjust the second configuration parameter according to the first configuration parameter.

[0071] The judgment module is also used to re-determine whether the first configuration parameter can meet the new second configuration parameter based on the adjustment result.

[0072] If the first configuration parameter can satisfy the new second configuration parameter, then the generation module is further used to generate a return message corresponding to the request message.

[0073] If the first configuration parameter cannot satisfy the new second configuration parameter, the generation module is further configured not to generate a return message corresponding to the request message.

[0074] The determining module is also used to determine if the current link negotiation fails.

[0075] Fifthly, this application provides a link negotiation control device, comprising:

[0076] Memory;

[0077] processor;

[0078] The memory stores computer-executed instructions;

[0079] The processor executes computer execution instructions stored in the memory to implement the link negotiation control method as described in the first aspect and various possible implementations of the first aspect or the second aspect and various possible implementations of the second aspect.

[0080] In a sixth aspect, this application provides a computer storage medium storing computer execution instructions thereon, which are executed by a processor to implement the link negotiation control method as described in the first aspect and various possible implementations thereof, or the second aspect and various possible implementations thereof.

[0081] The link negotiation control method provided in this application obtains the current operating phase of the target access device. If the target access device is currently in a session phase, a request message corresponding to the current link negotiation is generated and sent to the target host. After receiving the request message, the target host obtains the first configuration parameters of the target access device and determines whether the first configuration parameters can satisfy the second configuration parameters. If the first configuration parameters can satisfy the second configuration parameters, a return message corresponding to the request message is generated and sent to the target access device. If the target access device receives the return message within a preset time period, the link negotiation with the target host is considered successful; otherwise, the link negotiation fails. This method reduces the complexity of the calculation process, simplifies the negotiation process between devices, improves the efficiency of link negotiation, reduces network bandwidth consumption caused by frequent signaling interactions between devices, and improves the user experience. Attached Figure Description

[0082] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0083] Figure 1 A schematic diagram illustrating a scenario for the link negotiation control method provided in this application;

[0084] Figure 2 Signaling interaction diagram of the link negotiation control method provided in this application Figure 1 ;

[0085] Figure 3Signaling interaction diagram of the link negotiation control method provided in this application Figure 2 ;

[0086] Figure 4 Schematic diagram of the link negotiation control device provided in this application Figure 1 ;

[0087] Figure 5 Schematic diagram of the link negotiation control device provided in this application Figure 2 ;

[0088] Figure 6 A schematic diagram of the link negotiation control device provided in this application.

[0089] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0090] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0091] The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented, for example, in orders other than those illustrated or described herein.

[0092] In this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0093] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0094] First, the terms used in this application will be explained.

[0095] PPPoE: PPPoE (Point-to-Point Protocol Over Ethernet) is a network tunneling protocol that encapsulates the Point-to-Point Protocol (PPP) within the Ethernet framework. It carries the PPP protocol over Ethernet, using Ethernet to connect a large number of hosts to the Internet via a remote access device, and providing control and billing functions for each connected host. Because it integrates the PPP protocol, it provides authentication, encryption, and compression functions that traditional Ethernet cannot offer. It can be used in cable modems and Digital Subscriber Line (DSL) systems that provide access services to users via Ethernet.

[0096] Session ID: A unique identifier used to track user sessions. When a user visits a website, the website creates a session and assigns it a Session ID. This Session ID is continuously updated as the user visits the website. Session IDs are typically stored in cookies, but can also be passed via URL parameters. When a user logs in or performs other actions, the server can use the Session ID to verify the user's identity and save relevant data.

[0097] BRAS (Broadband Remote Access Server) is a network device used to handle access, authentication, billing, control, and management of broadband network users across various access methods. It is the cornerstone of a broadband network's operability and manageability. BRAS primarily performs two functions: first, network transport: terminating user PPPoE connections and aggregating user traffic; second, control implementation: working in conjunction with authentication, billing, customer management, and service policy control systems to implement user access authentication, billing, and management functions. It is also a new type of access gateway for broadband network applications; a bridge between the broadband access network and the backbone network, providing basic access methods and broadband access network management functions. Located at the network edge, it provides broadband access services, aggregates and forwards various services, and can meet the transmission capacity and bandwidth utilization requirements of different users, thus being a core device for broadband user access.

[0098] PPPoE is a network tunneling protocol that encapsulates the Point-to-Point Protocol (PPP) within the Ethernet framework; that is, PPP carried over Ethernet. Through PPPoE, multiple hosts on a shared Ethernet network can establish multiple PPP sessions with one or more simple access devices.

[0099] PPPoE comprises two important phases: discovery and session. During the discovery phase, the host can discover one or more access devices. The host will select one of these devices, exchange information to obtain each other's MAC addresses, and establish a PPPoE Session ID. Once the discovery phase is complete, both the host and the BRAS device have information about establishing a PPP connection over Ethernet. The discovery phase remains stateless until the PPP session is established. Once the PPP session is established, both the host and the access device must allocate resources for the PPP virtual interface.

[0100] The session phase involves two important protocols: LCP (Link Control Protocol) and NCP (Network Control Protocol). LCP is used for negotiating and authenticating the underlying link between the host and the BRAS device. After the host passes the LCP phase, it obtains an IP address via NCP (which is IPCP for IP networks). The negotiation process defined by traditional protocols for LCP authentication is relatively complex. Considering the large number of users connected to each access device and the different user login and logout behaviors, this process introduces high network complexity. In other words, the excessively frequent signaling interactions between the host and access devices not only consume network bandwidth but also increase the computing and forwarding resources of various devices.

[0101] To address the aforementioned issues, this application provides a link negotiation control method.

[0102] Figure 1 This is a schematic diagram illustrating a scenario of the link negotiation control method provided in this application. For example... Figure 1 As shown, target host 1 and target access device 2 are communicatively connected. Target access device 2 can generate corresponding link negotiation request messages according to user needs; target host 1 can receive link negotiation request messages sent by target access device 2, and can also adjust its own configuration parameters according to the received request messages to generate corresponding return messages, which are then sent to target access device 2. Target host 1 can be, for example, a user terminal conducting a PPP session, and target access device 2 can be, for example, a BRAS device conducting a PPP session.

[0103] This application provides a link negotiation control method. The method involves controlling an access device to actively send a link negotiation request message to the host establishing the connection. Based on this request message, the host obtains the access device's configuration parameters and matches them with its own configuration parameters. Based on the matching result, the host adjusts its own configuration parameters to determine the return message to be sent to the access device. When the access device receives the return message from the host, the link negotiation between the access device and the host is completed. This method reduces the complexity of the computational process, simplifies the negotiation process between devices, improves the efficiency of link negotiation, reduces network bandwidth consumption caused by frequent signaling interactions between devices, and improves the user experience.

[0104] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0105] Figure 2 Signaling interaction diagram of the link negotiation control method provided in the embodiments of this application Figure 1 .like Figure 2 As shown, the link negotiation control method provided in this embodiment includes:

[0106] S201: The target access device obtains the current operating stage of the current device.

[0107] The "operation phase" indicates the stage at which the target access device establishes a link connection with the target host.

[0108] Understandably, the entity executing this step is the target access device, which connects the target host to the Ethernet network, enabling the target host to perform corresponding operations on the Ethernet. Therefore, to ensure that the target host can access the Ethernet network through the target access device, negotiation with the target host is necessary first. The negotiation method involved in this embodiment can, for example, be based on the PPPoE protocol.

[0109] The PPPoE protocol's workflow consists of two phases: discovery and session. The discovery phase is stateless and its purpose is to establish a communication connection between the target access device and the target host, generating a unique identifier between them to facilitate the establishment of a data link. After the discovery phase, the PPPoE protocol enters the PPP session phase. In the PPP session phase, the target access device and the target host exchange signaling signals to negotiate and authenticate the underlying link between them, thereby establishing a link connection between them, i.e., a data link between the target access device and the target host.

[0110] The target access device can obtain its own operational phase in real time. By determining whether there is signaling interaction between the target access device and the target host, the current operational phase of the target access device can be determined. If there is signaling interaction between the target access device and the target host, it can be determined that the target access device is currently in the session phase; if there is no signaling interaction between the target access device and the target host, it can be determined that the target access device is currently in the discovery phase. This application does not impose any special restrictions on determining the current operational phase of the target access device.

[0111] For example, if there is signaling interaction between the BRAS device and the user terminal, it can be determined that the current operating stage of the BRAS device is the session stage; if there is no signaling interaction between the BRAS device and the user terminal, it can be determined that the current operating stage of the BRAS device is the discovery stage.

[0112] S202: If the target access device is currently in the session phase, the target access device generates a request message corresponding to the current link negotiation.

[0113] S203: The target access device sends the request message to the target host.

[0114] The request message is used to indicate the data units to be exchanged and transmitted with the target host after a communication connection has been established.

[0115] Understandably, the PPP session phase includes two important protocols: the Link Control Protocol (LCP) and the Network Control Protocol (NCP). The LCP is primarily used to establish, configure, and detect the connection of the PPP data link. Based on the LCP and NCP, negotiation and authentication between the target access device and the target host can be achieved. During the negotiation between the target access device and the target host, the configuration parameters of both are matched. Based on the matching result, the negotiation between the target access device and the target host is completed, thereby determining whether to establish a data link between them.

[0116] When a PPP session is conducted between a target access device and a target host, a data link needs to be established between the two hosts in order for the target host to successfully access the Ethernet. Before establishing this data link, the target access device first needs to negotiate with the target host. By obtaining data units related to the current link negotiation from the target access device, the device encapsulates and processes these data units to obtain the corresponding request message. When the target access device is currently in the session phase, a communication connection has been established between the device and the target host, and this communication connection is unique and used only for signaling interaction with the target host. The request message obtained is then sent to the target host through this communication connection.

[0117] For example, if the BRAS device is in the PPP session stage, it indicates that there is a unique communication channel between the BRAS device and the user terminal. At this time, the data information related to link negotiation in the BRAS device is obtained, encapsulated, and a corresponding request message, namely the Configure-Request message, is generated. The corresponding data information in the request message may include: "MTU value, authentication method, connection hold time, link quality parameters". The Configure-Request message obtained at this time is sent to the user terminal through this communication channel.

[0118] S204: The target host determines the first configuration parameters of the target access device based on the request message.

[0119] The first configuration parameter is used to indicate the parameter information for the target access device to negotiate the link.

[0120] Through the communication connection established with the target access device, a request message can be received from the target access device; after receiving the request message, the target host analyzes and processes the request message to obtain the first configuration parameters related to the current link negotiation.

[0121] For example, after the user terminal receives the request message from the BRAS device, the user terminal analyzes and processes the request message to obtain the first configuration parameters related to the current link negotiation, that is, to obtain the data information related to the link negotiation in the BRAS device, and the data information may include: "MTU value, authentication method, connection hold time, link quality parameters".

[0122] S205: The target host determines whether the first configuration parameter can satisfy the second configuration parameter.

[0123] The second configuration parameter is used to instruct the target host on the parameters for link negotiation.

[0124] The purpose of this step, which determines whether the first configuration parameter can satisfy the second configuration parameter, is to determine whether the target host can establish a link connection with the target access device.

[0125] Understandably, the target access device is the medium through which the target host accesses the Ethernet, and the configuration parameters of the target access device are mostly fixed and will not change due to the configuration parameters of the target host. Therefore, when accessing the Ethernet through the target access device, it is necessary to compare the configuration parameters of the target access device with the configuration parameters of the target host to determine whether the target access device can meet the access requirements of the target host. In other words, by judging whether the first configuration parameter can meet the second configuration parameter, the target host can determine whether its configuration parameters meet the access conditions.

[0126] If the first configuration parameter can satisfy the second configuration parameter, it indicates that the target access device can meet the access requirements of the target host. The target host can access the Ethernet through the target access device with which the communication connection is currently established. At this time, a return message corresponding to the request message is generated and sent to the target access device.

[0127] If the first configuration parameter cannot meet the second configuration parameter, it indicates that the target access device cannot meet the access requirements of the target host. The target host cannot access the Ethernet through the target access device with which the current communication connection is established. At this time, the second configuration parameter needs to be adjusted, and based on the adjustment result, it is further determined whether the adjusted second configuration parameter can meet the first configuration parameter and whether a link connection can be established with the target access device.

[0128] For example, if the first configuration parameters include "MTU value, authentication method, connection hold time, and link quality parameters", then the second configuration parameters from the user terminal are obtained, and the second configuration parameters also include "MTU value, authentication method, connection hold time, and link quality parameters". The user terminal checks the authentication method, connection hold time, and link quality parameters in the first configuration parameters, and compares the MTU value in the first configuration parameters with the MTU value in the second configuration parameters. The MTU value is the maximum transmission unit of the device, used to determine whether the configuration parameters can be achieved, i.e., whether the configuration parameters can be met. When the MTU value in the first configuration parameters is less than the MTU value in the second configuration parameters, it indicates that the BRAS is not configured correctly. If the BRAS device cannot meet the maximum data transmission unit requirement of the user terminal, the two cannot be adapted and a link connection cannot be established. When the MTU value in the first configuration parameter is not less than the MTU value in the second configuration parameter, it means that the BRAS device can meet the maximum data transmission unit requirement of the user terminal and a corresponding link connection can be established. If the configuration parameter can be met, a corresponding return message, i.e., a Configure-Ack message, is generated and sent to the BRAS device. If the configuration parameter cannot be met, the parameters in the second configuration parameter that do not meet the access conditions are adjusted, and based on the adjustment result, it is re-determined whether the second configuration parameter can meet the configuration parameter.

[0129] S206: If the first configuration parameter can satisfy the second configuration parameter, then the target host generates a return message corresponding to the request message.

[0130] S207: The target host sends the return message to the target access device.

[0131] S208: The target access device determines whether it has received a return message corresponding to the request message within a preset time period.

[0132] The preset duration is used to indicate the length of time it takes for the target access device to receive the return message from the target host after sending the request message. For example, the preset duration can be 2 minutes.

[0133] The purpose of this step, which checks whether a return message corresponding to the request message has been received within a preset time period, is to determine whether the current link negotiation was successful.

[0134] If the target access device receives a return message within a preset time period, it indicates that the target access device can meet the access requirements of the target host, and the target host can access the Ethernet through the target access device. At this time, it is determined that the link negotiation with the target host is successful and a data link between the target access device and the target host can be established.

[0135] If the target access device does not receive a return message within the preset time period, it indicates that the target access device cannot meet the access requirements of the target host, the first configuration parameter cannot meet the negotiation requirements corresponding to the second configuration parameter, or the target host takes too long to produce a return message, thus causing the target access device to fail to receive a return message within the preset time period. At this time, it is determined that the link negotiation with the target host has failed, and the currently stored data information related to the target host is deleted.

[0136] For example, after sending a Configure-Request message, the BRAS device begins checking whether it has received a Configure-Ack message from the user terminal, and the detection period is 2 minutes. If the BRAS device detects a Configure-Ack message within 2 minutes, it indicates that the BRAS device can meet the user terminal's access requirements, and the BRAS device's configuration parameters are consistent with the user terminal's configuration parameters, or the BRAS device's configuration parameters can meet the access requirements corresponding to the user terminal's configuration parameters. At this time, it is determined that the BRAS device and the user terminal have successfully negotiated and can establish a data link between them. If the BRAS device does not detect a Configure-Ack message within 2 minutes, it indicates that the BRAS device cannot meet the user terminal's access requirements. At this time, it is determined that the BRAS device and the user terminal have failed to negotiate, and the currently stored data information related to the target host is deleted.

[0137] S209: If the target access device receives the return message within a preset time period, the target access device determines that the link negotiation with the target host was successful in this instance.

[0138] S210: If the target access device does not receive the return message within a preset time period, the target access device determines that the link negotiation with the target host has failed.

[0139] The link negotiation control method provided in this embodiment obtains the current operating phase of the target access device. If the target access device is currently in a session phase, a request message corresponding to the current link negotiation is generated and sent to the target host. After receiving the request message, the target host obtains the first configuration parameters of the target access device and determines whether the first configuration parameters can satisfy the second configuration parameters. If the first configuration parameters can satisfy the second configuration parameters, a return message corresponding to the request message is generated and sent to the target access device. If the target access device receives the return message within a preset time period, the link negotiation with the target host is determined to be successful; otherwise, the link negotiation fails. This method reduces the complexity of the calculation process, reduces network bandwidth consumption caused by frequent signaling interactions between devices, and improves the user experience.

[0140] Figure 3 Signaling interaction diagram of the link negotiation control method provided in the embodiments of this application Figure 2 .like Figure 3 As shown, in this embodiment... Figure 2 Based on the embodiments, the link negotiation control method is described in detail. The link negotiation control method shown in this embodiment includes:

[0141] S301: The target access device obtains the current operating stage of the target access device.

[0142] Step S301 is similar to step S201 above, and will not be described again here.

[0143] S302: If the target access device is currently in the session phase, the target access device obtains the first configuration parameters of the current device.

[0144] If the target access device is currently in the session phase, it indicates that the target access device needs to negotiate with the target host and determine whether to connect the target host to the Ethernet based on the negotiation result. At this time, negotiation with the target host is required, and the content negotiated by the target access device and the target host are their respective configuration parameters. Therefore, after determining that the target access device needs to negotiate with the target host, the first configuration parameter of the current target access device is obtained.

[0145] For example, if the BRAS device is in the PPP session stage, it indicates that there is a unique communication channel between the BRAS device and the user terminal. At this time, data information related to link negotiation in the BRAS device can be obtained. This data information may include: "MTU value, authentication method, connection hold time, and link quality parameters".

[0146] Optionally, the operation phase further includes a discovery phase, and the method further includes:

[0147] If the target access device is currently in the discovery phase, the target access device will exchange information with the target host; based on the result of the information exchange, a session address will be generated between the target host and the current running phase will be updated from the discovery phase to the session phase.

[0148] The session address is a unique identifier used to mark the communication connection between the target access device and the target host.

[0149] Understandably, the negotiation process between the target access device and the target host mainly involves two operational phases: the discovery phase and the session phase. The discovery phase is when the target access device and the target host establish a communication connection, while the session phase is when it is determined whether the current link connection can be established.

[0150] When the target access device is currently in the discovery phase, it begins to exchange information with the target host. Both parties obtain each other's physical addresses and generate a unique session address between themselves and the target host. The target access device can use this session address to identify the target host and assist the target host in accessing the Ethernet. At this time, the target access device's operation phase changes to the session phase, and the target access device can negotiate the link with the target host.

[0151] For example, when the BRAS device is in the discovery phase, the target access device begins to interact with the target host, exchanges their MAC addresses, and generates a unique Session ID; the BRAS device then switches its operating phase from the discovery phase to the session phase, and negotiates the link with the user terminal.

[0152] S303: The target access device stores the first configuration parameters in the corresponding message information field.

[0153] The message information field is used to indicate the storage location of the first configuration parameter.

[0154] After obtaining the first configuration parameters of the target access device, since the negotiation between the target access device and the target host requires signaling interaction, and the signaling interaction is achieved through the transmission between the messages generated by the target access device and the messages generated by the target host, it is necessary to store the currently obtained first configuration parameters into the message used for signaling interaction. In other words, it is necessary to store the first configuration parameters into the message information field corresponding to the message used for signaling interaction.

[0155] As is understandable, a message is essentially a string of text consisting of multiple lines of data. It is a data format used to exchange information when making requests and responses between different systems, and it generally has a fixed format. A message contains the complete data information to be sent.

[0156] For example, during a PPP session, the message information field of a BRAS device consists of a code field, an identifier field, a length field, and data. The code field contains multiple fields, including "0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C". The first configuration parameters obtained at the moment include "MTU value, authentication method, connection hold time, and link quality parameters", and these parameters are stored in the "0x01" field. In the original negotiation method, only the "0x0C" field was reserved. In this embodiment, the negotiation method adjusts the "0x03" and "0x04" fields to reserved fields and does not store other data information at the current moment. The addition of reserved fields brings more flexibility to the subsequent signaling interaction process.

[0157] S304: The target access device generates a request message corresponding to the current link negotiation based on the message information field.

[0158] S305: The target access device sends the request message to the target host.

[0159] After the first configuration parameters are stored in the message information field, the currently obtained data format is encapsulated to generate a request message containing the current link negotiation content. When the target access device is currently in the session stage, a communication connection has been established between the device and the target host. Through this communication connection, the currently obtained request message is sent to the target host.

[0160] For example, after the BRAS device stores the parameter information "MTU value, authentication method, connection hold time, and link quality parameters" in the "0x01" field, it encapsulates it to generate the corresponding request message, namely the Configure-Request message; and sends the currently obtained Configure-Request message to the user terminal through the unique communication channel between the BRAS device and the user terminal.

[0161] S306: The target host determines the first configuration parameters of the target access device based on the request message.

[0162] Step S306 is similar to step S204 above, and will not be described again here.

[0163] S307: The target host determines whether the first configuration parameter can satisfy the second configuration parameter.

[0164] The purpose of this step, which determines whether the first configuration parameter can satisfy the second configuration parameter, is to determine whether the target host can establish a link connection with the target access device.

[0165] Understandably, since the first configuration parameter cannot be changed, it can be used as the criterion for determining whether the target access device can access the Ethernet. Based on the parameter information corresponding to the first configuration parameter, the configuration parameters of the target host with access requirements are compared, and the corresponding negotiation content is transmitted based on the first configuration parameter, so that the target access device and the target host can reach an agreement, thereby facilitating successful negotiation between the two.

[0166] If the first configuration parameter can satisfy the second configuration parameter, it indicates that the target access device can meet the access requirements of the target host. The second configuration parameter meets the judgment criteria of the first configuration parameter as an accessible device. At this time, a return message corresponding to the request message is generated and the return message is sent to the target access device.

[0167] If the first configuration parameter cannot meet the second configuration parameter, it indicates that the target access device cannot meet the access requirements of the target host. The second configuration parameter does not meet the judgment criteria of the first configuration parameter as an accessible device. In this case, the second configuration parameter needs to be adjusted, and based on the adjustment result, it is further determined whether the adjusted second configuration parameter can meet the first configuration parameter.

[0168] For example, if the first configuration parameters include "MTU value, authentication method, connection hold time, and link quality parameters", then the second configuration parameters from the user terminal are obtained, and the second configuration parameters also include "MTU value, authentication method, connection hold time, and link quality parameters". The user terminal checks the authentication method, connection hold time, and link quality parameters in the first configuration parameters, and compares the MTU value in the first configuration parameters with the MTU value in the second configuration parameters. The MTU value is the maximum transmission unit of the device, used to determine whether the configuration parameters can be achieved, i.e., whether the configuration parameters can be met. When the MTU value in the first configuration parameters is less than the MTU value in the second configuration parameters, it indicates that the BRAS device cannot meet the user terminal's maximum data transmission requirements. The two cannot be compatible and cannot establish a link connection due to the different requirements of the transmission unit. When the MTU value in the first configuration parameter is not less than the MTU value in the second configuration parameter, it means that the BRAS device can meet the maximum data transmission unit requirement of the user terminal and can establish a corresponding link connection. If the configuration parameter can be met, the corresponding parameter information is stored in the "0x02" field, and a corresponding return message, i.e., a Configure-Ack message, is generated based on this and sent to the BRAS device. If the configuration parameter cannot be met, the parameters in the second configuration parameter that do not meet the access standard are adjusted, and the adjusted second configuration parameter is re-determined to meet the configuration parameter based on the adjustment result.

[0169] S308: If the first configuration parameter can satisfy the second configuration parameter, then the target host generates a return message corresponding to the request message.

[0170] S309: If the first configuration parameter cannot satisfy the second configuration parameter, the target host adjusts the second configuration parameter according to the first configuration parameter.

[0171] S310: The target host re-determines whether the first configuration parameters can meet the new second configuration parameters based on the adjustment results.

[0172] The purpose of this step, which determines whether the first configuration parameter can meet the new second configuration parameter, is to further determine whether the target host can establish a link connection with the target access device.

[0173] Understandably, the target host is the main body executing this step. When the second configuration parameter does not meet the judgment standard of the first configuration parameter as the accessible device, the target host adjusts the second configuration parameter according to the first configuration parameter, so that the first configuration parameter can meet the access requirements corresponding to the adjusted second configuration parameter, and the target host can access the Ethernet through the target access device.

[0174] If the first configuration parameter can satisfy the new second configuration parameter, and the target access device can meet the access requirements of the target host, then the target host will store the parameter information of the response and request message into the corresponding field in the request message, thereby obtaining the return message of the current link negotiation.

[0175] If the first configuration parameter cannot meet the new second configuration parameter, the target access device cannot meet the access requirements of the target host, and the target host will not generate a return message corresponding to the request message. Since the target access device has a time limit for receiving the return message, after determining that the first configuration parameter cannot meet the new second configuration parameter and the adjustment time of the second configuration parameter exceeds the preset time, it is determined that the link negotiation has failed.

[0176] For example, after the user terminal re-determines whether the first configuration parameter can satisfy the new second configuration parameter, if the first configuration parameter can satisfy the new second configuration parameter, the corresponding parameter information is stored in the "0x02" field of the message, and a corresponding return message, namely the Configure-Ack message, is generated based on this and sent to the BRAS device; if the first configuration parameter cannot satisfy the new second configuration parameter, and the current adjustment time exceeds 2 minutes, the user terminal does not generate a corresponding return message and determines that the link negotiation has failed.

[0177] S311: When the first configuration parameter can satisfy the new second configuration parameter, the target host generates a return message corresponding to the request message.

[0178] S312: When the first configuration parameter cannot satisfy the new second configuration parameter, the target host does not generate a return message corresponding to the request message, and determines that the link negotiation has failed.

[0179] S313: The target host sends the return message to the target access device.

[0180] S314: The target access device detects the message reception status of the current link negotiation in real time and starts a timer.

[0181] S315: The target access device determines the detection duration of the message reception status according to the timer.

[0182] Among them, the message reception status is used to indicate whether the target access device has received the return message from the target host, and the detection duration is used to indicate the length of time that the timer takes after the target access device sends the request message.

[0183] After sending the request message for the current link negotiation, the target access device performs real-time detection of the message from the target host and starts its own configured timer to detect the length of time it takes for the target host to respond to the currently sent request message, thereby obtaining the detection time of the message reception status for the current link negotiation.

[0184] For example, after the BRAS device sends the request message for the current link negotiation, it performs real-time detection on the messages from the target host. At the same time, a timer is started, and the detection duration is 2 minutes, that is, the real-time detection of messages by the BRAS device lasts for 2 minutes.

[0185] S316: The target access device determines whether the detection duration is greater than the preset duration.

[0186] The purpose of this step, which determines whether the detection time is greater than the preset time, is to ascertain whether the target access device is in the state of receiving return messages.

[0187] If the detection duration is not greater than the preset duration, it indicates that the target access device is in a state of real-time detection of the message reception status of the current link negotiation. At this time, it is necessary to determine whether the target access device has received the return message in the current state.

[0188] If the detection duration exceeds the preset duration, it indicates that the target access device is not in a state of real-time detection of the message reception status of the current link negotiation. The target access device currently stops receiving return messages from the target host, and at this time, the target access device stops detecting the message reception status of the current link negotiation.

[0189] For example, if the current detection duration is 1 minute, which is less than 2 minutes, it indicates that the BRAS device is still in a state where it can receive return messages from the target host. In this case, it is necessary to further determine whether the BRAS device has received the Configure-Ack message. If the current detection duration is 3 minutes, which is greater than 2 minutes, it indicates that the BRAS device is not currently in a state where it can receive return messages from the target host. In this case, the BRAS device stops receiving Configure-Ack messages from the user terminal and stops detecting the message reception status of the current link negotiation.

[0190] S317: If the detection duration is not greater than the preset duration, the target access device determines whether it has received a return message corresponding to the request message within the preset duration.

[0191] S318: When the target access device receives the return message within a preset time period, it determines that the link negotiation with the target host is successful.

[0192] S319: If the target access device does not receive the return message within a preset time period, it determines that the link negotiation with the target host has failed.

[0193] Steps S317-S319 are similar to steps S208-S210 above, and will not be repeated here.

[0194] S320: If the detection duration is longer than the preset duration, then stop detecting the current device's message reception status.

[0195] S321: The target access device determines that the link negotiation with the target host has failed in this instance, and interrupts the communication connection with the target host.

[0196] S322: The target access device deletes the currently stored session address, generates a prompt message corresponding to the current link negotiation, and sends the prompt message to the target user.

[0197] The prompt message indicates that there was an anomaly in the current link negotiation and that the negotiation failed; the target user is used to indicate the personnel responsible for handling the current link negotiation anomaly.

[0198] After ceasing to detect the current device's message reception status, the target access device can determine that the link negotiation with the target host has failed, and will interrupt the communication connection with the target host and delete the currently stored session address, thereby preventing it from receiving return messages from the target host; and generate a prompt message corresponding to the current link negotiation, and send the prompt message to the target user to prompt the target user to take subsequent actions for the failure of the link negotiation between the target access device and the target host.

[0199] For example, after stopping the detection of message reception by the BRAS device, the BRAS device can determine that the current link negotiation with the user terminal has failed, and interrupt the communication connection with the user terminal, as well as delete the currently stored unique Session ID, so that the BRAS device will not receive the Configure-Ack message from the current moment, regardless of whether the user terminal successfully generates the message; generate a prompt message corresponding to the current link negotiation, and send the prompt message to the target user to prompt the target user to take subsequent actions for the failure of the current link negotiation.

[0200] The link negotiation control method provided in this implementation obtains the current operating phase of the target access device. If the target access device is currently in the session phase, it obtains the first configuration parameters of the current device and stores them in the corresponding message information field, thereby generating a request message corresponding to the current link negotiation and sending the request message to the target host. After receiving the request message, the target host obtains the first configuration parameters of the target access device and determines whether the first configuration parameters can satisfy the second configuration parameters. If the first configuration parameters can satisfy the second configuration parameters, it generates a return message corresponding to the request message. If the first configuration parameters cannot satisfy the second configuration parameters, it adjusts the second configuration parameters and re-determines whether the first configuration parameters can satisfy the new second configuration parameters. If the first configuration parameters can satisfy the new second configuration parameters, it generates a return message. If the first configuration parameters cannot satisfy the new second configuration parameters, it does not generate a return message. The method involves several steps: First, the target host generates a response message corresponding to the request message and sends it to the target access device. The target access device continuously monitors the message reception status of the current link negotiation and starts a timer to determine the detection duration. It then checks if this detection duration exceeds a preset duration. If the detection duration is not greater than the preset duration, it checks if the target access device has received and returned the message within the preset duration. If the target access device receives the response message within the preset duration, the link negotiation with the target host is considered successful; otherwise, the link negotiation fails. If the detection duration exceeds the preset duration, the monitoring of message reception by the current device is stopped, the link negotiation is determined to have failed, the communication connection between the target access device and the target host is interrupted, and the currently stored session address is deleted. A prompt message corresponding to the current link negotiation is generated and sent to the target user. This method reduces the complexity of the computation process, simplifies the negotiation process between devices, improves the efficiency of link negotiation, reduces network bandwidth consumption caused by frequent signaling interactions between devices, and enhances the user experience.

[0201] It is understood that the above embodiments mainly involve the negotiation process of the target host accessing the Ethernet through the target access device. This application does not impose any special restrictions on the system accessed by the target host through the target access device.

[0202] Figure 4 A schematic diagram of the link negotiation control device provided in this application. Figure 4 As shown, this application provides a link negotiation control device 400, which includes:

[0203] The acquisition module 401 is used to acquire the current operating stage of the target access device.

[0204] If the target access device is currently in the session phase, the generation module 402 is used to generate a request message corresponding to the current link negotiation.

[0205] The sending module 403 is used to send the request message to the target host.

[0206] The judgment module 404 is used to determine whether a return message corresponding to the request message has been received within a preset time period.

[0207] If the return message is received within a preset time period, the determination module 405 is used to determine that the link negotiation with the target host was successful in this instance.

[0208] Optionally, the acquisition module 401 is further configured to acquire first configuration parameters of the target access device, wherein the first configuration parameters are used to instruct the target access device to perform link negotiation parameter information.

[0209] Optionally, the link negotiation control device further includes a processing module 406.

[0210] The processing module 406 is used to store the first configuration parameters into the corresponding message information field.

[0211] The generation module 402 is further configured to generate a request message corresponding to the current link negotiation based on the message information field.

[0212] Optionally, the processing module 406 is also used to detect the message reception status of the current link negotiation in real time and start a timer.

[0213] The determining module 405 is further configured to determine the detection duration of the message reception status based on the timer.

[0214] The judgment module 404 is also used to determine whether the detection duration is greater than the preset duration.

[0215] If the detection duration is not greater than the preset duration, then the judgment module 404 is specifically used to determine whether a return message has been received within the preset duration.

[0216] If the detection duration exceeds the preset duration, the processing module 406 is further configured to stop detecting the message reception status.

[0217] Optionally, if the target access device is currently in the discovery phase, the processing module 406 is further configured to interact with the target host.

[0218] The generation module 402 is further configured to generate a session address with the target host based on the result of the information interaction.

[0219] The processing module 406 is further configured to update the current running stage from the discovery stage to the session stage.

[0220] Optionally, the determining module 405 is further configured to determine that the link negotiation with the target host failed in the current attempt.

[0221] The processing module 406 is also used to interrupt the communication connection with the target host.

[0222] The processing module 406 is also used to delete the currently stored session address.

[0223] The generation module 402 is also used to generate prompt information corresponding to the current link negotiation.

[0224] The sending module 403 is also used to send the prompt information to the target user.

[0225] Figure 5 A schematic diagram of the link negotiation control device provided in this application. Figure 5 As shown, this application provides a link negotiation control device 500, which includes:

[0226] The acquisition module 501 is used to acquire the request message sent by the target access device.

[0227] The determination module 502 is used to determine the first configuration parameters of the target access device based on the request message.

[0228] The judgment module 503 is used to determine whether the first configuration parameter can satisfy the second configuration parameter, which is used to instruct the target host to perform link negotiation.

[0229] If the first configuration parameter can satisfy the second configuration parameter, then the generation module 504 is used to generate a return message corresponding to the request message.

[0230] The sending module 505 is used to send the return message to the target access device.

[0231] The determining module 502 is also used to determine that the link negotiation with the target access device was successful in this instance.

[0232] Optionally, the link negotiation control device further includes a processing module 506.

[0233] If the first configuration parameter cannot satisfy the second configuration parameter, the processing module 506 is used to adjust the second configuration parameter according to the first configuration parameter.

[0234] The judgment module 503 is also used to re-determine whether the first configuration parameter can meet the new second configuration parameter based on the adjustment result.

[0235] If the first configuration parameter can satisfy the new second configuration parameter, then the generation module 504 is further used to generate a return message corresponding to the request message.

[0236] If the first configuration parameter cannot satisfy the new second configuration parameter, the generation module 504 is further configured not to generate a return message corresponding to the request message.

[0237] The determining module 502 is also used to determine that the current link negotiation has failed.

[0238] Figure 6 A schematic diagram of the link negotiation control device provided in this application. Figure 6 As shown, this application provides a link negotiation control device 600, which includes a receiver 601, a transmitter 602, a processor 603, and a memory 604.

[0239] Receiver 601 is used to receive instructions and data;

[0240] Transmitter 602 is used to send commands and data;

[0241] Memory 604 is used to store instructions executed by the computer;

[0242] Processor 603 is used to execute computer execution instructions stored in memory 604 to implement the various steps of the link negotiation control method in the above embodiments. For details, please refer to the relevant descriptions in the foregoing embodiments of the link negotiation control method.

[0243] Optionally, the memory 604 can be either standalone or integrated with the processor 603.

[0244] When the memory 604 is set up independently, the electronic device also includes a bus for connecting the memory 604 and the processor 403.

[0245] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the link negotiation control method performed by the link negotiation control device described above.

[0246] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0247] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0248] It will be understood by those skilled in the art that all or some of the steps, systems, or apparatuses disclosed above, and their functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0249] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0250] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0251] The technical solutions of this application have been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it is readily understood by those skilled in the art that the scope of protection of this application is obviously not limited to these specific embodiments. The above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. These modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method of link negotiation control, characterized by, Applied to a target access device, the method includes: Obtain the current operating stage of the target access device; If the target access device is currently in the session phase, a request message corresponding to the current link negotiation is generated and the request message is sent to the target host; Determine whether a return message corresponding to the request message has been received within a preset time period; If the return message is received within the preset time period, it is determined that the link negotiation with the target host was successful.

2. The method of claim 1, wherein, The generation of the request message corresponding to the current link negotiation includes: Obtain the first configuration parameters of the target access device, wherein the first configuration parameters are used to instruct the target access device to perform link negotiation. Store the first configuration parameter into the corresponding message information field; Based on the message information field, a request message corresponding to the current link negotiation is generated.

3. The method of claim 2, wherein, The determination of whether a return message corresponding to the request message has been received within a preset time period includes: Real-time monitoring of message reception for current link negotiation, and start a timer; The detection duration for the message reception status is determined based on the timer. Determine whether the detection duration is greater than the preset duration; If the detection duration is not greater than the preset duration, then determine whether a return message has been received within the preset duration; If the detection duration exceeds the preset duration, the detection of message reception will be stopped.

4. The method of claim 3, wherein, The operational phase further includes a discovery phase, and the method further includes: If the target access device is currently in the discovery phase, it will interact with the target host. Based on the results of the information exchange, a session address is generated between the host and the target host, and the current running phase is updated from the discovery phase to the session phase.

5. The method of claim 4, wherein, After stopping the detection of message reception, the method further includes: If the link negotiation with the target host fails, the communication connection with the target host will be interrupted. Delete the currently stored session address, generate a prompt message corresponding to the current link negotiation, and send the prompt message to the target user.

6. A link negotiation control method characterized by comprising: Applied to a target host, the method includes: Obtain the request message sent by the target access device; Based on the request message, determine the first configuration parameters of the target access device; Determine whether the first configuration parameter can satisfy the second configuration parameter, the second configuration parameter being used to instruct the target host on parameter information for link negotiation; If the first configuration parameter can satisfy the second configuration parameter, then a return message corresponding to the request message is generated, the return message is sent to the target access device, and it is determined that the link negotiation with the target access device is successful in this instance. If the first configuration parameter cannot satisfy the second configuration parameter, then the second configuration parameter shall be adjusted according to the first configuration parameter; Based on the adjustment results, reassess whether the first configuration parameter can satisfy the new second configuration parameter; If the first configuration parameter can satisfy the new second configuration parameter, then a return message corresponding to the request message is generated, the return message is sent to the target access device, and it is determined that the link negotiation was successful. If the first configuration parameter cannot satisfy the new second configuration parameter, then no return message corresponding to the request message will be generated, and the link negotiation for this time will be determined to have failed.

7. A link negotiation control apparatus characterized by comprising: The device includes: The acquisition module is used to obtain the current operating stage of the target access device; If the target access device is currently in the session phase, the generation module is used to generate a request message corresponding to the current link negotiation. The sending module is used to send the request message to the target host; The judgment module is used to determine whether a return message corresponding to the request message has been received within a preset time period; If the return message is received within a preset time period, the determination module is used to determine that the link negotiation with the target host was successful in this instance.

8. A link negotiation control apparatus characterized by comprising: The device includes: The acquisition module is used to acquire request messages sent by the target access device; The determining module is used to determine the first configuration parameters of the target access device based on the request message; The judgment module is used to determine whether the first configuration parameter and the second configuration parameter are consistent, wherein the second configuration parameter is used to instruct the target host to perform link negotiation. If the first configuration parameter is consistent with the second configuration parameter, then the generation module is used to generate a return message corresponding to the request message; the sending module is used to send the return message to the target access device; the determining module is also used to determine that the link negotiation with the target access device is successful in this instance. If the first configuration parameter cannot satisfy the second configuration parameter, the processing module is used to adjust the second configuration parameter according to the first configuration parameter; The judgment module is also used to re-determine whether the first configuration parameter can meet the new second configuration parameter based on the adjustment result; If the first configuration parameter can satisfy the new second configuration parameter, the generation module is further configured to generate a return message corresponding to the request message; the sending module is further configured to send the return message to the target access device; the determining module is further configured to determine that the link negotiation was successful. If the first configuration parameter cannot satisfy the new second configuration parameter, the generation module is further configured not to generate a return message corresponding to the request message; The determining module is also used to determine if the current link negotiation fails.

9. A link negotiation control device characterized by comprising: include: Memory; processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the link negotiation control method as described in any one of claims 1 to 6.

Images