User plane early data transmission (EDT) message 4 (MSG4) loss

Technology is disclosed for an evolved node B (eNB) operable for early data transmission (EDT) in a user plane (UP) in a cellular internet of things (CIoT) evolved 5 packet system (EPS) network. The eNB can be configured to encode, at the eNB for transmission to a user equipment (UE), a message 4 (Msg4) including a resume identifier (ID) and a next-hop chaining count (NCC). The eNB can be configured to determine, at the eNB, a delivery status of the Msg4 to the UE. The eNB can be configured to encode, at the eNB for transmission to a previous eNB of the UE, one or more of an EDT failure 10 indicator or the resume ID.

BACKGROUND

Wireless systems typically include multiple User Equipment (UE) devices communicatively coupled to one or more Base Stations (BS). The one or more BSs may be Long Term Evolved (LTE) evolved NodeBs (eNB) or new radio (NR) NodeBs (gNB), next generation node Bs (gNB), or new radio base stations (NR BS) that can be communicatively coupled to one or more UEs by a Third-Generation Partnership Project (3GPP) network.

Next generation wireless communication systems are expected to be a unified network/system that is targeted to meet vastly different and sometimes conflicting performance dimensions and services. New Radio Access Technology (RAT) is expected to support a broad range of use cases including Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), Mission Critical Machine Type Communication (uMTC), and similar service types operating in frequency ranges up to 100 GHz.

Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the technology is thereby intended.

DETAILED DESCRIPTION

Example Embodiments

In Long Term Evolution (LTE), the Early Data Transmission (EDT) procedure for User Plane (UP) Consumer Internet of Things (CIoT) evolved packet system (EPS) optimization has been specified, see Third Generation Partnership Project (3GPP) Technical Specification (TS) 36.300 Section 7.3b.3. This procedure can be modified to support resuming on a new evolved node B (eNB) different from the old eNB where the connection was suspended.

During this EDT procedure, it is possible that cell reselection occurs or timer T300 expires after sending a (Message 3) Msg3 resume request or the user equipment (UE) may have missed the Message 4 (Msg4) that can include information for EDT (e.g., new NextHop Chaining Count (NCC), new Resume ID). But it does not affect the functionality if the UE resumes on the same eNB where the Msg4 was lost on the next time because the same eNB can use the old NCC or the old resume ID because it may be aware of unsuccessful Msg4 delivery.

However, the loss of Msg4 can affect the functionality when the UE resumes on an eNB that is different from the eNB where the Msg4 was lost. The eNB on which the Msg4 failed already became the new anchor after path switch, but because of unsuccessful Msg4 delivery, the UE may still use the old NCC or old resume ID received from the old anchor eNB for subsequent resumptions. As a result, the eNB (e.g., a third eNB that is different from the new anchor eNB and old anchor eNB) that receives the Msg3 request from the UE can trigger a context retrieval procedure onto the previous anchor before that path switch happened (e.g., the old anchor) because the UE signals based on the old resume ID associated with the old anchor eNB. However, the UE context has been already released as part of that path switch procedure, which may unnecessarily trigger the UE to fallback to IDLE or limit the UE to use UP CIoT EDT only when the UE successfully receives Msg4.

The issue can be on the network (NW) side because an eNB may not be able to point to the correct anchor because of the legacy UP EDT structure in which path switch occurs before Msg4 can be sent. Therefore, permitting the NW to continue UP EDT without limiting the UE to fallback to IDLE or unnecessarily limiting its applicability is desirable.

In one example, in a scenario including unsuccessful Msg4 delivery, the new anchor after path switch can send an EDT failure indication and a Resume ID to the previous anchor before the path switch to enable the UE to use RRC_CONNECTED mode instead of sending reject message to the UE.

In one example, in a scenario including unsuccessful Msg4 delivery, the previous anchor before the path switch can forward a new resumption request to the new anchor after the path switch. This RAN-based solution can enable the NW nodes to pinpoint the correct anchor to continue the EDT procedure without involving the core network (CN). This approach can have a minimal stage-2 impact but may require a complicated handling in the radio access network (RAN) with some stage-3 impacts on the existing X2 Application Protocol (X2-AP) messages to support this approach.

In one example, in a scenario including unsuccessful Msg4 delivery, the new anchor after the path switch can trigger to revert back the anchoring to previous anchor before the path switch. This CN-involved solution can revert the termination point of the de-activated evolved packet system (EPS) bearer back to the previous anchor before the path switch. This approach can have a minimal RAN impact but can impact some stage-3 efforts on X2-AP with significant stage-2 impacts. Also, this approach may not be efficient in case the UE resumes on the new anchor next time.

In one example, the UE can be released without anchor relocation. This approach can avoid the situation in advance by not relocating the anchor, but its applicability can be limited because the previous anchor may not have information in advance related to the success of Msg4 from the new eNB.

These alternative NW mechanisms are approaches that can limit UE impact, without limiting the feature applicability of the UE or wasting the UE's power.

In one example, an apparatus of an evolved node B (eNB) can be operable for early data transmission (EDT) in a user plane (UP) in a cellular internet of things (CIoT) evolved packet system (EPS) network. The apparatus can comprise one or more processors. The one or more processors can be configured to encode, at the eNB for transmission to a user equipment (UE), a message 4 (Msg4) including a resume identifier (ID) and a next-hop chaining count (NCC). The one or more processors can be configured to determine, at the eNB, a delivery status of the Msg4 to the UE. The one or more processors can be configured to encode, at the eNB for transmission to a previous eNB of the UE, one or more of an EDT failure indicator or the resume ID. The eNB can further comprise a memory interface configured to store the Msg4 in a memory.

FIG.1provides an example of a 3GPP NR Release 15 frame structure. In particular,FIG.1illustrates a downlink radio frame structure. In the example, a radio frame100of a signal used to transmit the data can be configured to have a duration, Tf, of 10 milliseconds (ms). Each radio frame can be segmented or divided into ten subframes110ithat are each 1 ms long. Each subframe can be further subdivided into one or multiple slots120a,120i, and120x, each with a duration, Tslot, of 1/μ ms, where μ=1 for 15 kHz subcarrier spacing, μ=2 for 30 kHz, μ=4 for 60 kHz, μ=8 for 120 kHz, and μ=16 for 240 kHz. Each slot can include a physical downlink control channel (PDCCH) and/or a physical downlink shared channel (PDSCH).

Each slot for a component carrier (CC) used by the node and the wireless device can include multiple resource blocks (RBs)130a,130b,130i,130m, and130nbased on the CC frequency bandwidth. The CC can have a carrier frequency having a bandwidth. Each slot of the CC can include downlink control information (DCI) found in the PDCCH. The PDCCH is transmitted in control channel resource set (CORESET) which can include one, two or three Orthogonal Frequency Division Multiplexing (OFDM) symbols and multiple RBs.

Each RB (physical RB or PRB) can include 12 subcarriers (on the frequency axis) and14orthogonal frequency-division multiplexing (OFDM) symbols (on the time axis) per slot. The RB can use 14 OFDM symbols if a short or normal cyclic prefix is employed. The RB can use 12 OFDM symbols if an extended cyclic prefix is used. The resource block can be mapped to 168 resource elements (REs) using short or normal cyclic prefixing, or the resource block can be mapped to 144 REs (not shown) using extended cyclic prefixing. The RE can be a unit of one OFDM symbol142by one subcarrier (i.e., 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz)146.

Each RE140ican transmit two bits150aand150bof information in the case of quadrature phase-shift keying (QPSK) modulation. Other types of modulation may be used, such as 16 quadrature amplitude modulation (QAM) or 64 QAM to transmit a greater number of bits in each RE, or bi-phase shift keying (BPSK) modulation to transmit a lesser number of bits (a single bit) in each RE. The RB can be configured for a downlink transmission from the NR BS to the UE, or the RB can be configured for an uplink transmission from the UE to the NR BS.

This example of the 3GPP NR Release 15 frame structure provides examples of the way in which data is transmitted, or the transmission mode. The example is not intended to be limiting. Many of the Release 15 features will evolve and change in the 5G frame structures included in 3GPP LTE Release 15, MulteFire Release 1.1, and beyond. In such a system, the design constraint can be on co-existence with multiple 5G numerologies in the same carrier due to the coexistence of different network services, such as eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type Communications or massive IoT) and URLLC (Ultra Reliable Low Latency Communications or Critical Communications). The carrier in a 5G system can be above or below 6 GHz. In one embodiment, each network service can have a different numerology.

In another example, as depicted inFIG.2, a call flow for EDT when resuming in new eNB can include: a random access preamble transmitted from a UE210to a new eNB220, as in operation202; and a random access response transmitted from the new eNB220to the UE210, as in operation204.

In another example, an RRCConnectionResume Request can include one or more of a resume identifier (ID), a resumeCause, or a shortResumeMAC-I. The RRCConnectionResume Request and uplink data can be transmitted from the UE210to the new eNB220, as in operation206. In another example, an X2 application protocol (AP) (X2-AP) retrieve UE context request can be transmitted from the new eNB220to the old eNB230, as in operation208. In another example, an X2-AP retrieve UE context response can be transmitted from the old eNB230to the new eNB220, as in operation212.

In another example, an S1-AP path switch request can be transmitted from the new eNB220to a mobility management entity (MME)240, as depicted in operation214. In another example, a modify bearer communication can be communicated between the MME240and a serving gateway (S-GW)250, as depicted in operation216. In another example, an S1-AP path switch request acknowledgement (ACK) can be transmitted from the MME240to the new eNB220, as depicted in operation218. In another example, an X2-AP UE context release can be transmitted from the new eNB220to the old eNB230, as depicted in operation222.

In another example, uplink (UL) data can be transmitted from the new eNB220to the S-GW250, as depicted in operation224. In another example, downlink (DL) data can be transmitted from the S-GW250to the new eNB220, as depicted in operation226. In another example, an S1 suspend procedure can be communicated between the MME240and the new eNB220, as depicted in operation228. In another example, a modify bearer communication can be communicated between the MME240and the S-GW250, as depicted in operation232. In another example, an RRCConnectionRelease can include one or more of a releaseCause, a resumeID, or a NextHop Chaining Count (NCC). The RRCConnectionRelease and downlink data can be transmitted from the new eNB220to the UE210, as depicted in operation234.

In another example, operation234may not be successful. In this scenario, a new resume ID and a new NCC may not be provisioned to the UE210, while the new eNB220may become the new anchor to serve the UE210from the network (NW) point of view. If the UE210resumes on different eNB next time, then the UE210might use the old resume ID and the old NCC. As a result, the X2-AP context retrieval may be requested to the previous anchor (i.e. the old eNB230), but the previous anchor (i.e. the old eNB230) may not have this information because the related UE context information may have been released from the previous anchor in operation222. Therefore, the X2-AP context retrieval procedure can fail, which can result in UE fallback to IDLE and re-establishment of the RRC Connection. The failure of the X2-AP context retrieval procedure can be inefficient waste battery consumption.

In one example, as depicted inFIG.3a, the RRCConnectionRelease in Msg4 can include one or more of a releaseCause, a new resumeID, or an NCC. The RRCConnectionRelease can be attempted to be transmitted from the new anchor eNB320ato the UE310, as depicted in operation302a.

In one example, in a scenario in which RRCConnectionRelease delivery (e.g., Message 4 (Msg4) delivery) is unsuccessful, a new anchor node (e.g., new anchor eNB320a) which already became the new anchor after the path switch can send an EDT failure indication and a Resume ID to the previous anchor node (e.g., old anchor eNB330).

In another example, when the RRCConnectionRelease delivery is unsuccessful in operation302a, the new anchor eNB320acan be configured to transmit an X2-AP EDT failure indication and an old Resume ID to an old anchor eNB330, as depicted in operation304a.

In another example, a random access preamble can be transmitted from the UE310to the new eNB320b, as in operation306a. In another example, a random access response can be transmitted from the new eNB320bto the UE310, as in operation308a.

In another example, an RRCConnectionResumeRequest can include one or more of an old resumeID, a resumeCause, or a shortResumeMAC-I). In another example, the RRCConnectionResumeRequest and uplink data can be transmitted from the UE310to the new eNB320b, as depicted in operation312a. In another example, an X2-AP retrieve UE context request can be transmitted from the new eNB320bto the old anchor eNB330, as depicted in operation314a.

In another example, an X2-AP previous EDT failure indication and no UE context can be transmitted from the old anchor eNB330to the new eNB320b, as depicted in operation316a. In another example, an RRCConnectionSetup can be transmitted from the new eNB320bto the UE310in a Msg4 to initiate a new legacy RRC Connection, as depicted in operation318a.

In the example depicted inFIG.3a, the new anchor eNB320acan become the new anchor eNB after the path switch and suspend procedure but before sending Msg4 to the UE310. In one example, the new anchor eNB320acan be configured to determine that the Msg4 delivery to the UE310is not successful and can be configured to send the EDT failure indication and resume ID to the previous anchor eNB (e.g., old anchor eNB330). When the UE310resumes in a different eNB (i.e. an eNB that is different from new anchor320aand old anchor eNB330) with the old resume ID of the old anchor eNB330, the old anchor eNB330can determine that EDT was a failure and can send an EDT failure indication to the new eNB320bin which the UE310is attempting to resume. The new eNB320bcan be configured to enable RRC_CONNECTED instead of sending a reject message by sending a legacy RRCConnectionSetup message in Msg4. In this scenario, the UE can abort the EDT and set up a new connection to retransmit the data.

In another example, the stage-2 call flow as depicted inFIG.3amay not be changed. In another example, the new eNB320bcan be configured to move the UE to RRC-CONNECTED instead of sending a reject message. In another example, EDT may not be continued.

In another example, the new anchor eNB320acan be configured to send one or more of the EDT failure indication or the old resume ID so that the old anchor eNB330can respond with an X2-AP previous EDT failure and no UE context to the new eNB320b, as depicted in operation316a. In another example, the X2-AP UE CONTEXT RELEASE message can be enhanced or defined. In another example, the X2-AP RETRIEVE UE CONTEXT RESPONSE message can be enhanced.

In one example, as depicted inFIG.3b, in a scenario in which RRCConnectionRelease delivery (e.g., Message 4 (Msg4) delivery) is unsuccessful, an old anchor node (e.g., old eNB330) can forward a new resumption request to the new anchor node (e.g., new eNB320), which became the new anchor node after the path switch.

In another example, a random access preamble can be transmitted from the UE310to the new eNB320, as in operation302b. In another example, a random access response can be transmitted from the new eNB320to the UE310, as in operation304b.

In another example, an RRCConnectionResumeRequest can include one or more of a resumeID, a resumeCause, or a shortResumeMAC-I). In another example, the RRCConnectionResumeRequest and uplink data can be transmitted from the UE310to the new eNB320, as depicted in operation306b. In another example, an X2-AP retrieve UE context request can be transmitted from the new eNB320to the old eNB330, as depicted in operation308b.

In another example, an X2-AP retrieve UE context response can be transmitted from the old eNB330to the new eNB320, as depicted in operation312b. In another example, an S1-AP path switch request can be transmitted from the new eNB320to an MME340, as depicted in operation314b. In another example, a modify bearer communication can be communicated between the MME340and the S-GW350, as depicted in316b. In another example, an S1-AP path switch request ACK can be transmitted from the MME340to a new eNB320, as depicted in operation318b.

In another example, the new eNB320can attempt to transmit an X2-AP UE context release (i.e. a Msg4) from the new eNB320to the old eNB330, as depicted in operation322b. In another example, UL data can be transmitted from the new eNB320to the S-GW350, as depicted in operation324b. In another example, DL data can be transmitted from the S-GW350to the new eNB320, as depicted in operation326b. In another example, an S1 suspend procedure can be communicated between the new eNB320and the MME340, as depicted in operation328b. In another example, a modify bearer communication can be communicated between the MME340and the S-GW350, as depicted in operation332b.

In another example, an RRCConnectionRelease can include one or more of a releaseCause, resumeID, or an NCC. In another example, the RRCConnectionRelease and downlink data can be attempted to be transmitted from the new eNB320to the UE310, as depicted in operation334b. In another example, an X2-AP UE context release can be transmitted from the new eNB320to the old eNB330, as depicted in operation336b. In one example, when the RRCConnectionRelease transmission is unsuccessful, the old eNB330can be configured to forward the future resumption request to the new eNB320.

In another example, in a scenario in which Msg4 delivery is unsuccessful, when the UE310resumes on another eNB, the old eNB330can receive a request for context retrieval based on the old resume ID. If the old eNB330can forward this retrieval request (from another eNB) to the new eNB320, then the EDT procedure can be continued.

In another example, the old eNB330can provide the old resume ID and the old NCC when forwarding so that new eNB320can use the old resume ID and the old NCC to verify the resume request. The transport network layer (TNL) information of the eNB with which the UE has resumed and the eNB UE X2-AP ID that the eNB has allocated for the UE can be forwarded from the old eNB330to the new eNB320. The NCC, TNL, and eNB UE X2-AP ID can have a stage-3 impact on the X2AP RETRIEVE UE CONTEXT REQUEST message.

In another example, the NW can be configured to coordinate old eNB330forwarding of the future retrieval request to the new eNB320based on unsuccessful Msg4 delivery. In another example, forwarding can be assumed if the old eNB330does not receive the X2-AP UE CONTEXT RELEASE message from the new eNB320to release UE context in the old eNB330. In another example, operation322bcan be moved after operation334band can occur when Msg4 delivery is successful. If Msg4 delivery is unsuccessful, then the new eNB320can determine whether to send X2AP UE CONTEXT RELEASE. In this example, the new eNB320can be configured to send the X2AP UE CONTEXT RELEASE when the UE310resumes on the new eNB320again.

In another example, the new eNB320can be configured to send the X2-AP UE CONTEXT RELEASE message to the old eNB330with an indication that Msg4 delivery was unsuccessful to allow the old eNB330to determine whether to forward or not (i.e. operation322bcan be moved or repeated after operation334b. If operation322bis repeated, then the old UE Context can be provided, and can occur regardless of whether Msg4 delivery was successful or not. But if Msg4 delivery is unsuccessful, then a failure indicator can be included.

In another example, the new eNB320may not send X2-AP UE CONTEXT RELEASE again even when the UE310resumes on the new eNB320again. In one example, a new X2-AP message can be defined. In another example, there can be minimal stage-2 impact. In another example, the core network (CN) may not be involved (e.g. if the UE resumes on the new eNB320again, then an additional path switch may not occur).

In another example, when Msg4 delivery fails consecutively (i.e. unsuccessful in another eNB) and the X2-AP UE CONTEXT REQUEST message from another eNB is addressed directly to the new eNB320, then it can be forwarded to the old eNB330where the subsequent resume request is addressed (based on the old resume ID). In another example, some stage-3 changes can be defined for X2-AP RETRIEVE UE CONTEXT REQUEST (to include old UE Context, old NCC, TNL, and eNB UE X2AP ID of another eNB) and for X2-AP UE CONTEXT RELEASE (to include a forwarding indication).

In another example, as depicted inFIG.3c, when Msg4 delivery is unsuccessful, the new eNB320which became the new anchor after the path switch can be configured to revert anchoring back to the old eNB330.

In another example, a random access preamble can be transmitted from the UE310to the new eNB320, as in operation302c. In another example, a random access response can be transmitted from the new eNB320to the UE310, as in operation304c.

In another example, an RRCConnectionResumeRequest can include one or more of a resumeID, a resumeCause, or a shortResumeMAC-I). In another example, the RRCConnectionResumeRequest and uplink data can be transmitted from the UE310to the new eNB320, as depicted in operation306c. In another example, an X2-AP retrieve UE context request can be transmitted from the new eNB320to the old eNB330, as depicted in operation308c.

In another example, an X2-AP retrieve UE context response can be transmitted from the old eNB330to the new eNB320, as depicted in operation312c. In another example, an S1-AP path switch request can be transmitted from the new eNB320to an MME340, as depicted in operation314c. In another example, a modify bearer communication can be communicated between the MME340and the S-GW350, as depicted in316c. In another example, an S1-AP path switch request ACK can be transmitted from the MME340to the new eNB320, as depicted in operation318c.

In another example, the new eNB320can attempt to transmit an X2-AP UE context release (i.e. a Msg4) from the new eNB320to the old eNB330, as depicted in operation322c. In another example, UL data can be transmitted from the new eNB320to the S-GW350, as depicted in operation324c. In another example, DL data can be transmitted from the S-GW350to the new eNB320, as depicted in operation326c. In another example, an S1 suspend procedure can be communicated between the new eNB320and the MME340, as depicted in operation328c. In another example, a modify bearer communication can be communicated between the MME340and the S-GW350, as depicted in operation332c.

In another example, an RRCConnectionRelease can include one or more of a releaseCause, a resumeID, or an NCC. In another example, the RRCConnectionRelease and downlink data can be attempted to be transmitted from the new eNB320to the UE310, as depicted in operation334c. In another example, an X2-AP UE context release can be transmitted from the new eNB320to the old eNB330, as depicted in operation336c, when the RRCConnectionRelease is successful. In another example, an X2-AP path switch request can be transmitted from the new eNB320to the old eNB330, as depicted in operation338c, when the RRCConnectionRelease is unsuccessful.

In another example, an S1-AP path switch request can be transmitted from the old eNB330to the MME340, as depicted in operation342c. In another example, a modify bearer communication can be communicated between the MME340and the S-GW350, as depicted in operation344c. In another example, an S1-AP path switch request ACK can be transmitted from the MME340to the old eNB330, as depicted in operation346c. In another example, an X2-AP path switch response can be transmitted from the old eNB330to the new eNB320, as depicted in operation348c.

In another example, the NW can be configured to revert the anchoring back to the previous anchor. This can be achieved if operation322c(X2-AP UE Context Release) is moved after operation334cwhen operation334cis successful, and, if operation334cis unsuccessful, then operation338c(X2-AP Path Switch Request) can request the old eNB330to trigger a path switch to revert the termination point of the de-activated evolved packet system (EPS) bearer back to the old eNB330. In another example, when operation322coccurs before operation334c, then operation338ccan include the UE Context to provide it to the old eNB330in case of unsuccessful Msg4 delivery. In another example, stage-2 and stage-3 can be impacted.

In another example, as illustrated inFIG.3d, the UE can be released without anchor relocation. In another example, a random access preamble can be transmitted from the UE310to the new eNB320, as in operation302d. In another example, a random access response can be transmitted from the new eNB320to the UE310, as in operation304d.

In another example, an RRCConnectionResumeRequest can include one or more of a resumeID, a resumeCause, or a shortResumeMAC-I). In another example, the RRCConnectionResumeRequest and uplink data can be transmitted from the UE310to the new eNB320, as depicted in operation306d. In another example, an X2-AP retrieve UE context request can be transmitted from the new eNB320to the old eNB330, as depicted in operation308d. In another example, uplink data308ecan be transmitted from the new eNB320to the old eNB330in operation308d.

In another example, an S1-AP context resume request can be transmitted from the old eNB330to an MME340, as depicted in operation312d. In another example, a modify bearer communication can be communicated between the MME340and the S-GW350, as depicted in314d. In another example, an S1-AP path UE context resume response can be transmitted from the MME340to the old eNB330, as depicted in operation316d.

In another example, UL data can be transmitted from the old eNB330to the S-GW350, as depicted in operation318d. In another example, DL data can be transmitted from the S-GW350to the old eNB330, as depicted in operation322d. In another example, an S1 suspend procedure can be communicated between the old eNB330and the MME340, as depicted in operation324d. In another example, a modify bearer communication can be communicated between the MME340and the S-GW350, as depicted in operation326d. In another example, an X2-AP retrieve UE context response can be transmitted from the old eNB330to the new eNB320, as depicted in operation328d. In another example, downlink data328ecan be transmitted from the old eNB330to the new eNB320in operation328d.

In another example, an RRCConnectionRelease can include one or more of a releaseCause, a resumeID, or an NCC. In another example, the RRCConnectionRelease and downlink data can be attempted to be transmitted from the new eNB320to the UE310, as depicted in operation332d.

In another example, the UE can be released without anchor relocation, wherein the old eNB330can determine whether to relocate the anchor or not. If the old eNB330relocates the anchor, then the RRCConnectionRelease can be forwarded via new eNB320and thus reduce the subsequent path switch signaling. Uplink and Downlink data can also be forwarded and sent via new eNB320.

In another example, when the UE310resumes successfully in a new eNB320, the old eNB330can be requested by the UE310to release the UE310and the old eNB330can request the new eNB320to release the UE310. In another example, the old eNB330and the new eNB320can be configured to have a timer to release the UE310after msg4 delivery failure is detected.

Another example provides functionality400of an evolved node B (eNB) operable for early data transmission (EDT) in a user plane (UP) in a cellular internet of things (CIoT) evolved packet system (EPS) network, as shown inFIG.4. The eNB can comprise one or more processors. The one or more processors can be configured to encode, at the eNB for transmission to a user equipment (UE), a message 4 (Msg4) including a resume identifier (ID) and a next-hop chaining count (NCC), as in block410. The one or more processors can be configured to determine, at the eNB, a delivery status of the Msg4 to the UE, as in block420. The one or more processors can be configured to encode, at the eNB for transmission to a previous eNB of the UE, one or more of an EDT failure indicator or the resume ID, as in block430. In addition, the eNB can comprise a memory interface configured to store the msg4 in a memory.

Another example provides functionality500of an evolved node B (eNB) operable for early data transmission (EDT) in a user plane (UP) in a cellular internet of things (CIoT) evolved packet system (EPS) network, as shown inFIG.5. The eNB can comprise one or more processors. The one or more processors can be configured to encode, at the eNB for transmission to a user equipment (UE), a message 4 (Msg4) including a resume identifier (ID) and a next-hop chaining count (NCC), as in block510. The one or more processors can be configured to determine, at the eNB, a delivery status of the Msg4 to the UE, as in block520. The one or more processors can be configured to encode, at the eNB for transmission to a previous eNB of the UE, an X2 application protocol (AP) (X2-AP) UE context release message after the delivery status of the Msg4 to the UE has been determined, as in block530. In addition, the eNB can comprise a memory interface configured to store the Msg4 in a memory.

Another example provides functionality600of an evolved node B (eNB) operable for early data transmission (EDT) in a user plane (UP) in a cellular internet of things (CIoT) evolved packet system (EPS) network, as shown inFIG.6. The eNB can comprise one or more processors. The one or more processors can be configured to encode, at the eNB for transmission to a user equipment (UE), a message 4 (Msg4) including a resume identifier (ID) and a next-hop chaining count (NCC), as in block610. The one or more processors can be configured to determine, at the eNB, a delivery status of the Msg4 to the UE, as in block620. The one or more processors can be configured to encode, at the eNB for transmission to a previous eNB of the UE, an X2 application protocol (AP) path switch request message based on the delivery status of the Msg4 to the UE, as in block630. In addition, the eNB can comprise a memory interface configured to store the Msg4 in a memory.

While examples have been provided in which an eNB has been specified, they are not intended to be limiting. 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) can be used in place of an eNB. Accordingly, unless otherwise stated, any example herein in which an eNB has been disclosed, can similarly be disclosed with the use of an eNB, gNB, or new radio base station (NR BS).

FIG.7illustrates an example architecture of a system700of a network, in accordance with various embodiments. The following description is provided for an example system700that operates in conjunction with the LTE system standards and 5G or NR system standards as provided by 3GPP technical specifications. However, the example embodiments are not limited in this regard and the described embodiments may apply 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.), or the like.

As shown byFIG.7, the system700includes UE701aand UE701b(collectively referred to as “UEs701” or “UE701”). In this example, UEs701are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, an Instrument Cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic/engine control units (ECUs), electronic/engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or “smart” appliances, MTC devices, M2M, IoT devices, and/or the like.

The UEs701may be configured to connect, for example, communicatively couple, with an or RAN710. In embodiments, the RAN710may be an NG RAN or a 5G RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN. As used herein, the term “NG RAN” or the like may refer to a RAN710that operates in an NR or 5G system700, and the term “E-UTRAN” or the like may refer to a RAN710that operates in an LTE or 4G system700. The UEs701utilize connections (or channels)703and704, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below).

In this example, the connections703and704are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and/or any of the other communications protocols discussed herein. In embodiments, the UEs701may directly exchange communication data via a ProSe interface705. The ProSe interface705may alternatively be referred to as a SL interface705and may comprise one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

The UE701bis shown to be configured to access an AP706(also referred to as “WLAN node706,” “WLAN706,” “WLAN Termination706,” “WT706” or the like) via connection707. The connection707can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP706would comprise a wireless fidelity (Wi-Fi®) router. In this example, the AP706is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below). In various embodiments, the UE701b, RAN710, and AP706may be configured to utilize LWA operation and/or LWIP operation. The LWA operation may involve the UE701bin RRC_CONNECTED being configured by a RAN node711a-bto utilize radio resources of LTE and WLAN. LWIP operation may involve the UE701busing WLAN radio resources (e.g., connection707) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) sent over the connection707. IPsec tunneling may include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.

The RAN710can include one or more AN nodes or RAN nodes711aand711b(collectively referred to as “RAN nodes711” or “RAN node711”) that enable the connections703and704. As used herein, the terms “access node,” “access point,” or the like may describe equipment that provides the radio baseband functions for data and/or voice connectivity between a network and one or more users. These access nodes can be referred to as BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs or TRPs, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). As used herein, the term “NG RAN node” or the like may refer to a RAN node711that operates in an NR or 5G system700(for example, a gNB), and the term “E-UTRAN node” or the like may refer to a RAN node711that operates in an LTE or 4G system700(e.g., an eNB). According to various embodiments, the RAN nodes711may be implemented as one or more of a dedicated physical device such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

In some embodiments, all or parts of the RAN nodes711may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a CRAN and/or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement a RAN function split, such as a PDCP split wherein RRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocol entities are operated by individual RAN nodes711; a MAC/PHY split wherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN/vBBUP and the PHY layer is operated by individual RAN nodes711; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer are operated by the CRAN/vBBUP and lower portions of the PHY layer are operated by individual RAN nodes711. This virtualized framework allows the freed-up processor cores of the RAN nodes711to perform other virtualized applications. In some implementations, an individual RAN node711may represent individual gNB-DUs that are connected to a gNB-CU via individual F1 interfaces (not shown byFIG.7). In these implementations, the gNB-DUs may include one or more remote radio heads or RFEMs, and the gNB-CU may be operated by a server that is located in the RAN710(not shown) or by a server pool in a similar manner as the CRAN/vBBUP. Additionally or alternatively, one or more of the RAN nodes711may be next generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol terminations toward the UEs701, and are connected to a 5GC via an NG interface (discussed infra).

In V2X scenarios one or more of the RAN nodes711may be or act as RSUs. The term “Road Side Unit” or “RSU” may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a “UE-type RSU,” an RSU implemented in or by an eNB may be referred to as an “eNB-type RSU,” an RSU implemented in or by a gNB may be referred to as a “gNB-type RSU,” and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs701(vUEs701). The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communications (DSRC) band to provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications, as well as other cellular communications 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. The computing device(s) and some or all of the radiofrequency circuitry of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and/or a backhaul network.

Any of the RAN nodes711can terminate the air interface protocol and can be the first point of contact for the UEs701. In some embodiments, any of the RAN nodes711can fulfill various logical functions for the RAN710including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

According to various embodiments, the UEs701and the RAN nodes711communicate data (for example, transmit and receive) data over a licensed medium (also referred to as the “licensed spectrum” and/or the “licensed band”) and an unlicensed shared medium (also referred to as the “unlicensed spectrum” and/or the “unlicensed band”). The licensed spectrum may include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, whereas the unlicensed spectrum may include the 5 GHz band.

To operate in the unlicensed spectrum, the UEs701and the RAN nodes711may operate using LAA, eLAA, and/or feLAA mechanisms. In these implementations, the UEs701and the RAN nodes711may perform one or more known medium-sensing operations and/or carrier-sensing operations in order to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum. The medium/carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

LBT is a mechanism whereby equipment (for example, UEs701RAN nodes711, etc.) senses a medium (for example, a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear. This LBT mechanism allows cellular/LAA networks to coexist with incumbent systems in the unlicensed spectrum and with other LAA networks. ED may include sensing RF energy across an intended transmission band for a period of time and comparing the sensed RF energy to a predefined or configured threshold.

Typically, the incumbent systems in the 5 GHz band are WLANs based on IEEE 802.11 technologies. WLAN employs a contention-based channel access mechanism, called CSMA/CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE701, AP706, or the like) intends to transmit, the WLAN node may first perform CCA before transmission. Additionally, a backoff mechanism is used to avoid collisions in situations where more than one WLAN node senses the channel as idle and transmits at the same time. The backoff mechanism may be a counter that is drawn randomly within the CWS, which is increased exponentially upon the occurrence of collision and reset to a minimum value when the transmission succeeds. The LBT mechanism designed for LAA is somewhat similar to the CSMA/CA of WLAN. In some implementations, the LBT procedure for DL or UL transmission bursts including PDSCH or PUSCH transmissions, respectively, may have an LAA contention window that is variable in length between X and Y ECCA slots, where X and Y are minimum and maximum values for the CWSs for LAA. In one example, the minimum CWS for an LAA transmission may be 9 microseconds (μs); however, the size of the CWS and a MCOT (for example, a transmission burst) may be based on governmental regulatory requirements.

The LAA mechanisms are built upon CA technologies of LTE-Advanced systems. In CA, each aggregated carrier is referred to as a CC. A CC may have a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz and a maximum of five CCs can be aggregated, and therefore, a maximum aggregated bandwidth is 100 MHz. In FDD systems, the number of aggregated carriers can 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 can have a different bandwidth than other CCs. In TDD systems, the number of CCs as well as the bandwidths of each CC is usually the same for DL and UL.

CA also comprises individual serving cells to provide individual CCs. The coverage of the serving cells may differ, for example, because CCs on different frequency bands will experience different pathloss. A primary service cell or PCell may provide a PCC for both UL and DL, and may handle RRC and NAS related activities. The other serving cells are referred to as SCells, and each SCell may provide an individual SCC for both UL and DL. The SCCs may be added and removed as required, while changing the PCC may require the UE701to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in the unlicensed spectrum (referred to as “LAA SCells”), and the LAA SCells are assisted by a PCell operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within a same subframe.

The PDSCH carries user data and higher-layer signaling to the UEs701. The PDCCH carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs701about the transport format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE701bwithin a cell) may be performed at any of the RAN nodes711based on channel quality information fed back from any of the UEs701. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs701.

The RAN nodes711may be configured to communicate with one another via interface712. In embodiments where the system700is an LTE system, the interface712may be an X2 interface712. The X2 interface may be defined between two or more RAN nodes711(e.g., two or more eNBs and the like) that connect to EPC720, and/or between two eNBs connecting to EPC720. 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 flow control mechanisms for user data packets transferred over the X2 interface, and may be used to communicate information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information for user data transferred from a MeNB to an SeNB; information about successful in sequence delivery of PDCP PDUs to a UE701from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE701; information about a current minimum desired buffer size at the SeNB for transmitting to the UE user data; and the like. The X2-C may provide intra-LTE access mobility functionality, including context transfers from source to target eNBs, user plane transport control, etc.; load management functionality; as well as inter-cell interference coordination functionality.

In embodiments where the system700is a 5G or NR system, the interface712may be an Xn interface712. The Xn interface is defined between two or more RAN nodes711(e.g., two or more gNBs and the like) that connect to 5GC720, between a RAN node711(e.g., a gNB) connecting to 5GC720and an eNB, and/or between two eNBs connecting to 5GC720. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality. The Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE701in a connected mode (e.g., CM-CONNECTED) including functionality to manage the UE mobility for connected mode between one or more RAN nodes711. The mobility support may include context transfer from an old (source) serving RAN node711to new (target) serving RAN node711; and control of user plane tunnels between old (source) serving RAN node711to new (target) serving RAN node711. A protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of a 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 Xn Application Protocol (Xn-AP)) and a transport network layer that is built on SCTP. The SCTP may be on top of an IP layer, and may provide the guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.

The RAN710is shown to be communicatively coupled to a core network—in this embodiment, core network (CN)720. The CN720may comprise a plurality of network elements722, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UEs701) who are connected to the CN720via the RAN710. The components of the CN720may be implemented in one physical node or separate physical nodes including 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 mediums (described in further detail below). A logical instantiation of the CN720may be referred to as a network slice, and a logical instantiation of a portion of the CN720may be referred to as a network sub-slice. NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.

Generally, the application server730may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server730can also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs701via the EPC720.

In embodiments, the CN720may be a 5GC (referred to as “5GC720” or the like), and the RAN710may be connected with the CN720via an NG interface713. In embodiments, the NG interface713may be split into two parts, an NG user plane (NG-U) interface714, which carries traffic data between the RAN nodes711and a UPF, and the S1 control plane (NG-C) interface715, which is a signaling interface between the RAN nodes711and AMFs.

In embodiments, the CN720may be a 5G CN (referred to as “5GC720” or the like), while in other embodiments, the CN720may be an EPC). Where CN720is an EPC (referred to as “EPC720” or the like), the RAN710may be connected with the CN720via an S1 interface713. In embodiments, the S1 interface713may be split into two parts, an S1 user plane (S1-U) interface714, which carries traffic data between the RAN nodes711and the S-GW, and the S1-MME interface715, which is a signaling interface between the RAN nodes711and MMEs.

FIG.8illustrates an example of a platform800(or “device800”) in accordance with various embodiments. In embodiments, the computer platform800may be suitable for use as UEs701, application servers730, and/or any other element/device discussed herein. The platform800may include any combinations of the components shown in the example. The components of platform800may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform800, or as components otherwise incorporated within a chassis of a larger system. The block diagram ofFIG.8is intended to show a high level view of components of the computer platform800. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.

The processor(s) of 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 DSP, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multithreaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof. In some embodiments, the application circuitry may comprise, or may be, a special-purpose processor/controller to operate according to the various embodiments herein.

As examples, the processor(s) of application circuitry805may include an Intel® Architecture Core™ based processor, such as a Quark™, an Atom™, an i3, an i5, an i7, or an MCU-class processor, or another such processor available from Intel® Corporation, Santa Clara, CA The processors of the application circuitry805may also be one or more of Advanced Micro Devices (AMD) Ryzen® processor(s) or Accelerated Processing Units (APUs); A5-A9 processor(s) from Apple® Inc., Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.® Open Multimedia Applications Platform (OMAP)™ processor(s); a MIPS-based design from MIPS Technologies, Inc. such as MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; an ARM-based design licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M family of processors; or the like. In some implementations, the application circuitry805may be a part of a system on a chip (SoC) in which the application circuitry805and other components are formed into a single integrated circuit, or a single package, such as the Edison™ or Galileo™ SoC boards from Intel® Corporation.

The baseband circuitry810may be implemented, for example, as a solder-down substrate including 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. The various hardware electronic elements of baseband circuitry810are discussed infra with regard toFIG.9.

The memory circuitry820may include any number and type of memory devices used to provide for a given amount of system memory. As examples, the memory circuitry820may include one or more of volatile memory including random access memory (RAM), dynamic RAM (DRAM) and/or synchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuitry820may be developed in accordance with a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry820may be implemented as one or more of solder down packaged integrated circuits, single die package (SDP), dual die package (DDP) or quad die package (Q17P), socketed memory modules, dual inline memory modules (DIMMs) including microDIMMs or MiniDIMMs, and/or soldered onto a motherboard via a ball grid array (BGA). In low power implementations, the memory circuitry820may be on-die memory or registers associated with the application circuitry805. To provide for persistent storage of information such as data, applications, operating systems and so forth, memory circuitry820may include one or more mass storage devices, which may include, inter alia, a solid state disk drive (SSDD), hard disk drive (HDD), a micro HDD, resistance change memories, phase change memories, holographic memories, or chemical memories, among others. For example, the computer platform800may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.

Removable memory circuitry823may include devices, circuitry, enclosures/housings, ports or receptacles, etc. used to couple portable data storage devices with the platform800. 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, and the like), and USB flash drives, optical discs, external HDDs, and the like.

The platform800may also include interface circuitry (not shown) that is used to connect external devices with the platform800. The external devices connected to the platform800via the interface circuitry include sensor circuitry821and electro-mechanical components (EMCs)822, as well as removable memory devices coupled to removable memory circuitry823.

The sensor circuitry821include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other a device, module, subsystem, etc. Examples of such sensors include, inter alia, inertia measurement units (IMUs) comprising accelerometers, gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) comprising 3-axis accelerometers, 3-axis gyroscopes, and/or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detector and the like), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other like audio capture devices; etc.

EMCs822include devices, modules, or subsystems whose purpose is to enable platform800to change its state, position, and/or orientation, or move or control a mechanism or (sub)system. Additionally, EMCs822may be configured to generate and send messages/signalling to other components of the platform800to indicate a current state of the EMCs822. Examples of the EMCs822include one or more power switches, relays including electromechanical relays (EMRs) and/or solid state relays (SSRs), actuators (e.g., valve actuators, etc.), an audible sound generator, a visual warning device, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and/or other like electro-mechanical components. In embodiments, platform800is configured to operate one or more EMCs822based on one or more captured events and/or instructions or control signals received from a service provider and/or various clients.

In some implementations, the interface circuitry may connect the platform800with positioning circuitry845. The positioning circuitry845includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a GNSS. Examples of navigation satellite constellations (or GNSS) include United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., NAVIC), Japan's QZSS, France's DORIS, etc.), or the like. The positioning circuitry845comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry845may include a Micro-PNT IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance. The positioning circuitry845may also be part of, or interact with, the baseband circuitry and/or RFEMs815to communicate with the nodes and components of the positioning network. The positioning circuitry845may also provide position data and/or time data to the application circuitry805, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations), for turn-by-turn navigation applications, or the like

In some implementations, the interface circuitry may connect the platform800with Near-Field Communication (NFC) circuitry840. NFC circuitry840is configured to provide contactless, short-range communications based on radio frequency identification (RFID) standards, wherein magnetic field induction is used to enable communication between NFC circuitry840and NFC-enabled devices external to the platform800(e.g., an “NFC touchpoint”). NFC circuitry840comprises an NFC controller coupled with an antenna element and a processor coupled with the NFC controller. The NFC controller may be a chip/IC providing NFC functionalities to the NFC circuitry840by executing NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to emit short-range RF signals. The RF signals may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transmit stored data to the NFC circuitry840, or initiate data transfer between the NFC circuitry840and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) that is proximate to the platform800.

The driver circuitry846may include software and hardware elements that operate to control particular devices that are embedded in the platform800, attached to the platform800, or otherwise communicatively coupled with the platform800. The driver circuitry846may include individual drivers allowing other components of the platform800to interact with or control various input/output (I/O) devices that may be present within, or connected to, the platform800. For example, driver circuitry846may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface of the platform800, sensor drivers to obtain sensor readings of sensor circuitry821and control and allow access to sensor circuitry821, EMC drivers to obtain actuator positions of the EMCs822and/or control and allow access to the EMCs822, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.

The power management integrated circuitry (PMIC)825(also referred to as “power management circuitry825”) may manage power provided to various components of the platform800. In particular, with respect to the baseband circuitry810, the PMIC825may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMIC825may often be included when the platform800is capable of being powered by a battery830, for example, when the device is included in a UE701.

In some embodiments, the PMIC825may control, or otherwise be part of, various power saving mechanisms of the platform800. For example, if the platform800is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the platform800may power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the platform800may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The platform800goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The platform800may not receive data in this state; in order to receive data, it must transition back to RRC_Connected state. An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

A battery830may power the platform800, although in some examples the platform800may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid. The battery830may 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, such as in V2X applications, the battery830may be a typical lead-acid automotive battery.

In some implementations, the battery830may be a “smart battery,” which includes or is coupled with a Battery Management System (BMS) or battery monitoring integrated circuitry. The BMS may be included in the platform800to track the state of charge (SoCh) of the battery830. The BMS may be used to monitor other parameters of the battery830to provide failure predictions, such as the state of health (SoH) and the state of function (SoF) of the battery830. The BMS may communicate the information of the battery830to the application circuitry805or other components of the platform800. The BMS may also include an analog-to-digital (ADC) convertor that allows the application circuitry805to directly monitor the voltage of the battery830or the current flow from the battery830. The battery parameters may be used to determine actions that the platform800may perform, such as transmission frequency, network operation, sensing frequency, and the like.

A power block, or other power supply coupled to an electrical grid may be coupled with the BMS to charge the battery830. In some examples, the power block may be replaced with a wireless power receiver to obtain the power wirelessly, for example, through a loop antenna in the computer platform800. In these examples, a wireless battery charging circuit may be included in the BMS. The specific charging circuits chosen may depend on the size of the battery830, and thus, the current required. The charging may be performed using the Airfuel standard promulgated by the Airfuel Alliance, the Qi wireless charging standard promulgated by the Wireless Power Consortium, or the Rezence charging standard promulgated by the Alliance for Wireless Power, among others.

User interface circuitry850includes various input/output (I/O) devices present within, or connected to, the platform800, and includes one or more user interfaces designed to enable user interaction with the platform800and/or peripheral component interfaces designed to enable peripheral component interaction with the platform800. The user interface circuitry850includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, and/or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information. Output device circuitry may include any number and/or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators (e.g., binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., Liquid Chrystal Displays (LCD), LED displays, quantum dot displays, projectors, etc.), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the platform800. The output device circuitry may also include speakers or other audio emitting devices, printer(s), and/or the like. In some embodiments, the sensor circuitry821may be used as the input device circuitry (e.g., an image capture device, motion capture device, or the like) and one or more EMCs may be used as the output device circuitry (e.g., an actuator to provide haptic feedback or the like). In another example, NFC circuitry comprising an NFC controller coupled with an antenna element and a processing device may be included to read electronic tags and/or connect with another NFC-enabled device. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power supply interface, etc.

Although not shown, the components of platform800may communicate with one another using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a Time-Trigger Protocol (ITP) system, a FlexRay system, or any number of other technologies. The bus/IX may be a proprietary bus/IX, for example, used in a SoC based system. Other bus/IX systems may be included, such as an I2C interface, an SPI interface, point-to-point interfaces, and a power bus, among others.

FIG.9illustrates example components of baseband circuitry910and radio front end modules (RFEM)915in accordance with various embodiments. The baseband circuitry910corresponds to the baseband circuitry810ofFIG.8, respectively. The RFEM915corresponds to the RFEM815ofFIG.8, respectively. As shown, the RFEMs915may include Radio Frequency (RF) circuitry906, front-end module (FEM) circuitry908, antenna array911coupled together at least as shown.

The baseband circuitry910includes circuitry and/or control logic configured to carry out various radio/network protocol and radio control functions that enable communication with one or more radio networks via the RF circuitry906. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry910may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry910may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments. The baseband circuitry910is configured to process baseband signals received from a receive signal path of the RF circuitry906and to generate baseband signals for a transmit signal path of the RF circuitry906. The baseband circuitry910is configured to interface with application circuitry805(seeFIG.8) for generation and processing of the baseband signals and for controlling operations of the RF circuitry906. The baseband circuitry910may handle various radio control functions.

The aforementioned circuitry and/or control logic of the baseband circuitry910may include one or more single or multi-core processors. For example, the one or more processors may include a 3G baseband processor904A, a 4G/LTE baseband processor904B, a 5G/NR baseband processor904C, or some other baseband processor(s)904D for other existing generations, generations in development or to be developed in the future (e.g., sixth generation (6G), etc.). In other embodiments, some or all of the functionality of baseband processors904A-D may be included in modules stored in the memory904G and executed via a Central Processing Unit (CPU)904E. In other embodiments, some or all of the functionality of baseband processors904A-D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with the appropriate bit streams or logic blocks stored in respective memory cells. In various embodiments, the memory904G may store program code of a real-time OS (RTOS), which when executed by the CPU904E (or other baseband processor), is to cause the CPU904E (or other baseband processor) to manage resources of the baseband circuitry910, schedule tasks, etc. Examples of the RTOS may include Operating System Embedded (OSE)™ provided by Enea®, Nucleus RTOS™ provided by Mentor Graphics®, Versatile Real-Time Executive (VRTX) provided by Mentor Graphics®, ThreadX™ provided by Express Logic®, FreeRTOS, REX OS provided by Qualcomm®, OKL4 provided by Open Kernel (OK) Labs®, or any other suitable RTOS, such as those discussed herein. In addition, the baseband circuitry910includes one or more audio digital signal processor(s) (DSP)904F. The audio DSP(s)904F include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.

In some embodiments, each of the processors904A-904E include respective memory interfaces to send/receive data to/from the memory904G. The baseband circuitry910may further include one or more interfaces to communicatively couple to other circuitries/devices, such as an interface to send/receive data to/from memory external to the baseband circuitry910; an application circuitry interface to send/receive data to/from the application circuitry805ofFIG.9); an RF circuitry interface to send/receive data to/from RF circuitry906ofFIG.9; a wireless hardware connectivity interface to send/receive data to/from one or more wireless hardware elements (e.g., Near Field Communication (NFC) components, Bluetooth®/Bluetooth® Low Energy components, Wi-Fi® components, and/or the like); and a power management interface to send/receive power or control signals to/from the PMIC825.

In alternate embodiments (which may be combined with the above described embodiments), baseband circuitry910comprises one or more digital baseband systems, which are coupled with one another via an interconnect subsystem and to a CPU subsystem, an audio subsystem, and an interface subsystem. The digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, point-to-point connections, network-on-chip (NOC) structures, 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 of amplifiers and filters, and/or other like components. In an aspect of the present disclosure, baseband circuitry910may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and/or radio frequency circuitry (e.g., the radio front end modules915).

Although not shown byFIG.9, in some embodiments, the baseband circuitry910includes individual processing device(s) to operate one or more wireless communication protocols (e.g., a “multi-protocol baseband processor” or “protocol processing circuitry”) and individual processing device(s) to implement PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. 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 LTE protocol entities and/or 5G/NR protocol entities when the baseband circuitry910and/or RF circuitry906are part of mmWave communication circuitry or some other suitable cellular communication circuitry. In the first example, the protocol processing circuitry would 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 circuitry910and/or RF circuitry906are part of a Wi-Fi communication system. In the second example, the protocol processing circuitry would operate Wi-Fi MAC and 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 for operating the protocol functions, as well as one or more processing cores to execute the program code and perform various operations using the data. The baseband circuitry910may also support radio communications for more than one wireless protocol.

The various hardware elements of the baseband circuitry910discussed herein may be implemented, for example, as a solder-down substrate including one or more integrated circuits (ICs), a single packaged IC soldered to a main circuit board or a multi-chip module containing two or more ICs. In one example, the components of the baseband circuitry910may be suitably combined in a single chip or chipset, or disposed on a same circuit board. In another example, some or all of the constituent components of the baseband circuitry910and RF circuitry906may be implemented together such as, for example, a system on a chip (SoC) or System-in-Package (SiP). In another example, some or all of the constituent components of the baseband circuitry910may be implemented as a separate SoC that is communicatively coupled with and RF circuitry906(or multiple instances of RF circuitry906). In yet another example, some or all of the constituent components of the baseband circuitry910and the application circuitry805may be implemented together as individual SoCs mounted to a same circuit board (e.g., a “multi-chip package”).

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

In some embodiments, the mixer circuitry906aof the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry906dto generate RF output signals for the FEM circuitry908. The baseband signals may be provided by the baseband circuitry910and may be filtered by filter circuitry906c.

The synthesizer circuitry906dmay be configured to synthesize an output frequency for use by the mixer circuitry906aof the RF circuitry906based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry906dmay be a fractional N/N+1 synthesizer.

FEM circuitry908may include a receive signal path, which may include circuitry configured to operate on RF signals received from antenna array911, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry906for further processing. FEM circuitry908may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry906for transmission by one or more of antenna elements of antenna array911. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry906, solely in the FEM circuitry908, or in both the RF circuitry906and the FEM circuitry908.

In some embodiments, the FEM circuitry908may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry908may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry908may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry906). The transmit signal path of the FEM circuitry908may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry906), and one or more filters to generate RF signals for subsequent transmission by one or more antenna elements of the antenna array911.

The antenna array911comprises one or more antenna elements, each of which is configured convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. For example, digital baseband signals provided by the baseband circuitry910is converted into analog RF signals (e.g., modulated waveform) that will be amplified and transmitted via the antenna elements of the antenna array911including one or more antenna elements (not shown). The antenna elements may be omnidirectional, direction, or a combination thereof. The antenna elements may be formed in a multitude of arranges as are known and/or discussed herein. The antenna array911may comprise microstrip antennas or printed antennas that are fabricated on the surface of one or more printed circuit boards. The antenna array911may be formed in as a patch of metal foil (e.g., a patch antenna) in a variety of shapes, and may be coupled with the RF circuitry906and/or FEM circuitry908using metal transmission lines or the like.

Processors of the application circuitry805and processors of the baseband circuitry910may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry910, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry805may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., TCP and UDP layers). As referred to herein, Layer 3 may comprise a RRC layer, described in further detail below. As referred to herein, Layer 2 may comprise a MAC layer, an RLC layer, and a PDCP layer, described in further detail below. As referred to herein, Layer 1 may comprise a PHY layer of a UE/RAN node, described in further detail below.

FIG.10is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically,FIG.10shows a diagrammatic representation of hardware resources1000including one or more processors (or processor cores)1010, one or more memory/storage devices1020, and one or more communication resources1030, each of which may be communicatively coupled via a bus1040. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor1002may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources1000.

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

The communication resources1030may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices1004or one or more databases1006via a network1008. For example, the communication resources1030may include wired communication components (e.g., for coupling via USB), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

Instructions1050may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors1010to perform any one or more of the methodologies discussed herein. The instructions1050may reside, completely or partially, within at least one of the processors1010(e.g., within the processor's cache memory), the memory/storage devices1020, or any suitable combination thereof. Furthermore, any portion of the instructions1050may be transferred to the hardware resources1000from any combination of the peripheral devices1004or the databases1006. Accordingly, the memory of processors1010, the memory/storage devices1020, the peripheral devices1004, and the databases1006are examples of computer-readable and machine-readable media.

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

FIG.12illustrates an example architecture of a system1200including a first CN1220, in accordance with various embodiments. In this example, system1200may implement the LTE standard wherein the CN1220is an EPC1220that corresponds with CN720ofFIG.7. Additionally, the UE1201may be the same or similar as the UEs701ofFIG.7, and the E-UTRAN1210may be a RAN that is the same or similar to the RAN710ofFIG.7, and which may include RAN nodes711discussed previously. The CN1220may comprise MMEs1221, an S-GW1222, a P-GW1223, a HSS1224, and a SGSN1225.

The MMEs1221may be similar in function to the control plane of legacy SGSN, and may implement MM functions to keep track of the current location of a UE1201. The MMEs1221may perform various MM procedures to manage mobility aspects in access such as gateway selection and tracking area list management. MM (also referred to as “EPS MM” or “EMM” in E-UTRAN systems) may refer to all applicable procedures, methods, data storage, etc. that are used to maintain knowledge about a present location of the UE1201, provide user identity confidentiality, and/or perform other like services to users/subscribers. Each UE1201and the MME1221may include an MM or EMM sublayer, and an MM context may be established in the UE1201and the MME1221when an attach procedure is successfully completed. The MM context may be a data structure or database object that stores MM-related information of the UE1201. The MMEs1221may be coupled with the HSS1224via an S6a reference point, coupled with the SGSN1225via an S3 reference point, and coupled with the S-GW1222via an S11 reference point.

The SGSN1225may be a node that serves the UE1201by tracking the location of an individual UE1201and performing security functions. In addition, the SGSN1225may perform Inter-EPC node signaling for mobility between 2G/3G and E-UTRAN 3GPP access networks; PDN and S-GW selection as specified by the MMEs1221; handling of UE1201time zone functions as specified by the MMEs1221; and MME selection for handovers to E-UTRAN 3GPP access network. The S3 reference point between the MMEs1221and the SGSN1225may enable user and bearer information exchange for inter-3GPP access network mobility in idle and/or active states.

The HSS1224may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The EPC1220may comprise one or several HSSs1224, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS1224can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS1224and the MMEs1221may enable transfer of subscription and authentication data for authenticating/authorizing user access to the EPC1220between HSS1224and the MMEs1221.

The S-GW1222may terminate the S1 interface713(“S1-U” inFIG.12) toward the RAN1210, and routes data packets between the RAN1210and the EPC1220. In addition, the S-GW1222may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement. The S11 reference point between the S-GW1222and the MMEs1221may provide a control plane between the MMEs1221and the S-GW1222. The S-GW1222may be coupled with the P-GW1223via an S5 reference point.

The P-GW1223may terminate an SGi interface toward a PDN1230. The P-GW1223may route data packets between the EPC1220and external networks such as a network including the application server730(alternatively referred to as an “AF”) via an IP interface725(see e.g.,FIG.7). In embodiments, the P-GW1223may be communicatively coupled to an application server (application server730ofFIG.7or PDN1230inFIG.12) via an IP communications interface725(see, e.g.,FIG.7). The S5 reference point between the P-GW1223and the S-GW1222may provide user plane tunneling and tunnel management between the P-GW1223and the S-GW1222. The S5 reference point may also be used for S-GW1222relocation due to UE1201mobility and if the S-GW1222needs to connect to a non-collocated P-GW1223for the required PDN connectivity. The P-GW1223may further include a node for policy enforcement and charging data collection (e.g., PCEF (not shown)). Additionally, the SGi reference point between the P-GW1223and the packet data network (PDN)1230may be an operator external public, a private PDN, or an intra operator packet data network, for example, for provision of IMS services. The P-GW1223may be coupled with a PCRF1226via a Gx reference point.

PCRF1226is the policy and charging control element of the EPC1220. In a non-roaming scenario, there may be a single PCRF1226in the Home Public Land Mobile Network (HPLMN) associated with a UE1201's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE1201's IP-CAN session, a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF1226may be communicatively coupled to the application server1230via the P-GW1223. The application server1230may signal the PCRF1226to indicate a new service flow and select the appropriate QoS and charging parameters. The PCRF1226may provision this rule into a PCEF (not shown) with the appropriate TFT and QCI, which commences the QoS and charging as specified by the application server1230. The Gx reference point between the PCRF1226and the P-GW1223may allow for the transfer of QoS policy and charging rules from the PCRF1226to PCEF in the P-GW1223. An Rx reference point may reside between the PDN1230(or “AF1230”) and the PCRF1226.

EXAMPLES

The following examples pertain to specific technology embodiments and point out specific features, elements, or actions that can be used or otherwise combined in achieving such embodiments.

Example 1 includes an apparatus of an evolved node B (eNB) operable for early data transmission (EDT) in a user plane (UP) in a cellular internet of things (CIoT) evolved packet system (EPS) network, the apparatus comprising: one or more processors configured to: encode, at the eNB for transmission to a user equipment (UE), a message 4 (Msg4) including a resume identifier (ID) and a next-hop chaining count (NCC); determine, at the eNB, a delivery status of the Msg4 to the UE; and encode, at the eNB for transmission to a previous eNB of the UE, one or more of an EDT failure indicator or the resume ID; and a memory interface configured to store the Msg4 in a memory.

Example 2 includes the apparatus of Example 1, wherein the one or more processors are further configured to: encode, at the eNB for transmission to the previous eNB of the UE, one or more of the EDT failure indicator or the resume ID when an X2 application protocol (X2-AP) UE context release message is transmitted to the previous eNB of the UE after a transmission of the Msg4 to the UE.

Example 3 includes the apparatus of Example 1, wherein the one or more processors are further configured to: encode, at the eNB for transmission to the previous eNB of the UE, one or more of an EDT failure indicator or the resume ID when the delivery status of the Msg4 to the UE is unsuccessful.

Example 4 includes the apparatus of Example 1, wherein the one or more processors are further configured to: encode, at the eNB for transmission to the previous eNB of the UE, the EDT failure indicator via an X2 application protocol (X2-AP) message.

Example 5 includes the apparatus of Example 1, wherein the one or more processors are further configured to: encode, at the eNB for transmission to the previous eNB of the UE, the resume ID via an X2 application protocol (X2-AP) retrieve UE context request message.

Example 6 includes the apparatus of Example 1, wherein the one or more processors are further configured to: decode, at the eNB for transmission to the UE, an X2 application protocol (X2-AP) retrieve UE context response message including a previous EDT failure indication without UE context.

Example 7 includes the apparatus of Example 1, wherein the one or more processors are further configured to: encode, at the eNB for transmission to the UE, a radio resource control (RRC) connection setup in the Msg4 to initiate an RRC connection between the eNB and the UE.

Example 8 includes the apparatus of any of Examples 1 to 7, wherein Msg4 is a radio resource control (RRC) Connection Release message.

Example 9 includes an apparatus of an evolved node B (eNB) operable for early data transmission (EDT) in a user plane (UP) in a cellular internet of things (CIoT) evolved packet system (EPS) network, the apparatus comprising: one or more processors configured to: encode, at the eNB for transmission to a user equipment (UE), a message 4 (Msg4) including a resume identifier (ID) and a next-hop chaining count (NCC); determine, at the eNB, a delivery status of the Msg4 to the UE; and encode, at the eNB for transmission to a previous eNB of the UE, an X2 application protocol (AP) (X2-AP) UE context release message after the delivery status of the Msg4 to the UE has been determined; and a memory interface configured to store the Msg4 in a memory.

Example 10 includes the apparatus of Example 9, wherein the one or more processors are further configured to: decode, at the eNB, a previous resume ID and a previous NCC received from the previous eNB of the UE; verify, at the eNB, the previous resume ID and the previous NCC; and encode, at the eNB for transmission to a next eNB of the UE, an X2-AP retrieve UE context response.

Example 11 includes the apparatus of Example 9, wherein the one or more processors are further configured to: encode, at the eNB for transmission to the previous eNB of the UE, the X2-AP UE context release message when the delivery status of the Msg4 to the UE is successful.

Example 12 includes the apparatus of Example 9, wherein the one or more processors are further configured to: encode, at the eNB for transmission to the previous eNB of the UE, the X2-AP UE context release message when: the delivery status of the Msg4 to the UE is unsuccessful, and the UE resumes with the eNB.

Example 13 includes the apparatus of Example 9, wherein the one or more processors are further configured to: encode, at the eNB for transmission to the previous eNB of the UE, the X2-AP UE context release message that includes an indication that the previous eNB of the UE forward a resumption request from a next eNB of the UE to the eNB.

Example 14 includes the apparatus of any of Examples 9 to 13, wherein Msg4 is a radio resource control (RRC) Connection Release message.

Example 15 includes an apparatus of an evolved node B (eNB) operable for early data transmission (EDT) in a user plane (UP) in a cellular internet of things (CIoT) evolved packet system (EPS) network, the apparatus comprising: one or more processors configured to: encode, at the eNB for transmission to a user equipment (UE), a message 4 (Msg4) including a resume identifier (ID) and a next-hop chaining count (NCC); determine, at the eNB, a delivery status of the Msg4 to the UE; and encode, at the eNB for transmission to a previous eNB of the UE, an X2 application protocol (AP) path switch request message based on the delivery status of the Msg4 to the UE; and a memory interface configured to store the Msg4 in a memory.

Example 16 includes the apparatus of Example 15, wherein the one or more processors are further configured to: encode, at the eNB for transmission to the previous eNB of the UE, the X2-AP path switch request message when the delivery status of the Msg4 to the UE is unsuccessful.

Example 17 includes the apparatus of Example 15, wherein the one or more processors are further configured to: decode, at the eNB, an X2-AP path switch response message received from the previous eNB of the UE when the delivery status of the Msg4 to the UE is unsuccessful.

Example 18 includes the apparatus of Example 15, wherein the one or more processors are further configured to: encode, at the eNB for transmission to the previous eNB of the UE, an X2-AP UE context release message when the delivery status of the Msg4 to the UE is successful.

Example 19 includes the apparatus of Example 15, wherein the one or more processors are further configured to: encode, at the eNB for transmission to a mobility management entity (MME), an S1-AP path switch request; or decode, at the eNB, an S1-AP path switch request acknowledgement (ACK) received from the MME; or decode, at the eNB, an S1 suspend procedure received from the MME.

Example 20 includes the apparatus of any of Examples 15 to 19, wherein Msg4 is a radio resource control (RRC) Connection Release message.