Device, radio network node and methods performed therein
By allocating both CFRA and CBRA resources to devices, the mechanism addresses inefficiencies in re-access for low-power and zero-energy devices, enhancing network performance and reducing signaling overhead.
Patent Information
- Application Number
- PCT/SE2026/050292
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-05
- Filing Date
- 2026-04-30
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication technologies face challenges in efficiently handling re-access for devices that fail contention resolution or have low energy, particularly in scenarios involving zero-energy (ZE) and low-power wide area (LPWA) devices, leading to collisions, high energy consumption, and inefficient data transmission.
A mechanism is introduced where a radio network node allocates both contention-free random access (CFRA) and contention-based random access (CBRA) resources to devices, indicated through DL scheduling messages, to facilitate efficient re-access for devices that have previously succeeded or failed in contention, reducing signaling overhead and energy consumption.
This approach reduces R2D signaling, DL signaling, and paging overhead by collectively allocating CFRA and CBRA resources, ensuring deterministic access and minimizing collisions for low-power and zero-energy devices, thereby optimizing network performance.
Smart Images

Figure SE2026050292_12112026_PF_FP_ABST
Abstract
Description
[0001] DEVICE, RADIO NETWORK NODE AND METHODS PERFORMED THEREIN
[0002] TECHNICAL FIELD
[0003] Embodiments herein relate to a device, a radio network node, and methods performed therein for communication. Furthermore, a computer program and a computer readable storage medium are also provided herein. In particular, embodiments herein relate to handling access of a device to a wireless communications network.
[0004] BACKGROUND
[0005] In a typical wireless communications network, user equipments (UE), also known as wireless communication devices, mobile stations, stations (STA) and / or wireless devices, communicate via for example a Radio Access Network (RAN) with one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cell areas, with each service area or cell area being served by radio network node such as an access node e.g. a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB. The service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the radio network node. The radio network node communicates over a downlink (DL) to the UE and the UE communicates over an uplink (UL) to the radio network node.
[0006] A Universal Mobile Telecommunications System (UMTS) is a third-generation telecommunications network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and / or High-Speed Packet Access (HSPA) for communication with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for present and future generation networks and UTRAN specifically and investigate enhanced data rate and radio capacity. In some RANs, e.g. as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of theplural radio network nodes connected thereto. The RNCs are typically connected to one or more core networks.
[0007] Specifications for the Evolved Packet System (EPS) have been completed within the 3GPP and this work continues in the coming 3GPP releases, such as 5G, for example New Radio (NR), and beyond networks. The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN / LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network. As such, the Radio Access Network (RAN) of an EPS has an architecture comprising radio network nodes connected directly to one or more core networks.
[0008] With the 5G technologies such as NR, focus is on a set of features such as the use of very many transmit- and receive-antenna elements that make it possible to utilize beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions.
[0009] Wireless internet of things (loT) devices are often battery powered and both the need to change battery, and the battery lifetime may be concerns for many potential applications such as asset tracking or environmental and / or industrial sensors. For this reason, the wireless communications industry has been interested in so-called zeroenergy (ZE) devices. ZE devices refer to wireless loT devices that do not require battery replacement, and which can harvest energy from the environment. These ZE-loT devices can in addition be of very small form factor and could even be printable and they target ultra-low power consumption to enable operation based on either energy-harvesting from ambient sources or back-scattering communication, such as radio frequency identification (RFID). That is, instead of relying on active transmission and reception for communication being powered by a battery, energy is instead harvested from an ambient source, such as vibrations, solar power, radio frequencies (RF), or similar, and for back-scattering communication a charge carrier wave is provided to the device from the network which is modulated and reflected back to the network, such as back to the “reader”. This enables energy autonomous operation during the lifetime of the devices without a need for either manual replacement or charging of the batteries. Compared to existing radio access technologies this puts new requirements on the radio interface and the protocols.In 3GPP, ZE-loT started to be studied in Release 18, there referred to as ‘Ambient loT’, see RP-222685. The resulting study item technical report is found in 3GPP TR 38.848 v.18.0.0. In Release 19 the work continued with a study in RAN working groups, see RP-240826, for which the outcome is found in technical report 3GPP TR 38.769 v.19.0.0. It was agreed to continue in the last part of Release 19 with normative work, see RP-243326, to specify a limited solution:
[0010] • Indoor inventory, indoor command only
[0011] • Backscattering Device Type 1 only
[0012] • Deployment scenario 1 , Topology 1 (D1T1)-B (micro base station (BS) indoor; device indoor) only
[0013] • carrier wave (CW) outside topology
[0014] • Reader to device (R2D) in DL spectrum; device to reader (D2R) and CW in UL spectrum.
[0015] The only services supported in Release 19 are ‘inventory’, i.e., reporting of device identified to the reader, and ‘command’, i.e., transmitting a small payload to the device. Further the deployment scenario supported are indoor devices which receive CW transmissions for network nodes and the reflected signals are received by indoor micro base stations, e.g., in frequency division duplex (FDD) uplink spectrum. For downlink, direct transmission from the indoor micro base station to the device is supported, e.g., in FDD downlink spectrum, see Fig. 1A.
[0016] For Ambient loT (A-loT), 3GPP will target an loT segment well below the existing cellular loT technologies, e.g. narrowband (NB)-loT, with significantly lower energy consumption, device complexity, and / or cost. This requires simplifications in physical layer design, and higher layer design, such as layer 2 and / or layer 3 (L2 / L3) design, will also be much more lightweight with a minimal set of functionalities. For Random Access (RA) and multiple access devices, the Release 19 scope is limited to the following:
[0017] • A-loT Random access, including re-access for failure handling. Contentionbased and contention-free cases are supported. For the contention-based random access, only Solution 1 (3-step only) is included (unless RAN2 decides to use Solution 3 (unified solution) by RAN2#129).
[0018]
[0019] RA types and / or contention-based random access (CBRA) types may be one or more of the following:- 2-step CBRA comprises a 2 messages / steps sequence, wherein Message 2 may be optional, at least for study. The device transmits collision resolution (CR), such as CR ID, e.g., RN16, along with data in 1stmessage;
[0020] 3 / 4-Step CBRA comprises a 4 messages I steps sequence, wherein Message 4 may be optional, at least for study. The device transmits CR, such as CR ID, e.g., RN16, in 1stmessage and data in subsequent message only if the 1stmessage is acknowledged. In CBRA the device select a random preamble from a shared pool of preambles;
[0021] Contention free random access (CFRA), e.g., built similar and / or over CBRA, may comprise methods using 3-step CBRA for single device but without Msg 1 and / or Msg 2. The paging message triggering the CBRA, targets a single device. Other methods may be based on identity (ID) to address resource utilization locally, e.g., access stratum (AS) ID and / or other ID, for further study (FFS). The reader or radio network node allocates a dedicated preamble to accessing the network.
[0022] Fig. 1B shows a 2-step contention-based Random Access, and Fig. 1C shows a 3-step and 4-step contention-based Random Access.
[0023] Low-power wide area (LPWA) technologies including NB-loT, LTE- machine type communication (LTE-M), and future 6G LPWA enable massive loT deployment by offering a lower device cost, a wide range of device complexity and capability with a lower power consumption compared to Enhanced Mobile Broadband (eMBB) devices. LPWA devices are usually deployed in networks and / or environments with a large number of connected devices, and limited time-frequency resources. Different applications supported by LPWA devices have different periodicities for data transmission, different data sizes as well as different latency requirements. In order to address the requirements for the different applications efficiently, different types of random access mechanisms are supported to optimize performance.
[0024] 6G LPWA will likely include a lower complexity UE class that is energy constrained but is more capable than A-loT devices. Such devices may need efficient combinations of RA procedures and contention resolution mechanisms.
[0025] SUMMARYAs part of developing embodiments herein one or more issues were first identified. Regarding the areas A-loT and LPWA, the following are brought forward:
[0026] A-loT. In a given access or inventory round, some devices may fail and require re-access, e.g., in a subsequent round. These devices may have had previous successful contention resolutions. There can be other segments of devices which don’t have successful contention resolution or have missed paging or DL control signaling associated with previous paging and / or access round. For example, one possible reason is devices may have too low energy.
[0027] Hence in the next access round, gNB and / or reader should provide re-access for both device segments, which have had
[0028] (i) Contention-successful previously but had failed data transmission, and
[0029] (ii) Contention-failure previously
[0030] Embodiments herein may solve the issue how reader can schedule both device segments in the given round.
[0031] LPWA’. LPWA devices, e.g., LTE-M and NB-loT, use CBRA for initial access as well as sporadic and infrequent transmissions. In order to reduce power consumption and signaling overhead, early data transmission (EDT) was introduced in 3GPP Rel-15 for NB-loT and LTE-M. EDT aims at enabling small data transmission during the RA procedure without having to complete the full radio resource control (RRC) connection setup.
[0032] Since EDT can only be used during the random access channel (RACH) procedure, small data transmission (SDT) has been introduced in 3GPP Rel-17 to allow LPWA devices to transmit a small amount of data when coming from idle state without requiring a full RRC connection. In SDT, The LPWA device follows the RACH procedure, transmits its small data, and quickly returns to idle mode.
[0033] Problems with EDT and SDT are:
[0034] • Collisions may happen if many devices attempt EDT at the same time leading to collisions and energy consuming retransmissions.
[0035] • EDT allows for a limited uplink data size. Larger messages would require completing the full RRC setup.
[0036] • If the uplink SDT data is not received (transmission is not acknowledged), the device we will have to change from idle mode and complete RRC connection procedure for retransmission
[0037] • In both EDT and SDT, the RA preamble is usually allowed to be transmitted at a higher power, making it more detectable. However, data transmission in EDT orSDT may follow an adjusted transmit power based on the network feedback / requirements.
[0038] In order to reduce latency as well as energy consumption of the LPWA devices, e.g., the lowest complexity device class, the network may provide re-access resources for devices who failed EDT and / or SDT and / or devices that completed EDT but wants to continue critical uplink data transmission without the completion of the full RRC setup.
[0039] The object of embodiments herein is to provide a mechanism handling devices in an efficient manner. The embodiments herein may also be applied for LPWA to address the above-mentioned problems.
[0040] According to an aspect of embodiments herein the object is achieved by providing a method performed by a radio network node, or reader, for handling communication in a wireless communication network. The radio network node transmits an indication to a device, wherein the indication indicates both CFRA and CBRA resources for re-accessing a cell of the radio network node for one or more first devices. The indication may also comprise information regarding one or more CBRA resources for re-accessing the cell of the radio network node for one or more second devices.
[0041] According to another aspect of embodiments herein the object is achieved by providing a method performed by a device for handling communication in a wireless communication network. The device receives from a radio network node an indication, wherein the indication indicates both CFRA and CBRA resources for re-accessing a cell of the radio network node for one or more first devices. The indication may also comprise information regarding one or more CBRA resources for re-accessing the cell of the radio network node for one or more second devices.
[0042] According to another aspect of embodiments herein the object is achieved by providing a device and a radio network node / reader configured to perform the methods herein, respectively.
[0043] Thus, according to an aspect of embodiments herein the object is achieved by providing a radio network node for handling communication in a wireless communication network. The radio network node is configured to transmit an indication to a device, wherein the indication indicates both CFRA and CBRA resources for re-accessing a cell of the radio network node for one or more first devices. The indication may also comprise information regarding one or more CBRA resources for re-accessing a cell of the radio network node for one or more second devices.
[0044] According to another aspect of embodiments herein the object is achieved by providing a device for handling communication in a wireless communication network. Thedevice is configured to receive from a radio network node an indication, wherein the indication indicates both CFRA and CBRA resources for re-accessing a cell of the radio network node for one or more first devices. The indication may also comprise information regarding one or more CBRA resources for re-accessing a cell of the radio network node for one or more second devices.
[0045] It is furthermore provided herein a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the device and the radio network node, respectively. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the device and the radio network node, respectively.
[0046] The radio network node may provide re-access resources for devices who failed connection and / or devices that want to continue critical uplink data transmission without the completion of the full RRC setup. Embodiments herein propose an allocation mechanism where the radio network node such as a reader may allocate both CFRA and CBRA resources, also referred to as one or more contention-free resources and one or more contention-based resources, to a set of devices.
[0047] - CFRA resource may be utilized for scheduled access, e.g., for deterministic, known traffic, device triggered or application function (AF) triggered like in A-loT, i.e., the base station already knew buffer reporting of device in some scenarios. The CFRA resource may still be allocated to a device which has not indicated buffer status for probabilistic data arrival but that could risk a resource wastage if device has no actual data to transmit.
[0048] - CBRA resource may be used for RACH, initial access, autonomous access, or transmission of sporadic data if the scheduled resource is limited.
[0049] It is important to remark that both CFRA and CBRA resources can be used by a same device, especially if the device could fit not all data onto one or more CFRA resources, and thus remaining data may be pushed onto or using CBRA resources.
[0050] The transmission from the radio network node may be a DL scheduling message and / or control signaling, e.g., downlink control information (DCI), paging, and / or access trigger, providing both CFRA and CBRA resources for re-access for devices of a first group, also referred to as first devices. The first device may have had contention passed previously but failed data transmission. The DL scheduling message and / or controlsignaling may further indicate CBRA resources for devices of a second group that previously had failed contention. By allocating both CFRA and CBRA resources instead of doing it in an individual manner, i.e., per device basis, this reduces R2D signaling, DL signaling, and / or paging signaling. Hence, embodiments handling devices, such as loT, LPWA, ZE-loT, or A-loT devices, in an efficient manner.
[0051] BRIEF DESCRIPTION OF THE DRAWINGS
[0052] Embodiments will now be described in more detail in relation to the enclosed drawings, in which:
[0053] Fig. 1 Aillustrates A-loT scenario according to prior art;
[0054] Fig. 1B illustrates a CBRA procedure according to prior art;
[0055] Fig. 1 Cillustrates a CBRA procedure according to prior art;
[0056] Fig. 2 is a schematic overview depicting a wireless communication network according to embodiments herein;
[0057] Fig. 3 shows a combined flowchart and signaling scheme according to some embodiments herein;
[0058] Fig. 4 is a schematic flowchart depicting a method performed by a device according to embodiments herein;
[0059] Fig. 5 is a schematic flowchart depicting a method performed by a radio network node according to some embodiments herein;
[0060] Fig. 6 is a schematic overview depicting allocation according to some embodiments herein;
[0061] Fig. 7 is a schematic overview depicting a format used to indicate resources to be used for RA according to some embodiments herein;
[0062] Fig. 8 is a block diagram depicting a device according to embodiments herein;
[0063] Fig. 9 is a block diagram depicting a radio network node according to embodiments herein;
[0064] Fig. 10 shows an example of a communication system 15100 in accordance with some embodiments;
[0065] Fig. 11 shows a communication system 15200 in accordance with some embodiments; Fig. 12 shows a UE 15300 in accordance with some embodiments;
[0066] Fig. 13 is a block diagram of a network node 15400 in accordance with various aspects described herein; and
[0067] Fig. 14 is a block diagram illustrating a virtualization environment 15500 in which functions implemented by some embodiments may be virtualized.DETAILED DESCRIPTION
[0068] Embodiments herein relate to communication networks in general. Fig. 2 is a schematic overview depicting a wireless communications network 1. The wireless communications network 1 comprises one or more RANs and one or more CNs. The wireless communications network 1 may use a number of different technologies, such as Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, NR, 6G, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / Enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.
[0069] In the wireless communications network 1 , wireless devices e.g. a device 10 such as an loT device, an A-loT device, a LPWA device, a ZE device, a UE, a mobile station, a non-access point (non-AP) STA, a STA, a wireless device and / or a wireless terminal, communicate via one or more Access Networks (AN), e.g. a RAN, to one or more core networks (CN). It should be understood by those skilled in the art that “device” is a nonlimiting term which means any terminal, wireless communication terminal, internet of things (loT) capable device, a tag, a device, wearable device, a Machine Type Communication (MTC) device, a Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a base station communicating within a cell. The device 10 may also be referred to as device in a reader to device (R2D) communication. The device 10 may be a first device or a second device according to some embodiments herein.
[0070] The wireless communications network 1 comprises a radio network node 12 providing radio coverage over a geographical area, e.g. a service area, of a radio access technology (RAT), such as 6G, NR, LTE, UMTS, Wi-Fi or similar. The radio network node 12 may be a radio access network node such as radio network controller or an access point such as a wireless local area network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNodeB), a base transceiver station, Access Point Base Station, base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit capable of serving a UE such as the device 10 within the service area served by the radio network node 12 depending e.g. on the first radio access technology and terminology used. The radio network node 12 may also be referred to as reader in a R2D communication.According to embodiments herein the radio network node 12 transmits to the device 10 an indication indicating both CFRA and CBRA resources for re-accessing a cell of the radio network node 12 for one or more first devices. The indication may also comprise information regarding one or more CBRA resources for re-accessing a cell of the radio network node 12 for one or more second devices. This may be used for D2R or R2D communication. Some embodiments herein enable devices, such as the device 10, which may operate with limited energy storage and unpredictable energy sources, to initiate a re-access procedure. A CFRA resource may be utilized for scheduled access, e.g., for deterministic, known traffic, device triggered or AF triggered like in A-loT, and a CBRA resource may be used for RACH, initial access, autonomous access, or transmission of sporadic data if the scheduled resource is limited.
[0071] Embodiments herein may have one or more of the following advantages:
[0072] Reducing R2D signaling, DL signaling, and / or paging signaling by allocating both CFRA and CBRA resources instead of doing the allocation in an individual manner, i.e., CFRA or CBRA per device basis.
[0073] CFRA may be used when the network assigns specific time resources to devices, minimizing contention and ensuring a deterministic access scheme.
[0074] CBRA may be used when multiple devices attempt to access the network simultaneously, contending for the available resources, e.g., a pool of preambles and / or occasions.
[0075] In below embodiments, use cases are assumed with ultra-low power devices, LPWA devices, zero-energy or A-loT devices being examples of the device 10.
[0076] The term radio network node 12 or RAN node is used which may be a network node or a UE. Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, MeNB, SeNB, location measurement unit (LMU), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, IAB, repeater, donor node controlling relay, base transceiver station (BTS), Central Unit e.g. in a gNB, Distributed Unit e.g. in a gNB, Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, transmission reception point (TRP), remote radio unit (RRU), remote radio head (RRH), nodes in distributed antenna system (DAS), core network node, e.g. multicast coordination entities (MCE), mobility management entity (MME), or similar, Operation and Maintenance (O&M), Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes, e.g., Evolved Serving Mobile Location Centers (E-SMLC), and / or similar.In particular, in an A-loT scenario the radio network node 12 may comprise an intermediate node and / or UE, e.g., a relay UE, IAB, repeater or similar, master node, and assisting node and / or assisting UE, e.g., relay UE, IAB, repeater or similar.
[0077] In embodiments herein device, UE, A-loT device, LPWA device, slave node, are used interchangeably.
[0078] In embodiments herein ‘intermediate node’, and ‘intermediate UE’ are applied interchangeably.
[0079] Both a gNB or an intermediate UE may operate as the radio network node 12 being a reader, towards devices, such as UEs.
[0080] The transmission from the device 10, and / or slave node to gNB and / or base station may be termed as UL, D2R, and / or physical uplink shared channel (PUSCH) transmission.
[0081] The transmission from to the radio network node 12 such as gNB and / or base station to device 10, or slave node may be termed as DL, R2D, physical downlink shared channel (PDSCH), and / or physical downlink control channel (PDCCH) transmission.
[0082] CFRA and CBRA resources may comprise, e.g., time, time division multiple access (TDMA), slot, occasion, frequency, frequency division multiple access (FDMA), and / or frequency shift number, value, or counter.
[0083] It is herein proposed an allocation mechanism where the radio network node 12 may allocate both CFRA and CBRA resources, also referred to as contention-free and contention-based resources, to a set of devices, such as first devices, and to indicate the CFRA and CBRA resources to the set of devices.
[0084] CFRA resource may be utilized for scheduled access, e.g., for deterministic, known traffic, such as, device triggered or AF triggered like in A-loT, i.e., base station already know from buffer reporting of device in some scenarios. The CFRA resource may still be allocated to a device which has not indicated buffer status for probabilistic data arrival but.
[0085] CBRA resource usage may be considered for RACH, initial access, autonomous access, or transmission of sporadic data if scheduled resources are limited.
[0086] Both resource sets may be used by same device, especially if the device 10 could not fit all data onto one or more CFRA resources, and thus the remaining data may be pushed onto or by using CBRA resources.
[0087] Fig. 3 is a combined flowchart and signaling scheme according to some embodiments herein.Action 301. The radio network node 12 may allocate one or more resources for the device 10 to use when performing RA procedure. The radio network node 12 may allocate CFRA and CBRA resources for re-accessing a cell of the radio network node 12 for one or more first devices, and / or also one or more CBRA resources for re-accessing a cell of the radio network node for one or more second devices. The one or more first devices may comprise a device which has previously passed contention resolution but failed data transmission. The one or more second devices may comprise a device which has failed contention resolution.
[0088] Action 302. The radio network node 12 transmits to the device 10 the indication indicating CFRA and CBRA resources for re-accessing a cell of the radio network node 12 for one or more first devices. The indication, such as a message, some values, some index values or similar, may also indicate one or more CBRA resources for re-accessing a cell of the radio network node for one or more second devices. The first UEs may be indicated by UE identity, and / or second device may be indicated by other UE identities.
[0089] Action 303. The device 10 may initiate a RA procedure using the indicated one or more resources for initial access and / or data transmission. This may be based on whether the device is a first device or a second device. If the device 10 is a first device, the device 10 may use CFRA resource for data transmission and CBRA resource for spillover data transmissions. If the device 10 is a second device, the device 10 may use a CBRA resource.
[0090] Example embodiments of a method performed by the device 10, such as a tag or sensor, for handling communication in the wireless communication network 1 will now be described with reference to a flowchart depicted in Fig. 4. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Optional features are disclosed in dashed boxes. The device may an ultra-low power device, an LPWA device, zero-energy device, or A-loT device.
[0091] Action 401. The device 10 receives from the radio network node 12, the indication indicating the CFRA and CBRA resources for re-accessing the cell of the radio network node 12 for one or more first devices. The indication, such as a message, some values, some index values or similar, may also indicate the one or more CBRA resources for reaccessing the cell of the radio network node 12 for one or more second devices. The one or more first devices and the one or more second devices may be of different categories based on traffic types, priorities, and / or capabilities. The one or more first devices may comprise a device which has previously passed contention resolution but failed datatransmission. The one or more second devices may comprise a device which has failed contention resolution.
[0092] Action 402. The device 10 may initiate the RA procedure using the indicated one or more CBRA and / or CFRA resources for initial access and / or data transmission. This may be based on whether the device 10 is a first device or a second device.
[0093] Example embodiments of a method performed by the radio network node 12, such as a reader, for handling communication in the wireless communication network 1 will now be described with reference to a flowchart depicted in Fig.5. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Optional features are disclosed in dashed boxes.
[0094] Action 501. The radio network node 12 may determine or obtain one or more resources for the device 10 to perform RA procedure with. The radio network node 12 may allocate one or more resources for the device 10 to use when performing RA procedure. The radio network node 12 may allocate CFRA and CBRA resources for reaccessing the cell of the radio network node 12 for one or more first devices, and / or also one or more CBRA resources for re-accessing the cell of the radio network node 12 for one or more second devices. The one or more first devices may comprise a device which has previously passed contention resolution but failed data transmission. The one or more second devices may comprise a device which has failed contention resolution. The device may be an ultra-low power device, a LPWA device, zero-energy device, or A-loT device.
[0095] Action 502. The radio network node 12 transmits to the device 10 the indication indicating CFRA and CBRA resources for re-accessing a cell of the radio network node 12 for one or more first devices. The indication, such as a message, some values, some index values or similar, may also indicate one or more CBRA resources for re-accessing a cell of the radio network node 12 for one or more second devices. The one or more first devices and the one or more second devices may be of different categories based on traffic types, priorities, and / or capabilities.
[0096] Action 503. The radio network node 12 may receive the initial message such as response in the CFRA and may receive data using the CBRA resource.
[0097] In an embodiment, the radio network node 12 such as a RAN node allocates both CFRA and CBRA based resources to one or more devices, such as a group of known devices or UEs and unknown devices or UEs:
[0098] i. by the same signaling, e.g., paging, orii. as a part of same procedure, e.g., a paging procedure containing multiple signaling where in one signaling, information related to target population indicates plus higher layer information indicated, and in other signaling, resource allocation information is indicated.
[0099] A known device may use CFRA resource and / or optionally CBRA resource.
[0100] An unknown device may use CBRA resource.
[0101] A classification around known an unknown device is indicated below. For example, known device may be a first device that is a device which has previously passed contention resolution but failed data transmission, and unknown device may be a second device that is a device which has failed contention resolution.
[0102] A simple access mechanism allocating different access resource type may be useful for low power use cases such as for LPWA, or A-loT devices. The device 10 may utilize a CFRA resource if network a-priori knows, and the prospective retransmissions or spillover data transmissions can be carried over a CBRA resource. The device 10 may not need to monitor for an extensive DL signaling or may be defined with an allocation behavior like in legacy RRC connected mode devices. Thus, in legacy mechanism, specifically in existing A-loT, and radio frequency identity (RFID), the allocation is either CBRA or CFRA based which is indicated via paging, SELECT, or a query command. RFID has no CFRA allocation mechanism. With regards to LPWA and NR, CBRA and CFRA resources are defined, but there is no access mechanism which allocates both RA types in a cohesive manner.
[0103] Fig. 6 presents an example according to embodiments herein, where DL control signaling may allocate both CBRA and CFRA resources for group of devices, I D_1 , ID_2, ID_A, and ID_Z, for a finite time, a time window, or within an access round. Unlike in NR, where specifically RACH resources are pre-configured / repetitive. Thus, Fig. 6 shows where the ID_1 is allocated CFRA occasion at X1, ID_2 is allocated CFRA occasion at X2, and ID_A and ID_Z may use Y1-Y98 for random access for data transmissions. Fig. 6 shows an allocation method that provides both CFRA and CBRA resources. The CBRA resources may be targeted for spillover data that may happen over CFRA resources or unknown users or devices’ data transmissions which are not allocated CFRA resources.
[0104] The resources for CFRA and / or CBRA can be in the form of, e.g., PUSCH, or 6G data channels, D2R channels, like in A-loT, or similar.
[0105] If the device 10 is transmitting some data on a CFRA resource and still has remaining and / or spillover data, the device 10 may transmit the remaining and / or spilloverdata on a CBRA resource. The device 10 may then indicate following information, such as information related to transmission over CBRA, in the transmission over CFRA resource. An example is shown in Fig. 7 illustrating a case where an uplink control information (UCI) is scheduling PUSCH over CFRA resource and the UCI includes a resource pointer pointing, in an autonomous manner, to a PUSCH transmitted over a CBRA resource which is used for remaining data or spillover data. The remaining data or spillover data area data that cannot be accommodated in the scheduled CFRA PUSCH.
[0106] Information type Comment
[0107] The device includes the CBRA resource CBRA resource (e.g., information in UCI, or in UL medium access time / TDMA / slot / occasion control (MAC) control element (CE) in and / or UL / D2R / PUSCH transmission over CFRA f re q u e n cy / F D M A / f re q u e n cy
[0108] shift number / value / counter)
[0109] The device includes the CBRA transmission’s Data size data size or transport block size (TBS)
[0110] information in UCI, or in UL MAC CE in UL / D2R / PUSCH transmission over CFRA The device indicates, using some flags, if it Feedback requirement needs feedback for transmission in CBRA indication resource where the flag is included in UCI, or in UL MAC CE in UL / D2R / PUSCH transmission over CFRA
[0111]
[0112] The allocation may be done by DL signaling, such as a paging mechanism or signaling, e.g., in A-loT, or prospective group-common DCI, for low power or LPWA devices, where the indication indicating information related to CBRA and CFRA resources and an optional information related to target device IDs or group IDs can be indicated in the:
[0113] same DL control signaling, or
[0114] multiple DL signaling / messages but associated with allocation procedure. The one or more CFRA resources, such as a CFRA resource subset, allocated to known devices are to be used, or intend to utilize, by these devices for:
[0115] retransmissions, or / or
[0116] new transmissions.The radio network node 12 may map a device identity to the resources in the DL signaling.
[0117] Additionally, the resources for retransmission may be allocated via a CFRA manner to devices which have failed with a transmission in a previous inventory, access, and / or paging round. In a previous round, the device may have had a successful contention resolution, e.g., Msg1 success during a CBRA procedure, but had failed a data transmission, such as a Msg3 failure in A-loT like use cases. Hence, in a current round, the radio network node 12 may allocate retransmission resources intended for CFRA mechanism to those devices.
[0118] A known device and a unknown device may be classified as:
[0119] Unknown devices: Whose identity has not yet been established or defined on AS or network level
[0120] o AS ID has not yet been allocated by the radio network node 12 or another RAN node
[0121] o The device can be unregistered
[0122] ■ Authentication or mutual authentication has not been performed for such devices
[0123] ■ Session has not been established for devices
[0124] ■ Temporary device ID has not been allocated by CN o The device may be registered but AS ID is not yet allocated
[0125] o The device may be in RRC idle mode
[0126] Known devices: Whose identity has been established or defined on AS level, e.g.;
[0127] o AS ID is allocated for the device
[0128] o The device is in RRC inactive mode or RRC connected mode o The device may have a temporary CN ID allocated, e.g., Globally Unique Temporary Identifier (GUTI), or the like or some other form, e.g., some encrypted temporary ID allocated by CN
[0129] ■ This temporary CN ID can be made visible to the radio network node 12 such as gNB / reader.
[0130] An unknown device may be provided with CBRA resources if:
[0131] o The device has not been provided with CFRA or dedicated resources o The device has non-deterministic or sporadic traffic to transmit, o The device has completed EDT but has indicated longer UL messages. o The device may transmit BSR on CBRA resources■ If the device does not receive any grant after transmitting BSR on CBRA resources, the device may assume a BSR transmission failure, and may trigger a scheduling request (SR) afterwards o The device may use CBRA resource to transmit spillover data. For example, if the device is allocated CFRA resources but it could not include all data in the CFRA resource and the remaining data may be transmitted via a CBRA resource.
[0132] The CBRA resources allocated to a group of devices, which group can be indicated by a group ID or set of individual device IDs.
[0133] There may be two reasons to indicate device IDs for the set of resources to be allocated over CBRA:
[0134] o The device IDs are non-access stratum (NAS) encrypted, which means the radio network node 12 does not know or have understanding of device IDs o The radio network node 12 specifies device IDs which are possibly nonencrypted information, e.g., the radio network node 12 may understand this information, but the radio network node 12 is not sure if all these devices exist in the radio network node 12 coverage / cell or registered, or similar.
[0135] DL control signaling may provide a Q parameter, similar to an RFID, or N number of access occasions and / or resources, such as N = 2AQ or function(Q), which may be divided into two subsets of access occasions and / or resources, where one subset containing N_1 occasions may be utilized in CFRA manner for specific devices, and the other set containing N_2 occasions may be utilized in CBRA manner.
[0136] A DL signaling, or paging, message indicating both the CFRA and CBRA resources may be associated to a service or transaction ID that corresponds to a service or transaction ID associated with a previous access, such as a previous round or trigger. The devices, which are currently engaged in an CFRA manner, may have previously been engaged in a previous DL and / or paging trigger associated with a given service ID where devices were provided CBRA access, or resources. During the previous access, some of the devices have failed data transmissions, however the devices may have had a successful contention resolution. This means the radio network node 12 is able to know their IDs, device ID used in contention resolution, due to contention success previously in CBRA occasions. Hence in new access round, the paging and / or DL trigger associatedwith same service and / or transaction ID, associated with previous paging trigger, and provides CFRA resources for previously contention resolution passed devices and CBRA resources for previously contention resolution failed devices or devices which had missed previous paging trigger.
[0137] If the device may be scheduled with CFRA resources, but have had a transmission failure, the device may do a re-access attempt using CBRA resources where CBRA resources are provided later in time where both CFRA and CBRA resource sets are allocated by same DL control signaling. The radio network node 12 may define policies for re-access, e.g.,
[0138] o devices which are accessing CFRA resources may retransmit or re-access in CBRA resources, or not, which devices are allocated by a same DL signaling which also indicates allocated CFRA resources for these devices. o A minimum and / or a maximum timeline, which timeline, time window, or time interval the device may follow for a re-transmission on CBRA resources. For example, if a device has failed data transmission in a CFRA occasion X, then the device may retry accessing the network using CBRA occasions which may be allocated in a time window defined by X + T_min and X + T_max. During this time window, the device may not be allowed to re-access the network on those access occasions which are not CBRA based. For example, during this window, there are 10 RA occasions out of which 4 are CBRA based RA occasions and remaining allocated to other devices, such as devices to use CFRA procedure, and hence, the reaccess for the indicated failed device is only allowed on these 4 CBRA occasions.
[0139] o The device that has experienced a failed CFRA access can be allowed for a subsequent re-access on a CBRA occasion if the radio network node 12 explicitly or implicitly indicates. One example of implicit indication is if device does not receive any new resource for re-transmission, then device is implicitly triggered for re-access in subsequent CBRA occasions.
[0140] For a device in sleep state or RRC idle mode, the device 10 may be instructed to wake up either explicitly by a network trigger, e.g., wakeup signal (WUS), or implicitly, e.g., using a preconfigured discontinuous reception (DRX) cycle, after contention-free / CFRA resource window, e.g., a X_T1 + X_T2 window, has ended and the device 10 may attempt RACH / data transmission in contention / CBRA window, e.g., window Y.
[0141] Network triggering or pre-configuration may include policies on allowed datatransmissions without completing RRC connection setup such as buffer status report (BSR), EDT orSDT.
[0142] Devices may be grouped into categories based on traffic types, priority and / or capability. The radio network node 12 may allocate both CBRA and CFRA resources to the devices based on their category and may also with an indication for a preferred access method, e.g., CFRA for high priority, scheduled devices, or triggered critical devices, and CBRA for lower priority and / or unpredictable traffic, and another indication for the backup access method (CBRA + CFRA or one of them).
[0143] The IDs, especially AS IDs, may be used for addressing devices, e.g., for CFRA allocation, then the other device group which are engaging in CBRA, which include some random number for contention access, may preclude number matching AS IDs of devices for CFRA allocation. For example, a paging message indicating AS I D_1 and AS ID_2 for given devices for CFRA and targeting some unknown group of devices for CBRA, ID_A and ID_Z. During CBRA, if the device includes some random number or ID for contention resolution, then this device may select any number based random number pool except numbers 1 and 2 which corresponds to CFRA device I D_1 and ID_2. It may happen I D_1 , ID_2 and IDs from random pool are of same size. Also, these random IDs can be promoted to AS IDs for unknown devices once they are identified or successfully won their contentions.
[0144] The network can configure flexible feedback behavior for devices subject on which resources it transmits and the requirements of transmissions, such as quality of service (QoS), reliability, or similar. See below table with some examples where feedback may be configured or not subject to inputs on resource type and transmission key performance indicators (KPI).
[0145] No. Resource Transmission Feedback in Comment
[0146] type Type / content response to
[0147] device’s
[0148] UL / D2R
[0149] transmission
[0150] CFRA data Not
[0151] 1. needed
[0152]
[0153] CBRA Collision Not The device will receive 2. resolution needed grant or not
[0154] ID CBRA BSR Not The device will receive 3. needed grant or not CBRA Sporadic Not Feedback can be 4a or small needed disabled or are not data configured if transmissions are of low reliability or QoS CBRA Sporadic Needed Feedback can be 4a or small enabled or configured data if transmissions are of high reliability or QoS, e.g., sporadic URLLC *Note: CBRA may be only useful for sporadic URLLC transmission, for non-sporadic or deterministic use case with large data, it is recommended to utilize dedicated scheduled allocation
[0155]
[0156] Fig. 8 shows a block diagram depicting the device 10, such as a device or tag, for handling communication in the wireless communication network.
[0157] The device 10 may comprise processing circuitry 801, e.g. one or more processors, configured to perform the methods herein. The device may be an ultra-low power device, a LPWA device, zero-energy device, or A-loT device.
[0158] The device 10 and / or the processing circuitry 801 is configured to receive the indication indicating the CFRA and CBRA resources for re-accessing the cell of the radio network node 12 for the one or more first devices. The indication, such as a message, some values, some index values or similar, may also indicate the one or more CBRA resources for re-accessing the cell of the radio network node for one or more second devices. The device 10 may be a first device, for example, a device which has previously passed contention resolution but failed data transmission. The device 10 may be a second device, for example, a device which has failed contention resolution. The one or more first devices and the one or more second devices may be of different categories based on traffic types, priorities, and / or capabilities.The device 10 and / or the processing circuitry 801 may be configured to initiate the RA procedure using the indicated one or more CBRA and / or CFRA resources for initial access and / or data transmission. This may be based on whether the device 10 is a first device or a second device.
[0159] The device 10 further comprises a memory 805. The memory comprises one or more units to be used to store data on, such as indications, energy levels, information of resources, CFRA, CBRA, parameters, thresholds, time intervals, formats, RA resources, reconfiguration, applications to perform the methods disclosed herein when being executed, and similar. The device 10 comprises a communication interface 806 comprising transmitter, receiver, transceiver and / or one or more antennas. Thus, it is herein provided the device 10 for handling communication in a wireless communication network, wherein the device 10 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said device 10 is operative to perform any of the methods herein.
[0160] The methods according to the embodiments described herein for the device 10 are respectively implemented by means of e.g. a computer program product 807 or a computer program product, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the device 10. The computer program product 807 may be stored on a computer-readable storage medium 808, e.g. a universal serial bus (USB) stick, a disc or similar. The computer-readable storage medium 808, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the device 10. In some embodiments, the computer-readable storage medium may be a non-transitory or transitory computer-readable storage medium.
[0161] Fig. 9 shows a block diagram depicting the radio network node 12, such as a Reader, for handling communication in the wireless communication network.
[0162] The radio network node 12 may comprise processing circuitry 901, e.g. one or more processors, configured to perform the methods herein.
[0163] The radio network node 12 and / or the processing circuitry 901 may be configured to determine or obtain one or more resources for the device 10 to perform RA procedure with. The radio network node 12 and / or the processing circuitry 901 may be configured to allocate one or more resources for the device 10 to use when performing RA procedure.The radio network node 12 and / or the processing circuitry 901 may be configured to allocate CFRA and CBRA resources for re-accessing a cell of the radio network node 12 for one or more first devices, and / or also one or more CBRA resources for re-accessing a cell of the radio network node 12 for one or more second devices. The one or more first devices may comprise a device which have previously passed contention resolution but failed data transmission. The one or more second devices may comprise a device which have failed contention resolution. The one or more first devices and the one or more second devices may be of different categories based on traffic types, priorities, and / or capabilities.
[0164] The radio network node 12 and / or the processing circuitry 901 is configured to transmit the indication indicating CFRA and CBRA resources for re-accessing a cell of the radio network node for one or more first devices. The indication, such as a message, some values, some index values or similar, may also indicate one or more CBRA resources for re-accessing a cell of the radio network node for one or more second devices. The device 10 may be an ultra-low power device, a LPWA device, zero-energy device, or A-loT device.
[0165] The radio network node 12 and / or the processing circuitry 901 may be configured to receive the initial message such as response in the CFRA and / or may receive data using the CBRA resource.
[0166] The radio network node 12 further comprises a memory 905. The memory comprises one or more units to be used to store data on, such as indications, energy levels, resources information, CFRA, CBRA, parameters, thresholds, time intervals, formats, RA resources, reconfiguration, applications to perform the methods disclosed herein when being executed, and similar. The radio network node 12 comprises a communication interface 906 comprising transmitter, receiver, transceiver and / or one or more antennas. Thus, it is herein provided the radio network node 12 for handling communication in a wireless communication network, wherein the radio network node 12 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said radio network node 12 is operative to perform any of the methods herein.
[0167] The methods according to the embodiments described herein for the radio network node 12 are respectively implemented by means of e.g. a computer program product 907 or a computer program product, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the radio network node 12. Thecomputer program product 907 may be stored on a computer-readable storage medium 908, e.g. a universal serial bus (USB) stick, a disc or similar. The computer-readable storage medium 908, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the radio network node 12. In some embodiments, the computer-readable storage medium may be a non-transitory or transitory computer-readable storage medium.
[0168] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.
[0169] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.
[0170] Fig. 10 shows an example of a communication system 15100 in accordance with some embodiments.
[0171] In the example, the communication system 15100 includes a telecommunications network 15102 that includes an access network 15104, such as a radio access network (RAN), and a core network 15106, which includes one or more core network nodes 15108. The access network 15104 includes one or more access network nodes or base stations of various types, access network nodes 15110A and 15110B are depicted (which may be collectively referred to as network nodes 15110 or radio network node 12), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPPaccess points (APs). Some embodiments of the access network 15104 may include more than one access network technology. The network nodes 15110 of access network 15104 facilitate direct or indirect connection of wireless devices, also referred to as UEs, such as by connecting UEs 15112A, 15112B, 15112C, and 15112D (one or more of which may be generally referred to as UEs 15112 being examples of the device 10) to the core network 15106 over one or more wireless connections.
[0172] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 15102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 15102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 15102, including one or more access network nodes 15110 and / or core network nodes 15108 such as first / second network node.
[0173] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.
[0174] The network nodes 15110 facilitate direct or indirect connection of one or more UEs 15112 to the core network 15106 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receivingwireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 15100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 15100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0175] The UEs 15112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 15110 and other communication devices. Similarly, the network nodes 15108, 15110 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 15102) with the UEs 15112 and / or with other network nodes or equipment in the telecommunications network 15102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 15102. More specifically, UEs 15112 may send messages, data, and / or other signals to network nodes 15108, 15110 or other elements of the telecommunications network 15102 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 15108, 15110 may send messages, data, and other signals to UEs 151122, other network nodes 15108, 15110, and other devices in telecommunications network 15102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 15112 by transmitting the message to an access network node 15110 that will then transmit the message to the intended UE 15112. Similarly, a core network node 108 may receive a particular message from a UE 15112 by receiving the message from an access network node 15110 that itself received the message from the UE 15112.
[0176] In the depicted example, the core network 15106 connects elements of the access network 15104 (e.g., one or more of the network nodes 15110) to one or more host computing systems, such as host 15116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 15106 includes one or more core networknodes (e.g., core network node 15108) of various types, one or more of which may be generally referred to as network nodes 15108. Network nodes 15108 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 15108 being examples of the first network node 140. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).
[0177] The host 15116 may be under the ownership or control of a service provider other than an operator or provider of the access network 15104 and / or the telecommunications network 15102. The host 15116 may be operated by the service provider or on behalf of the service provider. The host 15116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
[0178] As a whole, the communication system 15100 of Figure 10 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 15100 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 15100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different componentsor sub-systems within the communication system 15100 supporting different standards, protocols, or rule sets.
[0179] As one example, in certain embodiments, access network 15104 may contain some access network nodes 15110 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 15110 support (or the same access network nodes 15110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 15102 may support multiple generations of related communication standards, e.g., 4G and 5G 3GPP communication standards, and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.
[0180] Telecommunications network 15102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 15102. For example, the telecommunications network 15102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.
[0181] In some examples, one or more of the UEs 15112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 15104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 15104. Additionally, a UE may be configured for operating in single-or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
[0182] In the example, the hub 15114 communicates with the access network 15104 to facilitate indirect communication between one or more UEs (e.g., UE 15112C and / or 15112D) and network nodes (e.g., network node 15110B). In some examples, the hub 15114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 15114 may be a broadband router enabling access to the core network 15106 for the UEs. As another example, the hub 15114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from theUEs, network nodes 15110, or by executable code, script, process, or other instructions in the hub 15114.
[0183] As another example, the hub 15114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 15114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 15114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 15114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 15114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0184] The hub 15114 may have a constant / persistent or intermittent connection to the network node 15110B. The hub 15114 may also allow for a different communication scheme and / or schedule between the hub 15114 and UEs (e.g., UE 15112C and / or 15112D), and between the hub 15114 and the core network 15106. In other examples, the hub 15114 is connected to the core network 15106 and / or one or more UEs via a wired connection. Moreover, the hub 15114 may be configured to connect to an M2M service provider over the access network 15104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 15110 while still connected via the hub 15114 via a wired or wireless connection. In some embodiments, the hub 15114 may be a dedicated hub -that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 15110B. In other embodiments, the hub 15114 may be a non-dedicated hub -that is, a device which is capable of operating to route communications between the UEs and network node 15110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0185] Figure 11 is another example of a communication system 15200 according to some embodiments. As used herein, the communication system 15200 includes multiple access points (APs) 15210 (with four exemplary APs 15210A, 15210B, 15210C, and 15210D being depicted) and multiple wireless devices, referred to in the context of communication system 15200 as stations (STAs) 15212 (referred to individually as STA 15212A, STA 15212B, STA 15212C, STA 15212D, and STA 15212E). STA 15212A is served by AP 15210A in a first basic service set (BSS) 15220A. STA 15210B and STA 15210C are served by AP 15210B in a second BSS, BSS 15220B. STA 15212D is servedby AP 15210C in a third BSS, BSS 15220C. STA 15212E is served by AP 15210D in a fourth BSS, BSS 15220D. Stations 15212 may be non-AP ST As and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 15212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.
[0186] Each of ST As 15212 may connect through a radio link to one of APs 15210. For example, depending on location or channel conditions experienced by a given STA 15212, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contentionbased mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.
[0187] Each AP 15210 may provide data connectivity to ST As 15212 connected to a particular AP 15210. As illustrated, APs 15210 may be connected to a data network 15230. In this way, APs 15210 may also provide data connectivity between STAs 15212 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 15212 and its serving AP 15210 may be used for providing various kinds of services to STA 15212, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 15212 and / or on a device linked to STA 15212. By way of example, Figure 11 illustrates an application service platform 15232 provided in data network 15230. The application(s) executed on STA 15212 and / or on one or more other devices linked to STA 15212 may use the radio link for data communication with one or more other STA 15212 and / or the application service platform 15232, thereby enabling utilization of the corresponding service(s) at STA 15212.
[0188] Figure 12 shows a wireless device 15300 being example of the device 10, which may be configured to operate in communication system 15100 of Figure 10 or in communication system 15200 of Figure 11. The wireless device 15300 may be alternatively referred to as a UE 15300, like a UE 15112 within the context of communication system 15100, or as a station (STA) 15300 or as a non-access-point station (non-AP STA) 15300, like a STA 15212 within the context of the communicationsystem 15200, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.
[0189] A wireless device 15300 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 15300 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 15300 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 15300 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0190] In particular embodiments, wireless device 15300 includes processing circuitry 15302 that is operatively coupled via a bus 15304 to an input / output interface 15306, a power source 15308, a memory 15310, a communication interface 15312, and / or any other component, or any combination thereof. Certain embodiments of wireless device 15300 may include all or a subset of the components shown in Figure 12. The level of integration between the components may vary from one embodiment of wireless device 15300 to another. In general, in a particular embodiment of wireless device 15300, processing circuitry 15302, input / output interface 15306, power source 15308, memory 15310, and communication interface 15312 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 15300. Further, certain embodiments of wireless devices 15300 maycontain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0191] The processing circuitry 15302 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 15310. The processing circuitry 15302 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 15302 may include multiple central processing units (CPUs).
[0192] In the example, the input / output interface 15306 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 15300. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
[0193] In some embodiments, the power source 15308 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 15308 may further include power circuitry for delivering power from the power source 15308 itself, and / or an external power source, to the various parts of wireless device 15300 via input circuitry or an interface such as an electrical power cable. Power source 15308 may perform anyformatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 15300 to which power is supplied.
[0194] The memory 15310 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 15310 includes one or more programs 15314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 15316. The memory 15310 may store, for use by wireless device 15300, any of a variety of various operating systems or combinations of operating systems.
[0195] The memory 15310 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 15310 may allow wireless device 15300 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 15310, which may be or comprise a device-readable storage medium.
[0196] The processing circuitry 15302 may be configured to communicate with an access network or other network via or using the communication interface 15312. The communication interface 15312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 15322. The communication interface 15312 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 15318 and / or a receiver 15320 appropriate to provide network communications (e.g., optical, electrical,frequency allocations, and so forth). Moreover, the transmitter 15318 and receiver 15320 may be coupled to one or more antennas (e.g., antenna 15322) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0197] In the illustrated embodiment, communication functions of the communication interface 15312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
[0198] Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0199] In particular embodiments, wireless device 15300 may provide an output of data captured via a sensor, through its communication interface 15312, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 15300 can be communicated through a wireless connection to a network node via another wireless device 15300. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0200] As another example, wireless device 15300 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 15300 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
[0201] Wireless device 15300, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 15300 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 15300 shown in Figure 12.
[0202] As yet another specific example, in an loT scenario, wireless device 15300 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 15300 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 15300 may implement the 3GPP NB-loT standard. In other scenarios, wireless device 15300 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.
[0203] In practice, any number of wireless devices 15300 may be used together with respect to a single use case. For example, a first wireless device 15300 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 15300 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 15300 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 15300 can also include more than one of the functionalities described above. For example, wireless device 15300 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.Figure 13 shows a network node 15400 being an example of the radio network node 12 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 15400 may be configured to operate in communication system 15100 of Figure 10, like network nodes 15108 or 15110, or in communication system 15200 of Figure 11 , like an AP 15210 or a station 15212. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).
[0204] Network nodes 15400 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 15400 may be a relay node or a relay donor node controlling a relay. Network nodes 15400 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRU), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0205] Other examples of network nodes 15400 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).
[0206] In particular embodiments, network node 15400 includes a processing circuitry 15402, a memory 15404, a communication interface 15406, and a power source 15408. In general, in a particular embodiment of network node 15400, processing circuitry 15402, memory 15404, communication interface 15406, and power source 15408 may, in wholeor in part, represent or include physical components common to or shared by one or more of the other elements of network node 15400.
[0207] The network node 15400 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 15400 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 15400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 15404 or portions of memory 15404 for different RATs) and some components may be reused (e.g., a same antenna 15410 may be shared by different RATs). The network node 15400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 15400, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 15400.
[0208] The processing circuitry 15402 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 15404, to provide network node 15400 functionality.
[0209] In some embodiments, the processing circuitry 15402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 15402 includes one or more of radio frequency (RF) transceiver circuitry 15412 and baseband processing circuitry 15414. In some embodiments, the RF transceiver circuitry 15412 and the baseband processing circuitry 15414 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 15412 and baseband processing circuitry 15414 may be on the same chip or set of chips, boards, or units.The memory 15404 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 15402. The memory 15404 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 15402 and utilized by the network node 15400. The memory 15404 may be used to store any calculations made by the processing circuitry 15402 and / or any data received via the communication interface 15406. In some embodiments, the processing circuitry 15402 and memory 15404 is integrated.
[0210] The communication interface 15406 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 15406 comprises port(s) / terminal(s) 15416 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 15300 may be capable of wireless communication and communication interface 15406 may also include radio front-end circuitry 15418 that may be coupled to, or in certain embodiments a part of, an antenna 15410. Particular embodiments of radio front-end circuitry 15418 include filter(s) 15420 and amplifier(s) 15422. The radio front-end circuitry 15418 may be connected to an antenna 15410 and processing circuitry 15402. The radio front-end circuitry may be configured to condition signals communicated between antenna 15410 and processing circuitry 15402. The radio front-end circuitry 15418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 15418 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 15420 and / or amplifiers 15422. The radio signal(s) may then be transmitted via the antenna 15410. Similarly, when receiving data, the antenna 15410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 15418. The digital data may be passed to the processing circuitry 15402. In other embodiments, the communicationinterface may comprise different components and / or different combinations of components.
[0211] In certain alternative embodiments, network node 15400 may be capable of wireless communication but does not include separate radio front-end circuitry 15418, instead, the processing circuitry 15402 includes radio front-end circuitry and is connected to the antenna 15410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 15412 is part of the communication interface 15406. In still other embodiments, the communication interface 15406 includes one or more ports or terminals 15416, the radio front-end circuitry 15418, and the RF transceiver circuitry 15412, as part of a radio unit (not shown), and the communication interface 15406 communicates with the baseband processing circuitry 15414, which is part of a digital unit (not shown).
[0212] The antenna 15410 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 15410 may be coupled to the radio front-end circuitry 15418 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 15410 is separate from the network node 15400 and connectable to the network node 15400 through one or more interfaces or ports.
[0213] The antenna 15410, communication interface 15406, and / or the processing circuitry 15402 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 15400. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 15410, the communication interface 15406, and / or the processing circuitry 15402 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 15400. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.
[0214] The power source 15408 provides power to the various components of network node 15400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 15408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 15400 with power for performing the functionality described herein. For example, the network node 15400 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 15408. As a further example, the power source 15408 may comprise asource of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
[0215] Embodiments of the network node 15400 may include additional components beyond those shown in Figure 13 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 15400 may include user interface equipment to allow input of information into the network node 15400 and to allow output of information from the network node 15400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 15400.
[0216] Figure 14 is a block diagram illustrating a virtualization environment 15500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 15500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 15500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.
[0217] Applications 15502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0218] Hardware 15504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or morevirtualization layers 15506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 15508A and VM 15508B (which may be collectively referred to as VMs 15508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 15506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 15508.
[0219] The VMs 15508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 15506. Different embodiments of the instance of a virtual appliance 15502 may be implemented on one or more of VMs 15508, and the implementations may be made in different ways.
[0220] Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
[0221] In the context of NFV, each of the VMs 15508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, nonvirtualized machine. Each of the VMs 15508, and that part of hardware 15504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 15508 on top of the hardware 15504 and corresponds to an application 15502.
[0222] Hardware 15504 may be implemented in a standalone network node with generic or specific components. Hardware 15504 may implement some functions via virtualization. Alternatively, hardware 15504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 15510, which, among others, oversees lifecycle management of applications 15502. In some embodiments, hardware 15504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 15512which may alternatively be used for communication between hardware nodes and radio units.
[0223] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
[0224] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.Modifications and other embodiments of the disclosed embodiments will come to mind to one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the embodiment(s) is / are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of this disclosure. Although specific terms may be employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
[0225] EMBODIMENTS
[0226] Embodiment A1.
[0227] A method performed by a UE (10) for handling communication in a wireless communication network, the method comprising
[0228] receiving (401) from a radio network node (12), an indication indicating CFRA and CBRA resources for re-accessing a cell of the radio network node for one or more first UEs.
[0229] Embodiment A2.
[0230] The method according to embodiment A1 , wherein the indication also indicates the one or more CBRA resources for re-accessing the cell of the radio network node for one or more second UEs.
[0231] Embodiment A3.
[0232] The method according to any of the embodiments A1-A2, wherein one or more first UEs comprises a device which has previously passed contention resolution but failed data transmission and / or the one or more second UEs comprises a device which have failed contention resolution.
[0233] Embodiment A4.
[0234] The method according to any of the embodiments A1-A3, further comprising initiating (402) a RA procedure using the indicated one or more CBRA / CFRA resources for initial access and / or data transmission.
[0235] Embodiment B1.
[0236] A method performed by a radio network node (12) for handling communication in a wireless communication network, the method comprising
[0237] - transmitting (502) an indication to a UE, wherein the indication indicates CFRA and CBRA resources for re-accessing a cell of the radio network node for one or more first UEs.
[0238] Embodiment B2.The method according to embodiment B1, wherein the indication also indicates the one or more CBRA resources for re-accessing the cell of the radio network node for one or more second UEs.
[0239] Embodiment B3.
[0240] The method according to any of the embodiments B1-B2, wherein one or more first UEs comprises a device which has previously passed contention resolution but failed data transmission and / or the one or more second UEs comprises a device which have failed contention resolution.
[0241] Embodiment B4.
[0242] The method according to any of the embodiments B1-B3, further comprising - allocating the one or more CFRA and CBRA resources for re-accessing the cell of the radio network node for the one or more first UEs, and / or also one or more CBRA resources for re-accessing the cell of the radio network node for the one or more second UEs.
[0243] Embodiment C1.
[0244] A UE (10) for handling communication in a wireless communication network, wherein the UE is configured to:
[0245] receive an indication, from a radio network node (12), indicating CFRA and CBRA resources for re-accessing a cell of the radio network node for one or more first UEs.
[0246] Embodiment C2.
[0247] The UE (10) according to embodiment C1, wherein the UE is configured to perform the method according to any of the embodiments A2-A4.
[0248] Embodiment D1.
[0249] A radio network node (12) for handling communication in a wireless communication network, wherein the radio network node is configured to
[0250] - transmit an indication to a UE, wherein the indication indicates CFRA and CBRA resources for re-accessing a cell of the radio network node for one or more first UEs.
[0251] Embodiment D2.
[0252] The radio network node according to embodiment D1, wherein the radio network node is configured to perform the method according to any of the embodiments B2-B4. Embodiment E1.
[0253] A computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the methodaccording to any of the embodiments A1-A4 or B1-B4, as performed by the UE and the radio network node, respectively.
[0254] Embodiment F1.
[0255] A computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the embodiments A1-A4 or B1-B4, as performed by the UE and the radio network node, respectively.
Claims
CLAIMS1. A method performed by a device (10) for handling communication in a wireless communication network, the method comprising- receiving (401) from a radio network node (12), an indication indicating contention free random access, CFRA, and contention-based random access, CBRA, resources for re-accessing a cell of the radio network node (12) for one or more first devices.
2. The method according to claim 1 , wherein the indication also indicates one or more CBRA resources for re-accessing the cell of the radio network node for one or more second devices.
3. The method according to claim 2, wherein the one or more first devices and the one or more second devices are of different categories based on traffic types, priorities, and / or capabilities.
4. The method according to any of the claims 1-3, wherein the one or more first devices comprise a device which has previously passed contention resolution but failed data transmission, and / or the one or more second devices comprise a device which has failed contention resolution.
5. The method according to any of the 1-4, further comprising- initiating (402) a random access procedure using the indicated one or more CBRA and / or CFRA resources for initial access and / or data transmission.
6. The method according to any of the claims 1-5, wherein the device is an ultralow power device, a Low-power wide area, LPWA, device, zero-energy device, or Ambient-Internet of things, A-loT, device.
7. A method performed by a radio network node (12) for handling communication in a wireless communication network, the method comprising- transmitting (502) an indication to a device (10), wherein the indication indicates contention free random access, CFRA, and contention-based random access, CBRA, resources for re-accessing a cell of the radio network node for one or more first devices.
8. The method according to claim 7, wherein the indication also indicates one or more CBRA resources for re-accessing the cell of the radio network node for one or more second devices.
9. The method according to claim 8, wherein the one or more first devices and the one or more second devices are of different categories based on traffic types, priorities, and / or capabilities.
10. The method according to any of the claims 7-9, wherein the one or more first devices comprise a device which has previously passed contention resolution but failed data transmission, and / or the one or more second devices comprise a device which has failed contention resolution.
11. The method according to any of the claims 7-10, further comprising- allocating one or more CFRA and CBRA resources for re-accessing the cell of the radio network node (12) for the one or more first devices, and / or one or more CBRA resources for re-accessing the cell of the radio network node for the one or more second devices.
12. The method according to any of the claims 7-11, wherein the device is an ultralow power device, a Low-power wide area, LPWA, device, zero-energy device, or Ambient-Internet of things, A-loT, device.
13. A device (10) for handling communication in a wireless communication network, wherein the device (10) is configured to:receive an indication, from a radio network node (12), indicating contention free random access, CFRA, and contention-based random access, CBRA, resources for re-accessing a cell of the radio network node (12) for one or more first devices.
14. The device (10) according to claim 13, wherein the indication also indicates one or more CBRA resources for re-accessing the cell of the radio network node for one or more second devices.
15. The device (10) according to claim 14, wherein the one or more first devices and the one or more second devices are of different categories based on traffic types, priorities, and / or capabilities.
16. .The device (10) according to any of the claims 13-15, wherein the one or more first devices comprise a device which has previously passed contention resolution but failed data transmission, and / or the one or more second devices comprise a device which has failed contention resolution.
17. The device (10) according to any of the claims 13-16, further comprising initiate a random access procedure using the indicated one or more CBRA and / or CFRA resources for initial access and / or data transmission.
18. The device (10) according to any of the claims 13-17, wherein the device is an ultra-low power device, a Low-power wide area, LPWA, device, zero-energy device, or Ambient-Internet of things, A-loT, device.
19. A radio network node (12) for handling communication in a wireless communication network, wherein the radio network node (12) is configured to transmit an indication to a device (10), wherein the indication indicates contention free random access, CFRA, and contention-based random access, CBRA, resources for re-accessing a cell of the radio network node for one or more first devices.
20. The radio network node (12) according to claim 19, wherein the indication also indicates one or more CBRA resources for re-accessing the cell of the radio network node (12) for one or more second devices.
21. The radio network node (12) according to claim 20, wherein the one or more first devices and the one or more second devices are of different categories based on traffic types, priorities, and / or capabilities.
22. The radio network node (12) according to any of the claims 19-21, wherein the one or more first devices comprise a device which has previously passed contention resolution but failed data transmission, and / or the one or more second devices comprise a device which has failed contention resolution.
23. The radio network node (12) according to any of the claims 19-22, wherein the radio network node is configured toallocate one or more CFRA and CBRA resources for re-accessing the cell of the radio network node (12) for the one or more first devices, and / or one or more CBRA resources for re-accessing the cell of the radio network node for the one or more second devices.
24. The radio network node (12) according to any of the claims 19-23, wherein the device is an ultra-low power device, a Low-power wide area, LPWA, device, zero-energy device, or Ambient-Internet of things, A-loT, device.
25. A computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-12, as performed by the device and the radio network node, respectively.
26. A computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-12, as performed by the device and the radio network node, respectively.
