WO2024026787A1 - 一种载波配置方法及装置、终端设备 - Google Patents

一种载波配置方法及装置、终端设备 Download PDF

Info

Publication number
WO2024026787A1
WO2024026787A1 PCT/CN2022/110360 CN2022110360W WO2024026787A1 WO 2024026787 A1 WO2024026787 A1 WO 2024026787A1 CN 2022110360 W CN2022110360 W CN 2022110360W WO 2024026787 A1 WO2024026787 A1 WO 2024026787A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
carrier
information
carriers
network
Prior art date
Application number
PCT/CN2022/110360
Other languages
English (en)
French (fr)
Inventor
冷冰雪
卢前溪
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2022/110360 priority Critical patent/WO2024026787A1/zh
Publication of WO2024026787A1 publication Critical patent/WO2024026787A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • the embodiments of the present application relate to the field of mobile communication technology, and specifically relate to a carrier configuration method and device, and terminal equipment.
  • unicast sidelink communication In sidelink (SL) communication, not only broadcast communication, but also unicast and multicast communication can be supported.
  • unicast sidelink communication (hereinafter referred to as unicast sidelink communication)
  • the corresponding receiving end of the communication has only one terminal device.
  • carrier aggregation technology In order to expand bandwidth, consider introducing carrier aggregation technology into sidelink communications, and how to support carrier aggregation in unicast sidelink communications needs to be improved.
  • Embodiments of the present application provide a carrier configuration method and device, terminal equipment, chips, computer-readable storage media, computer program products, and computer programs.
  • the first terminal device sends first information to the second terminal device, where the first information is used for the second terminal device or the second network configuration carrier where the second terminal device is located;
  • the first terminal device receives first configuration information sent by the second terminal device, the first configuration information is used to configure multiple carriers, at least part of the multiple carriers are used for the first terminal Unicast sidelink communication is performed between the device and the second terminal device.
  • the second terminal device receives the first information sent by the first terminal device, where the first information is used for the second terminal device or the second network configuration carrier where the second terminal device is located;
  • the second terminal device sends first configuration information to the first terminal device, the first configuration information is used to configure multiple carriers, at least part of the multiple carriers are used for the first terminal device Perform unicast sidelink communication with the second terminal device.
  • the carrier configuration device provided by the embodiment of the present application is applied to the first terminal equipment, and the method includes:
  • a sending unit configured to send first information to a second terminal device, where the first information is used for the second terminal device or the second network configuration carrier where the second terminal device is located;
  • a receiving unit configured to receive first configuration information sent by the second terminal device, the first configuration information being used to configure multiple carriers, at least part of the multiple carriers being used by the first terminal device Perform unicast sidelink communication with the second terminal device.
  • the carrier configuration device provided by the embodiment of the present application is applied to the second terminal equipment, and the method includes:
  • a receiving unit configured to receive the first information sent by the first terminal device, the first information being used for the second terminal device or the second network configuration carrier where the second terminal device is located;
  • a sending unit configured to send first configuration information to the first terminal device, where the first configuration information is used to configure multiple carriers, at least some of the multiple carriers are used for the first terminal device and Unicast sidelink communication is performed between the second terminal devices.
  • the terminal device provided by the embodiment of the present application includes a processor and a memory.
  • the memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute the above carrier configuration method.
  • the chip provided by the embodiment of this application is used to implement the above carrier configuration method.
  • the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above-mentioned carrier configuration method.
  • the computer-readable storage medium provided by the embodiment of the present application is used to store a computer program.
  • the computer program causes the computer to execute the above-mentioned carrier configuration method.
  • the computer program product provided by the embodiment of the present application includes computer program instructions, which cause the computer to execute the above-mentioned carrier configuration method.
  • the computer program provided by the embodiment of the present application when run on a computer, causes the computer to execute the above carrier configuration method.
  • 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 to provide unicast between the first terminal device and the second terminal device.
  • Sidelink communication configures multiple carriers, thereby supporting carrier aggregation in unicast sidelink communication. Since this carrier configuration method is combined with the first information provided by the first terminal device as an aid, the configured carrier has higher reliability and improves the performance of unicast sidelink communication.
  • Figure 1-1 is a schematic diagram of the terminal device in mode one
  • Figure 1-2 is a schematic diagram of the terminal device in mode two;
  • FIG. 2 is a schematic flowchart 1 of the carrier configuration method provided by the embodiment of the present application.
  • FIG. 3 is a schematic flowchart 2 of the carrier configuration method provided by the embodiment of the present application.
  • FIG. 4 is a schematic flowchart three of the carrier configuration method provided by the embodiment of the present application.
  • Figure 5 is a schematic structural diagram of a carrier configuration device provided by an embodiment of the present application.
  • Figure 6 is a schematic diagram 2 of the structural composition of a carrier configuration device provided by an embodiment of the present application.
  • Figure 7 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 8 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • Figure 9 is a schematic block diagram of a communication system provided by an embodiment of the present application.
  • D2D Device to Device
  • D2D communication technology is introduced.
  • D2D communication is based on sidelink transmission technology.
  • the Internet of Vehicles system uses D2D communication (that is, direct device-to-device communication), so it has higher spectral efficiency and lower transmission delay.
  • the Third Generation Partnership Project (3GPP) defines two transmission modes: Mode 1 and Mode 2. Mode 1 and Mode 2 are described below.
  • Mode 1 As shown in Figure 1-1, the transmission resources of the terminal equipment are allocated by the base station, and the terminal equipment sends data on the sidelink according to the resources allocated by the base station; the base station can allocate a single transmission to the terminal equipment. resources, and can also allocate semi-static transmission resources to terminal devices.
  • Mode 2 As shown in Figure 1-2, the terminal device selects a resource in the resource pool to send data. Specifically, the terminal device may select transmission resources from the resource pool by listening, or select transmission resources from the resource pool by random selection.
  • D2D communication is divided into the following different stages for research:
  • Proximity based Service Device-to-device communication is studied for the ProSe scenario, which is mainly targeted at public safety services.
  • ProSe by configuring the position of the resource pool in the time domain, for example, the resource pool is discontinuous in the time domain, so that the terminal device can transmit/receive discontinuously on the sidelink, thereby achieving the effect of power saving.
  • V2X Vehicle to Everything
  • D2D Device-to-device communication is studied for scenarios where wearable devices access the network through mobile phones. It is mainly oriented to low mobile speed and low-power access scenarios.
  • FeD2D during the pre-research phase, 3GPP concluded that the base station can configure the DRX parameters of the remote terminal device through a relay terminal device.
  • LTE V2X has also evolved into New Radio (NR) V2X.
  • NR V2X needs to support autonomous driving, so it puts forward higher requirements for data interaction between vehicles, such as higher throughput, lower latency, higher reliability, larger coverage, and more flexible resources. Distribution etc.
  • NR V2X is not limited to broadcast scenarios, but further extends to unicast and multicast scenarios, and the application of V2X is studied in these scenarios.
  • unicast transmission there is only one terminal device at the receiving end.
  • the receiving end is all terminal devices in a communication group, or all terminal devices within a certain transmission distance.
  • broadcast transmission the receiving end is any terminal device.
  • Mode one is that the network device allocates transmission resources to the terminal device
  • mode two is that the terminal device selects transmission resources.
  • the terminal device may be in a mixed mode. Specifically, it can use mode 1 to obtain resources and mode 2 to obtain resources at the same time.
  • a side feedback mechanism is introduced, that is, feedback-based Hybrid Automatic Repeat ReQuest (HARQ) retransmission.
  • HARQ Hybrid Automatic Repeat ReQuest
  • the side feedback mechanism is not limited to unicast scenarios, and can also be used in unicast scenarios. Applicable to multicast scenarios.
  • CA Carrier Aggregation
  • CA is a bandwidth expansion technology that can aggregate multiple component carriers (CC) together and be received or transmitted simultaneously by a terminal device or network device.
  • CC component carriers
  • CA can be divided into intra-band CA (Intra-band CA) and inter-band CA (Inter-band CA).
  • intra-band CA Intra-band CA
  • Inter-band CA inter-band CA
  • One of the main uses of intra-band CA is in scenarios where the cell carrier bandwidth is greater than the single carrier bandwidth capability of the terminal device.
  • the terminal device can use CA to operate in a "wide carrier".
  • the base station supports a 300MHz carrier, while the terminal device supports a maximum carrier of 100MHz.
  • the terminal device can use CA to achieve broadband operation greater than 100MHz.
  • the aggregated carriers can be adjacent carriers or non-adjacent carriers.
  • the primary cell (PCell) and the 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 Detection (BFD); New Beam Identification (NBI); Failure recovery request (Beam Failure Recovery ReQest, BFRQ); network side response.
  • BFD Beam Failure Detection
  • NBI Beam Failure Detection
  • BFD Beam Failure Detection
  • BFD New Beam Identification
  • NBI New Beam Identification
  • Failure recovery request Beam Failure Recovery ReQest, BFRQ
  • network side response Specifically, the terminal device measures the downlink transmission beam to determine the link quality corresponding to the downlink transmission beam. If the corresponding link quality is very poor, the downlink beam is considered to have beam failure.
  • the terminal equipment will also measure a set of candidate beams and select the beam that meets a certain threshold as a new beam. Then the terminal device notifies the network that a beam failure has occurred through the beam failure recovery request process, and reports a new beam. After the network receives the beam failure recovery request sent by the terminal device, it knows that the beam failure has occurred in the terminal device, and chooses to send the Physical Downlink Control Channel (PDCCH) from the new beam. The terminal device receives the PDCCH sent by the network on the new beam. PDCCH considers that the response from the network side has been received correctly. At this point, the beam failure recovery process is successfully completed.
  • PDCCH Physical Downlink Control Channel
  • the upper layer is configured with a mapping relationship between service types and carriers.
  • the upper layer indicates the available carriers or carrier sets to the access (Access Stotum, AS) layer;
  • the AS layer is configured with the available carriers or carrier sets for each logical channel and is configured with the Channel Busy Rate (CBR) threshold value 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.
  • NR SL also needs to introduce carrier aggregation technology. Compared with LTE V2X, NR SL requires additional considerations when introducing carrier aggregation technology. 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 of the embodiments of the present application are proposed.
  • FIG. 2 is a schematic flow chart of a carrier configuration method provided by an embodiment of the present application. As shown in Figure 2, the carrier configuration method includes the following steps:
  • Step 201 The first terminal device sends the first information to the second terminal device.
  • Step 202 The second terminal device receives the first information sent by the first terminal device, where the first information is used for the second terminal device or the second network configuration carrier where the second terminal device is located.
  • the first terminal device is a sending end of unicast sidelink communication
  • the second terminal device is a receiving end of unicast sidelink communication.
  • the first terminal device is a receiving end of unicast sidelink communication
  • the second terminal device is a sending end of unicast sidelink communication.
  • the sender sends data on the unicast sidelink; for the receiver of unicast sidelink communication, the receiver sends data on the unicast sidelink. Receive data on the link.
  • 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.
  • carrier aggregation that is, communication is performed on the unicast sidelink through aggregated carriers.
  • corresponding carrier configuration is required.
  • the first terminal device sends the first information to the second terminal device, and the second terminal device receives the first information sent by the first terminal device, and the first information is used for the second terminal device or the second terminal device.
  • the second network where the second terminal device is located configures a carrier.
  • the first information includes a carrier or a set of carriers recommended to be configured by the first terminal device and/or a carrier or set of carriers supported by the capabilities of the first terminal device.
  • the information corresponding to the carrier or carrier set recommended to be configured by the first terminal device may also be called carrier configuration assistance information, which is not limited in this application.
  • the information corresponding to the carrier or carrier set supported by the capability of the first terminal device may also be called carrier-related capability information, which is not limited in this application.
  • the carrier or carrier set recommended to be configured by the first terminal device is determined based on at least one of the following:
  • the carrier or set of carriers supported by the capability of the first terminal device
  • the carrier or set of carriers used by the first terminal device The carrier or set of carriers used by the first terminal device;
  • the carrier or set of carriers available to the first terminal device are the carrier or set of carriers available to the first terminal device
  • the carrier or set of carriers used by the second terminal device is not limited to
  • the carrier or set of carriers available to the second terminal device are the carrier or set of carriers available to the second terminal device.
  • the link quality of the unicast sidelink between the first terminal device and the second terminal device is the link quality of the unicast sidelink between the first terminal device and the second terminal device
  • the network configuration of the first network where the first terminal device is located is used to configure carriers or carrier sets 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 is used to determine whether the first network supports carrier aggregation.
  • the carrier or carrier set supported by the capability of the first terminal device is determined based on at least one of the following:
  • the carrier or set of carriers used by the first terminal device The carrier or set of carriers used by the first terminal device;
  • the carrier or set of carriers available to the first terminal device are the carrier or set of carriers available to the first terminal device
  • the network capability of the first network where the first terminal device is located is used to determine whether the first network supports carrier aggregation.
  • the carriers or carrier sets used by the first terminal device refer to: other sidelinks and/or carriers on uplinks and downlinks other than the unicast sidelink of the first terminal device. or carrier set.
  • the carriers or carrier sets available to the first terminal device refer to the carriers or carrier sets supported by the capabilities of the first terminal device excluding the carriers or carrier sets already used by the first terminal device.
  • the carriers or carrier sets used by the second terminal device refer to: other sidelinks and/or carriers on uplinks and downlinks other than the unicast sidelink of the second terminal device. or carrier set.
  • the carriers or carrier sets available to the second terminal device refer to the carriers or carrier sets supported by the capabilities of the second terminal device excluding the carriers or carrier sets used by the second terminal device.
  • the first terminal device may, but is not limited to, obtain relevant information of the second terminal device (i.e., the carrier or carrier set supported by the capabilities of the second terminal device, the second terminal device At least one of the carrier or carrier set used by the device and the carrier or carrier set available to the second terminal device):
  • Method 1-1 The first terminal device sends request information to the second terminal device, the request information is used to request the second terminal device to report relevant information of the second terminal device; the second terminal device After receiving the request information, the 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. .
  • Method 1-2 The first terminal device receives the relevant information of the second terminal device actively sent by the second terminal device.
  • 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:
  • Method 2-1 When the first terminal device is the sending end of unicast sidelink communication, the first terminal device naturally knows the communication between the first terminal device and the second terminal device. Communication information for unicast sidelink communications.
  • Method 2-2 When the first terminal device is the receiving end of unicast sidelink communication, the first terminal device receives the communication information of unicast sidelink communication sent by the second terminal device. .
  • the communication information of the unicast sidelink communication includes at least one of the following communication-related information: data amount, data type, and logical channel identification.
  • 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:
  • Method 3-1 The first terminal device measures the reference signal sent by the second terminal device, and determines the unicast between the first terminal device and the second terminal device based on the measurement result of the reference signal. Link quality of the sidelink.
  • 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 sidelink between the first terminal device and the second terminal device.
  • the measurement result of the reference signal may be a reference signal receiving power (RSRP) measurement value of the reference signal, a reference signal receiving quality (Reference Signal Received Quality, RSRQ), etc.
  • RSRP reference signal receiving power
  • RSRQ Reference Signal Received Quality
  • the first terminal device may, but is not limited to, obtain the network configuration and/or network capabilities of the first network where the first terminal device is located in the following manner:
  • Method 4-1) The first terminal device receives a system broadcast message sent by the first network, the system broadcast message carries the network configuration and/or network capabilities of the first network; the first terminal device receives from The network configuration and/or network capabilities of the first network are obtained from the system broadcast message.
  • Method 4-2) The first terminal device sends request information to the first network, where the request information is used to request the first network to deliver the network configuration and/or network capabilities of the first network; so The first terminal device receives the network configuration and/or network capabilities of the first network delivered by the first network.
  • the network configuration of the first network is used to configure carriers or sets of carriers supported by one or more coverage areas of the first network.
  • the network capability of the first network is used to determine whether the first network supports carrier aggregation.
  • the network capability of the first network may be a piece of capability information or a piece of 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. Whether the first network supports carrier aggregation.
  • 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 a mode one state; the first terminal device is in a connected state.
  • the first terminal device when the first terminal device determines that the trigger condition is met, the first terminal device sends the first information to the second terminal device.
  • the triggering condition includes at least one of the following:
  • a first triggering condition refers to: the first terminal device receives request information sent by the second terminal device, and the request information is used to request the first terminal device to send a request to the second terminal device.
  • the terminal device sends the first information;
  • the second triggering condition refers to: the first terminal device receives the first indication information sent by the second terminal device, and the first indication information is used to instruct the second terminal device and /or the second network where the second terminal device is located supports sidelink carrier aggregation;
  • a third triggering condition refers to: the arrival of a periodic time point determined by the first terminal device;
  • the fourth trigger condition refers to: the first terminal device determines that a target event occurs.
  • the target event includes at least one of the following:
  • the carrier or carrier set recommended to be configured 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 equipment changes
  • the carrier or 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.
  • the first terminal device and the second terminal device use the first carrier or The second carrier communicates, 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 the first terminal device to receive the first Configuration information for carriers that have been successfully configured before.
  • the first mapping rule includes a mapping relationship between third information to available carriers and/or available carrier serial numbers, and the third information includes at least one of the following:
  • the layer 2 ID of the first terminal device and/or the second terminal device is the layer 2 ID of the first terminal device and/or the second terminal device
  • the transmission configuration (Tx profile) corresponding to the data transmitted between the first terminal device and the second terminal device;
  • the amount of data corresponding to the data transmitted between the first terminal device and the second terminal device is the amount of data corresponding to the data transmitted between the first terminal device and the second terminal device
  • the transmission type corresponding to the data transmitted between the first terminal device and the second terminal device
  • a resource pool corresponding to data transmission between the first terminal device and the second terminal device
  • the congestion level (CBR) of the resource pool corresponding to data transmission between the first terminal device and the second terminal device is the congestion level (CBR) of the resource pool corresponding to data transmission between the first terminal device and the second terminal device.
  • the layer 2 ID is the communication address used by the terminal device for side link communication.
  • the transmission type may be a broadcast type, a unicast type, or a multicast type.
  • the transmission type is a unicast type.
  • Step 203 The second terminal device sends the first configuration information to the first terminal device.
  • Step 204 The first terminal device receives the first configuration information sent by the second terminal device, the first configuration information is used to configure multiple carriers, and at least part of the multiple carriers are used for the Unicast sidelink communication is performed between the first terminal device and the second terminal device.
  • the first information is used for the second terminal device or the second network configuration carrier where the second terminal device is located. It is explained below case by case.
  • Solution 1-1 The first information is used for the second terminal device to configure a carrier.
  • Solution 1-1 may be, but is not limited to, applicable to the following scenarios: the second terminal device is located outside the coverage of the second network; the second terminal device is in a non-connected state; the second terminal device is in a mode two state .
  • the second terminal device After receiving the first information sent by the first terminal device, the second terminal device configures the carrier according to the first information to generate first configuration information; the second terminal device sends the first configuration to the first terminal device information, 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.
  • 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; and the first terminal device is in a mode one state.
  • Solution 1-2 The first information is used to configure the carrier of the second network where the second terminal device is located.
  • 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; and the second terminal device is in a mode one state.
  • the second terminal device 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.
  • the first information will be forwarded by the second terminal device to the second network, and the second network configures the carrier according to the first information to generate the 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 configuration information from the second terminal device forwarded by the second terminal device.
  • the first configuration information of the second network is used to configure multiple carriers.
  • the first terminal device or the first network where the first terminal device is located decides to accept or Reject all or part of the carriers configured by the first configuration information. It is explained below case by case.
  • Solution 2-1 The first terminal device decides to accept or reject all or part of the carriers configured in the first configuration information.
  • Solution 2-1 may be, but is not limited to, 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 a mode two state .
  • the first terminal device 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 part of the carriers configured by the first configuration information and sends a request to the second terminal device.
  • the terminal device sends a configuration result corresponding to the first configuration information, where the configuration result includes at least one of the following:
  • the second indication information is used to indicate acceptance or rejection of all carriers or part of the carriers configured by the first configuration information
  • First carrier information the first carrier information is used to indicate an accepted carrier
  • Second carrier information the second carrier information is used to indicate the rejected carrier.
  • the accepted carrier is also the successfully configured carrier.
  • the first carrier information may also be called configuration success information, which is not limited in this application.
  • the first carrier information includes the carrier identifier of the accepted carrier.
  • the rejected carrier is also the carrier whose configuration failed.
  • the second carrier information may also be called configuration failure information, which is not limited in this application.
  • the second carrier information includes the carrier identification of the rejected carrier.
  • solution 2-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; and the first terminal device is in a mode one state.
  • the first terminal device sends the configuration result to the first network where it is located.
  • Solution 2-2 The first network where the first terminal device is located decides to accept or reject all or part of the carriers configured in the first configuration information.
  • 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; and the first terminal device is in a mode one state.
  • the first terminal device 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; the first network receives the first configuration information. After the first configuration information is 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 first configuration information corresponding to the first terminal device to the first terminal device.
  • the configuration result 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 first configuration to the second terminal device The configuration result corresponding to the information.
  • the second terminal device receives the configuration result corresponding to the first configuration information sent by the first terminal device.
  • the configuration results include at least one of the following:
  • the second indication information is used to indicate acceptance or rejection of all carriers or part of the carriers configured by the first configuration information
  • First carrier information the first carrier information is used to indicate an accepted carrier
  • Second carrier information the second carrier information is used to indicate the rejected carrier.
  • the accepted carrier is also the successfully configured carrier.
  • the first carrier information may also be called configuration success information, which is not limited in this application.
  • the first carrier information includes the carrier identifier of the accepted carrier.
  • the rejected carrier is also the carrier whose configuration failed.
  • the second carrier information may also be called configuration failure information, which is not limited in this application.
  • the second carrier information includes the carrier identification of the rejected carrier.
  • the second terminal device performs at least one of the following operations:
  • the second terminal device sends the configuration result to the second network where it is located or the second terminal device sends the final carrier configuration to the second network where it is located based on the configuration result.
  • the prerequisites for the second terminal device to send the configuration result to the second network where it is located include at least one of the following: the second terminal device is located within the coverage of the second network; the second terminal device is located in Connected state; the second terminal device is in a mode one state.
  • the accepted carrier indicated by the first carrier information is used for the Unicast sidelink communication is performed between the first terminal device and the second terminal device; or, when the second indication information is used to indicate rejecting some of the carriers configured by the first configuration information, Among all carriers configured in the first configuration information, carriers other than the rejected carrier indicated by the second carrier information are used for unicast side communication between the first terminal device and the second terminal device. Line link communication.
  • a first terminal device is used between the first terminal device and the second terminal device.
  • 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
  • the second carrier is the first terminal.
  • the carrier is a carrier that has been configured successfully before the device receives the first configuration information
  • the third carrier is a carrier among some of the carriers that are successfully configured among the plurality of carriers.
  • the first mapping rule includes a mapping relationship between third information to available carriers and/or available carrier serial numbers, and the third information includes at least one of the following:
  • the layer 2 ID of the first terminal device and/or the second terminal device is the layer 2 ID of the first terminal device and/or the second terminal device
  • the transmission configuration (Tx profile) corresponding to the data transmitted between the first terminal device and the second terminal device;
  • the amount of data corresponding to the data transmitted between the first terminal device and the second terminal device is the amount of data corresponding to the data transmitted between the first terminal device and the second terminal device
  • the transmission type corresponding to the data transmitted between the first terminal device and the second terminal device
  • a resource pool corresponding to data transmission between the first terminal device and the second terminal device
  • the CBR of the resource pool corresponding to the data is transmitted between the first terminal device and the second terminal device.
  • the layer 2 ID is the communication address used by the terminal device for side link communication.
  • the transmission type may be a broadcast type, a unicast type, or a multicast type.
  • the transmission type is a unicast type.
  • first carrier, the second carrier, or the third carrier in the above solution may be one carrier or multiple carriers.
  • the interaction between the first terminal device and the second terminal device is based on the PC5 interface.
  • the first information sent by the first terminal device to the second terminal device may be carried in RRC signaling based on the PC5 interface (PC5-RRC signaling), or sidelink control information (Sidelink Control Information (SCI) or sidelink MAC CE (SL-MAC CE).
  • the first configuration information sent by the second terminal device to the first terminal device may be carried in PC5-RRC signaling, or in SCI, or in MAC CE.
  • the first terminal device is the receiving end of unicast sidelink communication (denoted as Rx UE), and the second terminal device is the sending end of unicast sidelink communication (denoted as Tx UE).
  • the network where the first terminal device is located is called network 2, and the network where the second terminal device is located is called network 1.
  • the carrier is configured by the Tx UE or the network 1 where the Tx UE is located.
  • Step 300 The Tx UE and the Rx UE communicate using the default carrier or the mapped carrier.
  • the default carrier can be defined by the protocol, and both Tx UE and Rx UE know the default carrier.
  • the mapped carrier may be determined based on a first mapping rule.
  • the first mapping rule includes a mapping relationship between third information to available carriers and/or available carrier serial numbers, and the third information includes at least the following: One: the layer 2 ID of Tx UE and/or Rx UE; the transmission configuration (Tx profile) corresponding to the data transmitted between Tx UE and Rx UE; the service type or application type corresponding to the data transmitted between Tx UE and Rx UE; The amount of data corresponding to the data transmitted between Tx UE and Rx UE; the transmission type corresponding to the data transmitted between Tx UE and Rx UE; the QoS flow corresponding to the data transmitted between Tx UE and Rx UE; the transmission between Tx UE and Rx UE The logical channel corresponding to the data; the resource pool corresponding to the data transmitted between Tx UE and Rx UE; the radio bearer corresponding to the data transmitted between Tx UE and Rx UE; the data priority corresponding to
  • the Tx UE obtains the third information and determines the carrier (ie, the mapped carrier) corresponding to the third information based on the first mapping rule.
  • the Rx UE obtains the third information from the Tx UE, and determines the carrier (ie, the mapped carrier) corresponding to the third information based on the first mapping rule.
  • Tx UE and Rx UE will use the default carrier or the carrier or mapping in the default available carrier set.
  • carrier for communication For example: Tx UE or 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, and other PC5-S messages , PC5-RRC message, etc.
  • DCR Direct Communication Request
  • Step 301 Rx UE sends carrier configuration assistance information and/or carrier-related capability information to Tx UE.
  • 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 to be configured by the Rx UE
  • the carrier-related capability information includes the carrier or carrier set supported by the Rx UE's capabilities.
  • the conditions that trigger 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:
  • the first triggering condition refers to: the Rx UE receives the request information sent by the Tx UE, and the request information is used to request the Rx UE to send the carrier configuration assistance information and/or carrier-related capability information to the Tx UE;
  • the second triggering condition refers to: the Rx UE receives the first indication information sent by the Tx UE, and the first indication information is used to indicate that the Tx UE and/or the network 1 where the Tx UE is located supports the side link. road carrier aggregation;
  • the third triggering condition refers to: the Rx UE determines the arrival of a periodic time point;
  • the fourth trigger condition refers to: Rx UE determines that the target event occurs.
  • the trigger corresponding to the third trigger condition may also be called periodic trigger.
  • the trigger corresponding to the fourth trigger condition may also be called target event trigger.
  • the target event includes at least one of the following:
  • Rx The carrier or carrier set recommended for configuration by Rx UE changes
  • Rx UE and Tx UE establish a unicast sidelink
  • Rx The carrier or carrier set used by the UE changes
  • Rx The carrier or carrier set available to the UE changes
  • the link quality of the unicast sidelink between Rx UE and Tx UE changes
  • a conflict occurs on the carrier resources on the unicast sidelink between Rx UE and Tx UE.
  • Rx UE needs to confirm that Tx UE has carrier aggregation capability.
  • Tx UE has carrier aggregation capability
  • Rx UE sends a message to Tx UE.
  • Carrier configuration assistance information and/or carrier-related capability information are examples of carrier-related capability information.
  • the carrier configuration assistance information (i.e., the carrier or carrier set recommended by the Rx UE to be configured) is determined by the Rx UE based on at least one of the following:
  • Rx The carrier or carrier set supported by the UE's capabilities
  • Rx The carrier or carrier set used by the UE
  • Rx Carrier or carrier set available to UE
  • Tx The carrier or carrier set supported by the UE's capabilities
  • Tx Carrier or carrier set used by UE Tx Carrier or carrier set used by UE
  • Tx Carrier or carrier set available to UE Tx Carrier or carrier set available to UE
  • Rx The network configuration of network 2 where the UE is located.
  • the network configuration of network 2 is used to configure the carriers or carrier sets supported by one or more coverage areas of network 2;
  • Rx The network capability of network 2 where the UE is located.
  • the network capability of network 2 is used to determine whether network 2 supports carrier aggregation.
  • 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:
  • Rx The carrier or carrier set used by the UE
  • Rx Carrier or carrier set available to UE
  • Rx The network capability of network 2 where the UE is located.
  • the network capability of network 2 is used to determine whether network 2 supports carrier aggregation.
  • 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.
  • Step 303 Network 1 delivers carrier configuration information to the Tx UE.
  • the carrier configuration information is the first configuration information in the above solution, and is used to configure multiple carriers.
  • Step 304 Tx UE delivers carrier configuration information to Rx UE.
  • 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.
  • the accepted carrier can be understood as the successfully configured carrier.
  • Rejected carriers can be understood as carriers whose configuration failed.
  • the Rx UE accepts all carriers configured by the carrier configuration information, which can be understood as indicating that all carriers configured by the carrier configuration information are successfully configured (or directly understood as that the carrier configuration information is configured successfully).
  • Rx UE rejects all carriers configured by the carrier configuration information, which can be understood as failure to configure all carriers configured by the carrier configuration information (or directly understood as failure to configure the carrier configuration information).
  • the Rx UE accepts the partial carriers configured by the carrier configuration information, which can be understood as the partial carriers configured by the carrier configuration information are successfully configured (or directly understood as the partial carrier configuration information is successfully configured).
  • Rx UE rejects part of the carriers configured by the carrier configuration information, which can be understood as a failure to configure part of the carriers configured by the carrier configuration information (or directly understood as a failure to configure part of the carrier configuration information).
  • the configuration result includes at least one of the following: indication information used to indicate acceptance or rejection of all or part of the carriers configured by the carrier configuration information; carrier information (such as carrier identification) used to indicate acceptance of the carrier; information used to indicate rejection Carrier information (such as carrier identification) of the carrier.
  • Step 306 Rx UE reports the configuration result to Network 2.
  • the configuration result includes at least one of the following: indication information used to indicate acceptance or rejection of all or part of the carriers configured by the carrier configuration information; carrier information (such as carrier identification) used to indicate acceptance of the carrier; information used to indicate rejection Carrier information (such as carrier identification) of the carrier.
  • Step 307 Tx UE reports the configuration result to Network 1.
  • the configuration result includes at least one of the following: indication information used to indicate acceptance or rejection of all or part of the carriers configured by the carrier configuration information; carrier information (such as carrier identification) used to indicate acceptance of the carrier; information used to indicate rejection Carrier information (such as carrier identification) of the carrier.
  • the Tx UE performs at least one of the following operations:
  • Step 308 If all or part of the carrier configuration information is configured successfully, the Tx UE and the Rx UE use the successfully configured carrier for unicast sidelink communication.
  • the Tx UE 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 a mode 2 state, 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.
  • step 306 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 a mode two state, the above step 306 will not be executed.
  • Step 305a Rx UE reports carrier configuration information to Network 2.
  • 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.
  • Step 306a Rx UE sends the configuration result to Tx UE.
  • the first terminal device is the sender of unicast sidelink communication (denoted as Tx UE), and the second terminal device is the receiver of unicast sidelink communication (denoted as Rx UE).
  • the network where the first terminal device is located is called network 1
  • the network where the second terminal device is located is called network 2.
  • the carrier is configured by the Rx UE or the network 2 where the Rx UE is located.
  • Step 400 The Rx UE and the Tx UE communicate using the default carrier or the mapped carrier.
  • the default carrier can be defined by the protocol, and both Rx UE and Tx UE know the default carrier.
  • the mapped carrier may be determined based on a first mapping rule.
  • the first mapping rule includes a mapping relationship between third information to available carriers and/or available carrier serial numbers, and the third information includes at least the following: One: the layer 2 ID of Tx UE and/or Rx UE; the transmission configuration (Tx profile) corresponding to the data transmitted between Tx UE and Rx UE; the service type or application type corresponding to the data transmitted between Tx UE and Rx UE; The amount of data corresponding to the data transmitted between Tx UE and Rx UE; the transmission type corresponding to the data transmitted between Tx UE and Rx UE; the QoS flow corresponding to the data transmitted between Tx UE and Rx UE; the transmission between Tx UE and Rx UE The logical channel corresponding to the data; the resource pool corresponding to the data transmitted between Tx UE and Rx UE; the radio bearer corresponding to the data transmitted between Tx UE and Rx UE; the data priority corresponding to
  • the Tx UE obtains the third information and determines the carrier (ie, the mapped carrier) corresponding to the third information based on the first mapping rule.
  • the Rx UE obtains the third information from the Tx UE, and determines the carrier (ie, the mapped carrier) corresponding to the third information based on the first mapping rule.
  • Rx UE and Tx UE will use the default carrier or the carrier or mapping in the default available carrier set.
  • carrier for communication For example: Rx UE or Tx UE uses the default carrier or the carrier in the default available carrier set or the mapped carrier to send or receive discovery messages, DCR messages, other PC5-S messages, PC5-RRC messages, etc.
  • Step 401 The Tx UE sends carrier configuration assistance information and/or carrier-related capability information to the Rx UE.
  • 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 to be configured by the Tx UE
  • the carrier-related capability information includes the carrier or carrier set supported by the Tx UE's capabilities.
  • the conditions that trigger 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:
  • the first triggering condition refers to: the Tx UE receives the request information sent by the Rx UE, the request information is used to request the Tx UE to send the carrier configuration assistance information and/or carrier-related capability information to the Rx UE;
  • the second triggering condition refers to: the Tx UE receives the first indication information sent by the Rx UE, and the first indication information is used to indicate that the Rx UE and/or the network 2 where the Rx UE is located supports the side link. road carrier aggregation;
  • the third triggering condition refers to: Tx UE determines the arrival of a periodic time point;
  • the fourth trigger condition refers to: Tx UE determines that the target event occurs.
  • the trigger corresponding to the third trigger condition may also be called periodic trigger.
  • the trigger corresponding to the fourth trigger condition may also be called target event trigger.
  • the target event includes at least one of the following:
  • Tx The carrier or carrier set recommended for configuration by Tx UE changes;
  • Tx UE and Rx UE establish unicast sidelink
  • Tx The carrier or carrier set used by the UE changes
  • Tx The carrier or carrier set available to the UE changes
  • the link quality of the unicast sidelink between Tx UE and Rx UE changes
  • a conflict occurs on the carrier resources on the unicast sidelink between Tx UE and Rx UE.
  • Tx UE needs to confirm that Rx UE has carrier aggregation capability.
  • Rx UE has carrier aggregation capability
  • Tx UE sends Rx UE Carrier configuration assistance information and/or carrier-related capability information.
  • the carrier configuration assistance information (i.e., the carrier or carrier set recommended by the Tx UE to be configured) is determined by the Tx UE based on at least one of the following:
  • Tx The carrier or carrier set supported by the UE's capabilities
  • Tx Carrier or carrier set used by UE Tx Carrier or carrier set used by UE
  • Tx Carrier or carrier set available to UE Tx Carrier or carrier set available to UE
  • Rx The carrier or carrier set supported by the UE's capabilities
  • Rx The carrier or carrier set used by the UE
  • Rx Carrier or carrier set available to UE
  • Tx The network configuration of network 1 where the UE is located.
  • the network configuration of network 1 is used to configure the carriers or carrier sets supported by one or more coverage areas of network 1;
  • Tx The network capability of network 1 where the UE is located.
  • the network capability of network 1 is used to determine whether network 1 supports carrier aggregation.
  • 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:
  • Tx Carrier or carrier set used by UE Tx Carrier or carrier set used by UE
  • Tx Carrier or carrier set available to UE Tx Carrier or carrier set available to UE
  • Tx The network capability of network 1 where the UE is located.
  • the network capability of network 1 is used to determine whether network 1 supports carrier aggregation.
  • Step 402 The Rx UE reports the carrier configuration assistance information and/or carrier-related capability information obtained from the Tx UE to the network 2.
  • Step 403 Network 2 sends the carrier configuration information to the Rx UE.
  • the carrier configuration information is the first configuration information in the above solution, and is used to configure multiple carriers.
  • Step 404 Rx UE delivers carrier configuration information to Tx UE.
  • 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.
  • the accepted carrier can be understood as the successfully configured carrier.
  • Rejected carriers can be understood as carriers whose configuration failed.
  • the Tx UE accepts all carriers configured by the carrier configuration information, which can be understood as indicating that all carriers configured by the carrier configuration information are successfully configured (or directly understood as that the carrier configuration information is configured successfully). Tx UE rejects all carriers configured by the carrier configuration information, which can be understood as failure to configure all carriers configured by the carrier configuration information (or directly understood as failure to configure the carrier configuration information).
  • the Tx UE accepts the partial carriers configured by the carrier configuration information, which can be understood as the partial carriers configured by the carrier configuration information are successfully configured (or directly understood as the partial carrier configuration information is successfully configured).
  • Tx UE rejects part of the carriers configured by the carrier configuration information, which can be understood as failure to configure part of the carriers configured by the carrier configuration information (or directly understood as failure to configure part of the carrier configuration information).
  • the configuration result includes at least one of the following: indication information used to indicate acceptance or rejection of all or part of the carriers configured by the carrier configuration information; carrier information (such as carrier identification) used to indicate acceptance of the carrier; information used to indicate rejection Carrier information (such as carrier identification) of the carrier.
  • Step 406 Tx UE reports the configuration result to Network 1.
  • the configuration result includes at least one of the following: indication information used to indicate acceptance or rejection of all or part of the carriers configured by the carrier configuration information; carrier information (such as carrier identification) used to indicate acceptance of the carrier; information used to indicate rejection Carrier information (such as carrier identification) of the carrier.
  • Step 407 Rx UE reports the configuration result to Network 2.
  • the configuration result includes at least one of the following: indication information used to indicate acceptance or rejection of all or part of the carriers configured by the carrier configuration information; carrier information (such as carrier identification) used to indicate acceptance of the carrier; information used to indicate rejection Carrier information (such as carrier identification) of the carrier.
  • the Rx UE performs at least one of the following operations:
  • Step 408 If all or part of the carrier configuration information is successfully configured, the Rx UE and the Tx UE use the successfully configured carrier for unicast sidelink communication.
  • the Rx UE 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 a mode 2 state, the above steps 402, 403 and 407 will not be executed. In this case, after step 401, the Rx UE autonomously determines the carrier configuration information and executes step 404.
  • the above steps 405 and 406 can also be replaced with the following steps:
  • Step 405a Tx UE reports carrier configuration information to Network 1.
  • 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.
  • Step 406a Tx UE sends the configuration result to Rx UE.
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not be used in this application.
  • the implementation of the examples does not constitute any limitations.
  • the terms “downlink”, “uplink” and “sidelink” are used to indicate the transmission direction of signals or data, where “downlink” is used to indicate that the transmission direction of signals or data is from the station.
  • uplink is used to indicate that the transmission direction of the signal or data is the second direction from the user equipment of the cell to the site
  • sidelink is used to indicate that the transmission direction of the signal or data is A third direction sent from User Device 1 to User Device 2.
  • downlink signal indicates that the transmission direction of the signal is the first direction.
  • the term “and/or” is only an association relationship describing 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 article generally indicates that the related objects are an "or" relationship.
  • FIG. 5 is a schematic structural diagram of a carrier configuration device provided by an embodiment of the present application. It is applied to the first terminal equipment. As shown in Figure 5, the carrier configuration device includes:
  • Sending unit 501 configured to send first information to a second terminal device, where the first information is used for the second terminal device or the second network configuration carrier where the second terminal device is located;
  • Receiving unit 502 configured to receive first configuration information sent by the second terminal device, where the first configuration information is used to configure multiple carriers, at least some of the multiple carriers are used for the first terminal Unicast sidelink communication is performed between the device and the second terminal device.
  • the first information includes a carrier or a set of carriers recommended to be configured by the first terminal device and/or a carrier or set of carriers supported by the capabilities of the first terminal device.
  • the carrier or carrier set recommended to be configured by the first terminal device is determined based on at least one of the following:
  • the carrier or set of carriers supported by the capability of the first terminal device
  • the carrier or set of carriers used by the first terminal device The carrier or set of carriers used by the first terminal device;
  • the carrier or set of carriers available to the first terminal device are the carrier or set of carriers available to the first terminal device
  • the carrier or set of carriers used by the second terminal device is not limited to
  • the carrier or set of carriers available to the second terminal device are the carrier or set of carriers available to the second terminal device.
  • the link quality of the unicast sidelink between the first terminal device and the second terminal device is the link quality of the unicast sidelink between the first terminal device and the second terminal device
  • the network configuration of the first network where the first terminal device is located is used to configure carriers or carrier sets 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 is used to determine whether the first network supports carrier aggregation.
  • the carrier or carrier set supported by the capability of the first terminal device is determined based on at least one of the following:
  • the carrier or set of carriers used by the first terminal device The carrier or set of carriers used by the first terminal device;
  • the carrier or set of carriers available to the first terminal device are the carrier or set of carriers available to the first terminal device
  • the network capability of the first network where the first terminal device is located is used to determine whether the first network supports carrier aggregation.
  • 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.
  • the triggering condition includes at least one of the following:
  • a first triggering condition refers to: the first terminal device receives request information sent by the second terminal device, and the request information is used to request the first terminal device to send a request to the second terminal device.
  • the terminal device sends the first information;
  • the second triggering condition refers to: the first terminal device receives the first indication information sent by the second terminal device, and the first indication information is used to instruct the second terminal device and /or the second network where the second terminal device is located supports sidelink carrier aggregation;
  • a third triggering condition refers to: the arrival of a periodic time point determined by the first terminal device;
  • the fourth trigger condition refers to: the first terminal device determines that a target event occurs.
  • the target event includes at least one of the following:
  • the carrier or carrier set recommended to be configured 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 equipment changes
  • the carrier or 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.
  • the first information 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 configured to receive the first configuration information from the second network forwarded by the second terminal device.
  • the device further includes: a decision-making unit 503, configured to accept or reject all or part of the carriers configured by the first configuration information; and the sending unit 501, configured to send a notification to the second terminal
  • the device sends a configuration result corresponding to the first configuration information, where the configuration result includes at least one of the following:
  • the second indication information is used to indicate acceptance or rejection of all carriers or part of the carriers configured by the first configuration information
  • First carrier information the first carrier information is used to indicate an accepted carrier
  • Second carrier information the second carrier information is used to indicate the rejected carrier.
  • the sending unit 501 is configured to send the configuration result to the first network where it is located.
  • the sending unit 501 is used to send the first configuration information to the first network where it is located, and the receiving unit 502 is used to receive the first configuration sent by the first network.
  • the configuration result corresponding to the information, the configuration result includes at least one of the following:
  • the second indication information is used to indicate acceptance or rejection of all carriers or part of the carriers configured by the first configuration information
  • First carrier information the first carrier information is used to indicate an accepted carrier
  • Second carrier information the second carrier information is used to indicate the rejected carrier.
  • the sending unit 501 is configured to send the configuration result to the second terminal device.
  • the accepted carrier indicated by the first carrier information is used for the Unicast sidelink communication is performed between the first terminal device and the second terminal device; or, when the second indication information is used to indicate rejecting some of the carriers configured by the first configuration information, Among all carriers configured in the first configuration information, carriers other than the rejected carrier indicated by the second carrier information are used for unicast side communication between the first terminal device and the second terminal device. Line link communication.
  • the first terminal device and the second terminal device use the first carrier or The second carrier communicates, 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 the first terminal device to receive the first Configuration information for carriers that have been successfully configured before.
  • a first terminal device is used between the first terminal device and the second terminal device.
  • 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
  • the second carrier is the first terminal.
  • the carrier is a carrier that has been configured successfully before the device receives the first configuration information
  • the third carrier is a carrier among some of the carriers that are successfully configured among the plurality of carriers.
  • the first mapping rule includes a mapping relationship between third information to available carriers and/or available carrier serial numbers, and the third information includes at least one of the following:
  • the layer 2 ID of the first terminal device and/or the second terminal device is the layer 2 ID of the first terminal device and/or the second terminal device
  • the transmission configuration (Tx profile) corresponding to the data transmitted between the first terminal device and the second terminal device;
  • the amount of data corresponding to the data transmitted between the first terminal device and the second terminal device is the amount of data corresponding to the data transmitted between the first terminal device and the second terminal device
  • the transmission type corresponding to the data transmitted between the first terminal device and the second terminal device
  • a resource pool corresponding to data transmission between the first terminal device and the second terminal device
  • the CBR of the resource pool corresponding to the data is transmitted between the first terminal device and the second terminal device.
  • the first terminal device is a sending end of unicast sidelink communication
  • the second terminal device is a receiving end of unicast sidelink communication
  • the first terminal device The second terminal device is a receiving end of unicast side link communication
  • the second terminal device is a sending end of unicast side link communication.
  • Figure 6 is a schematic diagram 2 of the structure of a carrier configuration device provided by an embodiment of the present application. It is applied to the second terminal equipment.
  • the carrier configuration device includes:
  • the receiving unit 601 is configured to receive the first information sent by the first terminal device, where the first information is used for the second terminal device or the second network configuration carrier where the second terminal device is located;
  • Sending unit 602 configured to send first configuration information to the first terminal device, where the first configuration information is used to configure multiple carriers, and at least part of the multiple carriers are used for the first terminal device. Perform unicast sidelink communication with the second terminal device.
  • the first information includes a carrier or a set of carriers recommended to be configured by the first terminal device and/or a carrier or set of carriers supported by the capabilities of the first terminal device.
  • the carrier or carrier set recommended to be configured by the first terminal device is determined based on at least one of the following:
  • the carrier or set of carriers supported by the capability of the first terminal device
  • the carrier or set of carriers used by the first terminal device The carrier or set of carriers used by the first terminal device;
  • the carrier or set of carriers available to the first terminal device are the carrier or set of carriers available to the first terminal device
  • the carrier or set of carriers used by the second terminal device is not limited to
  • the carrier or set of carriers available to the second terminal device are the carrier or set of carriers available to the second terminal device.
  • the link quality of the unicast sidelink between the first terminal device and the second terminal device is the link quality of the unicast sidelink between the first terminal device and the second terminal device
  • the network configuration of the first network where the first terminal device is located is used to configure carriers or carrier sets 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 is used to determine whether the first network supports carrier aggregation.
  • the carrier or carrier set supported by the capability of the first terminal device is determined based on at least one of the following:
  • the carrier or set of carriers used by the first terminal device The carrier or set of carriers used by the first terminal device;
  • the carrier or set of carriers available to the first terminal device are the carrier or set of carriers available to the first terminal device
  • the network capability of the first network where the first terminal device is located is used to determine whether the first network supports carrier aggregation.
  • the sending unit 602 when the first information is used to configure a carrier in the second network where the second terminal device is located, the sending unit 602 is configured to forward the first information to the second network. ; The receiving unit 601 is configured to receive the first configuration information sent by the second network.
  • 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:
  • 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 the first carrier information is used to indicate an accepted carrier
  • Second carrier information the second carrier information is used to indicate the rejected carrier.
  • the sending unit 602 is configured to send the configuration result to the second network where it is located.
  • the apparatus further includes: a processing unit configured to perform at least one of the following operations if the second indication information is used to indicate rejecting all or part of the carriers configured by the first configuration information:
  • the accepted carrier indicated by the first carrier information is used for the Unicast sidelink communication is performed between the first terminal device and the second terminal device; or, when the second indication information is used to indicate rejecting some of the carriers configured by the first configuration information, Among all carriers configured in the first configuration information, carriers other than the rejected carrier indicated by the second carrier information are used for unicast side communication between the first terminal device and the second terminal device. Line link communication.
  • the first carrier or the first terminal device is used between the second terminal device and the first terminal device.
  • the second carrier communicates, 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 the first terminal device to receive the first Configuration information for carriers that have been successfully configured before.
  • a first terminal device is used between the second terminal device and the first terminal device.
  • 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 the first terminal.
  • the carrier is a carrier that has been configured successfully before the device receives the first configuration information, and the third carrier is a carrier among some of the carriers that are successfully configured among the plurality of carriers.
  • the first mapping rule includes a mapping relationship between third information to available carriers and/or available carrier serial numbers, and the third information includes at least one of the following:
  • the layer 2 ID of the first terminal device and/or the second terminal device is the layer 2 ID of the first terminal device and/or the second terminal device
  • the amount of data corresponding to the data transmitted between the first terminal device and the second terminal device is the amount of data corresponding to the data transmitted between the first terminal device and the second terminal device
  • the transmission type corresponding to the data transmitted between the first terminal device and the second terminal device
  • a resource pool corresponding to data transmission between the first terminal device and the second terminal device
  • the CBR of the resource pool corresponding to the data is transmitted between the first terminal device and the second terminal device.
  • the first terminal device is a sending end of unicast sidelink communication
  • the second terminal device is a receiving end of unicast sidelink communication
  • the first terminal device The second terminal device is a receiving end of unicast side link communication
  • the second terminal device is a sending end of unicast side link communication.
  • Figure 7 is a schematic structural diagram of a communication device 700 provided by an embodiment of the present application.
  • the communication device may be a first terminal device or a second terminal device.
  • the communication device 700 shown in Figure 7 includes a processor 710.
  • the processor 710 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the communication device 700 may further include a memory 720 .
  • the processor 710 can call and run the computer program from the memory 720 to implement the method in the embodiment of the present application.
  • the memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .
  • the communication device 700 can also include a transceiver 730, and the processor 710 can control the transceiver 730 to communicate with other devices. Specifically, it can send information or data to other devices, or receive other devices. Information or data sent by the device.
  • 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.
  • the communication device 700 may specifically be the first terminal device in the embodiment of the present application, and the communication device 700 may implement the corresponding processes implemented by the first terminal device in the various methods of the embodiment of the present application. For simplicity, in This will not be described again.
  • the communication device 700 can be specifically the second terminal device in the embodiment of the present application, and the communication device 700 can implement the corresponding processes implemented by the second terminal device in the various methods of the embodiment of the present application. For simplicity, in This will not be described again.
  • FIG 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.
  • the processor 810 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the chip 800 may also include a memory 820 .
  • the processor 810 can call and run the computer program from the memory 820 to implement the method in the embodiment of the present application.
  • the memory 820 may be a separate device independent of the processor 810 , or may be integrated into the processor 810 .
  • the chip 800 may also include an input interface 830.
  • the processor 810 can control the input interface 830 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.
  • the chip 800 may also include an output interface 840.
  • the processor 810 can control the output interface 840 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.
  • 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 the various methods of the embodiment of the present application. For the sake of brevity, they will not be described here. Repeat.
  • the chip can be applied to the second terminal device in the embodiment of the present application, and the chip can implement 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 described here. Repeat.
  • chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.
  • Figure 9 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application. As shown in FIG. 9 , the communication system 900 includes a first terminal device 910 and a second terminal device 920 .
  • the first terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method
  • the second terminal device 920 can be used to implement the corresponding functions implemented by the first terminal device in the above method.
  • the first terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method
  • the second terminal device 920 can be used to implement the corresponding functions implemented by the first terminal device in the above method.
  • the processor in the embodiment of the present application may be an integrated circuit chip and has signal processing capabilities.
  • each step of the above method embodiment can be completed through an integrated logic circuit of hardware in the processor or instructions in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available processors.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • the steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field.
  • 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.
  • non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory may be Random Access Memory (RAM), which is used as an external cache.
  • RAM Random Access Memory
  • RAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • Synchlink DRAM SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiment of the present application can also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, memories in embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.
  • Embodiments of the present application also provide a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium can be applied to the first terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the first terminal device in the various methods of the embodiment of the present application, in order to It’s concise and I won’t go into details here.
  • the computer-readable storage medium can be applied to the second terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the second terminal device in the various methods of the embodiment of the present application, in order to It’s concise and I won’t go into details here.
  • An embodiment of the present application also provides a computer program product, including computer program instructions.
  • the computer program product can be applied to the first terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the first terminal device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding processes implemented by the first terminal device in each method of the embodiment of the present application.
  • the computer program product can be applied to the second terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the second terminal device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding processes implemented by the second terminal device in each method of the embodiment of the present application.
  • An embodiment of the present application also provides a computer program.
  • the computer program can be applied to the first terminal device in the embodiment of the present application.
  • the computer program When the computer program is run on the computer, it causes the computer to execute the corresponding steps implemented by the first terminal device in each method of the embodiment of the present application. The process, for the sake of brevity, will not be repeated here.
  • the computer program can be applied to the second terminal device in the embodiment of the present application.
  • the computer program When the computer program is run on the computer, the computer performs the corresponding steps implemented by the second terminal device in each method of the embodiment of the present application. The process, for the sake of brevity, will not be repeated here.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • 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.
  • the technical solution of the present application is essentially or the part that contributes to the existing technology 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, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供一种载波配置方法及装置、终端设备，该方法包括：第一终端设备向第二终端设备发送第一信息，所述第一信息用于所述第二终端设备或者所述第二终端设备所在的第二网络配置载波；所述第一终端设备接收所述第二终端设备发送的第一配置信息，所述第一配置信息用于配置多个载波，所述多个载波中的至少部分载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。

Description

一种载波配置方法及装置、终端设备 技术领域
本申请实施例涉及移动通信技术领域，具体涉及一种载波配置方法及装置、终端设备。
背景技术
在侧行链路(Sidelink，SL)通信中，不仅可以支持广播方式的通信，还可以支持单播方式和组播方式的通信。对于单播方式的侧行链路通信(以下简称为单播侧行链路通信)来说，通信对应的接收端只有一个终端设备。为了扩展带宽，考虑将载波聚合技术引入到侧行链路通信中，如何支持单播侧行链路通信中的载波聚合需要完善。
发明内容
本申请实施例提供一种载波配置方法及装置、终端设备、芯片、计算机可读存储介质、计算机程序产品、计算机程序。
本申请实施例提供的载波配置方法，包括：
第一终端设备向第二终端设备发送第一信息，所述第一信息用于所述第二终端设备或者所述第二终端设备所在的第二网络配置载波；
所述第一终端设备接收所述第二终端设备发送的第一配置信息，所述第一配置信息用于配置多个载波，所述多个载波中的至少部分载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
本申请实施例提供的载波配置方法，包括：
第二终端设备接收第一终端设备发送的第一信息，所述第一信息用于所述第二终端设备或者所述第二终端设备所在的第二网络配置载波；
所述第二终端设备向所述第一终端设备发送第一配置信息，所述第一配置信息用于配置多个载波，所述多个载波中的至少部分载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
本申请实施例提供的载波配置装置，应用于第一终端设备，所述方法包括：
发送单元，用于向第二终端设备发送第一信息，所述第一信息用于所述第二终端设备或者所述第二终端设备所在的第二网络配置载波；
接收单元，用于接收所述第二终端设备发送的第一配置信息，所述第一配置信息用于配置多个载波，所述多个载波中的至少部分载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
本申请实施例提供的载波配置装置，应用于第二终端设备，所述方法包括：
接收单元，用于接收第一终端设备发送的第一信息，所述第一信息用于所述第二终端设备或者所述第二终端设备所在的第二网络配置载波；
发送单元，用于向所述第一终端设备发送第一配置信息，所述第一配置信息用于配置多个载波，所述多个载波中的至少部分载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
本申请实施例提供的终端设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述的载波配置方法。
本申请实施例提供的芯片，用于实现上述的载波配置方法。
具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行上述的载波配置方法。
本申请实施例提供的计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述的载波配置方法。
本申请实施例提供的计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机 执行上述的载波配置方法。
本申请实施例提供的计算机程序，当其在计算机上运行时，使得计算机执行上述的载波配置方法。
通过上述技术方案，第一终端设备向第二终端设备提供第一信息，来辅助第二终端设备或者第二终端设备所在的第二网络为第一终端设备和第二终端设备之间的单播侧行链路通信配置多个载波，从而支持了单播侧行链路通信中的载波聚合。这种载波配置方式由于结合了第一终端设备提供的第一信息作为辅助，因而所配置的载波具有更高的可靠性，提升了单播侧行链路通信的性能。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1-1是终端设备处于模式一的示意图；
图1-2是终端设备处于模式二的示意图；
图2是本申请实施例提供的载波配置方法的流程示意图一；
图3是本申请实施例提供的载波配置方法的流程示意图二；
图4是本申请实施例提供的载波配置方法的流程示意图三；
图5是本申请实施例提供的载波配置装置的结构组成示意图一；
图6是本申请实施例提供的载波配置装置的结构组成示意图二；
图7是本申请实施例提供的一种通信设备示意性结构图；
图8是本申请实施例的芯片的示意性结构图；
图9是本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
为便于理解本申请实施例的技术方案，以下对本申请实施例的相关技术进行说明，以下相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合，其均属于本申请实施例的保护范围。
设备到设备(Device to Device，D2D)通信
在长期演进(Long Term Evolution，LTE)系统中，引入了D2D通信技术。D2D通信基于侧行链路传输技术，与传统的蜂窝系统中通信数据通过基站接收或者发送的方式不同，车联网系统采用D2D通信的方式(即设备到设备直接通信的方式)，因此具有更高的频谱效率以及更低的传输时延。对于D2D通信，第三代合作伙伴计划(Third Generation Partnership Project，3GPP)定义了两种传输模式：模式一和模式二。以下对模式一和模式二进行描述。
模式一：如图1-1所示，终端设备的传输资源是由基站分配的，终端设备根据基站分配的资源在侧行链路上进行数据的发送；基站可以为终端设备分配单次传输的资源，也可以为终端设备分配半静态传输的资源。
模式二：如图1-2所示，终端设备在资源池中选取一个资源进行数据的发送。具体地，终端设备可以通过侦听的方式在资源池中选取传输资源，或者通过随机选取的方式在资源池中选取传输资源。
在3GPP中，D2D通信分成了以下不同的阶段进行研究：
近距离服务(Proximity based Service，ProSe)：设备到设备的通信是针对ProSe的场景进行了研究，其主要针对公共安全类的业务。在ProSe中，通过配置资源池在时域上的位置，例如资源池在时域上非连续，达到终端设备在侧行链路上非连续发送/接收的目的，从而达到省电的效果。
车辆到其他设备(Vehicle to Everything，V2X)：设备到设备的通信是针对车辆到其他设备的通信场景进行了研究，其主要面向相对高速移动的车车、车人通信的业务。在V2X中，由于车载系统具有持续的供电，因此功率效率不是主要问题，而数据传输的时延是主要问题，因此在系统设计上要求终端设备进行连续的发送和接收。
进一步增强D2D(Further Enhancement Device to Device，FeD2D)：设备到设备的通信是针对可穿戴设备通过手机接入网络的场景进行了研究，其主要面向是低移动速度以及低功率接入的场景。在FeD2D中，在预研阶段3GPP结论为基站可以通过一个中继终端设备去配置远程终端设备的DRX参数。
随着移动通信系统的演进，LTE V2X也演进成了新无线(New Radio，NR)V2X。NR V2X需要支持自动驾驶，因此对车辆之间数据交互提出了更高的要求，如更高的吞吐量、更低的时延、更高的可靠性、更大的覆盖范围、更灵活的资源分配等。NR V2X在LTE V2X的基础上，不局限于广播场景，而是进一步拓展到了单播和组播的场景，在这些场景下研究V2X的应用。对于单播传输方式，其接收端只有一个终端设备。对于组播传输方式，其接收端是一个通信组内的所有终端设备，或者是在一定传输距离内的所有终端设备。对于广播传输方式，其接收端是任意一个终端设备。在NR V2X系统中，引入了多种传输模式，包括模式一和模式二，其中，模式一是网络设备为终端设备分配传输资源，模式二是终端设备选取传输资源。更进一步，终端设备可能处在一个混合的模式下，具体地，既可以使用模式一进行资源的获取，又同时可以使用模式二进行资源的获取。此外，在NR V2X系统中，引入了侧行反馈机制，也即基于反馈的混合自动重传请求(Hybrid Automatic Repeat reQuest，HARQ)重传，侧行反馈机制不限于应用于单播场景，也可以应用于组播场景。
载波聚合(Carrier Aggregation，CA)
CA是一种带宽扩展技术，可以将多个成员载波(Component Carrier，CC)聚合在一起，由一个终端设备或网络设备同时接收或发送。按照聚合的载波的范围来划分，CA可以分为频带内CA(Intra-band CA)和跨频带CA(Inter-band CA)。Intra-band CA的一个主要用途是用于小区载波带宽大于终端设备的单个载波带宽能力的场景，这种情况下，终端设备可以用CA来实现在“宽载波”(wide carrier)中的操作。例如基站支持300MHz的载波，而终端设备最大支持100MHz的载波，终端设备可以用CA实现大于100MHz的宽带操作，聚合的载波可以是相邻的载波，也可以是不相邻的载波。
当终端设备和网络设备使用CA进行通信时，可能会同时配置主小区(PCell)和辅小区(SCell)。针对主小区和辅主小区设计了波束失败恢复机制，其主要功能模块(或称为主要步骤)包括：波束失败检测(Beam Failure Detection，BFD)；新波束选择(New Beam Identification，NBI)；波束失败恢复请求(Beam Failure Recovery ReQest，BFRQ)；网络侧响应。具体地，终端设备对下行发送波束进行测量，从而判断下行发送波束对应的链路质量。如果对应的链路质量很差，则认为下行波束发生波束失败。终端设备还会对一组备选波束进行测量，从中选择满足一定门限的波束作为新波束。然后终端设备通过波束失败恢复请求流程，通知网络发生了波束失败，并且上报新波束。网络收到终端设备发送的波束失败恢复请求后，知道终端设备发生了波束失败，选择从新波束上发送物理下行控制信道(Physical Downlink Control Channel，PDCCH)，终端设备在新波束上收到网络发送的PDCCH则认为正确接收了网络侧的响应。至此，波束失败恢复流程成功完成。
在LTE V2X中，也引入了CA技术。LTE V2X中的载波选择由以下机制完成：上层配置有业务类型到载波的映射关系，如此，针对某类型的业务，上层指示给接入(Access Stotum，AS)层可用的载波或载波集合；进一步，AS层配置有每一个逻辑信道可用的载波或载波集合及配置有每个资源池中针对数据优先级的信道忙碌比(Channel Busy Rate，CBR)门限值。终端设备测量资源池中的CBR值，并与数据优先级所对应的CBR门限值相比较，若测量的CBR值低于CBR门限值，则认为资源池对应的载波可用。
NR SL也有需求引入载波聚合技术。相比较LTE V2X，NR SL引入载波聚合技术需要额外考虑的问题是NR V2X支持单播通信，如何支持单播侧行链路通信中的载波聚合需要完善。为此，提出了本申请实施例的以下技术方案。
为便于理解本申请实施例的技术方案，以下通过具体实施例详述本申请的技术方案。以上相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合，其均属于本申请实施例的保护范围。本申请实施例包括以下内容中的至少部分内容。
图2是本申请实施例提供的载波配置方法的流程示意图，如图2所示，所述载波配置方法包括以下步骤：
步骤201：第一终端设备向第二终端设备发送第一信息。
步骤202：第二终端设备接收第一终端设备发送的第一信息，所述第一信息用于所述第二终端设备或者所述第二终端设备所在的第二网络配置载波。
在一些实施方式中，所述第一终端设备为单播侧行链路通信的发送端，所述第二终端设备为单 播侧行链路通信的接收端。在另一些实施方式中，所述第一终端设备为单播侧行链路通信的接收端，所述第二终端设备为单播侧行链路通信的发送端。
这里，对于单播侧行链路通信的发送端来说，发送端在单播侧行链路上发送数据；对于单播侧行链路通信的接收端来说，接收端在单播侧行链路上接收数据。
本申请实施例中，所述第一终端设备与所述第二终端设备之间的单播侧行链路通信支持载波聚合，即通过聚合的载波在单播侧行链路上进行通信。为了实现单播侧行链路上的载波聚合，需要进行相应的载波配置。具体地，所述第一终端设备向第二终端设备发送第一信息，第二终端设备接收第一终端设备发送的第一信息，所述第一信息用于所述第二终端设备或者所述第二终端设备所在的第二网络配置载波。
在一些实施方式中，所述第一信息包括所述第一终端设备建议配置的载波或载波集合和/或所述第一终端设备的能力支持的载波或载波集合。这里，所述第一终端设备建议配置的载波或载波集合对应的信息也可以称为载波配置协助信息，本申请对此不做限定。所述第一终端设备的能力支持的载波或载波集合对应的信息也可以称为载波相关能力信息，本申请对此不做限定。
在一些实施方式中，所述第一终端设备建议配置的载波或载波集合基于以下至少之一确定：
所述第一终端设备的能力支持的载波或载波集合；
所述第一终端设备已用的载波或载波集合；
所述第一终端设备可用的载波或载波集合；
所述第二终端设备的能力支持的载波或载波集合；
所述第二终端设备已用的载波或载波集合；
所述第二终端设备可用的载波或载波集合；
所述第一终端设备与所述第二终端设备之间的单播侧行链路通信的通信信息；
所述第一终端设备与所述第二终端设备之间的单播侧行链路的链路质量；
所述第一终端设备所在的第一网络的网络配置，所述第一网络的网络配置用于配置所述第一网络的一个或多个覆盖范围所支持的载波或载波集合；
所述第一终端设备所在的第一网络的网络能力，所述第一网络的网络能力用于确定所述第一网络是否支持载波聚合。
在一些实施方式中，所述第一终端设备的能力支持的载波或载波集合基于以下至少之一确定：
所述第一终端设备已用的载波或载波集合；
所述第一终端设备可用的载波或载波集合；
所述第一终端设备所在的第一网络的网络能力，所述第一网络的网络能力用于确定所述第一网络是否支持载波聚合。
上述方案中，所述第一终端设备已用的载波或载波集合是指：所述第一终端设备的单播侧行链路以外的其他侧行链路和/或上下行链路上的载波或载波集合。
上述方案中，所述第一终端设备可用的载波或载波集合是指：所述第一终端设备的能力支持的载波或载波集合去除所述第一终端设备已用的载波或载波集合。
上述方案中，所述第二终端设备已用的载波或载波集合是指：所述第二终端设备的单播侧行链路以外的其他侧行链路和/或上下行链路上的载波或载波集合。
上述方案中，所述第二终端设备可用的载波或载波集合是指：所述第二终端设备的能力支持的载波或载波集合去除所述第二终端设备已用的载波或载波集合。
上述方案中，所述第一终端设备可以但不局限于通过以下方式获取所述第二终端设备的相关信息(即所述第二终端设备的能力支持的载波或载波集合、所述第二终端设备已用的载波或载波集合以及所述第二终端设备可用的载波或载波集合中的至少之一)：
方式1-1：所述第一终端设备向所述第二终端设备发送请求信息，所述请求信息用于请求所述第二终端设备报告所述第二终端设备的相关信息；所述第二终端设备接收到请求信息后，向所述第一终端设备报告所述第二终端设备的相关信息，所述第一终端设备接收所述第二终端设备发送的所述第二终端设备的相关信息。
方式1-2：所述第一终端设备接收所述第二终端设备主动发送的所述第二终端设备的相关信息。
上述方案中，所述第一终端设备可以但不局限于通过以下方式获取所述第一终端设备与所述第二终端设备之间的单播侧行链路通信的通信信息：
方式2-1：所述第一终端设备为单播侧行链路通信的发送端的情况下，所述第一终端设备自然就知道所述第一终端设备与所述第二终端设备之间的单播侧行链路通信的通信信息。
方式2-2：所述第一终端设备为单播侧行链路通信的接收端的情况下，所述第一终端设备接收所述第二终端设备发送的单播侧行链路通信的通信信息。
在一些实施方式中，所述单播侧行链路通信的通信信息包括通信相关的以下至少一种信息：数据量、数据类型、逻辑信道标识。
上述方案中，所述第一终端设备可以但不局限于通过以下方式获取所述第一终端设备与所述第二终端设备之间的单播侧行链路的链路质量：
方式3-1：所述第一终端设备测量所述第二终端设备发送的参考信号，基于所述参考信号的测量结果确定所述第一终端设备与所述第二终端设备之间的单播侧行链路的链路质量。
方式3-2：所述第二终端设备测量所述第一终端设备发送的参考信号，将所述参考信号的测量结果上报给所述第一终端设备，从而所述第一终端设备获取所述第一终端设备与所述第二终端设备之间的单播侧行链路的链路质量。
在一些实施方式中，所述参考信号的测量结果可以是参考信号的参考信号接收功率(Reference Signal Receiving Power，RSRP)测量值、参考信号接收质量(Reference Signal Received Quality，RSRQ)等。
上述方案中，所述第一终端设备可以但不局限于通过以下方式获取所述第一终端设备所在的第一网络的网络配置和/或网络能力：
方式4-1)所述第一终端设备接收所述第一网络发送的系统广播消息，所述系统广播消息携带所述第一网络的网络配置和/或网络能力；所述第一终端设备从所述系统广播消息中获取所述第一网络的网络配置和/或网络能力。
方式4-2)所述第一终端设备向所述第一网络发送请求信息，所述请求信息用于请求所述第一网络下发所述第一网络的网络配置和/或网络能力；所述第一终端设备接收所述第一网络下发的所述第一网络的网络配置和/或网络能力。
在一些实施方式中，所述第一网络的网络配置用于配置所述第一网络的一个或多个覆盖范围所支持的载波或载波集合。所述第一网络的网络能力用于确定所述第一网络是否支持载波聚合。这里，所述第一网络的网络能力可以是一个能力信息或者也可以是一个网络版本信息，所述能力信息显式指示所述第一网络是否支持载波聚合，所述网络版本信息隐式指示所述第一网络是否支持载波聚合。
需要说明的是，所述第一终端设备获取所述第一网络的网络配置和/或网络能力的前提条件包括以下至少之一：所述第一终端设备在所述第一网络的覆盖范围内；所述第一终端设备处于模式一的状态；所述第一终端设备处于连接态。
本申请实施例中，所述第一终端设备在确定触发条件满足的情况下，向第二终端设备发送第一信息。
在一些实施方式中，所述触发条件包括以下至少之一：
第一触发条件，所述第一触发条件指：所述第一终端设备接收到所述第二终端设备发送的请求信息，所述请求信息用于请求所述第一终端设备向所述第二终端设备发送第一信息；
第二触发条件，所述第二触发条件指：所述第一终端设备接收到所述第二终端设备发送的第一指示信息，所述第一指示信息用于指示所述第二终端设备和/或所述第二终端设备所在的第二网络支持侧行链路载波聚合；
第三触发条件，所述第三触发条件指：所述第一终端设备确定周期性的时间点到达；
第四触发条件，所述第四触发条件指：所述第一终端设备确定目标事件发生。
这里，作为一些实现方式，所述目标事件包括以下至少之一：
所述第一终端设备建议配置的载波或载波集合发生变化；
所述第一终端设备与所述第二终端设备建立单播侧行链路；
所述第一终端设备已用的载波或载波集合发生变化；
所述第一终端设备可用的载波或载波集合发生变化；
所述第一终端设备与所述第二终端设备之间的单播侧行链路的链路质量发生变化；
所述第一终端设备与所述第二终端设备之间的单播侧行链路上的载波资源上发生冲突。
在一些实施方式中，在所述第一配置信息所配置的多个载波中的全部载波或者部分载波配置成功之前，所述第一终端设备和所述第二终端设备之间使用第一载波或第二载波进行通信，所述第一载波为默认的载波或者默认可用载波集合中的载波或者基于第一映射规则确定的载波，所述第二载波为所述第一终端设备接收所述第一配置信息之前已经配置成功的载波。这里，可选地，所述第一映射规则包括第三信息到可用载波和/或可用载波序号的映射关系，所述第三信息包括以下至少之一：
所述第一终端设备和/或所述第二终端设备的层二ID；
所述第一终端设备和所述第二终端设备之间传输数据对应的发射配置(Tx profile)；
所述第一终端设备与所述第二终端设备之间传输数据对应的服务类型或应用类型；
所述第一终端设备与所述第二终端设备之间传输数据对应的数据量；
所述第一终端设备与所述第二终端设备之间传输数据对应的传输类型；
所述第一终端设备与所述第二终端设备之间传输数据对应的QoS流；
所述第一终端设备与所述第二终端设备之间传输数据对应的逻辑信道；
所述第一终端设备与所述第二终端设备之间传输数据对应的资源池；
所述第一终端设备与所述第二终端设备之间传输数据对应的无线承载；
所述第一终端设备与所述第二终端设备之间传输数据对应的数据优先级；
所述第一终端设备与所述第二终端设备之间传输数据对应的资源池的拥塞程度(CBR)。
这里，层二ID即为终端设备进行侧行链路通信时所使用的通信地址。
这里，传输类型可以是广播类型、或者单播类型、或者组播类型。对于本申请实施例的方案来说，所述传输类型为单播类型。
步骤203：所述第二终端设备向所述第一终端设备发送第一配置信息。
步骤204：所述第一终端设备接收所述第二终端设备发送的第一配置信息，所述第一配置信息用于配置多个载波，所述多个载波中的至少部分载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
本申请实施例中，所述第一信息用于所述第二终端设备或者所述第二终端设备所在的第二网络配置载波。以下分情况对其进行说明。
方案1-1：所述第一信息用于所述第二终端设备配置载波。
方案1-1可以但不局限于适用于以下场景：所述第二终端设备位于第二网络覆盖范围外；所述第二终端设备处于非连接态；所述第二终端设备处于模式二的状态。
所述第二终端设备接收第一终端设备发送的第一信息之后，根据所述第一信息配置载波从而生成第一配置信息；所述第二终端设备向所述第一终端设备发送第一配置信息，所述第一终端设备接收所述第二终端设备发送的第一配置信息，所述第一配置信息用于配置多个载波。
当然，方案1-1还可以适用于以下场景：所述第一终端设备位于第一网络覆盖范围内；所述第一终端设备处于连接态；所述第一终端设备处于模式一的状态。
方案1-2：所述第一信息用于所述第二终端设备所在的第二网络配置载波。
方案1-2适用于以下场景：所述第二终端设备位于第二网络覆盖范围内；所述第二终端设备处于连接态；所述第二终端设备处于模式一的状态。
所述第二终端设备接收第一终端设备发送的第一信息之后，所述第二终端设备向所述第二网络转发所述第一信息。这里，所述第一信息会由所述第二终端设备转发给所述第二网络，所述第二网络根据所述第一信息配置载波从而生成第一配置信息；所述第二终端设备接收所述第二网络发送的所述第一配置信息；所述第二终端设备向所述第一终端设备发送第一配置信息，所述第一终端设备接收所述第二终端设备转发的来自所述第二网络的第一配置信息，所述第一配置信息用于配置多个载波。
本申请实施例中，所述第一终端设备接收所述第二终端设备发送的第一配置信息之后，由所述第一终端设备或者所述第一终端设备所在的第一网络来决定接受或拒绝所述第一配置信息所配置的全部载波或者部分载波。以下分情况对其进行说明。
方案2-1：由所述第一终端设备来决定接受或拒绝所述第一配置信息所配置的全部载波或者部分载波。
方案2-1可以但不局限于适用于以下场景：所述第一终端设备位于第一网络覆盖范围外；所述第一终端设备处于非连接态；所述第一终端设备处于模式二的状态。
所述第一终端设备接收所述第二终端设备发送的第一配置信息之后，所述第一终端设备接受或拒绝所述第一配置信息所配置的全部载波或者部分载波，向所述第二终端设备发送所述第一配置信息对应的配置结果，所述配置结果包括以下至少之一：
第二指示信息，所述第二指示信息用于指示接受或拒绝所述第一配置信息所配置的全部载波或者部分载波；
第一载波信息，所述第一载波信息用于指示接受的载波；
第二载波信息，所述第二载波信息用于指示拒绝的载波。
这里，所述接受的载波也即是配置成功的载波。所述第一载波信息也可以称为配置成功信息，本申请对此不做限定。作为示例：所述第一载波信息包括接受的载波的载波标识。
这里，所述拒绝的载波也即是配置失败的载波。所述第二载波信息也可以称为配置失败信息，本申请对此不做限定。作为示例：所述第二载波信息包括拒绝的载波的载波标识。
当然，方案2-1还可以适用于以下场景：所述第一终端设备位于第一网络覆盖范围内；所述第一终端设备处于连接态；所述第一终端设备处于模式一的状态。对于这种场景，在一些实施方式中，所述第一终端设备向其所在的第一网络发送所述配置结果。
方案2-2：由所述第一终端设备所在的第一网络来决定接受或拒绝所述第一配置信息所配置的全部载波或者部分载波。
方案2-2适用于以下场景：所述第一终端设备位于第一网络覆盖范围内；所述第一终端设备处于连接态；所述第一终端设备处于模式一的状态。
所述第一终端设备接收所述第二终端设备发送的第一配置信息之后，所述第一终端设备向其所在的第一网络发送所述第一配置信息；所述第一网络接收所述第一终端设备发送的第一配置信息之后，所述第一网络接受或拒绝所述第一配置信息所配置的全部载波或者部分载波，向所述第一终端设备发送所述第一配置信息对应的配置结果，所述第一终端设备接收所述第一网络发送的所述第一配置信息对应的配置结果；进一步，所述第一终端设备向所述第二终端设备发送所述第一配置信息对应的配置结果。所述第二终端设备接收所述第一终端设备发送的所述第一配置信息对应的配置结果。所述配置结果包括以下至少之一：
第二指示信息，所述第二指示信息用于指示接受或拒绝所述第一配置信息所配置的全部载波或者部分载波；
第一载波信息，所述第一载波信息用于指示被接受的载波；
第二载波信息，所述第二载波信息用于指示被拒绝的载波。
这里，所述接受的载波也即是配置成功的载波。所述第一载波信息也可以称为配置成功信息，本申请对此不做限定。作为示例：所述第一载波信息包括接受的载波的载波标识。
这里，所述拒绝的载波也即是配置失败的载波。所述第二载波信息也可以称为配置失败信息，本申请对此不做限定。作为示例：所述第二载波信息包括拒绝的载波的载波标识。
在一些实施方式中，若所述第二指示信息用于指示拒绝所述第一配置信息所配置的全部载波或者部分载波，则所述第二终端设备执行以下至少一个操作：
基于所述第一信息重新配置多个载波并向所述第一终端设备发送第一配置信息，所述第一配置信息用于重新配置多个载波；
触发单播侧行链路的链路失败流程；
断开单播侧行链路。
在一些实施方式中，所述第二终端设备向其所在的第二网络发送所述配置结果或者所述第二终端设备基于所述配置结果，向其所在的第二网络发送最终的载波配置。这里，所述第二终端设备向其所在的第二网络发送所述配置结果的前提条件包括以下至少之一：所述第二终端设备位于第二网络覆盖范围内；所述第二终端设备处于连接态；所述第二终端设备处于模式一的状态。
在一些实施方式中，所述第二指示信息用于指示接受所述第一配置信息所配置的全部载波或者部分载波的情况下，所述第一载波信息所指示的被接受的载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信；或者，所述第二指示信息用于指示拒绝所述第一配置信息所配置的部分载波的情况下，所述第一配置信息所配置的全部载波中除所述第二载波信息所指示的被拒绝的载波以外的载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
在一些实施方式中，在所述第一配置信息所配置的多个载波中的全部载波或者部分载波配置失败的情况下，所述第一终端设备和所述第二终端设备之间使用第一载波或第二载波或第三载波进行通信，所述第一载波为默认的载波或者默认可用载波集合中的载波或者基于第一映射规则确定的载波，所述第二载波为所述第一终端设备接收所述第一配置信息之前已经配置成功的载波，所述第三载波为所述多个载波中配置成功的部分载波中的载波。这里，可选地，这里，可选地，所述第一映射规则包括第三信息到可用载波和/或可用载波序号的映射关系，所述第三信息包括以下至少之一：
所述第一终端设备和/或所述第二终端设备的层二ID；
所述第一终端设备和所述第二终端设备之间传输数据对应的发射配置(Tx profile)；
所述第一终端设备与所述第二终端设备之间传输数据对应的服务类型或应用类型；
所述第一终端设备与所述第二终端设备之间传输数据对应的数据量；
所述第一终端设备与所述第二终端设备之间传输数据对应的传输类型；
所述第一终端设备与所述第二终端设备之间传输数据对应的QoS流；
所述第一终端设备与所述第二终端设备之间传输数据对应的逻辑信道；
所述第一终端设备与所述第二终端设备之间传输数据对应的资源池；
所述第一终端设备与所述第二终端设备之间传输数据对应的无线承载；
所述第一终端设备与所述第二终端设备之间传输数据对应的数据优先级；
所述第一终端设备与所述第二终端设备之间传输数据对应的资源池的CBR。、
这里，层二ID即为终端设备进行侧行链路通信时所使用的通信地址。
这里，传输类型可以是广播类型、或者单播类型、或者组播类型。对于本申请实施例的方案来说，所述传输类型为单播类型。
需要说明的是，上述方案中的第一载波或第二载波或第三载波可以是1个载波也可以是多个载波。
本申请实施例中，所述第一终端设备与所述第二终端设备之间的交互基于PC5接口进行交互。在一些实施方式中，所述第一终端设备向第二终端设备发送的第一信息可以携带在基于PC5接口的RRC信令(PC5-RRC信令)中、或者侧行链路控制信息(Sidelink Control Information，SCI)中、或者侧行链路MAC CE(SL-MAC CE)中。在一些实施方式中，所述第二终端设备向所述第一终端设备发送的第一配置信息可以携带在PC5-RRC信令中、或者SCI中、或者MAC CE中。
以下结合具体应用实例对本申请实施例的技术方案进行举例说明。
应用实例一
本应用实例中，第一终端设备为单播侧行链路通信的接收端(记作Rx UE)，第二终端设备为单播侧行链路通信的发送端(记作Tx UE)。第一终端设备所在的网络记作网络2，第二终端设备所在的网络记作网络1。由Tx UE或者Tx UE所在的网络1配置载波。具体流程如图3所示，包括以下步骤：
步骤300：Tx UE与Rx UE之间使用默认的载波或者映射的载波进行通信。
这里，默认的载波可以由协议定义，Tx UE与Rx UE双方都知道默认的载波。
这里，映射的载波可以基于第一映射规则确定，这里，可选地，所述第一映射规则包括第三信息到可用载波和/或可用载波序号的映射关系，所述第三信息包括以下至少之一：Tx UE和/或Rx UE的层二ID；Tx UE和Rx UE之间传输数据对应的发射配置(Tx profile)；Tx UE与Rx UE之间传输数据对应的服务类型或应用类型；Tx UE与Rx UE之间传输数据对应的数据量；Tx UE与Rx UE之间传输数据对应的传输类型；Tx UE与Rx UE之间传输数据对应的QoS流；Tx UE与Rx UE之间传输数据对应的逻辑信道；Tx UE与Rx UE之间传输数据对应的资源池；Tx UE与Rx UE之间传输数据对应的无线承载；Tx UE与Rx UE之间传输数据对应的数据优先级；Tx UE与Rx UE之间传输数据对应的资源池的CBR。Tx UE获取第三信息，基于所述第一映射规则确定与第三信息对应的载波(即映射的载波)。Rx UE从Tx UE获取第三信息，基于所述第一映射规则确定与第三信息对应的载波(即映射的载波)。
需要说明的是，在未配置用于Tx UE与Rx UE之间用于单播侧行链路通信的载波之前，Tx UE与Rx UE将使用默认的载波或者默认可用载波集合中的载波或者映射的载波进行通信。例如：Tx UE或Rx UE使用默认的载波或者默认可用载波集合中的载波或者映射的载波发送或接收发现(discovery)消息、直连通信请求(Direct Communication Request，DCR)消息、其他PC5-S消息、PC5-RRC消息等。
步骤301：Rx UE向Tx UE发送载波配置协助信息和/或载波相关能力信息。
这里，载波配置协助信息和/或载波相关能力信息即为上述方案中的第一信息。其中，载波配置协助信息包括Rx UE建议配置的载波或载波集合，载波相关能力信息包括Rx UE的能力支持的载波或载波集合。
触发Rx UE向Tx UE发送载波配置协助信息和/或载波相关能力信息的条件包括以下至少之一：
第一触发条件，所述第一触发条件指：Rx UE接收到Tx UE发送的请求信息，所述请求信息用于请求Rx UE向Tx UE发送载波配置协助信息和/或载波相关能力信息；
第二触发条件，所述第二触发条件指：Rx UE接收到Tx UE发送的第一指示信息，所述第一指示信息用于指示Tx UE和/或Tx UE所在的网络1支持侧行链路载波聚合；
第三触发条件，所述第三触发条件指：Rx UE确定周期性的时间点到达；
第四触发条件，所述第四触发条件指：Rx UE确定目标事件发生。
这里，第三触发条件对应的触发也可以称为周期性触发。
这里，第四触发条件对应的触发也可以称为目标事件触发。作为一些实现方式，所述目标事件包括以下至少之一：
Rx UE建议配置的载波或载波集合发生变化；
Rx UE与Tx UE建立单播侧行链路；
Rx UE已用的载波或载波集合发生变化；
Rx UE可用的载波或载波集合发生变化；
Rx UE与Tx UE之间的单播侧行链路的链路质量发生变化；
Rx UE与Tx UE之间的单播侧行链路上的载波资源上发生冲突。
需要说明的是，对于周期性触发和目标事件触发的情况，Rx UE需确认Tx UE具有载波聚合能力，在Tx UE具有载波聚合能力的情况下，若目标事件发生，则Rx UE向Tx UE发送载波配置协助信息和/或载波相关能力信息。
上述方案中，载波配置协助信息(即Rx UE建议配置的载波或载波集合)由Rx UE基于以下至少之一确定：
Rx UE的能力支持的载波或载波集合；
Rx UE已用的载波或载波集合；
Rx UE可用的载波或载波集合；
Tx UE的能力支持的载波或载波集合；
Tx UE已用的载波或载波集合；
Tx UE可用的载波或载波集合；
Rx UE与Tx UE之间的单播侧行链路通信的通信信息；
Rx UE与Tx UE之间的单播侧行链路的链路质量；
Rx UE所在的网络2的网络配置，网络2的网络配置用于配置网络2的一个或多个覆盖范围所支持的载波或载波集合；
Rx UE所在的网络2的网络能力，网络2的网络能力用于确定网络2是否支持载波聚合。
上述方案中，载波相关能力信息(即Rx UE的能力支持的载波或载波集合)由Rx UE基于以下至少之一确定：
Rx UE已用的载波或载波集合；
Rx UE可用的载波或载波集合；
Rx UE所在的网络2的网络能力，网络2的网络能力用于确定网络2是否支持载波聚合。
步骤302：Tx UE向网络1上报从Rx UE获得的载波配置协助信息和/或载波相关能力信息。
步骤303：网络1向Tx UE下发载波配置信息。
这里，载波配置信息即为上述方案中的第一配置信息，用于配置多个载波。
步骤304：Tx UE向Rx UE下发载波配置信息。
步骤305：Rx UE接受或拒绝载波配置信息所配置的全部载波或部分载波，并向Tx UE发送配置结果。
这里，被接受的载波可以理解为配置成功的载波。被拒绝的载波可以理解为配置失败的载波。
这里，Rx UE接受载波配置信息所配置的全部载波，可以理解为载波配置信息所配置的全部载波被配置成功(或者直接理解为载波配置信息配置成功)。Rx UE拒绝载波配置信息所配置的全部载波，可以理解为载波配置信息所配置的全部载波被配置失败(或者直接理解为载波配置信息配置失败)。
这里，Rx UE接受载波配置信息所配置的部分载波，可以理解为载波配置信息所配置的部分载波被配置成功(或者直接理解为载波配置信息部分配置成功)。Rx UE拒绝载波配置信息所配置的部分载波，可以理解为载波配置信息所配置的部分载波被配置失败(或者直接理解为载波配置信息部分配置失败)。
这里，配置结果包括以下至少之一：用于指示接受或拒绝载波配置信息所配置的全部载波或者部分载波的指示信息；用于指示接受的载波的载波信息(如载波标识)；用于指示拒绝的载波的载波信息(如载波标识)。
步骤306：Rx UE向网络2上报配置结果。
这里，配置结果包括以下至少之一：用于指示接受或拒绝载波配置信息所配置的全部载波或者部分载波的指示信息；用于指示接受的载波的载波信息(如载波标识)；用于指示拒绝的载波的载波 信息(如载波标识)。
步骤307：Tx UE向网络1上报配置结果。
这里，配置结果包括以下至少之一：用于指示接受或拒绝载波配置信息所配置的全部载波或者部分载波的指示信息；用于指示接受的载波的载波信息(如载波标识)；用于指示拒绝的载波的载波信息(如载波标识)。
这里，若配置结果中的指示信息指示拒绝载波配置信息所配置的全部载波或者部分载波(也即载波配置信息全部或部分配置失败)，则Tx UE执行以下至少一个操作：
重配置载波(即重新执行上述步骤302至步骤304)；
触发单播侧行链路的链路失败流程；
断开单播侧行链路。
步骤308：若载波配置信息全部或部分配置成功，则Tx UE与Rx UE使用配置成功的载波进行单播侧行链路通信。
需要说明的是，在Tx UE位于网络1覆盖范围外和/或Tx UE处于非连接态和/或Tx UE处于模式二的状态的情况下，上述步骤302、步骤303以及步骤307不会执行，这种情况下，在步骤301之后，Tx UE自主决定载波配置信息，并执行步骤304。
需要说明的是，在Rx UE位于网络2覆盖范围外和/或Rx UE处于非连接态和/或Rx UE处于模式二的状态的情况下，上述步骤306不会执行。
需要说明的是，在Rx UE位于网络2覆盖范围内和/或Rx UE处于连接态和/或Rx UE处于模式一的状态的情况下，上述步骤305和步骤306也可以替换为以下步骤：
步骤305a：Rx UE向网络2上报载波配置信息。
步骤305b：网络2接受或拒绝载波配置信息所配置的全部载波或部分载波，并向Rx UE发送配置结果。
步骤306a：Rx UE向Tx UE发送配置结果。
应用实例二
本应用实例中，第一终端设备为单播侧行链路通信的发送端(记作Tx UE)，第二终端设备为单播侧行链路通信的接收端(记作Rx UE)。第一终端设备所在的网络记作网络1，第二终端设备所在的网络记作网络2。由Rx UE或者Rx UE所在的网络2配置载波。具体流程如图4所示，包括以下步骤：
步骤400：Rx UE与Tx UE之间使用默认的载波或者映射的载波进行通信。
这里，默认的载波可以由协议定义，Rx UE与Tx UE双方都知道默认的载波。
这里，映射的载波可以基于第一映射规则确定，这里，可选地，所述第一映射规则包括第三信息到可用载波和/或可用载波序号的映射关系，所述第三信息包括以下至少之一：Tx UE和/或Rx UE的层二ID；Tx UE和Rx UE之间传输数据对应的发射配置(Tx profile)；Tx UE与Rx UE之间传输数据对应的服务类型或应用类型；Tx UE与Rx UE之间传输数据对应的数据量；Tx UE与Rx UE之间传输数据对应的传输类型；Tx UE与Rx UE之间传输数据对应的QoS流；Tx UE与Rx UE之间传输数据对应的逻辑信道；Tx UE与Rx UE之间传输数据对应的资源池；Tx UE与Rx UE之间传输数据对应的无线承载；Tx UE与Rx UE之间传输数据对应的数据优先级；Tx UE与Rx UE之间传输数据对应的资源池的CBR。Tx UE获取第三信息，基于所述第一映射规则确定与第三信息对应的载波(即映射的载波)。Rx UE从Tx UE获取第三信息，基于所述第一映射规则确定与第三信息对应的载波(即映射的载波)。
需要说明的是，在未配置用于Rx UE与Tx UE之间用于单播侧行链路通信的载波之前，Rx UE与Tx UE将使用默认的载波或者默认可用载波集合中的载波或者映射的载波进行通信。例如：Rx UE或Tx UE使用默认的载波或者默认可用载波集合中的载波或者映射的载波发送或接收发现(discovery)消息、DCR消息、其他PC5-S消息、PC5-RRC消息等。
步骤401：Tx UE向Rx UE发送载波配置协助信息和/或载波相关能力信息。
这里，载波配置协助信息和/或载波相关能力信息即为上述方案中的第一信息。其中，载波配置协助信息包括Tx UE建议配置的载波或载波集合，载波相关能力信息包括Tx UE的能力支持的载波或载波集合。
触发Tx UE向Rx UE发送载波配置协助信息和/或载波相关能力信息的条件包括以下至少之一：
第一触发条件，所述第一触发条件指：Tx UE接收到Rx UE发送的请求信息，所述请求信息用于请求Tx UE向Rx UE发送载波配置协助信息和/或载波相关能力信息；
第二触发条件，所述第二触发条件指：Tx UE接收到Rx UE发送的第一指示信息，所述第一指示信息用于指示Rx UE和/或Rx UE所在的网络2支持侧行链路载波聚合；
第三触发条件，所述第三触发条件指：Tx UE确定周期性的时间点到达；
第四触发条件，所述第四触发条件指：Tx UE确定目标事件发生。
这里，第三触发条件对应的触发也可以称为周期性触发。
这里，第四触发条件对应的触发也可以称为目标事件触发。作为一些实现方式，所述目标事件包括以下至少之一：
Tx UE建议配置的载波或载波集合发生变化；
Tx UE与Rx UE建立单播侧行链路；
Tx UE已用的载波或载波集合发生变化；
Tx UE可用的载波或载波集合发生变化；
Tx UE与Rx UE之间的单播侧行链路的链路质量发生变化；
Tx UE与Rx UE之间的单播侧行链路上的载波资源上发生冲突。
需要说明的是，对于周期性触发和目标事件触发的情况，Tx UE需确认Rx UE具有载波聚合能力，在Rx UE具有载波聚合能力的情况下，若目标事件发生，则Tx UE向Rx UE发送载波配置协助信息和/或载波相关能力信息。
上述方案中，载波配置协助信息(即Tx UE建议配置的载波或载波集合)由Tx UE基于以下至少之一确定：
Tx UE的能力支持的载波或载波集合；
Tx UE已用的载波或载波集合；
Tx UE可用的载波或载波集合；
Rx UE的能力支持的载波或载波集合；
Rx UE已用的载波或载波集合；
Rx UE可用的载波或载波集合；
Tx UE与Rx UE之间的单播侧行链路通信的通信信息；
Tx UE与Rx UE之间的单播侧行链路的链路质量；
Tx UE所在的网络1的网络配置，网络1的网络配置用于配置网络1的一个或多个覆盖范围所支持的载波或载波集合；
Tx UE所在的网络1的网络能力，网络1的网络能力用于确定网络1是否支持载波聚合。
上述方案中，载波相关能力信息(即Tx UE的能力支持的载波或载波集合)由Tx UE基于以下至少之一确定：
Tx UE已用的载波或载波集合；
Tx UE可用的载波或载波集合；
Tx UE所在的网络1的网络能力，网络1的网络能力用于确定网络1是否支持载波聚合。
步骤402：Rx UE向网络2上报从Tx UE获得的载波配置协助信息和/或载波相关能力信息。
步骤403：网络2向Rx UE下发载波配置信息。
这里，载波配置信息即为上述方案中的第一配置信息，用于配置多个载波。
步骤404：Rx UE向Tx UE下发载波配置信息。
步骤405：Tx UE接受或拒绝载波配置信息所配置的全部载波或部分载波，并向Rx UE发送配置结果。
这里，被接受的载波可以理解为配置成功的载波。被拒绝的载波可以理解为配置失败的载波。
这里，Tx UE接受载波配置信息所配置的全部载波，可以理解为载波配置信息所配置的全部载波被配置成功(或者直接理解为载波配置信息配置成功)。Tx UE拒绝载波配置信息所配置的全部载波，可以理解为载波配置信息所配置的全部载波被配置失败(或者直接理解为载波配置信息配置失败)。
这里，Tx UE接受载波配置信息所配置的部分载波，可以理解为载波配置信息所配置的部分载波被配置成功(或者直接理解为载波配置信息部分配置成功)。Tx UE拒绝载波配置信息所配置的部分载波，可以理解为载波配置信息所配置的部分载波被配置失败(或者直接理解为载波配置信息部分配置失败)。
这里，配置结果包括以下至少之一：用于指示接受或拒绝载波配置信息所配置的全部载波或者部分载波的指示信息；用于指示接受的载波的载波信息(如载波标识)；用于指示拒绝的载波的载波 信息(如载波标识)。
步骤406：Tx UE向网络1上报配置结果。
这里，配置结果包括以下至少之一：用于指示接受或拒绝载波配置信息所配置的全部载波或者部分载波的指示信息；用于指示接受的载波的载波信息(如载波标识)；用于指示拒绝的载波的载波信息(如载波标识)。
步骤407：Rx UE向网络2上报配置结果。
这里，配置结果包括以下至少之一：用于指示接受或拒绝载波配置信息所配置的全部载波或者部分载波的指示信息；用于指示接受的载波的载波信息(如载波标识)；用于指示拒绝的载波的载波信息(如载波标识)。
这里，若配置结果中的指示信息指示拒绝载波配置信息所配置的全部载波或者部分载波(也即载波配置信息全部或部分配置失败)，则Rx UE执行以下至少一个操作：
重配置载波(即重新执行上述步骤402至步骤404)；
触发单播侧行链路的链路失败流程；
断开单播侧行链路。
步骤408：若载波配置信息全部或部分配置成功，则Rx UE与Tx UE使用配置成功的载波进行单播侧行链路通信。
需要说明的是，在Rx UE位于网络2覆盖范围外和/或Rx UE处于非连接态和/或Rx UE处于模式二的状态的情况下，上述步骤402、步骤403以及步骤407不会执行，这种情况下，在步骤401之后，Rx UE自主决定载波配置信息，并执行步骤404。
需要说明的是，在Tx UE位于网络1覆盖范围外和/或Tx UE处于非连接态和/或Tx UE处于模式二的状态的情况下，上述步骤406不会执行。
需要说明的是，在Tx UE位于网络1覆盖范围内和/或Tx UE处于连接态和/或Tx UE处于模式一的状态的情况下，上述步骤405和步骤406也可以替换为以下步骤：
步骤405a：Tx UE向网络1上报载波配置信息。
步骤405b：网络1接受或拒绝载波配置信息所配置的全部载波或部分载波，并向Tx UE发送配置结果。
步骤406a：Tx UE向Rx UE发送配置结果。
以上结合附图详细描述了本申请的优选实施方式，但是，本申请并不限于上述实施方式中的具体细节，在本申请的技术构思范围内，可以对本申请的技术方案进行多种简单变型，这些简单变型均属于本申请的保护范围。例如，在上述具体实施方式中所描述的各个具体技术特征，在不矛盾的情况下，可以通过任何合适的方式进行组合，为了避免不必要的重复，本申请对各种可能的组合方式不再另行说明。又例如，本申请的各种不同的实施方式之间也可以进行任意组合，只要其不违背本申请的思想，其同样应当视为本申请所公开的内容。又例如，在不冲突的前提下，本申请描述的各个实施例和/或各个实施例中的技术特征可以和现有技术任意的相互组合，组合之后得到的技术方案也应落入本申请的保护范围。
还应理解，在本申请的各种方法实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。此外，在本申请实施例中，术语“下行”、“上行”和“侧行”用于表示信号或数据的传输方向，其中，“下行”用于表示信号或数据的传输方向为从站点发送至小区的用户设备的第一方向，“上行”用于表示信号或数据的传输方向为从小区的用户设备发送至站点的第二方向，“侧行”用于表示信号或数据的传输方向为从用户设备1发送至用户设备2的第三方向。例如，“下行信号”表示该信号的传输方向为第一方向。另外，本申请实施例中，术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系。具体地，A和/或B可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
图5是本申请实施例提供的载波配置装置的结构组成示意图一，应用于第一终端设备，如图5所示，所述载波配置装置包括：
发送单元501，用于向第二终端设备发送第一信息，所述第一信息用于所述第二终端设备或者所述第二终端设备所在的第二网络配置载波；
接收单元502，用于接收所述第二终端设备发送的第一配置信息，所述第一配置信息用于配置多个载波，所述多个载波中的至少部分载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
在一些实施方式中，所述第一信息包括所述第一终端设备建议配置的载波或载波集合和/或所述第一终端设备的能力支持的载波或载波集合。
在一些实施方式中，所述第一终端设备建议配置的载波或载波集合基于以下至少之一确定：
所述第一终端设备的能力支持的载波或载波集合；
所述第一终端设备已用的载波或载波集合；
所述第一终端设备可用的载波或载波集合；
所述第二终端设备的能力支持的载波或载波集合；
所述第二终端设备已用的载波或载波集合；
所述第二终端设备可用的载波或载波集合；
所述第一终端设备与所述第二终端设备之间的单播侧行链路通信的通信信息；
所述第一终端设备与所述第二终端设备之间的单播侧行链路的链路质量；
所述第一终端设备所在的第一网络的网络配置，所述第一网络的网络配置用于配置所述第一网络的一个或多个覆盖范围所支持的载波或载波集合；
所述第一终端设备所在的第一网络的网络能力，所述第一网络的网络能力用于确定所述第一网络是否支持载波聚合。
在一些实施方式中，所述第一终端设备的能力支持的载波或载波集合基于以下至少之一确定：
所述第一终端设备已用的载波或载波集合；
所述第一终端设备可用的载波或载波集合；
所述第一终端设备所在的第一网络的网络能力，所述第一网络的网络能力用于确定所述第一网络是否支持载波聚合。
在一些实施方式中，所述发送单元501，用于在确定触发条件满足的情况下，向第二终端设备发送第一信息。
在一些实施方式中，所述触发条件包括以下至少之一：
第一触发条件，所述第一触发条件指：所述第一终端设备接收到所述第二终端设备发送的请求信息，所述请求信息用于请求所述第一终端设备向所述第二终端设备发送所述第一信息；
第二触发条件，所述第二触发条件指：所述第一终端设备接收到所述第二终端设备发送的第一指示信息，所述第一指示信息用于指示所述第二终端设备和/或所述第二终端设备所在的第二网络支持侧行链路载波聚合；
第三触发条件，所述第三触发条件指：所述第一终端设备确定周期性的时间点到达；
第四触发条件，所述第四触发条件指：所述第一终端设备确定目标事件发生。
在一些实施方式中，所述目标事件包括以下至少之一：
所述第一终端设备建议配置的载波或载波集合发生变化；
所述第一终端设备与所述第二终端设备建立单播侧行链路；
所述第一终端设备已用的载波或载波集合发生变化；
所述第一终端设备可用的载波或载波集合发生变化；
所述第一终端设备与所述第二终端设备之间的单播侧行链路的链路质量发生变化；
所述第一终端设备与所述第二终端设备之间的单播侧行链路上的载波资源上发生冲突。
在一些实施方式中，所述第一信息用于所述第二终端设备所在的第二网络配置载波的情况下，所述第一信息由所述第二终端设备转发给所述第二网络；所述接收单元502，用于接收所述第二终端设备转发的来自所述第二网络的第一配置信息。
在一些实施方式中，所述装置还包括：决策单元503，用于接受或拒绝所述第一配置信息所配置的全部载波或者部分载波，所述发送单元501，用于向所述第二终端设备发送所述第一配置信息对应的配置结果，所述配置结果包括以下至少之一：
第二指示信息，所述第二指示信息用于指示接受或拒绝所述第一配置信息所配置的全部载波或者部分载波；
第一载波信息，所述第一载波信息用于指示接受的载波；
第二载波信息，所述第二载波信息用于指示拒绝的载波。
在一些实施方式中，所述发送单元501，用于向其所在的第一网络发送所述配置结果。
在一些实施方式中，所述发送单元501，用于向其所在的第一网络发送所述第一配置信息，所述接收单元502，用于接收所述第一网络发送的所述第一配置信息对应的配置结果，所述配置结果包括以下至少之一：
第二指示信息，所述第二指示信息用于指示接受或拒绝所述第一配置信息所配置的全部载波或者部分载波；
第一载波信息，所述第一载波信息用于指示被接受的载波；
第二载波信息，所述第二载波信息用于指示被拒绝的载波。
在一些实施方式中，所述发送单元501，用于向所述第二终端设备发送所述配置结果。
在一些实施方式中，所述第二指示信息用于指示接受所述第一配置信息所配置的全部载波或者部分载波的情况下，所述第一载波信息所指示的被接受的载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信；或者，所述第二指示信息用于指示拒绝所述第一配置信息所配置的部分载波的情况下，所述第一配置信息所配置的全部载波中除所述第二载波信息所指示的被拒绝的载波以外的载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
在一些实施方式中，在所述第一配置信息所配置的多个载波中的全部载波或者部分载波配置成功之前，所述第一终端设备和所述第二终端设备之间使用第一载波或第二载波进行通信，所述第一载波为默认的载波或者默认可用载波集合中的载波或者基于第一映射规则确定的载波，所述第二载波为所述第一终端设备接收所述第一配置信息之前已经配置成功的载波。
在一些实施方式中，在所述第一配置信息所配置的多个载波中的全部载波或者部分载波配置失败的情况下，所述第一终端设备和所述第二终端设备之间使用第一载波或第二载波或第三载波进行通信，所述第一载波为默认的载波或者默认可用载波集合中的载波或者基于第一映射规则确定的载波，所述第二载波为所述第一终端设备接收所述第一配置信息之前已经配置成功的载波，所述第三载波为所述多个载波中配置成功的部分载波中的载波。
在一些实施方式中，所述第一映射规则包括第三信息到可用载波和/或可用载波序号的映射关系，所述第三信息包括以下至少之一：
所述第一终端设备和/或所述第二终端设备的层二ID；
所述第一终端设备和所述第二终端设备之间传输数据对应的发射配置(Tx profile)；
所述第一终端设备与所述第二终端设备之间传输数据对应的服务类型或应用类型；
所述第一终端设备与所述第二终端设备之间传输数据对应的数据量；
所述第一终端设备与所述第二终端设备之间传输数据对应的传输类型；
所述第一终端设备与所述第二终端设备之间传输数据对应的QoS流；
所述第一终端设备与所述第二终端设备之间传输数据对应的逻辑信道；
所述第一终端设备与所述第二终端设备之间传输数据对应的资源池；
所述第一终端设备与所述第二终端设备之间传输数据对应的无线承载；
所述第一终端设备与所述第二终端设备之间传输数据对应的数据优先级；
所述第一终端设备与所述第二终端设备之间传输数据对应的资源池的CBR。
在一些实施方式中，所述第一终端设备为单播侧行链路通信的发送端，所述第二终端设备为单播侧行链路通信的接收端；或者，所述第一终端设备为单播侧行链路通信的接收端，所述第二终端设备为单播侧行链路通信的发送端。
本领域技术人员应当理解，本申请实施例的上述载波配置装置的相关描述可以参照本申请实施例的载波配置方法的相关描述进行理解。
图6是本申请实施例提供的载波配置装置的结构组成示意图二，应用于第二终端设备，如图6所示，所述载波配置装置包括：
接收单元601，用于接收第一终端设备发送的第一信息，所述第一信息用于所述第二终端设备或者所述第二终端设备所在的第二网络配置载波；
发送单元602，用于向所述第一终端设备发送第一配置信息，所述第一配置信息用于配置多个载波，所述多个载波中的至少部分载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
在一些实施方式中，所述第一信息包括所述第一终端设备建议配置的载波或载波集合和/或所述第一终端设备的能力支持的载波或载波集合。
在一些实施方式中，所述第一终端设备建议配置的载波或载波集合基于以下至少之一确定：
所述第一终端设备的能力支持的载波或载波集合；
所述第一终端设备已用的载波或载波集合；
所述第一终端设备可用的载波或载波集合；
所述第二终端设备的能力支持的载波或载波集合；
所述第二终端设备已用的载波或载波集合；
所述第二终端设备可用的载波或载波集合；
所述第一终端设备与所述第二终端设备之间的单播侧行链路通信的通信信息；
所述第一终端设备与所述第二终端设备之间的单播侧行链路的链路质量；
所述第一终端设备所在的第一网络的网络配置，所述第一网络的网络配置用于配置所述第一网络的一个或多个覆盖范围所支持的载波或载波集合；
所述第一终端设备所在的第一网络的网络能力，所述第一网络的网络能力用于确定所述第一网络是否支持载波聚合。
在一些实施方式中，所述第一终端设备的能力支持的载波或载波集合基于以下至少之一确定：
所述第一终端设备已用的载波或载波集合；
所述第一终端设备可用的载波或载波集合；
所述第一终端设备所在的第一网络的网络能力，所述第一网络的网络能力用于确定所述第一网络是否支持载波聚合。
在一些实施方式中，所述第一信息用于所述第二终端设备所在的第二网络配置载波的情况下，所述发送单元602，用于向所述第二网络转发所述第一信息；所述接收单元601，用于接收所述第二网络发送的所述第一配置信息。
在一些实施方式中，所述接收单元601，用于接收所述第一终端设备发送的所述第一配置信息对应的配置结果，所述配置结果包括以下至少之一：
第二指示信息，所述第二指示信息用于指示接受或拒绝所述第一配置信息所配置的全部载波或者部分载波；
全部载波或者部分载波；
第一载波信息，所述第一载波信息用于指示被接受的载波；
第二载波信息，所述第二载波信息用于指示被拒绝的载波。
在一些实施方式中，所述发送单元602，用于向其所在的第二网络发送所述配置结果。
在一些实施方式中，所述装置还包括：处理单元，用于若所述第二指示信息用于指示拒绝所述第一配置信息所配置的全部载波或者部分载波，则执行以下至少一个操作：
基于所述第一信息重新配置多个载波并向所述第一终端设备发送第一配置信息，所述第一配置信息用于重新配置多个载波；
触发单播侧行链路的链路失败流程；
断开单播侧行链路。
在一些实施方式中，所述第二指示信息用于指示接受所述第一配置信息所配置的全部载波或者部分载波的情况下，所述第一载波信息所指示的被接受的载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信；或者，所述第二指示信息用于指示拒绝所述第一配置信息所配置的部分载波的情况下，所述第一配置信息所配置的全部载波中除所述第二载波信息所指示的被拒绝的载波以外的载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
在一些实施方式中，在所述第一配置信息所配置的多个载波中的全部载波或者部分载波配置成功之前，所述第二终端设备和所述第一终端设备之间使用第一载波或第二载波进行通信，所述第一载波为默认的载波或者默认可用载波集合中的载波或者基于第一映射规则确定的载波，所述第二载波为所述第一终端设备接收所述第一配置信息之前已经配置成功的载波。
在一些实施方式中，在所述第一配置信息所配置的多个载波中的全部载波或者部分载波配置失败的情况下，所述第二终端设备和所述第一终端设备之间使用第一载波或第二载波或第三载波进行通信，所述第一载波为默认的载波或者默认可用载波集合中的载波或者基于第一映射规则确定的载波，所述第二载波为所述第一终端设备接收所述第一配置信息之前已经配置成功的载波，所述第三载波为所述多个载波中配置成功的部分载波中的载波。
在一些实施方式中，所述第一映射规则包括第三信息到可用载波和/或可用载波序号的映射关系，所述第三信息包括以下至少之一：
所述第一终端设备和/或所述第二终端设备的层二ID；
所述第一终端设备和所述第二终端设备之间传输数据对应的(Tx profile)；
所述第一终端设备与所述第二终端设备之间传输数据对应的服务类型或应用类型；
所述第一终端设备与所述第二终端设备之间传输数据对应的数据量；
所述第一终端设备与所述第二终端设备之间传输数据对应的传输类型；
所述第一终端设备与所述第二终端设备之间传输数据对应的QoS流；
所述第一终端设备与所述第二终端设备之间传输数据对应的逻辑信道；
所述第一终端设备与所述第二终端设备之间传输数据对应的资源池；
所述第一终端设备与所述第二终端设备之间传输数据对应的无线承载；
所述第一终端设备与所述第二终端设备之间传输数据对应的数据优先级；
所述第一终端设备与所述第二终端设备之间传输数据对应的资源池的CBR。
在一些实施方式中，所述第一终端设备为单播侧行链路通信的发送端，所述第二终端设备为单播侧行链路通信的接收端；或者，所述第一终端设备为单播侧行链路通信的接收端，所述第二终端设备为单播侧行链路通信的发送端。
本领域技术人员应当理解，本申请实施例的上述载波配置装置的相关描述可以参照本申请实施例的载波配置方法的相关描述进行理解。
图7是本申请实施例提供的一种通信设备700示意性结构图。该通信设备可以第一终端设备，也可以是第二终端设备。图7所示的通信设备700包括处理器710，处理器710可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图7所示，通信设备700还可以包括存储器720。其中，处理器710可以从存储器720中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器720可以是独立于处理器710的一个单独的器件，也可以集成在处理器710中。
可选地，如图7所示，通信设备700还可以包括收发器730，处理器710可以控制该收发器730与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器730可以包括发射机和接收机。收发器730还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备700具体可为本申请实施例的第一终端设备，并且该通信设备700可以实现本申请实施例的各个方法中由第一终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备700具体可为本申请实施例的第二终端设备，并且该通信设备700可以实现本申请实施例的各个方法中由第二终端设备实现的相应流程，为了简洁，在此不再赘述。
图8是本申请实施例的芯片的示意性结构图。图8所示的芯片800包括处理器810，处理器810可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图8所示，芯片800还可以包括存储器820。其中，处理器810可以从存储器820中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器820可以是独立于处理器810的一个单独的器件，也可以集成在处理器810中。
可选地，该芯片800还可以包括输入接口830。其中，处理器810可以控制该输入接口830与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片800还可以包括输出接口840。其中，处理器810可以控制该输出接口840与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的第一终端设备，并且该芯片可以实现本申请实施例的各个方法中由第一终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的第二终端设备，并且该芯片可以实现本申请实施例的各个方法中由第二终端设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图9是本申请实施例提供的一种通信系统900的示意性框图。如图9所示，该通信系统900包括第一终端设备910和第二终端设备920。
其中，该第一终端设备910可以用于实现上述方法中由终端设备实现的相应的功能，以及该第二终端设备920可以用于实现上述方法中由第一终端设备实现的相应的功能为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行 本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的第一终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由第一终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的第二终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由第二终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的第一终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由第一终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的第二终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由第二终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的第一终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由第一终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的第二终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由第二终端设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的 方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (37)

  1. 一种载波配置方法，所述方法包括：
    第一终端设备向第二终端设备发送第一信息，所述第一信息用于所述第二终端设备或者所述第二终端设备所在的第二网络配置载波；
    所述第一终端设备接收所述第二终端设备发送的第一配置信息，所述第一配置信息用于配置多个载波，所述多个载波中的至少部分载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
  2. 根据权利要求1所述的方法，其中，所述第一信息包括所述第一终端设备建议配置的载波或载波集合和/或所述第一终端设备的能力支持的载波或载波集合。
  3. 根据权利要求2所述的方法，其中，所述第一终端设备建议配置的载波或载波集合基于以下至少之一确定：
    所述第一终端设备的能力支持的载波或载波集合；
    所述第一终端设备已用的载波或载波集合；
    所述第一终端设备可用的载波或载波集合；
    所述第二终端设备的能力支持的载波或载波集合；
    所述第二终端设备已用的载波或载波集合；
    所述第二终端设备可用的载波或载波集合；
    所述第一终端设备与所述第二终端设备之间的单播侧行链路通信的通信信息；
    所述第一终端设备与所述第二终端设备之间的单播侧行链路的链路质量；
    所述第一终端设备所在的第一网络的网络配置，所述第一网络的网络配置用于配置所述第一网络的一个或多个覆盖范围所支持的载波或载波集合；
    所述第一终端设备所在的第一网络的网络能力，所述第一网络的网络能力用于确定所述第一网络是否支持载波聚合。
  4. 根据权利要求2或3所述的方法，其中，所述第一终端设备的能力支持的载波或载波集合基于以下至少之一确定：
    所述第一终端设备已用的载波或载波集合；
    所述第一终端设备可用的载波或载波集合；
    所述第一终端设备所在的第一网络的网络能力，所述第一网络的网络能力用于确定所述第一网络是否支持载波聚合。
  5. 根据权利要求1至4中任一项所述的方法，其中，所述第一终端设备向第二终端设备发送第一信息，包括：
    所述第一终端设备在确定触发条件满足的情况下，向第二终端设备发送第一信息。
  6. 根据权利要求5所述的方法，其中，所述触发条件包括以下至少之一：
    第一触发条件，所述第一触发条件指：所述第一终端设备接收到所述第二终端设备发送的请求信息，所述请求信息用于请求所述第一终端设备向所述第二终端设备发送所述第一信息；
    第二触发条件，所述第二触发条件指：所述第一终端设备接收到所述第二终端设备发送的第一指示信息，所述第一指示信息用于指示所述第二终端设备和/或所述第二终端设备所在的第二网络支持侧行链路载波聚合；
    第三触发条件，所述第三触发条件指：所述第一终端设备确定周期性的时间点到达；
    第四触发条件，所述第四触发条件指：所述第一终端设备确定目标事件发生。
  7. 根据权利要求5所述的方法，其中，所述目标事件包括以下至少之一：
    所述第一终端设备建议配置的载波或载波集合发生变化；
    所述第一终端设备与所述第二终端设备建立单播侧行链路；
    所述第一终端设备已用的载波或载波集合发生变化；
    所述第一终端设备可用的载波或载波集合发生变化；
    所述第一终端设备与所述第二终端设备之间的单播侧行链路的链路质量发生变化；
    所述第一终端设备与所述第二终端设备之间的单播侧行链路上的载波资源上发生冲突。
  8. 根据权利要求1至7中任一项所述的方法，其中，所述第一信息用于所述第二终端设备 所在的第二网络配置载波的情况下，所述第一信息由所述第二终端设备转发给所述第二网络；
    所述第一终端设备接收所述第二终端设备发送的第一配置信息，包括：
    所述第一终端设备接收所述第二终端设备转发的来自所述第二网络的第一配置信息。
  9. 根据权利要求1至8中任一项所述的方法，其中，所述第一终端设备接收所述第二终端设备发送的第一配置信息之后，所述方法还包括：
    所述第一终端设备接受或拒绝所述第一配置信息所配置的全部载波或者部分载波，向所述第二终端设备发送所述第一配置信息对应的配置结果，所述配置结果包括以下至少之一：
    第二指示信息，所述第二指示信息用于指示接受或拒绝所述第一配置信息所配置的全部载波或者部分载波；
    第一载波信息，所述第一载波信息用于指示接受的载波；
    第二载波信息，所述第二载波信息用于指示拒绝的载波。
  10. 根据权利要求9所述的方法，其中，所述方法还包括：
    所述第一终端设备向其所在的第一网络发送所述配置结果。
  11. 根据权利要求1至8中任一项所述的方法，其中，所述第一终端设备接收所述第二终端设备发送的第一配置信息之后，所述方法还包括：
    所述第一终端设备向其所在的第一网络发送所述第一配置信息，接收所述第一网络发送的所述第一配置信息对应的配置结果，所述配置结果包括以下至少之一：
    第二指示信息，所述第二指示信息用于指示接受或拒绝所述第一配置信息所配置的全部载波或者部分载波；
    第一载波信息，所述第一载波信息用于指示被接受的载波；
    第二载波信息，所述第二载波信息用于指示被拒绝的载波。
  12. 根据权利要求11所述的方法，其中，所述方法还包括：
    所述第一终端设备向所述第二终端设备发送所述配置结果。
  13. 根据权利要求9至12中任一项所述的方法，其中，
    所述第二指示信息用于指示接受所述第一配置信息所配置的全部载波或者部分载波的情况下，所述第一载波信息所指示的被接受的载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信；或者，
    所述第二指示信息用于指示拒绝所述第一配置信息所配置的部分载波的情况下，所述第一配置信息所配置的全部载波中除所述第二载波信息所指示的被拒绝的载波以外的载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
  14. 根据权利要求1至13中任一项所述的方法，其中，所述方法还包括：
    在所述第一配置信息所配置的多个载波中的全部载波或者部分载波配置成功之前，所述第一终端设备和所述第二终端设备之间使用第一载波或第二载波进行通信，所述第一载波为默认的载波或者默认可用载波集合中的载波或者基于第一映射规则确定的载波，所述第二载波为所述第一终端设备接收所述第一配置信息之前已经配置成功的载波。
  15. 根据权利要求1至13中任一项所述的方法，其中，所述方法还包括：
    在所述第一配置信息所配置的多个载波中的全部载波或者部分载波配置失败的情况下，所述第一终端设备和所述第二终端设备之间使用第一载波或第二载波或第三载波进行通信，所述第一载波为默认的载波或者默认可用载波集合中的载波或者基于第一映射规则确定的载波，所述第二载波为所述第一终端设备接收所述第一配置信息之前已经配置成功的载波，所述第三载波为所述多个载波中配置成功的部分载波中的载波。
  16. 根据权利要求14或15所述的方法，其中，所述第一映射规则包括第三信息到可用载波和/或可用载波序号的映射关系，所述第三信息包括以下至少之一：
    所述第一终端设备和/或所述第二终端设备的层二ID；
    所述第一终端设备和所述第二终端设备之间传输数据对应的发射配置Tx profile；
    所述第一终端设备与所述第二终端设备之间传输数据对应的服务类型或应用类型；
    所述第一终端设备与所述第二终端设备之间传输数据对应的数据量；
    所述第一终端设备与所述第二终端设备之间传输数据对应的传输类型；
    所述第一终端设备与所述第二终端设备之间传输数据对应的QoS流；
    所述第一终端设备与所述第二终端设备之间传输数据对应的逻辑信道；
    所述第一终端设备与所述第二终端设备之间传输数据对应的资源池；
    所述第一终端设备与所述第二终端设备之间传输数据对应的无线承载；
    所述第一终端设备与所述第二终端设备之间传输数据对应的数据优先级；
    所述第一终端设备与所述第二终端设备之间传输数据对应的资源池的拥塞程度CBR。
  17. 根据权利要求1至16中任一项所述的方法，其中，
    所述第一终端设备为单播侧行链路通信的发送端，所述第二终端设备为单播侧行链路通信的接收端；或者，
    所述第一终端设备为单播侧行链路通信的接收端，所述第二终端设备为单播侧行链路通信的发送端。
  18. 一种载波配置方法，所述方法包括：
    第二终端设备接收第一终端设备发送的第一信息，所述第一信息用于所述第二终端设备或者所述第二终端设备所在的第二网络配置载波；
    所述第二终端设备向所述第一终端设备发送第一配置信息，所述第一配置信息用于配置多个载波，所述多个载波中的至少部分载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
  19. 根据权利要求18所述的方法，其中，所述第一信息包括所述第一终端设备建议配置的载波或载波集合和/或所述第一终端设备的能力支持的载波或载波集合。
  20. 根据权利要求19所述的方法，其中，所述第一终端设备建议配置的载波或载波集合基于以下至少之一确定：
    所述第一终端设备的能力支持的载波或载波集合；
    所述第一终端设备已用的载波或载波集合；
    所述第一终端设备可用的载波或载波集合；
    所述第二终端设备的能力支持的载波或载波集合；
    所述第二终端设备已用的载波或载波集合；
    所述第二终端设备可用的载波或载波集合；
    所述第一终端设备与所述第二终端设备之间的单播侧行链路通信的通信信息；
    所述第一终端设备与所述第二终端设备之间的单播侧行链路的链路质量；
    所述第一终端设备所在的第一网络的网络配置，所述第一网络的网络配置用于配置所述第一网络的一个或多个覆盖范围所支持的载波或载波集合；
    所述第一终端设备所在的第一网络的网络能力，所述第一网络的网络能力用于确定所述第一网络是否支持载波聚合。
  21. 根据权利要求19或20所述的方法，其中，所述第一终端设备的能力支持的载波或载波集合基于以下至少之一确定：
    所述第一终端设备已用的载波或载波集合；
    所述第一终端设备可用的载波或载波集合；
    所述第一终端设备所在的第一网络的网络能力，所述第一网络的网络能力用于确定所述第一网络是否支持载波聚合。
  22. 根据权利要求18至21中任一项所述的方法，其中，所述第一信息用于所述第二终端设备所在的第二网络配置载波的情况下，
    所述第二终端设备接收第一终端设备发送的第一信息之后，所述方法还包括：所述第二终端设备向所述第二网络转发所述第一信息；
    所述第二终端设备向所述第一终端设备发送第一配置信息之前，所述方法还包括：所述第二终端设备接收所述第二网络发送的所述第一配置信息。
  23. 根据权利要求18至22中任一项所述的方法，其中，所述第二终端设备向所述第一终端设备发送第一配置信息之后，所述方法还包括：
    所述第二终端设备接收所述第一终端设备发送的所述第一配置信息对应的配置结果，所述配置结果包括以下至少之一：
    第二指示信息，所述第二指示信息用于指示接受或拒绝所述第一配置信息所配置的全部载波或者部分载波；
    全部载波或者部分载波；
    第一载波信息，所述第一载波信息用于指示被接受的载波；
    第二载波信息，所述第二载波信息用于指示被拒绝的载波。
  24. 根据权利要求23所述的方法，其中，所述方法还包括：
    所述第二终端设备向其所在的第二网络发送所述配置结果。
  25. 根据权利要求23或24所述的方法，其中，所述方法还包括：
    若所述第二指示信息用于指示拒绝所述第一配置信息所配置的全部载波或者部分载波，则所述第二终端设备执行以下至少一个操作：
    基于所述第一信息重新配置多个载波并向所述第一终端设备发送第一配置信息，所述第一配置信息用于重新配置多个载波；
    触发单播侧行链路的链路失败流程；
    断开单播侧行链路。
  26. 根据权利要求23至25中任一项所述的方法，其中，
    所述第二指示信息用于指示接受所述第一配置信息所配置的全部载波或者部分载波的情况下，所述第一载波信息所指示的被接受的载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信；或者，
    所述第二指示信息用于指示拒绝所述第一配置信息所配置的部分载波的情况下，所述第一配置信息所配置的全部载波中除所述第二载波信息所指示的被拒绝的载波以外的载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
  27. 根据权利要求18至26中任一项所述的方法，其中，所述方法还包括：
    在所述第一配置信息所配置的多个载波中的全部载波或者部分载波配置成功之前，所述第二终端设备和所述第一终端设备之间使用第一载波或第二载波进行通信，所述第一载波为默认的载波或者默认可用载波集合中的载波或者基于第一映射规则确定的载波，所述第二载波为所述第一终端设备接收所述第一配置信息之前已经配置成功的载波。
  28. 根据权利要求18至26中任一项所述的方法，其中，所述方法还包括：
    在所述第一配置信息所配置的多个载波中的全部载波或者部分载波配置失败的情况下，所述第二终端设备和所述第一终端设备之间使用第一载波或第二载波或第三载波进行通信，所述第一载波为默认的载波或者默认可用载波集合中的载波或者基于第一映射规则确定的载波，所述第二载波为所述第一终端设备接收所述第一配置信息之前已经配置成功的载波，所述第三载波为所述多个载波中配置成功的部分载波中的载波。
  29. 根据权利要求27或28所述的方法，其中，所述第一映射规则包括第三信息到可用载波和/或可用载波序号的映射关系，所述第三信息包括以下至少之一：
    所述第一终端设备和/或所述第二终端设备的层二ID；
    所述第一终端设备和所述第二终端设备之间传输数据对应的Tx profile；
    所述第一终端设备与所述第二终端设备之间传输数据对应的服务类型或应用类型；
    所述第一终端设备与所述第二终端设备之间传输数据对应的数据量；
    所述第一终端设备与所述第二终端设备之间传输数据对应的传输类型；
    所述第一终端设备与所述第二终端设备之间传输数据对应的QoS流；
    所述第一终端设备与所述第二终端设备之间传输数据对应的逻辑信道；
    所述第一终端设备与所述第二终端设备之间传输数据对应的资源池；
    所述第一终端设备与所述第二终端设备之间传输数据对应的无线承载；
    所述第一终端设备与所述第二终端设备之间传输数据对应的数据优先级；
    所述第一终端设备与所述第二终端设备之间传输数据对应的资源池的CBR。
  30. 根据权利要求18至29中任一项所述的方法，其中，
    所述第一终端设备为单播侧行链路通信的发送端，所述第二终端设备为单播侧行链路通信的接收端；或者，
    所述第一终端设备为单播侧行链路通信的接收端，所述第二终端设备为单播侧行链路通信的发送端。
  31. 一种载波配置装置，应用于第一终端设备，所述方法包括：
    发送单元，用于向第二终端设备发送第一信息，所述第一信息用于所述第二终端设备或者所述第二终端设备所在的第二网络配置载波；
    接收单元，用于接收所述第二终端设备发送的第一配置信息，所述第一配置信息用于配置多个载波，所述多个载波中的至少部分载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
  32. 一种载波配置装置，应用于第二终端设备，所述方法包括：
    接收单元，用于接收第一终端设备发送的第一信息，所述第一信息用于所述第二终端设备或者所述第二终端设备所在的第二网络配置载波；
    发送单元，用于向所述第一终端设备发送第一配置信息，所述第一配置信息用于配置多个载波，所述多个载波中的至少部分载波用于所述第一终端设备和所述第二终端设备之间进行单播侧行链路通信。
  33. 一种终端设备，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至17中任一项所述的方法，或者权利要求18至30中任一项所述的方法。
  34. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至17中任一项所述的方法，或者权利要求18至30中任一项所述的方法。
  35. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至17中任一项所述的方法，或者权利要求18至30中任一项所述的方法。
  36. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至17中任一项所述的方法，或者权利要求18至30中任一项所述的方法。
  37. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1至17中任一项所述的方法，或者权利要求18至30中任一项所述的方法。
PCT/CN2022/110360 2022-08-04 2022-08-04 一种载波配置方法及装置、终端设备 WO2024026787A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/110360 WO2024026787A1 (zh) 2022-08-04 2022-08-04 一种载波配置方法及装置、终端设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/110360 WO2024026787A1 (zh) 2022-08-04 2022-08-04 一种载波配置方法及装置、终端设备

Publications (1)

Publication Number Publication Date
WO2024026787A1 true WO2024026787A1 (zh) 2024-02-08

Family

ID=89848242

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/110360 WO2024026787A1 (zh) 2022-08-04 2022-08-04 一种载波配置方法及装置、终端设备

Country Status (1)

Country Link
WO (1) WO2024026787A1 (zh)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112737755A (zh) * 2019-03-29 2021-04-30 华为技术有限公司 通信方法和通信装置

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112737755A (zh) * 2019-03-29 2021-04-30 华为技术有限公司 通信方法和通信装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
OPPO: "TP for PC5-RRC based procedure for unicast in NR-V2X", 3GPP DRAFT; R2-1902502 - TP OF PC5-RRC BASED PROCEDURE FOR UNICAST IN NR-V2X, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Athens, Greece; 20190225 - 20190301, 1 March 2019 (2019-03-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051603753 *

Similar Documents

Publication Publication Date Title
WO2020191769A1 (zh) 传输侧行信道的方法和终端设备
WO2019214301A1 (zh) 通信方法和设备
WO2016161900A1 (zh) 一种进行数据传输的方法和设备
WO2021203872A1 (zh) 节能配置方法及装置、节能方法及装置、通信节点、存储介质
TW202019205A (zh) 一種資源配置方法及裝置、終端
WO2019237805A1 (zh) 一种随机接入方法及装置、通信设备
WO2020056560A1 (zh) 一种通信方法、终端设备和网络设备
WO2020015267A1 (zh) 一种随机接入方法及装置
WO2021212372A1 (zh) 资源分配方法和终端
WO2023153336A1 (ja) 通信システムおよび基地局
WO2021016979A1 (zh) 无线通信方法和终端设备
WO2023030088A1 (zh) 旁链路通信方法及设备
WO2020124534A1 (zh) 数据传输的方法和设备
WO2024026787A1 (zh) 一种载波配置方法及装置、终端设备
WO2021212283A1 (zh) 一种请求系统广播信息的方法及装置、终端设备
WO2021134477A1 (zh) 一种波束训练方法及相关设备
WO2019213806A1 (zh) 通信方法和终端
WO2023205950A1 (zh) 载波管理方法、装置、设备和介质
TW202015477A (zh) 通訊方法、終端設備和網路設備
WO2023205951A1 (zh) 载波确定方法、装置、设备和介质
WO2023216048A1 (zh) 一种无线通信方法及装置、通信设备
WO2023220961A1 (zh) 数据传输方法、第一设备、第二设备
WO2023245493A1 (zh) 无线通信的方法和终端设备
US20240031857A1 (en) Method for determining drx parameter, terminal device and storage medium
WO2024026632A1 (zh) 传输资源选取方法和设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22953596

Country of ref document: EP

Kind code of ref document: A1