Restricted access and usage control for user equipments with reduced capability

Abstract

Certain aspects of the present disclosure provide techniques for controlling user equipment access and use of network resources and services based on user equipment capabilities. In one aspect, a method for wireless communication by a network entity includes receiving, from a user equipment, a request to connect to a network, the request including a user equipment identifier and a reduced capability indication, determining a validity of the reduced capability indication based on at least one of: subscription data associated with the user equipment, or one or more capabilities associated with the user equipment, and making a connectivity decision based on the validity of the reduced capability indication.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Application No. 17 / 220,751 filed April 1, 2021, which claims benefit of and priority to U.S. Provisional Patent Application No. 63 / 007,049 filed April 8, 2020, the entire contents of which are incorporated herein by reference.

[0003] BACKGROUND

[0004] DISCLOSURE

[0005] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for controlling access and use of network resources and services by user equipment based on user equipment capabilities.

[0006] DESCRIPTION OF RELATED ART

[0007] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, etc. These wireless communication systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing the available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and others.

[0008] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. New radio (e.g., 5G NR) is an example of an emerging telecommunication standard. NR is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink (UL). To these ends, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0009] However, as the demand for mobile broadband access continues to increase, there exists a need for further improvements in NR and LTE technology. Preferably, these improvements should be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

[0010] SUMMARY

[0011] The systems, methods, and devices of the disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without intending to be limiting as to the scope of the disclosure as expressed by the appended claims, some features will now be discussed briefly. The detailed description, after considering this discussion, will assist in understanding how the described features of the disclosure provide advantages that include improved network control of access and use of its services for user equipment of different capabilities.

[0012] Aspects provide a method for wireless communications by a network entity, the method including receiving, from a user equipment, a request to connect to a network, the request including a user equipment identifier and a reduced capability indication; determining validity of the reduced capability indication based on at least one of: subscription data associated with the user equipment, or one or more capabilities associated with the user equipment; and making a connection decision based on the validity of the reduced capability indication.

[0013] Another aspect provides a method for wireless communications by a network entity, the method including receiving, from a user equipment, a request to connect to a network, the request including a user equipment identifier and a reduced capability indication; retrieving subscription data associated with the user equipment based on the user equipment identifier; initiating a capability matching procedure with the user equipment; determining one or more capabilities of the user equipment based on the capability matching procedure; and comparing the one or more capabilities to the subscription data to determine a result of the capability matching procedure, making a connection decision based on the result of the capability matching procedure.

[0014] Another aspect provides a method for performing wireless communications, the method including transmitting, to a network entity, a request to connect to a network, the request including a user equipment identifier and a reduced capability indication; receiving, from the network entity, a capability query; transmitting, to the network entity, one or more user equipment capabilities; and receiving, from the network entity, a connection decision.

[0015] Further aspects provide a non-transitory computer-readable medium including instructions that, when executed by one or more processors of a processing system, cause the processing system to perform the methods described above and those further described herein.

[0016] Further aspects provide a computer program product, embodied on a computer readable storage medium, comprising code for performing the methods described above and those further described herein.

[0017] Further aspects provide a processing system including means for performing the methods described above and those further described herein.

[0018] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects can be employed. BRIEF DESCRIPTION OF DRAWINGS

[0020] So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, can be had by reference to various aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description can admit to other equally effective aspects.

[0021] Figure 1 is a block diagram conceptually illustrating an example wireless communication network.

[0022] Figure 2 is a block diagram conceptually illustrating a design of an example base station and user equipment.

[0023] Figure 3 is an example frame format for certain wireless communication systems.

[0024] Figure 4 depicts an example architecture for an NR core network.

[0025] Figure 5A and Figure 5B is a flowchart illustrating an example operation for wireless communication.

[0026] Figure 6 depicts an example method for performing network communications.

[0027] Figure 7 depicts another example method for performing network communications.

[0028] Figure 8 depicts another example method for performing network communications.

[0029] Figure 9 depicts an example communications device that includes various components configured to perform operations for the techniques disclosed herein.

[0030] Figure 10 depicts another example communications device that includes various components configured to perform operations for the techniques disclosed herein.

[0031] To facilitate understanding, like reference numerals have been used, where possible, to designate like elements across the figures. It is contemplated that elements disclosed in one aspect can be beneficially utilized on other aspects without specific recitation.

[0032] DETAILED DESCRIPTION

[0033] Aspects of the disclosure provide apparatuses, methods, processing systems, and computer readable media for controlling access and use of network resources and services by user equipment based on user equipment capabilities.

[0034] The following description provides examples of controlling access and use of network resources and services by user equipment based on user equipment capabilities in a communication system and is not limiting of the scope, applicability, or examples set forth in the claims. Changes can be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples can omit, substitute, or add various procedures or components as appropriate. For instance, the methods described can be performed in an order different than that described, and various steps can be added, omitted, or combined. Also, features described with respect to some examples can be combined in some other examples. For example, an apparatus or a method can be implemented using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using an additional structure, functionality, or structure and functionality in addition to the aspects set forth herein. It should be understood that any aspect of the disclosure disclosed herein can be embodied by one or more elements of a claim. The language “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.

[0035] In general, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a particular radio access technology (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, an air interface, etc. A frequency can also be referred to as a carrier, a subcarrier, a frequency channel, a tone, a subband, etc. In some cases, a frequency can be a component of a spread spectrum signal. In some cases, a frequency can be a component of a single carrier signal. Each frequency can support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.

[0036] The techniques described herein can be used for various wireless networks and radio access technologies. While aspects can be described herein using terminology commonly associated with 3G, 4G, and / or new radio (e.g., 5G NR) wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems.

[0037] NR access can support various wireless communication services such as Enhanced Mobile Broadband (eMBB) that can target wide bandwidth (e.g., 80 MHz or beyond), Millimeter Wave (mmWave) that can target high carrier frequency (e.g., 24 GHz to 53 GHz or beyond), massive Machine Type Communications (MTC) that can target non-backward compatible MTC techniques with a large number of low-cost, low-complexity devices, and / or mission critical that can target ultra-reliable low-latency communications (URLLC). These services can include latency and reliability requirements. These services can also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements. In addition, these services can co-exist in the same subframe. NR supports beamforming and beam direction can be dynamically configured. MIMO transmissions with precoding can also be supported in NR. For example, a MIMO configuration in the DL can support up to 8 transmit antennas (multi-layer DL transmission with up to 8 streams) and up to 2 streams per UE. In addition, multi-layer transmissions with up to 2 streams per UE can be supported in NR. Further, up to 8 service cells can be supported in NR with carrier aggregation.

[0038] Figure 1 An example wireless communication network 100 in which aspects of the present disclosure can be performed is illustrated. For example, the wireless communication network 100 can be an NR system (e.g., a 5G NR network). As shown, the wireless communication network 100 can be in communication with a core network 132. The core network 132 can in communication with one or more base stations (BSs) 110 and / or user equipment (UE) 120 in the wireless communication network 100 via one or more interfaces. Figure 1

[0039] According to certain aspects, the BSs 110 and UEs 120 can be configured to verify capabilities of the UEs 120 and control network access and usage based on those capabilities. As Figure 1 shown, the BS 110a includes an access and usage manager 112 that is configured to verify capabilities of UEs and control network access and usage accordingly in accordance with aspects of the present disclosure, such as those described below with respect to Figure 5A , 5B , 6, and 7. The UE 120a includes a capability manager 122 that is configured to identify its capabilities to the network 100 in accordance with aspects of the present disclosure, such as those described below with respect to Figure 5A , 5B , and 8, so that the network 100 can control access and usage of network resources.

[0040] As Figure 1 ​As illustrated in the example of FIG. 1, wireless communication network 100 can include a number of BSs 110a-z (each also individually referred to herein as BS 110 or collectively as BSs 110) and other network entities. A BS 110 can provide communication coverage for a particular geographic area, which can be referred to as a “cell” (not shown) or a “bacterial cell,” that can be stationary or can move according to the location of a mobile BS 110. In some examples, BSs 110 can be interconnected to one another and / or to one or more other BSs or network nodes (not shown) in wireless communication network 100 through various types of backhaul interfaces (e.g., a direct physical connection, a wireless connection, a virtual network, or the like) using any suitable transport network. Figure 1 In the example shown in FIG. 1, BSs 110a, 110b, and 110c can be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x can be a pico BS for a pico cell 102x. BSs 110y and 110z can be femto BSs for femto cells 102y and 102z, respectively. A BS can be generally referred to as a BS, a base station, an access point, a radio transceiver, a NodeB, eNodeB, gNodeB (gNB), Home Base Station, or the like.

[0041] BSs 110 communicate with UEs 120a-y (each also individually referred to herein as UE 120 or collectively as UEs 120) in the wireless communication network 100. The UEs 120 (e.g., 120x, 120y, etc.) can be dispersed throughout the wireless communication network 100, and each UE 120 can be stationary or mobile. Wireless communication network 100 can also include relay stations (e.g., relay station 110r), also referred to as relays or the like, that receive a transmission of data and / or other information from an upstream station (e.g., a BS 110a or a UE 120r) and sends a transmission of the data and / or other information to a downstream station (e.g., a UE 120 or a BS 110), or that relays transmissions between UEs 120 to facilitate communication between devices.

[0042] A network controller 130 can be in communication with a set of BSs 110 and provide coordination and control for the BSs 110 (e.g., via the backhaul). In some aspects, the network controller 130 can be in communication with a core network 132 (e.g., a 5G core network (5GC)), which provides various network functions such as access and mobility management, session management, user plane function, policy control function, authentication server function, unified data management, application function, network exposure function, network repository function, network slice selection function, etc. (as described in more detail below with regard to FIG. 2). Figure 4 Further description of the network controller 130 is provided below.

[0043] Figure 2 BS 110a and UE 120a, illustrated in FIG. 1, can implement aspects of the present disclosure.Figure 1 Example components of a wireless communications system 100.

[0044] At BS 110a, a transmit processor 220 can receive data from a data source 212 and control information from a controller / processor 240. The control information can be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid ARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), etc. The data can be for the physical downlink shared channel (PDSCH), etc. A controller / processor 240 can determine an appropriate format for the control information and / or data and send information to the transmit processor 220.

[0045] A medium access control (MAC)-control element (MAC-CE) is a MAC layer communication structure that can be used for control command exchange between wireless nodes. A MAC-CE can be carried in a shared channel, such as a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), or a physical sidelink shared channel (PSSCH).

[0046] The processor 220 can process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 220 can also generate reference symbols, such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and / or the reference symbols, if applicable, and can provide output symbol streams to the modulators (MODs) 232a-232t. Each modulator 232 can process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators 232a-232t can be transmitted via the antennas 234a-234t, respectively.

[0047] At the UE 120a, the antennas 252a-252r can receive the downlink signals from the BS 110a and can provide received signals to the demodulators (DEMODs) 254a-254r, respectively, in the transceivers. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 can obtain received symbols from all the demodulators 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols to other aspects of the UE 120a. A receive processor 258 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE 120a to a data sink 260, and provide decoded control information to a controller / processor 280.

[0048] On the uplink, at the UE 120a, a transmit processor 264 can receive and process data (e.g., for the physical uplink shared channel (PUSCH)) from a data source 262 and control information (e.g., for the physical uplink control channel (PUCCH)) from the controller / processor 280. The transmit processor 264 can also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS)). The symbols from the transmit processor 264 can be precoded by a TX MIMO processor 266 if applicable, further processed by the modulators 254a-254r in the transceivers, and transmitted to the BS 110a. At the BS 110a, the uplink signals from the UE 120a can be received by the antennas 234, processed by the modulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120a. The receive processor 238 can provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240.

[0049] The memory 242 and 282 can store data and program codes for the BS 110a and the UE 120a, respectively. A scheduler 244 can schedule UEs for data transmission on the downlink and / or uplink.

[0050] The antennas 252, processors 266, 258, 264, and / or controller / processor 280 of the UE 120a, and / or the antennas 234, processors 220, 230, 238, and / or controller / processor 240 of the BS 110a can be used to perform the various techniques and methods described herein. For example, as described Figure 2As shown in FIG. 1, the controller / processor 240 of the BS 110a has an access and usage manager 241 configured to verify the capabilities of UEs and control network access and usage accordingly according to the aspects described herein, such as those described below with respect to Figure 5A , 5B , 6, and 7. As shown in FIG. 1, the controller / processor 280 of the UE 120a has a capability manager 281 that identifies its capabilities to the network (e.g., via the BS 110a) according to the aspects described herein, such as those described below with respect to Figure 2 , Figure 5A , 5B , and 8. Although shown at the controller / processor, other components of the UE 120a and the BS 110a can be used to perform the operations described herein.

[0051] NR can utilize orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) on the uplink and downlink. NR can support half-duplex operation using time division duplex (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth into multiple orthogonal subcarriers, which are also commonly referred to as tones, frequency bins, and the like. Each subcarrier can be modulated with data. Modulation symbols can be transmitted on the frequency domain with OFDM and on the time domain with SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers can be dependent on the system bandwidth. The minimum resource allocation, called a resource block (RB), can be 12 consecutive subcarriers. The system bandwidth can also be partitioned into subbands. For example, a subband can cover multiple RBs. NR can support a base subcarrier spacing (SCS) of 15 KHz and other SCS can be defined with respect to the base SCS (e.g., 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc.).

[0052] Figure 3is a diagram illustrating an example of a frame format 300 for NR. The transmission timeline for each of the downlink and uplink can be partitioned into units of radio frames. Each radio frame can have a predetermined duration (e.g., 10 milliseconds) and can be partitioned into 10 subframes of 1 millisecond each. Each subframe can include a variable number of time slots (e.g., 1, 2, 4, 8, 16,... time slots) depending on the SCS. Each time slot can include a variable number of symbol periods (e.g., 7, 12, or 14 symbol periods) depending on the SCS. Symbol periods in each slot can be assigned an index. A mini-slot (which can be referred to as a sub-slot) refers to a transmission time interval having a duration less than a slot (e.g., 2, 3, or 4 symbol periods). Each symbol period in a slot can indicate a link direction (e.g., DL, UL, or flexible) for data transmission and the link direction for each subframe can be dynamically switched. The link direction can be based on a slot format. Each slot can include DL / UL data as well as DL / UL control information.

[0053] In NR, synchronization signal blocks (SSBs) are transmitted. In certain aspects, SSBs can be transmitted in a burst, where each SSB in the burst corresponds to a different beam direction for UE-side beam management (e.g., including beam selection and / or beam refinement). An SSB includes a PSS, a SSS, and a two symbol PBCH. The SSBs can be transmitted in fixed slot positions, such as symbols 0-3 as shown in FIG. 3B. The PSS and SSS can be used by UEs to Figure 3 perform cell search and acquisition. The PSS can provide half-frame timing, and the SS can provide CP length and frame timing. The PSS and SSS can provide the cell identity. The PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frame, SS burst set periodicity, system frame number, etc. The SSBs can be organized into SS bursts to support beam sweeping. Further system information, such as remaining minimum system information (RMSI), system information blocks (SIBs), other system information (OSI), can be transmitted on a physical downlink shared channel (PDSCH) in certain subframes. The SSBs can be transmitted up to 64 times, for example, up to 64 different beam directions for mmWave. The multiple transmissions of the SSB are referred to as a SS burst set. The SSBs in a SS burst set can be transmitted in the same frequency region, while the SSBs in different SS bursts sets can be transmitted in different frequency regions.

[0054] In NR, a protocol and reference point are defined for each network function (NF). In comparison, in a 4G core network (e.g., an evolved packet core (EPC) network), a protocol and reference point are defined for each entity, such as a mobility management entity (MME), a serving gateway (S-GW), and a packet data network gateway (P-GW).

[0055] Figure 4 An example architecture for the NR core network 400 is described, which includes various example NFs and the connections between NFs.

[0056] In the depicted example, UE 402 is connected to a radio access network (RAN) or access network (AN) 404 and access and mobility functions (AMF) 406. In some respects, RAN refers to a base station that concurrently uses new radio access technologies (such as NR) and other technologies (such as evolved LTE), while AN may include a general base station that includes non-3GPP access (such as Wi-Fi).

[0057] exist Figure 4 In the example depicted, the NR core network 400 (e.g., the 5GC network) includes various NFs, including AMF 406, Session Management Function (SMF) 408, Policy Control Function (PCF) 410, Application Function (AF) 412, Authentication Server Function (AUSF) 414, User Plane Function (UPF) 416, and User Data Management (UDM) 418.

[0058] In some respects, AMF 406 provides UE-based authentication, authorization, mobility management, and related functions. For example, a UE using multiple access technologies (e.g., UE 402) can still be connected to a single AMF because the AMF is independent of those access technologies.

[0059] In some respects, SMF 408 is responsible for session management and assigning IP addresses to UEs (such as UE 402). It also selects and controls UPFs (e.g., 416) for data transmission. If a UE has multiple sessions, different SMFs can be assigned to each session to manage them individually and may provide different functionality per session.

[0060] In some respects, AF 412 provides information on packet flows to PCF 410, which is responsible for policy control to support Quality of Service (QoS). Based on this information, PCF 410 determines policies regarding mobility and session management to ensure the proper operation of AMF406 and SMF 408.

[0061] In some respects, AUSF 414 stores data used to authenticate UEs (e.g., 402), while UDM 418 stores subscription data for UEs (e.g., 402).

[0062] The subscription data for a UE can be a subscription profile associated with a subscriber (user) and can generally contain information about services applicable to the subscriber and / or the subscriber's UE. For example, the subscription data can include: one or more categories associated with the subscriber and / or the subscriber's UE; a list of allowed services for the subscriber and / or the subscriber's UE; information about allowed QoS for the subscriber and / or the subscriber's UE; subscription pricing information; location information related to service pricing; information related to usage monitoring for the subscriber and / or the subscriber's UE; priority levels for various multimedia services; a subscriber spending cap; a list of application service providers and their applications; and so on.

[0063] The subscription data can be used by the NFs of the network 400 to perform policy control based on the services offered by the operator of the network 400 to its subscribers (e.g., end users), and can be changed by the operator based on the individual operator's business model and commercial offerings.

[0064] In some aspects, the data network 420 is not part of the NR core network, but it provides various services to the core network, such as Internet access or operator services.

[0065] The NR core network (such as 400) can be configured to separate user plane and control plane. In the network 400, the user plane can generally carry user traffic and the control plane can generally carry signaling. In Figure 4 The UPF 416 is in the user plane, while other NFs (such as AMF 406, SMF 408, PCF 410, AF 412, AUSF 414, and UDM 418) are in the control plane. Separating the user plane and the control plane advantageously allows for individual scaling of each NF, as well as deployment of the UPF (e.g., 416) in a distributed manner from the control plane functions. For example, the UPF (e.g., 416) can be deployed very close to the UE (e.g., 402) to shorten the round-trip time between the UE (e.g., 402) and a data network (e.g., 420) for applications that require low latency.

[0066] Generally speaking, Figure 4 Each NF in the network 400 can be configured to interact directly with another NF, although intermediary functions can be used to route messages from one NF to another. In the control plane, the set of interactions between two NFs can be defined as a service, to enable reuse. The user plane supports interactions between different UPFs, such as forwarding operations.

[0067] Supporting reduced capability user equipment in a network

[0068] As networks become more capable and data services become more diverse, further segmentation and control of UE interaction with data networks based on UE capabilities is needed.

[0069] For example, a reduced capability NR UE (e.g., as compared to a regular NR UE) can have fewer antennas, a narrower bandwidth, and a longer processing timeline, and thus, can consume more radio resources (such as requiring transmission repetitions to ensure network coverage) than a full capability NR UE. As a result, network providers need to control access to network resources by reduced capability UEs to ensure overall network performance.

[0070] UE capabilities can be associated with or part of a profile data of a network subscriber, which can include subscription data defining network access and services available to the subscriber. In some cases, UE capability categories can be defined in network interoperability standards, such as those maintained by 3GPP, including specific categories for reduced capability UEs. Such categories can be based on various factors, such as intended use cases (e.g., wearable devices, cameras, sensors, loT, etc.), and based on radio capabilities of the UE (e.g., high performance, mid-range, low cost, etc.), and combinations of the two. In some cases, network operators can employ all or a subset of the categories defined by the standards, or define their own UE categories based on operational needs specific to their network environment and users. Notably, these are just a few examples, and many other examples are possible.

[0071] Unfortunately, various problems can arise when UEs of different capabilities interact with a network that is unable to verify the capabilities of these UEs.

[0072] For example, a misconfigured reduced capability UE can attempt to access network resources and services reserved for full capability UEs, which can waste limited network resources (e.g., air time) to the detriment of other UEs interacting with the network. As another example, an intentionally misconfigured (or intentionally compromised) UE can pretend to be a reduced capability UE in order to steal a lower-tier subscription plan while still consuming higher level network services reserved for a higher-tier subscription plan. Thus, techniques for verifying UE capabilities and controlling access to network services based on those capabilities are needed.

[0073] Various network control techniques that beneficially support network interoperability with UEs of different capabilities (e.g., full and reduced capability NR UEs) are described herein. The techniques described herein provide matching capabilities between network resources and UE capabilities, limiting network usage based on UE capabilities (e.g., based on defined sets of devices with similar capabilities), and limiting access to network resources based on UE capabilities. In some aspects, as further described below, matching capabilities can be implemented on the network side by confirming that a UE's capabilities match its subscription, and on the UE side by confirming that the network supports the UE's capabilities. Once matched, the verified capabilities of the UE can then generally be used to control access to the network and more specifically to control usage of the network.

[0074] Accordingly, the techniques described herein improve upon conventional network access and control schemes that either do not account for UE capabilities or rely solely on an indication of UE capabilities without verification to control access and usage. This improvement results in more efficient use of the limited resources of the radio access network, which in turn provides benefits of better network availability and faster data exchange with the network, among other benefits.

[0075] Example procedures for controlling access and usage of network resources based on UE capabilities

[0076] Figure 5A And 5B are flow diagrams that respectively illustrate example operations 500 and 550 for wireless communication, in accordance with certain aspects of the present disclosure.

[0077] In some aspects, the various operations 500 and 550 can be performed between a UE (such as the UE 120a in Figure 1 and 2 and a base station (such as the BS 110a in Figure 1 and 2 of the wireless communication network 100.

[0078] In some aspects, the operations performed by the UE 120 can be implemented as software components that are executed and run on one or more processors (e.g., controller / processor 280 of the UE 120). Further, the transmission and reception of signals by the UE 120 in Figure 2 may be enabled, for example, by one or more antennas (e.g., antennas 252 of the UE 120). In certain aspects, the transmission and / or reception of signals by the UE can be implemented via a bus interface of one or more processors (e.g., controller / processor 280) obtaining and / or outputting signals. Figure 2

[0079] ​In some respects, the operations performed by the BS 110 can be complementary to the operations performed by the UE, and can be implemented in one or more processors (e.g., Figure 2 The software components executed and running on the controller / processor 240. Furthermore, the signal transmission and reception performed by BS 110 in operations 500 and 550 can be, for example, by one or more antennas (e.g., Figure 2 The antenna 234) is used for implementation. In some aspects, signal transmission and / or reception by the BS can be achieved by obtaining and / or outputting signals via a bus interface of one or more processors (e.g., controller / processor 240).

[0080] exist Figure 5A and 5B In the middle, large arrows (e.g., 506) generally represent groups of signaling messages within a procedure between the UE and network elements (such as BS 110 and AMF 502), while thin arrows (e.g., 510) represent individual messages between the UE and network elements.

[0081] Specifically, go to Figure 5A Operation 500 begins with Operation 504, where UE 120 uses the Random Access Channel (RACH) procedure to initiate a session with BS 110 (e.g., a gB node). In some respects, BS110 can be as follows: Figure 4 An example of R(AN)404 (e.g., access network entity) in the database.

[0082] Operation 500 then proceeds to operation 506, where UE 120 initiates connection establishment procedures with BS 110, such as RRC connection procedures. During connection establishment, UE 120 transmits a registration request message to Access Management Function (AMF) (or alternatively, Security Anchor Function (SEAF)) 502 via a Direct Non-Access Stratum (NAS) message in operation 508.

[0083] In some aspects, the registration request message at Operation 508 includes the UE ID (e.g., Subscription Hidden Identifier (SUCI) or Service Temporary Mobile Subscriber Identity (S-TMSI)) and a reduced capability indication. In some aspects, the reduced capability indication may include information about the UE 120, such as physical capabilities (e.g., number of antennas), functional capabilities (e.g., operating bandwidth), and other capabilities.

[0084] Operation 500 can then optionally proceed to 510, where UE 120 begins the authentication procedure with AMF / SEAF 502.

[0085] Generally, there are various registration scenarios, such as initial registration, mobility registration update, and periodic registration update. In the initial registration scenario, the UE can provide its SUCI in the registration request (as in the steps above), which triggers authentication. In the mobility or periodic registration update scenario, the UE can provide the S-TMSI and authentication can not be needed. However, the network (e.g., AMF) can decide to run authentication in certain scenarios anyway, such as when the AMF is unable to locate the UE (security) context, or when the AMF decides to run a new authentication due to the UE being registered for a long time without authentication. Thus, operation 510 can be necessary for certain scenarios, and optional for others.

[0086] Operation 500 then proceeds to operation 512, where the reduced capability indication of the UE (provided in operation 508) is verified against the subscription data of the UE to determine the validity of the reduced capability indication of the UE. In some aspects, the subscription data associated with the UE 120 can be retrieved from another network function (such as the UDM 418 in FIG. 4) based on the UE ID provided in operation 508. Figure 4

[0087] For example, the allowable, required, or maximum capabilities defined in the subscription data can be compared against the capabilities provided by the UE 120 in the reduced capability indication. If the reduced capability indication information is consistent with the subscription, the subscription can be deemed verified (or valid) for the purpose of allowing the UE to connect to the network. On the other hand, if the reduced capability indication information is inconsistent with the subscription data, the subscription can be deemed unverified for the purpose of allowing the UE to connect to the network. In some aspects, the consistency with the subscription data can be determined based on an exact match of the indicated capabilities to the subscription capabilities or a match of a certain subset of the subscription capabilities.

[0088] Operation 500 then proceeds to operation 514, where the AMF / SEAF 502 provides a registration decision to the UE 120 and causes the BS 110 to complete a connection procedure (e.g., RRC connection procedure) or release the connection at operation 516.

[0089] In some aspects, the AMF / SEAF 502 can determine that the capabilities of the UE 120 do not match the subscription data, but can still allow the connection. However, in such scenarios, the AMF / SEAF 502 can downgrade the level of service or services available to the UE 120, e.g., to a preconfigured level of service by the network for such scenarios. For example, the default level of service can be a low-end level of service with limited usage restrictions.

[0090] ​In some aspects, when the AMF / SEAF 502 determines that the UE 120 is not allowed to connect to the network, it can send a rejection indication in, for example, the registration decision 514. In some aspects, the rejection indication can include a code corresponding to a particular rejection reason. Upon receiving the rejection indication, the UE 120 can determine the reason for not being allowed to access the network based on the rejection indication.

[0091] Figure 5B Optional operations 550 are depicted that can be performed as a supplement to (or in some cases as a replacement for) the operations 500 in Figure 5A Figure 5A Figure 5A The numbering of similar operations is the same as in Figure 5B and has the same meaning, while new operations in

[0092] In Figure 5B operations 550 begin with optional operation 552, in which the BS 110 broadcasts network information and the UE 120 receives the network information, such as within a system information broadcast (SIB) message.

[0093] In some aspects, the message broadcast message 552 can include information about whether the BS 110 supports reduced-capability UEs. In some cases, the information broadcast 552 can include information about whether particular types of reduced-capability UEs are supported. In some aspects, these categories can be based on a particular usage category, a UE capability, or a combination of the two. For example, the information broadcast 552 can include information that the BS 110 will allow connections from wearable devices (a usage category) with an operating bandwidth (a capability category) of at least 20 MHz.

[0094] In alternative aspects, the network can advertise access entities and access categories defined specifically for reduced-capability UEs in a unified access control procedure, and in such aspects, the information broadcast 552 can be part of the unified access control procedure.

[0095] Operations 550 then proceed to optional operation 554, in which the UE 120 can compare its capabilities to those of the network.

[0096] ​​In some aspects, UE 120 may compare its capabilities with the network based on information broadcast message 552. In other aspects, UE 120 may compare its capabilities with the network based on internal storage of network element information. For example, UE 120 may store a list of restricted access network elements (e.g., base stations, cells, etc.) based on its capabilities and network configuration. In some aspects, the list of restricted access network elements may be configured in UE 120 by the network, for example, in an RRC release message or another network message. In some aspects, the list of restricted access network elements may be separately configured by the network. Figure 1 and 2 Use the capability manager 122 or 281 for maintenance.

[0097] Operation 550 then proceeds to operation 504, as mentioned above. Figure 5A The RACH procedure is implemented as described.

[0098] Operation 550 then proceeds to operation 556, where the connection establishment procedure between UE 120 and BS 110 begins. In this respect, UE 120 may include the UE ID and reduced capability indication in the RRC connection establishment message. BS 110 may then receive this UE ID and reduced capability indication and forward it to AMF / SEAF 502 in a message such as the Initial UE Context Message. Thus, with Figure 5A Unlike in the example where UE 120 provides its UE ID and reduced capability indication directly to AMF / SEAF 502, in this example, BS 110 acts as an intermediary for this data.

[0099] Operation 550 then proceeds to operation 510, where AMF / SEAF 502 can optionally authenticate UE 120.

[0100] Operation 550 then proceeds to operation 512, where the reduced capability indication of UE 120 is verified against the subscription data of UE 120 (provided in operation 558), as mentioned above. Figure 5A Described.

[0101] Operation 550 then proceeds to the optional UE radio capability verification set of operation 560.

[0102] In some cases, verifying the reduced capability indication of UE 120 against its subscription in Operation 512 does not completely prevent compromised or misconfigured UEs from reporting incorrect indications. Or in other aspects, such as regarding... Figure 7In more detail, the network can not have received a reduced capability indication from the UE. Thus, in some aspects, the network can perform further procedures to verify that the radio capabilities of the UE 120 are consistent with the capabilities included in its reduced capability indication, which can be referred to as a capability matching procedure.

[0103] Operation 560 begins with operation 562, in which the AMF / SEAF 502 initiates an initial UE context procedure (without sending a NAS registration response), and then the BS 110 performs an access stratum (AS) security setup procedure with the UE 120 at operation 564.

[0104] Operation 560 then proceeds to operation 566, in which the AMF / SEAF 502 requests the BS 110 to perform a UE capability matching procedure. In some aspects, operation 566 includes sending the reduced capability indication received at operation 558 to the BS 110 at operation 566.

[0105] Operation 560 then proceeds to operation 568, in which the BS 110 can optionally perform a capability query procedure with the UE 120 to determine the radio capabilities of the UE 120 if they are not already available at the BS 110.

[0106] Operation 560 then proceeds to operation 570, in which the BS 110 compares the radio capabilities of the UE 120 to the capabilities included with the reduced capability indication of the UE 120 as provided in operation 558.

[0107] In some aspects, the OAM specifies a mapping between a list of radio capabilities and one or more categories of reduced capability UEs. This list can only need to include a subset of the UE radio capabilities.

[0108] Operation 560 then proceeds to operation 572, in which the BS 110 reports the results of the capability comparison back to the AMF / SEAF 502. Based on these results, the AMF / SEAF 502 sends a registration decision message to the UE 120 at operation 514, and then the BS 110 completes the connection or releases the connection with the UE 120 at operation 516.

[0109] In some aspects, the AMF / SEAF 502 can determine that the capabilities of the UE 120 do not match, but can still allow the connection. However, in such cases, the AMF / SEAF 502 can downgrade the level of service or services available to the UE 120 based on the determined capabilities during operation 560.

[0110] As in Figure 5AIn the registration decision 514, when AMF / SEAF 502 determines that UE 120 is not allowed to connect to the network, it may send a denial indication. In some aspects, the denial indication may include a code corresponding to a specific denial reason. Upon receiving the denial indication, UE 120 may determine the reason for not being allowed network access based on the denial indication.

[0111] In some cases ( Figure 5A and 5B (Not depicted in the text), UE 120 may not include a reduced capability indication during the connection establishment procedure, or the reduced capability indication may not be received by AMF / SEAF 502 for other reasons. In such cases, Operation 560 provides a method for verifying the capabilities of UE 120 without an explicit indication.

[0112] Example methods for controlling network access and usage based on UE capabilities

[0113] Figure 6 An example method 600 for wireless communication by a network entity is described. In some aspects, method 600 is performed by a network entity (such as...) Figure 1 The network entity (based on 100 base stations) performs this function. In some aspects, the network entity can implement multiple network functions, such as... Figure 4 As described in [the text]. In some respects, method 600 can be related to [the text]. Figure 5A and 5B All aspects described are executed consistently.

[0114] Method 600 begins in step 602, receiving a request from the user equipment to connect to the network, the request including a user equipment identifier and a degraded capability indication.

[0115] In some aspects of method 600, access network entities (such as...) Figure 1 and 2 Base station 110, or Figure 4 R(AN)404) in the process performs the action of receiving a request from the user equipment for connection to the network, including the user equipment identifier and a degraded capability indication.

[0116] Method 600 then proceeds to step 604, where the validity of the reduced capability indication is determined based on subscription data associated with the user equipment and / or one or more capabilities associated with the user equipment. In some aspects, the one or more capabilities include at least one radio capability of the user equipment.

[0117] In some respects, access and mobility network entities (such as Figure 4 The AMF 406 in the system performs the determination of the effectiveness of the reduced capability indication based on subscription data associated with the user equipment.

[0118] The method 600 then proceeds to step 606, where a connection decision is made based on the validity of the reduced capability indication.

[0119] In some aspects, an access and mobility network entity (such as the AMF 406 in Figure 4 makes the connection decision based on the validity of the reduced capability indication.

[0120] In some aspects of the method 600, the connection decision includes a decision to reject a request from the user equipment to connect to the network based on the reduced capability indication being inconsistent with subscription data or one or more capabilities associated with the user equipment, and the method further includes transmitting a connection reject message to the user equipment.

[0121] In some aspects of the method 600, the connection reject message includes a code defining a reason for the connection decision.

[0122] In some aspects of the method 600, the connection decision includes a decision to accept a request from the user equipment to connect to the network based on the reduced capability indication being consistent with subscription data associated with the user equipment, and the method further includes transmitting a connection accept message to the user equipment.

[0123] In some aspects, the method 600 further includes retrieving subscription data associated with the user equipment based on a user equipment identifier. In some aspects, an access and mobility network entity (such as the AMF 406 in Figure 4 retrieves the subscription data associated with the user equipment based on the user equipment identifier.

[0124] In some aspects of the method 600, the access and mobility network entity retrieves the subscription data from a user data management network entity (such as the UDM 418 in Figure 4 .

[0125] In some aspects of the method 600, the user equipment identifier and the reduced capability indication are received in a non-access stratum (NAS) registration request message.

[0126] In some aspects of the method 600, the NAS registration request is received by the access and mobility network entity directly from the user equipment, such as depicted in Figure 5A .

[0127] In some aspects of the method 600, the user equipment identifier and the reduced capability indication are received in a RRC connection setup message.

[0128] In some aspects of the method 600, the RRC connection setup message is received by the access and mobility network entity from an access network entity.

[0129] In some aspects of method 600, the reduced capability indication includes one or more UE radio capabilities.

[0130] In some aspects, method 600 further includes: initiating a capability matching procedure with the user equipment; determining one or more capabilities of the user equipment based on the capability matching procedure; and comparing the one or more capabilities with the degraded capability indication to determine the result of the capability matching procedure, wherein a connection decision is further based on the result of the capability matching procedure. In some aspects, the one or more capabilities are radio capabilities of the user equipment.

[0131] In some aspects of method 600, the access and mobility network entity performs an initiation of a capability matching procedure with the user equipment by sending a request to the access network entity for a capability matching procedure, including a capability reduction indication, and the access network entity performs a determination of one or more capabilities of the user equipment based on the capability matching procedure.

[0132] In some aspects, method 600 further includes broadcasting a System Information Broadcast (SIB) message, which includes instructions regarding network support for reduced-capacity user equipment.

[0133] It is worth noting that method 600 is only one example, and other examples with further or alternative steps for performing the various functions described herein are also possible.

[0134] Figure 7 Another method 700 for performing network communication is described. In some aspects, method 700 is performed by a network (such as...) Figure 1 The network (100) is executed. In some aspects, the network may include multiple network functions, such as in Figure 4 As depicted in the text.

[0135] Method 700 begins in step 702, receiving a request from the user equipment to connect to the network, wherein the request includes a user equipment identifier.

[0136] Method 700 then proceeds to step 704, where subscription data associated with the user equipment is retrieved based on the user equipment identifier.

[0137] Method 700 then proceeds to step 706, where a capability matching procedure with the user's equipment is initiated. In one aspect, the capability matching procedure is as described above regarding... Figure 5B As described in operation 560.

[0138] Method 700 then proceeds to step 708, where one or more capabilities of the user equipment are determined based on a capability matching procedure. In some respects, these one or more capabilities are the radio capabilities of the user equipment.

[0139] The method 700 then proceeds to step 710, where the one or more capabilities are compared to subscription data to determine a result of the capability matching procedure.

[0140] The method 700 then proceeds to step 712, where a connection decision is made based on the result of the capability matching procedure.

[0141] In some aspects of the method 700, the connection decision includes a decision to reject a request from the user equipment to connect to the network based on the determined one or more capabilities being inconsistent with subscription data associated with the user equipment, and the method further includes transmitting a connection reject message to the user equipment. In some aspects, the connection reject message includes a code defining a reason for the connection decision.

[0142] In some aspects of the method 700, the connection decision includes a decision to accept a request from the user equipment to connect to the network based on the determined one or more capabilities being consistent with subscription data associated with the user equipment, and the method further includes transmitting a connection accept message to the user equipment.

[0143] In some aspects of the method 700, an access network entity (such as a base station 110 in Figure 1 and 2 or a R(AN) 404 in Figure 4 receives, from a user equipment, a request to connect to a network including a user equipment identifier, and an access and mobility network entity (such as an AMF 406 in Figure 4 initiates a capability matching procedure with the user equipment, and makes a connection decision based on a validity of the reduced capability indication.

[0144] In some aspects of the method 700, the access and mobility network entity retrieves the subscription data from a user data management network entity.

[0145] Some aspects of the method 700 further include broadcasting a system information broadcast (SIB) message including an indication that the network supports reduced-capability user equipment.

[0146] Notably, the method 700 is just one example, and other examples with further or alternative steps for performing various functions described herein are also possible.

[0147] Figure 8 An example method 800 for performing network communications is depicted. In some aspects, the method 800 can be performed by a UE (such as a UE 120 of Figure 1 and 2 ).

[0148] The method 800 begins, at step 802, by transmitting, to a network entity, a request to connect to a network, the request including a user equipment identifier and a reduced capability indication.

[0149] The method 800 then proceeds to step 804, where a capability query is received from the network entity.

[0150] The method 800 then proceeds to step 806, where one or more user equipment capabilities are transmitted to the network entity.

[0151] The method 800 then proceeds to step 808, where a connection decision message is received from the network entity.

[0152] In some aspects, the connection decision can be a connection accept decision. In other aspects, the connection decision can be a connection reject decision. In such aspects, the connection decision can include a rejection indication (such as a code or other data) indicating a rejection reason (such as the capabilities not matching a subscription of the user equipment).

[0153] Some aspects of the method 800 further include receiving, from the network entity, a system information broadcast (SIB) message including an indication that the network entity supports reduced capacity user equipment.

[0154] Some aspects of the method 800 further include receiving a list of network entities that do not support reduced capacity user equipment, where the network entity is not on the list.

[0155] Notably, the method 800 is just one example, and other examples with further or alternative steps for performing various functions described herein are also possible.

[0156] Example Communication Device

[0157] Figure 9 An example communication device 900 is depicted that can include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in FIGS. 7-8. Figure 6 and 7 In some aspects, the communication device 900 is a network entity, such as a base station 110 in Figure 1 and 2

[0158] ​The communications device 900 includes a processing system 902 coupled to a transceiver 908 (e.g., a transmitter and / or a receiver). The transceiver 908 is configured to transmit and receive signals for the communications device 900 via an antenna 910, such as the various signals as described herein. The processing system 902 can be configured to perform processing functions for the communications device 900, including processing signals received and / or to be transmitted by the communications device 900.

[0159] The processing system 902 includes a processor 904 coupled to a computer- readable medium / memory 912 via a bus 906. In certain aspects, the computer-readable medium / memory 912 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 904, cause the processor 904 to perform Figure 6 and Figure 7 the operations illustrated in FIG. 13, or other operations for performing the various techniques discussed herein for controlling access and usage of network services for user equipment of different capabilities.

[0160] In certain aspects, the computer-readable medium / memory 912 stores code 914 for receiving, at a network, a request to connect to the network from a user equipment, the request including a user equipment identifier and a reduced capability indication; code 916 for retrieving subscription data associated with the user equipment based on the user equipment identifier; code 918 for determining a priority of the reduced capability indication based on the subscription data associated with the user equipment and / or one or more capabilities; and code 920 for making a connection decision based on a validity of the reduced capability indication.

[0161] In certain aspects, the processor 904 has circuitry configured to implement code stored in the computer-readable medium / memory 912, including circuitry 922 for receiving, at a network, a request to connect to the network from a user equipment, the request including a user equipment identifier and a reduced capability indication; circuitry 924 for retrieving subscription data associated with the user equipment based on the user equipment identifier; circuitry 926 for determining a priority of the reduced capability indication based on the subscription data associated with the user equipment and / or one or more capabilities; and circuitry 928 for making a connection decision based on a validity of the reduced capability indication.

[0162] Notably, Figure 9 is just one example, and other examples, with further circuitry and further code to perform various functions described herein, are also possible.

[0163] Figure 10 depicted as being implemented with three distinct components: an identifying component 1002, a determining component 1004, and a making component 1006. However, this depicted architecture is merely an example and Figure 8FIG. 10 is an example communications device 1000 including various components (e.g., corresponding to means-plus-function components) configured to perform the operations as explained in FIG. 9 (and other operations for performing the features described throughout this disclosure). In some aspects, the communications device 900 is a user equipment, such as a UE 120. Figure 1 and 2 the UE 120 in FIG. 1.

[0164] The communications device 1000 includes a processing system 1008 coupled to a transceiver 1002 (e.g., a transmitter and / or a receiver). The transceiver 1008 is configured to transmit and receive signals for the communications device 1000 via an antenna 1010, such as the various signals as described herein. The processing system 1002 can be configured to perform processing functions for the communications device 1000, including processing signals received and / or to be transmitted by the communications device 1000.

[0165] The processing system 1002 includes a processor 1004 coupled to a computer- readable medium / memory 1012 via a bus 1006. In certain aspects, the computer-readable medium / memory 1012 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 1004, cause the processor 1004 to perform Figure 8 the operations illustrated in FIG. 9, or other operations for performing the various techniques discussed herein for controlling access and usage of network services for user equipment of different capabilities.

[0166] In certain aspects, the computer-readable medium / memory 1012 stores code 1014 for transmitting, to a network entity, a request to connect to a network, the request including a user equipment identifier and a reduced capability indication; code 1016 for receiving, from the network entity, a capability query; code 1016 for transmitting, to the network entity, one or more user equipment capabilities; and code 1020 for receiving, from the network entity, a connection decision.

[0167] In certain aspects, the processor 1004 has circuitry configured to implement code stored in the computer-readable medium / memory 1012, including circuitry 1022 for transmitting, to a network entity, a request to connect to a network, the request including a user equipment identifier and a reduced capability indication; circuitry 1024 for receiving, from the network entity, a capability query; circuitry 1026 for transmitting, to the network entity, one or more user equipment capabilities; and circuitry 1028 for receiving, from the network entity, a connection decision.

[0168] Notably, Figure 10 is just one example and other examples, with further circuitry and further code configured to perform various functions described herein, are also possible.

[0169] Example Clauses

[0170] Implementation examples are described in the following numbered clauses.

[0171] Clause 1: A method for wireless communications by a network entity, comprising: receiving, from a user equipment, a request to connect to a network, the request including a user equipment identifier and a reduced capability indication; determining validity of the reduced capability indication based on at least one of: subscription data associated with the user equipment, or one or more capabilities associated with the user equipment; and making a connection decision based on the validity of the reduced capability indication.

[0172] Clause 2: The method of clause 1, wherein: the connection decision includes a decision to reject the request from the user equipment to connect to the network based on the reduced capability indication being inconsistent with the subscription data or the one or more capabilities associated with the user equipment, and the method further comprises: transmitting a connection reject message to the user equipment.

[0173] Clause 3: The method of clause 2, wherein the connection reject message includes a code defining a reason for the connection decision.

[0174] Clause 4: The method of any of clauses 1-3, wherein: the connection decision includes a decision to accept the request from the user equipment to connect to the network based on the reduced capability indication being consistent with the subscription data associated with the user equipment, and the method further comprises: transmitting a connection accept message to the user equipment.

[0175] Clause 5: The method of any of clauses 1-4, further comprising: retrieving subscription data associated with the user equipment based on the user equipment identifier;

[0176] Clause 6: The method of clause 1, wherein determining the validity of the reduced capability indication is based on the subscription data and includes comparing capabilities defined in the subscription data associated with the user equipment with one or more capabilities associated with the received reduced capability indication.

[0177] Clause 7: The method of any of clauses 1-6, wherein receiving, at the network, the request from the user equipment to connect to the network, the request including the user equipment identifier and the reduced capability indication, comprises: receiving the user equipment identifier and the reduced capability indication in a non-access stratum (NAS) registration request message.

[0178] Clause 8: The method of clause 7, wherein receiving, at the network, the request from the user equipment to connect to the network, the request including the user equipment identifier and the reduced capability indication, comprises: receiving the NAS registration request directly from the user equipment at an access and mobility network entity.

[0179] Clause 9: The method of any of clauses 1-8, wherein receiving, at the network, the request from the user equipment to connect to the network, the request including the user equipment identifier and the reduced capability indication, comprises receiving the user equipment identifier and the reduced capability indication in a radio resource control (RRC) connection setup message.

[0180] Clause 10: The method of clause 9, wherein receiving, at the network, the request from the user equipment to connect to the network, the request including the user equipment identifier and the reduced capability indication, comprises receiving the RRC connection setup message at an access and mobility network entity from an access network entity.

[0181] Clause 11: The method of any of clauses 1-10, wherein the reduced capability indication includes the one or more capabilities.

[0182] Clause 12: The method of any of clauses 1-11, further comprising initiating a capability matching procedure with the user equipment; determining the one or more capabilities of the user equipment based on the capability matching procedure; and comparing the one or more capabilities to the reduced capability indication to determine a result of the capability matching procedure, wherein the connection decision is further based on the result of the capability matching procedure.

[0183] Clause 13: The method of clause 12, wherein the one or more capabilities of the user equipment include at least one radio capability of the user equipment.

[0184] Clause 14: The method of any of clauses 1-15, further comprising broadcasting a system information broadcast (SIB) message, the SIB message including an indication that the network supports reduced capacity user equipment.

[0185] Clause 15: A method for wireless communications by a network entity, comprising: receiving, from a user equipment, a request to connect to a network, the request including a user equipment identifier and a reduced capability indication; retrieving subscription data associated with the user equipment based on the user equipment identifier; initiating a capability matching procedure with the user equipment; determining one or more capabilities of the user equipment based on the capability matching procedure; comparing the one or more capabilities to the subscription data to determine a result of the capability matching procedure; and making a connection decision based on the result of the capability matching procedure.

[0186] Clause 16: The method of clause 15, wherein: the connection decision comprises a decision to reject the request from the user equipment to connect to the network based on the determined one or more capabilities being inconsistent with subscription data associated with the user equipment, and the method further comprises transmitting a connection reject message to the user equipment.

[0187] Clause 17: The method of clause 16, wherein the connection reject message includes a code defining a reason for the connection decision.

[0188] Clause 18: The method of any of clauses 15-17, wherein: the connection decision comprises a decision to accept the request from the user equipment to connect to the network based on the determined one or more capabilities being consistent with subscription data associated with the user equipment, and the method further comprises: transmitting a connection accept message to the user equipment.

[0189] Clause 19: The method of any of clauses 15-18, wherein: an access network entity performs receiving, from the user equipment, the request to connect to the network including the user equipment identifier, and an access and mobility network entity performs: retrieving subscription data associated with the user equipment based on the user equipment identifier; initiating a capability matching procedure with the user equipment; and making the connection decision based on a result of the capability matching procedure.

[0190] Clause 20: The method of clause 19, wherein the access and mobility network entity retrieves the subscription data from a user data management network entity.

[0191] Clause 21: The method of any of clauses 15-20, further comprising: broadcasting a system information broadcast (SIB) message including an indication that the network supports reduced-capability user equipment.

[0192] Clause 22: A method for performing wireless communication, comprising: transmitting, to a network entity, a request to connect to a network, the request including a user equipment identifier and a reduced-capability indication; receiving, from the network entity, a capability query; transmitting, to the network entity, one or more user equipment capabilities; and receiving, from the network entity, a connection decision.

[0193] Clause 23: The method of clause 22, further comprising: receiving, from the network entity, a system information broadcast (SIB) message including an indication that the network entity supports reduced-capability user equipment.

[0194] Clause 24: The method of any of clauses 22-23, further comprising: receiving a list of network entities that do not support reduced-capability user equipment, wherein the network entity is not on the list.

[0195] Clause 25: A processing system comprising: a memory comprising computer-executable instructions; and one or more processors configured to execute the computer-executable instructions and cause the processing system to perform the method of any of clauses 1-24.

[0196] Clause 26: A processing system comprising means for performing the method of any of clauses 1-24.

[0197] Clause 27: A non-transitory computer-readable medium comprising computer-executable instructions that, when executed by one or more processors of a processing system, cause the processing system to perform the method of any of clauses 1-24.

[0198] Clause 28: A computer program product embodied on a computer-readable storage medium comprising code for performing the method of any of clauses 1-24.

[0199] Additional Considerations

[0200] The techniques described herein can be used for various wireless communication technologies, such as NR (e.g., 5G NR), 3GPP Long Term Evolution (LTE), LTE-Advanced (LTE-A), code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), time division synchronous code division multiple access (TD-SCDMA), and other networks. The terms “network” and “system” are often used interchangeably. A CDMA network can implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, and so on. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95, and IS-856 standards. A TDMA network can implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network can implement a radio technology such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash- OFDMA, and so on. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). LTE and LTE-A are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). cdma2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). NR is an emerging wireless communications technology.

[0201] In 3GPP, the term "cell" can refer to a coverage area of a Node B (NB) and / or a NB subsystem serving this coverage area, depending on the context in which the term is used. In NR systems, the term “cell” and BS, next generation Node B (gNB or gNodeB), access point (AP), Distributed Unit (DU), carrier, or Transmission Reception Point (TRP) can be used interchangeably. A BS can provide communication coverage for a macro cell, a pico cell, a femto cell, and / or other types of cell. A macro cell can cover a relatively large geographic area (e.g., several kilometers in radius) and can allow unrestricted access by UEs with service subscriptions. A pico cell can cover a relatively small geographic area (e.g., a city neighborhood or a college campus) and can allow unrestricted access by UEs with service subscriptions. A femto cell can cover a relatively small geographic area (e.g., a home) and can allow restricted access by UEs with service subscriptions, e.g., UEs in an closed subscriber group (CSG) or UEs with an association to the femto cell. A BS for a macro cell can be referred to as a macro BS. A BS for a pico cell can be referred to as a pico BS. A BS for a femto cell can be referred to as a femto BS or a home BS.

[0202] A UE can also be known as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a Customer Premises Equipment (CPE), a cellular phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, an electric appliance, a medical device or medical equipment, a biometric sensor / device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet, etc.), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium. Some UEs can be considered machine-type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that can communicate with a BS, another device (e.g., remote device), or some other entity. A wireless node can provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs can be considered Internet-of-Things (IoT) devices, which can be Narrowband IoT (NB-IoT) devices.

[0203] In some examples, access to the air interface can be scheduled. A scheduling entity (e.g., a BS) allocates resources for communication among some or all of the devices and equipment within its serving area or cell. The scheduling entity can be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity. A base station is not the only entity that can function as a scheduling entity. In some examples, a UE can function as a scheduling entity and can schedule resources for one or more subordinate entities (e.g., one or more other UEs), and the other UEs can utilize the resources scheduled by the UE. In some examples, a UE can act as a scheduling entity in a peer-to-peer (P2P) network and / or in a mesh network. In a mesh networking example, UEs can communicate directly with one another, such as using a proscribed set of resources.

[0204] The methods disclosed herein comprise one or more steps or actions for achieving the methods. The method steps and / or actions can be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order is specified, the order or sequence of any step or action can be modified without departing from the scope of the claims.

[0205] As used herein, the phrase “at least one of” followed by a listing of two or more items means any one of those items can be present or any combination of those items can be present. For example, “at least one of a, b, and c” means that only a can be present, or only b, or only c, or a combination thereof. For example, “at least one of a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any of the individual members of the set.

[0206] As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” can include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “determining” can include resolving, selecting, choosing, establishing and the like.

[0207] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more." Unless specifically stated otherwise, the term "some" refers to one or more. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that enable a person skilled in the art to practice the disclosure, are

[0208] Various operations described above may be performed by any suitable means capable of performing the corresponding functions. The means can include various hardware and / or software component(s) and / or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor. Generally, where there are operations illustrated in figures, those operations can have corresponding counterpart means-plus-function components with similar numbering.

[0209] The various illustrative logical blocks, modules, and circuits described in connection with the disclosure can be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any commercially available processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0210] If implemented in hardware, an example hardware configuration can include a processing system in a wireless node. The processing system can be implemented with a bus architecture. The bus can include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints. The bus can link together various circuits such as a processor, machine-readable medium, and buses. A bus interface can be used to connect a network adapter to the processing system via the bus. The network adapter can be used to implement signal processing functionality for the PHY layer. The network adapter can be used to implement signal processing functionality for the PHY layer. The processor can be implemented with one or more general-purpose and / or special- purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how to best implement the functionality described above with respect to the processing system depending on the particular application and the overall design constraints imposed on the overall system.

[0211] If implemented in software, the functions can be stored or transmitted over as one or more instructions or code on a computer-readable medium. Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The processor can be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage media. A computer-readable storage medium can be coupled with the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. By way of example, the machine-readable media can include a transmission line, a carrier wave modulated by data, and / or a computer readable storage medium for storing software, all of which are within the scope of the present disclosure. Additionally or alternatively, the machine-readable media can include a storage medium implemented using one or more of a semiconductor-based or other integrated circuit (IC) (e.g., a general purpose IC and / or an application specific IC (ASIC)), a programmable logic device (PLD), a memory device (e.g., a computer-readable storage medium), and / or a radio frequency communication module. In implementation, the machine-readable media can take the form of any suitable type of hardware that is capable of storing or communicating software.

[0212] Software modules may comprise a single instruction or a number of instructions, and may be distributed across several different code segments, across different programs, and across multiple storage media. Computer-readable media may include several software modules. These software modules include instructions that, when executed by an instrument (such as a processor), enable the processing system to perform various functions. These software modules may include transfer modules and receive modules. Each software module may reside in a single storage device or be distributed across multiple storage devices. As an example, when a trigger event occurs, a software module may be loaded from a hard drive into RAM. During the execution of a software module, the processor may load some instructions into a cache to improve access speed. One or more cache lines may subsequently be loaded into a general-purpose register file for processor execution. In the context of the functionality of a software module described below, it will be understood that such functionality is implemented by the processor when the processor executes the instructions from that software module.

[0213] Similarly, any connection is also legitimately referred to as computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared (IR), radio, and microwave), then that coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of medium. As used herein, disks and discs include compact discs (CDs), laser discs, optical discs, digital multi-purpose discs (DVDs), floppy disks, and... Disks, where disks often magnetically reproduce data, and discs optically reproduce data using lasers. Therefore, in some aspects, computer-readable media may include non-transient computer-readable media (e.g., tangible media). Additionally, in other aspects, computer-readable media may include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0214] Therefore, certain aspects may include computer program products for performing the operations described herein. For example, such computer program products may include computer-readable media on which instructions are stored (and / or encoded) that can be executed by one or more processors to perform the operations described herein, such as those for performing the operations described herein and in... Figure 5A , 5B The instructions for the operations explained in sections 6, 7, and 8.

[0215] Further, it should be appreciated that modules and / or other appropriate means for performing the methods and techniques described herein can be downloaded and / or otherwise obtained by a user terminal and / or base station as applicable. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, various methods described herein can be provided via a storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.), such that a user terminal and / or base station can obtain the various methods upon coupling or providing the storage means to the device.

[0216] It will be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes, and adaptations will be apparent to others skilled in the art with the benefit of this disclosure. The scope of the claims should be determined by the appropriate scope of the following claims.

Claims

1. A method for wireless communications by a network entity, comprising: receiving, from a user equipment, a request to connect to a network, the request comprising a user equipment identifier and a reduced capability indication; determining validity of the reduced capability indication based on at least one of: subscription data associated with the user equipment; or one or more capabilities associated with the user equipment; and making a connection decision based on the validity of the reduced capability indication, wherein the connection decision comprises a decision to reject the request from the user equipment to connect to the network when the reduced capability indication is inconsistent with the subscription data or the one or more capabilities associated with the user equipment; and transmitting a connection reject message to the user equipment when the connection decision comprises the decision to reject the request from the user equipment to connect to the network.

2. The method of claim 1, wherein, the connection reject message comprises a code defining a cause of the connection decision.

3. The method of claim 1, wherein: the connection decision comprises a decision to accept the request from the user equipment to connect to the network when the reduced capability indication is consistent with the subscription data associated with the user equipment, and the method further comprises transmitting a connection accept message to the user equipment when the connection decision comprises the decision to accept the request from the user equipment to connect to the network.

4. The method of claim 1, further comprising: retrieving subscription data associated with the user equipment based on the user equipment identifier.

5. The method of claim 1, wherein, determining the validity of the reduced capability indication is based on the subscription data and comprises comparing capabilities defined in the subscription data associated with the user equipment with one or more capabilities associated with the received reduced capability indication.

6. The method of claim 1, wherein, receiving, at the network, the request from the user equipment to connect to the network, the request comprising the user equipment identifier and the reduced capability indication, comprises receiving the user equipment identifier and the reduced capability indication in a non-access stratum (NAS) registration request message.

7. The method of claim 6, wherein, receiving, at the network, the request from the user equipment to connect to the network, the request comprising the user equipment identifier and the reduced capability indication, comprises receiving the NAS registration request directly from the user equipment at an access and mobility network entity.

8. The method of claim 1, wherein, receiving, at the network, the request from the user equipment to connect to the network, the request comprising the user equipment identifier and the reduced capability indication, comprises receiving the user equipment identifier and the reduced capability indication in a radio resource control (RRC) connection setup message.

9. The method of claim 8, wherein, receiving, at the network, the request from the user equipment to connect to the network, the request comprising the user equipment identifier and the reduced capability indication, comprises receiving the RRC connection setup message from an access network entity at an access and mobility network entity.

10. The method of claim 1, wherein, the reduced capability indication comprises the one or more capabilities.

11. The method of claim 1, further comprising: initiating a capability match procedure with the user equipment; determining the one or more capabilities of the user equipment based on the capability matching procedure; and comparing the one or more capabilities to the reduced capability indication to determine a result of the capability matching procedure, wherein the connection decision is further based on the result of the capability matching procedure.

12. The method of claim 11, wherein, The one or more capabilities of the user equipment include at least one radio capability of the user equipment.

13. The method of claim 1, further comprising: broadcasting a system information broadcast (SIB) message, the SIB message including an indication that the network supports reduced capability user equipment.

14. A network entity comprising: memory including computer-executable instructions; and one or more processors configured to execute the computer-executable instructions and cause the network entity to: receive, from a user equipment, a request to connect to a network, the request including a user equipment identifier and a reduced capability indication; determine a validity of the reduced capability indication based on at least one of: subscription data associated with the user equipment; or one or more capabilities associated with the user equipment; and make a connection decision based on the validity of the reduced capability indication, wherein the connection decision includes a decision to reject the request from the user equipment to connect to the network when the reduced capability indication is inconsistent with the subscription data or the one or more capabilities associated with the user equipment; and transmit, to the user equipment, a connection reject message when the connection decision includes the decision to reject the request from the user equipment to connect to the network.

15. The network entity of claim 14, wherein, The connection reject message includes a code defining a cause of the connection decision.

16. The network entity of claim 14, wherein: the connection decision includes a decision to accept the request from the user equipment to connect to the network when the reduced capability indication is consistent with the subscription data associated with the user equipment, and the one or more processors are further configured to cause the network entity to transmit, to the user equipment, a connection accept message when the connection decision includes the decision to accept the request from the user equipment to connect to the network.

17. The network entity of claim 14, wherein, The one or more processors are further configured to cause the network entity to retrieve subscription data associated with the user equipment based on the user equipment identifier.

18. The network entity of claim 14, wherein, To determine the validity of the reduced capability indication based on the subscription data, the one or more processors are further configured to cause the network entity to compare capabilities defined in the subscription data associated with the user equipment to one or more capabilities associated with the received reduced capability indication.

19. The network entity of claim 14, wherein, To receive, at the network, the request from the user equipment to connect to the network, the request including the user equipment identifier and the reduced capability indication, the one or more processors are further configured to cause the network entity to receive the user equipment identifier and the reduced capability indication in a non-access stratum (NAS) registration request message.

20. The network entity of claim 19, wherein, To receive, at the network, the request from the user equipment to connect to the network, the request including the user equipment identifier and the reduced capability indication, the one or more processors are further configured to cause the network entity to receive the NAS registration request directly from the user equipment at an access and mobility network entity.

21. The network entity of claim 14, wherein, To receive, at the network, the request from the user equipment to connect to the network, the request including the user equipment identifier and the reduced capability indication, the one or more processors are further configured to cause the network entity to receive the user equipment identifier and the reduced capability indication in a radio resource control (RRC) connection setup message.

22. The network entity of claim 21, wherein, To receive, at the network, the request from the user equipment to connect to the network, the request including the user equipment identifier and the reduced capability indication, the one or more processors are further configured to cause the network entity to receive the RRC connection setup message from an access network entity at an access and mobility network entity.

23. The network entity of claim 14, wherein, The reduced capability indication includes the one or more capabilities.

24. The network entity of claim 14, wherein: the one or more processors are further configured to cause the network entity to: initiate a capability match procedure with the user equipment; determine the one or more capabilities of the user equipment based on the capability match procedure; and compare the one or more capabilities to the reduced capability indication to determine a result of the capability match procedure, and the connection decision is further based on the result of the capability match procedure.

25. The network entity of claim 24, wherein, The one or more capabilities of the user equipment include at least one radio capability of the user equipment.

26. The network entity of claim 14, wherein, The one or more processors are further configured to cause the network entity to broadcast a system information broadcast (SIB) message, the SIB message including an indication that the network supports reduced capacity user equipment.

27. A non-transitory computer-readable medium comprising computer-executable instructions that, when executed by one or more processors of a network entity, cause the network entity to perform a method comprising: receiving, from a user equipment, a request to connect to a network, the request including a user equipment identifier and a reduced capability indication; determining a validity of the reduced capability indication based on at least one of: subscription data associated with the user equipment; or one or more capabilities associated with the user equipment; and making a connection decision based on the validity of the reduced capability indication, wherein the connection decision includes a decision to reject the request from the user equipment to connect to the network when the reduced capability indication is inconsistent with the subscription data or the one or more capabilities associated with the user equipment; and transmitting a connection reject message to the user equipment when the connection decision includes the decision to reject the request from the user equipment to connect to the network.

28. A network entity comprising: Apparatus for receiving, from a user equipment, a request to connect to a network, the request comprising a user equipment identifier and a reduced capability indication; Apparatus for determining validity of the reduced capability indication based on at least one of: subscription data associated with the user equipment; or one or more capabilities associated with the user equipment; and Apparatus for making a connection decision based on the validity of the reduced capability indication, wherein the connection decision comprises a decision to reject the request from the user equipment to connect to the network when the reduced capability indication is inconsistent with the subscription data or the one or more capabilities associated with the user equipment; and Apparatus for transmitting, to the user equipment, a connection reject message when the connection decision comprises the decision to reject the request from the user equipment to connect to the network. The connection reject message comprises a code defining a cause of the connection decision.

29. The network entity of claim 28, wherein, 30. The network entity of claim 28, wherein: the connection decision comprises a decision to accept the request from the user equipment to connect to the network when the reduced capability indication is consistent with the subscription data associated with the user equipment, and the network entity further comprises apparatus for transmitting, to the user equipment, a connection accept message when the connection decision comprises the decision to accept the request from the user equipment to connect to the network. Apparatus for retrieving subscription data associated with the user equipment based on the user equipment identifier.

31. The network entity of claim 28, further comprising: Apparatus for determining validity of the reduced capability indication based on the subscription data and comprising apparatus for comparing capabilities defined in the subscription data associated with the user equipment with one or more capabilities associated with the received reduced capability indication.

32. The network entity of claim 28, further comprising: Apparatus for receiving, at the network, the request from the user equipment to connect to the network, the request comprising the user equipment identifier and the reduced capability indication, comprises apparatus for receiving the user equipment identifier and the reduced capability indication in a non-access stratum (NAS) registration request message.

33. The network entity of claim 28, further comprising: Apparatus for receiving, at the network, the request from the user equipment to connect to the network, the request comprising the user equipment identifier and the reduced capability indication, comprises apparatus for receiving the NAS registration request directly from the user equipment at an access and mobility network entity.

34. The network entity of claim 33, further comprising: Apparatus for receiving, at the network, the request from the user equipment to connect to the network, the request comprising the user equipment identifier and the reduced capability indication, comprises apparatus for receiving the user equipment identifier and the reduced capability indication in a radio resource control (RRC) connection setup message.

35. The network entity of claim 28, further comprising: ​ 36. The network entity of claim 35, further comprising: means for receiving, at the network, from the user equipment, a request to connect to the network, the request comprising the user equipment identifier and the reduced capability indication, comprising: means for receiving, at an access and mobility network entity, the RRC connection setup message from an access network entity.

37. The network entity of claim 28, wherein, The reduced capability indication comprises the one or more capabilities.

38. The network entity of claim 28, further comprising: means for initiating a capability matching procedure with the user equipment; means for determining the one or more capabilities of the user equipment based on the capability matching procedure; and means for comparing the one or more capabilities to the reduced capability indication to determine a result of the capability matching procedure, wherein the connection decision is further based on the result of the capability matching procedure.

39. The network entity of claim 28, wherein, The one or more capabilities of the user equipment comprise at least one radio capability of the user equipment.

40. The network entity of claim 28, further comprising: means for broadcasting a system information broadcast (SIB) message, the SIB message comprising an indication that the network supports reduced capacity user equipment.

Images