CN106941732A

CN106941732A - Reconnection method, system and WFD equipment

Info

Publication number: CN106941732A
Application number: CN201610004338.3A
Authority: CN
Inventors: 田康
Original assignee: China Mobile Communications Group Co Ltd
Current assignee: China Mobile Communications Group Co Ltd
Priority date: 2016-01-04
Filing date: 2016-01-04
Publication date: 2017-07-11
Anticipated expiration: 2036-01-04
Also published as: CN106941732B

Abstract

The invention discloses a kind of reconnection method, including：When needing to reconnect, the first WFD equipment sends to the 2nd WFD equipment and reconnects mark and corresponding session identification；The mark that reconnects is used to indicate the 2nd WFD equipment this is connected as reconnecting；The session identification is used for the parameter set for indicating that the 2nd WFD equipment is obtained after capability negotiation corresponding with the session identification；The session identification connects the session identification of uniqueness for mark；The 2nd WFD equipment is the receiving device of the first WFD equipment；Receive the 2nd WFD equipment return reconnects response；The response sign that reconnects reconnects success.The present invention also discloses a kind of first WFD equipment, the 2nd WFD equipment and reconnect welding system.

Description

Reconnection method, reconnection system and WFD (Windows presentation device)

Technical Field

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

Background

The Wi-Fi Direct (WFD) project newly published by the Wi-Fi alliance can enable a wireless fidelity card on a notebook computer of a user to bypass an access point and be directly connected to a wireless printer, a digital camera, a projector, a sensor or a plasma screen and the like. Accordingly, a device capable of directly implementing these functions is called a WFD device.

In the process of performing the same screen process or audio and video transmission between WFD devices, a case of device switching or device failure disconnection requiring reconnection may be encountered, and at this time, two WFD devices need to perform information interaction, such as device and capability negotiation, from the beginning of device discovery, that is, a process of connecting newly discovered devices is implemented. Thus, the time required for reconnection is relatively long, and the connection speed is greatly reduced.

Disclosure of Invention

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

In order to achieve the above purpose, the technical solution of the embodiment of the present invention is realized as follows:

the embodiment of the invention provides a reconnection method, which is applied to first WFD equipment and comprises the following steps:

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.

In the foregoing solution, the reconnection identifier and the corresponding session identifier are carried in an option request message of Real Time Streaming Protocol (RTSP), where the RTSP option 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.

In the above scheme, the method further comprises:

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

In the above scheme, the session identifier sent to the second WFD device is carried in the attach/reconnect request frame.

In the above scheme, the method further comprises:

generating the session identifier before the P2P connection is established;

storing the session identification locally.

The embodiment of the invention also provides a reconnection method, which is applied to second WFD equipment and comprises the following steps:

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.

In the above solution, the reconnection identifier and the corresponding session identifier are carried in an RTSP OPTIONS request message, where 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.

In the above scheme, 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.

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

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

An embodiment of the present invention further provides a first WFD device, including: 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.

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

In the foregoing solution, the first WFD device further includes: a generating unit, configured to generate the session identifier before the P2P connection is established; and stores the session identification locally.

The embodiment of the present invention further provides a second WFD device, including: 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.

In the foregoing solution, the second WFD device further includes: 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.

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 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.

According to the reconnection method, the system and the WFD equipment provided by the embodiment of the invention, when reconnection is needed, the first WFD equipment sends the reconnection identification and the corresponding session identification to the second WFD equipment; the session identifier is a session identifier for identifying the uniqueness of connection; the second WFD equipment is the data receiving end equipment of the first WFD equipment, and receives the reconnection identifier and the corresponding session identifier sent by the first WFD equipment; 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 reconnection response represents that reconnection is successful, and because during reconnection, the second WFD device only determines that the connection is reconnection according to the received reconnection identifier and only searches the corresponding parameter set after capability negotiation according to the session identifier, the message interaction process in the WFD capability negotiation stage is omitted, so that the connection speed is greatly increased, and the reconnection process can be accelerated.

Drawings

In the drawings, which are not necessarily drawn to scale, like reference numerals may describe similar components in different views. Like reference numerals having different letter suffixes may represent different examples of similar components. The drawings illustrate generally, by way of example, but not by way of limitation, various embodiments discussed herein.

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

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

FIG. 3 is a flowchart illustrating a first WFD-side reconnection method according to an embodiment of the present invention;

FIG. 4 is a flowchart illustrating a second WFD-side reconnection method according to an embodiment of the present invention;

FIG. 5 is a flowchart illustrating a reconnection method according to an embodiment of the invention;

FIG. 6 is a diagram of a second WFD structure according to a second embodiment of the present invention;

FIG. 7 is a diagram of a second WFD according to a second embodiment of the present invention;

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

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples.

Prior to describing embodiments of the present invention, a detailed understanding of the present related art will be provided.

As shown in fig. 1, the process of establishing a connection between two WFD devices mainly includes: WFD device discovery procedure, WFD connection establishment procedure, and capability negotiation procedure (i.e., session establishment procedure). In addition, a WFD service discovery process may be further included. In practical applications, the WFD service discovery process is not necessarily performed, and whether the WFD service discovery process needs to be performed may be determined according to service requirements.

The Information exchanged in the above processes all includes WFD Information (Information) Identification (ID) (i.e., WFD Information Element (IE)), for example, the data structures of the beacon (beacon) packet, probe request (probe request), and probe response (probe response) messages sent by the WFD devices for connection all include WFD IE. Some basic information carried by the WFD IE may enable an optimal connection between two devices.

Meanwhile, fig. 2 shows a process of performing session connection between WFD devices, that is, a WFD capability Negotiation stage (WFD capabilities Negotiation), which may also be referred to as a WFD device both-side capability information interaction process, in which case, the WFD device is referred to as a miracast device. As shown in fig. 2, the process includes the steps of:

step 201: a Source device sends an M1 request message to a Sink device;

in other words, an RTSP OPTIONS request message is sent to obtain the RTSP method set supported by the Sink device.

Step 202: and after receiving the M1 request message, the Sink device sends an M1 response message.

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

in other words, an RTSP OPTIONS request message is sent to obtain the RTSP method set supported by the Source device.

Step 204: the Source equipment sends an M2 response message to the Source equipment after receiving the M2 request message;

step 205: after the M2 response message is successfully sent, the Source equipment sends an M3 request message to Sink equipment;

in other words, a RTSP PARAMETER GET (GET _ PARAMETER) request message is sent to GET the WFD capability list of the Sink device interested in itself.

The specific content of the WFD capability list may include an audio format, a video format, several resolutions (e.g., 1080p, 720p, 480p, etc.), a corresponding frame rate, and a supported content protection method.

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 setup PARAMETER (SET _ PARAMETER) request message, i.e., an M4 request message, to the Sink device, so as to enable the Sink device to SET the corresponding PARAMETERs.

Step 208: after receiving the M4 request message, the Sink device replies 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, a RTSP SET _ PARAMETER-request message is sent for triggering the functions of subsequent connection establishment, playing, and the like.

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 a positive message reply, the Source device sends an M6 request message to the Sink device;

in other words, an RTSP SETUP (SETUP) request message is sent, which carries the message content of the connection SETUP function.

Step 212: after receiving the request message of M6, 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 an M7 request message to the Sink device;

in other words, a RTSP setup (PLAY) request message is sent, and the message carries the message content of the functions such as connection PLAY.

Step 214: after receiving the request message of M7, the Sink device replies an M7 response message to the Source device.

When the M7 response message is received and the response message is a positive message reply, the session connection process between the WFD devices is completed. After the transmission is finished, the same frequency or audio/video transmission process can be carried out between the Source equipment and the Sink equipment.

In the process of performing on-screen or audio-video transmission between WFD devices, on one hand, a problem of device switching is often encountered, for example, it is assumed that a device a and a device B are connected, and then the device a and the device C are switched to be connected, but then the device B may be switched to, and in this process, reconnection is performed between the device a and the device B; on the other hand, the problem of disconnection and reconnection of the network fault can also exist; under these circumstances, in the prior art, the RTSP negotiation needs to be performed again, that is, the steps 201 to 214, that is, the steps of the M1-M7 related process in miracast, need to be performed again. Thus, the connection speed is greatly reduced, thereby reducing the user experience.

Based on this, in various embodiments of the invention: when reconnection is needed, the first WFD equipment sends reconnection identification and corresponding session identification to the second WFD equipment; the session identifier is a session identifier for identifying the uniqueness of connection; the second WFD equipment receives a reconnection identifier and a corresponding session identifier sent by the first WFD equipment; 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.

Wherein the second WFD device is a data sink device of the first WFD device.

Example one

The embodiment provides a reconnection method, which is applied to a first WFD device, and as shown in fig. 3, the method includes the following steps:

step 301: when reconnection is needed, the first WFD equipment sends reconnection identification and corresponding session identification to the second WFD equipment;

here, the reconnection flag is used to indicate that the current connection of the second WFD device is reconnection and not new connection; 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 the connection.

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

The timing of reconnection is as follows: the first WFD device needs to be reconnected for switching or device failure disconnection.

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

In other words, the reconnection flag and the corresponding session flag may be carried in the M1 request message shown in fig. 2.

At this time, the contents carried in the M1 request message are as 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 an M1 request message sent by the first WFD device to the second WFD device; from Sink to Source represents an M1 reply message sent by the second WFD device to the first WFD device. The purpose of sending the M1 reply message is to: and the first WFD device is informed of the success of reconnection.

In actual application, before reconnection, the first WFD device and the second WFD device need to set and store the session identifier for subsequent processing.

Based on this, the method may further comprise:

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

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

Here, the P2P connection establishment phase refers to the WFD connection establishment procedure in fig. 1.

The Association/conversation Request Frame carries the session identifier, which can be implemented according to the following method:

since some basic information carried in the WFD IE may enable the two devices to be optimally connected, in order to implement a Session identifier unique to the connection between the two WFD devices, WFD sub-elements (fragments) in the WFDIE may be extended, so that the WFD sub-elements include the content of the Session identifier (Session ID), and the specific content of the extension may be the content shown in table 2 with a Session ID of 11.

TABLE 2

Meanwhile, in order to enable the two WFD devices performing the connection to set and store the session identifier (SessionID), the content needs to be extended in the Association/Reassociation Request Frame and the Association/Reassociation Response Frame sent in the device connection establishment phase. The specific content expanded in the Association/responsiveness Request Frame may be the content shown in the row corresponding to the Session ID as mentioned in table 3, and the specific content expanded in the Association/responsiveness response Frame may be the content shown in the row corresponding to the Session ID as mentioned in table 4.

TABLE 3

TABLE 4

Wherein, the Association/conversation Response Frame carries the session identifier (SessionID) with the following functions: and making the first WFD device know that the second WFD device receives the session identification.

In an embodiment, the method may further comprise:

generating the session identifier before the P2P connection is established;

storing the session identification locally.

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

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

Here, after receiving the reconnection identifier and the corresponding session identifier, the second WFD device learns that the connection is reconnection according to the reconnection identifier, and thus locally searches a stored parameter set after capability negotiation corresponding to the session identifier; and after finding the corresponding parameter set, sending a reconnection response to the first WFD device, and when the reconnection identifier and the corresponding session identifier are carried in the M1 request message, the second WFD device returning an M1 response message to the first WFD device, that is, the reconnection response is an RTSP OPTIONS response.

When the second WFD device cannot find the corresponding parameter set locally, i.e. when the search fails, the second WFD device performs 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 identifier (Session ID) is different from a general device identifier, and is more like a manager (Handler), and the Session identifier associates parameter sets after capability negotiation between WFD devices in a call process, and the second WFD device may realize a quick reconnection effect just by associating the parameter sets.

The embodiment further provides a reconnection method, which is applied to the second WFD device, and as shown in fig. 4, the method includes the following steps:

step 401: receiving a reconnection identifier and a corresponding session identifier sent by first WFD equipment;

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

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

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

Based on this, the method may further comprise:

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

locally saving the received session identification;

in the session establishment stage before 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.

The session identifier received by the second WFD device may be carried in the Association/reaction Request Frame;

accordingly, the second WFD device extracts the session identifier from the Association/conversation Request Frame.

because some basic information carried in the WFD IE may enable the two devices to be optimally connected, in order to implement connection of a unique Session identifier between the two WFD devices, WFD sub-components in the WFDIE may be extended, so that the WFD sub-components include the content of the Session identifier (Session ID), and the specific content of the extension may be the content shown in table 2 with a sub-ID of 11.

Meanwhile, in order to enable the two WFD devices performing the connection to set and store the session identifier (SessionID), the content needs to be extended in the Association/Reassociation Request Frame and the Association/Reassociation Response Frame sent in the device connection establishment phase. The specific content expanded in the Association/reactionrequest Frame may be the content shown in the row corresponding to the Session ID as the tokens in table 3, and the specific content expanded in the Association/reactionresponse Frame may be the content shown in the row corresponding to the Session ID as the tokens in table 4.

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

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

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

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

It should be noted that: the Session identifier (Session ID) is different from a general device identifier, and is more like a Handler, and the Session identifier associates a parameter set after capability negotiation between WFD devices in a call process, and the second WFD device may realize a quick reconnection effect just by associating the parameter set.

The embodiment further provides a reconnection method, as shown in fig. 5, the method includes the following steps:

step 501: when reconnection is needed, the first WFD equipment sends reconnection identification and corresponding session identification to the second WFD equipment;

Step 502: the second WFD equipment receives a reconnection identifier and a corresponding session identifier sent by the first WFD equipment; 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;

here, the reconnection acknowledgement indicates that reconnection was 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 are not described herein again.

According to the reconnection method provided by the embodiment of the invention, when reconnection is needed, the first WFD equipment sends the reconnection identifier and the corresponding session identifier to the second WFD equipment; the session identifier is a session identifier for identifying the uniqueness of connection; the second WFD equipment is the data receiving end equipment of the first WFD equipment, and receives the reconnection identifier and the corresponding session identifier sent by the first WFD equipment; 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 reconnection response represents that reconnection is successful, and because during reconnection, the second WFD device only determines that the connection is reconnection according to the received reconnection identifier, and only searches the corresponding parameter set after capability negotiation according to the session identifier, the message interaction process in the WFD capability negotiation stage is omitted, so that the connection speed is greatly increased, the reconnection process can be accelerated, the user experience is improved, and the practicability of WFD device interconnection is improved.

Example two

To implement the method of the embodiment of the present invention, the embodiment provides a first WFD device, as shown in fig. 6, where the first WFD device includes: a first transmitting 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 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 first receiving unit 62 is configured to receive a reconnection response returned by the second WFD device; the reconnect reply is indicative of a successful reconnection.

Wherein the second WFD device is a sink device of the first WFD device. In other words, the first WFD device is a sender device, and the second WFD device is a receiver device. That is, multimedia data is sent by the first WFD device, and multimedia data sent by the first WFD device is received by the second WFD device.

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 in the P2P connection establishment phase before reconnection.

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

since some basic information carried in the WFD IE may enable the two devices to be optimally connected, in order to implement a Session identifier unique to the connection between the two WFD devices, WFD sub-components) in the WFDIE may be extended, so that the WFD sub-components include the content of the Session identifier (Session ID), and the specific content of the extension may be the content shown in table 2 with a sub-ID of 11.

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

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

After receiving the reconnection identifier and the corresponding session identifier, the second WFD device learns that the connection is reconnection according to the reconnection identifier, and therefore locally searches a stored parameter set after capability negotiation corresponding to the session identifier; and after finding the corresponding parameter set, sending a reconnection response to the first WFD device, and when the reconnection identifier and the corresponding session identifier are carried in the M1 request message, the second WFD device returning an M1 response message to the first WFD device, that is, the reconnection response is an RTSP OPTIONS response.

In practical application, the first sending Unit 61, the first receiving Unit 62 and the second sending Unit may be implemented by a Central Processing Unit (CPU), a Micro Control Unit (MCU), a Digital Signal Processor (DSP), or a Programmable logic Array (FPGA) in the first WFD device in combination with a transceiver; the generating unit can be realized by a CPU, an MCU, a DSP or an FPGA in the first WFD device.

To implement the method of the embodiment of the present invention, this embodiment further provides a second WFD, as shown in fig. 7, where the second WFD device includes: a second receiving unit 71, a determining unit 72, a searching unit 73 and a third sending unit 74; wherein,

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

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

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

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

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

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

Here, when the second receiving unit 71 acquires the reconnection flag and the corresponding session flag through the M1 request message, and after the parameter set is successfully searched, the third sending unit 74 returns an M1 response message to the first WFD device, that is, the reconnection response is an RTSP OPTIONS response.

When the search unit 73 cannot find the corresponding parameter set locally, that is, when the search fails, the complete process shown in fig. 2 is performed with the first WFD device to complete the session establishment process.

In practical application, the second receiving unit 71, the third sending unit 74, and the third receiving unit may be implemented by a transceiver combined with a CPU, an MCU, a DSP, or an FPGA in the second WFD device; the determining unit 72, the searching unit 73 and the storing unit can be implemented by a CPU, MCU, DSP or FPGA in the second WFD device.

To implement the method of the embodiment of the present invention, this embodiment further provides a reconnection system, as shown in fig. 8, where 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 for identifying the uniqueness of connection; receiving a 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, and is configured to receive the reconnection identifier and the corresponding session identifier sent by the first WFD device 81; determining that the connection with the first WFD device 81 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 device 81; the reconnect reply is indicative of a successful reconnection.

It should be noted that: the specific processes of the first WFD device 81 and the second WFD device 82 have been described in detail above, and are not described herein again.

According to the scheme provided by the embodiment of the invention, when reconnection is needed, the first WFD equipment sends the reconnection identification and the corresponding session identification to the second WFD equipment; the session identifier is a session identifier for identifying the uniqueness of connection; the second WFD equipment is the data receiving end equipment of the first WFD equipment, and receives the reconnection identifier and the corresponding session identifier sent by the first WFD equipment; 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 reconnection response represents that reconnection is successful, and because during reconnection, the second WFD device only determines that the connection is reconnection according to the received reconnection identifier, and only searches the corresponding parameter set after capability negotiation according to the session identifier, the message interaction process in the WFD capability negotiation stage is omitted, so that the connection speed is greatly increased, the reconnection process can be accelerated, the user experience is improved, and the practicability of WFD device interconnection is improved.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may 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, optical storage, and the like) 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 will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims

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

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:

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;

the reconnection response is an RTSP OPTIONS response.

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

locally saving the received session identification;

9. The method of claim 8, wherein the received session identifier is carried in a 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,

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,

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

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