Data transmission method and device and communication equipment
By sending and receiving containers between communication devices, the container contains perceived data of perceived services, the problem of customized perceived services is solved, and the satisfaction of customized needs and flexibility of perceived data transmission is achieved.
Patent Information
- Application Number
- CN202310491030.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-04
- Publication Date
- 2024-11-05
AI Technical Summary
The prior art only supports the transmission of perceived data for specific perceived services, and cannot effectively solve the problem of perceived data transmission of customized perceived services.
By sending and receiving containers between communication devices, the container contains perceived data of perceived services, realizing the transmission of perceived data of customized perceived services.
When the operator or manufacturer has customized needs, the transmission of perceived data corresponding to the perceived service that meets the customized needs can be realized through containers, which expands the flexibility and adaptability of perceived data transmission.
Smart Images

Figure CN118900429A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of communication technology, and specifically relates to a data transmission method, device and communication equipment. Background Art
[0002] The 3rd Generation Partnership Project (3GPP) standard is responsible for standardizing the sensing data between the Radio Access Network (RAN) and the Sensing Function (SF), that is, standardizing how to transmit specific sensing data through specific parameters. 3GPP currently only supports the standardization of the transmission of sensing data for specific sensing services, that is, the existing solution can only transmit the sensing data of specific sensing services, and there is no relevant solution for how to transmit the sensing data of customized sensing services other than the above-mentioned specific sensing services. Summary of the invention
[0003] 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 a customized perception service.
[0004] In a first aspect, a data transmission method is provided, comprising:
[0005] The first device sends a container to the second device, where the container includes perception data of a perception service.
[0006] In a second aspect, a data transmission method is provided, comprising:
[0007] The second device obtains the container sent by the first device, where the container includes perception data of the perception service.
[0008] In a third aspect, a data transmission device is provided, including:
[0009] The first sending module is used to send a container to the second device, where the container includes perception data of the perception service.
[0010] In a fourth aspect, a data transmission device is provided, including:
[0011] 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.
[0012] In a 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.
[0013] 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 comprises perception data of a perception service.
[0014] 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.
[0015] 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 comprises perception data of a perception service.
[0016] In a 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.
[0017] 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.
[0018] In the eleventh aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect, or to implement the method described in the second aspect.
[0019] In the 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.
[0020] In an embodiment of the present application, the first device sends a container to the second device, and the container 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 realize the transmission of the perception data corresponding to the perception service that meets the customized requirements. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] Figure 1 A structural diagram showing a communication system to which the embodiments of the present application can be applied;
[0022] Figure 2 A schematic diagram showing the transmission architecture of perception data;
[0023] Figure 3 A schematic diagram showing a flow chart of a data transmission method according to an embodiment of the present application;
[0024] Figure 4 One of the interactive schematic diagrams showing the data transmission method according to an embodiment of the present application;
[0025] Figure 5 A second interactive schematic diagram showing the data transmission method according to an embodiment of the present application;
[0026] Figure 6 A second flowchart of the data transmission method according to an embodiment of the present application is shown;
[0027] Figure 7 One of the module schematic diagrams showing the data transmission device according to an embodiment of the present application;
[0028] Figure 8 A second schematic diagram showing a module of a data transmission device according to an embodiment of the present application;
[0029] Fig. 9 A structural block diagram showing a communication device according to an embodiment of the present application;
[0030] Fig.10 A structural block diagram showing a terminal according to an embodiment of the present application;
[0031] Fig.11 One of the structural block diagrams of the network side device of the embodiment of the present application is shown;
[0032] Fig.12 The second structural block diagram of the network side device of the embodiment of the present application. DETAILED DESCRIPTION
[0033] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.
[0034] The terms "first", "second", etc. of the present 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 one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0035] The term "indication" in this application can be 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, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.
[0036] 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 above-mentioned systems and radio technologies as well as other systems and radio technologies. The following description describes a new radio (NR) system for example purposes, and NR terms are used in most of the following descriptions, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.
[0037] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle-mounted device (Vehicle User Equipment, VUE), a ship-mounted device, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and 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 referred to as 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 may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B (home evolved Node B), a 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 terms. It should be noted that in the embodiments 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.
[0038] 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 (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unified Data Repository, UDR), home user server (Home Subscriber Server, HSS), centralized network configuration (CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc. 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.
[0039] In order to enable those skilled in the art to better understand the embodiments of the present application, the following description is now provided.
[0040] 1. Communication and perception integration / synaesthesia integration;
[0041] Among the related technologies, wireless communication and radar sensing (Communication & Sensing, C&S) have been developing in parallel, but with limited overlap. They have many commonalities in signal processing algorithms, equipment, and to a certain extent, system architecture. In recent years, the two systems have attracted more and more attention from researchers in terms of coexistence, cooperation, and joint design.
[0042] In the early days, people conducted extensive research on the coexistence of communication systems and radar systems, focusing on developing effective interference management techniques to enable two separately deployed systems to operate smoothly without interfering with each other. Although radar and communication systems may be co-located or even physically integrated, they transmit two different signals in the time / frequency domain. They share the same resources through cooperation to minimize the interference between each other when working simultaneously. Corresponding measures include beamforming, cooperative spectrum sharing, primary and secondary spectrum sharing, dynamic coexistence, etc. However, effective interference elimination usually has strict requirements on the mobility of nodes and the information exchange between nodes, so the improvement of spectrum efficiency is actually limited. Since the interference in the coexistence system is caused by the transmission of two independent signals, it is natural to ask whether we can use one transmission signal for communication and radar sensing at the same time. Radar systems usually use specially designed waveforms, such as short pulses and chirps, which enable high-power radiation and simplified receiver processing. However, these waveforms are not necessary for radar detection. Passive radar or passive sensing using different radio signals as sensing signals is a good example.
[0043] Machine learning, especially deep learning technology, further promotes the potential of non-dedicated radio signals for radar sensing. With these technologies, traditional radar is moving towards more general wireless sensing. Wireless sensing here can broadly refer to retrieving information from received radio signals instead of communication data modulated into the signal at the transmitter. For wireless sensing related to sensing the location of the target, the target signal reflection delay, angle of arrival (AoA), angle of departure (AoD), Doppler and other dynamic parameters can be estimated through common signal processing methods; for sensing the physical characteristics of the target, it can be achieved by measuring the inherent pattern signals of the device, object, and living things. The two sensing methods can be called perception parameter estimation and pattern recognition respectively. In this sense, wireless sensing refers to more general sensing technologies and applications using radio signals.
[0044] Integrated Sensing and Communication (ISAC) has the potential to integrate wireless sensing into large-scale mobile networks, where it becomes Perceptive Mobile Networks (PMNs). PMNs can evolve from the current 5G mobile network and are expected to become a ubiquitous wireless sensor network while providing stable and high-quality mobile communication services. It can be built on top of the existing mobile network infrastructure without major changes to the network structure and equipment. It will unleash the maximum capacity of mobile networks and avoid the high infrastructure costs of building new wide-area wireless sensor networks separately. With the expansion of coverage, the integrated communication and sensing capabilities are expected to enable many new applications. Perceptive mobile networks are able to provide both communication and wireless sensing services and have the potential to become a ubiquitous wireless sensing solution due to their large broadband coverage and strong infrastructure. Their jointly coordinated communication and sensing capabilities will improve the productivity of our society and help give rise to a large number of new applications that cannot be effectively implemented by existing sensor networks. Some early work on passive sensing using mobile signals has demonstrated its potential. Examples include traffic monitoring, weather forecasting, and rainfall remote sensing based on radio signals from the Global System for Mobile Communications (GSM). Sensing mobile networks can be widely used for communication and sensing in the fields of transportation, communications, energy, precision agriculture, and security, where existing solutions are either not feasible or inefficient. It can also provide complementary sensing capabilities to existing sensor networks, with unique day and night operation capabilities and the ability to penetrate fog, foliage, and even solid objects.
[0045] 2. Data transmission method of synaesthesia service;
[0046] like Figure 2In the architecture shown, the sensing function (SF) is a network element newly added for the synaesthesia service, which is responsible for managing the synaesthesia service and processing the synaesthesia data. SF can be a network element, that is, it is responsible for both the user plane and the control plane; it can also be two network elements, that is, the user plane (Sensing Function Control plane, SF-C) and the control plane (Sensing Function User plane, SF-U) are separated. Exemplarily, the sensing measurement (SensingMeasurement) includes delay, Doppler, angle, intensity, and their multi-dimensional combinations. The sensing result (Sensing Result) is the result obtained after SF processes the Sensing Measurement, such as intermediate processing results such as speed, distance, direction, acceleration, position, trajectory, and action. The sensing target (Sensing Objective) is the final result obtained by the application function (ApplicationFunction, AF), for example, car violations, road congestion, etc.
[0047] The data transmission method provided in the embodiment of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.
[0048] like Figure 3 As shown, an embodiment of the present application provides a data transmission method, including:
[0049] Step 301: The first device sends a container to the second device, wherein the container includes perception data of a perception service.
[0050] 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., a 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.
[0051] 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.
[0052] In an embodiment of the present application, the first device sends a container to the second device, and the container 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.
[0053] Optionally, the first device sending the container to the second device includes at least one of the following:
[0054] The first device sends an Internet Protocol (IP) packet to the second device, wherein the IP packet includes the container;
[0055] 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;
[0056] The first device sends a New Radio Sensing Protocol (NRSP) packet to the second device, where the NRSP packet includes the container;
[0057] It should be noted that NRSP is introduced using the 5G communication system as an example; in the 4G communication system, it may be the Long Term Evolution (LTE) Sensing Protocol (LSP); in the 6G communication system, it may be the 6G Sensing Protocol (6GSP), where 6G may change according to the naming of 6G, for example, when 6G is named NG (Next General), 6GSP is NGSP.
[0058] The first device sends a Non Access Stratum (NAS) message to the second device, where the NAS message includes the container.
[0059] 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 through the IP packet, the GTP packet, the NRSP packet or the NAS message.
[0060] Optionally, the first device sending the container to the second device includes:
[0061] The first device sends a private message (Private Message, PrivateMessage) to the second device, wherein the private message includes the container. The container may be a private information element container (Private Information Element Container, Private IE-Container).
[0062] Optionally, the first device sending the container to the second device includes:
[0063] 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;
[0064] 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;
[0065] 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.
[0066] 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.
[0067] Optionally, 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 (additional perception measurement amount); or, the perception measurement amount of the perception service includes an additional perception measurement amount.
[0068] In the embodiment of the present application, the universal perception measurement quantity may be a standardized perception measurement quantity, and the additional perception measurement quantity may be an unstandardized perception measurement quantity. For example, the universal perception measurement quantity is a perception measurement quantity that has been standardized in 3GPP, and the additional perception measurement quantity is a perception measurement quantity that has not been standardized in 3GPP. Alternatively, the universal perception measurement quantity may be a measurement quantity transmitted between the first device and the second device in a predefined transmission manner, for example, the first device may transmit data corresponding to the perception measurement quantity through a predefined parameter, and when the second device obtains the data carried by the parameter, it may learn the perception measurement quantity corresponding to the data.
[0069] Optionally, in a case where the perception measurement amount of the perception service includes an additional perception measurement amount, the method further includes:
[0070] 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.
[0071] 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 ID, and identifier. The following is the same and will not be repeated.
[0072] 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 an 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.
[0073] 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.
[0074] Optionally, the first device sends the container to the second device, including:
[0075] The first device negotiates with the second device to determine a transmission mode of the perception data of the perception service;
[0076] 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.
[0077] In an embodiment of the present application, the transmission method of the perception data includes transmitting the perception data through predefined parameters or transmitting the perception data through a container. The first device and the second device first negotiate to determine the transmission method of the perception data, and when it is determined that the transmission method of the perception data is to send the perception data of the perception service through a container, the first device sends the container to the second device.
[0078] 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:
[0079] 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;
[0080] 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.
[0081] Optionally, the first message may be a perception service request. After receiving the need to perform the perception service, the second device sends the perception service request to the first device. The need for the perception service may be triggered by an application function, by the second device itself, or by the first device or terminal.
[0082] Optionally, in the 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 used to transmit the perception data. In the 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 used to transmit the perception data.
[0083] 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.
[0084] Optionally, the first device sending a second message to the second device includes:
[0085] In the 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 perception data, the final transmission mode is determined by the second device.
[0086] 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.
[0087] Optionally, when 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.
[0088] In an embodiment of the present application, the service identifier corresponding to the perception service can be allocated by the first device or by 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.
[0089] Optionally, the implementation further includes:
[0090] The first device sends at least one of the following to the second device:
[0091] Supported sensing services;
[0092] Supported perceptual measurements;
[0093] Supported perceptual data transmission methods;
[0094] The sensing data transmission method includes: transmitting the sensing data through predefined parameters or transmitting the sensing data through a container.
[0095] In this implementation, the first device may send the above information by registering the perception service supported by the first device to the second device. Specifically, the registration information includes at least one of the following:
[0096] Supported perceptual measurements;
[0097] Supported transmission methods for sensory data;
[0098] Vendor information of the first device, such as a vendor identifier of the first device;
[0099] Token information supported by the first device.
[0100] 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.
[0101] The second device records the perception services supported by each first device or the transmission mode of the perception data supported by each first device according to the registration information. After receiving the demand for executing the perception service, the second device selects the first device according to the transmission mode of the perception data or the perception service supported by each first device, and sends the first message to the selected first device.
[0102] Optionally, the registration message may also be a notification message or a service request message.
[0103] Optionally, the first message further includes at least one of the following:
[0104] the sensing measurement quantity that needs to be reported by the first device;
[0105] The vendor information of the second device;
[0106] Token information of the second device.
[0107] Optionally, the first device sending a second message to the second device includes:
[0108] 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.
[0109] Optionally, the above-mentioned preset conditions include: the supplier of the second device is a pre-agreed supplier who 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.
[0110] The above implementation is described below in conjunction with embodiments.
[0111] In this embodiment, the first device is RAN and the second device is SF. Figure 4 As shown, this embodiment includes:
[0112] Step 401: RAN registers the awareness services it supports with SF. The registration information includes the following information:
[0113] Supported transmission methods for sensor data.
[0114] Optionally, the registration information may further include at least one of the following:
[0115] Supported perceptual measurements;
[0116] The vendor ID of the RAN;
[0117] Token supported by RAN.
[0118] This step 401 is an optional step.
[0119] Step 402: The SF records the perception services supported by each RAN and the transmission modes of the perception data supported by each RAN.
[0120] This step 402 is an optional step.
[0121] Step 403: The SF receives a demand for executing the sensing service and selects a RAN according to the demand for the sensing service.
[0122] The requirement may be triggered by the AF, the SF itself, the RAN or the UE.
[0123] If the above steps 401 and 402 are performed, the SF selects the RAN according to the capabilities of each RAN (supported perception services and supported transmission methods of perception data).
[0124] Step 404: The SF sends a sensing service request to the selected RAN.
[0125] The sensing service request includes the following information:
[0126] The sensing service being executed or the service identifier corresponding to the sensing service;
[0127] The transmission method of the sensing data requested or supported by the SF.
[0128] 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 a container), the SF further indicates which measurement quantities correspond to the perception data to be transmitted through the container.
[0129] Optionally, the above-mentioned perception service request further includes at least one of the following:
[0130] The perception measurements that need to be reported by the RAN;
[0131] SF's vendor ID, i.e. SF's own vendor information;
[0132] SF's token information, that is, the token owned by SF itself.
[0133] Step 405: The RAN determines to reply with a perception service configuration response according to whether it supports the perception service corresponding to the perception service request and the transmission mode of the perception data. The perception configuration service response includes a confirmation message or a rejection message.
[0134] If the RAN supports the transmission mode of the perception service and perception data corresponding to the perception 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 perception service and perception data corresponding to the perception service request, a rejection message is determined to be returned.
[0135] 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).
[0136] Step 406: RAN collects and processes the perception data.
[0137] Step 407: RAN sends the acquired sensing data to SF.
[0138] For common sensing measurements, when RAN sends sensing data to SF, it uses predefined parameters to send;
[0139] For additional sensing measurements, container transport is used.
[0140] Specifically, using container transmission includes the following two solutions:
[0141] Solution 1: Data of multiple sensing services of RAN are transmitted through one container. Different sensing services are distinguished in the container by using sensing service ID + sensing data.
[0142] 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.
[0143] For a specific sensing service, a portion of the sensing data corresponding to the sensing measurement quantity may be transmitted using predefined parameters, and another portion of the sensing data corresponding to the additional sensing measurement quantity may be transmitted through a container, and the two portions of data may be associated using the sensingService id.
[0144] For example, the perception measurement quantities corresponding to a certain perception service are X1 and X2. In order to improve the accuracy, the perception measurement quantities X3 and X4 are customized.
[0145] For common RAN equipment, only X1 and X2 need to be transmitted through a predefined message format.
[0146] For customized RAN equipment, in addition to transmitting X1 and X2 through the predefined message format, X3 and X4 are also transmitted through the container. SF associates X1, X2, X3 and X4 according to the sensing Service id and processes them together.
[0147] The container can be carried in a GTP message, an IP packet, an NRSP packet or a NAS message.
[0148] For RAN-SF architecture: The container is contained in a GTP message, IP packet or NRSP packet.
[0149] For the RAN-UPF-SF architecture: the container is contained in an IP packet or an NRSP packet.
[0150] For RAN-AMF-SF architecture: the container is included in the NAS signaling or NRSP packet.
[0151] 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.
[0152] In the above step 404, the SF allocates the sensing service id as an example for explanation. It can also be allocated by the RAN. In this case, the sensing service id is not carried in step 404. After receiving step 404, the RAN allocates it and sends it to the SF in step 405.
[0153] It should be noted that between step 403 and step 404, SF may first request RAN for the supported transmission mode of perception data, vender ID or token, and SF sends step 404 according to the information obtained from RAN. This step may replace the above steps 401 and 402.
[0154] 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:
[0155] 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;
[0156] 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;
[0157] 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.
[0158] Optionally, the implementation further includes:
[0159] 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.
[0160] The ninth message may specifically be perception service configuration information.
[0161] Optionally, the ninth message further includes at least one of the following:
[0162] the sensing measurement quantity that needs to be reported by the first device;
[0163] The vendor information of the second device;
[0164] Token information.
[0165] Optionally, the first device sending the container to the second device includes:
[0166] 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.
[0167] Optionally, the above-mentioned preset conditions include: the supplier of the second device is a pre-agreed supplier who 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.
[0168] The implementation is described below in conjunction with an embodiment.
[0169] In this embodiment, the first device is RAN and the second device is SF. Figure 5 As shown, this embodiment includes:
[0170] Step 501: SF receives a request to execute a sensing service and selects RAN.
[0171] The requirement may be triggered by the AF, the SF itself, the RAN or the UE.
[0172] Optionally, the SF may select the RAN according to the location information.
[0173] Step 502: The SF sends the awareness service configuration information to the selected RAN.
[0174] 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.
[0175] Optionally, the perception service configuration information further includes at least one of the following:
[0176] The perception measurements that need to be reported by the RAN;
[0177] SF's vendor ID, i.e. SF's own vendor information;
[0178] SF's token information, that is, the token owned by SF itself.
[0179] Step 503: RAN sends the supported transmission mode of the perception data to SF for the service.
[0180] For example, the RAN lists all the transmission modes of the perception data supported by it. The transmission modes of the perception data supported by the RAN may be sent to the SF via a perception transmission mode request message.
[0181] Alternatively, when the RAN determines that the perception service can be transmitted through predefined parameters, the RAN asks the SF whether it supports transmitting the perception data corresponding to the additional perception measurement quantity through the container;
[0182] Alternatively, when the RAN determines that the perception service does not support transmission through predefined parameters, the RAN inquires whether it supports transmitting the perception data corresponding to the perception measurement amount through the container.
[0183] Step 504: SF sends the determined transmission mode of the sensing data.
[0184] The SF may send the transmission mode of the sensing data determined by the SF through a sensing transmission mode response message.
[0185] Step 505: RAN sends an awareness service configuration response message, where the awareness service configuration response message includes an acceptance message or a rejection message.
[0186] Among them, the acceptance message in the perception service configuration response message indicates that the RAN agrees with the transmission method of the perception data determined by the SF, and the rejection message indicates that the RAN disagrees with the transmission method of the perception data determined by the SF.
[0187] Subsequent process is the same as Figure 4 Steps 406 to 408 in the illustrated embodiment.
[0188] It should be noted that, in this embodiment, step 503 and step 504 are described by taking the example that SF finally determines the transmission method of 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 perception data.
[0189] In the data transmission method of the embodiment of the present application, the first device sends a container to the second device, and the container 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 realize the transmission of the perception data corresponding to the perception service that meets the customized requirements.
[0190] like Figure 6 As shown, the embodiment of the present application also provides a data transmission method, including:
[0191] Step 601: The second device obtains a container sent by the first device, where the container includes perception data of a perception service.
[0192] 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.
[0193] 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.
[0194] In an embodiment of the present application, the second device obtains a container sent by the first device, and the container 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.
[0195] Optionally, the second device obtains the container sent by the first device, including at least one of the following:
[0196] The second device obtains an Internet Protocol IP packet sent by the first device, where the IP packet includes the container;
[0197] 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;
[0198] The second device obtains a New Radio Interface Perception Protocol (NRSP) packet sent by the first device, where the NRSP packet includes the container;
[0199] The second device obtains a non-access stratum NAS message sent by the first device, where the NAS message includes the container.
[0200] Optionally, the second device obtains the container sent by the first device, including:
[0201] 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;
[0202] 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;
[0203] 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.
[0204] Optionally, 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.
[0205] Optionally, in a case where the perception measurement amount of the perception service includes an additional perception measurement amount, the method further includes:
[0206] 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.
[0207] Optionally, the method of the embodiment of the present application further includes:
[0208] The first device negotiates with the second device to determine a transmission mode of the perception data of the perception service;
[0209] 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.
[0210] Optionally, the first device negotiates with the second device to determine a transmission mode of the perception data of the perception service, including:
[0211] 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;
[0212] 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.
[0213] 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.
[0214] Optionally, when 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.
[0215] Optionally, the second device sending a first message to the first device includes:
[0216] The second device obtains the tenth message sent by the first device;
[0217] The second device sends the first message to the first device according to the tenth message;
[0218] The tenth message includes at least one of the following:
[0219] Supported sensing services;
[0220] Supported perceptual measurements;
[0221] Supported perceptual data transmission methods;
[0222] The sensing data transmission method includes: transmitting the sensing data through predefined parameters or transmitting the sensing data through a container.
[0223] Optionally, the first device negotiates with the second device to determine a transmission mode of the perception data of the perception service, including:
[0224] 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;
[0225] 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;
[0226] 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.
[0227] Optionally, the method of the embodiment of the present application further includes:
[0228] 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.
[0229] 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, and 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.
[0230] In an embodiment of the present application, the second device obtains a container sent by the first device, and the container 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.
[0231] 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 executed by a data transmission device is taken as an example to illustrate the data transmission device provided in the embodiment of the present application.
[0232] like Figure 7 As shown, an embodiment of the present application provides a data transmission device 700, which is applied to a first device, and the device includes:
[0233] 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.
[0234] Optionally, the first sending module is used to perform at least one of the following:
[0235] Sending an Internet Protocol IP packet to the second device, wherein the IP packet includes the container;
[0236] Sending a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) packet to the second device, where the GTP packet includes the container;
[0237] Sending a New Air Interface Perception Protocol (NRSP) packet to the second device, where the NRSP packet includes the container;
[0238] A non-access stratum (NAS) message is sent to the second device, where the NAS message includes the container.
[0239] Optionally, 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;
[0240] Alternatively, N1 containers and N1 perception service identifiers are sent 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;
[0241] 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.
[0242] Optionally, 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.
[0243] Optionally, in a case where the perception measurement amount of the perception service includes an additional perception measurement amount, the method further includes:
[0244] 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.
[0245] Optionally, the first sending module includes:
[0246] a negotiation submodule, configured to negotiate with the second device to determine a transmission mode of the perception data of the perception service;
[0247] The first sending submodule is configured to send the container to the second device when it is determined that the sensing data of the sensing service is sent through the container.
[0248] Optionally, the negotiation submodule includes:
[0249] 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 perception data requested or supported by the second device;
[0250] The second sending submodule is used 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.
[0251] Optionally, the second sending submodule is used to send the second message to the second device when the first device supports the transmission mode of the perception data requested or supported by the second device, and 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.
[0252] 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.
[0253] Optionally, when 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.
[0254] Optionally, the device of the embodiment of the present application further includes:
[0255] A second sending module is configured to send at least one of the following to the second device:
[0256] Supported sensing services;
[0257] Supported perceptual measurements;
[0258] Supported perceptual data transmission methods;
[0259] The sensing data transmission method includes: transmitting the sensing data through predefined parameters or transmitting the sensing data through a container.
[0260] Optionally, the first message further includes at least one of the following:
[0261] the sensing measurement quantity that needs to be reported by the first device;
[0262] The vendor information of the second device;
[0263] Token information of the second device.
[0264] 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.
[0265] Optionally, the negotiation submodule is used for:
[0266] Sending a third message to the second device, the third message including a transmission mode of the perception data supported by the first device; acquiring 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;
[0267] 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; a sixth message sent by the second device is obtained, where the sixth message includes a transmission method of the perception data of the perception service determined by the second device according to the fifth message;
[0268] Alternatively, a seventh message is sent to the second 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; an eighth message is obtained from the second device, wherein 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 according to the eighth message.
[0269] Optionally, the first sending module further includes:
[0270] 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.
[0271] Optionally, the ninth message further includes at least one of the following:
[0272] the sensing measurement quantity that needs to be reported by the first device;
[0273] The vendor information of the second device;
[0274] Token information of the second device.
[0275] Optionally, the first sending submodule is used for, 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 sending the container to the second device.
[0276] Optionally, the first device is a wireless access network device or a terminal, and the second device is a perception function network element device.
[0277] In an embodiment of the present application, the first device sends a container to the second device, and the container 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.
[0278] like Figure 8 As shown, an embodiment of the present application provides a data transmission device 800, which is applied to a second device, and the device includes:
[0279] The first acquisition module 801 is configured to acquire a container sent by a first device, wherein the container includes perception data of a perception service.
[0280] Optionally, the first acquisition module is used to perform at least one of the following:
[0281] Acquire an Internet Protocol IP packet sent by the first device, wherein the IP packet includes the container;
[0282] Acquire a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) packet sent by the first device, where the GTP packet includes the container;
[0283] Obtain a New Air Interface Perception Protocol (NRSP) packet sent by the first device, where the NRSP packet includes the container;
[0284] Obtain a non-access stratum NAS message sent by the first device, where the NAS message includes the container.
[0285] Optionally, the first acquisition module is used to:
[0286] Acquire 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;
[0287] Alternatively, obtaining 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;
[0288] Alternatively, N2 containers sent by the first device are obtained, 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.
[0289] Optionally, 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.
[0290] Optionally, when the perception measurement amount of the perception service includes an additional perception measurement amount, the apparatus further includes:
[0291] The second acquisition module is used to acquire 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 through predefined parameters.
[0292] Optionally, the device of the embodiment of the present application further includes:
[0293] a negotiation module, configured to negotiate with the second device to determine a transmission mode of the perception data of the perception service;
[0294] 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.
[0295] Optionally, the negotiation module includes:
[0296] A transmission submodule, configured to send a first message to the first device, wherein the first message includes: a transmission mode of the perception data requested or supported by the second device;
[0297] The third acquisition submodule is used 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.
[0298] 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.
[0299] Optionally, when 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.
[0300] Optionally, the transmission submodule includes:
[0301] A fourth acquisition submodule, used to acquire a tenth message sent by the first device;
[0302] A third sending submodule, configured to send the first message to the first device according to the tenth message;
[0303] The tenth message includes at least one of the following:
[0304] Supported sensing services;
[0305] Supported perceptual measurements;
[0306] Supported perceptual data transmission methods;
[0307] The sensing data transmission method includes: transmitting the sensing data through predefined parameters or transmitting the sensing data through a container.
[0308] Optionally, the negotiation module is used to:
[0309] Acquire 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; send 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;
[0310] Alternatively, obtaining a fifth message sent by the first device, the fifth message being used to inquire whether the second device supports transmission of perception data through a container; sending a sixth message to the first device, the sixth message including a transmission mode of the perception data of the perception service determined by the second device according to the fifth message;
[0311] 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; 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.
[0312] Optionally, the negotiation module further includes:
[0313] 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.
[0314] In an embodiment of the present application, the second device obtains a container sent by the first device, and the container 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.
[0315] The data transmission device in the embodiment of the present application may 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 a chip. The electronic device may be a terminal, or may be other devices other than a terminal. For example, the terminal may include but is not limited to the types of the terminal 11 listed above, and other devices may be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.
[0316] The data transmission device provided in the embodiment of the present application can achieve Figures 3 to 6The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.
[0317] Optional, such as Fig. 9 As shown, the embodiment of the present application further provides a communication device 900, including a processor 901 and a memory 902, and 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 executed by the first device, and can achieve the same technical effect. When the communication device 900 is a SF, the program or instruction is executed by the processor 901 to implement the various steps of the method embodiment executed by the second device, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0318] The embodiment of the present application also provides a first device, including a processor and a communication interface, the communication interface is used to send a container to a second device, the container including the perception data of the perception service. The first device embodiment corresponds to the first device side method embodiment described above, and each implementation process and implementation method of the method embodiment described above can be applied to the first device embodiment and can achieve the same technical effect. Specifically, Fig.10 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.
[0319] 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 a processor 1010.
[0320] Those skilled in the art will appreciate that the terminal 1000 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 1010 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.10 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.
[0321] It should be understood that in the 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 the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the 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 a joystick, which will not be repeated here.
[0322] In the embodiment of the present application, after receiving downlink data from the network side device, the RF unit 1001 can transmit the data to the processor 1010 for processing; in addition, the RF unit 1001 can send uplink data to the network side device. Generally, the RF unit 1001 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
[0323] 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, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), 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.
[0324] The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1010.
[0325] The radio frequency unit 1001 is used to send a container to the second device, where the container includes perception data of the perception service.
[0326] Optionally, the radio frequency unit 1001 is configured to perform at least one of the following:
[0327] Sending an Internet Protocol IP packet to the second device, wherein the IP packet includes the container;
[0328] Sending a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) packet to the second device, where the GTP packet includes the container;
[0329] Sending a New Air Interface Perception Protocol (NRSP) packet to the second device, where the NRSP packet includes the container;
[0330] A non-access stratum (NAS) message is sent to the second device, where the NAS message includes the container.
[0331] Optionally, the radio frequency unit 1001 is used for:
[0332] Sending 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;
[0333] Alternatively, N1 containers and N1 perception service identifiers are sent 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;
[0334] 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.
[0335] Optionally, 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.
[0336] 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:
[0337] The data corresponding to the universal perception measurement amount of the perception service and the service identifier corresponding to the perception service are sent to the second device through predefined parameters.
[0338] 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.
[0339] 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 according to the first message.
[0340] 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.
[0341] 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.
[0342] Optionally, when 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.
[0343] Optionally, the radio frequency unit 1001 is configured to send at least one of the following to the second device:
[0344] Supported sensing services;
[0345] Supported perceptual measurements;
[0346] Supported perceptual data transmission methods;
[0347] The sensing data transmission method includes: transmitting the sensing data through predefined parameters or transmitting the sensing data through a container.
[0348] Optionally, the first message further includes at least one of the following:
[0349] the sensing measurement quantity that needs to be reported by the first device;
[0350] The vendor information of the second device;
[0351] Token information of the second device.
[0352] 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.
[0353] Optionally, the radio frequency unit 1001 is used 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;
[0354] 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; a sixth message sent by the second device is obtained, where the sixth message includes a transmission method of the perception data of the perception service determined by the second device according to the fifth message;
[0355] Alternatively, a seventh message is sent to the second 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; an eighth message sent by the second device is obtained, wherein 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 according to the eighth message.
[0356] Optionally, the radio frequency unit 1001 is used to: obtain a ninth message sent by the second device, where the ninth message includes a perception service executed by the second device or a service identifier corresponding to the perception service executed by the second device.
[0357] Optionally, the ninth message further includes at least one of the following:
[0358] the sensing measurement quantity that needs to be reported by the first device;
[0359] The vendor information of the second device;
[0360] Token information of the second device.
[0361] 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 the token information meets a preset condition, send the container to the second device.
[0362] Optionally, the second device is a perception function network element device.
[0363] In an embodiment of the present application, a container is sent to the second device, and the container 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.
[0364] The embodiment of the present application also provides a network side device, including a processor and a communication interface, the communication interface is used to send a container to a second device, the container includes the perception data of the perception service, or to obtain a container sent by a first device, the container includes the perception data of the perception service. The 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 the network side device embodiment, and can achieve the same technical effect.
[0365] Specifically, the embodiment of the present application also provides a network side device. Fig.11 As shown, 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. The antenna 111 is connected to the radio frequency device 112. In the uplink direction, the radio frequency device 112 receives information through the antenna 111 and sends the received information to the baseband device 113 for processing. In the downlink direction, the baseband device 113 processes the information to be sent and sends it to the radio frequency device 112, and the radio frequency device 112 processes the received information and sends it out through the antenna 111.
[0366] The method executed by the first device in the above embodiment may be implemented in the baseband device 113, which includes a baseband processor.
[0367] The baseband device 113 may include, for example, at least one baseband board on which a plurality of chips are arranged. Fig.11 As shown, 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 execute the operation of the first device shown in the above method embodiment.
[0368] The network side device may further include a network interface 116, which is, for example, a Common Public Radio Interface (CPRI).
[0369] Specifically, the network side device 1100 of the embodiment of the present invention further includes: instructions or programs stored in the memory 115 and executable on the processor 114, and the processor 114 calls the instructions or programs in the memory 115 to execute Figure 7 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.
[0370] Specifically, the embodiment of the present application also provides a network side device. Fig.12As shown, 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).
[0371] Specifically, the network side device 1200 of the embodiment of the present invention further includes: instructions or programs stored in the memory 1203 and executable on the processor 1201, and the processor 1201 calls the instructions or programs in the memory 1203 to execute Figure 8 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.
[0372] 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.
[0373] 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-transient readable storage medium.
[0374] 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.
[0375] 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.
[0376] The embodiments of the present application further provide a computer program / program product, which is stored in a storage medium and 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 described here.
[0377] 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.
[0378] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out 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 reverse 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.
[0379] Through the description of the above implementation methods, 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 hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.
[0380] 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 the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.
Claims
1. A data transmission method, characterized in that: include: 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, characterized in that: 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, characterized in that: 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, characterized in that: 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, characterized in that 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, characterized in that: 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 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.
7. The method according to claim 6, characterized in that 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, characterized in that 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, characterized in that: 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, characterized in that 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, characterized in that: The method further comprises: 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, characterized in that: 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, characterized in that 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, characterized in that 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, characterized in that Also includes: 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that: include: 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that The method further comprises: 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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 according to claim 24, characterized in that 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 according to claim 29, characterized in that Also includes: 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, characterized in that: include: 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, characterized in that 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, characterized in that 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 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, 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, characterized in that: include: 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, characterized in that: It includes a processor and a memory, 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, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it 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.
