A communication method and apparatus

Abstract

A communication method and apparatus are disclosed. In the method: receiving first information, the first information indicating compression parameters for a sensing service, the compression parameters including one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, and area or angle range corresponding to each beam; determining a first strategy based on the compression parameters and the requirements of the first service, the first service being one of the sensing services, the first strategy being used to compress the data of the first service; and transmitting the first strategy. Since the first compression strategy is determined based on the compression parameters supported by the first apparatus, the first compression strategy can be executed by the first apparatus; furthermore, since the first compression strategy is determined based on the requirements of the sensing service, the sensing service data compressed according to the first compression strategy can meet the requirements of the sensing service.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] Communication and sensing based on cellular networks is one of the future trends in mobile communication technology. Figure 1 An exemplary perception service in a traffic scenario is illustrated: Vehicle-mounted terminal device 1 receives perception signals from a certain area. These signals may have been sent by vehicle-mounted terminal device 1 in a previous moment, by a base station, or by other vehicle-mounted terminal devices. After processing the perception signals, vehicle-mounted terminal device 1 obtains raw perception data (e.g., spectral information of wireless signals). Considering the limited computing power and sensitivity to power consumption of vehicle-mounted terminal devices, vehicle-mounted terminal device 1 can transmit the perception data back to the network side for processing, for example, by transmitting it to a sensing function (SF) network element via a base station, where the SF processes and analyzes the perception data.

[0003] Sensing data is characterized by its large volume and high bandwidth requirements, and the need for compression varies depending on the type of sensing service, the number of sensing beams, and the sensing resolution. Therefore, how to compress sensing data is a pressing technical problem that needs to be solved. Summary of the Invention

[0004] This application provides a communication method and apparatus for determining compression methods / compression parameters of sensing data in a sensing service scenario.

[0005] In a first aspect, embodiments of this application provide a communication method applied to a first device, or a communication module / processing module in the first device, or a circuit or chip in the first device responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core or a system-in-package (SIP) chip), or a circuit or chip in a network device or terminal device responsible for processing functions (such as a graphics processing unit (GPU), an artificial intelligence (AI) processor, or an application-specific integrated circuit (ASIC)).

[0006] Taking the application of this method to a first device as an example, in this method, first information is sent, which is used to indicate the compression parameters of the sensing service. The compression parameters include one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, or, the area or angle range corresponding to each beam; a first strategy is received, which is determined according to the compression parameters and the requirements of the first service, where the first service is one of the sensing services, and the first strategy is used to compress the data of the first service.

[0007] Optionally, the first device mentioned above is a wireless access network device.

[0008] In the above method, the first device first reports the compression parameters of the sensing services it supports, thereby obtaining a compression strategy determined based on the compression parameters supported by the first device and the requirements of the sensing services. Since the compression strategy is determined based on the compression parameters supported by the first device, it can be executed by the first device; and since the compression strategy is determined based on the requirements of the sensing services, the sensing service data compressed by the first device according to the compression strategy can meet the requirements of the sensing services.

[0009] In one possible implementation, the method further includes: receiving first indication information, the first indication information being used to instruct the data of the first service to be compressed according to the first strategy. In the above implementation, the first device compresses the data of the first service according to the first strategy after receiving the first indication information; if the first strategy is received but the first indication information is not received, the first device may store the first strategy first, but does not need to compress the data of the first service according to the first strategy.

[0010] In one possible implementation, the first strategy includes compression configuration and / or compression requirements; the compression configuration includes one or more of the following: the compression mode of the first service, the data type of the first service, the compression algorithm of the first service, or the parameters of the compression algorithm of the first service; the compression requirements include one or more of the following: bandwidth requirements, compression quality requirements, or compression latency requirements. After obtaining the above compression configuration and / or compression requirements, the first device can compress the data of the first service according to the above compression configuration and / or compression requirements, which helps to ensure that the compressed data can meet the requirements of the first service, such as compression quality and compression latency requirements.

[0011] In one possible implementation, the requirements of the first service include one or more of the following: the type of the first service, the resolution requirement of the first service, the frequency requirement of the first service, the beam count requirement of the first service, or the area or angular range requirement of the first service. The first strategy acquired by the first device is determined based on the aforementioned requirements of the first service, such that the data obtained by the first device after compressing the data of the first service according to the first strategy can meet the requirements of the first service for resolution, reporting frequency, data accuracy, beam count, beam area, or angular range.

[0012] In one possible implementation, the method further includes: sending second information, the second information including data of the first service compressed according to the first strategy. Upon receiving the first strategy, the first device, when it needs to report data of the first service, compresses the data of the first service according to the first strategy and reports the compressed data to the second device.

[0013] In one possible implementation, the second information further includes auxiliary information used to decompress the data of the first service. The auxiliary information includes one or more of the following: the range of the first service data, the transmission beam corresponding to the first service data, or the region or angle range corresponding to the transmission beam. In this implementation, in addition to reporting the compressed data, the first device can also send auxiliary information for decompression to the second device, enabling the second device to conveniently decompress the received data using the auxiliary information.

[0014] Optionally, the second device can be SF.

[0015] In one possible implementation, the method further includes: receiving third information, the third information indicating compression parameters for a sensing service, the compression parameters including one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, or, the area or angle range corresponding to each beam; determining a second strategy based on the compression parameters and the requirements of the first service, the second strategy being used to compress the data of the first service; and sending the second strategy. In this implementation, the first device may also obtain compression parameters for sensing services supported by the third device, and then determine and send the second strategy to the third device based on the requirements of the first service and the compression parameters supported by the third device, thereby enabling the third device to compress the data of the first service according to the second strategy, and ensuring that the compressed data meets the requirements of the first service.

[0016] Optionally, the third device can be a terminal device.

[0017] In one possible implementation, the method further includes: sending a second instruction message, the second instruction message being used to instruct the data of the first service to be compressed according to the second strategy. Using the above implementation, the first device can first send the compression strategies of each sensing service to the third device, and when compression is required, instruct the third device to compress the data according to the corresponding compression strategy via the second instruction message.

[0018] In one possible implementation, the method further includes: receiving fourth information, the fourth information including first data, the first data being data of the first service type compressed according to the second strategy; and sending fifth information, the fifth information including second data, the second data being data obtained by compressing the first data according to the first strategy. In the above implementation, the third device compresses the data of the first service according to the second strategy and sends the compressed data to the first device. The first device then performs a second compression on the compressed data according to the first strategy and sends the second compressed data to the second device. That is, the first device and the third device jointly complete the compression and reporting of the first service data. Since the data of the first service is compressed by the third device and the first device, it helps to further reduce the data transmission volume, thereby helping to improve the throughput of the second device.

[0019] In one possible implementation, the fourth information further includes first auxiliary information, which is used to decompress the first data. The first auxiliary information includes one or more of the following: the range of the first data, the transmission beam corresponding to the first data, or the region or angle range corresponding to the transmission beam. In this implementation, the fourth message received by the first device may include, in addition to the compressed data, auxiliary information for decompression, facilitating the data receiving end (such as the second device or the first device) to conveniently decompress the received data based on the auxiliary information.

[0020] In one possible implementation, the fifth information further includes second auxiliary information determined based on the first auxiliary information. The second auxiliary information is used to decompress the second data. The second auxiliary information includes one or more of the following: the range of the first data, the transmission beam corresponding to the first data, or the region or angle range corresponding to the transmission beam. In this implementation, since the fourth message received by the first device includes the first auxiliary information for decompression, when the first device sends the compressed data to the second device, it can generate the second auxiliary information based on the first auxiliary information and send it to the second device, facilitating convenient decompression of the received data by the second device based on the auxiliary information.

[0021] Secondly, embodiments of this application provide a communication method applied to a third device, or a communication module / processing module in the third device, or a circuit or chip in the third device responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core or a system-in-package (SIP) chip), or a circuit or chip in a network device or terminal device responsible for processing functions (such as a graphics processing unit (GPU), an artificial intelligence (AI) processor, or an application-specific integrated circuit (ASIC)).

[0022] Taking the application of this method to a third device as an example, in this method, first information is sent, which is used to indicate the compression parameters of the sensing service. The compression parameters include one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, or, the area or angle range corresponding to each beam; a first strategy is received, which is determined according to the compression parameters and the requirements of the first service, where the first service is one of the sensing services, and the first strategy is used to compress the data of the first service.

[0023] Optionally, the aforementioned third device is a terminal device.

[0024] In the above method, the third device first reports the compression parameters of the sensing services it supports, thereby obtaining a compression strategy determined based on the compression parameters supported by the third device and the requirements of the sensing services. Since this compression strategy is determined based on the compression parameters supported by the third device, it can be executed by the first device; and since this compression strategy is determined based on the requirements of the sensing services, the sensing service data compressed by the third device according to this compression strategy can meet the requirements of the sensing services.

[0025] In one possible implementation, the method further includes: receiving first indication information, the first indication information being used to instruct the data of the first service to be compressed according to the first strategy. In the above implementation, the third device compresses the data of the first service according to the first strategy after receiving the first indication information; if the first strategy is received but the first indication information is not received, the third device may store the first strategy first, but does not need to compress the data of the first service according to the first strategy.

[0026] In one possible implementation, the first strategy includes compression configuration and / or compression requirements; the compression configuration includes one or more of the following: the compression mode of the first service, the data type of the first service, the compression algorithm of the first service, or the parameters of the compression algorithm of the first service; the compression requirements include one or more of the following: bandwidth requirements, compression quality requirements, or compression latency requirements. After obtaining the above compression configuration and / or compression requirements, the third device can compress the data of the first service according to the above compression configuration and / or compression requirements, which helps to ensure that the compressed data can meet the requirements of the first service, such as compression quality and compression latency requirements.

[0027] In one possible implementation, the requirements of the first service include one or more of the following: the type of the first service, the resolution requirement of the first service, the frequency requirement of the first service, the beam count requirement of the first service, or the area or angular range requirement of the first service. The first strategy acquired by the third device is determined based on the aforementioned requirements of the first service, such that the data obtained by the third device after compressing the data of the first service according to the first strategy can meet the requirements of the first service for resolution, reporting frequency, data accuracy, beam count, beam area, or angular range.

[0028] In one possible implementation, the method further includes: sending second information, the second information including data of the first service compressed according to the first strategy. Upon receiving the first strategy, the third device, when it needs to report data of the first service, compresses the data of the first service according to the first strategy and reports the compressed data to the second device.

[0029] In one possible implementation, the second information further includes auxiliary information used to decompress the data of the first service. The auxiliary information includes one or more of the following: the range of the first service data, the transmission beam corresponding to the first service data, or the region or angle range corresponding to the transmission beam. In this implementation, in addition to reporting the compressed data, the third device can also send the auxiliary information for decompression to the second device, enabling the second device to conveniently decompress the received data using the auxiliary information.

[0030] Optionally, the second device can be SF.

[0031] Thirdly, embodiments of this application provide a communication method applied to a second device. The second device in this application can be a network device or a terminal device, or a communication module / processing module within the network device or terminal device, or a circuit or chip responsible for communication functions within the network device or terminal device (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip), or a circuit or chip responsible for processing functions within the network device or terminal device (such as a graphics processing unit (GPU), an artificial intelligence (AI) processor, or an application-specific integrated circuit (ASIC)).

[0032] Taking the application of this method to a second device as an example, in this method: receiving first information, the first information is used to indicate compression parameters of the sensing service, the compression parameters including one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, or, the area or angle range corresponding to each beam; determining a first strategy according to the compression parameters and the requirements of the first service, the first service being one of the sensing services, the first strategy being used to compress the data of the first service; and sending the first strategy.

[0033] Optionally, the second device mentioned above can be an SF.

[0034] In the above method, the second device can acquire the compression parameters of the access network device or terminal device, and then determine the compression strategy for the corresponding sensing service based on the compression parameters of the access network device or terminal device and the requirements of the sensing service, and send the compression strategy to the access network device or terminal device. On the one hand, the compression strategy is determined based on the compression parameters supported by the access network device or terminal device, therefore, the compression strategy can be executed by the access network device or terminal device; on the other hand, the compression strategy is determined based on the requirements of the sensing service, therefore, the sensing service data compressed according to the compression strategy can meet the requirements of the sensing service.

[0035] In one possible implementation, the method further includes: sending first instruction information, which instructs the data of the first service to be compressed according to the first strategy. The first instruction information may be sent to the first device together with the first strategy; alternatively, it may be sent to the first device after sending the first strategy. The second device may first send the compression strategies for each sensing service to the first device, and then, when compression is required, instruct the first device to compress the data according to the corresponding compression strategy via the instruction information, which facilitates data management by the second device.

[0036] In one possible implementation, the first strategy includes compression configuration and / or compression requirements; the compression configuration includes one or more of the following: the compression mode of the first service, the data type of the first service, the compression algorithm of the first service, or the parameters of the compression algorithm of the first service; the compression requirements include one or more of the following: bandwidth requirements, compression quality requirements, or compression latency requirements. The second device sends the above compression configuration and / or compression requirements to the first device, causing the first device to compress the data of the first service according to the above compression configuration and / or compression requirements, which helps to ensure that the compressed data meets the requirements of the first service, such as compression quality and compression latency requirements.

[0037] In one possible implementation, the requirements of the first service include one or more of the following: the type of the first service, the resolution requirement of the first service, the frequency requirement of the first service, the accuracy requirement of the first service, the number of beams requirement of the first service, or the area or angular range requirement of the first service. The second device determines a first strategy based on the aforementioned requirements of the first service, such that the determined first strategy can meet the requirements of the first service for resolution, reporting frequency, data accuracy, number of beams, and beam area or angular range.

[0038] In one possible implementation, the method further includes: receiving second information, the second information including data of the first service compressed according to the first strategy. After sending the first strategy to the first device, the second device can receive the data of the first service compressed by the first device according to the first strategy. Although the received data has been compressed, it can still meet the requirements of the first service, and then the received data can be processed.

[0039] In one possible implementation, the second information further includes auxiliary information used to decompress the data of the first service. The auxiliary information includes one or more of the following: the range of the first service data, the transmission beam corresponding to the first service data, or the region or angle range corresponding to the transmission beam. In this implementation, the second information received by the second device not only includes the compressed data but may also include auxiliary information for decompression, enabling the second device to conveniently decompress the received data based on the auxiliary information.

[0040] Fourthly, a communication device is provided. The communication device includes: a processing unit configured to execute the first aspect and any possible method thereof, or to execute the second aspect and any possible method thereof, or to execute the third aspect and any possible implementation thereof.

[0041] In some implementations, the communication device described in the fourth aspect may further include a transceiver unit. This transceiver unit may include a transmitting unit and a receiving unit. The transceiver unit can be used for communication between the communication device described in the fourth aspect and other communication devices.

[0042] In one possible implementation, the communication device described in the fourth aspect may further include a storage unit. This storage unit may be integrated with the processing unit or may be separate. The storage unit may be used to store computer programs and / or data involved in the method of the first aspect or any embodiment thereof, or computer programs and / or data involved in the method of the second aspect or any embodiment thereof, or computer programs and / or data involved in the method of the third aspect or any embodiment thereof.

[0043] Furthermore, the technical effects of the communication device described in the fourth aspect can be referred to the technical effects of the first aspect or any embodiment of the first aspect, or the technical effects of the second aspect or any embodiment of the second aspect, or the technical effects of the third aspect or any embodiment of the third aspect, which will not be repeated here.

[0044] Fifthly, the communication device includes: a processor configured to perform the first aspect and any possible method thereof, or the processor configured to perform the second aspect and any possible method thereof, or the processor configured to perform the third aspect and any possible method thereof.

[0045] In some implementations, the communication device described in the fifth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the fifth aspect and other communication devices.

[0046] In one possible implementation, the communication device described in the fifth aspect may further include a memory. This memory may be integrated with the processor or disposed separately. The memory may be used to store computer programs and / or data related to the methods of the first aspect or any embodiment thereof, or computer programs and / or data related to the methods of the second aspect or any embodiment thereof, or computer programs and / or data related to the methods of the third aspect or any embodiment thereof.

[0047] Furthermore, the technical effects of the communication device described in the fifth aspect can be referred to the technical effects of the first aspect or any embodiment of the first aspect, the second aspect or any embodiment of the second aspect, or the third aspect or any embodiment of the third aspect, which will not be repeated here.

[0048] In a sixth aspect, embodiments of this application provide a communication system, including a first means for performing the method described in the first aspect or any embodiment of the first aspect, and a second means for performing the method described in the third aspect or any embodiment of the third aspect.

[0049] In a seventh aspect, embodiments of this application provide a chip including a processor, configured to invoke a computer program or computer instructions in a memory to cause the processor to execute any of the implementations of the first aspect, or to cause the processor to execute any of the implementations of the second aspect, or to cause the processor to execute any of the implementations of the third aspect.

[0050] In some implementations, the processor is coupled to the memory via an interface.

[0051] Eighthly, embodiments of this application provide a computer-readable storage medium, including: a computer program or instructions; when the computer program or instructions are executed, causing the method as described in the first aspect or any embodiment of the first aspect to be implemented, or causing the method as described in the second aspect or any embodiment of the second aspect to be implemented, or causing the method as described in the third aspect or any embodiment of the third aspect to be implemented.

[0052] Ninthly, embodiments of this application provide a computer program product, including a computer program or instructions that, when executed, cause the method as described in the first aspect or any of the embodiments described in the first aspect to be implemented, or cause the method as described in the second aspect or any of the embodiments described in the second aspect to be implemented, or cause the method as described in the third aspect or any of the embodiments described in the third aspect to be implemented. Attached Figure Description

[0053] Figure 1 This is a perception service for a specific traffic scenario;

[0054] Figure 2 A schematic diagram of a communication system provided in an embodiment of this application;

[0055] Figures 3(a), 3(b), and 3(c) show the network architectures applicable to the embodiments of this application;

[0056] Figure 4 A flowchart illustrating a communication method provided in an embodiment of this application;

[0057] Figure 5 A flowchart illustrating another communication method provided in an embodiment of this application;

[0058] Figure 6 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0059] Figure 7 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0060] Figure 8 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0061] Figure 9 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0062] Figure 10 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0063] Figure 11 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0064] Sensing data, due to its large volume, has high bandwidth requirements. The bandwidth requirement for sensing data is related to factors such as the resolution of the sensing data, the data size of each sensing point, the number of transmitting beams, and the sensing interval. For example, the backhaul bandwidth requirement for sensing data from a terminal device can be estimated as follows: 1024 * 400 * 4 Bytes * 8 Beams / 100ms = 1000Mbps, where 1024 * 400 represents the resolution of the sensing data, meaning one frame includes 1024 * 400 data points (e.g., 1024 data points on the X-axis and 400 data points on the Y-axis), 4 Bytes represents the data size of one sensing data point, 8 Beams represents 8 virtual beams, and 100ms represents the sensing interval, meaning 10 frames of sensing data are transmitted per second. It is evident that the backhaul rate of sensing data from a single terminal device reaches 1Gbps, thus the air interface bandwidth requirement for sensing data is very high. If an access network device serves a large number of terminal devices, the bandwidth requirement for the access network device to send sensing data to the SF will also be very high.

[0065] Therefore, compressing the sensed data within an acceptable range before transmitting it back can reduce the bandwidth requirements of the sensed data.

[0066] The form of the sensing data can include two-dimensional or three-dimensional matrices, and applicable compression techniques include image compression, video compression, spatial point cloud compression, and other methods.

[0067] Image compression methods can be categorized into lossless and lossy compression. Lossless compression primarily reduces file size by decreasing the redundancy of the original data. Lossy compression, on the other hand, reduces file size by performing operations such as resampling and color space mapping on the original image data, thus preserving some information with some distortion; a common example is JPG compression. Lossy compression parameters can include quality parameters, among others.

[0068] Regarding video compression methods: Video can be understood as a set of images, and video compression is equivalent to compressing each image frame by frame. However, when a set of images is continuous in time, there is a correlation between adjacent image data. Utilizing this correlation can further reduce data redundancy and lower file size. Common compression methods include H.264 encoding, and compression parameters can include quality parameters, bitrate, etc.

[0069] For compressed transmission of spatial point clouds: Compression of spatial point cloud data can utilize the spatial correlation between data points to reduce data redundancy. Common compression methods include the TMC3 compression algorithm defined by the Moving Pictures Experts Group (MPEG). Compression parameters can include sampling algorithms, quality parameters, data types, etc.

[0070] Using different compression methods or different compression parameters for the same data can yield different performance metrics, such as compression ratio, compression quality (error), and compression delay.

[0071] Compression methods and their parameter configurations can be pre-configured. Alternatively, compression parameters can be negotiated and determined by the sending and receiving ends. Both parties or one party sends their own compression capabilities or suggested compression parameters to the other party, and the final compression parameters to be used are determined through negotiation or by one party.

[0072] However, current compression technologies are all suitable for traditional image, video, and point cloud services or scenarios. The negotiation process for compression methods and parameters focuses more on the impact of distorted compression on "human vision," and is not suitable for sensory data processing. For sensory service compression, the compression requirements vary depending on the type of sensory service, the number of sensory beams, and the sensory resolution. Obviously, traditional methods of determining compression parameters are difficult to adapt to sensory service scenarios.

[0073] In view of this, embodiments of this application provide a communication method for determining compression methods / compression parameters of sensing data in a sensing service scenario.

[0074] The communication method provided in this application can be applied to various communication systems, such as: 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, wireless local area network (WLAN) systems, Internet of Things (IoT) communication systems, satellite communication systems, future communication systems such as 6th generation (6G) mobile communication systems, or integrated systems of multiple systems, etc.

[0075] Figure 2 An exemplary system architecture diagram applicable to embodiments of this application is provided. For example... Figure 2 As shown, the communication system 1000 may include a wireless access network 100 and a core network 200. Optionally, the communication system 1000 may also include an Internet 300. The wireless access network 100 may include at least one wireless access network device (such as...). Figure 2 110a and 110b in the above), may also include at least one terminal device (such as Figure 2(Referring to 120a-120j in the original text). Terminal devices connect wirelessly to the wireless access network (WLAN) equipment, which in turn connects wirelessly or via a wired connection to the core network 200. The core network equipment and the WLAN equipment can be independent physical devices, or they can integrate the functions of the core network equipment and the logical functions of the WLAN equipment onto the same physical device. Alternatively, a single physical device can integrate some of the functions of both the core network equipment and the WLAN equipment. Terminal devices and WLAN equipment can be interconnected via wired or wireless connections. Figure 2 This is just an illustration; the communication system 1000 may also include other network devices, such as wireless repeaters and wireless backhaul devices. Figure 2 It is not shown in the middle.

[0076] Radio access network (RAN) equipment is used to implement radio-related functions. RAN equipment can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a next-generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc. The RAN can also be a module or unit that performs some of the functions of a base station; for example, it can be a central unit (CU), a distributed unit (DU), a control plane (CP), a user plane (UP), or a radio unit (RU), etc. RAN can also be an open access network (open RAN, O-RAN, or ORAN). In an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. This application does not limit the specific technology or equipment form used in the radio access network. For example, in a network structure, the radio access network can be CU nodes, DU nodes, or a radio access network including both CU nodes and DU nodes. Specifically, CU nodes are used to support protocols such as radio resource control (RRC), packet data convergence protocol (PDCP), and service data adaptation protocol (SDAP); DU nodes are used to support radio link control (RLC) layer protocols, medium access control (MAC) layer protocols, and physical layer protocols. In the following embodiments, the radio access network is referred to as RAN for illustrative purposes.

[0077] A terminal device is a device with wireless transceiver capabilities. It connects wirelessly to wireless access network equipment, thereby accessing the communication system. Terminal devices can also be called terminals, user equipment (UE), mobile stations, mobile terminals, etc. Terminal devices can be mobile phones, tablets, personal digital assistants (PDAs), computers with wireless transceiver capabilities, wireless data cards, wireless modems, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, complete vehicles, wireless communication modules in vehicles, telematics boxes (T-boxes), roadside units (RSUs), terminal devices in autonomous driving, terminal devices in Internet of Things (IoT) networks, terminal devices in remote medical care, terminal devices in smart grids, terminal devices in transportation safety, terminal devices in smart cities, or terminal devices in smart homes, etc. This application's embodiments are not limited to these categories. For ease of description, the following embodiments of this application will use a UE as an example. In this application embodiment, the device for implementing the functions of the terminal device can be the terminal device itself; it can also be a device capable of supporting the terminal device in implementing the functions, such as a chip system, which can be installed in the terminal device. In this application embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. In the technical solutions provided in this application embodiment, the terminal device is used as an example to describe the technical solutions provided in this application embodiment.

[0078] The main functions of the core network 200 include providing UE connectivity, managing UEs, carrying out service transmission, and providing interfaces to external networks as a bearer network. The core network may include network elements such as access and mobility management function (AMF), session management function (SMF), and user plane function (UPF).

[0079] Base stations and terminal equipment can be relatively fixed in location or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base stations and terminal equipment.

[0080] The roles of base stations and terminal devices can be relative, for example, Figure 2 The helicopter or drone 120i can be configured as a mobile base station. For terminal devices 120j that access the wireless access network 100 via 120i, terminal device 120i is a base station; however, for base station 110a, 120i is a terminal device, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol; in this case, 120i is also a base station relative to 110a. Therefore, both base stations and terminals can be collectively referred to as communication devices. Figure 2 The 110a and 110b in the text can be referred to as communication devices with base station functions. Figure 2 The 120a-120j in the text can be referred to as communication devices with terminal functions.

[0081] Communication between base stations and terminals, between base stations, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0082] Figures 3(a), 3(b), and 3(c) exemplarily provide other network architectures applicable to embodiments of this application. The network architecture shown in Figure 3(a) may include terminal devices and sensing function (SF) network elements. The network architecture shown in Figure 3(b) may include radio access network (RAN) devices and SF. The network architecture shown in Figure 3(c) may include terminal devices, RAN, and SF.

[0083] SF (Sensing Component) can be used for sensing control and sensing service data processing, such as the management, registration, demand distribution, and data processing of sensing capabilities. Furthermore, SF can also expose sensing capabilities to the application server (AS) of sensing applications through the 5GC's network exposure function (NEF). SF can be deployed independently, or it can be integrated with other devices.

[0084] It should be understood that Figures 3(a) to 3(c) This is merely one example of an applicable network architecture; real-world network architectures may include more than [examples of applicable network architectures]. Figures 3(a) to 3(c) More or fewer network elements may be included, such as access and mobility management function (AMF), session management function (SMF), user plane function (UPF), core network portal function, etc.

[0085] This application provides a communication method applicable to the aforementioned communication system, primarily involving the interaction between a first device and a second device. The first device reports compression parameters for supported sensing services, and the second device determines the compression strategy of the first device based on the compression parameters supported by the first device. Unless otherwise specified, the term "device" in this application can refer to the device itself, a module within the device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the first device.

[0086] The communication method provided in the embodiments of this application can be as follows: Figure 4 As shown, it includes the following steps:

[0087] Step 401: The first device sends first information, which is used to indicate the compression parameters of the sensing service. Correspondingly, the receiving end receives the first message.

[0088] The first device can be a UE or RAN device that supports wireless signal sensing services. The receiving end can be a second device or a third device, wherein the second device can be a SF (Signal Streaming Function), and the third device can be a network repository function (NRF) or other network element. When the receiving end is a third device, the second device can obtain the compression parameters of the sensing services supported by the first device from the third device.

[0089] The compression parameters indicated by the first indication information may include one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, or the area or angle range corresponding to each beam.

[0090] The compression mode described above is the compression mode supported by the first device. Further, it could be a compression model supported by the first device for sensing services. Specific compression modes could include two-dimensional data compression, three-dimensional data compression, etc.

[0091] The aforementioned data types are data types that the first device can compress. Further, they can be data types that the first device can compress for sensing services. Specific data types may include RV spectrum data (i.e., distance and speed determined based on the strength and frequency of the wireless signal), point cloud data (such as data obtained after processing the RV spectrum using the constant false alarm rate (CFAR) algorithm), etc.

[0092] The compression algorithm described above is a compression algorithm supported by the first device. Further, it can be a compression algorithm supported by the first device for sensing services. For example, the compression algorithm may include: image compression methods such as JPG / PNG, and video compression algorithms such as H.264 / H.265 / AV1.

[0093] Furthermore, for each compression algorithm supported by the first device, the first information may also include compression parameters supported by the first device for each compression algorithm. For example, for a compression algorithm for two-dimensional data, the compression parameters may include quality parameters, format (e.g., jpg, png, mp4, mkv, etc.), inter-frame compression configuration, data range type, etc.; for a compression algorithm for three-dimensional data, the compression parameters may include quality parameters, sampling algorithm, multi-frame merging and transmission, etc.

[0094] The aforementioned computing power can refer to the computing power of the first device, or the computing power allocated by the first device for sensing services, or the computing power allocated by the first device for compression operations. Computing power can be represented by computing power performance indicators, such as million instructions per second (MIPS), floating point operations per second (FLOPS), and data compression throughput (Mbps).

[0095] The aforementioned compression delay can represent the time it takes for the first device to compress a standard data, wherein the standard data can be sensing service data of a specific resolution under a pre-set specific data type.

[0096] The resolution of the aforementioned sensing service refers to the resolution of each frame of sensing service data reported by the first device. Furthermore, the first device can support different resolutions for different types of sensing services; or, for different data types, the first device can support different resolutions. For example, if the matrix dimension of the RV spectrum data reported by the first device is 1024*400, then the resolution of the RV spectrum data is 1024*400.

[0097] The aforementioned number of beams refers to the number of beams supported by the first device. More specifically, it can be the number of beams supported by the first device for a specific sensing service. For example, if the first device can generate sensing service data using N beams for a sensing service, then the first device can report the indication information of the N beams in the first information. Furthermore, the first device can support the same or different number of beams for different sensing services; if different, the first device can report the supported number of beams separately for each different sensing service.

[0098] Furthermore, for each beam supported by the first device, the first information may also include the area range or angle range corresponding to each beam.

[0099] When the first device is a UE, the aforementioned receiving end can be a RAN device (the third device), meaning the UE sends the first information to the RAN device, which then forwards it to the second device. Furthermore, after receiving a perception request message from the SF forwarded by the RAN device, the UE can send the first information to the RAN device, which then forwards it to the SF. Optionally, the RAN device can send the first information directly to the SF, or it can forward it to the SF through other devices.

[0100] When the first device is a RAN device, the receiving end can be a second device. Furthermore, after receiving a sensing request message from the second device, the RAN device can send the first information to the second device. Optionally, the RAN device can send the first information directly to the SF, or it can forward it to the SF through other devices.

[0101] Alternatively, when the first device is a RAN device, the aforementioned receiving end can be an NRF or other network element (a third device). That is, the RAN device can also send its supported compression parameters to the third device (such as an NRF or other network element). The second device then obtains the compression parameters from the third device when it needs to obtain them from the first device. For example, after going online, the RAN device can send first information to the NRF. The first information may include the compression parameters supported by the RAN device. In addition, the first information may also include other information about the RAN device. When the SF needs the RAN device to compress the sensed service data, it obtains the compression parameters supported by the RAN device from the NRF.

[0102] Step 402: The second device determines the first strategy based on the obtained compression parameters and the requirements of the first service.

[0103] The second device mentioned above can be SF.

[0104] As mentioned above, the second device can receive compression parameters supported by the first device sent by the first device, or the second device can obtain the compression parameters supported by the first device through a third device. For example, when the second device has a compression requirement, it can send a discovery request to the NRF network element to obtain the compression parameters supported by the RAN device. After obtaining the compression parameters of the first device for the sensing service, the second device can determine the compression strategy of the first device for the first service, i.e., the first strategy, based on the compression parameters of the first device and the requirements of the first service.

[0105] The first strategy described above is used to compress the data of the first service; the first service is one or more of the sensing services. For example, the sensing services may include multiple service types, such as traffic service type, drone service type, assisted driving service type, etc.

[0106] Optionally, the requirements for the first service may include one or more of the following: the type of the first service, the resolution requirements of the first service, the frequency requirements of the first service, the accuracy requirements of the first service, the number of beams required for the first service, or the area or angular range requirements of the first service.

[0107] For example, the type of the first service can be used to indicate that the first service is a traffic service type, drone service type, assisted driving service type or other service type in the perception service.

[0108] The resolution requirement of the first service refers to its data resolution requirements. All other things being equal, a higher resolution requirement means a larger amount of sensing service data that the first device needs to send to the second device; conversely, a lower resolution requirement means a smaller amount of sensing service data that the first device needs to send to the second device. The size of the data volume will affect the compression strategy (i.e., the first strategy mentioned above). Different service types may have different data resolution requirements.

[0109] The frequency requirement of the first service refers to the frequency at which the first service collects or reports data. All other things being equal, a higher frequency requirement means a larger amount of sensing service data that the first device needs to send to the second device; conversely, a lower frequency requirement means a smaller amount of sensing service data that the first device needs to send to the second device. The magnitude of this quantity will affect the compression strategy. Different service types may have different frequency requirements for data.

[0110] The accuracy requirement of the first service refers to the accuracy requirement of the data for that service. Higher accuracy requirements may lead to a higher number of bits needed for a single sensing point, which in turn may result in a larger amount of sensing service data that the first device needs to send to the second device. The size of the data will then affect the compression strategy. Different service types may have different accuracy requirements for the data.

[0111] The beam count requirement for the first service refers to the number of beams required by the first device to receive and / or transmit data for the first service. Different service types may have different beam count requirements.

[0112] The area and / or angular range requirements of the first service refer to the area and / or angular range within which the first device can receive and / or transmit the first service data. Different service types may have different area and / or angular range requirements.

[0113] Optionally, the first strategy determined by the second device may include compression configuration and / or compression requirements.

[0114] The compression configuration may include one or more of the following: the compression mode of the first service, the data type of the first service, the compression algorithm of the first service, or the parameters of the compression algorithm of the first service.

[0115] Typically, the compression configuration determined by the second device is the compression configuration that the first device can support. For example, if the first device supports RV spectrum data and spatial point cloud data, then the second device determines whether to compress the RV spectrum data or the spatial point cloud data of the first service based on the first service requirements and the compression parameters of the first device. If the compression parameters reported by the first device do not fully include the compression parameters that the second device needs to configure, then the second device can also determine them independently based on the requirements of the first service. For example, if the compression parameters reported by the first device include the compression algorithms supported by the first device but do not include the parameters of the compression algorithms, then the second device can configure the compression algorithm used by the first device when compressing the data of the first service, and the specific compression parameters used can be determined according to the requirements of the first service.

[0116] The second device can send one or more of the above compression configurations to the first device, so that the first device can compress the data of the first service according to the compression configuration.

[0117] Compression requirements may include one or more of the following: the bandwidth requirements of the primary service, the compression quality requirements of the primary service, or the compression latency requirements of the primary service.

[0118] For example, SF can determine the bandwidth requirements of the first service based on the data volume of the first service; SF can also determine the latency requirements for compressing the data of the first service based on the time domain requirements of the first service; SF can also determine the quality requirements for compressing the data of the first service based on whether the data of the first service can be lossily compressed, the accuracy requirements of the data of the first service, etc.

[0119] The second device can send one or more of the above compression requirements to the first device, so that the first device can determine the compression configuration according to the compression requirements and compress the data of the first service according to the determined compression configuration.

[0120] Optionally, the second device can also determine compression strategies for other sensing services based on the compression parameters supported by the first device and the needs of other sensing services. For example, SF can determine compression strategies for traffic services, drone services, and assisted driving services based on the compression parameters supported by the first device, the needs of traffic services, the needs of drone services, and the needs of assisted driving services.

[0121] For example, traffic services have high resolution requirements, lower frequency requirements, and a minimum of 8 beams, resulting in a high data volume. Therefore, a lower target compression ratio and 2D image compression can be used. Unmanned aerial vehicle (UAV) services have lower resolution requirements, higher frequency requirements, and a minimum of 4 beams, potentially resulting in a higher data volume than traffic services. Therefore, a higher target compression ratio and 2D time-frequency compression can be used. Static target services have high resolution and quality requirements, but lower frequency requirements. The UE needs to support the TMC3 compression algorithm, so 3D compression methods and lossless compression methods can be used.

[0122] Step 403: The second device sends the first strategy.

[0123] After determining the compression strategy of the first device for the first service data, the second device sends the first strategy to the first device.

[0124] When the first device is a RAN device, the second device can directly send the first policy to the RAN device, or the second device can send the first policy to the RAN device through other devices. For example, the SF can send the first policy to AMF, CN Portal Function (CPF) and other network elements so that they can forward the first policy to the RAN device.

[0125] When the first device is a UE, the second device can send the first policy to the RAN device, which then forwards it to the UE. Alternatively, the second device can send the first policy to the RAN device through other devices, which then forwards it to the UE.

[0126] As mentioned above, when the second device also determines the compression strategies for other services, the second device can also send the compression strategies for other services to the first device.

[0127] In the above method, the second device can acquire the compression parameters of the access network device or terminal device, and then determine the compression strategy for the corresponding sensing service based on the compression parameters of the access network device or terminal device and the requirements of the sensing service, and send the compression strategy to the access network device or terminal device. On the one hand, the compression strategy is determined based on the compression parameters supported by the access network device or terminal device, therefore, the compression strategy can be executed by the access network device or terminal device; on the other hand, the compression strategy is determined based on the requirements of the sensing service, therefore, the sensing service data compressed according to the compression strategy can meet the requirements of the sensing service.

[0128] In one possible implementation, after receiving the first policy, when the first device needs to send data of the first service to the second device, it compresses the data of the first service according to the first policy and sends second information to the second device. This second information includes the compressed data of the first service according to the first policy. In this implementation, there is no need to indicate whether the first policy is effective through other indication information; the first device can compress the data of the first service according to the first policy after receiving it. Similarly, if the first device also receives compression policies for other service types, there is no need for other indication information regarding the effectiveness of the compression policies; it can compress the data of those other services according to their respective compression policies.

[0129] In another possible implementation, after receiving the first strategy, the first device may first store the first strategy, but may not immediately compress the data of the first service according to the first strategy. Instead, it may compress the data of the first service according to the first strategy after receiving the first instruction information sent by the second device. The first instruction information is used to instruct the compression of the data of the first service according to the first strategy. In this implementation, the second device may first send the first strategy to the first device, and then send the first instruction information to the first device when compression is required, instructing the first device to compress the data of the first service according to the first strategy. If the first device only receives the first strategy and not the first instruction information, then the first device does not need to compress the data of the first service according to the first strategy; when compression of the data of the first service according to the first strategy is required...

[0130] In addition, the aforementioned first instruction information can also be sent to the first device together with the first strategy. After receiving the first strategy and the first instruction information, the first device can immediately compress the data of the first service according to the first strategy.

[0131] When the first device is a RAN device, the data of the first service compressed by the first device according to the first policy can be the data of the first service obtained by the RAN device itself; or it can be the data of the first service obtained by the UE. The RAN device forwards the data of the first service sent by the UE to the second device. After receiving the data of the first service sent by the UE, the RAN device compresses the data sent by the UE according to the first policy and then sends the compressed data to the second device.

[0132] Similarly, if the first device also receives compression strategies for other service types, it can also compress the data of other service types according to the compression strategies for other service types after receiving the instruction information sent by the second device to instruct data compression according to the compression strategies for other service types. For example, the first device receives compression strategies for traffic services, drone services, and assisted driving services. The first device stores these strategies, but currently does not need to compress the data of the corresponding service types according to these strategies. When the second device confirms that the data of the traffic services needs to be compressed according to the compression strategy of the traffic services, it sends instruction information 1 to the first device. Instruction information 1 includes instruction information for the traffic service type. After receiving instruction information 1, the first device determines to compress the data of the traffic services according to the compression strategy for the traffic service type. When the second device confirms that the data of the drone services and assisted driving services needs to be compressed according to the compression strategies for the drone services and assisted driving services, it sends instruction information 2 to the first device. Instruction information 2 includes instruction information for the drone services and assisted driving services. The first device determines to compress the data of the drone services and assisted driving services according to the compression strategies for the drone services and assisted driving services.

[0133] The second device first sends its own compression strategy for sensing services to the first device. When there is a need for compression, it then instructs the first device via an instruction message whether to compress the corresponding sensing services according to the compression strategy, which is beneficial for the second device to manage the data.

[0134] When the first device sends the data compressed according to the first strategy to the second device, it may also send auxiliary information to the second device. This auxiliary information is used to decompress the compressed first service data. The auxiliary information may include one or more of the following: the range of the first service data, the beam corresponding to the first service data, or the area range and / or angle range corresponding to the beam.

[0135] Understandably, the data for the first service can be generated through one or more beams, which can be physical beams or virtual beams obtained from two or more physical beams. That is, each frame of sensing service data can be composed of data from one or more beams, and the first device can merge the sensing service data from each beam into one frame of sensing service data. The first device can send beam indication information to the second device, and further, it can also send the correspondence between data and the transmitting beam to the second device. For example, the first device generates sensing service data 1 to sensing service data 8 through beams 1 to 8, respectively, and these data belong to sensing service data frame 1. Then, when the first device sends the sensing service data to the second device, it can send sensing service data 1, beam 1 indication information, data frame 1 indication information, and sensing service data 2, beam 2 indication information, data frame 1 indication information, ..., sensing service data 8, beam 8 indication information, and data frame 1 indication information, respectively. For example, if the data generated by the first device through beams 1, 2, 3, and 4 are combined into a sensing service data frame 1, then when the first device sends the sensing service data 1 to the second device, it can further send indication information of beams 1 to 4, and / or the area / angle range corresponding to each beam in beams 1 to 4.

[0136] In this implementation, in addition to reporting the compressed data, the first device can also send auxiliary information for decompression to the second device, so that the second device can conveniently decompress the received data with the assistance of the information.

[0137] In one possible design, when the first device is a RAN device, if the UE obtains data from the first service and reports it to the second device through the RAN device, the RAN device can further determine the UE's compression strategy. Specifically, the RAN device can receive third information sent by the UE, which indicates the compression parameters of the sensing service supported by the UE. The compression parameters may include one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, or the area range or angle range corresponding to each beam. The RAN device can determine a second strategy based on the compression parameters supported by the UE and the requirements of the first service. This second strategy is used by the UE to compress the data of the first service, and the second strategy is sent to the UE.

[0138] After obtaining the first strategy, the first device can further configure a second strategy for the terminal device, which is used to compress the data of the first service by the terminal device. This enables the terminal device and the first device to jointly compress and report the data of the first service, so that the compressed data can meet the needs of the sensing service and also helps to further reduce the amount of data transmission, thereby helping to improve the throughput of SF.

[0139] The compression parameters for sensing services supported by the UE are similar to those supported by the RAN equipment. You can refer to the description of the compression parameters supported by the RAN equipment in the aforementioned implementation method, which will not be repeated here.

[0140] Optionally, when determining the second policy, the RAN device can also determine the UE's second policy based on the first policy determined by the second device for the RAN device. For example, if the second device determines a first compression policy for compressing the first service data for the RAN device, the RAN device can determine that the UE also needs to compress the first service data based on one or more of the following: its supported compression parameters, the first policy, the requirements of the first service, and the current network status, and then determine the UE's compression policy for the first service data, i.e., the second policy. In one possible implementation, the RAN device can determine the requirements of the first service based on the first compression policy. The RAN device can estimate the requirements of the first service based on the first policy configured by the second device and determine the UE's compression policy based on the requirements of the first service.

[0141] In a specific example, after the RAN device configures the second policy for the UE, when the UE obtains the perception data of the first service and needs to report it to the second device, the UE can compress the data of the first service according to the second policy and send a fourth message to the RAN device. The fourth message includes the first data, that is, the data of the first service compressed according to the second policy. After receiving the fourth message, the RAN device compresses the first data again according to the first policy to obtain the second data and sends a fifth message containing the second data to the second device.

[0142] Optionally, the fourth message may also include first auxiliary information for the receiving end to decompress the compressed data. The first auxiliary information may include one or more of the following: the range of the first data, the beam corresponding to the first data, or the area range or angle range corresponding to the beam.

[0143] Optionally, the fifth message may also include second auxiliary information for the receiving end to decompress the compressed data. The second auxiliary information sent by the RAN device may be determined based on the first auxiliary information, and the second auxiliary information may include one or more of the following: the range of the first data, the beam corresponding to the first data, or the area range or angle range corresponding to the beam.

[0144] Furthermore, the RAN equipment can also determine compression strategies for other service types based on the compression parameters supported by the UE and the requirements of other service types. For example, the RAN equipment can determine compression strategies for traffic services, drone services, and assisted driving services based on the compression parameters supported by the UE, the requirements of traffic services, the requirements of drone services, and the requirements of assisted driving services.

[0145] In some embodiments, after receiving the second policy, when the UE needs to send the data of the first service to the second device through the RAN device, it compresses the data of the first service according to the second policy. In other words, the UE can compress the data of the first service according to the second policy after receiving it. Similarly, if the UE also receives compression policies for other service types, it can compress the data according to the compression policies for those other service types.

[0146] In other embodiments, after receiving the second policy, the UE may first store the second policy, but may not immediately compress the data of the first service according to the second policy. Instead, it may compress the data of the first network element according to the second policy after receiving the second indication information sent by the RAN device. The second indication information is used to indicate that the data of the first service should be compressed according to the second policy. Similarly, if the UE also receives compression policies for other service types sent by the RAN device, it may compress the data of other service types according to the compression policies of those other service types after receiving the indication information sent by the RAN device indicating that the compression policies for those other service types are effective.

[0147] To better understand the above embodiments of this application, the following is in conjunction with... Figures 5 to 7 Provide detailed examples.

[0148] exist Figure 5 In the illustrated embodiment, the first device is a RAN device, and the second device is an SF. The SF sends a message to the RAN, either directly or through the AMF or CPF. The RAN sends a message to the SF, either directly or through the AMF or CPF.

[0149] like Figure 5 As shown, the communication process may include the following steps:

[0150] Step 501: The RAN sends a connection establishment request to the SF, which includes compression parameters for the sense services supported by the RAN.

[0151] Step 501 is the same as step 401 in the aforementioned embodiment; the connection establishment request is the same as the first information in the aforementioned embodiment.

[0152] Optionally, after going online, the RAN can send the compression parameters of the sensing services it supports to the SF, so that the SF can determine the compression strategy of the sensing services based on the compression parameters supported by the RAN.

[0153] The connection establishment request may also include the RAN ID.

[0154] Step 502: SF determines the compression strategy for RAN sensing services based on the compression parameters of the sensing services supported by RAN and the sensing service requirements.

[0155] Step 502 is the same as step 402 in the aforementioned embodiment.

[0156] Based on the compression parameters of the sensing services supported by the RAN and the requirements of the first sensing service, SF determines the compression strategy of the RAN for the first sensing service.

[0157] Optionally, the SF can determine the compression strategy corresponding to each sensing service requirement based on the compression parameters of the sensing services supported by the RAN and the requirements of various sensing services. For example, the SF can determine the RAN's compression strategy for the first sensing service, the second sensing service, the third sensing service, and other sensing services based on the compression parameters supported by the RAN, the requirements of the first sensing service, the second sensing service, the third sensing service, and other sensing services.

[0158] Step 503: SF sends a connection establishment response to RAN, which includes the compression strategy for RAN-aware services.

[0159] Step 503 is the same as step 403 in the aforementioned embodiment.

[0160] Optionally, the connection establishment response may also include activation indication information to indicate whether the compression strategy is currently activated. If the indication is activated, then after receiving the connection establishment response, if the RAN needs to send sensing service data to the SF, it will compress the data according to the corresponding compression strategy. If the indication is not activated, then after receiving the connection establishment response, even if the RAN needs to send sensing service data to the SF, it does not need to compress the data according to the corresponding compression strategy.

[0161] Furthermore, if the SF sends multiple sensing service compression strategies to the RAN, such as a compression strategy for the first sensing service, a compression strategy for the second sensing service, and a compression strategy for the third sensing service, then the activation indication information can include activation indication information for the first sensing service, activation indication information for the second sensing service, and activation indication information for the third sensing service. Each indication information is only used to indicate whether the compression strategy of its corresponding sensing service is activated. Of course, a common activation indication information can also be set for multiple sensing services.

[0162] If the connection establishment response does not include activation indication information, the compression policy can be activated by default for all compression policies, or the compression policy can be deactivated by default for all compression policies.

[0163] Step 504: SF sends a sensing request to RAN, which includes activation indication information, indicating the activation of the compression strategy for the first sensing service.

[0164] When SF determines that the data of the first sensing service needs to be compressed, it activates the compression strategy of the first sensing service through a sensing request.

[0165] Furthermore, if SF determines that data from other sensing services needs to be compressed, it can activate the corresponding compression strategy through a sensing request. Alternatively, if SF determines that data from certain sensing services can be decompressed, it can disable the corresponding compression strategy through a sensing request.

[0166] Optionally, if the SF modifies the compression strategy for a certain sensing service, it can also send the modified compression strategy to the RAN through the aforementioned sensing request.

[0167] Step 504 above is an optional step.

[0168] Step 505: The RAN sends sensing data to the SF, which includes first sensing service data compressed according to the first sensing service compression strategy.

[0169] After the RAN obtains the data of the first sensing service, it can compress the data according to the compression strategy of the first sensing service and send the compressed data to the SF; or, after the RAN receives the data of the first sensing service sent by the UE, it can compress the data of the first sensing service sent by the UE according to the compression strategy of the first sensing service and send the compressed data to the SF.

[0170] Optionally, the sensing data may also include auxiliary information, which may include the range of the data, the beam corresponding to the data, and the area or angle range corresponding to the beam.

[0171] exist Figure 6In the illustrated embodiment, the first device is a RAN device, and the second device is an SF. The SF sends a message to the RAN, either directly or through the AMF or CPF. The RAN sends a message to the SF, either directly or through the AMF or CPF.

[0172] Figure 6 The illustrated embodiments and Figure 5 The difference in the illustrated embodiment is that the RAN sends the compression parameters of the sensing services it supports to the NRF instead of to the SF; the SF obtains the compression parameters of the sensing services supported by the RAN from the NRF.

[0173] like Figure 6 As shown, the communication process may include the following steps:

[0174] Step 601: The RAN sends a registration request to the NRF, which includes compression parameters for the sense services supported by the RAN.

[0175] Step 601 is the same as step 401 in the aforementioned embodiment.

[0176] After going live, the RAN can send the compression parameters of the sensing services it supports to the NRF. The registration request can also include the RAN's ID.

[0177] Step 602: The SF sends a discovery request to the NRF, which may include the RAN type, RAN ID, or RAN area information.

[0178] When an SF has a reporting and compression requirement for sensing services, if the ID of an available RAN is known, the compression parameters of the sensing services supported by the corresponding RAN can be obtained from the NRF through the RAN ID; if the SF does not know the ID of an available RAN, the ID of an available RAN and the compression parameters of the sensing services supported by the RAN can be obtained through the RAN type and / or area information.

[0179] Step 603: The NRF sends a discovery response to the SF, which includes the RAN ID and compression parameters of the sense services supported by the RAN.

[0180] The above-mentioned discovery response is the first information in the aforementioned embodiments.

[0181] If the request includes the RAN ID, the NRF can look up the compression parameters of the sensing services supported by the corresponding RAN based on the RAN ID; if the request does not include the RAN ID, the NRF can look up the RAN that meets the SF requirements and the compression parameters of the sensing services supported by the RAN that meets the requirements based on the information of the registered RAN, and send it to the SF.

[0182] Step 604: SF determines the compression strategy for RAN sensing services based on the compression parameters of the sensing services supported by RAN and the sensing service requirements.

[0183] Step 604 is... Figure 4 Step 402 in the illustrated embodiment can also be referred to. Figure 5 Step 502 in the illustrated embodiment will not be repeated here.

[0184] Step 605: SF sends a perception request to RAN, which includes the compression strategy of RAN perception services.

[0185] Step 605 is the same as step 403 in the aforementioned embodiment.

[0186] Optionally, the perception request may also include activation indication information to indicate whether the compression strategy is currently activated. The activation indication information can be found in the description of activation indication information in the foregoing embodiments, and will not be repeated here.

[0187] Step 606: The RAN sends sensing data to the SF, which includes sensing service data compressed according to the compression strategy.

[0188] This step can be referred to the description of step 505 in the aforementioned embodiment, and will not be repeated here.

[0189] exist Figure 7 In the illustrated embodiment, the first device is the UE, and the second device is the SF; when the SF sends a message to the UE, it means that the SF sends the message to the UE through the RAN; when the UE sends a message to the SF, it means that the message is sent to the SF through the RAN.

[0190] Figure 7 The illustrated embodiments and Figure 5 The difference in the illustrated embodiment is that the SF determines the compression strategy for the UE's perceived services.

[0191] like Figure 7 As shown, the communication process may include the following steps:

[0192] Step 701: SF sends a sensing service request to UE, which requests UE to perform sensing services and report the compression parameters of the supported sensing services.

[0193] When there is a data transmission and compression requirement for sensing services, the SF can send a sensing request to the UE so that the UE can report the compression parameters of the sensing services it supports.

[0194] Step 702: The UE sends a perception response to the SF, which includes compression parameters of the perception services supported by the UE.

[0195] Step 702 is... Figure 4 Step 401 in the illustrated embodiment; the above-mentioned sensing response is... Figure 4 The first information in the illustrated embodiment.

[0196] Step 703: SF determines the compression strategy for the UE's sense services based on the compression parameters of the sense services supported by the UE and the sense service requirements.

[0197] Step 703 is... Figure 4 Step 402 in the illustrated embodiment.

[0198] Based on the compression parameters of the sensing services supported by the UE and the requirements of the first sensing service, the SF determines the compression strategy of the UE for the first sensing service.

[0199] Optionally, SF can determine the compression strategy corresponding to each sensing service requirement based on the compression parameters of the sensing services supported by the RAN and the requirements of various sensing services.

[0200] Step 704: SF sends a perception request to UE, which includes the compression strategy for UE perception services.

[0201] Step 704 is... Figure 4 Step 403 in the illustrated embodiment.

[0202] Optionally, the perception request may also include activation indication information to indicate whether the compression strategy is currently activated.

[0203] Furthermore, if the SF sends compression strategies for multiple sensing services to the UE, the activation indication information can include separate activation indication information for each sensing service, with each indication information only used to indicate whether the compression strategy for its corresponding sensing service is activated. Alternatively, a common activation indication information can be set for multiple sensing services.

[0204] If the perception request does not include activation indication information, the compression strategy can be activated by default for all compression policies, or the compression strategy can be deactivated by default for all compression policies.

[0205] Step 705: The UE sends sensing data to the SF, which includes sensing service data compressed according to the compression strategy.

[0206] After the UE obtains the data from the first sensing service, the UE can compress the data according to the compression strategy of the first sensing service and send the compressed data to the SF.

[0207] Optionally, the sensing data may also include auxiliary information, which may include the range of the data, the beam corresponding to the data, and the area or angle range corresponding to the beam.

[0208] exist Figure 8 In the illustrated embodiment, the first device is a RAN device, and the second device is an SF. The SF sends a message to the RAN, either directly or through the AMF or CPF. The RAN sends a message to the SF, either directly or through the AMF or CPF.

[0209] Figure 8 The illustrated embodiments and Figure 5 The difference in the illustrated embodiment is that after the SF determines the compression strategy for the sensed service for the RAN, the RAN further determines the compression strategy for the sensed service for the UE.

[0210] Step 801: SF obtains the compression parameters of the sensing services supported by RAN.

[0211] The way SF obtains the compression parameters of the sensing services supported by RAN can be as follows: Figure 5 As shown in step 501, it can also be as follows: Figure 6 Steps 602 and 603 are shown in the diagram.

[0212] Step 802: SF determines the first compression strategy for RAN sensing services based on the compression parameters of the sensing services supported by RAN and the requirements of the sensing services.

[0213] Step 802 is... Figure 4 Step 402 in the illustrated embodiment can also be referred to. Figure 5 Step 502 in the illustrated embodiment will not be repeated here.

[0214] Step 803: SF sends a perception request to RAN, which includes the first compression strategy.

[0215] This step 803 is... Figure 4 Step 403 in the illustrated embodiment.

[0216] Optionally, the perception request may also include activation indication information to indicate whether the compression strategy is currently activated. The activation indication information can be found in the description of activation indication information in the foregoing embodiments, and will not be repeated here.

[0217] Step 804: SF sends a perception request to UE through RAN, which includes perception service information.

[0218] The aforementioned sensing service information may include sensing service type indication information, sensing frequency, sensing accuracy, area range or angle range, etc., which are used to instruct the UE to report data of the corresponding service type according to the sensing frequency, sensing accuracy, area range or angle range, etc.

[0219] Step 805: The UE establishes a sensing data radio bearer (DRB) with the RAN and reports the compression parameters of the sensing services supported by the UE to the RAN.

[0220] Establishing a DRB between the UE and the RAN is an optional step. The UE can also send the compression parameters of the sense services it supports to the RAN through other means.

[0221] Step 806: The RAN determines the second compression strategy for the UE's sense services based on the compression parameters of the sense services supported by the UE and the sense service requirements.

[0222] Step 807: The RAN sends the second compression strategy to the UE.

[0223] Optionally, the RAN can also send activation indication information to the UE to indicate whether the compression strategy is currently activated.

[0224] Step 808: The UE compresses the acquired perception service data according to the second compression strategy to obtain the first data.

[0225] Step 809: The UE will send sensing data to the RAN.

[0226] The sensed data includes the first data mentioned above. Optionally, the sensed data may also include first auxiliary information for decompressing the compressed data.

[0227] Step 810: RAN compresses the first data according to the first compression strategy to obtain the second data.

[0228] Step 811: RAN sends sensing data to SF, which includes the second data.

[0229] Optionally, the sensing data may also include second auxiliary information generated based on the first auxiliary information, used to decompress the compressed data.

[0230] This application also provides a communication method. Unlike the aforementioned communication methods, the SF can determine the compression strategy for sensing services for both the RAN device and the UE.

[0231] This communication method can be as follows: Figure 9 As shown, it includes the following steps:

[0232] Step 901: SF obtains the compression parameters of the sensing services supported by the RAN equipment.

[0233] The compression parameters of the sensing services supported by the RAN equipment may include one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, or the area or angle range corresponding to each beam.

[0234] In step 901 above, the RAN device can send the compression parameters of the sensing services it supports to the SF, or forward them to the SF through other devices. Furthermore, after receiving a sensing request message from the SF, the RAN device can send the compression parameters of the sensing services it supports to the SF.

[0235] Alternatively, the RAN device can send the compression parameters it supports to the NRF. For example, after going online, the RAN device can send first information to the NRF. The first information may include the compression parameters supported by the RAN device. In addition, the first information may also include other information of the RAN device. When the SF needs the RAN device to compress the sensed service data, it obtains the compression parameters supported by the RAN device from the NRF.

[0236] Step 902: SF obtains the compression parameters of the sensing services supported by the UE.

[0237] The compression parameters of the sensing services supported by the UE may include one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, or the area or angle range corresponding to each beam.

[0238] In step 902 above, the UE can send the compression parameters of the sensing services it supports to the SF via the RAN device. Furthermore, after receiving a sensing request message from the SF, the UE can send the compression parameters of the sensing services it supports to the SF via the RAN device.

[0239] In this embodiment of the application, the order of steps 901 and 902 is not limited. Step 902 can be executed first, followed by step 901.

[0240] Step 903: SF determines the first strategy and the second strategy based on the requirements of the first service, the compression parameters of the sensing services supported by the RAN equipment, and the compression parameters of the sensing services supported by the UE.

[0241] The first strategy is used by the RAN device to compress the data of the first service, and the second strategy is used by the UE to compress the data of the first service. The first service is one or more of the sensing services. For example, sensing services may include multiple service types, such as traffic service types, drone service types, assisted driving service types, etc.

[0242] After obtaining the compression parameters of the RAN device for the sensing service, SF can determine the compression strategy of the RAN device for the first service, i.e., the first strategy, based on the compression parameters of the RAN device and the requirements of the first service.

[0243] After obtaining the compression parameters of the UE for the sensing service, SF can also determine the compression strategy of the UE for the first service, i.e., the second strategy, based on the compression parameters of the UE and the requirements of the first service.

[0244] Optionally, the requirements for the first service may include one or more of the following: the type of the first service, the resolution requirements of the first service, the frequency requirements of the first service, the accuracy requirements of the first service, the number of beams required for the first service, or the area or angular range requirements of the first service.

[0245] Optionally, the first strategy determined by SF may include compression configuration and / or compression requirements. The compression configuration may include one or more of the following: the compression mode of the first service, the data type of the first service, the compression algorithm of the first service, or the parameters of the compression algorithm of the first service. The compression requirements may include one or more of the following: the bandwidth requirements of the first service, the compression quality requirements of the first service, or the compression latency requirements of the first service.

[0246] Similarly, the second strategy identified by SF may also include compression configuration and / or compression requirements. The compression configuration and compression requirements are similar to those in the first strategy.

[0247] Optionally, SF can also determine the compression strategy for other sensing service data by the RAN equipment / UE based on the compression parameters supported by the RAN equipment / UE and the requirements of other sensing services. For example, SF can determine the compression strategy for traffic services, the compression strategy for drone services, and the compression strategy for assisted driving services based on the compression parameters supported by the RAN equipment / UE, the requirements of traffic services, the requirements of drone services, and the requirements of assisted driving services.

[0248] Step 904: SF sends the first policy to the RAN device.

[0249] The SF can send the first policy directly to the RAN device, or the SF can send the first policy to the RAN device through other devices.

[0250] Step 905: SF sends the second strategy to UE.

[0251] The SF can send the first policy to the RAN device, which then forwards it to the UE. Alternatively, the SF can send the first policy to the RAN device through other devices, which then forwards it to the UE.

[0252] In this embodiment of the application, the order of steps 904 and 905 is not limited. Step 905 can be executed first, followed by step 904.

[0253] In one possible implementation, after receiving the first policy, the RAN device can compress the data of the first service according to the first policy; after receiving the second policy, the UE can compress the data of the first service according to the second policy. Then, when the UE needs to send the data of the first service to the SF, it compresses the data of the first service according to the second policy and sends it to the RAN device; the RAN device performs secondary compression on the received data according to the first policy and then sends it to the SF. When the RAN device needs to send the data of the first service to the SF, it compresses the data of the first service according to the first policy and sends it to the SF.

[0254] In another possible implementation, after receiving the first policy, the RAN device can first store the first policy, and then compress the first service data according to the first policy after receiving the first indication information sent by the SF (indicating that the first service data should be compressed according to the first policy). After receiving the second policy, the UE can first store the second policy, and then compress the first service data according to the second indication information (indicating that the first service data should be compressed according to the second policy). Optionally, the SF can send the indication information to both the RAN device and the UE separately, or the SF can send the indication information to the RAN device to instruct that the data of the first service should be compressed according to the first policy. After receiving this indication information, the RAN device can further send the indication information to the UE to instruct that the data of the first service should be compressed according to the second policy.

[0255] It should be understood that when the SF sends indication information to the UE, it means that the SF sends indication information to the UE through the RAN device. For example, the SF can carry the indication information in a NAS message, and the RAN device will forward the NAS message carrying the indication information to the UE.

[0256] Similarly, if the RAN device / UE also receives compression policies for other service types, it can compress the data of other service types according to the compression policies of other service types after receiving the indication information sent by the SF to indicate that the compression policies of other service types are effective.

[0257] When the UE sends data compressed according to the second strategy to the RAN device, it can also send auxiliary information to the RAN device. This auxiliary information is used to decompress the compressed first service data. The auxiliary information may include one or more of the following: the range of the first service data, the beam corresponding to the first service data, or the area range and / or angle range corresponding to the beam.

[0258] When the RAN device sends data compressed according to the first strategy to the SF, it can also send auxiliary information to the SF. This auxiliary information is used to decompress the compressed data of the first service. The auxiliary information may include one or more of the following: the range of the first service data, the beam corresponding to the first service data, or the area range and / or angle range corresponding to the beam.

[0259] When the RAN device sends the first data (data of the first service compressed according to the second policy) sent by the UE to the SF, it compresses the first data according to the policy to obtain the second data and sends the second data to the SF. Furthermore, the RAN device can also generate second auxiliary information based on the first auxiliary information sent by the UE, and send the second data and the second auxiliary information to the SF.

[0260] Figure 10 This is a schematic diagram of a communication device according to an embodiment of this application. The communication device includes an interface module 1001 and a processing module 1002. The processing module 1002 is used to process data by the communication device. The interface module 1001 is used to receive content from the communication device and other units or network elements, or to send content from the communication device and other units or network elements. It should be understood that the processing module 1002 in this embodiment of the application can be implemented by a processor or processor-related circuit components (or, referred to as processing circuitry), and the interface module 1001 can be implemented by a receiver / transmitter or receiver / transmitter-related circuit components.

[0261] For example, the communication device may be a communication device equipment, or it may be a chip or other combination device or component that has the functions of the aforementioned communication device equipment applied in the communication device equipment.

[0262] When the communication device is SF, the processing module 1002 is configured to: receive first information through the interface module 1001, the first information being used to indicate compression parameters for the sensing service, the compression parameters including one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, or, the area or angle range corresponding to each beam; determine a first strategy based on the compression parameters and the requirements of the first service, the first service being one of the sensing services, the first strategy being used to compress the data of the first service; and send the first strategy through the interface module 1001.

[0263] In addition, the above modules can also be used to support Figures 4 to 9 Other processes performed by SF in the illustrated embodiment. The beneficial effects are described above and will not be repeated here.

[0264] When the communication device is a RAN device or a terminal device, the processing module 1002 is configured to: send first information through the interface module 1001, the first information being used to indicate compression parameters for a sensing service, the compression parameters including one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, or, the area or angle range corresponding to each beam; and receive a first strategy through the interface module 1001, the first strategy being determined based on the compression parameters and the requirements of the first service, the first service being one of the sensing services, the first strategy being used to compress the data of the first service.

[0265] In addition, the above modules can also be used to support Figures 4 to 9 Other processes performed by the RAN device or terminal device in the illustrated embodiments. The beneficial effects are described above and will not be repeated here.

[0266] Figure 11 This is a schematic diagram of another communication device provided according to an embodiment of this application. The communication device includes a processor 1101, a communication interface 1102, and may further include a memory 1103 and a bus 1104. The processor 1101, communication interface 1102, and memory 1103 can be interconnected via the bus 1104. The bus 1104 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus 1104 can be divided into an address bus, a data bus, and a control bus, etc. For ease of illustration, Figure 11 The symbol is represented by only one line, but this does not mean that there is only one bus or one type of bus.

[0267] Processor 1101 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor may further include hardware chips. These hardware chips may be application-specific integrated circuits (ASICs), programmable logic devices (PLDs), or combinations thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. Memory 1103 may be volatile memory or non-volatile memory, or may include both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache.

[0268] The processor 1101 is used to implement the data processing operation of the communication device, and the communication interface 1102 is used to implement the receiving and sending operations of the communication device.

[0269] When the communication device is SF, the processor 1101 is configured to: receive first information through the communication interface 1102, the first information being used to indicate compression parameters for a sensing service, the compression parameters including one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, or, the area or angle range corresponding to each beam; determine a first strategy based on the compression parameters and the requirements of the first service, the first service being one of the sensing services, the first strategy being used to compress the data of the first service; and send the first strategy through the communication interface 1102.

[0270] In addition, the above modules can also be used to support Figures 4 to 9Other processes performed by SF in the illustrated embodiment. The beneficial effects are described above and will not be repeated here.

[0271] When the communication device is a RAN device or a terminal device, the processor 1101 is configured to: send first information through the communication interface 1102, the first information being used to indicate compression parameters for a sensing service, the compression parameters including one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, or, the area or angle range corresponding to each beam; and receive a first strategy through the communication interface 1102, the first strategy being determined based on the compression parameters and the requirements of the first service, the first service being one of the sensing services, the first strategy being used to compress the data of the first service.

[0272] In addition, the above modules can also be used to support Figures 4 to 9 Other processes performed by the RAN device or terminal device in the illustrated embodiments. The beneficial effects are described above and will not be repeated here.

[0273] Based on the same technical concept, embodiments of this application provide a communication system including the aforementioned SF and RAN devices.

[0274] Based on the same technical concept, embodiments of this application provide a chip, including: a processor coupled to a memory for storing instructions, wherein when the instructions are executed by the processor, the chip enables the chip to implement the method described in any of the above implementation methods.

[0275] Based on the same technical concept, embodiments of this application also provide a computer-readable storage medium storing computer-readable instructions, which, when executed on a computer, cause the above-described method embodiments to be performed.

[0276] Based on the same technical concept, this application also provides a computer program product containing instructions that, when run on a computer, cause the above-described method embodiments to be executed.

[0277] It should be understood that in the description of this application, terms such as "first" and "second" are used only for distinguishing purposes and should not be construed as indicating or implying relative importance or order. References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in still other embodiments" appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0278] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0279] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0280] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0281] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0282] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0283] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the spirit and scope of the embodiments of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include these modifications and variations.

Claims

1. A communication method, characterized in that, The method includes: Receive first information, the first information being used to indicate compression parameters of the sensing service, the compression parameters including one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, or, area or angle range corresponding to each beam. Based on the compression parameters and the requirements of the first service, a first strategy is determined, wherein the first service is one of the sensing services, and the first strategy is used to compress the data of the first service. Send the first strategy.

2. The method according to claim 1, characterized in that, The method further includes: Send a first instruction message, which is used to instruct the data of the first service to be compressed according to the first strategy.

3. The method according to claim 1 or 2, characterized in that, The first strategy includes compressing configurations and / or compressing requirements; The compression configuration includes one or more of the following: the compression mode of the first service, the data type of the first service, the compression algorithm of the first service, or the parameters of the compression algorithm of the first service. The compression requirements include one or more of the following: bandwidth requirements, compression quality requirements, or compression latency requirements.

4. The method according to any one of claims 1-3, characterized in that, The requirements of the first service include one or more of the following: the type of the first service, the resolution requirement of the first service, the frequency requirement of the first service, the accuracy requirement of the first service, the number of beams of the first service, or the area or angular range requirement of the first service.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Receive second information, the second information including data of the first service compressed according to the first strategy.

6. The method according to claim 5, characterized in that, The second information also includes auxiliary information used to decompress the data of the first service. The auxiliary information includes one or more of the following: the range of the first service data, the transmission beam corresponding to the first service data, or the area or angle range corresponding to the transmission beam.

7. A communication method, characterized in that, The method includes: Send first information, which is used to indicate the compression parameters of the sensing service. The compression parameters include one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, or, the area or angle range corresponding to each beam. A first strategy is received, which is determined based on the compression parameters and the requirements of a first service, wherein the first service is one of the sensing services, and the first strategy is used to compress the data of the first service.

8. The method according to claim 7, characterized in that, The method further includes: Receive first instruction information, which is used to instruct the data of the first service to be compressed according to the first strategy.

9. The method according to claim 7 or 8, characterized in that, The first strategy includes compressing configurations and / or compressing requirements; The compression configuration includes one or more of the following: the compression mode of the first service, the data type of the first service, the compression algorithm of the first service, or the parameters of the compression algorithm of the first service. The compression requirements include one or more of the following: bandwidth requirements, compression quality requirements, or compression latency requirements.

10. The method according to any one of claims 7-9, characterized in that, The requirements of the first service include one or more of the following: the type of the first service, the resolution requirement of the first service, the frequency requirement of the first service, the number of beams required for the first service, or the area or angular range requirement of the first service.

11. The method according to any one of claims 7-10, characterized in that, The method further includes: Send a second message, which includes data of the first service compressed according to the first strategy.

12. The method according to claim 11, characterized in that, The second information also includes auxiliary information, which is used to decompress the data of the first service. The auxiliary information includes one or more of the following: The range of the first service data, the transmission beam corresponding to the first service data, or the area or angle range corresponding to the transmission beam.

13. The method according to any one of claims 7-12, characterized in that, The method further includes: Receive third information, the third information being used to indicate compression parameters of the sensing service, the compression parameters including one or more of the following: compression mode, data type, compression algorithm, parameters of the compression algorithm, computing power, compression latency, resolution of the sensing service, number of beams, or, the area or angle range corresponding to each beam. Based on the compression parameters and the requirements of the first service, a second strategy is determined, which is used to compress the data of the first service. Send the second strategy.

14. The method according to claim 13, characterized in that, The method further includes: Send a second instruction message, which is used to instruct the data of the first service to be compressed according to the second strategy.

15. The method according to claim 13 or 14, characterized in that, The method further includes: Receive fourth information, the fourth information including first data, the first data being data of the first service type compressed according to the second strategy; Send a fifth message, which includes second data, which is data obtained by compressing the first data according to the first strategy.

16. The method according to claim 15, characterized in that, The fourth information further includes first auxiliary information, which is used to decompress the first data. The first auxiliary information includes one or more of the following: The range of the first data, the transmission beam corresponding to the first data, or the region or angle range corresponding to the transmission beam.

17. The method according to claim 15, characterized in that, The fifth information further includes second auxiliary information determined based on the first auxiliary information, the second auxiliary information being used to decompress the second data, and the second auxiliary information including one or more of the following: The range of the first data, the transmission beam corresponding to the first data, or the region or angle range corresponding to the transmission beam.

18. A communication device, characterized in that, Includes units or modules for performing the method according to any one of claims 1-17.

19. A communication device, characterized in that, include: A processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the apparatus to perform the method as described in any one of claims 1-17.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-17.

21. A computer program product containing instructions, characterized in that, When the instructions are executed on a computer, the computer causes the computer to perform the method as described in any one of claims 1-17.

Images