Dynamic Quality Of Service (qos) Setup Over Wired And Wireless Networks

Abstract

A method to setup Quality of Service (QoS) parameters over a wireless network and over a wired network is described herein. A request to setup the QoS parameters may be initiated by a wireless device. The method includes the steps of receiving a first message from the wireless device that includes a first set of QoS parameters requested by the wireless device and determining a second set of QoS parameters for transmission over a wired network corresponding to the first set of QoS parameters. The method further includes the steps of transmitting a second message to a wired device including the second set of QoS parameters and receiving a response to the second message from the wired device that indicates whether the second set of QoS parameters was accepted by the wired device. The method also includes transmitting a response to the first message, based on the response to the second message, to the wireless device indicating whether the first set of QoS parameters are acceptable. A similar method is provided to setup QoS parameters over the wireless network when the initial request is received over the wired network.

Description

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 61/259,911 filed Nov. 10, 2009, which is incorporated herein by reference in its entirety.

BACKGROUND OF THE INVENTION

[0002] 1. Field of the Invention

[0003] This application generally relates to Quality of Service (QoS) setup and more specifically to dynamic QoS setup over wired and wireless networks.

[0004] 2. Background Art

[0005] Applications running on wireless devices such as cellular phones, wireless enabled laptops, personal digital assistants (PDAs) or any device that communicates over a wireless network have differing Quality of Service (QoS) requirements depending upon the nature of the application. For example, Voice over Internet Protocol (VoIP) applications such as Skype.TM. require specific parameters such as a controlled latency and jitter for desired operation. Typically, QoS parameters for an application's traffic flows over wireless and wired networks are statically setup by a network administrator. If an application such as a VoIP application is initiated in real time and the corresponding traffic flows do not have QoS parameters to support the VoIP call over a wired and/or wireless network, then the call will not function properly. Current communications systems are not able to dynamically (i.e. in real-time or on-the-fly) create required traffic flows with desired QoS parameters.

[0006] Methods and systems are needed to overcome the above mentioned deficiency.

BRIEF DESCRIPTION OF THE DRAWINGS/FIGURES

[0007] The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention. In the drawings:

[0008] FIG. 1A illustrates an example communication system according to an embodiment of the invention.

[0009] FIG. 1B illustrates wireless gateway and cable modem according to a further embodiment of the invention.

[0010] FIG. 1C illustrates a protocol stack on wireless gateway and cable modem according to an embodiment of the invention.

[0011] FIG. 2 illustrates dynamic quality of service setup for a wireless gateway and cable modem to setup and map Traffic Specification (TSpec) parameters over a wireless network to Data Over Cable Service Interface Specification (DOCSIS) service flow parameters over a wired network according to an embodiment of the present invention.

[0012] FIG. 3 illustrates an example system to dynamically setup and map quality of service over a wired network and over a wireless network according to an embodiment of the invention.

[0013] FIG. 4A illustrates an example communication system according to an embodiment of the invention.

[0014] FIG. 4B further illustrates a wireless gateway according to an embodiment of the invention.

[0015] FIG. 5 illustrates an example system to setup and map QoS parameters over a wireless network and a wired network according to an embodiment of the invention.

[0016] FIG. 6 illustrates an example system to setup and map quality of service over a wired network and over a wireless network according to an embodiment of the invention.

[0017] FIG. 7 illustrates an example of flowchart illustrating steps performed to set up quality of service parameters over a wireless network and over a wired network according to an embodiment of the invention.

[0018] FIG. 8 illustrates an example flowchart illustrating steps performed to set up quality of service parameters over a wired network and a wireless network according to an embodiment of the invention.

[0019] The present invention will now be described with reference to the accompanying drawings. In the drawings, like reference numbers may indicate identical or functionally similar elements. Additionally, the left-most digit(s) of a reference number may identify the drawing in which the reference number first appears.

DETAILED DESCRIPTION OF THE INVENTION

[0020] FIG. 1A illustrates an example communication system 100 according to an embodiment of the invention. System 100 includes wireless device 102, wireless gateway and cable modem 110, cable modem termination system (CMTS) 108 and application server 119. In the embodiment in FIG. 1A, wireless gateway 104 and cable modem 106 from FIG. 4A are combined into a single physical unit which is wireless gateway and cable modem 110. In an example, wireless gateway and cable mode 110 may operate using a single processor that is configured to perform the functions of both wireless gateway 104 and cable modem 106. Alternatively, wireless gateway and cable modem 110 may be a single physical device that includes multiple processors with a first processor implementing a functionality of wireless gateway 104 and a second processor implementing functionality of cable modem 106.

[0021] In the embodiment shown in FIG. 1A, wireless device 102 communicates with wireless gateway and cable modem 110 using IEEE 802.11(e) frames. Wireless gateway and cable modem 110 encapsulates data in the IEEE 802.11(e) frame received from wireless device 102 into DOCSIS packets that are transmitted over a wired network 107, for example a DOCSIS network, to CMTS 108. CMTS 108 may encapsulate or translate data from DOCSIS frames or packets into Internet Protocol (IP) frames and transmit the IP frames over an Internet network 109 to application server 119. Application server 119 may include a processor (not shown) that executes instructions in a memory (not shown) to perform the functions of application server 119 described herein.

[0022] A "wireless device" as described herein refers to a device that can communicate wirelessly with other devices i.e. without using tangible physical media such as coaxial cables, twisted pair Ethernet cables, optical fibers etc. For example, wireless device 102 is any device that can communicate wirelessly over wireless network 101. In an example, wireless device 102 may be referred to as a WiFi station (WiFi STA or simply STA). Wireless device 102 may be, for example, any wireless device including but not limited to a cellular phone (including a smart phone, for example, an iPhone.TM.), a wireless laptop or any device enabled to communicate over wireless network 101.

[0023] A "wireless network" as referred to herein may refer to any network that transmits and receives data between two or more devices without using physical media such as wires or cables. In an example, wireless network 101 is based on Institute of Electrical and Electronics Engineers (IEEE) 802.11 protocol for wireless communication networks. In another example, wireless network 101 may be referred to as a Wireless Local Area Network (WLAN) or a WiFi network.

[0024] Cable modem 106 (see FIG. 4A) communicates with CMTS 108 using a Data Over Cable Service Interface Specification (DOCSIS) protocol. Cable modem 106 and CMTS 108 are both referred to as "wired devices" herein. A "wired device" as described herein refers to a device that communicates using tangible physical media including but not limited to coaxial cables, twisted pair Ethernet cables, optical fibers etc. Cable modem 106 may communicate with wireless gateway 104 using Ethernet packets over an Ethernet network.

[0025] Wireless gateway and cable modem 110 and wireless gateway 104 (see FIG. 4A) can both be considered as wired and wireless devices. For example, wireless gateway and cable modem 110 can transmit and receive data both wirelessly and through wires. Wireless gateway and cable modem 110 can communicate with wireless device 102 and can also communicate with cable modem 106. Wireless gateway and cable modem 110 can communicate with wireless device 102 using 802.11 frames over wireless network 101. Wireless gateway and cable modem 110 can also communicate with CMTS 108 over wired network 107. Thus wireless gateway and cable modem 110 serves as a conduit that bridges wireless network 101 and wired network 107. Wireless gateway and cable modem 110 or wireless gateway 104, may also be referred to as a wireless access point (AP), a radio or a "wireless hotspot." In the example in FIG. 4A, wireless gateway 104 and cable modem 106 are physically separate devices with wireless gateway 104 being coupled to cable modem 106 via an Ethernet cable. Wireless gateway 104 sends data encapsulated in the 802.11 frames in an Ethernet format to cable modem 106. Cable modem 106 may encapsulate or convert the Ethernet packets into a DOCSIS format and transmit them to CMTS 108 for further transmission over another network such as the Internet. Thus, data is transmitted from a wireless device 102 over wireless network 101 to wireless gateway 104 and from wireless gateway 104 and cable modem 106 over wired network 107 to CMTS 108. Network 109 may be a wired network such as the Internet. CMTS 108 transmits data over network 109 to application server 119.

[0026] It is to be appreciated that wireless gateway and cable modem 110 may be used interchangeably with one or both of wireless gateway 104 and cable modem 106 because wireless gateway and cable modem 110 implements the functionality of both wireless gateway 104 and cable modem 106.

[0027] Applications running on wireless device 102 may require a certain Quality of Service (QoS) over wireless network 101 and wired network 107 for desired operation of the application. Quality-of-service (QoS) in communication protocols such as, including but not limited to, Data Over Cable Service Interface Specification (DOCSIS), PacketCable.TM., IEEE 802.11 etc., is the ability to guarantee a certain level of performance to a traffic flow or to provide different levels of priority to different traffic flows. For example, parameters such as a required bit rate, delay, jitter, packet loss probability and/or bit error rate may be guaranteed for different traffic flows. Quality of service guarantees are important if the network capacity is insufficient, especially for real-time multimedia applications such as Voice over Internet Protocol (VoIP), online games and Internet Protocol Television (IPTV), since these often require guaranteed bit rate and are delay sensitive. Quality of service guarantees are also important in networks where the network capacity is a limited resource, for example, in cellular data communication. QoS may be guaranteed, for example, for traffic flows generated by a particular user who subscribes to a high date rate service from his cable company. A particular QoS may also be guaranteed for traffic flows generated by certain applications. For example, traffic flows generated by streaming video and VoIP applications may be guaranteed a certain bit rate. In another example, all voice traffic flows may be allocated a certain QoS and all video traffic may be guaranteed another QoS. Users, applications and traffic flows may be used interchangeably herein.

[0028] The basic DOCSIS QoS element is a "service flow" (SF), which is a unidirectional flow of packets with guaranteed QoS parameters such as bit rate, delay, jitter, etc. For example, negotiation between cable modem 106 and CMTS 108 may be used to assign a service flow with QoS parameters guaranteed for certain traffic flows. For example, Voice Over IP (VoIP) applications may be assigned a first service flow with a first set of guaranteed QoS parameters, file transfer applications may be assigned a second service flow with a second set of guaranteed QoS parameters and streaming multimedia may be assigned a third service flow with a third set of guaranteed QoS parameters. Examples of DOCSIS service flow parameters that indicate a QoS over wired network 107 are shown below in table 1.

TABLE-US-00001 TABLE 1 DOCSIS SF Parameters Traffic Priority Maximum Traffic Burst Minimum Reserved Traffic Rate Maximum Sustained Traffic Rate Tolerated Poll Jitter for Unsolicited Grant Service (UGS) Nominal Grant Interval for UGS

[0029] In wireless networks operating under an IEEE 802.11(e) protocol, Traffic

[0030] Specification (TSpec) parameters are used to determine a Quality of Service for a traffic flow. Examples of TSpec parameters that indicate QoS over wireless network 101 are shown below in table 2.

TABLE-US-00002 TABLE 2 TSpec Parameters User Priority Max Media Access Control Service Data Unit (MSDU) Size Maximum Burst Size Min Physical Layer (PHY) Rate Peak Data Rate Mean Data Rate Delay Bound Nominal MSDU Size Max Service Interval

[0031] In conventional communication systems, DOCSIS service flows are "statically" created across network 107 corresponding to TSpec quality of service parameters over a wireless network 101. "Static" service flow setup or creation as referred to herein describe service flows that are created before start up by a cable network operator. These service flows support certain QoS parameters as determined by the cable network operator. However, applications running on wireless device 102, have no control over their quality of service requirements. For example, an application running on a wireless device 102 may require specific quality of service parameters over wired network 107. If traffic flows over wireless network 101 and the corresponding service flows over wired network 107 were not statically created to support the desired QoS, then the application will not function properly. Thus, in current systems, if an application is started on wireless device 102, then it has to utilize the available service flows over wired network 107. Similarly applications that originate on application server 119 may have to utilize available statically created QoS over a wireless network 101.

[0032] While many applications running on wireless device 102 can utilize available DOCSIS service flows over network 107, certain applications require a particular quality of service and may not function properly if the required quality of service is not available in a corresponding DOCSIS service flow over a wired network 107. For example, a VoIP application running on wireless device 102 may require a controlled latency and jitter over wired network 107. If a DOCSIS service flow with QoS parameters to support the required controlled latency and jitter was not statically created prior to startup, then the VoIP IP application on wireless device 102 cannot function as desired and in a worst case cannot function at all. Similarly, applications originating over a wired network that needs to communicate with wireless device 102 may require a certain quality of service over wireless network 101. If that quality of service is not available over wireless network 101, then the functioning of the application will not be as desired or in a worst case it may not function at all. For example, a VoIP application originating across wired network 107 on application server 119 may require a certain quality of service (specified by TSpec parameters) over wireless network 101. If a quality of service with TSpec parameters corresponding to the VoIP application was not statistically created prior to startup, then the functioning of the VoIP application is not as desired. Thus, according to an embodiment of the present invention, the inventors have provided a solution that allows for dynamic setup or creation of service flows with desired quality of service parameters over a wireless network 101 and a wired network 107. According to an embodiment of the invention, applications running on wireless device 102 can request certain Quality of Service parameters over wireless network 101 and wired network 107. Similarly applications originating across wired network 107 via application server 119 can also request a quality of service over wired network 107 and wireless network 101 as will be described further below.

[0033] FIG. 1B illustrates wireless gateway and cable modem 110 according to a further embodiment of the invention. In this example, wireless gateway and cable modem 110 includes a processor 103 that runs applications 111, memory 105 and a quality of service mapper 112. Processor 103 is coupled to memory 105 and QoS mapper 112. QoS mapper 112 dynamically (i.e. on-the-fly or in real time) sets up a QoS with requested TSpec parameters across wireless network 101 and a QoS with DOCSIS service flow parameters across a wired network 107 based on a mapping between TSpec parameters and corresponding DOCSIS service flow parameters as provided, for example, in mapping table 3. Similarly, QoS mapper 112 dynamically sets up a QoS with requested DOCSIS service flow parameters across wired network 107 and a corresponding QoS with TSpec across wireless network 101 based on a mapping between DOCSIS SF parameters and TSpec parameters as shown, for example, in table 3 below.

TABLE-US-00003 TABLE 3 TSpec Parameters DOCSIS SF Parameters User Priority Traffic Priority Max MSDU Size No corresponding DOCSIS parameter. By default, it is proposed to set this according to Max Burst Size. Max Burst Size Maximum Traffic Burst Min PHY Rate Minimum Reserved Traffic Rate Peak Data Rate Maximum Sustained Traffic Rate Mean Data Rate No corresponding DOCSIS parameter. By default, it is proposed to set this according to Peak Data Rate. Delay Bound Tolerated Poll Jitter for UGS Nominal MSDU Size No corresponding DOCSIS parameter. By default, it is proposed to set this according to Assumed Minimum Reserved Rate Packet Size. Max Service Interval Nominal Grant Interval for UGS

[0034] The mapping rules for Table 3 may be stored, for example, in memory 105. In an example, processor 103 based on instructions stored in memory 105 performs the mapping and setup of requested quality of service across wireless network 101 and wired network 107. In an embodiment, QoS mapper 112 is an application, such as application 111, that runs on processor 103 based on instructions stored in memory 105. In another example, QoS mapper 112 is solely hardware based and includes hard wired circuitry such as logic gates.

[0035] FIG. 1C illustrates a protocol stack 150 operating on wireless gateway and cable modem 110 according to an embodiment of the invention. Wireless gateway and cable modem 110 includes functionality of a wireless gateway 104 and cable modem 106. Wireless gateway and cable modem 110 includes a wireless protocol stack 114 that has wireless application layer 116, wireless Media Access Control (MAC) layer 118 and wireless physical (PHY) layer 120. Wireless gateway and cable modem 110 also includes a DOCSIS stack 122 that has a DOCSIS application layer 123, a DOCSIS MAC layer 126 and a DOCSIS PHY layer 128. Wireless stack 114 and DOCSIS stack 122 may run on a single processor or on separate processors. QoS mapper 112 communicates with wireless MAC 118 using wireless MAC interface 130. QoS mapper 112 communicates with DOCSIS MAC 126 using DOCSIS MAC interface 132. QoS mapper 112 may include an EDCA (Enhanced Distributed Coordination Function)-Service Flow (SF) quality of service mapper and/or an HCCA (Hybrid coordination function Controlled Channel Access)-Service Flow (SF) quality of service mapper based on the protocol used by DOCSIS MAC 126. In an example, QoS mapper 112 is hardware based and includes a memory (not shown) that stores the mapping rules for table 3 that includes a mapping between wireless TSpec parameters and DOCSIS service flow parameters.

[0036] FIG. 2 illustrates dynamic quality of service setup for a wireless gateway and cable modem 110 to map TSpec parameters over wireless network 101 to DOCSIS service flow parameters over wired network 107 according to an embodiment of the present invention.

[0037] If an application is initiated on wireless device 102 that requires a quality of service over wireless network 101 and wired network 107 that is not currently setup, then the application generates an ADDTS message 202 that includes TSpec parameters corresponding to the desired quality of service. The ADDTS message 202 is transmitted to wireless gateway and cable modem 110.

[0038] In response to receiving ADDTS message 202, QoS mapper 112 in wireless gateway and cable modem 110 maps the QoS parameters (i.e. the TSpec parameters) requested by wireless device 102 in ADDTS message 202 to corresponding DOCSIS service flow parameters over wired network 107 using, for example, the mapping rules for table 3. Wireless gateway and cable modem 110 generates a DSA message 204 that includes the mapped DOCSIS service flow parameters. DSA message 204 is transmitted to cable modem termination system 108.

[0039] Wireless gateway and cable modem 110 receives a DSA response 206 from cable modem termination system 108. The DSA response 206 indicates whether the DOCSIS service flow parameter in DSA message 204 were accepted by cable modem termination system 108.

[0040] If the DSA response 206 indicates that the DOCSIS service flow parameters in DSA message 204 were accepted by CMTS 108, then wireless gateway and cable modem 110 sends an ADDTS response 208 to wireless device 102 indicating that a requested quality of service has been setup over wireless network 101 and wired network 107 corresponding to the TSpec parameters requested by wireless device 102 in ADDTS message 202.

[0041] If DSA response 206 from CMTS 108 indicates that the QoS parameters in DSA 204 are rejected, then wireless gateway and cable modem 110 transmits the ADDTS response 208 to wireless device 102 indicating the rejection of the TSpec parameters in ADDTS 202. Steps 202, 204, 206 and 208 can be repeated to renegotiate a new set of QoS parameters between wireless device 102 and cable modem termination system 108 according to an embodiment of the invention. The negotiation may continue till QoS parameters are agreed upon.

[0042] FIG. 3 illustrates an example system to dynamically setup and map quality of service over a wired network 107 and over a wireless network 101 according to an embodiment of the invention.

[0043] In this embodiment, a request for certain quality of service parameters may be generated on a network side, e.g., by application server 119. For example, such a request for a VoIP application or a streaming video game application generated on application server 119 may be transmitted to CMTS 108. In response to the quality of service requested by application server 119, CMTS 108 generates a DSA message 302 that includes DOCSIS service flow parameters corresponding to the requested QoS.

[0044] In response to receiving a DSA message 302, wireless gateway and cable modem 110, using quality of service mapper 112, maps the DOCSIS service flow parameters to corresponding TSpec parameters using, for example, the mapping rules for table 3. Wireless gateway and cable modem 110 generates an ADDTS trigger 304 that includes the mapped TSpec parameters and transmits the ADDTS trigger 304 to wireless device 102.

[0045] ADDTS trigger 304 triggers wireless device 102 to generate an ADDTS message 306 that includes the TSpec parameters in ADDTS trigger 304. Wireless gateway and cable modem 110 may either accept or reject the TSpec parameters, by sending a corresponding ADDTS response message 308 to wireless device 102.

[0046] Wireless gateway and cable modem 110 sends a DSA response message 310 to CMTS 108 in response to DSA message 302. If, wireless gateway and cable modem 110 accepted the TSpec parameters, then DSA response message 310 indicates that the process is complete and the required quality of service is setup over wireless network 101 and wired network 107.

[0047] If, wireless gateway and cable modem 110 rejected the TSpec parameters then wireless gateway and cable modem 110 sends DSA response 310 to CMTS 108, indicating the rejection of the DOCSIS QoS parameters in DSA 302. Messages 302 through 310 may be repeated in a negotiation process until quality of service parameters over wired network 107 and wireless network 101 are agreed upon.

[0048] FIG. 4A illustrates an example system 400 according to an embodiment of the invention. In system 400, wireless gateway 104 is physically separate and distinct from cable modem 106 and communicates with cable modem 106 using an Ethernet protocol over an Ethernet network.

[0049] FIG. 4B further illustrates wireless gateway 104 according to an embodiment of the invention. Wireless gateway 104 includes processor 103, application 111 that runs on processor 103, memory 105, QoS mapper 112 and a PacketCable.TM. MultiMedia (PCMM) client 124, according to an embodiment of the invention. In the embodiments described in FIGS. 5 and 6 below, wireless gateway 104 is separate and distinct from cable modem 106 and hence wireless gateway 104 does not have direct control over QoS setup and negotiation over wired network 107. Therefore, wireless gateway 104 implements PCMM client 124, which interacts with application server 119 for QoS setup and negotiation over wired network 107. In these embodiments, QoS mapper 112 is again used to map TSpec parameters to DOCSIS service flow parameters and vice versa as described below with respect to FIGS. 5 and 6. In an embodiment, QoS mapper 112 and PCMM client 124 may be combined into a single unit that is implemented solely in hardware, software, firmware or in any combination thereof.

[0050] FIG. 5 illustrates an example system to setup and map QoS parameters over a wireless network 101 and a wired network 107 according to an embodiment of the invention. For example, an application originating on wireless device 102 may require a particular quality of service across wireless network 101 and wireless network 107 for proper functioning. The application generated on wireless device 102 may interact with application server 119 across network 109.

[0051] If an application is initiated on wireless device 102 that requires a quality of service over wireless network 101 and wired network 107 that is not currently setup, then the application generates an ADDTS message 502 that includes TSpec parameters corresponding to the desired quality of service. The ADDTS message 502 is transmitted to wireless gateway 104.

[0052] Quality of service mapper 112 maps the TSpec parameters in ADDTS message 502 to corresponding DOCSIS service flow parameters that operate over wired network 107. Quality of service mapper 112 generates a PCMM trigger 504 that is sent to PCMM client 124. PCMM trigger 504 includes the mapped DOCSIS service flow parameters. Communications between QoS mapper 112 and PCMM client 124 may be software function calls between software modules. In alternate embodiments, the communications between QoS mapper 112 and PCMM client 124 may be signals between hardware based modules.

[0053] PCMM client 124 generates a PCMM quality of service creation trigger 506 that includes the mapped DOCSIS service flow parameters. The PCMM quality of service creation trigger 506 is transmitted to application server 119.

[0054] In response to PCMM quality of service creation trigger 506, application server 119 transmits a DSA trigger 508 to CMTS 108. DSA trigger message 508 includes the mapped DOCSIS service flow parameters from PCMM quality of service creation trigger 506.

[0055] DSA trigger 508 triggers a DSA message 510 from CMTS 108. DSA message 510 requests whether cable modem 106 can support a service flow corresponding to the DOCSIS service flow parameters in PCMM QoS trigger 506.

[0056] In response to DSA message 510, cable modem 106 sends a DSA response message 512 indicating whether cable modem 106 can add a service flow that can support the DOCSIS service flow parameters in DSA message 510.

[0057] CMTS 108 sends a DSA trigger response message 514 that is transmitted to application server 119 indicating whether a service flow over wired network 107 corresponding to the DOCSIS service flow parameters specified in DSA trigger 508 was created or not.

[0058] Application server 119, based on DSA trigger response 514, generates a PCMM QoS creation response 516 in response to PCMM QoS creation trigger 506. Message 516 acknowledges whether the DOCSIS service flow parameters suggested in message 506 were accepted by cable modem termination system 108. The parameters in message 506 may be rejected if CMTS 108 cannot create the desired service flow or if cable modem 106 cannot add the desired service flow.

[0059] In response to message 516, PCMM client 124 sends a PCMM trigger response 518 in response to PCMM trigger 504 to quality of service mapper 112 indicating whether the DOCSIS service flow parameters mapped by quality of service mapper 112 were accepted or rejected by cable modem termination system 108.

[0060] If the DOCSIS service flow parameters were accepted by application server 119 and CMTS 108 then the process is complete and the required quality of service is available across wireless network 101 and wired network 107. PCMM client 518 generates a PCMM trigger response 518 that indicates creation of the desired QoS. QoS mapper 112 generates an ADDTS response 520 that indicates creation of the desired QoS to wireless device 102.

[0061] If the DOCSIS service flow parameters were rejected according to the PCMM QoS creation response 516, then PCMM client 124 sends PCMM trigger response 518 to QoS mapper 112, indicating the rejection. QoS mapper 112 transmits an ADDTS response message 520 to wireless device 102 to indicate that the TSpec parameters in ADDTS 502 are rejected. Negotiation occurs by repeating messages 502-520 as described above until agreement is reached upon QoS parameters.

[0062] FIG. 6 illustrates an example system to create and map quality of service over a wired network 107 and over a wireless network 101 based on a request generated by an application on application server 119, according to an embodiment of the invention.

[0063] In this embodiment, a request for quality of service creation is generated by an application running on application server 119. For example, a VoIP application running on application server 119 or received via, e.g., a wireless device such as a laptop through application server 119, requests quality of service creation across wired network 107 and wireless network 101.

[0064] In response to the application, a DSA trigger 602 requesting quality of service creation across wired network 107 is transmitted from application server 119 to CMTS 108. DSA trigger 602 includes DOCSIS service flow parameters requested across wired network 107.

[0065] CMTS 108 in response to message 602, generates a DSA message 604 that requests cable modem 106 to add a service flow that supports the DOCSIS service flow parameters requested by application server 119 in DSA trigger 602.

[0066] Cable modem 106, in response to DSA message 604, transmits a DSA response message 606 that indicates whether cable modem 106 can add a DOCSIS service flow that can support the requested DOCSIS service flow parameters in DSA message 604.

[0067] CMTS 108 transmits a DSA trigger response message 607 that indicates whether the DOCSIS service flow including requested DOCSIS service flow parameters from message 602 was created across wired network 107. In an example, if CMTS 108 or cable modem 106 rejects the proposed DOCSIS service flow parameters in DSA trigger 602, then step 602-607 are repeated until DOCSIS service flow parameters across wired network 107 are agreed upon.

[0068] When a desired DOCSIS service flow is created across wired network 107, then application server 119 generates a PCMM quality of service creation trigger 608 that includes the DOCSIS service flow parameters agreed upon over wired network 107.

[0069] Trigger 608 causes PCMM client 124 to transmit a PCMM trigger 610 to quality of service mapper 112 that includes the DOCSIS service flow parameters from trigger 608.

[0070] QoS mapper 112 in response to trigger 610, maps the DOCSIS service flow parameters to corresponding TSpec parameters using, for example, the mapping rules for table 3. QoS mapper 112 generates an ADDTS trigger 612 that includes the mapped TSpec parameters and transmits the ADDTS trigger 612 to wireless device 102.

[0071] Wireless device 102, upon receiving ADDTS trigger 612, generates an ADDTS message 614 with the same set of TSpec parameters as in message 612

[0072] Wireless gateway 104 sends an ADDTS response message 616 indicating the acceptance or rejection of the TSpec parameters in ADDTS message 614. If, the TSpec parameters in message 614 were accepted by wireless gateway 104, then PCMM trigger response 618 is generated by QoS mapper 112 and PCMM QoS creation response 620 is generated by PCMM client 124 to indicate that the requested QoS across wired network 107 and wireless network 101 has been created.

[0073] If the TSpec parameters in ADDTS message 614 were not accepted by wireless gateway 104, then QoS mapper 112 generates a PCMM trigger response 618 that indicates the rejection of DOCSIS service flow parameters that were in PCMM trigger 610. PCMM client 124, based on response 618, transmits a PCMM QoS creation response 620, that indicates the rejection, to application server 119. A negotiation process including step 602-620 is repeated until service flows with acceptable QoS parameters across wired network 107 and wireless network 101 are created.

[0074] FIG. 7 illustrates an example of flowchart 700 illustrating steps performed to set up quality of service parameters over a wireless network and over a wired network according to an embodiment of the invention. Flowchart 700 will be described with continued reference to the example operating environment depicted in FIGS. 2 and 5. However, the flowchart is not limited to these embodiments. Note that some steps shown in flowchart 700 do not necessarily have to occur in the order shown. The steps in flow chart 700 may be performed by, for example, one or more of QoS mapper 112, PCMM client 124 and processor 103. The quality of service setup may be initiated by, for example, wireless device 102.

[0075] In step 702, a request is received over a wireless network to setup quality of service over the wireless network based on a first set of parameters. For example, a message is received from wireless device 102. The message may include quality of service parameters. For example, an ADDTS message 202 or 502 including TSpec parameters is received from wireless device 102.

[0076] In step 704, a second set of parameters corresponding to quality of service over a wired network based on the first set of parameters is determined. For example, DOCSIS service flow parameters corresponding to the TSpec parameters in the ADDTS message in step 702 are determined by QoS mapper 112 using the mapping rules for table 3.

[0077] In step 706, a message is transmitted to a wired device requesting quality of service setup over the wired network based on the second set of parameters determined in step 704. For example, a DSA message 204 is transmitted to a CMTS 108 requesting setup of a DOCSIS service flow over wired network 107 based on DOCSIS service flow parameters included in the DSA message. In another example, the message is a PCMM quality of service creation message sent to an application server 119. For example, a PCMM quality of service creation message 506 that includes DOCSIS service flow parameters desired over wired network 107 is sent to application server 119.

[0078] In step 708, a response is received from the wired device indicating whether the second set of parameters were accepted or rejected. For example, a DSA response 206 is received from cable modem termination system 108 indicating whether cable modem termination system 108 accepted or rejected the DOCSIS service flow parameters. In another example, a PCMM quality of service creation response message is received indicating whether the DOCSIS service flow parameters in the PCMM quality of service creation message 506 were accepted or rejected by cable modem termination system 108.

[0079] If the parameters in the message in step 706 were accepted by the wired device then the process is complete and quality of service over the wireless network and the wired network is setup. If, however, the quality of service parameters are rejected by the wired device, then steps 702-708 are repeated for negotiations between wireless device and wired device until QoS parameters are agreed upon.

[0080] FIG. 8 illustrates an example flowchart 800 illustrating steps performed to set up quality of service parameters over a wired network and a wireless network according to an embodiment of the invention. Flowchart 800 will be described with continued reference to the example operating environment depicted in FIGS. 3 and 6. However, the flowchart is not limited to these embodiments. Note that some steps shown in flowchart 800 do not necessarily have to occur in the order shown. The steps in flow chart 800 may be performed by, for example, one or more of QoS mapper 112, PCMM client 124 and processor 103. The quality of service setup may be initiated by, for example, CMTS 108 or application server 119.

[0081] In step 802, a request to a setup a QoS over a wired network based on a first set of parameters is received. For example, a DSA message 302 or 604 including DOCSIS service flow parameters is received from CMTS 108.

[0082] In step 804, a second set of parameter corresponding to quality of service over a wireless network is determined based on the first set of parameters. For example, TSpec parameters corresponding to the DOCSIS service flow parameters are determined based on table 3 using QoS mapper 112.

[0083] In step 806, a message is transmitted to the wireless device to trigger quality of service set up over the wireless network based on the second set of parameters. For example, an ADDTS trigger 304 or 612 is transmitted to wireless device 102 to trigger quality of service setup over wireless network 101 based on TSpec parameters mapped by QoS mapper 112.

[0084] In step 808, a request is received from the wireless device to setup QoS over the wireless network based on the set second set of parameters. For example, an ADDTS message 306 or 614 is received from wireless device 102 requesting QoS setup over wireless network 101 based on the second set of parameters.

[0085] If the second set of parameters in step 808 are accepted, then the process is complete and quality of service as requested is set up over wireless network 101 and wireless network 107 using respective TSpec parameters and DOCSIS service flow parameters. If, however, the second set of parameters are rejected, then steps 802-808 may be repeated until parameters are agreed upon for QoS setup over wireless network 101 and wired network 107.

[0086] Embodiments presented herein, or portions thereof, can be implemented in hardware, firmware, software, and/or combinations thereof. The embodiments presented herein apply to any communication system that utilizes packets for data transmission.

[0087] The representative packet processing functions described herein (e.g. functions performed by processor 103, QoS mapper 112 or PCMM client 124 can be implemented in hardware, software, or some combination thereof. For instance, the method of flowcharts 700 and 800 can be implemented using computer processors, such as processor 103, computer logic, application specific circuits (ASIC), digital signal processors, etc., or any combination thereof, as will be understood by those skilled in the arts based on the discussion given herein. Accordingly, any processor that performs the functions described herein is within the scope and spirit of the embodiments presented herein.

[0088] Further, the packet processing functions described herein could be embodied by computer program instructions that are executed by a computer processor, for example processor 103, or any one of the hardware devices listed above. The computer program instructions cause the processor to perform the instructions described herein. The computer program instructions (e.g. software) can be stored in a computer usable medium, computer program medium, or any storage medium that can be accessed by a computer or processor. Such media include a memory device, such as instruction memory 204, a RAM or ROM, or other type of computer storage medium such as a computer disk or CD ROM, or the equivalent. Accordingly, any computer storage medium having computer program code that cause a processor to perform the functions described herein are within the scope and spirit of the embodiments presented herein.

CONCLUSION

[0089] While various embodiments have been described above, it should be understood that they have been presented by way of example, and not limitation. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the spirit and scope of the embodiments presented herein.

[0090] The embodiments presented herein have been described above with the aid of functional building blocks and method steps illustrating the performance of specified functions and relationships thereof. The boundaries of these functional building blocks and method steps have been arbitrarily defined herein for the convenience of the description. Alternate boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Any such alternate boundaries are thus within the scope and spirit of the claimed embodiments. One skilled in the art will recognize that these functional building blocks can be implemented by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof. Thus, the breadth and scope of the present embodiments should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

Claims

1. A method to setup Quality of Service (QoS) parameters over a wireless network and over a wired network, wherein a request to setup the QoS parameters is initiated by a wireless device, comprising: (a) receiving a first message from the wireless device, wherein the first message includes a first set of QoS parameters requested by the wireless device; (b) determining a second set of QoS parameters for transmission over a wired network corresponding to the first set of QoS parameters; (c) transmitting a second message to a wired device including the second set of QoS parameters; (d) receiving a response to the second message from the wired device that indicates whether the second set of QoS parameters was accepted by the wired device; and (e) transmitting a response to the first message, based on the response to the second message, to the wireless device indicating whether the first set of QoS parameters are acceptable.

2. The method of claim 1, wherein the first message is an Add Traffic Stream (ADDTS) message, the second message is one of a Dynamic Service Addition (DSA) message or a Packet Cable Multi-Media (PCMM) QoS creation request.

3. The method of claim 1, wherein the steps (a)-(e) are performed by a wireless gateway integrated with a cable modem, or a standalone wireless gateway.

4. The method of claim 1, wherein the wired device is one of a cable modem termination system or an application server.

5. The method of claim 1, wherein the determining step comprises determining the second set of QoS parameters based on mapping rules that map the first set of parameters to the second set of parameters.

6. The method of claim 1, wherein the first set of parameters are IEEE 802.11(e) Traffic Specification (TSpec) parameters and the second set of parameters are Data Over Cable Service Interface Specification (DOCSIS) Service Flow (SF) parameters.

7. The method of claim 1, wherein the wireless network is a Wireless Local Area Network (WLAN) and the wired network is a Data Over Cable Service Interface Specification (DOCSIS).

8. The method of claim 1, wherein the first set of QoS parameters includes one or more of: user priority, maximum Media Access Control Service Data Unit (MSDU) size, max burst size, minimum Physical Layer (PHY) rate, peak date rate, mean data rate, delay bound, nominal MSDU size and maximum service interval.

9. The method of claim 1, wherein the second set of QoS parameters includes one or more of: traffic priority, maximum traffic burst, minimum reserved traffic rate, maximum sustained traffic rate, tolerated poll jitter for Unsolicited Grant Service (UGS) and nominal Grant Interval for UGS.

10. The method of claim 1, further comprising repeating steps (a)-(e) if the second set of QoS parameters is not accepted by the wired device.

11. A method to setup Quality of Service (QoS) parameters over a wired network and over a wireless network, wherein a request to setup the QoS parameters is initiated by a wired device, comprising: (a) receiving a first message from the wired device, wherein the first message includes a first set of QoS parameters requested by the wired device; (b) determining a second set of QoS parameters for transmission over a wireless network corresponding to the first set of QoS parameters; (c) transmitting a second message to a wireless device including the second set of QoS parameters; (d) receiving a request, in response to the second message, from the wireless device to setup QoS over the wireless network based on the second set of QoS parameters; and (e) transmitting a response to the first message, based on the received request from the wireless device, to the wired device indicating whether the first set of QoS parameters are acceptable.

12. The method of claim 11, wherein the first message is one of a Dynamic Service Addition (DSA) message or a Packet Cable Multi-Media (PCMM) QoS creation request and the second message is an Add Traffic Stream (ADDTS) trigger that is configured to trigger an ADDTS message from the wireless device and the response to the second message is an ADDTS message.

13. The method of claim 11, wherein the steps (a)-(e) are performed by a wireless gateway integrated with a cable modem or a standalone wireless gateway.

14. The method of claim 11, wherein the wired device is one of a cable modem termination system or an application server.

15. The method of claim 11, wherein the determining step comprises determining the second set of QoS parameters based on mapping rules that map the first set of QoS parameters to the second set of QoS parameters.

16. The method of claim 11, wherein the first set of QoS parameters are DOCSIS Service Flow parameters and the second set of QoS parameters are IEEE 802.11(e) Traffic Specification (TSpec) parameters.

17. The method of claim 11, wherein the wireless network is a Wireless Local Area Network (WLAN) and the wired network is a Data Over Cable Service Interface Specification (DOCSIS) network.

18. The method of claim 11, wherein the first set of QoS parameters include one or more of traffic priority, maximum traffic burst, minimum reserved traffic rate, maximum sustained traffic rate, tolerated poll jitter for Unsolicited Grant Service (UGS) and nominal Grant Interval for UGS.

19. The method of claim 11, wherein the second set of QoS parameters include one or more of user priority, maximum Media Access Control Service Data Unit (MSDU) size, max burst size, minimum Physical Layer (PHY) rate, peak date rate, mean data rate, delay bound, nominal MSDU size and maximum service interval.

20. The method of claim 11, further comprising repeating steps (a)-(e) if the second set of QoS parameters are not accepted by the wireless device.

21. A system to setup Quality of Service (QoS) parameters over a wireless network and over a wired network, wherein a request to setup the QoS parameters is initiated by a wireless device, comprising: a memory; and a processor that maps a first set of QoS parameters over a wireless network to a corresponding second set of QoS parameters over a wired network, based on instructions stored in the memory, wherein the processor is configured to: (a) receive a first message from the wireless device, wherein the first message includes the first set of QoS parameters requested by the wireless device; (b) determine a second set of QoS parameters for transmission over a wired network corresponding to the first set of QoS parameters; (c) transmit a second message to a wired device including the second set of QoS parameters; (d) receive a response to the second message from the wired device that indicates whether the second set of QoS parameters was accepted by the wired device; and (e) transmit a response to the first message, based on the response to the second message, to the wireless device that indicates whether the first set of QoS parameters are acceptable.

22. The system of claim 21, wherein the processor is configured to, based on instructions stored in the memory, repeat steps (a)-(e) if the second set of QoS parameters are not accepted by the wired device.

23. The system of claim 21, wherein the system is a wireless gateway integrated with a cable modem or a standalone wireless gateway.

24. The system of claim 21, wherein the wired device is a cable modem termination system or an application server.

25. The system of claim 21, wherein the first message is an Add Traffic Stream (ADDTS) message, the second message is one of a Dynamic Service Addition (DSA) message or a Packet Cable Multi-Media (PCMM) QoS creation request.

26. The system of claim 21, wherein the wireless network is a Wireless Local Area Network (WLAN) and the wired network is a Data Over Cable Service Interface Specification (DOCSIS) network.

27. The system of claim 21, wherein the processor is configured to, based on instructions in memory, determine the second set of QoS parameters based on mapping rules that map the first set of QoS parameters to the second set of QoS parameters.

28. The system of claim 21, wherein the first set of QoS parameters are IEEE 802.11e Traffic Specification (TSpec) parameters and the second set of QoS parameters are Data Over Cable Service Interface Specification (DOCSIS) Service Flow (SF) parameters.

29. The system of claim 21, wherein the first set of QoS parameters are one or more of user priority, maximum Media Access Control Service Data Unit (MSDU) size, max burst size, minimum Physical Layer (PHY) rate, peak date rate, mean data rate, delay bound, nominal MSDU size and maximum service interval.

30. The system of claim 21, wherein the second set of QoS parameters are one or more of traffic priority, maximum traffic burst, minimum reserved traffic rate, maximum sustained traffic rate, tolerated poll jitter for Unsolicited Grant Service (UGS) and nominal Grant Interval for UGS.

31. A system to setup Quality of Service (QoS) parameters over a wireless network and over a wired network, wherein a request to setup the QoS parameters is initiated by a wired device, comprising, comprising: a memory; and a processor that maps a first Quality of Service parameter over the wired network to a corresponding second Quality of Service parameter over a wireless network, based on instructions stored in the memory, wherein the processor is configured to: (a) receive a first message from a wired device, wherein the first message includes a first set of QoS parameters requested by the wired device; (b) determine a second set of QoS parameters for transmission over the wireless network corresponding to the first set of QoS parameters; (c) transmit a second message to the wireless device that includes the second set of QoS parameters corresponding to the first set of QoS parameters; (d) receive a request, in response to the second message, from the wireless device to setup QoS over the wireless network based on the second set of QoS parameters; and (e) transmit a response to the first message, based on received request from the wireless device, to the wired device that indicates whether the first set of QoS parameters are acceptable.

32. The system of claim 31, wherein the processor is configured to, based on instructions stored in the memory, repeat steps (a)-(e) if the second set of QoS parameters are not accepted by the wireless device.

33. The system of claim 31, wherein the system is a wireless gateway integrated with a cable modem, or a standalone wireless gateway.

34. The system of claim 31, wherein the wired device is a cable modem termination system or an application server.

35. The system of claim 31, wherein the first message is one of a Dynamic Service Addition (DSA) message or a Packet Cable Multi-Media (PCMM) QoS creation request and the second message is an Add Traffic Stream (ADDTS) trigger that is configured to trigger an ADDTS message from the wireless device and the response to the second message is an ADDTS message.

36. The system of claim 31, wherein the wireless network is a Wireless Local Area Network (WLAN) and the wired network is a Data Over Cable Service Interface Specification (DOCSIS) network.

37. The system of claim 31, wherein the processor is configured to, based on instructions in memory, determine the second set of QoS parameters based on a mapping table that maps the first set of QoS parameters to the second set of QoS parameters.

38. The system of claim 31, wherein the first set of QoS parameters are Data Over Cable Service Interface Specification (DOCSIS) Service Flow (SF) parameters and the second set of QoS parameters are IEEE 802.11(e) Traffic Specification (TSpec) parameters.

39. The system of claim 31, wherein the first set of QoS parameters include one or more of traffic priority, maximum traffic burst, minimum reserved traffic rate, maximum sustained traffic rate, tolerated poll jitter for Unsolicited Grant Service (UGS) and nominal Grant Interval for UGS.

40. The system of claim 31, wherein the second set of QoS parameters include one or more of user priority, maximum Media Access Control Service Data Unit (MSDU) size, max burst size, minimum Physical Layer (PHY) rate, peak date rate, mean data rate, delay bound, nominal MSDU size and maximum service interval.