Method and communication device for sensing

Abstract

A method and a communication device for awareness are provided. The method comprises: a first network element sending a first message to an application function network element, the first message being used for requesting awareness data of a target device associated with a first communication device, the target device being a non-3GPP awareness device.

Description

Method and communication device for sensing Technical Field

[0001] The present application relates to the field of communication technology, and more particularly, to a method and a communication device for sensing. Background Art

[0002] To enrich perception methods, the integrated synaesthesia scenario is currently considering supporting perception data generated by non-3rd Generation Partnership Project (3GPP) perception devices. However, how to transmit the perception data generated by non-3GPP perception devices is an issue that needs to be addressed.

[0003] Summary of the Invention

[0004] The present application provides a method and a communication device for sensing. The following introduces various aspects of the present application.

[0005] In a first aspect, a method for perception is provided, including: a first network element sends a first message to an application function network element, wherein the first message is used to request perception data of a target device associated with a first communication device, and the target device is a non-3GPP perception device.

[0006] In a second aspect, a method for perception is provided, including: an application function network element receives a first message sent by a first network element, the first message being used to request perception data of a target device associated with a first communication device, the target device being a non-3GPP perception device.

[0007] According to a third aspect, a method for perception is provided, including: a first communication device sends a fourth message to an application function network element, wherein the fourth message includes device information of a target device associated with the first communication device, and the target device is a non-3GPP perception device.

[0008] In a fourth aspect, a communication device is provided, which is a first network element, and the communication device includes: a first communication module, used to send a first message to an application function network element, the first message being used to request perception data of a target device associated with the first communication device, and the target device being a non-3GPP perception device.

[0009] In the fifth aspect, a communication device is provided, which is an application function network element, and the communication device includes: a first communication module, used to receive a first message sent by a first network element, the first message is used to request perception data of a target device associated with the first communication device, and the target device is a non-3GPP perception device.

[0010] In the sixth aspect, a communication device is provided, which is a first communication device, and the communication device includes: a first communication module, used to send a fourth message to an application function network element, the fourth message including device information of a target device associated with the first communication device, and the target device is a non-3GPP aware device.

[0011] In the seventh aspect, a communication device is provided, comprising a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the communication device executes the method as described in any one of the first to third aspects.

[0012] In an eighth aspect, a device is provided, comprising a processor for calling a program from a memory so that the device executes a method as described in any one of the first to third aspects.

[0013] In a ninth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes a method as described in any one of the first to third aspects.

[0014] In a tenth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method as described in any one of the first to third aspects.

[0015] In the eleventh aspect, a computer program product is provided, characterized in that it includes a program, and the program enables a computer to execute the method as described in any one of the first to third aspects.

[0016] In a twelfth aspect, a computer program is provided, which enables a computer to execute the method as described in any one of the first to third aspects.

[0017] The embodiment of the present application proposes requesting the application function network element for the perception data of the non-3GPP perception device associated with the first communication device. Since the data interaction between the application function network element and the first communication device can be protected by the application layer, transmitting the non-3GPP perception data through the application function network element can improve the security of data transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] FIG1 is a diagram illustrating an example of a system architecture of a wireless communication system to which an embodiment of the present application may be applied.

[0019] FIG2 is a system architecture diagram of a fifth generation (5G) communication system.

[0020] FIG3 is an example diagram of another communication system architecture provided in an embodiment of the present application.

[0021] FIG4 is a flow chart of a method for sensing provided in accordance with an embodiment of the present application.

[0022] FIG5 is a flow chart of a method for sensing provided in another embodiment of the present application.

[0023] FIG6 is a flowchart of a method for sensing provided in another embodiment of the present application.

[0024] FIG7 is a flowchart of a method for sensing provided in another embodiment of the present application.

[0025] FIG8 is a flowchart of a method for sensing provided in another embodiment of the present application.

[0026] FIG9 is a schematic diagram of the structure of a communication device provided in one embodiment of the present application.

[0027] FIG10 is a schematic structural diagram of a communication device provided in another embodiment of the present application.

[0028] FIG11 is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.

[0029] FIG12 is a schematic diagram of a device to which an embodiment of the present application can be applied. DETAILED DESCRIPTION

[0030] The technical solution in this application will be described below with reference to the accompanying drawings.

[0031] Wireless communication system

[0032] Figure 1 is a diagram illustrating an example of the system architecture of a wireless communication system 100 to which an embodiment of the present application may be applied. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide network coverage for a specific geographical area and may communicate with the terminal device 120 located within the coverage area. The terminal device 120 may access a network (e.g., a wireless network) through the network device 110. Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

[0033] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: 5G system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0034] The terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects, and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a scheduling entity that provides sidelink signals between terminal devices in vehicle to everything (V2X) or device to device (D2D). For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through a base station.

[0035] The network device in the embodiment of the present application may be a device for communicating with a terminal device. The network device may be, for example, an access network device or a wireless access network device. For example, the network device may be a base station. The base station may broadly cover the following various names, or be replaced with the following names: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmitting point (TP), home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station may be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof.

[0036] Terminal devices can communicate with each other via sidelinks. Sidelink communication can also be called proximity services (ProSe) communication, unilateral communication, sidelink communication, or D2D communication.

[0037] 5G network system architecture and perception network elements

[0038] The 5G network system architecture is shown in Figure 2. In this system architecture, the UE establishes an access layer connection with the access node (AN) through the air interface (Uu interface), exchanges access layer messages and wireless data transmission. The UE establishes a non-access stratum (NAS) connection with the access and mobility management function (AMF) through the N1 interface, and exchanges NAS messages. In addition to managing the mobility of the UE, the AMF is also responsible for forwarding session management-related messages between the UE and the SMF. The policy control function (PCF) is responsible for formulating policies related to UE mobility management, session management, billing, etc. The user plane function (UPF) transmits data with the external data network (DN) through the N6 interface and with the AN through the N3 interface.

[0039] Current cellular networks (including 5G networks) are primarily used for wireless data transmission and communication. However, the radio electromagnetic wave signals used by cellular networks can be used not only for wireless data transmission and communication but also for environmental perception. For example, cellular network radio electromagnetic wave signals can be used for user motion or gesture recognition, respiratory monitoring, terminal device movement speed measurement, environmental imaging, weather monitoring, and more. Therefore, cellular networks can also be used to obtain sensory information.

[0040] Currently, support for perception capabilities in B5G (beyond 5G) networks is under discussion. For example, perception capabilities can be supported in 3GPP networks by adding perception network elements (or perception control network elements) and corresponding processes. Figure 3 shows an example of a network system architecture that supports perception capabilities. As shown in Figure 3, a perception network element (i.e., the sensing function (SF) in Figure 3) is added to the core network to handle perception-related operations. After the application sends a perception request to the core network of the 3GPP network, the core network can select the correct base station or auxiliary terminal device through the perception network element or AMF, and trigger the base station or auxiliary terminal device to enable the perception-related wireless measurement capability to start the measurement of perception information and generate perception results.

[0041] The main perception links or perception methods of synaesthesia integration scenarios include the following:

[0042] 1. Base station echo sensing link (single base station sensing): The base station sends a sensing signal and receives an echo signal;

[0043] 2. Inter-base station sensing link (base station-base station sensing): Base station B receives the sensing signal sent by base station A;

[0044] 3. Air interface uplink perception link (terminal device-base station uplink perception): The base station receives the perception signal sent by the terminal;

[0045] 4. Air interface downlink perception link (terminal device-base station downlink perception): The terminal device receives the perception signal sent by the base station;

[0046] 5. Terminal echo sensing link (single terminal device sensing): The terminal device sends a sensing signal and receives an echo signal; and

[0047] 6. Inter-terminal perception link (terminal device-terminal device perception): Terminal device B receives the perception signal sent by terminal device A.

[0048] At present, considering that the amount of interactive data between the terminal device and the perception network element is large, the terminal device can transmit data with the perception network element through the user plane to complete the necessary interaction of the perception service. For example, the terminal device can send perception data to the perception network element through the UPF by establishing a protocol data unit (PDU) session (which can be a special PDU session). Taking the perception network element as the SF shown in Figure 3 as an example, in some implementations, the perception network element may include SF-C (SF control plane network element) and SF-U (SF user plane network element). The terminal device can, for example, send perception data to SF-U through the UPF. Of course, SF, SF-C, and SF-U are only examples of the name of the network element. The network element may also use other names, or may be jointly established with the location management function (LMF). This embodiment of the present application does not specifically limit this. At the same time, for some perception tasks, in order to save network resources, the perception node may be allowed to perform partial processing and only transmit a small amount of data to the SF for processing through the control plane. At the same time, considering the situation that multiple terminal devices may be needed to assist in perception, terminal devices are allowed to discover and select other terminal devices through the PC5 interface, and use other terminal devices as perception nodes to complete the perception task.

[0049] In order to enrich the means of perception, it is currently considered to continue to support non-3GPP perception devices to provide perception data on the basis of 3GPP perception devices. For example, non-3GPP perception devices such as cameras, microphones, radars, gyroscopes, etc. attached to access network nodes or terminal devices can be used for auxiliary perception and provide perception data. In this scenario, how the core network (such as the network elements used for perception services in the core network) obtains the perception data generated by such non-3GPP perception devices is a problem that needs to be solved. In response to this problem, one possible solution is for the core network to obtain non-3GPP perception data directly from the terminal device or access network device. However, this data acquisition method is unsafe (because the data interaction between the core network and the access network device or terminal device does not require user permission) and may cause user privacy leakage. Therefore, this method is difficult to commercialize.

[0050] Therefore, how to safely transmit non-3GPP perception data is a concern of the embodiments of the present application. In response to the above problems, the embodiments of the present application propose that the terminal device authorize and register the non-3GPP perception device at the application layer, and then interact with the core network through the application function (AF) network element, so as to selectively and reliably send the perception data collected by the non-3GPP perception device to the core network to complete the perception task. The processing flow and method of non-3GPP perception data provided by the embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0051] Referring to FIG. 4 , in step S410 , the first network element sends a first message to the AF.

[0052] The first network element may be a network element in the core network for sensing services. For example, the first network element may be the SF mentioned above. Alternatively, the first network element may be the LMF (i.e., the SF and the LMF are provided together).

[0053] The first message is used to request perception data of a target device associated with the first communication device. The first communication device may be a 3GPP-aware device. For example, the first communication device may be a terminal device or an access network device. The target device associated with the first communication device is a non-3GPP-aware device. For example, the target device includes one or more sensors attached to the first communication device, such as a camera, a microphone, a radar, or a gyroscope.

[0054] In some implementations, the first message may include one or more of the following:

[0055] identification information of the first communication device;

[0056] Device information of the target device;

[0057] Perceive time information.

[0058] For example, the first message may include identification information of the first communication device. The identification information of the first communication device may be a common UE ID, such as a user permanent identifier (SUPI) or a generic public subscription identifier (GPSI). Alternatively, the identification information of the first communication device may be an Internet Protocol (IP) address or a Media Access Control (MAC) address of the first communication device.

[0059] For another example, the first message may include device information of the target device. The device information of the target device may include identification information of the target device and / or type information of the target device. The identification information of the target device (also referred to as identification information of the target device) may include one or more of the following information: the manufacturer of the target device, MAC address, device serial number, etc. The type information of the target device may, for example, indicate that the target device is a camera, gyroscope, or microphone.

[0060] For another example, the first message may include sensing time information. The sensing time information is used to indicate the execution time of the sensing task, so that the AF returns sensing data within the corresponding time to the first network element.

[0061] After the first network element sends the first message to the AF, in some implementations, the first network element may receive the perception data of the target device sent by the AF. For example, after receiving the first message, the AF may collect non-3GPP perception data from the first communication device via the application layer (or application server). The AF may then feed back the non-3GPP perception data to the SF via the control plane or the user plane.

[0062] Before the first network element sends the first message to the AF, the first network element may first determine the AF, or determine the identification information of the AF. The identification information of the AF may include one or more of the following: the ID of the AF, the ID of the application, the address information of the AF, and the fully qualified domain name (FQDN) of the AF. There are multiple ways for the first network element to determine the AF or the identification information of the AF. Two possible implementations are given below in combination with Example 1 and Example 2.

[0063] Example 1: Querying AF through the second network element in the core network

[0064] Referring to Figure 5, in step S530, the first network element sends a second message to the second network element in the core network. The second message is used to determine (or to query) the AF (the AF corresponding to the first communication device). The second network element can be, for example, a network repository function (NRF) or a unified data repository (UDR). The second network element can record the correspondence between the first communication device and the AF. For example, the second network element can record the correspondence between the identification information of the first communication device and the identification information of the AF.

[0065] The second message may include identification information of the first communication device. The identification information of the first communication device may be a common UE ID, such as SUPI or GPSI. Alternatively, the identification information of the first communication device may be an IP address / MAC address of the first communication device.

[0066] The second message may include first indication information. The first indication information is used to indicate a non-3GPP perception mode. It should be understood that the first indication information may explicitly indicate a non-3GPP perception mode, or may implicitly indicate a non-3GPP perception mode. For example, the first indication information includes a first value and a second value. If the value of the first indication information is the first value, the first indication information is used to indicate a non-3GPP perception mode; if the value of the first indication information is the second value, the first indication information is used to indicate a 3GPP perception mode. For another example, the first indication information may be identification information and / or type information of the target device. That is, the first network element implicitly indicates a non-3GPP perception mode by sending the identification information and / or type information of the target device.

[0067] Continuing with FIG. 5 , in some implementations, FIG. 5 may further include step S540, where the first network element receives a feedback message regarding the second message from the second network element. The feedback message includes identification information of the AF. The identification information of the AF may include one or more of the following: an AF ID, an application ID, address information of the AF, and an FQDN of the AF.

[0068] Furthermore, the feedback message may also include one or more of the following: identification information of the first communication device and device information of the target device. The identification information of the first communication device may be a common UE ID, such as SUPI or GPSI. Alternatively, the identification information of the first communication device may be the IP address / MAC address of the first communication device, etc. The device information of the target device may include identification information of the target device and / or type information of the target device. The identification information of the target device (also referred to as identification information of the target device) may include one or more of the following information: the manufacturer of the target device, the MAC address, the device number, etc. The type information of the target device may, for example, indicate that the target device is a camera, a gyroscope, or a microphone.

[0069] After determining the AF (AF identification information), the first network element proceeds to step S550 and sends a first message to the AF (sending the first message to the AF based on the AF identification information). Step S550 in Figure 5 corresponds to step S410 in Figure 4. For details, please refer to the relevant introduction of step S410 and will not be described in detail here.

[0070] It should be understood that the first network element and the second network element can interact directly or through an intermediate network element. For example, the first network element and the second network element can interact through one or more network elements of AMF, GMLC, and NEF.

[0071] Optionally, before step S530, the first communication device may first execute step S510, that is, send a fourth message to the AF.

[0072] In some implementations, the fourth message includes one or more of the following: identification information of the first communication device, and device information of the target device. The identification information of the first communication device may be a common UE ID, such as SUPI or GPSI. Alternatively, the identification information of the first communication device may be the IP address / MAC address of the first communication device, etc. The device information of the target device may include identification information of the target device and / or type information of the target device. The identification information of the target device (also referred to as identification information of the target device) may include one or more of the following information: the manufacturer of the target device, the MAC address, the device number, etc. The type information of the target device may, for example, indicate that the target device is a camera, a gyroscope, or a microphone.

[0073] In some implementations, the fourth message is used to register the device information of the target device with the AF (or application server). In other words, the first terminal device registers the device information of the non-3GPP-aware device associated with the first terminal device with the AF through the fourth message, thereby preparing for the subsequent acquisition of non-3GPP-aware data.

[0074] After receiving the fourth message, the AF may store one or more of the following information to the second network element of the core network: identification information of the first communication device, device information of the target device, and identification information of the AF. The identification information of the first communication device may be an ordinary UE ID, such as SUPI or GPSI. Alternatively, the identification information of the first communication device may be the IP address / MAC address of the first communication device, etc. The device information of the target device may include the identification information of the target device and / or the type information of the target device. The identification information of the target device (also referred to as the identification information of the target device) may include one or more of the following information: the manufacturer of the target device, the MAC address, the device number, etc. The type information of the target device may, for example, indicate that the target device is a camera, a gyroscope, or a microphone, etc. The identification information of the AF may include one or more of the following: the ID of the AF, the ID of the application, the address information of the AF, and the FQDN of the AF.

[0075] Example 2: Obtaining AF through the first communication device

[0076] 6 , in step S620 , the first communication device sends a third message to the first network element.

[0077] In some implementations, the third message may be used to register the non-3GPP awareness capability of the first communication device with the first network element.

[0078] In some implementations, the third message may include one or more of the following: identification information of the first communication device, device information of the target device, and identification information of the AF. The identification information of the first communication device may be a common UE ID, such as SUPI or GPSI. Alternatively, the identification information of the first communication device may be the IP address / MAC address of the first communication device, etc. The device information of the target device may include the identification information of the target device and / or the type information of the target device. The identification information of the target device (also referred to as the identification information of the target device) may include one or more of the following information: the manufacturer of the target device, the MAC address, the device number, etc. The type information of the target device may, for example, indicate that the target device is a camera, a gyroscope, or a microphone, etc. The identification information of the AF may include one or more of the following: the ID of the AF, the ID of the application, the address information of the AF, and the FQDN of the AF.

[0079] After determining the AF (AF identification information), the first network element proceeds to step S630 and sends a first message to the AF (sending the first message to the AF based on the AF identification information). Step S630 corresponds to step S410 in Figure 4. For details, please refer to the relevant introduction of step S410 and will not be described in detail here.

[0080] Optionally, before step S630, the first communication device may first execute step S610, ie, send a fourth message to the AF.

[0081] In some implementations, the fourth message includes one or more of the following: identification information of the first communication device, and device information of the target device. The identification information of the first communication device may be a common UE ID, such as SUPI or GPSI. Alternatively, the identification information of the first communication device may be the IP address / MAC address of the first communication device, etc. The device information of the target device may include identification information of the target device and / or type information of the target device. The identification information of the target device (also referred to as identification information of the target device) may include one or more of the following information: the manufacturer of the target device, the MAC address, the device number, etc. The type information of the target device may, for example, indicate that the target device is a camera, a gyroscope, or a microphone.

[0082] In some implementations, the fourth message is used to register the device information of the target device with the AF (or application server). In other words, the first terminal device registers the device information of the non-3GPP-aware device associated with the first terminal device with the AF through the fourth message, thereby preparing for the subsequent acquisition of non-3GPP-aware data.

[0083] The embodiments of the present application are described in more detail below with reference to specific examples. The SF in the examples shown in Figures 7 to 8 corresponds to the first network element mentioned above, the NRF / UDR corresponds to the second network element mentioned above, and the UE corresponds to the first terminal device mentioned above. It should be noted that the examples of Figures 7 to 8 are only intended to help those skilled in the art understand the embodiments of the present application, and are not intended to limit the embodiments of the present application to the specific numerical values ​​or specific scenarios illustrated. Those skilled in the art can obviously make various equivalent modifications or changes based on the examples of Figures 7 to 8, and such modifications or changes also fall within the scope of the embodiments of the present application.

[0084] Example 1:

[0085] In Example 1, the AF registers and manages non-3GPP sensing devices through the NRF / UDR. The UE registers its ID and the information of the associated non-3GPP sensing devices to the application server through the application layer. The application server stores the relevant information on the NRF / UDR through the AF. When the SF decides to use non-3GPP sensing data, it can query the NRF / UDR to learn how to interact with the AF, and then request the relevant non-3GPP sensing data from the AF. Example 2 is described in detail below in conjunction with Figure 7.

[0086] Referring to Figure 7 , in step S702, the UE registers its associated non-3GPP-aware device information with the application server through the application layer. This registration message may include the UE ID (which may be SUPI, GPSI, UE IP / MAC address information, etc.) and the type of the non-3GPP-aware device (such as a camera, gyroscope, microphone, etc.). Optionally, the registration message may also include identification information of the non-3GPP-aware device, such as the manufacturer, MAC address, or device number.

[0087] In step S704, after receiving the UE's non-3GPP-aware device information, the application server stores relevant information, such as the UE's ID information and the device information of the non-3GPP-aware device, to the NRF or UDR via the AF. The device information of the non-3GPP-aware device may include the device type and identification information of the non-3GPP-aware device. In addition, the AF's identification information, such as the AF's ID, application ID, AF's address information, and the AF's FQDN, may also be stored to the NRF or UDR. The AF may store the above information to the NRF / UDR via an intermediate network element such as the NEF.

[0088] In step S706, the SF decides to use non-3GPP sensing data for sensing when receiving a sensing request or when performing a sensing service.

[0089] In step S708, the SF queries the NRF / UDR (i.e., the network function (NF) query in Figure 7) based on the information of the currently perceived UE. The query message may include the UE ID information and the indication information of the non-3GPP perception mode (the indication information may be displayed or implicitly indicated, such as the device type information of the non-3GPP perception device). The SF may query the NRF / UDR through network elements such as AMF / GMLC / NEF.

[0090] In step S710, the NRF / UDR feeds back the corresponding AF information (such as AF identification information) to the SF. In addition, the NRF / UDR may also include the UE ID information and the device information of the non-3GPP sensing device associated with the UE. This information may be sent to the SF via network elements such as the AMF / GMLC / NEF.

[0091] In step S712, the SF requests the corresponding AF for the perception data of the non-3GPP perception device associated with the UE based on the AF information. The request message may include, for example, the UE ID information, the device information of the designated non-3GPP perception device, and the perception time information.

[0092] In step S714, the AF collects non-3GPP perception data from the UE through the application layer.

[0093] In step S716, the AF feeds back the non-3GPP perception data to the SF via the control plane or the user plane. For example, the AF may establish a user plane connection with the SF in step S712 and transmit the non-3GPP perception data via the user plane connection.

[0094] Example 1: AF stores relevant information for non-3GPP perception in NRF / UDR. When non-3GPP perception is required, SF requests non-3GPP perception data from AF, thereby adding application layer protection for the transmission of non-3GPP perception data to the core network, which can better protect user privacy.

[0095] Example 2:

[0096] In Example 2, the AF's identification information is provided by the UE to the SF. For example, the UE obtains the corresponding AF's identification information when registering its non-3GPP awareness device information with the application server. Subsequently, when the UE interacts with the SF, it sends the AF's identification information and its own non-3GPP awareness capability information to the SF. When the SF decides to use non-3GPP awareness data, it learns how to interact with the AF based on the AF's identification information and then requests the relevant non-3GPP awareness data from the AF. Example 2 is described in detail below in conjunction with Figure 8.

[0097] Referring to Figure 8 , in step S802, the UE registers its associated non-3GPP-aware device information with the application server through the application layer. This registration message may include the UE ID (which may be SUPI, GPSI, UE IP / MAC address information, etc.) and the type of the non-3GPP-aware device (such as a camera, gyroscope, microphone, etc.). Optionally, the registration message may also include identification information of the non-3GPP-aware device, such as the manufacturer, MAC address, or device number.

[0098] In step S804, after establishing a connection with the SF, the UE registers its non-3GPP awareness capability information with the SF. This non-3GPP awareness capability information includes the UE's ID information and device information of non-3GPP-aware devices. The device information of non-3GPP-aware devices may include device type information, device identification information, etc. In addition, the UE may also send the AF's identification information to the SF, such as the AF's ID, application ID, AF address information, and AF's Full Qualified Domain Name (FQDN).

[0099] In step S806, the SF decides to use non-3GPP sensing data for sensing when receiving a sensing request or when performing a sensing service.

[0100] In step S808, the SF requests the corresponding AF for the perception data of the non-3GPP perception device associated with the UE based on the AF's identification information. The request message may include, for example, the UE's ID information and the device information of the designated non-3GPP perception device. In addition, the request message may also include perception time information.

[0101] In step S810 , the AF collects non-3GPP perception data from the UE via the application layer (possibly via an application server).

[0102] In step S812, the AF feeds back the non-3GPP perception data to the SF via the control plane or the user plane. For example, the AF may establish a user plane connection with the SF in step S808 and transmit the non-3GPP perception data via the user plane connection.

[0103] Compared to Example 1, Example 2 allows the UE to directly register non-3GPP sensing capability information with the SF, which is more convenient for core network management and more timely. In addition, non-3GPP sensing data is obtained through the AF, which can protect the privacy of sensitive data.

[0104] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 8 . The device embodiment of the present application is described in detail below in conjunction with Figures 9 to 12 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0105] FIG9 is a schematic diagram of the structure of a communication device provided by an embodiment of the present application. The communication device 900 in FIG9 may be the first network element mentioned above. The communication device 900 may include a first communication module 910.

[0106] The first communication module 910 is configured to send a first message to the application function network element, wherein the first message is used to request perception data of a target device associated with the first communication device, wherein the target device is a non-3GPP perception device.

[0107] In some implementations, the first message includes one or more of the following:

[0108] identification information of the first communication device;

[0109] Device information of the target device;

[0110] Perceive time information.

[0111] In some implementations, the device information includes one or more of the following:

[0112] identification information of the target device;

[0113] Type information of the target device.

[0114] In some implementations, the communication device further includes:

[0115] The second communication module is used to send a second message to a second network element in the core network before the first network element sends the first message to the application function network element, where the second message is used to determine the application function network element.

[0116] In some implementations, the second message includes one or more of the following:

[0117] identification information of the first communication device;

[0118] The first indication information is used to indicate a non-3GPP perception mode.

[0119] In some implementations, the communication device further includes:

[0120] The third communication module is configured to receive a feedback message of the second message from the second network element, where the feedback message includes one or more of the following:

[0121] identification information of the first communication device;

[0122] Device information of the target device;

[0123] Identification information of the application function network element.

[0124] In some implementations, the second network element is an NRF or a UDR.

[0125] In some implementations, the communication device 900 further includes:

[0126] The fourth communication module is configured to receive a third message sent by the first communication device before the first network element sends the first message to the application function network element, where the third message includes one or more of the following:

[0127] identification information of the first communication device;

[0128] Device information of the target device;

[0129] Identification information of the application function network element.

[0130] In some implementations, the third message is used to register the non-3GPP awareness capability of the first communication device with the first network element.

[0131] In some implementations, the communication device 900 further includes:

[0132] The fifth communication module is used to receive the perception data of the target device sent by the application function network element.

[0133] In some implementations, the first communication device is a terminal device or an access network device.

[0134] In some implementations, the first network element is a network element in a core network used for sensing services.

[0135] Figure 10 is a schematic diagram of the structure of a communication device provided in another embodiment of the present application. The communication device 1000 in Figure 10 may be the application function network element (AF) mentioned above. The communication device 1000 may include a first communication module 1010. The first communication module 1010 is used to receive a first message sent by a first network element. The first message is used to request perception data of a target device associated with the first communication device, where the target device is a non-3GPP perception device.

[0136] In some implementations, the first message includes one or more of the following:

[0137] identification information of the first communication device;

[0138] Device information of the target device;

[0139] Perceive time information.

[0140] In some implementations, the device information includes one or more of the following:

[0141] identification information of the target device;

[0142] Type information of the target device.

[0143] In some implementations, the communication device 1000 further includes:

[0144] The second communication module is configured to receive a fourth message sent by the first communication device before the application function network element receives the first message sent by the first network element, where the fourth message includes one or more of the following:

[0145] identification information of the first communication device;

[0146] The device information of the target device.

[0147] In some implementations, the fourth message is used to register device information of the target device with the application function network element.

[0148] In some implementations, the communication device 1000 further includes:

[0149] The third communication module is configured to store one or more of the following information to the second network element of the core network:

[0150] identification information of the first communication device;

[0151] Device information of the target device;

[0152] Identification information of the application function network element.

[0153] In some implementations, the second network element is an NRF or a UDR.

[0154] In some implementations, the communication device 1000 further includes:

[0155] The fourth communication module is used to send the perception data of the target device to the first network element.

[0156] In some implementations, the first communication device is a terminal device or an access network device.

[0157] In some implementations, the first network element is a network element in a core network used for sensing services.

[0158] Figure 11 is a schematic diagram of the structure of a communication device provided in another embodiment of the present application. Communication device 1100 in Figure 11 may be the first communication device mentioned above. Communication device 1100 may include a first communication module 1110. First communication module 1110 is configured to send a fourth message to an application function network element, the fourth message including device information of a target device associated with the first communication device, the target device being a non-3GPP-aware device.

[0159] In some implementations, the device information includes one or more of the following:

[0160] identification information of the target device;

[0161] Type information of the target device.

[0162] In some implementations, the fourth message also includes identification information of the first communication device.

[0163] In some implementations, the fourth message is used to register device information of the target device with the application function network element.

[0164] In some implementations, the communication device 1100 further includes:

[0165] The second communication module is configured to send a third message to the first network element in the core network, where the third message includes one or more of the following:

[0166] identification information of the first communication device;

[0167] Device information of the target device;

[0168] Identification information of the application function network element.

[0169] In some implementations, the third message is used to register the non-3GPP awareness capability of the first communication device with the first network element.

[0170] In some implementations, the first network element is a network element for sensing services.

[0171] In some implementations, the communication device 1100 further includes:

[0172] The third communication module is used to send the perception data of the target device to the application function network element.

[0173] In some implementations, the first communication device is a terminal device or an access network device.

[0174] Figure 12 is a schematic block diagram of a communication device to which embodiments of the present application may be applied. Dashed lines in Figure 12 indicate that the unit or module is optional. Device 1200 may be used to implement the method described in the above method embodiment. Device 1200 may be a chip, a terminal device, or a network device.

[0175] The device 1200 may include one or more processors 1210. The processor 1210 may support the device 1200 to implement the method described in the above method embodiment. The processor 1210 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0176] The apparatus 1200 may further include one or more memories 1220. The memories 1220 store programs that can be executed by the processor 1210, causing the processor 1210 to perform the methods described in the above method embodiments. The memories 1220 may be independent of the processor 1210 or integrated into the processor 1210.

[0177] The apparatus 1200 may further include a transceiver 1230. The processor 1210 may communicate with other devices or chips via the transceiver 1230. For example, the processor 1210 may transmit and receive data with other devices or chips via the transceiver 1230.

[0178] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the first network element, application function network element, or first communication device provided in the present application, and the program causes a computer to execute the method performed by the first network element, application function network element, or first communication device in each embodiment of the present application.

[0179] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the first network element, application function network element, or first communication device provided in the embodiments of the present application, and the program causes a computer to execute the method performed by the first network element, application function network element, or first communication device in various embodiments of the present application.

[0180] The present application also provides a computer program. This computer program can be applied to the first network element, application function network element, or first communication device provided in the present application, and the computer program causes a computer to execute the method performed by the first network element, application function network element, or first communication device in each embodiment of the present application.

[0181] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0182] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0183] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0184] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0185] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0186] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0187] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0188] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0189] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0190] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0191] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0192] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0193] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for sensing, characterized in that, it includes: A first network element sends a first message to an application function network element, where the first message is used to request sensing data of a target device associated with a first communication device, and the target device is a non-3GPP (Third Generation Partnership Project) sensing device.

2. The method according to claim 1, characterized in that, the first message includes one or more of the following: identification information of the first communication device; device information of the target device; sensing time information.

3. The method according to claim 2, characterized in that, the device information includes one or more of the following: identification information of the target device; type information of the target device.

4. The method according to any one of claims 1 to 3, characterized in that, before the first network element sends the first message to the application function network element, the method further includes: the first network element sends a second message to a second network element in the core network, and the second message is used to determine the application function network element.

5. The method according to claim 4, characterized in that, the second message includes one or more of the following: identification information of the first communication device; a first indication information for indicating a non-3GPP sensing method.

6. The method according to claim 4 or 5, characterized in that, the method further includes: the first network element receives a feedback message of the second message from the second network element, and the feedback message includes one or more of the following: identification information of the first communication device; device information of the target device; identification information of the application function network element.

7. The method according to any one of claims 4 to 6, characterized in that, the second network element is a Network Repository Function (NRF) or a Unified Data Repository (UDR).

8. The method according to any one of claims 1 to 3, characterized in that, before the first network element sends the first message to the application function network element, the method further includes: the first network element receives a third message sent by the first communication device, and the third message includes one or more of the following: identification information of the first communication device; device information of the target device; identification information of the application function network element.

9. The method according to claim 8, characterized in that, the third message is used to register the non-3GPP sensing capability of the first communication device with the first network element.

10. The method according to any one of claims 1 to 9, characterized in that, the method further includes: the first network element receives the sensing data of the target device sent by the application function network element.

11. The method according to any one of claims 1 to 10, characterized in that, the first communication device is a terminal device or an access network device.

12. The method according to any one of claims 1 to 11, characterized in that, the first network element is a network element for sensing services in the core network.

13. A method for sensing, characterized in that, it includes: The application function network element receives a first message sent by a first network element, where the first message is used to request the sensing data of a target device associated with a first communication device, and the target device is a non-3rd Generation Partnership Project (3GPP) sensing device.

14. The method according to claim 13, wherein, the first message includes one or more of the following: the identification information of the first communication device; the device information of the target device; the sensing time information.

15. The method according to claim 14, wherein, the device information includes one or more of the following: the identification information of the target device; the type information of the target device.

16. The method according to any one of claims 13 to 15, wherein, before the application function network element receives the first message sent by the first network element, the method further includes: the application function network element receives a fourth message sent by the first communication device, and the fourth message includes one or more of the following: types: the identification information of the first communication device; the device information of the target device.

17. The method according to claim 16, wherein, the fourth message is used to register the device information of the target device with the application function network element.

18. The method according to claim 16 or 17, wherein, the method further includes: the application function network element stores one or more of the following information in a second network element of the core network: the identification information of the first communication device; the device information of the target device; the identification information of the application function network element.

19. The method according to claim 18, wherein, the second network element is a Network Repository Function (NRF) or a Unified Data Repository (UDR).

20. The method according to any one of claims 13 to 19, wherein, the method further includes: the application function network element sends the sensing data of the target device to the first network element.

21. The method according to any one of claims 13 to 20, wherein, the first communication device is a terminal device or an access network device.

22. The method according to any one of claims 13 to 21, wherein, the first network element is a network element for sensing services in the core network.

23. A method for sensing, wherein, it includes: a first communication device sends a fourth message to an application function network element, and the fourth message contains the device information of a target device associated with the first communication device, and the target device is a non-3GPP sensing device.

24. The method according to claim 23, wherein, the device information includes one or more of the following: the identification information of the target device; the type information of the target device.

25. The method according to claim 23 or 24, wherein, the fourth message further includes the identification information of the first communication device.

26. The method according to any one of claims 23 to 25, wherein, the fourth message is used to register the device information of the target device with the application function network element.

27. The method according to any one of claims 23 to 26, wherein, the method further comprises: the first communication device sending a third message to a first network element in the core network, the third message comprising one or more of the following: identification information of the first communication device; device information of the target device; identification information of the application function network element.

28. The method according to claim 27, wherein, the third message is used to register the non-3GPP awareness capability of the first communication device with the first network element.

29. The method according to claim 27 or 28, wherein, the first network element is a network element for awareness services.

30. The method according to any one of claims 23 to 29, wherein, the method further comprises: the first communication device sending the awareness data of the target device to the application function network element.

31. The method according to any one of claims 23 to 30, wherein, the first communication device is a terminal device or an access network device.

32. A communication device, wherein, the communication device is a first network element, and the communication device comprises: a first communication module, configured to send a first message to an application function network element, the first message being used to request awareness data of a target device associated with a first communication device, the target device being a non-3rd Generation Partnership Project (3GPP) awareness device.

33. The communication device according to claim 32, wherein, the first message comprises one or more of the following: identification information of the first communication device; device information of the target device; awareness time information.

34. The communication device according to claim 33, wherein, the device information comprises one or more of the following: identification information of the target device; type information of the target device.

35. The communication device according to any one of claims 32 to 34, wherein, the communication device further comprises: a second communication module, configured to send a second message to a second network element in the core network before the first network element sends the first message to the application function network element, the second message being used to determine the application function network element.

36. The communication device according to claim 35, wherein, the second message comprises one or more of the following: identification information of the first communication device; a first indication information, configured to indicate a non-3GPP awareness mode.

37. The communication device according to claim 35 or 36, wherein, the communication device further comprises: a third communication module, configured to receive a feedback message of the second message from the second network element, the feedback message comprising one or more of the following: identification information of the first communication device; device information of the target device; identification information of the application function network element.

38. The communication device according to any one of claims 35 to 37, wherein, the second network element is a Network Repository Function (NRF) or a Unified Data Repository (UDR).

39. The communication device according to any one of claims 32 to 34, ​ It is characterized in that the communication device further comprises: a fourth communication module, configured to receive a third message sent by the first communication device before the first network element sends a first message to an application function network element, where the third message includes one or more of the following: identification information of the first communication device; device information of the target device; identification information of the application function network element.

40. The communication device according to claim 39, it is characterized in that the third message is used to register the non-3GPP awareness capability of the first communication device with the first network element.

41. The communication device according to any one of claims 32 to 40, it is characterized in that the communication device further comprises: a fifth communication module, configured to receive the awareness data of the target device sent by the application function network element.

42. The communication device according to any one of claims 32 to 41, it is characterized in that the first communication device is a terminal device or an access network device.

43. The communication device according to any one of claims 32 to 42, it is characterized in that the first network element is a network element for awareness services in the core network.

44. A communication device, it is characterized in that the communication device is an application function network element, and the communication device comprises: a first communication module, configured to receive a first message sent by a first network element, where the first message is used to request the awareness data of a target device associated with a first communication device, and the target device is a non-Third Generation Partnership Project (3GPP) awareness device.

45. The communication device according to claim 44, it is characterized in that the first message includes one or more of the following: identification information of the first communication device; device information of the target device; awareness time information.

46. The communication device according to claim 45, it is characterized in that the device information includes one or more of the following: identification information of the target device; type information of the target device.

47. The communication device according to any one of claims 44 to 46, it is characterized in that the communication device further comprises: a second communication module, configured to receive a fourth message sent by the first communication device before the application function network element receives the first message sent by the first network element, where the fourth message includes one or more of the following: identification information of the first communication device; device information of the target device.

48. The communication device according to claim 47, it is characterized in that the fourth message is used to register the device information of the target device with the application function network element.

49. The communication device according to claim 47 or 48, it is characterized in that the communication device further comprises: a third communication module, configured to store one or more of the following information in a second network element of the core network: identification information of the first communication device; device information of the target device; identification information of the application function network element.

50. The communication device according to claim 49, it is characterized in that the second network element is a Network Repository Function (NRF) or a Unified Data Repository (UDR).

51. The communication device according to any one of claims 44 to 50, characterized in that, the communication device further comprises: a fourth communication module, configured to send the sensing data of the target device to the first network element.

52. The communication device according to any one of claims 44 to 51, characterized in that, the first communication device is a terminal device or an access network device.

53. The communication device according to any one of claims 44 to 52, characterized in that, the first network element is a network element for sensing services in the core network.

54. A communication device, characterized in that, the communication device is a first communication device, and the communication device comprises: a first communication module, configured to send a fourth message to an application function network element, the fourth message comprising device information of a target device associated with the first communication device, and the target device being a non-3rd Generation Partnership Project (3GPP) sensing device.

55. The communication device according to claim 54, characterized in that, the device information includes one or more of the following: identification information of the target device; type information of the target device.

56. The communication device according to claim 54 or 55, characterized in that, the fourth message further includes identification information of the first communication device.

57. The communication device according to any one of claims 54 to 56, characterized in that, the fourth message is used to register the device information of the target device with the application function network element.

58. The communication device according to any one of claims 54 to 57, characterized in that, the communication device further comprises: a second communication module, configured to send a third message to a first network element in the core network, the third message including one or more of the following: identification information of the first communication device; device information of the target device; identification information of the application function network element.

59. The communication device according to claim 58, characterized in that, the third message is used to register the non-3GPP sensing capability of the first communication device with the first network element.

60. The communication device according to claim 58 or 59, characterized in that, the first network element is a network element for sensing services.

61. The communication device according to any one of claims 54 to 60, characterized in that, the communication device further comprises: a third communication module, configured to send the sensing data of the target device to the application function network element.

62. The communication device according to any one of claims 54 to 61, characterized in that, the first communication device is a terminal device or an access network device.

63. A communication device, characterized in that, comprising a transceiver, a memory and a processor, the memory is configured to store a program, and the processor is configured to call the program in the memory and control the transceiver to receive or send signals, so that the communication device executes the method according to any one of claims 1 to 12, 13 to 22 or 23 - 31.

64. A device, characterized in that, comprising a processor for invoking a program from a memory to cause the device to execute the method according to any one of claims 1 to 12, 13 to 22 or 23 - 31.

65. A chip, characterized in that it comprises a processor for invoking a program from a memory, such that a device installed with the chip executes the method according to any one of claims 1 to 12, 13 to 22 or 23 - 31.

66. A computer - readable storage medium, characterized in that a program is stored thereon, and the program causes a computer to execute the method according to any one of claims 1 to 12, 13 to 22 or 23 - 31.

67. A computer program product, characterized in that it comprises a program, and the program causes a computer to execute the method according to any one of claims 1 to 12, 13 to 22 or 23 - 31.

68. A computer program, characterized in that the computer program causes a computer to execute the method according to any one of claims 1 to 12, 13 to 22 or 23 - 31.

Images