Methods to trigger collaborative sensing in cellular networks

Abstract

Methods for triggering collaborative sensing in cellular networks are described herein. According to an aspect of the present disclosure, a method may include receiving a first request for a collaborative sensing service; sending a second request to a cellular core network function for a sensing service; receiving sensing results in a response sent from the cellular core network function; and sending a response with the sensing results in response to the first request.

Description

METHODS TO TRIGGER COLLABORATIVE SENSING IN CELLULARNETWORKSCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 725,578 (titled ‘‘Methods to Trigger Collaborative Sensing in Cellular Networks’"), filed November 27, 2024, the contents of which are hereby incorporated by reference in its entirety for any and all purposes.BACKGROUND

[0002] Applications are becoming increasingly more complex and various mechanisms have been designed to assist with quicker development of the applications. One such mechanism is the introduction of different functional layers within (or adjacent to) the application layer to separate functions that may be accessed via application programming interfaces or APIs. FIG. 1 shows an example of a generalized application layer architecture that separates application development into three distinct layers: application-specific, vertical application enabler, and (common) service layers. At the bottom of the application stack is the (common) service layer, which provides common or horizontal services to all applications. The services may include location management, group management, configuration management, and security aspects for application development. Above the service layer is the vertical application enabler layer, which is a layer that manages services for a specific vertical application such as autonomous vehicles, drones, loT, gaming, etc. At the top of the application stack is the application-specific layer which serves specific applications within a vertical application. This layer contains custom or business logic for a particular application and may be provided by various service providers in a vertical application domain. One goal of this three-layered approach is to abstract common sendees for all applications to the vertical application enabler and service layers to simplify application development for faster deployments of the applications.

[0003] The architecture shown in FIG. 1 is based on a client-server communication model. One or more client applications on devices may communicate with one or more serv er applications on application servers. Note that server applications may reside in one or more application servers. The client application and server application of each layer communicate with each other between the devices and application servers. The application-specific client and server may communicate with client and server applications at any of the lower layers,CNV15059W001 (101859.002201) respectively. For example, an application-specific client may communicate with the client application at either the vertical application enabler or service layers. A network between the client and server applications provides the medium for communication. The network may be a cellular network such as a mobile operator network or the network may be a broadband service provider network providing access to the internet for client and server applications.

[0004] It is worth noting that the architecture shown in FIG. 1 may also apply to publish- subscribe and subscription-notification communication models. It is also worth noting that for decentralized deployments in which devices communicate directly with other devices, server functionality may reside on a device rather than on the application servers. For this case, devices may communicate with one another such that one device may function as a client and another device may function as a server.

[0005] 3 GPP wireless sensing is a technology that aims to acquire information about characteristics of an area and objects within the area using 3 GPP radio frequency (RF) signals. 3GPP wireless sensing can operate in a similar manner as radar in which the sensing transmitter and receiver are co-located in the same device. This configuration is known as monostatic sensing. Bistatic sensing can also be possible where the sensing transmitter and receiver are located in different devices. A more advanced scenario, termed multistatic sensing, with multiple sensing transmitters and receivers may be possible as well.

[0006] 3GPP w ireless sensing is the transmission of RF signals and the processing of the received signals to obtain characteristics of an area and / or objects within the area. The received signals may be reflected, refracted, diffracted, scattered, etc. from the object or the environment. Sensing characteristics can then be derived to determine the object’s size, shape, orientation, speed, location, and distance from a sensing device. 3GPP TS 22.137 provides service requirements for 3GPP wireless sensing. Within 3GPP systems, sensing devices may be RAN nodes or UEs that are able to transmit and receive sensing signals. Sensing data are collected by sensing devices and sensing results are generated from the sensing data to obtain sensing characteristics.

[0007] Sensing capabilities in 3GPP networks can provide new possibilities for enhanced usage of existing telecommunication infrastructure in areas of object detection and tracking, collision avoidance, and intruder detection. The capabilities may provide advanced usage to various verticals such as smart home, UAVs, V2X, and industrial factories.CNV15059W001 (101859.002201)While 3GPP wireless sensing offers many possibilities for new use cases, there are also challenges to obtaining characteristics about an object and / or environment through sensing. The environment may be dynamic in nature with a multitude of objects within a target area. The objects may be mobile and change location over time. During mobility, objects may change orientation and direction and thereby making it harder to track. Furthermore, obstacles may be present and interfere with sensing operations and objects may also share similar characteristics that makes it difficult to distinguish from one another.SUMMARY

[0008] Methods for triggering collaborative sensing in cellular networks are described herein. In order to overcome challenges with 3GPP wireless sensing technology, methods for triggering collaborative sensing may be employed to assist with the generation of more accurate sensing results. Sensing devices may be grouped together to obtain sensing data collaboratively. Sensing device selection may be made based on perspective, mobility, and proximity criteria and grouped together for collaborative sensing. Sensing data obtained from sensing devices in a sensing group may then be collectively processed to generate more accurate sensing results. The availability’ of sensing data from multiple sensing devices and from different perspectives, mobility’, and proximity, may increase the confidence and accuracy levels of the sensing results.

[0009] According to an aspect of the present disclosure, a method for a sensing enablement client may include sending a first request for collaborative sensing service to a sensing enablement server. The first request includes a requestor identifier, an indicator for sensing to be performed, a target sensing area, a list of requested sensing characteristics, and one or more of: sensing assistance information, a sensing depth, one or more sensing perspectives, a sensing precision level, a sensing confidence level, a minimum number of sensing devices, a number of successive sensing measurements, a number of successive sensing data, a sensing measurement window, a group collaboration window, and an expiration for the sensing request. In some cases, the list of sensing characteristics may include one or more of a size, a shape, an orientation, a speed or velocity, a position and / or location, mobility information, and a distance from a known location (e g. such as from a sensing device) for a sensed object in the target area.CNV15059W001 (101859.002201)

[0010] In some cases, the first request triggers the sensing enablement server to send a second request to a cellular core network function. The second request may trigger sensing operations to be performed by a group of sensing devices. In some cases, sensing data from the sensing operations from the group of sensing devices are collaboratively processed into sensing results.

[0011] In some cases, sensing results are returned in a response sent to the sensing enablement server. In some cases, the method may further include receiving a response with the sensing results from the sensing enablement server for the first request. In some cases, the sensing results may include one or more of a size, a shape, an orientation, a speed or velocity, a position and / or location, mobility information, and a distance from a known location (e.g. such as from a sensing device) for a sensed object in the target area.

[0012] According to another aspect of the present disclosure, a method for a sensing enablement server may include receiving a first request for collaborative sensing service. In some cases, the request includes a requestor identifier, an indicator for sensing to be performed, a target sensing area, a list of requested sensing characteristics, and one or more of: sensing assistance information, a sensing depth, one or more sensing perspectives, a sensing precision level, a sensing confidence level, a minimum number of sensing devices, a number of successive sensing measurements, a number of successive sensing data, a sensing duration, a sensing measurement window, a group collaboration window, and an expiration for the sensing request. In some cases, the list of sensing characteristics may include one or more of a size, a shape, an orientation, a speed or velocity, a position and / or location, mobility information, and a distance from a known location (e g. such as from a sensing device) for a sensed object in the target area.

[0013] The method may also include sending a second request to a cellular core network function for sensing service. In some cases, the second request includes an identifier for the application function, a service identifier, a requested service type, one or more requested sensing characteristics, one of a 2-diminsional or 3-dimensional location, and one or more of a list of sensing devices, a number of sensing devices, one or more requested sensing perspectives, sensing assistance information, a desired precision level, a desired confidence level, a number of successive measurements, a number of successive sensing data, a successive measurement window, a collaboration window, and an expiration for the request.CNV15059W001 (101859.002201)

[0014] In some cases, the second request triggers sensing operations to be performed by a group of sensing devices. In some cases, sensing data from the sensing operations from the group of sensing devices are collaboratively processed into sensing results.

[0015] The method may also include receiving sensing results in a response sent from the cellular core network function. The method may also include sending a response with the sensing results for the first request. In some cases, the sensing results may include one or more of a size, a shape, an orientation, a speed or velocity, a position and / or location, mobility information, and a distance from a known location (e.g. such as from a sensing device) for a sensed object in the target area.BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG. 1 depicts an application layer architecture model.

[0017] FIG. 2 depicts an architecture for a sensing enablement service.

[0018] FIG. 3 depicts a collaborative sensing example.

[0019] FIG. 4 depicts a UE-initiated collaborative sensing process.

[0020] FIG. 5 depicts a collaborative sensing request process.

[0021] FIG. 6 depicts a GUI for configurating sensing perspectives.

[0022] FIG. 7A depicts an example communications system in which the methods and apparatuses described and claimed herein may be an aspect of.

[0023] FIG. 7B depicts a block diagram of an example apparatus or device configured for wireless communications.

[0024] FIG. 7C depicts a system diagram of an example radio access network (RAN) and core network.

[0025] FIG. 7D depicts a system diagram of another example RAN and core network.

[0026] FIG. 7E depicts a system diagram of another example RAN and core network.

[0027] FIG. 7F depicts a block diagram of an example computing system.

[0028] FIG. 7G depicts a block diagram of another example communications system.DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

[0029] A sensing enablement service (SES) may provide VAL applications access to sensing functionality that may be available in a 3GPP network. An architecture for such a sensing enablement service is shown in Figure 2 where sensing enablement clients andCNV15059W001 (101859.002201) sensing enablement servers provide access to sensing functionalities to VAL clients and VAL servers through the SES-C and SES-S interfaces, respectively. Sensing enablement clients communicate with sensing enablement servers through the SES-UU interface and the sensing enablement server may also have an interface SES-NW with the 3GPP network. VAL clients and VAL servers communicate with each other over the VAL-UU interface.

[0030] The sensing enablement service architecture may support various sensing services and among them, collaborative sensing may be supported. Collaborative sensing describes a process where multiple sensing devices are configured and grouped together to collect sensing data for a target area or a target object in a particular area. The collection of sensing data may be synchronized to occur within a certain time duration such that the sensing data may be used collectively to generate sensing results with more accuracy and details. The selection (and location) of sensing devices relative to the target area and / or target object mayoffer sensing data from multiple perspectives to enrich the sensing results. Therefore, a certain number of sensing devices may be required to obtain sensing results with sufficient quality and / or confidence level.

[0031] The process of collaborative sensing may be illustrated with an example. Figure 3 shows an example of collaborative sensing in a vehicular application, e.g. for navigation purposes as part of autonomous vehicular operations. Other applications such as crash avoidance and vehicular cruise control operations may also be part of the vehicular application. In the example, the target object is a vehicle that is to be sensed. UE1 may initiate a collaborative sensing request to an application server in the network (which is not shown in the figure). The application server in turn may request a cellular core network to perform the collaborative sensing in which multiple sensing devices are selected to work together to sense an area or a target object in a particular area. The core network may then discover, select, and configure sensing devices in the target area to generate sensing data that may be correlated with each other to generate a more accurate and detailed sensing result. The selection of sensing devices may be made to offer multiple perspectives surrounding the target area or target object in the area. A RAN node, a road-side unit (RSU), and UE2 may be selected in this example. Other entities such as uncrewed aerial vehicles (UAV) and mobile RAN nodes may also be selected as sensing devices. Note that the RSU and UAV may be considered as UEs; the RSU as a static sensing device on the side of a road and the UAV as aCNV15059W001 (101859.002201) mobile sensing device that is airborne. The RSU and UAV may be entities comprising part of the system for the vehicular application.

[0032] Sensing devices may need to synchronize the collection of sensing data within a time window to ensure the sensing data can be correlated with each other. Additionally and / or alternatively, the core network may schedule such collaboration in the configurations of the sensing devices. For example, the core netw ork may schedule the sensing operation to be performed at the same time or within a small finite time window for the collection of sensing data to all sensing devices in the sensing group. In doing so, the sensing configuration may trigger each sensing device to synchronize its internal time with a known time source, so all sensing devices are time synchronized for the collaboration.

[0033] In Figure 3, UE1 may also participate in the collaborative sensing with UE2, RAN node, and the RSU. Note that more sensing devices may participate in the collaborative sensing than what is shown in the figure, e.g. to achieve accuracy requirements for the sensing operation.

[0034] The selection of sensing devices for the sensing group plays an important role in collaborative sensing. As shown in Figure 3, sensing devices UE1, UE2, RSU, and RAN node may be selected to provide sensing data from different perspectives or positions relative to the target object. The location of the sensing devices relative to the location of the target object or environment may be used to select sensing devices for the group. The location of the sensing devices and the sensing data that are collected may then be used to collaboratively generate sensing characteristics about the target object, e.g. the distance the target object is from a sensing device whose location is known. The speed of the target object may also be determined from sensing data collected by static sensing devices or from mobile sensing devices with known speed or velocity. The size and shape of the target object may also be determined from sensing data collected from various perspectives that are collaboratively processed. Similarly, the orientation of a target object may be determined from successive sensing data collected for a duration of time and correlated with sensing data from different perspectives.

[0035] Another consideration for the selection of sensing devices for a sensing group may be whether the sensing device is static or mobile. For certain cases, it may be beneficial for a combination of static and mobile sensing devices to be selected for the sensing group. StaticCNV15059W001 (101859.002201) sensing devices may be able to better determine the speed of a target object while a mobile device may be able to better track the movements of the target object.

[0036] The proximity of a sensing device relative to the location of the target object or environment may be another consideration for sensing device selection. A sensing device within close proximity may be able to collect more accurate sensing data and overcome any potential obstacles that may appear between the sensing device and the target object or environment. A sensing device further away from the target object may be able to sense a wider area and its sensing data may be used to help track the movements of the target object. Note that the criteria for sensing device selection may incorporate perspective (or positioning), mobility, and proximity for collaborative sensing.

[0037] After sensing measurements are collected, each sensing device in the group may send the collected sensing data to an entity in the cellular network for further processing to generate collaborated sensing results. The cellular network entity may be a RAN node, a network function in the core network, or even a UE with the capability to generate sensing results. The UE in this case may receive sensing data from other UEs in the sensing group through sidelink or device-to-device communications. In addition to sensing data, sensing devices may include its own known location, orientation and / or direction at the time of collecting the sensing data, a time stamp of when the sensing data was collected, the name or identifier of a know n time source and the last synchronization with the time source, and a confidence level associated with the sensing data. Each sensing device may be configured to collect multiple sensing measurements within a certain time and averaging the measurements to provide as sensing data. The relative distribution or similarity of the sensing measurements may assist the sensing device with deriving the confidence level for the sensing data. The configuration for collaborative sensing may specify that each sensing device generate multiple successive sensing data to further enhance the sensing results.

[0038] The collaborative sensing example shown in Figure 3 may also be represented as a procedure, which is shown in Figure 4. In this alternative representation, a sensing enablement server is shown as w ell as a sensing enablement client, which resides on UE1 in this example. The sensing enablement server represents the application server in the network that is authorized to request for collaborative sensing. RSU and UE2 are represented as nearby UEs in the figure and the RAN node and the 3GPP CN are the entities in the cellular network performing the sensing operations and calculating the sensing results, respectively.CNV15059W001 (101859.002201)Within the 3GPP CN, a network function may be defined to process sensing service requests and is responsible for configuring sensing devices for collaborative sensing and generating sensing results from sensing data received from sensing devices. Note that in this example, a network function in the 3GPP CN is generating the sensing results. An alternative is that a RAN node may also have the capability to generate sensing results and as previously mentioned, a UE may also have the capability to generate sensing results. The detailed description of a RAN node generating sensing results will be provided in a subsequent procedure.

[0039] Step 1: A sensing enablement client may be triggered by a VAL client on UE1 to make a request for sensing service to a sensing enablement server in the network. The request may include the information elements as depicted in Table 1. Note that even though the sensing related parameters in Table 1 are shown as separate information elements in the sensing service request, the parameters may be grouped together as part of a sensing policy that may be provided in the sensing service request or configured / provisioned to the sensing enablement client or server to assist with initiating sensing operations.Table 1 - Sensing service request parametersCNV15059W001 (101859.002201)CNV15059W001 (101859.002201)

[0040] Step 2: Using the parameters received in the sensing service request or from a sensing policy, the sensing enablement server may determine that a collaborative sensing may be required. The sensing enablement server may make the determination based on parameters such as requested 3-dimensional sensing, sensing perspective parameters, minimum number of sensing devices, group collaboration window, etc. The sensing enablement server may send a collaborative sensing request to a network function in the 3GPP core network (CN). The request may include the information listed in Table 1.

[0041] Step 3: Using the information received from the collaborative sensing request from step 2, a network function in the 3GPP core network may initiate the process of discovering sensing devices in the target area, selecting sensing devices that meets the requirements for the sensing operations, and configuring the selected sensing devices with sensing parameters required for the sensing devices to collect sensing data for the collaboration and processing of the sensing data into sensing results.

[0042] Step 4 : Each configured sensing device performs one or more sensing operations as specified by the sensing configuration provided in step 3. The sensing devices may collect successive sensing measurements within a measurement window and perform a statistical operation on the collected sensing measurements to obtain sensing data to return to a sensing data processing entity such as a RAN node or a network function in the core network. Each sensing device may obtain one or more sensing data during this step according to the Number of successive sensing data parameter.

[0043] Prior to initiating sensing operations, each sensing device may perform a time synchronization with a known time source to have time synchronization with other members of the collaborative sensing. The sensing device may skip performing the time synchronization if a synchronization had already been performed recently.

[0044] Sensing devices within the sensing group may also be configured to obtain sensing measurements within a certain duration as specified by the Group collaboration window parameter. This enables the sensing data to be correlated with each other for collaborative sensing. If configured, sensing devices may also collect successive sensing measurements within a configured Measurement window' to provide more accurate sensing data. Combined,CNV15059W001 (101859.002201) the Measurement window and Group collaboration window parameters may be used to increase the confidence level of the generated sensing results.

[0045] Step 5: Once sensing data are available, each sensing device may send one or more notifications with the sensing data to a network function responsible for processing the sensing data into sensing results. The sensing devices may send the sending data as they become available, or the sensing devices may aggregate the sensing data and send a single notification with all the sensing data. In addition to sensing data, sensing devices may include its own known location, orientation and / or direction at the time of collecting the sensing data, a time stamp of when the sensing data was collected, the name or identifier of a known time source and the last synchronization with the time source, and a confidence level associated with the sensing data.

[0046] Step 6: The network function processes all the received sensing data to generate collaborative sensing result(s) for the sensing request received in step 2. The network function may also use information provided by the sensing device as previously described to generate the collaborative sensing result(s).

[0047] Step 7: The network function in the 3GPP CN sends a response to the sensing enablement server with the sensing results for the collaborative sensing operation. The response includes information as listed in Table 2.Table 2 - Sensing results for collaborative sensing operationCNV15059W001 (101859.002201)

[0048] Step 8: The sensing enablement server sends a response to the sensing enablement client and includes the sensing results received from the network function in the 3GPP CN as listed in Table 2.

[0049] The procedure described by Figure 4 depicted a UE requesting collaborative sensing via a sensing enablement client initiating the request. In that example, the UE making the request is not part of the collaborative sensing. An alternative method may be such that a VAL server may initiate the collaborative sensing with a sensing enablement server. Figure 5 shows such an example procedure. In this example, a VAL server requests the collaborative sensing on behalf of UE1 and UE1 may even participate in the collaborative sensing operation. The example may describe an autonomous navigation service as part of a city’s traffic management system. The VAL server may request collaborative sensing for areas along the navigation route towards a destination. UE1 may participate in the collaborative sensing to sense nearby objects and may provide one of the sensing perspectives. In addition, a sensing enablement client on UE1 may also initiate the collaborative sensing to request assistance from other nearby sensing devices, e.g. as part of sidelink or device-to-device communications.

[0050] Step 1 : A VAL server may initiate a sensing service request that triggers collaborative sensing operations. The request may include information elements as listed in Table 1. The sensing request may include an indication for collaborative sensing, or the request may be designed for triggering collaborative sensing, i.e. the request is defined forCNV15059W001 (101859.002201) collaborative sensing. Alternatively, a sensing enablement client (SEC) may also be able to request for collaborative sensing. A SEC may be triggered by a VAL client located on UE1 to request for collaborative sensing and UE1 has sensing capabilities. The VAL client may be looking for assistance from other sensing devices (e.g. from different perspectives) in the surrounding area to perform collaborative sensing.

[0051] Steps 2 to 6: The sensing enablement server may send a collaborative sensing request to a network function in the 3GPP CN as in step 2 of Figure 4. The request sent in step 2 may trigger the execution of steps 3 - 6 similar to that of steps 3 - 6 of Figure 4 with a couple of modifications. In this example, steps 3 - 5 may involve UE1 whereas steps 3 - 5 of Figure 4 did not include UE1. As previously described, UE1 is participating in the collaborative sensing in this example. In addition, a RAN node is generating the sensing results in this example as opposed to the example described by Figure 4. UE1 and nearby UEs (i.e. UE2 and RSU as shown in Figure 3) send their sensing data to the RAN node serving the local area and the RAN node generates the collaborated sensing result(s).

[0052] Step 7: The RAN node sends the collaborated sensing result(s) to a network function in the 3GPP CN. Steps 4 to 6 may be repeated according to sensing configurations provided in step 3.

[0053] Step 8: The network function in the 3GPP CN may aggregate collaborative sensing results from multiple RAN nodes or from a combination of RAN nodes and UEs capable of generating sensing results. The 3GPP CN may send a response to the collaborative sensing request received in step 2. The response may include the information elements listed in Table 2.

[0054] Step 9: Similar to step 8 of Figure 4, the sensing enablement server may send a response to the sensing service requestor, which in this case is the VAL server. The information elements in the response may be ones similar to those listed in Table 2.

[0055] Note that Figure 4 and Figure 5 shows sensing enablement clients and VAL clients and servers making sensing service requests for collaborative sensing, respectively. There may be other entities that are able to make requests. For example, an analytics server, a spatial map server, and other enabler servers and clients may also be able to make sensing service requests to trigger collaborative sensing. Furthermore, UEs may be configured to provide collaborative sensing results if the UEs are capable of and authorized to do so. In this scenario, multiple UEs may be configured to be part of a sensing group and at least one UECNV15059W001 (101859.002201) within the sensing group has the capability to generate sensing results. The UEs within the sensing group performs sensing operations as previously described using sidelink or device- to-device communication. The UE capable of generating sensing results then aggregates and correlates all the sensing data from the other UEs together to generate collaborative sensing results. The UE may then send the sensing results to a 3GPP network function for exposure to application servers.

[0056] Previously, step 2 of Figure 4 described the sensing enablement server making a request to a network function in the 3GPP core network for collaborative sensing. The request may include information elements as listed in Table 3.Table 3 - Sensing service request to 3GPP core networkCNV15059W001 (101859.002201)

[0057] An important configuration parameter when requesting collaborative sensing is sensing perspectives. The use of sensing perspectives may be better illustrated with an example. Figure 6 shows an example of a graphical user interface that may be provided on a VAL server to configure sensing perspectives. The GUI shows a rendering of a target area of interest with known information provided to the VAL server. In this example, the VAL server may have the location information of UE1, a RAN node, and a RSU as shown. In addition, the VAL server may have identified a target area for which to request collaborative sensing. The figure shows the different sensing perspectives that may be configured for collaborative sensing. Sensing perspectives Pl to P6 may be specified as a list of 2-dimensional areas surrounding the sensing area for complete sensing coverage. Sensing perspective P7E may be specified as a 2-dimensional area with an elevation component, e g. to infer sensing is required to be performed by a UAV in the area. The sensing perspective configuration may then be used by a sensing service in the 3GPP core network to select sensing devices as part of a sensing group for collaborative sensing.

[0058] The GUI shown in Figure 6 may be replaced with another rendering if the collaborative sensing request was made by a sensing enablement client. The new rendering may show the area based on the field of view of the vehicle associated with UE1, e.g. from a camera mounted on the windshield of the vehicle. However, if the vehicle is equipped with a 360-degree camera system, the rendering may include all areas surrounding the vehicle. The configuration of sensing perspectives may be specified by the vehicular applicationCNV15059W001 (101859.002201) autonomously or presented in a GUI in a VAL client for a user within the vehicle to further configure.Example Communications System

[0059] 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 quality7of service. Recent radio access technology (RAT) standards include 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 continue and include the definition of next generation radio access technology (new RAT), which is expected to include the provision of new7flexible 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 include 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 include cmWave and mmWave spectrum that will 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 below77 GHz, with cmWave and mmWave specific design optimizations.

[0060] 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 include 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 include 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 include, e.g., monitoring and sensor networks, device remote controlling, bi-directional remote controlling, personal cloud computing, video streaming, wireless cloud-based office, first responder connectivity7, automotive ecall, disaster alerts,CNV15059W001 (101859.002201) real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile internet, virtual reality, home automation, robotics, and aerial drones to name a few. All of these use cases and others are contemplated herein.

[0061] FIG. 7A illustrates an example communications system 100 in which the methods and apparatuses described and claimed herein may be an aspect of. As shown, the example communications system 100 may include 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), a radio access network (RAN) 103 / 104 / 105 / 103b / 104b / l 05b. a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, other networks 112, and V2X server (or ProSe function and server) 113, though it will be appreciated that the disclosed examples contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b. 102c. 102d, 102e, 102f, 102g may be any type of apparatus or device configured to operate and / or communicate in a wireless environment. Although each WTRU 102a, 102b, 102c, 102d, 102e, 102f, 102g is depicted in FIGs 7A-7E as a hand-held wireless communications apparatus, it is understood that with the wide variety of use cases contemplated for 5G wireless communications, each WTRU may comprise or be embodied 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 static 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, truck, train, or airplane, and the like.

[0062] The communications system 100 may also include a base station 114a and a base station 114b. Base stations 114a may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c to facilitate access to one or more communication netw orks, such as the core netw ork 106 / 107 / 109, the Internet 110, and / or the other networks 112. Base stations 114b may be any type of device configured to wiredly and / or wirelessly interface with at least one of the RRHs (Remote Radio Heads) 118a, 118b, TRPs (Transmission and Reception Points) 119a, 119b, and / or RSUs (Roadside Units) 120a and 120b to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, the other networks 112, and / or V2X server (or ProSeCNV15059W001 (101859.002201) function and server) 113. RRHs 118a, 118b may be any type of device configured to wirelessly interface with at least one of the WTRU 102c, to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or the other networks 1 12. 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, and / or the other networks 112. RSUs 120a and 120b may be any type of device configured to wirelessly interface with at least one of the WTRU 102e or 102f, to facilitate access to one or more communication netw orks, such as the core netw ork 106 / 107 / 109, the Internet 110, the other networks 112, and / or V2X server (or ProSe function and server) 113. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), aNode-B, an eNode B, a Home Node B. a Home eNode B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or netw ork elements.

[0063] The base station 114a may be part of the RAN 103 / 104 / 105, which may also include other base stations and / or netw ork elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114b may be part of the RAN 103b / 104b / 105b, which may also include other base stations and / or netw ork elements (not shown), such as a base station controller (BSC), a radio network controller (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). 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, the base station 114a may include three transceivers, e.g., one for each sector of the cell. In some cases, the base station 114a may employ multiple-input multiple output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.

[0064] The base stations 114a may communicate with one or more of the WTRUs 102a, 102b, 102c over an air interface 115 / 1 16 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microw ave, infrared (IR), ultraviolet (UV),CNV15059W001 (101859.002201) visible light, cmWave, mmWave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT).

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

[0066] 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 / l 16c / l 17c, 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 115c / l 16c / l 17c may be established using any suitable radio access technology (RAT).

[0067] The WTRUs 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g may communicate with one another over an air interface 115d / l 16d / l 17d (not shown in the figures), which maybe any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115d / l 16d / l 17d may be established using any suitable radio access technology- (RAT).

[0068] More specifically, as noted above, 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 RSUs 120a, 120b, in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d, 102e. 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 or 115c / l 16c / l 17c respectively using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed Uplink Packet Access (HSUPA).

[0069] In some cases, the base station 114a and the WTRUs 102a, 102b, 102c, or RRHs 118a, 118b, TRPs 119a, 119b, and / or RSUs 120a, 120b, in the RAN 103b / 104b / 105b and theCNV15059W001 (101859.002201)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). In the future, the air interface 115 / 116 / 1 17 may implement 3GPP NR technology. The LTE and LTE-A technology includes LTE D2D and V2X technologies and interface (such as Sidelink communications, etc.) The 3GPP NR technology7includes NR V2X technologies and interface (such as Sidelink communications, etc.)

[0070] In some cases, 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, 120b, in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d, 102e, 102f may implement radio technologies such as IEEE 802.16 (e.g., Worldwide Interoperability7for 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.

[0071] The base station 114c in FIG. 7A 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 connectivity7in a localized area, such as a place of business, a home, a vehicle, a campus, and the like. In some cases, the base station 114c and the WTRUs 102e, may implement a radio technology such as IEEE 802. 11 to establish a wireless local area network (WLAN). In some cases, the base station 114c and the WTRUs 102d, may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In some cases, the base station 114c and the WTRUs 102e, may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell. As shown in FIG. 7 A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114c may not be required to access the Internet 1 10 via the core network 106 / 107 / 109.

[0072] The RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b may be in communication with the core network 106 / 107 / 109. which may be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may provide call control, billing services, mobile location-based services, pre-paid calling,CNV15059W001 (101859.002201)Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication.

[0073] Although not shown in FIG. 7A, it will be appreciated that the RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b and / or the core network 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 / 105b, 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 radio technology.

[0074] The core network 106 / 107 / 109 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d, 102e to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include 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 networks 112 may include wired or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 may include another core network 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.

[0075] Some or all of the WTRUs 102a. 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities, e.g., the WTRUs 102a, 102b, 102c, 102d, and 102e may include multiple transceivers for communicating with different wireless networks over different wireless links. For example, the WTRU 102e show n in FIG. 7A 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.

[0076] FIG. 7B is a block diagram of an example apparatus or device configured for wireless communications in accordance with the aspects illustrated herein, such as for example, a WTRU 102. As shown in FIG. 7B, the example WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 113, a display / touchpad / indicators 128, non-removable memory 130, removableCNV15059W001 (101859.002201) memory 132, a power source 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an example. Also, in some cases the base stations 114a and 114b, and / or the nodes that base stations 1 14a and 114b may represent, such as but not limited to transceiver station (BTS), aNode-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, and proxy nodes, among others, may include some or all of the elements depicted in FIG. 7B and described herein.

[0077] 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 functionality7that 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 transmit / receive element 122. While FIG. 7B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0078] The transmit / receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 115 / 116 / 117. For example, in some cases, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In some cases, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In some cases, the transmit / receive element 122 may be configured to transmit and receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0079] In addition, although the transmit / receive element 122 is depicted in FIG. 7B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in some cases, theCNV15059W001 (101859.002201)WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 115 / 116 / 117.

[0080] 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 include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as UTRA and IEEE 802. 11. for example.

[0081] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 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 / microphone 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 type of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other t pe of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory' card, and the like. In some cases, 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 or a home computer (not shown).

[0082] 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 include one or more dry cell batteries, solar cells, fuel cells, and the like.

[0083] 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, 1 14b) and / or determine its location based on the timing of the signals being received from two or more nearby base stations. It will beCNV15059W001 (101859.002201) appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an aspect.

[0084] The processor 118 may further be coupled to other peripherals 138, which may include 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 include 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 universal 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.

[0085] The WTRU 102 may be embodied 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 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.

[0086] FIG. 7C is a system diagram of the RAN 103 and the 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 FIG. 7C. the RAN 103 may include Node-Bs 140a. 140b, 140c, which may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 115. The Node-Bs 140a, 140b, 140c may each be associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a, 142b. It will be appreciated that the RAN 103 may include any number of Node-Bs and RNCs while remaining consistent with an aspect of the disclosure.

[0087] As shown in FIG. 7C, 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, 140c may communicate with the respective RNCs 142a, 142b via an lub interface. The RNCs 142a, 142b may be in communication with one another via an lur interface. Each of the RNCs 142a, 142b may be configured to control the respective Node-Bs 140a, 140b, 140c to which it is connected. In addition, each of the RNCs 142a, 142b may beCNV15059W001 (101859.002201) 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.

[0088] The core network 106 shown in FIG. 7C may include 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 will be appreciated that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0089] 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, 102c with access to circuit-switched networks, such as the PSTN 108. to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.

[0090] 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, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between and the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0091] As noted above, the core network 106 may also be connected to the networks 112, which may include other wired or wireless networks that are owned and / or operated by other service providers.

[0092] FIG. 7D is a system diagram of the RAN 104 and the 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 116. The RAN 104 may also be in communication with the core network 107.

[0093] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an aspect of the disclosure. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In some cases, the eNode-Bs 160a, 160b, 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.CNV15059W001 (101859.002201)

[0094] 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 downlink, and the like. As shown in FIG. 7D, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0095] The core network 107 shown in FIG. 7D may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. While each of the foregoing elements are depicted as part of the core network 107, it will be appreciated that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0096] 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, 102c, bearer activation / deactivation, selecting a particular serving gatew ay during an initial attach of the WTRUs 102a, 102b, 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.

[0097] 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, 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, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0098] The serving gateway 164 may also be connected to the PDN gateway 166, which may provide the WTRUs 102a, 102b, 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.

[0099] The core netw ork 107 may facilitate communications with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the core netw ork 107 may include, or may communicate with, an IP gateway (e.g., an IPCNV15059W001 (101859.002201) 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, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and / or operated by other service providers.

[0100] FIG. 7E is a system diagram of the RAN 105 and the core network 109. The RAN 105 may be an access service network (ASN) that employ s IEEE 802.16 radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 117. As will be further discussed below, the communication links between the different functional entities of the WTRUs 102a, 102b, 102c, the RAN 105, and the core network 109 may be defined as reference points.

[0101] As shown in FIG. 7E, the RAN 105 may include base stations 180a, 180b, 180c, and an ASN gateway 182, though it will be appreciated that the RAN 105 may include any number of base stations and ASN gateways while remaining consistent with an aspect of the disclosure. The base stations 180a, 180b, 180c may each be associated with a particular cell in the RAN 105 and may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 117. In some cases, the base stations 180a, 180b, 180c may implement MIMO technology. Thus, the base station 180a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a. The base stations 180a, 180b, 180c may also provide mobility management functions, such as handoff triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, and the like. The ASN gateway 182 may serve as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to the core network 109, and the like.

[0102] The air interface 117 betw een the WTRUs 102a, 102b, 102c and the RAN 105 may be defined as an R1 reference point that implements the IEEE 802.16 specification. In addition, each of the WTRUs 102a, 102b, and 102c may establish a logical interface (not shown) with the core netw ork 109. The logical interface betw een the WTRUs 102a, 102b, 102c and the core netw ork 109 may be defined as an R2 reference point, which may be used for authentication, authorization, IP host configuration management, and / or mobility management.

[0103] The communication link betw een each of the base stations 180a, 180b, and 180c may be defined as an R8 reference point that includes protocols for facilitating WTRUCNV15059W001 (101859.002201) handovers and the transfer of data between base stations. The communication link between the base stations 180a, 180b, 180c and the ASN gateway 182 may be defined as an R6 reference point. The R6 reference point may include protocols for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 102c.

[0104] As shown in FIG. 7E, the RAN 105 may be connected to the core network 109. The communication link between the RAN 105 and the core netw ork 109 may defined as an R3 reference point that includes protocols for facilitating data transfer and mobility management capabilities, for example. The core network 109 may include a mobile IP home agent (MIP-HA) 184, an authentication, authorization, accounting (AAA) server 186, and a gatew ay 188. While each of the foregoing elements are depicted as part of the core netw ork 109, it will be appreciated that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0105] The MIP-HA may be responsible for IP address management, and may enable the WTRUs 102a, 102b, and 102c to roam betw een different ASNs and / or different core networks. The MIP-HA 184 may provide the WTRUs 102a, 102b, 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. The AAA server 186 may be responsible for user authentication and for supporting user services. The gateway 188 may facilitate interworking with other netw orks. For example, the gatew ay 188 may provide the WTRUs 102a. 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a. 102b, 102c and traditional land-line communications devices. In addition, the gateway 188 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and / or operated by other senice providers.

[0106] Although not shown in FIG. 7E, it will be appreciated that the RAN 105 may be connected to other ASNs and the core network 109 may be connected to other core networks. The communication link between the RAN 105 the other ASNs may be defined as an R4 reference point, which may include protocols for coordinating the mobility of the WTRUs 102a. 102b, 102c between the RAN 105 and the other ASNs. The communication link between the core network 109 and the other core netw orks may be defined as an R5 reference, which may include protocols for facilitating interw orking betw een home core networks and visited core netw orks.CNV15059W001 (101859.002201)

[0107] The core network entities described herein and illustrated in FIGs 7A, 7C, 7D, and 7E 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 FIGs 7A, 7B, 7C, 7D, and 7E 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.

[0108] FIG. 7F is a block diagram of an exemplary' computing system 90 in which one or more apparatuses of the communications networks illustrated in FIGs 7 A, 7C, 7D and 7E 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, or Other Networks 112. 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.

[0109] 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 sy stem bus connects the components in computing system 90 and defines the medium for data exchange. System bus 80 typically includes data lines for sending data, address lines for sending addresses, and control lines for sendingCNV15059W001 (101859.002201) interrupts and for operating the system bus. An example of such a system bus 80 is the PCI (Peripheral Component Interconnect) bus.

[0110] Memories coupled to system bus 80 include random access memory (RAM) 82 and read only memory (ROM) 93. Such memories include circuitry that allows information to be stored and retrieved. ROMs 93 generally contain stored data that cannot 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 cannot access memory within another process’s virtual address space unless memory sharing between the processes has been set up.

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

[0112] Display 86, which is controlled by display controller 96, is used to display visual output generated by computing system 90. Such visual output may include 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 includes electronic components required to generate a video signal that is sent to display 86.

[0113] Further, computing system 90 may contain communication circuitry, such as for example a network adapter 97, that may be used to connect computing system 90 to an external communications network, such as the RAN 103 / 104 / 105, Core Network 106 / 107 / 109, PSTN 108, Internet 110, or Other Networks 112 ofFIGs 7A, 7B, 7C, 7D, and 7E, to enable the computing system 90 to communicate with other nodes or functional entities of those networks. The communication circuitry, alone 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.CNV15059W001 (101859.002201)

[0114] FIG. 7G illustrates an example communications system 111 in which the methods and apparatuses described and claimed herein may be an aspect of. As shown, the example communications system 111 may include wireless transmit / receive units (WTRUs) A, B, C, D, E, F, a base station, a V2X server, and a RSUs A and B, though it will be appreciated that the disclosure contemplates any number of WTRUs, base stations, networks, and / or network elements. One or several or all WTRUs A, B, C, D, E can be out of range of the netw ork (for example, in the figure out of the cell coverage boundary shown as the dash line). WTRUs A. B, C form a V2X group, among which WTRU A is the group lead and WTRUs B and C are group members. WTRUs A, B, C, D, E, F may communicate over Uu interface or Sidelink (PC 5) interface.

[0115] 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 a processor, such as processors 118 or 91, cause the processor 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 of an apparatus or computing system configured for wireless and / or wired network communications. Computer readable storage media include 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 include signals. Computer readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology7, 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

[0116] Provided below are definitions for abbreviations found w ithin the body of the disclosure.CNV15059W001 (101859.002201)

[0117] Provided below are definitions for terms found within the body of the disclosure.CNV15059W001 (101859.002201)CNV15059W001 (101859.002201)

Claims

CNV15059W001 (101859.002201)What is claimed:

1. An apparatus comprising: one or more processors; memory storing a set of computer-executable instructions that, when executed by the one or more processors, cause: receiving, from an application server (AS), a sensing group request comprising one or more sensing service request parameters; initiating a process for generating a sensing group comprising at least one sensing device; wherein the process for generating the sensing group comprises: discovering one or more sensing devices in a target range; and selecting the at least one sensing device from the discovered one or more sensing devices; and receiving, from the sensing group, information indicative of sensing data collected from the sensing group.

2. The apparatus of claim 1 , wherein the process for generating the sensing group further comprises: configuring the selected at least one sensing device according to one or more sensing parameters.

3. The apparatus of claim 1, wherein the set of computer-executable instructions, when executed by the one or more processors, further cause: sending, to the AS, sensing results corresponding to the sensing data collected from the sensing group.

4. The apparatus of claim 1, wherein the one or more sensing sen ice request parameters comprise: a sensing depth parameter; a sensing perspective parameter; a sensing precision level parameter; a sensing confidence level parameter; a minimum number of sensing devices parameter;CNV15059W001 (101859.002201) a number of successive sensing measurements parameter; a number of successive sensing data parameter; a sensing duration parameter; a measurement window parameter; a statistical function parameter; a group collaboration window parameter; an expiration parameter; or a combination thereof.

5. The apparatus of claim 1, wherein the process for generating a sensing group is based on the one or more sensing service request parameters.

6. The apparatus of claim 1, wherein the selecting is based on one or more characteristics of a target object or target environment.

7. The apparatus of claim 1, wherein the information indicative of the sensing data comprises collaborative sensing result data; or wherein the set of computer-executed instructions, when executed by the one or more processors; further cause: generating, based on the information indicative of the sensing data, collaborative sensing result data.

8. A wireless transmit / receive unit (WTRU), comprising: one or more processors; and memory' storing a set of computer-executable instructions that, when executed by the one or more processors, cause: receiving sensing configuration information for a collaborative sensing operation; performing one or more sensing measurements according to a configured collaborative sensing measurement window; generating sensing data comprising at least one of a timestamp, an orientation of the WTRU, or a location of the WTRU; synchronizing the sensing data with a known time source to enable time-aligned sensing with one or more other sensing devices; andCNV15059W001 (101859.002201) transmitting the sensing data to a network function or another sensing device for generation of collaborative sensing results.

9. The WTRU of claim 8, wherein the set of computer-executable instructions, when executed by the one or more processors, further cause: receiving, from a network function or an application server, sensing configuration information associated with a collaborative sensing operation, wherein the sensing configuration information comprises one or more of: a target sensing area; one or more requested sensing characteristics; a sensing depth; one or more sensing perspectives; a sensing precision level; a sensing confidence level; a measurement window; a group collaboration window; a number of successive sensing measurements; a number of successive data; or an expiration for the sensing configuration.

10. The WTRU of claim 8, wherein the set of computer-executable instructions, when executed by the one or more processors, further cause performing, based on the sensing configuration information, the one or more sensing measurements within measurement window-.1 1. The WTRU of claim 8, wherein the set of computer-executable instructions, when executed by the one or more processors, further cause synchronizing, prior to or during the one or more sensing measurements, an internal time reference for the WTRU with the known time source to enable the time-aligned sensing with the one or more other sensing devices, and wherein the one or more other sensing devices are participating in the collaborative sensing operation.CNV15059W001 (101859.002201)12. The WTRU of claim 8, wherein the sensing data further comprises a confidence level associated with the sensing data.

13. The WTRU of claim 8, wherein the set of computer-executable instructions, when executed by the one or more processors, further cause: applying a statistical function to a set of successive sensing measurements collected within the collaborative sensing measurement window to generate the sensing data.

14. The WTRU of claim 8, wherein the set of computer-executable instructions, when executed by the one or more processors, further cause: receiving, from one of the one or more sensing devices, additional sensing data; and transmitting the additional sensing data to the network function or the another sensing device.

15. A method comprising: receiving, by a wireless transmit / receive unit (WTRU), sensing configuration information for a collaborative sensing operation; performing, by the WTRU, one or more sensing measurements according to a configured collaborative sensing measurement window; generating, by the WTRU, sensing data comprising at least one of a timestamp, an orientation of the WTRU, or a location of the WTRU; synchronizing, by the WTRU, the sensing data with a known time source to enable time-aligned sensing with one or more other sensing devices; and transmitting, by the WTRU, the sensing data to a network function or another sensing device for generation of collaborative sensing results.

16. The method of claim 15, further comprising: receiving, by the WTRU and from a network function or an application server, sensing configuration information associated with a collaborative sensing operation, wherein the sensing configuration information comprises one or more of: a target sensing area; one or more requested sensing characteristics;CNV15059W001 (101859.002201) a sensing depth; one or more sensing perspectives; a sensing precision level; a sensing confidence level; a measurement window; a group collaboration window; a number of successive sensing measurements; a number of successive data; or an expiration for the sensing configuration.

17. The method of claim 15, further comprising performing, based on the sensing configuration information, the one or more sensing measurements within measurement window.

18. The method of claim 15, further comprising synchronizing, prior to or during the one or more sensing measurements, an internal time reference for the WTRU with the know n time source to enable the time-aligned sensing with the one or more other sensing devices, and wherein the one or more other sensing devices are participating in the collaborative sensing operation.

19. The method of claim 15. wherein the sensing data further comprises a confidence level associated with the sensing data.

20. The method of claim 15, further comprising: applying, by the WTRU, a statistical function to a set of successive sensing measurements collected within the collaborative sensing measurement window' to generate the sensing data.

Images