Primary protocol stack having a secondary protocol stack entry point

A terminal device and its used protocol stack structure and operation method

The present invention relates to packet data communication, and more specifically, to the transmission of data packets at two communication incompatible (communicatively incompatible) protocol stack layers executed on end devices.

Notebook computers, personal computers, video game consoles, personal digital workhorses, headsets, telephones, set-top boxes, servers, and many other types of end point devices (EPD) can be communicatively connected to more than one packet-switched data network. These packet-switched data networks can operate according to communication incompatible protocols. Examples of packet-switched data networks include EDGE (Enhanced Data Rate GSM Evolution) networks, GSM (Global System for Mobile Communications) networks, CDMA (Code Division Multiple Access) networks, IEEE (Institute of Electrical and Electronic Engineers) 802.11 networks , Bluetooth, WiMax network, Internet, corporate intranet, satellite network, etc.

A typical EPD with two communication interfaces can be used to operate according to two communication incompatible protocols. These two agreements follow a multi-layer stacking architecture. Of the two communication interfaces, the first communication interface uses the first protocol of the two protocols to exchange packet data with the second EPD through one or more packet-switched data networks; the second communication interface uses the two protocols The second protocol in the protocol exchanges packet data with the second EPD through one or more packet-switched data networks. The EPD that has used the first communication interface to exchange packet data with the second EPD can decide to use the second communication interface instead of using the first communication interface to exchange packet data with the second EPD. In this case, the EPD needs to re-establish a communication session that completely penetrates all layers of the second protocol stack. The re-establishment of this communication session exchanges a large amount of information between the layers of the second stack, which is time-consuming.

Comparing the system of the present invention which will be introduced later in conjunction with the drawings, other limitations and drawbacks of the prior art will be obvious to those of ordinary skill in the art.

The present invention relates to a protocol stack. The protocol stack allows unrelated protocol stacks to communicate with it, thereby allowing the establishment of communication sessions that are partly in the protocol stack and partly in the unrelated protocol stack. In the following, at least one attachment will be combined. The figure gives a description, and a more complete description is given in the claims. The present invention also relates to a terminal device in which both the protocol stack and the unrelated protocol stack can be executed.

According to an aspect of the present invention, there is provided an end device that can selectively communicate with a first access point and a second access point, the first access point uses a first protocol to manage communication, and the second access point Use a second protocol to manage communications, the first protocol is incompatible with the second protocol, the end device includes: a first protocol stack, the first protocol stack includes at least a first application layer, a first intermediate layer, and The first physical layer, the first physical layer supports packet data communication using the first protocol and the first access point; the second protocol stack, the second protocol stack includes at least a second intermediate layer and A second physical layer, the second physical layer supports packet data communication with the second access point using the second protocol; the first application layer of the first protocol stack passes from the first application Layer to the first access point and via a first communication path from the first intermediate layer and the first physical layer to establish a communication session, the communication session having at least one parameter determined when the communication session is established And a processing circuit, the processing circuit responds to changes in communication characteristics, while maintaining the at least one session parameter, by providing a bridge between the first intermediate layer and the second intermediate layer, so as to pass the The first intermediate layer, the second intermediate layer, and the second physical layer establish a second communication path between the first application layer and the second access point to reroute communication flows.

Preferably, the execution of the rerouting does not require the assistance of the first application layer.

Preferably, the change in the communication characteristics indicates that the second communication path is at least better than the first communication path.

Preferably, the first intermediate layer includes a plurality of intermediate layers, the processing circuit selects the first layer among the plurality of intermediate layers, and the bridge is established between the first layer and the second layer Between layers.

Preferably, the at least one session parameter includes an encryption parameter.

Preferably, the rerouting performed by the processing circuit does not require reestablishment of the communication session.

According to one aspect of the present invention, there is provided a protocol stacking architecture used in a device, having a first physical layer for communicating with a first access point and a second physical layer for communicating with a second access point, wherein the The first access point and the second access point are both communicatively connected to the packet-switched network, the protocol stacking structure includes: an application layer; a first protocol stacking structure, the first protocol stacking structure includes supporting the application layer and A first intermediate layer of the first communication path between the first physical layers; a second protocol stacking structure, the second protocol stacking structure including a second intermediate layer communicatively connected to the second physical layer; A bridge between the first intermediate layer of the first agreement stack structure and the second intermediate layer of the second agreement stack structure, the bridge being supported by the first intermediate layer and the second intermediate layer A second communication path between the application layer and the second physical layer; and a bridge manager that selects and enables the bridge to communicate between the first communication path and the second communication path To switch between.

Preferably, the bridge manager activates the bridge in response to a significant change in the performance of the first communication path.

Preferably, a communication session using at least one session parameter is established to the application layer through the first communication path, and the at least one session parameter will be maintained in the second communication path.

Preferably, the at least one session parameter includes an encryption parameter.

Preferably, the at least one session parameter includes a login parameter.

Preferably, the at least one session parameter includes a billing parameter.

Preferably, the at least one session parameter includes an association parameter.

According to an aspect of the present invention, there is provided an end device that can selectively communicate with a first access point and a second access point, wherein the first access point uses a first protocol to manage communication, and the second access point Use a second protocol to manage communications. The first protocol and the second protocol are incompatible. The end device includes: a first protocol stack, and the first protocol stack includes at least a first application layer, a first intermediate layer, and The first physical layer, the first physical layer supports packet data communication using the first protocol and the first access point; the second protocol stack, the second protocol stack includes at least a second intermediate layer and A second physical layer, where the second physical layer supports packet data communication with the second access point using the second protocol; a bridge that connects the first intermediate layer and the second intermediate layer for communication; Bridge manager, the bridge manager responds to the communication characteristics, supports originating from the first application layer, passes through the first intermediate layer, the bridge, and the second intermediate layer, and reaches the second physical layer The first packet data flow; and the bridge manager responds to the communication characteristics, and also supports entry through the second physical layer, passing through the second intermediate layer, the bridge, and the first intermediate layer to reach the The second data grouping process of the first application layer is described.

Preferably, the communication characteristic is a load factor of the first physical layer.

Preferably, the communication characteristic is an unacceptable communication flow through the first physical layer.

According to one aspect of the present invention, there is provided a protocol stack structure used in a device supporting communication applications, the device having a first communication interface circuit and a second communication interface circuit, and the protocol stack structure includes: The application layer of a communication application; a first physical layer including the first communication interface circuit; a plurality of first intermediate layers, and the plurality of first intermediate layers together provide the application layer and the first physical layer The communication application program establishes communication through the first communication path, and generates at least one parameter as part of establishing communication; a second physical layer including the second communication interface circuit; and At least one second intermediate layer connected to the second physical layer; the at least one second intermediate layer supports the communication application through at least one of the plurality of first intermediate layers, the At least one second intermediate layer reaches the second communication path of the second physical layer.

Preferably, the plurality of first intermediate layers, the first physical layer and the application layer jointly constitute a first protocol stack.

Preferably, the at least one second intermediate layer is part of a second agreement stack.

Preferably, the first protocol stack has a bridge access point to support the second communication path.

Preferably, the first protocol stack has a plurality of bridge access points to support the second communication path.

According to an aspect of the present invention, there is provided a method executed by a device having a first wireless physical protocol stacking layer and a second wireless physical protocol stacking layer, the device having a communication application protocol stacking layer, and the method includes: The intermediate protocol stacking layer establishes a first data path between the communication application protocol stacking layer and the first wireless physical protocol stacking layer; exchanging parameters through the first data path as part of establishing the first data path Exchanging the first part of the data packet through the first data path; and using the parameters to establish a second data path, the second data path starting from the communication application protocol stacking layer and passing through the first intermediate protocol The bridge between the stacking layer and the second intermediate protocol stacking layer connected to the second wireless physical protocol stacking layer reaches the second wireless physical protocol stacking layer.

Preferably, the method further includes detecting a significant change in at least one communication characteristic, and establishing the second data path in response to the detection.

Preferably, the parameters include session parameters.

Preferably, the bridge has multiple entry points.

The various advantages, various aspects and innovative features of the present invention, as well as the details of the embodiments exemplified therein, will be described in detail in the following description and drawings.

FIG. 1 is a schematic block diagram of a communication network 101 of end devices (EPD) 151, 153, and 155 and access points (AP) 121, 123, 125, and 127. Among them, each of the end devices 151, 153, and 155 adopts the first protocol stack having an entry point provided to the second protocol stack. The end device supports communication with an access point using the first protocol, and supports communication with another access point using the second protocol. EPDs 151, 153, and 155 can be notebooks, video game consoles, servers, personal computers, telephones, personal digital assistants (PDAs), and so on. The first AP 121 and the second AP 123 are communicatively connected to the terrestrial cellular network 105. Typically, the terrestrial cellular network 105 is a CDMA, HSDAP, GSM, EDGE, GPRS network, etc. In addition to being communicatively connected to the satellite data network 109, the third AP 125 is also connected to the wireless data network 107. The wireless data network 107 may be a WiFi network, a WiMax network, a Bluetooth network, and the like. The fourth AP 127 is communicatively associated with the wired data network 111. For example, the wired data network 111 may be a PSTN network, a cable data network, or an optical fiber data network. In EPD 151, 153, and 155, each EPD is used to communicate with more than one AP 121, 123, 125, and 127 exchange data, and each EPD supports data communication with their associated APs that use more than one data communication protocol. For example, the EPD 151 exchanges data with the first AP 121 using the first protocol 131, the third AP 125 using the second protocol 133, and the fourth AP 127 using the fourth protocol 137. If the cellular network 105 is a CDMA network, then the first protocol 131 is a CDMA protocol. Similarly, the second protocol 133 and the fourth protocol 137 are protocols used by the APs 125 and 127 to communicate with the wireless data network 107 and the wired data network 111, respectively. The data includes real-time and/or archived information, such as videos, audios, video games, films, TV shows, music shows, images, and any multimedia information. An AP is a transceiver that exchanges data with one or more associated downstream EPDs (151, 153, and 155) and exchanges data with one or more upstream data networks (105, 107, 109, and 111). The uplink data networks 105, 107, 109, and 111 are communicatively connected through the backbone network 103.

For example, the first EPD 151 is used to operate according to three types of agreements, namely, the first agreement 131, the second agreement 133, and the fourth agreement 137. These three agreements can be communication incompatible. Each of these three protocols uses a stacking architecture. The communication application program running on the first EPD 151 (and any one of EPD 151, 153, and 155) is the uppermost layer, that is, the seventh layer, or application layer, of the stack structure. The communication application can be, for example, an HTTP browsing application, an archived multimedia file download application, a video and/or audio streaming application, an Internet phone application, a phone call, a video game, and the like. The communication interface of the first EPD 151 is the lowest layer, that is, the first layer of the stack structure, or the physical layer (PHY layer). For example, a voice call is made between the first PED 151 and the third EPD 155. The first EPD 151 uses the first protocol 131 to send and receive voice data to and from the first AP 121. The first protocol stack 161 refers to the stack structure of the first protocol 131. The telephone call is made on the 7th layer of the first protocol stack 161, and the first communication interface (not shown in the figure) used by the first EPD 151 to communicate with the first AP 121 is the first layer of the first protocol stack 161.

Similarly, the second protocol stack 163 refers to the stack structure of the second protocol 133, and the third protocol stack 165 refers to the stack structure of the fourth protocol 137. The third EPD 155 uses the fourth protocol 137 to send and receive data to and from the fourth AP 127. The first protocol stack structure 181 used by the third EPD refers to the stack structure of the fourth protocol 137. The first EPD 151 establishes a first data path with the third EPD 155, and transmits voice calls, that is, voice data, through the first data path. The first data path passes through the layers of the first protocol stack 161, the first communication interface (not shown in the figure) of the first EPD 151 (the first layer of the protocol stack 161), the first AP 121, and the ground cellular network 105, the backbone network 103, the wired data network 111, the fourth AP 127, the third EPD 155, and all layers of the protocol stack 181. Before transmitting the voice data generated by the voice call application on the first EPD 151 to the first AP 121 through the first communication interface (not shown in the figure) of the first EPD 151, each of the first protocol stacks 161 The layer independently encrypts the voice data, and this encryption is performed according to the first protocol 131.

The first EPD 151 decides to send the voice data to the third EPD 155 through the second data path instead of the first data path. This decision can be made in response to the following situations: increased communication load of the first data path, removal of the first AP 121, higher data rate requirements, the second data path supports better QoS than the first data path, and the second data path supports better QoS than the first data path. An unacceptable delay on the data path, etc. For example, the second data path passes through all layers of the third AP 125, the wireless data network 107, the backbone network 103, the wired data network 151, the fourth AP 127, the third EPD 155, and the protocol stack 181. In one embodiment, some other nodes of the communication network 101 guide the first EPD 151 to use the second data path to transmit voice data.

The first EPD 151 is communicatively connected to the third AP 125 through a second communication interface (not shown in the figure). The second communication interface is the first layer or physical layer of the second protocol stack 163. The first EPD 151 communicates with the third AP 125 using the second protocol 133. Before sending the voice data generated by the voice call application running on the first EPD 151 through the second communication interface (not shown in the figure) of the first EPD 151, the voice data needs to be encrypted according to the second protocol. The decision made by the first EPD 151 to send voice data through the second data path instead of the first data path requires the termination of the voice call session through the first protocol stack 161, and the independent establishment of all layers of the second protocol stack 163 Voice call conversation.

In response to the above-mentioned situation, the bridge management module 167 of the first EPD 151 establishes a "bridge" between a layer of the first protocol stack 161 and a corresponding layer of the second protocol stack 163. In a non-limiting example, the bridge management module 167 establishes a bridge between the fourth layer of the first protocol stack 161, that is, the transport layer, and the fourth layer of the second protocol stack 163. In this way, the fourth layer of the first protocol stack 161 is communicatively connected to the fourth layer of the second protocol stack 163. The bridge management module 167 guides the voice data generated by the voice call application running on the 7th layer of the first protocol stack 161 through the 6th, 5th, and 4th layers of the first protocol stack 161, and bridges The fourth layer, the third layer and the second layer of the second protocol stack 163, the second communication interface of the first EPD 151, that is, the first layer of the second protocol stack 163. Then, the second communication interface transmits the voice data to the third AP 125, and finally reaches the third EPD 155 from the third AP 125. In this way, the second data path includes the seventh, sixth, fifth, and fourth layers of the first protocol stack 161, and the bridge, the fourth, third, and second layers of the second protocol stack 163. Layer and layer 1, and all layers of the third AP 125, wireless data network 107, backbone network 103, wired data network 151, fourth AP 127, third EPD 155, and protocol stack 181.

When the voice call is switched from the first data path to the second data path, the bridge management module 167 transmits at least one session parameter through the first data path to the second data path. For example, the at least one session parameter is an encryption parameter, a login parameter, a billing parameter, a correlation parameter, and so on.

In one embodiment, the fifth, sixth, and seventh layers of the second protocol stack 163, that is, the layers above the bridge in the second protocol stack 163, are not aware of bridging. The bridging between the 4th layer of the first protocol stack 161 and the 4th layer of the second protocol stack 163 does not require the re-establishment of the voice call session through all the layers of the second protocol stack 163. The fourth layer of the first protocol stack 161 and the fourth layer of the second protocol stack 163, that is, the participating layers exchange the secrets required to transmit data through some layers of the first protocol stack 161 and some layers of the second protocol stack 163. Keys and/or parameters, wherein the first protocol stack 161 complies with the first protocol 131, and the second protocol stack 163 complies with the second protocol 133. The first agreement 131 and the second agreement 133 may be incompatible in communication.

In another embodiment, the bridge is formed between the fifth layer (ie, the session layer) of the first protocol stack 161 and the fifth layer (ie, the session layer) of the second protocol stack 163. The bridge management module 167 is used to establish a bridge between any of the second, third, fourth, and fifth layers of the first protocol stack 161 and the corresponding layer of the second protocol stack 163. In another embodiment, the bridge management module 167 informs each layer above the participating layer in the second protocol stack 163 (the layer communicatively connected with the corresponding layer of the first protocol stack 161) of the bridge.

In another embodiment, the first EPD 151 uses all the layers of the first agreement stack 161 and the participating layer and the layers below the participating layer in the second agreement stack 181. In other words, the first EPD 151 uses all the layers of the first protocol stack 161 and a part of the layers of the second protocol stack 163, that is, the second protocol sub-stack. The bridge management module 167 can support half-duplex and/or full-duplex data exchange via the established bridge. Alternatively, the bridge management module 167 can guide the voice data to be transmitted through the bridge, that is, the second data path, and to receive data from the third EPD 155 through the first data path.

In some embodiments, the bridge management module 167 can guide the transmission of voice data through the first data path, and the transmission of commands and/or auxiliary data through the second data path. For example, the bridge management module 167 guides voice data (ie, data generated by a communication application running on the 7th layer of the first protocol stack 161) through the first communication interface of the first EPD 151 (not shown in the figure) ) Transmission, and at the same time guide the command data for the third EPD 155 to be transmitted through the second communication interface (not shown in the figure) of the first EPD 151. For example, a bridge is enabled between the third layer of the first protocol stack 161 and the third layer of the second protocol stack 163. Before the voice data is sent to the first AP 121 through the first communication interface (not shown in the figure) of the first EPD, that is, the first layer or physical layer of the first protocol stack 161, the voice data must flow through the first protocol Stack all layers of 161, and before sending command data to the third AP 125 through the second communication interface (not shown in the figure) of the first EPD 151, that is, the first layer or physical layer of the second protocol stack 163, The command data passes through the 7, 6, 5, 4, and 3 layers of the first protocol stack 161, the bridge, and the third and second layers of the second protocol stack 163.

In various variations of the above-mentioned invention, each layer of the first agreement stack 161 and each layer of the second agreement stack 163 includes a layer manager. For example, the layer manager corresponding to the fifth layer of the first protocol stack 161 is independent of the other layer managers of the first protocol stack 161, and independently determines whether to enable the bridge to the fifth layer of the second protocol stack 163. Once the decision is made, the fifth layer of the first protocol stack 161 attempts to establish a bridge with the fifth layer of the second protocol stack 163. The fifth layer of the first and second protocol stacks can jointly choose to enable a bridge between them.

In addition, the first EPD 151 also supports the fourth protocol 137, and executes all the layers and/or part of the layers of the third protocol stack 165. In addition, the bridge management module 167 supports bridges between corresponding layers of the first protocol stack 161 and the third protocol stack 165. Generally speaking, the corresponding layers of the two protocol stacks with bridges are the sixth, fifth, fourth, and third layers of the first protocol stack 161 and the third protocol stack 165.

Fig. 2 is a schematic block diagram of an end device shown in Fig. 1. The end device 201 supports half-duplex bridging between the first protocol stack and the second protocol stack. The first protocol stack supports a first radio device (primary radio) 227, and the second protocol stack supports a second radio device (secondary radio). )281. The first protocol stack includes seven layers, namely the first application layer 203, the first presentation layer 205, the first session layer 207, the first transport layer 209, the first network layer 211, the first data link layer 213, and the first Physical layer 227. The first data link layer 213 includes a first logical link control layer 215 and a first medium access control layer 217. The first radio 227 is part of the first physical layer 227. The first radio 227 and the first physical layer 227 refer to the same entity. The second protocol stack includes a second session layer 261, a second transport layer 263, a second network layer 265, a second logical link control layer 267, and a second medium access control layer 269. The second radio 281 is part of the second physical layer of the second protocol stack.

The session layer bridge 241 unidirectionally connects the first session layer 207 and the second session layer 261, that is, between the first session layer 207 of the first protocol stack and the second session layer 261 of the second protocol stack Establish a half-duplex communication link. Similarly, the transmission layer bridge 243 establishes a half-duplex communication path between the first transmission layer 209 and the second transmission layer 263. The network layer bridge 245 and the logical link control (LLC) layer bridge 247 respectively connect the network layer and LLC layer of the first protocol stack to the network layer and LLC layer of the second protocol stack. If the first protocol stack corresponds to a wireless protocol, such as WiFi, WiMax, Bluetooth, CDMA, GSM, GPRS, EDGE, WCDMA, etc., then the first radio device 227 is a wireless radio device. If the first protocol stack corresponds to a wired protocol, such as a cable data protocol, an optical fiber data protocol, etc., then the first radio device 227 is a wired radio device. Similarly, according to the type of the second agreement, the second radio 281 may be wired or wireless. In one embodiment, the first agreement and the second agreement are communication incompatible.

The EPD 201 is communicatively connected to multiple EPDs through a packet-switched backbone network. The EPD 201 has a first radio device 227 and a second radio device 281, and can exchange data packets with two different EPDs at the same time using the first protocol and the second protocol, respectively. The EPD 201 chooses to use the first radio device 227 to transmit data packets generated by the communication application program running on the first EPD 201. Similarly, the first radio device 227 is selected by default to receive data packets required by the communication application program. The radio device 227 therefore refers to the first radio device. Under certain circumstances, for example, in the case of sending auxiliary information, command data, test data, etc. to the backbone network and/or other EPDs, when the load of the first radio device 227 exceeds a certain threshold, the first radio device 227 When the data packet generated by the application program is sent when the path through the first radio device 227 cannot support the required quality of service, etc., the EPD 201 uses the second radio device 281 to perform packet data communication.

Among the plurality of bridge management modules, each bridge management module corresponds to one of the layer bridges 241, 243, 245, and 247. These multiple bridge management modules independently and/or cooperatively determine whether to enable the bridge between the two communication connection layers of the first protocol stack and the second protocol stack. If they decide to enable it, then decide to enable the layer bridge 241, Which layer of 243, 245, and 247 is the bridge? At the specified time, only one of the layer bridges 241, 243, 245, and 247 can be used. Each bridge management module collects information from the layer directly below it, and makes a decision to enable the bridge based on the collected information.

For example, the bridge management module corresponding to the session layer bridge 241 collects information from the first MAC layer 217 and the first radio device 227, and decides to activate the session layer bridge 241 based on the collected information. The collected information generally includes the load on the first radio device 227, the queue length corresponding to the data packet waiting to be sent on the first radio device 227, the quality of the communication path connected to the first radio device 227, and so on. In one embodiment, the bridge management module corresponding to the session layer bridge 241 is only communicatively connected to the first session layer 207. In this case, the bridge management module corresponding to the session layer bridge 241 collects information through the first transport layer 209, the first network layer 211, and the first LLC layer 215. Once the session layer bridge 241 is enabled, the bridge management module corresponding to the session layer bridge 241 notifies the decision to the remaining bridge management modules, and then guides the communication application program, the first protocol stack Data packets generated by an application layer are transmitted through the session layer bridge 241. In this case, the data packet passes downward through the first presentation layer 205 and the first session layer 207, and reaches the session layer bridge 241. Starting from the session layer bridge 241, the data packet is sent down through the second session layer 261, the second transport layer 263, the second network layer 265, the second LLC layer 267, and the second MAC layer 269, and finally reaches the second radioDevice281. Device 281. The second radio device 281 sends the data packet to the target node. The bridge management module corresponding to the session layer bridge 241 ensures that the session parameters corresponding to the ongoing communication session using the first radio device 227 are maintained when the communication session is switched to the second radio device 281. For example, the session parameters are encryption parameters, login parameters, billing parameters, correlation parameters, and so on.

Once the session layer bridge 241 between the session layers of the two protocol stacks is established, the data packet will pass through the layers above the first session layer 207 in the first protocol stack, the first session layer 207, the session layer bridge 241, and the first session layer. The second session layer 261 and the layers below the second session layer 261 in the second protocol stack. Once the session layer bridge 241 is enabled, the first session layer 207 and the second session layer 261 exchange session information, such as login information, between them. The second session layer 261 needs the session information to support packet data communication via a part of the second protocol stack. Enabling the session layer bridge 241 can eliminate the need for the EPD 201 to re-establish a communication session involving all layers of the second protocol stack. Re-establishing a communication session is usually time-consuming. The bridge management module corresponding to the session layer bridge 241 may choose not to notify the packet data communication via the session layer bridge 241 to the layers above the second session layer 261 of the second protocol stack. The EPD 201 may choose not to execute the layers above the second session layer 261 in the EPD circuit. In this case, as long as the EPD When 201 decides to use the second radio device 281 for packet data communication, the second protocol stack (ie, sub-stack) does not include the application layer, and any one of the bridges 241, 243, 245, and 247 will be activated. Similarly, if the transport layer bridge 243 is enabled, then the first transport layer 209 and the second transport layer 263 exchange transport layer information between them, such as TCP-related parameters, TCP window length, and so on.

In another embodiment, the EPD 201 does not have multiple bridge management modules corresponding to the layer bridges 241, 243, 245, and 247, but has only one bridge management module for determining and controlling the first protocol stack and the first protocol stack. Second, the bridging between the layers of the protocol stack communication connection. In another embodiment, the single bridge management module and/or multiple bridge management modules control the first data flow path and the second data flow path while maintaining the first data flow path through the first protocol All layers of the stack are from the first communication application 203 to the first radio device 227, and the second data flow path is from the first communication application 203 to the second radio device 281 via the enabled bridge. The first data flow path transmits a part of the data packets, and the second data flow path transmits the remaining part of the data packets. When dividing the communication load between the first radio device 227 and the second radio device 281 to balance the load reaching the backbone network (not shown in the figure) via the first radio device 227 and the second radio device 281, it is usually The above situation occurs.

Fig. 3 is a schematic block diagram of an end device shown in Fig. 1. The end device 301 supports a full-duplex bridge between the first protocol stack 371 and the second protocol stack 381. The first protocol stack 371 supports the first radio device 315, and the second protocol stack 381 supports the second radio device 341. The EPD 301 is used to simultaneously support packet data communication via the first radio device 315 and via the second radio device 341. In other words, the EPD 301 supports the first protocol and the second protocol to simultaneously perform packet data communication with any two nodes such as an access point, a router, a bridge, another EPD, and so on. Both the first protocol and the second protocol support a 7-layer protocol stacking structure. Because the EPD 301 uses the first protocol by default to support communication applications running on the EPD 301, the first protocol stack 371 is referred to as the main protocol stack. If the first radio device 315 related to the first protocol stack 371 enters a "sleep state" and/or does not operate and/or the EPD 301 decides not to use the first radio device 315 in some cases, the EPD 301 will use the second radio device 315 Agreement to support the communication application. If the second communication application is running on the EPD 301, then the EPD 301 can only use the second protocol to support the second communication application.

As an example, a communication application such as Internet phone runs on EPD 301. As explained above, EPD 301 uses the first protocol to support Internet telephony applications. The first protocol stack 371 includes 7 layers, namely the 7th layer 303, the 6th layer 305, the 5th layer 307, the 4th layer 309, the 3rd layer 311, the 2nd layer 313, and the 1st layer 315. The seventh layer 303 is the Internet phone application, and the first layer 315 is the first radio device. The EPD 301 directs the data generated by the Internet phone application and/or sent to the Internet phone application through all the layers (305, 307, 309, 311, 313, and 315) of the first protocol stack 371. When the packet data passes through these layers, these layers 305, 307, 309, 311, 313, and 315 encode or decode the packet data. The first protocol stack 371 supports full-duplex packet data communication via the first radio device 315. For example, but not limited to, the EPD 301 is communicatively connected to another EPD on which another Internet phone application is running through the first path. In this example, the first path includes the first radio device or the first physical circuit 315.

The EPD 301 sometimes decides to connect another EPD through the second radio device or the second physical circuit 341. The path to another EPD via the second radio device 341 is called a second path. When the second path provides higher QoS, smaller delay, higher data rate, less interference, higher security, etc. than the first path, it is usually recommended that EPD 301 transfer the communication from the first path Switch to the second path. When the load of the first path exceeds a predetermined limit, the EPD 301 can decide to use the second path to maintain an Internet phone call with another EPD. The EPD 301 usually has to establish an Internet telephone session through the second protocol stack 381. The establishment of such a complete session spanning the 7 layers of the second protocol stack 381 is time-consuming.

The EPD 301 does not re-establish a complete session through the second protocol stack 381, but continues to run the Internet telephony application on the application layer of the first protocol stack 371 or the seventh layer 303. The EPD 301 establishes a bridge 351 between the fourth layer 309 of the first protocol stack 371 and the fourth layer 335 of the second protocol stack 381, that is, the first protocol stack 371 and the second protocol stack 381 are communicatively connected. 4th floor. The EPD 301 then establishes a full-duplex path through the bridge 351. The full-duplex path includes the sixth layer 305, the fifth layer 307, the fourth layer 309 of the first protocol stack 371, the bridge 351, and the fourth layer 355, the third layer 337, and the second protocol stack 381. Layer 339 and first layer 341. The first layer of the second protocol stack 381 is the second radio device 341. The data packets generated by the Internet phone application are transmitted through the full-duplex path. The data packets received by the EPD 301 through the second radio device 341 and the data packets sent to the Internet phone application 303 are transmitted to the Internet application 303 through the established full-duplex path.

The data packets transmitted between the Internet phone application 303 and the second radio device 303 through the established full-duplex path are encoded/decoded according to the first protocol and the second protocol. Layers 7, 6, 5, and 4 of the first protocol stack 371 encode/decode data packets according to the first protocol. Layers 4, 3, and 2 of the second protocol stack encode/decode data packets according to the second protocol. After the EPD 301 establishes a full-duplex path through the bridge 351, the fourth layer 309 of the first protocol stack 371 and the fourth layer 355 of the second protocol stack 381 exchange information. The information generally includes encryption and/or decryption information, and parameters corresponding to the transport layer of the first protocol stack 371 and the second protocol stack 381, that is, the fourth layer. This information is necessary to support the data flow through the established full-duplex path.

In this way, when the EPD 301 is connected to another EPD through the second wireless device 341, that is, the second path, it continues to run the Internet phone application on the 7th layer 303 of the first protocol stack 371. The EPD 301 can choose to let the 5th, 6th and 7th layers of the second protocol stack 381 not know the establishment of the bridge 351 between the 4th layer, and the subsequent communication applications (for example, Internet phone applications) and the first The data flow between the two radio devices 341 establishes a full-duplex path through the bridge 351.

In another embodiment, the EPD 301 chooses to send and/or receive data packets corresponding to the Internet phone application 303 through the first radio device 315, that is, through all the layers of the first protocol stack 371, and chooses to pass through the bridge The full-duplex path established by the device 350 to send and/or receive command data corresponding to the Internet phone application 303.

The EPD 301 can be used to establish a bridge between any two layers of the first protocol stack 371 and the second protocol stack 381 except for the 7th and 1st layers. The first agreement and the second agreement may be incompatible in communication. In this example, both the first agreement and the second agreement are packet exchange data agreements. In another embodiment, the first protocol and the second protocol may be a combination of a packet-switched data protocol and a circuit-switched data protocol.

Fig. 4 is a schematic block diagram of an end device shown in Fig. 1. The end device 401 supports full-duplex bridging between the first protocol stack 490, the second protocol sub-stack 495, and the third protocol sub-stack 493. The first protocol stack 490 supports the first physical layer circuit 415 and the second protocol The sub-stack 495 supports the second physical layer circuit 437, and the third protocol sub-stack 493 supports the third physical layer circuit 457. The EPD 401 includes a first physical layer circuit 415, a second physical layer circuit 437, and a third physical layer circuit 457. These physical layer circuits are transceivers or radio devices used to send data or receive data from nodes such as access points, bridges, EPDs, etc. The first physical layer circuit 415 operates in accordance with the first protocol. The second physical layer circuit 437 and the third physical layer circuit 457 support the second protocol and the third protocol, respectively. The communication application runs on EPD 401. The EPD 401 communicates with a second EPD (not shown in the figure), and another communication application is running on the second EPD. As an exemplary and non-limiting example, the EPD 401 is a laptop, the communication application is a web browsing application, and the second EPD is a web server. EPD with three physical layers 401 can establish up to 3 communication paths to the second EPD. These three communication paths are called a first path, a second path, and a third path, and they operate through the first physical layer circuit 415, the second physical layer circuit 437, and the third physical layer circuit 457, respectively.

The first protocol stack 490 used in the EPD 401 includes a 7-layer protocol stack structure. EPD 401 implements the second agreement sub-stack 495 and the third agreement sub-stack 493, that is, EPD 401 does not need to implement all 7 layers of the second agreement and all 7 layers of the third agreement, but only executes the second agreement. 4 layers and 4 layers of the third agreement, namely the first layer, the second layer, the third layer and the fourth layer. Any communication application runs on the 7th layer of the protocol stack. If the EPD 401 executes all 7 layers of the first protocol stack 490 in its circuit, the EPD 401 can only run one communication application at a time. However, the EPD 401 relies on its three physical layer circuits 415, 437, and 457 to support three paths to the second EPD.

Because the EPD 401 uses the first protocol stack 490 to establish any communication application by default, the first protocol stack 490 is called the main protocol stack. As an example, the EPD 401 runs a web browsing application on the 7th layer 403 of the first protocol stack 490. The data generated by and/or sent by the web browsing application 403 passes through all 7 layers of the first protocol stack 490, namely 403, 405, 407, 409, 411, 413, and 415, and passes The first path reaches the second EPD (not shown in the figure). The EPD 401 periodically measures and/or collects information related to delay, communication load, supported data rate, etc. on the first path, the second path, and the third path. The EPD 401 also periodically collects status information corresponding to the first, second, and third physical layer circuits 415, 437, and 457. For example, without limitation, sometimes, the EPD 401 decides to switch the communication from the first path to the third path based on the collected information.

After the EPD 401 decides to switch the communication from the first path to the third path, a full-duplex bridge is established between the fourth layer 490 of the first protocol stack 490 and the fourth layer 451 of the third protocol stack 493. The EPD 401 then guides the transfer of data between the web browsing application 403 (layer 7 of the first protocol stack) and the third physical circuit 457 (layer 1 of the third protocol sub-stack) through the first protocol stack 490. The 6th layer 405, the 5th layer 407 and the 4th layer 409, the bridge 475, the 4th layer 451, the 3rd layer 453, and the 2nd layer 455 of the third protocol sub-stack 493. After that, the web browsing application 403 running on the EPD 401 continues to exchange data with the second EPD (not shown in the figure) through the third physical circuit 457 or the third path. When the data passes through the 7, 6, 5, and 4 layers of the first protocol stack 490, it is encoded according to the first protocol; when the data passes through the 4th, 3, 2 and 1 layers of the third protocol sub-stack 493, Encode according to the third agreement.

In another embodiment, after the EPD 401 decides to switch the communication from the first path to the third path, it establishes a connection between the third layer 411 of the first protocol stack 490 and the third layer 453 of the third protocol stack 493. Duplex bridge 477. The EPD 401 then guides the data path between the web browsing application 403 (layer 7 of the first protocol stack) and the third physical circuit 457 (layer 1 of the third protocol sub-stack) to pass through the sixth layer of the first protocol stack 490. The layer 405, the fifth layer 407, the fourth layer 409 and the third layer 411, the bridge 477, the third layer 453 and the second layer 455 of the third protocol sub-stack 493.

Sometimes, EPD 401 decides which of bridges 475 and 477 is enabled. This decision of EPD 401 depends on the information collected by EPD 401 from three physical layer circuits and three paths. EPD 401 only activates one bridge between two protocol stacks at a time. When necessary, the EPD 401 can interrupt the bridge 475 and enable the bridge 477. The EPD 401 is also used to establish a bridge between the 4th and 3rd layers of the first protocol stack 490 and the second protocol sub-stack 495, so as to support the web browsing application 403 and the second EPD through the second path. Communication.

FIG. 5 is a schematic diagram of the end device 503 interacting with the backbone network 551 through the first path and the second path. The end device 503 has a bridge management module 517. The bridge management module 517 manages the bridge between the layers of the first protocol stack 519 and the layers of the second protocol stack 521, so as to facilitate the switch from the data communication session through the first path to the second path without re-establishing the Communication session. The EPD 503 can be a phone, a laptop, a PDA, a PC, a video game console, a server, or any client device. The backbone network is communicatively connected to multiple EPDs (not shown in the figure). Therefore, the EPD 503 can exchange data packets with multiple EPDs through the backbone network 551. The EPD 503 includes a first communication interface 505 through which the EPD 503 is communicatively connected to the downlink communication interface 533 of the first AP 531. The first communication interface 505 operates according to the first protocol following the first protocol stacking architecture 519. The first AP 531 is also communicatively connected to the first packet switched data network (PS-DN) 541 through its uplink communication interface 535. The first PS-DN 541 interacts with the backbone network 551. The EPD 503 therefore interacts with the backbone network 551 through the first communication interface 505 and using the first protocol. The first path from EPD 503 to the second EPD (not shown in the figure) of the multiple EPDs passes through the first AP 531, the first PS-DN 541 and the backbone network 551. A part of the first path running between the EPD 503 and the backbone network 551 follows the first agreement. Similarly, the second path from the EPD 503 to the second EPD (not shown in the figure) of the plurality of EPDs passes through the second AP 571, the second PS-DN 561, and the backbone network 551. A part of the second path running between the EPD 503 and the backbone network 551 follows the second agreement.

The first protocol stack 519 includes 7 layers. Among them, communication applications such as video games, Internet telephony, web browsing applications, phone calls, file download applications, video streaming, etc. run on the seventh layer 7 of the first protocol stack 519 . The first layer or physical layer of the first protocol stack 519 is the first communication interface 505. Similarly, the second protocol stack 521 includes 7 layers, and the communication application program runs on the 7th layer of the second protocol stack 521. The first layer or physical layer of the second protocol stack 521 is the second communication interface 509. For example, a video game application runs on the EPD 503, and as long as the video game session continues, the EPD 503 interacts with the second EPD of the multiple EPDs through the backbone network 551. In this embodiment, the second EPD may be a game server. Here, the communication session refers to a video game session between the EPD 503 and a second EPD (not shown in the figure). The EPD 503 interacts with the second EPD, that is, the game server, through the first path and the second path. This video game session requires full-duplex communication between the EPD 503 and the game server (not shown in the figure).

EPD 503 decides to use the first path to exchange data packets with the game server. The EPD 503 sends and receives data packets through the first communication interface 505. The video game application 515 runs on the 7th layer of the first protocol stack 519. Before sending a data packet (generated by a video game application) through the first path to the outside of layer 1 of the first protocol stack 519, the data packet is sent down through the first protocol stack from layer 7 to layer 1. At 519, different layers of the first protocol stack 519 encapsulate the data packets according to the first protocol. Similarly, the encapsulated and/or encoded data packets that reach the first communication interface 505 through the first path also follow the first protocol. These encapsulated and/or encoded data packets, namely video game applications, are decoded and/or decrypted by different layers of the first protocol stack 519 when they pass through the first protocol stack 519 from layer 1 to layer 7. .

Sometimes, EPD 503 decides to use the second path instead of the first path to exchange data packets with the game server. For example, if the first communication interface 505 enters the "sleep mode", the communication load on the first path exceeds the maximum limit, the second path supports a higher data rate within a specified time, and the second path provides higher data rates than the first path. QoS, etc., EPD 503 is prompted to make such a decision. Because part of the second path running between the EPD 503 and the backbone network 551 follows the second agreement, the video game session must be rebuilt in the second agreement stack 521. Before sending the data packets generated by the video game application 515 to the outside of the second communication interface 509, these data packets are required to be encoded and/or encrypted according to the second protocol.

EPD The bridge management module 517 in 503 establishes a bridge between one layer of the first protocol stack 519 and the corresponding layer of the second protocol stack 521. The bridge management module 517 also guides the data packets generated by the video game application 515 and/or sent to the video game application 515 through the established bridge. For example, the bridge management module 517 enables the bridge between the fourth layer of the first protocol stack 519 and the fourth layer of the second protocol stack 521. The fourth layer is the transport layer in the 7-layer protocol stacking architecture. In this case, it is neither necessary to terminate the video game session through the first protocol stack 519, nor to re-establish the video game session through the second protocol stack 521. In contrast, at least one session parameter is transferred from the first protocol stack 519 to the second protocol stack 521 through the established bridge. The at least one session parameter is usually an encryption parameter, a login parameter, a billing parameter, an associated parameter, etc. The data packet generated by the video game application 515 running on the 7th layer of the first protocol stack 519, under the guidance of the bridge management module 517, passes downwards through the 7th, 6th, and the first protocol stack 519. 5th floor, reach the 4th floor. Then, the data packet is transmitted from the fourth layer of the first protocol stack 519 to the fourth layer of the second protocol stack 521 through the established bridge. Then, the data packet passes downward through the third layer, the second layer, and the first layer of the second protocol stack 521, and then is sent out of the second communication interface 509. When the data packet passes through the above layers of the first protocol stack 519, the data packet is encapsulated and/or encrypted according to the first protocol. When the data packet passes through the above layers of the second protocol stack 521, the data packet is also encapsulated and/or encrypted according to the second protocol. The data packet stream generated by the video game application is managed by the bridge management module 517. In this example, the second protocol stack 521 has an entry point for the first protocol stack 519 on its 4th layer. When the EPD 503 switches from the first path to the second path, the EPD 503 does not need to pass the second protocol. All layers of the stack 521 re-establish the video game session. In this example, as long as the EPD 503 exchanges data through the second path, the first communication interface 505 is not in use. In another embodiment, the second agreement stack 521 leaves multiple entry points for the first agreement stack 519, for example, there is a first entry point on its fifth layer, and a second entry point on its fourth layer. Entry point, which has a third entry point on its third floor.

Similarly, the bridge management module 517 guides the data packets arriving at the second communication interface 509 via the second path upwards through the first, second, third, and fourth layers of the second protocol stack 521. The received data is further transmitted through the fourth layer of the first protocol stack 519 through the established bridge. Then, the received data packet passes upward through the 4th, 5th, and 6th layers of the first protocol stack 519 to the 7th layer, which is the video game application 515. In this embodiment, the first protocol stack 519 has the entry point of the second protocol stack 521 on its 4th layer. In this way, even if the EPD 503 uses the second path instead of the first path to communicate with the game server (Not shown in the figure) When communicating, there is no need to go through all the layers of the second protocol stack 521 to re-establish the video game session. In another embodiment, the first protocol stack 519 leaves multiple entry points for the second protocol stack 521, for example, there is a first entry point on its 4th level, and a second entry point on its 3rd level. Entry point, which has a third entry point on its second floor.

In one embodiment, the bridge management module 517 decides to keep interacting with the game server through the first path and the second path at the same time. The bridge management module 517 guides the transmission of data generated by the video game application 515 and/or sent to the video game application 515 through the first path, that is, through the first communication interface 505 and each layer of the first protocol stack 519. In addition, the bridge management module 517 also guides the command packets periodically and/or accidentally generated by the video game application 515 and/or sent by the game server (not shown in the figure) to the video game application through the first path. Transmission of 515 command packets. These command packets are directed to pass through some layers of the first protocol stack 519, the established bridge, and some layers of the second protocol stack 521. By establishing a bridge, the layers of the two protocol stacks become communicatively interconnected, that is, the fourth layer of the first protocol stack 519 and the fourth layer of the second protocol stack 521 exchange required information to support the two Protocol sub-stacked packet data communication. For example, if the layer 4 on both sides participates in the connection, they can exchange information corresponding to the TCP protocol; if the layer 3 on both sides participates in the connection, then they can exchange information corresponding to the IP protocol; if the layer 5 on both sides Participate in the connection, then they can exchange login information and so on. In another embodiment, the first protocol and the second protocol are incompatible in communication. The first protocol and the second protocol can be any kind of packet exchange data communication protocol.

FIG. 6 is a schematic block diagram of multiple elements of the end device 600. The end device 600 supports multiple data communication protocol stacks, wherein each layer of the first protocol stack independently manages the bridging with the corresponding layer of the second protocol stack. The EPD 600 is usually a notebook computer, PC, PDA, server, video game box, etc., and includes a display 661 and a user input interface 671. The user input interface 671 is usually a plurality of buttons, a touch pad, a mouse, a joystick, a thumb wheel, a touch screen, a stylus, a voice-based interface, and the like. The EPD 600 is communicatively connected to the first AP, the second AP, the third AP, and the second AP through the first wired uplink interface 623, the second wired uplink interface 637, the first wireless uplink interface 643, and the second wireless uplink interface 647, respectively. Four AP. EPD 600 can simultaneously support data communication with four different APs using four different communication protocols. Among the four different communication protocols, two are wired protocols and the other two are wireless protocols. EPD 600 implements four different protocol stacks, and each protocol stack is responsible for data communication using one of the four different protocols. The four protocol stacks are the first protocol stack 611, the second protocol stack 625, the third protocol stack 641, and the fourth protocol stack 645. Among the four protocol stacks 611, 625, 641, and 645, each protocol stack includes 7 layers. The communication application program runs on the uppermost layer of each protocol stack in the protocol stacks 611, 625, 641, and 645, that is, the application layer or the seventh layer. The communication interface, that is, the radio device, constitutes the lowest layer of each protocol stack in the protocol stacks 611, 625, 641, and 645, which is the physical layer or the first layer. The first wired uplink interface 623 is the first layer of the first protocol stack 611, the second wired uplink interface 637 is the first layer of the second protocol stack 625, and the first wireless uplink interface 643 is the first layer of the third protocol stack 641. The first layer, the second wireless uplink interface 647 is the first layer of the fourth protocol stack 645.

Each of the protocol stacks 611, 625, 641, and 645 has an associated layer manager from layer 6 to layer 2. The 7th layer where the application runs and the 1st layer as the physical layer do not participate in the bridging between protocol stacks. The 6th layer manager 614 determines whether the 6th layer 613 of the first protocol stack 611 is to be the same as the 6th layer of the second protocol stack 625, or the 6th layer of the third protocol stack 641, or the 6th layer of the fourth protocol stack 645. The layers form a bridge. In another embodiment, the layer 6 manager 614 of the first protocol stack 611 and the layer 6 manager 628 of the second protocol stack 625 jointly determine whether the 6th layer 613 and the 6th layer of the first protocol stack 611 A bridge is established between the sixth layer 627 of the second protocol stack 625. The decision whether to enable the bridge depends on the information collected by the relevant layer manager from the first and second layers of the participating protocol stack.

As an exemplary and non-limiting example, the layer 6 manager 614 of the first protocol stack 611 and the layer 6 manager 628 of the second protocol stack 625 from the first and second layers of the first protocol stack 611 And collect information on the first and second layers of the second protocol stack 625. The first layer 623 of the first protocol stack 611 is communicatively connected to the first AP through a first path. The first layer 637 of the second protocol stack 625 is communicatively connected to the second AP through a second path. The collected information generally includes the load on the first path and the second path, the interference level, the current data transmission rate, the maximum supported data rate, and the status of the first wired uplink interface 623, and the status of the second wired uplink interface 637. Status, etc. Based on the collected information, the layer 6 manager 614 and the layer 6 manager 628 jointly decide to transmit the data packet previously transmitted to the first AP through the first path to the second AP through the second path. Subsequently, the 6th layer manager 614 and the 6th layer manager 628 jointly enable the bridge between the 6th layer 613 of the first protocol stack 611 and the 6th layer 627 of the second protocol stack 625. Before enabling the bridge, the data generated by the communication application 607 and/or the data sent to the communication application 607 is transmitted through all the layers of the first protocol stack 611, and is sent by the first wired uplink interface 623 and/ Or receive. After the bridge is enabled, the layer 6 manager 614 and the layer 6 manager 628 guide the data packet flow between the communication application 607 and the second wired uplink interface 623 through the 6th layer 613 of the first protocol stack 611, so The enabled bridge, the 6th layer 627, the 5th layer 629, the 4th layer 631, the 3rd layer 622 and the 2nd layer 635 of the second protocol stack 625. The data packets that previously passed through the first wired uplink interface 623 are now transmitted through the second wired uplink interface 637. The first wired uplink interface 623 is related to the first protocol stack 611, and the second wired uplink interface 637 is related to the second protocol stack 625. The data packet does not need to pass through all the layers of the second protocol stack 625, but only passes through some layers of the second protocol stack 625 and some layers of the first protocol stack 611 to reach the seventh layer of the first protocol stack 611. Communication application. The reconstruction of the communication session still passing through the first protocol stack 611 and through the second protocol stack 625 requires the transmission of information from the first protocol stack 611 to the second protocol stack 625, which results in a delay. The bridging between the two layers of the first protocol stack 611 and the second protocol stack 625 reduces

FIG. 7 is a flowchart of a method for establishing a path through the second physical layer by enabling a bridge between two communication-incompatible protocol stacks executed on the end device. In the two protocol stacks, the first protocol stack supports the first physical layer, and the second protocol stack supports the second physical layer. In these two protocol stacks, the first layer of each protocol stack is the physical layer, that is, the first layer of the first protocol stack is the first physical layer, and the first layer of the second protocol stack is the second physical layer. . The EPD chooses to use the first protocol of the two protocols to transmit and receive data packets, that is, the EPD sends and receives data packets through the first layer of the first protocol stack by default, as shown in step 703. This also causes the first layer of the first protocol stack to be called the primary physical layer.

In the next step 705, the bridge management module used in the EPD (end device) collects information from the first and second layers of the two protocol stacks executed in the EPD. The information collected by the bridge management module in step 705 can usually inform the bridge management module of the delay, communication load, link quality, device status, received information intensity, etc. related to the first physical layer and the second physical layer. In the next step 715, the bridge management module determines whether to enable the bridge between the two protocol stacks. If the bridge management module decides not to enable the bridge, then the method returns to step 705. In a non-limiting example, the bridge management module collects information periodically.

If the bridge management module decides to enable the bridge, the method goes to step 725. In step 725, the bridge management module activates a bridge between the corresponding layers of the two protocol stacks, thereby establishing a communication path from the communication application running on the EPD to the second physical layer, without the need to re-establish a through A complete communication session for all layers of the second protocol stack. The bridge management module guides at least one session parameter corresponding to the communication session just running through the first protocol stack to be transmitted to the second protocol stack through the established bridge. By maintaining the at least one session parameter, the EPD does not need to terminate the communication session of all the layers stacked through the first protocol, and then re-establish the communication session completely passing through all the layers of the second protocol stack. Enabling the bridge means connecting the two corresponding layers to communicate, and then the two layers agree to receive data from each other. In step 725, the bridge management module can choose between two protocol-stacked session layers, between two protocol-stacked transport layers, between two protocol-stacked network layers, or two protocol-stacked LLCs. Establish bridges between layers. The bridge management module makes all decisions based on the information collected in step 705. In one embodiment, the bridge management module may not have the right to choose between which layers a bridge should be established. For example, the EPD circuit can only support the establishment of a bridge between the transport layers of two protocol stacks.

In step 725, the bridge management module establishes a communication path. The path includes some higher layers above the bridge in the first protocol stack, and some lower layers below the bridge in the second protocol stack, that is, the path includes the application layer of the first protocol stack , Presentation layer, session layer and transport layer, as well as the transport layer, network layer, data link layer and physical layer of the second protocol stack. The physical layer of the second protocol stack is the second physical layer (sub-physical layer). Therefore, in step 725, through the bridge management module, a communication path from the communication application, that is, the application layer of the first protocol stack, to the second physical layer is established.

In step 735, the bridge management module directs the data packet stream previously passed through the first physical layer to be transmitted through the established bridge. In one embodiment, the established communication path supports a half-duplex data flow; in another embodiment, the established communication path supports a full-duplex data flow. The bridge management module monitors the communication characteristics on the second physical layer, that is, delay, communication load, QoS, etc., to determine whether to continue to let data packets flow through the established communication path through the second physical layer, as shown in step 745. If at some point, the bridge management module finds that the established path is not suitable to continue, then the bridge management module will guide the data packet to flow through the first physical layer, that is, through all the layers of the first protocol stack, as in step 703 Show.

FIG. 8 is a flowchart of a method for establishing a path through the second physical layer by enabling a bridge between two protocol stacks executed on an end device, in which multiple layer managers enable and manage the bridge. In the two protocol stacks, the first protocol stack supports the first physical layer, and the second protocol stack supports the second physical layer. In these two protocol stacks, the first layer of each protocol stack is called the physical layer, that is, the first layer of the first protocol stack is the first physical layer, and the first layer of the second protocol stack is the second Physical layer. The EPD chooses to use the first protocol of the two protocols to transmit and receive data packets, that is, the EPD sends and receives data packets through the first layer of the first protocol stack by default, as shown in step 803. This makes the first layer of the first protocol stack the main physical layer. EPD chooses to run any application on the 7th layer of the first protocol stack, the application layer. Before the first physical layer, that is, the first layer of the first protocol stack, sends out the data packet generated by the communication application, the data packet passes through all the layers of the first protocol stack, as shown in step 803. Similarly, the data packets received by the EPD through the first physical layer and sent to the communication application pass through all layers of the first protocol stack to reach the communication application. In one embodiment, the two communication stacks are communication incompatible. For example, the first protocol stack follows the WiMax protocol, and the second protocol stack follows the GPRS protocol.

EPD uses multiple layer managers to determine, enable, and maintain the bridge between the two corresponding layers of the two protocol stacks. In these two protocol stacks, each protocol stack follows a 7-layer architecture, that is, each protocol stack includes an application layer, a presentation layer, a session layer, a transport layer, a network layer, a data link layer, and a physical layer. The first session layer manager corresponding to the session layer of the first protocol stack and/or the second session layer manager corresponding to the session layer of the second protocol stack respectively from its direct lower layer, that is, the transport layer of the first protocol stack and The transport layer of the second protocol stack collects information, as shown in step 805. The first session layer manager and/or the second session layer manager request information related to the first physical layer and the second physical layer, such as delay, communication load, link quality, device status, received signal strength, and the like. Usually, this information is available to the first physical layer and the second physical layer. Based on the requests of the first physical layer and the second physical layer, the information passes upward through the protocol stack to reach the first session layer manager and/or the second session layer manager.

In the next step 815, the first session layer manager and/or the second session layer manager decides whether to enable a bridge between the two session layers of the two protocol stacks. If it is decided not to enable, then the method returns to step 805. For example, the first session layer manager and/or the second session layer manager may periodically collect information from the immediate lower layer.

Step 805 and step 825 are executed by each layer manager of the plurality of layer managers. In other words, the first transport layer manager corresponding to the transport layer of the first protocol stack and/or the second transport layer manager corresponding to the transport layer of the second protocol stack collects information from the directly lower layer, that is, from the corresponding network The layer collects information to determine whether to enable a bridge between the transport layers of the two protocol stacks. The network layer manager and LLC layer manager also perform similar steps. Only one bridge can be established at a time between the two corresponding layers of the two protocol stacks. Therefore, the session layer manager, the transport layer manager, the network layer manager, and the LLC layer manager inform each other of their decisions.

The method continues to step 825, the layer manager (one of the session layer manager, transport layer manager, network layer manager, and LLC layer manager) is activated between the two selected layers of the two protocol stacks Bridge. The layer manager directs at least one session parameter corresponding to the communication session to be transmitted to the second protocol stack through the enabled bridge. The at least one session parameter allows the EPD to not terminate the passage of all the layers of the first protocol stack, and then re-establish a communication session that completely passes through all the layers of the second protocol stack. The at least one session parameter is generally an encryption parameter, a login parameter, a billing parameter, an associated parameter, etc. In this way, the layer manager establishes a communication path from the communication application running on the application layer of the first protocol stack to the second physical layer. The activation of the bridge means that the two selected layers are connected in communication, and then the two layers agree to receive data from each other. The decision of whether to establish a bridge is made by the layer manager based on the information collected in step 805.

In step 825, the bridge management module establishes a communication path. If the LLC layer managers of two protocol stacks establish a bridge between the LLC layers of the two protocol stacks, then the path includes the application layer, presentation layer, session layer, transport layer, and network layer of the first protocol stack. And the LLC layer, and the LLC layer, MAC layer and physical layer of the second protocol stack. Therefore, in step 825, a path from the communication application to the second physical layer is established without re-establishing a communication session that completely passes through all the layers of the second protocol stack.

In this embodiment, in step 835, the participating layer manager, that is, the LLC layer manager, directs the data packet stream that passed through the first physical layer to be transmitted through the established communication path. In one embodiment, the established communication path supports a half-duplex data flow; in another embodiment, the established communication path supports a full-duplex data flow. The LLC layer manager monitors the communication characteristics on the second physical layer, that is, delay, communication load, QoS, etc., to determine whether to continue to let data packets flow through the established communication path through the second physical layer, as shown in step 845. If at some point, the LLC layer manager finds that the established path is not suitable to continue, then the LLC layer manager will guide the data packet to flow through the first physical layer, that is, all the layers stacked through the first protocol, as in step 703 Shown.

In another embodiment, the LLC layer manager establishes a half-duplex communication path. The LLC layer manager guides the data packets generated by the communication application to flow through the established communication path, and then send it out from the second physical layer. The LLC layer manager simultaneously receives multiple data packets sent to the communication application through the first physical layer, and guides these data packets to be transmitted through all layers of the first protocol stack.

Those skilled in the art should understand that the term "communicatively connected" as used herein includes wireless and wired connections, direct connections and indirect connections through other elements, elements, circuits or modules. Those skilled in the art should also understand that inferred connection (that is, knowing that one element is connected to another element by inference) includes wireless and wired, direct connection between two elements in the same manner as the above-mentioned "communication connection". And indirect connection.

The above description of the present invention uses method steps to describe the execution process of specific functions and their interrelationships. For ease of description, the boundary and sequence of these functional modules and method steps are specifically defined in the article. As long as these functions and their relationships work normally, their boundaries and order can also be redefined. Therefore, any redefinition of boundaries and order will fall into the spirit of the present invention and the declared protection scope.

The above description of the present invention uses functional modules to describe the execution process of some important functions. For ease of description, the boundary of these functional modules is specifically defined in the article. As long as these functions can be implemented normally, their boundaries can also be redefined. Similarly, the steps in the flowchart are also specifically defined to describe some important functions. In order to expand the application of these flowcharts, the boundaries and sequence of the modules in the flowchart can be redefined. At the same time, after the redefinition, these modules still complete the original important functions. This redefinition of the steps and sequence of the functional modules and flowcharts will also fall into the spirit of the present invention and the declared scope of protection.

Those skilled in the art can also realize that the functional modules and other modules and components described in this article can be implemented as shown in the figure, or distributed components, dedicated integrated circuits, and software that executes specific software can also be used. Processor and any combination of them.

In addition, for ease of understanding, the present invention is described in detail with the help of specific embodiments, but the present invention is not limited to these embodiments. Obviously, for those skilled in the art, the content of this document can be modified within the spirit and scope of the present invention, but these modifications still fall within the scope of the present invention.

<p>101Communication network</p><p>103Backbone network</p><p>105Terrestrial cellular network</p><p>107Wireless data network</p><p>109Satellite Data Network</p><p>111Wired data network</p><p>121First Access Point (AP)</p><p>123Second Access Point (AP)</p><p>125Third access point (AP)</p><p>127Fourth Access Point (AP)</p><p>131First Agreement</p><p>133Second Agreement</p><p>137 Fourth Agreement</p><p>151First End Device (EPD)</p><p>153Second end device (EPD)</p><p>155Third end device (EPD)</p><p>161The first protocol stack</p><p>163Second Protocol Stack</p><p>165The third protocol stack</p><p>167Bridge Management Module</p><p>181protocol stacking architecture</p><p>201End Equipment</p><p>203First application layer</p><p>205First performance layer</p><p>207First Session Layer</p><p>209First transport layer</p><p>211First network layer</p><p>213First data link layer</p><p>215First logical link control layer</p><p>217First media access control layer</p><p>227First physical layer</p><p>241Session Layer Bridge</p><p>243Transport layer bridge</p><p>245Network Layer Bridge</p><p>247Logical Link Control (LLC) Layer Bridge</p><p>261Second session layer</p><p>263Second transport layer</p><p>265Second network layer</p><p>267Second logical link control layer</p><p>269Second media access control layer</p><p>281secondary radio</p><p>301End Equipment</p><p>303Internet Phone Application</p><p>305Floor 6</p><p>307Fifth Floor</p><p>309Fourth floor</p><p>311Level 3</p><p>313Level 2</p><p>315The first radio device</p><p>355Fourth floor</p><p>337Level 3</p><p>339Level 2</p><p>341Second radio device</p><p>351Bridge</p><p>371The first protocol stack</p><p>381Second Protocol Stack</p><p>401End Equipment</p><p>403Web browsing application</p><p>Floors 405, 407, 409, 411, 413</p><p>415First physical layer circuit</p><p>437Second physical layer circuit</p><p>451Fourth floor</p><p>453Level 3</p><p>4552nd floor</p><p>457The third physical layer circuit</p><p>475Bridge</p><p>477Bridge</p><p>490First Protocol Stack</p><p>493The third protocol sub-stack</p><p>495Second Protocol Substack</p><p>503End Equipment</p><p>505First communication interface</p><p>509Second communication interface</p><p>515Video Game Application</p><p>517Bridge Management Module</p><p>519The first protocol stack</p><p>521Second Protocol Stack</p><p>531First AP</p><p>533Downlink communication interface</p><p>535Uplink communication interface</p><p>541First Packet Switched Data Network (PS-DN)</p><p>551Backbone Network</p><p>561Second PS-DN</p><p>571Second AP</p><p>600End Equipment</p><p>607Communication Application</p><p>611The first protocol stack</p><p>6136th floor</p><p>614Layer 6 Manager</p><p>622Level 3</p><p>623The first wired uplink interface</p><p>625Second Protocol Stack</p><p>6276th floor</p><p>628Layer 6 Manager</p><p>629Fifth Floor</p><p>631Fourth floor</p><p>6352nd floor</p><p>637The second wired uplink interface</p><p>641The third protocol stack</p><p>643The first wireless uplink interface</p><p>645The fourth protocol stack</p><p>647Second wireless uplink interface</p><p>661Display</p><p>671User input interface</p>

Fig. 1 is a schematic block diagram of a communication network of end devices and access points, where each end device adopts a first protocol stack having an entry point provided to a second protocol stack, and the end device supports and uses the first protocol 2 is a schematic block diagram of an end device shown in Fig. 1, and the end device supports data communication with another access point using the second protocol. A half-duplex bridge between a protocol stack and a second protocol stack, wherein the first protocol stack supports the first radio device, and the second protocol stack supports the second radio device; FIG. 3 is an end shown in FIG. 1 A schematic block diagram of a device, the end device supports a full-duplex bridge between a first protocol stack and a second protocol stack, wherein the first protocol stack supports the first radio device, and the second protocol stack supports the second radio device Fig. 4 is a schematic block diagram of an end device shown in Fig. 1, the end device supports full-duplex bridging between the first protocol stack, the second protocol sub-stack, and the third protocol sub-stack, wherein the The first protocol stack supports the first physical layer circuit, the second protocol sub-stack supports the second physical layer circuit, and the third protocol sub-stack supports the third physical layer circuit; Figure 5 shows the end device and the backbone through the first path and the second path A schematic diagram of network interaction. The terminal device has a bridge management module that manages the bridges between each layer of the first protocol stack and each layer of the second protocol stack to facilitate data communication through the first path The session is switched to the second path without the need to re-establish the communication session; FIG. 6 is a schematic block diagram of multiple components of the end device, the end device supports multiple data communication protocol stacks, and each of the first protocol stacks Each layer independently manages the bridging with the corresponding layer in the second protocol stack; Figure 7 is to establish a communication path through the second physical layer by enabling a bridge between two communication incompatible protocol stacks executed on the end device Figure 8 is a flow chart of a method for establishing a communication path through the second physical layer by enabling a bridge between two corresponding layers of the two protocol stacks executed on the end device, wherein multiple layers are managed The device calls and manages the bridge.