CN111935800B

CN111935800B - System message changing method under multilink scene, terminal equipment and storage medium

Info

Publication number: CN111935800B
Application number: CN202010804887.5A
Authority: CN
Inventors: 吴昊; 谢芳; 廖杨
Original assignee: Chengdu Jimi Technology Co Ltd
Current assignee: Chengdu Jimi Technology Co Ltd
Priority date: 2020-08-12
Filing date: 2020-08-12
Publication date: 2022-08-19
Anticipated expiration: 2040-08-12
Also published as: CN111935800A

Abstract

The application relates to the field of wireless communication, and discloses a system message changing method, terminal equipment and a storage medium under a multilink scene. The system message changing method under the multilink scene comprises the following steps: a first logic entity of the multilink terminal equipment sends a connection request message to a second logic entity of the network access equipment; the first logic entity receives a connection response message sent by the second logic entity, and the link connected with the first logic entity is indicated as a main link in the connection response message; and after the first logic entity is connected to the second logic entity, reading the broadcast message sent by the second logic entity on the main link, and determining whether the updated system message needs to be read or not according to the information in the broadcast message. The method and the device realize the system information synchronization of a plurality of links through the monitoring and the operation of a single link, save the power consumption of the terminal equipment, and simultaneously avoid the problem of data receiving and sending failure caused by using overdue wrong system information.

Description

System message changing method under multilink scene, terminal equipment and storage medium

Technical Field

The present application relates to the field of wireless communications, and in particular, to a method for changing system messages in a multilink scenario, a terminal device, and a storage medium.

Background

802.11be networks, also known as Extreme High Throughput (EHT) networks, are enhanced by a range of system features and a variety of mechanisms to achieve very High Throughput. As the use of Wireless Local Area Networks (WLANs) continues to grow, it becomes increasingly important to provide wireless data services in many environments, such as homes, businesses, and hot spots. In particular, video traffic will continue to be the dominant type of traffic in many WLAN deployments. With the advent of 4k and 8k video (uncompressed rates of 20 Gbps), the throughput requirements for these applications are constantly evolving. New high throughput, low latency applications such as virtual reality or augmented reality, gaming, remote offices and cloud computing will proliferate (e.g., latency for real-time gaming below 5 milliseconds).

In view of the high throughput and stringent real-time latency requirements of these applications, users expect higher throughput, higher reliability, less latency and jitter, and higher power efficiency when supporting their applications over a WLAN. Users desire improved integration with Time Sensitive Networks (TSNs) to support applications on heterogeneous ethernet and wireless LANs. 802.11be networks aim to ensure the competitiveness of WLANs by further increasing overall throughput and reducing latency, while ensuring backward compatibility and coexistence with legacy technology standards. 802.11 compatible devices operating in the 2.4GHz, 5GHz and 6GHz bands.

In the 802.11be network, in order to achieve the above-mentioned object, it is proposed that a plurality of data transmission links can be established between a terminal and an access point, and transmission is performed through the plurality of links simultaneously, so as to improve the transmission rate.

Disclosure of Invention

In a multilink scenario, in order to improve system throughput, a multilink terminal device may use multiple links to transmit data simultaneously, however, when there is no data to transmit, in order to save power consumption of the multilink terminal, the terminal device may not monitor the links when there is no data to transmit. However, when the multilink network access device changes the configuration information and transmits the changed message in the broadcast message, the terminal device cannot know the changed message, or the logic entity in the dormant state of the terminal device cannot know the updated system message because the logic entity does not monitor the link, so that when multilink data transmission is required again, expired error parameters are used, and data transmission fails.

In view of this, the present application provides a system message changing method, a terminal device and a storage medium in a multilink scenario.

In a first aspect, the present application provides a method for changing a system message in a multilink scenario, including: a first logic entity of the multilink terminal equipment sends a connection request message to a second logic entity of the network access equipment; the first logic entity receives a connection response message sent by the second logic entity, and the link connected with the first logic entity is indicated as a main link in the connection response message; and after the first logic entity is connected to the second logic entity, reading the broadcast message sent by the second logic entity on the main link, and determining whether the updated system message needs to be read or not according to the information in the broadcast message.

In a possible implementation manner, before sending the connection request message to the logic entity two, the logic entity one also reads a broadcast message sent by the logic entity two or receives a probe response message sent by the logic entity two, wherein the broadcast message and the probe response message contain a link identifier and a corresponding system message change sequence number; and after the first logic entity is connected to the second logic entity, the link identification and the corresponding system message change serial number in the broadcast message or the detection response message read before the connection request message is sent are locally stored.

In one possible implementation, determining whether the updated system message needs to be read according to the information in the broadcast message includes: reading a Link identifier in a broadcast message and a corresponding system message change serial number, comparing the read system message change serial number with a locally stored system message change serial number corresponding to a corresponding Link, and if the values of the read system message change serial number and the locally stored system message change serial number are different, sending a request message I to a logic entity II, wherein the request message I comprises a parameter Link List which is used for indicating the identifier of one or more links needing to acquire the system message; receiving a response message I sent by a logic entity II, wherein the response message I comprises a system message of a Link indicated by a Link identifier in a parameter Link List; and storing the requested system information of each link locally, and setting the system information change serial number of the link corresponding to the received updated system information as the system information change serial number corresponding to the link read in the broadcast information.

In a possible implementation manner, the broadcast message and the probe response message further include a parameter SITT, where the parameter SITT indicates a time when the updated system message is sent, and is used for indicating when the updated system message is to be sent; the logical entity will also save the parameter SITT as soon as it locally saves the link identification and the corresponding system message change sequence number.

In one possible implementation, determining whether the updated system message needs to be read according to the information in the broadcast message includes: reading a link identification in the broadcast message and a corresponding system message change serial number, comparing the read system message change serial number with a locally stored system message change serial number corresponding to a corresponding link, and if the values of the read system message change serial number and the locally stored system message change serial number are different, reading the system message on the link at a specified time according to a parameter SITT corresponding to the link identification; and storing the system messages received by each link locally, and setting the system message change sequence number of the link corresponding to the received updated system message as the system message change sequence number corresponding to the link read in the broadcast message.

In a possible implementation manner, the connection response message includes association identifiers allocated by the network access device to each logic entity in the multilink terminal device or association identifiers allocated to the multilink terminal device; the broadcast message contains a parameter AID bitmap, and the parameter AID bitmap is used for identifying a logic entity of the system message needing to be read in the multilink terminal equipment or the multilink terminal equipment needing to read the updated system message.

In one possible implementation, determining whether the updated system message needs to be read according to the information in the broadcast message includes: reading a parameter AID bitmap in the broadcast message, determining which logic entity in the multilink terminal equipment needs to read the updated system message, and then sending a request message II to a peer logic entity connected with the logic entity by the logic entity, wherein the request message II is used for requesting the system message, and then receiving the system message sent by the peer logic entity and storing the system message locally.

In a possible implementation, the broadcast message further includes a link identifier and a corresponding parameter SITT, where the parameter SITT indicates a time when the updated system message is sent, and is used to indicate when the updated system message will be sent.

In one possible implementation, determining whether the updated system message needs to be read according to the information in the broadcast message includes: reading the parameter AID bitmap in the broadcast message, determining which logic entity in the multilink terminal equipment needs to read the updated system message, and reading the system message on the link at the specified time by the logic entity according to the parameter SITT corresponding to the identifier of the link connected with the logic entity, and storing the system message locally.

In a possible implementation manner, the broadcast message further includes a parameter Link bitmap, and the parameter Link bitmap is used to indicate which Link needs to receive the updated system message.

In one possible implementation, determining whether the updated system message needs to be read according to the information in the broadcast message includes: reading a parameter AID bitmap in the broadcast message, determining whether the multilink terminal equipment needs to read the updated system message, if so, reading a parameter Link bitmap in the broadcast message, determining which Link the system message needs to read, sending a request message III to a peer logic entity connected with the Link by a logic entity on the Link, wherein the request message III is used for requesting the system message, then receiving the system message sent by the peer logic entity, and locally storing the system message.

In one possible implementation, determining whether the updated system message needs to be read according to the information in the broadcast message includes: reading a parameter AID bitmap in the broadcast message, determining whether the multilink terminal equipment needs to read the updated system message, if so, reading a parameter Link bitmap in the broadcast message, determining which Link the system message needs to read, reading the system message on the Link at the specified time according to a parameter SITT corresponding to the identifier of the Link, and storing the system message locally.

In one possible implementation, the determining which logical entity in the multi-link terminal device needs to read the updated system message includes: and checking whether the bit corresponding to the association identifier of each logic entity in the multilink terminal equipment in which the logic entity I in the parameter AID bitmap is positioned indicates that the updated system message needs to be read or not.

In one possible implementation, determining whether the updated system message needs to be read by the multi-link terminal device comprises: and checking whether a bit corresponding to the association identifier of the logic entity I in the parameter AID bitmap indicates that the updated system message needs to be read or not, or checking whether a bit corresponding to the association identifier of the multilink terminal equipment in the parameter AID bitmap indicates that the updated system message needs to be read or not.

In a second aspect, the present application provides a multi-link terminal device, comprising: the first logic entity is used for sending a connection request message to a second logic entity of the network access equipment; receiving a connection response message sent by the logic entity II, wherein the connection response message indicates that the link connected with the logic entity I is a main link; and after connecting to the second logic entity, reading the broadcast message sent by the second logic entity on the main link, and determining whether the updated system message needs to be read according to the information in the broadcast message.

In a third aspect, the present application provides a multi-link terminal device, comprising: a memory for storing a program; a processor, coupled to the memory, where the program, when executed by the processor, implements the method for changing system messages in a multilink scenario according to any one of the first aspect or possible implementations of the first aspect.

In a fourth aspect, the present application provides a computer-readable storage medium comprising computer instructions that, when executed on a terminal, implement the method for establishing a multilink connection according to the first aspect or any one of the possible implementations of the first aspect.

It should be noted that, in the present application, the multi-link terminal device according to the second aspect and the multi-link terminal device according to the third aspect and the computer-readable storage medium according to the fourth aspect are used for executing the method provided by the first aspect, so that the same beneficial effects as those of the method according to the first aspect can be achieved, and details of the embodiments of the present application are not repeated here.

The method and the device realize the system information synchronization of a plurality of links through the monitoring and the operation of a single link, save the power consumption of the terminal equipment, and simultaneously avoid the problem of data receiving and sending failure caused by using overdue wrong system information.

Drawings

The present application will now be described by way of example only and with reference to the accompanying drawings in which:

fig. 1 is a flowchart of a system message change method in a multilink scenario according to an embodiment of the present application;

fig. 2 is a flowchart of a system message change method in a multilink scenario according to an embodiment of the present disclosure;

fig. 3 is a flowchart of a system message changing method in a multilink scenario according to another specific embodiment of the present application.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application. Moreover, while the disclosure herein has been presented in terms of exemplary embodiment or embodiments, it is to be understood that each aspect of the disclosure can independently be implemented as a single unitary embodiment. The embodiments described below and the features of the embodiments can be combined with each other without conflict.

In the embodiments of the present application, the words "exemplary," "for example," and "such as" are used herein to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, the term using examples is intended to present concepts in a concrete fashion.

Unless defined otherwise, technical or scientific terms used herein shall have the ordinary meaning as understood by one of ordinary skill in the art to which this application belongs. The use of "first," "second," and similar terms in this application do not denote any order, quantity, or importance, but rather the description is used to distinguish one element from another. The word "comprising" or "comprises", and the like, means that the element or item listed before the word covers the element or item listed after the word and its equivalents, but does not exclude other elements or items. The term "and/or" includes any and all combinations of one or more of the associated listed items.

The technical solution in the present application will be described below with reference to the accompanying drawings.

In the following embodiments, the STA represents a logical entity of a multi-link terminal device, where the multi-link terminal device includes multiple logical entities, each logical entity performs data transmission through one link, and each logical entity includes an independent data transceiver module. A link is a wireless resource for transmitting data. The network access device also includes a plurality of logical entities.

The application is based on three links, namely link1, link2 and link3, but is not limited to the scenario in which two or more than three links are applied in the implementation process. It is assumed that the multi-link terminal device includes three logical entities STA1, STA2 and STA3, the network access device includes three logical entities AP1, AP2 and AP3, and STA1, STA2 and STA3 perform data transmission with AP1, AP2 and AP3 respectively, that is, AP1, AP2 and AP3 are peer logical entities of STA1, STA2 and STA3 respectively, and their corresponding operating links are link1, link2 and link3 respectively.

As shown in fig. 1, the method for changing system messages in a multilink scenario includes the following steps:

s11, the logic entity STA1 of the multilink terminal equipment sends a connection request message to the logic entity AP1 of the network access equipment.

S12.ap1 sends a connection response message to STA1, where the connection response message indicates that the link to which logical entity one is connected is the primary link.

S13.STA1 is connected to AP 1.

S14.AP1 sends broadcast message.

S15, the STA1 reads the broadcast message on the main link and determines whether the updated system message needs to be read according to the information in the broadcast message.

In some embodiments, the STA1 further reads the broadcast message sent by the AP1 or receives the probe response message sent by the AP1 before sending the connection request message, where the broadcast message and the probe response message include the link identifier and the corresponding system message change sequence number, and after the STA1 connects to the AP1, locally stores the link identifier and the corresponding system message change sequence number in the broadcast message or the probe response message read before sending the connection request message. In some other embodiments, the broadcast message and the probe response message further include a parameter SITT, where the parameter SITT indicates the time when the updated system message is sent and indicates when the updated system message will be sent.

In some embodiments, the connection response message includes association identifiers allocated by the network access device to each logical entity in the multi-link terminal device; the broadcast message contains a parameter AID bitmap, and the parameter AID bitmap is used for identifying a logic entity which needs to read the updated system message in the multilink terminal equipment or the multilink terminal equipment which needs to read the updated system message. In some embodiments, the broadcast message further includes a Link bitmap, where the Link bitmap is used to indicate which Link needs to receive the updated system message. In some embodiments, the broadcast message may also include a link identification and a corresponding parameter SITT.

The present application is further illustrated by the following specific examples.

As shown in fig. 2, the method for changing system messages in a multilink scenario includes the following steps: the STA1 reads the broadcast message sent by the AP1 or receives the probe response message sent by the AP1 on the link 1; STA1 sends a connection request message to AP1 on link 1; AP1 sends a connection response message to STA1 indicating that the link to which STA1 is connected is the primary link; STA1 connects to AP 1; the AP1 sends a broadcast message; STA1 reads the broadcast message on the main link and determines whether an updated system message needs to be read based on information in the broadcast message. The information contained in the broadcast messages is different and the method of determining whether updated system messages need to be read is different.

In some embodiments, the broadcast message and the probe response message include a link identification and a corresponding system message change sequence number. In this embodiment, the method for changing the system message in the multilink scenario includes the following steps:

s21, the logical entity STA1 of the multi-link terminal device reads, on the link1, a broadcast message (for example, a Beacon broadcast message, which is described below by taking the Beacon broadcast message as an example) sent by the logical entity AP1 of the network access device, or receives a probe response (probe response) message sent by the AP1, where the broadcast message or the probe response message includes a link identifier and a corresponding system message change sequence number, and for example, the link identifier and the corresponding system message change sequence number in the broadcast message or the probe response message are shown in table 1.

TABLE 1

Link ID	Change SN
		1	44
2	47
		3	32

S22.sta1 sends a connection request (Association request) message to the AP1 on link 1.

S23.ap1 sends an Association response (Association response) message to STA1 indicating that the link to which STA1 is connected is the primary link.

S24.sta1 is connected to the AP1 and locally stores the link identification and the corresponding system message change sequence number, which are illustratively shown in table 2.

TABLE 2

And S25, AP1 sends Beacon broadcast message, wherein the broadcast message comprises link identification and system message change sequence number. Illustratively, the link identification and corresponding system message change sequence number are shown in table 3.

TABLE 3

Link ID	Change SN
		1	45
2	48
		3	33

The Link ID represents the Link identifier, the Change SN represents the system message Change serial number, illustratively, the value range of the Change SN is set to 0-255, the initial value is 0, after each system message update, the value is incremented by 1, when the value is 255, after the system message update, the value is set to 0, and the process is repeated.

S26.STA1 reads the link identification and the corresponding system message change sequence number in the Beacon broadcast message on the main link, compares the read system message change sequence number with the system message change sequence number corresponding to the corresponding link stored locally, and if the two values are different, sends a request message (such as an ML SystemInfo request message, which is described below by taking the ML SystemInfo request message as an example) to the AP1, wherein the ML SystemInfo request message comprises the following parameters:

link List: indicating the identity of one or more links that need to acquire system messages.

And S27. after receiving the ML SystemInfo request message, the AP1 includes the system message of the indicated Link in the ML SystemInfo response message according to the Link identifier included in the Link List, and sends the ML SystemInfo response message to the STA 1.

S28.STA1 receives the ML SystemInfo response message, stores the system message of each requested link in local, and sets the system message change serial number of the link corresponding to the received updated system message as the system message change serial number corresponding to the link read in the Beacon broadcast message.

In some embodiments, the broadcast message and the probe response message include a link identifier, a corresponding system message change sequence number, and a parameter SITT indicating when the updated system message is to be sent and indicating when the updated system message will be sent. In this embodiment, the method for changing the system message in the multilink scenario includes the following steps:

s31, the STA1 reads the Beacon broadcast message of the AP1 on the link1, or receives the probe response message sent by the AP1, wherein the Beacon message or the probe response message contains the link identification, the corresponding system message change sequence number and the updated system message sending time SITT. Illustratively, the Beacon message or the probe response message includes the link identifier, the corresponding system message change sequence number, and the updated system message transmission time SITT as shown in table 4.

TABLE 4

Link ID	Change SN	SITT
			1	44	0ms
2	47	20ms
			3	32	30ms

S32.STA1 sends an Association request message to AP1 on link 1.

S33.ap1 sends an Association response message to STA1 indicating that the link to which STA1 is connected is the primary link.

S34.sta1 is connected to the AP1 and locally saves the link identification, the corresponding system message change sequence number and the parameters SITT. Illustratively, the link identification, the corresponding system message change sequence number, and the parameter SITT are shown in table 5.

TABLE 5

Link ID	Change SN	SITT
			1	44	0ms
2	47	20ms
			3	32	30ms

S35, AP1 sends Beacon broadcast message, wherein the broadcast message comprises: link identification, system message change sequence number, and updated system message send time SITT. Illustratively, the link identification, the system message change sequence number, and the updated system message transmission time SITT are shown in Table 6.

TABLE 6

Link ID	Change SN	SITT
			1	45	0ms
2	48	20ms
			3	33	30ms

Wherein Link ID represents the identity of the Link; change SN represents a system message Change sequence number, illustratively, the value range of Change SN is set to 0-255, the initial value is 0, after each system message is updated, the value is added with 1, when the value is 255, after the system message is updated, the value is set to 0, and the process is repeated; the SITT indicates the time of sending the updated system message, and is used to indicate when the updated system message will be sent, when the time of the SITT arrives, the AP on the corresponding link will send the Beacon frame, and the STA on the corresponding link will receive the Beacon frame at this time, and read the updated system message.

Illustratively, the SITT (time of updated system message transmission) may be set as follows:

1) the specific time is as follows: e.g., 2020/2/114: 25: 00;

2) offset value relative to Beacon receive time on current link: for example 20 ms;

3) listening for a period of broadcast messages.

S36.STA1 reads the link identification and the corresponding system message change serial number in the Beacon broadcast message on the main link, compares the read system message change serial number with the system message change serial number corresponding to the corresponding link stored locally, and reads the system message on the link at the specified time according to the parameter SITT corresponding to the link identification if the values of the two are different. In general, both the network access device and the multilink terminal device locally store the corresponding relationship between the Link ID and the STA address, and according to the corresponding relationship, the multilink terminal device can know which logical entity needs to read the system message.

S37, the STA1 stores the system messages received by each link locally, and sets the system message change serial number of the link corresponding to the received updated system message as the system message change serial number corresponding to the link read in the Beacon broadcast message.

As shown in fig. 3, the method for changing system messages in a multilink scenario includes the following steps: STA1 sends a connection request message to AP1 on link 1; the AP1 sends a connection response message to the STA1, where the connection response message includes Association Identifiers (AIDs) allocated by the AP1 to each logical entity of the multi-link terminal device, and indicates the link connected by the STA1 as a primary link; STA1 connects to AP 1; the AP1 sends a broadcast message; STA1 reads the broadcast message on the main link and determines whether an updated system message needs to be read based on information in the broadcast message. The AIDs allocated by the AP1 to the STAs in the same multi-link terminal device may be the same or different, and if the AIDs are the same, the AP1 may directly allocate the AIDs to the multi-link terminal device, for example, the AIDs allocated by the AP1 to the STAs 1, 2, and 3 of the multi-link terminal device may all be 5, as shown in table 7, or the AIDs of 5 may be directly allocated to the multi-link terminal device, as shown in table 8. If the information contained in the broadcast message is different, the method of determining whether the updated system message needs to be read is different.

TABLE 7

AID	address
		5	STA1 address
5	STA2 address
		5	STA3 address

TABLE 8

STA1 address, STA2address, and STA3 address respectively indicate addresses of logical entities STA1, STA2, and STA3, and STA MLD address indicates an address of a multi-link terminal device.

The system message changing method in the multilink scenario of the embodiment shown in fig. 3 is further described below, which includes the following steps:

s41, the logic entity STA1 of the multi-link terminal equipment sends an Association request message to the logic entity AP1 of the network access equipment on link 1.

S42, the AP1 sends an Association response message to the STA1, and assigns Association identifications AIDs to the various logical entities STA1, STA2 and STA3 of the multi-link terminal equipment, wherein the AIDs assigned to the same multi-link terminal equipment may be the same or different, and indicate that the link connected with the STA1 is the main link.

Exemplarily, when the AIDs are the same, the network access device needs to store a corresponding relationship between the AID, a Link ID and an STA address, where the Link ID represents an identifier of a Link and is used to identify different links running on the network access device, and the STA address represents an address of a logical entity, and sends the Link ID and the STA address corresponding relationship to the STA 1.

S43.sta1 is connected to the AP1, and reads the broadcast message according to the transmission period of the broadcast message or according to the listening interval time requested in the Association request.

S44.sta1 receives the SIM (System Information bitmap) in the broadcast message, illustratively, the SIM Information element structure is as shown in 9 or table 10.

TABLE 9

Element ID

Length

AID bitmap

Watch 10

Element ID

Length

AID bitmap

Link Bitmap

Element ID: a number indicating the information element;

length: indicating the length of the information element;

AID bitmap: the method is used for identifying the STA needing to read the updated system message in the multilink terminal equipment or the multilink terminal equipment needing to read the updated system message. In some embodiments, the AID bitmap is set in the following manner: when the indication STA needs to read the system message, setting the bit corresponding to the AID corresponding to the STA as '1', when the indication STA does not need to read the system message, setting the bit corresponding to the AID corresponding to the STA as '0', and if the AIDs allocated by the AP1 for the logic entities of the same multilink terminal device are the same, directly indicating whether the multilink terminal device needs to read the system message. For example, assuming that the number of logical entities included in all the multi-link terminal devices in the cell where the network access device is located is 16 in total, AIDs allocated by the AP1 to the STA1, the STA2, and the STA3 are 1, 2, and 3, respectively, and the setting of the AID bitmap is shown in table 11, it can be known from table 11 that the STA2 and the STA3 need to read system messages.

TABLE 11

0	1	1	0	0	0	0	0
								0	0	0	0	0	0	0	0

Link bitmap, when the same AID is allocated to the same multilink terminal device in step S42, the parameter is needed to indicate which Link needs to receive the updated system message. In some embodiments, the Link bitmap is set in the following manner: when the updated system message is required to be received on the indication link, the bit corresponding to the identifier of the link is set to be 1, and when the updated system message is not required to be received on the indication link, the bit corresponding to the identifier of the link is set to be 0. For example, assuming that the number of links over which the network access device can operate is 4, the Link bitmap is set as shown in table 12, and as can be seen from table 12, the Link2 and the Link3 need to receive updated system messages.

TABLE 12

0

1

0

S45, STA1 determines whether the updated system message needs to be read or not according to the received SIM information element. Illustratively, a method of determining whether an updated system message needs to be read includes:

if the AIDs of the STAs in the multilink terminal device where the STA1 is located are different, reading an AID bitmap parameter in an SIM information element, and determining which logical entity in the multilink terminal device needs to read an updated system message, for example, checking whether a bit corresponding to the AID of each STA in the multilink terminal device where the STA1 is located is "1", and if a bit value corresponding to which STA is "1", the STA sends a request message (such as a PS-POLL message, which is described below by taking the PS-POLL message as an example directly) to an AP connected to the STA, where the PS-POLL message is used for requesting the system message, and then receives the system message sent by the AP and stores the system message locally. Exemplarily, the AID bitmap is set as shown in table 11, the bit value corresponding to the AID of the STA1 is "0", and no operation is performed; the bit value corresponding to the AID of the STA2 is '1', the STA2 sends a PS-POLL message to the AP2 and then receives a system message sent by the AP 2; the bit value corresponding to the AID of STA3 is "1", STA3 sends a PS-POLL message to AP3, and then receives a system message sent by AP 3.

If the AIDs of the STAs in the multilink terminal device where the STA1 is located are the same, first, the AID bitmap parameter in the SIM information element is read, and it is determined whether the multilink terminal device needs to read the updated system message, e.g., it is checked whether the bit corresponding to the AID of the STA1 is "1", if the AP1 directly allocates the AID to the multilink terminal device, it is checked whether the bit corresponding to the AID of the multilink terminal device is "1", if so, the Link bitmap parameter in the SIM information element is read, it is determined which Link the system message needs to be read, the STA on the Link sends a PS-POLL message to the AP connected thereto, and the PS-POLL message is used for requesting the system message, and then the system message sent by the AP is received and locally stored.

In some embodiments, the broadcast message further includes a link identifier and a corresponding parameter SITT (an identifier of a link other than the currently connected link and its corresponding SITT), and for example, the link identifier and the corresponding parameter SITT in the broadcast message are shown in table 13. In this embodiment, the method of determining whether an updated system message needs to be read includes:

if the AIDs of the STAs in the multilink terminal device where the STA1 is located are different, reading the AID bitmap parameter in the SIM information element, and determining which logical entity in the multilink terminal device needs to read the updated system message, e.g., checking whether the bit corresponding to the AID of each STA in the multilink terminal device where the STA1 is located is "1", and if the bit corresponding to which STA is "1", reading the system message on the link at a specified time by the STA according to the parameter SITT corresponding to the identifier of the link to which the STA is connected, and storing the system message locally.

If the AIDs of all STAs in the multilink terminal equipment where the STA1 is located are the same, firstly reading AID bitmap parameters in an SIM information element, determining whether the multilink terminal equipment needs to read updated system messages, for example, checking whether a bit corresponding to the AID of the STA1 is '1', if the AID is directly distributed to the multilink terminal equipment by the AP1, checking whether a bit corresponding to the AID of the multilink terminal equipment is '1', if so, reading Link bitmap parameters in the SIM information element, determining which Link needs to read the system messages, and reading the system messages on the Link at the specified time according to a parameter SITT corresponding to the identification of the Link and storing the system messages locally.

Watch 13

Link ID	SITT
		2	20ms
3	30ms

And S46, after the AP receives the PS-POLL message of the STA and successfully sends a system message to the STA, setting the bit corresponding to the STA in the AID bitmap parameter as '0', or setting the bit corresponding to the STA in the AID bitmap parameter and the Link bitmap parameter as '0'.

The embodiment of the present application further provides a multilink terminal device, where the device is used to implement the method for changing the system message in the multilink scenario according to any one of embodiments in fig. 1 to 3, and the method may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions, for example, logical entities, and the like.

An embodiment of the present application further provides a multi-link terminal device, which includes a memory, and a processor, coupled to the memory, where the processor is configured to execute the program to implement the method according to any one of fig. 1 to 3.

The embodiment of the present application further provides a computer-readable storage medium, which includes computer instructions, and when the computer instructions are executed on a terminal, the method according to any one of the embodiments in fig. 1 to 3 is implemented.

It should be understood that, in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, some or all of the steps may be executed in parallel or executed sequentially, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, a network device or a terminal device, etc.) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: u disk, removable hard disk, ROM, RAM) magnetic disk or optical disk, etc. on which various types of program codes can be stored.

The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the examples of this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. The character "/" herein generally indicates that the former and latter associated objects are in an "or" relationship.

The word "if" or "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.

It will be understood by those skilled in the art that all or part of the steps in the method for implementing the above embodiments may be implemented by instructing the relevant hardware through a program, which may be stored in a storage medium readable by a device and includes all or part of the steps when executed, such as: FLASH, EEPROM, etc.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A system message change method under a multilink scene is characterized by comprising the following steps:

a first logic entity of the multilink terminal equipment reads a first broadcast message sent by a second logic entity of the network access equipment or receives a detection response message sent by the second logic entity of the network access equipment, wherein the first broadcast message and the detection response message contain a link identification and a corresponding system message change serial number;

the first logic entity sends a connection request message to a second logic entity;

the first logic entity receives a connection response message sent by the second logic entity, and the link connected with the first logic entity is indicated as a main link in the connection response message;

after the first logic entity is connected to the second logic entity, the link identification and the corresponding system message change sequence number are stored locally;

reading a second broadcast message sent by a logic entity II on a main link by the logic entity I, wherein the second broadcast message comprises a link identification and a corresponding system message change sequence number;

if the system message change serial number read from the second broadcast message is different from the system message change serial number corresponding to the corresponding Link stored locally, the first logic entity sends a first request message to the second logic entity, wherein the first request message contains a parameter Link List, and the parameter Link List is used for indicating the identification of one or more links needing to acquire the system message;

and the first logic entity receives a first response message sent by the second logic entity, wherein the first response message contains the system message of the link indicated by the link identifier in the parameter LinkList.

2.A system message change method under a multilink scene is characterized by comprising the following steps:

reading a second broadcast message sent by a logic entity II on a main link by the logic entity I, wherein the second broadcast message comprises a link identification, a corresponding system message change sequence number and updated system message sending time;

and if the system message change serial number read from the second broadcast message is different from the system message change serial number corresponding to the corresponding link stored locally, the multilink terminal equipment reads the system message on the corresponding link at the specified time according to the updated system message sending time corresponding to the link identification.

3.A system message change method under a multilink scene is characterized by comprising the following steps:

a first logic entity of the multilink terminal equipment sends a connection request message to a second logic entity of the network access equipment;

the first logic entity receives a connection response message sent by the second logic entity, the connection response message indicates that a link connected with the first logic entity is a main link and comprises an associated identifier distributed by the network access equipment for each logic entity in the multi-link terminal equipment or an associated identifier distributed for the multi-link terminal equipment;

and after the first logic entity is connected to the second logic entity, reading a broadcast message sent by the second logic entity on the main link, and determining whether to read the updated system message according to information in the broadcast message, wherein the broadcast message comprises a parameter AID bitmap, and the parameter AID bitmap is used for identifying the logic entity which needs to read the updated system message in the multilink terminal equipment or the multilink terminal equipment which needs to read the updated system message.

4. The method as claimed in claim 3, wherein determining whether the updated system message needs to be read according to the information in the broadcast message comprises:

reading a parameter AID bitmap in the broadcast message, determining a logic entity needing to read the updated system message in the multilink terminal equipment, sending a request message II to a peer-to-peer logic entity connected with the logic entity by the logic entity, wherein the request message II is used for requesting the system message, receiving the system message sent by the peer-to-peer logic entity, and storing the system message locally.

5. The method as claimed in claim 3, wherein the broadcast message further includes a link identifier and a time of sending the updated system message.

6. The method of claim 5, wherein determining whether the updated system message needs to be read according to the information in the broadcast message comprises:

reading a parameter AID bitmap in the broadcast message, determining a logic entity which needs to read the updated system message in the multilink terminal equipment, and reading the system message on a corresponding link at a specified time by the logic entity according to the time of sending the updated system message corresponding to the identifier of the link connected with the logic entity, and storing the system message locally.

7. The method for changing the system message under the multilink scene according to claim 3, wherein the broadcast message further comprises a parameter Link bitmap, and the parameter Link bitmap is used for indicating which links need to receive the updated system message.

8. The method of claim 7, wherein determining whether the updated system message needs to be read according to the information in the broadcast message comprises:

reading a parameter AID bitmap in a broadcast message, determining whether a multilink terminal device needs to read an updated system message, if so, reading a parameter Link bitmap in the broadcast message, determining a Link which needs to read the system message, and sending a request message III to a peer logic entity connected with the Link by a logic entity on the Link, wherein the request message is used for requesting the system message, and then receiving the system message sent by the peer logic entity and storing the system message locally.

9. The method as claimed in claim 7, wherein the broadcast message further includes a link id and a time of sending the corresponding updated system message.

10. The method of claim 9, wherein determining whether the updated system message needs to be read according to the information in the broadcast message comprises:

reading a parameter AID bitmap in the broadcast message, determining whether the multilink terminal equipment needs to read the updated system message, if so, reading a parameter Link bitmap in the broadcast message, determining a Link which needs to read the system message, reading the system message on a corresponding Link at a specified time according to the time of sending the updated system message corresponding to the identifier of the Link, and locally storing the system message.

11. The method as claimed in claim 4 or 6, wherein determining the logical entity of the multilink terminal device that needs to read the updated system message comprises:

and checking whether the bit corresponding to the association identifier of each logic entity in the multilink terminal equipment in which the logic entity I in the parameter AID bitmap is positioned indicates that the updated system message needs to be read or not.

12. The method as claimed in claim 8 or 10, wherein determining whether the updated system message needs to be read by the multi-link terminal device comprises:

checking whether the bit corresponding to the association identifier of the logic entity one in the parameter AID bitmap indicates that the updated system message needs to be read,

or, checking whether the bit corresponding to the association identifier of the multilink terminal device in the parameter AID bitmap indicates that the updated system message needs to be read.

13. A multi-link terminal device, comprising a first logical entity, wherein the first logical entity is configured to perform the following steps:

reading a first broadcast message sent by a logic entity II of the network access equipment or receiving a detection response message sent by the logic entity II of the network access equipment, wherein the first broadcast message and the detection response message contain a link identification and a corresponding system message change sequence number;

sending a connection request message to a second logic entity;

receiving a connection response message sent by the logic entity II, wherein the connection response message indicates that the link connected with the logic entity I is a main link;

after connecting to the second logic entity, locally storing the link identification and the corresponding system message change sequence number;

reading a second broadcast message sent by a second logic entity on a main link, wherein the second broadcast message comprises a link identification and a corresponding system message change sequence number;

if the system message change serial number read from the second broadcast message is different from the system message change serial number corresponding to the corresponding Link stored locally, sending a request message I to a logic entity II, wherein the request message I comprises a parameter Link List, and the parameter Link List is used for indicating the identification of one or more links needing to acquire the system message;

and receiving a response message I sent by the logic entity II, wherein the response message I contains the system message of the Link indicated by the Link identifier in the parameter Link List.

14.A multi-link terminal device, comprising a first logical entity, wherein the first logical entity is configured to perform the following steps:

sending a connection request message to a second logic entity of the network access equipment;

receiving a connection response message sent by a logic entity II, wherein the connection response message indicates that a link connected with the logic entity I is a main link and comprises an associated identifier distributed by network access equipment for each logic entity in the multi-link terminal equipment or an associated identifier distributed by the multi-link terminal equipment;

and after the multi-link terminal equipment is connected to the logic entity II, reading the broadcast message sent by the logic entity II on the main link, and determining whether the updated system message needs to be read or not according to the information in the broadcast message, wherein the broadcast message comprises a parameter AID bitmap which is used for identifying the logic entity which needs to read the updated system message in the multi-link terminal equipment or the multi-link terminal equipment which needs to read the updated system message.

15. A multi-link terminal device, comprising:

a memory for storing a program;

a processor coupled to the memory, wherein the program when executed by the processor implements the method for changing system messages in a multilink scenario according to any one of claims 1 to 12.

16. A computer-readable storage medium, comprising computer instructions which, when executed on a terminal, implement the system message change method in a multilink scenario according to any one of claims 1-12.