Sensing entity selection methods, sensing devices and sensing system

Abstract

The embodiments of the present disclosure relate to sensing entity selection methods, sensing devices, a sensing system, a storage medium, and a program product. A sensing entity selection method comprises: a Non-3GPP device sending a sensing capability and / or sensing information of the Non-3GPP device; and receiving a sensing task request, wherein the sensing task request is used for requesting the Non-3GPP device to execute a sensing task. In this way, a mechanism for performing a sensing service by means of a Non-3GPP device can be provided.

Description

Entity selection method, sensing device and sensing system Technical Field

[0001] This disclosure relates to the field of sensing technology, and in particular to a method for selecting sensing entities, a sensing device, a sensing system, a storage medium, and a program product. Background Technology

[0002] In current 5G research, Non-3GPP devices can obtain services and exchange traffic with network equipment by connecting to a UE or 5G-RG. The UE or 5G-RG matches with the Non-3GPP device through existing PDU sessions or by establishing new PDU sessions to meet the QoS (Quality of Service) requirements of the Non-3GPP device. However, whether Non-3GPP devices can provide service awareness remains to be studied. Summary of the Invention

[0003] This disclosure provides a method for selecting sensing entities, a sensing device, a sensing system, a storage medium, and a program product to provide a mechanism for providing sensing services through Non-3GPP devices.

[0004] In a first aspect, embodiments of this disclosure provide a method for selecting perceived entities, applied to Non-3GPP equipment, the method comprising:

[0005] Send the sensing capabilities and / or sensing information of the Non-3GPP device;

[0006] Receive a sensing task request; wherein the sensing task request is used to request the Non-3GPP device to perform a sensing task.

[0007] Secondly, this disclosure also provides a method for selecting a sensing entity, applied to a first device, the first device including a UE or a gateway; the method includes:

[0008] Receive the sensing capabilities and / or sensing information of the Non-3GPP device sent by the Non-3GPP device;

[0009] Send a sensing task request to the Non-3GPP device; wherein the sensing task request is used to request the Non-3GPP device to perform a sensing task.

[0010] Thirdly, this disclosure also provides a method for selecting a sensing entity, applied to a third network element, the method comprising:

[0011] Receive sensing capabilities and / or sensing information of a Non-3GPP device sent by a first device; the first device includes a UE or a gateway.

[0012] Fourthly, this disclosure also provides a method for selecting a sensing entity, applied to a first network element, the method comprising:

[0013] Receive the sensing capabilities and / or sensing information of the Non-3GPP device sent by the Non-3GPP device.

[0014] Fifthly, this disclosure also provides a method for selecting a sensing entity, applied to a fourth network element, the method comprising:

[0015] Receive a sensing service request; wherein the sensing service request is used to request the execution of a sensing task;

[0016] Based on the sensing capabilities and / or sensing information of at least one sensing entity stored in the second network element, a Non-3GPP device is identified from the at least one sensing entity as the sensing entity performing the sensing task.

[0017] A sensing task request is sent to a first device; wherein the sensing task request is used to request the Non-3GPP device to perform a sensing task; the first device includes a UE or a gateway.

[0018] Sixthly, embodiments of this disclosure also provide a method for selecting a sensing entity, applied to a second network element, the method comprising:

[0019] Receive sensing capabilities and / or sensing information from Non-3GPP devices;

[0020] Store the sensing capabilities and / or sensing information of the Non-3GPP device.

[0021] In a seventh aspect, embodiments of this disclosure also provide a sensing device for performing the sensing entity selection method described in the first, second, third, fourth, fifth, or sixth aspects.

[0022] Eighthly, embodiments of this disclosure also provide a sensing device, including:

[0023] One or more processors;

[0024] The sensing device is used to implement the sensing entity selection method described in the first, second, third, fourth, fifth, or sixth aspects of the embodiments of this disclosure.

[0025] Ninthly, embodiments of this disclosure also provide a storage medium storing instructions that, when executed on a sensing device, cause the sensing device to perform the sensing entity selection method as described in the first, second, third, fourth, fifth, or sixth aspects of embodiments of this disclosure.

[0026] In a tenth aspect, embodiments of this disclosure also provide a program product, including at least one of a program and instructions, wherein the at least one of the program and instructions, when executed by a sensing device, implements the sensing entity selection method described in the first aspect, second aspect, third aspect, fourth aspect, fifth aspect, or sixth aspect.

[0027] In this embodiment of the disclosure, the Non-3GPP device can report its sensing capabilities and / or sensing information; thus, the upstream device of the Non-3GPP device can determine whether to designate the Non-3GPP device as a sensing entity to sense the sensing object based on the sensing capabilities and / or sensing information reported by the Non-3GPP device. Furthermore, the Non-3GPP device can execute the sensing task indicated by the received sensing task request.

[0028] Additional aspects and advantages of embodiments of this disclosure will be set forth in part in the description which follows, and will become apparent from the description or may be learned by practice of this disclosure. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0030] Figure 1 is a schematic diagram of the architecture of the perception system provided in an embodiment of this disclosure;

[0031] Figure 2 is one of the interactive schematic diagrams of the entity selection method provided in the embodiments of this disclosure;

[0032] Figure 3 is one of the scenario diagrams of the entity selection method provided in the embodiments of this disclosure;

[0033] Figure 4 is a second scenario illustration of the perceptual entity selection method provided in the embodiments of this disclosure;

[0034] Figure 5 is a third scenario diagram of the perceptual entity selection method provided in the embodiments of this disclosure;

[0035] Figure 6 is a second interactive schematic diagram of the entity selection method provided in the embodiments of this disclosure;

[0036] Figure 7 is the third interactive schematic diagram of the entity selection method provided in the embodiments of this disclosure;

[0037] Figure 8 is a fourth interactive schematic diagram of the entity selection method provided in the embodiments of this disclosure;

[0038] Figure 9 is one of the flowcharts of the entity selection method provided in this embodiment of the present disclosure;

[0039] Figure 10 is a second schematic flowchart of the entity selection method provided in the embodiments of this disclosure;

[0040] Figure 11 is a third flowchart illustrating the entity selection method provided in this embodiment of the present disclosure;

[0041] Figure 12 is a fourth flowchart illustrating the entity selection method provided in this embodiment of the present disclosure;

[0042] Figure 13 is a fifth flowchart illustrating the entity selection method provided in this embodiment of the present disclosure;

[0043] Figure 14 is a sixth flowchart illustrating the entity selection method provided in this embodiment of the present disclosure;

[0044] Figure 15 is a schematic diagram of the structure of the Non-3GPP equipment proposed in the embodiments of this disclosure;

[0045] Figure 16 is a schematic diagram of the structure of the first device proposed in an embodiment of this disclosure;

[0046] Figure 17 is a schematic diagram of the structure of the third network element proposed in an embodiment of this disclosure;

[0047] Figure 18 is a schematic diagram of the structure of the first network element proposed in an embodiment of this disclosure;

[0048] Figure 19 is a schematic diagram of the structure of the fourth network element proposed in an embodiment of this disclosure;

[0049] Figure 20 is a schematic diagram of the structure of the first device proposed in an embodiment of this disclosure;

[0050] Figure 21 is a schematic diagram of the structure of the terminal proposed in an embodiment of this disclosure;

[0051] Figure 22 is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0052] This disclosure provides a method for selecting sensing entities, a sensing device, a sensing system, a storage medium, and a program product.

[0053] In a first aspect, embodiments of this disclosure provide a method for selecting perceived entities, applied to Non-3GPP equipment, the method comprising:

[0054] Send the sensing capabilities and / or sensing information of the Non-3GPP device;

[0055] Receive a sensing task request; wherein the sensing task request is used to request the Non-3GPP device to perform a sensing task.

[0056] Secondly, this disclosure also provides a method for selecting a sensing entity, applied to a first device, the first device including a UE or a gateway; the method includes:

[0057] Receive the sensing capabilities and / or sensing information of the Non-3GPP device sent by the Non-3GPP device;

[0058] Send a sensing task request to the Non-3GPP device; wherein the sensing task request is used to request the Non-3GPP device to perform a sensing task.

[0059] Thirdly, this disclosure also provides a method for selecting a sensing entity, applied to a third network element, the method comprising:

[0060] Receive sensing capabilities and / or sensing information of a Non-3GPP device sent by a first device; the first device includes a UE or a gateway.

[0061] Fourthly, this disclosure also provides a method for selecting a sensing entity, applied to a first network element, the method comprising:

[0062] Receive the sensing capabilities and / or sensing information of the Non-3GPP device sent by the Non-3GPP device.

[0063] Fifthly, this disclosure also provides a method for selecting a sensing entity, applied to a fourth network element, the method comprising:

[0064] Receive a sensing service request; wherein the sensing service request is used to request the execution of a sensing task;

[0065] Based on the sensing capabilities and / or sensing information of at least one sensing entity stored in the second network element, a Non-3GPP device is identified from the at least one sensing entity as the sensing entity performing the sensing task.

[0066] A sensing task request is sent to a first device; wherein the sensing task request is used to request the Non-3GPP device to perform a sensing task; the first device includes a UE or a gateway.

[0067] Sixthly, embodiments of this disclosure also provide a method for selecting a sensing entity, applied to a second network element, the method comprising:

[0068] Receive sensing capabilities and / or sensing information from Non-3GPP devices;

[0069] Store the sensing capabilities and / or sensing information of the Non-3GPP device.

[0070] In a seventh aspect, embodiments of this disclosure also provide a sensing device for performing the sensing entity selection method described in the first, second, third, fourth, fifth, or sixth aspects.

[0071] Eighthly, embodiments of this disclosure also provide a sensing device, including:

[0072] One or more processors;

[0073] The sensing device is used to implement the sensing entity selection method described in the first, second, third, fourth, fifth, or sixth aspects of the embodiments of this disclosure.

[0074] In a ninth aspect, embodiments of this disclosure also provide a storage medium storing instructions that, when executed on a sensing device, cause the sensing device to perform the sensing entity selection method as described in the first, second, third, fourth, fifth, or sixth aspects of embodiments of this disclosure.

[0075] In a tenth aspect, embodiments of this disclosure also provide a program product, including at least one of a program and instructions, wherein the at least one of the program and instructions, when executed by a sensing device, implements the sensing entity selection method described in the first aspect, second aspect, third aspect, fourth aspect, fifth aspect, or sixth aspect.

[0076] In the eleventh aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in optional implementations of the first, second, third, fourth, fifth, or sixth aspects.

[0077] In a twelfth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to optional implementations of the first, second, third, fourth, fifth, or sixth aspects above.

[0078] It is understood that the aforementioned sensing devices, sensing systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0079] This disclosure presents a method for selecting sensing entities, a sensing device, and a sensing system.

[0080] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0081] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0082] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0083] In the embodiments disclosed herein, "multiple" refers to two or more.

[0084] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0085] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (performing A regardless of whether there is a branch B); in some embodiments, B (performing B regardless of whether there is a branch A); in some embodiments, performing a selection from A and B (A and B are selectively performed); in some embodiments, A and B (both A and B are performed). The same applies when there are more branches such as A, B, C, etc.

[0086] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (performing A regardless of whether a branch B exists); in some embodiments, B (performing B regardless of whether a branch A exists); in some embodiments, a selection is made between A and B (A and B are selectively performed). The same applies when there are more branches such as A, B, and C.

[0087] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0088] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0089] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0090] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0091] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0092] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0093] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0094] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0095] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0096] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0097] Figure 1 is a schematic diagram of the architecture of a sensing system according to an embodiment of the present disclosure.

[0098] As shown in Figure 1, the sensing system 100 includes a Non-3GPP device, a first device, a first network element, a second network element, a third network element, a fourth network element, and a fifth network element.

[0099] Optionally, the first device may include a UE (User Equipment) or a gateway.

[0100] In some embodiments, the UE includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0101] Optionally, the first network element may include an AF (Application Function) network element. The second network element may include a data storage function network element. The third network element may include an SMF (Session Management Function) network element. The fourth network element may include an SF (Service Communication Proxy) network element. The fifth network element may include a NEF (Network Exposure Function).

[0102] In some embodiments, the first network element, the second network element, the third network element, the fourth network element, and the fifth network element can be network elements in a network device (specifically, they may include core network devices).

[0103] The network device can configure the user equipment with the information required for measurement and send the configuration information to the user equipment. The user equipment can then perform corresponding measurement operations based on the configuration information sent by the network device.

[0104] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The protocol layer of the access network device can be separated through the CU-DU structure. Some protocol layer functions are centrally controlled by the CU, while the remaining part or all protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0105] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of the aforementioned one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC).

[0106] It is understood that the perception system described in the embodiments of this disclosure is for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and does not constitute a limitation on the technical solutions proposed in the embodiments of this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in the embodiments of this disclosure are also applicable to similar technical problems.

[0107] The following embodiments of this disclosure can be applied to the sensing system 100 shown in FIG1, or to some of the subjects, but are not limited thereto. The subjects shown in FIG1 are illustrative. The sensing system may include all or some of the subjects in FIG1, or may include other subjects other than those in FIG1. ​​The number and form of each subject are arbitrary. Each subject may be physical or virtual. The connection relationship between the subjects is illustrative. The subjects may not be connected or may be connected. The connection may be in any way, such as direct connection or indirect connection, wired connection or wireless connection.

[0108] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, Open Radio Access Network (O-RAN) systems, systems utilizing other resource determination methods, and next-generation systems extended from them, such as the 6th generation mobile communication system (6G). Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0109] Figure 2 is one of the interactive schematic diagrams of a perceptual entity selection method according to an embodiment of the present disclosure. Referring to Figure 2, the method includes:

[0110] Step 201: The Non-3GPP device sends its sensing capabilities and / or sensing information.

[0111] In current wireless communication systems, the rapid growth of wireless communication technology and the increasing demand for high-quality data transmission have led to the development of modern sensing systems. This includes Integrated Sensing and Communication (ISAC) technology, which integrates sensing and communication technologies. ISAC technology may impact multiple industries, including automotive, healthcare, and smart cities.

[0112] Specifically, sensing technology refers to acquiring information about the environment and / or objects in the environment through radio frequency signals, such as, but not limited to, shape, size, orientation, speed, position, distance, or relative motion between objects.

[0113] Referring to Figure 3, the ISAC (Integrated Sensing and Communication) system includes the following roles: sensing object or environment, sensing transmitter, sensing receiver, sensing processor, and sensing consumer / user:

[0114] Perceived object or environment: The target object being perceived may not fall under the scope of the 3rd Generation Partnership Project (3GPP).

[0115] Sensing transmitter: A device that transmits radio signals to a sensed object. A sensing transmitter may include a UE or a gNB (gNodeB, a type of base station).

[0116] A sensing receiver is a device that detects sensing data (i.e., information obtained by sensing the target object, also known as the sensing information of the target object) based on radio signals reflected and / or diffracted by the target object (i.e., the sensing object). A sensing receiver may include a UE or a gNB.

[0117] Perception processor: A device that collects perception data, processes the collected perception data, and generates perception results. The processor may include UE, gNB, core network entity, or application server.

[0118] Sensing consumers / users: Authorized devices that request or subscribe to sensing data and calculate outputs based on the sensing data, such as UE applications, ISAC service application servers, core network entities, or RAN nodes (RAN stands for wireless access network).

[0119] For the target object, the perception results may include shape, size, orientation, speed, position, distance between objects, or relative motion (e.g., between the target object and the sensing signal receiver). For the target environment, the perception results may include parameters describing the environment's space or state.

[0120] In current 5G research, Non-3GPP devices can obtain services by connecting to a UE or 5G-RG and interact with network devices (e.g., traffic interaction; for example, the information interaction methods that can be achieved with reference to the architecture shown in Figure 5). The UE or 5G-RG matches with the Non-3GPP device through existing PDU sessions or by establishing new PDU sessions to meet the QoS (Quality of Service) requirements of the Non-3GPP device.

[0121] However, Non-3GPP devices may also possess sensing capabilities as sensing entities, and in some cases, they are required to perform sensing tasks. However, currently there is no mechanism to enable Non-3GPP devices to provide sensing services. Therefore, how to provide a mechanism for identifying and organizing Non-3GPP devices through network devices to enable them to provide sensing services is a pressing problem in this field.

[0122] In this embodiment of the disclosure, as an example, referring to Figure 4, in the sensing system architecture based on the 5G system (5th Generation Partnership Project), the bold black line represents the "bus interface"; (R)AN (Radio Access Network) can access the UPF (User Plane Function) network element through the N3 interface; the UPF network element accesses the SF-UPF (sensing function-user plane function) network element through the NS1 interface; the NSSF (Network Slice Selection Function) network element accesses the bus interface through the Nnssf interface; the NEF (Network Exposure Function) network element accesses the bus interface through the Nnef interface; the NRF (NF Repository Function) network element accesses the bus interface through the Nnrf interface; the PCF (Policy Control Function) network element accesses the bus interface through the Npcf interface; the UDM (Unified Data Management) network element accesses the bus interface through the Nudf interface; AF (Application Function) network element accesses the bus interface through the Nudf interface; Application Function (NSF) network elements access the bus interface through the Naf interface; Service Data Management Function (SDMF) network elements access the bus interface through the Nsdmf interface; Network Slice-Specific Authentication and Authorization Function (NSSA AF) network elements access the bus interface through the Nnssaaf interface; Authentication Server Function (AUSF) network elements access the bus interface through the Nausf interface; Access and Mobility Management Function (AMF) network elements access the bus interface through the Naamf interface; Session Management Function (SMF) network elements access the bus interface through the Nsmf interface; Service Control Point (SCP) network elements directly access the bus interface.The NSACF (Network Slice Admission Control Function) network element connects to the bus interface via the Nnsacf interface; the SF-C (Sensing Function Control Plane) network element connects to the bus interface via the Nsf interface; the UE can connect to the AMF network element via the N1 interface; the (R)AN connects to the AMF network element via the N2 interface; the UPF network element connects to the SMF network element via the N4 interface; the SMF network element connects to the SF-UPF network element via the N9 interface; the SF-UPF network element connects to the SF-C network element via the NS0 interface; and the (R)AN connects to the SF-C network element via the NS2 interface.

[0123] In this embodiment of the disclosure, the user equipment and (wireless) access network entity can be a service consumer, a data processor, a sensing receiver, or a sensing transmitter, and the SF-UPF network element can implement data processing or data storage functions.

[0124] In this embodiment, the network slice selection function network element, network capability opening function network element, network function repository function network element, policy control function network element, unified data management function network element, application function network element, service data management function network element, network slice selection authentication and authorization function network element, authentication server function network element, access and mobility management function, session management function, service control point, and network slice admission control function network element can be directly connected to the bus or connected to the bus through the corresponding network interface to jointly participate in the sensing process.

[0125] In this embodiment of the disclosure, the AF network element can also participate in the sensing process as a service consumer or a data processor, and the SDMF network element can participate in the sensing process as a data storage device.

[0126] In some embodiments, based on Figure 4, Figure 5 illustrates a scenario where Non-3GPP devices (3GPP, or 3rd Generation Partnership Project) are connected after a 5G-RG (5G Residential Gateway) based on a connection group. Referring to Figure 5, different Non-3GPP devices can access the 5G-RG through the range of their respective Service Sets (SSs). After accessing the 5G-RG, different Non-3GPP devices can establish PDU sessions with Access and Mobility Management Function (UPF) network elements through the 5G-RG, and then establish network connections through the UPF network elements.

[0127] Optionally, the ACS (Access Control Server) can be used to control the Non-3GPP equipment accessing 5G-RG; the AMF (Access and Mobility Management Function) network element can be used to manage the access and mobility of the Non-3GPP equipment accessing 5G-RG; and the SMF (Session Management Function) network element can be used to manage different PDU (Protocol Data Unit) sessions.

[0128] Optionally, the sensing capability of the Non-3GPP equipment refers to whether the Non-3GPP equipment has the ability to sense the sensing object, that is, whether the Non-3GPP equipment supports sensing services.

[0129] Optionally, the sensing information of the Non-3GPP device refers to the sensing identity, sensing mode, and other information used by the Non-3GPP device when acquiring the sensing information of the sensing object during the process of the Non-3GPP device sensing the sensing object.

[0130] In some embodiments, a Non-3GPP device may send only its sensing capabilities, only its sensing information, or both its sensing capabilities and sensing information.

[0131] It is understandable that when a Non-3GPP device sends its sensing information, it can implicitly indicate that the Non-3GPP device supports sensing services and has the ability to sense objects.

[0132] In some embodiments, the Non-3GPP device may be a device that uses communication technologies and standards not defined by 3GPP. For example, it may include, but is not limited to, Wi-Fi devices (including but not limited to smartphones, tablets, laptops, smart home devices, etc.), Bluetooth devices (including but not limited to Bluetooth headsets, Bluetooth speakers, Bluetooth keyboards, Bluetooth mice, etc.), satellite communication devices (including but not limited to satellite phones, satellite data terminals, etc.), and devices that can provide high-speed Internet access services (Worldwide Interoperability for Microwave Access, WiMAX, for example, may include base stations, user terminals, etc.).

[0133] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device include at least one of the following:

[0134] A. Sensing indication information; the sensing indication information includes: whether sensing services are supported;

[0135] B. Sensing data processing capability; the sensing data processing capability includes: whether it supports processing sensing data locally;

[0136] C. Sensing role; the sensing role includes: sensing sender and / or sensing receiver;

[0137] D. Sensing RAT (RAT stands for Retrieval-Augmented Thoughts); the Sensing RAT includes: 3GPP and / or non-3GPP;

[0138] E. Sensing mode; the sensing mode includes at least one of: transmitting only (A transmits B receives), transmitting and receiving (A transmits A receives), specific times, and periodicity;

[0139] F. Sensing plane; The sensing plane includes the control plane, user plane, data plane, and sensing plane;

[0140] G. Sensing method; the sensing method includes at least one of the following: GNSS (Global Navigation Satellite System), OTDOA (Observed Time Difference of Arrival), TBS (Terrestrial Beacon System), TDOA (Time Difference of Arrival), AoD (Angle of Departure), Multi-RTT (Multi-Round Trip Time), AoA (Angle of Arrival), WLAN (Wireless Local Area Networks), Bluetooth, lidar, radar, and sonar;

[0141] H. Sensing service performance; the sensing service performance includes at least one of the following: latency, sensing measurement resolution, QoS (Quality of Service), sensing service priority, time period, sensing measurement type, start time, end time, and sensing result;

[0142] I. Sensing measurement type; the sensing measurement type includes at least one of the following: location, distance, angle, velocity, recognition, detection, reconstruction, imaging, tracking and monitoring;

[0143] G. Sensing measurement parameter; the sensing measurement parameter includes at least one of the following: position, distance, velocity, angle accuracy, sensing frequency, bandwidth, time-frequency resource blocks, antenna number, refresh rate, maximum sensing latency, missed alarm probability, false alarm probability, reconstruction precision, imaging precision, and confidence level.

[0144] Optionally, based on actual needs, the sensing capabilities and / or sensing information of Non-3GPP devices can be configured to carry specific information from A to G as described above.

[0145] Optionally, if the sensing indication information includes that the Non-3GPP device supports sensing services, the sensing capability and / or sensing information of the Non-3GPP device includes all of the above information; if the sensing indication information includes that the Non-3GPP device supports sensing services, the sensing capability and / or sensing information of the Non-3GPP device only includes the sensing indication information.

[0146] Optionally, if the Non-3GPP device supports processing sensing data locally, it may also include the computing power of the Non-3GPP device in processing sensing data. For example, the computing power of the Non-3GPP device in processing sensing data can be identified by the parameter values ​​of parameters such as Flops (floating-point operations per second) and Ops (operations per second).

[0147] Alternatively, the "sensing transmitter" can also be called the "sensing transmitter", and the "sensing receiver" can also be called the "sensing receiver".

[0148] The sensing identity of a Non-3GPP device refers to whether, during the sensing process, the Non-3GPP device acts as a sensing transmitter, transmitting radio signals to the sensing object, or as a sensing receiver, detecting sensing data based on the radio signals reflected by the sensing object.

[0149] Optionally, the "transmit-only" sensing mode can be understood as the Non-3GPP device only transmits radio signals to the sensing object and does not receive radio signals reflected by the sensing object, i.e., the "A transmits B receives" sensing mode, where A represents the Non-3GPP device; the "transmit and receive" sensing mode can be understood as the Non-3GPP device both transmits radio signals to the sensing object and receives radio signals reflected by the sensing object, i.e., the "A transmits A receives" sensing mode.

[0150] The sensing cycle refers to the periodic information of a Non-3GPP device performing sensing operations, including but not limited to the frequency at which the Non-3GPP device senses an object and the duration of each sensing session. For example, a Non-3GPP device senses an object at a certain frequency f, and the duration of each sensing session is t.

[0151] As can be understood, the sensing measurement type refers to the type of sensing measurement required when a Non-3GPP device performs sensing operations on the sensing object. Sensing measurement parameters are the parameters used to identify the sensing data of the sensing object.

[0152] Optionally, when the sensed measurement parameters include angular accuracy, they may specifically include: horizontal angular accuracy and / or vertical angular accuracy.

[0153] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device are identified by at least one of the device identifier of the Non-3GPP device and the device identifier of the UE bound to the Non-3GPP device.

[0154] Optionally, a Non-3GPP device can directly send its sensing capabilities and / or sensing information to the network device; alternatively, a UE bound to the Non-3GPP device can send the Non-3GPP device's sensing capabilities and / or sensing information to the network device. In this way, at least one network element in the network device can determine whether to treat the Non-3GPP device as a sensing entity and perform sensing on the sensing object based on the Non-3GPP device's sensing capabilities and / or sensing information.

[0155] In the above embodiments, the identification of the sensing capabilities and / or sensing information of the Non-3GPP device can be identified by at least one of the device identifier of the Non-3GPP device and the device identifier of the UE bound to the Non-3GPP device.

[0156] Optionally, Non-3GPP equipment may transmit its sensing capabilities and / or sensing information in any of the following ways:

[0157] Method 1 (combination of 1a and 2a):

[0158] 1a. Non-3GPP equipment transmits its sensing capabilities and / or sensing information to a first network element. The first network element may include an AF (AF-enabled) network element.

[0159] 2a. The first network element transmits the received sensing capabilities and / or sensing information to the second network element via the fifth network element. The second network element stores the sensing capabilities and / or sensing information of the Non-3GPP equipment. The second network element may include a data storage function network element. The fifth network element may include a NEF network element.

[0160] Optionally, the data storage function network element may include, but is not limited to, UDM network element, UDR network element, or sensor data storage function network element.

[0161] Method 2 (combination of 1b and 2b):

[0162] 1b. Non-3GPP devices transmit their sensing capabilities and / or sensing information to a first device. The first device may be a UE / gateway.

[0163] 2b. The first device transmits the sensing capabilities and / or sensing information of the Non-3GPP device to the third network element, and the third network element transmits the sensing capabilities and / or sensing information of the Non-3GPP device to the second network element, which stores the sensing capabilities and / or sensing information of the Non-3GPP device. The third network element may include an SMF network element.

[0164] Step 202: The Non-3GPP device receives a sensing task request; wherein the sensing task request is used to request the Non-3GPP device to perform a sensing task.

[0165] Optionally, after at least one network element in the network device receives a sensing service request, it can determine, based on the sensing capabilities and / or sensing information of at least one sensing entity, that a Non-3GPP device is selected as a sensing entity to provide the sensing task requested in the sensing service request. In this case, a sensing task request can be determined, and the sensing task request can be sent to the Non-3GPP device through a UE bound to the Non-3GPP device, requesting the Non-3GPP device to perform the sensing task.

[0166] Optionally, the sensed entity may include, but is not limited to, at least one of the following: UE, gNB, Non-3GPP equipment, etc.

[0167] In this embodiment of the disclosure, the Non-3GPP device can report its sensing capabilities and / or sensing information; thus, the upstream device of the Non-3GPP device can determine whether to designate the Non-3GPP device as a sensing entity to sense the sensing object based on the sensing capabilities and / or sensing information reported by the Non-3GPP device. Furthermore, the Non-3GPP device can execute the sensing task indicated by the received sensing task request.

[0168] In some embodiments, the sensing task request includes at least one of the following: the device identifier of the UE bound to the Non-3GPP device, the device identifier of the Non-3GPP device, the sensing task policy of the sensing task, and a pre-configured URSP rule.

[0169] Optionally, the perception task strategy of the perception task may include strategy information that needs to be associated with the perception task being performed. For example, it may include, but is not limited to, the object identifier of the perception object, information on perceiving the perception object (e.g., the shape, size, direction, speed, position, etc. of the perception object).

[0170] In some embodiments, receiving the perception task request includes:

[0171] The fourth network element receives a sensing task request from the first device; wherein the sensing task request is sent to the first device after the fourth network element receives the sensing service request and determines the Non-3GPP device as the sensing entity to perform the sensing task from the at least one sensing entity stored in the second network element based on the sensing capabilities and / or sensing information of the at least one sensing entity.

[0172] A perception service request is used to request the execution of a perception task; at least one perception entity includes: UE, gNB, or Non-3GPP equipment.

[0173] In some embodiments, the fourth network element may include: a sensing service provider.

[0174] Optionally, before receiving the sensing task request sent by the first device, the above method may further include: the first device establishing a wired or wireless connection with the Non-3GPP device; the first device determining, based on pre-configured URSP (UE Route Selection Policy) rules, whether to establish a new PDU (Packet Data Unit) session with the third network element or to reuse an existing PDU session (hereinafter referred to as the first PDU session).

[0175] Optionally, before the Non-3GPP device establishes a wired or wireless connection with the first device, the first device may establish a PDU session (hereinafter referred to as "second PDU session") with the third network element.

[0176] After the Non-3GPP device establishes a wired or wireless connection with the first device, the first device and the third network element can determine, based on pre-configured URSP rules, whether to establish a new PDU session or reuse an existing PDU session (i.e., a second PDU session) for the Non-3GPP device. The new PDU session established or the existing PDU session reused between the Non-3GPP device and the first device is the aforementioned "first PDU session," thus enabling matching between the first PDU session and the Non-3GPP device.

[0177] Taking the first device as a UE as an example, the connection method between the first device and the Non-3GPP device can be referred to the embodiments shown in Figures 4 and 5 above.

[0178] As mentioned above, the fourth network element may include an SF network element. The second network element may include a data storage function network element.

[0179] Optionally, SF network elements may include sensing service providers in the network. Data storage function network elements may include, but are not limited to, at least one of UDM, UDR, or sensing data storage function network elements.

[0180] Optionally, the SF network element can receive sensing service requests sent by a sensing consumer or user. Specifically, after receiving a sensing service request from a sensing consumer or user, the SF network element can provide sensing services to that sensing consumer or user by configuring a sensing entity to perform sensing tasks.

[0181] Optionally, after receiving a sensing service request, the fourth network element can interact with the data storage function network element to retrieve the sensing capabilities and / or sensing information of at least one sensing entity stored in the data storage function network element, and determine the sensing entity capable of performing the aforementioned sensing task from among the at least one sensing entity. For example, the sensing entity determined by the fourth network element can be any one of the at least one sensing entities mentioned above.

[0182] Optionally, if the sensing entity determined by the fourth network element is a Non-3GPP device, the aforementioned sensing task request can be determined and sent to the first device, instructing the first device to send the sensing task request to the Non-3GPP device to request the Non-3GPP device to perform the aforementioned sensing task.

[0183] Figure 6 is a second interactive schematic diagram of the sensing entity selection method according to an embodiment of the present disclosure. Referring to the above, the first network element may include an AF network element. The second network element may include a data storage function network element. The third network element may include an SMF network element. The fourth network element may include an SF network element. The fifth network element may include a NEF network element. As shown in Figure 6, the above method may include:

[0184] Step 601: The Non-3GPP device sends its sensing capabilities and / or sensing information to the first network element, instructing the first network element to send the same sensing capabilities and / or sensing information to the second network element. Correspondingly, the first network element receives the Non-3GPP device's sensing capabilities and / or sensing information.

[0185] In some embodiments, the second network element includes at least one of UDM, UDR, or sensing data storage function network element.

[0186] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device include at least one of the following:

[0187] Sensing indication information; the sensing indication information includes: whether sensing services are supported;

[0188] Sensing data processing capability; the sensing data processing capability includes: whether it supports local processing of sensing data;

[0189] Identity perception; the identity perception includes: a sensing transmitter and / or a sensing receiver;

[0190] Aware RAT; the aware RAT includes: 3GPP and / or non-3GPP;

[0191] The sensing mode includes at least one of the following: sending only, sending and receiving, number of sensing times, and sensing period.

[0192] The perception plane includes the control plane, user plane, data plane, and perception plane.

[0193] Sensing methods; the sensing methods include at least one of GNSS, OTDOA, TBS, TDOA, AoD, Multi-RTT, AoA, WLAN, Bluetooth, lidar, radar, and sonar;

[0194] Sensing service performance; the sensing service performance includes at least one of the following: latency, sensing measurement resolution, QoS, sensing service priority, time period, sensing measurement type, start time, end time, and sensing result;

[0195] Sensing measurement types; the sensing measurement types include at least one of: position, distance, angle, speed, recognition, detection, reconstruction, imaging, tracking, and monitoring;

[0196] Sensing measurement parameters; the sensing measurement parameters include at least one of the following: position, distance, speed, angle accuracy, sensing frequency, bandwidth, time-frequency resource block, number of antennas, refresh rate, maximum sensing delay, missed alarm probability, false alarm probability, reconstruction accuracy, imaging accuracy, and confidence level.

[0197] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device are identified by at least one of the device identifier of the Non-3GPP device and the device identifier of the UE bound to the Non-3GPP device.

[0198] Optionally, the specific information indicating the sensing capabilities and / or sensing information of the Non-3GPP device can be found in the instruction manual section of step 201, and will not be repeated here.

[0199] Step 602: The first network element sends the sensing capabilities and / or sensing information of the Non-3GPP device to the second network element. Correspondingly, the second network element receives the sensing capabilities and / or sensing information of the Non-3GPP device sent by the first network element.

[0200] Optionally, in some embodiments, the first network element can send the sensing capabilities and / or sensing information of the Non-3GPP device to the second network element through the fifth network element. Correspondingly, the second network element can receive the sensing capabilities and / or sensing information of the Non-3GPP device sent by the first network element through the fifth network element.

[0201] Step 603: The second network element stores the sensing capabilities and / or sensing information of the Non-3GPP device.

[0202] In the above embodiments, through the embodiments shown in steps 601 to 603, the Non-3GPP device can send the Non-3GPP device's sensing capabilities and / or sensing information to the second network element through the first network element, and store the Non-3GPP device's sensing capabilities and / or sensing information through the second network element.

[0203] Step 604: The fourth network element receives a sensing service request; the sensing service request is used to request the execution of a sensing task.

[0204] Optionally, the fourth network element can receive sensing service requests sent by sensing consumers or users.

[0205] Step 605: The fourth network element determines the Non-3GPP device as the sensing entity performing the sensing task from the at least one sensing entity stored in the second network element, based on the sensing capabilities and / or sensing information of at least one sensing entity; the at least one sensing entity includes: the UE, gNB, or the Non-3GPP device.

[0206] Optionally, after receiving a sensing service request, the fourth network element can interact with the second network element to retrieve the sensing capabilities and / or sensing information of at least one sensing entity stored in the second network element, and determine from the at least one sensing entity that can perform the aforementioned sensing task. For example, the sensing entity determined by the fourth network element can be any one of the at least one sensing entities.

[0207] Optionally, this embodiment of the disclosure uses a Non-3GPP device as the sensing entity determined by the fourth network element for illustration.

[0208] Step 606: The fourth network element determines the sensing task request; the sensing task request is used to request the Non-3GPP device to perform the sensing task.

[0209] Step 607: The fourth network element sends a sensing task request to the first device. Correspondingly, the first device receives the sensing task request sent by the first device.

[0210] In some embodiments, the sensing task request includes at least one of the following: the device identifier of the UE bound to the Non-3GPP device, the device identifier of the Non-3GPP device, the sensing task policy of the sensing task, and a pre-configured URSP rule.

[0211] Optionally, you can refer to the description of the perception task request in step 201 above, which will not be repeated here.

[0212] Step 608: The first device sends a sensing task request to the Non-3GPP device. Correspondingly, the Non-3GPP device receives the sensing task request sent by the first device.

[0213] Optionally, before step 601, the above method may further include: the first device establishing a wired or wireless connection with the Non-3GPP device; the first device determining, based on pre-configured URSP rules, whether to establish a new PDU session with the third network element or reuse an existing PDU session (hereinafter referred to as the first PDU session).

[0214] Step 609: The first device sends a PDU session establishment request or a PDU session modification request to the third network element based on the pre-configured URSP rules; correspondingly, the third network element receives the PDU session establishment request or PDU session modification request sent by the first device.

[0215] The PDU session establishment request is used to request the establishment of a new PDU session with the third network element; the PDU session modification request is used to request the third network element to modify the existing PDU session.

[0216] Optionally, the PDU session modification request can be specifically used to request a third network element to modify the first PDU session.

[0217] Step 610: The third network element establishes a new PDU session with the first device or modifies an existing PDU session.

[0218] Figure 7 is a third interactive schematic diagram of a perceptual entity selection method according to an embodiment of the present disclosure. Referring to Figure 7, the method includes:

[0219] Step 701: The Non-3GPP device sends its sensing capabilities and / or sensing information to the first device, instructing the first device to send its sensing capabilities and / or sensing information to the third network element; correspondingly, the first device receives the Non-3GPP device's sensing capabilities and / or sensing information sent by the Non-3GPP device.

[0220] The first device includes a user equipment (UE) or a gateway.

[0221] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device include at least one of the following:

[0222] Sensing indication information; the sensing indication information includes: whether sensing services are supported;

[0223] Sensing data processing capability; the sensing data processing capability includes: whether it supports local processing of sensing data;

[0224] Identity perception; the identity perception includes: a sensing transmitter and / or a sensing receiver;

[0225] Aware RAT; the aware RAT includes: 3GPP and / or non-3GPP;

[0226] The sensing mode includes at least one of the following: sending only, sending and receiving, number of sensing times, and sensing period.

[0227] The perception plane includes the control plane, user plane, data plane, and perception plane.

[0228] Sensing methods; the sensing methods include at least one of GNSS, OTDOA, TBS, TDOA, AoD, Multi-RTT, AoA, WLAN, Bluetooth, lidar, radar, and sonar;

[0229] Sensing service performance; the sensing service performance includes at least one of the following: latency, sensing measurement resolution, QoS, sensing service priority, time period, sensing measurement type, start time, end time, and sensing result;

[0230] Sensing measurement types; the sensing measurement types include at least one of: position, distance, angle, speed, recognition, detection, reconstruction, imaging, tracking, and monitoring;

[0231] Sensing measurement parameters; the sensing measurement parameters include at least one of the following: position, distance, speed, angle accuracy, sensing frequency, bandwidth, time-frequency resource block, number of antennas, refresh rate, maximum sensing delay, missed alarm probability, false alarm probability, reconstruction accuracy, imaging accuracy, and confidence level.

[0232] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device are identified by at least one of the device identifier of the Non-3GPP device and the device identifier of the UE bound to the Non-3GPP device.

[0233] Optionally, the specific information indicating the sensing capabilities and / or sensing information of the Non-3GPP device can be found in the instruction manual section of step 201, and will not be repeated here.

[0234] In some embodiments, before the Non-3GPP device sends its sensing capabilities and / or sensing information to the first device, the first device establishes a wired or wireless connection with the Non-3GPP device; the first device determines, based on pre-configured URSP rules, whether to establish a new PDU session with the third network element or to reuse an existing PDU session.

[0235] Step 702: The first device sends the sensing capabilities and / or sensing information of the Non-3GPP device to the third network element. Correspondingly, the third network element receives the sensing capabilities and / or sensing information of the Non-3GPP device sent by the first device.

[0236] In some embodiments, before sending the sensing capability and / or sensing information of the Non-3GPP device to the first device, the method further includes:

[0237] The first device establishes a wired or wireless connection with the Non-3GPP device; based on pre-configured URSP rules, the first device determines whether to establish a new PDU session with the third network element or reuse an existing PDU session.

[0238] Step 703: The third network element sends the sensing capabilities and / or sensing information of the Non-3GPP device to the second network element. Correspondingly, the second network element receives the sensing capabilities and / or sensing information of the Non-3GPP device sent by the third network element.

[0239] Step 704: The second network element stores the sensing capabilities and / or sensing information of the Non-3GPP device.

[0240] In the above embodiments, through the embodiments shown in steps 701 to 704, the Non-3GPP device can sequentially transmit its sensing capabilities and / or sensing information to the second network element via the first device, the fourth network element, and the second network element, and store the Non-3GPP device's sensing capabilities and / or sensing information through the second network element.

[0241] Step 705: The fourth network element receives a sensing service request; the sensing service request is used to request the execution of a sensing task.

[0242] Optionally, the specific implementation of step 705 can be found in the specific implementation of step 604, and will not be repeated here.

[0243] Step 706: The fourth network element determines the Non-3GPP device as the sensing entity to perform the sensing task from the at least one sensing entity stored in the second network element, based on the sensing capabilities and / or sensing information of at least one sensing entity; the at least one sensing entity includes: the UE, gNB, or the Non-3GPP device.

[0244] Optionally, the specific implementation of step 706 can be found in the specific implementation of step 605, and will not be repeated here.

[0245] Step 707: The fourth network element determines the sensing task request; the sensing task request is used to request the Non-3GPP device to perform the sensing task.

[0246] In some embodiments, the sensing task request includes at least one of the following: the device identifier of the UE bound to the Non-3GPP device, the device identifier of the Non-3GPP device, the sensing task policy of the sensing task, and a pre-configured URSP rule.

[0247] Optionally, the specific implementation of step 707 can be found in the specific implementation of step 606, and will not be repeated here.

[0248] Step 708: The fourth network element sends a sensing task request to the first device; the sensing task request is used to request the Non-3GPP device to perform a sensing task.

[0249] Optionally, the specific implementation of step 708 can be found in the specific implementation of step 607, and will not be repeated here.

[0250] Step 709: The first device sends a sensing task request to the Non-3GPP device. Correspondingly, the Non-3GPP device receives the sensing task request sent by the first device.

[0251] Optionally, the specific implementation of step 709 can be found in the specific implementation of step 608, and will not be repeated here.

[0252] Step 710: The first device sends a PDU session establishment request or a PDU session modification request to the third network element based on the pre-configured URSP rules; correspondingly, the third network element receives the PDU session establishment request or PDU session modification request sent by the first device.

[0253] The PDU session establishment request is used to request the establishment of a new PDU session with the third network element; the PDU session modification request is used to request the third network element to modify the existing PDU session.

[0254] Optionally, the specific implementation of step 710 can be found in the specific implementation of step 609, which will not be elaborated here.

[0255] Step 711: The third network element establishes a new PDU session with the first device, which modifies the existing PDU session modification request.

[0256] To address the aforementioned issues, this disclosure provides a mechanism whereby a Non-3GPP device reports its awareness capabilities to a network device, and the network device identifies and organizes the Non-3GPP device to provide awareness services based on its awareness capabilities. Referring to Figure 8, this mechanism may specifically include the following execution steps:

[0257] 0a. Non-3GPP devices connect to the UE / gateway via wired or wireless means.

[0258] 0b. The UE / gateway determines whether to establish a new PDU session with the network device or reuse an existing PDU session based on pre-configured URSP rules, thereby enabling the PDU session to match with the Non-3GPP device.

[0259] Optionally, the data storage function network element can store the sensing capabilities and / or sensing information of Non-3GPP devices through an embodiment consisting of 1a and 2a or an embodiment consisting of 1b and 2b.

[0260] 1a. Non-3GPP equipment sends its sensing capabilities and / or sensing information to the AF.

[0261] Optionally, the sensing capabilities and / or sensing information of a Non-3GPP device can be identified by the Non-3GPP device ID, or by the device ID of the UE bound to the Non-3GPP device.

[0262] Optionally, the sensing capabilities and / or sensing information of a Non-3GPP device may include at least one of the following:

[0263] A. Sensing indication information. Optionally, the sensing indication information may include: whether the Non-3GPP device supports sensing services.

[0264] Optionally, when the Non-3GPP equipment supports sensing services, the sensing capabilities and / or sensing information of the Non-3GPP equipment may further include at least one of B to G; when the Non-3GPP equipment supports sensing services, the sensing capabilities and / or sensing information of the Non-3GPP equipment may not include any one of B to G.

[0265] B. Sensing data processing capability. Optionally, sensing data processing capability may include: whether the Non-3GPP device supports processing sensing data locally.

[0266] Optionally, if the Non-3GPP device supports processing sensing data locally, it may also include the computing power of the Non-3GPP device in processing sensing data. For example, the computing power of the Non-3GPP device in processing sensing data can be identified by the parameter values ​​of parameters such as Flops and Ops.

[0267] C. Sensing Identity. Optionally, sensing identity includes: sensing transmitter and / or sensing receiver; that is, during the sensing process of Non-3GPP equipment, it is a sensing transmitter and / or sensing receiver.

[0268] D. Sensitive RAT; Sensitive RAT includes: 3GPP and / or non-3GPP.

[0269] E. Sensing mode. Optionally, the sensing mode includes at least one of: sending only, sending and receiving, sensing count, and sensing period.

[0270] F. Perception Plane. Optionally, the perception plane includes the control plane, user plane, data plane, and perception plane.

[0271] G. Sensing method. Optionally, the sensing method includes at least one of the following: GNSS, OTDOA, TBS, TDOA, AoD, Multi-RTT, AoA, WLAN, Bluetooth, LiDAR, radar, and sonar.

[0272] H. Sensing service performance. Optionally, sensing service performance includes at least one of the following: latency, sensing measurement resolution, QoS, sensing service priority, time period, sensing measurement type, start time, end time, and sensing result.

[0273] I. Types of Sensing Measurements. Optionally, types of sensing measurements include at least one of the following: position, distance, angle, velocity, recognition, detection, reconstruction, imaging, tracking, and monitoring.

[0274] G. Sensing Measurement Parameters. Optionally, the sensing measurement parameters include at least one of the following: position, distance, velocity, angular accuracy, sensing frequency, bandwidth, time-frequency resource block, number of antennas, refresh rate, maximum sensing delay, false alarm probability, reconstruction accuracy, imaging accuracy, and confidence level. Angular accuracy may include horizontal angular accuracy and / or vertical angular accuracy.

[0275] 2a.AF transmits the received sensing capabilities and / or sensing information to the data storage function network element via NEF, and the data storage function network element stores the sensing capabilities and / or sensing information of Non-3GPP equipment.

[0276] Optionally, the data storage function network element may include, but is not limited to, UDM (Unified Data Management) network element, UDR (Unified Data Repository) network element, or sensor data storage function network element.

[0277] 1b. Non-3GPP devices send their sensing capabilities and / or sensing information to the UE / gateway.

[0278] 2b. The UE / gateway sends the sensing capabilities and / or sensing information of the Non-3GPP device to the SMF, and the SMF sends the sensing capabilities and / or sensing information of the Non-3GPP device to the data storage function network element, which stores the sensing capabilities and / or sensing information of the Non-3GPP device.

[0279] 3. SF receives the perception service request sent by the consumer.

[0280] 4.SF retrieves the sensing capabilities of at least one sensing entity from the information stored in the data storage function network element.

[0281] Optionally, at least one sensing entity includes at least one of the following: UE, gNB, and Non-3GPP equipment.

[0282] 5. SF configures the perception service and determines the perception entity and perception service request based on the received perception capability information and perception service request.

[0283] Optionally, the sensing task can also be transmitted from the SF to the UE (i.e., the aforementioned UE / gateway) via the control plane, user plane, data plane, or sensing plane.

[0284] 6. The sensing service provider sends a sensing task request to the UE (i.e., the aforementioned UE / gateway) bound to the Non-3GPP device, and the UE routes the sensing task request to the Non-3GPP device.

[0285] Optionally, the sensing task request may include, but is not limited to, at least one of the following: the UE's device identifier, the Non-3GPP device's device identifier, the sensing task policy, and the URSP rule. The sensing task policy may include, but is not limited to, at least one of the following: sensing method, sensing mode, and sensing measurement parameters.

[0286] 7. Based on the pre-configured URSP rules, the UE determines to send a PDU session establishment request and / or PDU session modification request to the SMF, thereby establishing a new PDU session or modifying the current PDU session.

[0287] Through the above mechanism, Non-3GPP devices can report their awareness capabilities to network devices, and network devices can identify and arrange Non-3GPP devices to provide awareness services.

[0288] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0289] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0290] In some embodiments, terms such as wireless access scheme and waveform can be used interchangeably.

[0291] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0292] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0293] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing any further processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0294] The communication signal transmission and reception method involved in the embodiments of this disclosure may include the foregoing steps and at least one of the embodiments. For example, step 201 may be implemented as a separate embodiment, step 202 may be implemented as a separate embodiment, and so on.

[0295] Step 601 can be implemented as an independent embodiment; step 602 can be implemented as an independent embodiment; step 603 can be implemented as an independent embodiment; step 604 can be implemented as an independent embodiment; step 605 can be implemented as an independent embodiment; step 606 can be implemented as an independent embodiment; step 607 can be implemented as an independent embodiment; step 608 can be implemented as an independent embodiment; step 609 can be implemented as an independent embodiment; step 610 can be implemented as an independent embodiment; step 701 can be implemented as an independent embodiment; step 702 can be implemented as an independent embodiment; step 703 can be implemented as an independent embodiment; step 704 can be implemented as an independent embodiment. Step 705 can be implemented as an independent embodiment, step 706 can be implemented as an independent embodiment, step 707 can be implemented as an independent embodiment, step 708 can be implemented as an independent embodiment, step 709 can be implemented as an independent embodiment, step 710 can be implemented as an independent embodiment, step 711 can be implemented as an independent embodiment, step 0a can be implemented as an independent embodiment, step 0b can be implemented as an independent embodiment, step 1a can be implemented as an independent embodiment, step 1b can be implemented as an independent embodiment, step 2a can be implemented as an independent embodiment, step 2b can be implemented as an independent embodiment, step 3 can be implemented as an independent embodiment. The following steps can be implemented as independent embodiments: Step 4 can be implemented as an independent embodiment; Step 5 can be implemented as an independent embodiment; Step 6 can be implemented as an independent embodiment; Step 7 can be implemented as an independent embodiment; The combination of Step 201 and Step 202 can be implemented as an independent embodiment; The combination of Step 601 and Step 602 can be implemented as an independent embodiment; The combination of Step 601, Step 602, Step 603, Step 604 can be implemented as an independent embodiment; The combination of Step 601, Step 602, Step 603, Step 604, Step 605 can be implemented as an independent embodiment. For example, the combination of steps 604 and 605 can be implemented as an independent embodiment; the combination of steps 601, 602, 603, 604, 605, and 606 can be implemented as an independent embodiment; the combination of steps 601, 602, 603, 604, 605, 606, and 607 can be implemented as an independent embodiment; the combination of steps 604, 605, 606, and 607 can be implemented as an independent embodiment; and the combination of steps 601, 602, 603, 604, 605, 606, 607, and 608 can be implemented as an independent embodiment.The combination of steps 601, 602, 603, 604, 605, 606, 607, 608, and 609 can be implemented as an independent embodiment; the combination of steps 601, 602, 603, 604, 605, 606, 607, 608, 609, and 610 can be implemented as an independent embodiment; the combination of steps 609 and 610 can be implemented as an independent embodiment; the combination of steps 701 and 702 can be implemented as an independent embodiment; the combination of steps 701, 702, and 703 can be implemented as an independent embodiment; the combination of steps 701, 702, and 709 can be implemented as an independent embodiment. The combination of step 3 and step 704 can be implemented as an independent embodiment; the combination of steps 701, 702, 703, 704 and step 705 can be implemented as an independent embodiment; the combination of steps 704 and 705 can be implemented as an independent embodiment; the combination of steps 701, 702, 703, 704, 705 and step 706 can be implemented as an independent embodiment; the combination of steps 701, 702, 703, 704, 705, 706 and step 707 can be implemented as an independent embodiment; the combination of steps 705, 706 and step 707 can be implemented as an independent embodiment; steps 701, 702... The combination of steps 703, 704, 705, 706, 707, and 708 can be implemented as an independent embodiment; the combination of steps 701, 702, 703, 704, 705, 706, 707, 708, and 709 can be implemented as an independent embodiment; the combination of steps 705, 706, 707, 708, and 709 can be implemented as an independent embodiment; the combination of steps 701, 702, 703, 704, 705, 706, 707, 708, 709, and 710 can be implemented as an independent embodiment; step 701… Steps 702, 703, 704, 705, 706, 707, 708, 709, 710, and 711 can be implemented as an independent embodiment; the combination of steps 710 and 711 can be implemented as an independent embodiment; the combination of steps 0a and 0b can be implemented as an independent embodiment; the combination of steps 0a, 0b, 1a, and 2a can be implemented as an independent embodiment; the combination of steps 1a and 2a can be implemented as an independent embodiment; the combination of steps 0a, 0b, 1b, and 2b can be implemented as an independent embodiment; and the combination of steps 1b and 2b can be implemented as an independent embodiment.The combination of steps 3, 4, and 5 can be implemented as an independent embodiment; the combination of steps 3, 4, 5, and 6 can be implemented as an independent embodiment; the combination of steps 3, 4, 5, 6, and 7 can be implemented as an independent embodiment; the combination of steps 0a, 0b, 1a, 2a, 3, 4, and 5 can be implemented as an independent embodiment; the combination of steps 0a, 0b, 1a, 2a, 3, 4, 5, and 6 can be implemented as an independent embodiment; the combination of steps 0a, 0b, 1a, 2a, 3, 4, 5, and 6 can be implemented as an independent embodiment; the combination of steps 0a, 0b, 1a, 2a, 3, 4, 5, and 6 can be implemented as an independent embodiment. The combination of steps 1a, 2a, 3, 4, 5, 6, and 7 can be implemented as an independent embodiment, as can the combination of steps 0a, 0b, 1b, 2b, 3, 4, and 5, as can the combination of steps 0a, 0b, 1b, 2b, 3, 4, 5, and 6, as can the combination of steps 0a, 0b, 1b, 2b, 3, 4, 5, 6, and 7, as can the combination of steps 0a, 0b, 1b, 2b, 3, 4, 5, 6, and 7, as an independent embodiment, but is not limited thereto.

[0296] In some embodiments, other optional implementations may be described before or after the specification corresponding to Figures 2 to 8.

[0297] Figure 9 is a flowchart illustrating a perceptual entity selection method according to an embodiment of the present disclosure.

[0298] As shown in Figure 9, the above method can be applied to Non-3GPP equipment, and the method includes:

[0299] Step 901: Send the sensing capabilities and / or sensing information of the Non-3GPP device.

[0300] Step 902: Receive a sensing task request; wherein the sensing task request is used to request the Non-3GPP device to perform a sensing task.

[0301] In some embodiments, transmitting the sensing capabilities and / or sensing information of the Non-3GPP device includes:

[0302] Send the sensing capabilities and / or sensing information of the Non-3GPP device to the first network element, and instruct the first network element to send the sensing capabilities and / or sensing information of the Non-3GPP device to the second network element.

[0303] In some embodiments, transmitting the sensing capabilities and / or sensing information of the Non-3GPP device includes:

[0304] Sending the sensing capabilities and / or sensing information of the Non-3GPP device to a first device, and instructing the first device to send the sensing capabilities and / or sensing information of the Non-3GPP device to a third network element; wherein, the first device includes a user equipment (UE) or a gateway.

[0305] In some embodiments, before sending the sensing capabilities and / or sensing information of the Non-3GPP device to the first device, the method further includes:

[0306] The first device establishes a wired or wireless connection with the Non-3GPP device; based on pre-configured URSP rules, the first device determines whether to establish a new PDU session with the third network element or reuse an existing PDU session.

[0307] In some embodiments, receiving a sensing task request includes:

[0308] The fourth network element receives a sensing task request sent by the first device; wherein the sensing task request is sent to the first device after the fourth network element receives the sensing service request, determines the Non-3GPP device as the sensing entity to perform the sensing task from the at least one sensing entity stored by the second network element based on the sensing capabilities and / or sensing information of the at least one sensing entity;

[0309] The perception service request is used to request the execution of the perception task; at least one perception entity includes: UE, gNB or Non-3GPP device.

[0310] In some embodiments, the sensing task request includes at least one of the following: the device identifier of the UE bound to the Non-3GPP device, the device identifier of the Non-3GPP device, the sensing task policy of the sensing task, and a pre-configured URSP rule.

[0311] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device are identified by at least one of the device identifier of the Non-3GPP device and the device identifier of the UE bound to the Non-3GPP device.

[0312] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device include at least one of the following:

[0313] Sensing indication information; the sensing indication information includes: whether sensing services are supported;

[0314] Sensing data processing capability; the sensing data processing capability includes: whether it supports local processing of sensing data;

[0315] Identity perception; the identity perception includes: a sensing transmitter and / or a sensing receiver;

[0316] Aware RAT; the aware RAT includes: 3GPP and / or non-3GPP;

[0317] The sensing mode includes at least one of the following: sending only, sending and receiving, number of sensing times, and sensing period.

[0318] The perception plane includes the control plane, user plane, data plane, and perception plane.

[0319] Sensing methods; the sensing methods include at least one of GNSS, OTDOA, TBS, TDOA, AoD, Multi-RTT, AoA, WLAN, Bluetooth, lidar, radar, and sonar;

[0320] Sensing service performance; the sensing service performance includes at least one of the following: latency, sensing measurement resolution, QoS, sensing service priority, time period, sensing measurement type, start time, end time, and sensing result;

[0321] Sensing measurement types; the sensing measurement types include at least one of: position, distance, angle, speed, recognition, detection, reconstruction, imaging, tracking, and monitoring;

[0322] Sensing measurement parameters; the sensing measurement parameters include at least one of the following: position, distance, speed, angle accuracy, sensing frequency, bandwidth, time-frequency resource block, number of antennas, refresh rate, maximum sensing delay, missed alarm probability, false alarm probability, reconstruction accuracy, imaging accuracy, and confidence level.

[0323] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0324] The perceptual entity selection method disclosed herein may include the foregoing steps and at least one of the embodiments. For example, step 901 may be implemented as a separate embodiment, and step 902 may be implemented as a separate embodiment; a combination of steps 901 and 902 may be implemented as a separate embodiment, but is not limited thereto.

[0325] In some embodiments, other alternative implementations described before or after the specification corresponding to Figure 9 may be referred to.

[0326] Figure 10 is a flowchart illustrating a perceptual entity selection method according to an embodiment of the present disclosure.

[0327] As shown in Figure 10, the above method can be applied to a first device, which includes a UE or a gateway, and the method includes:

[0328] Step 1001: Receive the sensing capabilities and / or sensing information of the Non-3GPP device sent by the Non-3GPP device.

[0329] Step 1002: Send a sensing task request to the Non-3GPP device; wherein the sensing task request is used to request the Non-3GPP device to perform a sensing task.

[0330] In some embodiments, after receiving the sensing capabilities and / or sensing information of the Non-3GPP device sent by the Non-3GPP device, the method further includes:

[0331] Send the sensing capabilities and / or sensing information of the Non-3GPP device to the third network element, and instruct the third network element to send the sensing capabilities and / or sensing information of the Non-3GPP device to the second network element.

[0332] In some embodiments, before receiving the sensing capabilities and / or sensing information of the Non-3GPP device sent by the Non-3GPP device, the method includes:

[0333] The first device establishes a wired or wireless connection with the Non-3GPP device; based on pre-configured URSP rules, the first device determines whether to establish a new PDU session with the third network element or reuse an existing PDU session.

[0334] In some embodiments, before sending the sensing task request to the Non-3GPP device, the method further includes:

[0335] The fourth network element receives the sensing task request sent by the fourth network element; wherein the sensing task request is determined by the fourth network element after receiving the sensing service request, based on the sensing capabilities and / or sensing information of at least one sensing entity stored in the second network element, and after determining that the Non-3GPP device is the sensing entity to perform the sensing task from the at least one sensing entity.

[0336] The perception service request is used to perform the perception task; the at least one perception entity includes: the UE, gNB, or the Non-3GPP device.

[0337] In some embodiments, after sending the sensing task request to the Non-3GPP device, the method further includes:

[0338] Based on the pre-configured URSP rules, a PDU session establishment request or a PDU session modification request is sent to the third network element;

[0339] The PDU session establishment request is used to request the establishment of a new PDU session with the third network element; the PDU session modification request is used to request the third network element to modify the existing PDU session.

[0340] In some embodiments, the sensing task request includes at least one of the following: the device identifier of the UE bound to the Non-3GPP device, the device identifier of the Non-3GPP device, the sensing task policy of the sensing task, and a pre-configured URSP rule.

[0341] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device are identified by at least one of the device identifier of the Non-3GPP device and the device identifier of the UE bound to the Non-3GPP device.

[0342] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device include at least one of the following:

[0343] Sensing indication information; the sensing indication information includes: whether sensing services are supported;

[0344] Sensing data processing capability; the sensing data processing capability includes: whether it supports local processing of sensing data;

[0345] Identity perception; the identity perception includes: a sensing transmitter and / or a sensing receiver;

[0346] Aware RAT; the aware RAT includes: 3GPP and / or non-3GPP;

[0347] The sensing mode includes at least one of the following: sending only, sending and receiving, number of sensing times, and sensing period.

[0348] The perception plane includes the control plane, user plane, data plane, and perception plane.

[0349] Sensing methods; the sensing methods include at least one of GNSS, OTDOA, TBS, TDOA, AoD, Multi-RTT, AoA, WLAN, Bluetooth, lidar, radar, and sonar;

[0350] Sensing service performance; the sensing service performance includes at least one of the following: latency, sensing measurement resolution, QoS, sensing service priority, time period, sensing measurement type, start time, end time, and sensing result;

[0351] Sensing measurement types; the sensing measurement types include at least one of: position, distance, angle, speed, recognition, detection, reconstruction, imaging, tracking, and monitoring;

[0352] Sensing measurement parameters; the sensing measurement parameters include at least one of the following: position, distance, speed, angle accuracy, sensing frequency, bandwidth, time-frequency resource block, number of antennas, refresh rate, maximum sensing delay, missed alarm probability, false alarm probability, reconstruction accuracy, imaging accuracy, and confidence level.

[0353] The perceptual entity selection method involved in the embodiments of this disclosure may include the foregoing steps and at least one of the embodiments. For example, step 1001 may be implemented as a separate embodiment, step 1002 may be implemented as a separate embodiment, and the combination of step 1001 and step 1002 may be implemented as a separate embodiment, but is not limited thereto.

[0354] In some embodiments, other alternative implementations described before or after the specification corresponding to FIG10 may be referred to.

[0355] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0356] Figure 11 is a flowchart illustrating a sensing entity selection method according to an embodiment of the present disclosure.

[0357] As shown in Figure 11, the above method can be applied to the third network element, and the method includes:

[0358] Step 1101: Receive the sensing capabilities and / or sensing information of the Non-3GPP device sent by the first device; the first device includes a UE or a gateway.

[0359] In some embodiments, before receiving the sensing capabilities and / or sensing information of the Non-3GPP device sent by the first device, the method further includes:

[0360] The first device establishes a wired or wireless connection with the Non-3GPP device; based on pre-configured URSP rules, the first device determines whether to establish a new PDU session with the third network element or reuse an existing PDU session.

[0361] In some embodiments, after receiving the sensing capabilities and / or sensing information of the Non-3GPP device sent by the first device, the method further includes:

[0362] Send the sensing capabilities and / or sensing information of the Non-3GPP device to the second network element.

[0363] In some embodiments, after receiving the sensing capabilities and / or sensing information of the Non-3GPP device sent by the first device, the method further includes: receiving a PDU session establishment request or a PDU session modification request sent by the first device;

[0364] The PDU session establishment request is used to request the establishment of a new PDU session with the third network element; the PDU session modification request is used to request the third network element to modify the existing PDU session.

[0365] The PDU session establishment request is sent by the first device based on pre-configured URSP rules.

[0366] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device are identified by at least one of the device identifier of the Non-3GPP device and the device identifier of the UE bound to the Non-3GPP device.

[0367] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device include at least one of the following:

[0368] Sensing indication information; the sensing indication information includes: whether sensing services are supported;

[0369] Sensing data processing capability; the sensing data processing capability includes: whether it supports local processing of sensing data;

[0370] Identity perception; the identity perception includes: a sensing transmitter and / or a sensing receiver;

[0371] Aware RAT; the aware RAT includes: 3GPP and / or non-3GPP;

[0372] The sensing mode includes at least one of the following: sending only, sending and receiving, number of sensing times, and sensing period.

[0373] The perception plane includes the control plane, user plane, data plane, and perception plane.

[0374] Sensing methods; the sensing methods include at least one of GNSS, OTDOA, TBS, TDOA, AoD, Multi-RTT, AoA, WLAN, Bluetooth, lidar, radar, and sonar;

[0375] Sensing service performance; the sensing service performance includes at least one of the following: latency, sensing measurement resolution, QoS, sensing service priority, time period, sensing measurement type, start time, end time, and sensing result;

[0376] Sensing measurement types; the sensing measurement types include at least one of: position, distance, angle, speed, recognition, detection, reconstruction, imaging, tracking, and monitoring;

[0377] Sensing measurement parameters; the sensing measurement parameters include at least one of the following: position, distance, speed, angle accuracy, sensing frequency, bandwidth, time-frequency resource block, number of antennas, refresh rate, maximum sensing delay, missed alarm probability, false alarm probability, reconstruction accuracy, imaging accuracy, and confidence level.

[0378] In some embodiments, other alternative implementations described before or after the specification corresponding to FIG11 may be referred to.

[0379] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0380] Figure 12 is a flowchart illustrating a perceptual entity selection method according to an embodiment of the present disclosure.

[0381] As shown in Figure 12, the above method can be applied to the first network element, where the first network element can be an SF; the above method includes:

[0382] Step 1201: Receive the sensing capabilities and / or sensing information of the Non-3GPP device sent by the Non-3GPP device.

[0383] In some embodiments, after receiving the sensing capabilities and / or sensing information of the Non-3GPP device sent by the Non-3GPP device, the method further includes:

[0384] Send the sensing capabilities and / or sensing information of the Non-3GPP device to the second network element.

[0385] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device are identified by at least one of the device identifier of the Non-3GPP device and the device identifier of the UE bound to the Non-3GPP device.

[0386] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device include at least one of the following:

[0387] Sensing indication information; the sensing indication information includes: whether sensing services are supported;

[0388] Sensing data processing capability; the sensing data processing capability includes: whether it supports local processing of sensing data;

[0389] Identity perception; the identity perception includes: a sensing transmitter and / or a sensing receiver;

[0390] Aware RAT; the aware RAT includes: 3GPP and / or non-3GPP;

[0391] The sensing mode includes at least one of the following: sending only, sending and receiving, number of sensing times, and sensing period.

[0392] The perception plane includes the control plane, user plane, data plane, and perception plane.

[0393] Sensing methods; the sensing methods include at least one of GNSS, OTDOA, TBS, TDOA, AoD, Multi-RTT, AoA, WLAN, Bluetooth, lidar, radar, and sonar;

[0394] Sensing service performance; the sensing service performance includes at least one of the following: latency, sensing measurement resolution, QoS, sensing service priority, time period, sensing measurement type, start time, end time, and sensing result;

[0395] Sensing measurement types; the sensing measurement types include at least one of: position, distance, angle, speed, recognition, detection, reconstruction, imaging, tracking, and monitoring;

[0396] Sensing measurement parameters; the sensing measurement parameters include at least one of the following: position, distance, speed, angle accuracy, sensing frequency, bandwidth, time-frequency resource block, number of antennas, refresh rate, maximum sensing delay, missed alarm probability, false alarm probability, reconstruction accuracy, imaging accuracy, and confidence level.

[0397] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG12.

[0398] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0399] Figure 13 is a flowchart illustrating a perceptual entity selection method according to an embodiment of the present disclosure.

[0400] As shown in Figure 13, the above method can be applied to the first network element, wherein the first network element can be an SF; the above method includes:

[0401] Step 1301: Receive a perception service request; wherein the perception service request is used to request the execution of a perception task.

[0402] Step 1302: Based on the sensing capabilities and / or sensing information of at least one sensing entity stored in the second network element, determine the Non-3GPP device as the sensing entity to perform the sensing task from the at least one sensing entity.

[0403] Step 1303: Send a sensing task request to the first device; wherein the sensing task request is used to request the Non-3GPP device to perform a sensing task; the first device includes a UE or a gateway.

[0404] In some embodiments, the fourth network element includes: a sensing service provider.

[0405] In some embodiments, the sensing task request includes at least one of the following: the device identifier of the UE bound to the Non-3GPP device, the device identifier of the Non-3GPP device, the sensing task policy of the sensing task, and a pre-configured URSP rule.

[0406] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device include at least one of the following:

[0407] Sensing indication information; the sensing indication information includes: whether sensing services are supported;

[0408] Sensing data processing capability; the sensing data processing capability includes: whether it supports local processing of sensing data;

[0409] Identity perception; the identity perception includes: a sensing transmitter and / or a sensing receiver;

[0410] Aware RAT; the aware RAT includes: 3GPP and / or non-3GPP;

[0411] The sensing mode includes at least one of the following: sending only, sending and receiving, number of sensing times, and sensing period.

[0412] The perception plane includes the control plane, user plane, data plane, and perception plane.

[0413] Sensing methods; the sensing methods include at least one of GNSS, OTDOA, TBS, TDOA, AoD, Multi-RTT, AoA, WLAN, Bluetooth, lidar, radar, and sonar;

[0414] Sensing service performance; the sensing service performance includes at least one of the following: latency, sensing measurement resolution, QoS, sensing service priority, time period, sensing measurement type, start time, end time, and sensing result;

[0415] Sensing measurement types; the sensing measurement types include at least one of: position, distance, angle, speed, recognition, detection, reconstruction, imaging, tracking, and monitoring;

[0416] Sensing measurement parameters; the sensing measurement parameters include at least one of the following: position, distance, speed, angle accuracy, sensing frequency, bandwidth, time-frequency resource block, number of antennas, refresh rate, maximum sensing delay, missed alarm probability, false alarm probability, reconstruction accuracy, imaging accuracy, and confidence level.

[0417] The perceptual entity selection method involved in the embodiments of this disclosure may include the foregoing steps and at least one of the embodiments. For example, step 1301 may be implemented as an independent embodiment, step 1302 may be implemented as an independent embodiment, and step 1303 may be implemented as an independent embodiment; the combination of step 1301 and step 1302 may be implemented as an independent embodiment, and the combination of step 1301, step 1302 and step 1303 may be implemented as an independent embodiment, but is not limited thereto.

[0418] In some embodiments, other alternative implementations described before or after the specification corresponding to FIG13 may be referred to.

[0419] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0420] Figure 14 is a flowchart illustrating a perceptual entity selection method according to an embodiment of the present disclosure.

[0421] As shown in Figure 14, the above method can be applied to the second network element, and the method includes:

[0422] Step 1401: Receive the sensing capabilities and / or sensing information of the Non-3GPP device.

[0423] Step 1402: Store the sensing capabilities and / or sensing information of the Non-3GPP device.

[0424] In some embodiments, receiving the sensing capabilities and / or sensing information of a Non-3GPP device includes at least one of the following:

[0425] Receive the sensing capabilities and / or sensing information of the Non-3GPP equipment sent by the first network element;

[0426] Receive the sensing capabilities and / or sensing information of the Non-3GPP equipment sent by the third network element.

[0427] In some embodiments, the second network element includes at least one of UDM, UDR, or sensing data storage function network element.

[0428] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device are identified by at least one of the device identifier of the Non-3GPP device and the device identifier of the UE bound to the Non-3GPP device.

[0429] In some embodiments, the sensing capabilities and / or sensing information of the Non-3GPP device include at least one of the following:

[0430] Sensing indication information; the sensing indication information includes: whether sensing services are supported;

[0431] Sensing data processing capability; the sensing data processing capability includes: whether it supports local processing of sensing data;

[0432] Identity perception; the identity perception includes: a sensing transmitter and / or a sensing receiver;

[0433] Aware RAT; the aware RAT includes: 3GPP and / or non-3GPP;

[0434] The sensing mode includes at least one of the following: sending only, sending and receiving, number of sensing times, and sensing period.

[0435] The perception plane includes the control plane, user plane, data plane, and perception plane.

[0436] Sensing methods; the sensing methods include at least one of GNSS, OTDOA, TBS, TDOA, AoD, Multi-RTT, AoA, WLAN, Bluetooth, lidar, radar, and sonar;

[0437] Sensing service performance; the sensing service performance includes at least one of the following: latency, sensing measurement resolution, QoS, sensing service priority, time period, sensing measurement type, start time, end time, and sensing result;

[0438] Sensing measurement types; the sensing measurement types include at least one of: position, distance, angle, speed, recognition, detection, reconstruction, imaging, tracking, and monitoring;

[0439] Sensing measurement parameters; the sensing measurement parameters include at least one of the following: position, distance, speed, angle accuracy, sensing frequency, bandwidth, time-frequency resource block, number of antennas, refresh rate, maximum sensing delay, missed alarm probability, false alarm probability, reconstruction accuracy, imaging accuracy, and confidence level.

[0440] The perceptual entity selection method involved in the embodiments of this disclosure may include the foregoing steps and at least one of the embodiments. For example, step 1401 may be implemented as a separate embodiment, step 1402 may be implemented as a separate embodiment, and the combination of step 1401 and step 1402 may be implemented as a separate embodiment, but is not limited thereto.

[0441] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG14.

[0442] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0443] This disclosure also proposes an apparatus (also referred to as a sensing device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0444] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0445] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0446] Figure 15 is a schematic diagram of the structure of a Non-3GPP device according to an embodiment of this disclosure. The Non-3GPP device is used to perform any of the above methods. In some embodiments, as shown in Figure 15, the Non-3GPP device 1500 may include a transceiver module 1501.

[0447] In some embodiments, the transceiver module 1501 is configured to transmit the sensing capabilities and / or sensing information of the Non-3GPP device; and to receive a sensing task request; wherein the sensing task request is used to request the Non-3GPP device to perform a sensing task.

[0448] Optionally, the transceiver module 1501 is used to perform at least one of the transceiver steps performed by the Non-3GPP device in any of the above methods (e.g., steps 201, 202, 601, 608, 701, 709, 0a, 1b, 6, 901, 902, but not limited thereto), which will not be elaborated here.

[0449] In some embodiments, the transceiver module can be interchanged with the transceiver, the sending module, and the receiving module.

[0450] Figure 16 is a schematic diagram of the structure of a first device according to an embodiment of this disclosure. The first device is used to perform any of the above methods. In some embodiments, as shown in Figure 16, the first device 1600 may include a transceiver module 1601.

[0451] In some embodiments, the transceiver module 1601 is configured to receive the sensing capabilities and / or sensing information of the Non-3GPP device sent by the Non-3GPP device; and to send a sensing task request to the Non-3GPP device; wherein the sensing task request is used to request the Non-3GPP device to perform a sensing task.

[0452] Optionally, the transceiver module 1601 is used to perform at least one of the transceiver steps performed by the first device in any of the above methods (e.g., steps 202, 607, 608, 609, 610, 701, 702, 708, 709, 710, 711, 0a, 0b, 1b, 6, 7, 1001, 1002, but not limited thereto), which will not be elaborated here.

[0453] In some embodiments, the transceiver module can be interchanged with the transceiver, the sending module, and the receiving module.

[0454] Figure 17 is a schematic diagram of the structure of the third network element proposed in an embodiment of this disclosure. The third network element is used to perform any of the above methods. In some embodiments, as shown in Figure 17, the third network element 1700 may include: a transceiver module 1701.

[0455] In some embodiments, the transceiver module 1701 is configured to receive sensing capabilities and / or sensing information of a Non-3GPP device sent by a first device; the first device includes a UE or a gateway.

[0456] Optionally, the transceiver module 1701 is used to perform at least one of the transceiver steps performed by the third network element in any of the above methods (e.g., steps 609, 610, 710, 711, 2b, 6, 7, 1101, but not limited thereto), which will not be elaborated here.

[0457] In some embodiments, the transceiver module can be interchanged with the transceiver, the sending module, and the receiving module.

[0458] Figure 18 is a schematic diagram of the structure of the first network element proposed in an embodiment of this disclosure. The first network element is used to perform any of the above methods. In some embodiments, as shown in Figure 18, the first network element 1800 may include: a transceiver module 1801.

[0459] In some embodiments, the transceiver module 1801 is configured to receive the sensing capabilities and / or sensing information of the Non-3GPP device sent by the Non-3GPP device.

[0460] Optionally, the transceiver module 1801 is used to perform at least one of the transceiver steps performed by the first network element in any of the above methods (e.g., steps 601, 602, 1a, 2a, 1201, but not limited thereto), which will not be elaborated here.

[0461] In some embodiments, the transceiver module can be interchanged with the transceiver, the sending module, and the receiving module.

[0462] Figure 19 is a schematic diagram of the structure of the fourth network element proposed in an embodiment of this disclosure. The fourth network element is used to perform any of the above methods. In some embodiments, as shown in Figure 19, the fourth network element 1900 may include: a transceiver module 1901 and a processing module 1902.

[0463] In some embodiments, the transceiver module 1901 is configured to receive a sensing service request; wherein the sensing service request is used to request the execution of a sensing task; the processing module 1902 is configured to determine, based on the sensing capabilities and / or sensing information of at least one sensing entity stored in the second network element, a Non-3GPP device as the sensing entity to execute the sensing task; the transceiver module 1901 may also be configured to send a sensing task request to a first device; wherein the sensing task request is used to request the Non-3GPP device to execute a sensing task; the first device includes a UE or a gateway.

[0464] Optionally, the transceiver module 1901 is used to perform at least one of the transceiver steps performed by the fourth network element in any of the above methods (e.g., steps 604, 607, 705, 708, 3, 4, 6, 1301, 1303, but not limited thereto), which will not be described in detail here. The processing module 1902 is used to perform at least one of the communication steps performed by the fourth network element in any of the above methods (e.g., steps 605, 606, 706, 707, 5, 1302, but not limited thereto), which will not be described in detail here.

[0465] In some embodiments, the processing module can be interchanged with the processor and the determination module. The transceiver module can be interchanged with the transceiver, the sending module, and the receiving module.

[0466] Figure 20 is a schematic diagram of the structure of the second network element proposed in an embodiment of this disclosure. The second network element is used to perform any of the above methods. In some embodiments, as shown in Figure 20, the second network element 2000 may include: a transceiver module 2001 and a processing module 2002.

[0467] In some embodiments, the transceiver module 2001 is used to receive the sensing capabilities and / or sensing information of the Non-3GPP device; the processing module 2002 is used to store the sensing capabilities and / or sensing information of the Non-3GPP device.

[0468] Optionally, the transceiver module 2001 is used to perform at least one of the transceiver steps performed by the second network element in any of the above methods (e.g., steps 201, 602, 703, 1401, but not limited thereto), which will not be elaborated here. The processing module 1902 is used to perform at least one of the communication steps performed by the second network element in any of the above methods (e.g., steps 603, 704, 2a, 1402, but not limited thereto), which will not be elaborated here.

[0469] In some embodiments, the processing module can be interchanged with a processor, a storage module, or a memory. The transceiver module can be interchanged with a transceiver, a transmitting module, or a receiving module.

[0470] Figure 21 is a schematic diagram of the structure of the sensing device 2100 proposed in an embodiment of this disclosure. The sensing device 2100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The sensing device 2100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0471] As shown in Figure 21, the sensing device 2100 is used to perform any of the above methods. In some embodiments, the sensing device 2100 includes one or more processors 2101. The processor 2101 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the sensing device 2100 is used to perform any of the above methods. Optionally, one or more processors 2101 are used to invoke instructions to cause the sensing device 2100 to perform any of the above methods.

[0472] In some embodiments, the sensing device 2100 further includes one or more transceivers 2102. When the sensing device 2100 includes one or more transceivers 2102, the transceivers 2102 perform communication steps such as sending and / or receiving in the above method (e.g., steps 201, 202, 601, 602, 604, 607, 608, 609, 610, 701, 702, 703, 705, 708, 709, 710, 711, 0a, 0b, 1a, 1b, 2a, 2b). b) At least one of steps 3, 4, 6, 901, 902, 7, 1001, 1002, 1101, 602, 1201, 1301, 1303, and 1401 (but not limited thereto), processor 2101 performs at least one of other steps (e.g., steps 603, 605, 606, 704, 706, 707, 2a, 5, 1302, and 1402, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver device, transceiver circuit, interface circuit, and interface can be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit can be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit can be used interchangeably.

[0473] In some embodiments, the sensing device 2100 further includes one or more memories 2103 for storing data and / or instructions. Optionally, one or more processors 2101 are used to invoke instructions stored in the memories 2103 to cause the sensing device 2100 to perform any of the above methods. Optionally, all or part of the memories 2103 may also be located outside the sensing device 2100. In optional embodiments, the sensing device 2100 may include one or more interface circuits 2104. Optionally, the interface circuits 2104 are connected to the memories 2102 and can be used to receive data and / or instructions from the memories 2102 or other devices, and can be used to send data and / or instructions to the memories 2102 or other devices. For example, the interface circuits 2104 can read data and / or instructions stored in the memories 2102 and send the data and / or instructions to the processor 2101.

[0474] The sensing device 2100 described in the above embodiments may be a network device or a terminal, but the scope of the sensing device 2100 described in this disclosure is not limited thereto, and the structure of the sensing device 2100 may not be limited by FIG. 21. The sensing device may be a standalone device or may be part of a larger device. For example, the sensing device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0475] Figure 22 is a schematic diagram of the structure of the chip 2200 proposed in an embodiment of this disclosure. For cases where the sensing device 2100 can be a chip or a chip system, please refer to the schematic diagram of the chip 2200 shown in Figure 22, but it is not limited thereto.

[0476] Chip 2200 includes one or more processors 2201. Chip 2200 is used to perform any of the above methods.

[0477] In some embodiments, chip 2200 further includes one or more interface circuits 2202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 2200 further includes one or more memories 2203 for storing data and / or instructions. Optionally, all or part of the memories 2203 may be located outside of chip 2200. Optionally, the interface circuits 2202 are connected to the memories 2203, and the interface circuits 2202 can be used to receive data and / or instructions from the memories 2203 or other devices, and can be used to send data and / or instructions to the memories 2203 or other devices. For example, the interface circuits 2202 can read data and / or instructions stored in the memories 2203 and send the data and / or instructions to the processor 2201.

[0478] In some embodiments, the interface circuit 2202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps 201, 202, 601, 602, 604, 607, 608, 609, 610, 701, 702, 703, 705, 708, 709, 710, 711, 0a, 0b, 1a, 1b, 2a, 2b, 3, 4, 6, 901, 902, 7, 1001, 1002, 1101, 602, 1201, 1301, 1303, 1401, but not limited thereto). The interface circuit 2202 performing the communication steps such as sending and / or receiving in the above method refers to, for example, the interface circuit 2202 performing data and / or instruction interaction between the processor 2201, the chip 2200, the memory 2203, or the transceiver device. In some embodiments, the processor 2201 performs at least one of other steps (e.g., steps 603, 605, 606, 704, 706, 707, 2a, 5, 1302, 1402, but is not limited thereto).

[0479] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0480] This disclosure also proposes a storage medium storing instructions that, when executed on a sensing device, cause the sensing device to perform any of the methods described above. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0481] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a sensing device, cause the sensing device to perform any of the methods described above. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0482] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

A method for selecting sensing entities, applied to Non-3GPP equipment, is characterized in that... The method includes: Send the sensing capabilities and / or sensing information of the Non-3GPP device; Receive a sensing task request; wherein the sensing task request is used to request the Non-3GPP device to perform a sensing task. The perceptual entity selection method according to claim 1 is characterized in that, The transmission of the sensing capabilities and / or sensing information of the Non-3GPP device includes: Send the sensing capabilities and / or sensing information of the Non-3GPP device to the first network element, and instruct the first network element to send the sensing capabilities and / or sensing information of the Non-3GPP device to the second network element. The perceptual entity selection method according to claim 1 is characterized in that, The transmission of the sensing capabilities and / or sensing information of the Non-3GPP device includes: Send the sensing capabilities and / or sensing information of the Non-3GPP device to the first device, and instruct the first device to send the sensing capabilities and / or sensing information of the Non-3GPP device to the third network element; The first device includes a user equipment (UE) or a gateway. The perceptual entity selection method according to claim 3 is characterized in that, Before sending the sensing capabilities and / or sensing information of the Non-3GPP device to the first device, the method further includes: The first device establishes a wired or wireless connection with the Non-3GPP device; based on pre-configured URSP rules, the first device determines whether to establish a new PDU session with the third network element or reuse an existing PDU session. The method for selecting a perceptual entity according to any one of claims 1 to 4 is characterized in that, The receiving of the sensing task request includes: Receive the sensing task request sent by the first device; The sensing task request is sent to the first device after the fourth network element receives the sensing service request, determines the Non-3GPP device as the sensing entity to perform the sensing task from the at least one sensing entity stored in the second network element based on the sensing capabilities and / or sensing information of the at least one sensing entity; The perception service request is used to request the execution of the perception task; the first device includes a user equipment (UE) or a gateway; the at least one perception entity includes: the UE, gNB, or the Non-3GPP device. The method for selecting a perceptual entity according to any one of claims 1 to 5 is characterized in that, The perception task request includes at least one of the following: the device identifier of the UE bound to the Non-3GPP device, the device identifier of the Non-3GPP device, the perception task policy of the perception task, and the pre-configured URSP rule. The method for selecting a perceptual entity according to any one of claims 1 to 6 is characterized in that, The sensing capabilities and / or sensing information of the Non-3GPP device are identified by at least one of the device identifier of the Non-3GPP device and the device identifier of the UE bound to the Non-3GPP device. A method for selecting a perceived entity, applied to a first device, characterized in that: The first device includes a UE or a gateway; the method includes: Receive the sensing capabilities and / or sensing information of the Non-3GPP device sent by the Non-3GPP device; Send a sensing task request to the Non-3GPP device; wherein the sensing task request is used to request the Non-3GPP device to perform a sensing task. The perceptual entity selection method according to claim 8 is characterized in that, After receiving the sensing capabilities and / or sensing information of the Non-3GPP device sent by the Non-3GPP device, the method further includes: Send the sensing capabilities and / or sensing information of the Non-3GPP device to the third network element, and instruct the third network element to send the sensing capabilities and / or sensing information of the Non-3GPP device to the second network element. The perceptual entity selection method according to claim 9 is characterized in that, Before receiving the sensing capabilities and / or sensing information of the Non-3GPP device sent by the Non-3GPP device, the method includes: The first device establishes a wired or wireless connection with the Non-3GPP device; based on pre-configured URSP rules, the first device determines whether to establish a new PDU session with the third network element or reuse an existing PDU session. The perceptual entity selection method according to claim 9 or 10 is characterized in that, Before sending the sensing task request to the Non-3GPP device, the method further includes: Receive the sensing task request sent by the fourth network element; The sensing task request is determined by the fourth network element after receiving the sensing service request, based on the sensing capabilities and / or sensing information of at least one sensing entity stored in the second network element, and after determining that the Non-3GPP device is the sensing entity to perform the sensing task from the at least one sensing entity. The perception service request is used to perform the perception task; the at least one perception entity includes: the UE, gNB, or the Non-3GPP device. The method for selecting a perceptual entity according to any one of claims 8 to 11 is characterized in that, After sending the sensing task request to the Non-3GPP device, the method further includes: Based on the pre-configured URSP rules, send a PDU session establishment request or a PDU session modification request to the third network element; The PDU session establishment request is used to request the establishment of a new PDU session with the third network element; the PDU session modification request is used to request the third network element to modify the existing PDU session. The method for selecting a perceptual entity according to any one of claims 8 to 12 is characterized in that, The perception task request includes at least one of the following: the device identifier of the UE bound to the Non-3GPP device, the device identifier of the Non-3GPP device, the perception task policy of the perception task, and the pre-configured URSP rule. The method for selecting a perceptual entity according to any one of claims 8 to 13 is characterized in that, The sensing capabilities and / or sensing information of the Non-3GPP device are identified by at least one of the device identifier of the Non-3GPP device and the device identifier of the UE bound to the Non-3GPP device. A sensing entity selection method, applied to a third network element, is characterized in that... The method includes: Receive sensing capabilities and / or sensing information of a Non-3GPP device sent by a first device; the first device includes a UE or a gateway. The perceptual entity selection method according to claim 15 is characterized in that, Before receiving the sensing capabilities and / or sensing information of the Non-3GPP device sent by the first device, the method further includes: The first device establishes a wired or wireless connection with the Non-3GPP device; based on pre-configured URSP rules, the first device determines whether to establish a new PDU session with the third network element or reuse an existing PDU session. The perceptual entity selection method according to claim 15 or 16 is characterized in that, After receiving the sensing capabilities and / or sensing information of the Non-3GPP device sent by the first device, the method further includes: Send the sensing capabilities and / or sensing information of the Non-3GPP device to the second network element. The perceptual entity selection method according to claim 15 or 16 is characterized in that, After receiving the sensing capabilities and / or sensing information of the Non-3GPP device sent by the first device, the method further includes: Receive a PDU session establishment request or a PDU session modification request sent by the first device; The PDU session establishment request is used to request the establishment of a new PDU session with the third network element; the PDU session modification request is used to request the third network element to modify the existing PDU session. The PDU session establishment request is sent by the first device based on pre-configured URSP rules; the PDU session modification request is sent by the first device based on pre-configured URSP rules. The method for selecting a perceptual entity according to any one of claims 15 to 18 is characterized in that, The sensing capabilities and / or sensing information of the Non-3GPP device are identified by at least one of the device identifier of the Non-3GPP device and the device identifier of the UE bound to the Non-3GPP device. A sensing entity selection method, applied to a fourth network element, is characterized in that... The method includes: Receive a sensing service request; wherein the sensing service request is used to request the execution of a sensing task; Based on the sensing capabilities and / or sensing information of at least one sensing entity stored in the second network element, a Non-3GPP device is identified from the at least one sensing entity as the sensing entity performing the sensing task. A sensing task request is sent to a first device; wherein the sensing task request is used to request the Non-3GPP device to perform a sensing task; the first device includes a UE or a gateway. The method for selecting a perceptual entity according to claim 20 is characterized in that, The fourth network element includes: a perception service provider. The perceptual entity selection method according to claim 20 or 21 is characterized in that, The perception task request includes at least one of the following: the device identifier of the UE bound to the Non-3GPP device, the device identifier of the Non-3GPP device, the perception task policy of the perception task, and the pre-configured URSP rule. A sensing device, characterized in that, The sensing device is used to perform the sensing entity selection method according to any one of claims 1 to 7, any one of claims 8 to 14, any one of claims 15 to 19, and any one of claims 20 to 22. A storage medium storing instructions, characterized in that, When the instruction is executed on the sensing device, the sensing device performs the sensing entity selection method according to any one of claims 1 to 7, any one of claims 8 to 14, any one of claims 15 to 19, and any one of claims 20 to 22. A program product comprising at least one of a program and instructions, characterized in that: At least one of the program or instructions is implemented by the sensing device to implement the sensing entity selection method of any one of claims 1 to 7, any one of claims 8 to 14, any one of claims 15 to 19, and any one of claims 20 to 22.

Images