Methods and nodes for improved ran awareness, to improve reader-based scheduling procedure for a-iot

Abstract

There is provided a method performed by a Radio Access Network (RAN) node. The method comprises: obtaining a configuration for scheduling resources to one or more devices for transmissions; receiving, from a core network node, a signal to trigger a scheduling round for the one or more devices; and initiating the scheduling round towards the one or more devices, according to the obtained configuration.

Description

METHODS AND NODES FOR IMPROVED RAN AWARENESS, TO IMPROVE READER-BASED SCHEDULING PROCEDURE FOR A-IOTRELATED APPLICATIONS

[0001] This application claims the benefits of priority of US 63 / 574,387, entitled “Improved RAN awareness, to improve reader-based scheduling procedure, for A-IoT” and filed at the USPTO on April 4, 2024, which is hereby incorporated by reference in its entirety. TECHNICAL FIELD

[0002] This application relates to communication networks and more particularly to methods and apparatuses / nodes for improved RAN awareness, to improve the reader-based scheduling procedure for A-IoTs.BACKGROUND

[0003] Zero-Energy Internet of Thing (loT) & Ambient-IoT

[0004] Wireless 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 / industrial sensors. For this reason, the wireless communications industry has been interested in so-called zero-energy (ZE) devices. ZE devices refer to wireless loT devices that do not require battery replacement, and often harvest energy from the environment. In some use cases, such as monitoring the temperature of foodstuffs, the ZE devices may have small batteries that are disposable (e.g., organic, compostable batteries), rechargeable or have very limited capacity.

[0005] These ZE-IoT 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 an ambient sources or back-scattering communication (e.g. Radio Frequency Identification (RFID)). That is, instead of relying on energy for communication being provided by a battery, it is instead harvested from an ambient source, such as vibrations, solar power, Radio frequency (RF), etc. (harvesting), or a charge carrier wave is provided to the device which is modulated and reflected back to a reader (in the back-scattering communication case). This enables energy autonomous operation during the lifetime of the devices without 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.

[0006] Recently, work on this has started in third Generation Partnership Project (3GPP), then referred to as ‘Ambient-IoT’ (A-IoT). Technical report (TR) 22.840 is being developedby SAI to capture potential use cases, traffic scenarios, device constraints of Ambient loT (A- loT) and identify new potential service requirements as well as new key performance indicators (KPIs). Meanwhile, a study item at Radio Access Network (RAN) plenary level 1^222685, ‘Study on Ambient loT’ is being carried out with a focus on the feasibility of meeting design targets for relevant use cases of Ambient loT. The outcome is reported in TR 38.848.

[0007] Based on the outcome of the RAN study item, and the discussion during Rel-19 workshop during RAN# 100 (RWS-230 88), a Work group (WG)-level study item is expected to continue in Release (Rel)-19. In addition, depending on the progress and outcome of the WG-level study, a work item may be started during Rel-19 as well.

[0008] Deployment scenarios, use cases, services for A-IoT are described in clause 4 of TR 38.848 V 1.0.0.

[0009] Use cases

[0010] Two sets or levels of grouping were defined. The first, Grouping A, is on the basis of the deployment environment s) described for a use case in TR 22.840 [2], and the second, Grouping B, is on the basis of fimctionality / application described in TR 22.840 [2],

[0011] Grouping A: Indoor, Outdoor, Indoor / outdoor;

[0012] Grouping B: Inventory, Sensors, Positioning, Command.

[0013] These two groupings are then used to form representative use cases (rUCs) as follows, which are used in Clause 4.2 - Deployment scenarios and connectivity topologies: rUCl: Indoor inventory; rUC2: Indoor sensors; rUC3: Indoor positioning; rUC4: Indoor command; rUC5: Outdoor inventory; rUC6: Outdoor sensors; rUC7: Outdoor positioning; rUC8: Outdoor command.

[0014] This resulted in the mapping from SA 1 use cases and traffic scenarios onto RAN rUCs, as illustrated in TR 38.848 V 1.0.0 Table 1 / 4.1.1-1: Mapping between RAN representative use cases and SAI use cases.

[0015] Connectivity topologies

[0016] The following connectivity topologies for Ambient loT networks and devices are defined for the purposes of the study. In all these topologies, the Ambient loT device may be provided with a carrier wave from other node(s) either inside or outside the topology. The links in each topology may be bidirectional or unidirectional.

[0017] Base Station (BS), User Equipment (UE), assisting node, or intermediate node could be multiple BSs or UEs, respectively. The mixture of indoor and outdoor placement of such nodes is regarded as a network implementation choice. Account would need to be taken of potential impact on device or node complexity. In the connectivity topologies, this does notimply the existence of multi-hop assisting or intermediate nodes. Different topologies are described below with reference to Figs. 1 to 5, respectively.

[0018] Topology 1 : BS A-IoT device (illustrated in Fig, 1)

[0019] In Topology 1, the A-IoT device directly and bidirectionally communicates with a base station. The communication between the base station and the A-IoT device includes A- loT data and / or signalling. This topology includes the possibility that the BS transmitting to the A-IoT device is a different from the BS receiving from the A-IoT device.

[0020] Topology 2: BS «-» intermediate node «-» A- loT device (as illustrated in Fig, 2)

[0021] In Topology 2, the A-IoT device communicates bidirectionally with an intermediate node between the device and base station. In this topology, the intermediate node can be a relay, Integrated Access and Backhaul (IAB) node, UE, repeater, etc., which is capable of A-IoT. The intermediate node transfers A-IoT data and / or signalling between the BS and the A-IoT device.

[0022] Topology 3: BS assisting node «-» A-IoT device «-» BS (as illustrated in Fig, 3 and Fig, 4)

[0023] In Topology 3, the A-IoT device transmits data / signalling to a base station, and receives data / signalling from the assisting node (as shown in Fig. 3, which illustrates a topology with downlink assistance); or the A-IoT device receives data / signalling from a base station and transmits data / signalling to the assisting node (as shown in Fig. 4, which illustrates a topology with uplink assistance). In this topology, the assisting node can be a relay, IAB, UE, repeater, etc., which is capable of A-IoT.

[0024] Topology 4: UE «-» A-IoT device (as illustrated in Fig, 5)

[0025] In Topology 4, the A-IoT device communicates bidirectionally with a UE. The communication between the UE and the A-IoT device includes A-IoT data and / or signalling.

[0026] Deployment scenarios can be as follows:

[0027] Deployment scenario 1: Device indoors, base station indoors;

[0028] Deployment scenario 2: Device indoors, base station outdoors;

[0029] Deployment scenario 3 : Device indoors, UE-based reader;

[0030] Deployment scenario 4: Device outdoors, base station outdoors;

[0031] Deployment scenario 5: Device outdoors, UE-based reader;

[0032] Device categories

[0033] A-IoT devices are characterized in the study according to their energy storage capacity, and capability of generating RF signals for their transmissions.

[0034] The study considers that a device has either: No energy storage at all or Limited energy storage.

[0035] Relying on these storage capacities, the study considers the following set of Ambient loT devices:

[0036] Device A: No energy storage, no independent signal generation / amplification, i.e. backscattering transmission.

[0037] Device B: Has energy storage, no independent signal generation, i.e. backscattering transmission. Use of stored energy can include amplification for reflected signals.

[0038] Device C: Has energy storage, has independent signal generation, i.e., activeRF components for transmission.

[0039] A limited energy storage can be different among implementations within Device B or implementations within Device C. Such storage is expected to be order(s) of magnitude smaller than an NarrowBand (NB)-IoT device would typically include.

[0040] Devices A, B, and C are able to demodulate control signals, data signals, etc. from the relevant entity in RAN according to connectivity topology.

[0041] Functional and protocol simplifications for A / ZE loT

[0042] For A-IoT, 3GPP will target an loT segment well below the existing Consumer loT(CIoT) technologies rather than replacing the existing 3GPP PLWA technologies. It is expected that together with simplifications in the physical layer design, the higher layer (L2 / L3) design will also be much more lightweighted than the existing higher layer design in 3GPP, i.e., a minimal set of functionalities (both at access stratum (AS) and non-access stratum (NAS) levels), which is even more simplified compared to the design adopted for the existing CIoT technologies, should be used to operate A-IoT devices. One way of such simplifications is to design a communication protocol shifted from fully connection oriented with both NAS and Radio Resource Control (RRC) connections between the device and network to connectionless type of communication without RRC connections or even without NAS connections between the device and network so that the protocol and signaling overhead associated with the handshaking between the device and network is minimized. This means A-IoT devices do not setup and maintain an RRC connection with the network, also A-IoT devices do not setup and maintain AS context including (dedicated) radio bearer, logical channel, etc.

[0043] One way to implement connectionless communication is to employ message-based or self-contained transmission where context / control information associated with the signaling / data traffic is transmitted together with or right after the signaling / data traffic wherein the latter case (i.e., the right after case) there is no other transmission between the context / control information and the associated signaling / data traffic carrying the information that is needed for reception of the signaling / data traffic. One such example is that in downlink (DL), the signaling / data traffic is transmitted within or right after the paging message.SUMMARY

[0044] There currently exist certain challenge(s). A-IoT has been agreed to be a study and / or work item for 3GPP Rel-19. It is assumed that an inventory request / signaling is triggered by the core network (CN) or application function (AF) towards one or multiple devices. Such request / signaling message is transmitted to the devices via the RAN node. The RAN node will not be able to read the content of the signaling message. In this case, how the RAN node schedules resources to the devices would be unclear.

[0045] Therefore, it is necessary to study this issue and develop corresponding solutions.

[0046] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.

[0047] For example, there is provided a method at the RAN node / reader. The methods may comprise the following aspects:

[0048] - Detailed information content on the reader (RAN node) scheduling for the reader.

[0049] - In one option, such information can be signaled to the reader.

[0050] - In one option, such information can be a default / pre-configuration to the reader.

[0051] - In one option, a device sends an indicator to the reader indicating that the device is not able to be scheduled for uplink (UL) transmission / the device is experiencing high congestion / collision for UL transmission.

[0052] For example, there is provided a method performed by a RAN node (e.g UE or network node). The method comprises: obtaining a configuration for scheduling resources to one or more devices for transmissions; receiving, from a core network node, a signal to trigger a scheduling round for the one or more devices; and initiating the scheduling round towards the one or more devices, according to the obtained configuration.

[0053] Certain embodiments may provide one or more of the following technical advantage(s). RAN awareness on A-IoT services / data is improved so that the A-IoT performance can be improved. Resources to devices are better scheduled / allocated by the reader. Therefore, resource waste and potential interferences are avoided. Resource utilization efficiency is improved by the reader, i.e., assigning resources to devices by the reader depends on the actual needs of devices.

[0054] The teachings of certain embodiments may improve, e.g., the data rate, latency, power consumption.BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Exemplary embodiments will be described in more detail with reference to the following figures, in which:

[0056] Fig. 1 illustrates Topology 1 in TR 38.848 VI.0.0 for Ambient loT networks.

[0057] Fig. 2 illustrates Topology 2 in TR 38.848 VI.0.0 for Ambient loT networks.

[0058] Fig. 3 illustrates Topology 3 with DL assistance in TR 38.848 VI.0.0 for A-IoT networks.

[0059] Fig. 4 illustrates Topology 3 with UL assistance in TR 38.848 VI.0.0 for A- loT networks.

[0060] Fig. 5 illustrates Topology 4 in TR 38.848 VI.0.0 for Ambient loT networks.

[0061] Fig. 6 illustrates an example of a signaling diagram for scheduling in a network comprising ambient loT.

[0062] Fig. 7 illustrates an example of a flow chart of a method in a network node, according to an embodiment.

[0063] Fig. 8 shows an example of a communication system, according to an embodiment.

[0064] Fig. 9 shows a schematic diagram of a UE, according to an embodiment.

[0065] Fig. 10 shows a schematic diagram of a network node, according to an embodiment.

[0066] Fig. 11 illustrates a block diagram illustrating a virtualization environment.DETAILED DESCRIPTION

[0067] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0068] Terminology and disclaimer

[0069] In below embodiments, we have considered or assumed use cases with ultra-low power devices, zero-energy or A-IoT devices.

[0070] The term RAN node is used which can be a network node or a UE. Examples of network nodes are NodeB (NB), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNB, gNB, 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), RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. MCS, MME, etc.), O&M, OSS, SON, positioning node (e.g. E-SMEC), etc. In particular, in Ambient loT scenario, the RAN nodes comprise intermediate node / UE (e.g., relay UE, IAB, repeater, etc.) and assisting node / UE (e.g., relay UE, IAB, repeater, etc.).

[0071] In particular, in an A-IoT scenario, the RAN nodes comprise intermediate node / UE (e.g., relay UE, IAB, repeater, etc.) and assisting node / UE (e.g., relay UE, IAB, repeater, etc.).

[0072] In this disclosure, ‘polling’, ‘poll’ and ‘paging’, ‘page’, ‘inventory’, ‘query’, ‘interrogate’, is used to represent one or more than one signal transmitted by a network node broadcast wise or specially to a dedicated UE. The purpose of the signal is to facilitate / serve / manage / command one or more than one UE to synchronize to the network node (DL / UL synchronize to a reference time / frame / symbol, or synchronize to one or more than one signal which the UE receives from the network node, or synchronize based on a pre-defined rule), receive DL data, response and transmit UL data correctly in intended resources. The content of such signal may be a particular reference signal or a signal carrying control information and / or data. Such signal may be transmitted periodically or periodically configured by the network node.

[0073] In this disclosure, ‘A-IoT UE’, ‘A-IoT device’, ‘device’, or ‘UE’ are used interchangeably without losing the meaning.

[0074] In this disclosure, ‘intermediate node’, ‘intermediate UE’, ‘UE’ are used interchangeably without losing the meaning.

[0075] The following terminologies are used in the embodiments to represent different device types:

[0076] Device 1: ~1 pW peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to 10xppm, neither DL nor UL amplification in the device. The device’s UL transmission is backscattered on a carrier wave provided externally.

[0077] Device 2a:a few hundred pW peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to 10xppm, both DL and / or UL amplification in the device. The device’s UL transmission is backscattered on a carrier wave provided externally.

[0078] Device 2b: < a few hundred pW peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to 10xppm, both DL and / or UL amplification in the device. The device’s UL transmission is generated internally by the device.

[0079] Embodiments on the RAN node operating as a reader

[0080] In this clause, a RAN node (e.g., gNB, DU or CU) operates as a reader towards one or multiple devices. Devices (20) access the RAN node directly, e.g., see the connectivity in Topology 1 of Fig. 1.

[0081] Fig. 6 illustrates a signal diagram for this case. In step 102, the RAN node is the reader node (10) and is signaled of a configuration / information regarding RAN scheduling for one or multiple devices (20). The configuration can comprise at least one of the following information:

[0082] - Number of devices / occasions that can be scheduled (at maximum) during a scheduling round;

[0083] - Total (maximum) number of resources (in frequency and / or in time) that can be scheduled to devices for UL transmission during a scheduling round;

[0084] - A (maximum) number of resources (in frequency and / or in time) that can be scheduled per UL transmission / occasion during a scheduling round;

[0085] - The (longest) duration that a scheduling round span in time;

[0086] - Device type (e.g., type 1, type 2a, or type 2b) that allowed to be scheduled in a scheduling round;

[0087] - Transmission mode in UL that is allowed to be scheduled in a scheduling round;

[0088] - Backscatter based UL transmission and / or UL transmissions generated by device itself.

[0089] In step 104, upon triggering of a scheduling round (e.g., receiving a message from the CN (30) or AF, or triggered by the RAN node itself) the RAN node initiates a scheduling round according to the above configuration, in step 106. The message can be a request / command, for example.

[0090] For example, the RAN node can be a DU, and the configuration is received from a CU (step 102). In another example, the RAN node can be a gNB, a DU, or a CU, and the configuration is received from a CN node (e.g., AMF, SMF, UPF, or a CN node responsible for A-IoT service handling, e.g., AIOTF, or AIOTNF). The configuration can be also received from the 0AM or the AF. In another example, the configuration is preconfigured for the RAN node. In one example, the information regarding RAN scheduling can be the same for multiplescheduling rounds, since the configuration regarding RAN scheduling may be a semi-static setting / configuration. In one example, the information on RAN scheduling is carried in NGAP signaling or in Fl signaling.

[0091] In one embodiment, upon reception of a signaling from the CN node (e.g., AMF, SMF, UPF, or a CN node responsible for A-IoT service handling, e.g., AIOTF, or AIOTNF) indicating / carrying an inventory request / command for one or multiple intended devices (see step 104), the signaling also carries information regarding RAN scheduling, which can comprise the same information as described above (e.g. configuration). In addition, the signaling may also carry the following information:

[0092] - indicator indicating whether a response is needed for each occasion / device; if there are multiple intended devices in the scheduling round, there may be separate indicators for each device, carried in the signaling.

[0093] In this embodiment, the information regarding RAN scheduling can be different for different scheduling rounds (which is triggered by a CN signaling).

[0094] In one example, the inventory request / command is carried by NAS (like) signaling, however, the information on scheduling is carried in NGAP signaling.

[0095] In another example, both the inventory request / command and the information on scheduling are carried in NGAP signaling. Other signaling may be used as well to carry the request / command and the configuration / information on scheduling.

[0096] Embodiments on the intermediate UE operating as a reader

[0097] In this clause, an intermediate UE operates as a reader towards one or multiple devices. Devices access the network via the intermediate UE, e.g., see the connectivity Topology 2 of Fig. 2.

[0098] For example, with reference to Fig. 6, the intermediate UE acts as the reader node (10) and receives a configuration regarding scheduling towards devices (20). The configuration can be semi-static, i.e., the same configuration for multiple scheduling rounds, or fully dynamic, i.e., different configurations for different scheduling rounds, from a RAN node (i.e., gNB, DU, or CU), or a CN node (e.g., AMF, SMF, UPF, or a CN node responsible for A-IoT service handling, e.g., AIOTF, or AIOTNF) or an AF.

[0099] The configuration carries the same information described above, regarding the “embodiments on the RAN node operating as a reader”.

[0100] In one example, the configuration on scheduling towards devices can be a default configuration / pre-configuration, which is already stored at the intermediate UE (suchdefault / pre -configuration is only stored at the UE, which is capable of operating as an intermediate UE), prior to operating as an intermediate UE.

[0101] In one example, the configuration on scheduling towards devices can be delivered / signaled to the intermediate UE by 0AM.

[0102] Referring back to Fig. 6, an A-IoT device (20) may send a signaling to the reader (10), i.e., the gNB or the intermediate UE, in step 108. The signaling may carry at least one of the following information:

[0103] - an indicator indicating that the device is not able to be scheduled for UL transmission / the device is experiencing high congestion / collision for UL transmission;

[0104] - Number of scheduling rounds that the device has missed (i.e., the number of scheduling rounds during which the device has not been able to obtain any opportunity / occasion to perform UL transmission);

[0105] - Number of occasions that the device has missed (i.e., in this round or recent scheduling rounds). In this case, although the device has obtained at least one UL occasion, however, the device’s UL transmission on these occasions were not successful (i.e., not acknowledged (ACKed), or not received positive ACK);

[0106] - The time (until now) since the device has been triggered / indicated to perform UL transmissions but the device has not succeeded to perform these UL transmissions; in one example, the device is triggered to perform UL transmission to send a response after reception of a request message from the reader; in another example, the device is triggered to perform UL transmission autonomously (e.g., upon detection of a waming / urgent event);

[0107] - Other measurement results (e.g., DL radio channel quality measurements);

[0108] The signaling in step 108 may be carried via an upper layer signaling (e.g., RRC signaling), a MAC CE or a LI signaling.

[0109] Upon reception of the signaling, in step 110, the reader 10 may decide to adjust its scheduling towards the devices (may or may not include this reporting device) via at least one of the below options:

[0110] Option 1 : increase the number of devices (occasions) that are allowed to be scheduled in the current or next scheduling rounds;

[0111] Option 2 : increase the number of resources that are allowed to be used by devices in the current or next scheduling rounds;

[0112] Option 3 : terminate the current scheduling round and restart a new scheduling round (which allows more devices to be scheduled, or provides more resources for devices);

[0113] Option 4: don’t adjust the current scheduling round. When the current scheduling round finishes, scheduling one or multiple more scheduling rounds.

[0114] In step 112, the reader 10 may signal to the RAN node or the CN or other nodes informing them of the updated scheduling decision (made by the reader).

[0115] Optionally or alternatively, in step 114, the reader may send a signaling to the RAN node, CN, or AF indicating that the reader prefers to receive an updated configuration on its scheduling. The adjustment may be either to increase or decrease the number of allowed devices, or the number of resources to be used in a scheduling round.

[0116] Now turning to Fig. 7, an exemplary flow chart of a method 200 in a RAN node for communicating with other nodes, will be described. The RAN node can be a reader node and can be a gNB, such as 810 of Fig. 8 or 1000 of Fig. 10, etc., or it can be a UE, such as 812 of Fig. 8 or 900 of Fig. 9. Method 200 comprises:

[0117] Step 210: obtaining a configuration for scheduling resources to one or more devices for transmissions;

[0118] Step 220: receiving, for a core network node, a signal to trigger a scheduling round for the one or more devices; and

[0119] Step 230: initiating the scheduling round towards the one or more devices, according to the obtained configuration.

[0120] In some examples, the core network node is an Ambient Internet of Thing Function (AIOTF). In some examples the configuration comprises one or more of the following:

[0121] - a number of devices that can be scheduled during the scheduling round;

[0122] - a total number of resources that can be scheduled to the one or more devices for transmissions during the scheduling round;

[0123] - a number of resources that can be scheduled per transmission between a device and the RAN node during the scheduling round;

[0124] - a duration that the scheduling round spans in time;

[0125] - a device type that is allowed to be scheduled in the scheduling round; and

[0126] - a transmission mode that is allowed to be scheduled in the scheduling round.

[0127] In some examples, the RAN node obtains the configuration by receiving the configuration from a network node, if the RAN node is a UE. In some examples, the RAN node is one of a gNB, a DU, and a CU, and the RAN node obtains the configuration by receiving the configuration from one of the core network node, and 0AM. In some examples, the RAN node obtains a configuration by pre -configuring the configuration in the RAN node. In some examples, the RAN node obtains a configuration by receiving the configuration in a NGAPsignaling or Fl signaling. In some examples, the received signal to trigger the scheduling round comprises an indication of the configuration for scheduling the one or more devices. In some examples, the received signal is an inventory request or a command request. In some examples, the received signal is a NGAP signaling. In some examples, the RAN node is an intermediate UE. In some examples, the RAN node receives a message from one or more of the one or more devices. In some examples, the message comprises one or more of the following:

[0128] - an indicator indicating that the one or more devices are not able to be scheduled for transmissions or the one or more devices are experiencing high congestion / collision for transmissions;

[0129] - a number of scheduling rounds or occasions that the one or more devices have missed;

[0130] - a time since the one or more devices have been triggered / indicated to perform transmissions but the one or more devices have not succeeded to perform the transmissions; and

[0131] - measurement results.

[0132] In some examples, the message is received in a RRC signaling, a MAC CE or LI signaling. In some examples, the RAN node adjusts the configuration. In some examples, the RAN node adjusts the scheduling configuration by performing one or more of:

[0133] - increasing a number of devices that are allowed to be scheduled in a current or next scheduling round;

[0134] - increasing a number of resources that are allowed to be used by devices in the current or next scheduling rounds;

[0135] - terminating the current scheduling round and restart a new scheduling round; and

[0136] - not adjusting the current scheduling round.

[0137] In some examples, the RAN node sends an indication of the updated configuration to another network node.

[0138] Fig. 8 shows an example of a communication system 800 in accordance with some embodiments.

[0139] In the example, the communication system 800 includes a telecommunication network 802 that includes an access network 804, such as a RAN, and a core network 806, which includes one or more core network nodes 808. The access network 804 includes one or more access network nodes, such as network nodes 810a and 810b (one or more of which may be generally referred to as network nodes 810), or any other similar 3GPP access nodes or non- 3GPP access points. Moreover, as will be appreciated by those of skill in the art, a networknode 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 telecommunication network 802 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 802 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 nodes to implement one or more functionalities of any node in the telecommunication network 802, including one or more network nodes 810 and / or core network nodes 808.

[0140] 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). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access 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. The network nodes 810 facilitate direct or indirect connection of UE, such as by connecting UEs 812a, 812b, 812c, and 812d (one or more of which may be generally referred to as UEs 812) to the core network 806 over one or more wireless connections.

[0141] Example wireless communications over a wireless connection include transmitting and / or receiving wireless 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 800 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 800may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0142] The UEs 812 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 810 and other communication devices. Similarly, the network nodes 810 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 812 and / or with other network nodes or equipment in the telecommunication network 802 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 802.

[0143] In the depicted example, the core network 806 connects the network nodes 810 to one or more host computing systems, such as host 816. 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 806 includes one more core network nodes (e.g., core network node 808) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 808. Example core network nodes include 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).

[0144] The host 816 may be under the ownership or control of a service provider other than an operator or provider of the access network 804 and / or the telecommunication network 802. The host 816 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.

[0145] As a whole, the communication system 800 of Fig. 8 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 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); Uong Term Evolution (UTE), 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 (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0146] In some examples, the telecommunication network 802 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 802. For example, the telecommunications network 802 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.

[0147] In some examples, the UEs 812 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 804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 804. 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 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).

[0148] In the example, the hub 814 communicates with the access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812c and / or 812d) and network nodes (e.g., network node 810b). In some examples, the hub 814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 814 may be a broadband router enabling access to the core network 806 for the UEs. As another example, the hub 814 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 810, or by executable code, script, process, or other instructions in the hub 814. As another example, the hub 814 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 814 may be a content source. For example,for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 814 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 814 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0149] The hub 814 may have a constant / persistent or intermittent connection to the network node 810b. The hub 814 may also allow for a different communication scheme and / or schedule between the hub 814 and UEs (e.g., UE 812c and / or 812d), and between the hub 814 and the core network 806. In other examples, the hub 814 is connected to the core network 806 and / or one or more UEs via a wired connection. Moreover, the hub 814 may be configured to connect to an M2M service provider over the access network 804 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 810 while still connected via the hub 814 via a wired or wireless connection. In some embodiments, the hub 814 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 810b. In other embodiments, the hub 814 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 810b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0150] Fig. 9 shows a UE / wireless device 900 in accordance with some embodiments. The UE 900 presents additional details of some embodiments of the UE 812 of Fig. 8. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE 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 / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd 3GPP, including a (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0151] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-RangeCommunication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), orvehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE 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, a UE 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).

[0152] The UE 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input / output interface 906, a power source 908, a memory 910, a communication interface 912, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig. 9. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0153] The processing circuitry 902 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 910. The processing circuitry 902 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 902 may include multiple central processing units (CPUs). The processing circuitry 902 may be further configured to perform any of the steps of method 200 of Fig. 7, when the reader is a UE.

[0154] In the example, the input / output interface 906 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, or any combination thereof. An input device may allow a user to capture information into the UE 900. Examples of an input device include a touch-sensitive or presence-sensitive display, 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, atilt sensor, a force sensor, a magnetometer, an opticalsensor, 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.

[0155] In some embodiments, the power source 908 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. The power source 908 may further include power circuitry for delivering power from the power source 908 itself, and / or an external power source, to the various parts of the UE 900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 908. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 908 to make the power suitable for the respective components of the UE 900 to which power is supplied.

[0156] The memory 910 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 910 includes one or more application programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916. The memory 910 may store, for use by the UE 900, any of a variety of various operating systems or combinations of operating systems.

[0157] The memory 910 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 (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 910 may allow the UE 900 to access instructions, application 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 acommunication system may be tangibly embodied as or in the memory 910, which may be or comprise a device-readable storage medium.

[0158] The processing circuitry 902 may be configured to communicate with an access network or other network using the communication interface 912. The communication interface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 922. The communication interface 912 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 UE or a network node in an access network). Each transceiver may include a transmitter 918 and / or a receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., antenna 922) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0159] In the illustrated embodiment, communication functions of the communication interface 912 may include cellular communication, Wi-Fi communication, 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. Communications may be implemented in 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 / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0160] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 912, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.

[0161] A UE, when in the form of an loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city 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 controlledsmart speaker, a medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device 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 UE 900 shown in Fig. 9.

[0162] As yet another specific example, in an loT scenario, a UE 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 UE and / or a network node. The UE 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, the UE may implement the 3 GPP NB-IoT standard. In other scenarios, a UE 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.

[0163] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE 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 UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0164] Fig. 10 shows a network node 1000 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 telecommunication network. 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, NBs, evolved NBs (eNBs) and NRNBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0165] Base stations 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, pico, micro, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node 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 (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not beintegrated 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).

[0166] Other examples of network nodes include multiple transmission point (multi-TRP)5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, 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).

[0167] The network node 1000 includes a processing circuitry 1002, a memory 1004, a communication interface 1006, and a power source 1008. The network node 1000 may be composed of multiple physically separate components (e.g., a NB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1000 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NBs. In such a scenario, each unique NB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs). The network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, for example GSM, WCDMA, LTE, NR, WiFi, 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 1000.

[0168] The processing circuitry 1002 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 network node 1000 components, such as the memory 1004, to provide network node 1000 functionality.

[0169] In some embodiments, the processing circuitry 1002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1002 includes one or more of radio frequency RF transceiver circuitry 1012 and baseband processing circuitry 1014. In someembodiments, the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 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 1012 and baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units. The processing circuitry 1002 may be further configured to perform any steps of method 200 of Fig. 7, when the reader is a network node.

[0170] The memory 1004 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, RAM, 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 1002. The memory 1004 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 1002 and utilized by the network node 1000. The memory 1004 may be used to store any calculations made by the processing circuitry 1002 and / or any data received via the communication interface 1006. In some embodiments, the processing circuitry 1002 and memory 1004 is integrated.

[0171] The communication interface 1006 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 1006 comprises port(s) / terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection. The communication interface 1006 also includes radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, the antenna 1010. Radio front-end circuitry 1018 comprises filters 1020 and amplifiers 1022. The radio front-end circuitry 1018 may be connected to an antenna 1010 and processing circuitry 1002. The radio front-end circuitry may be configured to condition signals communicated between antenna 1010 and processing circuitry 1002. The radio front-end circuitry 1018 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 1018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1020 and / or amplifiers 1022. The radio signal may then be transmitted via the antenna 1010. Similarly, when receiving data, the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018. The digital data may bepassed to the processing circuitry 1002. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0172] In certain alternative embodiments, the network node 1000 does not include separate radio front-end circuitry 1018, instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communication interface 1006. In still other embodiments, the communication interface 1006 includes one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012, as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).

[0173] The antenna 1010 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1010 may be coupled to the radio frontend circuitry 1018 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1010 is separate from the network node 1000 and connectable to the network node 1000 through an interface or port.

[0174] The antenna 1010, communication interface 1006, and / or the processing circuitry 1002 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1010, the communication interface 1006, and / or the processing circuitry 1002 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0175] The power source 1008 provides power to the various components of network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1000 with power for performing the functionality described herein. For example, the network node 1000 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 1008. As a further example, the power source 1008 may comprise a source 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.

[0176] Embodiments of the network node 1000 may include additional components beyond those shown in Fig .10 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 1000 may include user interface equipment to allow input of information into the network node 1000 and to allow output of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000. In some embodiments providing a core network node, such as core network node 108 of FIG. 8, some components, such as the radio front-end circuitry 1018 and the RF transceiver circuitry 1012 may be omitted.

[0177] Fig. 11 is a block diagram illustrating a virtualization environment 1100 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 1100 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the 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 1100 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0178] Applications 1102 (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.

[0179] Hardware 1104 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 more virtualization layers1106 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1108a and 1108b (one or more of which may be generally referred to as VMs 1108), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1106 may present a virtual operating platform that appears like networking hardware to the VMs 1108.

[0180] The VMs 1108 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1106. Different embodiments of the instance of a virtual appliance 1102 may be implemented on one or more of VMs 1108, and the implementations may be made in different ways. 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.

[0181] In the context of NFV, a VM 1108 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non- virtualized machine. Each of the VMs 1108, and that part of hardware 1104 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 VMs 1108 on top of the hardware 1104 and corresponds to the application 1102.

[0182] Hardware 1104 may be implemented in a standalone network node with generic or specific components. Hardware 1104 may implement some functions via virtualization. Alternatively, hardware 1104 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 1110, which, among others, oversees lifecycle management of applications 1102. In some embodiments, hardware 1104 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 1112 which may alternatively be used for communication between hardware nodes and radio units.

[0183] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprisecomputing 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.

[0184] 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.

[0185] The above-described embodiments are intended to be examples only. Alterations, modifications and variations may be effected to the particular embodiments by those of skill in the art without departing from the scope of the description.

Claims

CLAIMS1. A method performed by a Radio Access Network (RAN) node, the method comprising:- obtaining a configuration for scheduling resources to one or more devices for transmissions;- receiving, from a core network node, a signal to trigger a scheduling round for the one or more devices; and- initiating the scheduling round towards the one or more devices, according to the obtained configuration.

2. The method of claim 1, wherein the core network node is an Ambient Internet of Thing Function (AIOTF).

3. The method of any one of claims 1 to 2, wherein the configuration comprises one or more of the following:- a number of devices that can be scheduled during the scheduling round;- a total number of resources that can be scheduled to the one or more devices for transmissions during the scheduling round;- a number of resources that can be scheduled per transmission between a device and the RAN node during the scheduling round;- a duration that the scheduling round spans in time;- a device type that is allowed to be scheduled in the scheduling round; and- a transmission mode that is allowed to be scheduled in the scheduling round.

4. The method of any one of claims 1 to 3, wherein obtaining the configuration comprises receiving the configuration from a network node, if the RAN node is a User Equipment (UE).

5. The method of any one of claims 1 to 3, wherein the RAN node is one of a gNB, a Distributed Unit (DU), and a Central Unit (CU), and wherein obtaining the configuration comprises receiving the configuration from one of the core network node, and Operations Administration and Maintenance (OAM).

6. The method of any one of claims 1 to 3, wherein obtaining a configuration comprises pre-configuring the configuration in the RAN node.

7. The method of any one of claims 1 to 5, wherein obtaining a configuration comprises receiving the configuration in a NGAP signaling or Fl signaling.

8. The method of any one of claims 1 to 3, wherein the received signal to trigger the scheduling round comprises an indication of the configuration for scheduling the one or more devices.

9. The method of any one of claims 1 to 8, wherein the received signal is an inventory request or a command request.

10. The method of any one of claims 1 to 9, wherein the received signal is a NGAP signaling.

11. The method of any one of claims 1 to 3, wherein the RAN node is an intermediate UE.

12. The method of any one of claims 1 to 11, further comprising receiving a message from one or more of the one or more devices.

13. The method of claim 12, wherein the message comprises one or more of the following:- an indicator indicating that the one or more devices are not able to be scheduled for transmissions or the one or more devices are experiencing high congestion / collision for transmissions;- a number of scheduling rounds or occasions that the one or more devices have missed;- a time since the one or more devices have been triggered / indicated to perform transmissions but the one or more devices have not succeeded to perform the transmissions; and- measurement results.

14. The method of claim 12 or 13, wherein the message is received in a Radio Resource Control (RRC) signaling, a Medium Access Control (MAC) Control Element (CE) or Layer 1 (LI) signaling.

15. The method of any one of claims 1 to 14, further comprising adjusting the configuration.

16. The method of claim 15, wherein adjusting the scheduling configuration comprises performing one or more of:- increasing a number of devices that are allowed to be scheduled in a current or next scheduling round;- increasing a number of resources that are allowed to be used by devices in the current or next scheduling rounds;- terminating the current scheduling round and restart a new scheduling round; and- not adjusting the current scheduling round.

17. The method of claim 15 or 16, further comprising sending an indication of the updated configuration to another network node.

18. The method of any one of claims 1 to 17, wherein the one or more devices are Ambient Internet of Things (A-IoT) devices.

19. A Radio Access Network (RAN) node for scheduling one or more devices, the RAN node comprising a network interface and processing circuitry connected thereto, the processing circuitry configured to perform the method of any one of claims 1 to 18.

20. A computer-readable medium comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claims 1 to 18.

Images