TW200926708A - Method and apparatus for communicating over multiple networks - Google Patents

Abstract

A Asymmetric Data over Coaxial (ADoC) dual mode device provides support for both wired and wireless modes of operation, and can switch between these two modes periodically. In ADoC (wired) mode, the dual mode device operates as ADoC Station while in WLAN (wireless) mode, it operates as WLAN Access Point In one particular implementation, a communication unit (3100, 3104, 3106) is configured for communicating over multiple media including a wireless medium and a wired medium, the communication unit being operable (1) in a wireless mode for communicating over a wireless medium using a wireless protocol, and (2) in a wired mode for communicating over the wired medium using a variation of the wireless protocol. The implementation also includes a switch (3104) to switch the communication unit between the wireless mode and the wired mode.

Description

200926708 IX. Description of the invention: [Technical field to which the invention pertains] This disclosure generally addresses various aspects of a communication system. [Prior Art]

[Summary of the Invention]

包括 Include a wireless medium and a device (e.g., a communication unit) for communicating over the multimedia of the wired medium. The communication unit can operate in (1) a wireless mode communicating over a wireless medium using a wireless protocol, and (2) operating in a wired mode of communication over the wired medium using one of the wireless protocols. A device (e.g., a switch) is configured to switch the communication device (e.g., the communication unit) between the wireless mode and the wired mode. According to another general aspect, a method includes communicating over a multimedia comprising a wireless medium and a wired medium using (1) a no-mode of communication over a wireless medium using a wireless protocol, and (2) One or more of a wired mode communicated over the wired medium is changed using one of the wired protocols. The method includes switching between the wireless mode and the wired mode. According to another aspect, a device includes a processor readable medium </ RTI> comprising instructions stored in the processor readable medium for communicating over multimedia including a wireless medium and a wired medium, The communication uses (1) a wireless module that communicates over a wireless medium using a wireless protocol, and (2) communicates over the wired medium using one of the wired protocols - a wired mode 132611.doc -6 - 200926708 - or more. The instructions are also used to switch between the wireless mode and the wired mode. The details of the embodiment or embodiments are set forth in the drawings and the description below. Even if a specific approach is used, it remains clear that the various configurations or implementations can be used in a variety of ways. For example, an embodiment can be implemented as a method, or embodied as one of the instructions configured to perform one of a set of operations for performing a set of operations. Other aspects will be apparent from the following detailed description and claims. [Embodiment] At least the description of Figures 1 to 8 presents a sentence extension. The main present includes - or a plurality of novel and inventive aspects or Various embodiments of features. These implementers (4) at least _ ^ ^ (4) - the typical characteristics of the wireless system - the transmission of data in the Wei - system. In particular, 'at least one implementation ❹—time-sharing in coaxial cable. This system allows, for example, - (iv) television operators to provide television signals in portions of the spectrum and provide additional services in another portion of the spectrum. Additional services may include, for example, Internet access, except for network access, including access to search the Internet and view the illusion on the Internet and receive services over the Internet (eg, on-demand) Video). At least the description of Figures 9 through 20 presents additional embodiments, and at least one of the additional embodiments expands the description of Figures 1 through 8 by illustrating the novelty and inventive use of the town. A specific implementation, the + implementation includes a modem that receives an Ethernet packet from multiple hosts. Each I can try to communicate with a different website through a router. The Zhao data packet encapsulates the packets into a single packet formatted for use in a format or protocol of wireless transmission. However, 132611.doc 200926708 and the 'packet message' is transmitted in the coaxial electrical meter for reception by the router. The router in turn transmits the packets to the different websites with which each of the hosts attempts to communicate. The packet used by the embodiment described above is provided to the booster port of the enemy supply for comparison with the system of only the packet-packet. Therefore, the workload of the wireless infrastructure is spread across multiple Ethernet packets. This is in contrast to, for example, the use of a packet that allows additional features to be provided by another communication layer, or by the preservation of the old frame structure in the packet data. Ensure backward compatibility. In addition, the package of the above-mentioned embodiment is also allowed to use the data of multiple sources to be packaged together and the pre-50 for different terminals, according to the system design. The data (for example, different websites, or different hosts) is packaged together. At least the description of Figures 2! through 34 presents additional embodiments. Some of these implementations address the new structure of the frame structure and the connection to the polling and competition-based access. Another embodiment addresses the dual module state. · This app now offers a map! To the description of 8. Attention should be paid to the header system, the chapters used for the description of Figure 8 to 8. A given chapter is not considered to be limited to the subject matter of the header, nor is it limited to topics other than the subject matter of the header. The headers are exemplary: for general assistance to readers. These headers are not intended to be included in the disclosure, nor to limit the applicability or generality of the disclosure. 13261 l.doc 200926708 Application to provide the existing coaxial cable τν system (CATV) Data Service, at least one embodiment provides a Time Division Function (TDF) protocol compliant access point (AP) and station (STA) in the cable access network. APs and STAs are connected via a splitter in a hierarchical tree structure. In this way, users at home can access the remote IP core network via the cable access network. The detailed network layout is illustrated as illustrated in Figure 1. As can be seen from Figure 1, in this typical access network infrastructure, there is a TDF protocol compliant AP with an Ethernet interface connected to the IP core network, and the cable access network. A coaxial cable interface for the road connection. On the other end of the cable access network, there is a TDF protocol compliant STA, ie a terminal, which is connected to the cable access network via the coaxial cable interface and via the Ethernet interface to the home LAN (regional network) Road) connection.

According to at least one embodiment, both the TDF AP and the STA implement the protocol stack separately in the logical link control sublayer, the MAC sublayer, and the physical layer according to the 8〇2·11 series specification. However, in the MAC sublayer, the TDP AP and STA 取代 replace the 8〇2·11 frame transmission entity with the TDF frame transmission entity. Therefore, the MAC sublayer for TDF ΑΡ and STA is composed of 802.1 1 frame packet/decapsulation entity and TDF frame transmission entity, and the MAC sublayer for 802.11 compliant AP and STA is encapsulated by 802.1 1 frame/ Decapsulation entity and 802.1 1 frame transmission entity. For integrated APs and STAs, TDF frame transmission entities and 802.11 frame transmission entities can coexist simultaneously to provide both 802.11 and TDF functions. Switching between the two modes can be achieved by manual or dynamic configuration. 132611.doc 200926708 Basic Approach The main idea of the TDF protocol is to transmit IEEE 802.1 1 frames over coaxial cable media rather than over the air. The purpose of utilizing the IEEE 802.1 1 mechanism is to implement mature hardware and software implementations that are stacked using the 802.1 1 protocol. The main feature of TDF is its unique media access control method for transmitting IEEE 802.1 1 data frames. That is, it does not utilize a legacy IEEE 802.11 DCF (Distributed Coordination Function) or PCF (Point Coordination Function) mechanism to exchange MAC frames, including MSDU (MAC Service Data Unit) and MMPDU (MAC Management Protocol Data Unit). Instead, it uses a time-sharing method to transmit MAC frames. Thus TDF is an access method that defines a detailed implementation of a frame transport entity located in the MAC sublayer. For purposes of comparison, the IEEE 802.1 1 MAC sublayer protocol in the OSI reference model as shown in Figure 2 is illustrated herein. Although the exact location of the TDF protocol for use in the OSI reference model is illustrated in FIG. Communication mode entry procedure

Currently, there are two communication modes suggested for the TDF compliant station, as explained below. One is the standard IEEE 802.1 1 operating mode, which is subject to the frame structure and transmission mechanism defined in the IEEE 802.1 1 series of standards; the other is in the TDF operating mode, and detailed information about it will be explained in the following paragraphs. Figure 4 indicates the strategy for deciding which mode of operation to enter when a TDF STA is activated. Once a TDF STA receives a sync frame from an AP, it is enabled to enter the TDF mode. If the sync frame is not received within a preset timeout, then the D8 is kept or offset to a ratio of £. £ 802.1 1 mode. TDF Agreement Functional Description 132611.doc -10- 200926708 Access Method The physical layer in the TDF station can have multiple data transfer rate capabilities that allow the implementation to implement dynamic rate switching with improved performance and device maintenance goals. Currently, the TDF station can support three types of data rates: 54 Mbps '18 Mbps and 6 Mbps. Data services are provided primarily at 54 Mbps data rates. When there is some problem with supporting 54 Mbps data transmission, it can temporarily switch to the 18 Mbps data rate. Design a 6 Mbps data rate operating mode based on network maintenance and desk debugging. The data rate can be statically configured before a TDF station enters the TDF communication program and remains the same throughout the communication procedure. On the other hand, the TDF station can also support dynamic data rate switching during service. The criteria for data rate can be based on channel signal quality and other factors. The basic access method of the TDF protocol is Time Division Multi-Direction (TDMA), which allows multiple users to share the same channel by dividing the same channel into different time slots. The TDF STAs successively transmit uplink traffic in succession, and each STA uses its own time slot in the TDF hyperframe assigned by the TDF AP. For downlink traffic, the STAs share the channel and select the data or management frame targeted by comparing the destination address information of the frame with its address. Figure 5 illustrates an example of a TDF hyperframe structure and time slot allocation for a typical TDF hyperframe when there are m STAs competing for uplink transmission opportunities simultaneously. As shown in FIG. 5, there is a time slot of a fixed number of TDF frames (tdfTotalTimeSlotNumber), which is composed of: a 13611 for transmitting clock synchronization information from the TDF AP to the TDF STA. Doc 11 200926708 Synchronous time slots; a contention time slot for transmitting registration requests for uplink time slot allocation; tdfUplinkTimeSlotNumber uplinks for registering TDF STAs for successive transmission of data and some management frames to TDF APs The time slot; and the tdfDownlinkTimeSlotNumber downlink time slot of the frame to the data machine by the TDF AP for transmitting data and registering response management. Except for the sync slot, all other slots known as the common slot have the same duration and have a length equal to tdfCommonTimeSlotDuration. The value of tdfCommonTimeSlotDuration is defined to allow transmission

® At least one of the largest IEEE 802.1 1 PLCP (Physical Layer Convergence Protocol) Protocol Data Units (PPDUs) in one of the highest rate data modules. The duration of the synchronization slot tdfSyncTimeSlotDuration is shorter than the common

The duration of the time slot, because the clock synchronization frame transmitted from the TDF AP to the TDF STA in this slot is shorter than the 802.11 data frame. Therefore, the duration of a TDF hyperframe defined as tdfSuperframeDuration can be calculated by the following equation: _ tdfSuperframeDuration = tdfSyncTimeSlotDuration + ❹ tdfCommonTimeSlotDuration * (tdfTotalTimeSlotNumber - 1) The relationship between tdfTotalTimeSlotNumber, tdfUplinkTimeSlotNumber and tdfDownlinkTimeSlotNumber satisfies the following equation: tdfTotalTimeSlotNumber = tdfUplinkTimeSlotNumber + tdfDownlinkTimeSlotNumber + 2 In addition, the number of allocated uplink time slots of the TDF STA in a TDF hyperframe can be changed from one to tdfUplinkTimeSlotThreshold. Therefore, the available downlink time slot in a TDF hyperframe can be changed from 132611.doc 12 200926708 (tdfTotalTimeSlotNumber-2) to (tdfTotalTimeSlotNumber-2-tdfMaximumUplinkTimeSlotNumber). Each time there is a TDF STA requesting an uplink time slot, the TDF AP will infer one or more time slots from the available downlink time slots, and then assign the time slots to the TDF STA, As long as the number of uplink time slots will not exceed the value of tdfMaximumUplinkTimeSlotNumber ° tdfMaximumUplinkTimeSlotNumber afterwards, it may vary in different implementations. However, it must be carefully chosen so that there is at least one downlink © time slot available for an associated TDF STA in order to guarantee the QoS of the data service. In addition, all consecutive time slots used by the same TDF STA or AP for transmission in the same direction can be combined to continuously transmit MAC frames to avoid such time slots caused by unnecessary conversion and protection. Waste at the edge. In the current embodiment, tdfCommonTimeSlotDuration is about 300 sec, which is sufficient for the TDF STA to transmit at least one of the largest 802.1 1 PPDUs in a common time slot of the 54 mode, and there are a total of 62 times per TDF frame. groove. In this time slot, there are 20 uplink time slots and 40 downlink time slots in this way. When there are 20 STAs, each TDF STA can be guaranteed access to 680 kbps uplink data rate and share 30 Mbps (40 consecutive time slots) downlink data rate; when there are 30 STAs, Ensure that each TDF STA has access to the 680 kbps uplink data rate and share a 22. 5 Mbps (30 consecutive time slots) downlink rate. tdfMaximumUplinkTimeSlotNumber is 30. Finally, the value of tdfSuperframeDuration, which is the total duration of 61 common time slots and a synchronized time slot, is approximately 1 8.6 ms and can be determined 132611.doc -13- 200926708 is a different value for different uses. For example, if there is only one TDF STA, it can be guaranteed to have 4 time slots to achieve an uplink data rate of approximately 18 Mbps and its own 18 Mbps (4 consecutive time slots) downlink data rate. In this way, the total duration of the nine data time slots and one synchronization time slot. The number of time tdfSuperframeDurations is approximately 4 ms. Frame Format In the 802.1 1 specification, there are three main frame types. Use the data frame to exchange data between stations. Depending on the network, several different types of data frames can appear. The control frame is combined with the data frame to implement the regional clearing operation, channel acquisition, and carrier sensing maintenance functions and positive confirmation of the received data. Control and data frame joint operations to reliably deliver data between stations. More specifically, an important feature of data frame exchange is the existence of an acknowledgment mechanism, and therefore there is an acknowledgment (ACK) frame for each downlink unicast frame to reduce unreliable wireless The possibility of data loss caused by the channel. Eventually, the management frame performs a supervisory function: it is used to join and leave the wireless network and move the associated links between access points. However, in the TDF system, since the TDF STA passively waits for the target TDF AP to be found from the sync frame of the TDF AP, the classic probe request and the probe response frame are not required. In addition, the frames are exchanged over the coaxial cable rather than over the air so that RTS and CTS frames do not have to be defined to clean up an area and prevent hidden node problems, and an ACK frame is defined to ensure reliable delivery of the data frame. Therefore, in the TDF protocol, only some useful 802.1 1 MSDU and MMPDU types are used for the data in the coaxial cable scheme. For example, use the subtype of material in the frame type of 132611.doc -14- 200926708, which is used to encapsulate the upper layer data and transfer it from one station to another. In addition, in order to meet the clock synchronization requirements in the TDF system, a new management frame (synchronization frame) is defined; and in order to implement the functions of the uplink key slot request, allocation and release, four other management frames are defined. It is a registration request, registration response, non-registration request, and active notification. To outline the four new subtypes in the management frame type of the 'defined TDF agreement'. The following table defines the valid combinations of types and subtypes added to the TDF contract. Table 1 shows the valid types and subtypes of TDF frames added for use in the TDF protocol. Table 1 Type Description Subtype Description Management Synchronization Management Registration Request Management Registration Response Management Non-Registration Request Management Active Notification TDF Access Procedure

TDF AP finds timely synchronization procedures The TDF protocol largely depends on the distribution of timing information to all nodes. First, the TDF STA listens to the synchronization frame to determine whether there is an available TDF AP. Once it enters the TDF communication procedure, it uses the synchronization frame to adapt the area timer, and the TDF STA determines whether it is transmitting the uplink according to the timer. Road frame. Any time, tdf in the synchronization program? Department 132611.doc • 15· 200926708 Primary and TDF STA is subordinate. Furthermore, if it does not receive any synchronization frame from the associated AP within a predefined critical period defined as tdfSynchronizationCycle, the TDF STA will consider that the AP has abandoned the service and then it stops the TDF communication procedure and begins listening again. Synchronize the frame and look for any TDF AP. In a TDF system, all STAs associated with the same TDF AP will be synchronized with a common clock. The TDF AP will periodically transmit the special frame containing its clock information to be synchronized by the call to make the data machine in the local area network the same as the © step. Each TDF STA will maintain a Zone Timing Synchronization Function (TSF) timer to ensure that it is synchronized with the associated TDF AP. After receiving a sync frame, a TDF STA always accepts timing information in the frame. If the TSF timer is different from the timestamp of the received synchronization frame, the receiving TDF STA sets its regional timer according to the received timestamp value. In addition, it can add a small offset to the received timing value to resolve the area processing by the transceiver. The sync frame will be generated to be transmitted by the TDF AP once per TDF frame time unit and transmitted in the sync slot of each TDF frame. Registration Procedure Figure 6 illustrates the entire registration process illustratively. Once a TDF STA has obtained timer synchronization information from the sync frame, it will know when the time slot has started. If a TDF STA is not associated with any TDF AP, it will try to register with a particular TDF AP that transmits the registration request during the contention slot of the second time slot for a TDF frame. Frame to 132611.doc •16· 200926708 TDF AP and transmit the sync frame. The duration of the contention time slot equal to tdfCommonTimeSlotDuration, and the registration request frame structure should be carefully designed to allow at least tdfMaximumUplinkTimeSlotNumber registration request frames to be transmitted in a contention slot. According to the design, the contention time slot is divided into tdfMaximumUplinkTimeSlotNumber sub-time slots of the same length. As soon as the target TDF AP is found, a TDF STA will select a sub-time slot in the contention time slot to transmit a registration request frame to the TDF AP according to the following method: Α· Each time an uplink time slot is allocated, A TDF STA will store the number of allocated uplink key slots defined as tdfAllocatedUplinkTimeSlot indicating the location of the time slots in the slot pool and the range from 1 to tdfMaximumUplinkTimeSlotNumber throughout the uplink. B. The TDF AP shall allocate the same uplink time slot to the same TDF STA every time it requests an uplink time slot. » When it is decided to select the time slot, the registration request frame is transmitted. At the time, if there is a stored tdfAllocatedUplinkTimeSlot value ', the TDF STA will set the same number of sub-time slots as tdfAllocatedUplinkTimeSlot; if this value is not present, the TDF STA will randomly select a sub-time slot in the available sub-time slot of tdfMaximumUplinkTimeSlotNumber. It will transmit a registration request frame to the TDF AP in a randomly selected sub-time slot. The purpose of such an operation is to reduce the chance of collisions when there are many STAs that are simultaneously activated and the same TDF AP registration is used at the same time. 132611.doc • 17- 200926708 The TDF STA will list all the data rates it supports at the time and also carry some useful information, such as the received signal carrier/noise ratio in the registration request frame. It can start with the highest data rate and transmit several consecutive registration request frames at different support data rates. After transmitting the frame, the TDF STA will listen to the registration response frame from the TDF AP. After receiving a registration request frame from a TDF STA, the TDF AP will transmit a different kind of registration response frame to the TDF STA in the downlink time slot according to the following method: ® A. If the allocated uplink is The link time slot is equal to tdfMaximumUplinkTimeSlotNumber, and the TDF AP places the uplinkTimeSlotUnavailable indicator in the frame body. B. If the TDF AP does not support any data rate listed in the supportedDataratesSet of the registration request management frame, the TDF AP places the unsupportedDatarates indicator in the frame body. 0 C. If there is an available uplink for allocation The time slot and the common data rate that both the TDF AP and the TDF STA can support, the AP will allocate an uplink time slot and according to certain information (for example, the carrier/noise ratio of the STA's registration request frame) Selecting an appropriate common data rate and then transmitting a registration response frame to the TDF STA. The information about the assigned uplink time slot and the selected data rate will be included in the frame body. After a successful registration procedure, the TDF STA and the TDF AP will reach an information about which uplink time slot and data to use. Rate protocol. Segmentation/reassembly procedure 132611.doc -18 - 200926708 In the TDF protocol, the time slot duration for the transmission of the MSDU is fixed to tdfCommonTimeSlotDuration. In some data rates, when the length of the MSDU is greater than a threshold, it is not possible to transmit in a single time slot. Thus, when a data rate for uplink transmission is longer than a threshold defined as tdfFragmentationThreshold and varies according to different data rates, it is segmented before being scheduled for transmission. For all segments except the last segment that can be smaller, the length of a segment frame will be an equal number of octets (tdfFragmentationThreshold octet). After segmentation, the segmentation frame is placed in the delivery queue for transmission to the TDF AP. The segmentation procedure can be run in the TDF frame transport entity or upper layer by using the tdfFragmentationThreshold dynamically set in the TDF frame transport entity. At the end of the TDF AP, each received segment contains information to allow the complete frame to be reassembled from its constituent segments. The header of each segment contains the TDF AP for reassembling the message. The following information in the box: A. Frame type B. Address of the sender obtained from the address 2 block C. Destination address D. Sequence control field: This field allows the TDF AP to check all project segments. Belong to the same MSDU and the sequence that should be used to reassemble the segments. The sequence number within the sequence control block remains the same for all segments of an MSDU; the sequence number within the sequence control block is incremented for each segment. E. Multiple Segment Indicators: Indicates to the TDF AP that this is not the last segment of the data frame 132611.doc -19- 200926708. Only the last or only segment of the MSDU sets this bit to zero. All other segments of the MSDU set this bit to one. The TDF AP reconstructs the MSDU by combining the segments in the order of the segment number subfields of the sequence control field. If the segmentation of a multi-segment bit with a setting of zero is not received, then the TDF AP will know that the frame has not been completed. The TDF AP - receives a segment with multi-segment bits set to zero, which knows that no more segments are available for the frame. The TDF AP maintains a Receive Timer for each frame received. There is also an attribute tdfMaxReceiveLifetime that specifies the maximum amount of time allowed to receive a frame. The receiving timer is started after receiving the first segment of the MSDU. If the receiving timer exceeds tdfMaxReceiveLifetime, all receiving segments of the MSDU are discarded by the TDF AP. If additional segments that must be sent to the MSDU are received after their tdfMaxReceiveLifetime has passed, then the segments are discarded. Uplink Transmission Procedure After receiving a registration response frame from the TDF AP, the TDF STA will analyze the frame body to see if it is granted an uplink time slot. If it is not granted, it will stop for a while and apply for an uplink time slot later. If granted, it will begin transmitting uplink traffic during the assigned time slot using the data rate indicated in the registration response frame.

When the uplink transmission is started during the assignment time slot, if there is at least one external transmission frame in the transmission queue outside the TDF STA, the TDF STA will transmit the first frame to the external transmission queue to the TDF AP. Thereafter, the TDF 132611.doc -20·200926708 STA will check the length of the second uplink frame and evaluate whether the third uplink frame can be transmitted during the remaining duration in the assigned time slot. If not, it will stop the uplink transmission procedure and wait for the second uplink frame to be transmitted in the assigned time slot during the next tdf frame. If it is possible, it will immediately transmit the second frame to the destination and the AP. The transfer program will continue to run in this manner until the time slot has been assigned, or there are no uplink frames to transmit.

Downlink Transmission Procedure In the entire TDF communication procedure, the total number of downlink time slots may change dynamically due to changing the number of associated STAs. When the TDF Ap prepares the transmission frame to the associated STA, it compares the time left in the remaining downlink_ with the duration b required to transmit the particular downlink information frame using the protocol data rate. Therefore, depending on the result, it will decide whether to transmit the frame at a specific data rate during this period. In addition, tdf Μ does not need to fragment any downlink frames.

When the time of the uplink message is not transmitted to the associated STA, the STA always listens to the channel for the feasible τ line frame targeted for it. The non-registration procedure, as shown in Figure 7, if the TDF STA decides to abandon the TDF communication procedure, it sends a non-registration request frame to the associated TDF AP in its uplink time slot (four) to inform the TDF Ap to release The allocation of uplink time slot resources for it. After receiving the non-registration request frame, the uplink time slot for the TDF STA is freed and placed in the free time slot pool for future use. Ϊ 3261 l.doc 200926708 Active Notification Procedure Referring now to Figure 8, in order to release resources as soon as a TDF STA accidentally crashes or shuts down, the TDF STA must periodically transmit an active during its uplink time slot period. Notify the frame to the TDF AP and report its activity. If there is no active notification frame within a predefined critical period called tdfAliveNotificationCycle, the associated TDF AP will consider that the TDF STA has abandoned the service and thus release the uplink time slot allocated for the TDF STA, Just like receiving a non-registration request frame from the TDF STA. To ensure coexistence and interoperability on multi-rate capable TDF STAs, this specification defines a set of rules to be followed by all stations: A. The sync frame will be transmitted at the lowest rate of the TDF base rate set so that it will be used by All STAs understand. B. All frames with destination unicast addresses are transmitted at the supported data rate selected by the registration mechanism. No station transmits a single frame at a rate supported by the receiver station. C. All frames with destination multicast addresses are transmitted at the highest rate of TDF base rate concentration. 9 to 20 are explained as follows. At least Figures 9 through 20 illustrate embodiments that may be used, for example, in one or more of the systems illustrated by Figures 1-8. Of course, the features and aspects of the embodiments of Figures 9 through 20 can be used in other systems. As explained above, a TDF protocol can replace the traditional 802.1 1 DCF (distribution coordination function) or PCF (point coordination function) mechanism. This system can take advantage of the wide layout of WLAN (802.11) networks and a set of wireless local area network (WLAN) chips that may become more and more familiar and cheap. This system provides a cost-effective solution for two-way communication of CATV networks by transmitting WLAN signals in a cable network, even if a WLAN protocol is established to transmit/receive in the two-in-one network instead of the electric magic network. In this system, the basic access method of the Tdf protocol is TDMA' which allows multiple users to share the same channel by dividing the same channel into different time slots. These 1; 〇 17 units successively transmit uplink traffic in succession, each of which uses its own time slot in one of the TDF hypertext frames assigned by the 11) 17 Ap (access point). For downlink traffic, the stations share channels (eg, as shown in the TDF hyperframe of Figure 5) and are selected by comparing the destination address information of the frames to their addresses. It is the target frame. Referring to Figure 9, a typical TDF network is shown. The network 9 provides a connection from the user's home 910 and 920 to the Internet (or another resource or network). The user's homes 910 and 920 are connected via the access point (AP) 940 in the cable system 95. The AP 940 can be located, for example, at home 91〇 and 92〇 neighbors, or in the home (in this case) For the apartment) 91〇 and 92〇 in the apartment building. The AP 940 can be owned by, for example, a cable operator. The Ap MO is further coupled to a router 96 〇d router 960 in the Ethernet 970 and also interfaces to the Internet 930. _ It should be clear that the term, the conjunction "#" is directly connected (without intermediate components or units) and indirectly connected (- or multiple intermediate components and/or units). Such connections may be, for example, wired or wireless, as well as permanent or instantaneous. User homes 91 and 920 can have a variety of different configurations, and each can be configured differently. However, as shown in the network, the user's home "Ο 132611.doc 23 200926708 and 920 each include one (referred to as a data machine) 912 and 922 respectively. The data machines 912 and 922 are respectively in an Ethernet The networks 918, 928 are coupled to a first host (host 1) 914, 924, and a second host (host 2) 916, 926. Each of the hosts 914, 916, 924, and 926 can be, for example, a computer or another A processing device or communication device. There are various ways in which network 900 can allow multiple hosts (e.g., 914, 916, 924, and 926) to connect to router 960. Based on simplicity, only data machine 912 and hosts 914 and 916 are considered below. In the first method, the data machine 912 acts as another router. The hosts 914 and 916 are identified by their address, and the data 912 sends 11 packets from the hosts 914 and 916. Sent to router 960. This method 1 typically requires the data processor 912 to run the router software 'which requires additional memory and increased processing power. In a second method, the 'data machine 912 acts as a bridge. The data machine 912 and the AP 940 Use standard wireless distribution The system (WDS) mechanism transmits the layer 2 packets to the router 960. The hosts 914 and 916 are identified by their Media Access Control (MAC) addresses. This method 2 is part of the 802.1 1 standard and can simultaneously serve multiple Host. However, not all APs and modems support WDS, and APs and modems that do support WDS usually only have limited support. For example, some APs and modems cannot be used to access Wi_Fi (WP A). Used in WDS, and this may introduce security issues. In a second method, 'data machine 912 uses MAC priming to change the source MAC address of the local network packet (one of the source hosts 914 and 916) as Its own MAC address. Therefore, from the perspective of the router 96〇, the router 132611.doc -24- 200926708 960 only sees the data machine 912. The data machine 9! 2 adopts this method - only one host can be fed. In addition, the 'data machine 912 uses a packet, as explained in more detail below. Each of the above methods has advantages and disadvantages, and such advantages and disadvantages may vary depending on the implementation. However, the schematic method provides certain advantages. ' It is generally not necessary for the data machine to run the router software to allow the data machine to be simpler, it usually does not introduce security (4), and it can serve multiple hosts at a time. In addition, the 'packet method avoids and transmits by using a single WLAN packet. Each of the three methods from the host-package is associated with a large workload. Therefore, the 'first three methods incur the workload of the WLAN packets for each packet transmitted from the host' and correspondingly decrease Output. Such benefit rates are often exacerbated in the TDF environment. In the Qing environment, the duration of the time slot is fixed, * and the time slot is designed to allow only - WLAN

The package is transmitted in the - slot. Therefore, only one host packet can be transmitted in each slot. Therefore, the packet method generally provides one or more of various advantages. Such advantages include, for example, simpler router design and operation, increased security, servoing multiple hosts, and increased efficiency and output. In summary, at least one embodiment of the packetization method includes packetizing a plurality of Ethernet packets into one WLAN packet. The WLAN packet will be as large as the maximum length allowed by the TDF time slot. The Ap (e.g., another data machine) will de-packet the WLAN packet into an individual Ethernet to the router. For communication in the reverse direction, a data = seal: 132611.doc -25· 200926708 A WLAN packet and transmits an individual Ethernet packet to the (etc.) host. Referring to FIG. 10, a diagram 1000 includes a plurality of data machines, two of which are explicitly displayed; and a ΑΡβ narration includes a data machine Η 1〇1〇, a data machine #N 1020, and a ΑΡ 1030 Each of the data machines 1010 and 1020 is coupled to 1030 in a cable network 1〇4〇. Other embodiments use a separate cable network for each of the data machines. Data machines 1010 and 1020 and ΑΡ 1030 include functional components of the same name, although some of the external connections are different and the components themselves perform different functions on a data machine and a computer. Therefore, a common unit for use as a data machine and a pair is provided. However, it should be clear that different units can be designed for a data machine and a single unit, where different units only perform the functions required for a data machine or a separate unit. The data machine 1010 includes an area application layer 1011 followed by a TCP/IP layer 1012' followed by a bridge 1014. The bridge 1014 is coupled to an Ethernet interface 1015, a packet aggregation/de-collection module (PADM) 1〇16, and a WLAN interface 1017. The PADM 1016 is also coupled to the WLAN interface 1017. The Ethernet interface 1 〇 15 is coupled to the Ethernet 1 〇 52, which is coupled to a first host (host 1) 1054 and a second host (host 2) 1 〇 56. Data machine 1020 is similar to data machine 1010. However, the data processor is coupled to the Ethernet 1062, and the Ethernet 1〇62 is coupled to a first host (host 1) 1064 and a second host (host 2) 1066. The components of the modem 1020 are shown as being the same as the components of the modem 1 〇 1 。. However, it should be clear that when the data machines 1010 and 1020 are set up and operating, the various configuration parameters 132611.doc -26· 200926708 (for example) will be different. The AP 1030 includes a regional application layer 1071 followed by a TCP/IP layer 1072' followed by a bridge 1 74. Bridge 1074 is coupled to an Ethernet interface 1077, a PADM 1076, and a WLAN interface 1075. The PADM 1076 is also coupled to the WLAN interface 1075. The Ethernet interface 1077 is tied to an Ethernet 1〇82 ’, which in turn is integrated into a router 1090. The WLAN interfaces 1017 and 1075 are communicatively coupled to each other in the cable network 1〇4〇. Router 1090 is further coupled to the Internet 1〇95. Therefore, there is a connection between the host 1054 '1056, 1064, 1066 and the Internet 1〇95. The various regional application layers (1011, 1071) are standard layers for running regional applications and interfacing with other layers in the architecture. The various TCP/IP layers (1012, 1072) are standard layers for running TCP/IP and providing services typically provided by such layers, including interfacing with other layers in the architecture. Various Ethernet interfaces (1015, 1077) are used to interface to/from the standard unit of the Ethernet. Such interfaces 1015, 1077 transmit and receive Ethernet packets and operate in accordance with the Ethernet protocol. Various WLAN interfaces (1017, 1075) are used to interface to/from the WLAN network. Such interfaces 1017, 1075 transmit and receive WLAN packets and operate in accordance with the WLAN protocol. However, the WLAN interfaces 1017, 1075 are actually coupled to a cable network 1 〇 4 在 instead of using wireless communication. Ethernet, 132611.doc -27· 200926708 and WLAN interfaces 1015, 1017, 1〇75, and 1〇7^ can be implemented in, for example, a hardware such as a computer for inserting a card. Such interfaces are implemented in a software such as a program that performs the functions of the interface using instructions implemented by the processing device. This interface generally includes a portion for receiving the actual k number (eg, a connector) and buffering the received signal (eg, a transmit/receive buffer) and typically includes a portion for processing the signal (eg, a signal) Processing all or part of the wafer). The various bridges (1014, 1074) are units that forward packets between an Ethernet interface and a WLAN interface. A bridge can be implemented in software or hardware, or it can be just a logical entity. A standard implementation for a bridge includes a processing device (e.g., an integrated circuit) or a set of instructions running on a processor (e.g., one of the processors running the bridge software). The PADM 1016 performs various functions, including packet encapsulation and decapsulation, which are further described below. PADMs 101 6 and 1076 can be implemented, for example, in software, hardware, firmware, or some combination. Software implementations include, for example, an instruction set, such as a program for running on a processing device. Hardware implementations include, for example, a dedicated chip, such as an Application Specific IC (ASIC). Referring to Figure 11, a routine 1100 describes a procedure for transferring packets from a host to a modem. The packets are further transmitted from the modem for reception by an AP and finally delivered to a router and then to the final destination. This program 1100 is also referred to as an uplink transmission procedure. The program 1100 includes connecting the data machine to the AP (1110) using, for example, the procedure described earlier in this application. Such programs may include (eg, scooping standard WLAN protocols including authentication and associated operations. 匕 132611.doc • 28- 200926708 The program 1100 thus includes one or more hosts transmitting one or more packets (1120) to the data machine And the data machine receives the (etc.) transport packet (113 0). It should be noted that the transport packets are received by a router that delivers the (etc.) packets to the final destination. In the embodiment of FIG. 1, the data machine 1010 receives the transport packets from one or more of the hosts 1054 and 1056 over the Ethernet interface 1015 over the Ethernet 1052. The data machine therefore Deciding that the (etc.) packet will be transmitted (114 〇) on a WLAN interface. The modem makes this decision (1140) by identifying that the router is accessed on the WLAN interface, and in another The interface (not shown) has the opposite access. In the embodiment of Figure 10, the data machine transmits - (------) the packet is received to the bridge and the bridge 1014 makes this Decide (1140). The data machine therefore encapsulates multiple packets for the router. Comprising one or more information packets received ⑴50). The packet (1) 5) may include packets received from a plurality of hosts, such as the hosts 1054 and 156 in the embodiment of FIG. The 彳 封 packet may include the (4) packet received in operation 1130 and the packet received earlier and stored in the queue. In an embodiment that does not packetize multiple packets, the implementation may use a bridge to map the Ethernet packets to the individual machine packets, thereby individually packetizing each Ethernet packet. . This packet can, for example, include the entire Ethernet packet as part of the -WLAN packet and add an external WLAN header. In addition, the implementation of not including multiple packets does not even need to encapsulate individual Ethernet packets. Conversely, such an implementation may convert an individual Ethernet by, for example, replacing the Ethernet header with a WLAN header of 132611.doc -29-200926708 and by adding one or more additional fields as needed. The network packet is packaged into individual WLAN packets. For example, referring to FIG. 12, a conversion 1200 is shown that receives an Ethernet packet including an Ethernet header 1220 and a data portion 1230.

1210. The conversion 1200 generates a WLAN packet 1240 that includes a WLAN header 125A, a data portion 1230, and a frame check sequence (fcs) 1260 °.

However, the implementation operation 1 150 includes including a plurality of Ethernet packets into a single WLAN packet. Figure 13 illustrates one of the operations of Figure 11 . Referring to Figure 13', a conversion 1300 receives a plurality of Ethernet packets, including Ethernet packets 1310, 1312, and 13丨4, and generates a single WLAN packet 1318. Ethernet packets 131, 1312 and 1314

Net road signs (10), (10) and test, and include 3 materials Z 1326, 1328 and 1329 respectively. Ethernet packets 131, 1312 and 1314 can originate from the same host or different hosts. In addition, although the Ethernet packets (10), 1312, and 1314 are packetized for transmission to the router, the final destinations of the Ethernet packets 131(), m2, and (3)* may be different. For example, each of the Ethernet packets 1310, 13 12, and 13 14 may be at a destination of a different internet location with which one or more hosts communicate (or attempt to communicate) with one or more hosts. . The conversion test system (4) includes the second wealth (four). The scheme does not implement any intermediate operations between him and the other, and other implementations implement multiple 132611.doc -30- 200926708 first intermediate operating system to convert these Ethernet packets into extended Ethernet Packet. The Ethernet packets 131, 1312 and 1314 are converted into expanded Ethernet packets 1330, 1332 and 1334, respectively. In the conversion 1300, all Ethernet packets 1310, 1312, and 1314 are included to expand the data portions 1336, 1338, and 134 of the Ethernet packets 1330, 1332, and 1334, respectively. The extended Ethernet packets 1330, 1332 and 1334 also include optional headers 1342, 1343 and 1344' and optional endings 1346, 1347 and 1348, respectively. Headers 1342, 1343, and 1344 and endings 1346, 1347, and 1348 may include a variety of different pieces of information, whether or not they are typical for the header/end, such as the number of packets, confirmation and retransmission information, for source and/or The address of the destination, as well as error checking information. The second intermediate operation includes converting the expanded Ethernet packets into a single "WLAN In Wi-Fi" (EIW) packet 1350. The EIW Packet 1350 includes a data portion for each of these extended Ethernet packets. Show two possible conversions. The first transformation is illustrated by the solid arrow 1370 and the second transformation is illustrated by the dashed arrow 13 75. As indicated by the solid arrow 1370 in the conversion 1300, the data portions 1352, 1353, and 13 54 correspond to the included extended Ethernet packets 133, 13, 32, and 1334, respectively. The ugly 1\¥ packet 1350 further includes an optional header 1356 (also known as an EIW header) and an optional ending 1358, which may include, for example, any of the previously described data for the header/end By. If the header or the end is not inserted in an extended Ethernet packet, the data portion of the extended Ethernet packet (eg, data portion 1336) becomes the data portion of the EIW packet (eg, , data section 1352). In addition, 132611.doc -31 - 200926708 even if a header or trailer is inserted into the extended Ethernet packet, an embodiment can still discard/ignore the header or end when forming the EIW packet. In these cases, the data of the E-Taiwan Internet Packet and the information section of the Qingbao Packet have the same information. As indicated by the dashed arrow 1375 in the transformation 1300, the data portions 1352, 13 53 and 1354 do not have to correspond to the expanded Ethernet packets 133 〇 1332 and 1334, respectively. That is, one of the data portions of an EIW packet does not have to include an entire extended Ethernet packet. As indicated by the dashed arrow 1375, an extended Ethernet packet can be divided into data portions of two EIW packets. More specifically, the embodiment illustrated by the dashed arrow 1375 displays ο) placing the second portion of the extended Ethernet packet 1330 in the data portion 1352 of the EIW packet 1350, and (2) expanding the entire expansion. The network packet 332 is placed in the data portion 1353 of the EIW packet 1350, and (3) the first portion of the extended Ethernet packet 1334 is placed in the data portion U54 of the EIW packet 135. Therefore, in a scheme for the EIW packet n5, (1) the first data portion 1352 includes a portion of the extended Ethernet packet, and (2) the last data portion 354 includes a portion of the extended Ethernet network. The package, and (3) intermediate materials (1353 and any other data sections not explicitly shown) contain all of the extended Ethernet packets. Although not shown, it should be clear that the first part of the extended Ethernet packet U30 can be placed in one of the data sections of a previous mw packet, and (2) the second part of the Ethernet packet 1334 can be expanded. Place it in a data section of a subsequent EIW packet. In the final stage of the conversion 1300, the EIW packet 135 includes a data portion 136 中 in the packet 13 18 . |1^^ Packet 1318 also 132611.doc -32- 200926708 includes a WLAN MAC header 1362 and an FCS 1364. It should be clear that not all embodiments use all of the optional headers and endings' even without using all (or any) of the optional intermediate operations (also known as stages). For example, other embodiments only copy portions of the extended Ethernet packets into the EIW packets to fit more of the original data (e.g., data portions U26, 1328, and 1329) to a fixed duration slot. It should be clear that which headers and endings are used, and how many intermediate operations are included, can be made for each implementation and based on design goals and constraints. Referring to Figure 14, a diagram 1400 shows how an embodiment of a PADM encapsulates an Ethernet packet. The PADM maintains an entry queue 14 10 in which each item of the Ethernet packet is placed. The PADM chained these Ethernet channels into a series of 1420s, and added an EIW header 143〇 and a wlan header 1440. Based on the information included in headers 1430 and 1440, these headers 1430 and 1440 can be constructed early or after chaining the Ethernet packets. For example, at least one embodiment includes a number in the EIW header 1430 indicating the number of Ethernet packets in the string 1420. If the Ethernet packets can have a variable length&apos; then this number is typically not available until the Ethernet packets have been packaged into strings 1420. It should be clear that headers 1430 and 1440 can be defined to meet the needs of a particular implementation. Referring to Figure 15', a format 1500 of one embodiment of an EIW header is shown. The format 1500 includes a block 151 for the sequence and the confirmation number, a total number of packets 1 520, and a series of packet descriptors, including each Ethernet packet for packetization in the WLAN packet. One of the descriptors of the package. Since 132611.doc -33- 200926708 one of the 'expected packet descriptors has a variable number, as indicated by the ellipsis in FIG. Packet descriptors 1530 and 1540 are displayed, wherein each of the packet descriptors 1530 and 1540 includes a packet flag (155 〇 and 1555, respectively) and a packet length (1560 and 1565, respectively). The sequence number (1 5 10) provides a sequence identifier for the packet material that allows the recipient to confirm receipt of the transmission. The confirmation number provides confirmation of previously received data. The number of total packets is the number of Ethernet packets encapsulated in the WLAN packet. The packet flag (1 5 5 0, 1 5 5 5) indicates whether the associated Ethernet packet is a complete packet. If the time slot has a fixed duration, then it is possible that the entire Ethernet packet may not fit a given WLan packet. Therefore, it is contemplated in the particular embodiment that the first and last Ethernet packets are typically incomplete in any given WLAN packet. The packet length (156〇, 1565) indicates the length of the particular Ethernet packet. Continuing with the routine 1100, in the embodiment of Figure 1, the operation 1150 can be performed by, for example, the PADM 1016 of the data processor. Other embodiments may perform operation 115 in, for example, the bridge, the Ethernet interface, the WLan interface, another intermediate component other than the PADM, a component over the bridge, or a combination of components. 0. It should be clear that operation 115 can be implemented, for example, in software (eg, a program of instructions), hardware (eg, a 1C), firmware (eg, firmware embedded in a processing device), or a combination thereof ( Etc.) components. In addition, the PADM can be located at different locations within the data machine (eg, over the bridge or between the Ethernet interface and the bridge), in one of the interfaces or within the bridge, And/or distributed among multiple components when 13261I.doc -34- 200926708 0 The program 1100 further includes transmitting the packet to the AP (1160) in the battery. The transmission packet is expected to include the same power meter, a fiber optic gauge or its = line = media. When the slot of the uplink of the H-data machine of the embodiment H arrives, the data machine will collect the packet of the self-entry (4) and place it in a large

WLAN packet towel. The WLAN packet is not larger than the maximum packet allowed by the time slot. Conversely, when the time slot arrives, if the wlan packet is not large enough to fill the duration of the fixed slot, then an implementation will transmit a (smaller) WLAN packet, while another implementation transmits null data. (10)ll data) 〇 Refer to Figure 16 'Program 1' to describe a program for receiving packet packets, decapsulating the packets, and delivering one of the packets. This program is also known as the uplink receiving procedure. The program 1600 includes an Ap receiving a packet (1620) from a modem on a WLAN interface. In the embodiment of Figure 1, Αρ 1〇3〇 receives the packet from the data processor 1010. The packet is received on cable interface 1075 in cable network 1040 (e.g., a coaxial cable network). The AP decapsulates the packet to receive the packet forming the packet (in the embodiment of FIG. 1G, the WLAN interface (7) transmits and receives the packet to the PADM. PADM bribes are decapsulated and provided to form an Ethernet packet to the bridge. By checking (for example) the number of total packets (10)' and each packet descriptor (for example, packet descriptor (5) 〇) 132611.doc -35- 200926708 packet flag (for example, packet flag 1550) ) Decapsulation is performed with the packet length (for example, the packet length is 1560). By examining this information, PADM 1076 can determine where each of the constituent packets is opened and closed. Specifically, PADM 1076 checks each component packet to ensure that the packet is a complete Ethernet packet. If the packet is not complete, PADM 1076 retains the incomplete packet and waits until it receives the B. The rest of the network packet (presumably in the subsequent packet). When receiving the rest of the Ethernet packet, the PADM 1076 assembles the full Ethernet packet and forwards the full Ethernet packet to the bridge 1074. Referring to Figure 17, the above embodiment of operation 1630 is described in Figure 17A for receiving a packet 1710. Based on the simplicity, the received packet packet 1710 is assumed to be identical to the transport packet described with reference to FIG. However, it should be understood that there may be a change between a transmission packet and a reception packet. The receive packet 1710 includes a WLAN header 1440, an EIW header 1430, and a string 1420 that forms an Ethernet packet. As the PADM 1076 processes the received packet 1710, if a component of the Ethernet packet is complete, the packet (e.g., packet 1720) is provided to the bridge 1074. If a component of the Ethernet packet is incomplete, the incomplete packet is stored in a waiting queue 1730 (which does not have to be located in the PADM 1076) until the remainder of the packet arrives. Figure 1700 shows an incomplete packet 1740 stored in the waiting queue 1730. This can occur, for example, in the case of an Ethernet packet spanning two WLAN packets. When the packet is complete, the packet is transmitted to the bridge 1074. It should be noted that a WLAN may include, for example, a full Ethernet packet and a portion 132611.doc -36.200926708 Ethernet packet. Referring to Figure 18, to further illustrate the decapsulation process 1130, a PADM 1750 is described that provides an implementation of any of the PADMs 1016 or 1076. The PADM 1750 includes a packetizer 1760 and a depacketer 1770. Packetizer 1760 and depacketizer 1770 are communicatively coupled to a bridge and a WLAN interface. In the case of providing components of the PADM 1750, the PADM 175 0 may be more specifically referred to as a packet encapsulation/decapsulation module. In operation, packetizer 1760 receives an Ethernet packet from the bridge and encapsulates the Ethernet packets, as explained above. The packet data is then provided to the WLAN interface. In operation, the depacketer 1770 receives the packet information from the WLAN interface. The packetizer 1770 is decapsulated to receive the received data as described above and provides decapsulation information to the bridge. Clearly, other embodiments are possible and envisioned. For example, another embodiment combines a packetizer with a decapsulator. Another embodiment uses the virtual Ethernet interface feature of Linux. It should be noted that an AP or other embodiment of a modem directly transmits a packet from a WLAN interface to a bridge. The bridge determines that the packet is to be packetized and transmitted to a PADM. Continuing with process 1600, the AP determines that the component packets are to be transmitted to a router (1640). This operation can be performed at a different point in the program 1600 with a number of operations (1640). In the embodiment of Figure 10, bridge 1074 determines that the packets will be transmitted to router 1090. The AP then transmits the component packets to the 132611.doc • 37-200926708 router (1650) on an Ethernet interface. In the embodiment of FIG. 1 , the bridge 1 〇 74 transmits the component packets to the Ethernet interface 〇 77, which transmits the packets to the router 1 〇 9 on the Ethernet 1 〇 82. Hey. The router receives (1060) and processes (1〇7〇) the packets. Processing may include, for example, transmitting the packets or portions thereof to another destination, such as a website with which the host communicates or attempts to communicate. In addition, in an implementation in which one packet includes an Ethernet packet from multiple hosts, the router can transmit the underlying information to multiple websites. Referring to Figure 19, a routine 1800 depicts a procedure for receiving a packet from a router at an Ap. The packets are encapsulated and the packet is transmitted from the heart. The transport packet is expected to be received by a modem, and the component packet is expected to be finally delivered from the modem to one or more hosts. This procedure 1 800 is also known as the downlink transmission procedure. The program 1800 includes a router receiving one or more packets intended for one or more hosts (1820), and the router transmits the (etc.) received packets to the -AP (183〇). The router can receive packets from, for example, one or more websites that are tried and/or hosted by multiple hosts. In the embodiment of Figure 1, the router 1090 receives packets from the Internet 1095. The router 1〇9〇 then transmits the received packet to the Ethernet interface 1077 on the Ethernet 1082. The AP decides that at least the received packet will be transmitted to the datar (circle) on the _1 interface. In the embodiment of Figure 1G, the Ethernet interface sends a receive packet (which is an Ethernet packet) to the bridge (10) 74. The bridge will be transmitted on the WLAN interface to (for example) data 132611.doc -38-

φ 200926708 Machine 1010 〇 The Α 封 packet includes—or multiple packets of the received packet for transmission to the modem. New (4) Road (4) (4) There are multiple packets, {疋可月b has received the packets from one or more different sources "columns such as different websites" at the router. In addition, the packets can be included in the operation i The received packet and the packet received earlier and stored in a queue. With respect to operation 1850, in the embodiment of FIG. 10, the bridge ι 74 forwards the (equal) received packet to the PADM 1076. epADM 1 〇 76 arranges the (and other) received packets together with other packets intended for, for example, data machine 1010

A packet for the available downlink time slot of the data machine 1010. The PADM 1076 maintains a separate queue for each data machine (also referred to as a single), including a first queue for the data machine 1010 and a second queue for the data machine 1020. The packet is illustrated as described earlier with reference to Figures n through 15 of pADM 1016. The AP transmits a packet to the modem in a cable connection, which is expected to be delivered to one or more hosts (186 〇). In the implementation of Figure 1A, PADM 1076 prepares a WLAN packet for each of data machines 1〇1〇 and 1020 in a circular frequency format. The PADM 1076 then supplies the WLAN packet to the WLAN interface 1075 for insertion into the corresponding downstream key slot in the TDF frame structure. The WLAN interface 1075 then transmits the WLAN packet to the modems 1〇1〇 and 1〇2〇 using the TDF frame structure. Referring to Figure 20, a procedure 19 〇〇 describes a procedure for receiving a packet, decapsulating the packet, and delivering a packet. This program 900 is also referred to as a downlink receiving procedure. 132611.doc -39- 200926708 The program 1900 includes a number of broadcast axt^v devices that receive a packet from a frame on a WLAN interface (1920). In the Figure 1, the data machine 1010 receives the packet on the WLAN interface 1 〇 17 in a cable network 1040 (e.g., a coaxial ray glaze cable network). The data machine then goes to the packet to receive but receives the message: the message L extracts the component packet (touch) that constitutes the packet. In the embodiment of Figure 1G, the pADM is configured to decapsulate the packet and provide an Ethernet packet to the bridge i〇u. The de-packing can be performed as described earlier in the description of Figures 16 through 18. The modem determines that the component packets will be delivered to - or to multiple prospective host recipients. This operation can be performed at a different point in the program 1_ with many operations (1940). For example, operation 1940 can be performed in conjunction with any of operations 193, or 195. In the embodiment of Figure 1, the bridge ι 4 determines that the packet will be transmitted to the host. The modem then transmits the component packets to the host (195 ports) on an Ethernet interface. In the embodiment of Figure 10, the bridge 1014 transmits the component packets to the Ethernet interface 1〇15, which transmits the packets to the host over the Ethernet (7)! One or more of 1〇54 and host 2 1〇56. One or more hosts receive (1960) and process (1970) the packets. Processing may include, for example, a personal computer that stores multimedia files received on the Internet; a PDA that displays an electronic message (also received over the Internet) for viewing and interacting with a user . 21 to 34 will now be explained. However, the description of the embodiments represented by Figs. 21 to 34 is not limited to the following description. 132611.doc 200926708 In order to take advantage of the mature hardware and software implementation of 802.11 protocol stacking, the concept of 802.11 frames in coaxial cable media with different frequency bands for WLANs with modified WLAN (Wireless Local Area Network) chip sets has been proposed. Therefore, a TDF (Time Sharing Function) agreement is established to replace the traditional 802_11 DCF (Distributed Coordination Function) or PCF (Point Coordination Function) mechanism in the MAC (Media Access Control) layer for this application. As mentioned above, this TDF protocol is based on TDMA (Time Division Multi-Direction), which allows multiple users to share the same channel by dividing the same channel into different time slots. The TDF STAs quickly and successively transmit uplink traffic, each of which uses its own time slot in one of the TDF super-frames assigned by the TDF AP (access point). For downlink traffic, the STAs share the channel and select the frame to target by comparing the destination address information in the frame with the address of interest. Figure 5 illustrates time slot allocation for a typical TDF hyperframe when there are m (= tdfUplinkTimeSlotNumber) STAs that are simultaneously competing for uplink transmission opportunities. As shown and described with respect to FIG. 5, there is a time slot of a fixed number of TDF frames (tdfTotalTimeSlotNumber), which is composed of: one for transmitting the clock step information from the TDF AP to the TDF STA ( 1) Synchronization time slot, one of the registration requests for transmitting the time slot allocation for the uplink (1) the competition time slot, the tdfUplinkTimeSlotNumber uplink used by the registered TDF STA for successive transmission of data and some management frames to the TDF AP. The link time slot and the tdfDownlinkTimeSlotNumber downlink time slot used by the TDF AP to transmit data and some management frames to the STA. Except for the sync slot, all other slots known as the common slot have the same 132611.doc •41 · 200926708 duration, which is equal to tdfCommonTimeSlotDuration. The duration value of tdfCommonTimeSlotDuration is defined to allow transmission of at least one of the largest 802.1 1卩1^? (physical layer convergence protocol) protocol data elements (??〇1;) in one of the normal time slots of the highest rate data mode. The duration of the synchronization slot tdfSyncTimeSlotDuration is shorter than the duration of the co-located slot because the clock synchronization frame transmitted from the TDF AP to the TDF STA in the slot is shorter than the 802.1 1 data frame. Therefore, the duration of a TDF hyperframe defined as tdfSuperframeDuration can be calculated by the following equation: tdfSuperframeDuration = tdfSyncTimeSlotDuration + tdfCommonTimeSlotDuration * (tdfTotalTimeSlotNumber - 1) tdfTotalTimeSlotNumber ' The relationship between tdfUplinkTimeSlotNumber and tdfDownlinkTimeSlotNumber satisfies the following equation: tdfTotalTimeSlotNumber = tdfUplinkTimeSlotNumber + tdfDownlinkTimeSlotNumber + 2 In a practical application scenario where a WLAN chipset with a reduced frequency band is used to provide data transmission over a CATV access network, there are typically two applications. An application uses this solution to provide Internet access, so users must be assigned a guaranteed time slot to achieve constant data rate and QoS (quality of service). Another application uses this solution to transmit sporadic uplink traffic from the user side to the headend, such as user control messages in VoD (Video on Demand) applications for digital TV services. Using the above proposed MAC layer mechanism, the STA uses an AP registration to first acquire an uplink time slot, and then transmits such control information for 132611.doc -42 - 200926708 in each slot allocation time slot. However, because the traffic for such applications is extremely low', the STA needs to use a very small portion of the time slot for data transmission, and even 'quite quite even for supporting such applications with sporadic traffic. There are still no traffic to be transmitted during the number of consecutive hyperframes of the TDF STA. Therefore, those skilled in the art will appreciate that in some scenarios, it may be quite costly to support this second application using a purely time-sharing media access method previously established and known in the TDF protocol. According to other known embodiments, a TDF STA with occasional uplink traffic to transmit and no TDF AP registration for uplink time slot allocation during the contention-based uplink time slot will use DCF The mechanism transmits uplink traffic to the TDF AP. However, due to the inherent nature of the DCF mechanism, it is possible that a TDF STA will have a greater chance of accessing the channel for uplink traffic transmission than the STA if it always uses a smaller contention window to obtain transmission opportunities. . Moreover, a fair distribution of transmission opportunities cannot be achieved among such TDF STAs that use a contention-based media access method for uplink traffic. This disclosure suggests at least two TDFs to support data services and sporadic user control messages over the cable access network. The first type of TDF uses both polling and time-sharing media access, and the second type of TDF uses a hybrid mechanism to obtain the upstream channel. Variations and other combinations, such as the use of polling and a competition-based hybrid mechanism, are imaginary and part of this disclosure. Referring to Figure 21, in order to provide 132611.doc -43-200926708 support for both high data rate services with Q〇s support and other services with sporadic data traffic and latency tolerance characteristics, an advanced technology TDF is shown, Both polling and time-sharing media access mechanisms including access to the uplink channel are included. The suggested TDF with polling and time-sharing media access adds a time slot (e.g., a polling slot) to one of the time slots used in the previous implementation of the TDF program. As shown in Fig. 21, there is a time slot of a fixed number of TDF frames (tdfTotalTimeSlotNumber), and the detailed function series for each of the time slots included therein is as follows: &gt; One (1) sync slot. This synchronization slot of the synchronization time slot is used to transmit clock synchronization information from the TDF AP to the TDF STA. &gt; One (1) registration slot. The registration slot (ie, the registration time slot) is used by the TDF STA to transmit a registration request to the TDF AP. In the registration request frame body, the TDF STA will inform the AP of its operation mode, polling mode or time-sharing mode to obtain an uplink transmission request. &gt; One (1) polling slot. During this time slot, TDF STAs with occasional uplink traffic to transmit and not using TDF AP registration for uplink time slot allocation will transmit uplinks using the specific PCF (Point Coordination Function) mechanism detailed below. Link traffic to the TDF AP. &gt; Downstream key time slot. These slots contain tdfDownlinkTimeSlotNumber downlink time slots, which are used by the TDF AP to transmit data and some management frames to the TDF STAs.

&gt; Time-sharing uplink time slot. These slots contain tdfUplinkTimeSlotNumber uplink time slots, which are used by the registered TDF STA to successively transmit data and some management frames to TDF 132611.doc -44- 200926708 AP with high data rate and QoS support. Depending on the requirements of the particular application, the duration of the slots for the synchronization time slot, the registration time slot, the polling time slot, the downlink time slot, and the time-sharing uplink time slot are different in most cases. However, each upstream key slot in the tdfUplinkTimeSlotNumber time-sharing slot, called the common time slot, has the same duration equal to tdfCommonTimeSlotDuration. Therefore, the duration of a TDF hyperframe defined as tdfSuperframeDuration can be calculated by the following equation: tdfSuperframeDuration = tdfSyncTimeSlotDuration + tdfRegTimeSlotDuration + tdfPollingTimeSlotDuration + tdfCommonTimeSlotDuration * (tdfTotalTimeSlotNumber - 3) The relationship between tdfTotalTimeSlotNumber, tdfUplinkTimeSlotNumber and tdfDownlinkTimeSlotNumber satisfies the following Eq: tdfTotalTimeSlotNumber = tdfUplinkTimeSlotNumber + tdfDownlinkTimeSlotNumber + 3. Enhanced PCF Procedure During Polling Time Slots For STAs in this TDF with both polling and time-sharing media access mechanisms, various implementations include two modes of operation: one is a polling mode; and the other is a time-sharing mode . The basic media access method for the STA operating in the polling mode for uplink traffic transmission is the PCF. However, several improvements to this classic PCF mechanism have been made due to the specific environment for the transmission of data 132611.doc -45- 200926708 on the fixed line. Basic Access The PCF mechanism in the slot provides a non-competitive frame transmission. Referring to Figure 23, the PC (Point Coordinator) 2302 is resident in the TDF AP 2300. The form of the polling mode support provided by the AP 2300 is identified in the capability information field of the beacon frame transmitted from the APs. The TDF STA 2304, which requires poll-based media access, should be able to respond to the contention-free polling (CF polling) received from an AP 2300, and is therefore referred to as CF-capable polling. When polled by PC 2302, the CF pollable STA will transmit only one MPDU (MAC Protocol Material Unit), which will be transmitted to the AP and the MPDU is not required to be acknowledged by the AP. An AP never rounds the STA that is not in the polling list of this AP. The frame transmitted by an AP or STA during the polling slot will use the appropriate frame type according to the following usage rules: 1 - CF Polling, which is transmitted by only one AP to the CF-capable STA. In this frame, the AP is not transmitting data to the address recipient, and the address receiver is allowed to transmit the next STA during the polling time slot; and 2 - data and null frames can be any CF Poll the STA transmission. The AP gets media control at the beginning of the polling slot and attempts to maintain control of the entire polling slot. It does not require the start and end of the polling slot to be sent by the AP transmitting a beacon and the CF, respectively, as required in the Classic PCF protocol. When there is an entity in the polling list, the AP will transmit a CF poll to at least one STA during each polling slot. During each polling slot, the 132611.doc -46- 200926708 AP will post a subset of the STAs polled to the polling list in order from beginning to end. Referring to Figures 24 and 25, once each polling slot begins, the AP will transmit (25 06) - the CF poll frame to one of the STAs in the polling list. If there is no entity (2502) in the polling list, the AP will immediately transmit downlink traffic (2504) during this polling time slot until the downlink time slot ends. The AP then resumes control after receiving a data or null frame from the particular CF-capable STA (2508), or after receiving a response to the CF poll from a particular STA within a predefined period immediately following the AP transmission. The next CF round inquiry frame can be transmitted to the next entity in the polling list, unless there is insufficient time during the current polling period. If at this point it has reached the last item in the polling list, the next time the AP will attempt to transmit a CF round of inquiries to the STA from the first item in the polling list. If the current polling period does not hold enough time (2510) to allow the polling STA to transmit the data frame containing the minimum length MPDU, the AP will not issue a CF round inquiry frame. Conversely, if the last item in the STA list has been polled at the beginning of the polling time slot during the next hyperframe, the AP begins to issue a CF round inquiry frame to the polled STA of the polling list. The next item in the box, or the first item in the polling list.

Referring to Figure 24, all CF-capable STAs in the polling mode associated with this AP should not transmit any uplink traffic unless it is polled by the AP during this polling slot. One of the polling modulo CF polling STAs always responds to CF polling that leads to its MAC address and receives without error. It will transmit a data frame immediately after receiving the CF poll. If the STA 132611.doc -47- 200926708 does not have a frame to transmit when polling, the response will be a null value frame. Before the end of the polling slot for transmitting its aligned data frame, there is insufficient time for one of the polling CF polling STAs to respond by transmitting a null value frame. Polling list maintenance, this will maintain a "polling list" for selecting STAs that meet the criteria for receiving CF polls during the polling slot and for polling the CF polling STAs. The polling list can be used to control the use of the CF polling type for transmitting the data frame transmitted by the UI to the CF-capable STA. Receiving a registration request frame from a STA, wherein the STA needs to use a polling mechanism to access the channel, and the node decides to authorize the STA to transmit the transmission mechanism according to the setting policy in the UI, ΑΡ An item will be added to the end of the polling list, which includes the STA's MAC address and data rate. On the other hand, once an AP receives an unregistered frame from a STA indicating that it will not access the channel using the polling mechanism, the AP will delete the corresponding entry for the STA in the polling list. If a STA needs to change from a time-sharing mode to a polling mode, the STA will notify the AP by transmitting a non-registration to abandon the time-sharing mode and then transmitting a registration request with a polling mode indication to the AP. Referring to FIG. 22, in order to enjoy the flexibility provided by the DCF and the fairness provided by the PCF, a hybrid medium access mechanism for uplink traffic is also described, which uses both DCF and PCF for the STA to obtain For sporadic traffic transmission opportunities, and dedicated time slots for STAs to transmit high data rate traffic. A detailed time slot allocation for this enhanced TDF hyperframe is illustrated in FIG. As shown, there are fixed tdfTotalTimeSlotNumber 132611.doc -48- 200926708 time slots per TDF hyperframe, and the detailed functions for each of the time slots contained therein are listed below: &gt; One (1) sync slot. This synchronization slot of the synchronization time slot is used to transmit clock synchronization information from the TDF AP to the TDF STA. &gt; One (1) contention-based uplink slot. During this slot, the TDF STA can transmit a registration request to the TDF AP. In the registration request frame body, the TDF STA will inform the AP of its mode of operation, polling, contention-based or time-sharing mode to obtain an uplink transmission request. At the same time, TDF STAs with occasional uplink traffic to transmit and not using TDF AP registration for uplink time slot allocation will use the specific DCF mechanism to transmit uplink traffic to the TDF AP. &gt; One (1) polling slot. During this time slot, TDF STAs with occasional uplink traffic to transmit and not using TDF AP registration for uplink time slot allocation will transmit uplink traffic to the TDF using the specific PCF mechanism previously described. AP. In general, the TDF STA can inform the TDF AP of its mode of operation (i.e., DCF or PCF) by setting a corresponding flag in the associated request frame transmitted by the TDF STA to the TDF AP. &gt; Downstream key time slot. These slots contain tdfDownlinkTimeSlotNumber downlink time slots, which are used by the TDF AP to transmit data and some management frames to the TDF STAs.

&gt; Time-sharing uplink time slot. These slots contain tdfUplinkTimeSlotNumber uplink time slots, which are used by the registered TDF STA to transmit data and some management frames successively to TDF 132611.doc -49- 200926708 AP with high data rate and QoS support. Depending on the requirements of the particular application, the duration of the slot for the synchronization time slot, the contention base time slot, the polling time slot, the downlink time slot, and the time-sharing uplink time slot are different in most cases. Therefore, the duration of a TDF hyperframe defined as tdfSuperframeDuration can be calculated by the following equation: tdfSuperframeDuration = tdfSyncTimeSlotDuration + tdfContentionTimeSlotDuration + tdfPollingTimeSlotDuration + tdfCommonTimeSlotDuration * (tdfTotalTimeSlotNumber - 3). The relationship between tdfTotalTimeSlotNumber, tdfUplinkTimeSlotNumber and tdfDownlinkTimeSlotNumber satisfies the following equation: tdfTotalTimeSlotNumber = tdfUplinkTimeSlotNumber + tdfDownlinkTimeSlotNumber + 3 0 This principle suggests a TDF that uses both contention-based and time-sharing media access to obtain uplink channels so that Support data access on the cable access network and occasional user control messages. In order to provide support for both high data rate services with QoS support and other services with sporadic data traffic and latency tolerance characteristics, an advanced technology TDF is shown that includes competition for uplink channel access. Basic and time-sharing media access mechanisms. The following is a detailed description of the functional description of this TDF protocol using the mixed media access method. Access Method 132611.doc -50· 200926708 Adding a time slot to the TDF using both the competition-based and time-sharing media access of the present principles (for example) , a registration slot) to the previously revealed TDF program. The detailed time slot allocation for this enhanced TDF hyperframe is illustrated in Figure 26. As shown in Fig. 26, there is a time slot of a fixed number of TDF frames (tdfTotalTimeSlotNumber), and the detailed functions for each of the time slots included therein can be enumerated as follows: - One (1) sync slot. This synchronization slot of the synchronization time slot is used to transmit clock synchronization information from the TDF AP to the TDF STA. - One (1) registration slot. A registration slot (ie, a registration time slot) that can be compared to a contention time slot in the hyperframe structure illustrated in FIG. 5 is used by the TDF STA to transmit a registration request to a TDF AP for uplink time slot allocation. A (1) contention-based uplink time slot" during this time slot, TDF STAs with occasional uplink traffic to be transmitted and not used for uplink time slot allocation TDF STAs will be used The specific DCF mechanism detailed below transmits uplink traffic to the TDF AP. - Time-sharing uplink time slot. These slots contain tdfUplinkTimeSlotNumber uplink time slots, which are used by registered TDF STAs to transmit data and some management frames successively to TDF APs with high data rate and QoS support.

- Downlink time slot. These slots contain tdfDownlinkTimeSlotNumber downlink time slots, which are used by the TDF AP to transmit data and some management frames to the TDF 132611.doc • 51 - 200926708 STA. In one embodiment, the registration slot and the contention based uplink time slot can be combined into a mixed time slot to improve system performance. This improvement will be due to the fact that both slots will use the contention-based fallback method for channel access. In most cases, there may be few transactions during the registration slot. In addition, the CWmin and CWmax of the competition window for the registration request can be defined as CWmin and CWmax which are smaller than the competition window for the data frame respectively, so as to provide a higher transmission rate than the data frame for the transmission of the registration request frame. Priority. Those skilled in the art will recognize that the "competition window" is for the 802.1 1 standard and indicates how many hours the STA will wait before attempting to access the wireless medium and then decide whether the medium is available to the user for transmission of data (eg, 9) Us) By way of example, the exact contention window is initially determined by selecting the number of random backoffs between 0 and CWmin. Each time the back-off period expires, indicating that the channel is still busy, the STA will randomly select another back-off period between 0 and a number of [CWmin, CWmax] in an incremental manner, φ until 0 is selected The last backoff period between CWmax. CWmin and CWmax defined by the competition window for the registration request frame are smaller than CWmin and CWmax for the competition window respectively used for the data frame, ie (CWmin for registration) &lt; (CWmin for data frame) And (CWmax for registration) &lt; (CWmin for data frame), ensuring priority over the transmission of the registration request frame of the transmission of the data frame. As explained below, this higher priority is due to the smaller number of backoff periods available during the smaller competition window. 132611.doc -52- 200926708 The duration for synchronization time slots, registration time slots, contention-based time slots, time-sharing uplink time slots, and downlink time slots is large, depending on the requirements of a particular application In most cases, they are different from each other. However, each of the tdfUplinkTimeSlotNumber time-sharing slots is called a common time slot, and one uplink time slot has the same duration whose length is equal to tdfCommonTimeSlotDuration. Therefore, the duration of a TDF hyperframe defined as tdfSuperframeDuration can be calculated by the following equation: tdfSuperframeDuration = tdfSyncTimeSlotDuration + tdfRegTimeSlotDuration + tdfContentionTimeSlotDuration + tdfCommonTimeSlotDuration * (tdfTotalTimeSlotNumber - 3) ° The relationship between tdfTotalTimeSlotNumber, tdfUplinkTimeSlotNumber and tdfDownlinkTimeSlotNumber is satisfied歹 ij equation: ❺ tdfTotalTimeSlotNumber = tdfUplinkTimeSlotNumber + tdfDownlinkTimeSlotNumber + 3 〇 In addition, the number of allocated uplink time slots of the TDF STA in a TDF frame can be changed from 0 to tdfMaximumUplinkTimeSlotNumber. Therefore, the available duration of the downlink time slot in a TDF hyperframe can be changed from (tdfCommonTimeSlotDuration * (tdfTotalTimeSlotNumber -3)) to tdfCommonTimeSlotDuration * (tdfTotalTimeSlotNumber -3 - tdfMaximumUplinkTimeSlotNumber)) 132611.doc -53- 200926708 per When there is a TDF STA that requires an uplink time slot, the TDF AP will infer one or more common time slots from the available downlink time slots, and then allocate the time slots to the TDF STA as long as the uplink The waylot will not exceed tdfMaximumUplinkTimeSlotNumber after it. ^ Furthermore, although the duration of the slot for the downlink is equal to (tdfCommonTimeSlotDuration * tdfDownlinkTimeSlotNumber) » it is not necessary to have the guard time between the boundaries of these common time slots, since the slots are continuous and from the downlink An independent AP transmits traffic. © In this way, the downlink transmissions in this protocol will be highly efficient and channel utilised. Enhanced DCF Procedure for Contention-Based Uplink Time Slots For STAs in this TDF with both contention-based and time-sharing media access mechanisms, several implementations have two modes of operation: one system Based on competition, the other is time-sharing. The basic media access method for STAs operating in a contention-based mode of uplink traffic transmission is the DCF defined in the 802.1 1 specification, which allows for the use of CSMA/CA (carrier collision avoidance for collision avoidance). Automatic media sharing is performed immediately after random back-off time following busy media conditions. However, several improvements to this classic DCF mechanism have been made due to the specific environment of data transmission on the fixed line. Random Backoff Procedure A TDF STA that initiates the transmission of the frame calls the carrier detect mechanism (in most cases the physical carrier detect) to determine the busy/idle state of the media. If the media is busy, the STA is deferred until the media system decides to be idle 132161.doc -54- 200926708 and is not interrupted during the defined time period. After this media idle time, the STA generates a random backoff period for the extra delay time before transmission, unless the back-off timer already contains a non-zero value, in which case the selection of the random number is unnecessary and not implemented. This procedure minimizes collisions during the competition between multiple STAs that have been postponed to the same event. Back time = Random() * aSlotTime where

Random() = pseudo-random © integer from a uniform distribution in intervals [0, CW], where CW is an integer in the range of aCWmin and aCWmax, aCWmin &lt;= CW &lt;= aCWmax.

The set of CW values will be a sequence of 2 increments of the integer power minus 1, starting with the special application aCWmin value and continuing upwards and including a special application aCWmax value. More specifically, for most of the application environment for this agreement, the maximum number of STAs in the competition-based model (which is tdfMaximumContentionStationNumber) is known in advance and can be manually configured and/or broadcast from TDF APs. The management frame is notified to the TDF ❹ STA, so the aCWmax value can be set to a multiple of tdfMaximumContentionStationNumber or tdfMaximumContentionStationNumber. Therefore, the STA can access the physical medium after a relatively short back-off time when compared to the condition in which the aCWmax value is blindly set. By reducing the size of the contention window for the registration frame, the number of available backoff periods will be less than the number of backoff periods available for the data frame, resulting in a higher priority registration frame. Confirmation procedure 132611.doc -55- 200926708 For TDF STAs operating in time-sharing mode, the STA-derived frame is switched in a wired environment rather than over the air during the allocation of the uplink time slot for this particular STA, so It is transmitted in a non-competitive manner with excellent signal quality. Therefore, it is not necessary to define an acknowledgment (ACK) frame to ensure the reliability of the delivery of the MAC frame. However, for TDF STAs operating in a competition-based mode, because of the difference between the wired environment and the wireless channel, the physical carrier sensing mechanism does not work extremely well in the fixed line, so the hidden table problem will be The competition® mode causes many collisions among different TDF STAs. As a way to combat this failure, this principle recommends the use of a positive confirmation mechanism. Therefore, there are two kinds of acknowledgments that can be used for configuration: 1. This AP—initiating an uplink frame originating from a TDF STA in a contention mode, immediately acknowledges from the TDF AP, and therefore, if no ACK is received, Then, the TDF STA schedules retransmission. 2. Block ACK mechanism that improves channel efficiency by grouping several acknowledgments into one frame. There are two types of block ACK mechanisms: immediate and delayed. The immediate block ACK is immediately transmitted by the TDF AP after being a number of uplink frames from a TDF STA in the contention mode, and is suitable for high frequency wide and low latency traffic. The delay block ACK is transmitted by the TDF AP at the beginning of the downlink time slot in the same hyperframe as the contention-based uplink time slot in response to the TDF during the time slot based on the specific contention. Several successfully transmitted uplink frames transmitted by the STA. It is suitable for applications that tolerate moderate latency 132611.doc -56- 200926708 and will be used for most of this TDF agreement with contention-based and time-sharing media access control. The block ACK frame may be a unicast frame in a competition mode to a specific TDF STA to notify it of successful reception of its uplink frame, and may also be a broadcast or multicast frame for notification. The number of TDF STAs in the contention mode successfully received from the uplink frames of the STAs. Operational Mode Conversion Procedure Once a TDF STA is initiated (e. g., after initialization), it enters a competition-based mode by a preset. Then, depending on its application requirements, configuration, and/or service provider's service level agreement, it can enter the time-sharing mode after transmitting the registration frame to the TDF AP and receiving the registration response with access permission. The transition from a competition-based mode to a time-sharing mode is illustrated in FIG. As shown, when in the competition-based modulo 2710, it is decided (2712) whether or not it is necessary to enter the time-sharing mode. When the answer is yes, then it is determined (2714) whether a positive response has been received after the TDF STA has transmitted a registration request to the TDF AP. If a positive response has been received, then the time sharing mode 2716 is entered. If the decision 2712 or 2714 produces a negative response, the system remains in the competition-based modulo 2710. In contrast to the embodiment shown in Figure 27, a TDF STA can enter a competition-based mode from a time-sharing mode during its operation. This concept is illustrated in Figure 28. As shown, when in time-sharing mode 2802, it is decided (2804) whether a competition-based mode is required. If necessary, a non-registration request (2806) is transmitted and the competition-based modulo 2808 is entered. If the competition-based module (2804) is not required to enter 132611.doc -57- 200926708, the system remains at 2802. It should be noted that similar procedures can be applied to the polling implementation. For example, the implementation can switch between polling mode and time-sharing mode as needed. As explained above, in order to provide a cost effective two-way data transmission solution over existing coaxial cable access networks, a method has been established for integrating mature products with external frequency conversion circuits for frame delivery. The system using this method is called the AD〇c (Asymmetric Coaxial Cable Data) system, in which the TDF (Time Sharing Function) protocol must be configured in the cable access network to comply with the ADoC Access Point (AP) and the station (STA). ). The terms "ADoC system" and "TDF system" are used interchangeably herein. The AP and STA are connected via a splitter in the hierarchical tree structure (see Figure 丨). In this way, users at home can access the remote core network via a cable access network. The detailed network layout is illustrated in Figure 1. In this typical infrastructure access network architecture, there is a TDF protocol adaptation ADoC (TDF) access point (AP) that has an Ethernet interface through which the AP is connected to the ip core network. And a coaxial cable interface through which the AP is connected to the cable access network. At the other end of the access network, there is a TDF protocol adaptation ad〇C (TDF) STA, which is connected to the cable access network via a coaxial cable interface, and via a wireless interface (such as WLAN (Wireless Local Area Network) ) interface) or a wired interface (such as an Ethernet interface) to connect to a resident LAN (local area network). Referring to Figure 29, an embodiment of an embodiment of a hardware implementation for an ADoC STA 2900 integrates two devices (an ADoC device 2903 and a WLAN device 132611.doc 58-200926708 2904) into a composite STA. The ADoC device 2903 will interface with a coaxial cable interface 2906 to support bidirectional data communication in the cable network, while the WLAN device 2904 will interface with an antenna 2908 to support bidirectional data communication in the WLAN network. The STA 2900 will exchange the data frame between the ad C device 2903 and the WLAN device 2904 as needed to enable the PC in the WLAN network to access the Internet via the ADoC STA. The STA presented in Figure 29 requires two separate devices for channel encoder/decoder and data processing to provide Internet access for personal computers in a home WLAN. The present principles provide a solution that utilizes a single dual mode device and can periodically switch between the ADoC mode and the WLAN mode to provide the same access to the local area network. The dual mode ADoC device of the present principle can support both the ADoC mode and the WLAN mode and periodically switch between the two modes. In the AD〇C mode, the dual mode device operates as an ADoC STA; and in the WLAN mode, it operates as a WLAN AP. By using a single dual-mode device solution of the present principles, rather than two of the classic solutions shown in Figure 29, the ADoC STA embedded in the dual-mode ADoc device can provide Internet access to the local area network. Features. Thus, the manufacturing cost of an ADoC STA with Internet access support via a cable access network can be reduced by half the cost of the original compared to the classic solution of the two devices shown in FIG. To implement the dual mode device 2902 of the present principles, a standard ADoC device 2903 is modified and developed in accordance with a mature WLAN device. It differs from WLAN device 2904 mainly in two aspects: 1) In the physical implementation aspect, its RF is 132611.doc • 59- 200926708 ADoC band (about 1 GHz) instead of standard 802.1 1 band (about 2.4 GHz) ); and 2) in the MAC (Media Access Control) layer, which does not utilize the traditional 802.1 1 DCF (Distributed Coordination Function) or PCF (Point Coordination Function) mechanism to exchange MAC frames. Instead, it uses the TDF protocol, which is based on the Time Division Multiple Access (TDMA) method to transmit MAC frames.

As shown in Figure 30, dual mode ADoC device 2902 will be coupled to a coaxial cable interface 2906 for interconnection with a cable access network and simultaneously coupled to an antenna 2908 to support bidirectional data communication in a WLAN network. The ADoC © STA 2900 will exchange the data frames received from this dual mode ADoC device 2902 during the two modes as needed. The hardware architecture of the dual mode ADoC device is based on a hardware implementation of the dual mode ADoC device 2902 shown in FIG. 31, providing a switch 3 1 02 that is configured for use in the WLAN RF circuit 3 104 and the ADoC RF A circuit that switches between circuits 31 06. The switch 3 1 02 can be controlled by the MAC layer software. This embodiment requires modifying the WLAN die set and adding switch 3 1 02 to the modified wafer set. According to another hardware embodiment shown in Fig. 32, the position of the switch 3102 can be changed in accordance with the proximity of the MAC baseband portion 3100 of the device. In this embodiment, converter 3108 reduces the WLAN band (which is the output of WLAN RF 3 104 and is about 2.4 GHz) to the ADoC spectrum (which is about 1 GHz) and can reach a relatively long distance in the coaxial cable. It should be noted that the MAC baseband portion 3 100 may be characterized by a communication device configured to enable a user device to communicate with the dual mode ADoC device 2902. In contrast to the embodiment of Figure 31, the embodiment of Figure 32 is external to the existing 132611.doc-60-200926708 WLAN chipset, and likewise does not require modification of the WLAN chip set. MAC Layer Program for Dual Mode ADoC Devices In dual mode ADoC device 2902, the basic access method is the TDF protocol, which is the same as the MAC layer protocol in ADoC device 2903. As shown in FIG. 34, there is a time slot of a fixed number of TDF frames (tdfTotalTimeSlotNumber), which is composed of the following items: a synchronization time slot for transmitting clock synchronization information from the ADoC AP to the ADoC STA, a competing time slot for transmitting a registration request for uplink time slot allocation, tdfUplinkTimeSlotNumber uplink time slots used by the registered ADoC STA for successive transmission of data and some management frames to the ADoC AP, and by the ADoC AP The tdfDownlinkTimeSlotNumber downlink time slot used to transmit data and some management frames to the STA. With this TDF protocol, the dual mode ADoC device 2902 in the STA mode will be active only during the synchronization slot, the contention time slot, the allocation uplink time slot (e.g., time slot k), and the downlink time slot. In the remaining time slots (ie, from time slot 2 to time slot k; and from time slot k to time slot m), the dual mode ADoC device in the STA mode will be inactive in the ADoC interface portion and thus Switching to the WLAN AP mode is present in the presence of a switch that can be controlled to change the operational RF from the ADoC band to the WLAN band. The detailed MAC layer procedure in a dual mode ADoC device is as follows: 1. Once an ADoC STA is enabled and successfully allocates an uplink time slot for uplink traffic transmission, such as time slot k, then the dual mode The device will calculate if k&gt;(m+2)/2. If k&gt;(m+2)/2, then 132611.doc •61 · 200926708 T[time slot 2, time slot k) means that the [time slot 2, time slot k) duration is tied to J. T (time slot k, time slot m) indicates the duration of (time slot k, time slot 1n). Therefore, the dual mode ADoC device will choose to operate in the WLAN mode during the [time slot 2, time slot k) period. On the other hand, 'if k&lt;(m+2)/2 ', it means that T[time s丨.t 2 time si〇tk) is shorter than T(time slot k, time slot m] 0, therefore, double The modulo AD〇c device will choose to operate in the WLAN mode during the [time slot k, time slot m) period. It should be noted that determining whether the period [slot 2, slot k) &gt; period (slot k, slot m) yields criterion (k-2) &gt; (mk) 'which in turn generates criterion k &gt; (m + 2)/2. Furthermore, in the illustrated embodiment, the WLAN mode is selected for longer periods. However, other embodiments operate in the WLAN mode during shorter periods or multiple times between modes in the hyperframe. 2. For other time slots in a TDF frame, in the case where the dual mode ADoC device decides to operate in the WLAN mode during the [Time slot 2, time slot k) period, the dual mode ADoC device will be in the ADoC mode. The operation is an ADOC STA and acts in a manner consistent with the standard ADoC TDF protocol. Therefore, when the dual mode ADoC device enters the time slot 2 in the ADoC mode, it will configure the RF switch 3102 to change the operating frequency to the WLAN spectrum&apos; and act as a WLAN AP. Therefore, the dual mode STA can communicate with the WLAN STA in the resident WLAN network in accordance with the standard WLAN procedure. Over time and closer to time slot k, and before time slot k begins to show no time for at least one WLAN frame, dual mode device 2902 will transmit a CTS (clear transmission) signal to the resident WLAN 132611 .doc • 62- 200926708 for all STAs. The duration field in the CTS frame will be equal to the duration from time slot k in the superframe to time slot 2 in the next frame. After receiving the CTS message, all STAs will update their NAV and stop accessing the WLAN. Media for the duration reported by the CTS message. In this way, the dual mode device will cause all STAs to move from the time slot k in the superframe to the time slot 2 in the next superframe by pretending another entity to save the WLAN media for the duration. Keep quiet during the cycle. Thereafter, the device will control the switch to change the 〇 operational spectrum back to the ADoC band and operate in accordance with the TDF procedure. When the dual mode device 2902 enters the time slot 2 of the next hyperframe, the device 2902 will repeat the same mode switch procedure and the STAs resident in the WLAN will also begin to use this available infrastructure WLAN to communicate again because The quiet duration indicated by the CTS expires at the same time. Conversely, for the dual mode ADoC device to determine operation in the WLAN mode during other time slots (time slot k, time slot m) periods for use in a TDF superframe, the dual mode ADoC device will be in the ADoC The operation in the modulo is a STA. When the dual mode ADoC device 2902 enters the time slot (k+1) in the ADoC mode, it will configure the switch 3102 to change the operating frequency to the WLAN spectrum and act as an AP. Once it is passed over time slot (m-1), the dual mode device will try to transmit the CST signal during time slot m, the duration field is equal to the downlink from this superframe The duration from the start of the time slot to the time slot (k+Ι) in the next superframe. Thereafter, the dual mode device 132611.doc-63-200926708 2902 will control the switch 2G02 to change the operational spectrum to ADq (and operate according to the ADoC TDF procedure. Thus, #the dual mode device enters the next superframe Time slot (k+(d), which will again perform the same mode switching procedure, as explained above. According to one embodiment, the dual mode device 2902 of one embodiment of the present principle is δ δ from a data from FIG. In the case of a machine (eg, ι〇ι〇, (7), etc.) Figure 33 shows an example of this embodiment. Similarly, when a dual mode device is operating or performing standard WLAN communication (i.e., during an appropriate time period) In this case, the device allows the user pc to connect to the Internet. In this embodiment, the PC user will pass a request to the Internet address on the wireless medium by transmitting a request to the data plane. An internet address (e.g., a web page) is requested, and 2) the data machine relays the request to the AD〇c Ap over the cable network via the AD〇c interface, then to the router, and then to the internet. In this embodiment, the dual mode The piece 2902 includes an ADoC interface or device 1018 instead of an Ethernet interface. When the dual mode device of the data machine operates in a WLAN (ie, wireless mode), the device acts as a 1 WLAN AP, and the personal computer acts as a wlan The dual-mode device receives the request from the personal computer via a wireless link between the modem and the personal computer. The dual-mode device relays a request to the bridge, and the bridge determines whether the dual-mode device requires The request is transmitted in the cable via the ADoC interface in the dual mode device, or the request is transmitted to other PCs in the resident network based on destination address information in the IP packet for the request. The request is then sent down 132611.doc • 64· 200926708 to the dual mode device. In order for the request to establish an external connection, the dual mode device maintains the request until the dual mode device enters the ADoC mode (ie, the wired mode). At this time, the dual mode device acts as an ADoC station and transmits the request to the ADoC AP over the wired network via the ADoC interface. In order to make the request establish with other PCs in the resident network. An internal connection, the dual mode device maintains the request until the dual mode device enters the WLAN mode (ie, the wireless mode), at which time it acts as a WLAN AP and transmits the request to the destination PC over the wireless medium via the WLAN. The dual-mode device will perform the reverse process when it receives any response from the associated ADoC AP in the cable network or other PCs in the regional network. It will be apparent from the above description that in at least some embodiments, the common circuit or The software, for example, can be used to perform most of the processing associated with the WLAN mode and the ADoC mode. For example, the reception and de-encapsulation of data from the two modes can be performed by a common circuit, and between the two modes. Conversion. Various applications that may require this conversion include (1) receiving a WLAN mode item from a computer (eg, a request for Internet access) and transmitting the data machine using the ADoC module, and (2) receiving the ADoC The modem requests the internet data and uses the WLAN module to transmit the data to a modem of a computer. These scenarios will typically involve conversions between different agreements. Various embodiments of a dual mode device use a communication unit to enable communication in one or more modes. A communication unit can include, for example, a dual mode ADoC device 2902, or portions thereof, such as MAC baseband 3100, WLAN RF 3 104, and ADoC RF 3106. 132611.doc -65- 200926708 It should be noted that the data machine may include not only a dual mode device as explained above, but also an interface for enabling communication across other networks (other than wlan &amp; ad〇c). Such other networks may include (eg, Ethernet). Thus, the &apos;data machine may include, for example, a dual mode device (4) that enables communication across the camera and the ADGC network as well as the Ethernet interface UH5. Various embodiments (for example) access data in the form of _ 斗 ' + σ V or another form. Technique: "Access" is used as a generalized term that includes, for example, obtaining, receiving, manipulating or processing in a manner. Therefore, the description of the access to the data (for example) is a broad description of the possible implementation. The features and aspects of the illustrated embodiments can be applied to a variety of applications. Applications include, for example, an individual using a host device in their home to communicate with the Internet using an electrical communication over Ethernet communication framework, as explained above, however, the features and states described herein can be adapted to other Application areas, and therefore other applications are feasible and envisioned. For example, the user can be located outside of his or her home, for example, in a public space or in its work. In addition, protocols and communication systems other than Ethernet and cable can be used, for example, in fiber optic = universal serial bus (USB), small computer system interface (scsi) cable, digital users Line/loop (DSL) junction. Line connection and honeycomb connection &amp;, star connection, view and receive data. (Using the agreement associated with it) The implementation of the implementation of the (4)m software program is implemented. Even if only stated in the single form of the implementation (for example, only as a prescription), the features of the description can be implemented in other forms (for example, a device or a program) 1326II.doc - 66 - 200926708 施. The method can be implemented, for example, in a suitable hardware, software, and firmware, for example, in a device, the processor of the device, including (for example, a computer, a microprocessor, a An integrated circuit, or a programmable logic device. The processing device also includes communication devices such as computers, mobile phones, portable/personal digital assistants ("like"), and other devices that facilitate communication of information between end users. Embodiments of the various programs and features described herein may be embodied in a variety of different devices or applications, particularly, for example, devices or applications associated with data transmission and reception. Examples of devices include video encoders, video, and video. Decoders, video codecs, web servers, transponders, laptops, personal computers, and other communication devices. It should be clear that the device can be mobile and even installed in a car. The instructions implemented by the processor implement the method and can store such instructions in a processor readable medium, such as an integrated battery a software carrier or other storage device, such as a hard disk drive, a compact disc, a random access memory ("ram") or a read only memory ("ROM"). The command can be made tactilely specific The processor can read an application in the medium. It should be clear that a processor can include a processor readable medium having, for example, one of the instructions for implementing a program. The various devices in the embodiments typically include one or more health devices. For example, although not explicitly indicated, 'data machines 1010 and 1020 and AP 1030 (and various other components) typically include one or Multiple storage units. Storage can be, for example, electronic, magnetic or optical. 132611.doc -67- 200926708

It should be understood from the above disclosure that embodiments can also be formatted to carry signals that can, for example, be stored or transmitted. The information may include, for example, instructions for implementing a method, or data generated by the illustrated embodiments. This signal can be formatted, for example, as an electromagnetic wave (e.g., using one of the radio frequency portions of the spectrum) or as a baseband signal. The formatting may include, for example, encoding a data stream, encapsulating the encoded stream according to any of the various frame structures, and employing a packetized stream to modulate a carrier. The information carried by the signal can be, for example, analog or digital information. This signal can be transmitted over a variety of different wired or wireless keyways, as is known. BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 illustrates a simplified exemplary TDF access network architecture. Figure 2 illustrates the 8〇2 u Mac sublayer in the OSI reference model. Figure 3 illustrates an implementation of the -TDF transport entity in the SI reference model. 4 illustrates an embodiment of a communication mode entry procedure. FIG. 5 illustrates an embodiment of a TDF hyperframe structure. Figure 6 illustrates one implementation of a registration procedure. Figure 7 illustrates one implementation of a non-registration procedure. Figure 8 illustrates an implementation of an active notification procedure. , &quot;~ Not machine round. Figure 10 includes a flow diagram of one embodiment of a block from one embodiment of a circle and a digital map data machine. One-to-one between WLAN packets Figure 11 includes an uplink transmission procedure. Figure 12 includes a diagram of an embodiment of an Ethernet packet and a 132611.doc-68-200926708 mapping. Figure 13 is a diagram of one embodiment of a transition between a plurality of Ethernet packets and a single WLAN packet. Figure 14 includes a diagram depicting the packet flow in the conversion of Figure 13. • Figure 15 includes a diagram of one embodiment of the EIW header from Figure 14. Figure 16 includes a flow diagram of one embodiment of an uplink receiving procedure. Figure 17 includes a diagram of an embodiment for decapsulating packets. Figure 18 includes a diagram depicting one embodiment of a padm from Figure 1A. ® Figure 19 includes a flow chart of one implementation of the next downlink transmission procedure. Figure 20 includes a flow diagram of one embodiment of a downlink receive procedure. Figure 21 illustrates one embodiment of a TDF hyperframe structure employing both polling and time-sharing media access. Figure 22 illustrates an embodiment of a TDF hyperframe structure with a hybrid media access mechanism. Figure 23 illustrates a block diagram and SP and stations in a TDF network. &amp; Figure 24 illustrates one implementation of the polling notification procedure. Figure 25 illustrates a flow chart of a polling procedure. Figure 26 illustrates an embodiment of a TDF hyperframe structure with a hybrid media access mechanism. Figure 27 illustrates a flow chart for a procedure for switching from a contention based mode to a time sharing mode. Figure 28 illustrates a flow diagram of a procedure for switching from a time-sharing mode to a contention-based mode. Figure 29 is a block diagram of a TDF (ADoC) STA. 132611.doc • 69- 200926708 Figure 30 is a block diagram of a TDF (ADoC) STA having a dual mode device in accordance with an embodiment. Figure 31 is a block diagram of one of the hardware implementations of a TDF (ADoC) STA dual mode device. Figure 32 is a block diagram of another hardware implementation of a TDF (ADoC) STA dual mode device. Figure 33 is a block diagram of an embodiment of a dual mode device of the present principles in the data engine of Figure 10. ® Figure 34 illustrates another solution for a TDF hyperframe structure. [Main component symbol description] 900 Network 910 User Home 912 Data Machine 914 Host 1 916 Host 2 918 Ethernet 920 User Home 922 Data Machine 924 Host 1 926 Host 2 928 Ethernet 930 Internet 940 AP 950 Electron Microscope System 132611.doc -70- 200926708

960 Router 970 Ethernet 1010 Data Machine #1 1011 Area Application Layer. 1012 TCP/IP^ 1014 Bridge 1015 Ethernet Interface 1016 PADM ® 1017 WLAN Interface 1018 Device 1020 Data Machine #N 1030 AP 1040 Cable Network 1052 Ethernet 1054 First Host 1056 ❿ Second Host 1062 Ethernet 1064 First Host 1066 Second Host 1071 Area Application Layer 1072 TCP/IP Layer 1074 Bridge 1075 WLAN Interface 1076 PADM 132611.doc • 71- 200926708

1077 Ethernet Interface 1082 Ethernet 1090 Router 1095 Internet 1210 Ethernet Packet 1220 Ethernet Pathhead 1230 Data Section 1240 WLAN Packet 1250 WLAN Header 1260 Frame Check Sequence (FCS) 1310 Ethernet Packet 1312 Ethernet Packet 1314 Ethernet Packet 1318 WLAN Packet 1320 Ethernet Network Header 1322 Ethernet Network Header 1324 Ethernet Network Headset 1326 Data Section 1328 Data Section 1329 Data Part 1330 Expanding the Ethernet Packet 1332 Expanding the Ethernet Packet 1334 Expanding the Ethernet Packet 1336 Data Section -72- 132611.doc 200926708

1338 Data Section 1340 Data Section 1342 Header 1343 Header 1344 Header 1346 End 1347 End 1348 End 1350 El W Packet 1352 Data Section 1353 Data Section 1354 Data Section 1356 Header 1358 End 1360 Data Section 1362 WLAN MAC Header, 1364 FCS 1410 enter queue 1420 string 1430 EIW header 1440 WLAN header 1530 packet descriptor 1540 packet descriptor 1550 packet flag -73- 132611.doc 200926708

1555 1560 1565 1710 1720 1730 1740 1750 1760 1770 2002 2100 2110 2120 2300 2302 2304 2600 2610 2620 2900 2902 2903 2904 132611.doc Packet packet packet length packet length packet packet waiting for incomplete packet PADM packet Transceiver switch

Frame structure polling time slot time slot TDF AP PC

TDF STA Frame Structure Competitive Time Slot Time Slot STA Dual Mode Device ADoC Device WLAN Device -74- 200926708 2906 Coaxial Interface 2908 Antenna 3100 MAC Fundamental Part 3102 Switch 3104 WLAN RF Circuit 3106 ADoC RF Circuit 3108 Converter

132611.doc 75-

Claims (1)

200926708 X. Patent Application Range: u A device comprising: a communication unit (3100, 3102, 3104, 31〇6) for communicating on multimedia including a wireless medium and a wired medium, the communication unit can be (1) operating in a wireless mode using a wireless protocol for communication over a wireless medium, operating in a wired mode using the wireless protocol - changing on the wired medium, and (3) operable to The wireless mode is switched between the wired mode and the wired mode. The device of claim 2 further includes a switch to switch the communication unit between the wireless mode and the wired mode. 3' The apparatus of claim 2, wherein the communication unit comprises: a communication H component (10) 0) coupled to the switch and configured to enable a user device to communicate with the communication unit; a wireless local area network ( a WLAN) device (3丨04) connected to the switch, the WLAN device being configured to be connected to a wireless network via an antenna; a wired network device connected to the switch, The wired network device is configured to connect to a wired network. A device of θ term 3 wherein the wired network device is configured to connect to a coaxial cable network. 5. The apparatus of &quot;monthly item 1, wherein the change in the wireless protocol in the wired mode comprises a time sharing mechanism. The device of claim 1 wherein the change in the wireless protocol in the cable mode comprises a WLAN packet structure. 132611.doc 200926708 The apparatus of claim 5, wherein the change in the wireless protocol in the wired mode is conveyed in at least one of the allocation slots in a time slot function (TDF) hyperframe. The device of claim 1 wherein the communication unit comprises a wireless local area network (WLAN) device connected to the switch; a WLAN antenna connected to the switch; 〇 9.10 a communication device, It is connected to the WLAN device; and a converter connected to the switch and configured to connect to a wired network' and convert a wireless frequency band into a wired frequency band. A device of claim 1, wherein the wireless mode is entered during one of two time periods in a TDF frame in one of the time slots. A device as claimed in claim 9, wherein the wireless mode is entered during the selection of a longer one of the two time periods. 11. The device of claim 10, wherein: the TDF hyperframe of the time slot further comprises a plurality of uplink time slots&apos; and the two time periods are within the plurality of uplink time slots. 12. A device as claimed, where the device is part of the tdf station. 13. The apparatus of claim 1, wherein the communication unit is configured to use a frame structure for communication, the frame structure supporting at least two communication modes, wherein the pass L mode includes the frame structure A slot is used to store a time-sharing mode for a device, and one of the competing slots in the frame structure is a competition-based mode by which multiple devices are used for data communication. 14. The apparatus of claim 3, wherein the apparatus is configured to transmit data from the tdf station in the contention slot during a modulo based on the competition of 132611.doc -2 - 200926708 To a TDF access point to use a portion of the TDF station of the frame structure. 15. 15. 16. Φ 18. The device of claim 1, wherein the communication unit is further configured to have a frame structure For communication, the frame structure supports at least two communication modes, wherein the communication modes include a slot system in the frame structure for storing a time division mode of a device, and one of the frame structures is polled The slot is used by one of the multi-device polling modules for data communication. The device of claim 15 wherein the frame structure supports a third communication mode based on a competition, wherein one of the content frames of the frame structure is used for data communication by a plurality of devices. Such as a requesting device, wherein the communication unit is further configured to: receive a packet from a first source, the packet from the first source has a particular format; 2 receive one from a second source The packet 'from the second source has the specific format; and the packet from the first source and the packet from the second source have a packet of different format . The device of claim 17, wherein: the feature format comprises an Ethernet format, the different format includes a adapted mode, and one of the wireless transmission WLAN cells is further included in a coaxial transmission cable. The packet packet is transmitted to the packet containing the following megabytes to transmit the packet: 132611.doc 200926708 (a) in one slot of a time division multiplexing scheme, and (b) based on one of the carried television materials One of the signals is a frequency division multiplexing scheme that assumes that the packet is transmitted within a frequency range of the packet data and that the television data is transmitted in a different frequency range. 19_ A method, comprising: communicating on a multimedia comprising a wireless medium and a wired medium, the communication using (1) using a wireless protocol to communicate with one of the wireless modes on a wireless medium, and (2) using the wired protocol One of the changes is one or more of one of the wired modes of communication over the wired medium; and switching between the wireless mode and the wired mode. 20. The method of claim 19, wherein: the communication comprises receiving a communication in the wireless mode or a particular one of the wired modes, Switching includes switching the particular one of the two modes of operation to the other of the two modes of operation, and the communication further comprises (1) associating the received communication from the particular one of the two modes of operation The agreement translates into the agreement associated with the other of the two modes of operation, and (7) transmits the received communication in the other of the two modes of operation. The method of claim 19, wherein the wired operating system is part of a time sharing functional communication system. 22. An apparatus comprising: a communication component (referred to as 3104, a pass) for communicating over a multimedia comprising a wireless medium 132611.doc 200926708 body and a wired medium, the communication being wirelessly agreed upon by a wireless medium The communication is - (1) enabling and operating in (2) using the wired association, the operation, the operation of the switch, and the switching of the switch module (3102), It is not replaced. The force deep mode is cut between 23. The device of claim 22, wherein: The communication component is configured to receive a communication in the wireless mode, the one of the wired modules being specifically configured to switch from the particular one of the two modes of operation to the other of the two modes of operation And, the communication component is further configured to (1) convert the receiving communication from the agreement associated with the particular one of the two modes of operation to associated with the other of the two modes of operation The agreement, and (2) transmitting the receiving communication in the other of the two modes of operation. 24. The device of claim 22, wherein the wired operation module is part of a time sharing functional communication system. 25. A device (3A) comprising a processor readable medium, the processor readable medium comprising instructions stored in the processor readable medium for performing at least the following actions: Multimedia communication over wireless media and a wired medium using (1) wireless communication over a wireless medium using a wireless protocol' and (2) communication over the wired medium using one of the wired protocols One or more of a wired mode; and 132611.doc 200926708 switches between the wireless mode and the wired mode. 26. The apparatus of claim 25, wherein the communicating comprises converting the communication received in a particular one of the two modes of operation from the agreement associated with the particular one of the two modes of operation to the second The other mode of operation is associated with the agreement. 132611.doc