Techniques and configurations associated with user equipment-initiated congestion reporting
View Patent ↗Embodiments of the present disclosure describe systems and methods for user equipment (UE)-initiated reporting of congestion information. Various embodiments may include systems and methods for reporting congestion information to an evolved node B (eNB) by UEs. In embodiments, the congestion information may be utilized in managing access requests made by the UEs. Other embodiments may be described and/or claimed.
1. A user equipment (UE) comprising:
transceiver circuitry to:
receive, from an evolved node B (eNB), a system information block (SIB) having a Boolean reporting parameter that indicates the eNB supports UE-initiated reporting of congestion information; and
send a random access channel (RACH) transmission to the eNB in an attempt to connect with the eNB; and
logic circuitry coupled with the transceiver circuitry, the logic circuitry to:
monitor RACH transmissions from the UE to the eNB to detect one or more congestion events associated with attempts by the UE to connect with the eNB; and
initiate, based on receipt of the Boolean reporting parameter and detection of at least one of the one or more congestion events, reporting of congestion information to the eNB via the transceiver circuitry upon a successful connection with the eNB,
wherein the SIB further includes one or more additional parameters that define one or more congestion events for individual access classes of a plurality of access classes, the one or more congestion events to include a threshold number of unsuccessful connection attempts by the UE or a threshold duration of unsuccessful connection attempts by the UE.
2. The UE of claim 1 , wherein the congestion information includes one or more of:
a Boolean indicator that at least one of the one or more congestion events was detected;
an access class identifier that identifies an access class to which the UE belongs;
a numerical indicator indicating a number of consecutive unsuccessful attempts to connect with the eNB; or
a time indicator indicating a duration of consecutive unsuccessful attempts to connect with the eNB.
3. The UE of claim 2 , wherein the transceiver circuitry is further to report the congestion information via an uplink transmission including:
a medium access control (MAC) header that includes the congestion information; or
a MAC control element that includes the congestion information, wherein the MAC control element is indicated by a logical channel identifier (LCID).
4. The UE of claim 2 , wherein the transceiver circuitry is further to report the congestion information via a dedicated radio resource control (RRC) message.
5. An evolved node B (eNB) comprising:
transceiver circuitry to:
send, by a system information block (SIB), a reporting-support transmission to a plurality of user equipments (UEs), wherein the reporting-support transmission includes a Boolean reporting parameter that indicates that the eNB supports UE-initiated reporting of congestion information, wherein the SIB further includes one or more additional parameters that define one or more congestion events for individual access classes of a plurality of access classes, the one or more congestion events to include a threshold number of unsuccessful connection attempts or a threshold duration of unsuccessful connection attempts; and
receive, from each of one or more UEs of the plurality of UEs, congestion information, wherein the congestion information is indicative of an occurrence of at least one of the one or more congestion events at the one or more UEs; and
logic circuitry coupled with the transceiver circuitry, the logic circuitry configured to manage random access requests received from the plurality of UEs based on the congestion information received from the one or more UEs.
6. The eNB of claim 5 , wherein the congestion information includes one or more of:
a Boolean indicator that at least one of the one or more congestion events was detected;
an access class identifier that identifies an access class to which a respective UE belongs;
a numerical indicator indicating a number of consecutive unsuccessful attempts to connect with the eNB; or
a time indicator indicating a duration of consecutive unsuccessful attempts to connect with the eNB.
7. The eNB of claim 6 , wherein the transceiver circuitry is further to receive the congestion information via an uplink transmission including:
a medium access control (MAC) header that includes the congestion information; or
a MAC control element that includes the congestion information, wherein the MAC control element is indicated by a logical channel identifier (LCID).
8. The eNB of claim 6 , wherein the transceiver circuitry is further to receive the congestion information via a dedicated radio resource control (RRC) message from each of the one or more UEs.
9. The eNB of claim 5 , wherein each UE of the plurality of UEs is associated with an access class, and wherein to manage random access requests is to dynamically adjust access class barring parameters to control access requests from an individual UE of the plurality of UEs based on the access class to which the individual UE is associated.
10. A method of UE-initiated congestion reporting comprising:
sending, by an eNB, a system information block (SIB) having a reporting-support transmission to a plurality of user equipments (UEs), wherein the reporting-support transmission includes a Boolean reporting parameter that indicates that the eNB supports UE-initiated reporting of congestion information, wherein the SIB further includes one or more additional parameters that define one or more congestion events for individual access classes of a plurality of access classes, the one or more congestion events to include a threshold number of unsuccessful connection attempts or a threshold duration of unsuccessful connection attempts;
receiving, by the eNB, from each of one or more UEs of the plurality of UEs, congestion information, wherein the congestion information is indicative of an occurrence of one or more congestion events at the one or more UEs; and
managing, by the eNB, random access requests received from the plurality of UEs based on the congestion information received from the one or more UEs.
11. The method of claim 10 , wherein the congestion information includes one or more of:
a Boolean indicator that at least one of the one or more congestion events was detected;
an access class identifier that identifies an access class to which a respective UE belongs;
a numerical indicator indicating a number of consecutive unsuccessful attempts by the respective UE to connect with the eNB; or
a time indicator indicating a duration of consecutive unsuccessful attempts by the respective UE to connect with the eNB.
12. The method of claim 11 , wherein receiving the congestion information further comprises: receiving the congestion information via an uplink transmission including:
a medium access control (MAC) header that includes the congestion information; or
a MAC control element that includes the congestion information, wherein the MAC control element is indicated by a logical channel identifier (LCID).
13. The method of claim 11 , wherein receiving the congestion information further comprises: receiving the congestion information via a dedicated radio resource control (RRC) message from each of the one or more UEs.
14. One or more computer-readable non-transitory media, having instructions stored thereon, the instructions, in response to execution by an eNB, to cause the eNB to:
send, by a system information block (SIB), a reporting-support transmission to a plurality of user equipments (UEs), wherein the reporting-support transmission includes a Boolean reporting parameter that indicates that the eNB supports UE-initiated reporting of congestion information, wherein the SIB further includes one or more additional parameters that define one or more congestion events for individual access classes of a plurality of access classes, the one or more congestion events to include a threshold number of unsuccessful connection attempts or a threshold duration of unsuccessful connection attempts; and
receive, from each of one or more UEs of the plurality of UEs, congestion information, wherein the congestion information is indicative of an occurrence of one or more congestion events at the one or more UEs; and
manage random access requests received from the plurality of UEs based on the congestion information received from the one or more UEs.