WO2018063453A1 - Commande de surcharge de réseau central pour système de paquet évolué à plan de command - Google Patents

Commande de surcharge de réseau central pour système de paquet évolué à plan de command Download PDF

Info

Publication number
WO2018063453A1
WO2018063453A1 PCT/US2017/035970 US2017035970W WO2018063453A1 WO 2018063453 A1 WO2018063453 A1 WO 2018063453A1 US 2017035970 W US2017035970 W US 2017035970W WO 2018063453 A1 WO2018063453 A1 WO 2018063453A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
connection
data
mme
bearer
Prior art date
Application number
PCT/US2017/035970
Other languages
English (en)
Inventor
Puneet Jain
Marta MARTINEZ TARRADELL
Original Assignee
Intel IP Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel IP Corporation filed Critical Intel IP Corporation
Priority to CN201780053482.9A priority Critical patent/CN109923879B/zh
Publication of WO2018063453A1 publication Critical patent/WO2018063453A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H04W12/033—Protecting confidentiality, e.g. by encryption of the user plane, e.g. user's traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H04W12/037—Protecting confidentiality, e.g. by encryption of the control plane, e.g. signalling traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/80—Arrangements enabling lawful interception [LI]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]

Definitions

  • Embodiments of the present disclosure generally relate to the field of networks, and more particularly, to apparatuses, systems, and methods for core network overload control for a control plane evolved packet system.
  • CIoT Internet of things
  • CN core network
  • EPS evolved packet system
  • MME mobility management entity
  • NAS non-access stratum
  • Figure 1 illustrates an architecture of a system in accordance with some embodiments.
  • Figure 2 illustrates a control plane protocol stack in accordance with some embodiments.
  • Figure 3 illustrates a flow in accordance with some embodiments.
  • FIG. 4 illustrates a flow in accordance with other embodiments.
  • Figure 5 illustrates an example operation flow/algorithmic structure of a user equipment according to some embodiments.
  • Figure 6 illustrates an example operation flow/algorithmic structure of an access node according to some embodiments.
  • Figure 7 illustrates an example operation flow/algorithmic structure of a mobility management entity according to some embodiments.
  • Figure 8 illustrates a device according to some embodiments.
  • FIG. 9 illustrates hardware resources in accordance with some embodiments.
  • the phrases “A or B,” “A and/or B,” and “A/B” mean (A), (B), or (A and B).
  • the description may use the phrases “in an embodiment,” or “in embodiments,” which may each refer to one or more of the same or different embodiments.
  • the terms “comprising,” “including,” “having,” and the like, as used with respect to embodiments of the present disclosure, are synonymous.
  • FIG. 1 illustrates an architecture of a system 100 of a network in accordance with some embodiments.
  • the system 100 is shown to include a user equipment (UE) 104.
  • the UE 104 may be a smartphone (for example, a 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 Personal Data Assistants (PDAs), pagers, Internet of things (“IoT”) devices, smart sensors, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
  • PDAs Personal Data Assistants
  • IoT Internet of things
  • the UE 104 may also include a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • An IoT UE can utilize technologies such as machine-to-machine (“M2M”) or machine-type communications (“MTC”) for exchanging data with an MTC server or device via a public land mobile network (“PLMN”), Proximity-Based Service (“ProSe”) or device-to-device (“D2D”) communication, sensor networks, or IoT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the IoT UEs may execute background applications (for example, keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
  • the UE 104 may be configured to connect, for example, communicatively couple, with an access node 108 of a radio access network (“RAN”) 1 10 via a Uu interface.
  • the RAN 1 10 may be, for example, an Evolved Universal Terrestrial Radio Access Network ("E- UTRAN”) in which case the access node 108 may be an evolved node B ("eNB"), a NextGen RAN (“NG RAN”) in which case the access node 108 may be a next generation node B (“gNB”), or some other type of RAN.
  • E- UTRAN Evolved Universal Terrestrial Radio Access Network
  • eNB evolved node B
  • NG RAN NextGen RAN
  • the UE 104 may utilize an air-interface protocol to enable communicative coupling over the Uu interface.
  • the air-interface protocol can be consistent with cellular communications protocols such as a Globalstar
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT push-to-talk
  • POC PTT over cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE 3GPP Long Term Evolution
  • 5G fifth generation
  • NR New Radio
  • the access node 108 can terminate the air-interface protocol and can be the first point of contact for the UE 104.
  • the access node 108 can fulfill various logical functions for the RAN 110 including, 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.
  • RNC radio network controller
  • the UE 104 may perform a number of operations.
  • the first operation may include, for example, synchronizing with a frequency to identify an operator with which the UE 104 is to connect.
  • the UE 104 may be able to read and process information blocks such as, for example, master information block ("MIB”) and system information blocks (“SIBs”), to obtain information used to access a cell provided by the access node 108.
  • MIB master information block
  • SIBs system information blocks
  • the UE 104 may then perform a random access procedure to request the access node 108 to provide the UE 104 temporary resources for initial communication.
  • the UE 104 may establish a radio resource control (“RRC") connection by sending an RRC connection request message, which may also be referred to as an RRC Msg 3; receiving an RRC connection setup message; and sending an RRC connection setup complete message, which may be referred to as an RRC Msg 5.
  • RRC radio resource control
  • the UE 104 may be in an RRC- CONNECTED state after sending the RRC connection setup complete message.
  • the RRC connection request message may include a UE identity, which may include a temporary mobile subscriber identity ("TMSI”) or a random value, and a connection establishment cause.
  • the RRC connection setup message may include a default configuration for a first signaling radio bearer (SRBl) and other configuration information related to, for example, physical uplink shared channel (“PUSCH”), physical uplink control channel (“PUCCH”), physical downlink shared channel (“PDSCH”), channel quality indicator (“CQI”) report, sounding reference signal, antenna configuration, scheduling request, etc.
  • the RRC connection setup complete message may include information about a selected PLMN and UE- specified NAS layer information.
  • the UE 104 can be configured to communicate using Orthogonal Frequency-Division Multiplexing ("OFDM") communication signals with other UEs or with the access node 108 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (“OFDMA”) communication technique (for example, for downlink communications) or a Single Carrier Frequency Division Multiple Access (“SC-FDMA”) communication technique (for example, for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect.
  • OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink
  • the grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time-frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated.
  • the PDSCH may carry user data and higher-layer signaling to the UE 104.
  • the physical downlink control channel (“PDCCH”) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UE 104 about the transport format, resource allocation, and hybrid automatic repeat request ("H-ARQ") information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 104 within a cell) may be performed at the access node 108 based on channel quality information fed back from the UE 104.
  • the downlink resource assignment information may be sent on the PDCCH used for (for example, assigned to) the UE 104.
  • the PDCCH may use control channel elements ("CCEs”) to convey the control information.
  • CCEs control channel elements
  • the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching.
  • Each PDCCH may be sent using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups ("REGs").
  • REGs resource element groups
  • QPSK Quadrature Phase Shift Keying
  • the PDCCH can be sent using one or more CCEs, depending on the size of the downlink control information ("DO") and the channel condition.
  • DO downlink control information
  • There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (for example, aggregation level, L l, 2, 4, or 8).
  • some embodiments may utilize an enhanced physical downlink control channel
  • EPDCCH that uses PDSCH resources for control information transmission.
  • the EPDCCH may be sent using one or more enhanced control channel elements ("ECCEs"). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (“EREGs"). An ECCE may have other numbers of EREGs in some situations.
  • ECCEs enhanced control channel elements
  • the RAN 110 may be communicatively coupled to a core network ("CN") 116 through an SI interface.
  • the communications over the SI interface may be compatible with an SI Application protocol (SIAP).
  • the CN 116 may be an evolved packet core (“EPC") network, a NextGen Packet Core (“NPC”) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the SI interface may be split into two parts: an Sl-U interface, which carries traffic data between the access node 108 and serving gateway (“S-GW")/packet gateway (“P-GW”) 120, and an Sl-mobility management entity (“MME”) interface, which is a signaling interface between the access node 108 and an MME 124. While shown together in Figure 1, the S-GW and the P-GW may alternatively be implemented in different devices, servers, etc.
  • the CN 116 comprises the S-GW/P-GW 120, the MME 124, and a service capability exposure function ("SCEF") 128.
  • the MME 124 may be similar in function to the control plane of legacy Serving General Packet Radio Service (“GPRS") Support Nodes ("SGSN").
  • the MME 124 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the S-GW of the S-GW/P-GW 120 may terminate the Sl-U interface towards the RAN 110, and may route data packets between the RAN 110 and the CN 116.
  • the S- GW may 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 P-GW of the S-GW/P-GW 120 may terminate an SGi interface toward a packet data network ("PDN") 132.
  • the P-GW may route data packets between the CN 116 and external networks such as the PDN 132.
  • the PDN 132 may include an application server ("AS") 136 (alternatively referred to as application function ("AF")) that is
  • IP Internet Protocol
  • the application server 136 may be an element offering applications that use IP bearer resources with the CN 116 (for example, UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • the application server 136 can also be configured to support one or more communication services (for example, Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 104 via the CN 116.
  • VoIP Voice-over-Internet Protocol
  • the SCEF 128 may be the device used to securely expose the security and capabilities provided by 3GPP network interfaces.
  • the SCEF 128 may perform a variety of functions that may provide, for example, entities external to a 3GPP network the ability to discover service capabilities of components within the 3GPP network. These functions may include, for example, authentication and authorization, policy enforcement, assurance, accounting, access, abstraction, etc.
  • the SCEF 128 may protect entities of the CN116 from requests exceeding permissions provided in a service level agreement with a third- party service provider.
  • the components of the system 100 may cooperate to provide one or more PDN connections that connect the UE 104 to the PDN 132.
  • a PDN connection may be established with the creation of a default EPS bearer.
  • the default EPS bearer may be associated with a default quality of service ("QoS"). If the PDN connection is to handle a type of service that requires specific QoS handling, for example, voice or video streaming, additional EPS bearers, referred to as dedicated EPS bearers, may be created and associated with specific QoSs.
  • a PDN connection may be an SCEF connection routed through the SCEF 128 or an SGi connection routed through the S-GW/P-GW 120.
  • Figure 1 shows different routing paths, over various PDN connections, which may be used for CIoT optimizations.
  • Path 1 may be for data routing over an SCEF connection using control plane CIoT EPS optimization. This connection is always pinned to the control plane (in other words, it cannot be switched to the user plane).
  • Path 2 may be for data routing over an SGi connection using control plane CIoT EPS optimization. This connection may or may not be pinned to the control plane.
  • Path 3 may be for data routing over an SGi connection using user plane EPS CIoT optimization (or legacy Sl-U).
  • UP user plane
  • CP control plane
  • data could be routed via paths 1 and 3, or via paths 1 and 2 within the same RRC connection.
  • the UE 104 If the UE 104 is in an RRC-CONNECTED state, it may only have path 2 connections or path 3 connections active, but not both at the same time (for the same or different PDN), and may only transition from path 2 to path 3 (but not vice-versa).
  • FIG. 2 illustrates a control plane protocol stack in accordance with some embodiments.
  • a control plane 200 is shown as a communications protocol stack between the UE 104, the AN 108, and the MME 124.
  • the physical (“PHY”) layer 204 may transmit/receive information used by the media access control (“MAC”) layer 208 over one or more air interfaces.
  • the PHY layer 204 may further perform link adaptation or adaptive modulation and coding (“AMC”), power control, cell search (for example, for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer 220.
  • the PHY layer 204 may still further perform error detection on the transport channels, forward error correction (“FEC”) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and multiple input multiple output (“MIMO”) antenna processing.
  • FEC forward error correction
  • the MAC layer 208 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units ("SDUs") from one or more logical channels onto transport blocks to be delivered to the PHY layer 204 via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks delivered from the PHY layer 204 via transport channels, multiplexing MAC SDUs onto transport blocks, scheduling information reporting, error correction through hybrid automatic repeat request ("H-ARQ”), and logical channel prioritization.
  • SDUs MAC service data units
  • H-ARQ hybrid automatic repeat request
  • the radio link control (“RLC") layer 212 may operate in a plurality of modes of operation, including: Transparent Mode (“TM”), Unacknowledged Mode (“UM”), and
  • the RLC layer 212 may execute transfer of upper layer protocol data units (“PDUs”), error correction through automatic repeat request (“ARQ”) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers.
  • the RLC layer 212 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re- establishment.
  • the packet data convergence protocol (“PDCP") layer 216 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers ("SNs"), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (for example, ciphering, deciphering, integrity protection, integrity verification, etc.).
  • SNs PDCP Sequence Numbers
  • the main services and functions of the RRC layer 220 may include broadcast of system information (for example, included in Master Information Blocks ("MIBs") or
  • MIBs Master Information Blocks
  • SIBs System Information Blocks
  • NAS non-access stratum
  • SIBs System Information Blocks
  • UE access stratum
  • paging for example, RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release
  • RRC connection release for example, RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release
  • RAT inter radio access technology
  • SIBs may comprise one or more information elements (“IEs”), which may each comprise individual data fields or data structures.
  • the RRC layer 220 and below layers may be generically referred to as the AS.
  • the UE 104 and the AN 108 may utilize a Uu interface (for example, an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 204, the MAC layer 208, the RLC layer 212, the PDCP layer 216, and the RRC layer 220.
  • a Uu interface for example, an LTE-Uu interface
  • the NAS layer 224 may form the highest stratum of the control plane between the UE 104 and the MME 124.
  • the NAS layer 224 may support the mobility of the UE 104 and the session management procedures to establish and maintain IP connectivity between the UE 104 and the P-GW.
  • the S I Application Protocol (“S l-AP”) layer 228 may support the functions of the SI interface and comprise Elementary Procedures ("EPs").
  • An EP may be a unit of interaction between the AN 108 and the CN 116.
  • the Sl-AP layer services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer ("E- RAB”) management, UE capability indication, mobility, NAS signalling transport, RAN Information Management (“RIM”), and configuration transfer.
  • E- RAB E-UTRAN Radio Access Bearer
  • RAM Radio Access Management
  • the Stream Control Transmission Protocol (“SCTP") layer (altematively referred to as the SCTP/IP layer) 232 may ensure reliable delivery of signalling messages between the AN 108 and the MME 124 based on the IP protocol supported by the IP layer 236.
  • the L2 layer 240 and the LI layer 244 may refer to communication links (for example, wired or wireless) used by the AN 108 and the MME 124 to exchange information.
  • the AN 108 and the MME 124 may utilize an S I -MME interface to exchange control plane data via a protocol stack comprising the LI layer XVI 1, the L2 layer XV12, the IP layer XV13, the SCTP layer XV14, and the Sl-AP layer XV15.
  • an eNB may be informed by an MME of an overload condition of a CN over the Sl-AP and the eNB may take the decision of rejecting RRC connection requests for any UE. However, the eNB may still not know if the RRC connection request is for sending data via control plane or user plane.
  • embodiments described herein provide a way in which the access node 108 may differentiate whether the RRC connection is for user plane (for example, a service request or extended service request) or for control plane (for example, a control plane service request).
  • the UE 104 may only support control plane CIoT EPS
  • the access node 108 can parse the NAS message received inside an RRC msg 5 (rather than transparently relaying the NAS message to the MME 124) to determine whether it is a control plane service request.
  • a new CP- data indication may be defined in Msg 3 (for example, the RRC connection request).
  • the new CP-data indication may be added through a new information element or through a new establishment cause.
  • a new logical channel identity ("LCID") for RRC msg 3 (e.g., RRC connection request) may be used.
  • a new CP-data indication IE may be defined in RRC msg 5 (for example, RRC connection setup complete).
  • An RRC connection request may be defined as shown below in order to add a new CP- data indication through a new information element.
  • the RRC Connection Request message is used to request the establishment of an RRC connection.
  • the RRC Connection Request message may be sent on signal radio bearer 0 ("SRBO") from the UE 104 to the RAN 110; have a transparent mode ("TM") radio link control - service access point (“RLC-SAP"); and be sent in a logical channel such as the common control channel (“CCCH”).
  • SRBO signal radio bearer 0
  • TM transparent mode
  • RLC-SAP radio link control - service access point
  • CCCH common control channel
  • the RRC Connection Request message may have an abstract syntax notation one
  • the RRC Connection Request message may include a CP-Data field and a CP- Only-Connection field. These fields may be enumerated type fields.
  • a value of true for the CP-Data field may indicate that an RRC connection may be established for the purposes of sending data via control plane CIoT EPS optimization.
  • a value of true for the CP-Only - Connection field may indicate that the RRC connection is pinned to the control plane (for example, the RRC connection is only used to send the data via control plane optimization and cannot switch to user plane).
  • An RRC connection may have both a signaling radio bearer (SRB) and a data radio bearer (DRB).
  • SRB signaling radio bearer
  • DRB data radio bearer
  • Msg 3 may only have one spare bit and, therefore, two indicators may be multiplexed.
  • the CP-Only-Connection value may also indicate that CP-Data.
  • Msg 3 could rely on a larger UL grant.
  • an RRC connection request message may be used to provide the CP-data indication via a new establishment cause in altemative 2.
  • An establishment cause may provide an indication of why the UE 104 needs to connect to the network.
  • the establishment cause may be determined by a NAS procedure for which an RRC connection is being established.
  • the below message may be sent on SRBO from the UE 104 to the RAN 110; have a TM RLC-SAP; and be sent in a logical channel such as the CCCH.
  • the RRC Connection Request message may have an ASN.l structure as shown below.
  • CP-Data and CP-Only-Connection values are added as possible values that may be used in the establishment cause.
  • a new LCID may be used for Msg 3.
  • a MAC header for a downlink shared channel (“DL-SCH”), uplink shared channel (“UL-SCH”), and multicast channel (“MCH”) may be of variable size and consists of the following fields: LCID; L; F; F2; and E.
  • the LCID field may include an LCID value that identifies the logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC control element or padding as described in Tables 1 and 2 (below) for the DL-SCH and UL-SCH, respectively. Except as otherwise noted, Tables 1 and 2 may be similar to Tables 6.2.1-1 and 6.2.1-2 of 3GPP TS 36.321 vl4.2.0 (2017-03).
  • the UE 104 may indicate CCCH using LCID "01011"; if the UE 104 is sending data using CP EPS CIoT optimization, the UE 104 may indicate CCCH using LCID "01100"; and the UE 104 may indicate CCCH using LCID "00000” otherwise.
  • the LCID field size may be 5 bits.
  • the L field may include a length value to indicate the length of the corresponding MAC SDU or variable-sized MAC control element in bytes. There may be one L field per MAC PDU subheader except for the last subheader and subheaders corresponding to fixed-sized MAC control elements. The size of the L field may be indicated by the F field and F2 field.
  • the F field may include a format value to indicate the size of the L field. There may be one F field per MAC PDU subheader except for the last subheader and subheaders corresponding to fixed-sized MAC control elements and except for when F2 is set to 1.
  • the size of the F field may be 1 bit. If the F field is included, if the size of the MAC SDU or variable-sized MAC control element is less than 128 bytes, the value of the F field may be set to 0; otherwise it may be set to 1.
  • the F2 field may include a format2 value to indicate the size of the L field. There may be one F2 field per MAC PDU subheader. The size of the F2 field may be 1 bit. If the size of the MAC SDU or variable-sized MAC control element is larger than 32,767 bytes, and if the corresponding subheader is not the last subheader, the value of the F2 field may be set to 1, otherwise it may be set to 0.
  • the E field may include an extension flag to indicate whether more fields are present in the MAC header or not.
  • the E field may be set to " 1 " to indicate another set of at least R/F2/E/LCID fields.
  • the E field may be set to "0" to indicate that either a MAC SDU, a MAC control element or padding starts at the next byte.
  • the R field may include a reserved bit set to "0.”
  • the MAC header and subheaders may be octet aligned.
  • LCID values for DL-SCH may be applicable: CCCH, Identity of the logical channel, UE Contention Resolution Identity, Timing Advance Command, discontinuous reception (“DRX”) Command and Padding.
  • LCID values for UL-SCH may be applicable: CCCH (LCID "00000”), identity of the logical channel, cell radio network temporary identifier (“C-RNTI”), short buffer status report (“BSR”) and padding.
  • C-RNTI cell radio network temporary identifier
  • BSR short buffer status report
  • the NAS layer 224 of the UE 104 will provide a CP-data indication to the AS of the UE 104 (for example, to the RRC 220 of the UE 104) indicating that a NAS message contains data that is to be sent via Control plane CIoT EPS optimization.
  • the AS of the UE 104 may establish an RRC Connection and send msg 5 (for example, RRC connection setup complete, which may be used to confirm the successful establishment of an RRC connection) by including new CP-data indication IE in msg 5.
  • the AN 108 can reject msg 5 with a cause code - Control Plane data overload and provide a backoff timer value to the UE in an RRC reject message.
  • One potential advantage is that eNB can let MME decide for switching to user plane based on this indication.
  • Example ASN.1 defining this new indication is shown below for reference using RRC Connection Request and RRC Connection Setup complete as reference; however similar field could also be defined in other msg.3 or msg.5 as it is explained previously.
  • LTE RRC messages are used; however the same new field could be defined on the equivalent NB-IoT messages, e.g. RRCConnectionSetupComplete-NB.
  • the RRC connection setup complete message may be sent on SRB1 from the UE 104 to the RAN 110; have an acknowledged mode ("AM") RLC-SAP; and be sent in a logical channel such as a dedicated control channel (“DCCH”).
  • the RRC Connection Request message may have an ASN.1 structure as shown below.
  • the CP-data field may be included (and set to "true") when the UE 104 sends data using the control plane CIoT EPS optimization.
  • the CP-Only-Connection field may be included (and set to "true") when the UE 104 sends data using the control plane CIoT EPS optimization over an EPS bearer that is pinned to control plane CIoT EPS optimization.
  • alternative 3 may include an LCID value being used to indicate whether the UE 104 sends data using the control plane CIoT EPS optimization over an EPS bearer that is pinned to control plane CIoT EPS optimization.
  • an eNB may directly reject RRC msg 3 messages when they include a CP-Only-Connection indication (and MME is overloaded). If the RRC msg 3 doesn't indicate anything it may be assumed that it is not pinned to the CP. Then later Alternative 4 can be used, for example, RRC msg 5 could indicate that it is CP-data. Therefore, the information is sent in 2 parts.
  • the UE 104 may support both control plane and user plane optimization. If the UE 104 supports both EPS CIoT optimizations and has an SGi PDN connection that is not pinned to CP (for example, path 2 of Figure 1), then the UE 104 may be able to switch from CP to UP if the congestion is due to control plane data.
  • the NAS layer 224 of the UE 104 may provide a CP-data indication to the RRC layer 220 of the UE 104 to indicate that a NAS message contains data that is to be sent via Control plane CIoT EPS optimization.
  • the RRC layer 220 of the UE 104 may then establish RRC Connection and may send msg 5 (for example, RRC connection setup complete) including a CP-data indication IE. If the AN 108 has received an Sl-AP overload start command from the MME 124, the AN 108 can reject the RRC msg 5 with cause code - Control Plane data overload and provide a backoff timer value to the UE in an RRC reject message. Since the UE 104 also supports UP EPS CIoT optimization (or legacy Sl-U), the UE 104 can decide to establish a new RRC connection for UP by sending a NAS Service Request in msg 5.
  • some embodiments may have the MME 124 switch the connection to the user plane if SGi PDN connection is not pinned to the control plane.
  • Figure 3 illustrates a flow 300 for the MME 124 switching from control plane to user plane due to congestion from control plane data in accordance with some embodiments.
  • the UE 104 may send an RRC msg 5 at 304.
  • the RRC msg 5 may include a NAS control plane service request ("CPSR") message.
  • the CPSR message may be a NAS message that is integrity protected.
  • the CPSR message may include an EPS bearer ID (“EBI”) and encrypted uplink data.
  • the RRC msg 5 may also include a CP-data indication to indicate that a user data transport message is sent in the CPSR message.
  • the RRC msg 5 may also include a CP-only-connection to indicate whether an EPS bearer that corresponds to the EBI is pinned to the control plane.
  • the AN 108 may, at 308, determine whether the RRC msg 5 includes control plane data for the MME 124, which is congested (as previously indicated to the AN 108). The AN 108 may then determine whether the msg 5 has the CP-only-connection set to true or false. If the CP-only-connection is set to true, indicating that the EBI is pinned to the control plane only, and the MME 124 has indicated the AN 108 is to stop loads for CP data, the AN 108 may send an RRC reject message to the UE 104 and the flow may stop here.
  • the AN 108 may determine that the EBI is not pinned to the control plane only. The AN 108 may then send the Sl-AP initial UE message to the MME 124 at 312. The Sl-AP initial UE message may include the CPSR message with the EBI.
  • the MME 124 may check whether the EBI received in the Sl-AP message is pinned to the control plane or not. Given that the access node 108 will likely reject an RRC msg 5 with CP-only-connection set to true, the chances of the MME 124 receiving an Sl-AP initial UE message with an EBI pinned to the control plane may be relatively small when the MME is overloaded.
  • the MME 124 may decide, based on operator policy, to switch the connection to the user plane.
  • the MME 124 may also decide to forward the data in the CPSR message via SI 1-U.
  • the MME 124 may decide to inform the UE 104 to resend data over a user plane by including a new indicator in aNAS response/Sl-AP message.
  • the flow 300 may include the message exchange at 320 and 324.
  • the MME 124 may send a modify bearer request at 320 to the S-GW/P-GW 120 to modify an existing bearer.
  • the S-GW/P-GW 120 may then transmit, in response, a modify bearer response at 324 to the MME 124.
  • the message exchange at 320 and 324 may also be used if the
  • MME 124 decides to establish an Sl-U interface, between the UE 104 and the S-GW/P- GW 120, for the UE 104 to resend data over a user plane connection. If the MME 124 decides to forward data in the CPSR over the control plane via an SI 1-U interface, the MME 124 may send the uplink data at 328 to the S-GW/P-GW 120.
  • the flow 300 may include, at 332, the MME 124 deciding to switch to a user plane.
  • the MME 124 may initiate establishment of a DRB and Sl-U interface by sending an Sl-AP initial context setup request ("ICSR") message at 336.
  • the Sl-AP ICSR message may include a control plane backoff timer ("BOT") value and an indication to resend the data over the user plane.
  • BOT control plane backoff timer
  • the CP BOT value may prevent the UE 104 from sending further uplink data over the control plane connection for a period of time.
  • the flow 300 may further include the AN 108 and UE 104 performing a radio bearer establishment procedure at 340 to establish the DRB.
  • the AN 108 may send an RRC downlink ("DL") message.
  • the RRC downlink message may include the control plane backoff timer and the indication to resend the data.
  • the UE 104 may send the data over the user plane to the AN 108 at 348.
  • the AN 108 may further send the UL data over the user plane to the S-GW/P-GW 120 at 352.
  • Figure 4 illustrates a flow 400 for an overload start message for data transfer via control plane for a CP-pinned connection in accordance with some embodiments.
  • the flow 400 may include, at 404, the MME 124 determining an overload condition at the MME 124.
  • the overload condition may be determined when a volume of traffic that includes, for example, control plane EPS optimization data reaches a predetermined threshold.
  • the MME 124 may initiate procedures to restrict data transfer via control plane CIoT EPS optimization.
  • the criteria for restricting control plane data transfers, for example, the predetermined threshold, and the procedures to do so may be based on operator's policy or configuration.
  • the MME 124 may send an Sl-AP overload start message to the AN 108 at 408.
  • the Sl-AP overload start message may include a control plane CIoT data parameter that informs the AN 108 that the MME 124 is overloaded.
  • the overload condition determined at 404 and signaled at 408 may indicate that the MME 124 is close to being overloaded, rather than already overloaded.
  • the Sl-AP overload start message may also include a CP-only indication to indicate that the AN 108 is to perform overload restrictions with respect to CP-pinned connections only. In the event that the CP-only indication is not included in the Sl-AP overload start message, the AN 108 may perform overload restrictions with respect to all connections.
  • the flow 400 may further include, at 412, the UE 104 sending RRC msg 5 to the AN 108.
  • the RRC msg 5 may include a CP-data indicator to indicate that the RRC msg 5 includes control plane data.
  • the RRC msg 5 may also include the CP-only connection indicator to indicate that the EPS bearer is pinned to the control plane.
  • the AN 108 may, at 416, check to determine whether the RRC msg 5 is for a congested MME and whether it corresponds to a CP-pinned connection.
  • the access node 108 may check to determine whether the RRC msg 5 includes an MME identity, for example, a registeredMME parameter, that identifies an MME that is previously sent an Sl-AP overload start message. If, for example, the RRC msg 5 includes an MME identity that corresponds to MME 124, for this embodiment, the access node 108 may determine that the RRC msg 5 is for a congested MME.
  • the AN 108 may send a CP-data message to the MME 124.
  • the MME 124 may decide to switch the control plane to the user plane as shown above with respect to Figure 3.
  • the AN 108 may send an RRC reject message to the UE 104 at 420.
  • the RRC reject message may include a backoff timer value.
  • the UE 104 may start a backoff timer with the backoff timer value received in the RRC connection reject message. Upon expiration of the backoff timer, the UE 104 may send additional messages to send data via the control plane.
  • the access node 108 may be coupled with more than one MME. If the access node 108 receives an overload message from a first MME, it may still be able to send a CP-data message to a second MME with which it is connected.
  • FIG. 5 illustrates an example operation flow/algorithmic structure of the UE 104 according to some embodiments.
  • the flow/structure 500 may include, at 504, generating and sending a CP-data message.
  • the CP-data message may be generated by the NAS layer 224 of the UE 104 providing a NAS message and a CP-data indication to the AS of the UE 104.
  • the CP-data indication may indicate that the NAS message contains data that is to be sent via control plane CIoT EPS optimization.
  • the AS of the UE 104 may then generate and send one or more RRC messages (for example, an RRC msg 3 or RRC msg 5) with, for example, the CP-data indication or the CP-only-connection indication as discussed above.
  • RRC messages for example, an RRC msg 3 or RRC msg 5
  • the flow/structure 500 may further include, at 508, receiving an RRC message from the AN 108.
  • the RRC message may be an RRC DL message as described in Figure 3 or an RRC connection reject message as described in Figure 4.
  • the RRC message may include a CP BOT value.
  • the RRC message may include a resend indicator that instructs the UE 104 to resend data previously sent in the CP-data message.
  • the flow/structure 500 may further include, at 512, setting a backoff timer with the CP BOT value received in the RRC message.
  • the backoff timer may be reset to the new CP-BOT value.
  • the CP BOT value may be added to the remaining time on the backoff timer when the new CP BOT value is received.
  • the flow/structure 500 may further include, at 516, generating and sending another CP- data message.
  • the other CP-data message may be generated similar to the CP-data message generated at 504.
  • the other CP-data message may be sent after expiration of the backoff timer.
  • Figure 6 illustrates an example operation flow/algorithmic structure 600 of the AN 108 according to some embodiments.
  • the flow/structure 600 may include, at 604, processing a CPSR message.
  • the CPSR message may include an EBI that identifies an EPS bearer of the UE 104.
  • the CPSR may be included in an RRC message such as an RRC msg 3 or an RRC msg 5.
  • the CPSR message, or the encapsulating RRC message may further include an MME identity that corresponds to MME 124 in some embodiments.
  • the flow/structure 600 may further include, at 608, determining whether the MME indicated in the CPSR, for example, the MME 124, is overloaded.
  • the AN 108 may determine that the MME 124 is overloaded based on a prior receipt of an Sl-AP overload start message from the MME 124. If it is determined, at 608, that the MME 124 is not overloaded, the flow/structure 600 may further include, at 612, forwarding the CPSR message to the MME 124. In some embodiments, the CPSR message may be forwarded to the MME 124 in an Sl-AP initial UE message.
  • the flow/structure 600 may further include, at 616, determining whether the data is to be sent by a bearer that is pinned to a CP-only connection.
  • the AN 108 may determine whether the data is to be sent by a bearer that is pinned to the CP-only connection by checking for a CP-only field in the RRC message that transmits the CPSR message.
  • the flow/structure 600 may advance to forwarding the CPSR message to the MME 124 at 612.
  • the flow/structure 600 may advance to sending an RRC connection reject message at 620.
  • the RRC connection reject message may include a CP BOT value that the UE 104 may use to start a CP backoff timer.
  • Figure 7 illustrates an example operation flow/algorithmic structure 700 of the MME 124 according to some embodiments.
  • the flow/structure 700 may include, at 704, processing a CPSR message.
  • the CPSR message may include an EBI that identifies an EPS bearer of the UE 104.
  • the CPSR may be included in an S l-AP initial UE message.
  • the flow/structure 700 may further include, at 708, detecting an overload condition in a network.
  • the overload condition may be detected by comparing levels of a certain type of traffic to a predetermined threshold.
  • the MME 124 may compare a level of CP CIoT EPS optimization traffic to a predetermined threshold that is configured in accordance with operator policy. If the detected traffic exceeds the predetermined threshold, the MME 124 may detect an overload condition.
  • the flow/structure 700 may advance to sending data over the control plane at 712. If, at 708, an overload condition is detected, the flow/structure 700 may advance to determining whether the EPS bearer identified by the EBI is pinned to a CP-only connection at 716. The MME 124 may determine whether the data is to be sent by a bearer that is pinned to the CP-only connection by checking for a CP-only field in the S l-AP initial UE message that transmits the CPSR message.
  • the flow/structure 700 may advance to rejecting the message at 720.
  • the message may be rejected by sending a reject message to the AN 108.
  • the situation may happen infrequently given that the AN 108 may have already rejected an RRC message if it was pinned to CP-only connection and the MME 124 was overloaded.
  • the flow/structure may advance to initiating establishment of an SI -U bearer at 724. This may be the result of the MME 124 deciding to switch from the control plane to the user plane.
  • the MME 124 may send an Sl-AP message to the AN 108.
  • the Sl- AP message may be an S l-AP initial context setup request message that may, in some embodiments, include a CP BOT value for the UE.
  • Figure 8 illustrates, for one embodiment, example components of an electronic device 800.
  • the electronic device 800 may be, implement, be incorporated into, or otherwise be a part of the UE 104, the AN 108, the MME 124 or some other electronic device.
  • the electronic device 800 may include application circuitry 802, baseband circuitry 804, Radio Frequency ("RF") circuitry 806, front-end module (“FEM”) circuitry 808 and one or more antennas 810, coupled together at least as shown.
  • RF Radio Frequency
  • FEM front-end module
  • the electronic device 800 may also include network interface circuitry (not shown) for communicating over a wired interface (for example, an X2 interface, an S 1 interface, and the like).
  • circuitry may refer to, be part of, or include
  • circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware.
  • the application circuitry 802 may include one or more application processors.
  • the application circuitry 802 may include circuitry such as, but not limited to, one or more single-core or multi-core processors 802a.
  • the processor(s) 802a may include any combination of general -purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors 802a may be coupled with and/or may include computer-readable media 802b (also referred to as "CRM 802b,” “memory 802b,” “storage 802b,” or “memory /storage 802b”) and may be configured to execute instructions stored in the CRM 802b to enable various applications
  • the baseband circuitry 804 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 804 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 806 and to generate baseband signals for a send signal path of the RF circuitry 806.
  • Baseband circuity 804 may interface with the application circuitry 802 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 806.
  • the baseband circuitry 804 may include a second generation (“2G") baseband processor 804a, third generation (“3G”) baseband processor 804b, fourth generation (“4G”) baseband processor 804c, fifth generation (“5G”) baseband processor 804h, and/or other baseband processor(s) 804d for other existing generations, generations in development or to be developed in the future (e.g., 6G, etc.).
  • the baseband circuitry 804 e.g., one or more of baseband processors 804a-d, h
  • the radio control functions may include, but are not limited to, signal
  • modulation/demodulation circuitry of the baseband circuitry 804 may include Fast-Fourier Transform (FFT), precoding, and/or
  • encoding/decoding circuitry of the baseband circuitry 804 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 804 may include elements of a
  • a central processing unit (CPU) 804e of the baseband circuitry 804 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers.
  • the baseband circuitry 804 may include one or more audio digital signal processor(s) (DSP) 804f.
  • the audio DSP(s) 804f may include elements
  • the baseband circuitry 804 may further include computer-readable media 804g (also referred to as “CRM 804g,” “memory 804g,” “storage 804g,” or “CRM 804g”).
  • CRM 804g may be used to load and store data and/or instructions for operations performed by the processors of the baseband circuitry 804.
  • CRM 804g for one embodiment may include any combination of suitable volatile memory and/or non-volatile memory.
  • the CRM 804g may include any combination of various levels of memory /storage including, but not limited to, read-only memory (ROM) having embedded software instructions (e.g., firmware), random access memory (e.g., dynamic random access memory (DRAM)), cache, buffers, etc.
  • ROM read-only memory
  • DRAM dynamic random access memory
  • the CRM 804g may be shared among the various processors or dedicated to particular processors.
  • Components of the baseband circuitry 804 may be suitably combined in a single chip or a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 804 and the application circuitry 802 may be implemented together, such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 804 may provide for
  • the baseband circuitry 804 may support communication with an E-UTRAN and/or other wireless metropolitan area networks ("WMAN”), a wireless local area network (“WLAN”), a wireless personal area network (“WPAN”).
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments in which the baseband circuitry 804 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 806 may enable communication with wireless networks
  • the RF circuitry 806 may include switches, filters, amplifiers, etc., to facilitate the communication with the wireless network.
  • RF circuitry 806 may include a receive signal path that may include circuitry to down-convert RF signals received from the FEM circuitry 808 and provide baseband signals to the baseband circuitry 804.
  • RF circuitry 806 may also include a send signal path that may include circuitry to up-convert baseband signals provided by the baseband circuitry 804 and provide RF output signals to the FEM circuitry 808 for transmission.
  • the RF circuitry 806 may include a receive signal path and a send signal path.
  • the receive signal path of the RF circuitry 806 may include mixer circuitry 806a, amplifier circuitry 806b and filter circuitry 806c.
  • the send signal path of the RF circuitry 806 may include filter circuitry 806c and mixer circuitry 806a.
  • RF circuitry 806 may also include synthesizer circuitry 806d for synthesizing a frequency for use by the mixer circuitry 806a of the receive signal path and the send signal path.
  • the mixer circuitry 806a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 808 based on the synthesized frequency provided by synthesizer circuitry 806d.
  • the amplifier circuitry 806b may be configured to amplify the down-converted signals and the filter circuitry 806c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • LPF low-pass filter
  • BPF band-pass filter
  • Output baseband signals may be provided to the baseband circuitry 804 for further processing.
  • the output baseband signals may be zero-frequency baseband
  • mixer circuitry 806a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 806a of the send signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 806d to generate RF output signals for the FEM circuitry 808.
  • the baseband signals may be provided by the baseband circuitry 804 and may be filtered by filter circuitry 806c.
  • the filter circuitry 806c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
  • LPF low-pass filter
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the send signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion, respectively.
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the send signal path may include two or more mixers and may be arranged for image rej ection (e.g., Hartley image rej ection).
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the send signal path may be arranged for direct downconversion and/or direct upconversion, respectively.
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the send signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 806 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 804 may include a digital baseband interface to communicate with the RF circuitry 806.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 806d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 806d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 806d may be configured to synthesize an output frequency for use by the mixer circuitry 806a of the RF circuitry 806 based on a frequency input and a divider control input.
  • the synthesizer circuitry 806d may be a fractional N/N+1 synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 804 or the application circuitry 802 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 802.
  • Synthesizer circuitry 806d of the RF circuitry 806 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A).
  • the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 806d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 806 may include an IQ/polar converter.
  • FEM circuitry 808 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 810, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 806 for further processing.
  • FEM circuitry 808 may also include a send signal path that may include circuitry configured to amplify signals for transmission provided by the RF circuitry 806 for transmission by one or more of the one or more antennas 810.
  • the FEM circuitry 808 may include a TX/RX switch to switch between send mode and receive mode operation.
  • the FEM circuitry 808 may include a receive signal path and a send signal path.
  • the receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 806).
  • the send signal path of the FEM circuitry 808 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 806), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 810).
  • PA power amplifier
  • the electronic device 800 may include additional elements such as, for example, a display, a camera, one or more sensors, and/or interface circuitry (for example, input/output (I/O) interfaces or buses) (not shown).
  • the electronic device 800 may include network interface circuitry.
  • the network interface circuitry may be one or more computer hardware components that connect electronic device 800 to one or more network elements, such as one or more servers within a core network or one or more other eNBs via a wired connection.
  • the network interface circuitry may include one or more dedicated processors and/or field programmable gate arrays (FPGAs) to communicate using one or more network communications protocols such as X2 application protocol (AP), S I AP, Stream Control Transmission Protocol (SCTP), Ethernet, Point-to-Point (PPP), Fiber Distributed Data Interface (FDDI), and/or any other suitable network communications protocols.
  • FPGAs field programmable gate arrays
  • the electronic device 800 may be configured to perform one or more processes, techniques, and/or methods as described herein, or portions thereof.
  • the electronic device 800 may implement the flows/structures shown and described above with respect to Figures 3-7.
  • Figure 9 is a block diagram illustrating components, according to some embodiments.
  • Figure 9 shows a diagrammatic representation of hardware resources 900 including one or more processors (or processor cores) 910, one or more memory /storage devices 920, and one or more communication resources 930, each of which may be communicatively coupled via a bus 940.
  • processors or processor cores
  • memory /storage devices 920 for example, one or more memory /storage devices
  • communication resources 930 each of which may be communicatively coupled via a bus 940.
  • a hypervisor 902 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 900.
  • NFV network function virtualization
  • the processors 910 may include, for example, a processor, a reduced instruction set computing (“RISC”) processor, a complex instruction set computing (“CISC”) processor, a graphics processing unit (“GPU”), a digital signal processor (“DSP”) such as a baseband processor, an application specific integrated circuit (“ASIC”), a radio-frequency integrated circuit (“RFIC”), another processor, or any suitable combination thereof) may include, for example, a processor 912 and a processor 914.
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • RFIC radio-frequency integrated circuit
  • the memory /storage devices 920 may include main memory, disk storage, or any suitable combination thereof.
  • the memory /storage devices 920 may include, but are not limited to, any type of volatile or non-volatile memory such as dynamic random access memory (“DRAM”), static random-access memory (“SRAM”), erasable programmable read-only memory (“EPROM”), electrically erasable programmable read-only memory
  • DRAM dynamic random access memory
  • SRAM static random-access memory
  • EPROM erasable programmable read-only memory
  • EEPROM Electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources 930 may include interconnection or network
  • the communication resources 930 may include wired communication components (for example, for coupling via a Universal Serial Bus (“USB”)), cellular communication components, near-field communication (“NFC”) components, Bluetooth®
  • USB Universal Serial Bus
  • NFC near-field communication
  • Bluetooth® Low Energy Wi-Fi® components
  • other communication components for example, Bluetooth® Low Energy, Wi-Fi® components, and other communication components.
  • Instructions 950 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 910 to perform any one or more of the methodologies discussed herein.
  • the instructions 950 may cause the processors 910 to perform the operation
  • the instructions 950 may cause the processors 910 to perform the operation flow/algorithmic structure 600 or other operations of an AN described, for example, in the flows of Figures 3-4.
  • the instructions 950 may cause the processors 910 to perform the operation
  • the instructions 950 may reside, completely or partially, within at least one of the processors 910 (for example, within the processor's cache memory), the memory /storage devices 920, or any suitable combination thereof. Furthermore, any portion of the instructions 950 may be transferred to the hardware resources 900 from any combination of the peripheral devices 904 or the databases 906. Accordingly, the memory of processors 910, the memory /storage devices 920, the peripheral devices 904, and the databases 906 are examples of computer-readable and machine-readable media.
  • the resources described in Figure 9 may also be referred to as circuitry.
  • communication resources 930 may also be referred to as communication circuitry 930.
  • Example 1 includes one or more computer-readable media having instructions that, when executed, cause a mobility management entity (“MME") to: process a control plane service request (“CPSR") message with an evolved packet services bearer identity (“EBI”) that identifies an evolved packet services (“EPS”) bearer of a user equipment; detect an overload condition in a network; determine that the EPS bearer is not pinned to a control plane (CP)-only connection; and initiate establishment of an S I -U bearer for the user equipment based on detection of the overload condition and determination that the EPS bearer is not pinned to the CP-only connection.
  • Example 2 includes the one or more computer-readable media of example 1 or some other example herein, wherein the instructions, when executed, further cause the MME to: forward uplink data over a user plane connection with a gateway.
  • Example 3 includes the one or more computer-readable media of example 1 or some other example herein, wherein the instructions, when executed, further cause the MME to: send a backoff timer value within a non-access stratum ("NAS") message to a user equipment (“UE") to prevent the UE from sending further uplink data over a control plane connection.
  • Example 4 includes the one or more computer-readable media of example 3 or some other example herein, wherein the instructions, when executed, further cause the MME to: send the backoff timer value in an SI -access point (“AP”) initial context setup request message.
  • NAS non-access stratum
  • UE user equipment
  • AP SI -access point
  • Example 5 includes the one or more computer-readable media of example 4 or some other example herein, wherein the instructions, when executed, further cause the MME to: send an indication, in the Sl-AP initial context setup request message, for the UE to resend data of the CPSR message over a user plane connection.
  • Example 6 includes the one or more computer-readable media of any one of examples 1-5 or some other example herein, wherein the instructions, when executed, further cause the MME to: transmit, to a serving/packet gateway, a modify bearer request to modify an existing bearer for transmission of uplink data from the user equipment; and receive, from the serving/packet gateway, a modify bearer response.
  • Example 7 includes the one or more computer-readable media of example 6 or some other example herein, wherein the modify bearer request is to modify an existing bearer for transmission of uplink data over an Sl l-U interface and the instructions, when executed, further cause the MME to: send the uplink data over the SI 1-U interface.
  • Example 8 includes the one or more computer-readable media of example 6 or some other example herein, wherein the modify bearer request is to modify an existing bearer for transmission of uplink data over an S 1-U interface and the instructions, when executed, further cause the MME to: send a message to instruct the user equipment to send the uplink data over the Sl-U interface.
  • Example 9 includes the one or more computer-readable media of any one of examples 1-8 or some other example herein, wherein the instructions, when executed, further cause the MME to: compare a volume of traffic that includes control plane evolved packet system ("EPS") optimization data to a predetermined threshold; detect the overload condition; and send an Sl-AP overload start message to an access node based on said detection of the overload condition.
  • EPS control plane evolved packet system
  • Example 10 includes one or more computer-readable media having instructions, that when executed, cause an evolved node B ("eNB") to: receive a first message from a user equipment (“UE"), the first message to include data to be sent by a control plane connection via a mobility management entity (“MME"); determine whether the MME is overloaded; determine, based on the first message, whether the data is to be sent by a bearer that is pinned to a control-plane-only connection; forward the first message to the MME if it is determined that the data is to be sent by a bearer that is pinned to a control- plane only connection; and send a radio resource control (“RRC”) connection reject message to the UE if it is determined that the data is to be sent by a bearer that is not pinned to a control-plane only connection.
  • eNB evolved node B
  • Example 11 includes the one or more computer-readable media of example 10 or some other example herein, wherein the instructions, when executed, further cause the eNB to: determine that the data is to be sent by a bearer that is pinned to the control-plane-only connection; and send the RRC connection reject message with a backoff timer value to the UE to prevent the UE from sending further uplink data over the control plane connection.
  • Example 12 includes the one or more computer-readable media of example 10 or some other example herein, wherein the instructions, when executed, further cause the eNB to: determine that the data is to be sent by a bearer that is not pinned to the control-plane-only connection; and forward the first message in an S 1-AP initial UE message.
  • Example 13 includes the one or more computer-readable media of example 12 or some other example herein, wherein the instructions, when executed, further cause the eNB to: receive an Sl-AP initial context setup request ("ICSR") message that includes an indication that the UE is to resend data over a user plane connection; and send an RRC download message to the UE with the indication.
  • SSR Sl-AP initial context setup request
  • Example 14 includes the one or more computer-readable media of example 13 or some other example herein, wherein the Sl-AP ICSR message and the RRC download message further include a backoff timer value to prevent the UE from sending further uplink data over the control plane connection.
  • Example 15 includes the one or more computer-readable media of example 13 or 14 or some other example herein, wherein the instructions, when executed, further cause the eNB to: receive a second message from the UE including the data to be sent by a user plane connection.
  • Example 16 includes one or more computer-readable media having instructions that, when executed, cause a user equipment (“UE") to: generate and send a first control plane("CP")-data message to send data over a control plane connection; receive a radio resource control (“RRC”) message having a backoff timer value; set a CP backoff timer based on the backoff timer value; and generate and send a second CP-data message upon expiration of the CP backoff timer.
  • UE user equipment
  • RRC radio resource control
  • Example 17 includes the one or more computer-readable media of example 16 or some other example herein, wherein the first CP-data message comprises an RRC message.
  • Example 18 includes the one or more computer-readable media of example 17 or some other example herein, wherein the RRC message is an RRC connection request message or an RRC connection setup complete message.
  • Example 19 includes the one or more computer-readable media of example 16 or some other example herein, wherein the first CP-data message comprises a control plane service request message.
  • Example 20 includes the one or more computer-readable media of any one of examples 16-18 or some other example herein, wherein the first CP-data message includes a CP-data indicator to indicate the first CP-data message is to establish a connection for transmission of data via a control plane or a CP-only-connection indicator to indicate a connection to be established for transmission of data via the control plane is pinned to the control plane.
  • the first CP-data message includes a CP-data indicator to indicate the first CP-data message is to establish a connection for transmission of data via a control plane or a CP-only-connection indicator to indicate a connection to be established for transmission of data via the control plane is pinned to the control plane.
  • Example 21 includes processing circuitry to be implemented within a mobility
  • MME management entity
  • the processing circuitry configured to cause the MME to: process a control plane service request (“CPSR") message with an evolved packet services bearer identity (“EBI”) that identifies an evolved packet services (“EPS”) bearer of a user equipment; detect an overload condition in a network; determine that the EPS bearer is not pinned to a control plane (CP)-only connection; and initiate establishment of an SI -U bearer for the user equipment based on detection of the overload condition and
  • CPSR control plane service request
  • EBI evolved packet services bearer identity
  • Example 22 includes the processing circuitry of example 21 or some other example herein, wherein the instructions, when executed, further cause the MME to: forward uplink data over a user plane connection with a gateway.
  • Example 23 includes the processing circuitry of example 21 or some other example herein, wherein the instructions, when executed, further cause the MME to: send a backoff timer value within a non-access stratum ("NAS") message to a user equipment (“UE") to prevent the UE from sending further uplink data over a control plane connection.
  • Example 24 includes the processing circuitry of example 23 or some other example herein, wherein the processing circuitry is further configured to cause the MME to: send the backoff timer value in an S I -access point (“AP”) initial context setup request message.
  • NAS non-access stratum
  • UE user equipment
  • Example 25 includes the processing circuitry of example 24 or some other example herein, wherein the processing circuitry is further configured to cause the MME to: send an indication, in the S l-AP initial context setup request message, for the UE to resend data of the CPSR message over a user plane connection.
  • Example 26 includes the processing circuitry of any one of examples 21 -25 or some other example herein, wherein the processing circuitry is further configured to cause the MME to: transmit, to a serving/packet gateway, a modify bearer request to modify an
  • Example 27 includes the processing circuitry of example 26 or some other example herein, wherein the modify bearer request is to modify an existing bearer for transmission of uplink data over an S 11 -U interface and the processing circuitry is further configured to cause the MME to: send the uplink data over the S 11 -U interface.
  • Example 28 includes the processing circuitry of example 26 or 27 or some other example herein, wherein the modify bearer request is to modify an existing bearer for transmission of uplink data over an S l -U interface and the processing circuitry is further configured to cause the MME to: send a message to instruct the user equipment to send the uplink data over the S l -U interface.
  • Example 29 includes the processing circuitry of any one of examples 21 -28 or some other example herein, wherein the processing circuitry is further configured to cause the MME to: compare a volume of traffic that includes control plane evolved packet system ("EPS") optimization data to a predetermined threshold; detect the overload condition; and send an S l-AP overload start message to an access node based on said detection of the overload condition.
  • EPS control plane evolved packet system
  • Example 30 includes processing circuitry to be implemented in an evolved node B
  • eNB the processing circuitry configured to cause the eNB to: process a first message from a user equipment (“UE"), the first message to include data to be sent by a control plane connection via a mobility management entity (“MME"); determine whether the MME is overloaded; determine, based on the first message, whether the data is to be sent by a bearer that is pinned to a control-plane-only connection; forward the first message to the MME if it is determined that the data is to be sent by a bearer that is pinned to a control-plane only connection; and send a radio resource control (“RRC”) connection reject message to the UE if it is determined that the data is to be sent by a bearer that is not pinned to a control-plane only connection.
  • RRC radio resource control
  • Example 31 includes the processing circuitry of example 30 or some other example herein, wherein the processing circuitry is further configured to cause the eNB to: determine that the data is to be sent by a bearer that is pinned to the control-plane-only connection; and send the RRC connection rejection message with a backoff timer value to the UE to prevent the UE from sending further uplink data over the control plane connection.
  • Example 32 includes the processing circuitry of example 30 or some other example herein, wherein the processing circuitry is further configured to cause the eNB to: determine that the data is to be sent by a bearer that is not pinned to the control-plane-only connection; and forward the first message in an Sl-AP initial UE message.
  • Example 33 includes the processing circuitry of example 32 or some other example herein, wherein the processing circuitry is further configured to cause the eNB to: receive an Sl- AP initial context setup request ("ICSR") message that includes an indication that the UE is to resend data over a user plane connection; and send an RRC download message to the UE with the indication.
  • SSR Sl- AP initial context setup request
  • Example 34 includes the processing circuitry of example 33 or some other example herein, wherein the Sl-AP ICSR message and the RRC download message further include a backoff timer value to prevent the UE from sending further uplink data over the control plane connection.
  • Example 35 includes the processing circuitry of example 33 or 34 or some other example herein, wherein the processing circuitry is further configured to cause the eNB to: receive a second message from the UE including the data to be sent by a user plane connection.
  • Example 36 includes processing circuitry to be implemented in a user equipment (“UE"), the processing circuitry configured to cause the UE to: generate and send a first control plane("CP")-data message to send data over a control plane connection; receive a radio resource control (“RRC") message having a backoff timer value; set a CP backoff timer based on the backoff timer value; and generate and send a second CP-data message upon expiration of the CP backoff timer.
  • Example 37 includes the processing circuitry of example 36 or some other example herein, wherein the first CP-data message comprises an RRC message.
  • Example 38 includes the processing circuitry of example 37 or some other example herein, wherein the RRC message is an RRC connection request message or an RRC connection setup complete message.
  • Example 39 includes the processing circuitry of any one of examples 36-38 or some other example herein, wherein the first CP-data message comprises a control plane service request message.
  • Example 40 includes the processing circuitry of any one of examples 36-39 or some other example herein, wherein the first CP-data message includes a CP-data indicator to indicate the first CP-data message is to establish a connection for transmission of data via a control plane or a CP-only-connection indicator to indicate a connection to be established for transmission of data via the control plane is pinned to the control plane.
  • the first CP-data message includes a CP-data indicator to indicate the first CP-data message is to establish a connection for transmission of data via a control plane or a CP-only-connection indicator to indicate a connection to be established for transmission of data via the control plane is pinned to the control plane.
  • Example 41 includes a method of operation performed by a mobility management entity (“MME”), the method comprising: processing a control plane service request (“CPSR") message with an evolved packet services bearer identity (“EBI”) that identifies an evolved packet services (“EPS”) bearer of a user equipment; detecting an overload condition in a network; determining that the EPS bearer corresponds to a PDN connection that is not set to control plane (CP)-only; and initiating establishment of an Sl-U bearer for the user equipment based on detection of the overload condition and determination that the EPS bearer does corresponds to the PDN connection that is not set to CP-only.
  • CPSR control plane service request
  • EBI evolved packet services bearer identity
  • Example 42 includes the method of example 41 or some other example herein, wherein the method further comprises: forwarding uplink data over a user plane connection with a gateway.
  • Example 43 includes the method of example 41 or some other example herein, wherein the method further comprises: sending a backoff timer value within a non-access stratum ("NAS") message to a user equipment (“UE”) to prevent the UE from sending further uplink data over a control plane connection.
  • NAS non-access stratum
  • UE user equipment
  • Example 44 includes the method of example 43 or some other example herein, wherein the method further comprises: sending the backoff timer value in an SI -access point ("AP") initial context setup request message.
  • Example 45 includes the method of example 44 or some other example herein, wherein the method further comprises: sending an indication, in the Sl-AP initial context setup request message, for the UE to resend data of the CPSR message over a user plane connection.
  • AP SI -access point
  • Example 46 includes the method of any one of examples 41-45 or some other example herein, wherein the method further comprises: sending, to a serving/packet gateway, a modify bearer request to modify an existing bearer for transmission of uplink data from the user equipment; and receiving, from the serving/packet gateway, a modify bearer response.
  • Example 47 includes the method of example 46 or some other example herein, wherein the modify bearer request is to modify an existing bearer for transmission of uplink data over an SI 1-U interface and the method further comprises: sending the uplink data over the Sl l-U interface.
  • Example 48 includes the method of example 46 or some other example herein, wherein the modify bearer request is to modify an existing bearer for transmission of uplink data over an Sl-U interface and the method further comprises: sending a message to instruct the user equipment to send the uplink data over the Sl-U interface.
  • Example 49 includes the method of any one of examples 41-48 or some other example herein, wherein the method further comprises: comparing a volume of traffic that includes control plane evolved packet system ("EPS") optimization data to a predetermined threshold; detecting the overload condition; and sending an Sl-AP overload start message to an access node based on said detection of the overload condition.
  • EPS control plane evolved packet system
  • Example 50 includes a method to be performed by an evolved node B (“eNB”), the method comprising: receiving a first message from a user equipment (“UE”), the first message to include data to be sent by a control plane connection via a mobility
  • eNB evolved node B
  • UE user equipment
  • MME management entity
  • determining whether the MME is overloaded determining, based on the first message, whether the data is to be sent by a bearer that is pinned to a control-plane-only connection; forwarding the first message to the MME if it is determined that the data is to be sent by a bearer that is pinned to a control-plane only connection; and sending a radio resource control (“RRC”) connection reject message to the UE if it is determined that the data is to be sent by a bearer that is not pinned to a control-plane only connection.
  • RRC radio resource control
  • Example 51 includes the method of example 50 or some other example herein, wherein the method further comprises: determining that the data is to be sent by a bearer that is pinned to the control-plane-only connection; and sending the RRC connection reject
  • Example 52 includes the method of example 50 or some other example herein, wherein the method further comprises: determining that the data is to be sent by a bearer that is not pinned to the control-plane-only connection; and forwarding the first message in an Sl-AP initial UE message.
  • Example 53 includes the method of example 52 or some other example herein, wherein the method further comprises: receiving an Sl-AP initial context setup request ("ICSR") message that includes an indication that the UE is to resend data over a user
  • SSR Sl-AP initial context setup request
  • Example 54 includes the method of example 53 or some other example herein, wherein the S 1-AP ICSR message and the RRC download message further include a backoff timer value to prevent the UE from sending further uplink data over the control
  • Example 55 includes the method of example 53 or 54 or some other example herein, wherein the method further comprises: receiving a second message from the UE including the data to be sent by a user plane connection.
  • Example 56 includes a method to be performed by a user equipment (“UE"), the method comprising: generating and sending a first control plane("CP")-data message to send data over a control plane connection; receiving a radio resource control (“RRC”) message having a backoff timer value; setting a CP backoff timer based on the backoff timer value; and generating and sending a second CP-data message upon expiration of the CP backoff timer.
  • UE user equipment
  • Example 57 includes the method of example 56 or some other example herein, wherein the first CP-data message comprises an RRC message.
  • Example 58 includes the method of example 57 or some other example herein, wherein the RRC message is an RRC connection request message or an RRC connection setup complete message.
  • Example 59 includes the method of example 56 or some other example herein, wherein the first CP-data message comprises a control plane service request message.
  • Example 60 includes the method of any one of examples 56-58 or some other example herein, wherein the first CP-data message includes a CP-data indicator to indicate the first CP-data message is to establish a connection for transmission of data via a control plane or a CP-only-connection indicator to indicate a connection to be established for transmission of data via the control plane is pinned to the control plane.
  • the first CP-data message includes a CP-data indicator to indicate the first CP-data message is to establish a connection for transmission of data via a control plane or a CP-only-connection indicator to indicate a connection to be established for transmission of data via the control plane is pinned to the control plane.
  • Example 61 includes an apparatus comprising: means to perform any one of the methods of examples 41 -60.
  • Example 62 includes a mobility management entity having: processing circuitry to perform any one of the methods of examples 41 -49; and communication circuitry, coupled with the processing circuitry, to send messages to a user equipment (“UE”) or an evolved node B (“eNB”) or to receive messages from the UE or the eNB.
  • UE user equipment
  • eNB evolved node B
  • Example 63 includes an evolved node B (eNB) having: processing circuitry to perform any one of the methods of examples 50-55; and communication circuitry, coupled with the processing circuitry, to send messages to a mobility management entity (“MME”) or a user equipment (“UE”) or to receive messages from the eNB or the UE.
  • MME mobility management entity
  • UE user equipment
  • Example 64 includes a user equipment (“UE") having: processing circuitry to perform any one of the methods of examples 56-60; and communication circuitry, coupled with the processing circuitry, to send messages to an evolved node B (“eNB”) or a mobility management entity (“MME”) or to receive messages from the eNB or the MME.
  • UE user equipment
  • processing circuitry to perform any one of the methods of examples 56-60
  • communication circuitry coupled with the processing circuitry, to send messages to an evolved node B (“eNB”) or a mobility management entity (“MME”) or to receive messages from the eNB or the MME.
  • eNB evolved node B
  • MME mobility management entity
  • Example 65 includes a radio resource control (“RRC") message comprising: a control plane (CP) data field having a first indicator to indicate whether a user equipment is sending data using control plane cellular Internet of things evolved packet system (CIoT EPS) optimization; or a CP-only connection field having a second indicator to indicate whether the user equipment is sending data using control plane CIoT EPS optimization over an evolved packet system bearer that is pinned to control plane CIoT EPS optimization.
  • RRC radio resource control
  • Example 66 includes the RRC message of example 65, wherein the RRC message is an RRC connection request message or an RRC connection setup complete message.
  • Example 67 includes processing circuitry to be implemented within a mobility
  • MME management entity
  • the processing circuitry configured to cause the MME to: process a control plane service request (“CPSR") message with an evolved packet services bearer identity (“EBI”) that identifies an evolved packet services (“EPS”) bearer of a user equipment; detect an overload condition in a network; and send a backoff timer value within a non-access stratum (“NAS”) message to a user equipment (“UE”) to prevent the UE from sending further uplink data over a control plane connection.
  • CPSR control plane service request
  • EBI evolved packet services bearer identity
  • EPS evolved packet services bearer of a user equipment
  • NAS non-access stratum
  • Example 68 may include the processing circuitry of example 67 or some other example, wherein the instructions, when executed, further cause the MME to: forward uplink data over a user plane connection with a gateway.
  • Example 69 may include the processing circuitry of example 67 or some other example, wherein the instructions, when executed, further cause the MME to: determine that the EPS bearer corresponds to a PDN connection that is not set to control plane (CP)- only; and initiate establishment of an Sl-U bearer for the user equipment based on detection of the overload condition and determination that the EPS bearer does corresponds to the PDN connection that is not set to CP-only.
  • CP control plane
  • Example 70 may include the processing circuitry of example 67, wherein the processing circuitry is further configured to cause the MME to: send the backoff timer value in an Sl- access point ("AP") initial context setup request message.
  • AP Sl- access point
  • Example 71 may include the processing circuitry of example 70, wherein the processing circuitry is further configured to cause the MME to: send an indication, in the Sl-AP initial context setup request message, for the UE to resend data of the CPSR message over a user plane connection.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Technology Law (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente invention décrivent des procédés et des appareils destinés à des mécanismes permettant d'empêcher une surcharge de réseau central pour des transmissions de données de plan de commande.
PCT/US2017/035970 2016-09-30 2017-06-05 Commande de surcharge de réseau central pour système de paquet évolué à plan de command WO2018063453A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201780053482.9A CN109923879B (zh) 2016-09-30 2017-06-05 控制平面演进分组系统的核心网过载控制

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662402515P 2016-09-30 2016-09-30
US62/402,515 2016-09-30

Publications (1)

Publication Number Publication Date
WO2018063453A1 true WO2018063453A1 (fr) 2018-04-05

Family

ID=59351048

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/035970 WO2018063453A1 (fr) 2016-09-30 2017-06-05 Commande de surcharge de réseau central pour système de paquet évolué à plan de command

Country Status (2)

Country Link
CN (1) CN109923879B (fr)
WO (1) WO2018063453A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020102637A1 (fr) * 2018-11-16 2020-05-22 Convida Wireless, Llc Sélection de plan de commande et de plan utilisateur pour petites données
WO2020223909A1 (fr) * 2019-05-07 2020-11-12 Oppo广东移动通信有限公司 Procédé de gestion de contexte, dispositif et support d'informations
US20210168646A1 (en) * 2018-08-09 2021-06-03 Zte Corporation Methods, apparatus and systems for integrated access and backhaul bearer management
US20230026925A1 (en) * 2019-12-18 2023-01-26 Zte Corporation Information transmission method and apparatus, information processing method and apparatus, terminal, network element and storage medium

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021163853A1 (fr) * 2020-02-17 2021-08-26 Oppo广东移动通信有限公司 Procédé et appareil de changement de mode de transmission de données, et dispositif et support de stockage

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140016614A1 (en) * 2011-04-05 2014-01-16 Panasonic Corporation Short message transmission and handover procedures
US20140341041A1 (en) * 2011-12-13 2014-11-20 Panasonic Corporation Device triggering and apn-based congestion control
US20150296321A1 (en) * 2012-11-02 2015-10-15 Lg Electronics Inc. Method for transmitting data of mtc device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102111847B (zh) * 2011-01-10 2013-07-24 大唐移动通信设备有限公司 一种接入控制的方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140016614A1 (en) * 2011-04-05 2014-01-16 Panasonic Corporation Short message transmission and handover procedures
US20140341041A1 (en) * 2011-12-13 2014-11-20 Panasonic Corporation Device triggering and apn-based congestion control
US20150296321A1 (en) * 2012-11-02 2015-10-15 Lg Electronics Inc. Method for transmitting data of mtc device

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210168646A1 (en) * 2018-08-09 2021-06-03 Zte Corporation Methods, apparatus and systems for integrated access and backhaul bearer management
US11950124B2 (en) * 2018-08-09 2024-04-02 Zte Corporation Methods, apparatus and systems for integrated access and backhaul bearer management
WO2020102637A1 (fr) * 2018-11-16 2020-05-22 Convida Wireless, Llc Sélection de plan de commande et de plan utilisateur pour petites données
WO2020223909A1 (fr) * 2019-05-07 2020-11-12 Oppo广东移动通信有限公司 Procédé de gestion de contexte, dispositif et support d'informations
CN112425206A (zh) * 2019-05-07 2021-02-26 Oppo广东移动通信有限公司 一种上下文管理方法、设备及存储介质
CN112425206B (zh) * 2019-05-07 2023-10-24 Oppo广东移动通信有限公司 一种上下文管理方法、设备及存储介质
US20230026925A1 (en) * 2019-12-18 2023-01-26 Zte Corporation Information transmission method and apparatus, information processing method and apparatus, terminal, network element and storage medium
US11888649B2 (en) * 2019-12-18 2024-01-30 Zte Corporation Information transmission method and apparatus, information processing method and apparatus, terminal, network element and storage medium

Also Published As

Publication number Publication date
CN109923879A (zh) 2019-06-21
CN109923879B (zh) 2022-03-22

Similar Documents

Publication Publication Date Title
US10939501B2 (en) Apparatus, system and method to implement reserved resources for forward compatibility in new radio (NR) networks
US11871291B2 (en) Data forwarding tunnel establishment between two user plane functions in fifth generation
US11291030B2 (en) Sidelink control information for vehicle-to-vehicle communications
EP3451553B1 (fr) Mécanismes pour surveiller un canal de commande physique de liaison descendante comportant un espace de recherche commun et un espace de recherche spécifique d'un équipement utilisateur dans un système à formation de faisceau
US11134538B2 (en) Apparatuses for end-to-end coordination of voice over cellular data network communications
US11272391B2 (en) Concatenation of service data units above a packet data convergence protocol layer
US20190387578A1 (en) Handling multiple sr configurations and corresponding ul grants
US11277191B2 (en) Radio link monitoring, beam recovery and radio link failure handling
US20200110627A1 (en) Centralized unit and distributed unit connection in a virtualized radio access network
US10979958B2 (en) Systems, methods, and apparatuses for providing and obtaining scheduling information for SIB1-BR during handover
CN109923879B (zh) 控制平面演进分组系统的核心网过载控制
US10631256B2 (en) Power headroom of grantless uplink
CN109691222B (zh) 用于配置轻型连接的装置
US11502805B2 (en) Resource mapping schemes for channel state information reporting on new radio physical uplink control channel
CN112544099A (zh) 用于集成接入和回程网络中的上行链路流量的流控制
US11838839B2 (en) V2X policy and parameters provisioning to user equipment by a policy and control function
US11109355B2 (en) Interruption and delay for V2X sidelink carrier aggregation
WO2018106429A1 (fr) Mécanisme de transfert intercellulaire amélioré
WO2019032532A1 (fr) Nouvelle gestion d'enregistrement radio
US11419001B2 (en) Critical data handling for video and other applications
US20190044810A1 (en) Channel whitelist and flexible frame design for enhanced machine-type communications systems in unlicensed spectrum
WO2017197359A1 (fr) Suivi d'un équipement d'utilisateur au niveau d'un réseau d'accès radio
EP3646566B1 (fr) Dispositifs de déchargement partiel des tâches de traitements de protocole

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17740140

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17740140

Country of ref document: EP

Kind code of ref document: A1