Method for increasing synchronous control channel capacity in a wireless system
Claim Score by NHIP
Abstract
A method is provided for controlling delivery of packets over a synchronous control channel in a wireless system employing the High Rate Packet Data (HRPD) standard. The synchronous channel is comprised of a plurality of slots, and a first packet is sent over the synchronous control channel in a first one of the plurality of slots along with an indication of a second one of the plurality of slots in which a second packet will be delivered. Thereafter, the second packet is sent over the control channel in the second one of the plurality of slots. Subsequent packets are handled similarly.

Term
Projected expiry 17 June 2028.
- Priority and filed
- Published
- Today
- Projected expiry
6 claims: 2 independent, 4 dependent
- 1A method for controlling delivery of packets over a control channel comprised of a plurality of slots, comprising:sending a first packet over the control channel in a first one of the plurality of slots along with an indication of a second one of the plurality of slots in which a second packet will be delivered;and sending the second packet over the control channel in the second one of the plurality of slots.
- 4Broadest claimClaim Score 88, very broad(NHIP)A method for controllably receiving packets over a control channel comprised of a plurality of slots, comprising:receiving a first packet over the control channel in a first one of the plurality of slots along with an indication of a second one of the plurality of slots in which a second packet will be received;and monitoring the second one of the plurality of slots to receive the second packet.
Independent claims2
40 paragraphs in 4 sections, as filed
BACKGROUND OF THE INVENTION
00011. Field of the Invention
0002This invention relates generally to telecommunications, and, more particularly, to wireless communications.
00032. Description of the Related Art
0004In the field of wireless telecommunications, such as cellular telephony, a system typically includes a plurality of base stations (e.g., Node Bs) distributed within an area to be serviced by the system. Various Access Terminals (ATs, also known as User Equipment (UE), mobile devices, and the like) within the area may then access the system and, thus, other interconnected telecommunications systems, via one or more of the base stations. Typically, an AT maintains communications with the system as it passes through an area by communicating with one and then another base station, as the AT moves. The AT may communicate with the closest base station, the base station with the strongest signal, the base station with a capacity sufficient to accept communications, etc.
0005Communications between the ATs and the base stations may occur over a variety of channels, including dedicated and shared channels. Typically, when an AT is not currently involved in a communication session, it enters an idle mode of operation where the dedicated channels are dropped and it monitors only a shared channel to periodically determine if the base station is attempting to contact it. For example, in a wireless data technology known as High Rate Packet Data (HRPD), a control channel protocol provides a mechanism for an access network to deliver broadcast, multicast and unicast messages to idle and active ATs. The synchronous control channel is typically used to carry overhead messages, multicast and unicast messages (e.g., paging signals) to idle ATs. Currently, the forward link employs a 4-slot interlace structure, and the synchronous control channel can only use one of the 4 interlaces. Therefore, the maximum capacity of the synchronous control channel is 25% of the total forward link slots.
0006However, synchronous control channel usage has increased dramatically such that the 25% usage rate has become problematic. For example, with more applications (such as VoIP, PTT, Video Telephony) being employed in HRPD systems, control channel usage has increased significantly. Delivery of Page messages introduces very heavy traffic on the synchronous control channel. Additionally, for many attractive applications (such as, emergent notifications, community services, targeted advertisements, etc.), it is very fast, flexible and efficient to deliver short multicast messages to a group of people over the synchronous control channel. Further, Data over Signaling protocol, introduced in HRPD Rev. A, allows short data burst to be encapsulated in signaling messages and delivered over the synchronous control channel. Therefore, it becomes highly probable that the 25% usage rate of the forward link slots will be insufficient to accommodate all the traffic on the synchronous control channel.
SUMMARY OF THE INVENTION
0007The present invention is directed to addressing the effects of one or more of the problems set forth above. The following presents a simplified summary of the invention in order to provide a basic understanding of some aspects of the invention. This summary is not an exhaustive overview of the invention. It is not intended to identify key or critical elements of the invention or to delineate the scope of the invention. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is discussed later.
0008In one aspect of the instant invention, a method is provided for controlling delivery of packets over a control channel comprised of a plurality of slots. The method comprises sending a first packet over the control channel in a first one of the plurality of slots along with an indication of a second one of the plurality of slots in which a second packet will be delivered. Thereafter, the second packet is sent over the control channel in the second one of the plurality of slots.
0009In another aspect of the instant invention, a method is provided for controllably receiving packets over a control channel comprised of a plurality of slots. The method comprises receiving a first packet over the control channel in a first one of the plurality of slots along with an indication of a second one of the plurality of slots in which a second packet will be received. Thereafter, the second one of the plurality of slots is monitored to receive the second packet.
BRIEF DESCRIPTION OF THE DRAWINGS
0010The invention may be understood by reference to the following description taken in conjunction with the accompanying drawings, in which like reference numerals identify like elements, and in which:
0011<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram of a communications system, in accordance with one embodiment of the present invention;
0012<figref idref="DRAWINGS">FIG. 2</figref> depicts a block diagram of one embodiment of a base station, an access terminal and a radio network controller used in the communications system of <figref idref="DRAWINGS">FIG. 1</figref>;
0013<figref idref="DRAWINGS">FIG. 3</figref> depicts a stylistic representation of forward link interlaces of the HRPD system;
0014<figref idref="DRAWINGS">FIG. 4</figref> is one embodiment of a flow chart representation of a method that may be used by the base stations of <figref idref="DRAWINGS">FIGS. 1 and 2</figref> to provide greater utilization of the forward link slots of the synchronous control channel; and
0015<figref idref="DRAWINGS">FIG. 5</figref> is one embodiment of a flow chart representation of a method that may be used by the access terminals of <figref idref="DRAWINGS">FIGS. 1 and 2</figref> to provide greater utilization of the forward link slots of the synchronous control channel.
0016While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the description herein of specific embodiments is not intended to limit the invention to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the appended claims.
DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS
0017Illustrative embodiments of the invention are described below. In the interest of clarity, not all features of an actual implementation may be described in this specification. It will of course be appreciated that in the development of any such actual embodiment, numerous implementation-specific decisions may be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but may nevertheless be a routine undertaking for those of ordinary skill in the art having the benefit of this disclosure.
0018Portions of the present invention and corresponding detailed description are presented in terms of software, or algorithms and symbolic representations of operations on data bits within a computer memory. These descriptions and representations are the ones by which those of ordinary skill in the art effectively convey the substance of their work to others of ordinary skill in the art. An algorithm, as the term is used here, and as it is used generally, is conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of optical, electrical, or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
0019It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise, or as is apparent from the discussion, terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical, electronic quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
0020Note also that the software implemented aspects of the invention are typically encoded on some form of program storage medium or implemented over some type of transmission medium. The program storage medium may be magnetic (e.g., a floppy disk or a hard drive) or optical (e.g., a compact disk read only memory, or “CD ROM”), and may be read only or random access. Similarly, the transmission medium may be twisted wire pairs, coaxial cable, optical fiber, or some other suitable transmission medium known to the art. The invention is not limited by these aspects of any given implementation.
0021The present invention will now be described with reference to the attached figures. Various structures, systems and devices are schematically depicted in the drawings for purposes of explanation only and so as to not obscure the present invention with details that are well known to those skilled in the art. Nevertheless, the attached drawings are included to describe and explain illustrative examples of the present invention. The words and phrases used herein should be understood and interpreted to have a meaning consistent with the understanding of those words and phrases by those skilled in the relevant art. No special definition of a term or phrase, i.e., a definition that is different from the ordinary and customary meaning as understood by those skilled in the art, is intended to be implied by consistent usage of the term or phrase herein. To the extent that a term or phrase is intended to have a special meaning, i.e., a meaning other than that understood by skilled artisans, such a special definition will be expressly set forth in the specification in a definitional manner that directly and unequivocally provides the special definition for the term or phrase.
0022Turning now to the drawings, and specifically referring to <figref idref="DRAWINGS">FIG. 1</figref>, a communications system <b>100</b> is illustrated, in accordance with one embodiment of the present invention. For illustrative purposes, the communications system <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref> is an architecture based on the High Rate Packet Data (HRPD) standard, although it should be understood that the present invention may find application in other systems that support data and/or voice communication. The communications system <b>100</b> allows one or more ATs <b>120</b> to communicate with a data network <b>125</b>, such as the Internet, through one or more base stations <b>130</b>. The AT <b>120</b> may take the form of any of a variety of devices, including cellular phones, personal digital assistants (PDAs), laptop computers, digital pagers, wireless cards, and any other device capable of accessing the data network <b>125</b> through the base station <b>130</b>.
0023In one embodiment, a plurality of the base stations <b>130</b> may be coupled to a Radio Network Controller (RNC) <b>138</b>(<b>1</b>-<b>2</b>) by one or more connections <b>139</b>. Although two RNCs <b>138</b>(<b>1</b>-<b>2</b>) are illustrated, those skilled in the art will appreciate that more RNCs <b>138</b> may be utilized to interface with a large number of base stations <b>130</b>. Generally, the RNC <b>138</b> provides signaling and traffic processing for each wireless data session. The AT <b>120</b>, base station <b>130</b>, RNC <b>138</b> and the interfaces between these components comprises a radio access network (RAN).
0024The RNC <b>138</b> is coupled to a Core Network (CN) <b>165</b> via a connection <b>145</b>. Generally, the CN <b>165</b> operates as an interface to a data network <b>125</b> and/or to a public telephone system (PSTN) <b>160</b>. The CN <b>165</b> performs a variety of functions and operations, such as user authentication, however, a detailed description of the structure and operation of the CN <b>165</b> is not necessary to an understanding and appreciation of the instant invention. Accordingly, to avoid unnecessarily obfuscating the instant invention, further details of the CN <b>165</b> are not presented herein.
0025The data network <b>125</b> may be a packet-switched data network, such as a data network according to the Internet Protocol (IP). One version of IP is described in Request for Comments (RFC) <b>791</b>, entitled “Internet Protocol,” dated September 1981. Other versions of IP, such as IPv6, or other connectionless, packet-switched standards may also be utilized in further embodiments. A version of IPv6 is described in RFC 2460, entitled “Internet Protocol, Version 6 (IPv6) Specification,” dated December 1998. The data network <b>125</b> may also include other types of packet-based data networks in further embodiments. Examples of such other packet-based data networks include Asynchronous Transfer Mode (ATM), Frame Relay networks, and the like.
0026As utilized herein, a “data network” may refer to one or more communication networks, channels, links, or paths, and systems or devices (such as routers) used to route data over such networks, channels, links, or paths.
0027Thus, those skilled in the art will appreciate that the communications system <b>100</b> facilitates communications between the ATs <b>120</b> and the data network <b>125</b>. It should be understood, however, that the configuration of the communications system <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref> is exemplary in nature, and that fewer or additional components may be employed in other embodiments of the communications system <b>100</b> without departing from the spirit and scope of the instant invention.
0028Referring now to <figref idref="DRAWINGS">FIG. 2</figref>, a block diagram of one embodiment of a functional structure associated with an exemplary base station <b>130</b> and AT <b>120</b> is shown. The base station <b>130</b> includes an interface unit <b>200</b>, a controller <b>210</b>, an antenna <b>215</b> and a plurality of channels: a shared channel <b>220</b>, a data channel <b>230</b>, and a control channel <b>240</b>. The interface unit <b>200</b>, in the illustrated embodiment, controls the flow of information between the base station <b>130</b> and the RNC <b>138</b> (see <figref idref="DRAWINGS">FIG. 1</figref>). The controller <b>210</b> generally operates to control both the transmission and reception of data and control signals over the antenna <b>215</b> and the plurality of channels <b>220</b>, <b>230</b>, <b>240</b> and to communicate at least portions of the received information to the RNC <b>138</b> via the interface unit <b>200</b>. For example, one piece of information transmitted from the base station <b>130</b> to the RNC <b>138</b> is information used by the base station <b>130</b> to communicate with the ATs <b>120</b>.
0029The AT <b>120</b> shares certain functional attributes with the base station <b>130</b>. For example, the AT <b>120</b> includes a controller <b>250</b>, an antenna <b>255</b> and a plurality of channels: a shared channel <b>260</b>, a data channel <b>270</b>, and a control channel <b>280</b>. The controller <b>250</b> generally operates to control both the transmission and reception of data and control signals over the antenna <b>255</b> and the plurality of channels <b>260</b>, <b>270</b>, <b>280</b>.
0030Normally, the channels <b>260</b>, <b>270</b>, <b>280</b> in the AT <b>120</b> communicate with the corresponding channels <b>220</b>, <b>230</b>, <b>240</b> in the base station <b>130</b>. Under the operation of the controllers <b>210</b>, <b>250</b>, the channels <b>220</b>, <b>260</b>; <b>230</b>, <b>270</b>; <b>240</b>, <b>280</b> are used to effect a controlled scheduling for communications from the AT <b>120</b> to the base station <b>130</b>.
0031Referring now to <figref idref="DRAWINGS">FIG. 3</figref>, a stylistic representation of a forward link synchronous control channel <b>300</b> having a 4-slot interlace structure is depicted. In a wireless system employing the HRPD standard, the synchronous control channel <b>300</b> is divided into a 4-slot interlace. That is, beginning with slot <b>1</b>, every fourth slot (e.g., slot <b>5</b>, slot <b>9</b>, etc.) is assigned to a first interlace <b>301</b>. Similarly, slot <b>2</b> and every fourth slot thereafter (e.g., slot <b>6</b>, slot <b>10</b>, etc.) is assigned to a second interlace <b>302</b>. Slot <b>3</b> and every fourth slot thereafter (e.g., slot <b>7</b>, slot <b>11</b>, etc.) is assigned to a third interlace <b>303</b>. Likewise, slot <b>4</b> and every fourth slot thereafter (e.g., slot <b>8</b>, slot <b>12</b>, etc.) is assigned to a fourth interlace <b>304</b>.
0032In one embodiment of the instant invention, the synchronous control channel <b>300</b> is capable of employing all four interlaces <b>301</b>-<b>304</b>, rather than just one interlace, so that its capacity is significantly improved. The first packet of the synchronous control channel <b>300</b> is sent in the interlace <b>301</b>-<b>304</b> specified in the current standard, such as the first interlace <b>301</b> in slot <b>1</b>. All subsequent packets, sent after the transmission of the first packet is completed, may be sent in any one of the four interlaces <b>301</b>-<b>304</b>.
0033In one embodiment of the instant invention, broadcast, multicast and unicast messages may be handled separately. Broadcast messages may be transmitted the same way as in the current HRPD standard. That is, broadcast messages may be transmitted in only one of the interlaces <b>301</b>-<b>304</b>, the specified interlace, such as the first interlace <b>301</b> at slots <b>1</b>, <b>5</b>, <b>9</b>, etc. The ATs <b>120</b> need only monitor the specified interlace <b>301</b>-<b>304</b> until the synchronous control channel capsule in that interlace finishes.
0034As shown in the flowchart representations of <figref idref="DRAWINGS">FIGS. 4 and 5</figref>, multicast packets are handled differently. Turning first to <figref idref="DRAWINGS">FIG. 4</figref>, the operation of the base station <b>130</b> during a multicast transmission is shown. As shown in block <b>400</b>, the base station <b>130</b> transmits the first multicast packet for a multicast group in the same way as the current standard, so that the ATs <b>120</b> receive it by monitoring the specified interlace <b>301</b>-<b>304</b>, such as the first interlace <b>301</b> at slots <b>1</b>, <b>5</b>, <b>9</b>, etc. Thereafter, multicast packets may be sent in any subsequent interlace <b>301</b>-<b>304</b>. An optional field is added in the MAC overhead of the multicast packet to indicate the interlace and/or time slot location of the next packet that the ATs <b>120</b> in the multicast group should monitor. If the field is omitted, the current standard rules. In this way, part of the multicast messages can be sent outside the regular synchronous control channel interlaces and/or time slots. For example, the first packet in the first interlace <b>301</b> at time slot <b>1</b> may include the optional field to indicate that the next packet will be sent in the second interlace <b>302</b> at the time slots <b>2</b>, <b>6</b>, <b>10</b> etc. Thereafter, the packet contained in the second interlace <b>302</b> at time slot <b>2</b> may include the optional field to indicate that the next packet will be sent in the third interlace <b>303</b> at time slot <b>3</b>. Likewise, the third interlace <b>303</b> may include the optional field to indicate that the next packet will be sent in the fourth interlace <b>304</b> at time slot <b>4</b>. In this manner, the base station <b>130</b> may use all, or a desired portion, of the interlaces <b>301</b>-<b>301</b> to transmit the multicast packets, as shown in block <b>402</b>.
0035Turning to <figref idref="DRAWINGS">FIG. 5</figref>, the operation of the AT <b>120</b> during a multicast transmission is shown. At block <b>500</b>, the AT <b>120</b> monitors the specified interlace <b>301</b>-<b>304</b> for the first packet of the multicast message, such as the first interlace <b>301</b> at time sots <b>1</b>, <b>5</b>, etc. At block <b>502</b>, the AT <b>120</b> inspects the multicast message to determine which interlace <b>301</b>-<b>304</b> to monitor for the next multicast packet. If the optional field is not included in the multicast packet, then control transfers to block <b>500</b> where the AT <b>120</b> again monitors the next default or specified interlace <b>301</b>-<b>304</b>. Alternatively, if the optional field is included in the multicast packet, then at block <b>504</b>, the AT <b>120</b> monitors the identified interlace <b>301</b>-<b>304</b>, such as the second interlace <b>302</b> at time slots <b>2</b>,<b>6</b>, etc.
0036Increasing the capacity of the synchronous control channel <b>300</b> to handle unicast messages can be achieved in two ways. The approach described above for multicast packets may be applied to unicast packets as well. Alternatively, the base station <b>130</b> may send a broadcast message, or add a new field in an existing broadcast message, to indicate which of the interlaces <b>301</b>-<b>304</b> available for unicast messages over the synchronous control channel <b>300</b>. A hashing function is specified to let each AT <b>120</b> determine which interlace(s) <b>301</b>-<b>304</b> it needs to monitor for unicast messages over the synchronous control channel <b>300</b>. A matching hashing function is implemented in the base station to determine the interlaces <b>301</b>-<b>304</b> in which to send the unicast packets.
0037In one embodiment of the instant invention, all the other functions in the current HRPD standard may remain the same. Additionally, existing overhead messages, such as Qpage, can be used to notify the idle mobile terminals of upcoming messages on the synchronous control channel <b>300</b> so as to reduce power consumption by the AT <b>120</b> due to wake-ups.
0038Those skilled in the art will appreciate that in addition to increasing the synchronous control channel capacity, the instant invention also improves message delivery latency because multiple packets can be sent in parallel in different interlaces.
0039Those skilled in the art will appreciate that the various system layers, routines, or modules illustrated in the various embodiments herein may be executable control units. The controllers may include a microprocessor, a microcontroller, a digital signal processor, a processor card (including one or more microprocessors or controllers), or other control or computing devices. The storage devices referred to in this discussion may include one or more machine-readable storage media for storing data and instructions. The storage media may include different forms of memory including semiconductor memory devices such as dynamic or static random access memories (DRAMs or SRAMs), erasable and programmable read-only memories (EPROMs), electrically erasable and programmable read-only memories (EEPROMs) and flash memories; magnetic disks such as fixed, floppy, removable disks; other magnetic media including tape; and optical media such as compact disks (CDs) or digital video disks (DVDs). Instructions that make up the various software layers, routines, or modules in the various systems may be stored in respective storage devices. The instructions when executed by the controllers <b>210</b>, <b>250</b> cause the corresponding system to perform programmed acts.
0040The particular embodiments disclosed above are illustrative only, as the invention may be modified and practiced in different but equivalent manners apparent to those skilled in the art having the benefit of the teachings herein. Furthermore, no limitations are intended to the details of construction or design herein shown, other than as described in the claims below. Consequently, the method, system and portions thereof and of the described method and system may be implemented in different locations, such as the wireless unit, the base station, a base station controller and/or mobile switching center. Moreover, processing circuitry required to implement and use the described system may be implemented in application specific integrated circuits, software-driven processing circuitry, firmware, programmable logic devices, hardware, discrete components or arrangements of the above components as would be understood by one of ordinary skill in the art with the benefit of this disclosure. It is therefore evident that the particular embodiments disclosed above may be altered or modified and all such variations are considered within the scope and spirit of the invention. Accordingly, the protection sought herein is as set forth in the claims below.
Contents4
5 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2009080396A1 | Cited by | United States of America | Pre-grant |
| WO2010127494A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US9198006B2 | Cited by | United States of America | Applicant |
| US2011116449A1 | Cited by | United States of America | Pre-grant |
| US8457044B2 | Cited by | United States of America | Search report |
| US2006285601A1 | Cites | United States of America | Pre-grant |
| US2007014272A1 | Cites | United States of America | Pre-grant |
| US2007274288A1 | Cites | United States of America | Pre-grant |
| US2008013485A1 | Cites | United States of America | Pre-grant |
| US5778318A | Cites | United States of America | Pre-grant |
| US5933418A | Cites | United States of America | Pre-grant |
| US6888805B2 | Cites | United States of America | Pre-grant |
2 priority claims, no other members on record
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 42335406 | United States of America | A | |
| US20060423354 | – | – | – |
87 transactions on the USPTO file
Allowed after 3 non-final rejections, 3 final rejections and 3 RCEs.
- Non-final rejections
- 3
- Final rejections
- 3
- RCEs
- 3
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Examiner Interview Summary (PTOL - 413)MEXIN | MEXIN | |
| Examiner Interview Summary Record (PTOL - 413)EXIN | EXIN | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Examiner Interview Summary (PTOL - 413)MEXIN | MEXIN | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Examiner Interview Summary Record (PTOL - 413)EXIN | EXIN | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Mail Notice of Informal or Non-Responsive AmendmentNINA | NINA | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Informal or Non-Responsive Amendment after Examiner ActionA.I. | A.I. | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Sent to Classification ContractorPGPC | PGPC | |
| Application Is Now CompleteCOMP | COMP | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Cleared by L&R (LARS)L128 | L128 | |
| Referred to Level 2 (LARS) by OIPE CSRL198 | L198 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
15 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication
- 20070286148
- Publication, DOCDB
- 2007286148
- Publication, EPODOC
- US2007286148
- Application
- 11423354
- Application, DOCDB
- 42335406
- Application, EPODOC
- US20060423354
Titles
- English
- METHOD FOR INCREASING SYNCHRONOUS CONTROL CHANNEL CAPACITY IN A WIRELESS SYSTEM
Patent term adjustment
- A delay
- +698 daysthe office missed an examination deadline
- B delay
- +153 dayspendency past three years
- Applicant delay
- −112 days
- Net adjustment
- 739 days
Classification
- CPC, 3
- H04W72/1273
- H04B7/212
- H04B7/204
- IPC, 2
- H04B7 212
- H04W72 12
- USPC, 1
- 370345000