Sensing UE, detection and consent

Abstract

Disclosed herein is method performed by a sensing controller (502) for identifying user equipment devices, UEs, to perform UE-assisted sensing. The method comprises: receiving (302) a first indication indicating whether UE-assisted sensing is allowed at a UE (402); receiving (304) a second indication indicating that UE-assisted sensing is allowed by a subscription owner of the UE (402); and in response to both the first indication and the second indication indicating that UE-assisted sensing is allowed, adding (306) the UE (402) to a registry of UE-assisted sensing enabled UEs at the sensing controller (502).

Description

Applicant's Ref: P113217WO01 1SENSING UE, DETECTION AND CONSENTTECHNICAL FIELD

[0001] The present disclosure relates to methods for identifying a User Equipment (UE) to perform UE-assisted sensing in a wireless communications system.BACKGROUND

[0002] Integrated Communication And Sensing (ISAC) is a key technology with many envisioned use cases positioned for Sixth Generation (6G), even if study work is already ongoing in Third Generation Partnership Program (3GPP) for Fifth Generation (5G) Advanced. The work so far has very much been focused on the radio signaling and analysis of different models for re-using or adding signals between a base station and / or a User Equipment (UE) plus some architecture aspects related to the control plane (CP).

[0003] ISAC is an integrated part of the communication network, where Sensing, according to European Telecommunication Standards Institute (ETSI), refers to the use of radio signals to detect and estimate characteristics of target objects in the environment. By integrating sensing into the communications network, the network acts as a "radar” sensor, using its own radio signals to sense and comprehend the physical world in which it operates. This allows the network to collect data on the range, velocity, position, orientation, size, shape, image, materials of objects and devices. Sensing is not aware or centered around users at all but around anonymous environment and equipment, i.e., it is UE / user agnostic.

[0004] By contrast, positioning, according to ETSI 38.305, provides the mechanisms to support or assist the calculation of the geographical position of a UE. UE position knowledge can be used, for example, in support of Radio Resource Management functions, as well as location-based services for operators, subscribers, and third-party service providers. UE Positioning may be considered as a network-provided enabling technology consisting of standardized service capabilities that enable the provision of location applications. The applications) may be service provider specific. Positioning is UE centric where the geographical position of a user (or rather the UE holding the USIM) is requested / provided. Sensing data can be leveraged to possibly increase accuracy of positioning i.e., UE / User specific. TFigures 1A and 1B

[0005] The differences are illustrated in Figures 1Aand 1 B, where 1 Ashows positioning functionality with a UE in a car sending out active signals to nearby base stations, and where in Figure 1B, which shows sensing, a base station emits a signal that reflects off the car, and the nearby base stations sense / detect the passive reflections off of the car in order to sense the car.

[0006] With that said there are aspects related to Sensing where dependencies on specific UE and User data is needed, i.e., UE Assisted sensing where any capable UE could be used as SU, Sensing Unit.Figures 2A and 2BThere are also a few actors which impacts the solution from a privacy perspective, and this is shown in Figures 2A and 2B, where in Figure 2A, the end user needs to consent (unless CSP deployed UE) to be an assistant in the sensingApplicant's Ref: P113217WO01 2operation, whereas in Figure 2B the subscription owner may need to consent for its equipment to be used as assistant in the sensing operation.

[0007] Some additional definitions used:• Assisting UE: UE which is also a Sensing Unit (SU).• Object detection: identify and locate an object.• Object tracking: continuous monitoring of objects' positions and trajectories.• Sensing: Wireless sensing is a technology enabler to acquire information about characteristics of the environment and / or objects within the environment, that uses radio frequency to determine the distance (range), angle, or instantaneous linear velocity of objects, etc.• Sensing Unit: sensing capable Radio Access Network (RAN) entities and UEs having the capability to send and receive sensing radio signals used for ISAC as well as reporting measurement results.• Sensing 6G-NB is supporting SU Tx, SU Rx, and / or SU RxTx.• Serving 6G-NB provides connectivity for the assisting UE.SUMMARY

[0008] In an embodiment, a method is provided for a sensing controller to identify a User Equipment (UE) that is capable of and allowed to perform UE-assisted sensing. In an embodiment, the sensing controller can receive a first indication indicating whether UE-assisted sensing is allowed at a UE. The first indication can be signaled in a dedicated information element from the UE to the sensing controller, where a positive indication indicates that the UE is allowed to perform UE-assisted sensing, and a negative indication, or lack of information element, indicates the UE is not allowed. The sensing controller can also receive a second indication indicating that UE-assisted sensing is allowed by the subscription owner of the UE. If both indications indicate the UE-assisted sensing is allowed, the sensing controller can add the UE to a registry of UE-assisted sensing enabled UEs.BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.Figures 1A and 1B show examples of positioning and sensing in accordance with some embodiments of the present disclosure;Figures 2A and 2B show examples of subscription owners and involved parties in accordance with some embodiments of the present disclosure;Figure 3 shows a flowchart of a method for identifying UEs for UE-assisted sensing in accordance with some embodiments of the present disclosure;Figure 4 shows a message sequence chart of a method for a UE storing its consent level in a core network in accordance with some embodiments of the present disclosure;Figure 5 shows a block diagram depicting consent logic and indications in accordance with some embodiments of the present disclosure;Applicant's Ref: P113217WO01 3Figure 6 shows a block diagram of an architecture of a UE-assisted sensing communications system in accordance with some embodiments of the present disclosure;Figure 7 shows an example of a communication system in accordance with some embodiments of the present disclosure;Figure 8 is another example of a communication system according to some embodiments of the present disclosure; Figure 9 shows a wireless device, which may be configured to operate in the communication system of Figure 7 or in the communication system of Figure 8;Figure 10 shows a network node in accordance with some embodiments of the present disclosure; andFigure 11 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.DETAILED DESCRIPTION

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

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

[0012] There currently exist certain challenge(s). There is a lack of an End to End (e2e) architecture description involving the coordination about Assisting User Equipment (UE) and their privacy. There’s also no method to inform the Radio Access Network (RAN) about which UEs that are capable and allowed as acting as sensing units (SU) in UE-assisted sensing, and there’s no current method described for the subscription owners to consent to being part of a sensing task.

[0013] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. In an embodiment, a method is provided for a sensing controller to identify User Equipments (UEs) that are capable of and allowed to perform UE-assisted sensing. In an embodiment, the sensing controller can receiving a first indication indicating whether UE-assisted sensing is allowed at a UE. The first indication can be signaled in a dedicated information element from the UE to the sensing controller, where a positive indication indicates that the UE is allowed to perform UE-assisted sensing, and a negative indication, or lack of information element, indicates the UE is not allowed. The sensing controller can also receive a second indication indicating that UE-assisted sensing is allowed by the subscription owner of the UE. If both indications indicate the UE-assisted sensing is allowed, the sensing controller can add the UE to a registry of UE-assisted sensing enabled UEs.

[0014] The present disclosure provides a framework that provides the two most important actors, end users and subscription owners, the possibility to consent to being part of the sensing tasks. The procedures here are performed in the RAN without explicit packet core impacts. In an embodiment, some of the features disclosed herein includes:Applicant's Ref: P113217WC01 4• Toggle in the UE that consent to being used as an SU during a sensing job.• Communication between the UE and 6G-NB / gNB that informs RAN about:o the UE capability.o the willingness by the end user to participate.• Information and communication that prevents sensing operation from a subscription owner perspective. • Information and coordination that prevents sensing operation from a location perspective.• Procedures that make all information available in RAN, without explicit Packet Core impact.

[0015] Certain embodiments may provide one or more of the following technical advantage(s):• Protect the privacy for the end user in a sensing job.• Protect the subscription owner in a sensing job.• Solution piggybacks on existing procedures and messages.• If the sensing related subscription data is updated while the UE is registered a normal procedure will be initiated where the sensing information re-uses the same procedure but includes new information in the existing messages.• Separation of concern between the new Sensing function and the legacy Packet Core is maintained.• Figures 2A and 2BFigure 3

[0016] Figure 3 shows a flowchart of a method for identifying UEs for UE-assisted sensing in accordance with some embodiments of the present disclosure;

[0017] At step 302, the method includes receiving a first indication indicating whether UE-assisted sensing is allowed at a UE 402.

[0018] In an embodiment, the first indication is received from the UE 402 via a Radio Resource Control (RRC) message and the first indication can be included in a dedicated information element.

[0019] In an embodiment, the first indication can be received from a core network node such as a Unified Data Management (UDM) 408.

[0020] In an embodiment, an absence of the dedicated information element in the RRC message indicates that UE-assisted sensing is not allowed at the UE.

[0021] At step 304, the method includes receiving a second indication indicating that UE-assisted sensing is allowed by a subscription owner of the UE 402.

[0022] In an embodiment, the second indication can be received from a core network node such as UDM 408.

[0023] In another embodiment, the first indication and second indication are a single indication received from the UDM 408.

[0024] At step 306, the method includes in response to both the first indication and the second indication indicating that UE-assisted sensing is allowed, adding the UE 402 to a registry of UE-assisted sensing enabled UEs at the sensing controller.Applicant's Ref: P113217WC01 5

[0025] At step 308, the method includes providing to a core network node, a third indication that UE-assisted sensing is allowed at the UE 402. In an embodiment, the third indication is provided via a Next Generation Application Protocol (NGAP) message. In an embodiment, the core network node could be an Access and Mobility Management Function 406.

[0026] In an embodiment, the UE 402 has a built-in switch that could be toggled by either the end user locally on the UE 402 or the UE Admin service could do it remotely (operator controlled or enterprise); so that RRC or Non-Access Stratum (NAS) information is influenced.• If the switch is "Sensing Allowed” then sensing capability is indicated to RAN over RRC, alternatively, this capability is indicated to the CN in NAS. If provided to RAN in RRC, then this can be indicated to the CN in the message (e.g., NGAP) to the CN.• If the switch is "Sensing not Allowed” then sensing capability is not indicated over RRC or over NAS.• If the switch is missing / not supported then RRC or NAS should not include the "Sensing Allowed” Information Element.

[0027] In an embodiment, the "Sensing Allowed” could be signaled explicitly (as its own information element (complementing the sensing capability information element) or implicitly as described in the three bullets above. If explicitly signaled, the capability could be permanent (and indicate "not capable” when the device lacks the sensing capability).Figure 4

[0028] Figure 4 shows a message sequence chart of a method for a UE storing its consent level in a core network in accordance with some embodiments of the present disclosure. In an embodiment. The UE support can support a similar function as the Privacy Profile management as described in 3GPP TS 23.273 (where Figure 6.12.1-1 from the technical specification is reproduced as Figure 4 in the present disclosure) where the UE can store its wanted consent level directly in a Unified Data Repository (UDR) such as a UDM 408.

[0029] At step 412, the NF 410 subscribes to UDM 408 notifications of UE LCS privacy profile updates.

[0030] At step 414, the UE 402 sends the UE location privacy indication to the AMF 406 via UE location Privacy Setting Request in N1 NAS message.

[0031] At step 416, the AMF 406 invokes a Nudm_ParameterProvision_Update service operation towards the UDM 408 and the service operation carries the Location privacy indication information and may include event reporting expected area and the area usage indication. The UDM 408 stores or updates the UE LCS privacy profile in the UDR by invoking Nudr_DM_Update (SUPI, Subscription Data) service operation accordingly.

[0032] At step 418, the AMF 406 responds to the UE via UE Location Privacy Setting Response in N1 NAS message.

[0033] At step 420, the UDM 408 notifies the subscribed Network Function 410 (e.g., GMLC, NEF) of the updated UE LCS privacy profile via Nudm_SDM_Notification Notify message.

[0034] At step 422, the NF 410 may unsubscribe to UDM notification if a deferred location procedure is cancelled.

[0035] In an embodiment, existing consent management in the Service Exposure Layer (SEP) could be extended and used for external Sensing exposure tasks.Applicant's Ref: P113217WO01 6Figures 5 and 6

[0036] Figure 5 shows a block diagram depicting consent logic and indications in accordance with some embodiments of the present disclosure, and should be viewed alongside Figure 6 which shows a block diagram of an architecture of a UE-assisted sensing communications system in accordance with some embodiments of the present disclosure;

[0037] The UE 402 indicates its willingness and capability to assist in sensing to the Sensing Controller 502 in the 6G-RAN. The AMF 406 receives an indication as to whether the UE is allowed to assist in sensing from the UDM 408 and indicates sensing allowed to the 6G-RAN and sensing controller 502. The sensing controller 502 includes the UE as an assisting UE into its registry if the UE 402 is allowed and willing to assist in assisting.

[0038] The messages between AMF 406 and UDM 408 can include an extended version of the Access and Mobility Subscription Data which then includes e.g., a sensing allowed Boolean.

[0039] The UE context stored in the AMF 406 needs to host and transfer this data, sensing allowed Boolean, to any new AMF (caused by e.g., mobility).

[0040] The information (sensing allowed Boolean) can be sent from the AMF 406 to the gNB / 6G-NB during the Registration procedure (or alternatively in the UE Context Update procedure.

[0041] The following tables show the logic that the sensing controller 502 uses in determining whether the UE 402 is available for sensing. Table 1 shows the logic the sensing controller 502 uses to determine whether the UE 402 indicates it is willing to assist, and Table 2 incorporates the second indication from subscription owner.

[0042] Table 1:I T LOGIC RRC PART i i: CAPABLI: \\i) SENSING RAN INTERPRETATION WILLING TO ASSIS I CAPABILITY CAPABLE WILLING RLSULT SETTINGAbsent No N / A NoExist - set to “NO” Yes No NoExist - set to “YES Yes Yes No

[0043] Table 2:SL\SI\G UNIT LOGICUE CAPABLE AND USIM ALLOWS UE TO UE ACTIVE PART AS AN WILLING TO ASSIST ASSIST SUYes Yes YesYes No NoNo Yes NoNo No No0044] If the UE can be an active part as a Sensing Unit (SU), this information is to be stored in the UE Context in RAF (which can be the same as the SU registry, extended with UE details).Applicant's Ref: P113217WO01 7

[0045] It is populated by extending the existing procedures over RRC with an indication to cover the UE willingness and Capability aspect, then the NGAP message Initial Context Setup Request is extended to include the subscription data aspects (information provided to the RAN). That way no new procedures or messages are needed to convey the information to RAN AND the separation of concern is maintained.

[0046] In another option, when the UE Context in AMF includes indication that the UE is willing to participate in sensing (received from the UE via NAS), the AMF queries RAN for UE sensing capability support which can be included in the UE Radio Capability. Based on the query result, the AMF can update the UE Context in RAN to indicate that UE is willing, capable, and allowed to participate in sensing using NGAP UE Context Modification Request. Or, alternatively, simply indicate that the UE is allowed (require both willing and allowed) to the RAN (with or without querying the RAN for the capability) and the RAN filter away any UE that is allowed but not capable.Figure 7

[0047] Figure 7 shows an example of a communication system 700 in accordance with some embodiments.

[0048] In the example, the communication system 700 includes a telecommunications network 702 that includes an access network 704, such as a radio access network (RAN), and a core network 706, which includes one or more core network nodes 708. The access network 704 includes one or more access network nodes or base stations of various types, access network nodes 710A and 710B are depicted (which may be collectively referred to as network nodes 710), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 704 may include more than one access network technology. The network nodes 710 of access network 704 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 712A, 712B, 712C, and 712D (one or more of which may be generally referred to as UEs 712) to the core network 706 over one or more wireless connections.

[0049] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 702 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 702 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 702, including one or more access network nodes 710 and / or core network nodes 708.

[0050] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective "open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may beApplicant's Ref: P113217WO01 8implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies.

[0051] The network nodes 710 facilitate direct or indirect connection of one or more UEs 712 to the core network 706 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 700 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 700 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0052] The UEs 712 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 710 and other communication devices. Similarly, the network nodes 708, 710 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 702) with the UEs 712 and / or with other network nodes or equipment in the telecommunications network 702 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 702. More specifically, UEs 712 may send messages, data, and / or other signals to network nodes 708, 710 or other elements of the telecommunications network 702 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 708, 710 may send messages, data, and other signals to UEs 7122, other network nodes 708, 710, and other devices in telecommunications network 702 directly or indirectly. As one specific example, a core network node 708 may transmit a particular message to a UE 712 by transmitting the message to an access network node 710 that will then transmit the message to the intended UE 712. Similarly, a core network node 708 may receive a particular message from a UE 712 by receiving the message from an access network node 710 that itself received the message from the UE 712.

[0053] In the depicted example, the core network 706 connects elements of the access network 704 (e.g., one or more of the network nodes 710) to one or more host computing systems, such as host 716. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 706 includes one or more core network nodes (e.g., core network node 708) of various types, one or more of which may be generally referred to as network nodes 708. Network nodes 708 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 708. Example core network nodes provideApplicant's Ref: P113217WC01 9functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

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

[0055] As a whole, the communication system 700 of Figure 7 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 700 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 700 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 700 supporting different standards, protocols, or rule sets.

[0056] As one example, in certain embodiments, access network 704 may contain some access network nodes 710 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 710 support (or the same access network nodes 710 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 702 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 704 and / or a core network 706 that supports multiple different standard generations or may include multiple access networks 704 and / or multiple core networks 706 with individual networks 704, 706 supporting different standard generations.

[0057] Telecommunications network 702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 702. For example, the telecommunications network 702 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.Applicant's Ref: P113217WO01 10

[0058] In some examples, one or more of the UEs 712 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 704. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0059] In the example, the hub 714 communicates with the access network 704 to facilitate indirect communication between one or more UEs (e.g., UE 712C and / or 712D) and network nodes (e.g., network node 710B). In some examples, the hub 714 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 714 may be a broadband router enabling access to the core network 706 for the UEs. As another example, the hub 714 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 710, or by executable code, script, process, or other instructions in the hub 714.

[0060] As another example, the hub 714 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 714 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 714 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 714 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 714 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0061] The hub 714 may have a constant / persistent or intermittent connection to the network node 710B. The hub 714 may also allow for a different communication scheme and / or schedule between the hub 714 and UEs (e.g., UE 712C and / or 712D), and between the hub 714 and the core network 706. In other examples, the hub 714 is connected to the core network 706 and / or one or more UEs via a wired connection. Moreover, the hub 714 may be configured to connect to an M2M service provider over the access network 704 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 710 while still connected via the hub 714 via a wired or wireless connection. In some embodiments, the hub 714 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 710B. In other embodiments, the hub 714 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 710B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.Figure 8

[0062] Figure 8 is another example of a communication system 800 according to some embodiments. As used herein, the communication system 800 includes multiple access points (APs) 810 (with four exemplary APs 810A, 810B, 810C, and 810D being depicted) and multiple wireless devices, referred to in the context of communication system 800 as stations (STAs) 812 (referred to individually as STA 812A, STA 812B, STA 812C, STA 812D, and STA 812E). STAApplicant's Ref: P113217WO01 11812A is served by AP 810A in a first basic service set (BSS) 820A. STA 81 OB and STA 810C are served by AP 81 OB in a second BSS, BSS 820B. STA 812D is served by AP 81 OC in a third BSS, BSS 820C. STA 812E is served by AP 81 OD in a fourth BSS, BSS 820D. Stations 812 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 812 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0063] Each of STAs 812 may connect through a radio link to one of APs 810. For example, depending on location or channel conditions experienced by a given STA 812, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0064] Each AP 810 may provide data connectivity to STAs 812 connected to a particular AP 810. As illustrated, APs 810 may be connected to a data network 830. In this way, APs 810 may also provide data connectivity between STAs 812 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 812 and its serving AP 810 may be used for providing various kinds of services to STA 812, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 812 and / or on a device linked to STA 812. By way of example, Figure 8 illustrates an application service platform 832 provided in data network 830. The application(s) executed on STA 812 and / or on one or more other devices linked to STA 812 may use the radio link for data communication with one or more other STA 812 and / or the application service platform 832, thereby enabling utilization of the corresponding service(s) at STA 812.Figure 9

[0065] Figure 9 shows a wireless device 900, which may be configured to operate in communication system 700 of Figure 7 or in communication system 800 of Figure 8. The wireless device 900 may be alternatively referred to as a UE 900, like a UE 712 within the context of communication system 700, or as a station (STA) 900 or as a non-access-point station (non-AP STA) 900, like a STA 812 within the context of the communication system 800, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.Applicant's Ref: P113217WO01 12

[0066] A wireless device 900 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 900 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 900 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 900 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0067] In particular embodiments, wireless device 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input / output interface 906, a power source 908, a memory 910, a communication interface 912, and / or any other component, or any combination thereof. Certain embodiments of wireless device 900 may include all or a subset of the components shown in Figure 9. The level of integration between the components may vary from one embodiment of wireless device 900 to another. In general, in a particular embodiment of wireless device 900, processing circuitry 902, input / output interface 906, power source 908, memory 910, and communication interface 912 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 900. Further, certain embodiments of wireless devices 900 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0068] The processing circuitry 902 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 910. The processing circuitry 902 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 902 may include multiple central processing units (CPUs).

[0069] In the example, the input / output interface 906 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 900. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.Applicant's Ref: P113217WO01 13

[0070] In some embodiments, the power source 908 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 908 may further include power circuitry for delivering power from the power source 908 itself, and / or an external power source, to the various parts of wireless device 900 via input circuitry or an interface such as an electrical power cable. Power source 908 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 900 to which power is supplied.

[0071] The memory 910 may be or be configured to include memory such as random access memory (RAM), readonly memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 910 includes one or more programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916. The memory 910 may store, for use by wireless device 900, any of a variety of various operating systems or combinations of operating systems.

[0072] The memory 910 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (IUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 910 may allow wireless device 900 to access instructions, programs, and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 910, which may be or comprise a device-readable storage medium.

[0073] The processing circuitry 902 may be configured to communicate with an access network or other network via or using the communication interface 912. The communication interface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 922. The communication interface 912 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 918 and / or a receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., antenna 922) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0074] In the illustrated embodiment, communication functions of the communication interface 912 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication,Applicant's Ref: P113217WO01 14data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0075] In particular embodiments, wireless device 900 may provide an output of data captured via a sensor, through its communication interface 912, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 900 can be communicated through a wireless connection to a network node via another wireless device 900. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0076] As another example, wireless device 900 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 900 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0077] Wireless device 900, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 900 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 900 shown in Figure 9.

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

[0079] In practice, any number of wireless devices 900 may be used together with respect to a single use case. For example, a first wireless device 900 might be or be integrated in a drone and provide the drone's speed information (obtained through a speed sensor) to a second wireless device 900 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 900 may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or the second wireless device 900 can also include more than one of the functionalities described above. For example, wireless device 900 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.Figure 108

[0080] Figure 10 shows a network node 1000 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 1000 may be configured to operate in communication system 700 of Figure 7, like network nodes 708 or 710, or in communication system 800 of Figure 8, like an AP 810 or a station 812. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0081] Network nodes 1000 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 1000 may be a relay node or a relay donor node controlling a relay. Network nodes 1000 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0082] Other examples of network nodes 1000 include multiple transmission point (multi-TRP) 5G access nodes, multistandard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0083] In particular embodiments, network node 1000 includes a processing circuitry 1002, a memory 1004, a communication interface 1006, and a power source 1008. In general, in a particular embodiment of network node 1000, processing circuitry 1002, memory 1004, communication interface 1006, and power source 1008 may, in whole or inApplicant's Ref: P113217WO01 16part, represent or include physical components common to or shared by one or more of the other elements of network node 1000.

[0084] The network node 1000 may be composed of multiple distinct network entities (e.g., a NodeB entity and an RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 1000 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1004 or portions of memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs). The network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1000.

[0085] The processing circuitry 1002 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 1004, to provide network node 1000 functionality.

[0086] In some embodiments, the processing circuitry 1002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1002 includes one or more of radio frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014. In some embodiments, the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1012 and baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.

[0087] The memory 1004 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1002. The memory 1004 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1002 and utilized by the network node 1000. The memory 1004 may be used to store any calculations made by the processing circuitry 1002 and / or any data received via the communication interface 1006. In some embodiments, the processing circuitry 1002 and memory 1004 is integrated.Applicant's Ref: P113217WO01 17

[0088] The communication interface 1006 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 1006 comprises port(s) / terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 900 may be capable of wireless communication and communication interface 1006 may also include radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, an antenna 1010. Particular embodiments of radio front-end circuitry 1018 include filter(s) 1020 and amplifier(s) 1022. The radio front-end circuitry 1018 may be connected to an antenna 1010 and processing circuitry 1002. The radio front-end circuitry may be configured to condition signals communicated between antenna 1010 and processing circuitry 1002. The radio front-end circuitry 1018 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1018 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 1020 and / or amplifiers 1022. The radio signal(s) may then be transmitted via the antenna 1010. Similarly, when receiving data, the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018. The digital data may be passed to the processing circuitry 1002. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0089] In certain alternative embodiments, network node 1000 may be capable of wireless communication but does not include separate radio front-end circuitry 1018, instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communication interface 1006. In still other embodiments, the communication interface 1006 includes one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012, as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).

[0090] The antenna 1010 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1010 may be coupled to the radio front-end circuitry 1018 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1010 is separate from the network node 1000 and connectable to the network node 1000 through one or more interfaces or ports.

[0091] The antenna 1010, communication interface 1006, and / or the processing circuitry 1002 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 1000. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 1010, the communication interface 1006, and / or the processing circuitry 1002 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 1000. Any information, data and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0092] The power source 1008 provides power to the various components of network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of theApplicant's Ref: P113217WO01 18network node 1000 with power for performing the functionality described herein. For example, the network node 1000 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1008. As a further example, the power source 1008 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0093] Embodiments of the network node 1000 may include additional components beyond those shown in Figure 10 for providing certain aspects of the network node's functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1000 may include user interface equipment to allow input of information into the network node 1000 and to allow output of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000.Figure 11

[0094] Figure 11 is a block diagram illustrating a virtualization environment 1100 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1100 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1100 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

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

[0096] Hardware 1104 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1106 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 1108A and VM 1108B (which may be collectively referred to as VMs 1108), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1106 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 1108.

[0097] The VMs 1108 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 1106. Different embodiments of the instance of a virtual appliance 1102 may beApplicant's Ref: P113217WO01 19implemented on one or more of VMs 1108, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0098] In the context of NFV, each of the VMs 1108 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1108, and that part of hardware 1104 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 1108 on top of the hardware 1104 and corresponds to an application 1102.

[0099] Hardware 1104 may be implemented in a standalone network node with generic or specific components. Hardware 1104 may implement some functions via virtualization. Alternatively, hardware 1104 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1110, which, among others, oversees lifecycle management of applications 1102. In some embodiments, hardware 1104 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1112 which may alternatively be used for communication between hardware nodes and radio units.

[0100] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0101] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in theApplicant's Ref: P113217WC01 20form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0102] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.EMBODIMENTS

[0103] Some of the embodiments described above may be summarized in the following manner:1. A method performed by a sensing controller (502) for identifying user equipment devices, UEs, to perform UE-assisted sensing, the method comprising:receiving (302) a first indication indicating whether UE-assisted sensing is allowed at a UE (402); receiving (304) a second indication indicating that UE-assisted sensing is allowed by a subscription owner of the UE (402);in response to both the first indication and the second indication indicating that UE-assisted sensing is allowed, adding (306) the UE (402) to a registry of UE-assisted sensing enabled UEs at the sensing controller (502).2. The method of embodiment 1 , wherein the first indication is received from the UE (402) via a Radio Resource Control, RRC, message.3. The method of any of embodiments 1 to 2, wherein the first indication is comprised in a dedicated information element.4. The method of any of embodiments 2 to 3, wherein an absence of the dedicated information element in the RRC message indicates that UE-assisted sensing is not allowed at the UE (402).5. The method of any of embodiments 1 to 4, further comprising:providing (308), to a core network node, a third indication that UE-assisted sensing is allowed at the UE (402).6. The method of embodiment 5, wherein the third indication is provided via a Next Generation Application Protocol, NGAP, message.7. The method of embodiment 5, wherein the core network node is an Access and Mobility ManagementApplicant's Ref: P113217WO01 21Function, AMF (406).8. The method of embodiment 1 , wherein the first indication is received from a core network node.9. The method of embodiment 8, wherein the core network node is a Unified Data Management, UDM (408).10. The method of any of embodiments 1 to 9, wherein the first indication and the second indication are a single indication received from a core network node.11. The method of embodiment 10, wherein the single indication is received via a Service Exposure Layer.12. The method of embodiment 1, wherein the second indication is received from a core network node.13. The method of any of embodiments 1 to 12, wherein the sensing controller (502) is implemented by a radio access network node (404).14. A sensing controller (502) for identifying user equipment devices, UEs, to perform UE-assisted sensing, the sensing controller (502) comprising processing circuitry configured to cause the sensing controller (502) to perform operations comprising:receiving (302) a first indication indicating whether UE-assisted sensing is allowed at a UE (402); receiving (304) a second indication indicating that UE-assisted sensing is allowed by a subscription owner of the UE (402);in response to both the first indication and the second indication indicating that UE-assisted sensing is allowed, adding (306) the UE (402) to a registry of UE-assisted sensing enabled UEs at the sensing controller (502).15. The sensing controller (502) of embodiment 14, wherein the processing circuitry is further configured to cause the sensing controller (502) to perform the method of any one of embodiments 2 to 13.

Claims

Applicant's Ref: P113217WO01 22CLAIMSWhat is claimed is:

1. A method performed by a sensing controller (502) for identifying user equipment devices, UEs, to perform UE-assisted sensing, the method comprising:receiving (302) a first indication indicating whether UE-assisted sensing is allowed at a UE (402); receiving (304) a second indication indicating that UE-assisted sensing is allowed by a subscription owner of the UE (402);in response to both the first indication and the second indication indicating that UE-assisted sensing is allowed, adding (306) the UE (402) to a registry of UE-assisted sensing enabled UEs at the sensing controller (502).

2. The method of claim 1 , wherein the first indication is received from the UE (402) via a Radio Resource Control, RRC, message.

3. The method of any one of claim 1 to 2, wherein the first indication is comprised in a dedicated information element.

4. The method of any one of claim 2 to 3, wherein an absence of the dedicated information element in the RRC message indicates that UE-assisted sensing is not allowed at the UE (402).

5. The method of any one of claim 1 to 4, further comprising:providing (308), to a core network node, a third indication that UE-assisted sensing is allowed at the UE (402).

6. The method of claim 5, wherein the third indication is provided via a Next Generation Application Protocol, NGAP, message.

7. The method of claim 5, wherein the core network node is an Access and Mobility Management Function, AMF (406).

8. The method of claim 1 , wherein the first indication is received from a core network node.

9. The method of claim 8, wherein the core network node is a Unified Data Management, UDM (408).

10. The method of any one of claim 1 to 9, wherein the first indication and the second indication are a single indication received from a core network node.

11. The method of claim 10, wherein the single indication is received via a Service Exposure Layer.Applicant's Ref: P113217WO01 2312. The method of claim 1, wherein the second indication is received from a core network node.

13. The method of any one of claim 1 to 12, wherein the sensing controller (502) is implemented by a radio access network node (404).

14. A sensing controller (502) for identifying user equipment devices, UEs, to perform UE-assisted sensing, the sensing controller (502) comprising processing circuitry configured to cause the sensing controller (502) to perform operations comprising:receiving (302) a first indication indicating whether UE-assisted sensing is allowed at a UE (402); receiving (304) a second indication indicating that UE-assisted sensing is allowed by a subscription owner of the UE (402);in response to both the first indication and the second indication indicating that UE-assisted sensing is allowed, adding (306) the UE (402) to a registry of UE-assisted sensing enabled UEs at the sensing controller (502).

15. The sensing controller (502) of claim 14, wherein the processing circuitry is further configured to cause the sensing controller (502) to perform the method of any one of claim 2 to 13.

Images