Method and System for Handling Congestion in a Communications System
Abstract
An apparatus for managing contention in a communications system, the apparatus comprising a processor and a non-transitory computer readable storage medium storing programming for execution by the processor. The programming may include instructions to receive a ranging code from a device in a ranging channel, the ranging code corresponding to a current ranging attempt. The programming may further include instructions to broadcast a message acknowledging reception of the ranging code. The programming may further include instructions to receive a ranging request message from the device, the ranging request message comprising a ranging retries parameter that specifies a number of ranging retries that the device performed during the current ranging attempt.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method for operating a base station (BS) in a network, the method comprising:
receiving, by the BS, a ranging request (RNG-REQ) message from a mobile-to-mobile (M2M) device in a ranging channel of the network, wherein the RNG-REQ message comprises a ranging retries parameter specifying a number of ranging retries that the M2M device performed during a current ranging attempt.
2 . The method of claim 1 , wherein the ranging retries parameter comprises a type-length-value (TLV) message comprising a two bit value field that is set to 00 to indicate that the current ranging process was successful on a first attempt, to 01 to indicate that the current ranging process was successful on a second attempt, to 10 to indicate that the current ranging process was successful on a third attempt, and to 11 to indicate that the current ranging process was successful on a fourth attempt.
3 . The method of claim 1 , wherein the network is a legacy Worldwide Interoperability for Microwave Access (WiMAX) network compliant with Institute of Electrical and Electronics Engineers (IEEE) 802.16.
4 . The method of claim 1 , wherein the ranging retries parameter specifies that the M2M device attempted three or more ranging retries during the current ranging attempt.
5 . The method of claim 4 , wherein the ranging retries parameter specifies that the M2M device attempted three ranging retries during the current ranging attempt.
6 . The method of claim 4 , wherein the ranging retries parameter specifies that the M2M device attempted more than three ranging retries during the current ranging attempt.
7 . The method of claim 1 , wherein the contention indicator indicates a first percentage of contending devices that succeeded on a first ranging code transmission attempt.
8 . The method of claim 7 , wherein the contention indicator indicates a second percentage of contending devices that succeeded on a second ranging code transmission attempt
9 . The method of claim 7 , wherein the contention indicator indicates a third percentage of contending devices that succeeded on a third ranging code transmission attempt.
10 . The method of claim 7 , wherein the contention indicator indicates a forth percentage of contending devices that succeeded after a third ranging code transmission attempt.
11 . The method of claim 1 , wherein the contention indicator indicates each of a first percentage of contending devices that succeeded on a first ranging code transmission attempt, a second percentage of contending devices that succeeded on a second ranging code transmission attempt, a third percentage of contending devices that succeeded on a third ranging code transmission attempt, and a forth percentage of contending devices that succeeded after the third ranging code transmission attempt.
12 . A method for operating a base station (BS) in a network, the method comprising:
receiving, by the BS, an AAI ranging request (AAI-RNG-REQ) message from a mobile-to-mobile (M2M) device in a ranging channel of the network, wherein the AAI-RNG-REQ message comprises a retrials field that specifies a number of failed trials in a current ranging process of the M2M device.
13 . The method of claim 12 , wherein the retrials field comprises a two bit value that is set to 00 to indicate that the current ranging process was successful on a first attempt, to 01 to indicate that the current ranging process was successful on a second attempt, to 10 to indicate that the current ranging process was successful on a third attempt, and to 11 to indicate that the current ranging process was successful on a fourth attempt.
14 . The method of claim 12 , wherein the network is a Worldwide Interoperability for Microwave Access (WiMAX) Advanced network compliant with Institute of Electrical and Electronics Engineers (IEEE) 802.16m.
15 . The method of claim 12 , wherein the retrials field specifies that the M2M device had two or more failed ranging retries during the current ranging process.
16 . The method of claim 15 , wherein the retrials field specifies that the M2M device had two failed ranging retries during the current ranging process.
17 . The method of claim 15 , the retrials field specifies that the M2M device had more than failed ranging retries during the current ranging process.
18 . The method of claim 12 , wherein the network is a legacy Worldwide Interoperability for Microwave Access (WiMAX) network compliant with Institute of Electrical and Electronics Engineers (IEEE) 802.16.
19 . A method comprising:
receiving a ranging request message from a device, wherein the ranging request message comprises a ranging retries parameter specifying a number of ranging retries that the device performed during a current ranging attempt, and wherein the ranging retires parameter species a first value to indicate that a first ranging attempt was successful, a second value to indicate that a second ranging attempt was successful, a third value to indicate that a third ranging attempt was successful, and a fourth value to indicate that a fourth or later ranging attempt was successful.
20 . The method of claim 19 , wherein the device is a mobile-to-mobile (M2M) device.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.