Communication method and communication apparatus

Abstract

Provided in the present application are a communication method and a communication apparatus. The communication method comprises: sending first data to a first terminal device, wherein the first data is scheduled by means of first DCI, which is scrambled by means of a first identifier, and the first data corresponds to a first HARQ process number; and sending second data to the first terminal device, wherein the second data is scheduled by means of second DCI, which is scrambled by means of a second identifier, the first data and the second data correspond to the same TB, HARQ process numbers corresponding to the second data comprise the first HARQ process number, and the first identifier is different from the second identifier, or the transmission mode corresponding to the first data is different from the transmission mode corresponding to the second data, the transmission mode comprising either of the following: a unicast mode and a multicast mode. The technical solution can improve the decoding performance of a first terminal device for decoding a TB.

Description

Communication method and communication device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on December 29, 2023, with application number 202311856671.3 and application name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The embodiments of the present application relate to the field of communications, and in particular to a communication method and a communication device. Background Art

[0003] Access network devices may scramble the same service data using different identifiers, or transmit the same service data using different transmission methods. This same service data corresponds to the same transport block (TB). However, there is currently no solution for enabling the receiver to merge the two transmissions corresponding to the same TB in this scenario. Transmission methods include multicast transmission and unicast transmission. Summary of the Invention

[0004] The present application provides a communication method and a communication device, so that when the sending end scrambles the same business data with different identifiers, or transmits the same business data through different transmission methods, the receiving end can merge the data corresponding to the same TB transmitted twice before and after, so that the receiving end can obtain better decoding effect.

[0005] On the first aspect, the present application provides a communication method, which can be executed by an access network device, or by a component configured in the access network device (such as a chip, a chip system, etc.), or it can also be a logical module or software that can realize all or part of the functions of the access network device. The present application does not limit this.

[0006] Exemplarily, the method includes: sending first data to a first terminal device, the first data is scheduled through first downlink control information (DCI), the first DCI is scrambled through a first identifier, and the first data corresponds to a first hybrid automatic repeat request (HARQ) process number; sending second data to the first terminal device, the second data is scheduled through a second DCI, the second DCI is scrambled through a second identifier, the first data and the second data correspond to the same TB, and the HARQ process number corresponding to the second data includes the first HARQ process number; wherein the first identifier and the second identifier are different, or the transmission mode corresponding to the first data and the transmission mode corresponding to the second data are different, and the transmission mode includes any one of the following: unicast mode, multicast mode.

[0007] It should be noted that for the access network device that sends data, the first identifier and the second identifier specifically refer to identifiers used to scramble the DCI. From the perspective of the access network device, the first identifier and the second identifier are also called scrambling identifiers. From the perspective of the terminal device, the first identifier and the second identifier are also called descrambling identifiers.

[0008] In this application, the same TB corresponding to the first data and the second data is also referred to as the first TB.

[0009] In this technical solution, the first data and the second data refer to data carried in the PDSCH. In this technical solution, the PDSCH carrying the first data is referred to as the first PDSCH, and the PDSCH carrying the second data is referred to as the second PDSCH. The first PDSCH is scheduled by the first DCI, and the second PDSCH is scheduled by the second DCI. It can be understood that the relationship between the first data and the second data and the first TB is: the first data and the second data may be obtained by processing the first TB, for example, in order to better adapt to air interface transmission, the first TB is encoded, and then carried in the PDSCH for transmission. In other words, the first data and the second data are the data in the PDSCH corresponding to when the first TB is placed in the PDSCH for transmission.

[0010] It can be understood that, in the present application, the first DCI scheduling the first PDSCH and the first DCI scheduling the first data can be considered to have the same meaning, and the second DCI scheduling the second PDSCH and the second DCI scheduling the second data can be considered to have the same meaning.

[0011] It can be understood that sending first data to the first terminal device, the first data is scheduled through the first DCI, and the first DCI is scrambled through the first identifier, can also be considered as the access network device sending the first data to the first terminal device based on the first identifier; similarly, sending second data to the first terminal device, the second data is scheduled through the second DCI, and the second DCI is scrambled through the second identifier, can also be considered as the access network device sending the second data through the second identifier.

[0012] It can be seen that in this technical solution, although the access network device sends the same TB to the first terminal device based on different identifiers before and after, or the access network device sends the same TB to the first terminal device before and after through different transmission methods, but since the HARQ process number corresponding to the second data transmitted in the latter time includes the first HARQ process number corresponding to the first data transmitted in the previous time, the first terminal device will think that the data transmitted twice correspond to the same TB, and can merge the data received twice before and after, thereby improving the decoding effect of the terminal device when decoding the data corresponding to the same TB.

[0013] With reference to the first aspect, in some possible implementations of the first aspect, the HARQ process number corresponding to the second data also includes a second HARQ process number.

[0014] That is, in this technical solution, there are two HARQ process numbers corresponding to the second data, one is the first HARQ process number, and the other is the second HARQ process number, and the first HARQ process number and the second HARQ process number are different.

[0015] It can be understood that under this technical solution, for the first terminal device, it can be known that the first HARQ process number and the second HARQ process number both correspond to the transmitted second data, and since the first HARQ process number is also the HARQ process number corresponding to the first data, the terminal device knows that the first data and the second data correspond to the same TB.

[0016] Optionally, if the access network device sends the second data via multicast, that is, the receiving end of the second data includes other terminal devices in addition to the first terminal device, then when the access network device indicates the HARQ process number corresponding to the second data, the HARQ process number corresponding to the second data includes not only the first HARQ process number and the second HARQ process number, but also the HARQ process number corresponding to the data last received by the other terminal device. In this way, the other terminal device knows that the received second data and the previously received data correspond to the same TB, thereby merging the received data.

[0017] In combination with the first aspect, in some possible implementations of the first aspect, the above method also includes: sending first information to the first terminal device, the first information being used to indicate that the transport block size (TBS) corresponding to the second data is the same as the TBS corresponding to the first data.

[0018] It is understandable that when the transmitter sends data corresponding to the same TB to the first terminal device via different transmission methods, the first terminal device may obtain different TBSs, and thus the first terminal device will not be able to merge the data. To this end, in this technical solution, the access network device will specifically indicate to the first terminal device that the TBS corresponding to the second data is the same as the TBS corresponding to the first data, thereby ensuring that the first terminal device can merge the data.

[0019] In combination with the first aspect, in some possible implementations of the first aspect, the first data can also be received by the second terminal device; wherein, the first terminal device and the second terminal device have different PDU sessions for the first service, and the first data and the second data are both data of the first service.

[0020] It is understandable that when the second terminal device can also receive the first data, it means that the second terminal device can also descramble the first DCI based on the first identifier, that is, the first terminal device and the second terminal device can both parse the first DCI based on the first identifier, and further receive the first data carried on the first PDSCH. Or from another perspective, although the first terminal device and the second terminal device maintain their own PDU sessions on the network side, the access network device does not send them to the first terminal device and the second terminal device respectively by unicast, but sends them to the first terminal device and the second terminal device by multicast.

[0021] Optionally, the channel status of the first terminal device is similar to the channel status of the second terminal device, and / or the first terminal device and the second terminal device are both located within the first area.

[0022] In combination with the first aspect, in some possible implementations of the first aspect, the above method also includes: sending second information to the first terminal device, the second information is used to instruct the first terminal device to deactivate the first identifier, or the second information is used to instruct the first terminal device to stop using the first identifier, or the second information is used to instruct the first terminal device to stop using the first identifier to receive data corresponding to the first service within a period of time.

[0023] Correspondingly, for the first terminal device, after receiving the second information, the first terminal device no longer de-scrambles the received DCI based on the first identifier.

[0024] In this application, deactivation may also be referred to as disabling.

[0025] Among them, the second information is used to instruct the first terminal device to stop using the first identifier to receive data corresponding to the first service within a period of time. It can be understood that the second information is used to instruct the first terminal device to temporarily stop using the first identifier to receive data corresponding to the first service.

[0026] In combination with the first aspect, in some possible implementations of the first aspect, the second data can also be received by a third terminal device; wherein the third terminal device and the second terminal device have different PDU sessions for the first service.

[0027] That is, in this technical solution, the sending end sends the same second TB to the first terminal device and the third terminal device, and the sending end sends it in a multicast manner.

[0028] Optionally, the first terminal device and the third terminal device meet at least one of the following conditions: a channel condition of the first terminal device is similar to a channel condition of the third terminal device, and the first terminal device and the third terminal device are both located within the second area.

[0029] It should be noted that in this application, TBs from different PDU sessions but with the same content that can be HARQ combined can be considered as the same TB, or TBs from the same PDU session and with the same content that can be HARQ combined can be considered as the same TB.

[0030] On the second aspect, the present application provides a communication method, which can be executed by a terminal device, or by a component configured in the terminal device (such as a chip, chip system, etc.), or it can also be a logic module or software that can realize all or part of the terminal device functions. The present application does not limit this.

[0031] Exemplarily, the method includes: receiving first data based on a first identifier and a first DCI, where the first data corresponds to a first HARQ process number; receiving second data based on a second identifier and a second DCI, where the HARQ process number corresponding to the second data includes the first HARQ process number;

[0032] The received first data and the received second data are merged; wherein the first identifier and the second identifier are different, or the transmission mode corresponding to the first data and the transmission mode corresponding to the second data are different, and the transmission mode includes any one of the following: unicast mode, multicast mode.

[0033] In this technical solution, since the HARQ process number corresponding to the second data transmitted in the latter time includes the first HARQ process number corresponding to the first data transmitted in the previous time, the first terminal device will think that the data transmitted twice correspond to the same TB, so that the data received twice can be merged, thereby improving the decoding effect of the terminal device when decoding the data corresponding to the same TB.

[0034] In combination with the second aspect, in some possible implementations of the second aspect, the HARQ process number corresponding to the second data also includes a second HARQ process number.

[0035] In combination with the second aspect, in some possible implementations of the second aspect, the method further includes: receiving first information, where the first information is used to indicate that the TBS corresponding to the second data is the same as the TBS corresponding to the first data.

[0036] In combination with the second aspect, in some possible implementations of the second aspect, the above method also includes: receiving second information, wherein the second information is used to instruct the first terminal device to deactivate the first identifier, or the second information is used to instruct the first terminal device to stop using the first identifier, or the second information is used to instruct the first terminal device to stop using the first identifier to receive data corresponding to the first service within a period of time.

[0037] On the third aspect, the present application provides a communication method, which can be executed by a terminal device that sends data, or by a component configured in the terminal (such as a chip, chip system, etc.), or it can also be a logic module or software that can realize all or part of the terminal device functions. The present application does not limit this.

[0038] Specifically, the method is applied in a slidelink scenario.

[0039] Exemplarily, the method includes: sending first data to a first terminal device, the first data is scheduled through a first SCI, and the first data corresponds to a first HARQ process number; sending second data to the first terminal device, the second data is scheduled through a second SCI, the first data and the second data correspond to the same TB, and the HARQ process number corresponding to the second data includes the first HARQ process number; wherein, the transmission mode corresponding to the first TB is different from the transmission mode corresponding to the second TB, and the transmission mode includes any one of the following: unicast mode, multicast mode.

[0040] In this technical solution, although the terminal device sending data sends the same TB to the first terminal device based on different transmission methods before and after, since the HARQ process number corresponding to the second data transmitted in the latter time includes the first HARQ process number corresponding to the first data transmitted in the previous time, the first terminal device will think that the data transmitted twice before and after correspond to the same TB, and can merge the data received twice before and after, thereby improving the decoding effect when the terminal device decodes the data corresponding to the same TB.

[0041] In combination with the third aspect, in one possible implementation, the first data can also be received by the second terminal device; wherein, the first terminal device and the second terminal device have different PDU sessions for the first service, and the first data and the second data are both data of the first service.

[0042] In combination with the third aspect, in a possible implementation, the second data can also be received by a third terminal device; wherein the third terminal device has a different PDU session of the first service.

[0043] In combination with the third aspect, in a possible implementation, the first terminal device and the second terminal device are both located within the first area.

[0044] In conjunction with the third aspect, in one possible implementation, the second data can also be received by a third terminal device; wherein the third terminal device and the second terminal device have different PDU sessions for the first service. In conjunction with the third aspect, in certain possible implementations of the third aspect, the method further includes: indicating to the first terminal device that the TBS corresponding to the second data is the same as the TBS corresponding to the first data.

[0045] Fourthly, the present application provides a communication method, which can be executed by a terminal device that receives data, or by a component configured in the terminal device (such as a chip, chip system, etc.), or it can also be a logic module or software that can realize all or part of the terminal device functions. The present application does not limit this.

[0046] Exemplarily, the method includes: based on a first SCI, receiving first data, the first data corresponding to a first HARQ process number; based on a second SCI, receiving second data, the HARQ process number corresponding to the second data includes the first HARQ process number; merging the received first data and the received second data; wherein the transmission mode corresponding to the first data and the transmission mode corresponding to the second data are different, and the transmission mode includes any one of the following: unicast mode, multicast mode.

[0047] In this technical solution, since the HARQ process number corresponding to the second data transmitted in the latter time includes the first HARQ process number corresponding to the first data transmitted in the previous time, the first terminal device will think that the data transmitted twice correspond to the same TB, so that the data received twice can be merged, thereby improving the decoding effect of the terminal device when decoding the data corresponding to the same TB.

[0048] In combination with the fourth aspect, in some possible implementations of the fourth aspect, the HARQ process number corresponding to the second data also includes a second HARQ process number.

[0049] In combination with the fourth aspect, in some possible implementations of the fourth aspect, the method further includes: receiving information indicating that the TBS corresponding to the second data is the same as the TBS corresponding to the first data.

[0050] Fifthly, the present application provides a communication method, which can be executed by an access network device that sends data, or by a component configured in the access network device (such as a chip, chip system, etc.), or it can also be a logical module or software that can realize all or part of the functions of the access network device. The present application does not limit this.

[0051] Exemplarily, the method includes: sending first target data of a first service to a first terminal device and a second terminal device, the first target data is scheduled based on a first target DCI, and the first target DCI is encrypted by a first target identifier; wherein, the first terminal device has a first PDU session for the first service, and the second terminal device has a second PDU session for the first service, and the first PDU session and the second PDU session are different sessions.

[0052] In this technical solution, the first DCI can be descrambled by the first terminal device and the second terminal device through the first identifier, but cannot be descrambled by other terminal devices. That is, in this technical solution, although the first terminal device and the second terminal device have their own PDU sessions for the first service, the transmitter sends the data of the first service to the first terminal device and the second terminal device simultaneously via multicast on the air interface side. In other words, the transmitter sends the same data of the first service to the first terminal device and the second terminal device via multicast on the air interface side.

[0053] It can be understood that compared with the sending end using unicast to all data terminal devices that need to receive the first service, this method makes the sending end no longer need to use a resource for each data terminal device that needs to receive the first service, thereby improving resource utilization and further improving system capacity (that is, the number of terminal devices accommodated).

[0054] In combination with the fifth aspect, in some possible implementations of the fifth aspect, the first terminal device and the second terminal device meet at least one of the following conditions: the channel condition of the first terminal device and the channel condition of the second terminal device are similar, the first terminal device and the second terminal device are both located within the first target area, and the first target area is smaller than the coverage range / service range of the transmitter.

[0055] In combination with the fifth aspect, in some possible implementations of the fifth aspect, the above method also includes: receiving first indication information sent by the first core network network element, the first indication information being used to indicate that the data of the first service sent to the first terminal device and the second terminal device are the same.

[0056] In combination with the fifth aspect, in some possible implementations of the fifth aspect, the above method also includes: sending second indication information to the first core network network element, the second indication information being used to indicate that the first terminal device and the second terminal device belong to the first device set.

[0057] In combination with the fifth aspect, in some possible implementations of the fifth aspect, the above method also includes: sending second target data of the first service to the first terminal device, the second target data is scheduled based on the second target DCI, the second DCI is encrypted by the second target identifier, the first target data and the second target data correspond to the same TB, and the HARQ process number corresponding to the second target data includes the first target HARQ process number corresponding to the first target data; wherein, the first target identifier and the second target identifier are different, or the transmission mode corresponding to the first target data and the transmission mode corresponding to the second target data are different, and the transmission mode includes any one of the following: unicast mode, multicast mode.

[0058] In combination with the fifth aspect, in some possible implementations of the fifth aspect, the HARQ process number corresponding to the second target data also includes a second target HARQ process number.

[0059] In combination with the fifth aspect, in some possible implementations of the fifth aspect, the above method also includes: sending fourth indication information to the first terminal device, the fourth indication information being used to indicate that the TBS corresponding to the second target data is the same as the TBS corresponding to the first target data.

[0060] In a sixth aspect, the present application provides a communication method, which can be executed by a terminal device that sends data, or by a component configured in the terminal device (such as a chip, a chip system, etc.), or it can also be a logic module or software that can realize all or part of the functions of the terminal device. The present application does not limit this.

[0061] For ease of description, in this embodiment, the terminal device that sends data is referred to as a sending terminal.

[0062] Exemplarily, the method includes: sending first target data of a first service to a first terminal device and a second terminal device; wherein, the first terminal device has a first PDU session for the first service, and the second terminal device has a second PDU session for the first service, and the first PDU session and the second PDU session are different sessions.

[0063] That is, in this technical solution, although the first terminal device and the second terminal device have their own PDU sessions for the first service, the sending terminal sends the data of the first service to the first terminal device and the second terminal device simultaneously via multicast. In other words, the sending terminal sends the same data of the first service to the first terminal device and the second terminal device via multicast.

[0064] It can be understood that compared with the sending terminal using unicast to all data terminal devices that need to receive the first service, this method makes the sending terminal no longer need to use a resource for each data terminal device that needs to receive the first service, thereby improving resource utilization and further improving system capacity (that is, the number of terminal devices accommodated).

[0065] In combination with the sixth aspect, in some possible implementations of the sixth aspect, the first terminal device and the second terminal device meet at least one of the following conditions: the channel condition of the first terminal device and the channel condition of the second terminal device are similar, the first terminal device and the second terminal device are both located within the first target area, and the first target area is smaller than the coverage range / service range of the transmitter.

[0066] In a seventh aspect, the present application provides a communications device that can implement the methods described in aspects 1 to 6 and any possible implementation of aspects 1 to 6. The device includes corresponding modules for executing the aforementioned methods. The modules included in the device can be implemented in software and / or hardware.

[0067] In an eighth aspect, the present application provides a communication device comprising a processor, wherein the processor can be used to execute a computer program in a memory to implement the method described in the first to sixth aspects and any possible implementation of the first to sixth aspects.

[0068] Optionally, the device further includes a communication interface, and the processor is coupled to the communication interface. The communication interface is configured to receive signals from other communication devices outside the device and transmit them to the processor, or to transmit signals from the processor to other communication devices outside the device. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, pin, or other type of communication interface.

[0069] Optionally, the apparatus further comprises a memory, the processor being coupled to the memory. The memory is configured to store program instructions and data. The memory is coupled to the processor, and when the processor executes instructions stored in the memory, the methods described in the above aspects can be implemented.

[0070] In a ninth aspect, the present application provides a communication device comprising a processor and a communication interface, wherein the communication interface is configured to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device, wherein the processor implements the method described in any possible implementation of aspects 1 to 6 and aspects 1 to 6 through a logic circuit or by executing code instructions. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, pin, or other type of communication interface.

[0071] Optionally, the device further includes a memory for storing instructions and data. The memory may be coupled to the processor, and when the processor executes the instructions stored in the memory, the method described in any one of the first to sixth aspects and any possible implementation of the first to sixth aspects is implemented.

[0072] In the tenth aspect, the present application provides a communication device comprising a processor and a memory, wherein the memory is used to store instructions and data. When the processor executes the instructions stored in the memory, it can implement the methods described in the first to sixth aspects and any possible implementation methods of the first to sixth aspects.

[0073] Optionally, the device further includes a communication interface, which is used for the device to communicate with other communication devices. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, pin or other types of communication interfaces.

[0074] In the eleventh aspect, the present application provides a computer-readable storage medium, which stores a computer program or instructions. When the computer program or instructions are executed, the method described in the first to sixth aspects and any possible implementation method of the first to sixth aspects is implemented.

[0075] In a twelfth aspect, the present application provides a computer program product comprising instructions, which, when executed, implement the method described in aspects 1 to 6 and any possible implementation of aspects 1 to 6.

[0076] In the thirteenth aspect, the present application provides a chip system comprising at least one processor for supporting the functions involved in the implementation of the first to sixth aspects and any possible implementation of the first to sixth aspects, such as receiving or processing the data involved in the above method.

[0077] In one possible design, the chip system further includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.

[0078] The chip system can be composed of chips, or can include chips and other discrete devices.

[0079] Among them, the effects that can be obtained from the second to eleventh aspects can be referred to the description in the first aspect and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0080] FIG1 is a schematic diagram of a communication system applicable to a communication method according to an embodiment of the present application;

[0081] FIG2 is a schematic diagram of another communication system applicable to the communication method of an embodiment of the present application;

[0082] FIG3 is a schematic diagram of an existing unicast provided by the application;

[0083] FIG4 is a schematic diagram of the process of calculating TBS of TB provided by the application;

[0084] FIG5 is a flow chart of a communication method according to an embodiment of the present application;

[0085] FIG6 is a schematic diagram of grouping provided in an embodiment of the present application;

[0086] 7 is a schematic diagram of the load-bearing device maintenance provided by an embodiment of the present application;

[0087] FIG8 is a schematic diagram of a transmission method provided in an embodiment of the present application;

[0088] FIG9 is a schematic diagram of another transmission method provided in an embodiment of the present application;

[0089] FIG10 is a flow chart of a communication method according to an embodiment of the present application;

[0090] 11 is a schematic diagram of indicating a HARQ process number to a first terminal device according to an embodiment of the present application;

[0091] FIG12 is a flow chart of a communication method according to an embodiment of the present application;

[0092] FIG13 is a schematic diagram of a communication device provided in an embodiment of the present application;

[0093] FIG14 is a schematic diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0094] The technical solution provided in this application can be applied to various communication systems, such as: fifth generation (5G) or new radio (NR) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, wireless local area network (WLAN) system, satellite communication system, future communication system, such as sixth generation (6G) mobile communication system, or a fusion system of multiple systems.

[0095] Figure 1 is a schematic diagram of the architecture of a communication system to which the communication method of the present application can be applied. As shown in Figure 1, the communication system 1000 includes a radio access network 100 and a core network 200, the Internet 300 and a server (not shown in the figure). Among them, the radio access network (RAN) 100 may include at least one RAN node (such as 110a and 110b in Figure 1, collectively referred to as 110), and may also include at least one terminal (such as 120a-120j in Figure 1). The terminal is connected to the radio access network device via wireless means, and the radio access network device is connected to the core network via wireless or wired means. The core network device and the radio access network device can be independent and different physical devices, or the functions of the core network device and the logical functions of the radio access network device can be integrated into the same physical device, or the functions of some core network devices and some radio access network devices can be integrated into one physical device. Terminals and radio access network devices can be connected to each other via wired or wireless means. FIG1 is only a schematic diagram. The communication system may further include other network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in FIG1 .

[0096] The RAN 100 may be a 3GPP-related cellular system, such as a 4G or 5G mobile communication system, or a future-oriented evolutionary system (such as a 6G mobile communication system). The RAN 100 may also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. The RAN 100 may also be a communication system that integrates two or more of the above systems.

[0097] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, constitutes part of the communication system and facilitates wireless access for terminals. Multiple RAN nodes 110 in communication system 1000 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminal 120j accessing RAN 100 via network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functionality, and network elements 120a-120j can be understood as communication devices with terminal functionality.

[0098] In one possible scenario, a RAN node may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. A RAN node may be a macro base station (such as 110a in FIG1 ), a micro base station or an indoor station (such as 110b in FIG1 ), a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, a RAN node may also be a server, a wearable device, a vehicle or an onboard device. For example, an access network device in vehicle to everything (V2X) technology may be a road side unit (RSU). All or part of the functions of the RAN node in this application may also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (such as a cloud platform). The RAN node in this application may also be a logical node, a logical module or software that can implement all or part of the RAN node functions.

[0099] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or they can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0100] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0101] A terminal is a device with wireless transceiver capabilities that can send signals to a base station or receive signals from a base station. A terminal may also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. A terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, airplane, ship, robot, robotic arm, smart home device, etc. The embodiments of this application do not limit the specific technology and specific device form adopted by the terminal.

[0102] Base stations and terminals can be fixed or mobile. They can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; on water; or on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of base stations and terminals.

[0103] The roles of base stations and terminals can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. To terminals 120j accessing the wireless access network 100 via 120i, terminal 120i is a base station. However, to base station 110a, 120i is a terminal, meaning that communication between 110a and 120i occurs via a wireless air interface protocol. Of course, communication between 110a and 120i can also occur via a base station-to-base station interface protocol. In this case, 120i is also a base station relative to 110a. Therefore, base stations and terminals can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be referred to as communication devices with base station functionality, while 120a-120j in Figure 1 can be referred to as communication devices with terminal functionality.

[0104] Communication between base stations and terminals, between base stations, and between terminals can be carried out through authorized spectrum, unauthorized spectrum, or both; communication can be carried out through spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or spectrum below 6 GHz and spectrum above 6 GHz. The embodiments of the present application do not limit the spectrum resources used for wireless communication.

[0105] The server can provide data of a certain service to the terminal device through the Internet 300, the core network 200 and the access network.

[0106] In the embodiments of the present application, the functions of the base station may also be performed by a module (such as a chip) in the base station, or by a control subsystem that includes the base station functions. The control subsystem that includes the base station functions here may be a control center in the above-mentioned application scenarios such as smart grid, industrial control, smart transportation, and smart city. The functions of the terminal may also be performed by a module (such as a chip or modem) in the terminal, or by a device that includes the terminal functions.

[0107] It is understood that the number of terminal devices shown in FIG1 is only an example. In actual practice, the number of terminal devices may be other numbers. It should be noted that the specific forms of the network devices and terminal devices are not limited in the embodiments of the present application.

[0108] FIG2 is a schematic diagram of the architecture of another communication system to which the communication method of the present application can be applied. As shown in FIG2 , the communication system 2000 includes a terminal device 210 and a terminal device 220, and the terminal device 210 and the terminal device 220 can communicate with each other through wireless communication technology. Among them, the communication link between the terminal device 210 and the terminal device 220 can be called a side link or other names; the air interface for direct communication between the terminal device 210 and the terminal device 220 is called PC5 or other names, and the embodiments of the present application do not limit this. It should be understood that FIG2 is only a simplified schematic diagram shown for ease of understanding. For example, the communication system 2000 may also include other devices, which are not drawn in FIG2 . For example, the communication system 2000 may also include access network equipment.

[0109] It should be noted that in the embodiments of the present application, the terminal device or access network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. In addition, the embodiments of the present application do not specifically limit the specific structure of the execution subject of the method provided in the embodiments of the present application, as long as it is possible to communicate according to the method provided in the embodiments of the present application by running a program that records the code of the method provided in the embodiments of the present application. For example, the execution subject of the method provided in the embodiments of the present application can be a terminal device or a network device, or a functional module in a terminal device or a network device that can call a program and execute the program.

[0110] In addition, the methods of various aspects of the present application can be implemented using programming and form a computer program accessed by a computer-readable device, carrier or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes, etc.), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memories (EPROMs), cards, sticks, or key drives, etc.). In addition, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0111] At present, the service data of users is generally sent in unicast mode. Or in other words, the service data is sent to the terminal device in unicast mode. For example, Figure 3 is a schematic diagram of a base station performing unicast for each vehicle (which can be considered as a terminal device). It can be understood that the advantage of this method is that the network side can perform special scheduling planning based on the channel conditions of a single terminal device, thereby ensuring that the scheduling for a single terminal device is always the most suitable for that single terminal device.

[0112] For example, when a base station wants to send service data to terminal device 1 and terminal device 2, when using unicast, the base station can select the precoding method and modulation and coding scheme (MCS) that are most suitable for terminal device 1 based on the channel condition of terminal device 1, to ensure that terminal device 1 can better receive the service data. Similarly, the base station can select the precoding method and modulation and coding scheme (MCS) that are most suitable for terminal device 2 based on the channel condition of terminal device 2, to ensure that terminal device 2 can better receive the service data.

[0113] However, in scenarios with very high quality of service (QoS) requirements, such as the Internet of Vehicles (IoV), if base stations send service data to all terminal devices in the entire system in unicast mode, the base stations will need to use more resources because sending service data to each terminal device requires a resource. However, the available resources of base stations are limited, which will result in an insufficient number of terminal devices that can meet QoS requirements. In other words, for services with very high quality of service (QoS) requirements, such as the IoV, the entire system has limited capacity and cannot meet the service needs of all terminal devices.

[0114] To solve the above problems, the present application provides a communication method. Taking into account that the service data sent by the base station to multiple terminal devices are sometimes the same, for example, for vehicle network services, the server will send the same perception results to different vehicles with similar locations. Therefore, on the air interface side, the base station can flexibly determine whether to use multicast transmission based on whether the service data sent to each terminal device is the same, thereby improving the system capacity of the entire system.

[0115] In addition, considering that the access network device may schedule the same service data through DCI encrypted with different identifiers, or the access network device may transmit the same service data through different transmission methods, and the same service data corresponds to the same TB, the present application also provides a communication method, so that when the access network device schedules the same service data through DCI encrypted with different identifiers, or transmits the same service data through different transmission methods, the terminal device can merge the data corresponding to the same TB transmitted twice before and after, so that the terminal device can obtain a better decoding effect. This communication method is also called a HARQ merging method.

[0116] Below, before introducing the communication method of the present application, some of the terms involved in the present application are explained to facilitate understanding by those skilled in the art.

[0117] 1) Multicast and broadcast service (MBS) technology: It can also be called multimedia broadcast multicast service (MBMS) technology, or it can also be called multicast transmission mode. It refers to the technology of sending data of a certain service to multiple terminal devices simultaneously through a base station. When using multicast technology for transmission, when multiple terminal devices subscribe to the same broadcast multicast service, multiple terminal devices can receive the broadcast multicast service sent by the base station. For example, for services similar to television broadcasting, it supports transmission in a broadcast multicast manner. From the base station side, the base station uses one air interface resource to send the same service data to multiple terminal devices. Therefore, when multiple terminal devices subscribe to the same service, this transmission method can greatly save air interface resources.

[0118] Specifically, terminal devices are configured with a group radio network temporary identifier (G-RNTI). Different terminal devices that subscribe to the same broadcast / multicast service will be configured with the same G-RNTI. The base station then uses the G-RNTI to scramble data sent from the broadcast / multicast service, while the subscribed terminal devices use the G-RNTI to descramble data, thus achieving one-to-many transmission.

[0119] 2) Internet of Vehicles (IoV) services: These allow devices to receive road condition information from a cloud platform. This information, for example, includes perception data from roadside sensors, helping devices identify the surrounding road environment and providing driver assistance. These services place high demands on transmission reliability, latency, and speed.

[0120] 3) HARQ process: HARQ uses a stop-and-wait protocol to transmit data. In the stop-and-wait protocol, after the transmitter sends a TB, it stops and waits for confirmation information. The receiver uses 1 bit of information to confirm (ACK) or negatively (NACK) the TB. However, the transmitter stops and waits for confirmation after each transmission, resulting in very low throughput. Therefore, multiple parallel stop-and-wait processes can be used: while one HARQ process is waiting for confirmation information, the transmitter can use another HARQ process to continue sending data. These HARQ processes together form a HARQ entity. Each terminal device has a HARQ entity.

[0121] Each HARQ process requires an independent HARQ buffer at the receiving end to perform soft combining on the received data.

[0122] 4) HARQ process number: also known as HARQ process ID, used to uniquely identify a HARQ process.

[0123] 5) NDI: New Data Indicator. Each HARQ process stores a single-bit NDI value, which indicates whether the scheduled data is a new transmission or a retransmission. If the NDI value for the same HARQ process changes (NDI toggled), it indicates that the current transmission is a new TB initial transmission. Otherwise (NDI not toggled), it indicates that the current transmission is a retransmission of the same TB.

[0124] 6) Determination of transport block size (TBS):

[0125] Before decoding data, the terminal device needs to determine the TBS.

[0126] For example, Figure 4 shows the key parameters for TBS calculation. As shown in Figure 4, TBS is determined by the number of layers v of the data being transmitted, the MCS value, the number of RBs, and the transmission duration. For example, an MCS table is shown in Table 1.

[0127] Table 1 MCS table

[0128] This application then provides an exemplary method for calculating TBS for the sidelink system. For the sidelink system, for the physical sidelink shared channel (PSSCH) allocated by the sidelink control information (SCI), if Table 1 is used and 0≤I MCS ≤27, the UE calculates the TBS as follows:

[0129] Step 1: The terminal device first calculates the number of REs in the time slot, that is, the parameter N RE .

[0130] First, calculate the number of REs N′ allocated to a physical resource block (PRB) for PSSCH transmission RE , the calculation formula is

[0131] in, Indicates the number of subcarriers on the PRB;

[0132] in, sl-LengthSymbols indicates the number of SL symbols in a time slot. This parameter is provided by a higher layer.

[0133] Among them, when the higher layer parameter sl-PSFCH-Period is 2 or 4, if the "PSFCH overhead indication" field in SCI format 1-A indicates "1, then otherwise When the higher layer parameter sl-PSFCH-Period is 0, When the higher layer parameter sl-PSFCH-Period is 1,

[0134] in, Indicates the overhead, given by the higher-layer parameter sl-X-Overhead.

[0135] in, Determined by Table 2 according to the higher layer parameter sl-PSSCH-DMRS-TimePattern.

[0136] Table 2

[0137] Next, the terminal device calculates the formula Determine the number of REs N allocated for PSSCH transmission RE Among them, n PRB is the number of PRBs allocated to PSSCH, Indicates the number of REs occupied by PSCCH and PSCCH DM-RS, It is represented by the number of coded modulation symbols generated by the 2nd-order SCI transmission when it is assumed that the number of idle resource elements in the resource block to which the last coded symbol of the 2nd-order SCI belongs is 0.

[0138] Step 2: According to the formula N inf o =N RE ·R·Q m ·υ calculates the intermediate variable N inf o .

[0139] If N inf o ≤3824, use step 3 as the subsequent TBS calculation step, otherwise use step 4 as the subsequent TBS calculation step.

[0140] Step 3: If N inf o ≤3824, TBS calculation steps are:

[0141] Calculate intermediate variables, Find N' by Table 3 inf o The closest TBS.

[0142] Step 4: If N inf o >3824, TBS calculation steps are:

[0143] Quantize the number of intermediate information bits

[0144] If R≤1 / 4

[0145] in

[0146] otherwise

[0147] If N' inf o >8424

[0148] in

[0149] otherwise

[0150] end if

[0151] end if

[0152] Table 3 TBS for N inf o ≤3824

[0153] In particular, when using Table 1, the terminal device does not expect to receive 28≤I MCS SCI ≤31

[0154] Specifically, for the Uu network, taking the downlink (DL) as an example, the terminal device can calculate the TBS according to the following steps.

[0155] Step 1: The terminal device first calculates the number of REs in the time slot, that is, the parameter N RE .

[0156] First, calculate the number of REs N′ allocated to a PRB for PDSCH transmissionRE , the calculation formula is

[0157] in, Indicates the number of subcarriers on the PRB; Indicates the number of symbols allocated to PDSCH in a time slot; Indicates the overhead, which is given by the higher layer parameter xOverhead in PDSCH-ServingCellConfig. If xOverhead in PDSCH-ServingCellConfig is not configured (the value range is 6, 12, 18), then Set to 0. If PDSCH is scheduled by PDCCH and CRC is scrambled by SI-RNTI, RA-RNTI, MSGB-RNTI or P-RNTI, it is assumed If the PDSCH scheduled by PDCCH is scrambled by CRC of G-RNTI or G-CS-RNTI, or if there is no PDCCH but the PDSCH is activated by PDCCH scrambled by G-CS-RNTI, Provided by the higher-layer parameter xOverhead-Multicast in pdsch-ConfigMulticast. If xOverhead-Multicast in pdsch-ConfigMulticast is not configured, then is 0; The number of REs per PRB DM-RS within the scheduling duration (including DM-RS CDM group overhead).

[0158] Next, the terminal device calculates the formula N RE =min(156,N′ RE )·n PRB , determine the number of REs N allocated for PDSCH transmission RE ; Where nPRB is the number of PRBs allocated to PSSCH.

[0159] The subsequent steps are the same as steps 2 to 4 described in the SL system and will not be repeated here.

[0160] In addition, it should be noted that if the terminal device uses Table 1 and 29≤I MCS ≤31: then assuming that the TBS is based on the DCI transmitted in the latest PDCCH of the same transmission, use 0≤I MCS ≤27. For the same transmission block, if 0≤I MCS≤ 27 PDCCHs, and if the initial PDSCH of the same transport block is semi-persistently scheduled, the TBS shall be determined based on the most recent semi-persistently scheduled PDCCH.

[0161] In addition, it should be noted that for the retransmitted TB, the TBS is usually unchanged, that is, the retransmitted TB is consistent with the TBS of the initially transmitted TB, otherwise the soft combining process cannot be performed.

[0162] The communication method provided by this application is described in detail below.

[0163] FIG5 is a flow chart of a communication method provided by an embodiment of the present application. The method 500 shown in FIG5 includes steps 501, 502 and 503.

[0164] Each step in method 500 is described in detail below.

[0165] Step 501: The access network device determines that the first terminal device and the second terminal device are capable of multicast transmission.

[0166] In this embodiment, the first terminal device and the second terminal device can establish connections with the network respectively, and the first terminal device has a first PDU session for the first service, and the second terminal device has a second PDU session for the first service. The first PDU session and the second PDU session are different sessions.

[0167] Optionally, the first terminal device having a first PDU session for the first service can also be described as the first terminal device maintaining the first PDU session for the first service, and the second terminal device having a second PDU session for the first service can also be described as the second terminal device maintaining the second PDU session for the first service. It can be understood that when the first terminal device and the second terminal device respectively establish connections with the network, and the first terminal device has the first PDU session for the first service and the second terminal device has the second PDU session for the first service, the first terminal device and the second terminal device can communicate with the network side based on unicast transmission.

[0168] It is understandable that there are scenarios where access network devices sometimes send the same business data to multiple terminal devices, or to put it another way, there are scenarios where access network devices sometimes send the same TB content to multiple terminal devices. For example, for Internet of Vehicles services, the server sends similar roadside perception results to different vehicles in similar locations. For ease of understanding, the description is given in conjunction with Figure 6. As shown in Figure 6, assuming that the perception results of each roadside device are stored in the cloud platform, vehicles 601, 602, 603, and 604 have established their own PDU sessions with the network side, and the locations of vehicles 601 to 604 are relatively close, the following situation may exist: the business data sent by the server to each vehicle 601 to 603 is the same.

[0169] It should be noted that the term "same" in this application is not strictly limited to being completely identical, and can be referred to as "same" as long as it is within a predetermined range. Therefore, "same" can also be replaced by "similar."

[0170] In view of the fact that the access network device sometimes sends the same service data to multiple terminal devices, in this embodiment, before sending service data to the first terminal device, the access network device first determines whether the first terminal device is capable of multicast transmission.

[0171] Specifically, the condition for determining whether different terminal devices perform multicast transmission includes whether the service data sent to different terminal devices are the same. Whether the service data sent to different terminal devices are the same can also be described as whether the content of the TBs sent to different terminal devices is the same.

[0172] In this application, TBs that send the same content are referred to as the same TB, or the same TB.

[0173] Applied to this embodiment, for the first terminal device and the second terminal device, if the first terminal device and the second terminal device are capable of multicast transmission, it is necessary to meet the condition that the content of the data of the first service sent to the first terminal device and the second terminal device is the same, or the content of the TB sent to the first terminal device and the second terminal device is the same.

[0174] Optionally, when determining whether the first terminal device is capable of multicast transmission with the second terminal device, the channel condition of the first terminal device and the channel condition of the second terminal device may also be considered. For example, only when the content of the TB corresponding to the PDU session of the first terminal device and the content of the TB corresponding to the PDU session of the second terminal device are the same, and the channel condition of the first terminal device is similar to the channel condition of the second terminal device, is it determined that the first terminal device is capable of multicast transmission with the second terminal device.

[0175] Optionally, the similarity between the channel state of the first terminal device and the channel state of the second terminal device can be understood as a high correlation between the channels of the two. For example, when the correlation between the first terminal device and the second terminal device is greater than 0.7, the channel states of the two are considered to be similar.

[0176] It should be noted that this embodiment does not limit how the access network device determines that the contents of the TBs sent to the first terminal device and the second terminal device are the same.

[0177] For example, in one implementation, the access network device may determine this. Optionally, when a terminal device and a second terminal device are within the same area, for the same first service, the access network device determines that the content of the TB sent to the first terminal device and the second terminal device is the same. For ease of description, in this embodiment, the same area is also referred to as the first target area. Optionally, the first target area is smaller than the coverage / service range of the access network device.

[0178] For another example, in another implementation, the server (Server or DN) may give instructions to the access network device.

[0179] In another implementation, the core network element (eg, UPF) may also indicate to the access network device.

[0180] Optionally, if the method is to indicate to the access network device, in one implementation, as shown in FIG5 , before step 501 , step 0a and step 0b may also be included.

[0181] Step 0a: The access network device sends a first request to the first core network network element, where the first request is used to request or query information of a second terminal device with the same content as the TB sent to the first terminal device.

[0182] The first request is used to request information of the second terminal device with the same content as the TB sent to the first terminal device, which can also be described as: the first request is used to request information of the second terminal device with the same service data as the first terminal device.

[0183] Step 0b: After receiving the first request, the first core network element obtains information about the second terminal device in response to the first request and feeds back first indication information to the access network device, where the first indication information is used to indicate that the data of the first service sent to the first terminal device and the second terminal device are the same. Optionally, when feeding back the first indication information to the access network device, the first core network element may also indicate session information or QoS flow information of the second terminal device to the access network device.

[0184] Exemplarily, the first core network element is an access and mobility management function (AMF). The access network device sends a first request to the AMF, and the AMF indicates to the access network device that the content of the TB sent to the first terminal device and the second terminal device is the same. Optionally, before feeding back and sending the first indication information to the access network device, the AMF may further query the UPF or SMF, and then the user plane function (UPF) or session management function (SMF) further queries the server. Accordingly, the server sends the information of the second terminal device to the access network device through the UPF or SMF.

[0185] It should be noted that this embodiment does not limit how the access network device sends the first request. For example, the first request can be sent via control plane signaling or user plane signaling. The details of control plane signaling and user plane signaling can be found in the description of related technologies and are not further described here.

[0186] Alternatively, if the indication is to the access network device, in another implementation, the core network device may proactively provide the indication. In this case, step 0a in Figure 5 may be omitted, with only step 0b remaining. Optionally, when the first core network element feeds back the first indication information to the access network device, it may also indicate to the access network device the session information or QoS flow information of the second terminal device.

[0187] Step 502: The access network device sends first target data of a first service to the first terminal device and the second terminal device. The first target data is scheduled based on a first target DCI, and the first target DCI is encrypted by a first target identifier.

[0188] It will be appreciated that the first target data in this embodiment specifically refers to data transmitted over the air interface. This data can be understood as being obtained by processing the contents of a TB to optimize air interface transmission. While essentially still transmitting the contents of a TB, it can be referred to as service data for the first service. It should be noted that this embodiment does not limit the specific method for processing the contents of a TB to obtain the first target data for air interface transmission. For example, encoding may be performed.

[0189] In this embodiment, after determining that the first terminal device and the second terminal device are capable of multicast transmission, when the access network device needs to send the first target data of the first service to the first terminal device and the second terminal device at the same time, it will indicate the PDSCH carrying the first target data to the first terminal device and the second terminal device through the first target DCI, which is also called the first target PDSCH in this embodiment; accordingly, the first terminal device is informed through the first target DCI to receive the first target data on the first target PDSCH.

[0190] Specifically, in this embodiment, when the access network device sends the first target DCI, it scrambles it through the first target identifier. Specifically, after the access network device scrambles the first target DCI using the first target identifier, the terminal devices belonging to the first device set can descramble the first target DCI, that is, the terminal devices in the first device set are configured with the first target identifier. On the contrary, for terminal devices outside the first device set that are not configured with the first target identifier, the first target DCI cannot be descrambled. That is, only the terminal devices in the first device set can obtain the PDSCH carrying the first target data based on the first target identifier, while for other terminal devices outside the terminal devices outside the first device set, because they do not obtain the first target identifier, they cannot obtain the PDSCH carrying the first target data. In this embodiment, the first device set includes the first terminal device and the second terminal device, or in other words, the first terminal device and the second terminal device belong to the first device set.

[0191] That is, in this embodiment, the first target identifier can be understood as an identifier used for scrambling similar to the group-radio network temporary identifier (G-RNTI), and the first terminal device and the second terminal device are configured with the first target identifier, so that when the access network device sends the first target data through multicast on the air interface side, the first terminal device and the second terminal device can both receive the first target data based on the first target identifier.

[0192] Optionally, the access network device can send multicast configuration information to the first terminal device and the second terminal device respectively, wherein the multicast configuration information includes, for example, a multicast bearer and a first target identifier for de-interference, so that the first terminal device and the second terminal device can parse the first target data sent by the access network device via multicast.

[0193] Optionally, when it is determined that the first terminal device and the second terminal device are capable of multicast transmission, at this time, on the access network device side, as shown in Figure 7, the access network device will maintain three bearers for the first terminal device and the second terminal device, one is the data radio bearer (DRB) of the first terminal device, one is the DRB of the second terminal device, and the other is the public radio bearer of the first terminal device and the second terminal device.

[0194] In addition, optionally, the public wireless bearer sent to the first terminal device and the second terminal device and the DRB of the first terminal device correspond to the same PDU session, and the public wireless bearer sent to the first terminal device and the second terminal device and the DRB of the second terminal device correspond to the same PDU session, and the public wireless bearer and the DRB both have complete protocol stacks, and the two correspond to different scrambling identifiers (it should be understood that for the access network device it is a scrambling identifier, and for the terminal device it is a descrambling identifier).

[0195] Optionally, in this embodiment, the access network device also uses a third target identifier to send third target data to a third terminal device. The third target data is scheduled based on a third DCI, and the third DCI is encrypted by the third target identifier. The content of the third target data is the same as the content of the first target data (that is, the third target data and the first target data correspond to the same service data), and the third target identifier is different from the first target identifier.

[0196] It should be noted that this embodiment does not limit the specific form of the third target identifier.

[0197] For example, in one implementation, the access network device determines to send third target data to a third terminal device via unicast. The third target identifier is the identifier used for scrambling in the unicast mode, such as the C-RNTI of the third terminal device. It is understandable that in this manner, the access network device can be considered to send the same service data to different terminal devices via different transmission modes.

[0198] For example, in another implementation, the access network device determines to send the third target data to the third terminal device in a multicast manner, and then the third target identifier is the identifier used for scrambling in the multicast manner.

[0199] It can be seen that in the communication method provided in this embodiment, for the service data of the first service, the access network device determines whether to transmit it in multicast or unicast mode based on whether the multicast conditions are met. It can be understood that compared to sending the service data of the first service in unicast mode to all terminal devices, the method of the present application eliminates the need for the access network device to use a resource for each terminal device, thereby improving resource utilization and further increasing system capacity (i.e., the number of terminal devices accommodated).

[0200] Optionally, the above method 500 may further include step 503: the access network device sends second indication information to the first core network network element, the second indication information being used to indicate that the first terminal device and the second terminal device belong to the first device set. Alternatively, it can be described in another way, the second indication information is used to indicate to the first core network network element that the first terminal device and the second terminal device are terminal devices that can perform multicast transmission together. Or in other words, when the access network device determines that the same service data is to be sent to the first terminal device and the second terminal device in a multicast manner, it will also indicate to the core network that the same service data is to be sent to the first terminal device and the second terminal device in a multicast manner.

[0201] Optionally, after the core network receives the second indication information, a new PDU session / QoS flow tunnel can be established between the core network and the access network device to transmit the same service data for the first terminal device and the second terminal device. Specifically, the access network device can indicate the identification of the first terminal device and the second terminal device to the first core network element of the core network, and provide downlink tunnel endpoint information. Then the first core network element replies with the uplink tunnel endpoint information on the core network side to complete the establishment of the tunnel for transmitting the service data of the first service of the first terminal device and the second terminal device. Afterwards, the core network side can send the service data to be transmitted to the access network device through this newly created tunnel, and accordingly, the access network device obtains the service data sent to the first terminal device and the second terminal device through this newly created tunnel.

[0202] Optionally, instead of creating a new tunnel between the access network device and the core network, the existing tunnel of the first terminal device and the second terminal device may be reused. Specifically, the base station may determine the reused tunnel and then indicate it to the core network device. The core network device then sends the service data to be transmitted based on the reused tunnel indicated by the access network device. Alternatively, the base station may determine the reused tunnel and then indicate it to the access network device. The core network device then sends the service data to be transmitted based on the determined reused tunnel. Accordingly, the access network device obtains the service data to be transmitted based on the reused tunnel indicated by the core network device.

[0203] It is understandable that step 503 is optional. For example, the access network device may still obtain the corresponding service data from the tunnel corresponding to the first terminal device and the corresponding service data from the tunnel corresponding to the second terminal device. However, when sending the service data to the first terminal device and the second terminal device, only the service data in one of the tunnels is sent to the first terminal device and the second terminal device in a multicast manner, and the service data in the other tunnel is discarded by default and not sent.

[0204] It is understandable that there is no absolute order between step 503 and step 502. That is, step 503 can be performed before or after step 502, or step 503 and step 502 can be performed simultaneously.

[0205] It is understandable that there are situations where terminal devices move. In this way, after the access network device sends the first target data to the first terminal device and the second terminal device via multicast, it is possible that due to the movement of the first terminal device, the access network device can no longer send service data to the first terminal device via the previous packet. For example, as shown in Figure 8, the access network device initially determines to perform multicast transmission on the vehicles in device set 1, and device set 1 includes vehicle 801, vehicle 802, and vehicle 803. Later, due to the rapid movement of vehicle 802 (vehicle 802 can be considered as the first terminal device), if vehicle 802 is placed in device set 1 and sent to vehicle 802 via multicast, the error rate of the data received by vehicle 802 is high.

[0206] Optionally, in an embodiment of the present application, when the first terminal device can no longer perform multicast transmission with the second terminal device, the access network device can send a third indication message to the first terminal device, and the third indication message is used to instruct the first terminal device to deactivate the first target identifier or stop using the first target identifier. Accordingly, the first terminal device will no longer parse the first target data of the first service through the first target identifier, thereby eliminating the need to decode the DCI through the first target identifier, thereby reducing the hardware processing complexity of the first terminal device.

[0207] In this embodiment, if the third indication information is used to instruct to stop using the first target identifier for a period of time, it can also be considered as instructing the first terminal device to temporarily deactivate the first target identifier.

[0208] The above describes a method for improving system capacity by flexibly determining whether to use multicast or unicast to send service data of the same first service to multiple terminal devices through an access network device.

[0209] Next, an embodiment of the present application provides another communication method.

[0210] Access network devices may scramble the same service data using different identifiers, or transmit the same service data using different transmission methods. This same service data corresponds to the same TB. This can also be referred to as: access network devices scramble the transmission of the same TB using different identifiers, or transmit the same TB using different transmission methods. Transmission methods include multicast transmission and unicast transmission.

[0211] Exemplarily, the description is made in conjunction with the aforementioned FIG8 . As shown in FIG8 , for vehicle 802, it is initially relatively close to the position of vehicle 801 and vehicle 803. The access network device determines that vehicle 801, vehicle 802, and vehicle 803 are a device set, and then sends the same service data to vehicle 801, vehicle 802, and vehicle 803 via multicast. As vehicle 802 moves, the access network device determines to send service data to vehicle 802 via unicast. However, for vehicle 802, when a decoding error occurs when it uses multicast to transmit data, if it uses unicast to retransmit the previous data, the data transmitted twice corresponds to the same TB. It should be noted that when the service data is sent through DCI scheduling, when the access network device uses different transmission methods, the identifier used to scramble the DCI is different.

[0212] For example, FIG. 9 is used for description. As shown in FIG. 9 , an access network device needs to provide the same service data to vehicles 901, 902, 903, 904, 905, and 906. Vehicles 901, 902, and 903 are relatively close in location, and vehicles 904 and 905 are relatively close in location. The access network device determines that vehicles 901, 902, and 903 are a device set, and vehicles 904 and 905 are a device set. The access network device then sends service data to vehicles 901, 902, and 903 using DCI scheduling scrambled with identifier 1, sends service data to vehicles 904 and 905 using DCI scheduling scrambled with identifier 2, and sends service data to vehicle 906 using DCI scheduling scrambled with identifier 3. It will be understood that identifiers 1 and 2 can be considered identifiers of corresponding multicast types used for scrambling, and identifier 3 can be considered an identifier of corresponding unicast types used for scrambling. Identifiers 1, 2, and 3 are all different. Afterwards, as each vehicle travels, the access network device determines that vehicle 905 has joined the device set consisting of the previous vehicles 901, 902, and 903, and that vehicle 906 can join the device set consisting of the previous vehicles 904 and 905, and indicates identifier 1 to vehicle 905 and identifier 2 to vehicle 906, so that vehicle 905 can receive the DCI-scheduled service data encrypted by the access network device through identifier 1, and vehicle 906 can receive the DCI-scheduled service data encrypted by the access network device through identifier 2.

[0213] As can be seen, for vehicle 905, the access network device first schedules service data scrambled with ID 2 to vehicle 905, and then schedules service data scrambled with ID 1 to vehicle 905. However, if vehicle 905 encounters a decoding error when using multicast transmission corresponding to ID 2, and then retransmits the previous data using multicast transmission corresponding to ID 1, the two transmitted data correspond to the same TB.

[0214] Similarly, it can be seen that for vehicle 906, the access network device first sends the service data to vehicle 906 through the DCI scheduling encrypted with identifier 3, and then sends the service data to vehicle 906 through the DCI scheduling encrypted with identifier 2. However, for vehicle 906, when a decoding error occurs when it uses the multicast transmission corresponding to identifier 3, if the multicast transmission corresponding to identifier 2 is used to retransmit the previous data, the data transmitted twice correspond to the same TB.

[0215] It should be noted that this embodiment does not limit how the access network device determines whether to schedule the transmission of the same TB through DCI scrambled with different identifiers, or whether to transmit the same TB through different transmission methods.

[0216] For example, for a certain terminal device, if the access network device first determines that the terminal device belongs to a certain device set, and then the network status or behavior trajectory of the terminal device changes, resulting in the terminal device no longer being able to be classified into the previous device set, data transmission can be carried out by re-dividing the groups or switching to unicast.

[0217] For example, for a certain terminal device, if the access network device first determines that the terminal device belongs to a certain device set, but finds that when the terminal device is placed in the device set, the number of HARQ-NACKs of the terminal device reaches a certain threshold, then it is determined to schedule the transmission of the same TB through DCI encrypted with different identifiers.

[0218] For another example, for a certain terminal device, if the access network device first determines that the terminal device belongs to a certain device set, but finds that when the terminal device is placed in the device set, the remaining PDB and channel quality of the terminal device are lower than a certain threshold, then it is determined to schedule the transmission of the same TB through DCI encrypted with different identifiers.

[0219] It is understandable that when an access network device transmits the same TB twice, if the access network device sends the DCI twice using different identifiers, or if the access network device sends the DCI twice using different transmission modes, the terminal device can merge the content received twice to achieve better decoding results. However, there is currently no solution proposed for how to enable the receiving end to merge the data corresponding to the same TB transmitted twice when the access network device schedules the transmission of the same transport block (TB) using DCI using different identifiers, or when the access network device may transmit the same TB using different transmission modes.

[0220] In view of this, the present application provides a method that allows the terminal device to merge the data corresponding to the same TB transmitted twice before and after when the access network device schedules the transmission of the same TB through DCI encrypted with different identifiers, or when the access network device transmits the same TB through different transmission methods, so that the terminal device can obtain better decoding effect.

[0221] Figure 10 is a flow chart of a communication method provided by one embodiment of the present application. This method may also be referred to as a HARQ combining method.

[0222] Figure 10 only describes the method from the perspective of the interaction between the terminal device and the access network device, and should not constitute any limitation on this application. For example, the terminal device in Figure 10 can be replaced by a component configured in the terminal device (such as a chip, a chip system, a processor, etc.), or a logic module or software that can implement all or part of the functions of the terminal device; the access network device can be replaced by a component configured in the access network device (such as a chip, a chip system, a processor, etc.), or a logic module or software that can implement all or part of the functions of the access network device.

[0223] The method 1000 shown in Figure 10 includes steps 1001 to 1003. Each step in the method 1000 is described in detail below.

[0224] Step 1001: The access network device sends first data to the first terminal device. The first data is scheduled through the first DCI, the first DCI is encrypted through the first identifier, and the first data corresponds to the first HARQ process number; the first terminal device receives the first data based on the first identifier and the first downlink control information DCI.

[0225] In this embodiment, for the access network device, the first identifier specifically refers to an identifier used to scramble the first DCI. Specifically, the first identifier is an identifier activated by the first terminal device, that is, the first terminal device will use the first identifier to descramble the DCI.

[0226] Specifically, the first DCI in this embodiment is a DCI that can schedule the first data to be sent to the first terminal device; or in other words, the DCI used to schedule the first data to be sent to the first terminal device is called the first DCI.

[0227] In the present application, the PDSCH carrying the first data is referred to as the first PDSCH. It can be understood that in the present application, the first DCI scheduling the first PDSCH and the first DCI scheduling the first data can be considered to have the same meaning.

[0228] Optionally, the access network device may further scramble the first data using the first identifier and scramble the second data using the second identifier.

[0229] In this embodiment, the first HARQ process number corresponding to the first data is the first HARQ process number. The first HARQ process number may also be called a first HARQ process identifier, which is used to uniquely identify a HARQ process.

[0230] Exemplarily, the access network device carries indication information for indicating the HARQ process number corresponding to the first data in the first DCI.

[0231] In this embodiment, the TB corresponding to the first data to be transmitted is referred to as the first TB. Specifically, the relationship between the first data and the first TB is that the first data may be obtained by processing the first TB, for example, by encoding the first TB to better adapt to air interface transmission, and then carried on the PDSCH for transmission. However, it is understood that both the first TB and the first data can be considered as data for a certain service.

[0232] In one implementation, the access network device sends the first data to the first terminal device via unicast transmission. In this case, the first identifier is an identifier applicable to the unicast transmission mode and used to scramble the first DCI. For example, it is the C-RNTI of the first terminal device, and the C-RNTI is only activated by the first terminal device.

[0233] In another implementation, the access network device sends the first data to the first terminal device via multicast. For example, the first terminal device and the second terminal device each maintain a different PDU session for the same service. However, when the access network device schedules the first data via the first DCI, when scrambling the first DCI, the scrambling identifier used is an identifier activated by both the first terminal device and the second terminal device; accordingly, the first terminal device and the second terminal device both descramble the first DCI via the first identifier, and then receive the first data. Optionally, the first terminal device and the second terminal device meet at least one of the following conditions: the channel condition of the first terminal device and the channel condition of the second terminal device are similar, and the first terminal device and the second terminal device are both located within the first area. Optionally, the first area is smaller than the coverage / service range of the access network device.

[0234] It can be understood that the access network device sends the first data to the first terminal device, the first data is scheduled through the first DCI, and the first DCI is encrypted through the first identifier. It can also be described as: the access network device sends the first data to the first terminal device based on the first identifier.

[0235] Step 1002: Send second data to the first terminal device, the second data is scheduled through the second DCI, the second DCI is encrypted through the second identifier, the first data and the second data correspond to the same TB, and the HARQ process number corresponding to the second data includes the first HARQ process number; the first terminal device receives the second data based on the second identifier and the second DCI.

[0236] In this embodiment, for the access network device, the second identifier specifically refers to an identifier used to scramble the second DCI. Similarly, the second identifier is an identifier activated by the first terminal device, that is, the first terminal device will use the second identifier to descramble the DCI.

[0237] Specifically, the second DCI in this embodiment is a DCI that can schedule the second data to be sent to the first terminal device; or in other words, the DCI used to schedule the second data to be sent to the first terminal device is called the second DCI.

[0238] In the present application, the PDSCH carrying the second data is referred to as a second PDSCH. It can be understood that in the present application, the second DCI scheduling the second PDSCH and the second DCI scheduling the second data can be considered to have the same meaning.

[0239] It can be understood that the access network device sends the second data to the first terminal device, the second data is scheduled through the second DCI, and the second DCI is encrypted through the second identifier. It can also be described as: the access network device sends the second data to the first terminal device based on the second identifier.

[0240] In this embodiment, the first data and the second data correspond to the same TB, but the first identifier and the second identifier are different.

[0241] It should be noted that this embodiment does not limit the specific types of the first identifier and the second identifier, as long as the first identifier and the second identifier are different.

[0242] Exemplarily, the first identifier is an identifier for scrambling the first DCI when transmitting in a multicast manner, and the second identifier is an identifier for scrambling the second DCI when transmitting in a unicast manner. For ease of description, this type of first identifier is also referred to as a multicast identifier, and this type of second identifier is also referred to as a unicast identifier. That is, in this example, when the access network device transmits data with the same content to the first terminal device twice (or is called transmitting the same TB), the former transmission mode is multicast and the latter transmission mode is unicast. For example, taking Figure 8 as an example, for vehicle 802, the data transmitted by the access network device to vehicle 802 twice corresponds to the same TB, but the former uses multicast and the latter uses unicast, and the identifier used for scrambling DCI in the multicast mode is different from the identifier used for scrambling DCI in the unicast mode.

[0243] Exemplarily, the first identifier is an identifier for scrambling the first DCI when transmitting in unicast mode, and the second identifier is an identifier for scrambling the second DCI when transmitting in multicast mode. That is to say, in this example, when the access network device transmits data with the same content to the first terminal device twice (or is called transmitting the same TB), the former transmission mode is unicast mode, and the latter transmission mode is multicast mode. For example, taking Figure 9 as an example, for vehicle 906, the data transmitted by the access network device to vehicle 906 twice correspond to the same TB, the former using unicast mode, and the latter using multicast mode, and the identifier used for scrambling DCI in multicast mode is different from the identifier used for scrambling DCI in unicast mode.

[0244] Exemplarily, the first identifier is an identifier for scrambling the first DCI when transmitting in a multicast manner, and the second identifier is also an identifier for scrambling the second DCI when transmitting in a multicast manner, but the first identifier and the second identifier are different. That is to say, in this example, when the access network device transmits data with the same content to the first terminal device twice (or is called transmitting the same TB), the former transmission mode is multicast, and the latter transmission mode is multicast. For example, taking Figure 9 as an example, for vehicle 905, the data transmitted by the access network device to vehicle 905 twice corresponds to the same TB, the former uses the multicast mode, and the latter uses the multicast mode, but the identifiers used for scrambling the DCI are different.

[0245] In order to allow the terminal device to merge the data corresponding to the same TB transmitted twice before and after so as to obtain a better decoding effect when the access network device schedules the transmission of the same TB through DCI scrambled by different identifiers, or when the access network device transmits the same TB through different transmission methods, in this embodiment, the access network device indicates the HARQ process number corresponding to the second data to the first terminal device, and the indicated HARQ process number corresponding to the second TB includes the first HARQ process number, that is, the indicated HARQ process number corresponding to the second data includes the HARQ process number corresponding to the first data.

[0246] Exemplarily, the access network device carries indication information for indicating the HARQ process number corresponding to the second data in the second DCI.

[0247] It should be noted that this embodiment does not limit how the access network device specifically indicates that the HARQ process number corresponding to the second data includes the second HARQ process number.

[0248] Optionally, in the first implementation mode, when the access network device indicates the HARQ process number corresponding to the second data to the first terminal device, the HARQ process number corresponding to the second data only includes the first HARQ process number. It can be understood that for the first terminal device, after receiving the second data, since one HARQ process is associated with one TB, and the HAQR process number corresponding to the second data received by the first terminal device is the same as the HARQ process number corresponding to the first data (the access network device specifically indicates that the HAQR process number corresponding to the second data is the same as the HARQ process number corresponding to the first data), the first terminal device will believe that the received first data and second data correspond to the same TB, and then merge the first data and the second data to improve decoding performance.

[0249] Optionally, in a second implementation, when the access network device indicates the HARQ process number corresponding to the second data to the first terminal device, as shown in FIG11 , in addition to indicating the new HARQ process number corresponding to the second data to the first terminal device, the access network device also indicates a first HARQ process number to the first terminal device; in this way, the first terminal device can know that the first HARQ process number and the second HARQ process number both correspond to the transmitted second data, and since the first HARQ process number is also the HARQ process number corresponding to the first data, the terminal device knows that the first data and the second data correspond to the same TB, and then merges the first data with the second data to improve decoding performance. Exemplarily, the first terminal device stores the first data received based on the first identifier and the first DCI in a first buffer, and the second buffer is used to store the second data received based on the second identifier and the second DCI, and then merges the received second data with the data in the first buffer; or merges the first data with the data in the second buffer to complete the decoding of the TB.

[0250] It can be understood that the first implementation method is more suitable for the scenario where the transmission method corresponding to the second data is unicast. The reason is as follows: when indicating the HARQ process identifier corresponding to the second number, there is only one HARQ process identifier corresponding to the second data and it is the HARQ process identifier corresponding to the first data. Therefore, only the first terminal device will think that the second data and the first data correspond to the same TB, while for other terminal devices, it will be considered that the second data corresponds to a new TB, and therefore will not be merged.

[0251] It is understandable that the second implementation is applicable to both scenarios where the subsequent transmission is unicast and scenarios where the subsequent transmission is multicast. For example, when the subsequent transmission is multicast, the HARQ process number of the previously transmitted data is additionally indicated to each terminal device that needs to perform HARQ combining during the subsequent transmission, so that the terminal device can perform the combining.

[0252] Step 1003: The terminal device merges the received first data and the received second data.

[0253] That is, the terminal device merges the first data received based on the first identifier and the first DCI and the second data received based on the second identifier and the second DCI.

[0254] It can be understood that in this embodiment, since in step 1002, when the access network device sends the second data to the terminal device, the HARQ process number corresponding to the second data is indicated to the terminal device through the first information, and the HARQ process number corresponding to the second data includes the first HARQ process number, therefore, for the terminal device, it can be considered that the received second data and the received data correspond to the same TB, therefore, the received first data and the received second data can be merged, thereby improving the decoding performance.

[0255] Optionally, the above method 1000 also includes: sending first information to the first terminal device, the first information is used to indicate that the TBS corresponding to the second data is the same as the TBS corresponding to the first data. It can be understood that the first terminal device can only perform HARQ merging on the same TB when the TBSs of the two TBs transmitted are the same. However, in an embodiment of the present application, when the access network device sends the same TB to the first terminal device through different transmission modes, the first terminal device may obtain different TBSs. For example, from a multicast mode to a unicast mode, the MCS of the two transmissions may change, and the transmission efficiency will become higher, so that the first terminal device will not merge. For this reason, in this technical solution, the access network device will specifically indicate to the first terminal device that the TBS corresponding to the second data is the same as the TBS corresponding to the first data, thereby ensuring that the first terminal device can merge. Specifically, for example, the first information indicates that the first terminal device is determined according to the TBS corresponding to the data scheduled by the first DCI or the second DCI; for example, the first information indicates a specific TBS value or an index corresponding to the TBS value.

[0256] Optionally, in an embodiment of the present application, after the access network device sends the first data to the first terminal device, if it is determined that the first terminal device can no longer de-scramble the received DCI based on the first identifier, the access network device can send second information to the first terminal device, and the second information is used to instruct the first terminal device to deactivate the first identifier, or the second information is used to instruct the first terminal device to stop using the first identifier.

[0257] Correspondingly, for the first terminal device, after receiving the second information, the received DCI is no longer de-scrambled based on the first identifier, and thus the first data scheduled based on the first DCI is no longer received.

[0258] It should be noted that Figure 10 illustrates the HARQ combining method provided by this application, using an access network device as the data transmitter and a terminal device as the data receiver. However, the HARQ combining concept can also be extended to sidelink systems, namely, Slindelink systems, where both the terminal device and the terminal device are the data transmitter and receiver. The following describes the HARQ combining method when extended to sidelink systems, in conjunction with Figure 12.

[0259] For ease of description, in this embodiment, the terminal device that sends data is referred to as a fourth terminal device.

[0260] As shown in Figure 12, the method includes steps 1201 to 1203. Each step is described in detail below.

[0261] Step 1201: The fourth terminal device sends first data to the first terminal device. The first data is scheduled through the first SCI, and the first data corresponds to the first HARQ process number.

[0262] In this embodiment, the first data refers to data scheduled by the first SCI, that is, the first SCI is an SCI used to schedule the first data to be sent to the first terminal device.

[0263] It is understood that in the sidelink system, the PSSCH carries the first data. In this embodiment, the PSSCH carrying the first data is referred to as the first PSSCH. It is understood that in the embodiment of Figure 12, the first SCI scheduling the first PSSCH and the first SCI scheduling the first data can be considered to have the same meaning.

[0264] In this embodiment, the HARQ process number corresponding to the first data is also referred to as the first HARQ process number. Exemplarily, the fourth terminal device carries indication information for indicating the HARQ process number corresponding to the first data in the first SCI.

[0265] Likewise, the TB corresponding to the first data can be considered as the first TB.

[0266] In step 1202, the fourth terminal device sends second data to the first terminal device. The second data is scheduled through the second SCI. The first data and the second data correspond to the same TB. The HARQ process number corresponding to the second data includes the first HARQ process number. The transmission methods of the first data and the second data are different.

[0267] In this embodiment, the second data refers to data scheduled by the second SCI. That is, the second SCI is the SCI used to schedule the second data to be sent to the first terminal device. How the first terminal device receives the second data can be analogous to how the first terminal device receives the first data in step 1101, and will not be further described here.

[0268] In this embodiment, the first data and the second data correspond to the same TB.

[0269] In order to enable the first terminal device to know that the received first data and second data correspond to the transmission of the same TB, in this embodiment, when the fourth terminal device indicates the HARQ process number corresponding to the second data to the first terminal device, the indicated HARQ process number corresponding to the second data includes the first HARQ process number, that is, the indicated HARQ process number corresponding to the second data includes the HARQ process number corresponding to the first data; in this way, the first terminal device will know that the received first data and second data correspond to the same TB, and then merge the received first data and second data.

[0270] Exemplarily, the fourth terminal device carries indication information for indicating the HARQ process number corresponding to the second data in the second DCI.

[0271] The transmission method may refer to the description in the aforementioned embodiment and will not be repeated here.

[0272] Step 1203: The terminal device merges the received first data and the received second data.

[0273] That is, the terminal device combines the first data received based on the first SCI and the second data received based on the second SCI.

[0274] Optionally: the fourth terminal device sends indication information to the first terminal device for indicating that the TBS corresponding to the second data is the same as the TBS corresponding to the first data. It can be understood that the first terminal device can perform HARQ merging on the same TB only when the TBSs of the two transmitted TBs are the same. For ease of description, the indication information used to indicate that the TBS corresponding to the second data is the same as the TBS corresponding to the first data in the embodiment of Figure 12 is referred to as indication information 1. Specifically, for example, indication information 1 indicates that the first terminal device determines the TBS corresponding to the data scheduled according to the first SCI or the second SCI; for example, when the MCS index indicated in the SCI is the first value, such as I MCS =30, indicating that the first terminal device determines the TBS corresponding to the PSSCH data scheduled by the SCI corresponding to other valid MCS indexes, for example, the indication information 1 indicates a specific TBS value, or the index corresponding to the TBS value.

[0275] In summary, it can be seen that both the first DCI and the first SCI can be considered as control information 1, and both the second DCI and the second SCI can be considered as control information 2. Accordingly, the data scheduled by the first DCI and the first SCI can be considered as data 1, and the data scheduled by the second DCI and the second SCI can be considered as data 2. In this way, the HARQ merging method provided in the present application includes: the transmitting end sends data 1 to the first terminal device, and data 1 is scheduled by control information 1. Data 1 corresponds to a HARQ process number, for example, the HARQ process number is called HARQ process number 1; the transmitting end sends data 2 to the first terminal device, and data 2 is scheduled by two control information 2. Data 1 and data 2 correspond to the same TB, and the HARQ process number corresponding to data 2 includes HARQ process number 1; wherein, the transmitting end uses different transmission modes when sending data 1 and data 2, and the transmission mode includes any one of the following: unicast mode, multicast mode; or, when the transmitting end is an access network device, the identifier of the scrambling control information 1 and the identifier of the scrambling control information 2 used are different.

[0276] The communication method of the embodiment of the present application is described in detail above in conjunction with Figures 5 to 12. The communication device provided in the present application will be described in detail below in conjunction with Figures 13 and 14.

[0277] FIG13 is a schematic structural diagram of a communication device provided by an embodiment of the present application. Specifically, as shown in FIG13 , the device 1300 includes: a receiving module 1301 , a sending module 1302 , and a processing module 1303 .

[0278] In a first embodiment, the method is applied to an access network device.

[0279] Specifically, in the first embodiment, the sending module 1302 is used to send first data to the first terminal device, the first data is scheduled through the first DCI, the first DCI is scrambled through the first identifier, and the first data corresponds to the first HARQ process number; the sending module 1302 is also used to send second data to the first terminal device, the second data is scheduled through the second DCI, the second DCI is scrambled through the second identifier, the first data and the second data correspond to the same TB, and the HARQ process number corresponding to the second data includes the first HARQ process number; wherein the first identifier and the second identifier are different, or the transmission mode corresponding to the first data and the transmission mode corresponding to the second data are different, and the transmission mode includes any one of the following: unicast mode, multicast mode.

[0280] In a possible implementation manner, the HARQ process number corresponding to the second data also includes a second HARQ process number.

[0281] In a possible implementation, the sending module 1302 is further used to: send first information to the first terminal device, where the first information is used to indicate that the TBS corresponding to the second data is the same as the TBS corresponding to the first data.

[0282] In a possible implementation, the first data can also be received by the second terminal device; wherein the first terminal device and the second terminal device have different PDU sessions of the first service, and the first data and the second data are both data of the first service.

[0283] In a possible implementation, a channel condition of the first terminal device is similar to a channel condition of the second terminal device, and / or the first terminal device and the second terminal device are both located within the first area.

[0284] In a possible implementation, the sending module 1302 is further used to: send second information to the first terminal device, where the second information is used to instruct the first terminal device to deactivate the first identifier, or the second information is used to instruct the first terminal device to stop using the first identifier.

[0285] In a possible implementation, the second data can also be received by a third terminal device; wherein the third terminal device has a different PDU session of the first service.

[0286] In a possible implementation, a channel condition of the first terminal device is similar to a channel condition of the third terminal device, and / or the first terminal device and the third terminal device are both located within the second area.

[0287] In a second embodiment, the method is applied to a terminal device that receives data.

[0288] Specifically, in the second embodiment, the receiving module 1301 is used to receive first data based on a first identifier and a first DCI, and the first data corresponds to a first HARQ process number; the receiving module 1301 is also used to receive second data based on a second identifier and a second DCI, and the HARQ process number corresponding to the second data includes the first HARQ process number; the processing module 1303 is used to merge the received first data and the received second data; wherein, the first identifier and the second identifier are different, or the transmission mode corresponding to the first data and the transmission mode corresponding to the second data are different, and the transmission mode includes any one of the following: unicast mode, multicast mode.

[0289] In a possible implementation manner, the HARQ process number corresponding to the second data also includes a second HARQ process number.

[0290] In a possible implementation, the receiving module 1301 is further configured to: receive first information, where the first information is used to indicate that the TBS corresponding to the second data is the same as the TBS corresponding to the first data.

[0291] In a possible implementation, the receiving module 1301 is further used to: receive second information, where the second information is used to instruct the first terminal device to deactivate the first identifier, or the second information is used to instruct the first terminal device to stop using the first identifier.

[0292] Figure 14 is a schematic structural diagram of a communication device provided in another embodiment of the present application. The device shown in Figure 14 can be used to execute the method described in any of the above embodiments.

[0293] As shown in Figure 14, the apparatus 1400 of this embodiment includes a memory 1401 and a processor 1402. In one implementation, the apparatus 1400 further includes a communication interface 1403 and a bus 1404. The memory 1401, the processor 1402, and the communication interface 1403 are communicatively connected to each other via the bus 1404.

[0294] The memory 1401 may be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1401 may store a program. When the program stored in the memory 1401 is executed by the processor 1402, the processor 1402 is configured to perform the steps of the method shown in Figures 5 to 11.

[0295] The processor 1402 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits to execute relevant programs to implement the methods shown in Figures 5 to 11 of the present application.

[0296] The processor 1402 may also be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the method of Figures 5 to 11 of the embodiment of the present application may be completed by an integrated logic circuit of hardware in the processor 1402 or by instructions in the form of software.

[0297] The processor 1402 may also 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 device, a discrete gate or transistor logic device, or a discrete hardware component. The processor 1402 may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or a conventional processor.

[0298] 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 decoding processor, or can be executed 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 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 1401, and the processor 1402 reads the information in the memory 1401 and, in combination with its hardware, completes the functions required to be performed by the units included in the device of the present application. For example, the various steps / functions of the embodiments shown in Figures 5 to 11 can be executed.

[0299] The communication interface 1403 may use, but is not limited to, a transceiver or other transceiver device to implement communication between the apparatus 1400 and other devices or a communication network.

[0300] The bus 1404 may include a path for transmitting information between various components of the device 1400 (eg, the memory 1401 , the processor 1402 , and the communication interface 1403 ).

[0301] It should be understood that the apparatus 1400 shown in the embodiment of the present application can be an electronic device, or a chip configured in an electronic device. The apparatus 1400 can be deployed in a terminal device, or can also be deployed in a network device.

[0302] The present application also provides a computer program product, which includes: a computer program (also referred to as code, or instructions). When the computer program is run, it can implement the steps executed by the terminal, verification network element or storage network element in any one of the embodiments shown in Figures 5 to 11.

[0303] The present application also provides a computer-readable storage medium storing a computer program (also referred to as code or instructions). When the computer program is executed, the steps performed by the terminal, verification network element, or storage network element in any of the embodiments shown in Figures 5 to 11 can be implemented.

[0304] An embodiment of the present application provides a communication system, which includes the first terminal device and the access network device as described above.

[0305] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, the above embodiments 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 or computer programs. When the computer instructions or computer program are loaded or 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., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be an available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state drive.

[0306] It should be understood that the term "and / or" as used herein simply describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. A and B can be singular or plural. Furthermore, the character " / " as used herein generally indicates an "or" relationship between the associated objects, but it may also indicate an "and / or" relationship. For specific understanding, please refer to the context.

[0307] In this application, "at least one" means one or more, and "plurality" means two or more. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.

[0308] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute a limitation on the implementation process of the embodiments of the present application.

[0309] 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.

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

[0311] 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.

[0312] 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.

[0313] 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.

[0314] 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 to the prior art, 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 several instructions for enabling a computer device (which can be a personal computer, server, or 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, a random access memory, a magnetic disk, or an optical disk.

Claims

1. A communication method, characterized in that, Including: Sending first data to a first terminal device, where the first data is scheduled by first downlink control information (DCI), the first DCI is scrambled by a first identifier, and the first data corresponds to a first hybrid automatic repeat request (HARQ) process number; Sending second data to the first terminal device, where the second data is scheduled by second DCI, the second DCI is scrambled by a second identifier, the first data and the second data correspond to the same transport block (TB), and the HARQ process number corresponding to the second data includes the first HARQ process number; Wherein, the first identifier and the second identifier are different, or the transmission mode corresponding to the first data and the transmission mode corresponding to the second data are different, and the transmission mode includes any one of the following: unicast mode, multicast mode.

2. The method according to claim 1, wherein The HARQ process number corresponding to the second data further includes a second HARQ process number.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Sending first information to the first terminal device, where the first information is used to indicate that the transport block size (TBS) corresponding to the second data is the same as the TBS corresponding to the first data.

4. The method according to any one of claims 1 to 3, characterized in that, The first data can also be received by a second terminal device; Wherein, the first terminal device and the second terminal device have different PDU sessions for a first service, and the first data and the second data are both data of the first service.

5. The method according to claim 4, wherein The channel condition of the first terminal device and the channel condition of the second terminal device are similar, and / or the first terminal device and the second terminal device are both within a first area range.

6. The method according to any one of claims 1 to 5, characterized in that The method further includes: Sending second information to the first terminal device, where the second information is used to indicate the first terminal device to deactivate the first identifier, or the second information is used to indicate the first terminal device to stop using the first identifier.

7. The method according to claim 6, wherein The second data can also be received by a third terminal device; Wherein, the third terminal device and the second terminal device have different PDU sessions for a first service.

8. The method according to claim 7, characterized in that, The channel condition of the first terminal device and the channel condition of the third terminal device are similar, and / or the first terminal device and the third terminal device are both within a second area range.

9. A communication method, characterized in that, Including: Receiving first data based on a first identifier and first downlink control information (DCI), where the first data corresponds to a first hybrid automatic repeat request (HARQ) process number; Receiving second data based on a second identifier and second DCI, where the HARQ process number corresponding to the second data includes the first HARQ process number; Combining the received first data and the received second data; Wherein, the first identifier and the second identifier are different, or the transmission mode corresponding to the first data and the transmission mode corresponding to the second data are different, and the transmission mode includes any one of the following: unicast mode, multicast mode.

10. The method according to claim 9, wherein The HARQ process number corresponding to the second data further includes a second HARQ process number.

11. The method according to claim 9 or 10, characterized in that, The method further includes: Receiving first information, where the first information is used to indicate that the transport block size (TBS) corresponding to the second data is the same as the TBS corresponding to the first data.

12. The method according to claim 11, wherein The method further includes: Receive second information, where the second information is used to instruct the first terminal device to deactivate the first identifier, or the second information is used to instruct the first terminal device to stop using the first identifier.

13. A communication device, characterized in that, Comprising: A sending module, configured to send first data to a first terminal device, where the first data is scheduled by a first downlink control information DCI, the first DCI is scrambled by a first identifier, and the first data corresponds to a first hybrid automatic repeat request HARQ process number; A sending module, configured to send second data to the first terminal device, where the second data is scheduled by a second DCI, the second DCI is scrambled by a second identifier, the first data and the second data correspond to the same transport block TB, and the HARQ process number corresponding to the second data includes the first HARQ process number; Wherein, the first identifier is different from the second identifier, or the transmission mode corresponding to the first data is different from the transmission mode corresponding to the second data, and the transmission mode includes any one of the following: unicast mode, multicast mode.

14. The device according to claim 13, wherein The HARQ process number corresponding to the second data further includes a second HARQ process number.

15. The device according to claim 13 or 14, characterized in that, The sending module is further configured to: Send first information to the first terminal device, where the first information is used to instruct that the transport block size TBS corresponding to the second data is the same as the TBS corresponding to the first data.

16. The device according to any one of claims 13 to 15, characterized in that, The first data can also be received by a second terminal device; Wherein, the first terminal device and the second terminal device have different PDU sessions for a first service, and the first data and the second data are both data of the first service.

17. The device according to claim 16, characterized in that, The channel conditions of the first terminal device and the channel conditions of the second terminal device are similar, and / or the first terminal device and the second terminal device are both within a first area range.

18. The device according to claim 16 or 17, characterized in that, The sending module is further configured to: Send second information to the first terminal device, where the second information is used to instruct the first terminal device to deactivate the first identifier, or the second information is used to instruct the first terminal device to stop using the first identifier.

19. The device according to claim 18, characterized in that, The second data can also be received by a third terminal device; Wherein, the third terminal device has different PDU sessions for a first service.

20. The device according to claim 19, wherein The channel conditions of the first terminal device and the channel conditions of the third terminal device are similar, and / or the first terminal device and the third terminal device are both within a second area range.

21. A communication device, characterized in that, Comprising: A receiving module, configured to receive first data based on a first identifier and a first downlink control information DCI, where the first data corresponds to a first hybrid automatic repeat request HARQ process number; The receiving module is further configured to receive second data based on a second identifier and a second DCI, where the HARQ process number corresponding to the second data includes the first HARQ process number; A processing module, configured to combine the received first data and the received second data; Wherein, the first identifier is different from the second identifier, or the transmission mode corresponding to the first data is different from the transmission mode corresponding to the second data, and the transmission mode includes any one of the following: unicast mode, multicast mode.

22. The device according to claim 21, wherein, The HARQ process number corresponding to the second data further includes a second HARQ process number.

23. The device according to claim 21 or 22, characterized in that, The receiving module is further configured to: receive first information, where the first information is used to indicate that the transport block size (TBS) corresponding to the second data is the same as the TBS corresponding to the first data.

24. The device according to claim 23, wherein The receiving module is further configured to: receive second information, where the second information is used to indicate that the first terminal device deactivates the first identifier, or the second information is used to indicate that the first terminal device stops using the first identifier.

25. A communication device, characterized in that, Comprising: a processor, wherein the processor is configured to cause the communication device to implement the method according to any one of claims 1 to 8 by executing a computer program and / or by means of logic circuits.

26. A communication device, characterized in that, Comprising: a processor, wherein the processor is configured to cause the communication device to implement the method according to any one of claims 9 to 12 by executing a computer program and / or by means of logic circuits.

27. A computer-readable medium, characterized in that, The computer-readable medium stores program code for execution by a computer, and the program code includes instructions for executing the method according to any one of claims 1 to 8 or 9 to 12.

28. A computer program product, characterized in that, The computer program product includes computer program code, and when the computer program code runs on a computer, it causes the computer to implement the method according to any one of claims 1 to 8 or 9 to 12.

29. A chip, characterized in that, Comprising at least one processor and a communication interface, the communication interface and the at least one processor are interconnected by a line, and the at least one processor is configured to run a computer program or instructions to perform the communication method according to any one of claims 1 to 8 or 9 to 12.

Images