Apparatus and method in a radio communications network

Abstract

A method for handling user equipment, UE, access to a radio communications network performed by an apparatus is provided. The UE is using a reduced capability. The reduced capability relates to a reduced capability for communication in the radio communications network. The apparatus obtains (302) information about a user profile of the UE. The apparatus determines (303), based on the obtained information about the user profile of the UE, whether the UE is authorized to access the radio communications network by using the reduced capability when the UE is using the reduced capability to access the radio communications network.

Description

Technical Field

[0001] The embodiments described herein relate to apparatus and methods therein. In some aspects, they relate to processing user equipment (UE) access to a radio communication network. Background Technology

[0002] In a typical wireless communication network, wireless devices (also referred to as wireless communication devices, mobile stations, stations (STAs), and / or user equipment (UEs)) communicate with one or more core networks (CNs) via a local area network (LAN) (e.g., a Wi-Fi network) or a radio access network (RAN). RAN coverage is divided into geographical areas of service area or cell area (which may also be referred to as a beam or beam group), each of which is served by a radio network node (e.g., a radio access node, such as a Wi-Fi access point or radio base station (RBS)). In some networks, this radio network node may also be represented as, for example, a NodeB, an eNodeB (eNB), or, as in 5G, a gNB. A service area or cell area is a geographical area for which radio coverage is provided by a radio network node. Radio network nodes communicate with wireless devices within their range via an air interface operating on radio frequency.

[0003] The specifications for Evolved Packet System (EPS) (also known as fourth-generation (4G) networks) have been finalized within the 3rd Generation Partnership Project (3GPP), and this work continues in upcoming 3GPP releases, such as those specifying fifth-generation (5G) networks (also known as 5G New Radio (NR)). EPS comprises Evolved Universal Terrestrial Radio Access Network (E-UTRAN) (also known as Long Term Evolution (LTE) Radio Access Network) and Evolved Packet Core (EPC) (also known as System Architecture Evolution (SAE) Core Network). E-UTRAN / LTE is a variant of the 3GPP Radio Access Network where radio network nodes are directly connected to the EPC core network instead of the RNC used in 3G networks. Generally, in E-UTRAN / LTE, the functionality of the 3G RNC is distributed between the radio network nodes (e.g., eNodeBs in LTE) and the core network. Therefore, the RAN of EPS has a essentially "flat" architecture, consisting of radio network nodes that are directly connected to one or more core networks, i.e., they are not connected to an RNC. To compensate for this, the E-UTRAN specification defines a direct interface between radio network nodes, which is referred to as the X2 interface.

[0004] Multi-antenna technology can significantly improve the data rate and reliability of wireless communication systems. Performance is particularly enhanced when both the transmitter and receiver are equipped with multiple antennas (creating a multiple-input multiple-output (MIMO) communication channel). Such systems and / or related technologies are commonly referred to as MIMO.

[0005] As mentioned above, 5G is the fifth generation of cellular technology and was introduced in Release 15 of the 3GPP standard. It aims to improve speed, reduce latency, and enhance the flexibility of wireless services. The 5G system (5GS) comprises both a new radio access network (NG-RAN) (which utilizes a new air interface known as New Radio (NR)) and a new core network (5GC).

[0006] In 3GPP Release 17, a new UE type was introduced for NR. This new type of UE is a UE with reduced capabilities, designed for applications with low to medium performance requirements, such as wearable devices and industrial sensors.

[0007] NG-RAN Architecture Overview

[0008] Similar to E-UTRAN in 4G, NG-RAN uses a flat architecture and includes base stations called gNBs, which interconnect with each other via the Xn interface. The gNBs are also connected to the 5GC via the NG interface, more specifically, to the Access and Mobility Management Functions (AMF) via the NG-C interface, and to the User Plane Functions (UPF) via the NG-U interface. The gNBs, in turn, provide radio access to the UEs; the coverage of the gNBs effectively forms “cells” of radio coverage. The radio access technology (called New Radio (NR)) is based on Orthogonal Frequency Division Multiplexing (OFDM) (similar to LTE) and provides high data transmission speeds and low latency. Note that NR is sometimes used to refer to the entire 5G system, although strictly speaking it refers only to the 5G radio access technology.

[0009] NR is expected to be rolled out gradually over legacy LTE networks, starting in areas with high data traffic. This means NR coverage will be limited initially, and users will have to move between NR and LTE to enter and leave NR coverage. To support rapid mobility between NR and LTE and avoid changes to the core network, LTE eNBs will also connect to the 5GC and support the Xn interface. eNBs connected to the 5GC are called next-generation eNBs (ng-eNBs) and are considered part of NG-RAN. See the diagram illustrating the NG-RAN architecture. Figure 1 The LTE connected to 5GC is described for completeness and will not be considered further in this document.

[0010] NR RedCap

[0011] The initial 5G release in Release 15 was optimized for Enhanced Mobile Broadband (eMBB) and Ultra-Reliable and Low-Latency Communication (URLLC). These services require very high data rates and / or low latency, thus placing high demands on the UE. To enable 5G to be used for other services with more relaxed performance requirements (such as wireless sensors or wearable devices), a new low-cost UE type was introduced in Release 17, see 3GPP RP-193238 “New SIDon support of reduced capability NR devices”. Compared to Release 15 devices, this low-cost UE has reduced capabilities, such as:

[0012] - Reduced device bandwidth, for example, 10MHz instead of 100MHz in FR1.

[0013] - Reduced number of antennas, for example, one antenna instead of two in the FR1.

[0014] - Half-duplex FDD instead of full-duplex FDD

[0015] This new UE type is sometimes referred to as NR RedCap UE.

[0016] If low-complexity UEs with reduced capabilities are used in applications they are not intended for, they may fail to meet the service requirements and user expectations of applications such as eMBB or URLLC applications. Although the problem is caused by the low-complexity UE, it may be perceived as a network error by other UEs in the network, and thus could damage the operator's reputation. If low-complexity UEs become widespread, this could also undermine public perception of 5G as a superior technology. Summary of the Invention

[0017] One objective of the embodiments described herein is to improve the performance of radio communication networks in which UEs with reduced capabilities operate.

[0018] According to one aspect of the embodiments herein, this objective is achieved by a method performed by an apparatus for processing a user equipment (UE) accessing a radio communication network. The UE is using reduced capabilities. The reduced capabilities are related to reduced capabilities for communication within the radio communication network. The apparatus obtains information about the UE's user profile. When the UE uses reduced capabilities to access the radio communication network, the apparatus determines, based on the obtained information about the UE's user profile, whether the UE is authorized to access the radio communication network using reduced capabilities.

[0019] According to another aspect of the embodiments herein, this objective is achieved by an apparatus in a radio communication network, the apparatus being configured to process user equipment (UE) access to the radio communication network. The UE is configured to use reduced capabilities. The reduced capabilities are adapted to be associated with reduced capabilities for communication in the radio communication network. The apparatus is further configured to:

[0020] - Obtain information about the user profile of the UE, and

[0021] When the UE uses reduced capabilities to access the radio communication network, based on the information obtained about the UE's user profile, it is determined whether the UE is authorized to access the radio communication network by using reduced capabilities.

[0022] Furthermore, this document provides a computer program product including instructions that, when executed on at least one processor, cause the at least one processor to perform any of the methods described above, performed by the means. Additionally, this document provides a computer-readable storage medium storing a computer program product including instructions that, when executed on at least one processor, cause the at least one processor to perform the method described above, according to any of the methods described above, performed by the means.

[0023] For example, a UE using reduced capabilities has a subscription with the operator and therefore has a user profile with the operator.

[0024] By utilizing the UE's user profile, network access for UEs with reduced capabilities can be controlled. Access is controlled to enable... quilt The UE authorized to access the radio communication network obtains access to the radio communication network, and enables... Not A UE authorized to access a radio communication network may be denied access, for example, by being denied access to a wireless communication network.

[0025] In this way, unauthorized UEs will not access the network and therefore will not cause any problems within the radio communication network. As a result, the performance of the radio communication network (e.g., in terms of capacity, latency, and spectral efficiency) is improved for any UE (e.g., a regular UE). Attached Figure Description

[0026] Examples of embodiments described herein are described in more detail with reference to the accompanying drawings, which are:

[0027] Figure 1 This is a schematic block diagram illustrating the prior art;

[0028] Figure 2 This is a schematic block diagram illustrating an embodiment of a radio communication network;

[0029] Figure 3 This is a flowchart illustrating an embodiment of a method in the apparatus;

[0030] Figure 4 This is a sequence diagram illustrating an embodiment of the method;

[0031] Figure 5 This is a sequence diagram illustrating an embodiment of the method;

[0032] Figure 6 This is a sequence diagram illustrating an embodiment of the method;

[0033] Figure 7 This is a sequence diagram illustrating an embodiment of the method;

[0034] Figure 8a and 8b This is a schematic block diagram illustrating an embodiment of the device;

[0035] Figure 9 This schematically illustrates a telecommunications network connected to a host computer via an intermediate network;

[0036] Figure 10 It is an overall block diagram of a host computer communicating with user equipment via a base station on some wireless connections;

[0037] Figure 11-14 This is a flowchart illustrating a method implemented in a communication system including a host computer, a base station, and user equipment. Detailed Implementation

[0038] As part of the development of this article, the inventors identified the issues that will be discussed first.

[0039] As mentioned above, 3GPP Release 17 introduced a new UE type with reduced capabilities for NR, which is used for applications with low to medium performance requirements, such as wearable devices and industrial sensors.

[0040] Besides perception issues, the use of low-complexity UEs can also impact system capacity because the network can serve fewer UEs when UEs have reduced capabilities. For example, even with a carrier bandwidth of 100MHz, the network might only be able to utilize 10MHz due to UE bandwidth limitations. If all UEs are restricted to the same 10MHz, system capacity will decrease by approximately 90% compared to when all UEs support the full carrier bandwidth.

[0041] Therefore, it is necessary for operators to be able to restrict the use of low-complexity UEs on their networks based on the services users are using.

[0042] Therefore, one objective of the embodiments described herein is to improve the performance of radio communication networks in which UEs with reduced capabilities operate.

[0043] The embodiments described herein may relate to how operators can restrict the use of such UEs (e.g., low-cost UEs) that utilize reduced capabilities in radio communication networks. This is an issue that has therefore received attention in the latest version of the research project description in 3GPP RP-193238, “New SID on support of reduced capability NR devices,” with the following objectives:

[0044] • Research a standardized framework and principles for defining and limiting this reduced capability—consider defining a limited set of one or more device types and how to ensure that these device types are used only for the intended use cases [RAN2, RAN1].

[0045] • The study will allow devices with reduced capabilities to be explicitly identified by the network and network operators and allow operators to restrict the access of these devices when necessary [RAN2, RAN1].

[0046] The embodiments herein provide methods for restricting the use of low-complexity UEs. According to the embodiments herein, when a UE uses reduced capabilities to connect to a network, an authorization check is performed to verify that the UE is permitted to use the reduced capabilities to access the network. The authorization check may be performed by the CN, RAN, or the UE, and may be based, for example, on information in the user profile.

[0047] One advantage of the embodiments described herein is that these embodiments enable operators to limit the use of low-complexity UEs (e.g., UE 120) with reduced capabilities to applications the UE is intended to be used for, such as industrial sensors or wearable devices. This can be achieved by using a UE (e.g., UE 120) user profile that informs the UE of the intended application.

[0048] The operator controls network access (e.g., access to a radio communication network) permissions by pre-configuring a UE (e.g., UE 120) with authorization information. This authorization information defines whether access for a specific UE type (e.g., UE type 120) is permitted in a specific network, based on the UE's user profile. This means that the operator can use authorization information to pre-configure UE 120, defining whether access for a specific UE type (e.g., UE type 120) is permitted in radio communication network 100, based on the UE's user profile.

[0049] Figure 2This is a schematic overview diagram illustrating a radio communication network 100 in which embodiments of the invention may be implemented. The radio communication network 100 includes one or more RANs and one or more CNs. The radio communication network 100 may use 5G NR, but may also use many other different technologies, such as Wi-Fi, LTE, Advanced LTE, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications / Enhanced Data Rate GSM Evolution (GSM / EDGE), or Ultra Mobile Broadband (UMB), to name just a few possible implementations.

[0050] A radio access network node (e.g., RAN node 110) operates within the radio communication network 100. RAN node 110 provides access to the radio communication network 100, for example, for UEs served by RAN node 110. RAN node 110 provides, for example, multiple cells. RAN node 110 can be a transmitting and receiving point, such as a radio access network node like a base station, such as a NodeB, evolved Node B (eNB, eNode B), NR Node B (gNB), base transceiver station, radio remote unit, access point base station, base station router, transmission equipment of a radio base station, stand-alone access point, wireless local area network (WLAN) access point, access point station (AP STA), access controller, a UE acting as an access point or peer in device-to-device (D2D) communication, or any other network element capable of communicating with a UE served by RAN node 110, depending on, for example, the radio access technology and terminology used.

[0051] User equipment operates in radio communication network 100, such as UE 120. UE 120 may be, for example, an NR device, mobile station, wireless terminal, NB-IoT device, eMTC device, low-complexity UE, NR RedCap device, CAT-M device, WiFi device, LTE device, and non-access point (non-AP) STA, STA, communicating via a base station (e.g., network node 110), one or more access networks (ANs) (e.g., RANs) and one or more core networks (CNs). Those skilled in the art will understand that UE is a non-limiting term that refers to any UE, terminal, wireless communication terminal, user equipment, (D2D) terminal, or node, such as a smartphone, laptop computer, mobile phone, sensor, repeater, mobile tablet, or even a small base station communicating within a cell. UE 120 is capable of communicating in radio communication network 100 using reduced capabilities.

[0052] UE 120 has a subscription with the operator. This subscription can be, for example, a data subscription and / or a voice subscription. Therefore, UE 120 has a user profile with the operator. When used herein, the user profile of UE 120 refers to a collection of user policy control data, such as including subscribed services, user level, permitted Public Land Mobile Network (PLMN) identifiers (IDs), permitted RATs, permitted network slices, QoS profile, etc.

[0053] The user profile of UE 120 can be included in the operator's centralized user database, such as the Unified Data Management (UDM) in a 5G CN. A subset of the user profile can also be stored in the user's Common User Identifier Module (USIM). User policy information common to multiple users may also be stored separately, for example, in another CN node (such as AMF) or a RAN node in the RAN (such as RAN node 110, or gNB).

[0054] CN nodes (e.g., CN node 130) operate in the CN network of radio communication network 100. CN node 130 may include, for example, any one or more of AMF, SMF, UDM, UPF, and any suitable functions. CN node 130 may be any one or more of an AMF node, SMF node, UDM or UPF node, or any other suitable node.

[0055] In one aspect, the method described herein can be performed by a device (sometimes referred to as device 110, 120, 130), which can be any one or more of UE 120, RAN node 110, and CN node 130. Alternatively, it can be used, for example, those included in... Figure 2 The distributed nodes (DNs) and functions in the cloud 140 shown are used to perform or partially perform these methods.

[0056] The embodiments described herein enable, when UE 120 is connected to radio communication network 100, to restrict the use of a reduced-capability UE to specific services based on the user profile of UE 120. This method is performed by devices 110, 120, and 130, which can be any one or more of RAN node 110, UE 120, and CN node 130. This means that when UE 120 is connected to radio communication network 100, this method can be performed in more than one device.

[0057] Figure 3An example method in a radio communication network 100, performed by devices 110, 120, and 130 (including any one or more of UE 120, RAN node 110, and CN node 130), is illustrated. This method is used to process UE 120 accessing the radio communication network 100. When used herein, UE 120 accessing the radio communication network 100 may, for example, mean that UE 120 attempts to camp on a cell belonging to the radio communication network 100, establish a connection with the radio communication network 100, register with the radio communication network 100, or generally utilize resources belonging to the radio communication network 100. UE 120 is using reduced capabilities related to reduced capabilities for communication within the radio communication network 100. Reduced capabilities may include, for example, one or more of the following:

[0058] - Reduced UE bandwidth.

[0059] - Reduce the number of UE receive RX and / or transmit TX antennas.

[0060] - Half-duplex frequency division duplex (FDD).

[0061] -Relaxed UE processing time.

[0062] -Relaxed UE processing capabilities.

[0063] This method includes any one or more of the following actions:

[0064] Action 301

[0065] In some embodiments, devices 110, 120, and 130 may receive an indication that UE 120 intends to access radio communication network 100 using reduced capabilities. Devices 110, 120, and 130 may receive this indication from UE 120 or a node. Alternatively, devices 110, 120, and 130 may receive this indication through a pre-configured indication. This operation will be described in more detail below.

[0066] Action 302

[0067] UE 120 is a UE using reduced capabilities, and therefore the device needs to check whether UE 120 is authorized to use reduced capabilities to access radio communication network 100. This is necessary because if UE 120 accesses radio communication network 100 without authorization, it may cause problems in radio communication network 100, as described above.

[0068] As described above, UE 120 has a subscription with the operator and therefore a user profile with the operator. The operator controls access to the radio communication network 100 by pre-configuring the UE (e.g., UE 120) with authorization information that defines whether access for a specific UE type (e.g., UE 120 type) is permitted in a specific network based on the UE's user profile. The pre-configured information may be stored, for example, in the UE 120 or in the UE 120's USIM. The pre-configured information may be defined by network identified by PLMN ID, by access technology, or a combination of both. The operator controls and sets the user profile of UE 120.

[0069] Devices 110, 120, and 130 obtain information about the user profile of UE 120. When UE 120 accesses the radio communication network 100, this information will be used as the basis for determining whether UE 120 is authorized to access the radio communication network 100 by using reduced capabilities.

[0070] Information about a user profile can be obtained, for example, by examining the user profile of the UE 120. The user profile can also be obtained from, for example, the Unified Data Management (UDM) included in the 5G CN.

[0071] In some embodiments, RAN node 110 will use the UE identifier to obtain the UE context from CN node 130, which includes UE capabilities and user profile. It should be noted that CN node 130 may send only a subset of the user profile to the RAN (e.g., RAN node 110), or send configuration data derived from the user profile.

[0072] In some embodiments where the device is represented by UE 120, UE 120 checks whether it is authorized to use reduced capabilities to access radio communication network 100.

[0073] Information in the user profile of UE 120 may include information about how UE 120 is authorized to use reduced capabilities when accessing one or more specific portions of radio communication network 100. One or more specific portions of radio communication network 100 may include, for example, a private network, a network slice, a geographic area of ​​radio communication network 100, or a frequency of radio communication network 100.

[0074] Furthermore, the user profile information for UE 120 may include information about how UE 120 is authorized to use reduced capabilities when accessing radio communication network 100 using one or more specific policies. This means, for example, that if UE 120 accessing radio communication network 100 uses a specific policy (e.g., a Quality of Service (QoS) profile or a Radio Resource Management (RRM) policy), then UE 120 will also be allowed to use reduced capabilities.

[0075] One or more specific policies may include, for example, QoS profiles or RRM policies configured for a specific service.

[0076] The action will be described in more detail below.

[0077] Action 303

[0078] When UE 120 uses reduced capabilities to access radio communication network 100, devices 110, 120, and 130 determine whether UE 120 is authorized to access radio communication network 100 by using reduced capabilities. This determination is based on information obtained about the user profile of UE 120. It should be noted that the phrase "when UE 120 uses reduced capabilities to access radio communication network 100" also includes the phrase "when UE 120 intends to use reduced capabilities to access radio communication network 100." This may mean that devices 110, 120, and 130 check the information in the user profile of UE 120.

[0079] As described above, the embodiments herein may relate to how an operator can restrict the use of such a UE with reduced capabilities. Using information obtained about the user profile of UE 120, the operator can accept or reject the use of a UE with reduced capabilities (e.g., UE 120) when the UE accesses the radio communication network 100.

[0080] The action will be described in more detail below.

[0081] Action 304

[0082] When it is determined that UE 120 is authorized to access radio communication network 100 by using reduced capabilities, devices 110, 120, and 130 may accept access to radio communication network 100 by using reduced capabilities. This action will be described in more detail below.

[0083] Action 305

[0084] When it is determined that UE 120 is not authorized to access radio communication network 100 by using reduced capabilities, devices 110, 120, and 130 may refuse access to radio communication network 100 by using reduced capabilities. This action will be described in more detail below.

[0085] Regarding the operator's control over access to the radio communication network 100, the operator can pre-configure the UE (e.g., UE 120) using authorization information that defines whether access for a specific UE type is allowed in a specific network based on the UE's user profile.

[0086] In this way, the operator can control the access of a UE (e.g., UE 120) to the radio communication network 100 using information in the user profile (e.g., pre-configured by the operator in UE 120). This prevents unauthorized UEs from accessing the network and therefore will not cause any problems within the radio communication network. Consequently, the performance of the radio communication network is improved rather than degraded.

[0087] The method will now be further illustrated and illustrated in the following embodiments. These embodiments can be combined with any suitable embodiments as described above.

[0088] As described above, processing UE 120 access to radio communication network 100 (e.g., authorization using reduced UE capabilities) can be performed in the CN, for example by CN node 130, in the RAN, for example by RAN node 110, or in UE 122.

[0089] Alternative 1. Authorization check performed in the CN, for example by CN node 130. That is, devices 110, 120, and 130 are represented by CN node 130. Authorization check is performed in CN node 130 (when used herein, it is also referred to as determining whether UE 120 is authorized to access radio communication network 100 by using reduced capabilities).

[0090] In this alternative, the CN (e.g., CN node 130) verifies (also known as "determining whether") that UE 120 is authorized to use reduced UE capabilities during network registration. Figure 4 The action of an example embodiment is shown in the figure. Figure 4 The process of granting reduced capabilities to a CN (e.g., CN node 130) is illustrated. Figure 4 In the example and its corresponding text below, UE 120 is referred to as UE, CN node 130 is represented by AMF and is referred to as AMF, and RAN node 110 is referred to as gNB.

[0091] Action 401. This action relates to action 301, namely, how devices 110, 120, 130 (e.g., CN nodes, such as AMF) obtain an indication that UE 120 intends to use reduced capabilities to access the radio communication network, as described above.

[0092] UE 120 registers with radio communication network 100, for example, by sending a NAS registration request to the AMF (e.g., CN node 130). In this registration request, UE 120 indicates that it is using reduced capabilities (also referred to as reduced UE capabilities and RedCap indication). The use of reduced UE capabilities can be explicitly or implicitly indicated in the Non-Access Stratum (NAS) registration request.

[0093] Examples of explicit instructions include:

[0094] - "RedCap" flag, "RedCap" device type, or "RedCap" specific UE category.

[0095] - By including (low) UE capability information of UE 120, such as reduced device bandwidth, half-duplex FDD, or support for 1 receive antenna.

[0096] Examples of implicit indications include:

[0097] - The requested network (indicated by, for example, the selected / registered PLMN ID).

[0098] - The requested network slice, as indicated by the Requested Network Slice Selection Auxiliary Information (NSSAI).

[0099] Another alternative is for the gNB (e.g., RAN node 110) to indicate to the AMF (e.g., CN node 130) that UE 120 is using reduced UE capabilities, for example, based on specific low UE capabilities (e.g., reduced device bandwidth), when forwarding the NAS registration request to the AMF (e.g., CN node 130). Note that Figure 4 This is simplified because it only shows the message exchange between UE 120 and CN node 130, represented by AMF. In reality, the NAS registration request is first sent from UE 120 to gNB (e.g., RAN node 110) during Radio Resource Control (RRC) connection establishment and / or recovery, and then gNB (e.g., RAN node 110) forwards the request to AMF (e.g., CN node 130) in the NG-AP initial UE message. Therefore, gNB (e.g., RAN node 110) is able to include additional information about UE 120 in the NG-AP initial UE message.

[0100] Another alternative is for the AMF (e.g., CN node 130) to snoop on the stored UE capabilities to determine if UE 120 is using reduced UE capabilities. However, from a design perspective, this approach is not recommended because UE capabilities are intended to be transparent to the AMF.

[0101] Another alternative is for the AMF (e.g., CN node 130) to use a Permanent Device Identifier (PEI) to identify UEs (e.g., UE 120) with reduced capabilities. The PEI is sent from UE 120 to the AMF (e.g., CN node 130) during initial network registration and is stored by the AMF (e.g., CN node 130) as part of the UE context. By using, for example, a database lookup, the AMF (e.g., CN node 130) can determine whether the PEI belongs to UE 120 with reduced capabilities.

[0102] Action 402. This action relates to actions 302 and 303 as described above, namely, how devices 110, 120, 130 (e.g., CN nodes, such as AMF) obtain information about the user profile of UE 120, and based on the obtained information about the user profile of UE 120, determine whether UE 120 is authorized to access the radio communication network 100 using reduced capabilities. That is, for example, by checking the user profile of UE 120.

[0103] The AMF (e.g., CN node 130) checks (also known as determines) whether UE 120 is authorized to use reduced capabilities based on the user profile. The user profile can be obtained, for example, from the Unified Data Management (UDM) included in the 5G CN. The check can be performed, for example, based on an explicit indication of "Allow RedCap" in the user profile, or implicitly based on, for example, a list of allowed networks or allowed network slices. In the latter case, it is assumed that a dedicated network or network slice in the radio communication network 100 has been configured for a specific service, and a UE (e.g., UE 120) authorized to connect to that network or network slice is also authorized to use reduced capabilities.

[0104] Action 403. This action relates to actions 304 and 305 as described above, namely, how devices 110, 120, 130 (e.g., CN nodes, such as AMF) accept and / or refuse to use reduced capabilities to access the radio communication network.

[0105] If authorization is successful, the AMF (e.g., CN node 130) accepts the registration request and responds to UE 120 with NAS registration acceptance. Otherwise, if authorization fails, the AMF (e.g., CN node 130) can reject the registration request by sending a NAS registration rejection to UE 120 with an appropriate reason value (e.g., "PLMN not allowed", "TA not allowed", or "RedCap not allowed"). Alternatively, even if the authorization check fails, the AMF can accept the registration request but instruct the UE that the reduced UE capabilities must be disabled. This approach may be useful if the reduced capabilities can be disabled and / or enabled by the UE. For example, this might occur if the UE has full capabilities but prefers to operate with reduced capabilities to, for example, save power. Another alternative is for the AMF to accept registration but delete those network slices, such as MBB or URLLC slices, for which it does not allow reduced capabilities.

[0106] Instead of authorizing UE 120 during network registration, the AMF (e.g., CN node 130) can also authorize UE 120 during Protocol Data Unit (PDU) session establishment or PDU session modification (i.e., when UE 120 requests or modifies a data connection for a specific service). During PDU session establishment / modification, UE 120 can indicate the associated network slice identified by S-NSSAI and the gateway identified by Data Network Name (DNN). This can be used for authorization, meaning that only UEs (e.g., UE 120) that are permitted to connect to a specific network slice or gateway are allowed to use reduced capabilities.

[0107] A special case is when UE 120 performs emergency registration or establishes an emergency PDU session for an emergency call. In this case, the AMF (e.g., CN node 130) may choose to allow a UE with reduced capabilities (e.g., UE 120) to continue registration and / or PDU session establishment, even if UE 120 is not normally allowed to use reduced capabilities.

[0108] Note that with CN authorization, the configuration can be UE-specific. That is, although UE120 or gNB (e.g., RAN node 110) indicates that UE120 has low UE capability, the CN (e.g., CN node 130) determines on a per-UE basis whether UE120 should be authorized to access the network (i.e., depending on the CN implementation). Furthermore, in this CN (e.g., CN node 130) implementation, the UE will typically be authorized across the entire network, the PLMN, or a specific slice within the network, but there is no distinction at the cell level.

[0109] Alternative 2: Authorization check performed in the RAN (e.g., in RAN node 110). That is, devices 110, 120, and 130 are represented by RAN node 110.

[0110] In this alternative, RAN node 110 verifies (also referred to as “determine if”) that UE 120 is authorized to use reduced UE capabilities during RRC connection establishment.

[0111] exist Figure 5 The method of alternative solution 2 is illustrated in the diagram. Figure 5 In the example and its corresponding text below, UE 120 is referred to as UE, CN node 130 is represented by AMF and is referred to as AMF, and RAN node 110 is referred to as gNB.

[0112] Actions 501-505. These actions, for example, relate to actions 301 and 302, namely, how devices 110, 120, 130 (e.g., RAN node 110, such as gNB) obtain indications that UE 120 intends to use reduced capabilities to access radio communication network 100 and information about the UE user profile, as described above.

[0113] UE 120 performs random access and establishes an RRC connection with the gNB to exchange data or signaling with the network. During the RRC connection establishment process, the RRCSetupComplete message sends the UE identifier (e.g., a globally unique temporary UE identifier (GUTI)) and a NAS message (e.g., a NAS registration request) that triggers the RRC connection establishment.

[0114] RAN node 110 can determine whether UE 120 is using a reduced capability from the RRC connection establishment itself (e.g., UE 120 includes an indication in its RRC establishment request message that UE 120 is using a reduced capability) or when RAN node 110 receives UE capabilities stored in the CN. The UE identifier (e.g., GUTI) itself does not indicate whether UE 120 is using a reduced capability. However, the UE identifier is used to obtain information from the CN regarding whether UE 120 is permitted to use a reduced capability.

[0115] Therefore, the UE identifier will be used by RAN node 110 to obtain the UE context from CN node 130, which includes UE capabilities and user profile. It should be noted that CN node 130 may send only a subset of the user profile to the RAN (e.g., RAN node 110), or send configuration data derived from the user profile.

[0116] Action 506. This action relates to part of action 302, namely, how devices 110, 120, 130 (e.g., RAN node 110, such as gNB) obtain information about UE user profiles, as described above.

[0117] The gNB (e.g., RAN node 110) will forward the UE identifier and initial NAS message received from UE 120 during RRC connection establishment to the AMF, for example, in the NG-AP initial UE message. This is to enable RAN node 110 to obtain information about the UE user profile by retrieving information about the UE user profile from the UE context, which includes information about the UE capabilities and user profile.

[0118] Actions 507-508. These actions relate to a portion of action 302, namely, how devices 110, 120, 130 (e.g., RAN node 110, such as gNB) obtain information about UE user profiles, as described above.

[0119] The AMF (e.g., CN node 130) uses the UE identifier to obtain the UE context (which includes UE capabilities and user profile) or information derived from the user profile. The UE context is sent to the gNB in ​​the NG-AP Initial Context Establishment Request, and the gNB responds to the request with NG-AP Initial Context Establishment Complete.

[0120] Action 509. This action relates to action 303 as described above, namely, how devices 110, 120, 130 (e.g., RAN node 110, such as a gNB) determine, based on information obtained about the user profile of UE 120, whether UE 120 is authorized to access radio communication network 100 using reduced capabilities, as described above. The gNB (e.g., RAN node 110) checks whether UE 120 is authorized to use reduced UE capabilities based on UE context information received from the AMF. The check can be based, for example, on an explicit indication in the UE context (e.g., “Allow RedCap”), or the check can be implicitly performed based on one of the existing parameters included in the UE context, for example:

[0121] - The allowed networks, such as those indicated by the PLMN ID.

[0122] - Allowed network slices, for example, as indicated by the allowed NSSAI.

[0123] - The QoS policy information carried by the data to be established, such as the associated QoS profile indicated by QFI for each QoS flow in a PDU session.

[0124] -RRM policy information, such as information indicated by RFSP / SPID.

[0125] When using an implicit approach, it can be assumed that a private network, network slice, QoS profile, or RRM policy has been configured for a specific service, and any UE (e.g., UE120) assigned to that network, network slice, QoS profile, or RRM policy is allowed to use reduced capabilities.

[0126] Note that the gNB (e.g., RAN node 110) can determine that the UE is using a reduced capability based on the UE capabilities in the UE context. Depending on whether a new or existing random access procedure is used for the UE with reduced capabilities, the gNB can also determine that the UE was already using the reduced UE capability during the random access procedure. A third option is to indicate that the UE is using a reduced capability in, for example, an RRCSetupRequest or RRCSetupComplete message.

[0127] Action 510. This action relates to actions 304 and 305 as described above, namely, how devices 110, 120, 130 (e.g., RAN node 110, such as gNB) accept or refuse to use reduced capabilities to access the radio communication network.

[0128] If authorization is successful, the gNB (e.g., RAN node 110) can proceed with, for example, bearer establishment to exchange data with UE 120. Otherwise, if authorization fails, the gNB (e.g., RAN node 110) can release the RRC connection, for example, by sending an RRC release (RRCRelease) message with an appropriate reason value and a possible extended waiting time (to avoid frequent retries). The gNB (e.g., RAN node 110) can also redirect UE 120 to another RAT and / or frequency and / or cell in the RRCRelease message. Another alternative is for the gNB (e.g., RAN node 110) to notify the AMF (e.g., CN node 130) of the authorization failure, so that the AMF (e.g., CN node 130) can reject UE 120 on the NAS. For example, the AMF (e.g., CN node 130) can perform a network-initiated UE 120 deregistration and send a NAS deregistration request to the UE (the AMF including an appropriate reason value in the NAS deregistration request).

[0129] In certain situations, a gNB (e.g., RAN node 110) can perform authorization checks without obtaining the UE context from the AMF (e.g., CN node 130). For example, if the gNB (e.g., RAN node 110) can determine that UE 120 is already using degraded UE capabilities during random access or during RRC connection establishment, and UE 120 requests access to a network or network slice that does not allow degraded UE capabilities during connection establishment, the gNB (e.g., RAN node 110) can directly reject UE 120 without contacting the AMF (e.g., CN node 130).

[0130] In the description above, it is assumed that UE 120 is in the RRC_IDLE state when establishing an RRC connection with a gNB (e.g., RAN node 110). The situation where UE 120 is in the RRC_INACTIVE state and resumes a previously suspended RRC connection can be handled in a similar manner. The main difference is that UE 120 performs RRC resumption instead of RRC establishment, and the gNB (e.g., RAN node 110) obtains the UE context from the gNB (e.g., RAN node 110) that suspended the RRC connection, rather than from the AMF (e.g., CN node 130). The stored UE context is obtained using the Inactive Radio Network Temporary Identifier (I-RNTI) included in the RRC Resume Request (RRCResumeRequest) and includes authorization information (e.g., "RedCap Allowed" indication) and UE capabilities.

[0131] Similar to the first alternative, a special case occurs when a UE makes an emergency call. In this situation, the gNB can choose to allow a UE with reduced capabilities to continue making an emergency call, even if the UE would not normally be allowed to use the reduced capabilities.

[0132] Alternative 3: Authorization check performed in UE 120.

[0133] In this alternative, the device is UE 120.

[0134] exist Figure 6 In the example and its corresponding text below, UE 120 is referred to as UE, CN node 130 is represented by AMF and is referred to as AMF, and RAN node 110 is referred to as gNB.

[0135] To prevent access attempts from degraded UEs (e.g., UE 120) (also known as RedCap UEs), the gNB (e.g., RAN node 110) can include an indication in the system information (SI) indicating whether access from RedCap UEs is permitted in the cell. See [link to relevant documentation]. Figure 6 .

[0136] Action 601.

[0137] This action relates to action 302, namely, how devices 110, 120, 130 (e.g., UE 120) obtain information about the UE user profile, as described above.

[0138] UE 120 obtains information about its UE user profile, including indications in the System Information (SI). The SI indication indicates whether a UE (e.g., UE 120) can access the cell using reduced capabilities, and is applicable to all UEs within the cell. Therefore, this indication can be interpreted as being part of the user profiles of all UEs (e.g., UE 120). That is, instead of storing information about cells that can be accessed using reduced capabilities in each UE's user profile, the network (e.g., RAN node 110) broadcasts a common indication in the cell (e.g., the cell of RAN node 110) indicating whether UEs with reduced capabilities (e.g., including UE 120) can access the cell.

[0139] Actions 602 and 603.

[0140] These actions relate to action 303 as described above, namely, how devices 110, 120, 130 (e.g., UE 120) determine, based on information obtained about the user profile of UE 120, whether UE 120 is authorized to access radio communication network 100 by using reduced capabilities, as described above.

[0141] UE 120 checks the SI to determine whether it is authorized to use reduced capabilities to access radio communication network 100. As described in Action 601, the SI indication can be considered a common part of the user profiles of all UEs and indicates whether a UE with reduced capabilities (e.g., UE 120) can access the cell.

[0142] This is performed when UE 120 uses reduced capabilities to access radio communication network 100 (which also includes the phrase "when UE 120 intends to use reduced capabilities to access radio communication network 100").

[0143] For gNBs (e.g., RAN Node 110), this is beneficial because it saves a significant amount of signaling used to reject UEs (e.g., UE 120) in subsequent steps. For UEs (e.g., UE 120), this is beneficial for the same reason, as random access and connection establishment attempts are not required to discover that UE 120 is not allowed to access using its low UE capabilities. This indication in the system information can be explicit or implicit, for example, based on the presence of a configuration for RedCap PRACH partitions, any other RedCap configuration information, or any other RedCap-related broadcast information (e.g., SSS-L) in the system information. Another alternative is to include the indication by network (identified by PLMN ID), by slice (identified by S-NSSAI), or by service (identified by service identifier).

[0144] exist Figure 7 Another option is shown in [the document / reference]. Figure 7 In the process, UE 120 checks if the USIM is authorized to use reduced capabilities to access the network.

[0145] exist Figure 7 In the example and its corresponding text below, UE 120 is referred to as UE, CN node 130 is represented by the operator and is referred to as the operator, and RAN node 110 is referred to as gNB. An operator is an entity that owns and / or manages a network or a part of a network (such as radio communication network 100).

[0146] Actions 701-703.

[0147] This action involves: action 302, i.e., how devices 110, 120, 130 (e.g., UE 120) obtain information about the UE user profile, as described above; and action 303, i.e., how devices 110, 120, 130 (e.g., UE 120) determine, based on the obtained information about the UE 120's user profile, whether the UE 120 is authorized to access the radio communication network 100 by using reduced capabilities, as described above.

[0148] UE 120 obtains information about the UE user profile, including USIM information.

[0149] Operators control network access (e.g., access to a radio communication network) permissions by pre-configuring a UE (e.g., UE 120) with authorization information that defines whether access for a specific UE type is permitted in a particular network, based on the UE's user profile. This pre-configured information can be stored, for example, in the UE 120 or its USIM. The pre-configured information can be defined by network identified by a PLMN ID, by access technology, or a combination of both. Furthermore, the access information can indicate the minimum UE capability level required to perform access in the network using a specific access technology. In one example, the UE (e.g., UE 120) supports NB IoT UE category NB1 and NR MTC UE category, thus supporting a reduced set of capabilities. The UE is pre-configured with a USIM that includes a list of instructions indicating the UE can perform the following actions:

[0150] - Use NB-IoT access technology to access PLMN X

[0151] - Do not use an NR with a set of reduced NR UE capabilities to access PLMN X.

[0152] - Use both NB-IoT access technology and NR to access PLMN Y, regardless of the UE's NR UE capabilities.

[0153] Pre-configured information can be updated or overwritten based on network signaling (e.g., RAN node 11).

[0154] Note that if UE 120 performs authorization checks as described in the options above, previous alternatives still have an interest in having appropriate network mechanisms to check whether the UE (such as UE 120) is following the instructions in the SI or USIM and is not attempting to spoof.

[0155] If UE 120 is not allowed to access the network, then in either of the above alternatives, the UE can still be allowed to access the network to make emergency calls (i.e., the so-called "limited service state"). During cell selection and cell reselection, UE 120 may first search for cells that provide normal service, and if no such cell is found, the UE will begin searching for cells that provide limited service.

[0156] Figure 8a and 8b Examples of arrangements in devices 110, 120, and 130 are shown. Devices 110, 120, and 130 are adapted to be any one or more of the following: UE 120, RAN node 110 and CN node 130 in a radio communication network.

[0157] RAN node 110 may include input and output interfaces configured to communicate with each other, see [link to documentation]. Figure 8a The input and output interface may include a wireless receiver (not shown) and a wireless transmitter (not shown).

[0158] Apparatus 110, 120, and 130 may include an acquisition unit, a determination unit, an acceptance unit, and a rejection unit to perform the method actions described herein. See also Figure 8b .

[0159] It can be done through a corresponding processor or one or more processors (e.g. Figure 8a The embodiments of the present invention are implemented by a processor of the processing circuitry in the illustrated devices 110, 120, and 130, and computer program code for performing the functions and actions of the embodiments herein. The program code may also be provided as a computer program product, for example, in the form of a data carrier carrying the computer program code, which, when loaded into devices 110, 120, and 130, is used to execute the embodiments of the present invention. One such carrier may be in the form of a CD-ROM. However, other data carriers such as memory sticks are feasible. Furthermore, the computer program code may be provided as plain program code on a server and downloaded to devices 110, 120, and 130.

[0160] Devices 110, 120, and 130 may also include corresponding memories, which include one or more storage units. The memories include instructions executable by the processor in devices 110, 120, and 130.

[0161] The memory is arranged to store information, instructions, data, configurations, and applications related to the UE user profile, which, when executed in devices 110, 120, and 130, perform the methods described herein.

[0162] In some embodiments, the computer program includes instructions that, when executed by at least one processor, cause at least one processor of the apparatus 110, 120, 130 to perform the aforementioned actions.

[0163] In some embodiments, the corresponding carrier includes a corresponding computer program, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electrical signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0164] Those skilled in the art will also understand that the functional modules in the devices 110, 120, and 130 described below can refer to a combination of analog and digital circuits and / or one or more processors configured with, for example, software and / or firmware stored in the devices 110, 120, and 130, which, when executed by the respective one or more processors (e.g., the processors described above), cause the respective at least one processor to perform an action according to any of the above actions. One or more of these processors, along with other digital hardware, may be included in a single application-specific integrated circuit (ASIC), or multiple processors and various digital hardware may be distributed across multiple separate components (whether individually packaged or assembled into a system-on-a-chip (SoC)).

[0165] When the word “includes” or “contains” is used, it will be interpreted as non-restrictive, that is, meaning “consisting of at least…”.

[0166] The embodiments described herein are not limited to the preferred embodiments described above. Various alternatives, modifications, and equivalents may be used.

[0167] Below, some example embodiments 1-16 are briefly described. See, for example... Figure 2 , 3 8a and 8b.

[0168] Example 1. A method, for example, for processing user equipment UE 120 accessing radio communication network 100, the UE 120 using reduced capabilities related to reduced capabilities for communication in radio communication network 100, the method comprising any one or more of the following:

[0169] Obtain information from the 302 user profile for UE 120.

[0170] When UE 120 uses reduced capabilities to access radio communication network 100, based on the information obtained about the user profile of UE 120, it is determined whether UE 120 is authorized to access radio communication network 100 by using reduced capabilities.

[0171] Example 2. The method according to Example 1 further includes:

[0172] When it is determined that UE 120 is authorized to access radio communication network 100 by using reduced capabilities, Accept 304 access radio communication network 100 by using reduced capabilities;

[0173] When it is determined that UE 120 is not authorized to access radio communication network 100 by using reduced capabilities, access to radio communication network 100 by using reduced capabilities is denied 305.

[0174] Example 3. The method according to any one of Examples 1-2, wherein the information in the user profile of UE 120 includes information about UE 120 being authorized to use reduced capabilities when accessing one or more specific parts of the radio communication network 100. For example, a private network, network slicing.

[0175] Example 4. The method according to any one of Examples 1-3, wherein the information regarding the user profile of UE 120 includes information about the reduced capabilities of UE 120 when it is authorized to access the radio communication network 100 using one or more specific policies. For example, a QoS profile or RRM policy configured for a specific service.

[0176] Example 5. The method according to any one of Examples 1-4, wherein the reduced capability includes one or more of the following:

[0177] - Reduced UE bandwidth,

[0178] - Reduce the number of UE receive RX and / or transmit TX antennas.

[0179] - Half-duplex frequency division duplex (FDD)

[0180] -Relaxed UE processing time, and

[0181] -Relaxed UE processing capabilities.

[0182] Example 6. The method according to any one of Examples 1-5 further includes:

[0183] 301UE 120 received an instruction that it intends to use reduced capabilities to access radio communication network 100.

[0184] Example 7. The method according to any one of Examples 1-6, wherein the method is performed by any one or more of the following: UE 120, radio access network RAN ​​node 110 and core network CN node 130 in radio communication network 100.

[0185] Example 8. A computer program including instructions that, when executed by a processor, cause the processor to perform any one of Examples 1-7.

[0186] Example 9. A carrier comprising a computer program according to Example 8, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electrical signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0187] Example 10. An apparatus 110, 120, 130 in a radio communication network 100, configured, for example, to process user equipment 120 accessing the radio communication network 100, the UE 120 being configured to use reduced capabilities, and the reduced capabilities being adapted to be associated with reduced capabilities for communication in the radio communication network 100, and the apparatus being further configured to perform any one or more of the following:

[0188] For example, information about the user profile of UE 120 can be obtained using the acquisition units in devices 110, 120, and 130.

[0189] When UE 120 uses reduced capabilities to access radio communication network 100, for example by means of the determining unit in devices 110, 120, 130, it is determined whether UE 120 is authorized to access radio communication network 100 by using reduced capabilities, based on the information obtained about the user profile of UE 120.

[0190] Example 11. The apparatus 110, 120, 130 according to Example 10 is further configured as follows:

[0191] When it is determined that UE 120 is authorized to access radio communication network 100 by using reduced capabilities, for example by means of the receiving unit in devices 110, 120, 130, access to radio communication network 100 by using reduced capabilities is accepted.

[0192] When it is determined that UE 120 is not authorized to access radio communication network 100 by using reduced capabilities, access to radio communication network 100 by using the reduced capabilities is denied, for example by means of the denial unit in devices 110, 120, 130.

[0193] Example 12. The apparatus 110, 120, 130 according to any one of Examples 10-11, wherein the information in the user profile of UE 120 is adapted to include information that UE 120 is authorized to use reduced capabilities when accessing one or more specific portions of the radio communication network 100. For example, a private network, network slicing.

[0194] Example 13. The apparatus 110, 120, 130 according to any one of Examples 10-12, wherein the information regarding the user profile of UE 120 is further adapted to include information about the reduced capabilities of UE 120 when it is authorized to access the radio communication network 100 using one or more specific policies. For example, a QoS profile or RRM policy configured for a specific service.

[0195] Example 14. The apparatus 110, 120, 130 according to any one of Examples 10-13, wherein the reduced capability is suitable to include one or more of the following:

[0196] - Reduced UE bandwidth,

[0197] - Reduce the number of UE receive RX and / or transmit TX antennas.

[0198] - Half-duplex frequency division duplex (FDD)

[0199] -Relaxed UE processing time, and

[0200] -Relaxed UE processing capabilities.

[0201] Example 15. The apparatus 110, 120, 130 according to any one of Examples 10-14 is further configured as follows:

[0202] For example, by means of the acquisition unit in devices 110, 120, 130, an indication is obtained that UE 120 intends to use reduced capabilities to access radio communication network 100.

[0203] Example 16. The apparatus 110, 120, 130 according to any one of Examples 10-15, wherein the apparatus 110, 120, 130 is adapted to be any one or more of the following: UE 120, radio access network RAN ​​node 110 and core network CN node 130 in radio communication network 100.

[0204] Other extensions and variations

[0205] refer to Figure 9According to one embodiment, the communication system includes a telecommunications network 3210 such as a radio communication network 100, an IoT network such as a 3GPP-type cellular network, or a WLAN, which includes an access network 3211 such as a radio access network and a core network 3214. The access network 3211 includes multiple base stations 3212a, 3212b, and 3212c, such as RAN node 110, access nodes, AP STAs, NBs, eNBs, gNBs, or other types of radio access points, each defining a corresponding coverage area 3213a, 3213b, or 3213c. Each base station 3212a, 3212b, or 3212c can be connected to the core network 3214 via a wired or wireless connection 3215. A first user equipment (UE) located in coverage area 3213c (e.g., UE 120, such as a non-AP STA 3291) is configured to be wirelessly connected to or paged by a corresponding base station 3212c. A second UE 3292 (e.g., wireless device 122, such as a non-AP STA) in coverage area 3213a may wirelessly connect to the corresponding base station 3212a. Although multiple UEs 3291, 3292 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or a single UE is connected to the corresponding base station 3212.

[0206] Telecommunication network 3210 is connected to host computer 3230, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. Host computer 3230 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. Connections 3221 and 3222 between telecommunication network 3210 and host computer 3230 may extend directly from core network 3214 to host computer 3230, or may be via optional intermediate network 3220. Intermediate network 3220 may be one of public, private, or hosted networks, or a combination of more than one; intermediate network 3220 (if any) may be a backbone network or the Internet; in particular, intermediate network 3220 may include two or more subnetworks (not shown).

[0207] Overall, Figure 10The communication system enables connectivity between one of the connected UEs 3291 and 3292 and the host computer 3230. This connectivity can be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291 and 3292 are configured to transmit data and / or signaling via the OTT connection 3250 using access network 3211, core network 3214, any intermediate network 3220, and possibly other infrastructure (not shown) as intermediaries. The OTT connection 3250 can be transparent because the participating communication devices traversed by the OTT connection 3250 are unaware of the routes for uplink and downlink communications. For example, the base station 3212 may not be notified or need not be notified of past routes for incoming downlink communications originating from the host computer 3230 that are to be forwarded (e.g., handed over) to the connected UE 3291. Similarly, the base station 3212 does not need to know the future routes for outgoing uplink communications from the UE 3291 to the host computer 3230.

[0208] According to one embodiment, reference will now be made to Figure 10 Example implementations of the UE, base station, and host computer discussed in the preceding paragraphs are described. In the communication system 3300, the host computer 3310 includes hardware 3315, which includes a communication interface 3316 configured to establish and maintain wired or wireless connections with different communication devices of the communication system 3300. The host computer 3310 also includes processing circuitry 3318, which may have storage and / or processing capabilities. In particular, the processing circuitry 3318 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. The host computer 3310 also includes software 3311, which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318. The software 3311 includes a host application 3312. Host application 3312 is operable to provide services to remote users, such as UE 3330, connected via an OTT connection 3350 terminated between UE 3330 and host computer 3310. In providing services to remote users, host application 3312 can provide user data sent using OTT connection 3350.

[0209] The communication system 3300 also includes a base station 3320 disposed in the telecommunications system, and the base station 3320 includes hardware 3325 that enables it to communicate with a host computer 3310 and a UE 3330. Hardware 3325 may include a communication interface 3326 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 3300, and a radio interface 3327 for establishing and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown) served by the base station 3320. Communication interface 3326 may be configured to facilitate a connection 3360 with the host computer 3310. Connection 3360 may be direct, or connection 3360 may be through the core network of the telecommunications system (…). Figure 10 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 3325 of base station 3320 also includes processing circuitry 3328, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. Base station 3320 also has software 3321 stored internally or accessible via an external connection.

[0210] The communication system 3300 also includes the previously mentioned UE 3330. The hardware 3335 of UE 3330 may include a radio interface 3337 configured to establish and maintain a radio connection 3370 with a base station serving the coverage area where UE 3330 is currently located. The hardware 3335 of UE 3330 also includes processing circuitry 3338, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. UE 3330 also includes software 3331, which is stored in or accessible by UE 3330 and executable by processing circuitry 3338. Software 3331 includes a client application 3332. The client application 3332 is operable to provide services to human or non-human users via UE 3330 with the support of host computer 3310. In host computer 3310, the executing host application 3312 can communicate with the executing client application 3332 via OTT connection 3350 terminated between UE 3330 and host computer 3310. When providing services to a user, client application 3332 can receive request data from host application 3312 and provide user data in response to that request data. OTT connection 3350 can transmit both request data and user data. Client application 3332 can interact with the user to generate user-provided user data.

[0211] Notice, Figure 10The host computer 3310, base station 3320, and UE 3330 shown can be respectively connected to... Figure 11 The host computer 3230, one of the base stations 3212a, 3212b, and 3212c, and one of the UEs 3291 and 3292 are identical. That is to say, the internal working principles of these entities can be as follows: Figure 10 As shown, and independently, the surrounding network topology can be Figure 9 The surrounding network topology.

[0212] exist Figure 10 The OTT connection 3350 has been abstractly depicted to illustrate communication between the host computer 3310 and the user equipment 3330 via the base station 3320, without explicitly referencing any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine the routing, and can be configured to hide the routing from the UE 3330, the service provider operating the host computer 3310, or both. When the OTT connection 3350 is active, the network infrastructure can further make decisions, dynamically changing the routing accordingly (e.g., based on load balancing considerations or network reconfiguration).

[0213] The radio connection 3370 between UE 3330 and base station 3320 is based on the teachings of embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 3330 using OTT connection 3350 (where radio connection 3370 forms the final segment). More precisely, the teachings of these embodiments can improve applicable RAN effects: data rate, latency, power consumption, thereby providing benefits such as corresponding effects on OTT services: for example, reduced user wait time, relaxed file size limits, better responsiveness, and extended battery life.

[0214] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors improved thereon in one or more embodiments. Optional network functions may also be available for reconfiguring the OTT connection 3350 between the host computer 3310 and the UE 3330 in response to changes in measurement results. The measurement procedures and / or network functions for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities as exemplified above or by providing values ​​of other physical quantities from which the software 3311, 3331 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 3350 may include message formats, retransmission settings, preferred routing, etc. Reconfiguration does not need to affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host computer 3310 in measuring throughput, propagation time, latency, etc. Measurements can be made because software 3311, 3331 causes the use of OTT connection 3350 to send messages, particularly empty or "dummy" messages, during its monitoring of propagation time, errors, etc.

[0215] Figure 11 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station (e.g., network node 110), and a UE (e.g., UE 120), which may be referenced... Figure 9 and Figure 10 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section includes only descriptions of... Figure 11 Referring to the accompanying drawings. In the first action 3410 of the method, the host computer provides user data. In an optional sub-action 3411 of the first action 3410, the host computer provides user data by executing a host application. In the second action 3420, the host computer initiates a transmission carrying user data to the UE. In an optional third action 3430, in accordance with the teachings of the embodiments described throughout this disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In an optional fourth action 3440, the UE executes a client application associated with the host application executed by the host computer.

[0216] Figure 12This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station (e.g., an AP STA), and a UE (e.g., a non-AP STA), which may be referenced... Figure 9 and Figure 10 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section includes only descriptions of... Figure 12 Referring to the accompanying drawings. In the first action 3510 of the method, the host computer provides user data. In an optional sub-action (not shown), the host computer provides user data by executing a host application. In the second action 3520, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, this transmission can be performed via a base station. In an optional third action 3530, the UE receives the user data carried in the transmission.

[0217] Figure 13 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station (e.g., an AP STA), and a UE (e.g., a non-AP STA), which may be referenced... Figure 9 and Figure 10 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section includes only descriptions of... Figure 13 Referring to the accompanying drawings. In an optional first action 3610 of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second action 3620, the UE provides user data. In an optional sub-action 3621 of the second action 3620, the UE provides user data by executing a client application. In another optional sub-action 3611 of the first action 3610, the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates the transmission of user data to the host computer in an optional third sub-action 3630. In a fourth action 3640 of the method, the host computer receives user data sent from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0218] Figure 14 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station (e.g., an AP STA), and a UE (e.g., a non-AP STA), which may be referenced... Figure 9 and Figure 10 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section includes only descriptions of... Figure 14Refer to the accompanying drawings. In an optional first action 3710 of the method, the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In an optional second action 3720, the base station initiates a transmission of the received user data to a host computer. In a third action 3730, the host computer receives the user data carried in the transmission initiated by the base station.

[0219] Abbreviation Explanation

[0220] 3GPP Third Generation Partnership Project

[0221] 4G fourth generation

[0222] 5G (Fifth Generation)

[0223] 5GC 5G core

[0224] 5GS 5G system

[0225] AMF Access and Mobility Management Functions

[0226] CN Core Network

[0227] CU Central Unit

[0228] DU Distributed Unit

[0229] eNB (evolved node B) is a radio base station in LTE.

[0230] E-UTRAN (Evolved Universal Terrestrial Radio Access Network)

[0231] gNB 5G Node B (Radio Base Station in NR).

[0232] LTE Long Term Evolution

[0233] Interface / reference point between RAN and CN in NG 5G / NR.

[0234] NG-C NG control plane portion (between gNB and AMF).

[0235] NG-RAN (Next Generation Radio Access Network)

[0236] NG-U is the user-side portion of NG (between gNB and UPF).

[0237] NR New Radio

[0238] NSSAI Network Slice Selection Auxiliary Information

[0239] OFDM (Orthogonal Frequency Division Multiplexing)

[0240] PLMN Public Land Mobile Network

[0241] RAN (Radio Access Network)

[0242] RLC Radio Link Control

[0243] RRC Radio Resource Control

[0244] RFSP Index RAT / Frequency Selection Priority Index

[0245] S-NSSAI Selected NSSAI

[0246] SN serial number

[0247] SPID is a user profile ID used for RAT / frequency priority.

[0248] TA tracking area

[0249] TS Technical Specifications

[0250] UDM Unified Data Management

[0251] UE User Equipment

[0252] UPF User Face Functions

[0253] URLLC Ultra-Reliable Low-Latency Communication

[0254] USIM Unified User Identification Module

[0255] Xn is the interface / reference point between the two gNBs.

Claims

1. A method performed by apparatus (110, 120, 130) for processing a user equipment (UE) (120) accessing a radio communication network (100), the UE (120) using reduced capabilities, and the reduced capabilities being related to reduced capabilities for communication in the radio communication network (100), the method comprising: (302) Obtain information about the user profile of the UE (120), wherein the user profile of the UE informs the UE of one or more applications it intends to use. When the UE (120) uses reduced capabilities to access the radio communication network (100), based on the information obtained about the user profile of the UE (120), it is determined (303) whether the UE (120) is authorized to access the radio communication network (100) by using reduced capabilities, wherein the information about the user profile of the UE (120) includes information that the UE (120) is authorized to use reduced capabilities when accessing one or more specific parts of the radio communication network (100).

2. The method according to claim 1, further comprising: When it is determined that the UE (120) is authorized to access the radio communication network (100) by using reduced capabilities, accept (304) access the radio communication network (100) by using reduced capabilities; When it is determined that the UE (120) is not authorized to access the radio communication network (100) by using reduced capabilities, access to the radio communication network (100) by using reduced capabilities is denied (305).

3. The method according to any one of claims 1-2, wherein, The information in the user profile of the UE (120) also includes information about the UE (120) being authorized to use reduced capabilities when accessing the radio communication network (100) using one or more specific policies.

4. The method according to any one of claims 1-2, wherein, The reduced capability includes one or more of the following: - Reduced UE bandwidth, - Reduce the number of UE receive RX and / or transmit TX antennas. - Half-duplex frequency division duplex (FDD) -Relaxed UE processing time, and -Relaxed UE processing capabilities.

5. The method according to any one of claims 1-2, further comprising: (301) Obtain an indication that the UE (120) intends to use reduced capabilities to access the radio communication network (100).

6. The method according to any one of claims 1-2, wherein, The method is performed by the apparatus comprising any one or more of the following: the UE (120), the radio access network RAN ​​node (110) and the core network CN node (130) in the radio communication network (100).

7. An apparatus (110, 120, 130) in a radio communication network (100), configured to process user equipment (UE) (120) accessing the radio communication network (100), the UE (120) being configured to use reduced capabilities adapted to be related to reduced capabilities for communication in the radio communication network (100), and the apparatus further being configured to: Obtain information about the user profile of the UE (120), wherein, The UE's user profile informs the UE of one or more applications it intends to use, and When the UE (120) uses reduced capabilities to access the radio communication network (100), based on the information obtained about the user profile of the UE (120), it is determined whether the UE (120) is authorized to access the radio communication network (100) by using reduced capabilities, wherein the information about the user profile of the UE (120) is adapted to include information that the UE (120) is authorized to use reduced capabilities when accessing one or more specific parts of the radio communication network (100).

8. The apparatus (110, 120, 130) according to claim 7 is further configured to: When it is determined that the UE (120) is authorized to access the radio communication network (100) by using reduced capabilities, access to the radio communication network (100) by using reduced capabilities is accepted; When it is determined that the UE (120) is not authorized to access the radio communication network (100) by using reduced capabilities, access to the radio communication network (100) by using reduced capabilities is denied.

9. The apparatus (110, 120, 130) according to any one of claims 7-8, wherein, The information in the user profile of the UE (120) is also adapted to include information about the UE (120) being authorized to use reduced capabilities when accessing the radio communication network (100) using one or more specific policies.

10. The apparatus (110, 120, 130) according to any one of claims 7-8, wherein, The reduced capability is suitable for including one or more of the following: - Reduced UE bandwidth, - Reduce the number of UE receive RX and / or transmit TX antennas. - Half-duplex frequency division duplex (FDD) -Relaxed UE processing time, and -Relaxed UE processing capabilities.

11. The apparatus (110, 120, 130) according to any one of claims 7-8 is further configured to: The UE (120) is given an indication that it intends to use reduced capabilities to access the radio communication network (100).

12. The apparatus (110, 120, 130) according to any one of claims 7-8, wherein, The apparatus (110, 120, 130) is adapted to be any one or more of the following: the UE (120), the radio access network RAN ​​node (110) and the core network CN node (130) in the radio communication network (100).

Images