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

Abstract

The present disclosure relates to a communication method, a communication device, a communication system, a storage medium, and a program product. The method comprises: sending first information to a terminal, wherein the first information is used for indicating that one cell of a network device corresponds to a plurality of uplink carriers; and sending second information to the terminal, wherein the second information is used for indicating: among the plurality of uplink carriers, at least two uplink carriers that support the terminal in performing simultaneous uplink transmission. In embodiments of the present disclosure, one cell comprises a plurality of carriers, and the network device may indicate, to the terminal, at least two carriers on which simultaneous uplink transmission can be performed, such that the terminal may transmit uplink information on the at least two carriers, thereby improving uplink throughput and thus meeting diverse service requirements.

Description

Communication methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system, storage medium, and program product. Background Technology

[0002] In communication systems, carrier aggregation (CA) technology can be used to improve system bandwidth and throughput. Among the carriers participating in carrier aggregation, at the cell level, they are divided into primary cells (PCell) and secondary cells (SCell). Each cell participating in carrier aggregation can have a physical downlink control channel (PDCCH). Each carrier or cell can perform self-scheduling or cross-carrier scheduling. Summary of the Invention

[0003] In carrier aggregation, the number of downlink (DL) carriers is greater than the number of uplink (UL) carriers. However, due to service diversity, some services have a higher UL throughput requirement than DL throughput.

[0004] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0005] In a first aspect, embodiments of this disclosure provide a communication method executed by a network device, the method comprising:

[0006] Send first information to the terminal, the first information being used to indicate that one cell of the network device corresponds to multiple uplink carriers;

[0007] Send a second message to the terminal, the second message indicating that at least two uplink carriers among the plurality of uplink carriers support the terminal to perform uplink transmission simultaneously.

[0008] Secondly, embodiments of this disclosure provide a communication method executed by a terminal, the method comprising:

[0009] The network device receives first information, which indicates that one cell of the network device corresponds to multiple uplink carriers.

[0010] The network device receives second information, which indicates that at least two uplink carriers among the plurality of uplink carriers support the terminal to perform uplink transmission simultaneously.

[0011] Thirdly, embodiments of this disclosure provide a communication method for a communication system, the communication system including network devices and terminals, the method comprising:

[0012] The network device sends first information to the terminal, the first information being used to indicate that one cell of the network device corresponds to multiple uplink carriers;

[0013] The network device sends a second message to the terminal, the second message indicating that at least two uplink carriers among the plurality of uplink carriers support the terminal to perform uplink transmission simultaneously.

[0014] Fourthly, embodiments of this disclosure provide a communication device, wherein the communication device is used to perform the method described in the first aspect or the second aspect.

[0015] Fifthly, according to an embodiment of this disclosure, a communication system includes a network device and a terminal, wherein,

[0016] The network device is configured to implement the method as described in the first aspect;

[0017] The terminal is configured to implement the method as described in the second aspect.

[0018] Sixthly, according to an embodiment of this disclosure, a storage medium stores instructions, wherein...

[0019] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method as described in the first aspect or the second aspect.

[0020] In a seventh aspect, an embodiment of this disclosure provides a program product comprising at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, they implement the method described in the first aspect or the second aspect.

[0021] In this embodiment of the disclosure, a cell includes multiple carriers. The network device can indicate to the terminal at least two carriers that can transmit uplink information simultaneously, so that the terminal can transmit uplink information on at least two carriers, thereby improving uplink throughput and meeting diverse service needs. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0023] Figure 1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0024] Figures 2A and 2B are exemplary interactive schematic diagrams of the method provided according to embodiments of the present disclosure;

[0025] Figure 2C is a scheduling diagram provided according to an embodiment of the present disclosure;

[0026] Figures 3A to 3C are exemplary interactive schematic diagrams of the method provided according to embodiments of the present disclosure;

[0027] Figure 4A is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure;

[0028] Figure 4B is a schematic diagram of the structure of a network device according to an embodiment of the present disclosure;

[0029] Figure 5A is a schematic diagram of a communication device according to an embodiment of the present disclosure;

[0030] Figure 5B is a schematic diagram of a communication device according to an embodiment of the present disclosure. Detailed Implementation

[0031] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0032] In a first aspect, embodiments of this disclosure provide a communication method executed by a network device, the method comprising:

[0033] Send first information to the terminal, the first information being used to indicate that one cell of the network device corresponds to multiple uplink carriers;

[0034] Send a second message to the terminal, the second message indicating that at least two uplink carriers among the plurality of uplink carriers support the terminal to perform uplink transmission simultaneously.

[0035] In the above embodiments, a cell includes multiple carriers. The network device can indicate to the terminal at least two carriers that can transmit uplink information simultaneously, so that the terminal can transmit uplink information on at least two carriers, thereby improving uplink throughput and meeting diverse service needs.

[0036] In conjunction with the embodiments of the first aspect, in some embodiments, the second information is used to indicate at least one of the following:

[0037] Carrier indices of at least two uplink carriers;

[0038] Multiple uplink carriers correspond to carrier types, wherein the carrier type is a first type or a second type, the uplink carrier of the first type does not support simultaneous uplink transmission with other uplink carriers, and the uplink carrier of the second type supports simultaneous uplink transmission with other uplink carriers;

[0039] Multiple uplink carriers correspond to carrier groups, wherein different uplink carriers within one carrier group support simultaneous uplink transmission, while uplink carriers within different carrier groups do not support simultaneous uplink transmission.

[0040] In the above embodiments, the second information can indicate uplink carriers that support simultaneous transmission in various ways, thereby improving the flexibility of indication or configuration in scenarios that improve uplink throughput.

[0041] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0042] The receiving terminal sends third information, which is used to indicate the carrier combination and / or frequency band combination that the terminal can simultaneously perform uplink transmission; wherein, the second information is used to indicate whether the uplink carrier corresponding to the carrier combination and / or frequency band combination supports simultaneous uplink transmission.

[0043] In the above embodiments, the network device can indicate uplink carriers that support simultaneous transmission based on the capabilities reported by the terminal, thereby improving the accuracy and rationality of the configuration or indication and thus increasing uplink throughput.

[0044] In conjunction with the embodiments of the first aspect, in some embodiments, multiple uplink carriers correspond to the same Hybrid Automatic Repeat Request (HARQ) entity; or, among multiple uplink carriers, each uplink carrier corresponds to a HARQ entity.

[0045] In the above embodiments, the efficiency of uplink scheduling can be improved, thereby improving uplink communication performance.

[0046] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0047] A fourth message is sent to the terminal, which instructs the terminal to perform HARQ retransmission.

[0048] In the above embodiments, the network device can schedule the terminal to perform repeated transmissions, thereby improving communication performance.

[0049] In conjunction with the embodiments of the first aspect, in some embodiments, the fourth information includes at least one of the following:

[0050] Carrier pattern for HARQ repetition; wherein the carrier pattern indicates the carrier for HARQ repetition among multiple uplink carriers;

[0051] Carrier index for HARQ retransmission;

[0052] A neighborhood index for a residential community.

[0053] In the above embodiments, network devices can indicate the carrier for repeated transmission in various ways to improve the efficiency of uplink repeated transmission, thereby improving communication performance.

[0054] In conjunction with the embodiments of the first aspect, in some embodiments, the carrier index corresponding to each uplink carrier is a number among all uplink carriers of multiple serving cells configured for the terminal, or a number among the uplink carriers of a single cell.

[0055] In the above embodiments, different numbering methods can accurately determine the corresponding uplink carriers, thereby improving the accuracy when the terminal transmits simultaneously.

[0056] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0057] The fifth information is sent to the terminal. The fifth information is used to indicate the timing advance TA group corresponding to each of the multiple uplink carriers. The transmit and receive points corresponding to the multiple uplink carriers are non-co-located.

[0058] In the above embodiments, the network device can ensure the accuracy of the timing of the terminal's uplink transmission through the fifth information.

[0059] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0060] The sixth message is sent to the terminal. The sixth message is used to indicate the priority information of the uplink transmission and to help the terminal handle uplink transmission conflicts.

[0061] In the above embodiments, the priority information indicated by the sixth information can improve the efficiency of conflict handling.

[0062] In conjunction with the embodiments of the first aspect, in some embodiments, uplink transmission conflicts include at least one of the following:

[0063] Uplink transmissions on the first carrier (Dynamic Grant, DG) conflict with uplink transmissions on the second carrier (Configured Grant, CG).

[0064] The CG uplink transmission on the first carrier conflicts with the CG uplink transmission on the second carrier;

[0065] The DG uplink transmission on the first carrier conflicts with the DG uplink transmission on the second carrier;

[0066] Among them, the first carrier and the second carrier are two carriers that do not support simultaneous uplink transmission among multiple uplink carriers.

[0067] In conjunction with the embodiments of the first aspect, in some embodiments, the priority information includes at least one of the following:

[0068] DG uplink transmission priority;

[0069] Service priority associated with DG uplink transmission;

[0070] Priority of CG uplink transmission;

[0071] Service priority associated with CG uplink transmission.

[0072] In conjunction with the embodiments of the first aspect, in some embodiments, the first information includes: Random Access Channel (RACH) resources corresponding to each of the plurality of uplink carriers.

[0073] In the above embodiments, the RACH resources configured by the network device facilitate random access by the terminal on any uplink carrier, thereby improving communication performance.

[0074] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0075] The receiving terminal sends random access information, wherein the random access information is sent by the terminal based on the RACH resource corresponding to the third carrier among multiple uplink carriers, wherein the third carrier satisfies at least one of the following:

[0076] The terminal selects randomly;

[0077] The terminal is selected based on the terminal type;

[0078] The terminal selects based on the type of uplink service;

[0079] The terminal selects based on the slice information.

[0080] In the above embodiments, the network device can establish a connection with the terminal to improve communication performance, wherein the terminal can select a randomly accessed carrier based on multiple methods to improve access flexibility.

[0081] In conjunction with embodiments of the first aspect, in some embodiments, each of the plurality of uplink carriers is associated with at least one of the following:

[0082] Terminal type, uplink service type, and slice information.

[0083] Secondly, embodiments of this disclosure provide a communication method executed by a terminal, the method comprising:

[0084] The network device receives first information, which indicates that one cell of the network device corresponds to multiple uplink carriers.

[0085] The network device receives second information, which indicates that at least two uplink carriers among the plurality of uplink carriers support the terminal to perform uplink transmission simultaneously.

[0086] In the above embodiments, a cell includes multiple carriers. The terminal can learn about at least two carriers that are transmitting uplink at the same time based on the instructions of the network device, so that the terminal can transmit uplink information on at least two carriers, improve uplink throughput, and meet diverse service needs.

[0087] In conjunction with embodiments of the second aspect, in some embodiments, the second information is used to indicate at least one of the following:

[0088] Carrier indices of at least two uplink carriers;

[0089] Multiple uplink carriers correspond to carrier types, wherein the carrier type is a first type or a second type, the uplink carrier of the first type does not support simultaneous uplink transmission with other uplink carriers, and the uplink carrier of the second type supports simultaneous uplink transmission with other uplink carriers;

[0090] Multiple uplink carriers correspond to carrier groups, wherein different uplink carriers within one carrier group support simultaneous uplink transmission, while uplink carriers within different carrier groups do not support simultaneous uplink transmission.

[0091] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0092] The third information is sent to the network device, the third information being used to indicate that the terminal supports carrier combinations and / or frequency band combinations for simultaneous uplink transmission; wherein, the second information is used to indicate whether the uplink carrier corresponding to the carrier combination and / or the frequency band combination supports simultaneous uplink transmission.

[0093] In conjunction with the embodiments of the second aspect, in some embodiments, the plurality of uplink carriers correspond to the same Hybrid Automatic Repeat Request (HARQ) entity; or, in the plurality of uplink carriers, each uplink carrier corresponds to a HARQ entity.

[0094] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0095] The terminal receives a fourth message sent by the network device, the fourth message being used to instruct the terminal to perform HARQ retransmission.

[0096] In conjunction with the embodiments of the second aspect, in some embodiments, the fourth information includes at least one of the following:

[0097] A carrier pattern for HARQ repetition; wherein the carrier pattern indicates the carriers for HARQ repetition in the plurality of uplink carriers;

[0098] Carrier index for HARQ retransmission;

[0099] A neighborhood index for a residential community.

[0100] In conjunction with the embodiments of the second aspect, in some embodiments, the carrier index corresponding to each uplink carrier is a number among all uplink carriers of multiple serving cells configured for the terminal, or a number among the uplink carriers of the cell.

[0101] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0102] The network device receives a fifth message sent by the network device, the fifth message being used to indicate the timing advance TA group corresponding to each of the plurality of uplink carriers, wherein the network device includes a plurality of non-co-located transceiver points corresponding to the cell.

[0103] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0104] Receive the sixth information sent by the network device, the sixth information being used to indicate the priority information of uplink transmission;

[0105] There is an uplink transmission conflict. Uplink transmissions with lower priority are discarded based on priority information.

[0106] In conjunction with embodiments of the second aspect, in some embodiments, uplink transmission conflicts include at least one of the following:

[0107] The dynamic license DG uplink transmission on the first carrier conflicts with the configuration license CG uplink transmission on the second carrier.

[0108] The CG uplink transmission on the first carrier conflicts with the CG uplink transmission on the second carrier;

[0109] The DG uplink transmission on the first carrier conflicts with the DG uplink transmission on the second carrier;

[0110] Wherein, the first carrier and the second carrier are two carriers among the plurality of uplink carriers that do not support simultaneous uplink transmission.

[0111] In conjunction with embodiments of the second aspect, in some embodiments, the priority information includes at least one of the following:

[0112] DG uplink transmission priority;

[0113] Service priority associated with DG uplink transmission;

[0114] Priority of CG uplink transmission;

[0115] Service priority associated with CG uplink transmission.

[0116] In conjunction with the embodiments of the second aspect, in some embodiments, the first information includes: the random access channel (RACH) resources corresponding to each of the plurality of uplink carriers.

[0117] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0118] Random access information is sent to the network device based on the RACH resource corresponding to the third carrier among the plurality of uplink carriers; wherein the third carrier satisfies at least one of the following:

[0119] The terminal is randomly selected;

[0120] The terminal is selected based on the terminal type;

[0121] The terminal is selected based on the type of uplink service;

[0122] The terminal is selected based on the slice information.

[0123] In conjunction with embodiments of the second aspect, in some embodiments, each of the plurality of uplink carriers is associated with at least one of the following:

[0124] Terminal type, uplink service type, and slice information.

[0125] Thirdly, embodiments of this disclosure provide a communication method for a communication system, the communication system including network devices and terminals, the method comprising:

[0126] The network device sends first information to the terminal, the first information being used to indicate that one cell of the network device corresponds to multiple uplink carriers;

[0127] The network device sends a second message to the terminal, the second message indicating that at least two uplink carriers among the plurality of uplink carriers support the terminal to perform uplink transmission simultaneously.

[0128] Fourthly, embodiments of this disclosure provide a communication device, wherein the communication device is used to perform the method described in the first aspect or the second aspect.

[0129] Fifthly, according to an embodiment of this disclosure, a communication system includes a network device and a terminal, wherein,

[0130] The network device is configured to implement the method as described in the first aspect;

[0131] The terminal is configured to implement the method as described in the second aspect.

[0132] Sixthly, according to an embodiment of this disclosure, a storage medium stores instructions, wherein...

[0133] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method as described in the first aspect or the second aspect.

[0134] In a seventh aspect, an embodiment of this disclosure provides a program product comprising at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, they implement the method described in the first aspect or the second aspect.

[0135] It is understood that the aforementioned communication equipment, communication system, storage medium, program product, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0136] This disclosure provides embodiments of communication methods, communication devices, communication systems, storage media, and program products. In some embodiments, terms such as communication method and information processing method may be used interchangeably.

[0137] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

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

[0139] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0140] In the embodiments disclosed herein, "multiple" refers to two or more.

[0141] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0142] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0143] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0144] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing 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 is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0145] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0146] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0147] In some embodiments, 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 a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0148] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0149] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0150] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0151] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0152] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0153] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0154] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0155] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0156] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0157] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0158] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0159] As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102.

[0160] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.

[0161] In some embodiments, network device 102 may include at least one of access network device and core network device.

[0162] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system, but is not limited thereto.

[0163] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0164] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

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

[0166] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0167] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0168] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0169] In some implementations, the PCell in the CA is responsible for receiving system broadcast information, paging, and Radio Resource Control (RRC) signaling connection management and mobility, while the system broadcast information on the SCell is configured through RRC-specific signaling, and the SCell is responsible for data transmission and reception.

[0170] In some implementations, the PCell and at most one SCell may have a Physical Uplink Control Channel (PUCCH) to implement HARQ feedback and channel state information (CSI) reporting for all carriers within the PUCCH group.

[0171] In some implementations, when configuring SCells: each SCell is associated with an index, and UL carrier configuration information can be nested when configuring DL carrier configuration information. When configuring a carrier-aggregated SCell, only DL carriers can be configured, or both DL and UL carriers can be configured simultaneously; therefore, the number of DL carriers is always greater than the number of UL carriers.

[0172] In some implementations, due to the diversification of services, some services require higher UL throughput than DL throughput, and carrier aggregation configurations cannot meet these diverse service needs. Furthermore, there is a one-to-one association between DL and UL carriers, such as a System Information Block 2 (SIB2) linkage. This lack of flexibility in carrier management makes it impossible to meet the high UL data throughput requirements of services.

[0173] In some implementations, during mobility operations, changes to a PCell trigger a cell handover process, even if the target cell is a SCell within the CA, due to the PCell's functional responsibilities. During handover, key changes lead to MAC resets, Packet Data Convergence Protocol (PDCP) or Radio Link Control (RLC) reconstruction, resulting in service interruptions and packet loss, impacting service performance. Furthermore, if a PCell experiences a Radio Link Failure (RLF), regardless of whether the SCell experiences an RLF, it will trigger a PCell RLF, thereby triggering RRC connection reconstruction, which also leads to service interruptions and packet loss, impacting service performance.

[0174] In some implementations, traditional mobile communication system designs, such as CA, still assume a scenario dominated by DL (Deep Flow) services. However, with the development of communication technologies, such as in future 6G networks, there are use cases with high UL (Ultra-Low Flow) traffic loads, including remote driving, machine vision, and factory video surveillance. In these use cases, DL data traffic is limited, while UL traffic will be much larger. In PCells, Time Division Duplexing (TDD) configurations are typically designed to support more DL time slots, which is not UL-friendly. Reducing secondary cell SSBs (SSB-less SCells) can be primarily used to support the additional UL traffic in such scenarios with high UL usage. DL services and network signaling will be offloaded to PCells or other SCells. Since only UL traffic can be scheduled in SSB-less SCells, from an energy-saving perspective, the network can correspondingly shut down the transmitters in SSB-less SCells, thus anticipating significant network energy-saving gains.

[0175] In some implementations, a cell may have one DL carrier and two UL carriers, the two UL carriers being the Normal Uplink (NUL) and the Supplementary Uplink (SUL), respectively.

[0176] Introducing a SUL frequency can improve uplink coverage in the NR high-frequency band. Terminal uplink power is limited, and the NR spectrum has a relatively high frequency, resulting in high propagation loss, thus limiting uplink coverage. To improve uplink coverage, utilizing the LTE spectrum (relatively lower frequency) as the uplink SUL can enhance uplink coverage.

[0177] Among them, the two ULs and one DL belong to the same cell, and at most one Physical Uplink Shared channel (PUSCH) can be used for transmission at any given time.

[0178] Unless the network side explicitly instructs the terminal to use either NUL or SUL, the terminal determines the UL selection based on a measurement threshold. This threshold is configured and broadcast in the system broadcast.

[0179] The two UL carriers can be dynamically switched, indicated by Downlink Control Information (DCI).

[0180] In this implementation, although a cell supports two UL carriers, the two UL carriers cannot transmit data simultaneously. The purpose of SUL is mainly to enhance UL coverage, but it does not solve the problem of improving UL throughput.

[0181] Figure 2A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2A, a communication method according to an embodiment of the present disclosure includes:

[0182] In step S2101, terminal 101 sends third information to network device 102.

[0183] In some embodiments, network device 102 receives the third information.

[0184] Optionally, the access network device receives the third information.

[0185] In some embodiments, terminal 101 may report its capabilities to network device 102 via third information.

[0186] In some embodiments, the third information may be, for example, capability information.

[0187] In some embodiments, the reporting capability in the third information may also be default or omitted, in which case step S2101 can be omitted.

[0188] In some embodiments, the third information is used to indicate that the terminal supports carrier combinations and / or band combinations (BC) for simultaneous uplink transmission.

[0189] Optionally, when the third information includes a carrier combination, it indicates that the terminal supports simultaneous transmission of uplink information on multiple uplink carriers in the carrier combination.

[0190] Optionally, when the third information includes a frequency band combination, it indicates that the terminal supports simultaneous transmission of uplink information on multiple uplink carriers in that frequency band combination.

[0191] In some embodiments, third information may be used by network device 102 to configure or instruct based on the capabilities of terminal 101.

[0192] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0193] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0194] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.

[0195] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0196] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0197] In step S2102, network device 102 sends first information to terminal 101.

[0198] In some embodiments, terminal 101 receives the first information.

[0199] In some embodiments, network device 102 may be configured or instructed by first information.

[0200] In some embodiments, the first information may be configuration information.

[0201] In some embodiments, network device 102 can configure a cell to correspond to multiple uplink carriers (UL carriers) through first information.

[0202] Optionally, a cell may correspond to multiple uplink carriers, or a cell may include multiple uplink carriers.

[0203] Optionally, a cell may correspond to multiple uplink carriers, meaning that multiple uplink carriers can transmit uplink information within a single cell. These multiple uplink carriers may transmit uplink information simultaneously or separately.

[0204] Optionally, a cell may correspond to multiple uplink carriers, and the relevant configurations of these multiple uplink carriers, such as frequency domain information, may be the same as those of the single cell.

[0205] In some embodiments, network device 102 may indicate to terminal 101 via first information that a cell of network device 102 includes multiple uplink carriers.

[0206] In some embodiments, the first information may include carrier indexes of the plurality of uplink carriers, wherein each uplink carrier is associated with a carrier index.

[0207] In some embodiments, the first information can be broadcast via system information. Terminal 101 obtains the first information by receiving system information.

[0208] In some embodiments, the multiple uplink carriers configured by the network device 102 in the first information may be configured based on the network implementation; or, based on the capabilities of the terminal, such as the third information, multiple carriers may be configured in the carrier combination and / or frequency band combination supported by the terminal.

[0209] In some embodiments, the first information includes: the random access channel (RACH) resources corresponding to each uplink carrier among a plurality of uplink carriers.

[0210] Optionally, network device 102 can configure corresponding RACH resources for multiple uplink carriers of a cell using the first information.

[0211] Optionally, terminal 101 may perform random access based on RACH resources in accordance with the following steps S2104.

[0212] In step S2103, network device 102 sends second information to terminal 101.

[0213] In some embodiments, terminal 101 receives the second information.

[0214] In some embodiments, the second information may be indication information.

[0215] In some embodiments, network device 102 may indicate to terminal 101 through second information that at least two uplink carriers among a plurality of uplink carriers support simultaneous uplink transmission by the terminal.

[0216] Optionally, on the at least two uplink carriers, the terminal 101 can transmit uplink information simultaneously to improve uplink throughput.

[0217] In some embodiments, the at least two uplink carriers indicated by the network device 102 may be configured based on the network implementation, or may be configured based on the terminal's capabilities, such as third information, in a combination of carriers and / or frequency bands supported by the terminal.

[0218] Optionally, when the terminal reports the third information, the second information can be used to indicate whether the uplink carrier corresponding to the carrier combination and / or the frequency band combination supports simultaneous uplink transmission.

[0219] In some embodiments, step S2103 can be performed simultaneously.

[0220] Optionally, the second information can be the same as the first information.

[0221] Optionally, the second information and the first information can be carried in the same information or signaling. For example, the first information and the second information are information in the same signaling, used to configure a cell to correspond to multiple uplink carriers, and also used to indicate at least two uplink carriers that support the terminal to perform uplink transmission simultaneously.

[0222] In some embodiments, the second information is used to indicate at least one of the following:

[0223] Carrier indices of at least two uplink carriers;

[0224] The carrier types corresponding to multiple uplink carriers are either type 1 or type 2. Type 1 uplink carriers do not support simultaneous uplink transmission with other uplink carriers, while type 2 uplink carriers support simultaneous uplink transmission with other uplink carriers.

[0225] Multiple uplink carriers correspond to carrier groups, wherein different uplink carriers within one carrier group support simultaneous uplink transmission, while uplink carriers within different carrier groups do not support simultaneous uplink transmission.

[0226] Multiple uplink carriers can correspond to a single cell, such as a cell in the first information.

[0227] In some examples, the second information may directly indicate the carrier indices of at least two uplink carriers that support simultaneous uplink transmission. Alternatively, indicating at least two uplink carrier indices in the second information may implicitly indicate that the terminal can use the at least two carriers in connected mode to transmit uplink information simultaneously on at least two uplink carriers.

[0228] Optionally, the second information may indicate the carrier index of the uplink carrier that does not support simultaneous uplink transmission among multiple uplink carriers, thereby indirectly indicating the carrier index of at least two uplink carriers that support simultaneous uplink transmission.

[0229] Optionally, the second information may also indicate the uplink carriers that the terminal can use in the connected state, or the uplink carriers that the terminal can use in the connected state may be indicated by separate information. The uplink carriers that the terminal can use in the connected state may be included among multiple uplink carriers in a cell, and may include at least two uplink carriers that support simultaneous uplink transmission.

[0230] The uplink carriers that the terminal can use in connected mode or RRC connected mode (RRC_CONNECTED) can be indicated by the carrier index.

[0231] In some examples, the second information may indicate the carrier type corresponding to each of the multiple uplink carriers, or the carrier type corresponding to a subset of the multiple uplink carriers. For example, it may indicate the carrier type corresponding to uplink carriers that support simultaneous transmission.

[0232] Optionally, the carrier type can be replaced with the carrier purpose, or the carrier type can indicate the carrier purpose. The carrier type can be associated with a carrier index, such as indicating the carrier type or carrier purpose corresponding to a specific carrier index. In this case, the second information can indicate: the uplink carriers that the terminal can use in connected mode, and the corresponding carrier types.

[0233] Optionally, the first type of uplink carrier is an uplink carrier used for coverage enhancement and cannot be used for uplink transmission simultaneously with other uplink carriers. For example, when the second information indicates the carrier index of the first type of uplink carrier, the terminal cannot perform uplink transmission simultaneously on that uplink carrier and other uplink carriers.

[0234] Optionally, the second type of uplink carrier is an uplink carrier used for throughput enhancement and can perform uplink transmission simultaneously with other uplink carriers. For example, when the second information indicates the carrier index of the second type of uplink carrier, the terminal can perform uplink transmission simultaneously on that uplink carrier and other uplink carriers.

[0235] In some examples, the second information may indicate the carrier group corresponding to each of the multiple uplink carriers, or the carrier group corresponding to a subset of the multiple uplink carriers. For example, it may indicate the carrier group containing uplink carriers that support simultaneous transmission.

[0236] Optionally, network device 102 indicates the uplink carriers that the terminal can use in the connected state by indicating carrier packets.

[0237] Optionally, the network device 102 can configure multiple carrier groups through the second information, and the carriers within each carrier group can transmit uplink simultaneously. For example, the terminal can transmit uplink simultaneously on at least two uplink carriers within a carrier group.

[0238] Optionally, uplink carriers between different carrier groups cannot be transmitted simultaneously. For example, a terminal cannot perform uplink transmission simultaneously on two uplink carriers located in two different carrier groups.

[0239] In some embodiments, the second information can be sent via RRC signaling.

[0240] Optionally, the second information can be sent via RRC dedicated signaling.

[0241] In step S2104, terminal 101 sends random access information to network device 102.

[0242] In some embodiments, random access information includes, but is not limited to, messages exchanged during the random access process such as MSG1 and / or MSG3.

[0243] In some embodiments, in conjunction with the first information, corresponding RACH resources may be configured on multiple uplink carriers in a cell. Terminal 101 can select a third carrier from these multiple uplink carriers and initiate a random access procedure on the third carrier based on the RACH resources corresponding to the third carrier, such as sending MSG1 to network device 102.

[0244] In some embodiments, the third carrier may be randomly selected by the terminal. For example, the terminal may randomly select RACH resources on one of multiple uplink carriers to initiate a random access procedure.

[0245] In some embodiments, the third carrier may be selected by the terminal based on the terminal type.

[0246] Optionally, the terminal type can indicate terminals with different capabilities, such as device types that support different bandwidth capabilities.

[0247] Optionally, the terminal type can indicate an Internet of Things (IoT) device or a regular non-IoT terminal device.

[0248] Optionally, the terminal may select a carrier corresponding to the terminal type as the third carrier, depending on the terminal type.

[0249] In some embodiments, the third carrier may be selected by the terminal based on the uplink service type.

[0250] Optionally, the uplink service type can be at least one of the following: voice service, video service, high priority service, ultra-reliable low-latency communication (URLLC) service, IoT service, industrial internet service, sensor service, etc.

[0251] Optionally, the terminal may select a carrier corresponding to a different uplink service type as the third carrier.

[0252] In some embodiments, the third carrier may be selected by the terminal based on slice information.

[0253] Optionally, the terminal can select a carrier corresponding to the slice information as the third carrier based on the slice information.

[0254] In some embodiments, each of the plurality of uplink carriers is associated with at least one of the following:

[0255] Terminal type, uplink service type, and slice information.

[0256] Optionally, based on the association between each uplink carrier and the terminal type, the terminal can select a third carrier based on the terminal type.

[0257] Optionally, based on the association between each uplink carrier and the uplink service type, the terminal can select a third carrier based on the uplink service type.

[0258] Optionally, based on the association between each uplink carrier and the slice information, the terminal can select a third carrier based on the slice information.

[0259] In some embodiments, the terminal initiates a random access procedure to establish a connection with the network device 102 and enters the RRC connection state.

[0260] In step S2105, network device 102 schedules terminal 101 to perform uplink transmission.

[0261] In some embodiments, after the terminal enters the RRC connection state, the network device 102 can schedule the terminal 101 to perform uplink transmission.

[0262] In some embodiments, network device 102 may send DCI to terminal 101 to schedule terminal 101 to perform uplink transmission.

[0263] Optionally, network device 102 can simultaneously schedule uplink transmissions on different uplink carriers or schedule uplink grants (UL grants) on different uplink carriers through a DCI.

[0264] Optionally, network device 102 can schedule uplink transmission on at least two uplink carriers in the second information via DCI. For example, scheduling terminal 101 can schedule uplink transmission on the at least two uplink carriers simultaneously.

[0265] Optionally, network device 102 can retransmit via DCI scheduling terminal 101.

[0266] In some embodiments, the multiple uplink carriers included in a cell include the following two examples:

[0267] In one example, multiple uplink carriers correspond to the same Hybrid Automatic Repeat Request (HARQ) entity.

[0268] Optionally, HARQ entities are per cell (per cell HARQ entity), with each cell in different cells corresponding to one HARQ entity, and different carriers in a cell corresponding to the same HARQ entity.

[0269] Optionally, each HARQ entity may correspond to multiple HARQ processes.

[0270] Optionally, when DCI is used for retransmission scheduling, it can indicate that the carrier scheduled for retransmission is different from the carrier scheduled for initial transmission, but belongs to the same cell.

[0271] For example, the DCI used for scheduling initial transmissions indicates that the cell is serving cell 1, the uplink carrier is carrier 1, and the HARQ process identifier (ID) is HARQ process id 1. The DCI used for scheduling retransmissions can indicate that the cell is serving cell 1, the uplink carrier is carrier 2, and the HARQ process identifier is HARQ process id 1. Here, both carrier 1 and carrier 2 belong to the uplink carriers of serving cell 1.

[0272] In another example, among multiple uplink carriers, each uplink carrier corresponds to a HARQ entity.

[0273] Optionally, HARQ entities are per carrier (per carrier HARQ entity), and different uplink carriers in a cell may correspond to different HARQ entities.

[0274] Optionally, each HARQ entity may correspond to multiple HARQ processes.

[0275] In some embodiments, the configuration of network device 102 can be used to determine whether HARQ entities are based on cells or carriers.

[0276] In some embodiments, combining the two examples above, resources for uplink data can be specified during DCI scheduling of initial transmission or scheduling of retransmission.

[0277] Optionally, all uplink carriers of all serving cells are uniformly numbered, and the location of the time-frequency resources to be scheduled is indicated in the dynamic scheduling DCI by the carrier index. Here, "all serving cells" can refer to multiple serving cells of the configured CA.

[0278] For example, when all serving cells have uniform uplink carrier numbering, the carrier index corresponding to each uplink carrier is the number among all uplink carriers of the multiple serving cells configured for the terminal. For example, if the terminal is configured with a CA, the multiple serving cells refer to some or all of the serving cells configured for the terminal in the CA.

[0279] Optionally, the uplink carriers of a serving cell are uniformly numbered, while the uplink carriers of different serving cells are numbered in their respective spatial domains. In dynamic scheduling DCI, the location of the time-frequency resources to be scheduled is indicated by the serving cell index and the carrier index.

[0280] For example, the carrier index corresponding to each uplink carrier is the number of the uplink carrier in a cell within the first information.

[0281] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0282] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0283] In step S2106, terminal 101 simultaneously sends uplink information to network device 102 on at least two uplink carriers.

[0284] In some embodiments, network device 102 receives uplink information.

[0285] In some embodiments, uplink information may include uplink data.

[0286] In some embodiments, after receiving DCI, terminal 101 can simultaneously transmit uplink information on different uplink carriers to improve uplink throughput.

[0287] Optionally, terminal 101 transmits uplink information simultaneously on at least two uplink carriers.

[0288] In some embodiments, if in a cell of network device 102, the transceiver points (UL reception or TRP) corresponding to multiple uplink carriers are non-colocated, or in other words, multiple uplink carriers in a cell are not co-located at the network receiving point, terminal 101 can transmit uplink information on the uplink carrier according to the timing advance (TA) corresponding to the uplink carrier.

[0289] In some embodiments, in the above-described non-co-located scenario, network device 102 can send the fifth information to terminal 101 in advance, such as sending the fifth information before step S2106.

[0290] Optionally, the fifth piece of information is used to indicate the TA Group (TAG) corresponding to each uplink carrier among multiple uplink carriers, or to configure the TA Group to which each uplink carrier belongs. For example, each uplink carrier is associated with a TAG ID.

[0291] Optionally, the terminal 101 can obtain the TA information of each uplink carrier based on the fifth information, which facilitates uplink transmission based on the TA information of each uplink carrier.

[0292] In step S2107, network device 102 sends fourth information to terminal 101.

[0293] In some embodiments, terminal 101 receives fourth information.

[0294] In some embodiments, the fourth information may be indication information.

[0295] In some embodiments, network device 102 may send fourth information via DCI or RRC signaling.

[0296] In some embodiments, the fourth information is used to instruct the terminal to perform HARQ repetition. For example, network device 102 performs repetition via DCI scheduling terminal 101.

[0297] In some embodiments, the fourth information includes at least one of the following:

[0298] The carrier pattern for HARQ repetition; wherein the carrier pattern indicates the carriers for HARQ repetition in multiple uplink carriers;

[0299] Carrier index for HARQ retransmission;

[0300] The first piece of information contains the neighborhood index of a community.

[0301] Optionally, network device 102 may pre-configure multiple carrier patterns, indicating the index of the carrier pattern in the fourth information, wherein the index of each carrier pattern can determine one or more carrier indices that are repeatedly transmitted in that carrier pattern.

[0302] For example, in Dynamic Scheduling (DCI), a frequency hopping pattern that is repeatedly transmitted on multiple carriers can be indicated. Dynamic scheduling can be applied to Dynamic Grant (DG) scenarios. In Configurable Grant (CG) scenarios, the frequency hopping pattern that is repeatedly transmitted can be indicated via dedicated RRC signaling.

[0303] For example, by specifying at least one HARQ repetitive frequency hopping pattern through RRC signaling or system, an index is indicated in the configuration information of DCI or CG, associating it with one of the at least one repetitive frequency hopping patterns.

[0304] Optionally, network device 102 can indicate one or more carrier indices that need to be repeatedly transmitted via the fourth information. With all uplink carriers in all serving cells uniformly numbered, network device 102 indicates the carrier index, allowing terminal 101 to determine the corresponding carrier.

[0305] Optionally, network device 102 can indicate one or more carrier indices that need to be repeatedly transmitted, as well as the cell index of the cell where the carrier index is located, through the fourth information. In the case of unified uplink carrier numbering in a serving cell, network device 102 needs to indicate not only the carrier index, but also the cell index of the cell where the carrier index is located, so that terminal 101 can determine the corresponding carrier.

[0306] Optionally, when HARQ entities are organized by cell, each cell corresponds to one HARQ entity, and each HARQ entity corresponds to multiple HARQ processes. In this example, for repeated transmissions, frequency hopping transmission on different carriers can be supported to obtain frequency selection gain.

[0307] Alternatively, when HARQ entities are on a carrier-by-carrier basis, each uplink carrier in a cell can correspond to one HARQ entity.

[0308] In some embodiments, the fourth information is used to indicate the carrier index for HARQ retransmission by the terminal.

[0309] In one example, referring to Figure 2C, to support the simultaneous transmission of multiple uplink carriers in a cell, one or more uplink carriers can be scheduled simultaneously in a DCI (such as the DCI in step S2105). These one or more uplink carriers can belong to the same HARQ process or different HARQ processes.

[0310] For example, a DCI may schedule four uplink grants (UL grants) simultaneously. These four uplink grants may belong to the same uplink carrier, or to different uplink carriers, or some of the four uplink grants may belong to the same uplink carrier.

[0311] In this example, the uplink grants scheduled in a single DCI can belong to the same HARQ process, such as HARQ process ID #5. Assuming that the four uplink grants correspond to four transmission blocks (TBs), terminal 101 sends uplink information on the time-frequency resources corresponding to the four uplink grants. If the network receives all the information correctly (no NACK), then network device 102 schedules a new transmission; the new transmission is, for example, still the four uplink grants.

[0312] If, at this point, uplink transmission of a certain TB fails, such as network device 102 failing to successfully receive the uplink information of the second TB (or in other words, uplink grant 2 corresponds to NACK), network device 102 can schedule the failed uplink grant for retransmission. Terminal 101 retransmits on uplink grant 2. If the retransmission is received correctly, network device 102 continues to schedule the transmission of these four uplink grants.

[0313] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc., from one subject to another passes through other subjects, it can be interpreted as the message being forwarded from one subject to another via other subjects, or it can be interpreted as the message being sent from one subject to another without passing through other subjects. For example, step S2101.

[0314] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2107. For example, steps S2102 to S2103 may be implemented as independent embodiments, steps S2102 to S2103 and S2107 may be implemented as independent embodiments, and steps S2101 to S2103 may be implemented as independent embodiments, but are not limited thereto.

[0315] In some embodiments, steps S2101 and S2102 may be performed in an alternate order or simultaneously.

[0316] In some embodiments, at least one of steps S2101, S2104, S2105, S2106, and S2107 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0317] In some embodiments, at least one of steps S2101, S2104, S2105, and S2106 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0318] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0319] Figure 2B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2B, a communication method according to an embodiment of the present disclosure includes:

[0320] In step S2201, terminal 101 sends third information to network device 102.

[0321] In some embodiments, the implementation of step S2201 can be referred to the implementation of step S2101 in FIG2A, and will not be repeated here.

[0322] In step S2202, network device 102 sends first information to terminal 101.

[0323] In some embodiments, the implementation of step S2202 can be referred to the implementation of step S2102 in FIG2A, and will not be repeated here.

[0324] In step S2203, network device 102 sends second information to terminal 101.

[0325] In some embodiments, the implementation of step S2203 can be referred to the implementation of step S2103 in FIG2A, and will not be repeated here.

[0326] In step S2204, terminal 101 sends random access information to network device 102.

[0327] In some embodiments, the implementation of step S2204 can be referred to the implementation of step S2104 in FIG2A, and will not be repeated here.

[0328] In step S2205, network device 102 schedules terminal 101 to perform uplink transmission.

[0329] In some embodiments, the implementation of step S2205 can be referred to the implementation of step S2105 in FIG2A, and will not be repeated here.

[0330] In some embodiments, network device 102 may schedule terminal 101 to perform uplink transmission simultaneously on at least two uplink carriers, as described in steps S2105 to S2107 of FIG2A.

[0331] In some embodiments, when network device 102 schedules uplink transmission of terminal 101, it may instruct it to transmit on an uplink carrier that does not support simultaneous transmission. In this case, uplink transmissions on different uplink carriers may conflict.

[0332] Optionally, the conflict can be a time-domain conflict, such as uplink transmissions on different uplink carriers partially or completely overlapping in the time domain.

[0333] In step S2206, network device 102 sends the sixth information to terminal 101.

[0334] In some embodiments, terminal 101 receives sixth information.

[0335] In some embodiments, the sixth information may be configuration information or instruction information.

[0336] In some embodiments, the sixth information can be sent via DCI. For example, network device 102 performs uplink transmission through SCI scheduling terminal 101, and the sixth information is carried in the DCI. In this embodiment, steps S2205 and S2206 can be executed synchronously.

[0337] In some embodiments, the sixth information is used by the terminal to handle uplink transmission conflicts. For example, when there is an uplink transmission conflict between two carriers that do not support simultaneous uplink transmission, the terminal can handle it based on the sixth information.

[0338] In some embodiments, the sixth information is used to indicate the priority information of the uplink transmission.

[0339] Optionally, the sixth information indicates the priority of DG uplink transmissions, such as the priority of DG PUSCH.

[0340] Optionally, the sixth piece of information indicates the service priority associated with the DG uplink transmission, such as the priority of the service associated with the DG PUSCH.

[0341] Optionally, the sixth information indicates the priority of the CG uplink transmission, such as the priority of the CG PUSCH.

[0342] Optionally, the sixth piece of information indicates the service priority associated with the CG uplink transmission, such as the priority of the service associated with the CG PUSCH.

[0343] Optionally, services associated with DG uplink transmission and / or services associated with CG uplink transmission can be identified by a Logical Channel Identifier (LCID).

[0344] In step S2207, terminal 101 processes the uplink transmission conflict according to the sixth information.

[0345] In some embodiments, uplink transmission conflicts include at least one of the following:

[0346] Dynamic licensed DG uplink transmission on the first carrier conflicts with configuration licensed CG uplink transmission on the second carrier, such as a conflict between the DG PUSCH on the first carrier and the CG PUSCH on the second carrier.

[0347] CG uplink transmission on the first carrier conflicts with CG uplink transmission on the second carrier, such as CG PUSCH on the first carrier conflicting with CG PUSCH on the second carrier.

[0348] DG uplink transmission on the first carrier conflicts with DG uplink transmission on the second carrier, such as DG PUSCH on the first carrier conflicting with DG PUSCH on the second carrier.

[0349] Among them, the first carrier and the second carrier are two carriers that do not support simultaneous uplink transmission among multiple uplink carriers.

[0350] In some embodiments, based on the priority information indicated by the sixth information, terminal 101 handles any of the above uplink transmission conflicts.

[0351] Optionally, if the DG uplink transmission of the first carrier conflicts with the CG uplink transmission of the second carrier, the terminal 101 determines, based on priority information, to discard either the DG uplink transmission of the first carrier or the CG uplink transmission of the second carrier. For example, the uplink transmission with lower priority is discarded.

[0352] Optionally, if the CG uplink transmission of the first carrier conflicts with the CG uplink transmission of the second carrier, the terminal 101 determines, based on priority information, to discard the CG uplink transmission of the first carrier or the CG uplink transmission of the second carrier. For example, the uplink transmission with lower priority is discarded.

[0353] Optionally, if the DG uplink transmission of the first carrier conflicts with the DG uplink transmission of the second carrier, the terminal 101 determines, based on priority information, to discard either the DG uplink transmission of the first carrier or the DG uplink transmission of the second carrier. For example, the uplink transmission with lower priority is discarded.

[0354] In some embodiments, step S2207 is optional. For example, network device 102 does not schedule services with uplink transmission conflicts, or in other words, network device 102 does not schedule simultaneous transmission on different carriers that do not support simultaneous transmission. As another example, as illustrated in FIG2A, network device 102 schedules uplink transmission on at least two uplink carriers, which support simultaneous transmission by terminal 101.

[0355] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2207. For example, steps S2202 to S2203 may be implemented as independent embodiments, and steps S2202 to S2203 and S2206 to S2207 may be implemented as independent embodiments, but are not limited thereto.

[0356] In some embodiments, steps S2201 and S2202 may be performed in an interchangeable order or simultaneously. Steps S2205 and S2206 may be performed in an interchangeable order or simultaneously.

[0357] In some embodiments, at least one of steps S2201, S2204, S2205, S2206, and S2207 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0358] In some embodiments, at least one of steps S2201, S2204, and S2205 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0359] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0360] Figure 3A is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3A, a communication method according to an embodiment of the present disclosure includes:

[0361] In step S3101, network device 102 sends first information to terminal 101.

[0362] In some embodiments, the implementation of step S3101 can be referred to the implementation of step S2102 in FIG2A.

[0363] In some embodiments, each of the multiple uplink carriers in a cell within the first information can be configured with RACH resources.

[0364] In step S3102, network device 102 sends second information to terminal 101.

[0365] In some embodiments, the implementation of step S3102 can be referred to the implementation of step S2103 in FIG2A.

[0366] In some embodiments, the second information may indicate at least one of the following:

[0367] The different uplink carrier indices that the terminal can use in the connected state, wherein the different uplink carrier indices include the indices of the at least two uplink carriers;

[0368] The carrier type corresponding to different uplink carrier indices, wherein the carrier type is a first type or a second type, the uplink carrier of the first type does not support simultaneous uplink transmission with other uplink carriers, and the uplink carrier of the second type supports simultaneous uplink transmission with other uplink carriers;

[0369] Each uplink carrier in a plurality of uplink carriers corresponds to a carrier group, wherein different uplink carriers located within one carrier group support simultaneous uplink transmission, while uplink carriers located in different carrier groups do not support simultaneous uplink transmission.

[0370] In some embodiments, the terminal may report supported carrier combinations and / or frequency band combinations based on its capabilities. The second information may indicate whether the uplink carrier involved in the frequency band combination or carrier combination supported by the terminal supports simultaneous transmission.

[0371] In some embodiments, when an uplink transmission conflict exists, the terminal can handle the conflict based on priority information.

[0372] In some embodiments, for multiple uplink carriers of a cell, HARQ entities can be configured on a cell-by-cell basis or on a carrier-by-carrier basis.

[0373] Optionally, during repeated transmissions, the terminal may perform frequency hopping transmission based on the carrier pattern or carrier index indicated by the network device.

[0374] Optionally, the carrier index can be a unified number for all uplink carriers of all serving cells of the CA, or a unified number for the uplink carriers of a single serving cell.

[0375] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0376] Figure 3B is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, a communication method according to an embodiment of the present disclosure includes:

[0377] In step S3201, network device 102 sends first information to terminal 101.

[0378] In some embodiments, the implementation of step S3201 can be referred to the implementation of step S2102 in FIG2A, and will not be repeated here.

[0379] In step S3202, network device 102 sends second information to terminal 101.

[0380] In some embodiments, the implementation of step S3202 can be referred to the implementation of step S2103 in FIG2A, and will not be repeated here.

[0381] In step S3203, terminal 101 simultaneously sends uplink information to network device 102 on at least two uplink carriers.

[0382] In some embodiments, the implementation of step S3203 can be referred to the implementation of step S2106 in FIG2A, and will not be repeated here.

[0383] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0384] Figure 3C is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3C, a communication method according to an embodiment of the present disclosure includes:

[0385] In step S3301, network device 102 sends first information to terminal 101.

[0386] In some embodiments, the implementation of step S3301 can be referred to the implementation of step S2102 in FIG2A, and will not be repeated here.

[0387] In step S3302, network device 102 sends second information to terminal 101.

[0388] In some embodiments, the implementation of step S3302 can be referred to the implementation of step S2103 in FIG2A, and will not be repeated here.

[0389] In step S3303, network device 102 sends the sixth information to terminal 101.

[0390] In some embodiments, the implementation of step S3303 can be found in the implementation of step S2206 in FIG2B, and will not be repeated here.

[0391] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0392] In the method provided in this disclosure, a cell contains multiple carriers, and at least two of the multiple carriers can transmit UL data simultaneously. To facilitate understanding of the embodiments of this disclosure, some examples are listed below:

[0393] Example 1: Configuration

[0394] Option 1: The system broadcasts a configuration that a cell contains multiple UL carriers.

[0395] Optionally, each UL carrier is associated with an index.

[0396] Optionally, each UL carrier can be configured with RACH resources, and the UE can choose to randomly select a RACH resource on any UL carrier to initiate a random access procedure. Alternatively, it can select a RACH resource on the corresponding UL carrier to initiate a random access procedure based on the UE type, the type of service initiated by the UE, or the slice selected by the UE.

[0397] Optionally, the UL carrier can be associated with the UE type, service type, or slice information.

[0398] Optionally, the UE type can be an IoT device, a normal UE device, a terminal type with different capabilities, such as a device type with different bandwidth support capabilities, etc.

[0399] Optionally, the service type can be voice service, video service, high-priority service, URLLC service, IoT service, industrial internet service, sensor service, etc.

[0400] Optional Example 2: Configure the UL carriers that the UE can use in RRC connection state, and the purpose of each usable UL carrier, via RRC dedicated signaling.

[0401] Optionally, an index for each UL carrier can be configured.

[0402] Optionally, the UL carrier can be used for purposes such as coverage enhancement and throughput enhancement. The coverage-type carrier does not perform uplink transmission simultaneously with other UL carriers, while the throughput-type carrier can perform uplink transmission simultaneously.

[0403] Optional Example 3: Configure the UL carrier that the UE can use in RRC connection state via RRC dedicated signaling.

[0404] Optionally, the UL carriers that can be used can be configured with multiple groups via RRC signaling. Carriers within each group can transmit uplink simultaneously, while carriers in different carrier groups cannot transmit simultaneously.

[0405] Optional Example 4: Based on the capabilities reported by the UE, indicate the carrier combinations or band combinations that can be transmitted simultaneously, such as BC capabilities, and configure whether simultaneous transmission is possible on the network side.

[0406] Optional Example 5: If the dynamically scheduled DG and the configured licensed CG on two carriers that cannot be transmitted simultaneously conflict, the decision to discard the DG or the CG is based on the priority indication configured on the network side. The priority can be based on the service (e.g., LCID) priority associated with the DG and CG, or simply the priority of the DG and the CG.

[0407] If the configured licensed CG on two carriers that cannot be transmitted simultaneously conflicts with the configured licensed CG, the priority indicator configured on the network side is used to determine which CG to discard. The priority can be based on the service (e.g., LCID) priority associated with the CG.

[0408] If two dynamically scheduled DGs on two carriers that cannot be transmitted simultaneously conflict with each other, the priority indicator configured on the network side will determine which DG to discard. The priority can be based on the priority of the service associated with the DG (e.g., LCID).

[0409] Alternatively, the network side can guarantee that no conflict will occur.

[0410] Optionally, the different alternative examples in Example 1 can be implemented independently or in combination.

[0411] Example 2: Regarding HARQ entities, HARQ buffers, retransmissions, and repetitions.

[0412] Optionally, Embodiment 2 can be combined with any one or more of the optional embodiments in Embodiment 1.

[0413] Optional Example 1: Per-cell HARQ entity

[0414] Optionally, multiple UL carriers belong to the same cell, each cell corresponds to one HARQ entity, and each HARQ entity corresponds to multiple HARQ processes. For retransmission scheduling, the carrier to be retransmitted can be the same as the initial transmission cell, but with a different carrier. For example, the initial transmission DCI indicates the cell as serving cell1, carrier 1, and HARQ process ID 1; the retransmission scheduling DCI can indicate the cell as serving cell1, carrier 2, and HARQ process ID 1; where carrier 1 and carrier 2 are both UL carriers belonging to serving cell1.

[0415] Optionally, multiple UL carriers belong to the same cell, each cell corresponds to one HARQ entity, and each HARQ entity corresponds to multiple HARQ processes. For repeated transmissions, frequency hopping transmission on different carriers can be supported to obtain frequency selection gain. Two examples are possible:

[0416] In one example: In Dynamic Scheduling (DCI), a frequency hopping pattern for repeated transmissions on multiple carriers is indicated. If it's a CG (Cyclic Grid), the repeated frequency hopping pattern is indicated via dedicated RRC (Regulatory Control Code) signaling.

[0417] In another example: RRC signaling or the system specifies a frequency hopping pattern that is repeatedly transmitted on at least one or more carriers, and an index in the DCI or CG indicates that the pattern is associated with at least one of the repeated frequency hopping patterns.

[0418] Optional Example 2: Per-carrier HARQ entity

[0419] Optionally, multiple UL carriers belong to the same cell, each carrier corresponds to one HARQ entity, and each HARQ entity corresponds to multiple HARQ processes. In DCI scheduling, the resources for uplink data transmission can be specified as follows:

[0420] In one example: all uplink carriers of all serving cells are uniformly numbered, and the carrier index used in dynamic scheduling indicates the location of the time-frequency resources to be scheduled.

[0421] In another example: the uplink carrier of a serving cell is uniformly numbered, while the uplink carriers of different serving cells are numbered in their respective spatial domains. In dynamic scheduling, the serving cell index and carrier index are used to indicate the location of the time-frequency resources to be scheduled.

[0422] For Option 1 and Option 2 above, as shown in Figure 2C, to support the simultaneous transmission of a certain number of uplink carriers within a cell, multiple uplink carrier UL grants can be scheduled simultaneously within a single DCI. These multiple UL grants can belong to the same HARQ process or different HARQ processes. If the UL grants scheduled in a DCI belong to the same HARQ process, for example, four UL grants, the UE transmits uplink on the corresponding time-frequency resources. If the network receives all transmissions correctly, a new transmission is scheduled, for example, still four UL grants. If uplink transmission on a certain UL carrier fails at this point, the network schedules the failed carrier for retransmission. If the retransmission is received correctly, the four UL grants are scheduled for continued transmission.

[0423] Example 3: TA of a non-colocated UL reception point

[0424] If multiple UL carriers in a cell are not co-located at the network receiving point, the network side will configure the TA group to which each UL carrier belongs, for example, each UL carrier is associated with a TAG ID.

[0425] Optionally, Embodiment 3 can be combined with any one or more of the optional embodiments in Embodiment 1. And / or, Embodiment 3 can be combined with any one or more of the optional embodiments in Embodiment 2.

[0426] In this embodiment, a single cell can be associated with multiple uplink carriers, with at least two UL carriers capable of simultaneous transmission, thereby improving uplink throughput. It supports per-serving-cell HARQ entities to enable cross-carrier retransmission and cross-carrier duplicate transmission. It also supports a single HARQ process scheduling multiple UL transmissions simultaneously, further enhancing uplink throughput. Finally, it supports per-carrier TAG configuration.

[0427] In this embodiment of the disclosure, UL throughput can be improved to meet the service requirements of high uplink throughput, such as services in future 6G, and scenarios where cameras are used as terminals.

[0428] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0429] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0430] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0431] Figure 4A is a schematic diagram of the structure of a network device according to an embodiment of this disclosure. The network device 4100 is used to perform any of the above methods. In some embodiments, as shown in Figure 4A, the network device 4100 may include at least one of a transceiver module 4101, a processing module 4102, etc. In some embodiments, the transceiver module 4101 is used to send first information to a terminal, the first information indicating that a cell of the network device corresponds to multiple uplink carriers. The transceiver module 4101 is also used to send second information to the terminal, the second information indicating that among the multiple uplink carriers, at least two uplink carriers support simultaneous uplink transmission by the terminal. Optionally, the transceiver module is used to perform at least one of the communication steps (e.g., steps S2101, S2102, S2103, S2107, S2206, but not limited thereto) performed by the network device in any of the above methods, which will not be elaborated further here. Optionally, the above processing module is used to perform at least one of the other steps (such as step S2105, but not limited thereto) performed by the network device 102 in any of the above methods, which will not be described in detail here.

[0432] Figure 4B is a schematic diagram of the terminal structure proposed in an embodiment of this disclosure. Terminal 4200 is used to execute any of the above methods. In some embodiments, as shown in Figure 4B, terminal 4200 may include at least one of a transceiver module 4201, a processing module 4202, etc. In some embodiments, the transceiver module 4201 is used to receive first information sent by a network device, the first information indicating that a cell of the network device corresponds to multiple uplink carriers; the transceiver module 4201 is also used to receive second information sent by the network device, the second information indicating that among the multiple uplink carriers, at least two uplink carriers support simultaneous uplink transmission by the terminal. Optionally, the transceiver module is used to execute at least one of the communication steps (e.g., steps S2104, S2106, but not limited thereto) performed by the network device in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to execute at least one of other steps (e.g., step S2207, but not limited thereto) performed by the network device 102 in any of the above methods, which will not be elaborated here.

[0433] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0434] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0435] In some embodiments, the processing module can be interchanged with the processor, and the transceiver module can be interchanged with the transceiver.

[0436] Figure 5A is a schematic diagram of the structure of the communication device 5100 proposed in an embodiment of this disclosure. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0437] As shown in Figure 5A, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0438] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102, S2103, S2104, S2106, S2107, S2206, but not limited thereto), and the processor 5101 performs at least one of other steps (e.g., steps S2105, S2207, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0439] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5103 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5103 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5102 and can be used to receive data and / or instructions from the memory 5102 or other devices, and can be used to send data and / or instructions to the memory 5102 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5102 and send the data and / or instructions to the processor 5101.

[0440] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0441] Figure 5B is a schematic diagram of the structure of chip 5200 according to an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, please refer to the schematic diagram of chip 5200 shown in Figure 5B, but it is not limited thereto.

[0442] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

[0443] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.

[0444] In some embodiments, the interface circuit 5202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101, S2102, S2103, S2104, S2106, S2107, S2206, but not limited thereto). The interface circuit 5202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 5202 performing data and / or instruction interaction between the processor 5201, chip 5200, memory 5203, or transceiver device. In some embodiments, the processor 5201 performs at least one of other steps (e.g., steps S2105, S2207, but not limited thereto). The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0445] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0446] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0447] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods. Industrial applicability

[0448] A cell includes multiple carriers. Network equipment can indicate to the terminal at least two carriers that can transmit uplink information simultaneously, so that the terminal can transmit uplink information on at least two carriers, thereby improving uplink throughput and meeting diverse service needs.

Claims

1. A communication method performed by a network device, the method comprising: Send first information to the terminal, the first information being used to indicate that one cell of the network device corresponds to multiple uplink carriers; Send a second message to the terminal, the second message indicating that at least two uplink carriers among the plurality of uplink carriers support the terminal to perform uplink transmission simultaneously.

2. The method as described in claim 1, wherein, The second information is used to indicate at least one of the following: The carrier index of the at least two uplink carriers; The carrier types corresponding to the plurality of uplink carriers are either a first type or a second type. The uplink carrier of the first type does not support simultaneous uplink transmission with other uplink carriers, while the uplink carrier of the second type supports simultaneous uplink transmission with other uplink carriers. The multiple uplink carriers correspond to carrier groups, wherein different uplink carriers located in one carrier group support simultaneous uplink transmission, while uplink carriers located in different carrier groups do not support simultaneous uplink transmission.

3. The method as described in any one of claims 1 to 2, wherein, The method further includes: Receive third information sent by the terminal, the third information being used to indicate at least one of the following: The terminal is capable of simultaneously performing uplink transmission of carrier combinations; The terminal can simultaneously perform uplink transmission frequency band combinations; The second information is used to indicate whether the uplink carrier corresponding to the carrier combination and / or the frequency band combination supports simultaneous uplink transmission.

4. The method as described in any one of claims 1 to 3, wherein, The multiple uplink carriers correspond to the same Hybrid Automatic Repeat Request (HARQ) entity; or, among the multiple uplink carriers, each uplink carrier corresponds to a HARQ entity.

5. The method of claim 4, wherein, The method further includes: A fourth message is sent to the terminal, which instructs the terminal to perform HARQ retransmission.

6. The method of claim 5, wherein, The fourth piece of information includes at least one of the following: A carrier pattern for HARQ repetition; wherein the carrier pattern indicates the carriers for HARQ repetition in the plurality of uplink carriers; Carrier index for HARQ retransmission; The cell index of a community.

7. The method as described in any one of claims 4 to 6, wherein, The carrier index corresponding to each uplink carrier is a number among all uplink carriers of the multiple serving cells configured for the terminal, or a number among the uplink carriers of a single cell.

8. The method according to any one of claims 1 to 7, wherein, The method further includes: A fifth message is sent to the terminal, the fifth message being used to indicate the timing advance TA group corresponding to each of the plurality of uplink carriers, wherein the transceiver points corresponding to the plurality of uplink carriers are non-co-located.

9. The method according to any one of claims 1 to 8, wherein, The method further includes: A sixth message is sent to the terminal, the sixth message being used to indicate the priority information of uplink transmission, and the sixth message being used by the terminal to handle uplink transmission conflicts.

10. The method of claim 9, wherein, The uplink transmission conflict includes at least one of the following: The dynamic license DG uplink transmission on the first carrier conflicts with the configuration license CG uplink transmission on the second carrier. The CG uplink transmission on the first carrier conflicts with the CG uplink transmission on the second carrier; The DG uplink transmission on the first carrier conflicts with the DG uplink transmission on the second carrier; Wherein, the first carrier and the second carrier are two carriers among the plurality of uplink carriers that do not support simultaneous uplink transmission.

11. The method of claim 9 or 10, wherein, The priority information includes at least one of the following: DG uplink transmission priority; Service priority associated with DG uplink transmission; Priority of CG uplink transmission; Service priority associated with CG uplink transmission.

12. The method as claimed in any one of claims 1 to 11, wherein, The first information includes: the random access channel (RACH) resources corresponding to each of the plurality of uplink carriers.

13. The method of claim 12, wherein, The method further includes: The terminal receives random access information, wherein the random access information is sent by the terminal based on the RACH resource corresponding to the third carrier among the plurality of uplink carriers, wherein the third carrier satisfies at least one of the following: The terminal is randomly selected; The terminal is selected based on the terminal type; The terminal is selected based on the type of uplink service; The terminal is selected based on the slice information.

14. The method of claim 13, wherein, Each of the plurality of uplink carriers is associated with at least one of the following: Terminal type, uplink service type, and slice information.

15. A communication method, executed by a terminal, the method comprising: The network device receives first information, which indicates that one cell of the network device corresponds to multiple uplink carriers. The network device receives second information, which indicates that at least two uplink carriers among the plurality of uplink carriers support the terminal to perform uplink transmission simultaneously.

16. The method of claim 15, wherein, The second information is used to indicate at least one of the following: The carrier index of the at least two uplink carriers; The carrier types corresponding to the plurality of uplink carriers are either a first type or a second type. The uplink carrier of the first type does not support simultaneous uplink transmission with other uplink carriers, while the uplink carrier of the second type supports simultaneous uplink transmission with other uplink carriers. The multiple uplink carriers correspond to carrier groups; wherein, different uplink carriers located in one carrier group support simultaneous uplink transmission, while uplink carriers located in different carrier groups do not support simultaneous uplink transmission.

17. The method of any one of claims 15 to 16, wherein, The method further includes: Send a third message to the network device, the third message indicating at least one of the following: The terminal is capable of simultaneously performing uplink transmission of carrier combinations; The terminal can simultaneously perform uplink transmission frequency band combinations; The second information is used to indicate whether the uplink carrier corresponding to the carrier combination and / or the frequency band combination supports simultaneous uplink transmission.

18. The method as claimed in any one of claims 15 to 17, wherein, The multiple uplink carriers correspond to the same Hybrid Automatic Repeat Request (HARQ) entity; or, in the multiple uplink carriers, each uplink carrier corresponds to a HARQ entity.

19. The method of claim 18, wherein, The method further includes: The terminal receives a fourth message sent by the network device, the fourth message being used to instruct the terminal to perform HARQ retransmission.

20. The method of claim 18, wherein, The fourth piece of information includes at least one of the following: A carrier pattern for HARQ repetition; wherein the carrier pattern indicates the carriers for HARQ repetition in the plurality of uplink carriers; Carrier index for HARQ retransmission; The cell index of a community.

21. The method as claimed in any one of claims 18 to 20, wherein, The carrier index corresponding to each uplink carrier is a number among all uplink carriers of the multiple serving cells configured for the terminal, or a number among the uplink carriers of a single cell.

22. The method according to any one of claims 15 to 21, wherein, The method further includes: The network device receives a fifth message sent by the network device, the fifth message being used to indicate the timing advance TA group corresponding to each of the plurality of uplink carriers, wherein the network device includes a plurality of non-co-located transceiver points corresponding to the cell.

23. The method as claimed in any one of claims 15 to 22, wherein, The method further includes: Receive the sixth information sent by the network device, the sixth information being used to indicate the priority information of uplink transmission; There is an uplink transmission conflict. Uplink transmissions with lower priority are discarded based on priority information.

24. The method of claim 23, wherein, The uplink transmission conflict includes at least one of the following: The dynamic license DG uplink transmission on the first carrier conflicts with the configuration license CG uplink transmission on the second carrier. The CG uplink transmission on the first carrier conflicts with the CG uplink transmission on the second carrier; The DG uplink transmission on the first carrier conflicts with the DG uplink transmission on the second carrier; Wherein, the first carrier and the second carrier are two carriers among the plurality of uplink carriers that do not support simultaneous uplink transmission.

25. The method of claim 23 or 24, wherein, The priority information includes at least one of the following: DG uplink transmission priority; Service priority associated with DG uplink transmission; Priority of CG uplink transmission; Service priority associated with CG uplink transmission.

26. The method as claimed in any one of claims 15 to 25, wherein, The first information includes: the random access channel (RACH) resources corresponding to each of the plurality of uplink carriers.

27. The method of claim 26, wherein, The method further includes: Random access information is sent to the network device based on the RACH resource corresponding to the third carrier among the plurality of uplink carriers; wherein the third carrier satisfies at least one of the following: The terminal is randomly selected; The terminal is selected based on the terminal type; The terminal is selected based on the type of uplink service; The terminal is selected based on the slice information.

28. The method of claim 27, wherein, Each of the plurality of uplink carriers is associated with at least one of the following: Terminal type, uplink service type, and slice information.

29. A communication method for a communication system, the communication system including network devices and terminals, the method comprising: The network device sends first information to the terminal, the first information being used to indicate that one cell of the network device corresponds to multiple uplink carriers; The network device sends a second message to the terminal, the second message indicating that at least two uplink carriers among the plurality of uplink carriers support the terminal to perform uplink transmission simultaneously.

30. A communication device, wherein, The communication device is used to perform the method according to any one of claims 1 to 14 or any one of claims 15 to 28.

31. A communication system comprising network equipment and a terminal, wherein, The network device is configured to implement the method as described in any one of claims 1 to 14; The terminal is configured to implement the method as described in any one of claims 15 to 28.

32. A storage medium storing instructions, wherein, When the instructions are executed on the communication device, the communication device performs the method as described in any one of claims 1 to 14 or any one of claims 15 to 28.

33. A program product comprising at least one of a program and instructions, wherein, When at least one of the programs or instructions is executed by a communication device, it implements the method as described in any one of claims 1 to 14 or any one of claims 15 to 28.

Images