Communication method and communication device
Patent Information
- Application Number
- CN202380096227.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-03-28
- Publication Date
- 2025-11-21
AI Technical Summary
In the sidelink, the sensing task of the target user equipment needs to be assisted by other user equipment, but there is currently a lack of clear methods to achieve this auxiliary sensing task.
The first terminal device sends request information to the second terminal device to use it as another user device that performs the sensing task, and the first network element instructs the terminal device to discover and connect to other user devices that can perform the sensing task, and establishes a connection with the network. connection.
It realizes the assistance of other user equipment in completing sensing tasks in the side link, ensuring the effective execution of sensing tasks and network connection, and solving the technical problems of sensing task execution and connection establishment.
Smart Images

Figure CN121002986A_ABST
Abstract
Description
Communication method and communication device Technical Field
[0001] The present application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Art
[0002] In some communication systems, when performing a sensing task for a target user equipment (UE) in a sidelink (SL), other UEs may be assisted. However, it is currently unclear how to implement the sensing task with the assistance of other UEs.
[0003] Summary of the Invention
[0004] The embodiments of the present application provide a communication method and a communication device. The following describes various aspects of the embodiments of the present application.
[0005] In a first aspect, a communication method is provided, including: a first terminal device sends first information to a second terminal device, where the first information is used to request the second terminal device to serve as another user equipment UE that performs a first perception task.
[0006] In a second aspect, a communication method is provided, including: a second terminal device receives first information sent by a first terminal device, where the first information is used to request the second terminal device to serve as another user equipment UE to perform a first perception task.
[0007] According to a third aspect, a communication method is provided, including: a first network element sends second information to a first terminal device, wherein the second information is used to instruct the first terminal device to discover other user equipment UEs that can perform a first perception task.
[0008] In a fourth aspect, a communication device is provided, including: a sending unit, configured to send first information to a second terminal device, wherein the first information is used to request the second terminal device to serve as another user equipment UE to perform a first perception task.
[0009] In a fifth aspect, a communication device is provided, including: a receiving unit for receiving first information sent by a first terminal device, wherein the first information is used to request the device to act as another user equipment UE to perform a first perception task.
[0010] In a sixth aspect, a communication device is provided, including: a sending unit, used to send second information to a first terminal device, wherein the second information is used to instruct the first terminal device to discover other user equipment UE that can perform the first perception task.
[0011] In the seventh aspect, a communication device is provided, comprising a memory, a transceiver and a processor, wherein the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method described in any one of the first to third aspects.
[0012] In an eighth aspect, a communication device is provided, comprising a processor for calling a program from a memory so that the communication device executes the method 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 the method 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 described in any one of the first to third aspects.
[0015] In an eleventh aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method according to any one of the first to third aspects.
[0016] In a twelfth aspect, a computer program is provided, wherein the computer program enables a computer to execute the method described in any one of the first to third aspects.
[0017] In an embodiment of the present application, the first terminal device sends the first information to the second terminal device, which helps to use the second terminal device as another UE for the first perception task, thereby helping to implement the perception task with the assistance of the second terminal device. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] FIG1 is an example diagram of a wireless communication system used in an embodiment of the present application.
[0019] Figure 2 is a schematic diagram of the 5G system architecture.
[0020] FIG3 is a schematic flowchart of UE-level awareness in one embodiment.
[0021] FIG4 is a schematic diagram of a sidelink UE discovery selection model in one embodiment.
[0022] FIG5 is a schematic diagram of a sidelink UE discovery selection model in another embodiment.
[0023] FIG6 is a schematic flowchart of a communication method provided in one embodiment of the present application.
[0024] FIG7 is a schematic flowchart of a communication method provided in another embodiment of the present application.
[0025] FIG8 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.
[0026] FIG9 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.
[0027] FIG10 is a schematic structural diagram of a communication device provided in one embodiment of the present application.
[0028] FIG11 is a schematic structural diagram of a communication device provided in another embodiment of the present application.
[0029] FIG12 is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.
[0030] FIG13 is a schematic structural diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0031] The technical solution in this application will be described below with reference to the accompanying drawings.
[0032] FIG1 illustrates a wireless communication system 100 used in an embodiment of the present application. The wireless communication system 100 may include a network device 110 and a user equipment (UE) 120. The network device 110 may communicate with the UE 120. The network device 110 may provide communication coverage for a specific geographic area and may communicate with the UE 120 within the coverage area. The UE 120 may access a network (e.g., a wireless network) through the network device 110.
[0033] Figure 1 exemplarily shows a network device and two UEs. Optionally, the wireless communication system 100 may include multiple network devices, and each network device may include a different number of terminal devices within its coverage area, which is not limited in this embodiment of the present application. 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 this embodiment of the present application.
[0034] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (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.
[0035] The UE in the embodiments of the present application may also be referred to as a terminal device, an access terminal, a user unit, a user station, a mobile station, a mobile station (MS), a mobile terminal (MT), a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. The UE 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 or an in-vehicle device with wireless connection capabilities. The UE 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 UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. 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.
[0036] The network device in the embodiments of the present application may be a device for communicating with a UE, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a UE to a wireless network. A base station may broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A 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.
[0037] In some embodiments, the network device can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile network device, and one or more cells can move according to the location of the mobile network device. In other examples, the helicopter or drone can be configured to act as a device for communicating with another network device. In some embodiments, the network device can refer to a CU or a DU, or the network device can include a CU and a DU, or the network device can also include an AAU.
[0038] It should be understood that network devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water; and can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the network devices and the scenarios in which they are used.
[0039] It should also be understood that all or part of the functions of the network device and UE in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).
[0040] Figure 2 is a diagram of the 5G system architecture, which includes: network slice selection function (NSSF), authentication server function (AUSF), unified data management (UDM), access and mobility management function (AMF), session management function (SMF), policy control function (PCF), application function (AF), UE, radio access network (RAN), user plane function (UPF), data network (DN) and other network elements.
[0041] As shown in Figure 2, the UE can establish an access layer connection with the AN through the Uu interface, exchange access layer messages and transmit wireless data. The UE can establish a non-access stratum (NAS) connection with the AMF through the N1 interface and exchange NAS messages. The AMF is the mobility management function in the core network, and the SMF is the session management function in the core network. 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 PCF is the policy management function in the core network, responsible for formulating policies related to the mobility management, session management, and billing of the UE. The UPF is the user plane function in the core network. It can transmit data with the external data network through the N6 interface and with the AN through the N3 interface.
[0042] Current cellular networks, including 5G networks, are typically used only for 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, they can detect user movements or gestures, monitor breathing, measure terminal movement speed, perform environmental imaging, and monitor weather conditions. Therefore, in cellular networks, radio electromagnetic wave signals can be used not only for communication and data transmission but also for acquiring sensory information.
[0043] Currently, discussions are underway to support perception functions (such as integrated communication and perception) in beyond 5G (B5G) mobile communication networks, and to support perception functions in 3rd Generation Partnership Project (3GPP) networks by adding sensing control network elements (SF) and corresponding processes.
[0044] Figure 3 is a flowchart of a possible method for controlling an access network device or UE to perform UE-level (per-UE) sensing operations. For example, as shown in Figure 3, when an application (e.g., AF) sends a sensing request for a target UE to the core network (e.g., network exposure function (NEF)) of a 3GPP network, the core network can select the correct access network device or other UE through a sensing control network element or a mobility management network element (e.g., AMF), and send a sensing instruction to the access network device (e.g., step 4 in Figure 3) or the target UE (e.g., step 7 in Figure 3) to trigger its ability to perform wireless measurements related to the sensing task, initiate the measurement of sensing information (e.g., steps 5 and 8 in Figure 3), and generate sensing results (e.g., steps 6 and 9 in Figure 3).
[0045] The main wireless sensing scenarios for communication and perception integration (also referred to as synaesthesia integration) are as follows:
[0046] 1) Base station echo sensing link (single gNB sensing): The base station sends a sensing signal and receives an echo signal.
[0047] 2) Inter-base station sensing link (gNB-gNB sensing): Base station B receives the sensing signal sent by base station A;
[0048] 3) Air interface uplink perception link (UE-gNB uplink perception): The base station receives the perception signal sent by the terminal;
[0049] 4) Air interface downlink perception link (UE-gNB downlink perception): The terminal receives the perception signal sent by the base station;
[0050] 5) Terminal echo perception link (single UE perception): The terminal sends a perception signal and receives an echo signal;
[0051] 6) Inter-terminal perception link (UE-UE perception): Terminal B receives the perception signal sent by terminal A.
[0052] In the early stages of B5G interawareness integration, consideration should be given to reusing existing air interface signals as much as possible to perform perception behaviors without introducing too much air interface enhancement; and considering the complexity of full-duplex implementation, collaborative perception between terminal devices and / or base stations is a priority.
[0053] For UE-level perception, the perception target is usually a certain UE or the object environment around the UE. Because it is difficult to implement UE full-duplex autonomous transmission and reception, other UE nodes may be needed to assist in the one-transmission and one-reception perception tasks.
[0054] It can be seen from the above embodiments that when performing a sensing task for a target user equipment (UE) in a sidelink (SL), assistance from other UEs may be required.
[0055] In the sidelink, the UE can discover (and select) other SL UE nodes (sidelink UE discovery and selection) in a variety of ways. The following describes two common models:
[0056] model A discovery ("I am here") model:
[0057] The model defines two roles for UEs participating in discovery: (1) Notifying UE: The notifying UE can announce certain information (such as can be carried in the notification message shown in Figure 4), which can be used by nearby UEs with discovery rights; (2) Monitoring UE: The monitoring UE monitors UEs that are interested in certain information in the vicinity of the notifying UE.
[0058] In this model, an advertising UE can broadcast advertising messages at predefined discovery intervals, and monitoring UEs that are interested in these messages can read and process the discovery messages. This model is equivalent to "I am here" because an advertising UE can broadcast information about itself.
[0059] Model B discovery ("Who's there?" / "Are you there?") model:
[0060] The model defines two roles for UEs participating in discovery: (1) Discoverer UE: The discoverer UE can send a request message containing certain information about what it is interested in discovering; (2) Discovered UE: The UE that receives the request message can respond with some information related to the request message sent by the discoverer UE.
[0061] It is equivalent to "Who is there / Are you there?" because the discoverer UE sends information that it hopes to receive a response from other UEs. This information can be a proximity services (ProSe) application identifier corresponding to a group, and members of the group can respond.
[0062] As can be seen, currently, in the sidelink, the target UE can detect other SL UEs through various methods. However, it is not clear how to achieve the sensing task with the assistance of other UEs. Therefore, how to achieve the sensing task with the assistance of other UEs has become a technical problem that needs to be solved urgently.
[0063] Moreover, the above-mentioned sidelink UE discovery selection model is only applicable to the discoverer UE obtaining the information of the discovered UE (or the notifying UE obtaining the information of the monitoring UE). However, the execution of the final perception task requires both the discoverer UE and the discovered UE to establish a connection with the network (such as the SF in Figure 3). The discovered UE information obtained by the discoverer UE through the sidelink usually does not contain the subscription permanent identifier (SUPI) and other UE identification (ID) information that can be recognized by the core network. Even if the message is reported to the network, the network may not be able to find the corresponding UE, nor can it interact with the perception task. Therefore, how to enable other UEs in the perception task to establish a connection with the network is also a technical problem that needs to be solved.
[0064] In order to solve one or more of the above technical problems, the present application proposes a communication method and a communication device. The embodiments of the present application are described in detail below with reference to Figures 6 to 9.
[0065] FIG6 is a schematic flow chart of a communication method according to an embodiment of the present application. The method 600 shown in FIG6 may include steps S610 and S620, which are as follows:
[0066] S610: The first terminal device sends first information to the second terminal device.
[0067] The first information may be used to request the second terminal device to serve as another UE that performs the first perception task. Optionally, the first perception task may be a perception task for the first terminal device. Optionally, the other UE may refer to another SL UE that assists the first terminal device in performing the first perception task. The other UE may also be referred to as an auxiliary UE.
[0068] Optionally, the first information may include one or more of the following: identification information of the first perception task, identification information of the perception request, the perception type, perception quality requirements, and identification information of the first network element.
[0069] Among them, the identification information of the perception request can be the identification information corresponding to the following second information.
[0070] Perception types may include one or more of the following: intrusion detection, target positioning, motion capture, speed prediction, trajectory prediction, and reporting channel processing information (such as location information, Doppler frequency shift information, point cloud information, etc.).
[0071] The quality requirements of perception may include information such as perception accuracy, reporting frequency, and false alarm rate.
[0072] The first network element may be a network element for sensing services. For example, the first network element may be a newly added network element, such as a newly added sensing control network element (SF) in a 5G system. Alternatively, the first network element may be an existing network element, such as an LMF or an AMF. The identification information of the first network element may include device identification (ID) information of the first network element, instance information of the first network element within a system (such as a 5G system), and / or address information of the first network element.
[0073] Optionally, the first information may further include identification (ID) information of the first terminal device.
[0074] Optionally, the first information may be carried in a perception request message. The perception request message may be an announcement message or a solicitation message sent through the PC5 interface in the SL, or may be other messages (such as a newly defined perception request message).
[0075] Optionally, the first information may be sent by the first terminal device to one or more terminal devices around it (the second terminal device may be one of the one or more terminal devices). Optionally, the first information may be sent in a multicast or broadcast manner.
[0076] For example, the first terminal device may first discover other SL UEs through the aforementioned model A discovery model or model B discovery model, and then send the first information to the other discovered SL UEs through a perception request message.
[0077] For another example, the first terminal device may directly use a perception request message to send the first information to the terminal devices around it. Optionally, at this time, the perception request message may simultaneously contain the meaning of discovering other SL UEs and requesting other UEs as the first perception task to perceive.
[0078] In an embodiment of the present application, the first terminal device sends the first information to the second terminal device, which helps to use the second terminal device as another UE for the first perception task, thereby helping to implement the perception task with the assistance of the second terminal device.
[0079] In some embodiments, before step S610, method 600 may include step S620, which is as follows:
[0080] S620, the first network element sends second information to the first terminal device.
[0081] The second information can be used to instruct the first terminal device to discover other UEs that can perform the first perception task.
[0082] Optionally, the second information may include one or more of the following: first indication information, identification information of the first perception task, identification information of the perception request, perception mode, perception type, perception quality requirement, and identification information of the first network element. The first indication information may instruct the first terminal device to discover other UEs for performing the first perception task.
[0083] In this application, the second information can be discovered in a variety of ways, as follows:
[0084] In some embodiments, the second information may be indicated in an explicit manner. For example, the second information itself may be a request message for requesting the first terminal device to discover other UEs for performing the first sensing task; or the second information may include a request message, such as the first indication information described above.
[0085] In some embodiments, the second information may be indicated in an implicit manner. For example, when the second information includes one or more of the identification information of the first perception task, the identification information of the perception request, the perception method, the perception type, the perception quality requirement, and the identification information of the first network element, it may indicate a request for the first terminal device to discover other UEs for performing the first perception task. The perception method may include an indication of the method in which the first terminal device sends and other UEs (such as the second terminal device) receive, and may also include an indication of other UEs as senders or receivers.
[0086] In the present application, a connection between other UEs and the network can be established through a variety of methods, which are respectively explained below in conjunction with Figures 7 to 9 (the first network element in Figures 7 to 9 takes SF as an example).
[0087] Method 1: The first terminal device sends the identification information of the first network element to the second terminal device. After receiving the first information, the second terminal device actively establishes a connection with the first network element based on the identification information of the first network element. Method 1 is described in detail below.
[0088] The first terminal device may send the first information to its second terminal device. Optionally, the first information may include identification information of the first network element.
[0089] Optionally, the second terminal device may actively establish a connection with the first network element based on the first information.
[0090] Optionally, after establishing a connection with the first network element, the second terminal device may interact with the first network element. For example, the second terminal device may send sixth information to the first network element.
[0091] Optionally, the sixth information may be used to indicate that the second terminal device is capable of performing the first sensing task. Optionally, the sixth information may include one or more of the following: identification information of the first sensing task, identification information of the sensing request, and identification information of the first terminal device.
[0092] Optionally, the first network element may receive sixth information sent by one or more terminal devices (the second terminal device may be one of the one or more terminal devices), and determine other UEs of the first perception task based on the received sixth information.
[0093] The specific implementation process of method 1 is described below with reference to Figure 7. In Figure 7, after the SF receives the UE-level perception request message and discovers UE1, it can send a discovery request message to UE1. UE1 can carry the perception mode information of the current perception task and the identification information of the SF in the perception request message sent to the surrounding UE2. Subsequently, UE2 can establish a connection with the SF and notify the SF. At this point, the SF can then select other UEs.
[0094] As shown in FIG7 , method 700 may include steps S710 to S790, which are specifically as follows:
[0095] S710: The consumer NF sends a perception request message to the SF.
[0096] The consumer NF can be a core network element, such as AMF, NEF, etc., or an application server, such as AF, or a UE.
[0097] The perception request message may include target UE information (such as target UE ID information), the requested perception mode and / or perception service type, and quality information required for the perception service, such as accuracy.
[0098] The target UE information may include one or more of the following:
[0099] The target UE's subscription permanent identifier (SUPI), subscription concealed identifier (SUCI), and generic public subscription identifier (GPSI);
[0100] Address information of the target UE (IP address, MAC address, etc.).
[0101] Optionally, the SF or other network elements (such as NEF, etc.) may map the target UE information to convert it into ID information (such as SUPI, etc.) that can be directly used for query within the core network.
[0102] S720, SF queries UE1 according to the target UE information (UE1 may be the first terminal device in the above embodiment).
[0103] Specifically, SF may discover UE1 by querying other network elements, such as AMF, unified data repository (UDR), UDM, etc., or by querying local information.
[0104] S730, SF sends a discovery request message to UE1.
[0105] The discovery request message may include the second information in the aforementioned embodiment.
[0106] SF sends a discovery request message to UE1 based on the perception request message, which may include indication information for discovering the auxiliary UE. Optionally, it may also include the ID information of the perception task / request, the perception method (such as the method in which UE A sends and B receives, specifically, it may also include an indication of the auxiliary UE as a sender or receiver), the perception type, the perception quality requirements, etc. It also includes the ID information of the SF (such as the device ID information of the SF, the instance information within the 5GC, the address information of the SF, etc.).
[0107] Perception types may include intrusion detection, target positioning, motion capture, speed / trajectory prediction, etc., and may also be specific requests to report channel processing information (position information, Doppler frequency shift information, point cloud information, etc.). Perception quality requirements may include perception accuracy information, reporting frequency, false alarm rate, etc.
[0108] S740, UE1 sends a perception request message to UE2.
[0109] The perception request message may include the first information in the aforementioned embodiment.
[0110] For example, after receiving the discovery request message sent by the SF, UE1 can send a perception request message to the UE2 around it through the SL. The perception request message may include the ID information of the perception task, the ID information of the discovery request message (consistent with the ID sent by the SF), the perception type, the perception quality requirement, etc. It may also include the ID information of the SF and, optionally, the ID information of the UE1 itself.
[0111] Here, UE1 sends a perception request message to the surrounding UE2, and may reuse the announcement message (announcement message) or solicitation message (solicitation message) sent through the PC5 interface in the current SL, and add the information carried by the perception request message (such as the first information); it can also first discover other SL UEs through the aforementioned model A discovery model or model B discovery model, and then initiate a request to the other discovered SL UEs through the perception request message; it can also directly use the newly defined SL perception request message to send, and the SL perception request message may be different from the existing solicitation message, but may include the meaning of discovering SL UE and requesting to perceive as other UEs. After receiving the message, the surrounding UE2 can simultaneously reply to UE1 with a response to discovering SL UE and send a response to SF to perceive as other UEs.
[0112] S750: UE2 establishes a connection with SF.
[0113] After UE2 receives the perception request message sent by UE1, it can determine that it can perform perception tasks as other UEs based on its own perception capabilities and perception needs, and establish a connection with SF through SF's ID information. Specifically, it can establish a session through SF's user plane address information, or it can interact through control plane signaling based on SF's ID information.
[0114] S760, UE2 reports a notification message to SF.
[0115] The notification message may include the sixth information in the aforementioned embodiment.
[0116] The notification message may carry the ID information of the sensing task and the ID information of the discovery request message (consistent with that sent by the SF in S730). Optionally, the notification message may also include the ID information of UE1.
[0117] S770, SF selects other UEs to perform the sensing task.
[0118] The SF obtains information of multiple selectable UEs based on the notification messages reported by multiple UE2s, and selects other UEs.
[0119] S780, SF sends a sensing task request message to UE1.
[0120] S790: SF sends a sensing task request message to the selected UE2, which may be different from the sensing request sent to UE1.
[0121] This application carries the perception requirements and SF ID information in the perception request message sent by UE1 to its surrounding UEs, so that the surrounding UEs can know whether they can support the perception task, and know how to establish a connection with the SF and report that they can complete the perception task as other UEs.
[0122] Method 2: The first terminal device selects the second terminal device as the other UE for the first sensing task and sends the identification information of the first network element to the second terminal device, and the second terminal device actively connects to the first network element based on the identification information of the first network element. Method 2 is described in detail below.
[0123] Optionally, after receiving the first information, the second terminal device may send third information to the first terminal device.
[0124] Optionally, the third information may be used to indicate that the second terminal device is capable of performing the first perception task. Optionally, the third information may include perception capability information of the second terminal device. Optionally, the perception capability information may include information such as the perception type supported by the second terminal device and the perception quality capability.
[0125] Optionally, the first terminal device can determine, based on the third information, that the second terminal device can serve as another UE that performs the first perception task.
[0126] Furthermore, the first terminal device may send fourth information to the second terminal device.
[0127] Optionally, the fourth information may be used to request the second terminal device to perform the first perception task. Optionally, the fourth information may include one or more of the following: identification information of the first perception task, identification information of the perception request, the perception type, the perception quality requirement, identification information of the first network element, and identification information of the first terminal device.
[0128] Optionally, after receiving the fourth information, the second terminal device may establish a connection with the first network element and interact with the first network element.
[0129] The specific implementation process of Method 2 is described below in conjunction with Figure 8. In Figure 8, after the SF receives the UE-level perception request message and discovers UE1, it can send a discovery request message to UE1. UE1 can send a perception request message to the surrounding UE2, which carries the perception mode information of the current perception task, etc. After obtaining the UE information of UE2, the UE can select other UEs and send perception task request messages to the selected UEs. The other UEs can establish connections with the SF and directly report perception data to the SF.
[0130] As shown in FIG8 , method 800 may include steps S810 to S880, which are specifically as follows:
[0131] S810: The consumer NF sends a perception request message to the SF.
[0132] The consumer NF can be a core network element, such as AMF, NEF, etc., or an application server, such as AF, or a UE.
[0133] The perception request message may include target UE information (such as target UE ID information), the requested perception mode and / or perception service type, and quality information required for the perception service, such as accuracy.
[0134] The target UE information may include one or more of the following:
[0135] The target UE's subscription permanent identifier (SUPI), subscription concealed identifier (SUCI), and generic public subscription identifier (GPSI);
[0136] Address information of the target UE (IP address, MAC address, etc.).
[0137] Optionally, the SF or other network elements (such as NEF, etc.) may map the target UE information to convert it into ID information (such as SUPI, etc.) that can be directly used for query within the core network.
[0138] S820, SF queries UE1 according to the target UE information (UE1 may be the first terminal device in the above embodiment).
[0139] Specifically, SF may discover UE1 by querying other network elements, such as AMF, unified data repository (UDR), UDM, etc., or by querying local information.
[0140] S830, SF sends a discovery request message to UE1.
[0141] The discovery request message may include the second information in the aforementioned embodiment.
[0142] SF sends a discovery request message to UE1 based on the perception request message, which may include indication information for discovering the auxiliary UE. Optionally, it may also include the ID information of the perception task / request, the perception method (such as the method in which UE A sends and B receives, specifically, it may also include an indication of the auxiliary UE as a sender or receiver), the perception type, the perception quality requirements, etc. It also includes the ID information of the SF (such as the device ID information of the SF, the instance information within the 5GC, the address information of the SF, etc.).
[0143] Perception types may include intrusion detection, target positioning, motion capture, speed / trajectory prediction, etc., and may also be specific requests to report channel processing information (position information, Doppler frequency shift information, point cloud information, etc.). Perception quality requirements may include perception accuracy information, reporting frequency, false alarm rate, etc.
[0144] S840, UE1 sends a perception request message to UE2.
[0145] The perception request message may include the first information in the aforementioned embodiment.
[0146] For example, after receiving the discovery request message sent by the SF, the UE1 can send a perception request message to the UE2 around it in the SL mode. The perception request message may include the perception type, the perception quality requirement, etc.
[0147] Here, UE1 sends a perception request message to the surrounding UE2, and may reuse the announcement message (announcement message) or solicitation message (solicitation message) sent through the PC5 interface in the current SL, and add the information carried by the perception request message (such as the first information); it can also first discover other SL UEs through the aforementioned model A discovery model or model B discovery model, and then initiate a request to the other discovered SL UEs through the perception request message; it can also directly use the newly defined SL perception request message to send, and the SL perception request message may be different from the existing solicitation message, but may include the meaning of discovering SL UE and requesting to perceive as other UEs. After receiving the message, the surrounding UE2 can simultaneously reply to UE1 with a response to discovering SL UE and send a response to SF to perceive as other UEs.
[0148] S850, UE2 sends a response message to UE1.
[0149] The response message may include the third information in the aforementioned embodiment.
[0150] After receiving the sensing request message sent by UE1, UE2 can determine that it can perform sensing tasks as other UEs based on its own sensing capabilities and sensing requirements, and send a response message to UE1. The response message may include an indication that it can perform sensing tasks as other UEs, and may also include UE2's sensing capability information, such as supported sensing types and sensing quality capabilities.
[0151] S860, UE1 sends a sensing task request message to UE2.
[0152] The perception task request message may include the fourth information in the aforementioned embodiment.
[0153] After receiving the response message from UE2, UE1 can select UE2 as the other UE and send a sensing task request message to UE2. The sensing task request message may include the ID information of the sensing task, the ID information of the discovery request message (consistent with the ID issued by the SF), the sensing type, the sensing quality requirement, etc. It may also include the ID information of the SF and, optionally, the ID information of UE1 itself.
[0154] S870: UE2 establishes a connection with SF.
[0155] After receiving the perception task request message sent by UE1, UE2 can establish a connection with SF through the ID information of SF. Specifically, it can establish a session through the user plane address information of SF, or interact through control plane signaling according to the ID information of SF.
[0156] S880, UE2 reports the perception data to SF.
[0157] UE2 can report the perception data to SF based on the ID information of the perception task, the ID information of the discovery request message (consistent with that sent by SF in S830 and the same as that sent by UE1 in S860), and the ID information of UE1.
[0158] This application obtains the perception capability information of surrounding UEs by UE1 sending a perception request message to its surrounding UEs, selects other UEs, and then sends the SF ID information to the selected other UEs, so that other UEs can communicate with the SF and report perception data.
[0159] Method 3: The first terminal device reports to the first network element that the second terminal device can perform the first sensing task, and the first network element selects the second terminal device as the other UE for the first sensing task and establishes a connection with the second terminal device. Method 3 is described in detail below.
[0160] Optionally, after receiving the first information, the second terminal device may send third information to the first terminal device.
[0161] Optionally, the third information may be used to indicate that the second terminal device is capable of performing the first sensing task. Optionally, the third information may include sensing capability information of the second terminal device.
[0162] Optionally, the first terminal device may send fifth information to the first network element based on the third information. Optionally, the fifth information may be used to indicate that the second terminal device is capable of performing the first sensing task.
[0163] Optionally, the fifth information may include one or more of the following: identification information of the second terminal device, address information of the second terminal device, identification information of the first perception task, and identification information of the perception request.
[0164] Optionally, after selecting the second terminal device as the other UE for the first perception task, the first network element can establish a connection with the second terminal device and interact with the second terminal device.
[0165] The specific implementation process of method three is described below with reference to Figure 9. In Figure 9, after the SF receives the UE-level perception request message and discovers UE1, it sends a discovery request message to UE1. UE1 can carry the perception mode information of the current perception task in the perception request message sent to the surrounding UE2. UE1 obtains the UE information of UE2 and notifies the SF, which can then select other UEs.
[0166] As shown in FIG9 , method 900 may include steps S910 to S990, which are specifically as follows:
[0167] S910: The consumer NF sends a perception request message to the SF.
[0168] The consumer NF can be a core network element, such as AMF, NEF, etc., or an application server, such as AF, or a UE.
[0169] The perception request message may include target UE information (such as target UE ID information), the requested perception mode and / or perception service type, and quality information required for the perception service, such as accuracy.
[0170] The target UE information may include one or more of the following:
[0171] The target UE's subscription permanent identifier (SUPI), subscription concealed identifier (SUCI), and generic public subscription identifier (GPSI);
[0172] Address information of the target UE (IP address, MAC address, etc.).
[0173] Optionally, the SF or other network elements (such as NEF, etc.) may map the target UE information to convert it into ID information (such as SUPI, etc.) that can be directly used for query within the core network.
[0174] S920, SF queries UE1 according to the target UE information (UE1 may be the first terminal device in the above embodiment).
[0175] Specifically, SF may discover UE1 by querying other network elements, such as AMF, unified data repository (UDR), UDM, etc., or by querying local information.
[0176] S930, SF sends a discovery request message to UE1.
[0177] The discovery request message may include the second information in the aforementioned embodiment.
[0178] SF sends a discovery request message to UE1 based on the perception request message, which may include indication information for discovering the auxiliary UE. Optionally, it may also include the ID information of the perception task / request, the perception method (such as the method in which UE A sends and B receives, specifically, it may also include an indication of the auxiliary UE as a sender or receiver), the perception type, the perception quality requirements, etc. It also includes the ID information of the SF (such as the device ID information of the SF, the instance information within the 5GC, the address information of the SF, etc.).
[0179] Perception types may include intrusion detection, target positioning, motion capture, speed / trajectory prediction, etc., and may also be specific requests to report channel processing information (position information, Doppler frequency shift information, point cloud information, etc.). Perception quality requirements may include perception accuracy information, reporting frequency, false alarm rate, etc.
[0180] S940, UE1 sends a perception request message to UE2.
[0181] The perception request message may include the first information in the aforementioned embodiment.
[0182] For example, after receiving the discovery request message sent by the SF, UE1 can send a perception request message to the UE2 around it through the SL. The perception request message may include the ID information of the perception task, the ID information of the discovery request message (consistent with the ID sent by the SF), the perception type, the perception quality requirement, etc. It may also include the ID information of the SF and, optionally, the ID information of the UE1 itself.
[0183] Here, UE1 sends a perception request message to the surrounding UE2, and may reuse the announcement message (announcement message) or solicitation message (solicitation message) sent through the PC5 interface in the current SL, and add the information carried by the perception request message (such as the first information); it can also first discover other SL UEs through the aforementioned model A discovery model or model B discovery model, and then initiate a request to the other discovered SL UEs through the perception request message; it can also directly use the newly defined SL perception request message to send, and the SL perception request message may be different from the existing solicitation message, but may include the meaning of discovering SL UE and requesting to perceive as other UEs. After receiving the message, the surrounding UE2 can simultaneously reply to UE1 with a response to discovering SL UE and send a response to SF to perceive as other UEs.
[0184] S950, UE2 sends a response message to UE1.
[0185] The response message may include the third information in the aforementioned embodiment.
[0186] After receiving the perception request message sent by UE1, UE2 can determine that it can perform the perception task as other UE based on its own perception capabilities and perception requirements, and send a response message to UE1. The response message may include an indication that it can perform the perception task as other UE, and may also include UE2's ID information and / or address information, and UE2's perception capability information (such as supported perception types, perception quality capabilities, etc.).
[0187] S960, UE1 sends a discovery response message to SF.
[0188] The discovery response message may include the fifth information in the aforementioned embodiment.
[0189] The discovery response message may carry the ID information and / or address information of UE2, and optionally, may also include the ID information of the perception task, the ID information of the discovery request message (consistent with that sent by SF), etc.
[0190] S970, SF selects another UE.
[0191] The SF may obtain information of multiple selectable UEs (such as ID information and / or address information of UE2) based on the discovery response message reported by UE1, and select other UEs.
[0192] S980: SF establishes a connection with UE2.
[0193] The SF may establish user plane or control plane connections with multiple selected UE2s according to the ID information and / or address information of the UE2.
[0194] S990, SF sends a sensing task request message to UE1 and UE2.
[0195] This solution carries the perception requirements and SF ID information in the perception request message sent by UE1 to its surrounding UEs, so that the surrounding UEs can know whether they can support the perception task. After UE1 selects other UEs, it reports the information of the selected other UEs to SF, and SF triggers the establishment of connections with other UEs.
[0196] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 9 . The device embodiment of the present application is described in detail below in conjunction with Figures 10 to 13 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for portions not described in detail, reference can be made to the above method embodiment.
[0197] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application. As shown in FIG10 , the device 1000 includes a sending unit 1010, which is specifically as follows:
[0198] The sending unit 1010 is used to send first information to the second terminal device, where the first information is used to request the second terminal device to serve as another user equipment UE to perform the first perception task.
[0199] Optionally, the first information includes one or more of the following: identification information of the first perception task, identification information of the perception request, perception type, perception quality requirements, and identification information of the first network element.
[0200] Optionally, the device 1000 further includes a receiving unit 1020, configured to receive second information sent by the first network element, where the second information is used to instruct the device to discover other user equipment UEs capable of performing the first perception task.
[0201] Optionally, the second information includes one or more of the following: first indication information, identification information of the first perception task, identification information of the perception request, perception method, perception type, perception quality requirement, and identification information of the first network element; wherein, the first indication information instructs the device to discover other UEs for performing the first perception task.
[0202] Optionally, the apparatus 1000 further includes a receiving unit 1020, configured to receive third information sent by the second terminal device, wherein the third information is used to indicate that the second terminal device is capable of performing the first perception task.
[0203] Optionally, the third information includes perception capability information of the second terminal device.
[0204] Optionally, the apparatus 1000 further includes a determination unit 1030, configured to determine, based on the third information, that the second terminal device can serve as another UE that performs the first perception task.
[0205] Optionally, the sending unit 1010 is further used to: send fourth information to the second terminal device, where the fourth information is used to request the second terminal device to perform the first perception task.
[0206] Optionally, the fourth information includes one or more of the following: identification information of the first perception task, identification information of the perception request, perception type, perception quality requirements, identification information of the first network element, and identification information of the device.
[0207] Optionally, the sending unit 1010 is further used to: send fifth information to the first network element according to the third information, and the fifth information is used to indicate that the second terminal device can perform the first perception task.
[0208] Optionally, the fifth information includes one or more of the following: identification information of the second terminal device, address information of the second terminal device, identification information of the first perception task, and identification information of the perception request.
[0209] Optionally, the first network element is a network element used for perception service.
[0210] Optionally, the perception type includes one or more of the following: intrusion monitoring, target positioning, motion capture, speed prediction, trajectory prediction, and reporting channel processing information.
[0211] FIG11 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device 1100 in FIG11 includes a receiving unit 1110, which is specifically as follows:
[0212] The receiving unit 1110 is used to receive first information sent by a first terminal device, where the first information is used to request the device to act as another user equipment UE to perform a first perception task.
[0213] Optionally, the first information includes one or more of the following: identification information of the first perception task, identification information of the perception request, perception type, perception quality requirements, and identification information of the first network element.
[0214] Optionally, the device 1100 further includes a sending unit 1120, configured to send sixth information to the first network element, wherein the sixth information is used to indicate that the device is capable of performing the first perception task.
[0215] Optionally, the sixth information includes one or more of the following: identification information of the first perception task, identification information of the perception request, and identification information of the first terminal device.
[0216] Optionally, the apparatus 1100 further includes a sending unit 1120, configured to send third information to the first terminal device, wherein the third information is used to indicate that the apparatus is capable of performing the first perception task.
[0217] Optionally, the third information includes perception capability information of the device.
[0218] Optionally, the receiving unit 1110 is further used to: receive fourth information sent by the first terminal device, where the fourth information is used to request the device to perform the first perception task.
[0219] Optionally, the fourth information includes one or more of the following: identification information of the first perception task, identification information of the perception request, perception type, perception quality requirements, identification information of the first network element, and identification information of the first terminal device.
[0220] Optionally, the first network element is a network element used for perception service.
[0221] Optionally, the perception type includes one or more of the following: intrusion monitoring, target positioning, motion capture, speed prediction, trajectory prediction, and reporting channel processing information.
[0222] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device 1200 in FIG12 includes a sending unit 1210, which is specifically as follows:
[0223] The sending unit 1210 is used to send second information to the first terminal device, where the second information is used to instruct the first terminal device to discover other user equipment UE that can perform the first perception task.
[0224] Optionally, the second information includes one or more of the following: first indication information, identification information of the first perception task, identification information of the perception request, perception method, perception type, perception quality requirement, and identification information of the device; wherein, the first indication information indicates that the first terminal device discovers other UEs for performing the first perception task.
[0225] Optionally, the apparatus 1200 further includes a receiving unit 1220, configured to receive sixth information sent by a second terminal device, wherein the sixth information is used to indicate that the second terminal device is capable of performing the first perception task.
[0226] Optionally, the sixth information includes one or more of the following: identification information of the first perception task, identification information of the perception request, and identification information of the first terminal device.
[0227] Optionally, the apparatus 1200 further includes a receiving unit 1220, configured to receive fifth information sent by the first terminal device, wherein the fifth information is used to indicate that the second terminal device is capable of performing the first perception task.
[0228] Optionally, the fifth information includes one or more of the following: identification information of the second terminal device, address information of the second terminal device, identification information of the first perception task, and identification information of the perception request.
[0229] Optionally, the device is a network element for sensing services.
[0230] Optionally, the perception type includes one or more of the following: intrusion monitoring, target positioning, motion capture, speed prediction, trajectory prediction, and reporting channel processing information.
[0231] FIG13 is a schematic diagram of the structure of an apparatus provided in one embodiment of the present application. The dashed lines in FIG13 indicate that the unit or module is optional. Apparatus 1300 may be used to implement the method described in the above method embodiment. Apparatus 1300 may be a chip or a communication device.
[0232] The device 1300 may include one or more processors 1310. The processor 1310 may support the device 1300 to implement the method described in the above method embodiment. The processor 1310 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.
[0233] The apparatus 1300 may further include one or more memories 1320. The memories 1320 store programs that can be executed by the processor 1310, causing the processor 1310 to perform the methods described in the above method embodiments. The memories 1320 may be independent of the processor 1310 or integrated into the processor 1310.
[0234] The apparatus 1300 may further include a transceiver 1330. The processor 1310 may communicate with other devices or chips via the transceiver 1330. For example, the processor 1310 may transmit and receive data with other devices or chips via the transceiver 1330.
[0235] The present invention also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the communication device provided in the present invention, and the program enables a computer to execute the method performed by the communication device in each embodiment of the present invention.
[0236] 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 communication device provided in the present application, and the program causes a computer to execute the method performed by the communication device in each embodiment of the present application.
[0237] The embodiments of the present application also provide a computer program. The computer program can be applied to the communication device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the communication device in each embodiment of the present application.
[0238] It should be understood that in the embodiments 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 also 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.
[0239] It should be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.
[0240] It should be understood that in the 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.
[0241] 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.
[0242] 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.
[0243] 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.
[0244] 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)).
[0245] 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 communication method, characterized in that: include: The first terminal device sends first information to the second terminal device, where the first information is used to request the second terminal device to serve as another user equipment UE that performs a first perception task.
2. The method according to claim 1, characterized in that: The first information includes one or more of the following: The identification information of the first perception task, the identification information of the perception request, the perception type, the perception quality requirement, and the identification information of the first network element.
3. The method according to claim 1 or 2, characterized in that: The method further comprises: The first terminal device receives second information sent by the first network element, where the second information is used to instruct the first terminal device to discover other user equipment UE that can perform the first perception task.
4. The method according to claim 3, characterized in that The second information includes one or more of the following: first indication information, identification information of the first sensing task, identification information of the sensing request, sensing mode, sensing type, sensing quality requirement, and identification information of the first network element; Among them, the first indication information instructs the first terminal device to discover other UEs for performing the first perception task.
5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: The first terminal device receives third information sent by the second terminal device, where the third information is used to indicate that the second terminal device can perform the first perception task.
6. The method according to claim 5, characterized in that The third information includes perception capability information of the second terminal device.
7. The method according to claim 5 or 6, characterized in that: The method further comprises: The first terminal device determines, based on the third information, that the second terminal device can serve as another UE that performs the first perception task.
8. The method according to claim 7, characterized in that The method further comprises: The first terminal device sends fourth information to the second terminal device, where the fourth information is used to request the second terminal device to perform the first perception task.
9. The method according to claim 8, characterized in that The fourth information includes one or more of the following: The identification information of the first perception task, the identification information of the perception request, the perception type, the perception quality requirement, the identification information of the first network element, and the identification information of the first terminal device.
10. The method according to claim 5 or 6, characterized in that: The method further comprises: The first terminal device sends fifth information to the first network element based on the third information, and the fifth information is used to indicate that the second terminal device can perform the first perception task.
11. The method according to claim 10, characterized in that The fifth information includes one or more of the following: The identification information of the second terminal device, the address information of the second terminal device, the identification information of the first perception task, and the identification information of the perception request.
12. The method according to any one of claims 2 to 11, characterized in that The first network element is a network element used for sensing services.
13. The method according to any one of claims 2, 3 and 9, characterized in that: The perception type includes one or more of the following: Intrusion monitoring, target positioning, motion capture, speed prediction, trajectory prediction, and reporting channel processing information.
14. A communication method, characterized in that: include: The second terminal device receives the first information sent by the first terminal device, where the first information is used to request the second terminal device to serve as another user equipment UE that performs the first perception task.
15. The method according to claim 14, characterized in that The first information includes one or more of the following: the identification information of the first sensing task, the identification information of the sensing request, the sensing type, the sensing quality requirement, Identification information of the first network element.
16. The method according to claim 14 or 15, characterized in that The method further comprises: The second terminal device sends sixth information to the first network element, where the sixth information is used to indicate that the second terminal device can perform the first perception task.
17. The method according to claim 16, characterized in that The sixth information includes one or more of the following: The identification information of the first perception task, the identification information of the perception request, and the identification information of the first terminal device.
18. The method according to claim 14 or 15, characterized in that The method further comprises: The second terminal device sends third information to the first terminal device, where the third information is used to indicate that the second terminal device can perform the first perception task.
19. The method according to claim 18, characterized in that The third information includes perception capability information of the second terminal device.
20. The method according to claim 18 or 19, characterized in that The method further comprises: The second terminal device receives fourth information sent by the first terminal device, where the fourth information is used to request the second terminal device to perform the first perception task.
21. The method according to claim 20, characterized in that The fourth information includes one or more of the following: The identification information of the first perception task, the identification information of the perception request, the perception type, the perception quality requirement, the identification information of the first network element, and the identification information of the first terminal device.
22. The method according to any one of claims 15 to 21, characterized in that The first network element is a network element used for sensing services.
23. The method according to claim 15 or 21, characterized in that The perception type includes one or more of the following: Intrusion monitoring, target positioning, motion capture, speed prediction, trajectory prediction, and reporting channel processing information.
24. A communication method, characterized in that: include: The first network element sends second information to the first terminal device, where the second information is used to instruct the first terminal device to discover other user equipment UE that can perform the first perception task.
25. The method according to claim 24, characterized in that The second information includes one or more of the following: first indication information, identification information of the first sensing task, identification information of the sensing request, sensing mode, sensing type, sensing quality requirement, and identification information of the first network element; Among them, the first indication information instructs the first terminal device to discover other UEs for performing the first perception task.
26. The method according to claim 24 or 25, characterized in that The method further comprises: The first network element receives sixth information sent by the second terminal device, and the sixth information is used to indicate that the second terminal device can perform the first perception task.
27. The method according to claim 26, characterized in that The sixth information includes one or more of the following: The identification information of the first perception task, the identification information of the perception request, and the identification information of the first terminal device.
28. The method according to claim 24 or 25, characterized in that The method further comprises: The first network element receives fifth information sent by the first terminal device, and the fifth information is used to indicate that the second terminal device can perform the first perception task.
29. The method according to claim 28, characterized in that The fifth information includes one or more of the following: The identification information of the second terminal device, the address information of the second terminal device, the identification information of the first perception task, and the identification information of the perception request.
30. The method according to any one of claims 24 to 29, characterized in that The first network element is a network element F used for sensing services.
31. The method according to claim 25, characterized in that The perception type includes one or more of the following: Intrusion monitoring, target positioning, motion capture, speed prediction, trajectory prediction, and reporting channel processing information.
32. A communication device, characterized in that: include: A sending unit is used to send first information to a second terminal device, where the first information is used to request the second terminal device to serve as another user equipment UE that performs a first perception task.
33. The device according to claim 32, characterized in that The first information includes one or more of the following: The identification information of the first perception task, the identification information of the perception request, the perception type, the perception quality requirement, and the identification information of the first network element.
34. The device according to claim 32 or 33, characterized in that The device also includes a receiving unit, which is used to: receive second information sent by the first network element, where the second information is used to instruct the device to discover other user equipment UE that can perform the first perception task.
35. The device according to claim 34, characterized in that The second information includes one or more of the following: First indication information, identification information of the first perception task, identification information of the perception request, perception method, perception type, perception quality requirement, and identification information of the first network element; wherein, the first indication information instructs the device to discover other UEs for performing the first perception task.
36. The device according to any one of claims 32 to 35, characterized in that The apparatus also includes a receiving unit, configured to receive third information sent by the second terminal device, wherein the third information is used to indicate that the second terminal device is capable of performing the first sensing task.
37. The device according to claim 36, characterized in that The third information includes perception capability information of the second terminal device.
38. The device according to claim 36 or 37, characterized in that The apparatus also includes a determination unit, configured to determine, based on the third information, that the second terminal device can serve as another UE that performs the first perception task.
39. The device according to claim 38, characterized in that The sending unit is further used to: send fourth information to the second terminal device, where the fourth information is used to request the second terminal device to perform the first perception task.
40. The device according to claim 39, characterized in that The fourth information includes one or more of the following: The identification information of the first perception task, the identification information of the perception request, the perception type, the perception quality requirement, the identification information of the first network element, and the identification information of the device.
41. The device according to claim 36 or 37, characterized in that The sending unit is also used to: send fifth information to the first network element according to the third information, and the fifth information is used to indicate that the second terminal device can perform the first perception task.
42. The device according to claim 41, characterized in that The fifth information includes one or more of the following: The identification information of the second terminal device, the address information of the second terminal device, the identification information of the first perception task, and the identification information of the perception request.
43. The device according to any one of claims 33 to 42, characterized in that The first network element is a network element used for sensing services.
44. The device according to any one of claims 33, 34 and 40, characterized in that The perception type includes one or more of the following: Intrusion monitoring, target positioning, motion capture, speed prediction, trajectory prediction, and reporting channel processing information.
45. A communication device, characterized in that: include: A receiving unit is used to receive first information sent by a first terminal device, where the first information is used to request the device to act as another user equipment UE to perform a first perception task.
46. The device according to claim 45, characterized in that The first information includes one or more of the following: The identification information of the first perception task, the identification information of the perception request, the perception type, the perception quality requirement, and the identification information of the first network element.
47. The device according to claim 45 or 46, characterized in that The device also includes a sending unit, which is used to: send sixth information to the first network element, and the sixth information is used to indicate that the device can perform the first perception task.
48. The device according to claim 47, characterized in that The sixth information includes one or more of the following: The identification information of the first perception task, the identification information of the perception request, and the identification information of the first terminal device.
49. The device according to claim 45 or 46, characterized in that The apparatus further includes a sending unit, configured to send third information to the first terminal device, wherein the third information is used to indicate that the apparatus is capable of performing the first sensing task.
50. The device according to claim 49, characterized in that The third information includes sensory capability information of the device.
51. The device according to claim 49 or 50, characterized in that The receiving unit is also used to: receive fourth information sent by the first terminal device, and the fourth information is used to request the device to perform the first perception task.
52. The device according to claim 51, characterized in that The fourth information includes one or more of the following: The identification information of the first perception task, the identification information of the perception request, the perception type, the perception quality requirement, the identification information of the first network element, and the identification information of the first terminal device.
53. The device according to any one of claims 46 to 52, characterized in that The first network element is a network element used for sensing services.
54. The device according to claim 46 or 52, characterized in that The perception type includes one or more of the following: Intrusion monitoring, target positioning, motion capture, speed prediction, trajectory prediction, and reporting channel processing information.
55. A communication device, characterized in that: include: A sending unit is used to send second information to the first terminal device, where the second information is used to indicate that the first terminal device has discovered other user equipment UE that can perform the first perception task.
56. The device according to claim 55, characterized in that The second information includes one or more of the following: First indication information, identification information of the first perception task, identification information of the perception request, perception method, perception type, perception quality requirement, and identification information of the device; wherein, the first indication information indicates that the first terminal device discovers other UEs for performing the first perception task.
57. The device according to claim 55 or 56, characterized in that The apparatus also includes a receiving unit, configured to receive sixth information sent by a second terminal device, wherein the sixth information is used to indicate that the second terminal device is capable of performing the first sensing task.
58. The device according to claim 57, characterized in that The sixth information includes one or more of the following: The identification information of the first perception task, the identification information of the perception request, and the identification information of the first terminal device.
59. The device according to claim 55 or 56, characterized in that The apparatus also includes a receiving unit, configured to receive fifth information sent by the first terminal device, wherein the fifth information is used to indicate that the second terminal device is capable of performing the first sensing task.
60. The device according to claim 59, characterized in that The fifth information includes one or more of the following: The identification information of the second terminal device, the address information of the second terminal device, the identification information of the first perception task, and the identification information of the perception request.
61. The device according to any one of claims 55 to 60, characterized in that The device is a network element for sensing services.
62. The device according to claim 56, characterized in that The perception type includes one or more of the following: Intrusion monitoring, target positioning, motion capture, speed prediction, trajectory prediction, and reporting channel processing information.
63. A communication device, characterized in that: It includes a memory, a transceiver and a processor, the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method as described in any one of claims 1 to 13.
64. A communication device, characterized in that: It includes a memory, a transceiver and a processor, the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method as described in any one of claims 14 to 23.
65. A communication device, characterized in that: It includes a memory, a transceiver and a processor, the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method as described in any one of claims 24 to 31.
66. A communication device, characterized in that: The device comprises a processor, configured to call a program from a memory so as to enable the communication device to execute the method according to any one of claims 1 to 13.
67. A communication device, characterized in that: The device comprises a processor, configured to call a program from a memory so as to enable the communication device to execute the method according to any one of claims 14 to 23.
68. A communication device, characterized in that: The device comprises a processor, configured to call a program from a memory so as to enable the communication device to execute the method according to any one of claims 24 to 31.
69. A chip, characterized in that: The device comprises a processor, which is used to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 13.
70. A chip, characterized in that: The device comprises a processor, configured to call a program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 14 to 23.
71. A chip, characterized in that: The device comprises a processor, configured to call a program from a memory so that a device equipped with the chip executes a method as claimed in any one of claims 24 to 31.
72. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 13.
73. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 14 to 23.
74. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 24 to 31.
75. A computer program product, characterized in that The method comprises a program for causing a computer to execute the method according to any one of claims 1 to 13.
76. A computer program product, characterized in that A program is included, which causes a computer to execute the method as claimed in any one of claims 14 to 23.
77. A computer program product, characterized in that A program is included, which causes a computer to execute the method as claimed in any one of claims 24 to 31.
78. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 13.
79. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 14 to 23.
80. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 24 to 31.