Mechanism for ambient IoT reader selection in a mixed type of aiot readers and multi-operation-areas environment

Abstract

The disclosure provides methods, apparatuses, entities, and computer program products for ambient reader selection. A first network function entity receives first AIoT reader selection information associated with an AIoT service, receives a first message including a request for the AIoT service, selects a second network function entity that serves one or more AIoT readers, determines second AIoT reader selection information in accordance with the first AIoT reader selection information and the second network function entity, and sends a second message to the second network function entity, the second message including information of the request for the AIoT service and the second AIoT reader selection information, and is for the second network function entity selecting AIoT readers.

Description

MECHANISM FOR AMBIENT loT READER SELECTION IN A MIXED TYPE OF AIoT READERS AND MULTIOPERATION-AREAS ENVIRONMENTPRIORITY CLAIM AND CROSS-REFERENCE

[0001] This patent application claims priority to U.S. Provisional Application No.63 / 675,631 filed on July 25, 2024 and entitled “NEW MECHANISM FOR AMBIENT loT READER SELECTION IN A MIXED TYPE OF AIoT READERS AND MULTI- OPERATION-AREAS ENVIRONMENT,” which is hereby incorporated by reference herein as if reproduced in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates generally to reader selection, and in particular embodiments, to techniques and mechanisms for ambient Internet of Things (loT) reader selection of mixed types and / or in multi-operation area environments.BACKGROUND

[0003] loT readers may be utilized in different contexts. Several implementations do not contemplate more practical deployments in which different types of AIoT readers coexist in the same coverage area or different coverage areas for one or more single AIoT services. Most approaches propose to select an AIoT reader only by the serving area, but in view of the complexity of an actual AIoT deployment, these considerations are not enough. Revisiting implementations for such AIoT reader selection is thus desired.SUMMARY OF THE DISCLOSURE

[0004] Technical advantages are generally achieved, by embodiments of this disclosure which describe ambient loT (AIoT) reader selection of mixed types and / or in multi-operation area environments.

[0005] In accordance with a first aspect of the disclosure, an example method is provided. The method may be a method for AIoT reader selection performed by a first network function entity. An example method includes managing, by a first network function entity, two or more ambient Internet of Things (AIoT) readers within at least one service area with a first group of AIoT devices. The example method further includes receiving, by the first network function entity, first AIoT reader selection information associated with an AIoT service. The example method further includes receiving, by the first network function entity, a first message from an AIoT application, the first message including information of a request for the AIoT service. The example method furtherincludes selecting, by the first network function entity, a second network function entity from one or more second network function entities, where the second network function entity serves one or more AIoT readers. The example method further includes determining, by the first network function entity, second AIoT reader selection information in accordance with the first AIoT reader selection information and the second network function entity. The example method further includes sending, by the first network function entity, a second message to the second network function entity, the second message comprising the information of the request for the AIoT service and the second AIoT reader selection information, w here the second AIoT reader selection information is for the second network function entity to select a set of AIoT readers from the one or more AIoT readers.

[0006] In some embodiments of the example method, the first message is from an AIoT service client, and the AIoT service client comprises an application function (AF) entity.

[0007] In some embodiments of the example method, an AIoT reader of two or more AIoT readers comprises an intermediate node, the intermediate node comprising a next generation NodeB (gNB) or a user equipment (UE).

[0008] In some embodiments of the example method, the first AIoT reader selection information indicates an AIoT reader selection policy that the first network function entity and the second network function entity uses during AIoT selection.

[0009] In some embodiments of the example method, the set of AIoT readers comprises at least one AIoT reader.

[0010] In some embodiments of the example method, the first network function entity includes an AIoT management function entity, and the second network function entity includes a mobile base station.[00111 In some embodiments of the example method, the selecting the second network function entity is based on information related to AIoT reader selection collected from a third network function entity, where the third network function entity comprises a network data analytic function (NWDAF) entity.

[0012] In some embodiments of the example method, the first network function entity selects one or more different types of AIoT readers for the AIoT service.

[0013] In some embodiments of the example method, the at least one service area includes a single service area.

[0014] In some embodiments of the example method, the at least one service area comprises a plurality of different service areas.

[0015] In some embodiments of the example method, the request for the AIoT sendee client includes the first AIoT reader selection information used in selecting the second network function entity.

[0016] In some embodiments of the example method, the first AIoT reader selection information associated w ith the AIoT sen ice is one of a plurality of AIoT reader selection policies.

[0017] In some embodiments of the example method, the first AIoT reader selection information includes one or more of: an indication that both intermediate node reader types and next generation NodeB (gNB) reader types within an overlapping AIoT reader coverage area are allowed; an indication that AIoT reader selection is to be decided by a gNB; a maximum number of AIoT readers allowed for the at least one service area or the AIoT sen ice; a prioritization policy between an intermediate node as a reader and the gNB as a reader when both types of readers are candidate readers within the at least one senice area; a gNB reader load condition; an energy criteria; a maximum number of sening AIoT devices per reader; a data-privacy-protection-based indication; a target AIoT device behavior or pattern target indication; a sensing based criteria; an AIoT device position-based selection criteria; a mobility status criteria of an intermediate node; or a prioritization for different criteria.

[0018] In some embodiments of the example method, the method further includes receiving, by the first network function entity from the set of AIoT readers, one or more responses to the request for the AIoT service, and sending, by the first network function entity, a third message to the AIoT application, the third message comprising the one or more responses.

[0019] In some embodiments of the example method, the first network function entity includes an AIoT management function (AloTF or AIoT MF).

[0020] In some embodiments of the example method, the second network function entity includes a next generation NodeB (gNB).

[0021] In accordance with another aspect of the present disclosure, another example method is provided. The method may be a method for AIoT reader selection performed by a second network function entity. The example method includes receiving, by a second network function entity, a first message from a first network function entity, the first message including information of a request for an ambient Internet of Things (AIoT) service and AIoT reader selection information associated with the AIoT service. The example method further includes selecting, by the second network function entity, a first set of AIoT readers based on the AIoT reader selection information. The example method further includes sending, by the second network function entity, a second message to each of the first set of AIoT readers selected, the second message including theinformation of the request for the AIoT service. In some embodiments of the example method, receiving, by the second network function entity from the first set of AIoT readers, one or more responses to the request for the AIoT service.

[0022] In some embodiments of the example method, the AIoT reader selection information includes an AIoT reader selection policy that the second network function entity uses to select first set of AIoT readers.

[0023] In some embodiments of the example method, the first network function entity includes an AIoT management function (AIoTF).

[0024] In some embodiments of the example method, the second network function entity includes a next generation NodeB (gNB).

[0025] In some embodiments of the example method, the one or more responses to the request for the AIoT service are received from the first set of AIoT readers by the second network function entity, and the one or more responses is forwarded to the first network function entity from the second network function entity.

[0026] In some embodiments of the example method, the AIoT reader selection information includes one or more of: a first ID associated with a service provider owning or using one or more AIoT devices, the first ID being shared among the first set of AIoT readers, a second ID identifying a group or a business association that the first set of AIoT readers belong to, a first indication indicating one or more preferred AIoT readers to be selected, or a second indication indicating a preference between a gNB type of readers and a user equipment (UE) type of readers.

[0027] In some embodiments of the example method, the AIoT reader selection information includes first AIoT reader selection information, and second AIoT reader selection information is based on the first AIoT reader selection information and includes at least a portion of the first AIoT reader selection information.

[0028] In some embodiments of the example method, the first network function entity receives AIoT reader selection assistant information from the second network function entity before sending the second message to the second network function entity, the AIoT reader selection assistant information including information utilized by the first network function entity to select the second network function entity for AIoT reader selection.

[0029] In some embodiments of the example method, the AIoT reader selection assistant information includes one or more IDs of AIoT readers or a type of reader, the type of reader including a gNB type of reader and a UE type of reader, for each of the AIoT readers wit hi n a serving area of the second network function entity.

[0030] In some embodiments of the example method, the first set of AIoT readers are within at least one service area, and the at least one service area includes a single sendee area.

[0031] In some embodiments of the example method, the first set of AIoT readers are within at least one service area, and the at least one service area includes a plurality of different serv ice areas.

[0032] In some embodiments of the example method, the AIoT reader selection information comprises criteria including one or more of: an indication that both intermediate node reader types and next generation NodeB (gNB) reader types within an overlapping AIoT reader service area are allowed; an indication that AIoT reader selection is to be decided by a gNB; a maximum number of AIoT readers allowed for the at least one service area or the AIoT serv ice; a prioritization policy between an intermediate node and a gNB as reader when both types of readers are candidate readers within the at least one service area; a gNB reader load condition; an energy criteria; a maximum number of serving AIoT devices per reader; a data-privacy-protection-based indication; a target AIoT device behavior or pattern target indication; a sensing based criteria; an AIoT device position-based selection criteria; a mobility status criteria of an intermediate node; or a prioritization for different criteria.

[0033] In accordance with a third aspect of the disclosure, another example method is provided. The example method may be a method for AIoT reader selection performed by a NWDAF. The example method includes receiving, at a network data analytics function (NWDAF) entity and from a first network function entity, first AIoT reader selection information associated with an AIoT service. The example method further includes collecting, by the NWDAF and based on the first AIoT reader selection information, information associated with the selection of a second network function entity. The example method further includes sending, by the NWDAF to the first network function entity, the information associated with the selection of the second network function entity.

[0034] In accordance with another aspect of the disclosure, an example network function entity is provided. The example network function entity may be a device or apparatus, or the like. The example network function entity includes at least one processor and at least one non-transitory computer readable storage medium. The at least one non-transitory computer readable storage medium stores programming, the programming including instructions that, when executed by the at least one processor, cause the network function entity to perform a method according to any one of the example methods described herein.

[0035] In accordance with another aspect of the disclosure, an example non- transitory computer readable storage medium is provided. The non-transitoiy computer readable storage medium includes instructions stored thereon that, when executed by at least one processor, cause the non-transitory’ computer readable storage medium to perform a method according to any one of the example methods described herein.BRIEF DESCRIPTION OF THE DRAWINGS

[0036] For a more complete understanding of the present disclosure, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

[0037] FIG. 1 illustrates an example topology in accordance with at least one embodiment of the present disclosure;

[0038] FIG. 2 illustrates another example topology in accordance with at least one embodiment of the present disclosure;

[0039] FIG. 3 illustrates an example of mixed topologies and multi-area AIoT operation in accordance with at least one example embodiment of the present disclosure;

[0040] FIG. 4 illustrates an example system architecture based on a sendee area in accordance with at least one example embodiment of the present disclosure;

[0041] FIG. 5 illustrates an example of a hierarchical AIoT reader selection policy in accordance with at least one example embodiment of the present disclosure;

[0042] FIGs. 6A-6B illustrate an example diagram of operations in AIoT reader selection in accordance with at least one example embodiment of the present disclosure;

[0043] FIGs. 7A-7B illustrate an example diagram of operations in AIoT reader selection in accordance with at least one example embodiment of the present disclosure;

[0044] FIGs. 8A-8B illustrate an example diagram of operations in a mixed AIoT reader status update for AIoT reader replacement in accordance with at least one example embodiment of the present disclosure;

[0045] FIG. 9 illustrates an example flow’ diagram depicting operations of an example process in accordance with at least one embodiment of the present disclosure;

[0046] FIG. 10 illustrates an example communications system in accordance with at least one embodiment of the present disclosure;

[0047] FIG. 11 illustrates another example communication system in accordance with at least one embodiment of the present disclosure;

[0048] FIG. 12A illustrates an example edge device in accordance with at least one embodiment of the present disclosure;

[0049] FIG. 12B illustrates an example base station in accordance with at least one embodiment of the present disclosure;

[0050] FIG. 13 illustrates a block diagram of an example computing system in accordance w ith at least one embodiment of the present disclosure;

[0051] FIG. 14 illustrates a flowchart depicting example operations for AIoT reader selection by a first network function entity in accordance with at least one embodiment of the present disclosure;

[0052] FIG. 15 illustrates a flowchart depicting example operations for AIoT reader selection by a second network function entity in accordance w ith at least one embodiment of the present disclosure; and

[0053] FIG. 16 illustrates a flowchart depicting example operations for information management associated with AIoT reader selection in accordance with at least one embodiment of the present disclosure.

[0054] Corresponding numerals and symbols in the different figures generally refer to corresponding parts unless otherwise indicated. The figures are drawn to clearly illustrate the relevant aspects of the embodiments and are not necessarily drawn to scale.DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

[0055] The making and using of embodiments of this disclosure are discussed in detail below. It should be appreciated, however, that the concepts disclosed herein can be embodied in a wide variety of specific contexts, and that the specific embodiments discussed herein are merely illustrative and do not serve to limit the scope of the claims. Further, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of this disclosure as defined by the appended claims.In several contexts, supporting 5G Ambient loT is desired. Two types of topologies for Ambient loT are identified, for example as depicted in FIG. 1 (depicting an example Topology 1) and FIG. 2 (depicting an example Topology 2) respectively. In Topology 1, an ambient loT device 104 communicates with a base station 102. In Topology 2, an ambient loT device 204 communicates through an intermediate node 206 with the base station 202, where the base station 202 and the intermediate node 206 communicate via a Uu link. For topology 2, the intermediate node may be a UE under network control, or in some embodiments may be another type of device.

[0056] These topologies aim to develop 5G core network architecture to sufficiently support Ambient loT. One assumption may be that one mobile network can support both topologies for an AIoT service, implying that there can be two different types of AIoT readers (e.g., a next-Generation Node-B (gNB) as reader and user equipment (UE) as reader) being used for a single AIoT service. In an example of one AIoT service, a gNB reader first performs an inventoiy to identify AIoT devices with certain characteristics. An AIoT is an ambient -powered loT device, which in some embodiments includes an loT device powered by energy harvesting, being either battery-less or with limited energy storage capability (e.g., using a capacitor). After the AIoT devices are identified, an intermediate node reader (for example) performs commands on those AIoT devices. In another example, both the gNB reader and one or more intermediate node readers operate concurrently (e.g., by transmitting and receiving at the same time) or even coordinating to manage interference, for instance.

[0057] Embodiments of the present disclosure are provided to support several advancements in 5G systems supporting AIoT reader selection. Such advancements include supporting different types of AIoT readers coexisting in the same coverage area or different coverage areas for a single AIoT service. One such example of mixed topologies and multi-area AIoT operation as shown in Error! Reference source not found., discussed further herein.

[0058] Additionally or alternatively, some embodiments additionally advantageously address that not all the AIoT readers can be used for certain AIoT operations. For example, some AIoT operation require specific types of AIoT readers (e.g., AIoT inventory operation and AIoT command operation may require two types of AIoT readers with different capabilities).

[0059] Additionally or alternatively, some embodiments additionally advantageously address privacy protection, which involves some association between AIoT reader and AIoT devices to protect the data from the AIoT devices.

[0060] Additionally or alternatively, some embodiments additionally advantageously address network and UE load conditions that can restrict some AIoT readers from being used. Additionally or alternatively, some embodiments, advantageously address energy consumption, especially when considering that a UE reader’s battery status can impact its AIoT operation.

[0061] Additionally or alternatively, some embodiments additionally advantageously address identified deficiencies in implementations where there is no information collection mechanism, such as AIoT reader status monitoring, information associated with AIoT capability and association with the AIoT devices, to be used for AIoT reader selection. Some such embodiments additionally or alternatively advantageously address that there is no mechanism to monitor the AIoT reader status and change the AIoT reader for the AIoT service according to the status of one or more AIoT readers during the AIoT service time.

[0062] FIG. 3 depicts an AIoT management function having a logical connection to readers in three different areas. A logical connection may, in some implementations, be different than a physical connection. In some embodiments, one or more portions of the areas may overlap. In Area 308C, which can correspond to Topology 1 in Error! Reference source not found, for example, the gNB is a reader (gNB reader) 310B serving two devices (e.g., AIoT device 312.1 and 312.2). In Area 308B, which can correspond to Topology 2 in Error! Reference source not found, for example, there is one reader (e.g., UE reader 314). A gNB 310C manages a Uu link to UE reader 314. An AIoT management function 302, which is connected to a NEF 304 that is further connected to an AF 306, can logically manage AIoT functionality of UE reader 314 via the Uu link. The Area 308B further includes several AIoT devices, including AIoT device 312.3, AIoT device 312.9, and AIoT device 312.4. In Area 308A, there are three readers, specifically a gNB 310A, UE reader 316.1, and UE reader 316.2. In some such embodiments, the gNB 310A manages Uu links to UE reader 316.1 and UE reader 316.2. The Area 308A furtherincludes a plurality of AIoT devices, for example AIoT device 312.5, AIoT device 312.6, AIoT device 312.7, and AIoT device 312.8. Each AIoT reader may be within the listed area as a service area, the at least one service area associated with serving the service to the AIoT devices within that service area.

[0063] Approaches on area-based selection only generally consider a single location for the AIoT service, and do not consider that one service may cover multiple locations. Specifically, such approaches often only consider a single service area, not two or more service areas. Such approaches may consider the gNB’s loading status, energy consumption for gNB reader selection; however in reality a gNB maybe overloaded with other traffic and cannot handle more AIoT services involving large number of AIoT devices. To ensure sufficient performance for Ambient loT devices, a gNB may use time division multiplexing (TDM), where for one portion of time it serves cellular devices and another portion of time it serves Ambient loT devices. This TDM, however, can cause overloading at the gNB when cellular service traffic increases significantly. Alternatively, a gNB reader may be used w’hen most of AIoT devices are in the proximity to save gNB transmission power.

[0064] In some implementations, a UE as an intermediate node requires the consensus from the user and matches its subscription because the UE is not only for AIoT services but also used for other purposes for the user. No current approach considers this subscription status.

[0065] Most of the AIoT services may not have one-time transactions. Often, those AIoT services may be associated with a service time, meaning that the AIoT readers that participate in the service may be changed during the service time (such as when a UE reader moves out of the area). Some approaches focus on the initial selection of AIoT reader, but existing approaches do not consider dynamic AIoT reader selection and replacement during one AIoT service time. The dy namic selection can be based on the latest condition and status for a reader (e.g., the reader’s local condition, UE reader mobility (for example, if UE is moving out / in the area), and the like).

[0066] Some proposed approaches allow an application function (AF) to select the intermediate node reader, but those approaches lack network exposure function (NEF) exposure to provide AF UE reader status and information to help the AF to make an appropriate selection based on the latest information. Certain of the proposed approaches assume the selection made by the AF at the beginning of the AIoT service applies for the duration of the service.

[0067] Certain of the proposed approaches suggest that the AF (e.g., an AIoTF or AIoTF) selects the reader. For the gNB reader and intermediate Node co-existence deployment however (e.g., Area 308A in Error! Reference source not found.), there can be interference between those two types of readers. In some contexts, it may be preferable that the reader selection be performed in the gNB instead of the AIoTF or AF, because the gNB has better knowledge of its radio condition and the radio configuration for the AIoT operations. Embodiments of the present disclosure provide improvements in some or all of the above-mentioned aspects over alternative implementations.

[0068] Embodiments describe mechanisms for AIoT reader selection, specifically to select one or more AIoT readers for one or a group of AIoT devices, to execute an AIoT service / operation which may require multiple Al oT-service-delivery-topologies being deployed across multiple service areas. An example mechanism includes multilevel reader selection policies with additional selection criteria. Additional mechanisms in some embodiments include information feedback mechanism for the decision-making function to make selection decisions.

[0069] FIG. 4 depicts a system architecture based on a service area, for example the service area in Error! Reference source not found.. The system architecture is of a network 402, which includes an AIoT MF (or AIoTF) 418, connected to an AMF 408, a NWDAF 410, a UDM 412, and NEF 414. The NEF 414 is further connected to an AF 416, for example an AIoT sendee. The AMF 408 is connected to several gNBs, specifically gNB 404C and gNB 404B. The network 402 further includes gNB 404A. The gNB 404C is communicable with an intermediate node 420C, for example a UE (UE3). The intermediate node 420C is communicable with each of an AIoT device 422C, AIoT device 422D, and AIoT device 422I, embodying AIoT devices 3, 4, and 9 respectively. The gNB 404B includes or embodies an AIoT reader 406B. The gNB 404B (for example, via the AIoT reader 406B) is communicable with each of AIoT device 422A and AIoT device 422B respectively and directly, for example embodying devices AIoT devices 1 and 2. The gNB 404A similarly includes or embodies an AIoT reader 406A. The gNB 404A (for example, via the AIoT reader 406A) is communicable with each of an intermediate node 420A and intermediate node 420B, for example embodying a UE 1 and a UE 2. In other embodiments, one or more of the intermediate nodes may be embodied by a different type of device. The intermediate node 420A is communicable with each of the AIoT device 422E and AIoT device 422F, for example embodying AIoT devices 5 and 6.The intermediate node 420B is communicable with each of the AIoT device 422G andAIoT device 422H, for example embodying AIoT devices 7 and 8. To simplify the diagram, other links between the AIoT reader in gNB 404A to AIoT devices 422E, 422F, 422G, and 422H are not illustrated.

[0070] Some possible selection criteria, which can be used to select the preferred AIoT reader(s), include one or more of the following:

[0071] 1. An indication if mixed types of AIoT readers (e.g., an intermediate Node and gNB reader) for one AIoT service or operation is allowed. This indication can be provided from the AF to the AIoT management functions, or from the AIoT management function to the gNB. For the latter case, the gNB can conduct an AIoT reader selection within its coverage to meet the network operator’s location policy.

[0072] 2. An indication if using both intermediate node and gNB reader for one or a group of AIoT device(s) within one overlapping AIoT reader coverage area is allowed. This indicator indicates that an AIoT device may receive the same AIoT operation command and / or request from both an intermediate node and gNB reader. This can happen, for example, when the AIoT device is moving, and using both gNB reader and intermediate node can increase the reachability of the AIoT device. In some embodiments, to address potential radio interference issues while using both types of reader, this indication and its relevant policy may be configured by the operation and administration management (0AM) or other operator’s network management system.

[0073] 3. An indication of AIoT reader selection to be decided by gNB. This indication in some embodiments can be configured and provisioned in the AIoTF by the 0AM for certain areas. With this indication, the AIoTF selects a gNB based on the gNB selection policy associated w ith this indication, and the selected gNB further conducts the final reader selection (for example, either selecting this gNB as reader, or selecting other gNB readers, which is coordinated by this gNB for AIoT operation, or selecting the intermediate Nodes within the coverage of this gNB). This indication can be sent to the AIoTF from the 0AM or sent to the gNB from the AIoTF. For the former case, in some embodiments the AIoTF sends the reader selection to policy to the selected gNB for final reader selection. For the latter case, in some embodiments if the gNB receives this indication or the AIoT service request without the AIoT reader ID, the gNB selects the AIoT reader based on the received AIoT reader policy. In the AIoT reader selection policy to gNB, in some embodiments it also contains the other candidate gNB(s) to make the selection decision, in case the first selected gNB can’t find the reader according to the policy and the first selected gNB can forw ard the AIoT reader selection request to the candidate gNB(s). Compared to the gNB’sexisting capability of selecting a relay UE, selecting a UE AIoT reader is different functionality, because the Relay UE and AIoT reader UE are different type of UE. From the serving UE point of view, in some such contexts, the Relay UE node is not its service end point but a data route point to the end, but for an AIoT device, the AIoT reader UE is the service end point. Also, in such contexts, from gNB point of view, the relay UE is a communication routing point for the UE data, but the AIoT reader UE is not only a communication routing point but also a service point to serve AIoT device directly.

[0074] 4. A maximum number of AIoT readers being allowed for one area or oneAIoT service. In some embodiments, this is further defined with different granularities, such as maximum number of intermediate nodes served by one gNB or within one area or per AIoT service operation. This indication in some embodiments is used for energy efficiency consideration or load control.

[0075] 5. A prioritization policy between intermediate node and gNB as a reader when both two types of readers are candidate readers within one area. In some embodiments, this prioritization policy indicates which type of reader is preferred when both are present in the serving area. In some embodiments there can be conditions associated with the preference, such as location, time, type of AIoT operations (such as inventory, command), the number of AIoT devices and the capabilities of the AIoT devices being involved, and / or load condition of candidate intermediate node and gNB readers.

[0076] 6. A gNB reader load condition. In some embodiments, selection priority can be based on the gNB reader’s load condition, including the general load status or the AIoT traffic load status. This may also include a load threshold for the gNB to be selected as reader.

[0077] 7. An energy criteria. In some embodiments, this is used for intermediateNode selection (such as UE), such as selecting intermediate Node with more batterypower, or the minimum threshold of battery- status of the intermediate node to be considered as a candidate reader. This energy criteria also in some embodiments is used by gNB when energy efficiency and saving are considered for the AIoT operation when gNB conducts intermediate Node selection.

[0078] 8. A maximum number of serving AIoT devices allowed per reader (such as per intermediate Node). In some embodiments, this is used for reliability purposes to avoid one reader being responsible for too many Ambient loT devices.

[0079] 9- A data-privacy-protection-based selection, for example using Business association-based selection. Selecting the intermediate Node (UE), which may have relevant relationship w ith the target AIoT devices, for example AIoT readers sharing the same AIoT Service provider (SP) identifier (ID) who own or use the AIoT devices, or AIoT reader belonging to the same group or business association (e.g. share the same group ID). In some embodiments, this prevent AIoT device data being shared with other AIoT readers which has no business association with the AIoT device.

[0080] to. A target AIoT device behavior or pattern, for example if the AIoT device is moving or in fixed location. In some embodiments, if the target AIoT devices can be associated with moving objects, such as goods in the truck, gNB reader may be preferred and more than one gNB reader may be selected (such as multiple adjacent gNBs readers will be selected) for better coverage. In some embodiments, the behavior information is provided by AF via NEF interface, or from a network data analytic function (NWDAF), or be collected via AIoT device and service subscription information in the network.

[0081] 11. A sensing based criteria or AIoT device position-based selection. In some services, an AIoT device is attached to an object, such as an animal. In some embodiments, when sensing technologies are used to detect and position the object, the information from sensing allows the system to know the position of the AIoT device. This utilizes interaction with certain sensing function to detect target objects, which are integrated with AIoT device and based on the collected sensing information to make selection decision, for example selecting the reader which is closer to the serving AIoT devices for better coverage and quality. The sensing information in some embodiments is collected from mobile based ISAC or other sensors, such as non-gGPP wireless sensors, video, and so on.

[0082] 12. For intermediate Node (such as UE) selection, an intermediate node mobility status can be also considered as selection criteria. For example, in some embodiments if the intermediate node is detected moving out of the target service area, this intermediate node will not be considered, or if the trajectory of intermediate node is closer to the target areas, this intermediate can be selected.

[0083] 13. A prioritization between different AIoT reader selection criteria. One selection policy can contain multiple selection criteria. In some embodiments, the decision function may start from the highest selection criteria.

[0084] 14. A preferred AIoT-reader-list, which in some embodiments lists all the preferred AIoT reader to be selected. In some embodiments, different preferred listsfor various types of AIoT readers. In some embodiments, this list is used as default selection policy if other selection criteria cannot be met or is not present.

[0085] In some embodiments, as a policy may be for a mixed reader type and crossing multiple serving area deployment, the selection policy in some embodiments is constructed and organized hierarchically with different levels of sub-policies. The categorization of each level of sub-policy in some embodiments is organized by different sen ice areas, different operation times, or different AIoT operations.

[0086] A non-limiting example of a hierarchical AIoT reader selection policy is depicted in FIG. 5. In FIG. 5, a plurality of AIoT reader selection policies are organized in an example hierarchical manner. Specifically, an AIoT reader selection policy 502 for a particular service is depicted at a first level of the hierarchy, with the AIoT reader selection policy 502 defining criteria (e.g., area separation) between different AIoT reader selection policies 504A, 504B, and 504C (corresponding to an Area A policy, Area B policy, and Area C policy, respectively). Each of the AIoT reader selection policies 504A, 504B, and 504 include a plurality of defined criteria, where the AIoT reader selection policy 504A includes a different set of criteria from the AIoT reader selection policy 504B and the AIoT reader selection policy 504C. The AIoT reader selection policy 504A, corresponding to Area A, further is associated with a third level AIoT reader selection policy 506. The AIoT reader selection policy 506 is for gNB use for AIoT reader selection, and includes its own criteria.

[0087] For a selection constraint that indicates the constraint of using a certain AIoT reader, several aspects may apply. The selection criteria listed above, as well as time (including operation duration) and area restrictions, for example, can be used as constraints. In some embodiments, the AIoT reader is selected only when all the constraints are not met. The constraint, in some embodiments, also includes an indication that if co-existence of two types of AIoT readers are allowed in certain area, time. This may be because of the radio configuration in that restricted area, for example. A prohibited AIoT reader list may be used, where the list includes all the prohibited AIoT reader(s) that should not be selected. This list in some embodiments may be per AIoT sendee, per certain service area, per AIoT service provider, or per network operators. In some embodiments, this list is provided by the AF, AIoTF, or other network functions.

[0088] In addition to the AIoTF, the reader selection policy and the selection criteria can also be used by other network functions, such as the RAN, the access management function (AMF) as well as the AF which is used by the AIoT service client. There can be multiple hierarchical reader selection policies being used bydifferent network functions to coordinate the AIoT reader selection. For example, the AF may provide a first high level AIoT reader selection policy to the AIoTF for specifying a preference for an intermediate node as a reader for certain AIoT operation in certain locations and during certain times. The AIoTF may have been configured a local secondary reader selection policy for selecting the intermediate node, such as based on intermediate node load condition. After receiving the first level selection policy from AF, the AIoTF uses its local secondary intermediate node selection policy (such as based on intermediate node load condition or based on AIoT operation type) to select the potential AIoT reader from the candidate AIoT readers after satisfying the first level selection policy from the AF. The AF in some embodiments also provides the AIoT reader selection policy to the gNB to allow the gNB to use that policy to select intermediate nodes that connect with this gNB or other gNB readers.

[0089] The reader selection policy can be configured and stored in unified data management (UDM) or other network functions which manage the AIoT service and / or AIoT device subscription or profile as well as policy management (e.g. a policy control function (PCF)), so the selection policy can be associated with particular AIoT service or AIoT device(s). The reader selection policy in some embodiments also is configured or provisioned by the 0AM to the AIoT management function and / or the gNB to conduct general AIoT reader selection based on network operator’s policy. The reader selection in some embodiments also is provided by the AF to AIoT management function.

[0090] The AIoT selection policy and criteria in some embodiments are used for AIoT reader reselection, replacement, or removal. The decision function uses the selection policy to select a new’ AIoT reader, or replace the current AIoT reader with a new reader, or remove AIoT reader(s) from the operation. For example, for battery selection criteria, if an intermediate node reader’s battery’ power level drops below a certain threshold, the intermediate node reader may be replaced by a different AIoT reader with higher batteiy power in some embodiments.

[0091] In some embodiments, an information feedback mechanism may be utilized to assist in AIoT reader selection. Some embodiments provide a feedback mechanism for the function which performs the AIoT reader selection to receive the corresponding information associated with the selection criteria. The AIoT reader selection function can be the AF, the AIoT management function, or the gNB which selects the Intermediate Nodes with which the gNB is connected.

[0092] To enable selection of a suitable AIoT reader(s) according to the selection policy, new AIoT reader information request and / or response control messages being exchanged between the AIoT selector function (e.g., an AF or AIoT Management function) and the AIoT reader or other network functions are introduced, such as new message being exchanged between the AF and network functions (e.g., an AIoTF, NEF, NWDAF, or other network management functions), or the AIoT management function with the gNB or intermediate node. This request and / or response interaction can be also incorporated with the existing control messages being exchanged between AIoT selection function and other network functions and AIoT readers. This allows AIoT selection function (e.g., an AF, or AIoTF) to query mobile network and UE information which can be used for AIoT network selection.

[0093] The query and response information can include one or more pieces of information. Non-limiting examples of such information may include:

[0094] 1. Potential AIoT reader I Ds or type (intermediate Node or gNB) in the target serving area.

[0095] 2. Coverage and load status of the queried intermediate Node.

[0096] 3. Latest load condition of the serving AIoT service under the queried gNB reader.

[0097] 4. The prediction or statistic of the AIoT device behavior pattern.

[0098] 5. Capability of candidate AIoT reader, for example support certain type ofAIoT device, support certain type of AIoT operation (e.g., inventory7, read, yvrite, and / or command), security and privacy feature support capability, so on.

[0099] 6. Capacity of candidate AIoT reader, for example a maximum number ofAIoT device can serve, maximum operation duration, coverage area, so the like.

[0100] 7. An event triggered response indication. This indication in some embodiments allows the network function to only provide information when certain events occur, for example when a pre-configured threshold is reached, status change of the candidate AIoT reader, or when an AIoT device is moving out certain areas. Associated with this indication, trigger events in some embodiments are defined and provided to the network function.

[0101] During an AIoT operation / service that requires periodic or multiple transactions, such as periodic inventory operation for a period of time or sensor information collection for a period of time, some AIoT readers may be replaced or removed from the AIoT operation due to changes in certain conditions. To supportthis scenario, in some embodiments an AIoT reader status report mechanism is introduced to allow an AIoT reader to report its status to the AIoT selection function. The status report in some embodiments is configured via an AIoT control message, which can be a new dedicated AIoT select and / or active control message or be reusing existing AIoT control messages. The AIoT control message in some embodiments may have different types of reporting triggers (e.g., periodically, on- demand, or event trigger). Based on the status report from the AIoT reader, the AIoT reader selection function can make a decision if this AIoT reader needs to be replaced or removed.

[0102] Another deployment option is to enhance the NWDAF to collect AIoT reader data and provide analytic data of the AIoT reader(s), which can be used for AIoT reader selection. This mechanism allows the AIoT management function, the AF, the gNB, or other network functions to provide status data of the serving AIoT reader(s) to the NWDAF or other AI / ML functions, which provides analytic prediction data of the AIoT reader(s). This output prediction data can be per AIoT reader, per AIoT sendee, per sendee area (for example, including per cell, per tracking area (TA) or AIoT sendee area), and so on. The anahtic prediction data can be used by AIoT management function or AF to select or update the AIoT readers. Such embodiments may include a new AIoT reader status anahtic ID provided by NWDAF function.

[0103] Some other embodiments leverage integrated sensing and communication (ISAC) functions for AIoT reader selection. In some such embodiments, the AIoTF interacts with the ISAC function to collect positioning information on potential tracking objects (such as goods, equipment, animal) for the AIoT service. Each of those tracking object is attached with an AIoT device in some such embodiments. The AIoTF may determine the best suitable reader(s) based on those positioning information, for example to select the reader(s) closer to the most of target objects and / or AIoT devices, or selecting a reader based on if AIoT devices or intermediate node are indoor or outdoor, or select the readers which are surrounded by more target objects / AIoT devices.

[0104] FIGs. 6A-6B depict an example diagram of operations in AIoT reader selection, specifically by an AIoTF in a mixed topology (e.g., Topology 1 and / or Topology 2) environment. Specifically, the operations are performed between an example AF, NEF, NWDAF, UDM, optional AIoTF, AMF, one or more gNBs, one or more intermediate nodes, and one or more AIoT devices.

[0105] At operation 601, an AIoT service client initiates an AIoT inventory sendee by using the AF to send an AIoT sendee request to mobile network. AIoT sendee client groups the AIoT devices into several groups, each of the AIoT devices in a group can be associated with the same type of goods. The sendee request can include the sendee type (e.g., periodic inventory operation) that targets group 1 devices in area A, sen ice duration (e.g., 24 hours) and the periodic inventory operation interval is once per hour. The request also contains AIoT reader selection policy, such as: preference to use intermediate Node (UE) which is ow ned by the sendee client or having a business relationship with the service client, the intermediate Node’s battery status (e.g., should have more than 50% power remaining while being selected) and overall data rate (e.g., greater than 10Mbps), also the indication can allow mixed gNB readers and intermediate node readers for the service.

[0106] At operation 602, the NEF selects the appropriate AIoTF based on various criteria, such as based on the target sendng area.

[0107] At operation 603, the NEF fonvards the AIoT service request to the AIoTF.

[0108] At operation 604, the AIoTF receives a UE mobility event notification from the AMF regarding reader UEt (e.g., as Intermediate Node) has moved into another tracking area (e.g., TA2). During UEt registration procedure, UEt is registered with the AIoTF as an intermediate node and the AIoTF subscribes to the UE mobility event notification provided by the AMF for UEt.

[0109] At operation 605, the AIoTF identifies within the area A, which includes TAt (Tracking Area 1) and TA2 (Tracking Area 2), that the candidate readers are gNB A, UEi, and UE2. In some embodiments, the tracking area is a set of cells and it is used to locate a UE in a mobile network.

[0110] At optional operation 606, the AIoTF sends a request to the UDM to query if UEt and UE2 belong to a particular sendee operator (e.g., service operator X) based on their subscriptions.

[0111] At optional operation 607, the UDM responds to the AIoTF with information that UEi belongs to the service operator (e.g., service operator X) while UE2 belongs to another service operator (e.g., service operator Y).

[0112] In some embodiments operation 606 and / or operation 607 are optional, for example as the AIoTF may be provisioned with UEi and UE2 subscription information and store them locally. If an AIoTF has such subscription information,the AIoTF can check locally in some embodiments. Alternatively or additionally, an AIoTF can query the information to the AMF that UEt and UE2 connect with.

[0113] At operation 608, the AIoTF collects UEt and UE2 analytic data from NWDAF to check if their current and predicted data rate can meet the reader selection criteria from the AF.

[0114] At operation 609, the AIoTF selects UEt and gNB A in the area (e.g., area A) for the inventory service based on the request and reader selection policy from the AF, as well as AIoTF local policy on selecting the gNB reader (e.g., gNB A meets the AIoT capacity and capability criteria).

[0115] At operation 610A, the AIoTF sends the AIoT service request to gNB A for group 1 devices. Additionally or alternatively, at operation 610B, the AIoTF sends the AIoT service request to UEt for group 1 devices.

[0116] In some embodiments, at either or both of operations 611A and / or 611B, UEt and gNB A conduct an AIoT operation. The AIoTF collects the AIoT operation results from UEt and gNB A after the AIoT operations.

[0117] FIGs. 7A-7B depict an example diagram of operations in AIoT reader selection, specifically by a gNB in a mixed topology (e.g., Topology 1 and / or Topology 2) environment. Specifically, the operations are performed between an example AF, NEF, NWDAF, UDM, optional AIoTF, AMF, one or more gNBs, one or more intermediate nodes, and one or more AIoT devices.

[0118] At operation 700, an 0AM configures an AIoTF local reader selection policy. Specifically, the AIoTF local reader selection policy is configured to include criteria of: for area A, gNB selecting reader indication is set and use gNB A for AIoT reader selection.

[0119] At operation 701, an AIoT service client initiates an AIoT inventoiy service by using an AF to send an AIoT service request to mobile network. The service request includes the service type (e.g., a periodic inventory operation) that targets group 1 devices in an area (e.g., area A), service duration (e.g., 24 hour) and an interval of once per hour. The request in some embodiments also contains an AIoT reader selection policy, such as a policy that indicates prefer to use intermediate node (e.g., a UE), also indication allow mixed both gNB reader and intermediate node for maximum coverage.

[0120] At operation 702, a NEF selects the right AIoTF based on various criteria, such as based on the target serving area.

[0121] At operation 703, a NEF forwards the AIoT service request to AIoTF.

[0122] At operation 704, the AIoTF selects gNB A for reader selection.

[0123] At operation 705, the AIoTF collects analytic data information for the UE readers that are in the area of gNB A coverage.

[0124] At operation 706, the AIoTF sends AIoT service request to the gNB. In some embodiments, this request includes reader selection indication and selection assistance information. Non-limiting examples of such indications and information includes: UE reader analytic information within gNB A coverage, such as that UE1 is closer to the AIoT devices.

[0125] At operation 707, gNB A selects UE1 as AIoT reader.

[0126] At operation 708, gNB A sends AIoT service request to UE1 for group 1 devices.

[0127] At operation 709, UE1 conducts an AIoT operation, for example an inventory operation. For example, in some embodiments, the AIoTF collects the AIoT operation result from UE1.

[0128] FIGs. 8A-8B depict an example diagram of operations in a mixed AIoT reader status update for AIoT reader replacement. Specifically, the operations are performed between an example AF, NEF, NWDAF, UDM, optional AIoTF, AMF, one or more gNBs, one or more intermediate nodes, and one or more AIoT devices.

[0129] At operation 801, the AIoTF configures a gNB (e.g., gNB A) and an intermediate node (e.g., UE1) for periodic status report as well as event trigger report via an AIoT control message.

[0130] At operation 802, the AIoTF sends AIoT service request to gNB A for group 1 devices.

[0131] At operation 803, the gNB A and UE1 provide periodic or on-demand status report on the AIoT service they provide

[0132] At operation 804, the total service capability provided by UEt reaches a certain service capacity, for example its 80% service-capacity (e.g. the total AIoT devices it is serving reach of 80% of maximum number of AIoT device it can serve). This triggers UE to send event trigger report to AIoTF.

[0133] At operation 805, the AIoTF requests the analytic data on all the AIoT readers in an area (e.g., area A) from NWF.

[0134] At operation 806, the NWDAF provides analytic data on all the AIoT readers in the area A to AIoTF.

[0135] At operation 807, based on the analytic data, when the AIoTF cannot find any suitable intermediate Node which is close by UE2, then the AIoTF selects the gNB B reader that can cover the sendee area of UE1. In some such embodiments, the AIoTF sends a sendee request to gNB B, for example, to start AIoT inventory service for group 1.

[0136] At operation 808, the AIoTF sends a termination request to UEt to terminate its inventory service for group 1 devices.

[0137] At operation 809, the intermediate node (e.g., UE 2) moves into area A.

[0138] At operation 810, the UE2 sends a status update to AIoTF, for example in response to being configured for event trigger report (e.g., moving in or out of area A).

[0139] At operation 811, the AIoTF adds UE2 as reader for periodic inventory service for group 1 AIoT devices.

[0140] At operation 812, the AIoTF sends a service request to UE2 to start the inventoiy service for group 1 AIoT devices. In some embodiments, the AIoTF collects the AIoT operation result from UE2.

[0141] FIG. 9 depicts an example flow diagram depicting operations of an example process in accordance with at least some embodiments of the present disclosure. Specifically, FIG. 9 depicts a flow diagram of example operations for an internal logical flow of AIoT reader selection in the AIoT Management Function (e.g., the AIoTF, as depicted and described herein).

[0142] At operation 902, the process includes receiving an AIoT sendee request, for example by the AIoTF. The AIoT service request in some embodiments includes an AIoT reader selection policy. In some embodiments, the AIoT reader selection policy is received from an AF. Additionally or alternatively, in some embodiments the AIoT sendee request is received via a NEF.

[0143] At operation 904, the process includes checking if the AIoT reader selection policy is included, for example by the AIoTF. In some embodiments, the AIoTF checks the received AIoT sendee request to determine if the AIoT reader selection policy is included.

[0144] In a circumstance where the AIoT reader selection policy is determined to be included, the process proceeds to operation 906. At operation 906, the processincludes checking if an AIoT reader ID is included, for example by the AIoTF. In some embodiments, the AIoTF checks the AIoT sendee request, or AIoT reader selection policy therein, to determine if the AIoT reader ID is included.

[0145] In a circumstance where the AIoT reader ID is determined included, the process proceeds to operation 908.

[0146] In a circumstance where the AIoT reader is determined not included, the process continues to operation 912. At operation 912, the process includes applying the AIoT reader selection policy from the AF to identify one or more candidate AIoT reader(s). For example, the AIoTF may determine the candidate AIoT reader(s) that best fit the criteria of the AIoT reader selection policy. Additionally or alternatively, in some embodiments, the operation 912 includes collecting AIoT information from other network functions based on the AIoT reader selection policy from the AF. For example, the AIoT reader selection policy may include or otherwise define the AIoT information to be collected from the one or more other network functions. The process proceeds to operation 914.

[0147] Returning to operation 904, in a circumstance where the AIoT reader selection policy is not included, the process also proceeds to operation 914. At operation 914, the process includes applying a local stored AIoT reader policy for AIoT reader selection. The locally stored AIoT reader policy may have been previously received and / or stored, as discussed herein. Additionally or alternatively, in some embodiments the operation 914 includes collecting AIoT information from one or more other network functions based on the local AIoT reader selection policy. For example, the AIoT reader selection policy may include or otherwise define the AIoT information to be collected from the one or more other network functions.

[0148] Operation 908 is optional in some embodiments. In some such embodiments, at optional operation 908, the process includes providing a local intermediate node selection policy (or some of a local intermediate node selection policy) to a gNB. In some embodiments, the local intermediate node selection policy is provided so that the gNB may select one or more intermediate nodes that are connected, or connecting, to the gNB. In this regard, the local intermediate node selection policy may be utilized to determine which intermediate nodes are selected based on the criteria of the local intermediate node selection policy information provided to the gNB.

[0149] At operation 910, the process includes selecting and commanding an AIoT reader for the AIoT service. The AIoT reader that is selected in some embodiments isbased on the criteria of one or more AIoT reader selection policy, for example one that satisfies the criteria of an AIoT reader selection policy. The AIoT reader may be commanded to perform a particular AIoT service or operation of an action, for example an inventory operation. Additionally or alternatively, in some embodiments, the AIoT reader is configured for status reporting. For example, in some embodiments, the AIoT reader provides status report information to the AIoTF, and / or another network function, for use in subsequent AIoT reader selection processes.

[0150] FIG. 14 depicts a process embodying a method in accordance with at least one embodiment of the present disclosure. Specifically, FIG. 14 depicts a process 1400 including operations for AIoT reader selection by a first network function entity in accordance w ith at least one embodiment of the present disclosure. The example process may be performed by one or more device(s) in accordance with embodiments of the present disclosure, for example a device, system, or the like embodying an AIoTF or the like, as depicted and described herein. Optional steps may be depicted in broken (e.g., dashed) lines. The device(s) may include computer-readable code or instructions executing on one or more processors of the device(s). Coding of the software for carrying out or performing the process 1400 is well w ithin the scope of a person of ordinary skill in the art having regard to the present disclosure. The process 1400 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the software executable by the one or more processors may be stored on a non-transitory computer- readable medium, such as for example, the memory of the device(s). In some embodiments, the process 1400 may be performed by one or more of units or modules (e.g., an integrated circuit) of the device(s), such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0151] The process 1400 includes an operation 1402 of managing, by a first network function entity, two or more ambient Internet of Things (AIoT) readers within at least one service area w ith a first group of AIoT devices. The at least one serv ice area may be a single service area, or a plurality of service areas. In this regard, a first AIoT reader and a second AIoT reader of the two or more AIoT readers may be associated with different service areas. Each service area may be associated with one or more AIoT devices of the first group of AIoT devices, which are communicable with the corresponding AIoT reader within that area.

[0152] The process 1400 includes operation 1404 of receiving, by the first network function entity, first AIoT reader selection information associated with anAIoT sendee. In some embodiments, the AIoT sendee is associated with an AIoT sendee client, and the first message is from the AIoT sendee client. Additionally or alternatively, in some embodiments, the AIoT sendee client includes an application function (AF) entity.

[0153] In some embodiments, the first AIoT reader selection information includes an AIoT reader selection policy. The AIoT reader selection policy in some embodiments is one of a plurality of AIoT reader selection policies, for example of a hierarchy as depicted and described herein. The AIoT reader selection policy may be used by the first network function entity and the second network function entity during AIoT selection. Additionally or alternatively, in some embodiments, the first AIoT reader selection information is used in selecting a second network function entity. In some embodiments, the first AIoT reader selection information includes one or more of (a) an indication that both intermediate node reader types and next generation NodeB (gNB) reader types within an overlapping AIoT reader coverage area are allowed, (b) an indication that AIoT reader selection is to be decided by a gNB, (c) a maximum number of AIoT readers allowed for the sendee area or the AIoT sendee, (d) a prioritization policy between an intermediate node as a reader and the gNB as a reader when both types of readers are candidate readers w ithin the sendee area, (e) a gNB reader load condition, (f) an energy criteria, (g) a maximum number of sendng AIoT devices per reader, (h) a data-privacy-protection-based indication, (i) a target AIoT device behavior or pattern target indication, (j) a sensing based criteria, (k) an AIoT device position-based selection criteria, (1) a mobility status criteria of an intermediate node, and / or (m) a prioritization for different criteria.

[0154] The process 1400 includes operation 1406 of receiving, by the first network function entity, a first message from an AIoT application. The first message includes information of a request for the AIoT service. In some embodiments, the request for the AIoT sendee includes the first AIoT reader selection information. Additionally or alternatively, in some embodiments the first AIoT reader selection information in the request is used in selecting the second network function entity.

[0155] The process 1400 includes operation 1408 of selecting, by the first network function entity, a second network function entity from one or more second network function entities. The second network function entity serves one or more AIoT readers. In some embodiments, the second network function entity is selected based on at least some of the first AIoT reader selection information, for example including the first AIoT reader selection policy.

[0156] The process 1400 includes operation 1410 of determining, by the first network function entity, second AIoT reader selection information in accordance w ith the first AIoT reader selection information and the second network function entity. The second AIoT reader selection information may be determined to be utilized by the second network function entity for AIoT reader selection and / or for an action associated w ith AIoT devices communicable with the second network function entity or an AIoT reader associated therew ith.

[0157] The process 1400 includes operation 1412 of sending, by the first network function entity, a second message to the second network function entity. The second message includes the information of the request for the AIoT sendee and the second AIoT reader selection information. Additionally or alternatively, the second message may include other information, commands, and / or the like, utilized in performing an action.

[0158] FIG. 15 depicts a process embodying a method in accordance with at least one embodiment of the present disclosure. Specifically, FIG. 15 depicts a process 1500 including operations for AIoT reader selection by a second network function entity. The example process may be performed by one or more device(s) in accordance w ith embodiments of the present disclosure, for example a device, system, or the like embodying a gNB, intermediate node, and / or the like, as depicted and described herein. Optional steps may be depicted in broken (e.g., dashed) lines. The device(s) may include computer-readable code or instructions executing on one or more processors of the device(s). Coding of the software for carrying out or performing the process 1500 is well within the scope of a person of ordinary skill in the art having regard to the present disclosure. The process 1500 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the soft w a re executable by the one or more processors may be stored on a non-transitoiy computer-readable medium, such as for example, the memory of the device(s). In some embodiments, the process 1500 may be performed by one or more of units or modules (e.g., an integrated circuit) of the device(s), such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0159] The process 1500 includes operation 1502 of receiving, by a second network function entity, a first message from a first network function entity. The first message includes information of a request for an ambient Internet of Things (AIoT) service, and AIoT reader selection information associated with the AIoT service. In some embodiments, the first network function entity is an AIoTF. Additionally oralternatively, in some embodiments, the second network function entity is a gNB. In some embodiments, the AIoT reader selection information includes one or more of (a) an indication that both intermediate node reader types and next generation NodeB (gNB) reader types within an overlapping AIoT reader service area are allowed, (b) an indication that AIoT reader selection is to be decided by a gNB, (c) a maximum number of AIoT readers allowed for the service area or the AIoT service, (d) a prioritization policy between an intermediate node and a gNB as reader w hen both types of readers are candidate readers within the service area, (e) a gNB reader load condition, (f) an energy criteria, (g) a maximum number of serving AIoT devices per reader, (h) a data-privacy-protection-based indication, (i) a target AIoT device behavior or pattern target indication, (j) a sensing based criteria, (k) an AIoT device position-based selection criteria, (1) a mobility status criteria of an intermediate node, and / or (m) a prioritization for different criteria.

[0160] The process 1500 includes operation 1504 of selecting, by the second network function entity, a first set of AIoT readers based on the AIoT reader selection information. In some embodiments, the AIoT reader selection information includes one or more of (a) a first ID associated w ith a service provider owning or using one or more AIoT devices, the first ID being shared among the first set of AIoT readers, (b) a second ID identifying a group or a business association that the first set of AIoT readers belong to, (c) a first indication indicating one or more preferred AIoT readers to be selected, and / or (d) a second indication indicating a preference between a gNB type of readers and a user equipment (UE) type of readers. In some embodiments, the AIoT reader selection information includes first AIoT reader selection information. Second AIoT reader selection information may be determined and is based on the first AIoT reader selection information. The second AIoT reader selection information in some embodiments includes at least a portion of the first AIoT reader selection information.

[0161] The process 1500 includes operation 1506 of sending, by the second network function entity, a second message to each of the first set of AIoT readers selected. The second message includes the information of the request for the AIoT service.

[0162] In some embodiments, the first network function entity and / or second network function entity receives AIoT reader selection assistant information before sending the second message. In some embodiments, the AIoT reader selection assistant information includes information utilized by the first network function entity to select the second network function entity for AIoT reader selection, and / orincludes information utilized by the second network function entity to select the AIoT readers utilized. In some embodiments, the AIoT reader selection assistant information includes an AIoT reader selection policy. Additionally or alternatively, in some embodiments, the AIoT reader selection assistant information (or an AIoT reader selection policy thereof) includes one or more IDs of AIoT readers or a type of reader, where the type of reader includes a gNB type of reader and a UE type of reader, for each of the AIoT readers within a serving area of the second network function entity.

[0163] The process 1500 includes operation 1508 of receiving, by the second network function entity from the first set of AIoT readers, one or more responses to the request for the AIoT service. In some embodiments, the one or more responses to the request are received from the set of AIoT reader, and the one or more responses are forwarded to the first network function entity. The responses may be responses to a particular action, for example an inventory action or operation thereof. The first set of AIoT readers may be associated with at least one service area, where the at least one sendee area includes a single service area or a plurality of different sendee areas.

[0164] FIG. 16 depicts a process embodying a method in accordance with at least one embodiment of the present disclosure. Specifically, FIG. 16 depicts a process 1600 including operations for AIoT reader selection by a second network function entity. The example process may be performed by one or more device(s) in accordance with embodiments of the present disclosure, for example a device, system, or the like embodying a gNB, intermediate node, and / or the like, as depicted and described herein. Optional steps may be depicted in broken (e.g., dashed) lines. The device(s) may include computer-readable code or instructions executing on one or more processors of the device(s). Coding of the software for carrying out or performing the process 1600 is well within the scope of a person of ordinary skill in the art having regard to the present disclosure. The process 1600 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the software executable by the one or more processors may be stored on a non-transitoiy computer-readable medium, such as for example, the memory of the de ice(s). In some embodiments, the process 1600 may be performed by one or more of units or modules (e.g., an integrated circuit) of the device(s), such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0165] The process 1600 includes operation 1602 of receiving, at a network data analytics function (NWDAF) entity and from a first network function entity, a first setof selected AIoT reader information. The first AIoT reader information may include one or more AIoT reader selection policies, as depicted and described herein.

[0166] The process 1604 includes collecting, by the NWDAF and based on the first set of selected AIoT reader information, information associated with the first set of selected AIoT reader information. The information may correspond to a particular selected AIoT reader associated with at least a portion of the first set of selected AIoT reader information. In some embodiments, for example, the NWDAF collects the information associated w ith the first set of selected AIoT reader information from one or more candidate network function entities, for example based on a reader selection policy of other information of the first set of selected AIoT reader information. In some embodiments, the information may be based on the first set of selected AIoT reader information.[01671 The process 1606 includes sending, by the NWDAF and to the first network function entity, the information associated with the first set of selected AIoT reader information. The information may be utilized for selection of one or more AIoT readers in an AIoT reader selection process, as depicted and described herein.

[0168] Having described example systems and devices therein, and processes performed by various devices of the disclosure, further example system aspects are described below. FIG. 10 illustrates an example communications system 1000. Communications system 1000 includes an access node 1010 serving user equipments (UEs) with coverage 1001, such as UEs 1020. In a first operating mode, communications to and from a UE passes through access node 1010 with a coverage area 1001. The access node 1010 is connected to a backhaul network 1015 for connecting to the internet, operations and management, and so forth. In a second operating mode, communications to and from a UE do not pass through access node 1010, however, access node 1010 typically allocates resources used by the UE to communicate when specific conditions are met. Communications between a pair of UEs 1020 can use a sidelink connection (shown as two separate one-way connections 1025). In FIG.10, the sidelink communication is occurring between two UEs operating inside of coverage area 1001. However, sidelink communications, in general, can occur when UEs 1020 are both outside coverage area 1001, both inside coverage area 1001, or one inside and the other outside coverage area 1001. Communication between a UE and access node pair occur over uni -directional communication links, where the communication links between the UE and the access node are referred to as uplinks 1030, and the communication links between the access node and UE is referred to as downlinks 1035.

[0169] Access nodes may also be commonly referred to as Node-Bs, evolved Node-Bs (eNBs), next generation (NG) Node-Bs (gNBs), master-eNBs (MeNBs), secondary eNBs (SeNBs), master gNBs (MgNBs), secondary gNBs (SgNBs), network controllers, control nodes, base stations, access points, transmission points (TPs), transmission-reception points (TRPs), cells, carriers, macro cells, femtocells, pico cells, and so on, while UEs may also be commonly referred to as mobile stations, mobiles, terminals, users, subscribers, stations, and the like. Access nodes may provide w ireless access in accordance with one or more wireless communication protocols, e.g., the Third Generation Partnership Project (3GPP) long term evolution (LTE), LTE advanced (LTE-A), 5G, 5G LTE, 5G NR, sixth generation (6G), High Speed Packet Access (HSPA), the IEEE 802.11 family of standards, such as 802.na / b / g / n / ac / ad / ax / ay / be, etc. While it is understood that communications systems may employ multiple access nodes capable of communicating with a number of UEs, only one access node and two UEs are illustrated for simplicity.

[0170] FIG. 11 illustrates an example communication system 1100. In general, the system 1100 enables multiple wireless or wired users to transmit and receive data and other content. The system 1100 may implement one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), singlecarrier FDMA (SC-FDMA), or non-orthogonal multiple access (NOMA).

[0171] In this example, the communication system tioo includes electronic devices (ED) titoa-inoc, radio access networks (RANs) H2oa-ti2ob, a core network 1130, a public switched telephone network (PSTN) 1140, the Internet 1150, and other networks 1160. While certain numbers of these components or elements are shown in FIG. 11, any number of these components or elements may be included in the system 1100.

[0172] The EDs liioa-inoc are configured to operate or communicate in the system 1100. For example, the EDs liioa-inoc are configured to transmit or receive via wireless or wired communication channels. Each ED liioa-inoc represents any suitable end user device and may include such devices (or may be referred to) as a user equipment or device (UE), wireless transmit or receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular telephone, personal digital assistant (PDA), smartphone, laptop, computer, touchpad, wireless sensor, AIoT device (e.g., for asset management), or consumer electronics device.

[0173] The RANs H2oa-ii2ob here include base stations nyoa-nyob, respectively. Each base station nyoa-nyob is configured to wirelessly interface withone or more of the EDs liioa-moc to enable access to the core network 1130, the PSTN 1140, the Internet 1150, or the other networks 1160. For example, the base stations 1170a-! 170b may include (or be) one or more of several well-known devices, such as a base transceiver station (BTS), a Node-B (NodeB), an evolved NodeB (eNB), a Next Generation (NG) NodeB (gNB), a gNB centralized unit (gNB-CU), a gNB distributed unit (gNB-DU), a Home NodeB, a Home eNodeB, a site controller, an access point (AP), or a wireless router. The EDs liioa-nioc are configured to interface and communicate with the Internet 1150 and may access the core network 1130, the PSTN 1140, or the other networks 1160.

[0174] In the embodiment shown in FIG. 11, the base station 1170a forms part of the RAN 1120a, which may include other base stations, elements, or devices. Also, the base station 1170b forms part of the RAN 1120b, which may include other base stations, elements, or devices. Each base station H7oa-ii7ob operates to transmit or receive w ireless signals within a particular geographic region or area, sometimes referred to as a “cell.” In some embodiments, multiple-input multiple-output (MI MO) technology may be employed having multiple transceivers for each cell.

[0175] The base stations H70a-H70b communicate w ith one or more of the EDs liioa-moc over one or more air interfaces 1190 using wireless communication links. The air interfaces 1190 may utilize any suitable radio access technology.

[0176] It is contemplated that the system 1100 may use multiple channel access functionality, including such schemes as described above. In particular embodiments, the base stations and EDs implement 5G New Radio (NR), LTE, LTE-A, or LTE-B. Of course, other multiple access schemes and wireless protocols may be utilized.

[0177] The RANs H2oa-ti2ob are in communication with the core network 1130 to provide the EDs liioa-nioc with voice, data, application, Voice over Internet Protocol (VoIP), or other services. Understandably, the RANs Ii2oa-ti2ob or the core network 1130 may be in direct or indirect communication with one or more other RANs (not shown). The core network 1130 may also serve as a gateway access for other networks (such as the PSTN 1140, the Internet 1150, and the other networks 1160). In addition, some or all of the EDs liioa-nioc may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies or protocols. Instead of wireless communication (or in addition thereto), the EDs may communicate via wired communication channels to a service provider or switch (not shown), and to the Internet 1150.

[0178] Although FIG. 11 illustrates one example of a communication system, various changes may be made to FIG. 11. For example, the communication system 1100 could include any number of EDs, base stations, networks, or other components in any suitable configuration.

[0179] FIGs. 12A and 12B illustrate example devices that may implement the methods and teachings according to this disclosure. In particular, FIG. 12A illustrates an example ED 1210, and FIG. 12B illustrates an example base station 1270. These components could be used in the system 1100 or in any other suitable system.

[0180] As shown in FIG. 12A, the ED 1210 includes at least one processing unit 1200. The processing unit 1200 implements various processing operations of the ED 1210. For example, the processing unit 1200 could perform signal coding, data processing, power control, input / output processing, or any other functionality enabling the ED 1210 to operate in the system 1100. The processing unit 1200 also supports the methods and teachings described in more detail above. Each processing unit 1200 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 1200 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.

[0181] The ED 1210 also includes at least one transceiver 1202. The transceiver 1202 is configured to modulate data or other content for transmission by at least one antenna or NIC (Network Interface Controller) 1204. The transceiver 1202 is also configured to demodulate data or other content received by the at least one antenna 1204. Each transceiver 1202 includes any suitable structure for generating signals for wireless or wired transmission or processing signals received wirelessly or by wire. Each antenna 1204 includes any suitable structure for transmitting or receiving wireless or wired signals. One or multiple transceivers 1202 could be used in the ED 1210, and one or multiple antennas 1204 could be used in the ED 1210. Although shown as a single functional unit, a transceiver 1202 could also be implemented using at least one transmitter and at least one separate receiver.

[0182] The ED 1210 further includes one or more input / output devices 1206 or interfaces (such as a wired interface to the Internet 1150). The input / output devices 1206 facilitate interaction w ith a user or other devices (network communications) in the network. Each input / output device 1206 includes any suitable structure for providing information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen, including network interface communications.

[0183] In addition, the ED 1210 includes at least one memory 1208. The memory 1208 stores instructions and data used, generated, or collected by the ED 1210. For example, the memory 1208 could store software or firmware instructions executed by the processing unit(s) 1200 and data used to reduce or eliminate interference in incoming signals. Each memory 1208 includes any suitable volatile or non-volatile storage and retrieval device(s). Any suitable type of memory’ may be used, such as random access memory’ (RAM), read only memory’ (ROM), hard disk, optical disc, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, and the like.

[0184] As shown in FIG. 12B, the base station 1270 includes at least one processing unit 1250, at least one transceiver 1252, which includes functionality for a transmitter and a receiver, one or more antennas 1256, at least one memory? 1258, and one or more input / output devices or interfaces 1266. A scheduler, which would be understood by one skilled in the art, is coupled to the processing unit 1250. The scheduler could be included within or operated separately? from the base station 1270. The processing unit 1250 implements various processing operations of the base station 1270, such as signal coding, data processing, power control, input / output processing, or any other functionality. The processing unit 1250 can also support the methods and teachings described in more detail above. Each processing unit 1250 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 1250 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.

[0185] Each transceiver 1252 includes any suitable structure for generating signals for wireless or wired transmission to one or more EDs or other devices. Each transceiver 1252 further includes any suitable structure for processing signals received wirelessly? or by wire from one or more EDs or other devices. Although show n combined as a transceiver 1252, a transmitter and a receiver could be separate components. Each antenna 1256 includes any? suitable structure for transmitting or receiving wireless or w i red signals. While a common antenna 1256 is shown here as being coupled to the transceiver 1252, one or more antennas 1256 could be coupled to the transceiver(s) 1252, allowing separate antennas 1256 to be coupled to the transmitter and the receiver if equipped as separate components. Each memory? 1258 includes any? suitable volatile or non-volatile storage and retrieval device(s). Each input / output device 1266 facilitates interaction with a user or other devices (network communications) in the network. Each input / output device 1266 includes anysuitable structure for providing information to or receiving / providing information from a user, including network interface communications.

[0186] FIG. 13 is a block diagram of a computing system 1300 that may be used for implementing the devices and methods disclosed herein. For example, the computing system can be any entity of UE, access network (AN), mobility management (MM), session management (SM) or session management function (SMF), user plane (UP) gateway (UPGW), or access stratum (AS). Specific devices may utilize all of the components shown or only a subset of the components, and levels of integration may vary from device to device. Furthermore, a device may contain multiple instances of a component, such as multiple processing units, processors, memories, transmitters, receivers, etc. The computing system 1300 includes a processing unit 1302. The processing unit includes a central processing unit (CPU) 1314, memory 1308, and may further include a mass storage device 1304, a video adapter 1310, and an I / O interface 1312 connected to a bus 1320.

[0187] The bus 1320 may be one or more of any type of several bus architectures including a memory bus or memory controller, a peripheral bus, or a video bus. The CPU 1314 may comprise any type of electronic data processor. The memory 1308 may comprise any type of non-transitory system memory such as static random access memoiy (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or a combination thereof. In an embodiment, the memory 1308 may include ROM for use at boot-up, and DRAM for program and data storage for use while executing programs.

[0188] The mass storage 1304 may comprise any type of non-transitoiy storage device configured to store data, programs, and other information and to make the data, programs, and other information accessible via the bus 1320. The mass storage 1304 may comprise, for example, one or more of a solid state drive, hard disk drive, a magnetic disk drive, or an optical disk drive.

[0189] The video adapter 1310 and the I / O interface 1312 provide interfaces to couple external input and output devices to the processing unit 1302. As illustrated, examples of input and output devices include a display 1318 coupled to the video adapter 1310 and a mouse, keyboard, or printer 1316 coupled to the I / O interface 1312. Other devices may be coupled to the processing unit 1302, and additional or fewer interface cards may be utilized. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide an interface for an external device.

[0190] The processing unit 1302 also includes one or more network interfaces1306, which may comprise w ired links, such as an Ethernet cable, or wireless links to access nodes or different networks. The network interfaces 1306 allow the processing unit 1302 to communicate with remote units via the networks. For example, the network interfaces 1306 may provide wireless communication via one or more transmitters / transmit antennas and one or more receivers / receive antennas. In an embodiment, the processing unit 1302 is coupled to a local-area network 1322 or a wide-area network for data processing and communications with remote devices, such as other processing units, the Internet, or remote storage facilities.

[0191] It should be appreciated that one or more steps of the embodiment methods provided herein may be performed by corresponding units or modules. For example, a signal may be transmitted by a transmitting unit or a transmitting module. A signal may be received by a receiving unit or a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be performed by a performing unit or module, a generating unit or module, an obtaining unit or module, a setting unit or module, an adjusting unit or module, an increasing unit or module, a decreasing unit or module, a determining unit or module, a modifying unit or module, a reducing unit or module, a removing unit or module, or a selecting unit or module. The respective units or modules may be hardware, software, or a combination thereof. For instance, one or more of the units or modules may be an integrated circuit, such as field programmable gate arrays (FPGAs) or applicationspecific integrated circuits (ASICs).

[0192] Although the description has been described in detail, it should be understood that various changes, substitutions and alterations can be made without departing from the spirit and scope of this disclosure as defined by the appended claims. Moreover, the scope of the disclosure is not intended to be limited to the particular embodiments described herein, as one of ordinary skill in the art will readily appreciate from this disclosure that processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed, may perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.

[0193] It should be appreciated that not all components in the devices described in FIG. 10-13 are required. In a non-limiting example, the ED 1210 may be implemented as an AIoT device 1210. But, the AIoT device 1210 may not include an input / output devices1206 for providing information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen. The transceiver 1202 of the AIoT device 1210 may be capable of transmitting by backscattering a radio wave received, instead of by generating the radio wave, for wireless communication purpose. In another non-limiting example, the system 1300 may be implemented as an AIoT device 1300 that does not include or use the mass storage device 1304, the video adapter 1310, the mouse, keyboard, or printer 1316, or the display 1318.

[0194] It should be appreciated that one or more steps of the embodiment methods provided herein may be performed by corresponding units or modules. For example, a signal may be transmitted by a transmitting unit or a transmitting module. A signal may be received by a receiving unit or a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be performed by an AIoT reader management module / unit, an AIoT reader selection information transceiving module / unit, an AIoT reader selection policy management module / unit, a message transceiving module / unit, a request response transceiving module / unit, a request response management module / unit, an AIoT reader selection assistant information management module / unit, an AIoT reader service area management module / unit, and / or the like. The respective units / modules may be hardware, software, or a combination thereof. For instance, one or more of the units / modules may be an integrated circuit, such as field programmable gate arrays (FPGAs) or applicationspecific integrated circuits (ASICs).

[0195] Although the description has been described in detail, it should be understood that various changes, substitutions and alterations can be made without departing from the spirit and scope of this disclosure as defined by the appended claims. Moreover, the scope of the disclosure is not intended to be limited to the particular embodiments described herein, as one of ordinary skill in the art will readily appreciate from this disclosure that processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed, may perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.

Claims

WHAT IS CLAIMED IS:

1. A method comprising: receiving, by a first network function entity, first ambient Internet of Things (AIoT) reader selection information associated with an AIoT service; receiving, by the first network function entity, a first message from an AIoT application, the first message comprising information of a request for the AIoT service; selecting, by the first network function entity, a second network function entity from one or more second network function entities, wherein the second network function entity serves one or more AIoT readers; determining, by the first network function entity, second AIoT reader selection information in accordance with the first AIoT reader selection information and the second network function entity; and sending, by the first network function entity, a second message to the second network function entity, the second message comprising the information of the request for the AIoT service and the second AIoT reader selection information, wherein the second AIoT reader selection information is for the second network function entity to select a set of AIoT readers from the one or more AIoT readers.

2. The method of claim 1, wherein the first message is from an AIoT sendee client, and the AIoT sendee client comprises an application function (AF) entity.

3. The method of any one of claims 1-2, the first AIoT reader selection information indicates an AIoT reader selection policy that the first network function entity and the second network function entity uses during AIoT selection.

4. The method of any one of claims 1-4, wherein the first network function entity comprises an AIoT management function entity, the second network function entity comprises a base station.

5. The method of claim 4, wherein the second AIoT reader selection policy comprises AIoT reader analytic information associated w ith a coverage of the base station6. The method of any one of claims 1-5, the method further comprising: collecting, by the first network function entity, AIoT information comprising at least part of the following: AIoT service capability of one or more AIoT readers, analytic data of AIoT readers associated with the second network function entity, wherein the AIoT information is used by the first network function entity to determine the second AIoT reader selection policy7.

7. The method of any one of claims 1-6, wherein the first network function entity selects one or more different types of AIoT readers for the AIoT service.

8. The method of any one of claims 1-7, wherein the request for the AIoT service client comprises the first AIoT reader selection information used in selecting the second network function entity.

9. The method of any one of claims 1-8, wherein the first AIoT reader selection information associated with the AIoT sendee is one of a plurality of AIoT reader selection policies.

10. The method of any one of claims 1-9, wherein the first AIoT reader selection information comprises one or more of: an indication that both an intermediate node reader type and a next generation NodeB (gNB) reader type within an overlapping AIoT reader coverage area are allowed; an indication that AIoT reader selection is to be decided by a gNB; a maximum number of AIoT readers allowed for the at least one service area or the AIoT sendee; a prioritization policy between an intermediate node as a reader and the gNB as a reader when both types of readers are candidate readers within the at least one senice area; a gNB reader load condition; an energy criteria; a maximum number of serving AIoT devices per reader; a data-privacy-protection-based indication; a target AIoT device behavior or pattern target indication; a sensing based criteria; an AIoT device position-based selection criteria; a mobility status criteria of an intermediate node; or a prioritization for different criteria.

11. The method of any one of claims 1-10, further comprising: receiving, by the first network function entity from the set of AIoT readers, one or more responses to the request for the AIoT service; and sending, by the first network function entity, a third message to the AIoT application, the third message comprising the one or more responses.

12. A method comprising: receiving, by a second network function entity, a first message from a first network function entity, the first message comprising information of a request for an ambientInternet of Things (AIoT) service and AIoT reader selection information associated with the AIoT sendee; selecting, by the second network function entity, a first set of AIoT readers based on the AIoT reader selection information; sending, by the second network function entity, a second message to each of the first set of AIoT readers selected, the second message comprising the information of the request for the AIoT service; and receiving, by the second network function entity from the first set of AIoT readers, one or more responses to the request for the AIoT service.

13. The method of claim 12, wherein the AIoT reader selection information comprises an AIoT reader selection policy that the second network function entity uses to select the first set of AIoT readers.

14. The method of any one of claims 12-13, wherein the first network function entity comprises an AIoT management function (AIoTF), and the second network function entity comprises a base station.

15. The method of any one of claims 12-14, wherein the one or more responses to the request for the AIoT se n ice are received from the first set of AIoT readers by the second network function entity, and the one or more responses is forwarded to the first network function entity from the second network function entity.

16. The method of any one of claims 12-15, wherein the AIoT reader selection information comprises one or more of: a first identifier (ID) associated with a service provider owning or using one or more AIoT devices, the first ID being shared among the first set of AIoT readers, a second ID identifying a group or a business association that the first set of AIoT readers belong to, a first indication indicating one or more preferred AIoT readers to be selected, or a second indication indicating a preference between a gNB type of readers and a user equipment (UE) type of readers.

17. The method of any one of claims 12-16, wherein the AIoT reader selection information comprises first AIoT reader selection information, and second AIoT reader selection information is based on the first AIoT reader selection information and comprises at least a portion of the first AIoT reader selection information.

18. The method of any one of claims 12-17, wherein the first network function entity receives AIoT reader selection assistant information from the second network function entity before sending the second message to the second network function entity, the AIoT reader selection assistant information comprising information utilized by the first network function entity to select the second network function entity for AIoT reader selection.

19. The method of any one of claims 12-18, wherein the AIoT reader selection assistant information comprises one or more identifiers (IDs) of AIoT readers or a type of reader, the type of reader comprising a next generation NodeB (gNB) type of reader and a UE type of reader, for each of the AIoT readers within a serving area of the second network function entity.

20. The method of any one of claims 12-19, wherein the AIoT reader selection information comprises criteria comprising one or more of: an indication that both an intermediate node reader type and a next generation NodeB (gNB) reader type within an overlapping AIoT reader sendee area are allowed; an indication that AIoT reader selection is to be decided by a gNB; a maximum number of AIoT readers allowed for the at least one sendee area or the AIoT service; a prioritization policy between an intermediate node and a gNB as reader when both types of readers are candidate readers with i n the at least one sendee area; a gNB reader load condition; an energy criteria; a maximum number of sendng AIoT devices per reader; a data-privacy-protection-based indication; a target AIoT device behavior or pattern target indication; a sensing based criteria; an AIoT device position-based selection criteria; a mobility status criteria of an intermediate node; or a prioritization for different criteria.

21. A method comprising : receiving, at a network data analytics function (NWDAF) entity and from a first network function entity, first set of selected AIoT reader information ; collecting, by the NWDAF and based on the first set of selected AIoT reader information, information associated with the first set of selected AIoT reader information; andsending, by the NWDAF to the first network function entity, the information associated with the first set of selected AIoT reader information.

22. A first network function entity comprising: at least one processor; and at least one non-transitoiy computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor, cause the first network function entity to perform a method according to any one of claims 1- n.

23. A second network function entity comprising: at least one processor; and at least one non-transitoiy computer readable storage medium storing programming, the programming including instructions that, w’hen executed by the at least one processor, cause the second network function entity to perform a method according to any one of claims 12-20.

24. A device comprising : at least one processor; and at least one non-transitoiy computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor, cause the device to perform the method according to claim 21.

25. A non-transitoiy computer readable storage medium comprising instructions stored thereon that, w hen executed by at least one processor, cause the non-transitory computer readable storage medium to perform the method according to any one of claims 1-11.

26. A non-transitoiy computer readable storage medium comprising instructions stored thereon that, when executed by at least one processor, cause the non-transitory computer readable storage medium to perform a method according to any one of claims 12-20.

27. A non-transitoiy computer readable storage medium comprising instructions stored thereon that, when executed by at least one processor, cause the non-transitory' computer readable storage medium to perform a method according to claim 21.

Images