Methods and systems for optimization of signaling and connection management in non-access stratum
Patent Information
- Application Number
- IN202141036382
- Authority / Receiving Office
- IN · IN
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-08-11
- Publication Date
- 2026-10-28
- Estimated Expiration
- 2041-08-11
AI Technical Summary
In wireless communication networks, particularly in non-access stratum (NAS) signaling, inefficiencies such as delayed registration, resource hogging, and lack of service recovery occur due to issues like transmission failures and UE movement during registration procedures, leading to delayed signaling and resource wastage.
Implementing methods and systems where user equipment (UE) in 5G and LTE networks initiates a connection release timer under specific conditions, such as receipt of certain messages or movement to new tracking areas, allowing for local release of signaling connections and immediate reinitiation of procedures, thereby overcoming delays and resource wastage.
This approach enhances registration and tracking area update procedures by allowing immediate reinitiation of processes, reducing delays and resource consumption, and ensuring efficient signaling management in wireless communication networks.
Abstract
Description
TECHNICAL FIELD
[0002] Embodiments disclosed herein relate to wireless communicationnetworks, and more particularly to optimization or improvement of signaling andconnection management in non-access stratum in wireless communicationnetworks.BACKGROUND
[0003] There are various scenarios in non-access stratum (NAS) signalingwhere inefficiencies may be present, such as, but not limited to, a delay inregistration of a user equipment (UE), hogging of resources like power, and lack ofservice recovery. An example of such a scenario is where a registration procedurefor a UE may not be completed because of a transmission failure of a registrationcomplete message or when the UE moves to a new tracking area identity (TAI)when the registration is in progress. As a result, any subsequent registrationprocedure may be delayed due to a connection release timer, such as T3540, startingafter the UE receives a registration accept message, and only upon expiry of theconnection release timer is the UE able to initiate signaling.SUMMARY
[0004] Accordingly, embodiments herein provide methods and systems foroptimizing or improving signaling and connection management in NAS. A methodfor completing a registration procedure in the fifth generation (5G) networkincludes transmitting, by a user equipment (UE), a registration request message tothe 5G network, the registration request message initiating a first registrationprocedure, starting, by the UE, a connection release timer in response to occurrenceof a plurality of events, the plurality of events including receiving, by the UE, a firstregistration accept message from the 5G network, the registration accept messagenot including pending slice selection assistance information, the registration requestmessage not including a pending follow-on request, the registration requestmessage does not include an uplink data status information element (IE), or theregistration request message includes the uplink data status IE and a secondregistration accept message received by the UE from the 5G network indicates thatno user plane resources of protocol data unit (PDU) sessions are to be reestablished,the registration request message does not include an allowed PDUsession status IE, the registration request message includes the allowed PDU statusIE which indicates there are no PDU sessions for which the UE has allowed the userplane resources to be re-established over access, or the allowed PDU session statusIE in the registration request message is included by the UE and a third registrationaccept message received by the UE from the 5G network does not indicate that userplane resources of PDU sessions are to be re-established, the transmitting theregistration request message is performed while the UE is in 5G mobilitymanagement (5GMM)-idle mode, first user plane resources for first PDU sessionsare not set up, and the UE is configured to perform vehicle to everything (V2X)communication without requesting resources for the V2X communication over areference point; meeting, by the UE, at least one of a plurality of conditions, theplurality of conditions including transmission failure of a registration completemessage from the UE to the 5G network, movement of the UE to a new trackingarea before the completion of the first registration procedure, and movement of theUE to a new tracking area that is not in a registered tracking area identity (TAI) list;stopping, by the UE, the connection release timer in response to the meeting the atleast one of the plurality of conditions; and performing, by the UE, a local releaseof a signaling connection in response to the meeting the at least one of the pluralityof conditions if the UE is in a connected state.
[0005] The UE may be a dual sim dual standby (DSDS) device with twosubscriber identity module application toolkits (STKs), one of the two STKs beingregistered with the 5G network; and the transmitting the registration requestmessage may transmit the registration request message via the STK registered withthe 5G network.
[0006] A method disclosed herein for completing a tracking area update(TAU) procedure in a fourth generation (LTE) network. The method includestransmitting, by a user equipment (UE), a TAU request message to the 4G network,the TAU request message initiating a first registration procedure, starting, by theUE, a connection release timer in response to occurrence of a plurality of events,the plurality of events including a TAU accept message that is received does notinclude a UE radio capability identity deletion indication information element (IE),the TAU request message does not include a signaling active flag, an active flag, ora flag indicating that the 4G network is going to maintain connection, the firstregistration procedure is initiated while the UE is in 4G mobility management(EMM)-idle mode, and one or more user plane resources for one or more radiobearers are not set up, meeting, by the UE, at least one of a plurality of conditions,the plurality of conditions including transmission failure of a TAU completemessage from the UE to the 4G network, movement of the UE to a new trackingarea before the completion of the first registration procedure, and movement of theUE to a new tracking area that is not available in a registered tracking area identity(TAI) list, stopping, by the UE, the connection release timer in response to themeeting the at least one of the plurality of conditions, performing, by the UE, a localrelease of a signaling connection in response to the meeting the at least one of theplurality of conditions if the UE is in a connected state, and initiating, by the UE,another TAU request message after establishment of a radio connection and thestopping the connection release timer.
[0007] A method disclosed herein for completing a registration procedure.The method includes transmitting, by a user equipment (UE), a service requestmessage to the 5G network, the service request message initiating a first servicerequest procedure, starting, by the UE, a connection release timer in response tooccurrence of a plurality of events, the plurality of events including receiving, bythe UE, a first service accept message from the 5G network, a service typeinformation element (IE) is not set for signaling or high priority access in the servicerequest message, the an uplink data status IE is not included in the service requestmessage, or the uplink data status IE is included in the service request message anda second service accept message received by the UE from the 5G network indicatesthat no user plane resources of a protocol data unit (PDU) session are to be reestablished,the service request message does not include an allowed PDU sessionsstatus IE, the service request message includes the allowed PDU sessions status IEwhich indicates that there are no PDU sessions for which the UE has allowed theuser plane resources to be re-established over access, or the service request messageincludes the allowed PDU sessions status IE and the service accept message doesnot indicate that user plane resources of PDU sessions are to be re-established, thetransmitting the service request message is performed while the UE is in 5Gmobility management (5GMM)-idle mode, first user plane resources for first PDUsessions have not been set up, and the UE is configured to perform vehicle toeverything (V2X) communication without requesting resources for the V2Xcommunication over a reference point, meeting, by the UE, at least one of a pluralityof conditions, the plurality of conditions including changing of a cell to a newtracking area, the new tracking area not being present in a registered tracking areaidentity (TAI) list due to a handover, and a data radio bearer not being establishedby a radio access network, stopping, by the UE, the connection release timer inresponse to the meeting the at least one of the plurality of conditions, and initiating,by the UE, signaling in response to the meeting the at least one of the plurality ofconditions.
[0008] The UE may be a dual sim dual standby (DSDS) device with twosubscriber identity module application toolkits (STKs), one of the two STKs beingregistered with the 5G network, and the transmitting the service request messagemay transmit the service request message via the STK registered with the 5Gnetwork.
[0009] A method disclosed herein for locally releasing a signalingconnection in a wireless communication network includes receiving, by a userequipment (UE), a configuration update command message from an access andmobility management function (AMF), the configuration update command messageincluding a configuration update indication information element (IE) with aregistration request due to a change in a network slice subscription, and starting, bythe UE, a connection release timer in response to occurrence of a plurality of events,the plurality of events including the configuration update command messageincluding at least one of new allowed network slice selection assistance information(NSSAI), new configured NSSAI, or a combination of the new allowed NSSAI andthe new configured NSSAI, or a network slicing indication IE that indicates achange in a network slice, and no emergency protocol data unit (PDU) sessionshaving been established irrespective of whether a plurality of user plane resourcesfor one or more PDU sessions have been set up, and locally releasing, by the UE, asignaling connection on expiry of the connection release timer.
[0010] The UE may be a dual sim dual standby (DSDS) device with twosubscriber identity module application toolkits (STKs), a first STK among the twoSTKs being registered with a fifth generation (5G) network, the starting theconnection release timer may start the connection release timer while the pluralityof user plane resources are established for the one or more PDU sessions, and themethod may further comprise establishing the plurality of user plane resources forthe one or more PDU sessions, transmitting, by the AMF, the configuration updatecommand message to the first STK, activating a second STK among the two STKto process one or more triggered services while transmitting by the AMF acommand to release the signaling connection to the first STK, failing, by the firstSTK, to process the transmitted command by the AMF to release the signalingconnection, and activating the first STK for performing the local release of thesignaling connection, by the UE, upon expiry of the connection release timer.
[0011] A method disclosed herein for performing a local release of asignaling connection upon receiving a mobility registration reject message for amobility registration procedure including transmitting, by a user equipment (UE), amobility registration request message to a network, receiving, by the UE, themobility registration reject message from the network, the mobility registrationreject message including an abnormal cause value, starting, by the UE, a first shorttimer in response to receiving the mobility registration reject message, andperforming the local release of the signaling connection upon receiving the mobilityregistration reject message or expiry of the first short timer. The method may furthercomprise incrementing a first attempt counter in response to receiving the mobilityregistration reject message, starting a second short timer in response to the firstattempt counter having a value equal to or greater than a first threshold count, andtransmitting a new mobility registration request upon expiry of the second shorttimer.
[0012] The UE may be a dual sim dual standby (DSDS) device with twosubscriber identity module application toolkits (STKs), a first STK among the twoSTKs being registered with a fifth generation (5G) network, the transmitting themobility registration request message may transmit the mobility registration requestmessage to an access and mobility management function (AMF), the receiving themobility registration reject message may receive the mobility registration rejectmessage from the AMF, and the method may further comprise incrementing a firstattempt counter in response to receiving the mobility registration reject message,and performing a local release of the signaling connection upon a value of the firstattempt counter becoming equal to or greater than a second threshold count. Themethod may further comprise starting a second short timer in response to receivingthe mobility registration reject message, activating a second STK among the twoSTKs to process one or more triggered services, and activating the first STK fortriggering the mobility registration procedure after the activating the second STKupon the second short timer being stopped or expiring, the mobility registrationprocedure being performed with release of the signaling connection of the firstSTK.
[0013] The UE may be a dual sim dual standby (DSDS) device with twosubscriber identity module application toolkits (STKs), a first STK among the twoSTKs being registered with a fourth generation (4G) network, and the method mayfurther comprise transmitting, by the UE, an attach request message or a trackingarea update (TAU) request message to a mobility management entity (MME),receiving, by the UE, an attach reject message or a TAU reject message having anabnormal cause from the MME, starting, by the UE, the first short timer in responseto receiving the attach reject message or the TAU reject message, incrementing asecond attempt counter in response to receiving the attach reject message orincrementing a third attempt counter in response to receiving the TAU rejectmessage, and releasing the signaling connection upon a value of the second attemptcounter or the third attempt counter becoming equal to or greater than a thirdthreshold count, or after expiry of the first short timer. The method may furthercomprise activating a second STK among the two STKs to process one or moretriggered services, and activating the first STK for triggering an attach procedure ora TAU procedure upon expiry of the first short timer, the attach procedure or theTAU procedure being performed with local release of the signaling connection ofthe first STK.
[0014] Accordingly, embodiments herein provide a system including a fifthgeneration (5G) network, a fourth generation (4G) network, and a user equipment(UE) configured to perform at least one of transmitting a registration requestmessage to the 5G network, receiving a registration accept message from the 5Gnetwork, transmitting a registration complete message to the 5G network,modifying the registration request message to include at least one of: a pendingfollow-on request, an uplink data status information element (IE), or an allowedprotocol data unit (PDU) session status IE, transmitting a service request messageto the 5G network, receiving a service accept message from the 5G network,transmitting an attach request message or a tracking area update (TAU) requestmessage to the 4G network, receiving an attach reject message or a TAU rejectmessage from the 4G network, modifying the service request message to include atleast one of: a service type IE, an uplink data status IE, or an allowed PDU sessionsstatus IE, receiving a configuration update command message from an access andmobility management function (AMF), or locally releasing a signaling connectionif the UE is in a connected state.
[0015] These and other aspects of embodiments herein will be betterappreciated and understood when considered in conjunction with the followingdescription and the accompanying drawings. It should be understood, however, thatthe following descriptions, while indicating embodiments and numerous specificdetails thereof, are given by way of illustration and not of limitation. Many changesand modifications may be made within the scope of embodiments herein withoutdeparting from the spirit thereof, and embodiments herein include all suchmodifications.BRIEF DESCRIPTION OF FIGURES
[0016] Embodiments herein are illustrated in the accompanying drawings,throughout which like reference letters indicate corresponding parts in the variousfigures. Embodiments herein will be better understood from the followingdescription with reference to the drawings, in which:
[0017] FIG. 1 illustrates a challenge scenario where a UE, upon atransmission failure of a registration complete message due to a TAI change, isunable to perform a registration procedure until expiry of a timer;
[0018] FIG. 2 illustrates a solution to the challenge scenario of FIG. 1 wherethe UE, upon the transmission failure of the registration complete message due tothe TAI change, is unable to perform the registration procedure, according toembodiments as disclosed herein;
[0019] FIGS. 3A and 3B illustrate a method for completing the mobilityregistration procedure in a DSDS device, upon transmission failure of theregistration complete message, according to embodiments as disclosed herein;
[0020] FIG. 4 illustrates a method for completing a TAU procedure when aconnection release timer is still running due to a previous TAU procedure,according to embodiments as disclosed herein;
[0021] FIG. 5 illustrates a challenge scenario where a UE is unable toperform a mobility registration procedure upon receiving a service accept messageand before the establishment of a data radio bearer (DRB);
[0022] FIG. 6 illustrates a solution to the challenge scenario illustrated inFIG. 5 where the UE is unable to perform the mobility registration procedurereceiving the service accept message and before the establishment of the data radiobearer (DRB), according to embodiments as disclosed herein;
[0023] FIG. 7 illustrates a method for completing the registration procedurein a DSDS device, upon receiving the service accept message, according toembodiments as disclosed herein;
[0024] FIG. 8 illustrates a challenge scenario where a UE is stuck in aconnected state and when the network has not released the signaling connection;
[0025] FIG. 9 illustrates a solution to the challenge scenario illustrated inFIG. 8 where the UE is stuck in the connected state and when the network has notreleased the signaling connection, according to embodiments as disclosed herein;
[0026] FIG. 10 illustrates a challenge scenario in a dual SIM dual standby(DSDS) device where one of the subscriber identity module application toolkits(STKs) of a UE is stuck in a connected state due to its failure of releasing thesignaling connection;
[0027] FIG. 11 illustrates a solution to the challenge scenario illustrated inFIG. 10 in the DSDS device where the STK having the 5G network of the UE is inthe connected state due to its failure to release the signaling connection, accordingto embodiments as disclosed herein;
[0028] FIGS. 12A and 12B illustrate a challenge scenario where a UE isstuck in a connected state after receiving a registration reject message having anabnormal cause value;
[0029] FIGS. 13A and 13B illustrate a solution to the challenge scenarioillustrated in FIGS. 12A and 12B where the UE is stuck in the connected state afterreceiving the registration reject message having the abnormal cause value,according to embodiments as disclosed herein;
[0030] FIG. 14 illustrates a challenge scenario in a DSDS device where aftera UE receives a registration reject message having an abnormal cause value, a STKhaving the 5G network of a UE is stuck in a connected state due to its failure torelease the signaling connection;
[0031] FIG. 15 illustrates a solution to the challenge scenario illustrated inFIG. 14 in the DSDS device where after the UE receives the first registration rejecthaving the abnormal cause value, the STK having the 5G network of the UE is stuckin the connected state due to its failure to release the signaling connection,according to embodiments as disclosed herein;
[0032] FIG. 16 illustrates a method for releasing the signaling connectionupon receiving an attach reject message or a TAU reject message in a DSDS device,according to embodiments as disclosed herein; and
[0033] FIG. 17 is a system diagram for enabling optimization orimprovement of signaling and connection management in NAS, according toembodiments as disclosed herein.DETAILED DESCRIPTIONScenario 1 Challenge: Completing a registration procedure in the 5G network upontransmission failure of the registration complete message
[0034] FIG. 1 illustrates a challenge scenario where a UE is not able toperform a registration procedure until expiry of a timer. The UE (e.g., a new radioUE (NR MM)) may transmit (e.g., via NR radio resource control (RRC) protocolvia a wireless network) a registration request message to a fifth generation (5G)network, and upon receiving a registration accept message from the 5G network(following the performance of NAS and AS security procedures), the UE may starta connection release timer, such as T3540, if the following conditions are satisfied:a. The registration accept message does not include any pendingnetwork slice subscription assistance information (NSSAI)information element (IE);b. The UE has set a follow-on request indicator to "No follow-onrequest pending" in the registration request message;c. The UE has not included an uplink (UL) data status IE in theregistration request message, or the UE has included the UL datastatus IE in the registration request message but the registrationaccept message indicates that no user plane resources of anyprotocol data unit (PDU) sessions are to be re-established;d. The UE has not included an allowed PDU session status IE, hasincluded the allowed PDU session status IE indicating that there areno PDU sessions for which the UE has allowed the user planeresources to be re-established over access (an example of this is3GPP access) in the registration request message, or the UE hasincluded the allowed PDU session status IE in the registrationrequest message but the registration accept message does notindicate that any user plane resources of any PDU sessions are to bere-established;e. The registration procedure has been initiated in 5G MobilityManagement (5GMM)-IDLE mode;f. The user plane resources for PDU sessions have not been set up;and / org. The UE is able to perform vehicle-to-everything (V2X)communication without requesting resources for V2Xcommunication over a reference point.
[0035] Upon starting the connection release timer, if there is a transmissionfailure of a registration complete message from the UE to the 5G network, whichmay trigger a mobility registration update procedure, or a change of a cell to a newtracking area before the completion of the ongoing registration procedure, the UEis supposed to perform a new or subsequent mobility registration procedure.However, as the connection release timer continues to run, the initiation of themobility registration update procedure may be affected. Handling of the connectionrelease timer is also not considered, due to which initiation of signaling may nothappen until expiry of the connection release timer or release of the signalingconnection. This may cause a time delay and resource wastage, as signaling mayonly be performed after the expiry of the connection release timer. Moreover, if theUE has moved to a different cell and / or tracking area, or if the UE encounters lowerlayer failures, the UE may not receive a message regarding release of the signalingconnection.Scenario 2 Challenge: Completing a tracking area update (TAU) procedure when aconnection release timer is running due to a previous TAU procedure
[0036] In another challenge scenario, the UE may transmit a TAU requestmessage to a fourth generation (4G) network and receive a TAU accept messagefrom the network. The UE may start a connection release timer, an example ofwhich is T3440, upon all of the following events occurring:a. The UE receives the TAU accept message without a UE radiocapability identity deletion indication IE;b. The UE has not set an "active" flag or a "signaling" flag in the TAUrequest message;c. The tracking area updating or combined tracking area updatingprocedure has been initiated in evolved packet system (EPS)mobility management (EMM)-IDLE mode; and / ord. One or more user plane resources for one or more radio bearers arenot set up.
[0037] In other challenge scenarios, the UE may start the connection releasetimer if it receives a EMM cause value, such as, but not limited to #11, #12, #13,#14, #15, #25, #31 and #35. The UE may also start the connection release timer ifthe UE receives a detach accept message and the UE has set a detach type to "IMSIdetach" in the detach request message, and one or more user plane resources forone or more radio bearers have not been set up.
[0038] In another challenge scenario, the UE may start the connectionrelease timer if the UE receives a TAU reject message indicating:a. Any of the EMM cause values, such as, but not limited to #9 or #10,and the UE has no circuit switched (CS) fallback emergency call, aCS fall back, a CS fallback call, 1xCS fallback emergency call, or1xCS fallback call pending; orb. An EMM cause value, such as, but not limited to #40, the TAUupdate message was not triggered due to receiving a paging for CSfallback or a paging for CS fallback, and the UE has no CS fallbackemergency call, CS fallback call, a CS fallback call, 1xCS fallbackemergency call, or 1xCS fallback call pending.
[0039] In another challenge scenario, the UE may start the connectionrelease timer if the UE receives a service reject message indicating an EMM causevalue, such as, but not limited to, #9, #10, or #40, as a response to the service requestmessage, a control plane service request message, or an extended service requestmessage with service type set to "packet services via S1."
[0040] In another challenge scenario, the UE may start the connectionrelease timer if the UE receives an EMM cause value, such as, but not limited to#3, #6, #7, or #8, or if it receives an authentication reject message.
[0041] In another challenge scenario, the UE may start the connectionrelease timer if the UE receives a service reject message indicating an EMM causevalue, such as, but not limited to, #39, and the UE has initiated extended servicerequest in EMM-IDLE and one or more user plane resources for one or more radiobearers have not been set up.
[0042] In another challenge scenario, the UE may start the connectionrelease timer if the UE receives a service reject message, a service accept message,an attach accept message, or a TAU accept message with control plane data backofftimer.
[0043] However, upon starting the connection release timer, if the cellchanges to a new tracking area before the completion of the ongoing TAUprocedure or if there is a transmission failure of a TAU complete message, the UEmay attempt to reinitiate the TAU procedure immediately or promptly. However,as the connection release timer is still running, the initiation of the TAU proceduremay be impacted, as the UE may not be able to initiate the TAU procedure whilethe connection release timer is running. Similarly, if the UE has moved to a newtracking area that is not in the registered TAI list, the UE may initiate the TAUrequest or a combined TAU request, however with the connection release timer stillrunning, the initiation of the TAU procedure or the combined TAU procedure maybe impacted, as the UE may not be able to initiate any uplink message transmission,except for any emergency-related signaling when the connection release timer isrunning.Scenario 3 Challenge: Completing a mobility registration procedure upon receivinga service accept message and before establishment of a data radio bearer
[0044] FIG. 5 illustrates a challenge scenario where a UE is unable toperform a mobility registration procedure upon receiving a service accept messageand before the establishment of a data radio bearer (DRB). When the UE (in theregistered state) transmits the service request message to the network for initiatinga service request, the network may accept the service request and send a serviceaccept message to the UE. One of the conditions for starting the connection releasetimer, an example of which is T3540, may be the occurrence of the followingevents:a. The UE receives the service accept message from the network;b. The UE did not set the service type IE to "signaling" or "highpriority access," the UE has not included the UL data status IE in theservice request message, or the UE has included the UL data statusIE in the service request message but the service accept messageindicates that no user plane resources of any PDU sessions are to bere-established;c. The UE has not included the allowed PDU session status IE, hasincluded the allowed PDU session status IE indicating there are noPDU sessions for which the UE has allowed the user plane resourcesto be re-established over access (an example of this access is 3GPPaccess) in the service accept message, or the UE has included theallowed PDU session status IE in the service request message butthe service accept message does not indicate that any user planeresources of any PDU sessions are to be re-establishedd. The service request procedure has been initiated in 5GMM-IDLEmode;e. The user plane resources for PDU sessions have not been set up;and / orf. The UE is able to perform V2X communication without requestingresources for the V2X communication over a PC5 reference point.
[0045] In addition to one of the above events occurring, if no DRB isestablished from the network (e.g., the radio access network (RAN)), the connectionrelease timer may be started. If the cell changes to a new tracking area that is notpresent in the registered TAI list due to handover or radio resource control (RRC)re-establishment, then a new mobility registration request may be triggered. As theconnection release timer is running, the initiation of the new mobility registrationupdate procedure may be affected, as initiating signaling is not allowed until expiryof the connection release timer or release of the signaling connection. Moreover, ifthe UE has moved to a different cell and tracking area, or if the UE is encounteringlower layer failures, the reception of release of the signaling connection or set up ofsignaling radio bearer (SRB) may not be possible. As a result, there may be a timedelay in signaling, a lack of data, and / or wastage of resources. This may causechallenges for service that may utilize quick data transmission, where the packetsmay have a smaller size.Scenario 4 Challenge: Releasing a signaling connection to perform the mobilityregistration procedure
[0046] FIG. 8 illustrates a challenge scenario where a UE is stuck in aconnected state and when the network has not released the signaling connection.For example, the UE may be registered for enhanced mobile broadband slice(eMBBs) service and may have user plane resources setup. Also, the UE may enterthe MM states of 5GMM-Connected and 5GMM-Registered.Normal-Service.When the UE receives a configuration update command message, from an accessand mobility function (AMF), containing a configuration update indication IE witha registration bit set to "registration requested" due to network slicing subscriptionchange indication, then the UE may perform the mobility registration again afterthe release of the current N1 NAS signaling connection.
[0047] For the UE to release the N1 NAS signaling connection locally, ifthe network has failed to release the signaling connection, the UE may start theconnection release timer if there are no emergency PDU sessions established and ifthere are no user plane resources for PDU sessions that have been set up as percertain specifications (an example of this is 3GPP specifications). If the networkslice subscription has changed, all allowed and configured slices may be erased bythe AMF. Therefore, even if there may be DRBs set up, it may not help the UE fordata session as the AMF itself may want to release the signaling connection. Dueto the UE being registered with user plane resources for the PDU sessions set upand the network failing to release the user plane resources and the signalingconnection, the UE may get stalled in the connected state for an indefinite period oftime without any service. This issue may also be applicable to dual subscriberidentity module (SIM) dual standby (DSDS) devices, and may be more evident inDSDS devices where the UE may miss a DRB release or RRC release when radiofrequency (RF) is being used by another stack.
[0048] The UE may start the connection release timer upon all of thefollowing conditions being satisfied:a. The UE receives the configuration update command message havingthe configuration update indication IE with the registration bit set to"registration requested" and with one or more of the following: i)either new allowed network slice selection assistance information(NSSAI) information, new configured NSSAI information, or both,ii) the network slicing subscription change indication, or iii) no otherparameters;b. The user plane resources for PDU sessions have not been set up; andc. No emergency PDU sessions have been established.
[0049] With respect to the first event, if any changes to the allowed NSSAIinvolve the UE immediately or promptly performing the registration procedurebecause the changes affect the existing connectivity to network slices, for example,the new single-NSSAI (S-NSSAI), may involve a separate AMF that may not bedeterminable by the current serving AMF, or the AMF may not determine theallowed NSSAI, or if the changes do not affect the existing connectivity to thenetwork slices because of AMF local policies, the serving AMF may indicate to theUE to perform the registration procedure without including the globally uniqueAMF ID (GUAMI) or 5G-S-temporary mobile subscriber identity (TMSI) in theaccess stratum signaling after entering connection management-IDLE (CM-IDLE)state. The AMF may release the NAS signaling connection to the UE to allow toenter CM-IDLE after receiving the acknowledgement from the UE.
[0050] If the UE receives an indication to perform the registrationprocedure without including the GUAMI or 5G-S-TMSI in the access stratumsignaling after entering CM-IDLE state, then the UE may delete any stored (old)allowed NSSAI, any associated mapping, and any rejected (old) S-NSSAI.
[0051] The UE may initiate the registration procedure with the registrationtype mobility registration update after the UE enters CM-IDLE state. The UE mayinclude a requested NSSAI with the associated mapping of the requested NSSAI inthe registration request message. The UE may also include a requested NSSAI inthe access stratum signaling, but no GUAMI.
[0052] If there are established PDU sessions associated with emergencyservices, then the serving AMF may indicate to the UE to perform the registrationprocedure, however, the AMF may fail to release the signaling connection to theUE. As a result, the UE may only be able to perform the registration procedure afterthe release of the PDU sessions used for emergency services.Scenario 5 Challenge: Releasing the signaling connection to perform themobility registration procedure in a DSDS device
[0053] FIG. 10 illustrates a challenge scenario in a dual sim dual standby(DSDS) device where one of the subscriber identity module application toolkits(STKs) of a UE is stuck in a connected state due to its failure to release the signalingconnection. At least one of the two STKs of the UE may be registered with the 5Gnetwork (also referred to herein as UE-5G STK or UE-STK1), and user planeresources may be established for PDU sessions for enhanced mobile broadbandslice (eMBBs). The other STK may be registered with a long-term evolution (LTE)network (e.g., 4G network) and in EMM-IDLE state, or may also be registered withthe 5G network. The slice subscription for the UE may be updated at the AMF side.The AMF may send to the UE the configuration update command message with theregistration request and the network slice subscription changed. The network mayfail to release the signaling connection, and due to user plane resources existing, theUE may fail to start the connection release timer (an example of this is T3540).Paging for downlink (DL) short message service (SMS) from a MME may besignaled to the STK with the LTE network (also referred to herein as UE-LTE STKor UE-STK2). The UE-LTE STK may become active and send a service requestfrom idle mode to the MME. The AMF may then send a signaling releaseindication / message to the UE-5G STK but the UE-5G STK may fail to process theRRC release message from the AMF due to RF tune-away to the UE-LTE STK.Upon the UE-5G STK resuming, the 5G remains in connected mode withoutperforming connection release as it is still waiting for the "connection release"(which was missed due to no RF with UE-5G STK) from the network. As a result,the UE-5G STK may get stalled in connected mode for an indefinite period of timewithout any service. When the UE-5G STK becomes active, it may not progresswith any pending uplink (UL) messages as the mobility registration has still notbeen performed from 5GMM-IDLE state. For further background understanding,under 3GPP clause TS 23.401 section 5.4.4.4., when a network has requested forregistration through the configuration update command (indicating certainconfiguration changes) containing the configuration update indication IE with theregistration bit set to "registration requested," the UE 10 may need to go to idlemode and perform mobility registration without GUAMI or 5G- STMSI. However,the STK1 may be unable to perform the mobility registration without GUAMI or5G-STMSI after it is active as the connection release message was missed by theSTK1 because the STK2 was using the radio receiver and transmitter of the UE atthat time. Due to this, uplink signaling, data etc. may not be possible on STK1.
[0054] In other challenge scenarios where the UE-LTE STK is replaced bya second UE-5G STK, the second UE-5G STK may perform the same actions as,or similar actions t o, the UE-LTE STK as described aboveScenario 6 Challenge: Performing a mobility registration procedure upon receivinga registration reject message with an abnormal cause
[0055] FIGS. 12A and 12B illustrate a challenge scenario where a UE isstuck in a connected state after receiving a registration reject message having anabnormal cause value. Prior to the UE sending a registration request to the network,a series of basic steps may be followed by the UE, such as powering on of the UE,initialization of the layers, completion of reading the SIM card, triggering of theregistration procedure, and establishment of NAS and AS level security. Upon theUE sending a registration request to the network for initial registration, the networkmay, in response to the registration request, send a registration reject messageindicating a rejection of the registration request. The registration reject messagemay have an abnormal cause value. The timer T3346 value IE may not be includedin the registration request message. The UE may determine this situation to be anabnormal case, and following this, the UE may increment a 5G registration attemptcounter and increment a first short timer (an example of this is T3511). However,the network may not release the signaling connection. Upon the expiry of the firstshort timer, the UE may send again a registration request to the network, followingwhich the network may again send a registration reject message having an abnormalcause value, in response to the registration request. The UE may increment the 5Gregistration attempt counter again, where the process may be repeated until the 5Gregistration attempt counter reaches a value equal to or greater than the thresholdcount. Upon the 5G registration attempt counter reaching this value (e.g., "5"), theUE may start a second short timer (an example of this is T3502) for a specific timeperiod, which may be predetermined or alternatively, given. After the expiry of thesecond short timer, the UE may send again a registration request to the network,following which the network may send a registration accept message to the UE.When the UE requests registration (through the registration request) and is acceptedby the network (through the registration accept), the UE may need to acknowledgethis through the "registration complete" message. If after this process there is nodata to be exchanged between the UE and the network, the network may thenrelease the connection, upon which the UE may move to 5G idle state. Thedrawback in this scenario is that once the second short timer is started, the UE couldremain in connected mode for a duration longer than the specific time period forwhich the second short timer runs, during which the UE may not perform anyprocedures or be able to avail itself of any services.Scenario 7 Challenge: Performing a mobility registration procedure in a DSDSdevice upon receiving a registration reject message with an abnormal cause
[0056] FIG. 14 illustrates a challenge scenario in a DSDS device where aftera UE receives a registration reject message having an abnormal cause value, the UEis stuck in a connected state due to its failure to release the signaling connection.The UE may be registered with two STKs, with at least one of the two STKs havingthe 5G network (also referred to herein as UE-5G STK or UE-STK1). The otherSTK may be registered with the 5G network or the LTE network and in EMMIDLEstate (also referred to herein as UE-LTE STK or UE-STK2). If the UE entersa tracking area that is not present in a registered TAI list, the UE may trigger amobility registration procedure. The AMF may send to the UE a mobilityregistration reject message with a 5GMM cause. The network may also fail torelease the signaling connection. In response to the mobility registration rejectmessage, the UE may increment the 5G registration attempt counter and start thefirst short timer (an example of this is T3511), as the 5GMM cause may be anabnormal cause and because the UE may be remaining in connected mode. Oncethe 5G registration attempt counter reaches a value equal to or greater than thethreshold count (e.g., 5), the second short timer (an example of this is T3502) maybe started. Paging for DL SMS from MME may be signaled to one of the two STK(e.g., the UE-LTE STK). The STK receiving the paging for DL SMS may becomeactive and send a service request from idle mode. The AMF may then send asignaling release to the UE-5G STK, but the UE-5G STK may fail to process theRRC release message from the AMF due to RF tune-away to the UE-LTE STK.Due to this, the UE may be stalled in connected mode for an indefinite time periodwithout any service. The NAS downlink (DL) transport message is a NAS messagethat can carry short message service (SMS), position information container etc. Thenetwork can send this message after paging the UE, based on which the UE movesto connected state and the network transmits this message to the UE. When the UE-5G STK becomes active, it may not progress with idle procedure actions until itenters idle mode. The UE may continue to remain in connected with the secondshort timer still running as the UE may be waiting for the network to release thesignaling connection. When the abnormal failures relate to the UE-STK1 havingthe 5G network, the 5G registration attempt counter is incremented for everyinstance of receiving the registration reject message.
[0057] For tracking the abnormal failures relating to the UE-STK2 havingthe 4G network, an attach attempt counter is incremented for every instance of theattach procedure being rejected with an abnormal reject cause.
[0058] The challenges that follow from such scenarios involving NASsignaling may include a delay in resuming data sessions, resource wastage due tobreaking and / or making of a connection, keeping the connection without anyactivity, and / or having the UE stuck in a connected state without any uplink (UL)or downlink (DL) services. Additionally, when the UE is camped in a fake network(a false base station and network that may attack a UE to fetch informationregarding the UE or a user), this may lead to drainage of the UE resources throughrepeated signaling rejects and re-attempts. Prolonged connection of the UE in aconnected state may lead to wastage of resources in both the network and UE. Theremay be extra overhead of signaling, and the delay in data services may beparticularly harmful in situations in which critical data is being sent. Devices havingdual SIM capabilities may suffer as prolonged connected state in one SIM mayhamper the procedures in the other SIM. Embodiments provide systems andmethods for overcoming the drawbacks and inefficiencies associated when suchscenarios in NAS signaling are encountered.
[0059] Embodiments herein disclose methods and systems for completinga registration procedure in a wireless communication network by optimizing orimproving the signaling and connection mana gement in a non-access stratum.
[0060] Embodiments herein disclose methods and systems for completinga TAU procedure in the wireless communication network.
[0061] Embodiments herein disclose methods and systems for locallyreleasing a signaling connection in the wireless communication network.
[0062] Embodiments herein disclose methods and systems for completinga registration procedure when the UE receives a registration reject message with anabnormal cause value.
[0063] Embodiments herein and the various features and advantageousdetails thereof are explained more fully with reference to the non-limiting examplesthat are illustrated in the accompanying drawings and detailed in the followingdescription. Descriptions of well-known components and processing techniques areomitted so as to not unnecessarily obscure embodiments herein. The examples usedherein are intended merely to facilitate an understanding of ways in whichembodiments herein may be practiced and to further enable those of skill in the artto practice embodiments herein. Accordingly, the examples should not be construedas limiting the scope of embodiments herein. According to embodiments, timersdiscussed herein may correspond to those provided in 3GPP specifications.
[0064] Embodiments herein disclose methods and systems to overcome thechallenges of various scenarios in NAS signaling. Referring now to FIGS. 1 through17, where similar reference characters denote corresponding features consistentlythroughout the figures, there are shown embodiments.Scenario 1 solution: Completing a registration procedure in the 5G network upontransmission failure of the registration complete message
[0065] FIG. 2 illustrates a solution to the challenge scenario discussed inconnection with FIG. 1 where a UE 10 is unable to perform the registrationprocedure upon the transmission failure of the registration complete message dueto the TAI change, according to embodiments as disclosed herein. As outlined inthe scenario 1 challenge, after the UE 10 starts the connection release timer (anexample of which is T3540), the UE 10 may then meet at least one of the followingconditions to trigger a new registration request:a. Cell change (also referred to herein as "movement of the UE 10") toa new tracking area that is not present in a registered tracking areaidentity (TAI) list;b. Cell change to a new tracking area before the completion of theongoing mobility registration procedure; orc. Transmission failure of the registration complete message from theUE 10 to the 5G network.
[0066] Once the UE 10 meets the conditions to transmit the new registrationrequest, the UE 10 may then stop the connection release timer and perform a localrelease of the signaling connection for immediately or promptly initiating the newor subsequent mobility registration procedure. According to embodiments, the UE10 may stop (e.g., interrupt) the connection release timer before expiration of theconnection release timer in response to meeting one or more of the above conditionsto trigger a new registration request. According to embodiments, the UE 10 mayperform a new registration in response to meeting the one or more of the aboveconditions, the new registration including local release of a current signalingconnection (e.g., if the UE 10 is in a connected state) and / or transmission of a newregistration request message.
[0067] In embodiments, as illustrated by the method 300 in FIGS. 3A and3B for completing the registration procedure in the 5G network in a DSDS deviceupon a transmission failure of the registration complete message, the followingoperations may be performed, according to embodiments as disclosed herein. Whilethe UE 10 is described as being a DSDS device in the context of performing themethod 300, similar operations (e.g., operations 304-310) may be performed by theUE 10 in embodiments in which the UE 10 is not a DSDS device. At operation 302,the UE 10 may be registered with two STKs, wherein at least one of the two STKshas (e.g., is connected to) the 5G network. At operation 304, the UE 10 may transmitthe registration request message to (e.g., to the 5G network via) the STK having the5G network (also referred to herein as UE-5G STK). At operation 306, the UE 10may start the connection release timer upon the occurrence all the events thatfollow:a. The registration accept message does not include any pendingNSSAI IE;b. The UE 10 has set a follow-on request indicator to "No follow-onrequest pending" in the registration request message;c. The UE 10 has not included an uplink (UL) data status IE in theregistration request message, or the UE 10 has included the UL datastatus IE in the registration request message but the registrationaccept message indicates that no user plane resources of any PDUsessions are to be re-established;d. The UE 10 has not included (e.g., in the registration requestmessage) an allowed PDU session status IE, has included (e.g., inthe registration request message) the allowed PDU session status IEindicating that there are no PDU sessions for which the UE 10 hasallowed the user plane resources to be re-established over access (anexample of this is 3GPP access) in the registration request message,or the UE 10 has included the allowed PDU session status IE in theregistration request message but the registration accept messagedoes not indicate that any user plane resources of any PDU sessionsare to be re-established;e. The mobility registration procedure has been initiated (e.g., by thesending of the registration request message) in 5GMM-IDLE mode;f. The user plane resources for PDU sessions have not been set up;and / org. The UE 10 is able to perform V2X communication withoutrequesting resources for the V2X communication over the referencepoint.
[0068] After starting the connection release timer, at operation 308, the UE10 may complete the registration procedure in the DSDS device after meeting atleast one of the following conditions to transmit the new registration requestmessage:a. Cell change (or movement) to a new tracking area that is not presentin a registered tracking area identity (TAI) list;b. Cell change (or movement) to a new tracking area before thecompletion of the ongoing mobility registration procedure; and / orc. Transmission failure of the registration complete message.
[0069] At operation 310, the UE 10 may then stop the connection releasetimer and initiate signaling (e.g., to perform a local release of the signalingconnection for immediately or promptly initiating the new or subsequent mobilityregistration procedure). According to embodiments, the UE 10 may stop (e.g.,interrupt) the connection release timer before expiration of the connection releasetimer in response to meeting one or more of the above conditions to transmit a newregistration request. According to embodiments, the UE 10 may perform a newregistration in response to meeting the one or more of the above conditions, the newregistration including local release of a current signaling connection (e.g., if the UE10 is in a connected state) and / or transmission of a new registration requestmessage.Scenario 2 Solution: Completing a tracking area update (TAU) procedure when aconnection release timer is running due to a previous TAU procedure
[0070] In order to overcome the impact of the initiation of the TAUprocedure or combined TAU procedure, the following operations in method 400, asillustrated in FIG. 4, may be performed. At operation 402, the UE 10 may start theconnection release timer if all of the following events occur:a. The UE receives the TAU accept message without a UE radiocapability identity deletion indication IE;b. The UE has not located (or included) any signaling active flag, anyactive flag, or any equivalent flag which indicates that the LTEnetwork (e.g., 4G network) is going to maintain connection in aTAU request message;c. The TAU procedure is initiated in LTE-EMM-idle mode (e.g., 4GEMM-idle mode); andd. One or more user plane resources for one or more radio bearers arenot set up.
[0071] At operation 404, the UE may transmit a new TAU request messageif one of the following conditions are met:a. A cell change (or movement) to a new tracking area that is notpresent in the registered TAI list;b. A cell change (or movement) to a new tracking area before thecompletion of the ongoing TAU procedure; orc. A transmission failure of the TAU complete message, due to whichthe UE 10 may re-initiate the TAU procedure.
[0072] At operation 406, the UE may stop the connection release timer (e.g.,in response to meeting one of the above conditions), and perform a local release ofthe signaling connection if the UE is in a connected state (e.g., in response tomeeting one of the above conditions). At operation 408, the UE may then initiatethe new TAU request message after the establishment of a radio connection (e.g.,in response to meeting one of the above conditions). According to embodiments,the UE 10 may stop (e.g., interrupt) the connection release timer before expirationof the connection release timer in response to meeting one of the above conditions.According to e mbodiments, the UE 10 may perform a new registration in responseto meeting the one or more of the above conditions, the new registration includinglocal release of a current signaling connection (e.g., if the UE 10 is in a connectedstate) and / or transmission of a new TAU request message. According toembodiments, the connection release timer is T3440.
[0073] In embodiments, upon an indication from the lower layers that theone or more user plane resources for the one or more radio bearers are set up, theUE 10 may stop the connection release timer and send uplink (UL) signaling viathe existing NAS signaling connection or user data via the one or more user planeresources for the one or more radio bearers. If the UL signaling is for CS fallbackfor emergency call, or for establishing a packet data network (PDN) connection foremergency bearer services, the UE 10 may send the UP signaling via the existingNAS signaling connection. If the UE 10 receives a detach request message, the UE10 may stop the connection release timer and may respond to the network initiateddetach.
[0074] In embodiments, if the UE 10 receives a request from upper layersto send NAS signaling not associated with establishing either a CS emergency callor a PDN connection for emergency bearer services, the UE 10 may wait for thelocal release of the established NAS signaling connection upon the expiry orstopping of the connection release timer. If the UE 10 receives a request from theupper layers to establish a CS emergency call or a PDN connection for emergencybearer services, the UE 10 may stop the connection release timer and may locallyrelease the NAS signaling connection. If the UE 10 receives an EPS (evolved packetsystem) Session Management (ESM) data transport message, as an implementationoption, the UE 10 may reset and restart the connection release timer. If the UE 10receives a DL NAS transport message or a DL generic NAS transport message, theUE, which may be EMM-registered without PDN connection, the UE 10 may stopthe connection release timer and may send UL signaling via the existing signalingconnection. If the UE 10 receives an activate default EPS bearer context requestmessage, a modify EPS bearer context request message, a deactivate EPS bearercontext request message, a DL NAS transport message or a DL generic NAStransport message, and if the UE 10 is using a control plane cellular internet ofthings (CIoT) EPS optimization, the UE 10 may stop the connection release timerand may send the UL signaling via the existing signaling connection.
[0075] In embodiments, the UE 10, upon receiving a request from upperlayers to send NAS signaling not associated with establishing a PDN connectionfor emergency bearer services, the UE 10 may wait for the local release of theestablished NAS signaling connection upon expiry or stopping of the connectionrelease timer. If the UE 10 receives a request from the upper layers to establish aPDN connection for emergency bearer services, the UE 10 may stop the connectionrelease timer and locally release the NAS signaling connection.
[0076] In embodiments, upon an indication from the lower layers that theradio release control (RRC) connection has been released, the UE 10 may stop theconnection release timer and perform a new attach procedure. If the UE 10 receivesa request from the upper layers to establish a PDN connection for emergency bearerservices, the UE 10 may stop the connection release timer and locally release theNAS signaling connection.
[0077] In embodiments, upon receiving a request from the upper layers tosend NAS signaling not associated with establishing either a CS emergency call ora PDN connection for emergency bearer services, the UE 10 may wait for the localrelease of the established NAS signaling connection upon expiry or stopping of theconnection release timer. If the UE 10 receives a request from the upper layers toestablish a CS emergency call or a PDN connection for emergency bearer services,the UE 10 may stop the connection release timer and locally release the NASsignaling connection.
[0078] In embodiments, if there is an indication from the lower layers thatthe user plane radio bearers are set up or upon receiving a request from the upperlayers to send NAS signaling not associated with the ESM data transport message,the UE 10 may stop the connection release timer. The UE 10 may also not sendESM data transport message until the expiry or stopping of the connection releasetimer.Scenario 3 Solution: Completing a mobility registration procedure upon receivinga service accept message and before establishment of a data radio bearer
[0079] FIG. 6 illustrates a solution to the challenge scenario illustrated inFIG. 5 where the UE 10 is unable to perform the mobility registration procedureupon receiving a service accept message and before the establishment of a dataradio bearer (DRB), according to embodiments as disclosed herein. After the UE10 starts the connection release timer, upon the occurrence of the one or more eventsas outlined in the paragraph describing the challenge in the third scenario, the UE10 may meet at least one of the following conditions to trigger a new MobilityRegistration request:a. changing of a cell to a new tracking area that is not present in aregistered TAI list due to handover; andb. a DRB is not established by the network (an example of which isradio access network (RAN)).
[0080] Upon meeting the above conditions, the UE 10 may stop theconnection release timer and initiate signaling immediately or promptly (e.g., toperform a local release of the signaling connection for initiating the new orsubsequent mobility registration procedure). According to embodiments, the UE 10may stop (e.g., interrupt) the connection release timer before expiration of theconnection release timer in response to meeting one or more of the above conditionsto trigger a new Mobility Registration request. According to embodiments, the UE10 may perform a new registration in response to meeting the one or more of theabove conditions, the new registration including local release of a current signalingconnection (e.g., if the UE 10 is in a connected state) and / or transmission of a newregistration request message.
[0081] In embodiments, as illustrated by method 700 in FIG. 7, forcompleting the registration procedure in the 5G network in a DSDS device, thefollowing operations may be performed. While the UE 10 is described as being aDSDS device in the context of performing the method 700, similar operations (e.g.,operations 704-710) may be performed by the UE 10 in embodiments in which theUE 10 is not a DSDS device. At operation 702, the UE 10 may register with twoSTKs, where one of the two STKs has the 5G network. At operation 704, the UE10 may transmit the service request message to the UE-5G STK. At operation 706,the UE 10 may start the connection release timer on all of the following conditionsbeing satisfied:a. The UE 10 receives the service accept message from the network;b. The UE 10 did not set (e.g., in the service request message) theservice type IE to "signaling" or "high priority access," the UE 10has not included the UL data status IE in the service requestmessage, or the UE 10 has included the UL data status IE in theservice request message but the service accept message indicatesthat no user plane resources of any PDU sessions are to be re20established;c. The UE 10 has not included (e.g., in the service request message)the allowed PDU session status IE, has included the allowed PDUsession status IE (e.g., in the service request message) indicatingthere are no PDU sessions for which the UE 10 has allowed the userplane resources to be re-established over access (an example of thisis 3GPP access) in the service accept message, or the UE 10 hasincluded the allowed PDU session status IE in the service requestmessage but the service accept message does not indicate that anyuser plane resources of any PDU sessions are to be re-establishedd. The service request procedure has been initiated in 5GMM-IDLEmode;e. The user plane resources for PDU sessions have not been set up; andf. The UE 10 is able to perform V2X communication withoutrequesting resources for the V2X communication over the referencepoint.
[0082] After starting the connection release timer, at operation 708, the UE10 may meet at least one of the following conditions to transmit the new MobilityRegistration request message:a. the service request is accepted and no DRB is establishedfrom the network; and / orb. handover or RRC re-establishment to a new tracking areathat is not in the UE 10 TAI list.
[0083] At operation 710, the UE 10 may then stop the connection releasetimer and initiate signaling (e.g., to perform a local release of the signalingconnection for immediately or promptly initiating the new or subsequent mobilityregistration procedure). According to embodiments, the UE 10 may stop (e.g.,interrupt) the connection release timer before expiration of the connection releasetimer in response to meeting one or more of the above conditions to transmit a newMobility Registration request message. According to embodiments, the UE 10 mayperform a new registration in response to meeting the one or more of the aboveconditions, the new registration including local release of a current signalingconnection (e.g., if the UE 10 is in a connected state) and / or transmission of a newservice request message.Scenario 4 Solution: Releasing a signaling connection to perform the mobilityregistration procedure
[0084] FIG. 9 illustrates a solution to the challenge scenario illustrated inFIG. 8 where the UE 10 is stuck in the connected state and when the network hasnot released the signaling connection, according to embodiments as disclosedherein. In order to prevent the UE 10 from being stalled in the connected state foran indefinite period of time, or reduce the occurrence thereof, and when the networkhas failed to release the signaling connection, the UE 10 may be allowed to start theconnection release timer despite user plane resources existing, provided that all ofthe following events occur:a. The UE 10 receives the configuration update command, from theAMF, containing the configuration update indication IE with theregistration bit set to "registration requested," and the configurationupdate command includes one or more of the following: i) anallowed NSSAI (e.g., new allowed NSSAI), a configured NSSAI(e.g., new configured NSSAI), or both, ii) the network slicingindication IE with the network slicing subscription changeindication set to "network slicing subscription changed," or iii) noother parameters; and / orb. No emergency PDU sessions have been established for the UE.
[0085] Upon starting the connection release timer, the UE 10 may wait untilthe expiry of the connection release timer to release the signaling connection.According to embodiments, the UE 10 may be able to override or interruptconventional protocol (e.g., 3GPP protocol) to start the connection release timerdespite the existence of user plane resources. Upon releasing the signalingconnection, the UE 10 may then, from 5GMM-IDLE state, perform the mobilityregistration procedure without GUAMI or 5G-STMSI. Alternatively, the AMF mayinitiate the release of the signaling connection.Scenario 5 Solution: Releasing the signaling connection to perform the mobilityregistration procedure in a DSDS device
[0086] FIG. 11 illustrates a solution to the challenge scenario illustrated inFIG. 10 in the DSDS device where the UE-5G STK is in the connected state due toits failure to release the signaling connection, according to embodiments asdisclosed herein. The UE-STK1 (which may be registered with the 5G network) inthe UE 10 may start the connection release timer even if user plane resources areestablished for non-emergency PDU sessions. According to embodiments, the UE10 may be able to override or interrupt conventional protocol (e.g., 3GPP protocol)to start the connection release timer despite the existence of user plane resources.The UE-STK2 (which may be registered with the 5G network or the 4G network)may become active to process one or more triggered services. An example of thetriggered process may be a mobile originated or terminated service, such as mobileterminated paging for DL SMS. The UE-STK1 in UE 10 may not be able to receiveor process any transmitted command (an example of which is the RRC releasemessage) from the AMF as the service request procedure on the UE-STK2 isongoing. Upon expiry of the connection release timer and completion of the servicerequest procedure on the UE-STK2, the UE-STK1 in the UE 10 may then becomeactive and perform the local release of the signaling connection. If the connectionrelease timer has expired during the service request procedure on the UE-STK2, theUE-STK1 may remember (or detect) this event and perform the local release afterthe UE-STK1 becomes active. Then from 5GMM-IDLE state, the UE 10 mayperform the mobility registration without GUAMI or 5G-STMSI.Scenario 6 Solution: Performing a mobility registration procedure upon receiving aregistration reject message with an abnormal cause
[0087] FIGS. 13A and 13B illustrate a solution to the challenge scenarioillustrated in FIGS. 12A-12B where the UE 10 is stuck in the connected state afterreceiving the registration reject message having the abnormal cause value,according to embodiments as disclosed herein. Once the UE receives theregistration reject message, the UE 10 may increment the 5G registration attemptcounter. The UE 10 may locally release the signaling connection upon at least oneof the following situations occurring:a. the UE 10 receives the registration reject message having anabnormal cause value and the network does not release the signalingconnection; and / orb. expiry of the first short timer, wherein the UE 10 may start the firstshort timer after incrementing the 5G registration attempt counter.
[0088] Following the expiry of the first short timer, the next registrationprocedure may be triggered from 5GMM-IDLE mode. In embodiments, the UE 10may locally release the signaling connection upon the 5G registration attemptcounter reaching a value equal to or greater than the threshold count. The UE 10may then start the second short timer, and upon expiry of the second short timer,the UE 10 may send a new mobility registration request message.Scenario 7 Solution: Performing a mobility registration procedure in a DSDS deviceupon receiving a registration reject message with an abnormal cause
[0089] FIG. 15 illustrates a solution to the challenge scenario in the DSDSdevice where after the UE 10 receives the first registration reject message havingthe abnormal cause value, the UE 10 is stuck in the connected state due to its failureto release the signaling connection, according to embodiments as disclosed herein.After (e.g., in response to) receiving the registration reject message from the AMFwith a 5GMM cause, and / or the network not releasing the user plane resources andthe signaling connection, the UE 10 may start the second short timer. Upon the 5Gregistration attempt counter reaching a value equal to or greater than the thresholdcount, the UE 10 may locally release the signaling connection. One of the two STKsmay become active to process one more triggered services (an example of this isprocessing paging for DL SMS), and then send a service request to the MME. TheMME may send an RRC release message to the STK that processes the triggeredservices, which may then result in the completion of a plurality of servicesassociated with this STK. The UE-5G STK may become active, and when the UE10 finds a new suitable cell in a new tracking area by idle procedure, the UE 10 maystop the second short timer. After the stopping the second short timer, the UE 10may trigger the mobility registration procedure by sending a registration request tothe AMF. The AMF may respond by sending a registration accept message, and theUE 10 may find a suitable service immediately or promptly though the network didnot release the signaling connection in the STK having the 5G network. Forexample, according to embodiments, the UE may perform an immediate or promptrelease of the signaling connection upon the value of the 5G registration attemptcounter becoming equal to or greater than a threshold count, or after the expiry ofthe first short timer.
[0090] FIG. 16 illustrates a method 1600 by which the UE 10 may releasethe signaling connection after receiving an attach reject message or a TAU rejectmessage in a DSDS device, according to embodiments as disclosed herein. Atoperation 1602, the UE may be registered with two STKs, with at least one of thetwo STKs having (e.g., being connected to, registered with, etc.) the LTE network.At operation 1604, the UE may transmit an attach request message or a TAU requestmessage to a MME. At operation 1606, the UE may receive an attach reject messageor a TAU reject message having an abnormal cause value from the MME. Atoperation 1608, the UE may start the first short timer. At operation 1610, the attachattempt counter or the TAU attempt counter may be incremented for every instancethat the UE receives the attach reject message or the TAU reject message from theMME, respectively. At operation 1612, the UE may perform an immediate orprompt release of the signaling connection upon the value of the attempt counterbecoming equal to or greater than a threshold count (e.g., a predetermined oralternatively, given value), or after the expiry of the first short timer.
[0091] It is to be noted that there may be separate counters, associated witheach stack (the 5G stack or 4G stack) in the UE, that may be incremented uponreceiving the reject message with an abnormal cause value that is associated withthe respective stack. For example, in the case of 5G, for every instance of receivingthe registration reject message with an abnormal cause value, the 5G registrationattempt counter may be incremented. For example, in the case of 4G, for everyinstance of receiving the attach reject message with an abnormal cause value, theattach attempt counter may be incremented and for every instance of receiving theTAU reject message with an abnormal cause value, the TAU attempt counter maybe incremented.
[0092] The various actions or operations in method 300, 400, 700, and / or1600 may be performed in the order presented, in a different order, simultaneouslyor contemporaneously. Further, in embodiments, some actions or operations listedin FIGS. 3, 4, 7, and / or 16 may be omitted.
[0093] Conventional devices and methods for registering a UE with anetwork (e.g., base station) result in excessive resource consumption (e.g., power,processor, memory, bandwidth, etc.), delay and / or signaling. For example, whenthe conventional devices experience a signaling failure during registration (e.g., dueto cell change), the registration process becomes stalled. In some scenarios, theregistration is stalled while the conventional devices wait for expiration of a startedtimer. In some scenarios, the registration is stalled because conventional devicesare unable to start a timer due to an unmet precondition (e.g., network release ofuser plane resources). Accordingly, in such scenarios, the conventional devices andmethods experience the above-mentioned deficiencies.
[0094] However, according to embodiments, improved devices andmethods are provided for registering a UE with a network. For example, inscenarios in which the registration of the conventional devices would be stalledwaiting for timer expiration, the improved devices may stop (e.g., interrupt) thetimer before expiration and resume registration. In scenarios in which theregistration of the conventional devices would be stalled due to an unmetprecondition for starting a timer, the improved devices may override conventionalprotocols to start the timer despite the unmet precondition. Accordingly, in suchscenarios, the improved devices and methods overcome the deficiencies of theconventional devices and methods to at least reduce resource consumption (e.g.,power, processor, memory, bandwidth, etc.), delay and / or signaling in registeringthe UE with the network.
[0095] FIG. 17 illustrates a system 1700 for implementing optimization orimprovement of signaling and connection management in NAS. The system 1700may comprise the UE 10 and a plurality of connection release timers and shorttimers. The UE 10 may have a memory 1702 to store a set of instructions, that whenexecuted by a processor 1704, result in the UE performing at least one of thefollowing actions: transmitting a registration request message to the 5G network1710, transmit a registration complete message to the 5G network 1710, transmit aservice request message to the 5G network 1710, receive a registration acceptmessage from the 5G network 1710, receive a service accept message from the 5Gnetwork 1710, modify the registration request message (to include at least one of apending follow-on request, an uplink data status information element (IE), and / oran allowed protocol data unit (PDU) session status IE), modify the service requestmessage (e.g., to include at least one of a service type IE, an uplink data status IE,or an allowed PDU sessions status IE), transmit an attach request message or a TAUmessage to the LTE network (e.g., the 4G network 1712), receive an attach rejectmessage or a TAU reject message from the LTE network, receive a configurationupdate command message from the AMF 1716, locally release a signalingconnection if the UE is in a connected state, and start / stop the plurality ofconnection release timers and short timers. According to embodiments, theprocessor 1704 may implement and / or communicate with the UE-STK1 1706, theUE-STK2 1708, the plurality of connection release timers and / or the plurality ofshort timers. According to embodiments, the UE 10 may communicate with the 5Gnetwork 1710, the 4G network 1712, the MME 1714 and / or the AMF 1716 via oneor more network connections (e.g., RRC).
[0096] For example, in network of the system 1700, information may betransmitted in various multiple access schemes, such as Code Division MultipleAccess (CDMA), Frequency Division Multiple Access (FDMA), Time DivisionMultiple Access (TDMA), Orthogonal Frequency Division Multiple Access(OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA),OFDM-FDMA, OFDM-TDMA, and OFDM-CDMA.
[0097] Each of the 5G network 1710, the 4G network 1712, the MME 1714and / or the AMF 1716 may be implemented using a corresponding base station. Thebase station may generally refer to a fixed station that communicates with userequipment and / or other base stations, and may exchange data and controlinformation by communicating with user equipment and / or other base stations. Forexample, the base station may also be referred to as a Node B, an evolved-Node B(eNB), a next generation Node B (gNB), a sector, a site, a base transceiver system(BTS), an access point (AP), a relay node, a remote radio head (RRH), a radio unit(RU), a small cell, or the like. In the present specification, a base station or a cellmay be interpreted in a comprehensive sense to indicate some area or functioncovered by a base station controller (BSC) in CDMA, a Node-B in WCDMA, aneNB in LTE, a gNB or sector (site) in 5G, and the like, and may cover all the variouscoverage areas such as megacell, macrocell, microcell, picocell, femtocell and relaynode, RRH, RU, and small cell communication range. According to embodiments,the 5G network 1710 may refer to a base station implementing 5th generation LTEand / or the 4G network 1712 may refer to a base station implementing 4th generationLTE.
[0098] The user equipment 10 may be fixed or mobile and may refer to anydevice that may communicate with a base station, such as the 5G network 1710, totransmit and receive data and / or control information. For example, the UE 10 maybe referred to as a terminal, a terminal equipment, a mobile station (MS), a mobileterminal (MT), a user terminal (UT), a subscriber station (SS), a wireless device, ahandheld device, or the like.
[0099] According to embodiments, operations described herein as beingperformed by the UE 10, the processor 1704, the 5G network 1710, the 4G network1712, the MME 1714, the AMF 1716, the UE-STK1 1706 and / or the UE-STK21708 may be performed by processing circuitry. The term 'processing circuitry,'as used in the present disclosure, may refer to, for example, hardware includinglogic circuits; a hardware / software combination such as a processor executingsoftware; or a combination thereof. For example, the processing circuitry morespecifically may include, but is not limited to, a central processing unit (CPU), anarithmetic logic unit (ALU), a digital signal processor, a microcomputer, a fieldprogrammable gate array (FPGA), a System-on-Chip (SoC), a programmable logicunit, a microprocessor, application-specific integrated circuit (ASIC), etc.
[0100] The various operations of methods described above may beperformed by any suitable device capable of performing the operations, such as theprocessing circuitry discussed above. For example, as discussed above, theoperations of methods described above may be performed by various hardwareand / or software implemented in some form of hardware (e.g., processor, ASIC,etc.).
[0101] The software may comprise an ordered listing of executableinstructions for implementing logical functions, and may be embodied in any"processor-readable medium" for use by or in connection with an instructionexecution system, apparatus, or device, such as a single or multiple-core processoror processor-containing system.
[0102] The blocks or operations of a method or algorithm and functionsdescribed in connection with embodiments disclosed herein may be embodieddirectly in hardware, in a software module executed by a processor, or in acombination of the two. If implemented in software, the functions may be stored onor transmitted over as one or more instructions or code on a tangible, non-transitorycomputer-readable medium. A software module may reside in Random AccessMemory (RAM), flash memory, Read Only Memory (ROM), ElectricallyProgrammable ROM (EPROM), Electrically Erasable Programmable ROM(EEPROM), registers, hard disk, a removable disk, a CD ROM, or any other formof storage medium known in the art.
[0103] Embodiments disclosed herein may be implemented through at leastone software program running on at least one hardware device (an example of thisis the UE 10) and performing network management functions to control the networkelements.
[0104] It is to be noted that the terms "connected mode" and "connectedstate" as included in the description herein are used interchangeably. It is also to benoted that the various threshold counts for the registration attempt counter may bepredetermined or alternatively, given.
[0105] It is to be noted that the term "user plane resources" may imply theestablishment of user plane radio bearers for the EPS bearers (in LTE) or PDUsessions (in NR) which may be active at the UE 10. However, it is also to be notedthat the user plane configuration can be different for different PDU sessions orbearers.
[0106] It is to be noted that the term "abnormal cause values" may refer tothe reject causes (e.g., REGISTRATION REJECT message and SERVICEREJECT message) as referenced in 3GPP TS 24501 and 3GPP TS 24301.
[0107] The foregoing description of specific examples will so fully revealthe general nature of embodiments herein that others may, by applying currentknowledge, readily modify and / or adapt for various applications such specificexamples without departing from the generic concept, and, therefore, suchadaptations and modifications should and are intended to be comprehended withinthe meaning and range of equivalents of embodiments. It is to be understood thatthe phraseology or terminology employed herein is for the purpose of descriptionand not of limitation. Therefore, while embodiments herein have been described interms of examples, those skilled in the art will recognize that the examples disclosedherein may be practiced with modification within the spirit and scope ofembodiments as described herein.
Claims
1. A method for completing a registration procedure in a fifth generation (5G) network (1710), comprising: transmitting, by a use r equipment (UE) (10), a registration request message to the 5G network (1710), the registration request message initiating a first registration procedure; starting, by the UE (10), a connection release timer in response to occurrence of a plurality of events, the plurality of events including: receiving, by the UE (10), a first registration accept message from the 5G network (1710), the first registration accept message not including pending slice selection assistance information, the registration request message does not include a pending followon request, the registration request message does not include an uplink data status information element (IE), or the registration request message includes the uplink data status IE and a second registration accept message received by the UE (10) from the 5G network (1710) indicates that no user plane resources of protocol data unit (PDU) sessions are to be re-established, the registration request message does not include an allowed PDU session status IE, the registration request message includes the allowed PDU status IE which indicates there are no PDU sessions for which the UE (10) has allowed the user plane resources to be re-established over access, or the allowed PDU session status IE in the registration request message is included by the UE (10) and a third registration accept message received by the UE (10) from the 5G network (1710) does not indicate that user plane resources of PDU sessions are to be re-established, the transmitting the registration request message is performed while the UE is in 5G mobility management (5GMM)-idle mode, first user plane resources for first PDU sessions are not set up, and the UE (10) is configured to perform vehicle to everything (V2X) communication without requesting resources for the V2X communication over a reference point; meeting, by the UE (10), at least one of a plurality of conditions, the plurality of conditions including: transmission failure of a registration complete message from the UE (10) to the 5G network (1710), movement of the UE (10) to a new tracking area before the completion of the first registration procedure, and movement of the UE (10) to a new tracking area that is not in a registered tracking area identity (TAI) list; stopping, by the UE (10), the connection release timer in response to the meeting the at least one of the plurality of conditions; and performing, by the UE (10), a local release of a signaling connection in response to the meeting the at least one of the plurality of conditions if the UE (10) is in a connected state.
2. The method of claim 1, wherein the connection release timer is T3540.
3. The method of claim 1, wherein the UE (10) is a dual sim dual standby (DSDS) device with two subscriber identity module application toolkits (STKs) (1706 / 1708), one of the two STKs being registered with the 5G network (1710); and the transmitting the registration request message transmits the registration request message via the one of the two STKs (1706 / 1708) registered with the 5G network (1710).
4. A method for completing a tracking area update (TAU) procedure in a fourth generation (4G) network (1712), comprising: Transmitting, by a user equipment (UE) (10), a TAU request message to the 4G network (1712), the TAU request message initiating a first registration procedure; starting, by the UE (10), a connection release timer in response to occurrence of a plurality of events, the plurality of events including: a TAU accept message that is received does not include a UE radio capability identity deletion indication information element (IE); the TAU request message does not include a signaling active flag, an active flag, or a flag indicating that the 4G network (1712) is going to maintain connection, the first registration procedure is initiated while the UE is in 4G mobility management (EMM)-idle mode, and one or more user plane resources for one or more radio bearers are not set up; meeting, by the UE (10), at least one of a plurality of conditions, the plurality of conditions including: transmission failure of a TAU complete message from the UE (10) to the 4G network (1712), movement of the UE (10) to a new tracking area before the completion of the first registration procedure, and movement of the UE (10) to a new tracking area that is not available in a registered tracking area identity (TAI) list; stopping, by the UE (10), the connection release timer in response to the meeting the at least one of the plurality of conditions; performing, by the UE (10), a local release of a signaling connection in response to the meeting the at least one of the plurality of conditions if the UE (10) is in a connected state; and initiating, by the UE (10), another TAU request message after establishment of a radio connection and the stopping the connection release timer.
5. The method of claim 4, wherein the connection release timer is T3440.
6. A method for completing a mobility registration procedure in a 5G network (1710), comprising: transmitting, by a user equipment (UE) (10), a service request message to the 5G network, the service request message initiating a first service request procedure; starting, by the UE (10), a connection release timer in response to occurrence of a plurality of events, the plurality of events including: receiving, by the UE (10), a first service accept message from the 5G network (1710), a service type information element (IE) is not set for signaling or high priority access in the service request message, the an uplink data status IE is not included in the service request message, or the uplink data status IE is included in the service request message and a second service accept message received by the UE from the 5G network (1710) indicates that no user plane resources of a protocol data unit (PDU) session are to be reestablished, the service request message does not include an allowed PDU sessions status IE, the service request message includes the allowed PDU sessions status IE which indicates that there are no PDU sessions for which the UE (10) has allowed the user plane resources to be re-established over access, or the service request message includes the allowed PDU sessions status IE and the service accept message does not indicate that user plane resources of PDU sessions are to be re-established, the transmitting the service request message is performed while the UE is in 5G mobility management (5GMM)-idle mode, first user plane resources for first PDU sessions have not been set up, and the UE (10) is configured to perform vehicle to everything (V2X) communication without requesting resources for the V2X communication over a reference point; meeting, by the UE (10), at least one of a plurality of conditions, the plurality of conditions including: changing of a cell to a new tracking area, the new tracking area not being present in a registered tracking area identity (TAI) list due to a handover, and a data radio bearer not being established by a radio access network; stopping, by the UE (10), the connection release timer in response to the meeting the at least one of the plurality of conditions; and initiating, by the UE (10), signaling in response to the meeting the at least one of the plurality of conditions.
7. The method of claim 6, wherein the UE (10) is a dual sim dual standby (DSDS) device with two subscriber identity module application toolkits (STKs) (1706 / 1708), one of the two STKs being registered with the 5G network; and the transmitting the service request message transmits the service request message via the one of the two STKs (1706 / 1708) registered with the 5G network (1710).
8. A method for performing a local release of a signaling connection in a wireless communication network, comprising: receiving, by a user equipment (UE) (10), a configuration update command message from an access and mobility management function (AMF) (1716), the configuration update command message including a configuration update indication information element (IE) with a registration request due to a change in a network slice subscription; and starting, by the UE (10), a connection release timer in response to occurrence of a plurality of events, the plurality of events including: the configuration update command message including at least one of: new allowed network slice selection assistance information (NSSAI), new configured NSSAI, or a combination of the new allowed NSSAI and the new configured NSSAI, or a network slicing indication IE that indicates a change in a network slice, and no emergency protocol data unit (PDU) sessions having been established irrespective of whether a plurality of user plane resources for one or more PDU sessions have been set up; and locally releasing, by the UE (10), a signaling connection on expiry of the connection release timer.
9. The method of claim 8, wherein the UE (10) is a dual sim dual standby (DSDS) device with two subscriber identity module application toolkits (STKs), a first STK among the two STKs (1706 / 1708) being registered with a fifth generation (5G) network (1710); the starting the connection release timer starts the connection release timer while the plurality of user plane resources are established for the one or more PDU sessions; and the method further comprises establishing the plurality of user plane resources for the one or more PDU sessions, transmitting, by the AMF (1716), the configuration update command message to the first STK (1706), activating a second STK (1708) among the two STK to process one or more triggered services, transmitting, by the AMF (1716), a command to release the signaling connection to the first STK (1706), failing, by the first STK (1706), to process the transmitted command by the AMF (1716) to release the signaling connection, and activating the first STK (1706) for performing the local release of the signaling connection, by the UE (10), upon expiry of the connection release timer.
10. A method for performing a local release of a signaling connection upon receiving a mobility registration reject message for a mobility registration procedure, comprising: transmitting, by a user equipment (UE) (10), a mobility registration request message to a network; receiving, by the UE (10), the mobility registration reject message from the network, the mobility registration reject message including an abnormal cause value; starting, by the UE (10), a first short timer in response to receiving the mobility registration reject message; and performing the local release of the signaling connection upon receiving the mobility registration reject message or expiry of the first short timer.
11. The method of claim 10, further comprising: incrementing a first attempt counter in response to receiving the mobility registration reject message; starting a second short timer in response to the first attempt counter having a value equal to or greater than a first threshold count; and transmitting a new mobility registration request message upon expiry of the second short timer.
12. The method of claim 10, wherein the UE is a dual sim dual standby (DSDS) device with two subscriber identity module application toolkits (STKs) (1706 / 1708), a first STK (1706) among the two STKs being registered with a fifth generation (5G) network (1710); the transmitting the mobility registration request message transmits the mobility registration request message to an access and mobility management function (AMF) (1716); the receiving the mobility registration reject message receives the mobility registration reject message from the AMF (1716); and the method further comprises incrementing a first attempt counter in response to receiving the mobility registration reject message, and performing a local release of the signaling connection upon a value of the first attempt counter becoming equal to or greater than a second threshold count.
13. The method of claim 12, further comprising: starting a second short timer in response to receiving the mobility registration reject message; activating a second STK (1708) among the two STKs to process one or more triggered services; and activating the first STK (1706) for triggering the mobility registration procedure after the activating the second STK (1708) upon the second short timer being stopped or expiring, the mobility registration procedure being performed without release of the signaling connection of the first STK (1706).
14. The method of claim 10, wherein the UE is a dual sim dual standby (DSDS) device with two subscriber identity module application toolkits (STKs) (1706 / 1708), a first STK (1706) among the two STKs being registered with a fourth generation (4G) network (1712); and the method further comprises transmitting, by the UE (10), an attach request message or a tracking area update (TAU) request message to a mobility management entity (MME) (1714), receiving, by the UE (10), an attach reject message or a TAU reject message having an abnormal cause from the MME (1714), starting, by the UE (10), the first short timer in response to receiving the attach reject message or the TAU reject message, incrementing a second attempt counter in response to receiving the attach reject message or incrementing a third attempt counter in response to receiving the TAU reject message, and releasing the signaling connection upon a value of the second attempt counter or the third attempt counter becoming equal to or greater than a third threshold count, or after expiry of the first short timer.
15. The method of claim 14, further comprising: activating a second STK (1708) among the two STKs (1706 / 1708) to process one or more triggered services; and activating the first STK (1706) for triggering an attach procedure or a TAU procedure upon expiry of the first short timer, the attach procedure or the TAU procedure being performed without release of the signaling connection of the first STK (1706).
16. A system, comprising: a fifth generation (5G) network (1710); a fourth generation (4G) network (1712); and a user equipment (UE) (10) configured to perform at least one of: transmitting a registration request message to the 5G network (1710), receiving a registration accept message from the 5G network (1710), transmitting a registration complete message to the 5G network (1710), modifying the registration request message to include at least one of: a pending follow-on request, an uplink data status information element (IE), or an allowed protocol data unit (PDU) session status IE, transmitting a service request message to the 5G network (1710), receiving a service accept message from the 5G network (1710), transmitting an attach request message or a tracking area update (TAU) request message to the 4G network (1712), receiving an attach reject message or a TAU reject message from the 4G network (1712), modifying the service request message to include at least one of: a service type IE, an uplink data status IE, or an allowed PDU sessions status IE, receiving a configuration update command message from an access and mobility management function (AMF) (1716), or locally releasing a signaling connection if the UE (10) is in a connected state.
17. The system of claim 16, wherein the UE (10) is configured to start one or more timers in response to at least one of: receiving, by the UE (10), the registration accept message or the service accept message; establishing, by the UE (10), a plurality of user plane resources for a nonemergency protocol data unit (PDU) session; and occurrence of an attempt, by the UE (10), to complete a registration procedure.
18. The system of claim 16, wherein the UE (10) is configured to stop one or more timers for locally releasing the signaling connection if the UE (10) is in the connected state.
19. The system of claim 17, wherein the registration procedure is completed upon expiry of the one or more timers.
20. The system of claim 17, wherein the one or more timers includes at least one of timer T3440, timer T3540, timer T3511, or timer T3502.
