EP3858005A1 - Systems and methods for notification and acquisition of mobile network public warnings in connected mode for coverage enhanced user equipment - Google Patents

Abstract

Systems, methods, and devices provide for notification and acquisition of public warning system (PWS) information by user equipment in connected mode. The PWS information may include, for example, earthquake and tsunami warning system (ETWS) and/or commercial mobile alert system (CMAS). The user equipment may include non-bandwidth reduced low complexity (non-BL) user equipment operating in coverage enhanced mode.

Description

SYSTEMS AND METHODS FOR NOTIFICATION AND ACQUISITION OF MOBILE NETWORK PUBLIC WARNINGS IN CONNECTED MODE FOR COVERAGE

ENHANCED USER EQUIPMENT

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 62/737,503, filed September 27, 2018, U.S. Provisional Application No. 62/824, 149, filed March 26, 2019, and U.S. Provisional Application No. 62/884,051, filed August 7, 2019, each of which is hereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

[0002] This application relates generally to wireless communication systems, and more specifically to mobile network public warning systems.

BACKGROUND

[0003] Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless mobile device. Wireless communication system standards and protocols can include the 3rd Generation Partnership Project (3GPP) long term evolution (LTE); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly known to industry groups as worldwide

interoperability for microwave access (WiMAX); and the IEEE 802.11 standard for wireless local area networks (WLAN), which is commonly known to industry groups as Wi-Fi. In 3GPP radio access networks (RANs) in LTE systems, the base station can include a RAN Node such as a Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and/or Radio Network Controller (RNC) in an E-UTRAN, which communicate with a wireless communication device, known as user equipment (UE). In fifth generation (5G) wireless RANs, RAN Nodes can include a 5G Node, new radio (NR) node or g Node B (gNB).

[0004] RANs use a radio access technology (RAT) to communicate between the RAN Node and UE. RANs can include global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and/or E-UTRAN, which provide access to

communication services through a core network. Each of the RANs operates according to a specific 3GPP RAT. For example, the GERAN implements GSM and/or EDGE RAT, the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3 GPP RAT, and the E-UTRAN implements LTE RAT.

[0005] A core network can be connected to the UE through the RAN Node. The core network can include a serving gateway (SGW), a packet data network (PDN) gateway (PGW), an access network detection and selection function (ANDSF) server, an enhanced packet data gateway (ePDG) and/or a mobility management entity (MME).

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0006] FIG. 1 illustrates a timing diagram in accordance with one embodiment.

[0007] FIG. 2 illustrates a timing diagram in accordance with one embodiment.

[0008] FIG. 3 illustrates a MAC control element command in accordance with one embodiment.

[0009] FIG. 4 illustrates a MAC control element command in accordance with one embodiment.

[0010] FIG. 5 illustrates a variable MAC control element command in accordance with one embodiment.

[0011] FIG. 6 illustrates a system in accordance with one embodiment.

[0012] FIG. 7 illustrates a device in accordance with one embodiment.

[0013] FIG. 8 illustrates an example interfaces in accordance with one embodiment.

[0014] FIG. 9 illustrates a system in accordance with one embodiment.

[0015] FIG. 10 illustrates components in accordance with one embodiment.

DETAILED DESCRIPTION

[0016] Objectives for enhanced machine type communication (eMTC) may include extreme coverage for non-bandwidth reduced low complexity (non-BL) user equipment (UE). Desired coverage enhanced (CE) mode A and B improvements for non-BL UEs earthquake and tsunami warning system (ETWS) and/or commercial mobile alert system (CMAS) in connected mode.

[0017] Non-BL UEs operating in bandwidth reduced (BR)/CE mode are not required to monitor the UE-specific search space (USS) and common search space (CSS) machine type communication physical downlink control channel (MPDCCH) (type-l and type-2) simultaneously when in connected mode. Therefore, such UEs do not monitor for MPDCCH with cyclical redundancy check (CRC) scrambled with paging radio temporary identifier (P- RNTI) to receive any paging message or direct indication of system information (SI) update or public warning system (PWS) messages (e.g., ETWS/CMAS) in connected mode.

Currently, if a wireless network wants to send the ETWS/CMAS notification to ETEs operating in CE mode, then the network releases all the UEs to IDLE mode and sends the notification using direct indication message in MPDCCH with CRC scrambled with P-RNTI in the paging occasion (PO). After receiving the notification, the UE has to acquire the latest system information block (SIB) type 10 (SIB10), SIB type 11 (SIB 11), and/or an SIB type 12 (SIB 12). This method may incur additional signaling overhead, delay, radio resources, and UE power consumption in receiving the notification. It may also disrupt unicast traffic. On the other hand, non-BL UEs are capable of receiving paging message in connected mode when operating in non-coverage enhanced (non-CE) or wideband (WB) mode.

[0018] In connected mode, non-BL UEs in CE may monitor MPDCCH to receive an ETWS indication and/or a CMAS indication using CSS in the same narrowband where unicast transmission can be received. Under this assumption, it is feasible for a non-BL UE in CE in connected mode to monitor MPDCCH to receive an ETWS indication and/or a CMAS indication using Type 0 CSS in the same narrowband where unicast transmission can be received. It is also feasible for a non-BL UE in CE in connected mode to monitor USS and Type 0 CSS simultaneously in the same narrowband. Type 0 CSS may also be supported in CE mode B.

[0019] Embodiments described and disclosed herein may be directed to downlink control information (DCI), radio resource control (RRC) and medium access control (MAC) control element based techniques, methods, procedures, apparatus, or implementations for

ETWS/CMAS notification and its acquisition (or system information update

notification/acquisition) in connected mode. In addition, or in other embodiments, details are provided for on connected mode discontinuous reception (C-DRX) state and monitoring CSS in PO and the UE’s action after acquisition of DCI for ETWS/CMAS notification and the system information for ETWS/CMAS notification. In certain embodiments, BL UEs or UEs in CE initiate RRC re-establishment procedure after the acquisition of ETWS/CMAS information.

[0020] Bandwidth reduced low complexity (BL) UEs or UEs in CE are not required to monitor packet data convergence protocol (PDCCP) with P-RNTI to detect any system information change or receive any ETWS/CMAS notification. So DCI, RRC and MAC control element based options for this purpose are provided for BL UEs or UEs in CE to acquire the ETWS/CMAS information. [0021] Certain embodiments described herein may be applicable to both BL UEs and non

BL UEs in connected mode. The embodiments described herein may also applicable to provide system information change/update and/or EAB parameter change/update notification or acquisition in connected mode.

[0022] Processes to consider for UEs in connected mode include processes to receive the ETWS/CWAS notification, processes to acquire the ETWS/CWAS information, and processes after acquisition of the ETWS/CMAS information.

[0023] 1 Example ETWAS/CMAS Notification Embodiments

[0024] In IDLE mode, a UE monitors physical downlink control channel (PDCCH) scrambled with P-RNTI to receive the ETWS/CMAS notification. In RRC CONNECTED, the following options are provided according to certain embodiments. The options may also applicable to provide any system information change notification and/or system information contents in connected mode.

[0025] 1 1 Dedicated signaling for ETWS/CMAS notification

[0026] 1.1(a) Unicast MPDCCH: A new DCI format or updated legacy DCI format (DCI formats 6-1A, 6-1B) may be used to either directly indicate the PWS notification (e.g., by defining new or re-interpreting existing DCI bit-fields), or to schedule a PDSCH to carry the PWS notification.

[0027] 1.1(b) Unicast physical downlink shared channel (PDSCH): A new or updated RRC message or MAC control element can be used for the ETWS/CMAS notification. This notification can be implicit (e.g., if the actual RRC msg or MAC control element already carries the ETWS/CMAS information itself) or explicit (e.g., conveying an indication for the UE to acquire SIB 10/11/12 or conveying the scheduling information of SIB 10/11/12 for the UE to acquire them).

[0028] In certain embodiments for dedicated signaling for ETWS/CMAS notification, the network (NW) does not need to wait for paging occasion to send the notification (i.e., faster notification to the UE). Thus, legacy UE behavior may not be impacted (as the UE does not require to receive broadcast signal when in connected mode). The network sends the same information (i.e., ETWS/CMAS notification) to each UE operating in CE mode A and B (as a dedicated mechanism is used).

[0029] 1 2 Broadcast signaling for ETWS/CMAS notification

[0030] 1.2(a) Broadcast MPDCCH: Use P-RNTI or other cell-specific RNTI with possible impact to DCI format. A new DCI format may be used to indicate the scheduling

information of particular SI messages to be acquired by the UE. Alternatively, as further described herein, the UE may be configured by higher layers to monitor for DCI formats 6- 1A or 6-1B with CRC scrambled with P-RNTI for MPDCCH candidates starting at subframes and in narrow bands (NBs) corresponding to the paging occasions (POs) and paging NBs (PNBs) respectively. Such configuration may be defined as monitoring of MPDCCH candidates as per Type-l CSS for MPDCCH or as mentioned below, be defined as extension of currently defined Type-0 CSS for MPDCCH.

[0031] In certain embodiments for dedicated signaling for ETWS/CMAS notification, a group of ETEs can be notified at the same time. A new DCI format may be used to indicate the scheduling information of SI. However, additional complexity may be introduced because a non-BL EGE in CE may need to perform additional blind decoding (BD) trials of MPDCCH scrambled e.g. with P-RNTI (i.e., the UE also monitors CSS in RRC-Connected mode). However, for non-BL UEs, performing a few additional few BD trials (for type-2 CSS) in CE mode may not be major issue. Some optimization may also be performed to avoid the additional BD trials, for example, monitoring only MPDCCH scrambled with P- RNTI at a certain POs.

[0032] In certain embodiments, the paging may be monitored in all POs or one PO per paging discontinuous reception (DRX) cycle, or at least one PO in a paging DRX cycle or at least one PO in a given period. In another embodiment, a new DCI format or update of existing DCI format for type-0 CSS can also be defined.

[0033] 1 3 Checking ETWS/CMAS notification for DRX mode

[0034] As discussed above, there are different options to notify a non-BL UE in CE mode and RRC CONNECTED about the ETWS/CMAS information to come. The working assumption is that (if it is feasible from RAN1 point of view) UE can monitor the CSS and UE-specific search space (USS) in the same unicast narrowband and the notification can be scheduled in the CSS.

[0035] As in legacy LTE, a UE may be able to monitor the P-RNTI in any paging occasion (PO) at least once in a paging DRX cycle, which may introduce the least interruption to the unicast message. The network can set the appropriate value of parameter nB such that there is no overlapping of paging repetitions over multiple POs. For example, if T is equal to l28rf and parameter nB is set to T/64, then there are two POs in a DRX cycle. The network would need to schedule such notification in CSS in both POs to notify all UEs. Therefore, the UE may have freedom to monitor the second PO of the DRX cycle in case the UE would have unicast activity during the first PO of the DRX cycle, e.g., a HARQ RTT timer would be running or the UE would be in DRX sleep. [0036] If the UE is using connected mode DRX, the PO and the ON duration boundary may not be aligned. It is possible that the UE would be in a DRX sleep where PO falls. It is possible that during PO, the UE’s DRX timers (e.g., HARQ RTT timer,

drxRetransmissionTimer) are running. It should be possible for the UE to select a PO to monitor CSS where it would be in DRX active time.

[0037] In certain embodiments, if every available PO in a paging DRX cycle falls on the DRX sleep time, the UE may wakeup to monitor the CSS in one PO and if there is nothing scheduled, the UE may continue its DRX state without impacting the DRX timers. If the UE finishes monitoring the CSS in a PO and the UE would still be in DRX sleep, the UE may go back to the DRX sleep state.

[0038] It is possible that some UEs are operating in CE mode B. Therefore, the network may transmit the DCI for ETWS/CMAS notification considering the worst coverage level that is being used by a UE in RRC CONNECTED. For example, if there are no UEs operating in CE mode B, then the DCI can be transmitted with repetition corresponding to CE mode A.

[0039] In another embodiment, the DCI scheduling on the PO restarts the RRC inactivity timer in the network.

[0040] In another embodiment, the network aligns the connected mode DRX cycle ON duration boundary with a PO of the paging DRX cycle.

[0041] In another embodiment, the UE may be required to check the ETWS/CMAS notification (e.g., CSS) only once during the connected mode DRX cycle. In such

embodiments, the UE may still sleep and when it wakes up, the UE makes sure it checks the CSS at least once.

[0042] 2 Example ETWAS/CMAS Information Acquisition Embodiments

[0043] For non-BL UEs operating in CE mode and connected mode, embodiments herein send and acquire the ETWS/CMAS information. In certain embodiments, if SIB 10/1 1/12 are to be acquired, the UE may not have up to date SI scheduling information (as a UE in CE is not required to have up to date master information block (MIB)/SIB(s)).

[0044] 2 1 Acquire broadcast SIB 10/ 11/12

[0045] 2.1(a) Certain embodiments follow a procedure to acquire latest scheduling of SIB 10/11/12 and acquire the information. The ETWS/CMAS notification may be conveyed via any of the mechanism described in section 2.1 (e.g, 1.1(a), 1.1(b), 1.2). [0046] In certain such embodiments, a UE acquires the MIB and system information block (SIB) type 1 bandwidth reduced (SIB 1-BR) because the UE may not be aware of the change in system information and may not have the updated schedule of SIB 10/1 1/12. This could take a long time which is not desirable when in connected mode.

[0047] 2.1(b) Certain embodiments use scheduling information of SIB 1-BR or

SIB10/11/12 provided by unicast (see 1.1(b)) or broadcast notification (see 1.2(a)). In certain such embodiments, ETWS/CMAS notification itself provides the scheduling information of SIB 10/11/12 (e.g., narrowband, periodicity and TBS size) or SIB1-BR, and the UE saves power by avoiding the acquisition of MIB and SIB1-BR or MIB only.

[0048] 2 2 Acquire copy of SIB 10/11/12

[0049] 2.2(a) Unicast: RRC message or MAC control element (new or updated) provides the ETWS/CMAS information e.g. including SIB 10/11/12. in certain such embodiments, there is no need to have explicit ETWS/CMAS notification (1.1(b) via implicit mechanism).

[0050] 2.2(b) Broadcast: New or updated broadcast message (e.g., paging-like message class extension, Si-like message). An advantage of defining a copy of SIB10/11/12 is that the information could potentially be sent in any narrowband which could help for parallel unicast transmissions. The ETWS/CMAS notification may be conveyed via any of the mechanism described in section 2.1 (e.g., 1.1(a), 1.1(b), 1.2).

[0051] In certain embodiments, the network provides a separate copy of SIB 10/11/12 in unicast or broadcast PDSCH scheduled by either broadcast signaling or dedicated signaling with legacy gap between physical downlink control channel (PDCCH) and PDSCH. The broadcast PDSCH (with P-RNTI or other RNTI) can be scheduled at the beginning of a notification period. However, if the PDCCH monitoring and PDSCH broadcast are in different narrowband, the UE does not monitor the PDCCH at the beginning of the notification period even if no broadcast PDSCH is scheduled.

[0052] In certain embodiments, the UE acquires the ETWS/CMAS information directly receiving the scheduled PDSCH reducing the acquisition delay. The network sends a separate copy of information to UEs in IDLE mode and non-BL UEs in CE in connected mode.

[0053] 23. Additional example embodiments for receiving ETWS/CMAS information

[0054] As mentioned above, for a non-BL UE operating in CE mode in connected mode, if ETWS/CMAS notification is received in CSS, different options can be considered to acquire the ETWS/CMAS information. The legacy procedure would be to acquire the MIB in PBCH to receive the scheduling information of SIB1-BR which in turn provides the scheduling information of SIB10/11/12 as UE may not be aware of the change in system information.

[0055] The PBCH for UEs in enhanced coverage is also broadcast in the central 72 carriers as in LTE and are independent of the narrowband allocated to ETEs. This could add interruption to unicast and power consumption. If ETWS/CMAS notification itself can provide the scheduling information of SIB 10/11/12 (e.g., narrowband, periodicity and TBS size) or SIB1-BR, the UE can save power by avoiding the acquisition of MIB and SIB 1-BR or MIB only. However, deciding what information can be provided in the DCI in CSS may depend on the design of DCI for ETWS/CMAS notification.

[0056] Therefore, in certain embodiments, a simple solution is that the DCI includes just 1 bit (i.e., a single bit) indication to inform the UE that scheduling information of SIB1-BR is the same or unchanged at least over the SI validity time, or alternatively to indicate when there is a change in the scheduling information of SIB1-BR. A benefit is that the UE can re- use the same scheduling information that was provided in the MIB at least over the SI validity time, as scheduling information may change rarely. In this case, the UE may skip acquiring MIB and save power. Table 1 provides an example of DCI content for

ETWS/CMAS notification. Table 2 provides an example of DCI content for ETWS/CMAS notification with random access (RA) backoff.

TABLE 1

[0057] Table 2 provides an example of DCI content for ETWS/CMAS notification with random access (RA) backoff.

TABLE 2

[0058] 2.4 Example embodiments when a UE starts acquisition of ETWS/CMAS

information

[0059] In certain embodiments, the network needs to know when the LTE in

RRC CONNECTED starts acquiring the corresponding SIB, as this would mean that the LTE may not be able to receive LTE-specific signaling and/or data. In one such embodiment, the network knows this implicitly e.g. based on when the network starts sending the

corresponding SI notification for ETWS/CMAS. It can be based on the scheduling of corresponding SI message or SIB1-BR or MIB after the scheduling of the notification in the first associated PO of the LTE or after the end of the DRX cycle where the first notification is scheduled in a PO for the LTE. In other embodiments, the LTE informs the network when the LTE plans to start acquiring the ETWS/CMAS corresponding SI messages. Different mechanism may be enabled for the LTE to provide this information, for example, via: uplink (LTL) RRC signaling using existing messages such as LTE Assistance (where a new indication could be defined for this) or defining a new RRC message related to bandwidth part (BWP) operation; LTL MAC control element using existing one, such as BSR, or new one, such as BWP operating related one; and/or layer 1 (Ll) Ll signaling (e.g., new uplink control information (UCI) design or using existing LTCI in physical uplink control channel (PLTCCE1) or piggybacked on physical uplink shared channel (PLTSCE1)).

[0060] The signaling mentioned above may include just an indication that it started or it may include a time or gap after which it intends to acquire the system information. The signaling may be just an indication that it will acquire the next scheduled system

information. The same message can also be used to indicate success or failure of acquisition. [0061] In one embodiment, the network can also send a response message (e.g., PDCCH scheduling PDSCH) if there is any higher priority downlink (DL) traffic e.g., for emergency services.

[0062] In one embodiment, the UL message can also be used to start a timer configured by the network (either in RRC signaling or system broadcast). In one such embodiment, the timer can be started from the location of corresponding SI message or SIB1-BR or MIB or paging occasion (PO) after the scheduling of the notification in the first associated PO of the UE or after the end of the DRX cycle where the first notification is scheduled in a PO for the UE. The timer may indicate an estimated time the EGE may take to acquire the corresponding SI message. If the EGE cannot finish acquisition of the SI message within this timer, the EGE uses random access or RRC re-establishment or new RRC connection establishment procedure to let the network know it finished the acquisition. In another embodiment, the network can release the EGE and the EGE can go to IDLE mode after the expiry of the timer. But as long as the timer is running, the UE’s resources are kept and the UE is in

RRC CONNECTED.

[0063] In another embodiment, the timer is used to synchronize between the UE and the network regarding entering the RRC IDLE state. When the UE receives the ETWS/CMAS notification, the UE can go to RRC IDLE state or IDLE while keeping the UE context, but the network waits until the timer expires to release the UE’s context or just release the UE’s resource keeping UE’s context. In one embodiment, the network temporarily suspends the UE but keeps the UE in RRC CONNECTED. While the timer is running, the UE cannot send/receive any unicast message as the network may be re-using the UE’s resource for other purposes. The UE either can wait to expire the timer to send an UL message or start a random access procedure (RACH) or RRC reestablishment to resume the unicast with the network. In one embodiment, the network sends RRC signaling or a Timing Advance Command MAC control element (assuming the UE is out of sync) to resume the unicast after the expiry of the timer. In another embodiment, the UE sends an indication in an UL message using its resources.

[0064] If the network does not hear anything from the UE or if the network does not receive any response after scheduling the DL message or transmission of the DL message fails, the network releases the UE. In one embodiment, the network can start a new RRC release timer after scheduling the DL message (e.g., RRC message).

[0065] After the acquisition of the SI message, the UE can again send the same indications mentioned above (e.g., Ll signaling) to let the network know it is ready for unicast transmission or indication of success/failure of acquisition of the SI message if the timer is still running.

[0066] In one embodiment, the UE may miss to receive the ETWS/CMAS notification scheduled in a DRX cycle and receive the ETWS/CMAS notification in X>= 1 DRX cycle.

It may also miss the notification and use the PETCCE1 resource to send some ETL signal or use the configured ETL assignment to send UL data. In this case, the network can wait e.g., for a next X >= 1 paging DRX cycle or start a timer to release the UE’s resource and keep the UE’s context or to release completely to RRC IDLE. If the UE sends some UL signal or message after the network has already sent the ETWS/CMAS notification, the network may release the UE to RRC IDLE or suspend the UE to IDLE or send ETWS/CMAS information or just notification using dedicated signaling.

[0067] 3 Example Embodiments for After Acquisition of ETWAS/CMAS Information Acquisition

[0068] When a UE receives the notification of ETWS/CMAS in connected mode, the UE may be performing unicast transmission/reception or be scheduled for the unicast transmission/reception. However, the network may not know exactly when the UE would be able to finish receiving the ETWS/CMAS information and resume unicast. Therefore, a mechanism is needed so that the network does not waste resource for the UE or

unnecessarily delay any DL transmission for too long. Also, after the acquisition of the SI message or if UE fails to acquire the intended SI message, the UE and the network may be out of sync or timing advance (TA) information may be invalid.

[0069] A possible way to address the problems is for all the UEs receiving notification (some operating in CE mode A and others in CE mode B) go to IDLE mode autonomously and acquire the ETWS/CMAS information following legacy procedure. However, this procedure has drawbacks. Going into IDLE could be even more costly as any pending UL/DL data would be lost as UE would have to start new RRC connection and eNB will delete the UE’s context. Another disadvantage is that many UEs can try to initiate the random access procedure at the same time to continue transmission of the pending UL data worsening the congestion and wasting power. Therefore, going into IDLE mode would not be beneficial unless some mechanism to handle the RACH congestion and recover the unacknowledged data.

[0070] In one embodiment, the UE signals the network that it finished obtaining the ETWS/CMAS information and is ready for unicast transmission/reception. If there is any ongoing or scheduled unicast transmission/reception, the UE can resume the unicast with or without indicating that the UE finished receiving ETWS/CMAS information.

[0071] The indication can be sent using dedicated RRC message or a MAC control element. In other embodiments, the UE can send a scheduling request (SR), any quality channel indicator (CQI) or sounding reference signal (SRS) report, hybrid automatic repeat request (HARQ) feedback, or any new signal on PUCCH as an indication. While receiving the ETWS/CMAS, the UE can also indicate to the network to pause any ongoing or scheduled transmission.

[0072] In one embodiment, the UE can prioritize receiving of system information of ETWS/CMAS over unicast. In another embodiment, an expected window (e.g., SI modification window) can be defined. If there is no activity from the time the UE receives the notification of ETWS/CMAS and the expected window expires, the UE may go to IDLE mode or the network can release the the UE to IDLE mode.

[0073] In one embodiment, if the UE receives RRC connection release message while acquiring the ETWS/CMAS information, the UE can follow but the UE also completes the acquisition of ETWS/CMAS.

[0074] In certain embodiments, receiving the ETWS/CMAS does not impact the connected mode DRX procedure.

[0075] In another embodiment, when the UE finishes the acquisition of ETWS/CMAS information, the UE may initiate the RRC connection re-establishment procedure similar to the case when UE goes to radio link failure (RLF). In this case, the network may provide a backoff indicator in the DCI during ETWS/CMAS notification such that random access congestion can be minimized. An example is shown in Table 2. The network can also keep the UE’s context and any unacknowledged DL data. However, the network can release any reserved resource (e.g., PUCCH, SRS and SPS resource) as it can be re-configured in Msg4 (. RRCConnectionReestablishment message). In one embodiment, the eNB does not ask the MME to release the UE’s Sl-U or Sl l-U connection and they are maintained. In another embodiment, the eNB can initiate the UE release procedure to the MME.

[0076] In one embodiment, the UE follows a legacy procedure to initiate the RRC re- establishment procedure (e.g., cell (re) selection). The cell (re) selection process can also be skipped. Access barring can be applicable. In another embodiment, the UE does not check access barring to initiate the RRC re-establishment. In another embodiment, the UE assumes it is synchronized with the serving cell and uses the common configuration to initiate the RACH. In another option, the UE makes sure it has valid MIB and system information before initiating the RRC connection or RRC reestablishment procedure.

[0077] In another embodiment, after going to IDLE keeping the EGE context to acquire the intended SI message, the EGE finishes the acquisition and initiates the RRC re-establishment procedure using a legacy procedure. This may resume the RRC connection and recover any pending ETL/DL transmission.

[0078] In one embodiment, the EGE initiates random access but sends cell RNTI (C-RNTI) MAC control element and buffer status report (BSR) MAC control element, or only C-RNTI MAC control element, in the ETL grant received in a random access response (RAR) (e.g., in Msg3) to resume the RRC connection with the eNB. In Msg4, the EGE receives PDCCH addressed to the C-RNTI that can schedule ETL/DL assignments for any pending DL/UL data or any RRC reconfiguration message. In one embodiment, if the non BL UE is using control plane (CP) cellular internet of things (C-IoT) evolved packet system (EPS)/5GS

optimization, it can initiate the RRC re-establishment procedure defined for narrow band internet of things (NB-IoT).

[0079] In another embodiment, the network does not know when the UE would become reachable and the same procedure is applied as if the UE goes to RLF (e.g., the network does not release the UE’s resources until the data inactivity timer expires).

[0080] In one embodiment, in the UL message to the network, the UE also indicates indication of success/failure of acquisition of the SI message. In case of failure, the network may schedule the notification or SI message for the UE using dedicated signaling.

[0081] For RRC re-establishment, a spare value in reestablishment cause or 1 spare bit in RRCConnectionReestablishmentRequest-r8-IEs can be used to indicate (e.g., success- ETWS-CMAS-rl6) that the UE is performing reestablishment after finishing the acquisition of ETWS/CMAS from RRC connected mode. For example:

RRCConnectionReestablishmentRequest-r8-IEs : := SEQUENCE {

ue-Identity ReestabUE-Identity,

reestablishmentCause ReestablishmentCause,

success-ETWS-CMAS-rl6 BOOLEAN,

spare BIT STRING (SIZE (1))

[0082] In another embodiment, the UE follows the same procedure as if

timeAlignmentTimer expired. This time can be considered expired either from the time of ETWS/CMAS notification or when ETWS/CMAS acquisition is complete. After the acquisition of SIB 10/11/12, the UE may be listening to MPDCCH (or PDCCH) to receive any Timing Advance Command MAC control element.

[0083] In another embodiment, the UE is moved to a suspended state after the

ETWS/CMAS notification.

[0084] 4 Example Embodiments for Acquiring Broadcast PDSCH

[0085] FIG. 1 is a timing diagram 100 illustrating example broadcast PDSCH based ETWS/CMAS information acquisition according to one embodiment. In this example, a copy of SIB 10/11/12 in PDSCH with the encoded bits scrambled with P-RNTI or other RNTI are scheduled by an eNB at the beginning of ETWS/CMAS notification period in connected mode. A new period for monitoring the broadcast PDSCH can be defined or existing modification period or SI periodicity can also be used. At the subframe starting the period, UEs (e.g., shown as UE1 and UE2) try to decode the PDSCH with the encoded bits scrambled with P-RNTI or other RNTI with high priority. Already scheduled unicast PDSCH transmission may be scheduled at the subframe, as shown in FIG. 1.

[0086] In another embodiment, a UE can monitor and receive the PDCCH with the CRC scrambled with P-RNTI or a new broadcast RNTI and the scheduled PDSCH in the same or different narrowband simultaneously at this subframe. Furthermore, the UE may also receive unicast transport block (TB) and broadcast TB at same or different narrowband

simultaneously at this subframe. Note that receiving DL physical channels over different NBs simultaneously may be feasible for non-BL UEs in CE mode due to their inherent RF and baseband capability to operate in systems with up to 20 MHz system bandwidth (BW). The resource configuration for such PDSCH (e.g., narrowband, periodicity, TB size, repetitions) can be configured by dedicated RRC signaling or broadcast in SI.

[0087] FIG. 2 is a timing diagram 200 illustrating example broadcast PDSCH based ETWS/CMAS information acquisition with notification according to one embodiment.

Legacy PO 202 are shown with PDCCH with P-RNTI (broadcast), wherein a UE (e.g., UE1 or UE2) may be required to monitor at least one PO 202 in NP. FIG. 2 also shows PDSCH 204 scrambled with P-RNTI (broadcast), wherein the UEs that receive notification search the PDSCH 204 to receive it. This can be a new paging message or RRC reconfiguration message or MAC control element. If notification is provided, the eNB schedules the PDSCH comprising SIB 10/11/12 for ETWS/CMAS at the beginning of the next NP or as schedule by PDCCH. A copy of SIB 10/11/12 in PDSCH can be scheduled in a broadcast way after receiving notification at a PO. The UE can monitor PDCCH in all POs or one PO per paging DRX cycle or at least one PO in a paging DRX cycle or at least one PO in a given period for the notification.

[0088] In one embodiment, options to schedule the broadcast PDSCH may include:

broadcast PDSCH is sent in a fixed NB x; broadcast PDSCH is sent in a NB configured by RRC or broadcast in SI; PDCCH indicates which NB to use for broadcast PDSCH; broadcast PDSCH is scheduled in each narrowband so UE is required to decode it in the same NB; periodicity (or new notification period), TBS size or repetitions are predefined or configured via RRC or broadcast in system information; and SIB10 and/or SIB11 and/or SIB12 are used.

[0089] In one embodiment, options to notify the presence of broadcast PDSCH include: a new PHY signal (similar to WUS) is defined to indicate presence of broadcast PDSCH; DCI in paging occasion indicates presence of broadcast PDSCH; dedicated signaling (PDCCH in UESS or RRC message or MAC CE) indicates the presence of broadcast PDSCH; DCI or new paging message or RRC message or MAC CE provides scheduling information of SIB1- BR or SIB10/11/12 as indication; and broadcast PDSCH is dynamically scheduled with SI- RNTI or P-RNTI or other cell specific RNTI.

[0090] In one embodiment, options to decode the broadcast PDSCH include: broadcast PDSCH is prioritized over unicast transmission; UE receives both TBs in unicast and broadcast PDSCH from the same NB; and NB switching gap is defined for parallel reception of unicast PDSCH and broadcast PDSCH.

[0091] 5 Example Embodiments of DCI Design for ETWS/CMAS

Notification/ Acquisition

[0092] In certain embodiments, various DCI design options may be considered.

[0093] One embodiment uses existing DCI formats (6-1A, 6-1B) scrambled with C-RNTI (for unicast DCI based notification).

[0094] One embodiment uses a new DCI format scrambled with C-RNTI (new unicast DCI based notification to provide at least 5 bits information for SIB 1-BR scheduling or scheduling of SIB 10/11/12).

[0095] One embodiment uses existing DCI format 6-2 scrambled with P-RNTI/ or new RNTI (for broadcast DCI based notification with both flag 0 and flag 1).

[0096] One embodiment uses new DCI scrambled with P-RNTI/ or new RNTI (new broadcast DCI based notification to provide at least additional 5 bits for SIB 1-BR

scheduling). This DCI format can be based on DCI format 6-2 with the direct information flag bit-field assumed enabled and the remaining bits in the DCI format used for direct indication including any information on SIB1-BR scheduling or SIB 10/11/12 scheduling.

[0097] For example, the DCI format 6-2 when flag = 0 for direct indication has reserved bits available which can be used to provide the SIB 1-BR scheduling information or

SIB 10/11/12 scheduling information as shown below.

[0098] One embodiment includes scheduling SIB1-BR. For example, Table 3 shows reserved bit in DCI format 6-2 when flag = 0 for paging direct indication.

TABLE 3

[0099] One embodiment includes optional scheduling SIB1-BR. In this embodiment, a flag is used to indicate whether the following bits are used for scheduling information of SIB1- BR. This flag = 1 could also mean that there is some change in the scheduling information of SIB1-BR. For example, Table 4 shows reserved bit in DCI format 6-2 when flag = 0 for paging direct indication.

TABLE 4 [0100] On embodiment includes an indication of whether SIB 1-BR scheduling has changed or not at least over the SI validity time. If the UE is synchronized (e.g., in connected mode), it does not require to re-synchronize. Therefore, the UE just needs the scheduling

information of SIB1-BR if it has changed. If the indication is true, it indicates that no change has occurred in the scheduling information of SIB1-BR message at least over the SI validity time so the UE can assume the stored scheduling information of SIB-BR as valid and use it to acquire the SIB 1-BR. If the UE does not have stored scheduling information, then it can acquire the MIB. For example, Table 5 shows reserved bit in DCI format 6-2 when flag = 0 for paging direct indication.

TABLE 5

[0101] Table 6 shows another example reserved bit in DCI format 6-2 when flag = 0 for paging direct indication.

TABLE 6

[0102] 6. Example Embodiments for Minimizing Blind Decoding (BD) Efforts at the UE

[0103] Certain embodiments are provided to minimize the impact on complexity and power consumption from additional BD efforts for the LTEs to additionally monitor for MPDCCH in connected mode.

[0104] In one embodiment, the LTE is not expected to monitor for MPDCCH with CRC scrambled with C-RNTI during subframes starting from a PO in which the LTE is expected to monitor DCI w/ P-RNTI. However, this can be too restrictive and, especially when using larger numbers of repetitions, adversely impact scheduling ability for the LTE in connected mode.

[0105] One embodiment limits the additional number of BDs for monitoring MPDCCH carrying DCI format 6-2 with CRC scrambled with P-RNTI. Following this approach, the existing number of BD candidates in a Type-l MPDCCH CSS for paging of four candidates with different numbers of repetitions may be reduced by allowing the LTE to monitor a subset of the possible set of candidates (based on Rmax for paging CSS) based on one or more of: the configured CE mode, Rmax of MPDCCH LTESS, Rmax of Type 1 MPDCCH CSS for paging, etc.).

[0106] One embodiment defines a new variant of DCI formats 6-1A/6-1B that, when the CRC is scrambled with P-RNTI (instead of C-RNTI) carries PWS (and possibly SI update) related information. This implies no increase in the BD efforts for the non-BL LTEs (and certain such embodiments may be supported for BL LTEs). However, the down-side is that the network may now need to transmit both DCI formats 6-2 and the 6-1A/6-1B considering mix of Idle and different Connected mode LTEs in the cell/tracking area for each PO. For DCI format 6-2, for the use case of only PWS notification, as one option, the header bit field could be removed or fixed to always indicate“direct indication”.

[0107] 7 Example Embodiments for Design of RRC Message Based Implementation

[0108] In certain embodiments, an RRC reconfiguration message can be used to provide SIB1-BR and additionally can provide that the signaling schedule for SIB 10 or SIB 11 or SIB12 is also provided and the LTE acquires the ETWS and/or CMS information. An example is shown below: RRCConnectionReconfiguration-vl5 l0-IEs : := SEQUENCE {

nr-Config-rl5 CHOICE {

release NULL,

setup SEQUENCE {

endc-ReleaseAndAdd-rl5 BOOLEAN,

nr-SecondaryCellGroupConfig-r 150CTET STRING OPTIONAL, - Need ON p-MaxEUTRA-r 15 P-Max OPTIONAL - Need ON

}

} OPTIONAL, - Need ON sk-Counter-rl 5 INTEGER (0.. 65535) OPTIONAL, - Need ON nr-RadioBearerConfigl-rl5 OCTET STRING OPTIONAL, - Need ON nr-RadioBearerConfig2-rl 5 OCTET STRING OPTIONAL, - Need ON tdm-PatternConfig-rl5 CHOICE {

release NULL,

setup SEQUENCE {

subframeAssignment-rl 5 SubframeAssignment-r 15,

harq-Offset-rl5 INTEGER (0.. 9)

}

} OPTIONAL, — Cond FDD-PCell nonCriticalExtension RRCConnectionReconfiguration-vl6xy-IEs OPTIONAL

}

RRCConnectionReconfiguration-vl6xy-IEs : := SEQUENCE {

notificationETWS-CMAS-r 16 ENUMERATED {true} OPTIONAL, - Cond SIB1-BR nonCriticalExtension SEQUENCE } } OPTIONAL

}

OR

RRCConnectionReconfiguration-vl6xy-IEs : := SEQUENCE {

notificationETWS-CMAS-r 16 ENUMERATED {ETWS, CMAS} OPTIONAL, - Cond SIB1-BR

nonCriticalExtension SEQUENCE } } OPTIONAL

[0109] Table 7 shows various corresponding parameters.

TABLE 7

[0110] Table 8 shows corresponding field descriptions.

TABLE 8

[0111] The RRC reconfiguration message can also be used to provide the container which includes the contents of SIB 10 or SIB 11 or SIB 12. For example:

RRCConnectionReconfiguration-vl6xy-IEs : := SEQEENCE {

systemlnformationBlockTypelOorl lorl2Dedicated-rl 1 OCTET STRING

(CONTAINING SystemlnformationBlockTypelO or SystemlnformationBlockTypel 1 or SystemInformationBlockTypel2) OPTIONAL, — Need ON

nonCriticalExtension SEQUENCE { } OPTIONAL

}

OR

RRCConnectionReconfiguration-vl6xy-IEs : := SEQUENCE {

systemlnformationBlockTypelOorl lorl2Dedicated-rl 1 OCTET STRING

(CONTAINING SystemlnformationBlockTypelO or SystemlnformationBlockTypel 1 or SystemlnformationBlockTypel 2) OPTIONAL, — Need ON

nonCriticalExtension SEQUENCE { } OPTIONAL

}

[0112] Table 9 shows corresponding field descriptions.

TABLE 9

[0113] As another example:

RRCConnectionReconfiguration-vl6xy-IEs : := SEQEENCE {

systemlnformationBlockTypelOorl lorl2Dedicated SEQEENCE {

systemlnformationBlockTypelODedicated-rl 1 OCTET STRING (CONTAINING Sy stemlnformati onBlockType 10) OPTIONAL, — Need ON

sy stemlnformati onBlockTypel lDedicated-rl 1 OCTET STRING (CONTAINING Sy stemlnformati onBlockTypel 1) OPTIONAL, — Need ON

systemInformationBlockTypel2Dedicated-rl 1 OCTET STRING (CONTAINING SystemInformationBlockTypel2) OPTIONAL, — Need ON

} OPTIONAL,- Need ON

nonCriticalExtension SEQUENCE { } OPTIONAL

}

[0114] Table 10 shows corresponding field descriptions.

TABLE 10

[0115] In another embodiment, the scheduling information of SIB 10 or SIB 11 and or SIB 12 can be provides as follows:

RRCConnectionReconfiguration-vl6xy-IEs : := SEQUENCE {

shedulingInfoList-BR-rl6 SchedulingInfoList-BR-rl6 OPTIONAL,— Need ON

nonCriticalExtension SEQUENCE ! } OPTIONAL

}

SchedulinglnfoLi st-BR-r 16 ::= SEQUENCE (SIZE (1..3)) OF SchedulingInfo-BR-rl6 Schedulinglnfo-BR-r 16 : := SEQUENCE {

si-Periodicity-rl6 ENUMERATED {

rf8, rfl6, rf32, rf64, rfl28, rf256, rf 512},

sib-MappingInfo-rl6 SIB-MappingInfo-rl6,

si -N arrowb and-r 16 INTEGER ( 1.. max Avai 1N arrowB ands-rl3),

si-TBS-rl6 ENUMERATED {bl52, b208, b256, b328, b408, b504, b600, b7l2, b808, b936}

}

SIB-Mappinglnfo-r 16 : := SEQUENCE (SIZE (0..3)) OF SIB-Type-rl6

SIB-Type-rl6 : := ENUMERATED (sibTypelO, sibTypel l, sibTypel2-v920} [0116] 8. Example Embodiments for Design of MAC Control Element Based Implementation

[0117] In certain embodiments, a new MAC control element can be used to provide scheduling information of SIB1-BR and additionally can provide that the signaling schedule for SIB10 or SIB 11 or SIB12 is also provided and the UE acquires the ETWS and/or CMS information. For example, FIG. 3 illustrates a MAC control element command 300 according to one embodiment to provide SIB1-BR scheduling (e.g., using 5 bits).

[0118] In one embodiment, scheduling information of SIB 10/1 1/12 may also be indicated in the MAC control element. For example, FIG. 4 illustrates a MAC control element command 400 according to one embodiment to provide scheduling information of SI comprising SIB 10/11/12 as indicated by bitmap "SIB 11/12/13".

[0119] As another example, FIG. 5 illustrates a variable MAC control element command 500 to provide scheduling information of SIB10, SIB11 and SIB 12 as indicated by bitmap "SIB11/12/13". Note that the variable MAC control element command 500 may be of fixed size of 6 octets without bitmap "SIB 11/12/13".

[0120] For this purpose, a new logical channel identifier (LCID) or enhanced LCID (eLCID) may be used. For example, Table 11 shows values of LCID for DL-SCH with ETWS/CMAS notification according to one embodiment.

TABLE 11

[0121] Table 12 shows values of eLCID for DL-SCH with ETWS/CMAS notification according to one embodiment.

TABLE 12

[0122] Example Systems and Apparatuses

[0123] FIG. 6 illustrates an architecture of a system 600 of a network in accordance with some embodiments. The system 600 is shown to include a UE 602; a 5G access node or RAN node (shown as (R)AN node 608); a User Plane Function (shown as UPF 604); a Data Network (DN 606), which may be, for example, operator services, Internet access or 3rd party services; and a 5G Core Network (5GC) (shown as CN 610).

[0124] The CN 610 may include an Authentication Server Function (AUSF 614); a Core Access and Mobility Management Function (AMF 612); a Session Management Function (SMF 618); a Network Exposure Function (NEF 616); a Policy Control Function (PCF 622); a Network Function (NF) Repository Function (NRF 620); a Unified Data Management (UDM 624); and an Application Function (AF 626). The CN 610 may also include other elements that are not shown, such as a Structured Data Storage network function (SDSF), an Unstructured Data Storage network function (UDSF), and the like.

[0125] The UPF 604 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to DN 606, and a branching point to support multi-homed PDU session. The UPF 604 may also perform packet routing and forwarding, packet inspection, enforce user plane part of policy rules, lawfully intercept packets (UP collection); traffic usage reporting, perform QoS handling for user plane (e.g. packet filtering, gating, UL/DL rate enforcement), perform Uplink Traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in the uplink and downlink, and downlink packet buffering and downlink data notification triggering. UPF 604 may include an uplink classifier to support routing traffic flows to a data network. The DN 606 may represent various network operator services, Internet access, or third party services.

[0126] The AUSF 614 may store data for authentication of UE 602 and handle

authentication related functionality. The AUSF 614 may facilitate a common authentication framework for various access types.

[0127] The AMF 612 may be responsible for registration management (e.g., for registering UE 602, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. AMF 612 may provide transport for SM messages for the SMF 618, and act as a transparent proxy for routing SM messages. AMF 612 may also provide transport for short message service (SMS) messages between UE 602 and an SMS function (SMSF) (not shown by FIG. 6). AMF 612 may act as Security Anchor Function (SEA), which may include interaction with the AUSF 614 and the UE 602, receipt of an intermediate key that was established as a result of the UE 602 authentication process. Where USIM based authentication is used, the AMF 612 may retrieve the security material from the AUSF 614. AMF 612 may also include a Security Context Management (SCM) function, which receives a key from the SEA that it uses to derive access-network specific keys. Furthermore, AMF 612 may be a termination point of RAN CP interface (N2 reference point), a termination point of NAS (NI) signaling, and perform NAS ciphering and integrity protection.

[0128] AMF 612 may also support NAS signaling with a UE 602 over an N3 interworking -function (IWF) interface. The N3IWF may be used to provide access to untrusted entities. N3IWF may be a termination point for the N2 and N3 interfaces for control plane and user plane, respectively, and as such, may handle N2 signaling from SMF and AMF for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking taking into account QoS requirements associated to such marking received over N2. N3IWF may also relay uplink and downlink control-plane NAS (NI) signaling between the UE 602 and AMF 612, and relay uplink and downlink user-plane packets between the UE 602 and UPF 604. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 602.

[0129] The SMF 618 may be responsible for session management (e.g., session

establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation & management (including optional Authorization); Selection and control of UP function; Configures traffic steering at UPF to route traffic to proper destination; termination of interfaces towards Policy control functions; control part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI System);

termination of SM parts of NAS messages; downlink Data Notification; initiator of AN specific SM information, sent via AMF over N2 to AN; determine SSC mode of a session. The SMF 618 may include the following roaming functionality: handle local enforcement to apply QoS SLAs (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI System); support for interaction with external DN for transport of signaling for PDU session

authorization/authentication by external DN.

[0130] The NEF 616 may provide means for securely exposing the services and

capabilities provided by 3 GPP network functions for third party, internal exposure/re exposure, Application Functions (e.g., AF 626), edge computing or fog computing systems, etc. In such embodiments, the NEF 616 may authenticate, authorize, and/or throttle the AFs. NEF 616 may also translate information exchanged with the AF 626 and information exchanged with internal network functions. For example, the NEF 616 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 616 may also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information may be stored at the NEF 616 as structured data, or at a data storage NF using a standardized interfaces. The stored information can then be re-exposed by the NEF 616 to other NFs and AFs, and/or used for other purposes such as analytics.

[0131] The NRF 620 may support service discovery functions, receive NF Discovery Requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 620 also maintains information of available NF instances and their supported services.

[0132] The PCF 622 may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behavior. The PCF 622 may also implement a front end (FE) to access subscription information relevant for policy decisions in a ETDR of ETDM 624.

[0133] The ETDM 624 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of EGE 602.

The UDM 624 may include two parts, an application FE and a ETser Data Repository (UDR). The UDM may include a UDM FE, which is in charge of processing of credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing; user identification handling; access authorization; registration/mobility management; and subscription management. The UDR may interact with PCF 622 . UDM 624 may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously.

[0134] The AF 626 may provide application influence on traffic routing, access to the Network Capability Exposure (NCE), and interact with the policy framework for policy control. The NCE may be a mechanism that allows the 5GC and AF 626 to provide information to each other via NEF 616, which may be used for edge computing

implementations. In such implementations, the network operator and third party services may be hosted close to the UE 602 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC may select a UPF 604 close to the UE 602 and execute traffic steering from the UPF 604 to DN 606 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 626. In this way, the AF 626 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 626 is considered to be a trusted entity, the network operator may permit AF 626 to interact directly with relevant NFs.

[0135] As discussed previously, the CN 610 may include an SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE 602 to/from other entities, such as an SMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF 612 and UDM 624 for notification procedure that the UE 602 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 624 when UE 602 is available for SMS).

[0136] The system 600 may include the following service-based interfaces: Namf:

Service-based interface exhibited by AMF; Nsmf: Service-based interface exhibited by SMF; Nnef: Service-based interface exhibited by NEF; Npcf: Service-based interface exhibited by PCF; Nudm: Service-based interface exhibited by UDM; Naf: Service-based interface exhibited by AF; Nnrf: Service-based interface exhibited by NRF; and Nausf: Service-based interface exhibited by AUSF.

[0137] The system 600 may include the following reference points: Nl : Reference point between the UE and the AMF; N2: Reference point between the (R)AN and the AMF; N3 : Reference point between the (R)AN and the UPF; N4: Reference point between the SMF and the UPF; and N6: Reference point between the UPF and a Data Network. There may be many more reference points and/or service-based interfaces between the NF services in the NFs, however, these interfaces and reference points have been omitted for clarity. For example, an NS reference point may be between the PCF and the AF; an N7 reference point may be between the PCF and the SMF; an Nl 1 reference point between the AMF and SMF; etc. In some embodiments, the CN 610 may include an Nx interface, which is an inter-CN interface between the MME and the AMF 612 in order to enable interworking between CN 610 and other core networks.

[0138] Although not shown by FIG. 6, the system 600 may include multiple RAN nodes (such as (R)AN node 608) wherein an Xn interface is defined between two or more (R)AN node 608 (e.g., gNBs and the like) that connecting to 5GC 410, between a (R)AN node 608 (e.g., gNB) connecting to CN 610 and an eNB, and/or between two eNBs connecting to CN 610.

[0139] In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality. The Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE 602 in a connected mode (e.g., CM-CONNECTED) including functionality to manage the EGE mobility for connected mode between one or more (R)AN node 608. The mobility support may include context transfer from an old (source) serving (R)AN node 608 to new (target) serving (R)AN node 608; and control of user plane tunnels between old (source) serving (R)AN node 608 to new (target) serving (R)AN node 608.

[0140] A protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-EG layer on top of a ETDP and/or IP layer(s) to carry user plane PDETs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is built on an SCTP layer. The SCTP layer may be on top of an IP layer. The SCTP layer provides the guaranteed delivery of application layer messages. In the transport IP layer point-to-point transmission is used to deliver the signaling PDETs. In other implementations, the Xn-ET protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.

[0141] FIG. 7 illustrates example components of a device 700 in accordance with some embodiments. In some embodiments, the device 700 may include application circuitry 702, baseband circuitry 704, Radio Frequency (RF) circuitry (shown as RF circuitry 720), front- end module (FEM) circuitry (shown as FEM circuitry 730), one or more antennas 732, and power management circuitry (PMC) (shown as PMC 734) coupled together at least as shown. The components of the illustrated device 700 may be included in a UE or a RAN node. In some embodiments, the device 700 may include fewer elements (e.g., a RAN node may not utilize application circuitry 702, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device 700 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

[0142] The application circuitry 702 may include one or more application processors. For example, the application circuitry 702 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 700. In some embodiments, processors of application circuitry 702 may process IP data packets received from an EPC.

[0143] The baseband circuitry 704 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 704 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 720 and to generate baseband signals for a transmit signal path of the RF circuitry 720. The baseband circuitry 704 may interface with the application circuitry 702 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 720. For example, in some embodiments, the baseband circuitry 704 may include a third generation (3G) baseband processor (3G baseband processor 706), a fourth generation (4G) baseband processor (4G baseband processor 708), a fifth generation (5G) baseband processor (5G baseband processor 710), or other baseband processor(s) 712 for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 704 (e.g., one or more of baseband processors) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 720. In other embodiments, some or all of the functionality of the illustrated baseband processors may be included in modules stored in the memory 718 and executed via a Central Processing Unit (CPU 714). The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 704 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 704 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[0144] In some embodiments, the baseband circuitry 704 may include a digital signal processor (DSP), such as one or more audio DSP(s) 716. The one or more audio DSP(s) 716 may include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 704 and the application circuitry 702 may be implemented together such as, for example, on a system on a chip (SOC).

[0145] In some embodiments, the baseband circuitry 704 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 704 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), or a wireless personal area network (WPAN).

Embodiments in which the baseband circuitry 704 is configured to support radio

communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0146] The RF circuitry 720 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 720 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. The RF circuitry 720 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 730 and provide baseband signals to the baseband circuitry 704. The RF circuitry 720 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 704 and provide RF output signals to the FEM circuitry 730 for transmission.

[0147] In some embodiments, the receive signal path of the RF circuitry 720 may include mixer circuitry 722, amplifier circuitry 724 and filter circuitry 726. In some embodiments, the transmit signal path of the RF circuitry 720 may include filter circuitry 726 and mixer circuitry 722. The RF circuitry 720 may also include synthesizer circuitry 728 for synthesizing a frequency for use by the mixer circuitry 722 of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 722 of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 730 based on the synthesized frequency provided by synthesizer circuitry 728. The amplifier circuitry 724 may be configured to amplify the down-converted signals and the filter circuitry 726 may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 704 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, the mixer circuitry 722 of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0148] In some embodiments, the mixer circuitry 722 of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 728 to generate RF output signals for the FEM circuitry 730. The baseband signals may be provided by the baseband circuitry 704 and may be filtered by the filter circuitry 726.

[0149] In some embodiments, the mixer circuitry 722 of the receive signal path and the mixer circuitry 722 of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 722 of the receive signal path and the mixer circuitry 722 of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 722 of the receive signal path and the mixer circuitry 722 may be arranged for direct

downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 722 of the receive signal path and the mixer circuitry 722 of the transmit signal path may be configured for super-heterodyne operation.

[0150] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 720 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 704 may include a digital baseband interface to communicate with the RF circuitry 720.

[0151] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0152] In some embodiments, the synthesizer circuitry 728 may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 728 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0153] The synthesizer circuitry 728 may be configured to synthesize an output frequency for use by the mixer circuitry 722 of the RF circuitry 720 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 728 may be a fractional N/N+l synthesizer.

[0154] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 704 or the application circuitry 702 (such as an applications processor) depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 702.

[0155] Synthesizer circuitry 728 of the RF circuitry 720 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0156] In some embodiments, the synthesizer circuitry 728 may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 720 may include an IQ/polar converter.

[0157] The FEM circuitry 730 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 732, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 720 for further processing. The FEM circuitry 730 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 720 for transmission by one or more of the one or more antennas 732. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 720, solely in the FEM circuitry 730, or in both the RF circuitry 720 and the FEM circuitry 730.

[0158] In some embodiments, the FEM circuitry 730 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry 730 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 730 may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 720). The transmit signal path of the FEM circuitry 730 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by the RF circuitry 720), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 732).

[0159] In some embodiments, the PMC 734 may manage power provided to the baseband circuitry 704. In particular, the PMC 734 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 734 may often be included when the device 700 is capable of being powered by a battery, for example, when the device 700 is included in a EGE. The PMC 734 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

[0160] FIG. 7 shows the PMC 734 coupled only with the baseband circuitry 704. However, in other embodiments, the PMC 734 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, the application circuitry 702, the RF circuitry 720, or the FEM circuitry 730.

[0161] In some embodiments, the PMC 734 may control, or otherwise be part of, various power saving mechanisms of the device 700. For example, if the device 700 is in an

RRC Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 700 may power down for brief intervals of time and thus save power.

[0162] If there is no data traffic activity for an extended period of time, then the device 700 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 700 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device 700 may not receive data in this state, and in order to receive data, it transitions back to an RRC Connected state.

[0163] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

[0164] Processors of the application circuitry 702 and processors of the baseband circuitry 704 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 704, alone or in combination, may be used to execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 702 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

[0165] FIG. 8 illustrates example interfaces 800 of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 704 of FIG. 7 may comprise 3G baseband processor 706, 4G baseband processor 708, 5G baseband processor 710, other baseband processor(s) 712, CPU 714, and a memory 718 utilized by said processors. As illustrated, each of the processors may include a respective memory interface 802 to send/receive data to/from the memory 718.

[0166] The baseband circuitry 704 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 804 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 704), an application circuitry interface 806 (e.g., an interface to send/receive data to/from the application circuitry 702 of FIG. 7), an RF circuitry interface 808 (e.g., an interface to send/receive data to/from RF circuitry 720 of FIG. 7), a wireless hardware connectivity interface 810 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 812 (e.g., an interface to send/receive power or control signals to/from the PMC 734.

[0167] FIG. 9 is a block diagram illustrating components, according to some example embodiments, of a system 900 to support NFV. The system 900 is illustrated as including a virtualized infrastructure manager (shown as VIM 902), a network function virtualization infrastructure (shown as NFVI 904), a VNF manager (shown as VNFM 906), virtualized network functions (shown as VNF 908), an element manager (shown as EM 910), an NFV Orchestrator (shown as NFVO 912), and a network manager (shown as NM 914).

[0168] The VIM 902 manages the resources of the NFVI 904. The NFVI 904 can include physical or virtual resources and applications (including hypervisors) used to execute the system 900. The VIM 902 may manage the life cycle of virtual resources with the NFVI 904 (e.g., creation, maintenance, and tear down of virtual machines (VMs) associated with one or more physical resources), track VM instances, track performance, fault and security of VM instances and associated physical resources, and expose VM instances and associated physical resources to other management systems.

[0169] The VNFM 906 may manage the VNF 908. The VNF 908 may be used to execute EPC components/functions. The VNFM 906 may manage the life cycle of the VNF 908 and track performance, fault and security of the virtual aspects of VNF 908. The EM 910 may track the performance, fault and security of the functional aspects of VNF 908. The tracking data from the VNFM 906 and the EM 910 may comprise, for example, performance measurement (PM) data used by the VIM 902 or the NFVI 904. Both the VNFM 906 and the EM 910 can scale up/down the quantity of VNFs of the system 900.

[0170] The NFVO 912 may coordinate, authorize, release and engage resources of the NFVI 904 in order to provide the requested service (e.g., to execute an EPC function, component, or slice). The NM 914 may provide a package of end-user functions with the responsibility for the management of a network, which may include network elements with VNFs, non-virtualized network functions, or both (management of the VNFs may occur via the EM 910).

[0171] FIG. 10 is a block diagram illustrating components 1000, according to some example embodiments, able to read instructions from a machine-readable or computer- readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 10 shows a diagrammatic representation of hardware resources 1002 including one or more processors 1012 (or processor cores), one or more memory/storage devices 1018, and one or more communication resources 1020, each of which may be communicatively coupled via a bus 1022. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1004 may be executed to provide an execution environment for one or more network slices/sub- slices to utilize the hardware resources 1002. [0172] The processors 1012 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 1014 and a processor 1016.

[0173] The memory/storage devices 1018 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 1018 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM),

Flash memory, solid-state storage, etc.

[0174] The communication resources 1020 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1006 or one or more databases 1008 via a network 1010. For example, the communication resources 1020 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.

[0175] Instructions 1024 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1012 to perform any one or more of the methodologies discussed herein. The instructions 1024 may reside, completely or partially, within at least one of the processors 1012 (e.g., within the processor’s cache memory), the memory/storage devices 1018, or any suitable combination thereof. Furthermore, any portion of the instructions 1024 may be transferred to the hardware resources 1002 from any combination of the peripheral devices 1006 or the databases 1008. Accordingly, the memory of the processors 1012, the memory/storage devices 1018, the peripheral devices 1006, and the databases 1008 are examples of computer-readable and machine-readable media.

[0176] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the Example Section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

[0177] Example Section

[0178] The following examples pertain to further embodiments.

[0179] Example 1 is an apparatus for a user equipment (EGE). The apparatus includes a memory interface and a baseband processor. The memory interface to send or receive, to or from a memory device, data corresponding to downlink control information (DCI). The baseband processor to: monitor a common search space (CSS) of a machine-type

communications (MTC) physical downlink control channel (MPDCCH) for scheduling of a physical downlink shared channel (PDSCH) in a wireless network, wherein to monitor the CSS includes to decode a DCI transmission, wherein a cyclic redundancy check (CRC) portion of the DCI transmission is scrambled with a radio temporary identifier (RNTI) configured to indicate a notification of a public warning system (PWS) message in connected mode; in response to the notification of the PWS message, acquire the PWS message from broadcast system information; and generate an indication to the wireless network of completion of acquiring the PWS message, wherein the indication signals that the EGE is ready new unicast communications with the wireless network.

[0180] Example 2 is the apparatus of Example 1, wherein the EGE is a non-bandwidth reduced low complexity (non-BL) EGE configured for operation in coverage enhanced (CE) mode.

[0181] Example 3 is the apparatus of Example 2, wherein a format of the DCI transmission comprises a DCI format 6-1A or a DCI format 6-1B with the RNTI corresponding to notification of at least one of an earthquake and tsunami warn system (ETWS) and a commercial mobile alert system (CMAS).

[0182] Example 4 is the apparatus of Example 3, wherein the RNTI comprises a paging RNTI (P-RNTI).

[0183] Example 5 is the apparatus of Example 4, wherein the EGE is configured by higher layers to monitor for the DCI format 6-1 A or the DCI format 6-1B with the CRC scrambled with the P-RNTI for MPDCCH candidates start at subframes and in narrowbands (NBs) corresponding to paging occasions (POs) and paging narrowbands (PNBs), respectively. [0184] Example 6 is the apparatus of Example 4, wherein the DCI format 6-1 A or the DCI format 6-1B with the CRC scrambled with the P-RNTI further comprises system information (SI) update related information.

[0185] Example 7 is the apparatus of Example 1, wherein acquiring the PWS message from broadcast system information comprises: decode a master information block (MIB) and a system information block (SIB) type 1 bandwidth reduced (SIB1-BR) to determine an updated schedule of an SIB type 10 (SIB10), an SIB type 11 (SIB11), and an SIB type 12 (SIB 12); and decode one or more of the SIB 10, the SIB1 1, and the SIB 12 to acquire the PWS message.

[0186] Example 8 is the apparatus of Example 1, wherein the notification of the PWS message comprises schedule information of a system information block (SIB) type 10 (SIB 10), an SIB type 11 (SIB 11), and an SIB type 12 (SIB 12), or the notification of the PWS message comprises scheduling information of an SIB type 1 bandwidth reduced (SIB1- BR) to determine an updated schedule of the SIB 10, the SIB11, and the SIB 12, and wherein acquiring the PWS message from broadcast system information comprises decoding one or more of the SIB 10, the SIB 11, and the SIB 12 to acquire the PWS message.

[0187] Example 9 is the apparatus of Example 1, wherein the DCI comprises a single bit configured to indicate whether or not schedule information of a system information block (SIB) type 1 bandwidth reduced (SIB1-BR) has changed at least over a system information (SI) validity time, and wherein acquiring the PWS message from broadcast system information comprises: if the single bit indicates that no change has occurred in the scheduling information of the SIB 1-BR at least over the SI validity time, use the scheduling information to decode one or more of an SIB type 10 (SIB10), an SIB type 11 (SIB11), and an SIB type 12 (SIB 12) to acquire the PWS message; and if the single bit indicates that a change has occurred in the scheduling information of the SIB1-BR, decode a master information block (MIB) and the SIB 1-BR determine an updated schedule for the SIB 10, the SIB 11, and the SIB 12 to acquire the PWS message.

[0188] Example 10 is the apparatus of Example 1, wherein to generate the indication comprises to generate one of a dedicated radio resource control (RRC) message, a media access control (MAC) control element, a scheduling request (SR), a quality channel indicator (CQI) report, a sounding reference signal (SRS) report, hybrid automatic repeat request (HARQ) feedback, and a new signal on a physical uplink control channel (PETCCE1). [0189] Example 11 is the apparatus of Example 1, wherein the baseband processor is further configured to request the wireless network to pause ongoing or scheduled unicast transmissions to the EGE while the EGE is acquiring the PWS message.

[0190] Example 12 is the apparatus of Example 1, wherein to generate the indication comprises to initiate a radio resource control (RRC) connection re-establishment procedure.

[0191] Example 13 is the apparatus of Example 12, wherein the baseband processor is further configured to generate an RRC connection re-establishment request comprising a single bit to indicate that the EGE is performing the RRC connection re-establishment after acquiring the PWS message from RRC connected mode.

[0192] Example 14 is the apparatus of Example 1, wherein to generate the indication comprises to initiate a random access procedure wherein the EGE sends at least one of a cell RNTI (C-RNTI) media access control (MAC) control element and a buffer status report (BSR) MAC control element in an uplink grant received in a random access response (RAR) to resume an RRC connection with a node in the wireless network.

[0193] Example 15 is the apparatus of Example 1, wherein the EGE is configured to operate in a discontinuous reception (DRX) in the connected mode, and wherein available page occasions (POs) in a paging DRX cycle occur during a DRX sleep state, wherein the baseband processor is further configured to: wake up the EGE to monitor the CSS in a first PO; if the PDSCH is not scheduled in the first PO, continue a current DRX state without modifying one or more DRX timers; and if monitor the CSS is completed in the first PO and the EGE should still be in a DRX sleep state according to the paging DRX cycle, return the EGE to the DRX sleep state.

[0194] Example 16 is the apparatus of Example 1, wherein the EGE is configured to operate in a discontinuous reception (DRX) in the connected mode, wherein the baseband processor is further configured to check the CSS for the notification of the PWS message once during a connected mode DRX cycle, and wherein the EGE does not check the CSS during a DRX sleep state.

[0195] Example 17 is a method for communicating a public warning system (PWS) message in a wireless network. The method includes: encoding downlink control

information (DCI) for broadcast in an MTC physical downlink control channel (MPDCCH), wherein a cyclic redundancy check (CRC) portion of the DCI transmission is scrambled with a radio temporary identifier (RNTI) configured to provide a notification of the PWS message to one or more user equipment (UE) operating in connected mode; generating the PWS message; and processing an indication from the one or more UE that the PWS message has been acquired.

[0196] Example 18 is the method of Example 17, wherein a format of the DCI comprises a DCI format 6-1A or a DCI format 6-1B with the RNTI corresponding to notification of at least one of an earthquake and tsunami warning system (ETWS) and a commercial mobile alert system (CMAS).

[0197] Example 19 is the method of Example 18, wherein the RNTI comprises a paging RNTI (P-RNTI).

[0198] Example 20 is the method of Example 18, wherein the DCI format 6-1 A or the DCI format 6-1B with the CRC scrambled with the P-RNTI further comprises system information (SI) update related information.

[0199] Example 21 is the method of Example 18, wherein the DCI comprises a single bit configured to indicate whether or not scheduling information of a system information block (SIB) type 1 bandwidth reduced (SIB1-BR) has changed at least over a system information (SI) validity time.

[0200] Example 22 is the method of Example 17, wherein processing the indication comprises processing one of a dedicated radio resource control (RRC) message, a media access control (MAC) control element, a scheduling request (SR), a quality channel indicator (CQI) report, a sounding reference signal (SRS) report, hybrid automatic repeat request (HARQ) feedback, and a new signal on a physical uplink control channel (PETCCE1).

[0201] Example 23 is the method of Example 17, further comprising, receiving a request from a EGE to pause ongoing or scheduled unicast transmissions to the EGE while the EGE is acquiring the PWS message.

[0202] Example 24 is the method of Example 17, wherein processing the indication comprises processing a radio resource control (RRC) connection re-establishment request from a EGE comprising a single bit to indicate that the EGE is initiating an RRC connection re establishment after acquiring the PWS message from an RRC connected mode.

[0203] Example 25 is the method of Example 17, wherein processing the indication comprises performing a random access procedure wherein at least one of a cell RNTI (C- RNTI) media access control (MAC) control element and a buffer status report (BSR) MAC control element is received from a EGE to indicate that the EGE is ready to resume an RRC connection in the wireless network. [0204] Example 26 is a non-transitory computer-readable storage medium including instructions that, when processed by a processor, configure the processor to perform the method of any one of Example 17 to Example 25.

[0205] Any of the above described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0206] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general- purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and/or firmware.

[0207] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters/attributes/aspects/etc. of one embodiment can be used in another embodiment. The parameters/attributes/aspects/etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters/attributes/aspects/etc. can be combined with or substituted for

parameters/attributes/etc. of another embodiment unless specifically disclaimed herein.

[0208] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of

implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. An apparatus for a user equipment (UE), the apparatus comprising:

a memory interface to send or receive, to or from a memory device, data

corresponding to downlink control information (DCI); and

a baseband processor to:

monitor a common search space (CSS) of a machine-type communications (MTC) physical downlink control channel (MPDCCH) for scheduling of a physical downlink shared channel (PDSCH) in a wireless network, wherein to monitor the CSS includes to decode a DCI transmission, wherein a cyclic redundancy check (CRC) portion of the DCI transmission is scrambled with a radio temporary identifier (RNTI) configured to indicate a notification of a public warning system (PWS) message in connected mode;

in response to the notification of the PWS message, acquire the PWS message from broadcast system information; and

generate an indication to the wireless network of completion of acquiring the PWS message, wherein the indication signals that the UE is ready new unicast communications with the wireless network.

2. The apparatus of claim 1, wherein the UE is a non-bandwidth reduced low complexity (non-BL) UE configured for operation in coverage enhanced (CE) mode.

3. The apparatus of claim 2, wherein a format of the DCI transmission comprises a DCI format 6-1A or a DCI format 6-1B with the RNTI corresponding to notification of at least one of an earthquake and tsunami warn system (ETWS) and a commercial mobile alert system (CMAS).

4. The apparatus of claim 3, wherein the RNTI comprises a paging RNTI (P-RNTI).

5. The apparatus of claim 4, wherein the UE is configured by higher layers to monitor for the DCI format 6-1 A or the DCI format 6-1B with the CRC scrambled with the P-RNTI for MPDCCH candidates start at subframes and in narrowbands (NBs) corresponding to paging occasions (POs) and paging narrowbands (PNBs), respectively.

6. The apparatus of claim 4, wherein the DCI format 6-1 A or the DCI format 6-1B with the CRC scrambled with the P-RNTI further comprises system information (SI) update related information.

7. The apparatus of claim 1, wherein acquiring the PWS message from broadcast system information comprises: decode a master information block (MIB) and a system information block (SIB) type 1 bandwidth reduced (SIB1-BR) to determine an updated schedule of an SIB type 10 (SIB 10), an SIB type 11 (SIB 11), and an SIB type 12 (SIB 12); and

decode one or more of the SIB 10, the SIB11, and the SIB 12 to acquire the PWS message.

8. The apparatus of claim 1, wherein the notification of the PWS message comprises schedule information of a system information block (SIB) type 10 (SIB 10), an SIB type 11 (SIB 11), and an SIB type 12 (SIB12), or the notification of the PWS message comprises scheduling information of an SIB type 1 bandwidth reduced (SIB 1-BR) to determine an updated schedule of the SIB 10, the SIB 11, and the SIB12, and wherein acquiring the PWS message from broadcast system information comprises decoding one or more of the SIB 10, the SIB 11, and the SIB 12 to acquire the PWS message.

9. The apparatus of claim 1, wherein the DCI comprises a single bit configured to indicate whether or not schedule information of a system information block (SIB) type 1 bandwidth reduced (SIB 1-BR) has changed at least over a system information (SI) validity time, and wherein acquiring the PWS message from broadcast system information comprises:

if the single bit indicates that no change has occurred in the scheduling information of the SIB1-BR at least over the SI validity time, use the scheduling information to decode one or more of an SIB type 10 (SIB 10), an SIB type 11 (SIB 11), and an SIB type 12 (SIB 12) to acquire the PWS message; and

if the single bit indicates that a change has occurred in the scheduling information of the SIB 1-BR, decode a master information block (MIB) and the SIB1-BR determine an updated schedule for the SIB10, the SIB11, and the SIB 12 to acquire the PWS message.

10. The apparatus of claim 1, wherein to generate the indication comprises to generate one of a dedicated radio resource control (RRC) message, a media access control (MAC) control element, a scheduling request (SR), a quality channel indicator (CQI) report, a sounding reference signal (SRS) report, hybrid automatic repeat request (HARQ) feedback, and a new signal on a physical uplink control channel (PUCCH).

11. The apparatus of claim 1, wherein the baseband processor is further configured to request the wireless network to pause ongoing or scheduled unicast transmissions to the UE while the UE is acquiring the PWS message.

12. The apparatus of claim 1, wherein to generate the indication comprises to initiate a radio resource control (RRC) connection re-establishment procedure.

13. The apparatus of claim 12, wherein the baseband processor is further configured to generate an RRC connection re-establishment request comprising a single bit to indicate that the UE is performing the RRC connection re-establishment after acquiring the PWS message from RRC connected mode.

14. The apparatus of claim 1, wherein to generate the indication comprises to initiate a random access procedure wherein the UE sends at least one of a cell RNTI (C-RNTI) media access control (MAC) control element and a buffer status report (BSR) MAC control element in an uplink grant received in a random access response (RAR) to resume an RRC connection with a node in the wireless network.

15. The apparatus of claim 1, wherein the UE is configured to operate in a discontinuous reception (DRX) in the connected mode, and wherein available page occasions (POs) in a paging DRX cycle occur during a DRX sleep state, wherein the baseband processor is further configured to:

wake up the UE to monitor the CSS in a first PO;

if the PDSCH is not scheduled in the first PO, continue a current DRX state without modifying one or more DRX timers; and

if monitor the CSS is completed in the first PO and the UE should still be in a DRX sleep state according to the paging DRX cycle, return the UE to the DRX sleep state.

16. The apparatus of claim 1, wherein the UE is configured to operate in a discontinuous reception (DRX) in the connected mode, wherein the baseband processor is further configured to check the CSS for the notification of the PWS message once during a connected mode DRX cycle, and wherein the UE does not check the CSS during a DRX sleep state.

17. A method for communicating a public warning system (PWS) message in a wireless network, the method comprising:

encoding downlink control information (DCI) for broadcast in an MTC physical downlink control channel (MPDCCH), wherein a cyclic redundancy check (CRC) portion of the DCI transmission is scrambled with a radio temporary identifier (RNTI) configured to provide a notification of the PWS message to one or more user equipment (UE) operating in connected mode;

generating the PWS message; and

processing an indication from the one or more UE that the PWS message has been acquired.

18. The method of claim 17, wherein a format of the DCI comprises a DCI format 6-1A or a DCI format 6-1B with the RNTI corresponding to notification of at least one of an earthquake and tsunami warning system (ETWS) and a commercial mobile alert system (CMAS).

19. The method of claim 18, wherein the RNTI comprises a paging RNTI (P-RNTI).

20. The method of claim 18, wherein the DCI format 6-1A or the DCI format 6-1B with the CRC scrambled with the P-RNTI further comprises system information (SI) update related information.

21. The method of claim 18, wherein the DCI comprises a single bit configured to indicate whether or not scheduling information of a system information block (SIB) type 1 bandwidth reduced (SIB 1-BR) has changed at least over a system information (SI) validity time.

22. The method of claim 17, wherein processing the indication comprises processing one of a dedicated radio resource control (RRC) message, a media access control (MAC) control element, a scheduling request (SR), a quality channel indicator (CQI) report, a sounding reference signal (SRS) report, hybrid automatic repeat request (HARQ) feedback, and a new signal on a physical uplink control channel (PUCCH).

23. The method of claim 17, further comprising, receiving a request from a UE to pause ongoing or scheduled unicast transmissions to the UE while the UE is acquiring the PWS message.

24. The method of claim 17, wherein processing the indication comprises processing a radio resource control (RRC) connection re-establishment request from a UE comprising a single bit to indicate that the UE is initiating an RRC connection re-establishment after acquiring the PWS message from an RRC connected mode.

25. The method of claim 17, wherein processing the indication comprises performing a random access procedure wherein at least one of a cell RNTI (C-RNTI) media access control (MAC) control element and a buffer status report (BSR) MAC control element is received from a UE to indicate that the UE is ready to resume an RRC connection in the wireless network.

26. A non-transitory computer-readable storage medium including instructions that, when processed by a processor, configure the processor to perform the method of any one of claim 17 to claim 25.