Communication method, apparatus, device, system, storage medium and program product

Abstract

Embodiments of the present application provide a kind of communication method, device, equipment, system, storage medium and program product, relate to wireless communication field, the method is executed by terminal device, comprising: receiving the configuration information sent by network device, configuration information is used to configure terminal equipment to repeat transmission physical uplink shared channel (PUSCH);According to configuration information, multiple PUSCH are sent to network device;Wherein, multiple PUSCH are repeated transmission PUSCH, multiple PUSCH include at least one PUSCH group, the same redundancy version is used in the PUSCH group in PUSCH;PUSCH group in PUSCH is superimposed with N orthogonal cover code (OCC) sequence, N is 0 or 1.The scheme of the present application embodiment can guarantee that multiple terminal equipment is mutually orthogonal between the uplink data based on PUSCH transmission, to avoid the mutual interference between different terminal equipment, improve system capacity.

Description

Technical Field

[0001] This application relates to the field of wireless communication, and more particularly to a communication method, apparatus, device, system, storage medium, and program product. Background Technology

[0002] A non-terrestrial network (NTN) is a network that provides wireless resources via satellite or drones and offers communication services to ground-based terminal devices. By integrating NTN networks with terrestrial networks, extensive coverage can be provided.

[0003] In NTN networks, due to the limitations of ground-based terminal equipment and the long distance between the terminal equipment and the satellite, the uplink communication link coverage is poor. Therefore, the terminal equipment can improve the reliability of uplink transmission and increase the success rate of uplink data transmission by repeating the transmission through the physical uplink shared channel (PUSCH).

[0004] In NTN networks, due to the large number of terminal devices that a single cell needs to serve, there may be situations where multiple terminal devices need to perform PUSCH retransmission simultaneously. However, limited frequency domain resources restrict the number of terminal devices in a cell that can perform PUSCH retransmission simultaneously, resulting in low system capacity. Summary of the Invention

[0005] This application provides a communication method, apparatus, device, system, storage medium, and program product to improve system capacity.

[0006] In a first aspect, embodiments of this application provide a communication method executed by a terminal device, the method comprising:

[0007] Receive configuration information sent by network devices. The configuration information is used to configure the terminal devices to repeatedly transmit the Physical Uplink Shared Channel (PUSCH).

[0008] Based on the configuration information, send multiple PUSCHs to the network device;

[0009] Among them, multiple PUSCHs are repeatedly transmitted PUSCHs, and multiple PUSCHs include at least one PUSCH group. The PUSCHs in the PUSCH group use the same redundant version. N orthogonal overlay code (OCC) sequences are superimposed on the PUSCHs in the PUSCH group, where N is 0 or 1.

[0010] In this embodiment, the terminal device receives configuration information and sends multiple PUSCHs to the network device according to the configuration information. These multiple PUSCHs are repeatedly transmitted PUSCHs, comprising at least one PUSCH group. The PUSCHs in the PUSCH group use the same redundant version, ensuring that the data transmitted on the PUSCHs within the same PUSCH group is identical. N OCC sequences, where N is 0 or 1, are superimposed on the PUSCHs in the PUSCH group. This embodiment superimposes OCC sequences on PUSCH groups. Since the data transmitted on the PUSCHs within the same PUSCH group is identical, when multiple terminal devices repeatedly transmit PUSCHs on the same time-frequency domain resources, it ensures that the uplink data transmitted by the multiple terminal devices based on PUSCHs is orthogonal, thus avoiding mutual interference between different terminal devices. This achieves code division multiplexing between different terminal devices, improving system capacity while ensuring uplink coverage and reliability.

[0011] In some embodiments, the configuration information includes at least one of the following:

[0012] PUSCH configuration information, used to configure the PUSCH for repeated transmission;

[0013] PUSCH group configuration information, used to configure at least one PUSCH group;

[0014] Frequency hopping information;

[0015] OCC configuration information is used to configure the OCC sequence superimposed on the PUSCH in the PUSCH group;

[0016] Uplink control information (UCI) indication information is used to indicate whether UCI multiplexing is allowed on repeatedly transmitted PUSCH.

[0017] In this embodiment of the application, the terminal device receives configuration information, thereby enabling it to send multiple PUSCHs to the network device according to at least one of the following information in the configuration information: PUSCH configuration information, PUSCH group configuration information, frequency hopping information, OCC configuration information, and UCI indication information.

[0018] In some embodiments, PUSCH configuration information includes:

[0019] The number of times the terminal device repeatedly transmits the PUSCH;

[0020] And / or,

[0021] The terminal device repeatedly transmits PUSCH resources.

[0022] In this embodiment of the application, after receiving the configuration information, the terminal device can know the number of times the terminal device repeatedly transmits PUSCH and / or the resources of the terminal device repeatedly transmitting PUSCH, and then send multiple PUSCH to the network device according to the number of times the terminal device repeatedly transmits PUSCH and / or the resources of the terminal device repeatedly transmitting PUSCH.

[0023] In some embodiments, the PUSCH group configuration information includes at least one of the following:

[0024] The number of at least one PUSCH group;

[0025] The number of PUSCHs in the PUSCH group;

[0026] The transmission order of the PUSCH group;

[0027] Redundancy version information for PUSCH groups, used to indicate the redundant versions used by PUSCHs in the PUSCH group.

[0028] In this embodiment of the application, after receiving the configuration information, the terminal device can obtain the PUSCH group configuration information, and then send multiple PUSCHs to the network device according to the PUSCH group configuration information.

[0029] In some embodiments, the frequency hopping information includes at least one of the following:

[0030] The first indication information is used to indicate whether the terminal device repeatedly transmits PUSCH based on frequency hopping.

[0031] Frequency hopping type;

[0032] Frequency hopping parameters are used to indicate the frequency domain resources of the PUSCH group.

[0033] In this embodiment, after receiving the configuration information, the terminal device can determine whether to repeatedly transmit multiple PUSCHs using frequency hopping based on the frequency hopping information in the configuration information. If multiple PUSCHs are repeatedly transmitted using frequency hopping, by configuring an appropriate frequency hopping type, such as configuring at least one PUSCH group with superimposed OCC sequences as inter-PUSCH group frequency hopping, frequency selective gain and randomized interference are obtained, while ensuring that a PUSCH group transmits the exact same data on the same frequency domain resources. This ensures the orthogonality between the uplink data transmitted by multiple terminal devices multiplexed by OCC sequences on the same time-frequency resources, thereby improving system capacity while ensuring system decoding performance.

[0034] In some embodiments, frequency hopping types include at least one of the following:

[0035] Frequency hopping type within a time slot;

[0036] Inter-slot frequency hopping type;

[0037] PUSCH inter-group frequency hopping type.

[0038] In some embodiments, the OCC configuration information includes at least one of the following:

[0039] The second indication information is used to indicate whether an OCC sequence is superimposed on the PUSCH in the PUSCH group;

[0040] Length of the OCC sequence;

[0041] Index of OCC sequence;

[0042] How OCC sequences are generated;

[0043] OCC sequence set.

[0044] In this embodiment, the terminal device can determine whether an OCC sequence needs to be superimposed on the PUSCH in the PUSCH group and determine the specific OCC sequence based on the relevant information in the OCC configuration information. This helps to ensure the orthogonality between uplink data transmitted by multiple terminal devices that reuse OCC sequences on the same time-frequency resources.

[0045] In some embodiments, an OCC sequence is superimposed on the PUSCH in the PUSCH group, and the PUSCH group satisfies:

[0046] The number of PUSCHs in a PUSCH group is equal to the length of the OCC sequence superimposed on the PUSCHs in the PUSCH group.

[0047] In this embodiment, the number of PUSCHs in a PUSCH group is equal to the length of the OCC sequence superimposed on the PUSCHs in the PUSCH group, and the data transmitted on the PUSCHs in the same PUSCH group is exactly the same. When multiple terminal devices repeatedly transmit PUSCHs on the same time-frequency domain resources, it can ensure that the uplink data transmitted by multiple terminal devices based on PUSCHs are mutually orthogonal, thereby avoiding mutual interference between different terminal devices and realizing code division multiplexing between different terminal devices. While ensuring the uplink coverage and reliability of the system, the system capacity is improved.

[0048] In some embodiments, the number of PUSCHs in different PUSCH groups is the same; or, the number of PUSCHs in different PUSCH groups is different.

[0049] In this embodiment, the number of PUSCHs in different PUSCH groups is the same, resulting in lower processing complexity for both network devices and terminal devices, thus improving processing efficiency. The different number of PUSCHs in different PUSCH groups allows for the rational allocation of resources based on the transmission needs of different terminal devices, enabling flexible configuration of multiple terminal devices for reuse and effectively improving system capacity and throughput.

[0050] In some embodiments, an OCC sequence is superimposed on the PUSCH in the PUSCH group, wherein:

[0051] The OCC sequence superimposed on the PUSCH in the PUSCH group is determined based on configuration information and / or predefined methods.

[0052] In the embodiments of this application, the terminal device can determine the OCC sequence superimposed on the PUSCH in the PUSCH group based on configuration information and / or predefined methods, thereby improving the flexibility of OCC sequence configuration.

[0053] In some embodiments, for any first PUSCH group and second PUSCH group in at least one PUSCH group, the first OCC sequence superimposed on the PUSCH in the first PUSCH group and the second OCC sequence superimposed on the PUSCH in the second PUSCH group satisfy at least one of the following:

[0054] The first OCC sequence and the second OCC sequence are the same OCC sequence;

[0055] The first OCC sequence and the second OCC sequence belong to different sets of OCC sequences;

[0056] The first OCC sequence and the second OCC sequence belong to different indices of the same OCC sequence set;

[0057] The first OCC sequence is generated in the same way as the second OCC sequence, but the generation parameters used for the first OCC sequence are different from those used for the second OCC sequence.

[0058] The first OCC sequence is generated in a different way than the second OCC sequence.

[0059] In some embodiments, the redundant versions of the PUSCHs in the PUSCH group are determined based on at least one of the following:

[0060] Configuration information;

[0061] Index of the PUSCH group;

[0062] The transmission order of the PUSCH group;

[0063] The cyclical order of redundant versions.

[0064] In this embodiment, the terminal device can determine the redundant version of the PUSCH in the PUSCH group based on at least one of the following: configuration information, PUSCH group index, PUSCH group transmission order, and redundant version cyclic order, thereby improving the configuration flexibility of the redundant version.

[0065] In some embodiments, where UCI multiplexing on repeatedly transmitted PUSCH is permitted, the method further includes:

[0066] Repeatedly send UCI to the network device on the PUSCH in the third PUSCH group;

[0067] Among them, the third PUSCH group is the PUSCH group with the earliest corresponding start transmission time in at least one fourth PUSCH group; at least one fourth PUSCH group is the PUSCH group with a corresponding start transmission time no earlier than the first time, where the first time is the start transmission time of UCI.

[0068] In this embodiment, when there is a conflict between UCI resources and repeatedly transmitted PUSCH resources, multiplexing UCI onto PUSCH in the third PUSCH group ensures timely transmission of UCI, which is beneficial for network resource scheduling. Furthermore, by multiplexing UCI onto multiple PUSCH within a PUSCH group, the reliability of UCI transmission is improved, and the data transmitted on PUSCH within the same PUSCH group is identical. This ensures the orthogonality of uplink data transmitted by multiple terminal devices multiplexed using OCC sequences on the same time-frequency resources, improving system capacity while maintaining system decoding performance.

[0069] In some embodiments, when a terminal device sends multiple repetitive PUSCHs to a network device based on a frequency hopping method, the multiple PUSCHs include at least one PUSCH group, and an OCC sequence is superimposed on the PUSCHs in the PUSCH group, the frequency hopping type used by the multiple PUSCHs is the inter-PUSCH group frequency hopping type.

[0070] In this embodiment, repeating PUSCH transmission through inter-PUSCH frequency hopping ensures that a PUSCH group transmits identical data on the same frequency domain resources. This guarantees the orthogonality of uplink data transmitted by multiple terminal devices multiplexed by OCC sequence on the same time-frequency resources, improving system capacity while ensuring system decoding performance.

[0071] In some embodiments, the frequency domain resources of the PUSCH group are determined based on the index of the PUSCH group.

[0072] In some embodiments, configuration information is carried in at least one of the following signaling:

[0073] Downlink Control Information (DCI);

[0074] Media Access Control - Control Element MAC CE;

[0075] Radio Resource Control (RRC) message.

[0076] In this embodiment of the application, configuration information can be carried in different signaling, which improves the configuration flexibility of configuration information.

[0077] Secondly, this application provides a communication method executed by a network device, the method comprising:

[0078] Send configuration information to the terminal device. The configuration information is used to configure the terminal device to repeatedly transmit PUSCH.

[0079] Based on the configuration information, receive multiple PUSCHs sent by the terminal device;

[0080] Among them, multiple PUSCHs are repeatedly transmitted PUSCHs, and multiple PUSCHs include at least one PUSCH group. The PUSCHs in the PUSCH group use the same redundant version. N OCC sequences are superimposed on the PUSCHs in the PUSCH group, where N is 0 or 1.

[0081] In this embodiment, the network device sends configuration information indicating the relevant parameters of the repeatedly transmitted PUSCH. Multiple PUSCHs are repeatedly transmitted, comprising at least one PUSCH group. The PUSCHs within a PUSCH group use the same redundant version, ensuring that the data transmitted on the PUSCHs within the same group is identical. N OCC sequences, where N is 0 or 1, are superimposed on the PUSCHs within the PUSCH group. This embodiment superimposes OCC sequences on PUSCH groups. Since the data transmitted on the PUSCHs within the same group is identical, when multiple terminal devices repeatedly transmit PUSCHs on the same time-frequency domain resources, it ensures that the uplink data transmitted by multiple terminal devices based on PUSCHs is orthogonal, thus avoiding mutual interference between different terminal devices. This achieves code division multiplexing between different terminal devices, improving system capacity while ensuring uplink coverage and reliability.

[0082] In some embodiments, the configuration information includes at least one of the following:

[0083] PUSCH configuration information, used to configure the PUSCH for repeated transmission;

[0084] PUSCH group configuration information, used to configure at least one PUSCH group;

[0085] Frequency hopping information;

[0086] OCC configuration information is used to configure the OCC sequence superimposed on the PUSCH in the PUSCH group;

[0087] UCI indication information is used to indicate whether UCI multiplexing is allowed on repeatedly transmitted PUSCH.

[0088] In this embodiment of the application, the network device sends configuration information to the terminal device, thereby enabling the terminal device to send multiple PUSCHs according to at least one of the following information in the configuration information: PUSCH configuration information, PUSCH group configuration information, frequency hopping information, OCC configuration information, and UCI indication information.

[0089] In some embodiments, PUSCH configuration information includes:

[0090] The number of times the terminal device repeatedly transmits the PUSCH;

[0091] And / or,

[0092] The terminal device repeatedly transmits PUSCH resources.

[0093] In this embodiment of the application, the network device can send configuration information to instruct the terminal device on the number of times to repeatedly transmit PUSCH and / or the resources of the terminal device to repeatedly transmit PUSCH, thereby helping the terminal device to send multiple PUSCHs to the network device according to the number of times the terminal device repeatedly transmits PUSCH and / or the resources of the terminal device to repeatedly transmit PUSCH.

[0094] In some embodiments, the PUSCH group configuration information includes at least one of the following:

[0095] The number of at least one PUSCH group;

[0096] The number of PUSCHs in the PUSCH group;

[0097] The transmission order of the PUSCH group;

[0098] Redundancy version information for PUSCH groups, used to indicate the redundant versions used by PUSCHs in the PUSCH group.

[0099] In this embodiment of the application, the network device can send PUSCH group configuration information, which helps the terminal device to send multiple PUSCHs to the network device according to the PUSCH group configuration information.

[0100] In some embodiments, the frequency hopping information includes at least one of the following:

[0101] The first indication information is used to indicate whether the terminal device repeatedly transmits PUSCH based on frequency hopping.

[0102] Frequency hopping type;

[0103] Frequency hopping parameters are used to indicate the frequency domain resources of the PUSCH group.

[0104] In this embodiment, the network device can send configuration information to indicate whether to repeatedly transmit multiple PUSCHs using frequency hopping. If multiple PUSCHs are repeatedly transmitted using frequency hopping, by configuring an appropriate frequency hopping type, such as configuring at least one PUSCH group with superimposed OCC sequences as inter-PUSCH group frequency hopping, frequency selective gain and randomized interference are obtained, while ensuring that a PUSCH group transmits the exact same data on the same frequency domain resources. This ensures the orthogonality between uplink data transmitted by multiple terminal devices multiplexed by OCC sequences on the same time and frequency resources, thereby improving system capacity while ensuring system decoding performance.

[0105] In some embodiments, frequency hopping types include at least one of the following:

[0106] Frequency hopping type within a time slot;

[0107] Inter-slot frequency hopping type;

[0108] PUSCH inter-group frequency hopping type.

[0109] In some embodiments, the OCC configuration information includes at least one of the following:

[0110] The second indication information is used to indicate whether an OCC sequence is superimposed on the PUSCH in the PUSCH group;

[0111] Length of the OCC sequence;

[0112] Index of OCC sequence;

[0113] How OCC sequences are generated;

[0114] OCC sequence set.

[0115] In this embodiment, the network device can send OCC configuration information to indicate whether an OCC sequence needs to be superimposed on the PUSCH in the PUSCH group, and to indicate the specific OCC sequence. This helps to ensure the orthogonality between uplink data transmitted by multiple terminal devices that reuse OCC sequences on the same time-frequency resources.

[0116] In some embodiments, an OCC sequence is superimposed on the PUSCH in the PUSCH group, and the PUSCH group satisfies:

[0117] The number of PUSCHs in a PUSCH group is equal to the length of the OCC sequence superimposed on the PUSCHs in the PUSCH group.

[0118] In this embodiment, the number of PUSCHs in a PUSCH group is equal to the length of the OCC sequence superimposed on the PUSCHs in the PUSCH group, and the data transmitted on the PUSCHs in the same PUSCH group is exactly the same. When multiple terminal devices repeatedly transmit PUSCHs on the same time-frequency domain resources, it can ensure that the uplink data transmitted by multiple terminal devices based on PUSCHs are mutually orthogonal, thereby avoiding mutual interference between different terminal devices and realizing code division multiplexing between different terminal devices. While ensuring the uplink coverage and reliability of the system, the system capacity is improved.

[0119] In some embodiments, the number of PUSCHs in different PUSCH groups is the same; or, the number of PUSCHs in different PUSCH groups is different.

[0120] In this embodiment, the number of PUSCHs in different PUSCH groups is the same, resulting in lower processing complexity for both network devices and terminal devices, thus improving processing efficiency. The different number of PUSCHs in different PUSCH groups allows for the rational allocation of resources based on the transmission needs of different terminal devices, enabling flexible configuration of multiple terminal devices for reuse, thereby effectively improving system capacity and throughput.

[0121] In some embodiments, an OCC sequence is superimposed on the PUSCH in the PUSCH group, wherein:

[0122] The OCC sequence superimposed on the PUSCH in the PUSCH group is determined based on configuration information and / or predefined methods.

[0123] In the embodiments of this application, the terminal device can determine the OCC sequence superimposed on the PUSCH in the PUSCH group based on configuration information and / or predefined methods, thereby improving the flexibility of OCC sequence configuration.

[0124] In some embodiments, for any first PUSCH group and second PUSCH group in at least one PUSCH group, the first OCC sequence superimposed on the PUSCH in the first PUSCH group and the second OCC sequence superimposed on the PUSCH in the second PUSCH group satisfy at least one of the following:

[0125] The first OCC sequence and the second OCC sequence are the same OCC sequence;

[0126] The first OCC sequence and the second OCC sequence belong to different sets of OCC sequences;

[0127] The first OCC sequence and the second OCC sequence belong to different indices of the same OCC sequence set;

[0128] The first OCC sequence is generated in the same way as the second OCC sequence, but the generation parameters used for the first OCC sequence are different from those used for the second OCC sequence.

[0129] The first OCC sequence is generated in a different way than the second OCC sequence.

[0130] In some embodiments, the redundant versions of the PUSCHs in the PUSCH group are determined based on at least one of the following:

[0131] Configuration information;

[0132] Index of the PUSCH group;

[0133] The transmission order of the PUSCH group;

[0134] The cyclical order of redundant versions.

[0135] In this embodiment, the redundant version of the PUSCH in the PUSCH group can be determined based on at least one of the following: configuration information, PUSCH group index, PUSCH group transmission order, and redundant version cyclic order, thereby improving the configuration flexibility of the redundant version.

[0136] In some embodiments, where UCI multiplexing on repeatedly transmitted PUSCH is permitted, the method further includes:

[0137] Receive the UCI repeatedly transmitted by the terminal device on the PUSCH in the third PUSCH group;

[0138] Among them, the third PUSCH group is the PUSCH group with the earliest corresponding start transmission time in at least one fourth PUSCH group; at least one fourth PUSCH group is the PUSCH group with a corresponding start transmission time no earlier than the first time, where the first time is the start transmission time of UCI.

[0139] In this embodiment, when there is a conflict between UCI resources and repeatedly transmitted PUSCH resources, multiplexing UCI onto PUSCH in the third PUSCH group ensures timely transmission of UCI, which is beneficial for network resource scheduling. Furthermore, by multiplexing UCI onto multiple PUSCH within a PUSCH group, the reliability of UCI transmission is improved, and the data transmitted within a PUSCH group is guaranteed to be identical. This ensures the orthogonality of uplink data transmitted by multiple terminal devices multiplexed using OCC sequences on the same time-frequency resources, improving system capacity while maintaining system decoding performance.

[0140] In some embodiments, when a terminal device sends multiple repetitive PUSCHs to a network device based on a frequency hopping method, the multiple PUSCHs include at least one PUSCH group, and an OCC sequence is superimposed on the PUSCHs in the PUSCH group, the frequency hopping type used by the multiple PUSCHs is the inter-PUSCH group frequency hopping type.

[0141] In this embodiment, repeating PUSCH transmission through inter-PUSCH frequency hopping ensures that a PUSCH group transmits identical data on the same frequency domain resources. This guarantees the orthogonality of uplink data transmitted by multiple terminal devices multiplexed by OCC sequence on the same time-frequency resources, improving system capacity while ensuring system decoding performance.

[0142] In some embodiments, the frequency domain resources of the PUSCH group are determined based on the index of the PUSCH group.

[0143] In some embodiments, the plurality of PUSCHs includes at least a fifth PUSCH group sent by a first terminal device and a sixth PUSCH group sent by a second terminal device; a third OCC sequence is superimposed on the PUSCHs in the fifth PUSCH group, and a fourth OCC sequence is superimposed on the PUSCHs in the sixth PUSCH group; wherein:

[0144] The resources of the fifth PUSCH group are the same as those of the sixth PUSCH group, and the third OCC sequence and the fourth OCC sequence are orthogonal to each other.

[0145] or,

[0146] The resources of the first PUSCH sequence are the same as those of the second PUSCH sequence. The first PUSCH sequence has a first OCC subsequence superimposed on the PUSCH, and the second PUSCH sequence has a second OCC subsequence superimposed on the PUSCH. The first OCC subsequence and the second OCC subsequence are orthogonal to each other.

[0147] The first PUSCH sequence is a subset of the fifth PUSCH group, the second PUSCH sequence is a subset of the sixth PUSCH group, the first OCC subsequence is a subset of the third OCC sequence, and the second OCC subsequence is a subset of the fourth OCC sequence.

[0148] In some embodiments, the third OCC sequence and the fourth OCC sequence satisfy at least one of the following:

[0149] The third OCC sequence and the fourth OCC sequence belong to different sets of OCC sequences;

[0150] The third and fourth OCC sequences belong to different indices of the same OCC sequence set;

[0151] The third OCC sequence is generated in the same way as the fourth OCC sequence, but the generation parameters used for the third OCC sequence are different from those used for the fourth OCC sequence.

[0152] The third OCC sequence is generated in a different way than the fourth OCC sequence.

[0153] In this embodiment of the application, the network device can flexibly configure the multiplexing method among multiple terminal devices according to the transmission requirements of different terminal devices, effectively improving system capacity and throughput.

[0154] In some embodiments, configuration information is carried in at least one of the following signaling:

[0155] DCI;

[0156] MAC CE;

[0157] RRC message.

[0158] In this embodiment of the application, configuration information can be carried in different signaling, which improves the configuration flexibility of configuration information.

[0159] Thirdly, embodiments of this application provide a communication device, including:

[0160] The transceiver module is used to receive configuration information sent by network devices. This configuration information is used to configure the terminal device to repeatedly transmit PUSCH.

[0161] The transceiver module is also used to send multiple PUSCHs to network devices according to configuration information;

[0162] Among them, multiple PUSCHs are repeatedly transmitted PUSCHs, and multiple PUSCHs include at least one PUSCH group. The PUSCHs in the PUSCH group use the same redundant version. N OCC sequences are superimposed on the PUSCHs in the PUSCH group, where N is 0 or 1.

[0163] In some embodiments, the configuration information includes at least one of the following:

[0164] PUSCH configuration information, used to configure the PUSCH for repeated transmission;

[0165] PUSCH group configuration information, used to configure at least one PUSCH group;

[0166] Frequency hopping information;

[0167] OCC configuration information is used to configure the OCC sequence superimposed on the PUSCH in the PUSCH group;

[0168] Uplink control information (UCI) indication information is used to indicate whether UCI multiplexing is allowed on repeatedly transmitted PUSCH.

[0169] In some embodiments, PUSCH configuration information includes:

[0170] The number of times the terminal device repeatedly transmits the PUSCH;

[0171] And / or,

[0172] The terminal device repeatedly transmits PUSCH resources.

[0173] In some embodiments, the PUSCH group configuration information includes at least one of the following:

[0174] The number of at least one PUSCH group;

[0175] The number of PUSCHs in the PUSCH group;

[0176] The transmission order of the PUSCH group;

[0177] Redundancy version information for PUSCH groups, used to indicate the redundant versions used by PUSCHs in the PUSCH group.

[0178] In some embodiments, the frequency hopping information includes at least one of the following:

[0179] The first indication information is used to indicate whether the terminal device repeatedly transmits PUSCH based on frequency hopping.

[0180] Frequency hopping type;

[0181] Frequency hopping parameters are used to indicate the frequency domain resources of the PUSCH group.

[0182] In some embodiments, frequency hopping types include at least one of the following:

[0183] Frequency hopping type within a time slot;

[0184] Inter-slot frequency hopping type;

[0185] PUSCH inter-group frequency hopping type.

[0186] In some embodiments, the OCC configuration information includes at least one of the following:

[0187] The second indication information is used to indicate whether an OCC sequence is superimposed on the PUSCH in the PUSCH group;

[0188] Length of the OCC sequence;

[0189] Index of OCC sequence;

[0190] How OCC sequences are generated;

[0191] OCC sequence set.

[0192] In some embodiments, an OCC sequence is superimposed on the PUSCH in the PUSCH group, and the PUSCH group satisfies:

[0193] The number of PUSCHs in a PUSCH group is equal to the length of the OCC sequence superimposed on the PUSCHs in the PUSCH group.

[0194] In some embodiments, the number of PUSCHs in different PUSCH groups is the same; or, the number of PUSCHs in different PUSCH groups is different.

[0195] In some embodiments, an OCC sequence is superimposed on the PUSCH in the PUSCH group, wherein:

[0196] The OCC sequence superimposed on the PUSCH in the PUSCH group is determined based on configuration information and / or predefined methods.

[0197] In some embodiments, for any first PUSCH group and second PUSCH group in at least one PUSCH group, the first OCC sequence superimposed on the PUSCH in the first PUSCH group and the second OCC sequence superimposed on the PUSCH in the second PUSCH group satisfy at least one of the following:

[0198] The first OCC sequence and the second OCC sequence are the same OCC sequence;

[0199] The first OCC sequence and the second OCC sequence belong to different sets of OCC sequences;

[0200] The first OCC sequence and the second OCC sequence belong to different indices of the same OCC sequence set;

[0201] The first OCC sequence is generated in the same way as the second OCC sequence, but the generation parameters used for the first OCC sequence are different from those used for the second OCC sequence.

[0202] The first OCC sequence is generated in a different way than the second OCC sequence.

[0203] In some embodiments, the redundant versions of the PUSCHs in the PUSCH group are determined based on at least one of the following:

[0204] Configuration information;

[0205] Index of the PUSCH group;

[0206] The transmission order of the PUSCH group;

[0207] The cyclical order of redundant versions.

[0208] In some embodiments, where UCI multiplexing on repeatedly transmitted PUSCH is permitted, the transceiver module is further configured to:

[0209] Repeatedly send UCI to the network device on the PUSCH in the third PUSCH group;

[0210] Among them, the third PUSCH group is the PUSCH group with the earliest corresponding start transmission time in at least one fourth PUSCH group; at least one fourth PUSCH group is the PUSCH group with a corresponding start transmission time no earlier than the first time, where the first time is the start transmission time of UCI.

[0211] In some embodiments, when a terminal device sends multiple PUSCHs to a network device based on a frequency hopping method, the frequency hopping type used by the multiple PUSCHs is the inter-PUSCH group frequency hopping type.

[0212] In some embodiments, the frequency domain resources of the PUSCH group are determined based on the index of the PUSCH group.

[0213] In some embodiments, configuration information is carried in at least one of the following signaling:

[0214] DCI;

[0215] MAC CE;

[0216] RRC message.

[0217] Fourthly, embodiments of this application provide a communication device, including:

[0218] The transceiver module is used to send configuration information to the terminal device. The configuration information is used to configure the terminal device to repeatedly transmit PUSCH.

[0219] The transceiver module is also used to receive multiple PUSCHs sent by the terminal device according to the configuration information;

[0220] Among them, multiple PUSCHs are repeatedly transmitted PUSCHs, and multiple PUSCHs include at least one PUSCH group. The PUSCHs in the PUSCH group use the same redundant version. N OCC sequences are superimposed on the PUSCHs in the PUSCH group, where N is 0 or 1.

[0221] In some embodiments, the configuration information includes at least one of the following:

[0222] PUSCH configuration information, used to configure the PUSCH for repeated transmission;

[0223] PUSCH group configuration information, used to configure at least one PUSCH group;

[0224] Frequency hopping information;

[0225] OCC configuration information is used to configure the OCC sequence superimposed on the PUSCH in the PUSCH group;

[0226] UCI indication information is used to indicate whether UCI multiplexing is allowed on repeatedly transmitted PUSCH.

[0227] In some embodiments, PUSCH configuration information includes:

[0228] The number of times the terminal device repeatedly transmits the PUSCH;

[0229] And / or,

[0230] The terminal device repeatedly transmits PUSCH resources.

[0231] In some embodiments, the PUSCH group configuration information includes at least one of the following:

[0232] The number of at least one PUSCH group;

[0233] The number of PUSCHs in the PUSCH group;

[0234] The transmission order of the PUSCH group;

[0235] Redundancy version information for PUSCH groups, used to indicate the redundant versions used by PUSCHs in the PUSCH group.

[0236] In some embodiments, the frequency hopping information includes at least one of the following:

[0237] The first indication information is used to indicate whether the terminal device repeatedly transmits PUSCH based on frequency hopping.

[0238] Frequency hopping type;

[0239] Frequency hopping parameters are used to indicate the frequency domain resources of the PUSCH group.

[0240] In some embodiments, frequency hopping types include at least one of the following:

[0241] Frequency hopping type within a time slot;

[0242] Inter-slot frequency hopping type;

[0243] PUSCH inter-group frequency hopping type.

[0244] In some embodiments, the OCC configuration information includes at least one of the following:

[0245] The second indication information is used to indicate whether an OCC sequence is superimposed on the PUSCH in the PUSCH group;

[0246] Length of the OCC sequence;

[0247] Index of OCC sequence;

[0248] How OCC sequences are generated;

[0249] OCC sequence set.

[0250] In some embodiments, an OCC sequence is superimposed on the PUSCH in the PUSCH group, and the PUSCH group satisfies:

[0251] The number of PUSCHs in a PUSCH group is equal to the length of the OCC sequence superimposed on the PUSCHs in the PUSCH group.

[0252] In some embodiments, the number of PUSCHs in different PUSCH groups is the same; or, the number of PUSCHs in different PUSCH groups is different.

[0253] In some embodiments, an OCC sequence is superimposed on the PUSCH in the PUSCH group, wherein:

[0254] The OCC sequence superimposed on the PUSCH in the PUSCH group is determined based on configuration information and / or predefined methods.

[0255] In some embodiments, for any first PUSCH group and second PUSCH group in at least one PUSCH group, the first OCC sequence superimposed on the PUSCH in the first PUSCH group and the second OCC sequence superimposed on the PUSCH in the second PUSCH group satisfy at least one of the following:

[0256] The first OCC sequence and the second OCC sequence are the same OCC sequence;

[0257] The first OCC sequence and the second OCC sequence belong to different sets of OCC sequences;

[0258] The first OCC sequence and the second OCC sequence belong to different indices of the same OCC sequence set;

[0259] The first OCC sequence is generated in the same way as the second OCC sequence, but the generation parameters used for the first OCC sequence are different from those used for the second OCC sequence.

[0260] The first OCC sequence is generated in a different way than the second OCC sequence.

[0261] In some embodiments, the redundant versions of the PUSCHs in the PUSCH group are determined based on at least one of the following:

[0262] Configuration information;

[0263] Index of the PUSCH group;

[0264] The transmission order of the PUSCH group;

[0265] The cyclical order of redundant versions.

[0266] In some embodiments, where UCI multiplexing on repeatedly transmitted PUSCH is permitted, the transceiver module is further configured to:

[0267] Receive the UCI repeatedly transmitted by the terminal device on the PUSCH in the third PUSCH group;

[0268] Among them, the third PUSCH group is the PUSCH group with the earliest corresponding start transmission time in at least one fourth PUSCH group; at least one fourth PUSCH group is the PUSCH group with a corresponding start transmission time no earlier than the first time, where the first time is the start transmission time of UCI.

[0269] In some embodiments, when a terminal device sends multiple PUSCHs to a network device based on a frequency hopping method, the frequency hopping type used by the multiple PUSCHs is the inter-PUSCH group frequency hopping type.

[0270] In some embodiments, the frequency domain resources of the PUSCH group are determined based on the index of the PUSCH group.

[0271] In some embodiments, the plurality of PUSCHs includes at least a fifth PUSCH group sent by a first terminal device and a sixth PUSCH group sent by a second terminal device; a third OCC sequence is superimposed on the PUSCHs in the fifth PUSCH group, and a fourth OCC sequence is superimposed on the PUSCHs in the sixth PUSCH group; wherein:

[0272] The resources of the fifth PUSCH group are the same as those of the sixth PUSCH group, and the third OCC sequence and the fourth OCC sequence are orthogonal to each other.

[0273] or,

[0274] The resources of the first PUSCH sequence are the same as those of the second PUSCH sequence. The first PUSCH sequence has a first OCC subsequence superimposed on the PUSCH, and the second PUSCH sequence has a second OCC subsequence superimposed on the PUSCH. The first OCC subsequence and the second OCC subsequence are orthogonal to each other.

[0275] The first PUSCH sequence is a subset of the fifth PUSCH group, the second PUSCH sequence is a subset of the sixth PUSCH group, the first OCC subsequence is a subset of the third OCC sequence, and the second OCC subsequence is a subset of the fourth OCC sequence.

[0276] In some embodiments, the third OCC sequence and the fourth OCC sequence satisfy at least one of the following:

[0277] The third OCC sequence and the fourth OCC sequence belong to different sets of OCC sequences;

[0278] The third and fourth OCC sequences belong to different indices of the same OCC sequence set;

[0279] The third OCC sequence is generated in the same way as the fourth OCC sequence, but the generation parameters used for the third OCC sequence are different from those used for the fourth OCC sequence.

[0280] The third OCC sequence is generated in a different way than the fourth OCC sequence.

[0281] In some embodiments, configuration information is carried in at least one of the following signaling:

[0282] DCI;

[0283] MAC CE;

[0284] RRC message.

[0285] Fifthly, embodiments of this application provide a communication device, which includes:

[0286] At least one processor; and

[0287] A memory that is communicatively connected to at least one processor; wherein,

[0288] The memory stores instructions that can be executed by at least one processor, which enables the at least one processor to perform any one of the communication methods of the first aspect to the second aspect.

[0289] In a sixth aspect, embodiments of this application provide a communication system including a terminal device and a network device, wherein the terminal device is configured to implement the communication method of any one of the first aspects, and the network device is configured to implement the communication method of any one of the second aspects.

[0290] In a seventh aspect, embodiments of this application provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform a communication method as described in any one of the first to second aspects.

[0291] Eighthly, embodiments of this application provide a program product including at least one of a program and instructions, wherein when the program and at least one of the instructions are executed by a communication device, the program implements the communication method of any one of the first to second aspects. Attached Figure Description

[0292] Figure 1 This is a schematic diagram of the architecture of the communication system shown in the embodiments of this application;

[0293] Figure 2 This is a schematic diagram of an NTN communication provided in an embodiment of this application;

[0294] Figure 3 This is a schematic diagram of repeated PUSCH transmission provided in an embodiment of this application;

[0295] Figure 4 This is a schematic diagram of a redundant version provided in the embodiments of this application;

[0296] Figure 5 This is a signaling diagram of the communication method provided in the embodiments of this application;

[0297] Figure 6 This is a schematic diagram of PUSCH retransmission provided in the embodiments of this application. Figure 1 ;

[0298] Figure 7 A schematic diagram of PUSCH retransmission provided in the embodiments of this application. Figure 2 ;

[0299] Figure 8 A schematic diagram of PUSCH retransmission provided in the embodiments of this application. Figure 3 ;

[0300] Figure 9 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application. Figure 1 ;

[0301] Figure 10 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application. Figure 2 ;

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

[0303] The technical solution provided in this application will now be described with reference to the accompanying drawings.

[0304] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0305] In the embodiments of this application, prefixes such as "first" and "second" are used merely to distinguish different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects can be found in the context of the embodiments of this application, and the use of prefixes should not constitute unnecessary restrictions. For example, "first device" and "second device" are simply different devices and do not limit the number of devices or their priority; similarly, "first information" and "second information" are simply different pieces of information, and they have no temporal sequence, size, or priority relationship.

[0306] In the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates an "or" relationship between the preceding and following related objects, but it does not exclude the possibility of indicating an "and" relationship. The specific meaning can be understood in conjunction with the context. "At least one of the following" or similar expressions refer 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 represent: a, b, c; a and b; a and c; b and c; or a and b and c. Here, a, b, and c can be single or multiple.

[0307] In the embodiments of this application, "including A," "containing A," "used to indicate A," and "carrying A" can be interpreted as directly carrying A or indirectly indicating A. The indication includes explicit indication (also called direct indication) and implicit indication (also called indirect indication). Explicit indication of A means including A; implicit indication of A means indicating A through the correspondence between A and B and the direct indication B. The correspondence between A and B can be predefined, pre-stored, pre-burned, or pre-configured; or it can refer to indicating A through B and preset rules.

[0308] In the embodiments of this application, terms such as "in response to...", "in response to determining...", "in the case of...", "when...", "when...", "if...", etc. can be used interchangeably. These descriptions all refer to the device making corresponding processing under certain objective circumstances. It is not necessary to limit the time, nor is it required that the device must have a judgment action when implementing it, nor does it mean that there must be other limitations.

[0309] The technical solutions provided in this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Long Term Evolution Advanced (LTE-A) systems, sidelink (SL) communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, 5th Generation (5G) mobile communication systems or new radio access technology (NR), satellite communication systems, etc. Among these, 5G mobile communication systems can include non-standalone (NSA) and / or standalone (SA) networks. Satellite communication systems can be satellite communication systems integrated with 5G mobile communication systems or future communication systems, such as non-terrestrial networks (NTNs), etc., and this application does not limit this. The technical solution provided in this application can also be applied to future communication systems, such as the sixth generation (6G) mobile communication system.

[0310] Figure 1 This is a schematic diagram of the architecture of a communication system shown in an embodiment of this application. Figure 1 As shown, by way of example and not limitation, the communication system 1100 includes a terminal device 1101 and a network device 1102.

[0311] The terminal device 1101 involved in this application embodiment can be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. The terminal device can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships); and it can also be deployed in the air (e.g., on airplanes, balloons, and satellites). Terminal devices 1101 include, for example, mobile phones, wearable devices, Internet of Things (IoT) devices, cars with communication capabilities, smart cars, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminal devices in industrial control, wireless terminal devices in self-driving, wireless terminal devices in remote medical surgery, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, wireless terminal devices in smart homes, and so on.

[0312] The name of the terminal device may differ across different systems. For example, in a 5G or 6G system, the terminal device may be called User Equipment (UE). In some embodiments, the terminal device may also be referred to as a terminal, user terminal, mobile station, mobile terminal, mobile unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client, vehicle-mounted terminal, vehicle-mounted terminal equipment, industrial control terminal equipment, UE unit, UE station, UE agent, UE device, etc., and is not limited in the embodiments of this application.

[0313] The network device 1102 involved in the embodiments of this application may include at least one of an access network device and a core network device.

[0314] Access network equipment is part of a communication system, used to help terminal devices achieve wireless access. The name of access network equipment may vary in different systems. For example, access network equipment can also be called radio access network device (RAN device), base station (BS), radio base station, fixed station, node, access point, transmission point (TP), reception point (RP), transmission and / or reception point (TRP), and so on.

[0315] In some embodiments, access network equipment may be, for example, a base station, an evolved NodeB (eNodeB), an evolved NodeB (eNB) in a 5G communication system, a next-generation eNB (ng-eNB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a home node B (HNB), a home evolved node B (HeNB), a radio backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, or an open base station. Access network equipment can be RAN (Radio Access Network), Cloud RAN (Cloud RAN), next-generation base stations in 6G mobile communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. It can also be macro base stations, micro base stations, indoor stations, relay nodes, or radio controllers in CRAN scenarios. Optionally, access network equipment can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in vehicle-to-everything (V2X) technology, the access network equipment can be a roadside unit (RSU). In satellite communication systems, access network equipment can be a satellite or base station equipment mounted on a satellite. Access network equipment in satellite communication can also be a satellite communication terminal, such as a portable station, a fixed station, or a vehicle-mounted or airborne satellite communication terminal. It should be understood that satellite communication terminals communicate with satellites and can also act as micro base stations to further provide data interfaces to accessed user equipment.

[0316] In some embodiments, the access network device can consist of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure allows the protocol layers of the access network device to be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed in the DU, which is centrally controlled by the CU. The CU and DU can be separate entities or included in the same network element, such as a baseband unit (BBU).

[0317] In different systems, CU and DU may have different names, but those skilled in the art will understand their meaning. For example, in the ORAN system, CU can also be called O-CU (Open CU), and DU can also be called O-DU. Any unit in CU or DU can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0318] In some embodiments, a core network device can be a single device comprising different core network elements, or it can be multiple devices or a group of devices, each comprising all or part of the core network elements. Network elements can be virtual or physical. The core network includes, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

[0319] In the embodiments of this application, the terminal device and the network device can be hardware devices, or software functions running on dedicated hardware, or software functions running on general-purpose hardware, such as virtualization functions instantiated on a platform (e.g., a cloud platform), or entities that include dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the terminal device and the network device.

[0320] To better understand the methods provided in the embodiments of this application, the terms involved in this application will be briefly explained below.

[0321] 1. NTN

[0322] NTN is a wireless communication system that operates above the Earth's surface, enabling extensive coverage of the Earth's surface and multidimensional space based on satellites, high-altitude platforms, and drones in Earth orbit. NTN includes satellite networks operating in different orbits, such as low Earth orbit (LEO), medium Earth orbit (MEO), and geostationary Earth orbit (GEO).

[0323] Figure 2 This is a schematic diagram of NTN communication provided in an embodiment of this application, as shown below. Figure 2 As shown, it includes terminal equipment 201, satellite 202, and NTN ground station 203. Among them, satellite 202 can transmit signals by transmitting beams to the earth. In order to ensure the coverage of satellite 202 and improve the system capacity of the entire satellite communication system, satellite 202 can use multiple beams to cover the ground. Different satellites can use different beam shapes and coverage ranges to meet the communication needs of different areas.

[0324] Currently, based on the different methods of satellite signal processing, relay modes can be divided into transparent relay mode and regenerative relay mode. In transparent relay mode, the NTN ground station sends the base station's signal to satellite 202. Satellite 202 converts the signal to the satellite frequency band and then transmits it to terminal device 201 via the satellite frequency band. In this process, satellite 202 only performs signal filtering, frequency conversion, RF amplification, and RF transceiver processing; it does not demodulate the signal. In this NTN communication system architecture, satellite 202 can be regarded as a relay device between terminal device 201 and the base station. In regenerative relay mode, satellite 202 functions as a base station. The NTN ground station sends the base station's signal to satellite 202. Satellite 202 demodulates and decodes the signal, then re-encodes and modulates it, and transmits the regenerated signal to terminal device 201 via the satellite frequency band.

[0325] NTN is an important supplement to terrestrial cellular communication technology. By integrating non-terrestrial and terrestrial networks, it can provide ubiquitous coverage regardless of terrain, connecting multiple dimensions of space, air, land, and sea to form an integrated ubiquitous access network, enabling on-demand access in all scenarios.

[0326] Compared to terrestrial networks, NTN systems suffer from greater propagation delays. The high-speed movement of low-Earth orbit satellites relative to the ground also introduces significant Doppler shift. Furthermore, the distance between terminal devices and satellites and base stations is substantial, leading to attenuation issues common to terrestrial communication, as well as adverse weather conditions such as heavy rain or atmospheric interference. Due to limited transmission power, the high propagation loss in satellite communication severely impacts link budgets, particularly uplink resources. To overcome path loss and uplink bandwidth limitations in satellite communication, NTN employs various coverage enhancement technologies. These include installing large onboard phased array antennas and beamforming techniques on the satellite side, and setting elevation thresholds and repetitive uplink control channel transmissions on the terminal device side to improve signal reception strength and transmission distance.

[0327] Compared to the typical cell radius of terrestrial networks, which ranges from a few hundred meters to several kilometers, NTN cells have a much larger coverage area, with LEO beams reaching up to 1,000 kilometers and GEO beams reaching up to 3,500 kilometers. Therefore, the time delay differences between the center and edge of a satellite cell will be more pronounced, and the number of terminal devices within a cell will increase exponentially, placing higher demands on system timing synchronization and system capacity.

[0328] 2. PUSCH repetition

[0329] PUSCH is a key uplink channel in LTE and NR, used to transmit user data (such as application layer data) and some uplink control information (UCI).

[0330] PUSCH retransmission is a technique used to improve uplink transmission reliability. Its main purpose is to increase the success rate of data transmission by transmitting the same data multiple times, especially in situations with poor wireless channel conditions or insufficient signal coverage.

[0331] During PUSCH retransmission, network devices can configure relevant parameters for PUSCH retransmission to terminal devices via radio resource control (RRC) signaling, such as PUSCH retransmission type, whether frequency hopping is enabled, etc. When a terminal device needs to send uplink data, the network device can send downlink control information (DCI) via the physical downlink control channel (PDCCH). The DCI may include PUSCH time-frequency resource allocation information, redundancy version (RV), and information such as the number of PUSCH retransmissions, start symbol, and length.

[0332] Currently, PUSCH retransmission mainly includes two types: Type A and Type B.

[0333] PUSCH Repetition Type A is a type of PUSCH repetition transmission that repeats at the slot level. Each slot uses the same symbol-level allocation (the start symbol S and length L are consistent). For details, please refer to [link to relevant documentation]. Figure 3 Examples.

[0334] Figure 3 This is a schematic diagram of repeated PUSCH transmission provided in an embodiment of this application. Please refer to [link / reference]. Figure 3 The example is the PUSCHRepetition Type A transmission process.

[0335] For PUSCH Repetition Type A transmission, the terminal device needs to send the same transport block (TB) over K consecutive time slots. The TB is carried on the PUSCH for transmission, and the value of K can be configured by the network device. During the terminal device's transmission of the K PUSCHs, the symbol positions occupied by the PUSCH in the K time slots are exactly the same (including the starting symbol position in the time slot and the length of the occupied symbol).

[0336] like Figure 3As shown, for example, each time slot includes 14 symbols. The starting symbol position of PUSCH is the first symbol in the time slot, and the symbol length is n (n is less than or equal to 14). Therefore, for any i-th PUSCH transmission, the time domain resources used are the first to nth symbols in time slot #i. For example, the terminal device transmits PUSCH on the first to nth symbols of time slot #1, PUSCH on the first to nth symbols of time slot #2, PUSCH on the first to nth symbols of time slot #3, ..., and PUSCH on the first to nth symbols of time slot #K, thereby completing K repeated PUSCH transmissions.

[0337] PUSCH Repetition Type A is primarily used in scenarios requiring high reliability, such as under poor channel conditions, to improve data transmission success rate through multiple repeated PUSCH transmissions. The maximum number of PUSCH transmissions can be configured by `numberOfRepetitions` in `PUSCH-TimeDomainResourceAllocationList->PUSCH-Allocation`, for example, it can be set to 32 or other values; this application embodiment does not limit this. PUSCH repetition Type A supports frequency hopping between and within time slots. After obtaining the frequency hopping status and related configurations based on RRC and / or DCI, the RB start position for frequency hopping between or within time slots can be calculated according to the protocol's predefined formula and the frequency hopping offset value (the offset between the hopped frequency and the current frequency during the frequency hopping process).

[0338] PUSCH repetition Type B is another type of PUSCH repetition transmission, which is based on mini-slot (time resource less than one time slot) level or symbol level repetition. For PUSCH repetition Type B transmission, the terminal device can start transmitting PUSCH at different symbol positions within a time slot, or it can transmit PUSCH across time slot boundaries. PUSCH repetition Type B aims to reduce latency and improve uplink resource utilization by repetitively transmitting PUSCH through flexible configuration and smaller time domain resource units, thus better adapting to the needs of ultra-reliable and low-latency communication (URLLC).

[0339] 3. Orthogonal covering codes (OCC)

[0340] OCC (Optical Code Coding) is a coding technique used in wireless communication systems to reduce interference and improve overall system performance. OCC is a set of orthogonal code sequences, also known as OCC sequences. OCC sequences are used to distinguish different ports, terminal devices, antennas, etc., in the code domain. Based on OCC sequences, multiple data streams transmitted simultaneously on the same time-frequency resources can be made to operate without interference, thereby increasing system capacity and efficiency.

[0341] The inner product between a set of orthogonal OCC sequences is zero (unless two identical sequences are multiplied, in which case the inner product equals the length of the OCC sequence). This orthogonality allows multiple data streams to be transmitted simultaneously without interfering with each other.

[0342] In 5G NR systems, for the transmission processes of Physical Uplink Control Channel (PUCCH) formats 2, 3, and 4, terminal devices can achieve orthogonal multiplexing among multiple terminal devices based on OCC sequences. For the transmission processes of demodulation reference signal (DMRS) and channel state information reference signal (CSI-RS), code division multiplexing can also be achieved using OCC sequences.

[0343] Currently, there are various combinations of OCC sequences, with lengths of 2, 4, or other values. Tables 1 and 2 below illustrate OCC sequences of length 4 for PUCCH format 2 and OCC sequences of length 2, respectively:

[0344] Table 1

[0345] n <![CDATA[w n (i)]]> 0 [+1+1+1+1] 1 [+1-1+1-1] 2 [+1+1-1-1] 3 [+1-1-1+1]

[0346] Table 2

[0347] n <![CDATA[w n (i) <!-- 17 -->]]> 0 [+1+1] 1 [+1-1]

[0348] In Tables 1 and 2, n represents the index of the OCC sequence, w n (i) is an OCC sequence.

[0349] It should be noted that the OCC sequences in Table 1 are merely examples and do not constitute a limitation on the OCC sequence or its length. For example, in some embodiments, mutually orthogonal sequences can also be generated as OCC sequences using Walsh-Hadamard codes, Golay codes, or cyclic shifts of base sequences.

[0350] 4. Redundancy Version (RV)

[0351] The redundant version design is used to implement incremental redundancy (IR) hybrid automatic repeat request (HARQ) transmission. That is, the redundant bits generated by the encoder are divided into several groups, and each redundant version defines a transmission start point. By using different redundant versions in multiple HARQ transmissions, the redundant bits are gradually accumulated, which can increase the probability of correct decoding at the receiver and thus improve the reliability of transmission.

[0352] The 5G NR PUSCH channel uses Low-Density Parity-Check (LDPC) coding to add redundancy information and stores it in a circular buffer. Starting from the corresponding position according to the configuration information, the encoded bit stream needs to be rate-matched and bits selected according to the actual physical resources of transmission. After bit interleaving, different redundancy versions are generated to support the HARQ process.

[0353] Figure 4 This is a schematic diagram of the redundant versions provided in the embodiments of this application. The bit start positions corresponding to different redundant versions are as follows: Figure 4 As shown. In Figure 4 The example shows four redundant versions: rv0, rv1, rv2, and rv3.

[0354] In some embodiments, the redundancy version of the PUSCH scheduled by the DCI can be determined based on the redundancy version field in the DCI, wherein the redundancy version used by the PUSCH repetition type A or PUSCH repetition type B scheduled by the DCI in the nth transmission can be determined according to Table 3 below:

[0355] Table 3

[0356]

[0357] In Table 3, rv idThis is a redundancy version identifier used to identify the redundant version used. N represents the nth transmission timing, and mod represents the modulo operation.

[0358] For PUSCH repetition Type A or PUSCH repetition Type B with configured grant, the redundant version used can be configured by the cell configuredGrantConfig->repK-RV IE. The cyclic order of the redundant versions can be configured as {0,2,3,1},{0,3,0,3},{0,0,0,0}. If repK-RV is not configured, the actual redundant version of the PUSCH transmitted is 0.

[0359] In the above embodiments, the relevant concepts involved in the embodiments of this application have been introduced. The solutions of the embodiments of this application will be described below with reference to the accompanying drawings.

[0360] In NTN, due to the limitations of ground terminal equipment and the long distance between the terminal equipment and the satellite (or high-altitude platform), the uplink communication link coverage is poor. Therefore, uplink transmission reliability and coverage can be improved by repeating PUSCH transmission, thereby increasing the success rate of uplink data transmission.

[0361] For each PUSCH transmission, the terminal device uses a corresponding redundant version to process the uplink data carried on the PUSCH to improve data transmission reliability. In the NTN network, the cell radius corresponding to network equipment at different orbital altitudes is different, which may be between hundreds and thousands of kilometers. A single cell needs to serve a large number of terminal devices with different service requirements. Therefore, while ensuring uplink coverage, system capacity also needs to be considered.

[0362] In NTN networks, a single cell needs to serve a large number of terminal devices, and limited time-frequency domain resources restrict the number of terminal devices that can simultaneously perform PUSCH retransmission. Related technologies can superimpose OCC sequences onto the PUSCH to achieve code division multiplexing for PUSCH retransmission. However, in current PUSCH retransmission mechanisms, directly superimposing OCC sequences results in different redundancy versions being used in different PUSCH retransmissions. Therefore, the orthogonality of uplink data between different terminal devices during PUSCH retransmission cannot be guaranteed, leading to interference between users and reduced system performance.

[0363] Based on this, embodiments of this application provide a communication method in which, during the process of repeated PUSCH transmission by a terminal device, multiple repeatedly transmitted PUSCHs are divided into at least one PUSCH group. The PUSCHs within the same PUSCH group use the same redundant version, ensuring that the data transmitted on the PUSCHs within the same group is identical. Then, an OCC sequence is superimposed on each PUSCH group. Since the data transmitted on the PUSCHs within the same group is identical, when multiple terminal devices perform repeated PUSCH transmissions on the same time-frequency domain resources, the uplink data transmitted by the multiple terminal devices based on PUSCHs can be guaranteed to be orthogonal, thereby avoiding mutual interference between different terminal devices and improving system capacity.

[0364] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0365] Figure 5 This is a signaling diagram of the communication method provided in the embodiments of this application, such as... Figure 5 As shown, the method includes:

[0366] S501, the network device sends configuration information to the terminal device. The configuration information is used to configure the terminal device to repeatedly transmit PUSCH.

[0367] The network device sends configuration information to the terminal device, and the terminal device receives the configuration information sent by the network device.

[0368] In the embodiments of this application, "send" and "receive" indicate the direction of signal transmission. For example, "sending configuration information to a terminal device" can be understood as the destination of the configuration information being the terminal device, which may include sending directly via the air interface or sending indirectly via the air interface from other units or modules. "Receiving configuration information from a network device" can be understood as the source of the configuration information being the network device, which may include receiving directly from the network device via the air interface or receiving indirectly from the network device via the air interface from other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface.

[0369] It is understandable that information may undergo necessary processing, such as encoding and modulation, before being sent from the source to the destination. Similarly, the destination, upon receiving information from the source, can also perform corresponding processing, such as decoding and demodulation, to interpret the valid information from the source. Similar expressions in this application can be understood in a similar way and will not be elaborated further.

[0370] This configuration information is used to configure the terminal device to repeatedly transmit PUSCH. For example, this configuration information can be used to indicate the number of times the terminal device repeatedly transmits PUSCH, to indicate the time-frequency domain resources used when the terminal device repeatedly transmits PUSCH, to indicate the redundant version of PUSCH used when the terminal device repeatedly transmits PUSCH, etc. This application embodiment does not limit this.

[0371] In some embodiments, the number of terminal devices can be one or more. If there are multiple terminal devices, the network device can send corresponding configuration information to each terminal device separately. The number of times different terminal devices repeatedly transmit PUSCH, the time-frequency domain resources used, the redundant version of PUSCH used, and other information may differ, therefore the configuration information corresponding to different terminal devices may also be different.

[0372] S502, the terminal device sends multiple PUSCHs to the network device according to the configuration information; wherein, the multiple PUSCHs are repeatedly transmitted PUSCHs, the multiple PUSCHs include at least one PUSCH group, the PUSCHs in the PUSCH group use the same redundant version; N OCC sequences are superimposed on the PUSCHs in the PUSCH group, where N is 0 or 1.

[0373] After receiving the configuration information, the terminal device sends multiple PUSCHs to the network device according to the configuration information. In this embodiment, the multiple PUSCHs are repeatedly transmitted PUSCHs. Specifically, the terminal device divides the multiple PUSCHs into at least one PUSCH group. For any given PUSCH group, the PUSCH group includes one or more PUSCHs. The PUSCHs within the same PUSCH group use the same redundant version, meaning that the data transmitted on the PUSCHs within the same PUSCH group is identical.

[0374] For any given PUSCH group, N OCC sequences are superimposed on the PUSCHs within that group, where N is either 0 or 1. N = 0 indicates that no OCC sequences are superimposed on the PUSCHs in that group, while N = 1 indicates that one OCC sequence is superimposed on the PUSCHs in that group. In other words, in some embodiments, for a given PUSCH group, either no OCC sequences are superimposed on the PUSCHs, or only one OCC sequence is superimposed; that is, the OCC sequences are superimposed on a per-PUSCH-group basis.

[0375] For example, terminal device A sends multiple PUSCHs to the network device, including PUSCH group 1 and PUSCH group 2. Terminal device B sends multiple PUSCHs to the network device, including PUSCH group 3. If the time domain resources of PUSCH group 1 and PUSCH group 3 are the same, and the frequency domain resources of PUSCH group 1 and PUSCH group 3 are also the same, then an OCC sequence x can be superimposed on the PUSCHs in PUSCH group 1, and an OCC sequence y can be superimposed on the PUSCHs in PUSCH group 3, where the OCC sequence x and OCC sequence y are orthogonal to each other.

[0376] Since PUSCH group 1 includes repeatedly transmitted PUSCHs, and the redundant versions of the PUSCHs in PUSCH group 1 are the same, and PUSCH group 3 also includes repeatedly transmitted PUSCHs, and the redundant versions of the PUSCHs in PUSCH group 3 are the same, and since OCC sequences x and y are orthogonal, the uplink data transmitted by terminal device A based on PUSCHs in PUSCH group 1 and the uplink data transmitted by terminal device B based on PUSCHs in PUSCH group 3 are orthogonal. Although PUSCH groups 1 and 3 use the same time-frequency domain resources, they are code-division multiplexed and will not interfere with each other. In this scenario, the value of N is 1 for both PUSCH groups 1 and 3.

[0377] The time-frequency domain resources of PUSCH group 2 are different from those of PUSCH group 3. Therefore, an OCC sequence can be superimposed on the PUSCH in PUSCH group 2, or no OCC sequence can be superimposed. That is, for PUSCH group 2, the value of N can be 0 or 1.

[0378] The communication method provided in this application embodiment involves a network device sending configuration information to a terminal device to configure the terminal device to repeatedly transmit PUSCH. The terminal device, based on this configuration information, sends multiple PUSCHs to the network device. These multiple PUSCHs are repeatedly transmitted PUSCHs, comprising at least one PUSCH group. The PUSCHs within a PUSCH group use the same redundant version, ensuring that the data transmitted on the PUSCHs within the same PUSCH group is identical. N OCC sequences, where N is 0 or 1, are superimposed on the PUSCHs within the PUSCH group. This embodiment of the application superimposes OCC sequences on PUSCH groups. Since the data transmitted on the PUSCHs within the same PUSCH group is identical, when multiple terminal devices repeatedly transmit PUSCHs on the same time-frequency domain resources, it ensures that the uplink data transmitted by the multiple terminal devices based on PUSCHs is orthogonal to each other. This avoids mutual interference between different terminal devices, achieving code division multiplexing between different terminal devices. While ensuring uplink coverage and reliability, it also improves system capacity.

[0379] The network device sends configuration information to the terminal device, which is used to configure the terminal device to repeatedly transmit PUSCH. In some embodiments, the configuration information includes at least one of the following 1.1 to 1.5:

[0380] 1.1 PUSCH Configuration Information

[0381] PUSCH configuration information is used to configure PUSCHs that are repeatedly transmitted, i.e., multiple PUSCHs that the terminal device needs to transmit repeatedly.

[0382] In some embodiments, the PUSCH configuration information includes at least one of the following ab:

[0383] a. The number of times the terminal device repeatedly transmits the PUSCH

[0384] The number of times a terminal device repeatedly transmits a PUSCH can be denoted as K, where K is a positive integer greater than 1. Therefore, the number of PUSCHs that the terminal device sends to the network device is also K.

[0385] b. Terminal devices repeatedly transmit PUSCH resources

[0386] The resources for repeated PUSCH transmissions by the terminal device can include time-domain resources and / or frequency-domain resources. The network device can configure the resources for each PUSCH transmission individually, or it can configure resources for a portion of the PUSCH transmissions and indicate the association between these resources and the resources for the remaining PUSCH transmissions. The terminal device can then determine the resources for the remaining PUSCH transmissions based on this association.

[0387] Taking time-domain resources as an example, if the transmission type of the terminal device when repeatedly transmitting PUSCH is PUSCH RepetitionType A, the network device can configure the starting symbol position and the symbol length occupied by the PUSCH. Since the symbol position occupied by the PUSCH is exactly the same in K time slots, the terminal device can determine the time-domain resources when transmitting each PUSCH based on the starting symbol position and the symbol length occupied.

[0388] Taking frequency domain resources as an example, if the terminal device does not send multiple PUSCHs based on frequency hopping, the frequency domain resources are the same for multiple PUSCH transmissions, and the network device can configure only one frequency domain resource. If the terminal device sends multiple PUSCHs based on frequency hopping, the frequency domain resources for multiple PUSCH transmissions are different. The network device can configure the starting frequency point and frequency hopping offset value for PUSCH transmission, and determine the frequency domain resources for each PUSCH transmission based on the starting frequency point and frequency hopping offset value.

[0389] 1.2 PUSCH Group Configuration Information

[0390] PUSCH group configuration information is used to configure at least one PUSCH group. At least one PUSCH group is obtained by dividing multiple PUSCHs that are repeatedly transmitted. For any PUSCH group within the at least one PUSCH group, the PUSCH group includes one or more PUSCHs. PUSCH group configuration information can be used to indicate how to divide the multiple PUSCHs that are repeatedly transmitted, such as the number of PUSCHs included in each PUSCH group, the number of PUSCH groups, the redundancy version of the PUSCHs used, and so on.

[0391] In some embodiments, the PUSCH group configuration information includes at least one of the following:

[0392] c. Number of at least one PUSCH group

[0393] The number of at least one PUSCH group refers to the number of PUSCH groups after dividing the multiple PUSCHs that are repeatedly transmitted into groups. The number of at least one PUSCH group is a positive integer greater than or equal to 1, such as 1, 2, 3, ... etc.

[0394] d. Number of PUSCHs in the PUSCH group

[0395] For any PUSCH group within at least one PUSCH group, the number of PUSCHs in that PUSCH group can be one or more. In some embodiments, the number of PUSCHs in different PUSCH groups can be equal, thereby reducing the complexity of network device configuration and demodulation. In some embodiments, the number of PUSCHs in different PUSCH groups can also be unequal, thereby enabling flexible configuration of multiple terminal devices for multiplexing, and allowing for reasonable allocation of transmission resources according to the transmission needs of multiple different terminal devices, which helps to improve system capacity and throughput.

[0396] Transmission sequence of e.PUSCH group

[0397] The transmission order of PUSCH groups, also known as the arrangement of PUSCH groups, the order of PUSCH groups, etc., refers to the sequential order between different PUSCH groups.

[0398] For example, if multiple PUSCHs are divided into 3 PUSCH groups, one PUSCH group has 2 PUSCHs, one PUSCH group has 1 PUSCH, and one PUSCH group has 4 PUSCHs, then the transmission order of the PUSCH groups can be, for example, 2-1-4 (meaning that the PUSCH group with 2 PUSCHs is transmitted first, then the PUSCH group with 1 PUSCH is transmitted, and finally the PUSCH group with 4 PUSCHs is transmitted), or 1-2-4 (meaning that the PUSCH group with 1 PUSCH is transmitted first, then the PUSCH group with 2 PUSCHs is transmitted, and finally the PUSCH group with 4 PUSCHs is transmitted), or 4-2-1 (meaning that the PUSCH group with 4 PUSCHs is transmitted first, then the PUSCH group with 2 PUSCHs is transmitted, and finally the PUSCH group with 1 PUSCH is transmitted), and so on.

[0399] In some embodiments, the division of PUSCH groups can be completed by determining the number of at least one PUSCH group, the number of PUSCHs in each PUSCH group, and the transmission order of the PUSCH groups. For example, if the number of at least one PUSCH group is 3, and the number of PUSCHs in the 3 PUSCH groups is 1, 2, and 4, the transmission order of the PUSCH groups may include, for example, 2-1-4. Then, the PUSCH transmitted in the first and second repeated transmissions belongs to the same PUSCH group, the PUSCH transmitted in the third repeated transmission belongs to another PUSCH group, and the PUSCH transmitted in the fourth to seventh repeated transmissions belong to the same PUSCH group.

[0400] f. Redundant version information for the PUSCH group

[0401] The redundancy version information of the PUSCH group is used to indicate the redundancy version used by the PUSCH in the PUSCH group. The PUSCH in the same PUSCH group uses the same redundancy version, while the PUSCH in different PUSCH groups can use the same or different redundancy versions.

[0402] In some embodiments, the redundancy version information of a PUSCH group can be the redundancy version used by the PUSCH in the PUSCH group, that is, the network device can directly configure the redundancy version used by the PUSCH in the PUSCH group through configuration information.

[0403] In some embodiments, the redundant version information of the PUSCH group can be, for example, the cyclic order of the redundant versions. The terminal device can determine the redundant version used by the PUSCH in each PUSCH group in turn according to the cyclic order of the redundant versions.

[0404] 1.3 Frequency Hopping Information

[0405] Frequency hopping information can be used to indicate whether the terminal device uses frequency hopping to transmit PUSCH. If frequency hopping is used to transmit PUSCH, frequency hopping information can also be used to indicate frequency hopping type, frequency hopping parameters, etc.

[0406] In some embodiments, frequency hopping information may include at least one of the following g to i:

[0407] g. First instruction information

[0408] The first indication information is used to indicate whether the terminal device repeatedly transmits PUSCH based on frequency hopping. If the terminal device does not repeatedly transmit PUSCH based on frequency hopping, the frequency domain resources used by the multiple PUSCHs repeatedly transmitted by the terminal device are the same; if the terminal device repeatedly transmits PUSCH based on frequency hopping, the frequency domain resources used by the multiple PUSCHs repeatedly transmitted by the terminal device are different.

[0409] h. Frequency hopping type

[0410] In some embodiments, the frequency hopping type may include at least one of the following: intra-slot frequency hopping type, inter-slot frequency hopping type, and inter-PUSCH group frequency hopping type.

[0411] Intra-slot frequency hopping refers to the transmission of PUSCH using frequency hopping within the same time slot. In other words, different PUSCHs transmitted within the same time slot use different frequency domain resources.

[0412] Inter-slot frequency hopping refers to the transmission of PUSCH using frequency hopping in different time slots. In other words, different PUSCH transmitted in different time slots use different frequency domain resources.

[0413] Inter-PUSCH frequency hopping refers to the use of frequency hopping to transmit PUSCH between different PUSCH groups. In other words, different PUSCH groups use different frequency domain resources.

[0414] i. Frequency hopping parameters, used to indicate the frequency domain resources of the PUSCH group.

[0415] When a terminal device repeatedly transmits PUSCHs using frequency hopping, the frequency hopping parameters are used to determine the frequency domain resources of a PUSCH group. For example, the frequency hopping parameters may include the starting position of the frequency domain resources of a PUSCH group, such as the frequency offset between the starting position of the frequency domain resources of this PUSCH group and the starting position of the frequency domain resources of another PUSCH group, etc. Based on the frequency hopping parameters, the frequency domain resources of each PUSCH group can be determined.

[0416] 1.4 OCC Configuration Information

[0417] OCC configuration information is used to configure the OCC sequences superimposed on the PUSCHs in a PUSCH group. For any given PUSCH group, there are N OCC sequences superimposed on the PUSCHs, where N is 0 or 1. The OCC configuration information may specify the value of N, the OCC sequence superimposed on the PUSCHs in the PUSCH group, the length of the OCC sequence, the index of the OCC sequence, and so on.

[0418] In some embodiments, the OCC configuration information may include at least one of the following j to n:

[0419] j. Second instruction information

[0420] The second indication information is used to indicate whether an OCC sequence is superimposed on the PUSCH in the PUSCH group, that is, the corresponding N value is 0 or 1.

[0421] In some embodiments, for a certain PUSCH group that a terminal device needs to transmit, if the time-frequency domain resources of the PUSCH group conflict with the time-frequency domain resources of the PUSCH group transmitted by another terminal device, that is, the two terminal devices reuse the time-frequency domain resources to repeatedly transmit PUSCH, then OCC sequences need to be superimposed on the PUSCH in the two PUSCH groups, and the OCC sequences superimposed on the PUSCH in the two PUSCH groups are orthogonal to each other, thereby realizing code division multiplexing.

[0422] In some embodiments, for a certain PUSCH group that a terminal device needs to transmit, if the time-frequency domain resources of the PUSCH group do not overlap with the time-frequency domain resources of the PUSCH group transmitted by other terminal devices, then there are no other terminal devices that reuse the time-frequency domain resources to repeatedly transmit PUSCH with the terminal device, and the PUSCH of the PUSCH group may not be superimposed with an OCC sequence.

[0423] Network devices can determine whether time-frequency domain resources need to be reused based on the time-frequency domain resources of each PUSCH group, thereby determining whether OCC sequences need to be superimposed on the PUSCHs in each PUSCH group.

[0424] k. Length of the OCC sequence.

[0425] The length of an OCC sequence refers to the length of each codeword in a set of OCC sequences. The length of the OCC sequence determines the number and capability of different ports, terminal devices, or antennas that the OCC sequence can distinguish in the code domain. Typically, the length of the OCC sequence is determined based on the actual system requirements to ensure the orthogonality of the PUSCH during transmission and avoid mutual interference.

[0426] In some embodiments, for any given PUSCH group, the length of the OCC sequence superimposed on the PUSCHs in that PUSCH group is equal to the number of PUSCHs in that PUSCH group.

[0427] For example, if a PUSCH group includes two PUSCHs that are transmitted repeatedly, then the OCC sequence superimposed on the PUSCHs in the PUSCH group has a length of 2. The OCC sequence with a length of 2 can include, for example, [+1,+1], [+1,-1], etc.

[0428] For example, if a PUSCH group includes 4 repeatedly transmitted PUSCHs, then the OCC sequence superimposed on the PUSCHs in the PUSCH group has a length of 4. The OCC sequence of length 4 can include, for example, [+1,+1,+1,+1], [+1,-1,+1,-1], [+1,+1,-1,-1], [+1,-1,-1,+1], etc.

[0429] l. Index of the OCC sequence

[0430] The index of an OCC sequence, also known as the identifier of an OCC sequence or the OCC codeword index, is used to identify the corresponding OCC sequence among multiple OCC sequences.

[0431] For example, the index of an OCC sequence can be the index of the OCC sequence in an OCC sequence table. One form of an OCC sequence table is, for example, the form of Table 1 above. In this case, the index of the OCC sequence is n in Table 1. Each value of n corresponds to an OCC sequence. Once the value of n is determined, the corresponding OCC sequence can be determined.

[0432] For example, the index of an OCC sequence can be the index of the OCC sequence in an OCC sequence set, which includes multiple OCC sequences. In some embodiments, the OCC sequence set can be in the form of an OCC sequence table, or other forms, which are not limited in this application embodiment. In some embodiments, the OCC sequence set can also be a set of multiple predefined OCC sequences, or a set of multiple OCC sequences configured by a network device, etc.

[0433] How the m.OCC sequence is generated

[0434] The method of generating OCC sequences, also known as the OCC scheme, refers to how to determine the OCC sequence to be superimposed on the PUSCH in the PUSCH group. Terminal devices can generate corresponding OCC sequences based on this method, and then superimpose the OCC sequence on the PUSCH in the corresponding PUSCH group.

[0435] In some embodiments, the OCC sequence superimposed on the PUSCHs in a PUSCH group is determined based on configuration information and / or a predefined method. The predefined method may be, for example, a predefined formula or a predefined association relationship, etc.

[0436] For example, the OCC sequence is generated by determining it from the OCC sequence set based on its index. Specifically, the network device sends configuration information to the terminal device, which includes the index of the OCC sequence. The terminal device can then determine the OCC sequence from the OCC sequence set based on the index.

[0437] For example, the generation method of the OCC sequence is determined based on a predefined formula and parameters in the configuration information. For instance, the configuration information includes the length N and phase parameter Φ(m) of the OCC sequence, thereby generating an OCC sequence of the corresponding length based on the following predefined formula:

[0438] w(m)=e j2πΦ(m) / N m = 0, 1, 2, ..., N

[0439] Where w(m) is the OCC sequence.

[0440] For example, an OCC sequence table can be predefined, which contains parameter values ​​corresponding to different indices at different lengths. Then, the corresponding parameter values ​​are indicated by the configuration information, and the corresponding parameters can be obtained by looking up the table. Then, the corresponding OCC sequence can be obtained by substituting it into the predefined formula.

[0441] An example of a table is shown in Table 4 below.

[0442] Table 4

[0443]

[0444] Given index i and OCC sequence length N, obtain the sequence corresponding to Φ(m), and then use the following formula to generate an OCC sequence of length N:

[0445] w i (m)=e j2πΦ(m) / N m = 0, 1, 2, ..., N

[0446] Among them, w i (m) is an OCC sequence.

[0447] In some embodiments, the network device may also directly indicate the OCC sequence superimposed on the PUSCH in the PUSCH group in the configuration information. For example, an OCC sequence of length 4 can be configured in the RRC message. For example, an OCC sequence of length 4 can be [+1 -1+1 -1].

[0448] n. OCC sequence set.

[0449] An OCC sequence set is a collection of one or more OCC sequences. In some embodiments, the OCC sequence set may be in the form of an OCC sequence table (e.g., an OCC codeword table), or other forms, which are not limited in this application. In some embodiments, the OCC sequence set may also be a collection of predefined OCC sequences, or a collection of multiple OCC sequences configured by a network device, etc.

[0450] 1.5 UCI Indication Information

[0451] UCI indication information is used to indicate whether UCI multiplexing is allowed on repeatedly transmitted PUSCH.

[0452] UCI includes Hybrid Automatic Repeat Request Acknowledge (HARQ-ACK), Channel State Information (CSI), and Scheduling Request (SR). HARQ-ACK and CSI can be transmitted on the PUCCH or multiplexed onto the PUSCH. CSI consists of two parts: CSI part 1 has a fixed payload size, indicating the number of CSI information bits in CSI part 2, and CSI part 1 must be transmitted in its entirety. When UCI is multiplexed onto the PUSCH, HARQ-ACK is mapped onto consecutive OFDM symbols after the first DMRS on the PUSCH, while CSI part 1 or CSI part 2 starts mapping from the first symbol not used for DMRS. If the number of bits in HARQ-ACK is less than or equal to 2, HARQ-ACK uses puncturing; otherwise, it uses rate matching.

[0453] If the UCI indication information indicates that UCI multiplexing is permitted on a repeatedly transmitted PUSCH, then in the event of a resource conflict between UCI and repeatedly transmitted PUSCH, UCI can be transmitted on the repeatedly transmitted PUSCH. In other words, in this case, UCI is not transmitted on the PUCCH, but rather on the PUSCH.

[0454] If the UCI indication information indicates that UCI multiplexing is not allowed on a repeatedly transmitted PUSCH, then UCI cannot be carried on a repeatedly transmitted PUSCH if there is a conflict between the resources of UCI and the resources of the repeatedly transmitted PUSCH.

[0455] In some embodiments, for any first PUSCH group and second PUSCH group in at least one PUSCH group, if a first OCC sequence is superimposed on the PUSCH in the first PUSCH group and a second OCC sequence is superimposed on the PUSCH in the second PUSCH group, then the first OCC sequence and the second OCC sequence satisfy at least one of the following 2.1 to 2.5:

[0456] 2.1 The first OCC sequence and the second OCC sequence are the same OCC sequence.

[0457] In other words, for any two PUSCH groups, the OCC sequences superimposed on the PUSCHs in these two PUSCH groups can be the same. The same OCC sequence can be, for example, the same OCC sequence from the same OCC sequence set, or an OCC sequence generated using the same generation method and parameters, and so on.

[0458] 2.2 The first OCC sequence and the second OCC sequence belong to different sets of OCC sequences.

[0459] The first OCC sequence and the second OCC sequence belong to different sets of OCC sequences. For example, the first OCC sequence belongs to a set of OCC sequences of length 2, and the second OCC sequence belongs to a set of OCC sequences of length 4. If the first OCC sequence and the second OCC sequence belong to different sets of OCC sequences, the first OCC sequence and the second OCC sequence can be the same OCC sequence or they can be different OCC sequences.

[0460] 2.3 The first OCC sequence and the second OCC sequence belong to different indexes of the same OCC sequence set.

[0461] If the first OCC sequence and the second OCC sequence belong to different indexes of the same OCC sequence set, then the first OCC sequence and the second OCC sequence belong to different OCC sequences.

[0462] 2.4 The first OCC sequence is generated in the same way as the second OCC sequence, but the generation parameters used for the first OCC sequence are different from those used for the second OCC sequence.

[0463] The generation method of the OCC sequence can be determined based on configuration information, a predefined method, or a combination of configuration information and a predefined method, etc. If the generation method of the first OCC sequence is the same as that of the second OCC sequence, but the generation parameters used by the first OCC sequence and the second OCC sequence are different, then the first OCC sequence and the second OCC sequence are different OCC sequences.

[0464] 2.5 The generation methods of the first OCC sequence and the second OCC sequence are different.

[0465] The generation method of the OCC sequence can be determined based on configuration information, a predefined method, or a combination of configuration information and a predefined method, etc. If the generation methods of the first OCC sequence and the second OCC sequence are different, the first OCC sequence and the second OCC sequence can be the same OCC sequence or different OCC sequences.

[0466] In some embodiments, for any PUSCH group, the redundant versions of the PUSCHs in that PUSCH group are determined based on at least one of the following: configuration information, the index of the PUSCH group, the transmission order of the PUSCH group, and the cyclic order of the redundant versions.

[0467] For example, the configuration information includes redundancy version information for PUSCH groups. This redundancy version information indicates the redundancy version used by the PUSCHs in each PUSCH group. For instance, multiple PUSCHs repeatedly transmitted by the terminal device may include PUSCH group 1, PUSCH group 2, and PUSCH group 3. The redundancy version information of the PUSCH groups indicates that the PUSCHs in PUSCH group 1 use redundancy version 0, the PUSCHs in PUSCH group 2 use redundancy version 2, the PUSCHs in PUSCH group 3 use redundancy version 3, and so on.

[0468] For example, if the cyclic order of the redundancy versions is 0, 2, 3, 1, and the terminal device repeatedly transmits multiple PUSCHs including PUSCH group 1, PUSCH group 2, and PUSCH group 3, then starting from redundancy version 0, the PUSCHs in PUSCH group 1 use redundancy version 0, the PUSCHs in PUSCH group 2 use redundancy version 2, the PUSCHs in PUSCH group 3 use redundancy version 3, and so on.

[0469] For example, the cycle order of the redundant versions is 0, 2, 3, 1. The multiple PUSCHs repeatedly transmitted by the terminal device include PUSCH group 1, PUSCH group 2 and PUSCH group 3. The starting version of the redundant version cycle is determined according to the index of the PUSCH group or the transmission order of the PUSCH group. Then, the cycle is performed according to the cycle order of the redundant versions to obtain the redundant version used by the PUSCH in each PUSCH group.

[0470] For example, the redundancy version cycle order is 0, 2, 3, 1. The terminal device repeatedly transmits multiple PUSCHs, including PUSCH group 1, PUSCH group 2, and PUSCH group 3. Configuration information can indicate the starting version for the redundancy version cycle. Taking the starting redundancy version as 2 as an example, the cycle is performed according to the redundancy version cycle order to obtain the redundancy version used by the PUSCHs in each PUSCH group. Thus, starting with redundancy version 2, the PUSCHs in PUSCH group 1 use redundancy version 2, the PUSCHs in PUSCH group 2 use redundancy version 3, the PUSCHs in PUSCH group 3 use redundancy version 1, and so on.

[0471] In the above embodiments, the contents of the configuration information have been described. The following describes the solution of the embodiments of this application with reference to the accompanying drawings.

[0472] Figure 6 This is a schematic diagram of PUSCH retransmission provided in the embodiments of this application. Figure 1 ,like Figure 6 As shown, this example illustrates the case of four terminal devices performing repeated PUSCH transmissions: terminal device #1, terminal device #2, terminal device #3, and terminal device #4.

[0473] The four terminal devices retransmit PUSCH repeatedly on some of the same time-frequency resources using PUSCH repetition Type A, meaning that PUSCH is retransmitted repeatedly in units of time slots. For any given terminal device, the PUSCH retransmitted by that terminal device is divided into at least one PUSCH group, and the PUSCH within the same PUSCH group uses the same redundant version.

[0474] The network device configures corresponding configuration information for each terminal device based on the number of terminal devices that need to be reused on the same time-frequency resources, channel status information, system performance requirements, etc. The content of the configuration information can be found in the relevant descriptions in 1.1 to 1.5 of the above embodiments, and will not be repeated here.

[0475] For any given terminal device, the configuration information sent by the network device is used to configure the terminal device to repeatedly transmit PUSCH. Based on this configuration information, the terminal device can determine at least the number of PUSCH groups, the redundant versions of the PUSCHs within each group, whether OCC sequences are superimposed on the PUSCHs, whether frequency hopping is used for PUSCH retransmission, whether UCI multiplexing is performed on the retransmitted PUSCHs, and so on. Then, based on this information, the terminal device generates the corresponding data stream (if OCC sequences need to be superimposed on the PUSCHs in the PUSCH group, then the OCC sequences are superimposed), maps it to the PUSCH resources, and sends it to the network device, thereby completing K retransmissions of PUSCHs in the form of PUSCH groups, where K is the number of times the terminal device retransmits PUSCHs, and K is a positive integer.

[0476] K can be directly configured by the network device (e.g., the configuration information sent by the network device to the terminal device includes the number of times the terminal device repeatedly transmits PUSCH), or it can be calculated based on the relevant parameters in the PUSCH group configuration information of the network device. For example, if the PUSCH group configuration information includes the number of at least one PUSCH group, the number of PUSCHs in the PUSCH group, and the number of at least one PUSCH group is 5, and the number of PUSCHs in the 5 PUSCH groups is [2, 4, 4, 1, 1] respectively, then K is equal to the cumulative value of the number of PUSCHs in all PUSCH groups, which is 12.

[0477] exist Figure 6 In the example, each box represents one PUSCH transmission. Terminal device #1 transmits PUSCH 12 times. These 12 PUSCH transmissions are divided into 5 PUSCH groups: group11, group12, group13, group14, and group15. The number of PUSCHs in each PUSCH group is 2, 4, 4, 1, and 1, respectively. The redundant versions of the PUSCHs in each PUSCH group are RV0, RV2, RV3, RV1, and RV0, respectively.

[0478] Terminal device #2 transmits PUSCH 4 times. The 4 PUSCH transmissions are divided into 2 PUSCH groups, namely group21 and group22. The number of PUSCHs in each PUSCH group is 2 and 2 respectively. The redundant versions of PUSCHs in each PUSCH group are RV0 and RV2 respectively.

[0479] Terminal device #3 repeatedly transmits PUSCH 8 times. The 8 repeated PUSCH transmissions are divided into 2 PUSCH groups, namely group31 and group32. The number of PUSCHs in each PUSCH group is 4 and 4 respectively. The redundant versions of PUSCHs in each PUSCH group are RV0 and RV3 respectively.

[0480] Terminal device #4 transmits PUSCH 4 times. The 4 PUSCH transmissions are divided into 1 PUSCH group, which is group41. The number of PUSCHs in the PUSCH group is 4. The redundant versions of the PUSCHs in the PUSCH group are RV0 in sequence.

[0481] In some embodiments, for any given terminal device, the PUSCHs repeatedly transmitted by that terminal device can be divided into multiple PUSCH groups of the same length, meaning that the number of PUSCHs in different PUSCH groups is the same. Multiple PUSCH groups can use the same OCC sequence, meaning that the OCC sequences superimposed on the PUSCHs in multiple PUSCH groups are identical.

[0482] by Figure 6 For example, targeting Figure 6 Terminal device #2 transmits PUSCH 4 times. These 4 PUSCH transmissions are divided into 2 PUSCH groups, each containing 2 PUSCHs. The OCC sequence superimposed on the PUSCHs in group 21 is [+1,-1], and the OCC sequence superimposed on the PUSCHs in group 22 is also [+1,-1]. In other words, the OCC sequences superimposed on the PUSCHs in group 21 and group 22 are identical.

[0483] by Figure 6 For example, targeting Figure 6 Terminal device #3 transmits PUSCH 8 times. These 8 PUSCH transmissions are divided into 2 PUSCH groups, each containing 4 PUSCHs. The OCC sequence superimposed on the PUSCHs in group 31 is [+1,+1,-1,-1], and the OCC sequence superimposed on the PUSCHs in group 32 is also [+1,+1,-1,-1]. In other words, the OCC sequences superimposed on the PUSCHs in group 31 and group 32 are identical.

[0484] By adopting the above configuration method (i.e., the number of PUSCHs in different PUSCH groups is the same, and the OCC sequence superimposed on the PUSCHs in multiple PUSCH groups is the same), the processing complexity of network devices and terminal devices is low, which can improve processing efficiency.

[0485] In some embodiments, for any given terminal device, the PUSCH repeatedly transmitted by that terminal device can be divided into multiple PUSCH groups of different lengths, meaning the number of PUSCHs in different PUSCH groups is different. Multiple PUSCH groups can use different OCC sequences, meaning the OCC sequences superimposed on the PUSCHs in multiple PUSCH groups are different. In some embodiments, if a PUSCH group transmitted by the terminal device does not share time-frequency domain resources with PUSCH groups transmitted by other terminal devices, then an OCC sequence may or may not be superimposed on the PUSCHs in that PUSCH group.

[0486] by Figure 6 For example, targeting Figure 6 Terminal device #1 transmits PUSCH 12 times. These 12 PUSCH transmissions are divided into 5 PUSCH groups, with the number of PUSCHs in each group not being exactly equal: 2, 4, 4, 1, 1. Specifically, the OCC sequence superimposed on the PUSCH in group 11 is [+1,+1], in group 12 it is [+1,+1,+1,+1], and in group 13 it is [+1,-1,+1,-1]. That is, the OCC sequences superimposed on the PUSCHs in group 11, group 12, and group 13 are different.

[0487] For groups 14 and 15, since no other terminal devices transmit PUSCH when terminal device #1 transmits PUSCH in group 14, meaning no other terminal device reuses the time-frequency domain resources of group 14 and group 15, the PUSCH in group 14 does not need to be superimposed with an OCC sequence, and the PUSCH in group 15 also does not need to be superimposed with an OCC sequence.

[0488] By adopting the above configuration method (i.e., different numbers of PUSCHs in different PUSCH groups, and different OCC sequences superimposed on the PUSCHs in multiple PUSCH groups), resources can be reasonably allocated according to the transmission needs of different terminal devices, and multiple terminal devices can be flexibly configured for multiplexing, thereby effectively improving system capacity and throughput.

[0489] In some embodiments, the multiple PUSCHs that are repeatedly transmitted include at least a fifth PUSCH group sent by a first terminal device and a sixth PUSCH group sent by a second terminal device, wherein a third OCC sequence is superimposed on the PUSCHs in the fifth PUSCH group, and a fourth OCC sequence is superimposed on the PUSCHs in the sixth PUSCH group. Then:

[0490] The resources of the fifth PUSCH group are the same as those of the sixth PUSCH group, and the third OCC sequence and the fourth OCC sequence are orthogonal to each other.

[0491] or,

[0492] The resources of the first PUSCH sequence are the same as those of the second PUSCH sequence. The first PUSCH sequence has a first OCC subsequence superimposed on the PUSCH, and the second PUSCH sequence has a second OCC subsequence superimposed on the PUSCH. The first OCC subsequence and the second OCC subsequence are orthogonal to each other.

[0493] The first PUSCH sequence is a subset of the fifth PUSCH group, the second PUSCH sequence is a subset of the sixth PUSCH group, the first OCC subsequence is a subset of the third OCC sequence, and the second OCC subsequence is a subset of the fourth OCC sequence.

[0494] For example, since the resources of the fifth PUSCH group are the same as those of the sixth PUSCH group, the network device needs to configure mutually orthogonal third and fourth OCC sequences. This allows the first terminal device to superimpose the third OCC sequence onto the PUSCHs in the fifth PUSCH group, and the second terminal device to superimpose the fourth OCC sequence onto the PUSCHs in the sixth PUSCH group, thus achieving code division multiplexing. Through this processing method, the first terminal device will not interfere with each other when sending PUSCHs from the fifth PUSCH group, and the second terminal device will not interfere with each other when sending PUSCHs from the sixth PUSCH group.

[0495] For example, since the resources of the first PUSCH sequence are the same as those of the second PUSCH sequence, the network device needs to configure a third OCC sequence and a fourth OCC sequence. The third OCC sequence includes a first OCC subsequence, and the fourth OCC sequence includes a second OCC subsequence, with the first and second OCC subsequences being orthogonal to each other. Then, the first terminal device superimposes the third OCC sequence onto the PUSCHs in the fifth PUSCH group, and the second terminal device superimposes the fourth OCC sequence onto the PUSCHs in the sixth PUSCH group, thus achieving code division multiplexing. Through this processing method, when the first terminal device transmits PUSCHs in the fifth PUSCH group, and when the second terminal device transmits PUSCHs in the sixth PUSCH group, there will be no mutual interference between the first and second PUSCH sequences.

[0496] In some embodiments, the third OCC sequence and the fourth OCC sequence satisfy at least one of the following conditions 3.1 to 3.4:

[0497] 3.1 The third OCC sequence and the fourth OCC sequence belong to different sets of OCC sequences.

[0498] The third and fourth OCC sequences belong to different sets of OCC sequences. For example, the third OCC sequence belongs to a set of OCC sequences of length 2, and the fourth OCC sequence belongs to a set of OCC sequences of length 4. If the third and fourth OCC sequences belong to different sets of OCC sequences, then the third and fourth OCC sequences are different OCC sequences.

[0499] 3.2 The third OCC sequence and the fourth OCC sequence belong to different indexes of the same OCC sequence set.

[0500] If the third OCC sequence and the fourth OCC sequence belong to different indexes of the same OCC sequence set, then the third OCC sequence and the fourth OCC sequence belong to different OCC sequences.

[0501] 3.3 The generation method of the third OCC sequence is the same as that of the fourth OCC sequence, but the generation parameters used for the third OCC sequence are different from those used for the fourth OCC sequence.

[0502] The generation method of an OCC sequence can be determined based on configuration information, a predefined method, or a combination of configuration information and a predefined method, etc. If the generation method of the third OCC sequence is the same as that of the fourth OCC sequence, but the generation parameters used in the third OCC sequence are different from those used in the fourth OCC sequence, then the third OCC sequence and the fourth OCC sequence are different OCC sequences.

[0503] 3.4 The generation methods of the third OCC sequence and the fourth OCC sequence are different.

[0504] The generation method of the OCC sequence can be determined based on configuration information, a predefined method, or a combination of configuration information and a predefined method, etc. If the generation methods of the third OCC sequence and the fourth OCC sequence are different, the third OCC sequence and the fourth OCC sequence are different OCC sequences.

[0505] Different OCC sequences can be reused across different terminal devices. This process can be found in [reference needed]. Figure 6 Examples, such as Figure 6 As shown, the resources used by groups 12, 22, and 31 conflict. Reuse can be achieved by overlaying OCC sequences onto the PUSCH in groups 12, 22, and 31. Specifically, the OCC sequence overlaid on the PUSCH in group 12 is [+1,+1,+1,+1] with a length of 4; the OCC sequence overlaid on the PUSCH in group 22 is [+1,-1] with a length of 2; and the OCC sequence overlaid on the PUSCH in group 31 is [+1,+1,-1,-1] with a length of 4.

[0506] Specifically, the OCC sequences superimposed on the PUSCH in group12 are orthogonal to the OCC sequences superimposed on the PUSCH in group31; the first two terms of the OCC sequences superimposed on the PUSCH in group12 are orthogonal to the OCC sequences superimposed on the PUSCH in group22; and the first two terms of the OCC sequences superimposed on the PUSCH in group31 are orthogonal to the OCC sequences superimposed on the PUSCH in group22.

[0507] Multiplexing among users with different OCC sequence lengths can improve the flexibility of network device scheduling and the flexibility of multiplexing when scheduling different terminal devices to transmit PUSCH groups.

[0508] In some embodiments, multiple PUSCHs that a terminal device needs to repeatedly transmit can be divided into multiple PUSCH groups, and these multiple PUSCH groups can be multiplexed with PUSCHs repeatedly transmitted by other different terminal devices. Figure 6 For example, regarding terminal device #1, there is multiplexing between group11 transmitted by terminal device #1 and group21 transmitted by terminal device #2; there is multiplexing between group12 transmitted by terminal device #1, group22 transmitted by terminal device #2, and group31 transmitted by terminal device #2; there is multiplexing between group13 transmitted by terminal device #1, group32 transmitted by terminal device #3, and group41 transmitted by terminal device #4, and so on.

[0509] The above processing method allows network devices to flexibly configure multiplexing methods among multiple terminal devices according to the transmission needs of different terminal devices, effectively improving system capacity and throughput.

[0510] In some embodiments, configuration information may be carried in at least one of the following signaling methods: DCI, medium access control-control element (MAC CE), or RRC message.

[0511] In some embodiments, configuration information is carried in RRC messages, meaning that network devices can carry configuration information through RRC messages. RRC messages may include, for example, at least one of the following: PUSCH configuration information, PUSCH group configuration information, frequency hopping information, OCC configuration information, and UCI indication information. For a detailed description of the above information, please refer to the relevant content in 1.1 to 1.5 of the above embodiments, which will not be repeated here.

[0512] For example, network devices can carry configuration information in RRC messages (such as RRC IE PUSCH-TimeDomainResourceAllocation). This information may include the resource location for repeated PUSCH transmissions by the terminal device, and the number of times the terminal device repeatedly transmits the PUSCH (numberOfRepetitionsExt-r17) is configured as n12. Network devices can also carry PUSCH group configuration information, OCC configuration information, and so on, in the RRC IE PUSCH-TimeDomainResourceAllocation message.

[0513] For example, the information carried in RRC IE PUSCH-TimeDomainResourceAllocation may include:

[0514] The number of at least one PUSCH group: numberOfRepetitionGroups = n5 (meaning the number of at least one PUSCH group is n5);

[0515] The number of PUSCHs in each PUSCH group: sizeOfRepetitionGroups = n2-n4-n4-n1-n1 (meaning the number of PUSCHs in the 5 PUSCH groups is n2, n4, n4, n1, n1 respectively);

[0516] The length of the OCC sequence superimposed on the PUSCH in each PUSCH group: OCC-lengthOfRepetitionGroups=len2-len4-len4-no-no (meaning that the length of the OCC sequence superimposed on the PUSCH in the 1st PUSCH group is len2, the length of the OCC sequence superimposed on the PUSCH in the 2nd PUSCH group is len4, the length of the OCC sequence superimposed on the PUSCH in the 3rd PUSCH group is len4, and no OCC sequence is superimposed on the PUSCH in the 4th PUSCH group and the PUSCH in the 5th PUSCH group).

[0517] The index of the OCC sequence superimposed on the PUSCH in each PUSCH group: OCC-indexOfRepetitionGroups = [0 0 1]; where the OCC sequence can be determined by looking up the corresponding table according to the configured OCC sequence length and OCC sequence index.

[0518] The above-mentioned scheme for carrying configuration information can configure rich parameters based on RRC messages, thereby helping terminal devices to send multiple PUSCHs to network devices according to the configuration information.

[0519] In some embodiments, multiple combinations of relevant parameters can be configured via RRC messages, and then the specific combination of parameters used by the terminal device can be indicated via MAC CE or DCI.

[0520] For example, taking terminal device #1 as an example, the network device can configure parameters related to repeated PUSCH transmission in the RRC message (e.g., RRC IE PUSCH-TimeDomainResourceAllocation), such as the resource location for repeated PUSCH transmission by the terminal device, and the number of times the terminal device repeatedly transmits the PUSCH (numberOfRepetitionsExt-r17) is configured as n12. A PUSCH group configuration information list is added to the RRC IE PUSCH-TimeDomainResourceAllocation, which contains parameters related to OCC configuration information, for example:

[0521] The length of the PUSCH group configuration list: sizeOfRepetitionGroupConfigList = n10 (meaning that a total of n10 groups of related parameter configurations were configured via RRC messages);

[0522] PUSCH Group Configuration 0: RepetitionGroupConfig0

[0523] {

[0524] sizeOfRepetitionGroup = 1

[0525] OCC-lengthOfRepetitionGroup=no-CDM

[0526] OCC-indexOfRepetitionGroup=no

[0527] }

[0528] Where sizeOfRepetitionGroup is the number of at least one PUSCH group, OCC-lengthOfRepetitionGroup is the length of the OCC sequence superimposed on the PUSCH in the PUSCH group, OCC-indexOfRepetitionGroup is the index of the OCC sequence superimposed on the PUSCH in the PUSCH group, and no / no-CDM indicates that it is not configured.

[0529] For example, PUSCH group configuration 1: RepetitionGroupConfig1

[0530] {

[0531] sizeOfRepetitionGroup = n2

[0532] OCC-lengthOfRepetitionGroup=len2

[0533] OCC-indexOfRepetitionGroup=0

[0534] }

[0535] For example, PUSCH group configuration 2: RepetitionGroupConfig2

[0536] {

[0537] sizeOfRepetitionGroup = n4

[0538] OCC-lengthOfRepetitionGroup=len4

[0539] OCC-indexOfRepetitionGroup=0

[0540] }

[0541] For example, PUSCH group configuration 3: RepetitionGroupConfig3

[0542] {

[0543] sizeOfRepetitionGroup = n4

[0544] OCC-lengthOfRepetitionGroup=len4

[0545] OCC-indexOfRepetitionGroup=2

[0546] }......

[0547] For example, PUSCH group configuration 9: RepetitionGroupConfig9

[0548] {

[0549] sizeOfRepetitionGroup = n8

[0550] OCC-lengthOfRepetitionGroup=len8

[0551] OCC-indexOfRepetitionGroup=4

[0552] }

[0553] Then, the DCI indicates the PUSCH group used by terminal device #1. For example, it indicates that the number of PUSCH groups is 5, and the index combination of the OCC sequences superimposed on the PUSCHs in the PUSCH group is configured as 12300, and so on.

[0554] The above configuration method allows for a rich and flexible combination of parameters, and can quickly adjust the configuration according to the needs of different terminal devices with less MAC CE or DCI overhead.

[0555] In some embodiments, some parameters in the configuration information can be carried through RRC messages, while other parameters in the configuration information can be carried through MAC CE or DCI.

[0556] In some embodiments, all parameters in the configuration information can also be carried through MAC CE or DCI.

[0557] The above configuration method takes effect quickly and can be flexibly adjusted according to real-time needs.

[0558] In some embodiments, if a terminal device sends multiple PUSCHs to a network device based on frequency hopping, the multiple PUSCHs include at least one PUSCH group, and an OCC sequence is superimposed on the PUSCHs in the PUSCH group, then the frequency hopping type used by the multiple PUSCHs is the inter-PUSCH group frequency hopping type.

[0559] In some embodiments, the frequency domain resources of a PUSCH group are determined based on the PUSCH group index. For example, if the index of a PUSCH group is odd, then the initial frequency domain resources of that PUSCH group are RB. start If the index of a PUSCH group is even, then the starting frequency domain resource of that PUSCH group is RB. start +RB offset For example, if the index of a PUSCH group is even, then the starting frequency domain resource of that PUSCH group is RB. start If the index of a PUSCH group is odd, then the initial frequency domain resource of that PUSCH group is RB. start +RB offset .

[0560] Figure 7 A schematic diagram of PUSCH retransmission provided in the embodiments of this application. Figure 2 ,like Figure 7The illustration shows a scenario where a terminal device performs PUSCH repetition. This terminal device performs PUSCH repetition using PUSCH repetition Type A, meaning that PUSCH is repetitively transmitted in units of time slots. The PUSCHs repetitively transmitted by this terminal device are divided into at least one PUSCH group, and the PUSCHs within the same PUSCH group use the same redundant version.

[0561] The network device configures corresponding configuration information for each terminal device based on the number of terminal devices that need to be reused on the same time-frequency resources, channel status information, system performance requirements, etc. The content of the configuration information can be found in the relevant descriptions in 1.1 to 1.5 of the above embodiments, and will not be repeated here.

[0562] exist Figure 7 In the example, each box represents a PUSCH transmission. The terminal device transmits PUSCH 12 times. The 12 PUSCH transmissions are divided into 5 PUSCH groups: group11, group12, group13, group14, and group15. The number of PUSCHs in each PUSCH group is 2, 4, 4, 1, and 1, respectively.

[0563] The redundant version's cyclic order is {0, 2, 3, 1}, with an initial RV of 0. Therefore, the PUSCH in group11 uses redundant version 0, and the length of the OCC sequence superimposed on the PUSCH is 2. Figure 7 In the example, the OCC sequence superimposed on the PUSCH in group11 is [+1+1]; the redundant version of the PUSCH in group12 is version 2, and the length of the OCC sequence superimposed on the PUSCH is 4. Figure 7 In the example, the OCC sequence superimposed on the PUSCH in group12 is [+1+1+1+1]; the PUSCH in group13 uses the redundancy version 3, and the length of the OCC sequence superimposed on the PUSCH is 4. Figure 7 In the example, the OCC sequence superimposed on the PUSCH in group13 is [+1 -1+1 -1]; the PUSCH in group14 uses the redundant version 1, and no OCC sequence is superimposed on the PUSCH in group14; the PUSCH in group15 uses the redundant version 0, and no OCC sequence is superimposed on the PUSCH in group15.

[0564] like Figure 7As shown, the terminal device sends multiple PUSCHs to the network device according to the configuration information. The PUSCHs in a PUSCH group use the same redundant version, and the redundant versions are cyclical according to the PUSCH group index. Frequency hopping can be performed on a PUSCH group basis. The starting position of the frequency domain resources transmitted in each PUSCH group is calculated according to the following formula:

[0565]

[0566] For PUSCH groups with odd indices, the starting position in the frequency domain is RB. start For PUSCH groups with even indices, the starting position in the frequency domain is RB. start +RB offset .

[0567] in, The bandwidth part (BWP) width, n PUSCH-repetition-group This is the index for the PUSCH group. If the PUSCH group configuration method is to configure only one PUSCH group size or OCC sequence length N for a single terminal device... repetition-group Exemplary in To round down, k is the kth repeated PUSCH.

[0568] In the embodiments of this application, by configuring an appropriate frequency hopping type, such as configuring at least one PUSCH group with superimposed OCC sequences as inter-PUSCH group frequency hopping, frequency selective gain and randomized interference are obtained, while ensuring that a PUSCH group transmits exactly the same data on the same frequency domain resources. This ensures the orthogonality between uplink data transmitted by multiple terminal devices multiplexed by OCC sequences on the same time and frequency resources, thereby improving system capacity while ensuring system decoding performance.

[0569] In some embodiments, if UCI multiplexing is permitted on repeatedly transmitted PUSCHs, the terminal device may repeatedly transmit UCIs to the network device on PUSCHs in the third PUSCH group. The third PUSCH group is the PUSCH group with the earliest corresponding actual transmission time among at least one fourth PUSCH group; the at least one fourth PUSCH group is a PUSCH group with a corresponding start transmission time no earlier than a first time, where the first time is the start transmission time of the UCI.

[0570] In other words, if a terminal device needs to send a UCI, and the resources for the UCI conflict with the resources for repeatedly transmitting PUSCH, the terminal device needs to determine a first time (i.e., the start time of the UCI transmission), and then, based on the first time, determine a third PUSCH group from at least one PUSCH group that the terminal device needs to transmit. The start time of the third PUSCH group is no earlier than the first time, and the third PUSCH group is the earliest starting time among at least one fourth PUSCH group whose start time is no earlier than the first time.

[0571] Then, the terminal device repeatedly sends the UCI to the network device on each PUSCH in the third PUSCH group. In other words, the UCI is carried and transmitted on every PUSCH in the third PUSCH group. Since each PUSCH in the third PUSCH group carries the same UCI, and each PUSCH in the third PUSCH group uses the same redundant version, it can be guaranteed that the uplink data on each PUSCH in the third PUSCH group is identical. Therefore, even if other terminal devices share the time-frequency domain resources of the third PUSCH group with this terminal device, it can be guaranteed that the uplink data transmitted by different terminal devices are orthogonal and do not interfere with each other.

[0572] The following example will illustrate this point.

[0573] Figure 8 A schematic diagram of PUSCH retransmission provided in the embodiments of this application. Figure 3 ,like Figure 8 The example shown illustrates the case of two terminal devices performing repeated PUSCH transmissions, namely terminal device #1 and terminal device #2.

[0574] Two terminal devices retransmit PUSCH repeatedly on partially identical time-frequency resources using PUSCH repetition Type A, meaning PUSCH is retransmitted in units of time slots. For any given terminal device, the PUSCHs retransmitted by that device are divided into at least one PUSCH group, and the PUSCHs within the same PUSCH group use the same redundant version.

[0575] exist Figure 8 In the example, each box represents a sequential PUSCH transmission. Terminal device #1 transmits PUSCH 12 times. These 12 PUSCH transmissions are divided into 5 PUSCH groups: group11, group12, group13, group14, and group15. The number of PUSCHs in each PUSCH group is 2, 4, 4, 1, and 1, respectively.

[0576] Terminal device #2 transmits PUSCH 8 times. These 8 PUSCH transmissions are divided into 2 PUSCH groups, group21 and group22, with 4 PUSCHs in each group and 4 PUSCHs in the other group.

[0577] For example, for terminal device #1, there is a UCI that needs to be transmitted at time t1. The resources of this UCI conflict with the resources of terminal device #1 that repeatedly transmit PUSCH. If the terminal device allows UCI multiplexing on repeatedly transmitted PUSCH, the terminal device needs to determine the third PUSCH group.

[0578] like Figure 8 As shown, the starting transmission time of UCI is t1, which is also the starting transmission time of group11. Therefore, at least one fourth PUSCH group includes group11, group12, group13, group14, and group15. Among at least one fourth PUSCH group, the PUSCH group with the earliest corresponding starting transmission time is group11. Therefore, the third PUSCH group is group11. Accordingly, the terminal device can repeatedly send UCI to the network device on the PUSCH of the third PUSCH group.

[0579] For example, for terminal device #2, there is a UCI that needs to be transmitted at time t2. The resources of this UCI conflict with the resources of terminal device #2 that repeatedly transmit PUSCH. If the terminal device allows UCI multiplexing on the repeatedly transmitted PUSCH, the terminal device needs to determine the third PUSCH group.

[0580] like Figure 8 As shown, the starting transmission time of UCI is t2. T2 is later than the starting transmission time corresponding to group 21, but earlier than the starting transmission time corresponding to group 22 (i.e., t3). Therefore, at least one fourth PUSCH group includes group 22, and among at least one fourth PUSCH group, the PUSCH group with the earliest corresponding starting transmission time is group 22. Therefore, the third PUSCH group is group 22. Accordingly, the terminal device can repeatedly send UCI to the network device on the PUSCH of the third PUSCH group.

[0581] For example, if the terminal device does not allow UCI multiplexing on the repeatedly transmitted PUSCH, the terminal device will not send UCI to the network device on the repeatedly transmitted PUSCH even if the UCI resources conflict with the resources of the repeatedly transmitted PUSCH.

[0582] Since UCI is crucial for network resource scheduling, in cases where UCI resources conflict with the resources of repeatedly transmitted PUSCHs, multiplexing UCI onto PUSCHs within a PUSCH group ensures timely transmission of UCI, facilitating network resource scheduling. Furthermore, by multiplexing UCI onto multiple PUSCHs within a PUSCH group, the reliability of UCI transmission is improved, and it also ensures that a PUSCH group transmits identical data on the same frequency domain resources. This guarantees the orthogonality of uplink data transmitted by multiple terminal devices multiplexed using OCC sequences on the same time-frequency resources, increasing system capacity while maintaining system decoding performance.

[0583] Considering that when UCI is multiplexed on a PUSCH group, the network device needs to cache all PUSCHs in the PUSCH group before it can perform joint decoding, which will prolong the decoding time of UCI, when the timeliness requirement of UCI is relatively high or the priority of UCI is relatively low, the network device can also be configured not to multiplex UCI on repeatedly transmitted PUSCHs or PUSCH groups, thereby avoiding unnecessary waste of spectrum resources and reducing device complexity.

[0584] Figure 9 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application. Figure 1 ,like Figure 9 As shown, the communication device 900 includes:

[0585] The transceiver module 910 is used to receive configuration information sent by the network device. The configuration information is used to configure the terminal device to repeatedly transmit PUSCH.

[0586] The transceiver module 910 is also used to send multiple PUSCHs to the network device according to the configuration information;

[0587] Among them, multiple PUSCHs are repeatedly transmitted PUSCHs, and multiple PUSCHs include at least one PUSCH group. The PUSCHs in the PUSCH group use the same redundant version. N OCC sequences are superimposed on the PUSCHs in the PUSCH group, where N is 0 or 1.

[0588] In some embodiments, the configuration information includes at least one of the following:

[0589] PUSCH configuration information, used to configure the PUSCH for repeated transmission;

[0590] PUSCH group configuration information, used to configure at least one PUSCH group;

[0591] Frequency hopping information;

[0592] OCC configuration information is used to configure the OCC sequence superimposed on the PUSCH in the PUSCH group;

[0593] Uplink control information (UCI) indication information is used to indicate whether UCI multiplexing is allowed on repeatedly transmitted PUSCH.

[0594] In some embodiments, PUSCH configuration information includes:

[0595] The number of times the terminal device repeatedly transmits the PUSCH;

[0596] And / or,

[0597] The terminal device repeatedly transmits PUSCH resources.

[0598] In some embodiments, the PUSCH group configuration information includes at least one of the following:

[0599] The number of at least one PUSCH group;

[0600] The number of PUSCHs in the PUSCH group;

[0601] The transmission order of the PUSCH group;

[0602] Redundancy version information for PUSCH groups, used to indicate the redundant versions used by PUSCHs in the PUSCH group.

[0603] In some embodiments, the frequency hopping information includes at least one of the following:

[0604] The first indication information is used to indicate whether the terminal device repeatedly transmits PUSCH based on frequency hopping.

[0605] Frequency hopping type;

[0606] Frequency hopping parameters are used to indicate the frequency domain resources of the PUSCH group.

[0607] In some embodiments, frequency hopping types include at least one of the following:

[0608] Frequency hopping type within a time slot;

[0609] Inter-slot frequency hopping type;

[0610] PUSCH inter-group frequency hopping type.

[0611] In some embodiments, the OCC configuration information includes at least one of the following:

[0612] The second indication information is used to indicate whether an OCC sequence is superimposed on the PUSCH in the PUSCH group;

[0613] Length of the OCC sequence;

[0614] Index of OCC sequence;

[0615] How OCC sequences are generated;

[0616] OCC sequence set.

[0617] In some embodiments, an OCC sequence is superimposed on the PUSCH in the PUSCH group, and the PUSCH group satisfies:

[0618] The number of PUSCHs in a PUSCH group is equal to the length of the OCC sequence superimposed on the PUSCHs in the PUSCH group.

[0619] In some embodiments, the number of PUSCHs in different PUSCH groups is the same; or, the number of PUSCHs in different PUSCH groups is different.

[0620] In some embodiments, an OCC sequence is superimposed on the PUSCH in the PUSCH group, wherein:

[0621] The OCC sequence superimposed on the PUSCH in the PUSCH group is determined based on configuration information and / or predefined methods.

[0622] In some embodiments, for any first PUSCH group and second PUSCH group in at least one PUSCH group, the first OCC sequence superimposed on the PUSCH in the first PUSCH group and the second OCC sequence superimposed on the PUSCH in the second PUSCH group satisfy at least one of the following:

[0623] The first OCC sequence and the second OCC sequence are the same OCC sequence;

[0624] The first OCC sequence and the second OCC sequence belong to different sets of OCC sequences;

[0625] The first OCC sequence and the second OCC sequence belong to different indices of the same OCC sequence set;

[0626] The first OCC sequence is generated in the same way as the second OCC sequence, but the generation parameters used for the first OCC sequence are different from those used for the second OCC sequence.

[0627] The first OCC sequence is generated in a different way than the second OCC sequence.

[0628] In some embodiments, the redundant versions of the PUSCHs in the PUSCH group are determined based on at least one of the following:

[0629] Configuration information;

[0630] Index of the PUSCH group;

[0631] The transmission order of the PUSCH group;

[0632] The cyclical order of redundant versions.

[0633] In some embodiments, where UCI multiplexing on repeatedly transmitted PUSCH is permitted, the transceiver module 910 is further configured to:

[0634] Repeatedly send UCI to the network device on the PUSCH in the third PUSCH group;

[0635] Among them, the third PUSCH group is the PUSCH group with the earliest corresponding start transmission time in at least one fourth PUSCH group; at least one fourth PUSCH group is the PUSCH group with a corresponding start transmission time no earlier than the first time, where the first time is the start transmission time of UCI.

[0636] In some embodiments, when a terminal device sends multiple PUSCHs to a network device based on a frequency hopping method, the frequency hopping type used by the multiple PUSCHs is the inter-PUSCH group frequency hopping type.

[0637] In some embodiments, the frequency domain resources of the PUSCH group are determined based on the index of the PUSCH group.

[0638] In some embodiments, configuration information is carried in at least one of the following signaling:

[0639] DCI;

[0640] MAC CE;

[0641] RRC message.

[0642] The communication device provided in this application embodiment is used to execute the above method embodiment. Its implementation principle and technical effect are similar, and will not be described again here.

[0643] Figure 10 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application. Figure 2 ,like Figure 10 As shown, the communication device 1000 includes:

[0644] The transceiver module 1010 is used to send configuration information to the terminal device. The configuration information is used to configure the terminal device to repeatedly transmit PUSCH.

[0645] The transceiver module 1010 is also used to receive multiple PUSCHs sent by the terminal device according to the configuration information;

[0646] Among them, multiple PUSCHs are repeatedly transmitted PUSCHs, and multiple PUSCHs include at least one PUSCH group. The PUSCHs in the PUSCH group use the same redundant version. N OCC sequences are superimposed on the PUSCHs in the PUSCH group, where N is 0 or 1.

[0647] In some embodiments, the configuration information includes at least one of the following:

[0648] PUSCH configuration information, used to configure the PUSCH for repeated transmission;

[0649] PUSCH group configuration information, used to configure at least one PUSCH group;

[0650] Frequency hopping information;

[0651] OCC configuration information is used to configure the OCC sequence superimposed on the PUSCH in the PUSCH group;

[0652] UCI indication information is used to indicate whether UCI multiplexing is allowed on repeatedly transmitted PUSCH.

[0653] In some embodiments, PUSCH configuration information includes:

[0654] The number of times the terminal device repeatedly transmits the PUSCH;

[0655] And / or,

[0656] The terminal device repeatedly transmits PUSCH resources.

[0657] In some embodiments, the PUSCH group configuration information includes at least one of the following:

[0658] The number of at least one PUSCH group;

[0659] The number of PUSCHs in the PUSCH group;

[0660] The transmission order of the PUSCH group;

[0661] Redundancy version information for PUSCH groups, used to indicate the redundant versions used by PUSCHs in the PUSCH group.

[0662] In some embodiments, the frequency hopping information includes at least one of the following:

[0663] The first indication information is used to indicate whether the terminal device repeatedly transmits PUSCH based on frequency hopping.

[0664] Frequency hopping type;

[0665] Frequency hopping parameters are used to indicate the frequency domain resources of the PUSCH group.

[0666] In some embodiments, frequency hopping types include at least one of the following:

[0667] Frequency hopping type within a time slot;

[0668] Inter-slot frequency hopping type;

[0669] PUSCH inter-group frequency hopping type.

[0670] In some embodiments, the OCC configuration information includes at least one of the following:

[0671] The second indication information is used to indicate whether an OCC sequence is superimposed on the PUSCH in the PUSCH group;

[0672] Length of the OCC sequence;

[0673] Index of OCC sequence;

[0674] How OCC sequences are generated;

[0675] OCC sequence set.

[0676] In some embodiments, an OCC sequence is superimposed on the PUSCH in the PUSCH group, and the PUSCH group satisfies:

[0677] The number of PUSCHs in a PUSCH group is equal to the length of the OCC sequence superimposed on the PUSCHs in the PUSCH group.

[0678] In some embodiments, the number of PUSCHs in different PUSCH groups is the same; or, the number of PUSCHs in different PUSCH groups is different.

[0679] In some embodiments, an OCC sequence is superimposed on the PUSCH in the PUSCH group, wherein:

[0680] The OCC sequence superimposed on the PUSCH in the PUSCH group is determined based on configuration information and / or predefined methods.

[0681] In some embodiments, for any first PUSCH group and second PUSCH group in at least one PUSCH group, the first OCC sequence superimposed on the PUSCH in the first PUSCH group and the second OCC sequence superimposed on the PUSCH in the second PUSCH group satisfy at least one of the following:

[0682] The first OCC sequence and the second OCC sequence are the same OCC sequence;

[0683] The first OCC sequence and the second OCC sequence belong to different sets of OCC sequences;

[0684] The first OCC sequence and the second OCC sequence belong to different indices of the same OCC sequence set;

[0685] The first OCC sequence is generated in the same way as the second OCC sequence, but the generation parameters used for the first OCC sequence are different from those used for the second OCC sequence.

[0686] The first OCC sequence is generated in a different way than the second OCC sequence.

[0687] In some embodiments, the redundant versions of the PUSCHs in the PUSCH group are determined based on at least one of the following:

[0688] Configuration information;

[0689] Index of the PUSCH group;

[0690] The transmission order of the PUSCH group;

[0691] The cyclical order of redundant versions.

[0692] In some embodiments, where UCI multiplexing on repeatedly transmitted PUSCH is permitted, the transceiver module 1010 is further configured to:

[0693] Receive the UCI repeatedly transmitted by the terminal device on the PUSCH in the third PUSCH group;

[0694] Among them, the third PUSCH group is the PUSCH group with the earliest corresponding start transmission time in at least one fourth PUSCH group; at least one fourth PUSCH group is the PUSCH group with a corresponding start transmission time no earlier than the first time, where the first time is the start transmission time of UCI.

[0695] In some embodiments, when a terminal device sends multiple PUSCHs to a network device based on a frequency hopping method, the frequency hopping type used by the multiple PUSCHs is the inter-PUSCH group frequency hopping type.

[0696] In some embodiments, the frequency domain resources of the PUSCH group are determined based on the index of the PUSCH group.

[0697] In some embodiments, the plurality of PUSCHs includes at least a fifth PUSCH group sent by a first terminal device and a sixth PUSCH group sent by a second terminal device; a third OCC sequence is superimposed on the PUSCHs in the fifth PUSCH group, and a fourth OCC sequence is superimposed on the PUSCHs in the sixth PUSCH group; wherein:

[0698] The resources of the fifth PUSCH group are the same as those of the sixth PUSCH group, and the third OCC sequence and the fourth OCC sequence are orthogonal to each other.

[0699] or,

[0700] The resources of the first PUSCH sequence are the same as those of the second PUSCH sequence. The first PUSCH sequence has a first OCC subsequence superimposed on the PUSCH, and the second PUSCH sequence has a second OCC subsequence superimposed on the PUSCH. The first OCC subsequence and the second OCC subsequence are orthogonal to each other.

[0701] The first PUSCH sequence is a subset of the fifth PUSCH group, the second PUSCH sequence is a subset of the sixth PUSCH group, the first OCC subsequence is a subset of the third OCC sequence, and the second OCC subsequence is a subset of the fourth OCC sequence.

[0702] In some embodiments, the third OCC sequence and the fourth OCC sequence satisfy at least one of the following:

[0703] The third OCC sequence and the fourth OCC sequence belong to different sets of OCC sequences;

[0704] The third and fourth OCC sequences belong to different indices of the same OCC sequence set;

[0705] The third OCC sequence is generated in the same way as the fourth OCC sequence, but the generation parameters used for the third OCC sequence are different from those used for the fourth OCC sequence.

[0706] The third OCC sequence is generated in a different way than the fourth OCC sequence.

[0707] In some embodiments, configuration information is carried in at least one of the following signaling:

[0708] DCI;

[0709] MAC CE;

[0710] RRC message.

[0711] The communication device provided in this application embodiment is used to execute the above method embodiment. Its implementation principle and technical effect are similar, and will not be described again here.

[0712] Figure 11 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Figure 11 As shown, the communication device includes: at least one processor 1102, a memory 1101 communicatively connected to at least one processor 1102, and a transceiver 1103.

[0713] Memory 1101 is used to store instructions.

[0714] The processor 1102 is used to execute the instructions stored in the memory so that the communication device performs the method steps performed by the terminal device or the network device.

[0715] Transceiver 1103 may include a transmitter and / or a receiver. The transmitter may also be referred to as a transmitter, transmitter, transmitting port, or transmitting interface, and the receiver may also be referred to as a receiver, receiving port, or receiving interface, etc. Exemplarily, the memory 1101, processor 1102, and transceiver 1103 are interconnected via bus 1104.

[0716] All or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a readable memory. When the program is executed, it performs the steps of the above method embodiments; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid-state drive, magnetic tape, floppy disk, optical disk, and any combination thereof.

[0717] This application provides a communication system including a terminal device and a network device. The terminal device is configured to implement the communication method executed by the terminal device in the above method embodiment, and the network device is configured to implement the communication method executed by the network device in the above method embodiment.

[0718] This application provides a non-transitory computer-readable storage medium storing computer instructions. The computer-readable storage medium stores computer instructions that, when executed by a processor, are used to implement the method steps executed by a terminal device or network device in the above method embodiments.

[0719] This application also provides a program product, including at least one of a program and instructions. When the program or instructions are executed by a communication device, they can implement the method steps executed by the terminal device or network device in the above method embodiments.

[0720] This application also provides a chip that stores a computer program. When the computer program is executed by the chip, it implements the method steps executed by the terminal device or network device in the above method embodiments.

[0721] This application also provides a chip module, on which a computer program is stored. When the computer program is executed by the chip module, it implements the method steps executed by the terminal device or network device in the above method embodiments.

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

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

[0724] Regarding the modules / units included in the various devices and products described in the above embodiments, they can be software modules / units, hardware modules / units, or a combination of both. For example, for devices and products applied to or integrated into a chip, all modules / units can be implemented using hardware methods such as circuits, or at least some modules / units can be implemented using software programs running on a processor integrated within the chip, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits. For devices and products applied to or integrated into a chip module, all modules / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units can be implemented using software programs. The software program runs on the processor integrated inside the chip module, and the remaining (if any) modules / units can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into terminal devices or network devices, each of its modules / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components within the terminal device or network device. Alternatively, at least some modules / units can be implemented using software programs that run on the processor integrated inside the terminal device or network device, and the remaining (if any) modules / units can be implemented using hardware methods such as circuits.

[0725] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0726] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0727] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0728] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned computer program can be stored in a computer-readable storage medium. When executed by a processor, the computer program implements the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0729] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A communication method, characterized in that, The method, executed by a terminal device, includes: The terminal device receives configuration information sent by a network device, the configuration information being used to configure the terminal device to repeatedly transmit the Physical Uplink Shared Channel (PUSCH). Based on the configuration information, multiple PUSCHs are sent to the network device; The plurality of PUSCHs are repeatedly transmitted PUSCHs, and the plurality of PUSCHs include at least one PUSCH group. The PUSCHs in the PUSCH group use the same redundant version. N orthogonal overlay code (OCC) sequences are superimposed on the PUSCHs in the PUSCH group, where N is 0 or 1.

2. The method according to claim 1, characterized in that, The configuration information includes at least one of the following: PUSCH configuration information, used to configure the PUSCH for repeated transmissions; PUSCH group configuration information, used to configure the at least one PUSCH group; Frequency hopping information; OCC configuration information is used to configure the OCC sequence superimposed on the PUSCH in the PUSCH group; Uplink control information (UCI) indication information is used to indicate whether UCI multiplexing is allowed on the repeatedly transmitted PUSCH.

3. The method according to claim 2, characterized in that, PUSCH configuration information includes: The number of times the terminal device repeatedly transmits PUSCH; And / or, The terminal device repeatedly transmits PUSCH resources.

4. The method according to claim 2, characterized in that, PUSCH group configuration information includes at least one of the following: The number of at least one PUSCH group; The number of PUSCHs in the PUSCH group; The transmission order of the PUSCH group; Redundancy version information for PUSCH groups, used to indicate the redundant versions used by the PUSCHs in the PUSCH group.

5. The method according to claim 2, characterized in that, The frequency hopping information includes at least one of the following: The first indication information is used to indicate whether the terminal device repeatedly transmits PUSCH based on frequency hopping. Frequency hopping type; Frequency hopping parameters are used to indicate the frequency domain resources of the PUSCH group.

6. The method according to claim 5, characterized in that, The frequency hopping type includes at least one of the following: Frequency hopping type within a time slot; Inter-slot frequency hopping type; PUSCH inter-group frequency hopping type.

7. The method according to claim 2, characterized in that, The OCC configuration information includes at least one of the following: The second indication information is used to indicate whether an OCC sequence is superimposed on the PUSCH in the PUSCH group; Length of the OCC sequence; Index of OCC sequence; How OCC sequences are generated; OCC sequence set.

8. The method according to any one of claims 1-7, characterized in that, The PUSCH group contains PUSCHs superimposed with OCC sequences, and the PUSCH group satisfies: The number of PUSCHs in the PUSCH group is equal to the length of the OCC sequence superimposed on the PUSCHs in the PUSCH group.

9. The method according to any one of claims 1-8, characterized in that, The number of PUSCHs is the same in different PUSCH groups; or the number of PUSCHs is different in different PUSCH groups.

10. The method according to any one of claims 1-9, characterized in that, The PUSCH in the PUSCH group has an OCC sequence superimposed on it, wherein: The OCC sequence superimposed on the PUSCH in the PUSCH group is determined based on the configuration information and / or a predefined method.

11. The method according to any one of claims 1-10, characterized in that, For any first PUSCH group and second PUSCH group in the at least one PUSCH group, the first OCC sequence superimposed on the PUSCH in the first PUSCH group and the second OCC sequence superimposed on the PUSCH in the second PUSCH group satisfy at least one of the following: The first OCC sequence and the second OCC sequence are the same OCC sequence; The first OCC sequence and the second OCC sequence belong to different sets of OCC sequences; The first OCC sequence and the second OCC sequence belong to different indices of the same OCC sequence set; The first OCC sequence is generated in the same way as the second OCC sequence, but the generation parameters used for the first OCC sequence are different from those used for the second OCC sequence. The first OCC sequence is generated in a different way than the second OCC sequence.

12. The method according to any one of claims 1-11, characterized in that, The redundant versions of the PUSCHs in the PUSCH group are determined based on at least one of the following: The configuration information; The index of the PUSCH group; The transmission order of the PUSCH group; The cyclical order of redundant versions.

13. The method according to any one of claims 1-12, characterized in that, If UCI multiplexing is permitted on the repeatedly transmitted PUSCH, the method further includes: Repeatedly send UCI to the network device on the PUSCH in the third PUSCH group; Wherein, the third PUSCH group is the PUSCH group with the earliest corresponding start transmission time among at least one fourth PUSCH group; the at least one fourth PUSCH group is the PUSCH group with a corresponding start transmission time no earlier than the first time, where the first time is the start transmission time of the UCI.

14. The method according to any one of claims 1-13, characterized in that, When the terminal device sends the multiple PUSCHs to the network device based on frequency hopping, the frequency hopping type used by the multiple PUSCHs is the inter-PUSCH frequency hopping type.

15. The method according to claim 14, characterized in that, The frequency domain resources of the PUSCH group are determined based on the index of the PUSCH group.

16. The method according to any one of claims 1-15, characterized in that, The configuration information is carried in at least one of the following signaling messages: Downlink Control Information (DCI); Media Access Control - Control Element MAC CE; Radio Resource Control (RRC) message.

17. A communication method, characterized in that, Performed by a network device, the method includes: Send configuration information to the terminal device, the configuration information being used to configure the terminal device to repeatedly transmit PUSCH; According to the configuration information, receive multiple PUSCHs sent by the terminal device; The plurality of PUSCHs are repeatedly transmitted PUSCHs, and the plurality of PUSCHs include at least one PUSCH group. The PUSCHs in the PUSCH group use the same redundant version. N OCC sequences are superimposed on the PUSCHs in the PUSCH group, where N is 0 or 1.

18. The method according to claim 17, characterized in that, The configuration information includes at least one of the following: PUSCH configuration information, used to configure the PUSCH for repeated transmissions; PUSCH group configuration information, used to configure the at least one PUSCH group; Frequency hopping information; OCC configuration information is used to configure the OCC sequence superimposed on the PUSCH in the PUSCH group; UCI indication information is used to indicate whether UCI multiplexing is allowed on the repeatedly transmitted PUSCH.

19. The method according to claim 18, characterized in that, PUSCH configuration information includes: The number of times the terminal device repeatedly transmits PUSCH; And / or, The terminal device repeatedly transmits PUSCH resources.

20. The method according to claim 18, characterized in that, PUSCH group configuration information includes at least one of the following: The number of at least one PUSCH group; The number of PUSCHs in the PUSCH group; The transmission order of the PUSCH group; Redundancy version information for PUSCH groups, used to indicate the redundant versions used by the PUSCHs in the PUSCH group.

21. The method according to claim 18, characterized in that, The frequency hopping information includes at least one of the following: The first indication information is used to indicate whether the terminal device repeatedly transmits PUSCH based on frequency hopping. Frequency hopping type; Frequency hopping parameters are used to indicate the frequency domain resources of the PUSCH group.

22. The method according to claim 21, characterized in that, The frequency hopping type includes at least one of the following: Frequency hopping type within a time slot; Inter-slot frequency hopping type; PUSCH inter-group frequency hopping type.

23. The method according to claim 18, characterized in that, The OCC configuration information includes at least one of the following: The second indication information is used to indicate whether an OCC sequence is superimposed on the PUSCH in the PUSCH group; Length of the OCC sequence; Index of OCC sequence; How OCC sequences are generated; OCC sequence set.

24. The method according to any one of claims 17-23, characterized in that, The PUSCH group contains PUSCHs superimposed with OCC sequences, and the PUSCH group satisfies: The number of PUSCHs in the PUSCH group is equal to the length of the OCC sequence superimposed on the PUSCHs in the PUSCH group.

25. The method according to any one of claims 17-24, characterized in that, The number of PUSCHs is the same in different PUSCH groups; or the number of PUSCHs is different in different PUSCH groups.

26. The method according to any one of claims 17-25, characterized in that, The PUSCH in the PUSCH group has an OCC sequence superimposed on it, wherein: The OCC sequence superimposed on the PUSCH in the PUSCH group is determined based on the configuration information and / or a predefined method.

27. The method according to any one of claims 17-26, characterized in that, For any first PUSCH group and second PUSCH group in the at least one PUSCH group, the first OCC sequence superimposed on the PUSCH in the first PUSCH group and the second OCC sequence superimposed on the PUSCH in the second PUSCH group satisfy at least one of the following: The first OCC sequence and the second OCC sequence are the same OCC sequence; The first OCC sequence and the second OCC sequence belong to different sets of OCC sequences; The first OCC sequence and the second OCC sequence belong to different indices of the same OCC sequence set; The first OCC sequence is generated in the same way as the second OCC sequence, but the generation parameters used for the first OCC sequence are different from those used for the second OCC sequence. The first OCC sequence is generated in a different way than the second OCC sequence.

28. The method according to any one of claims 17-27, characterized in that, The redundant versions of the PUSCHs in the PUSCH group are determined based on at least one of the following: The configuration information; The index of the PUSCH group; The transmission order of the PUSCH group; The cyclical order of redundant versions.

29. The method according to any one of claims 17-28, characterized in that, If UCI multiplexing is permitted on the repeatedly transmitted PUSCH, the method further includes: Receive the UCI repeatedly transmitted by the terminal device on the PUSCH in the third PUSCH group; Wherein, the third PUSCH group is the PUSCH group with the earliest corresponding start transmission time among at least one fourth PUSCH group; the at least one fourth PUSCH group is the PUSCH group with a corresponding start transmission time no earlier than the first time, where the first time is the start transmission time of the UCI.

30. The method according to any one of claims 17-29, characterized in that, When the terminal device sends the multiple PUSCHs to the network device based on frequency hopping, the frequency hopping type used by the multiple PUSCHs is the inter-PUSCH frequency hopping type.

31. The method according to claim 30, characterized in that, The frequency domain resources of the PUSCH group are determined based on the index of the PUSCH group.

32. The method according to any one of claims 17-31, characterized in that, The plurality of PUSCHs includes at least a fifth PUSCH group sent by the first terminal device and a sixth PUSCH group sent by the second terminal device; a third OCC sequence is superimposed on the PUSCHs in the fifth PUSCH group, and a fourth OCC sequence is superimposed on the PUSCHs in the sixth PUSCH group; wherein: The resources of the fifth PUSCH group are the same as those of the sixth PUSCH group, and the third OCC sequence and the fourth OCC sequence are orthogonal to each other; or, The resources of the first PUSCH sequence are the same as those of the second PUSCH sequence. The first PUSCH sequence has a first OCC subsequence superimposed on the PUSCH, and the second PUSCH sequence has a second OCC subsequence superimposed on the PUSCH. The first OCC subsequence and the second OCC subsequence are orthogonal to each other. Wherein, the first PUSCH sequence is a subset of the fifth PUSCH group, the second PUSCH sequence is a subset of the sixth PUSCH group; the first OCC subsequence is a subset of the third OCC sequence; and the second OCC subsequence is a subset of the fourth OCC sequence.

33. The method according to claim 32, characterized in that, The third OCC sequence and the fourth OCC sequence satisfy at least one of the following: The third OCC sequence and the fourth OCC sequence belong to different sets of OCC sequences; The third OCC sequence and the fourth OCC sequence belong to different indices of the same OCC sequence set; The third OCC sequence is generated in the same way as the fourth OCC sequence, but the generation parameters used for the third OCC sequence are different from those used for the fourth OCC sequence. The method of generating the third OCC sequence is different from the method of generating the fourth OCC sequence.

34. The method according to any one of claims 17-33, characterized in that, The configuration information is carried in at least one of the following signaling messages: DCI; MAC CE; RRC message.

35. A communication device, characterized in that, include: The transceiver module is used to receive configuration information sent by the network device, the configuration information being used to configure the terminal device to repeatedly transmit PUSCH; The transceiver module is also used to send multiple PUSCHs to the network device according to the configuration information; The plurality of PUSCHs are repeatedly transmitted PUSCHs, and the plurality of PUSCHs include at least one PUSCH group. The PUSCHs in the PUSCH group use the same redundant version. N OCC sequences are superimposed on the PUSCHs in the PUSCH group, where N is 0 or 1.

36. A communication device, characterized in that, include: The transceiver module is used to send configuration information to the terminal device, wherein the configuration information is used to configure the terminal device to repeatedly transmit PUSCH; The transceiver module is also configured to receive multiple PUSCHs sent by the terminal device according to the configuration information; The plurality of PUSCHs are repeatedly transmitted PUSCHs, and the plurality of PUSCHs include at least one PUSCH group. The PUSCHs in the PUSCH group use the same redundant version. N OCC sequences are superimposed on the PUSCHs in the PUSCH group, where N is 0 or 1.

37. A communication device, characterized in that, include: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 34.

38. A communication system, characterized in that, The device includes a terminal device and a network device, wherein the terminal device is configured to implement the communication method of any one of claims 1 to 16, and the network device is configured to implement the communication method of any one of claims 17 to 34.

39. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1 to 34.

40. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the steps of the communication method according to any one of claims 1 to 34.

Images