Communication method and communication apparatus

Abstract

The present application provides a communication method and a communication apparatus. Considering that when a QoS parameter is not a parameter defined by a standard, a terminal device cannot distinguish the service type of data by means of a standard protocol, at this point, according to the present application, the terminal device may internally acquire first indication information, the indication information being used for indicating a service type corresponding to the data. The first indication information may further be sent to a network device, and the network device is instructed, by means of the indication information, to allocate a resource for the service type. Therefore, the terminal device may send, on the resource configured by the network device, service data of a corresponding service type, so that the resource configured by the network device may be correctly utilized and a transmission error is prevented, thereby ensuring the service experience of a user.

Description

Communication method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on November 2, 2023, with application number 202311452415.8, and priority to the Chinese patent application entitled “A Communication Method and Communication Device”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and more specifically, to a communication method and a communication device. Background Art

[0003] Uncrewed aerial vehicles (UAVs), a new type of aircraft, are becoming increasingly popular due to their flexibility and convenience. Cellular networks provide UAVs with key features such as wide coverage, high reliability, high security, and continuous mobility, as well as oversight by regulators. The communication environment of UAVs differs significantly from that of standard user equipment (UE). UAVs primarily fly above base stations, connecting to them via the Uu port and primarily communicating within line of sight (LOS). Therefore, UAVs can receive signals from more base stations.

[0004] There may be a risk of collision when drones are flying in the air. To avoid drone collisions, the current 3rd Generation Partnership Project (3GPP) system supports a detect and avoid mechanism (DAA). On the other hand, regulators require drones to broadcast their identifiers (ID) during flight to facilitate continuous management of drones. The 3GPP system supports broadcast UAV IDs (BRID). It can also be understood that the services currently supported by drones include BRID services, DAA, and command and control (C2) services (where C2 is the communication between the drone and the controller). Currently, 3GPP has defined the standard PC5 interface 5G Service Quality Identification (PC5 5G QoS Identification, PC5 PQI) (hereinafter referred to as "PQI") to indicate the different services supported by drones.

[0005] Current standards specify that base stations can configure dedicated resource pools for drones. These dedicated resource pools support the transmission of DAA and / or BRID service data. However, when data arrives from drones, if a non-standard PQI is used or no PQI is used, the drone cannot distinguish the specific service type of the incoming data based on standard protocols. As a result, the drone may not transmit data for the corresponding service type in the base station's configured resource pool, potentially causing transmission errors and impacting the user experience.

[0006] Summary of the Invention

[0007] The present application provides a communication method, in which a terminal device can distinguish data of different business types based on indication information, and instruct a network device through the indication information to allocate resources of the business type. Therefore, the terminal device can subsequently send data of the corresponding business type on the corresponding resources configured by the network device, which can avoid transmission errors caused by the terminal device and ensure the user's business experience.

[0008] In a first aspect, a communication method is provided, which is applied to sidelink communication. The method can be executed by a terminal device, or by a component of the terminal device (such as a chip or circuit), without limitation. For example, the terminal device can be a drone, an aerial vehicle, etc.

[0009] The method includes: the terminal device obtains a first quality of service QoS parameter and indication information, the indication information is used to indicate the service type corresponding to the first data, the first QoS parameter is the QoS requirement parameter of the first data of the terminal device, the terminal device sends first information to the network device, and the first information includes indication information.

[0010] In a possible implementation, the first QoS parameter is a QoS parameter not defined by the Third Generation Partnership Project 3GPP.

[0011] In the present application, “the first QoS parameter is a QoS parameter not defined by 3GPP” can also be understood as “the first QoS parameter is a QoS parameter corresponding to a service type not specified by the 3GPP standard”.

[0012] In a possible implementation scenario, "non-3GPP defined parameters" can be understood as a private parameter, not a parameter specified in the protocol. For example, assuming that the QoS parameter is PQI, the protocol defines that when the PQI value is 40 to 44, and 62 to 65, there is a corresponding service type. The "first QoS parameter" in this application can be understood as a PQI value of 10, or a PQI value of 100. At this time, the protocol does not specify the service type corresponding to the PQI value of 10, nor does it specify the service type corresponding to the PQI value of 100.

[0013] In another possible implementation scenario, "non-3GPP defined parameters" can be understood as, although the parameters defined in 3GPP are used, the corresponding service type is not defined in the protocol. For example, assuming that the QoS parameter is PQI, the protocol defines that when the PQI value is 42, the corresponding service type is C2 service; when the PQI value is 62, the corresponding service type is BRID service; when the PQI value is 64, the corresponding service type is DAA service. The "first QoS parameter" in this application can be understood as, when the PQI value is 42, the corresponding service type customized within the terminal device is DAA service; when the PQI value is 62, the corresponding service type customized within the terminal device is C2 service; when the PQI value is 64, the corresponding service type customized within the terminal device is BRID service.

[0014] Optionally, the terminal device may determine whether the QoS parameter is the first QoS parameter or the second QoS parameter, where the second QoS parameter may be understood as "the QoS parameter defined by 3GPP" or "the QoS parameter corresponding to the service type specified in the 3GPP standard." Specifically, how the terminal device determines whether the QoS parameter is a parameter specified in the protocol or not may be implemented internally by the terminal device and is not limited.

[0015] It should be noted that the specific name of the QoS parameter is not limited in this application. For example, the QoS parameter can be PQI or other parameters. As long as the parameter is used to characterize the QoS requirements, it falls within the scope of protection required by this application.

[0016] In this application, for example, "service type" includes at least one of the following: detection and avoidance of collisions (DAA) service, drone ID broadcast (BRID) service, and command and control (C2) service. Exemplarily, the service type corresponding to the first data may include: DAA service type and BRID service type.

[0017] Exemplarily, the first QoS parameter may be obtained by the terminal device from the core network via a non-access stratum (NAS) message.

[0018] Optionally, in the present application, since the terminal device can distinguish the service type corresponding to the data through the obtained indication information, if the network device has pre-configured resources of different service types for the terminal device, the terminal device can directly transmit data of the corresponding service type on the corresponding resources, thereby avoiding transmission errors.

[0019] Based on the above technical solution, in this application, considering that when the QoS parameters are not parameters defined by the standard, the terminal device cannot distinguish the service type of the data through the standard protocol, at this time, this application proposes that the terminal device can determine the first indication information inside, and the indication information is used to indicate the service type corresponding to the data. The terminal device can also send the first indication information to the network device to instruct the network device to allocate resources of this service type, so that the terminal device can send service data of the corresponding service type on the resources configured by the network device. This allows the resources configured by the network device to be properly utilized to avoid transmission errors. For example, the terminal device can transmit DAA service data on the DAA dedicated resources configured by the network device, the terminal device can transmit BRID service data on the BRID dedicated resources configured by the network device, and the terminal device can transmit ordinary service data on ordinary resources configured by the network device.

[0020] In a possible implementation, the indication information is used by the network device to allocate resources corresponding to the service type to the terminal device.

[0021] Based on the above technical solution, in this application, the network device can configure resources of corresponding business types for the terminal device based on the indication information, and the terminal device can transmit data of the corresponding business type on the resources configured by the network device to avoid transmission errors and ensure the user's business experience.

[0022] In one possible implementation, the indication information is obtained from an upper layer of the terminal device and sent to a lower layer by the upper layer of the terminal device; alternatively, the indication information is obtained by the terminal device based on the first data. For example, the upper layer of the terminal device determines the indication information based on the first QoS parameter. In another example, the upper layer of the terminal device determines the indication information based on the first data.

[0023] In this application, the "upper layer of the terminal device" can be understood as, for example, the A2X layer or the application layer; the "lower layer of the terminal device" can be understood as, for example, the physical layer or the access layer.

[0024] In a possible implementation, the indication information is used to indicate a service type corresponding to the Quality of Service (QoS) flow.

[0025] In a possible implementation, the first information further includes a layer 2 identifier L2 ID, and the indication information is used to indicate a service type of data of the terminal device corresponding to the L2 ID.

[0026] In this application, L2 ID is an L2 identifier of a destination, and L2 ID can be used to indicate a terminal device.

[0027] In a possible implementation, the indication information is used to indicate a service type corresponding to the QoS flow associated with the L2 ID.

[0028] In a possible implementation, the service types corresponding to the QoS flows are the same.

[0029] In one possible implementation, the method also includes: determining a first resource allocated by the network device, the first resource being used to transmit data of a first service type; sending a first transmission block to the network device on the first resource, wherein the service types corresponding to the data in the first transmission block are the same, the service type corresponding to the data in the first transmission block is the first service type, and the data in the first transmission block is part or all of the first data.

[0030] Based on the above technical solution, in this application, by limiting the data of the same business type to be grouped into the same transmission block, it is ensured that data of other business types will not be transmitted on the dedicated resources allocated by the network device to the terminal device, thereby avoiding transmission errors.

[0031] In a second aspect, a communication method is provided, which is applied to sidelink communication. The method can be executed by a network device, or by a component of the network device (such as a chip or circuit), without limitation. For example, the network device can be a base station, etc.

[0032] It should be noted that the beneficial effects achieved by the various methods in the second aspect that are the same as those achieved in the first aspect will not be described again, and can be understood by referring to the beneficial effects in the first aspect.

[0033] The method includes: a network device receives first information from a terminal device, the first information includes indication information, and the indication information is used to indicate the service type corresponding to the first data; the network device allocates resources corresponding to the service type to the terminal device according to the first indication information.

[0034] Exemplarily, the network device may indicate to the terminal device the allocated resources of different service types by means of configuration information.

[0035] In a possible implementation, the first information further includes a first QoS parameter, where the first QoS parameter is a QoS requirement parameter of the first data of the terminal device, wherein the first QoS parameter is a QoS parameter not defined by the Third Generation Partnership Project 3GPP.

[0036] In a possible implementation manner, the indication information is provided by an upper layer of the terminal device, or the indication information is obtained by the terminal device according to the first data.

[0037] In a possible implementation, the service type includes at least one of the following: detection and avoidance of collisions (DAA) service, drone ID broadcast (BRID) service, and command and control (C2) service.

[0038] In a possible implementation, the indication information is used to indicate a service type corresponding to the Quality of Service (QoS) flow.

[0039] In a possible implementation, the first information further includes a layer 2 identifier L2 ID, and the indication information is used to indicate a service type of data of the terminal device corresponding to the L2 ID.

[0040] In a possible implementation, the indication information is used to indicate a service type corresponding to the QoS flow associated with the L2 ID.

[0041] In a possible implementation, the service types corresponding to the QoS flows are the same.

[0042] In one possible implementation, the method also includes: the network device receives a first transmission block from the terminal device, wherein the service type corresponding to the data in the first transmission block is the same, the service type corresponding to the data in the first transmission block is the first service type, the data in the first transmission block is part or all of the first data, the first transmission block is located on a first resource, and the first resource is used to transmit data of the first service type.

[0043] In a third aspect, a communication method is provided, which is applied to sidelink communication. The method can be executed by a terminal device, or by a component of the terminal device (such as a chip or circuit), without limitation. For example, the terminal device can be a drone, an aerial vehicle, etc.

[0044] The method includes: the terminal device obtains a second quality of service QoS parameter, the second QoS parameter is used to indicate the service type corresponding to the second data, wherein the second QoS parameter is a QoS requirement parameter of the second data of the terminal device, and the second QoS parameter is a service QoS parameter defined by the Third Generation Partnership Project 3GPP; the terminal device sends second information to the network device, and the second information includes the second QoS parameter.

[0045] Exemplarily, the second QoS parameter may be obtained by the terminal device from the core network via a non-access stratum (NAS) message.

[0046] Exemplarily, the “service type” in this application may include at least one of the following: detection and avoidance of collisions (DAA) service, drone ID broadcast (BRID) service, and command and control (C2) service.

[0047] Based on the above technical solution, in this application, when the QoS parameters are parameters defined by the standard, the terminal device can distinguish the service type of the data through the standard QoS parameters, and the terminal device can also send the QoS parameters to the network device. The terminal device can send data of the corresponding service type on the resources configured by the network device, so that the resources configured by the network device can be properly utilized and transmission errors can be avoided. For example, the terminal device can transmit DAA service data on the DAA dedicated resources configured by the network device, the terminal device can transmit BRID service data on the BRID dedicated resources configured by the network device, and the terminal device can transmit ordinary service data on ordinary resources configured by the network device.

[0048] In a possible implementation, the second QoS parameter is used by the network device to allocate resources corresponding to the service type to the terminal device.

[0049] In a possible implementation, the second QoS parameter is used to indicate a service type corresponding to the quality of service QoS flow.

[0050] In a possible implementation, the second information further includes a layer 2 identifier L2 ID, and the second QoS parameter is used to indicate a service type corresponding to the L2 ID.

[0051] In a possible implementation, the second QoS parameter is used to indicate a service type corresponding to the QoS flow associated with the L2 ID.

[0052] In a possible implementation, the service types corresponding to the QoS flows are the same.

[0053] In one possible implementation, the method also includes: determining a second resource allocated by the network device, the second resource being used to transmit data of a second service type; sending a second transmission block to the network device on the second resource, wherein the service type corresponding to the data in the second transmission block is the same, the service type corresponding to the data in the second transmission block is the second service type, and the data in the second transmission block is part or all of the second data.

[0054] Based on the above technical solution, in this application, by limiting the data of the same business type to be grouped into the same transmission block, it is ensured that data of other business types will not be transmitted on the dedicated resources allocated by the network device to the terminal device, thereby avoiding transmission errors.

[0055] In a fourth aspect, a communication method is provided, which is applied to sidelink communication. The method can be performed by a network device, or by a component of the network device (such as a chip or circuit), without limitation. For example, the network device can be a base station, etc.

[0056] It should be noted that the beneficial effects achieved by the various methods in the fourth aspect and those in the third aspect will not be described again, and can be understood by referring to the beneficial effects in the first aspect.

[0057] The method includes: a network device receives second information from a terminal device, the second information includes a second quality of service (QoS) parameter, the second QoS parameter is used to indicate a service type corresponding to the second data, wherein the second QoS parameter is a QoS requirement parameter of the second data of the terminal device, and the second QoS parameter is a service QoS parameter defined by the Third Generation Partnership Project (3GPP); the network device allocates resources corresponding to the service type to the terminal device according to the second QoS parameter.

[0058] In a possible implementation, the second QoS parameter is provided by an upper layer of the terminal device.

[0059] In a possible implementation, the service type includes at least one of the following: detection and avoidance of collisions (DAA) service, drone ID broadcast (BRID) service, and command and control (C2) service.

[0060] In a possible implementation, the second QoS parameter is used to indicate a service type corresponding to the QoS flow.

[0061] In a possible implementation, the second information further includes a layer 2 identifier L2 ID, and the second QoS parameter is used to indicate a service type corresponding to the L2 ID.

[0062] In a possible implementation, the second QoS parameter is used to indicate a service type corresponding to the QoS flow associated with the L2 ID.

[0063] In a possible implementation, the service types corresponding to the QoS flows are the same.

[0064] In one possible implementation, the method also includes: the network device receives a second transmission block from the terminal device, wherein the service type corresponding to the data in the second transmission block is the same, the service type corresponding to the data in the second transmission block is the second service type, and the data in the second transmission block is part or all of the second data, wherein the second transmission block is located in the second resource, and the second resource is used to transmit data of the second service type.

[0065] In a fifth aspect, a communication device is provided, which is configured to execute the method of any possible implementation of the first and third aspects. Specifically, the device may include units and / or modules, such as a transceiver unit and / or a processing unit, configured to execute the method of any possible implementation of the first and third aspects.

[0066] In one implementation, the device is a first node. When the device is a communication device, the communication unit may be a transceiver or an input / output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0067] In another implementation, the device is a chip, chip system, or circuit for the first node. When the device is a chip, chip system, or circuit for a communication device, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0068] In a sixth aspect, a communication device is provided, which is configured to execute the method of any possible implementation of the second aspect or the fourth aspect. Specifically, the device may include units and / or modules, such as a transceiver unit and / or a processing unit, configured to execute the method of any possible implementation of the second aspect or the fourth aspect.

[0069] In one implementation, the device is a second node. When the device is a communication device, the communication unit may be a transceiver or an input / output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0070] In another implementation, the device is a chip, chip system, or circuit for the second node. When the device is a chip, chip system, or circuit for a communication device, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0071] In a seventh aspect, a communication device is provided, comprising: at least one processor configured to execute a computer program or instruction stored in a memory to perform the method of any possible implementation of any of the first and third aspects. Optionally, the device further comprises a memory configured to store the computer program or instruction. Optionally, the device further comprises a communication interface, through which the processor reads the computer program or instruction stored in the memory.

[0072] In one implementation, the device is a first node.

[0073] In another implementation, the device is a chip, a chip system, or a circuit for the first node.

[0074] In an eighth aspect, a communication device is provided, comprising: at least one processor configured to execute a computer program or instruction stored in a memory to perform the method of any possible implementation of any of the second and fourth aspects. Optionally, the device further comprises a memory configured to store the computer program or instruction. Optionally, the device further comprises a communication interface, and the processor reads the computer program or instruction stored in the memory through the communication interface.

[0075] In one implementation, the device is a second node.

[0076] In another implementation, the device is a chip, a chip system, or a circuit for the second node.

[0077] In a ninth aspect, the present application provides a processor, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method of any possible implementation of any one of the first to fourth aspects.

[0078] In a specific implementation, the processor may be one or more chips, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, or various logic circuits. The input signal received by the input circuit may be, for example, but not limited to, received and input by a transceiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by a transmitter. The input circuit and the output circuit may be the same circuit, which functions as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation of the processor and various circuits.

[0079] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as processor output, reception, input and other operations, and can also be understood as sending and receiving operations performed by the radio frequency circuit and antenna. This application does not limit this.

[0080] In a tenth aspect, a processing device is provided, comprising a processor and a memory. The processor is configured to read instructions stored in the memory, receive signals via a transceiver, and transmit signals via a transmitter, to execute the method of any possible implementation of any one of aspects 1 to 4.

[0081] Optionally, there are one or more processors and one or more memories.

[0082] Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0083] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be set on different chips. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0084] It should be understood that related data interaction processes, such as sending indication information, can be the process of outputting indication information from the processor, and receiving capability information can be the process of receiving input capability information from the processor. Specifically, data output by the processor can be output to the transmitter, and input data received by the processor can be received from the transceiver. The transmitter and transceiver can be collectively referred to as a transceiver.

[0085] The processing device in the ninth aspect may be one or more chips. The processor in the processing device may be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated into the processor or located independently of the processor.

[0086] In an eleventh aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, wherein the program code includes a method for executing any possible implementation of the first to fourth aspects above.

[0087] In a twelfth aspect, a computer program product comprising instructions is provided, which, when run on a computer, enables the computer to execute the method in any possible implementation of the first to fourth aspects above.

[0088] In the thirteenth aspect, a chip system is provided, comprising a processor for calling and running a computer program from a memory, so that a device equipped with the chip system executes the methods in each implementation of any one of the first to fourth aspects above.

[0089] In a fourteenth aspect, a communication system is provided, comprising the terminal device and a network device. The terminal device is configured to execute any possible implementation method of any of the first and third aspects, and the network device is configured to execute any possible implementation method of any of the second and fourth aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0090] FIG1 is a schematic diagram of a scenario to which this application is applicable.

[0091] FIG2 is a schematic diagram of another scenario to which this application is applicable.

[0092] FIG3 is a schematic diagram of another scenario to which the present application is applicable.

[0093] FIG4 is a schematic flow chart of a communication method 400 provided in this application.

[0094] FIG5 is a schematic flowchart of a communication method 500 provided in this application.

[0095] FIG6 is a schematic block diagram of a communication device 600 provided in this application.

[0096] FIG7 is a schematic block diagram of a communication device 700 provided in this application. DETAILED DESCRIPTION

[0097] The technical solution in this application will be described below with reference to the accompanying drawings.

[0098] The technology provided in this application can be applied to various communication systems. For example, the communication system can be a fourth-generation (4G) communication system (such as a long-term evolution (LTE) system), a fifth-generation (5G) communication system, a world-wide interoperability for microwave access (WiMAX) or a wireless local area network (WLAN) system, a satellite communication system, a future communication system such as a sixth-generation (6G) mobile communication system, or a fusion system of multiple systems. Among them, the 5G communication system can also be called a new radio (NR) system. Satellite communication system, future communication system such as a sixth-generation (6G) mobile communication system, or a fusion system of multiple systems.

[0099] The network device may be an entity on the network side for transmitting or receiving signals. The network device may be an access device for a communication device to access the wireless communication system in a wireless manner, for example, the network device may be a base station. The base station can broadly cover the following various names, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), access network equipment in open radio access network (O-RAN), relay station, access point, transmission point (TRP), transmitting point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, radio node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), radio head (RRH), central unit (CU), distributed unit (DU), radio unit (RU), centralized unit control plane (CU-CP) node, centralized unit user plane (CU-UP) node, positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The network device can also refer to a communication module, a modem or a chip for being arranged in the aforementioned device or apparatus. The network device can also be a mobile switching center and a device to device (Device-to-Device, D2D), vehicle outreach (vehicle-to-everything, V2X), a device that performs the base station function in machine to machine (machine-to-machine, M2M) communications, a network side device in a 6G network, a device that performs the base station function in a future communication system, etc. The network device can support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.

[0100] In a network structure, the network device may also refer to a centralized unit (CU) or a distributed unit (DU), or the network device may also be composed of a CU and a DU. CU and DU can be understood as a division of the base station from a logical function perspective. Among them, the CU and DU can be physically separated or deployed together, and the embodiments of the present application do not specifically limit this. A CU can be connected to a DU, or multiple DUs can share a CU, which can save costs and facilitate network expansion. The division of CU and DU can be based on the protocol stack. One possible way is to deploy the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP) and Packet Data Convergence Protocol (PDCP) layers in the CU, and the remaining Radio Link Control (RLC) layer, Media Access Control (MAC) layer and physical layer in the DU. The present application does not limit the above-mentioned protocol stack segmentation method, and other segmentation methods may be used. For details, please refer to the technical research report (TR) 38.801v14.0.0.

[0101] The terminal devices in this application may include drones and aerial vehicles. For example, "aerial vehicles" may include airships, gliders, hot air balloons, jet backpacks, etc.

[0102] Uncrewed aerial vehicles (UAVs), a new type of aircraft, are becoming increasingly popular due to their flexibility and convenience. Cellular networks provide UAVs with key features such as wide coverage, high reliability, high security, and continuous mobility, as well as oversight by regulators. The communication environment of UAVs differs significantly from that of standard user equipment (UE). UAVs primarily fly above base stations, connecting to them via the Uu port and primarily communicating in line of sight (LOS). Therefore, UAVs can receive signals from more base stations. As shown in Figure 1, a UAV can simultaneously communicate with base stations #1, #2, and #3.

[0103] Drones (UAVs) may face the risk of collision while in flight. To prevent collisions, the current 3rd Generation Partnership Project (3GPP) system supports a detect and avoid collision (DAA) mechanism. This includes network-assisted DAA and PC5-based DAA. Specifically, for network-assisted DAA, the unmanned aircraft system traffic management (UTM) obtains the flight path of each UAV during the flight authorization process or application-layer reporting. In some cases, the flight paths of different UAVs overlap or are within the same area. The UTM can request the 5G system (5GS) to perform a DAA between any two UAVs whose flight paths may overlap or be within the same area. The network determines the collision risk of the UAVs based on the flight paths reported by the UAVs. If a collision risk exists, the network issues a collision avoidance command to the UE. Network-assisted DAA is useful for scenarios where regulations may deem sidelink transmission unresolvable or the UAV's PC5 connection is unavailable. In the DAA based on the PC5 port, the drone directly broadcasts the DAA message (for example, location information, etc.) through the PC5 port. After receiving the DAA message, the other end drone determines the collision risk. If there is a collision risk, it sends a collision resolution message to the other end UE, and the other end UE replies with a collision resolution response message. On the other hand, regulators require drones to broadcast their IDs during flight to facilitate continuous management of drones. The 3GPP system supports drone ID broadcasts (Broadcast UAV ID, BRID), including BRIDs based on the multicast broadcast service (MBS) and BRIDs based on the PC5 port. The MBS-based BRID uses the existing MBS to broadcast the drone ID. The PC5-based BRID is similar to DAA, and the drone broadcasts through the PC5 port. Figure 2 shows the DAA scenario and BRID scenario described above. For example, DAA services can be carried out between drone #1 and drone #2, and BRID services can be carried out between drone #1 and the regulator.

[0104] The Uu interface allocates resources at the resource block (RB) granularity, while Sidelink allocates channel resources in "resource pools." Existing New Radio (NR) Sidelink systems already support the configuration of up to eight resource pools for standard Sidelink communications, where "standard Sidelink communications" refers to all Sidelink communications other than Sidelink relay discovery. For Sidelink relay discovery, the protocol defines a dedicated resource pool, meaning that this resource pool can only be used to send Sidelink relay discovery messages.

[0105] There are two ways to obtain resources for Sidelink, namely base station scheduling mode (mode1) and user equipment (UE) selection mode (mode2). In base station scheduling mode (mode1), the base station can indicate which resource pool the currently scheduled resources belong to by carrying the resource pool (RP) index in the downlink control information (DCI). After receiving the scheduled sidelink resources, the UE will first determine which destination (destination) data to send, and then determine which logical channel data of the destination to send. Among them, "destination" can be a unicast, multicast or broadcast. Simply put, it is to see which destination has the highest priority for the data to be transmitted among all destinations, and then select the destination, and then sort the cached data and media access control control element (MAC CE) in each logical channel in the destination, and give priority to sending high-priority data or MAC CE.

[0106] 3GPP defines the aerial to everything (A2X) layer for drone services. A2X communicates based on the PC5 port and transmits over sidelink. A2X includes BRID, DAA, and command and control (C2) communications (C2 is the communication between the drone and the controller). The existing standard introduces additional resource pools for drones, the A2X resource pool. For example, DAA-dedicated resources transmit DAA service data, and BRID-dedicated resource pools transmit BRID services. Specifically, when the base station broadcasts a SIB message, it can add additional indication information to the A2X resource pool to indicate whether the resources are used for DAA services and / or BRID services. Currently, 3GPP has defined the standard PC5 interface 5G Service Quality Indication Information (PC5 5G QoS Identification, PC5 PQI) (hereinafter referred to as "PQI") to indicate the different services supported by drones. See technical specification (TS) 23.256. The table defines specific PQI values ​​and their corresponding specific A2X service types.

[0107] The current standard has stipulated that the base station can configure a dedicated resource pool for the UAV, which can support the UAV to transmit data for DAA services and / or BRID services. However, for the UAV, when data arrives, if a non-standard PQI is used or no PQI is used, the UAV cannot distinguish the specific service the arriving data is used for based on the standard protocol. Alternatively, when service data arrives at the upper layer, if the upper layer uses a non-standard PQI or no PQI is used, the UAV lower layer cannot distinguish the specific service the arriving service data is used for based on the standard PQI protocol. Therefore, it may cause the UAV to fail to transmit data of the corresponding service type on the resource pool configured by the base station, resulting in transmission errors.

[0108] In view of this, the present application provides a communication method, when the terminal device determines that the PQI is not a standard PQI (or, when the upper layer of the terminal device determines that the PQI is not a standard PQI), the terminal device can obtain indication information, which is used to indicate the service type corresponding to the data. The terminal device can also send a first indication information to the network device to instruct the network device to allocate resources of this service type. Subsequently, the terminal device can send service data of the corresponding service type on the resources configured by the network device, so that the resources configured by the network device can be correctly utilized to avoid transmission errors. For example, the terminal device can transmit DAA service data on the DAA dedicated resources configured by the network device, the terminal device can transmit BRID service data on the BRID dedicated resources configured by the network device, and the terminal device can transmit ordinary service data on ordinary resources configured by the network device.

[0109] FIG3 is a schematic diagram of a scenario to which the present application is applicable. As shown in FIG3 , the application scenario is a scenario in which a drone determines the service type corresponding to service data during flight and reports the service type to a network device.

[0110] FIG4 is a schematic flow chart of a communication method 400 provided by the present application. As shown in FIG4 , the method includes:

[0111] 410. The terminal device obtains a first QoS parameter and / or indication information, where the indication information is used to indicate a service type corresponding to the first data. The first QoS parameter is a QoS requirement parameter of the first data of the terminal device.

[0112] Exemplarily, the first QoS parameter is a QoS parameter not defined by 3GPP.

[0113] The "first data" in this application can be understood as data from an upper layer. The "data" in this application can also be replaced by "business data".

[0114] In the present application, “the first QoS parameter is a QoS parameter not defined by 3GPP” can also be understood as “the first QoS parameter is a QoS parameter corresponding to a service type not specified by the 3GPP standard”.

[0115] In a possible implementation scenario, "non-3GPP defined parameters" can be understood as a private parameter, not a parameter specified in the protocol. For example, assuming that the QoS parameter is PQI, the protocol defines that when the PQI value is 40 to 44, and 62 to 65, there is a corresponding service type. The "first QoS parameter" in this application can be understood as a PQI value of 10, or a PQI value of 100. At this time, the protocol does not specify the service type corresponding to the PQI value of 10, nor does it specify the service type corresponding to the PQI value of 100.

[0116] In another possible implementation scenario, "non-3GPP defined parameters" can be understood as, although the parameters defined in 3GPP are used, the corresponding service type is not defined in the protocol. For example, assuming that the QoS parameter is PQI, the protocol defines that when the PQI value is 42, the corresponding service type is C2 service; when the PQI value is 62, the corresponding service type is BRID service; when the PQI value is 64, the corresponding service type is DAA service. The "first QoS parameter" in this application can be understood as, when the PQI value is 42, the corresponding service type customized within the terminal device is DAA service; when the PQI value is 62, the corresponding service type customized within the terminal device is C2 service; when the PQI value is 64, the corresponding service type customized within the terminal device is BRID service.

[0117] Optionally, the terminal device may determine whether the QoS parameter is the first QoS parameter or the second QoS parameter, where the second QoS parameter may be understood as "the QoS parameter defined by 3GPP" or "the QoS parameter corresponding to the service type specified in the 3GPP standard." Specifically, how the terminal device determines whether the QoS parameter is a parameter specified in the protocol or not may be implemented internally by the terminal device and is not limited.

[0118] It should be noted that the specific name of the QoS parameter is not limited in this application. For example, the QoS parameter can be PQI or other parameters. As long as the parameter is used to characterize the QoS requirements, it falls within the scope of protection required by this application.

[0119] In this application, for example, "service type" includes at least one of the following: detection and avoidance of collisions (DAA) service, drone ID broadcast (BRID) service, and command and control (C2) service. Exemplarily, the service type corresponding to the first data may include: DAA service type and BRID service type.

[0120] Exemplarily, when the bit value in the indication information is "01", it is used to indicate the DAA service, and when the bit value in the indication information is "10", it is used to indicate the BRID service. Exemplarily, the indication information can indicate different service types by multiplexing the name of a QoS field in the PQI, for example, the name of a QoS field in the PQI is DAA-QoS, or the name of a QoS field in the PQI is DAA-QoS.

[0121] In this application, “the terminal device obtains the first QoS parameter and / or indication information” may be implemented in the following ways, for example:

[0122] Method 1

[0123] In another possible implementation, the terminal device obtains a first QoS parameter, the upper layer of the terminal device sends the first QoS parameter to the lower layer, and the lower layer of the terminal device determines that the first QoS parameter is not a QoS parameter defined by the standard. Therefore, the lower layer of the terminal device can determine the indication information based on the first QoS parameter and / or based on the first data.

[0124] Method 2

[0125] In one possible implementation, the terminal device obtains a first QoS parameter. The terminal device determines the first QoS parameter, which is not a QoS parameter defined by the standard. Therefore, the upper layer of the terminal device can determine the indication information based on the first QoS parameter and / or based on the first data, and send the indication information to the lower layer.

[0126] Method 3

[0127] In another possible implementation, the terminal device obtains the first QoS parameter, and the upper layer of the terminal device determines the first QoS parameter, which is not a QoS parameter defined by the standard. Therefore, the upper layer of the terminal device can determine the indication information based on the first QoS parameter and / or based on the first data, and send the first QoS parameter and the indication information together to the lower layer.

[0128] Method 4

[0129] In a possible implementation, the upper layer of the terminal device may determine the indication information based on the data and send the indication information to the lower layer. Alternatively, the lower layer of the terminal device may determine the indication information based on the data.

[0130] It should be noted that, in mode 4, the terminal device initially only obtains the indication information but does not obtain the first QoS parameter. Subsequently, the terminal device may receive the first QoS parameter from the core network via a NAS message.

[0131] In this application, the "upper layer of the terminal device" can be understood as, for example, the A2X layer or the application layer; the "lower layer of the terminal device" can be understood as, for example, the physical layer or the access layer.

[0132] Optionally, in the present application, since the terminal device can distinguish the service type corresponding to the data through the obtained indication information, if the network device has pre-configured resources of different service types for the terminal device, the terminal device can directly transmit data of the corresponding service type on the corresponding resources, thereby avoiding transmission errors.

[0133] 420. The terminal device sends the first information to the network device, where the first information includes the indication information.

[0134] Correspondingly, the network device receives the first information.

[0135] In this application, the indication information can be used by the network device to allocate resources corresponding to the service type to the terminal device.

[0136] Exemplarily, the first information may be sidelink UE information (SUI).

[0137] In one possible implementation, the indication information can directly indicate the service type at the QoS flow granularity. It can also be understood that the indication information is used to indicate the service type corresponding to each QoS flow. Exemplarily, the indication information can uniformly indicate the service type corresponding to all QoS flows; Exemplarily, the indication information can also separately indicate the service type corresponding to each QoS flow. This application does not limit the specific implementation method.

[0138] In another possible implementation, the first information may further include a Layer 2 identifier (L2 ID), where the L2 ID is used to identify a terminal device. In this case, the indication information may be used to indicate the service type of the data of the terminal device corresponding to the L2 ID. For example, the L2 ID may be used to determine which terminal devices are the destination terminals. In this case, the indication information may specifically indicate the service type corresponding to the terminal device. Assuming that the first information includes L2 ID #1, in one possible implementation, the indication information may indicate that the service type corresponding to L2 ID #1 is a DAA service.

[0139] In another possible implementation, if multiple QoS flows are associated with the L2 ID, the indication information can be used to indicate the service type corresponding to each of the multiple QoS flows. For example, assuming that there are two QoS flows under L2 ID#1, namely QoS flow#1 and QoS flow#1#, the indication information includes field#1 and field#2, wherein field#1 is used to indicate that the service type is a DAA service, and field#2 is used to indicate a BRID service. The indication information can indicate that the service type corresponding to QoS flow#1 is a DAA service, and the service type corresponding to QoS flow#2 is a BRID service. For example, assuming that there are 5 QoS flows under L2 ID#2, and the indication information only includes field#1, field#1 can indicate that the service types corresponding to the 5 QoS flows under L2 ID#2 are all BRID service types. At this point, it can also be understood that the service types corresponding to multiple QoS flows associated with the same L2 ID are the same.

[0140] In the present application, in one possible implementation, in the above-mentioned methods 1 to 2, the first information may further include a first QoS parameter. In another possible implementation, the first QoS parameter may not be sent in the same message as the indication information. For example, the first QoS parameter may be sent to the network device through other signaling after the indication information is sent.

[0141] The above implementation can be understood as being mainly for unicast services. If it is a broadcast service, the service type can be distinguished by directly including the L2 ID in the first information.

[0142] Optionally, the method further includes step 430, in which the network device allocates resources corresponding to the service type to the terminal device according to the indication information.

[0143] In this application, in one possible implementation, the network device allocates corresponding resources to the terminal device based on the indication information reported by the terminal device. For example, if the indication information is used to indicate that the service types include DAA service and C2 service, the network device can allocate a DAA dedicated resource pool for the DAA service and a common resource pool for the C2 service.

[0144] In another possible implementation, the network device may pre-allocate resources corresponding to each service type for the terminal device. For example, the network device may allocate a DAA-specific resource pool for DAA services, or a BRID-specific resource pool for BRID services and a common resource pool for C2 services.

[0145] Exemplarily, the network device may indicate the resources allocated to the terminal device by sending configuration information.

[0146] In this application, “resources” may be frequency domain resources, time domain resources, resource pools, resource blocks (RBs), physical resource blocks (PRBs), etc., and this application does not limit them.

[0147] Optionally, the method further includes step 440, where the terminal device determines a first resource allocated by the network device, where the first resource is used to transmit data of the first service type.

[0148] Assuming that the service type corresponding to the first data of the terminal device is the DAA service, and the resource allocated by the network device to the terminal device for transmitting the data of the DAA service is the first resource, the terminal device can determine the location of the first resource.

[0149] Optionally, the method further includes step 450, in which the terminal device sends a first transmission block to the network device on the first resource.

[0150] Correspondingly, the network device receives the first transmission block from the terminal device.

[0151] In this application, after the terminal device receives the sidelink resources scheduled by the network device, it will first determine which destination data to send, and then determine which logical channel data of the destination to send, and determine that the data to be transmitted has the highest priority among all destinations, then select the destination, and then sort the cached data and media access control element (MAC CE) in each logical channel in the destination, and give priority to sending high-priority data or MAC CE. This process can also be understood as the process of the terminal device group transport block (TB).

[0152] Furthermore, the present application also proposes that the service type corresponding to the data in the transmission block (i.e., the first transmission block) of the terminal device group is the same, that is, the service type corresponding to the data in the first transmission block is the first service type, and the data in the first transmission block is part or all of the first data. For example, if the first service type is a DAA service, the data in the first transmission block is data of the DAA service type in the first data.

[0153] Based on the above technical solution, considering that when the QoS parameters are not parameters defined by the standard, the terminal device cannot distinguish the service type of the data through the standard protocol, at this time, the present application proposes that the terminal device can determine the first indication information inside, and the indication information is used to indicate the service type corresponding to the data. The terminal device can also send the first indication information to the network device. Thus, the terminal device can send service data of the corresponding service type on the resources configured by the network device, so that the resources configured by the network device can be correctly utilized to avoid transmission errors. For example, the terminal device can transmit DAA service data on the DAA dedicated resources configured by the network device, the terminal device can transmit BRID service data on the BRID dedicated resources configured by the network device, and the terminal device can transmit ordinary service data on ordinary resources configured by the network device.

[0154] In addition, in this application, by limiting the data of the same business type to be grouped into the same transmission block, it is ensured that data of other business types will not be transmitted on the dedicated resources allocated by the network device to the terminal device, thereby avoiding transmission errors.

[0155] FIG5 is a schematic flow chart of a communication method 500 provided in the present application. Implementations in method 500 that are the same as those in method 400 will not be described again. Method 500 mainly describes differences from method 400. As shown in FIG5 , the method includes:

[0156] 510. The terminal device obtains a second QoS parameter, where the second QoS parameter is used to indicate a service type corresponding to the second data. The second QoS parameter is a QoS requirement parameter of the second data of the terminal device, and the second QoS parameter is a QoS parameter defined by 3GPP.

[0157] In this application, "the second QoS parameter is a 3GPP-defined QoS parameter" can also be understood to mean that the second QoS parameter is a QoS parameter corresponding to the service type specified by the 3GPP standard. For example, the 3GPP-defined QoS parameters can refer to the parameters defined in TS 38.331, and of course also include QoS parameters newly defined by 3GPP in the future. For example, different PQI values ​​defined in TS 23.256 can indicate different service types.

[0158] Exemplarily, the second QoS parameter may be obtained by the terminal device from the core network via a NAS message.

[0159] Exemplarily, the “service type” in this application may include at least one of the following: detection and avoidance of collisions (DAA) service, drone ID broadcast (BRID) service, and command and control (C2) service.

[0160] In a possible implementation, after obtaining the second QoS parameter, the terminal device may also generate second indication information based on the second QoS parameter and / or the second data, where the second indication information is used to indicate the service type corresponding to the second data.

[0161] 520. The terminal device sends second information to the network device, where the second information includes a second QoS parameter.

[0162] Correspondingly, the network device receives the second information from the terminal device.

[0163] Exemplarily, the second information may be sidelink UE information (SUI).

[0164] In this application, the second QoS parameter is used by the network device to allocate resources corresponding to the service type to the terminal device.

[0165] In one possible implementation, the second QoS parameter can directly indicate the service type at the QoS flow granularity. It can also be understood that the second QoS parameter is used to indicate the service type corresponding to each QoS flow. Exemplarily, the second QoS parameter can uniformly indicate the service type corresponding to all QoS flows; exemplary, the second QoS parameter can also separately indicate the service type corresponding to each QoS flow. This application is not limited to the specific implementation method.

[0166] In another possible implementation, the second information may further include a layer 2 identifier L2 ID, where the L2 ID is used to indicate the type of the terminal device. In this case, the second QoS parameter may be used to indicate the service type of the data of the terminal device corresponding to the L2 ID.

[0167] In yet another possible implementation, if the L2 ID is associated with multiple QoS flows, the second QoS parameter may be used to indicate service types corresponding to the multiple QoS flows.

[0168] In another possible implementation, the service types corresponding to the multiple QoS flows are the same.

[0169] The specific implementation method can be understood by referring to the description and examples related to step 420 in method 400, and will not be repeated here.

[0170] In some implementations, if the second indication information is generated in step 510 , then in step 520 , the second information may further include the second indication information.

[0171] Optionally, the method further includes step 530, in which the network device allocates resources corresponding to the service type to the terminal device according to the second QoS parameter.

[0172] In this application, in one possible implementation, the network device allocates corresponding resources to the terminal device based on the second QoS parameter reported by the terminal device. For example, if the second QoS parameter is used to indicate that the service type includes DAA service and C2 service, the network device can allocate a DAA dedicated resource pool for the DAA service and a common resource pool for the C2 service.

[0173] In another possible implementation, the network device may pre-allocate resources corresponding to each service type for the terminal device. For example, the network device allocates DAA-specific resources for DAA services, allocates BRID-specific resources for BRID services, or allocates common resources for C2 services.

[0174] Optionally, the method further includes step 540, where the terminal device determines a second resource allocated by the network device, where the second resource is used to transmit data of a second service type.

[0175] Assuming that the service type corresponding to the second data of the terminal device is the DAA service, and the resource allocated by the network device to the terminal device for transmitting the data of the DAA service is the second resource, the terminal device can determine the location of the second resource.

[0176] Optionally, the method further includes step 550, in which the terminal device sends a second transmission block to the network device on the second resource.

[0177] Correspondingly, the network device receives the second transmission block from the terminal device.

[0178] In this application, after the terminal device receives the sidelink resources scheduled by the network device, it will first determine which destination data to send, and then determine which logical channel data of the destination to send, and determine that the data to be transmitted has the highest priority among all destinations, then select that destination, and then sort the cached data and media access control element (MAC CE) in each logical channel in that destination, and give priority to sending high-priority data or MAC CE. This process can also be understood as the process of the terminal device group transmission block.

[0179] Furthermore, the present application also proposes that the service type corresponding to the data in the transport block (TB) (i.e., the second transport block) of the terminal device group is the same, that is, the service type corresponding to the data in the second transport block is the second service type, and the data in the second transport block is part or all of the second data. For example, if the second service type is DAA service, the data in the second transport block is data of the DAA service type in the second data.

[0180] Based on the above technical solution, in this application, when the QoS parameters are parameters defined by the standard, the terminal device can distinguish the service type of the data through the standard QoS parameters. The terminal device can also send the QoS parameters to the network device. Thus, the terminal device can send service data of the corresponding service type on the resources configured by the network device, so that the resources configured by the network device can be correctly utilized to avoid transmission errors. For example, the terminal device can transmit DAA service data on the DAA dedicated resources configured by the network device, the terminal device can transmit BRID service data on the BRID dedicated resources configured by the network device, and the terminal device can transmit ordinary service data on ordinary resources configured by the network device.

[0181] In addition, in this application, by limiting the data of the same service type to be grouped into the same transmission block, it is ensured that data of other service types will not be transmitted on the dedicated resources allocated by the network device to the terminal device, thereby avoiding waste of dedicated resources.

[0182] It should be understood that the examples in methods 400 and 500 in the embodiments of the present application are merely intended to facilitate understanding of the embodiments of the present application by those skilled in the art, and are not intended to limit the embodiments of the present application to the specific scenarios illustrated. Those skilled in the art can obviously make various equivalent modifications or variations based on the examples in methods 400 and 500, and such modifications or variations also fall within the scope of the embodiments of the present application.

[0183] It can also be understood that some optional features in the various embodiments of the present application may not depend on other features in certain scenarios, and may also be combined with other features in certain scenarios, without limitation.

[0184] It is also understood that the various embodiments described in this application may be independent solutions or combined according to internal logic, and all of these solutions fall within the scope of protection of this application. In addition, the explanations or descriptions of various terms appearing in the embodiments may refer to or explain each other in the various embodiments, without limitation.

[0185] It should be understood that the term "and / or" in this document simply describes an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0186] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of interaction between each node. It is understandable that each node, such as a terminal device, a network device, includes a hardware structure and / or software module corresponding to the execution of each function in order to implement the above functions. Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0187] In the embodiment of the present application, the terminal device and the network device can be divided into functional modules according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module according to each function.

[0188] FIG6 is a schematic block diagram of a communication device 600 according to an embodiment of the present application. As shown in the figure, the device 600 may include a transceiver unit 610 and a processing unit 620.

[0189] In one possible design, the apparatus 600 may be the terminal device in the above method embodiment, or may be a chip for implementing the functions of the terminal device in the above method embodiment. It should be understood that the apparatus 600 may correspond to the terminal device in methods 400 and 500 according to the embodiments of the present application, and the apparatus 600 may perform the steps corresponding to the terminal device in methods 400 and 500 according to the embodiments of the present application.

[0190] In one possible implementation, the transceiver unit is used to obtain a first quality of service QoS parameter and indication information, the indication information is used to indicate the service type corresponding to the first data, and the first QoS parameter is the first data QoS requirement parameter of the terminal device; the transceiver unit is used to send first information to the network device, and the first information includes indication information.

[0191] In one possible implementation, the processing unit is used to determine a first resource allocated by the network device, and the first resource is used to transmit data of a first service type; the transceiver unit is used to send a first transmission block to the network device on the first resource, wherein the service types corresponding to the data in the first transmission block are the same, the service type corresponding to the data in the first transmission block is the first service type, and the data in the first transmission block is part or all of the first data.

[0192] In one possible implementation, the transceiver unit is used to obtain a second quality of service QoS parameter, where the second QoS parameter is used to indicate the service type corresponding to the second data, wherein the second QoS parameter is a QoS requirement parameter of the terminal device, and the second QoS parameter is a service QoS parameter defined by the Third Generation Partnership Project 3GPP; the transceiver unit is used to send second information to the network device, where the second information includes the second QoS parameter.

[0193] In one possible implementation, the processing unit is used to determine a second resource allocated by the network device, and the second resource is used to transmit data of a second service type; the transceiver unit is used to send a second transmission block to the network device on the second resource, wherein the service type corresponding to the data in the second transmission block is the same, the service type corresponding to the data in the second transmission block is the second service type, and the data in the second transmission block is part or all of the second data.

[0194] In one possible design, the apparatus 600 may be the network device in the above method embodiment, or may be a chip for implementing the functions of the network device in the above method embodiment. It should be understood that the apparatus 600 may correspond to the network device in method 400 or method 500 according to the embodiments of the present application, and the apparatus 600 may perform the steps corresponding to the network device in method 400 or method 500 according to the embodiments of the present application.

[0195] In one possible implementation, the transceiver unit is used to receive first information from a terminal device, where the first information includes indication information, and the indication information is used to indicate a service type corresponding to the first data; the processing unit is used to allocate resources corresponding to the service type to the terminal device based on the first indication information.

[0196] In one possible implementation, the transceiver unit is used to receive a first transmission block from a terminal device, wherein the service type corresponding to the data in the first transmission block is the same, the service type corresponding to the data in the first transmission block is the first service type, the data in the first transmission block is part or all of the first data, the first transmission block is located on a first resource, and the first resource is used to transmit data of the first service type.

[0197] In one possible implementation, the transceiver unit is used to receive second information from a terminal device, the second information includes a second quality of service QoS parameter, and the second QoS parameter is used to indicate the service type corresponding to the second data, wherein the second QoS parameter is a QoS requirement parameter of the second data of the terminal device, and the second QoS parameter is a service QoS parameter defined by the Third Generation Partnership Project 3GPP; the processing unit is used to allocate resources corresponding to the service type to the terminal device according to the second QoS parameter.

[0198] In one possible implementation, the transceiver unit is used to receive a second transmission block from a terminal device, wherein the service type corresponding to the data in the second transmission block is the same, the service type corresponding to the data in the second transmission block is the second service type, and the data in the second transmission block is part or all of the second data, wherein the second transmission block is located in a second resource, and the second resource is used to transmit data of the second service type.

[0199] It should also be understood that the device 600 here is embodied in the form of a functional unit. The term "unit" here can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merging logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the device 600 can be specifically the first node or the second node in the above-mentioned embodiment, and can be used to execute the various processes and / or steps corresponding to the first node or the second node in the above-mentioned method embodiments. To avoid repetition, they will not be described here.

[0200] The apparatus 600 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the terminal device or network device in the above-mentioned method. The functions can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.

[0201] In addition, the transceiver unit 610 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing unit may be a processing circuit.

[0202] It should be noted that the device in FIG6 can be a terminal device or network device in the aforementioned embodiment, or a chip or chip system, such as a system on a chip (SoC). The transceiver unit can be an input / output circuit or a communication interface; the processing unit can be a processor, microprocessor, or integrated circuit integrated on the chip. This is not limited here.

[0203] Figure 7 is a schematic block diagram of a communication device 700 provided in an embodiment of the present application. As shown in the figure, the device 700 includes: at least one processor 720. The processor 720 is coupled to a memory and is configured to execute instructions stored in the memory to send and / or receive signals. Optionally, the device 700 also includes a memory 730 for storing instructions. Optionally, the device 700 also includes a transceiver 710, and the processor 720 controls the transceiver 710 to send and / or receive signals.

[0204] It should be understood that the processor 720 and memory 730 may be combined into one processing device, and the processor 720 is configured to execute the program code stored in the memory 730 to implement the above functions. In specific implementations, the memory 730 may also be integrated into the processor 720 or independent of the processor 720.

[0205] It should also be understood that the transceiver 710 may include a transceiver (or receiver) and a transmitter (or transmitter). The transceiver may further include an antenna, and the number of antennas may be one or more. The transceiver 710 may also be a communication interface or interface circuit.

[0206] Specifically, the transceiver 710 in the device 700 may correspond to the transceiver unit 610 in the device 600 , and the processor 620 in the device 600 may correspond to the processing unit 620 in the device 600 .

[0207] As a solution, the apparatus 700 is used to implement the operations performed by the terminal device in the above various method embodiments.

[0208] For example, the processor 720 is configured to execute computer programs or instructions stored in the memory 730 to implement the relevant operations of the terminal device in the above various method embodiments, such as the method performed by the terminal device in any of the illustrated embodiments of method 400 and method 500.

[0209] As another solution, the apparatus 700 is configured to implement the operations performed by the network device in each of the above method embodiments. For example, the processor 720 is configured to execute computer programs or instructions stored in the memory 730 to implement the relevant operations of the network device in each of the above method embodiments. For example, the method performed by the network device in any of the embodiments shown in methods 400 and 500.

[0210] It should be understood that the specific process of each transceiver and processor executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0211] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it will not be described in detail here.

[0212] It should be noted that the processor in the embodiments of the present application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or by software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0213] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous-link DRAM (SLDRAM), and direct RAM-bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0214] According to the method provided in the embodiments of the present application, the present application also provides a computer program product, which stores computer program code. When the computer program code runs on a computer, the computer executes the method performed by a terminal device or a network device in any one of the embodiments of method 400 and method 500.

[0215] According to the method provided in the embodiments of the present application, the present application also provides a computer-readable medium, which stores program code. When the program code runs on a computer, the computer executes the method performed by the first node or the second node in the above embodiment.

[0216] According to the method provided in the embodiment of the present application, the present application also provides a communication system, which includes a terminal device and a network device. The terminal device is used to perform the steps corresponding to the terminal device in the above methods 400 and 500, and the network device is used to perform the steps corresponding to the network device in the above methods 400 and 500.

[0217] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

[0218] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disc (SSD)).

[0219] In each of the above-mentioned device embodiments, the corresponding modules or units perform the corresponding steps. For example, the transceiver unit (transceiver) performs the receiving or sending steps in the method embodiments, and other steps except sending and receiving can be performed by the processing unit (processor). The functions of the specific units can be referred to in the corresponding method embodiments. There can be one or more processors.

[0220] As used in this specification, the terms "component," "module," "system," and the like are used to represent computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. By way of illustration, both an application running on a computing device and a computing device can be a component. One or more components can reside in a process and / or an execution thread, and a component can be located on a computer and / or distributed between two or more computers. In addition, these components can be executed from various computer-readable media having various data structures stored thereon. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component on a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0221] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0222] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described systems, devices and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0223] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0224] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0225] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0226] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0227] It should be understood that references to "embodiments" throughout this specification mean that a particular feature, structure, or characteristic associated with the embodiment is included in at least one embodiment of the present application. Therefore, various embodiments throughout this specification do not necessarily refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0228] It should also be understood that the ordinal numbers such as "first" and "second" mentioned in the embodiments of the present application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. For example, the first PDSCH and the second PDSCH can be the same physical channel or different physical channels, and such names do not indicate a difference in the amount of information, content, priority, or importance of the two physical channels.

[0229] It should also be understood that, in this application, "at least one" means one or more, and "plurality" means two or more. "At least one item" or similar expressions refers to one or more items, that is, any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a, b, and c.

[0230] It should also be understood that in each embodiment of the present application, "A corresponds to B" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based solely on A, and B can also be determined based on A and / or other information.

[0231] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, applied to sidelink communication, characterized in that: include: The terminal device obtains a first quality of service QoS parameter and indication information, where the indication information is used to indicate a service type corresponding to the first data, and the first QoS parameter is a QoS requirement parameter of the first data of the terminal device; The terminal device sends first information to the network device, where the first information includes the indication information.

2. The method according to claim 1, characterized in that The indication information is obtained from an upper layer of the terminal device, or the indication information is obtained by the terminal device according to the first data.

3. The method according to claim 1 or 2, characterized in that The indication information is used by the network device to configure resources corresponding to the service type for the terminal device.

4. The method according to any one of claims 1 to 3, characterized in that The first QoS parameter is a QoS parameter not defined by the 3rd Generation Partnership Project 3GPP.

5. The method according to any one of claims 1 to 4, characterized in that The first information also includes the first QoS parameter.

6. The method according to any one of claims 1 to 5, characterized in that The service type includes at least one of the following: detection and avoidance of collision DAA service, drone ID broadcast BRID service, command and control C2 service.

7. The method according to any one of claims 1 to 6, characterized in that The indication information is used to indicate the service type corresponding to the Quality of Service QoS flow.

8. The method according to any one of claims 1 to 6, characterized in that The first information also includes a layer 2 identifier L2 ID, and the indication information is used to indicate a service type of data of a terminal device corresponding to the L2 ID.

9. The method according to claim 8, characterized in that The indication information is used to indicate the service type corresponding to the QoS flow associated with the L2 ID.

10. The method according to claim 9, characterized in that The service types corresponding to the QoS flows are the same.

11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: Determine a first resource allocated by the network device, where the first resource is used to transmit data of a first service type; A first transmission block is sent to the network device on the first resource, wherein the service types corresponding to the data in the first transmission block are the same, the service type corresponding to the data in the first transmission block is the first service type, and the data in the first transmission block is part or all of the first data.

12. A communication method, applied to sidelink communication, characterized in that: include: The network device receives first information from the terminal device, where the first information includes indication information, where the indication information is used to indicate a service type corresponding to the first data; The network device allocates resources corresponding to the service type to the terminal device according to the first indication information.

13. The method according to claim 12, characterized in that The first information also includes a first QoS parameter, which is a QoS requirement parameter of the first data of the terminal device, wherein the first QoS parameter is a QoS parameter not defined by the Third Generation Partnership Project 3GPP.

14. The method according to claim 12 or 13, characterized in that The indication information is provided by an upper layer of the terminal device, or the indication information is obtained by the terminal device according to the first data.

15. The method according to any one of claims 12 to 14, characterized in that The service type includes at least one of the following: detection and avoidance of collision DAA service, drone ID broadcast BRID service, command and control C2 service.

16. The method according to any one of claims 12 to 15, characterized in that The indication information is used to indicate the service type corresponding to the Quality of Service QoS flow.

17. The method according to any one of claims 12 to 15, characterized in that The first information also includes a layer 2 identifier L2 ID, and the indication information is used to indicate a service type of data of a terminal device corresponding to the L2 ID.

18. The method according to claim 17, characterized in that The indication information is used to indicate the service type corresponding to the QoS flow associated with the L2 ID.

19. The method according to claim 18, characterized in that The service types corresponding to the QoS flows are the same.

20. The method according to any one of claims 12 to 19, characterized in that The method further comprises: The network device receives a first transmission block from the terminal device, wherein the service type corresponding to the data in the first transmission block is the same, the service type corresponding to the data in the first transmission block is the first service type, and the data in the first transmission block The first transmission block is part or all of the first data, and the first transmission block is located on a first resource, and the first resource is used to transmit data of the first service type.

21. A communication device, characterized in that: Used to implement the method according to any one of claims 1 to 11, or used to implement the method according to any one of claims 12 to 20.

22. A communication device, characterized in that: The communication device includes a processor and a memory, the memory is used to store computer programs or instructions, and the processor is used to execute the computer program or instructions in the memory, so that the method described in any one of claims 1 to 11 is executed, or the method described in any one of claims 12 to 20 is executed.

23. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed on a computer, the computer executes the method according to any one of claims 1 to 11, or the computer executes the method according to any one of claims 12 to 20.

24. A computer program product, characterized in that The computer program product comprises means for executing the method according to any one of claims 1 to 11, or the computer program product comprises means for executing the method according to any one of claims 12 to 20.

Images