Implementing an integrated sensing and communication function

Abstract

A first network node (4000) receives (3410, 3510, 3530, 3560) a request for sensing information from a second network node Responsive to receiving the request for the sensing information, the first network node transmits (3420, 3530, 3550, 3570) a message to the second network node.

Description

IMPLEMENTING AN INTEGRATED SENSING AND COMMUNICATION FUNCTIONTECHNICAL FIELD

[0001] The present disclosure is related to wireless communication systems and more particularly to implementing an integrated sensing and communication, ISAC, function.BACKGROUND

[0002] Recently, the system architectures (SAI and SA2) groups of the 3rdGeneration Partnership Project (“3GPP”) have defined study items to identify use cases and architectural enhancements that will enable integrated sensing and communication (“ISAC”) in cellular network. The term ISAC can correspond to the internal term joint communication and sensing (“JCAS”), used for the same technology.

[0003] FIG. 1 illustrates an example of current 5thgeneration radio access network (“NG- RAN”) architecture. The NG-RAN architecture can be further described as follows. The NG- RAN includes a set of 5thgeneration (“5G”) base stations (referred to herein as gNBs) connected to the 5thgeneration core network (“5GC”) through the next generation (“NG”) network. A gNB can support frequency division duplex (“FDD”) mode, time division duplex (“TDD”) mode or dual mode operation. gNBs can be interconnected through the Xn interface. A gNB can include a gNB-central unit (“CU”) and gNB-distributed units (“DUs”). A gNB-CU and a gNB- DU are connected via a Fl logical interface. One gNB-DU is connected to only one gNB-CU. For resiliency, a gNB-DU may be connected to multiple gNB-CU by appropriate implementation. NG, Xn, and Fl are logical interfaces. The NG-RAN is layered into a Radio Network Layer (“RNL”) and a Transport Network Layer (“TNL”). The NG-RAN architecture (e.g., the NG-RAN logical nodes and interfaces between them) is defined as part of the RNL. For each NG-RAN interface (e.g., NG, Xn, and Fl) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport and signaling transport. NG, Xn and Fl are logical interfaces.

[0004] For NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For EN-DC, the Sl-U and X2-C interfaces for a gNB including a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.

[0005] In some examples of network sharing with multiple cell ID broadcast, each Cell Identity associated with a subset of PLMNs corresponds to a gNB-DU and the gNB-CU it is connected to, for example, the corresponding gNB-DUs share the same physical layer cellresources. For resiliency, a gNB-DU may be connected to multiple gNB-CUs by appropriate implementation.

[0006] For NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For EN-DC, the Sl-U and X2-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.

[0007] The node hosting user plane part of NR PDCP (e.g., gNB-CU, gNB-CU-UP, and for EN-DC, MeNB or SgNB depending on the bearer split) shall perform user inactivity monitoring and further informs its inactivity or (re)activation to the node having C-plane connection towards the core network (e.g., over El, X2). The node hosting NR RLC (e.g. gNB-DU) may perform user inactivity monitoring and further inform its inactivity or (re)activation to the node hosting control plane, e.g. gNB-CU or gNB-CU-CP.

[0008] UL PDCP configuration (i.e. how the UE uses the UL at the assisting node) is indicated via X2-C (for EN-DC), Xn-C (for NG-RAN) and Fl-C. Radio Link Outage / Resume for DL and / or UL is indicated via X2-U (for EN-DC), Xn-U (for NG-RAN) and Fl-U.

[0009] The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture (e.g., the NG-RAN logical nodes and interfaces between them) is defined as part of the RNL. For each NG-RAN interface (NG, Xn, Fl) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport, signalling transport. In NG-Flex configuration, each NG-RAN node is connected to all AMFs of AMF Sets within an AMF Region supporting at least one slice also supported by the NG-RAN node. The AMF Set and the AMF Region are defined in 3GPP. If security protection for control plane and user plane data on TNL of NG-RAN interfaces has to be supported, NDS / IP 3GPP TS 33.501 shall be applied.

[0010] The overall architecture for separation of gNB-CU-CP and gNB-CU-UP is depicted in FIG. 2.

[0011] A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs and multiple gNB- DUs. The gNB-CU-CP is connected to the gNB-DU through the Fl-C interface. The gNB-CU- UP is connected to the gNB-DU through the Fl-U interface. The gNB-CU-UP is connected to the gNB-CU-CP through the El interface. One gNB-DU is connected to only one gNB-CU-CP. One gNB-CU-UP is connected to only one gNB-CU-CP. For resiliency, a gNB-DU and / or a gNB-CU-UP may be connected to multiple gNB-CU-CPs by appropriate implementation. One gNB-DU can be connected to multiple gNB-CU-UPs under the control of the same gNB-CU- CP. One gNB-CU-UP can be connected to multiple DUs under the control of the same gNB- CU-CP.

[0012] The connectivity between a gNB-CU-UP and a gNB-DU is established by the gNB- CU-CP using Bearer Context Management functions. The gNB-CU-CP selects the appropriate gNB-CU-UP(s) for the requested services for the UE. In case of multiple CU-UPs they belong to same security domain. Data forwarding between gNB-CU-UPs during intra-gNB-CU-CP handover within a gNB may be supported by Xn-U.SUMMARY

[0013] According to some embodiments, a method of operating a first network node is provided. The method includes receiving a request for sensing information from a second network node. The method further includes, responsive to receiving the request for the sensing information, transmitting a message to the second network node.

[0014] According to other embodiments, a method of operating a second network node is provided. The method includes transmitting a request for sensing information from a first network node. The method further includes, responsive to transmitting the request for the sensing information, receiving (3630, 3720, 3750, 3770) a message from the first network node.

[0015] Certain aspects of these embodiments may provide technical advantages. In some embodiments, support for sensing is provided in split NG-RAN architectures, which can improve network recognition and monitoring of connected and non-connected devices within an environment.BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

[0017] FIG. 1 is a block diagram illustrating an example of a NG-RAN architecture;

[0018] FIG. 2 is a block diagram illustrating an example of a gNB architecture with separation of gNB-CU-CP and gNB-CU-UP;

[0019] FIGS. 3A-D are schematic diagrams illustrating examples of sensing modes;

[0020] FIG. 4 is a signal flow diagram illustrating an example of signals communicated within a network to perform a sensing procedure;

[0021] FIG. 5 is a signal flow diagram illustrating an example of a SRU information exchange between SeMF and gNB-CU in accordance with some embodiments;

[0022] FIGS. 6-7 are tables illustrating an example of a SRU Information Request in accordance with some embodiments;

[0023] FIGS. 8-9 are tables illustrating an example of a SRU Information Response in accordance with some embodiments;

[0024] FIG. 10 is a table illustrating an example of a SRU information Failure in accordance with some embodiments;

[0025] FIG. 1 lis a signal flow diagram illustrating an example of a sensing configuration exchange between SeMF and gNB-CU in accordance with some embodiments;

[0026] FIG. 12 is a table illustrating an example of a Sensing Configuration Request in accordance with some embodiments;

[0027] FIG. 13 is a table illustrating an example of a Sensing Configuration Response in accordance with some embodiments;

[0028] FIG. 14 is a table illustrating an example of a Sensing Configuration Failure in accordance with some embodiments;

[0029] FIG. 15 is a table illustrating an example of a Sensing Configuration Update in accordance with some embodiments;

[0030] FIG. 16 is a table illustrating an example of a Sensing Activation Command in accordance with some embodiments;

[0031] FIG. 17 is a table illustrating an example of a Sensing Activation Response in accordance with some embodiments;

[0032] FIG. 18 is a table illustrating an example of a Sensing Activation Failure in accordance with some embodiments;

[0033] FIG. 19 is a table illustrating an example of a Sensing Deactivation Command in accordance with some embodiments;

[0034] FIG. 20 is a signal flow diagram illustrating an example of a sensing measurement exchange between SeMF and gNB in accordance with some embodiments;

[0035] FIGS. 21-22 are tables illustrating an example of a Sensing Measurement Request in accordance with some embodiments;

[0036] FIGS. 23-24 are tables illustrating an example of a Sensing Measurement Response in accordance with some embodiments;

[0037] FIG. 25 is a table illustrating an example of a SRU Measurement Report in accordance with some embodiments;

[0038] FIG. 26 is a table illustrating an example of a Sensing Measurement Failure in accordance with some embodiments;

[0039] FIGS. 27-28 are tables illustrating an example of a Sensing Measurement Update in accordance with some embodiments;

[0040] FIG. 29 is a table illustrating an example of a Sensing Measurement Abort in accordance with some embodiments;

[0041] FIG. 30 is a table illustrating an example of a Sensing Measurement Failure Indication in accordance with some embodiments;

[0042] FIG. 31 is a signal flow diagram illustrating an example of SRUs information exchange between CU and DU in accordance with some embodiments;

[0043] FIG. 32 is a signal flow diagram illustrating an example of Fl Sensing Configuration Exchange between CU and DU in accordance with some embodiments;

[0044] FIG. 33 is a signal flow diagram illustrating an example of a Fl sensing measurement exchange procedure between CU and DU in accordance with some embodiments;

[0045] FIGS. 34-37 are flow charts illustrating examples of operations performed by a network node in accordance with some embodiments;

[0046] FIG. 38 is a block diagram of a communication system in accordance with some embodiments;

[0047] FIG. 39 is a block diagram of a user equipment in accordance with some embodiments;

[0048] FIG. 40 is a block diagram of a network node in accordance with some embodiments;

[0049] FIG. 41 is a block diagram of a host, which may be an embodiment of the host of FIG. 38, in accordance with some embodiments;

[0050] FIG. 42 is a block diagram of a virtualization environment in accordance with some embodiments; and

[0051] FIG. 43 shows a communication diagram of a host communicating via a network node with a user equipment over a partially wireless connection in accordance with some embodiments.DETAILED DESCRIPTION

[0052] 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, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in theart. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present / used in another embodiment.

[0053] Sensing using cellular networks can be performed in a monostatic setting, when the transmitter and the receiver sensing antennas are located in the same node, and in a multistatic setting, when the transmitter and the receiver sensing antennas are located in different nodes. FIGS. 3A-B illustrate examples of different radar settings that can be deployed using NR base stations (“BSs”), denoted by gNB, and user equipments (“UEs”). A goal is to detect and localize a target which, in general, is a non-connected object (e.g.a pedestrian or an animal). Targets can be connected UEs and in this case sensing is used to improve communication-based positioning of such UEs.

[0054] FIG. 3A illustrates an example gNB(s)-only based monostatic sensing. FIG. 3B illustrates an example of different bi-static settings with gNB-only. FIGS. 3C-D both illustrate examples of both gNB / UEs-based bi-static sensing settings. TX-s and RX-s denote respectively the sensing transmitter node and the sensing receiver node.

[0055] FIG. 4 illustrates an example of signals communicated within a network to perform a sensing procedure. In some examples, the sensing radio unit is a logical entity in RAN capable of at least one of: radio signal transmission used for sensing; radio signal reception used for sensing; radio measurement used for sensing; and radio antennas. In additional or alternative examples, the sensing radio units can have their own internal or external antenna or can share antenna(s) with other radio nodes. Multiple sensing units can be involved in a sensing session. The relevant sensing units can be selected or configured. In additional or alternative examples, sensing radio units can be deployed in different ways, for example, as integrated into a gNB / base station or other radio nodes; as integrated into standalone radio nodes; by sharing radio equipment (at different levels) with other radio nodes; or by sensing result and different levels of processing.

[0056] In some examples, sensing radio units use different sources of sensing types of data including, for example, 3GPP sensing data, 5G wireless sensing data, human motion rate accuracy, or non-3GPP sensing data. 3GPP sensing data can be data derived from 3GPP radio signals impacted (e.g., reflected, refracted, diffracted) by an object or environment of interest for sensing purposes, and optionally processed within the 5G system. 5G wireless sensing can be a 5GS feature providing capabilities to get information about characteristics of the environment and / or objects within the environment (e.g., shape, size, orientation, speed, location, distances or relative motion between objects, etc) using NR RF signals and, in some cases, previously defined information available in EPC and / or E-UTRA. Human motion rate accuracy can describe the closeness of the measured value of the human body movement frequency caused bypart(s) (e.g., chest) of the target object (i.e. human body) to the true value of the human body movement frequency. non-3GPP sensing data can be data provided by non-3GPP sensors (e.g. video, LiDAR, sonar) about an object or environment of interest for sensing purposes.

[0057] There currently exist certain challenges. Sensing may be a key technology in the future, however, it is not clear how the current NG-RAN architecture, both disaggregated and non-disaggregated forms, can encompass the sensing features and related signaling aspects (e.g., the Sensing Radio Units with their different types of data sensing) for configuration and sensing measurement reporting.

[0058] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. In some embodiments, integration of sensing functions in nondisaggregated and disaggregated gNB architecture (e.g., between gNB-CU and gNB-CU) is provided to support signaling of sensing unit capabilities, sensing configuration, and sensing measurements in the network protocols.

[0059] Herin, a network node can be a RAN node, a gNB, eNB, en-gNB, ng-eNB, gNB- CU, gNB-CU-CP, gNB-DU, gNB-CU-UP, eNB-CU, eNB-CU-CP, eNB-CU-UP, lAB-node, lAB-donor DU, lAB-donor-CU, IAB-DU, IAB-MT, O-CU, O-CU-CP, O-CU-UP, O-DU, O- RU, O-eNB, aNon-Real Time RAN Intelligent Controller (Non-RT RIC), a Real-Time RAN Intelligent Controller (RT-RIC).

[0060] Various embodiment herein prove basic functionality support to integrate sensing functions in NG-RAN architecture protocols including support for: sensing radio unit capabilities exchange; sensing configuration with addition of tag IDs for the detected objects, update of sensing configuration; and requesting and reporting of sensing measurement and associated time stamp.

[0061] Embodiments associated with Non-disaggregated gNB architecture (e.g., SeMF and gNB-CU) are described below.

[0062] In some embodiments, the gNB-CU is the entity in NG-RAN that terminates the application protocol with the Sensing Management Function (“SeMF”). The SeMF can be connected towards the gNB-CU via a newly defined interface named, which can be referred to as a New Radio Sensing Protocol (“NRSP”).

[0063] In additional or alternative embodiments, each message between the SeMF and the NG-RAN can be identified by a transaction ID (e.g., a NRSP Transaction ID).

[0064] In additional or alternative embodiments, the SeMF sends a message over the NSRP interface to the gNB-CU to perform one or more operations. In some operations, the functions include a transfer of sensing messages between gNB central unit in NG-RAN and the SeMF, such as: a message from SeMF asking gNB to report the capabilities of the sensing radio unitshosted by the gNB. In additional or alternative examples, the Sensing Radio Unit (“SRU”) is identified by a {SRU ID, cell ID} pair, where the cell ID is optional. Absence of the cell ID indicates that the SRU is not associated with a cell. SRU is a part of gNB which has capability to perform sensing measurements and transmitting sensing reference signals (signals that can be used for signaling). In additional or alternative examples, a SRU capability can indicate which 3GPP sensing data it supports measuring, whether 5G Wireless sensing capabilities are supported, whether Human motion rate accuracy and which levels are supported, and which non-3GPP sensing data are supported to be reported. In additional or alternative examples, the message signaled over NRSP to request SRU information is called SRU INFORMATION REQUEST message. The message for reporting SRU capability information is called SRU INFORMATION RESPONSE message. In case of failure, the gNB sends a SRU INFORMATION FAILURE message to the SeMF.

[0065] FIG. 5 is a signal flow diagram illustrating an example of a SRU information exchange between SeMF and gNB-CU in accordance with some embodiments. An example of specification impact of the definition of a NRSP SRU information exchange procedure is illustrated in FIGS. 6-10. FIGS. 6-7 are tables illustrating an example of a SRU Information Request. This message can be sent by an SeMF to request information for SRUs hosted by an NG-RAN node. FIGS. 8-9 are tables illustrating an example of a SRU Information Response. This message can be sent by an NG-RAN node to convey SRU information to an SeMF. FIG. 10 is a table illustrating an example of a SRU information Failure. This message is sent by an NG-RAN node to indicate that the requested SRU information cannot be provide to an SeMF.

[0066] In some embodiments, the SeMF sends a message over the NSRP interface to the gNB-CU to perform one or more operations. In some examples, the operations include, the SeMF requesting the gNB perform sensing configuration to start measuring sensing raw data from the environment. For instance, upon receiving the SENSING CONFIGURATION REQUEST message, the gNB can add a tag ID of the detected passive object in the sensing area and the time indication associated to the action. The indication can be a time stamp with System Frame Number, UTC time, or a relative time indication.

[0067] FIG. 1 lis a signal flow diagram illustrating an example of a sensing configuration exchange between SeMF and gNB-CU. At block 3 of FIG. 11, a failure message can be signaled in case of unsuccessful operation.

[0068] In additional or alternative embodiments, the recommended sensing characteristics may recommend to perform a periodic, semi-periodic, or aperiodic sensing configuration. lat block 4, the gNB may update the SeMF with a SENSING CONFIGURATION UPDATE message, in case the sensing configuration changed over time. The gNB indicates a timeindicator associated to this update, which can be time stamp, System Frame Number, UTC time, etc.

[0069] In additional or alternative examples, if aperiodic configuration, then SeMF provides the command to activate the sensing command to the gNB via NRSP interface. For example, at blocks 5-6 , SENSING ACTIVATION COMMAND message between SeMF and gNB is defined for gNB to activate the sensing transmission.

[0070] At block 7, if the activation is successful, the gNB responds with a SENSING ACTIVATION RESPONSE message over the NRSP interface, with the slot number and SFN indicating when the activation in time was performed. Otherwise, it sends a SENSING ACTIVATION FAILURE message to SeMF.

[0071] In additional or alternative examples, the SeMF may provide a deactivation command to indicate the gNB to stop the aperiodic transmission. For example, at blocks 8-9, a SENSING DEACTIVATION COMMAND message is communicated between SeMF and gNB.

[0072] An example of specification impact of the definition of a NRSP sensing configuration exchange procedure is illustrated in FIGS. 12-19. FIG. 12 is a table illustrating an example of a Sensing Configuration Request. This message can be sent by an SeMF to request sensing configuration information. FIG. 13 is a table illustrating an example of a Sensing Configuration Response. This message can be sent by an NG-RAN node to report sensing configuration information SeMF. FIG. 14 is a table illustrating an example of a Sensing Configuration Failure. This message can be sent by an NG-RAN node to indicate that the requested sensing configuration cannot be provided to an SeMF. FIG. 15 is a table illustrating an example of a Sensing Configuration Update. This message can be sent by the NG-RAN node to indicate that a change in the sensing configuration has occurred. FIG. 16 is a table illustrating an example of a Sensing Activation Command. This message can be sent by the SeMF to cause the NG RAN node to activate / trigger sensing transmission. FIG. 17 is a table illustrating an example of a Sensing Activation Response. This message can be sent by NG-RAN node to confirm successful sensing activation. FIG. 18 is a table illustrating an example of a Sensing Activation Failure. This message can be sent by NG-RAN node to indicate that activation of sensing transmission was unsuccessful. FIG. 19 is a table illustrating an example of a Sensing Deactivation Command in accordance with some embodiments; This message can be sent by the SeMF to cause the NG RAN node to deactivate sensing transmission or release all the transmission resources.

[0073] FIG. 20 is a signal flow diagram illustrating an example of a sensing measurement exchange between SeMF and gNB. In some embodiments, the SeMF sends a message over the NSRP interface to the gNB-CU to perform one or more operations. In some examples, theoperations include, where SeMF can request sensing measurements from gNB, indicating the tag ID of the interested passive object, the SRU ID of each SRU (it can be one SRU or a list of SRUs) to use for performing sensing measurement, and the requested sensing measurements. The gNB responses to SeMF with the sensing measurements from the indicated SRUs with list of collected measurements, which can be: Number Of Reflected Paths; RSRP per path; peak-to- average power ratio; Round trip type measurements; time delay per path; angle of departure; angle of arrival per path; doppler frequency; acceleration measurements; carrier phase measurements per path; carrier phase difference measurements; orientation measurements; object geometry-related (size,. . . ); object material-related (type of material can be detected by sensing at different frequencies); or object other physical characteristics (humidity, temperature, etc.).

[0074] At blocks 1-3, the SRU can also report the time stamp associated to when the measurements where collected. In case of unsuccessful operation, a failure message is signaled over NRSP interface.

[0075] In some embodiments, the SeMF indicates in the SENSING MEASUREMENT REQUEST message the data format type of the request sensing measurement, if raw data from SRU, or processed sensing data considering SRU has such capability.

[0076] At block 5, a SENSING MEASUREMENT UPDATE is sent by the SeMF, in case the SeMF is interested in requesting different type of measurements and changing the reporting characteristics.

[0077] At block 7, in case gNB detects error and / or can no longer perform sensing measurement from the passive objects, it sends a SENSING MEASUREMENT FAILURE INDICATION to SeMF, indicating a cause value.

[0078] At block 9, in case the SeMF would like to stop the sensing reporting, it sends a SENSING MEASUREMENT ABORT message to gNB over NRSP interface.

[0079] An example of specification impact of the definition of a NRSP sensing measurement exchange procedure is illustrated in FIGS. 21-30. FIGS. 21-22 are tables illustrating an example of a Sensing Measurement Request. This message can be sent by the SeMF to request the NG-RAN to configure a sensing measurement. FIGS. 23-24 are tables illustrating an example of a Sensing Measurement Response. This message can be sent by the NG-RAN to report sensing measurements. FIG. 25 is a table illustrating an example of a SRU Measurement Report. This information element (report) can indicate the SRU measurements. FIG. 26 is a table illustrating an example of a Sensing Measurement Failure. This message can be sent by the NG-RAN to report sensing measurement failure. FIGS. 27-28 are tables illustrating an example of a Sensing Measurement Update. The message can be sent by theSeMF to update a previously configured measurement. FIG. 29 is a table illustrating an example of a Sensing Measurement Abort. This message can be sent by the SeMF to request the NG- RAN node to abort a sensing measurement. FIG. 30 is a table illustrating an example of a Sensing Measurement Failure Indication. This message can be sent by the NG-RAN node to indicate that the previously requested sensing measurements can no longer be reported.

[0080] Embodiments associated with gNB-CU and gNB-DU are described below. FIG. 31 is a signal flow diagram illustrating an example of SRUs information exchange between CU and DU. In some embodiments, the Fl protocol between the gNB-CU and gNB-DU is enhanced to support sensing functions. Specifically, a new list of sensing messages and procedures are introduced between the gNB-CU and the gNB-CU to perform an operation. The operation can include a transfer of sensing messages between gNB-CU and the SRUs located at the gNB-DU, to inquire about the SRU sensing capabilities hosted by the gNB-DU and identified by their ID. This can be defined as new Fl messages for SRU Information Exchange, which can have the same structure as the NRSP SRU Information Exchange procedure.

[0081] The operation can include, the gNB-CU requesting that the gNB-DU perform sensing configuration to start measuring sensing raw data from the environment. For instance, upon receiving the Sensing configuration request, the gNB-DU can add a tag ID of the detected passive object in the sensing area, and inform the gNB-CU of those passive objects associated tag IDs and time stamp information.

[0082] In some embodiments, the recommended sensing characteristics may recommend to perform periodic or aperiodic sensing configuration. In some examples, the gNB-DU may update the gNB-CU with a Fl SENSING CONFIGURATION UPDATE message, in case the sensing configuration changed over time. The gNB-DU indicates a time indicator associated to this update, which can be time stamp, UTC time. In additional or alternative examples, if aperiodic configuration, activation command message are exchanged between gNB-CU and gNB-DU over the Fl interface, similarly as between the SeMF and gNB-CU for the purpose of activation command request, response, failure and deactivation command.

[0083] FIG. 32 is a signal flow diagram illustrating an example of Fl Sensing Configuration Exchange between CU and DU. In some examples, the operations incude, where gNB-CU can request sensing measurements from gNB-DU, indicating the tag ID of the interested passive object, the SRU ID of each SRU (it can be one SRU or a list of SRUs) to use for performing sensing measurement, and the requested sensing measurements. In additional or alternative embodiments, the gNB-DU responses to gNB-CU with the sensing measurements from the indicated SRUs with list of collected measurements and the time stamp as indicated above. The gNB-CU relays the SRU sensing measurement report to the SeMF.

[0084] In additional lor alternative embodiments, the gNB-CU relays to gNB-DU whether the SeMF requests raw data from SRU, or processed sensing data considering SRU has such capability.

[0085] In additional or alternative embodiments, new messages are exchanged between CU and DU over the Fl interface, similarly over the NRSP interface between SeMF and CU, for the purpose of SENSING MEASUREMENT UPDATE, SENSING MEASUREMENT FAILURE INDICATION and SENSING MEASUREMENT ABORT.

[0086] FIG. 33 is a signal flow diagram illustrating an example of a Fl sensing measurement exchange procedure between CU and DU.

[0087] Operations of the network node 4000 (implemented using the structure of FIG. 40) will now be discussed with reference to the flow charts of FIGS. 34-37 according to some embodiments of inventive concepts. For example, modules may be stored in memory 4004 of FIG. 40, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry 4002, network node 4000 performs respective operations of the flow charts.

[0088] FIG. 34 illustrates an example of operations performed by a first network node to enable IS AC. At block 3410, processing circuitry 4002 receives, via communication interface 4006, a request for sensing information from a second network node. At block 3420, processing circuitry 4002 transmits, via communication interface 4006, a message to the second network node.

[0089] FIG. 35 illustrates another example of operations performed by a first network node to enable ISAC. At block 3510, processing circuitry 4002 receives, via communication interface 4006, a SRU Information Request from a second network node. At block 3520, processing circuitry 4002 transmits, via communication interface 4006, a SRU Information Response to the second network node. At block 3530, processing circuitry 4002 receives, via communication interface 4006, a sensing configuration request from the second network node. At block 3540, processing circuitry 4002 determines an identity of a passive object. At block 3550, processing circuitry 4002 transmits, via communication interface 4006, a sensing information response to the second network node. At block 3560, processing circuitry 4002 receives, via communication interface 4006, a sensing measurement request from a second network node. At block 3570, processing circuitry 4002 transmits, via communication interface 4006, a sensing measurement Response to the second network node. At block 3580, processing circuitry 4002 receives, via communication interface 4006, a sensing measurement abort. At block 3590, processing circuitry 4002 ceases the sensing procedure.

[0090] FIG. 36 illustrates an example of operations performed by a first network node to enable IS AC. At block 3610, processing circuitry 4002 transmits, via communication interface 4006, a request for sensing information to a first network node. At block 3620, processing circuitry 4002 receives, via communication interface 4006, a message from the first network node.

[0091] FIG. 37 illustrates another example of operations performed by a first network node to enable IS AC. At block 3710, processing circuitry 4002 transmits, via communication interface 4006, a SRU Information Request to a first network node. At block 3720, processing circuitry 4002 receives, via communication interface 4006, a SRU Information Response from the first network node. At block 3730, processing circuitry 4002 transmits, via communication interface 4006, a sensing configuration request to the first network node. At block 3750, processing circuitry 4002 receives, via communication interface 4006, a sensing information response from the first network node. At block 3760, processing circuitry 4002 transmits, via communication interface 4006, a sensing measurement request to the first network node. At block 3770, processing circuitry 4002 receives, via communication interface 4006, a sensing measurement Response from the first network node. At block 3780, processing circuitry 4002 transmits, via communication interface 4006, a sensing measurement abort.

[0092] Various operations from the flow charts of FIGS. 34-37 may be optional with respect to some embodiments of network nodes and related methods.

[0093] Example Embodiments are described below.

[0094] Embodiment 1. A method of operating a first network node (4000), the method comprising: receiving (3410, 3510, 3530, 3560) a request for sensing information from a second network node; and responsive to receiving the request for the sensing information, transmitting (3420, 3530, 3550, 3570) a message to the second network node.

[0095] Embodiment 2. The method of Embodiment 1 , wherein receiving the request for sensing information comprises receiving a request for the sensing capability information indicating sensing capabilities of the first network node.

[0096] Embodiment 3. The method of Embodiment 2, wherein the sensing capabilities of the first network node comprises capabilities of one or more sensing radio units, SRUs, hosted by the first network node, the SRUs.

[0097] Embodiment 4. The method of any of Embodiments 2-3, wherein the sensing capabilities comprise an indication of a type of data that can be measured including at least one of:Third Generation Partnership Project, 3GPP, sensing data;Fifth Generation, 5G, Wireless sensing data;Human motion rate accuracy data; andNon-3GPP sensing data.

[0098] Embodiment 5. The method of any of Embodiments 2-4, wherein the request for sensing information includes an indication of one or more of: an identifier of a sensing radio unit, SRU; and an identifier of a cell associated with the SRU.

[0099] Embodiment 6. The method of any of Embodiments 2-5, wherein receiving the request for sensing capability information comprises receiving a sensing radio unit, SRU, Information Request, and wherein transmitting the message comprises transmitting at least one of: a SRU Information Response; and a SRU Information Failure.

[0100] Embodiment 7. The method of any of Embodiments 1-6, wherein receiving the request for sensing information comprises receiving a request for sensing configuration information for performing a sensing procedure.

[0101] Embodiment s. The method of Embodiment 7, further comprising: determining (3540) an identifier for a passive object within an environment of the first network node, wherein the message include an indication of the identifier.

[0102] Embodiment 9. The method of Embodiment 8, wherein the identifier includes a time stamp associated with detection of the passive object.

[0103] Embodiment 10. The method of any of Embodiments 7-9, wherein the sensing configuration information includes an indication that the sensing procedure be performed at least one of: periodically; semi-periodically; and aperiodically.

[0104] Embodiment 11. The method of any of Embodiments 7-10, wherein receiving the request for sensing configuration information comprises receiving a sensing configuration request, and\ wherein transmitting the message comprises transmitting at least one of: a sensing configuration response; a sensing configuration failure;a sensing configuration update; a sensing activation response; and a sensing configuration failure.

[0105] Embodiment 12. The method of any of Embodiments 1-11, wherein receiving the request for sensing information comprises receiving a request for sensing measurement information.

[0106] Embodiment 13. The method of Embodiment 12, wherein the message comprises the sensing measurement information including at least one of: an indication of a Number Of Reflected Paths; an indication of a RSRP per path; an indication of a peak-to-average power ratio; an indication of a Round trip type measurements; an indication of a time delay per path; an indication of an angle of departure; an indication of an angle of arrival per path; an indication of a doppler frequency; an indication of an acceleration measurements; an indication of a carrier phase measurements per path; an indication of a carrier phase difference measurements; an indication of an orientation measurements; an indication of an object geometry -related characteristic; an indication of an object material-related characteristic; and an indication of an object other physical characteristics.

[0107] Embodiment 14. The method of any of Embodiments 12-13, wherein receiving the request for sensing measurement information comprises receiving a sensing measurement request, and wherein transmitting the message comprises transmitting at least one of: a sensing measurement response; a sensing measurement failure; and a sensing measurement update.

[0108] Embodiment 15. The method of any of Embodiments 12-14, wherein transmitting the message comprises transmitting an indication of an identity of a passive object associated with the sensing measurements.

[0109] Embodiment 16. The method of any of Embodiment 1-15, further comprising: receiving (3580) a sensing measurement abort message; andresponsive to receiving the sensing measurement abort message, ceasing (3590) to perform the sensing procedure.

[0110] Embodiment 17. The method of any of Embodiments 1-16, wherein the second network node comprises a core network, CN, node configured to provide a sensing management function, SeMF.

[0111] Embodiment 18. The method of any of Embodiments 1-17, wherein the first network node comprises a radio access network, RAN, node.

[0112] Embodiment 19. The method of Embodiment 18, wherein the RAN node comprises a distributed unit, DU, and wherein the second network node comprises a central unit, CU of the first network node.

[0113] Embodiment 20. The method of Embodiment 18, wherein the RAN node is configured to provide a central unit, CU, the method further comprising: transmitting (3610, 3710, 3730, 3760) the request for sensing information to a distributed unit, DU; responsive to transmitting the request for sensing information to the DU, receiving(3630, 3720, 3750, 3770) information from the DU; and determining the message based on the information.

[0114] Embodiment 21. A method of operating a second network node (4000), the method comprising: transmitting (3610, 3710, 3730, 3760) a request for sensing information from a first network node; and responsive to transmitting the request for the sensing information, receiving (3630, 3720, 3750, 3770) a message from the first network node.

[0115] Embodiment 22. The method of Embodiment 21, wherein the sensing information includes an indication of sensing capabilities of the first network node.

[0116] Embodiment 23. The method of Embodiment 22, wherein the sensing capabilities of the first network node comprises capabilities of one or more sensing radio units, SRUs, hosted by the first network node, the SRUs.

[0117] Embodiment 24. The method of any of Embodiments 22-23, wherein the sensing capabilities comprise an indication of a type of data that can be measured including at least one of:Third Generation Partnership Project, 3GPP, sensing data;Fifth Generation, 5G, Wireless sensing data;Human motion rate accuracy data; andNon-3GPP sensing data.

[0118] Embodiment 25. The method of any of Embodiments 21-24, wherein the request for sensing information includes an indication of one or more of: an identifier of a sensing radio unit, SRU; and an identifier of a cell associated with the SRU.

[0119] Embodiment 26. The method of any of Embodiments 21-25, wherein transmitting the request for sensing information comprises transmitting a sensing radio unit, SRU, Information Request, and wherein receiving the message comprises receiving at least one of: a SRU Information Response; and a SRU Information Failure.

[0120] Embodiment 27. The method of any of Embodiments 21-26, wherein transmitting the request for sensing information comprises transmitting a request for sensing configuration information for performing a sensing procedure.

[0121] Embodiment 28. The method of Embodiment 27, wherein the message include an indication of an identifier of a passive object in an environment of the first network node.

[0122] Embodiment 29. The method of Embodiment 28, wherein the identifier includes a time stamp associated with detection of the passive object.

[0123] Embodiment 30. The method of any of Embodiments 27-29, wherein the sensing configuration information includes an indication that the sensing procedure be performed at least one of: periodically; semi-periodically; and aperiodically.

[0124] Embodiment 31. The method of any of Embodiments 27-30, wherein transmitting the request for sensing configuration information comprises transmitting a sensing configuration request, and wherein receiving the message comprises transmitting at least one of: a sensing configuration response; a sensing configuration failure; a sensing configuration update; a sensing activation response; and a sensing configuration failure.

[0125] Embodiment 32. The method of any of Embodiments 21-31, wherein transmitting the request for sensing information comprises transmitting a request for sensing measurement information.

[0126] Embodiment 33. The method of Embodiment 32, wherein the message comprises the sensing measurement information including at least one of: an indication of a Number Of Reflected Paths; an indication of a RSRP per path; an indication of a peak-to-average power ratio; an indication of a Round trip type measurements; an indication of a time delay per path; an indication of an angle of departure; an indication of an angle of arrival per path; an indication of a doppler frequency; an indication of an acceleration measurements; an indication of a carrier phase measurements per path; an indication of a carrier phase difference measurements; an indication of an orientation measurements; an indication of an object geometry -related characteristic; an indication of an object material-related characteristic; and an indication of an object other physical characteristics.

[0127] Embodiment 34. The method of any of Embodiments 32-33, wherein transmitting the request for sensing measurement information comprises transmitting a sensing measurement request, and wherein receiving the message comprises receiving at least one of: a sensing measurement response; a sensing measurement failure; and a sensing measurement update.

[0128] Embodiment 35. The method of any of Embodiments 32-34, wherein receiving the message comprises receiving an indication of an identity of a passive object associated with the sensing measurements.

[0129] Embodiment 36. The method of any of Embodiment 21-35, further comprising: transmitting (3780) a sensing measurement abort message to cause the first network node to cease performing the sensing procedure.

[0130] Embodiment 37. The method of any of Embodiments 21-36, wherein the second network node comprises a core network, CN, node configured to provide a sensing management function, SeMF.

[0131] Embodiment 38. The method of any of Embodiments 21-37, wherein the first network node comprises a radio access network, RAN, node.

[0132] Embodiment 39. The method of Embodiment 38, wherein the RAN node comprises a distributed unit, DU, and wherein the second network node comprises a central unit, CU of the first network node.

[0133] Embodiment 40. A network node (4000), the communication device comprising: processing circuitry (4002); and memory (4006) coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the network node to perform operations comprising any of the operations of Embodiments 1-39.

[0134] Embodiment 41. A computer program comprising program code to be executed by processing circuitry (4002) of a network node (4000), whereby execution of the program code causes the network node to perform operations comprising any operations of Embodiments 1-39.

[0135] Embodiment 42. A computer program product comprising a non-transitory storage medium (4006) including program code to be executed by processing circuitry (4002) of a network node (4000), whereby execution of the program code causes the network node to perform operations comprising any operations of Embodiments 1-39.

[0136] FIG. 38 shows an example of a communication system 3800 in accordance with some embodiments.

[0137] In the example, the communication system 3800 includes a telecommunication network 3802 that includes an access network 3804, such as a radio access network (RAN), and a core network 3806, which includes one or more core network nodes 3808. The access network 3804 includes one or more access network nodes, such as network nodes 3810a and 3810b (one or more of which may be generally referred to as network nodes 3810), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. Moreover, as will be appreciated by those of skill in the art, the network nodes 3810 are 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 the network nodes 3810 may include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 3802 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 3802 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similarorganization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 3802, including one or more network nodes 3810 and / or core network nodes 3808.

[0138] 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 RAN control application (e.g., xApp) or a non-real time RAN automation application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Intents and content-aware notifications described herein may be communicated from a 3GPP network node or an ORAN network node over 3GPP-defined interfaces (e.g., N2, N3) and / or ORAN Alliance-defined interfaces (e.g., Al, 01). Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the 0-RAN Alliance. The network nodes 3810 facilitate direct or indirect connection of user equipment (UE), such as by connecting wireless devices 3812a, 3812b, 3812c, and 3812d (one or more of which may be generally referred to as UEs 3812) to the core network 3806 over one or more wireless connections. The network nodes 3810 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 3812a, 3812b, 3812c, and 3812d (one or more of which may be generally referred to as UEs 3812) to the core network 3806 over one or more wireless connections.

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

[0140] The UEs 3812 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 3810 and other communication devices. Similarly, the network nodes 3810 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 3812 and / or with other network nodes or equipment in the telecommunication network 3802 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 3802.

[0141] In the depicted example, the core network 3806 connects the network nodes 3810 to one or more hosts, such as host 3816. 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 3806 includes one more core network nodes (e.g., core network node 3808) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 3808. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0142] The host 3816 may be under the ownership or control of a service provider other than an operator or provider of the access network 3804 and / or the telecommunication network 3802, and may be operated by the service provider or on behalf of the service provider. The host 3816 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.

[0143] As a whole, the communication system 3800 of FIG. 38 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 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 othersuitable 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 (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low- power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0144] In some examples, the telecommunication network 3802 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 3802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 3802. For example, the telecommunications network 3802 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.

[0145] In some examples, the UEs 3812 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 3804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 3804. 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).

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

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

[0148] FIG. 39 shows a UE 3900 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over 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-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

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

[0150] The UE 3900 includes processing circuitry 3902 that is operatively coupled via a bus 3904 to an input / output interface 3906, a power source 3908, a memory 3910, a communication interface 3912, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG. 39. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0151] The processing circuitry 3902 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 3910. The processing circuitry 3902 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 3902 may include multiple central processing units (CPUs).

[0152] In the example, the input / output interface 3906 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 3900. 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.

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

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

[0155] The memory 3910 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 (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 3910 may allow the UE 3900 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 3910, which may be or comprise a device-readable storage medium.

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

[0157] In the illustrated embodiment, communication functions of the communication interface 3912 may include cellular communication, Wi-Fi communication, LPWAN communication, data 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 in 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 / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0158] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 3912, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

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

[0160] A UE, 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, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator orfreezer, 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 head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 3900 shown in FIG. 39.

[0161] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a 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.

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

[0163] FIG. 40 shows a network node 4000 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs,evolved Node Bs (eNBs), NRNodeBs (gNBs)), O-RAN nodes, or components of an O-RAN node (e.g., intelligent controller, O-RU, O-DU, O-CU).

[0164] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units 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).

[0165] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard 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).

[0166] The network node 4000 includes a processing circuitry 4002, a memory 4004, a communication interface 4006, and a power source 4008. The network node 4000 may be composed of multiple physically separate components (e.g., aNodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 4000 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 4000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 4004 for different RATs) and some components may be reused (e.g., a same antenna 4010 may be shared by different RATs). The network node 4000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 4000, for example GSM, WCDMA, LTE, NR, WiFi, 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 4000.

[0167] The processing circuitry 4002 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 network node 4000 components, such as the memory 4004, to provide network node 4000 functionality.

[0168] In some embodiments, the processing circuitry 4002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 4002 includes one or more of radio frequency (RF) transceiver circuitry 4012 and baseband processing circuitry 4014. In some embodiments, the radio frequency (RF) transceiver circuitry 4012 and the baseband processing circuitry 4014 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 4012 and baseband processing circuitry 4014 may be on the same chip or set of chips, boards, or units.

[0169] The memory 4004 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 4002. The memory 4004 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 4002 and utilized by the network node 4000. The memory 4004 may be used to store any calculations made by the processing circuitry 4002 and / or any data received via the communication interface 4006. In some embodiments, the processing circuitry 4002 and memory 4004 is integrated.

[0170] The communication interface 4006 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 4006 comprises port(s) / terminal(s) 4016 to send and receive data, for example to and from a network over a wired connection. The communication interface 4006 also includes radio front-end circuitry 4018 that may be coupled to, or in certain embodiments a part of, the antenna 4010. Radio front-end circuitry 4018 comprises filters 4020 and amplifiers 4022. The radio front-end circuitry 4018 may be connected to an antenna 4010 and processing circuitry 4002. The radio front-end circuitry may be configured to condition signals communicated between antenna 4010 and processing circuitry 4002. The radio front-endcircuitry 4018 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 4018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 4020 and / or amplifiers 4022. The radio signal may then be transmitted via the antenna 4010. Similarly, when receiving data, the antenna 4010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 4018. The digital data may be passed to the processing circuitry 4002. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0171] In certain alternative embodiments, the network node 4000 does not include separate radio front-end circuitry 4018, instead, the processing circuitry 4002 includes radio front-end circuitry and is connected to the antenna 4010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 4012 is part of the communication interface 4006. In still other embodiments, the communication interface 4006 includes one or more ports or terminals 4016, the radio front-end circuitry 4018, and the RF transceiver circuitry 4012, as part of a radio unit (not shown), and the communication interface 4006 communicates with the baseband processing circuitry 4014, which is part of a digital unit (not shown).

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

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

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

[0175] Embodiments of the network node 4000 may include additional components beyond those shown in FIG. 40 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 4000 may include user interface equipment to allow input of information into the network node 4000 and to allow output of information from the network node 4000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 4000.

[0176] FIG. 41 is a block diagram of a host 4100, which may be an embodiment of the host 3816 of FIG. 38, in accordance with various aspects described herein. As used herein, the host 4100 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 4100 may provide one or more services to one or more UEs.

[0177] The host 4100 includes processing circuitry 4102 that is operatively coupled via a bus 4104 to an input / output interface 4106, a network interface 4108, a power source 4110, and a memory 4112. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as FIGS. 39 and 40, such that the descriptions thereof are generally applicable to the corresponding components of host 4100.

[0178] The memory 4112 may include one or more computer programs including one or more host application programs 4114 and data 4116, which may include user data, e.g., data generated by a UE for the host 4100 or data generated by the host 4100 for a UE. Embodiments of the host 4100 may utilize only a subset or all of the components shown. The host application programs 4114 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 4114 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to acentral node, such as a device in or on the edge of a core network. Accordingly, the host 4100 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 4114 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0179] FIG. 42 is a block diagram illustrating a virtualization environment 4200 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 4200 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 4200 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.

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

[0181] Hardware 4204 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 4206 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 4208a and 4208b (one or more of which may be generally referred to as VMs 4208), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 4206 may present a virtual operating platform that appears like networking hardware to the VMs 4208.

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

[0183] In the context of NFV, a VM 4208 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 4208, and that part of hardware 4204 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 4208 on top of the hardware 4204 and corresponds to the application 4202.

[0184] Hardware 4204 may be implemented in a standalone network node with generic or specific components. Hardware 4204 may implement some functions via virtualization. Alternatively, hardware 4204 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 4210, which, among others, oversees lifecycle management of applications 4202. In some embodiments, hardware 4204 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 4212 which may alternatively be used for communication between hardware nodes and radio units.

[0185] FIG. 43 shows a communication diagram of a host 4302 communicating via a network node 4304 with a UE 4306 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 3812a of FIG. 38 and / or UE 3900 of FIG. 39), network node (such as network node 3810a of FIG. 38 and / or network node 4000 of FIG. 40), and host (such as host 3816 of FIG. 38 and / or host 4100 of FIG. 41) discussed in the preceding paragraphs will now be described with reference to FIG. 43.

[0186] Like host 4100, embodiments of host 4302 include hardware, such as a communication interface, processing circuitry, and memory. The host 4302 also includes software, which is stored in or accessible by the host 4302 and executable by the processingcircuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 4306 connecting via an over-the-top (OTT) connection 4350 extending between the UE 4306 and host 4302. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 4350.

[0187] The network node 4304 includes hardware enabling it to communicate with the host 4302 and UE 4306. The connection 4360 may be direct or pass through a core network (like core network 3806 of FIG. 38) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0188] The UE 4306 includes hardware and software, which is stored in or accessible by UE 4306 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 4306 with the support of the host 4302. In the host 4302, an executing host application may communicate with the executing client application via the OTT connection 4350 terminating at the UE 4306 and host 4302. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 4350 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 4350.

[0189] The OTT connection 4350 may extend via a connection 4360 between the host 4302 and the network node 4304 and via a wireless connection 4370 between the network node 4304 and the UE 4306 to provide the connection between the host 4302 and the UE 4306. The connection 4360 and wireless connection 4370, over which the OTT connection 4350 may be provided, have been drawn abstractly to illustrate the communication between the host 4302 and the UE 4306 via the network node 4304, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0190] As an example of transmitting data via the OTT connection 4350, in step 4308, the host 4302 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 4306. In other embodiments, the user data is associated with a UE 4306 that shares data with the host 4302 without explicit human interaction. In step 4310, the host 4302 initiates a transmission carrying the user data towards the UE 4306. The host 4302 may initiate the transmission responsive to a request transmitted by the UE 4306. The request may be caused by human interaction with the UE 4306 or by operation of the client application executing on the UE 4306. The transmission may pass via the network node 4304, in accordance with the teachings of theembodiments described throughout this disclosure. Accordingly, in step 4312, the network node 4304 transmits to the UE 4306 the user data that was carried in the transmission that the host 4302 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 4314, the UE 4306 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 4306 associated with the host application executed by the host 4302.

[0191] In some examples, the UE 4306 executes a client application which provides user data to the host 4302. The user data may be provided in reaction or response to the data received from the host 4302. Accordingly, in step 4316, the UE 4306 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 4306. Regardless of the specific manner in which the user data was provided, the UE 4306 initiates, in step 4318, transmission of the user data towards the host 4302 via the network node 4304. In step 4320, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 4304 receives user data from the UE 4306 and initiates transmission of the received user data towards the host 4302. In step 4322, the host 4302 receives the user data carried in the transmission initiated by the UE 4306.

[0192] One or more of the various embodiments improve the performance of OTT services provided to the UE 4306 using the OTT connection 4350, in which the wireless connection 4370 forms the last segment. More precisely, the teachings of these embodiments may enable sensing procedures in NR architectures including disaggregated and non-diaggregated gNB architecture.

[0193] In an example scenario, factory status information may be collected and analyzed by the host 4302. As another example, the host 4302 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 4302 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 4302 may store surveillance video uploaded by a UE. As another example, the host 4302 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 4302 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0194] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection4350 between the host 4302 and UE 4306, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 4302 and / or UE 4306. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 4350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 4350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 4304. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 4302. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 4350 while monitoring propagation times, errors, etc.

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

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

Claims

CLAIMSWhat is claimed is:

1. A method of operating a first network node (4000), the method comprising: receiving (3410, 3510, 3530, 3560) a request for sensing information from a second network node; and responsive to receiving the request for the sensing information, transmitting (3420, 3530, 3550, 3570) a message to the second network node.

2. The method of Claim 1, wherein receiving the request for sensing information comprises receiving a request for the sensing capability information indicating sensing capabilities of the first network node.

3. The method of Claim 2, wherein the sensing capabilities of the first network node comprises capabilities of one or more sensing radio units, SRUs, hosted by the first network node, the SRUs.

4. The method of any of Claims 2-3, wherein the sensing capabilities comprise an indication of a type of data that can be measured including at least one of:Third Generation Partnership Project, 3GPP, sensing data;Fifth Generation, 5G, Wireless sensing data;Human motion rate accuracy data; andNon-3GPP sensing data.

5. The method of any of Claims 2-4, wherein the request for sensing information includes an indication of one or more of: an identifier of a sensing radio unit, SRU; and an identifier of a cell associated with the SRU.

6. The method of any of Claims 2-5, wherein receiving the request for sensing capability information comprises receiving a sensing radio unit, SRU, Information Request, and wherein transmitting the message comprises transmitting at least one of: a SRU Information Response; and a SRU Information Failure.

7. The method of any of Claims 1-6, wherein receiving the request for sensing information comprises receiving a request for sensing configuration information for performing a sensing procedure.

8. The method of Claim 7, further comprising: determining (3540) an identifier for a passive object within an environment of the first network node, wherein the message include an indication of the identifier.

9. The method of Claim 8, wherein the identifier includes a time stamp associated with detection of the passive object.

10. The method of any of Claims 7-9, wherein the sensing configuration information includes an indication that the sensing procedure be performed at least one of: periodically; semi-periodically; and aperiodically.

11. The method of any of Claims 7-10, wherein receiving the request for sensing configuration information comprises receiving a sensing configuration request, and wherein transmitting the message comprises transmitting at least one of: a sensing configuration response; a sensing configuration failure; a sensing configuration update; a sensing activation response; and a sensing configuration failure.

12. The method of any of Claims 1-11, wherein receiving the request for sensing information comprises receiving a request for sensing measurement information.

13. The method of Claim 12, wherein the message comprises the sensing measurement information including at least one of: an indication of a Number Of Reflected Paths; an indication of a RSRP per path;an indication of a peak-to-average power ratio; an indication of a Round trip type measurements; an indication of a time delay per path; an indication of an angle of departure; an indication of an angle of arrival per path; an indication of a doppler frequency; an indication of an acceleration measurements; an indication of a carrier phase measurements per path; an indication of a carrier phase difference measurements; an indication of an orientation measurements; an indication of an object geometry -related characteristic; an indication of an object material-related characteristic; and an indication of an object other physical characteristics.

14. The method of any of Claims 12-13, wherein receiving the request for sensing measurement information comprises receiving a sensing measurement request, and wherein transmitting the message comprises transmitting at least one of: a sensing measurement response; a sensing measurement failure; and a sensing measurement update.

15. The method of any of Claims 12-14, wherein transmitting the message comprises transmitting an indication of an identity of a passive object associated with the sensing measurements.

16. The method of any of Claim 1-15, further comprising: receiving (3580) a sensing measurement abort message; and responsive to receiving the sensing measurement abort message, ceasing (3590) to perform the sensing procedure.

17. The method of any of Claims 1-16, wherein the second network node comprises a core network, CN, node configured to provide a sensing management function, SeMF.

18. The method of any of Claims 1-17, wherein the first network node comprises a radio access network, RAN, node.

19. The method of Claim 18, wherein the RAN node comprises a distributed unit, DU, and wherein the second network node comprises a central unit, CU of the first network node.

20. The method of Claim 18, wherein the RAN node is configured to provide a central unit, CU, the method further comprising: transmitting (3610, 3710, 3730, 3760) the request for sensing information to a distributed unit, DU; responsive to transmitting the request for sensing information to the DU, receiving (3630, 3720, 3750, 3770) information from the DU; and determining the message based on the information.

21. A method of operating a second network node (4000), the method comprising: transmitting (3610, 3710, 3730, 3760) a request for sensing information from a first network node; and responsive to transmitting the request for the sensing information, receiving (3630, 3720, 3750, 3770) a message from the first network node.

22. The method of Claim 21, wherein the sensing information includes an indication of sensing capabilities of the first network node.

23. The method of Claim 22, wherein the sensing capabilities of the first network node comprises capabilities of one or more sensing radio units, SRUs, hosted by the first network node, the SRUs.

24. The method of any of Claims 22-23, wherein the sensing capabilities comprise an indication of a type of data that can be measured including at least one of:Third Generation Partnership Project, 3GPP, sensing data;Fifth Generation, 5G, Wireless sensing data;Human motion rate accuracy data; and Non-3GPP sensing data.

25. The method of any of Claims 21-24, wherein the request for sensing information includes an indication of one or more of:an identifier of a sensing radio unit, SRU; and an identifier of a cell associated with the SRU.

26. The method of any of Claims 21-25, wherein transmitting the request for sensing information comprises transmitting a sensing radio unit, SRU, Information Request, and wherein receiving the message comprises receiving at least one of: a SRU Information Response; and a SRU Information Failure.

27. The method of any of Claims 21-26, wherein transmitting the request for sensing information comprises transmitting a request for sensing configuration information for performing a sensing procedure.

28. The method of Claim 27, wherein the message include an indication of an identifier of a passive object in an environment of the first network node.

29. The method of Claim 28, wherein the identifier includes a time stamp associated with detection of the passive object.

30. The method of any of Claims 27-29, wherein the sensing configuration information includes an indication that the sensing procedure be performed at least one of: periodically; semi-periodically; and aperiodically.

31. The method of any of Claims 27-30, wherein transmitting the request for sensing configuration information comprises transmitting a sensing configuration request, and wherein receiving the message comprises transmitting at least one of: a sensing configuration response; a sensing configuration failure; a sensing configuration update; a sensing activation response; and a sensing configuration failure.

32. The method of any of Claims 21-31, wherein transmitting the request for sensinginformation comprises transmitting a request for sensing measurement information.

33. The method of Claim 32, wherein the message comprises the sensing measurement information including at least one of: an indication of a Number Of Reflected Paths; an indication of a RSRP per path; an indication of a peak-to-average power ratio; an indication of a Round trip type measurements; an indication of a time delay per path; an indication of an angle of departure; an indication of an angle of arrival per path; an indication of a doppler frequency; an indication of an acceleration measurements; an indication of a carrier phase measurements per path; an indication of a carrier phase difference measurements; an indication of an orientation measurements; an indication of an object geometry -related characteristic; an indication of an object material-related characteristic; and an indication of an object other physical characteristics.

34. The method of any of Claims 32-33, wherein transmitting the request for sensing measurement information comprises transmitting a sensing measurement request, and wherein receiving the message comprises receiving at least one of: a sensing measurement response; a sensing measurement failure; and a sensing measurement update.

35. The method of any of Claims 32-34, wherein receiving the message comprises receiving an indication of an identity of a passive object associated with the sensing measurements.

36. The method of any of Claim 21-35, further comprising: transmitting (3780) a sensing measurement abort message to cause the first network node to cease performing the sensing procedure.

37. The method of any of Claims 21-36, wherein the second network node comprises a corenetwork, CN, node configured to provide a sensing management function, SeMF.

38. The method of any of Claims 21-37, wherein the first network node comprises a radio access network, RAN, node.

39. The method of Claim 38, wherein the RAN node comprises a distributed unit, DU, and wherein the second network node comprises a central unit, CU of the first network node.

40. A network node (4000) adapted to perform operations comprising any of the operations of Claims 1-39.

41. A computer program comprising program code to be executed by processing circuitry (4002) of a network node (4000), whereby execution of the program code causes the network node to perform operations comprising any operations of Claims 1-3942. A computer program product comprising a non-transitory storage medium (4006) including program code to be executed by processing circuitry (4002) of a network node (4000), whereby execution of the program code causes the network node to perform operations comprising any operations of Claims 1-39.

Images