CN106941732A - Reconnection method, system and WFD equipment - Google Patents

Abstract

The invention discloses a reconnection method, comprising: when reconnection is required, a first WFD device sends a reconnection identifier and a corresponding session identifier to a second WFD device; the reconnection identifier is used to indicate the second WFD device This connection is a reconnection; the session identifier is used to instruct the second WFD device to obtain a negotiated parameter set corresponding to the capability of the session identifier; the session identifier is a session identifier that identifies the uniqueness of the connection; the The second WFD device is the receiving end device of the first WFD device; receives the reconnection response returned by the second WFD device; the reconnection response indicates that the reconnection is successful. The invention also discloses a first WFD device, a second WFD device and a reconnection system.

Description

Reconnection method, system and WFD device

technical field

The present invention relates to the field of reconnection of communication technology, in particular to a reconnection method, system and WFD (Wi-Fi Direct) equipment.

Background technique

The Wi-Fi Alliance's newly announced Wi-Fi Direct (WFD) project allows the Wi-Fi card on the user's laptop to bypass the access point and connect directly to a wireless printer, digital camera, projector, sensor or plasma screen. Correspondingly, devices that can directly implement these functions are called WFD devices.

During the process of sharing the same screen or audio and video transmission between WFD devices, there will be a situation where the device is switched or disconnected due to a device failure and needs to be reconnected. At this time, the two WFD devices need to perform device and capability negotiation from the beginning from the device discovery. Information exchange, that is, the process of connecting newly discovered devices. In this way, the time required to reconnect will be relatively long, greatly reducing the connection speed.

Contents of the invention

In order to solve existing technical problems, embodiments of the present invention provide a reconnection method, system, and WFD equipment.

In order to achieve the above object, the technical solution of the embodiment of the present invention is achieved in this way:

An embodiment of the present invention provides a reconnection method, which is applied to a first WFD device, and the method includes:

When reconnection is required, send a reconnection identifier and a corresponding session identifier to the second WFD device; the reconnection identifier is used to indicate that the second WFD device is reconnected this time; the session identifier is used to indicate the The second WFD device obtains a negotiated parameter set corresponding to the capability of the session identifier; the session identifier is a session identifier that identifies the uniqueness of the connection; the second WFD device is the receiving end device of the first WFD device;

receiving a reconnection response returned by the second WFD device; the reconnection response indicates that the reconnection is successful.

In the above solution, the reconnection identifier and the corresponding session identifier are carried in a Real Time Streaming Protocol (RTSP, Real Time Streaming Protocol) option (OPTIONS) request message, and the RTSP OPTIONS request message is used to obtain the second WFD RTSP method set supported by the device;

Correspondingly, the reconnection response is an RTSP OPTIONS response.

In the above scheme, the method also includes:

In the stage of establishing a point-to-point (P2P, Peer to Peer) connection before the reconnection, the session identifier is sent to the second WFD device.

In the above solution, the session identifier sent to the second WFD device is carried in the connection/reconnection request frame.

In the above scheme, the method also includes:

Before the P2P connection is established, generate the session identifier;

The session identification is stored locally.

The embodiment of the present invention also provides a reconnection method, which is applied to the second WFD device, and the method includes:

Receiving the reconnection identifier and the corresponding session identifier sent by the first WFD device; the second WFD device is the receiving end device of the first WFD device; the session identifier is a session identifier that identifies the uniqueness of the connection;

Determining that the connection with the first WFD device is a reconnection according to the reconnection identifier;

According to the session identifier, search locally for the negotiated parameter set corresponding to the capability of the session identifier;

After the search is successful, a reconnection response is sent to the first WFD device; the reconnection response indicates that the reconnection is successful.

In the above solution, the reconnection identifier and the corresponding session identifier are carried in the RTSP OPTIONS request message, and the RTSP OPTIONS request message is used to obtain the RTSP method set supported by the second WFD device;

Correspondingly, extracting the reconnection identifier and the corresponding session identifier from the RTSP OPTIONS request message;

The reconnection response is an RTSP OPTIONS response.

In the above scheme, the method also includes:

In the P2P connection establishment stage before the reconnection, receiving the session identifier sent by the first WFD device;

saving the received session identifier locally;

In the session establishment phase before the reconnection, after performing capability negotiation with the first WFD device, the corresponding relationship between the session identifier and the parameter set after capability negotiation is saved.

In the above solution, the received session identifier is carried in the connection/reconnection request frame;

Correspondingly, the session identifier is extracted from the connection/reconnection request frame.

The embodiment of the present invention further provides a first WFD device, including: a first sending unit and a first receiving unit; wherein,

The first sending unit is configured to send a reconnection identifier and a corresponding session identifier to the second WFD device when reconnection is required; the reconnection identifier is used to indicate that the second WFD device is reconnecting this time; The session ID is used to instruct the second WFD device to acquire a negotiated parameter set corresponding to the capability of the session ID; the session ID is a session ID that identifies the uniqueness of the connection; the second WFD device is the a receiving end device of the first WFD device;

The first receiving unit is configured to receive a reconnection response returned by the second WFD device; the reconnection response indicates that the reconnection is successful.

In the above solution, the first WFD device further includes: a second sending unit, configured to send the session identifier to the second WFD during the P2P connection establishment phase before the reconnection.

In the above solution, the first WFD device further includes: a generating unit, configured to generate the session identifier before establishing the P2P connection; and store the session identifier locally.

The embodiment of the present invention also provides a second WFD device, including: a second receiving unit, a determining unit, a searching unit, and a third sending unit; wherein,

The second receiving unit is configured to receive the reconnection identifier and the corresponding session identifier sent by the first WFD device; the second WFD device is the receiving end device of the first WFD device; the session identifier is an identification connection Unique session ID;

The determining unit is configured to determine that the connection with the first WFD device is a reconnection according to the reconnection identifier;

The searching unit is configured to search locally for the negotiated capability parameter set corresponding to the session ID stored according to the session ID;

The third sending unit is configured to send a reconnection response to the first WFD device after the search is successful; the reconnection response indicates that the reconnection is successful.

In the above solution, the second WFD device further includes: a third receiving unit and a storage unit; wherein,

The third receiving unit is used for the P2P connection establishment stage before the reconnection, and receives the session identifier sent by the first WFD device;

The storage unit is configured to store the received session identifier locally; and after performing capability negotiation with the first WFD device in the session establishment phase before the reconnection, save the session identifier and the capability negotiation The corresponding relationship of the parameter set.

An embodiment of the present invention further provides a reconnection system, including: a first WFD device and a second WFD device; wherein,

The first WFD device is configured to send a reconnection identifier and a corresponding session identifier to the second WFD device when reconnection is required; the session identifier is a session identifier that identifies the uniqueness of the connection; and receives the second The reconnection response returned by the WFD device;

The second WFD device is a data receiving end device of the first WFD device, configured to receive the reconnection identifier and the corresponding session identifier sent by the first WFD device; determine the connection with the reconnection identifier according to the reconnection identifier The connection between the first WFD devices is a reconnection; according to the session identifier, search locally for the negotiated parameter set corresponding to the capability corresponding to the session identifier; and after the search is successful, report to the first WFD The device sends a reconnection response; the reconnection response indicates that the reconnection is successful.

In the reconnection method, system, and WFD device provided by the embodiments of the present invention, when reconnection is required, the first WFD device sends a reconnection identifier and a corresponding session identifier to the second WFD device; the session identifier is a session that identifies the uniqueness of the connection ID; the second WFD device is the data receiving end device of the first WFD device. The second WFD device receives the reconnection ID and the corresponding session ID sent by the first WFD device; according to the reconnection ID, determine The connection with the first WFD device is a reconnection; according to the session identifier, search locally for the negotiated parameter set corresponding to the capability corresponding to the session identifier; A WFD device sends a reconnection response; the reconnection response indicates that the reconnection is successful, because during reconnection, the second WFD device only determines that this connection is a reconnection according to the received reconnection identifier, and only according to The session identifier searches for the corresponding parameter set after capability negotiation, thereby eliminating the message interaction process in the WFD capability negotiation stage, thus greatly improving the connection speed and accelerating the reconnection process.

Description of drawings

In the drawings (which are not necessarily drawn to scale), like reference numerals may describe like parts in different views. Similar reference numbers with different letter suffixes may indicate different instances of similar components. The drawings generally illustrate the various embodiments discussed herein, by way of example and not limitation.

Fig. 1 is a schematic diagram of the process of establishing a connection between two WFD devices in the related art;

FIG. 2 is a schematic diagram of a session connection process between WFD devices in the related art;

3 is a schematic flowchart of a reconnection method on the first WFD side according to Embodiment 1 of the present invention;

4 is a schematic flowchart of a reconnection method on the second WFD side according to Embodiment 1 of the present invention;

5 is a schematic flow chart of a reconnection method according to an embodiment of the present invention;

Fig. 6 is a schematic structural diagram of the first WFD in Embodiment 2 of the present invention;

FIG. 7 is a schematic structural diagram of a second WFD according to Embodiment 2 of the present invention;

FIG. 8 is a schematic structural diagram of a double connection system according to an embodiment of the present invention.

detailed description

The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments.

Before describing the embodiments of the present invention, let us have a detailed understanding of the current related technologies.

As shown in FIG. 1 , the process of establishing a connection between two WFD devices mainly includes: a WFD device discovery process, a WFD connection establishment process, and a capability negotiation process (that is, a session establishment process). In addition, it may further include a WFD service discovery process. In actual application, the WFD service discovery process is not a mandatory process, and it can be determined according to service requirements whether to perform the WFD service discovery process.

Among them, the information exchanged in the above-mentioned processes all include WFD information (Information) identification (ID) (that is, WFD information element (IE, Information Element)), such as the beacon (beacon) sent by the WFD device for connection The data structure of WFD IE is included in the packet, probe request and probe response message. Some basic information carried by WFD IE can make an optimal connection between two devices.

At the same time, FIG. 2 shows the process of session connection between WFD devices, that is, the WFD Capability Negotiation stage (WFD Capability Negotiation), which can also be called the process of exchanging capability information between WFD devices. At this time, the WFD device is called a miracast device. As shown in Figure 2, the process includes the following steps:

Step 201: the source (Source) device sends an M1 request message to the receiving (Sink) device;

In other words, send an RTSP OPTIONS request message to obtain the RTSP method set supported by the Sink device.

Step 202: the sink device sends an M1 response message after receiving the M1 request message.

Step 203: After the M1 response message is sent successfully, the Sink device sends an M2 request message to the Source device;

In other words, send an RTSP OPTIONS request message to obtain the RTSP method set supported by the Source device.

Step 204: After the Source device receives the M2 request message, it sends the M2 response message to the Source device;

Step 205: After the M2 response message is sent successfully, the Source device sends the M3 request message to the Sink device;

In other words, send an RTSP parameter acquisition (GET_PARAMETER) request message to obtain the WFD capability list of the Sink device of interest.

The specific content of the WFD capability list may include audio format, video format, several resolutions (such as 1080p, 720p, 480p, etc.), corresponding frame rate, and supported content protection methods.

Step 206: After receiving the M3 request message, the Sink device sends an M3 response message to the Source device;

Step 207: After receiving the M3 response message, the Source device sets parameters by sending an M4 request message to the Sink device;

Here, after receiving the M3 response message, according to the information carried in the response message, the Source device determines the parameter set of the subsequent WFD session (the direction is sent by the Source device and received by the Sink device) and sends an RTSP setting parameter (SET_PARAMETER) request message to the Sink device That is, the M4 request message to allow the Sink device to set the corresponding parameters.

Step 208: After receiving the M4 request message, the Sink device replies with an M4 response message;

Step 209: After receiving the M4 response message and the response message is a positive message reply, the Source device sends an M5 request message to the Sink device;

In other words, send RTSP SET_PARAMETER (WFD-trigger-method) request message to trigger subsequent connection establishment, playback and other functions.

Step 210: After receiving the M5 request message, the Sink device replies an M5 response message to the Source device;

Step 211: After receiving the M5 response message and the response message is an affirmative message reply, the Source device sends an M6 request message to the Sink device;

In other words, an RTSP establishment (SETUP) request message is sent, and the message carries the message content of the connection establishment function.

Step 212: After receiving the M6 please request message, the Sink device replies an M6 response message to the Source device;

Step 213: After receiving the M6 response message and the response message is a positive message reply, the Source device sends the M7 request message to the Sink device;

In other words, an RTSP establishment (PLAY) request message is sent, and the message carries message content of functions such as connection playback.

Step 214: After receiving the M7 Please request message, the Sink device replies an M7 Reply message to the Source device.

When the M7 response message is received and the response message is an affirmative reply, it means that the session connection process between the WFD devices is completed. After completion, the same frequency or audio and video transmission process can be carried out between the Source device and the Sink device.

During the same screen or audio and video transmission between WFD devices, on the one hand, the problem of device switching is often encountered. For example, suppose device A is connected to device B, and then switched to device A and device C Connect, but then may switch to device B, during which device A and device B need to be reconnected; on the other hand, there may also be a problem of network failure disconnection and reconnection; in these cases, in In the existing technical solution, the RTSP negotiation needs to be performed again, that is, steps 201-214 need to be performed again, that is, M1-M7 related process steps in miracast. In this way, the connection speed will be greatly reduced, thereby reducing the user experience.

Based on this, in various embodiments of the present invention: when reconnection is required, the first WFD device sends a reconnection identifier and a corresponding session identifier to the second WFD device; the session identifier is a session identifier that identifies the uniqueness of the connection; The second WFD device receives the reconnection identifier and the corresponding session identifier sent by the first WFD device; according to the reconnection identifier, determine that the connection with the first WFD device is a reconnection; according to the session identifier , searching locally for the negotiated capability parameter set corresponding to the session identifier stored; and after the search is successful, sending a reconnection response to the first WFD device; the reconnection response indicates that the reconnection is successful.

Wherein, the second WFD device is a data receiving end device of the first WFD device.

Embodiment one

This embodiment provides a reconnection method, which is applied to the first WFD device. As shown in FIG. 3, the method includes the following steps:

Step 301: When reconnection is required, the first WFD device sends a reconnection identifier and a corresponding session identifier to the second WFD device;

Here, the reconnection identifier is used to indicate that the second WFD device is reconnecting this time, not a new connection; the session identifier is used to instruct the second WFD device to obtain the capability negotiation corresponding to the session identifier The following parameter set; the session identifier is a session identifier that identifies the uniqueness of the connection.

The second WFD device is a receiving end device of the first WFD device. In other words, the first WFD device is a sending end device, and the second WFD device is a receiving end device. That is, the multimedia data sent by the first WFD device is sent, and the multimedia data sent by the first WFD device is received by the second WFD device.

The timing when reconnection is required may be: the first WFD device needs to be reconnected when it is switched or disconnected due to a device failure.

In an embodiment, the reconnection identifier and the corresponding session identifier may be carried in an RTSP OPTIONS request message, and the RTSP OPTIONS request message is used to obtain the RTSP method set supported by the second WFD device.

In other words, the reconnection identifier and the corresponding session identifier can be carried in the M1 request message shown in FIG. 2 .

At this time, the content carried in the M1 request message is shown in Table 1.

Table 1

Among them, in Table 1, Reconnect and Session ID are newly added contents. Reconnect is the reconnection identifier, and Session ID is the session identifier.

In Table 1, Required means that it must be carried. From Source to Sink represents the M1 request message sent by the first WFD device to the second WFD device; From Sink to Source represents the M1 response message sent by the second WFD device to the first WFD device. The purpose of sending the M1 response message is to let the first WFD device know that the reconnection is successful.

In practical applications, before reconnection, both the first WFD device and the second WFD device need to set and save the session identifier for subsequent processing.

Based on this, the method may also include:

In the P2P connection establishment phase before the reconnection, the session identifier is sent to the second WFD device.

Specifically, the session identifier sent to the second WFD device may be carried in an association/reassociation request frame (Association/Reassociation Request Frame).

Here, the P2P connection establishment phase refers to the WFD connection establishment process in FIG. 1 .

Carrying the session identifier in the Association/Reassociation Request Frame can be implemented in the following way:

Since some basic information carried in WFD IE can make the best connection between two devices, in order to realize a unique session identifier for the connection between two WFD devices, WFD subelements (subelements) in WFDIE can be extension, so that the WFD subelements include the content of the session ID (Session ID).

Table 2

At the same time, in order to enable the two connected WFD devices to set and save the above-mentioned session ID (SessionID), it is necessary to expand the contents of the Association/Reassociation Request Frame and Association/Reassociation Response Frame sent during the device connection establishment phase. The specific content expanded in the Association/Reassociation Request Frame can be shown in the row corresponding to the Session ID in Subelements in Table 3, and the specific content expanded in the Association/ReassociationResponse Frame can be shown in the row corresponding to the Session ID in Table 4. displayed content.

table 3

Table 4

Wherein, the role of the Association/Reassociation Response Frame carrying the session ID (SessionID) is to let the first WFD device know that the second WFD device has received the session ID.

In one embodiment, the method may also include:

Before the P2P connection is established, generate the session identifier;

The session identification is stored locally.

Here, the session identifier generated by the first WFD device may be a string of random numbers, as long as it is a unique identifier.

Step 302: Receive a reconnection response returned by the second WFD device; the reconnection response indicates that the reconnection is successful.

Here, after the second WFD device receives the reconnection identifier and the corresponding session identifier, it knows that this connection is a reconnection according to the reconnection identifier, so after searching and storing the capability negotiation corresponding to the session identifier locally, parameter set; when the corresponding parameter set is found, it will send a reconnection response to the first WFD device. At this time, when the reconnection identifier and the corresponding session identifier are carried in the M1 request message, the second WFD The device returns an M1 response message to the first WFD device, that is, the reconnection response is an RTSP OPTIONS response.

Wherein, when the second WFD device cannot find the corresponding parameter set locally, that is, when the search fails, it will perform the complete process shown in FIG. 2 with the first WFD device to complete the session establishment process.

It should be noted that: the session ID (Session ID) is different from an ordinary device ID, it is more like a manager (Handler), and the session ID is associated with the parameter set after capability negotiation between WFD devices during a call , it is precisely because of the association of this parameter set that the second WFD device may realize the effect of fast reconnection.

This embodiment also provides a reconnection method, which is applied to the second WFD device. As shown in FIG. 4, the method includes the following steps:

Step 401: Receive the reconnection identifier and the corresponding session identifier sent by the first WFD device;

Here, the session identifier is a session identifier that identifies the uniqueness of the connection.

The second WFD device is a receiving end device of the first WFD device. In other words, the first WFD device is a sending end device, and the second WFD device is a receiving end device. That is, the multimedia data sent by the first WFD device is sent, and the multimedia data sent by the first WFD device is received by the second WFD device.

In an embodiment, the reconnection identifier and the corresponding session identifier may be carried in an RTSP OPTIONS request message, and the RTSP OPTIONS request message is used to obtain the RTSP method set supported by the second WFD device;

Correspondingly, the second WFD device extracts the reconnection identifier and the corresponding session identifier from the RTSP OPTIONS request message.

In other words, the reconnection identifier and the corresponding session identifier can be carried in the M1 request message shown in FIG. 2 .

At this time, the content carried in the M1 request message is shown in Table 1.

Among them, in Table 1, Reconnect and Session ID are newly added contents. Reconnect is the reconnection identifier, and Session ID is the session identifier.

In Table 1, Required means that it must be carried. From Source to Sink represents the M1 request message sent by the first WFD device to the second WFD device; From Sink to Source represents the M1 response message sent by the second WFD device to the first WFD device. The purpose of sending the M1 response message is to let the first WFD device know that the reconnection is successful.

In practical applications, before reconnection, both the first WFD device and the second WFD device need to set and save the session identifier for subsequent processing.

Based on this, the method may also include:

In the P2P connection establishment stage before the reconnection, the second WFD device receives the session identifier sent by the first WFD device;

saving the received session identifier locally;

In the session establishment phase before the reconnection, after performing capability negotiation with the first WFD device, the second WFD device saves the correspondence between the session identifier and the parameter set after capability negotiation.

Wherein, the session identifier received by the second WFD device may be carried in the Association/Reassociation Request Frame;

Correspondingly, the second WFD device extracts the session identifier from the Association/Reassociation Request Frame.

Here, the P2P connection establishment phase refers to the WFD connection establishment process in FIG. 1 .

Carrying the session identifier in the Association/Reassociation Request Frame can be implemented in the following way:

Since some basic information carried in WFD IE can make an optimal connection between two devices, in order to realize a unique session identifier for the connection between two WFD devices, the WFD subelements in WFDIE can be extended, so that The WFD subelements include the content of the session ID (Session ID), and the specific content of the extension may be as shown in Table 2 where the Subelement ID is 11.

At the same time, in order to enable the two connected WFD devices to set and save the above-mentioned session ID (SessionID), it is necessary to expand the contents of the Association/Reassociation Request Frame and Association/Reassociation Response Frame sent during the device connection establishment phase. The specific content expanded in the Association/Reassociation Request Frame can be as shown in the row corresponding to the Session ID in the Subelements in Table 3, and the specific content expanded in the Association/ReassociationResponse Frame can be shown in the row corresponding to the Session ID in the Subelements in Table 4 content shown.

Wherein, the role of the Association/Reassociation Response Frame carrying the session ID (SessionID) is to let the first WFD device know that the second WFD device has received the session ID.

Step 402: According to the reconnection identifier, determine that the connection with the first WFD device is a reconnection;

Step 403: According to the session ID, search locally for the negotiated parameter set corresponding to the capability of the session ID;

Step 404: After the search succeeds, send a reconnection response to the first WFD device; the reconnection response indicates that the reconnection is successful.

Here, when the second WFD device obtains the reconnection identifier and the corresponding session identifier through the M1 request message, after finding the parameter set successfully, the second WFD device will return an M1 response message to the first WFD device , that is, the reconnection response is an RTSP OPTIONS response.

Wherein, when the second WFD device cannot find the corresponding parameter set locally, that is, when the search fails, it will perform the complete process shown in FIG. 2 with the first WFD device to complete the session establishment process.

It should be noted that: the session ID (Session ID) is different from ordinary device IDs, it is more like a Handler, and the session ID is associated with the parameter set after capability negotiation between WFD devices during a call, precisely because Only by associating such a parameter set can the second WFD device realize the effect of fast reconnection.

This embodiment also provides a reconnection method, as shown in Figure 5, the method includes the following steps:

Step 501: When reconnection is required, the first WFD device sends a reconnection identifier and a corresponding session identifier to the second WFD device;

Here, the session identifier is a session identifier that identifies the uniqueness of the connection.

Step 502: The second WFD device receives the reconnection identifier and the corresponding session identifier sent by the first WFD device; according to the reconnection identifier, determine that the connection with the first WFD device is a reconnection; according to the The session identifier, searching locally for the negotiated parameter set corresponding to the capability corresponding to the session identifier; and after the search succeeds, sending a reconnection response to the first WFD device;

Here, the reconnection response indicates that the reconnection is successful.

It should be noted that: the specific processing procedures of the first WFD device and the second WFD device have been described in detail above, and will not be repeated here.

In the reconnection method provided by the embodiment of the present invention, when reconnection is required, the first WFD device sends a reconnection identifier and a corresponding session identifier to the second WFD device; the session identifier is a session identifier that identifies the uniqueness of the connection; the second WFD device The second WFD device is the data receiving end device of the first WFD device. The second WFD device receives the reconnection identifier and the corresponding session identifier sent by the first WFD device; according to the reconnection identifier, determine the connection with the first WFD device. The connection between WFD devices is a reconnection; according to the session identifier, search locally for the parameter set after negotiation of the capability corresponding to the session identifier; and after the search succeeds, send a reconnection to the first WFD device Connection response; the reconnection response indicates that the reconnection is successful, because during reconnection, the second WFD device only determines that this connection is a reconnection according to the received reconnection identifier, and only searches for the corresponding session identifier according to the session identifier. The parameter set after capability negotiation saves the message interaction process in the WFD capability negotiation stage, thus greatly improving the connection speed and speeding up the reconnection process, thereby improving user experience and improving the practicability of WFD device interconnection .

Embodiment two

In order to implement the method of the embodiment of the present invention, this embodiment provides a first WFD device. As shown in FIG. 6, the first WFD device includes: a first sending unit 61 and a first receiving unit 62; wherein,

The first sending unit 61 is configured to send a reconnection identifier and a corresponding session identifier to the second WFD device when reconnection is required; the reconnection identifier is used to indicate that the second WFD device is reconnecting this time ; The session identifier is used to instruct the second WFD device to obtain a negotiated parameter set corresponding to the capability corresponding to the session identifier; the session identifier is a session identifier that identifies the uniqueness of the connection;

The first receiving unit 62 is configured to receive a reconnection response returned by the second WFD device; the reconnection response indicates that the reconnection is successful.

Wherein, the second WFD device is a receiving end device of the first WFD device. In other words, the first WFD device is a sending end device, and the second WFD device is a receiving end device. That is, the multimedia data sent by the first WFD device is sent, and the multimedia data sent by the first WFD device is received by the second WFD device.

The timing when reconnection is required may be: the first WFD device needs to be reconnected when it is switched or disconnected due to a device failure.

In an embodiment, the reconnection identifier and the corresponding session identifier may be carried in an RTSP OPTIONS request message, and the RTSP OPTIONS request message is used to obtain the RTSP method set supported by the second WFD device.

In other words, the reconnection identifier and the corresponding session identifier can be carried in the M1 request message shown in FIG. 2 .

At this time, the content carried in the M1 request message is shown in Table 1.

Among them, in Table 1, Reconnect and Session ID are newly added contents. Reconnect is the reconnection identifier, and Session ID is the session identifier.

In Table 1, Required means that it must be carried. From Source to Sink represents the M1 request message sent by the first WFD device to the second WFD device; From Sink to Source represents the M1 response message sent by the second WFD device to the first WFD device. The purpose of sending the M1 response message is to let the first WFD device know that the reconnection is successful.

In practical applications, before reconnection, both the first WFD device and the second WFD device need to set and save the session identifier for subsequent processing.

Based on this, the first WFD device may further include: a second sending unit, configured to send the session identifier to the second WFD device during the P2P connection establishment phase before the reconnection.

Specifically, the session identifier sent to the second WF device D may be carried in an association/reassociation request frame (Association/Reassociation Request Frame).

Here, the P2P connection establishment phase refers to the WFD connection establishment process in FIG. 1 .

Carrying the session identifier in the Association/Reassociation Request Frame can be implemented in the following way:

Since some basic information carried in WFD IE can make an optimal connection between two devices, in order to implement a unique session identifier for the connection between two WFD devices, the WFD subelements in WFDIE can be extended, so that Make the WFD subelements include the content of the session ID (Session ID), and the specific content of the extension may be as shown in Table 2 where the Subelement ID is 11.

At the same time, in order to enable the two connected WFD devices to set and save the above-mentioned session ID (SessionID), it is necessary to expand the contents of the Association/Reassociation Request Frame and Association/Reassociation Response Frame sent during the device connection establishment phase. The specific content expanded in the Association/Reassociation Request Frame can be as shown in the row corresponding to the Session ID in the Subelements in Table 3, and the specific content expanded in the Association/ReassociationResponse Frame can be shown in the row corresponding to the Session ID in the Subelements in Table 4 content shown.

Wherein, the role of the Association/Reassociation Response Frame carrying the session ID (SessionID) is to let the first WFD device know that the second WFD device has received the session ID.

In an embodiment, the first WFD device may further include: a generating unit, configured to generate the session identifier before establishing the P2P connection; and store the session identifier locally.

Here, the session identifier generated by the generating unit may be a string of random numbers, as long as it is a unique identifier.

After the second WFD device receives the reconnection identifier and the corresponding session identifier, it knows that this connection is a reconnection according to the reconnection identifier, so it searches locally for the parameter after negotiation of the capability corresponding to the session identifier set; when the corresponding parameter set is found, it will send a reconnection response to the first WFD device. At this time, when the reconnection identifier and the corresponding session identifier are carried in the M1 request message, the second WFD device will An M1 response message is returned to the first WFD device, that is, the reconnection response is an RTSP OPTIONS response.

Wherein, when the second WFD device cannot find the corresponding parameter set locally, that is, when the search fails, it will perform the complete process shown in FIG. 2 with the first WFD device to complete the session establishment process.

It should be noted that: the session ID (Session ID) is different from ordinary device IDs, it is more like a Handler, and the session ID is associated with the parameter set after capability negotiation between WFD devices during a call, precisely because Only by associating such a parameter set can the second WFD device realize the effect of fast reconnection.

In actual application, the first sending unit 61, the first receiving unit 62 and the second sending unit can be composed of a central processing unit (CPU, Central Processing Unit), a microprocessor (MCU, Micro Control Unit), digital A signal processor (DSP, Digital Signal Processor) or a programmable logic array (FPGA, Field-Programmable Gate Array) is implemented in combination with a transceiver; the generating unit can be implemented by a CPU, MCU, DSP or FPGA in the first WFD device.

In order to realize the method of the embodiment of the present invention, this embodiment also provides a second WFD. As shown in FIG. Sending unit 74; wherein,

The second receiving unit 71 is configured to receive the reconnection identifier and the corresponding session identifier sent by the first WFD device; the session identifier is a session identifier that identifies the uniqueness of the connection;

The determining unit 72 is configured to determine that the connection with the first WFD device is a reconnection according to the reconnection identifier;

The search unit 73 is configured to, according to the session identifier, locally search for a parameter set after negotiation of a capability corresponding to the session identifier that is stored;

The third sending unit 74 is configured to send a reconnection response to the first WFD device after the search is successful; the reconnection response indicates that the reconnection is successful.

Wherein, the second WFD device is a receiving end device of the first WFD device. In other words, the first WFD device is a sending end device, and the second WFD device is a receiving end device. That is, the multimedia data sent by the first WFD device is sent, and the multimedia data sent by the first WFD device is received by the second WFD device.

In an embodiment, the reconnection identifier and the corresponding session identifier may be carried in an RTSP OPTIONS request message, and the RTSP OPTIONS request message is used to obtain the RTSP method set supported by the second WFD device;

Correspondingly, the second receiving unit 71 extracts the reconnection identifier and the corresponding session identifier from the RTSP OPTIONS request message.

In other words, the reconnection identifier and the corresponding session identifier can be carried in the M1 request message shown in FIG. 2 .

At this time, the content carried in the M1 request message is shown in Table 1.

Among them, in Table 1, Reconnect and Session ID are newly added contents. Reconnect is the reconnection identifier, and Session ID is the session identifier.

In Table 1, Required means that it must be carried. From Source to Sink represents the M1 request message sent by the first WFD device to the second WFD device; From Sink to Source represents the M1 response message sent by the second WFD device to the first WFD device. The purpose of sending the M1 response message is to let the first WFD device know that the reconnection is successful.

In practical applications, before reconnection, both the first WFD device and the second WFD device need to set and save the session identifier for subsequent processing.

Based on this, the second WFD device may further include: a third receiving unit and a storage unit; wherein,

The third receiving unit is used for the P2P connection establishment stage before the reconnection, and receives the session identifier sent by the first WFD device;

The storage unit is configured to store the received session identifier locally; and after performing capability negotiation with the first WFD device in the session establishment phase before the reconnection, save the session identifier and the capability negotiation The corresponding relationship of the parameter set.

Wherein, the session identifier received by the second WFD device may be carried in the Association/Reassociation Request Frame;

Correspondingly, the second WFD device extracts the session identifier from the Association/Reassociation Request Frame.

Here, the P2P connection establishment phase refers to the WFD connection establishment process in FIG. 1 .

Carrying the session identifier in the Association/Reassociation Request Frame can be implemented in the following way:

Since some basic information carried in WFD IE can make an optimal connection between two devices, in order to realize a unique session identifier for the connection between two WFD devices, the WFD subelements in WFDIE can be extended, so that The WFD subelements include the content of the session ID (Session ID), and the specific content of the extension may be as shown in Table 2 where the Subelement ID is 11.

At the same time, in order to enable the two connected WFD devices to set and save the above-mentioned session ID (SessionID), it is necessary to expand the contents of the Association/Reassociation Request Frame and Association/Reassociation Response Frame sent during the device connection establishment phase. The specific content expanded in the Association/Reassociation Request Frame can be as shown in the row corresponding to the Session ID in the Subelements in Table 3, and the specific content expanded in the Association/ReassociationResponse Frame can be shown in the row corresponding to the Session ID in the Subelements in Table 4 content shown.

Wherein, the role of the Association/Reassociation Response Frame carrying the session ID (SessionID) is to let the first WFD device know that the second WFD device has received the session ID.

Here, when the second receiving unit 71 obtains the reconnection identifier and the corresponding session identifier through the M1 request message, after finding the parameter set successfully, the third sending unit 74 will return the M1 message to the first WFD device. The response message, that is, the reconnection response is an RTSP OPTIONS response.

Wherein, when the search unit 73 cannot find the corresponding parameter set locally, that is, when the search fails, it will perform the complete process shown in FIG. 2 with the first WFD device to complete the session establishment process.

It should be noted that: the session ID (Session ID) is different from ordinary device IDs, it is more like a Handler, and the session ID is associated with the parameter set after capability negotiation between WFD devices during a call, precisely because Only by associating such a parameter set can the second WFD device realize the effect of fast reconnection.

During actual application, the second receiving unit 71, the third sending unit 74, and the third receiving unit can be realized by CPU, MCU, DSP or FPGA in the second WFD device in conjunction with a transceiver; the determining unit 72, the searching unit 73 and the storage The unit can be realized by CPU, MCU, DSP or FPGA in the second WFD device.

In order to implement the method of the embodiment of the present invention, this embodiment also provides a reconnection system, as shown in FIG. 8 , the system includes: a first WFD device 81 and a second WFD device 82; wherein,

The first WFD device 81 is configured to send a reconnection identifier and a corresponding session identifier to the second WFD device 82 when reconnection is required; the session identifier is a session identifier that identifies the uniqueness of the connection; and receives the The reconnection response returned by the second WFD device 82;

The second WFD device 82 is a data receiving end device of the first WFD device 81, configured to receive the reconnection identifier and the corresponding session identifier sent by the first WFD device 81; according to the reconnection identifier, determine and The connection between the first WFD devices 81 is a reconnection; according to the session identifier, search locally for the negotiated parameter set corresponding to the capability corresponding to the session identifier; A WFD device 81 sends a reconnection response; the reconnection response indicates that the reconnection is successful.

It should be noted that: the specific processing procedures of the first WFD device 81 and the second WFD device 82 have been described in detail above, and will not be repeated here.

In the solution provided by the embodiment of the present invention, when reconnection is required, the first WFD device sends the reconnection identifier and the corresponding session identifier to the second WFD device; the session identifier is a session identifier that identifies the uniqueness of the connection; the second WFD The device is the data receiving end device of the first WFD device. The second WFD device receives the reconnection identifier and the corresponding session identifier sent by the first WFD device; according to the reconnection identifier, determine the connection with the first WFD device The connection between them is a reconnection; according to the session identifier, search locally for the negotiated parameter set corresponding to the capability corresponding to the session identifier; and after the search succeeds, send a reconnection response to the first WFD device ; The reconnection response indicates that the reconnection is successful, because during reconnection, the second WFD device only determines that this connection is a reconnection according to the received reconnection identifier, and only searches for the corresponding capability negotiation according to the session identifier The final parameter set saves the message interaction process in the WFD capability negotiation stage. In this way, the connection speed is greatly improved, and the reconnection process can be accelerated, thereby improving user experience and improving the practicability of WFD device interconnection.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, systems, or computer program products. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (15)

1. A reconnection method applied to a first WFD device, the method comprising:

when reconnection is needed, sending a reconnection identifier and a corresponding session identifier to second WFD equipment; the reconnection identifier is used for indicating that the current connection of the second WFD equipment is reconnection; the session identifier is used for indicating the second WFD device to acquire a parameter set after capability negotiation corresponding to the session identifier; the session identifier is a session identifier for identifying the uniqueness of connection; the second WFD equipment is receiving end equipment of the first WFD equipment;

receiving a reconnection response returned by the second WFD equipment; the reconnect reply is indicative of a successful reconnection.

2. The method of claim 1, wherein the reconnection identity and the corresponding session identity are carried in an RTSP streaming protocol (RTSP) selection OPTIONS request message, wherein the RTSP selection OPTIONS request message is used to obtain an RTSP method set supported by the second WFD device;

accordingly, the reconnection response is an RTSP OPTIONS response.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

and in the point-to-point P2P connection establishment phase before reconnection, sending the session identification to the second WFD device.

4. The method of claim 3, wherein the session identification sent to the second WFD device is carried in a join/reconnect request frame.

5. The method of claim 3, further comprising:

generating the session identifier before the P2P connection is established;

storing the session identification locally.

6. A reconnection method, applied to a second WFD device, the method comprising:

receiving a reconnection identifier and a corresponding session identifier sent by first WFD equipment; the second WFD equipment is receiving end equipment of the first WFD equipment; the session identifier is a session identifier for identifying the uniqueness of connection;

determining that the connection between the first WFD equipment is reconnection according to the reconnection identifier;

according to the session identifier, locally searching a stored parameter set after capability negotiation corresponding to the session identifier;

after the search is successful, sending a reconnection response to the first WFD equipment; the reconnect reply is indicative of a successful reconnection.

7. The method of claim 6, wherein the reconnection identifier and the corresponding session identifier are carried in an RTSP OPTIONS request message, and wherein the RTSP OPTIONS request message is used to obtain an RTSP method set supported by the second WFD device;

correspondingly, extracting the reconnection identifier and the corresponding session identifier from the RTSP OPTIONS request message;

the reconnection response is an RTSP OPTIONS response.

8. The method according to claim 6 or 7, characterized in that the method further comprises:

receiving the session identifier sent by the first WFD device in a P2P connection establishment phase before the reconnection;

locally saving the received session identification;

in the session establishment stage before reconnection, after performing capability negotiation with the first WFD device, storing a correspondence between the session identifier and the parameter set after the capability negotiation.

9. The method of claim 8, wherein the received session identifier is carried in a join/reconnect request frame;

accordingly, the session identification is extracted from the join/reconnect request frame.

10. A first WFD device, wherein the first WFD device comprises: a first transmitting unit and a first receiving unit; wherein,

the first sending unit is used for sending the reconnection identifier and the corresponding session identifier to the second WFD device when reconnection is needed; the reconnection identifier is used for indicating that the current connection of the second WFD equipment is reconnection; the session identifier is used for indicating the second WFD device to acquire a parameter set after capability negotiation corresponding to the session identifier; the session identifier is a session identifier for identifying the uniqueness of connection; the second WFD equipment is receiving end equipment of the first WFD equipment;

the first receiving unit is configured to receive a reconnection response returned by the second WFD device; the reconnect reply is indicative of a successful reconnection.

11. The device of claim 10, wherein the first WFD device further comprises: a second sending unit, configured to send the session identifier to the second WFD in the P2P connection establishment phase before reconnection.

12. The device of claim 11, wherein the first WFD device further comprises: a generating unit, configured to generate the session identifier before the P2P connection is established; and stores the session identification locally.

13. A second WFD device, wherein the second WFD device comprises: the device comprises a second receiving unit, a determining unit, a searching unit and a third sending unit; wherein,

the second receiving unit is configured to receive a reconnection identifier and a corresponding session identifier sent by the first WFD device; the second WFD equipment is receiving end equipment of the first WFD equipment; the session identifier is a session identifier for identifying the uniqueness of connection;

the determining unit is configured to determine, according to the reconnection identifier, that the connection with the first WFD device is reconnection;

the searching unit is used for locally searching the stored parameter set after the capability negotiation corresponding to the session identifier according to the session identifier;

the third sending unit is configured to send a reconnection response to the first WFD device after the successful search; the reconnect reply is indicative of a successful reconnection.

14. The device of claim 13, wherein the second WFD device further comprises: a third receiving unit and a storage unit; wherein,

the third receiving unit, configured to receive, in the P2P connection establishment phase before reconnection, the session identifier sent by the first WFD device;

the storage unit is used for locally saving the received session identifier; and in the session establishment stage before reconnection, after carrying out capability negotiation with the first WFD device, storing the corresponding relation between the session identifier and the parameter set after the capability negotiation.

15. A reconnecting system, characterized in that the system comprises: a first WFD device and a second WFD device; wherein,

the first WFD device is used for sending a reconnection identifier and a corresponding session identifier to the second WFD device when reconnection is needed; the session identifier is a session identifier for identifying the uniqueness of connection; receiving a reconnection response returned by the second WFD equipment;

the second WFD device is a data receiving end device of the first WFD device, and is configured to receive the reconnection identifier and the corresponding session identifier sent by the first WFD device; determining that the connection between the first WFD equipment is reconnection according to the reconnection identifier; according to the session identifier, locally searching a stored parameter set after capability negotiation corresponding to the session identifier; after the search is successful, sending a reconnection response to the first WFD equipment; the reconnect reply is indicative of a successful reconnection.