Carrier configuration method and device, and terminal equipment

Abstract

Provided in an embodiment of the present application are a carrier configuration method and apparatus, and a terminal device, the method comprising: a first terminal device sending first information to a second terminal device, the first information being used for the second terminal device or a second network where the second terminal device is located to configure a carrier; and the first terminal device receives first configuration information sent by the second terminal device, the first configuration information being used for configuring a plurality of carriers, and at least part of the plurality of carriers being used for unicast sidelink communication between the first terminal device and the second terminal device.

Description

Carrier configuration method and device, and terminal equipment Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a carrier configuration method and apparatus, and terminal equipment. Background Art

[0002] Sidelink (SL) communications support not only broadcast, but also unicast and multicast. Unicast sidelink communications (hereinafter referred to as unicast sidelink communications) have only one receiving terminal device. To expand bandwidth, carrier aggregation technology is being considered for sidelink communications. However, support for carrier aggregation in unicast sidelink communications requires further development.

[0003] Summary of the Invention

[0004] Embodiments of the present application provide a carrier configuration method and apparatus, terminal equipment, a chip, a computer-readable storage medium, a computer program product, and a computer program.

[0005] The carrier configuration method provided in the embodiment of the present application includes:

[0006] The first terminal device sends first information to the second terminal device, where the first information is used to configure a carrier for the second terminal device or a second network where the second terminal device is located;

[0007] The first terminal device receives first configuration information sent by the second terminal device, where the first configuration information is used to configure multiple carriers, and at least some of the multiple carriers are used for unicast sidelink communication between the first terminal device and the second terminal device.

[0008] The carrier configuration method provided in the embodiment of the present application includes:

[0009] The second terminal device receives first information sent by the first terminal device, where the first information is used to configure a carrier for the second terminal device or a second network where the second terminal device is located;

[0010] The second terminal device sends first configuration information to the first terminal device, where the first configuration information is used to configure multiple carriers, at least some of which are used for unicast sidelink communication between the first terminal device and the second terminal device.

[0011] The carrier configuration apparatus provided in an embodiment of the present application is applied to a first terminal device, and the method includes:

[0012] A sending unit, configured to send first information to a second terminal device, where the first information is used to configure a carrier for the second terminal device or a second network where the second terminal device is located;

[0013] A receiving unit is used to receive first configuration information sent by the second terminal device, where the first configuration information is used to configure multiple carriers, and at least some of the multiple carriers are used for unicast sidelink communication between the first terminal device and the second terminal device.

[0014] The carrier configuration device provided in an embodiment of the present application is applied to a second terminal device, and the method includes:

[0015] A receiving unit, configured to receive first information sent by a first terminal device, where the first information is used to configure a carrier for the second terminal device or a second network where the second terminal device is located;

[0016] A sending unit is used to send first configuration information to the first terminal device, where the first configuration information is used to configure multiple carriers, and at least some of the multiple carriers are used for unicast sidelink communication between the first terminal device and the second terminal device.

[0017] The terminal device provided in an embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the above-mentioned carrier configuration method.

[0018] The chip provided in the embodiment of the present application is used to implement the above-mentioned carrier configuration method.

[0019] Specifically, the chip includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned carrier configuration method.

[0020] The computer-readable storage medium provided in an embodiment of the present application is used to store a computer program, which enables a computer to execute the above-mentioned carrier configuration method.

[0021] The computer program product provided in an embodiment of the present application includes computer program instructions, which enable a computer to execute the above-mentioned carrier configuration method.

[0022] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned carrier configuration method.

[0023] Through the above technical solution, the first terminal device provides the first information to the second terminal device to assist the second terminal device or the second network where the second terminal device is located in configuring multiple carriers for unicast sidelink communication between the first terminal device and the second terminal device, thereby supporting carrier aggregation in unicast sidelink communication. Because this carrier configuration method incorporates the first information provided by the first terminal device as an aid, the configured carriers have higher reliability and improve the performance of unicast sidelink communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0025] Figure 1-1 is a schematic diagram of a terminal device in mode 1;

[0026] Figure 1-2 is a schematic diagram of the terminal device in mode 2;

[0027] FIG2 is a flow chart of a carrier configuration method according to an embodiment of the present application;

[0028] FIG3 is a second flow chart of a carrier configuration method according to an embodiment of the present application;

[0029] FIG4 is a third flow chart of a carrier configuration method according to an embodiment of the present application;

[0030] FIG5 is a schematic diagram of the first structure of a carrier configuration device provided in an embodiment of the present application;

[0031] FIG6 is a second schematic diagram of the structure of the carrier configuration device provided in an embodiment of the present application;

[0032] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0033] FIG8 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0034] FIG9 is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0035] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0036] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0037] Device to Device (D2D) communication

[0038] D2D communication technology was introduced in the Long Term Evolution (LTE) system. D2D communication is based on sidelink transmission technology. Unlike traditional cellular systems, where communication data is received or sent via base stations, the connected vehicle system uses D2D communication (i.e., direct device-to-device communication), resulting in higher spectrum efficiency and lower transmission latency. The Third Generation Partnership Project (3GPP) defines two transmission modes for D2D communication: Mode 1 and Mode 2. Mode 1 and Mode 2 are described below.

[0039] Mode 1: As shown in Figure 1-1, the base station allocates transmission resources to the terminal device, and the terminal device sends data on the sidelink based on the resources allocated by the base station. The base station can allocate resources for single transmission or semi-static transmission to the terminal device.

[0040] Mode 2: As shown in Figure 1-2, the terminal device selects a resource from the resource pool to send data. Specifically, the terminal device can select a transmission resource from the resource pool by listening or by random selection.

[0041] In 3GPP, D2D communication is divided into the following different stages for research:

[0042] Proximity-based services (ProSe): Device-to-device communication is studied in ProSe scenarios, primarily for public safety services. In ProSe, by configuring resource pools in the time domain (e.g., discontinuous resource pools), discontinuous transmission / reception on the sidelink is achieved by the terminal device, thereby saving power.

[0043] Vehicle-to-Everything (V2X) communication is a field of research focused on vehicle-to-everything communication scenarios, primarily targeting high-speed vehicle-to-vehicle and vehicle-to-pedestrian communications. In V2X, power efficiency is less of a concern due to the continuous power supply provided by the vehicle's onboard systems, while data transmission latency is the primary concern. Therefore, system design requires continuous transmission and reception by terminal devices.

[0044] Further Enhanced Device to Device (FeD2D): Device-to-device communication is being studied for scenarios where wearable devices access the network via mobile phones, primarily targeting low-speed and low-power access scenarios. In FeD2D, during its preliminary research phase, 3GPP concluded that base stations can configure DRX parameters for remote devices through a relay terminal.

[0045] With the evolution of mobile communication systems, LTE V2X has also evolved into New Radio (NR) V2X. NR V2X needs to support autonomous driving, placing higher demands on data exchange between vehicles, such as higher throughput, lower latency, higher reliability, wider coverage, and more flexible resource allocation. Building on LTE V2X, NR V2X is not limited to broadcast scenarios, but further expands to unicast and multicast scenarios, investigating V2X applications in these scenarios. Unicast transmission has a single receiving end, while multicast transmission targets all devices in a communication group or all devices within a certain transmission distance. Broadcast transmission targets any device. NR V2X systems introduce multiple transmission modes, including Mode 1 and Mode 2. Mode 1 involves the network allocating transmission resources to a device, while Mode 2 allows the device to select transmission resources. Furthermore, a device may operate in a mixed mode, specifically using both Mode 1 and Mode 2 to acquire resources. In addition, in the NR V2X system, a side feedback mechanism is introduced, that is, the feedback-based Hybrid Automatic Repeat reQuest (HARQ) retransmission. The side feedback mechanism is not limited to unicast scenarios, but can also be applied to multicast scenarios.

[0046] Carrier Aggregation (CA)

[0047] CA is a bandwidth extension technology that aggregates multiple component carriers (CCs) together and is simultaneously received or transmitted by a terminal device or network device. According to the range of the aggregated carriers, CA can be divided into intra-band CA (Intra-band CA) and inter-band CA (Inter-band CA). One of the main uses of intra-band CA is for scenarios where the cell carrier bandwidth is greater than the single carrier bandwidth capability of the terminal device. In this case, the terminal device can use CA to operate in a "wide carrier". For example, the base station supports a 300MHz carrier, and the terminal device supports a maximum of 100MHz carrier. The terminal device can use CA to achieve broadband operation greater than 100MHz. The aggregated carriers can be adjacent carriers or non-adjacent carriers.

[0048] When a terminal device and a network device use CA for communication, a primary cell (PCell) and a secondary cell (SCell) may be configured at the same time. A beam failure recovery mechanism is designed for the primary cell and the secondary primary cell. Its main functional modules (or main steps) include: Beam Failure Detection (BFD); New Beam Identification (NBI); Beam Failure Recovery Request (BFRQ); and network-side response. Specifically, the terminal device measures the downlink transmit beam to determine the link quality corresponding to the downlink transmit beam. If the corresponding link quality is very poor, it is considered that the downlink beam has a beam failure. The terminal device also measures a set of alternative beams and selects a beam that meets a certain threshold as a new beam. The terminal device then notifies the network of the beam failure through the beam failure recovery request process and reports the new beam. After receiving the beam failure recovery request from the terminal device, the network recognizes that a beam failure has occurred and selects a new beam to transmit the Physical Downlink Control Channel (PDCCH). Upon receiving the PDCCH sent by the network on the new beam, the terminal device assumes it has correctly received the network's response. The beam failure recovery process is now successfully completed.

[0049] Carrier aggregation (CA) technology has also been introduced in LTE V2X. Carrier selection in LTE V2X is accomplished by the following mechanism: the upper layer is configured with a mapping relationship between service types and carriers. Thus, for a certain type of service, the upper layer indicates to the access storage (AS) layer the available carriers or carrier sets. Furthermore, the AS layer is configured with the available carriers or carrier sets for each logical channel and the channel busy rate (CBR) threshold for data priority in each resource pool. The terminal device measures the CBR value in the resource pool and compares it with the CBR threshold corresponding to the data priority. If the measured CBR value is lower than the CBR threshold, the carrier corresponding to the resource pool is considered available.

[0050] NR SL also requires the introduction of carrier aggregation technology. Compared with LTE V2X, the introduction of carrier aggregation technology in NR SL requires additional consideration. NR V2X supports unicast communication, and how to support carrier aggregation in unicast sidelink communication needs to be improved. To this end, the following technical solutions are proposed in the embodiments of this application.

[0051] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0052] FIG2 is a flow chart of a carrier configuration method provided in an embodiment of the present application. As shown in FIG2 , the carrier configuration method includes the following steps:

[0053] Step 201: A first terminal device sends first information to a second terminal device.

[0054] Step 202: The second terminal device receives first information sent by the first terminal device, where the first information is used to configure a carrier for the second terminal device or a second network where the second terminal device is located.

[0055] In some embodiments, the first terminal device is a transmitter of unicast sidelink communication, and the second terminal device is a receiver of unicast sidelink communication. In other embodiments, the first terminal device is a receiver of unicast sidelink communication, and the second terminal device is a transmitter of unicast sidelink communication.

[0056] Here, for the sending end of the unicast sidelink communication, the sending end sends data on the unicast sidelink; for the receiving end of the unicast sidelink communication, the receiving end receives data on the unicast sidelink.

[0057] In an embodiment of the present application, the unicast sidelink communication between the first terminal device and the second terminal device supports carrier aggregation, that is, communication is performed on the unicast sidelink through aggregated carriers. In order to achieve carrier aggregation on the unicast sidelink, corresponding carrier configuration is required. Specifically, the first terminal device sends a first message to the second terminal device, and the second terminal device receives the first message sent by the first terminal device. The first information is used to configure a carrier for the second terminal device or the second network where the second terminal device is located.

[0058] In some embodiments, the first information includes a carrier or a carrier set recommended for configuration by the first terminal device and / or a carrier or a carrier set supported by the capability of the first terminal device. Here, the information corresponding to the carrier or the carrier set recommended for configuration by the first terminal device may also be referred to as carrier configuration assistance information, which is not limited in this application. The information corresponding to the carrier or the carrier set supported by the capability of the first terminal device may also be referred to as carrier-related capability information, which is not limited in this application.

[0059] In some implementations, the carrier or carrier set that the first terminal device recommends configuring is determined based on at least one of the following:

[0060] a carrier or a carrier set supported by the capabilities of the first terminal device;

[0061] The carrier or carrier set used by the first terminal device;

[0062] a carrier or a set of carriers available to the first terminal device;

[0063] a carrier or a set of carriers supported by the capabilities of the second terminal device;

[0064] The carrier or carrier set used by the second terminal device;

[0065] a carrier or a set of carriers available to the second terminal device;

[0066] Communication information of unicast sidelink communication between the first terminal device and the second terminal device;

[0067] link quality of the unicast sidelink between the first terminal device and the second terminal device;

[0068] a network configuration of a first network where the first terminal device is located, the network configuration of the first network being used to configure a carrier or a carrier set supported by one or more coverage areas of the first network;

[0069] The network capability of the first network where the first terminal device is located, where the network capability of the first network is used to determine whether the first network supports carrier aggregation.

[0070] In some embodiments, the carrier or carrier set supported by the capabilities of the first terminal device is determined based on at least one of the following:

[0071] The carrier or carrier set used by the first terminal device;

[0072] a carrier or a set of carriers available to the first terminal device;

[0073] The network capability of the first network where the first terminal device is located, where the network capability of the first network is used to determine whether the first network supports carrier aggregation.

[0074] In the above solution, the carrier or carrier set used by the first terminal device refers to: the carrier or carrier set on other side links and / or uplinks and downlinks other than the unicast side link of the first terminal device.

[0075] In the above solution, the carrier or carrier set available to the first terminal device refers to: the carrier or carrier set supported by the capability of the first terminal device minus the carrier or carrier set used by the first terminal device.

[0076] In the above solution, the carrier or carrier set used by the second terminal device refers to: the carrier or carrier set on other side links and / or uplinks and downlinks other than the unicast side link of the second terminal device.

[0077] In the above solution, the carrier or carrier set available to the second terminal device refers to: the carrier or carrier set supported by the capability of the second terminal device minus the carrier or carrier set used by the second terminal device.

[0078] In the above scheme, the first terminal device may, but is not limited to, obtain the relevant information of the second terminal device (i.e., at least one of the carrier or carrier set supported by the capability of the second terminal device, the carrier or carrier set used by the second terminal device, and the carrier or carrier set available to the second terminal device) in the following manner:

[0079] Method 1-1: The first terminal device sends a request message to the second terminal device, and the request message is used to request the second terminal device to report relevant information of the second terminal device; after receiving the request message, the second terminal device reports the relevant information of the second terminal device to the first terminal device, and the first terminal device receives the relevant information of the second terminal device sent by the second terminal device.

[0080] Mode 1-2: The first terminal device receives relevant information of the second terminal device actively sent by the second terminal device.

[0081] In the above solution, the first terminal device may, but is not limited to, obtain the communication information of the unicast sidelink communication between the first terminal device and the second terminal device in the following manner:

[0082] Mode 2-1: When the first terminal device is a transmitter of unicast sidelink communication, the first terminal device naturally knows the communication information of the unicast sidelink communication between the first terminal device and the second terminal device.

[0083] Mode 2-2: When the first terminal device is a receiving end of unicast sidelink communication, the first terminal device receives communication information of unicast sidelink communication sent by the second terminal device.

[0084] In some embodiments, the communication information of the unicast sidelink communication includes at least one of the following communication-related information: data volume, data type, and logical channel identifier.

[0085] In the above solution, the first terminal device may, but is not limited to, obtain the link quality of the unicast sidelink between the first terminal device and the second terminal device in the following manner:

[0086] Mode 3-1: The first terminal device measures the reference signal sent by the second terminal device, and determines the link quality of the unicast side link between the first terminal device and the second terminal device based on the measurement result of the reference signal.

[0087] Method 3-2: The second terminal device measures the reference signal sent by the first terminal device and reports the measurement result of the reference signal to the first terminal device, so that the first terminal device obtains the link quality of the unicast side link between the first terminal device and the second terminal device.

[0088] In some implementations, the measurement result of the reference signal may be a reference signal received power (RSRP) measurement value, a reference signal received quality (RSRQ) or the like of the reference signal.

[0089] In the above solution, the first terminal device may obtain the network configuration and / or network capability of the first network where the first terminal device is located in the following manner, but is not limited to:

[0090] Method 4-1) The first terminal device receives a system broadcast message sent by the first network, and the system broadcast message carries the network configuration and / or network capabilities of the first network; the first terminal device obtains the network configuration and / or network capabilities of the first network from the system broadcast message.

[0091] Method 4-2) The first terminal device sends a request message to the first network, where the request message is used to request the first network to send the network configuration and / or network capabilities of the first network; the first terminal device receives the network configuration and / or network capabilities of the first network sent by the first network.

[0092] In some embodiments, the network configuration of the first network is used to configure carriers or carrier sets supported by one or more coverage areas of the first network. The network capabilities of the first network are used to determine whether the first network supports carrier aggregation. Here, the network capabilities of the first network can be capability information or network version information. The capability information explicitly indicates whether the first network supports carrier aggregation, and the network version information implicitly indicates whether the first network supports carrier aggregation.

[0093] It should be noted that the prerequisites for the first terminal device to obtain the network configuration and / or network capabilities of the first network include at least one of the following: the first terminal device is within the coverage of the first network; the first terminal device is in mode one; the first terminal device is in a connected state.

[0094] In an embodiment of the present application, the first terminal device sends the first information to the second terminal device when determining that the trigger condition is met.

[0095] In some embodiments, the trigger condition includes at least one of the following:

[0096] A first trigger condition, where the first trigger condition refers to: the first terminal device receiving a request message sent by the second terminal device, where the request message is used to request the first terminal device to send first information to the second terminal device;

[0097] A second trigger condition, where the second trigger condition refers to: the first terminal device receiving first indication information sent by the second terminal device, where the first indication information is used to indicate that the second terminal device and / or the second network where the second terminal device is located supports sidelink carrier aggregation;

[0098] A third trigger condition, wherein the third trigger condition refers to: the first terminal device determines that a periodic time point has arrived;

[0099] The fourth trigger condition refers to: the first terminal device determines that the target event occurs.

[0100] Here, as some implementations, the target event includes at least one of the following:

[0101] The carrier or carrier set recommended for configuration by the first terminal device changes;

[0102] The first terminal device establishes a unicast sidelink with the second terminal device;

[0103] The carrier or carrier set used by the first terminal device changes;

[0104] A carrier or a carrier set available to the first terminal device changes;

[0105] The link quality of the unicast sidelink between the first terminal device and the second terminal device changes;

[0106] A conflict occurs on carrier resources on the unicast sidelink between the first terminal device and the second terminal device.

[0107] In some embodiments, before all or some of the multiple carriers configured by the first configuration information are successfully configured, the first terminal device and the second terminal device communicate using the first carrier or the second carrier, the first carrier being a default carrier or a carrier in a default available carrier set or a carrier determined based on a first mapping rule, and the second carrier being a carrier that has been successfully configured before the first terminal device receives the first configuration information. Here, optionally, the first mapping rule includes a mapping relationship between third information and available carriers and / or available carrier sequences, and the third information includes at least one of the following:

[0108] a layer 2 ID of the first terminal device and / or the second terminal device;

[0109] a transmission profile (Tx profile) corresponding to data transmission between the first terminal device and the second terminal device;

[0110] The service type or application type corresponding to the data transmitted between the first terminal device and the second terminal device;

[0111] The amount of data transmitted between the first terminal device and the second terminal device;

[0112] a transmission type corresponding to data transmitted between the first terminal device and the second terminal device;

[0113] A QoS flow corresponding to data transmitted between the first terminal device and the second terminal device;

[0114] a logical channel corresponding to data transmission between the first terminal device and the second terminal device;

[0115] a resource pool corresponding to data transmitted between the first terminal device and the second terminal device;

[0116] a radio bearer corresponding to data transmission between the first terminal device and the second terminal device;

[0117] a data priority corresponding to data transmitted between the first terminal device and the second terminal device;

[0118] The congestion rate (CBR) of the resource pool corresponding to the data transmitted between the first terminal device and the second terminal device.

[0119] Here, the layer 2 ID is the communication address used by the terminal device for side link communication.

[0120] Here, the transmission type may be a broadcast type, a unicast type, or a multicast type. For the solution of the embodiment of the present application, the transmission type is a unicast type.

[0121] Step 203: The second terminal device sends first configuration information to the first terminal device.

[0122] Step 204: The first terminal device receives first configuration information sent by the second terminal device, where the first configuration information is used to configure multiple carriers, and at least some of the multiple carriers are used for unicast sidelink communication between the first terminal device and the second terminal device.

[0123] In the embodiment of the present application, the first information is used to configure a carrier for the second terminal device or the second network where the second terminal device is located.

[0124] Solution 1-1: The first information is used to configure the carrier for the second terminal device.

[0125] Solution 1-1 can be applicable to, but is not limited to, the following scenarios: the second terminal device is outside the coverage of the second network; the second terminal device is in a non-connected state; the second terminal device is in mode two.

[0126] After the second terminal device receives the first information sent by the first terminal device, it configures the carrier according to the first information to generate the first configuration information; the second terminal device sends the first configuration information to the first terminal device, and the first terminal device receives the first configuration information sent by the second terminal device, and the first configuration information is used to configure multiple carriers.

[0127] Of course, solution 1-1 can also be applied to the following scenarios: the first terminal device is located within the coverage of the first network; the first terminal device is in a connected state; the first terminal device is in mode one.

[0128] Solution 1-2: The first information is used to configure a carrier in the second network where the second terminal device is located.

[0129] Solution 1-2 is applicable to the following scenarios: the second terminal device is located within the coverage of the second network; the second terminal device is in a connected state; the second terminal device is in mode one.

[0130] After the second terminal device receives the first information sent by the first terminal device, the second terminal device forwards the first information to the second network. Here, the first information is forwarded by the second terminal device to the second network, and the second network configures carriers based on the first information to generate first configuration information. The second terminal device receives the first configuration information sent by the second network. The second terminal device sends the first configuration information to the first terminal device, and the first terminal device receives the first configuration information from the second network forwarded by the second terminal device. The first configuration information is used to configure multiple carriers.

[0131] In this embodiment of the present application, after the first terminal device receives the first configuration information sent by the second terminal device, the first terminal device or the first network where the first terminal device is located decides whether to accept or reject all or some of the carriers configured by the first configuration information. This is described below in different situations.

[0132] Solution 2-1: The first terminal device decides to accept or reject all or part of the carriers configured by the first configuration information.

[0133] Solution 2-1 can be but is not limited to being applicable to the following scenarios: the first terminal device is located outside the coverage of the first network; the first terminal device is in a non-connected state; the first terminal device is in mode two.

[0134] After the first terminal device receives the first configuration information sent by the second terminal device, the first terminal device accepts or rejects all or some of the carriers configured by the first configuration information, and sends a configuration result corresponding to the first configuration information to the second terminal device, where the configuration result includes at least one of the following:

[0135] second indication information, where the second indication information is used to indicate acceptance or rejection of all or part of the carriers configured by the first configuration information;

[0136] first carrier information, where the first carrier information is used to indicate the accepted carrier;

[0137] Second carrier information, where the second carrier information is used to indicate a rejected carrier.

[0138] Here, the accepted carrier is also the carrier that is successfully configured. The first carrier information can also be called configuration success information, which is not limited in this application. As an example: the first carrier information includes the carrier identifier of the accepted carrier.

[0139] Here, the rejected carrier is also the carrier for which configuration fails. The second carrier information may also be referred to as configuration failure information, which is not limited in this application. As an example, the second carrier information includes the carrier identifier of the rejected carrier.

[0140] Of course, Solution 2-1 can also be applied to the following scenarios: the first terminal device is within the coverage of the first network; the first terminal device is in a connected state; and the first terminal device is in Mode 1. For this scenario, in some embodiments, the first terminal device sends the configuration result to the first network in which it is located.

[0141] Solution 2-2: The first network where the first terminal device is located decides whether to accept or reject all or part of the carriers configured by the first configuration information.

[0142] Solution 2-2 is applicable to the following scenarios: the first terminal device is located within the coverage of the first network; the first terminal device is in a connected state; the first terminal device is in mode one.

[0143] After the first terminal device receives the first configuration information sent by the second terminal device, the first terminal device sends the first configuration information to the first network where it is located; after the first network receives the first configuration information sent by the first terminal device, the first network accepts or rejects all or part of the carriers configured by the first configuration information, and sends the configuration result corresponding to the first configuration information to the first terminal device, and the first terminal device receives the configuration result corresponding to the first configuration information sent by the first network; further, the first terminal device sends the configuration result corresponding to the first configuration information to the second terminal device. The second terminal device receives the configuration result corresponding to the first configuration information sent by the first terminal device. The configuration result includes at least one of the following:

[0144] second indication information, where the second indication information is used to indicate acceptance or rejection of all or part of the carriers configured by the first configuration information;

[0145] First carrier information, where the first carrier information is used to indicate an accepted carrier;

[0146] Second carrier information, where the second carrier information is used to indicate a rejected carrier.

[0147] Here, the accepted carrier is also the carrier that is successfully configured. The first carrier information can also be called configuration success information, which is not limited in this application. As an example: the first carrier information includes the carrier identifier of the accepted carrier.

[0148] Here, the rejected carrier is also the carrier for which configuration fails. The second carrier information may also be referred to as configuration failure information, which is not limited in this application. As an example, the second carrier information includes the carrier identifier of the rejected carrier.

[0149] In some implementations, if the second indication information is used to indicate rejection of all or part of the carriers configured by the first configuration information, the second terminal device performs at least one of the following operations:

[0150] reconfiguring multiple carriers based on the first information and sending first configuration information to the first terminal device, where the first configuration information is used to reconfigure the multiple carriers;

[0151] Triggering the link failure process for the unicast sidelink;

[0152] Disconnect the unicast sidelink.

[0153] In some embodiments, the second terminal device sends the configuration result to the second network in which it is located, or the second terminal device sends the final carrier configuration to the second network in which it is located based on the configuration result. Here, the prerequisite for the second terminal device to send the configuration result to the second network in which it is located includes at least one of the following: the second terminal device is within the coverage area of ​​the second network; the second terminal device is in a connected state; and the second terminal device is in mode 1.

[0154] In some embodiments, the second indication information is used to indicate that, when all or part of the carriers configured by the first configuration information are accepted, the accepted carriers indicated by the first carrier information are used for unicast sidelink communication between the first terminal device and the second terminal device; or, the second indication information is used to indicate that part of the carriers configured by the first configuration information are rejected, all carriers configured by the first configuration information except the rejected carriers indicated by the second carrier information are used for unicast sidelink communication between the first terminal device and the second terminal device.

[0155] In some embodiments, when the configuration of all or some of the multiple carriers configured by the first configuration information fails, the first terminal device and the second terminal device communicate using the first carrier, the second carrier, or the third carrier, where the first carrier is a default carrier, a carrier in a default available carrier set, or a carrier determined based on a first mapping rule, the second carrier is a carrier that has been successfully configured before the first terminal device receives the first configuration information, and the third carrier is a carrier in some of the carriers that have been successfully configured among the multiple carriers. Here, optionally, here, optionally, the first mapping rule includes a mapping relationship between the third information and the available carriers and / or the available carrier sequence number, and the third information includes at least one of the following:

[0156] a layer 2 ID of the first terminal device and / or the second terminal device;

[0157] a transmission profile (Tx profile) corresponding to data transmission between the first terminal device and the second terminal device;

[0158] The service type or application type corresponding to the data transmitted between the first terminal device and the second terminal device;

[0159] The amount of data transmitted between the first terminal device and the second terminal device;

[0160] a transmission type corresponding to data transmitted between the first terminal device and the second terminal device;

[0161] A QoS flow corresponding to data transmitted between the first terminal device and the second terminal device;

[0162] a logical channel corresponding to data transmission between the first terminal device and the second terminal device;

[0163] a resource pool corresponding to data transmitted between the first terminal device and the second terminal device;

[0164] a radio bearer corresponding to data transmission between the first terminal device and the second terminal device;

[0165] a data priority corresponding to data transmitted between the first terminal device and the second terminal device;

[0166] The CBR of the resource pool corresponding to the data transmitted between the first terminal device and the second terminal device.

[0167] Here, the layer 2 ID is the communication address used by the terminal device for side link communication.

[0168] Here, the transmission type may be a broadcast type, a unicast type, or a multicast type. For the solution of the embodiment of the present application, the transmission type is a unicast type.

[0169] It should be noted that the first carrier, the second carrier, or the third carrier in the above solution may be one carrier or multiple carriers.

[0170] In an embodiment of the present application, the interaction between the first terminal device and the second terminal device is based on the PC5 interface. In some embodiments, the first information sent by the first terminal device to the second terminal device can be carried in RRC signaling based on the PC5 interface (PC5-RRC signaling), or in Sidelink Control Information (SCI), or in Sidelink MAC CE (SL-MAC CE). In some embodiments, the first configuration information sent by the second terminal device to the first terminal device can be carried in PC5-RRC signaling, or in SCI, or in MAC CE.

[0171] The technical solutions of the embodiments of the present application are illustrated below with reference to specific application examples.

[0172] Application Example 1

[0173] In this application example, the first terminal device is the receiver of unicast sidelink communication (denoted as Rx UE), and the second terminal device is the transmitter of unicast sidelink communication (denoted as Tx UE). The network where the first terminal device is located is denoted as Network 2, and the network where the second terminal device is located is denoted as Network 1. The carrier is configured by the Tx UE or Network 1 where the Tx UE is located. The specific process is shown in Figure 3 and includes the following steps:

[0174] Step 300: The Tx UE and the Rx UE communicate with each other using a default carrier or a mapped carrier.

[0175] Here, the default carrier may be defined by a protocol, and both the Tx UE and the Rx UE know the default carrier.

[0176] Here, the mapped carrier can be determined based on the first mapping rule. Here, optionally, the first mapping rule includes a mapping relationship between third information and available carriers and / or available carrier sequences, and the third information includes at least one of the following: layer 2 ID of Tx UE and / or Rx UE; transmission configuration (Tx profile) corresponding to data transmitted between Tx UE and Rx UE; service type or application type corresponding to data transmitted between Tx UE and Rx UE; data volume corresponding to data transmitted between Tx UE and Rx UE; transmission type corresponding to data transmitted between Tx UE and Rx UE; QoS flow corresponding to data transmitted between Tx UE and Rx UE; logical channel corresponding to data transmitted between Tx UE and Rx UE; resource pool corresponding to data transmitted between Tx UE and Rx UE; radio bearer corresponding to data transmitted between Tx UE and Rx UE; data priority corresponding to data transmitted between Tx UE and Rx UE; CBR of resource pool corresponding to data transmitted between Tx UE and Rx UE. The Tx UE obtains the third information and determines the carrier corresponding to the third information (ie, the mapped carrier) based on the first mapping rule. The Rx UE obtains the third information from the Tx UE and determines the carrier corresponding to the third information (ie, the mapped carrier) based on the first mapping rule.

[0177] It should be noted that before a carrier for unicast sidelink communication between the Tx UE and the Rx UE is configured, the Tx UE and the Rx UE will communicate using a default carrier or a carrier in the default available carrier set or a mapped carrier. For example, the Tx UE or the Rx UE uses the default carrier or a carrier in the default available carrier set or a mapped carrier to send or receive discovery messages, direct communication request (DCR) messages, other PC5-S messages, PC5-RRC messages, etc.

[0178] Step 301: The Rx UE sends carrier configuration assistance information and / or carrier-related capability information to the Tx UE.

[0179] Here, the carrier configuration assistance information and / or carrier-related capability information is the first information in the above solution. The carrier configuration assistance information includes the carrier or carrier set recommended for configuration by the Rx UE, and the carrier-related capability information includes the carrier or carrier set supported by the Rx UE.

[0180] The conditions for triggering the Rx UE to send carrier configuration assistance information and / or carrier-related capability information to the Tx UE include at least one of the following:

[0181] A first trigger condition, where the first trigger condition refers to: the Rx UE receiving request information sent by the Tx UE, where the request information is used to request the Rx UE to send carrier configuration assistance information and / or carrier-related capability information to the Tx UE;

[0182] A second trigger condition, where the second trigger condition refers to: the Rx UE receiving first indication information sent by the Tx UE, where the first indication information is used to indicate that the Tx UE and / or the network 1 where the Tx UE is located supports sidelink carrier aggregation;

[0183] A third trigger condition, wherein the third trigger condition refers to: the Rx UE determines that a periodic time point has arrived;

[0184] The fourth trigger condition refers to: the Rx UE determines that the target event occurs.

[0185] Here, the trigger corresponding to the third trigger condition may also be referred to as a periodic trigger.

[0186] Here, the trigger corresponding to the fourth trigger condition may also be referred to as a target event trigger. As some implementations, the target event includes at least one of the following:

[0187] The carrier or carrier set recommended by the Rx UE has changed;

[0188] The Rx UE establishes a unicast sidelink with the Tx UE;

[0189] The carrier or carrier set used by the Rx UE changes;

[0190] The carrier or carrier set available to the Rx UE changes;

[0191] The link quality of the unicast sidelink between the Rx UE and the Tx UE changes;

[0192] A conflict occurs on carrier resources on the unicast sidelink between the Rx UE and the Tx UE.

[0193] It should be noted that for periodic triggering and target event triggering, the Rx UE needs to confirm that the Tx UE has carrier aggregation capability. When the Tx UE has carrier aggregation capability, if the target event occurs, the Rx UE sends carrier configuration assistance information and / or carrier-related capability information to the Tx UE.

[0194] In the above solution, the carrier configuration assistance information (i.e., the carrier or carrier set recommended for configuration by the Rx UE) is determined by the Rx UE based on at least one of the following:

[0195] Rx UE's capabilities support the carrier or carrier set;

[0196] Rx UE used carrier or carrier set;

[0197] Rx carrier or carrier set available to the UE;

[0198] Tx UE's capabilities support the carrier or carrier set;

[0199] Tx UE used carrier or carrier set;

[0200] Tx carrier or carrier set available to UE;

[0201] Communication information of unicast sidelink communication between Rx UE and Tx UE;

[0202] Link quality of the unicast sidelink between the Rx UE and the Tx UE;

[0203] The network configuration of network 2 where the Rx UE is located is used to configure the carrier or carrier set supported by one or more coverage areas of network 2;

[0204] The network capability of network 2 where the Rx UE is located is used to determine whether network 2 supports carrier aggregation.

[0205] In the above solution, the carrier-related capability information (i.e., the carrier or carrier set supported by the Rx UE's capabilities) is determined by the Rx UE based on at least one of the following:

[0206] Rx UE used carrier or carrier set;

[0207] Rx carrier or carrier set available to the UE;

[0208] The network capability of network 2 where the Rx UE is located is used to determine whether network 2 supports carrier aggregation.

[0209] Step 302: The Tx UE reports the carrier configuration assistance information and / or carrier-related capability information obtained from the Rx UE to the network 1.

[0210] Step 303: Network 1 sends carrier configuration information to Tx UE.

[0211] Here, the carrier configuration information is the first configuration information in the above solution, which is used to configure multiple carriers.

[0212] Step 304: The Tx UE sends carrier configuration information to the Rx UE.

[0213] Step 305: The Rx UE accepts or rejects all or part of the carriers configured by the carrier configuration information, and sends the configuration result to the Tx UE.

[0214] Here, an accepted carrier may be understood as a carrier with successful configuration, and a rejected carrier may be understood as a carrier with failed configuration.

[0215] Here, if the Rx UE accepts all carriers configured by the carrier configuration information, it can be understood that all carriers configured by the carrier configuration information are successfully configured (or directly understood as the carrier configuration information is successfully configured). If the Rx UE rejects all carriers configured by the carrier configuration information, it can be understood that all carriers configured by the carrier configuration information fail to be configured (or directly understood as the carrier configuration information fails to be configured).

[0216] Here, the Rx UE accepts some of the carriers configured by the carrier configuration information, which can be understood as the configuration of some of the carriers configured by the carrier configuration information being successful (or directly understood as the partial configuration of the carrier configuration information being successful). The Rx UE rejects some of the carriers configured by the carrier configuration information, which can be understood as the configuration of some of the carriers configured by the carrier configuration information failing (or directly understood as the partial configuration of the carrier configuration information failing).

[0217] Here, the configuration result includes at least one of the following: indication information for indicating acceptance or rejection of all or part of the carriers configured by the carrier configuration information; carrier information (such as carrier identifier) ​​for indicating the accepted carriers; and carrier information (such as carrier identifier) ​​for indicating the rejected carriers.

[0218] Step 306: The Rx UE reports the configuration result to the network 2.

[0219] Here, the configuration result includes at least one of the following: indication information for indicating acceptance or rejection of all or part of the carriers configured by the carrier configuration information; carrier information (such as carrier identifier) ​​for indicating the accepted carriers; and carrier information (such as carrier identifier) ​​for indicating the rejected carriers.

[0220] Step 307: The Tx UE reports the configuration result to the network 1.

[0221] Here, the configuration result includes at least one of the following: indication information for indicating acceptance or rejection of all or part of the carriers configured by the carrier configuration information; carrier information (such as carrier identifier) ​​for indicating the accepted carriers; and carrier information (such as carrier identifier) ​​for indicating the rejected carriers.

[0222] Here, if the indication information in the configuration result indicates that all or part of the carriers configured by the carrier configuration information are rejected (that is, all or part of the carrier configuration information fails), the Tx UE performs at least one of the following operations:

[0223] Reconfigure the carrier (i.e., re-execute steps 302 to 304 above);

[0224] Triggering the link failure process for the unicast sidelink;

[0225] Disconnect the unicast sidelink.

[0226] Step 308: If the carrier configuration information is fully or partially configured successfully, the Tx UE and the Rx UE use the successfully configured carrier to perform unicast sidelink communication.

[0227] It should be noted that, when the Tx UE is outside the coverage of network 1 and / or the Tx UE is in a non-connected state and / or the Tx UE is in mode 2, the above steps 302, 303 and 307 will not be executed. In this case, after step 301, the Tx UE independently determines the carrier configuration information and executes step 304.

[0228] It should be noted that, when the Rx UE is outside the coverage of the network 2 and / or the Rx UE is in a non-connected state and / or the Rx UE is in mode 2, the above step 306 will not be performed.

[0229] It should be noted that, when the Rx UE is within the coverage of network 2 and / or the Rx UE is in a connected state and / or the Rx UE is in mode 1, the above steps 305 and 306 may also be replaced by the following steps:

[0230] Step 305a: The Rx UE reports the carrier configuration information to the network 2.

[0231] Step 305b: Network 2 accepts or rejects all or part of the carriers configured by the carrier configuration information, and sends the configuration result to the Rx UE.

[0232] Step 306a: The Rx UE sends the configuration result to the Tx UE.

[0233] Application Example 2

[0234] In this application example, the first terminal device is the transmitter of unicast sidelink communication (referred to as Tx UE), and the second terminal device is the receiver of unicast sidelink communication (referred to as Rx UE). The network where the first terminal device is located is referred to as Network 1, and the network where the second terminal device is located is referred to as Network 2. The carrier is configured by either the Rx UE or Network 2 where the Rx UE is located. The specific process is shown in Figure 4 and includes the following steps:

[0235] Step 400: The Rx UE and the Tx UE communicate with each other using a default carrier or a mapped carrier.

[0236] Here, the default carrier may be defined by a protocol, and both the Rx UE and the Tx UE know the default carrier.

[0237] Here, the mapped carrier can be determined based on the first mapping rule. Here, optionally, the first mapping rule includes a mapping relationship between third information and available carriers and / or available carrier sequences, and the third information includes at least one of the following: layer 2 ID of Tx UE and / or Rx UE; transmission configuration (Tx profile) corresponding to data transmitted between Tx UE and Rx UE; service type or application type corresponding to data transmitted between Tx UE and Rx UE; data volume corresponding to data transmitted between Tx UE and Rx UE; transmission type corresponding to data transmitted between Tx UE and Rx UE; QoS flow corresponding to data transmitted between Tx UE and Rx UE; logical channel corresponding to data transmitted between Tx UE and Rx UE; resource pool corresponding to data transmitted between Tx UE and Rx UE; radio bearer corresponding to data transmitted between Tx UE and Rx UE; data priority corresponding to data transmitted between Tx UE and Rx UE; CBR of resource pool corresponding to data transmitted between Tx UE and Rx UE. The Tx UE obtains the third information and determines the carrier corresponding to the third information (ie, the mapped carrier) based on the first mapping rule. The Rx UE obtains the third information from the Tx UE and determines the carrier corresponding to the third information (ie, the mapped carrier) based on the first mapping rule.

[0238] It should be noted that before a carrier for unicast sidelink communication between the Rx UE and the Tx UE is configured, the Rx UE and the Tx UE will communicate using a default carrier, a carrier in the default available carrier set, or a mapped carrier. For example, the Rx UE or Tx UE uses the default carrier, a carrier in the default available carrier set, or a mapped carrier to send or receive discovery messages, DCR messages, other PC5-S messages, PC5-RRC messages, etc.

[0239] Step 401: The Tx UE sends carrier configuration assistance information and / or carrier-related capability information to the Rx UE.

[0240] Here, the carrier configuration assistance information and / or carrier-related capability information is the first information in the above solution. The carrier configuration assistance information includes the carrier or carrier set recommended for configuration by the Tx UE, and the carrier-related capability information includes the carrier or carrier set supported by the Tx UE's capabilities.

[0241] The conditions for triggering the Tx UE to send carrier configuration assistance information and / or carrier-related capability information to the Rx UE include at least one of the following:

[0242] A first trigger condition, where the first trigger condition refers to: the Tx UE receiving request information sent by the Rx UE, where the request information is used to request the Tx UE to send carrier configuration assistance information and / or carrier-related capability information to the Rx UE;

[0243] A second trigger condition, where the second trigger condition refers to: the Tx UE receiving first indication information sent by the Rx UE, where the first indication information is used to indicate that the Rx UE and / or the network 2 where the Rx UE is located supports sidelink carrier aggregation;

[0244] A third trigger condition, wherein the third trigger condition refers to: the Tx UE determines that a periodic time point has arrived;

[0245] The fourth trigger condition refers to: the Tx UE determines that the target event occurs.

[0246] Here, the trigger corresponding to the third trigger condition may also be referred to as a periodic trigger.

[0247] Here, the trigger corresponding to the fourth trigger condition may also be referred to as a target event trigger. As some implementations, the target event includes at least one of the following:

[0248] The carrier or carrier set recommended by the Tx UE changes;

[0249] The Tx UE establishes a unicast sidelink with the Rx UE;

[0250] The carrier or carrier set used by the Tx UE changes;

[0251] The carrier or carrier set available to the Tx UE changes;

[0252] The link quality of the unicast sidelink between the Tx UE and the Rx UE changes;

[0253] A conflict occurs on carrier resources on a unicast sidelink between a Tx UE and an Rx UE.

[0254] It should be noted that for periodic triggering and target event triggering, the Tx UE needs to confirm that the Rx UE has carrier aggregation capability. When the Rx UE has carrier aggregation capability, if the target event occurs, the Tx UE sends carrier configuration assistance information and / or carrier-related capability information to the Rx UE.

[0255] In the above solution, the carrier configuration assistance information (i.e., the carrier or carrier set recommended for configuration by the Tx UE) is determined by the Tx UE based on at least one of the following:

[0256] Tx UE's capabilities support the carrier or carrier set;

[0257] Tx UE used carrier or carrier set;

[0258] Tx carrier or carrier set available to UE;

[0259] Rx UE's capabilities support the carrier or carrier set;

[0260] Rx UE used carrier or carrier set;

[0261] Rx carrier or carrier set available to the UE;

[0262] Communication information of unicast sidelink communication between Tx UE and Rx UE;

[0263] Link quality of the unicast sidelink between the Tx UE and the Rx UE;

[0264] The network configuration of the network 1 where the Tx UE is located is used to configure the carrier or carrier set supported by one or more coverage areas of the network 1;

[0265] The network capability of the network 1 where the Tx UE is located is used to determine whether the network 1 supports carrier aggregation.

[0266] In the above solution, the carrier-related capability information (i.e., the carrier or carrier set supported by the Tx UE's capabilities) is determined by the Tx UE based on at least one of the following:

[0267] Tx UE used carrier or carrier set;

[0268] Tx carrier or carrier set available to UE;

[0269] The network capability of the network 1 where the Tx UE is located is used to determine whether the network 1 supports carrier aggregation.

[0270] Step 402: The Rx UE reports to the network 2 the carrier configuration assistance information and / or carrier-related capability information obtained from the Tx UE.

[0271] Step 403: Network 2 sends carrier configuration information to Rx UE.

[0272] Here, the carrier configuration information is the first configuration information in the above solution, which is used to configure multiple carriers.

[0273] Step 404: The Rx UE sends carrier configuration information to the Tx UE.

[0274] Step 405: The Tx UE accepts or rejects all or part of the carriers configured by the carrier configuration information, and sends the configuration result to the Rx UE.

[0275] Here, an accepted carrier may be understood as a carrier with successful configuration, and a rejected carrier may be understood as a carrier with failed configuration.

[0276] Here, if the Tx UE accepts all carriers configured by the carrier configuration information, it can be understood that all carriers configured by the carrier configuration information are successfully configured (or directly understood as the carrier configuration information is configured successfully). If the Tx UE rejects all carriers configured by the carrier configuration information, it can be understood that all carriers configured by the carrier configuration information are failed to be configured (or directly understood as the carrier configuration information configuration fails).

[0277] Here, the Tx UE accepts some of the carriers configured by the carrier configuration information, which can be understood as the configuration of some of the carriers configured by the carrier configuration information being successful (or directly understood as the partial configuration of the carrier configuration information being successful). The Tx UE rejects some of the carriers configured by the carrier configuration information, which can be understood as the configuration of some of the carriers configured by the carrier configuration information failing (or directly understood as the partial configuration of the carrier configuration information failing).

[0278] Here, the configuration result includes at least one of the following: indication information for indicating acceptance or rejection of all or part of the carriers configured by the carrier configuration information; carrier information (such as carrier identifier) ​​for indicating the accepted carriers; and carrier information (such as carrier identifier) ​​for indicating the rejected carriers.

[0279] Step 406: The Tx UE reports the configuration result to the network 1.

[0280] Here, the configuration result includes at least one of the following: indication information for indicating acceptance or rejection of all or part of the carriers configured by the carrier configuration information; carrier information (such as carrier identifier) ​​for indicating the accepted carriers; and carrier information (such as carrier identifier) ​​for indicating the rejected carriers.

[0281] Step 407: Rx UE reports the configuration result to network 2.

[0282] Here, the configuration result includes at least one of the following: indication information for indicating acceptance or rejection of all or part of the carriers configured by the carrier configuration information; carrier information (such as carrier identifier) ​​for indicating the accepted carriers; and carrier information (such as carrier identifier) ​​for indicating the rejected carriers.

[0283] Here, if the indication information in the configuration result indicates that all or part of the carriers configured by the carrier configuration information are rejected (that is, all or part of the carrier configuration information fails), the Rx UE performs at least one of the following operations:

[0284] Reconfigure the carrier (i.e., re-execute steps 402 to 404 above);

[0285] Triggering the link failure process for the unicast sidelink;

[0286] Disconnect the unicast sidelink.

[0287] Step 408: If the carrier configuration information is fully or partially configured successfully, the Rx UE and the Tx UE use the successfully configured carrier to perform unicast sidelink communication.

[0288] It should be noted that, when the Rx UE is outside the coverage of network 2 and / or the Rx UE is in a non-connected state and / or the Rx UE is in mode 2, the above steps 402, 403 and 407 will not be performed. In this case, after step 401, the Rx UE independently determines the carrier configuration information and executes step 404.

[0289] It should be noted that, when the Tx UE is outside the coverage of the network 1 and / or the Tx UE is in a non-connected state and / or the Tx UE is in mode 2, the above step 406 will not be performed.

[0290] It should be noted that, when the Tx UE is within the coverage of network 1 and / or the Tx UE is in a connected state and / or the Tx UE is in mode 1, the above steps 405 and 406 may also be replaced by the following steps:

[0291] Step 405a: The Tx UE reports carrier configuration information to the network 1.

[0292] Step 405b: Network 1 accepts or rejects all or part of the carriers configured by the carrier configuration information, and sends the configuration result to the Tx UE.

[0293] Step 406a: The Tx UE sends the configuration result to the Rx UE.

[0294] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will no longer describe the various possible combinations separately. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in each embodiment described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the scope of protection of the present application.

[0295] It should also be understood that in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply a precedence in the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. In addition, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate the first direction of transmission of signals or data from a site to a user equipment in a cell, "uplink" is used to indicate the second direction of transmission of signals or data from a user equipment in a cell to a site, and "sidelink" is used to indicate the third direction of transmission of signals or data from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0296] FIG5 is a first structural diagram of a carrier configuration apparatus provided in an embodiment of the present application, which is applied to a first terminal device. As shown in FIG5 , the carrier configuration apparatus includes:

[0297] A sending unit 501 is configured to send first information to a second terminal device, where the first information is used to configure a carrier for the second terminal device or a second network where the second terminal device is located;

[0298] The receiving unit 502 is used to receive first configuration information sent by the second terminal device, where the first configuration information is used to configure multiple carriers, and at least some of the multiple carriers are used for unicast sidelink communication between the first terminal device and the second terminal device.

[0299] In some embodiments, the first information includes a carrier or a carrier set recommended for configuration by the first terminal device and / or a carrier or a carrier set supported by the capabilities of the first terminal device.

[0300] In some implementations, the carrier or carrier set that the first terminal device recommends configuring is determined based on at least one of the following:

[0301] a carrier or a set of carriers supported by the capabilities of the first terminal device;

[0302] The carrier or carrier set used by the first terminal device;

[0303] a carrier or a set of carriers available to the first terminal device;

[0304] a carrier or a set of carriers supported by the capabilities of the second terminal device;

[0305] The carrier or carrier set used by the second terminal device;

[0306] a carrier or a set of carriers available to the second terminal device;

[0307] Communication information of unicast sidelink communication between the first terminal device and the second terminal device;

[0308] link quality of the unicast sidelink between the first terminal device and the second terminal device;

[0309] a network configuration of a first network where the first terminal device is located, the network configuration of the first network being used to configure a carrier or a carrier set supported by one or more coverage areas of the first network;

[0310] The network capability of the first network where the first terminal device is located, where the network capability of the first network is used to determine whether the first network supports carrier aggregation.

[0311] In some embodiments, the carrier or carrier set supported by the capabilities of the first terminal device is determined based on at least one of the following:

[0312] The carrier or carrier set used by the first terminal device;

[0313] a carrier or a set of carriers available to the first terminal device;

[0314] The network capability of the first network where the first terminal device is located, where the network capability of the first network is used to determine whether the first network supports carrier aggregation.

[0315] In some implementations, the sending unit 501 is configured to send the first information to the second terminal device when it is determined that the trigger condition is met.

[0316] In some embodiments, the trigger condition includes at least one of the following:

[0317] a first trigger condition, where the first trigger condition refers to: the first terminal device receiving a request message sent by the second terminal device, where the request message is used to request the first terminal device to send the first message to the second terminal device;

[0318] A second trigger condition, where the second trigger condition refers to: the first terminal device receiving first indication information sent by the second terminal device, where the first indication information is used to indicate that the second terminal device and / or the second network where the second terminal device is located supports sidelink carrier aggregation;

[0319] A third trigger condition, wherein the third trigger condition refers to: the first terminal device determines that a periodic time point has arrived;

[0320] The fourth trigger condition refers to: the first terminal device determines that the target event occurs.

[0321] In some embodiments, the target event includes at least one of the following:

[0322] The carrier or carrier set recommended for configuration by the first terminal device changes;

[0323] The first terminal device establishes a unicast sidelink with the second terminal device;

[0324] The carrier or carrier set used by the first terminal device changes;

[0325] A carrier or a carrier set available to the first terminal device changes;

[0326] The link quality of the unicast sidelink between the first terminal device and the second terminal device changes;

[0327] A conflict occurs on carrier resources on the unicast sidelink between the first terminal device and the second terminal device.

[0328] In some embodiments, when the first information is used to configure a carrier in the second network where the second terminal device is located, the first information is forwarded by the second terminal device to the second network; the receiving unit 502 is used to receive the first configuration information from the second network forwarded by the second terminal device.

[0329] In some embodiments, the apparatus further includes: a decision unit 503, configured to accept or reject all or some of the carriers configured by the first configuration information; and the sending unit 501, configured to send a configuration result corresponding to the first configuration information to the second terminal device, where the configuration result includes at least one of the following:

[0330] second indication information, where the second indication information is used to indicate acceptance or rejection of all or part of the carriers configured by the first configuration information;

[0331] first carrier information, where the first carrier information is used to indicate the accepted carrier;

[0332] Second carrier information, where the second carrier information is used to indicate a rejected carrier.

[0333] In some implementations, the sending unit 501 is configured to send the configuration result to the first network where it is located.

[0334] In some embodiments, the sending unit 501 is configured to send the first configuration information to the first network in which it is located, and the receiving unit 502 is configured to receive a configuration result corresponding to the first configuration information sent by the first network, where the configuration result includes at least one of the following:

[0335] second indication information, where the second indication information is used to indicate acceptance or rejection of all or part of the carriers configured by the first configuration information;

[0336] First carrier information, where the first carrier information is used to indicate an accepted carrier;

[0337] Second carrier information, where the second carrier information is used to indicate a rejected carrier.

[0338] In some implementations, the sending unit 501 is configured to send the configuration result to the second terminal device.

[0339] In some embodiments, the second indication information is used to indicate that, when all or part of the carriers configured by the first configuration information are accepted, the accepted carriers indicated by the first carrier information are used for unicast sidelink communication between the first terminal device and the second terminal device; or, the second indication information is used to indicate that part of the carriers configured by the first configuration information are rejected, all carriers configured by the first configuration information except the rejected carriers indicated by the second carrier information are used for unicast sidelink communication between the first terminal device and the second terminal device.

[0340] In some embodiments, before all or some of the multiple carriers configured by the first configuration information are successfully configured, the first terminal device and the second terminal device communicate using a first carrier or a second carrier, where the first carrier is a default carrier or a carrier in a default available carrier set or a carrier determined based on a first mapping rule, and the second carrier is a carrier that has been successfully configured before the first terminal device receives the first configuration information.

[0341] In some embodiments, when the configuration of all or some of the multiple carriers configured by the first configuration information fails, the first terminal device and the second terminal device communicate using the first carrier, the second carrier, or the third carrier, where the first carrier is a default carrier, a carrier in the default available carrier set, or a carrier determined based on a first mapping rule, the second carrier is a carrier that has been successfully configured before the first terminal device receives the first configuration information, and the third carrier is a carrier among some of the successfully configured carriers among the multiple carriers.

[0342] In some embodiments, the first mapping rule includes a mapping relationship between third information and available carriers and / or available carrier sequences, where the third information includes at least one of the following:

[0343] a layer 2 ID of the first terminal device and / or the second terminal device;

[0344] a transmission profile (Tx profile) corresponding to data transmission between the first terminal device and the second terminal device;

[0345] The service type or application type corresponding to the data transmitted between the first terminal device and the second terminal device;

[0346] The amount of data transmitted between the first terminal device and the second terminal device;

[0347] a transmission type corresponding to data transmitted between the first terminal device and the second terminal device;

[0348] A QoS flow corresponding to data transmitted between the first terminal device and the second terminal device;

[0349] a logical channel corresponding to data transmission between the first terminal device and the second terminal device;

[0350] a resource pool corresponding to data transmitted between the first terminal device and the second terminal device;

[0351] a radio bearer corresponding to data transmission between the first terminal device and the second terminal device;

[0352] a data priority corresponding to data transmitted between the first terminal device and the second terminal device;

[0353] The CBR of the resource pool corresponding to the data transmitted between the first terminal device and the second terminal device.

[0354] In some embodiments, the first terminal device is a transmitter of unicast side link communication, and the second terminal device is a receiver of unicast side link communication; or, the first terminal device is a receiver of unicast side link communication, and the second terminal device is a transmitter of unicast side link communication.

[0355] Those skilled in the art should understand that the relevant description of the above-mentioned carrier configuration device in the embodiment of the present application can be understood with reference to the relevant description of the carrier configuration method in the embodiment of the present application.

[0356] FIG6 is a second structural diagram of a carrier configuration apparatus provided in an embodiment of the present application, which is applied to a second terminal device. As shown in FIG6 , the carrier configuration apparatus includes:

[0357] A receiving unit 601 is configured to receive first information sent by a first terminal device, where the first information is used to configure a carrier for the second terminal device or a second network where the second terminal device is located;

[0358] The sending unit 602 is used to send first configuration information to the first terminal device, where the first configuration information is used to configure multiple carriers, and at least some of the multiple carriers are used for unicast sidelink communication between the first terminal device and the second terminal device.

[0359] In some embodiments, the first information includes a carrier or a carrier set recommended for configuration by the first terminal device and / or a carrier or a carrier set supported by the capabilities of the first terminal device.

[0360] In some implementations, the carrier or carrier set that the first terminal device recommends configuring is determined based on at least one of the following:

[0361] a carrier or a carrier set supported by the capabilities of the first terminal device;

[0362] The carrier or carrier set used by the first terminal device;

[0363] a carrier or a set of carriers available to the first terminal device;

[0364] a carrier or a set of carriers supported by the capabilities of the second terminal device;

[0365] The carrier or carrier set used by the second terminal device;

[0366] a carrier or a set of carriers available to the second terminal device;

[0367] Communication information of unicast sidelink communication between the first terminal device and the second terminal device;

[0368] link quality of the unicast sidelink between the first terminal device and the second terminal device;

[0369] a network configuration of a first network where the first terminal device is located, the network configuration of the first network being used to configure a carrier or a carrier set supported by one or more coverage areas of the first network;

[0370] The network capability of the first network where the first terminal device is located, where the network capability of the first network is used to determine whether the first network supports carrier aggregation.

[0371] In some embodiments, the carrier or carrier set supported by the capabilities of the first terminal device is determined based on at least one of the following:

[0372] The carrier or carrier set used by the first terminal device;

[0373] a carrier or a set of carriers available to the first terminal device;

[0374] The network capability of the first network where the first terminal device is located, where the network capability of the first network is used to determine whether the first network supports carrier aggregation.

[0375] In some embodiments, when the first information is used to configure a carrier for the second network where the second terminal device is located, the sending unit 602 is used to forward the first information to the second network; and the receiving unit 601 is used to receive the first configuration information sent by the second network.

[0376] In some implementations, the receiving unit 601 is configured to receive a configuration result corresponding to the first configuration information sent by the first terminal device, where the configuration result includes at least one of the following:

[0377] second indication information, where the second indication information is used to indicate acceptance or rejection of all or part of the carriers configured by the first configuration information;

[0378] All carriers or part of the carriers;

[0379] First carrier information, where the first carrier information is used to indicate an accepted carrier;

[0380] Second carrier information, where the second carrier information is used to indicate a rejected carrier.

[0381] In some implementations, the sending unit 602 is configured to send the configuration result to the second network where it is located.

[0382] In some embodiments, the apparatus further includes: a processing unit, configured to, if the second indication information is used to indicate rejection of all or some of the carriers configured by the first configuration information, perform at least one of the following operations:

[0383] reconfiguring multiple carriers based on the first information and sending first configuration information to the first terminal device, where the first configuration information is used to reconfigure the multiple carriers;

[0384] Triggering the link failure process for the unicast sidelink;

[0385] Disconnect the unicast sidelink.

[0386] In some embodiments, the second indication information is used to indicate that, when all or part of the carriers configured by the first configuration information are accepted, the accepted carriers indicated by the first carrier information are used for unicast sidelink communication between the first terminal device and the second terminal device; or, the second indication information is used to indicate that part of the carriers configured by the first configuration information are rejected, all carriers configured by the first configuration information except the rejected carriers indicated by the second carrier information are used for unicast sidelink communication between the first terminal device and the second terminal device.

[0387] In some embodiments, before all or some of the multiple carriers configured by the first configuration information are successfully configured, the second terminal device and the first terminal device communicate using the first carrier or the second carrier, the first carrier is a default carrier or a carrier in the default available carrier set or a carrier determined based on the first mapping rule, and the second carrier is a carrier that has been successfully configured before the first terminal device receives the first configuration information.

[0388] In some embodiments, when the configuration of all or some of the multiple carriers configured by the first configuration information fails, the second terminal device and the first terminal device communicate using the first carrier, the second carrier, or the third carrier, where the first carrier is a default carrier, a carrier in the default available carrier set, or a carrier determined based on a first mapping rule, the second carrier is a carrier that has been successfully configured before the first terminal device receives the first configuration information, and the third carrier is a carrier among some of the successfully configured carriers among the multiple carriers.

[0389] In some embodiments, the first mapping rule includes a mapping relationship between third information and available carriers and / or available carrier sequences, where the third information includes at least one of the following:

[0390] a layer 2 ID of the first terminal device and / or the second terminal device;

[0391] (Tx profile) corresponding to data transmitted between the first terminal device and the second terminal device;

[0392] The service type or application type corresponding to the data transmitted between the first terminal device and the second terminal device;

[0393] The amount of data transmitted between the first terminal device and the second terminal device;

[0394] a transmission type corresponding to data transmitted between the first terminal device and the second terminal device;

[0395] A QoS flow corresponding to data transmitted between the first terminal device and the second terminal device;

[0396] a logical channel corresponding to data transmission between the first terminal device and the second terminal device;

[0397] a resource pool corresponding to data transmitted between the first terminal device and the second terminal device;

[0398] a radio bearer corresponding to data transmission between the first terminal device and the second terminal device;

[0399] a data priority corresponding to data transmitted between the first terminal device and the second terminal device;

[0400] The CBR of the resource pool corresponding to the data transmitted between the first terminal device and the second terminal device.

[0401] In some embodiments, the first terminal device is a transmitter of unicast side link communication, and the second terminal device is a receiver of unicast side link communication; or, the first terminal device is a receiver of unicast side link communication, and the second terminal device is a transmitter of unicast side link communication.

[0402] Those skilled in the art should understand that the relevant description of the above-mentioned carrier configuration device in the embodiment of the present application can be understood with reference to the relevant description of the carrier configuration method in the embodiment of the present application.

[0403] Figure 7 is a schematic diagram of a communication device 700 provided in an embodiment of the present application. The communication device can be a first terminal device or a second terminal device. The communication device 700 shown in Figure 7 includes a processor 710, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0404] Optionally, as shown in Figure 7, the communication device 700 may further include a memory 720. The processor 710 may call and execute a computer program from the memory 720 to implement the method in the embodiment of the present application.

[0405] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0406] Optionally, as shown in FIG7 , the communication device 700 may further include a transceiver 730 , and the processor 710 may control the transceiver 730 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0407] The transceiver 730 may include a transmitter and a receiver. The transceiver 730 may further include an antenna, and the number of antennas may be one or more.

[0408] Optionally, the communication device 700 may specifically be the first terminal device of the embodiment of the present application, and the communication device 700 may implement the corresponding processes implemented by the first terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0409] Optionally, the communication device 700 may specifically be the second terminal device of the embodiment of the present application, and the communication device 700 may implement the corresponding processes implemented by the second terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0410] Figure 8 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 800 shown in Figure 8 includes a processor 810, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0411] Optionally, as shown in FIG8 , the chip 800 may further include a memory 820 , wherein the processor 810 may call and execute a computer program from the memory 820 to implement the method in the embodiment of the present application.

[0412] The memory 820 may be a separate device independent of the processor 810 , or may be integrated into the processor 810 .

[0413] Optionally, the chip 800 may further include an input interface 830. The processor 810 may control the input interface 830 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0414] Optionally, the chip 800 may further include an output interface 840. The processor 810 may control the output interface 840 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0415] Optionally, the chip can be applied to the first terminal device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first terminal device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0416] Optionally, the chip can be applied to the second terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the second terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0417] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0418] FIG9 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. As shown in FIG9 , the communication system 900 includes a first terminal device 910 and a second terminal device 920 .

[0419] Among them, the first terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the second terminal device 920 can be used to implement the corresponding functions implemented by the first terminal device in the above method. For the sake of brevity, they are not repeated here.

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

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

[0422] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0423] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0424] Optionally, the computer-readable storage medium can be applied to the first terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the first terminal device in the various methods of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0425] Optionally, the computer-readable storage medium can be applied to the second terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the second terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0426] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0427] Optionally, the computer program product can be applied to the first terminal device in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the first terminal device in the various methods of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0428] Optionally, the computer program product can be applied to the second terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the second terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0429] The embodiment of the present application also provides a computer program.

[0430] Optionally, the computer program can be applied to the first terminal device in the embodiment of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the first terminal device in the various methods of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0431] Optionally, the computer program can be applied to the second terminal device in the embodiment of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the second terminal device in the various methods of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

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

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

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

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

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

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

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

Claims

1. A carrier configuration method, the method comprising: The first terminal device sends first information to the second terminal device, where the first information is used to configure a carrier for the second terminal device or a second network where the second terminal device is located; The first terminal device receives first configuration information sent by the second terminal device, where the first configuration information is used to configure multiple carriers, and at least some of the multiple carriers are used for unicast sidelink communication between the first terminal device and the second terminal device.

2. The method according to claim 1, wherein The first information includes a carrier or a carrier set recommended for configuration by the first terminal device and / or a carrier or a carrier set supported by the capabilities of the first terminal device.

3. The method according to claim 2, wherein: The carrier or carrier set recommended for configuration by the first terminal device is determined based on at least one of the following: a carrier or a set of carriers supported by the capabilities of the first terminal device; The carrier or carrier set used by the first terminal device; a carrier or a set of carriers available to the first terminal device; a carrier or a carrier set supported by the capabilities of the second terminal device; The carrier or carrier set used by the second terminal device; a carrier or a set of carriers available to the second terminal device; Communication information of unicast sidelink communication between the first terminal device and the second terminal device; link quality of the unicast sidelink between the first terminal device and the second terminal device; a network configuration of a first network where the first terminal device is located, the network configuration of the first network being used to configure a carrier or a carrier set supported by one or more coverage areas of the first network; The network capability of the first network where the first terminal device is located, where the network capability of the first network is used to determine whether the first network supports carrier aggregation.

4. The method according to claim 2 or 3, wherein: The carrier or carrier set supported by the capabilities of the first terminal device is determined based on at least one of the following: The carrier or carrier set used by the first terminal device; a carrier or a set of carriers available to the first terminal device; The network capability of the first network where the first terminal device is located, where the network capability of the first network is used to determine whether the first network supports carrier aggregation.

5. The method according to any one of claims 1 to 4, wherein The first terminal device sending first information to the second terminal device includes: When determining that the trigger condition is met, the first terminal device sends the first information to the second terminal device.

6. The method according to claim 5, wherein: The triggering condition includes at least one of the following: a first trigger condition, where the first trigger condition refers to: the first terminal device receiving a request message sent by the second terminal device, where the request message is used to request the first terminal device to send the first message to the second terminal device; The second trigger condition refers to: the first terminal device receives first indication information sent by the second terminal device, and the first indication information is used to indicate that the second terminal device and / or the second network where the second terminal device is located supports sidelink carrier aggregation; A third trigger condition, wherein the third trigger condition refers to: the first terminal device determines that a periodic time point has arrived; The fourth trigger condition refers to: the first terminal device determines that the target event occurs.

7. The method according to claim 5, wherein: The target event includes at least one of the following: The carrier or carrier set recommended for configuration by the first terminal device changes; The first terminal device establishes a unicast sidelink with the second terminal device; The carrier or carrier set used by the first terminal device changes; A carrier or a carrier set available to the first terminal device changes; The link quality of the unicast sidelink between the first terminal device and the second terminal device changes; A conflict occurs on carrier resources on the unicast sidelink between the first terminal device and the second terminal device.

8. The method according to any one of claims 1 to 7, wherein When the first information is used for configuring a carrier in the second network where the second terminal device is located, the first information is forwarded by the second terminal device to the second network; The first terminal device receiving the first configuration information sent by the second terminal device includes: The first terminal device receives first configuration information from the second network forwarded by the second terminal device.

9. The method according to any one of claims 1 to 8, wherein After the first terminal device receives the first configuration information sent by the second terminal device, the method further includes: The first terminal device accepts or rejects all or some of the carriers configured by the first configuration information, and sends a configuration result corresponding to the first configuration information to the second terminal device, where the configuration result includes at least one of the following: second indication information, where the second indication information is used to indicate acceptance or rejection of all or part of the carriers configured by the first configuration information; first carrier information, where the first carrier information is used to indicate the accepted carrier; Second carrier information, where the second carrier information is used to indicate a rejected carrier.

10. The method according to claim 9, wherein: The method further comprises: The first terminal device sends the configuration result to the first network where it is located.

11. The method according to any one of claims 1 to 8, wherein After the first terminal device receives the first configuration information sent by the second terminal device, the method further includes: The first terminal device sends the first configuration information to the first network where the first terminal device is located, and receives a configuration result corresponding to the first configuration information sent by the first network, where the configuration result includes at least one of the following: second indication information, where the second indication information is used to indicate acceptance or rejection of all or part of the carriers configured by the first configuration information; First carrier information, where the first carrier information is used to indicate an accepted carrier; Second carrier information, where the second carrier information is used to indicate a rejected carrier.

12. The method according to claim 11, wherein The method further comprises: The first terminal device sends the configuration result to the second terminal device.

13. The method according to any one of claims 9 to 12, wherein: The second indication information is used to indicate that, when all or part of the carriers configured by the first configuration information are accepted, the accepted carrier indicated by the first carrier information is used for unicast sidelink communication between the first terminal device and the second terminal device; or The second indication information is used to indicate that, in the case where some carriers configured by the first configuration information are rejected, all carriers configured by the first configuration information except the rejected carriers indicated by the second carrier information are used for unicast sidelink communication between the first terminal device and the second terminal device.

14. The method according to any one of claims 1 to 13, wherein The method further comprises: Before all or part of the multiple carriers configured by the first configuration information are successfully configured, the first terminal device and the second terminal device communicate using the first carrier or the second carrier, the first carrier is a default carrier or a carrier in the default available carrier set or a carrier determined based on the first mapping rule, and the second carrier is a carrier that has been successfully configured before the first terminal device receives the first configuration information.

15. The method according to any one of claims 1 to 13, wherein The method further comprises: In the event that the configuration of all or some of the multiple carriers configured by the first configuration information fails, the first terminal device and the second terminal device communicate using the first carrier, the second carrier, or the third carrier, where the first carrier is a default carrier, a carrier in a default available carrier set, or a carrier determined based on a first mapping rule, the second carrier is a carrier that has been successfully configured before the first terminal device receives the first configuration information, and the third carrier is a carrier among some of the successfully configured carriers among the multiple carriers.

16. The method according to claim 14 or 15, wherein: The first mapping rule includes a mapping relationship between third information and available carriers and / or available carrier sequences, where the third information includes at least one of the following: a layer 2 ID of the first terminal device and / or the second terminal device; a Tx profile corresponding to data transmission between the first terminal device and the second terminal device; The service type or application type corresponding to the data transmitted between the first terminal device and the second terminal device; The amount of data transmitted between the first terminal device and the second terminal device; a transmission type corresponding to data transmitted between the first terminal device and the second terminal device; A QoS flow corresponding to data transmitted between the first terminal device and the second terminal device; a logical channel corresponding to data transmission between the first terminal device and the second terminal device; a resource pool corresponding to data transmitted between the first terminal device and the second terminal device; a radio bearer corresponding to data transmission between the first terminal device and the second terminal device; a data priority corresponding to data transmitted between the first terminal device and the second terminal device; The congestion level CBR of the resource pool corresponding to the data transmitted between the first terminal device and the second terminal device.

17. The method according to any one of claims 1 to 16, wherein The first terminal device is a transmitting end of unicast sidelink communication, and the second terminal device is a receiving end of unicast sidelink communication; or, The first terminal device is a receiving end of unicast side link communication, and the second terminal device is a sending end of unicast side link communication.

18. A carrier configuration method, the method comprising: The second terminal device receives first information sent by the first terminal device, where the first information is used to configure a carrier for the second terminal device or a second network where the second terminal device is located; The second terminal device sends first configuration information to the first terminal device, where the first configuration information is used to configure multiple carriers, at least some of which are used for unicast sidelink communication between the first terminal device and the second terminal device.

19. The method according to claim 18, wherein The first information includes a carrier or a carrier set recommended for configuration by the first terminal device and / or a carrier or a carrier set supported by the capabilities of the first terminal device.

20. The method according to claim 19, wherein The carrier or carrier set recommended for configuration by the first terminal device is determined based on at least one of the following: a carrier or a set of carriers supported by the capabilities of the first terminal device; The carrier or carrier set used by the first terminal device; a carrier or a set of carriers available to the first terminal device; a carrier or a carrier set supported by the capabilities of the second terminal device; The carrier or carrier set used by the second terminal device; a carrier or a set of carriers available to the second terminal device; Communication information of unicast sidelink communication between the first terminal device and the second terminal device; link quality of the unicast sidelink between the first terminal device and the second terminal device; a network configuration of a first network where the first terminal device is located, the network configuration of the first network being used to configure a carrier or a carrier set supported by one or more coverage areas of the first network; The network capability of the first network where the first terminal device is located, where the network capability of the first network is used to determine whether the first network supports carrier aggregation.

21. The method according to claim 19 or 20, wherein The carrier or carrier set supported by the capabilities of the first terminal device is determined based on at least one of the following: The carrier or carrier set used by the first terminal device; a carrier or a set of carriers available to the first terminal device; The network capability of the first network where the first terminal device is located, where the network capability of the first network is used to determine whether the first network supports carrier aggregation.

22. The method according to any one of claims 18 to 21, wherein The first information is used when the second network where the second terminal device is located is configured with a carrier, After the second terminal device receives the first information sent by the first terminal device, the method further includes: the second terminal device forwarding the first information to the second network; Before the second terminal device sends the first configuration information to the first terminal device, the method further includes: the second terminal device receiving the first configuration information sent by the second network.

23. The method according to any one of claims 18 to 22, wherein After the second terminal device sends the first configuration information to the first terminal device, the method further includes: The second terminal device receives a configuration result corresponding to the first configuration information sent by the first terminal device, where the configuration result includes at least one of the following: second indication information, where the second indication information is used to indicate acceptance or rejection of all or part of the carriers configured by the first configuration information; All carriers or part of the carriers; First carrier information, where the first carrier information is used to indicate an accepted carrier; Second carrier information, where the second carrier information is used to indicate a rejected carrier.

24. The method according to claim 23, wherein The method further comprises: The second terminal device sends the configuration result to the second network where it is located.

25. The method according to claim 23 or 24, wherein The method further comprises: If the second indication information is used to indicate rejection of all or part of the carriers configured by the first configuration information, the second terminal device performs at least one of the following operations: reconfiguring multiple carriers based on the first information and sending first configuration information to the first terminal device, where the first configuration information is used to reconfigure the multiple carriers; Triggering the link failure process for the unicast sidelink; Disconnect the unicast sidelink.

26. The method according to any one of claims 23 to 25, wherein The second indication information is used to indicate that, when all or part of the carriers configured by the first configuration information are accepted, the accepted carrier indicated by the first carrier information is used for unicast sidelink communication between the first terminal device and the second terminal device; or The second indication information is used to indicate that, in the case where some carriers configured by the first configuration information are rejected, all carriers configured by the first configuration information except the rejected carriers indicated by the second carrier information are used for unicast sidelink communication between the first terminal device and the second terminal device.

27. The method according to any one of claims 18 to 26, wherein The method further comprises: Before all or part of the multiple carriers configured by the first configuration information are successfully configured, the second terminal device and the first terminal device communicate using the first carrier or the second carrier, the first carrier is a default carrier or a carrier in the default available carrier set or a carrier determined based on the first mapping rule, and the second carrier is a carrier that has been successfully configured before the first terminal device receives the first configuration information.

28. The method according to any one of claims 18 to 26, wherein The method further comprises: In the event that the configuration of all or some of the multiple carriers configured by the first configuration information fails, the second terminal device and the first terminal device communicate using the first carrier, the second carrier, or the third carrier, where the first carrier is a default carrier, a carrier in a default available carrier set, or a carrier determined based on a first mapping rule, the second carrier is a carrier that has been successfully configured before the first terminal device receives the first configuration information, and the third carrier is a carrier among some of the successfully configured carriers among the multiple carriers.

29. The method according to claim 27 or 28, wherein The first mapping rule includes a mapping relationship between third information and available carriers and / or available carrier sequences, where the third information includes at least one of the following: a layer 2 ID of the first terminal device and / or the second terminal device; a Tx profile corresponding to data transmitted between the first terminal device and the second terminal device; The service type or application type corresponding to the data transmitted between the first terminal device and the second terminal device; The amount of data transmitted between the first terminal device and the second terminal device; a transmission type corresponding to data transmitted between the first terminal device and the second terminal device; A QoS flow corresponding to data transmitted between the first terminal device and the second terminal device; a logical channel corresponding to data transmission between the first terminal device and the second terminal device; a resource pool corresponding to data transmitted between the first terminal device and the second terminal device; a radio bearer corresponding to data transmission between the first terminal device and the second terminal device; a data priority corresponding to data transmitted between the first terminal device and the second terminal device; The CBR of the resource pool corresponding to the data transmitted between the first terminal device and the second terminal device.

30. The method according to any one of claims 18 to 29, wherein The first terminal device is a transmitting end of unicast sidelink communication, and the second terminal device is a receiving end of unicast sidelink communication; or, The first terminal device is a receiving end of unicast side link communication, and the second terminal device is a sending end of unicast side link communication.

31. A carrier configuration apparatus, applied to a first terminal device, the method comprising: A sending unit, configured to send first information to a second terminal device, where the first information is used to configure a carrier for the second terminal device or a second network where the second terminal device is located; A receiving unit is used to receive first configuration information sent by the second terminal device, where the first configuration information is used to configure multiple carriers, and at least some of the multiple carriers are used for unicast sidelink communication between the first terminal device and the second terminal device.

32. A carrier configuration apparatus, applied to a second terminal device, the method comprising: A receiving unit, configured to receive first information sent by a first terminal device, where the first information is used to configure a carrier for the second terminal device or a second network where the second terminal device is located; A sending unit is used to send first configuration information to the first terminal device, where the first configuration information is used to configure multiple carriers, and at least some of the multiple carriers are used for unicast sidelink communication between the first terminal device and the second terminal device.

33. A terminal device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to perform the method according to any one of claims 1 to 17, or the method according to any one of claims 18 to 30.

34. A chip comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 17, or the method according to any one of claims 18 to 30.

35. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 17, or the method according to any one of claims 18 to 30.

36. A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 1 to 17, or any one of claims 18 to 30.

37. A computer program, the computer program causing a computer to perform the method of any one of claims 1 to 17, or any one of claims 18 to 30.

Images