Wireless communication method, terminal equipment and network equipment
Patent Information
- Application Number
- CN202280096042.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-07-07
- Publication Date
- 2025-01-10
AI Technical Summary
In sidelink communications, the fixed mapping relationship of carrier aggregation makes the carrier selection process inflexible and difficult to meet dynamically changing communication needs.
Through communication between terminal equipment and network equipment, carriers on sidelinks are dynamically configured, and carrier configuration information and configuration auxiliary information are used to improve the flexibility of carrier configuration and ensure the adaptability of carrier selection.
It improves the flexibility and success rate of carrier configuration in sidelinks, adapts to dynamic changes in different communication scenarios, and improves communication performance.
Smart Images

Figure CN119302014A_ABST
Abstract
Description
Wireless communication method, terminal device and network device Technical Field
[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal equipment, and network equipment. Background Art
[0002] In the sidelink communication scenario, communication can be based on carrier aggregation (CA) technology when broadcast and multicast communication is based on broadcast and multicast communication. However, the multiple carriers (or at least two carriers) used by carrier aggregation need to be determined based on the mapping relationship between carriers and service types. However, this mapping relationship is fixed and not easy to change. This method of determining carriers based on a fixed mapping relationship makes the carrier selection process inflexible.
[0003] Summary of the Invention
[0004] The present application provides a wireless communication method, a terminal device, and a network device. The following introduces various aspects of the present application.
[0005] In a first aspect, a wireless communication method is provided, comprising: a first terminal device sends carrier configuration information for a first side link to a second terminal device; wherein the first side link is a side link for unicast communication between the first terminal device and the second terminal device, and the carrier configuration information is used to configure at least two carriers on the first side link.
[0006] In a second aspect, a wireless communication method is provided, including: a second terminal device receives carrier configuration information for a first side link sent by a first terminal device; wherein the first side link is a side link for unicast communication between the first terminal device and the second terminal device, and the carrier configuration information is used to configure at least two carriers on the first side link.
[0007] According to a third aspect, a wireless communication method is provided, comprising: a network device determines carrier configuration information for a first side link; wherein the first side link is a side link for unicast communication between the first terminal device and the second terminal device, and the carrier configuration information is used to configure multiple carriers on the first side link.
[0008] In a fourth aspect, a first terminal device is provided, comprising: a sending unit for sending carrier configuration information for a first side link to a second terminal device; wherein the first side link is a side link for unicast communication between the first terminal device and the second terminal device, and the carrier configuration information is used to configure at least two carriers on the first side link.
[0009] In the fifth aspect, a second terminal device is provided, including: a receiving unit for receiving carrier configuration information for a first side link sent by a first terminal device; wherein the first side link is a side link for unicast communication between the first terminal device and the second terminal device, and the carrier configuration information is used to configure at least two carriers on the first side link.
[0010] In the sixth aspect, a network device is provided, including: a processing unit, determining carrier configuration information for a first side link; wherein the first side link is a side link for unicast communication between the first terminal device and the second terminal device, and the carrier configuration information is used to configure multiple carriers on the first side link.
[0011] In the seventh aspect, a terminal device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the terminal device executes part or all of the steps in the methods of the above aspects.
[0012] In an eighth aspect, a network device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the network device executes part or all of the steps in the method of the third aspect.
[0013] In a ninth aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal and / or network device. In another possible design, the system may also include other devices that interact with the terminal or network device in the solution provided in the embodiment of the present application.
[0014] In a tenth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program enables a terminal to execute part or all of the steps in the methods of the above aspects.
[0015] In an eleventh aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a terminal to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.
[0016] In the twelfth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.
[0017] In the present application, the first terminal device can configure multiple carriers used on the side link for the second terminal device, so that the multiple carriers used on the side link can be changed based on the configuration, which helps to improve the flexibility of configuring multiple carriers in the side link. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] FIG1 is a diagram illustrating an example of a system architecture of a wireless communication system to which an embodiment of the present application may be applied.
[0019] FIG2 is an example diagram of a side communication scenario within network coverage.
[0020] FIG3 is an example diagram of a side communication scenario with partial network coverage.
[0021] FIG4 is an example diagram of a side communication scenario outside network coverage.
[0022] FIG5 is a diagram showing an example of a side communication scenario based on a central control node.
[0023] FIG6 is an example diagram of a sideline communication method based on broadcasting.
[0024] FIG7 is an example diagram of a unicast-based sideline communication method.
[0025] FIG8 is an example diagram of a side communication method based on multicast.
[0026] FIG9 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.
[0027] FIG10 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.
[0028] FIG11 is a schematic flowchart of a wireless communication method according to another embodiment of the present application.
[0029] FIG12 is a schematic diagram of a terminal device according to an embodiment of the present application.
[0030] FIG13 is a schematic diagram of a terminal device according to another embodiment of the present application.
[0031] FIG14 is a schematic diagram of a network device according to an embodiment of the present application.
[0032] FIG15 is a schematic structural diagram of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION
[0033] Communication system architecture
[0034] FIG1 is a diagram illustrating an exemplary system architecture of a wireless communication system 100 to which embodiments of the present application may be applied. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide communication coverage for a specific geographic area and may communicate with the terminal device 120 within the coverage area.
[0035] FIG1 exemplarily shows a network device and a terminal device. Optionally, the wireless communication system 100 may include one or more network devices 110 and / or one or more terminal devices 120. For a network device 110, the one or more terminal devices 120 may all be located within the network coverage of the network device 110, or all be located outside the network coverage of the network device 110, or some may be located within the coverage of the network device 110 and others outside the network coverage of the network device 110. This is not limited in the embodiments of the present application.
[0036] Optionally, the wireless communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.
[0037] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.
[0038] The terminal device in the embodiment of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal device, mobile device, user terminal, wireless communication device, user agent or user device. The terminal device in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiment of the present application may be a mobile phone, a tablet computer (Pad), a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a vehicle, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. For example, a terminal device can act as a dispatching entity, providing sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) communications. For example, a cell phone and a car can communicate with each other using sidelink signals. A cell phone and a smart home device can also communicate without relaying the communication signal through a base station. Alternatively, the terminal device can be used to act as a base station.
[0039] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station may broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. A base station may also refer to a communication module, modem, or chip used to be set in the aforementioned device or apparatus. A base station may also be a mobile switching center and a device that performs base station functions in device-to-device D2D, V2X, or machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station may support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by network devices.
[0040] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.
[0041] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device includes a CU and a DU. The gNB may also include an AAU.
[0042] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.
[0043] Sideline communication under different network coverage conditions
[0044] Sidelink communication refers to a communication technology based on a sidelink. Sidelink communication can be, for example, device-to-device (D2D) or vehicle-to-everything (V2X) communication. In traditional cellular systems, communication data is received or sent between terminal devices and network devices, while sidelink communication supports direct communication and data transmission between terminal devices. Compared with traditional cellular communication, direct communication data transmission between terminal devices can have higher spectrum efficiency and lower transmission latency. For example, the vehicle networking system adopts sidelink communication technology.
[0045] In side communication, according to the network coverage of the terminal device, the side communication can be divided into side communication within the network coverage, side communication with partial network coverage, and side communication outside the network coverage.
[0046] Figure 2 illustrates an example scenario for sidelink communication within network coverage. In the scenario shown in Figure 2, both terminal devices 120a are within the coverage of network device 110. Therefore, both terminal devices 120a can receive configuration signaling from network device 110 (configuration signaling in this application can also be replaced by configuration information) and determine the sidelink configuration based on the configuration signaling from network device 110. After both terminal devices 120a have configured their sidelinks, sidelink communication can proceed on the sidelink.
[0047] Figure 3 is an example diagram of a sidelink communication scenario with partial network coverage. In the scenario shown in Figure 3, terminal device 120a performs sidelink communication with terminal device 120b. Terminal device 120a is located within the coverage range of network device 110, so terminal device 120a can receive the configuration signaling of network device 110 and determine the sidelink configuration based on the configuration signaling of network device 110. Terminal device 120b is located outside the network coverage and cannot receive the configuration signaling of network device 110. In this case, terminal device 120b can determine the sidelink configuration based on pre-configuration information and / or information carried in the physical sidelink broadcast channel (PSBCH) sent by terminal device 120a within the network coverage. After both terminal device 120a and terminal device 120b perform sidelink configuration, sidelink communication can be performed on the sidelink.
[0048] Figure 4 illustrates an example scenario for sidelink communication outside of network coverage. In the scenario shown in Figure 4, both terminal devices 120b are outside of network coverage. In this scenario, both terminal devices 120b can determine the sidelink configuration based on pre-configured information. After both terminal devices 120b have configured their sidelinks, sidelink communication can proceed over the sidelink.
[0049] Sideline communication based on central control node
[0050] Figure 5 is an example diagram of a sideline communication scenario based on a central control node. In this sideline communication scenario, multiple terminal devices can form a communication group, and the communication group has a central control node. The central control node can be a terminal device in the communication group (such as terminal device 1 in Figure 5), and the terminal device can also be called a cluster head (CH) terminal device. The central control node can be responsible for completing one or more of the following functions: establishing a communication group, joining and leaving group members of the communication group, coordinating resources within the communication group, allocating sideline transmission resources to other terminal devices, receiving sideline feedback information from other terminal devices, and coordinating resources with other communication groups.
[0051] Sideline communication mode
[0052] Some standards or protocols (such as the 3rd Generation Partnership Project (3GPP)) define two sideline communication modes: a first mode and a second mode.
[0053] In the first mode, the resources of the terminal device (the resources mentioned in this application may also be referred to as transmission resources, such as time-frequency resources) are allocated by the network device. The terminal device can send data on the side link according to the resources allocated by the network device. The network device can allocate resources for a single transmission to the terminal device, or it can allocate resources for semi-static transmission to the terminal device. This first mode can be applied to scenarios covered by a network device, such as the scenario shown in Figure 2 above. In the scenario shown in Figure 2, the terminal device 120a is within the network coverage of the network device 110, so the network device 110 can allocate resources used in the side transmission process to the terminal device 120a.
[0054] In the second mode, the terminal device can autonomously select one or more resources from a resource pool (RP). The terminal device can then perform sideline transmission based on the selected resources. For example, in the scenario shown in FIG4 , the terminal device 120b is located outside the cell coverage area. Therefore, the terminal device 120b can autonomously select resources from a preconfigured resource pool for sideline transmission. Alternatively, in the scenario shown in FIG2 , the terminal device 120a can also autonomously select one or more resources from a resource pool configured by the network device 110 for sideline transmission.
[0055] Data transmission method of side communication
[0056] Some sidewalk communication systems (such as long-term evolution vehicle to everything (LTE-V2X)) support broadcast-based data transmission (hereinafter referred to as broadcast transmission). For broadcast transmission, the receiving terminal can be any terminal device around the transmitting terminal. Taking Figure 6 as an example, terminal device 1 is the transmitting terminal, and the receiving terminal corresponding to the transmitting terminal is any terminal device around terminal device 1, for example, terminal device 2 to terminal device 6 in Figure 6.
[0057] In addition to broadcast transmission, some communication systems also support unicast-based data transmission (hereinafter referred to as unicast transmission) and / or multicast-based data transmission (hereinafter referred to as multicast transmission). For example, the new radio vehicle to everything (NR-V2X) hopes to support autonomous driving. Autonomous driving places higher requirements on data interaction between vehicles. For example, data interaction between vehicles requires higher throughput, lower latency, higher reliability, larger coverage, more flexible resource allocation modes, etc. Therefore, in order to improve the performance of data interaction between vehicles, NR-V2X introduces unicast transmission and multicast transmission.
[0058] For unicast transmission, there is typically only one receiving terminal. For example, in Figure 7, unicast transmission occurs between terminal devices 1 and 2. Terminal device 1 can be the sending terminal, and terminal device 2 can be the receiving terminal, or vice versa.
[0059] For multicast transmission, the receiving terminal can be a terminal device within a communication group, or a terminal device within a certain transmission distance. For example, in Figure 8, terminal devices 1, 2, 3, and 4 form a communication group. If terminal device 1 sends data, all other terminal devices in the group (terminal devices 2 through 4) can be receiving terminals.
[0060] Carrier aggregation technology
[0061] To meet the requirements for single-user peak data rates and improved system capacity, one of the most direct approaches is to increase the system transmission bandwidth. Therefore, a bandwidth-enhancing technology, carrier aggregation (CA), has been introduced into communication systems. CA aggregates multiple (e.g., 2-5) component carriers (CCs) to increase transmission bandwidth, effectively boosting uplink and downlink transmission rates.
[0062] In some implementations, the CCs participating in the aggregation may be carriers that are adjacent in frequency band, or may be carriers that are not adjacent in frequency band.
[0063] In other implementations, CA technologies can be categorized based on the range of aggregated carriers. CA types can be divided into intra-band CA and inter-band CA (or inter-band CA). As the name implies, in intra-band CA, the CCs participating in carrier aggregation belong to the same frequency band. In inter-band CA, the CCs participating in carrier aggregation belong to multiple different frequency bands.
[0064] For ease of understanding, the following introduces CA technology using scenarios where network devices communicate with terminal devices, and sideline communication scenarios where terminal devices communicate with each other as examples.
[0065] In communications between network devices and end devices, CA is a bandwidth extension technology supported since the LTE-Advanced standard. It aggregates multiple CCs, allowing a single end device to receive or transmit simultaneously. In this scenario, intra-band CA can be used when the cell carrier bandwidth exceeds the bandwidth capability of a single end device. In this case, the end device can use CA to operate within a "wide carrier."
[0066] For example, the network device supports a 300MHz carrier, while the terminal device only supports a maximum of 100MHz carrier. At this time, in order to improve the transmission rate between the terminal device and the network device, the terminal device can use CA to communicate with the network device using a bandwidth greater than 100MHz.
[0067] In some scenarios, when a terminal device and a network device communicate based on CA, a primary cell (PCell) and a secondary cell (SCell) may be configured simultaneously. The secondary cell may include a primary secondary cell (PSCell). Currently, in known communication protocols (e.g., NR Release 15), a beam failure recovery mechanism is designed for PCell and PSCell. Its main functional modules (or main steps) can be divided into the following four: beam failure detection (BFD); new beam identification (NBI); beam failure recovery request (BFRQ); and network-side response.
[0068] That is to say, in the beam failure detection step, the terminal device can measure the PDCCH to determine the link quality corresponding to the downlink transmission beam. If the corresponding link quality is very poor, it is considered that the downlink beam has a beam failure. Then enter the new beam selection step, the terminal device can measure a set of alternative beams, and select a beam that meets a certain threshold from the alternative beams as a new beam. The terminal device then notifies the network device of the beam failure through the BFRQ process and reports the selected new beam. Accordingly, in the network side response step, after receiving the BFRQ information sent by the terminal device, the network device can know that the terminal device has a beam failure and choose to send PDCCH from the new beam. Then, the network device sends PDCCH to the terminal device on the new beam. Accordingly, after the terminal device receives the PDCCH on the new beam, it can be considered that the response information from the network side has been correctly received. At this point, the beam failure recovery process is successfully completed.
[0069] In a sideline communication scenario, when a terminal device communicates with other terminal devices in a broadcast or multicast manner, the terminal device can select the carrier set corresponding to the service to which the data to be transmitted belongs based on the pre-stored mapping relationship between the service type and the carrier set, and perform carrier aggregation based on the selected carrier set to communicate with other terminal devices.
[0070] In some implementations, the terminal device may determine the CC for carrier aggregation from the selected carrier set based on the CBR. For example, the terminal device may measure the CBR value in the resource pool and compare it with the CBR threshold corresponding to the priority of the data to be transmitted. If the measured CBR value is lower than the CBR threshold, the terminal device may determine that the carrier is suitable for carrier aggregation. Conversely, if the measured CBR value is higher than or equal to the CBR threshold, the terminal device may determine that the carrier is not suitable for carrier aggregation.
[0071] As described above, the multiple carriers (or at least two carriers) used for sidelink communication need to be determined based on a mapping relationship between carriers and service types. However, this mapping relationship is fixed and difficult to change. This method of determining carriers based on a fixed mapping relationship is not flexible.
[0072] Therefore, in order to avoid the above problems, an embodiment of the present application provides a wireless communication method, in which a first terminal device can configure multiple carriers used on a side link for a second terminal device, so that the multiple carriers used on the side link can be changed based on the configuration, which helps to improve the flexibility of configuring multiple carriers in the side link.
[0073] For ease of understanding, the following describes the wireless communication method according to an embodiment of the present application, using a first terminal device and a second terminal device as examples, in conjunction with Figure 9. The first terminal device and the second terminal device can perform unicast communication via a first sidelink. Figure 9 is a schematic flow chart of the wireless communication method according to an embodiment of the present application. The method shown in Figure 9 includes step S910.
[0074] In step S910, the first terminal device sends carrier configuration information for the first sidelink to the second terminal device.
[0075] The carrier configuration information is used to configure at least two carriers on the first sidelink. The at least two carriers may include carriers participating in carrier aggregation, or in other words, the at least two carriers may include carrier members participating in carrier aggregation. Therefore, alternatively, the carrier configuration information may be used to perform related configurations for carrier aggregation on the first sidelink.
[0076] In addition, in an embodiment of the present application, the above-mentioned carrier configuration information can configure the carriers on the first sidelink in the form of a carrier set, wherein the carrier set can include the above-mentioned at least two carriers.
[0077] In some scenarios, the above-mentioned first terminal device sends carrier configuration information to the second terminal device, which can be understood as the first terminal device configuring at least two carriers on the first side link for the second terminal device, that is, the first terminal device can control the carrier used by the second terminal device. Therefore, the first terminal device can also be called a "controlling terminal device" and the second terminal device can also be called a "controlled terminal device."
[0078] Typically, different terminal devices support different carriers, and the first terminal device may not be able to determine the carrier supported by the second terminal device. In this case, the first terminal device may configure a carrier for the second terminal device that the second terminal device does not support, resulting in carrier configuration failure.
[0079] Therefore, to improve the success rate of carrier configuration, the second terminal device can send configuration auxiliary information (e.g., "first configuration auxiliary information") to the first terminal device to assist the first terminal device in configuring at least two carriers on the first sidelink for the second terminal device. In other words, the first configuration auxiliary information is used to determine the carrier configuration information. Therefore, the above-mentioned configuration auxiliary information can also be referred to as "carrier configuration auxiliary information."
[0080] In some implementations, the first configuration auxiliary information may include a carrier that the second terminal device expects to be configured. On the one hand, the determination of the carrier that the second terminal device expects to be configured may take into account the carrier situation of the second terminal device. Generally, after a carrier is used on a certain communication link, the carrier may not be used on other links at the same time. Therefore, the carrier expected by the second terminal device may be determined based on the carrier used on other communication links of the second terminal device. The other communication links may be communication links other than the first sidelink in the second terminal device, and the other communication links may include one or more of an uplink, a downlink, and a sidelink.
[0081] On the other hand, the first sidelink is the link used by the first terminal device to communicate with the second terminal device. Therefore, the carrier situation of the first terminal device can be considered when determining the carrier that the second terminal device expects to be configured. For example, the carrier expected by the second terminal device can be determined based on the carrier supported by the terminal capability of the first terminal device. For another example, the carrier expected by the second terminal device can also be determined based on the idle carrier of the first terminal device. This embodiment of the present application is not limited to this.
[0082] The carrier status of the above-mentioned first terminal device can be sent by the first terminal device to the second terminal device. In some implementations, when the first terminal device requests the first configuration auxiliary information from the second terminal device (see trigger method 3 described below for details), the first terminal device can carry the carrier status of the first terminal device in the request. Of course, the first terminal device can also send the carrier status of the first terminal device to the second terminal device through other information. This embodiment of the present application is not limited to this.
[0083] It should be noted that, as described above, the second terminal device can determine the carrier that the second terminal device expects to be configured based on the carrier situation of the second terminal device or the carrier situation of the first terminal device. Of course, the carrier situation of the first terminal device and the carrier situation of the second terminal device can also be comprehensively considered to determine the carrier expected by the second terminal device, and this embodiment of the application is not limited to this.
[0084] In addition, in the embodiment of the present application, the first configuration auxiliary information can indicate the carrier that the second terminal device expects to be configured by carrying indication information of the carrier that the second terminal device expects to be configured (for example, the identifier of the carrier, the serial number of the carrier, etc.). The embodiment of the present application does not limit the specific method of indicating the carrier that the second terminal device expects to be configured.
[0085] In some other implementations, the first configuration assistance information may include a carrier supported by the terminal capability of the second terminal device. Generally, the carrier supported by the terminal capability of the second terminal device may be understood as a carrier available to the second terminal device.
[0086] In the embodiment of the present application, the first configuration auxiliary information may carry information indicating the carriers supported by the terminal capability to indicate the carriers supported by the terminal capability. The embodiment of the present application does not limit the specific manner of indicating the carriers supported by the terminal capability.
[0087] The above describes the content of the first configuration auxiliary information, and the following describes the triggering method for sending the first configuration auxiliary information. In the embodiments of this application, the triggering method for the first configuration auxiliary information is not limited. The following describes several common triggering methods.
[0088] Triggering mode 1: the sending of the first configuration auxiliary information may be triggered periodically.
[0089] That is, the second terminal device may periodically send the first configuration auxiliary information. The period used in the periodic triggering may be configured by predefinition, preconfiguration, network configuration, etc., which is not limited in the embodiment of the present application.
[0090] It should be noted that if the first terminal device does not have carrier aggregation capability, but the second terminal device still periodically sends the first configuration auxiliary information to the first terminal device, at this time, the first configuration auxiliary information is useless to the first terminal device, then the periodic sending of the first configuration auxiliary information may result in a waste of transmission resources. Therefore, the periodic triggering method is usually a triggering method used when it is determined that the first terminal device has carrier aggregation capability. Of course, if the problem of transmission resource waste is not considered, when using the periodic triggering method, it is also possible not to consider whether the first terminal device has carrier aggregation capability.
[0091] In addition, whether the first terminal device has the carrier aggregation capability can be requested by the second terminal device to the first terminal device, or the first terminal device can also actively inform the second terminal device, which is not limited in this embodiment of the present application.
[0092] Triggering mode 2: the sending of the first configuration auxiliary information may be triggered based on an event.
[0093] That is, if an event occurs, the second terminal device will send the first configuration auxiliary information to the first terminal device. Conversely, if the aforementioned event does not occur, the second terminal device will not send the first configuration auxiliary information to the first terminal device. The event can be configured through pre-definition, pre-configuration, network device configuration, etc., which is not limited in this embodiment of the present application.
[0094] It should be noted that if the first terminal device does not have carrier aggregation capability, but in the event of the above-mentioned event, the second terminal device still periodically sends the first configuration auxiliary information to the first terminal device. At this time, the first configuration auxiliary information is useless to the first terminal device. Then, the sending of the first configuration auxiliary information based on the event trigger may result in a waste of transmission resources. Therefore, the event-based triggering method is usually a triggering method used when it is determined that the first terminal device has carrier aggregation capability. Of course, if the problem of transmission resource waste is not considered, when using the event-based triggering method, it is also possible not to consider whether the first terminal device has carrier aggregation capability.
[0095] In an embodiment of the present application, the above-mentioned events may be related to the scenarios that cause the carrier usage of the second terminal device to change. Several possible events are introduced below as examples.
[0096] In some scenarios, when the link quality of the first side link changes, the carrier used on the first side link may also change. For example, when the link quality of the first side link deteriorates, the second terminal device may no longer use the carrier on the first side link, resulting in a change in the carrier available to the second terminal device on the first side link. Therefore, the above event can be associated with the link quality of the first side link. In some implementations, the above event can include a change in the link quality of the first side link. The link quality change can, for example, include a deterioration in link quality.
[0097] In some scenarios, after a conflict occurs between communication links, the second terminal device may no longer use the conflicting communication link. In this case, the second terminal device may no longer use the carrier on the conflicting communication link, or the second terminal device may use the carrier on the first sidelink. Ultimately, regardless of whether the second terminal device uses the carrier, the available carrier for the second terminal device on the first sidelink may change. Therefore, the above event may be associated with a conflict between the first sidelink and the other communication link. In some implementations, the above event may include a conflict between the first sidelink and the other communication link.
[0098] In some scenarios, the carrier that the second terminal device expects to be configured with may change for various reasons. When the carrier that the second terminal device expects to be configured with changes, the change in the carrier that the second terminal device expects to be configured with needs to be considered when configuring the carrier used in the first sidelink. Therefore, the above event may be associated with the change in the carrier that the second terminal device expects to be configured with. In some implementations, the above event may include a change in the carrier that the second terminal device expects to be configured with.
[0099] In some scenarios, the configuration auxiliary information may change due to various reasons. For example, as described above, when the carrier that the second terminal device expects to configure changes, the configuration auxiliary information will also change. Accordingly, the change in configuration auxiliary information needs to be considered when configuring the carrier used on the first sidelink, so the above event may be associated with a change in configuration auxiliary information. In some implementations, the above event may include a change in the first configuration auxiliary information compared to the previously sent configuration auxiliary information, wherein the configuration auxiliary information is used to determine the carrier configuration information, or in other words, the configuration auxiliary information has the same function as the first configuration auxiliary information.
[0100] In some scenarios, the carrier configuration of other communication links of the second terminal device, other than the first sidelink, may change. When the carrier configuration of other communication links changes, the carrier that the second terminal device can use in the first sidelink may change. Therefore, the above event may be associated with a change in the carrier configuration of other communication links in the second terminal device. In some implementations, the above event may include a change in the carrier configuration of other communication links of the second terminal device.
[0101] Of course, in the embodiments of the present application, in addition to being related to various scenarios that cause changes in the carrier usage of the second terminal device, the above-mentioned event may also be related to the transmission of configuration auxiliary information. In some implementations, the above-mentioned event may include that the second terminal device has not sent configuration auxiliary information via the first sidelink, or in other words, that the second terminal device has not sent configuration auxiliary information via the first sidelink before sending the first configuration auxiliary information.
[0102] Trigger mode 3: The sending of the first configuration auxiliary information may be triggered based on a request from the first terminal device.
[0103] That is, the first terminal device may actively send a request to the second terminal device to request the first configuration auxiliary information. Correspondingly, in response to the request, the second terminal device may send the first configuration auxiliary information to the first terminal device.
[0104] It should be noted that the embodiments of the present application do not limit the timing of the first terminal device sending the above request. In some implementations, the first terminal device may send the request to the second terminal device before sending the carrier configuration information. In other implementations, the first terminal device may also send the request to the second terminal device after failing to configure the carrier of the first sidelink for the second terminal device.
[0105] It should be noted that the above triggering modes 1 to 3 can be used alone or in combination with each other, and the embodiments of the present application do not limit this.
[0106] In some scenarios, the first terminal device and / or the second terminal device may be within the coverage of the network device. In this case, if the first terminal device directly configures the carrier used by the first side link for the second terminal device, the carrier configured on the first side link may be allocated to other terminal devices by the network device, resulting in unreasonable carrier configuration on the first side link.
[0107] For example, network devices in urban areas may have a large amount of service data to transmit. In this case, the network devices typically do not want to allocate the carrier used for cellular communication to sideline communication. In this case, if the first terminal device configures the same carrier for cellular communication for the second terminal device, this may cause a conflict between the cellular communication and the sideline communication.
[0108] Therefore, to avoid the above situation, in the embodiment of the present application, when the first terminal device or the second terminal device is within the coverage of the network, the network device can participate in the carrier configuration process of the first sidelink. Of course, if the above problem is not taken into consideration, when the first terminal device or the second terminal device is within the coverage of the network device, the first terminal device can also directly configure the carrier of the first sidelink without the participation of the network device.
[0109] The following describes a solution for network devices to participate in carrier configuration in two situations: a first terminal device is located within the network coverage area; and a second terminal device is located within the network coverage area.
[0110] In scenario 1, the first terminal device is within the coverage area of the network.
[0111] In this case, the carrier configuration information may be determined by the network device. For example, the network device may configure at least two carriers used on the first sidelink to the second terminal device through the first terminal device. Alternatively, the network device may send the carrier configuration information to the first terminal device, and the first terminal device may send the received carrier configuration information to the second terminal device.
[0112] In some scenarios, the network device may not be able to obtain the carrier status of the second terminal device. In this case, the second terminal device may not be able to use the carrier configured by the network device for the first sidelink. Therefore, to improve the rationality of the carrier configured by the network device for the first sidelink, the first terminal device can send the configuration assistance information described above to the network device to assist the network device in determining the carrier configuration information.
[0113] It should be noted that in an embodiment of the present application, the first terminal device can directly send the configuration auxiliary information sent by the second terminal device to the network device, that is, the first terminal device sends the second configuration auxiliary information to the network device, wherein the second configuration auxiliary information is the same as the first configuration auxiliary information (that is, the configuration auxiliary information sent by the second terminal device to the first terminal device).
[0114] Of course, after receiving the first configuration auxiliary information sent by the second terminal device, the first terminal device may also process the first configuration auxiliary information to obtain second configuration auxiliary information, and send the second configuration auxiliary information to the network device. In this case, the second configuration auxiliary information is different from the first configuration auxiliary information. The second configuration auxiliary information may be determined based on the first configuration auxiliary information, or in other words, the second configuration auxiliary information is used to indicate the first configuration auxiliary information.
[0115] For example, assuming that the first configuration auxiliary information includes the carrier supported by the terminal capability of the second terminal device, after the first terminal device receives the first configuration auxiliary information, the carrier supported by the terminal capability of the first terminal device can be added to the first configuration auxiliary information to obtain the second configuration auxiliary information. Then, the first terminal device can send the second configuration auxiliary information to the network device.
[0116] Accordingly, after the second terminal device receives the carrier configuration information, the second terminal device may choose to accept part or all of the configuration information in the carrier configuration information, or the second terminal device may choose to refuse to accept part or all of the configuration information in the carrier configuration information. At this time, the second terminal device may notify the first terminal device of the above selection result through the first indication information, so that the first terminal device can subsequently determine whether to communicate with the second terminal device based on the carrier configured in the carrier configuration information.
[0117] In some implementations, the first indication information may be carried in a configuration complete message or a configuration failure message. The configuration complete message is used to indicate that the carrier configuration process for the first sidelink is complete. The configuration failure message is used to indicate that the carrier configuration process for the first sidelink has failed.
[0118] It should be noted that when the first indication information indicates a refusal to accept the carrier configuration information, and the first indication information is carried in the configuration completion message, at this time, it can be understood that the configuration process for the first side link is completed, and the configuration parameters other than the carrier configuration are successfully or partially successful, but the carrier on the first side link is not successfully configured.
[0119] In addition, when the first indication information indicates acceptance of the carrier configuration information, and the first indication information is carried in the configuration failure message, it can be understood that the carrier configuration process for the first sidelink has failed.
[0120] In other implementations, the first terminal device may further notify the network device of the selection result so that the network device can determine whether to reconfigure the carrier for the first sidelink. Therefore, the first terminal device may send second indication information to the network device to instruct the second terminal device to accept part or all of the configuration information in the carrier configuration information, or to instruct the second terminal device to reject part or all of the configuration information in the carrier configuration information.
[0121] It should be noted that the second indication information can be the same as the first indication information, that is, the first terminal device directly forwards the first indication information to the network device. Of course, the second indication information can also be different from the first indication information, that is, the second indication information can be used to indicate the first indication information, or in other words, the second indication information is determined based on the first indication information. In other words, after receiving the first indication information, the first terminal device processes the first indication information to obtain the second indication information, and then sends the second indication information to the network device.
[0122] In the above-mentioned scenario 1, for the first terminal device within the coverage of the network device, the first terminal device may be in a connected state. At this time, the resource allocation mode of the first terminal device may include Mode 1 or Mode 2 introduced above. Of course, the above-mentioned network device-assisted carrier configuration process may be limited to the first terminal device whose resource allocation mode is in Mode 1.
[0123] In the above scenario 1, the second terminal device may not be within the coverage of the network device, or in other words, the second terminal device is outside the coverage of the network device, that is, the scenario shown in Figure 3 above. Of course, in the above scenario 1, the second terminal device may also be within the coverage of the network device, and this embodiment of the application is not limited to this.
[0124] In scenario 2, the second terminal device is located within the coverage area of the network device.
[0125] At this time, the second terminal device can send carrier configuration information to the network device. Accordingly, the network device can instruct the second terminal device to accept part or all of the configuration information in the carrier configuration information through the first indication information, or the network device can instruct the second terminal device to refuse to accept part or all of the configuration information in the carrier configuration information.
[0126] For example, when the network device determines that the carrier in the carrier configuration information is idle, it can instruct the second terminal device to accept the carrier configuration information through the first indication information. Conversely, when the network device determines that the carrier in the carrier configuration information is occupied by cellular communication, it can instruct the second terminal device to refuse to accept the carrier configuration information through the first indication information.
[0127] Typically, after the network device indicates the configuration result of the carrier configuration information to the second terminal device through the first indication information, the first terminal device also needs to know the configuration result of the carrier configuration information in order to subsequently determine whether to communicate with the second terminal device based on the carrier configured based on the carrier configuration information. Therefore, the second terminal device can send the first indication information to the first terminal device.
[0128] In some implementations, the first indication information may be carried in a configuration complete message or a configuration failure message. The configuration complete message is used to indicate that the carrier configuration process for the first sidelink is complete. The configuration failure message is used to indicate that the carrier configuration process for the first sidelink has failed.
[0129] It should be noted that when the first indication information indicates a refusal to accept the carrier configuration information, and the first indication information is carried in the configuration completion message, it can be understood that the carrier configuration process for the first side link is completed, but the carrier on the first side link is not configured successfully.
[0130] In addition, when the first indication information indicates acceptance of carrier configuration information, and the first indication information is carried in the configuration failure message, at this time, it can be understood that the carrier configuration process for the first side link has failed, but the reason for the failure of the configuration process is not because the second terminal device refuses to accept the carrier configuration information.
[0131] In the above situation 2, for the second terminal device within the coverage of the network device, the second terminal device may be in a connected state. At this time, the resource allocation mode of the second terminal device may include mode 1 and mode 2 introduced above.
[0132] In the above scenario 2, whether the first terminal device is within the coverage of the network device is not limited. For example, the first terminal device may not be within the coverage of the network device, or in other words, the first terminal device is located outside the coverage of the network device, that is, the scenario shown in Figure 3 above. Of course, in the above scenario 2, the first terminal device may also be within the coverage of the network device, and this embodiment of the application does not limit this.
[0133] In some implementations, if the second terminal device refuses to accept part or all of the configuration information in the carrier configuration information, and / or the second terminal device sends a configuration failure message to the first terminal device, the first terminal device and / or the second terminal device performs one or more of the following operations: determining that a radio link failure (RLF) occurs in the first sidelink; disconnecting the first sidelink; and reconfiguring the carrier configuration information of the first sidelink.
[0134] On the contrary, if the second terminal device accepts part or all of the configuration information in the carrier configuration information, the first terminal device can communicate with the second terminal device based on the carrier configured by the configuration information accepted by the second terminal device.
[0135] In an embodiment of the present application, before the above-mentioned configuration signaling interaction for the first side link is completed, communication on the first side link may not be based on carrier aggregation technology, that is, communication on the first side link may be performed in a single-carrier manner. Of course, in order to increase the bandwidth, carrier aggregation technology may also be used for communication on the first side link before the above-mentioned configuration signaling interaction for the first side link is completed. In this case, the carrier participating in carrier aggregation may be configured based on pre-configuration information, or the carrier used on the first side link may be a carrier determined based on the mapping rule between the configured service and the carrier. The mapping rule between the service and the carrier may reuse the mapping relationship in LTE V2X.
[0136] For example, before the first terminal device sends carrier configuration information to the second terminal device, the carrier used on the first side link has not been configured, but the first terminal device needs to communicate with the second terminal device based on carrier aggregation (for example, transmitting PC5-radio resource control (PC5-RRC) signaling (for example, PC5-S signaling), transmitting discovery messages, transmitting direct communication requests (DCR), etc.). At this time, the carrier used can be configured based on pre-configuration information, and / or can be determined based on the mapping rules between the configured service and the carrier.
[0137] It should be noted that the terminal device may select the carrier set in a manner that adopts a conventional sidelink carrier selection method. For example, the carriers participating in the carrier set may be selected based on the CBR threshold as described above, which is not limited in this embodiment of the present application.
[0138] For ease of understanding, the wireless communication method of an embodiment of the present application is described below in conjunction with Figures 10 and 11. In the following description, the first terminal device is terminal device 1, the second terminal device is terminal device 2, and the first sidelink is sidelink 1.
[0139] It should be noted that the methods shown in Figures 10 and 11 are based on the example of a first terminal device or a second terminal device being within the coverage range of a network device, and primarily illustrate the execution flow of the methods. Information in Figures 10 and 11 that has the same function as that described above uses the same name. The content and transmission methods of the information can be found in the description above and will not be further elaborated below for the sake of brevity.
[0140] FIG10 is a schematic flow chart of a wireless communication method according to an embodiment of the present application. Referring to FIG10 , it is assumed that terminal device 1 is within the coverage of a network device, and terminal device 2 is not within the coverage of the network device. The method of FIG10 includes steps S1010 to S1019.
[0141] In step S1010, if terminal device 1 is not configured with a carrier for carrier aggregation in sidelink 1, terminal device 1 and terminal device 2 can perform carrier aggregation based on a carrier set on the first sidelink and communicate based on carrier aggregation.
[0142] The carrier set may be configured based on pre-configured information and / or may be determined based on a configured service-to-carrier mapping rule, wherein the service-to-carrier mapping rule may reuse the mapping relationship in LTE V2X.
[0143] It should be noted that, in the above step S1010, communication may also be performed based on a single carrier on the first sidelink, which is not limited in this embodiment of the present application.
[0144] In step S1011 , terminal device 2 sends first configuration auxiliary information to terminal device 1 .
[0145] In step S1012, the terminal device 1 sends second configuration auxiliary information to the network device.
[0146] In step S1013 , the network device generates carrier configuration information based on the second configuration assistance information.
[0147] In step S1014 , the network device sends carrier configuration information to terminal device 1 .
[0148] In step S1015 , terminal device 1 sends carrier configuration information to terminal device 2 .
[0149] In step S1016 , the terminal device 2 determines whether to accept the carrier configuration information.
[0150] In step S1017 , terminal device 2 sends first indication information to terminal device 1 , where the first indication information is used to indicate the determination result in step S1016 .
[0151] That is, the first indication information instructs terminal device 2 to accept part or all of the configuration information in the carrier configuration information, or the first indication information instructs terminal device 2 to refuse to accept part or all of the configuration information in the carrier configuration information. If the first indication information instructs to accept part or all of the configuration information in the carrier configuration information, step S1018 is executed; if the first indication information instructs to accept part or all of the configuration information in the carrier configuration information, step S1019 is executed.
[0152] In step S1018, terminal device 1 and terminal device 2 perform carrier aggregation based on the carriers configured by the carrier configuration information received by terminal device 2, and communicate based on the carrier set.
[0153] In step S1019 , the terminal device 1 performs a first operation.
[0154] The above-mentioned first operation includes one or more of the following: sending second indication information to the network device, the second indication information is used to indicate the first indication information; determining that a wireless link failure occurs in the first side link; disconnecting the first side link; and reconfiguring the carrier configuration information of the first side link.
[0155] FIG11 is a schematic flow chart of a wireless communication method according to another embodiment of the present application. Referring to FIG11 , it is assumed that terminal device 2 is within the coverage of a network device, while terminal device 1 is not. The method of FIG11 includes steps S1110 to S1118.
[0156] In step S1110, if the terminal device 1 is not configured with a carrier for carrier aggregation in the side link 1, the terminal device 1 and the terminal device 2 can perform carrier aggregation based on the carrier set on the first side link and communicate based on the carrier aggregation.
[0157] The carrier set may be configured based on pre-configured information and / or may be determined based on a configured service-to-carrier mapping rule, wherein the service-to-carrier mapping rule may reuse the mapping relationship in LTE V2X.
[0158] It should be noted that, in the above step S1110, communication may also be performed based on a single carrier on the first sidelink, which is not limited in this embodiment of the present application.
[0159] In step S1111 , terminal device 2 sends first configuration auxiliary information to terminal device 1 .
[0160] In step S1112 , the terminal device 1 generates carrier configuration information based on the first configuration auxiliary information.
[0161] In step S1113 , terminal device 1 sends carrier configuration information to terminal device 2 .
[0162] In step S1114, terminal device 2 sends carrier configuration information to the network device.
[0163] In step S1115 , the network device sends first indication information to the terminal device 2 .
[0164] The first indication information is used to instruct the terminal device 2 to accept part or all of the configuration information in the carrier configuration information, or the first indication information is used to instruct the terminal device 2 to refuse to accept part or all of the configuration information in the carrier configuration information.
[0165] In step S1116, terminal device 2 sends first indication information to terminal device 1.
[0166] If the first indication information indicates that the terminal device 2 determines to accept the carrier configuration information, step S1117 is executed. If the first indication information indicates that the terminal device 2 determines to reject the carrier configuration information, steps S1118 and S1119 are executed.
[0167] In step S1117, terminal device 1 and terminal device 2 perform carrier aggregation based on the carriers configured by the carrier configuration information received by terminal device 2, and communicate based on the carrier aggregation.
[0168] In step S1118 , the terminal device 1 performs a first operation.
[0169] The first operation includes one or more of the following: determining that a radio link failure occurs in the first sidelink; disconnecting the first sidelink; and reconfiguring carrier configuration information of the first sidelink.
[0170] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 11. The device embodiment of the present application is described in detail below in conjunction with Figures 12 to 15. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.
[0171] FIG12 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 1200 shown in FIG12 may be, for example, the first terminal device described above. The terminal device 1200 shown in FIG12 includes: a sending unit 1210.
[0172] The sending unit 1210 is used to send carrier configuration information for the first side link to the second terminal device; wherein the first side link is a side link for unicast communication between the first terminal device and the second terminal device, and the carrier configuration information is used to configure at least two carriers on the first side link.
[0173] In a possible implementation, the terminal device further includes: a first receiving unit, configured to receive first configuration auxiliary information sent by the second terminal device, where the first configuration auxiliary information is used to determine the carrier configuration information.
[0174] In a possible implementation, the first configuration auxiliary information includes at least one of the following: a carrier that the second terminal device expects to configure; and a carrier supported by the terminal capability of the second terminal device.
[0175] In one possible implementation, the carrier that the second terminal device expects to configure is determined based on at least one of the following: the carrier used on the sidelink other than the first sidelink of the second terminal device; the carrier used on the uplink of the second terminal device; the carrier used on the downlink of the second terminal device; and the carrier supported by the terminal capabilities of the first terminal device.
[0176] In a possible implementation, the sending of the first configuration auxiliary information is triggered based on one or more of the following methods: periodic triggering; event triggering; and triggering based on a request of the first terminal device.
[0177] In one possible implementation, the event includes one or more of the following: a change in the link quality of the first side link; a conflict between the first side link and other communication links; a change in the carrier that the second terminal device expects to configure; the second terminal device has not sent configuration auxiliary information through the first side link, and the configuration auxiliary information is used to determine the carrier configuration information; the first configuration auxiliary information changes compared to the configuration auxiliary information sent previously, and the configuration auxiliary information is used to determine the carrier configuration information; and a change in the carrier configuration of other communication links of the second terminal device other than the first side link.
[0178] In a possible implementation manner, the carrier configuration information is determined based on the network device.
[0179] In a possible implementation, the first terminal device is in a connected state, and / or the resource allocation mode of the first terminal device includes mode 1.
[0180] In a possible implementation, the sending unit is further used to: send second configuration auxiliary information to the network device, where the second configuration auxiliary information is used to indicate the first configuration auxiliary information, and the first configuration auxiliary information is used to determine the carrier configuration information.
[0181] In a possible implementation, the terminal device further includes: a second receiving unit, configured to receive the carrier configuration information sent by the network device.
[0182] In a possible implementation, the terminal device further includes: a third receiving unit, configured to receive first indication information sent by the second terminal device, wherein the first indication information is configured to instruct the second terminal device to accept part or all of the configuration information in the carrier configuration information.
[0183] In a possible implementation, the terminal device further includes: a fourth receiving unit, configured to receive first indication information sent by the second terminal device, wherein the first indication information is configured to instruct the second terminal device to refuse to accept part or all of the configuration information in the carrier configuration information.
[0184] In one possible implementation, the above-mentioned terminal device also includes: a processing unit, used to perform one or more of the following operations in response to the first indication information: determining that a wireless link failure occurs in the first side link; disconnecting the first side link; reconfiguring the carrier configuration information of the first side link; and sending a second indication information to the network device, wherein the second indication information is used to indicate whether the second terminal device accepts part or all of the configuration information in the carrier configuration information.
[0185] In a possible implementation manner, the first indication information is carried in a configuration completion message or a configuration failure message.
[0186] In one possible implementation, the above-mentioned terminal device also includes: a communication unit for communicating with the second terminal device based on a carrier set; wherein the carrier set includes one or more of the following: a carrier determined based on pre-configuration information; and a carrier determined based on a mapping rule between configured services and carriers.
[0187] FIG13 is a schematic diagram of a terminal device according to another embodiment of the present application. The terminal device 1300 shown in FIG13 may be the second terminal device described above. The terminal device 1300 includes a receiving unit 1310.
[0188] The receiving unit 1310 is used to receive carrier configuration information for a first side link sent by a first terminal device; wherein the first side link is a side link for unicast communication between the first terminal device and the second terminal device, and the carrier configuration information is used to configure at least two carriers on the first side link.
[0189] In a possible implementation, the terminal device further includes: a first sending unit, configured to send first configuration auxiliary information to the first terminal device, where the first configuration auxiliary information is used to determine the carrier configuration information.
[0190] In a possible implementation, the first configuration auxiliary information includes at least one of the following: a carrier that the second terminal device expects to configure; and a carrier supported by the terminal capability of the second terminal device.
[0191] In one possible implementation, the carrier that the second terminal device expects to configure is determined based on at least one of the following: the carrier used on the sidelink other than the first sidelink of the second terminal device; the carrier used on the uplink of the second terminal device; the carrier used on the downlink of the second terminal device; or the carrier supported by the terminal capabilities of the first terminal device.
[0192] In a possible implementation, the sending of the first configuration auxiliary information is triggered based on one or more of the following methods: periodic triggering; event triggering; or request triggering based on the first terminal device.
[0193] In one possible implementation, the event includes one or more of the following: a change in the link quality of the first side link; a conflict between the first side link and other communication links; a change in the carrier that the second terminal device expects to configure; the second terminal device has not sent configuration auxiliary information through the first side link, and the configuration auxiliary information is used to determine the carrier configuration information; the first configuration auxiliary information changes compared to the configuration auxiliary information sent previously, and the configuration auxiliary information is used to determine the carrier configuration information; and a change in the carrier configuration of other communication links of the second terminal device other than the first side link.
[0194] In a possible implementation manner, the carrier configuration information is determined based on the network device.
[0195] In a possible implementation, the first terminal device is located within the coverage of the network device, and / or the resource allocation mode of the first terminal device includes mode 1.
[0196] In a possible implementation, the second terminal device is located within the coverage of a network device, and the terminal device further includes: a second sending unit, configured to send the carrier configuration information to the network device.
[0197] In one possible implementation, the receiving unit is further used to: receive first indication information sent by the network device, wherein the first indication information is used to instruct the second terminal device to accept part or all of the configuration information in the carrier configuration information, or the first indication information is used to instruct the second terminal device to refuse to accept part or all of the configuration information in the carrier configuration information.
[0198] In one possible implementation, if the second terminal device refuses to accept part or all of the configuration information in the carrier configuration information, the first terminal device performs one or more of the following operations: determining that a radio link failure occurs in the first side link; disconnecting the first side link; reconfiguring the carrier configuration information of the first side link; and sending a second indication information to the network device, where the second indication information is used to indicate whether the second terminal device accepts part or all of the configuration information in the carrier configuration information.
[0199] In a possible implementation, the terminal device further includes: a third sending unit, configured to send the first indication information to the first terminal device.
[0200] In a possible implementation manner, the first indication information is carried in a configuration completion message or a configuration failure message.
[0201] In one possible implementation, the above-mentioned terminal device also includes: a communication unit for communicating with the first terminal device based on a carrier set; wherein the carrier set includes one or more of the following: a default carrier; and a carrier determined based on a mapping rule between a configured service type and a carrier.
[0202] FIG14 is a schematic diagram of a network device according to an embodiment of the present application. The network device 1400 shown in FIG14 includes a processing unit 1410 .
[0203] Processing unit 1410 determines carrier configuration information for a first side link; wherein the first side link is a side link for unicast communication between the first terminal device and the second terminal device, and the carrier configuration information is used to configure multiple carriers on the first side link.
[0204] In a possible implementation, the above-mentioned network device further includes: a first receiving unit, used to receive second configuration auxiliary information sent by the first terminal device; the processing unit is further used to determine the carrier configuration information based on the second configuration auxiliary information.
[0205] In a possible implementation manner, the second configuration auxiliary information is determined based on first configuration auxiliary information, and the first configuration auxiliary information is used to determine the carrier configuration information.
[0206] In a possible implementation, the first configuration auxiliary information includes at least one of the following: a carrier that the second terminal device expects to configure; and a carrier supported by the terminal capability of the second terminal device.
[0207] In one possible implementation, the carrier that the second terminal device expects to configure is determined based on at least one of the following: the carrier used on the sidelink other than the first sidelink of the second terminal device; the carrier used on the uplink of the second terminal device; the carrier used on the downlink of the second terminal device; and the carrier supported by the terminal capabilities of the first terminal device.
[0208] In a possible implementation, the sending of the first configuration auxiliary information is triggered based on one or more of the following methods: periodic triggering; event triggering; and triggering based on a request of the first terminal device.
[0209] In one possible implementation, the event includes one or more of the following: a change in the link quality of the first side link; a conflict between the first side link and other communication links; a change in the carrier that the second terminal device expects to configure; the second terminal device has not sent configuration assistance information through the first side link; the first configuration assistance information changes compared to the configuration assistance information sent previously; and a change in the carrier configuration of other communication links of the second terminal device other than the first side link.
[0210] In a possible implementation, the first terminal device is located within the coverage of the network device, and / or the resource allocation mode of the first terminal device includes mode 1.
[0211] In a possible implementation, the second terminal device is located within the coverage of the network device, and the processing unit is further used to: receive the carrier configuration information sent by the second terminal device, where the carrier configuration information is based on the configuration of the first terminal device.
[0212] In a possible implementation, the above-mentioned network device also includes: a first sending unit, used to send first indication information to the second terminal device, and the first indication information is used to instruct the second terminal device to accept part or all of the configuration information in the carrier configuration information.
[0213] In a possible implementation, the above-mentioned network device also includes: a second sending unit, used to send first indication information to the second terminal device, and the first indication information is used to instruct the second terminal device to refuse to accept part or all of the configuration information in the carrier configuration information.
[0214] In one possible implementation, if the second terminal device refuses to accept part or all of the configuration information in the carrier configuration information configuration, the first terminal device performs at least one of the following operations: determining that a radio link failure occurs in the first side link; disconnecting the first side link; reconfiguring the carrier configuration information of the first side link; and sending a second indication information to the network device, where the second indication information is used to indicate whether the second terminal device accepts part or all of the configuration information in the carrier configuration information.
[0215] In an optional embodiment, the sending unit 1210 may be a transceiver 1540. The terminal device 1200 may further include a processor 1510 and a memory 1520, as specifically shown in FIG15 .
[0216] In an optional embodiment, the receiving unit 1310 may be a transceiver 1540. The terminal device 1300 may further include a processor 1510 and a memory 1520, as specifically shown in FIG15 .
[0217] In an optional embodiment, the processing unit 1420 may be the processor 1510. The network device 1400 may further include a transceiver 1530 and a memory 1520, as specifically shown in FIG15 .
[0218] Figure 15 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 15 indicate that the unit or module is optional. Apparatus 1500 may be used to implement the method described in the above method embodiment. Apparatus 1500 may be a chip, a terminal device, or a network device.
[0219] The device 1500 may include one or more processors 1510. The processor 1510 may support the device 1500 to implement the method described in the method embodiment above. The processor 1510 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
[0220] The apparatus 1500 may further include one or more memories 1520. The memories 1520 store programs that can be executed by the processor 1510, causing the processor 1510 to perform the methods described in the above method embodiments. The memories 1520 may be independent of the processor 1510 or integrated into the processor 1510.
[0221] The apparatus 1500 may further include a transceiver 1530. The processor 1510 may communicate with other devices or chips via the transceiver 1530. For example, the processor 1510 may transmit and receive data with other devices or chips via the transceiver 1530.
[0222] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.
[0223] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.
[0224] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.
[0225] It should be understood that the term "carrier" in this application can be replaced with a "carrier set." That is, a "carrier" can be configured as a "carrier set," or a "carrier" can be indicated as a "carrier set." For example, the carrier configuration information can be used to configure a carrier set on the first sidelink, where the carrier set includes at least two carriers.
[0226] In addition, the "carrier" in the embodiments of the present application may include a receiving carrier and / or a transmitting carrier. Accordingly, if the carrier includes a receiving carrier and a transmitting carrier, the carrier configuration information may include the configuration corresponding to the receiving carrier and the configuration corresponding to the transmitting carrier. The configuration corresponding to the receiving carrier and the configuration corresponding to the transmitting carrier may be independent configurations. Of course, the configuration corresponding to the receiving carrier and the configuration corresponding to the transmitting carrier may also be expressed in combination, or in other words, the configuration corresponding to the receiving carrier and the configuration corresponding to the transmitting carrier are not independent configurations.
[0227] The terms "system" and "network" in this application may be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first," "second," "third," and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions.
[0228] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.
[0229] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.
[0230] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.
[0231] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.
[0232] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.
[0233] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.
[0234] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0235] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0236] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0237] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0238] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).
[0239] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
Claims
1. A wireless communication method, characterized in that: include: The first terminal device sends carrier configuration information for the first sidelink to the second terminal device; The first sidelink is a sidelink for unicast communication between the first terminal device and the second terminal device, and the carrier configuration information is used to configure at least two carriers on the first sidelink.
2. The method according to claim 1, wherein The method further comprises: The first terminal device receives first configuration auxiliary information sent by the second terminal device, where the first configuration auxiliary information is used to determine the carrier configuration information.
3. The method according to claim 2, wherein The first configuration auxiliary information includes at least one of the following: The carrier that the second terminal device expects to be configured; and The carrier supported by the terminal capabilities of the second terminal device.
4. The method according to claim 3, wherein The carrier that the second terminal device desires to configure is determined based on at least one of the following: a carrier used by the second terminal device on other sidelinks except the first sidelink; a carrier used on the uplink of the second terminal device; a carrier used on a downlink of the second terminal device; as well as The carrier supported by the terminal capabilities of the first terminal device.
5. The method according to any one of claims 2 to 4, wherein: The sending of the first configuration auxiliary information is triggered based on one or more of the following methods: Periodic triggering; Event-triggered; and Triggered based on a request from the first terminal device.
6. The method according to claim 5, wherein The events include one or more of the following: a change in link quality of the first sidelink; There is a conflict between the first sidelink and other communication links; The carrier that the second terminal device expects to be configured changes; The second terminal device has not sent configuration auxiliary information through the first sidelink, and the configuration auxiliary information is used to determine the carrier configuration information; The first configuration auxiliary information is changed compared to the previously sent configuration auxiliary information, and the configuration auxiliary information is used to determine the carrier configuration information; as well as The carrier configuration of other communication links of the second terminal device except the first side link changes.
7. The method according to any one of claims 1 to 6, wherein The carrier configuration information is determined based on the network device.
8. The method according to any one of claims 1 to 7, wherein The first terminal device is in a connected state, and / or the resource allocation mode of the first terminal device includes mode 1.
9. The method according to claim 7 or 8, wherein The method further comprises: The first terminal device sends second configuration auxiliary information to the network device, where the second configuration auxiliary information is used to indicate the first configuration auxiliary information, and the first configuration auxiliary information is used to determine the carrier configuration information.
10. The method according to any one of claims 7 to 9, wherein The method further comprises: The first terminal device receives the carrier configuration information sent by the network device.
11. The method according to any one of claims 1 to 10, wherein The method further comprises: The first terminal device receives first indication information sent by the second terminal device, where the first indication information is used to instruct the second terminal device to accept part or all of the configuration information in the carrier configuration information.
12. The method according to any one of claims 1 to 11, wherein The method further comprises: The first terminal device receives first indication information sent by the second terminal device, where the first indication information is used to instruct the second terminal device to refuse to accept part or all of the configuration information in the carrier configuration information.
13. The method according to claim 12, wherein: The method further comprises: In response to the first indication information, the first terminal device performs one or more of the following operations: Determining that a radio link failure occurs in the first sidelink; disconnecting the first sidelink; reconfiguring carrier configuration information of the first sidelink; and Send second indication information to the network device, where the second indication information is used to indicate whether the second terminal device accepts part or all of the configuration information in the carrier configuration information.
14. The method according to any one of claims 11 to 13, wherein The first indication information is carried in a configuration completion message or a configuration failure message.
15. The method according to any one of claims 1 to 14, wherein Before the first terminal device sends the carrier configuration information to the second terminal device, the method includes: The first terminal device communicates with the second terminal device based on a carrier set; The carrier set includes one or more of the following: A carrier determined based on preconfigured information; and The carrier is determined based on the configured service-to-carrier mapping rules.
16. A wireless communication method, characterized in that: include: The second terminal device receives the carrier configuration information for the first sidelink sent by the first terminal device; The first sidelink is a sidelink for unicast communication between the first terminal device and the second terminal device, and the carrier configuration information is used to configure at least two carriers on the first sidelink.
17. The method according to claim 16, wherein The method further comprises: The second terminal device sends first configuration auxiliary information to the first terminal device, where the first configuration auxiliary information is used to determine the carrier configuration information.
18. The method according to claim 17, wherein The first configuration auxiliary information includes at least one of the following: The carrier that the second terminal device expects to be configured; The carrier supported by the terminal capabilities of the second terminal device.
19. The method according to claim 18, wherein The carrier that the second terminal device desires to configure is determined based on at least one of the following: a carrier used by the second terminal device on other sidelinks except the first sidelink; a carrier used on the uplink of the second terminal device; A carrier used on the downlink of the second terminal device; a carrier supported by the terminal capability of the first terminal device.
20. The method according to any one of claims 17 to 19, wherein The sending of the first configuration auxiliary information is triggered based on one or more of the following methods: Periodic triggering; Event-triggered; Triggered based on a request from the first terminal device.
21. The method according to claim 20, wherein The events include one or more of the following: a change in link quality of the first sidelink; There is a conflict between the first sidelink and other communication links; The carrier that the second terminal device expects to be configured changes; The second terminal device has not sent configuration auxiliary information through the first sidelink, and the configuration auxiliary information is used to determine the carrier configuration information; The first configuration auxiliary information is changed compared to the previously sent configuration auxiliary information, and the configuration auxiliary information is used to determine the carrier configuration information; as well as The carrier configuration of other communication links of the second terminal device except the first side link changes.
22. The method according to any one of claims 16 to 21, wherein The carrier configuration information is determined based on the network device.
23. The method according to any one of claims 16 to 22, wherein: The first terminal device is located within the coverage of the network device, and / or the resource allocation mode of the first terminal device includes mode 1.
24. The method according to any one of claims 16 to 23, wherein The second terminal device is within the coverage range of the network device, and the method further includes: The second terminal device sends the carrier configuration information to the network device.
25. The method of claim 24, wherein: The method further comprises: The second terminal device receives first indication information sent by the network device, where the first indication information is used to instruct the second terminal device to accept part or all of the configuration information in the carrier configuration information, or, The first indication information is used to instruct the second terminal device to refuse to accept part or all of the configuration information in the carrier configuration information.
26. The method according to any one of claims 16 to 25, wherein If the second terminal device refuses to accept part or all of the configuration information in the carrier configuration information, the first terminal device performs one or more of the following operations: Determining that a radio link failure occurs in the first sidelink; disconnecting the first sidelink; reconfiguring carrier configuration information of the first sidelink; as well as Send second indication information to the network device, where the second indication information is used to indicate whether the second terminal device accepts part or all of the configuration information in the carrier configuration information.
27. The method according to claim 25 or 26, wherein The method further comprises: The second terminal device sends the first indication information to the first terminal device.
28. The method according to any one of claims 25 to 27, wherein The first indication information is carried in a configuration completion message or a configuration failure message.
29. The method according to any one of claims 16 to 28, wherein Before the second terminal device receives the carrier configuration information sent by the first terminal device, the method further includes: The second terminal device communicates with the first terminal device based on a carrier set; The carrier set includes one or more of the following: the default carrier; and The carrier is determined based on the configured mapping rules between service types and carriers.
30. A wireless communication method, characterized in that: include: The network device determines carrier configuration information for the first sidelink; The first sidelink is a sidelink for unicast communication between the first terminal device and the second terminal device, and the carrier configuration information is used to configure multiple carriers on the first sidelink.
31. The method of claim 30, wherein: The method further comprises: The network device receives second configuration auxiliary information sent by the first terminal device; The network device determines the carrier configuration information, including: The network device determines the carrier configuration information based on the second configuration auxiliary information.
32. The method of claim 31, wherein The second configuration auxiliary information is determined based on the first configuration auxiliary information, and the first configuration auxiliary information is used to determine the carrier configuration information.
33. The method of claim 32, wherein: The first configuration auxiliary information includes at least one of the following: The carrier that the second terminal device expects to be configured; and The carrier supported by the terminal capabilities of the second terminal device.
34. The method of claim 33, wherein: The carrier that the second terminal device desires to configure is determined based on at least one of the following: a carrier used by the second terminal device on other sidelinks except the first sidelink; a carrier used on the uplink of the second terminal device; a carrier used on a downlink of the second terminal device; as well as The carrier supported by the terminal capabilities of the first terminal device.
35. The method according to any one of claims 32 to 34, wherein The sending of the first configuration auxiliary information is triggered based on one or more of the following methods: Periodic triggering; Event-triggered; and Triggered based on a request from the first terminal device.
36. The method of claim 35, wherein: The events include one or more of the following: a change in link quality of the first sidelink; There is a conflict between the first sidelink and other communication links; The carrier that the second terminal device expects to be configured changes; The second terminal device has not sent configuration auxiliary information through the first sidelink; The first configuration auxiliary information has changed compared to the previously sent configuration auxiliary information; as well as The carrier configuration of other communication links of the second terminal device except the first side link changes.
37. The method according to any one of claims 31 to 36, wherein The first terminal device is located within the coverage of the network device, and / or the resource allocation mode of the first terminal device includes mode 1.
38. The method of claim 30, wherein: The second terminal device is located within the coverage of the network device, and the network device determines the carrier configuration information, including: The network device receives the carrier configuration information sent by the second terminal device, where the carrier configuration information is configured based on the first terminal device.
39. The method according to any one of claims 30 to 38, wherein The method further comprises: The network device sends first indication information to the second terminal device, where the first indication information is used to instruct the second terminal device to accept part or all of the configuration information in the carrier configuration information.
40. The method according to any one of claims 30 to 38, wherein The method further comprises: The network device sends first indication information to the second terminal device, where the first indication information is used to instruct the second terminal device to refuse to accept part or all of the configuration information in the carrier configuration information.
41. The method of claim 40, wherein: If the second terminal device refuses to accept part or all of the configuration information in the carrier configuration information configuration, the first terminal device performs at least one of the following operations: Determining that a radio link failure occurs in the first sidelink; disconnecting the first sidelink; reconfiguring carrier configuration information of the first sidelink; as well as Send second indication information to the network device, where the second indication information is used to indicate whether the second terminal device accepts part or all of the configuration information in the carrier configuration information.
42. A first terminal device, characterized in that: include: A sending unit, configured to send carrier configuration information for the first sidelink to the second terminal device; The first sidelink is a sidelink for unicast communication between the first terminal device and the second terminal device, and the carrier configuration information is used to configure at least two carriers on the first sidelink.
43. The first terminal device according to claim 42, characterized in that Also includes: The first receiving unit is used to receive first configuration auxiliary information sent by the second terminal device, where the first configuration auxiliary information is used to determine the carrier configuration information.
44. The first terminal device according to claim 43, characterized in that The first configuration auxiliary information includes at least one of the following: The carrier that the second terminal device expects to be configured; and The carrier supported by the terminal capabilities of the second terminal device.
45. The first terminal device according to claim 44, characterized in that The carrier that the second terminal device desires to configure is determined based on at least one of the following: a carrier used by the second terminal device on other sidelinks except the first sidelink; a carrier used on the uplink of the second terminal device; a carrier used on a downlink of the second terminal device; as well as The carrier supported by the terminal capabilities of the first terminal device.
46. The first terminal device according to any one of claims 43 to 45, characterized in that: The sending of the first configuration auxiliary information is triggered based on one or more of the following methods: Periodic triggering; Event-triggered; and Triggered based on a request from the first terminal device.
47. The first terminal device according to claim 46, characterized in that The events include one or more of the following: a change in link quality of the first sidelink; There is a conflict between the first sidelink and other communication links; The carrier that the second terminal device expects to be configured changes; The second terminal device has not sent configuration auxiliary information through the first sidelink, and the configuration auxiliary information is used to determine the carrier configuration information; The first configuration auxiliary information is changed compared to the previously sent configuration auxiliary information, and the configuration auxiliary information is used to determine the carrier configuration information; as well as The carrier configuration of other communication links of the second terminal device except the first side link changes.
48. The first terminal device according to any one of claims 42 to 47, characterized in that: The carrier configuration information is determined based on the network device.
49. The first terminal device according to any one of claims 42 to 48, characterized in that: The first terminal device is in a connected state, and / or the resource allocation mode of the first terminal device includes mode 1.
50. The first terminal device according to claim 48 or 49, characterized in that: The sending unit is further configured to: Second configuration auxiliary information is sent to the network device, where the second configuration auxiliary information is used to indicate the first configuration auxiliary information, and the first configuration auxiliary information is used to determine the carrier configuration information.
51. The first terminal device according to any one of claims 48 to 50, characterized in that: Also includes: The second receiving unit is configured to receive the carrier configuration information sent by the network device.
52. The first terminal device according to any one of claims 42 to 51, characterized in that: Also includes: The third receiving unit is used to receive the first indication information sent by the second terminal device, where the first indication information is used to instruct the second terminal device to accept part or all of the configuration information in the carrier configuration information.
53. The first terminal device according to any one of claims 42 to 52, characterized in that: Also includes: The fourth receiving unit is used to receive the first indication information sent by the second terminal device, where the first indication information is used to instruct the second terminal device to refuse to accept part or all of the configuration information in the carrier configuration information.
54. The first terminal device according to claim 53, characterized in that Also includes: a processing unit, configured to perform one or more of the following operations in response to the first indication information: Determining that a radio link failure occurs in the first sidelink; disconnecting the first sidelink; reconfiguring carrier configuration information of the first sidelink; as well as Send second indication information to the network device, where the second indication information is used to indicate whether the second terminal device accepts part or all of the configuration information in the carrier configuration information.
55. The first terminal device according to any one of claims 52 to 54, characterized in that: The first indication information is carried in a configuration completion message or a configuration failure message.
56. The first terminal device according to any one of claims 42 to 55, characterized in that: Also includes: a communication unit, configured to communicate with the second terminal device based on a carrier set; The carrier set includes one or more of the following: A carrier determined based on preconfigured information; as well as The carrier is determined based on the configured service-to-carrier mapping rules.
57. A second terminal device, characterized in that: include: A receiving unit, configured to receive carrier configuration information for a first sidelink sent by a first terminal device; The first sidelink is a sidelink for unicast communication between the first terminal device and the second terminal device, and the carrier configuration information is used to configure at least two carriers on the first sidelink.
58. The second terminal device according to claim 57, characterized in that Also includes: The first sending unit is used to send first configuration auxiliary information to the first terminal device, where the first configuration auxiliary information is used to determine the carrier configuration information.
59. The second terminal device according to claim 58, characterized in that The first configuration auxiliary information includes at least one of the following: The carrier that the second terminal device expects to be configured; The carrier supported by the terminal capabilities of the second terminal device.
60. The second terminal device according to claim 59, wherein: The carrier that the second terminal device desires to configure is determined based on at least one of the following: a carrier used by the second terminal device on other sidelinks except the first sidelink; a carrier used on the uplink of the second terminal device; A carrier used on the downlink of the second terminal device; a carrier supported by the terminal capability of the first terminal device.
61. The second terminal device according to any one of claims 58 to 60, characterized in that: The sending of the first configuration auxiliary information is triggered based on one or more of the following methods: Periodic triggering; Event-triggered; Triggered based on a request from the first terminal device.
62. The second terminal device according to claim 61, characterized in that The events include one or more of the following: a change in link quality of the first sidelink; There is a conflict between the first sidelink and other communication links; The carrier that the second terminal device expects to be configured changes; The second terminal device has not sent configuration auxiliary information through the first sidelink, and the configuration auxiliary information is used to determine the carrier configuration information; The first configuration auxiliary information is changed compared to the previously sent configuration auxiliary information, and the configuration auxiliary information is used to determine the carrier configuration information; as well as The carrier configuration of other communication links of the second terminal device except the first side link changes.
63. The second terminal device according to any one of claims 57 to 62, characterized in that: The carrier configuration information is determined based on the network device.
64. The second terminal device according to any one of claims 57 to 63, characterized in that: The first terminal device is located within the coverage of the network device, and / or the resource allocation mode of the first terminal device includes mode 1.
65. The second terminal device according to any one of claims 57 to 64, characterized in that: The second terminal device is located within the coverage area of the network device, and further includes: The second sending unit is configured to send the carrier configuration information to the network device.
66. The second terminal device according to claim 65, characterized in that The receiving unit is further configured to: receiving first indication information sent by the network device, where the first indication information is used to instruct the second terminal device to accept part or all of the configuration information in the carrier configuration information, or, The first indication information is used to instruct the second terminal device to refuse to accept part or all of the configuration information in the carrier configuration information.
67. The second terminal device according to any one of claims 57 to 66, characterized in that: If the second terminal device refuses to accept part or all of the configuration information in the carrier configuration information, the first terminal device performs one or more of the following operations: Determining that a radio link failure occurs in the first sidelink; disconnecting the first sidelink; reconfiguring carrier configuration information of the first sidelink; as well as Send second indication information to the network device, where the second indication information is used to indicate whether the second terminal device accepts part or all of the configuration information in the carrier configuration information.
68. The second terminal device according to claim 66 or 67, characterized in that: Also includes: The third sending unit is used to send the first indication information to the first terminal device.
69. The second terminal device according to any one of claims 66 to 68, characterized in that: The first indication information is carried in a configuration completion message or a configuration failure message.
70. The second terminal device according to any one of claims 57 to 69, characterized in that: Also includes: a communication unit, configured to communicate with the first terminal device based on a carrier set; The carrier set includes one or more of the following: Default carrier; as well as The carrier is determined based on the configured mapping rules between service types and carriers.
71. A network device, characterized in that include: A processing unit, determining carrier configuration information for a first sidelink; The first sidelink is a sidelink for unicast communication between the first terminal device and the second terminal device, and the carrier configuration information is used to configure multiple carriers on the first sidelink.
72. The network device according to claim 71, wherein: Also includes: A first receiving unit, configured to receive second configuration auxiliary information sent by the first terminal device; The processing unit is further configured to determine the carrier configuration information based on the second configuration auxiliary information.
73. The network device according to claim 72, wherein: The second configuration auxiliary information is determined based on the first configuration auxiliary information, and the first configuration auxiliary information is used to determine the carrier configuration information.
74. The network device according to claim 73, wherein The first configuration auxiliary information includes at least one of the following: The carrier that the second terminal device expects to be configured; and The carrier supported by the terminal capabilities of the second terminal device.
75. The network device according to claim 74, wherein: The carrier that the second terminal device desires to configure is determined based on at least one of the following: a carrier used by the second terminal device on other sidelinks except the first sidelink; a carrier used on the uplink of the second terminal device; a carrier used on a downlink of the second terminal device; as well as The carrier supported by the terminal capabilities of the first terminal device.
76. The network device according to any one of claims 73 to 75, wherein: The sending of the first configuration auxiliary information is triggered based on one or more of the following methods: Periodic triggering; Event-triggered; and Triggered based on a request from the first terminal device.
77. The network device according to claim 76, wherein: The events include one or more of the following: a change in link quality of the first sidelink; There is a conflict between the first sidelink and other communication links; The carrier that the second terminal device expects to be configured changes; The second terminal device has not sent configuration auxiliary information through the first sidelink; The first configuration auxiliary information has changed compared to the previously sent configuration auxiliary information; as well as The carrier configuration of other communication links of the second terminal device except the first side link changes.
78. The network device according to any one of claims 72 to 77, wherein: The first terminal device is located within the coverage of the network device, and / or the resource allocation mode of the first terminal device includes mode 1.
79. The network device according to claim 71, wherein The second terminal device is located within the coverage of the network device, and the network device determines the carrier configuration information, including: The network device receives the carrier configuration information sent by the second terminal device, where the carrier configuration information is configured based on the first terminal device.
80. The network device according to any one of claims 71 to 79, wherein: Also includes: The first sending unit is used to send first indication information to the second terminal device, where the first indication information is used to instruct the second terminal device to accept part or all of the configuration information in the carrier configuration information.
81. The network device according to any one of claims 71 to 79, wherein: Also includes: The second sending unit is used to send first indication information to the second terminal device, where the first indication information is used to instruct the second terminal device to refuse to accept part or all of the configuration information in the carrier configuration information.
82. The network device according to claim 81, wherein If the second terminal device refuses to accept part or all of the configuration information in the carrier configuration information configuration, the first terminal device performs at least one of the following operations: Determining that a radio link failure occurs in the first sidelink; disconnecting the first sidelink; reconfiguring carrier configuration information of the first sidelink; as well as Send second indication information to the network device, where the second indication information is used to indicate whether the second terminal device accepts part or all of the configuration information in the carrier configuration information.
83. A terminal device, characterized in that: The terminal device comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the terminal device executes the method according to any one of claims 1 to 29.
84. A network device, characterized in that The network device comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so as to enable the network device to execute the method according to any one of claims 30 to 41.
85. A device, characterized in that The device comprises a processor configured to call a program from a memory so as to cause the device to execute the method according to any one of claims 1 to 41.
86. A chip, characterized in that The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 41.
87. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 41.
88. A computer program product, characterized in that The method comprises a program for causing a computer to execute the method according to any one of claims 1 to 41.
89. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 41.