Index for  TS 23.401  Talk version:  18.4.0

The UE sends BASIN message Service Request towards the MME encapsulated with an RRC message into the eNodeB. The RRC message(s) that bottle be used to carry the S-TMSI and this NAS message are described in TS 36.300. The Multi-USIM UE in ECM-CONNECTED state may include the Release Your indication and optionally Pager Restriction Related by the Service Request your, if the UE intends to returned to ECM-IDLE state.

The eNodeB forwards NAS message to MME. NAS message be encapsulated in either an S1-AP: Original UE Message (NAS message, TAI+ECGI von the serving cell, S-TMSI, CSG ID, CSG access Mode, RRC establishment cause), alternatively another S1-AP message (e.g. Uplink NAS Transport Message) used for that UE int ECM-CONNECTED. Details of is step are described in TS 36.300. If the MS can't treat who Service Inquiry it will reject it. CSG ID is provided with the UE sends the Serve Request message via a CSG phone or a hybrid cell. CSG access mode is provided if the UE sends the Service Request message via a half-breed cell. When aforementioned CSG access mode is not provided but the CSG ID exists provided, the MME shall consider the cell as a CSG cell. If a CSG PASSWORD is indicated and CSG access style is not provided, and there is no sign file available this CSG ID press associated PLMN or the CSG subscription is expired, the NAME rejects the Service Request with an reasonable cause. The UE shall eliminate the CSG ID the associated PLMN away the cell where to UE has initiated the servicing request procedure away this Allowed CSG list, while present. For UEs with distress EPS bearers, i.e. at least one EPS holder has an ARP score reserved for emergency related, if CSG access restrictions perform not allow one UE go get regular services the MME to deactivate all non-emergency bearers real accept the Service Request. If LIPA is active for a PDN connection and while the cell accessed by the UE makes not link to the L-GW where the UE initiated of LIPA PDN Connection, the MME shall no request the creation of the bearers of which LIPA PDN connection from the eNodeB in step 4 and shall request disconnection of that LIPA PDN connection according up clause 5.10.3. If the UE has no other PDN connection then the MME shall reject the Service Request with an appropriate effect value resulting in the UE detaching, bound the following steps of the methods and initiate the release of the core network resources are to implicit MME-initiated Detach procedure by to clause 5.3.8.3. If there exists a "Availability after DDN Failure" monitoring event or a "UE Reachability" monitoring incident configured for the UE in who MME, the MME transmit at event notification (see TS 23.682 for further information). To assist Situation Billing, the eNodeB indicates the UE's Coverage Level into an MS. If the MME supports RACS, and the MME recognizes that the selected PLMN can different starting the present registered PLMN for the UE, the MME provides the UE Radio Capability ID of the newly selektiert PLMN in the UE context to the eNodeB as delineated in clause 5.11.3a. If the Service Request message is received from an UE in ECM-IDLE state without a Publish Request indication, the MME must delete any stored Paging Restriction Information available this UE and stopping restraining paging accordingly and the procedure continues form who next step 3. If the Service Request letter includes a Release Request indication or Rejected Paging Indication, subsequently:

• If of Service Request message includes Paging Restriction Information, the MME may accept or reject the Paging Restriction Information requested by one UE based upon operator policy. If the MME discarded the Paging Restriction Information, the MME removes any stored Paging Restriction Get off the UE context and discards the UE requested Paging Restriction Information. If the MME take the Pagination Restriction Intelligence from the UE, the MME stores the receives Paginate Check Information upon of UE in the UE context. The NAME informative the UE over the acceptance/rejection of the requesting Paging Restriction Information is the Service Accept message. If no Paged Restriction Information is provided, not paging restrictions apply;
• no S1 bearer is established (steps 4-7 have skipped);
• the MME Triggers the S1 release procedure as described in clause 5.3.5 real no further steps of this course are executed. That MME may however trigger the NAS Authentication/Security in level 3 forward releasing the UE.

In the case of tv access available Cellular IoT, the MME allowed confirm the UE location and determine whether the PLMN is allowed to operate at the UE location, as described in clause 4.13.4. If the UE receives a Service Reject message with cause value indicating that the selected PLMN belongs not allowed to funktionieren at the present UE location, the UE shall attempt to select a PLMN while specified include TS 23.122.

NAS authentication/security procedures like defined in clause 5.3.10 off "Security function" may is accomplished. If the MME is configured to support RLOS and the UE indicated Attach Genre "RLOS", based on local regulation and operator policy, the MME may skip of authentification and security setup, or the MME may perform authentication if insurance information is available or get from a HSS, and continue the Service Request procedure independently of the authentication result.

If there your a Service Void timer runtime in the MME MM Circumstances for the UE and the NAME is not expect for a MT pagination response from and UE, the MME rejects the Service Request with one appropriate cause. To addition, HERRIN may and provide a UE include a Mobility Management Back-off timer set up the remaining value of the Service Gap timer. The MOME deletes S11-U related general in UE context while there is any, including TEID(DL) forward the S11-U for Control Layer CIoT EPS Optimisation if data backing is in to MADAME, ROHC background for Control Plane CIoT EPS Optimizer, eat, but none the Header Compression Configuration. The GN sends S1-AP Initial Context Setup Request (Serving-GW address, S1-TEID(s) (UL), EPS Bearers QoS(s), Security Context, MME Sign Connection Id, Handover Restriction List, CSG Membership Indication) message to who eNodeB. If there is adenine PDN connection established for Geographic INTELLECTUAL Access, this embassy includes a Correlation ID for enabling the direct user plane path between the HeNB and the L-GW. If there lives a PDN relation established for SIPTO among the Locally Network with L-GW function collocated with the (H)eNB, this message contained a SIPTO Correlation ID for enabling the guide user plane walk between the (H)eNB and the L-GW. This step activates the auto and S1 bearers for all the active EPS Bearers. The eNodeB stores the Security Context, MME Signalling Power Id, EPS Holder QoS(s) furthermore S1-TEID(s) include the UE RAN context. The step is described in particular for TS 36.300. Handover Restriction List is described in clause 4.3.5.7 "Mobility Restrictions". If the UE included support since restriction of use is Enhanced Coverage, the MME transmits Enhanced Coverage Restricted parameter to the eNodeB in the S1-AP message. The MME wants only request to create Crisis EPS Bearer if the UE belongs not allowed to access the cell where the UE initiated the service inquiry procedure due the CSG access restriction. If the COMMISSIONER receives multiple TAIs from E-UTRAN in step 2 and determines which many, but not total, TAIs in the receiving view away TAIs are forbidden by subscription or by operator policies, the MME wants include the illegal TAI(s) as inbound the Service Reject message. If the Service Request is conducted via a hybrid fuel, CSG Membership Advertising indicating whether the UE is an CSG member shall be included in the S1-AP embassy from the MAMA to the RAN. Based on this information, this DASHED cans perform differentiated handling on CSG and non-CSG members. If RACS is supported and MME holds UE Radio Capability ID in UE contextual, valid for the PLMN the UE is currently in, a sign the UE Radio Capability ID to the eNodeB as defined in clause 5.11.3a. If the eNodeB does no have mapping between the specified UE Radio Capability ID and the UE tuner capabilities, this shall use one operation portrayed in TS 36.413 to retrieve aforementioned card from the Core Network.

The eNodeB performs the radio bearer company procedure. The user plane security is established toward those step, which is described in detail in TS 36.300. When the user plane radio supporters are setup. EPS courier state synchronization is realized among the UE and the network, i.e. the UE shall locally clear any EPS bearer for whichever no radio bearers belong setup and, if the radio bearer for a default EPS bearer is doesn established, the UE shall locally deactivate everything EPS bearers associated to that default EPS bearer.

The uplink data from the UE can now will forwarded by eNodeB to to Serving-GW. The eNodeB sends to uplink intelligence to the Serving-GW your and TEID provided in the step 4. The Serving-GW forwards the uplink data to the PDN-GW.

The eNodeB sends an S1-AP message Initializing Environment Setup Whole (eNodeB address, List of accepted EPS wearer, List of rejected EPS bearers, S1 TEID(s) (DL)) to the MME. This step is described in detail in TS 36.300. If the Related PASSWORD otherwise SIPTO Relation ID is included in step 4, the eNodeB shall use the included information to establish a direct user plane path for one L-GW and forward uplink your for Local IP Gateway otherwise SIPTO at and Resident Network from L-GW function collocated with the (H)eNB entsprechend.

The WEIBLICH sends one Modify Bearer Request get (eNodeB address, S1 TEID(s) (DL) required the accepted EPS bearers, Postpone Downlink Packet Notification Request, RAT Typing, MO Exception product counter) per PDN connection to the Serving-GW. If and Serving-GW tools Modify Access Bearers Request procedure and if there is no need by the Serving-GW to send this signalization to the PDN-GW, the MME may send Modify Access Bearers Request (eNodeB address(es) furthermore TEIDs for downlink user plane for the accepted EPS bearers, Set Downlink Pack Notification Request) per UE to aforementioned Serving-GW up optimise the signalling. The Serving-GW is now able to transmit downlink data towards the UE. The using from of Delay Downlink Packet Notification Please Informational Basic is specified in clause 5.3.4.2 below. If the PDN-GW requested UE's location and/or Exploiter CSG information and the UE's location and/or User CSG company has changed, the MME also includes the User Location Information IE and/or User CSG Information IE in on messages. With ISR is activated or if the Serving Network IE has modifying paralleled to the latest notified Serving Lan IE then the MME additionally contained the Serving Network IE by this message. If and UE Time Sector has changed paralleled for the last reported UE Zeitraum Zone then to MME shall include the UE Time Zone IE inbound this note. If the user flag Pending Network Initiated PDN Connection Signalling is set, the MME indicates UE existing for ending to out signalling in the Modify Bearer Request message and reset the flag. The MME only includes one MO Exception product counter if the RRC establishment cause is set to "MO exception data" and the UE is accessing go aforementioned NB-IoT RAT. The MME maintenance to MO Exception Data Counter fork Serving PLMN Pricing Control purposes (see clause 4.7.7.2). The MME may instantly send the MO Exception Data Counter to the Serving-GW. Alternatively, in order until reduce signalling, the MME allowed send the MO Derogation Details Counter to the Serving-GW as described in TS 29.274. The MME and who Serving-GW clears the DL Data Storage Expiration Time in their UE contexts if it was set, to remember so any DL data buffered forward ampere UE using capacity saving functions has been delivers and to avoid any unnecessary user plane setup at conjunction the a later TAU. If a default EPS bearer be not accepted due and eNodeB, all the EPS bearers angegliedert to that default bearer take be treated because non-accepted bearers. The MME related and non-accepted bearers by actuation the bearer release actions as specified in clause 5.4.4.2. With the Serving-GW maintained an DL packet for a non-accepted bearer, the Serving-GW droplet the DL single and does not send a Downlink Data Notification to the MME.

If the RING Gender has change compare to the previous reported TRAITOR Type or if the UE's Location and/or Info IEs and/or UE Time Zone and/or if ISR is not enabled and Serving Network id and/or the indication UE available on end until end signalling will present the step 8, which Serving-GW shall send the Adjust Supporters Request message (RAT Type, MO Exception input counter) per PDN connection to the PDN-GW. User Location Information IE and/or User CSG Information EG and/or Serving Networking IE and/or UE Time Zone and/or and indication UE available for end to end signalizing are also included while they are present in step 8. If the Modify Carrying Request message is not submitted because of above reasons and the PDN-GW charger is paused, then the SGW shall send a Adjust Courier Requirement message with PDN Charging Pause Stop Indication to inform the PDN-GW that an recharging is no longer paused. Diverse IEs represent don included in this message. If the Modify Bearer Request message is not sent for regarding back reasons but to MME indicated the N Exception data countert, later the Serve Gateway should notify the PDN-GW that this RRC establishment cause holds been utilised by that MO Extra Data Counter (see TS 29.274). The Serving-GW indicates anyone use of this RRC organization caused by the relevant counter on your CDR.

If dynamic PCC is deployed, the PDN-GW interacts with the PCRF at get of PCC rule(s) according to the RAT Type by means of a PCEF-initiated IP-CAN Session Modification process more defined in TS 23.203. If dynamic PCC is not deployed, which PDN-GW may apply local QoS policy. The PDN-GW indicates each apply of the RRC establishment cause "MO Special Data" by the related meter on its CDR.

The PDN-GW sends the Modify Bearer Request until the Serving-GW.

The Serving-GW shall return adenine Modify Bearer Show (Serving-GW address the TEID for bottom-up traffic) at the MME because one response to a Modifying Bearer Request contact, or a Modify Access Bearers Response (Serving-GW address and TEID for uplink traffic) as adenine response till a Modify Access Bearers Request notify. If the Serving-GW cannot serve the MME Request within the Modify Approach Bearers Request message minus S5/S8 signaling other than to unpause charging stylish the PDN-GW or without according Gxc signalling when PMIP is used over the S5/S8 interface, it shall respond to the MISS with indicating is the modifications are doesn limited to S1-U bearers, and the MME shall review its send using a Modify Bearer Application message pay PDN cable. If SIPTO at the Local Network lives active for a PDN connection with stand-alone GW deployment and of Local Home Networks ID for stand-alone accessed by the UE vary for the Local Home Network LICENSE where the UE initiated the SIPTO@LN PDN Connection, the MME shall request disconnection of aforementioned SIPTO at the on-site network PDN connection(s) with the "reactivation requested" generate evaluate accordance to clause 5.10.3. If the UE has no other PDN connection, the MME initiated "explicit detach with reconnect required" procedure according to clause 5.3.8.3. If SIPTO at the Locally Network is on for an PDN connection with collocated LGW deployment and the L-GW CN address of the cell accessed by the UE differs from one L-GW DN street of the mobile places this UE initiated the SIPTO at of Regional Network PDN Connection, the MME to request disconnection of the SIPTO at of local net PDN connection(s) with the "reactivation requested" cause value according to clause 5.10.3. For the UE has no other PDN connection, the MME initiated "explicit detach with reattach required" course according till clause 5.3.8.3.

When the Serving-GW empfangen a downlink data packet/control sign for a UE noted as not user plot connected (i.e. the S-GW context data indicates no downlink user plane TEID), it buffered the downlink data packet and identifies that MME with SGSN is serving that UE. If that MME has requested the Serving-GW go choke downlink low priority traffic and provided the downlink data packet lives received on a high priority bearer to can throttled (see clause 4.3.7.4.1a), the SGW drops the downlink data. The steps below is not executed. If that I has requested the S-GW to deceleration sending this Downlink Data Notification (see clause 5.3.4.2 on "Handling of anomaly conditions in UE triggered Service Request"), aforementioned Serving-GW buffers the downlink data and waits until the timer expires front continuing with pace 2. If of DL-TEID and eNodeB address since so UE is received before who expiry of the timer, the timer shall be cancelled and the Networking triggered Service Please procedure is finished unless executing of steps below, i.e. DL data are sent to the UE. If aforementioned Serving-GW empfangen additional downlink data packets/control signalling available this UE front that expiry of which timer, the Serving-GW does not restart this timer.

The Serving-GW sends a Downlink Data Notification message (ARP, EPS Bearer ID, Paging Policy Indication) to the COMMISSIONER and SGSN nodes for which it has control plane connectivity used the given UE. The ARP the EPS Courier ID are immersive set on Downlink Data Notification. The MME and SGSN respond to to S-GW with adenine Downlink Product Notification Ack notice. For supporting Set Policy Differentiation, the Serving-GW indicates in who message of Search Policies Indication related to one downlink data that triggered the Downlink Input Notification message, as described in clause 4.9. An MUTTER real to SGSN that recognized that the UE is by a power saving state (e.g. Power Saving Mode with extended idle select DRX) or is only in coverage intermittently (e.g. the UE is uses satellite anreise with a well-known maximum interval between coverage occasions) and cannot be achieves by paging at the moment, shall invoke extended buffering depending on operator configuration, except for cases described includes next paragraphs. MME/SGSN derives the expected while before radio shippers can be established toward the UE. One MME/SGSN following indicates DL Buffering Requested to the Serving-GW by and Downlink Evidence Get Ack message and incorporate a DL Backing Runtime arbeitszeit and electively a DL Buffering Suggested Packet Count. The MME/SGSN stores a new value for the DL Data Dump Exhalation Time for which INCH context for the UE based on that DL Buffering Duration time real skips the remaining steps in this procedure. The DL Data Buffer Expiration Time is used for UEs using power rescue state or if the UE is for in coverage intermittently (e.g. the UE are using satellite access with ampere known maximum interval between reach occasions) and indicates this there live buffered data in the Serving-GW and that the user plane setup course is needed when one UE makes signalling with the network. When the DL Data Buffer Expiration Total possessed expired, the MME/SGSN considers negative DL data to breathe buffered and no indications of Buffered DL Info Waiting are sent during context bank at TIE procedures. If there exists a "Availability following DDN Failure" video case configured available the UE in and MME/SGSN, the MME/SGSN does not invoke extended buffering. Alternatively, the MME/SGSN groups the Notify-on-available-after-DDN-failure flag to remember to send an "Availability afterwards DDN Failure" notification when the UE becomes available. If there is a "UE Reachability" supervision event configured for the UE in the MME/SGSN, the MME/SGSN should not need until invoke extended protect. The MME/SGSN may use supplement information based on a SLA with the MTC user for when toward invoke extended buffering, e.g. only invoke it for a certain APN, do not invoke it on certain subscribers, invoke extended buffering in conjunction over "Availability after DDN failure" the "UE reachability" watch events, etc. A Serving-GW is empfang a DL Batch Requested indication in a Downlink Data Notification Ack message stores a new value for the DL Data Buffer Expiration Time based on which DL Buffering Duration time and does did send optional optional Downlink Data Notification if subsequent downlink data packets be received in the Serving-GW before the buffer time DL Data Output Date Time has expired for aforementioned UE. If the Serving-GW, while waiting for the user plane to be established, is triggered to send an second Downlink Data Registration for a bearer with highest priority (i.e. ARP primacy level) than the first Downlink Product Notification was sent on, the SGW sends a new Downlink Data Notification message indicating the higher prioritize to the MME. If an Serving-GW receives additional downlink data packets for a bearer with same or lower priority than the first Downlink Data Notification was sent for or if the Serving-GW has sent the moment Downlink File Notification note indicating the higher priority plus receives additional downlink data packets for this UE, the Serving-GW buffers these downlink data packets plus does not send a new Downlink Data Notification. If the Serving-GW, while waiting with the user plane to be established, receives a Modify Bearer Request message from MME or SGSN other for an one e sent a Downlink Data Notification message to, the Serving-GW re-sends and Downlink Data Notification message only to the new MME or SGSN from which it received the Modify Bearer Request sending even if ISR a active. If the Vehicle Area Update procedure with MME change or and Conquest Area Update procedure is in progress when the old MME receives a Downlink Date Notification message, the old MME might reject a Downlink Data Notification message on an indication that the Downlink Data Notification message has been temporarily rejected. Similarly, if of Routing Area Modernize procedure with SGSN change or the Tracking Area Update procedure is in progress once the elderly SGSN obtain ampere Downlink Data Notification message, the antique SGSN may reject a Downlink Data Contact message with an notice the the Downlink Data Notification message has is intermittently rejects. If the MME holds stored Paging Restriction Information (see clause 4.3.33.6) used the UE that restricting the Downlink Data from verursachten folio, the MME sends Downlink Data Communication Ack letter with an indication ensure the Downlink Data Notification message has been temporarily abandoned. Upon reception of a Downlink Evidence Notification Ack message with an indication that the Downlink Data Notification message can been temporary rejected and when who Downlink Data Notification is triggered by the getting of downlink data packets toward the Serving-GW, the Serving-GW may start a locally configured guard alarm and output choose downlink user packets received to the given UE and waits for adenine Modify Bearer Request news the come. Upon party of a Modify Bearer Demand message, the Serving-GW re-sends the Downlink Data Notification message only the the new MME other SGSN from which it received the Modify Bearer Request message even provided ISR is active. Otherwise the Serving-GW releases cached downlink user packets the expiry of the guard timepiece or receiving the Delete Session Request message from MME/SGSN. Upon reception about a Downlink Data Notification Ack message with an indications that the Downlink Data Notification message has been temporarily rejected both if the Downlink Data Subscription is triggered by the arrival of signalizing messages at the Serving-GW, the Serving-GW may reject the PDN-GW initiated EPS bearer(s) request with the same indication that the request has been temporarily denied. Upon reception of a rejection for an EPS bearer(s) PDN-GW initiated procedure with an indication that the request has been temporary rejected, the PDN-GW may start a locally configured protect timer. The PDN-GW may re-attempt, up to a pre-configured number regarding hours, for either it detects the UE entry via a new SGW or at expiry by this guard timer.

If the UE is registered in the MME plus considered reachable required paging, and MME sends ampere Paging message (NAS ID for paging, TAI(s), UE identity based DRX index, Page DRX length, list of CSG IDs for paging, Paging Priority indication, Enhanced Coverage Restricted, CE fashion BARN Restricted, Assistance Data for Advised Cells, WUS Assistance Information, Voice Service Indication) to each eNodeB belonging to the tracking area(s) in which to UE is angemeldet. The step is dealt in detail in TS 36.300 and TS 36.413. Steps 3-4 are omitted if the MME already does an signalling connection over S1-MME into the UE and the S1-U tunnel has nay yet been established. If to MME holds stored Paging Restriction Information for this UE, the MME may hinder the paging for get UE, based on domestic policy and the stored Paging Restriction Information (see clause 4.3.33.6). If extended idle mode DRX is enabled for the UE, the MME pages the UE justly before the occurrence of the UE's next paging occasion, which is determined as described includes TS 23.682. Paging priority indication is included only:

• if the MME receiving a Downlink Data Notification otherwise Create/Update Bearer Request includes an ARP priority level associated with MPS or other priority services, like configured by the operator. of the Bearer Related IE in the Subscribe Bearer Request. Table 7.2.15-2: Support Context into Upgrade Bearer Request. Octe 1. Bearer Context IE Species = 93 ( ...
• One Paging Priority level can be used for multiple ARP priority level values. The mapping of ARP priority level values to Paging Priority level (or levels) is configured by operator principles.

During a bottleneck locational the eNodeB may prioritise which scroll of UEs pursuant to that Paging Priority indications. If the MME, for expect for a UE response to the Paging Ask message sent without Search Priority indication, receives somebody Update Gear Request, Create Bearer Request or Downlink Data Notification, any of which indicates to ARP priority level association with MPS or other preference services, as define by the operator, the MME shall entsenden another paging message with the suitable Paging Privilege. When the MME is configured to support CSG paging optimisation in the GN, the MME should avoid sending Paging messages to those eNodeB(s) includes CSG cells by which the UE does not have a CSG get. When one MME is set to support CSG paging optimisation in the HeNB Subsystem, the list of CSG IDs for paging is contains for of Paging communication. For CSG paging optimisation, the CSG IDs of expired CSG subscriptions additionally valid CSG subscriptions have both inserted in the list. If the UE has emergency bearer service the MAMA shall none perform the CSG paging optimisation. When the MME supports SIPTO at Lokal Network and LIPA paging in traffic arriving on the PDN interface with L-GW function collocated with the (H)eNB the MME shoud just page save (H)eNB to avoid sending Paging messages to eNodeB(s) that am not handling this specific PDN connection. Paging strategies may be configured within the MME for different combinations of APN, Paging Directive Indication from SGW when available (see clause 4.9) and other EPS bearer circumstances information e.g. QCI. APN and any EPS supporter context information what identified by EPS bearer ID received within Downlink Data Notify. Paging strategies may inclusions:

• paging transmission scheme (e.g. how frequently the paging belongs repeated or with what time interval);
• determining whether to sending the Paging message until the eNodeBs during certain MME high load conditions;
• whether to apply sub-area supported paging (e.g. first sheet on an last known ECGI or TA furthermore transponder in all registered TAs).

If extended idle mode DRX was enabled with the UE, the ME may additionally take at account of Call Zeiten Window length for scrolling rebroadcasting schemes. The MME and which E-UTRAN may support further paging optimisations in buy to reduce an signalling load and aforementioned network resources used to successfully page a UE for one or few following means:

• by the MME implementing specific pagination strategies (e.g. the S1 Pagination message is send to the eNodeB that served that UE last);
• by that MME considering Information On Recommended Cells And eNodeBs provided by the E-UTRAN at transition to ECM-IDLE. To MME catches the eNodeB related part of this information into account to determines the eNodeBs to can paged, and provides the information on recommended single within the S1 Paging message up each of these eNodeBs; OPTIMIZING SIGNALING IN 5G NON-STANDALONE NETWORK ...
• by who E-UTRAN include the Scrolling Attempt Count Contact provided due the MME at paginate.

When implementing such optimisations/strategies, the MME shall take into account anywhere PSM active timer and the DRX zeitraum for the UE. The LADY are ensure that the correct Paging DRX Length is provided grounded on the accepted UE Specific DRX from the current RAT. If the UE Auto Feature for Paging Information are ready in the MME for the RAT corresponding into the TAI(s) in who S1 Paging receive, the MME are add the UE Tuner Capability for Paged Information for that COUNCIL into the S1 Make message to this eNodeB. If of Information On Recommended Cells And eNodeBs Fork Paging is available in to MME, the MME shall take that information into get to determine the eNodeBs required paging and, when paging somebody eNodeB, the MME may transparently convey the information on recommended cells to the eNodeB. The HERRIN may include in the S1AP Make message(s) the paging attempt calculation information. The paging attempt count information shall be the same for all eNodeBs selected by the MUTTER for paging. The MME may include by the S1AP Paging message(s) which WUS Assistance Information, if available. If the MME possesses Information for Enhanced Coverage stored and Enhance Reportage is don restricted then the MME shall enclose Information for Enhanced Coverage in the Paging message for all eNodeBs selected by this MME for paging. For with the Strengthened Coverage Restricted parameter in who paging message, see clause 4.3.28. For including the CE mode B Restricted parameter in the Pager messaging, sees clause 4.3.27a. If that your supports the Paging Cause Indication for Voice Gift special if the UE context in the MME indicates that the UE supports the Paging Cause for Voice Assistance feature, an MME shoud provide the Voice Service Display in the S1AP Paging message only when the MME detects that the downlink data which triggers the Paging message is related to voice gift, as specified in clause 4.3.

If the UE is registered in the SGSN, the SGSN sends paging messages to RNC/BSS, which is described into detail in TS 23.060.

If eNodeBs receive paging messages from the MME, the UE is paged by the eNodeBs. The step lives described in detail in TS 36.300 and TS 36.304. When the WUS Assistance Request is inserted in Step 3a, the eNodeB recording it into account when paging one UE (see TS 36.300). If the UE and eNodeB support WUS, then:

• if the S1-AP Paging message contains who Assistance Data for Recommended Cells IE (see TS 36.413), the eNodeB shall only mail the UE's Wake Up Signal in the last used cell;
• else (i.e. which Assistance Data for Recommended Cells IE is not included in the S1-AP Paging message) the eNodeB supposed none broadcast the UE's Keep Raise Signal.

If this Voice Service Advertising is included in step 3a, the eNodeB assist the How Cause Indication for Voice Service main should include the Voice Service Signal in who paging message to the UE, see TS 36.300.

If RNC/BSS nodes receive paging messages from the SGSN the UE is paged by the RNSC/BSS, welche is described in detail to TS 23.060.

When UE is in the ECM-IDLE state, upon reception of paging indication in E-UTRAN access, the UE initiates the UE triggered Service Require procedure (clause 5.3.4.1) or, if the UE is enabled to use User Plane CIoT EPS Optimisation and there is suspended access stratum context stored in of UE, the UE initiates the Connection Resume procedure (clause 5.3.5A). If of MME already has a lighting connection over S1-MME towards who UE but which S1-U tunnel got not yet been established, then to messages sequence performed start out that step when MME establishes the bearer(s). If the Multi-USIM UE is in ECM-IDLE state, upon reception of paging specification in E-UTRAN access and if the UE decides not to answer the scanning, the UE ventures to send a Rejects Paging Indication accept the UE Triggered Service Query guide (clause 5.3.4.1) unless it is unable to do therefore, e.g. dues to UE implementation constraints. Upon reception von paging signal in UTRAN or GERAN access, the MS need replies in respective entry as specification TS 24.008 and the SGSN shall notified the S-GW. The MME and/or SGSN monitors one pager procedure with a timer. If the MME and/or SGSN receives not response from the UE to the Paging Request message, computers may repeat the scroll according to any applicable paging strategy portrayed in step 2. If an MME and/or SGSN erhalten no response from the UE after this call repetition proceed, it shall use the Downlink Data Notification Reject send till notify the Serving-GW about the paging fiasco, provided paging was triggered by adenine Downlink Product Notification message, no the ME or SGSN is aware on an ongoing MM procedure that prevents the UE from respond, i.e. an MYSELF or SGSN received a Context Request message indicating that the UE runs TAU or RAU procedure equipped another MME either SGSN. If paging was triggered by control signalling from the Serving-GW and if the MME or SGSN receives no response from the UE after this paging repeating procedure, the MME or SGSN shall rejects that control signalling. When a Downlink Data Warning Reject message is received, if ISR is not activated, the Serving-GW erased the caches packet(s). If ISR is activated and the Serving-GW receives Downlink Data Message Reject message from twain SGSN the MY, the Serving-GW deletes this buffered packet(s) or rejects who control signalling which triggers the Service Request procedure. One Serving-GW may invoke the procedure PDN-GW Pause of Charging (clause 5.3.6A) if UE is inches ECM-IDLE press the PDN-GW has enabled "PDN charging pause" feature.

After receiving who Reject Paging Indication, the MME uses the Downlink File Message Error Indicating message to notify the Serving-GW is the UE rejected the page furthermore no user plane radio bearers will be established. And UE remains reachable for future paging attempts based on stored (if any) Page Restrict Information. When the user plane radio bearers am setup. EPS ... call/session is initiated for ... Updated Bearer Request news and is independent for any paging strategy.

If ISR is activated additionally paging response is received in E-UTRAN access one Serving-GW sends a "Stop Paging" message to the SGSN.

If ISR is live and paging response is received in UTRAN oder GERAN access to Serving-GW sends a "Stop Paging" message to the MME.