CN113141673B

CN113141673B - Link configuration method, device, system and storage medium in multi-link system

Info

Publication number: CN113141673B
Application number: CN202110379872.3A
Authority: CN
Inventors: 吴昊; 王鑫
Original assignee: Chengdu Jimi Technology Co Ltd
Current assignee: Chengdu Jimi Technology Co Ltd
Priority date: 2021-04-08
Filing date: 2021-04-08
Publication date: 2023-03-17
Anticipated expiration: 2041-04-08
Also published as: CN113141673A

Abstract

The application discloses a link configuration method, equipment, a system and a storage medium in a multi-link system, belonging to the technical field of communication. The method comprises the following steps: the media access layer management unit generates a link reset request message according to the link reset request primitive generated by the device management unit and sends the link reset request message to the second communication device, wherein the link reset request message comprises link reset negotiation information, and the link reset negotiation information is used for negotiating the reconfiguration of a target link; the media access layer management unit receives a link reset response message sent by the second communication device, generates a link reset indication primitive according to the link reset response message, and sends the link reset indication primitive to the device management unit, wherein the link reset response message comprises link reset result information, and the link reset result information represents a negotiation result of reconfiguration of a target link; and the equipment management unit executes the reconfiguration of the target link according to the link resetting result information. According to the embodiment of the application, the reconfiguration of the data transmission link under the scene of a multilink system can be realized.

Description

Link configuration method, device, system and storage medium in multi-link system

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method, a device, a system, and a storage medium for configuring links in a multilink system.

Background

With the popularization of Wireless Local Area Networks (WLANs), the number of application types increases, and the requirements on the performance of the Network, such as throughput, delay, and the like, also become higher and higher.

In order to improve the performance of network such as throughput and delay, a plurality of data transmission links may be established between the terminal device and the network Access device (AP). The end Device may comprise a Multi-link Device (MLD). The multi-link device may include a plurality of logical data transceiving terminals (STAs). The network access device may comprise a multi-link access device. A multi-link access device may include multiple logical access points. Data transmission between the terminal equipment and the network access equipment can be realized through a data transmission link between the logic data transceiver terminal and the logic access point.

Due to considerations of load, traffic type, power consumption, etc., the data transmission link between the terminal device and the network access device needs to be reconfigured. However, at present, reconfiguration of a data transmission link cannot be achieved in a multilink system scenario, and therefore, a configuration method capable of achieving a data transmission link in a multilink system scenario is urgently needed.

Disclosure of Invention

Embodiments of the present application provide a method, a device, a system, and a storage medium for configuring a link in a multilink system, which can implement reconfiguration of a data transmission link in a multilink system scenario.

In a first aspect, an embodiment of the present application provides a link configuration method in a multi-link system, which is applied to a first communication device, where the first communication device includes two or more first logic entities, and the first communication device includes a media access layer management unit and a device management unit, and the method includes: the media access layer management unit generates a link reset request message according to a link reset request primitive generated by the equipment management unit, wherein the link reset request primitive comprises link reset negotiation information which is used for negotiating the reconfiguration of a target link; the media access layer management unit sends a link reset request message to second communication equipment, and the second communication equipment comprises more than two second logic entities; the media access layer management unit receives a link resetting response message sent by the second communication device, generates a link resetting indication primitive according to the link resetting response message, and sends the link resetting indication primitive to the device management unit, wherein the link resetting response message comprises link resetting result information, the link resetting indication primitive comprises the link resetting result information, and the link resetting result information is used for representing a negotiation result of the reconfiguration of the target link; and the equipment management unit executes the reconfiguration of the target link according to the link resetting result information.

In a second aspect, an embodiment of the present application provides a link configuration method in a multi-link system, which is applied to a second communication device, where the second communication device includes two or more second logical entities, and the second communication device includes a media access layer management unit and a device management unit, and the method includes: a media access layer management unit receives a link reset request message sent by first communication equipment, wherein the link reset request message comprises link reset negotiation information, the link reset negotiation information is used for negotiating reconfiguration of a target link, and the first communication equipment comprises more than two first logic entities; the media access layer management unit determines whether to accept the reconfiguration of the target link represented by the link resetting negotiation information according to the link resetting negotiation information, generates a link resetting response message and sends the link resetting response message to the first communication device, wherein the link resetting response message comprises link resetting result information, and the link resetting result information is used for representing the negotiation result of the reconfiguration of the target link; or, the media access layer management unit sends a link reset indication primitive generated according to the link reset request message to the device management unit, and the link reset indication primitive includes link reset negotiation information; the equipment management unit determines whether to accept the reconfiguration of the target link represented by the link resetting negotiation information according to the link resetting negotiation information, generates a link resetting response primitive and sends the link resetting response primitive to the media access layer management unit, wherein the link resetting response primitive comprises link resetting result information; the medium access layer management unit sends a link reset response message generated according to the link reset response primitive to the first communication device.

In a third aspect, an embodiment of the present application provides a communication device, where the communication device includes two or more first logic entities, the communication device includes a media access layer management unit and a device management unit, and the communication device includes: a generation control module, configured to control a mac layer management unit to generate a link reset request message according to a link reset request primitive generated by an equipment management unit, where the link reset request primitive includes link reset negotiation information, and the link reset request message includes link reset negotiation information, and the link reset negotiation information is used to negotiate reconfiguration of a target link; the sending control module is used for controlling the media access layer management unit to send a link resetting request message to the second communication equipment, and the second communication equipment comprises more than two second logic entities; the receiving control module is used for controlling the media access layer management unit to receive a link resetting response message sent by the second communication equipment; the generation control module is further used for controlling the media access layer management unit to generate a link reset indication primitive according to the link reset response message, wherein the link reset response message comprises link reset result information, the link reset indication primitive comprises link reset result information, and the link reset result information is used for representing a negotiation result of reconfiguration of a target link; the sending control module is also used for controlling the media access layer management unit to send a link reset indication primitive to the equipment management unit; and the execution control module is used for controlling the equipment management unit to execute the reconfiguration of the target link according to the link resetting result information.

In a fourth aspect, an embodiment of the present application provides a communication device, where the communication device includes two or more second logical entities, the communication device includes a media access layer management unit and a device management unit, and the communication device includes: a receiving control module, configured to control a mac layer management unit to receive a link reset request message sent by a first communication device, where the link reset request message includes link reset negotiation information, and the link reset negotiation information is used to negotiate reconfiguration of a target link, and the first communication device includes two or more first logic entities; a generation control module, configured to control the mac layer management unit to determine, according to the link resetting negotiation information, whether to accept reconfiguration of the target link represented by the link resetting negotiation information, and generate a link resetting response message, where the link resetting response message includes link resetting result information, and the link resetting result information is used to represent a negotiation result of reconfiguration of the target link; the sending control module is used for controlling the media access layer management unit to send a link resetting response message to the first communication equipment; or, the sending control module is used for controlling the media access layer management unit to send a link reset indication primitive generated according to the link reset request message to the device management unit, and the link reset indication primitive includes link reset negotiation information; the generation control module is used for controlling the device management unit to determine whether to accept reconfiguration of a target link represented by the link resetting negotiation information according to the link resetting negotiation information, and generating a link resetting response primitive, the sending control module is also used for controlling the device management unit to send the link resetting response primitive to the media access layer management unit, wherein the link resetting response primitive comprises link resetting result information, and the media access layer management unit is controlled to send a link resetting response message generated according to the link resetting response primitive to the first communication device.

In a fifth aspect, an embodiment of the present application provides a communication device, including: a processor and a memory storing computer program instructions; the processor, when executing the computer program instructions, implements the method for configuring links in a multilink system of the first aspect or the method for configuring links in a multilink system of the second aspect.

In a sixth aspect, an embodiment of the present application provides a multilink system, including: a first communication device for performing the link configuration method in the multilink system of the first aspect; a second communication device for performing the link configuration method in the multilink system of the second aspect.

In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored, and when executed by a processor, the computer program instructions implement the link configuration method in the multilink system of the first aspect or the link configuration method in the multilink system of the second aspect.

The embodiment of the application provides a link configuration method, device, system and storage medium in a multi-link system, a media access layer management unit in first communication equipment can transmit link reset negotiation information to a device management unit in the first communication equipment through a link reset request, and the device management unit in the first communication equipment transmits link reset negotiation information to second communication equipment through the link reset request. The link reset negotiation information is used to negotiate reconfiguration of the target link. Through the link resetting negotiation information, the first communication device and the second communication device can negotiate the reconfiguration of the target link. The second communication device may transmit link reset result information to the first communication device through the link reset response message to notify the first communication device of a negotiation result of the reconfiguration of the target link. The first communication device and the second communication device can negotiate the reconfiguration of the target link through the link resetting request message and the link resetting response message, so that the reconfiguration of a data transmission link under the scene of a multilink system is realized.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required to be used in the embodiments of the present application will be briefly described below, and for those skilled in the art, other drawings may be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic architecture diagram of an example of a multilink system provided in an embodiment of the present application;

fig. 2 is a schematic diagram of an example of a management entity in a terminal device according to an embodiment of the present application;

fig. 3 is a flowchart of an embodiment of a link configuration method in a multi-link system according to a first aspect of the present application;

FIG. 4 is a flowchart of an embodiment of a method for configuring links in a multilink system according to a second aspect of the present application;

FIG. 5 is a flowchart of another embodiment of a method for configuring links in a multilink system according to a second aspect of the present application;

FIG. 6 is a flowchart of a method for configuring links in a multilink system according to a second aspect of the present application;

FIG. 7 is a flowchart of a method for configuring links in a multilink system according to a second aspect of the present application;

fig. 8 is a schematic structural diagram of an embodiment of a communication device according to a third aspect of the present application;

fig. 9 is a schematic structural diagram of an embodiment of a communication device according to a fourth aspect of the present application;

fig. 10 is a schematic hardware structure diagram of an embodiment of a communication device provided in the fifth aspect of the present application.

Detailed Description

Features and exemplary embodiments of various aspects of the present application will be described in detail below, and in order to make objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are merely illustrative of, and not restrictive on, the present application. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present application by illustrating examples thereof.

With the improvement of the requirements for network performance, in order to improve the performance of network throughput, delay, and the like, a plurality of data transmission links may be established between the terminal device and the network Access device (AP). The end Device may comprise a Multi-link Device (MLD). The multi-link device may include a plurality of logical data transceiving terminals (STAs). The network access device may comprise a multi-link access device. The multi-link access device may include a plurality of logical access points. A data transmission link may be established between the logical data-transceiving terminal and the logical access point. I.e. there may be multiple data transmission links established between the multilink device and the multilink access device. Data transmission can be realized between the multilink equipment and the multilink access equipment through a plurality of data transmission links. For convenience of explanation, the data transmission link is simply referred to as a link. The terminal device mentioned below is a terminal device including more than two logical data transceiver terminals, and the network access device is a network device including more than two logical access points.

According to the considerations of the working scenarios and working requirements of the terminal device and the network access device, there is a need to reconfigure the data transmission link between the terminal device and the network access device. The application provides a link configuration method, device, system and storage medium in a multi-link system, which can realize the configuration of links in a multi-link system scene. In some examples, the link configuration method, device, system, and storage medium in the multi-link system provided in the present application may be applied to an Extremely High Throughput (EHT) network, where the EHT network has higher Throughput, higher reliability, and less delay and jitter. The link configuration method in the multilink system in the embodiment of the application can be compatible with the old version technology and backward compatibility, and can be compatible with equipment which operates in frequency bands of 2.4 GHz,5 GHz, 6 GHz and the like.

Fig. 1 is a schematic architecture diagram of an example of a multilink system provided in an embodiment of the present application. As shown in fig. 1, the multi-link system may include a terminal device 11 and a network access device 12. The terminal device 11 may comprise more than two logical data transceiving terminals. Network access device 12 may include more than two logical access points. A link may be established between one logical data-transceiving terminal and one logical access point. For example, as shown in fig. 1, the terminal device 11 includes three logical data transceiving terminals, STA1, STA2, and STA3; the network access device 12 includes three logical access points, AP1, AP2, and AP3. A link 1 is established between the logic data transceiving terminal STA1 and the logic access point AP 1; a link 2 is established between the logic data transceiver terminal STA2 and the logic access point AP 2; the logical data transceiver station STA3 has not established a link yet, and the logical access point AP3 has not established a link yet.

Both the terminal device and the network Access device are deployed with a Media Access Layer (MAC) and a Physical Layer (PHY). The MAC has functions of channel management, connection management, quality of service management, power control, and the like. The PHY has modulation, coding, and transmission. The MAC deployed within the terminal device and the network access device may include a media access layer management element (MLME). The PHYs deployed within the terminal devices and the network access devices may include a Physical Layer Management Entity (PLME). The MLME and PLME may provide a layer management service interface to invoke layer management functions. The terminal device and the network access device may further include a device Management element (SME) which is a layer-independent Entity, has functions of setting a state related to a layer and the like from various Management entities, and sets a parameter value specific to a layer. Fig. 2 is a schematic diagram of an example of a management entity in a terminal device according to an embodiment of the present application. As shown in FIG. 2, the MLME may interact with the PLME, the SME may interact with the MLME, and the SME may interact with the PLME. The relationship between the management entities in the network access device is the same as the relationship between the management entities in the terminal device, and reference may also be made to fig. 2, which is not described herein again.

In some embodiments of the present application, the initiation of the target link reconfiguration may be performed by the terminal device, and correspondingly, the response of the target link reconfiguration may be performed by the network access device. In other embodiments of the present application, the initiating of the target link reconfiguration may be performed by the network access device, and correspondingly, the responding of the target link reconfiguration may be performed by the terminal device. For convenience of explanation, one of the terminal device and the network access device will be referred to as a first communication device, and the other of the terminal device and the network access device will be referred to as a second communication device. The first communication device comprises more than two first logical entities. The second communication device comprises more than two second logical entities. That is, in the case that the first communication device is a network access device, the first logical entity is a logical access point, the second communication device is a terminal device, and the second logical entity is a logical data transceiver terminal. Under the condition that the first communication equipment is terminal equipment, the first logic entity is a logic data receiving and transmitting terminal, the second communication equipment is network access equipment, and the second logic entity is a logic access point.

A first aspect of the present application provides a method for configuring links in a multilink system, which is applicable to a first communication device. The first communication device comprises more than two first logical entities as described above. Fig. 3 is a flowchart of an embodiment of a method for configuring links in a multilink system according to the first aspect of the present application. As shown in fig. 3, the link configuration method may include steps S301 to S304.

In step S301, the mac layer management unit generates a link reset request message according to the link reset request primitive generated by the device management unit.

The request primitive is generated by the device management unit, and includes link reset negotiation information. The link reset request primitive is used to transmit the link reset negotiation information to the medium access layer management unit. The device management unit sends a link reset request primitive to the medium access layer management unit. The media access layer management unit specifically generates a link reset request message according to the link reset negotiation information in the link reset request primitive. The link reset request message is for requesting reconfiguration of the target link to the second communication device. The link reset request message includes link reset negotiation information. The link reset negotiation information is used to negotiate reconfiguration of the target link.

In some embodiments, the link reset negotiation information may include a reset operation type identifier and target link information. The reset operation type identifier is used to identify a reset operation type. Different reset operation type identifications are correspondingly arranged on different reset operation types. The target link information may include configuration information for the target link, which may indicate the target link.

In some examples, the reset operation Type identification, reconfiguration Type, may include one or more of the following: the device comprises a first type identification, a second type identification, a third type identification and a fourth type identification.

The first type identification is used for indicating the addition of the target link. The second type identifier is used for indicating an update target link. The updating of the target link may be implemented by changing a first logical entity in the formed target link or changing a second logical entity in the formed target link, which is not limited herein. The third type identifier is used for indicating the deletion target link. The fourth type identification is used for indicating the service type corresponding to the modification target link. The reset operation type identifier may include numbers, letters, other characters, etc., and is not limited thereto. For example, the first type of identification may be ADD, the second type of identification may be MODIFY, the third type of identification may be REMOVE, and the fourth type of identification may be TID _ MAPPING.

In some examples, the target Link information may include a target Link identification, link ID. The target link identification may include, without limitation, numbers, letters, other characters, and the like.

In other examples, the target link information may include an address or identification of the target first logical entity and an address or identification of the target second logical entity. I.e. the target link information may be an information element comprising an address or identity of the target first logical entity and an address or identity of the target second logical entity. The target first logical entity is the first logical entity forming the target link. The target second logical entity is a second logical entity forming a target link. The Address of the target first logical entity may include a Media Access Control Address (MAC Address) and the like, which are unique to the target first logical entity, and is not limited herein. The identifier of the target first logical entity may be a number, a serial number, etc. of the target first logical entity, and is not limited herein. Similarly, the address of the target second logical entity may include an address unique to the target second logical entity, such as a MAC address, and is not limited herein. The identifier of the target second logical entity may be a number, a serial number, etc. of the target second logical entity, and is not limited herein. For example, if the target first logic entity is a logic data transceiver terminal, the target first logic entity may be the MAC address STAAddress of the logic data transceiver terminal forming the target link; the target second logical entity is a logical access point, and the target second logical entity may be the MAC address APAddress of the logical access point forming the target link.

In still other examples, the target link information may include a target link identification, an address or identification of the target first logical entity, and an address or identification of the target second logical entity. For specific contents of the target link identifier, the address or identifier of the target first logical entity, and the address or identifier of the target second logical entity, reference may be made to the relevant description in the above embodiments, and details are not repeated here.

In other embodiments, the link reset negotiation information may also include link reset parameter information and/or traffic type update information. The link resetting parameter information, i.e., reconfiguration parameters, may include parameters required in the Reconfiguration operation for the target link. In some examples, the link reset negotiation information may include link reset parameter information in the event that the reconfiguration of the target link operates to add or update the target link. The link reset negotiation information may include one or more of a block ack operation parameter, a power saving mode parameter, a security key, and the like, which is not limited herein. The traffic type update message is used to indicate the updated traffic supported by the target link. Note that, there is a case where the services supported by the target link are the same before and after the update. In some examples, the service type update message may include one or more than two service identifiers, and the service characterized by the service identifier is the updated service supported by the target link.

The second communication device may include more than two second logic entities as described above, and details thereof are not repeated herein.

In step S302, the medium access layer management unit transmits a link reset request message to the second communication device.

In particular, the medium access layer management unit in the first communication device may send a link reset request message to the medium access layer management unit in the second communication device. For specific contents of the link reset request message, reference may be made to the relevant description in the above embodiments, and details are not described herein again.

In step S303, the mac layer management unit receives the link reset response message sent by the second communication device, generates a link reset indication primitive according to the link reset response message, and sends the link reset indication primitive to the device management unit.

Specifically, the link reset response message is sent by the medium access layer management unit in the second communication device to the medium access layer management unit in the first communication device.

The Link reset Response message, i.e., the Link reset Response, may include Link reset result information. The link resetting result information is used for representing the negotiation result of the reconfiguration of the target link. In particular, the link reset result information may characterize whether the second communication device performs the reconfiguration of the target link according to the reset negotiation information.

In some examples, the link reset result information includes reset negotiation result information and target link information. The reset negotiation result information may be used to indicate a negotiation result of the reconfiguration. The target link information is used to indicate a target link. For specific content of the target link information, reference may be made to relevant descriptions in the above embodiments, and details are not described herein again.

Specifically, the reset negotiation result information, status code, may include a negotiation success identifier or a non-negotiation success identifier. The negotiation success identifier represents that the second communication equipment executes reconfiguration of the target link according to the link resetting negotiation information. The non-negotiation success identifier characterizes that the second communication device does not perform reconfiguration of the target link according to the link resetting negotiation information. The negotiation success flag may include numbers, letters, other characters, etc., and the non-negotiation success flag may include numbers, letters, other characters, etc., without limitation.

Different non-negotiation success identifications may be set to distinguish a reason why the second communication device does not perform the reconfiguration of the target link according to the link reset negotiation information using the different non-negotiation success identifications. I.e., the non-negotiation success identification, may also be used to indicate a reason why the second communication device did not perform the reconfiguration of the target link according to the link reset negotiation information.

In some examples, the non-negotiation success identification may include a first result identification, a second result identification, or a third result identification.

The first result identification characterizes that the target link already exists at the second communication device. The reconfiguration of the target link by the second communication device not according to the link resetting negotiation information caused by the existence of the second communication device occurs when the reconfiguration indicated by the link resetting request message is to add the target link or update the target link. The target link includes the target link in the link which is formed by the first communication device and the second communication device and is existed in the second communication device, and the reconfiguration such as addition or update of the target link is not required. For example, link 1 and link 2 already exist between the first communication device and the second communication device; a first logic entity A1 in the first communication device and a second logic entity B1 in the second communication device form a link 1, and a first logic entity A2 in the first communication device and a second logic entity B2 in the second communication device form a link 2; and in the case that the added or updated target link is indicated to be a link formed by the first logical entity A2 in the first communication device and the second logical entity B2 in the second communication device in the link resetting request message, confirming that the target link exists in the second communication device and the reconfiguration is not needed.

The second result identification characterizes that the target link does not exist at the second communication device. The target link is not reconfigured according to the link resetting negotiation information by the second communication device caused by the absence of the second communication device, and the reconfiguration is performed to delete the target link when the reconfiguration indicated by the link resetting request message is performed. The target link does not include a target link in the links formed by the first communication device and the second communication device when the second communication device does not exist, and no target link for reconfiguration such as deletion exists. For example, link 1 and link 2 already exist between the first communication device and the second communication device; a first logic entity A1 in the first communication device and a second logic entity B1 in the second communication device form a link 1, and a first logic entity A2 in the first communication device and a second logic entity B2 in the second communication device form a link 2; when the link resetting request message indicates that the deleted target link is a link formed by the first logical entity A3 in the first communication device and the second logical entity B3 in the second communication device, it is determined that the target link does not exist in the third communication device and cannot be deleted.

The third result identification characterizes a rejection by the second communication device of performing a reconfiguration of the target link. And if the second communication equipment does not agree with the reconfiguration of the target link indicated by the link resetting request message, the second communication equipment refuses to execute the reconfiguration of the target link, and can inform the first communication equipment through the third result identifier.

In some examples, the reset negotiation result information may further include one or more of: link resetting parameter information, service type updating information and resetting operation type identification. For specific contents of the link resetting parameter information, the service type updating information, and the resetting operation type identifier, reference may be made to the related description above, and details are not repeated here.

The link reset indication primitive, i.e., the MLME-link reset command. The specific content of the link resetting result information is referred to the above description, and is not described herein again.

In step S304, the device management unit performs reconfiguration of the target link according to the link reset result information.

The device management unit in the first communication device executes reconfiguration of the target link according to the link resetting result information acquired from the medium access layer management unit in the first communication device.

In the case that the link resetting result information indicates that the second communication device performs the reconfiguration of the target link according to the resetting negotiation information, the device management unit in the first communication device may add, update or delete information related to the target link stored in the first communication device according to the link resetting result information, so as to complete the reconfiguration of the target link by the first communication device.

When the link reconfiguration result information indicates that the second communication device does not execute the reconfiguration of the target link according to the reconfiguration negotiation information, the device management unit in the first communication device may keep the information related to the target link, which is originally stored in the first communication device, unchanged, that is, add, update, or delete the information related to the target link, which is originally stored in the first communication device.

In this embodiment of the present application, the mac layer management unit in the first communication device may transmit link reset negotiation information to the mac layer management unit in the first communication device through a link reset request, and the mac layer management unit in the first communication device transmits link reset negotiation information to the second communication device through a link reset request. The link reset negotiation information is used to negotiate reconfiguration of the target link. Through the link resetting negotiation information, the first communication device and the second communication device can negotiate the reconfiguration of the target link. The second communication device may transmit link reset result information to the first communication device through the link reset response message to notify the first communication device of a negotiation result of the reconfiguration of the target link. The first communication device and the second communication device can negotiate the reconfiguration of the target link through the link reset request message and the link reset response message, so that the reconfiguration of the data transmission link under the multi-link system scene is realized.

A second aspect of the present application provides a method for configuring links in a multilink system, which is applicable to a second communication device. The second communication device comprises more than two second logical entities as described above. Fig. 4 is a flowchart of an embodiment of a link configuration method in a multilink system according to a second aspect of the present application. As shown in fig. 4, the link configuration method may include steps S401 and S402, or may include steps S401, S403, S404, and S405.

In step S401, the medium access layer management unit receives a link reset request message sent by the first communication device.

The link reset request message includes link reset negotiation information. The link reset negotiation information is used to negotiate reconfiguration of the target link.

In some examples, the link reset negotiation information may include a reset operation type identification and target link information.

Specifically, the reset operation type identifier includes one or more of the following items: the first type identification, the second type identification, the third type identification and the fourth type identification.

The first type identification is used for indicating the addition of the target link. The second type identifier is used for indicating an update target link. The third type identifier is used for indicating the deletion target link. The fourth type identification is used for indicating the service type corresponding to the modification target link.

In some examples, the target link information includes a target link identification.

In other examples, the target link information includes an address or identification of the target first logical entity and an address or identification of the target second logical entity.

In still other examples, the target link information includes a target link identification, an address or identification of the target first logical entity, and an address or identification of the target second logical entity.

In some examples, the link reset negotiation information may also include link reset parameter information and/or traffic type update information.

For specific contents of the link resetting request message, the link resetting negotiation information, and the like, reference may be made to relevant descriptions in the foregoing embodiments, and details are not described herein again.

The first communication device includes more than two first logic entities, and specific contents may refer to relevant descriptions in the above embodiments, and are not described herein again.

In some embodiments, determining whether to accept reconfiguration of the target link, generating a link reset response message, sending a link reset response message, etc., may be performed by a media access layer management unit in the second communication device. The steps performed by the medium access layer managing unit in the second communication device can be seen in particular in step S402.

In other examples, the medium access layer management unit in the second communication device and the device management unit in the second communication device may interact through primitives to transmit link reset negotiation information, link reset result information, and the like. The determination of whether to accept the reconfiguration of the target link may be performed by a device management unit in the second communication device. The steps executed by the medium access layer management unit in the second communication device and the device management unit in the second communication device can be specifically seen in steps S403 to S405.

In step S402, the mac layer unit determines whether to accept the reconfiguration of the target link indicated by the link resetting negotiation information according to the link resetting negotiation information, generates a link resetting response message, and sends the link resetting response message to the first communication device.

The link reset response message includes link reset result information. The link resetting result information is used for representing the negotiation result of the reconfiguration of the target link.

In some examples, the link reset result information includes reset negotiation result information and target link information.

Specifically, the reset negotiation result information includes a negotiation success flag or a non-negotiation success flag. The negotiation success identifier represents that the second communication equipment executes reconfiguration of the target link according to the link resetting negotiation information. The non-negotiation success identifier characterizes that the second communication device does not execute reconfiguration of the target link according to the link reset negotiation information.

The non-negotiation success identification may include the first result identification, the second result identification, or the third result identification. The first result identification characterizes that the target link already exists at the second communication device. The second result identification characterizes that the target link does not exist at the second communication device. The third result identification characterizes a rejection by the second communication device of performing a reconfiguration of the target link.

In some examples, the reset negotiation result information further includes one or more of: link reset parameter information, service type update information and reset operation type identification.

For specific contents of the link resetting response message and the link resetting result information, reference may be made to relevant descriptions in the above embodiments, and details are not described herein again.

Specifically, the medium access layer management unit in the second communication device may determine whether to accept the reconfiguration of the target link according to a condition of a second logical entity corresponding to the target link in the second communication device.

In step S403, the media access layer management unit sends a link reset indication primitive generated according to the link reset request message to the device management unit.

Media access layer management unit in second communication device to device management unit in second communication device

The link reset indication primitive, i.e., MLME-link rod negotiation. For specific contents of the link resetting negotiation information, reference may be made to the relevant description in the above embodiments, and details are not described herein again.

In step S404, the device management unit determines whether to accept the reconfiguration of the target link represented by the link resetting negotiation information according to the link resetting negotiation information, generates a link resetting response primitive, and sends the primitive to the mac layer management unit.

The link reset response primitive, i.e., MLME-link reset command primitive, may include link reset result information. For the specific content of the link resetting result information, reference may be made to the relevant description in the above embodiments, and details are not repeated herein.

Specifically, the device management unit in the second communication device may determine whether to accept the reconfiguration of the target link according to a condition of a second logical entity corresponding to the target link in the second communication device.

In step S405, the medium access layer management unit sends a link reset response message generated from the link reset response primitive to the first communication device.

The medium access layer management unit in the second communication device and the device management unit in the second communication device transmit link reset negotiation information and link reset result information through a link reset indication primitive and a link reset response primitive.

In the embodiment of the present application, the medium access layer management unit in the second communication device transmits the link reset negotiation information and the link reset result information with the first communication device through the link reset request message and the link reset response message. Or, on the basis that the medium access layer management unit in the second communication device and the first communication device transmit the link reset negotiation information and the link reset result information through the link reset request message and the link reset response message, the medium access layer management unit in the second communication device and the device management unit in the second communication device transmit the link reset information and the link reset result information through the link reset indication primitive and the link reset response primitive. And the second communication equipment determines whether to accept the reconfiguration of the target link or not through the information acquired by interacting with the first communication equipment so as to realize the reconfiguration of the data transmission link in the multi-link system scene.

The following describes how to determine whether to accept the content of reconfiguration of the target link represented by the link resetting negotiation information according to the link resetting negotiation information.

In some examples, the link reset negotiation information is used to indicate deletion of the target link. Fig. 5 is a flowchart of another embodiment of a link configuration method in a multi-link system according to a second aspect of the present application. Fig. 5 is different from fig. 4 in that step S402 shown in fig. 4 can be subdivided into step S4021 and step S4022. For convenience of description, the refinement flow of step S402 is described here, but in this embodiment, the refinement of step S404 may refer to step S4021 and step S4022, and is not described herein again.

In step S4021, in the case that the second communication device has a second logical entity associated with the target first logical entity in the target link, and the reset operation type identifier includes the third type identifier, accepting the reconfiguration of the target link and generating a link reset response message characterizing the execution of the reconfiguration of the target link.

The reset operation type identifier comprises a third type identifier indicating deletion of the target link. And under the condition that the target link is indicated to be deleted, the second communication equipment has a second logic entity associated with the target first logic entity in the target link, the existence of the target link is represented, the reconfiguration, namely deletion, of the target link can be accepted, and a link resetting response message is generated. The target first logic entity is a first logic entity corresponding to the target link. The second logical entity already associated with the target first logical entity is the second logical entity in the already existing link corresponding to the target first logical entity.

Specifically, the second communication device has a second logical entity associated with the target first logical entity in the target link, and the second communication device may delete the link setting information of the second logical entity associated with the target first logical entity, that is, perform an operation of deleting the target link. In particular, a link reset response message may be generated that includes a negotiation success identification.

In step S4022, if there is no second logical entity associated with the target first logical entity in the target link in the second communication device and the reset operation type identifier includes the third type identifier, the reconfiguration of the target link is not accepted, and a link reset response message is generated that indicates that the reconfiguration of the target link is not performed.

The reset operation type identifier comprises a third type identifier indicating deletion of the target link. When the target link is instructed to be deleted, the second communication device does not have the second logical entity associated with the target first logical entity in the target link, and the second communication device indicates that the target link instructed to be deleted does not exist, and the nonexistent target link cannot be deleted, so that the second communication device does not accept the reconfiguration, namely the deletion, of the target link. Correspondingly, a link reset response message indicating that the target link does not exist may be specifically generated, such as generating a link reset response message including the second result identification.

In some examples, the link reset negotiation information is used to indicate that the target link is added or updated. Fig. 6 is a flowchart of a method for configuring links in a multi-link system according to a second aspect of the present application. Fig. 6 differs from fig. 4 in that step S402 shown in fig. 4 can be subdivided into step S4023 to step S4025, and step S4026. For convenience of description, the refining flow of step S402 is described here, but in this embodiment, the step S404 may also refer to step S4023 to step S4025, and refer to step S4026, which is not described herein again.

In step S4023, in a case that the second communication device has a second logical entity associated with the target first logical entity in the target link and the reset operation type identifier includes the first type identifier or the second type identifier, it is determined whether the associated second logical entity is the same as the target second logical entity in the target link.

The reset operation type identifier comprises a first type identifier or a second type identifier and indicates that the target link is added or updated. In the case of indicating to add or update the target link, the second communication device has a second logical entity associated with the target first logical entity in the target link, which indicates that the second logical entity corresponding to the target link exists, and needs to further confirm the second logical entity associated with the target first logical entity, and determine whether the second logical entity corresponding to the target link indicated by the link resetting negotiation information is the same as the second logical entity associated with the target first logical entity.

In step S4024, in case that the associated second logical entity is the same as the target second logical entity in the target link, the reconfiguration of the target link is not accepted, and a link reset response message indicating that the target link already exists in the second communication device is generated.

The target second logic entity is a second logic entity corresponding to the target link. The associated second logical entity is the same as the target second logical entity in the target link, which means that the existing link is the same as the target link, i.e. indicating that the added or updated target link already exists, and the reconfiguration is not required. Thus, reconfiguration of the target link is not accepted. Correspondingly, a link reset response message including the first result identification may be generated.

In step S4025, in case the associated second logical entity is different from the target second logical entity in the target link, the reconfiguration of the target link is accepted and executed, and a link reset response message indicating that the reconfiguration of the target link is executed is generated.

The associated second logical entity is different from the target second logical entity in the target link, which means that the existing link is different from the target link, i.e. indicates that the added or updated target link does not exist, and therefore the reconfiguration of the target link is accepted to add or update the target link.

Specifically, the setting information of the original link formed by the existing target first logical entity and the associated second logical entity may be deleted, and the setting information of the target link, which is the link between the target first logical entity and the target second logical entity, is newly established. Alternatively, the setting information of the original link may be changed so that the changed setting information of the original link is consistent with the setting information of the target link. For example, the address and configuration parameters of the associated second logical entity are modified to the address and configuration parameters of the target second logical entity. Specifically, a link reset response message including the negotiation success flag may be generated.

In step S4026, in the case that there is no second logical entity associated with the target first logical entity in the target link in the second communication device, and the reset operation type identifier includes the first type identifier or the second type identifier, accepting and executing the reconfiguration of the target link, and generating a link reset response message characterizing the execution of the reconfiguration of the target link.

The reset operation type identifier comprises a first type identifier or a second type identifier and indicates that the target link is added or updated. Under the condition that the target link is instructed to be added or updated, a second logic entity which is associated with a target first logic entity in the target link does not exist in the second communication device, which indicates that the target link does not exist and a target link formed by the target first logic entity and the target second logic entity needs to be established. Specifically, a link reset response message including the negotiation success flag may be generated.

In some examples, the link reset negotiation information is used to indicate that the traffic type corresponding to the target link is modified. Fig. 7 is a flowchart of a method for configuring links in a multi-link system according to a second aspect of the present application. Fig. 7 differs from fig. 4 in that step S402 shown in fig. 4 can be subdivided into step S4027 and step S4028 in fig. 7. For convenience of description, the refinement flow of step S402 is described here, but in this embodiment, the refinement of step S404 may refer to step S4027 and step S4028, and is not described herein again.

In step S4027, in the case that the second communication device does not have the second logical entity associated with the target first logical entity in the target link, and the reset operation type identifier includes the fourth type identifier, the reconfiguration of the target link is not accepted, and a link reset response message indicating that the target link does not exist in the second communication device is generated.

The reset operation type identifier comprises a fourth type identifier which indicates that the service type corresponding to the target link is modified. Under the condition of modifying the service type corresponding to the target link, the second communication device does not have a second logic entity associated with the target first logic entity in the target link, which indicates that the target link does not exist, the service type corresponding to the target link which does not exist cannot be modified, and the reconfiguration of the target link is not accepted. In particular, a link reset response message may be generated that includes the second result identification.

Specifically, the reconfiguration of the target link is not accepted, the service type corresponding to the established link can be kept unchanged, and no operation is performed.

In step S4028, if a second logical entity already associated with the target first logical entity in the target link exists in the second communication device, and the reset operation type identifier includes a fourth type identifier, the second communication device accepts the reconfiguration of the target link according to the configuration supported by the associated second logical entity, and generates a link reset response message indicating that the reconfiguration of the target link is to be performed.

The reset operation type identifier comprises a fourth type identifier which indicates that the service type corresponding to the target link is modified. And under the condition of modifying the service type corresponding to the target link, the second communication equipment has a second logic entity associated with the target first logic entity in the target link, which indicates that the target link exists, and can modify the service type corresponding to the existing target link and accept the reconfiguration of the target link. In particular, a link reset response message may be generated that includes a negotiation success identification.

Specifically, the reconfiguration of the target link is accepted, and the original service type corresponding to the target link is updated to the service type indicated by the reset negotiation result information.

The second communication device may store information related to the established link, such as a link identifier of the established link, address and configuration information of the first logical entity corresponding to the established link, address and configuration information of the second logical entity corresponding to the established link, and the like, which is not limited herein. The detection of whether the second communication device has the second logic entity associated with the target first logic entity in the target link can be realized through the detection of the target link information.

In some examples, the target link information includes a target link identification, and whether a link identification consistent with the target link identification exists may be queried in link identifications of established links stored in the second communication device. And if the link identification consistent with the target link identification exists in the link identifications of the established links stored in the second communication equipment, determining that the second communication equipment has a second logic entity associated with the target first logic entity in the target link. And if the link identifier which is consistent with the target link identifier does not exist in the link identifiers of the established links stored in the second communication equipment, determining that the second communication equipment does not have a second logic entity which is associated with the target first logic entity in the target link.

In other examples, the target link information includes an address or identification of the target first logical entity and an address or identification of the target second logical entity. Whether the address or the identification of the target second logical entity exists can be inquired in the address and the configuration information of the second logical entity corresponding to the established link stored in the second communication device. And if the address or the identifier of the target second logic entity exists in the address and the configuration information of the second logic entity corresponding to the established link stored in the second communication device, determining that the second communication device has the second logic entity associated with the target first logic entity in the target link. And if the address or the identifier of the target second logic entity does not exist in the address and the configuration information of the second logic entity corresponding to the established link stored in the second communication device, determining that the second communication device does not have the second logic entity associated with the target first logic entity in the target link.

In still other examples, the target link information includes a target link identification, an address or identification of the target first logical entity, and an address or identification of the target second logical entity. Whether a link identifier consistent with the target link identifier exists may be queried in the link identifier of the established link stored in the second communication device, or whether an address or an identifier of the target second logic entity exists may be queried in the address and configuration information of the second logic entity corresponding to the established link stored in the second communication device, and specific contents may refer to the above-mentioned related description, which is not described herein again.

A third aspect of the present application provides a communication apparatus, that is, the first communication apparatus in the above embodiments. The communication device comprises more than two first logical entities. The communication device may include a media access layer management unit and a device management unit. Fig. 8 is a schematic structural diagram of an embodiment of a communication device according to a third aspect of the present application. As shown in fig. 8, the communication apparatus 500 may include a generation control module 501, a transmission control module 502, a reception control module 503, and an execution control module 504.

The generation control module 501 may be configured to control the mac layer management unit to generate a link reset request message according to the link reset request primitive generated by the device management unit.

The link reset request primitive includes link reset negotiation information. The link reset request message includes link reset negotiation information. The link reset negotiation information is used to negotiate reconfiguration of the target link.

In some examples, the link reset negotiation information includes a reset operation type identification and target link information.

In some examples, the link reset negotiation information further includes link reset parameter information and/or traffic type update information.

Specifically, the reset operation type identifier includes one or more of the following items: the device comprises a first type identification, a second type identification, a third type identification and a fourth type identification. Wherein the first type identification is used for indicating the addition target link. The second type identifier is used for indicating an update target link. The third type identification is used for indicating deletion of the target link. The fourth type identification is used for indicating the service type corresponding to the modification target link.

Specifically, the target link information includes a target link identification. Alternatively, the target link information includes an address or identity of the target first logical entity and an address or identity of the target second logical entity. Alternatively, the target link information includes a target link identification, an address or identification of the target first logical entity, and an address or identification of the target second logical entity.

The sending control module 502 may be configured to control the medium access layer management unit to send a link reset request message to the second communication device.

The second communication device comprises more than two second logical entities.

The receiving control module 503 may be configured to control the medium access layer management unit to receive a link reset response message sent by the second communication device.

In some examples, the non-negotiation success identification includes a first result identification, a second result identification, or a third result identification. The first result identification represents that the second logic entity corresponding to the target link already exists in the second communication device. The second result identification characterizes that the target link does not exist at the second communication device. The third result identification characterizes a rejection by the second communication device of performing a reconfiguration of the target link.

For specific contents of the reset operation type identifier, the target link information, and the like, reference may be made to relevant descriptions in the above embodiments, and details are not described herein again.

The generation control module 501 may be further configured to control the mac layer management unit to generate a link reset indication primitive according to the link reset response message.

The link reset response message includes link reset result information. The link reset indication primitive includes link reset result information. The link resetting result information is used for representing the negotiation result of the reconfiguration of the target link.

The sending control module 502 may also be configured to control the mac layer management unit to send a link reset indication primitive to the device management unit.

The execution control module 504 may be configured to control the device management unit to execute the reconfiguration of the target link according to the link resetting result information.

In this embodiment of the present application, a media access layer management unit in a communication device, that is, a first communication device, may transmit link reset negotiation information to a device management unit in the communication device through a link reset request, and the device management unit in the communication device may transmit link reset negotiation information to a second communication device through a link reset request. The link reset negotiation information is used to negotiate reconfiguration of the target link. Through the link reset negotiation information, the communication device and the second communication device may negotiate for reconfiguration of the target link. The second communication device may transmit the link reset result information to the communication device through the link reset response message to notify the communication device of the negotiation result of the reconfiguration of the target link. The communication device and the second communication device can negotiate the reconfiguration of the target link through the link resetting request message and the link resetting response message, so that the reconfiguration of the data transmission link under the scene of the multilink system is realized.

In some embodiments, the communication device 500 is a network access device, the first logical entity is a logical access point, the second communication device is a terminal device, and the second logical entity is a logical data transceiver terminal.

In other embodiments, the communication device 500 is a terminal device, the first logical entity is a logical data transceiver terminal, the second communication device is a network access device, and the second logical entity is a logical access point.

For details of the communication device 500, reference may be made to the related description in the link configuration method applied to the multi-link system of the first communication device in the foregoing embodiment, and details are not repeated herein.

A fourth aspect of the present application provides a communication apparatus, that is, the second communication apparatus in the above-described embodiment. The communication device comprises more than two second logical entities. The communication device may include a media access layer management unit and a device management unit. Fig. 9 is a schematic structural diagram of an embodiment of a communication device according to a fourth aspect of the present application. As shown in fig. 9, the communication device 600 may include a reception control module 601, a generation control module 602, and a transmission control module 603.

The receiving control module 601 may be configured to control the mac layer management unit to receive a link reset request message sent by the first communication device.

The link reset request message includes link reset negotiation information. The link reset negotiation information is used to negotiate reconfiguration of the target link. The first communication device includes more than two first logical entities.

Specifically, the reset operation type identifier includes one or more of the following items: the first type identification, the second type identification, the third type identification and the fourth type identification. The first type identification is used for indicating the addition target link. The second type identifier is used for indicating an update target link. The third type identifier is used for indicating the deletion target link. The fourth type identification is used for indicating the service type corresponding to the modification target link.

The generation control module 602 may be configured to control the mac layer management unit to determine whether to accept reconfiguration of the target link represented by the link resetting negotiation information according to the link resetting negotiation information, and generate a link resetting response message.

In some examples, the non-negotiation success identification comprises a first result identification, a second result identification, or a third result identification. The first result identification characterizes that the target link already exists at the second communication device. The second result identification characterizes that the target link does not exist at the second communication device. The third result identification characterizes a rejection by the second communication device of performing a reconfiguration of the target link.

The transmission control module 603 may be configured to control the medium access layer management unit to transmit a link reset response message to the first communication device.

In other embodiments, the receiving control module 601 in the communication device 600 is configured to control the mac layer management unit to receive the link reset request message sent by the first communication device.

The sending control module 603 in the communication device 600 may be configured to control the medium access layer management unit to send a link reset indication primitive generated according to the link reset request message to the device management unit.

The link reset indication primitive includes link reset negotiation information.

The generation control module 602 in the communication device 600 is configured to control the device management unit to determine whether to accept the reconfiguration of the target link represented by the link resetting negotiation information according to the link resetting negotiation information, and generate a link resetting response primitive.

The sending control module 603 in the communication device 600 may be further configured to control the device management unit to send a link reset response primitive to the media access layer management unit, and control the media access layer management unit to send a link reset response message generated according to the link reset response primitive to the first communication device.

The link reset response primitive includes link reset result information.

In the embodiment of the present application, a medium access layer management unit in a communication device, that is, a second communication device, transmits link reset negotiation information and link reset result information with a first communication device through a link reset request message and a link reset response message. Or, on the basis that the medium access layer management unit in the communication device and the first communication device transmit the link reset negotiation information and the link reset result information through the link reset request message and the link reset response message, the medium access layer management unit in the communication device and the device management unit in the communication device transmit the link reset information and the link reset result information through the link reset indication primitive and the link reset response primitive. The communication equipment determines whether to accept the reconfiguration of the target link or not through the information acquired by interacting with the first communication equipment, so as to realize the reconfiguration of the data transmission link under the scene of the multilink system.

In some embodiments, the first communication device is a network access device, the first logical entity is a logical access point, the communication device 600 is a terminal device, and the second logical entity is a logical data transceiver terminal.

In other embodiments, the first communication device is a terminal device, the first logical entity is a logical data transceiver terminal, the communication device 600 is a network access device, and the second logical entity is a logical access point.

In some examples, the generation control module 602 may be configured to: and in the case that a second logic entity which is associated with a target first logic entity in the target link exists in the communication equipment, and the reset operation type identifier comprises a third type identifier, accepting the reconfiguration of the target link and generating a link reset response message for representing the execution of the reconfiguration of the target link.

In some examples, the generation control module 602 may be configured to: and in the case that a second logic entity which is associated with the target first logic entity in the target link does not exist in the communication equipment, and the reset operation type identifier comprises a third type identifier, not accepting the reconfiguration of the target link and generating a link reset response message for representing that the reconfiguration of the target link is not executed.

In some examples, the generation control module 602 may be configured to: determining whether the associated second logic entity is the same as the target second logic entity in the target link or not under the condition that the second logic entity associated with the target first logic entity in the target link exists in the communication equipment and the resetting operation type identifier comprises a first type identifier or a second type identifier; under the condition that the associated second logic entity is the same as the target second logic entity in the target link, not accepting the reconfiguration of the target link and generating a link resetting response message for representing that the target link exists in the communication equipment; and in the case that the associated second logic entity is different from the target second logic entity in the target link, accepting and executing the reconfiguration of the target link, and generating a link reset response message for representing the execution of the reconfiguration of the target link.

In some examples, the generation control module 602 may be configured to: and under the condition that a second logic entity which is associated with a target first logic entity in the target link does not exist in the communication equipment and the resetting operation type identifier comprises the first type identifier or the second type identifier, accepting and executing the reconfiguration of the target link and generating a link resetting response message for representing the execution of the reconfiguration of the target link.

In some examples, the generation control module 602 may be configured to: and in the case that a second logic entity which is associated with the target first logic entity in the target link does not exist in the communication equipment, and the reset operation type identifier comprises a fourth type identifier, not accepting the reconfiguration of the target link and generating a link reset response message which is characterized in that the target link does not exist in the communication equipment.

In some examples, the generation control module 602 may be configured to: and in the case that a second logic entity which is associated with the target first logic entity in the target link exists in the communication equipment, and the reset operation type identifier comprises a fourth type identifier, the reconfiguration of the target link is accepted according to the configuration supported by the associated second logic entity, and a link reset response message which is used for representing the execution of the reconfiguration of the target link is generated.

The embodiment of the application also provides communication equipment. Fig. 10 is a schematic hardware structure diagram of an embodiment of a communication device provided in the fifth aspect of the present application. As shown in fig. 10, the communication device 700 comprises a memory 701, a processor 702 and a computer program stored on the memory 701 and executable on the processor 702.

In one example, the processor 702 may include a Central Processing Unit (CPU), or an Application Specific Integrated Circuit (ASIC), or may be configured to implement one or more Integrated circuits of embodiments of the present Application.

Memory 701 may include Read-Only Memory (ROM), random Access Memory (RAM), magnetic disk storage media devices, optical storage media devices, flash Memory devices, electrical, optical, or other physical/tangible Memory storage devices. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software comprising computer-executable instructions and when the software is executed (e.g., by one or more processors) it is operable to perform operations described with reference to the link configuration method in a multi-link system according to the first aspect or the link configuration method in a multi-link system according to the second aspect of the present application.

The processor 702 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 701, for implementing the method for configuring a link in a multilink system of the first aspect or the method for configuring a link in a multilink system of the second aspect in the above-described embodiments.

In one example, the communication device 700 may also include a communication interface 703 and a bus 704. As shown in fig. 10, the memory 701, the processor 702, and the communication interface 703 are connected by a bus 704 to complete mutual communication.

The communication interface 703 is mainly used for implementing communication between modules, apparatuses, units and/or devices in this embodiment of the application. Input devices and/or output devices may also be accessed through communications interface 703.

The bus 704 includes hardware, software, or both to couple the components of the communication device 700 to one another. By way of example and not limitation, bus 704 may include an Accelerated Graphics Port (AGP) or other Graphics Bus, an Enhanced Industrial Standard Architecture (EISA) Bus, a Front Side Bus (Front Side Bus, FSB), a Hyper Transport (HT) Interconnect, an Industrial Standard Architecture (Industry Standard Architecture) Bus, an infiniband Interconnect, a Low Pin Count (LPC) Bus, a memory Bus, a microchannel Architecture (MCA) Bus, a Peripheral Component Interconnect (PCI) Bus, a PCI-Express (PCI-X) Bus, a Serial Advanced Technology Attachment (Attachment Technology) Bus, a Video Electronics Standards Local Association (Video Electronics Association), or other suitable combination of two or more of these buses. Bus 704 may include one or more buses, where appropriate. Although specific buses are described and shown in the embodiments of the present application, any suitable buses or interconnects are contemplated by the present application.

An embodiment of the present application further provides a computer-readable storage medium, where computer program instructions are stored on the computer-readable storage medium, and when the computer program instructions are executed by a processor, the method for configuring links in a multi-link system according to the first aspect or the second aspect in the foregoing embodiments can be implemented, and the same technical effects can be achieved, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may include a non-transitory computer-readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and the like, which is not limited herein.

It should be clear that the embodiments in this specification are described in a progressive manner, and the same or similar parts in the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. For communication device embodiments, system embodiments, computer-readable storage medium embodiments, reference may be made to the description of the method embodiments for relevant points. The present application is not limited to the particular steps and structures described above and shown in the drawings. Those skilled in the art may make various changes, modifications and additions or change the order between the steps after appreciating the spirit of the present application. Also, a detailed description of known process techniques is omitted herein for the sake of brevity.

Aspects of the present application are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions/acts specified in the flowchart and/or block diagram block or blocks. Such a processor may be, but is not limited to, a general purpose processor, a special purpose processor, an application specific processor, or a field programmable logic circuit. It will also be understood that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware for performing the specified functions or acts, or combinations of special purpose hardware and computer instructions.

It should be understood by those skilled in the art that the above embodiments are illustrative and not restrictive. Different features which are present in different embodiments may be combined to advantage. Other variations to the disclosed embodiments can be understood and effected by those skilled in the art upon studying the drawings, the specification, and the claims. In the claims, the term "comprising" does not exclude other means or steps; the word "a" or "an" does not exclude a plurality; the terms "first" and "second" are used to denote a name and not to denote any particular order. Any reference signs in the claims shall not be construed as limiting the scope. The functions of the various parts appearing in the claims may be implemented by a single hardware or software module. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

Claims

1. A method for configuring a link in a multi-link system, the method being applied to a first communication device, the first communication device including two or more first logical entities, the first communication device including a medium access layer management unit and a device management unit, the medium access layer management unit belonging to a medium access layer, the device management unit being a layer-independent entity, the method comprising:

the media access layer management unit generates a link reset request message according to a link reset request primitive generated by the device management unit, wherein the link reset request primitive comprises the link reset negotiation information, the link reset request message comprises the link reset negotiation information, and the link reset negotiation information is used for negotiating the reconfiguration of a target link;

the media access layer management unit sends the link reset request message to a second communication device, wherein the second communication device comprises more than two second logic entities;

the media access layer management unit receives a link reset response message sent by the second communication device, generates a link reset indication primitive according to the link reset response message, and sends the link reset indication primitive to the device management unit, where the link reset response message includes link reset result information, the link reset indication primitive includes the link reset result information, and the link reset result information is used to characterize a negotiation result of reconfiguration of the target link;

and the equipment management unit executes the reconfiguration of the target link according to the link resetting result information.

2. The method of claim 1, wherein the link reset negotiation information comprises a reset operation type identifier and target link information.

3. The method according to claim 2, wherein the link reset negotiation information further comprises link reset parameter information and/or traffic type update information.

4. The method of claim 1, wherein the link reset result information comprises reset negotiation result information and target link information.

5. The method of claim 4, wherein the reset negotiation result information comprises a negotiation success flag or a non-negotiation success flag,

the negotiation success identifier represents that the second communication device executes reconfiguration of the target link according to the link resetting negotiation information,

and the non-negotiation success identifier represents that the second communication equipment does not execute the reconfiguration of the target link according to the link resetting negotiation information.

6. The method of claim 5, wherein the non-negotiation success flag comprises a first result flag, a second result flag, or a third result flag,

the first result identification characterizes that the second logical entity corresponding to the target link already exists at the second communication device,

the second result identification characterizing the absence of the target link at the second communication device,

the third result identification characterizes that the second communication device refuses to perform the reconfiguration of the target link.

7. The method of claim 4, wherein the reset negotiation result information further comprises one or more of the following:

link reset parameter information, service type update information and reset operation type identification.

8. The method of claim 2 or 7, wherein the reset operation type identifier comprises one or more of:

the first type identification, the second type identification, the third type identification and the fourth type identification;

wherein the first type identifier is used to indicate that the target link is added,

the second type identifier is used for indicating to update the target link,

the third type identification is used for indicating the deletion of the target link,

the fourth type identification is used for indicating the modification of the service type corresponding to the target link.

9. The method according to claim 2 or 4, wherein the target link information comprises:

a target link identification;

or,

an address or identity of a target first logical entity, and an address or identity of a target second logical entity;

or,

a target link identification, an address or identification of a target first logical entity, and an address or identification of a target second logical entity.

10. The method of claim 1,

the first communication equipment is network access equipment, the first logic entity is a logic access point, the second communication equipment is terminal equipment, and the second logic entity is a logic data transceiver terminal;

or,

the first communication device is a terminal device, the first logic entity is a logic data transceiver terminal, the second communication device is a network access device, and the second logic entity is a logic access point.

11. A method for configuring a link in a multi-link system, the method being applied to a second communication device, the second communication device including two or more second logical entities, the second communication device including a medium access layer management unit and a device management unit, the medium access layer management unit belonging to a medium access layer, the device management unit being a layer-independent entity, the method comprising:

the media access layer management unit receives a link reset request message sent by a first communication device, wherein the link reset request message comprises link reset negotiation information, the link reset negotiation information is used for negotiating reconfiguration of a target link, and the first communication device comprises more than two first logic entities;

the MAC layer management unit determines whether to accept the reconfiguration of the target link represented by the link resetting negotiation information according to the link resetting negotiation information, generates a link resetting response message and sends the link resetting response message to the first communication device, wherein the link resetting response message comprises link resetting result information, and the link resetting result information is used for representing a negotiation result of the reconfiguration of the target link;

or, the mac layer management unit sends a link reset indication primitive generated according to the link reset request message to the device management unit, where the link reset indication primitive includes the link reset negotiation information; the device management unit determines whether to accept the reconfiguration of the target link represented by the link reset negotiation information according to the link reset negotiation information, generates a link reset response primitive and sends the link reset response primitive to the media access layer management unit, wherein the link reset response primitive comprises link reset result information; the media access layer management unit sends the link reset response message generated according to the link reset response primitive to the first communication device.

12. The method of claim 11, wherein the link reset negotiation information comprises a reset operation type identifier and target link information.

13. The method according to claim 12, wherein the link reset negotiation information further comprises link reset parameter information and/or traffic type update information.

14. The method of claim 11, wherein the link reset result information comprises reset negotiation result information and target link information.

15. The method of claim 14, wherein the reset negotiation result information comprises a negotiation success flag or a non-negotiation success flag,

16. The method of claim 15, wherein the non-negotiation success flag comprises a first result flag, a second result flag, or a third result flag,

the first result identification characterizes that the target link already exists at the second communication device,

the second result identification characterizes the target link as not present at the second communication device,

17. The method of claim 14, wherein the reset negotiation result information further comprises one or more of the following:

link resetting parameter information, service type updating information and resetting operation type identification.

18. The method of claim 12 or 17, wherein the reset operation type identifier comprises one or more of:

wherein the first type identification is used to indicate that the target link is added,

the second type identifier is used for indicating to update the target link,

and the fourth type identification is used for indicating to modify the service type corresponding to the target link.

19. The method according to claim 12 or 14, wherein the target link information comprises:

a target link identification;

or,

20. The method of claim 18, wherein the determining whether to accept the reconfiguration of the target link characterized by the link reset negotiation information according to the link reset negotiation information, and generating a link reset response message comprises:

and in the case that a second logic entity which is associated with a target first logic entity in the target link exists in the second communication device, and the reset operation type identifier comprises the third type identifier, accepting the reconfiguration of the target link and generating the link reset response message which is used for representing the execution of the reconfiguration of the target link.

21. The method of claim 18, wherein the determining whether to accept the reconfiguration of the target link characterized by the link reset negotiation information according to the link reset negotiation information, and generating a link reset response message comprises:

and in the case that a second logic entity which is associated with a target first logic entity in the target link does not exist in the second communication device, and the reset operation type identifier comprises the third type identifier, not accepting the reconfiguration of the target link, and generating the link reset response message which is used for representing that the reconfiguration of the target link is not executed.

22. The method of claim 18, wherein the determining whether to accept the reconfiguration of the target link indicated by the link resetting negotiation information according to the link resetting negotiation information and generating a link resetting response message comprises:

determining whether the associated second logical entity is the same as a target second logical entity in the target link, if a second logical entity associated with the target first logical entity in the target link exists in the second communication device, and the reset operation type identifier includes the first type identifier or the second type identifier;

in the case that the associated second logical entity is the same as a target second logical entity in the target link, not accepting reconfiguration of the target link and generating the link reset response message representing that the target link already exists at the second communication device;

and in the case that the associated second logic entity is different from a target second logic entity in the target link, accepting and executing the reconfiguration of the target link, and generating the link resetting response message for representing the execution of the reconfiguration of the target link.

23. The method of claim 18, wherein the determining whether to accept the reconfiguration of the target link characterized by the link reset negotiation information according to the link reset negotiation information, and generating a link reset response message comprises:

and in the case that a second logic entity which is associated with a target first logic entity in the target link does not exist in the second communication device, and the reset operation type identifier comprises the first type identifier or the second type identifier, accepting and executing the reconfiguration of the target link, and generating the link reset response message which is used for representing the execution of the reconfiguration of the target link.

24. The method of claim 18, wherein the determining whether to accept the reconfiguration of the target link indicated by the link resetting negotiation information according to the link resetting negotiation information and generating a link resetting response message comprises:

and in the case that a second logical entity which is already associated with a target first logical entity in the target link does not exist in the second communication device, and the reset operation type identifier includes the fourth type identifier, not accepting the reconfiguration of the target link, and generating the link reset response message which represents that the target link does not exist in the second communication device.

25. The method of claim 18, wherein the determining whether to accept the reconfiguration of the target link indicated by the link resetting negotiation information according to the link resetting negotiation information and generating a link resetting response message comprises:

and in the case that a second logical entity associated with a target first logical entity in the target link exists in the second communication device, and the reset operation type identifier includes the fourth type identifier, accepting the reconfiguration of the target link according to the configuration supported by the associated second logical entity, and generating the link reset response message representing that the reconfiguration of the target link is performed.

26. The method of claim 11,

or,

27. A communication device comprising two or more first logical entities, the communication device comprising a medium access layer management unit and a device management unit, the medium access layer management unit belonging to a medium access layer and the device management unit being a layer independent entity, the communication device comprising:

a generation control module, configured to control the mac layer management unit to generate a link reset request message according to a link reset request primitive generated by the device management unit, where the link reset request primitive includes the link reset negotiation information, and the link reset request message includes the link reset negotiation information, and the link reset negotiation information is used to negotiate reconfiguration of a target link;

a sending control module, configured to control the mac unit to send the link reset request message to a second communication device, where the second communication device includes two or more second logic entities;

a receiving control module, configured to control the mac layer management unit to receive a link reset response message sent by the second communication device;

the generation control module is further configured to control the mac layer management unit to generate a link reset indication primitive according to the link reset response message, where the link reset response message includes link reset result information, the link reset indication primitive includes the link reset result information, and the link reset result information is used to characterize a negotiation result of the reconfiguration of the target link;

the sending control module is further configured to control the mac layer management unit to send the link reset indication primitive to the device management unit;

and the execution control module is used for controlling the equipment management unit to execute the reconfiguration of the target link according to the link resetting result information.

28. A communication device comprising two or more second logical entities, the communication device comprising a medium access layer management unit and a device management unit, the medium access layer management unit belonging to a medium access layer and the device management unit being a layer-independent entity, the communication device comprising:

a receiving control module, configured to control the mac layer management unit to receive a link reset request message sent by a first communication device, where the link reset request message includes link reset negotiation information, the link reset negotiation information is used to negotiate reconfiguration of a target link, and the first communication device includes two or more first logic entities;

a generation control module, configured to control the mac layer management unit to determine, according to the link resetting negotiation information, whether to accept the reconfiguration of the target link represented by the link resetting negotiation information, and generate a link resetting response message, where the link resetting response message includes link resetting result information, and the link resetting result information is used to represent a negotiation result of the reconfiguration of the target link;

a sending control module, configured to control the mac unit to send the link reset response message to the first communication device;

or,

the sending control module is configured to control the mac layer management unit to send a link reset indication primitive generated according to the link reset request message to the device management unit, where the link reset indication primitive includes the link reset negotiation information;

the generation control module is configured to control the device management unit to determine whether to accept the reconfiguration of the target link indicated by the link resetting negotiation information according to the link resetting negotiation information, generate the link resetting response primitive,

the sending control module is further configured to control the device management unit to send the link reset response primitive to the media access layer management unit, where the link reset response primitive includes link reset result information, and control the media access layer management unit to send the link reset response message generated according to the link reset response primitive to the first communication device.

29. A communication device, comprising: a processor and a memory storing computer program instructions;

the processor, when executing the computer program instructions, implements a method of link configuration in a multilink system as claimed in any one of claims 1 to 26.

30. A multi-link system, comprising:

a first communication device for performing the method of link configuration in a multilink system according to any one of claims 1 to 10;

second communication device for performing the method of link configuration in a multilink system according to any one of claims 11 to 26.

31. A computer-readable storage medium, having stored thereon computer program instructions which, when executed by a processor, implement a method of link configuration in a multi-link system as claimed in any one of claims 1 to 26.