Method, apparatus and system for session reconstruction or sharing

By reconstructing or sharing a session only once between the session receiver and the session initiator, the signaling flow overhead caused by redundant handshake in the prior art is solved, and data transmission efficiency and system capacity are improved.

CN111416874BActive Publication Date: 2025-07-04TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202010255296.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-04-02
Publication Date
2025-07-04
Estimated Expiration
2040-04-02

AI Technical Summary

Technical Problem

In the prior art, there is a redundant handshake process during session reconstruction or sharing, resulting in large overhead of signaling flow and reducing data transmission time.

Method used

Reduce the number of handshakes by rebuilding or sharing a session by performing only one handshake between the session receiver and the session initiator, using session support for reconstruction or sharing indicators and session reconstruction parameters.

Benefits of technology

Reduces the number of handshakes in session reconstruction and sharing processes, saves signaling flow overhead, and improves data transmission efficiency and system capacity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN111416874B_ABST
    Figure CN111416874B_ABST
Patent Text Reader

Abstract

A method, apparatus, and system for session reconstruction are provided. The method includes: a session initiator determines that a session recipient supports the reconstruction of a predetermined session; the session initiator sends a session reconstruction request for reconstructing the predetermined session to the session recipient, where the predetermined session has been disconnected after being initially established with the session recipient; if the session recipient supports the reconstruction of the predetermined session, the session recipient sends an acknowledgement for the session reconstruction request to the session initiator; in response to receiving the acknowledgement for the session reconstruction request from the session recipient, the session initiator reconstructs the predetermined session with the session recipient according to the session reconstruction parameters of the predetermined session, and the session reconstruction parameters are determined based on the state parameters when the predetermined session is disconnected. Methods, apparatuses, and systems for session sharing are also provided.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of network communication technologies, and in particular, to methods, apparatuses, and systems for session reconstruction and methods, apparatuses, and systems for session sharing. Background Art

[0002] In network communication, it is necessary to establish a session on the link between a session initiator and a session recipient in order to transmit data. Generally speaking, according to the protocol followed, the establishment of a session requires multiple handshakes to determine whether both the session initiator and the session recipient support the establishment of the session and to negotiate various session parameters, etc. For example, in the IEEE 802.11 protocol defined by the Institute of Electrical and Electronics Engineers (IEEE), the establishment process of a BA (Block Ack) session is specified. According to this establishment process, for the establishment of any BA session, two handshake processes are required between the session initiator and the session recipient. Moreover, whether it is an initial establishment or a re - establishment, the same two handshake processes need to be completed, which undoubtedly requires a large overhead of signaling flow and reduces the time available for data transmission. Summary of the Invention

[0003] For a non - initial - establishment session, such as when reconstructing a session or sharing a session from one link to other links, since various parameters are basically the same as those in the initial establishment, the session establishment process with multiple handshakes may be redundant. In view of this, the present disclosure provides a method, apparatus, system, computing device, and storage medium for session reconstruction or sharing that can alleviate, mitigate, or even eliminate the above - mentioned problems.

[0004] According to a first aspect of the present disclosure, there is provided a method for session reconstruction. The method includes: determining that a session recipient supports the reconstruction of a predetermined session; sending a session reconstruction request for reconstructing the predetermined session to the session recipient, where the predetermined session has been disconnected after being initially established with the session recipient; and in response to receiving an acknowledgement of the session reconstruction request from the session recipient, reconstructing the predetermined session with the session recipient according to the session reconstruction parameters of the predetermined session, where the session reconstruction parameters of the predetermined session are determined based on the state parameters when the predetermined session was disconnected.

[0005] In some embodiments, determining that a session recipient supports the reconstruction of a predetermined session includes: determining that the session recipient supports the reconstruction of the predetermined session when the predetermined session is disconnected, which includes: receiving a session deletion frame from the session recipient, the session deletion frame being used to request deletion of the predetermined session to disconnect the predetermined session; in response to the session deletion frame including a session support reconstruction indicator, sending an acknowledgement for the session deletion frame to the session recipient to determine that the session recipient supports the reconstruction of the predetermined session while deleting the predetermined session.

[0006] In some embodiments, determining that a session recipient supports the reconstruction of a predetermined session includes: determining that the session recipient supports the reconstruction of the predetermined session when the predetermined session is disconnected, which includes: sending a session deletion frame to the session recipient, the session deletion frame including a session support reconstruction indicator and being used to request deletion of the predetermined session to disconnect the predetermined session; in response to receiving an acknowledgement of the session deletion frame from the session recipient, determining that the session recipient supports the reconstruction of the predetermined session while deleting the predetermined session.

[0007] In some embodiments, sending a session reconstruction request to the session recipient to reconstruct the predetermined session includes: sending a session reconstruction frame to the session recipient, the session reconstruction frame including a session identifier for the predetermined session.

[0008] In some embodiments, the session reconstruction frame further includes session reconstruction parameters of the predetermined session.

[0009] In some embodiments, determining that a session recipient supports the reconstruction of a predetermined session includes: determining that the session recipient supports the reconstruction of the predetermined session when the predetermined session is initially established, which includes: sending a first session request frame to the session recipient, where the first session request frame is used to request establishment of the predetermined session with the session recipient and includes a session support reconstruction indicator; receiving an acknowledgement of the first session request frame and a session response frame for the first session request frame from the session recipient; in response to determining that the session response frame includes a session support reconstruction indicator, sending an acknowledgement for the session response frame to the session recipient to determine that the session recipient supports the reconstruction of the predetermined session while establishing the predetermined session with the session recipient.

[0010] In some embodiments, sending a session reconstruction request to the session recipient to reconstruct the predetermined session includes: sending a second session request frame to the session recipient, the second session request frame including a session identifier for the predetermined session and a session support reconstruction indicator.

[0011] In some embodiments, the second session request frame further includes session reconstruction parameters of the predetermined session.

[0012] In some embodiments, the predetermined session has been disconnected after being initially established with the session recipient on a first link, and wherein, reconstructing the predetermined session with the session recipient according to the session reconstruction parameters of the predetermined session includes: reconstructing the predetermined session with the session recipient on one of a plurality of links according to the session reconstruction parameters of the predetermined session, wherein the plurality of links includes the first link.

[0013] According to a second aspect of the present disclosure, there is provided a method for session reconstruction. The method includes: receiving a session reconstruction request for reconstructing a predetermined session from a session initiator, wherein the predetermined session has been disconnected after being initially established with the session initiator; sending an acknowledgment for the session reconstruction request to the session initiator so as to reconstruct the predetermined session with the session initiator according to the session reconstruction parameters of the predetermined session, and the session reconstruction parameters of the predetermined session are determined based on state parameters when the predetermined session is disconnected.

[0014] In some embodiments, the method further includes: when the predetermined session is disconnected, acknowledging to the session initiator support for reconstructing the predetermined session, which includes: receiving a session deletion frame from the session initiator, the session deletion frame being used to request deletion of the predetermined session to disconnect the predetermined session; in response to the session deletion frame including a session support reconstruction indicator, sending an acknowledgment of the session deletion frame to the session initiator to acknowledge support for reconstructing the predetermined session to the session initiator while deleting the predetermined session.

[0015] In some embodiments, the method further includes: when the predetermined session is disconnected, acknowledging to the session initiator support for reconstructing the predetermined session, which includes: sending a session deletion frame to the session initiator, the session deletion frame being used to request deletion of the predetermined session to disconnect the predetermined session and including a session support reconstruction indicator to acknowledge support for reconstructing the predetermined session to the session initiator; in response to receiving an acknowledgment of the session deletion frame from the session initiator, deleting the predetermined session to disconnect the predetermined session.

[0016] In some embodiments, the receiving a session reconstruction request for reconstructing a predetermined session from a session initiator includes: receiving a session reconstruction frame from the session initiator, the session reconstruction frame including a session identifier for the predetermined session.

[0017] In some embodiments, the session reconstruction frame further includes the session reconstruction parameters of the predetermined session.

[0018] In some embodiments, the method further includes: when the predetermined session is initially established, confirming to the session initiator the support for the reconstruction of the predetermined session, which includes: receiving a first session request frame from the session initiator, where the first session request frame is used to request the establishment of the predetermined session with the session initiator; in response to the first session request frame including a session support reconstruction indicator, sending to the session initiator an acknowledgement of the first session request frame and a session response frame for the first session request frame, where the session response frame includes a session support reconstruction indicator to confirm to the session initiator the support for the reconstruction of the predetermined session; receiving an acknowledgement from the session initiator for the session response frame to establish the predetermined session with the session initiator.

[0019] In some embodiments, the receiving the session reconstruction request for reconstructing the predetermined session from the session initiator includes: receiving a second session request frame from the session initiator, where the second session request frame includes a session identifier for the predetermined session and a session support reconstruction indicator.

[0020] In some embodiments, the second session request frame further includes session reconstruction parameters for the predetermined session.

[0021] In some embodiments, after the predetermined session is initially established with the session initiator on a first link and then disconnected, where the sending to the session initiator an acknowledgement of the session reconstruction request to reconstruct the predetermined session with the session initiator according to the session reconstruction parameters of the predetermined session includes: sending to the session initiator an acknowledgement of the session reconstruction request to reconstruct the predetermined session with the session initiator on one of multiple links according to the session reconstruction parameters of the predetermined session, where the multiple links include the first link.

[0022] According to a third aspect of the present disclosure, there is provided a method for session sharing, including: sending a session sharing request for requesting to share a predetermined session to a session recipient, where the predetermined session has been established with the session recipient on a first link to enable data transmission with the session recipient; in response to receiving an acknowledgement from the session recipient for the session sharing request, sharing the predetermined session to at least one second link different from the first link, so that data transmission with the session recipient can be achieved on the first link and the at least one second link.

[0023] In some embodiments, the method further includes: determining that the session recipient supports sharing the predetermined session when the predetermined session is established with the session recipient on a first link, including: sending a first session request frame to the session recipient, where the first session request frame is used to request to establish the predetermined session with the session recipient and includes a session support sharing indicator; receiving an acknowledgement of the first session request frame from the session recipient and a session response frame for the first session request frame; in response to determining that the session response frame includes the session support sharing indicator, sending an acknowledgement for the session response frame to the session recipient to determine that the session recipient supports sharing the predetermined session while establishing the predetermined session with the session recipient.

[0024] In some embodiments, sending a session sharing request for requesting to share a predetermined session to the session recipient includes: sending a session sharing frame to the session recipient, where the session sharing frame includes a session identifier for the predetermined session.

[0025] In some embodiments, sending a session sharing request for requesting to share a predetermined session to the session recipient includes: sending a second session request frame to the session recipient, where the second session request frame includes a session identifier for the predetermined session and a session support sharing indicator.

[0026] According to a fourth aspect of the present disclosure, a method for session sharing is provided, including: receiving a session sharing request for requesting to share a predetermined session from a session initiator, where the predetermined session has been established with the session initiator on a first link to implement data transmission with the session initiator; sending an acknowledgement of the session sharing request to the session initiator to share the predetermined session to at least one second link different from the first link, so that data transmission can be implemented between the first link and the at least one second link with the session initiator.

[0027] In some embodiments, the method further includes: confirming to the session initiator that the predetermined session is supported for sharing when the predetermined session is established with the session initiator on a first link, including: receiving a first session request frame from the session initiator, where the first session request frame is used to request to establish the predetermined session with the session initiator; in response to the first session request frame including a session support sharing indicator, sending an acknowledgement of the first session request frame and a session response frame for the first session request frame to the session initiator, where the session response frame includes a session support sharing indicator to confirm to the session initiator that the predetermined session is supported for sharing; receiving an acknowledgement of the session response frame from the session initiator to establish the predetermined session with the session initiator on the first link.

[0028] In some embodiments, the session sharing request for receiving a request to share a predetermined session from a session initiator includes: receiving a session sharing frame from the session initiator, where the session sharing frame includes a session identifier for the predetermined session.

[0029] In some embodiments, the session sharing request for receiving a request to share a predetermined session from a session initiator includes: receiving a second session request frame from the session initiator, where the second session request frame includes a session identifier for the predetermined session and a session support sharing indicator.

[0030] According to a fifth aspect of the present disclosure, there is provided an apparatus for session reconstruction, including: a determination module configured to determine that a session recipient supports the reconstruction of a predetermined session; a request sending module configured to send a session reconstruction request for reconstructing the predetermined session to the session recipient, where the predetermined session has been disconnected after being initially established with the session recipient; a reconstruction module configured to, in response to receiving an acknowledgement of the session reconstruction request from the session recipient, reconstruct the predetermined session with the session recipient according to session reconstruction parameters of the predetermined session, where the session reconstruction parameters of the predetermined session are determined based on state parameters when the predetermined session was disconnected.

[0031] According to a sixth aspect of the present disclosure, there is provided an apparatus for session reconstruction, including: a receiving module configured to receive a session reconstruction request for reconstructing a predetermined session from a session initiator, where the predetermined session has been disconnected after being initially established with the session initiator; an acknowledgement sending module configured to send an acknowledgement of the session reconstruction request to the session initiator so as to reconstruct the predetermined session with the session initiator according to session reconstruction parameters of the predetermined session, where the session reconstruction parameters of the predetermined session are determined based on state parameters when the predetermined session was disconnected.

[0032] According to a seventh aspect of the present disclosure, there is provided an apparatus for session sharing, including: a request sending module configured to send a session sharing request for requesting to share a predetermined session to a session recipient, where the predetermined session has been established with the session recipient on a first link to enable data transmission with the session recipient; a sharing module configured to, in response to receiving an acknowledgement of the session sharing request from the session recipient, share the predetermined session to at least one second link different from the first link, such that data transmission with the session recipient can be achieved on the first link and the at least one second link.

[0033] According to an eighth aspect of the present disclosure, there is provided an apparatus for session sharing, including: a receiving module configured to receive a session sharing request for requesting to share a predetermined session from a session initiator, where the predetermined session has been established with the session initiator on a first link to implement data transmission with the session initiator; a confirmation sending module configured to send a confirmation of the session sharing request to the session initiator so as to share the predetermined session to at least one second link different from the first link, such that data transmission with the session initiator can be implemented on the first link and the at least one second link.

[0034] According to a ninth aspect of the present disclosure, there is provided a session reconstruction system, including the apparatus according to the fifth aspect of the present disclosure and the apparatus according to the sixth aspect of the present disclosure, where the apparatus according to the fifth aspect of the present disclosure is implemented as a session initiator, and the apparatus according to the sixth aspect of the present disclosure is implemented as a session receiver.

[0035] According to a tenth aspect of the present disclosure, there is provided a session sharing system, including the apparatus according to the seventh aspect of the present disclosure and the apparatus according to the eighth aspect of the present disclosure, where the apparatus according to the seventh aspect of the present disclosure is implemented as a session initiator, and the apparatus according to the eighth aspect of the present disclosure is implemented as a session receiver.

[0036] According to an eleventh aspect of the present disclosure, there is provided a computing device including a memory and a processor, the memory being configured to store computer-executable instructions thereon, and the computer-executable instructions, when executed on the processor, execute the method for session reconstruction and / or session sharing according to the foregoing aspects.

[0037] According to a twelfth aspect of the present disclosure, there is provided a computer-readable storage medium storing computer-executable instructions thereon, and the computer-executable instructions, when executed on a processor, execute the method for session reconstruction and / or session sharing according to the foregoing aspects.

[0038] A method for session reconstruction provided according to an embodiment of the present disclosure. After an initially established session is disconnected, the session initiator and the session recipient only need to perform one handshake (i.e., the session initiator sends a session reconstruction request to the session recipient, and the session recipient sends an acknowledgment of the session reconstruction request to the session initiator) to reconstruct the session. Similarly, through the method for session sharing provided according to an embodiment of the present disclosure, when the session initiator and the session recipient want to share a session established on one link to other links, they also only need to perform one handshake, that is, the session initiator sends a session sharing request to the session recipient, and the session recipient sends an acknowledgment of the session sharing request to the session initiator. Thus, the number of handshakes in the session reconstruction process and the session sharing process can be reduced, thereby saving the overhead of signaling flow, improving the efficiency of session reconstruction, increasing the time for data transmission, and improving the efficiency and capacity of the system.

[0039] According to the embodiments described hereinafter, these and other aspects of the present disclosure will be apparent and will be elucidated with reference to the embodiments described hereinafter. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In the following description of exemplary embodiments with reference to the accompanying drawings, more details, features, and advantages of the present disclosure are disclosed. In the drawings:

[0041] Figure 1 Schematically shows an example environment in which the method provided according to an embodiment of the present disclosure can be applied;

[0042] Figure 2 Schematically shows an example interaction diagram of a method for establishing and deleting a session in the related art;

[0043] Figure 3A and 3B Schematically shows an example flowchart of a method for session reconstruction according to an embodiment of the present disclosure;

[0044] Figure 3C Schematically shows some frame fields involved in an embodiment of the present disclosure;

[0045] Figure 4A and 4B Schematically shows an example interaction diagram of a method for session reconstruction according to an embodiment of the present disclosure;

[0046] Figure 5A and 5B Schematically shows an example flowchart of a method for session sharing according to an embodiment of the present disclosure;

[0047] Figure 5C Schematically shows some frame fields involved in an embodiment of the present disclosure;

[0048] Figure 6A and 6B schematically shows an example interaction diagram of a method for session sharing according to an embodiment of the present disclosure;

[0049] Figure 7 schematically shows an example block diagram of a device for session reconstruction according to an embodiment of the present disclosure;

[0050] Figure 8 schematically shows an example block diagram of another device for session reconstruction according to an embodiment of the present disclosure;

[0051] Figure 9 schematically shows an example block diagram of a device for session sharing according to an embodiment of the present disclosure;

[0052] Figure 10 schematically shows an example block diagram of another device for session sharing according to an embodiment of the present disclosure;

[0053] Figure 11 schematically shows an example block diagram of a computing device according to an embodiment of the present disclosure. Detailed Description of the Embodiments

[0054] Before introducing the embodiments of the present disclosure in detail, some related concepts are first explained:

[0055] 1. Session: The process of communication or data transmission between a session initiator and a session recipient, which is established through a signaling handshake between the session initiator and the session recipient, and can be disconnected due to being deleted or expired; 2. BA (Block Ack) session: A common session form in a WiFi network, where the session initiator continuously sends multiple data packets in blocks, and the session recipient does not perform one-to-one acknowledgments, but instead feedbacks a block acknowledgment message containing several acknowledgments based on the received information, thereby improving data transmission efficiency; in addition, the term ADDBA hereinafter is an abbreviation for Add Block Ack;

[0056] 3. MLD (Multi-link Device): A device that supports data transmission on multiple links simultaneously, and these multiple links can be in different frequency bands, for example;

[0057] 4. Session Reconstruction: When a session established between a pair of devices (session initiator and session receiver) is disconnected due to being deleted or expiring, etc., the process of re - establishing the session between this pair of devices is called session reconstruction. When at least one of the pair of devices is a multi - link device, the session can be reconstructed on the link where it was initially established, or can be reconstructed on a different link;

[0058] 5. Session Sharing: A session established on a certain link between a pair of multi - link devices (session initiator and session receiver) is shared to other links, so that the session is carried out or valid on at least two links simultaneously.

[0059] Figure 1 FIG. 100 schematically shows an example environment to which the session reconstruction method and / or session sharing method provided by embodiments of the present disclosure can be applied. Exemplarily, environment 100 includes four devices 110, 121, 122, 123. Device 110 is shown as a multi - link device serving as an access point (AP, Access Point) device, which includes two access points AP1 and AP2; devices 121 and 122 are shown as multi - link devices that are not access point devices, device 121 includes two stations STA1 and STA2 and device 122 includes two stations STAa and STAb; device 123 is shown as a single - link device, which includes a station 11beSTA that supports, for example, the 802.11be protocol. The connection lines between each station and the corresponding access point can represent the links between devices. Different access points or stations of the multi - link devices 110, 121, 122 can have different addresses, and independent sessions can be established between devices on different links as shown in the figure, such as establishing a BA session based on the 802.11 protocol.

[0060] It should be noted that Figure 1 the devices shown in FIG. 100 are merely illustrative and not restrictive. For example, device 110 can be a multi - link device serving as an access point device as shown in the figure, or can be other single - link devices. The multi - link devices and single - link devices can be various computing devices such as base station devices, routing and switching devices, etc. Similarly, devices 121, 122, 123 can be non - access point devices as shown in the figure, such as mobile phones, laptops, tablets, etc. that support communication on a single or multiple links, or can also be other access point devices that support communication on single - link or multi - link.

[0061] Next, taking Figure 2 as an example, the process of the method for establishing and deleting sessions in the related art will be described. Figure 2A flowchart of method 200 for establishing and deleting a BA session between a session initiator and a session receiver according to the 802.11 protocol is shown. Steps 201 to 204 show the process of establishing a BA session between the session initiator and the session receiver through a two-way handshake, and steps 205a, 205b and 206a, 206b show the process of deleting the established BA session.

[0062] In step 201, the session initiator sends an ADDBA Request Frame to the session receiver to request to establish a BA session with the session receiver. The ADDBA request frame includes the following fields:

[0063] Sequence number Information 1 Category 2 BlockAckAction 3 DialogToken 4 BlockAckParameterSet 5 BlockAckTimeoutValue 6 BlockAckStartingSequenceControl 7 GCR Group Address element (optional) 8 Multi-band (optional) 9 TCLAS (optional) 10 ADDBA Extension (optional)

[0064] Among them, the main fields include: Block Ack Action, which can have 256 values. Currently, only three BA operations are defined, that is, the ADDBA request, ADDBA response, and DELBA for requesting to establish a BA session, responding to the establishment of a BA session, and deleting a BA session are represented by the field values "0", "1", and "2" respectively. The remaining 253 field values are undefined. This field can distinguish the functions of different BA action frames; Block Ack Parameter Set, which includes the operating parameters required for the BA session, such as the TID corresponding to the BA session, the policy of the BA session, the recommended buffer size, etc. Among them, the TID can be regarded as the identifier of the session. Up to 16 BA sessions (TID = 0, 1,..., 15) can be established between a pair of devices; Block Ack Timeout Value defines the duration of the BA session; Block Ack Starting Sequence Control defines the starting sequence number of the data packets in the BA session.

[0065] In step 202, the session receiver sends an acknowledgement (ACK) for the ADDBA request frame to the session initiator.

[0066] In step 203, the session receiver sends an ADDBA Response Frame for the ADDBA request frame to the session initiator to respond to the request to establish a BA session. Specifically, the ADDBA response frame includes the following fields:

[0067]

[0068]

[0069] As shown above, the structure of the ADDBA response frame is similar to that of the above-mentioned ADDBA request frame, and also includes main fields such as block acknowledgment action (Block Ack Action), block acknowledgment parameter set (Block Ack Parameter Set), block acknowledgment timeout value (BlockAck Timeout Value), and also includes a status code (StatusCode) field indicating whether the session is successfully established. If this field is success (Success), it means that the session is successfully established. If it is rejected (Reject), it means that the session is not successfully established and the ADDBA request frame needs to be resent for another handshake.

[0070] In step 204, the session initiator sends an acknowledgment (ACK) for the ADDBA response frame to the session receiver. At this point, if the session receiver returns success to the session initiator in the ADDBA response frame, the BA session is successfully established. The successfully established BA session can be identified by the session initiator address, the session receiver address, and the TID. Furthermore, a BA session between a known pair of session initiators and session receivers can be identified by the TID, where the value of the TID can be between 0 and 15.

[0071] After the BA session is successfully established, data can be transmitted between the session initiator and the session receiver. During or after the data transmission process, either the session initiator or the session receiver can delete the current BA session by sending a DELBA frame, and the other party will send an acknowledgment (ACK) for the DELBA frame. Similarly, the DELBA frame includes fields such as Block Ack Action and Block Ack Parameter Set. Specifically, the DELBA frame includes the following fields:

[0072] Sequence number Information 1 Category 2 BlockAckAction 3 DELBA ParameterSet 4 Reason Code 5 BlockAckParameterSet 6 Multi-band (optional) 7 TCLAS (optional) .

[0073] Steps 205a and 206a show the process of deleting the current session by the session initiator. In step 205a, the session initiator sends a DELBA frame to the session receiver, and the DELBA frame includes the TID of the session to be deleted, so as to indicate to the session receiver to delete the session corresponding to the TID. Then, in step 206a, the session receiver sends an acknowledgment (ACK) for the DELBA frame to the session initiator, thereby deleting the corresponding session.

[0074] Optionally, steps 205b and 206b illustrate the process of deleting the current session by the session recipient. In step 205b, the session recipient sends a DELBA frame to the session initiator. The DELBA frame includes the TID of the session to be deleted, so as to indicate to the session initiator to delete the session corresponding to the TID. Then, in step 206b, the session initiator sends an acknowledgement (ACK) for the DELBA frame to the session recipient, thereby deleting the corresponding session.

[0075] It can be seen that according to the above process specified by the 802.11 protocol, any session needs to go through two handshakes to be successfully established. It should be noted that only the fields of the ADDBA request frame, ADDBA response frame, or DELBA frame involved in the description of the present disclosure are described above. The remaining fields not described have the same meaning as the corresponding fields defined in the 802.11 protocol and will not be elaborated here.

[0076] Figure 3A and Figure 3B respectively schematically show example flowcharts of methods 300A and 300B for session reconstruction according to embodiments of the present disclosure. As an example, method 300A can be executed at the session initiator, and method 300B can be correspondingly executed at the session recipient. As an example, either the session initiator or the session recipient described here can refer to various computing devices, such as mobile phones, laptops, tablets, base station devices, routing and switching devices, etc.

[0077] As Figure 3A shown, in step 311, it is determined that the session recipient supports the reconstruction of a predetermined session.

[0078] In some embodiments, it can be determined that the session recipient supports the reconstruction of a predetermined session when the predetermined session is disconnected. For example, it can be determined that the session recipient supports the reconstruction of a predetermined session during the session deletion in steps 205a, 206a or 205b, 206b as Figure 2 shown. When the session deletion is initiated by the session recipient, this determination can be completed through the following steps: receiving a session deletion frame from the session recipient, the session deletion frame being used to request the deletion of the predetermined session to disconnect the predetermined session; in response to the session deletion frame including a session support reconstruction indicator, sending an acknowledgement for the session deletion frame to the session recipient to determine that the session recipient supports the reconstruction of the predetermined session while deleting the predetermined session. When the session deletion is initiated by the session initiator, this determination can be completed through the following steps: sending a session deletion frame to the session recipient, the session deletion frame including a session support reconstruction indicator and being used to request the deletion of the predetermined session to disconnect the predetermined session; in response to receiving an acknowledgement from the session recipient for the session deletion frame, determining that the session recipient supports the reconstruction of the predetermined session while deleting the predetermined session.

[0079] Optionally, when the scheduled session is deleted, the session initiator and the session recipient may respectively store the state parameters when the session is disconnected, so as to subsequently determine the session reconstruction parameters required for reconstructing the session based on the stored state parameters. Alternatively, only the session initiator may store the state parameters when the session is disconnected, and when it subsequently requests to reconstruct the session, it may determine the session reconstruction parameters required for reconstructing the session based on the stored state parameters, and send the session reconstruction parameters to the session recipient, so as to reconstruct the session based on the session reconstruction parameters, which is not restrictive.

[0080] As an example, in an embodiment regarding a BA session, the session deletion frame sent may be the same as the one regarding Figure 2 The DELBA frames sent in the described steps 205a, 206a or 205b, 206b are similar. The difference is that in the session deletion frame, the reserved bit in the DELBA Parameter Set field of the DELBA frame is used to indicate the bit related to session reconstruction, and the bit related to session reconstruction can be set to indicate the above-mentioned session support reconstruction indicator. Figure 3C 331 in the figure shows a DELBA Parameter Set field, which includes Reserved, Initiator, and TID fields, and the reserved bits therein (bits B0 to B10 in the Reserved field, a total of 11 bits) are shown in a dotted box. Bits related to session reconstruction can be defined in such reserved bits, and the bits related to session reconstruction can be set to serve as a session support reconstruction indicator. In this way, when the session initiator intends to determine that the session receiver supports the reconstruction of the current BA session while deleting the current BA session, it can send a session deletion frame including a session support reconstruction indicator (i.e., a DELBA frame in which the bit related to session reconstruction is set (e.g., set to 1)) to the session receiver. When the session receiver receives such a session deletion frame, it can read the session support reconstruction indicator and indicate support for the reconstruction of the corresponding session by sending an acknowledgment (ACK) to the session initiator. Alternatively, similarly, the session receiver may send the above-mentioned session deletion frame (i.e., a DELBA frame in which the bit regarding session reconstruction is set (e.g., set to 1)) to indicate to the session initiator that it supports the reconstruction of the current BA session while deleting the current BA session.

[0081] In other embodiments, it may be determined when the scheduled session is initially established that the session recipient supports the reestablishment of the scheduled session. This is advantageous because it may support the reestablishment of the session after it is disconnected for any reason (e.g., due to session expiration). Figure 2In the session establishment steps 201 to 204 shown, it is determined that the session recipient supports the reconstruction of a predetermined session. This determination can be accomplished through the following steps: sending a first session request frame to the session recipient, where the first session request frame is used to request the establishment of a predetermined session with the session recipient and includes a session support reconstruction indicator; receiving an acknowledgment of the first session request frame and a session response frame for the first session request frame from the session recipient; in response to determining that the session response frame includes the session support reconstruction indicator, sending an acknowledgment for the session response frame to the session recipient to determine that the session recipient supports the reconstruction of the predetermined session while establishing a predetermined session with the session recipient.

[0082] As an example, in an embodiment regarding, for example, a BA session, the session request frame sent by the session initiator and the session response frame received from the session recipient are respectively similar to the ADDBA request frame and the ADDBA response frame in steps 201 to 204 described Figure 2 The difference is that in the session request frame and the session response frame, the reserved bits in the ADDBA Capabilities field in the ADDBA extension field of the ADDBA request frame and the ADDBA response frame are used to define the bits regarding session reconstruction, and such bits regarding session reconstruction can be set as the session support reconstruction indicator. Figure 3C 332 of shows the fields in the ADDBA Extension, which includes an Element ID, a Length, and an ADDBA Capabilities field, and the dashed box shows the reserved bits (bit B1 to bit B7, a total of 7 bits) in the ADDBA Capabilities field (including 8 bits). Thus, when the session initiator intends to determine that the session recipient supports the reconstruction of the BA session while initially establishing the BA session, it can send a session request frame including the session support reconstruction indicator (where the ADDBA request frame with the bits regarding session reconstruction set) to the session recipient. When the session recipient receives the session reconstruction frame, it can read the above session support reconstruction indicator and indicate support for the reconstruction of the corresponding session by sending an acknowledgment (ACK) to the session initiator and sending a corresponding session response frame (where the bits regarding session reconstruction are set (e.g., set to 1) ADDBA response frame).

[0083] In step 312, a session reconstruction request for reconstructing a predetermined session is sent to the session recipient, and the predetermined session has been disconnected after being initially established with the session recipient.

[0084] In an embodiment where it is determined that the session recipient supports the reconstruction of a scheduled session when the scheduled session is disconnected, step 312 may be completed through the following steps: sending a session reconstruction frame to the session recipient, the session reconstruction frame including a session identifier for the scheduled session. Optionally, the session reconstruction frame may further include session reconstruction parameters for the scheduled session, and the session reconstruction parameters may be determined based on state parameters when the scheduled session is disconnected. Specifically, the state parameters when the scheduled session is disconnected may be updated to update, for example, the starting sequence number of the data packets of the session or other appropriate parameters, so as to obtain the session reconstruction parameters. The state parameters of the session include any appropriate parameters characterizing the session. As an example, in a BA session, the state parameters may include the TID as described above, the policy of the BA session, the starting sequence number of the data packets in the BA session, and so on. Optionally, the session reconstruction parameters may be the same as the state parameters when the scheduled session is disconnected.

[0085] As an example, the session reconstruction frame may be customized. For example, in an embodiment regarding, for example, a BA session, the frame format of the session reconstruction frame may be similar to the frame format of an ADDBA request frame. For example, the existing Block Ack Action field may be expanded. Based on the existing ADDBA request frame, ADDBA response frame, and DELBA frame, a field value of "3" is used to indicate a session reconstruction (ADDBA resume) frame for reconstructing the BA session. The expanded Block Ack Action field may be as shown in the following table:

[0086]

[0087] In this way, when the session initiator intends to reconstruct a BA session (it has been determined that the session recipient supports the reconstruction of the BA session), it may send a session reconstruction frame with the Block Ack Action field value set to 3 to the session recipient to reconstruct the BA session. To indicate which session is intended to be reconstructed, the session reconstruction frame needs to include the session identifier (TID) of the session intended to be reconstructed. Additionally, optionally, the session reconstruction frame may include the starting sequence number of the data packets in the BA session intended to be reconstructed to specify where to resume data transmission. Alternatively, in the case where the session recipient does not store the state parameters of the session, the session reconstruction frame may include the state parameters of the BA session intended to be reconstructed. Alternatively, in the case where the session recipient stores the state parameters, the session reconstruction frame may include the state parameters of the session that need to be changed, and the session recipient may update the state parameters when the session is disconnected based on the state parameters of the session that need to be changed, so as to obtain the session reconstruction parameters.

[0088] Alternatively, in an embodiment where it is determined that the session recipient supports the reconstruction of a predetermined session when the predetermined session is initially established, step 312 may be completed by the following steps: sending a second session request frame to the session recipient, the second session request frame including a session identifier for the predetermined session and a session support reconstruction indicator. Optionally, the second session request frame may include session reconstruction parameters for the predetermined session.

[0089] As an example, in an embodiment regarding, for example, a BA session, the session initiator may send the same session request frame as described above when the session was initially established, that is, an ADDBA request frame in which the bit regarding session reconstruction is set. To identify the session to be reconstructed, the session request frame should include the session identifier (TID) of the corresponding BA session. When the session recipient receives the session request frame, if it reads that it is for the same session as the previous session request frame, it may default to restarting the BA session without sending a session response frame again. Similar to the session reconstruction frame in the foregoing embodiment, the session request frame may also include status parameters when the corresponding BA session was disconnected or status parameters that need to be changed, etc.

[0090] In step 313, in response to receiving an acknowledgment of the session reconstruction request from the session recipient, reconstruct the predetermined session with the session recipient according to the session reconstruction parameters of the predetermined session, the session reconstruction parameters of the predetermined session being determined based on the status parameters when the predetermined session was disconnected.

[0091] In some embodiments, one or both of the session initiator and the session recipient may be single-link devices, such as Figure 1 the device 123 shown. In this case, there is only one link between the session initiator and the session recipient, so both the initial establishment and reconstruction of the session are performed on this link. In other embodiments, both the session initiator and the session recipient may be multi-link devices, such as Figure 1 the devices 110, 121, 122 shown. In this case, there may be multiple links between the session initiator and the session recipient. Assuming that a predetermined session was initially established with the session recipient on the first link and has been disconnected, the session initiator may reconstruct the predetermined session with the session recipient on any of the multiple links, that is, it may reconstruct the predetermined session on the first link or on another link different from the first link. For example, if a certain session between devices 110 and 121 was initially established on the link between AP1 and STA1, then when this session is reconstructed after being deleted, it may be reconstructed on the link between AP1 and STA1 or on the link between AP2 and STA2.

[0092] In addition, it should be noted that when the reconstructed session is disconnected, it can also be reconstructed again according to the method described above. It should also be understood that although the embodiments of the present disclosure are described in detail through specific examples of BA sessions, in fact, the embodiments of the present disclosure can be similarly applied to other types of or sessions based on other protocols.

[0093] According to the method for session reconstruction provided by an embodiment of the present disclosure, after determining that the session recipient supports the reconstruction of a predetermined session, the session initiator only needs to perform a handshake with the session recipient once (that is, the session initiator sends a session reconstruction request to the session recipient, and the session recipient sends an acknowledgment of the session reconstruction request to the session initiator), and then the session can be reconstructed. In addition, the session initiator can determine that the session recipient supports the reconstruction of a predetermined session when the session with the session recipient is initially established or disconnected. Thereby, the number of handshakes in the session reconstruction process can be reduced, thus saving the overhead of signaling flow, improving the efficiency of session reconstruction, increasing the time for data transmission, and improving the efficiency and capacity of data transmission. Especially in the case of multi-link devices, for example, since independent sessions will be initiated on different sites of the same MLD, the same session establishment process will be repeated multiple times on each link, resulting in a large amount of resource overhead. By adopting the technical solution of the present disclosure, more signaling flow overhead can be saved, the time for data transmission can be greatly increased, and the efficiency and capacity of data transmission can be improved.

[0094] The following Figure 3B Briefly describe the method 300B for session reconstruction executed at the session recipient. It should be understood that various features described based on method 300A also apply to method 300B. To avoid redundancy, some of these features are omitted here. Moreover, method 300B has a similar technical effect to method 300A.

[0095] In step 321, receive a session reconstruction request for reconstructing a predetermined session from the session initiator, where the predetermined session has been disconnected after being initially established with the session initiator.

[0096] In some embodiments, when a scheduled session is disconnected, the session initiator may be confirmed that the reconstruction of the scheduled session is supported. As an example, the disconnection of the scheduled session is achieved by deleting the scheduled session. The deletion of the session may be initiated by the session initiator, which may be achieved through the following steps: receiving a session deletion frame from the session initiator, the session deletion frame being used to request the deletion of the scheduled session to disconnect the scheduled session; in response to the session deletion frame including a session support reconstruction indicator, sending an acknowledgement of the session deletion frame to the session initiator to confirm the support for the reconstruction of the scheduled session while deleting the scheduled session. Alternatively, the deletion of the session may be initiated by the session recipient, which may be achieved through the following steps: sending a session deletion frame to the session initiator, the session deletion frame being used to request the deletion of the scheduled session to disconnect the scheduled session and including a session support reconstruction indicator to confirm to the session initiator the support for the reconstruction of the scheduled session; in response to receiving an acknowledgement of the session deletion frame from the session initiator, deleting the scheduled session to disconnect the scheduled session.

[0097] In other embodiments, when a scheduled session is initially established, the session initiator may be confirmed that the reconstruction of the scheduled session is supported. This is advantageous because it can support the reconstruction of the session after it is disconnected for any reason (e.g., the session is disconnected due to session expiration). This may be achieved through the following steps: receiving a first session request frame from the session initiator, where the first session request frame is used to request the establishment of a scheduled session with the session initiator; in response to the first session request frame including a session support reconstruction indicator, sending an acknowledgement of the first session request frame and a session response frame for the first session request frame to the session initiator, where the session response frame includes a session support reconstruction indicator to confirm to the session initiator the support for the reconstruction of the scheduled session; receiving an acknowledgement of the session response frame from the session initiator to establish a scheduled session with the session initiator.

[0098] In step 322, send an acknowledgement of the session reconstruction request to the session initiator to reconstruct the scheduled session with the session initiator according to the session reconstruction parameters of the scheduled session, where the session reconstruction parameters of the scheduled session are determined based on the state parameters when the scheduled session is disconnected.

[0099] In the embodiment where the support for the reconstruction of the scheduled session is confirmed to the session initiator when the scheduled session is disconnected, the session recipient may receive a session reconstruction frame from the session initiator as a session reconstruction request, and the session reconstruction frame includes a session identifier for the scheduled session. Optionally, the session reconstruction frame may include the session reconstruction parameters of the scheduled session.

[0100] In an embodiment where the support for the reconstruction of a scheduled session is confirmed to the session initiator when the scheduled session is initially established, the session recipient may receive a second session request frame from the session initiator as a session reconstruction request. The second session request frame includes a session identifier for the scheduled session and a session support reconstruction indicator. Optionally, the second session request frame may include session reconstruction parameters for the scheduled session. By sending the second session request frame to the session recipient to initiate session reconstruction, this avoids the need to separately design a session reconstruction frame and saves resources.

[0101] In addition, assuming that the scheduled session has been disconnected after being initially established with the session initiator on a first link, an acknowledgment for the session reconstruction request may be sent to the session initiator so as to reconstruct the scheduled session with the session initiator on one of multiple links according to the session reconstruction parameters of the scheduled session. The multiple links include the first link.

[0102] Figure 4A The session reconstruction process 400A in the case of determining the support for reconstructing a scheduled session when the scheduled session is disconnected is shown in the form of an interaction diagram. In steps 411 to 414, the scheduled session is initially established through a two - handshake process between the session initiator and the session recipient, which is similar to steps 201 to 204 described with respect to Figure 2 In step 415a, the session initiator sends a session deletion frame to the session recipient. The session deletion frame includes a session support reconstruction indicator and is used to request the deletion of the scheduled session to disconnect the scheduled session. In step 416a, the session initiator receives an acknowledgment of the session deletion frame sent by the session recipient, and determines that the session recipient supports the reconstruction of the scheduled session while deleting the scheduled session. Optionally, as described above, the deletion of the scheduled session may be initiated by the session recipient. In step 415b, the session recipient sends a session deletion frame to the session initiator. The session deletion frame is used to request the deletion of the scheduled session to disconnect the scheduled session and includes a session support reconstruction indicator to confirm to the session initiator the support for the reconstruction of the scheduled session. In step 416b, the session recipient receives an acknowledgment for the session deletion frame sent by the session initiator to delete the scheduled session to disconnect the scheduled session. In step 417, the session initiator sends a session reconstruction frame to reconstruct the scheduled session to the session recipient. In step 418, the session initiator receives an acknowledgment of the session reconstruction request sent by the session recipient, and reconstructs the scheduled session between the session initiator and the session recipient according to the session reconstruction parameters of the scheduled session. The specific descriptions of the above steps refer to the content above with respect to Figure 3A - 3C and will not be repeated here.

[0103] Figure 4BThe session reconstruction process 400B in the case of determining support for reconstructing a predetermined session when the predetermined session is initially established is shown in the form of an interaction diagram. In steps 421 to 424, the predetermined session is initially established while it is determined that the session recipient supports the reconstruction of the predetermined session. In step 421, the session initiator sends a first session request frame to the session recipient, where the first session request frame is used to request the establishment of the predetermined session with the session recipient and includes a session support reconstruction indicator. The session recipient sends an acknowledgment of the first session request frame to the session initiator in step 422 and a session response frame for the first session request frame to the session initiator in step 423. In step 424, when the session initiator determines that the session response frame includes the session support reconstruction indicator, the session initiator sends an acknowledgment for the session response frame to the session recipient, so as to determine that the session recipient supports the reconstruction of the predetermined session while establishing the predetermined session between the session initiator and the session recipient. Steps 425a and 426a show the deletion of the predetermined session initiated by the session initiator; optionally, steps 425b and 426b show the deletion of the predetermined session initiated by the session recipient. In step 427, the session initiator sends a second session request frame to the session recipient, and the second session request frame includes a session identifier for the predetermined session and a session support reconstruction indicator. In step 428, the session initiator receives an acknowledgment of the second session request frame from the session recipient and reconstructs the predetermined session with the session recipient according to the session reconstruction parameters of the predetermined session. The processes of steps 425a and 426a and 425b and 426b are similar to steps 205a and 206a and 205b and 206b described with respect to Figure 2 The specific descriptions of the other steps refer to the above content with respect to Figure 3A - 3C and will not be repeated here.

[0104] Figure 5A and Figure 5B respectively schematically show example flowcharts of methods 500A and 500B for session sharing according to embodiments of the present disclosure. As an example, method 500A can be executed at the session initiator, and method 500B can be correspondingly executed at the session recipient. As an example, any one of the session initiator and the session recipient described here can refer to various computing devices, such as mobile phones, laptops, tablets, base station devices, routing and switching devices, etc.

[0105] As Figure 5A shown, in step 511, a session sharing request for requesting to share a predetermined session is sent to the session recipient, where the predetermined session has been established with the session recipient on a first link to achieve data transmission with the session recipient.

[0106] In some embodiments, step 511 is completed through the following steps: sending a session sharing frame to the session recipient, where the session sharing frame includes a session identifier for a predetermined session.

[0107] As an example, the session sharing frame can be customized. For example, in an embodiment regarding, for example, a BA session, the frame format of the session sharing frame can be similar to the frame format of an ADDBA request frame. For example, the existing BlockAck Action field can be expanded. Based on the existing ADDBA request frame, ADDBA response frame, and DELBA frame, a field value of "4" is used to represent a session sharing (ADDBA share) frame for sharing a BA session. The expanded Block Ack Action field can be as shown in the following table (assuming ADDBA resume is also expanded, but ADDBA share can also be expanded alone):

[0108] BlockAckAction Meaning 0 ADDBA request 1 ADDBA response 2 DELBA 3 ADDBA resume 4 ADDBA share 5-255 Reserved

[0109] In this way, when the session initiator intends to share a BA session on different links, it can send a session sharing frame with the Block AckAction field value set to 4 to the session recipient to achieve the sharing of the BA session. Similarly, the session sharing frame can include the session identifier (TID) of the session intended to be shared to indicate which session is intended to be shared. And, optionally, the session sharing frame can include the starting sequence number of the data packets in the BA session intended to be shared to start transmitting data packets on different links from that sequence number.

[0110] In some other embodiments, before step 511, it can be determined that the session recipient supports sharing the predetermined session when the predetermined session is established with the session recipient on the first link. This can include: sending a first session request frame to the session recipient, where the first session request frame is used to request to establish a predetermined session with the session recipient and includes a session support sharing indicator; receiving an acknowledgment of the first session request frame and a session response frame for the first session request frame from the session recipient; in response to determining that the session response frame includes the session support sharing indicator, sending an acknowledgment for the session response frame to the session recipient to determine that the session recipient supports sharing the predetermined session while establishing the predetermined session with the session recipient. In this case, step 511 can be completed through the following steps: sending a second session request frame to the session recipient, where the second session request frame includes a session identifier for the predetermined session and a session support sharing indicator.

[0111] As an example, in an embodiment regarding, for example, a BA session, it can be similar to regardingFigure 3A and 3C As described in 3C , in the session request frame and the session response frame, the reserved bits in the ADDBA Capabilities field in the ADDBA Extension field in the ADDBA request frame and the ADDBA response frame are used to define the shared bits regarding the session, and such shared bits regarding the session can be set as the session support sharing indicator. Figure 5C FIG. schematically shows the ADDBA Capabilities field. As shown by the dashed box in the figure, bits B1 and B2 of the ADDBA Capabilities field are respectively defined as the bits regarding session reconstruction (BA Fast resume) and the bits regarding session sharing (BA share). However, it should be understood that BA share can be defined separately when BA Fast resume is not defined. In this way, when the session initiator intends to determine whether the session recipient supports the sharing of the BA session while initially establishing the BA session, it can send a session request frame (an ADDBA request frame in which the bits regarding session sharing are set (e.g., set to 1)) to the session recipient. When the session recipient receives such a session request frame, it can read the session support sharing indicator and indicate support for the sharing of the corresponding session by sending an acknowledgment (ACK) to the session initiator and sending a corresponding session response frame (an ADDBA response frame in which the bits regarding session sharing are set (e.g., set to 1)).

[0112] In such an embodiment, during the existence (i.e., not disconnected) of the BA session, the session initiator can send the same session request frame as when the session was initially established, in which the bits regarding session sharing are set (e.g., set to 1). Similarly, the session request frame can include the session identifier (TID) of the session intended to be shared. When the session recipient receives the session request frame, if it reads that the TID therein is the same as the TID of the session determined to support sharing during the initial establishment, it can default to sharing the BA session without sending a session response frame again. In addition, the session request frame can also include the starting sequence number of the data packets in the BA session intended to be shared, so as to start transmitting the data packets on different links from that sequence number.

[0113] By determining that the session recipient supports sharing the predetermined session when the predetermined session is established with the session recipient on the first link, and by sending a second session request frame to the session recipient to initiate session sharing, this avoids the need to separately design a session sharing frame and saves resources.

[0114] In step 512, in response to receiving an acknowledgement of the session sharing request from the session recipient, the predetermined session is shared to at least one second link different from the first link, so that data transmission with the session recipient can be achieved on the first link and the at least one second link.

[0115] Exemplarily, in Figure 1 the illustrated system, if a certain session between device 110 and device 122 is initially established on the link between AP1 and STAa, it can be shared to the link between AP2 and STAb through the above method, so as to perform data transmission of the corresponding session on these two links simultaneously. However, it should be understood that the session can actually be shared on more links, not limited to the two links in the example.

[0116] For the method for session sharing provided according to an embodiment of the present disclosure, when the session initiator and the session recipient want to share the session established on one link to other links, only one handshake is required, that is, the session initiator sends a session sharing request to the session recipient, and the session recipient sends an acknowledgement of the session sharing request to the session initiator. Thus, the number of handshakes in the session sharing (i.e., establishment) process can be reduced, thereby saving the overhead of the signaling flow, improving the efficiency of session establishment, increasing the time for data transmission, and improving the efficiency and capacity of the system.

[0117] Next, in combination with Figure 5B Method 500B for session sharing executed at the session recipient is briefly described. It should be understood that various features described based on Method 500A also apply to Method 500B, and some of these features are omitted here to avoid redundancy. Moreover, Method 500B has a similar technical effect to Method 500A.

[0118] In step 521, a session sharing request for requesting to share a predetermined session is received from the session initiator, where the predetermined session has been established with the session initiator on the first link to achieve data transmission with the session initiator.

[0119] In some embodiments, step 521 can be completed through the following steps: receiving a session sharing frame from the session initiator, where the session sharing frame includes a session identifier for the predetermined session.

[0120] In some other embodiments, before step 521, when a predetermined session is established with a session initiator on a first link, the session initiator may be confirmed to support sharing the predetermined session. This may include: receiving a first session request frame from the session initiator, where the first session request frame is used to request the establishment of a predetermined session with the session initiator; in response to the first session request frame including a session support sharing indicator, sending an acknowledgment of the first session request frame and a session response frame for the first session request frame to the session initiator, where the session response frame includes the session support sharing indicator to confirm to the session initiator the support for sharing the predetermined session; receiving an acknowledgment of the session response frame from the session initiator to establish the predetermined session with the session initiator on the first link. In such an embodiment, step 521 may be completed by the following steps: receiving a second session request frame from the session initiator, where the second session request frame includes a session identifier for the predetermined session and a session support sharing indicator.

[0121] In step 522, send an acknowledgment of the session sharing request to the session initiator to share the predetermined session to at least one second link different from the first link, so as to enable data transmission between the session initiator and the session initiator on the first link and the at least one second link.

[0122] Figure 6A Method 600A for session sharing is shown in the form of an interaction diagram. In steps 611 to 614, a predetermined session is initially established, and the process is similar to steps 201 to 204 described with respect to Figure 2 In step 615, the session initiator sends a session sharing frame requesting to share the predetermined session to the session recipient, where the session sharing frame includes a session identifier for the predetermined session, and the predetermined session has been established with the session recipient on the first link to enable data transmission with the session recipient. In step 616, after the session initiator receives an acknowledgment of the session sharing frame sent by the session recipient, the session initiator and the session recipient share the predetermined session to at least one second link different from the first link, enabling data transmission between the two on the first link and the at least one second link.

[0123] Figure 6BMethod 600B for session sharing is shown in the form of an interaction diagram, where it is determined that sharing of a predetermined session is supported when the predetermined session is initially established. At step 621, the session initiator sends a first session request frame to the session recipient, where the first session request frame is used to request establishment of the predetermined session with the session recipient and includes a session support sharing indicator. The session recipient sends an acknowledgement of the first session request frame to the session initiator at step 622 and a session response frame for the first session request frame to the session initiator at step 623. At step 624, the session initiator sends an acknowledgement of the session response frame to the session recipient to determine that the session recipient supports sharing the predetermined session while establishing the predetermined session with the session recipient. At 625, the session initiator sends a second session request frame to the session recipient, and the second session request frame includes a session identifier for the predetermined session and a session support sharing indicator. At step 626, the session recipient sends an acknowledgement of the second session request frame to the session initiator to enable the session initiator and the session recipient to share the predetermined session to at least one second link different from the first link.

[0124] Figure 7 An example block diagram of an apparatus 700 for session reconstruction according to an embodiment of the present disclosure is schematically shown. The apparatus 700 may include a determination module 710, a request sending module 720, and a reconstruction module 730. The determination module 710 is configured to determine that a session recipient supports reconstruction of a predetermined session. The request sending module 720 is configured to send a session reconstruction request for reconstructing the predetermined session to the session recipient, where the predetermined session has been disconnected after being initially established with the session recipient. The reconstruction module 730 is configured to, in response to receiving an acknowledgement of the session reconstruction request from the session recipient, reconstruct the predetermined session with the session recipient according to the session reconstruction parameters of the predetermined session, and the session reconstruction parameters of the predetermined session are determined based on the state parameters when the predetermined session was disconnected.

[0125] Figure 8 An example block diagram of another apparatus 800 for session reconstruction according to an embodiment of the present disclosure is schematically shown. The apparatus 800 may include a receiving module 810 and an acknowledgement sending module 820. The receiving module 810 is configured to receive a session reconstruction request for reconstructing a predetermined session from a session initiator, where the predetermined session has been disconnected after being initially established with the session initiator. The acknowledgement sending module 820 is configured to send an acknowledgement of the session reconstruction request to the session initiator to reconstruct the predetermined session with the session initiator according to the session reconstruction parameters of the predetermined session, and the session reconstruction parameters of the predetermined session are determined based on the state parameters when the predetermined session was disconnected.

[0126] It should be understood that Figure 7The device shown can be implemented as a session initiator. Figure 8 The device shown can be implemented as a session recipient, thus constituting a system for session reconstruction. The session initiator and the session recipient can interact according to the Figure 4A or Figure 4B described process to achieve session reconstruction. As an example, in the environment described in reference Figure 1 Device 110 can be a session recipient, and any one of devices 121, 122, and 123 can be a session initiator. The session established therebetween can be reconstructed on the same or different links according to the foregoing method.

[0127] Figure 9 FIG. schematically shows an example block diagram of a device 900 for session sharing according to an embodiment of the present disclosure. The device 900 may include a request sending module 910 and a sharing module 920. The request sending module 910 is configured to send a session sharing request for requesting to share a predetermined session to a session recipient, where the predetermined session has been established with the session recipient on a first link to achieve data transmission with the session recipient. The sharing module 920 is configured to, in response to receiving an acknowledgment of the session sharing request from the session recipient, share the predetermined session to at least one second link different from the first link, so that data transmission can be achieved between the first link and the at least one second link with the session recipient.

[0128] Figure 10 FIG. schematically shows an example block diagram of another device 1000 for session sharing according to an embodiment of the present disclosure. The device 1000 may include a receiving module 1010 and an acknowledgment sending module 1020. The receiving module 1010 is configured to receive a session sharing request for requesting to share a predetermined session from a session initiator, where the predetermined session has been established with the session initiator on a first link to achieve data transmission with the session initiator. The acknowledgment sending module 1020 is configured to send an acknowledgment of the session sharing request to the session initiator to share the predetermined session to at least one second link different from the first link, so that data transmission can be achieved between the first link and the at least one second link with the session initiator.

[0129] It should be understood that Figure 9 The device shown can be implemented as a session initiator. Figure 10 The device shown can be implemented as a session recipient, thus constituting a system for session sharing. The session initiator and the session recipient can interact according to the Figure 6A or Figure 6B described process to achieve session sharing. As an example, in the reference Figure 1In the described environment, device 110 can be a session recipient, and any one of devices 121, 122, and 123 can be a session initiator. The session established therebetween can be shared on different links according to the foregoing method.

[0130] It should also be noted that with respect to Figures 7 to 10 the depicted apparatus can have various features according to Figures 3A to 6B the corresponding method described, and in order to avoid redundancy, they will not be described again here.

[0131] Figure 11 FIG. schematically shows an example block diagram of a computing device 1100 according to an embodiment of the present disclosure.

[0132] The computing device 1100 can be, for example, a server, a desktop computer, a laptop computer, a tablet, a smart phone, a smart watch, a wearable device, or any other suitable computing device or computing system, ranging from a full-resource device with a large amount of memory and processor resources to a low-resource device with limited memory and / or processing resources. In some embodiments, any one of the apparatuses 700, 800, 900, and 1000 described above with respect to Figures 7 to 10 can take the form of the computing device 1100.

[0133] As shown in the figure, the example computing device 1100 includes a processing system 1101, one or more computer-readable media 1102, and one or more I / O interfaces 1103 that are communicatively coupled to each other. Although not shown, the computing device 1100 may also include a system bus or other data and command transfer systems that couple the various components to each other. The system bus can include any one or combination of different bus structures, which can be, for example, a memory bus or memory controller, a peripheral bus, a universal serial bus, and / or a processor or local bus using any one of various bus architectures. Various other examples such as control and data lines are also contemplated.

[0134] The processing system 1100 represents the functionality to perform one or more operations using hardware. Thus, the processing system 1100 is illustrated as including hardware elements 1104 that can be configured as a processor, functional blocks, etc. This can include being implemented in hardware as an application specific integrated circuit or other logic devices formed using one or more semiconductors. The hardware elements 1104 are not limited by the materials from which they are formed or the processing mechanisms employed therein. For example, a processor can be composed of (multiple) semiconductors and / or transistors (e.g., an electronic integrated circuit (IC)). In such a context, the instructions executable by the processor can be electronically executable instructions.

[0135] The computer-readable medium 1102 is illustrated as including a memory / storage 1105. The memory / storage 1105 represents the memory / storage capacity associated with one or more computer-readable media. The memory / storage 1105 may include volatile media (such as random access memory (RAM)) and / or non-volatile media (such as read-only memory (ROM), flash memory, optical discs, magnetic disks, etc.). The memory / storage 1105 may include fixed media (e.g., RAM, ROM, fixed hard disk drive, etc.) and removable media (e.g., flash memory, removable hard disk drive, optical disc, etc.). Exemplarily, the memory / storage 1105 may be used to store session identifiers of sessions that can be reconstructed or shared, or to store state parameters of sessions, etc. The computer-readable medium 1412 may be configured in various other ways as further described below.

[0136] One or more input / output interfaces 1103 represent functions that allow a user to type commands and information into the computing device 1100 and also allow information to be presented to the user and / or sent to other components or devices using various input / output devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone (e.g., for voice input), a scanner, a touch function (e.g., a capacitive or other sensor configured to detect physical touch), a camera (e.g., that can detect motion not involving touch as a gesture using visible or non-visible wavelengths such as infrared frequencies), a network card, a receiver, etc. Examples of output devices include a display device (e.g., a monitor or a projector), a speaker, a printer, a haptic response device, a network card, a transmitter, etc. Exemplarily, a user can select a session to be reconstructed or shared through an input interface on the session initiator to cause the session initiator to initiate a corresponding reconstruction or sharing action.

[0137] The computing device 1100 further includes a session reconstruction and / or session sharing application 1106. The session reconstruction and / or session sharing application 1106 may be stored as computing program instructions in the memory / storage 1105. The session reconstruction and / or session sharing application 1106 may, together with the processing system 1101, implement the functions of various modules of the various devices described Figures 7 to 10 above.

[0138] Various technologies may be described herein in the general context of software hardware elements or program modules. Generally, these modules include routines, programs, objects, elements, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The terms "module", "function", and "component" as used herein generally refer to software, firmware, hardware, or a combination thereof. The features of the technologies described herein are platform-independent, meaning that these technologies can be implemented on various computing platforms with various processors.

[0139] Implementations of the described modules and techniques may be stored on or transmitted across some form of computer-readable medium. The computer-readable medium may include a variety of media accessible by computing device 1100. By way of example and not limitation, the computer-readable medium may include "computer-readable storage media" and "computer-readable signal media".

[0140] Contrary to mere signal transmission, carrier waves, or signals themselves, "computer-readable storage media" refers to media and / or devices that can persistently store information, and / or tangible storage devices. Thus, computer-readable storage media refers to non-signal-bearing media. Computer-readable storage media includes hardware such as volatile and non-volatile, removable and non-removable media and / or storage devices implemented in a method or technology suitable for storing information such as computer-readable instructions, data structures, program modules, logic elements / circuits, or other data. Examples of computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disks (DVDs) or other optical storage devices, hard disks, magnetic cassettes, magnetic tape, magnetic disk storage devices or other magnetic storage devices, or other storage devices, tangible media, or articles of manufacture suitable for storing the desired information and accessible by a computer.

[0141] "Computer-readable signal media" refers to a signal-bearing medium configured to send instructions to computing device 1100, such as via a network. Signal media typically may embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, data signal, or other transmission mechanism. Signal media also includes any information delivery medium. The term "modulated data signal" refers to a signal that has its information encoded in such a way as to set or change one or more of its characteristics. By way of example and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media.

[0142] As described above, the hardware elements 1104 and the computer-readable medium 1102 represent instructions, modules, programmable device logic, and / or fixed device logic implemented in hardware, which in some embodiments can be used to implement at least some aspects of the techniques described herein. The hardware elements can include integrated circuits or system-on-chips, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), and components of other hardware devices implemented in silicon or other hardware. In this context, the hardware elements can serve as processing devices that execute program tasks defined by the instructions, modules, and / or logic embodied by the hardware elements, as well as hardware devices for storing instructions for execution, e.g., the computer-readable storage medium described previously.

[0143] The foregoing combinations can also be used to implement the various techniques and modules described herein. Thus, software, hardware, or program modules and other program modules can be implemented as one or more instructions and / or logic on a computer-readable storage medium of some form and / or embodied by one or more hardware elements 1104. The computing device 1100 can be configured to implement specific instructions and / or functions corresponding to the software and / or hardware modules. Thus, for example, by using the computer-readable storage medium of the processing system and / or the hardware elements 1104, a module can be implemented at least in part in hardware as a module executable by the computing device 1100 as software. The instructions and / or functions can be executable / operable by one or more articles of manufacture (e.g., one or more computing devices 1100 and / or processing system 1101) to implement the techniques, modules, and examples described herein.

[0144] By studying the drawings, the disclosure, and the appended claims, those skilled in the art will be able to understand and implement variations of the disclosed embodiments when practicing the claimed subject matter. In the claims, the word "comprising" does not exclude other elements or steps, and the words "a" or "an" do not exclude a plurality. 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 session reconstruction, comprising: Determining that a session recipient supports the reconstruction of a predetermined session; Sending a session reconstruction request for reconstructing the predetermined session to the session recipient, where the predetermined session has been disconnected after being initially established with the session recipient; In response to receiving an acknowledgement of the session reconstruction request from the session recipient, reconstructing the predetermined session with the session recipient according to the session reconstruction parameters of the predetermined session, where the session reconstruction parameters of the predetermined session are determined based on the state parameters when the predetermined session is disconnected; Wherein, the determining that a session recipient supports the reconstruction of a predetermined session includes: determining at the time when the predetermined session is initially established that the session recipient supports the reconstruction of the predetermined session, which includes: Sending a first session request frame to the session recipient, where the first session request frame is used to request to establish the predetermined session with the session recipient and includes a session support reconstruction indicator; Receiving an acknowledgement of the first session request frame from the session recipient and a session response frame for the first session request frame; In response to determining that the session response frame includes a session support reconstruction indicator, sending an acknowledgement for the session response frame to the session recipient to determine that the session recipient supports the reconstruction of the predetermined session while establishing the predetermined session with the session recipient.

2. The method according to claim 1, wherein, The sending a session reconstruction request for reconstructing the predetermined session to the session recipient includes: Sending a second session request frame to the session recipient, where the second session request frame includes a session identifier for the predetermined session and a session support reconstruction indicator.

3. The method according to claim 2, wherein the second session request frame further includes the session reconstruction parameters of the predetermined session.

4. The method according to claim 1, wherein the predetermined session has been disconnected after being initially established with the session recipient on a first link, and wherein, The reconstructing the predetermined session with the session recipient according to the session reconstruction parameters of the predetermined session includes: Reconstructing the predetermined session with the session recipient on one of multiple links according to the session reconstruction parameters of the predetermined session, where the multiple links include the first link.

5. A method for session reconstruction, comprising: Receiving a session reconstruction request for reconstructing a predetermined session from a session initiator, where the predetermined session has been disconnected after being initially established with the session initiator; Sending an acknowledgement for the session reconstruction request to the session initiator to reconstruct the predetermined session with the session initiator according to the session reconstruction parameters of the predetermined session, where the session reconstruction parameters of the predetermined session are determined based on the state parameters when the predetermined session is disconnected; Wherein the method further includes: at the time when the predetermined session is initially established, acknowledging to the session initiator the support for the reconstruction of the predetermined session, which includes: Receiving a first session request frame from the session initiator, where the first session request frame is used to request to establish the predetermined session between the session initiator and the session recipient; In response to the first session request frame including a session support reconstruction indicator, send an acknowledgment of the first session request frame and a session response frame for the first session request frame to the session initiator, where the session response frame includes a session support reconstruction indicator to confirm to the session initiator the support for the reconstruction of the predetermined session; Receive an acknowledgment of the session response frame from the session initiator to establish the predetermined session with the session initiator.

6. The method according to claim 5, wherein The receiving of the session reconstruction request for reconstructing the predetermined session from the session initiator includes: Receive a second session request frame from the session initiator, where the second session request frame includes a session identifier for the predetermined session and a session support reconstruction indicator.

7. The method according to claim 6, wherein the second session request frame further includes session reconstruction parameters of the predetermined session.

8. The method according to claim 5, wherein the predetermined session has been disconnected after being initially established with the session initiator on a first link, wherein, The sending of an acknowledgment of the session reconstruction request to the session initiator to reconstruct the predetermined session with the session initiator according to the session reconstruction parameters of the predetermined session includes: Send an acknowledgment of the session reconstruction request to the session initiator to reconstruct the predetermined session with the session initiator on one of multiple links according to the session reconstruction parameters of the predetermined session, where the multiple links include the first link.

9. An apparatus for session reconstruction, comprising: A determination module configured to determine that a session recipient supports the reconstruction of a predetermined session; A request sending module configured to send a session reconstruction request for reconstructing the predetermined session to the session recipient, where the predetermined session has been disconnected after being initially established with the session recipient; A reconstruction module configured to, in response to receiving an acknowledgment of the session reconstruction request from the session recipient, reconstruct the predetermined session with the session recipient according to the session reconstruction parameters of the predetermined session, where the session reconstruction parameters of the predetermined session are determined based on state parameters when the predetermined session was disconnected; wherein the determination module is further configured to: determine that the session recipient supports the reconstruction of the predetermined session when the predetermined session is initially established, which includes: Send a first session request frame to the session recipient, where the first session request frame is used to request to establish the predetermined session with the session recipient and includes a session support reconstruction indicator; Receive an acknowledgment of the first session request frame and a session response frame for the first session request frame from the session recipient; In response to determining that the session response frame includes a session support reconstruction indicator, send an acknowledgment of the session response frame to the session recipient to determine that the session recipient supports the reconstruction of the predetermined session while establishing the predetermined session with the session recipient.

10. An apparatus for session reconstruction, comprising: A receiving module configured to receive a session reconstruction request for reconstructing a predetermined session from a session initiator, where the predetermined session has been disconnected after being initially established with the session initiator; A confirmation sending module, configured to send a confirmation for the session reconstruction request to a session initiator, so as to reconstruct the predetermined session with the session initiator according to the session reconstruction parameters of the predetermined session, and the session reconstruction parameters of the predetermined session are determined based on the state parameters when the predetermined session is disconnected; Wherein, the confirmation sending module is further configured to: when the predetermined session is initially established, confirm to the session initiator the support for the reconstruction of the predetermined session, which includes: Receiving a first session request frame from the session initiator, wherein the first session request frame is used to request the establishment of the predetermined session with the session initiator; In response to the first session request frame including a session support reconstruction indicator, sending a confirmation for the first session request frame and a session response frame for the first session request frame to the session initiator, wherein the session response frame includes a session support reconstruction indicator to confirm to the session initiator the support for the reconstruction of the predetermined session; Receiving a confirmation for the session response frame from the session initiator, so as to establish the predetermined session with the session initiator.

11. A system for session reconstruction, including the device according to claim 9 and the device according to claim 10, wherein the device according to claim 9 is implemented as a session initiator, and the device according to claim 10 is implemented as a session receiver.

12. A computing device, including a memory and a processor, the memory being configured to store computer-executable instructions thereon, and the computer-executable instructions, when executed on the processor, execute the method according to any one of claims 1-8.

13. A computer-readable storage medium, storing computer-executable instructions thereon, and the computer-executable instructions, when executed on a processor, execute the method according to any one of claims 1-8.

Citation Information

Patent Citations

  • Method for re-enabling data frame aggregation after bluetooth session

    CN107005366A