CN110050475B - Coverage enhancement restrictions for CIoT devices - Google Patents

Abstract

A Cellular Internet of Things (CIoT) capable User Equipment (UE) apparatus is configured for Evolved Packet System (EPS) communications in a Public Land Mobile Network (PLMN). The apparatus includes processing circuitry configured to encode an attach request message for transmission to a mobility management entity (MME) in the EPS, the attach request message including a message indicating whether the UE supports restrictions on the use of enhanced coverage UE Network Capability Information Element (IE). The processing circuitry may decode an Attach Accept message confirming attachment to the MME, the Attach Accept message including an EPS Network Feature Support IE indicating whether use of enhanced coverage is restricted to the UE. The processing circuitry may refrain from using enhanced coverage in the PLMN when the UE supports restrictions on the use of enhanced coverage and the EPS Network Feature Support IE indicates that enhanced coverage is restricted for the UE.

Description

Coverage Enhancement Restrictions for CIoT Devices

priority claim

This application claims the benefit of priority to US Provisional Patent Application Serial No. 62/444,200, filed January 9, 2017, entitled "RESTRICTIONS FOR COVERAGEENHANCEMENTS FOR CIOT DEVICES," which is hereby incorporated by reference in its entirety.

technical field

Aspects relate to wireless communications. Some aspects relate to wireless networks, including 3GPP (3rd Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, 3GPP LTE-A (LTE Plus) networks, and 3rd generation networks including new radio (NR) networks. Fifth-generation (5G) networks. Other aspects are directed to coverage enhancement (CE) limitations for Cellular Internet-of-Things (CIoT) devices.

Background technique

Mobile communications have evolved substantially from early voice systems to today's highly sophisticated integrated communications platforms. The use of 3GPP LTE systems has increased with the proliferation of different types of devices communicating with various network devices. The penetration of mobile devices (User Equipment or UE) in contemporary society continues to drive the demand for a wide variety of networked devices in a variety of different environments.

LTE and LTE Plus are standards for wireless communication of high-speed data for user equipment (UE) such as mobile phones. In LTE Plus and various wireless systems, carrier aggregation is a technique according to which multiple carrier signals operating on different frequencies can be used to carry communications for a single UE, thereby increasing the bandwidth available to a single device. In some aspects, carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.

The use of networked UEs using 3GPP LTE systems has increased in the areas of home and work life. Fifth generation (5G) wireless systems are on the horizon and are expected to enable higher speeds, connectivity and availability. Next-generation 5G networks are expected to increase throughput, coverage and robustness. As current cellular network frequencies are saturated, high frequencies such as millimeter wave (mmWave) frequencies may be beneficial due to their high bandwidth.

Explosive wireless traffic growth has led to the need for increased rates. With mature physical layer technology, further improvements in spectral efficiency may be trivial. On the other hand, the lack of licensed spectrum in the low frequency band leads to insufficient data rate boosting. Thus, there is interest in the operation of LTE systems in unlicensed spectrum. As a result, an important enhancement of LTE in 3GPP Release 13 is to enable its operation in unlicensed spectrum via Licensed-Assisted Access (LAA), by taking advantage of the flexible carriers introduced by the LTE Plus system The carrier aggregation (CA) framework extends the system bandwidth. Release 13 LAA systems focus on designs for downlink operation via CA on unlicensed spectrum, while Release 14 enhanced LAA (eLAA) systems focus on designs for uplink operation via CA on unlicensed spectrum design.

Potential LTE operations in unlicensed spectrum include (and are not limited to) LTE operation in unlicensed spectrum via dual connectivity (DC), or DC-based LAA, and standalone LTE systems in unlicensed spectrum, according to This system, LTE-based technology operating only in unlicensed spectrum without requiring an "anchor" in licensed spectrum, is called MulteFire. MulteFire combines the performance benefits of LTE technology with the simplicity of WiFi-like deployment. Further enhanced operation of LTE systems in licensed spectrum as well as unlicensed spectrum is expected in future releases and 5G systems.

Machine-to-Machine (M2M) communications represent an important growth opportunity for the 3GPP ecosystem. With the proliferation of wireless networks, there is an accelerated push towards connected smart physical objects such as wireless sensors, smart meters, specialized microprocessors, etc. that span different ecosystems with different business models.

Description of drawings

In the drawings, which are not necessarily to scale, like reference numerals may describe like components in the different views. Similar numbers with different letter suffixes may represent different instances of similar components. The drawings generally illustrate, by way of example and not limitation, various aspects discussed in this document.

1A illustrates the architecture of a network according to some aspects.

1B is a simplified diagram of an overall next generation (NG) system architecture in accordance with some aspects.

1C illustrates the functional split between NG-RAN and 5G core (5GC), according to some aspects.

1D and 1E illustrate a non-roaming 5G system architecture in accordance with some aspects.

1F illustrates an example CIoT network architecture in accordance with some aspects.

FIG. 2 illustrates example components of device 200 according to some aspects.

3 illustrates an example interface for a baseband circuit in accordance with some aspects.

4 is an illustration of a control plane protocol stack in accordance with some aspects.

5 is an illustration of a user plane protocol stack in accordance with some aspects.

6 is a diagram illustrating the ability to read instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and perform any one or more of the methods discussed herein, according to some example aspects Block diagram of components.

7 illustrates an example communication sequence in a CIoT environment, according to some aspects.

8 illustrates an example UE network capability information element in accordance with some aspects.

9 illustrates an example EPS network feature support information element in accordance with some aspects.

10 illustrates an example MS network capability information element in accordance with some aspects.

11 illustrates an example additional network feature support information element in accordance with some aspects.

12 generally illustrates a flow diagram of an example method of operating a UE that supports restrictions on use of enhanced coverage, in accordance with some aspects.

13 illustrates a device such as an Evolved Node B (eNB), Next Generation Node B (gNB), Access Point (AP), Radio Station (STA), Mobile Station (MS), or User Equipment (UE), in accordance with some aspects A block diagram of a class of communication devices.

Detailed ways

The following description and drawings illustrate various aspects sufficiently to enable those skilled in the art to practice them. Other aspects may incorporate structural, logical, electrical, process, and other changes. Portions and features of some aspects may be included in or substituted for those of other aspects. The recited aspects of the claims cover all available equivalents of such claims.

无线千兆比特联盟(Wireless Gigabit Alliance，WiGig)标准，一般mmWave标准(工作在10-300GHz及以上的无线系统，例如WiGig，IEEE 802.11ad，IEEE 802.11ay等等)，在300GHz以上和THz频带以上工作的技术(基于3GPP/LTE的或者IEEE 802.11p和其他)，车辆到车辆(Vehicle-to-Vehicle，V2V)和车辆到X(Vehicle-to-X，V2X)以及车辆到基础设施(Vehicle-to-Infrastructure，V2I)和基础设施到车辆(Infrastructure-to-Vehicle，I2V)通信技术，3GPP蜂窝V2X，DSRC(专用短程通信)通信系统，例如智能传输系统及其他，等等。Any radio link described herein may operate in accordance with any one or more of the following exemplary radio communication technologies and/or standards, including but not limited to: Global System for Mobile Communications (Global System) for Mobile Communications, GSM) radio communication technology, General Packet Radio Service (General Packet Radio Service, GPRS) radio communication technology, Enhanced Data Rates for GSM Evolution (Enhanced Data Rates for GSM Evolution, EDGE) radio communication technology and/or Third Generation Partnership Project (3GPP) radio communication technologies, such as Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (Long Term Evolution, LTE), 3GPP Long Term Evolution Advanced (LTE Upgrade), Code Division Multiple Access 2000 (Code division multiple access 2000, CDMA2000), Cellular Digital Packet Data (CDPD) , Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit-Switched Data (HSCSD), Universal Mobile Telecommunications System (third generation) (Universal Mobile Telecommunications System (Third Generation), UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (Wideband Code Division Multiple Access (Universal Mobile Telecommunications System), W-CDMA (UMTS)), high-speed packet access (High Speed Packet Access, HSPA), high-speed downlink packet access (High-Speed Downlink Packet Access, HSDPA), high-speed uplink Link Packet Access (High-Speed Uplink Packet Access, HSUPA), High Speed Packet Access Plus (HSPA+), Universal Mobile Telecommunications System-Time-Division Duplex (UMTS) -TDD), Time Division-Code Division Multiple Access (TD-CDMA), Time Division-Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3GPP Rel.8 (Pre-4G)), 3GPP Rel.9 (3rd Generation Partnership Project Release 9), 3GPP Rel.10 (3rd Generation Partner Program Release 10), 3GPP Rel.11 (3rd Generation Partnership Project Release 11), 3GPP Rel.12 (3rd Generation Partnership Project Release 12), 3GPP Rel.13 (3rd Generation Partnership Project Release 12) Project Release 13), 3GPP Rel.14 (3rd Generation Partnership Project Release 14), 3GPP Rel.15 (3rd Generation Partnership Project Release 15), 3GPP Rel.16 (3rd Generation Partnership Project Release 15) 16), 3GPP Rel.17 (3rd Generation Partnership Project Release 17), 3GPP Rel.18 (3rd Generation Partnership Project Release 18), 3GPP 5G, 3GPP LTE Extra, LTE-AdvancedPro, LTE License Assist Access (LTE Licensed-Assisted Access, LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Upgrade (4th Generation) (LTE Plus (4G)), cdmaOne (2G), Code Division Multiple Access 2000 (3rd Generation) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution-Data Optimized or Evolution-Data Only, EV-DO), Advanced Mobile Phone System (1st Generation) (Advanced Mobile Phone System) (1st Generation), AMPS (1G)), Total Access Communication System/Extended Total Access Communication System (Total Access Communication System/Extended Total Access Communication System, TACS/ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (Advanced Mobile Telephone System) MobileTelephone System, AMTS), OLT (Norwegian, Offentlig Landmobil Telefoni, Public Land Mobile Telephone), MTD (Swedish abbreviation for Mobiltelefonisystem D, or Mobile Telephone System D), Public Automated Land Mobile (Public Automated Land Mobile, Autotel/ PALM), ARP (Finnish, Autoradiopuhelin, "automobile radiotelephone"), NMT (Nordic Mobile Telephony, Nordic mobile telephony), NTT (Nippon Telegraph and Telephone) high-capacity version (Hicap), Cellular Digital Packet Data (Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handy Phone System ( Personal Handy-phone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA) (also known as 3GPP Universal Access Network, or GAN) standard), Zigbee,

Wireless Gigabit Alliance (WiGig) standard, general mmWave standard (wireless systems operating at 10-300GHz and above, such as WiGig, IEEE 802.11ad, IEEE 802.11ay, etc.), above 300GHz and above the THz frequency band Working technologies (3GPP/LTE based or IEEE 802.11p and others), Vehicle-to-Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to-Infrastructure (Vehicle- to-Infrastructure, V2I) and Infrastructure-to-Vehicle (I2V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short-Range Communication) communication systems such as intelligent transmission systems and others, etc.

Aspects described herein may be used in the context of any spectrum management scheme, including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (eg, 2.3-2.4GHz, 3.4-3.6GHz, 3.6-3.8GHz, and more frequencies) Licensed Shared Access (LSA) and Spectrum Access System (SAS) in 3.55-3.7GHz and more frequencies. Applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum (including 450–470MHz, 790–960MHz, 1710–2025MHz, 2110–2200MHz, 2300–2400MHz, 2500–2690MHz, 698-790MHz, 610–790MHz, 3400–3600MHz etc.), Advanced IMT Spectrum, IMT-2020 Spectrum (expected to include, for example, 3600-3800MHz, 3.5GHz bands, 700MHz bands, bands in the 24.25-86GHz range), available under the FCC's "Spectrum Frontiers" 5G initiative Spectrum (including 27.5–28.35GHz, 29.1–29.25GHz, 31–31.3GHz, 37–38.6GHz, 38.6–40GHz, 42–42.5GHz, 57–64GHz, 71–76GHz, 81–86GHz, and 92–94GHz, etc.) , 5.9GHz (usually 5.85-5.925GHz) and 63-64GHz ITS (Intelligent Transmission System) frequency bands, the frequency bands currently allocated to WiGig, such as WiGig Band 1 (57.24-59.40GHz), WiGig Band 2 (59.40-61.56GHz) ), WiGig Band 3 (61.56-63.72GHz) and WiGig Band 4 (63.72-65.88GHz), 70.2GHz–71GHz band, any frequency band between 65.88GHz and 71GHz, frequency bands currently allocated for automotive radar applications (e.g. 76- 81GHz), and future bands including 94-300GHz and above. Furthermore, the scheme can also be used on a secondary basis in frequency bands such as TV white space bands (typically below 790 MHz), where in particular the 400 MHz and 700 MHz frequency bands can be used. In addition to cellular applications, vertical market specific applications can be addressed, such as PMSE (Program Making and Special Events), medical, health, surgery, automotive, low latency, drones, and more.

The aspects described herein can also be applied to different single-carrier or OFDM forms (CP-OFDM, SC-FDMA, SC-OFDM, filter-bank based multi-carrier) by allocating OFDM carrier data bit vectors to corresponding symbol resources (filter bank-based multicarrier, FBMC), OFDMA, etc.) and especially 3GPP NR (New Radio).

1A illustrates the architecture of a network according to some aspects. Network 140A is shown to include user equipment (UE) 101 and UE 102 . UEs 101 and 102 are shown as smartphones (eg, handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs) PDA), pagers, laptops, desktops, wireless cell phones, drones, or any other computing device that includes a wired and/or wireless communication interface.

In some embodiments, any of UEs 101 and 102 may include an Internet of Things (IoT) UE that may include a network access layer designed for low-power IoT applications utilizing short-term UE connections . IoT UEs can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) to provide proximity-based connectivity via public land mobile network (PLMN) Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor network or IoT network to exchange data with MTC servers or devices. M2M or MTC data exchanges can be machine-initiated data exchanges. The IoT network description utilizes short-lived connections to interconnect IoT UEs, which may include uniquely identifiable embedded computing devices (within an Internet infrastructure). IoT UEs may execute background applications (eg, keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

UEs 101 and 102 may be configured to connect (eg, communicatively coupled) to a radio access network (RAN) 110, which may be, for example, an evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio connection. Access Network (E-UTRAN), Next Generation RAN (NextGenRAN, NG RAN), or some other type of RAN. UEs 101 and 102 utilize connections 103 and 104, respectively, each of which includes a physical communication interface or layer (discussed in more detail below); in this example, connections 103 and 104 are shown as air interfaces to enable communication coupling, and Compliant with cellular communication protocols such as Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push to Talk (PTT) protocol, Cellular PTT (POC) protocol, Universal Mobile Telecommunications System (UMTS) ) protocol, 3GPP Long Term Evolution (LTE) protocol, Fifth Generation (5G) protocol, New Radio (NR) protocol, etc.

In some aspects, RAN 110 may comprise an NG RAN or an NG core RAN. The NG RAN 110 may include various functions such as access and mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control Function (policy control function, PCF), unified data management (unified data management, UDM) function and network function (network function, NF) warehouse function (NF repository function, NRF). AMF can be used to manage access control and mobility, and can also include network slice selection functionality. SMF can be configured to set up and manage various sessions according to network policies. UPFs can be deployed in one or more configurations depending on the type of service desired. PCF can be configured to provide a policy framework with network slicing, mobility management and roaming (similar to PCRF in 4G communication systems). UDM may be configured to store subscriber profiles and data (similar to HSS in 4G communication systems). Various aspects of the NGRAN and the NG core are discussed herein with reference to Figures IB, 1C, ID, and IE.

In an aspect, UEs 101 and 102 may also exchange communication data directly via ProSe interface 105 . ProSe interface 105 may alternatively be referred to as a side interface including one or more logical channels, including but not limited to Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH) , Physical Sidelink Discovery Channel (PSDCH) and Physical Sidelink Broadcast Channel (PSBCH).

路由器。在此示例中，AP 106被示为连接到互联网，而不连接到无线系统的核心网络(下文更详述描述)。The UE 102 is shown configured to access an access point (AP) 106 via a connection 107 . Connection 107 may comprise a logical wireless connection, such as a connection conforming to any IEEE 802.11 protocol, according to which AP 106 may comprise Wi-Fi

router. In this example, AP 106 is shown connected to the Internet and not to the core network of the wireless system (described in more detail below).

RAN 110 may include one or more access nodes that enable connections 103 and 104 . These access nodes (ANs) may be referred to as base stations (BSs), NodeBs, Evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, etc., and may include providing a certain geographic area A covered ground station (eg, a ground access point) or satellite station within a (eg, a cell). In some aspects, communication nodes 111 and 112 may be transmission/reception points (TRPs). In the case where communication nodes 111 and 112 are NodeBs (eg, eNBs or gNBs), one or more TRPs may operate within the NodeB's communication cell. RAN 110 may include one or more RAN nodes for providing macro cells, such as macro RAN node 111, and for providing femto cells or pico cells (eg, having a smaller coverage area, smaller one or more RAN nodes, such as low power (LP) RAN nodes 112, of user capacity or higher bandwidth cells).

Either of the RAN nodes 111 and 112 may terminate the air interface protocol and may be the first point of contact for the UEs 101 and 102 . In some aspects, any of RAN nodes 111 and 112 may perform various logical functions for 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. In one example, any of nodes 111 and/or 112 may be a new generation Node B (gNB), an evolved Node B (eNB), or another type of RAN node.

According to some aspects, UEs 101 and 102 may be configured to communicate signals with each other or with RAN nodes 111 and 112 using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals over a multi-carrier communication channel according to various communication techniques communication using any of the communication technologies such as, but not limited to, Orthogonal Frequency-Division Multiple Access (OFDMA) communication technology (eg, for downlink communication) or single-carrier frequency division Multiple Access (Single Carrier Frequency Division Multiple Access, SC-FDMA) communication technology (eg, for uplink and ProSe or sideline communications), although such aspects are not required. An OFDM signal may include multiple orthogonal sub-carriers.

In some aspects, a grid of downlink resources may be used for downlink transmissions from any of RAN nodes 111 and 112 to UEs 101 and 102, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is the physical resource in the downlink in each time slot. This time-frequency plane representation can be used in OFDM systems, which makes it suitable for radio resource allocation. Each column and each row of the resource grid may correspond to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain may correspond to one slot in the radio frame. The smallest time-frequency unit in a resource grid can be represented as a resource element. Each resource grid may include several resource blocks, which describe the mapping of specific physical channels to resource elements. Each resource block may include a set of resource elements; in the frequency domain, this may in some aspects represent the minimum number of resources currently allocable. There may be several different physical downlink channels carried using such resource blocks.

A physical downlink shared channel (PDSCH) may carry user data and higher layer signaling to UEs 101 and 102 . The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocation related to the PDSCH channel, among others. It may also inform UEs 101 and 102 about transport format, resource allocation and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assignment of control and shared channel resource blocks to UEs 102 within a cell) may be at either of RAN nodes 101 and 102 based on channel quality information fed back from either of UEs 111 and 112 implement. Downlink resource assignment information may be sent on the PDCCH for (eg, assigned to) each of UEs 101 and 102 .

The PDCCH may use a control channel element (CCE) to carry control information. Before being mapped to resource elements, PDCCH complex-valued symbols may first be organized into quads, which may then be transposed using a subblock 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 called resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped for each REG. Depending on the size of downlink control information (DCI) and channel conditions, the PDCCH may be transmitted using one or more CCEs. There may be four or more different PDCCH formats defined in LTE, with different numbers of CCEs (eg, aggregation level L=1, 2, 4 or 8).

Some aspects may use concepts of resource allocation for control channel information that are extensions of the concepts described above. For example, some aspects may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more enhanced control channel elements (ECCEs). Similar to the above, each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs). ECCE may have other numbers of EREGs according to some arrangements.

RAN 110 is shown communicatively coupled to core network (CN) 120 via S1 interface 113 . In some aspects, CN 120 may be an evolved packet core (EPC) network, a NextGenPacket Core (NPC) network, or some other type of CN (eg, as shown with reference to FIGS. 1B-1E ). ). In this aspect, the S1 interface 113 is split into two parts: the S1-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122; and the S1 mobility A mobility management entity (MME) interface 115 is the signaling interface between the RAN nodes 111 and 112 and the MME 121 .

In this aspect, CN 120 includes MME 121 , S-GW 122 , Packet Data Network (PDN) Gateway (P-GW) 123 and Home Subscriber Server (HSS) 124 . The MME 121 may be functionally similar to the control plane of the legacy Serving GPRS Support Node (SGSN). The MME 121 may manage mobility aspects of access, such as gateway selection and tracking area list management. HSS 124 may include a database for network users, including subscription-related information, to support the processing of communication sessions by network entities. The CN 120 may include one or several HSSs 124, depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, and so on. For example, HSS 124 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location compliance, and the like.

S-GW 122 may terminate S1 interface 110 towards RAN 113 and route data packets between RAN 110 and CN 120. Furthermore, the S-GW 122 may be the local mobility anchor point for inter-RAN node handover and may also provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include lawful interception, charging, and some policy enforcement.

The P-GW 123 may terminate the SGi interface towards the PDN. P-GW 123 may route data packets via Internet Protocol (IP) interface 125 between EPC network 123 and an external network, eg, including an application server 130 (alternatively referred to as an application function (AF)) network. In general, application server 130 may be an element that provides applications that use IP bearer resources with the core network (eg, UMTS Packet Service (PS) domain, LTE PS data service, etc.). In this aspect, P-GW 123 is shown as being communicatively coupled to application server 130 via IP communication interface 125 . The application server 130 may also be configured to support one or more communication services (eg, Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social network services, etc.).

P-GW 123 may also be a node for policy enforcement and charging data collection. Policy and Charging Enforcement Function (PCEF) 126 is the policy and charging control element of CN 120 . In a non-roaming scenario, in some aspects, at the Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session There can be a single PCRF in the . In a roaming scenario with local grooming of traffic, there can be two PCRFs associated with the UE's IP-CAN session: the Home PCRF (H-PCRF) within the HPLMN and the Visited Public Land Mobile Network (Visited Public Land Mobile) Network, VPLMN) within the Visited PCRF (Visited PCRF, V-PCRF). PCRF 126 may be communicatively coupled to application server 130 via P-GW 123 . The application server 130 may signal the PCRF 126 to indicate the new service flow and select the appropriate Quality of Service (QoS) and charging parameters. PCRF 126 may deploy this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which begins The QoS and charges specified by the application server 130 are specified.

In an example, either node 111 or 112 may be configured to communicate (eg, dynamically communicate) antenna panel selection and receive (Rx) beam selection to UE 101/102, the antenna panel selection and receive beam selection Can be used by the UE for data reception on the Physical Downlink Shared Channel (PDSCH) as well as for channel state information reference signal (CSI-RS) measurements and channel state information (CSI) calculations.

In an example, either node 111 or 112 may be configured to communicate (eg, dynamically communicate) antenna panel selection and transmit (Tx) beam selection to UE 101/102, the antenna panel selection and transmit beam selection May be used by the UE for data transmission on the Physical Uplink Shared Channel (PUSCH) and for sounding reference signal (SRS) transmission.

In some aspects, LTE-based communications may use a fixed transmission time interval (TTI) length of 1 ms with 12-14 symbols, or may also use smaller TTIs (eg, in NR-based communications) ). The transmission of requests, grants or data may be accomplished using one or more subframes with TTI. Here, the TTI length can affect both the time to transmit over the air and the processing time at the transmitter and receiver.

1B is a simplified diagram of a Next Generation (NG) system architecture in accordance with some aspects. Referring to FIG. 1B , NG system architecture 140B includes NG-RAN 110 and 5G network core (5GC) 120 . NG-RAN 110 may include multiple nodes, such as gNB 128 and ng-eNB 130. gNB 128 and ng-eNB 130 may be communicatively coupled to UE 102 via, for example, an N1 interface.

The 5GC 120 includes an Access and Mobility Management Function (AMF) 132 and/or a User Plane Function (UPF) 134 . AMF 132 and UPF 134 may be communicatively coupled to gNB 128 and ng-eNB 130 via an NG interface. More specifically, in some aspects, gNB 128 and ng-eNB 130 may connect to AMF 132 through an NG-C interface and to UPF 134 through an NG-U interface. gNB 128 and ng-eNB 130 may be coupled to each other via an Xn interface.

In some aspects, gNB 128 may include a node that provides new radio (NR) user plane and control plane protocol termination towards the UE, and is connected to 5GC 120 via an NG interface. In some aspects, the ng-eNB 130 may include a node that provides Evolved Universal Terrestrial Radio Access (E-UTRA) user plane and control plane protocol termination towards the UE, and is connected to the 5GC 120 via the NG interface.

In some aspects, each of gNB 128 and ng-eNB 130 may be implemented as a base station, mobile edge server, small cell, home eNB, or the like.

1C illustrates the functional split between NG-RAN and 5G core (5GC), according to some aspects. Referring to Figure 1C, a more detailed diagram of the functions that may be performed by gNB 128 and ng-eNB 130 within NG-RAN 110 and AMF 132, UPF 134, and SMF 136 within 5GC 120 is illustrated. In some aspects, 5GC 120 may provide one or more devices with access to Internet 138 via NG-RAN 110 .

In some aspects, gNB 128 and ng-eNB 130 may be configured to host functions for radio resource management (eg, inter-cell radio resource management 129A, radio bearer control 129B, radio admission control 129D, connection mobility control 129C, dynamic allocation of resources to UE in both uplink and downlink (scheduling) 129F); IP header compression, encryption and integrity protection of data; Selection of AMF at UE attach when route to AMF cannot be determined; routing user plane data towards UPF(s); routing control plane information towards AMF; connection setup and release; ) scheduling and transmission of paging messages; scheduling and transmission of system broadcast information (derived from AMF or operation and maintenance); measurement and measurement reporting configuration 129E for mobility and scheduling; transmission level in uplink Packet marking; session management; support for network slicing; QoS flow management and mapping to data radio bearers; UE support in RRC_INACTIVE state; distribution functions for non-access stratus (NAS) messages ; radio access network sharing; dual connectivity; and tight interworking between NR and E-UTRA, etc.

In some aspects, AMF 132 may be configured to host functions such as: NAS signaling termination; NAS signaling security 133A; access stratus (AS) security control; for 3GPP access networks Inter-core network (CN) node signaling for mobility between; idle mode mobility processing 133B, including mobile device (eg, UE) reachability (eg, control and execution of page retransmissions); registration Area management; support for intra- and inter-system mobility; access authentication; access authorization, including verification of roaming rights; mobility management controls (subscriptions and policies); support for network slicing; and/or SMF selection, and other features.

UPF 134 may be configured to host functions such as: mobility anchor 135A (eg, anchor point for intra/inter-RAT mobility); packet data unit (PDU) processing 135B (eg, External PDU session interconnection point to data network); packet routing and forwarding; packet inspection and user plane portion of policy rule enforcement; traffic usage reporting; uplink classifiers to support routing traffic flows to data networks; branching Points to support multi-homed PDU sessions; for user plane QoS processing such as packet filtering, gating, UL/DL rate enforcement; uplink traffic validation (SDF to QoS flow mapping); and/or downlink Packet buffering and downlink data notification triggering, among other functions.

Session Management Function (SMF) 136 may be configured to host functions such as: Session Management; UE IP Address Assignment and Management 137A; Selection and Control of UP Functions; PDU Session Control 137B, including configuration at the UPF Traffic manipulation to route traffic to the appropriate destination; control portion of policy enforcement and QoS; and/or downlink data notification, among other functions.

1D and 1E illustrate a non-roaming 5G system architecture in accordance with some aspects. Referring to FIG. 1D, a 5G system architecture 140D, represented by reference points, is illustrated. More specifically, UE 102 may communicate with RAN 110 and one or more other 5GC network entities. The 5GC of the system architecture 140D includes a number of network functions (NF), such as an access and mobility management function (AMF) 132, a session management function (SMF) 136, a policy control function (PCF) 148, application function (AF) 150, user plane function (UPF) 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144 and unified data management , UDM) 146. UPF 134 may provide a connection to a data network (DN) 152, which may include, for example, carrier services, Internet access, or third-party services.

Referring to Figure IE, a 5G system architecture 140E and service-based representation is illustrated. System architecture 140E may be substantially similar (or identical) to system architecture 140D. In addition to the network entities shown in FIG. 1D , the system architecture 140E may also include a network exposure function (NEF) 154 and a network repository function (NRF) 156 .

In some aspects, the 5G system architecture may be service-based, and interactions between network functions may be represented by corresponding point-to-point reference points Ni (as shown in Figure ID) or as service-based interfaces (as shown in Figure 1D ). 1E).

Reference point representations indicate that interactions can exist between corresponding NF services. For example, Figure ID illustrates the following reference points: N1 (between UE and AMF), N2 (between RAN and AMF), N3 (between RAN and UPF), N4 (between SMF and UPF) , N5 (between PCF and AF), N6 (between UPF and DN), N7 (between SMF and PCF), N8 (between UDM and AMF), N9 (between two UPFs) , N10 (between UDM and SMF), N11 (between AMF and SMF), N12 (between AUSF and AMF), N13 (between AUSF and UDM), N14 (between two AMFs) , N15 (between PCF and AMF in case of non-roaming scenario, or between PCF and visited network and AFM in case of roaming scenario), N16 (between two SMFs; not shown in Figure 1D shown), and N22 (between AMF and NSSF). Other reference point representations not shown in Figure ID may also be used.

In some aspects, as shown in FIG. IE, a service-based representation may be used to represent network functions within the control plane that enable other authorized network functions to access their services. Here, 5G system architecture 140E may include the following service-based interfaces: Namf 158H (service-based interface presented by AMF 132 ), Nsmf 158I (service-based interface presented by SMF 136 ), Nnef 158B (service-based interface presented by NEF 154 ) service-based interface), Npcf 158D (service-based interface presented by PCF 148), Nudm 158E (service-based interface presented by UDM 146), Naf158F (service-based interface presented by AF 150), Nnrf 158C (service-based interface presented by NRF 156), Nnssf 158A (service-based interface presented by NSSF 142), Nausf 158G (service-based interface presented by AUSF 144). Other service-based interfaces (eg, Nudr, N5g-eir, and Nudsf) not shown in Figure IE may also be used.

1F illustrates an example CIoT network architecture in accordance with some aspects. Referring to Figure IF, a CIoT architecture 140F may include UE 102 and RAN 110 coupled to multiple core network entities. In some aspects, UE 102 may be a machine type communication (MTC) UE. The CIoT network architecture 140F may further include a mobile services switching center (MSC) 160, an MME 121, a serving GPRS support note (SGSN) 162, an S-GW 122, an IP short message gateway (IP- Short-Message-Gateway, IP-SM-GW) 164, Short Message Service Center (Short Message Service Service Center, SMS-SC)/Gateway Mobile Service Center (GMSC)/Interworking MSC (Interworking MSC, IWMSC) 166, MTC interworking function (MTC-IWF) 170, ServiceCapability Exposure Function (SCEF) 172, gateway GPRS supportnode (GGSN)/patent GW 174, charging data function (charging data function, CDF)/charging gateway function (charging gateway function, CGF) 176, home subscriber server (home subscriber server, HSS)/home location register (home location register, HLR) 177, short message entity (short message entity, SME) 168, MTC authorization, authentication, and accounting (MTC AAA) server 178, service capability server (SCS) 180, and application servers (AS) 182 and 184.

In some aspects, SCEF 172 may be configured to securely expose services and capabilities provided by various 3GPP network interfaces. SCEF 172 may also provide means for discovering exposed services and capabilities, as well as access to network capabilities through various network application programming interfaces (eg, API interfaces to SCS 180).

Figure IF also illustrates various reference points between different servers, functions or communication nodes of the CIoT architecture 140F. Some example reference points related to MTC-IWF 170 and SCEF 172 include the following: Tsms (reference point used by entities outside the 3GPP network to communicate with UEs for MTC via SMS), Tsp (used by SCS to communicate with MTC - Reference point for IWF related control plane signaling communication), T4 (for reference point between MTC-IWF 170 and SMS-SC 166 in HPLMN), T6a (for reference between SCEF 172 and serving MME 121 point), T6b (for reference point between SCEF 172 and serving SGSN 162), T8 (for reference point between SCEF 172 and SCS/AS 180/182), S6m (for interrogation by MTC-IWF 170 Reference point for HSS/HLR 177), S6n (reference point used by MTC-AAA 178 to interrogate HSS/HLR 177), and S6t (reference point used between SCEF 172 and HSS 177).

In some aspects, the CIoT UE 102 may be configured according to a non-access stratum (NAS) protocol and utilize one or more reference points, such as a narrowband air interface, based on one or more communication technologies, such as orthogonal frequency division complexing One or more entities within the CIoT architecture 140F are communicated via the RAN 110 using (OFDM) techniques. As used herein, the term "CIoT UE" refers to a UE capable of CIoT optimization as part of the CIoT communication architecture.

In some aspects, the NAS protocol may support a set of NAS messages for communication between CIoT UE 102 and Evolved Packet System (EPS) Mobile Management Entity (MME) 121 and SGSN 162 .

In some aspects, the CIoT network architecture 140F may include a packet data network, a carrier network, or a cloud services network with, for example, a service capability server (SCS) 180, an application server (AS) 182, or one or more other external servers or networks components, etc.

The RAN 110 may be coupled to the HSS/AAA server 177/178 using one or more reference points (eg, including an air interface based on the S6a reference point) and configured to authenticate/authorize the CIoT UE 102 to access the CIoT network. The RAN 110 may be coupled to the network 140F using one or more other reference points including, for example, an air interface corresponding to the SGi/Gi interface for 3GPP access. The RAN 110 may be coupled to the SCEF 172 using, for example, a T6a/T6b reference point based air interface for service capability exposure. In some aspects, SCEF 172 may act as an API GW towards a 3rd party application server such as AS 182. SCEF 172 may couple to the HSS/AAA server using the S6t reference point, and may also expose application programming interfaces to network capabilities.

In some examples, one or more of the CIoT devices disclosed herein, such as the CIoT UE 102, the CIoTRAN 110, etc., may include one or more other non-CIoT devices, or act as or function as CIoT devices Non-CIoT devices. For example, the CIoT UE 102 may include a smartphone, tablet computer, or one or more other electronic devices that act as CIoT devices for specific functions, while having other additional functions.

In some aspects, the RAN 110 may include a CIoT enhanced Node B (CIoT eNB) 111 communicatively coupled to a CIoT access network gateway (CIoT GW) 190 . In some examples, RAN 110 may include multiple base stations (eg, CIoT eNBs) connected to CIoT GW 190, which may include MSC 160, MME 121, SGSN 162, and/or S-GW 122. In some examples, the internal architecture of RAN 110 and CIoT GW 190 may be implementation-determined and need not be standardized.

As used herein, the term circuit may refer to, be a part of, or include an Application Specific Integrated Circuit (ASIC) or other special purpose circuit, electronic circuit, performing one or more A processor (shared, dedicated, or group) or memory (shared, dedicated, or group) of a software or firmware program, combinational logic, or other suitable hardware components that provide the described functionality. According to some aspects, a circuit may be implemented in, or functions associated with, a circuit may be implemented in one or more software or firmware modules. In some aspects, a circuit may include logic operable, at least in part, in hardware. In some aspects, the circuits and modules disclosed herein may be implemented in a combination of hardware, software and/or firmware. In some aspects, the functionality associated with a circuit may be distributed over more than one hardware or software/firmware module. In some aspects, a module (disclosed herein) may comprise logic operable, at least in part, in hardware. Aspects described herein may be implemented into a system using any suitably configured hardware or software.

FIG. 2 illustrates example components of device 200 according to some aspects. In some aspects, device 200 may include application circuitry 202, baseband circuitry 204, radio frequency (RF) circuitry 206, front-end module (FEM) circuitry 208, One or more antennas 210 and power management circuitry (PMC) 212 . The illustrated components of apparatus 200 may be included in a UE or a RAN node. In some aspects, apparatus 200 may include fewer elements (eg, a RAN node may not utilize application circuitry 202, but instead include a processor/controller to process IP data received from the EPC). In some aspects, device 200 may include additional elements, such as memory/storage, display, camera, sensors, and/or input/output (I/O) interface elements. In other aspects, the components described below may be included in more than one device (eg, for Cloud-RAN (C-RAN) implementations, the circuits may be included separately in more than one device) .

Application circuitry 202 may include one or more application processors. For example, application circuitry 202 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors, special-purpose processors, and special-purpose processors (eg, graphics processors, application processors, etc.). The processor may be coupled to and/or include the memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 200 . In some aspects, the processor of the application circuit 202 may process IP data packets received from the EPC.

Baseband circuitry 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 204 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of RF circuitry 206 and generate baseband signals for a transmit signal path of RF circuitry 206 . Baseband processing circuitry 204 may interface with application circuitry 202 to generate and process baseband signals and to control the operation of RF circuitry 206 . For example, in some aspects baseband circuitry 204 may include third generation (3G) baseband processor 204A, fourth generation (4G) baseband processor 204B, fifth generation (5G) baseband processor 204C, or for other existing Other baseband processor(s) 204D of a generation, a generation under development, or a generation to be developed in the future (eg, second generation (2G), sixth generation (6G), etc.). Baseband circuitry 204 (eg, one or more of baseband processors 204A-D) may handle various radio control functions that enable communication with one or more radio networks via RF circuitry 206 . In other aspects, some or all of the functions of baseband processors 204A-D may be included in modules stored in memory 204G and performed via central processing unit (CPU) 204E. Radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency offset, and the like. In some aspects, the modulation/demodulation circuitry of baseband circuitry 204 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some aspects, the encoding/decoding circuitry of baseband circuitry 204 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Aspects of modulation/demodulation and encoder/decoder functionality are not limited to these examples, and other suitable functionality may be included in other aspects.

In some aspects, baseband circuitry 204 may include one or more audio digital signal processors (DSPs) 204F. The audio DSP(s) 204F may include elements for compression/decompression and echo cancellation, and may include other suitable processing elements, among other aspects. The components of the baseband circuitry may be suitably combined in a single chip, a single chip set, or in some aspects arranged on the same circuit board. In some aspects, some or all of the constituent components of the baseband circuit 204 and the application circuit 202 may be implemented together, eg, on a system on a chip (SOC).

In some aspects, baseband circuitry 204 may support communications compatible with one or more radio technologies. For example, in some aspects, baseband circuitry 204 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network, WLAN) and/or wireless personal area network (wireless personal area network, WPAN). In some aspects, baseband circuitry 204 configured to support radio communications of more than one wireless protocol may be referred to as a multi-mode baseband circuit.

RF circuitry 206 may enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various aspects, RF circuitry 206 may include switches, filters, amplifiers, etc. to facilitate communication with wireless networks. RF circuitry 206 may include a receive signal path that may include circuitry to downconvert RF signals received from FEM circuitry 208 and provide baseband signals to baseband circuitry 204 . RF circuit 206 may also include a transmit signal path, which may include circuitry to upconvert the baseband signal provided by baseband circuit 204 and provide the RF output signal to FEM circuit 208 for transmission.

In some aspects, the receive signal path of RF circuit 206 may include mixer 206A, amplifier 206B, and filter 206C. In some aspects, the transmit signal path of RF circuit 206 may include filter 206C and mixer 206A. The RF circuit 206 may also include a synthesizer 206D for synthesizing frequencies for use by the mixer 206A of the receive signal path and the transmit signal path. In some aspects, the mixer 206A of the receive signal path may be configured to downconvert the RF signal received from the FEM circuit 208 based on the synthesized frequency provided by the synthesizer 206D. Amplifier 206B may be configured to amplify the down-converted signal and filter 206C may be a low-pass filter configured to remove unwanted signals from the down-converted signal to generate an output baseband signal , LPF) or band-pass filter (band-pass filter, BPF). The output baseband signal may be provided to baseband circuitry 204 for further processing. In some aspects, the output baseband signal may optionally be a zero-frequency baseband signal. In some aspects, the mixer 206A of the receive signal path may comprise a passive mixer.

In some aspects, the mixer 206A of the transmit signal path may be configured to upconvert the input baseband signal based on the synthesis frequency provided by the synthesizer 206D to generate the RF output signal for the FEM circuit 208 . The baseband signal may be provided by baseband circuitry 204 and may be filtered by filter 206C.

In some aspects, the mixer 206A of the receive signal path and the mixer 206A of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some aspects, the mixer 206A of the receive signal path and the mixer 206A of the transmit signal path may include two or more mixers and may be arranged for image rejection (eg, Hartley) image suppression). In some aspects, mixer 206A and mixer 206A of the receive signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some aspects, the mixer 206A of the receive signal path and the mixer 206A of the transmit signal path may be configured for superheterodyne operation.

In some alternative aspects, the output baseband signal and the input baseband signal may optionally be analog baseband signals. According to some alternative aspects, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative aspects, RF circuitry 206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits and baseband circuitry 204 may include digital A baseband interface to communicate with RF circuitry 206 .

In some dual-mode aspects, separate radio IC circuits may optionally be provided to process signals for each spectrum.

In some aspects, synthesizer 206D may alternatively be a fractional N synthesizer or a fractional N/N+1 synthesizer, although other types of frequency synthesizers may also be suitable. For example, the synthesizer 206D may be an incremental sum synthesizer, a frequency multiplier, or a synthesizer including a phase locked loop with a frequency divider.

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

In some aspects, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not a necessary requirement. The divider control input may be provided, for example, by the baseband circuit 204 or the application processor 202, depending on the desired output frequency. In some aspects, the divider control input (eg, N) may be determined from a lookup table based on the channel indicated by the application processor 202 .

The combiner circuit 206D of the RF circuit 206 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some aspects, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some aspects, the DMD may be configured to divide the input signal by N or N+1 (eg, based on carry) to provide a fractional divide ratio. In some example aspects, the DLL may include a cascaded set of tunable delay elements, phase detectors, charge pumps, and D-type flip-flops. In these aspects, the delay elements may be configured to decompose the VCO cycle into Nd equal phase groupings, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help keep the total delay through the delay line to one VCO cycle.

In some aspects, the synthesizer circuit 206D may be configured to generate the carrier frequency as the output frequency, while in other aspects the output frequency may be a multiple of the carrier frequency (eg, twice the carrier frequency, or four times the carrier frequency) And can be used with a quadrature generator and divider circuit to generate multiple signals at the carrier frequency with multiple different phases from each other. In some aspects, the output frequency may be the LO frequency (fLO). In some aspects, the RF circuit 206 may include an IQ/polarity converter.

FEM circuitry 208 may include a receive signal path that may include a receive signal path configured to operate on RF signals received from one or more antennas 210 and/or amplify and amplify received signals The amplified version is provided to the RF circuit 206 circuit for further processing. FEM circuitry 208 may also include a transmit signal path, which may include circuitry configured to amplify signals provided by RF circuitry 206 for transmission for transmission by one or more of one or more antennas 210 . In various aspects, the amplification through the transmit signal path or the receive signal path may be done partially or fully in RF circuit 206 , partially or fully in FEM 208 , or in both RF circuit 206 and FEM 208 .

In some aspects, the FEM circuit 208 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify the received RF signal and provide the amplified receive RF signal as an output (eg, to RF circuit 206). The transmit signal path of the FEM circuit 208 may include a power amplifier (PA) to amplify the input RF signal (eg, provided by the RF circuit 206) and one or more filters to generate the RF signal for subsequent transmission ( For example, transmitted by one or more of one or more antennas 210).

In some aspects, PMC 212 may manage the power provided to baseband circuitry 204 . The PMC 212 can control power selection, voltage scaling, battery charging and/or DC-to-DC conversion. The PMC 212 may be included in some aspects when the device 200 can be battery powered, such as when the device is included in a UE. PMC 212 increases power conversion efficiency while providing beneficial implementation size and thermal dissipation characteristics.

FIG. 2 shows the PMC 212 coupled to the baseband circuit 204 . In other aspects, PMC 212 may additionally or alternatively be coupled to and perform similar power management operations for other components, such as, but not limited to, application circuit 202 , RF circuit 206 , or FEM 208 .

In some aspects, PMC 212 may control or otherwise be part of various power saving mechanisms of device 200 . For example, if the device 200 is in the RRC_Connected state still connected to a RAN node because it expects to receive traffic soon, it may enter a state called Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, device 200 may be powered off for brief time intervals and thereby conserve power.

According to some aspects, if there is no data traffic activity for an extended period of time, the device 200 may transition off to the RRC_Idle state in which it is disconnected from the network and does not perform functions such as channel quality feedback, handover, etc. operation. The device 200 enters a very low power state and it performs a page, during which it periodically wakes up to listen to the network, and then powers down again. Device 200 may transition back to the RRC_Connected state to receive data.

Additional power saving modes may allow devices to be unavailable to the network for periods longer than the paging interval (ranging from seconds to hours). During this time, device 200 may be unreachable to the network in some aspects and may be powered off. Any data sent during this time suffers from a potentially large delay and is assumed to be acceptable.

The processor of the application circuit 202 and the processor of the baseband circuit 204 may be used to execute elements of one or more instances of the protocol stack. For example, the processors of baseband circuitry 204 may be used, alone or in combination, to perform layer 3, layer 2, or layer 1 functions, while the processors of application circuitry 204 may utilize data (eg, packetized data) received from these layers and further perform layer 3 4 functions (eg, transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, layer 3 may include a radio resource control (RRC) layer, which is described in more detail below. As referred to herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer layer, which is described in more detail below. As referred to herein, layer 1 may include the physical (PHY) layer of the UE/RAN node, which is described in more detail below.

3 illustrates an example interface for a baseband circuit in accordance with some aspects. As mentioned above, the baseband circuit 204 of FIG. 2 may include processors 204A-204E and memory 204G utilized by the processors. Each of the processors 204A-204E may include a memory interface 304A-304E, respectively, to send/receive data to/from the memory 204G.

组件(例如，低能耗

)、

组件和其他通信组件发送/接收数据的接口)以及电力管理接口320(例如，向/从PMC 212发送/接收电力或控制信号的接口)。The baseband circuit 204 may also include one or more interfaces to communicatively couple to other circuits/devices, such as a memory interface 312 (eg, an interface to send/receive data to/from memory external to the baseband circuit 204), an application circuit interface 314 ( For example, an interface to send/receive data to/from the application circuit 202 of FIG. 2 ), RF circuit interface 316 (eg, an interface to send/receive data to/from the RF circuit 206 of FIG. 2 ), wireless hardware connectivity interface 318 ( For example, to/from Near Field Communication (NFC) components,

components (e.g. low energy

),

components and other communication components to send/receive data) and a power management interface 320 (eg, an interface to send/receive power or control signals to/from the PMC 212).

4 is an illustration of a control plane protocol stack in accordance with some aspects. In one aspect, control plane 400 is shown as a communication protocol stack between UE 101 (or UE 102 ), RAN node 111 (or RAN node 112 ), and MME 121 .

PHY layer 401 may in some aspects transmit or receive information used by MAC layer 402 over one or more air interfaces. PHY layer 401 may also perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (eg, for initial synchronization and handover purposes), and processing by higher layers (eg, RRC layer 405) Other measurements used. PHY layer 401 may in some aspects also perform error detection on transport channels, forward error correction (FEC) encoding/decoding of transport channels, modulation/demodulation of physical channels, interleaving, rate matching, to physical Mapping on channels and Multiple Input Multiple Output (MIMO) antenna processing.

The MAC layer 402 may perform mapping between logical channels and transport channels in some aspects, multiplexing MAC service data units (SDUs) from one or more logical channels onto transport blocks (TBs) for delivery to the PHY via the transport channel, demultiplexing the MAC SDUs from transport blocks (TBs) delivered from the PHY via the transport channel to one or more logical channels, multiplexing the MAC SDUs onto the TBs, scheduling information reporting, via Error correction for hybrid automatic repeat request (HARQ), and logical channel prioritization.

The RLC layer 403 may, in some aspects, operate in various modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC layer 403 may perform upper layer protocol data unit (PDU) transfer, error correction by automatic repeat request (ARQ) for AM data transfer, and RLC for UM and AM data transfer Concatenation, segmentation and reassembly of SDUs. The RLC layer 403 may also, in some aspects, perform 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, and discard for UM and AM data transfers RLC SDU, detects protocol errors for AM data transfer, and performs RLC re-establishment.

The PDCP layer 404 may in some aspects perform header compression and decompression of IP data, maintain PDCP Sequence Number (SN), perform in-sequence delivery of upper layer PDUs upon lower layer re-establishment, for radio bearers mapped on RLC AM Eliminates duplication of lower layer SDUs upon lower layer re-establishment, encrypts and decrypts control plane data, performs integrity protection and integrity verification of control plane data, controls timer-based discard of data, and performs security operations (eg, encryption , decryption, integrity protection, integrity verification, etc.).

In some aspects, the primary services and functions of the RRC layer 405 may include system information (eg, including a Master Information Block (MIB) or system information in relation to a non-access stratum (NAS) block (System Information Block, SIB)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of RRC connection between UE and E-UTRAN ( For example, RRC connection paging, RRC connection establishment, RRC connection modification and RRC connection release), establishment, configuration, maintenance and release of point-to-point radio bearers, security functions including key management, radio access technology ( Inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting. The MIBs and SIBs may include one or more information elements (IEs), each information element may include an individual data field or data structure.

UE 101 and RAN node 111 may utilize a Uu interface (eg, LTE-Uu interface) to exchange control plane data via a protocol stack including PHY layer 401 , MAC layer 402 , RLC layer 403 , PDCP layer 404 and RRC layer 405 .

Non-Access Stratum (NAS) protocols 406 form the highest layer of the control plane between UE 101 and MME 121, as shown in FIG. 4 . In some aspects, NAS protocol 406 supports UE 101 mobility and session management procedures to establish and maintain IP connectivity between UE 101 and P-GW 123.

The S1 Application Protocol (S1-AP) layer 415 may support the functions of the S1 interface and include an Elementary Procedure (EP). EP is the unit of interaction between RAN node 111 and CN 120 . In certain aspects, S1-AP layer services may include 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 signaling, RAN Information Management , RIM), and configuration transfer.

Stream Control Transmission Protocol (SCTP) layer (which may alternatively be referred to as SCTP/IP layer) 414 may ensure the integrity of signaling messages between RAN node 111 and MME 121 based in part on IP protocols supported by IP layer 413 . Reliable delivery. The L2 layer 412 and the L1 layer 411 may refer to the communication links (eg wired or wireless) used by the RAN node and the MME to exchange information.

RAN node 111 and MME 121 may utilize the S1-MME interface to exchange control plane data via a protocol stack including L1 layer 411 , L2 layer 412 , IP layer 413 , SCTP layer 414 and S1-AP layer 415 .

5 is an illustration of a user plane protocol stack in accordance with some aspects. In this aspect, user plane 500 is shown as a communication protocol stack between UE 101 (or UE 102 ), RAN node 111 (or RAN node 112 ), S-GW 122 and P-GW 123 . User plane 500 may utilize at least some of the same protocol layers as control plane 400 . For example, UE 101 and RAN node 111 may utilize a Uu interface (eg, LTE-Uu interface) to exchange user plane data via a protocol stack including PHY layer 401 , MAC layer 402 , RLC layer 403 and PDCP layer 404 .

A General Packet Radio Service (GPRS) Tunneling Protocol (GTP-U) layer 504 for the user plane may be used to carry user data within the GPRS core network and between the radio access network and the core network. The transmitted user data may be packets in eg IPv4, IPv6 or PPP format. UDP and IP security (UDP/IP) layer 503 may provide checksums for data integrity, port numbers for addressing different functions at source and destination, and encryption sums on selected data streams. Certification. The RAN node 111 and the S-GW 122 may utilize the S1-U interface to exchange user plane data via a protocol stack including the L1 layer 411 , the L2 layer 412 , the UDP/IP layer 503 and the GTP-U layer 504 . S-GW 122 and P-GW 123 may utilize the S5/S8a interface to exchange user plane data via a protocol stack including L1 layer 411 , L2 layer 412 , UDP/IP layer 503 and GTP-U layer 504 . As described above for FIG. 4, the NAS protocol supports UE 101 mobility and session management procedures to establish and maintain IP connectivity between UE 101 and P-GW 123.

6 is a diagram illustrating the ability to read instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and perform any one or more of the methods discussed herein, according to some example aspects Block diagram of components. Specifically, Figure 6 shows a diagrammatic representation of a hardware resource 600 including one or more processors (or processor cores) 610, one or more memory/storage devices 620, and one or more communication resources 630 , each of which may be communicatively coupled via bus 640 . For aspects utilizing node virtualization (eg, NFV), a hypervisor 602 may be executed to provide an execution environment for utilizing hardware resources 600 for one or more network slices and/or sub-slices.

Processor 610 (eg, central processing unit (CPU), reduced instruction set computing (RISC) processor, complex instruction set computing (CISC) processor, graphics processing unit ( graphics processing unit (GPU), digital signal processor (DSP) (eg baseband processor), application specific integrated circuit (ASIC), radio-frequency integrated circuit (RFIC), other A processor or any suitable combination of these) may include processor 612 and processor 614, for example.

Memory/storage 620 may include main memory, disk storage, or any suitable combination of these. The memory/storage device 620 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random-access memory (SRAM) , erasable programmable read-only memory (erasable programmable read-only memory, EPROM), electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), flash memory, solid-state storage devices, and the like.

组件(例如，低能耗

)，

组件和其他通信组件。Communication resources 630 may include interconnect or network interface components or other suitable devices to communicate with one or more peripheral devices 604 or one or more databases 606 via network 608 . For example, communication resources 630 may include wired communication components (eg, for coupling via Universal Serial Bus (USB)), cellular communication components, NFC components,

components (e.g. low energy

),

components and other communication components.

Instructions 650 may include software, programs, applications, applets, apps, or other executable code for causing at least any one of processors 610 to perform any one or more of the methods discussed herein. Instructions 650 may reside fully or partially within at least one of processors 610 (eg, within the processor's cache memory), within memory/storage 620, or any suitable combination of these. Furthermore, any portion of instructions 650 may be communicated to hardware resource 600 from any combination of peripheral device 604 or database 606 . Accordingly, the memory of the processor 610, the memory/storage devices 620, the peripheral devices 604, and the database 606 are examples of computer-readable and machine-readable media.

In some aspects, with reference to the CIoT network architecture 140F of FIG. 1F , coverage enhancement (CE) functionality may be used to ensure that certain subscribers (eg, those subscribed to services using CE) can benefit from CE-related features. In some aspects, specific subscribers are blocked from using enhanced coverage functionality in order to address the use of large resources from the network. In some aspects, new subscription parameters (eg, Enhanced Coverage Allowed parameters) may be introduced and stored in HSS 177 . In some aspects, the enhanced coverage enable parameter may be configured to specify, for each public land mobile network (PLMN), whether enhanced coverage functionality is permitted for a given UE. In some aspects, the third party service provider may query the status of the enhanced overlay via SCEF 172 or request the MNO to enable/disable the enhanced overlay. This solution may include updating NAS procedures (eg, ATTACH ACCEPT, tracking area update (TAU)/routing area update (RAU) ACCEPT messages) to receive enhanced coverage enable parameters, which are used in the UE for each Each PLMN stores this parameter and then uses the enhanced coverage capability based on the value of this parameter. In some aspects, HSS 177 may be configured to update subscription information to determine whether the UE is allowed to use CE functionality, and then provide this information to MME 121, where this information may be stored as a mobility management (MM) context and EPS Part of the hosting context. In some aspects, SCEF 172 may be configured to query HSS 177 to determine the status of enhanced coverage, and to enable or disable it, if desired. For example, in the case where the UE is not subscribed to CE functionality, the enhanced coverage may be restricted to the UE.

In some aspects, the UE may indicate its support for the restricted enhanced coverage feature in the ATTACH REQUEST and TRACKING AREA UPDATE REQUST messages, and if the UE supports this feature, the MME may be configured To indicate whether enhanced coverage is restricted in the ATTACH ACCEPT and TRACKING AREA UPDATE ACCEPT messages. In the case where enhanced coverage is restricted for a particular PLMN, then the UE will not have access to the enhanced coverage capability in that PLMN.

7 illustrates an example communication sequence in a CIoT environment, according to some aspects. Referring to FIG. 7 , a communication sequence 700 may occur between UE 702 , MME/SGSN 704 and HSS 706 .

In one aspect, CIoT architecture 140F may be associated with an Evolved Packet System (EPS). In this case, the UE may send an attach request to the MME 704 at 708 . In one aspect, the attach request may include a UE network capability information element (IE) 800, as shown in FIG. 8 . The UE Network Capability IE 800 may include RestrictEC bits 802, which may be used to indicate whether the UE supports restrictions on enhanced coverage. For example, when the RestrictEC bit 802 is set, the UE Network Capability IE 800 indicates that the UE supports restrictions on the use of enhanced coverage. Conversely, when the RestrictEC bit 802 is not set, the UE Network Capability IE 800 indicates that the UE does not support restrictions on the use of enhanced coverage. In some aspects, the RestrictEC bit 802 may be located in bit number 3 of byte 9 of the UE Network Capability IE 800 .

Referring to FIG. 7 , at 710 , an update location request may be communicated from MME 704 to HSS 706 . The HSS 706 may obtain the value of the enhanced coverage allow parameter at 712 for the particular UE 702. At 714, the HSS 706 may communicate an updated location confirmation, which may include an enhanced coverage allow parameter (or another type of indication, such as subscription information regarding whether the UE 702 is subscribed to enhanced coverage functionality or restrictions on enhanced coverage functionality). At 716 , the MME 704 may set the value of the enhanced coverage allow parameter in the MM context for the UE 702 based on the parameter value received from the HSS 706 .

At 718, the MME 704 may send an Attach Accept message, which may include an indication of whether enhanced coverage is restricted to the UE. More specifically, the MME 704 may send an EPS Network Feature Support IE, which may include bits that indicate whether the use of enhanced coverage is restricted or not restricted for the UE 702. 9 illustrates an example EPS network feature support information element in accordance with some aspects. Referring to FIG. 9, the EPS Network Feature Support IE 900 may include RestrictEC bits 902, which may be used to indicate whether enhanced coverage is restricted for the UE. For example, when the RestrictEC bit 902 is set, enhanced coverage is restricted for this UE. Conversely, when the RestrictEC bit 902 is not set, the use of enhanced coverage is not restricted for the UE. In some aspects, RestrictEC bit 802 may be located in bit number 5 of byte 4 of EPS Network Feature Support IE 900.

In some aspects, the UE may indicate its support for the restricted enhanced coverage feature in a Tracking Area Update (TAU) request message, which may be conveyed at 708 . In this case, MME 704 may indicate whether enhanced coverage is restricted for UE 702 in a Tracking Area Update (TAU) Accept message conveyed at 718 . More specifically, the UE Network Capability IE 800 (with a RestrictEC bit indication of whether the UE supports restrictions on the use of enhanced coverage) is conveyed in the TAU Request message sent at 708, and the EPS Network Feature Support IE 900 (with The RestrictEC bit indicating whether the use of enhanced coverage is restricted to the UE) is conveyed in the TAU Accept message sent at 718.

In some aspects, CIoT architecture 140F may be associated with General Packet Radio Service (GPRS). In this case, UE 702 (which may be referred to as a mobile station or MS) may communicate with SGSN 704 (instead of MME), and different information elements may be used to convey restrictions on whether the MS supports the use of enhanced coverage and whether Indication of MS restricted enhanced coverage.

For example, referring to FIG. 7, at 708, MS 702 may send an attach request to SGSN 704. In one aspect, the attach request may include an MS Network Capability IE 1000, as shown in FIG. 10 . The MS Network Capability IE 1000 may include bits 1002 that may be used to indicate whether the MS supports restrictions on the use of enhanced coverage. For example, when bit 1002 is set, the MS Network Capability IE 1000 indicates that the MS supports restrictions on the use of enhanced coverage. Conversely, when the bit 1002 is not set, the MS Network Capability IE 1000 indicates that the MS does not support restrictions on the use of enhanced coverage.

At 710, an update location request may be communicated from the SGSN 704 to the HSS 706. The HSS 706 may obtain at 712 the value of the enhanced coverage allow parameter for the particular MS 702. At 714, the HSS 706 can communicate an updated location confirmation, which can include an enhanced coverage allow parameter (or another type of indication, such as subscription information as to whether the MS 702 subscribes to enhanced coverage functionality or restrictions on enhanced coverage functionality). At 716, the SGSN 704 may set the value of the enhanced coverage allow parameter in the MM context for the MS 702 based on the parameter value received from the HSS 706.

At 718, the SGSN 704 may send an Attach Accept message, which may include an indication of whether enhanced coverage is restricted to the MS. More specifically, the SGSN 704 may send an additional network feature support IE, which may include bits that indicate whether the use of enhanced coverage is restricted or not restricted for the MS 702. 11 illustrates an example additional network feature support information element in accordance with some aspects. Referring to Figure 11, the Additional Network Feature Support IE 900 may include RestrictEC bits 1102, which may be used to indicate whether enhanced coverage is restricted for MS 702. For example, when the RestrictEC bit 1102 is set, enhanced coverage is restricted for this MS. Conversely, when the RestrictEC bit 1102 is not set, the use of enhanced coverage is not restricted for the MS. In some aspects, the RestrictEC bit 1102 may be located in bit number 2 of byte 3 of the Additional Network Feature Support IE 1100.

In some aspects, the MS may indicate its support for the restricted enhanced coverage feature in a Routing Area Update (RAU) request message, which may be conveyed at 708 . In this case, SGSN 704 may indicate whether enhanced coverage is restricted for MS 702 in a Routing Area Update (RAU) Accept message conveyed at 718 . More specifically, the MS Network Capability IE 1000 (with bits 1002 indicating whether the MS supports restrictions on the use of enhanced coverage) is conveyed in the TAU Request message sent at 708, and the Additional Network Features Support IE 1100 (with information on whether A RestrictEC bit indicating that the MS restricts the use of enhanced coverage) is conveyed in the TAU Accept message sent at 718.

In some aspects, the MME 704 may communicate an Attach Accept or TAU Accept message at 718 in the form of a NAS message that is communicated to the eNB 703 at 717A and then forwarded by the eNB 703 to the UE 702 in communication 717B. In some aspects, MME 704 may send one or more additional messages to eNB 703 in communication 717A, which may include enhanced coverage restriction parameters (eg, indicating whether the UE is restricted from using coverage enhancement). In some aspects, the messages communicated from the MME 704 to the eNB 703 at 717A may include one or more of an initial context setup request message, a handover request message, and a downlink NAS transfer message.

12 generally illustrates a flow diagram of an example method of operating a UE that supports restrictions on use of enhanced coverage, in accordance with some aspects. 12, an example method 1200 may be performed by a CIoT UE (eg, 102) configured for Evolved Packet System (EPS) communications in a public land mobile network (PLMN). At operation 1202, the processing circuitry of the UE may be configured to encode the attach request message for transmission to a mobility management entity (MME) in the EPS (eg, conveyed at 708 in FIG. 7). The attach request message may include a UE network capability information element (IE) (eg, 800) that indicates whether the UE supports restrictions on using enhanced coverage. At operation 1204, the processing circuitry of the UE may be configured to decode the Attach Accept message (eg, conveyed at operation 718 in FIG. 7) confirming the attachment to the MME. The Attach Accept message may include an EPS Network Feature Support IE (eg, 900) indicating whether use of enhanced coverage is restricted for the UE. At operation 1206, the processing circuitry of the UE may be configured to refrain from using the enhanced coverage in the PLMN when the UE supports the restriction on using the enhanced coverage and the EPS Network Feature Support IE indicates that the enhanced coverage is restricted for the UE.

13 illustrates a block diagram of a communication device, such as an evolved Node B (eNB), next generation Node B (gNB), access point (AP), radio station (STA), or user equipment (UE), in accordance with some aspects . In alternate aspects, communication device 1300 may operate as a stand-alone device or may be connected (eg, networked) to other communication devices.

A circuit (eg, a processing circuit) is a collection of circuits implemented in a tangible entity of the device 1300 including hardware (eg, simple circuits, gates, logic, etc.). Circuit membership can be flexible over time. A circuit includes members that, when operated, individually or in combination, perform specified operations. In one example, the hardware of a circuit may be permanently designed (eg, hardwired) to perform a particular operation. In one example, the hardware of a circuit may include variably connected physical components (eg, execution units, transistors, simple circuits, etc.), including the ability to physically modify (eg, magnetically, electrically, invariably aggregate particles) mobile placement, etc.) to encode a machine-readable medium of instructions for a particular operation.

When connecting physical components, the underlying electrical properties of the hardware components are changed, eg, from an insulator to a conductor, or vice versa. The instructions enable embedded hardware (eg, an execution unit or loading mechanism) to create members of a circuit with hardware via variable connections to, when in operation, perform some portion of a particular operation. Thus, in one example, a machine-readable medium element is part of a circuit or is communicatively coupled to other components of a circuit when the device is in operation. In an example, any physical component may be used in more than one member of more than one circuit. For example, in operation, an execution unit may be used in a first circuit of a first circuit system at one point in time and by a second circuit in the first circuit system or by a second circuit system at a different time The third circuit is used again. Additional examples of these components of device 1300 are as follows.

In some aspects, device 1300 may operate as a stand-alone device or may be connected (eg, networked) to other devices. In a networked deployment, the communication device 1300 may operate as a server communication device, a client communication device, or both in a server-client network environment. In an example, the communication device 1300 may function as a peer-to-peer communication device in a peer-to-peer (P2P) (or other distributed) network environment. The communication device 1300 may be a UE, eNB, PC, tablet PC, STB, PDA, mobile phone, smartphone, web appliance, network router, switch or bridge or capable of executing instructions (sequence) specifying actions to be taken by the communication device. , or otherwise) any communication device. Additionally, although only a single communication device is illustrated, the term "communication device" should also be understood to include a set (or sets) of instructions executing, individually or jointly, any one or more of the methods discussed herein. Any collection of communication devices of a person, such as cloud computing, software as a service (SaaS), other computer cluster configurations.

Examples as described herein may include or may operate on logic or several components, modules or mechanisms. A module is a tangible entity (eg, hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged as modules in a specified manner (eg, internally or to external entities such as other circuits). In one example, all or a portion of one or more computer systems (eg, stand-alone, client, or server computer systems) or one or more hardware processors may be configured by firmware or software (eg, instructions, application portions, or applications) A module that performs the specified operation for the operation. In one example, the software may reside on a communication device readable medium. In one example, software, when executed by the underlying hardware of a module, causes the hardware to perform specified operations.

Accordingly, the term "module" is understood to encompass a tangible entity, whether physically constructed, specifically configured (eg, hardwired), or temporarily (eg, temporarily) configured (eg, programmed) to operate in a specified manner Or perform some or all of any of the operations described herein. Consider the example of configuring modules temporarily, each module need not be instantiated at any one time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as various modules at different times. The software may accordingly configure the hardware processor to constitute a particular module at one time and a different module at a different time, for example.

The communication device (eg, UE) 1300 may include a hardware processor 1302 (eg, a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination of these), a main Memory 1304 , static memory 1306 , and mass storage 1316 (eg, hard drives, tape drives, flash memory, or other block or storage devices), some or all of which may be in communication with each other via interconnecting links (eg, buses) 1308 .

The communication device 1300 may also include a display unit 1310, an alphanumeric input device 1312 (eg, a keyboard), and a user interface (UI) navigation device 1314 (eg, a mouse). In an example, display unit 1310, input device 1312, and UI navigation device 1314 may be touch screen displays. The communication device 1300 may also include a signal generating device 1318 (eg, a speaker), a network interface device 1320, and one or more sensors 1321, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors. Communication device 1300 may include an output controller 1328, such as serial (eg, universal serial bus (USB)), parallel, or other wired or wireless (eg, infrared (IR), near field communication communication, NFC), etc.) to communicate with or control one or more peripheral devices (eg, printers, card readers, etc.).

The storage device 1316 may include a communication device-readable medium 1322 having stored thereon data to implement or utilize any one or more of the techniques or functions described herein. One or more sets of data structures or instructions 1324 (eg, software). In some aspects, registers of processor 1302, main memory 1304, static memory 1306, and/or mass storage 1316 may be or include (in whole or at least in part) a device-readable medium 1322 on which are stored implementations described herein One or more sets of data structures or instructions 1324 used by any one or more of the techniques or functions described herein or utilized by any one or more of the techniques or functions described herein. In an example, one or any combination of hardware processor 1302 , main memory 1304 , static memory 1306 , or mass storage device 1316 may constitute device-readable medium 1322 .

As used herein, the term "device-readable medium" is interchangeable with "computer-readable medium" or "machine-readable medium." Although the communication device-readable medium 1322 is illustrated as a single medium, the term "communication device-readable medium" may include a single medium or multiple media (eg, centralized or distributed) configured to store one or more instructions 1324 databases, and/or associated caches and servers).

The term "communication device-readable medium" may include any instruction capable of storing, encoding, or carrying for execution by the communication device 1300 and causing the communication device 1300 to perform any one or more of the techniques of this disclosure or capable of storing, encoding, or carrying Such instructions use or mediate the data structures associated with such instructions. Non-limiting examples of communication device readable media may include solid state memory and optical and magnetic media. Specific examples of the communication device-readable medium may include: non-volatile memory, such as semiconductor memory devices (eg, Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (Electrically Erasable) Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; random access memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, the communication device-readable medium may include a non-transitory communication device-readable medium. In some examples, the communication device-readable medium may include a communication device-readable medium that is not a transitory propagating signal.

的电气与电子工程师学会(Institute of Electrical and Electronics Engineers，IEEE)802.11标准族、被称为

的IEEE802.16标准族)、IEEE 802.15.4标准族、长期演进(LongTerm Evolution，LTE)标准族、通用移动电信系统(Universal MobileTelecommunications System，UMTS)标准族、对等(peer-to-peer，P2P)网络，等等。在一示例中，网络接口设备1320可包括一个或多个物理插座(例如，以太网、同轴或电话插座)或者一个或多个天线来连接到通信网络1326。在一示例中，网络接口设备1320可包括多个天线以利用单输入多输出(single-input multiple-output，SIMO)、MIMO或者多输入单输出(multiple-input single-output，MISO)技术中的至少一者来无线地通信。在一些示例中，网络接口设备1320可利用多用户MIMO技术来无线地通信。Any of several transport protocols (eg, frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.) to send or receive instructions 1324 over a communication network 1326 using a transmission medium via a network interface device 1320. Example communication networks may include local area networks (LANs), wide area networks (WANs), packet data networks (eg, the Internet), mobile telephone networks (eg, cellular networks), Plain Old Telephone (POTS) ) networks and wireless data networks (for example, known as

The Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards, known as

IEEE802.16 standard family), IEEE 802.15.4 standard family, Long Term Evolution (LTE) standard family, Universal Mobile Telecommunications System (UMTS) standard family, peer-to-peer (P2P) ) network, etc. In an example, the network interface device 1320 may include one or more physical jacks (eg, Ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the communication network 1326 . In an example, network interface device 1320 may include multiple antennas to utilize single-input multiple-output (SIMO), MIMO, or multiple-input single-output (MISO) techniques At least one of them communicates wirelessly. In some examples, network interface device 1320 may communicate wirelessly using multi-user MIMO techniques.

The term "transmission medium" should be understood to include any intangible medium capable of storing, encoding, or carrying instructions for execution by communication device 1300, and includes digital or analog communication signals or other intangible media to facilitate communication of such software. Here, transmission media in the context of the present disclosure are device-readable media.

Additional notes and examples:

Example 1 is a cellular internet of things (CIoT) capable user equipment (UE) apparatus configured for evolved packet system (EPS) communications in a public land mobile network (PLMN), the apparatus comprising: processing circuitry configured to encode an Attach Request message for transmission to a Mobility Management Entity (MME) in the EPS, the Attach Request message including a message indicating whether the UE supports use of enhanced coverage Restricted UE Network Capability Information Element (IE); decoding an Attach Accept message confirming attachment to the MME, the Attach Accept message including EPS network feature support indicating whether the UE is restricted from using enhanced coverage IE; and suppressing the use of enhanced coverage in the PLMN when the UE supports restriction on the use of enhanced coverage and the EPS network feature support IE indicates that enhanced coverage is restricted for the UE; and a memory coupled to the processing circuit , the memory is configured to store the EPS network feature support IE.

In Example 2, the subject matter of Example 1 includes, wherein to suppress the use of enhanced coverage, the processing circuit is further configured to: when the UE supports restriction on the use of enhanced coverage and the EPS Network Feature Support IE indicates that the One or more enhanced coverage functions in the PLMN are disabled when the UE restricts enhanced coverage.

In Example 3, the subject matter of Examples 1-2 includes, wherein the memory stores a list of equivalent PLMNs, and the processing circuit is further configured to: when the UE supports restrictions on use of enhanced coverage and the EPS network features When the Support IE indicates that enhanced coverage is restricted to the UE, the use of enhanced coverage in any PLMN in the list of equivalent PLMNs is suppressed.

In Example 4, the subject matter of Examples 1-3 includes, wherein the UE Network Capability IE includes a bit that, when the bit is set, indicates that the UE supports a restriction on the use of enhanced coverage, and in the When the bit is not set, it indicates that the UE does not support restrictions on the use of enhanced coverage.

In Example 5, the subject matter of Example 4 includes wherein the bit is a Restrict Enhanced Coverage (RestrictEC) bit located in byte 9 of the UE Network Capability IE.

In Example 6, the subject matter of Examples 1-5 includes wherein the processing circuitry is configured to allow enhanced coverage to be used in the PLMN when the EPS Network Feature Support IE indicates that enhanced coverage is not restricted for the UE.

In Example 7, the subject matter of Examples 1-6 includes wherein the EPS Network Support IE includes a bit that indicates that the use of enhanced coverage is restricted for the UE when the bit is set, and When not set, indicates that the use of enhanced coverage is not restricted for the UE.

In Example 8, the subject matter of Example 7 includes wherein the bit is a Restricted Enhanced Coverage (RestrictEC) bit located in byte 4 of the EPS Network Feature Support IE.

In Example 9, the subject matter of Examples 1-8 includes, wherein the processing circuit is further configured to encode a tracking area update request message for transmission to the MME in the EPS, the tracking area update request message comprising indicating the Specifies whether the UE supports the UE Network Capability IE of Restriction on Using Enhanced Coverage.

In Example 10, the subject matter of Example 9 includes, wherein the processing circuit is further configured to decode a tracking area update accept message confirming a UE location update, the tracking area update accept message further including indicating whether the UE is restricted IE is supported by EPS network features for use of enhanced overlays.

In Example 11, the subject matter of Examples 1-10 includes: a transceiver circuit coupled to the processing circuit; and one or more antennas coupled to the transceiver circuit.

Example 12 is a non-transitory computer readable storage medium storing instructions for execution by one or more processors of a cellular internet of things (CIoT) capable mobile station (MS) configured for public land mobile General Packet Radio Service (GPRS) communications in a network (PLMN), the instructions configure the one or more processors to cause the MS to: encode an Attach Request message for transmission to a Serving GPRS Support Node (SGSN), The Attach Request message includes an MS Network Capability Information Element (IE) indicating whether the MS supports restrictions on the use of enhanced coverage; decoding an Attach Accept message confirming attachment to the SGSN, the Attach Accept message Including an additional network feature support IE indicating whether the use of enhanced coverage is restricted for the MS; and suppressing when the MS supports restriction on the use of enhanced coverage and the additional network feature support IE indicates that enhanced coverage is restricted for the MS Enhanced coverage is used in the PLMN.

In Example 13, the subject matter of Example 12 includes wherein the one or more processors further cause the MS to: when the MS supports restrictions on use of enhanced coverage and the Additional Network Feature Support IE indicates that the MS When restricting enhanced coverage, suppress the use of enhanced coverage in any PLMN in the list of equivalent PLMNs.

In Example 14, the subject matter of Examples 12-13 includes wherein the MS Network Capability IE includes a bit that, when the bit is set, indicates that the MS supports a restriction on use of enhanced coverage, and in the When the bit is not set, it indicates that the MS does not support restrictions on the use of enhanced coverage.

In Example 15, the subject matter of Examples 12-14 includes wherein the one or more processors further cause the MS to: allow enhanced coverage at the MS when the additional network feature support IE indicates that enhanced coverage is not restricted for the MS Enhanced coverage is used in PLMN.

In Example 16, the subject matter of Examples 12-15 includes wherein the additional network support IE includes a bit indicating that the MS restricts use of enhanced coverage for the MS when the bit is set, and in the bit When not set indicates that the use of enhanced coverage is not restricted for the MS.

In Example 17, the subject matter of Examples 12-16 includes, wherein the bit is a Restricted Enhanced Coverage (RestrictEC) bit located in a byte of the additional network feature support IE.

In Example 18, the subject matter of Example 17 includes, wherein the RestrictEC bit is located in byte 3 of the Additional Network Feature Support IE.

In Example 19, the subject matter of Examples 12-18 includes wherein the one or more processors further cause the MS to: encode a Routing Area Update (RAU) request message for transmission to the SGSN in the GPRS, the The RAU Request message includes an MS Network Capability IE indicating whether the MS supports the restriction on using enhanced coverage.

In Example 20, the subject matter of Example 19 includes wherein the one or more processors further cause the MS to: decode a Routing Area Update Accept message confirming the MS location update, the RAU Accept message further including indicating whether to The MS supports IE with additional network features that restrict the use of enhanced coverage.

Example 21 is an apparatus for a Node B (NB), the apparatus comprising: processing circuitry configured to decode a configuration message from a mobility management entity (MME), the configuration message ) an Enhanced Coverage Restriction Information Element (IE) that restricts use of enhanced coverage; creates a context for the UE based on the configuration message; and forwards a Downlink Network Access Stratum (NAS) Accept message for transmission based on the UE context to the UE, the NAS accept message including an EPS Network Feature Support IE indicating whether use of enhanced coverage is restricted to the UE; and a memory coupled to the processing circuit, the memory configured to store the enhanced coverage Restrict IE.

In Example 22, the subject matter of Example 21 includes wherein the configuration message is an initial context setup request message.

In Example 23, the subject matter of Examples 21-22 includes, wherein the configuration message is a handover request message.

In Example 24, the subject matter of Examples 21-23 includes wherein the configuration message is a downlink NAS transport message.

In Example 25, the subject matter of Examples 21-24 includes, wherein the processing circuit is further configured to encode an uplink non-access stratum (NAS) message for transmission to the MME, the NAS message including indicating the Specifies whether the UE supports the UE Network Capability Information Element (IE) for restrictions on using enhanced coverage.

In Example 26, the subject matter of Examples 21-25 includes: a transceiver circuit coupled to the processing circuit; and one or more antennas coupled to the transceiver circuit.

Example 27 is at least one machine-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement any of Examples 1-26.

Example 28 is an apparatus comprising means for implementing any of Examples 1-26.

Example 29 is a system for implementing any of Examples 1-26.

Example 30 is a method for implementing any of Examples 1-26.

Although an aspect has been described with reference to specific example aspects, it will be appreciated that various modifications and changes may be made in these aspects without departing from the broader scope of the disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings, which form a part hereof, show by way of illustration, and not limitation, specific aspects in which the subject matter may be implemented. The illustrated aspects are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other aspects may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. This "Detailed Description" section is therefore not to be taken in a limiting sense, but the scope of the various aspects is defined only by the appended claims, along with the full scope of equivalents to which such claims are entitled.

Such aspects of the inventive subject matter may be referred to herein individually and/or collectively for convenience only, and are not intended to voluntarily limit the scope of this application to any single aspect or inventive concept, if in fact more than one is disclosed. in one word. Thus, although specific aspects have been illustrated and described herein, it should be understood that any arrangement, which is calculated to achieve the same purpose, may be substituted for the specific aspects shown. This disclosure is intended to cover any and all adaptations or variations of various aspects. Combinations of the above aspects, as well as other aspects not specifically described herein, will be apparent to those skilled in the art upon reading the above description.

The Abstract of the Disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Furthermore, in the foregoing Detailed Description section, it can be seen that various features are grouped together in a single aspect for the purpose of streamlining the disclosure. This method of disclosure should not be construed as reflecting an intention that the claimed aspects require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed aspect. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate aspect.

Claims (25)

1. a device for a user equipment UE with cellular Internet of Things (CIoT) capability, the device being configured for Evolved Packet System (EPS) communication in a public land mobile network PLMN, the device comprising: a processing circuit configured to: encoding an Attach Request message for transmission to the Mobility Management Entity MME in the EPS, the Attach Request message including a UE Network Capability Information Element IE indicating whether the UE supports enhanced usage covered limitations; decoding an Attach Accept message confirming attachment to the MME, the Attach Accept message including an EPS Network Feature Support IE indicating whether the UE is restricted from using enhanced coverage; and suppressing the use of enhanced coverage in the PLMN when the UE supports the restriction on the use of enhanced coverage and the EPS Network Feature Support IE indicates that enhanced coverage is restricted for the UE; and A memory coupled to the processing circuit configured to store the EPS Network Feature Support IE. 2. The apparatus of claim 1, wherein to suppress the use of enhanced overlays, the processing circuit is further configured to: One or more enhanced coverage functions in the PLMN are disabled when the UE supports restriction on the use of enhanced coverage and the EPS Network Feature Support IE indicates that enhanced coverage is restricted for the UE. 3. The apparatus of any one of claims 1-2, wherein the memory stores a list of equivalent PLMNs, and the processing circuit is further configured to: When the UE supports restriction on the use of enhanced coverage and the EPS Network Feature Support IE indicates that enhanced coverage is restricted for the UE, the use of enhanced coverage in any PLMN in the list of equivalent PLMNs is suppressed. 4. The apparatus of any one of claims 1-2, wherein the UE Network Capability IE comprises bits that, when the bits are set, indicate that the UE supports restrictions on the use of enhanced coverage, And, when the bit is not set, it indicates that the UE does not support the restriction on the use of enhanced coverage. 5. The apparatus of claim 4, wherein the bit is a Restriction Enhancement Coverage RestrictEC bit located in byte 9 of the UE Network Capabilities IE. 6. The apparatus of any of claims 1-2, wherein the processing circuit is configured to: The use of enhanced coverage in the PLMN is allowed when the EPS Network Feature Support IE indicates that enhanced coverage is not restricted for the UE. 7. The apparatus of any one of claims 1-2, wherein the EPS network support IE includes a bit that, when the bit is set, indicates that use of enhanced coverage is restricted for the UE, and When the bit is not set, it indicates that the use of enhanced coverage is not restricted for the UE. 8. The apparatus of claim 7, wherein the bit is a Restriction Enhancement Override RestrictEC bit located in byte 4 of the EPS Network Feature Support IE. 9. The apparatus of any of claims 1-2, wherein the processing circuit is further configured to: A Tracking Area Update Request message is encoded for transmission to the MME in the EPS, the Tracking Area Update Request message including a UE Network Capability IE indicating whether the UE supports restrictions on using enhanced coverage. 10. The apparatus of claim 9, wherein the processing circuit is further configured to: Decoding a Tracking Area Update Accept message confirming UE location update, the Tracking Area Update Accept message further including the EPS Network Feature Support IE indicating whether the UE is restricted from using enhanced coverage. 11. The apparatus of any of claims 1-2, further comprising: a transceiver circuit coupled to the processing circuit; and one or more antennas coupled to the transceiver circuit. 12. A computer-readable storage medium storing instructions for execution by one or more processors of a device of a mobile station MS having cellular Internet of Things CIoT capabilities, the device being configured for general packetization in a public land mobile network PLMN radio service GPRS communications, the instructions for configuring the one or more processors such that the MS: encoding an Attach Request message for transmission to the Serving GPRS Support Node SGSN, the Attach Request message including an MS Network Capability Information Element IE, the MS Network Capability IE indicating whether the MS supports restrictions on the use of enhanced coverage; decoding an Attach Accept message confirming attachment to the SGSN, the Attach Accept message including an additional Network Feature Support IE indicating whether the MS is restricted from using enhanced coverage; and The use of enhanced coverage in the PLMN is suppressed when the MS supports a restriction on the use of enhanced coverage and the additional network feature support IE indicates that enhanced coverage is restricted for the MS. 13. The computer-readable storage medium of claim 12, wherein the one or more processors further cause the MS to: When the MS supports restriction on the use of enhanced coverage and the additional network feature support IE indicates that enhanced coverage is restricted for the MS, the use of enhanced coverage in any PLMN in the list of equivalent PLMNs is suppressed. 14. The computer-readable storage medium of any of claims 12-13, wherein the MS Network Capability IE includes bits that, when set, indicate that the MS supports enhanced coverage restrictions on usage and, when the bit is not set, indicate that the MS does not support restrictions on usage of enhanced coverage. 15. The computer-readable storage medium of any of claims 12-13, wherein the one or more processors further cause the MS to: The use of enhanced coverage in the PLMN is allowed when the additional network feature support IE indicates that enhanced coverage is not restricted for the MS. 16. The computer-readable storage medium of any of claims 12-13, wherein the additional network support IE includes a bit that, when the bit is set, indicates that the MS is restricted to enhanced coverage and indicates that the use of enhanced coverage is not restricted for the MS when the bit is not set. 17. The computer-readable storage medium of claim 16, wherein the bit is a restriction enhancement override RestrictEC bit located in a byte of the additional network feature support IE. 18. The computer-readable storage medium of claim 17, wherein the RestrictEC bit is located in byte 3 of the Additional Network Feature Support IE. 19. The computer-readable storage medium of any of claims 12-13, wherein the one or more processors further cause the MS to: A Routing Area Update RAU Request message is encoded for transmission to the SGSN in the GPRS, the RAU Request message including the MS Network Capability IE indicating whether the MS supports restrictions on using enhanced coverage. 20. The computer-readable storage medium of claim 19, wherein the one or more processors further cause the MS to: A Routing Area Update Accept message confirming the MS location update is decoded, the RAU Accept message also includes an additional network feature support IE indicating whether the MS is restricted from using enhanced coverage. 21. An apparatus for a Node BNB, the apparatus comprising: processing circuitry, configured as: decoding a configuration message from the mobility management entity MME, the configuration message comprising an enhanced coverage restriction information element IE, the enhanced coverage restriction IE indicating whether the use of enhanced coverage is restricted for the user equipment UE; creating a context for the UE based on the configuration message; and Forwards a downlink network access plane NAS accept message for sending to the UE based on the UE context, the NAS accept message including an EPS Network Feature Support IE indicating whether to restrict the UE to use of enhanced coverage; and A memory coupled to the processing circuit configured to store the enhanced coverage restriction IE. 22. The apparatus of claim 21, wherein the configuration message is an initial context setup request message. 23. The apparatus of any of claims 21-22, wherein the configuration message is a handover request message. 24. The apparatus of any of claims 21-22, wherein the configuration message is a downlink NAS transport message. 25. The apparatus of any of claims 21-22, wherein the processing circuit is further configured to: An uplink non-access stratum NAS message is encoded for transmission to the MME, the NAS message including a UE Network Capability Information Element IE indicating whether the UE supports restrictions on the use of enhanced coverage.

Images