First wireless device, network node and method performed thereby for handling access to a wireless communication network

Abstract

A method performed by a first wireless device (131). The method is for handling access to a wireless communication network (100). The first wireless device (131) transmits (403), to a network node (110), a first message as part of a random access procedure for accessing the wireless communication network (100). The first wireless device (131) has one or more first characteristics that are limited relative to one or more second characteristics of one or more second wireless devices (132). The transmitting (403) is performed in accordance with one or more first parameters. The one or more first parameters are different from one or more second parameters that are allowed to be used by the one or more second wireless devices (132) in the wireless communication network (100) when performing random access.

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to a first wireless device and a method performed by it for handling access to a wireless communication network. The present disclosure relates generally also to a network node and a method performed by it for handling access to a wireless communication network. BACKGROUND

[0002] A wireless device within a wireless communication network can be, for example, a User Equipment (UE), a Station (STA), a mobile terminal, a wireless terminal, a terminal and / or a Mobile Station (MS). The wireless device is enabled to communicate wirelessly in a cellular communications network or wireless communication system, sometimes also referred to as a cellular radio system, cellular system or cellular network. The communication can be performed, e.g., via a Radio Access Network (RAN) and possibly via one or more core networks, comprised within the wireless communication network, between two wireless devices, between a wireless device and a plain old telephone and / or between a wireless device and a server. The wireless device can further be referred to as (just to mention some other examples) a mobile phone, a cellular phone, a sensor, a camera, an Internet of Things (IoT) device, a laptop or a tablet with wireless capability. The wireless device in the present context can be, for example, a portable, pocket-storable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and / or data, via the RAN, with another entity, such as another terminal or a server.

[0003] A wireless communication network covers a geographical area that can be divided into cell areas, each served by a network node, which can be an access node such as a radio network node, a radio node or a base station (e.g. a Radio Base Station (RBS), which sometimes can be referred to as gNB, which is a 5G Node B, "eNodeB", "eNodeB", "Node B", "B-Node", transmission point (TP) or BTS (Base Transceiver Tower), depending on the technology and terminology used. Based on transmission power and thereby also cell size, base stations can be of different classes, such as wide area base stations, medium or small area base stations, local area base stations, home base stations, pico base stations, etc. A cell is the geographical area where radio coverage is provided by the base station or radio node at the base station site or radio node site, respectively, e.g. by a base station or radio node of a base station site or radio node site. One base station, which can be of different classes, can serve one or more cells. Further, each base station can support one or several communication technologies. The base stations communicate over the air interface operating on radio frequencies with the terminal within range of the base stations. A wireless communication network can also be a non-cellular system comprising network nodes which can use serving beams to serve receiving nodes, e.g. wireless devices. In the Third Generation Partnership Project (3GPP) Long Term Evolution (LTE), base stations, which can be referred to as eNodeBs or even eNBs, can be directly connected to one or more core networks. In the context of the present disclosure, the expression "downlink (DL)" can be used for the transmission path from a base station to a wireless device. The expression "uplink (UL)" can be used for the transmission path in the opposite direction, i.e. from the wireless device to the base station.

[0004] The standardization organization 3GPP is currently specifying a new radio interface, referred to as NR or 5G-UTRA, as well as a Fifth Generation (5G) Packet Core network, which can be referred to as Next Generation (NG) Core network, abbreviated as NG-CN, NGC or 5G Core Network (CN).

[0005] Internet of Things (IoT)

[0006] The Internet of Things (IoT) can be understood as the interconnection of communication devices, e.g. physical devices, vehicles, which can also be referred to as "connected devices" and "smart devices", buildings and other items embedded with electronics, software, sensors, actuators, and network connectivity that can enable these objects to collect and exchange data. The IoT can allow remote sensing and / or control of objects across existing network infrastructures.

[0007] A "thing" in the sense of IoT can refer to a variety of devices, such as a heart monitoring implant, a biochip transponder for farm animals, an electric clam along coastal waters, a car with built-in sensors, a DNA analysis device for environmental / food / pathogen monitoring, or a field operating device that can assist firefighters in search and rescue operations, home automation devices (e.g. control and automation of lighting, heating, ventilation, air conditioning, e.g. "smart" thermostats, ventilation, air conditioning), and devices that can be remotely monitored using telecommunication (e.g. washing machines, dryers, ovens, refrigerators or freezers). These devices can collect data by means of various existing technologies and then make the data autonomously flow between other devices.

[0008] It is expected that in the near future the number of IoT devices will be very large. There are various predictions, one of which assumes more than 60,000 devices per square kilometer, another of which assumes 1,000,000 devices per square kilometer. It is expected that a large part of these devices are stationary, such as gas and electricity meters, vending machines, etc.

[0009] Machine Type Communication (MTC)

[0010] In recent years, Machine Type Communication (MTC) has shown to be a growing market segment for cellular technology, especially in the context of the Internet of Things (IoT). MTC devices can be communication devices, often wireless communication devices or simply user equipment, which are self- and / or automatically controlled unattended machines and which are usually not associated with an active human user in order to generate data traffic. MTC devices can often be simpler compared to regular mobile phones or smart phones and are usually associated with a more specific application or purpose. MTC relates to communication in a wireless communication network to and / or from MTC devices, which is different from, e.g., communication associated with regular mobile phones and smart phones, which can often have completely different properties and have other requirements. In the context and development of the IoT, it is clear that MTC traffic will increase and thus needs to be supported more and more in wireless communication systems.

[0011] Reduced Capability NR Devices

[0012] 5G is the fifth generation of cellular technology and was introduced in Release 15 of the 3GPP standard. 5G can be understood as aiming to increase speed, reduce latency, and increase flexibility of wireless services. A 5G system (5GS) can be understood to comprise both a new radio access network (so-called Next Generation Radio Access Network (NG-RAN), which uses a new air interface called New Radio (NR)) and a new core network (5G Core (5GC)).

[0013] The initial version of 5G in Release 15 can be understood to be optimized for Mobile Broadband (MBB) as well as Ultra-Reliable and Low-Latency Communication (URLLC). These services can require very high data rates and / or low latency and can therefore put high requirements on the UEs. To enable 5G to be used for other services with more relaxed performance requirements, a new low complexity UE type is introduced in Release 17, see [1]. The Reduced Capability (RedCap) UE type can be understood to be particularly suitable for Machine-Type Communication (MTC) services (e.g. wireless sensors or video surveillance), but can also be used for MBB services with lower performance requirements (e.g. wearable devices). A low complexity UE can be understood to have reduced capabilities compared to a Release 15 NR UE, e.g. reduced UE bandwidth, reduced number of UE receive / transmit (RX / TX) antennas, half duplex frequency division duplex (FDD), relaxed UE processing time and / or relaxed UE processing capability.

[0014] Due to the reduced capabilities, a low complexity UE can sometimes also be referred to as an NR RedCap UE. An NR RedCap UE can have some or all of the above-mentioned reduced capabilities.

[0015] From an operator side, it can be important that low complexity UEs are only used for their intended use cases. To enforce this requirement, the network can need to be able to identify low complexity UEs and to restrict their access when necessary. This is captured in the 3GPP Study Item Description for Low Complexity UEs [1] as a study standardization framework and principles for how to define and constrain such reduced capabilities, with consideration of a limited set of one or more device type definitions, and with consideration of how to ensure that these device types are only used for the intended use cases. This is also captured in the 3GPP Study Item Description for Low Complexity UEs as a study function that can allow the network and network operators to explicitly identify devices with reduced capabilities and to allow operators to restrict access of devices when needed.

[0016] In some cases, it can also be required that the network is able to restrict access of UEs that can be authorized to use reduced capabilities. For example, in overload situations (e.g. radio resource congestion or insufficient processing capacity), the network can want to reduce the overload by rejecting low complexity UEs from accessing a cell. In overload situations, the network can also need to prioritize between normal complexity and low complexity UEs. To this end, the network can employ access control as referred to in 3GPP.

[0017] Access control mechanisms in NR

[0018] Access control can be used to prevent overloading in a wireless network and to ensure that high priority services (e.g. emergency calls) can access the system even in congestion. In NR, there can be multiple access control mechanisms, which one to use can depend on the severity of the specific load situation, as shown in Figure 1

[0019] During normal operation and light load, regular scheduling can be used to ensure that quality of service (QoS) targets can be met for UEs in a cell. At higher load, the network can decide to apply random access (RA) backoff or use a wait timer to release / reject UEs. Access barring can typically be applied as a last resort when the previous mechanisms can not be sufficient to reduce the load. Although scheduling can be understood to be performed in connected mode, random access backoff, release / rejection of UEs and UE access barring (UAC) can be applied in idle, inactive and / or connected mode.

[0020] Random access

[0021] Figure 2 is a schematic diagram showing non-limiting examples of the following random access procedures according to existing methods: a) CBRA with 4-step RA type, b) CBRA with 2-step RA type, c) CFRA with 4-step RA type, and d) CFRA with 2-step RA type. Figure 2 corresponding to Figure 9 .2.6-1 in technical specification (TS) 38.300 v16.1.0. CBRA can be understood to refer to contention-based random access, CFRA can be understood to refer to contention-free random access. The latter can be understood to cover cases where a UE has been provided with a unique preamble / RA resource, which can be understood to not require a contention resolution procedure, which is typically used only in CONNECTED. The random access procedure can be triggered when data arrives in the UE data buffer, if the UE is in RRC IDLE or RRC INACTIVE state, or if the UE is in RRC CONNECTED but if the UE does not have a physical uplink control channel (PUCCH) resource to send a scheduling request. The UE can then randomly select a preamble (Msg1) in the upcoming physical random access channel (PRACH) resource (typically the first preamble) to minimize the delay. This can be understood to correspond to the first arrow in step 1 in Figure 2 a) and step A in Figure 2 b). The gNB can then respond to the preamble transmission in Msg2, providing an UL grant for Msg3 transmission, a temporary cell radio network temporary identifier (C-RNTI) value to be used and a timing advance value to be applied by the UE to obtain uplink synchronization. This can be understood to correspond to Figure 2 ​Step 2 in a). Msg2 can be carried on Physical Downlink Shared Channel (PDSCH) and dynamically scheduled by gNB; UE can monitor Physical Downlink Control Channel (PDCCH) scrambled with Random Access Radio Network Temporary Identifier (RA-RNTI) during Random Access Response (RAR) window. If Msg2 is successfully received by UE, UE can next transmit Msg3, which can be understood to contain a Radio Resource Control (RRC) message (which can depend on the reason for the access attempt), but for example, if UE can wish to establish a connection to transmit data, contain RRCSetupRequest, and contain a UE_ID to identify the UE, or a random value (if it is an initial attach of the UE to the network). This can be understood to correspond to Figure 2 Step 3 in a). In Msg4, the network can provide a RRC message response (RRCSetup in the example above) to the UE, and provide other indications to the UE. This can be understood to correspond to Figure 2 Step 4 in a). In addition, as part of the contention resolution, the UE ID in Msg3 can be echoed back to the UE. That is, two or more UEs can have selected the same preamble in the same PRACH resource, have successfully received Msg2 and also transmitted Msg 3, but only the UE that receives its UE ID back in Msg4 can conclude that it has won the contention resolution and continues to establish a dedicated connection. In Figure 2 These messages are shown in Figure 2 corresponding to Figure 9 .2.6-1. In CBRA with 2-step RA type shown in panel b), the payload can be transmitted by the UE in step A together with the RA preamble. Then, contention resolution can be performed in step B, so that the whole procedure is performed in two steps. In Figure 2 In c) and d), the preamble assigned to the UE by the gNB in step 0 can be transmitted back to the gNB by the UE in step 1 and A, respectively. In CFRA with 2-step RA type shown in panel d), the payload can be transmitted by the UE in step A together with the RA preamble. Then, a random access response can be transmitted by the gNB in step 2 and step B, respectively.

[0022] The UE behavior at failure can depend on in which step the UE can fail. If no Msg2 is received, the UE can assume that the gNB was not able to successfully decode Msg1 and can perform a re-attempt with increased power, e.g., open loop power control. The UE can count the number of attempts and after a configurable maximum number of attempts has been reached, the UE can conclude that the random access procedure has failed and communicate this to higher layers in the UE. If no Msg4 is received, the UE can attempt a Msg3 hybrid automatic repeat request (HARQ) retransmission. Finally, if Msg4 is received but does not contain the UE's own UE_ID, the UE can conclude that it has lost the contention resolution and can start over from the Msg1 preamble transmission.

[0023] Existing methods for performing random access to a network can result in unnecessary delay, signaling overhead, processing, and energy waste, leading to poor network performance and user experience.

[0024] WO 2016 / 025899 describes that an eNB can allocate PRACH resources to reduced bandwidth wireless transmit / receive units (WTRUs). These resources can be the same as, separate from, or a subset of resources that can be allocated for legacy or other WTRUs. The allocated resources can include preambles that can or can only be used by reduced bandwidth WTRUs.

[0025] EP3468284 describes that a bandwidth reduced low complexity (BL) UE or a UE in coverage enhancement (CE) can select an arbitrary RA preamble corresponding to a decided CE level from multiple RA preamble candidates and can transmit the selected RA preamble to a base station.

[0026] EP3244686 describes that an indication of preamble reservation and set size can be provided. For example, a field such as numberOfRA-Preambles-MTC can be used to indicate that the number of MTC preambles is 8, so MTC devices should select from these preambles, and a field such as numberOfRA-Preambles can be used to indicate that the number of preambles intended for legacy devices is 40.

[0027] US 20190373450 describes that a reduced capability UE can indicate reduced capability support to a base station. SUMMARY

[0028] As part of the development of embodiments herein, one or more challenges of the prior art will first be identified and discussed.

[0029] For some access restriction mechanisms, reduced capability UEs cannot be distinguished and handled separately.

[0030] One object of embodiments herein is to improve handling of access to a wireless communication network. In particular, one object of embodiments herein can be seen to improve handling of access to a wireless communication network for wireless devices having restricted characteristics.

[0031] According to a first aspect of embodiments herein, the object is achieved by a method performed by a first wireless device. The method is for handling access to a wireless communication network. The first wireless device transmits, to a network node, a first message as part of a random access procedure for accessing the wireless communication network. The first wireless device has one or more first characteristics that are restricted with respect to one or more second characteristics of one or more second wireless devices. The transmitting is performed in accordance with one or more first parameters. The one or more first parameters are different from one or more second parameters that are allowed to be used in the wireless communication network by the one or more second wireless devices when performing random access.

[0032] According to a second aspect of embodiments herein, the object is achieved by a method performed by a network node. The method is for handling access to a wireless communication network. The network node receives, from a first wireless device, a first message as part of a random access procedure for accessing the wireless communication network. The first wireless device has one or more first characteristics that are restricted with respect to one or more second characteristics of one or more second wireless devices. The receiving is performed in accordance with one or more first parameters. The one or more first parameters are different from one or more second parameters that are allowed to be used in the wireless communication network by the one or more second wireless devices when performing random access.

[0033] According to a third aspect of embodiments herein, the object is achieved by a first wireless device for handling access to a wireless communication network. The first wireless device is configured to transmit, to a network node, a first message as part of a random access procedure for accessing the wireless communication network. The first wireless device is configured to have one or more first characteristics that are configured to be restricted with respect to one or more second characteristics of one or more second wireless devices. The transmitting is configured to be performed in accordance with one or more first parameters. The one or more first parameters are configured to be different from one or more second parameters that are configured to be allowed to be used in the wireless communication network by the one or more second wireless devices when performing random access.

[0034] According to a fourth aspect of embodiments herein, the object is also achieved by a network node for handling access to a wireless communication network. The network node is configured to receive, from a first wireless device, a first message as part of a random access procedure for accessing the wireless communication network. The first wireless device is configured to have one or more first characteristics configured to be limited in relation to one or more second characteristics of one or more second wireless devices. The receiving is configured to be performed in accordance with one or more first parameters. The one or more first parameters are configured to be different from one or more second parameters configured to be allowed to be used by the one or more second wireless devices in the wireless communication network when performing random access.

[0035] By transmitting the first message to the network node in accordance with the one or more first parameters, the random access procedure for accessing the wireless communication network 100 can be made more restrictive for the first wireless device, e.g. a RedCap UE, compared to the one or more second wireless devices, which can be non-limited. This can be understood as being able to protect or prioritize the performance of legacy or normal capability wireless devices. Thus, this can enable the network node to reduce overload by rejecting low complexity UEs, e.g. the first wireless device, from accessing the cell in an overload situation, e.g. radio resource congestion or insufficient processing capacity. Thus, the performance of the wireless communication network can be optimized, ensuring that high priority wireless devices are served. BRIEF DESCRIPTION OF DRAWINGS

[0036] Examples of embodiments herein are described in more detail according to the following description with reference to the drawings.

[0037] Figure 1 is a schematic overview illustrating access control mechanisms in NR according to prior methods;

[0038] Figure 2 is a schematic overview illustrating non-limiting examples of the following random access procedures according to prior methods: a) CBRA with 4-step RA type, b) CBRA with 2-step RA type, c) CFRA with 4-step RA type, and d) CFRA with 2-step RA type;

[0039] Figure 3 is a schematic overview of an example of a wireless communication network according to embodiments herein;

[0040] Figure 4 is a flowchart illustrating a method in a first wireless device according to embodiments herein;

[0041] Figure 5 is a flowchart illustrating a method in a network node according to embodiments herein;

[0042] Figure 6 are schematic block diagrams illustrating two embodiments of a first wireless device according to embodiments herein in panels a) and b);

[0043] Figure 7 are schematic block diagrams illustrating two embodiments of a network node according to embodiments herein in panels a) and b);

[0044] Figure 8 is a schematic block diagram illustrating a telecommunication network connected via an intermediate network to a host computer according to embodiments herein;

[0045] Figure 9 is a generalised block diagram of a host computer communicating via a base station with a user equipment according to embodiments herein over a partially wireless connection;

[0046] Figure 10 is a flowchart illustrating an embodiment of a method in a communication system including a host computer, a base station and a user equipment according to embodiments herein;

[0047] Figure 11 is a flowchart illustrating an embodiment of a method in a communication system including a host computer, a base station and a user equipment according to embodiments herein;

[0048] Figure 12 is a flowchart illustrating an embodiment of a method in a communication system including a host computer, a base station and a user equipment according to embodiments herein;

[0049] Figure 13 is a flowchart illustrating an embodiment of a method in a communication system including a host computer, a base station and a user equipment according to embodiments herein. DETAILED DESCRIPTION

[0050] Particular aspects of the present disclosure and embodiments thereof can provide solutions to the challenges described in the “BACKGROUND” and “SUMMARY” sections herein or other challenges. Particular embodiments herein can generally be understood to relate to different aspects of providing restricted random access for reduced capability NR devices. Embodiments herein can be understood to enable differentiation between reduced capability (RedCap) UEs in a random access procedure, and a more stringent access can be applied for RedCap UEs compared to legacy / normal capability UEs. That is, configuration parameters for random access (e.g., random backoff time or maximum number of attempts) can be configured to be more restrictive for RedCap UEs to give RedCap UEs a lower priority in the random access procedure.

[0051] Some embodiments contemplated will now be described more fully in the following, with reference being made to the accompanying drawings in which examples are shown. In this section, embodiments herein will be shown in more detail by a number of example embodiments. However, other embodiments are included within the scope of the subject matter disclosed herein. The disclosed subject matter is not to be interpreted to be limited to the embodiments set forth herein; rather, these embodiments are provided as example to convey the scope of the subject matter to one of ordinary skill in the art. It is noted that the example embodiments herein are not mutually exclusive from each other. Components from one embodiment can by default be assumed to be present in another embodiment, and it will be apparent to one of ordinary skill in the art how these components can be used in other example embodiments.

[0052] Figure 3 Two non-limiting examples of a wireless network or wireless communication network 100 (sometimes also referred to as a wireless communication system, a cellular radio system or a cellular network) in which embodiments herein can be implemented are shown. The wireless communication network 100 can typically support MTC, eMTC, IoT and / or NB-IoT. The wireless communication network 100 can be a 5G system, a 5G network or a next generation system or network. In other examples, the wireless communication network 100 can alternatively or additionally support other technologies such as Long Term Evolution (LTE), e.g. LTE-M, LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LDE Half-Duplex Frequency Division Duplex (HD-FDD), LTE operating in unlicensed bands (e.g. LTE LAA, eLAA, feLAA and / or MulteFire). However, in other examples, the wireless communication network 100 can support other technologies such as Wideband Code Division Multiple Access (WCDMA), Universal Terrestrial Radio Access (UTRA) TDD, Global System for Mobile Communications (GSM) network, GSM / Enhanced Data Rates for GSM Evolution (EDGE) Radio Access Network (GERAN) network, Ultra Mobile Broadband (UMB), EDGE network, a network comprising any combination of radio access technologies (RATs) (e.g. Multi-Standard Radio (MSR) base stations, multi-RAT base stations, etc.), any Third Generation Partnership Project (3GPP) cellular network, WiFi network, Worldwide Interoperability for Microwave Access (WiMax), or any cellular network or system. Thus, although terminology from 5G / NR and LTE can be used in this disclosure to exemplify embodiments herein, this should not be seen as limiting the scope of the embodiments herein only to the above mentioned systems.

[0053] The wireless communication network 100 can comprise a plurality of network nodes, wherein in Figure 3Network node 110 is shown in a non-limiting example. Network node 110 is a radio network node. That is, a transmission point (e.g., a radio base station, such as a gNB, eNB, eNodeB, or home node B, home eNode B), or any other network node with similar characteristics capable of serving user equipment (e.g., wireless devices or machine-type communication devices) in the wireless communication network 100. In some examples (e.g.) Figure 3 In the example shown, network node 110 can be a distributed node and can partially perform its functions in collaboration with virtual node 116 in cloud 115.

[0054] The wireless communication network 100 can cover a geographical area. In some embodiments, the geographical area can be divided into cell areas, where each cell area can be served by a radio network node, but a radio network node can serve one or more cells. Figure 3 In the example, network node 110 serves cell 120. Based on transmit power and thus also based on cell size, network node 110 may belong to different classes, such as macro eNodeB, home eNodeB, or pico base station. In some examples, network node 110 may use a serving beam to serve receiving nodes. Radio network nodes may support one or more communication technologies, and their names may depend on the technologies and terminology used. Any radio network node that can be included in communication network 100 may be directly connected to one or more core networks.

[0055] Multiple wireless devices can be located in the wireless communication network 100, wherein... Figure 3The first wireless device 131 and the one or more second wireless devices 132 are shown in the non-limiting example of Fig. 1. Any of the first wireless device 131 and the one or more second wireless devices 132 comprised in the wireless communication network 100 can be a wireless communication device such as a 5G UE or a UE, which can also be referred to as, for example, a mobile terminal, wireless terminal and / or mobile station, mobile phone, cellular phone, sensor, loT device, NB-loT device, a device equipped with a wireless interface such as a printer or a file storage device, or a laptop with wireless capability, just to mention some other examples. Any wireless device comprised in the wireless communication network 100 can be, for example, a portable, pocket-storable, hand-held, computer-included, or car-mounted mobile device, enabled to communicate voice and / or data, for example, via a RAN, with another entity, such as a server, a laptop, a personal data assistant (PDA), or a tablet computer, a machine-to-machine (M2M) device, a modem, or any other radio network unit capable of communicating over a radio link in a communication system. Any of the first wireless device 131 and the one or more second wireless devices 132 comprised in the wireless communication network 100 can be enabled to communicate in the wireless communication network 100. The communication can be performed, for example, via a RAN and possibly via one or more core networks that can be comprised within the wireless communication network 100.

[0056] The first wireless device 131 can have one or more first characteristics, which can be understood to be limited in relation to one or more second characteristics of the one or more second wireless devices 132. In a particular embodiment, the first wireless device 131 can be a RedCap UE. The one or more second wireless devices 132 can herein be referred to as legacy or full capability UEs, non-reduced capability UEs.

[0057] The first wireless device 131 can belong to a first group, type or class of wireless devices, while the one or more second wireless devices 132 can belong to a second group, type or class of wireless devices.

[0058] It can be understood that although the one or more wireless devices 132 are shown as being comprised in the cell 120 in Figure 3 It can be understood that although the one or more wireless devices 132 are shown as being comprised in the cell 120 in

[0059] The first wireless device 131 can be configured to communicate with the network node 110 within the wireless communication network 100 over a first link 141, e.g., a radio link. The network node 110 can be configured to communicate with the virtual network node 116 within the wireless communication network 100 over a second link 142, e.g., a radio link or a wireline link. One or more second wireless devices 132 can be configured to communicate with the network node 110 within the wireless communication network 100 over respective links, e.g., radio links, which are not shown in Figure 3 The figure is simplified to ease the understanding of the present disclosure.

[0060] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the technical field of the disclosure, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the item, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one and only one instance of the item, apparatus, component, means, step, etc., unless expressly specified otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed unless explicitly stated as such. Any of the embodiments disclosed herein can be applied to any other embodiments, wherever technically feasible. Similarly, any advantages, features, or benefits described in relation to one embodiment can be applied to any other embodiment, wherever technically feasible. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

[0061] Generally, the use of “first”, “second”, “third”, “fourth” and / or “fifth” herein can be understood as denoting any way of distinguishing between different elements or entities, and can be understood as not giving the nouns they modify a cumulative or chronological ordering unless otherwise indicated based on the context.

[0062] A number of embodiments are included herein. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment can be present by default in another embodiment, and it will be apparent to the skilled person how these components can be used in other exemplary embodiments.

[0063] More specifically, the following are embodiments relating to a wireless device, e.g., the first wireless device 131, such as a 5G UE or a UE, and embodiments relating to a network node, e.g., the network node 110, such as a gNB or an eNB.

[0064] Some embodiments herein can be further described using some non-limiting examples.

[0065] In the following description, any reference to one / the UE, UEs, RedCap UEs, RedCap UE (or simply "UE") can be understood as equally referring to the first wireless device 131, unless a reference to a legacy UE is made; any reference to one / the gNB, one / the NW and / or one / the network can be understood as equally referring to the network node 110; any reference to one / the legacy or full capability UE, non-reduced capability UE can be understood as equally referring to one or more second wireless devices 132.

[0066] Embodiments of a method performed by the first wireless device 131 will now be described with reference to the flowchart illustrated in Figure 4 The method can be understood as for handling access to a wireless communication network. The first wireless device 131 can be understood as operating in the wireless communication network 100.

[0067] In some examples, the wireless communication network 100 can support at least one of: New Radio (NR), Long Term Evolution (LTE), LTE for Machines (LTE-M), Enhanced Machine Type Communications (eMTC), and Narrow Band Internet of Things (NB-IoT).

[0068] The method can be understood as a computer-implemented method.

[0069] A number of embodiments are included herein. The method can comprise one or more of the following actions. In some embodiments, all actions can be performed. In some embodiments, one or more actions can be performed. It should be noted that the examples herein are not mutually exclusive. One or more embodiments can be combined, where applicable. To simplify the description, not all possible combinations are described. Components from one embodiment can by default be present in another embodiment, and it will be apparent to a person skilled in the art how these components can be used in other exemplary embodiments. In Figure 4 A non-limiting example of a method performed by the first wireless device 131 is illustrated in

[0070] In Figure 4 Optional actions are denoted using dashed lines in

[0071] Action 401

[0072] In order for the network node 110 to be able to perform access control for reduced devices, the network node 110 can need to first know which devices that can be reduced or not reduced.

[0073] According to the above, in this Action 401, the first wireless device 131 can transmit, to the network node 110, a first indication. The first indication can indicate that the first wireless device 131 has one or more first characteristics that are limited with respect to one or more second characteristics of one or more second wireless devices 132.

[0074] The one or more second wireless devices 132 can be understood as legacy non-limited devices. In some particular embodiments, the first wireless device 131 can be a reduced-capability wireless device, e.g. a RedCap UE. The one or more characteristics can be, e.g., a reduced UE bandwidth, a reduced number of UE receive / transmit (RX / TX) antennas, half duplex frequency division duplex (FDD), relaxed UE processing time, and / or relaxed UE processing capability.

[0075] The transmitting in this Action 403 can be performed, e.g., via the first link 141.

[0076] The first indication can be, e.g., a capability indication.

[0077] By transmitting the first indication in this Action 401, the first wireless device 131 can enable the network node 110 to know that the first wireless device 131 is a limited device, and thus, the first wireless device 131 can enable the network node 110 to apply random access control for the first wireless device 131.

[0078] Action 402

[0079] In this Action 402, the first wireless device 131 can obtain, from at least one of the network node 110 and a memory of the first wireless device 131, a second indication. The second indication can indicate at least one of: one or more first parameters, and one or more conditions.

[0080] The one or more first parameters can be to be used by the first wireless device 131 in Action 403 for transmitting the first message as part of a random access procedure for accessing the wireless communication network 100. The one or more parameters can be different from one or more second parameters that are allowed to be used in the wireless communication network 100 by the one or more second wireless devices 132 when performing random access. The one or more first parameters can be understood to encompass different ways in which the random access procedure can be made more limiting for RedCap UEs.

[0081] In a first example of embodiments herein, the random access procedure can be distinguished for RedCap UEs and other UEs (e.g. legacy or full capability UEs, non-reduced capability UEs). For example, a separate RedCap configuration for random access can be provided to the UEs via RRC signaling, possibly requiring application of the separate RedCap configuration by the RedCap UEs. That is, alternative configuration parameters can be provided for RedCap, e.g. in the RACH or PRACH configuration, and the RedCap UEs can be required to apply these parameters instead of the legacy parameters.

[0082] The one or more first parameters can comprise at least one of the following options with respect to the one or more second parameters.

[0083] i. Fewer preambles

[0084] According to a first option, the one or more second parameters can comprise a smaller set of preambles from which to select for transmission to the network node 110, e.g. for Msgl transmission. In one example, the RedCap UEs can be restricted to use fewer preambles compared to other UEs. This can be an artificial restriction for RedCap UEs, such that some preambles are not used by the RedCap UEs, and thus provide a lower collision rate for legacy / other UEs.

[0085] ii. Smaller preamble space for Msgl transmission

[0086] According to a second option, similar to the first option, the one or more second parameters can comprise a shorter preamble space for Msgl transmission to the network node 110. The preamble space can be understood to refer to a set of preambles or preamble indices available for Msgl transmission.

[0087] iii. Less frequent PRACH resources

[0088] According to a third option, the one or more second parameters can comprise less frequent PRACH resources. In one example, the RedCap UEs can be restricted to use a reduced number of PRACH resources compared to other UEs. This can be an artificial restriction for RedCap UEs, e.g. limiting the RedCap UEs to only use PRACH resources every second in time, such that some PRACH resources are not used by the RedCap UEs, and thus provide a lower collision rate for legacy / other UEs.

[0089] iv. Longer backoff time

[0090] According to a fourth option, one or more second parameters can comprise a longer back-off time. In one example, a longer back-off timer can be applied for RedCap UEs compared to other UEs upon a random access attempt failure. That is, it can take a longer time before a re-try can be made. This parameter can not be configured via RRC like many other parameters, but can instead be defined in the procedure text of TS 38.321 v.16.0.0 by the parameter PREAMBLE_BACKOFF. The principle can be that this value can initially be set to 0 ms, but then can be increased with the number of preamble collisions to enable the network to better handle congestion situations. The differentiation for RedCap UEs can be implemented, e.g., by the following modification to the procedure text, with added content marked with underlined font:

[0091] 1> set PREAMBLE_BACKOFF to 0 ms, Or for RedCap UEs, set PREAMBLE_BACKOFF to 10 ms Figure 5 ;

[0092] Unlike for LTE, it can be understood that there are already scaling factors in NR to prioritize random access in certain situations (e.g., in 2-step RACH, beam recovery, etc.), and in one example, the opposite logic can be applied here to instead deprioritize random access for RedCap UEs.

[0093] 2> if the random access response contains a MAC subPDU with the back-off indicator:

[0094] 3> set PREAMBLE_BACKOFF to the value of the BI field of the MAC subPDU multiplied with SCALING_FACTOR_BI using Table 7.2-1.

[0095] where

[0096] 5> set SCALING_FACTOR_BI to scalingFactorBI.

[0097] The added content can be to introduce a longer scaling factor for RedCap to protect legacy UEs:

[0098]

[0099]

[0100] The use of scalingFactorBIredcap can optionally be linked to the use of a new access identity or access category for RedCap.

[0101] v. Lower maximum number of RA attempts

[0102] According to a fifth option, one or more second parameters can comprise a lower maximum number of RA attempts.

[0103] In one example, a lower number of RA attempts can be configured for RedCap UEs, e.g. using differentiation of the parameter preambleTransMax, see example implementation in section 5.3 “Configuration aspects” below. This can reduce the interference and collision rate of other / legacy UEs caused by RedCap UEs in case of congestion.

[0104] Alternatively, the maximum number of RA attempts using 2-step RACH configured by the parameter msgA-TransMax can be lower for RedCap UEs.

[0105] vi. Reduced power control

[0106] According to a sixth option, one or more second parameters can comprise a reduced power control.

[0107] In one example of embodiments herein, the random access power control can be configured such that a RedCap UE can transmit effectively at a relatively lower power than other UEs. This can be achieved e.g. by the RedCap UE starting at a lower initial transmit power, that is, the parameter preambleReceivedTargetPower is set lower. Alternatively, the step size of the power ramping can be smaller than for other UEs, a separate powerRampingStep is applied for 4-step RACH, or msgA-PreamblePowerRampingStep is applied for 2-step RACH, or ramping is less frequent in time.

[0108] A first example of configuration can be to use a separate RRC configuration for RedCap, e.g. added to the general RRC configuration, see added parameters in example implementations under the section “Configuration aspects” herein, where different target power and step size can be configured for RedCap. Similar additions can be made in the new RACH-ConfigCommonRedcap configuration. Alternatively, the power ramping step or other parameters can be configured as an extension of RA-Prioritization, as shown below, where the added content is marked using underlined text:

[0109]

[0110] vii. Indication of lower priority

[0111] According to a seventh option, the one or more second parameters can comprise a lower priority for being granted access (e.g. a “RedCap UE” indication in Msg3) to be able to prioritize other UEs.

[0112] In one example, a RedCap UE can need to include a RedCap indication in Msg3. Using this new indication, the gNB can prioritize and decide how / whether to respond with Msg4. For example, if a RedCap UE and a legacy UE have both selected the same preamble in the same PRACH resource and also sent Msg3 according to the UL grant received in Msg2, the gNB can prioritize the legacy UE in the contention resolution. That is, if the gNB successfully decodes both Msg3 transmissions, the gNB can choose to prioritize and respond to the transmission from the legacy UE and thus the RedCap UE can lose the contention resolution.

[0113] For example, a spare bit in RRCSetupRequest can be used for this purpose, with the added content using underlined text markup:

[0114]

[0115] viii. Lower maximum number of Msg3 transmissions

[0116] According to an eighth option, the one or more second parameters can comprise a lower maximum number of Msg3 transmissions, e.g. a lower maximum number of Msg3 HARQ retransmissions.

[0117] In one example, a lower number of HARQ retransmissions can be configured or applied for RedCap UEs. This can also be addressed by a network implementation.

[0118] In one alternative example to the above, the one or more first parameters (e.g. differentiated RedCap parameters for random access) can instead be defined as an offset or factor from the legacy parameter value. This can be configured via RRC or be hardcoded in the specification. In one example of the latter, a RedCap UE can apply a double value of the backoff time or any other factor / offset of the backoff time compared to other UEs. In a congestion situation, this can keep the RedCap UE away for a longer time and thus ensure that legacy / other UEs can be prioritized. This principle can be understood to be the same for other parameters as well.

[0119] According to the above, in some embodiments, the one or more first parameters can be indicated as one of: one or more absolute values, one or more offsets (e.g., offsets relative to legacy parameter values) of the other one or more values, and one or more factors to be applied to the other one or more values. The factors can be, for example, scaling factors, e.g., hardcoded scaling factors relative to legacy parameter values.

[0120] Configuring aspects

[0121] The second indication can be understood as a configuration, the second indication can be pre-configured in the first wireless device 131 and retrieved from a memory of the first wireless device 133, or signaled by the network node 110.

[0122] In the second case, the obtained second indication can be comprised in a RRC configuration message. The second indication can be comprised in one of: a RACH-ConfigCommonRedcap information element (IE), a RA-Prioritization IE, a RACH-ConfigGeneric IE, and a RRCSetupRequest message.

[0123] As one particular example, the new differentiated and separate RedCap configuration parameters can be provided to the first wireless device 131 in different ways, e.g., in the following ways: a) hardcoded scaling or offset relative to legacy parameter values, b) in a new RRC configuration RACH-ConfigCommonRedcap, e.g., including PRACH configuration, configuration index, or configuration restriction, to indicate that the resources will be used for RedCap, c) as an extension of RA-Prioritization, see examples above for power control and back-off time, and d) in an extension of RACH-ConfigGeneric, see example below, where the added content is marked with underlined text.

[0124]

[0125] The one or more conditions can be conditions on which the first message can be transmitted in action 403 subsequently, and can comprise a load of the network node 110 or the wireless communication network 100 when performing the random access procedure. For example, the access control can only be applied when the load of the network node 110 or the wireless communication network 100 can be high (i.e., can exceed a certain threshold) when performing the random access, otherwise not.

[0126] By obtaining the second indication in this action 402, the first wireless device 131 can then be enabled to transmit the first message in a next action 403 using the one or more parameters, which in turn can enable the following control: enabling the random access procedure to be more restrictive for the first wireless device 131 (e.g. RedCap UE) compared to for the one or more second wireless devices 132 (which can be unrestricted).

[0127] Operation 403

[0128] In this action 403, the first wireless device 131 can initiate performing or perform an operation (e.g. a first operation) as part of a random access procedure for accessing the wireless communication network 100. As one example, the action can comprise the first wireless device 131 transmitting a first message to the network node 110 as part of a random access procedure for accessing the wireless communication network 100. The first wireless device 131 has one or more first characteristics that are restricted with respect to one or more second characteristics of one or more second wireless devices 132. The transmitting in this action 403 is performed in accordance with one or more first parameters. As previously mentioned, the one or more first parameters are different from one or more second parameters that are allowed to be used in the wireless communication network 100 by the one or more second wireless devices 132 when performing random access. The one or more second parameters can be referred to herein as legacy parameters.

[0129] The first message in the RA procedure can be, for example, any of Msg1, MsgA and / or Msg3.

[0130] For example, the one or more first parameters can be different from the one or more second parameters such that the RA of the one or more second wireless devices 132 can be configured to be prioritized (e.g. always prioritized) over the RA of the first wireless device 131. For example, the transmitting in this action 403 can be performed based on the second indication indicating that the RA of the one or more second wireless devices 132 is configured to be prioritized (e.g. always prioritized) over the RA of the first wireless device 131.

[0131] In some embodiments, the transmitting in this action 403 can be performed based on one or more conditions. The one or more conditions can comprise a load of the network node 110 or the wireless communication network 100 when performing the random access procedure.

[0132] The sending in the action 403 can be performed according to one or more first parameters based on one or more conditions. This can be understood to mean that the sending using the one or more first parameters can only be performed when the one or more conditions are fulfilled, e.g. when the load in a cell served by the network node 110 in which the first wireless device 131 is located is high, i.e. above a certain threshold. If such one or more conditions are not fulfilled, e.g. if the load is low, the first wireless device 131 can be enabled to use one or more second parameters, e.g. legacy parameters or parameters for non-restricted wireless devices, so that the restricted access parameters can only be applied when needed.

[0133] The sending in the action 403 can be performed, e.g. via the first link 141.

[0134] By sending the first message to the network node 110 according to the one or more first parameters, the random access procedure for accessing the wireless communication network 100 can be made more restrictive for the first wireless device 131, e.g. a RedCap UE, compared to one or more second wireless devices 132, which can be non-restricted. This can be understood to enable the performance of legacy or normal capability wireless devices to be protected or prioritized. Thus, this can enable the network node 110 to reduce overload by rejecting low complexity UEs, e.g. the first wireless device 131, from accessing a cell in an overload situation, e.g. radio resource congestion or insufficient processing capacity. Thus, the performance of the wireless communication network 100 can be optimized, ensuring that high priority wireless devices are served.

[0135] Embodiments of a method performed by a network node 110 will now be described with reference to the flowchart illustrated in Figure 5 The method can be understood as for handling access to a wireless communication network 100. The network node 110 can be understood as operating in the wireless communication network 100.

[0136] In some examples, the wireless communication network 100 can support at least one of: New Radio (NR), Long Term Evolution (LTE), LTE for Machines (LTE-M), Enhanced Machine Type Communications (eMTC), and Narrow Band-Internet of Things (NB-IoT).

[0137] The method can be understood as a computer-implemented method.

[0138] The method can comprise one or more of the following actions. A number of embodiments are included herein. In some embodiments, all actions can be performed. It should be noted that the examples herein are not mutually exclusive. One or more embodiments can be combined, where applicable. To simplify the description, not all possible combinations are described. Components from one embodiment can by default be present in another embodiment, and it will be apparent to a person skilled in the art how these components can be used in other exemplary embodiments. In Figure 6 A non-limiting example of a method performed by the network node 110 is shown in

[0139] The detailed description of some of the following sections corresponds to the same references provided above in relation to the actions described for the first wireless device 131, and is therefore not repeated here to simplify the description. For example, in some examples, the first wireless device 131 can be a reduced-capability wireless device, e.g. a RedCap UE.

[0140] Action 501

[0141] In this action 501, the network node 110 can receive, from the first wireless device 131, a first indication. The first indication can indicate that the first wireless device 131 has one or more first characteristics that are limited relative to one or more second characteristics of one or more second wireless devices 132.

[0142] The receiving in this action 501 can be performed, e.g. via the first link 141.

[0143] Action 502

[0144] In this action 502, the network node 110 can transmit, to the first wireless device 131, a second indication. The second indication can indicate at least one of: i) one or more first parameters, and ii) one or more conditions.

[0145] The transmitting of the second indication in this action 502 can be to the first wireless device 131.

[0146] The one or more first parameters can comprise at least one of: i) a smaller set of preambles to select from to transmit to the network node 110, ii) a shorter preamble space for Msgl transmission to the network node 110, iii) less frequent PRACH resources, iv) a longer back-off time, v) a lower maximum number of RA attempts, vi) a reduced power control, vii) a lower priority for licensed access, and viii) a lower maximum number of Msg3 transmissions, relative to one or more second parameters.

[0147] In some embodiments, the one or more first parameters can be indicated as one of: one or more absolute values, one or more offsets of the other one or more values, and one or more factors to be applied to the other one or more values.

[0148] In some embodiments, the transmitted second indication can be comprised in an RRC configuration message.

[0149] In some such embodiments, the second indication can be comprised in one of: a RACH-ConfigCommonRedcap IE, a RA-Prioritization IE, a RACH-ConfigGeneric IE, and an RRCSetupRequest message.

[0150] Action 503

[0151] In this Action 503, the network node 110 can initiate performing or perform an operation (e.g. a first operation or another operation) as part of a random access procedure for accessing the wireless communication network 100. As one example, the Action can comprise the network node 110 receiving, from a first wireless device 131, a first message as part of a random access procedure for accessing the wireless communication network 100. The first wireless device 131 has one or more first characteristics that are restricted relative to one or more second characteristics of one or more second wireless devices 132. The receiving in this Action 503 is performed in accordance with one or more first parameters. The one or more first parameters are different from one or more second parameters that are allowed to be used in the wireless communication network 100 by the one or more second wireless devices 132 when performing random access.

[0152] The receiving in this Action 503 can be performed, e.g. via the first link 141.

[0153] In some embodiments, the receiving in this Action 503 can be performed based on one or more conditions. The one or more conditions can comprise a load of the network node 110 or the wireless communication network 100 when performing the random access procedure.

[0154] The receiving in this Action 503 can be performed in accordance with the one or more first parameters based on one or more conditions.

[0155] As an overview of the above, the embodiments herein can be understood to enable separate configuration of UEs with restricted characteristics, e.g. Reduced Capability (RedCap) UEs, for random access procedures. In this way, differentiation can be enabled and access can be made more restrictive for RedCap UEs compared to legacy / full capability UEs which are typically higher priority.

[0156] Particular embodiments disclosed herein can provide one or more of the following technical advantages, which can be summarized as follows. Embodiments herein can be understood to introduce a mechanism for protecting the performance of legacy / normal capability UEs in a system when RedCap UEs can be introduced.

[0157] Figure 4 The first wireless device 131 can comprise two different examples of arrangements to perform the method actions described above for Figure 6 In some embodiments, the first wireless device 131 can comprise the following arrangement illustrated in panel a) and b), respectively. The first wireless device 131 can be understood to be for handling access to the wireless communication network 100. The first wireless device 131 can be understood to be configured to operate in the wireless communication network 100. Figure 6 In some embodiments, the first wireless device 131 can comprise the following arrangement illustrated in panel a) and b), respectively. The first wireless device 131 can be understood to be for handling access to the wireless communication network 100. The first wireless device 131 can be understood to be configured to operate in the wireless communication network 100.

[0158] A number of embodiments are included herein. Components from one embodiment can be assumed to be present in another embodiment by default, and it will be apparent to those skilled in the art how these components can be used in other example embodiments. The detailed description of certain sections below corresponds to the same references provided above in relation to the actions described for the first wireless device 131, and are therefore not repeated here. For example, the wireless device 130 can be configured as a RedCap UE.

[0159] In Figure 6 Optional units are indicated using dashed boxes.

[0160] The first wireless device 131 is configured to perform the transmission of action 403, e.g. by means of a transmitting unit 601 within the first wireless device 131, configured to transmit the first message to the network node 110 as part of a random access procedure for accessing the wireless communication network 100. The first wireless device 131 is configured to have one or more first characteristics configured to be limited in relation to one or more second characteristics of one or more second wireless devices 132. The transmission is configured to be performed in accordance with one or more first parameters. The one or more first parameters are configured to be different from one or more second parameters configured to be allowed to be used in the wireless communication network 100 by the one or more second wireless devices 132 when performing random access.

[0161] In some embodiments, the transmission can be configured to be performed based on one or more conditions. The one or more conditions can be configured to comprise a load of the network node 110 or the wireless communication network 100 when performing the random access procedure.

[0162] The one or more first parameters can be configured to comprise at least one of i) a smaller set of preambles to select from to transmit to the network node 110, ii) a shorter preamble space for Msgl transmission to the network node 110, iii) less frequent PRACH resources, iv) a longer back-off time, v) a lower maximum number of RA attempts, vi) a reduced power control, vii) a lower priority of licensed access, and viii) a lower maximum number of Msg3 transmissions, relative to the one or more second parameters.

[0163] The first wireless device 131 can be configured to perform the transmitting of action 401, e.g. by means of a transmitting unit 601 within the first wireless device 131, configured to transmit the first indication to the network node 110. The first indication can be configured to indicate that the first wireless device 131 has one or more first characteristics configured to be limited relative to one or more second characteristics of one or more second wireless devices 132.

[0164] The first wireless device 131 can be configured to perform the obtaining of action 402, e.g. by means of an obtaining unit 602 configured to obtain the second indication from at least one of the network node 110 and a memory of the first wireless device 131. The second indication can be configured to indicate at least one of i) the one or more first parameters, and ii) the one or more conditions.

[0165] In some embodiments, the one or more first parameters can be configured to indicate one of one or more absolute values, one or more offsets of other one or more values, and one or more factors to be applied to other one or more values.

[0166] In some embodiments, the second indication configured to be obtained can be configured to be comprised in a RRC configuration message.

[0167] The second indication can be configured to be comprised in one of a RACH-ConfigCommonRedcap information element, IE, a RA-Prioritization IE, a RACH-ConfigGeneric IE, and a RRCSetupRequest message.

[0168] The first wireless device 131 can comprise further units 603.

[0169] The one or more processors can be configured to perform the obtaining of action 402, e.g. by means of an obtaining unit 602 configured to obtain the second indication from at least one of the network node 110 and a memory of the first wireless device 131. The second indication can be configured to indicate at least one of i) the one or more first parameters, and ii) the one or more conditions. Figure 6The embodiments in the first wireless device 131 herein can be implemented in the processor 604 in the first wireless device 131 as described above by means of a computer program code 605, as well as by means of the computer program code for performing the functions and actions of the embodiments herein. As used herein, a processor can be understood to be a hardware component. The above-mentioned computer program code can also be provided as a computer program product, e.g. in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the first wireless device 131. One such carrier can be in the form of a CD ROM disc. However, the carrier can also be distributed over the Internet. Also, the computer program code can be provided as pure program code on a server and downloaded to the first wireless device 131.

[0170] The first wireless device 131 can further comprise a memory 605 comprising one or more storage units. The memory 605 is arranged to store obtained information, store data, configurations, schedules and applications, etc., which when executed in the first wireless device 131 perform the methods herein.

[0171] In some embodiments, the first wireless device 131 can receive information, e.g. from the network node 110, through a receiving port 606. In some embodiments, the receiving port 606 can be connected to one or more antennas in the first wireless device 131, e.g. In other embodiments, the first wireless device 131 can receive information from another structure in the wireless communication network 100 through the receiving port 606. Since the receiving port 606 can be in communication with the processor 604, the receiving port 606 can then send the received information to the processor 604. The receiving port 606 can also be configured to receive other information.

[0172] The processor 604 in the first wireless device 131 can also be configured to send information, e.g. to the network node 110 or to another structure in the wireless communication network 100, through a sending port 607, which can be in communication with the processor 604 and the memory 605.

[0173] The skilled person will also appreciate that the different units 601-603 described above can refer to a combination of analog and digital modules and / or one or more processors configured with software and / or firmware, e.g. stored in memory, that when executed by the one or more processors, e.g. the processor 604, perform as described above. One or more of these processors, as well as the other digital hardware, can be included in a single application-specific integrated circuit (ASIC), or one or more processors and various digital hardware can be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).

[0174] Furthermore, in some embodiments, the different units 601-603 described above can be implemented as one or more applications running on one or more processors (e.g., processor 604).

[0175] Therefore, the methods for the first wireless device 131 according to the embodiments described herein can be implemented by means of a computer program 608 product including instructions (i.e., software code portions) that, when executed on at least one processor 604, cause at least one processor 604 to perform the actions described herein performed by the first wireless device 131. The computer program 608 product can be stored on a computer-readable storage medium 609. The computer-readable storage medium 609 on which the computer program 608 is stored can include instructions that, when executed on at least one processor 604, cause at least one processor 604 to perform the actions described herein performed by the first wireless device 131. In some embodiments, the computer-readable storage medium 609 can be a non-transitory computer-readable storage medium, such as a CD-ROM or Memory Stick. In other embodiments, the computer program 608 product can be stored on a carrier containing the computer program 608 just described, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium 609 as described above.

[0176] The first wireless device 131 may include a communication interface configured to facilitate communication between the first wireless device 131 and other nodes or devices (e.g., network node 110). This interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface according to appropriate standards.

[0177] In other embodiments, the first wireless device 131 may include Figure 6 The following arrangement is shown in b. The first wireless device 131 may include processing circuitry 604 (e.g., one or more processors, such as processor 604 in the first wireless device 131) and memory 605. The first wireless device 131 may also include radio circuitry 610, which may include, for example, a receive port 606 and a transmit port 607. The processing circuitry 604 may be configured or operable to interact with... Figure 4 The method described in a similar manner is used to execute according to... Figure 4 The method of operation. Radio circuit 610 can be configured to establish and maintain at least a wireless connection with network node 110. In this document, circuitry can be understood as hardware components.

[0178] Therefore, embodiments herein also relate to a first wireless device 131, which includes processing circuitry 604 and a memory 605 containing instructions executable by the processing circuitry 604, thereby enabling the first wireless device 131 to perform, for example, the instructions described herein.Figure 7 The actions described above with respect to the first wireless device 131.

[0179] Figure 5 Two different examples of arrangements that the network node 110 can comprise to perform the method actions described above with respect to the first wireless device 131 are illustrated in panels a) and b), respectively. In some embodiments, the network node 110 can comprise the following arrangement illustrated in panel a). The network node 110 can be understood to be for handling access to the wireless communication network 100. The network node 110 can be understood to be configured to operate in the wireless communication network 100. Figure 7 Figure 7 a). The network node 110 can be understood to be for handling access to the wireless communication network 100. The network node 110 can be understood to be configured to operate in the wireless communication network 100.

[0180] A number of embodiments are included herein. Components from one embodiment can by default be assumed to be present in another embodiment, and it will be apparent to those skilled in the art how such components can be used in other example embodiments. The detailed description of certain sections below corresponds to the same references provided above with respect to the actions described for the first network node 111, and is therefore not repeated here. For example, the wireless device 130 can be configured as a RedCap UE.

[0181] In Figure 7 Optional units are indicated with dashed boxes.

[0182] The network node 110 can be configured to perform the receiving of action 503, e.g. by means of a receiving unit 701 within the network node 110, configured to receive, from the first wireless device 131, the first message as part of a random access procedure for accessing the wireless communication network 100. The first wireless device 131 is configured to have one or more first characteristics configured to be limited in relation to one or more second characteristics of one or more second wireless devices 132. The receiving is configured to be performed in accordance with one or more first parameters. The one or more first parameters are configured to be different from one or more second parameters configured to be allowed to be used in the wireless communication network 100 by the one or more second wireless devices 132 when performing random access.

[0183] In some embodiments, the receiving can be configured to be performed based on one or more conditions. The one or more conditions can be configured to comprise a load of the network node 110 or the wireless communication network 100 when performing the random access procedure.

[0184] ​The one or more first parameters can be configured to comprise at least one of the following relative to one or more second parameters: i) a smaller set of preambles from which to select for transmission to the network node 110, ii) a shorter preamble space for Msgl transmission to the network node 110, iii) less frequent PRACH resources, iv) a longer back-off time, v) a lower maximum number of RA attempts, vi) a reduced power control, vii) a lower priority for licensed access, and viii) a lower maximum number of Msg3 transmissions.

[0185] The network node 110 can be configured to perform the receiving of action 501, e.g. by means of a receiving unit 601 within the network node 110, configured to receive, from the first wireless device 131, a first indication. The first indication can be configured to indicate that the first wireless device 131 has one or more first characteristics configured to be limited relative to one or more second characteristics of one or more second wireless devices 132.

[0186] The network node 110 can be configured to perform the transmitting of action 502, e.g. by means of a transmitting unit 602, configured to transmit, to the first wireless device 131, a second indication. The second indication can be configured to indicate at least one of the following: i) the one or more first parameters, and ii) the one or more conditions.

[0187] In some embodiments, the one or more first parameters can be configured to indicate one of the following: one or more absolute values, one or more offsets from other one or more values, and one or more factors to be applied to other one or more values.

[0188] In some embodiments, the second indication configured to be transmitted can be configured to be comprised in a RRC configuration message.

[0189] The second indication can be configured to be comprised in one of the following: a RACH-ConfigCommonRedcap information element, IE, a RA-Prioritization IE, a RACH-ConfigGeneric IE, and a RRCSetupRequest message.

[0190] Other units 703 can be comprised in the network node 110.

[0191] The one or more processors (e.g. the processing unit 701) can be configured to perform the receiving of action 501, the transmitting of action 502, and / or the determining of action 503. Figure 7The embodiments in the network node 110 herein can be implemented through a processor 704, such as shown in the network node 110, together with computer program code for performing the functions and actions of the embodiments herein. As used herein, processor can be understood to mean hardware components. The computer program code mentioned above can further be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the network node 110. One such carrier can be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code can furthermore be provided as pure program code on a server and downloaded to the network node 110.

[0192] The network node 110 can further comprise a memory 705, comprising one or more memory units. The memory 705 is arranged to store obtained information, store data, configurations, schedules and applications, etc., which when executed in the network node 110 perform the methods herein.

[0193] In some embodiments, the network node 110 can receive information, e.g., from the first wireless device 131 and / or the one or more second wireless devices 132, through a receive port 706. In some embodiments, the receive port 706 can be connected to, for example, one or more antennas in the network node 110. In other embodiments, the network node 110 can receive information through the receive port 706 from another structure in the wireless communication network 100. As the receive port 706 can be in communication with the processor 704, the receive port 706 can then transmit the received information to the processor 704. The receive port 706 can be further configured to receive other information.

[0194] The processor 704 in the network node 110 can be further configured to transmit information, e.g., to the first wireless device 131, the one or more second wireless devices 132, and / or to another structure in the wireless communication network 100, through a transmit port 707, which can be in communication with the processor 704 and the memory 705.

[0195] The skilled person would also understand that the different units 701-703 described above can refer to a combination of analog and digital modules and / or to one or more processors configured with software and / or firmware, e.g., stored in memory, that, when executed by the one or more processors, e.g., the processor 704, carry out the described functions. One or more of these processors, as well as the other digital hardware, can be included in a single application-specific integrated circuit (ASIC), or one or more processors and various digital hardware can be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).

[0196] Furthermore, in some embodiments, the different units 701-703 described above can be implemented as one or more applications running on one or more processors (e.g. the processor 704).

[0197] Hence, the methods according to the embodiments described herein for the network node 110 can be implemented by means of a computer program 708, comprising instructions (i.e., software code portions), which, when executed on at least one processor 704, cause the at least one processor 704 to carry out the actions described herein, as performed by the network node 110. The computer program 708 can be stored on a computer-readable storage medium 709. The computer-readable storage medium 709, having stored thereon the computer program 708, can comprise instructions which, when executed on at least one processor 704, cause the at least one processor 704 to carry out the actions described herein, as performed by the network node 110. In some embodiments, the computer-readable storage medium 709 can be a non-transitory computer-readable storage medium, e.g., a CD ROM disc or a memory stick. In other embodiments, the computer program 708 can be stored on a carrier medium which can comprise a computer-readable storage medium 709 as just described or a computer-readable storage medium 709 and a communication medium, as just described.

[0198] The network node 110 can comprise a communication interface configured to facilitate communication between the network node 110 and other nodes or devices, e.g., the first wireless device 131. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

[0199] In other embodiments, the network node 110 can comprise Figure 7 b the following arrangement. The network node 110 can comprise processing circuitry 704 (e.g., one or more processors, like the processor 704 in the network node 110) and a memory 705. The network node 110 can further comprise radio circuitry 710, which may, for example, comprise a receive port 706 and a transmit port 707. The processing circuitry 704 can be configured to, or operable to, perform the method actions according to Figure 5 a in a similar manner as described for Figure 5 The radio circuitry 710 can be configured to establish and maintain at least a wireless connection with the first wireless device 131 and / or one or more second wireless devices 132. In this context, circuitry can be understood as a hardware component. The processing circuitry 704 can be configured to, or operable to, perform the method actions according to

[0200] Accordingly, embodiments herein also relate to a network node 110 comprising a processing circuitry 704 and a memory 705, said memory 705 containing instructions executable by said processing circuitry 704, whereby the network node 110 is operative to perform the actions described herein, e.g. in Figure 8 the actions described in relation to the network node 110 herein.

[0201] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the technical field of the technology concerned unless explicitly defined otherwise herein and / or in the context of the respective term. All references to a / an / the [element, device, component, means, step, etc.] are to be interpreted openly as referring to one or more instances of said element, device, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed unless explicitly stated. Any of the embodiments disclosed herein can be applied to any other embodiments unless explicitly stated otherwise. Likewise, any advantage described in relation to one embodiment can also apply to any other embodiment, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0202] As used herein, the expression "at least one of: followed by a list of alternatives separated by commas and where the last alternative is preceded by the term "and" can be interpreted as meaning that only one of the alternatives of the list of alternatives can apply, that more than one of the alternatives of the list of alternatives can apply, or that all of the alternatives of the list of alternatives can apply. This expression can be interpreted as equivalent to the expression "at least one of: followed by a list of alternatives separated by commas and where the last alternative is preceded by the term "or".

[0203] Examples relating to embodiments herein

[0204] Example 1. A method performed by a first wireless device (131), the method for handling access to a wireless communication network (100), the method comprising:

[0205] - transmitting (403), to a network node (110), a first message as part of a random access procedure for accessing the wireless communication network (100), wherein:

[0206] i. the first wireless device (131) has one or more first characteristics that are limited with respect to one or more second characteristics of one or more second wireless devices (132), and

[0207] ii. performing the sending (403) according to one or more first parameters, the one or more first parameters being different from one or more second parameters allowed to be used by one or more second wireless devices (132) in the wireless communication network (100) when performing random access, based on one or more conditions.

[0208] Example 2. The method of example 1, wherein the one or more conditions comprise a load of the network node (110) or the wireless communication network (100) when performing the random access procedure.

[0209] Example 3. The method of any of examples 1-2, wherein the one or more first parameters comprise at least one of:

[0210] i. a smaller set of preambles from which to select for transmission to the network node (110),

[0211] ii. a shorter preamble space for Msgl transmission to the network node (110),

[0212] iii. less frequent physical random access channel, PRACH, resources,

[0213] iv. a longer back-off time,

[0214] v. a lower maximum number of random access, RA, attempts,

[0215] vi. a reduced power control,

[0216] vii. a lower priority for licensed access, and

[0217] viii. a lower maximum number of Msg3 transmissions.

[0218] Example 4. The method of any of examples 1-3, further comprising:

[0219] - sending (401) a first indication to the network node (110), the first indication indicating that the first wireless device (131) has one or more first characteristics that are limited relative to one or more second characteristics of one or more second wireless devices (132).

[0220] Example 5. The method of any of examples 1-4, further comprising:

[0221] - obtaining (402) a second indication from at least one of the network node (110) and a memory of the first wireless device (131), the second indication indicating at least one of:

[0222] i. the one or more first parameters, and

[0223] ii. one or more conditions.

[0224] Example 6. The method of example 5, wherein the one or more first parameters are indicated as one of:

[0225] - one or more absolute values,

[0226] - one or more offsets of the other one or more values, and

[0227] - one or more factors to be applied to the other one or more values.

[0228] Example 7. The method of any of examples 5-6, wherein the obtained second indication is comprised in a Radio Resource Control, RRC, configuration message.

[0229] Example 8. The method of example 7, wherein the second indication is comprised in one of:

[0230] - a RACH-ConfigCommonRedcap information element, IE,

[0231] - a RA-Prioritization IE,

[0232] - a RACH-ConfigGeneric IE, and

[0233] - a RRCSetupRequest message.

[0234] Example 9. The method of any of examples 1-8, wherein the wireless device (130) is a RedCap UE.

[0235] Example 10. A method performed by a network node (110), the method for handling access to a wireless communication network (100), the method comprising:

[0236] - receiving (503), from a first wireless device (131), a first message as part of a random access procedure for accessing the wireless communication network (100), wherein:

[0237] i. the first wireless device (131) has one or more first characteristics that are restricted with respect to one or more second characteristics of one or more second wireless devices (132), and

[0238] ii. Reception is performed (503) based on one or more conditions and according to one or more first parameters, which are different from one or more second parameters that are permitted to be used by one or more second wireless devices (132) in the wireless communication network (100) when performing random access.

[0239] Example 11. The method according to Example 10, wherein one or more conditions include the load of the network node (110) or the wireless communication network (100) during the execution of the random access procedure.

[0240] Example 12. The method according to any one of Examples 10-11, wherein, relative to one or more second parameters, one or more first parameters include at least one of the following:

[0241] i. Select from these smaller preamble groups to send to network node (110),

[0242] ii. A shorter preamble space for transmission to Msg1 in network node (110),

[0243] iii. Less frequent Physical Random Access Channel (PRACH) resources,

[0244] iv. Longer retreat time,

[0245] v. Lower maximum number of random access (RA) attempts.

[0246] vi. Reduced power control

[0247] vii. Lower priority for licensed access, and

[0248] viii. Lower maximum number of Msg3 transfers.

[0249] Example 13. The method according to any one of Examples 10-12 further includes:

[0250] - Receive (501) a first instruction from a first wireless device (131), the first instruction indicating that the first wireless device (131) has one or more first characteristics that are limited relative to one or more second characteristics of one or more second wireless devices (132).

[0251] Example 14. The method according to any one of Examples 10-13 further includes:

[0252] - Send (502) a second instruction to the first wireless device (131), the second instruction specifying at least one of the following:

[0253] i. One or more first parameters, and

[0254] ii. one or more conditions.

[0255] Example 15. The method of example 14, wherein the one or more first parameters are indicated as one of:

[0256] - one or more absolute values,

[0257] - one or more offsets of the other one or more values, and

[0258] - one or more factors to be applied to the other one or more values.

[0259] Example 16. The method of any one of examples 14-15, wherein the transmitted second indication is comprised in a radio resource control, RRC, configuration message.

[0260] Example 17. The method of example 16, wherein the second indication is comprised in one of:

[0261] - a RACH-ConfigCommonRedcap information element, IE,

[0262] - a RA-Prioritization IE,

[0263] - a RACH-ConfigGeneric IE, and

[0264] - a RRCSetupRequest message.

[0265] Example 18. The method of any one of examples 10-17, wherein the wireless device (130) is a RedCap UE.

[0266] Further extensions and variations

[0267] Figure 8 Telecommunication network connected via an intermediate network to a host computer according to some embodiments

[0268] Reference Figure 8According to an embodiment, a communication system includes a telecommunication network 810, such as a 3GPP-type cellular network, which comprises access networks 811, such as radio access networks, and a core network 814. The access network 811 comprises a plurality of network nodes, such as the network node 110. For example, base stations 812a, 812b, 812c, such as NBs, eNBs, gNBs or other types of wireless access points, each define a corresponding coverage area 813a, 813b, 813c. Each base station 812a, 812b, 812c is connectable to the core network 814 over a wired or wireless connection 815. The wireless communication network 100 includes a plurality of user devices, such as a first wireless device 131 and / or one or more second wireless devices 132. In Figure 8 In the example, a first UE 891 located in the coverage area 813c is configured to wirelessly connect to, or be paged by, the corresponding base station 812c. A second UE 892 in the coverage area 813a is wirelessly connectable to the corresponding base station 812a. While a plurality of UEs 891, 892 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 812. Either of the UEs 891, 892 is an example of the first wireless device 131 and / or the one or more second wireless devices 132.

[0269] The telecommunication network 810 is itself connected to a host computer 830, which can be embodied in hardware and / or software and can be embodied as a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 830 can be under the ownership or control of a service provider, or can be operated by the service provider or on behalf of the service provider. Connections 821 and 822 between the telecommunication network 810 and the host computer 830 can extend directly from the core network 814 to the host computer 830 or can go via an optional intermediate network 820. The intermediate network 820 can be one of, or a combination of, public, private or hosted networks; it can be an intranet, an extranet, a LAN, a MAN, a WAN or

[0270] In its entirety, Figure 9The communication system enables connectivity between the connected UEs 891, 892 and the host computer 830. The connectivity can be described as an over-the-top (OTT) connection 850. The host computer 830 and the connected UEs 891, 892 are configured to communicate using the OTT connection 850 via the access network 811, the core network 814, any intermediate network 820 and possible further infrastructure (not shown), as will be discussed below. The OTT connection 850 can be transparent in the sense that the participating devices through which the OTT connection 850 passes are unaware of the

[0271] With respect to the next described Figure 9 , 10 , 11, 12 and 13, it can be understood that the UE is an example of the first wireless device 131 and / or the one or more second wireless devices 132, and any description provided for the UE equally applies to the first wireless device 131 and / or the one or more second wireless devices 132. It can also be understood that the base station is an example of the network node 110, and any description provided for the base station equally applies to the network node 110.

[0272] Figure 9 : Host computer communicating via a base station with a user equipment over a partial wireless connection, according to some embodiments.

[0273] According to embodiments, there will now be described Figure 9Example implementations of the first wireless device 131 and / or the one or more second wireless devices 132 (e.g., UEs), the network node 110 (e.g., base station), and the host computer discussed in the preceding paragraphs are described. In a communication system 900 (e.g., the wireless communication network 100), a host computer 910 comprises hardware 915 enabling communication with a communication device 910. The hardware 915 can comprise

[0274] The communication system 900 further includes a network node 110 (illustrated in Figure 9 as a base station 920) provided in a telecommunication system and comprising hardware 925 enabling it to communicate with the host computer 910 and with the UE 930. The hardware 925 can include a communication interface 926 for Figure 9 establishing and maintaining at least a wireless connection 970 with a first wireless device 131 and / or one or more second wireless devices 132 (illustrated in Figure 9 as UEs 930) located in a coverage area served by the base station 920 (not shown in Figure 9 ). The communication interface 926 can be configured to facilitate connection 960 to the host computer 910. The connection 960 can be direct or it can pass through a core network (not shown in the figure) of the telecommunication system and / or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 925 of the base station 920 further includes processing circuitry 928, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The base station 920 further has software 921 stored internally or accessible via an external connection.

[0275] The communication system 900 further includes the UE 930 already referred to. The UE 930 has hardware 935 that can include a radio interface 937 configured to set up and maintain a wireless connection 970 with a base station serving a coverage area in which the UE 930 currently is located. The hardware 935 of the UE 930 further includes processing circuitry 938, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE 930 further comprises software 931, which is stored in or accessible by the UE 930 and executable by the processing circuitry 938. The software 931 includes a client application 932. The client application 932 can be operable to provide a service to a human or non-human user via the UE 930, with the support of the host computer 910. In the host computer 910, an executing host application 912 can communicate with the executing client application 932 via the OTT connection 950 terminating at the UE 930 and the host computer 910. In providing the service to the user, the client application 932 can receive request data from the host application 912 and provide user data in response to the request data. The OTT connection 950 can carry both the request data and the user data. The client application 932 can interact with the user to generate the user-provided user data.

[0276] It is noted that Figure 8 the host computer 910, the base station 920, and the UE 930 illustrated in Figure 9 may be similar or identical to the host computer 830, one of the base stations 812a, 812b, 812c, and one of the UEs 891, 892 of Figure 8 , respectively. That is, the inner workings of these entities can be as Figure 9 illustrated in

[0277] In Figure 4 , the OTT connection 950 has been drawn abstractly to illustrate the communication between the host computer 910 and the UE 930 via the base station 920, without any reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure can determine the routing, which it can be configured to hide from the UE 930 or from the service provider operating the host computer 910, or both. While the OTT connection 950 is active, the network infrastructure can further take decisions that cause the routing to change (e.g., based on load balancing considerations or reconfiguration of the network).

[0278] The wireless connection 970 between the UE 930 and the base station 920 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UEs 930 using the OTT connection 950, in which the wireless connection 970 forms the last segment. More precisely, the teachings of these embodiments can improve the latency, signaling overhead, and service interruption, thereby providing benefits such as reduced user waiting time, better responsiveness, and extended battery lifetime.

[0279] A measurement procedure can be implemented for the purpose of monitoring the data rate, latency, and other factors on which the one or more embodiments improve. There can also be an optional network functionality for reconfiguring the OTT connection 950 between the host computer 910 and the UE 930, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 950 can be implemented in the software 911 and the hardware 915 of the host computer 910 or in the software 931 and the hardware 935 of the UE 930, or both. In embodiments, sensors (not shown) can be deployed in or in association with the communication devices through which the OTT connection 950 passes. The sensors can participate in the measurement procedure by providing values of the above-illustrated monitoring quantities, or physical quantities from which the software 911, 931 can compute or estimate the monitoring quantities. The reconfiguring of the OTT connection 950 can include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station 920, and it can be unknown or imperceptible to the base station 920. Such procedures and functionalities are known, specified, or recommended in the art for example by the 3GPP

[0280] The first wireless device 131 embodiments pertain to Figure 6 , Figures 8-13 and Figure 6 .

[0281] The first wireless device 131 can comprise an interface unit to facilitate communications between the first wireless device 131 and other nodes or devices, such as the network node 110, the host computer 910, or any other node. In some particular examples, the interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

[0282] The first wireless device 131 can comprise an arrangement as shown in Figure 9 or Figure 5 .

[0283] The first wireless device 131 can further be configured to transmit user data to the host application in the host computer 910, e.g., via another link 960.

[0284] Embodiments of the network node 110 relate to Figure 7 , Figures 8-13 and Figure 7 .

[0285] The network node 110 can comprise an interface to facilitate communication between the network node 110 and other nodes or devices (e.g., the first wireless device 131, the one or more second wireless devices 132, the host computer 910, or any other node). The interface may, for example, include a transceiver configured to transmit and to receive radio signals over a

[0286] The network node 110 can comprise an arrangement as illustrated in Figure 9 or Figure 10 .

[0287] The network node 110 can further be configured to transmit user data to the host application in the host computer 910, e.g., via another link 960.

[0288] Figure 10 Method implemented in a communication system including a host computer, a base station and a user equipment, according to some embodiments

[0289] Figure 8 is a flow chart illustrating a method implemented in a communication system, according to one embodiment. The communication system includes a host computer, a base station and a UE which can be those described Figure 9 and Figure 10 with reference to Figure 11 for simplicity of the present disclosure only. In step 1010, the host computer provides user data. In sub-step 1011 (which can be optional) of step 1010, the host computer provides the user data by executing a host application. In step 1020, the host computer initiates a transmission carrying the user data to the UE. In step 1030 (which can be optional), the base station transmits to the UE the user data carried in the transmission initiated by the host computer, according to the teachings of the embodiments described throughout this disclosure. In step 1040 (which can also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0290] Figure 11 Method implemented in a communication system including a host computer, a base station and a user equipment, according to some embodiments

[0291] Figure 8 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, and a UE, which may be referenced... Figure 9 and Figure 11 The host computer, base station, and UE are described. For the sake of simplicity in this disclosure, this section only includes descriptions of... Figure 12 Refer to the accompanying drawings. In step 1110 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 1120, the host computer initiates a transmission carrying user data to the UE. Based on the teachings of the embodiments described throughout this disclosure, the transmission can be performed via a base station. In step 1130 (which may be optional), the UE receives the user data carried in the transmission.

[0292] Figure 12 Methods implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments

[0293] Figure 8 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, and a UE, which may be referenced... Figure 9 and Figure 12 The host computer, base station, and UE are described. For the sake of simplicity in this disclosure, this section only includes descriptions of... Figure 13 Referring to the accompanying drawings. In step 1210 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1220, the UE provides user data. In sub-step 1221 of step 1220 (which may be optional), the UE provides user data by executing a client application. In sub-step 1211 of step 1210 (which may be optional), 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 sub-step 1230 (which may be optional). In step 1240 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.

[0294] Figure 13 Methods implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments

[0295] Figure 8is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described with reference to Figure 9 and Figure 13 the host computer, base station and UE described with reference to Other numbered embodiments the accompanying drawings. In step 1310 (which can be optional), in accordance with the teachings of embodiments described throughout the present disclosure, the base station receives user data from the UE. In step 1320 (which can be optional), the base station initiates transmission of the received user data to the host computer. In step 1330 (which can be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0296] Any appropriate steps, methods, features, functions, or benefits disclosed herein can be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus can comprise a number of these functional units. These functional units can be implemented via processing circuitry, which can include one or more microprocessor or microcontrollers, as well as other digital hardware, which can include digital signal processors (DSPs), special-purpose computer chips, or the like. The processing circuitry can be configured to execute program code stored in memory, which can include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data

[0297] The term "unit" can have conventional meaning in the electronic, electrical, and / or computer hardware arts, and can include, for example, electrical and / or electronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions, etc. that are arranged to perform the

[0298] ​

[0299] 1. A base station configured to communicate with a user equipment (UE), the base station comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as being performed by the network node 110.

[0300] 5. A communication system including a host computer, the host computer comprising:

[0301] processing circuitry configured to provide user data; and

[0302] a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),

[0303] wherein the cellular network comprises a base station having radio interface and processing circuitry, the base station's processing circuitry configured to perform one or more actions described herein as performed by the network node 110.

[0304] 6. The communication system of embodiment 5, further including the base station.

[0305] 7. The communication system of embodiment 6, further including the UE, wherein the UE is configured to communicate with the base station.

[0306] 8. The communication system of embodiment 7, wherein:

[0307] the processing circuitry of the host computer is configured to execute the host application, thereby providing the user data; and

[0308] the UE includes processing circuitry configured to execute a client application associated with the host application.

[0309] 11. A method implemented in a base station, comprising one or more actions described herein as performed by the network node 110.

[0310] 15. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0311] at the host computer, providing user data; and

[0312] at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs one or more actions described herein as performed by the network node 110.

[0313] 16. The method of embodiment 15, further comprising:

[0314] at the base station, transmitting the user data.

[0315] 17. The method of embodiment 16, wherein the user data is provided at the host computer by execution of a host application, the method further comprising:

[0316] at the UE, executing a client application associated with the host application.

[0317] 21. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as being performed by the first wireless device 131.

[0318] 25. A communication system including a host computer comprising:

[0319] processing circuitry configured to provide user data; and

[0320] a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),

[0321] wherein the UE comprises a radio interface and processing circuitry configured to perform one or more of the actions described herein as being performed by the first wireless device 131.

[0322] 26. A communication system according to embodiment 25, further including the UE.

[0323] 27. A communication system according to embodiment 26, wherein the cellular network further includes a base station configured to communicate with the UE.

[0324] 28. A communication system according to embodiment 26 or 27, wherein:

[0325] the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

[0326] the processing circuitry of the UE is configured to execute a client application associated with the host application.

[0327] 31. A method implemented in a user equipment (UE), comprising one or more of the actions described herein as being performed by the first wireless device 131.

[0328] 35. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

[0329] at the host computer, providing user data; and

[0330] at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs one or more of the actions described herein as being performed by the first wireless device 131.

[0331] 36. A method according to embodiment 35, further including:

[0332] at the UE, receiving the user data from the base station.

[0333] 41. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry, the processing circuitry configured to perform one or more of the actions described herein as being performed by the first wireless device 131.

[0334] 45. A communication system including a host computer comprising:

[0335] a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,

[0336] wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform one or more of the actions described herein as being performed by the first wireless device 131.

[0337] 46. A communication system according to embodiment 45, further including the UE.

[0338] 47. A communication system according to embodiment 46, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward the user data carried by transmissions from the UE to the base station to the host computer.

[0339] 48. A communication system according to embodiment 46 or 47, wherein:

[0340] the host computer’s processing circuitry is configured to execute a host application; and

[0341] the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

[0342] 49. A communication system according to embodiment 46 or 47, wherein:

[0343] the host computer’s processing circuitry is configured to execute a host application, thereby providing request data; and

[0344] the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

[0345] 51. A method implemented in a user equipment (UE), comprising one or more of the actions described herein as being performed by the first wireless device 131.

[0346] 52. A method according to embodiment 51, further comprising:

[0347] providing user data; and

[0348] forwarding the user data to a host computer via a transmission to a base station.

[0349] 55. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0350] receiving, at the host computer, user data transmitted by the UE to the base station, wherein the UE performs one or more actions described herein as performed by the first wireless device 131.

[0351] 56. The method of embodiment 55, further including:

[0352] providing, at the UE, the user data to the base station.

[0353] 57. The method of embodiment 56, further including:

[0354] executing, at the UE, a client application, thereby providing the user data to be transmitted; and

[0355] executing, at the host computer, a host application associated with the client application.

[0356] 58. The method of embodiment 56, further including:

[0357] executing, at the UE, a client application; and

[0358] receiving, at the UE, input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application,

[0359] wherein the client application provides the user data to be transmitted in response to the input data.

[0360] 61. A base station configured to communicate with a user equipment (UE), the base station comprising a radio interface and processing circuitry configured to perform one or more actions described herein as performed by the network node 110.

[0361] 65. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform one or more actions described herein as performed by the network node 110.

[0362] 66. The communication system of embodiment 65, further including the base station.

[0363] 67. The communication system of embodiment 66, further including the UE, wherein the UE is configured to communicate with the base station.

[0364] 68. The communication system of embodiment 67, wherein:

[0365] the processing circuitry of the host computer is configured to execute the host application;

[0366] the UE is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0367] 71. A method implemented in a base station, comprising one or more acts described herein as being performed by a network node 110.

[0368] 75. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0369] at the host computer, receiving user data originating from a transmission received by the base station from a UE, wherein the UE performs one or more acts described herein as being performed by a first wireless device 131.

[0370] 76. The method of embodiment 75, further comprising:

[0371] at the base station, receiving the user data from the UE.

[0372] 77. The method of embodiment 76, further comprising:

[0373] at the base station, initiating transmission of the received user data to the host computer.

[0374] References

[0375] 1. TS 38.331, NR RRC Protocol Specification v15.8.0

[0376] 2. TS 38.321, NR; Medium Access Control (MAC) protocol specification v16.0.0

Claims

1. A method performed by a first wireless device (131) for processing access to a wireless communication network (100), the method comprising: - Send a first message (403) to network node (110) as part of a random access procedure for accessing the wireless communication network (100), wherein: i. The first wireless device (131) has one or more first characteristics that are limited relative to one or more second characteristics of one or more second wireless devices (132), and ii. The transmission (403) is performed according to one or more first parameters, which are different from one or more second parameters permitted for use by the one or more second wireless devices (132) in the wireless communication network (100) during random access, wherein, relative to the one or more second parameters, the one or more first parameters include at least one of the following: a) Longer retreat time, b) Lower maximum number of random access (RA) attempts c) Reduced power control d) Lower priority of licensed access, and e) Lower maximum number of Msg3 transmissions.

2. The method according to claim 1, wherein, The transmission (403) is performed based on one or more conditions, wherein the one or more conditions include the load of the network node (110) or the wireless communication network (100) during the execution of the random access procedure.

3. The method according to any one of claims 1-2, wherein, In relation to the one or more second parameters, the one or more first parameters further include at least one of the following: i. Select from these smaller preamble groups to send to the network node (110), ii. A shorter preamble space for transmission to Msg1 of the network node (110), and iii. Less frequent Physical Random Access Channel (PRACH) resources.

4. The method according to any one of claims 1-2, further comprising: - Send (401) a first indication to the network node (110), the first indication indicating that the first wireless device (131) has one or more first characteristics that are limited relative to one or more second characteristics of one or more second wireless devices (132).

5. The method according to any one of claims 1-2, further comprising: - Obtain (402) a second instruction from at least one of the memories of the network node (110) and the first wireless device (131), the second instruction indicating at least one of the following: i. the one or more first parameters, and ii. The one or more conditions mentioned above.

6. The method according to claim 5, wherein, The one or more first parameters are indicated as one of the following: - One or more absolute values, - One or more offsets of other values, and - One or more factors to be applied to the other one or more values.

7. The method according to claim 5, wherein, The second instruction is obtained from the network node (110), and the obtained second instruction is included in the Radio Resource Control (RRC) configuration message.

8. The method according to claim 7, wherein, The second instruction is included in one of the following: -RACH-ConfigCommonRedcap information element IE, -RA-Prioritization IE, -RACH-ConfigGeneric IE, and -RRCSetupRequest message.

9. The method according to any one of claims 1-2, wherein, The first wireless device (131) is RedCapUE.

10. A method performed by a network node (110) for processing access to a wireless communication network (100), the method comprising: - Receive (503) a first message from the first wireless device (131) as part of a random access procedure for accessing the wireless communication network (100), wherein: i. The first wireless device (131) has one or more first characteristics that are limited relative to one or more second characteristics of one or more second wireless devices (132), and ii. The reception (503) is performed according to one or more first parameters, which are different from one or more second parameters permitted for use by the one or more second wireless devices (132) in the wireless communication network (100) during random access, wherein, relative to the one or more second parameters, the one or more first parameters include at least one of the following: a) Longer retreat time, b) Lower maximum number of random access (RA) attempts c) Reduced power control d) Lower priority of licensed access, and e) Lower maximum number of Msg3 transmissions.

11. The method according to claim 10, wherein, The reception (503) is performed based on one or more conditions, wherein the one or more conditions include the load of the network node (110) or the wireless communication network (100) during the execution of the random access procedure.

12. The method according to any one of claims 10-11, wherein, In relation to the one or more second parameters, the one or more first parameters further include at least one of the following: i. Select from these smaller preamble groups to send to the network node (110), ii. A shorter preamble space for transmission to Msg1 of the network node (110), and iii. Less frequent Physical Random Access Channel (PRACH) resources.

13. The method according to any one of claims 10-11, further comprising: - Receive (501) a first indication from the first wireless device (131), the first indication indicating that the first wireless device (131) has the one or more first characteristics that are limited relative to one or more second characteristics of one or more second wireless devices (132).

14. The method according to any one of claims 10-11, further comprising: - Send (502) a second instruction to the first wireless device (131), the second instruction specifying at least one of the following: i. the one or more first parameters, and ii. The one or more conditions mentioned above.

15. The method according to claim 14, wherein, The one or more first parameters are indicated as one of the following: - One or more absolute values, - One or more offsets of other values, and - One or more factors to be applied to the other one or more values.

16. The method of claim 14, wherein, The second instruction sent is included in the Radio Resource Control (RRC) configuration message.

17. The method according to claim 16, wherein, The second instruction is included in one of the following: -RACH-ConfigCommonRedcap information element IE, -RA-Prioritization IE, -RACH-ConfigGeneric IE, and -RRCSetupRequest message.

18. The method according to any one of claims 10-11, wherein, The first wireless device (131) is RedCapUE.

19. A first wireless device (131) for processing access to a wireless communication network (100), the first wireless device (131) being configured to: - A first message is sent to network node (110) as part of a random access procedure for accessing the wireless communication network (100), wherein: i. The first wireless device (131) is configured to have one or more first characteristics that are configured to be limited relative to one or more second characteristics of one or more second wireless devices (132), and ii. The transmission is configured to be performed according to one or more first parameters, which are configured to differ from one or more second parameters configured to be permitted for use by the one or more second wireless devices (132) in the wireless communication network (100) during random access, wherein, relative to the one or more second parameters, the one or more first parameters are configured to include at least one of the following: a) Longer retreat time, b) Lower maximum number of random access (RA) attempts c) Reduced power control d) Lower priority of licensed access, and e) Lower maximum number of Msg3 transmissions.

20. The first wireless device (131) according to claim 19, wherein, The transmission is configured to be performed based on one or more conditions, wherein the one or more conditions are configured to include the load of the network node (110) or the wireless communication network (100) during the execution of the random access procedure.

21. The first wireless device (131) according to any one of claims 19-20, wherein, In relation to the one or more second parameters, the one or more first parameters are configured to further include at least one of the following: i. Select from these smaller preamble groups to send to the network node (110), ii. A shorter preamble space for transmission to Msg1 of the network node (110), and iii. Less frequent Physical Random Access Channel (PRACH) resources.

22. The first wireless device (131) according to any one of claims 19-20 is further configured to: - Send a first indication to the network node (110), the first indication being configured to indicate that the first wireless device (131) has the one or more first characteristics that are configured to be limited relative to one or more second characteristics of one or more second wireless devices (132).

23. The first wireless device (131) according to any one of claims 19-20 is further configured to: - Obtain a second indication from at least one of the memories of the network node (110) and the first wireless device (131), the second indication being configured to indicate at least one of the following: i. the one or more first parameters, and ii. The one or more conditions mentioned above.

24. The first wireless device (131) according to claim 23, wherein, The one or more first parameters are configured to be indicated as one of the following: - One or more absolute values, - One or more offsets of other values, and - One or more factors to be applied to the other one or more values.

25. The first wireless device (131) according to claim 23, wherein, The second indication is configured to be obtained from the network node (110), and wherein the second indication, which is configured to be obtained, is configured to be included in the Radio Resource Control (RRC) configuration message.

26. The first wireless device (131) according to claim 25, wherein, The second instruction is configured to be included in one of the following: -RACH-ConfigCommonRedcap information element IE, -RA-Prioritization IE, -RACH-ConfigGeneric IE, and -RRCSetupRequest message.

27. The first wireless device (131) according to any one of claims 19-20, wherein, The first wireless device (131) is configured as a RedCap UE.

28. A network node (110) for processing access to a wireless communication network (100), the network node (110) being configured to: - Receive a first message from the first wireless device (131) as part of a random access procedure for accessing the wireless communication network (100), wherein: i. The first wireless device (131) is configured to have one or more first characteristics that are configured to be limited relative to one or more second characteristics of one or more second wireless devices (132), and ii. The receiving is configured to be performed according to one or more first parameters, the one or more first parameters being configured to differ from one or more second parameters that are permitted to be used by the one or more second wireless devices (132) in the wireless communication network (100) during random access, wherein, relative to the one or more second parameters, the one or more first parameters are configured to include at least one of the following: a) Longer retreat time, b) Lower maximum number of random access (RA) attempts c) Reduced power control d) Lower priority of licensed access, and e) Lower maximum number of Msg3 transmissions.

29. The network node (110) according to claim 28, wherein, The reception is configured to be performed based on one or more conditions, wherein the one or more conditions are configured to include the load of the network node (110) or the wireless communication network (100) during the execution of the random access procedure.

30. The network node (110) according to any one of claims 28-29, wherein, In relation to the one or more second parameters, the one or more first parameters are configured to further include at least one of the following: i. Select from these smaller preamble groups to send to the network node (110), ii. A shorter preamble space for transmission to Msg1 of the network node (110), and iii. Less frequent Physical Random Access Channel (PRACH) resources.

31. The network node (110) according to any one of claims 28-29 is further configured to: - Receive a first indication from the first wireless device (131), the first indication being configured to indicate that the first wireless device (131) has the one or more first characteristics that are configured to be limited relative to one or more second characteristics of one or more second wireless devices (132).

32. The network node (110) according to any one of claims 28-29 is further configured to: - Send a second instruction to the first wireless device (131), the second instruction being configured to specify at least one of the following: i. the one or more first parameters, and ii. The one or more conditions mentioned above.

33. The network node according to claim 32, wherein, The one or more first parameters are configured to be indicated as one of the following: - One or more absolute values, - One or more offsets of other values, and - One or more factors to be applied to the other one or more values.

34. The network node (110) according to claim 32, wherein, The second indication, configured to be sent, is configured to be included in the Radio Resource Control (RRC) configuration message.

35. The network node (110) according to claim 34, wherein, The second instruction is configured to be included in one of the following: -RACH-ConfigCommonRedcap information element IE, -RA-Prioritization IE, -RACH-ConfigGeneric IE, and -RRCSetupRequest message.

36. The network node (110) according to any one of claims 28-29, wherein, The first wireless device (131) is configured as a RedCap UE.

Images