CN112956221B

CN112956221B - Conflict resolution between User Equipment (UE) initiated signaling procedure and paging for Circuit Switched (CS) services

Info

Publication number: CN112956221B
Application number: CN201980042590.5A
Authority: CN
Inventors: 普拉迪普·C·帕吉; 尼尔什·K·科什塔; 阿尼克坦·R·V; 罗伯特·宙斯
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2018-11-16
Filing date: 2019-11-14
Publication date: 2024-03-22
Anticipated expiration: 2039-11-14
Also published as: WO2020102587A1; CN112956221A; EP3881573A1; EP3881573A4

Abstract

Techniques are disclosed for a User Equipment (UE) operable for conflict resolution between a UE-initiated signal and a page from a Mobile Terminated (MT) Circuit Switched (CS) service of a third generation partnership project (3 GPP) network. The UE may be configured to initiate a UE initiation procedure, wherein the UE initiation procedure is one or more of a Tracking Area Update (TAU) procedure, an International Mobile Subscriber Identity (IMSI) detach procedure, or a Routing Area Update (RAU) procedure. The UE may be configured to decode a CS paging procedure from a target Base Station (BS) prior to completion of the UE initiation procedure, wherein the CS paging procedure is one or more of a CS service notification or a CS paging request. The UE may be configured to complete the UE initiation procedure before responding to the CS paging procedure.

Description

Conflict resolution between User Equipment (UE) initiated signaling procedure and paging for Circuit Switched (CS) services

Background

A wireless system generally includes a plurality of User Equipment (UE) devices communicatively coupled to one or more Base Stations (BSs). The one or more BSs may be long term evolution (Long Term Evolution, LTE) evolved NodeB (eNB) or New Radio (NR) NodeB (gNB), next generation NodeB (next generation node B, gNB), or new radio base station (new radio base station, NR BS) capable of being communicatively coupled to one or more UEs through a Third generation partnership project (Third-Generation Partnership Project,3 GPP) network.

The next generation wireless communication systems are expected to be unified networks/systems, targeting performance dimensions and services that are very different and sometimes conflicting. The new radio access technology (Radio Access Technology, RAT) is expected to support a wide range of use cases including enhanced mobile broadband (Enhanced Mobile Broadband, emmbb), large-scale machine-type communications (Massive Machine Type Communication, emtc), mission-critical machine-type communications (Mission Critical Machine Type Communication, emtc), and similar service types operating in a frequency range up to 100 GHz.

Drawings

The features and advantages of the present disclosure will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, which together illustrate, by way of example, the features of the disclosure; and, in the drawings:

fig. 1 illustrates a block diagram of an Orthogonal Frequency Division Multiple Access (OFDMA) frame structure according to an example;

FIG. 2a depicts a collision scenario at a User Equipment (UE) and a network according to an example;

fig. 2b depicts a collision scenario at a User Equipment (UE) and a network according to an example;

fig. 3 illustrates an architecture of a cellular mobile network supporting Circuit Switched (CS) fallback from an evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), according to an example;

Fig. 4 depicts functionality of a User Equipment (UE) operable for conflict resolution between a UE originated signal and a page from a Mobile Terminated (MT) Circuit Switched (CS) service of a third generation partnership project (3 GPP) network, according to an example;

fig. 5 depicts functionality of a Mobility Management Entity (MME) operable for conflict resolution between a User Equipment (UE) originated signal and a page from a Mobile Terminated (MT) Circuit Switched (CS) service of a third generation partnership project (3 GPP) Long Term Evolution (LTE) network, according to an example;

fig. 6 depicts a flowchart of a machine-readable storage medium having instructions embodied thereon for conflict resolution between a UE-initiated signal and a page from a Mobile Terminated (MT) Circuit Switched (CS) service of a third generation partnership project (3 GPP) Long Term Evolution (LTE) network, according to an example;

FIG. 7 illustrates an example architecture of a system of networks according to some examples;

FIG. 8 illustrates an example of a platform or apparatus according to an example;

fig. 9 illustrates example components of a baseband circuit and a Radio Front End Module (RFEM) according to an example;

FIG. 10 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium according to an example;

Fig. 11 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example; and is also provided with

Fig. 12 illustrates an architecture of a system including a core network according to an example.

Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. However, it will be appreciated that it is not intended to limit the scope of the present technology.

Detailed Description

Before the present technology is disclosed and described, it is to be understood that this technology is not limited to the particular structures, process acts, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those of ordinary skill in the relevant arts. It is also to be understood that the terminology employed herein is for the purpose of describing particular examples only and is not intended to be limiting. Like reference symbols in the various drawings indicate like elements. Numerals provided in the flowcharts and processes are provided for clarity in illustrating actions and operations and do not necessarily indicate a particular order or sequence.

Example embodiment

An initial overview of the technical embodiments is provided below, followed by a more detailed description of specific technical embodiments. This initial summary is intended to aid the reader in understanding the present technology more quickly, and is not intended to identify key features or essential features of the technology, nor is it intended to limit the scope of the claimed subject matter.

In fourth generation (4G) cellular mobile networks according to the third generation partnership project (3 GPP) standards, two processes may conflict: (a) Initiation of a combined registration procedure (tracking area update (tracking area update, TAU) procedure), and (b) paging (CS SERVICE notify) of a mobile terminated (Mobile Terminated, MT) Circuit Switched (CS) call from a Long Term Evolution (LTE) network. When a User Equipment (UE) receives a page in a state in which it does not expect to receive such a message, the UE may not respond to the page, so that a CS call cannot be delivered to the UE, and further network behavior may cause a delay in completion of the registration procedure.

In some scenarios it is possible to handle conflicts involving paging for MT CS services, but unlike conflicts between other procedures, in the 3GPP standard the handling of conflicts between paging for UE and network not yet specified CS services and TAU procedures. Other collision situations (e.g., international mobile subscriber identity (international mobile subscriber identity, IMSI) detach procedure and paging of CS call) may also be specified.

In some cases, the UE may send an EMM STATUS message with a cause #98 "message type not compatible with protocol state" to the network because the UE is not expected to receive CS SERVICE notify message when the UE initiates the TAU procedure and is in the evolved packet system (evolved packet system, EPS) mobility management (EPS mobility management, EMM) state "initiated tracking area update". However, receiving an EMM STATUS message with cause #98 "message type not compatible with protocol state" may cause the network to abort any ongoing non-access stratum (NAS) signaling procedures, including TAU procedures, and release the radio resource control (radio resource control, RRC) connection to the UE.

Even when the UE does not send the EMM STATUS message, the network may not respond to the TAU REQUEST message sent by the UE because the network may be waiting for EXTENDED SERVICE REQUEST messages from the UE in response to the CS SERVICE NOTIFICATION message. When a TAU attempt fails due to a timeout (e.g., after 15 seconds), the RRC connection may be released and the UE may perform another TAU procedure when another timer expires (e.g., after 10 seconds). In some cases, this second registration attempt may be successful. However, the TAU procedure may be delayed and the CS call may be interrupted because the UE may not respond to the CS SERVICE NOTIFICATION message sent from the network.

In one example, the UE may proceed with the TAU procedure and respond to the page when the TAU procedure is complete (CS SERVICE NOTIFICATION). On the network side, the mobility management entity (mobility management entity, MME) may proceed with the TAU procedure and wait for the UE to respond to CS paging with EXTENDED SERVICE REQUEST messages when the TAU procedure is completed. In this case, the UE may register with the network with reduced delay and the MT CS call may be successfully established. The CS call related key performance indicators (key performance indicator, KPI) "successful MT call setup rate" may be enhanced by enabling the UE to respond to CS paging. The registration process (e.g., TAU process) may be completed faster to allow the UE to initiate the pending service request faster. As a result, the UE may enable faster redirection or packet-switched (PS) handover from LTE to 2G or 3G Radio Access Technology (RAT) for CS calls, which may result in shorter MT call setup time. Thus, the CS call related KPI "MT call setup time" may also be enhanced.

In one example, an apparatus of a User Equipment (UE) may be configured to be operable for conflict resolution between a UE-initiated signal and a page from a Mobile Terminated (MT) Circuit Switched (CS) service of a third generation partnership project (3 GPP) network. The apparatus may include one or more processors. The one or more processors may be configured to initiate a UE-initiated procedure at the UE, wherein the UE-initiated procedure is one or more of a Tracking Area Update (TAU) procedure, an International Mobile Subscriber Identity (IMSI) detach procedure, or a routing area update (routing area update, RAU) procedure. The one or more processors may be configured to decode, at the UE, a CS paging procedure from a Base Station (BS) prior to completion of the UE-initiated procedure, wherein the CS paging procedure is one or more of a CS service notification or a CS paging request. The one or more processors may be configured to complete a UE initiation procedure at the UE prior to responding to the CS paging procedure. The apparatus may also include a memory interface configured to store the CS paging procedure in memory.

Fig. 1 provides an example of a frame structure of 3GPP LTE release 8. Specifically, fig. 1 illustrates a downlink radio frame structure type 2. In this example, the radio frame 100 for transmitting signals of data may be configured to have a duration T of 10 milliseconds (ms) _f . Each radio frame may be partitioned or divided into ten subframes 110i, each 1ms long. Each subframe may be further subdivided into two slots 120a and 120b, each slot having a duration T of 0.5ms _slot . The first time slot (# 0) 120a may include a legacy physical downlink control channel (physical downlink control channel, PDCCH) 160 and/or a physical downlink shared channel (physical downlink shared channel, PDSCH) 166, and the second time slot (# 1) 120b may include data transmitted using the PDSCH.

Each slot of a component carrier (component carrier, CC) used by a node and a wireless device may include a plurality of Resource Blocks (RBs) 130a, 130b, 130i, 130m, and 130n based on a CC frequency bandwidth. The CC may have a carrier frequency with a bandwidth and a center frequency. Each subframe of the CC may include downlink control information (downlink control information, DCI) present in the legacy PDCCH. When a legacy PDCCH is used, the legacy PDCCH in the control region may include one to three columns of first orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing, OFDM) symbols in each subframe or RB. The remaining 11 to 13 OFDM symbols (or 14 OFDM symbols when the legacy PDCCH is not used) in the subframe may be allocated to PDSCH for data (for short or normal cyclic prefix).

The control region may include a physical control format indicator channel (physical control format indicator channel, PCFICH), a physical hybrid-automatic repeat request (hybrid-ARQ indicator channel, PHICH), and a PDCCH. The control region has a flexible control design to avoid unnecessary overhead. The number of OFDM symbols for the PDCCH in the control region may be determined by a control channel format indication (channel format indicator, CFI) transmitted in a Physical Control Format Indication Channel (PCFICH). The PCFICH may be located in the first OFDM symbol of each subframe. The PCFICH and PHICH may have priority over the PDCCH, and thus are scheduled before the PDCCH.

Each RB (physical RB or PRB) 130i may comprise 12-15 kilohertz (kHz) subcarriers 136 (on the frequency axis) and 6 or 7 Orthogonal Frequency Division Multiplexing (OFDM) symbols 132 (on the time axis) per slot. If a short or normal cyclic prefix is employed, the RB may use seven OFDM symbols. If an extended cyclic prefix is used, the RB may use six OFDM symbols. The resource blocks may be mapped to 84 Resource Elements (REs) 140i using a short or normal cyclic prefix, or the resource blocks may be mapped to 72 REs (not shown) using an extended cyclic prefix. REs may be units of one OFDM symbol 142 by one subcarrier (i.e., 15 kHz) 146.

Each RE may transmit two bits 150a and 150b of information in the case of quadrature phase-shift keying (QPSK) modulation. Other types of modulation, such as 16 quadrature amplitude modulation (quadrature amplitude modulation, QAM) or 64QAM, may be used to transmit a greater number of bits in each RE, or binary phase shift keying (bi-phase shift keying, BPSK) modulation may be used to transmit a smaller number of bits (a single bit) in each RE. RBs may be configured for downlink transmission from the eNodeB to the UE or configured for uplink transmission from the UE to the eNodeB.

This example of a 3GPP LTE release 8 frame structure provides an example of the manner in which data is transmitted. This example is not intended to be limiting. Many release 8 features will evolve and change in the 5G frame structure included in 3GPP LTE release 15, 3GPP LTE release 16, multewire release 1.1 and higher. In such a system, design constraints may coexist with multiple 5G parameter sets in the same carrier due to coexistence of different network services, such as eMBB (enhanced mobile broadband), emtc (large scale machine type communication or large scale IoT) and URLLC (ultra reliable low latency communication or critical communication). The carrier in a 5G system may be above or below 6GHz. In one embodiment, each web service may have a different set of parameters (numerology).

In another example, a handover may occur while the UE is in connected mode in LTE with an active PS data session (e.g., MME or intra-MME handover case), and the network may receive a CS page for the UE during an X2 handover or just before the X2 handover is about to begin. In another example, a data radio bearer (Data Radio Bearer, DRB) can be established and a PS data session can be active over LTE. In this example, the UE may camp on a cell belonging to a Tracking Area (TA) having a tracking area identifier (tracking area identifier, TAI) a. In another example, the UE may perform a handover to a cell belonging to a TA with a different TAI (TAI-B) and the UE may initiate a registration update (e.g., tracking Area Update (TAU)) procedure due to the TAI change. In another example, the network may trigger CS SERVICE NOTIFICATION due to a pending or received MT CS call.

In another example, due to this collision scenario, the network may expect the UE's response to CS SERVICE NOTIFICATION (e.g., EXTENDED SERVICE REQUEST), and the UE may not send EXTENDED SERVICE REQUEST, as the UE may be waiting for a response to the TAU REQUEST from the network. In this case, the MT CS call may be interrupted and completion of the TAU procedure may be delayed. In another example, instead of an X2 handover on the network side, a collision scenario may also occur for an S1 handover.

In another example, as shown in fig. 2a, the resolution of the collision scenario may be shown from the network side and the UE side. The Mobility Management Entity (MME) 240 may receive a page for the CS from the mobile services switching center (mobile services switching center, MSC), as depicted in operation 202. A CS service notification may be sent from the MME to the source eNB 220 as depicted in operation 204. The MME may send a CS service notification to target eNB 230 as depicted in operation 206. The UE 210 may send a tracking area update request to the MME 240 sent because of the TA change, as depicted in operation 207. The UE 210 may send a Tracking Area Update (TAU) request to the MME 240 due to the TA change, e.g., during a handover, as depicted in operation 208. The target eNB may send a CS service notification to the UE 210, as depicted in operation 212. Upon receiving the CS service notification, the UE may send an Evolved Packet System (EPS) mobility management (EMM) status message to the MME, as depicted in operation 214.

In one example, the UE 210 may continue the TAU procedure and the network may first resolve the TAU procedure. After the TAU procedure is completed, the UE may send EXTENDED SERVICE REQUEST a message in response to CS SERVICE NOTIFICATION.

In another example, as shown in fig. 2b, the resolution of the conflict is shown from the UE side and the network side. A Mobility Management Entity (MME) 240 may receive a page from the MSC for the CS, as depicted in operation 202. A CS service notification may be sent from MME 240 to source eNB 220 as depicted in operation 204. MME 240 may send a CS service notification to target eNB 230 as depicted in operation 206. The UE 210 may send a Tracking Area Update (TAU) request to the MME 240 during the handover because of the TA change, as depicted in operation 208.

In another example, target eNB 230 may send a CS service notification to UE 210, as depicted in operation 212. MME 240 may send a TAU accept message to the UE as depicted in operation 216. UE 210 may send a TAU complete message to MME 240 as depicted in operation 218. The UE 210 may send an extended service request for the to-do MT call, as depicted in operation 222.

In one example, a TAU may be initiated by a UE and the network may receive a CS page for the UE for cases other than a TAI change. TAU may be initiated by the UE for situations other than TAI changes (e.g., local packet data protocol (packet data protocol, PDP) context deactivation, voice domain preference changes, discontinuous reception (discontinuous reception, DRX) parameter changes, for load balancing at the MME, etc.).

In another example, the network may begin a CS paging procedure. In response, the UE may wait for a TAU ACCEPT message or the UE may send EXTENDED SERVICE REQUEST. In this example, collisions may occur at different times of RRC connection establishment. For example, when a CS page is received, the UE may start TAU while in IDLE mode. In another example, the UE may initiate RRC connection establishment and may receive CS SERVICE NOTIFICATION when the RRC connection has been successfully established.

In another example, the UE may continue the TAU procedure and the network may process the TAU procedure first. After the TAU procedure is completed, the UE may send EXTENDED SERVICE REQUEST a message.

In another example, the IMSI detach procedure may be initiated by the UE and the CS paging may be triggered by the LTE network. In this example, an IMSI detach procedure (i.e., a combined detach procedure with detach type "IMSI detach") may be initiated by the UE. The network may begin the CS paging procedure. The UE may continue waiting DETACH ACCEPT or the UE may send EXTENDED SERVICE REQUEST. In this case, the collision may occur at different times of RRC connection establishment. For example, when a CS page is received, the UE may proceed IMSI DETACH while in IDLE mode. Upon receiving CS SERVICE NOTIFICATION, the UE may initiate RRC connection establishment. In another example, the UE may ignore the CS page and the UE and the network may proceed with the IMSI detach procedure.

In another example, a combined Routing Area Update (RAU) procedure may be initiated by the UE for reasons other than routing area identifier (routing area identifier, RAI) changes. In this example, CS paging may be triggered by the network operating in "network operation mode 1" (NMO 1). In this example, an RAU with a type "combined RA/LA update" may be initiated by the UE. The MM state of the UE may be changed to MM LOCATION UPDATING PENDING state. In this example, the network may begin the CS paging procedure at the same time or before. In state "MM LOCATION UPDATING PENDING", the MM entity of the UE may not be able to process the CS paging request and it may be expected that the combined RAU procedure will be completed first.

In another example, the network (MSC) may expect a PAGING RESPONSE message (in the case of UMTS) or a channel request (in the case of GSM) to be sent by a Radio Resource (RR) entity of the UE for RR connection establishment. In this example, the UE and the network may proceed with the combined RAU procedure, and when complete, the UE may respond to the page by sending a PAGING RESPONSE message.

In another example, after a handover or cell change command (cell change order, CCO) (serving general packet radio service (general packet radio service, GPRS) support node (serving GPRS support node, SGSN) in 2G/3G PS connected mode or inter-SGSN), the combined RAU may be initiated by the UE due to the RAI change. In this case, a CS page triggered by the NMO1 network may be received by the UE in a packet data channel (Packet Data Channel, PDC).

In another example, an RAU with a type "combined RA/LA update" may be initiated by the UE. The MM state of the UE may be changed to MM LOCATION UPDATING PENDING state. The network (SGSN) may begin the CS paging procedure at the same time or before the RAU REQUEST is sent by the UE.

In another example, in state "MM LOCATION UPDATING PENDING", the MM entity of the UE may not be able to process the CS paging request and it is expected that the combined RAU procedure will be completed first. In this example, the network may expect that a PAGING RESPONSE (in the case of UMTS) or channel request (in the case of GSM) is sent by RR for RR connection establishment.

In another example, both the UE and the network may proceed with the combined RAU procedure, and when complete, the UE may respond to the page by sending a PAGING RESPONSE message.

In another example, as shown in fig. 3, when a UE 310 registers for CS services and an MSC server 340 receives a Mobile Terminated (MT) call for the UE, the MSC server may: (a) The SGsAP paging request message is sent to MME 330 via the SGs interface, or (b) the bssap+ paging request message is sent to SGSN 335 via the Gs interface, or both.

In another example, the MSC server 340 may also send a BSSMAP paging message to one or more BSCs in the GERAN 324 via the A interface, or a RANAP paging message to one or more RNC in the UTRAN 328 via the Iu-cs interface, or both.

In another example, upon receiving the SGsAP paging request message, MSC server 340 may page UE 310 by: (a) By sending an S1AP paging message to one or more enodebs in the E-UTRAN 320 via the S1-MME interface if the UE 310 is in IDLE mode, the one or more enodebs may in turn send pages for CS services to the UE 310 via a paging channel, or (b) by sending a non-access stratum (NAS) message CS SERVICE NOTIFICATION to the UE 310 via an existing signaling connection if the UE 310 is in CONNECTED mode.

In another example, upon receiving the bssap+paging request message, SGSN 335 may page UE 310 by: (a) If the UE 310 is in IDLE mode in UTRAN 328 or in STANDBY state in GERAN 324, SGSN 335 may page the UE 310 by sending RANAP page messages to one or more RNCs in UTRAN 328 via the Iu-CS interface, or by sending BSSGP "page CS" messages to one or more BSCs in GERAN 324 via the Gb interface, or both. The RNC can trigger paging for CS services via the node B via the paging channel and the BSC can trigger paging for CS services via the BTS via the paging channel, or (c) if the UE 310 is in the CONNECTED mode in UTRAN 328 or it is in the READY state in GERAN 324, the SGSN 335 can send a paging message to the RNC or a paging CS message to the BSC serving the UE 310. The RNC may deliver the page for CS services via the node B serving the UE 310 via the existing RRC connection, while the BSC may deliver the page for CS services via the BTS serving the UE 310 via the temporary block flow (temporary block flow, TBF).

Another example provides a function 400 of a User Equipment (UE) operable for conflict resolution between a UE-initiated signal and a page from a Mobile Terminated (MT) Circuit Switched (CS) service of a third generation partnership project (3 GPP) network, as shown in fig. 4. The UE may include one or more processors. The one or more processors may be configured to initiate a UE-initiated procedure at the UE, wherein the UE-initiated procedure is one or more of a Tracking Area Update (TAU) procedure, an International Mobile Subscriber Identity (IMSI) detach procedure, or a Routing Area Update (RAU) procedure, as shown in block 410. The one or more processors may be configured to decode, at the UE, a CS paging procedure from a Base Station (BS) prior to completion of the UE-initiated procedure, wherein the CS paging procedure is one or more of a CS service notification or a CS paging request, as shown in block 420. The one or more processors may be configured to complete a UE initiation procedure at the UE prior to responding to the CS paging procedure, as shown in block 430. Further, the UE may include a memory interface configured to store CS paging procedures in memory.

Another example provides a functionality 500 of a Mobility Management Entity (MME) operable for conflict resolution between a User Equipment (UE) -initiated signal and a page from a Mobile Terminated (MT) Circuit Switched (CS) service of a third generation partnership project (3 GPP) Long Term Evolution (LTE) network, as shown in fig. 5. The MME may include one or more processors. The one or more processors may be configured to encode, at the MME, a CS paging procedure for transmission to the UE via an evolved node B (eNB), wherein the CS paging procedure is a CS service notification, as shown in block 510. The one or more processors may be configured to decode, at the MME, a UE-initiated procedure prior to receiving the response to the CS paging procedure, wherein the UE-initiated procedure is a TAU procedure, as shown in block 520. The one or more processors may be configured to encode a Tracking Area Update (TAU) accept message at the MME for transmission to the UE via the BS, as shown in block 530. The one or more processors may be configured to decode the TAU complete message at the MME upon receiving the TAU complete message from the UE, as shown in block 540. In some examples, the one or more processors may be configured to determine, at the MME, that the UE-initiated procedure is complete when the TAU accept message is sent. In some examples, the one or more processors may be configured to determine, at the MME, that the UE-initiated procedure is complete when a TAU complete message is received from the UE. The one or more processors may be configured to decode, at the MME, an extended service request message received from the UE in response to the CS service notification after completion of the UE-initiated procedure, as shown in block 550. Further, the MME may include a memory interface configured to retrieve CS paging procedures from memory.

Another example provides at least one machine-readable storage medium having instructions 600 embodied thereon for conflict resolution between a UE-initiated signal and a page from a Mobile Terminated (MT) Circuit Switched (CS) service of a third generation partnership project (3 GPP) Long Term Evolution (LTE) network, as shown in fig. 6. The instructions may be executed on a machine, where the instructions are included on at least one computer-readable medium or at least one non-transitory machine-readable storage medium. The instructions, when executed, perform: a UE initiation procedure is initiated at the UE, wherein the UE initiation procedure is one or more of a Tracking Area Update (TAU) procedure, an International Mobile Subscriber Identity (IMSI) detach procedure, or a Routing Area Update (RAU) procedure, as shown in block 610. The instructions, when executed, perform: a CS paging procedure from a Base Station (BS) is decoded at the UE before completion of the UE-initiated procedure, wherein the CS paging procedure is one or more of a CS service notification or a CS paging request, as shown in block 620. The instructions, when executed, perform: the UE initiation procedure is completed at the UE prior to responding to the CS paging procedure, as shown in block 630.

Although examples are provided in which BSs are specified, they are not intended to be limiting. Instead of the BS, an evolved node B (eNB), a next generation node B (gNB), a new radio node B (gNB), or a new radio base station (NR BS) may be used. Thus, unless otherwise stated, any example herein in which a BS is disclosed may be similarly disclosed by using an eNB, a gNB, or a new radio base station (NR BS).

Fig. 7 illustrates an example architecture of a system 700 of a network in accordance with various embodiments. The following description is provided for an example system 700 that operates in conjunction with the LTE system standard and the 5G or NR system standard provided by the 3GPP technical specifications. However, the example embodiments are not limited thereto and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, wiMAX, etc.), and so forth.

As shown in fig. 7, system 700 includes a UE 701a and a UE 701b (collectively referred to as "UEs 701" or "UE 701"). In this example, the UE 701 is shown as a smart phone (e.g., a handheld touch screen mobile computing device connectable to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronics, cellular phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (personal digital assistant, PDA), pagers, wireless handsets, desktop computers, laptop computers, in-car infotainment (in-vehicle infotainment, IVI), in-car entertainment (in-car entertainment, ICE) devices, dashboards (Instrument Cluster, ICs), head-up display (HUD) devices, on-board diagnostics (onboard diagnostic, OBD) devices, dashboard surface mobile devices (dashtop mobile equipment, DME), mobile data terminals (mobile data terminal, MDT), electronic engine management systems (Electronic Engine Management System, EEMS), electronic/engine control units (electronic/engine control unit, ECU), electronic/engine control module, ECM), embedded systems, microcontrollers, control modules, engine management system, systems, internet appliances, systems, or the like.

In some embodiments, any of the UEs 701 may be IoT UEs that may include a network access layer designed for low power IoT applications that utilize short-term UE connections. IoT UEs may utilize technologies such as M2M or MTC to exchange data with MTC servers or devices via PLMN, proSe, or D2D communications, sensor networks, or IoT networks. The M2M or MTC data exchange may be a machine initiated data exchange. IoT network descriptions interconnect IoT UEs with short-term connections, which may include uniquely identifiable embedded computing devices (within the internet infrastructure). The IoT UE may execute a background application (e.g., keep-alive messages, status updates, etc.) to facilitate connection of the IoT network.

The UE 701 may be configured to connect, e.g., communicatively couple, with the RAN 710. In an embodiment, the RAN 710 may be a NG RAN or a 5G RAN, E-UTRAN, or a conventional RAN, such as UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to a RAN 710 operating in an NR or 5G system 700, and the term "E-UTRAN" or the like may refer to a RAN 710 operating in an LTE or 4G system 700. The UE 701 utilizes connections (or channels) 704 and 704, respectively, each of the connections (or channels) 703 and 704 including a physical communication interface or layer (discussed in more detail below).

In this example, connections 703 and 704 are shown as air interfaces to enable communicative coupling, and may conform to cellular communication protocols, such as GSM protocols, CDMA network protocols, PTT protocols, POC protocols, UMTS protocols, 3GPP LTE protocols, 5G protocols, NR protocols, and/or any other communication protocols discussed herein. In an embodiment, the UE 701 may exchange communication data directly via the ProSe interface 705. ProSe interface 705 may alternatively be referred to as SL interface 705 and may include one or more logical channels including, but not limited to PSCCH, PSSCH, PSDCH and PSBCH.

UE 701b is shown configured to access AP 706 (also referred to as "WLAN node 706", "WLAN termination 706", or "WT 706" or the like) via connection 707. Connection 707 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, where AP 706 would include wireless fidelityAnd a router. In this example, the AP 706 is shown connected to the internet, rather than to the core network of the wireless system (described in more detail below). In various embodiments, the UE 701b, RAN 710, and AP 706 may be configured to operate with LWA and/or LWIP. The LWA operation may involve the UE 701b in rrc_connected being configured by the RAN nodes 711a-b to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 701b utilizing WLAN radio resources (e.g., connection 707) to authenticate and encrypt packets (e.g., IP packets) sent over connection 707 via IPsec protocol tunneling. IPsec tunneling may involve encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

RAN 710 may include one or more AN nodes or RAN nodes 711a and 711b (collectively, "RAN nodes 711") that enable connections 703 and 704. As used herein, the terms "access node," "access point," and the like may describe devices that provide radio baseband functionality for data and/or voice connectivity between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN nodes, eNB, nodeB, RSU, TRxP or TRP, etc., and may include ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographic area (e.g., cell). As used herein, the term "NG RAN node" or the like may refer to a RAN node 711 (e.g., a gNB) operating in an NR or 5G system 700, and the term "E-UTRAN node" or the like may refer to a RAN node 711 (e.g., an eNB) operating in an LTE or 4G system 700. According to various embodiments, the RAN node 711 may be implemented as one or more of the following: dedicated physical devices such as macrocell base stations, and/or Low Power (LP) base stations for providing femto cells, pico cells or other similar cells with smaller coverage areas, smaller user capacities or higher bandwidths than the macrocell.

In some embodiments, all or some portions of the RAN node 711 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a CRAN and/or virtual baseband unit pool (virtual baseband unit pool, vbup). In these embodiments, CRAN or vBBUP may implement RAN functionality segmentation, e.g., PDCP segmentation, where RRC and PDCP layers are operated by CRAN/vBBUP and other L2 protocol entities are operated by individual RAN node 711; MAC/PHY splitting, where RRC, PDCP, RLC and MAC layers are operated by CRAN/vbup and PHY layers are operated by individual RAN nodes 711; or "lower PHY" split, where RRC, PDCP, RLC, MAC layers and upper portions of the PHY layers are operated by CRAN/vBBUP and lower portions of the PHY layers are operated by individual RAN nodes 711. This virtualization framework allows the vacated processor cores of RAN node 711 to execute other virtualized applications. In some implementations, the individual RAN node 711 may represent an individual gNB-DU connected to the gNB-CU via an individual F1 interface (not shown in fig. 7). In these implementations, the gNB-DU may include one or more remote radio heads or RFEM, and the gNB-CU may be operated by a server located in the RAN 710 (not shown) or by a server pool in a similar manner as the CRAN/vbBUP. Additionally or alternatively, one or more of the RAN nodes 711 may be next generation enbs (NG-enbs) that are RAN nodes providing E-UTRA user plane and control plane protocol termination towards the UE 701 and are connected to the 5GC via an NG interface (discussed below).

In a V2X scenario, one or more RAN nodes 711 may be or act as RSUs. The term "roadside unit" or "RSU" may refer to any transportation infrastructure entity for V2X communication. The RSUs may be implemented in or by appropriate RAN nodes or stationary (or relatively stationary) UEs, wherein the RSUs implemented in or by the UEs may be referred to as "UE-type RSUs", the RSUs implemented in or by the enbs may be referred to as "eNB-type RSUs", the RSUs implemented in or by the gnbs may be referred to as "gNB-type RSUs", etc. In one example, the RSU is a computing device coupled with radio frequency circuitry located at the roadside that provides connectivity support to the passing vehicle UE 701 (vUE 701). The RSU may also include internal data storage circuitry to store intersection map geometry, traffic flow statistics, media, and applications/software to sense and control ongoing vehicle and pedestrian traffic flows. The RSU may operate over the 5.9GHz direct short range communication (Direct Short Range Communications, DSRC) band to provide very low latency communications required for high speed events, such as collision avoidance, traffic flow warnings, and the like. Additionally or alternatively, the RSU may operate over a cellular V2X frequency band to provide the low latency communications described above, as well as other cellular communication services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and/or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the radio frequency circuitry of the computing device(s) and RSU may be enclosed in a weather-proof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., ethernet) to the traffic flow signal controller and/or the backhaul network.

Any of the RAN nodes 711 may terminate the air interface protocol and may be the first point of contact of the UE 701. In some embodiments, any of the RAN nodes 711 may perform various logical functions for the RAN 710 including, but not limited to, radio network controller (radio network controller, RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

In an embodiment, UE 701 may be configured to communicate with each other or any of RAN nodes 711 using OFDM communication signals over a multicarrier communication channel in accordance with various communication techniques such as, but not limited to, OFDMA communication techniques (e.g., for downlink communications) or SC-FDMA communication techniques (e.g., for uplink and ProSe or side-channel communications), although the scope of the embodiments is not limited in this respect. The OFDM signal may comprise a plurality of orthogonal subcarriers.

In some embodiments, the downlink resource grid may be used for downlink transmissions from any of the RAN nodes 711 to the UE 701, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which is a physical resource in the downlink in each time slot. This time-frequency plane representation is a common practice of OFDM systems, which makes it intuitive for radio resource allocation. Each column and first row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in the resource grid is denoted as a resource element. Each resource grid comprises several resource blocks, which describe the mapping of specific physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum number of resources that are currently allocable. There are several different physical downlink channels that utilize such resource block transport.

According to various embodiments, UE 701 and RAN node 711 transmit data (e.g., send and receive data) over a licensed medium (also referred to as a "licensed spectrum" and/or a "licensed band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and/or an "unlicensed band"). The licensed spectrum may include channels operating in a frequency range of about 400MHz to about 3.8GHz, while the unlicensed spectrum may include the 5GHz band.

To operate in unlicensed spectrum, the UE 701 and RAN node 711 may operate with LAA, eLAA, and/or feLAA mechanisms. In these implementations, the UE 701 and RAN node 711 may perform one or more known medium and/or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied prior to transmission in the unlicensed spectrum. The medium/carrier sense operation may be performed according to listen-before-talk (LBT) protocol.

LBT is a mechanism by which a device (e.g., UE 701, RAN node 711, etc.) detects a medium (e.g., channel or carrier frequency) and transmits when it detects that the medium is idle (or when it detects that a particular channel in the medium is unoccupied). The medium sensing operation may include a CCA that utilizes at least the ED to determine the presence or absence of other signals on the channel in order to determine whether the channel is occupied or idle. This LBT mechanism allows the cellular/LAA network to coexist with incumbent systems in unlicensed spectrum and with other LAA networks. ED may include detecting RF energy over an expected transmission band for a period of time and comparing the detected RF energy to a predetermined or configured threshold.

In general, incumbent systems in the 5GHz band are WLANs based on IEEE 802.11 technology. WLAN employs a contention-based channel access mechanism called CSMA/CA. Here, when a WLAN node (e.g., a Mobile Station (MS), an AP 706, etc., such as the UE 701) wants to transmit, the WLAN node may first perform CCA before transmitting. Furthermore, a back-off mechanism is used to avoid collisions when more than one WLAN node detects the channel as idle and transmits simultaneously. The backoff mechanism may be a counter that is randomly pulled out within the CWS, exponentially incremented when a collision occurs, and reset to a minimum when the transmission is successful. The LBT mechanism designed for LAA is sometimes similar to CSMA/CA of WLAN. In some implementations, the LBT procedure including DL or UL transmission bursts of PDSCH or PUSCH transmissions, respectively, may have LAA contention window that is variable in length between X and Y ECCA slots, where X and Y are minimum and maximum values of CWS for the LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and MCOT (e.g., transmit burst) may be based on government regulatory requirements.

The LAA mechanism is built on CA technology of LTE advanced systems. In CA, each aggregated carrier is referred to as a CC. CCs may have bandwidths of 1.4, 3, 5, 10, 15 or 20MHz and up to five CCs may be aggregated, and thus the maximum aggregate bandwidth is 100MHz. In an FDD system, the number of aggregated carriers may be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, individual CCs may have different bandwidths than other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are typically the same for DL and UL.

The CA also includes an individual serving cell to provide individual CCs. Coverage of a serving cell may be different, for example, because CCs on different frequency bands will experience different path loss. The primary serving cell or PCell may provide PCC for both UL and DL and may handle RRC and NAS related activities. Other serving cells are referred to as scells, and each SCell may provide an individual SCC for both UL and DL. SCCs may be added and removed as needed, while changing PCC may require UE 701 to undergo handover. In LAA, eLAA, and feLAA, some or all scells may operate in unlicensed spectrum (referred to as "LAA scells"), and LAA scells may be assisted by PCell operating in licensed spectrum. When the UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCell, the UL grants indicating different PUSCH start locations within the same subframe.

PDSCH carries user data and higher layer signaling to UE 701. The PDCCH carries information about transport formats and resource allocations related to the PDSCH channels, and so on. It may also inform the UE 701 about transport format, resource allocation and HARQ information related to the uplink shared channel. In general, downlink scheduling (assigning control and shared channel resource blocks to UEs 701b within a cell) may be performed at any of the RAN nodes 711 based on channel quality information fed back from any of the UEs 701. The downlink resource assignment information may be sent on a PDCCH for (e.g., assigned to) each of the UEs 701.

The PDCCH uses CCEs to convey control information. The PDCCH complex-valued symbols may first be organized into four tuples before being mapped to resource elements, which may then be permuted with sub-block interleavers for rate matching. Each PDCCH may be transmitted with one or more CCEs, where each CCE may correspond to nine sets of four physical resource elements called REGs. Four quadrature phase shift keying (Quadrature Phase Shift Keying, QPSK) symbols may be mapped for each REG. Depending on the size of the DCI and the channel conditions, the PDCCH may be transmitted with one or more CCEs. Four or more different PDCCH formats may be defined in LTE, with different numbers of CCEs (e.g., aggregation level l=1, 2, 4, or 8).

Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the concepts described above. For example, some embodiments may utilize EPDCCH using PDSCH resources for control information transmission. EPDCCH may be transmitted using one or more ECCEs. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements referred to as EREGs. ECCE may have other numbers of EREGs in some cases.

RAN nodes 711 may be configured to communicate with each other via interface 712. In embodiments where system 700 is an LTE system, interface 712 may be an X2 interface 712. The X2 interface may be defined between two or more RAN nodes 711 (e.g., two or more enbs, etc.) connected to EPC 720 and/or between two enbs connected to EPC 720. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user data packets transmitted over the X2 interface and may be used to transmit information between enbs regarding the delivery of user data. For example, X2-U may provide specific sequence number information for user data transferred from the MeNB to the SeNB; information about success of sequence delivery of PDCP PDUs for user data from SeNB to UE 701; information of PDCP PDUs not delivered to the UE 701; information about a current minimum expected buffer size for transmitting user data to the UE at the SeNB; etc. X2-C may provide LTE access mobility functions including context transfer from source to target eNB, user plane transmission control, and so on; a load management function; inter-cell interference coordination function.

In embodiments where system 700 is a 5G or NR system, interface 712 may be an Xn interface 712. An Xn interface is defined between two or more RAN nodes 711 (e.g., two or more gnbs, or the like) connected to the 5gc 720, between a RAN node 711 (e.g., a gNB) connected to the 5gc 720 and an eNB, and/or between two enbs connected to the 5gc 720. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U may provide for the non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functions. An Xn-C can provide management and error processing functions, and functions of managing an Xn-C interface; mobility support for a UE 701 in a CONNECTED mode (e.g., CM-CONNECTED) includes functionality to manage UE mobility in a CONNECTED mode between one or more RAN nodes 711. Mobility support may include context transfer from an old (source) serving RAN node 711 to a new (target) serving RAN node 711; and control of user plane tunnels between the old (source) serving RAN node 711 to the new (target) serving RAN node 711. The protocol stack of an Xn-U may include a transport network layer built on top of an internet protocol (Internet Protocol, IP) transport layer, and a GTP-U layer on top of UDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol, referred to as the Xn application protocol (Xn Application Protocol, xn-AP), and a transport network layer built on SCTP. SCTP may be above the IP layer and may provide for guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other implementations, the Xn-U protocol stack and/or the Xn-C protocol stack may be the same as or similar to the user plane(s) and/or control plane protocol stack(s) shown and described herein.

RAN 710 is shown communicatively coupled to a core network, in this embodiment Core Network (CN) 720.CN 720 may include a plurality of network elements 722 configured to provide a variety of data and telecommunications services to clients/subscribers (e.g., users of UE 701) connected to CN 720 via RAN 710. The components of CN 720 may be implemented in one physical node or in separate physical nodes, which include components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be utilized to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage media (described in more detail below). The logical instantiation of the CN 720 may be referred to as a network slice, and the logical instantiation of a portion of the CN 720 may be referred to as a network sub-slice. NFV architecture and infrastructure can be used to virtualize one or more network functions, either performed by proprietary hardware, onto physical resources including industry standard server hardware, storage hardware, or a combination of switches. In other words, NFV systems may be used to perform virtual or reconfigurable implementations of one or more EPC components/functions.

In general, the application server 730 may be an element that provides an application (e.g., UMTS PS domain, LTE PS data services, etc.) that uses IP bearer resources with the core network. The application server 730 may also be configured to support one or more communication services (e.g., voIP session, PTT session, group communication session, social networking service, etc.) for the UE 701 via the EPC 720.

In an embodiment, CN 720 may be 5GC (referred to as "5GC 720" or the like), and RAN 710 may be connected with CN 720 via NG interface 713. In an embodiment, NG interface 113A may be split into two parts: an NG user plane (NG-U) interface 714 that carries traffic data between RAN node 711 and UPF; and a NG control plane (NG-C) interface 715, which is a signaling interface between RAN node 111 and the AMF.

In an embodiment, CN 720 may be a 5G CN (referred to as "5gc 720" or the like), while in other embodiments CN 720 may be an EPC. In the case where CN 720 is EPC (referred to as "EPC 720" or the like), RAN 710 may connect with CN 720 via S1 interface 713. In an embodiment, S1 interface 713 may be split into two parts: an S1 user plane (S1-U) interface 714 that carries traffic data between RAN node 711 and S-GW; and an S1-MME interface 715, which is a signaling interface between RAN node 111 and MME.

Fig. 8 illustrates an example of a platform 800 (or "device 800") in accordance with various embodiments. In embodiments, computer platform 800 may be suitable for use as UE 701, application server 730, and/or any other element/device discussed herein. Platform 800 may include any combination of the components shown in the examples. The components of platform 800 may be implemented as Integrated Circuits (ICs), portions thereof, discrete electronic devices, or other modules adapted in computer platform 800, logic, hardware, software, firmware, or combinations thereof, or as components otherwise contained within the chassis of a larger system. The block diagram of fig. 8 is intended to illustrate a high-level view of the components of computer platform 800. However, in other implementations, some components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur.

The application circuitry 805 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: LDO, interrupt controller, such as SPI, I ² A serial interface such as a C or universal programmable serial interface module, RTC, timer-counter including interval and watchdog timer, universal I/O, memory card controller such as SD MMC, USB interface, MIPI interface, and JTAG test access port. The processor (or core) of the application circuit 805 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the system 800. In some implementations, the memory/storage elements may be on-chip memory circuits that may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid state memory, and/or any other type of memory device technology, such as those discussed herein.

The processor(s) of the application circuitry may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multi-threaded processor, an ultra-low voltage processor, an embedded processor, some other known processing elements, or any suitable combination of these. In some embodiments, the application circuitry may include or may be a dedicated processor/controller to operate in accordance with various embodiments herein.

As an example, the processor(s) of the application circuit 805 may include based onArchitecture Core ^TM For processors of (a), e.g. quick ^TM 、Atom ^TM I3, i5, i7 or MCU class processor, or alternatively from Santa Clara, calif.)Additional such processors are available from companies. The processor of the application circuit 805 may also be one or more of the following: ultra-micro semiconductor(s) (Advanced Micro Devices, AMD) +.>A processor or acceleration processing unit (Accelerated Processing Unit, APU); from- >Company A5-A9 processor(s), from +.>Snapdragon(s) of technology Co ^TM Processor(s)>Is (are) open multimedia application platform (Open Multimedia Applications Platform, OMAP) ^TM A processor; MIPS-based designs from MIPS technologies Inc., such as MIPS Warrior M-class, warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM-controlled companies,such as ARM Cortex-A, cortex-R and Cortex-M processor families; etc. In some implementations, the application circuit 805 may be part of a system on a chip (SoC) in which the application circuit 805 and other components are formed as a single integrated circuit, or a single package, e.g., from ∈ ->Edison of Co Ltd ^TM Or Galileo ^TM SoC board.

Additionally or alternatively, the application circuitry 805 may include circuitry such as, but not limited to, the following: one or more field-programmable devices (FPDs), such as FPGAs, etc.; a programmable logic device (programmable logic device, PLD), such as a Complex PLD (CPLD), a high-capacity PLD (HCPLD), or the like; an ASIC, such as a structured ASIC, etc.; programmable SoC (PSoC); etc. In such embodiments, the circuitry of application circuitry 805 may include logic blocks or logic architectures and other interconnected resources that can be programmed to perform various functions, such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of application circuitry 805 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), flash memory, static memory (e.g., static random access memory (static random access memory), antifuse, etc.) for storing logic blocks, logic architectures, data, etc. in a look-up table (LUT), and so forth.

The baseband circuitry 810 may be implemented, for example, as a solder-in substrate comprising one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Various hardware electronics of baseband circuitry 810 are discussed below with reference to fig. 9.

RFEM 815 may include millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (radio frequency integrated circuit, RFIC). In some implementations, one or more sub-mmWave RFICs may be physically separate from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., antenna array 911 of fig. 9 below), and the RFEM may be connected to multiple antennas. In alternative implementations, both mmWave and sub-mmWave radio functions may be implemented in the same physical RFEM 815, which RFEM 815 contains both mmWave antennas and sub-mmWave.

Memory circuit 820 may include any number and type of memory devices for providing a given amount of system memory. As an example, memory circuit 820 may include one or more of the following: volatile memory, including random access memory (random access memory, RAM), dynamic RAM (DRAM), and/or synchronous dynamic RAM (synchronous dynamic RAM, SDRAM); and nonvolatile memory (nonvolatile memory, NVM) including high-speed electrically erasable memory (commonly referred to as flash memory), phase-change random access memory (phase change random access memory, PRAM), magnetoresistive Random Access Memory (MRAM), and the like. The memory circuit 820 may be developed in accordance with a design based on the joint electron device engineering council (Joint Electron Devices Engineering Council, JEDEC) low power dual data rate (low power double data rate, LPDDR), such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 820 may be implemented as one or more of a solder-in package integrated circuit, a single die package (single die package, SDP), a Dual Die Package (DDP), or a quad die package (Q17P), a socket memory module, a dual inline memory module (dual inline memory module, DIMM) including a micro DIMM or a MiniDIMM, and/or soldered to a motherboard via a Ball Grid Array (BGA). In a low power implementation, the memory circuit 820 may be an on-chip memory or register associated with the application circuit 805. To support persistent storage of information, such as data, applications, operating systems, and the like, the memory circuit 820 may include one or more mass storage devices that are operated in accordance with a particular embodiment of the present invention May include solid state disk drives (solid state disk drive, SSDD), hard Disk Drives (HDD), micro HDDs, resistance change memory, phase change memory, holographic memory, or chemical memory, among others. For example, computer platform 800 may include a computer system from the group consisting ofAnd->Three-dimensional (3D) cross-point (XPOINT) memory.

Removable memory circuit 823 may include means, circuitry, boxes/housings, ports or receptacles, etc. for coupling the portable data storage device to platform 800. These portable data storage devices may be used for mass storage purposes and may include, for example, flash memory cards (e.g., secure Digital (SD) cards, microSD cards, xD picture cards, etc.), as well as USB flash drives, optical disks, external HDDs, and the like.

Platform 800 may also include interface circuitry (not shown) for connecting external devices to platform 800. External devices connected to platform 800 via interface circuitry include sensor circuitry 821 and electro-mechanical components (EMC-mechanical component) 822, as well as removable memory devices coupled to removable memory circuitry 823.

The sensor circuit 821 includes devices, modules, or subsystems whose purpose is to detect events or changes in its environment and to send information (sensor data) about the detected event to some other device, module, subsystem, etc. Examples of such sensors include, inter alia, inertial measurement units (inertia measurement unit, IMU), including accelerometers, gyroscopes and/or magnetometers; microelectromechanical systems (microelectromechanical systems, MEMS) or nanoelectromechanical systems (nanoelectromechanical systems, NEMS) including 3-axis accelerometers, 3-axis gyroscopes and/or magnetometers; a level sensor; a flow sensor; a temperature sensor (e.g., a thermal resistor); a pressure sensor; an air pressure sensor; a gravimeter; a altimeter; an image capturing device (e.g., a camera or a lensless aperture); light detection and ranging (light detection and ranging, liDAR) sensors; proximity sensors (e.g., infrared radiation detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers; a microphone or other similar audio capturing device; etc.

EMC 822 includes a device, module, or subsystem whose purpose is to enable platform 800 to change its state, position, and/or orientation or to move or control a mechanical device or (subsystem). Furthermore, EMC 822 may be configured to generate and send messages/signaling to other components of platform 800 to indicate the current state of EMC 822. Examples of EMC 822 include one or more power switches, relays including electromechanical relays (electromechanical relay, EMR) and/or solid state relays (solid state relay, SSR), actuators (e.g., valve actuators, etc.), audible sound generators, visual alarms, motors (e.g., dc motors, stepper motors, etc.), wheels, propellers, claws, clamps, hooks, and/or other similar electromechanical components. In an embodiment, the platform 800 is configured to operate one or more EMCs 822 based on one or more captured events and/or instructions or control signals received from a service provider and/or various clients.

In some implementations, interface circuitry may connect platform 800 with positioning circuitry 845. The positioning circuitry 845 includes circuitry to receive and decode signals transmitted/broadcast by the positioning network of the GNSS. Examples of navigation satellite constellations (or GNSS) include GPS in the united states, GLONASS in russia, galileo system in the european union, beidou navigation satellite system in china, regional navigation system or GNSS augmentation system (e.g., NAVIC), QZSS in japan, DORIS in france, etc.), and so forth. The positioning circuitry 845 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc., to facilitate OTA communications) to communicate with components of the positioning network (e.g., navigation satellite constellation nodes). In some embodiments, the positioning circuitry 845 may include a Micro-PNT IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance. The location circuitry 845 may also be part of or interact with baseband circuitry and/or RFEM 815 to communicate with nodes and components of a location network. The positioning circuitry 845 may also provide location data and/or time data to the application circuitry 805, which the application circuitry 805 may use to operate in synchronization with various infrastructure (e.g., radio base stations), for route planning navigation applications, and so forth.

In some implementations, the interface circuitry may connect the platform 800 with Near-field communication (NFC) circuitry 840. NFC circuit 840 is configured to provide contactless short-range communications based on radio frequency identification (radio frequency identification, RFID) standards, wherein magnetic field induction is used to enable communications between NFC circuit 840 and an NFC-enabled device (e.g., an "NFC contact point") external to platform 800. NFC circuit 840 includes an NFC controller coupled with an antenna element and a processor coupled with the NFC controller. The NFC controller may be a chip/IC that provides NFC functionality to NFC circuit 840 by executing NFC controller firmware and an NFC stack. The NFC stack may be executable by the processor to control the NFC controller, and the NFC controller firmware may be executable by the NFC controller to control the antenna element to transmit the short range RF signal. The RF signal may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to send stored data to NFC circuit 840 or initiate a data transfer between NFC circuit 840 and another active NFC device (e.g., a smart phone or NFC-enabled POS terminal) proximate platform 800.

The driver circuit 846 may include software and hardware elements that operate to control specific devices embedded in the platform 800, attached to the platform 800, or otherwise communicatively coupled with the platform 800. The driver circuits 846 may include individual drivers to allow other components of the platform 800 to interact with or control various input/output (I/O) devices that may be present within the platform 800 or connected to the platform 800. For example, the driver circuitry 846 may include a display driver to control and allow access to the display device, a touch screen driver to control and allow access to a touch screen interface of the platform 800, a sensor driver to obtain sensor readings of the sensor circuitry 821 and to control and allow access to the sensor circuitry 821, an EMC driver to obtain actuator positions of the EMC 822 and/or to control and allow access to the EMC 822, a camera driver to control and allow access to the embedded image capture device, and an audio driver to control and allow access to one or more audio devices.

A power management integrated circuit (power management integrated circuitry, PMIC) 825 (also referred to as a "power management circuit 825") may manage power provided to the various components of the platform 800. Specifically, for baseband circuitry 810, pmic 825 may control power supply selection, voltage scaling, battery charging, or DC-to-DC conversion. PMIC 825 may often be included when platform 800 is capable of being powered by battery 830, for example, when the apparatus is included in UE 701.

In some embodiments, PMIC 825 may control or otherwise be part of various power saving mechanisms of platform 800. For example, if the platform 800 is in an RRC Connected state that is still Connected to the RAN node because it is expected to receive traffic soon, it may enter a state called discontinuous reception mode (Discontinuous Reception Mode, DRX) after a period of inactivity. During this state, the platform 800 may be powered down for a brief interval and thereby save power. If there is no data traffic activity for an extended period of time, the platform 800 may transition to an rrc_idle state in which it is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. Platform 800 enters a very low power state and it performs paging in which it wakes up again periodically to listen to the network and then powers down again. Platform 800 may not receive data in this state; in order to receive data, it must transition back to the rrc_connected state. The additional power saving mode may allow the device to be unavailable to the network for periods longer than the paging interval (varying from seconds to hours). During this time, the device is completely unreachable to the network and may be completely powered down. Any data transmitted during this time suffers from a large delay and this delay is assumed to be acceptable.

The battery 830 may power the platform 800, although in some examples the platform 800 may be installed and deployed in a fixed location and may have a power source coupled to a power transmission network. The battery 830 may be a lithium ion battery, a metal air battery, such as a zinc air battery, an aluminum air battery, a lithium air battery, and the like. In some implementations, for example in V2X applications, battery 830 may be a typical lead-acid automotive battery.

In some implementations, the battery 830 may be a "smart battery" that includes or is coupled to a battery management system (Battery Management System, BMS) or battery monitoring integrated circuit. A BMS may be included in the platform 800 to track a state of charge (SoCh) of the battery 830. The BMS may be configured to monitor other parameters of the battery 830 to provide failure predictions, such as state of health (SoH) and functional status (state of function, soF) of the battery 830. The BMS may communicate information of the battery 830 to the application circuitry 805 or other components of the platform 800. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 805 to directly monitor the voltage of the battery 830 or the current flowing from the battery 830. The battery parameters may be used to determine actions that platform 800 may perform, such as transmit frequency, network operation, sensing frequency, and so forth.

A power block or other power source coupled to the power transmission network may be coupled with the BMS to charge the battery 830. In some examples, the power supply block may be replaced with a wireless power receiver to obtain power wirelessly, such as through a loop antenna in computer platform 800. In these examples, a wireless battery charging circuit may be included in the BMS. The particular charging circuit selected may depend on the size of the battery 830 and thus on the current required. Charging may be performed using an airforce standard promulgated by the international wireless charging industry consortium (airforce Alliance), a Qi wireless charging standard promulgated by the wireless power consortium (Wireless Power Consortium), or a Rezence charging standard promulgated by the wireless power consortium (Alliance for Wireless Power), or the like.

User interface circuitry 850 includes various input/output (I/O) devices that reside within platform 800 or are connected to platform 800, and includes one or more user interfaces designed to enable a user to interact with platform 800 and/or peripheral component interfaces designed to enable peripheral components to interact with platform 800. The user interface circuit 850 includes an input device circuit and an output device circuit. The input device circuitry includes any physical or virtual device for accepting input, including, inter alia, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, and so forth. Output device circuitry includes any physical or virtual device for displaying information or otherwise conveying information, such as sensor readings, actuator position(s), or other similar information. The output device circuitry may include any number and/or combination of audio or visual displays, including, inter alia, one or more simple visual outputs/indicators (e.g., binary status indicators (e.g., light emitting diodes (light emitting diode, LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touch screens (e.g., liquid crystal displays (Liquid Chrystal Display, LCDs), LED displays, quantum dot displays, projectors, etc.), wherein the outputs of characters, graphics, multimedia objects, etc., are generated or produced from the operation of platform 800.

Although not shown, the components of platform 800 may communicate with each other using suitable bus or Interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, time-Trigger Protocol (TTP) systems, flexRay systems, or any number of other technologiesAnd (5) performing surgery. The bus/IX may be a proprietary bus/IX used in, for example, soC based systems. Other bus/IX systems may be included, e.g. I ² C interface, SPI interface, point-to-point interface and power bus, etc.

Fig. 9 illustrates example components of baseband circuitry 910 and radio front-end modules (radio front end module, RFEM) 915 in accordance with various embodiments. The baseband circuits 910 correspond to the baseband circuits 810 of fig. 8, respectively. RFEM 915 corresponds to RFEM 815 of fig. 8, respectively. As shown, RFEM 915 may include Radio Frequency (RF) circuitry 906, front-end module (FEM) circuitry 908, antenna array 911 coupled together at least as shown.

The baseband circuitry 910 includes circuitry and/or control logic configured to perform various radio/network protocols and radio control functions that enable communication with one or more radio networks via the RF circuitry 906. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency offset, and the like. In some embodiments, the modulation/demodulation circuitry of the baseband circuitry 910 may include Fast fourier transform (Fast-Fourier Transform, FFT), precoding, or constellation mapping/demapping functions. In some embodiments, the encoding/decoding circuitry of baseband circuitry 910 may include convolution, tail-biting convolution, turbo, viterbi (Viterbi), or Low density parity check (Low-Density Parity Check, LDPC) encoder/decoder functions. Embodiments of the modem and encoder/decoder functions are not limited to these examples and may include other suitable functions in other embodiments. The baseband circuitry 910 is configured to process baseband signals received from the receive signal path of the RF circuitry 906 and generate baseband signals for the transmit signal path of the RF circuitry 906. The baseband circuitry 910 is configured to interface with the application circuitry 805 (see fig. 8) to generate and process baseband signals and control the operation of the RF circuitry 906. The baseband circuitry 910 may handle various radio control functions.

The above-described circuitry and/or control logic of baseband circuitry 910 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 904A, a 4G/LTE baseband processor 904B,The 5G/NR baseband processor 904C or some other baseband processor(s) 904D for other existing generations, generations under development, or generations to be developed in the future (e.g., sixth generation (6G), etc.). In other embodiments, some or all of the functionality of the baseband processors 904A-D may be included in modules that are stored in the memory 904G and executed via a Central Processing Unit (CPU) 904E. In other embodiments, some or all of the functionality of the baseband processors 904A-D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with appropriate bit streams or logic blocks stored in the respective memory units. In various embodiments, memory 904G may store program code for a real-time OS (RTOS), which when executed by CPU 904E (or other baseband processor) will cause CPU 904E (or other baseband processor) to manage the resources of baseband circuitry 910, schedule tasks, and so forth. Examples of RTOS may include a method consisting of Embedded operating system (Operating System Embedded, OSE) ^TM From Mentor->Provided Nucleus RTOS ^TM From MentrorUniversal Real-Time execution (VRTX) provided by ExpressProvided ThreadX ^TM FreeRTOS, by +.>REX OS is provided by Open Kernel (OK)OKL4 provided, or any other suitable RTOS, such as those discussed herein. In addition, the baseband circuitry 910 includes oneOr a plurality of audio digital signal processors (digital signal processor, DSP) 904F. The audio DSP(s) 904F includes elements for compression/decompression and echo cancellation, and may include other suitable processing elements in other embodiments.

In some embodiments, each of processors 904A-904E includes a respective memory interface to send and receive data to and from memory 904G. The baseband circuitry 910 may also include one or more interfaces to communicatively couple to other circuits/devices, including, for example, interfaces to send/receive data to/from memory external to the baseband circuitry 910; the application circuit interface to send/receive data to/from the application circuit 805 of fig. 9; the RF circuit interface to send/receive data to/from the RF circuit 906 of fig. 9; a wireless hardware connectivity interface to/from one or more wireless hardware elements (e.g., near Field Communication (NFC) components, Low energy consumption->Assembly, & gtof>Components, etc.) transmit/receive data; and a power management interface to send/receive power or control signals to/from PMIC 825.

In alternative embodiments (which may be combined with the embodiments described above), baseband circuitry 910 includes one or more digital baseband systems coupled to each other and to the CPU subsystem, audio subsystem, and interface subsystem via an interconnect subsystem. The digital baseband subsystem may also be coupled to the digital baseband interface and mixed signal baseband subsystem via additional interconnect subsystems. Each interconnect subsystem may include a bus system, a point-to-point connection, a network-on-chip (NOC) architecture, and/or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include DSP circuitry, buffer memory, program memory, speech processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital-to-analog converter circuitry, analog circuitry including one or more amplifiers and filters, and/or other similar components. In an aspect of the disclosure, the baseband circuitry 910 may include protocol processing circuitry having one or more instances of control circuitry (not shown) to provide control functions for digital baseband circuitry and/or radio frequency circuitry (e.g., the radio front end module 915).

Although not shown in fig. 9, in some embodiments, baseband circuitry 910 includes individual processing device(s) to operate one or more wireless communication protocols (e.g., a "multi-protocol baseband processor" or "protocol processing circuit") and includes individual processing device(s) to implement PHY layer functions. In these embodiments, the PHY layer functions include the radio control functions described above. In these embodiments, the protocol processing circuitry operates or implements various protocol layers/entities of one or more wireless communication protocols. In a first example, the protocol processing circuitry may operate an LTE protocol entity and/or a 5G/NR protocol entity when the baseband circuitry 910 and/or the RF circuitry 906 are part of mmWave communication circuitry or some other suitable cellular communication circuitry. In a first example, the protocol processing circuitry will operate MAC, RLC, PDCP, SDAP, RRC and NAS functions. In a second example, the protocol processing circuitry may operate one or more IEEE-based protocols when the baseband circuitry 910 and/or the RF circuitry 906 are part of a Wi-Fi communication system. In a second example, the protocol processing circuitry will operate Wi-Fi MAC and logical link control (logical link control, LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g., 904G) to store program code and data to operate the protocol functions, and one or more processing cores to execute the program code and to perform various operations with the data. The baseband circuitry 910 may also support radio communications for more than one wireless protocol.

The various hardware elements of the baseband circuitry 910 discussed herein may be implemented, for example, as a solder-in substrate comprising one or more Integrated Circuits (ICs), a single packaged IC soldered to a main circuit board, or a multi-chip module comprising two or more ICs. In one example, the components of baseband circuitry 910 may be suitably combined in a single chip or chip set, or disposed on the same circuit board. In another example, some or all of the constituent components of baseband circuitry 910 and RF circuitry 906 may be implemented together as, for example, a System on a chip (SoC) or a System-in-Package (SiP). In another example, some or all of the constituent components of baseband circuitry 910 may be implemented as a separate SoC communicatively coupled with RF circuitry 906 (or multiple instances of RF circuitry 906). In another example, some or all of the constituent components of baseband circuitry 910 and application circuitry 805 may be implemented together as an individual SoC (e.g., a "multi-chip package") mounted to the same circuit board.

In some embodiments, baseband circuitry 910 may provide communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 910 may support communication with E-UTRAN or other WMAN, WLAN, WPAN. Embodiments in which the baseband circuitry 910 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

The RF circuitry 906 may enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, RF circuitry 906 may include switches, filters, amplifiers, and the like to facilitate communication with a wireless network. The RF circuitry 906 may include a receive signal path that may include circuitry to down-convert RF signals received from the FEM circuitry 908 and provide baseband signals to the baseband circuitry 910. The RF circuitry 906 may also include a transmit signal path that may include circuitry to up-convert baseband signals provided by the baseband circuitry 910 and provide RF output signals to the FEM circuitry 908 for transmission.

In some embodiments, the receive signal path of RF circuitry 906 may include mixer circuitry 906a, amplifier circuitry 906b, and filter circuitry 906c. In some embodiments, the transmit signal path of RF circuitry 906 may include filter circuitry 906c and mixer circuitry 906a. The RF circuitry 906 may also include synthesizer circuitry 906d for synthesizing frequencies for use by the mixer circuitry 906a of the receive signal path and the transmit signal path. In some embodiments, mixer circuit 906a of the receive signal path may be configured to down-convert the RF signal received from FEM circuit 908 based on the synthesized frequency provided by synthesizer circuit 906 d. The amplifier circuit 906b may be configured to amplify the down-converted signal and the filter circuit 906c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 910 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not a necessary requirement. In some embodiments, mixer circuit 906a of the receive signal path may comprise a passive mixer, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuit 906a of the transmit signal path may be configured to upconvert the input baseband signal based on a synthesized frequency provided by the synthesizer circuit 906d to generate an RF output signal for the FEM circuit 908. The baseband signal may be provided by baseband circuitry 910 and may be filtered by filter circuitry 906 c.

In some embodiments, the mixer circuit 906a of the receive signal path and the mixer circuit 906a of the transmit signal path may comprise two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 906a of the receive signal path and the mixer circuit 906a 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 circuit 906a of the receive signal path and the mixer circuit 906a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 906a of the receive signal path and the mixer circuit 906a of the transmit signal path may be configured for superheterodyne operation.

In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuitry 906 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 910 may include a digital baseband interface to communicate with the RF circuitry 906.

In some dual mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

In some embodiments, synthesizer circuit 906d may be a fractional-N synthesizer or a fractional-N/n+1 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 circuit 906d may be an incremental sum synthesizer, a frequency multiplier, or a synthesizer including a phase locked loop with a frequency divider.

Synthesizer circuit 906d may be configured to synthesize an output frequency for use by mixer circuit 906a of RF circuit 906 based on the frequency input and the divider control input. In some embodiments, the synthesizer circuit 906d may be a fractional N/n+1 synthesizer.

In some embodiments, the frequency input may be provided by a voltage-controlled oscillator (VCO), although this is not a necessary requirement. The divider control input may be provided by baseband circuitry 910 or application circuitry 805, depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on a channel indicated by application circuitry 805.

Synthesizer circuitry 906d of RF circuitry 906 may include frequency dividers, delay-locked loops (DLLs), multiplexers, and phase accumulators. In some embodiments, the frequency divider may be a dual-mode frequency divider (dual modulus divider, DMD) and the phase accumulator may be a digital phase accumulator (digital phase accumulator, DPA). In some embodiments, the DMD may be configured to divide the input signal by N or n+1 (e.g., based on the carry out) to provide a fractional divide ratio. In some example embodiments, a 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 divide the VCO period into Nd equal phase packets, 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.

In some embodiments, synthesizer circuit 906d 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 a quadrature generator and divider circuit to generate a plurality of signals having a plurality of different phases from one another at the carrier frequency. In some embodiments, the output frequency may be an LO frequency (fLO). In some embodiments, the RF circuitry 906 may include an IQ/polarity converter.

The FEM circuitry 908 may include a receive signal path, which may include circuitry configured to operate on RF signals received from the antenna array 911, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 906 for further processing. The FEM circuitry 908 may also include a transmit signal path, which may include circuitry configured to amplify signals provided by the RF circuitry 906 for transmission by one or more antenna elements of the antenna array 911. In various embodiments, amplification through the transmit or receive signal path may be accomplished in only RF circuitry 906, only FEM 908, or in both RF circuitry 906 and FEM 908.

In some embodiments, FEM circuitry 908 may include TX/RX switches to switch between transmit and receive mode operation. The FEM circuitry 908 may include a receive signal path and a transmit signal path. The receive signal path of FEM circuitry 908 may include an LNA to amplify the received RF signal and provide an amplified received RF signal as an output (e.g., to RF circuitry 906). The transmit signal path of FEM circuitry 908 may include a Power Amplifier (PA) to amplify an input RF signal (e.g., provided by RF circuitry 906) and one or more filters to generate an RF signal for subsequent transmission by one or more antenna elements of antenna array 911.

The antenna array 911 includes one or more antenna elements, each configured to convert an electrical signal into a radio wave to travel through air and to convert a received radio wave into an electrical signal. For example, digital baseband signals provided by the baseband circuitry 910 are converted to analog RF signals (e.g., modulated waveforms) that are to be amplified and transmitted via antenna elements of the antenna array 911, including one or more antenna elements (not shown). The antenna elements may be omni-directional, or a combination of these. The antenna elements may be formed in a variety of arrangements known and/or discussed herein. The antenna array 911 may include a microstrip antenna or printed antenna fabricated on a surface of one or more printed circuit boards. The antenna array 911 may be formed of metal foil (e.g., patch antenna) in a variety of shapes and may be coupled to the RF circuitry 906 and/or FEM circuitry 908 using metal transmission lines or the like.

The processor of the application circuitry 805 and the processor of the baseband circuitry 910 may be used to execute elements of one or more instances of a protocol stack. For example, the processor of baseband circuitry 910 may be used, alone or in combination, to perform layer 3, layer 2, or layer 1 functions, while the processor of application circuitry 805 may utilize data (e.g., packet data) received from these layers and further perform layer 4 functions (e.g., TCP and UDP layers). For the purposes mentioned herein, layer 3 may comprise an RRC layer, which is described in more detail below. For the purposes mentioned herein, layer 2 may include a MAC layer, an RLC layer, and a PDCP layer, which are described in more detail below. For the purposes mentioned herein, layer 1 may include the PHY layer of the UE/RAN node, which is described in more detail below.

Fig. 10 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some example embodiments. In particular, fig. 10 shows a diagram of a hardware resource 1000, the hardware resource 1000 including one or more processors (or processor cores) 1010, one or more memory/storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040. For embodiments that utilize node virtualization (e.g., NFV), hypervisor (hypervisor) 1002 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize hardware resources 1000.

The processor 1010 may include, for example, a processor 1012 and a processor 1014. The processor(s) 1010 may be, for example, a central processing unit (central processing unit, CPU), a reduced instruction set computing (reduced instruction set computing, RISC) processor, a complex instruction set computing (complex instruction set computing, CISC) processor, a graphics processing unit (graphics processing unit, GPU), DSP, ASIC, FPGA such as a baseband processor, a radio-frequency integrated circuit (radio-frequency integrated circuit, RFIC), another processor (including those discussed herein), or any suitable combination of these.

Memory/storage 1020 may include main memory, disk storage, or any suitable combination of these. Memory/storage 1020 may include, but is 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 (electrically erasable programmable read-only memory, EEPROM), flash memory, solid state memory devices, and the like.

The communication resources 1030 may include interconnections or network interface components or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1006 via the network 1008. For example, the communication resources 1030 may include wired communication components (e.g., for coupling via USB), cellular communication components, NFC components, and so forth,(or low energy consumption)) Assembly, & gtof>Components and other communication components.

The instructions 1050 may include software, programs, applications, applets, apps, or other executable code for causing at least any one of the processors 1010 to perform any one or more of the methods discussed herein. The instructions 1050 may reside, completely or partially, within at least one of the processor 1010 (e.g., within a cache memory of the processor), the memory/storage 1020, or any suitable combination of these. Further, any portion of the instructions 1050 may be transferred from any combination of the peripheral 1004 or database 1006 to the hardware resource 1000. Accordingly, the memory of the processor 1010, the memory/storage 1020, the peripheral devices 1004, and the database 1006 are examples of computer-readable and machine-readable media.

Fig. 11 provides an example illustration of a wireless device, such as a User Equipment (UE), mobile Station (MS), mobile wireless device, mobile communication device, tablet, handset, or other type of wireless device. The wireless device may include one or more antennas configured to communicate with a Node, macro Node, low Power Node (LPN), or transmitting station, such as a Base Station (BS), evolved Node B (eNB), baseband processing unit (baseband processing unit, BBU), remote radio head (remote radio head, RRH), remote radio (remote radio equipment, RRE), relay Station (RS), radio Equipment (RE), or other type of wireless wide area network (wireless wide area network, WWAN) access point. The wireless device may be configured to communicate using at least one wireless communication standard, such as, but not limited to, 3GPP LTE, wiMAX, high speed packet access (High Speed Packet Access, HSPA), bluetooth, and WiFi. The wireless device may communicate by utilizing a separate antenna for each wireless communication standard or a shared antenna for multiple wireless communication standards. The wireless device may communicate in a wireless local area network (wireless local area network, WLAN), a wireless personal area network (wireless personal area network, WPAN), and/or WWAN. The wireless device may also include a wireless modem. The wireless modem may include, for example, a wireless radio transceiver and baseband circuitry (e.g., a baseband processor). In one example, a wireless modem may modulate signals transmitted by a wireless device via one or more antennas and demodulate signals received by the wireless device via one or more antennas.

Fig. 11 also provides an illustration of a microphone and one or more speakers that may be used for audio input and output from the wireless device. The display screen may be a liquid crystal display (liquid crystal display, LCD) screen, or other type of display screen, such as an organic light emitting diode (organic light emitting diode, OLED) display. The display screen may be configured as a touch screen. Touch screens may use capacitive, resistive, or another type of touch screen technology. The application processor and graphics processor may be coupled to an internal memory to provide processing and display capabilities. The non-volatile memory port may also be used to provide data input/output options to the user. Non-volatile memory ports may also be used to extend the memory capabilities of the wireless device. The keyboard may be integrated with the wireless device or wirelessly connected to the wireless device to provide additional user input. A virtual keyboard may also be provided using a touch screen.

Figure 12 illustrates an example architecture of a system 1200 including a first CN 1220, according to various embodiments. In this example, the system 1200 may implement the LTE standard, where the CN 1220 is the EPC 1220 corresponding to the CN 720 of fig. 7. Further, UE 1201 may be the same or similar to UE 701 of fig. 7, and E-UTRAN 1210 may be the same or similar to RAN 710 of fig. 7, and may include RAN node 711 previously discussed. CN 1220 may include MME 1221, S-GW 1222, P-GW 1223, HSS 1224, and SGSN 1225.

MME 1221 may be similar in function to the control plane of a legacy SGSN and may implement MM functionality to keep track of the current location of UE 1201. MME 1221 may perform various MM procedures to manage mobility aspects in the access, such as gateway selection and tracking area list management. MM (also referred to as "EPS MM" or "EMM" in an E-UTRAN system) may refer to all applicable procedures, methods, data storage, etc. for maintaining knowledge about the current location of the UE 1201, providing user identity confidentiality to users/subscribers, and/or performing other similar services. Each UE 1201 and MME 1221 may include an MM or EMM sub-layer, and when the attach procedure is successfully completed, an MM context may be established in the UE 1201 and MME 1221. The MM context may be a data structure or database object storing MM related information of the UE 1201. MME 1221 may be coupled with HSS 1224 via an S6a reference point, SGSN 1225 via an S3 reference point, and S-GW 1222 via an S11 reference point.

SGSN 1225 may be a node serving individual UEs 1201 by tracking the location of UEs 1201 and performing security functions. In addition, the SGSN 1225 may perform EPC inter-node signaling for mobility between 2G/3G and E-UTRAN 3GPP access networks; PDN and S-GW selection specified by MME 1221; processing of the UE 1201 time zone function specified by the MME 1221; and MME selection for handover to E-UTRAN 3GPP access networks. The S3 reference point between MME 1221 and SGSN 1225 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle and/or active states.

HSS 1224 may include a database for network users including subscription related information to support the handling of communication sessions by network entities. EPC 1220 may include one or several HSS 1224, depending on the number of mobile subscribers, the capacity of the device, the organization of the network, and so on. For example, HSS 1224 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location compliance, and so forth. The S6a reference point between the HSS 1224 and the MME 1221 may enable the transfer of subscription and authentication data to authenticate/authorize user access to the EPC 1220 between the HSS 1224 and the MME 1221.

The S-GW 1222 may terminate an S1 interface 713 (S1-U in fig. 12) towards the RAN 1210 and route data packets between the RAN 1210 and the EPC 1220. Furthermore, S-GW 1222 may be a local mobility anchor point for inter-RAN node handover and may also provide anchoring for inter-3 GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement. The S11 reference point between S-GW 1222 and MME 1221 may provide a control plane between MME 1221 and S-GW 1222. S-GW 1222 may be coupled with P-GW 1223 via an S5 reference point.

The P-GW 1223 may terminate the SGi interface towards the PDN 1230. P-GW 1223 may route data packets between EPC 1220 and external networks, such as a network including application server 730 (or referred to as "AF"), via IP interface 725 (see, e.g., fig. 7). In an embodiment, P-GW 1223 may be communicatively coupled to an application server (application server 730 of fig. 7 or PDN 1230 of fig. 12) via IP communication interface 725 (see, e.g., fig. 7). The S5 reference point between P-GW 1223 and S-GW 1222 may provide user plane tunneling and tunnel management between P-GW 1223 and S-GW 1222. The S5 reference point may also be used for S-GW 1222 relocation due to UE 1201 mobility and if at S-GW 1222 it is required to connect to non-co-located P-GW 1223 for required PDN connectivity. The P-GW 1223 may also include nodes for policy enforcement and charging data collection (e.g., PCEF (not shown)) furthermore, the SGi reference point between the P-GW 1223 and the packet data network (packet data network, PDN) 1230 may be an operator external public, private PDN or an operator intra packet data network, e.g., in order to provide IMS services. The P-GW 1223 may be coupled with the PCRF 1226 via a Gx reference point.

PCRF 1226 is the policy and charging control element of EPC 1220. In a non-roaming scenario, there may be a single PCRF 1226 in the home public land mobile network (Home Public Land Mobile Network, HPLMN) associated with the internet protocol connectivity access network (Internet Protocol Connectivity Access Network, IP-CAN) session of the UE 1201. In a roaming scenario with local traffic disruption, there may be two PCRFs associated with the IP-CAN session of UE 1201: a Home PCRF (H-PCRF) within the HPLMN and a Visited PCRF (V-PCRF) within the Visited public land mobile network (Visited Public Land Mobile Network, VPLMN). PCRF 1226 may be communicatively coupled to application server 1230 via P-GW 1223. Application server 1230 may signal PCRF 1226 to indicate the new service flow and select the appropriate QoS and charging parameters. PCRF 1226 may provision this rule into a PCEF (not shown) using the appropriate TFT and QCI, which begins QoS and charging specified by application server 1230. The Gx reference point between PCRF 1226 and P-GW 1223 may allow QoS policies and charging rules to be communicated from PCRF 1226 to the PCEF in P-GW 1223. An Rx reference point may exist between the PDN 1230 (or "AF 1230") and the PCRF 1226.

For one or more embodiments, at least one of the components recited in one or more of the preceding figures may be configured to perform one or more operations, techniques, procedures, and/or methods recited in the following example section. For example, the baseband circuitry described above in connection with one or more of the preceding figures may be configured to operate according to one or more examples set forth below. As another example, circuitry associated with a UE, base station, network element, etc., described above in connection with one or more of the preceding figures, can be configured to operate in accordance with one or more examples set forth in the examples section below.

Example

The following examples relate to particular technical embodiments and are indicative of particular features, elements, or actions that may be employed or otherwise combined in implementing such embodiments.

Example 1 includes an apparatus of a User Equipment (UE) operable for conflict resolution between a UE-initiated signal and a page from a Mobile Terminated (MT) Circuit Switched (CS) service of a third generation partnership project (3 GPP) network, the apparatus comprising: one or more processors configured to: initiating a UE initiation procedure at the UE, wherein the UE initiation procedure is one or more of a Tracking Area Update (TAU) procedure, an International Mobile Subscriber Identity (IMSI) detach procedure, or a Routing Area Update (RAU) procedure; decoding, at the UE, a CS paging procedure from a target Base Station (BS) prior to completion of the UE-initiated procedure, wherein the CS paging procedure is one or more of a CS service notification or a CS paging request; and completing the UE originated procedure at the UE prior to responding to the CS paging procedure; and a memory interface configured to store the CS paging procedure in memory.

Example 2 includes the apparatus of example 1, wherein the one or more processors are further configured to: when the UE-initiated procedure is the TAU procedure, after completion of the UE-initiated procedure, an extended service request message responsive to the CS service notification is encoded at the UE for transmission to a Mobility Management Entity (MME).

Example 3 includes the apparatus of example 2, wherein the one or more processors are further configured to: the UE initiation procedure is initiated at the UE when a Tracking Area Identifier (TAI) change occurs at the UE.

Example 4 includes the apparatus of example 2, wherein the one or more processors are further configured to: initiating the UE initiation procedure at the UE upon occurrence of one or more of: local Evolved Packet System (EPS) bearer context deactivation, local Packet Data Protocol (PDP) context deactivation, voice domain preference change, discontinuous Reception (DRX) parameter change, or load balancing at the MME.

Example 5 includes the apparatus of any one of examples 2-4, wherein the one or more processors are further configured to: and when the UE receives a TAU acceptance message or the UE transmits a TAU completion message, identifying that the UE initiating process is completed at the UE.

Example 6 includes the apparatus of example 1, wherein the one or more processors are further configured to: when the UE-initiated procedure is the IMSI detach procedure, the UE-initiated procedure is completed at the UE without sending a response to the CS service notification.

Example 7 includes the apparatus of example 1, wherein the one or more processors are further configured to: when the UE-initiated procedure is the RAU procedure, after the UE-initiated procedure is completed, a paging response message responsive to the CS paging request is encoded for transmission to a serving General Packet Radio Service (GPRS) support node (SGSN).

Example 8 includes the apparatus of example 7, wherein the one or more processors are further configured to: the UE initiation procedure is initiated at the UE when a Routing Area Identity (RAI) change occurs at the UE.

Example 9 includes the apparatus of example 7, wherein the one or more processors are further configured to: initiating the UE initiation procedure at the UE upon one or more of: local Packet Data Protocol (PDP) context deactivation, voice domain preference changes, discontinuous Reception (DRX) parameters changes, or MS network capability information changes.

Example 10 includes the apparatus of any of examples 7-9, wherein the one or more processors are further configured to: and when the UE receives the RAU acceptance message or the UE sends the RAU completion message, identifying that the UE initiation process is completed at the UE.

Example 11 includes the apparatus of any of examples 1-6, wherein the 3GPP network is a Long Term Evolution (LTE) network.

Example 12 includes the apparatus of any of examples 7-9, wherein the 3GPP network is a second generation (2G) or third generation (3G) network.

Example 13 includes an apparatus of a Mobility Management Entity (MME) operable for conflict resolution between a User Equipment (UE) -initiated signal and a page from a Mobile Terminated (MT) Circuit Switched (CS) service of a third generation partnership project (3 GPP) Long Term Evolution (LTE) network, the apparatus comprising: one or more processors configured to: encoding a CS paging procedure at the MME for transmission to a UE via an evolved node B (eNB), wherein the CS paging procedure is a CS service notification; decoding, at the MME, a UE-initiated procedure before a response to the CS paging procedure is received, wherein the UE-initiated procedure is a TAU procedure; at the MME, encoding a Tracking Area Update (TAU) accept message for transmission to the UE via the eNB; decoding, at the MME, a TAU complete message upon receiving the TAU complete message from the UE; and after the UE-initiated procedure is completed, decoding, at the MME, an extended service request message received from the UE in response to the CS service notification; and a memory interface configured to retrieve the CS paging procedure from memory.

Example 14 includes the apparatus of example 13, wherein the one or more processors are further configured to: and when the MME sends the TAU acceptance message or the MME receives the TAU completion message, identifying that the UE initiation process is completed at the MME.

Example 15 includes at least one machine-readable storage medium having instructions embodied thereon for a UE to initiate conflict resolution between a signal and a page from a Mobile Terminated (MT) Circuit Switched (CS) service of a third generation partnership project (3 GPP) Long Term Evolution (LTE) network, the instructions when executed by one or more processors at a User Equipment (UE) perform the operations of: initiating a UE initiation procedure at the UE, wherein the UE initiation procedure is one or more of a Tracking Area Update (TAU) procedure, an International Mobile Subscriber Identity (IMSI) detach procedure, or a Routing Area Update (RAU) procedure; decoding, at the UE, a CS paging procedure from a target evolved node B (eNB) prior to completion of the UE-initiated procedure, wherein the CS paging procedure is one or more of a CS service notification or a CS paging request; and completing the UE initiated procedure at the UE prior to responding to the CS paging procedure.

Example 16 includes the at least one machine-readable storage medium of example 15, further comprising instructions that when executed perform the following: when the UE-initiated procedure is the TAU procedure, after completion of the UE-initiated procedure, an extended service request message responsive to the CS service notification is encoded at the UE for transmission to a Mobility Management Entity (MME).

Example 17 includes the at least one machine-readable storage medium of example 16, further comprising instructions that when executed perform the following: the UE initiation procedure is initiated at the UE when a Tracking Area Identifier (TAI) change occurs at the UE.

Example 18 includes the at least one machine-readable storage medium of example 16, further comprising instructions that when executed perform the following: initiating the UE initiation procedure at the UE upon one or more of: local EPS bearer context deactivation, local Packet Data Protocol (PDP) context deactivation, voice domain preference change, discontinuous Reception (DRX) parameter change, or load balancing at the MME.

Example 19 includes the at least one machine-readable storage medium of example 16, further comprising instructions that when executed perform the following: and when the UE receives a TAU acceptance message or the UE sends a TAU completion message, identifying that the UE initiation process is completed at the UE.

Example 20 includes the at least one machine-readable storage medium of any of examples 16 to 18, further comprising instructions that when executed perform the following: when the UE-initiated procedure is the IMSI detach procedure, the UE-initiated procedure is completed at the UE without sending a response to the CS service notification.

The various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disk-read-only memories (CD-ROMs), hard drives, non-transitory computer-readable storage media, or any other machine-readable storage medium, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. In the case of program code execution on programmable computers, the computing device will include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and nonvolatile memory and/or storage elements may be random-access memory (RAM), erasable programmable read-only memory (erasable programmable read only memory, EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. The node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or a timer module (i.e., timer). In one example, selected components of the transceiver module may be located in a cloud radio access network (cloud radio access network, C-RAN). One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (application programming interface, API), reusable controls, and so forth. Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.

As used herein, the term "circuitry" may refer to, be part of, or include the following items: an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in or the functionality associated with one or more software or firmware modules. In some embodiments, the circuitry may comprise logic that is at least partially operable in hardware.

It should be appreciated that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom Very Large Scale Integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. However, the executables of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices. The modules may be passive or active, including agents operable to perform desired functions.

Reference throughout this specification to "an example" or "exemplary" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present technology. Thus, appearances of the phrase "in an example" or the word "exemplary" in various places throughout this specification are not necessarily all referring to the same embodiment.

As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as if each member of the list is individually identified as a separate and unique member. Thus, individual members of such a list should not be interpreted as being equivalent to any other member of the same list merely based on the fact that they are presented in a common group, if not indicated to the contrary. Furthermore, various embodiments and examples of the present technology may be referred to herein along with alternatives to its various components. It is to be understood that such embodiments, examples, and alternatives are not to be construed as being actual equivalents of each other, but are to be considered separate and autonomous representations of the present technology.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of arrangements, distances, network examples, etc., to provide a thorough understanding of embodiments of the present technology. One skilled in the relevant art will recognize, however, that the technology can be practiced without one or more of the specific details, or with other methods, components, arrangements, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the technology.

While the foregoing examples illustrate the principles of the technology in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and implementation details can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the technology. Accordingly, it is not intended that the present technology be limited except as by the claims set forth below.

Claims

1. An apparatus of a User Equipment (UE) operable for conflict resolution between a UE-initiated signal and a page from a Mobile Terminated (MT) Circuit Switched (CS) service of a third generation partnership project (3 GPP) network, the apparatus comprising:

one or more processors configured to:

initiating a UE initiation procedure at the UE, wherein the UE initiation procedure is one or more of a Tracking Area Update (TAU) procedure, an International Mobile Subscriber Identity (IMSI) detach procedure, or a Routing Area Update (RAU) procedure;

decoding, at the UE, a CS paging procedure from a target Base Station (BS) prior to completion of the UE-initiated procedure, wherein the CS paging procedure is one or more of a CS service notification or a CS paging request; and is also provided with

Completing the UE-initiated procedure at the UE prior to responding to the CS paging procedure; and

A memory interface configured to store the CS paging procedure in memory.

2. The apparatus of claim 1, wherein the one or more processors are further configured to:

when the UE-initiated procedure is the TAU procedure, after completion of the UE-initiated procedure, an extended service request message responsive to the CS service notification is encoded at the UE for transmission to a Mobility Management Entity (MME).

3. The apparatus of claim 2, wherein the one or more processors are further configured to:

the UE initiation procedure is initiated at the UE when a Tracking Area Identifier (TAI) change occurs at the UE.

4. The apparatus of claim 2, wherein the one or more processors are further configured to:

initiating the UE initiation procedure at the UE upon one or more of:

local Evolved Packet System (EPS) bearer context deactivation,

local Packet Data Protocol (PDP) context deactivation,

the voice domain preference is changed and,

discontinuous Reception (DRX) parameter variation, or

Load balancing at the MME.

5. The apparatus of any one of claims 2 to 4, wherein the one or more processors are further configured to:

And when the UE receives a TAU acceptance message or the UE sends a TAU completion message, identifying that the UE initiation process is completed at the UE.

6. The apparatus of claim 1, wherein the one or more processors are further configured to:

when the UE-initiated procedure is the IMSI detach procedure, the UE-initiated procedure is completed at the UE without sending a response to the CS service notification.

7. The apparatus of claim 1, wherein the one or more processors are further configured to:

when the UE-initiated procedure is the RAU procedure, after the UE-initiated procedure is completed, a paging response message responsive to the CS paging request is encoded for transmission to a serving General Packet Radio Service (GPRS) support node (SGSN).

8. The apparatus of claim 7, wherein the one or more processors are further configured to:

the UE initiation procedure is initiated at the UE when a Routing Area Identity (RAI) change occurs at the UE.

9. The apparatus of claim 7, wherein the one or more processors are further configured to:

initiating the UE initiation procedure at the UE upon one or more of:

Local Packet Data Protocol (PDP) context deactivation,

the voice domain preference is changed and,

discontinuous Reception (DRX) parameter variation, or

MS network capability information changes.

10. The apparatus of any one of claims 7 to 9, wherein the one or more processors are further configured to:

and when the UE receives the RAU acceptance message or the UE sends the RAU completion message, identifying that the UE initiation process is completed at the UE.

11. The apparatus of any of claims 1 to 6, wherein the 3GPP network is a Long Term Evolution (LTE) network.

12. The apparatus of any of claims 7 to 9, wherein the 3GPP network is a second generation (2G) or third generation (3G) network.

13. An apparatus of a Mobility Management Entity (MME) operable for conflict resolution between a User Equipment (UE) -initiated signal and a page from a Mobile Terminated (MT) Circuit Switched (CS) service of a third generation partnership project (3 GPP) Long Term Evolution (LTE) network, the apparatus comprising:

one or more processors configured to:

at the MME, encoding a CS paging procedure for transmission to a UE via an evolved node B (eNB), wherein the CS paging procedure is a CS service notification;

Decoding, at the MME, a UE-initiated procedure before a response to the CS paging procedure is received, wherein the UE-initiated procedure is a TAU procedure;

at the MME, encoding a Tracking Area Update (TAU) accept message for transmission to the UE via the eNB;

decoding, at the MME, a TAU complete message upon receiving the TAU complete message from the UE; and is also provided with

Decoding, at the MME, an extended service request message received from the UE in response to the CS service notification after the UE initiated procedure is completed; and

a memory interface configured to retrieve the CS paging procedure from memory.

14. The apparatus of claim 13, wherein the one or more processors are further configured to:

and when the MME sends the TAU acceptance message or the MME receives the TAU completion message, identifying that the UE initiation process is completed at the MME.

15. At least one machine-readable storage medium having instructions embodied thereon for UE initiated conflict resolution between a signal and a page from a Mobile Terminated (MT) Circuit Switched (CS) service of a third generation partnership project (3 GPP) Long Term Evolution (LTE) network, the instructions when executed by one or more processors at a User Equipment (UE) perform the operations of:

decoding, at the UE, a CS paging procedure from a target evolved node B (eNB) prior to completion of the UE-initiated procedure, wherein the CS paging procedure is one or more of a CS service notification or a CS paging request; and is also provided with

The UE-initiated procedure is completed at the UE prior to responding to the CS paging procedure.

16. The at least one machine readable storage medium of claim 15, further comprising instructions that when executed perform the following:

17. The at least one machine readable storage medium of claim 16, further comprising instructions that when executed perform the following:

18. The at least one machine readable storage medium of claim 16, further comprising instructions that when executed perform the following:

initiating the UE initiation procedure at the UE upon one or more of:

the local EPS bearer context is deactivated,

local Packet Data Protocol (PDP) context deactivation,

the voice domain preference is changed and,

discontinuous Reception (DRX) parameter variation, or

Load balancing at the MME.

19. The at least one machine readable storage medium of claim 16, further comprising instructions that when executed perform the following:

20. The at least one machine readable storage medium of any one of claims 16 to 18, further comprising instructions that when executed perform the following: