Carrier aggregation method and device

CN119817163APending Publication Date: 2025-04-11BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380010530.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-08-09
Publication Date
2025-04-11

AI Technical Summary

Technical Problem

When the terminal triggers carrier selection or reselect, how to effectively determine the candidate carrier and improve the efficiency and accuracy of carrier aggregation.

Method used

The indication information is sent to the network device through the first terminal, including the first indication information, the second indication information and the third indication information, for indicating the carrier supported by the second terminal, the preferred supported carrier, and the carrier supported by the first target address. The network device scheduling side link authorization for the first terminal according to this information.

Benefits of technology

The accuracy of side link authorization scheduling and the quality of side link communication between the first terminal and the second terminal are improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119817163A_ABST
    Figure CN119817163A_ABST
Patent Text Reader

Abstract

The present disclosure relates to a carrier aggregation method and device, the method comprising: sending indication information to a network device, the indication information comprising at least one of first indication information, second indication information, and third indication information; wherein the first indication information is used for indicating a carrier supported by the second terminal, the second indication information is used for indicating a carrier preferably supported by the second terminal, the third indication information is used for indicating a carrier supported by the first target address, and the second terminal is a terminal establishing unicast connection with the first terminal. Therefore, the network device can acquire the carrier supported by the second terminal, the carrier supported by the first target address and the like, and then can schedule the sidelink authorization for the first terminal based on the information, thereby improving the accuracy of sidelink authorization scheduling, and improving the user experience. And the side communication quality between the first terminal and the second terminal is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Carrier aggregation method and device Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a carrier aggregation method and apparatus. Background Art

[0002] In order to meet the requirements of single-user peak rate and system capacity improvement, the system transmission bandwidth can be increased, such as by adopting carrier aggregation (CA). SL communication can use carrier aggregation.

[0003] Summary of the Invention

[0004] The method disclosed in the present invention can be used to solve the technical problem of "how to determine a candidate carrier when a terminal triggers carrier selection or reselection".

[0005] The embodiments of the present disclosure provide a carrier aggregation method and apparatus.

[0006] According to a first aspect of an embodiment of the present disclosure, a carrier aggregation method is provided, which is performed by a first terminal. The method includes:

[0007] Sending indication information to the network device, where the indication information includes at least one of first indication information, second indication information, and third indication information;

[0008] The first indication information is used to indicate the carrier supported by the second terminal, the second indication information is used to indicate the carrier preferred by the second terminal, the third indication information is used to indicate the carrier supported by the first target address, and the second terminal is a terminal that establishes a unicast connection with the first terminal.

[0009] According to a second aspect of an embodiment of the present disclosure, a carrier aggregation method is proposed, which is performed by a network device. The method includes:

[0010] Receiving indication information sent by the first terminal device, where the indication information includes at least one of first indication information, second indication information, and third indication information;

[0011] The first indication information is used to indicate the carrier supported by the second terminal, the second indication information is used to indicate the carrier preferred by the second terminal, the third indication information is used to indicate the carrier supported by the first target address, and the second terminal is a terminal that establishes a unicast connection with the first terminal.

[0012] According to a third aspect of an embodiment of the present disclosure, a carrier aggregation method is proposed, which is performed by a second terminal. The method includes:

[0013] Send indication information to the first terminal device, the indication information including first indication information and / or second indication information, wherein the first indication information is used to indicate the carrier supported by the second terminal, and the second indication information is used to indicate the carrier preferred to be supported by the second terminal.

[0014] According to a fourth aspect of the embodiments of the present disclosure, a carrier aggregation method is proposed, characterized by including:

[0015] The first terminal device sends indication information to the network device, where the indication information includes at least one of first indication information, second indication information, and third indication information;

[0016] The network device receives the indication information;

[0017] The first indication information is used to indicate the carrier supported by the second terminal, the second indication information is used to indicate the carrier preferred by the second terminal, the third indication information is used to indicate the carrier supported by the first target address, and the second terminal is a terminal that establishes a unicast connection with the first terminal.

[0018] According to a fifth aspect of an embodiment of the present disclosure, a first terminal is provided, including:

[0019] a transceiver module, configured to send indication information to the network device, wherein the indication information includes at least one of first indication information, second indication information, and third indication information;

[0020] The first indication information is used to indicate the carrier supported by the second terminal, the second indication information is used to indicate the carrier preferred by the second terminal, the third indication information is used to indicate the carrier supported by the first target address, and the second terminal is a terminal that establishes a unicast connection with the first terminal.

[0021] According to a sixth aspect of an embodiment of the present disclosure, a network device is provided, including:

[0022] a transceiver module, configured to receive indication information sent by the first terminal device, where the indication information includes at least one of first indication information, second indication information, and third indication information;

[0023] The first indication information is used to indicate the carrier supported by the second terminal, the second indication information is used to indicate the carrier preferred by the second terminal, the third indication information is used to indicate the carrier supported by the first target address, and the second terminal is a terminal that establishes a unicast connection with the first terminal.

[0024] According to a seventh aspect of an embodiment of the present disclosure, a second terminal is provided, including:

[0025] The transceiver module is used to send indication information to the first terminal device, and the indication information includes first indication information and / or second indication information, wherein the first indication information is used to indicate the carrier supported by the second terminal, and the second indication information is used to indicate the carrier preferred to be supported by the second terminal.

[0026] According to an eighth aspect of an embodiment of the present disclosure, a first terminal is provided, including:

[0027] one or more processors;

[0028] The first terminal is used to execute the carrier aggregation method according to the embodiment of the first aspect.

[0029] According to a ninth aspect of an embodiment of the present disclosure, a network device is provided, including:

[0030] one or more processors;

[0031] The network device is used to execute the carrier aggregation method according to the embodiment of the second aspect.

[0032] According to a tenth aspect of an embodiment of the present disclosure, a second terminal is provided, including:

[0033] one or more processors;

[0034] The second terminal is used to execute the carrier aggregation method according to the embodiment of the third aspect.

[0035] According to the eleventh aspect of the embodiments of the present disclosure, a communication system is proposed, including a first terminal, a network device, and a second terminal, wherein the first terminal is configured to implement the carrier aggregation method described in the embodiment of the first aspect, the network device is configured to implement the carrier aggregation method described in the embodiment of the second aspect, and the second terminal is configured to implement the carrier aggregation method described in the embodiment of the third aspect.

[0036] According to the twelfth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the carrier aggregation method as described in any one of the first, second, and third aspects.

[0037] In an embodiment of the present disclosure, the first terminal can report one or more of the carriers supported by the second terminal with which a unicast connection is established, the carriers preferred by the second terminal, and the carriers supported by the first target address to a network device, so that the network device can learn the carriers supported by the second terminal, the carriers preferred by the second terminal, the carriers supported by the first target address, etc., and can then schedule sidelink authorization for the first terminal based on this information, thereby improving the accuracy of sidelink authorization scheduling and improving the quality of sidelink communication between the first terminal and the second terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The above and / or additional aspects and advantages of the present disclosure will become apparent and readily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0039] FIG1A is a schematic diagram illustrating an architecture of a communication system according to an embodiment of the present disclosure;

[0040] FIG1B is a schematic diagram showing the format of an SL BSR report according to an embodiment of the present disclosure;

[0041] FIG2 is an interactive schematic diagram illustrating a carrier aggregation method according to an embodiment of the present disclosure;

[0042] 3A-3E are schematic flow diagrams illustrating a carrier aggregation method according to an embodiment of the present disclosure;

[0043] 4A-4E are schematic flow diagrams illustrating a carrier aggregation method according to an embodiment of the present disclosure;

[0044] FIG5 is an interactive schematic diagram illustrating a carrier aggregation method according to an embodiment of the present disclosure;

[0045] FIG6 is an interactive schematic diagram illustrating a carrier aggregation method according to an embodiment of the present disclosure;

[0046] FIG7A is a schematic structural diagram of a first terminal proposed in an embodiment of the present disclosure;

[0047] FIG7B is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure;

[0048] FIG7C is a schematic structural diagram of a second terminal proposed in an embodiment of the present disclosure;

[0049] FIG8A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0050] FIG8B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0051] The embodiments of the present disclosure provide a carrier aggregation method and apparatus.

[0052] In a first aspect, an embodiment of the present disclosure provides a carrier aggregation method, performed by a first terminal, the method including:

[0053] Sending indication information to the network device, where the indication information includes at least one of first indication information, second indication information, and third indication information;

[0054] The first indication information is used to indicate the carrier supported by the second terminal, the second indication information is used to indicate the carrier preferred by the second terminal, the third indication information is used to indicate the carrier supported by the first target address, and the second terminal is a terminal that establishes a unicast connection with the first terminal.

[0055] In the above embodiment, the first terminal can report one or more of the carriers supported by the second terminal with which a unicast connection is established, the carriers preferred by the second terminal, and the carriers supported by the first target address to the network device, so that the network device can know the carriers supported by the second terminal, the carriers preferred by the second terminal, the carriers supported by the first target address, etc., and then can schedule sidelink authorization for the first terminal based on this information, thereby improving the accuracy of sidelink authorization scheduling and improving the sidelink communication quality between the first terminal and the second terminal.

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

[0057] Receive sending scheduling information sent by the network device according to the indication information, wherein the scheduling information is used to indicate a sidelink authorization scheduled for the first terminal.

[0058] In the above embodiment, the first terminal may receive scheduling information sent by the network device according to the indication information, so that the first terminal may send sidelink data according to the sidelink authorization scheduled by the network device.

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

[0060] Receive the indication information sent by the second terminal, where the indication information includes the first indication information and / or the second indication information.

[0061] In the above embodiment, the first terminal can receive the first indication information and / or the second indication information sent by the second terminal, so that the first terminal can know the carrier supported by the second terminal and / or the carrier preferred by the second terminal, and then report it to the network device, so that the network device can determine the carrier used for carrier aggregation, thereby ensuring that the first terminal and the second terminal communicate on the supported carrier, thereby improving the side communication quality.

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

[0063] Send a request message to the second terminal, wherein the request message is used to request to obtain the indication information, and the indication information includes the first indication information and / or the second indication information.

[0064] In the above embodiment, the first terminal can send a request message to the second terminal to request to obtain the first indication information and / or the second indication information, so that the second terminal can send the first indication information and / or the second indication information after obtaining the request information, thereby improving the accuracy of information sending, reducing the number of interactions between terminals, and saving resources.

[0065] In conjunction with some embodiments of the first aspect, in some embodiments, sending request information to the second terminal includes:

[0066] The resource allocation mode of the first terminal changes, and the request information is sent to the second terminal.

[0067] In the above embodiment, the first terminal can send a request message to the second terminal when the resource allocation method sends a change, so as to obtain the second terminal's currently supported carrier and the currently preferred supported carrier when the resource allocation method changes, so that the network device can accurately determine the carrier used for carrier aggregation and improve the accuracy of side link authorization scheduling.

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

[0069] The carrier supported by the first target address is determined according to a mapping relationship between a service type and the first target address and / or a mapping relationship between the service type and a carrier.

[0070] In the above embodiment, the first terminal can determine the carrier supported by the first target address based on the mapping relationship between the service type and the first target address, the mapping relationship between the service type and the carrier, etc., so as to report the carrier supported by the first target address to the network device, so that the network device can be used to determine the carrier used for carrier aggregation.

[0071] In conjunction with some embodiments of the first aspect, in some embodiments, the first target address includes at least one of the following:

[0072] a target address associated with the unicast service of the first terminal;

[0073] a target address associated with the multicast service of the first terminal;

[0074] The target address associated with the broadcast service of the first terminal.

[0075] In the above embodiment, the first terminal can report the target address associated with each service type to the network device, so that the network device can schedule side link authorization for each service type of the first terminal based on the target address associated with each service, thereby improving the accuracy of the side link authorization scheduled for each service type of the first terminal.

[0076] In conjunction with some embodiments of the first aspect, in some embodiments, the indication information includes the first indication information, and the first indication information further includes at least one of the following:

[0077] a second destination address of the second terminal;

[0078] Business type.

[0079] In the above embodiment, when the first terminal reports the carrier supported by the second terminal to the network device, it can also report the second target address, service type and other information of the second terminal to the network device, thereby improving the accuracy of the side link authorization scheduled by the network device.

[0080] In conjunction with some embodiments of the first aspect, in some embodiments, the indication information includes the second indication information, and the second indication information further includes at least one of the following:

[0081] a second destination address of the second terminal;

[0082] Business type.

[0083] In the above embodiment, when the first terminal reports the second terminal's preferred supported carrier to the network device, it can also report the second terminal's second target address, service type and other information to the network device, thereby improving the accuracy of the side link authorization scheduled by the network device.

[0084] In conjunction with some embodiments of the first aspect, in some embodiments, the indication information includes the third indication information, and the third indication information further includes at least one of the following:

[0085] the first target address;

[0086] The service type associated with the first target address.

[0087] In the above embodiment, when the first terminal reports the carrier supported by the first target address to the network device, it can also report the first target address, service type and other information to the network device, thereby improving the accuracy of the side link authorization scheduled by the network device.

[0088] In combination with some embodiments of the first aspect, in some embodiments, the supported carrier includes a carrier supporting transmission and / or reception.

[0089] In the above embodiment, the first terminal can report the carriers supported by the second terminal for sending and / or receiving and the carriers preferred by the second terminal for sending and / or receiving to the network device, so that the network device determines the carrier for carrier aggregation based on this information, thereby ensuring that the first terminal and the second terminal support the carrier for carrier aggregation, and improving the accuracy of the side link authorization scheduled by the network device.

[0090] In combination with some embodiments of the first aspect, in some embodiments, the first terminal is a sending terminal.

[0091] In the above embodiment, the sending terminal can report one or more of the carriers supported by the receiving terminal with which a unicast connection is established, the carriers preferred by the receiving terminal, and the carriers supported by the first target address to the network device, so that the network device can know the carriers supported by the receiving terminal, the carriers preferred by the receiving terminal, the carriers supported by the first target address, etc., and can then schedule sidelink authorization for the sending terminal based on this information, thereby improving the accuracy of sidelink authorization scheduling and improving the quality of sidelink communication between the sending terminal and the receiving terminal.

[0092] In combination with some embodiments of the first aspect, in some embodiments, the resource allocation method of the first terminal is a method in which the network schedules sending resources.

[0093] In the above embodiment, in the above embodiment, for the terminal whose resource allocation method is the network scheduling resource sending method, one or more of the carriers supported by the opposite terminal with which a unicast connection is established, the carriers preferred by the opposite terminal, and the carriers supported by the first target address can be reported to the network device, so that the network device can know the carriers supported by the opposite terminal, the carriers preferred by the opposite terminal, the carriers supported by the first target address, etc., and then can schedule side link authorization for the terminal based on this information, thereby improving the accuracy of side link authorization scheduling and improving the side link communication quality between the terminal and the opposite terminal.

[0094] In a second aspect, an embodiment of the present disclosure provides a carrier aggregation method, which is performed by a network device. The method includes:

[0095] Receiving indication information sent by the first terminal device, where the indication information includes at least one of first indication information, second indication information, and third indication information;

[0096] The first indication information is used to indicate the carrier supported by the second terminal, the second indication information is used to indicate the carrier preferred by the second terminal, the third indication information is used to indicate the carrier supported by the first target address, and the second terminal is a terminal that establishes a unicast connection with the first terminal.

[0097] In the above embodiment, the network device can obtain information such as the carrier supported by the second terminal establishing a unicast connection with the first terminal, the carrier preferred by the second terminal, and the carrier supported by the first target address.

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

[0099] Determining, according to the indication information, a carrier for carrier aggregation;

[0100] Scheduling information is sent to the first terminal, where the scheduling information is used to indicate a sidelink grant scheduled for the first terminal on the carrier used for carrier aggregation.

[0101] In the above embodiment, the network device can determine the carrier used for carrier aggregation based on information such as the carrier supported by the second terminal, the carrier preferred supported by the second terminal, and the carrier supported by the first target address, thereby ensuring that the first terminal and the second terminal both support the carrier used for carrier aggregation, thereby scheduling sidelink authorization for the first terminal on the carrier used for carrier aggregation, improving the accuracy of sidelink authorization scheduling, and improving the sidelink communication quality between the first terminal and the second terminal.

[0102] In conjunction with some embodiments of the second aspect, in some embodiments, the first target address includes one or more of the following:

[0103] a target address associated with the unicast service of the first terminal;

[0104] a target address associated with the multicast service of the first terminal;

[0105] The target address associated with the broadcast service of the first terminal.

[0106] In the above embodiment, the network device can grant sidelink authorization for each service scheduling of the first terminal based on the target address associated with each service, thereby improving the accuracy of the sidelink authorization for each service scheduling of the first terminal.

[0107] In conjunction with some embodiments of the second aspect, in some embodiments, the indication information includes the first indication information, and the first indication information further includes at least one of the following:

[0108] a second destination address of the second terminal;

[0109] Business type.

[0110] In the above embodiment, the network device can determine the carrier used for carrier aggregation based on the carrier supported by the second terminal, the second target address and service type of the second terminal, etc., thereby improving the accuracy of the determined carrier and further improving the accuracy of the scheduled sidelink authorization.

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

[0112] a second destination address of the second terminal;

[0113] Business type.

[0114] In the above embodiment, the network device can determine the carrier used for carrier aggregation based on the carrier preferred by the second terminal, the second target address and service type of the second terminal, etc., thereby improving the accuracy of the determined carrier and further improving the accuracy of the scheduled side link authorization.

[0115] In conjunction with some embodiments of the second aspect, in some embodiments, the indication information includes the third indication information, and the third indication information further includes at least one of the following:

[0116] the first target address;

[0117] The service type associated with the first target address.

[0118] In the above embodiment, the network device can determine the carrier used for carrier aggregation based on the first target address, the carrier supported by the first target address, the service type associated with the first target address, etc., thereby improving the accuracy of the determined carrier and further improving the accuracy of the side link authorization scheduled for the service type of the first terminal.

[0119] In combination with some embodiments of the second aspect, in some embodiments, the supported carrier includes a carrier supporting transmission and / or reception.

[0120] In the above embodiment, the network device can determine the carrier used for carrier aggregation based on the carrier supported by the second terminal for sending and / or receiving and the carrier preferred by the second terminal for sending and / or receiving, thereby ensuring that the first terminal and the second terminal support the carrier used for carrier aggregation, thereby improving the accuracy of the side link authorization scheduled by the network device.

[0121] In a third aspect, the embodiment of the present disclosure proposes a carrier aggregation method, which is performed by a second terminal. The method includes:

[0122] Send indication information to the first terminal device, the indication information including first indication information and / or second indication information, wherein the first indication information is used to indicate the carrier supported by the second terminal, and the second indication information is used to indicate the carrier preferred to be supported by the second terminal.

[0123] In the above embodiment, the second terminal can notify the first terminal of the carriers it supports, the carriers it prefers to support, etc., so that the first terminal can report this information to the network device, so that the network device can schedule sidelink authorization for the first terminal based on this information, thereby improving the accuracy of sidelink authorization scheduling and improving the sidelink communication quality between the first terminal and the second terminal.

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

[0125] Receive request information sent by the first terminal, where the request information is used to request to obtain the indication information.

[0126] In the above embodiment, the second terminal may send the first indication information and / or the second indication information after obtaining the request information sent by the first terminal, thereby improving the accuracy of information sending, reducing the number of interactions between terminals, and saving resources.

[0127] In conjunction with some embodiments of the third aspect, in some embodiments, the indication information includes the first indication information, and the first indication information further includes at least one of the following:

[0128] a second destination address of the second terminal;

[0129] Business type.

[0130] In the above embodiment, the second terminal can also send the second target address and service type of the second terminal to the first terminal, so that when the first terminal reports the carrier supported by the second terminal to the network device, it can also report the second target address, service type and other information of the second terminal to the network device, thereby improving the accuracy of the side link authorization scheduled by the network device.

[0131] In conjunction with some embodiments of the third aspect, in some embodiments, the indication information includes the second indication information, and the second indication information further includes at least one of the following:

[0132] a second destination address of the second terminal;

[0133] Business type.

[0134] In the above embodiment, the second terminal can also send the second target address and service type of the second terminal to the first terminal, so that when the first terminal reports the second terminal's preferred supported carrier to the network device, it can also report the second target address, service type and other information of the second terminal to the network device, thereby improving the accuracy of the side link authorization scheduled by the network device.

[0135] In combination with some embodiments of the third aspect, in some embodiments, the supported carrier includes a carrier supporting transmission and / or reception.

[0136] In the above embodiment, the second terminal can notify the first terminal of the carriers that it supports sending and / or receiving and the carriers that it prefers to support sending and / or receiving, so that the first terminal can report the carriers that the second terminal supports sending and / or receiving and the carriers that the second terminal prefers to support sending and / or receiving to the network device, so that the network device determines the carrier used for carrier aggregation based on this information, which can ensure that the first terminal and the second terminal support the carrier used for carrier aggregation, thereby improving the accuracy of the side link authorization scheduled by the network device.

[0137] In a fourth aspect, an embodiment of the present disclosure provides a carrier aggregation method, including:

[0138] The first terminal device sends indication information to the network device, where the indication information includes at least one of first indication information, second indication information, and third indication information;

[0139] The network device receives the indication information;

[0140] The first indication information is used to indicate the carrier supported by the second terminal, the second indication information is used to indicate the carrier preferred by the second terminal, the third indication information is used to indicate the carrier supported by the first target address, and the second terminal is a terminal that establishes a unicast connection with the first terminal.

[0141] In the above embodiment, the first terminal can report one or more of the carriers supported by the second terminal with which a unicast connection is established, the carriers preferred by the second terminal, and the carriers supported by the first target address to the network device, so that the network device can know the carriers supported by the second terminal, the carriers preferred by the second terminal, the carriers supported by the first target address, etc., and then can schedule sidelink authorization for the first terminal based on this information, thereby improving the accuracy of sidelink authorization scheduling and improving the sidelink communication quality between the first terminal and the second terminal.

[0142] In the fifth aspect, an embodiment of the present disclosure proposes a carrier aggregation device, which is applied to a first terminal. The device may include at least one of a transceiver module and a processing module: wherein the first terminal is used to execute the first aspect and the optional implementation method of the first aspect.

[0143] In the sixth aspect, an embodiment of the present disclosure proposes a carrier aggregation device, which is applied to a network device. The device may include at least one of a transceiver module and a processing module: wherein the network device is used to execute the second aspect and the optional implementation method of the second aspect.

[0144] In the seventh aspect, an embodiment of the present disclosure proposes a carrier aggregation device, which is applied to a second terminal. The device may include at least one of a transceiver module and a processing module: wherein the second terminal is used to execute the third aspect and the optional implementation method of the third aspect.

[0145] In an eighth aspect, an embodiment of the present disclosure proposes a first terminal, which includes: one or more processors; wherein the first terminal is used to execute the first aspect and the optional implementation method of the first aspect.

[0146] In a ninth aspect, an embodiment of the present disclosure proposes a network device, which includes: one or more processors; wherein the network device is used to execute the second aspect and the optional implementation method of the second aspect.

[0147] In a tenth aspect, an embodiment of the present disclosure proposes a second terminal, which includes: one or more processors; wherein the second terminal is used to execute the third aspect and the optional implementation method of the third aspect.

[0148] In the eleventh aspect, an embodiment of the present disclosure proposes a communication system, comprising a first terminal, a second terminal and a network device, wherein the first terminal is configured to implement the method described in the first aspect and the optional implementation of the first aspect, the network device is configured to implement the method described in the second aspect and the optional implementation of the first aspect, and the second terminal is configured to implement the method described in the third aspect and the optional implementation of the third aspect.

[0149] In the twelfth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect, the optional implementation of the first aspect, the second aspect, the optional implementation of the second aspect, the third aspect and the optional implementation of the third aspect.

[0150] In the thirteenth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first aspect, the optional implementation of the first aspect, the second aspect, the optional implementation of the second aspect, the third aspect and the optional implementation of the third aspect.

[0151] In the fourteenth aspect, an embodiment of the present disclosure proposes a computer program, which, when running on a computer, enables the computer to execute the method described in the first aspect, the optional implementation of the first aspect, the second aspect, the optional implementation of the second aspect, the third aspect and the optional implementation of the third aspect.

[0152] In a fifteenth aspect, embodiments of the present disclosure provide a chip or chip system. The chip or chip system includes a processing circuit configured to execute the method described in accordance with the first aspect, the optional implementation of the first aspect, the second aspect, the optional implementation of the second aspect, the third aspect, and the optional implementation of the third aspect.

[0153] It is understandable that the above-mentioned terminals, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0154] The present disclosure provides a carrier aggregation method and apparatus. In some embodiments, the terms "carrier aggregation method" and "information processing method" and "communication method" are interchangeable; "information transmission device" and "information processing device" and "communication device" are interchangeable; and "information processing system" and "communication system" are interchangeable.

[0155] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain 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 certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0156] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0157] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0158] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0159] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0160] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0161] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0162] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0163] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0164] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0165] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0166] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0167] 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", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0168] 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, client, etc. can be used interchangeably.

[0169] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, it can also be called device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it can also be set as a structure in which the terminal has all or part of the functions of the access network device. In addition, language such as "uplink" and "downlink" can also be replaced by language corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0170] 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, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0171] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

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

[0173] Figure 1 is a schematic diagram illustrating the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1, communication system 100 may include a first terminal 101, a network device 102, and a second terminal 103. A communication connection may be established between first terminal 101 and second terminal 103. SL communication may be performed between first terminal 101 and second terminal 103.

[0174] In some embodiments, the network device 102 may include at least one of an access network device and a core network device.

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

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

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

[0178] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0179] In some embodiments, a core network device may be a single device comprising one or more network elements, or may be a plurality of devices or a group of devices, each comprising all or part of one or more network elements. A network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0180] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0181] The following embodiments of the present disclosure may be applied to the communication system 100 shown in Figure 1, or a portion thereof, but are not limited thereto. The entities shown in Figure 1 are illustrative only. The communication system may include all or part of the entities shown in Figure 1, or may include other entities outside of Figure 1. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0182] The embodiments of the present disclosure 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 (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (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 utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0183] In order to support direct communication between terminals, a sidelink (SL) communication mode is introduced. Optionally, the interface between the terminals can be PC-5 (direct communication interface).

[0184] In some embodiments, the terms "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" and the like may be used interchangeably.

[0185] In some embodiments, based on the correspondence between the sending terminal and the receiving terminal, three transmission modes are supported on the SL: unicast, multicast, and broadcast.

[0186] In some embodiments, SL communication has two transmission resource allocation methods: one is the network dynamically scheduling transmission resources, and the other is the terminal autonomously selecting transmission resources from a network-configured or pre-configured resource pool. The network scheduling transmission resource method involves the network device dynamically allocating transmission resources on the SL to the terminal based on the terminal's cached data report, while the autonomous transmission resource selection method involves the terminal randomly selecting transmission resources from a network-configured or pre-configured resource pool. Optionally, the network device can configure the specific resource allocation method used by the terminal through RRC signaling.

[0187] In some embodiments, the name of the method for network scheduling to send resources is not limited. For example, the method for network scheduling to send resources may be mode 1 or mode1.

[0188] In some embodiments, the name of the method for autonomously selecting sending resources is not limited. For example, the method for autonomously selecting sending resources may be mode 2 or mode2.

[0189] In some embodiments, the transmitting terminal sends sidelink control information (SCI) on the physical sidelink control channel (PSCCH) and sends a second-stage SCI on the physical sidelink shared channel (PSSCH), which carries the resource location of the transmitted data and the source and destination identifiers, etc.

[0190] Optionally, for hybrid automatic repeat request (HARQ) enabled (HARQ-enabled) data packets, the receiving terminal performs HARQ confirmation (HARQ-ACK) feedback on the physical sidelink feedback channel (PSFCH) channel for the PSSCH.

[0191] To meet the requirements of single-user peak rate and system capacity improvement, the system transmission bandwidth can be increased, for example, by adopting CA. CA technology can aggregate multiple component carriers (CCs) together, effectively improving the uplink and downlink transmission rates.

[0192] In some embodiments, the multiplexing function of the transmitting terminal's media access control (MAC) layer loads data from multiple logical channels into a single transport channel. This multiplexes multiple MAC service data units (SDUs) into a single MAC protocol data unit (PDU), which is then transmitted via a physical layer channel. When multiple logical channels have data to send, and the total amount of data exceeds the currently authorized transmission capacity, the question of which logical channel should be prioritized for transmission arises. This is known as logical channel prioritization (LCP).

[0193] In some embodiments, each logical channel has a priority for logical channel scheduling. This priority is configured by the network based on the quality of service (QoS) of the data carried by the logical channel. When a terminal obtains a scheduling opportunity, that is, a resource for sidelink transmission of data on a carrier, the terminal first selects a target address and then selects a SL logical channel (LCH) that belongs to the target address and meets certain conditions to be multiplexed into the SL MAC PDU.

[0194] In some embodiments, some LCP processes need to select the target address corresponding to the sidelink logical channel that meets certain conditions and has the highest priority as the target address when determining the destination terminal. When the terminal device receives the sidelink grant on the carrier, it needs to determine the target address according to the LCP process and select the SL LCH group package.

[0195] In some embodiments, for a terminal device operating in Mode 2, the sidelink grant on the carrier may be selected by the terminal device itself. For a terminal device operating in Mode 1, the sidelink grant on the carrier may be scheduled by the network device through downlink control signaling. Even if the network device schedules the sidelink grant on the carrier, the network device cannot determine the target address of the sidelink grant; the target address is determined by the terminal device during the LCP process.

[0196] In some embodiments, a terminal device operating in mode 1 may report a SL buffer status report (BSR) to a network device to assist the network device in scheduling SL resources. Exemplarily, the SL-BSR includes a periodic SL-BSR and a regular SL-BSR. Exemplarily, the specific format of the SL-BSR is shown in FIG1B , where the first byte may include a target address identifier 1 and a logical channel group identifier 1, the second byte includes the cached data size 1 in the logical channel group 1, the third byte includes the target address identifier 2 and the logical channel group identifier 2, the fourth byte includes the cached data size 2 in the logical channel group 2, the 2N-1 byte includes the target address identifier N and the logical channel group identifier N, and the 2N byte includes the cached data size N in the logical channel group N.

[0197] Optionally, the network device may determine the amount of data to be transmitted of a logical channel group (LCG) associated with a Destination Index (identifier of a destination address), and then perform corresponding scheduling.

[0198] In some embodiments, due to limited sending and receiving capabilities, the receiving terminal may only be able to receive sidelink services on one or several carriers, and due to limited sending capabilities, the transmitting terminal may only be able to send sidelink services on one or several carriers.

[0199] In some embodiments, higher layer implementations may be relied upon to determine which service is of interest and only receive data on carriers associated with the service of interest.

[0200] In some embodiments, the New Radio (NR) SL also supports carrier aggregation. Optionally, the restricted terminal capabilities may not be considered, and terminals supporting carrier aggregation are assumed to support transmission and reception on all carriers. Optionally, the restricted terminal capabilities may be considered.

[0201] In some embodiments, NR SL CA only supports Mode 2.

[0202] In some embodiments, NR SL CA only supports Mode 1.

[0203] In some embodiments, for terminal devices operating in mode 1, taking into account the limited UE capabilities, if the network device is completely unaware of the carriers / frequency bands supported by the unicast connections and / or multicast broadcast services associated with the terminal device, it may be possible that the network device cannot reasonably schedule the terminal device according to the SL BSR. For example, there are three unicast connections between terminal device A and terminal devices BCD respectively, (A, B) supports carriers a and b, (A, C) supports carriers a, b, c, and (A, D) supports carriers a and c. If terminal device A has a lot of data to be transmitted to B, when the mapping relationship between the above unicast connections and carriers is unknown, the scheduling of the network device depends entirely on the implementation of the network device. The network device may schedule a lot of sidelink grants on carrier c, but the sidelink grants on carrier c cannot be used to transmit data from A to B. Therefore, terminal device A may have a large amount of data for terminal device B, but the network device cannot schedule it in time.

[0204] In some embodiments, for terminal devices operating in Mode 1, taking into account the limited UE capabilities, if the network device is completely unaware of the carrier / frequency band supported by the unicast connection and / or multicast broadcast service associated with the terminal device, the network device may be unable to properly schedule the terminal device according to the SL BSR. Therefore, when SL CA operates in Mode 1, how to let the network device know the carrier / frequency band supported by the unicast connection and / or multicast broadcast service associated with the terminal device is an urgent problem to be solved.

[0205] Based on this, the present disclosure proposes a carrier aggregation method.

[0206] Optionally, in some embodiments, the method of the present disclosure may be applied to a SL CA scenario. For example, in some embodiments, the method of the present disclosure may be applied to a vehicle networking scenario.

[0207] FIG2 is an interactive diagram of a carrier aggregation method according to an embodiment of the present disclosure. As shown in FIG2 , the embodiment of the present disclosure relates to a carrier aggregation method for a communication system 100, the method comprising:

[0208] Step S2101: The first terminal 101 sends indication information to the network device 102.

[0209] In some embodiments, terms such as "first", "certain", "preset", "preset", "setting", "indicated", "a certain", "arbitrary", and "any" can be interchangeable. "First A", "certain A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "any A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, any A, or any A, etc., but not limited to this.

[0210] In some embodiments, the first terminal 101 may be a sending terminal, and accordingly, there is a second terminal 103 that performs unicast communication with the first terminal 101 as a receiving terminal.

[0211] In some embodiments, the first terminal 101 may be a receiving terminal, and accordingly, there is a second terminal 103 that performs unicast communication with the first terminal 101 as a sending terminal.

[0212] In some embodiments, the resource allocation method of the first terminal 101 may be a method in which the network schedules sending resources (mode 1, mode 1).

[0213] In some embodiments, the first terminal 101 may be a terminal performing sidelink unicast communication.

[0214] In some embodiments, the indication information may include one or more of first indication information, second indication information, and third indication information. The first terminal 101 may send indication information to the network device 102 to indicate to the network device 102 information related to the supported carriers. In some embodiments, if the first terminal 101 determines that the indication information has changed compared to the previous indication information, the first terminal 101 may send the indication information to the network device 102. Exemplarily, the previous indication information may refer to the indication information last sent to the network device 102. Exemplarily, the change in the indication information compared to the previous indication information may refer to a change in at least one of the first indication information, the second indication information, and the third indication information. In addition, the first terminal 101 may actively obtain the indication information to determine whether the indication information has changed. For example, the first terminal 101 may periodically obtain the indication information to compare the currently obtained indication information with the last obtained indication information. Alternatively, the first terminal 101 may obtain the indication information and notify the network device only if the indication information has changed. If the first terminal 101 does not obtain new indication information, the first terminal 101 considers that the indication information has not changed. Accordingly, in the case of the first indication information, when the carrier supported by the second terminal 103 in unicast communication with the first terminal 101 changes, the second terminal 103 sends the first indication information to the first terminal 101 to inform it of the currently supported carrier; in the case of the second indication information, when the carrier preferred by the second terminal 103 changes, the second terminal 103 sends the second indication information to the first terminal 101 to inform it of the currently supported carrier. In the case of the third indication information, when the target address associated with the service of the first terminal 101 changes, the first terminal 101 sends the third indication information to the network device to inform it of the carrier supported by the target address.

[0215] In addition, when the indication information changes, the first terminal 101 notifies the network device 102 of the changed indication information. Optionally, the first indication information may send the changed new indication information to the network device 102, or may only send the amount of change in the indication information to the network device 102. For example, taking the indication information including the first indication information as an example, when the carrier supported by the second terminal 103 in unicast communication with the first terminal changes from the previous carriers a and b to carriers a and c, the first terminal 101 may send an indication to the network device 102 to indicate that the second terminal 103 supports carriers a and c, or may send indication information to the network device 102 to indicate that the second terminal 103 no longer supports carrier b and supports carrier c.

[0216] It should be understood that as long as one of the first indication information, the second indication information, and the third indication information included in the indication information changes, the first terminal 101 can trigger reporting of the indication information so that the network device 102 is aware of the latest indication information.

[0217] Exemplarily, when the first indication information changes compared to the previous first indication information (for example, the carrier supported by the second terminal 103 changes compared to the previously supported carrier), the first terminal 101 may send the first indication information to the network device 102. Exemplarily, the previous first indication information may refer to the first indication information last sent to the network device 102.

[0218] Exemplarily, when the second indication information changes compared to the previous second indication information (for example, the carrier preferred by the second terminal 103 changes compared to the previously preferred carrier supported), the first terminal 101 may send the second indication information to the network device 102. Exemplarily, the previous second indication information may refer to the second indication information last sent to the network device 102.

[0219] Exemplarily, when the third indication information changes compared to the previous third indication information (for example, the carrier supported by the first target address changes compared to the previously supported carrier), the first terminal 101 may send the third indication information to the network device 102. Exemplarily, the previous third indication information may refer to the third indication information last sent to the network device 102.

[0220] In some embodiments, the first terminal 101 may send indication information to the network device 102 through Uu RRC signaling. Exemplarily, the Uu RRC signaling may be sidelink UE Information (SUI) signaling or UE assistance information (UAI) signaling or other newly defined Uu RRC signaling, which is not specifically limited in this disclosure.

[0221] In some embodiments, the indication information may include one or more of the first indication information, the second indication information, and the third indication information. For example, the first indication information, the second indication information, and the third indication information may be carried using the same Uu RRC signaling or different Uu RRC signaling, which is not specifically limited in this disclosure.

[0222] In some embodiments, the first indication information may be used to indicate a carrier supported by the second terminal 103 , and the second indication information may be used to indicate a carrier preferred to be supported by the second terminal 103 .

[0223] In some embodiments, there may be one or more terminals that establish a unicast connection with the first terminal 101, and the second terminal 103 is one of them. In other words, the second terminal 103 is any terminal that establishes a unicast connection with the first terminal 101.

[0224] In some embodiments, the expressions: "carrier", "frequency band", "spectrum", and "frequency" can be used interchangeably.

[0225] In some embodiments, the carrier supported by the second terminal 103 may include a carrier supported by the second terminal 103 for sending and / or receiving. Exemplarily, the carrier supported by the second terminal 103 for sending may refer to a carrier that the second terminal 103 can use to send sidelink data, and the carrier supported by the second terminal 103 for receiving may refer to a carrier that the second terminal 103 can use to receive sidelink data.

[0226] In some embodiments, the carrier that the second terminal 103 preferably supports may include a carrier that the second terminal 103 preferably supports for sending and / or receiving. Exemplarily, the carrier that the second terminal 103 preferably supports may be a carrier that the second terminal 103 recommends for use among the supported carriers. Exemplarily, the carrier that the second terminal 103 preferably supports may be some of the preferred carriers selected by the second terminal 103 on the supported carriers. Exemplarily, the carrier that the second terminal 103 preferably supports for sending may refer to a carrier that the second terminal 103 may preferably use for sending sidelink data, and the carrier that the second terminal 103 preferably supports for receiving may refer to a carrier that the second terminal 103 may preferably use for receiving sidelink data. Here, preferred may refer to a carrier that the second terminal 103 expects to use for sending or receiving information. That is, the second terminal 103 may inform the network device 102 through the first terminal 101 of the carrier that the second terminal 103 expects to use, so that the network device 102 may prioritize scheduling the carrier when possible. The second terminal 103 can recommend its desired single carrier to the first terminal 101, or can recommend one or more of its desired multiple carriers to the first terminal 101, so that the first terminal 101 reports it to the network device 102, thereby enabling the network device 102 to perform targeted scheduling.

[0227] In some embodiments, the support described in the present disclosure may refer to support for sending sidelink data, or support for receiving sidelink data, or support for sending and receiving sidelink data.

[0228] In some embodiments, the supporting sending and / or receiving described in the present disclosure may refer to supporting sending and / or receiving sidelink data.

[0229] In some embodiments, the support for sending described in the present disclosure may refer to supporting the sending of sidelink data, and the support for receiving may refer to supporting the receiving of sidelink data.

[0230] Exemplarily, the first indication information may include a carrier identification list, which may include carrier information of carriers supported for transmission and / or carrier information of carriers supported for reception by the second terminal 103. Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission by the second terminal 103; Exemplarily, the one carrier identification list may include carrier information of carriers supported for reception by the second terminal 103; Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission and carriers supported for reception by the second terminal 103; Exemplarily, the second indication information may include two carrier identification lists, one list including carrier information of carriers supported for transmission by the second terminal 103, and the other list including carrier information of carriers supported for reception by the second terminal 103.

[0231] Exemplarily, the second indication information may include a carrier identification list, which may include carrier information of carriers that the second terminal 103 preferably supports for sending and / or carrier information of carriers that the second terminal 103 preferably supports for receiving. Exemplarily, the one carrier identification list may include carrier information of carriers that the second terminal 103 preferably supports for sending; Exemplarily, the one carrier identification list may include carrier information of carriers that the second terminal 103 preferably supports for receiving; Exemplarily, the one carrier identification list may include carrier information of carriers that the second terminal 103 preferably supports for sending and carriers that the second terminal 103 preferably supports for receiving; Exemplarily, the third indication information may include two carrier identification lists, one list including carrier information of carriers that the second terminal 103 preferably supports for sending, and the other list including carrier information of carriers that the second terminal 103 preferably supports for receiving.

[0232] In some embodiments, expressions in the present disclosure such as “carrier identification list”, “carrier list”, “carrier set”, etc. may be interchangeable.

[0233] In some embodiments, the first indication information may also include one or more of the second target address and service type of the second terminal 103, so that the network device 102 can know the target address and / or service type of the second terminal 103 and make targeted scheduling.

[0234] In some embodiments, the second indication information may also include one or more of the second target address and service type of the second terminal 103, so that the network device 102 can know the target address and / or service type of the second terminal 103 and make targeted scheduling.

[0235] In some embodiments, the expressions: second target address and second target layer 2 address may be interchangeable.

[0236] In some embodiments, the second terminal 103 may send indication information to the first terminal 101 via PC5-RRC signaling, where the indication information may include first indication information and / or second indication information. Exemplarily, the PC5-RRC signaling may be UECapabilityInformationSidelink signaling, UEAssistanceInformationSidelink, or newly defined PC5-RRC signaling, which is not specifically limited in this disclosure. Exemplarily, the second terminal 103 may send the first indication information and / or the second indication information to the first terminal 101 via other PC5 signaling, such as PC5 MAC CE. This disclosure does not specifically limit this.

[0237] In some embodiments, the second terminal 103 may actively send indication information to the first terminal 101, where the indication information may include first indication information and / or second indication information.

[0238] Exemplarily, if the second terminal 103 is motivated to send the first indication information and / or the second indication information (for example, when the first indication information and the second indication information change / update, it is necessary to inform the first terminal and / or the network device connected to the first terminal of the change so that the network device can make targeted scheduling, or the second terminal sends the first indication information to the first terminal periodically or upon request), it can send the first indication information and / or the second indication information to the first terminal 101. Exemplarily, after establishing a unicast connection with the first terminal 101, the second terminal 103 can send the first indication information and / or the second indication information to the first terminal 101 (the second indication information and / or the third indication information are sent for the first time after the unicast connection is established).

[0239] Exemplarily, when the first indication information changes compared to the previous first indication information (for example, the carrier supported by the second terminal 103 changes compared to the previously supported carrier), the first indication information is sent to the first terminal 101. Exemplarily, the previous first indication information may refer to the first indication information last sent to the first terminal 101. Thus, when the carrier supported by the second terminal 103 changes, the second terminal 103 can promptly notify the first terminal 101 of the currently supported carrier, so that the first terminal 101 notifies the network device 102.

[0240] Exemplarily, when the second indication information changes compared to the previous second indication information (for example, the carrier preferentially supported by the second terminal 103 changes compared to the previously preferred carrier preferentially supported), the second indication information is sent to the first terminal 101. Exemplarily, the previous second indication information may refer to the second indication information last sent to the first terminal 101. Thus, when the carrier supported by the second terminal 103 changes, the second terminal 103 can promptly notify the first terminal 101 of the currently supported carrier so that the first terminal 101 notifies the network device 102.

[0241] In some embodiments, the first terminal 101 may send a request message to the second terminal 103 to request to obtain indication information, wherein the indication information may include first indication information and / or second indication information. After receiving the request message, the second terminal 103 sends the first indication information and / or the second indication information to the first terminal 101, so that the first terminal 101 informs the network device 102.

[0242] For example, the first terminal 101 may send the request information to the second terminal 103 via PC5-RRC signaling. For example, the PC5-RRC signaling may be UECapabilityEnquirySidelink signaling or newly defined PC5-RRC signaling, which is not limited in this disclosure. For example, the first terminal 101 may send the request information to the second terminal 103 via other PC5 signaling, such as PC5 MAC CE. This disclosure does not specifically limit this.

[0243] In some embodiments, the request information may include carrier information of the carrier supported by the first terminal 101, and the second terminal 103 may determine the first indication information and / or the second indication information based on the carrier supported by the first terminal 101 and the carrier supported by the second terminal 103.

[0244] Exemplarily, the request information may include carrier information of carriers supported by the first terminal 101. Exemplarily, the carriers supported by the first terminal 101 include carriers supported by the first terminal 101 for receiving and / or sending. Exemplarily, the carriers supported by the first terminal 101 for sending may refer to carriers that the first terminal 101 may use to send sidelink data, and exemplary, the carriers supported by the first terminal 101 for receiving may refer to carriers that the first terminal 101 may use to receive sidelink data.

[0245] Exemplarily, the request information may include carrier information of the carrier that the first terminal 101 preferably supports. Exemplarily, the carrier that the first terminal 101 preferably supports may include the carrier that the first terminal 101 prefers to support sending and / or receiving. Exemplarily, the carrier that the first terminal 101 prefers to support may be some of the preferred carriers selected by the first terminal 101 on the supported carriers. Exemplarily, the carrier that the first terminal 101 prefers to support sending may refer to the carrier that the first terminal 101 prefers to use for sending sidelink data. Exemplarily, the carrier that the first terminal 101 prefers to support receiving may refer to the carrier that the first terminal 101 prefers to use for receiving sidelink data.

[0246] Exemplarily, the second terminal 103 may determine the first indication information and / or the second indication information based on one or more of the carriers supported by the first terminal 101, the carriers preferred by the first terminal 101, and the carriers supported for reception by the second terminal 103. For example, the second terminal 103 may determine the first indication information and / or the second indication information based on the carrier support of the first terminal 101 in unicast communication with itself and its own carrier support, and inform the network device via the first terminal 101. That is, the carrier support of the second terminal 103 obtained by the network device 102 should match the carrier support of the first terminal 101, so that the sending and receiving of the scheduled carrier of the second terminal 103 is compatible with the carrier support capability of the first terminal 101.

[0247] Exemplarily, the request information may include a carrier identification list, which may include carrier information of carriers supported for transmission and / or carrier information of carriers supported for reception by the first terminal 101. Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission by the first terminal 101; Exemplarily, the one carrier identification list may include carrier information of carriers supported for reception by the first terminal 101; Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission and carriers supported for reception by the first terminal 101; Exemplarily, the request information may include two carrier identification lists, one list including carrier information of carriers supported for transmission by the first terminal 101, and the other list including carrier information of carriers supported for reception by the first terminal 101.

[0248] Optionally, the first terminal 101 may send a request message to the second terminal 103 when the resource allocation mode changes. Exemplarily, when the resource allocation mode of the first terminal 101 is configured or reconfigured from mode 1 to mode 2, the request message is sent to the second terminal 103. Exemplarily, when the resource allocation mode of the first terminal 101 is configured or reconfigured from mode 2 to mode 1, the request message is sent to the second terminal 103.

[0249] Optionally, the first terminal 101 may send the request information to the second terminal 103 after establishing a unicast connection with the second terminal 103. Exemplarily, the first terminal 101 may send the request information to the second terminal 103 after establishing a unicast connection with the second terminal 103 based on implementation.

[0250] In some embodiments, the first terminal 101 may receive indication information sent by the second terminal 103 , where the indication information may include first indication information and / or second indication information.

[0251] In some embodiments, the third indication information may be used to indicate a carrier supported by the first target address. Exemplarily, the first target address may be a target layer 2 address.

[0252] In some embodiments, the carrier supported by the first target address may include a carrier supported for reception and / or a carrier supported for transmission by the first target address.

[0253] In some embodiments, the third indication information may further include one or more of the first target address and the service type associated with the first target address.

[0254] In some embodiments, the expressions: first target address and first target layer 2 address may be interchangeable.

[0255] In some embodiments, the first terminal 101 may determine the carriers supported by the first target address based on a mapping relationship between the service type and the first target address and / or a mapping relationship between the service type and the carrier configured by a higher layer. For example, the higher layer may be a V2X layer. For example, if the target address associated with service a1 is b1, and service a1 corresponds to carriers c1 and c2, then the carriers supported by target address b1 are c1 and c2.

[0256] In some embodiments, the first target address may include one or more of a target address associated with a unicast service of the first terminal 101 , a target address associated with a multicast service of the first terminal 101 , and a target address associated with a broadcast service of the first terminal 101 .

[0257] Exemplarily, if the first target address is the target address associated with the unicast service of the first terminal 101, the carrier supported by the first target address may refer to the carrier used by the first terminal 101 to send and / or receive the unicast service or unicast sidelink data associated with the first target address.

[0258] Exemplarily, if the first target address is the target address associated with the multicast service of the first terminal 101, the carrier supported by the first target address may refer to the carrier used by the first terminal 101 to send and / or receive the multicast service or multicast sidelink data associated with the first target address.

[0259] Exemplarily, if the first target address is the target address associated with the broadcast service of the first terminal 101, the carrier supported by the first target address may refer to the carrier used by the first terminal 101 to send and / or receive the broadcast service or broadcast sidelink data associated with the first target address.

[0260] In some embodiments, the network device 102 may receive indication information sent by the first terminal 101, wherein the indication information may include one or more of first indication information, second indication information, and third indication information.

[0261] In some embodiments, the network device 102 may determine, based on the indication information, that the first terminal 101 supports the carrier used for carrier aggregation, and schedule a sidelink grant for the first terminal 101 on the carrier used for carrier aggregation. That is, the network device 102 may determine, based on one or more of the first indication information, the second indication information, and the third indication information, that the first terminal 101 supports the carrier used for carrier aggregation, and schedule a sidelink grant for the first terminal 101 on the carrier used for carrier aggregation.

[0262] Optionally, the network device 102 may determine that the first terminal 101 supports a carrier for carrier aggregation based on one or more of the first indication information, the second indication information, and the third indication information, and / or the carrier supported by the first terminal 101, and schedule a sidelink grant for the first terminal 101 on the carrier used for carrier aggregation. Exemplarily, the carrier supported by the first terminal 101 may refer to a carrier supported by the first terminal 101 for sending and / or receiving. Exemplarily, the network device may obtain information about the carrier supported by the first terminal 101 through terminal capability information sent by the first terminal 101.

[0263] In some embodiments, a unicast connection exists between the first terminal 101 and the second terminal 103. The first terminal 101 may send first indication information to the network device 102, where the first indication information indicates a carrier supported by the second terminal 103. The network device 102 may determine, based on the first indication information and / or the carrier supported by the first terminal 101, a carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103, and may schedule a sidelink grant for the first terminal 101 on the carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103. The first terminal 101 is a transmitting terminal, and the second terminal 103 is a receiving terminal.

[0264] Exemplarily, a unicast connection exists between the first terminal 101 and the second terminal 103. The first terminal 101 supports sending carriers A1, A2, A3, and A4, and the second terminal 103 supports receiving carriers A2, A3, and A4. The network device 102 can determine that the carriers supported by the unicast connection between the first terminal 101 and the second terminal 103 for carrier aggregation are A2, A3, and A4, and can schedule a sidelink grant for the first terminal 101 on carriers A2, A3, and A4. Exemplarily, the network device 102 can determine that the carriers supported by the unicast connection between the first terminal 101 and the second terminal 103 for carrier aggregation are A2 and A3, or A2 and A4, or A3 and A4, and can schedule a sidelink grant for the first terminal 101 on A2 and A3, or A2 and A4, or A3 and A4.

[0265] In some embodiments, a unicast connection exists between the first terminal 101 and the second terminal 103. The first terminal 101 may send second indication information to the network device 102, where the second indication information indicates a carrier that the second terminal 103 preferably supports. The network device 102 may determine, based on the second indication information and / or the carrier supported by the first terminal 101, a carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103, and may schedule a sidelink grant for the first terminal 101 on the carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103. The first terminal 101 is a transmitting terminal, and the second terminal 103 is a receiving terminal.

[0266] For example, the first terminal 101 supports carriers A1, A2, A3, and A4 for transmission, and the second terminal 103 preferably supports carriers A2 and A3 for reception. The network device may determine that the carriers supported for carrier aggregation by the unicast connection between the first terminal 101 and the second terminal 103 are A2 and A3, and may schedule a sidelink grant for the first terminal 101 on carriers A2 and A3. Of course, if the second terminal 103 also supports carrier A4, the network device 102 may preferably schedule a sidelink grant for the first terminal 101 on carriers A2 and A3, and use carrier A4 as an alternative to schedule a sidelink grant for the first terminal 101 on carrier A4 when A2 and A3 are unavailable.

[0267] In some embodiments, a unicast connection exists between the first terminal 101 and the second terminal 103. The first terminal 101 may send first indication information and second indication information to the network device 102. The network device 102 may determine, based on the first indication information and / or the second indication information and / or the carrier supported by the first terminal 101, a carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103, and may schedule a sidelink grant for the first terminal 101 on the carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103. The first terminal 101 is a transmitting terminal, and the second terminal 103 is a receiving terminal.

[0268] Exemplarily, the first terminal 101 supports carriers A1, A2, A3, and A4 for transmission, and the second terminal 103 supports carriers A2, A3, and A4 for reception. The second terminal 103 preferentially supports carriers A2 and A3 for reception. The network device can determine that the carriers supported for carrier aggregation by the unicast connection between the first terminal 101 and the second terminal 103 are A2, A3, and A4, and can schedule a sidelink grant for the first terminal 101 on carriers A2, A3, and A4. Exemplarily, the network device can determine that the carriers supported for carrier aggregation by the unicast connection between the first terminal 101 and the second terminal 103 are A2 and A3, and can schedule a sidelink grant for the first terminal 101 on carriers A2 and A3.

[0269] In some embodiments, if the first destination address is the destination address associated with a unicast service of first terminal 101, for example, it may be the address of second terminal 103 that has a unicast connection with first terminal 101. First terminal 101 is a sending terminal, and second terminal 103 is a receiving terminal. A carrier supported by the first destination address is determined based on a high-level configuration. That is, a carrier that first terminal 101 can use to send and / or receive the unicast service or unicast sidelink data associated with the first destination address. First terminal 101 may obtain the first indication information and / or second indication information sent by the first destination address. The first terminal 101 can send one or more of the first indication information, the second indication information, and the third indication information of the first target address to the network device 102, so that for the first target address, the first terminal 101 can report to the network device 102 one or more of the carriers that the first terminal 101 can use to send and / or receive the unicast service or unicast sidelink data associated with the first target address, the carriers that the first target address supports receiving, and the carriers that are preferred to support receiving. The network device 102 can determine the carriers on which the first terminal 101 can aggregate the unicast service or unicast sidelink data associated with the first target address based on one or more of the carriers that the first terminal 101 can use to send and / or receive the unicast service or unicast sidelink data associated with the first target address, the carriers that the first target address supports receiving, and the carriers that are preferred to support receiving, and can schedule sidelink authorization for the first terminal 101 on the carrier used for carrier aggregation.

[0270] In some embodiments, the first terminal 101 may send first indication information and third information to the network device 102, where the first indication information indicates the carrier supported by the first target address, and the third indication information indicates the carrier that the first terminal 101 can use to send and / or receive the unicast service or unicast sidelink data associated with the first target address. The network device 102 may determine the carrier for carrier aggregation supported by the first terminal 101 for sending the unicast service or unicast sidelink data associated with the first target address based on the first indication information, the third information, and one or more of the carriers supported by the first terminal 101, and may schedule sidelink authorization for the first terminal 101 on the carrier for carrier aggregation supported by the first terminal 101 for sending the unicast service or unicast sidelink data associated with the first target address.

[0271] Exemplarily, the first terminal 101 determines, based on high-level configuration, that the carriers supported by the first target address are A1, A2, A3, and A4, that is, the carriers that the first terminal 101 can use to send and / or receive unicast services or unicast sidelink data associated with the first target address are A1, A2, A3, and A4. The first target address supports receiving carriers A2, A3, and A4. The network device 102 can determine that the carriers supported for carrier aggregation by the first terminal 101 for sending unicast services or unicast sidelink data associated with the first target address are A2, A3, and A4, and can schedule sidelink authorization for the first terminal 101 on carriers A2, A3, and A4. Exemplarily, the network device 102 can determine that the carriers supported for carrier aggregation for the first terminal 101 to send unicast services or unicast sidelink data associated with the first target address are A2 and A3, or A2 and A4, or A3 and A4, and can schedule sidelink authorization for the first terminal 101 on A2 and A3, or A2 and A4, or A3 and A4.

[0272] In some embodiments, the first terminal 101 may send second indication information and third indication information to the network device 102, where the second indication information indicates the carrier that is preferentially supported by the first target address, and the third indication information indicates the carrier that is preferentially used by the first terminal 101 to send and / or receive the unicast service or unicast sidelink data associated with the first target address. The network device 102 may determine the carrier for carrier aggregation supported by the first terminal 101 for sending the unicast service or unicast sidelink data associated with the first target address based on the second indication information, the third indication information, and one or more of the carriers supported by the first terminal 101, and may schedule sidelink authorization for the first terminal 101 on the carrier for carrier aggregation supported by the first terminal 101 for sending the unicast service or unicast sidelink data associated with the first target address. Exemplarily, the first terminal 101 determines, based on high-level configuration, that the carriers supported by the first target address are A1, A2, A3, and A4, that is, the carriers that the first terminal 101 can use to send and / or receive unicast services or unicast sidelink data associated with the first target address are A1, A2, A3, and A4, and the first target address preferentially supports receiving carriers A2 and A3. The network device 102 can determine that the carriers supported for carrier aggregation for the first terminal 101 to send unicast services or unicast sidelink data associated with the first target address are A2 and A3, and can schedule sidelink authorization for the first terminal 101 on carriers A2 and A3.

[0273] In some embodiments, if the first target address is the target address associated with the multicast service of the first terminal 101, illustratively, the target address associated with the multicast service that the first terminal 101 is interested in sending and / or receiving. Then, the carrier supported by the first target address is determined according to the high-level configuration. The carrier supported by the first target address is, that is, the carrier that the first terminal 101 can use to send and / or receive the multicast service or multicast sidelink data associated with the first target address. The first terminal 101 can send a third indication message to the network device 102. The network device 102 can determine, based on the third indication message, the carrier on which the first terminal 101 can aggregate the multicast service or multicast sidelink data associated with the first target address, and can schedule a sidelink authorization for the first terminal 101 on the carrier used for carrier aggregation.

[0274] Exemplarily, the first terminal 101 determines, based on high-level configuration, that the carriers supported by the first target address are a1, a2, a3, and a4, that is, the carriers that the first terminal 101 can use to send and / or receive the multicast service or multicast sidelink data associated with the first target address are a1, a2, a3, and a4. The network device 102 can determine that the carriers that can be aggregated for the first terminal 101 to send the multicast service or multicast sidelink data associated with the first target address are a1, a2, a3, and a4, and can schedule sidelink authorization for the first terminal 101 on carriers a1, a2, a3, and a4.

[0275] In some embodiments, if the first target address is a target address associated with a broadcast service of the first terminal 101, illustratively, the target address associated with a broadcast service that the first terminal 101 is interested in sending and / or receiving. Then, the carrier supported by the first target address is determined according to the high-level configuration. The carrier supported by the first target address is, that is, the carrier that the first terminal 101 can use to send and / or receive the broadcast service or broadcast sidelink data associated with the first target address. The first terminal 101 can send a third indication message to the network device 102. The network device 102 can determine, based on the third indication message, the carrier on which the first terminal 101 can aggregate the broadcast service or broadcast sidelink data associated with the first target address, and can schedule a sidelink authorization for the first terminal 101 on the carrier used for carrier aggregation.

[0276] Exemplarily, the first terminal 101 determines, based on high-level configuration, that the carriers supported by the first target address are b1, b2, b3, and b4, that is, the carriers that the first terminal 101 can use to send and / or receive the broadcast service or broadcast sidelink data associated with the first target address are b1, b2, b3, and b4. The network device 102 can determine that the carriers that can be aggregated for the first terminal 101 to send the broadcast service or broadcast sidelink data associated with the first target address are b1, b2, b3, and b4, and can schedule sidelink authorization for the first terminal 101 on carriers b1, b2, b3, and b4.

[0277] Step S2102 , the network device 102 sends scheduling information to the first terminal 101 .

[0278] In some embodiments, the scheduling information may be used to instruct the network device 102 to schedule a sidelink grant for the first terminal 101 on a carrier used for carrier aggregation.

[0279] In some embodiments, the first terminal 101 may receive scheduling information sent by the network device 102 .

[0280] In some embodiments, after receiving the scheduling information sent by the network device 102 , the first terminal 101 may send sidelink data according to the sidelink authorization scheduled by the network device 102 .

[0281] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0282] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0283] The carrier aggregation method involved in the embodiments of the present disclosure may include at least one of steps S2101 and S2102. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, and steps S2101 and S2102 may be implemented as independent embodiments, but are not limited thereto.

[0284] In some embodiments, step S2102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0285] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0286] FIG3A is a flow chart of a carrier aggregation method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a carrier aggregation method for a first terminal 101, the method comprising:

[0287] Step S3101, sending instruction information.

[0288] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0289] In some embodiments, the first terminal 101 may send indication information to the network device 102, but is not limited thereto and may also send indication information to other entities.

[0290] Step S3102, obtain scheduling information.

[0291] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0292] In some embodiments, the first terminal 101 receives scheduling information sent by the network device 102, but is not limited thereto and may also receive scheduling information sent by other entities.

[0293] In some embodiments, the first terminal 101 obtains scheduling information specified by the protocol.

[0294] In some embodiments, the first terminal 101 obtains scheduling information from upper layer(s).

[0295] The carrier aggregation method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3102. For example, step S3101 may be implemented as an independent embodiment, and step S3102 may be implemented as an independent embodiment, but are not limited thereto.

[0296] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0297] FIG3B is a flow chart of a carrier aggregation method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a carrier aggregation method for a first terminal 101, the method comprising:

[0298] Step S3201: Receive first indication information and / or second indication information sent by a second terminal.

[0299] Optional implementations of step S3201 can be found in step S2101 of FIG. 2 , optional implementations of step S3101 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0300] Step S3202: Send first indication information and / or second indication information to the network device.

[0301] Optional implementations of step S3201 can be found in step S2101 of FIG. 2 , optional implementations of step S3101 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0302] Step S3203: Receive scheduling information sent by the network device.

[0303] Optional implementations of step S3203 may refer to step S2102 in FIG. 2 , optional implementations of step S3102 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0304] The carrier aggregation method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3203. For example, step S3201 may be implemented as an independent embodiment, step S3202 may be implemented as an independent embodiment, step S3203 may be implemented as an independent embodiment, step S3201 and step S3202 may be implemented as independent embodiments, and step S3202 and step S3203 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0305] In some embodiments, step S3201 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0306] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0307] FIG3C is a flow chart of a carrier aggregation method according to an embodiment of the present disclosure. As shown in FIG3C , the embodiment of the present disclosure relates to a carrier aggregation method for a first terminal 101, the method comprising:

[0308] Step S3301: Send third indication information to the network device.

[0309] The optional implementation of step S3301 can refer to step S2101 in Figure 2, the optional implementation of step S3101 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0310] Step S3302: Receive scheduling information sent by the network device.

[0311] The optional implementation of step S3302 can refer to step S2102 in Figure 2, the optional implementation of step S3102 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0312] The carrier aggregation method involved in the embodiments of the present disclosure may include at least one of steps S3301 and S3302. For example, step S3301 may be implemented as an independent embodiment, step S3302 may be implemented as an independent embodiment, and step S3303 may be implemented as an independent embodiment, but are not limited thereto.

[0313] In some embodiments, step S3302 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0314] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0315] FIG3D is a flow chart of a carrier aggregation method according to an embodiment of the present disclosure. As shown in FIG3D , the embodiment of the present disclosure relates to a carrier aggregation method for a first terminal 101, the method comprising:

[0316] Step S3401: Receive first indication information and / or second indication information sent by a second terminal.

[0317] Optional implementations of step S3401 can be found in step S2101 of FIG. 2 , optional implementations of step S3101 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0318] Step S3402: Send one or more of the first indication information, the second indication information, and the third indication information to the network device.

[0319] The optional implementation of step S3402 can refer to step S2101 in Figure 2, the optional implementation of step S3101 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0320] Step S3403: receiving scheduling information sent by the network device.

[0321] The optional implementation of step S3403 can be found in the optional implementation of step S2102 in Figure 2, step S3102 in Figure 3A, step S3203 in Figure 3B, step S3302 in Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0322] The carrier aggregation method involved in the embodiments of the present disclosure may include at least one of steps S3401 to S3403. For example, step S3401 may be implemented as an independent embodiment, step S3402 may be implemented as an independent embodiment, and step S3403 may be implemented as an independent embodiment. Steps S3401 and S3402 may be implemented as independent embodiments, and steps S3402 and S3403 may be implemented as independent embodiments, but are not limited thereto.

[0323] In some embodiments, step S3401 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0324] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0325] FIG3E is a flow chart of a carrier aggregation method according to an embodiment of the present disclosure. As shown in FIG3E , the embodiment of the present disclosure relates to a carrier aggregation method for a first terminal 101, the method comprising:

[0326] Step S3501: Send instruction information to the network device.

[0327] In some embodiments, the first terminal 101 may be a sending terminal, and accordingly, there is a second terminal 103 that performs unicast communication with the first terminal 101 as a receiving terminal.

[0328] In some embodiments, the first terminal 101 may be a receiving terminal, and accordingly, there is a second terminal 103 that performs unicast communication with the first terminal 101 as a sending terminal.

[0329] In some embodiments, the resource allocation method of the first terminal 101 may be a method in which the network schedules and sends resources.

[0330] In some embodiments, the first terminal 101 may be a terminal performing sidelink unicast communication.

[0331] In some embodiments, the indication information may include one or more of first indication information, second indication information, and third indication information. The first terminal 101 may send indication information to the network device 102 to indicate relevant information of supported carriers to the network device 102.

[0332] In some embodiments, when the first terminal 101 determines that the indication information has changed compared to the previous indication information, the first terminal 101 may send the indication information to the network device 102. Exemplarily, the previous indication information may refer to the indication information last sent to the network device 102. Exemplarily, the change in the indication information compared to the previous indication information may refer to a change in at least one of the first indication information, the second indication information, and the third indication information compared to the previous one.

[0333] In addition, the first terminal 101 can actively obtain indication information to determine whether the indication information has changed. For example, the first terminal 101 can periodically obtain indication information to compare the currently obtained indication information with the last obtained indication information. Alternatively, the first terminal 101 can obtain indication information and notify the network device only when the indication information has changed. If the first terminal 101 does not obtain new indication information, the first terminal 101 assumes that the indication information has not changed. Accordingly, in the case of the first indication information, when the carrier supported by the second terminal 103 in unicast communication with the first terminal 101 changes, the second terminal 103 sends the first indication information to the first terminal 101 to notify it of the currently supported carrier. In the case of the second indication information, when the preferred carrier supported by the second terminal 103 changes, the second terminal 103 sends the second indication information to the first terminal 101 to notify it of the currently supported carrier. In the case of the third indication information, when the target address associated with the service of the first terminal 101 changes, the first terminal 101 sends the third indication information to the network device to notify it of the carrier supported by the target address.

[0334] In addition, when the indication information changes, the first terminal 101 notifies the network device 102 of the changed indication information. Optionally, the first indication information may send the changed new indication information to the network device 102, or may only send the amount of change in the indication information to the network device 102. For example, taking the indication information including the first indication information as an example, when the carrier supported by the second terminal 103 in unicast communication with the first terminal changes from the previous carriers a and b to carriers a and c, the first terminal 101 may send an indication to the network device 102 to indicate that the second terminal 103 supports carriers a and c, or may send indication information to the network device 102 to indicate that the second terminal 103 no longer supports carrier b and supports carrier c.

[0335] It should be understood that as long as one of the first indication information, the second indication information, and the third indication information included in the indication information changes, the first terminal 101 can trigger reporting of the indication information so that the network device 102 is aware of the latest indication information.

[0336] Exemplarily, when the first indication information changes compared to the previous first indication information (for example, the carrier supported by the second terminal 103 changes compared to the previously supported carrier), the first terminal 101 may send the first indication information to the network device 102. Exemplarily, the previous first indication information may refer to the first indication information last sent to the network device 102.

[0337] Exemplarily, when the second indication information changes compared to the previous second indication information (for example, the carrier preferred by the second terminal 103 changes compared to the previously preferred carrier supported), the first terminal 101 may send the second indication information to the network device 102. Exemplarily, the previous second indication information may refer to the second indication information last sent to the network device 102.

[0338] Exemplarily, when the third indication information changes compared to the previous third indication information (for example, the carrier supported by the first target address changes compared to the previously supported carrier), the first terminal 101 may send the third indication information to the network device 102. Exemplarily, the previous third indication information may refer to the third indication information last sent to the network device 102.

[0339] In some embodiments, the first terminal 101 may send the indication information to the network device 102 via Uu RRC signaling. Exemplarily, the Uu RRC signaling may be SUI signaling, UAI signaling, or other newly defined Uu RRC signaling, which is not specifically limited in the present disclosure.

[0340] In some embodiments, the indication information may include one or more of the first indication information, the second indication information, and the third indication information.

[0341] Exemplarily, the first indication information, the second indication information, and the third indication information may be carried by the same Uu RRC signaling, or may be carried by different Uu RRC signaling, which is not specifically limited in the present disclosure.

[0342] In some embodiments, the first indication information may be used to indicate a carrier supported by the second terminal 103 , and the second indication information may be used to indicate a carrier preferred to be supported by the second terminal 103 .

[0343] In some embodiments, there may be one or more terminals that establish a unicast connection with the first terminal 101, and the second terminal 103 is one of them. In other words, the second terminal 103 is any terminal that establishes a unicast connection with the first terminal 101.

[0344] In some embodiments, the expressions: "carrier", "frequency band", "spectrum", and "frequency" can be used interchangeably.

[0345] In some embodiments, the carrier supported by the second terminal 103 may include a carrier supported by the second terminal 103 for sending and / or receiving. Exemplarily, the carrier supported by the second terminal 103 for sending may refer to a carrier that the second terminal 103 can use to send sidelink data, and the carrier supported by the second terminal 103 for receiving may refer to a carrier that the second terminal 103 can use to receive sidelink data.

[0346] In some embodiments, the carrier that the second terminal 103 preferably supports may include a carrier that the second terminal 103 preferably supports for sending and / or receiving. Exemplarily, the carrier that the second terminal 103 preferably supports may be a carrier that the second terminal 103 recommends for use among the supported carriers. Exemplarily, the carrier that the second terminal 103 preferably supports may be some of the preferred carriers selected by the second terminal 103 on the supported carriers. Exemplarily, the carrier that the second terminal 103 preferably supports for sending may refer to a carrier that the second terminal 103 may preferably use for sending sidelink data, and the carrier that the second terminal 103 preferably supports for receiving may refer to a carrier that the second terminal 103 may preferably use for receiving sidelink data. Here, preferred may refer to a carrier that the second terminal 103 expects to use for sending or receiving information. That is, the second terminal 103 may inform the network device 102 through the first terminal 101 of the carrier that the second terminal 103 expects to use, so that the network device 102 may prioritize scheduling the carrier when possible. The second terminal 103 can recommend its desired single carrier to the first terminal 101, or can recommend one or more of its desired multiple carriers to the first terminal 101, so that the first terminal 101 reports it to the network device 102, thereby enabling the network device 102 to perform targeted scheduling.

[0347] In some embodiments, the support described in the present disclosure may refer to support for sending sidelink data, or support for receiving sidelink data, or support for sending and receiving sidelink data.

[0348] In some embodiments, the supporting sending and / or receiving described in the present disclosure may refer to supporting sending and / or receiving sidelink data.

[0349] In some embodiments, the support for sending described in the present disclosure may refer to supporting the sending of sidelink data, and the support for receiving may refer to supporting the receiving of sidelink data.

[0350] Exemplarily, the first indication information may include a carrier identification list, which may include carrier information of carriers supported for transmission and / or carrier information of carriers supported for reception by the second terminal 103. Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission by the second terminal 103; Exemplarily, the one carrier identification list may include carrier information of carriers supported for reception by the second terminal 103; Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission and carriers supported for reception by the second terminal 103; Exemplarily, the second indication information may include two carrier identification lists, one list including carrier information of carriers supported for transmission by the second terminal 103, and the other list including carrier information of carriers supported for reception by the second terminal 103.

[0351] Exemplarily, the second indication information may include a carrier identification list, which may include carrier information of carriers that the second terminal 103 preferably supports for sending and / or carrier information of carriers that the second terminal 103 preferably supports for receiving. Exemplarily, the one carrier identification list may include carrier information of carriers that the second terminal 103 preferably supports for sending; Exemplarily, the one carrier identification list may include carrier information of carriers that the second terminal 103 preferably supports for receiving; Exemplarily, the one carrier identification list may include carrier information of carriers that the second terminal 103 preferably supports for sending and carriers that the second terminal 103 preferably supports for receiving; Exemplarily, the third indication information may include two carrier identification lists, one list including carrier information of carriers that the second terminal 103 preferably supports for sending, and the other list including carrier information of carriers that the second terminal 103 preferably supports for receiving.

[0352] In some embodiments, expressions in the present disclosure such as “carrier identification list”, “carrier list”, “carrier set”, etc. may be interchangeable.

[0353] In some embodiments, the first indication information may also include one or more of the second target address and service type of the second terminal 103, so that the network device 102 can know the target address and / or service type of the second terminal 103 and make targeted scheduling.

[0354] In some embodiments, the second indication information may also include one or more of the second target address and service type of the second terminal 103, so that the network device 102 can know the target address and / or service type of the second terminal 103 and make targeted scheduling.

[0355] In some embodiments, the second target address may be a target layer 2 address, which means that the second target address and the second target layer 2 address may be interchangeable.

[0356] In some embodiments, the second terminal 103 may send indication information to the first terminal 101 via PC5-RRC signaling, where the indication information may include first indication information and / or second indication information. Exemplarily, the PC5-RRC signaling may be UECapabilityInformationSidelink signaling, UEAssistanceInformationSidelink, or newly defined PC5-RRC signaling, which is not specifically limited in this disclosure. Exemplarily, the second terminal 103 may send the first indication information and / or the second indication information to the first terminal 101 via other PC5 signaling, such as PC5 MAC CE. This disclosure does not specifically limit this.

[0357] In some embodiments, the second terminal 103 may actively send indication information to the first terminal 101, where the indication information may include first indication information and / or second indication information.

[0358] Exemplarily, if the second terminal 103 is motivated to send the first indication information and / or the second indication information, it can send the first indication information and / or the second indication information to the first terminal 101. Exemplarily, after establishing a unicast connection with the first terminal 101, the second terminal 103 can send the first indication information and / or the second indication information to the first terminal 101 (the second indication information and / or the third indication information is sent for the first time after the unicast connection is established).

[0359] Exemplarily, when the first indication information changes compared to the previous first indication information (for example, the carrier supported by the second terminal 103 changes compared to the previously supported carrier), the first indication information is sent to the first terminal 101. Exemplarily, the previous first indication information may refer to the first indication information last sent to the first terminal 101. Thus, when the carrier supported by the second terminal 103 changes, the second terminal 103 can promptly notify the first terminal 101 of the currently supported carrier, so that the first terminal 101 notifies the network device 102.

[0360] Exemplarily, when the second indication information changes compared to the previous second indication information (for example, the carrier preferentially supported by the second terminal 103 changes compared to the previously preferred carrier preferentially supported), the second indication information is sent to the first terminal 101. Exemplarily, the previous second indication information may refer to the second indication information last sent to the first terminal 101. Thus, when the carrier supported by the second terminal 103 changes, the second terminal 103 can promptly notify the first terminal 101 of the currently supported carrier, so that the first terminal 101 notifies the network device 102.

[0361] In some embodiments, the first terminal 101 may send a request message to the second terminal 103 to request indication information, wherein the indication information may include obtaining first indication information and / or second indication information. After receiving the request message, the second terminal 103 sends the first indication information and / or the second indication information to the first terminal 101, so that the first terminal 101 informs the network device 102.

[0362] For example, the first terminal 101 may send the request information to the second terminal 103 via PC5-RRC signaling. For example, the PC5-RRC signaling may be UECapabilityEnquirySidelink signaling or newly defined PC5-RRC signaling, which is not limited in this disclosure. For example, the first terminal 101 may send the request information to the second terminal 103 via other PC5 signaling, such as PC5 MAC CE. This disclosure does not specifically limit this.

[0363] In some embodiments, the request information may include carrier information of the carrier supported by the first terminal 101, and the second terminal 103 may determine the first indication information and / or the second indication information based on the carrier supported by the first terminal 101 and the carrier supported by the second terminal 103.

[0364] Exemplarily, the request information may include carrier information of carriers supported by the first terminal 101. Exemplarily, the carriers supported by the first terminal 101 include carriers supported by the first terminal 101 for receiving and / or transmitting. Exemplarily, the carriers supported by the first terminal 101 for transmitting may refer to carriers that the first terminal 101 may use to transmit sidelink data, and exemplary, the carriers supported by the first terminal 101 for receiving may refer to carriers that the first terminal 101 may use to receive sidelink data.

[0365] Exemplarily, the request information may include carrier information of the carrier that the first terminal 101 preferably supports. Exemplarily, the carrier that the first terminal 101 preferably supports may include the carrier that the first terminal 101 prefers to support sending and / or receiving. Exemplarily, the carrier that the first terminal 101 prefers to support may be some of the preferred carriers selected by the first terminal 101 on the supported carriers. Exemplarily, the carrier that the first terminal 101 prefers to support sending may refer to the carrier that the first terminal 101 prefers to use for sending sidelink data. Exemplarily, the carrier that the first terminal 101 prefers to support receiving may refer to the carrier that the first terminal 101 prefers to use for receiving sidelink data.

[0366] Exemplarily, the second terminal 103 may determine the first indication information and / or the second indication information based on one or more of the carriers supported by the first terminal 101, the carriers preferred by the first terminal 101, and the carriers supported for reception by the second terminal 103. For example, the second terminal 103 may determine the first indication information and / or the second indication information based on the carrier support of the first terminal 101 in unicast communication with itself and its own carrier support, and inform the network device via the first terminal 101. That is, the carrier support of the second terminal 103 obtained by the network device 102 should match the carrier support of the first terminal 101, so that the sending and receiving of the scheduled carrier of the second terminal 103 is compatible with the carrier support capability of the first terminal 101.

[0367] Exemplarily, the request information may include a carrier identification list, which may include carrier information of carriers supported for transmission and / or carrier information of carriers supported for reception by the first terminal 101. Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission by the first terminal 101; Exemplarily, the one carrier identification list may include carrier information of carriers supported for reception by the first terminal 101; Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission and carriers supported for reception by the first terminal 101; Exemplarily, the request information may include two carrier identification lists, one list including carrier information of carriers supported for transmission by the first terminal 101, and the other list including carrier information of carriers supported for reception by the first terminal 101.

[0368] Optionally, the first terminal 101 may send a request message to the second terminal 103 when the resource allocation mode changes. Exemplarily, when the resource allocation mode of the first terminal 101 is configured or reconfigured from mode 1 to mode 2, the request message is sent to the second terminal 103. Exemplarily, when the resource allocation mode of the first terminal 101 is configured or reconfigured from mode 2 to mode 1, the request message is sent to the second terminal 103.

[0369] Optionally, the first terminal 101 may send the request information to the second terminal 103 after establishing a unicast connection with the second terminal 103. Exemplarily, the first terminal 101 may send the request information to the second terminal 103 after establishing a unicast connection with the second terminal 103 based on implementation.

[0370] In some embodiments, the first terminal 101 may receive indication information sent by the second terminal 103 , where the indication information may include first indication information and / or second indication information.

[0371] In some embodiments, the third indication information may be used to indicate a carrier supported by the first target address. Exemplarily, the first target address may be a target layer 2 address.

[0372] In some embodiments, the carrier supported by the first target address may include a carrier supported for reception and / or a carrier supported for transmission by the first target address.

[0373] In some embodiments, the third indication information may further include one or more of the first target address and the service type associated with the first target address.

[0374] In some embodiments, the expressions: first target address and first target layer 2 address may be interchangeable.

[0375] In some embodiments, the first terminal 101 may determine the carriers supported by the first target address based on a mapping relationship between the service type and the first target address and / or a mapping relationship between the service type and the carrier configured by a higher layer. For example, the higher layer may be a V2X layer. For example, if the target address associated with service a1 is b1, and service a1 corresponds to carriers c1 and c2, then the carriers supported by target address b1 are c1 and c2.

[0376] In some embodiments, the first target address may include one or more of a target address associated with a unicast service of the first terminal 101 , a target address associated with a multicast service of the first terminal 101 , and a target address associated with a broadcast service of the first terminal 101 .

[0377] Exemplarily, if the first target address is the target address associated with the unicast service of the first terminal 101, the carrier supported by the first target address may refer to the carrier used by the first terminal 101 to send and / or receive the unicast service or unicast sidelink data associated with the first target address.

[0378] Exemplarily, if the first target address is the target address associated with the multicast service of the first terminal 101, the carrier supported by the first target address may refer to the carrier used by the first terminal 101 to send and / or receive the multicast service or multicast sidelink data associated with the first target address.

[0379] For example, if the first target address is the target address associated with the broadcast service of the first terminal 101, the carrier supported by the first target address may refer to the carrier used by the first terminal 101 to send and / or receive the broadcast service or broadcast sidelink data associated with the first target address.

[0380] In some embodiments, the network device 102 may receive indication information sent by the first terminal 101, wherein the indication information may include one or more of first indication information, second indication information, and third indication information.

[0381] In some embodiments, the network device 102 may determine, based on the indication information, that the first terminal 101 supports the carrier used for carrier aggregation, and schedule a sidelink grant for the first terminal 101 on the carrier used for carrier aggregation. That is, the network device 102 may determine, based on one or more of the first indication information, the second indication information, and the third indication information, that the first terminal 101 supports the carrier used for carrier aggregation, and schedule a sidelink grant for the first terminal 101 on the carrier used for carrier aggregation.

[0382] Optionally, the network device 102 may determine that the first terminal 101 supports a carrier for carrier aggregation based on one or more of the first indication information, the second indication information, and the third indication information, and / or the carrier supported by the first terminal 101, and schedule a sidelink grant for the first terminal 101 on the carrier used for carrier aggregation. Exemplarily, the carrier supported by the first terminal 101 may refer to a carrier supported by the first terminal 101 for sending and / or receiving. Exemplarily, the network device may obtain information about the carrier supported by the first terminal 101 through terminal capability information sent by the first terminal 101.

[0383] In some embodiments, a unicast connection exists between the first terminal 101 and the second terminal 103. The first terminal 101 may send first indication information to the network device 102, where the first indication information indicates a carrier supported by the second terminal 103. The network device 102 may determine, based on the first indication information and / or the carrier supported by the first terminal 101, a carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103, and may schedule a sidelink grant for the first terminal 101 on the carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103. The first terminal 101 is a transmitting terminal, and the second terminal 103 is a receiving terminal.

[0384] Exemplarily, a unicast connection exists between the first terminal 101 and the second terminal 103. The first terminal 101 supports sending carriers A1, A2, A3, and A4, and the second terminal 103 supports receiving carriers A2, A3, and A4. The network device 102 can determine that the carriers supported by the unicast connection between the first terminal 101 and the second terminal 103 for carrier aggregation are A2, A3, and A4, and can schedule a sidelink grant for the first terminal 101 on carriers A2, A3, and A4. Exemplarily, the network device 102 can determine that the carriers supported by the unicast connection between the first terminal 101 and the second terminal 103 for carrier aggregation are A2 and A3, or A2 and A4, or A3 and A4, and can schedule a sidelink grant for the first terminal 101 on A2 and A3, or A2 and A4, or A3 and A4.

[0385] In some embodiments, a unicast connection exists between the first terminal 101 and the second terminal 103. The first terminal 101 may send second indication information to the network device 102, where the second indication information indicates a carrier that the second terminal 103 preferably supports. The network device 102 may determine, based on the second indication information and / or the carrier supported by the first terminal 101, a carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103, and may schedule a sidelink grant for the first terminal 101 on the carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103. The first terminal 101 is a transmitting terminal, and the second terminal 103 is a receiving terminal.

[0386] For example, the first terminal 101 supports carriers A1, A2, A3, and A4 for transmission, and the second terminal 103 preferably supports carriers A2 and A3 for reception. The network device may determine that the carriers supported for carrier aggregation by the unicast connection between the first terminal 101 and the second terminal 103 are A2 and A3, and may schedule a sidelink grant for the first terminal 101 on carriers A2 and A3. Of course, if the second terminal 103 also supports carrier A4, the network device 102 may preferably schedule a sidelink grant for the first terminal 101 on carriers A2 and A3, and use carrier A4 as an alternative to schedule a sidelink grant for the first terminal 101 on carrier A4 when A2 and A3 are unavailable.

[0387] In some embodiments, a unicast connection exists between the first terminal 101 and the second terminal 103. The first terminal 101 may send first indication information and second indication information to the network device 102. The network device 102 may determine, based on the first indication information and / or the second indication information and / or the carrier supported by the first terminal 101, a carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103, and may schedule a sidelink grant for the first terminal 101 on the carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103. The first terminal 101 is a transmitting terminal, and the second terminal 103 is a receiving terminal.

[0388] Exemplarily, the first terminal 101 supports carriers A1, A2, A3, and A4 for transmission, and the second terminal 103 supports carriers A2, A3, and A4 for reception. The second terminal 103 preferentially supports carriers A2 and A3 for reception. The network device can determine that the carriers supported for carrier aggregation by the unicast connection between the first terminal 101 and the second terminal 103 are A2, A3, and A4, and can schedule a sidelink grant for the first terminal 101 on carriers A2, A3, and A4. Exemplarily, the network device can determine that the carriers supported for carrier aggregation by the unicast connection between the first terminal 101 and the second terminal 103 are A2 and A3, and can schedule a sidelink grant for the first terminal 101 on carriers A2 and A3.

[0389] In some embodiments, if the first destination address is the destination address associated with a unicast service of first terminal 101, for example, it may be the address of second terminal 103 that has a unicast connection with first terminal 101. First terminal 101 is a sending terminal, and second terminal 103 is a receiving terminal. A carrier supported by the first destination address is determined based on a high-level configuration. That is, a carrier that first terminal 101 can use to send and / or receive the unicast service or unicast sidelink data associated with the first destination address. First terminal 101 may obtain the first indication information and / or second indication information sent by the first destination address. The first terminal 101 can send one or more of the first indication information, the second indication information, and the third indication information of the first target address to the network device 102, so that for the first target address, the first terminal 101 can report to the network device 102 one or more of the carriers that the first terminal 101 can use to send and / or receive the unicast service or unicast sidelink data associated with the first target address, the carriers that the first target address supports receiving, and the carriers that are preferred to support receiving. The network device 102 can determine the carriers on which the first terminal 101 can aggregate the unicast service or unicast sidelink data associated with the first target address based on one or more of the carriers that the first terminal 101 can use to send and / or receive the unicast service or unicast sidelink data associated with the first target address, the carriers that the first target address supports receiving, and the carriers that are preferred to support receiving, and can schedule sidelink authorization for the first terminal 101 on the carrier used for carrier aggregation.

[0390] In some embodiments, the first terminal 101 may send first indication information and third information to the network device 102, where the first indication information indicates the carrier supported by the first target address, and the third indication information indicates the carrier that the first terminal 101 can use to send and / or receive the unicast service or unicast sidelink data associated with the first target address. The network device 102 may determine the carrier for carrier aggregation supported by the first terminal 101 for sending the unicast service or unicast sidelink data associated with the first target address based on the first indication information, the third information, and one or more of the carriers supported by the first terminal 101, and may schedule sidelink authorization for the first terminal 101 on the carrier for carrier aggregation supported by the first terminal 101 for sending the unicast service or unicast sidelink data associated with the first target address.

[0391] Exemplarily, the first terminal 101 determines, based on high-level configuration, that the carriers supported by the first target address are A1, A2, A3, and A4, that is, the carriers that the first terminal 101 can use to send and / or receive unicast services or unicast sidelink data associated with the first target address are A1, A2, A3, and A4. The first target address supports receiving carriers A2, A3, and A4. The network device 102 can determine that the carriers supported for carrier aggregation by the first terminal 101 for sending unicast services or unicast sidelink data associated with the first target address are A2, A3, and A4, and can schedule sidelink authorization for the first terminal 101 on carriers A2, A3, and A4. Exemplarily, the network device 102 can determine that the carriers supported for carrier aggregation for the first terminal 101 to send unicast services or unicast sidelink data associated with the first target address are A2 and A3, or A2 and A4, or A3 and A4, and can schedule sidelink authorization for the first terminal 101 on A2 and A3, or A2 and A4, or A3 and A4.

[0392] In some embodiments, the first terminal 101 may send second indication information and third indication information to the network device 102, where the second indication information indicates the carrier that is preferentially supported by the first target address, and the third indication information indicates the carrier that is preferentially used by the first terminal 101 to send and / or receive the unicast service or unicast sidelink data associated with the first target address. The network device 102 may determine the carrier for carrier aggregation supported by the first terminal 101 for sending the unicast service or unicast sidelink data associated with the first target address based on the second indication information, the third indication information, and one or more of the carriers supported by the first terminal 101, and may schedule sidelink authorization for the first terminal 101 on the carrier for carrier aggregation supported by the first terminal 101 for sending the unicast service or unicast sidelink data associated with the first target address.

[0393] Exemplarily, the first terminal 101 determines, based on high-level configuration, that the carriers supported by the first target address are A1, A2, A3, and A4, that is, the carriers that the first terminal 101 can use to send and / or receive unicast services or unicast sidelink data associated with the first target address are A1, A2, A3, and A4, and the first target address preferentially supports receiving carriers A2 and A3. The network device 102 can determine that the carriers supported for carrier aggregation for the first terminal 101 to send unicast services or unicast sidelink data associated with the first target address are A2 and A3, and can schedule sidelink authorization for the first terminal 101 on carriers A2 and A3.

[0394] In some embodiments, if the first target address is the target address associated with the multicast service of the first terminal 101, illustratively, the target address associated with the multicast service that the first terminal 101 is interested in sending and / or receiving. Then, the carrier supported by the first target address is determined according to the high-level configuration. The carrier supported by the first target address is, that is, the carrier that the first terminal 101 can use to send and / or receive the multicast service or multicast sidelink data associated with the first target address. The first terminal 101 can send a third indication message to the network device 102. The network device 102 can determine, based on the third indication message, the carrier on which the first terminal 101 can aggregate the multicast service or multicast sidelink data associated with the first target address, and can schedule a sidelink authorization for the first terminal 101 on the carrier used for carrier aggregation.

[0395] Exemplarily, the first terminal 101 determines, based on high-level configuration, that the carriers supported by the first target address are a1, a2, a3, and a4, that is, the carriers that the first terminal 101 can use to send and / or receive the multicast service or multicast sidelink data associated with the first target address are a1, a2, a3, and a4. The network device 102 can determine that the carriers that can be aggregated for the first terminal 101 to send the multicast service or multicast sidelink data associated with the first target address are a1, a2, a3, and a4, and can schedule sidelink authorization for the first terminal 101 on carriers a1, a2, a3, and a4.

[0396] In some embodiments, if the first target address is a target address associated with a broadcast service of the first terminal 101, illustratively, the target address associated with a broadcast service that the first terminal 101 is interested in sending and / or receiving. Then, the carrier supported by the first target address is determined according to the high-level configuration. The carrier supported by the first target address is, that is, the carrier that the first terminal 101 can use to send and / or receive the broadcast service or broadcast sidelink data associated with the first target address. The first terminal 101 can send a third indication message to the network device 102. The network device 102 can determine, based on the third indication message, the carrier on which the first terminal 101 can aggregate the broadcast service or broadcast sidelink data associated with the first target address, and can schedule a sidelink authorization for the first terminal 101 on the carrier used for carrier aggregation.

[0397] Exemplarily, the first terminal 101 determines, based on high-level configuration, that the carriers supported by the first target address are b1, b2, b3, and b4. That is, the first terminal 101 can use b1, b2, b3, and b4 to send and / or receive the broadcast service or broadcast sidelink data associated with the first target address. The network device 102 can determine that the carriers that can be aggregated for the first terminal 101 to send the broadcast service or broadcast sidelink data associated with the first target address are b1, b2, b3, and b4, and can schedule a sidelink grant for the first terminal 101 on carriers b1, b2, b3, and b4. In some embodiments, the network device 102 can send scheduling information to the first terminal 101.

[0398] In some embodiments, the scheduling information may be used to instruct the network device 102 to schedule a sidelink grant for the first terminal 101 on a carrier used for carrier aggregation.

[0399] In some embodiments, the first terminal 101 may receive scheduling information sent by the network device 102 .

[0400] In some embodiments, after receiving the scheduling information sent by the network device 102 , the first terminal 101 may send sidelink data according to the sidelink authorization scheduled by the network device 102 .

[0401] In this embodiment or example, all optional modes or optional examples may be arbitrarily combined unless there is any contradiction.

[0402] FIG4A is a flow chart of a carrier aggregation method according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a carrier aggregation method for a network device 102, the method comprising:

[0403] Step S4101, obtain instruction information.

[0404] In some embodiments, the network device 102 receives indication information sent by the first terminal 101, but is not limited thereto and may also receive indication information sent by other entities.

[0405] In some embodiments, the network device 102 obtains indication information specified by the protocol.

[0406] In some embodiments, the network device 102 obtains indication information from upper layer(s).

[0407] Step S4102, sending scheduling information.

[0408] In some embodiments, the network device 102 may send scheduling information to the first terminal 101, but is not limited thereto and may also send scheduling information to other entities.

[0409] The carrier aggregation method involved in the embodiments of the present disclosure may include at least one of steps S4101 and S4102. For example, step S4101 may be implemented as an independent embodiment, and step S4102 may be implemented as an independent embodiment, but are not limited thereto.

[0410] In some embodiments, step S4102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0411] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0412] FIG4B is a flow chart of a carrier aggregation method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a carrier aggregation method for a network device 102, the method comprising:

[0413] Step S4201: Receive first indication information and / or second indication information sent by a first terminal.

[0414] The optional implementation of step S4201 can refer to step S2101 in Figure 2, the optional implementation of step S4101 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0415] Step S4202: Determine a carrier for carrier aggregation according to the first indication information and / or the second indication information.

[0416] The optional implementation of step S4202 can refer to the optional implementation of step S2101 in Figure 2, step S4102 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0417] Step S4203: Send scheduling information to the first terminal.

[0418] The optional implementation of step S4203 can refer to the optional implementation of step S2101 in Figure 2, step S4102 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0419] The carrier aggregation method involved in the embodiments of the present disclosure may include at least one of steps S4201 to S4203. For example, step S4201 may be implemented as an independent embodiment, step S4202 may be implemented as an independent embodiment, step S4202 may be implemented as an independent embodiment, step S4201 and step S4202 may be implemented as independent embodiments, and step S4202 and step S4203 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0420] In some embodiments, step S4202 and step S4203 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0421] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0422] FIG4C is a flow chart of a carrier aggregation method according to an embodiment of the present disclosure. As shown in FIG4C , the embodiment of the present disclosure relates to a carrier aggregation method for a network device 102, the method comprising:

[0423] Step S4301: Receive third indication information sent by the first terminal.

[0424] The optional implementation of step S4301 can refer to step S2101 in Figure 2, the optional implementation of step S4101 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0425] Step S4302: Determine a carrier for carrier aggregation according to the third indication information.

[0426] The optional implementation of step S4302 can refer to step S2101 in Figure 2, the optional implementation of step S4101 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0427] Step S4303: Send scheduling information to the first terminal.

[0428] The optional implementation of step S4303 can refer to step S2101 in Figure 2, the optional implementation of step S4101 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0429] The carrier aggregation method involved in the embodiments of the present disclosure may include at least one of steps S4301 to S4303. For example, step S4301 may be implemented as an independent embodiment, step S4302 may be implemented as an independent embodiment, step S4302 may be implemented as an independent embodiment, step S4301 and step S4302 may be implemented as independent embodiments, and step S4302 and step S4303 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0430] In some embodiments, step S4302 and step S4303 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0431] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0432] FIG4D is a flow chart of a carrier aggregation method according to an embodiment of the present disclosure. As shown in FIG4D , the embodiment of the present disclosure relates to a carrier aggregation method for a network device 102, the method comprising:

[0433] Step S4401: Receive indication information sent by the first terminal, where the indication information includes one or more of first indication information, second indication information, and third indication information.

[0434] The optional implementation of step S4401 can refer to step S2101 in Figure 2, the optional implementation of step S4101 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0435] Step S4402: Determine a carrier for carrier aggregation according to the indication information.

[0436] The optional implementation of step S4402 can refer to step S2101 in Figure 2, the optional implementation of step S4101 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0437] Step S4403: Send scheduling information to the first terminal.

[0438] The optional implementation of step S4403 can refer to step S2101 in Figure 2, the optional implementation of step S4101 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0439] The carrier aggregation method involved in the embodiments of the present disclosure may include at least one of steps S4401 to S4403. For example, step S4401 may be implemented as an independent embodiment, step S4402 may be implemented as an independent embodiment, step S4402 may be implemented as an independent embodiment, step S4401 and step S4402 may be implemented as independent embodiments, and step S4402 and step S4403 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0440] In some embodiments, step S4402 and step S4403 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0441] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined.

[0442] FIG4E is a flow chart of a carrier aggregation method according to an embodiment of the present disclosure. As shown in FIG4E , the embodiment of the present disclosure relates to a carrier aggregation method for a network device 102, the method comprising:

[0443] Step S4501: Receive indication information sent by the first terminal.

[0444] In some embodiments, the first terminal 101 may be a sending terminal, and accordingly, there is a second terminal 103 that performs unicast communication with the first terminal 101 as a receiving terminal.

[0445] In some embodiments, the first terminal 101 may be a receiving terminal, and accordingly, there is a second terminal 103 that performs unicast communication with the first terminal 101 as a sending terminal.

[0446] In some embodiments, the resource allocation method of the first terminal 101 may be a method in which the network schedules sending resources (mode 1, mode 1).

[0447] In some embodiments, the first terminal 101 may be a terminal performing sidelink unicast communication.

[0448] In some embodiments, the indication information may include one or more of first indication information, second indication information, and third indication information. The first terminal 101 may send indication information to the network device 102 to indicate to the network device 102 information related to the supported carriers. In some embodiments, if the first terminal 101 determines that the indication information has changed compared to the previous indication information, the first terminal 101 may send the indication information to the network device 102. Exemplarily, the previous indication information may refer to the indication information last sent to the network device 102. Exemplarily, the change in the indication information compared to the previous indication information may refer to a change in at least one of the first indication information, the second indication information, and the third indication information. In addition, the first terminal 101 may actively obtain the indication information to determine whether the indication information has changed. For example, the first terminal 101 may periodically obtain the indication information to compare the currently obtained indication information with the last obtained indication information. Alternatively, the first terminal 101 may obtain the indication information and notify the network device only if the indication information has changed. If the first terminal 101 does not obtain new indication information, the first terminal 101 considers that the indication information has not changed. Accordingly, in the case of the first indication information, when the carrier supported by the second terminal 103 in unicast communication with the first terminal 101 changes, the second terminal 103 sends the first indication information to the first terminal 101 to inform it of the currently supported carrier; in the case of the second indication information, when the carrier preferred by the second terminal 103 changes, the second terminal 103 sends the second indication information to the first terminal 101 to inform it of the currently supported carrier. In the case of the third indication information, when the target address associated with the service of the first terminal 101 changes, the first terminal 101 sends the third indication information to the network device to inform it of the carrier supported by the target address.

[0449] In addition, when the indication information changes, the first terminal 101 notifies the network device 102 of the changed indication information. Optionally, the first indication information may send the changed new indication information to the network device 102, or may only send the amount of change in the indication information to the network device 102. For example, taking the indication information including the first indication information as an example, when the carrier supported by the second terminal 103 in unicast communication with the first terminal changes from the previous carriers a and b to carriers a and c, the first terminal 101 may send an indication to the network device 102 to indicate that the second terminal 103 supports carriers a and c, or may send indication information to the network device 102 to indicate that the second terminal 103 no longer supports carrier b and supports carrier c.

[0450] It should be understood that as long as one of the first indication information, the second indication information, and the third indication information included in the indication information changes, the first terminal 101 can trigger reporting of the indication information so that the network device 102 is aware of the latest indication information.

[0451] Exemplarily, when the first indication information changes compared to the previous first indication information (for example, the carrier supported by the second terminal 103 changes compared to the previously supported carrier), the first terminal 101 may send the first indication information to the network device 102. Exemplarily, the previous first indication information may refer to the first indication information last sent to the network device 102.

[0452] Exemplarily, when the second indication information changes compared to the previous second indication information (for example, the carrier preferred by the second terminal 103 changes compared to the previously preferred carrier supported), the first terminal 101 may send the second indication information to the network device 102. Exemplarily, the previous second indication information may refer to the second indication information last sent to the network device 102.

[0453] Exemplarily, when the third indication information changes compared to the previous third indication information (for example, the carrier supported by the first target address changes compared to the previously supported carrier), the first terminal 101 may send the third indication information to the network device 102. Exemplarily, the previous third indication information may refer to the third indication information last sent to the network device 102.

[0454] In some embodiments, the first terminal 101 may send the indication information to the network device 102 via Uu RRC signaling. Exemplarily, the Uu RRC signaling may be SUI signaling, UAI signaling, or other newly defined Uu RRC signaling, which is not specifically limited in the present disclosure.

[0455] In some embodiments, the indication information may include one or more of the first indication information, the second indication information, and the third indication information. For example, the first indication information, the second indication information, and the third indication information may be carried using the same Uu RRC signaling or different Uu RRC signaling, which is not specifically limited in this disclosure.

[0456] In some embodiments, the first indication information may be used to indicate a carrier supported by the second terminal 103 , and the second indication information may be used to indicate a carrier preferred to be supported by the second terminal 103 .

[0457] In some embodiments, there may be one or more terminals that establish a unicast connection with the first terminal 101, and the second terminal 103 is one of them. In other words, the second terminal 103 is any terminal that establishes a unicast connection with the first terminal 101.

[0458] In some embodiments, the expressions: "carrier", "frequency band", "spectrum", and "frequency" can be used interchangeably.

[0459] In some embodiments, the carrier supported by the second terminal 103 may include a carrier supported by the second terminal 103 for sending and / or receiving. Exemplarily, the carrier supported by the second terminal 103 for sending may refer to a carrier that the second terminal 103 can use to send sidelink data, and the carrier supported by the second terminal 103 for receiving may refer to a carrier that the second terminal 103 can use to receive sidelink data.

[0460] In some embodiments, the carrier that the second terminal 103 preferably supports may include a carrier that the second terminal 103 preferably supports for sending and / or receiving. Exemplarily, the carrier that the second terminal 103 preferably supports may be a carrier that the second terminal 103 recommends for use among the supported carriers. Exemplarily, the carrier that the second terminal 103 preferably supports may be some of the preferred carriers selected by the second terminal 103 on the supported carriers. Exemplarily, the carrier that the second terminal 103 preferably supports for sending may refer to a carrier that the second terminal 103 may preferably use for sending sidelink data, and the carrier that the second terminal 103 preferably supports for receiving may refer to a carrier that the second terminal 103 may preferably use for receiving sidelink data. Here, preferred may refer to a carrier that the second terminal 103 expects to use for sending or receiving information. That is, the second terminal 103 may inform the network device 102 through the first terminal 101 of the carrier that the second terminal 103 expects to use, so that the network device 102 may prioritize scheduling the carrier when possible. The second terminal 103 can recommend its desired single carrier to the first terminal 101, or can recommend one or more of its desired multiple carriers to the first terminal 101, so that the first terminal 101 reports it to the network device 102, thereby enabling the network device 102 to perform targeted scheduling.

[0461] In some embodiments, the support described in the present disclosure may refer to support for sending sidelink data, or support for receiving sidelink data, or support for sending and receiving sidelink data.

[0462] In some embodiments, the supporting sending and / or receiving described in the present disclosure may refer to supporting sending and / or receiving sidelink data.

[0463] In some embodiments, the support for sending described in the present disclosure may refer to supporting the sending of sidelink data, and the support for receiving may refer to supporting the receiving of sidelink data.

[0464] Exemplarily, the first indication information may include a carrier identification list, which may include carrier information of carriers supported for transmission and / or carrier information of carriers supported for reception by the second terminal 103. Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission by the second terminal 103; Exemplarily, the one carrier identification list may include carrier information of carriers supported for reception by the second terminal 103; Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission and carriers supported for reception by the second terminal 103; Exemplarily, the second indication information may include two carrier identification lists, one list including carrier information of carriers supported for transmission by the second terminal 103, and the other list including carrier information of carriers supported for reception by the second terminal 103.

[0465] Exemplarily, the second indication information may include a carrier identification list, which may include carrier information of carriers that the second terminal 103 preferably supports for sending and / or carrier information of carriers that the second terminal 103 preferably supports for receiving. Exemplarily, the one carrier identification list may include carrier information of carriers that the second terminal 103 preferably supports for sending; Exemplarily, the one carrier identification list may include carrier information of carriers that the second terminal 103 preferably supports for receiving; Exemplarily, the one carrier identification list may include carrier information of carriers that the second terminal 103 preferably supports for sending and carriers that the second terminal 103 preferably supports for receiving; Exemplarily, the third indication information may include two carrier identification lists, one list including carrier information of carriers that the second terminal 103 preferably supports for sending, and the other list including carrier information of carriers that the second terminal 103 preferably supports for receiving.

[0466] In some embodiments, expressions in the present disclosure such as “carrier identification list”, “carrier list”, “carrier set”, etc. may be interchangeable.

[0467] In some embodiments, the first indication information may also include one or more of the second target address and service type of the second terminal 103, so that the network device 102 can know the target address and / or service type of the second terminal 103 and make targeted scheduling.

[0468] In some embodiments, the second indication information may also include one or more of the second target address and service type of the second terminal 103, so that the network device 102 can know the target address and / or service type of the second terminal 103 and make targeted scheduling.

[0469] In some embodiments, the expressions: second target address and second target layer 2 address may be interchangeable.

[0470] In some embodiments, the second terminal 103 may send indication information to the first terminal 101 via PC5-RRC signaling, where the indication information may include first indication information and / or second indication information. Exemplarily, the PC5-RRC signaling may be UECapabilityInformationSidelink signaling, UEAssistanceInformationSidelink, or newly defined PC5-RRC signaling, which is not specifically limited in this disclosure. Exemplarily, the second terminal 103 may send the first indication information and / or the second indication information to the first terminal 101 via other PC5 signaling, such as PC5 MAC CE. This disclosure does not specifically limit this.

[0471] In some embodiments, the second terminal 103 may actively send indication information to the first terminal 101, where the indication information may include first indication information and / or second indication information.

[0472] Exemplarily, if the second terminal 103 is motivated to send the first indication information and / or the second indication information, it can send the first indication information and / or the second indication information to the first terminal 101. Exemplarily, after establishing a unicast connection with the first terminal 101, the second terminal 103 can send the first indication information and / or the second indication information to the first terminal 101 (the second indication information and / or the third indication information is sent for the first time after the unicast connection is established).

[0473] Exemplarily, when the first indication information changes compared to the previous first indication information (for example, the carrier supported by the second terminal 103 changes compared to the previously supported carrier), the first indication information is sent to the first terminal 101. Exemplarily, the previous first indication information may refer to the first indication information last sent to the first terminal 101. Thus, when the carrier supported by the second terminal 103 changes, the second terminal 103 can promptly notify the first terminal 101 of the currently supported carrier, so that the first terminal 101 notifies the network device 102.

[0474] Exemplarily, when the second indication information changes compared to the previous second indication information (for example, the carrier preferentially supported by the second terminal 103 changes compared to the previously preferred carrier preferentially supported), the second indication information is sent to the first terminal 101. Exemplarily, the previous second indication information may refer to the second indication information last sent to the first terminal 101. Thus, when the carrier supported by the second terminal 103 changes, the second terminal 103 can promptly notify the first terminal 101 of the currently supported carrier, so that the first terminal 101 notifies the network device 102.

[0475] In some embodiments, the first terminal 101 may send a request message to the second terminal 103 to request to obtain indication information, wherein the indication information may include first indication information and / or second indication information. After receiving the request message, the second terminal 103 sends the first indication information and / or the second indication information to the first terminal 101, so that the first terminal 101 informs the network device 102.

[0476] For example, the first terminal 101 may send the request information to the second terminal 103 via PC5-RRC signaling. For example, the PC5-RRC signaling may be UECapabilityEnquirySidelink signaling or newly defined PC5-RRC signaling, which is not limited in this disclosure. For example, the first terminal 101 may send the request information to the second terminal 103 via other PC5 signaling, such as PC5 MAC CE. This disclosure does not specifically limit this.

[0477] In some embodiments, the request information may include carrier information of the carrier supported by the first terminal 101, and the second terminal 103 may determine the first indication information and / or the second indication information based on the carrier supported by the first terminal 101 and the carrier supported by the second terminal 103.

[0478] Exemplarily, the request information may include carrier information of carriers supported by the first terminal 101. Exemplarily, the carriers supported by the first terminal 101 include carriers supported by the first terminal 101 for receiving and / or sending. Exemplarily, the carriers supported by the first terminal 101 for sending may refer to carriers that the first terminal 101 may use to send sidelink data, and exemplary, the carriers supported by the first terminal 101 for receiving may refer to carriers that the first terminal 101 may use to receive sidelink data.

[0479] Exemplarily, the request information may include carrier information of the carrier that the first terminal 101 preferably supports. Exemplarily, the carrier that the first terminal 101 preferably supports may include the carrier that the first terminal 101 prefers to support sending and / or receiving. Exemplarily, the carrier that the first terminal 101 prefers to support may be some of the preferred carriers selected by the first terminal 101 on the supported carriers. Exemplarily, the carrier that the first terminal 101 prefers to support sending may refer to the carrier that the first terminal 101 prefers to use for sending sidelink data. Exemplarily, the carrier that the first terminal 101 prefers to support receiving may refer to the carrier that the first terminal 101 prefers to use for receiving sidelink data.

[0480] Exemplarily, the second terminal 103 may determine the first indication information and / or the second indication information based on one or more of the carriers supported by the first terminal 101, the carriers preferred by the first terminal 101, and the carriers supported for reception by the second terminal 103. For example, the second terminal 103 may determine the first indication information and / or the second indication information based on the carrier support of the first terminal 101 in unicast communication with itself and its own carrier support, and inform the network device via the first terminal 101. That is, the carrier support of the second terminal 103 obtained by the network device 102 should match the carrier support of the first terminal 101, so that the sending and receiving of the scheduled carrier of the second terminal 103 is compatible with the carrier support capability of the first terminal 101.

[0481] Exemplarily, the request information may include a carrier identification list, which may include carrier information of carriers supported for transmission and / or carrier information of carriers supported for reception by the first terminal 101. Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission by the first terminal 101; Exemplarily, the one carrier identification list may include carrier information of carriers supported for reception by the first terminal 101; Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission and carriers supported for reception by the first terminal 101; Exemplarily, the request information may include two carrier identification lists, one list including carrier information of carriers supported for transmission by the first terminal 101, and the other list including carrier information of carriers supported for reception by the first terminal 101.

[0482] Optionally, the first terminal 101 may send a request message to the second terminal 103 when the resource allocation mode changes. Exemplarily, when the resource allocation mode of the first terminal 101 is configured or reconfigured from mode 1 to mode 2, the request message is sent to the second terminal 103. Exemplarily, when the resource allocation mode of the first terminal 101 is configured or reconfigured from mode 2 to mode 1, the request message is sent to the second terminal 103.

[0483] Optionally, the first terminal 101 may send the request information to the second terminal 103 after establishing a unicast connection with the second terminal 103. Exemplarily, the first terminal 101 may send the request information to the second terminal 103 after establishing a unicast connection with the second terminal 103 based on implementation.

[0484] In some embodiments, the first terminal 101 may receive indication information sent by the second terminal 103 , where the indication information may include first indication information and / or second indication information.

[0485] In some embodiments, the third indication information may be used to indicate a carrier supported by the first target address. Exemplarily, the first target address may be a target layer 2 address.

[0486] In some embodiments, the carrier supported by the first target address may include a carrier supported for reception and / or a carrier supported for transmission by the first target address.

[0487] In some embodiments, the expressions: first target address and first target layer 2 address may be interchangeable.

[0488] In some embodiments, the first terminal 101 may determine the carriers supported by the first target address based on a mapping relationship between the service type and the first target address and / or a mapping relationship between the service type and the carrier configured by a higher layer. For example, the higher layer may be a V2X layer. For example, if the target address associated with service a1 is b1, and service a1 corresponds to carriers c1 and c2, then the carriers supported by target address b1 are c1 and c2.

[0489] Exemplarily, if the first target address is the target address associated with the unicast service of the first terminal 101, the carrier supported by the first target address may refer to the carrier used by the first terminal 101 to send and / or receive the unicast service or unicast sidelink data associated with the first target address.

[0490] Exemplarily, if the first target address is the target address associated with the multicast service of the first terminal 101, the carrier supported by the first target address may refer to the carrier used by the first terminal 101 to send and / or receive the multicast service or multicast sidelink data associated with the first target address.

[0491] Exemplarily, if the first target address is the target address associated with the broadcast service of the first terminal 101, the carrier supported by the first target address may refer to the carrier used by the first terminal 101 to send and / or receive the broadcast service or broadcast sidelink data associated with the first target address.

[0492] In some embodiments, the network device 102 may receive indication information sent by the first terminal 101, wherein the indication information may include one or more of first indication information, second indication information, and third indication information.

[0493] In some embodiments, the network device 102 may determine, based on the indication information, that the first terminal 101 supports the carrier used for carrier aggregation, and schedule a sidelink grant for the first terminal 101 on the carrier used for carrier aggregation. That is, the network device 102 may determine, based on one or more of the first indication information, the second indication information, and the third indication information, that the first terminal 101 supports the carrier used for carrier aggregation, and schedule a sidelink grant for the first terminal 101 on the carrier used for carrier aggregation.

[0494] Optionally, the network device 102 may determine that the first terminal 101 supports a carrier for carrier aggregation based on one or more of the first indication information, the second indication information, and the third indication information, and / or the carrier supported by the first terminal 101, and schedule a sidelink grant for the first terminal 101 on the carrier used for carrier aggregation. Exemplarily, the carrier supported by the first terminal 101 may refer to a carrier supported by the first terminal 101 for sending and / or receiving. Exemplarily, the network device may obtain information about the carrier supported by the first terminal 101 through terminal capability information sent by the first terminal 101.

[0495] In some embodiments, a unicast connection exists between the first terminal 101 and the second terminal 103. The first terminal 101 may send first indication information to the network device 102, where the first indication information indicates a carrier supported by the second terminal 103. The network device 102 may determine, based on the first indication information and / or the carrier supported by the first terminal 101, a carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103, and may schedule a sidelink grant for the first terminal 101 on the carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103. The first terminal 101 is a transmitting terminal, and the second terminal 103 is a receiving terminal.

[0496] Exemplarily, a unicast connection exists between the first terminal 101 and the second terminal 103. The first terminal 101 supports sending carriers A1, A2, A3, and A4, and the second terminal 103 supports receiving carriers A2, A3, and A4. The network device 102 can determine that the carriers supported by the unicast connection between the first terminal 101 and the second terminal 103 for carrier aggregation are A2, A3, and A4, and can schedule a sidelink grant for the first terminal 101 on carriers A2, A3, and A4. Exemplarily, the network device 102 can determine that the carriers supported by the unicast connection between the first terminal 101 and the second terminal 103 for carrier aggregation are A2 and A3, or A2 and A4, or A3 and A4, and can schedule a sidelink grant for the first terminal 101 on A2 and A3, or A2 and A4, or A3 and A4.

[0497] In some embodiments, a unicast connection exists between the first terminal 101 and the second terminal 103. The first terminal 101 may send second indication information to the network device 102, where the second indication information indicates a carrier that the second terminal 103 preferably supports. The network device 102 may determine, based on the second indication information and / or the carrier supported by the first terminal 101, a carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103, and may schedule a sidelink grant for the first terminal 101 on the carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103. The first terminal 101 is a transmitting terminal, and the second terminal 103 is a receiving terminal.

[0498] For example, the first terminal 101 supports carriers A1, A2, A3, and A4 for transmission, and the second terminal 103 preferably supports carriers A2 and A3 for reception. The network device may determine that the carriers supported for carrier aggregation by the unicast connection between the first terminal 101 and the second terminal 103 are A2 and A3, and may schedule a sidelink grant for the first terminal 101 on carriers A2 and A3. Of course, if the second terminal 103 also supports carrier A4, the network device 102 may preferably schedule a sidelink grant for the first terminal 101 on carriers A2 and A3, and use carrier A4 as an alternative to schedule a sidelink grant for the first terminal 101 on carrier A4 when A2 and A3 are unavailable.

[0499] In some embodiments, a unicast connection exists between the first terminal 101 and the second terminal 103. The first terminal 101 may send first indication information and second indication information to the network device 102. The network device 102 may determine, based on the first indication information and / or the second indication information and / or the carrier supported by the first terminal 101, a carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103, and may schedule a sidelink grant for the first terminal 101 on the carrier for carrier aggregation supported by the unicast connection between the first terminal 101 and the second terminal 103. The first terminal 101 is a transmitting terminal, and the second terminal 103 is a receiving terminal.

[0500] Exemplarily, the first terminal 101 supports carriers A1, A2, A3, and A4 for transmission, and the second terminal 103 supports carriers A2, A3, and A4 for reception. The second terminal 103 preferentially supports carriers A2 and A3 for reception. The network device can determine that the carriers supported for carrier aggregation by the unicast connection between the first terminal 101 and the second terminal 103 are A2, A3, and A4, and can schedule a sidelink grant for the first terminal 101 on carriers A2, A3, and A4. Exemplarily, the network device can determine that the carriers supported for carrier aggregation by the unicast connection between the first terminal 101 and the second terminal 103 are A2 and A3, and can schedule a sidelink grant for the first terminal 101 on carriers A2 and A3.

[0501] In some embodiments, if the first destination address is the destination address associated with a unicast service of first terminal 101, for example, it may be the address of second terminal 103 that has a unicast connection with first terminal 101. First terminal 101 is a sending terminal, and second terminal 103 is a receiving terminal. A carrier supported by the first destination address is determined based on a high-level configuration. That is, a carrier that first terminal 101 can use to send and / or receive the unicast service or unicast sidelink data associated with the first destination address. First terminal 101 may obtain the first indication information and / or second indication information sent by the first destination address. The first terminal 101 can send one or more of the first indication information, the second indication information, and the third indication information of the first target address to the network device 102, so that for the first target address, the first terminal 101 can report to the network device 102 one or more of the carriers that the first terminal 101 can use to send and / or receive the unicast service or unicast sidelink data associated with the first target address, the carriers that the first target address supports receiving, and the carriers that are preferred to support receiving. The network device 102 can determine the carriers on which the first terminal 101 can aggregate the unicast service or unicast sidelink data associated with the first target address based on one or more of the carriers that the first terminal 101 can use to send and / or receive the unicast service or unicast sidelink data associated with the first target address, the carriers that the first target address supports receiving, and the carriers that are preferred to support receiving, and can schedule sidelink authorization for the first terminal 101 on the carrier used for carrier aggregation.

[0502] In some embodiments, the first terminal 101 may send first indication information and third information to the network device 102, where the first indication information indicates the carrier supported by the first target address, and the third indication information indicates the carrier that the first terminal 101 can use to send and / or receive the unicast service or unicast sidelink data associated with the first target address. The network device 102 may determine the carrier for carrier aggregation supported by the first terminal 101 for sending the unicast service or unicast sidelink data associated with the first target address based on the first indication information, the third information, and one or more of the carriers supported by the first terminal 101, and may schedule sidelink authorization for the first terminal 101 on the carrier for carrier aggregation supported by the first terminal 101 for sending the unicast service or unicast sidelink data associated with the first target address.

[0503] Exemplarily, the first terminal 101 determines, based on high-level configuration, that the carriers supported by the first target address are A1, A2, A3, and A4, that is, the carriers that the first terminal 101 can use to send and / or receive unicast services or unicast sidelink data associated with the first target address are A1, A2, A3, and A4. The first target address supports receiving carriers A2, A3, and A4. The network device 102 can determine that the carriers supported for carrier aggregation by the first terminal 101 for sending unicast services or unicast sidelink data associated with the first target address are A2, A3, and A4, and can schedule sidelink authorization for the first terminal 101 on carriers A2, A3, and A4. Exemplarily, the network device 102 can determine that the carriers supported for carrier aggregation for the first terminal 101 to send unicast services or unicast sidelink data associated with the first target address are A2 and A3, or A2 and A4, or A3 and A4, and can schedule sidelink authorization for the first terminal 101 on A2 and A3, or A2 and A4, or A3 and A4.

[0504] In some embodiments, the first terminal 101 may send second indication information and third indication information to the network device 102, where the second indication information indicates the carrier that is preferentially supported by the first target address, and the third indication information indicates the carrier that is preferentially used by the first terminal 101 to send and / or receive the unicast service or unicast sidelink data associated with the first target address. The network device 102 may determine the carrier for carrier aggregation supported by the first terminal 101 for sending the unicast service or unicast sidelink data associated with the first target address based on the second indication information, the third indication information, and one or more of the carriers supported by the first terminal 101, and may schedule sidelink authorization for the first terminal 101 on the carrier for carrier aggregation supported by the first terminal 101 for sending the unicast service or unicast sidelink data associated with the first target address.

[0505] Exemplarily, the first terminal 101 determines, based on high-level configuration, that the carriers supported by the first target address are A1, A2, A3, and A4, that is, the carriers that the first terminal 101 can use to send and / or receive unicast services or unicast sidelink data associated with the first target address are A1, A2, A3, and A4, and the first target address preferentially supports receiving carriers A2 and A3. The network device 102 can determine that the carriers supported for carrier aggregation for the first terminal 101 to send unicast services or unicast sidelink data associated with the first target address are A2 and A3, and can schedule sidelink authorization for the first terminal 101 on carriers A2 and A3.

[0506] In some embodiments, if the first target address is the target address associated with the multicast service of the first terminal 101, illustratively, the target address associated with the multicast service that the first terminal 101 is interested in sending and / or receiving. Then, the carrier supported by the first target address is determined according to the high-level configuration. The carrier supported by the first target address is, that is, the carrier that the first terminal 101 can use to send and / or receive the multicast service or multicast sidelink data associated with the first target address. The first terminal 101 can send a third indication message to the network device 102. The network device 102 can determine, based on the third indication message, the carrier on which the first terminal 101 can aggregate the multicast service or multicast sidelink data associated with the first target address, and can schedule a sidelink authorization for the first terminal 101 on the carrier used for carrier aggregation.

[0507] Exemplarily, the first terminal 101 determines, based on high-level configuration, that the carriers supported by the first target address are a1, a2, a3, and a4, that is, the carriers that the first terminal 101 can use to send and / or receive the multicast service or multicast sidelink data associated with the first target address are a1, a2, a3, and a4. The network device 102 can determine that the carriers that can be aggregated for the first terminal 101 to send the multicast service or multicast sidelink data associated with the first target address are a1, a2, a3, and a4, and can schedule sidelink authorization for the first terminal 101 on carriers a1, a2, a3, and a4.

[0508] In some embodiments, if the first target address is a target address associated with a broadcast service of the first terminal 101, illustratively, the target address associated with a broadcast service that the first terminal 101 is interested in sending and / or receiving. Then, the carrier supported by the first target address is determined according to the high-level configuration. The carrier supported by the first target address is, that is, the carrier that the first terminal 101 can use to send and / or receive the broadcast service or broadcast sidelink data associated with the first target address. The first terminal 101 can send a third indication message to the network device 102. The network device 102 can determine, based on the third indication message, the carrier on which the first terminal 101 can aggregate the broadcast service or broadcast sidelink data associated with the first target address, and can schedule a sidelink authorization for the first terminal 101 on the carrier used for carrier aggregation.

[0509] Exemplarily, the first terminal 101 determines, based on high-level configuration, that the carriers supported by the first target address are b1, b2, b3, and b4, that is, the carriers that the first terminal 101 can use to send and / or receive the broadcast service or broadcast sidelink data associated with the first target address are b1, b2, b3, and b4. The network device 102 can determine that the carriers that can be aggregated for the first terminal 101 to send the broadcast service or broadcast sidelink data associated with the first target address are b1, b2, b3, and b4, and can schedule sidelink authorization for the first terminal 101 on carriers b1, b2, b3, and b4.

[0510] In some embodiments, the network device 102 may send scheduling information to the first terminal 101 .

[0511] In some embodiments, the scheduling information may be used to instruct the network device 102 to schedule a sidelink grant for the first terminal 101 on a carrier used for carrier aggregation.

[0512] In some embodiments, the first terminal 101 may receive scheduling information sent by the network device 102 .

[0513] In some embodiments, after receiving the scheduling information sent by the network device 102 , the first terminal 101 may send sidelink data according to the sidelink authorization scheduled by the network device 102 .

[0514] In this embodiment or example, all optional modes or optional examples may be arbitrarily combined unless there is any contradiction.

[0515] FIG5 is an interactive diagram of a carrier aggregation method according to an embodiment of the present disclosure. As shown in FIG5 , the embodiment of the present disclosure relates to a carrier aggregation method for a second terminal 103, the method comprising:

[0516] Step S5101: Send indication information to the first terminal, where the indication information includes first indication information and / or second indication information.

[0517] In some embodiments, the first terminal 101 may be a sending terminal, and accordingly, there is a second terminal 103 that performs unicast communication with the first terminal 101 as a receiving terminal.

[0518] In some embodiments, the first terminal 101 may be a receiving terminal, and accordingly, there is a second terminal 103 that performs unicast communication with the first terminal 101 as a sending terminal.

[0519] In some embodiments, the resource allocation method of the first terminal 101 may be a method in which the network schedules and sends resources.

[0520] In some embodiments, the first terminal 101 may be a terminal performing sidelink unicast communication.

[0521] In some embodiments, the indication information may include one or more of the first indication information and the second indication information. The first terminal 101 may send indication information to the network device 102 to indicate relevant information of supported carriers to the network device 102.

[0522] In some embodiments, the first indication information may be used to indicate a carrier supported by the second terminal 103 , and the second indication information may be used to indicate a carrier preferred to be supported by the second terminal 103 .

[0523] In some embodiments, there may be one or more terminals that establish a unicast connection with the first terminal 101, and the second terminal 103 is one of them. In other words, the second terminal 103 is any terminal that establishes a unicast connection with the first terminal 101.

[0524] In some embodiments, the expressions: "carrier", "frequency band", "spectrum", and "frequency" can be used interchangeably.

[0525] In some embodiments, the carrier supported by the second terminal 103 may include a carrier supported by the second terminal 103 for sending and / or receiving. Exemplarily, the carrier supported by the second terminal 103 for sending may refer to a carrier that the second terminal 103 can use to send sidelink data, and the carrier supported by the second terminal 103 for receiving may refer to a carrier that the second terminal 103 can use to receive sidelink data.

[0526] In some embodiments, the carrier that the second terminal 103 preferably supports may include a carrier that the second terminal 103 preferably supports for sending and / or receiving. Exemplarily, the carrier that the second terminal 103 preferably supports may be a carrier that the second terminal 103 recommends for use among the supported carriers. Exemplarily, the carrier that the second terminal 103 preferably supports may be some of the preferred carriers selected by the second terminal 103 on the supported carriers. Exemplarily, the carrier that the second terminal 103 preferably supports for sending may refer to a carrier that the second terminal 103 may preferably use for sending sidelink data, and the carrier that the second terminal 103 preferably supports for receiving may refer to a carrier that the second terminal 103 may preferably use for receiving sidelink data. Here, preferred may refer to a carrier that the second terminal 103 expects to use for sending or receiving information. That is, the second terminal 103 may inform the network device 102 through the first terminal 101 of the carrier that the second terminal 103 expects to use, so that the network device 102 may prioritize scheduling the carrier when possible. The second terminal 103 can recommend its desired single carrier to the first terminal 101, or can recommend one or more of its desired multiple carriers to the first terminal 101, so that the first terminal 101 reports it to the network device 102, thereby enabling the network device 102 to perform targeted scheduling.

[0527] Exemplarily, the first indication information may include a carrier identification list, which may include carrier information of carriers supported for transmission and / or carrier information of carriers supported for reception by the second terminal 103. Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission by the second terminal 103; Exemplarily, the one carrier identification list may include carrier information of carriers supported for reception by the second terminal 103; Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission and carriers supported for reception by the second terminal 103; Exemplarily, the second indication information may include two carrier identification lists, one list including carrier information of carriers supported for transmission by the second terminal 103, and the other list including carrier information of carriers supported for reception by the second terminal 103.

[0528] Exemplarily, the second indication information may include a carrier identification list, which may include carrier information of carriers that the second terminal 103 preferably supports for sending and / or carrier information of carriers that the second terminal 103 preferably supports for receiving. Exemplarily, the one carrier identification list may include carrier information of carriers that the second terminal 103 preferably supports for sending; Exemplarily, the one carrier identification list may include carrier information of carriers that the second terminal 103 preferably supports for receiving; Exemplarily, the one carrier identification list may include carrier information of carriers that the second terminal 103 preferably supports for sending and carriers that the second terminal 103 preferably supports for receiving; Exemplarily, the third indication information may include two carrier identification lists, one list including carrier information of carriers that the second terminal 103 preferably supports for sending, and the other list including carrier information of carriers that the second terminal 103 preferably supports for receiving.

[0529] In some embodiments, expressions in the present disclosure such as “carrier identification list”, “carrier list”, “carrier set”, etc. may be interchangeable.

[0530] In some embodiments, the first indication information may also include one or more of the second target address and service type of the second terminal 103, so that the network device 102 can know the target address and / or service type of the second terminal 103 and make targeted scheduling.

[0531] In some embodiments, the second indication information may also include one or more of the second target address and service type of the second terminal 103, so that the network device 102 can know the target address and / or service type of the second terminal 103 and make targeted scheduling.

[0532] In some embodiments, the expressions: second target address and second target layer 2 address may be interchangeable.

[0533] In some embodiments, the second terminal 103 may send indication information to the first terminal 101 via PC5-RRC signaling, where the indication information may include first indication information and / or second indication information. Exemplarily, the PC5-RRC signaling may be UECapabilityInformationSidelink signaling, UEAssistanceInformationSidelink, or newly defined PC5-RRC signaling, which is not specifically limited in this disclosure. Exemplarily, the second terminal 103 may send the first indication information and / or the second indication information to the first terminal 101 via other PC5 signaling, such as PC5 MAC CE. This disclosure does not specifically limit this.

[0534] In some embodiments, the second terminal 103 may actively send indication information to the first terminal 101, where the indication information may include first indication information and / or second indication information.

[0535] Exemplarily, if the second terminal 103 is motivated to send the first indication information and / or the second indication information, it can send the first indication information and / or the second indication information to the first terminal 101. Exemplarily, after establishing a unicast connection with the first terminal 101, the second terminal 103 can send the first indication information and / or the second indication information to the first terminal 101 (the second indication information and / or the third indication information is sent for the first time after the unicast connection is established).

[0536] Exemplarily, when the first indication information changes compared to the previous first indication information (for example, the carrier supported by the second terminal 103 changes compared to the previously supported carrier), the first indication information is sent to the first terminal 101. Exemplarily, the previous first indication information may refer to the first indication information last sent to the first terminal 101. Thus, when the carrier supported by the second terminal 103 changes, the second terminal 103 can promptly notify the first terminal 101 of the currently supported carrier.

[0537] Exemplarily, when the second indication information changes compared to the previous second indication information (for example, the carrier preferentially supported by the second terminal 103 changes compared to the previously preferred carrier preferentially supported), the second indication information is sent to the first terminal 101. Exemplarily, the previous second indication information may refer to the second indication information last sent to the first terminal 101. Thus, when the carrier supported by the second terminal 103 changes, the second terminal 103 can promptly notify the first terminal 101 of the currently supported carrier.

[0538] In some embodiments, the first terminal 101 may send a request message to the second terminal 103 to request to obtain indication information, wherein the indication information may include first indication information and / or second indication information. After receiving the request message, the second terminal 103 sends the first indication information and / or second indication information to the first terminal 101.

[0539] For example, the first terminal 101 may send the request information to the second terminal 103 via PC5-RRC signaling. For example, the PC5-RRC signaling may be UECapabilityEnquirySidelink signaling or newly defined PC5-RRC signaling, which is not limited in this disclosure. For example, the first terminal 101 may send the request information to the second terminal 103 via other PC5 signaling, such as PC5 MAC CE. This disclosure does not specifically limit this.

[0540] In some embodiments, the request information may include carrier information of the carrier supported by the first terminal 101, and the second terminal 103 may determine the first indication information and / or the second indication information based on the carrier supported by the first terminal 101 and the carrier supported by the second terminal 103.

[0541] Exemplarily, the request information may include carrier information of carriers supported by the first terminal 101. Exemplarily, the carriers supported by the first terminal 101 include carriers supported by the first terminal 101 for receiving and / or sending. Exemplarily, the carriers supported by the first terminal 101 for sending may refer to carriers that the first terminal 101 may use to send sidelink data, and exemplary, the carriers supported by the first terminal 101 for receiving may refer to carriers that the first terminal 101 may use to receive sidelink data.

[0542] Exemplarily, the request information may include carrier information of the carrier that the first terminal 101 preferably supports. Exemplarily, the carrier that the first terminal 101 preferably supports may include the carrier that the first terminal 101 prefers to support sending and / or receiving. Exemplarily, the carrier that the first terminal 101 prefers to support may be some of the preferred carriers selected by the first terminal 101 on the supported carriers. Exemplarily, the carrier that the first terminal 101 prefers to support sending may refer to the carrier that the first terminal 101 prefers to use for sending sidelink data. Exemplarily, the carrier that the first terminal 101 prefers to support receiving may refer to the carrier that the first terminal 101 prefers to use for receiving sidelink data.

[0543] Exemplarily, the second terminal 103 may determine the first indication information and / or the second indication information based on one or more of the carriers supported by the first terminal 101, the carriers preferred by the first terminal 101, and the carriers supported and received by the second terminal 103.

[0544] Exemplarily, the request information may include a carrier identification list, which may include carrier information of carriers supported for transmission and / or carrier information of carriers supported for reception by the first terminal 101. Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission by the first terminal 101; Exemplarily, the one carrier identification list may include carrier information of carriers supported for reception by the first terminal 101; Exemplarily, the one carrier identification list may include carrier information of carriers supported for transmission and carriers supported for reception by the first terminal 101; Exemplarily, the request information may include two carrier identification lists, one list including carrier information of carriers supported for transmission by the first terminal 101, and the other list including carrier information of carriers supported for reception by the first terminal 101.

[0545] Optionally, the first terminal 101 may send a request message to the second terminal 103 when the resource allocation mode changes. Exemplarily, when the resource allocation mode of the first terminal 101 is configured or reconfigured from mode 1 to mode 2, the request message is sent to the second terminal 103. Exemplarily, when the resource allocation mode of the first terminal 101 is configured or reconfigured from mode 2 to mode 1, the request message is sent to the second terminal 103.

[0546] Optionally, the first terminal 101 may send the request information to the second terminal 103 after establishing a unicast connection with the second terminal 103. Exemplarily, the first terminal 101 may send the request information to the second terminal 103 after establishing a unicast connection with the second terminal 103 based on implementation.

[0547] In some embodiments, the first terminal 101 may receive indication information sent by the second terminal 103 , where the indication information may include first indication information and / or second indication information.

[0548] In this embodiment or example, all optional modes or optional examples may be arbitrarily combined unless there is any contradiction.

[0549] Figure 6 is an interactive diagram of a carrier aggregation method according to an embodiment of the present disclosure. As shown in Figure 6, the embodiment of the present disclosure relates to a carrier aggregation method, which is used in a communication system 100, wherein the communication system 100 includes a first terminal 101 and a network device 102. The method includes:

[0550] Step S6101: The first terminal 101 sends indication information to the network device 102.

[0551] The optional implementation of step S6101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0552] In this embodiment or example, all optional modes or optional examples may be arbitrarily combined unless there is any contradiction.

[0553] The following is an exemplary introduction to the above method.

[0554] Optional embodiment: The terminal device reports the carrier / frequency band supported by the opposite terminal device to the network device

[0555] Optionally, the terminal device reports the receiving capability of the opposite terminal device with a unicast connection on the carrier / frequency band to the network device. Exemplarily, the terminal device may request the opposite terminal device to notify the terminal device of the receiving capability of the opposite terminal device on the carrier / frequency band. For example, the opposite terminal device may be requested to send the information through PC5-RRC signaling. Exemplarily, the PC5-RRC signaling may be UECapabilityEnquirySidelink signaling or a newly defined PC5-RRC signaling. Exemplarily, the opposite terminal device may actively send the information, which is not specifically limited in the present disclosure. Exemplarily, the opposite terminal device notifies the sending terminal of the carrier / frequency band supported by the opposite terminal device through PC5-RRC signaling. Exemplarily, the PC5-RRC signaling may be UECapabilityInformationSidelink signaling or UEAssistanceInformationSidelink or a newly defined PC5-RRC signaling. Exemplarily, after obtaining the information, the terminal device reports it to the network device.

[0556] Optionally, the opposite terminal device may notify the terminal device of the preferred carrier / frequency band. Exemplarily, the opposite terminal device may select some preferred carriers / frequency bands on the carriers / frequency bands supported for reception and notify the terminal device. Exemplarily, the opposite terminal device notifies the sending terminal of the carrier / frequency band that the opposite terminal device preferably supports for reception through PC5-RRC signaling. Exemplarily, the PC5-RRC signaling may be UECapabilityInformationSidelink signaling or UEAssistanceInformationSidelink or a newly defined PC5-RRC signaling. Exemplarily, after the terminal device obtains the information, it reports it to the network device.

[0557] Optionally, the terminal device operates in mode 1; exemplarily, the terminal device is a transmitting terminal; optionally, the terminal device supports sidelink communication; optionally, the terminal device is performing sidelink unicast communication. The terminal device notifies the network device via Uu RRC signaling. exemplarily, the Uu RRC signaling may be SUI signaling or UAI signaling. exemplarily, in addition to the receiving capability of the opposite terminal device on the carrier / frequency band, the DST ID (destination address) and / or casttype (service type) of the opposite terminal device may be optionally carried. exemplarily, the receiving capability on the carrier / frequency band may be indicated by a carrier / frequency band list, which indicates the carrier / frequency band that supports reception.

[0558] Optionally, the network device schedules the sidelink transmission of the terminal device on the corresponding carrier / frequency band based on the reported information and in combination with other information (not specifically limited).

[0559] Optional embodiment: The terminal device reports the carrier / frequency band supported by the target layer 2 address to the network device.

[0560] Optionally, the target Layer 2 address can be associated with a multicast broadcast service or a unicast service. The terminal device determines the carrier / frequency band supported by the target Layer 2 address associated with the broadcast / multicast / unicast service based on the mapping relationship between the service provided by the higher layer (V2X) layer to the target Layer 2 address and the service to the carrier / frequency band. The terminal device reports this information to the network device.

[0561] Optionally, the terminal device operates in mode 1; exemplarily, the terminal device is a transmitting terminal; optionally, the terminal device supports sidelink communication. The terminal device notifies the network device through Uu RRC signaling. Exemplarily, the Uu RRC signaling can be SUI signaling or UAI signaling. Exemplarily, in addition to the carrier / frequency band supported by the target address for transmission, it can optionally carry DST ID (target address) and / or casttype (service type). Exemplarily, the carrier / frequency band supported for transmission can be indicated by a carrier / frequency band list, which indicates the carrier / frequency band supported for transmission.

[0562] Optionally, the network device schedules the sidelink transmission of the terminal device on the corresponding carrier / frequency band based on the reported information and in combination with other information (not specifically limited).

[0563] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0564] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0565] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0566] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution 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 relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by 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 implementing the hardware circuit configuration 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. In addition, 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), a deep learning processing unit (DPU), etc.

[0567] Figure 7A is a schematic diagram of the structure of the first terminal proposed in an embodiment of the present disclosure. As shown in Figure 7A, the first terminal 7100 may include: at least one of a transceiver module 7101, a processing module 7102, etc. In some embodiments, the above-mentioned transceiver module is used to send indication information to the network device, and the indication information includes at least one of the first indication information, the second indication information, and the third indication information; wherein, the first indication information is used to indicate the carrier supported by the second terminal, the second indication information is used to indicate the carrier preferred by the second terminal, and the third indication information is used to indicate the carrier supported by the first target address, and the second terminal is a terminal that establishes a unicast connection with the first terminal. Optionally, the above-mentioned transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (for example, step S2101, but not limited to this) performed by the first terminal 101 in any of the above methods, which will not be repeated here. Optionally, the above-mentioned processing module is used to execute at least one of the other steps performed by the first terminal 101 in any of the above methods, which will not be repeated here.

[0568] Figure 7B is a schematic diagram of the structure of the network device proposed in an embodiment of the present disclosure. As shown in Figure 7B, the network device 7200 may include: at least one of a transceiver module 7201, a processing module 7202, etc. In some embodiments, the transceiver module is used to receive indication information sent by the first terminal device, and the indication information includes at least one of the first indication information, the second indication information, and the third indication information; wherein the first indication information is used to indicate the carrier supported by the second terminal, the second indication information is used to indicate the carrier preferred by the second terminal, and the third indication information is used to indicate the carrier supported by the first target address, and the second terminal is a terminal that establishes a unicast connection with the first terminal. Optionally, the transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (for example, step S4201, but not limited to this) performed by the network device 102 in any of the above methods, and no further details are given here. Optionally, the processing module is used to execute at least one of the other steps (for example, step S4302, but not limited to this) performed by the network device 102 in any of the above methods, and no further details are given here.

[0569] Figure 7C is a schematic diagram of the structure of the second terminal proposed in an embodiment of the present disclosure. As shown in Figure 7C, the second terminal 7100 may include: at least one of a transceiver module 7301, a processing module 7302, etc. In some embodiments, the above-mentioned transceiver module is used to send indication information to the first terminal device, and the indication information includes first indication information and / or second indication information, wherein the first indication information is used to indicate the carrier supported by the second terminal, and the second indication information is used to indicate the carrier preferred by the second terminal. Optionally, the above-mentioned transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (for example, step S2102, but not limited to this) executed by the second terminal 103 in any of the above methods, which will not be repeated here. Optionally, the above-mentioned processing module is used to execute at least one of the other steps (for example, step S5101, but not limited to this) executed by the second terminal 103 in any of the above methods, which will not be repeated here.

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

[0571] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0572] Figure 8A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. Communication device 8100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 8100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0573] As shown in Figure 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 8100 is used to perform any of the above methods.

[0574] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may be located outside the communication device 8100.

[0575] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the transceiver 8103 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2102, but not limited thereto), and the processor 8101 performs at least one of the other steps (for example, step S4302, but not limited thereto).

[0576] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0577] In some embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuit 8104 is connected to the memory 8102. The interface circuit 8104 may be configured to receive signals from the memory 8102 or other devices, and may be configured to send signals to the memory 8102 or other devices. For example, the interface circuit 8104 may read instructions stored in the memory 8102 and send the instructions to the processor 8101.

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

[0579] FIG8B is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 8200 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG8B , but the present disclosure is not limited thereto.

[0580] The chip 8200 includes one or more processors 8201 , and the chip 8200 is configured to execute any of the above methods.

[0581] In some embodiments, the chip 8200 further includes one or more interface circuits 8202. Optionally, the interface circuit 8202 is connected to the memory 8203. The interface circuit 8202 can be used to receive signals from the memory 8203 or other devices, and can be used to send signals to the memory 8203 or other devices. For example, the interface circuit 8202 can read instructions stored in the memory 8203 and send the instructions to the processor 8201.

[0582] In some embodiments, the interface circuit 8202 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S4301, but not limited to this), and the processor 8201 performs at least one of the other steps (for example, step S4302, but not limited to this).

[0583] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0584] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0585] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 800, the communication device 8100 executes 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 is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0586] The present disclosure also provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0587] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A carrier aggregation method, characterized in that: The method is performed by a first terminal and includes: Sending indication information to the network device, where the indication information includes at least one of first indication information, second indication information, and third indication information; The first indication information is used to indicate the carrier supported by the second terminal, the second indication information is used to indicate the carrier preferentially supported by the second terminal, the third indication information is used to indicate the carrier supported by the first target address, and the second terminal is a terminal that establishes a unicast connection with the first terminal.

2. The method according to claim 1, characterized in that Also includes: Receive scheduling information sent by the network device according to the indication information, wherein the scheduling information is used to indicate a sidelink authorization scheduled for the first terminal.

3. The method according to any one of claims 1 to 2, characterized in that: Also includes: The indication information sent by the second terminal is received, where the indication information includes the first indication information and / or the second indication information.

4. The method according to claim 3, characterized in that Also includes: Sending a request message to the second terminal, wherein the request message is used to request obtaining the indication information, and the indication information includes the first indication information and / or the second indication information.

5. The method according to claim 4, characterized in that The sending the request information to the second terminal includes: The resource allocation mode of the first terminal changes, and the request information is sent to the second terminal.

6. The method according to any one of claims 1 to 5, characterized in that Also includes: The carrier supported by the first target address is determined according to a mapping relationship between the service type and the first target address and / or a mapping relationship between the service type and the carrier.

7. The method according to any one of claims 1 to 6, characterized in that The first target address includes at least one of the following: a target address associated with the unicast service of the first terminal; a target address associated with the multicast service of the first terminal; The target address associated with the broadcast service of the first terminal.

8. The method according to any one of claims 1 to 7, characterized in that The indication information includes the first indication information, and the first indication information further includes at least one of the following: a second destination address of the second terminal; Business type.

9. The method according to any one of claims 1 to 8, characterized in that The indication information includes the second indication information, and the second indication information further includes at least one of the following: a second destination address of the second terminal; Business type.

10. The method according to any one of claims 1 to 9, characterized in that The indication information includes the third indication information, and the third indication information further includes at least one of the following: the first target address; The service type associated with the first target address.

11. The method according to any one of claims 1 to 10, characterized in that The supported carriers include carriers that support transmission and / or reception.

12. The method according to any one of claims 1 to 11, characterized in that The first terminal is a sending terminal.

13. The method according to any one of claims 1 to 12, characterized in that The resource allocation method of the first terminal is a method in which the network schedules sending resources.

14. A carrier aggregation method, characterized in that: Executed by a network device, the method includes: Receiving indication information sent by the first terminal device, where the indication information includes at least one of first indication information, second indication information, and third indication information; The first indication information is used to indicate the carrier supported by the second terminal, the second indication information is used to indicate the carrier preferentially supported by the second terminal, the third indication information is used to indicate the carrier supported by the first target address, and the second terminal is a terminal that establishes a unicast connection with the first terminal.

15. The method according to claim 14, characterized in that Also includes: Determine, according to the indication information, a carrier for carrier aggregation; Scheduling information is sent to the first terminal, wherein the scheduling information is used to indicate a sidelink grant scheduled for the first terminal on the carrier used for carrier aggregation.

16. The method according to any one of claims 14 to 15, characterized in that The first target address includes at least one of the following: a target address associated with the unicast service of the first terminal; a target address associated with the multicast service of the first terminal; The target address associated with the broadcast service of the first terminal.

17. The method according to any one of claims 14 to 16, characterized in that The indication information includes the first indication information, and the first indication information further includes at least one of the following: a second destination address of the second terminal; Business type.

18. The method according to any one of claims 14 to 17, characterized in that The indication information includes the second indication information, and the second indication information further includes at least one of the following: a second destination address of the second terminal; Business type.

19. The method according to any one of claims 14 to 18, characterized in that The indication information includes the third indication information, and the third indication information further includes at least one of the following: the first target address; The service type associated with the first target address.

20. The method according to any one of claims 14 to 19, characterized in that The supported carriers include carriers that support transmission and / or reception.

21. A carrier aggregation method, characterized in that: The method is performed by the second terminal, and includes: Send indication information to the first terminal device, the indication information including first indication information and / or second indication information, wherein the first indication information is used to indicate the carrier supported by the second terminal, and the second indication information is used to indicate the carrier preferred to be supported by the second terminal.

22. The method according to claim 21, characterized in that Also includes: Receive request information sent by the first terminal, wherein the request information is used to request to obtain the indication information.

23. The method according to any one of claims 21 to 22, characterized in that The indication information includes the first indication information, and the first indication information further includes at least one of the following: a second destination address of the second terminal; Business type.

24. The method according to any one of claims 21 to 23, characterized in that The indication information includes the second indication information, and the second indication information further includes at least one of the following: a second destination address of the second terminal; Business type.

25. The method according to any one of claims 21 to 24, characterized in that The supported carriers include carriers that support transmission and / or reception.

26. A carrier aggregation method, characterized in that: include: The first terminal device sends indication information to the network device, where the indication information includes at least one of the first indication information, the second indication information, and the third indication information; The network device receives the indication information; The first indication information is used to indicate the carrier supported by the second terminal, the second indication information is used to indicate the carrier preferentially supported by the second terminal, the third indication information is used to indicate the carrier supported by the first target address, and the second terminal is a terminal that establishes a unicast connection with the first terminal.

27. A carrier aggregation device, characterized in that: Applied to a first terminal, the device includes: A transceiver module, used to send indication information to the network device, where the indication information includes at least one of first indication information, second indication information, and third indication information; The first indication information is used to indicate the carrier supported by the second terminal, the second indication information is used to indicate the carrier preferentially supported by the second terminal, the third indication information is used to indicate the carrier supported by the first target address, and the second terminal is a terminal that establishes a unicast connection with the first terminal.

28. A carrier aggregation device, characterized in that: Applied to network equipment, the device comprises: A transceiver module, configured to receive indication information sent by a first terminal device, wherein the indication information includes at least one of first indication information, second indication information, and third indication information; The first indication information is used to indicate the carrier supported by the second terminal, the second indication information is used to indicate the carrier preferentially supported by the second terminal, the third indication information is used to indicate the carrier supported by the first target address, and the second terminal is a terminal that establishes a unicast connection with the first terminal.

29. A carrier aggregation device, characterized in that: Applied to a second terminal, the device includes: A transceiver module is used to send indication information to a first terminal device, wherein the indication information includes first indication information and / or second indication information, wherein the first indication information is used to indicate a carrier supported by the second terminal, and the second indication information is used to indicate a carrier preferred to be supported by the second terminal.

30. A first terminal, characterized in that: include: one or more processors; The first terminal is used to execute the carrier aggregation method according to any one of claims 1-13.

31. A network device, characterized in that: include: one or more processors; The network device is used to execute the carrier aggregation method described in any one of claims 14-20.

32. A second terminal, characterized in that: include: one or more processors; The second terminal is used to execute the carrier aggregation method described in any one of claims 21-25.

33. A communication system, characterized in that: It includes a first terminal, a network device, and a second terminal, wherein the first terminal is configured to implement the carrier aggregation method described in any one of claims 1-13, the network device is configured to implement the carrier aggregation method described in any one of claims 14-20, and the second terminal is configured to implement the carrier aggregation method described in any one of claims 21-25.

34. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to perform the carrier aggregation method according to any one of claims 1-13, claims 14-20, or claims 21-25.