Adaptive sensing enablement service

Abstract

Described herein are methods, apparatuses, and systems for an adaptive sensing enablement service. This disclosure provides herein proposes an adaptive sensing enablement service, which is capable of managing the selection and configuration of sensing devices in a dynamic and adaptive manner. Particularly, the proposed service may support the following: monitoring sensing task process to detect conditions that may require updating the sensing configuration; dynamically updating the sensing configurations to adapt to conditions detected in the sensing tasks; leveraging analytics information to optimize and / or predict the configuration of sensing devices; and handling disruptions in sensing tasks with adaptive operations.

Description

CNV15057W001 / / 101859.002191ADAPTIVE SENSING ENABLEMENT SERVICECROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims benefit of U.S. Provisional Application No. 63 / 702.783 titled “Adaptive Sensing Enablement Service” filed October 3, 2024, the contents of which are hereby incorporated by reference in its entirety for any and all purposes.BACKGROUND3GPP Sensing

[0002] 3 GPP wireless sensing is a technology enabler to acquire information about characteristics of an environment and / or objects within the environment (or area of interest) . 3GPP sensing uses sensing signals in the form of radio waves to determine the presence, distance (range), angle, shape, velocity, or motion of objects. 3 GPP sensing relies on analyzing the transmissions, reflections, and scattering of wireless sensing signals, where the sensing signals may be transmitted and received by a sensing device such as a RAN node or a UE. Monostatic, Bistatic, and Multistatic sensing are possible. Objects that impact (e.g. reflect, refract, scatter) radio signals may be sensed by the sensing devices.

[0003] Sensing capabilities in the 3GPP network may provide new possibilities for enhanced usage of the telecommunication infrastructure in areas of object detection and tracking, environment monitoring and human motion monitoring. The capabilities may provide input to various verticals such as UAVs, smart home, V2X, and factories. Example use cases which may benefit from 3GPP sensing include: Object and intruder detection for smart home, on a highway, for railways, for factory, for predefined secure areas around critical infrastructure; Collision avoidance and trajectory tracking of UAVs, vehicles, AGVs; Automotive maneuvering and navigation; Public safety search and rescue; Rainfall monitoring and flooding; and Health and sports monitoring.

[0004] Figure 1 shows examples of the sensing signals and sensing data / result that can be transmitted among relevant entities within a 3GPP system enabled with sensing capabilities. The 3GPP system may include both 3GPP wireless sensing and other non-3GPP sensing technologies.

[0005] A sensing device is a device or sensor that is capable of transmitting sensing signals and / or receiving reflected / refracted / diffracted / scattered sensing signals to collect sensing data101859.002191 and potentially generate sensing results. Sensing data refers to the collected raw sensing data and sensing results are the outputs of processing the sensing data to obtain characteristics of an object. Sensing data / result can be provided by either 3GPP UEs or non-3GPP devices / sensors. The sensing data collected by the sensing devices can be transmitted via 3GPP or non-3GPP networks. Sensing devices may consist of UEs and RAN nodes as well as non-3GPP devices / sensors.

[0006] A target object in a sensing task may reflect / refract / diffract / scatter sensing signals and therefore can be sensed by sensing devices. A target object does not need to be connected to the network.

[0007] In order to perform a sensing task, sensing devices need to be properly selected and configured. The optimal selection and configuration of sensing devices may change over time during the sensing task period due to dynamics of the devices, target object, sensing area, etc. Furthermore, various events and conditions during the sensing task may disrupt the sensing process, such as the example shown in Figure 2.

[0008] In the example of Figure 2, RAN nodes are configured as sensing devices to perform a sensing task to track a vehicle. The RAN nodes can be configured to sense the area around the vehicle (sensing area), which is determined based on the real-time location of the vehicle. When the vehicle enters a tunnel, the sensing signals from the current sensing RAN node are blocked by the tunnel and the RAN node is unable to sense the vehicle.Furthermore, the real-time location of the vehicle is unknown through the tunnel and the sensing area cannot be determined to configure the sensing devices.

[0009] Currently, there is a lack of services defined to offload the burden of monitoring and managing the configuration of sensing devices for a sensing task. In addition, there is a lack of services defined to configure the sensing devices to adapt to dynamics and disruptions during sensing tasks.SUMMARY

[0010] Adaptive sensing enablement services are described herein. In one aspect, a method performed by an adaptive sensing enablement server or client may include: Receiving sensing device information. The sensing device information may include operation mode, availability, coverage area, location and mobility, permission indicator, objects that can be detected by the sensing device, characteristics that can be provided in the sensing results,101859.002191 sensing KPIs, etc. The sensing device information may be received via a registration or provisioning message. The sensing device information may be maintained and dynamically updated by the adaptive sensing enablement server / client. The sensing device information may be discovered by a requestor such as a VAL server or VAL client via one or more discovery requests and / or subscription requests.

[0011] The method may also include receiving a sensing task request. The sensing task request may be received from a requestor (e.g. VAL server. VAL client), a (another) sensing enablement server, a (another) sensing enablement client, etc. The sensing task request may specify sensing task type, task requirements, required sensing devices, task period, target object information, sensing area information, adaptive sensing configuration policies, notification requirements, etc. The adaptive sensing configuration policies may include policies on when and how to configure the sensing devices, when and how to update the sensing configurations, which may include the trigger conditions / events and the corresponding actions / operations to be performed by the adaptive sensing enablement sendee.

[0012] The method may also include determining sensing configuration information and sending one or more sensing configuration requests to one or more sensing devices. The sensing configuration information may include object information, task sensing area, a list of sensing devices and their corresponding device configuration for various timestamps. The sensing device configuration may include a priority indicator, device sensing area, object information, operation configuration, etc. The sensing configuration information may include sensing configuration for the current timestamp and future timestamps. The sensing configuration information may be determined based on the received sensing task request, sensing device information, analy tics information, etc. The sensing configuration information may be maintained at the adaptive sensing enablement server and / or client, and dynamically generated and updated before the task period starts and during the task period.

[0013] The method may also include receiving sensing results from the configured sensing devices. The sensing results may include information of the target object, such as the presence, location, mobility, etc.

[0014] The method may also include obtaining analytics information related to the sensing task. The analytics information may be generated by the adaptive sensing enablement sendee and / or one or more analytics sendees. The analytics information may include sensing101859.002191 configuration analytics (which may include sensing device selection analytics, sensing device configuration analytics, sensing adaptation event analytics), sensing task analytics (which may include task results analytics, task performance analytics, task disruption analytics), sensing device analytics (which may include device information analytics, device performance analytics), and the corresponding confidence level.

[0015] The method may also include sending a sensing task notification. The sensing task notification may include task results, sensing configuration information, adaptive operations that are performed by the adaptive sensing enablement service, etc. The sensing task results may include predictions and the corresponding confidence level.

[0016] The method may also include receiving sensing task feedback information. The feedback information may include performance measurements and / or indicators. The feedback information may be received from the sensing task requestor or the designated notification target(s).

[0017] The method may also include performing adaptive operations. The adaptive operations may include configuring / updating the task sensing area and / or device sensing area, configuring / updating the number of active sensing devices, configuring / updating the selection of sensing devices, configuring / updating the operation configuration of sensing devices, etc.

[0018] This Summary7is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to features that solve any or all disadvantages noted in any part of this disclosure.BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 depicts transmissions of sensing signals and sensing data / results;

[0020] Figure 2 depicts sensing task disruption: target object blocked;

[0021] Figure 3 depicts an adaptive sensing enablement service architecture;

[0022] Figure 4 depicts an adaptive sensing enablement service procedure;

[0023] Figure 5 depicts a sensing-related analytics procedure;101859.002191

[0024] Figure 6 depicts a handling task disruption;

[0025] Figure 7 depicts an update sensing area to the expected reappearance location;

[0026] Figure 8 depicts a predict sensing area for unknown obstacles;

[0027] Figure 9 depicts an example GUI for sensing task requests;

[0028] Figure 10 depicts an example GUI for sensing task notifications;

[0029] Figure 11 A depicts an example communications system in which the methods and apparatuses described and claimed herein may be an aspect of;

[0030] Figure 1 IB depicts a system diagram of an example radio access network (RAN) and core network;

[0031] Figure 11C depicts a system diagram of an example RAN and core network;

[0032] Figure 1 ID depicts a system diagram of another example RAN and core network;

[0033] Figure 1 IE depicts an example communications system:

[0034] Figure 1 IF depicts a block diagram of an example computing apparatus or device; and

[0035] Figure 11G depicts a block diagram of an example computing system.DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTSAdaptive Sensing Enablement Service Architecture

[0036] Figure 3 illustrates an example architecture for supporting an adaptive sensing enablement service within the context of a 3GPP system. The adaptive sensing enablement service architecture may support adaptive sensing enablement client(s) and server(s). An adaptive sensing enablement server may allow VAL servers to request a sensing task to be performed by sensing devices (e g. via the SES-S interface). The adaptive sensing enablement server may also be accessed by adaptive sensing enablement client(s) (e.g. via the SES-UU interface) on behalf of VAL clients which interface to the adaptive sensing enablement client(s) (e.g. via the SES-C interface). The adaptive sensing enablement server / client may interface to other functions and services in a 3 GPP system, such as SEAL location management server / client (e.g. via the SEAL-X interface), (application layer) data collection and coordination function, analytics service (e.g. NWDAF, AD AES), core network, RAN functions, etc. The adaptive sensing enablement clients on different UEs may interface with each other (e.g. via the SES-PC5 interface).101859.002191

[0037] The UE may be a sensing device, an object that can be sensed (i.e., target object), a sensing task requestor, or a combination thereof.

[0038] In addition to the example architecture shown in Figure 3. the adaptive sensing enablement service or part of the service may also be deployed as a core network function and / or RAN function.

[0039] Via the interfaces shown in Figure 3, the adaptive sensing enablement server and client may support one or more features defined herewithin. One or more of the interfaces may be mapped to existing interfaces defined in a 3GPP system. These existing interfaces may be enhanced with one or more of the features defined herewithin.

[0040] Note, one skilled in the art will recognize that the architecture shown in Figure 3 is not intended to limit or exclude other possible architectural options for supporting adaptive sensing enablement services within a 3GPP system. For example, the adaptive sensing enablement service may alternatively be realized as features of other sendees within a 3 GPP system such as but not limited to a location management service, XR (enablement) service, metaverse (enablement) service, analytics (enablement) service, etc.

[0041] Note that the adaptive sensing enablement sen ice shown in Figure 3 and described herein may also be deployed by a cloud service provider offering sensing functions / capabilities which may or may not communicate with a 3GPP network. The cloud sen ice provider may expose APIs for application servers or clients to access the adaptive sensing enablement service described herewithin.

[0042] Note, one skilled in the art will also recognize that the term client and server referenced throughout may be realized as software deployed on one or more network apparatuses comprising processor(s), memory, and network interface(s). The apparatuses may be deployed as cloud apparatuses, edge apparatuses, or device apparatuses. One or more servers and / or clients of the same or different type may be deployed on a single apparatus. A single server or client may be split and deployed across multiple apparatuses. The functionality of one type of server or client may be combined or consolidated with the functionality of another type of server or client and deployed together with one another on one or more apparatuses.

[0043] Throughout this disclosure, the adaptive sensing enablement service may refer to one or more adaptive sensing enablement servers and / or one or more adaptive sensing enabler clients.101859.002191Adaptive Sensing Enablement Service Procedure

[0044] Figure 4 provides an example of the adaptive sensing enablement service procedure. The requestor in the figure may be a VAL sen' er or an adaptive sensing enablement client requesting the assistance of an adaptive sensing enablement server for sensing service. The adaptive sensing enablement client may be hosted on a UE that is different from the UE shown in the figure and the requests may be triggered by a VAL client on the UE. Although not shown in the figure, the operations performed by an adaptive sensing enablement server may also be performed by an adaptive sensing enablement client. The procedures defined in the figure may be sequenced in an order different than is shown. Some procedures in the figure may be optional and / or performed independent of other procedures.

[0045] Step 1: An adaptive sensing enablement server and client may be provisioned with capabilities of sensing devices. A VAL server / client may register with the corresponding adaptive sensing enablement server / client to provide information for the associated sensing device(s). A sensing enablement client may register with an adaptive sensing enablement server to provide capabilities of the sensing device which may be the hosting UE. The sensing device capabilities may include information shown in Table 1. Information of the sensing devices may be maintained and dynamically updated by the adaptive sensing enablement server / client.Table 1. Sensing device information101859.002191101859.002191

[0046] Step 2: A requestor (e.g. VAL server, adaptive sensing enablement client) may send one or more messages indicating a sensing device discovery request (or subscription request) to the adaptive sensing enablement server. In addition, a sensing device may discover other sensing devices, where the associated sensing enablement client may send a discovery request to the adaptive sensing enablement server. The discovery request may include a discovery filter including the information shown in Table 1. The adaptive sensing enablement server may return a response with information of discovered sensing devices.

[0047] Step 3: A requestor (e.g. VAL server, sensing enablement client) may send one or more messages indicating a sensing task request (or subscription request) to the adaptive sensing enablement server. The sensing task request may include information as shown in Table 2.Table 2. Sensing task request101859.002191101859.002191101859.002191

[0048] Step 4: Based on the received sensing task request, the adaptive sensing enablement server may determine the sensing configuration. The adaptive sensing enablement server may request or retrieve additional information from the network and / or other entities in the system (e.g. other application / service enablement servers) to derive the sensing configuration. For example, the adaptive sensing enablement server may request sensing-related analytics information from an analytics service to determine the selection of sensing devices and their101859.002191 configurations (as described in the following section). The sensing configuration may be dynamically generated and / or updated before and as the sensing task is in progress (e.g. due to dynamics of the sensing devices and / or the target object, trigger conditions / events as specified in the adaptive sensing configuration policies) or as more information becomes available. The determined adaptive sensing configuration information (which may include configuration information for upcoming timestamps) may be maintained at the adaptive sensing enablement server, which may be used to configure the sensing devices. Table 3 shows examples of sensing configuration information.Table 3. Sensing configuration information101859.002191101859.002191101859.002191

[0049] Based on the received sensing task request and the determined sensing configuration information, the adaptive sensing enablement server may send one or more requests to the network and / or adaptive sensing enablement clients associated with the selected sensing devices to configure the sensing devices. The sensing configuration request may include information in Table 3.

[0050] Step 5: The sensing devices (including the sensing function in the 3 GPP network and the UEs) may perform sensing operations according to the sensing configurations and generate sensing results. Sensing data may be collected by the 3GPP network and processed into sensing results. Similarly, UEs may collect sensing data and generate sensing results to expose to the adaptive sensing enablement server.

[0051] Step 6: Sensing results, either from the 3GPP network or the UEs. may be sent to the adaptive sensing enablement server. The adaptive sensing enablement server may analyze the received sensing results to determine trigger conditions / events or if an adaptive operation is needed, as further elaborated in step 10.

[0052] Step 7 : The adaptive sensing enablement server may send one or more sensing task notifications to the requestor or the designated notification target according to the notification requirements specified in the sensing task request. The notification may include information as shown in Table 4.Table 4. Sensing task notification101859.002191

[0053] Step 8: The adaptive sensing enablement server may receive an acknowledgement from the requestor or the notification target, which may include feedback information. The feedback information may include performance measurements and / or indicators such as whether the task results are correct or accurate, error rate, deviation, etc. For example, a drone delivery application (requestor) may display the sensing task result to a user which shows the delivery drone has arrived at the destination address. However, the user at the address didn’t see the drone and reported this error in the application. The drone delivery application may send feedback information indicating this error in the task result. The requestor may also update the sensing task request (which may include the adaptive sensing configuration policies) or request to change the sensing configurations.101859.002191

[0054] Step 9: The adaptive sensing enablement server may generate and / or receive sensing-related analytics information, as described in the following section. Alternatively, this step may be performed after step 10 as an adaptive operation.

[0055] Step 10: Based on the sensing configuration policies, sensing results, feedback information, and sensing-related analytics information, the adaptive sensing enablement sen' er may detect conditions and events that may trigger adaptive operations. For example,

[0056] The adaptive sensing enablement senice may update the task sensing area and device sensing area. For example, the center location of the task sensing area may be dynamically adjusted to follow the (predicted) path of the target object. In another example, the size of the sensing area may be adjusted based on the number or density of detected (target) objects in the sensing area. In another example, the radius of the device sensing area may be increased to have overlapping device sensing areas such that each location in the task sensing area may be covered by more than one sensing device, which may improve the task performance. In another example, the radius of a task sensing area may be increased if the confidence level of the target object's predicted presence in the area is low so that there is higher probability to detect the target object in the configured sensing area. An upper limit of the radius of the sensing area may be specified, or can be determined based on the number and capability of sensing devices available in the sensing area.

[0057] The adaptive sensing enablement service may increase the number of active sensing devices in the events such as there are more objects detected in the task sensing area or the performance of the existing sensing devices degrades. For example, the adaptive sensing enablement service may increase the number of sensing devices and / or activate back-up sensing devices (or sensing devices with lower priorities) to perform sensing. With more active sensing devices, the device sensing area for each sensing device may shrink in size so that each sensing device may focus on sensing fewer objects. Alternatively, the size of the device sensing area may remain the same so that more activated sensing devices in the task sensing area may lead to overlapped device sensing areas, which may increase the accuracy of the results.

[0058] The adaptive sensing enablement service may update the selection of sensing devices based on the location and mobility’ information of the target objects and / or sensing devices. For example, the sensing area may change as the target object moves and / or sensing devices move, then the sensing devices may be updated based on their coverage areas and101859.002191 their distance with the target object. If the target object is known / detected to be moving, the adaptive sensing enablement service may select sensing devices located in the trajectory of the target object as the receivers of sensing operations. If the target object’s orientation is known / detected. the adaptive sensing enablement service may select sensing devices having antennas facing the target object and / or having the last amount of signaling obstruction with the target object.

[0059] The adaptive sensing enablement service may also perform operations as described in step 4 of Figure 5.

[0060] Based on the determined adaptive operations, the adaptive sensing enablement server may update the adaptive sensing configuration information (Table 3) for sensing devices and send an (updated) request to the network and / or the sensing enablement clients associated with the sensing devices to update the sensing configuration. Steps 4 through 10 may be repeatedly performed according to the adaptive operations.Analytics for Adaptive Sensing

[0061] The adaptive sensing enablement service may leverage analytics services / capabilities to obtain statistics and predictions related to the sensing task, such as the selection and configuration of sensing devices, the performance of a sensing task, the performance of a sensing device, etc. For example, the adaptive sensing enablement server / client may request an analytics service such as ADAE to generate analytics information about sensing devices and sensing performance (as shown in Figure 5). Additionally and / or alternatively, the adaptive sensing enablement service itself may be capable of generating analytics based on the received sensing results.

[0062] Step 1 : The adaptive sensing enablement sendee (server or client) may send an analytics (subscription) request to an analytics sendee (e.g. ADAE) to obtain sensing-related analytics information. In the analytics request, the adaptive sensing enablement service may provide previous sensing configuration information, sensing results and other information (e.g. information from the sensing task request as shown in Table 2, feedback information received from the requestor) as input data for the sensing-related analytics, such as the information shown in Table 5. Alternatively, the input data may be collected by the analytics service from the adaptive sensing enablement service and / or other entities in the system.Table 5. Sensing-related analytics request101859.002191101859.002191

[0063] Step 2: The analytics service may generate the required analytics information based on the analytics request and input data. Table 6 shows examples of analytics information that can be generated by the analytics service.Table 6. Sensing-related analytics information101859.002191101859.002191

[0064] Step 3: The analytics service may send a response or notification message to the adaptive sensing enablement service including the generated analytics information as shown in Table 6.

[0065] Step 4: The adaptive sensing enablement service may further process the analytics results to derive information such as the collective sensing performance for a group of sensing devices, sensing performance for a specific sensing area, sensing performance for a specific (type of) object, etc. Based on the derived information, the adaptive sensing enablement service may determine sensing configuration information and / or adaptive operations. For example,

[0066] The adaptive sensing enablement service may identify the specialty of one or more sensing devices. For example, a certain sensing device or a certain group of sensing devices101859.002191 may be the optimal choice when the object to be sensed is located in a specific area, or has a certain shape, or is composed of a certain type of material, etc.

[0067] After receiving a new sensing task request, the adaptive sensing enablement service may select sensing devices that have performed well in previous sensing tasks with a similar sensing area or a similar target object.

[0068] The adaptive sensing enablement service may update the selection and / or configuration of sensing devices based on the predicted performance of the sensing task and / or the sensing devices. For example, the adaptive sensing enablement service may increase the number of sensing devices or replace the existing sensing devices with higher performance ones if the number of objects in the sensing area is predicted to increase.

[0069] If the performance of sensing tasks at a certain area / location is always worse than the other areas in the tasks (e.g. due to area-specific interference), the adaptive sensing enablement service may assign more or higher-performance sensing devices for sensing this area when it is involved in a sensing task while selecting regular sensing devices for other sensing areas in the task.

[0070] The adaptive sensing enablement service may also perform operations as described in step 10 of Figure 4.Adaptive Operations for Task Disruption

[0071] The adaptive sensing enablement service may provide support when the sensing task encounters disruptions to ensure seamless and effective sensing. In a sensing task such as object tracking, the target object may be temporarily blocked by an obstacle or move into an obscured area (e.g. severe weather in the sensing area that affects sensing signals), which may lead to losing track of the target object (such as the example shown in Figure 2). The adaptive sensing enablement service may handle such scenario proactively and / or reactively to recover the tracking in a timely manner. An example procedure is shown in Figure 6. Although not shown in the figure, the operations performed by an adaptive sensing enablement server may also be performed by adaptive sensing enablement clients. The procedures defined in the figure may be sequenced in an order different than is shown. Some procedures in the figure may be optional and / or performed independent of other procedures.

[0072] Step 1: The adaptive sensing enablement service may take proactive actions to prepare for potential service disruptions or conditions such as an obstacle blocking the target object. For example, a proactive sensing procedure may have been performed with the101859.002191 purpose of detecting obstacles in the expected / predicted location or path of the target object that may potentially block or interfere with sensing signals to / from the target object (before the target object moves to the expected / predicted location). The adaptive sensing enablement service may further predict when the target object may be blocked based on the detected obstacle information and the (predicted) location / mobility information (e.g. speed or velocity of target object) about the target object.

[0073] Step 2: The adaptive sensing enablement server may detect the condition indicating the service disruption. For example, the received sensing results may show that the target object is detected at the sensing area in a previous time period but not detected in the current time period, which may indicate the object may be blocked.

[0074] Step 3: The adaptive sensing enablement server may apply sensing configuration policies based on the detected condition and update the sensing configuration in order to recover the sensing task (e.g. tracking of the target object). One or more of the following options may be taken.

[0075] Option 1: The adaptive sensing enablement service may update the selection of sensing devices so that the new sensing devices will be able to detect the target object. For example, if the target object enters a tunnel, the adaptive sensing enablement service may update the selection of sensing devices to devices in the vicinity of the target object which are also inside the tunnel so that they will be able to sense the target object. The re-selection of sensing devices can be done directly by the adaptive sensing enablement service.Alternatively, the adaptive sensing enablement service may update the configuration of sensing area to trigger the network to re-select the sensing devices. For example, after the target object enters a tunnel, the adaptive sensing enablement service may update the sensing area to be the space inside the tunnel and indicate that only the sensing devices within / inside the sensing area will be able to detect the target object (e.g., other vehicles in the tunnel and / or RSU in the tunnel). The updated configuration may trigger the network to re-select sensing devices that meet the requirements.

[0076] Option 2: If information of the obstacle or obscured area (e.g. size, shape, boundary) is known (e.g. from performing a proactive sensing procedure), the adaptive sensing enablement server may predict (by itself or by leveraging analytics services) when and where the target object may move out of the obscured area or be detected again based on the mobility information of the target object. The adaptive sensing enablement sen' er may then101859.002191 update the sensing area to the expected area where the target object may appear. The adaptive sensing enablement server may also configure the sensing devices to pause sensing when the target object is obscured. An example is illustrated in Figure 7.

[0077] In Figure 7, the target object (e.g. a vehicle) is blocked by an obstacle or enters an obscured area (e.g. a tunnel) at Time Period T_l. Based on the information of the obstacle (e.g. length or boundary7of the tunnel) and the predicted mobility information of the target object (e.g. velocity and direction), the adaptive sensing enablement service may predict where the object will be detected again and reposition the sensing area to the expected location (e.g. exit of the tunnel) starting from Time Period T_2. Note that the information about obstacles may have been determined by the proactive sensing procedure performed in step 1. The sensing devices will keep sensing the expected location until the target object is detected again at Time Period T n. Then the tracking will be resumed as normal. If the adaptive sensing enablement service is able to predict that the target object will be detected again at Time Period T_n, the adaptive sensing enablement service may configure the sensing devices to pause sensing starting from Time Period T_2 and resume sensing at (or ahead of) Time Period T_n. Note that the sensing devices configured to perform sensing at different time periods mentioned above may or may not be the same. To provide the VAL with continuity of sensing services during periods when a target object is in an obstructed area, the adaptive sensing enablement service may continue to estimate sensing results of a target object. The estimated sensing results may be computed by the adaptive sensing enablement service or by leveraging analytics services. For example, the adaptive sensing enablement service may determine an estimated time and location when a target object (e.g., vehicle) will exit an obstructed area (e.g., tunnel). Based on the target object’s entry location, time and speed, as well as its predicted exit location from an obstructed area, the adaptive sensing enablement service can estimate sensing results (e.g., vehicle locations and times) while the target object is an obstructed area.

[0078] Option 3: If information of the obstacle or the obscured area is unknown, the adaptive sensing enablement service may predict (by itself or by leveraging analytics services) mobility information of the target object and predict the sensing area accordingly. Based on the confidence level of the predictions, the adaptive sensing enablement service may adjust the configuration of the sensing area, such as to increase the radius of the sensing101859.002191 area (up to a pre-defined limit) if the confidence level is low, and to use a smaller radius if the confidence level is high. An example is illustrated in Figure 8.

[0079] In Figure 8. the target object (e.g. a vehicle) is blocked by an unknown obstacle or enters an obscured area at Time Period T_l. Based on the mobility information of the target object, the adaptive sensing enablement sendee may predict the expected location of the target object at Time Period T_2. The adaptive sensing enablement sen ice may then predict the sensing area at Time Period T_2 by using the expected object location as the center of the sensing area and using an increased radius for the sensing area as compared to Time Period T_l. As the confidence level of the predicted object location may decrease as time elapses, the adaptive sensing enablement service may further increase the radius of the predicted sensing area in the subsequent time periods, until the target object is detected again in Time Period T n. Then the configuration of sensing area may be reset to the normal value. Note that the sensing devices configured to perform sensing at different time periods mentioned above may or may not be the same.

[0080] Step 4: Based on the adaptive operations determined in step 3, the adaptive sensing enablement server may send an (updated) request to the network and / or the sensing enablement clients associated with the sensing devices to update the configuration of the sensing devices. The request may contain updated sensing configuration information as listed in Table 3. The adaptive sensing enablement server may receive sensing results and further process the results as needed.

[0081] Step 5: Based on the received and / or processed sensing results, the adaptive sensing enablement server may detect a new or updated condition indicating the recovery of sensing process. For example, the received or processed sensing results may indicate the target object is detected again. The adaptive sensing enablement server may determine the sensing configurations based on the detected target object in the subsequent time periods.

[0082] Step 6: The adaptive sensing enablement server may send one or more notifications to the sensing task requestor or the designated notification target indicating the detected conditions / events regarding the target object and the associated task results. The adaptive sensing enablement server may request additional information from the task requestor to assist the configuration of sensing devices (e.g. location and mobility information of the target object that is obtained through non-sensing methods).RESTful Embodiment101859.002191

[0083] In one embodiment, the information elements referenced in the adaptive sensing enablement service procedures (such as but not limited to those defined in Table 1 to Table 6) as RESTful resources. The RESTful resources may have unique addresses (e.g. URIs, URNs, etc.) and may also have one or more attributes that comprise resource data and / or metadata. These resources may be created, retrieved, discovered, updated, or deleted by the adaptive sensing enablement servers / clients, VAL servers / clients, as well as other entities in the system such as but not limited to those shown in Figure 3. Adaptive sensing enablement servers and clients may support RESTful APIs based on these resources. These APIs may be based on RESTful protocols such as HTTP and CoAP.Pub / Sub Embodiment

[0084] In another embodiment, the information elements referenced in the adaptive sensing enablement service procedures (such as but not limited to those defined in Table 1 to Table 6) as topics within a topic space of a message broker (e.g., MQTT broker, AMQP broker, etc.). An adaptive sensing enablement server and / or client may function as the message broker. Alternatively, the message broker may be hosted external to the adaptive sensing enablement server and / or client. For example, by another entity in the system which the adaptive sensing enablement server or client may communicate with. An adaptive sensing enablement server and / or client may send and / or receive publish and / or subscribe requests to topics within a message broker. The topics may have unique addresses (e.g. topic names, etc.) and also one or more attributes that contain topic data and / or metadata.Graphical User Interface Embodiment

[0085] Figure 9 shows an example GUI for sensing task requests. The requestor may specify object information, sensing requirements, notification settings, and other information in the request. The requestor may also select and / or customize adaptive sensing configuration policies to be applied to the sensing task.Communications System

[0086] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunications network technologies, including radio access, the core transport network, and service capabilities - including work on codecs, security, and quality of service. Recent radio access technology (RAT) standards comprise WCDMA (commonly referred as 3G), LTE (commonly referred as 4G), LTE- Advanced standards, and New Radio (NR), which is also referred to as “5G”. 3GPP NR standards development is expected to continue101859.002191 and comprise the definition of next generation radio access technology (new RAT), which is expected to comprise the provision of new flexible radio access below 7 GHz, and the provision of new ultra-mobile broadband radio access above 7 GHz. The flexible radio access is expected to consist of a new, non-backwards compatible radio access in new spectrum below 7 GHz, and it is expected to comprise different operating modes that may be multiplexed together in the same spectrum to address a broad set of 3GPP NR use cases with diverging requirements. The ultra-mobile broadband is expected to comprise cmWave and mmWave spectrum that may provide the opportunity for ultra-mobile broadband access for, e.g., indoor applications and hotspots. In particular, the ultra-mobile broadband is expected to share a common design framework with the flexible radio access below 7 GHz, with cmWave and mmWave specific design optimizations.

[0087] 3GPP has identified a variety of use cases that NR is expected to support, resulting in a wide variety of user experience requirements for data rate, latency, and mobility. The use cases comprise the following general categories: enhanced mobile broadband (eMBB) ultrareliable low-latency Communication (URLLC), massive machine type communications (mMTC), network operation (e.g., network slicing, routing, migration and interworking, energy savings), and enhanced vehicle-to-everything (eV2X) communications, which may comprise any of Vehicle-to-Vehicle Communication (V2V), Vehicle-to-Infrastructure Communication (V2I), Vehicle-to-Network Communication (V2N), Vehicle-to-Pedestrian Communication (V2P), and vehicle communications with other entities. Specific service and applications in these categories comprise, e.g., monitoring and sensor networks, device remote controlling, bi-directional remote controlling, personal cloud computing, video streaming, wireless cloud-based office, first responder connectivity, automotive ecall, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality7, tactile internet, virtual reality, home automation, robotics, and aerial drones to name a few. All of these use cases and others are contemplated herein.

[0088] Figure 11 A illustrates an example communications system 100 in which the systems, methods, and apparatuses described and claimed herein may be used. The communications system 100 may comprise wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g, which generally or collectively may be referred to as WTRU 102 or WTRUs 102. The communications system 100 may comprise, a radio access network (RAN) 103 / 104 / 105 / 103b / l 04b / l 05b, a core network 106 / 107 / 109, a public101859.002191 switched telephone network (PSTN) 108, the Internet 110, other networks 112, and Network Services 113. 113. Network Services 113 may comprise, for example, a V2X server, V2X functions, a ProSe server, ProSe functions, loT services, video streaming, federated learning (FL) services, and / or edge computing, etc.

[0089] It may be appreciated that the concepts disclosed herein may be used with any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102 may be any type of apparatus or device configured to operate and / or communicate in a wireless environment. In the example of Figure 11 A, each of the WTRUs 102a-d is depicted in Figures 11 A-l IE as a hand-held wireless communications apparatus. It is understood that with the wide variety of use cases contemplated for wireless communications, each WTRU may comprise or be comprised in any type of apparatus or device configured to transmit and / or receive wireless signals, including, by way of example only, user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, consumer electronics, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a vehicle such as a car, bus or truck, a train, or an airplane, and the like.

[0090] The communications system 100 may also comprise a base station 114a and a base station 114b. In the example of Figure 11A, each base stations 114a and 114b is depicted as a single element. In practice, the base stations 114a and 114b may comprise any number of interconnected base stations and / or network elements. Base stations 114a may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, and 102c to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, Network Sen-ices 113, and / or the other networks 112. Similarly, base station 114b may be any type of device configured to wiredly and / or wirelessly interface with at least one of the Remote Radio Heads (RRHs) 118a, 118b, Transmission and Reception Points (TRPs) 119a, 119b, and / or Roadside Units (RSUs) 120a and 120b to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, other networks 112. and / or Network Services 113. RRHs 118a, 118b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102, e.g., WTRU 102c, to facilitate access to one or more communication101859.002191 networks, such as the core network 106 / 107 / 109, the Internet 110, Network Services 113, and / or other networks 112.

[0091] TRPs 119a. 119b may be any type of device configured to wirelessly interface with at least one of the WTRU 102d, to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, Network Services 113, and / or other networks 112. RSUs 120a and 120b may be any ty pe of device configured to wirelessly interface with at least one of the WTRU 102e or 102f, to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109. the Internet 110, other networks 112, and / or Network Services 113. By way of example, the base stations 114a, 114b may be a Base Transceiver Station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a Next Generation Node-B (gNode B), a satellite, a site controller, an access point (AP). a wireless router, and the like.

[0092] The base station 114a may be part of the RAN 103 / 104 / 105, which may also comprise other base stations and / or network elements (not shown), such as a Base Station Controller (BSC), a Radio Network Controller (RNC), relay nodes, etc. Similarly, the base station 114b may be part of the RAN 103b / 104b / 105b, which may also comprise other base stations and / or network elements (not shown), such as a BSC, a RNC, relay nodes, etc. The base station 114a may be configured to transmit and / or receive wireless signals within a particular geographic region, which may be referred to as a cell (not shown). Similarly, the base station 114b may be configured to transmit and / or receive wired and / or wireless signals within a particular geographic region, which may be referred to as a cell (not shown). The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, for example, the base station 114a may comprise three transceivers, e.g., one for each sector of the cell. The base station 114a may employ Multiple-Input Multiple Output (MIMO) technology and. therefore, may utilize multiple transceivers for each sector of the cell, for instance.

[0093] The base station 114a may communicate with one or more of the WTRUs 102a, 102b, 102c, and 102g over an air interface 115 / 116 / 117, which may be any suitable wireless communication link (e.g., Radio Frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave. mmWave, etc.). The air interface 115 / 116 / 117 may be established using any suitable Radio Access Technology (RAT).101859.002191

[0094] The base station 114b may communicate with one or more of the RRHs 118a and 118b, TRPs 119a and 119b, and / or RSUs 120a and 120b, over a wired or air interface 115b / 116b / 117b. which may be any suitable wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., RF, microwave, IR, UV, visible light, cmWave, mmWave, etc.). The air interface 115b / l 16b / l 17b may be established using any suitable RAT.

[0095] The RRHs 118a, 118b, TRPs 119a, 119b and / or RSUs 120a, 120b, may communicate with one or more of the WTRUs 102c, 102d, 102e, 102f over an air interface 115c / I 16c / 117c. which may be any suitable wireless communication link (e.g.. RF, microwave, IR, ultraviolet UV, visible light, cmWave, mmWave, etc.) The air interface 115c / l 16c / l 17c may be established using any suitable RAT.

[0096] The WTRUs 102 may communicate with one another over a direct air interface 115d / l 16d / l 17d. such as Sidelink communication which may be any suitable wireless communication link (e.g., RF, microwave, IR, ultraviolet UV, visible light, cmWave, mmWave, etc.) The air interface 115d / l 16d / l 17d may be established using any suitable RAT.

[0097] The communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c, or RRHs 118a, 118b, TRPs 119a, 119b and / or RSUs 120a and 120b in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d, 102e, and 102f, may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 and / or 115c / l 16c / l 17c respectively using Wideband CDMA (WCDMA). WCDMA may comprise communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+).HSPA may comprise High-Speed Downlink Packet Access (HSDPA) and / or High-Speed Uplink Packet Access (HSUPA).

[0098] The base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c, and 102g, or RRHs 118a and 118b, TRPs 119a and 119b, and / or RSUs 120a and 120b in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d, may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 115 / 116 / 117 or 115c / l 16c / l 17c respectively using Long Term Evolution (LTE) and / or LTE- Advanced (LTE-A), for example. The air interface 115 / 116 / 117 or 115c / l 16c / l 17c may101859.002191 implement 3GPP NR technology'. The LTE and LTE-A technology7may comprise LTE D2D and / or V2X technologies and interfaces (such as Sidelink communications, etc.) Similarly, the 3GPP NR technology7may comprise NR V2X technologies and interfaces (such as Sidelink communications, etc.)

[0099] The base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c, and 102g or RRHs 118a and 118b, TRPs 119a and 119b, and / or RSUs 120a and 120b in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d, 102e, and 102f may implement radio technologies such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS- 2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM). Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0100] The base station 114c in Figure 11 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a train, an aerial, a satellite, a manufactory, a campus, and the like. The base station 114c and the WTRUs 102, e.g., WTRU 102e, may implement a radio technology7such as IEEE 802.11 to establish a Wireless Local Area Network (WLAN). Similarly, the base station 114c and the WTRUs 102, e.g., WTRU 102d, may implement a radio technology7such as IEEE 802. 15 to establish a wireless personal area network (WPAN). The base station 114c and the WTRUs 102, e.g., WRTU 102e. may utilize a cellular-based RAT (e.g., WCDMA. CDMA2000, GSM, LTE, LTE-A, NR, etc.) to establish a picocell or femtocell. As shown in Figure 11A, the base station 114c may have a direct connection to the Internet 110. Thus, the base station 114c may not be required to access the Internet 110 via the core netw ork 106 / 107 / 109.

[0101] The RAN 103 / 104 / 105 and / or RAN 103b / l 04b / l 05b may be in communication with the core network 106 / 107 / 109, w hich may be any type of netw ork configured to provide voice, data, messaging, authorization and authentication, applications, and / or Voice Over Internet Protocol (VoIP) services to one or more of the WTRUs 102. For example, the core network 106 / 107 / 109 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, packet data network connectivity7, Ethernet101859.002191 connectivity, video distribution, etc., and / or perform high-level security' functions, such as user authentication.

[0102] Although not shown in Figure 11 A. it may be appreciated that the RAN 103 / 104 / 105 and / or RAN 103b / l 04b / l 05b and / or the core netw ork 106 / 107 / 109 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b or a different RAT. For example, in addition to being connected to the RAN 103 / 104 / 105 and / or RAN 103b / 104b / l 05b, which may be utilizing an E-UTRA radio technology, the core network 106 / 107 / 109 may also be in communication with another RAN (not shown) employing a GSM or NR radio technology.

[0103] The core network 106 / 107 / 109 may also serve as a gateway for the WTRUs 102 to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may comprise circuit-switched telephone networks that provide Plain Old Telephone Service (POTS). The Internet 110 may comprise a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and the internet protocol (IP) in the TCP / IP internet protocol suite. The other networks 112 may comprise wired or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 may comprise any ty pe of packet data network (e.g., an IEEE 802.3 Ethernet netw ork) or another core netw ork connected to one or more RANs, which may employ the same RAT as the RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b or a different RAT.

[0104] Some or all of the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f in the communications system 100 may comprise multi-mode capabilities, e.g., the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f may comprise multiple transceivers for communicating with different wireless networks over different wireless links. For example, the WTRU 102g shown in Figure 11 A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114c, which may employ an IEEE 802 radio technology .

[0105] Although not shown in Figure 11 A. it may be appreciated that a User Equipment may make a wired connection to a gateway. The gateway maybe a Residential Gateway (RG). The RG may provide connectivity' to a Core Network 106 / 107 / 109. It may be appreciated that many of the ideas contained herein may equally apply to UEs that are101859.002191WTRUs and UEs that use a wired connection to connect to a network. For example, the ideas that apply to the wireless interfaces 115, 116, 117 and 115c / 116c / l 17c may equally apply to a wired connection.

[0106] Figure 1 IB is a system diagram of an example RAN 103 and core network 106. As noted above, the RAN 103 may employ a UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 115. The RAN 103 may also be in communication with the core network 106. As shown in Figure 11B, the RAN 103 may comprise Node-Bs 140a. 140b, and 140c, which may each comprise one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 115. The Node-Bs 140a, 140b, and 140c may each be associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also comprise RNCs 142a, 142b. It may be appreciated that the RAN 103 may comprise any number of Node-Bs and Radio Network Controllers (RNCs.)

[0107] As shown in Figure 1 IB, the Node-Bs 140a, 140b may be in communication with the RNC 142a. Additionally, the Node-B 140c may be in communication with the RNC 142b. The Node-Bs 140a, 140b, and 140c may communicate with the respective RNCs 142a and 142b via an lub interface. The RNCs 142a and 142b may be in communication with one another via an lur interface. Each of the RNCs 142aand 142b may be configured to control the respective Node-Bs 140a, 140b, and 140c to which it is connected. In addition, each of the RNCs 142aand 142b may be configured to carry out or support other functionality, such as outer loop power control, load control, admission control, packet scheduling, handover control, macro-diversity, security functions, data encryption, and the like.

[0108] The core network 106 shown in Figure 1 IB may comprise a media gateway (MGW) 144, a Mobile Switching Center (MSC) 146, a Serving GPRS Support Node (SGSN) 148, and / or a Gateway GPRS Support Node (GGSN) 150. While each of the foregoing elements are depicted as part of the core network 106, it may be appreciated that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0109] The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via an luCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may provide the WTRUs 102a, 102b, and 102c with access to101859.002191 circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, and 102c, and traditional land-line communications devices.

[0110] The RNC 142a in the RAN 103 may also be connected to the SGSN 148 in the core network 106 via an luPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between and the WTRUs 102a, 102b, and 102c, and IP-enabled devices.

[0111] The core network 106 may also be connected to the other networks 112. which may comprise other wired or wireless networks that are owned and / or operated by other sendee providers.

[0112] Figure 11C is a system diagram of an example RAN 104 and core network 107. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 1 16. The RAN 104 may also be in communication with the core network 107.

[0113] The RAN 104 may comprise eNode-Bs 160a, 160b, and 160c, though it may be appreciated that the RAN 104 may comprise any number of eNode-Bs. The eNode-Bs 160a, 160b, and 160c may each comprise one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 116. For example, the eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0114] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink and / or dow nlink, and the like. As shown in Figure 11C, the eNode-Bs 160a. 160b, and 160c may communicate with one another over an X2 interface.

[0115] The core network 107 shown in Figure 11C may comprise a Mobility Management Gateway (MME) 162, a serving gateway 164, and a Packet Data Network (PDN) gatew ay 166. While each of the foregoing elements are depicted as part of the core network 107, it may be appreciated that any one of these elements may be owned and / or operated by an entity other than the core netw ork operator.101859.002191

[0116] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an SI interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a. 102b, and 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, and 102c, and the like. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.

[0117] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via the SI interface. The serving gateway 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, and 102c. The serving gateway 164 may also perform other functions, such as anchoring user planes during inter- eNode B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, and 102c, managing and storing contexts of the WTRUs 102a, 102b, and 102c, and the like.

[0118] The serving gateway 164 may also be connected to the PDN gateway 166, which may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c, and IP-enabled devices.

[0119] The core network 107 may facilitate communications with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as the PSTN 108. to facilitate communications between the WTRUs 102a, 102b, and 102c and traditional land-line communications devices. For example, the core network 107 may comprise, or may communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the core network 107 and the PSTN 108. In addition, the core network 107 may provide the WTRUs 102a, 102b, and 102c with access to the networks 112, which may comprise other wired or wireless networks that are owned and / or operated by other service providers.

[0120] Figure 1 ID is a system diagram of an example RAN 105 and core network 109. The RAN 105 may employ an NR radio technology to communicate with the WTRUs 102a and 102b over the air interface 1 17. The RAN 105 may also be in communication with the core network 109. A Non-3GPP Interworking Function (N3IWF) 199 may employ a non-101859.0021913GPP radio technology to communicate with the WTRU 102c over the air interface 198. The N3IWF 199 may also be in communication with the core network 109.

[0121] The RAN 105 may comprise gNode-Bs 180a and 180b. It may be appreciated that the RAN 105 may comprise any number of gNode-Bs. The gNode-Bs 180a and 180b may each comprise one or more transceivers for communicating with the WTRUs 102a and 102b over the air interface 117. When integrated access and backhaul connection are used, the same air interface may be used between the WTRUs and gNode-Bs, which may be the core network 109 via one or multiple gNBs. The gNode-Bs 180a and 180b may implement MIMO, MU-MIMO, and / or digital beamforming technology. Thus, the gNode-B 180a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a. It should be appreciated that the RAN 105 may employ of other types of base stations such as an eNode-B. It may also be appreciated the RAN 105 may employ more than one type of base station. For example, the RAN may employ eNode-Bs and gNode-Bs.

[0122] The N3IWF 199 may comprise a non-3GPP Access Point 180c. It may be appreciated that the N3IWF 199 may comprise any number of non-3GPP Access Points. The non-3GPP Access Point 180c may comprise one or more transceivers for communicating with the WTRUs 102c over the air interface 198. The non-3GPP Access Point 180c may use the 802. 11 protocol to communicate with the WTRU 102c over the air interface 198.

[0123] Each of the gNode-Bs 180a and 180b may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink and / or downlink, and the like. As shown in Figure 1 ID, the gNode-Bs 180a and 180b may communicate with one another over an Xn interface, for example.

[0124] The core network 109 shown in Figure 1 ID may be a 5G core network (5GC). The core network 109 may offer numerous communication services to customers who are interconnected by the radio access network. The core network 109 comprises a number of entities that perform the functionality of the core netw ork. As used herein, the term “core network entity” or “network function” refers to any entity that performs one or more functionalities of a core network. It is understood that such core network entities may be logical entities that are implemented in the form of computer-executable instructions (softw are) stored in a memory of, and executing on a processor of, an apparatus configured101859.002191 for wireless and / or network communications or a computer system, such as system 90 illustrated in Figure 11G.

[0125] In the example of Figure 1 ID, the 5G Core Network 109 may comprise an access and mobility management function (AMF) 172, a Session Management Function (SMF) 174, User Plane Functions (UPFs) 176a and 176b, a User Data Management Function (UDM) 197, an Authentication Server Function (AUSF) 190, a Network Exposure Function (NEF) 196, a Policy Control Function (PCF) 184, a Non-3GPP Interworking Function (N3IWF) 199, a User Data Repository (UDR) 178. While each of the foregoing elements are depicted as part of the 5G core network 109, it may be appreciated that any one of these elements may be owned and / or operated by an entity other than the core network operator. It may also be appreciated that a 5G core network may not consist of all of these elements, may consist of additional elements, and may consist of multiple instances of each of these elements. Figure 1 ID shows that network functions directly connect to one another, however, it should be appreciated that they may communicate via routing agents such as a diameter routing agent or message buses.

[0126] In the example of Figure 1 ID, connectivity between network functions is achieved via a set of interfaces, or reference points. It may be appreciated that network functions may be modeled, described, or implemented as a set of services that are invoked, or called, by other netw ork functions or services. Invocation of a Network Function service may be achieved via a direct connection between netw ork functions, an exchange of messaging on a message bus. calling a software function, etc.

[0127] The AMF 172 may be connected to the RAN 105 via an N2 interface and may serve as a control node. For example, the AMF 172 may be responsible for registration management, connection management, reachability management, access authentication, access authorization. The AMF may be responsible forwarding user plane tunnel configuration information to the RAN 105 via the N2 interface. The AMF 172 may receive the user plane tunnel configuration information from the SMF via an N11 interface. The AMF 172 may generally route and forward NAS packets to / from the WTRUs 102a, 102b, and 102c via an N1 interface. The N1 interface is not shown in Figure 1 ID.

[0128] The SMF 174 may be connected to the AMF 172 via an N11 interface. Similarly the SMF may be connected to the PCF 184 via an N7 interface, and to the UPFs 176a and 176b via an N4 interface. The SMF 174 may serve as a control node. For example, the SMF101859.002191174 may be responsible for Session Management, IP address allocation for the WTRUs 102a, 102b, and 102c, management and configuration of traffic steering rules in the UPF 176a and UPF 176b, and generation of downlink data notifications to the AMF 172.

[0129] The UPF 176a and UPF 176b may provide the WTRUs 102a, 102b, and 102c with access to a Packet Data Network (PDN), such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, and 102c and other devices. The UPF 176a and UPF 176b may also provide the WTRUs 102a, 102b, and 102c with access to other types of packet data networks. For example. Other Networks 112 may be Ethernet Networks or any type of network that exchanges packets of data. The UPF 176a and UPF 176b may receive traffic steering rules from the SMF 174 via the N4 interface. The UPF 176a and UPF 176b may provide access to a packet data network by connecting a packet data network with an N6 interface or by connecting to each other and to other UPFs via an N9 interface. In addition to providing access to packet data networks, the UPF 176 may be responsible packet routing and forwarding, policy rule enforcement, quality of service handling for user plane traffic, downlink packet buffering.

[0130] The AMF 172 may also be connected to the N3IWF 199, for example, via an N2 interface. The N3IWF facilitates a connection between the WTRU 102c and the 5G core network 170, for example, via radio interface technologies that are not defined by 3GPP. The AMF may interact with the N3IWF 199 in the same, or similar, manner that it interacts with the RAN 105.

[0131] The PCF 184 may be connected to the SMF 174 via an N7 interface, connected to the AMF 172 via an N15 interface, and to an Application Function (AF) 188 via an N5 interface. The N15 and N5 interfaces are not shown in Figure 11D. The PCF 184 may provide policy rules to control plane nodes such as the AMF 172 and SMF 174, allowing the control plane nodes to enforce these rules. The PCF 184, may send policies to the AMF 172 for the WTRUs 102a, 102b, and 102c so that the AMF may deliver the policies to the WTRUs 102a, 102b, and 102c via an N1 interface. Policies may then be enforced, or applied, at the WTRUs 102a, 102b, and 102c.

[0132] The UDR 178 may act as a repository for authentication credentials and subscription information. The UDR may connect to network functions, so that network function may add to, read from, and modify the data that is in the repository. For example, the UDR 178 may connect to the PCF 184 via an N36 interface. Similarly, the UDR 178 may101859.002191 connect to the NEF 196 via an N37 interface, and the UDR 178 may connect to the UDM 197 via an N35 interface.

[0133] The UDM 197 may serve as an interface between the UDR 178 and other network functions. The UDM 197 may authorize network functions to access of the UDR 178. For example, the UDM 197 may connect to the AMF 172 via an N8 interface, the UDM 197 may connect to the SMF 174 via an N10 interface. Similarly, the UDM 197 may connect to the AUSF 190 via an N13 interface. The UDR 178 and UDM 197 may be tightly integrated.

[0134] The AUSF 190 performs authentication related operations and connects to the UDM 178 via an N13 interface and to the AMF 172 via an N12 interface.

[0135] The NEF 196 exposes capabilities and services in the 5G core network 109 to Application Functions (AF) 188. Exposure may occur on the N33 API interface. The NEF may connect to an AF 188 via an N33 interface and it may connect to other network functions in order to expose the capabilities and services of the 5G core network 109.

[0136] Application Functions 188 may interact with network functions in the 5G Core Network 109. Interaction between the Application Functions 188 and network functions may be via a direct interface or may occur via the NEF 196. The Application Functions 188 may be considered part of the 5G Core Network 109 or may be external to the 5G Core Network 109 and deployed by enterprises that have a business relationship with the mobile network operator.

[0137] Network Slicing is a mechanism that may be used by mobile network operators to support one or more ‘virtual7core networks behind the operator’s air interface. This involves ‘slicing’ the core network into one or more virtual networks to support different RANs or different service types running across a single RAN. Network slicing enables the operator to create networks customized to provide optimized solutions for different market scenarios which demands diverse requirements, e.g., in the areas of functionality, performance and isolation.

[0138] 3GPP has designed the 5G core network to support Network Slicing. Network Slicing is a good tool that network operators may use to support the diverse set of 5G use cases (e.g., massive loT, critical communications, V2X. and enhanced mobile broadband) which demand very diverse and sometimes extreme requirements. Without the use of network slicing techniques, it is likely that the network architecture would not be flexible and scalable enough to efficiently support a wider range of use cases need when each use case has101859.002191 its own specific set of performance, scalability, and availability requirements. Furthermore, introduction of new netw ork services should be made more efficient.

[0139] Referring again to Figure 1 ID, in a network slicing scenario, a WTRU 102a, 102b, or 102c may connect to an AMF 172, via an N1 interface. The AMF may be logically part of one or more slices. The AMF may coordinate the connection or communication of WTRU 102a, 102b, or 102c with one or more UPF 176a and 176b, SMF 174, and other network functions. Each of the UPFs 176a and 176b, SMF 174, and other network functions may be part of the same slice or different slices. When they are part of different slices, they may be isolated from each other in the sense that they may utilize different computing resources, security credentials, etc.

[0140] The core network 109 may facilitate communications with other networks. For example, the core net ork 109 may comprise, or may communicate with, an IP gateway, such as an IP Multimedia Subsystem (IMS) server, that serves as an interface between the 5G core network 109 and a PSTN 108. For example, the core network 109 may comprise, or communicate with a short message service (SMS) service center that facilities communication via the short message service. For example, the 5G core network 109 may facilitate the exchange of non-IP data packets between the WTRUs 102a, 102b, and 102c and servers or applications functions 188. In addition, the core network 170 may provide the WTRUs 102a, 102b, and 102c w ith access to the netw orks 112, w hich may comprise other wired or wireless networks that are owned and / or operated by other service providers.

[0141] The core network entities described herein and illustrated in Figures 11 A, 11C, 1 ID, and 1 IE are identified by the names given to those entities in certain existing 3GPP specifications, but it is understood that in the future those entities and functionalities may be identified by other names and certain entities or functions may be combined in future specifications published by 3GPP. including future 3GPP NR specifications. Thus, the particular network entities and functionalities described and illustrated in Figures 1 1A, 1 IB, 11C, 1 ID, and 1 IE are provided by way of example only, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether presently defined or defined in the future.

[0142] Figure 1 IE illustrates an example communications system 111 in which the systems, methods, apparatuses described herein may be used. Communications system 111 may comprise Wireless Transmit / Receive Units (WTRUs) A, B, C, D, E, F, a base station101859.002191 gNB 121, a V2X server 124, and Road Side Units (RSUs) 123a and 123b. In practice, the concepts presented herein may be applied to any number of WTRUs, base station gNBs, V2X networks, and / or other network elements. One or several or all WTRUs A, B, C, D, E, and F may be out of range of the access network coverage 131. WTRUs A, B, and C form a V2X group, among which WTRU A is the group lead and WTRUs B and C are group members.

[0143] WTRUs A, B, C, D, E, and F may communicate with each other over a Uu interface 129 via the gNB 121 if they are within the access network coverage 131. In the example of Figure HE, WTRUs B and F are shown within access network coverage 131. WTRUs A, B, C, D, E, and F may communicate with each other directly via a Sidelink interface (e.g., PC5 or NR PC5) such as interface 125a, 125b, or 128, whether they are under the access network coverage 131 or out of the access network coverage 131. For instance, in the example of Figure 1 IE, WRTU D. which is outside of the access network coverage 131, communicates with WTRU F, which is inside the coverage 131.

[0144] WTRUs A, B, C, D, E, and F may communicate with RSU 123a or 123b via a Vehicle-to-Network (V2N) 133 or Sidelink interface 125b. WTRUs A, B, C, D, E, and F may communicate to a V2X Server 124 via a Vehicle-to-Infrastructure (V2I) interface 127. WTRUs A, B, C, D, E, and F may communicate to another UE via a Vehicle-to-Person (V2P) interface 128.

[0145] Figure 1 IF is a block diagram of an example apparatus or device WTRU 102 that may be configured for wireless communications and operations in accordance with the systems, methods, and apparatuses described herein, such as a WTRU 102 of Figure 11A, 1 IB, 11C, 1 ID, or 1 IE. As shown in Figure 1 IF, the example WTRU 102 may comprise a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicators 128, non-removable memory 130, removable memory 132. a power source 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It may be appreciated that the WTRU 102 may comprise any subcombination of the foregoing elements. Also, the base stations 114a and 114b, and / or the nodes that base stations 114a and 114b may represent, such as but not limited to transceiver station (BTS), a Node-B, a site controller, an access point (AP), a home node-B, an evolved home node-B (eNodeB). a home evolved node-B (HeNB), a home evolved node-B gateway, a next generation node-B (gNode-B), and proxy nodes, among others, may comprise some or all of the elements depicted in Figure 1 IF and described herein.101859.002191

[0146] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller. Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality’ that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120. which may be coupled to the transmi t / receive element 122. While Figure 11 F depicts the processor 118 and the transceiver 120 as separate components, it may be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0147] The transmit / receive element 122 of a UE may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a of Figure 11A) over the air interface 115 / 116 / 117 or another UE over the air interface 115d / l 16d / l 17d. For example, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. The transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. The transmit / receive element 122 may be configured to transmit and receive both RF and light signals. It may be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless or wired signals.

[0148] In addition, although the transmit / receive element 122 is depicted in Figure 1 IF as a single element, the WTRU 102 may comprise any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology'. Thus, the WTRU 102 may comprise two or more transmit / receive elements 122 (e.g.. multiple antennas) for transmitting and receiving wireless signals over the air interface 115 / 116 / 117.

[0149] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may comprise multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs. for example NR and IEEE 802. 11 or NR and E-UTRA, or to communicate with the same RAT via multiple beams to different RRHs, TRPs, RSUs, or nodes.101859.002191

[0150] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / mi crophone 124, the keypad 126, and / or the display / touchpad / indicators 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit. The processor 118 may also output user data to the speaker / mi crophone 124, the keypad 126, and / or the display / touchpad / indicators 128. In addition, the processor 118 may access information from, and store data in, any ty pe of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 may comprise random-access memory (RAM), read-only- memory (ROM), a hard disk, or any other ty pe of memory storage device. The removable memory' 132 may comprise a subscriber identity- module (SIM) card, a memory- stick, a secure digital (SD) memory card, and the like. The processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102. such as on a server that is hosted in the cloud or in an edge computing platform or in a home computer (not shown).

[0151] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may comprise one or more dry cell batteries, solar cells, fuel cells, and the like.

[0152] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 115 / 116 / 117 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of the signals being received from two or more nearby base stations. It may be appreciated that the WTRU 102 may acquire location information by w ay of any suitable location-determination method.

[0153] The processor 118 may further be coupled to other peripherals 138, which may comprise one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may comprise various sensors such as an accelerometer, biometrics (e.g., finger print) sensors, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal101859.002191 serial bus (USB) port or other interconnect interfaces, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.

[0154] The WTRU 102 may be comprised in other apparatuses or devices, such as a sensor, consumer electronics, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a vehicle such as a car, truck, train, or an airplane. The WTRU 102 may connect to other components, modules, or systems of such apparatuses or devices via one or more interconnect interfaces, such as an interconnect interface that may comprise one of the peripherals 138.

[0155] Figure 11G is a block diagram of an exemplary computing system 90 in which one or more apparatuses of the communications networks illustrated in Figures 11 A, 11C, 1 ID and 1 IE may be embodied, such as certain nodes or functional entities in the RAN 103 / 104 / 105, Core Network 106 / 107 / 109, PSTN 108, Internet 110, Other Networks 112, or Network Services 113. Computing system 90 may comprise a computer or server and may be controlled primarily by computer readable instructions, which may be in the form of software, wherever, or by whatever means such software is stored or accessed. Such computer readable instructions may be executed within a processor 91, to cause computing system 90 to do work. The processor 91 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 91 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the computing system 90 to operate in a communications network. Coprocessor 81 is an optional processor, distinct from main processor 91, that may perform additional functions or assist processor 91. Processor 91 and / or coprocessor 81 may receive, generate, and process data related to the methods and apparatuses disclosed herein.

[0156] In operation, processor 91 fetches, decodes, and executes instructions, and transfers information to and from other resources via the computing system’s main data- transfer path, system bus 80. Such a system bus connects the components in computing101859.002191 system 90 and defines the medium for data exchange. System bus 80 typically comprises data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the system bus. An example of such a system bus 80 is the PCI (Peripheral Component Interconnect) bus.

[0157] Memories coupled to system bus 80 comprise random access memory (RAM) 82 and read only memory (ROM) 93. Such memories comprise circuitry that allows information to be stored and retrieved. ROMs 93 generally contain stored data that may not easily be modified. Data stored in RAM 82 may be read or changed by processor 91 or other hardware devices. Access to RAM 82 and / or ROM 93 may be controlled by memory controller 92. Memory controller 92 may provide an address translation function that translates virtual addresses into physical addresses as instructions are executed. Memory controller 92 may also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Thus, a program running in a first mode may access only memory mapped by its own process virtual address space; it may not access memory within another process’s virtual address space unless memory sharing between the processes has been set up.

[0158] In addition, computing system 90 may contain peripherals controller 83 responsible for communicating instructions from processor 91 to peripherals, such as printer 94, keyboard 84, mouse 95, and disk drive 85.

[0159] Display 86, which is controlled by display controller 96, is used to display visual output generated by computing system 90. Such visual output may comprise text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). Display 86 may be implemented with a CRT-based video display, an LCD-based flat-panel display, gas plasma-based flat-panel display, or a touch-panel. Display controller 96 comprises electronic components required to generate a video signal that is sent to display 86.

[0160] Further, computing system 90 may contain communication circuitry, such as for example a wireless or wired network adapter 97, that may be used to connect computing system 90 to an external communications network or devices, such as the RAN 103 / 104 / 105, Core Network 106 / 107 / 109, PSTN 108. Internet 110, WTRUs 102. or Other Networks 112 of Figures 11 A, 1 IB, 11C, 1 ID, and 1 IE, to enable the computing system 90 to communicate with other nodes or functional entities of those networks. The communication circuitry', alone101859.002191 or in combination with the processor 91. may be used to perform the transmitting and receiving steps of certain apparatuses, nodes, or functional entities described herein.

[0161] It is understood that any or all of the apparatuses, systems, methods and processes described herein may be embodied in the form of computer executable instructions (e.g., program code) stored on a computer-readable storage medium which instructions, when executed by one or more processors, such as processors 118 or 91, cause the one or more processors to perform and / or implement the systems, methods and processes described herein. Specifically, any of the steps, operations, or functions described herein may be implemented in the form of such computer executable instructions, executing on the processor(s) of an apparatus or computing system configured for wireless and / or wired network communications. Computer readable storage media comprises volatile and nonvolatile, removable and non-removable media implemented in any non-transitory (e.g.. tangible or physical) method or technology for storage of information, but such computer readable storage media do not comprise signals. Computer readable storage media comprise, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology , CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other tangible or physical medium which may be used to store the desired information and which may be accessed by a computing system.Definitions

[0162] Provided below are definitions for abbreviations found within the body of the disclosure.101859.002191Vertical Application Layer

[0163] Provided below are definitions for terms found within the body of the disclosure.

Claims

101859.002191What is claimed:

1. A method performed by an adaptive sensing enablement server, comprising: receiving sensing device information comprising at least sensing performance indicators of a sensing device; receiving a sensing task request comprising target object information and sensing performance requirements; determining sensing configuration information based on the sensing device information and sensing task request; sending one or more sensing configuration requests to one or more sensing devices; receiving sensing results from the one or more sensing devices; detecting a trigger event that requires updating the sensing configuration information based at least on the sensing results; and updating sensing configuration information.

2. The method of claim 1, wherein updating sensing configuration information comprises one or more of changing the radius of sensing area, changing the number of sensing devices, changing the sensing radius for one or more sensing devices, and changing the selection of sensing devices.

3. The method of claim 1, wherein the sensing task request comprises trigger event information.

4. The method of claim 1. wherein the trigger event comprises one or more of: mobility events of a target object, an obstruction of a target object, sensing performance degradation, and changes of sensing device information.

5. The method of claim 1. further comprising: receiving analytics information that is generated based at least on the sensing results.

6. The method of claim 5, wherein the analytics information comprises predicted trigger events.101859.0021917. The method of claim 5. wherein the analytics information comprises predicted sensing configuration information.

8. The method of claim 5, wherein the analytics information comprises predicted sensing device information.

9. The method of claim 1. further comprising: configuring sensing devices to detect obstacles that may impact the sensing operations for the sensing task.

10. The method of claim 1. wherein the sensing performance indicators of a sensing device comprises a detectable object indicator, location and mobility information, key performance indicators, sensing characteristics information, a permission indicator, a coverage area indicator, or a combination thereof.

11. An apparatus comprising an adaptive sensing enablement server, the apparatus further comprising: one or more processors; memory; and a set of computer-executable instructions stored in the memory that, when executed by the one or more processors, cause: receiving sensing device information comprising at least sensing performance indicators of a sensing device; receiving a sensing task request comprising target object information and sensing performance requirements; determining sensing configuration information based on the sensing device information and sensing task request; sending one or more sensing configuration requests to one or more sensing devices; receiving sensing results from the one or more sensing devices;101859.002191 detecting a trigger event that requires updating the sensing configuration information based at least on the sensing results; and updating sensing configuration information.

12. The apparatus of claim 11, wherein updating sensing configuration information comprises one or more of changing the radius of sensing area, changing the number of sensing devices, changing the sensing radius for one or more sensing devices, and changing the selection of sensing devices.

13. The apparatus of claim 11, wherein the sensing task request comprises trigger event information.

14. The apparatus of claim 1 1, wherein the trigger event comprises one or more of: mobility events of a target object, an obstruction of a target object, sensing performance degradation, and changes of sensing device information.

15. The apparatus of claim 11, wherein the set of computer-executable instructions, when executed by the one or more processors, further cause: receiving analytics information that is generated based at least on the sensing results.

16. The apparatus of claim 15, wherein the analytics information comprises predicted trigger events.

17. The apparatus of claim 15, wherein the analytics information comprises predicted sensing configuration information.

18. The apparatus of claim 15, wherein the analytics information comprises predicted sensing device information.

19. The apparatus of claim 1 1, wherein the set of computer-executable instructions, when executed by the one or more processors, further cause:101859.002191 configuring sensing devices to detect obstacles that may impact the sensing operations for the sensing task.

20. The apparatus of claim 11, wherein the sensing performance indicators of a sensing device comprises a detectable object indicator, location and mobility information, key performance indicators, sensing characteristics information, a permission indicator, a coverage area indicator, or a combination thereof.

Images