Communication method and communication device
By optimizing the perception data collection architecture, the problems of resource waste and inefficiency in the communication system were solved, and more efficient data collection and processing were achieved.
Patent Information
- Application Number
- PCT/CN2025/094001
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
Existing communication systems suffer from resource waste and inefficiency during the collection of sensing data. The same data may be repeatedly collected and stored by multiple network elements, triggering measurement tasks multiple times, increasing the computational load, and affecting normal business processing.
By optimizing the sensing data collection architecture, the sensing data collection process can be managed in a unified manner, reducing redundant collection and storage, allocating resources rationally, and improving data collection efficiency.
It reduces resource waste, lowers the computing load on terminal and network devices, and improves data collection efficiency and system performance.
Smart Images

Figure CN2025094001_12112026_PF_FP_ABST
Abstract
Description
Communication methods and communication equipment Technical Field
[0001] This application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Technology
[0002] With the development of communication technology, communication systems have gradually begun to support sensing and measurement based on wireless communication signals. During the sensing and measurement process, sensing data is generated; how to collect this data to generate sensing results is a problem that needs to be solved. Summary of the Invention
[0003] This application provides a communication method and a communication device. The various aspects covered by this application are described below.
[0004] In a first aspect, a communication method is provided, comprising: a first network element receiving a sensing service request; the first network element receiving sensing data matching the sensing service request from a second network element and / or from a sensing receiver associated with the sensing service request; wherein the second network element is a service data collection network element for a non-sensing service, and the service data collected by the second network element includes the sensing data.
[0005] In a second aspect, a communication method is provided, comprising: a second network element sending sensing data matching a sensing service request to a first network element; wherein the second network element is a service data collection network element for a non-sensing service, and the service data collected by the second network element includes the sensing data.
[0006] Thirdly, a communication method is provided, comprising: a third network element receiving a first message sent by a first network element, the first message being used to request the collection of sensing data from a second network element associated with the third network element; wherein the second network element is a service data collection network element for non-sensing services, and the service data collected by the second network element includes the sensing data.
[0007] Fourthly, a communication method is provided, comprising: a terminal device receiving control plane signaling sent by a first network element, the control plane signaling being used to instruct the terminal device to transmit sensing data to the first network element through a user plane connection or a data connection.
[0008] Fifthly, a communication device is provided, the communication device being a first network element, the communication device comprising: a communication module, configured to receive a sensing service request, and receive sensing data matching the sensing service request from a second network element and / or from a sensing receiver associated with the sensing service request; wherein the second network element is a service data collection network element for non-sensing services, and the service data collected by the second network element includes the sensing data.
[0009] In a sixth aspect, a communication device is provided, the communication device being a second network element, the communication device comprising: a communication module, configured to send sensing data matching a sensing service request to a first network element; wherein the second network element is a service data collection network element for non-sensing services, and the service data collected by the second network element includes the sensing data.
[0010] In a seventh aspect, a communication device is provided, the communication device being a third network element, the communication device comprising: a communication module, configured to receive a first message sent by a first network element, the first message being configured to request the collection of sensing data from a second network element associated with the third network element; wherein the second network element is a service data collection network element for non-sensing services, and the service data collected by the second network element includes the sensing data.
[0011] Eighthly, a communication device is provided, the communication device being a terminal device, the communication device comprising: a communication module, configured to receive control plane signaling sent by a first network element, the control plane signaling being configured to instruct the terminal device to transmit sensing data to the first network element via a user plane connection or a data connection.
[0012] A ninth aspect provides a communication device including a transceiver, a memory, and a processor, the memory for storing a program, the processor for calling the program in the memory, and controlling the transceiver to receive or transmit signals to cause the communication device to perform the method as described in any one of the first to fourth aspects.
[0013] A tenth aspect provides an apparatus including a processor for calling a program from a memory to cause the apparatus to perform the method as described in any one of the first to fourth aspects.
[0014] Eleventh aspect: A chip is provided, including a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of the first to fourth aspects.
[0015] In a twelfth aspect, a computer-readable storage medium is provided having a program stored thereon that causes a computer to perform the method described in any one of the first to fourth aspects.
[0016] In a thirteenth aspect, a computer program product is provided, comprising a program that causes a computer to perform the method as described in any one of the first to fourth aspects.
[0017] Fourteenth aspect, a computer program is provided that causes a computer to perform the method as described in any one of the first to fourth aspects. Attached Figure Description
[0018] Figure 1 is an example architecture diagram of a wireless communication system to which embodiments of this application can be applied.
[0019] Figure 2 is a schematic diagram of the communication system architecture.
[0020] Figure 3 is a schematic diagram of the core network element interface.
[0021] Figure 4 is another schematic diagram of the core network element interface.
[0022] Figure 5 is a schematic diagram of the architecture of the perception business system.
[0023] Figure 6 is a schematic diagram of the architecture of a perception data collection system applicable to embodiments of this application.
[0024] Figure 7 is a schematic flowchart of a communication method provided in one embodiment of this application.
[0025] Figure 8 is a schematic flowchart of a communication method provided in another embodiment of this application.
[0026] Figure 9 is a schematic flowchart of a communication method provided in another embodiment of this application.
[0027] Figure 10 is a flowchart of the sensing data collection process provided in an embodiment of this application.
[0028] Figure 11 is an example diagram of the user plane or data connection establishment process provided in the embodiments of this application.
[0029] Figure 12 is a schematic diagram of the structure of a communication device provided in one embodiment of this application.
[0030] Figure 13 is a schematic diagram of the structure of a communication device provided in another embodiment of this application.
[0031] Figure 14 is a schematic diagram of the structure of a communication device provided in another embodiment of this application.
[0032] Figure 15 is a schematic diagram of the structure of a communication device provided in another embodiment of this application.
[0033] Figure 16 is a schematic diagram of an apparatus applicable to embodiments of this application. Detailed Implementation
[0034] The technical solutions in this application will now be described with reference to the accompanying drawings.
[0035] Communication system
[0036] The technical solutions of this application embodiment can be applied to various communication systems. For example, the embodiments of this application can be applied to Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), Advanced Long Term Evolution (LTE-A), New Radio (NR), evolution systems of NR, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), and 5th-generation (5G) systems. The embodiments of this application can also be applied to other communication systems, such as 6th-generation (6G) mobile communication systems, or future communication systems such as satellite communication systems.
[0037] Traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, communication systems can support not only traditional cellular communication but also one or more other types of communication. For example, a communication system can support one or more of the following communication methods: device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), enhanced machine-type communication (eMTC), vehicle-to-vehicle (V2V) communication, and vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to communication systems that support the above-mentioned communication methods.
[0038] The communication system in this application embodiment can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.
[0039] The communication system in this application embodiment can be applied to unlicensed spectrum. This unlicensed spectrum can also be considered a shared spectrum. Alternatively, the communication system in this application embodiment can also be applied to licensed spectrum. This licensed spectrum can also be considered a dedicated spectrum.
[0040] The technical solutions of this application embodiment can be applied to various Internet of Things (IoT) communication systems. For example, this technical solution can be applied to narrowband Internet of Things (NB-IoT) communication systems. As another example, this technical solution can be applied to ambient IoT (AIoT) communication systems.
[0041] Figure 1 illustrates an example system architecture of a communication system 100 applicable to embodiments of this application. The 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 can provide network coverage for a specific geographical area and can communicate with the terminal device 120 located within that coverage area. The terminal device 120 can access a network (such as 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; this embodiment of the application does not limit this.
[0042] The terminal device in this application embodiment can 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 this application embodiment can be 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 connectivity, vehicle-mounted device, etc. The terminal devices in the embodiments of this application can be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, self-driving, remote medical surgery, smart grids, transportation safety, smart cities, smart homes, etc. Optionally, the terminal device can act as a base station. For example, the terminal device can act as a dispatching entity, providing sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) systems. For instance, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through base stations.
[0043] In some embodiments, the terminal device may also be a device in AIoT (such as a reader) to meet the needs of certain scenarios.
[0044] The network device in this application embodiment can also be an access network device or a radio access network device, such as a base station. The network device in this application embodiment can refer to a radio access network (RAN) node or device that connects a terminal device to a wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master station (MeNB), secondary station (SeNB), multi-mode 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 can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. Base stations can also be mobile switching centers, devices that perform base station functions in device-to-device (D2D), V2X, and M2M communications, network-side devices in 6G networks, and devices that perform base station functions in future communication systems. Base stations can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.
[0045] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.
[0046] In some deployments, the network device in this application embodiment may refer to a CU or a DU; or, the network device may include both a CU and a DU. The gNB may also include an AAU.
[0047] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.
[0048] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform such as a cloud platform.
[0049] Figure 1 illustrates an exemplary network device 110 and two terminal devices 120. Optionally, the communication system 100 may include multiple network devices 110, and the communication system 100 may also include other numbers of terminal devices 120.
[0050] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Taking the communication system 100 shown in FIG1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 can be the specific devices described above, which will not be repeated here. The communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities, and other network entities. This application embodiment does not limit this.
[0051] Minimization of drive-tests (MDT) technique
[0052] MDT (Multi-Data Acquisition) technology is a technique that automatically collects network measurement data through commercial terminal devices to optimize wireless networks. MDT configures network parameters, enabling supported terminal devices to automatically report measurement data during normal use.
[0053] MDT supports two data collection modes: Immediate MDT and Logged MDT. In Immediate MDT mode, the terminal device measures and reports network quality data (such as reference signal received power (RSRP), reference signal received quality (RSRQ), throughput, etc.) in real time while in connected state (RRC_CONNECTED) to support dynamic network optimization. In Logged MDT mode, the terminal device records measurement data (such as signal strength, location information) in idle state (RRC_IDLE) or inactive state (RRC_INACTIVE), and reports the measurement data the next time it accesses the network, for use by network devices in coverage blind spot analysis.
[0054] MDT measurement configuration is independent of conventional radio resource management (RRM) configuration, but actual data acquisition depends on the RRM status of the terminal device. Network devices can select appropriate terminal devices to perform tasks based on their capabilities and control these devices through signaling or management trace mechanisms. MDT measurement logs need to be bound to geographical location (depending on the terminal device's positioning capabilities), accurate timestamps, and sensor information (such as direction, air pressure, and speed). To reduce the power consumption and signaling load of terminal devices, a "decoupling of acquisition and reporting time" mechanism can be adopted, prioritizing the reuse of RRM measurement data, and considering the current status of the terminal device (e.g., battery level) when triggering the positioning process. The MDT measurement configuration can be configured to define the geographical range for executing MDT, thus limiting the area for measurement data collection. Based on 3GPP TS 32.42, MDT technology can reuse terminal device / cell tracking functions. For example, a signaling trace process can be used for a specific terminal device. Similarly, a management trace process can be used for a specific cell.
[0055] For Logged Measurement Measurement (MDT), the network device can first send a one-way signaling message to the terminal device in RRC connected state to configure the terminal device to perform measurements related to Logged Measurement Measurement (MDT). The terminal device notifies the network device of the availability of measurement logs through a 1-bit identifier in the RRC connection establishment message (such as RRCSetupComplete), triggering the network device to retrieve measurement logs on demand. The network device can also send a request through the UE Information procedure to request the terminal device to report the stored measurement logs.
[0056] Real-time MDT can be performed through RRC extended configuration. In connected mode, the terminal device reports measurement data containing global navigation satellite system (GNSS) positioning or neighboring cell radio frequency (RF) fingerprints (such as E-UTRAN cell global identifier (ECGI) / cell identifier), and performs correlation analysis with RAN measurements (such as M4-M7) through timestamps in the trace collection entity (TCE).
[0057] MDT task triggering has two modes:
[0058] 1) Administrative tracking is initiated by operations, administration and maintenance (OAM) through cell traffic tracking. It does not require specifying a particular terminal device, but user authorization must be considered (the MDT public land mobile network (PLMN) list is configured by AMF / OAM).
[0059] 2) Signaling-based tracing is activated by the core network for a specific terminal device through signaling such as the initial context establishment / switching request of the terminal device, and must comply with PLMN permissions and user licenses.
[0060] During PLMN handover, configuration information can be transferred if the target PLMN exists in the list of allowed MDT PLMNs. Furthermore, when network devices detect intra-frequency coexistence interference reported by terminal devices, they must associate the interference event with the affected RAN measurements and report it to the TCE.
[0061] MDT activation is divided into management activation and signaling activation. Management activation is handled by the Operations Support System (OSS) / Network Management System (NMS), which directly distributes configurations to network devices, AMFs, and other network elements via management interfaces. Configuration parameters include one or more of the following: tracking target (Subscription Permanent Identifier (SUPI) / International Mobile Equipment Identity (IMEI)), tracking reference identifier, TCE address, and tracking depth. In a separated architecture (gNB-CU-CP / CU-UP / DU separation), gNB-CU-CP coordinates the configuration of DU / CU-UP, passing parameters through the F1 / E1 interface; it supports selecting terminal devices based on regions (such as the NG-RAN cell list) and relies on the PLMN whitelist transmitted by the core network. After receiving the tracking configuration parameters, the Unified Data Management (UDM) transmits them to the AMF / SMF, and finally distributes the configuration parameters to the RAN. Signaling activation is triggered during core network signaling processes (such as registration and protocol data unit (PDU) session establishment). For example, the UDM transmits configuration parameters to the AMF through the Nudm interface, and the AMF then configures the measurement rules of the terminal equipment (such as log intervals, event triggering conditions, etc.) through RRC signaling.
[0062] MDT deactivation is divided into explicit deactivation and implicit deactivation. Explicit deactivation can include: OSS / NMS sending a deactivation command, or TCE actively releasing resources. Implicit deactivation can include: terminal device context release (such as detach), tracking timeout (exceeding the configured log duration), or automatic termination in the event of network failure.
[0063] Real-time MDT and log-based MDT differ in their reporting methods. Real-time MDT uses event-based (e.g., A2 event: serving cell quality below a threshold) or periodic reporting. Reported content includes real-time measurement data (e.g., RSRP / RSRQ), terminal device location (Global Navigation Satellite System (GNSS) / Observed Time Difference of Arrival (OTDOA)), and beam-level quality. This reported content requires anonymization (SUPI / IMEI masking, location obfuscation (e.g., cell CGI + offset)) to prevent user privacy leaks.
[0064] For the MDT log, the terminal device records RRM measurement results and L1 events (such as A1 / A2) in the idle / inactive state. The log cache duration can be up to 24 hours. When the terminal device enters the connected state, it can report the log via RRC signaling. This log can contain parameters such as event thresholds and the number of reports.
[0065] In a split architecture, gNB-CU-CP can aggregate log data from DU / CU-UP and forward the log data to TCE in a unified manner.
[0066] MDT can replace traditional manual drive testing with data from massive terminal devices, which can significantly reduce operation and maintenance costs, while supporting dynamic network diagnostics (such as coverage blind spot identification and interference source location) and performance optimization (such as handover parameter adjustment and capacity planning).
[0067] Tracking technology
[0068] Trace technology is a network management function defined in the 3GPP specification. It aims to optimize the network, diagnose faults, and improve user experience by actively or passively collecting signaling, measurement data, and performance indicators from terminal and network devices. Trace technology encompasses subscriber trace, equipment trace, and terminal device-level measurement functions, supporting full-domain data collection from the core network to the access network.
[0069] Data collection for positioning technology
[0070] Enhanced Location Services (eLCS) architecture is a system for enhancing location services. Its core is the collaborative collection and reporting of measurement data to the Location Management Function (LMF) through terminal devices and network devices. The LMF is responsible for generating location results based on the measurement data. Terminal devices interact with the LMF via the Location Protocol for Positioning (LPP); network devices interact with the LMF via the Neighbor Relation Protocol for Positioning Application (NRPPa). The LPP protocol can be carried by either the control plane (CP) or the user plane (UP). If carried by the UP, a UP connection needs to be established between the terminal device and the LMF. The NRPPa protocol is carried by the CP.
[0071] In addition, to improve positioning accuracy, artificial intelligence (AI) models can be applied to positioning technology. The data required for model training also needs to be collected through interaction between the LMF and the terminal device, and data collection can trigger the positioning process.
[0072] Data collection for AI / machine learning (ML)
[0073] Figure 2 illustrates the system architecture of a 5G communication system. In Figure 2, the terminal device mentioned earlier is the UE. Referring to Figure 2, the UE establishes an access layer connection with the radio access node (RAN) or access node (AN) via the Uu interface, exchanging access layer messages and radio data. The UE establishes a non-access stratum (NAS) connection with the access and mobility management function (AMF) via the N1 interface, exchanging NAS messages. The AMF is the mobility management function in the core network, and the session management function (SMF) is the session management function in the core network. In addition to managing the UE's mobility, the AMF is also responsible for forwarding session management-related messages between the UE and the SMF. The policy control function (PCF) is the policy management function in the core network, responsible for formulating policies related to UE mobility management, session management, and charging. The user plane function (UPF) transmits data with the external data network via the N6 interface and with the AN via the N3 interface. After the UE accesses the 5G network through the Uu port, it establishes a PDU session for data transmission under the control of the SMF.
[0074] In addition, 5G networks have added a network data analytics function (NWDAF) to the core network. NWDAF can collect data from various network elements and network management systems in the core network to perform big data statistics, analysis, or intelligent data analysis, and obtain network-side analysis or prediction data, thereby assisting various network elements to more effectively control UE access based on the data analysis results.
[0075] For example, NWDAF can collect data from other network elements for big data analysis. To this end, an interface is defined between NWDAF and other network functions (NFs), as shown in Figure 3. Based on this interface, an NF can request an analysis result from NWDAF (identified by an analytics ID), and NWDAF can return the analysis result to the NF.
[0076] In addition to the NWDAF, the core network also defines a data collection and coordination function (DCCF). Figure 4 illustrates the interface between the DCCF and other core network elements. As shown in Figure 4, each piece of data received from a data source NF is sent to the DCCF, which then distributes it to all consumer / notification endpoints specified by the data consumer or determined by the DCCF. Each data consumer can specify multiple notification endpoints in its requests to the DCCF; these endpoints may include the requesting data consumer, the analytics data repository function (ADRF), or other NFs. The DCCF can also select the ADRF or other notification endpoints based on its configuration. The DCCF supports data formatting and processing for each consumer / notification endpoint to ensure that the data format conforms to the data request received from each consumer NF.
[0077] When DCCF determines the data collection status of a data request: if the requested data has not yet been collected from the data source, DCCF sends a new subscription / request to the data source and specifies the notification target as DCCF; if the requested data is partially covered by an existing subscription of the data source, DCCF sends a request to the existing data source to modify the subscription, and / or creates a new subscription for new requested data that cannot be provided by the current data source; if the requested data has already been collected from the data source, DCCF determines that there is no need to create or modify a subscription to the data source.
[0078] When DCCF receives a notification, it processes it according to the formatting and processing instructions for each consumer and notification endpoint. Subsequently, DCCF sends the notification to the consumer and notification endpoint via the Ndccf_DataManagement service.
[0079] AI and wireless communication
[0080] Current wireless communication systems offer greater flexibility than their predecessors, emphasizing broad applicability to various scenarios and full utilization of limited resources. However, most current systems are still based on theoretical modeling of real-world communication environments or simple parameter selection. The gains from this approach are gradually diminishing in dynamic and complex communication environments. Therefore, it is necessary to adopt new methods and approaches, combining them with traditional wireless communication theories and systems, to find alternative solutions, break through performance bottlenecks, and further improve the performance of wireless communication systems.
[0081] Based on the above considerations, relevant technologies have begun to research AI / ML-enabled wireless air interface technologies, with the main research use cases including:
[0082] AI+Channel State Information (CSI) Feedback: AI / machine learning (ML) technology is used to compress and decompress CSI, reducing air interface transmission overhead and improving the accuracy of CSI feedback information;
[0083] AI+beam management: Utilizes AI / ML technology to predict beam information in the time and spatial domains, reducing measurement overhead and latency, and improving the accuracy of beam selection;
[0084] AI+ Positioning Technology: Utilizes AI / ML technology to predict UE location information, improving the accuracy of UE location information in NLOS scenarios.
[0085] Beyond the use cases mentioned above, related technologies also explore the lifecycle management of AI models, including model generation, deployment, transmission, monitoring, and updates. These technologies support model generation on the core network or third-party servers. In this scenario, the core network or third-party servers need to collect measurement data from terminal devices for model training.
[0086] Communication sensing technology
[0087] Based on the 3GPP TS22.137 technical specification, 5G wireless sensing achieves the perception of environmental and object features by analyzing the transmission, reflection, and scattering characteristics of wireless signals. 5G sensing is based on NR radio frequency signals, combined with existing information from EPC / E-UTRAN, and extracts target features using parameters such as signal strength, latency, Doppler shift, and angular spectrum.
[0088] Based on the deployment method of the sensing transmitter and the sensing receiver, sensing technology is divided into three modes:
[0089] Monostatic: The transmitter and receiver are co-located (such as access network equipment or terminal equipment), and sensing is achieved by analyzing the reflection characteristics of its own transmitted signals;
[0090] Bistatic: The transmitter and receiver are separate (such as access network equipment and terminal equipment working together), and sensing is achieved by receiving signals transmitted by other entities;
[0091] Multistatic: Multiple transmitters and receivers work together to improve sensing accuracy and coverage by synchronously collecting data.
[0092] Sensed data can be processed through the following process:
[0093] Signal acquisition: The sensing receiver captures wireless signals affected by the target object (reflection, refraction, diffraction).
[0094] Feature extraction: Analyze signal parameters (such as time delay and frequency offset) to calculate the target's position, velocity, shape and other attributes.
[0095] Data fusion: Combining non-3GPP sensor data (such as camera and radar) to improve the accuracy of results.
[0096] Output results: Generate perception results, including target features and contextual information (such as time and location), and provide them to authorized third parties through a secure interface.
[0097] The 3GPP TS22.137 specification also defines key performance indicators (KPIs) for sensing technologies, including positioning accuracy (horizontal / vertical), speed resolution, refresh rate, and false detection rate, to meet the needs of different scenarios, such as:
[0098] Object detection and tracking: such as unmanned aerial vehicle (UAV) positioning (accuracy 1m) and vehicle tracking (speed resolution 0.5m / s);
[0099] Environmental monitoring: such as flood level monitoring (vertical accuracy 0.2m);
[0100] Motion monitoring: such as human gesture recognition (accuracy 0.2m, refresh rate 0.1Hz).
[0101] Security requirements for sensing technologies include:
[0102] Data protection: Ensure the security of sensor data and results through encryption and integrity protection;
[0103] Privacy controls: Restrict access for unauthorized parties, and associate terminal identity with sensor results only with the user's consent;
[0104] Compliance: Follow operator policies and regional regulations to ensure that sensing services are legal and compliant.
[0105] Sensing technology can empower multiple vertical industries:
[0106] Intelligent transportation: vehicle collision avoidance, traffic flow management;
[0107] Public safety: intrusion detection, emergency rescue;
[0108] Industry 4.0: Automated Guided Vehicle (AGV) navigation and factory environment monitoring;
[0109] Consumer electronics: Gesture control and health monitoring in smart homes.
[0110] In summary, communication sensing technology, through flexible signal patterns, efficient data processing, and strict security mechanisms, extends communication networks into intelligent systems with environmental perception capabilities, providing key technological support for future intelligent applications.
[0111] In addition, to support sensing technologies, the following concepts have been defined:
[0112] 3GPP sensing data: Data derived from 3GPP radio signals affected by target objects or the environment (such as reflection, refraction, and diffraction) can be selectively processed within the 5G system for sensing purposes.
[0113] 5G wireless sensing: A functional characteristic of 5G systems, which acquires characteristic information of the environment and / or objects (such as shape, size, orientation, speed, position, distance or relative motion) through new radio frequency signals. In some cases, it can be extended by combining the existing functional information of EPC or E-UTRAN.
[0114] Non-3GPP sensing data: Sensing data about a target object or environment provided by non-3GPP sensors (such as cameras, lidar, and sonar).
[0115] Sensing assistance information: Information provided to the 5G system by a trusted third party to support the generation of sensing results. This type of information does not include 3GPP sensing data. For example, it may include map information, area information, identifiers of terminal devices attached to or near the sensing target, location information of the terminal devices, speed information of the terminal devices, etc.
[0116] Sensing contextual information: Contextual information associated with the sensing results provided by the 5G system to trusted third parties, explaining the conditions under which the sensing results were generated. This type of information does not include 3GPP sensing data.
[0117] Sensing group: A collection of sensing transmitters and receivers whose locations are known and which can synchronously collect sensing data.
[0118] Sensing receiver: An entity that receives sensing signals for use in sensing services. It can be located in a RAN (Radio Access Network) node or a user equipment (UE), and can be co-located or separate from the sensing transmitter.
[0119] Sensing result: Processed 3GPP sensing data requested by service consumers.
[0120] Sensing signal: A 3GPP radio interface transmission signal used for sensing purposes.
[0121] Sensing transmitter: An entity that transmits sensing signals for use by sensing services. It can be located in the RAN node or UE and can be co-located or separate from the sensing receiver.
[0122] Target sensing service area: A Cartesian coordinate area that uses 3GPP radio signals affected by the environment or objects (such as reflection, refraction, and diffraction) to deduce the characteristics of the environment or objects with a specific sensing service quality, covering indoor and outdoor scenarios.
[0123] Sensing service consumer: An entity that can consume sensing results or request sensing results.
[0124] Sensing entity: refers to a sensing transmitter or sensing receiver.
[0125] Sensing function: Represents the logical function that supports sensing services. A sensing function is generally not a sensing entity.
[0126] Sensing service: The ability to collect and provide information about the characteristics of objects and / or their environment via radio signals.
[0127] Figure 5 illustrates the architecture of the sensing system. As shown in Figure 5, upon receiving a sensing service request, the Sensing Service Management Function (SSMF) first authorizes the request. After authorization, the SSMF selects a sensing entity, which then senses the objects or environment within the target sensing service area. The sensing entity performs sensing measurements within the target sensing service area, and the SSMF collects and processes the sensing measurement data. Based on the sensing measurement data, the SSMF generates sensing results and provides these results to the sensing service consumer.
[0128] As described above, in related technologies, due to different purposes (MDT, tracking, data analysis, model training, etc.), the same data may be collected from multiple different network elements. The data collection methods for different network elements are usually different, and data collection for different purposes may trigger business processes multiple times, resulting in multiple measurements. This decentralized, high-frequency collection mechanism leads to resource waste and inefficiency. For example, the same data may be repeatedly collected and stored by multiple network elements (such as NWDAF, DCCF, TCE), resulting in wasted storage resources. Furthermore, multiple triggering of measurement tasks increases the computational load on terminal and network devices, affecting normal business processing.
[0129] To address the aforementioned issues, the embodiments of this application will be described in detail below.
[0130] This application relates to the collection of sensing data. For ease of understanding, an example of a sensing data collection architecture applicable to this application will be provided with reference to Figure 6.
[0131] Referring to Figure 6, this sensing data collection architecture may include one or more of the following: TCE, OSS / NMS / OAM, UDM, AMF / routing proxy, SSMF, access network equipment, and terminal equipment. TCE can be used to perform one or more of the following operations: MDT data collection, tracing data collection, and sensing data collection. OSS / NMS / OAM can be used to perform one or more of the following operations: MDT activation and / or deactivation, tracing session triggering, and routing tracing data (or tracing records) to TCE. UDM can be used to perform one or more of the following operations: tracing / MDT parameter storage, and tracing session triggering. AMF / routing proxy can be used to route tracing parameters to access network equipment. SSMF can be used to perform one or more of the following operations: authorization of sensing service requests, selection of sensing transmitters / sensing receivers, sensing data collection, generation of sensing results, and dissemination of sensing results. Access network equipment can be used for one or more of the following operations: activating the MDT configuration of the terminal equipment, receiving the MDT report from the terminal equipment, sending tracking data (or tracking records) to OSS / NMS / OAM or TCE, performing sensing measurements as a sensing transmitter / sensing receiver, and generating sensing results. Terminal equipment can be used for one or more of the following operations: MDT measurement, sending MDT reports to the access network equipment or TCE, performing sensing measurements as a sensing transmitter / sensing receiver, and generating sensing results. In the above system architecture, OSS / NMS / OAM may trigger the collection of sensing results or sensing measurement data due to the needs of MDT or tracking. The data collection node for MDT or tracking is the TCE, and the TCE's address can be stored in the UDM as the terminal equipment's subscription information. The TCE address can also be configured to the access network equipment via OSS / NMS / OAM or sent to the access network equipment by the AMF in the tracking activation message.
[0132] It should be noted that the perception data collection architecture shown in Figure 6 is merely an example of a perception data collection architecture applicable to this application. The embodiments of this application can also be applied to other types of perception data collection architectures. For example, TCE and OSS / NMS / OAM in Figure 6 can be replaced with NWDAF, DCF, or DCCF.
[0133] The following example illustrates the process of collecting sensing data from the perspective of interaction between network elements.
[0134] Figure 7 is a schematic flowchart of a communication method provided in one embodiment of this application. Figure 7 illustrates the interaction between a first network element and a second network element. Both the first and second network elements can be network elements in the core network. For example, the first network element can be a network element for managing sensed services, such as SSMF. The second network element can be a network element for collecting and / or storing service data and / or measurement data. For example, the second network element can be a service data collection network element for non-sensed services, and the service data collected by the second network element includes sensed data. Exemplarily, the second network element can be NWDAF, TCE, DCF, or DCCF.
[0135] Referring to Figure 7, in step S710, the first network element receives a sensing service request. This sensing service request can be initiated by a sensing service consumer. The sensing service consumer can be any type of network element or node that desires to obtain sensing results; for example, it can be a third-party application server or a network element in the core network. The sensing service request can include sensing-related parameters. For example, the sensing service request can include one or more of the following information: the target sensing service area associated with the sensing service request, the sensing time information associated with the sensing service request, the quality of service (QoS) information associated with the sensing service request, the data collection interval information associated with the sensing service request, the triggering event for sensing data collection associated with the sensing service request, and the sensing result (the desired sensing result) associated with the sensing service request.
[0136] In step S720, the first network element receives sensing data matching the sensing service request from the second network element and / or from the sensing receiver associated with the sensing service request. As mentioned earlier, the second network element can be a network element in the core network, such as NWDAF, TCE, DCF, or DCCF. The second network element may also collect sensing data while collecting other service data. The first network element directly obtaining or collecting sensing data from the second network element can effectively utilize existing data, reduce the number of triggers in the sensing process, and thus reduce the consumption of air interface resources.
[0137] Before step S720, in some embodiments, the first network element may first send a first message to the second or third network element (see step S810 in Figure 8). The third network element may be a network element in the core network associated with the second network element. The association between the third and second network elements can mean that the third network element is capable of interacting with the second network element, or that the third network element is capable of controlling the second network element. For example, the third network element may be a network element in the core network used for network management (or a gateway system, which may include one or more of OSS, NSM, and OAM). The first network element may interact with the second or third network element via signaling based on its address. The address of the second or third network element may be pre-configured in the first network element, or the address of the second or third network element may be obtained through network element discovery.
[0138] The first message can be used to request the collection of sensing data matching the sensing service request from the second network element. Taking the architecture shown in Figure 6 as an example, the first network element (SSMF) can directly send the first message to the second network element (TCE) to request the collection of sensing data matching the sensing service request from the second network element, or it can send the first message to the third network element (OSS / NSM / OAM) to request the collection of sensing data matching the sensing service request from the second network element.
[0139] The embodiments of this application do not specifically limit the content of the first message. For example, the first message may include relevant information about the sensing service request, so that the second network element or the third network element can determine whether the second network element has collected or stored sensing data that meets the sensing service request.
[0140] In some embodiments, the first message includes one or more of the following: an identifier of a non-aware service, an identifier of a sensing receiver associated with a sensing service request, a target sensing service area associated with a sensing service request, sensing time information associated with a sensing service request, QoS information associated with a sensing service request, data collection interval information associated with a sensing service request, a triggering event for sensing data collection associated with a sensing service request, and a sensing result (expected sensing result) associated with a sensing service request. One or more of the target sensing service area associated with a sensing service request, sensing time information associated with a sensing service request, QoS information associated with a sensing service request, data collection interval information associated with a sensing service request, triggering event for sensing data collection associated with a sensing service request, and sensing result associated with a sensing service request mentioned above can, for example, be obtained from the sensing service request received in step S710.
[0141] To obtain the identifier of the sensing receiver associated with the sensing service request, the first network element can first select the sensing receiver based on the sensing service request. For example, after receiving the sensing service request through step S710, the first network element executes the sensing transmitter / sensing receiver discovery and selection process to determine the sensing receiver. Then, the first network element sends a first message to the second or third network element, which contains the identifier of the sensing receiver, to confirm with the second or third network element whether the second network element has already collected sensing data for this sensing receiver that conforms to the sensing service request.
[0142] The identifier for non-perceptible services can be used to identify non-perceptible services that contain perceived data. Taking the second network element as TCE as an example, the identifier for non-perceptible services can be a trace reference ID.
[0143] It should be noted that the first message can be a message sent by the first network element to the second or third network element after it first receives a sensing service request. In this case, the first network element may not yet be able to determine which or more non-sensing services can provide the required sensing data. In this case, the first message may not carry the identifier of the non-sensing service. Alternatively, the first message can also be a message sent by the first network element to the second or third network element after it has received a sensing service request and subsequently received the same or similar sensing service requests (such as subsequent sensing service requests that have selected the same sensing receiver). In this case, through previous interactions, the first network element may have already determined which or more of the non-sensing services can provide the required sensing data. In this case, the first message can carry the identifier of the non-sensing service.
[0144] The first message can be either a regular sensing data collection request or a sensing data collection subscription request. For example, for a sensing service request of type one time, the first network element can send a sensing data collection request to the second or third network element. For a sensing service request of type periodic or event-based, the first network element can send a sensing data collection subscription request to the second or third network element.
[0145] After receiving the first message, the second or third network element can send a response message to the first network element (see step S820 in Figure 8). This response message can be used to indicate whether the second network element has sensing data matching the sensing service request. For example, after receiving the first message, the second or third network element can determine whether a matching non-sensing service exists based on the information in the first message and sensing-related parameters in the non-sensing service (taking the second network element as a TCE as an example; the non-sensing service could be, for example, a tracking / MDT session), and reply with a response message to the first network element according to the matching result.
[0146] If the second network element has sensing data that matches the sensing service request, in some embodiments, the response message of the first message may include one or more of the following information: the identifier of the non-sensing service (such as Trace reference ID), the address of the second network element, the data format of the sensing data, the data volume of the sensing data, the sensing data (the second network element or the third network element may send the sensing data directly through the control plane connection), and whether the second network element supports user plane connection or data connection.
[0147] Referring again to step S720 in Figure 7, the first network element can receive sensing data matching the sensing service request from the second network element via a control plane connection. Alternatively, the first network element can also receive sensing data matching the sensing service request from the second network element via a user plane connection or a data connection. Transmitting sensing data via a control plane connection can improve the transmission efficiency of sensing data. Transmitting sensing data via a user plane connection or a data connection can reduce the transmission latency and signaling overhead of sensing data.
[0148] In some embodiments, the first network element may first determine whether to receive sensing data from the second network element via a user plane connection or a data connection. For example, the first network element may determine whether to receive sensing data from the second network element via a user plane connection or a data connection based on one or more of the following information: whether the second network element supports a user plane connection or a data connection, the data format of the sensing data collected by the second network element, the amount of sensing data collected by the second network element, and the local configuration information of the first network element.
[0149] For example, the first network element can first send the aforementioned first message to the second or third network element. Then, the second or third network element can send a response message to the first network element, which may carry one or more of the following: whether the second network element supports user plane connection or data connection, the data format of the sensed data collected by the second network element, and the amount of sensed data collected by the second network element. Then, the first network element can determine whether to receive sensed data from the second network element through user plane connection or data connection based on the above information and / or local configuration information in the response message.
[0150] For example, if the data format of the sensing data collected by the second network element is point cloud or channel matrix, considering that the amount of such sensing data is usually large, the first network element can establish a user plane connection or data connection with the second network element, thereby receiving sensing data from the second network element through the user plane connection or data connection.
[0151] The user plane connection or data connection between the first network element and the second network element can be established by the first network element based on the address of the second network element. The address of the second network element can be provided by the second network element or the third network element when sending a response message to the first message mentioned above. Alternatively, the first network element can pre-configure the address of the second network element.
[0152] It should be noted that in some embodiments, step S720 may be executed under certain conditions. For example, the first network element may first determine whether the second network element has sensing data matching the sensing service request. If the second network element has sensing data matching the sensing service request, the first network element receives the sensing data matching the sensing service request from the second network element. If the second network element does not have sensing data matching the sensing service request, the first network element may receive sensing data from the sensing receiver associated with the sensing service request. For example, the first network element may interact with the second network element or the third network element through the aforementioned first message and its response message. If the response message of the first message indicates that the second network element does not have sensing data matching the sensing service request, the first network element may trigger the sensing transmitter / sensing receiver to perform sensing measurements, thereby collecting sensing data. After the sensing receiver collects the sensing data, the first network element may receive the sensing data from the sensing receiver.
[0153] When a first network element receives sensing data from a sensing receiver associated with a sensing service request, the first network element can receive the sensing data from the sensing receiver via a control plane connection, or via a user plane connection or a data connection. Transmitting sensing data via a user plane connection or a data connection can reduce the transmission latency of the sensing data and effectively avoid the problem of high signaling overhead caused by transmitting sensing data via a control plane connection.
[0154] In some embodiments, the first network element may first determine whether to receive sensing data from the sensing receiver via a user plane connection or a data connection. For example, the first network element may determine whether to receive sensing data from the sensing receiver via a user plane connection or a data connection based on one or more of the following information: whether the sensing receiver supports a user plane connection or a data connection, data volume-related parameters of the sensing data, and local configuration information of the first network element.
[0155] Whether the sensing receiver supports user plane connectivity or data connectivity can also be referred to as the sensing receiver's capability to support user plane connectivity or data connectivity. This capability information can be obtained by the first network element when selecting the sensing receiver. Alternatively, this capability information can be determined by the first network element based on local configuration information. Or, this capability information can be obtained by the first network element through interaction with the sensing receiver.
[0156] The data volume parameters of the sensed data can be used to indicate the size of the sensed data. These parameters may include, for example, one or more of the following: the data format of the sensed data; the sensed service type associated with the sensed service request. The data format of the sensed data can be obtained by the first network element through the sensed service request. Alternatively, the data format of the sensed data can be determined by the first network element based on local configuration information. Alternatively, the data format of the sensed data can be obtained by the first network element interacting with the sensed receiver. The sensed service type can, for example, be obtained from the sensed service request.
[0157] When the first network element determines that it will receive sensing data from the sensing receiver via a control plane connection, the first network element can interact with the sensing transmitter and / or the sensing receiver to trigger a sensing process. The sensing receiver can acquire sensing data through the sensing process and return the sensing data to the first network element via the control plane connection.
[0158] When the first network element determines that it will receive sensing data from the sensing receiver via a user plane connection or a data connection, the first network element can transmit the sensing data through the existing user plane connection or data connection between the first network element and the sensing receiver, or it can establish a new user plane connection or data connection. Furthermore, the first network element can send an instruction message to the sensing receiver, instructing the sensing receiver to transmit the sensing data using the user plane connection or data connection.
[0159] The sensing receiver can be an access network device and / or a terminal device. When the sensing receiver is an access network device, the user plane connection or data connection between the first network element and the sensing receiver is established based on the identifier or address of the access network device (or RAN node). The identifier or address of the access network device can be obtained by the first network element when selecting the sensing receiver, or it can be determined by the first network element's local configuration information.
[0160] When the sensing receiver is a terminal device, the first network element can determine whether an established user plane connection (or PDU session) or data connection (or a sensing-specific user plane connection (or PDU session) or data connection) can be used to transmit sensing data based on parameters in the URSP of the established user plane connection (or PDU session) or data connection between the first network element and the terminal device. The parameters in the URSP mentioned here may include, for example, a traffic descriptor and a route selection description (RSD). The traffic descriptor may indicate the address and / or connectivity capabilities of the first network element (for sensing). The route selection description may include a data network name (DNN) and single network slice selection assistance information (S-NSSAI).
[0161] Alternatively, when the sensing receiver is a terminal device, the first network element can send control plane signaling to the terminal device. This control plane signaling can be used to instruct the terminal device to transmit sensing data via a user plane connection or a data connection. The control plane signaling may include the address of the first network element, such as its Internet Protocol (IP) address or fully qualified domain name (FQDN). This control plane signaling can be used to trigger the terminal device to establish a user plane connection (or PDU session) or a data connection. This user plane connection (or PDU session) or data connection can be a sensing-dedicated user plane connection (or PDU session) or data connection.
[0162] In some embodiments, a first network element may send a sensing service request or a sensing data collection request to a sensing receiver to trigger the sensing receiver to collect sensing data. This sensing service request or sensing data collection request may be transmitted via a control plane connection, or via a user plane and / or data plane connection. Upon receiving the sensing service request, the sensing receiver (e.g., a terminal device) may perform sensing measurements based on the sensing service request or sensing data collection request to obtain sensing data.
[0163] In addition to determining the transmission method of the sensing data (which may include transmission based on a user plane connection, a data connection, or a control plane connection), in some embodiments, the first network element may also determine the transmission method of other messages besides the sensing data between itself and the network element providing the sensing data (such as the second network element or sensing receiver mentioned above). This application does not specifically limit the method for determining the transmission method of these other messages. For example, the first network element can determine the transmission method of the other messages based on the transmission method of the sensing data. That is, the other messages can be transmitted using the same transmission method as the sensing data. As another example, the first network element can determine the transmission method of the other messages based on the QoS information of the sensing service associated with the sensing service request. For example, for sensing services with high latency requirements, a control plane connection can be used for transmission.
[0164] As mentioned earlier, the sensing receiver can be an access network device or a terminal device. When the sensing receiver is a terminal device, the terminal device can transmit sensing data matching the sensing service request through the user plane connection or data connection between the terminal device and the first network element. This user plane connection or data connection can be an existing user plane connection or data connection established by the terminal device, or it can be a newly established user plane connection or data connection established by the terminal device for transmitting the sensing data. The behavior of the terminal device will be illustrated in more detail below.
[0165] In some embodiments, referring to FIG9, in step S910, the terminal device receives control plane signaling sent by the first network element. The control plane signaling instructs the terminal device to transmit sensing data to the first network element via a user plane connection or a data connection. This control plane signaling may, for example, include the address of the first network element.
[0166] After receiving the control plane signaling, the terminal device can establish a user plane connection or a data connection between the terminal device and the first network element based on the address and / or URSP (such as a sensing-related URSP); then, the terminal device can transmit sensing data to the first network element through the user plane connection or the data connection.
[0167] Alternatively, in some embodiments, the terminal device can select a user plane connection or data connection that matches the established user plane connection or data connection between the terminal device and the first network element based on the sensing-related URSP; then, the terminal device transmits sensing data to the first network element through the user plane connection or data connection that matches the URSP.
[0168] The URSP mentioned above can be information obtained by the terminal device from the core network during the registration process. For example, the terminal device sends a registration request to a mobility management element (such as the AMF) in the core network, indicating that the terminal device has the capability to act as a sense receiver. Then, when establishing a policy for the terminal device with a policy control element (such as the PCF) in the core network, the mobility management element in the core network indicates that the terminal device has the capability to act as a sense receiver. The policy control element in the core network can generate a URSP based on this capability of the terminal device and the authorization information of the terminal device as a sense receiver. This URSP can then be transmitted to the terminal device.
[0169] As described above, for a sensing service request, the first network element may collect sensing data from the second network element or from the sensing receiver. For subsequent sensing service requests, if they match previously sent sensing service requests, the first network element can collect sensing data in the same way, regardless of whether the request comes from the same or different sensing service consumers (or sensing service requesters).
[0170] The embodiments of this application will now be described in more detail with reference to Figures 10 and 11. In the examples of Figures 10 and 11, SSFM corresponds to the first network element mentioned above, TCE corresponds to the second network element mentioned above, the management system corresponds to the third network element mentioned above, and UE corresponds to the terminal device mentioned above. It should be noted that the examples of Figures 10 and 11 are merely to help those skilled in the art understand the embodiments of this application, and are not intended to limit the embodiments of this application to the specific values or scenarios illustrated. Those skilled in the art can obviously make various equivalent modifications or changes based on the examples of Figures 10 and 11, and such modifications or changes also fall within the scope of the embodiments of this application.
[0171] Figure 10 is a schematic flowchart of the sensing data collection process provided in an embodiment of this application.
[0172] In step S1002, the MDT / tracking service is activated, and the MDT / tracking measurement data (including sensing data) is reported to the TCE.
[0173] In step S1004, SSMF receives the sensing service request and successfully selects the sensing transmitter / receiver.
[0174] In step S1006 (including steps S1006a and S1006b in Figure 10), SSMF sends a sensing data collection message (which may correspond to the first message mentioned above) to the management system / TCE to request / subscribe to sensing data. This message may include one or more of the following information: the receiver identifier obtained in step S1004, the sensing service area obtained from the sensing service request, the sensing time period obtained from the sensing service request, the QoS requirements obtained from the sensing service request, the sensing time interval obtained from the sensing service request (for the case where the sensing service request is a periodic request), the triggering event obtained from the sensing service request (for the case where the sensing service request is an event-based request), and the sensing result.
[0175] In step S1008 (including steps S1008a and S1008b in Figure 10), the management system / TCE checks whether there is a tracing / MDT session that matches the sensing data service request. If a matching tracing / MDT session is available, the management system / TCE replies to the SSMF with one or more of the following information (which may correspond to the response message of the first message mentioned above): tracing reference identifier, TCE address, sensing data format, sensing data volume, sensing data, and the TCE's ability to support UP / data connection transmission.
[0176] In step S1010, if the SSMF receives information indicating a matching tracking / MDT session (e.g., tracking reference identifier, TCE address, sensing data format, sensing data volume, sensing data), the SSMF collects sensing data from the TCE; otherwise, the SSMF collects sensing data from the sensing receiver (steps S1010 to S1014 are skipped in this case). The SSMF determines whether the sensing data is transmitted via the CP or the UP / data connection based on one or more of the following: sensing data format, sensing data volume, the TCE's UP / data connection capability received in step S1008, the request type received from the sensing service request, and local configuration information.
[0177] In step S1012, if the SSMF decides to transmit data via the UP / data connection, the SSMF checks whether a UP / data connection has already been established with the TCE. If so, this connection is used for sensing data collection; otherwise, the SSMF establishes a UP / data connection to the TCE based on the TCE address obtained in step S1008 or a pre-configured TCE address.
[0178] In step S1014, sensing data is collected between TCE and SSMF. For subsequent sensing service requests that match the current sensing service request, SSMF can still collect sensing data through this connection.
[0179] In step S1016, if the TCE does not have a matching tracking / MDT session, the SSMF can determine whether the sensed data is transmitted between the sensed receiver and the SSMF via a CP or a UP / data connection based on the sensed data format, sensed data volume, the UP / data connection capability of the TCE received from step S1008, the service type received from the sensed service request, and local configuration information.
[0180] In step S1018, if the SSMF decides to transmit data via the UP / data connection, the SSMF checks whether a UP / data connection has already been established with the sensing receiver. If so, this connection is used for sensing data collection; otherwise, the SSMF establishes a UP / data connection to the sensing receiver based on the receiver's identifier / address.
[0181] In step S1020, the SSMF sends a sensing service request to the sensing transmitter and receiver. Depending on the sensing mode, the sensing service request can be sent directly to the sensing receiver or through the sensing transmitter; conversely, the sensing request can also be sent directly to the sensing transmitter or through the sensing receiver. This message can be sent via CP or UP / data connection.
[0182] In step S1022, if there is no ongoing sensing process matching the sensing service request, the sensing transmitter and sensing receiver execute the sensing process.
[0183] In step S1024, sensing data is collected between the sensing receiver and the SSMF. For subsequent sensing service requests that match the current sensing service request, the SSMF can still collect sensing data through this connection.
[0184] Figure 11 is a flowchart of the UP or data connection establishment process of the UE provided in the embodiment of this application.
[0185] In step S1102, during registration, the UE indicates its awareness capability as a receiver in the registration request. The AMF / routing agent forwards this capability to the PCF. Upon receiving the capability, the PCF checks the UE's awareness subscription on the UDR, authorizes the UE to perform awareness as a receiver, and then generates and provides the UE with a URSP.
[0186] In step S1104, SSMF determines that the sensed data is transmitted via the UP / data connection.
[0187] In step S1106, if a secure UP / data connection has not yet been established between the UE and the SSMF, the SSMF sends a Namf_communication_N1N2MessageTransfer message to the AMF, instructing the UE to use the UP / data connection over the Transport Layer Security (TLS) protocol for sensing data collection in the form of a NAS container. The UP / data connection information includes the address of the SSMF.
[0188] In step S1108, when the AMF / routing agent receives the UP / data connection information from the SSMF in step S1106, the AMF / routing agent sends it to the UE via a DL NAS TRANSPORT message.
[0189] In step S1110, if a PDU session / data connection suitable for sensing data collection has not yet been established, the UE establishes a PDU session using URSP. The UE establishes a secure UP / data connection with SSMF.
[0190] In step S1112, the UE sends an acknowledgment message to the SSMF through the AMF / routing agent to indicate whether the UP / data connection was successfully established or cannot be used.
[0191] In step S1114, the AMF / routing agent sends the acknowledgment message received in step S1112 to the SSMF via the Namf_N1messageNotify service.
[0192] In step S1116, the SSMF interacts with the UE to execute the sensing procedure. Messages between the two can be transmitted via the CP or UP / data connection.
[0193] In step S1118, sensing data is collected between the UE and the SSMF. For subsequent sensing service requests that match the current sensing service request, the SSMF can still collect sensing data through this connection.
[0194] This application mainly defines a multi-channel sensing data collection method, which can be applied to 5G, 6G or future communication systems.
[0195] Sensing data collection is an important part of sensing technology and an important component of the common data framework. Therefore, the data collection scheme based on multiple data sources proposed in this application can also be considered as a data collection scheme for the common data framework.
[0196] The method embodiments of this application have been described in detail above with reference to Figures 1 to 11. The apparatus embodiments of this application will be described in detail below with reference to Figures 12 to 16. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the foregoing method embodiments.
[0197] Figure 12 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device 1200 shown in Figure 12 can be the first network element mentioned above. The communication device 1200 includes a communication module 1210. The communication module 1210 is used to receive a sensing service request and receive sensing data matching the sensing service request from a second network element and / or from a sensing receiver associated with the sensing service request; wherein, the second network element is a service data collection network element for non-sensing services, and the service data collected by the second network element includes the sensing data.
[0198] In some embodiments, the communication module 1210 is further configured to: send a first message to the second network element or a third network element associated with the second network element before receiving the sensing data from the second network element and / or from the sensing receiver associated with the sensing service request, the first message being used to request the collection of the sensing data from the second network element.
[0199] In some embodiments, the first message includes one or more of the following: an identifier of the non-perceptual service; an identifier of the perception receiver associated with the perception service request; a target perception service area associated with the perception service request; perception time information associated with the perception service request; QoS information associated with the perception service request; data collection interval information associated with the perception service request; a triggering event for perception data collection associated with the perception service request; and a perception result associated with the perception service request.
[0200] In some embodiments, the communication module 1210 is further configured to: receive a response message of the first message from the second network element or the third network element, wherein the response message of the first message is used to indicate whether the second network element has sensing data that matches the sensing service request.
[0201] In some embodiments, if the second network element has sensing data that matches the sensing service request, the response message of the first message includes one or more of the following information: the identifier of the non-sensing service; the address of the second network element; the data format of the sensing data; the data volume of the sensing data; the sensing data; and whether the second network element supports user plane connection or data connection.
[0202] In some embodiments, the communication module 1210 is configured to receive the sensing data from the second network element via a user plane connection or a data connection.
[0203] In some embodiments, the communication device 1200 further includes: a first determining module, configured to determine, before the first network element receives the sensing data from the second network element via a user plane connection or a data connection, whether to receive the sensing data from the second network element via a user plane connection or a data connection based on one or more of the following information: whether the second network element supports a user plane connection or a data connection; the data format of the sensing data collected by the second network element; the data volume of the sensing data collected by the second network element; and the local configuration information of the first network element.
[0204] In some embodiments, the communication module 1210 is configured to: receive sensing data matching the sensing service request from the second network element if the second network element has sensing data matching the sensing service request; and / or, receive the sensing data from the sensing receiver associated with the sensing service request if the second network element does not have sensing data matching the sensing service request.
[0205] In some embodiments, the communication module 1210 is configured to receive the sensing data from the sensing receiver via a user plane connection or a data connection.
[0206] In some embodiments, the communication device 1200 further includes: a second determining module, configured to determine, before the first network element receives the sensing data from the sensing receiver via a user plane connection or a data connection, whether to receive the sensing data from the sensing receiver via the sensing receiver based on one or more of the following information: whether the sensing receiver supports a user plane connection or a data connection; data volume-related parameters of the sensing data; and local configuration information of the first network element.
[0207] In some embodiments, the data volume-related parameters of the sensing data include one or more of the following: the data format of the sensing data; the sensing service type associated with the sensing service request.
[0208] In some embodiments, the sensing receiver is an access network device, and the user plane connection or data connection is established based on the identifier or address of the access network device.
[0209] In some embodiments, the sensing receiver is a terminal device, and the communication module is further configured to: send control plane signaling to the terminal device, the control plane signaling being used to instruct the terminal device to transmit the sensing data through a user plane connection or a data connection, and / or, the control signaling containing the address of the first network element.
[0210] In some embodiments, the communication module 1210 is further configured to: send a sensing service request or a sensing data collection request to the sensing receiver to trigger the sensing receiver to collect sensing data, wherein the sensing service request is transmitted via a control plane connection, or the sensing service request or the sensing data collection request is transmitted via a user plane and / or a data plane connection.
[0211] In some embodiments, the communication device 1200 further includes: a third determining module, configured to determine, based on one or more of the following information, the transmission mode of other messages besides the sensing data between the first network element and the network element providing the sensing data: the transmission mode of the sensing data, the transmission mode including transmission based on user plane connection, transmission based on data connection, or transmission based on control plane connection; and QoS information of the sensing service associated with the sensing service request.
[0212] In some embodiments, the first network element is a network element in the core network used for managing sensing services; and / or, the second network element is a TCE, DCF, or DCCF.
[0213] Figure 13 is a schematic diagram of a communication device provided in an embodiment of this application. The communication device 1300 shown in Figure 13 can be the second network element mentioned above. The communication device 1300 includes a communication module 1310. The communication module 1310 is used to send sensing data matching the sensing service request to a first network element; wherein, the second network element is a service data collection network element for non-sensing services, and the service data collected by the second network element includes the sensing data.
[0214] In some embodiments, the communication module 1310 is further configured to: receive a first message from the first network element before sending the sensing data to the first network element, the first message being used to request the collection of the sensing data from the second network element.
[0215] In some embodiments, the first message includes one or more of the following: an identifier of the non-perceptual service; an identifier of the perception receiver associated with the perception service request; a target perception service area associated with the perception service request; perception time information associated with the perception service request; QoS information associated with the perception service request; data collection interval information associated with the perception service request; a triggering event for perception data collection associated with the perception service request; and a perception result associated with the perception service request.
[0216] In some embodiments, the communication module 1310 is further configured to: send a response message of the first message to the first network element, wherein the response message of the first message is used to indicate whether the second network element has sensing data that matches the sensing service request.
[0217] In some embodiments, if the second network element has sensing data that matches the sensing service request, the response message of the first message includes one or more of the following information: the identifier of the non-sensing service; the address of the second network element; the data format of the sensing data; the data volume of the sensing data; the sensing data; and whether the second network element supports user plane connection or data connection.
[0218] In some embodiments, the communication module 1310 is used to send the sensing data to the first network element via a user plane connection or a data connection.
[0219] In some embodiments, the transmission method of the sensed data between the first network element and the second network element is determined based on one or more of the following information: whether the second network element supports user plane connection or data connection; the data format of the sensed data collected by the second network element; the data volume of the sensed data collected by the second network element; and the local configuration information of the first network element; wherein the transmission method includes transmission based on user plane connection, transmission based on data connection, or transmission based on control plane connection.
[0220] In some embodiments, the transmission method of messages other than sensing data between the first network element and the second network element is determined based on one or more of the following: the transmission method of the sensing data, which includes transmission based on user plane connection, transmission based on data connection, or transmission based on control plane connection; and the QoS information of the sensing service associated with the sensing service request.
[0221] In some embodiments, the first network element is a network element in the core network used for managing sensing services; and / or, the second network element is a TCE, DCF, or DCCF.
[0222] Figure 14 is a schematic diagram of a communication device provided in an embodiment of this application. The communication device 1400 shown in Figure 14 can be the third network element mentioned above. The communication device 1400 includes a communication module 1410. The communication module 1410 is used to receive a first message sent by a first network element, the first message being used to request the collection of sensing data from a second network element associated with the third network element; wherein, the second network element is a service data collection network element for non-sensing services, and the service data collected by the second network element includes the sensing data.
[0223] In some embodiments, the first message includes one or more of the following: an identifier of the non-perceptual service; an identifier of the perception receiver associated with the perception service request; a target perception service area associated with the perception service request; perception time information associated with the perception service request; QoS information associated with the perception service request; data collection interval information associated with the perception service request; a triggering event for perception data collection associated with the perception service request; and a perception result associated with the perception service request.
[0224] In some embodiments, the communication module 1410 is further configured to: send a response message of the first message to the first network element, wherein the response message of the first message is used to indicate whether the second network element has sensing data that matches the sensing service request.
[0225] In some embodiments, if the second network element has sensing data that matches the sensing service request, the response message of the first message includes one or more of the following information: the identifier of the non-sensing service; the address of the second network element; the data format of the sensing data; the data volume of the sensing data; the sensing data; and whether the second network element supports user plane connection or data connection.
[0226] In some embodiments, the first network element is a network element in the core network used for managing sensing services; and / or, the second network element is a TCE, DCF, or DCCF; and / or, the third network element is a network element in the core network used for network management.
[0227] Figure 15 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device 1500 shown in Figure 15 can be the terminal device mentioned above. The communication device 1500 includes a communication module 1510. The communication module 1510 is used to receive control plane signaling sent by a first network element, the control plane signaling being used to instruct the terminal device to transmit sensing data to the first network element through a user plane connection or a data connection.
[0228] In some embodiments, the control plane signaling includes the address of the first network element, and the communication device 1500 further includes: a first processing module, configured to establish the user plane connection or data connection between the terminal device and the first network element based on the address of the first network element and / or the sensing-related URSP; the communication module 1510 is further configured to: transmit the sensing data to the first network element through the user plane connection or data connection.
[0229] In some embodiments, the communication device 1500 further includes: a second processing module, configured to select a user plane connection or data connection matching the URSP from the established user plane connection or data connection between the terminal device and the first network element according to the sensing-related URSP; the communication module 1510 is further configured to: transmit the sensing data to the first network element through the user plane connection or data connection matching the URSP.
[0230] In some embodiments, the communication module 1510 is further configured to: send a registration request to a network element in the core network, the registration request being used to indicate that the terminal device has the capability to act as a sensing receiver.
[0231] In some embodiments, the communication module 1510 is further configured to: receive sensing-related URSPs from network elements in the core network.
[0232] In some embodiments, the communication module 1510 is further configured to: receive a sensing service request or a sensing data collection request sent by the first network element, wherein the sensing service request or sensing data collection request is transmitted via a control plane connection, or the sensing service request or sensing data collection request is transmitted via a user plane and / or a data plane connection; the terminal device 1500 further includes: a measurement module, configured to perform sensing measurements according to the sensing service request or sensing data collection request.
[0233] In some embodiments, the terminal device is a sensing receiver.
[0234] In some embodiments, the first network element is a network element in the core network used for managing sensing services.
[0235] Figure 16 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 16 indicate that the unit or module is optional. This device 1600 can be used to implement the methods described in the above method embodiments. Device 1600 can be a chip, a terminal device, or a network device.
[0236] Apparatus 1600 may include one or more processors 1610. The processor 1610 may support apparatus 1600 in implementing the methods described in the preceding method embodiments. The processor 1610 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 other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.
[0237] The apparatus 1600 may further include one or more memories 1620. The memories 1620 store a program that can be executed by the processor 1610, causing the processor 1610 to perform the methods described in the preceding method embodiments. The memories 1620 may be independent of the processor 1610 or integrated within the processor 1610.
[0238] The device 1600 may also include a transceiver 1630. The processor 1610 can communicate with other devices or chips via the transceiver 1630. For example, the processor 1610 can send and receive data with other devices or chips via the transceiver 1630.
[0239] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to the communication device provided in this application, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.
[0240] This 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 this application embodiment, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.
[0241] This application also provides a computer program. This computer program can be applied to the communication device provided in this application, and causes the computer to execute the methods performed by the communication device in various embodiments of this application.
[0242] It should be understood that the terminology used in this application is only for explaining specific embodiments of this application and is not intended to limit this application. The terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.
[0243] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.
[0244] In the embodiments of this 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 that B is determined solely based on A; B can also be determined based on A and / or other information.
[0245] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.
[0246] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.
[0247] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.
[0248] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.
[0249] In the various embodiments of this application, the order of the above-mentioned processes does not imply 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 this application.
[0250] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0251] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0252] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0253] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially 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, all or part of the processes or functions described in the embodiments of this application are generated. 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. 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 wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.
[0254] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A communication method, characterized in that, include: The first network element receives sensing service requests; The first network element receives sensing data matching the sensing service request from the second network element and / or from the sensing receiver associated with the sensing service request; The second network element is a service data collection network element for non-perceptual services, and the service data collected by the second network element includes the perceived data.
2. The method according to claim 1, characterized in that, The method further includes: Before receiving the sensing data from the second network element and / or from the sensing receiver associated with the sensing service request, the first network element sends a first message to the second network element or a third network element associated with the second network element, the first message being used to request the collection of the sensing data from the second network element.
3. The method according to claim 2, characterized in that, The first message includes one or more of the following: The identifier of the non-perceptible service; The identifier of the sensing receiver associated with the sensing service request; The target sensing service area associated with the sensing service request. The sensing time information associated with the sensing service request; The Quality of Service (QoS) information associated with the perceived service request; The data collection interval information associated with the sensing service request; The triggering event for the collection of sensing data associated with the sensing service request; The perception result associated with the perception service request.
4. The method according to claim 2 or 3, characterized in that, The method further includes: The first network element receives a response message to the first message from the second network element or the third network element. The response message to the first message is used to indicate whether the second network element has sensing data that matches the sensing service request.
5. The method according to claim 4, characterized in that, If the second network element has sensing data that matches the sensing service request, then the response message of the first message includes one or more of the following information: The identifier of the non-perceptible service; The address of the second network element; The data format of the sensed data; The amount of data in the sensed data; The perceived data; Does the second network element support user plane connection or data connection? 6. The method according to any one of claims 1 to 5, characterized in that, The first network element receives sensing data matching the sensing service request from the second network element, including: The first network element receives the sensing data from the second network element through a user plane connection or a data connection.
7. The method according to claim 6, characterized in that, Before the first network element receives the sensed data from the second network element via a user plane connection or a data connection, the method further includes: The first network element determines whether to receive the sensed data from the second network element via a user plane connection or a data connection based on one or more of the following information: Does the second network element support user plane connectivity or data connectivity? The data format of the sensing data collected by the second network element; The amount of data collected by the second network element from the sensed data; The local configuration information of the first network element.
8. The method according to any one of claims 1 to 7, characterized in that, The first network element receives sensing data matching the sensing service request from the second network element and / or from the sensing receiver associated with the sensing service request, including: If the second network element has sensing data that matches the sensing service request, then the first network element receives the sensing data that matches the sensing service request from the second network element; and / or, If the second network element does not have sensing data that matches the sensing service request, then the first network element receives the sensing data from the sensing receiver associated with the sensing service request.
9. The method according to claim 8, characterized in that, The first network element receives the sensing data from the sensing receiver associated with the sensing service request, including: The first network element receives the sensing data from the sensing receiver via a user plane connection or a data connection.
10. The method according to claim 9, characterized in that, Before the first network element receives the sensing data from the sensing receiver via a user plane connection or data connection, the method further includes: The first network element determines whether to receive the sensed data from the sensed receiver via the user plane connection or data connection based on one or more of the following information: Does the sensing receiver support user plane connectivity or data connectivity? The data volume-related parameters of the sensed data; The local configuration information of the first network element.
11. The method according to claim 10, characterized in that, The data volume-related parameters of the sensed data include one or more of the following: The data format of the sensed data; The sensing service type associated with the sensing service request.
12. The method according to any one of claims 9 to 11, characterized in that, The sensing receiver is an access network device, and the user plane connection or data connection is established based on the identifier or address of the access network device.
13. The method according to any one of claims 9 to 11, characterized in that, The sensing receiver is a terminal device, and the method further includes: The first network element sends control plane signaling to the terminal device. The control plane signaling is used to instruct the terminal device to transmit the sensing data through a user plane connection or a data connection, and / or the control signaling includes the address of the first network element.
14. The method according to any one of claims 8 to 13, characterized in that, The method further includes: The first network element sends a sensing service request or a sensing data collection request to the sensing receiver to trigger the sensing receiver to perform measurements for collecting sensing data. The sensing service request or sensing data collection request is transmitted through a control plane connection, or the sensing service request or sensing data collection request is transmitted through a user plane and / or a data plane connection.
15. The method according to any one of claims 1 to 14, characterized in that, The method further includes: The first network element determines the transmission mode of messages other than the sensing data between itself and the network element providing the sensing data based on one or more of the following information: The transmission method of the sensed data includes transmission based on user plane connection, transmission based on data connection, or transmission based on control plane connection. The QoS information of the sensing service associated with the sensing service request.
16. The method according to any one of claims 1 to 15, characterized in that: The first network element is a network element in the core network used for managing sensing services; and / or, The second network element is the tracking and collection entity (TCE), data collection function (DCF), or data collection coordination function (DCCF).
17. A communication method, characterized in that, include: The second network element sends the sensing data matching the sensing service request to the first network element; The second network element is a service data collection network element for non-perceptual services, and the service data collected by the second network element includes the perceived data.
18. The method according to claim 17, characterized in that, The method further includes: Before sending the sensing data to the first network element, the second network element receives a first message from the first network element, the first message being used to request the collection of the sensing data from the second network element.
19. The method according to claim 18, characterized in that, The first message includes one or more of the following: The identifier of the non-perceptible service; The identifier of the sensing receiver associated with the sensing service request; The target sensing service area associated with the sensing service request. The sensing time information associated with the sensing service request; The Quality of Service (QoS) information associated with the perceived service request; The data collection interval information associated with the sensing service request; The triggering event for the collection of sensing data associated with the sensing service request; The perception result associated with the perception service request.
20. The method according to claim 18 or 19, characterized in that, The method further includes: The second network element sends a response message to the first network element for the first message. The response message to the first message is used to indicate whether the second network element has sensing data that matches the sensing service request.
21. The method according to claim 20, characterized in that, If the second network element has sensing data that matches the sensing service request, then the response message of the first message includes one or more of the following information: The identifier of the non-perceptible service; The address of the second network element; The data format of the sensed data; The amount of data in the sensed data; The perceived data; Does the second network element support user plane connection or data connection? 22. The method according to any one of claims 17 to 21, characterized in that, The second network element sends sensing data matching the sensing service request to the first network element, including: The second network element sends the sensing data to the first network element through a user plane connection or a data connection.
23. The method according to any one of claims 17 to 22, characterized in that, The transmission method of the sensed data between the first network element and the second network element is determined based on one or more of the following information: Does the second network element support user plane connectivity or data connectivity? The data format of the sensing data collected by the second network element; The amount of data collected by the second network element from the sensed data; The local configuration information of the first network element; The transmission methods include transmission based on user plane connection, transmission based on data connection, or transmission based on control plane connection.
24. The method according to any one of claims 17 to 23, characterized in that, The transmission method of messages other than sensing data between the first network element and the second network element is determined based on one or more of the following: The transmission method of the sensed data includes transmission based on user plane connection, transmission based on data connection, or transmission based on control plane connection. The QoS information of the sensing service associated with the sensing service request.
25. The method according to any one of claims 17 to 24, characterized in that: The first network element is a network element in the core network used for managing sensing services; and / or, The second network element is the tracking and collection entity (TCE), data collection function (DCF), or data collection coordination function (DCCF).
26. A communication method, characterized in that, include: The third network element receives a first message sent by the first network element, the first message being used to request the collection of sensing data from the second network element associated with the third network element; The second network element is a service data collection network element for non-perceptual services, and the service data collected by the second network element includes the perceived data.
27. The method according to claim 26, characterized in that, The first message includes one or more of the following: The identifier of the non-perceptible service; The identifier of the sensing receiver associated with the sensing service request; The target sensing service area associated with the sensing service request. The sensing time information associated with the sensing service request; The Quality of Service (QoS) information associated with the perceived service request; The data collection interval information associated with the sensing service request; The triggering event for the collection of sensing data associated with the sensing service request; The perception result associated with the perception service request.
28. The method according to claim 26 or 27, characterized in that, The method further includes: The third network element sends a response message to the first network element for the first message. The response message to the first message is used to indicate whether the second network element has sensing data that matches the sensing service request.
29. The method according to claim 28, characterized in that, If the second network element has sensing data that matches the sensing service request, then the response message of the first message includes one or more of the following information: The identifier of the non-perceptible service; The address of the second network element; The data format of the sensed data; The amount of data in the sensed data; The perceived data; Does the second network element support user plane connection or data connection? 30. The method according to any one of claims 26 to 29, characterized in that: The first network element is a network element in the core network used for managing sensing services; and / or, The second network element is the tracking and collection entity (TCE), data collection function (DCF), or data collection coordination function (DCCF). And / or, The third network element is a network element in the core network used for network management.
31. A communication method, characterized in that, include: The terminal device receives control plane signaling sent by the first network element. The control plane signaling is used to instruct the terminal device to transmit sensing data to the first network element through a user plane connection or a data connection.
32. The method according to claim 31, characterized in that, The control plane signaling includes the address of the first network element, and the method further includes: The terminal device establishes the user plane connection or data connection between the terminal device and the first network element based on the address of the first network element and / or the user equipment routing selection policy (URSP) related to perception. The terminal device transmits the sensing data to the first network element through the user plane connection or data connection.
33. The method according to claim 31, characterized in that, The method further includes: The terminal device selects a user plane connection or data connection that matches the URSP from the established user plane connections or data connections between the terminal device and the first network element, based on the perception-related URSP. The terminal device transmits the sensing data to the first network element through a user plane connection or data connection that matches the URSP.
34. The method according to any one of claims 31 to 33, characterized in that, The method further includes: The terminal device sends a registration request to a network element in the core network, the registration request indicating that the terminal device has the capability to act as a sensing receiver; and / or The terminal device receives perception-related URSPs from network elements in the core network.
35. The method according to any one of claims 31 to 34, characterized in that, The method further includes: The terminal device receives a sensing service request or a sensing data collection request sent by the first network element. The sensing service request or sensing data collection request is transmitted through a control plane connection, or the sensing service request or sensing data collection request is transmitted through a user plane and / or a data plane connection. The terminal device performs sensing measurements based on the sensing service request or sensing data collection request.
36. The method according to any one of claims 31 to 35, characterized in that, The terminal device is a sensing receiver.
37. The method according to any one of claims 31 to 36, characterized in that, The first network element is a network element in the core network used for managing sensing services.
38. A communication device, characterized in that, The communication device is a first network element, and the communication device includes: A communication module is used to receive a sensing service request and receive sensing data matching the sensing service request from a second network element and / or from a sensing receiver associated with the sensing service request. The second network element is a service data collection network element for non-perceptual services, and the service data collected by the second network element includes the perceived data.
39. The communication device according to claim 38, characterized in that, The communication module is also used for: Before receiving the sensing data from the second network element and / or from the sensing receiver associated with the sensing service request, a first message is sent to the second network element or a third network element associated with the second network element. The first message is used to request the collection of the sensing data from the second network element.
40. The communication device according to claim 39, characterized in that, The first message includes one or more of the following: The identifier of the non-perceptible service; The identifier of the sensing receiver associated with the sensing service request; The target sensing service area associated with the sensing service request. The sensing time information associated with the sensing service request; The Quality of Service (QoS) information associated with the perceived service request; The data collection interval information associated with the sensing service request; The triggering event for the collection of sensing data associated with the sensing service request; The perception result associated with the perception service request.
41. The communication device according to claim 39 or 40, characterized in that, The communication module is also used for: The response message to the first message is received from the second network element or the third network element. The response message to the first message is used to indicate whether the second network element has sensing data that matches the sensing service request.
42. The communication device according to claim 41, characterized in that, If the second network element has sensing data that matches the sensing service request, then the response message of the first message includes one or more of the following information: The identifier of the non-perceptible service; The address of the second network element; The data format of the sensed data; The amount of data in the sensed data; The perceived data; Does the second network element support user plane connection or data connection? 43. The communication device according to any one of claims 38 to 42, characterized in that, The communication module is used for: The sensed data is received from the second network element via a user plane connection or a data connection.
44. The communication device according to claim 43, characterized in that, The communication device also includes: The first determining module is configured to determine, before the first network element receives the sensing data from the second network element via a user plane connection or a data connection, whether to receive the sensing data from the second network element via a user plane connection or a data connection based on one or more of the following information: Does the second network element support user plane connectivity or data connectivity? The data format of the sensing data collected by the second network element; The amount of data collected by the second network element from the sensed data; The local configuration information of the first network element.
45. The communication device according to any one of claims 38 to 44, characterized in that, The communication module is used for: If the second network element contains sensing data that matches the sensing service request, then the sensing data matching the sensing service request is received from the second network element; and / or, If the second network element does not have sensing data that matches the sensing service request, it receives the sensing data from the sensing receiver associated with the sensing service request.
46. The communication device according to claim 45, characterized in that, The communication module is used for: The sensing data is received from the sensing receiver via a user plane connection or a data connection.
47. The communication device according to claim 46, characterized in that, The communication device also includes: The second determining module is configured to determine, before the first network element receives the sensing data from the sensing receiver via the user plane connection or data connection, whether to receive the sensing data from the sensing receiver via the user plane connection or data connection based on one or more of the following information: Does the sensing receiver support user plane connectivity or data connectivity? The data volume-related parameters of the sensed data; The local configuration information of the first network element.
48. The communication device according to claim 47, characterized in that, The data volume-related parameters of the sensed data include one or more of the following: The data format of the sensed data; The sensing service type associated with the sensing service request.
49. The communication device according to any one of claims 46 to 48, characterized in that, The sensing receiver is an access network device, and the user plane connection or data connection is established based on the identifier or address of the access network device.
50. The communication device according to any one of claims 46 to 48, characterized in that, The sensing receiver is a terminal device, and the communication module is further configured to: send control plane signaling to the terminal device, the control plane signaling being used to instruct the terminal device to transmit the sensing data through a user plane connection or a data connection, and / or, the control signaling containing the address of the first network element.
51. The communication device according to any one of claims 45 to 50, characterized in that, The communication module is also used for: A sensing service request or sensing data collection request is sent to the sensing receiver to trigger the sensing receiver to collect sensing data. The sensing service request or sensing data collection request is transmitted through a control plane connection, or the sensing service request or sensing data collection request is transmitted through a user plane and / or a data plane connection.
52. The communication device according to any one of claims 38 to 51, characterized in that, The communication device also includes: The third determining module is used to determine the transmission mode of messages other than the sensing data between the first network element and the network element providing the sensing data based on one or more of the following information: The transmission method of the sensed data includes transmission based on user plane connection, transmission based on data connection, or transmission based on control plane connection. The QoS information of the sensing service associated with the sensing service request.
53. The communication device according to any one of claims 38 to 52, characterized in that: The first network element is a network element in the core network used for managing sensing services; and / or, The second network element is the tracking and collection entity (TCE), data collection function (DCF), or data collection coordination function (DCCF).
54. A communication device, characterized in that, The communication device is a second network element, and the communication device includes: The communication module is used to send sensing data matching the sensing service request to the first network element; The second network element is a service data collection network element for non-perceptual services, and the service data collected by the second network element includes the perceived data.
55. The communication device according to claim 54, characterized in that, The communication module is also used for: Before sending the sensing data to the first network element, a first message is received from the first network element, the first message being used to request the collection of the sensing data from the second network element.
56. The communication device according to claim 55, characterized in that, The first message includes one or more of the following: The identifier of the non-perceptible service; The identifier of the sensing receiver associated with the sensing service request; The target sensing service area associated with the sensing service request. The sensing time information associated with the sensing service request; The Quality of Service (QoS) information associated with the perceived service request; The data collection interval information associated with the sensing service request; The triggering event for the collection of sensing data associated with the sensing service request; The perception result associated with the perception service request.
57. The communication device according to claim 55 or 56, characterized in that, The communication module is also used for: A response message to the first message is sent to the first network element. The response message to the first message is used to indicate whether the second network element has sensing data that matches the sensing service request.
58. The communication device according to claim 57, characterized in that, If the second network element has sensing data that matches the sensing service request, then the response message of the first message includes one or more of the following information: The identifier of the non-perceptible service; The address of the second network element; The data format of the sensed data; The amount of data in the sensed data; The perceived data; Does the second network element support user plane connection or data connection? 59. The communication device according to any one of claims 54 to 58, characterized in that, The communication module is used for: The sensing data is sent to the first network element via a user plane connection or a data connection.
60. The communication device according to any one of claims 54 to 59, characterized in that, The transmission method of the sensed data between the first network element and the second network element is determined based on one or more of the following information: Does the second network element support user plane connectivity or data connectivity? The data format of the sensing data collected by the second network element; The amount of data collected by the second network element from the sensed data; The local configuration information of the first network element; The transmission methods include transmission based on user plane connection, transmission based on data connection, or transmission based on control plane connection.
61. The communication device according to any one of claims 54 to 60, characterized in that, The transmission method of messages other than sensing data between the first network element and the second network element is determined based on one or more of the following: The transmission method of the sensed data includes transmission based on user plane connection, transmission based on data connection, or transmission based on control plane connection. The QoS information of the sensing service associated with the sensing service request.
62. The communication device according to any one of claims 54 to 61, characterized in that: The first network element is a network element in the core network used for managing sensing services; and / or, The second network element is the tracking and collection entity (TCE), data collection function (DCF), or data collection coordination function (DCCF).
63. A communication device, characterized in that, The communication device is a third network element, and the communication device includes: The communication module is used to receive a first message sent by the first network element, the first message being used to request the collection of sensing data from the second network element associated with the third network element; The second network element is a service data collection network element for non-perceptual services, and the service data collected by the second network element includes the perceived data.
64. The communication device according to claim 63, characterized in that, The first message includes one or more of the following: The identifier of the non-perceptible service; The identifier of the sensing receiver associated with the sensing service request; The target sensing service area associated with the sensing service request. The sensing time information associated with the sensing service request; The Quality of Service (QoS) information associated with the perceived service request; The data collection interval information associated with the sensing service request; The triggering event for the collection of sensing data associated with the sensing service request; The perception result associated with the perception service request.
65. The communication device according to claim 63 or 64, characterized in that, The communication module is also used for: A response message to the first message is sent to the first network element. The response message to the first message is used to indicate whether the second network element has sensing data that matches the sensing service request.
66. The communication device according to claim 65, characterized in that, If the second network element has sensing data that matches the sensing service request, then the response message of the first message includes one or more of the following information: The identifier of the non-perceptible service; The address of the second network element; The data format of the sensed data; The amount of data in the sensed data; The perceived data; Does the second network element support user plane connection or data connection? 67. The communication device according to any one of claims 63 to 66, characterized in that: The first network element is a network element in the core network used for managing sensing services; and / or, The second network element is the tracking and collection entity (TCE), data collection function (DCF), or data collection coordination function (DCCF). And / or, The third network element is a network element in the core network used for network management.
68. A communication device, characterized in that, The communication device is a terminal device, and the communication device includes: The communication module is used to receive control plane signaling sent by the first network element. The control plane signaling is used to instruct the terminal device to transmit sensing data to the first network element through a user plane connection or a data connection.
69. The communication device according to claim 68, characterized in that, The control plane signaling includes the address of the first network element, and the communication device further includes: The first processing module is used to establish the user plane connection or data connection between the terminal device and the first network element based on the address of the first network element and / or the user equipment routing selection policy (URSP) related to perception. The communication module is also used to transmit the sensing data to the first network element through the user plane connection or data connection.
70. The communication device according to claim 68, characterized in that, The communication device also includes: The second processing module is used to select a user plane connection or data connection that matches the URSP from the established user plane connection or data connection between the terminal device and the first network element, based on the perception-related URSP. The communication module is also used to transmit the sensing data to the first network element through a user plane connection or data connection matched with the URSP.
71. The communication device according to any one of claims 68 to 70, characterized in that, The communication module is also used for: Sending a registration request to network elements in the core network, the registration request indicating that the terminal device has the capability to act as a sensing receiver; and / or, Receive sensing-related URSPs from network elements in the core network.
72. The method according to any one of claims 68 to 71, characterized in that, The communication module is also used for: The network receives a sensing service request or a sensing data collection request sent by the first network element. The sensing service request is transmitted through a control plane connection, or the sensing service request or the sensing data collection request is transmitted through a user plane and / or a data plane connection. The terminal device also includes: The measurement module is used to perform sensing measurements based on the sensing service request or sensing data collection request.
73. The communication device according to any one of claims 68 to 72, characterized in that, The terminal device is a sensing receiver.
74. The communication device according to any one of claims 68 to 73, characterized in that, The first network element is a network element in the core network used for managing sensing services.
75. A communication device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals to cause the communication device to perform the method as described in any one of claims 1 to 16, 17 to 25, 26 to 30, or 31 to 37.
76. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1 to 16, 17 to 25, 26 to 30, or 31 to 37.
77. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 16, 17 to 25, 26 to 30, or 31 to 37.
78. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1 to 16, 17 to 25, 26 to 30, or 31 to 37.
79. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1 to 16, 17 to 25, 26 to 30, or 31 to 37.
80. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1 to 16, 17 to 25, 26 to 30, or 31 to 37.
