Data transmission methods and apparatuses, and communication devices
By transmitting perceived data of perceived services in the container, the problem of customized perceived services in the prior art is solved, and flexible and efficient transmission of perceived data is achieved to meet the customized needs of operators or manufacturers.
Patent Information
- Application Number
- PCT/CN2024/090250
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-04
- Filing Date
- 2024-04-28
- Publication Date
- 2024-11-07
AI Technical Summary
The existing wireless access network standards only support perceived data transmission for specific perceived services, and fail to effectively solve the perceived data transmission problem of customized perceived services.
By transmitting perceived data of perceived services in containers, the container is used to realize the transmission of perceived data when the operator or manufacturer customizes the requirements, including carrying the container in IP packets, GTP packets, NRSP packets or NAS messages, supporting universal and additional perceptions Transmission of measurement volume.
It realizes the effective transmission of customized perceived service perceived data, meets the customized needs of operators or manufacturers, and improves the flexibility and efficiency of perceived data transmission.
Smart Images

Figure CN2024090250_07112024_PF_FP_ABST
Abstract
Description
Data transmission method, device and communication equipment
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to Chinese Patent Application No. 202310491030.6 filed in China on May 4, 2023, the entire contents of which are incorporated herein by reference. Technical Field
[0003] The present application belongs to the field of communication technology, and specifically relates to a data transmission method, apparatus and communication equipment. Background Art
[0004] The 3rd Generation Partnership Project (3GPP) standard is responsible for standardizing the transmission of sensing data between the Radio Access Network (RAN) and the Sensing Function (SF), specifically how to transmit specific sensing data using specific parameters. Currently, 3GPP only supports standardization for the transmission of sensing data for specific sensing services. This means that related technical solutions can only transmit sensing data for specific sensing services. There are no solutions for transmitting sensing data for customized sensing services other than these specific services.
[0005] Summary of the Invention
[0006] The embodiments of the present application provide a data transmission method, apparatus, and communication equipment, which can solve the problem of how to transmit perception data of customized perception services.
[0007] In a first aspect, a data transmission method is provided, comprising:
[0008] The first device sends a container to the second device, where the container includes perception data of a perception service.
[0009] In a second aspect, a data transmission method is provided, comprising:
[0010] The second device obtains the container sent by the first device, where the container includes perception data of the perception service.
[0011] In a third aspect, a data transmission device is provided, comprising:
[0012] The first sending module is configured to send a container to the second device, where the container includes perception data of the perception service.
[0013] In a fourth aspect, a data transmission device is provided, comprising:
[0014] The first acquisition module is configured to acquire a container sent by a first device, where the container includes perception data of a perception service.
[0015] In the fifth aspect, a first device (terminal or network side device) is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.
[0016] In a sixth aspect, a first device (terminal or network side device) is provided, comprising a processor and a communication interface, wherein the communication interface is used to send a container to a second device, wherein the container includes perception data of a perception service.
[0017] In the seventh aspect, a second device (network side device) is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.
[0018] In an eighth aspect, a second device (network side device) is provided, comprising a processor and a communication interface, wherein the communication interface is used to obtain a container sent by the first device, wherein the container includes perception data of the perception service.
[0019] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.
[0020] In the tenth aspect, a data transmission system is provided, comprising: a first device and a second device, wherein the first device can be used to execute the steps of the method described in the first aspect, and the second device can be used to execute the steps of the method described in the second aspect.
[0021] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.
[0022] In a twelfth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a storage medium and is executed by at least one processor to implement the steps of the method described in the first aspect or the second aspect.
[0023] In an embodiment of the present application, a first device sends a container containing sensory data for a sensory service to a second device. This solution enables the transmission of sensory data corresponding to a sensory service that meets the customized requirements of an operator or manufacturer through the container. BRIEF DESCRIPTION OF THE DRAWINGS
[0024] FIG1 is a structural diagram of a communication system applicable to embodiments of the present application;
[0025] FIG2 is a schematic diagram showing a transmission architecture of sensing data;
[0026] FIG3 is a schematic diagram showing a flow chart of a data transmission method according to an embodiment of the present application;
[0027] FIG4 shows one interactive schematic diagram of the data transmission method according to an embodiment of the present application;
[0028] FIG5 shows a second interactive diagram of the data transmission method according to an embodiment of the present application;
[0029] FIG6 shows a second flow chart of the data transmission method according to an embodiment of the present application;
[0030] FIG7 shows one of the module schematic diagrams of the data transmission device according to an embodiment of the present application;
[0031] FIG8 shows a second module schematic diagram of the data transmission device according to an embodiment of the present application;
[0032] FIG9 is a block diagram showing a structure of a communication device according to an embodiment of the present application;
[0033] FIG10 is a block diagram showing a structure of a terminal according to an embodiment of the present application;
[0034] FIG11 shows one structural block diagram of a network side device according to an embodiment of the present application;
[0035] FIG12 shows a second structural block diagram of the network side device according to an embodiment of the present application. DETAILED DESCRIPTION
[0036] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.
[0037] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.
[0038] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.
[0039] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.
[0040] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. In addition to the above-mentioned terminal devices, it can also be a chip in the terminal, such as a modem chip, a system-on-chip (SoC). It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.
[0041] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.
[0042] In order to enable those skilled in the art to better understand the embodiments of the present application, the following description is now provided.
[0043] 1. Communication and perception integration / synaesthesia integration;
[0044] Among related technologies, wireless communications and radar sensing (C&S) have been developing in parallel, but with limited overlap. They share many commonalities in signal processing algorithms, equipment, and, to a certain extent, system architecture. In recent years, the coexistence, collaboration, and joint design of these two systems have attracted increasing research attention.
[0045] Early research on the coexistence of communication and radar systems has focused on developing effective interference management techniques to enable the two separately deployed systems to operate smoothly without interfering with each other. While radar and communication systems may be co-located or even physically integrated, they transmit distinct signals in the time / frequency domain. They collaborate to share the same resources to minimize interference caused by their simultaneous operation. Appropriate measures include beamforming, cooperative spectrum sharing, primary / secondary spectrum sharing, and dynamic coexistence. However, effective interference mitigation typically places strict demands on node mobility and information exchange between nodes, resulting in limited improvements in spectrum efficiency. Since interference in coexisting systems arises from transmitting two independent signals, it's natural to ask whether a single transmitted signal can be used for both communication and radar sensing. Radar systems typically use specially designed waveforms, such as short pulses and chirps, to achieve high power radiation and simplify receiver processing. However, these waveforms are not essential for radar detection. Passive radar or passive sensing, which uses different radio signals as sensing signals, is a good example.
[0046] Machine learning, particularly deep learning, has further advanced the potential of using non-dedicated radio signals for radar sensing. With these technologies, traditional radar is evolving towards more general wireless sensing. Wireless sensing here broadly refers to retrieving information from received radio signals, rather than the communication data modulated into the signal at the transmitter. For wireless sensing related to target location, common signal processing methods can be used to estimate dynamic parameters such as target signal reflection delay, angle of arrival (AoA), angle of departure (AoD), and Doppler. For sensing target physical characteristics, this can be achieved by measuring the inherent pattern signals of devices, objects, and living things. These two sensing methods can be referred to as perception parameter estimation and pattern recognition, respectively. In this sense, wireless sensing refers to more general sensing technologies and applications using radio signals.
[0047] Integrated Sensing and Communication (ISAC) has the potential to integrate wireless sensing into large-scale mobile networks, creating perceptive mobile networks (PMNs). PMNs can evolve from current fifth-generation (5G) mobile networks and are expected to become ubiquitous wireless sensor networks while also providing stable, high-quality mobile communication services. They can be built on the existing mobile network infrastructure of related technologies without requiring major changes to network structure and equipment. This will unleash the maximum capacity of mobile networks and avoid the high infrastructure costs of building new, separate wide-area wireless sensor networks. With expanded coverage, the combined communication and sensing capabilities are expected to enable numerous new applications. Perceptive mobile networks can simultaneously provide both communication and wireless sensing services, and due to their wide broadband coverage and robust infrastructure, they have the potential to become a ubiquitous wireless sensing solution. Their combined coordinated communication and sensing capabilities will enhance productivity and enable a wide range of new applications that cannot be effectively implemented with sensor networks based on related technologies. Early work on passive sensing using mobile signals has demonstrated its potential. Examples include traffic monitoring, weather forecasting, and rainfall remote sensing based on Global System for Mobile Communications (GSM) radio signals. Sensing mobile networks can be widely applied to communications and sensing in transportation, communications, energy, precision agriculture, and security, where related technology solutions are either infeasible or inefficient. They can also provide complementary sensing capabilities to related technology sensor networks, with unique day and night operation capabilities and the ability to penetrate fog, foliage, and even solid objects.
[0048] 2. Data transmission method for synaesthesia service;
[0049] In the architecture shown in Figure 2, the Sensing Function (SF) is a new network element added to the synaesthesia service, responsible for managing the synaesthesia service and processing synaesthesia data. The SF can be a single network element, responsible for both the user plane and the control plane; or it can be two network elements, with the Sensing Function Control Plane (SF-C) and the Sensing Function User Plane (SF-U) separated. For example, sensing measurements include latency, Doppler, angle, intensity, and their multi-dimensional combinations. The Sensing Result is the result obtained after the SF processes the Sensing Measurement, such as intermediate processing results such as speed, distance, direction, acceleration, position, trajectory, and motion. The Sensing Objective is the final result obtained by the Application Function (AF), such as traffic violations or road congestion.
[0050] The data transmission method provided in the embodiments of the present application is described in detail below through some embodiments and their application scenarios in conjunction with the accompanying drawings.
[0051] As shown in FIG3 , an embodiment of the present application provides a data transmission method, including:
[0052] Step 301: The first device sends a container to the second device, where the container includes perception data of a perception service.
[0053] Optionally, the first device is a wireless access network device (such as a base station) or a terminal, and the second device is a perception function network element device, i.e., an SF network element device; or, the second device is a network element device with a perception function, for example, an SMF or location management function (LMF) with a perception function.
[0054] The perception data in the embodiment of the present application is data corresponding to the perception measurement quantity. For example, when the perception measurement quantity is delay, the perception data is delay data detected by the base station. When the perception measurement quantity is signal strength, the perception data is signal strength data.
[0055] In this embodiment of the present application, a first device sends a container containing sensory data for a sensory service to a second device. This solution enables the transmission of sensory data corresponding to a sensory service that meets the customized requirements through the container when an operator or manufacturer has customized requirements for a sensory service.
[0056] Optionally, the first device sending the container to the second device includes at least one of the following:
[0057] The first device sends an Internet Protocol (IP) packet to the second device, where the IP packet includes the container;
[0058] The first device sends a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) packet to the second device, where the GTP packet includes the container;
[0059] The first device sends a New Radio Sensing Protocol (NRSP) packet to the second device, where the NRSP packet includes the container;
[0060] It should be noted that NRSP is introduced using the 5G communication system as an example; in the 4G communication system, it can be the Long Term Evolution (LTE) Perception Protocol (LSP); in the 6G communication system, it can be the 6G Sensing Protocol (6GSP), where 6G can change according to the naming of 6G. For example, when 6G is named Next General (NG), 6GSP is NGSP.
[0061] The first device sends a Non Access Stratum (NAS) message to the second device, where the NAS message includes the container.
[0062] In an embodiment of the present application, the above-mentioned container may be included in an IP packet, a GTP packet, an NRSP packet or a NAS message, and the container may be sent via the IP packet, the GTP packet, the NRSP packet or the NAS message.
[0063] Optionally, the first device sending the container to the second device includes:
[0064] The first device sends a private message (Private Message) to the second device, wherein the private message includes the container, which may be a private information element container (Private Information Element Container, Private IE-Container).
[0065] Optionally, the first device sending the container to the second device includes:
[0066] The first device sends a container to the second device, where the container includes at least two perception service identifiers and perception data of a perception service corresponding to each perception service identifier;
[0067] Alternatively, the first device sends N1 containers and N1 perception service identifiers to the second device, each of the N1 containers contains perception data of a perception service, the N1 perception service identifiers correspond to the N1 containers one-to-one, and N1 is a positive integer;
[0068] Alternatively, the first device sends N2 containers to the second device, each of the N2 containers includes a perception service identifier and perception data of the perception service corresponding to the perception service identifier, and N2 is a positive integer.
[0069] In an embodiment of the present application, one container may be carried in the above-mentioned IP packet, GTP packet, NRSP packet or NAS message, wherein the one container contains at least two perception service identifiers and perception data of the perception service corresponding to each of the perception service identifiers; or, the above-mentioned N1 containers and N1 perception service identifiers may be carried in the above-mentioned IP packet, GTP packet, NRSP packet or NAS message, or, the above-mentioned N2 containers may be carried in the above-mentioned IP packet, GTP packet, NRSP packet or NAS message.
[0070] Optionally, the perception data of the perception service includes data corresponding to a perception measurement quantity of the perception service, and the perception measurement quantity includes: a common perception measurement quantity and an additional perception measurement quantity (additional perception measurement quantity); or, the perception measurement quantity of the perception service includes an additional perception measurement quantity.
[0071] In the embodiments of the present application, the universal perception measurement quantity may be a standardized perception measurement quantity, and the additional perception measurement quantity may be a non-standardized perception measurement quantity. For example, the universal perception measurement quantity is a perception measurement quantity standardized in 3GPP, and the additional perception measurement quantity is a perception measurement quantity not standardized in 3GPP. Alternatively, the universal perception measurement quantity may be a measurement quantity transmitted between a first device and a second device using a predefined transmission method. For example, the first device may transmit data corresponding to the perception measurement quantity using a predefined parameter, and when the second device obtains the data carried by the parameter, it may obtain the perception measurement quantity corresponding to the data.
[0072] Optionally, when the perception measurement amount of the perception service includes an additional perception measurement amount, the method further includes:
[0073] The first device sends data corresponding to the universal perception measurement quantity of the perception service and a service identifier corresponding to the perception service to the second device using predefined parameters.
[0074] It should be noted that the service identifier in this application is used to identify the sensing service, and may also be referred to as the sensing service identifier, sensing service identifier, sensing task identifier, sensing target identifier, sensing identifier (Sensing ID), and identifier.
[0075] In the embodiment of the present application, the standardized universal perception measurement quantity is transmitted using predefined parameters, and the universal perception measurement quantity and the additional perception measurement quantity are associated with each other through the identifier corresponding to the perception service. That is, the universal perception measurement quantity and the additional perception measurement quantity of the same perception service correspond to the same service identifier.
[0076] Optionally, the predefined parameters are parameters agreed upon or specified in a protocol. For example, parameter 1 specified in the protocol is used to transmit Doppler data, and parameter 2 specified in the protocol is used to transmit signal strength data.
[0077] Optionally, the first device sending the container to the second device includes:
[0078] The first device negotiates with the second device to determine a transmission mode of the sensing data of the sensing service;
[0079] In a case where it is determined to send the perception data of the perception service through a container, the first device sends the container to the second device.
[0080] In an embodiment of the present application, the transmission method of the perception data includes transmitting the perception data using predefined parameters or transmitting the perception data using a container. The first device and the second device first negotiate to determine the transmission method of the perception data. If it is determined that the transmission method of the perception data is to send the perception data of the perception service using a container, the first device sends the container to the second device.
[0081] As an optional implementation manner, the first device negotiates with the second device to determine a transmission mode of the perception data of the perception service, including:
[0082] The first device obtains a first message sent by the second device, where the first message includes: a transmission mode of the sensing data requested or supported by the second device;
[0083] The first device sends a second message to the second device, where the second message includes a transmission mode of the perception data of the perception service determined by the first device according to the first message.
[0084] Optionally, the first message may be a perception service request. Upon receiving the request to perform the perception service, the second device sends the perception service request to the first device. The perception service request may be triggered by an application function, by the second device itself, or by the first device or terminal.
[0085] Optionally, in a case where the first message includes a transmission mode of the perception data requested by the second device, the second device may carry at least one transmission mode determined by the second device and usable for transmitting the perception data. In a case where the first message includes a transmission mode of the perception data supported by the second device, the second device may carry at least one transmission mode supported by the second device and usable for transmitting the perception data.
[0086] Optionally, when the transmission mode of the perception data requested or supported by the second device in the first message is to transmit the perception data through a container, the first message further includes: a perception measurement value corresponding to the perception data transmitted by the synaesthesia container indicated by the second device.
[0087] Optionally, the first device sending the second message to the second device includes:
[0088] In a case where the first device supports the transmission mode of the perception data requested or supported by the second device, the second message is sent to the second device, where the second message is used to indicate that the transmission mode of the perception data of the perception service determined is the transmission mode of the perception data requested or supported by the second device, or the second message is used to indicate that the transmission mode of the perception data of the perception service determined is one of the transmission modes of the perception data requested or supported by the second device. For example, when the second device requests or supports two transmission modes of the perception data, the final transmission mode is determined by the second device.
[0089] Optionally, the first message further includes: the perception service executed by the second device or a service identifier corresponding to the perception service executed by the second device.
[0090] Optionally, when the first message does not include the service identifier corresponding to the awareness service executed by the second device, the second message includes the service identifier corresponding to the awareness service executed by the second device.
[0091] In an embodiment of the present application, the service identifier corresponding to the perception service can be allocated by the first device or the second device. For example, when the service identifier corresponding to the perception service can be allocated by the second device, the service identifier is included in the first message; or, when the service identifier corresponding to the perception service can be allocated by the first device, the service identifier is included in the second message, and the service identifier is allocated by the first device for the perception service.
[0092] Optionally, the implementation further includes:
[0093] The first device sends at least one of the following to the second device:
[0094] Supported perception services;
[0095] Supported perceptual measurements;
[0096] Supported perceptual data transmission methods;
[0097] The sensing data transmission method includes: transmitting the sensing data through predefined parameters or transmitting the sensing data through a container.
[0098] In this implementation, the first device may send the above information by registering the awareness service supported by the first device to the second device. Specifically, the registration information includes at least one of the following:
[0099] Supported perceptual measurements;
[0100] Supported transmission methods for sensory data;
[0101] Vendor information of the first device, such as a vendor identifier of the first device;
[0102] Token information supported by the first device.
[0103] The perceptual measurement quantity in the embodiment of the present application includes at least one of delay, Doppler, angle or intensity. The perceptual measurement quantity can also be understood as a perceptual parameter, a perceptual input or a perceptual vector.
[0104] The second device records the sensing services supported by each first device or the transmission methods of the sensing data supported by each first device based on the registration information. After receiving a request to perform the sensing service, the second device selects a first device based on the transmission methods of the sensing data or the sensing services supported by each first device, and sends the first message to the selected first device.
[0105] Optionally, the registration message may also be a notification message or a service request message.
[0106] Optionally, the first message further includes at least one of the following:
[0107] The sensing measurement quantity that needs to be reported by the first device;
[0108] The supplier information of the second device;
[0109] Token information of the second device.
[0110] Optionally, the first device sending the second message to the second device includes:
[0111] When the transmission mode of the perception data requested by the second device is to transmit the perception data through a container, and the vendor information or token information meets a preset condition, the first device sends the second message to the second device.
[0112] Optionally, the above-mentioned preset conditions include: the supplier of the second device is a pre-agreed supplier that can transmit perception data with the first device through a container, or the token information of the second device is consistent with or matches the token information stored or possessed by the first device.
[0113] The above implementation is described below with reference to embodiments.
[0114] In this embodiment, the first device is a RAN and the second device is a SF. As shown in FIG4 , this embodiment includes:
[0115] Step 401: The RAN registers the awareness services it supports with the SF. The registration information includes the following information:
[0116] Supported transmission methods for sensory data.
[0117] Optionally, the registration information may further include at least one of the following:
[0118] Supported perceptual measurements;
[0119] The vendor ID of the RAN;
[0120] Token supported by RAN.
[0121] This step 401 is an optional step.
[0122] Step 402: The SF records the perception services supported by each RAN and the transmission mode of the perception data supported.
[0123] This step 402 is an optional step.
[0124] Step 403: The SF receives a request to perform the sensing service and selects a RAN according to the requirement of the sensing service.
[0125] The requirement can be triggered by the AF, the SF itself, the RAN or the UE.
[0126] If the above steps 401 and 402 are performed, the SF selects a RAN based on the capabilities of each RAN (supported sensing services and supported transmission methods of sensing data).
[0127] Step 404: The SF sends a sensing service request to the selected RAN.
[0128] The sensing service request includes the following information:
[0129] The executed sensing service or the service identifier corresponding to the sensing service;
[0130] The transmission method of the sensing data requested or supported by the SF.
[0131] If the transmission mode of the perception data requested or supported by the SF is to transmit the perception data through a container (for example, to transmit the perception data corresponding to the additional measurement quantity through the container), the SF further indicates which measurement quantities correspond to the perception data to be transmitted through the container.
[0132] Optionally, the above-mentioned perception service request further includes at least one of the following:
[0133] Perception measurements that need to be reported by the RAN;
[0134] SF's vendor ID, i.e. SF's own vendor information;
[0135] SF's token information, that is, the token owned by SF itself.
[0136] Step 405: The RAN determines to reply with a perception service configuration response based on whether it supports the perception service corresponding to the perception service request and the transmission mode of the perception data. The perception service configuration response includes a confirmation message or a rejection message.
[0137] If the RAN supports the transmission mode of the sensing service and sensing data corresponding to the sensing service request, a confirmation message (ie, the second message) is determined to be returned. If the RAN does not support the transmission mode of the sensing service and sensing data corresponding to the sensing service request, a rejection message is determined to be returned.
[0138] If the sensing request carries the vender ID or token information, the RAN further determines whether it supports transmission through the container (or customized transmission or private transmission).
[0139] Step 406: RAN collects and processes the sensing data.
[0140] Step 407: RAN sends the acquired sensing data to SF.
[0141] For general sensing measurements, when RAN sends sensing data to SF, it uses predefined parameters to send;
[0142] For additional perceptual measurements, container transport is used.
[0143] Specifically, using container transport includes the following two solutions:
[0144] Solution 1: Data of multiple RAN sensing services are transmitted through one container. Different sensing services are distinguished within the container by using the sensing service ID + sensing data.
[0145] Solution 2: Each sensing service corresponds to a separate container and is transmitted in the form of sensing service ID + container, or by carrying the sensing service ID and sensing data in the container.
[0146] For a specific sensing service, a portion of the sensing data corresponding to the sensing measurement amount may be transmitted using predefined parameters, and another portion of the sensing data corresponding to the additional sensing measurement amount may be transmitted through a container, and the two portions of data may be associated using a sensing service id.
[0147] For example, the perception measurement quantities corresponding to a certain perception service are X1 and X2. To improve accuracy, the perception measurement quantities X3 and X4 are customized.
[0148] For common RAN equipment, only X1 and X2 need to be transmitted through a predefined message format.
[0149] For customized RAN equipment, in addition to transmitting X1 and X2 through a predefined message format, X3 and X4 are also transmitted through a container. SF associates X1, X2, X3, and X4 based on the sensing service ID and processes them together.
[0150] The container can be carried in a GTP message, an IP packet, an NRSP packet, or a NAS message.
[0151] For RAN-SF architecture: The container is contained in a GTP message, IP packet, or NRSP packet.
[0152] For the RAN-UPF-SF architecture: the container is contained in an IP packet or an NRSP packet.
[0153] For the RAN-AMF-SF architecture: the container is included in the NAS signaling or NRSP packet.
[0154] Step 408: If the sensing service is a sensing service requested by the AF, the SF sends the sensing data to the AF through another container.
[0155] In the above step 404, the SF allocates the sensing service ID as an example. It can also be allocated by the RAN. In this case, the sensing service ID is not carried in step 404. The RAN allocates it after receiving step 404 and sends it to the SF in step 405.
[0156] It should be noted that between step 403 and step 404, the SF may first request the RAN for the supported transmission mode of the sensing data, the vendor ID or the token, and the SF sends step 404 based on the information obtained from the RAN. This step may replace the above steps 401 and 402.
[0157] As another optional implementation manner, the first device negotiates with the second device to determine a transmission mode of the perception data of the perception service, including:
[0158] The first device sends a third message to the second device, where the third message includes a transmission mode of the perception data supported by the first device; the first device obtains a fourth message sent by the second device, where the fourth message includes a transmission mode of the perception data of the perception service determined by the second device according to the third message;
[0159] Alternatively, the first device sends a fifth message to the second device, where the fifth message is used to inquire whether the second device supports transmission of perception data through a container; the first device obtains a sixth message sent by the second device, where the sixth message includes a transmission mode of the perception data of the perception service determined by the second device according to the fifth message;
[0160] Alternatively, the first device sends a seventh message to the second device, where the seventh message is used to request the second device to obtain the transmission method of the perception data supported by the perception service; the first device obtains the eighth message sent by the second device, where the eighth message includes the transmission method of the perception data supported by the second device for the perception service; the first device determines the transmission method of the perception data of the perception service based on the eighth message.
[0161] Optionally, the implementation further includes:
[0162] The first device obtains a ninth message sent by the second device, where the ninth message includes the perception service executed by the second device or a service identifier corresponding to the perception service executed by the second device.
[0163] The ninth message may specifically be perception service configuration information.
[0164] Optionally, the ninth message further includes at least one of the following:
[0165] The sensing measurement quantity that needs to be reported by the first device;
[0166] The supplier information of the second device;
[0167] Token information.
[0168] Optionally, the first device sending the container to the second device includes:
[0169] When it is determined that the transmission mode of the perception data of the perception service is to transmit the perception data through a container, and the vendor information or token information meets a preset condition, the first device sends the container to the second device.
[0170] Optionally, the above-mentioned preset conditions include: the supplier of the second device is a pre-agreed supplier that can transmit perception data with the first device through a container, or the token information of the second device is consistent with the token information stored or possessed by the first device.
[0171] The implementation is described below with reference to an embodiment.
[0172] In this embodiment, the first device is a RAN and the second device is a SF. As shown in FIG5 , this embodiment includes:
[0173] Step 501: SF receives a request to perform a sensing service and selects RAN.
[0174] The requirement can be triggered by the AF, the SF itself, the RAN or the UE.
[0175] Optionally, the SF may select the RAN based on the location information.
[0176] Step 502: The SF sends the awareness service configuration information to the selected RAN.
[0177] The above-mentioned perception service configuration information includes: a service identifier corresponding to the perception service being executed or the perception service executed by the second device.
[0178] Optionally, the awareness service configuration information further includes at least one of the following:
[0179] Perception measurements that need to be reported by the RAN;
[0180] SF's vendor ID, i.e. SF's own vendor information;
[0181] SF's token information, that is, the token owned by SF itself.
[0182] Step 503: RAN sends the supported sensing data transmission mode to SF for the service.
[0183] For example, the RAN lists all the transmission modes of the sensing data supported by it, and the transmission modes of the sensing data supported by the RAN can be sent to the SF via a sensing transmission mode request message.
[0184] Alternatively, when the RAN determines that the perception service can be transmitted using predefined parameters, the RAN asks the SF whether it supports transmitting the perception data corresponding to the additional perception measurement quantity through the container;
[0185] Alternatively, when the RAN determines that the perception service does not support transmission through predefined parameters, the RAN inquires whether it supports transmission of the perception data corresponding to the perception measurement quantity through the container.
[0186] Step 504: SF sends the determined transmission mode of the sensing data.
[0187] The SF may send the transmission mode of the sensing data determined by the SF through a sensing transmission mode response message.
[0188] Step 505: RAN sends an awareness service configuration response message, which includes an acceptance message or a rejection message.
[0189] The acceptance message in the perception service configuration response message indicates that the RAN agrees with the perception data transmission method determined by the SF, and the rejection message indicates that the RAN disagrees with the perception data transmission method determined by the SF.
[0190] The subsequent process is the same as steps 406 to 408 in the embodiment shown in FIG. 4 .
[0191] It should be noted that, in this embodiment, steps 503 and 504 are described using the example of SF finally determining the transmission method of the perception data. It may also be that RAN requests SF to transmit the perception data corresponding to the perception service supported by SF. After SF sends it to RAN, RAN finally determines the transmission method of the perception data.
[0192] In the data transmission method of an embodiment of the present application, a first device sends a container containing perception data of a perception service to a second device. This solution enables the transmission of perception data corresponding to the perception service that meets the customized requirements through the container when an operator or manufacturer has customized requirements for a perception service.
[0193] As shown in FIG6 , the embodiment of the present application further provides a data transmission method, including:
[0194] Step 601: The second device obtains a container sent by the first device, where the container includes perception data of a perception service.
[0195] In an embodiment of the present application, the first device is a wireless access device, such as a base station, and the second device is a perception function network element device, that is, a SF network element device.
[0196] The perception data is data corresponding to the perception measurement quantity. For example, when the perception measurement quantity is delay, the perception data is delay data detected by the base station. When the perception measurement quantity is signal strength, the perception data is signal strength data.
[0197] In this embodiment of the present application, the second device obtains a container sent by the first device, which includes the perception data of the perception service. Through this solution, when an operator or manufacturer has customized requirements for a certain perception service, the container can be used to transmit the perception data corresponding to the perception service that meets the customized requirements.
[0198] Optionally, the second device obtains the container sent by the first device, including at least one of the following:
[0199] The second device obtains an Internet Protocol (IP) packet sent by the first device, where the IP packet includes the container;
[0200] The second device obtains a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) packet sent by the first device, where the GTP packet includes the container;
[0201] The second device obtains a New Radio Interface Perception Protocol (NRSP) packet sent by the first device, where the NRSP packet includes the container;
[0202] The second device obtains a non-access stratum (NAS) message sent by the first device, where the NAS message includes the container.
[0203] Optionally, the second device obtains the container sent by the first device, including:
[0204] The second device obtains a container sent by the first device, where the container includes at least two perception service identifiers and perception data of a perception service corresponding to each perception service identifier;
[0205] Alternatively, the second device obtains N1 containers and N1 perception service identifiers sent by the first device, where each of the N1 containers contains perception data of a perception service, the N1 perception service identifiers correspond to the N1 containers one-to-one, and N1 is a positive integer;
[0206] Alternatively, the second device obtains N2 containers sent by the first device, each of the N2 containers includes a perception service identifier and perception data of the perception service corresponding to the perception service identifier, and N2 is a positive integer.
[0207] Optionally, the perception data of the perception service includes data corresponding to a perception measurement quantity of the perception service, and the perception measurement quantity includes: a common perception measurement quantity and an additional perception measurement quantity; or the perception measurement quantity of the perception service includes an additional perception measurement quantity.
[0208] Optionally, when the perception measurement amount of the perception service includes an additional perception measurement amount, the method further includes:
[0209] The second device obtains, through predefined parameters, data corresponding to the universal perception measurement amount of the perception service sent by the first device and an identifier corresponding to the perception service.
[0210] Optionally, the method of the embodiment of the present application further includes:
[0211] The first device negotiates with the second device to determine a transmission mode of the sensing data of the sensing service;
[0212] The container is sent from the first device to the second device when it is determined that the transmission mode of the perception data of the perception service is to send the perception data through the container.
[0213] Optionally, the first device negotiates with the second device to determine a transmission mode of the perception data of the perception service, including:
[0214] The second device sends a first message to the first device, where the first message includes: a transmission mode of the sensing data requested or supported by the second device;
[0215] The second device obtains a second message sent by the first device, where the second message includes a transmission mode of the perception data of the perception service determined by the first device according to the first message.
[0216] Optionally, the first message further includes: the perception service executed by the second device or a service identifier corresponding to the perception service executed by the second device.
[0217] Optionally, when the first message does not include the service identifier corresponding to the awareness service executed by the second device, the second message includes the service identifier corresponding to the awareness service executed by the second device.
[0218] Optionally, the second device sending the first message to the first device includes:
[0219] The second device obtains the tenth message sent by the first device;
[0220] The second device sends the first message to the first device according to the tenth message;
[0221] The tenth message includes at least one of the following:
[0222] Supported perception services;
[0223] Supported perceptual measurements;
[0224] Supported perceptual data transmission methods;
[0225] The sensing data transmission method includes: transmitting the sensing data through predefined parameters or transmitting the sensing data through a container.
[0226] Optionally, the first device negotiates with the second device to determine a transmission mode of the perception data of the perception service, including:
[0227] The second device obtains, by the first device, a third message sent by the first device, where the third message includes a transmission mode of the perception data supported by the first device; the second device sends a fourth message to the first device, where the fourth message includes a transmission mode of the perception data of the perception service determined by the second device according to the third message;
[0228] Alternatively, the second device obtains a fifth message sent by the first device, where the fifth message is used to inquire whether the second device supports transmission of perception data through a container; the second device sends a sixth message to the first device, where the sixth message includes a transmission mode of the perception data of the perception service determined by the second device according to the fifth message;
[0229] Alternatively, the second device obtains the seventh message sent by the first device, and the seventh message is used to request the second device to obtain the transmission method of the perception data supported by the perception service; the second device sends an eighth message to the first device, and the eighth message includes the transmission method of the perception data supported by the second device for the perception service.
[0230] Optionally, the method of the embodiment of the present application further includes:
[0231] The second device sends a ninth message to the first device, where the ninth message includes the perception service executed by the second device or a service identifier corresponding to the perception service executed by the second device.
[0232] It should be noted that the data transmission method executed by the second device is a method corresponding to the data transmission method executed by the above-mentioned first device. The interaction process between the two has been described in detail in the method embodiment on the first device side and will not be repeated here.
[0233] In this embodiment of the present application, the second device obtains a container sent by the first device, which includes the perception data of the perception service. Through this solution, when an operator or manufacturer has customized requirements for a certain perception service, the container can be used to transmit the perception data corresponding to the perception service that meets the customized requirements.
[0234] The data transmission method provided in the embodiment of the present application can be executed by a data transmission device. In the embodiment of the present application, the data transmission method performed by a data transmission device is taken as an example to illustrate the data transmission device provided in the embodiment of the present application.
[0235] As shown in FIG7 , an embodiment of the present application provides a data transmission apparatus 700, which is applied to a first device and includes:
[0236] The first sending module 701 is configured to send a container to a second device, where the container includes sensing data of a sensing service.
[0237] Optionally, the first sending module is configured to perform at least one of the following:
[0238] Sending an Internet Protocol (IP) packet to the second device, where the IP packet includes the container;
[0239] Sending a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) packet to the second device, where the GTP packet includes the container;
[0240] Sending a New Radio Protocol (NRSP) packet to the second device, where the NRSP packet includes the container;
[0241] A non-access stratum (NAS) message is sent to the second device, where the NAS message includes the container.
[0242] Optionally, the first sending module is configured to send a container to the second device, where the container includes at least two perception service identifiers and perception data of a perception service corresponding to each perception service identifier;
[0243] Alternatively, N1 containers and N1 perception service identifiers are sent to the second device, where each of the N1 containers contains perception data of a perception service, the N1 perception service identifiers correspond one-to-one to the N1 containers, and N1 is a positive integer;
[0244] Alternatively, N2 containers are sent to the second device, each of the N2 containers includes a perception service identifier and perception data of the perception service corresponding to the perception service identifier, and N2 is a positive integer.
[0245] Optionally, the perception data of the perception service includes data corresponding to a perception measurement quantity of the perception service, and the perception measurement quantity includes: a common perception measurement quantity and an additional perception measurement quantity; or the perception measurement quantity of the perception service includes an additional perception measurement quantity.
[0246] Optionally, when the perception measurement amount of the perception service includes an additional perception measurement amount, the first sending module is further configured to:
[0247] The first device sends data corresponding to the universal perception measurement quantity of the perception service and a service identifier corresponding to the perception service to the second device using predefined parameters.
[0248] Optionally, the first sending module includes:
[0249] a negotiation submodule, configured to negotiate with the second device to determine a transmission mode of the perception data of the perception service;
[0250] The first sending submodule is configured to send the container to the second device when it is determined that the perception data of the perception service is sent through the container.
[0251] Optionally, the negotiation submodule includes:
[0252] A first acquisition submodule is configured to acquire a first message sent by the second device, where the first message includes: a transmission mode of the sensing data requested or supported by the second device;
[0253] The second sending submodule is configured to send a second message to the second device, where the second message includes a transmission mode of the perception data of the perception service determined by the first device according to the first message.
[0254] Optionally, the second sending submodule is used to send the second message to the second device when the first device supports the transmission method of the perception data requested or supported by the second device, and the second message is used to indicate that the transmission method of the perception data of the determined perception service is the transmission method of the perception data requested or supported by the second device.
[0255] Optionally, the first message further includes: the perception service executed by the second device or a service identifier corresponding to the perception service executed by the second device.
[0256] Optionally, when the first message does not include the service identifier corresponding to the awareness service executed by the second device, the second message includes the service identifier corresponding to the awareness service executed by the second device.
[0257] Optionally, the device of the embodiment of the present application further includes:
[0258] A second sending module is configured to send at least one of the following to the second device:
[0259] Supported perception services;
[0260] Supported perceptual measurements;
[0261] Supported perceptual data transmission methods;
[0262] The sensing data transmission method includes: transmitting the sensing data through predefined parameters or transmitting the sensing data through a container.
[0263] Optionally, the first message further includes at least one of the following:
[0264] the sensing measurement quantity that needs to be reported by the first device;
[0265] The supplier information of the second device;
[0266] Token information of the second device.
[0267] Optionally, the second sending submodule is used for the first device to send the second message to the second device when the transmission mode of the perception data requested by the second device is to transmit the perception data through a container and the supplier information or token information meets a preset condition.
[0268] Optionally, the negotiation submodule is used to:
[0269] Sending a third message to the second device, the third message including a transmission mode of the perception data supported by the first device; obtaining a fourth message sent by the second device, the fourth message including a transmission mode of the perception data of the perception service determined by the second device according to the third message;
[0270] Alternatively, a fifth message is sent to the second device, where the fifth message is used to inquire whether the second device supports transmission of perception data through a container; and a sixth message is obtained from the second device, where the sixth message includes a transmission mode of the perception data of the perception service determined by the second device according to the fifth message.
[0271] Alternatively, a seventh message is sent to the second device, where the seventh message is used to request the second device to obtain the transmission method of the perception data supported by the perception service; an eighth message is obtained from the second device, where the eighth message includes the transmission method of the perception data supported by the second device for the perception service; and the transmission method of the perception data of the perception service is determined based on the eighth message.
[0272] Optionally, the first sending module further includes:
[0273] The second acquisition submodule is used to acquire a ninth message sent by the second device, where the ninth message includes the perception service executed by the second device or a service identifier corresponding to the perception service executed by the second device.
[0274] Optionally, the ninth message further includes at least one of the following:
[0275] the sensing measurement quantity that needs to be reported by the first device;
[0276] The supplier information of the second device;
[0277] Token information of the second device.
[0278] Optionally, the first sending submodule is used to send the container from the first device to the second device when it is determined that the transmission mode of the perception data of the perception service is to transmit the perception data through a container and the vendor information or token information meets a preset condition.
[0279] Optionally, the first device is a wireless access network device or a terminal, and the second device is a perception function network element device.
[0280] In this embodiment of the present application, a first device sends a container containing sensory data for a sensory service to a second device. This solution enables the transmission of sensory data corresponding to a sensory service that meets the customized requirements through the container when an operator or manufacturer has customized requirements for a sensory service.
[0281] As shown in FIG8 , an embodiment of the present application provides a data transmission apparatus 800, which is applied to a second device and includes:
[0282] The first acquisition module 801 is configured to acquire a container sent by a first device, where the container includes perception data of a perception service.
[0283] Optionally, the first acquisition module is configured to perform at least one of the following:
[0284] Obtaining an Internet Protocol (IP) packet sent by the first device, where the IP packet includes the container;
[0285] Obtaining a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) packet sent by the first device, where the GTP packet includes the container;
[0286] Obtain a New Radio Interface Perception Protocol (NRSP) packet sent by the first device, where the NRSP packet includes the container;
[0287] Obtain a non-access stratum (NAS) message sent by the first device, where the NAS message includes the container.
[0288] Optionally, the first acquisition module is used to:
[0289] Acquire a container sent by the first device, where the container includes at least two perception service identifiers and perception data of a perception service corresponding to each perception service identifier;
[0290] Alternatively, obtaining N1 containers and N1 perception service identifiers sent by the first device, where each of the N1 containers contains perception data of a perception service, the N1 perception service identifiers correspond one-to-one to the N1 containers, and N1 is a positive integer;
[0291] Alternatively, N2 containers sent by the first device are obtained, where each of the N2 containers includes a perception service identifier and perception data of a perception service corresponding to the perception service identifier, and N2 is a positive integer.
[0292] Optionally, the perception data of the perception service includes data corresponding to a perception measurement quantity of the perception service, and the perception measurement quantity includes: a common perception measurement quantity and an additional perception measurement quantity; or the perception measurement quantity of the perception service includes an additional perception measurement quantity.
[0293] Optionally, the device further comprises:
[0294] The second acquisition module is configured to acquire, when the perception measurement amount of the perception service includes an additional perception measurement amount, data corresponding to the general perception measurement amount of the perception service sent by the first device and an identifier corresponding to the perception service through predefined parameters.
[0295] Optionally, the device of the embodiment of the present application further includes:
[0296] a negotiation module, configured to negotiate with the second device to determine a transmission mode of the perception data of the perception service;
[0297] The container is sent from the first device to the second device when it is determined that the transmission mode of the perception data of the perception service is to send the perception data through the container.
[0298] Optionally, the negotiation module includes:
[0299] a transmission submodule, configured to send a first message to the first device, where the first message includes: a transmission mode of the sensing data requested or supported by the second device;
[0300] The third acquisition submodule is configured to acquire a second message sent by the first device, where the second message includes a transmission mode of the perception data of the perception service determined by the first device according to the first message.
[0301] Optionally, the first message further includes: the perception service executed by the second device or a service identifier corresponding to the perception service executed by the second device.
[0302] Optionally, when the first message does not include the service identifier corresponding to the awareness service executed by the second device, the second message includes the service identifier corresponding to the awareness service executed by the second device.
[0303] Optionally, the transmission submodule includes:
[0304] a fourth acquiring submodule, configured to acquire a tenth message sent by the first device;
[0305] a third sending submodule, configured to send the first message to the first device according to the tenth message;
[0306] The tenth message includes at least one of the following:
[0307] Supported perception services;
[0308] Supported perceptual measurements;
[0309] Supported perceptual data transmission methods;
[0310] The sensing data transmission method includes: transmitting the sensing data through predefined parameters or transmitting the sensing data through a container.
[0311] Optionally, the negotiation module is configured to:
[0312] Obtaining a third message sent by the first device, the third message including a transmission mode of the perception data supported by the first device; sending a fourth message to the first device, the fourth message including a transmission mode of the perception data of the perception service determined by the second device according to the third message;
[0313] Alternatively, obtaining a fifth message sent by the first device, where the fifth message is used to inquire whether the second device supports transmission of perception data through a container; sending a sixth message to the first device, where the sixth message includes a transmission mode for the perception data of the perception service determined by the second device according to the fifth message;
[0314] Alternatively, obtain the seventh message sent by the first device, wherein the seventh message is used to request the second device to obtain the transmission method of the perception data supported by the perception service; and send an eighth message to the first device, wherein the eighth message includes the transmission method of the perception data supported by the second device for the perception service.
[0315] Optionally, the negotiation module further includes:
[0316] The fourth sending submodule is used to send a ninth message to the first device, where the ninth message includes the perception service executed by the second device or a service identifier corresponding to the perception service executed by the second device.
[0317] In this embodiment of the present application, the second device obtains a container sent by the first device, which includes the perception data of the perception service. Through this solution, when an operator or manufacturer has customized requirements for a certain perception service, the container can be used to transmit the perception data corresponding to the perception service that meets the customized requirements.
[0318] The data transmission device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.
[0319] The data transmission device provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 3 to 6 and achieve the same technical effects. To avoid repetition, they will not be described here.
[0320] Optionally, as shown in Figure 9, an embodiment of the present application further provides a communication device 900, including a processor 901 and a memory 902, wherein the memory 902 stores a program or instruction that can be run on the processor 901. For example, when the communication device 900 is a terminal or a base station, the program or instruction is executed by the processor 901 to implement the various steps of the method embodiment performed by the first device above, and can achieve the same technical effect. When the communication device 900 is an SF, the program or instruction is executed by the processor 901 to implement the various steps of the method embodiment performed by the second device above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0321] The embodiment of the present application also provides a first device, including a processor and a communication interface, the communication interface being used to send a container to a second device, wherein the container includes perception data of a perception service. This first device embodiment corresponds to the above-mentioned first device-side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this first device embodiment and can achieve the same technical effect. Specifically, Figure 10 is a schematic diagram of the hardware structure of a terminal that implements an embodiment of the present application.
[0322] The terminal 1000 includes but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009 and at least some of the components of the processor 1010.
[0323] Those skilled in the art will appreciate that the terminal 1000 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1010 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG10 does not limit the terminal. The terminal may include more or fewer components than shown, or combine certain components, or arrange the components differently, which will not be described in detail here.
[0324] It should be understood that in an embodiment of the present application, the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042, and the graphics processor 10041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include two parts: a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.
[0325] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 1001 may transmit the data to the processor 1010 for processing. Furthermore, the RF unit 1001 may send uplink data to the network-side device. Typically, the RF unit 1001 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.
[0326] The memory 1009 can be used to store software programs or instructions and various data. The memory 1009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1009 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 1009 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.
[0327] Processor 1010 may include one or more processing units. Optionally, processor 1010 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1010.
[0328] The radio frequency unit 1001 is configured to send a container to the second device, where the container includes perception data of the perception service.
[0329] Optionally, the radio frequency unit 1001 is configured to perform at least one of the following:
[0330] Sending an Internet Protocol (IP) packet to the second device, where the IP packet includes the container;
[0331] Sending a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) packet to the second device, where the GTP packet includes the container;
[0332] Sending a New Radio Protocol (NRSP) packet to the second device, where the NRSP packet includes the container;
[0333] A non-access stratum (NAS) message is sent to the second device, where the NAS message includes the container.
[0334] Optionally, the radio frequency unit 1001 is configured to:
[0335] Sending a container to the second device, where the container includes at least two perception service identifiers and perception data of a perception service corresponding to each perception service identifier;
[0336] Alternatively, N1 containers and N1 perception service identifiers are sent to the second device, where each of the N1 containers contains perception data of a perception service, the N1 perception service identifiers correspond one-to-one to the N1 containers, and N1 is a positive integer;
[0337] Alternatively, N2 containers are sent to the second device, each of the N2 containers includes a perception service identifier and perception data of the perception service corresponding to the perception service identifier, and N2 is a positive integer.
[0338] Optionally, the perception data of the perception service includes data corresponding to a perception measurement quantity of the perception service, and the perception measurement quantity includes: a common perception measurement quantity and an additional perception measurement quantity; or the perception measurement quantity of the perception service includes an additional perception measurement quantity.
[0339] Optionally, when the perception measurement amount of the perception service includes an additional perception measurement amount, the radio frequency unit 1001 is further configured to:
[0340] Data corresponding to the universal perception measurement amount of the perception service and a service identifier corresponding to the perception service are sent to the second device through predefined parameters.
[0341] Optionally, the radio frequency unit 1001 is used to: negotiate with the second device to determine a transmission method for the perception data of the perception service; and when it is determined that the perception data of the perception service is to be sent through a container, send the container to the second device.
[0342] Optionally, the radio frequency unit 1001 is used to: obtain a first message sent by the second device, the first message including: a transmission method of perception data requested or supported by the second device; and send a second message to the second device, the second message including a transmission method of perception data of the perception service determined by the first device based on the first message.
[0343] Optionally, the radio frequency unit 1001 is used to: when the first device supports the transmission method of the perception data requested or supported by the second device, send the second message to the second device, and the second message is used to indicate that the transmission method of the perception data of the determined perception service is the transmission method of the perception data requested or supported by the second device.
[0344] Optionally, the first message further includes: the perception service executed by the second device or a service identifier corresponding to the perception service executed by the second device.
[0345] Optionally, when the first message does not include the service identifier corresponding to the awareness service executed by the second device, the second message includes the service identifier corresponding to the awareness service executed by the second device.
[0346] Optionally, the radio frequency unit 1001 is configured to send at least one of the following to the second device:
[0347] Supported sensing services; supported sensing measurements; supported sensing data transmission methods;
[0348] The sensing data transmission method includes: transmitting the sensing data through predefined parameters or transmitting the sensing data through a container.
[0349] Optionally, the first message further includes at least one of the following:
[0350] The sensing measurement quantity reported by the first device; the vendor information of the second device; and the token information of the second device.
[0351] Optionally, the radio frequency unit 1001 is used to: when the transmission mode of the perception data requested by the second device is to transmit the perception data through a container, and the vendor information or token information meets a preset condition, send the second message to the second device.
[0352] Optionally, the radio frequency unit 1001 is configured to: send a third message to the second device, where the third message includes a transmission mode of the perception data supported by the first device; obtain a fourth message sent by the second device, where the fourth message includes a transmission mode of the perception data of the perception service determined by the second device according to the third message;
[0353] Alternatively, a fifth message is sent to the second device, where the fifth message is used to inquire whether the second device supports transmission of perception data through a container; and a sixth message is obtained from the second device, where the sixth message includes a transmission mode of the perception data of the perception service determined by the second device according to the fifth message.
[0354] Alternatively, a seventh message is sent to the second device, where the seventh message is used to request the second device to obtain the transmission method of the perception data supported by the perception service; an eighth message is obtained from the second device, where the eighth message includes the transmission method of the perception data supported by the second device for the perception service; and the first device determines the transmission method of the perception data of the perception service based on the eighth message.
[0355] Optionally, the radio frequency unit 1001 is used to: obtain a ninth message sent by the second device, where the ninth message includes the perception service executed by the second device or a service identifier corresponding to the perception service executed by the second device.
[0356] Optionally, the ninth message further includes at least one of the following:
[0357] The sensing measurement quantity reported by the first device; the vendor information of the second device; and the token information of the second device.
[0358] Optionally, the radio frequency unit 1001 is used to: when it is determined that the transmission mode of the perception data of the perception service is to transmit the perception data through a container, and the vendor information or token information meets a preset condition, send the container to the second device.
[0359] Optionally, the second device is a perception function network element device.
[0360] In an embodiment of the present application, a container including the perception data of the perception service is sent to the second device. Through this solution, when an operator or manufacturer has customized requirements for a certain perception service, the perception data corresponding to the perception service that meets the customized requirements can be transmitted through the container.
[0361] An embodiment of the present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is configured to send a container including perception data of a perception service to a second device, or to obtain a container including perception data of a perception service sent by a first device. This network-side device embodiment corresponds to the above-mentioned first device or second device method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this network-side device embodiment and can achieve the same technical effect.
[0362] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 11, the network-side device 1100 includes an antenna 111, a radio frequency device 112, a baseband device 113, a processor 114, and a memory 115. Antenna 111 is connected to radio frequency device 112. In the uplink direction, radio frequency device 112 receives information via antenna 111 and sends the received information to baseband device 113 for processing. In the downlink direction, baseband device 113 processes the information to be transmitted and sends it to radio frequency device 112. Radio frequency device 112 processes the received information and then sends it through antenna 111.
[0363] The method executed by the first device in the above embodiment may be implemented in the baseband device 113 , which includes a baseband processor.
[0364] The baseband device 113 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 11, one of the chips is, for example, a baseband processor, which is connected to the memory 115 through a bus interface to call the program in the memory 115 to perform the operation of the first device shown in the above method embodiment.
[0365] The network side device may further include a network interface 116, which is, for example, a Common Public Radio Interface (CPRI).
[0366] Specifically, the network side device 1100 of the embodiment of the present application also includes: instructions or programs stored in the memory 115 and executable on the processor 114. The processor 114 calls the instructions or programs in the memory 115 to execute the method of execution of each module shown in Figure 7 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0367] Specifically, the embodiment of the present application further provides a network side device. As shown in FIG12 , the network side device 1200 includes: a processor 1201, a network interface 1202, and a memory 1203. The network interface 1202 is, for example, a common public radio interface (CPRI).
[0368] Specifically, the network side device 1200 of the embodiment of the present application also includes: instructions or programs stored in the memory 1203 and executable on the processor 1201. The processor 1201 calls the instructions or programs in the memory 1203 to execute the method of execution of each module shown in Figure 8 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0369] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned data transmission method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0370] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.
[0371] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned data transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0372] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0373] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned data transmission method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0374] An embodiment of the present application also provides a data transmission system, including: a first device and a second device, wherein the first device can be used to execute the steps of the method on the first device side as described above, and the second device can be used to execute the steps of the method on the second device side as described above.
[0375] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be noted that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0376] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.
[0377] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.
Claims
1. A data transmission method, comprising: The first device sends a container to the second device, where the container includes perception data of a perception service.
2. The method according to claim 1, wherein: The first device sends a container to the second device, including at least one of the following: The first device sends an Internet Protocol IP packet to the second device, wherein the IP packet includes the container; The first device sends a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) packet to the second device, where the GTP packet includes the container; The first device sends a New Radio Interface Perception Protocol (NRSP) packet to the second device, where the NRSP packet includes the container; The first device sends a non-access stratum (NAS) message to the second device, where the NAS message includes the container.
3. The method according to claim 1 or 2, wherein: The first device sends a container to the second device, including: The first device sends a container to the second device, wherein the container includes at least two perception service identifiers and perception data of a perception service corresponding to each of the perception service identifiers; Alternatively, the first device sends N1 containers and N1 perception service identifiers to the second device, each of the N1 containers contains perception data of a perception service, the N1 perception service identifiers correspond to the N1 containers one-to-one, and N1 is a positive integer; Alternatively, the first device sends N2 containers to the second device, each of the N2 containers includes a perception service identifier and perception data of a perception service corresponding to the perception service identifier, and N2 is a positive integer.
4. The method according to any one of claims 1 to 3, wherein: The perception data of the perception service includes data corresponding to a perception measurement amount of the perception service, and the perception measurement amount includes: a common perception measurement amount and an additional perception measurement amount; or the perception measurement amount of the perception service includes an additional perception measurement amount.
5. The method according to claim 4, wherein: In a case where the perception measurement amount of the perception service includes an additional perception measurement amount, the method further includes: The first device sends data corresponding to the universal perception measurement amount of the perception service and a service identifier corresponding to the perception service to the second device through predefined parameters.
6. The method according to any one of claims 1 to 5, wherein: The first device sends a container to the second device, including: The first device negotiates with the second device to determine a transmission mode of the perception data of the perception service; In the case where it is determined that the sensing data of the sensing service is sent through a container, the first device sends a The container is then sent.
7. The method according to claim 6, wherein: The first device negotiates with the second device to determine a transmission mode of the perception data of the perception service, including: The first device acquires a first message sent by the second device, where the first message includes: a transmission mode of the perception data requested or supported by the second device; The first device sends a second message to the second device, where the second message includes a transmission mode of the perception data of the perception service determined by the first device according to the first message.
8. The method according to claim 7, wherein: The first device sending a second message to the second device includes: In a case where the first device supports the transmission mode of the perception data requested or supported by the second device, the second message is sent to the second device, where the second message is used to indicate that the transmission mode of the perception data of the determined perception service is the transmission mode of the perception data requested or supported by the second device.
9. The method according to claim 7 or 8, wherein: The first message also includes: the perception service executed by the second device or a service identifier corresponding to the perception service executed by the second device.
10. The method according to claim 9, wherein: In a case where the first message does not include a service identifier corresponding to the perception service executed by the second device, the second message includes a service identifier corresponding to the perception service executed by the second device.
11. The method according to any one of claims 6 to 10, further comprising: The first device sends at least one of the following to the second device: Supported sensing services; Supported perceptual measurements; Supported perceptual data transmission methods; The sensing data transmission method includes: transmitting the sensing data through predefined parameters or transmitting the sensing data through a container.
12. The method according to any one of claims 7 to 10, wherein: The first message also includes at least one of the following: the sensing measurement quantity that needs to be reported by the first device; The vendor information of the second device; Token information of the second device.
13. The method according to claim 12, wherein: The first device sending a second message to the second device includes: When the transmission method of the perception data requested by the second device is to transmit the perception data through a container, and the vendor information or token information meets a preset condition, the first device sends the second message to the second device.
14. The method according to claim 6, wherein: The first device negotiates with the second device to determine a transmission mode of the perception data of the perception service, including: The first device sends a third message to the second device, where the third message includes a transmission mode of the perception data supported by the first device; the first device obtains a fourth message sent by the second device, where the fourth message includes a transmission mode of the perception data of the perception service determined by the second device according to the third message; Alternatively, the first device sends a fifth message to the second device, where the fifth message is used to inquire whether the second device supports transmission of perception data through a container; the first device obtains a sixth message sent by the second device, where the sixth message includes a transmission mode of the perception data of the perception service determined by the second device according to the fifth message; Alternatively, the first device sends a seventh message to the second device, where the seventh message is used to request the second device to obtain a transmission method for the perception data supported by the perception service; the first device obtains an eighth message sent by the second device, where the eighth message includes the transmission method for the perception data supported by the second device for the perception service; the first device determines the transmission method for the perception data of the perception service based on the eighth message.
15. The method according to claim 14, further comprising: The first device obtains a ninth message sent by the second device, where the ninth message includes the perception service executed by the second device or a service identifier corresponding to the perception service executed by the second device.
16. The method according to claim 15, wherein: The ninth message also includes at least one of the following: the sensing measurement quantity that needs to be reported by the first device; The vendor information of the second device; Token information of the second device.
17. The method according to claim 16, wherein: The first device sending the container to the second device includes: When it is determined that the transmission mode of the perception data of the perception service is to transmit the perception data through a container, and the vendor information or the token information meets a preset condition, the first device sends the container to the second device.
18. The method according to any one of claims 1 to 17, wherein: The first device is a wireless access network device or a terminal, and the second device is a perception function network element device.
19. A data transmission method, comprising: The second device obtains the container sent by the first device, where the container includes perception data of the perception service.
20. The method according to claim 19, wherein: The second device obtains the container sent by the first device, including at least one of the following: The second device obtains an Internet Protocol IP packet sent by the first device, where the IP packet includes the container; The second device obtains a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) packet sent by the first device, where the GTP packet includes the container; The second device obtains a New Radio Interface Perception Protocol (NRSP) packet sent by the first device, where the NRSP packet includes the container; The second device obtains a non-access stratum NAS message sent by the first device, where the NAS message includes the container.
21. The method according to claim 19 or 20, wherein: The second device obtains the container sent by the first device, including: The second device obtains a container sent by the first device, wherein the container includes at least two perception service identifiers and perception data of a perception service corresponding to each of the perception service identifiers; Alternatively, the second device obtains N1 containers and N1 perception service identifiers sent by the first device, each of the N1 containers contains perception data of a perception service, the N1 perception service identifiers correspond to the N1 containers one-to-one, and N1 is a positive integer; Alternatively, the second device obtains N2 containers sent by the first device, each of the N2 containers includes a perception service identifier and perception data of a perception service corresponding to the perception service identifier, and N2 is a positive integer.
22. The method according to any one of claims 19 to 21, wherein: The perception data of the perception service includes data corresponding to a perception measurement amount of the perception service, and the perception measurement amount includes: a common perception measurement amount and an additional perception measurement amount; or the perception measurement amount of the perception service includes an additional perception measurement amount.
23. The method according to claim 22, wherein: In a case where the perception measurement amount of the perception service includes an additional perception measurement amount, the method further includes: The second device obtains, through predefined parameters, data corresponding to the universal perception measurement amount of the perception service sent by the first device and an identifier corresponding to the perception service.
24. The method according to any one of claims 19 to 23, further comprising: The first device negotiates with the second device to determine a transmission mode of the perception data of the perception service; The container is sent from the first device to the second device when it is determined that the transmission mode of the perception data of the perception service is to send the perception data through the container.
25. The method according to claim 24, wherein: The first device negotiates with the second device to determine a transmission mode of the perception data of the perception service, including: The second device sends a first message to the first device, where the first message includes: a transmission mode of the perception data requested or supported by the second device; The second device obtains a second message sent by the first device, where the second message includes a transmission mode of the perception data of the perception service determined by the first device according to the first message.
26. The method according to claim 25, wherein: The first message also includes: the perception service executed by the second device or a service identifier corresponding to the perception service executed by the second device.
27. The method according to claim 26, wherein: In a case where the first message does not include a service identifier corresponding to the perception service executed by the second device, the second message includes a service identifier corresponding to the perception service executed by the second device.
28. The method according to claim 27, wherein: The second device sending a first message to the first device includes: The second device obtains the tenth message sent by the first device; The second device sends the first message to the first device according to the tenth message; The tenth message includes at least one of the following: Supported sensing services; Supported perceptual measurements; Supported perceptual data transmission methods; The sensing data transmission method includes: transmitting the sensing data through predefined parameters or transmitting the sensing data through a container.
29. The method of claim 24, wherein: The first device negotiates with the second device to determine a transmission mode of the perception data of the perception service, including: The second device obtains a third message sent by the first device, where the third message includes a transmission mode of the perception data supported by the first device; the second device sends a fourth message to the first device, where the fourth message includes a transmission mode of the perception data of the perception service determined by the second device according to the third message; Alternatively, the second device obtains a fifth message sent by the first device, where the fifth message is used to inquire whether the second device supports transmission of perception data through a container; the second device sends a sixth message to the first device, where the sixth message includes a transmission mode of the perception data of the perception service determined by the second device according to the fifth message; Alternatively, the second device obtains the seventh message sent by the first device, and the seventh message is used to request the second device to obtain the transmission method of the perception data supported by the perception service; the second device sends an eighth message to the first device, and the eighth message includes the transmission method of the perception data supported by the second device for the perception service.
30. The method of claim 29, further comprising: The second device sends a ninth message to the first device, where the ninth message includes the perception service executed by the second device or a service identifier corresponding to the perception service executed by the second device.
31. A data transmission device, comprising: The first sending module is used to send a container to the second device, where the container includes perception data of the perception service.
32. The device according to claim 31, wherein The first sending module is used to perform at least one of the following: Sending an Internet Protocol IP packet to the second device, wherein the IP packet includes the container; Sending a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) packet to the second device, where the GTP packet includes the container; Sending a New Air Interface Perception Protocol (NRSP) packet to the second device, where the NRSP packet includes the container; A non-access stratum (NAS) message is sent to the second device, where the NAS message includes the container.
33. The device according to claim 31 or 32, wherein: The first sending module is used to send a container to the second device, wherein the container includes at least two perception service identifiers and perception data of a perception service corresponding to each of the perception service identifiers; Alternatively, N1 containers and N1 perception service identifiers are sent to the second device, each of the N1 containers A container contains the sensing data of a sensing service, N1 sensing service identifiers correspond to N1 containers one by one, and N1 is a positive integer; Alternatively, N2 containers are sent to the second device, each of the N2 containers includes a perception service identifier and perception data of the perception service corresponding to the perception service identifier, and N2 is a positive integer.
34. A data transmission device, comprising: The first acquisition module is used to acquire a container sent by a first device, where the container includes perception data of a perception service.
35. A communication device, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, it implements the steps of the data transmission method as described in any one of claims 1 to 18, or implements the steps of the data transmission method as described in any one of claims 19 to 30.
36. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the data transmission method according to any one of claims 1 to 18, or implements the steps of the data transmission method according to any one of claims 19 to 30.
Citation Information
Patent Citations
Method and equipment for processing perception service
CN115755027A
Perception data acquisition method, equipment, device and storage medium
CN115915048A
Perception service processing method, terminal, and network side device
WO2023046012A1
Cited By
Method for initiating sensing performed by sensing function, method for initiating sensing performed by radio access network, sensing function, radio access network and method for updating sensing performed by radio access network
WO2026225593A1
