Handling of 5GSM congestion timers
In 5GS, Single-Network Slice Selection Assistance Information (S-NSSAI) based backoff (BO) timers (T3584/T3585) can be applied to either the registered PLMN or all the PLMNs based on a 5GSM congestion re-attempt indicator. For a specific PDU session, the corresponding BO timer applied to the registered PLMN and the BO timer applied to all PLMN can be both running concurrently. It is proposed for a UE to stop both the BO timer applied to all the PLMNs and the BO timer applied to the registered PLMN, if running, in all the following scenarios: 1) Receiving a PDU session release command without a BO timer, 2) Receiving a PDU session release command with 5GSM cause #39, 3) Receiving a PDU session modification command, 4) Receiving a 5GSM message with a 5GSM congestion control BO timer value, and 5) Receiving a PDU session authentication command.
1. A method, comprising:
receiving a 5G session management (5GSM) message by a user equipment (UE) in a mobile communication network, wherein the UE is registered to a public land mobile network (PLMN), wherein the 5GSM message comprises a 5GSM congestion re-attempt indicator, and wherein the 5GSM congestion re-attempt indicator indicates a new backoff (BO) timer applied to all PLMN or the registered PLMN;
determining whether a BO timer is running, wherein the running BO timer is applied for all PLMN or applied for the registered PLMN;
stopping the running BO timer in response to the 5GSM message; and
starting one or more new BO timers after the running BO timer is stopped, in accordance with the 5GSM message where the one or more new BO timers are provided by the network, and wherein each of the one or more new BO timers and the running BO timer corresponds to a different PLMN type.
2. The method of claim 1 , wherein the running BO timer and the new BO timer are associated with a Single-Network Slice Selection Assistance Information (S-NSSAI), or associated with the same S-NSSAI and data network name (DNN) combination.
3. The method of claim 1 , wherein the UE stops the running BO timer when the 5GSM message does not comprise a 5GSM congestion re-attempt indicator.
4. A User Equipment (UE), comprising:
a receiver that receives a 5G session management (5GSM) message in a mobile communication network, wherein the UE is registered to a public land mobile network (PLMN), wherein the 5GSM message comprises a 5GSM congestion re-attempt indicator, and wherein the 5GSM congestion re-attempt indicator indicates a new backoff (BO) timer applied to all PLMN or the registered PLMN;
a congestion control circuit that determines whether a backoff (BO) timer is running, wherein the running BO timer is applied for all PLMN or applied for the registered PLMN, wherein
the congestion control circuit stops the running BO timer in response to the 5GSM message; and
one or more new BO timers that are started after the running BO timer is stopped, in accordance with the 5GSM message where the one or more new BO timer is are provided by the network, and wherein each of the one or more new BO timers and the running BO timer corresponds to a different PLMN type.
5. The UE of claim 4 , wherein the running BO timer and the new BO timer are associated with a Single—Network Slice Selection Assistance Information (S-NSSAI), or associated with the same S-NSSAI and data network name (DNN) combination.
6. The UE of claim 4 , wherein the UE stops the running BO timer when the 5GSM message does not comprise a 5GSM congestion re-attempt indicator.
7. A method, comprising:
receiving a first 5G session management (5GSM) message by a user equipment (UE) in a mobile communication network, wherein the UE is registered to a first public land mobile network (PLMN), wherein the first 5GSM message comprises a 5GSM congestion re-attempt indicator, and wherein the 5GSM congestion re-attempt indicator indicates a new backoff (BO) timer applied to all PLMN or the registered PLMN;
starting a first BO timer based on a first BO timer value carried in the first 5GSM message, wherein the first BO timer is applied fora first PLMN type;
receiving a second 5GSM message by the UE and in response stops the first BO timer; and
starting a new BO timer based on a second BO timer value carried in the second 5GSM message, wherein the new BO timer is applied to a second PLMN type, and wherein the first PLMN type and the second PLMN type are different, and wherein the second 5GSM messages carries a 5GSM congestion re-attempt indicator that indicates the second PLMN type.
8. The method of claim 7 , wherein the second 5GSM message belongs to one of a PDU session release command, a PDU session modification reject, and a PDU session establishment reject.
9. The method of claim 7 , wherein the second 5GSM message does not comprise a 5GSM congestion re-attempt indicator.
10. The method of claim 7 , wherein the first PLMN type is ALL-PLMN and the second PLMN type is Registered-PLMN, or the first PLMN type is Registered-PLMN and the second PLMN type is ALL-PLMN.
11. The method of claim 7 , wherein the UE is registered to a second PLMN when the UE receives the second 5GSM message.