Handling transmission in a network

Abstract

There is provided a method for handling scheduling information in a network. The method is performed by a network node (10) of the network. The method comprises determining (602) a number of one or more occasions to be configured for one or more wireless devices (20) of the network in a random access (RA) scheduling interval. The method also comprises initiating (604) transmission of scheduling information towards a first wireless device (20) of the one or more wireless devices (20). The scheduling information is configured to be used by the first wireless device (20) to perform a RA procedure with the network node (10) in at least one occasion of the one or more occasions.

Description

[0001] HANDLING TRANSMISSION IN A NETWORK

[0002] Technical Field

[0003] The present disclosure relates to methods for handling transmission of a first message, methods for handling scheduling information, and entities configured to operate in accordance with those methods.

[0004] Background

[0005] Wireless Internet of Things (loT) devices are often battery powered and both the need to change the 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 and / or compostable batteries), rechargeable or have very limited capacity.

[0006] These ZE-IoT devices can in addition be of very small form factor and could even be printable. In addition, ZE-IoT devices target ultra-low power consumption to enable operation based on either energy-harvesting from an ambient source 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. (i.e. by harvesting), or a charged carrier wave is provided to the device which is modulated and reflected back to a reader (e.g. 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.

[0007] Recently work on this has started in the Third Generation Partnership Project (3GPP). The work, referred to as ‘Ambient-IoT’, and 3GPP technical report (TR) 22.840 V19.0.0 is being developed by System Aspects 1 (SAI) to capture potential use cases, traffic scenarios, device constraints of Ambient loT (A-IoT), 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 RP-222685, ‘Study on Ambient IoT’, is being carried out with a focus on the feasibility of meeting design targets for relevant use cases of Ambient IoT. The outcome is being reported in 3GPP TR 38.848 VI.0.0 This study targets at a new 3GPP IoT technology, suitable for deployment in a 3GPP system, which relies on ultra-low complexity devices with ultra-low power consumption for the very- low end IoT applications. The study shall provide clear differentiation, i.e. addressing use cases and scenarios that cannot otherwise be fulfilled based on existing 3GPP Low Power Wide Area (LPWA) IoT technology, e.g., Narrow-band (NB)-IoT including with reduced peak transmission (Tx) power.

[0008] There currently exist certain challenges with certain types of IoT devices. In particular, certain user equipments (UEs), such as A-IoT UEs or partial Ambient IoT UEs, are limited by extremely simple implementation and extremely low complexity. As a consequence, it is impossible for such a UE to always setup and / or keep synchronization with a network node that is serving, operating, and / or managing the UE. This is especially true as such a UE may have no clock and / or timing equipped. As a comparison, legacy UEs and network nodes in the legacy terrestrial system are able to exhibit tight synchronization (e.g. by using synchronization signal block (SSB) or other reference signals).

[0009] As mentioned above, there are certain challenges associated with existing techniques for handling certain types of devices in a network. In a particular example, in the current new radio (NR) release, a UE accesses a base station (e.g., a gNodeB (gNB)) via a random access channel (RACH) procedure, where the UE first obtains a RACH occasion (RO) among all ROs (e.g., in a random manner). After that, the UE randomly selects a physical random access channel (PRACH) preamble. The UE transmits the PRACH preamble on the selected RO towards the base station. The base station may detect the PRACH preamble and reply with grant(s) for the UE to further transmit its UE Identity (ID) (e.g. among other information) for collision resolution. If the UE wins the collision, the base station will successfully decode the UE ID and reply with further grant-based information on which the UE continues to establish the connection to the base station. Otherwise, if the base station cannot detect the preamble, or if the UE fails to resolve the collision, the UE may need to backoff and retransmit the preamble until its connection to the base station can be established. This procedure is also called 4-step RACH procedure. Such a procedure assumes that the UE has at least downlink (DL) synchronization with the base station. After completion of the 4-step RACH, the UE can also achieve uplink (UL) synchronization with the base station. However, such a RACH procedure cannot be directly applied for certain UEs, such as A-IoT UEs, since these UEs may have no timing capability (e.g. clock unit) and thus are not able to read / detect synchronization signals due to hardware limitations. As such, some UEs cannot achieve and / or maintain synchronization with the network.

[0010] Summary

[0011] It is an object of the present invention to improve the random access (RA) procedure for hardware limited UEs, such as A-IoT UEs. This object is achieved by the independent claims. Advantageous embodiments are described in the dependent claims.

[0012] According to an aspect of the disclosure, there is provided a first method for handling scheduling information in a network. The first method is performed by a network node of the network. The first method comprises determining a number of one or more occasions to be configured for one or more wireless devices of the network in a RA scheduling interval and initiating transmission of scheduling information towards a first wireless device of the one or more wireless devices. The scheduling information is configured to be used by the first wireless device to perform a RA procedure with the network node in at least one occasion of the one or more occasions.

[0013] According to another aspect of the disclosure, there is provided a second method for initiating transmission of a first message in a RA procedure in a network. The second method is performed by a first wireless device of the network. The second method comprises initiating a RA procedure for transmission, in a first occasion, of a first message towards the network node. The RA procedure is initiated if a counter associated with the first wireless device meets a triggering value.

[0014] According to another aspect of the disclosure, there is provided a third method for initiating transmission of a first message in a RA procedure in a network. The third method is performed by a first wireless device of the network. The third method comprises initiating transmission, in a first occasion, of a first message towards a network node of the network. The first occasion is associated with a first RA scheduling interval. The first message comprises a RA identifier for the first wireless device. The RA identifier is determined based on one or more of an identifier associated with a downlink message received from the network node, an identifier of a network channel associated with the first occasion, an identifier of the first occasion, and an identifier of the first RA scheduling interval.

[0015] According to another aspect of the disclosure, there is provided a fourth method for initiating transmission of a first message in a RA procedure in a network. The fourth method is performed by a first wireless device of a plurality of first wireless devices of the network. The fourth method comprises initiating transmission, in a first occasion, of a first message towards a network node of the network. The first occasion is one of a first plurality of occasions associated with a first RA scheduling interval, the fourth method comprises, in response to determining that no RA response message to the first message is received from the network node, selecting a second occasion for retransmission of the first message. The second occasion is one of the plurality of occasions associated with the first scheduling interval, or one of a plurality of occasions associated with a second RA scheduling interval.

[0016] According to another aspect of the disclosure, there is provided a system. The system comprises the network described earlier and the first wireless device described earlier.

[0017] According to another aspect of the disclosure, there is provided a computer program comprising instructions which, when executed by processing circuitry, cause the processing circuitry to perform the first method described earlier, the second method described earlier, the third method described earlier, and / or the fourth method described earlier.

[0018] According to another aspect of the disclosure, there is provided a computer program product, embodied on a non-transitory machine-readable medium, comprising instructions which are executable by processing circuitry to cause the processing circuitry to perform the first method described earlier, the second method described earlier, the third method described earlier, and / or the fourth method described earlier.

[0019] Certain embodiments may provide one or more of the following technical advantage(s). Advantageously, the network (e.g. the network node) is able to schedule a required amount of occasions (e.g. RACH resources) for a group of intended (e.g. A-IoT) wireless devices. Moreover, the network is able to schedule the occasions (e.g. RACH resources) to targeted (e.g. A-IoT) wireless devices. Moreover, some of the embodiments disclosed herein improve resource utilization of RA (e.g. RACH) resources for a large number of (e.g. A-IoT) wireless device. Furthermore, certain embodiments of the embodiments disclosed herein provide for a reduction in RACH collision (e.g. occurrence). In general, the embodiments disclosed herein provide for an improved framework for both active and passive A-IoT devices (especially for passive A-IoT devices). Brief Description of the Drawings

[0020] For a better understanding of the embodiments of the present disclosure, and to show how it may be put into effect, reference will now be made, by way of example only, to the accompanying drawings, in which:

[0021] Figs. 1-5 are schematic illustrations of example network architectures;

[0022] Fig. 6 is a block diagram illustrating a network node according to an embodiment;

[0023] Fig. 7 is a block diagram illustrating a method performed by a network node according to an embodiment;

[0024] Fig. 8 is a block diagram illustrating a first wireless device according to an embodiment;

[0025] Figs. 9-11 are block diagrams illustrating a method performed by a first wireless device according to some embodiments; and

[0026] Fig. 12 shows an example of a communication system in accordance with some embodiments;

[0027] Fig. 13 shows a UE in accordance with some embodiments;

[0028] Fig. 14 shows a network node in accordance with some embodiments;

[0029] Fig. 15 is a block diagram of a host;

[0030] Fig. 16 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; and

[0031] Fig. 17 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.

[0032] Detailed Description

[0033] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0034] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject-matter disclosed herein, the disclosed subject-matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject-matter to those skilled in the art.

[0035] In some instances, detailed descriptions of well-known methods, entities, interfaces, circuits, and devices are omitted so as not obscure the description with unnecessary detail. Those skilled in the art will appreciate that the functions described may be implemented in one or more entities using hardware circuitry (e.g., analogue and / or discrete logic gates interconnected to perform a specialized function, ASICs, PLAs, etc.) and / or using software programs and data in conjunction with one or more digital microprocessors or general purpose computers. Entities that communicate using the air interface also have suitable radio communications circuitry. Moreover, where appropriate the technology can additionally be considered to be embodied entirely within any form of computer-readable memory, such as solid-state memory, magnetic disk, or optical disk containing an appropriate set of computer instructions that would cause a processor to carry out the techniques described herein.

[0036] As mentioned earlier, there are described advantageous techniques for handling scheduling information and transmission in a network. The techniques described herein involve a first wireless device. The first wireless device, and / or any wireless device referred to herein, may be an ultra-low power device, a zero-energy device and / or an ambient loT (A-IoT) device. A UE, 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, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are devices which are or which are 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 head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), 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.

[0037] However, it will be understood that the embodiments described herein are not limited to such devices, and that the wireless devices referred to herein can comprise other service and / or device classes or categories. For example, any wireless device referred to herein may be related to enhanced mobile broadband (eMBB), massive machine type communication (MTC), ultrareliable low latency communications (URLLC), time sensitive networking (TSN), etc. The applicable services (e.g. associated with a wireless device) can be associated with a short data burst and a large interval. A wireless device (e.g. the first wireless device referred to herein) may be referred to as a user equipment (UE). 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 camera, 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, etc. Other examples include any UE identified by 3GPP, including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0038] 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 3GPP 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. 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.

[0039] A UE 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, 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).

[0040] The term RAN node can be used interchangeably with the terms network node and / or user equipment (UE) herein. A network node, as referred to herein, may be a NodeB, a base station (BS), a multi -standard radio (MSR) radio node (such as MSR BS, evolved NodeB (eNodeB), gNodeB, Master eNB (MeNB), Secondary eNB (SeNB), a location measurement unit (LMU), an integrated access backhaul (IAB) node, a network controller, a radio network controller (RNC), a base station controller (BCS), a relay, a repeater, a donor node controlling relay, a base transceiver station (BTS), a Central Unit (e.g. in a gNB), a Distributed Unit (e.g. in a gNB), a Baseband Unit, a Centralized Baseband, a centralized RAN (C-RAN), an access point (AP), a transmission point, a transmission node, a transmission reception point (TRP), a remote radio unit (RRU), a remote radio head (RRH), a node in a distributed antenna system (DAS), a core network node (e.g. MCS node, Mobility Management Entity (MME) node, etc.), an O&M node, an Operations Support Systems (OSS) node, a Self-Organizing Network (SON) node, and / or a positioning node (e.g. a Evolved Serving Mobile Location Center (E-SMLC) node), etc. In particular, in an A-IoT scenario RAN nodes may comprise an intermediate node / UE (e.g., a relay UE, an IAB, a repeater etc.) at least in connection topology 2 (as described below).

[0041] A carrier wave, as referred to herein, may occupy a full or a part of a carrier. For example, a carrier wave may occupy a certain number of physical resource blocks (PRBs) (e.g. N PRBs) and / or a certain frequency band (e.g. X Hz). The occupied carrier parts / segments may span in the frequency domain in a consecutive or non-consecutive manner. In case a carrier wave occupies part of a carrier / band, multiple carrier waves may occur at the same time and, for example, occupy the full carrier / band. A carrier wave may be emitted in a modulated or unmodulated manner.

[0042] Some of the embodiments refer to a network which may comprise two network nodes (e.g. one of them being a serving network node, and the other one being a network node providing a carrier wave). In some embodiments, the network may comprise a network node (e.g. a serving network node) and a UE (e.g. an IAB node, a repeater and / or a relay UE), which may provide a carrier wave. However, the embodiments described herein are not limited to such a network configuration. Indeed, the techniques described herein are applicable to a configuration comprising more than two network nodes (e.g. one of them may be a serving network node, and the other ones may be network nodes providing carrier wave(s)). In another example, the network may comprise a network node (e.g. a serving network node) and more than one of a UE, an IAB node, a repeater and a relay UE.

[0043] Herein, the terms “RACH procedure”, “random access procedure”, “uplink access” or “uplink channel access” may be used interchangeably.

[0044] Herein, the terms “Msgl”, “first transmission”, “first message” or “MsgA” may be used interchangeably. Herein, the terms “Msg2”, “second message”, “MsgB” may be used interchangeably.

[0045] Herein, the terms “channel” or “subband” may be define a carrier segment which may comprise a number of PRBs, or a number of Hz. Occupied carrier parts and / or segments may span in the frequency domain in a consecutive or non-consecutive manner.

[0046] The embodiments described herein are applicable to both a 4-Step RACH procedure and a 2- step RACH procedure. 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.

[0047] BS, 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 not imply the existence of multi-hop assisting or intermediate nodes. Different topologies are illustrated in Figures 1-5 below.

[0048] Figure 1 illustrates a first network topology as described in 3GPP TR 38.848 V 1.0.0 as “Topology 1”. The first network topology of Figure 1 comprises a base station (BS) 102 and an Ambient loT device 104. In Topology 1, the Ambient loT device 104 directly and bidirectionally communicates with the BS 102. The communication between the base station 102 and the ambient loT device 104 includes Ambient loT data and / or signaling (as illustrated by arrow 105 of Figure 1). This topology includes the possibility that the BS 102 transmitting to the Ambient loT device 104 is different from a BS receiving from the Ambient loT device 104.

[0049] Figure 2 illustrates a second network topology as described in 3GPP TR 38.848 V 1.0.0 as “Topology 2”. The second network topology of Figure 2 comprises a base station (BS) 102, an Ambient loT device 104, and an intermediate node 202. In Topology 2, the Ambient loT device 104 communicates bidirectionally with the intermediate node 202 between the device 104 and BS 102 (as illustrated by arrows 204 and 206 of Figure 2). In this topology, the intermediate node 202 can be a relay, an IAB node, a UE, a repeater, etc. which is capable of Ambient loT. The intermediate node 202 can transfer Ambient loT data and / or signaling between BS 102 and the Ambient loT device 104 (as illustrated by arrows 204 and 206 of Figure 2).

[0050] Figures 3 and 4 illustrate a third network topology as described in 3GPP TR 38.848 V 1.0.0 as “Topology 3”. The third network topology of Figure 3 comprises a base station (BS) 102, an Ambient loT device 104, and an assisting node 302. As described in 3GPP TR 38.848 V 1.0.0, Figure 3 illustrates Topology 3 with downlink assistance. As described in 3GPP TR 38.848 V 1.0.0, Figure 4 illustrates Topology 3 with uplink assistance. In Topology 3, the Ambient loT device 104 transmits data / signaling to the base station 102 and receives data / signaling from the assisting node 302 (as illustrated by arrows 304, 306 and 308 of Figure 3); or the Ambient loT device 104 receives data / signalling from the basestation 102 and transmits data / signalling to the assisting node 302 (as illustrated by arrows 402, 404 and 406 of Figure 4). In this topology, the assisting node 302 can be a relay, IAB, UE, repeater, etc. which is capable of ambient loT.

[0051] Figure 5 illustrates a fourth network topology as described in 3GPP TR 38.848 V 1.0.0 as “Topology 4”. The fourth network topology of Figure 5 comprises an Ambient loT device 104 and a UE 502. In Topology 4, the Ambient loT device 104 communicates bidirectionally with the UE 502 (as illustrated by arrow 504 of Figure 5). The communication between UE 502 and the ambient loT device 104 includes Ambient loT data and / or signaling.

[0052] Ambient loT devices are characterized in 3GPP TR 38.848 V 1.0.0 according to their energy storage capacity, and capability of generating RF signals for their transmissions.

[0053] The study considers that a device has either:

[0054] No energy storage at all; or

[0055] Limited energy storage

[0056] Relying on these storage capacities, 3GPP TR 38.848 V 1.0.0 considers the following set of Ambient loT devices:

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

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

[0059] - Device C: Has energy storage, has independent signal generation, i.e., active RF components for transmission.

[0060] A limited energy storage can be different among implementations within Device B or implementations within Device C, and different between Device B and Device C. Such storage is expected to be order(s) of magnitude smaller than an NB-IoT device would typically include. Device A, B, and C are able to demodulate control, data, etc. from the relevant entity in RAN according to connectivity topology. For Ambient loT (A-IoT), 3GPP will target an loT segment well below the existing cellular loT (CIoT) technologies rather than replacement of existing 3GPP LPWA technologies. It is expected that together with simplifications in physical layer design, the higher layer (L2 / L3) design will also be much more lightweight than the existing higher layer design in 3GPP, i.e., a minimal set of functionalities (both at access stratum and non-access stratum levels), which is even more simplified compared to that 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 non-access stratum (NAS) and radio resource configuration (RRC) connections between device and network, to a connectionless type of communication without RRC connections or even also without NAS connections between device and network so that the protocol and signaling overhead associated with the handshaking between device and network is minimized. This means A-IoT devices may not setup and maintain an RRC connection with the network. Also, A-IoT devices may not setup and maintain AS context including (dedicated) radio bearer, logical channel, etc.

[0061] 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. In the latter case (i.e., the right after case), there may be no other transmission between the context / control information and the associated signaling / data traffic carrying info that is needed for reception of the signaling / data traffic. One such example is that in DL the signaling / data traffic is transmitted within, or right after, a paging message.

[0062] The network referred to herein can be any type of network. For example, the network referred to herein may be a communications or telecommunications network. In some embodiments, the network referred to herein can be a mobile network, such as a fifth generation (5G) mobile network or any other generation mobile network (e.g. 6G). In some embodiments, the network referred to herein can be a core network (e.g. a 5G core (5GC) network) or a radio access network (RAN). In some embodiments, the network referred to herein can be a virtual network or an at least partially virtual network. Although some examples have been provided for the type of network referred to herein, it will be understood that the network referred to herein can be any other type of network.

[0063] Figure 6 illustrates a network node 10 of a network in accordance with an embodiment. The network node 10 is for handling scheduling information in a network. In some embodiments, the network node 10 referred to herein can refer to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with the first wireless device referred to herein, and / or with other nodes or equipment to enable and / or to perform the functionality described herein. In some embodiments, the network node 10 referred to herein can, for example, be a physical node (e.g. a physical machine or server) or a virtual node (e.g. a virtual machine, VM).

[0064] As illustrated in Figure 6, the network node 10 comprises processing circuitry (or logic) 12. The processing circuitry 12 controls the operation of the network node 10 and can implement the method described herein in respect of the network node 10. The processing circuitry 12 can be configured or programmed to control the network node 10 in the manner described herein. The processing circuitry 12 can comprise one or more hardware components, such as one or more processors, one or more processing units, one or more multi-core processors and / or one or more modules. In particular implementations, each of the one or more hardware components can be configured to perform, or is for performing, individual or multiple steps of the method described herein in respect of the network node 10. In some embodiments, the processing circuitry 12 can be configured to run software to perform the method described herein in respect of the network node 10. The software may be containerized according to some embodiments. Thus, in some embodiments, the processing circuitry 12 may be configured to run a container to perform the method described herein in respect of the network node 10.

[0065] Briefly, the processing circuitry 12 of the network node 10 is configured to determine a number of one or more occasions to be configured for one or more wireless devices of the network in a random access (RA) scheduling interval. The processing circuitry 12 of the network node 10 is also configured to initiate transmission of scheduling information towards a first wireless device of the one or more wireless devices. The scheduling information is configured to be used by the first wireless device to perform a RA procedure with the network node in at least one occasion of the one or more occasions.

[0066] As illustrated in Figure 6, in some embodiments, the network node 10 may optionally comprise a memory 14. The memory 14 of the network node 10 can comprise a volatile memory or a non-volatile memory. In some embodiments, the memory 14 of the network node 10 may comprise a non-transitory media. Examples of the memory 14 of the network node 10 include, but are not limited to, a random access memory (RAM), a read only memory (ROM), a mass storage media such as a hard disk, a removable storage media such as a compact disk (CD) or a digital versatile disk (DVD), and / or any other memory. The processing circuitry 12 of the network node 10 can be communicatively coupled (e.g. connected) to the memory 14 of the network node 10. In some embodiments, the memory 14 of the network node 10 may be for storing program code or instructions which, when executed by the processing circuitry 12 of the network node 10, cause the network node 10 to operate in the manner described herein in respect of the network node 10. For example, in some embodiments, the memory 14 of the network node 10 may be configured to store program code or instructions that can be executed by the processing circuitry 12 of the network node 10 to cause the network node 10 to operate in accordance with the method described herein in respect of the network node 10. Alternatively or in addition, the memory 14 of the network node 10 can be configured to store any information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein. The processing circuitry 12 of the network node 10 may be configured to control the memory 14 of the network node 10 to store any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.

[0067] In some embodiments, as illustrated in Figure 6, the network node 10 may optionally comprise a communications interface 16. The communications interface 16 of the network node 10 can be communicatively coupled (e.g. connected) to the processing circuitry 12 of the network node 10 and / or the memory 14 of the network node 10. The communications interface 16 of the network node 10 may be operable to allow the processing circuitry 12 of the network node 10 to communicate with the memory 14 of the network node 10 and / or vice versa. Similarly, the communications interface 16 of the network node 10 may be operable to allow the processing circuitry 12 of the network node 10 to communicate with any one or more nodes (e.g. the first wireless device) referred to herein and / or any other node. The communications interface 16 of the network node 10 can be configured to transmit and / or receive any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein. In some embodiments, the processing circuitry 12 of the network node 10 may be configured to control the communications interface 16 of the network node 10 to transmit and / or receive any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.

[0068] Although the network node 10 is illustrated in Figure 6 as comprising a single memory 14, it will be appreciated that the network node 10 may comprise at least one memory (i.e. a single memory or a plurality of memories) 14 that operate in the manner described herein. Similarly, although the network node 10 is illustrated in Figure 6 as comprising a single communications interface 16, it will be appreciated that the network node 10 may comprise at least one communications interface (i.e. a single communications interface or a plurality of communications interfaces) 16 that operate in the manner described herein. It will also be appreciated that Figure 6 only shows the components required to illustrate an embodiment of the network node 10 and, in practical implementations, the network node 10 may comprise additional or alternative components to those shown.

[0069] Figure 7 depicts a method in accordance with particular embodiments. The method may be performed by a network node. The method is for handling scheduling information in a network. The network node described earlier with reference to Figure 6 can be configured to operate in accordance with the method of Figure 7. The method can be performed by or under the control of processing circuitry 12 of the network node 10 according to some embodiments.

[0070] As illustrated by block 602 of Figure 7, the method comprises determining a number of one or more occasions to be configured for one or more wireless devices of the network in a RA scheduling interval. More specifically, the network node 10 (e.g. the processing circuitry 12 of the network node 10) determines the number of the one or more occasions. The number of the one or more occasions can be determined based on an amount of the one or more wireless devices, and / or a predefined number of occasions. The one or more occasion may only be valid (e.g. usable by a wireless device) within the RA scheduling interval. The scheduling interval can be associated with occasions (e.g. RACH resources) for both initial transmission and retransmission of RA (e.g. RACH) messages. Therefore, the network node can schedule an amount (e.g. number) of occasions (e.g. RA resources dynamically for a group of intended devices.

[0071] As illustrated by block 604 of Figure 7, the method also comprises initiating transmission of scheduling information towards a first wireless device of the one or more wireless devices. More specifically, the network node 10 (e.g. the processing circuitry 12 of the network node 10) initiates transmission of the scheduling information (e.g. via the communications interface 16 of the network node 10). The scheduling information is configured to be used by the first wireless device to perform a RA procedure with the network node in at least one occasion of the one or more occasions. Herein, the term “initiate” can mean, for example, cause or establish. Thus, the network node 10 (e.g. the processing circuitry 12 of the network node 10) can be configured to itself transmit the request (e.g. via a communications interface 16 of the network node 10) or can be configured to cause another entity to transmit the request. Therefore, the method described with reference to Figure 7 enables a network node 10 (e.g., a RAN node) to schedule occasions (e.g. RACH and / or uplink channel access resources) for an amount of intended (e.g. A-IoT) UEs in a RA (e.g. RACH) scheduling interval. The RA scheduling interval may be referred to herein as a RA scheduling cycle, and / or a RA scheduling round. Alternatively, or in addition, the RA scheduling interval may be referred to herein as a RACH scheduling interval.

[0072] Furthermore, different from the legacy RACH procedure (either UE initiated or Physical Downlink Control Channel (PDCCH) order triggered contention free RA), a (e.g. A-IoT) UE is able to grasp / obtain an occasion (e.g., RACH occasion and / or PUSCH occasion) among all occasions during a RACH scheduling round / cycle initiated by the network node 10 (e.g. gNB, CN node (e.g., AMF, SMF etc)). The network node 10 may initiate the RACH scheduling round / cycle by sending a downlink (DL) signaling towards one or more wireless devices (e.g. UEs). The DL signaling may comprise a signaling carried by an upper layer e.g., RRC, or a similar upper layer responsible for control signaling. The DL signaling may comprise signaling provided in system information, where the wireless device (e.g. UE) may obtain it when it e.g. camps on the cell and may possibly access the cell or cell carrier. The DL signaling may comprise a signaling carried by a lower layer, e.g., MAC. The signaling carried by a lower layer may be a Medium Access Control (MAC) control element (CE). The DL signaling may comprise a LI signaling, e.g., carried by a LI channel, e.g., PDCCH. For example, the LI signaling may be a new LI signaling carried on a physical channel, say AIoT Physical DL channel (APDC)

[0073] The scheduling information may comprise one or more of: first information configured to be used by the first wireless device to generate a first identifier; second information indicative of an initiation of the scheduling interval; third information indicative of the number of the one or more occasions determined by the network node 10; fourth information indicative of a network medium associated with the RA scheduling interval; fifth information indicative of a request for the first wireless device to configure a status of the first wireless device, wherein the status of the first wireless device is associated with a RA status of the first wireless device; sixth information indicative of a request for the first wireless device to generate a contention resolution identifier; and seventh information indicative of a request for the first wireless device to perform a computation required for communication with the network node 10.

[0074] The first identifier can be a radio network temporary identifier (RNTI) (e.g. a RA-RNTI). The first information may comprise a sequence number, and / or an index. For example, the first information may comprise a sequence number or index of the DL signaling (i.e., which may be used by the first wireless device (e.g. UE) to generate a RA-RNTI).

[0075] The second information may comprise information indicative that the scheduling interval has been initiated, or information indicative of a first point in time at which the scheduling interval is to be initiated. The information indicative of a first point in time at which the scheduling interval is to be initiated may comprise a first period of time to elapse after receipt of the scheduling information. For example, the second information can comprise an indicator(s) indicating that a RACH scheduling round / cycle is initiated immediate or to be initiated in a gap after this signaling (e.g. of the scheduling information).

[0076] The number of the one or more occasion can correspond to a number of dynamically allocated RACH occasions and / or PUSCH occasions. Herein, occasions may be (e.g. only) located / distributed in a time domain. Alternatively, or in addition, occasions may be located / distributed in a frequency domain (e.g. especially when a RACH cycle is scheduled among multiple channels / subbands). The time resource / length of each occasion (e.g. RACH occasion and / or PUSCH occasion) can be derived from the total resource / length and / or the total number of RA scheduling intervals.

[0077] With regards to the fourth information mentioned above, network medium may comprise one or more of: one or more channels of the network; one or more carriers of the network; and one or more sub bands of the network. For example, the fourth information may comprise indices of channel(s) / carrier(s) / subband(s) where the RA scheduling interval is concerned. A scheduling interval (cycle) may comprise / concem multiple channels, carries, or subbands. Meaning that a device may select / obtain an occasion in any channel / carrier / subband when performing access towards the network node 10 (e.g. RAN node). In a scenario in which multiple channels are signaled, multiple first wireless devices (e.g. UEs) can access channels at the same time, wherein each UE may access a different channel. In this way, FDM based channel accesses are supported.

[0078] Signaling may be provided per reference signal type i.e. there may be a RA configuration associated with each (or each subset) of a set of Carrier Waves and / or a reference associated with each (or each subset) of a set of network nodes (e.g. gNBs and / or intermediate nodes) reference signal or CW frequency.

[0079] Indication of scheduling or RA configuration(s) may be mapped to carrier resources directly or indirectly. For example, there may be a relation between a selected beam / Carrier Wave- (e.g. frequency) and a RA configuration and / or PUSCH resource, and / or a relation between RA preamble configuration and a RA UL PUSCH configuration.

[0080] The scheduling information referred to herein may comprise an indication of downlink power used for e.g. estimation of pathloss or other.

[0081] The scheduling information referred to herein may comprise an indication of a user group or user ID(s). If the DL signaling is combined with a DL inventory command, which is initiating random access triggered by the network, then this DL command can indicate users or devices it is targeting for random access (e.g. along with resources indication).

[0082] The scheduling information referred to herein may comprise an indication of random-access window in a resource grid (e.g., in time or frequency domain or both) and / or a resource pool (e.g., a group of resources in frequency and time) for random-access. For instance, if the DL signaling triggers random access of a group of users (e.g., as a part of an inventory command), and if it is desirable for all users to not initiate random-access at the same time in order not to have excessive collisions, then a resource pool may be indicated In this way, users can randomly pick resources and possibly distribute uniformly (e.g., random selection of resources), resulting in lower collision probability.

[0083] The fifth information referred to herein may comprise information, an indication, a parameter, and / or a value indicating (e.g. instructing) devices (e.g. the first wireless device) to (re)initialize a (e.g. relevant) local variable (e.g. for the device). The local variable can include one or more of a device state, a timer value, a flag, etc. In this way, the network is able to control / govem UL access / response (e.g. with a timer and / or a flag mechanism).

[0084] With regards to the sixth information referred to herein, the contention resolution identifier can be configured to be used by the first wireless device for contention-based RA. For example, the sixth information can comprise one or more indications triggering the first wireless device to generate / produce a contention resolution ID to be used in next steps during a contentionbased UL access.

[0085] The seventh information referred to herein may comprise information and / or an indication related to a security and / or a crypto mechanism indicating the first wireless device to (pre)process heavy computation that will be used during an UL access procedure and / or subsequent transmission, e.g., secure data transmission. This allows time for the first wireless device to prepare itself before starting / establishing dedicated communication with the network (e.g. network node 10). The scheduling information may be indicative of whether PRACH preamble can be skipped (e.g. for the first wireless device).

[0086] The one or more occasions referred to herein can be configured to be used by the one or more wireless devices to perform a RA procedure with the network node 10. The one or more occasions can comprise one or more random access channel, RACH, occasions, and / or one or more physical uplink shared channel, PUSCH, occasions.

[0087] Although not illustrated in Figure 7, in some embodiment, the method may comprise receiving a first message from the first wireless device in the at least one occasion. The first message may be a RACH message. The first network node 10 may perform one or more operations in response to receiving the first message. For example, although not illustrated in Figure 7, in some embodiments the network node 10 may, in response to receiving the first message: assign a carrier wave to the first wireless device, assign a transmit power configuration to the first wireless device, and / or assign a transmission duration to the first wireless device. The carrier wave can be configured to be used by the first wireless device to perform backscatter-based uplink transmission to the network node 10. For example, the carrier wave (e.g. and associated carrier regions / PRB regions) can be configured for the UE to perform backscatter-based UL transmission. The transmit power configuration is associated with one or more resources allocated to the first wireless device. For example, the transmit power configuration may comprise transmit power instructions associated with PUSCH resource allocations and / or associated preambles. The transmit power configuration may comprise CW and / or a part of a CW frequency range (e.g. in relation to a downlink pathloss). The transmission duration may be a duration in time (e.g. in units of ms, slot, and / or OFDM symbols).

[0088] Alternatively, or in addition, the network node (e.g. gNB) may assign any one or ore of the following resources to the first wireless device in response to receiving the first message:

[0089] One or more resources on the carrier wave

[0090] A modulation and / or a modulation and coding scheme

[0091] A transmit power instruction.

[0092] A redundancy version (e.g. in one alternative hard coded in a standard specification) An indication to receive higher layer signaling that provides a second PUSCH configuration that may identify at least one of a modulation and coding state, a number of FSK / OFDM symbols, and a number of physical resource blocks. One or more beams, directions, and / or spatial filters at which the carrier wave can be transmitted / emitted .

[0093] One or more beams, directions, and / or spatial filters at which the UE can perform UL transmissions / backscatter on the carrier wave.

[0094] In scenarios in which another node or UE (e.g. other than the network node referred to herein) is responsible for transmitting / emitting the carrier wave towards the UE, the above information / resources may be signaled to that node or UE. Alternatively, the above resources / information may be signaled to both the node which is responsible for transmitting / emitting the carrier wave and the first wireless device (e.g. the UE which may perform UL transmission).

[0095] Figure 8 illustrates a first wireless device 20 of a network in accordance with an embodiment. The first wireless device 20 is for initiating transmission of a first message in a RA procedure in a network. In some embodiments, the first wireless device 20 referred to herein can refer to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with the network node 10 referred to herein, and / or with other nodes or equipment to enable and / or to perform the functionality described herein. In some embodiments, the first wireless device 20 referred to herein can, for example, be a physical node (e.g. a physical machine or server) or a virtual node (e.g. a virtual machine, VM). The first wireless device 20 referred to herein, and / or any other wireless device referred to herein, may be a A-IoT wireless device and / or a zero-energy device (ZED).

[0096] As illustrated in Figure 8, the first wireless device 20 comprises processing circuitry (or logic) 22. The processing circuitry 22 controls the operation of the first wireless device 20 and can implement the method described herein in respect of the first wireless device 20. The processing circuitry 22 can be configured or programmed to control the first wireless device 20 in the manner described herein. The processing circuitry 22 can comprise one or more hardware components, such as one or more processors, one or more processing units, one or more multi-core processors and / or one or more modules. In particular implementations, each of the one or more hardware components can be configured to perform, or is for performing, individual or multiple steps of the method described herein in respect of the first wireless device 20. In some embodiments, the processing circuitry 22 can be configured to run software to perform the method described herein in respect of the first wireless device 20. The software may be containerised according to some embodiments. Thus, in some embodiments, the processing circuitry 22 may be configured to run a container to perform the method described herein in respect of the first wireless device 20.

[0097] Briefly, the processing circuitry 22 of the first wireless device 20 is configured to initiate a RA procedure for transmission, in a first occasion, of a first message towards a network node. The RA procedure is initiated if a counter associated with the first wireless device meets a triggering value.

[0098] As illustrated in Figure 8, in some embodiments, the first wireless device 20 may optionally comprise a memory 24. The memory 24 of the first wireless device 20 can comprise a volatile memory or a non-volatile memory. In some embodiments, the memory 24 of the first wireless device 20 may comprise a non-transitory media. Examples of the memory 24 of the first wireless device 20 include, but are not limited to, a random access memory (RAM), a read only memory (ROM), a mass storage media such as a hard disk, a removable storage media such as a compact disk (CD) or a digital versatile disk (DVD), and / or any other memory.

[0099] The processing circuitry 22 of the first wireless device 20 can be communicatively coupled (e.g. connected) to the memory 24 of the first wireless device 20. In some embodiments, the memory 24 of the first wireless device 20 may be for storing program code or instructions which, when executed by the processing circuitry 22 of the first wireless device 20, cause the first wireless device 20 to operate in the manner described herein in respect of the first wireless device 20. For example, in some embodiments, the memory 24 of the first wireless device 20 may be configured to store program code or instructions that can be executed by the processing circuitry 22 of the first wireless device 20 to cause the first wireless device 20 to operate in accordance with the method described herein in respect of the first wireless device 20. Alternatively or in addition, the memory 24 of the first wireless device 20 can be configured to store any information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein. The processing circuitry 22 of the first wireless device 20 may be configured to control the memory 24 of the first wireless device 20 to store any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.

[0100] In some embodiments, as illustrated in Figure 8, the first wireless device 20 may optionally comprise a communications interface 26. The communications interface 26 of the first wireless device 20 can be communicatively coupled (e.g. connected) to the processing circuitry 22 of the first wireless device 20 and / or the memory 24 of the first wireless device 20. The communications interface 26 of the first wireless device 20 may be operable to allow the processing circuitry 22 of the first wireless device 20 to communicate with the memory 24 of the first wireless device 20 and / or vice versa. Similarly, the communications interface 26 of the first wireless device 20 may be operable to allow the processing circuitry 22 of the first wireless device 20 to communicate with any one or more nodes (e.g. the network node 10) referred to herein and / or any other node. The communications interface 26 of the first wireless device 20 can be configured to transmit and / or receive any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein. In some embodiments, the processing circuitry 22 of the first wireless device 20 may be configured to control the communications interface 26 of the first wireless device 20 to transmit and / or receive any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.

[0101] Although the first wireless device 20 is illustrated in Figure 8 as comprising a single memory 24, it will be appreciated that the first wireless device 20 may comprise at least one memory (i.e. a single memory or a plurality of memories) 24 that operate in the manner described herein. Similarly, although the first wireless device 20 is illustrated in Figure 8 as comprising a single communications interface 26, it will be appreciated that the first wireless device 20 may comprise at least one communications interface (i.e. a single communications interface or a plurality of communications interfaces) 26 that operate in the manner described herein. It will also be appreciated that Figure 8 only shows the components required to illustrate an embodiment of the first wireless device 20 and, in practical implementations, the first wireless device 20 may comprise additional or alternative components to those shown.

[0102] Figure 9 depicts a method in accordance with particular embodiments. The method may be performed by a first wireless device. The method is for initiating transmission of a first message in a RA procedure in a network. The first wireless device described earlier with reference to Figure 8 can be configured to operate in accordance with the method of Figure 9. The method can be performed by or under the control of processing circuitry 22 of the first wireless device 20 according to some embodiments.

[0103] An (e.g. intended A-IoT) UE can initiate a RA (e.g. RACH) procedure on an occasion obtained by the UE within a RACH scheduling cycle / round. The UE can initiate a RA procedure (e.g. on a concerned channel) when one or multiple conditions are met / triggered. For example, a condition may comprise the UE having UL traffic / data available for transmission (e.g., the UE has triggered / detected a waring event, therefore the UE needs to send a report to the network). Alternatively or in addition, a condition may be that the UE has received a DL signaling (e.g., paging or query signaling), which may triggers the UE to provide a response / report message in UL. Alternatively or in addition, a condition may be that the UE has received CW (e.g., with a specific sequence) in UL / DL band which may act as a trigger. In such a case, the UE can include data in unmodulated CW (e.g. in UL band).

[0104] As illustrated by block 702 of Figure 9, the method comprises initiating a RA procedure for transmission, in a first occasion of a first message towards the network node 10. More specifically, the first wireless device 20 (e.g. the processing circuitry 22 of the first wireless device 20) may initiate the RA procedure. The RA procedure is initiated if a counter associated with the first wireless device meets a triggering value.

[0105] Although not illustrated in Figure 9, in some embodiments the method may comprise generating the counter. The step of generating the counter may comprise generating the counter in response to determining that the first message is to be transmitted to the network node, and / or receiving information indicative that the network node has initiated a RA scheduling interval. For example, the counter can be generated by the first wireless device 20 when the first wireless device 20 has a UL transmission newly triggered. In some examples, the counter can be generated by the first wireless device 20 when the first wireless device 20 receives a DL signaling indicating a RACH (scheduling) round / cycle is started.

[0106] In some embodiments, generating the counter may comprise generating an initial value for the counter. The initial value can be an integer value. Generating the initial value for the counter may comprise selecting the initial value from a range of values, wherein the range has a minimum value and a maximum value. For example, the initial value for the counter may be a random value chosen out of a congestion window [a, b] where a and b are two positive integer values.

[0107] In some embodiments, the maximum value can be configured based on one or more of: a configuration of the first wireless device, a type of network traffic associated with the first message, a type of network service associated with the first message, a priority associated with the first message, and a value configured by the network node.

[0108] In an example in which the maximum value and / or minimum value can be determined / set according to the first wireless device’s category, traffic / service type, and / or traffic / service priority associated with a data / transmission. In an example in which the range corresponds to the congestions window, [a, b], higher values may be set to a and b if the first wireless device is a lower priori ty / category first wireless device, and / or carrying lower priority traffic. Lower values may be set to a and b if the first wireless device is a higher priority / category first wireless device, and / or carrying higher priority traffic. The logic behind this being that, an A-IoT UE with higher priority / category, may need to access the channel first, while an A-IoT UE with lower priority / category, may need to access the channel with lower priority, i.e., the lower priority UE needs to wait until the higher priority UEs have fmished / completed data transmission, before initiating channel access.

[0109] In some embodiments, the minimum value (of the range) can zero. For example, in some embodiments, the (e.g. initial value of the) counter may be generated as a random value between 0 and an integer value Nmax, where Nmax is the higher of N1 and N2. N1 can be an integer value configured according to the first wireless device’s category, traffic / service type and / or traffic / service priority associated with the data / transmission. N2 can be an integer value signaled / indicated by the network node 10 (e.g. gNB). For example, N2 may be the total number of (e.g. RACH and / or PUSCH) occasions in a RA scheduling interval (cycle / round). In this example, the N2 can signaled by the network node 10 (e.g. gNB) in a DL signaling which may trigger the first wireless device to generate the counter. N2 may be set by the network node 10 (e.g. gNB) equal to the number of first wireless devices (e.g. UEs) which need to be polled in a RACH (scheduling) interval / round / cycle.

[0110] The step of generating the initial value for the counter may be based on an amount of data comprised in a buffer of the first wireless device. For example, for a RA scheduling interval, the first wireless device (e.g. UE) may consider queuing time of its data / event in a buffer of the first wireless device as an input to generate the counter. Higher queuing time may correspond to a lower value initial value for the counter being set. Lower queuing time may correspond to a higher initial value for the counter being set. In this way, the wireless devices (e.g. UEs) with longer / higher queuing time (e.g. for data / traffic) can first access the channel, while the wireless devices (e.g. UEs) with lower queuing time may access the channel with lower priority.

[0111] Although not illustrated in Figure 9, in some embodiments, the method may comprise decreasing the counter by an incremental value in response to a criterion being met. The criterion may comprise at least one of receiving, from the network node, information indicative that the network node is able to receive an uplink transmission; determining that an uplink transmission and / or a downlink transmission has occurred at the network node; receiving a timing signal; and a first period of time elapsing in which no downlink transmission is received from the network node.

[0112] For example, the first wireless device (referred to as UE below) may decrease the counter (e.g. by 1) each time one of the below conditions is met:

[0113] 1) The UE has received / detected a specific DL signaling, which indicates: a) an UL transmission occasion can be initiated (immediately or a gap) after the DL signaling. b) a transmission (i.e., DL transmission or UL transmission) has just completed, thus the concerned channel is idle (immediately or a gap) after the DL signaling.

[0114] 2) The UE has detected that a DL transmission or an UL transmission has just completed. a) In one option, the UE may detect if a transmission has just completed based on energy detection, e.g., the UE may detect energy levels which indicates that the recent on-going transmission has completed and there is no ongoing transmission on the concerned channel right now.

[0115] 3) The UE has received a timing signaling (e.g. from the network node (e.g. gNB) or another timing source, e.g., another gNB or UE). The signaling indicates that: a) The end of a previous / recent slot / occasion. b) A new occasion / slot can start after this timing signaling.

[0116] 4) The UE hasn’t received any DL transmission for a pre-defined time period.

[0117] In some embodiments, the first occasion is one of a plurality of occasions configured by the network node. Although not illustrated in Figure 9, the method may comprise selecting the first occasion from the plurality of occasions. The selection of the first occasion can be random. Each occasion of the plurality of occasions can be associated with a unique identifier (e.g. an index) of the occasion. The plurality of occasions can be associated with a RA scheduling interval configured by the network node.

[0118] The occasions (e.g RACH and / or PUSCH occasions on a channel, subband, and / or carrier) can be organized in one or more manners. For example, the occasions may be organized in order of frequency resource indexes for frequency multiplexed occasions. Alternatively, or in addition, the occasion may be organized in increasing order of time resource indexes for time multiplexed occasions. Each occasion (e.g. of the plurality of occasions) can be associated with a unique index within a RACH scheduling cycle. The first wireless device may be randomly selected an occasion out of all occasions. In some embodiments, the wireless device / UE may not initiate a RA (e.g. RACH) procedure if it has already replied / reacted to a DL message / command that triggers random access procedure within a configured time period indicated in the scheduling information, as referred to herein. This can be realized by e.g., maintaining a flag and a timer. This allows a network (e.g. the network node 10) to control / govern UL access / response. For example, the network can prevent a device that has already replied to a common DL message / command such as (group) paging / polling / inventory / query and / or established communication link with network to reply / react to the same DL message / command by the same network node or a new network node.

[0119] This also allows the wireless device / UE to unnecessarily reply / react commands of the same kind from network nodes / CWTs multiple times, e.g., during inventory / registration phase and thus mitigating interference.

[0120] In an example, a wireless device can maintain a flag for a registration state, e.g., ‘ 1’ = registered, ‘0’ = not registered, and / or a timer indicating how long it has been registered / inventoried to the network. If the timer expires, e.g., value reaching the configured period, a registered device may consider itself as non-registered and may react to the DL command signaling for new registration / inventory round. A registered device may not reply to a DL trigger command (paging / polling / inventory / registration) before the timer expires. Thereafter, the UE may initiate a RACH procedure on an occasion.

[0121] In some embodiments, upon initiating a RACH procedure, the first wireless device (e.g. A-IoT UE) may skip transmission of a PRACH preamble (e.g. subject to requirements and use case). In some use cases, where a user group is triggered for random-access during inventory command, lightweight preamble (e.g., sparse, near orthogonal sequences, etc.) may be included to resolute colliding users during intense random-access transmissions.

[0122] In some embodiments, upon initiating a RA procedure, the first wireless device (referred to as UE below) may transmit (e.g. indicate) at least one of the below information towards the network node (e.g. gNB) in a first transmission (e.g., also referred to Msgl) of the RA procedure: a UE ID o the UE ID may be a temporary ID determined by the UE itself, e.g., a random ID of fixed size (the size can be indicated in SI or previous DL command) which can help a RAN node to do confirmation for next signaling, e.g., in Msg 2. The RAN node can send responding DL informing along with this ID, so this user knows, that the DL command is directed to this, and this user is the rightful user, o the UE ID may be a formal UE ID (e.g., TMSI, IMSI etc.). o the UE ID may be an ID assigned by the gNB beforehand. o the UE ID may be an ID assigned by a CN entity (e.g., AMF, SMF, or a CN entity responsible for A-IoT traffic / service management), e.g., GUTI, or function or part of GUTI. o the UE ID may be an ID used for collision resolution purpose. o the UE ID may be a UE ID where the network / device identifiers merged with application identifiers (one ID for such UE), e.g., one ID acting as SUPI / SUCI / GUTI and some application ID, say EPC (application ID use to identify RFID tags). an indicator which may indicate a need of uplink resources (e.g. carrier wave, modulation scheme, and time duration) for one or multiple UL transmissions. o the indicator may indicate a data volume. o the indicator may indicate a priority of the associated data. o the indicator may indicate a UE category (e.g. A-IoT UE category / device type) data o In one use case, UE ID can be treated as data (e.g. payload) o In another use case, the UE may be required to report additional information, other than just UE ID control signaling (e.g., signaling (e.g., request) for establish a dedicated connection towards the gNB)

[0123] Control elements e.g., BSR, extremely light weight BSR, or other MAC CEs, e.g., PHR.

[0124] L identity of the network node (e.g. gNB) and / or cell to access if the information is available.

[0125] The channel where UL data (e.g. and control information) is transmitted can be PUSCH (e.g. multiplexed and / or included with control channels such as PUCCH), and / or a new physical channel can be defined for both data and control (e.g. AIoT Physical UL channel (APUC)).

[0126] In some examples, the first wireless device (e.g. UE) may skip PRACH preamble due to the first wireless device (e.g. and other neighbor A-IoT UEs) being close to the network node (e.g. gNB) so that all wireless devices (e.g. UEs) in the coverage of the network node (e.g. gNB) may have the same or similar uplink timing synchronization towards the network node (e.g. gNB). “Close to” may correspond to a range of 50-100 meters. Therefore, it is less necessary to apply PRACH preamble based on which the gNB can estimate uplink synchronization. However, a dedicated PRACH preamble may be still helpful for the gNB to identify the associated UE in a PRACH transmission without carrying UE ID. Applying PRACH can also be beneficial to a scenario in which more than one gNB covers / reaches the UE, such that the gNB(s) may determine the target gNB which the UE accesses.

[0127] In some embodiments, the first wireless device (e.g. UE) can be configured to apply or skip PRACH preamble when initiating a RACH procedure. In the event that the UE transmits a PRACH preamble in a first transmission, in the RACH procedure, the UE may also transmit the information and / or data as described herein in the first transmission.

[0128] In some embodiments, the first wireless device (e.g. UE) may estimate the downlink pathloss by comparing a received signal power with an available parameter and / or information for downlink transmit power (e.g. that may be part of a gNB or intermediate node system information and / or provided in control information / configuration). The UE may, based on these means, estimate the need for preamble and / or UL resources (e.g. PUSCH resources).

[0129] As an additional embodiment, the network node (e.g. gNB) may indicate in the DL signaling initiating the RA (e.g. RACH) scheduling interval (round / cycle) that the UE can / shall proactively initiate a RACH procedure in the indicated resources for random access (e.g. in case such resource is indicated). For backscattered transmission, the network node (e.g. gNB) may instruct the relevant carrier wave transmitter(s) (e.g. CWT(s)) to transmit carrier wave so that the UE can perform proactive RACH procedure when needed. The DL signaling may include the UE group info for which proactive RACH procedure is allowed. The UE group may be represented by, for example, the UE’s category, traffic / service type or traffic / service priority associated with the data / transmission. A separate signaling / command may be used to set a flag in the UE on whether proactive RACH procedure is allowed. The signaling / command may include UE group info which indicates which UEs shall set the flag. The UE may only perform a proactive RACH procedure if the DL signaling initiating the RACH scheduling round / cycle indicates that a proactive RACH procedure can / shall be performed and / or the flag is set in the UE.

[0130] In some embodiments, the network node (e.g. gNB) may send the following one or more of the following signaling to operate proactive RACH procedure: A DL signaling to indicate that proactive RACH procedure shall be suspended. The DL signaling may further include the UE group info for which the proactive RACH procedure shall be suspended.

[0131] A DL signaling to indicate that proactive RACH procedure shall be resumed. The DL signaling may further include the UE group info for which the proactive RACH procedure shall be resumed.

[0132] A DL signaling to indicate that proactive RACH procedure shall be stopped. The DL signaling may further include the UE group info for which the proactive RACH procedure shall be stopped.

[0133] Figure 10 depicts a method in accordance with particular embodiments. The method may be performed by a first wireless device. The method is for initiating transmission of a first message in a RA procedure in a network. The first wireless device 20 described earlier with reference to Figure 8 can be configured to operate in accordance with the method of Figure 10. The method can be performed by or under the control of processing circuitry 22 of the first wireless device 20 according to some embodiments. As illustrated by block 802 of Figure 10, the method comprises initiating transmission, in a first occasion, of a first message towards a network node of the network. The first occasion is associated with a first RA scheduling interval, and the first message comprises a RA identifier for the first wireless device. The RA identifier is determined based on one or more of: an identifier associated with a downlink message received from the network node; an identifier of a network channel associated with the first occasion; an identifier of the first occasion; and an identifier of the first RA scheduling interval.

[0134] Therefore, the first wireless device can determine (e.g. calculate) an RA identifier (e.g. RA- RNTI) corresponding to the first occasion on which the RA procedure has been initiated, considering one or more types of information. For example, the identifier associated with the downlink message received from the network node may comprise an ID and / or sequence number associated with the DL message. The DL message may initiate the (e.g. current) first RA scheduling interval. The identifier of the network channel associated with the first occasion may comprise an index of the channel on which the first occasion is located. The identifier of the first occasion may be an index of the first occasion during the first RA scheduling interval. The identifier of the first RA scheduling interval may be an ID of the (e.g. current) first RA scheduling interval. In some embodiments, the determination of the RA identifier may be based on one or more of the following types of information: an index of a first OFDM symbol of a PRACH occasion (e.g. 0 < s_id < 14) an index of a first slot of a PRACH occasion in a system frame (e.g. 0 < t_id < 80), where the subcarrier spacing to determine t_id is based on the value of p for p = {0, 1, 2, 3}, and for p = {5, 6}, t_id is the index of the 120 kHz slot in a system frame that contains the PRACH occasion (e.g. 0 < t_id < 80), an index of a PRACH occasion in a frequency domain (e.g., 0 < f id < 8), a ul carrier id. The ul carrier id can be a UL carrier used for Random Access Preamble transmission (e.g. 0 for NUL carrier, and 1 for SUL carrier).

[0135] Although not illustrated in Figure 10, in some embodiments, the method may comprise receiving a second message from the network node. Although also not illustrated in Figure 10, in some embodiments, the method may comprise determining whether the RA identifier for the first wireless device can be derived from the second message. If the RA identifier is derivable from the second message, the method may comprise determining that the second message is a response to the first message.

[0136] Although not illustrated in Figure 10, in some embodiments, the method may comprise starting a timer in response to initiating transmission of the first message. In some of these embodiments, the second message may be determined to be a response to the first message only if the timer has not elapsed upon receipt of the second message.

[0137] Therefore, in some embodiments, a RA procedure can be initiated on an occasion obtained by the first wireless device during a RA scheduling interval. After transmission of the first message (e.g. Msgl), the first wireless device can start a timer (e.g., RAR timer in case of 4- step RA, or MsgB timer in case of 2-step RA). The value of the timer can correspond to a RAR window.

[0138] In some embodiments, if the first wireless device receives the second (e.g. response) message from the network node associated with the RA identifier (e.g. RA-RNTI) while the timer is running, the first wireless device may determine that the response message is for the current RA procedure. The RA identifier (e.g. RA-RNTI) may be carried by the second message as a field (e.g. since the PDCCH channel may be not needed for A-IoT). In some embodiments, the RA identifier (e.g. RA-RNTI) may be applied as a scrambling code for the response message (e.g. instead of being carried as a field in the response message). After the first wireless device has determined that the received response message is for the current RACH procedure, the first wireless device may stop the timer.

[0139] If the first wireless device has not received a response upon expiration, or after expiration, of the timer, another response may indicate that the channel is congested. As such, the first wireless device may determine that it needs to perform a back off procedure.

[0140] In some embodiments, the timer can be a RA response timer (RAR). In some embodiments, the RA identifier can be a radio network temporary identifier, RNTI. In some embodiments, the downlink message can be indicative that the first RA scheduling interval has been initiated by the network node. In some embodiments, the first RA scheduling interval can be configured by the network node.

[0141] As mentioned herein, in some scenarios, the first wireless device (e.g. UE) may need to perform retransmission of a message (e.g Msgl).

[0142] Figure 11 depicts a method in accordance with particular embodiments. As illustrated by block 902 of Figure 11, the method comprises initiating transmission, in a first occasion, of a first message towards a network node of the network. The first occasion is one of a first plurality of occasions associated with a first RA scheduling interval. As illustrated by block 904 of Figure 11, the method further comprises, in response to determining that no RA response message to the first message is received from the network node, selecting a second occasion for retransmission of the first message. The second occasion is one of the plurality of occasions associated with the first scheduling interval, or one of a plurality of occasions associated with a second RA scheduling interval.

[0143] In some embodiments, the first message may comprise a RNTI of the first wireless device. In some embodiments, determining that no RA response message to the first message is received from the network node may comprise: determining that a first period of time has elapsed without receiving the RA response message, and / or receiving a second message comprising information indicative that the network node is unable to provide the RA response message.

[0144] In some embodiments, the RA response message may comprise the RNTI of the first wireless device. In some embodiments, the second message may be received from the network node. In some embodiments, the second occasion can be one of the plurality of occasions associated with the first scheduling interval corresponding to the network node. The first occasion can be comprised in a first set of occasions of the first plurality of occasions. The second occasion can be comprised in a second set of occasions of the first plurality of occasions. The second set of occasions may be configured for retransmission of the first message. In some embodiments, the number of occasions comprised in the first set of occasions may be equal to the number of first wireless devices comprised in the plurality of first wireless devices.

[0145] Although not illustrated in Figure 11, in some embodiments the method may comprise selecting the second occasion from the second set of occasions if a counter associated with the first wireless device meets a triggering value. The second occasion may be selected randomly from the second set of occasions.

[0146] Although not illustrated in Figure 11, in some embodiments the method may comprise generating the counter. In some embodiments, generating the counter may comprise generating an initial value for the counter. The initial value can be an integer value. Generating the initial value for the counter may comprise selecting the initial value from a range of values, wherein the range has a minimum value and a maximum value. The minimum value may be equal to the sum of one and the number of occasions comprised in the first set of occasions. The maximum value may be equal to the sum of the number of occasions comprised in the first set of occasions and the number of occasions comprised in the second set of occasions.

[0147] Although not illustrated in Figure 11, in some embodiments, the method may comprise decreasing the counter by an incremental value in response to a criterion being met. The criterion may comprise at least one of receiving, from the network node, information indicative that the network node is able to receive an uplink transmission; determining that an uplink transmission and / or a downlink transmission has occurred at the network node; receiving a timing signal; and a first period of time elapsing in which no downlink transmission is received from the network node.

[0148] In some embodiments, each occasion in the first set of occasions can be associated with an index value. In some embodiments, the initial value for the counter can be the index value of the first occasion.

[0149] Therefore, in an example, the first wireless device may select (e.g. obtain) a second occasion in the same RACH scheduling cycle / round. The network node may provide some additional occasions in this RACH scheduling cycle / round for retransmissions of Msgl. This RACH scheduling cycle / round may comprise two sets of (e.g. RACH / PUSCH) occasions. The first set of occasions may have the size (e.g., Nsetl) equal to the number of wireless devices (e.g. UEs) (e.g. which are intended to be scheduled / polled by the network node). The second set of occasions (e.g. with size equal to Nset2) can be reserved for retransmissions of (e.g. RACH) messages. In order to avoid a second occasion colliding with an occasion owned by another wireless device, the first wireless device may generate a counter randomly out of between [Nsetl+1, Nsetl+Nset2], to determine the second occasion. The counter can decrease by 1 when one of the criterions (e.g. conditions) as described above are met. When the counter has decreased to the value equal to the index of the first occasion (when the counter is generated, there may already be a number (equal to the index of the first occasion of the first wireless device) occasions elapsed in this RACH scheduling cycle / round), the first wireless device may (e.g. randomly) selects an occasion out of available occasions at that moment (e.g., there may be multiple occasions available in frequency domain, wherein each occasion may be located on a specific frequency region, e.g., a subband, or a PRB region).

[0150] In some embodiments, the second occasion can be one of the plurality of occasions associated with the second RA scheduling interval corresponding to the network node. In these embodiments, each of the occasions of the first plurality of occasions can be associated with an index value, each of the occasions of the second plurality of occasions can be associated with an index value, and the index value of the first occasion and the second occasion can be the same.

[0151] Therefore, in an example, the first wireless device can select (e.g. obtain) a second occasion in a next RACH scheduling cycle / round. In this example, the first wireless device may select an occasion that is the “same” as that selected for the first occasion in the previous RACH scheduling cycle / round. If the first wireless device cannot obtain a (e.g. RACH / PUSCH) occasion in the next scheduling cycle / round, the first wireless device may continue to attempt to obtain more occasions in one or more further RACH scheduling cycles / rounds (e.g. if it is still allowed to do so). The first wireless device may only be allowed to do this if an overall delay for the RA procedure has exceeded a given time period or a given number of transmission attempts (e.g. for Msgl). In some examples, the network node (e.g. RAN node) may indicate that the first wireless device stop accessing the channel (e.g. in a DL response message). This may assume that the network node can detect the UE ID but may not decode data in the first message.

[0152] In some embodiments, the first RA scheduling interval can be configured by the network node. In some embodiments, the second RA scheduling interval can be configured by the network node.

[0153] After selecting the second occasion, the first wireless device may (re)transmit the first message (e.g. Msg 1). If the retransmitted first message includes a PRACH preamble, the UE may transmit the same or different preamble as previous first message. The UE ID may be different in retransmitted first message compared to previous first message. The first wireless device may regenerate / re select a different UE ID (e.g. an ID used for collision resolution).

[0154] The first wireless device (e.g. UE) may determine whether a RACH procedure is completed successfully depending on the below conditions: after sending the first message of the RACH procedure, the UE has received a response message from the gNB before the RAR timer / MsgB timer is expired.

[0155] - the UE has received a response message from the gNB which contains an indicator (e.g., a UE ID or a contention resolution MAC CE) indicating that the UE has won the contention resolution.

[0156] The first wireless device (e.g. UE) may successfully complete a RACH procedure across multiple channels / carriers / subbands. In other words, the first wireless device (e.g. UE) may transmit or receive RACH messages in the same RACH procedure across multiple channels / carriers / subbands. If one RACH message doesn’t get through on one channel / carrier / subband (e.g. due to the channel is congested), the first wireless device (e.g. UE) may switch to another channel to perform further transmissions or receptions.

[0157] If the first wireless device (e.g. UE) performs a UL transmission in a backscatter fashion, the first wireless device (e.g. UE) may receive / detect multiple carrier waves (e.g. sent by the same or different network nodes or UEs) during the RACH procedure. In such a scenario, the first wireless device (e.g. UE) may backscatter its UL RACH transmissions towards a network node (e.g. gNB). A carrier wave sent by the same or different network nodes or UEs may be separated in time and / or frequency domain. When the network node successfully decodes backscattered transmission associated with multiple carrier waves, it may select a carrier wave for which it has received the associated backscattered transmission with the highest received power. The network node may access the first wireless device (e.g. UE) only with the selected carrier wave. In case the selected carrier wave is from another network node or UE, the network node (e.g. gNB) may inform that network node or UE to transmit the carrier wave before accessing the first wireless device (e.g. UE).

[0158] There is also provided a computer program comprising instructions which, when executed by processing circuitry (such as the processing circuitry 22 of the first wireless device 20 described herein and / or the processing circuitry 12 of the network node 10 described herein), cause the processing circuitry to perform at least part of the method described herein. There is provided a computer program product, embodied on a non-transitory machine-readable medium, comprising instructions which are executable by processing circuitry (such as the processing circuitry 22 of the first wireless device 20 described herein and / or the processing circuitry 12 of the network node 10 described herein) to cause the processing circuitry to perform at least part of the method described herein. There is provided a computer program product comprising a carrier containing instructions for causing processing circuitry (such as the processing circuitry 22 of the first wireless device 20 described herein and / or the processing circuitry 12 of the network node 10 described herein) to perform at least part of the method described herein. In some embodiments, the carrier can be any one of an electronic signal, an optical signal, an electromagnetic signal, an electrical signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0159] Figure 12 shows an example of a communication system 1100 in accordance with some embodiments. In the example, the communication system 1100 includes a telecommunication network 1102 that includes an access network 1104, such as a radio access network (RAN), and a core network 1106, which includes one or more core network nodes 1108. The access network 1104 includes one or more access network nodes, such as network nodes 1110a and 1110b (one or more of which may be generally referred to as network nodes 1110), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, 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 telecommunication network 1102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 1102 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 1102, including one or more network nodes 1110 and / or core network nodes 1108.

[0160] 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 0-2 interface defined by the 0-RAN Alliance or comparable technologies. The network nodes 1110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1112a, 1112b, 1112c, and 1112d (one or more of which may be generally referred to as UEs 1112) to the core network 1106 over one or more wireless connections.

[0161] 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 1100 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 1100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0162] The UEs 1112 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 1110 and other communication devices. Similarly, the network nodes 1110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1112 and / or with other network nodes or equipment in the telecommunication network 1102 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 1102.

[0163] In the depicted example, the core network 1106 connects the network nodes 1110 to one or more hosts, such as host 1116. 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 1106 includes one more core network nodes (e.g., core network node 1108) 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 1108. 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).

[0164] The host 1116 may be under the ownership or control of a service provider other than an operator or provider of the access network 1104 and / or the telecommunication network 1102, and may be operated by the service provider or on behalf of the service provider. The host 1116 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and / or pre-recorded audio / video content, data collection services, for example, 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.

[0165] As a whole, the communication system 1100 of Figure 12 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); 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 (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.

[0166] In some examples, the telecommunication network 1102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1102. For example, the telecommunications network 1102 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) / Massive loT services to yet further UEs.

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

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

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

[0170] Figure 13 shows a UE 1200 in accordance with some embodiments. 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 camera, 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, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0171] A UE 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, 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).

[0172] The UE 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input / output interface 1206, a power source 1208, a memory 1210, a communication interface 1212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 13. 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.

[0173] The processing circuitry 1202 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 1210. The processing circuitry 1202 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 1202 may include multiple central processing units (CPUs). The processing circuitry 1202 may be operable to provide, either alone or in conjunction with other UE 1200 components, such as the memory 1210, UE 1200 functionality. For example, the processing circuitry 1202 may be configured to cause the UE 1202 to perform the methods as described with reference to any of Figures 9 to 11.

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

[0175] The memory 1210 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 1210 includes one or more application programs 1214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1216. The memory 1210 may store, for use by the UE 1200, any of a variety of various operating systems or combinations of operating systems. The memory 1210 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 1210 may allow the UE 1200 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 a communication system may be tangibly embodied as or in the memory 1210, which may be or comprise a device-readable storage medium. The processing circuitry 1202 may be configured to communicate with an access network or other network using the communication interface 1212. The communication interface 1212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1222. The communication interface 1212 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 1218 and / or a receiver 1220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1218 and receiver 1220 may be coupled to one or more antennas (e.g., antenna 1222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0176] In some embodiments, communication functions of the communication interface 1212 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 / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0177] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1212, 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. The 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).

[0178] As another example, a UE 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, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or controls a robotic arm performing a medical procedure according to the received input.

[0179] A UE, 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, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are devices which are or which are 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 head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), 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. A UE in the form of an loT device comprises circuitry and / or software in dependence on the intended application of the loT device in addition to other components as described in relation to the UE 1200 shown in Figure 13.

[0180] 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 3GPP 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.

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

[0182] Figure 14 shows a network node 1300 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, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), 0-RAN nodes or components of an 0-RAN node (e.g, O-RU, O-DU, O-CU).

[0183] 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 base stations, pico base stations, micro base stations, 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 0-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 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).

[0184] Other examples of network nodes 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).

[0185] The network node 1300 includes processing circuitry 1302, a memory 1304, a communication interface 1306, and a power source 1308, and / or any other component, or any combination thereof. The network node 1300 may be composed of multiple physically separate components (e.g., a NodeB 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 1300 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 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 1300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1304 for different RATs) and some components may be reused (e.g., a same antenna 1310 may be shared by different RATs). The network node 1300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, 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 1300.

[0186] The processing circuitry 1302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, applicationspecific 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 1300 components, such as the memory 1304, network node 1300 functionality. For example, the processing circuitry 1302 may be configured to cause the network node to perform the methods as described with reference to Figure 7.

[0187] In some embodiments, the processing circuitry 1302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1302 includes one or more of radio frequency (RF) transceiver circuitry 1312 and baseband processing circuitry 1314. In some embodiments, the radio frequency (RF) transceiver circuitry 1312 and the baseband processing circuitry 1314 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 1312 and baseband processing circuitry 1314 may be on the same chip or set of chips, boards, or units.

[0188] The memory 1304 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 1302. The memory 1304 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 1302 and utilized by the network node 1300. The memory 1304 may be used to store any calculations made by the processing circuitry 1302 and / or any data received via the communication interface 1306. In some embodiments, the processing circuitry 1302 and memory 1304 is integrated.

[0189] The communication interface 1306 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 1306 comprises port(s) / terminal(s) 1316 to send and receive data, for example to and from a network over a wired connection. The communication interface 1306 also includes radio front-end circuitry 1318 that may be coupled to, or in certain embodiments a part of, the antenna 1310. Radio front-end circuitry 1318 comprises filters 1320 and amplifiers 1322. The radio front-end circuitry 1318 may be connected to an antenna 1310 and processing circuitry 1302. The radio front-end circuitry may be configured to condition signals communicated between antenna 1310 and processing circuitry 1302. The radio front-end circuitry 1318 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 1318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1320 and / or amplifiers 1322. The radio signal may then be transmitted via the antenna 1310. Similarly, when receiving data, the antenna 1310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1318. The digital data may be passed to the processing circuitry 1302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0190] In certain alternative embodiments, the network node 1300 does not include separate radio front-end circuitry 1318, instead, the processing circuitry 1302 includes radio front-end circuitry and is connected to the antenna 1310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1312 is part of the communication interface 1306. In still other embodiments, the communication interface 1306 includes one or more ports or terminals 1316, the radio front-end circuitry 1318, and the RF transceiver circuitry 1312, as part of a radio unit (not shown), and the communication interface 1306 communicates with the baseband processing circuitry 1314, which is part of a digital unit (not shown).

[0191] The antenna 1310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1310 may be coupled to the radio front-end circuitry 1318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1310 is separate from the network node 1300 and connectable to the network node 1300 through an interface or port.

[0192] The antenna 1310, communication interface 1306, and / or the processing circuitry 1302 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 1310, the communication interface 1306, and / or the processing circuitry 1302 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.

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

[0194] Embodiments of the network node 1300 may include additional components beyond those shown in Figure 14 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 1300 may include user interface equipment to allow input of information into the network node 1300 and to allow output of information from the network node 1300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1300. Figure 15 is a block diagram of a host 1400, which may be an embodiment of the host 1116 of Figure 12, in accordance with various aspects described herein. As used herein, the host 1400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1400 may provide one or more services to one or more UEs.

[0195] The host 1400 includes processing circuitry 1402 that is operatively coupled via a bus 1404 to an input / output interface 1406, a network interface 1408, a power source 1410, and a memory 1412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 12 and 13, such that the descriptions thereof are generally applicable to the corresponding components of host 1400.

[0196] The memory 1412 may include one or more computer programs including one or more host application programs 1414 and data 1416, which may include user data, e.g., data generated by a UE for the host 1400 or data generated by the host 1400 for a UE. Embodiments of the host 1400 may utilize only a subset or all of the components shown. The host application programs 1414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 1414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0197] Figure 16 is a block diagram illustrating a virtualization environment 1500 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 1500 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 1500 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.

[0198] Applications 1502 (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.

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

[0200] The VMs 1508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1506. Different embodiments of the instance of a virtual appliance 1502 may be implemented on one or more of VMs 1508, 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. In the context of NFV, a VM 1508 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 1508, and that part of hardware 1504 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 1508 on top of the hardware 1504 and corresponds to the application 1502.

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

[0202] Figure 17 shows a communication diagram of a host 1602 communicating via a network node 1604 with a UE 1606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as aUE 1112a ofFigure 12 and / or UE 1200 ofFigure 13), network node (such as network node 1110a ofFigure 12 and / or network node 1300 ofFigure 14), and host (such as host 1116 ofFigure 12 and / or host 1400 ofFigure 15) discussed in the preceding paragraphs will now be described with reference to Figure 17.

[0203] Like host 1400, embodiments of host 1602 include hardware, such as a communication interface, processing circuitry, and memory. The host 1602 also includes software, which is stored in or accessible by the host 1602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1606 connecting via an over-the-top (OTT) connection 1650 extending between the UE 1606 and host 1602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1650.

[0204] The network node 1604 includes hardware enabling it to communicate with the host 1602 and UE 1606. The connection 1660 may be direct or pass through a core network (like core network 1106 of Figure 12) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0205] The UE 1606 includes hardware and software, which is stored in or accessible by UE 1606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1606 with the support of the host 1602. In the host 1602, an executing host application may communicate with the executing client application via the OTT connection 1650 terminating at the UE 1606 and host 1602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1650.

[0206] The OTT connection 1650 may extend via a connection 1660 between the host 1602 and the network node 1604 and via a wireless connection 1670 between the network node 1604 and the UE 1606 to provide the connection between the host 1602 and the UE 1606. The connection 1660 and wireless connection 1670, over which the OTT connection 1650 may be provided, have been drawn abstractly to illustrate the communication between the host 1602 and the UE 1606 via the network node 1604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0207] As an example of transmitting data via the OTT connection 1650, in step 1608, the host 1602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1606. In other embodiments, the user data is associated with a UE 1606 that shares data with the host 1602 without explicit human interaction. In step 1610, the host 1602 initiates a transmission carrying the user data towards the UE 1606. The host 1602 may initiate the transmission responsive to a request transmitted by the UE 1606. The request may be caused by human interaction with the UE 1606 or by operation of the client application executing on the UE 1606. The transmission may pass via the network node 1604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1612, the network node 1604 transmits to the UE 1606 the user data that was carried in the transmission that the host 1602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1614, the UE 1606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1606 associated with the host application executed by the host 1602.

[0208] In some examples, the UE 1606 executes a client application which provides user data to the host 1602. The user data may be provided in reaction or response to the data received from the host 1602. Accordingly, in step 1616, the UE 1606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 1606. Regardless of the specific manner in which the user data was provided, the UE 1606 initiates, in step 1618, transmission of the user data towards the host 1602 via the network node 1604. In step 1620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1604 receives user data from the UE 1606 and initiates transmission of the received user data towards the host 1602. In step 1622, the host 1602 receives the user data carried in the transmission initiated by the UE 1606.

[0209] One or more of the various embodiments improve the performance of OTT services provided to the UE 1606 using the OTT connection 1650, in which the wireless connection 1670 forms the last segment. More precisely, the teachings of these embodiments may improve the allocation and utilization of resources for hardware limited devices, such as A-IoT devices, and thereby provide benefits such as reduces likelihood and / or probability of RA (e.g. RACH) collisions in a network, and an improved RA framework for both active and passive devices, such as A-IoT devices.

[0210] In an example scenario, factory status information may be collected and analyzed by the host 1602. As another example, the host 1602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1602 may store surveillance video uploaded by a UE. As another example, the host 1602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0211] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1650 between the host 1602 and UE 1606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1602 and / or UE 1606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1650 while monitoring propagation times, errors, etc.

[0212] Although the computing devices described herein (e.g., UEs, network nodes) 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.

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

Claims

Claims1. A method for handling scheduling information in a network, wherein the method is performed by a network node (10) of the network, the method comprising: determining a number of one or more occasions to be configured for one or more wireless devices (20) of the network in a random access, RA, scheduling interval; initiating transmission of scheduling information towards a first wireless device (20) of the one or more wireless devices (20), wherein the scheduling information is configured to be used by the first wireless device to perform a RA procedure with the network node (10) in at least one occasion of the one or more occasions.

2. The method of claim 1, wherein the scheduling information comprises one or more of:- first information configured to be used by the first wireless device (20) to generate a first identifier; second information indicative of an initiation of the scheduling interval;- third information indicative of the number of the one or more occasions determined by the network node (10);- fourth information indicative of a network medium associated with the RA scheduling interval;- fifth information indicative of a request for the first wireless device (20) to configure a status of the first wireless device (20), wherein the status of the first wireless device (20) is associated with a RA status of the first wireless device (20); sixth information indicative of a request for the first wireless device (20) to generate a contention resolution identifier; and- seventh information indicative of a request for the first wireless device (20) to perform a computation required for communication with the network node (10).

3. The method of claim 2, wherein the first identifier is a radio network temporary' identifier, RNTI.

4. The method of claim 2 or 3, wherein the first information comprises: a sequence number; and / or an index.

5. The method of any of claims 2 to 4, wherein the second information comprises:- information indicative that the scheduling interval has been initiated; or- information indicative of a first point in time at which the scheduling interval is to be initiated.

6. The method of claim 5, wherein the information indicative of a first point in time at which the scheduling interval is to be initiated comprises a first period of time to elapse after receipt of the scheduling information.

7. The method of any of claims 2 to 6, wherein the network medium comprises one or more of: one or more channels of the network; and one or more carriers of the network.

8. The method of any of claims 2 to 7, wherein the network medium comprises one or more sub bands of the network.

9. The method of any of claims 2 to 8, wherein the contention resolution identifier is to be used by the first wireless device (20) for contention-based RA.

10. The method of any of claims 2 to 8, wherein the RA scheduling interval is initiated in response to initiating transmission of the scheduling information.

11. The method of any of the preceding claims, wherein the one or more occasions are configured to be used by the one or more wireless devices (20) to perform a RA procedure with the network node (10).

12. The method of any of the preceding claims, wherein the one or more occasions comprise:- one or more random access channel, RACH, occasions; and / or- one or more physical uplink shared channel, PUSCH, occasion.

13. The method of any of the preceding claims, the method comprising receiving a first message from the first wireless device in the at least one occasion.

4. The method of claim 13, the method comprising in response to receiving the first message: assigning a carrier wave to the first wireless device (20); assigning a transmit power configuration to the first wireless device (20); and / or

Images