On method of signaling DL trigger for a-IOT devices

Abstract

Systems and methods are disclosed for providing a downlink (DL) trigger mechanism which can comprise of one or more signaling messages carrying information pertinent to device selection and device resource allocation parameters for random access or command request or inventory access. In one embodiment, a method performed by a User Equipment (UE) comprises receiving, from a Radio Access Network (RAN), one or more signaling messages comprising either: (a) a combined select and query signaling message or (b) separate select and query signaling messages. The method further comprises operating in accordance with the one or more signaling messages. In this manner, the signaling procedure can be adapted to device capabilities, requirements, energy storage, which enables the device to successfully decode this signaling. Without this signaling, the devices may not be able kickstart their inventory or random access.

Description

[0001] ON METHOD OF SIGNALING DL TRIGGER FOR A-IoT DEVICES

[0002] RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 644,856, filed May 9, 2024, the disclosure of which is hereby incorporated herein by reference in its entirety.

[0004] TECHNICAL FIELD

[0005] The present disclosure relates to a wireless communications system and, more specifically, signaling of a downlink trigger to devices such as, for example, an Ambient Internet of Things (A-IoT) devices.

[0006] BACKGROUND

[0007] Wireless Internet of Things (loT) devices are often battery powered and both the need to change battery and the battery lifetime may be concerns for many potential applications such as asset tracking or environmental / industrial sensors. For this reason, the wireless communications industry has been interested in so-called Zero-Energy (ZE) devices. ZE devices refer to wireless loT devices that do not require battery replacement and often harvest energy from the environment. In some use cases, such as monitoring the temperature of foodstuffs, the ZE devices may have small batteries that are disposable (e.g., organic, compostable batteries), rechargeable, or have very limited capacity.

[0008] In addition, ZE-IoT devices can be of very small form factor and could even be printable, and they target ultra-low power consumption to enable operation based on either energy -harvesting from an ambient sources or back-scattering communication (cf. Radio Frequency Identification (RFID)). That is, instead of relying on energy for communication being provided by a battery, energy is instead harvested from an ambient source, such as vibrations, solar power, RF, etc. (harvesting), or, in the case of back-scattering communication, a charge carrier wave is provided to the device which is modulated and reflected back to a. This enables energy autonomous operation during the lifetime of the devices without the 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 associated protocols.

[0009] Recently, work on ZE loT has started in 3rdGeneration Partnership Project (3GPP), where this is referred to as ‘Ambient-IoT’. 3GPP Technical Report (TR) 22.840 is being developed by 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 (see 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, and the study item description from RP -222686 is reproduced below:

[0010] ***** START EXCERPT FROM RP-222685 *****

[0011] 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 LPWA IoT technology e.g. NB-IoT including with reduced peak Tx power.

[0012] In terms of energy storage, the study will consider the following device characteristics:

[0013] • Pure batteryless devices with no energy storage capability at all, and completely dependent on the availability of an external source of energy

[0014] • Devices with limited energy storage capability that do not need to be replaced or recharged manually.

[0015] Device categorization based on corresponding characteristics (e.g. energy source, energy storage capability, passive / active transmission, etc.) may be discussed during the study, in relation with the relevant use cases. The device’s peak power consumption shall be limited by its practical form factor for the intended use cases, and shall consider its energy source.

[0016] Identify the suitable deployment scenarios and their characteristics, at least for the use cases / services agreed in SAl’s “Study on Ambient power-enabled internet of Things”, comprising among at least the following aspects

[0017] • Indoor / outdoor environment

[0018] • Basestation characteristics, e.g. macro / micro / pico cells-based deployments

[0019] • Connectivity topologies, including which node(s) , e.g. basestation, UE, relay, repeater, etc. can communicate with target devices

[0020] • TDD / FDD, and frequency bands in licensed or unlicensed spectrum

[0021] • Coexistence with Ues and infrastructure in frequency bands for existing 3 GPP technologies

[0022] • Device originated and / or device terminated traffic assumption

[0023] NOTE: There can be more than one deployment scenario identified for a use case, and a deployment scenario may be common to more than one use case.

[0024] NOTE: Where more than one deployment scenario is identified for a use case, the trade-offs between them should also be studied.

[0025] NOTE: The study shall not prioritize deployment aspects that should be coordinated with SA, e.g. public or private network, with or without CN connection.

[0026] NOTE: A representative use case can be studied for a group of use cases that have similar requirements.

[0027] Formulate a set of RAN design targets based on the identified deployment scenarios and their characteristics for the relevant use cases, at least including

[0028] - Power consumption

[0029] - Complexity

[0030] - Coverage

[0031] - Data rate

[0032] - Positioning accuracy

[0033] NOTE: The requirements from SAI on the relevant use cases shall be taken into consideration. NOTE: The study shall aim to provide better coverage compared to existing non-3GPP technologies for the relevant use cases.

[0034] NOTE: Other RAN design targets in relation to connection density, mobility, security, latency, reliability etc. may be discussed, if necessary for the relevant use cases.

[0035] NOTE: Detailed definitions of the RAN design targets should be discussed during the study.

[0036] Compare and assess the feasibility of meeting the design targets for relevant use case on the basis of the deployment scenario(s) appropriate to it, and identify assumptions on required functionality to be supported.

[0037] NOTE: This is not to require a detailed WG-level of analysis.

[0038] Note: This study shall target for an loT segment well below the existing 3GPP loT technologies, e.g. NB-IoT, eMTC, RedCap, etc. The study shall not aim to replace existing 3GPP LPWA technologies.

[0039] ***** END EXCERPT FROM RP -222685 *****

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

[0041] Deployment scenarios, use cases, services for Ambient-IoT are described in clause 4 of 3GPP TR 38.848 V 18.0.0, excerpts of which are included below.

[0042] ***** START EXCERPTS FROM 3GPP TR 38.848 *****

[0043] Use cases / services

[0044] 4.1.1 Representative use cases

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

[0046] Grouping A:

[0047] - Indoor

[0048] - Outdoor

[0049] - Indoor / outdoor

[0050] Grouping B:

[0051] - Inventory

[0052] - Sensors

[0053] - Positioning

[0054] - Command

[0055] These two groupings are then used to form representative use cases (rUCs) as follows, which are used in Clause 4.2 - Deployment scenarios and connectivity topologies.

[0056] - rUC 1 : Indoor inventory - rUC2: Indoor sensors

[0057] - rUC3: Indoor positioning

[0058] - rUC4: Indoor command

[0059] - rUC5: Outdoor inventory

[0060] - rUC6: Outdoor sensors

[0061] - rUC7: Outdoor positioning

[0062] - rUC8: Outdoor command

[0063] This resulted in the following mapping from SAI use cases and traffic scenarios onto RAN rUCs:

[0064] Table 4.1.1-1 : Mapping between RAN representative use cases and SA1 use cases

[0065] ***** NEXT EXCERPT FROM 3GPP TR 38.848 ***** 4.2.1 Connectivity topologies

[0066] 4.2.1.0 Introduction

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

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

[0069] 4.2.1.1 Topology 1 : BS - Ambient loT device

[0070] [RECREATED HEREIN AS FIGURE 1]

[0071] Figure 4.2.1.1 -1 : Topology 1

[0072] In Topology 1, the Ambient loT device directly and bidirectionally communicates with a basestation. The communication between the basestation and the ambient loT device includes Ambient loT data and / or signalling. This topology includes the possibility that the BS transmitting to the Ambient loT device is a different from the BS receiving from the Ambient loT device.

[0073] 4.2.1 .2 Topology 2: BS - intermediate node - Ambient loT device

[0074] [RECREATED HEREIN AS FIGURE 2]

[0075] Figure 4.2.1.2-1 : Topology 2

[0076] In Topology 2, the Ambient loT device communicates bidirectionally with an intermediate node between the device and basestation. In this topology, the intermediate node can be a relay, IAB node, UE, repeater, etc. which is capable of Ambient loT. The intermediate node transfers Ambient loT data and / or signalling between BS and the Ambient loT device.

[0077] 4.2.1 .3 Topology 3: BS assisting node Ambient loT device BS

[0078] [RECREATED HEREIN AS FIGURE 3]

[0079] Figure 4.2.1.3-1 : Topology 3 with downlink assistance

[0080] [RECREATED HEREIN AS FIGURE 4]

[0081] Figure 4.2.1.3-2: Topology 3 with uplink assistance

[0082] In Topology 3, the Ambient loT device transmits data / signalling to a basestation, and receives data / signalling from the assisting node; or the Ambient loT device receives data / signalling from a basestation and transmits data / signalling to the assisting node. In this topology, the assisting node can be a relay, IAB, UE, repeater, etc. which is capable of ambient loT. 4.2.1.4 Topology 4: UE - Ambient loT device

[0083] [RECREATED HEREIN AS FIGURE 5]

[0084] Figure 4.2.1.4-1 : Topology 4

[0085] In Topology 4, the Ambient loT device communicates bidirectionally with a UE. The communication between UE and the ambient loT device includes Ambient loT data and / or signalling.

[0086] 4.2.2 Deployment scenarios

[0087] 4.2.2.1 Deployment scenario 1 : Device indoors, basestation indoors

[0088] With Ambient loT device indoors and basestation indoors, this deployment scenario is characterized according to Table 4.2.2.1-1.

[0089] Table 4.2.2.1-1 : Characteristics of deployment scenario 1

[0090] NOTE 1 : Descriptions may not be applicable for some Devices (A, B).

[0091] 4.2.2.2 Deployment scenario 2: Device indoors, basestation outdoors

[0092] With Ambient loT device indoors and basestation outdoors, this deployment scenario is characterized according to Table 4.2.2.2-1.

[0093] Table 4.2.2.2-1 : Characteristics of deployment scenario 2

[0094] NOTE 1 : Descriptions may not be applicable for some Devices (A, B). 4.2.2.3 Deployment scenario 3: Device indoors, UE-based reader

[0095] With Ambient loT device indoors and UE-based reader, this deployment scenario is characterized according to Table 4.2.2.3-1.

[0096] Table 4.2.2.3-1 : Characteristics of deployment scenario 3 NOTE 1 : Descriptions may not be applicable for some Devices (A, B).

[0097] 4.2.2.4 Deployment scenario 4: Device outdoors, basestation outdoors

[0098] With Ambient loT device outdoors and basestation outdoors, this deployment scenario is characterized according to Table 4.2.2.4-1.

[0099] Table 4.2.2.4-1 : Characteristics of deployment scenario 4 NOTE 1 : Descriptions may not be applicable for some Devices (A, B).

[0100] 4.2.2.5 Deployment scenario 5: Device outdoors, UE-based reader

[0101] With Ambient loT device outdoors and UE-based reader, this deployment scenario is characterized according to Table 4.2.2.5-1. Table 4.2.2.5-1 : Characteristics of deployment scenario 5

[0102] NOTE 1 : Descriptions may not be applicable for some Devices (A, B). 4.3 Device categorization

[0103] Ambient loT devices are characterized in the study according to their energy storage capacity, and capability of generating RF signals for their transmissions.

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

[0105] - No energy storage at all; or

[0106] - Limited energy storage

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

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

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

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

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

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

[0113] ***** END EXCERPTS FROM 3GPP TR 38.848 *****

[0114] In regard to functional and protocol specifications for Ambient-IoT (or ZE loT), for A-IoT, 3GPP will target an loT segment well below the existing Cellular loT (CIoT) technologies rather than replacement of existing 3GPP Low Power Wide Access (LPWA) technologies. It is expected that together with simplifications in physical layer design, the higher layer (L2 / L3) design will also be much more light-weight 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 Control (RRC) connections between device and network to connectionless type of communication without RRC connections or also even 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 do not setup and maintain an RRC connection with the network also means that A-IoT devices do not setup and maintain an Access Stratum (AS) context including (dedicated) radio bearer, logical channel, etc.

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

[0116] In RAN2#125bis, the following agreements related to access procedure in random access where made: 1 RAN2 confirms slotted-ALOHA is the baseline for Ambient loT random access

[0117] 2 We will study the support for access triggering for a single device, group of devices, or all devices. RAN2 to discuss the contention-based and contention-free access procedures and detailed solutions.

[0118] 3 Random Access is triggered by the Reader

[0119] 4 Reader provides the information that the device needs to respond to the random access trigger. FFS what those parameters are

[0120] 5 Study the solution and benefits of both 2-step like random access procedure and 4-step like random access procedure. FFS the details on each procedure and how we call it.

[0121] 6 Handling of contention resolution failure and access failure at the device will be studied in RAN2, including failure detection and re-access. FFS details

[0122] 7 For the very first access message from the device to Reader in random access an ID is included. RAN2 to discuss whether a temporary identifier is included, or the permanent device ID is included (considering other WGs input as well).

[0123] In RAN1 116bis, RANI made the following agreements regarding UL multiple access:

[0124] • Study time-domain multiple access of D2R transmissions. Further details, including pros / cons, are FFS.

[0125] • Agreement

[0126] • Study frequency-domain multiple access of D2R transmissions, at least by utilizing a small frequency-shift in baseband. Further details, including pros / cons, are FFS.

[0127] • Agreement

[0128] • Whether code-domain multiple access is feasible and necessary for D2R transmissions for all devices is FFS. SUMMARY

[0129] Systems and methods are disclosed for providing a downlink (DL) trigger mechanism which can comprise of one or more signaling messages carrying information pertinent to device selection and device resource allocation parameters for random access or command request or inventory access. In one embodiment, a method performed by a User Equipment (UE) comprises receiving, from a Radio Access Network (RAN), one or more signaling messages comprising either: (a) a combined select and query signaling message or (b) separate select and query signaling messages. The method further comprises operating in accordance with the one or more signaling messages. In this manner, the signaling procedure can be adapted to device capabilities, requirements, energy storage, which enables the device to successfully decode this signaling. Without this signaling, the devices may not be able kickstart their inventory or random access.

[0130] In one embodiment, whether the one or more signaling messages comprise a combined select and query signaling message or separate select and query signaling messages depends on any one or more of the following: one or more cell conditions, one or more network conditions, one or more device capabilities of the UE or group of UEs by which the one or more signaling messages are received, and one or more charging requirements.

[0131] In one embodiment, whether the one or more signaling messages comprise a combined select and query signaling message or separate select and query signaling messages depends on any one or more of the following: load in a cell on which the one or more signaling messages are received by the UE, one or more device capabilities of the UE or group of UEs to which the one or more signaling messages are transmitted by the RAN node, a device type of the UE or a group of UEs to which the one or more signaling messages are transmitted by the RAN node, a use case cause of an operation to which the one or more signaling messages are related.

[0132] In one embodiment, the one or more signaling messages comprise the combined select and query signaling message. In one embodiment, the combined select and query signaling message comprises both select signaling information and query signaling information. In another embodiment, the combined select and query signaling message comprises an indication that the combined select and query signaling message comprises both select signaling information and query signaling information. In one embodiment, receiving the one or more signaling messages comprises determining that the one or more received signaling messages is the combined select and query signaling message based on the indication. In another embodiment, the combined select and query signaling message has a different message format than separate select and query signaling messages. In one embodiment, receiving the one or more signaling messages comprises blindly decoding the one or more signaling messages using different message formats comprising a first message format for combined select and query signaling messages and a second message format for separate select and query messages.

[0133] In one embodiment, the one or more signaling messages comprise the separate select and query signaling messages. In one embodiment, the select signaling message comprises select signaling information and the query signaling message comprises query signaling information.

[0134] In one embodiment, the select signaling information comprises any one or more of the following: device identity (ID), list of device IDs, device group ID, list of group IDs, indication to address all devices, setting of one or more flags relevant to inventory, selection cause or criteria or establishment cause, Public Land Mobile Network (PLMN) ID or network ID, mapping of device or device group information or IDs to a local device or device group index, mapping of PLMN ID to a local PLMN index, information about a time gap between the select signaling message and the query signaling message in the case of separate select and query signaling messages, information that indicates a maximum time gap between the separate select and query signaling messages, indication of one or more additional select signaling messages followed by this select signaling, reader ID, short-term procedure ID or index, indication of single ID and that the random access is contention-free.

[0135] In one embodiment, the query signaling information comprises any one or more of the following: an indication of a number of slots, frames, or sub-slots allocated for random access; an indication of a time gap between receipt of the query signaling information and the first / zeroth slot / frame / subslot which can be first opportunity to do uplink access; a parameter indicating some maximum value or set of values in the query signaling information and upon receiving this message, the UE can select some value based on this parameter to be used as device ID or temporary ID; Frequency Division Multiplexing (FDM) or Frequency Division Multiple Access (FDMA) resource or allowable frequency shift, alternatively expressed as the allowed data rates which the device can consider random selection over for the random access; reader ID; one or more device IDs, one or more device group IDs, or one or more local device indices, or one or more device group indices; short-term procedure ID or index for identification of a select signaling information or select signaling message to which this query signaling information belongs.

[0136] In one embodiment, the query signaling targets one or more specific UEs and contains one or more flags relevant to inventory, and the UE ignores the one or more flags relevant to inventory.

[0137] In one embodiment, the RAN node is a network. In another embodiment, the RAN node is an intermediate UE.

[0138] In one embodiment, the one or more signaling messages are carried via one or more Medium Access Control (MAC) Control Elements (CEs) or one or more control Protocol Data Units (PDUs).

[0139] In one embodiment, one or more timer flags are used to indicate whether the one or more signaling messages is a combined select and query signaling message or are separate select and query signaling messages.

[0140] In one embodiment, the UE is an Ambient Internet of Things (A-IoT) UE.

[0141] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE is adapted to receive, from a RAN node, one or more signaling messages comprising either: (a) a combined select and query signaling message or (b) separate select and query signaling messages. The UE is further adapted to operate in accordance with the one or more signaling messages.

[0142] In one embodiment, a UE comprises a communication interface comprising a receiver, and the UE further comprises processing circuitry associated with the communication interface. The processing circuitry is configured to cause the UE to receive, from a RAN node, one or more signaling messages comprising either: (a) a combined select and query signaling message or (b) separate select and query signaling messages. The processing circuitry is further configured to cause the UE to operate in accordance with the one or more signaling messages.

[0143] Embodiments of a method performed by a RAN node are also disclosed. In one embodiment, a method performed by a RAN node comprises transmitting, to a UE, one or more signaling messages comprising either: (a) a combined select and query signaling message or (b) separate select and query signaling messages.

[0144] In one embodiment, the method further comprises determining whether to transmit a combined select and query signaling message or separate select and query signaling messages based on one or more cell conditions, one or more network conditions, one or more device capabilities of the UE or a group of UEs, and / or one or more charging requirements.

[0145] In one embodiment, the method further comprises determining whether to transmit a combined select and query signaling message or separate select and query signaling messages based on any one or more of the following: load in a cell on which the one or more signaling messages are transmitted, one or more device capabilities of the UE or group of UEs to which the one or more signaling messages are transmitted by the RAN node, a device type of the UE or a group of UEs to which the one or more signaling messages are transmitted by the RAN node, a use case cause of an operation to which the one or more signaling messages are related.

[0146] In one embodiment, transmitting the one or more signaling messages comprises transmitting the combined select and query signaling message if a result of the determining is to transmit the combined select and query signaling message and transmitting the separate select and query signaling messages if the result of the determining is to transmit the separate select and query signaling messages.

[0147] Corresponding embodiments of a RAN node are also disclosed. In one embodiment, a RAN node is adapted to transmit, to a UE, one or more signaling messages comprising either: (a) a combined select and query signaling message or (b) separate select and query signaling messages.

[0148] In one embodiment, a RAN node comprises a communication interface and processing circuitry associated with the communication interface. The processing circuitry is configured to cause the RAN node to transmit, to a UE, one or more signaling messages comprising either: (a) a combined select and query signaling message or (b) separate select and query signaling messages.

[0149] BRIEF DESCRIPTION OF THE DRAWINGS

[0150] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0151] Figure 1 is a recreation of Figure 4.2.1.1-1 of 3rdGeneration Partnership Project (3GPP) Technical Report (TR) 38.848 V18.0.0.

[0152] Figure 2 is a recreation of Figure 4.2.1.2-1 of 3GPP TR 38.848.

[0153] Figure 3 is a recreation of Figure 4.2.1.3-1 of 3GPP TR 38.848.

[0154] Figure 4 is a recreation of Figure 4.2.1.3-2 of 3GPP TR 38.848.

[0155] Figure 5 is a recreation of Figure 4.2.1.4-1 of 3GPP TR 38.848.

[0156] Figure 6 is a flow chart that illustrates the operation of a network node (e.g., a gNB) to transmit either a combined SELECT and QUERY signaling message or separate SELECT and QUERY signaling messages, in accordance with one example embodiment of the present disclosure.

[0157] Figure 7 illustrates the operation of a Radio Access Network (RAN) node and a User Equipment (UE) in accordance with at least some embodiments of the present disclosure.

[0158] Figures 8 and 9 illustrate an example embodiment in which the network uses a timer flag(s) to indicate whether the Select and Query are carried separately or jointly.

[0159] Figure 10 shows an example of a communication system in accordance with some embodiments.

[0160] Figure 11 shows a UE in accordance with some embodiments.

[0161] Figure 12 shows a network node in accordance with some embodiments. Figure 13 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0162] DETAILED DESCRIPTION

[0163] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

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

[0165] There currently exist certain challenge(s). Ambient loT (A-IoT) has been agreed to be as one study and / or work item for 3rdGeneration Partnership Project (3GPP) Release (Rel-) 19. The A-IoT User Equipment (UE) will be studied to support use cases like inventory or read / write command in licensed spectrum / 3GPP domain, similar to Radio Frequency (RF) Identification (RFID) operation in unlicensed spectrum.

[0166] In order to execute inventory or command, the network needs to select the A-IoT UEs (similar to RFID’s SELECT COMMAND) and allocate contend on / random-access resource (similar to RFID’s QUERY COMMAND). RFID utilizes two separate commands (i.e., RFID’s SELECT COMMAND and RFID’s QUERY COMMAND) to initiate contention for users. However, for 3GPP A-IOT operation, the problem is open, i.e., how the base station (e.g., gNodeB (gNB) in the case of New Radio (NR)) (topology 1) or an intermediate UE with or without the assistance of the base station (e.g., gNB) (topology 2) can select A-IoT UEs and also resource allocation parameters.

[0167] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Systems and methods are disclosed that provide a downlink (DL) trigger mechanism which can comprise of one or more signaling messages carrying information pertinent to device selection and device resource allocation parameters for random access or command request or inventory access. Having multiple signaling messages or not can be motivated due to following conditions or requirements or capabilities: • If a device is unable to process a single signaling message carrying all the information due to limited energy in the storage (i.e., limited amount of stored energy), then the information is segmented into multiple signaling messages.

[0168] • If a device supports a signaling format of limited size, then reader needs to segment the information into multiple signaling messages.

[0169] • If the device resource allocation or selection of resources depends on device identity (ID) or selection criteria, then the signaling information is segmented into multiple signaling messages carrying different information.

[0170] Further details with examples are provided below.

[0171] Certain embodiments may provide one or more of the following technical advantage(s). Embodiments of the present disclosure adapt the signaling procedure to device capabilities, requirements, energy storage, which enables the device to successfully decode this signaling. Without this signaling, the devices may not be able to kickstart their inventory or random access.

[0172] In the description herein, use cases with ultra-low power devices, zero-energy, devices, or A-IoT devices are considered or assumed.

[0173] The term “RAN node” is used herein to refer to a network node or a User Equipment (UE). Examples of network nodes are NodeB, base station (BS), Multi -Standard Radio (MSR) radio node such as MSR BS, eNodeB (eNB), gNodeB (gNB), Master eNB (MeNB), Secondary eNB (SeNB), Location Measurement Unit (LMU), Integrated Access Backhaul (IAB) node, network controller, Radio Network Controller (RNC), Base Station Controller (BSC), relay, repeater, donor node controlling relay, Base Transceiver Station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, Cloud RAN (C-RAN), Access Point (AP), transmission points, transmission nodes, Transmission Reception Point (TRP), Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in Distributed Antenna System (DAS), core network node (e.g. MCS, Mobility Management Entity (MME), etc. in the case of a Evolved Packet Core (EPC) of an Evolved Packet System (EPS) or an Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy and Control Function (PCF), User Plane Function (UPF), etc. in the case of a 5thGeneration (5G) system including a 5G Core), Operations and Maintenance (O&M), Operations Support System (OSS), Self-Organizing Network (SON), positioning node (e.g. Evolved Serving Mobile Location Center (E-SMLC)), etc.

[0174] In particular, in the A-IoT scenario, the RAN nodes comprise intermediate node or intermediate UE (e.g., relay UE, IAB, repeater, etc.) and assisting node or assisting UE (e.g., relay UE, IAB, repeater etc.). In the present disclosure, the terms ‘polling’, ‘poll’, ‘paging’, ‘page’, ‘inventory’, ‘query’, ‘interrogate’, are used to represent one or more signals transmitted by a network node broadcast wise or specially to a dedicated UE. The purpose of the signal is to facilitate / serve / manage / command one or more UEs to synchronize to the network node (downlink (DL) / uplink (UL) synchronize to a reference time / frame / symbol, or synchronize to one or more than one signal which the UE receives from the network node, or synchronize based on a predefined rule), receive DL data, response and transmit UL data correctly in intended resources. The content of such signal may be a particular reference signal or a signal carrying control information and / or data. Such signal may be transmitted periodically or a periodically configured by the network node.

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

[0176] In the present disclosure, ‘intermediate node’, ‘intermediate UE’, ‘UE’ are applied interchangeably without losing the meaning.

[0177] In one embodiment of the present disclosure, a network node (e.g., gNB) sends device selection parameters or information (denoted herein as “device selection parameters / information”) and random-access parameters or information (denoted herein as “random-access parameters / information”) in the same or separate signaling messages depending on cell and network conditions, device capability, charging requirements. Note, for ease of discussion, device selection parameters / information are referred to herein as SELECT signaling, and the randomaccess parameters / information are referred to herein as QUERY signaling. Hence, in one embodiment, the network node (e.g., gNB) can either:

[0178] • transmit one signaling (e.g., one signaling message) combining both SELECT and QUERY signaling or

[0179] • separately transmit SELECT and QUERY signaling (e.g., transmit separate SELECT and QUERY signaling messages), depending on any one or more of the following network conditions:

[0180] • Load in the cell (e.g., the cell operated by the network node) o For example, if the load is high in the cell, the SELECT command unable to select or address devices in the same command / signaling, then we may need multiple SELECT signaling before QUERY command.

[0181] • Device’s capabilities or device type (e.g., one or more capabilities of a device(s) (e.g., A- loT UE(s)) to which the signaling is to be transmitted or a device type of a device(s) (e.g., A-IoT UE(s)) to which the signaling is to be transmitted) o Different device types can be indicated in different SELECT commands as the bit fields in different SELECT signaling can be interpreted in different manners by different types of devices. For instance, the SELECT signaling addressing active devices may ask the active devices to wake up again after X time units once their inventory is performed. The same bitfield in SELECT signaling addressing passive devices will be considered null, as this parameter may not be useful for passive devices due to their low capability, thus cannot monitor time implicitly.

[0182] • Use case or cause of the operation (e.g., ‘inventory’ or ‘DL command’)

[0183] Figure 6 is a flow chart that illustrates the operation of a network node (e.g., a gNB) to transmit either a combined SELECT and QUERY signaling message or separate SELECT and QUERY signaling messages, in accordance with one example embodiment of the present disclosure. As illustrated, a procedure for transmitting either a combined SELECT and QUERY signaling message or separate SELECT and QUERY signaling messages, to a UE (e.g. an A-IoT UE) or a group of UEs (e.g., a group of A-IoT UEs) is initiated (step 600). This may be initiated or triggered when the network node desires to send the signaling message(s) (e.g., upon receiving a request or command to do so, upon expiry of a timer, or the like). The network node determines whether the one or more network conditions for transmitting a combined SELECT and QUERY signaling message are satisfied (step 602). The one or more network conditions may be or include any one or more of the network conditions described above. If the one or more network conditions are satisfied (step 602, YES), the network node transmits combined SELECT and QUERY signaling message (step 604). Otherwise (step 602, NO), the network node transmits separate SELECT and QUERY signaling messages. In this example, the network node first transmits SELECT signaling message (step 606), then waits a defined or configured amount of time (step 608), and then transmits QUERY signaling message (step 610).

[0184] Figure 7 illustrates the operation of a RAN node 700 and a UE 702 in accordance with at least some embodiments of the present disclosure. Optional steps are represented by dashed lines. The RAN node 700 may be a network node (e.g., a base station such as, e.g., a gNB) (e.g., as in Topology 1 described above) or an intermediate UE (e.g., as in Topology 2 described above). The UE 702 is preferably, but not necessarily, an A-IoT UE.

[0185] As illustrated, the RAN node 700 determines whether to transmit a combined SELECT and QUERY signaling message or separate SELECT and QUERY signaling messages to the UE 702 (or to a group of UEs including the UE 702) (step 704). In one embodiment, the determining step 704 is as described above with respect to step 602 of Figure 6. In a first option (Option A), which may be responsive to the RAN node 700 determining in step 704 to transmit a combined SELECT and QUERY message, the RAN node 700 transmits, to the UE 702 (or to a group of UEs including the UE 702), a combined SELECT and QUERY signaling message (step 706).

[0186] In a second option (Option B), which may be responsive to the RAN node 700 determining in step 704 to transmit separate SELECT and QUERY messages, the RAN node 700 transmits, to the UE 702 (or to a group of UEs including the UE 702), a SELECT signaling message (step 708), optionally waits a predefined, selected, or configured amount of time (step 710), and then transmits QUERY signaling message to the UE 702 (or group of UEs including the UE 702) (step 712).

[0187] In case separate SELECT and QUERY signaling messages are sent (e.g., as in steps 708 and 710), the SELECT signaling may provide a mapping which maps a globally unique parameter such as global device ID and Public Land Mobile Network (PLMN) ID, etc., to a local index, and the local index is used in the rest of the procedure, i.e., the local index is indicated in the signaling for inventory such as QUERY and the signaling for access such as READ, WRITE, etc. The benefit is that the signaling for inventory and access is usually sent more often than SELECT thus indicating the local index in those signaling can reduce the signaling overhead.

[0188] In one embodiment, the RAN node 700 (e.g., gNB) indicates in the signaling whether the SELECT signaling additionally contains QUERY signaling parameters. For example, if a bit X is set to 1 (e.g., in the signaling message of step 706), then the signaling contains both SELECT and QUERY signaling parameters; otherwise if bit X is set to 0 (e.g., in the signaling message of step 708), then the signaling contains only SELECT signaling information (no QUERY signaling information). That is a signaling bit or flag is included to explicitly indicate to the device if the combination is used or not. In an alternative embodiment, two separate messages are instead defined as the SELECT message (as in step 708) and the combined SELECT+QUERY combination message (as in step 706), and the UE 702 performs blind decoding (e.g., during reception of the signaling message of step 706 or step 708) over the two formats of these messages to find out which one was transmitted. Alternatively, a new command with a new command code may be introduced which includes both (part of) the SELECT signaling parameters and (part of) the QUERY signaling parameters. Some parameter(s) are not needed in such new command, for instance, currently the SELECT signaling sets the relevant flags and then in the QUERY signaling the targeted devices are identified by the flags. When combining the two signaling into one, the devices can be directly identified by the device ID which is currently included in the SELECT signaling and the flags are no more needed. When receiving such signaling, the device first applies the SELECT signaling parameters and then applies the QUERY signaling parameters. In one embodiment, the SELECT signaling (included in the combined message of step 708 or the SELECT signaling message of step 708) can contain any one or more of the following types of information (i.e., only a device which matches this information will continue the procedure and process the QUERY command):

[0189] • Device ID

[0190] • List of device IDs

[0191] • Device group ID

[0192] • List of group IDs

[0193] • Indication to address all devices

[0194] • Setting of flag(s) relevant to inventory. For instance, the inventoried flag which may be set to either A or B, then the QUERY command may target device(s) with inventoried flag being A or B.

[0195] • Selection cause or criteria or establishment cause, e.g., o Inventory purpose, and / or o Read (NW polling of UL data / report) purpose o Write(DL data / command) purpose

[0196] In case a device belonging to a device group which is selected only for inventory purpose, it will not execute read / write / command that targets that device group, and vice versa.

[0197] • PLMN ID or network ID

[0198] • Mapping of device or device group information or IDs to a local device or device group index. For example, not only the device ID is included to indicated that a certain device is being addressed, but also a shorter local / short-term ID which will used to address the device during the rest of the procedure, e.g., {DeviceID=1759204, localID=4}.

[0199] • Mapping of PLMN ID to a local PLMN index. The local / short-term ID will be used during the rest of the procedure. This is needed as an A-IoT device may not know whether two different signaling is sent from the same or different nodes (unless a node ID is included in the signaling) thus the local / short-term ID is needed for the device to know to which PLMN the node sending QUERY and other signaling belongs.

[0200] • Time gap between . SELECT and QUERY signal, i.e., lime ap SELECT and QUERY o Note: if SELECT and QUERY signaling combined in same signaling, then this parameter is not needed o As an alternative, the time gap is indicated by a parameter / field explicitly (e.g., a value expressed in terms of number of symbols, slots, occasions, ms, or seconds, etc.) o As an alternative, the gap is indicated by an index of an entry in a table wherein the table comprises all possible time gap values. o As an alternative, there are multiple time gap values indicated in the signaling wherein each different time gap is associated with a specific device type / category. In this case, the device selects the time gap according to its device type / category. o As an alternative, there are multiple time gap values indicated in the signaling wherein each different time gap is associated with different measured radio channel quality level s / channel congestion levels. In this case, the device selects the time gap according to its measured radio channel quality level / channel congestion level. o As an alternative, there are multiple time gap values indicated in the signaling wherein each different time gap is associated with a different occasion. The device selects the time gap value according to the occasion on which the device has occupied / obtained for its subsequent transmissions.

[0201] • Maximum time gap between SELECT and QUERY signals, i.e., this is the maximum absolute time that a device can expect to receive a QUERY message associated with a SELECT message sent in prior, after this time has passed since SELECT message has been received the device assumes that it has not been selected anymore. This gap can be indicated along with the SELECT message or captured as a fixed value in the specifications. Note that this may only be relevant for active devices (device type 2b) which must restrict its monitoring for QUERY in time not to drain its energy storage.

[0202] • Possible indication of more SELECT signaling followed by this SELECT signaling o The purpose of send SELECT signaling again consecutively due to following reasons

[0203] ■ Different SELECT signaling contain different device IDs or device group IDs which cannot be accommodated in the same group ID or mask function

[0204] ■ Different SELECT signaling could be repetition of each other in order to increase its reliability o It can additionally indicate the time gap between consecutive SELECT signaling, i.e., time gap currentSELEC T and nextSELEC T o It can additionally indicate the remaining time (in terms of e.g., number of symbols) in which more identical SELECT signaling will be sent followed by this SELECT signaling, the device may skip monitoring in DL for a time not more than the indicated remaining time minus a margin, the margin may be determined by the device itself based on its timing accuracy or informed by the network based on e.g., the reported device type which is associated to the device’s timing accuracy. o It can additionally indicate a value Tag. If the value Tag received by a device is the same to the stored value Tag, the device may skip decoding the rest part of the SELECT signaling and / or skip applying the SELECT signaling.

[0205] • Reader ID (i.e., ID of the gNB in Topology 1 and ID of the intermediate UE in Topology 2).

[0206] • Short-term procedure ID / index for later identification of which QUERY commands belong to this SELECT (and QUERYREP). (For example., using 3 bits for 8 different values of the procedure index to allow for 8 simultaneously ongoing procedures, e.g., belonging to different PLMNS or NW owners, or allowing sufficient wrap-around for devices which may gotten stuck in an earlier procedure).

[0207] • Indication of single ID and that the random access is contention-free (see below). I.e., if a simple device cannot deduce from the single device ID (listed above) that it is the only device being addressed by the procedure, an explicit flag (1-bit indication) is needed to convey this information to the device.

[0208] In one embodiment, the QUERY signaling (included in the combined message of step 706 or the QUERY signaling message of step 712) can contain any one or more of the following types of information:

[0209] • Number of slots / frames / sub-slots allocated for random access o In another embodiment QUERY message may address multiple IDs (group or individual) and number of slots / frames / sub-slots allocated for random access can be divided and mapped to these IDs, e.g., if 20 slots are configured in total, the device(s) associated with the first ID can select a random slot between first and fifth, device(s) associated with the second ID can select a random slot between sixth and twentieth.

[0210] • Time gap between the QUERY command and the first / zeroth slot / frame / subslot which can be first opportunity to do UL access o As an alternative, the time gap is indicated by a parameter / field explicitly (e.g., a value expressed in terms of number of symbols, slots, occasions, ms, or seconds, etc.) o As an alternative, the gap is indicated by an index of an entry in a table wherein the table comprises all possible time gap values. o As an alternative, there are multiple time gap values indicated in the signaling wherein each different time gap is associated with a specific device type / category. In this case, the device selects the time gap according to its device type / category. o As an alternative, there are multiple time gap values indicated in the signaling wherein each different time gap is associated with different measured radio channel quality level s / channel congestion levels. In this case, the device selects the time gap according to its measured radio channel quality level / channel congestion level. o As an alternative, there are multiple time gap values indicated in the signaling wherein each different time gap is associated with a different occasion. The device selects the time gap value according to the occasion on which the device has occupied / obtained for its subsequent transmissions.

[0211] • Another parameter indicating some max value or set of values in Query command and upon receiving this command, the device can select some value based on this parameter (from the set, or less than equal to max, e.g., randomly or based on other function) to be used as device ID or temporary ID. This value is used by the device which enable gNB / reader / intermediate UE to address back to the device and negotiate exchanges between the device and gNB / reader initially during random access procedure

[0212] • Frequency Division Multiplexing (FDM) / Frequency Division Multiple Access (FDMA) resource / allowable frequency shift, alternatively expressed as the allowed data rates which the device can consider random selection over for the random access (discussed in other IvD in detail)

[0213] • Reader ID (i.e., ID of the gNB in Topology 1 and ID of the intermediate UE in Topology 2).

[0214] • Device or device group ID(s) or local device or device group index(s) o The ID(s) / index(s) may be associated with the time / frequency resource.

[0215] • Short-term procedure ID / index for identification of which SELECT commands this QUERY belongs to (see above).

[0216] In one embodiment, when the QUERY signaling targets specific device(s), the flag(s) relevant to inventory are ignored, i.e., the targeted device(s) will perform inventory even if the relevant flag(s) indicate that the inventory shall not be performed. In other words, the flag(s) relevant to inventory only apply to inventory of a group of device(s) or all device(s). Separate QUERY signaling with different format may be introduced for inventory of specific device(s) and inventory of a group of device(s) or all device(s).

[0217] In one embodiment, for any one of the above embodiments, it is an intermediate node / UE which sends the signaling to devices (e.g., the RAN node 700 is an intermediate node / UE). In an option, the signaling (i.e., select and / or query) is generated by the intermediate node / UE itself. In another option, the signaling (i.e., select and / or query) is fully or partially generated by the gNB (or a core network (CN) node), and sent to the intermediate node / UE. In the second step, the intermediate node / UE sends the received signaling (may with or without adjustment / update) to devices.

[0218] In an example, the signaling (i.e., select or query) (e.g., of step 706, 708, and 712) is carried via a Medium Access Control (MAC) Control Element (CE). In this case, the signaling may be associated with an identifier (e.g., a Logical Channel (LCH) channel ID, or MAC CE ID). In this case, it is the reader (e.g., the gNB or the intermediate node / UE) that determines whether or when to send one signaling or two signaling in the same transmission. Upon reception of the signaling, a device can determine the signaling type / purpose (i.e., select or query) based on the identifier associated with the signaling.

[0219] In an example, the signaling (i.e., select or query) is carried via a control Protocol Data Unit (PDU). In this case, the signaling may be associated with a control PDU type which indicates the control PDU carries content for select like signaling or query like signaling. In this case, it is the reader (e.g., the gNB or the intermediate node / UE) that determines whether or when to send one control PDU or two control PDUs in the same transmission. Upon reception of the signaling, a device can determine the signaling type / purpose (i.e., select or query) based on the control PDU type associated with the signaling.

[0220] In one embodiment, if only one device (e.g., only one UE 702) is indicated in the SELECT message, then contention-based resource allocation is not needed. Thus, the device can be provided with single access slot after SELECT message. Here query information is not needed, as there is one device. The time domain information of the access slot can be:

[0221] • Either indicated in SELECT message, e.g., some time gap can be mentioned, i.e., the time reference of access slot w.r.t. SELECT message (say time gap SELECT and AccessSlot), or

[0222] • the network can define default time gap between SELECT signaling and access slot (time gap SELECT and AccessSlot), thus, time gap SELECT and AccessSlot is not required to be indicated in the SELECT message, or • Pre-defined and implicit. I.e., since it is understood that the number of slots for random selection is 1 in this case, it would be implicitly understood by the UE in this case that it should use this slot for access.

[0223] In one embodiment, the device (e.g., the UE 702) considers the message size of DL transmission indicated in the control information (for the signaling message of steps 706, 708, and 712) to determine whether the message is Select or Query or both. In an example, the Query message can be of the shortest size in terms of number of bits, because it only provides the randomaccess parameter namely Q-value, and the Select message is of bigger size as it contains the device identifier and other selection parameters. Finally, the message size of Select + Query is the biggest as it contains both the selection and random access parameters. Therefore, given the transmission size the device can determine whether the message is Select, Query, or both.

[0224] Message size of (Query) < Message size of (Select) < Message size of (Query + Select)

[0225] In one embodiment, the network (e.g., the RAN node 700) uses timer flags to indicate whether the Select and Query are carried separately or jointly, as shown in Figures 8 and 9.

[0226] In a sub-embodiment, when the Query message follows the Select message, the network assigns the value of the timer i.e., TR?T> _R?D min: Minimum Time between two different consecutive R2D transmissions to the same A-IoT device. See Figure 8.

[0227] In another sub-embodiment, when the Query and Select message are combined in the same message, the network assigns the value of timer TROD mm: Minimum Time between a R2D transmission and the corresponding D2R transmission following it. See Figure 9.

[0228] Figure 10 shows an example of a communication system 1000 in accordance with some embodiments.

[0229] In the example, the communication system 1000 includes a telecommunication network 1002 that includes an access network 1004, such as a Radio Access Network (RAN), and a core network 1006, which includes one or more core network nodes 1008. The access network 1004 includes one or more access network nodes, such as network nodes 1010A and 1010B (one or more of which may be generally referred to as network nodes 1010), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs). 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 1002 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 1002 that supports an ORAN specification (e.g., a specification published by the 0-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 1002, including one or more network nodes 1010 and / or core network nodes 1008.

[0230] Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O- CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non- real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the 0-RAN Alliance or comparable technologies. The network nodes 1010 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 1012A, 1012B, 1012C, and 1012D (one or more of which may be generally referred to as UEs 1012) to the core network 1006 over one or more wireless connections.

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

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

[0233] In the depicted example, the core network 1006 connects the network nodes 1010 to one or more hosts, such as host 1016. 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 1006 includes one more core network nodes (e.g., core network node 1008) 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 1008. 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).

[0234] The host 1016 may be under the ownership or control of a service provider other than an operator or provider of the access network 1004 and / or the telecommunication network 1002, and may be operated by the service provider or on behalf of the service provider. The host 1016 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0235] As a whole, the communication system 1000 of Figure 10 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 1000 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 Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (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.

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

[0237] In some examples, the UEs 1012 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 1004 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1004. Additionally, a UE may be configured for operating in single- or multi -Radio Access Technology (RAT) or multi-standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).

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

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

[0240] Figure 11 shows a UE 1100 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 Internet Protocol (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 3 GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0241] 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).

[0242] The UE 1100 includes processing circuitry 1102 that is operatively coupled via a bus 1104 to an input / output interface 1106, a power source 1108, memory 1110, a communication interface 1112, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 11. 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.

[0243] The processing circuitry 1102 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 1110. The processing circuitry 1102 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 1102 may include multiple Central Processing Units (CPUs).

[0244] In the example, the input / output interface 1106 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 1100. 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.

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

[0246] The memory 1110 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1110 includes one or more application programs 1114, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1116. The memory 1110 may store, for use by the UE 1100, any of a variety of various operating systems or combinations of operating systems.

[0247] The memory 1110 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 RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and / or Internet Protocol Multimedia Services Identity Module (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 a ‘SIM card.’ The memory 1110 may allow the UE 1100 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 1110, which may be or comprise a device-readable storage medium.

[0248] The processing circuitry 1102 may be configured to communicate with an access network or other network using the communication interface 1112. The communication interface 1112 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1122. The communication interface 1112 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 1118 and / or a receiver 1120 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1118 and receiver 1120 may be coupled to one or more antennas (e.g., the antenna 1122) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0249] In the illustrated embodiment, communication functions of the communication interface 1112 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, NFC, 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 according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.

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

[0251] 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 to a robotic arm performing a medical procedure according to the received input.

[0252] A UE, when in the form of an loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, 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 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 of the intended application of the loT device in addition to other components as described in relation to the UE 1100 shown in Figure 11.

[0253] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3 GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

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

[0255] Figure 12 shows a network node 1200 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, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and 0-RAN nodes or components of an 0-RAN node (e.g., O-RU, O-DU, O-CU). 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 RRUs 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).

[0256] Other examples of network nodes include multiple Transmission Point (multi-TRP) 5G access nodes, Multi -Standard Radio (MSR) equipment such as MSRBSs, network controllers such as Radio Network Controllers (RNCs) or BS 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).

[0257] The network node 1200 includes processing circuitry 1202, memory 1204, a communication interface 1206, and a power source 1208. The network node 1200 may be composed of multiple physically separate components (e.g., a NodeB component and an 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 1200 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 1200 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 1204 for different RATs) and some components may be reused (e.g., a same antenna 1210 may be shared by different RATs). The network node 1200 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1200, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (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 the network node 1200. The processing circuitry 1202 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, 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 1200 components, such as the memory 1204, to provide network node 1200 functionality.

[0258] In some embodiments, the processing circuitry 1202 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 1202 includes one or more of Radio Frequency (RF) transceiver circuitry 1212 and baseband processing circuitry 1214. In some embodiments, the RF transceiver circuitry 1212 and the baseband processing circuitry 1214 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 the RF transceiver circuitry 1212 and the baseband processing circuitry 1214 may be on the same chip or set of chips, boards, or units.

[0259] The memory 1204 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable, and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1202. The memory 1204 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 1202 and utilized by the network node 1200. The memory 1204 may be used to store any calculations made by the processing circuitry 1202 and / or any data received via the communication interface 1206. In some embodiments, the processing circuitry 1202 and the memory 1204 are integrated.

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

[0261] In certain alternative embodiments, the network node 1200 does not include separate radio front-end circuitry 1218; instead, the processing circuitry 1202 includes radio front-end circuitry and is connected to the antenna 1210. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1212 is part of the communication interface 1206. In still other embodiments, the communication interface 1206 includes the one or more ports or terminals 1216, the radio front-end circuitry 1218, and the RF transceiver circuitry 1212 as part of a radio unit (not shown), and the communication interface 1206 communicates with the baseband processing circuitry 1214, which is part of a digital unit (not shown).

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

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

[0264] The power source 1208 provides power to the various components of the network node 1200 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1208 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1200 with power for performing the functionality described herein. For example, the network node 1200 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1208. As a further example, the power source 1208 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.

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

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

[0267] Applications 1302 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1300 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0268] Hardware 1304 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, an input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1306 (also referred to as hypervisors or Virtual Machine Monitors (VMMs)), provide VMs 1308A and 1308B (one or more of which may be generally referred to as VMs 1308), and / or perform any of the functions, features, and / or benefits described in relation with some embodiments described herein. The virtualization layer 1306 may present a virtual operating platform that appears like networking hardware to the VMs 1308.

[0269] The VMs 1308 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 1306. Different embodiments of the instance of a virtual appliance 1302 may be implemented on one or more of VMs 1308, 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.

[0270] In the context of NFV, a VM 1308 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 1308, and that part of the hardware 1304 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 1308 on top of the hardware 1304 and corresponds to the application 1302.

[0271] The hardware 1304 may be implemented in a standalone network node with generic or specific components. The hardware 1304 may implement some functions via virtualization. Alternatively, the hardware 1304 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 1310, which, among others, oversees lifecycle management of the applications 1302. In some embodiments, the hardware 1304 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 1312 which may alternatively be used for communication between hardware nodes and radio units.

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

[0273] 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. Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

[0274] Some exemplary embodiments of the present disclosure are as follows:

[0275] Group A Embodiments

[0276] Embodiment 1 : A method performed by a User Equipment, UE, (702), the method comprising: receiving (706 or 708, 712), from a Radio Access Network, RAN, node (700), one or more signaling messages comprising either: (a) a combined select and query signaling message or (b) separate select and query signaling messages; and operating (714) in accordance with the one or more signaling messages.

[0277] Embodiment 2: The method of embodiment 1, wherein the one or more signaling messages comprise the combined select and query signaling message.

[0278] Embodiment 3: The method of embodiment 2, wherein the combined select and query signaling message comprises both select signaling information and query signaling information.

[0279] Embodiment 4: The method of embodiment 2, wherein the combined select and query signaling message comprises an indication that it comprises both select signaling information and query signaling information.

[0280] Embodiment 5: The method of embodiment 4, wherein receiving (706) the one or more signaling messages comprises determining that the one or more received signaling messages is the combined select and query signaling message based on the indication.

[0281] Embodiment 6: The method of embodiment 2, wherein the combined select and query signaling message has a different message format than separate select and query signaling messages.

[0282] Embodiment 7: The method of embodiment 6, wherein receiving (706) the one or more signaling messages comprises blindly decoding the one or more signaling messages using different message formats comprising a first message format for combined select and query signaling messages and a second message format for separate select and query messages.

[0283] Embodiment 8: The method of embodiment 1, wherein the one or more signaling messages comprise the separate select and query signaling messages.

[0284] Embodiment 9: The method of embodiment 8, wherein the select signaling message comprises select signaling information and the query signaling message comprises query signaling information.

[0285] Embodiment 10: The method of embodiment 3 or 9, wherein the select signaling information comprises any one or more of the following: device ID, list of device IDs, device group ID, list of group IDs, indication to address all devices, setting of flag(s) relevant to inventory, selection cause or criteria or establishment cause, PLMN ID or network ID, mapping of device or device group information or IDs to a local device or device group index, mapping of PLMN ID to a local PLMN index, information about (e.g., an indication (e.g., value) of) a time gap between the select signaling message and the query signaling message in the case of separate select and query signaling messages, information that indicates a maximum time gap between the separate select and query signaling messages, indication of more select signaling message(s) followed by this select signaling, reader ID, short-term procedure ID / index, indication of single ID and that the random access is contention-free.

[0286] Embodiment 11: The method of embodiment 3 or 9 or 10, wherein the query signaling information comprises any one or more of the following: an indication of a number of slots / frames / sub-slots allocated for random access, an indication of a time gap between receipt of the query signaling information and the first / zeroth slot / frame / subslot which can be first opportunity to do uplink access, a parameter indicating some maximum value or set of values in the query signaling information and upon receiving this message, the UE can select some value based on this parameter to be used as device ID or temporary ID, Frequency Division Multiplexing (FDM) / Frequency Division Multiple Access (FDMA) resource / allowable frequency shift, alternatively expressed as the allowed data rates which the device can consider random selection over for the random access, reader ID (e.g., ID of the gNB in Topology 1 and ID of the intermediate UE in Topology 2), device or device group ID(s) or local device or device group index(s), short-term procedure ID / index for identification of which select signaling information or select signaling message this query signaling information belongs to.

[0287] Embodiment 12: The method of embodiment 3 or 9 or 10 or 11, wherein the query signaling targets one or more specific UEs and contains one or more flags relevant to inventory, and the UE ignores the one or more flags relevant to inventory.

[0288] Embodiment 13: The method of any of embodiments 1 to 12, wherein the RAN node is a network node (e.g., a base station).

[0289] Embodiment 14: The method of any of embodiments 1 to 12, wherein the RAN node is an intermediate UE.

[0290] Embodiment 15: The method of any of embodiments 1 to 14, wherein the one or more signaling messages are carried via a MAC CE(s) or a control PDU(s).

[0291] Embodiment 16: The method of any of embodiments 1 to 15, wherein one or more timer flags are used to indicate whether the one or more signaling messages is a combined select and query signaling message or are separate select and query signaling messages.

[0292] Embodiment 17: The method of any of embodiments 1 to 16, wherein the UE (702) is an Ambient Internet of Things, A-IoT, UE.

[0293] Group B Embodiments

[0294] Embodiment 18: A method performed by a RAN node (700), the method comprising: transmitting (706 or 708, 712), to a User Equipment, UE, (702), one or more signaling messages comprising either: (a) a combined select and query signaling message or (b) separate select and query signaling messages.

[0295] Embodiment 19: The method of embodiment 18, further comprising determining (704) whether to transmit a combined select and query signaling message or separate select and query signaling messages based on one or more network conditions.

[0296] Embodiment 20: The method of embodiment 19, wherein transmitting (706 or 708, 712) the one or more signaling messages comprises: transmitting (706) the combined select and query signaling message if a result of the determining (704, YES) is to transmit the combined select and query signaling message; and transmitting (708, 712) the separate select and query signaling messages if the result of the determining (704, YES) is to transmit the separate select and query signaling messages.

[0297] Embodiment 21: The method of embodiment 19 or 20, wherein the one or more network conditions comprises any one or more of the following: load in a cell operated by or otherwise associated to the RAN node (e.g., serving cell of the UE); one or more capabilities of the UE or an associated group of UEs; a device type of the UE or a device type of each of an associated group of UEs.

[0298] Embodiment 22: The method of any of embodiments 18 to 21, wherein the one or more signaling messages comprise the combined select and query signaling message.

[0299] Embodiment 23 : The method of embodiment 22, wherein the combined select and query signaling message comprises both select signaling information and query signaling information.

[0300] Embodiment 24: The method of embodiment 22, wherein the combined select and query signaling message comprises an indication that it comprises both select signaling information and query signaling information.

[0301] Embodiment 25: The method of embodiment 22, wherein the combined select and query signaling message has a different message format than separate select and query signaling messages.

[0302] Embodiment 26: The method of any of embodiments 18 to 21, wherein the one or more signaling messages comprise the separate select and query signaling messages.

[0303] Embodiment 27: The method of embodiment 26, wherein the select signaling message comprises select signaling information and the query signaling message comprises query signaling information.

[0304] Embodiment 28: The method of embodiment 23 or 27, wherein the select signaling information comprises any one or more of the following: device ID, list of device IDs, device group ID, list of group IDs, indication to address all devices, setting of flag(s) relevant to inventory, selection cause or criteria or establishment cause, PLMN ID or network ID, mapping of device or device group information or IDs to a local device or device group index, mapping of PLMN ID to a local PLMN index, information about (e.g., an indication (e.g., value) of) a time gap between the select signaling message and the query signaling message in the case of separate select and query signaling messages, information that indicates a maximum time gap between the separate select and query signaling messages, indication of more select signaling message(s) followed by this select signaling, reader ID, short-term procedure ID / index, indication of single ID and that the random access is contention-free.

[0305] Embodiment 29: The method of embodiment 23 or 27 or 28, wherein the query signaling information comprises any one or more of the following: an indication of a number of slots / frames / sub-slots allocated for random access, an indication of a time gap between receipt of the query signaling information and the first / zeroth slot / frame / subslot which can be first opportunity to do uplink access, a parameter indicating some maximum value or set of values in the query signaling information and upon receiving this message, the UE can select some value based on this parameter to be used as device ID or temporary ID, Frequency Division Multiplexing (FDM) / Frequency Division Multiple Access (FDMA) resource / allowable frequency shift, alternatively expressed as the allowed data rates which the device can consider random selection over for the random access, reader ID (e.g., ID of the gNB in Topology 1 and ID of the intermediate UE in Topology 2), device or device group ID(s) or local device or device group index(s), short-term procedure ID / index for identification of which select signaling information or select signaling message this query signaling information belongs to.

[0306] Embodiment 30: The method of embodiment 23 or 27 or 28 or 29, wherein the query signaling targets one or more specific UEs and contains one or more flags relevant to inventory, and the UE ignores the one or more flags relevant to inventory.

[0307] Embodiment 31: The method of any of embodiments 18 to 30, wherein the one or more signaling messages are carried via a MAC CE(s) or a control PDU(s).

[0308] Embodiment 32: The method of any of embodiments 18 to 31, wherein one or more timer flags are used to indicate whether the one or more signaling messages is a combined select and query signaling message or are separate select and query signaling messages.

[0309] Embodiment 33: The method of any of embodiments 18 to 32, wherein the UE (702) is an Ambient Internet of Things, A-IoT, UE.

[0310] Embodiment 34: The method of any of embodiments 18 to 33, wherein the RAN node is an intermediate UE.

[0311] Embodiment 35: The method of any of embodiments 18 to 33, wherein the RAN node is a network node (e.g., a base station).

[0312] Group C Embodiments

[0313] Embodiment 36: A user equipment comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0314] Embodiment 37: A RAN node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.

[0315] Embodiment 38: A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

Claims

CLAIMS1. A method performed by a User Equipment, UE, (702), the method comprising: receiving (706 or 708, 712), from a Radio Access Network, RAN, node (700), one or more signaling messages comprising either: (a) a combined select and query signaling message or (b) separate select and query signaling messages; and operating (714) in accordance with the one or more signaling messages.

2. The method of claim 1, wherein whether the one or more signaling messages comprise a combined select and query signaling message or separate select and query signaling messages depends on any one or more of the following: one or more cell conditions, one or more network conditions, one or more device capabilities of the UE or group of UEs by which the one or more signaling messages are received, and one or more charging requirements.

3. The method of claim 1, wherein whether the one or more signaling messages comprise a combined select and query signaling message or separate select and query signaling messages depends on any one or more of the following:• load in a cell on which the one or more signaling messages are received by the UE (702);• one or more device capabilities of the UE or group of UEs to which the one or more signaling messages are transmitted by the RAN node (700);• a device type of the UE or a group of UEs to which the one or more signaling messages are transmitted by the RAN node (700);• a use case cause of an operation to which the one or more signaling messages are related.

4. The method of any of claims 1 to 3, wherein the one or more signaling messages comprise the combined select and query signaling message.

5. The method of claim 4, wherein the combined select and query signaling message comprises both select signaling information and query signaling information.

6. The method of claim 4, wherein the combined select and query signaling message comprises an indication that the combined select and query signaling message comprises both select signaling information and query signaling information.

7. The method of claim 6, wherein receiving (706) the one or more signaling messagescomprises determining that the one or more received signaling messages is the combined select and query signaling message based on the indication.

8. The method of claim 4, wherein the combined select and query signaling message has a different message format than separate select and query signaling messages.

9. The method of claim 8, wherein receiving (706) the one or more signaling messages comprises blindly decoding the one or more signaling messages using different message formats comprising a first message format for combined select and query signaling messages and a second message format for separate select and query messages.

10. The method of any of claims 1 to 3, wherein the one or more signaling messages comprise the separate select and query signaling messages.

11. The method of claim 10, wherein the select signaling message comprises select signaling information and the query signaling message comprises query signaling information.

12. The method of claim 5 or 11, wherein the select signaling information comprises any one or more of the following:• device identity, ID;• list of device IDs;• device group ID;• list of group IDs;• indication to address all devices;• setting of one or more flags relevant to inventory;• selection cause or criteria or establishment cause;• Public Land Mobile Network, PLMN, ID or network ID;• mapping of device or device group information or IDs to a local device or device group index;• mapping of PLMN ID to a local PLMN index;• information about a time gap between the select signaling message and the query signaling message in the case of separate select and query signaling messages;• information that indicates a maximum time gap between the separate select and query signaling messages;• indication of one or more additional select signaling messages followed by this select signaling;• reader ID;• short-term procedure ID or index;• indication of single ID and that the random access is contention-free.

13. The method of claim 5 or 11 or 12, wherein the query signaling information comprises any one or more of the following:• an indication of a number of slots, frames, or sub-slots allocated for random access;• an indication of a time gap between receipt of the query signaling information and the first / zeroth slot / frame / subslot which can be first opportunity to do uplink access;• a parameter indicating some maximum value or set of values in the query signaling information and upon receiving this message, the UE can select some value based on this parameter to be used as device ID or temporary ID;• Frequency Division Multiplexing, FDM, or Frequency Division Multiple Access, FDMA, resource or allowable frequency shift, alternatively expressed as the allowed data rates which the device can consider random selection over for the random access;• reader ID;• one or more device IDs, one or more device group IDs, or one or more local device indices, or one or more device group indices;• short-term procedure ID or index for identification of a select signaling information or select signaling message to which this query signaling information belongs.

14. The method of claim 5 or 11 or 12 or 13, wherein the query signaling targets one or more specific UEs and contains one or more flags relevant to inventory, and the UE ignores the one or more flags relevant to inventory.

15. The method of any of claims 1 to 14, wherein the RAN node is a network.

16. The method of any of claims 1 to 14, wherein the RAN node is an intermediate UE.

17. The method of any of claims 1 to 16, wherein the one or more signaling messages are carried via one or more Medium Access Control, MAC, Control Elements, CEs, or one or more control Protocol Data Units, PDUs.

18. The method of any of claims 1 to 17, wherein one or more timer flags are used to indicate whether the one or more signaling messages is a combined select and query signaling message or are separate select and query signaling messages.

19. The method of any of claims 1 to 18, wherein the UE (702) is an Ambient Internet of Things, A-IoT, UE.

20. A User Equipment, UE, (702) adapted to: receive (706 or 708, 712), from a Radio Access Network, RAN, node (700), one or more signaling messages comprising either: (a) a combined select and query signaling message or (b) separate select and query signaling messages; and operate (714) in accordance with the one or more signaling messages.

21. The UE (702) of claim 20, further adapted to perform the method of any of claims 2 to 19.

22. A User Equipment, UE, (702; 1100) comprising: a communication interface (1112) comprising a receiver (1120); and processing circuitry (1102) associated with the communication interface (1112), the processing circuitry (1102) configured to cause the UE (702; 1100) to: receive (706 or 708, 712), from a Radio Access Network, RAN, node (700), one or more signaling messages comprising either: (a) a combined select and query signaling message or (b) separate select and query signaling messages; and operate (714) in accordance with the one or more signaling messages.

23. The UE (702) of claim 22, wherein the processing circuitry (1102) is further configured to cause the UE (702; 1100) to perform the method of any of claims 2 to 19.

24. A method performed by a Radio Access Network, RAN, node (700), the method comprising: transmitting (706 or 708, 712), to a User Equipment, UE, (702), one or more signaling messages comprising either: (a) a combined select and query signaling message or (b) separate select and query signaling messages.

25. The method of claim 24, further comprising determining (704) whether to transmit a combined select and query signaling message or separate select and query signaling messages based on one or more cell conditions, one or more network conditions, one or more device capabilities of the UE or a group of UEs, and / or one or more charging requirements.

26. The method of claim 24, further comprising determining (704) whether to transmit a combined select and query signaling message or separate select and query signaling messages based on any one or more of the following:• load in a cell on which the one or more signaling messages are transmitted;• one or more device capabilities of the UE or group of UEs to which the one or more signaling messages are transmitted by the RAN node (700);• a device type of the UE or a group of UEs to which the one or more signaling messages are transmitted by the RAN node (700);• a use case cause of an operation to which the one or more signaling messages are related.

27. The method of claim 25 or 26, wherein transmitting (706 or 708, 712) the one or more signaling messages comprises: transmitting (706) the combined select and query signaling message if a result of the determining (704, YES) is to transmit the combined select and query signaling message; and transmitting (708, 712) the separate select and query signaling messages if the result of the determining (704, NO) is to transmit the separate select and query signaling messages.

28. The method of any of claims 24 to 27, wherein the one or more signaling messages comprise the combined select and query signaling message.

29. The method of claim 28, wherein the combined select and query signaling message comprises both select signaling information and query signaling information.

30. The method of claim 28, wherein the combined select and query signaling message comprises an indication that the combined select and query signaling message comprises both select signaling information and query signaling information.

31. The method of claim 28, wherein the combined select and query signaling message has a different message format than separate select and query signaling messages.

32. The method of any of claims 24 to 31, wherein the one or more signaling messages comprise the separate select and query signaling messages.

33. The method of claim 32, wherein the select signaling message comprises select signaling information and the query signaling message comprises query signaling information.

34. The method of claim 29 or 33, wherein the select signaling information comprises any one or more of the following:• device identity, ID;• list of device IDs;• device group ID;• list of group IDs;• indication to address all devices;• setting of one or more flags relevant to inventory;• selection cause or criteria or establishment cause;• Public Land Mobile Network, PLMN, ID or network ID;• mapping of device or device group information or IDs to a local device or device group index;• mapping of PLMN ID to a local PLMN index;• information about a time gap between the select signaling message and the query signaling message in the case of separate select and query signaling messages;• information that indicates a maximum time gap between the separate select and query signaling messages;• indication of one or more additional select signaling messages followed by this select signaling;• reader ID;• short-term procedure ID / index;• indication of single ID and that the random access is contention-free.

35. The method of claim 29 or 33 or 34, wherein the query signaling information comprises any one or more of the following:• an indication of a number of slots, frames, or sub-slots allocated for random access;• an indication of a time gap between receipt of the query signaling information and the first or zeroth slot, frame, or subslot which can be first opportunity to do uplink access;• a parameter indicating some maximum value or set of values in the query signaling information and upon receiving this message, the UE can select some value based on this parameter to be used as device ID or temporary ID;• Frequency Division Multiplexing, FDM, or Frequency Division Multiple Access, FDMA, resource / allowable frequency shift, alternatively expressed as the allowed data rates which the device can consider random selection over for the random access;• reader ID;• one or more device IDs, one or more device group IDs, one or more local device indices, or one or more device group indices;• short-term procedure ID or index for identification of which select signaling information or select signaling message this query signaling information belongs to.

36. The method of claim 29 or 33 or 34 or 35, wherein the query signaling targets one or more specific UEs and contains one or more flags relevant to inventory, and the UE ignores the one or more flags relevant to inventory.

37. The method of any of claims 24 to 36, wherein the one or more signaling messages are carried via one or more Medium Access Control, MAC, Control Elements, CEs, or one or more control Protocol Data Units, PDUs.

38. The method of any of claims 24 to 37, wherein one or more timer flags are used to indicate whether the one or more signaling messages is a combined select and query signaling message or are separate select and query signaling messages.

39. The method of any of claims 24 to 38, wherein the UE (702) is an Ambient Internet of Things, A-IoT, UE.

40. The method of any of claims 24 to 39, wherein the RAN node is an intermediate UE.

41. The method of any of claims 24 to 39, wherein the RAN node is a network node.

42. A Radio Access Network, RAN, node (700) adapted to:transmit (706 or 708, 712), to a User Equipment, UE, (702), one or more signaling messages comprising either: (a) a combined select and query signaling message or (b) separate select and query signaling messages.

43. The RAN node (700) of claim 42, further adapted to perform the method of any of claims 25 to 41.

44. A Radio Access Network, RAN, node (700; 1100; 1200) comprising: a communication interface (1112; 1206); and processing circuitry (1102; 1202) associated with the communication interface (1112; 1206), the processing circuitry (1102; 1202) configured to cause the RAN node (700; 1100; 1200) to transmit (706 or 708, 712), to a User Equipment, UE, (702), one or more signaling messages comprising either: (a) a combined select and query signaling message or (b) separate select and query signaling messages.

45. The RAN node (700; 1100; 1200) of claim 44, wherein the processing circuitry (1102; 1202) is further configured to cause the RAN node (700; 100; 1200) to perform the method of any of claims 25 to 41.

Images