Coordinated inactivity timer information element (IE) for dual connectivity
Coordinated inactivity timer information element (IE) for dual connectivity. A Primary Node and a Secondary Node are established in a dual connectivity (DC) configuration. A Primary Node includes an Inactivity Timer IE that is communicated to the Secondary Node as part of Secondary Node addition process in Addition Request message. The Primary Node periodically evaluates resource congestion and when resource congestion occurs at the Primary Node. The Primary Node sends a New Inactivity Timer Value to a new incoming DC user in an Addition Request message and to existing DC users in a Modification Request message. Secondary Node detects the user data inactivity based on the inactivity timer received from Primary Node and indicates the user data inactivity to Primary Node. Primary Node decides either to release the UE or to move the UE to an inactive state based on the notification from Secondary Node.
1 . A method for providing coordinated inactivity timer information for dual connectivity, comprising:
establishing dual connectivity of User Equipment (UE) with a Primary Node and a Secondary Node;
determining resource congestion is occurring at the Primary Node;
sending, from the Primary Node to the Secondary Node, a new value of an inactivity timer for the UE of the Primary Node;
detecting, by the Secondary Node, user data inactivity based on the new value of the inactivity timer received from the Primary Node;
indicating, by the Secondary Node, the user data inactivity to the Primary Node; and
deciding, by the Primary Node, to release the UE or to move the UE to an inactive state based on the Secondary Node indicating the user data inactivity to the Primary Node;
wherein the sending, from the Primary Node to the Secondary Node, the new value of the inactivity timer is in response to the determining the resource congestion is occurring at the Primary Node, and wherein the new value of the inactivity timer is sent from the Primary Node to the Secondary Node over an interface setup between the Primary Node and the Secondary Node without being relayed through the UE.
2 . The method of claim 1 , wherein the establishing the dual connectivity of the UE with the Primary Node and the Secondary Node includes establishing one of:
an Evolved-Universal Terrestrial Radio Access (E-UTRA) New Radio (NR)-Dual Connectivity (EN-DC) configuration using a Primary evolved NodeB (eNB) and a Secondary next generation NodeB (gNB);
an E-UTRA Dual Connectivity (EUTRA-DC) configuration using the Primary eNB and a Secondary eNB;
a New Radio Dual Connectivity (NR-DC) configuration using a Primary gNB and the Secondary gNB; or
a NR-E-UTRA Dual Connectivity (NE-DC) configuration using the Primary gNB and a Secondary next generation evolved NodeB (ng-eNB).
3 . The method of claim 1 , wherein the releasing the UE or the moving the UE to the inactive state is based on adjusting the inactivity timer in the Secondary Node according to the new value of the Primary Node being provided to the Secondary Node.
4 . The method of claim 1 , wherein the sending, to the Secondary Node, the new value of the inactivity timer for the UE of the Primary Node includes sending the new value of the inactivity timer for the UE of the Primary Node through an interface that includes a private message interface for EN-DC, EUTRA-DC, NR-DC, or NE-DC, an X2 interface for EUTRA-DC or EN-DC, or an Xn interface for NR-DC or NE-DC.
5 . The method of claim 1 , wherein the sending, to the Secondary Node, the value of the inactivity timer for the UE of the Primary Node includes sending the Secondary Node one or more of:
an SGNB ADDITION REQUEST message having the new value of the inactivity timer of the Primary Node or an SGNB MODIFICATION REQUEST message having the new value of the inactivity timer of the Primary Node on an X2 interface between the Primary Node and the Secondary Node, wherein the Primary Node is a first eNB and the Secondary Node is a first gNB;
an S-Node Addition Request message having the new value of the inactivity timer of the Primary Node or an S-Node Modification Request message having the new value of the inactivity timer of the Primary Node on an Xn interface between the Primary Node and the Secondary Node, wherein the Primary Node is a second gNB and the Secondary Node is one of the first gNB or a ng-eNB; or
an SENB Addition Request message having the new value of the inactivity timer of the Primary Node or an SENB Modification Request message having the new value of the inactivity timer of the Primary Node on the X2 interface between the Primary Node and the Secondary Node, wherein the Primary Node is the first eNB and the Secondary Node is a second eNB.
6 . The method of claim 1 , wherein determining the resource congestion is occurring at the Primary Node includes determining the resource congestion at the Primary Node based on one or more of a number of RRC connected users, UE resource congestion, or signaling load in the Primary Node.
7 . The method of claim 1 , wherein the sending, to the Secondary Node, the new value of the inactivity timer for the UE of the Primary Node includes sending an inactivity timer Information Element (IE) of the Primary Node to existing users, sending the inactivity timer IE to the existing users based on a Subscriber Profile Identifier (SPID), sending the inactivity timer IE to the existing users belonging to a particular secondary node, or sending the inactivity timer IE in a Modification Request message initiated based on a non-inactivity purpose.
8 . A node in a dual connectivity mode, configured to:
establish dual connectivity of User Equipment (UE) with a Primary Node and a Secondary Node;
determine resource congestion is occurring at the Primary Node;
send, from the Primary Node to the Secondary Node, a new value of an inactivity timer for the UE of the Primary Node;
detect, by the Secondary Node, user data inactivity based on the new value of the inactivity timer received from Primary Node;
indicate, by the Secondary Node, the user data inactivity to the Primary Node; and
decide, by the Primary Node, to release the UE or to move the UE to an inactive state based on the Secondary Node indicating the user data inactivity to the Primary Node;
wherein the sending, from the Primary Node to the Secondary Node, the new value of the inactivity timer is in response to the determining the resource congestion is occurring at the Primary Node, and wherein the new value of the inactivity timer is sent from the Primary Node to the Secondary Node over an interface setup between the Primary Node and the Secondary Node without being relayed through the UE.
9 . The node of claim 8 , configured to establish the dual connectivity of the UE with the Primary Node and the Secondary Node by establishing one of:
an Evolved-Universal Terrestrial Radio Access (E-UTRA) New Radio (NR)-Dual Connectivity (EN-DC) configuration using a Primary evolved NodeB (eNB) and a Secondary next generation NodeB (gNB);
an E-UTRA Dual Connectivity (EUTRA-DC) configuration using the Primary eNB and a Secondary eNB;
a New Radio Dual Connectivity (NR-DC) configuration using a Primary gNB and the Secondary gNB; or
a NR-E-UTRA Dual Connectivity (NE-DC) configuration using the Primary gNB and a Secondary next generation evolved NodeB (ng-eNB).
10 . The node of claim 8 , configured to release the UE or to move the UE to the inactive state based on adjusting the inactivity timer in the Secondary Node according to the new value of the Primary Node being provided to the Secondary Node.
11 . The node of claim 8 , configured to send, to the Secondary Node, the new value of the inactivity timer for the UE of the Primary Node by sending the new value of the inactivity timer for the UE of the Primary Node through an interface that includes a private message interface for EN-DC, EUTRA-DC, NR-DC, or NE-DC, an X2 interface for EUTRA-DC or EN-DC, or an Xn interface for NR-DC or NE-DC.
12 . The node of claim 8 , configured to send, to the Secondary Node, the new value of the inactivity timer for the UE of the Primary Node by sending the Secondary Node one or more of:
an SGNB Addition Request message having the new value of the inactivity timer of the Primary Node or an SGNB Modification Request message having the new value of the inactivity timer of the Primary Node on an X2 interface between the Primary Node and the Secondary Node, wherein the Primary Node is a first eNB and the Secondary Node is a first gNB;
an S-Node Addition Request message having the new value of the inactivity timer of the Primary Node or an S-Node Modification Request message having the new value of the inactivity timer of the Primary Node on an Xn interface between the Primary Node and the Secondary Node, wherein the Primary Node is a second gNB and the Secondary Node is one of the first gNB or a ng-eNB; or
an SENB Addition Request message having the new value of the inactivity timer of the Primary Node or an SENB Modification Request message having the new value of the inactivity timer of the Primary Node on the X2 interface between the Primary Node and the Secondary Node, wherein the Primary Node is the first eNB and the Secondary Node is a second eNB.
13 . The node of claim 8 , configured to determine the resource congestion is occurring at the Primary Node by determining the resource congestion at the Primary Node based on one or more of a number of RRC connected users, UE resource congestion, or signaling load in the Primary Node.
14 . The node of claim 8 , configured to send, to the Secondary Node, the new value of the inactivity timer for the UE of the Primary Node by sending inactivity timer Information Element (IE) of the Primary Node to existing users, the inactivity timer IE to the existing users based on a Subscriber Profile Identifier (SPID), the inactivity timer IE to the existing users belonging to a particular secondary node, or the inactivity timer IE in a Modification Request message initiated based on a non-inactivity purpose.
15 . A non-transitory computer-readable media having computer-readable instructions stored thereon, which when executed causes operations to be performed for:
establishing dual connectivity of User Equipment (UE) with a Primary Node and a Secondary Node;
determining resource congestion is occurring at the Primary Node;
sending, from the Primary Node to the Secondary Node, a new value of an inactivity timer for the UE of the Primary Node;
detecting, by the Secondary Node, user data inactivity based on the new value of the inactivity timer received from Primary Node;
indicating, by the Secondary Node, the user data inactivity to the Primary Node; and
deciding, by the Primary Node, to release the UE or to move the UE to an inactive state based on the Secondary Node indicating the user data inactivity to the Primary Node;
wherein the sending, from the Primary Node to the Secondary Node, the new value of the inactivity timer is in response to the determining the resource congestion is occurring at the Primary Node, and wherein the new value of the inactivity timer is sent from the Primary Node to the Secondary Node over an interface setup between the Primary Node and the Secondary Node without being relayed through the UE.
16 . The non-transitory computer-readable media of claim 15 , wherein the establishing the dual connectivity of the UE with the Primary Node and the Secondary Node includes establishing one of:
an Evolved-Universal Terrestrial Radio Access (E-UTRA) New Radio (NR)-Dual Connectivity (EN-DC) configuration using a Primary evolved NodeB (eNB) and a Secondary next generation NodeB (gNB);
an E-UTRA Dual Connectivity (EUTRA-DC) configuration using the Primary eNB and a Secondary eNB;
a New Radio Dual Connectivity (NR-DC) configuration using a Primary gNB and the Secondary gNB; or
a NR-E-UTRA Dual Connectivity (NE-DC) configuration using the Primary gNB and a Secondary next generation evolved NodeB (ng-eNB).
17 . The non-transitory computer-readable media of claim 15 , wherein the releasing the UE or the moving the UE to the inactive state is based on adjusting the inactivity timer in the Secondary Node according to the new value of the Primary Node being provided to the Secondary Node.
18 . The non-transitory computer-readable media of claim 15 , wherein the sending, to the Secondary Node, the new value of the inactivity timer for the UE of the Primary Node includes sending the new value of the inactivity timer for the UE of the Primary Node through an interface that includes a private message interface for EN-DC, EUTRA-DC, NR-DC, or NE-DC, an X2 interface for EUTRA-DC or EN-DC, or an Xn interface for NR-DC or NE-DC.
19 . The non-transitory computer-readable media of claim 15 , wherein the sending, to the Secondary Node, the new value of the inactivity timer for the UE of the Primary Node includes sending the Secondary Node one or more of:
an SGNB Addition Request message having the new value of the inactivity timer of the Primary Node or an SGNB Modification Request message having the new value of the inactivity timer of the Primary Node on an X2 interface between the Primary Node and the Secondary Node, wherein the Primary Node is a first eNB and the Secondary Node is a first gNB;
an S-Node Addition Request message having the new value of the inactivity timer of the Primary Node or an S-Node Modification Request message having the new value of the inactivity timer of the Primary Node on an Xn interface between the Primary Node and the Secondary Node, wherein the Primary Node is a second gNB and the Secondary Node is one of the first gNB or a ng-eNB; or
an SENB Addition Request message having the new value of the inactivity timer of the Primary Node or an SENB Modification Request message having the new value of the inactivity timer of the Primary Node on the X2 interface between the Primary Node and the Secondary Node, wherein the Primary Node is the first eNB and the Secondary Node is a second eNB.
20 . The non-transitory computer-readable media of claim 15 , wherein the sending, to the Secondary Node, the new value of the inactivity timer for the UE of the Primary Node includes sending an inactivity timer Information Element (IE) of the Primary Node to existing users, sending the inactivity timer IE to the existing users based on a Subscriber Profile Identifier (SPID), sending the inactivity timer IE to the existing users belonging to a particular secondary node, or sending the inactivity timer IE in a Modification Request message initiated based on a non-inactivity purpose.