Title of Invention

A METHOD FOR REGISTERING A MULTISLOT CLASS FOR A MOBILE DEVICE IN A WIRELESS NETWORK

Abstract

A solution is provided wherein the mobile device selects a multislot class based on the profile of the traffic to be utilized by the mobile device. This may be performed manually by a user, or may be performed automatically where an application or driver software automatically and dynamically determines the best multislot class for the applications being used. This can be accomplished, for example, by looking at the classification of the transport control protocol (TCP) port numbers used, by examining the data sent and received by the network, and/or looking up a profile for the user or device, if the user changes applications or some other event occurs on the mobile device that might cause a change in the profile of the traffic, the mobile device may terminate its current multislot class assignment and re-announce itself, allowing the system to transfer the mobile device to a new multislot class.

Full Text

FIELD OF THE INVENTION [0001] The present invention relates to the field of wireless communications networks. More particularly, the present invention relates to configurable multislot classes for wireless devices. BACKGROUND OF THE INVENTION [0002] The mobile phone industry has ballooned into one of the most popular technological areas. The latest generation of mobile phone technology is known as the General Packet Radio Service (GPRS), which employs packet switching to allow mobile phones and pocket communication terminals to connect directly to remote networks via the Internet, at much higher bandwidths than older systems. Unlike the older cellular circuit switched data services, GPRS is an "always on" service that does not require the use of a dial-up modem. [0003] GPRS works by overlaying a packet switched data service on top of a circuit switched digital GSM telephone connection, which means that channel bandwidth is consumed only when users are actually sending or receiving data, rather than dedicating an entire channel to one use for a fixed period. [0004] GPRS may work in conjunction with the Enhanced Data rates GSM Evolution (EDGE), which is a faster version of GSM. The EDGE standard is built upon the existing GSM standard, using the same time-division multiple access (TDMA) frame structure and existing cell arrangements. [0005] Since the data transmissions in GPRS/EDGE networks are TDMA based on the number of active timeslots used for transmission or reception is a function of the "multislot class" of the device. The mobile terminal makes its multislot class known to the network during the registration process and it can be adjusted once the device is registered on the network. The multislot class defines the maximum number of slots assignable to downlink and uplink channels. FIG. 1 is a diagram illustrating a typical multislot class configuration table as defined in the GPRS Third Generation Partnership Project (3GPP) standard. [0006] The network totally controls the timeslot configuration assignment to the mobile devices and, as such, the mobile device has no control over this assignment (except when it advertises its multislot class). [0007] There are situations, however, where the network infastructure performs an ineffective assignment of timeslots based on the end user application. Broadly speaking, a network can perform an asymmetric timeslot, such as 4 timeslots for the downlink and 1 timeslot for the uplink. One example of an ineffective assignment occurs if the infrastructure effectively treats the timeslot assignment as static even after the downlink traffic goes idle. Treating the assignment as static could mean that only 1 uplink timeslot is used even when there is no downlink traffic. This results in poor uplink throughout for the end user. [0008] Another example of an ineffective assignment occurs in fairly symmetrical applications (e.g., VoIP). Here, on occasion, the network puts the mobile device into an asymmetric configuration even though the traffic is symmetrical. VoIP traffic typically requires more than 1 uplink timeslot to be effective, and thus placement in an asymmetrical configuration would reduce its effectiveness. [0009] These problems are exacerbated because the mobile device operating system is often not very smart - it always asks for the highest class it can. For example, mobile devices will often ask for class 10, which provides for a maximum 4 downlink slots and 2 uplink slots, with a total number of slots not exceeding 5 (see FIG. 1). This decision is made without regard to the type of traffic to the run on the device. The network then compounds this problem by assigning what it thinks is the best allocation of slots within the parameters of the class. For class 10, this typically means assigning 4 downlink slots and only 1 uplink slots. However, in certain circumstances, it might be more beneficial if the mobile device ran in class 9, as then the network could only assign 3 downlink slots and thus would be forced to assign 2 uplink slots as opposed to just 1. These circumstances leave the system completely at the mercy of the network, which has little or no information about the application traffic profile requirement, and yet has to make decisions regarding the class it will assign the device and the configuration of downlink slots and uplink slots it will select within the class. [0010] What is needed is a solution that allows for a more effective assignment of timeslots in a wireless network. BRIEF DESCRIPTION OF THE INVENTION [0011] A solution is provided wherein the mobile device selects a multislot class based on the profile of the traffic to be utilized by the mobile device. This may be performed manually by a user, or may be performed automatically where an application or driver software automatically and dynamically determines the best multislot class for the applications being used. This can be accomplished, for example, by looking at the classification of the transport control protocol (TCP) port numbers used, by examining the data sent and received by the network, and/or looking up a profile for the user or device. If the user changes applications or some other event occurs on the mobile device that might cause a change in the profile of the traffic, the mobile device may terminate its current multislot class assignment and re-announce itself, allowing the system to transfer the mobile device to a new multislot class. BRIEF DESCRIPTION OF THE DRAWINGS [0012] The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more embodiments of the present invention and, together with the detailed description, serve to explain the principles and implementations of the invention. [0013] In the drawings: FIG. 1 is a diagram illustrating a typical multislot class configuration table as defined in the GPRS Third Generation Partnership Project (3GPP) standard. FIG. 2 is a flow diagram illustrating a method for registering a multislot class for a mobile device in a wireless network in accordance with an embodiment of the present invention. FIG. 3 is a flow diagram illustrating a method for registering a multislot class for a mobile device in a wireless network in accordance with another embodiment of the present invention. FIG. 4 is a block diagram illustrating an apparatus for registering a multislot class for a mobile device in a wireless network in accordance with another embodiment of the present invention. DETAILED DESCRIPTION [0014] Embodiments of the present invention are described herein in the context of a system of computers, servers, and software. Those of ordinary skill in the art will realize that the following detailed description of the present invention is illustrative only and is not intended to be in any way limiting. Other embodiments of the present invention will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to implementations of the present invention as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following detailed description to refer to the same or like parts. [0015] In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with application- and business-related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure. [0016] In accordance with the present invention, the components, process steps, and/or data structures may be implemented using various types of operating systems, computing platforms, computer programs, and/or general purpose machines. In addition, those of ordinary skill in the art will recognize that devices of a less general purpose nature, such as hardwired devices, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herein. [0017] A solution is provided wherein the mobile device selects a multislot class based on the profile of the traffic to be utilized by the mobile device. This may be performed manually by a user, or may be performed automatically where an application or driver software automatically and dynamically determines the best multislot class for the applications being used. This can be accomplished, for example, by looking at the classification of the transport control protocol (TCP) port numbers used, by examining the data sent and received by the network, and/or looking up a profile for the user or device. If the user changes applications or some other event occurs on the mobile device that might cause a change in the profile of the traffic, the mobile device may terminate its current multislot class assignment and re-announce itself, allowing the system to transfer the mobile device to a new multislot class. [0018] FIG. 2 is a flow diagram illustrating a method for registering a multislot class for a mobile device in a wireless network in accordance with an embodiment of the present invention. At 200, the port ID of the traffic may be checked against a traffic profile database. This database may be a predetermined lookup table, or may be a well known lookup table such as one from the Internet Engineering Task Force (IETF). It should also be noted that utilizing the port ID of the traffic is just one example of the ways that the traffic profile for the traffic may be identified. Other examples include examining the data sent and received by the network, looking up a profile for the user or device, checking the names of applications being run, etc. It should additionally be noted that any lookup table created for such purposes may be modified through the use of a learned process, wherein traffic patterns are examined over time to determine which traffic types belong in which multislot classes. [0019] As part of this process, at 202, it may be determined if the data traffic profile is balanced. If not, then at 204, the mobile device may register itself as class 10, thus likely providing 4 downlink slots and 1 uplink slot. If, however, the data traffic profile is balanced, then the mobile device may register itself as class 9, thus likely providing 3 downlink slots and 2 uplink slots. [0020] FIG. 3 is a flow diagram illustrating a method for registering a multislot class for a mobile device in a wireless network in accordance with another embodiment of the present invention. At 300, it may be determined if a traffic profile for the mobile device is balanced, wherein the determining is performed by the mobile device. This may include, for example, comparing a port identification for an application on the mobile device with a look-up table to retrieve the traffic profile for the mobile device, examining data sent and received by the mobile device to determine a pattern for the traffic profile for the mobile device, or looking up a profile for the user/device combination. For the look-up table case, the look-up table may be predetermined or created through a learned process. At 302, if the mobile device traffic profile is balanced, then at 302 the mobile device may be registered as a symmetric multislot class, for example, class 9 of the GPRS 3GPP standard. If, on the other hand, the mobile device traffic profile is not balanced, then at 304, the mobile device may be registered as an asymmetric multislot, for example, class 10 of the GPRS 3GPP standard. [0021] FIG. 4 is a block diagram illustrating an apparatus for registering a multislot class for a mobile device in a wireless network in accordance with another embodiment of the present invention. A mobile device traffic profile determiner 400 may determine if a traffic profile for the mobile device is balanced, wherein the determining is performed by the mobile device. This may include, for example, comparing a port identification for an application on the mobile device with a look-up table to retrieve the traffic profile for the mobile device using a port identification look-up table comparer 402, examining data sent and received by the mobile device to determine a pattern for the traffic profile for the mobile device using a mobile device traffic data pattern examiner 404, or looking up a profile for the user/device combination using a user/device combination profile retriever 406. For the look-up table case, the look-up table may be predetermined or created through a learned process. If the mobile device traffic profile is balanced, then a mobile device symmetric multislot class registerer 408 coupled to the mobile device traffic profile determiner 400 may register the mobile device as a symmetric multislot class, for example, class 9 of the GPRS 3 GPP standard. If, on the other hand, the mobile device traffic profile is not balanced, then a mobile device asymmetric multislot class registerer 410 coupled to the mobile device traffic profile determiner 400 may register the mobile device as an asymmetric multislot, for example, class 10 of the GPRS 3GPP standard. [0022] While embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts herein. The invention, therefore, is not to be restricted except in the spirit of the appended claims. WE CLAIM: 1. A method for registering a multislot class for a mobile device in a wireless network, the method comprising: determining if a traffic profile for the mobile device is balanced, wherein said determining is performed by said mobile device; registering said mobile device as a symmetric multislot class if said mobile device traffic profile is balanced; and registering said mobile device as an asymmetric multislot class if said mobile device traffic profile is not balanced. 2. The method of claim 1, wherein said determining includes: comparing a port identification for an application on the mobile device with a look-up table to retrieve said traffic profile for the mobile device. 3. The method of claim 1, wherein said determining includes: examining data sent and received by the mobile device to determine a pattern for said traffic profile for the mobile device. 4. The method of claim 1, wherein said determining includes: looking up a profile for said user/device combination. 5. The method of claim 2, wherein said look-up table is predetermined. 6. The method of claim 2, wherein said look-up table is created through a learned process. 7. The method of claim 1, wherein said symmetric multislot class is class 9 as defined by the General Packet Radio Services (GPRS) Third Generation Partnership Project (3GPP) standard. 8. The method of claim 1, wherein said asymmetric multislot class is class 10 as defined by the General Packet Radio Services (GPRS) Third Generation Partnership Project (3GPP). 9. An apparatus for registering a multislot class for a mobile device in a wireless network, the apparatus comprising: a mobile device traffic profile determiner; a mobile device symmetric multislot class registerer coupled to said mobile device traffic profile determiner; a mobile device asymmetric multislot class registerer coupled to said mobile device traffic profile determiner. 10. The apparatus of claim 1, wherein said mobile device traffic profile determiner includes: a port identification look-up table comparer. 11. The apparatus of claim 1, wherein said mobile device traffic profile determiner includes: a mobile device traffic data pattern examiner. 12. The apparatus of claim 1, wherein said mobile device traffic profile determiner includes: a user/device combination profile retriever. 13. An apparatus for registering a multislot class for a mobile device in a wireless network, the apparatus comprising: means for determining if a traffic profile for the mobile device is balanced, wherein said determining is performed by said mobile device; means for registering said mobile device as a symmetric multislot class if said mobile device traffic profile is balanced; and means for registering said mobile device as an asymmetric multislot class if said mobile device traffic profile is not balanced. 14. The apparatus of claim 13, wherein said means for determining includes: means for comparing a port identification for an application on the mobile device with a look-up table to retrieve said traffic profile for the mobile device. 15. The apparatus of claim 13, wherein said means for determining includes: means for examining data sent and received by the mobile device to determine a pattern for said traffic profile for the mobile device. 16. The apparatus of claim 13, wherein said means for determining includes: means for looking up a profile for said user/device combination. 17. The apparatus of claim 14, wherein said look-up table is predetermined. 18. The apparatus of claim 14, wherein said look-up table is created through a learned process. 19. The apparatus of claim 13, wherein said symmetric multislot class is class 9 as defined by the General Packet Radio Services (GPRS) Third Generation Partnership Project (3GPP) standard. 20. The apparatus of claim 13, wherein said asymmetric multislot class is class 10 as defined by the General Packet Radio Services (GPRS) Third Generation Partnership Project (3GPP). 21. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform a method for registering a multislot class for a mobile device in a wireless network, the method comprising: determining if a traffic profile for the mobile device is balanced, wherein said determining is performed by said mobile device; registering said mobile device as a symmetric multistat class if said mobile device traffic profile is balanced; and registering said mobile device as an asymmetric multistat class if said mobile device traffic profile is not balanced.

Documents:

4745-CHENP-2007 AMENDED CLAIMS 29-05-2012.pdf

4745-CHENP-2007 AMENDED PAGES OF SPECIFICATION 29-05-2012.pdf

4745-CHENP-2007 CORRESPONDENCE OTHERS 21-07-2011.pdf

4745-CHENP-2007 CORRESPONDENCE OTHERS 31-01-2013.pdf

4745-CHENP-2007 EXAMINATION REPORT REPLY RECEIVED 05-10-2012.pdf

4745-CHENP-2007 EXAMINATION REPORT REPLY RECEIVED 29-05-2012.pdf

4745-CHENP-2007 FORM-1 29-05-2012.pdf

4745-CHENP-2007 FORM-3 29-05-2012.pdf

4745-CHENP-2007 OTHER PATENT DOCUMENT 29-05-2012.pdf

4745-CHENP-2007 POWER OF ATTORNEY 29-05-2012.pdf

4745-CHENP-2007 CORRESPONDENCE OTHERS 28-02-2013.pdf

4745-CHENP-2007 CORRESPONDENCE OTHERS 14-09-2011.pdf

4745-CHENP-2007 CORRESPONDENCE OTHERS 18-11-2010.pdf

4745-chenp-2007 correspondence others 22-07-2009.pdf

4745-CHENP-2007 CORRESPONDENCE OTHERS 29-06-2012.pdf

4745-CHENP-2007 FORM-13 15-06-2009.pdf

4745-CHENP-2007 FORM-3 14-09-2011.pdf

4745-chenp-2007 form-3 22-07-2009.pdf

4745-CHENP-2007 FORM-3 29-06-2012.pdf

4745-CHENP-2007 AMENDED CLAIMS 28-02-2013.pdf

4745-chenp-2007 correspondence others.pdf

4745-CHENP-2007 FORM-1 28-02-2013.pdf

4745-chenp-2007 form-26.pdf

4745-CHENP-2007 FORM-3 15-12-2009.pdf

4745-CHENP-2007 OTHER DOCUMENT 22-07-2009.pdf

4745-chenp-2007-abstract.pdf

4745-chenp-2007-assignement.pdf

4745-chenp-2007-claims.pdf

4745-chenp-2007-correspondnece-others.pdf

4745-chenp-2007-description(complete).pdf

4745-chenp-2007-drawings.pdf

4745-chenp-2007-form 1.pdf

4745-chenp-2007-form 26.pdf

4745-chenp-2007-form 3.pdf

4745-chenp-2007-form 5.pdf

4745-chenp-2007-pct.pdf