Discovery and selection of UES for assisting with sensing services
By allowing UEs to indicate sensing capabilities during registration and using AMF event exposure services, the solution addresses the challenge of selecting sensing-capable UEs, enhancing the network's ability to provide sensing services effectively.
Patent Information
- Application Number
- PCT/EP2026/060981
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-04-16
- Publication Date
- 2026-11-12
AI Technical Summary
Current 3GPP systems lack a solution for discovering and distinguishing between sensing-capable User Equipments (UEs) and non-sensing-capable UEs to enable their selection for assisting with sensing services.
UEs indicate their sensing capabilities during registration, and a Sensing Core Function (SCF) uses an AMF event exposure service to identify and select sensing-capable UEs within a target area, enhancing the UE registration and AMF event exposure procedures.
Enables the network to discover and select sensing-capable UEs for assisting with requested sensing services, improving the efficiency and effectiveness of sensing service delivery.
Smart Images

Figure EP2026060981_12112026_PF_FP_ABST
Abstract
Description
Applicant's Ref.: P113729WO01 1DISCOVERY AND SELECTION OF UEs FOR ASSISTING WITH SENSING SERVICESTECHNICAL FIELD
[0001] The present disclosure relates to methods for managing a User Equipment (UE) to support and assist with sensing services.BACKGROUNDIntegrated Sensing and Communication (ISAC) in 3GPP
[0002] The 3rdGeneration Partnership Project (3GPP) System Architecture Working Group 2 (SA2) has agreed to a study Integrated Sensing and Communication (ISAC) (FS_Sensing_ARC) in Release-20. The Study Item Description (SID) (see 3GPP SID Wl # 1070012 - FS_Sensing_ARC, v. SP-250401) lists six different Work Tasks (WTs) that the study will cover, as follows:WT-1: Architecture and function enhancements to support sensing.WT-2: Service authorization and revocation. This includes investigating mechanisms for authorization and revocation sensing service requests from the service consumer.WT-3: Discovery and selection of sensing entities based on service requirements triggered by the service request and capability of the sensing entities.WT-4: Sensing data and the associated information collection and transport mechanisms for result calculation. WT-5: Mechanisms for providing sensing associated information and result (including sensing result and contextual information) exposure, for one time, periodic or event-based reporting.WT-6: Configuration parameters / policy provisioning for the support of ISAC services.
[0003] WT-3 is addressed in the study described in 3GPP Technical Report (TR) 23.700-14, v. 0.1.0 in clause 5.3 Key Issue #3: Sensing Entity and Sensing Function Discovery and (Re-)Selection. Two objectives in this key issue that will be studied are:• Which entity(ies) performs the discovery and (re-)selection of the Sensing entity(ies); and• What the information and / or criteria are taken into account for the discovery and (re-)selection of the Sensing entity (ies).
[0004] In the context of present disclosure and 3GPP TR 23.700-14, a Sensing Entity can be eventually considered as a part of a Radio Access Network (RAN) node or a User Equipment (UE). This present disclosure relates to a scenario when UEs aim at assisting with the sensing service requested by the consumer from the network.UE Registration in 3GPP network
[0005] In a 3GPP 5thGeneration (5G) system, as described in 3GPP TS 23.502, v.19.3.0, a UE registers itself to the network to be authorized to use and enable services offered by the network, e.g., mobility tracking, and reachability. The registration procedure is described in 3GPP TS 23.502 clause 4.2.2.2.2. When the UE initiates the registration procedure by sending a Registration Request to the RAN, the UE also indicates its support of capabilities to theApplicant's Ref.: P113729WO01 2network. These capabilities are stored by the network. An example of parameters (capabilities) included in the Registration Request sent by the UE to the RAN is provided in the excerpt from clause 4.2.2.2.2 of 3GPP TS 23.502 below (emphasis added via bold text). The UE can set these parameters in order to achieve a certain behavior from the network.# - excerpt from clause 4.2.2.2.2 of TS 23.502 - # The UE may provide the UE’s usage setting based on its configuration as defined in clause 5.16.3.7 ofTS 23.501 [2], The UE provides Requested NSSAI (as described in clause 5.15.5.2.1 of TS 23.501 [2] and if the UE supports the subscription-based restrictions to simultaneous registration of network slices, also taking into account the NSSRG Information constraints as described in clause 5.15.12 of TS 23.501 [2] and in the case of Initial Registration or Mobility Registration Update, the UE includes the Mapping Of Requested NSSAI (if available), which is the mapping of each S-NSSAI of the Requested NSSAI to the HPLMN S-NSSAIs, to ensure that the network is able to verify whether the S-NSSAI(s) in the Requested NSSAI are permitted based on the Subscribed S-NSSAIs. If the Network Slice Replacement is used and the UE is configured with Mapping Of Alternative NSSAI, the Requested NSSAI may include Alternative S-NSSAI(s). If the AMF determines that S-NSSAI(s) that the UE requests are not Alternative S-NSSAI(s) in the UE context and not Subscribed S-NSSAIs, the AMF determines to update the UE configuration as described in clause 5.15.19 of TS 23.501 [2], In the case of inter PLMN mobility, if the serving PLMN S-NSSAI(s) corresponding to the established PDU Session(s) are not present in the UE, the associated HPLMN S-NSSAI(s) associated with the established PDU Session(s) shall be provided in the Mapping Of Requested NSSAI as described in clause 5.15.5.2.1 TS 23.501 [2], If the UEs supports reconnection to the network due to RAN timing synchronization status change as described in TS 23.501 [2], the UE indicates the support of this capability to the network. If the UE supports UE configuration of network-controlled Slice Usage Policy and the UE stores Slice Usage Policy, the UE shall include an on demand S-NSSAI in the Requested NSSAI only when applications in the UE require data transmission by a PDU session associated with the on demand S-NSSAI as described in clause 5.15.15 of TS 23.501 [2],# - #
[0006] Thus, one of the examples of a UE indicating its support of a certain capability is the UEs indication of support for "reconnection to the network due to RAN timing synchronization status change”. Other capabilities can also be indicated as described in the excerpt above.AMF event exposure in 3GPP networks
[0007] The Access and Mobility Management Function (AMF) in the 5G Core of the 5G system offers an event exposure service (see 3GPP TS 23.502). This service enables the consumer to subscribe to an event and get notifications. Events that are supported in this service are e.g., Loss of Connectivity, UE reachability, Location Reporting, UE moving in or out of Area of Interest, and UEs present in a geographical area. Examples of Event Filters for AMF exposure events can be seen in the table in the excerpt from 3GPP TS 23.502 below (emphasis added via bold text).# - excerpt from table 5.2.2.3.1-lof TS 23.502 - #Event ID Event Filter (List of Parameter Values to Match) Location Report <Parameter Type = LocationFilter, Value = TA1>UE moving in or out of Area of Interest <Parameter Type = TAI, Value = TA1><Parameter Type = S-NSSAI, Value = S- NSSAI1><Parameter Type = NSI ID, Value = NSI ID1 >Applicant's Ref.: P113729WO01 3<Parameter Type = PRA ID, Value = PRA ID value><Parameter Type = RAN Node ID, Value = RAN Node ID value><Parameter Type = Cell ID, Value = Cell ID value><Parameter Type = RAN timing synchronization status change event >(NOTE 1) (NOTE 2)<Parameter Type = Adjust Aol based on RA, Value = Yes or No> to indicate that AMF may adjust the received Aol depending on UE's current Registration Area. Absence of this parameter in the request is interpreted as "Aol remains unchanged".<Parameter Type = Notify the consumer considering UE identity, Value = List of SUPIs or Internal Group ID > The parameter may be included when the request is targeted to Any UE. Absence of this parameter in the request is interpreted as "AMF reports an event regardless to UE's identity triggering the event".(NOTE 2)<Parameter Type = Notify the consumer considering DNN / S-NSSAI, Value = DNN and / or S-NSSAI> Absence of this parameter in the request is interpreted as "AMF reports the event without checking to which DNN / S-NSSAI the UE has PDU sessions established".(NOTE 2)Access Type <Parameter Type=AN Type, Value=3GPP Access">Location <Parameter Type=TAI, Value=wildcard> (to report any TAI change)Location <Parameter Type=TAI Value=abnormal> (to report only when the TAI deviates from expected values based on Expected UE Moving Trajectory).Assigned Trajectory <Parameter Type = Notify when the UE deviates from the assigned trajectory, Value=TAI, Scheduled Time in a particular TA and / or Height> (to report only when the UE deviates from the assigned values of TAI, Scheduled Time in a particular TA and / or moves outside the altitude range based on the assigned flight plan).The assigned trajectory may consist of multiple segments identified by geographical areas that, for instance, are served by different UAV Service Suppliers. In this case, the information of each segment shall be provided.<Parameter Type = Notify when the altitude reporting conditions are met, Value=altitude thresholds, reporting periodicity>(NOTE 4)Reachability Filter Applicable to the event UE reachability. Value =UE reachability status change or UE reachable for DL traffic. Absence of this parameter in UE reachability event request is interpreted as "UE reachability status change".Total number of Transactions <Parameter Type = TAI, Value = TA1><Parameter Type = S-NSSAI, Value = S-NSSAI1> Number of UEs present in a geographical area <Parameter Type = UE Type, Value = Aerial UE><Parameter Type = PDU session status, Value = PDU session established for DNN subject to aerial services><Parameter Type = LCS broadcastingassistance data type, Value = A bitmapApplicant's Ref.: P113729WO01 4indicates broadcast location assistance datatypes for which the UE is subscribed to receive ciphering keys to decipher broadcastassistance data (see Table 7.1-3 in clause 7.1 ofTS 23.273
[0051] and clause 6.1.6.2.72 ofTS 29.503
[0052] )>NOTE 1 : The Parameter Type = RAN timing synchronization status change event can be present with Parameter Type defining a RAN Node ID.NOTE 2: The use of event filter parameters is described in clause 5.3.4.4 of TS 23.501 [2],NOTE 3: The mapping relationship between the LCS broadcasting assistance data element and corresponding positioning SIB type is described in clause 7.2 of TS 37.355
[0056] ,NOTE 4: Filter information for the events is provided as a set of TAI, Scheduled Time and / or Heightvalues for each of the trajectory segments assigned to the UE / UAV, see clause 5.13 ofTS 23.256
[0080] ,NOTE 5: Procedures related to reporting altitude information of aerial UEs are specified in clause 5.16of TS 23.256 [801.# - #
[0008] When subscribing to the AMF for event exposure and filtering using these events (e.g., UE moving in or out of Area of Interest or Number of UEs present in a geographical area), UEs can be found and tracked within a specific area. In the context of the present disclosure, two AMF events are of particular interest: UE moving in or out of Area of Interest and Number of UEs present in a geographical areaSUMMARY
[0009] In view of the discussion in the background section above a solution is needed to distinguish between and preferably discover wireless devices such as UEs that are sensing capable and those that are not, such that the sensing capable wireless devices can be selected by the network (e.g. by a core network handling the sensing service, or by a NG-RAN node) for assisting with the requested sensing service.
[0010] This may be accomplished in that such devices indicate their sensing capability during registration towards an NG-RAN and / or a network function such as an AMF. A list containing these sensing capable UEs can then be created and used to enable the sensing service for requesting sensing service consumers.BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.Figure 1 illustrates one example of a cellular communications system 100 in which embodiments of the present disclosure may be implemented;Figure 2 illustrates proposed enhancements to support selection of UE(s) or similar capable of sensing, in accordance with some embodiments of the present disclosure;Figure 3 illustrates a modified version of the UE registration procedure specified in 3GPP TS 23.502;Figure 4 xxx shows a request for a UE's AMF Registration Information for 3GPP Access;Applicant's Ref.: P113729WO01 5Figure 5 illustrates a wireless communication system represented as a 5G architecture (i.e. a 5GS) including core Network Functions (NFs);Figure 6 illustrates a 5G architecture using service-based interfaces between the NFs in the CP, instead of the point- to-point reference points / interfaces used in the 5G architecture of Figure 5,Figure 7 is a schematic block diagram of a network node 700 according to some embodiments of the present disclosure;Figure 8 is a schematic block diagram that illustrates a virtualized embodiment of the network node 700 according to some embodiments of the present disclosure;Figure 9 is a schematic block diagram of a UE 112 according to some embodiments of the present disclosure.DETAILED DESCRIPTION
[0012] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.
[0013] 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.
[0014] There currently exist certain challenge(s). Currently, no solution addressing Key Issue #3 (Sensing Entity and Sensing Function Discovery and (Re-)Selection) of 3GPP TR 23.700-14 has been proposed. A solution is needed to discover and distinguish between sensing capable User Equipments (UEs) and UEs that are not sensing capable so that the sensing capable UEs can be selected by the network (selected by, e.g., a core network function handling the sensing service or by a Radio Access Network (RAN) node such as, for example, a Next Generation RAN (NG-RAN) node) for assisting with the requested sensing service.
[0015] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Systems and methods are disclosed herein that relate to a scenario in which a Sensing EntityZ(ies) is(are) a UE(s). In an embodiment of the solution(s) described herein, a Sensing Core Function (SCF) invokes an AMF event exposure service(s), which may be a single service of a combination of UEs present in an Area of Interest and / or Number of UEs present in a geographical area, to get a list of UEs in a target area for sensing. One or more UEs that have indicated sensing capabilities, e.g., during UE registration are selected. The selection can be performed either by AMF, in which case the AMF provides to the SCF via the AMF event exposure service(s) a list of (selected) UEs that have indicated sensing capabilities, or by the SCF, in which case the SCF selects UEs from a list of UEs returned by the AMF to select only UEs that have indicated sensing capabilities.
[0016] UEs indicate sensing capabilities (i.e., capability of sensing), i.e., the capability to be able to act as sensing entities, during UE registration towards a RAN (e.g., NG-RAN) and AMF. In one embodiment, the SCF sends a request to the AMF for event exposure to receive a list of sensing-capable UEs present in the Area of Interest (i.e., the targetApplicant's Ref.: P113729WO01 6sensing area). In another embodiment, the SCF filters out the sensing capable UEs from a list of UEs present in Area of Interest (i.e., the target sensing area) received from the AMF via the AMF’s event exposure service. The list containing only these sensing capable UEs is then used to enable the sensing service to the requesting sensing service consumer.
[0017] Certain embodiments may provide one or more of the following technical advantage(s). Embodiments of the solution(s) described herein may enable the network (e.g., SCF and / or RAN (e.g., NG-RAN) node) to discover Sensing EntityZ(ies) using an AMF event exposure service to identify UEs or track UEs within a target area for sensing by enabling and enhancing the UE Registration procedure of a UE and AMF event exposure procedure. In this manner, the RAN, AMF, and / or SCF is able to discover sensing capable entities.
[0018] Note that the description herein uses a 5G system as an example and as such 5G terminology is used. However, the solution(s) described herein are not limited to 5G and can be used for future generations (e.g., 6G), in which case it is to be understood that the 5G terminology used herein is to be construed so as to include the corresponding terminology in 6G or beyond. For example, the term "AMF” used herein is to be understood so as to encompass the 6G network function that performs the functionality of the AMF described herein.Figure 1
[0019] Figure 1 illustrates one example of a cellular communications system 100 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system 100 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC). Note, however, that the solution(s) described herein are equally appliable to future generations (e.g., 6G). In this example, the RAN includes RAN nodes 102-1 and 102-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs), controlling corresponding (macro) cells 104-1 and 104-2. The RAN nodes 102-1 and 102-2 are generally referred to herein collectively as RAN nodes 102 and individually as RAN node 102. Likewise, the (macro) cells 104-1 and 104-2 are generally referred to herein collectively as (macro) cells 104 and individually as (macro) cell 104. The RAN may also include a number of low power nodes 106-1 through 106-4 controlling corresponding small cells 108-1 through 108-4. The low power nodes 106-1 through 106-4 can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like. Notably, while not illustrated, one or more of the small cells 108-1 through 108-4 may alternatively be provided by the RAN nodes 102. The low power nodes 106-1 through 106-4 are generally referred to herein collectively as low power nodes 106 and individually as low power node 106. Likewise, the small cells 108-1 through 108-4 are generally referred to herein collectively as small cells 108 and individually as small cell 108. The cellular communications system 100 also includes a core network 110, which in the 5G System (5GS) is referred to as the 5GC. The RAN nodes 102 (and optionally the low power nodes 106) are connected to the core network 110. The core network 110 includes various core network nodes (i.e., core network functions or network nodes that implement core network functions), as will be appreciated by those of ordinary skill in the art.
[0020] The RAN nodes 102 and the low power nodes 106 provide service to User Equipments (UEs) 112-1 through 112-5 in the corresponding cells 104 and 108. The UEs 112-1 through 112-5 are generally referred to herein collectively as UEs 112 and individually as UE 112.Applicant's Ref.: P113729WO01 7Figure 5
[0021] Figure 5 illustrates a wireless communication system represented as a 5G architecture corresponding to a 5G system (5GS) including a 5G core network (5GC) with core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point / interface. Figure 5 can be viewed as one particular implementation of the system 100 of Figure 1.
[0022] Seen from the access side the 5G network architecture shown in Figure 5 comprises a plurality of UEs 112 connected to either a RAN 102 or an Access Network (AN) as well as an AMF 500. Typically, the R(AN) 102 comprises base stations, e.g. such as eNBs or gNBs or similar. Seen from the core network side, the 5GC NFs shown in Figure 5 include a NSSF 502, an AUSF 504, a UDM 506, the AMF 500, a SMF 508, a PCF 510, and an Application Function (AF) 512.
[0023] Reference point representations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N1 reference point is defined to carry signaling between the UE 112 and AMF 500. The reference points for connecting between the AN 102 and AMF 500 and between the AN 102 and UPF 514 are defined as N2 and N3, respectively. There is a reference point, N11, between the AMF 500 and SMF 508, which implies that the SMF 508 is at least partly controlled by the AMF 500. N4 is used by the SMF 508 and UPF 514 so that the UPF 514 can be set using the control signal generated by the SMF 508, and the UPF 514 can report its state to the SMF 508. N9 is the reference point for the connection between different UPFs 514, and N14 is the reference point connecting between different AMFs 500, respectively. N15 and N7 are defined since the PCF 510 applies policy to the AMF 500 and SMF 508, respectively. N12 is required for the AMF 500 to perform authentication of the UE 112. N8 and N10 are defined because the subscription data of the UE 112 is required for the AMF 500 and SMF 508.
[0024] The 5GC network aims at separating UP and CP. The UP carries user traffic while the CP carries signaling in the network. In Figure 5, the UPF 514 is in the UP and all other NFs, i.e., the AMF 500, SMF 508, PCF 510, AF 512, NSSF 502, AUSF 504, and UDM 506, are in the CP. Separating the UP and CP guarantees each plane resource to be scaled independently. It also allows UPFs to be deployed separately from CP functions in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency.
[0025] The core 5G network architecture is composed of modularized functions. For example, the AMF 500 and SMF 508 are independent functions in the CP. Separated AMF 500 and SMF 508 allow independent evolution and scaling. Other CP functions like the PCF 510 and AUSF 504 can be separated as shown in Figure 5. Modularized function design enables the 5GC network to support various services flexibly.
[0026] Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the CP, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The UP supports interactions such as forwarding operations between different UPFs.Applicant's Ref.: P113729WO01 8Figure 6
[0027] Figure 6 illustrates a 5G network architecture corresponding to a 5GS using service-based interfaces between the NFs in the control plane (CP) of the core network, instead of the point-to-point reference points / interfaces used in the 5G network architecture of Figure 5. However, the NFs described above with reference to Figure 5 correspond to the NFs shown in Figure 6. The service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface. In Figure 6 the service based interfaces are indicated by the letter “N” followed by the name of the NF, e.g. Namf for the service based interface of the AMF 500 and Nsmf for the service based interface of the SMF 508, etc. The NEF 600 and the NRF 602 in Figure 6 are not shown in Figure 5 discussed above. However, it should be clarified that all NFs depicted in Figure 5 can interact with the NEF 600 and the NRF 602 of Figure 6 as necessary, though not explicitly indicated in Figure 5.
[0028] Some properties of the NFs shown in Figures 5 and 6 may be described in the following manner. The AMF 500 provides UE-based authentication, authorization, mobility management, etc. A UE 112 even using multiple access technologies is basically connected to a single AMF 500 because the AMF 500 is independent of the access technologies. The SMF 508 is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF 514 for data transfer. If a UE 112 has multiple sessions, different SMFs 508 may be allocated to each session to manage them individually and possibly provide different functionalities per session. The AF 512 provides information on the packet flow to the PCF 510 responsible for policy control in order to support QoS. Based on the information, the PCF 510 determines policies about mobility and session management to make the AMF 500 and SMF 508 operate properly. The AUSF 504 supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM 506 stores subscription data of the UE 112. The Data Network (DN), not part of the 5GC network, provides Internet access or operator services and similar.
[0029] An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.
[0030] Embodiments of the proposed solution encompass two options:• Option 1: Only RAN is made aware of UE’s sensing capabilities (see, e.g., Step 1 in Figure 2);• Option 2: Both RAN and Sensing Core Function (SCF) are made aware of UE’s sensing capabilities (see, e.g., Steps 1-7 in Figure 2).Figure 2
[0031] Figure 2 illustrates proposed enhancements to support selection of UE(s) capable of sensing, in accordance with embodiments of the present disclosure. Steps depicted in Figure 2 are described below, followed by a more detailed explanation of each proposed addition. The steps of the procedure of Figure 2 are as follows:• Step 1: The UE Registration procedure described in 3GPP TS 23.502 is adapted to support UE indication of sensing capabilities. Proposed additions to the procedure are described in Section 1 below referring to TS 23.502 clause 4.2.2.2.2 and to figure 3 herein. In other words, in Step 1, the UE performs UE registration with the RAN (i.e., with a RAN node) and the AMF. During the UE registration, the UE provides, to the RANApplicant's Ref.: P113729WO01 9and / or the AMF, an indication that indicates that the UE has sensing capabilities. Note that if the UE did not have sensing capabilities, then the UE would not provide this indication of sensing capabilities. In one example, the indication of sensing capabilities may only be present if the UE has sensing capabilities. In another example, the indication may be sent to a first value (e.g., True) to indicate that the UE has sensing capabilities or otherwise set to a second value (e.g., False).• Step 2: The SCF invokes an AMF event exposure service (e.g., Namf_Event_Exposure service) to discover UEs in an Area of Interest (i.e. , in a target sensing area). In one embodiment, the SCF may, as per a proposed enhancement, include a "Sensing-capable UE” indication as an event filter. In another embodiment, no such sensing-capable UE indication is included as an event filter. Proposed additions to the Event_Exposure service are described in Section 2 below.• Step 3: The AMF authorizes the request and generates a list of UE(s) within the requested Area of Interest.If the request from SCF includes the "Sensing-capable UE” indication as an event filter, the AMF may perform filtering such that the list of UE(s) includes only sensing-capable UE(s).• Step 4: The AMF responds to SCF with the list of UEs in the Area of Interest, optionally including only UE(s) with sensing capabilities.• Step 5: If the list of UEs was not filtered based on sensing capabilities by the AMF, the SCF invokes a service from the Unified Data Management (UDM) (e.g. the NudmJJECM service) to obtain information about the sensing capabilities of each UE in the list. The assumption is that the indication of UE’s sensing capabilities has been stored in the UE Context with the UDM during UE registration, as suggested in Step 1. In one embodiment, a sensing capability indication is included in the NudmJJECM service request / response, specifying that only that particular information element from the stored UE Context is requested / included in the service response (see, e.g., Section 3 below).• Step 6: The UDM responds to SCF with UE’s sensing capability indication.• Step 7: The SCF generates a list of sensing-capable UEs.• Step 8: Sensing service is performed using the list of sensing-capable UEs.1 UE Registration Procedure EnhancementsFigure 3
[0032] Figure 3 illustrates a modified version of the UE registration procedure specified in 3GPP TS 23.502, Clause 4.2.2.2.2. The enhanced steps of the UE registration procedure of Figure 3 are marked with callouts and detailed as follows:Step 1: A UE sends a Registration Request to an NG-RAN node. In addition to the conventional information included in the Registration Request, the Registration Request also includes the indication about the UE’s sensing capabilities.Applicant's Ref.: P113729WO01 10• Step 3: After selecting an AMF in Step 2, the NG-RAN sends to the selected AMF an N2 message with Registration Request parameters including the indication of UE’s sensing capabilities included in the Registration Request of Step 1.• Step 14: The AMF registers with the UDM using Nudm_UECM_Registration for the access to be registered. As part of this registration, the AMF provides the sensing capability indication to the UDM, where the sensing capability indication is stored as part of the UE context of the UE.
[0033] While it is not essential for understanding the solution(s) disclosed herein, for further information regarding the UE registration procedure of Figure 3, the interested reader is directed to 3GPP TS 23.502, Clause 4.2.2.2.2.2 Event Exposure Operation Enhancements
[0034] To discover UEs in the Area of Interest, optionally filtered by their sensing capabilities, the SCF invokes the Namf_EventExposure of the AMF.
[0035] As specified in 3GPP TS 23.502, Clause 5.2.2.3.2, the subscription request, which in the present disclosure is sent from the SCF to the AMF, includes the Target of Event Reporting (Subscription Permanent Identifier (SUPI) or Internal Group Identifier or indication that any UE is targeted), Event ID, and optional Event Filters, among other parameters that are not highlighted since they are not relevant for proposed solution.
[0036] This solution proposes the use of the parameters mentioned as follows:• Target of Event Reporting: SUPI or Internal Group Identifier if target UE IDs are known or "any UE” indication if the request does not specify a particular UE ID (parameter already existing in the standard)• Event ID: Number of UEs present in a geographical area (parameter already existing in the standard) • Event Filters: A new value of UE Type parameter is proposed - "Sensing-capable UE”, to indicate to the AMF that the request is for UEs in the Area of Interest and with sensing capabilities.
[0037] The subscription notification returned from the AMF to, in the present disclosure, the SCF contains an AMF Event Report and includes a ueldExtList parameter, listing multiple UE IDs, as specified in 3GPP TS 29.518 V19.2.0. In an embodiment of the present disclosure, the applicability of the parameter is extended from only ENA (Enablers for Network Automation) to both ENA and Sensing.# - excerpt from Table 6.2.6.2.5-1 of TS 29.518 - #Applicant's Ref.: P113729WO01 11Attribute name Data type P Cardinality Description Applicability ueldExtList array(UEIdExt) C 1..N This IE shall be present if multiple SUPIs ENAand / or GPSIs need to be included andthe subscribing NF indicated support ofthe ENA feature, unless the subscribingNF indicated to omit UE IDs in the eventreports by including ueldOmitlnd IE withthe value true.This attribute provides additional SUPIsand / or GPSIs to the supi attribute orgpsi attribute if present. The ueldExtListattribute may be present even if both thesupi and gpsi attributes are absent, e.g.,in a report of "UES_IN_AREA_REPORT"or "PRESENCE_IN_AOI_REPORT"event type.(NOTE 3)NOTE 3: When a subscription for "PRESENCE_IN_AOI_REPORT" event targets any UE but no UE is "IN" the AOI when the AMF generates the first notification (e.g. for one-time reporting or for the first notification for continuously reporting), the anyUe IE shall be present with the value true and lEs indicating UE IDs (Supi, Gpsi, Pei and ueldExtList) shall not be present; the areaList IE shall be present including the subscribed AOI with the Presence Status set to "IN", i.e. no UE is "IN" theAOI.
[0038] A new event filter is proposed to the "UE moving in or out Area of Interest” as shown below in a modified version of Table 5.2.2.3.1-1 from clause 5.2.2.3.1 of 3GPP TS 23.502 where additions are shown by bold, underlined text:Table 5.2.2.3.1 -1 : Example of Event Filters for AMF exposure eventsEvent ID Event Filter (List of Parameter Values to Match) Location Report <Parameter Type = LocationFilter, Value = TA1> UE moving in or out of Area of Interest <Parameter Type = TAI, Value = TA1><Parameter Type = S-NSSAI, Value = S-NSSAI1> <Parameter Type = NSI ID, Value = NSI ID1 > <Parameter Type = PRA ID, Value = PRA ID value> <Parameter Type = RAN Node ID, Value = RAN Node ID value><Parameter Type = Cell ID, Value = Cell ID value> <Parameter Type = RAN timing synchronization status change event >(NOTE 1) (NOTE 2)<Parameter Type = Adjust Aol based on RA, Value = Yes or No> to indicate that AMF may adjust the received Aol depending on UE's current Registration Area. Absence of this parameter in the request is interpreted as "Aol remains unchanged".<Parameter Type = Notify the consumer considering UE identity, Value = List of SUPIs or Internal Group ID > The parameter may be included when the request is targeted to Any UE. Absence of this parameter in the request is interpreted as "AMF reports an event regardless to UE's identity triggering the event".(NOTE 2)<Parameter Type = Notify the consumer considering DNN / S-NSSAI, Value = DNN and / or S-NSSAI> Absence of this parameter in the request is interpreted as "AMF reports the event without checking to which DNN / S-NSSAI the UE has PDU sessions established".(NOTE 2)Applicant's Ref.: P113729WO01 12<Parameter Type = Notify the consumer if an event is triggered by a UE having a subscription with capabilities for sensing services. Value = Yes or No> Absence of this parameter in the reguest is interpreted as "AMF reports an event without checking the subscription information of the UE triggering the event."Access Type <Parameter Type=AN Type, Value=3GPP Access"> Location <Parameter Type=TAI, Value=wildcard> (to report any TAI change)Location <Parameter Type=TAI Value=abnormal> (to report only when the TAI deviates from expected values based on Expected UE Moving Trajectory).Assigned Trajectory <Parameter Type = Notify when the UE deviates from the assigned trajectory, Value=TAI, Scheduled Time in a particular TA and / or Height> (to report only when the UE deviates from the assigned values of TAI, Scheduled Time in a particular TA and / or moves outside the altitude range based on the assigned flight plan).The assigned trajectory may consist of multiple segments identified by geographical areas that, for instance, are served by different UAV Service Suppliers. In this case, the information of each segment shall be provided.<Parameter Type = Notify when the altitude reporting conditions are met, Value=altitude thresholds, reporting periodicity>(NOTE 4)Reachability Filter Applicable to the event UE reachability. Value = UE reachability status change or UE reachable for DL traffic. Absence of this parameter in UE reachability event request is interpreted as "UE reachability status change".Total number of Transactions <Parameter Type = TAI, Value = TA1><Parameter Type = S-NSSAI, Value = S-NSSAI1> Number of UEs present in a geographical area <Parameter Type = UE Type, Value = Aerial UE> <Parameter Type = PDU session status, Value = PDU session established for DNN subject to aerial services> <Parameter Type = LCS broadcasting assistance data type, Value = A bitmap indicates broadcast location assistance data types for which the UE is subscribed to receive ciphering keys to decipher broadcast assistance data (see Table 7.1-3 in clause 7.1 of TS 23.273
[0051] and clause 6.1.6.2.72 of TS 29.503
[0052] )>(NOTE 3)NOTE 1 : The Parameter Type = RAN timing synchronization status change event can be present with Parameter Type defining a RAN Node ID.NOTE 2: The use of event filter parameters is described in clause 5.3.4.4 of TS 23.501 [2],NOTE 3: The mapping relationship between the LCS broadcasting assistance data element and corresponding positioning SIB type is described in clause 7.2 of TS 37.355
[0056] ,NOTE 4: Filter information for the events is provided as a set of TAI, Scheduled Time and / or Height values for each of the trajectory segments assigned to the UE / UAV, see clause 5.13 of TS 23.256
[0080] , NOTE 5: Procedures related to reporting altitude information of aerial UEs are specified in clause 5.16 of TS 23.256
[0080] ,
[0039] The following service operations are defined for the Namf_EventExposure service:Namf_EventExposure_Subscribe.Namf_EventExposure_UnSubscribe.- Namf_EventExposure_Notify.Applicant's Ref.: P113729WO01 133 Filtering of UE(s) with Sensing Capabilities based on UDM Data
[0040] SCF can retrieve UE registration information from the UDM using the Nudm_UECM service and specifying the type of requested information as Amf3GppAccessRegistration, as described in the excepts from 3GPP TS 29.503 below. In one embodiment, an attribute is added to the Amf3GppAccessRegistration: “sensingindication”, similar to existing indications for other services (e.g., ueSrvccCapability) specified in 3GPP TS 29.503 V19.2.0, Table 6.2.6.2.2. - 1. The new attribute “sensingindication” received as part of the response enables the SCF to select UEs with sensing capabilities.# - excerpt from TS 29.503, Clause 5.3.2.5.2 - # The NF service consumer (e.g. NEF) sends a request to the UDM to retrieve the UE’s Amf3GppAccessRegistration Information. The request contains the UE’s identity ( / {ueld}) which shall be a GPSI or SUPI, the type of the requested information ( / registrations / amf-3gpp-access) and query parameters (supported-features).Figure 4[REPRODUCED HEREIN AS FIGURE 4]Figure 5.3.2.5.2-1 : Requesting a UE’s AMF Registration Information for 3GPP Access 1. The NF service consumer (e.g. NEF) sends a GET request to the resource representing the UE’s AMF registration information for 3 GPP access, with query parameters indicating the supported-features.2. The UDM responds with "200 OK" with the message body containing the UE’sAmf3 GppAccessRegistration.# - #
[0041] Another option is the AMF performs the filtering, based on the AMF event subscription from the SCF for "UE moving in and out of Area Interest” considering the newly introduced event filter (<Parameter Type = Notify the consumer if an event is triggered by a UE having a subscription with capabilities for sensing services, Value = Yes or No>).
[0042] One more option would be the NG-RAN selecting the assisting UEs for sensing, once the NG-RAN receives the sensing service request from the SCF. The NG-RAN, in this case as well, uses the UE capability indication from the received Registration Request message the UE includes in Step 1 of the registration procedure as explained earlier. Figure 7
[0043] Figure 7 is a schematic block diagram of a network node 700 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The network node 700 may be, for example, a RAN node (e.g., the RAN node 102) or a network node that implements all or part of the functionality of RAN node described herein, or the network node 700 may be a core network node that implements all or part of the functionality of the AMF, SCF, or UDM described herein. As illustrated, the network node 700 includes a control system 702 that includes one or more processors 704 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and / or the like), memory 706, and a network interface 708. The one or moreApplicant's Ref.: P113729WO01 14processors 704 are also referred to herein as processing circuitry. In addition, if the network node 700 is a RAN node, the network node 700 may include one or more radio units 710 that each includes one or more transmitters 712 and one or more receivers 714 coupled to one or more antennas 716. The radio units 710 may be referred to or be part of radio interface circuitry. In some embodiments, the radio unit(s) 710 is external to the control system 702 and connected to the control system 702 via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) 710 and potentially the antenna(s) 716 are integrated together with the control system 702. The one or more processors 704 operate to provide one or more functions of the network node 700 as described herein (e.g., one or more functions of the RAN node, one or more functions of the AMF, one or more functions of the SCF, or one or more functions of the UDM, as described herein). In some embodiments, the function(s) are implemented in software that is stored, e.g., in memory 706 and executed by the one or more processors 704.Figure 8
[0044] Figure 8 is a schematic block diagram that illustrates a virtualized embodiment of the network node 700 according to some embodiments of the present disclosure. Again, optional features are represented by dashed boxes. As used herein, a "virtualized” network node is an implementation of the network node 700 in which at least a portion of the functionality of the network node 700 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, if the network node 700 is a RAN node, the network node 700 may include the control system 702 and / or the one or more radio units 710, as described above. The control system 702 may be connected to the radio unit(s) 710 via, for example, an optical cable or the like. The network node 700 includes one or more processing nodes 800 coupled to or included as part of a network(s) 802. If present, the control system 702 or the radio unit(s) are connected to the processing node(s) 800 via the network 802. Each processing node 800 includes one or more processors 804 (e.g., CPUs, ASICs, FPGAs, and / or the like), memory 806, and a network interface 808.
[0045] In this example, functions 810 of the network node 700 described herein (e.g., one or more functions of the RAN node, one or more functions of the AMF, one or more functions of the SCF, or one or more functions of the UDM, as described herein) are implemented at the one or more processing nodes 800 or distributed across the one or more processing nodes 800 and the control system 702 and / or the radio unit(s) 710 in any desired manner. In some particular embodiments, some or all of the functions 810 of the network node 700 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 800. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 800 and the control system 702 is used in order to carry out at least some of the desired functions 810. Notably, in some embodiments, the control system 702 may not be included, in which case the radio unit(s) 710 communicate directly with the processing node(s) 800 via an appropriate network interface(s).
[0046] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the network node 700 or a node (e.g., a processing node 800) implementing one or more of the functions 810 of the network node 700 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising theApplicant's Ref.: P113729WO01 15aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).Figure 9
[0047] Figure 9 is a schematic block diagram of a UE 112 according to some embodiments of the present disclosure. As illustrated, the UE 112 includes one or more processors 902 (e.g., CPUs, ASICs, FPGAs, and / or the like), memory 904, and one or more transceivers 906 each including one or more transmitters 908 and one or more receivers 910 coupled to one or more antennas 912. The transceiver(s) 906 includes radio-front end circuitry connected to the antenna(s) 912 that is configured to condition signals communicated between the antenna(s) 912 and the processor(s) 902, as will be appreciated by one of ordinary skill in the art. The processors 902 are also referred to herein as processing circuitry. The transceivers 906 are also referred to herein as radio circuitry. In some embodiments, the functionality of the UE 112 (or UE) described above may be fully or partially implemented in software that is, e.g., stored in the memory 904 and executed by the processor(s) 902. Note that the UE 112 may include additional components not illustrated in Figure 9 such as, e.g., one or more user interface components (e.g., an input / output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and / or the like and / or any other components for allowing input of information into the UE 112 and / or allowing output of information from the UE 112), a power supply (e.g., a battery and associated power circuitry), etc.
[0048] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the UE 112 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
[0049] Although the computing devices described herein (e.g., UEs, network nodes, etc.) 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.Applicant's Ref.: P113729WO01 16
[0050] 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.
[0051] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.EMBODIMENTSSome of the embodiments that have been described above can be summarized in the following manner:1. A method performed by a User Equipment, UE, for registration with a cellular communications system, the method comprising:transmitting (Fig. 2, step 1; Fig. 3, step 1) a registration request message to a Radio Access Network, RAN, node in a RAN of a cellular communications system, the registration request comprising an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).2. The method of embodiment 1, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.3. A User Equipment, UE, adapted to:transmit (Fig. 2, step 1; Fig. 3, step 1) a registration request message to a Radio Access Network, RAN, node in a RAN of a cellular communications system, the registration request comprising an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).4. The UE of embodiment 3, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.5. A User Equipment, UE, comprising:a transmitter; andprocessing circuitry associated with the transmitter, the processing circuitry configured to cause the UE to transmit (Fig. 2, step 1; Fig. 3, step 1) a registration request message to a Radio Access Network, RAN, node in a RANApplicant's Ref.: P113729WO01 17of a cellular communications system, the registration request comprising an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).6. The UE of embodiment 5, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.7. A method performed by a Radio Access Network, RAN, node, the method comprising:receiving (Fig. 2, step 1; Fig. 3, step 1) a registration request message from a User Equipment, UE, wherein the registration request comprises an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).8. The method of embodiment 7, further comprising sending (Fig. 3, step 3) the registration request to an Access and Mobility Management Function, AMF, wherein the registration request comprises the indication that the UE has sensing capabilities.9. The method of embodiment 7 or 8, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.10. A Radio Access Network, RAN, node adapted to:receive (Fig. 2, step 1; Fig. 3, step 1) a registration request message from a User Equipment, UE, wherein the registration request comprises an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).11. The RAN node of embodiment 10, wherein the RAN node is further adapted to send (Fig. 3, step 3) the registration request to an Access and Mobility Management Function, AMF, wherein the registration request comprises the indication that the UE has sensing capabilities.12. The RAN node of embodiment 10 or 11, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.13. A Radio Access Network, RAN, node comprising processing circuitry configured to cause the RAN node to:receive (Fig. 2, step 1; Fig. 3, step 1) a registration request message from a User Equipment, UE, wherein the registration request comprises an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).14. The RAN node of embodiment 13, wherein the processing circuitry is further configured to cause the RAN node to send (Fig. 3, step 3) the registration request to an Access and Mobility Management Function, AMF, whereinApplicant's Ref.: P113729WO01 18the registration request comprises the indication that the UE has sensing capabilities.15. The RAN node of embodiment 13 or 14, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.16. A method performed by an Access and Mobility Management Function, AMF, the method comprising: receiving (Fig. 3, step 3) a registration request message for a User Equipment, UE, from a Radio Access Network, RAN, node, wherein the registration request comprises an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).17. The method of embodiment 16, further comprising sending (Fig. 3, step 14a) (e.g., as part of the UE registration procedure) a UE context of the UE to a Unified Data Management, UDM, wherein the UE context comprises an indication that the UE has sensing capabilities.18. The RAN node of embodiment 16 or 17, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.19. An Access and Mobility Management Function, AMF, adapted to:receive (Fig. 3, step 3) a registration request message for a User Equipment, UE, from a Radio Access Network, RAN, node, wherein the registration request comprises an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).20. The AMF of embodiment 19, further adapted to send (Fig. 3, step 14a) (e.g., as part of the UE registration procedure) a UE context of the UE to a Unified Data Management, UDM, wherein the UE context comprises an indication that the UE has sensing capabilities.21. The AMF node of embodiment 19 or 20, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.22. A network node for implementing an Access and Mobility Management Function, AMF, the network node comprising processing circuitry configured to cause the network node to:receive (Fig. 3, step 3) a registration request message for a User Equipment, UE, from a Radio Access Network, RAN, node, wherein the registration request comprises an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).23. The network node of embodiment 22, wherein the processing circuitry is further configured to cause the network node to send (Fig. 3, step 14a) (e.g., as part of the UE registration procedure) a UE context of the UE to aApplicant's Ref.: P113729WO01 19Unified Data Management, UDM, wherein the UE context comprises an indication that the UE has sensing capabilities.24. The network node of embodiment 22 or 23, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.25. A method performed by a Sensing Control Function, SCF, in a cellular communications system having Integrated Sensing and Communication, ISAC, functionality, the method comprising:sending (Fig. 2, step 2) a request to an Access and Mobility Management Function, AMF, for a list of User Equipments, UEs, in an area of interest, the request comprising an explicit or implicit indication that the list of UEs is to include only UEs that have sensing capabilities; andreceiving (Fig. 2, step 4), from the AMF, a list of UEs that consists of UEs that both are in the area of interest and have sensing capabilities.26. The method of embodiment 25, further comprising performing one or more sensing related actions based on the list of UEs.27. The method of embodiment 25 or 26, wherein the request is a subscription request for event notifications for the area of interest, and the indication that the list of UEs is to include only UEs that have sensing capabilities comprise an indication of an event filter that indicates that the subscription request is for UEs in the area of interest having sensing capabilities.28. A method performed by a Sensing Control Function, SCF, in a cellular communications system having Integrated Sensing and Communication, ISAC, functionality, the method comprising:sending (Fig. 2, step 2) a request to an Access and Mobility Management Function, AMF, for a list of User Equipments, UEs, in an area of interest;receiving (Fig. 2, step 4), from the AMF, a list of UEs that consists of UEs that are in the area of interest; and filtering (Fig. 2, step 7) the list of UEs based on sensing capabilities to provide a filtered list of UEs consisting of UEs that both are in the area of interest and have sensing capabilities.29. The method of embodiment 28, further comprising performing one or more sensing related actions based on the list of UEs.30. The method of embodiment 28 or 29, further comprising:for each UE contained in the list of UEs, obtaining (Fig. 2, steps 5 and 6) information that indicates whether the UE has sensing capabilities;wherein filtering (Fig. 2, step 7) the list of UEs comprises filtering (Fig. 2, step 7) the list of UEs based on the obtained information that indicates whether the UEs have sensing capabilities.Applicant's Ref.: P113729WO01 2031. The method of embodiment 30, wherein obtaining (Fig. 2, steps 5 and 6) the information that indicates whether the UE has sensing capabilities comprises:sending (Fig. 2, step 5) a request to a Unified Data Management, UDM, wherein the request comprises an indication that the request is for information that indicates whether the UE has sensing capabilities; and receiving (Fig. 2, step 6) a response from the UDM, wherein the response comprises the information that indicates whether the UE has sensing capabilities.32. A Sensing Control Function, SCF, adapted to perform the method of any of embodiments 25 to 31.33. A network node for implementing a Sensing Control Function, SCF, the network node comprising processing circuitry configured to cause the network node to perform the method of any of embodiments 25 to 31.34. A method performed by an Access and Mobility Management Function, AMF, in a cellular communications system having Integrated Sensing and Communication, ISAC, functionality, the method comprising:receiving (Fig. 2, step 2) a request from a Sensing Control Function, SCF, for a list of User Equipments, UEs, in an area of interest, the request comprising an explicit or implicit indication that the list of UEs is to include only UEs that have sensing capabilities; andsending (Fig. 2, step 4), to the SCF, a list of UEs that consists of UEs that both are in the area of interest and have sensing capabilities.35. The method of embodiment 34, wherein the request is a subscription request for event notifications for the area of interest, and the indication that the list of UEs is to include only UEs that have sensing capabilities comprise an indication of an event filter that indicates that the subscription request is for UEs in the area of interest having sensing capabilities.36. An Access and Mobility Management Function, AMF, adapted to perform the method of any of embodiments 34 to 35.37. A network node for implementing an Access and Mobility Management Function, AMF, the network node comprising processing circuitry configured to cause the network node to perform the method of any of embodiments 34 to 35.
Claims
Applicant's Ref.: P113729WO01 21CLAIMSWhat is claimed is:
1. A method performed by a User Equipment, UE, for registration with a cellular communications system, the method comprising:transmitting (Fig. 2, step 1; Fig. 3, step 1) a registration request message to a Radio Access Network, RAN, node in a RAN of a cellular communications system, the registration request comprising an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).
2. The method of claim 1, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.
3. A User Equipment, UE, adapted to:transmit (Fig. 2, step 1; Fig. 3, step 1) a registration request message to a Radio Access Network, RAN, node in a RAN of a cellular communications system, the registration request comprising an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).
4. The UE of claim 3, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.
5. A User Equipment, UE, comprising:a transmitter; andprocessing circuitry associated with the transmitter, the processing circuitry configured to cause the UE to transmit (Fig. 2, step 1; Fig. 3, step 1) a registration request message to a Radio Access Network, RAN, node in a RAN of a cellular communications system, the registration request comprising an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).
6. The UE of claim 5, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.
7. A method performed by a Radio Access Network, RAN, node, the method comprising:receiving (Fig. 2, step 1; Fig. 3, step 1) a registration request message from a User Equipment, UE, wherein the registration request comprises an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).
8. The method of claim 7, further comprising sending (Fig. 3, step 3) the registration request to an Access and Mobility Management Function, AMF, wherein the registration request comprises the indication that the UE has sensingApplicant's Ref.: P113729WO01 22capabilities.
9. The method of claim 7 or 8, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.
10. A Radio Access Network, RAN, node adapted to:receive (Fig. 2, step 1; Fig. 3, step 1) a registration request message from a User Equipment, UE, wherein the registration request comprises an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).
11. The RAN node of claim 10, wherein the RAN node is further adapted to send (Fig. 3, step 3) the registration request to an Access and Mobility Management Function, AMF, wherein the registration request comprises the indication that the UE has sensing capabilities.
12. The RAN node of claim 10 or 11, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.
13. A Radio Access Network, RAN, node comprising processing circuitry configured to cause the RAN node to:receive (Fig. 2, step 1; Fig. 3, step 1) a registration request message from a User Equipment, UE, wherein the registration request comprises an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).
14. The RAN node of claim 13, wherein the processing circuitry is further configured to cause the RAN node to send (Fig. 3, step 3) the registration request to an Access and Mobility Management Function, AMF, wherein the registration request comprises the indication that the UE has sensing capabilities.
15. The RAN node of claim 13 or 14, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.
16. A method performed by an Access and Mobility Management Function, AMF, the method comprising: receiving (Fig. 3, step 3) a registration request message for a User Equipment, UE, from a Radio Access Network, RAN, node, wherein the registration request comprises an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).
17. The method of claim 16, further comprising sending (Fig. 3, step 14a) (e.g., as part of the UE registration procedure) a UE context of the UE to a Unified Data Management, UDM, wherein the UE context comprises an indication that the UE has sensing capabilities.Applicant's Ref.: P113729WO01 2318. The RAN node of claim 16 or 17, wherein the cellular communications system is a5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.
19. An Access and Mobility Management Function, AMF, adapted to:receive (Fig. 3, step 3) a registration request message for a User Equipment, UE, from a Radio Access Network, RAN, node, wherein the registration request comprises an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).
20. The AMF of claim 19, further adapted to send (Fig. 3, step 14a) (e.g., as part of the UE registration procedure) a UE context of the UE to a Unified Data Management, UDM, wherein the UE context comprises an indication that the UE has sensing capabilities.
21. The AMF node of claim 19 or 20, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.
22. A network node for implementing an Access and Mobility Management Function, AMF, the network node comprising processing circuitry configured to cause the network node to:receive (Fig. 3, step 3) a registration request message for a User Equipment, UE, from a Radio Access Network, RAN, node, wherein the registration request comprises an indication that the UE has sensing capabilities (e.g., the capability to act as a sensing entity for Integrated Sensing and Communication, ISAC).
23. The network node of claim 22, wherein the processing circuitry is further configured to cause the network node to send (Fig. 3, step 14a) (e.g., as part of the UE registration procedure) a UE context of the UE to a Unified Data Management, UDM, wherein the UE context comprises an indication that the UE has sensing capabilities.
24. The network node of claim 22 or 23, wherein the cellular communications system is a 5thGeneration, 5G, system, and the RAN node is a Next Generation RAN, NG-RAN, node or gNodeB, gNB.
25. A method performed by a Sensing Control Function, SCF, in a cellular communications system having Integrated Sensing and Communication, ISAC, functionality, the method comprising:sending (Fig. 2, step 2) a request to an Access and Mobility Management Function, AMF, for a list of User Equipments, UEs, in an area of interest, the request comprising an explicit or implicit indication that the list of UEs is to include only UEs that have sensing capabilities; andreceiving (Fig. 2, step 4), from the AMF, a list of UEs that consists of UEs that both are in the area of interest and have sensing capabilities.Applicant's Ref.: P113729WO01 2426. The method of claim 25, further comprising performing one or more sensing related actions based on the list of UEs.
27. The method of claim 25 or 26, wherein the request is a subscription request for event notifications for the area of interest, and the indication that the list of UEs is to include only UEs that have sensing capabilities comprise an indication of an event filter that indicates that the subscription request is for UEs in the area of interest having sensing capabilities.
28. A method performed by a Sensing Control Function, SCF, in a cellular communications system having Integrated Sensing and Communication, ISAC, functionality, the method comprising:sending (Fig. 2, step 2) a request to an Access and Mobility Management Function, AMF, for a list of User Equipments, UEs, in an area of interest;receiving (Fig. 2, step 4), from the AMF, a list of UEs that consists of UEs that are in the area of interest; and filtering (Fig. 2, step 7) the list of UEs based on sensing capabilities to provide a filtered list of UEs consisting of UEs that both are in the area of interest and have sensing capabilities.
29. The method of claim 28, further comprising performing one or more sensing related actions based on the list of UEs.
30. The method of claim 28 or 29, further comprising:for each UE contained in the list of UEs, obtaining (Fig. 2, steps 5 and 6) information that indicates whether the UE has sensing capabilities;wherein filtering (Fig. 2, step 7) the list of UEs comprises filtering (Fig. 2, step 7) the list of UEs based on the obtained information that indicates whether the UEs have sensing capabilities.
31. The method of claim 30, wherein obtaining (Fig. 2, steps 5 and 6) the information that indicates whether the UE has sensing capabilities comprises:sending (Fig. 2, step 5) a request to a Unified Data Management, UDM, wherein the request comprises an indication that the request is for information that indicates whether the UE has sensing capabilities; and receiving (Fig. 2, step 6) a response from the UDM, wherein the response comprises the information that indicates whether the UE has sensing capabilities.
32. A Sensing Control Function, SCF, adapted to perform the method of any one of claim 25 to 31.
33. A network node for implementing a Sensing Control Function, SCF, the network node comprising processing circuitry configured to cause the network node to perform the method of any one of claim 25 to 31.Applicant's Ref.: P113729WO01 2534. A method performed by an Access and Mobility Management Function, AMF, in a cellular communications system having Integrated Sensing and Communication, ISAC, functionality, the method comprising:receiving (Fig. 2, step 2) a request from a Sensing Control Function, SCF, for a list of User Equipments, UEs, in an area of interest, the request comprising an explicit or implicit indication that the list of UEs is to include only UEs that have sensing capabilities; andsending (Fig. 2, step 4), to the SCF, a list of UEs that consists of UEs that both are in the area of interest and have sensing capabilities.
35. The method of claim 34, wherein the request is a subscription request for event notifications for the area of interest, and the indication that the list of UEs is to include only UEs that have sensing capabilities comprise an indication of an event filter that indicates that the subscription request is for UEs in the area of interest having sensing capabilities.
36. An Access and Mobility Management Function, AMF, adapted to perform the method of any one of claim 34 to 35.
37. A network node for implementing an Access and Mobility Management Function, AMF, the network node comprising processing circuitry configured to cause the network node to perform the method of any one of claim 34 to
