# US 8,542,641 B1 · Quick reassignment of invalid forward traffic channels > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,542,641 B1 - Document ID: US8542641B1 - Status: Granted - Kind: B1 - Application number: 12/880,368 - Filed: 2010-09-13 - Granted: 2013-09-24 - Earliest claimed: 2010-09-13 - Assignees: Sprint Spectrum L.P. - Applicants: Sachin R Vargantwar - Inventors: Sachin R Vargantwar - Web page: https://patentgrep.com/patent/US8542641B1 ## CPC - H04W 76/18: Management of setup rejection or failure - H04W 76/36: for reassigning the resources associated with the released connections - H04W 76/38: triggered by timers - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Disclosed herein are methods and systems that may, among other possible benefits, help an access network to more quickly re-assign a forward traffic channel. An exemplary method involves an access network: (i) making a determination that a forward traffic channel is invalid, wherein the forward traffic channel is initially assigned to a first access terminal; and (ii) in response to the determination that the forward traffic channel is invalid: (a) after sending a first configuration message indicating that the forward traffic channel is invalid, waiting for at least a predetermined wait period before sending a second configuration message indicating that the forward traffic channel is valid; and (b) before the predetermined wait period has ended, making the forward traffic channel available for re-assignment to a second access terminal. ## Claims ### Claim 1 A method comprising: an access network making a determination that a forward traffic channel is invalid, wherein the forward traffic channel is initially assigned to a first access terminal; and in response to the determination that the forward traffic channel is invalid, the access network: (a) sending a first configuration message indicating that the forward traffic channel is invalid; (b) after sending the first configuration message that indicates the forward traffic channel is invalid, waiting for at least a predetermined wait period before sending a second configuration message indicating that the forward traffic channel is valid, wherein the predetermined wait period comprises a duration of a drop-call timer of the first access terminal; and (c) before the predetermined wait period has ended, making the forward traffic channel available for re-assignment to a second access terminal. ### Claim 2 (depends on 1) The method of claim 1, wherein the first configuration message is a QuickConfig message. ### Claim 3 (depends on 1) The method of claim 1, further comprising, while waiting for the predetermined period of time to elapse, the access network sending one or more QuickConfig messages that each indicate that the forward traffic channel is invalid. ### Claim 4 (depends on 3) The method of claim 3, wherein each QuickConfig message that indicates that the forward traffic channel is invalid includes a validity bit associated with the forward traffic channel, wherein the validity bit is set to indicate that the forward traffic channel is invalid. ### Claim 5 (depends on 3) The method of claim 3, wherein each QuickConfig message that indicates that the forward traffic channel is invalid comprises a list of valid forward traffic channels, and wherein an absence of the forward traffic channel in the list indicates that the forward traffic channel is invalid. ### Claim 6 (depends on 1) The method of claim 1, wherein making the forward traffic channel available for re-assignment to a second access terminal comprises, after determining that the forward traffic channel is invalid, immediately adding the forward traffic channel to a list of available forward traffic channels that are available to be assigned to the second access terminal. ### Claim 7 (depends on 6) The method of claim 6, further comprising, after adding the forward traffic channel to the list of available forward traffic channels and during the predetermined period of time, sending one or more QuickConfig messages indicating that the forward traffic channel is invalid. ### Claim 8 (depends on 1) The method of claim 1, further comprising, before the predetermined period of time has elapsed, re-assigning the forward traffic channel to a second access terminal. ### Claim 9 (depends on 8) The method of claim 8, further comprising, during the predetermined period of time, including after the forward traffic channel is re-assigned to the second access terminal, periodically sending QuickConfig messages indicating that the forward traffic channel is invalid. ### Claim 10 (depends on 1) The method of claim 1, wherein waiting for at least the predetermined period of time to elapse before sending a QuickConfig message indicating that the forward traffic channel is valid comprises: starting a forward-traffic-channel validity timer having a predetermined duration; and after the duration of the forward-traffic-channel validity timer; if the forward traffic channel is valid, then sending a QuickConfig message indicating that the forward traffic channel is valid; and if the forward traffic channel is invalid, then sending a QuickConfig message indicating that the forward traffic channel is invalid. ### Claim 11 (depends on 1) The method of claim 1, further comprising performing the method in response to a determination that traffic-channel usage is above a threshold usage level. ### Claim 12 A method comprising: an access terminal receiving a channel assignment message from an access network, wherein the channel assignment message identifies a forward traffic channel that is assigned to the access terminal; and responsive to receipt of the channel assignment message, the access terminal ignoring validity indications for the assigned forward traffic channel in any QuickConfig messages received during a predetermined ignore period. ### Claim 13 (depends on 12) The method of claim 12, wherein the channel assignment message identifies the forward traffic channel that is assigned to the access terminal with a medium access control identifier (MAC-ID) that is associated with the forward traffic channel and assigned to the access terminal. ### Claim 14 (depends on 12) The method of claim 12, further comprising, after the predetermined ignore period has ended, the access terminal monitoring validity indications for the assigned forward traffic channel in QuickConfig messages received from the access network. ### Claim 15 An access-network component comprising: a non-transitory tangible computer-readable medium; program instructions stored on the non-transitory tangible computer-readable medium and executable by at least one processor to: (i) determine that a forward traffic channel in a given coverage area of an access network is invalid, wherein the forward traffic channel is initially assigned to a first access terminal; and (ii) in response to the determination that the forward traffic channel is invalid: (a) send a first configuration message indicating that the forward traffic channel is invalid, (b) after sending the first configuration message that indicates the forward traffic channel is invalid, wait for at least a predetermined wait period before sending a second configuration message indicating that the forward traffic channel is valid, wherein the predetermined wait period comprises a duration of a drop-call timer of the first access terminal, and (c) before the predetermined wait period has ended, make the forward traffic channel available for re-assignment to a second access terminal. ### Claim 16 (depends on 15) The access-network component of claim 15, wherein the first configuration message is a QuickConfig message. ### Claim 17 (depends on 15) The access-network component of claim 15, further comprising program instructions stored on the non-transitory tangible computer-readable medium and executable by at least one processor to, during the wait period, send one or more QuickConfig messages that each indicate that the forward traffic channel is invalid. ### Claim 18 (depends on 15) The access-network component of claim 15, further comprising program instructions stored on the non-transitory tangible computer-readable medium and executable by at least one processor to, before the wait period has ended, re-assign the forward traffic channel to a second access terminal. ### Claim 19 (depends on 15) The access-network component of claim 15, wherein the program instructions stored on the non-transitory tangible computer-readable medium and executable by at least one processor to make the forward traffic channel available for re-assignment comprise: program instructions stored on the non-transitory tangible computer-readable medium and executable by at least one processor to, upon a determination that the forward traffic channel is invalid, update an entry in a forward-traffic-channel availability database to indicate that the forward traffic channel is available to be assigned to access terminals. ### Claim 20 (depends on 15) The access-network component of claim 15, further comprising program instructions stored on the non-transitory tangible computer-readable medium and executable by at least one processor to: in response to the determination that the forward traffic channel is invalid, start a wait timer having a duration equal to the predetermined wait period; while the wait timer is running, send one or more QuickConfig messages, wherein each QuickConfig message comprises an indication that the forward traffic channel is invalid; when the wait timer expires, determine if the forward traffic channel is re-assigned to another access terminal; and if the forward traffic channel is re-assigned to another access terminal, then send a QuickConfig message comprising an indication that the forward traffic channel is valid. ### Claim 21 (depends on 15) The access-network component of claim 15, further comprising program instructions stored on the non-transitory tangible computer-readable medium and executable by at least one processor to: make a determination that traffic-channel usage is above a threshold usage level; and perform (i)-(ii) in response to the determination that traffic-channel usage is above the threshold usage level.