Lateral communication method and device

Abstract

The invention relates to a sidewalk communication method and a sidewalk communication device, aiming at solving the problem that QoS (Quality of Service) flows supporting different carriers are mapped to the same SLRB (Service Link Resource Block) to reduce SL (Service Link) communication quality. The method comprises: a terminal device sending first information to a network device, the first information comprising: a first destination address, a first carrier index and a first quality of service (QoS) parameter, the first destination address, the first carrier index and the first QoS parameter having a corresponding relationship; a network device receives first information from a terminal device, the network device determines and sends configuration information of a sidelink bearer SLRB to the terminal device according to the first information, and the terminal device receives the configuration information of the sidelink bearer SLRB from the network device.

Description

[0001] This application is a divisional application. The application number of the original application is 201980103023.6, the filing date of the original application is December 31, 2019, and the entire content of the original application is incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technologies, and in particular, to a sidelink communication method and apparatus. Background Art

[0003] The 3rd Generation Partnership Project (3GPP) international standardization organization has been conducting research on vehicle-to-everything (V2X) since Release 14 of Long Term Evolution (LTE), and has proposed a V2X communication architecture. In the V2X communication architecture, terminal devices can directly transmit data to each other through a sidelink (SL).

[0004] Before a terminal device performs SL communication, the terminal device obtains configuration information of a sidelink radio bearer (SLRB) from a network device. The terminal device establishes an SLRB according to the configuration information of the SLRB and maps quality of service (QoS) flows to the corresponding SLRB. Since different QoS flows under a destination address may support different carriers, the terminal device may map QoS flows that support different carriers to the same SLRB. When transmitting data in the corresponding SLRB based on a certain carrier resource, some QoS flows may perform SL communication based on a carrier that they do not support, thereby reducing the SL communication quality. Summary of the Invention

[0005] This application provides a sidelink communication method and apparatus, aiming to solve the problem of reducing the SL communication quality by mapping QoS flows that support different carriers to the same SLRB.

[0006] In a first aspect, a sidelink communication method is provided. The method includes the following steps: A terminal device sends first information to a network device. The first information includes: a first destination address, a first carrier index, and a first quality of service (QoS) parameter. There is a corresponding relationship among the first destination address, the first carrier index, and the first QoS parameter. In this way, through the first information, the terminal device can indicate to the network device the carrier information corresponding to each QoS parameter under the destination address. The network device determines the sidelink radio bearer (SLRB) configuration according to this corresponding relationship, and can map the QoS flow configuration to the SLRB corresponding to the carrier supported by the QoS flow, avoiding the packets of the QoS flow using the carrier frequency that it does not support for sidelink (SL) transmission. Thereby, the accuracy of the SLRB configuration is improved, and the SL communication quality is improved.

[0007] In a possible design, the terminal device receives the configuration information of a sidelink radio bearer (SLRB) from the network device. The SLRB configuration determined by the network device is determined according to the carrier supported by the QoS flow. After receiving the SLRB configuration information, the terminal device will not map the QoS flow to the SLRB corresponding to the carrier that it does not support, improving the SL communication quality.

[0008] In a possible design, the first information further includes the second carrier index; there is a corresponding relationship between the first QoS parameter and the second carrier index.

[0009] In a possible design, the first information further includes the second QoS parameter, and there is a corresponding relationship between the second QoS parameter and the first carrier index.

[0010] In a possible design, the QoS parameter includes a QoS flow identifier and / or a QoS profile.

[0011] In a possible design, the SLRB configuration information includes one or more of a QoS parameter, destination address information, and carrier information.

[0012] In a possible design, the reporting manner of the first information can be in the manner of full information reporting or delta information reporting.

[0013] Second aspect, a sidelink communication method is provided. The method includes the following steps: A terminal device sends first information to a network device. The first information includes: a first destination address, a first carrier index, and at least one quality of service (QoS) parameter. There is a corresponding relationship among the first destination address, the first carrier index, and the at least one QoS parameter. All QoS flows corresponding to the at least one QoS parameter support the carrier indicated by the first carrier index. By reporting to the network device the carrier index of the carrier supported by all QoS flows corresponding to the QoS parameter under the destination address, when the network device configures an SLRB according to the reported first information after receiving it, it will not configure a carrier that is not supported by the QoS flows of this destination address, avoiding the use of a carrier frequency not supported by the data packets of the QoS flow for SL transmission. Thereby, the configuration accuracy of the SLRB is improved, and the sidelink communication quality is improved.

[0014] Among them, that all QoS flows corresponding to at least one QoS parameter support the carrier indicated by the first carrier index can be understood as that all QoS flows corresponding to at least one QoS parameter under the first destination address support SL transmission on the first carrier indicated by the first carrier index.

[0015] In a possible design, after the terminal device sends the first information to the network device, the terminal device receives configuration information of a sidelink radio bearer (SLRB) from the network device.

[0016] Optionally, if the index of the carrier supported by all QoS flows corresponding to multiple QoS parameters associated with the same QoS profile under the destination address is an empty set, the access stratum of the terminal device sends an indication message to the upper layer (such as the V2X layer). This indication message is used to indicate that the QoS flows or services corresponding to the same QoS profile associated with this destination address are unreasonable. Optionally, after receiving the indication message, the upper layer of the terminal device triggers a PC5-S link modification process with the peer terminal device, or modifies the information of the QoS parameter / service associated with this destination address.

[0017] Optionally, if the index of the carrier supported by all QoS flows corresponding to multiple QoS parameters associated with the same QoS profile under the first destination address is an empty set, the first destination address in the first information reported by the terminal device to the network device does not include the information of the multiple QoS flows, indicating that no carrier index supports the SL transmission of the QoS flows corresponding to the multiple QoS parameters under the first destination address. Alternatively, the multiple QoS parameters are associated with an indication message, and this indication message is used to indicate that no carrier index supports the SL transmission of the QoS flows corresponding to the multiple QoS parameters under the first destination address.

[0018] In a possible design, the QoS parameter includes a QoS flow identifier and / or a QoS file.

[0019] In a possible design, the method further includes: the terminal device obtains second information, where the second information includes a service identifier and a first carrier index; the terminal device determines that the QoS flow under the service corresponding to the service identifier supports the carrier indicated by the first carrier index.

[0020] In a possible design, the destination address can be represented by a destination address identifier and / or a communication type.

[0021] In a possible design, the SLRB configuration information includes one or more of a QoS parameter, destination address information, and carrier information.

[0022] In a third aspect, a sidelink communication method is provided. The method includes the following steps: the terminal device obtains configuration information of a sidelink radio bearer (SLRB), where the configuration information of the sidelink radio bearer (SLRB) includes one or more quality of service (QoS) parameters; the terminal device establishes an SLRB for a destination address according to the configuration information of the SLRB, and associates the SLRB with one or more QoS parameters corresponding to the destination address; the terminal device determines carrier information supported by the SLRB; the carrier information is carrier information supported by all of the one or more QoS flow information corresponding to the destination address information. In this way, when mapping QoS flows associated with different carrier information to the same SLRB / LCH based on network configuration, the terminal can determine the carrier information allowed by the SLRB / LCH, so that it will not use non-allowed carrier information for SL transmission.

[0023] Optionally, considering PDCP duplication, one SLRB is associated with multiple logical channel headers (LCHs). When the terminal device determines the carrier information supported by the SLRB, if the number of supported carrier information is less than the number of LCHs associated with the SLRB itself, the terminal device selects some LCHs for SL transmission based on PDCP duplication. Ensure normal SL communication.

[0024] In a possible design, the QoS flow information includes one or more of a QoS flow identifier, a QoS file, and destination address information.

[0025] In a possible design, the terminal device obtains configuration information of a sidelink radio bearer (SLRB) in the following possible ways: the terminal device obtains the SLRB configuration information through an RRC message, a broadcast message, or pre-configuration.

[0026] Fourthly, a sidelink communication method is provided, and the method includes the following steps: A terminal device obtains configuration information of a sidelink radio bearer (SLRB), where the SLRB configuration information includes M quality of service (QoS) parameters, and the M QoS flow information is associated with different lists of M carrier information, and M is an integer greater than 1; The terminal device determines that among the M QoS parameters corresponding to the first destination address, the carriers supported by the QoS flows corresponding to N QoS parameters are not completely the same; The terminal device establishes N SLRBs for the QoS flows corresponding to the N QoS parameters corresponding to the first destination address; where the QoS flows corresponding to the N QoS parameters corresponding to the first destination address correspond to the N SLRBs one by one. The terminal device can establish multiple SLRBs / LCHs under one destination address based on the configuration information of one SLRB, so as to ensure that the QoS flows mapped to one SLRB / LCH are all associated with the same carrier information, so that SL transmission can be carried out normally.

[0027] In a possible design, the terminal device assigns different SLRB identifiers or logical channel (LCH) identifiers to the M SLRBs.

[0028] In a possible design, the M SLRBs have the same PDCP entity parameters, RLC entity parameters, and LCH parameters.

[0029] In a possible design, the QoS parameter includes one or more of a QoS flow identifier, a QoS profile, and destination address information.

[0030] In a possible design, the terminal device obtains the configuration information of the sidelink radio bearer (SLRB) in the following manner: The terminal device obtains the SLRB configuration information through an RRC message, a broadcast message, or pre-configuration.

[0031] Fifthly, a sidelink communication method is provided, and the method includes the following steps: A network device receives first information from a terminal device, where the first information includes: a first destination address, a first carrier index, and a first quality of service (QoS) parameter, and there is a corresponding relationship among the first destination address, the first carrier index, and the first QoS parameter; The network device determines and sends configuration information of a sidelink radio bearer (SLRB) to the terminal device according to the first information. In this way, the network device receives the first information from the terminal device, and the first information includes the above corresponding relationship. The network device can determine the SLRB configuration according to this corresponding relationship, and can map the QoS flow configuration to the SLRB corresponding to the carrier supported by the QoS flow, avoiding the SL transmission of the data packets of the QoS flow using the carrier frequency that it does not support. Thereby improving the accuracy of the SLRB configuration and improving the SL communication quality.

[0032] In a possible design, the first information further includes the second carrier index; the first QoS parameter has a corresponding relationship with the second carrier index.

[0033] In a possible design, the first information further includes the second QoS parameter, and the second QoS parameter has a corresponding relationship with the first carrier index.

[0034] In a possible design, the QoS parameter includes a QoS flow identifier and / or a QoS profile.

[0035] In a possible design, the SLRB configuration information includes one or more of a QoS parameter, destination address information, and carrier information.

[0036] In a sixth aspect, a sidelink communication method is provided. The method includes the following steps: A network device receives first information from a terminal device. The first information includes: a first destination address, a first carrier index, and at least one quality of service (QoS) parameter. The first destination address, the first carrier index, and the at least one QoS parameter have a corresponding relationship, and all QoS flows corresponding to the at least one QoS parameter support the carrier indicated by the first carrier index; The network device determines, according to the first information, and sends configuration information of a sidelink radio bearer (SLRB) to the terminal device. By means of the carrier index of the carrier supported by all QoS flows corresponding to the QoS parameter under the destination address received by the network device from the terminal, when the network device configures the SLRB for the terminal according to the first information after receiving the reported first information, it will not configure a carrier that is not supported by the QoS flows of the destination address, thus avoiding the use of a carrier frequency not supported by the data packets of the QoS flows for SL transmission. Therefore, the configuration accuracy of the SLRB is improved, and the sidelink communication quality is improved.

[0037] Among them, that all QoS flows corresponding to at least one QoS parameter support the carrier indicated by the first carrier index can be understood as that all QoS flows corresponding to at least one QoS parameter under the first destination address support SL transmission on the first carrier indicated by the first carrier index.

[0038] In a possible design, the QoS parameter includes a QoS flow identifier and / or a QoS profile.

[0039] In a possible design, the destination address can be represented by a destination address identifier and / or a communication type.

[0040] In a possible design, the SLRB configuration information includes one or more of a QoS parameter, destination address information, and carrier information.

[0041] In a seventh aspect, a sidelink communication method is provided. The execution entity of this method can be a terminal device, and the method includes the following steps: The terminal device obtains the correspondence between geographical area information and carrier information; the terminal device determines the carrier information supported by sidelink (SL) communication in the current geographical area according to the correspondence between the geographical area information and the carrier information. Through the above process, the terminal device determines the carrier information supported by the current geographical area to perform subsequent SL communication, ensuring compliance with policies and regulations and the quality of SL communication.

[0042] Optionally, the terminal device can obtain the correspondence between geographical area information and carrier information through RRC messages, SIB messages, or pre-configuration. The state of the terminal device can be in the RRC connected state or the RRC non-connected state.

[0043] Optionally, the carrier information can include a carrier index and / or the synchronization type supported by the carrier.

[0044] Optionally, different geographical area information can also correspond to the same carrier information.

[0045] Optionally, the geographical location can be at the national or regional level, for example, different countries or regions correspond to different geographical areas.

[0046] Optionally, the geographical location can be at the cell level, for example, different cells correspond to different geographical areas.

[0047] Optionally, the geographical location can be at the zone level, for example, different zones within a cell correspond to different geographical areas.

[0048] In an eighth aspect, a device is provided. The device may be a terminal device, or a device located in the terminal device (for example, a chip, or a chip system, or a circuit), or a device that can be used in combination with the terminal device. In one design, the device may include modules corresponding one by one to the methods / operations / steps / actions described in the first aspect. The module may be a hardware circuit, software, or a combination of hardware circuit and software. In one design, the device may include a processing module and a communication module. The processing module is used to call the communication module to perform the functions of receiving and / or sending. Exemplarily, the communication module is used to send first information to a network device, where the first information includes: a first destination address, a first carrier index, and a first quality of service (QoS) parameter. The first destination address, the first carrier index, and the first QoS parameter have a corresponding relationship, and is used to receive configuration information of a sidelink radio bearer (SLRB) from the network device. In this way, through the first information, the terminal device can indicate to the network device the carrier information corresponding to each QoS parameter under the destination address. The network device determines the SLRB configuration according to this corresponding relationship, and can map the QoS flow configuration to the SLRB corresponding to the carrier supported by the QoS flow, avoiding the use of a carrier frequency that the QoS flow does not support for sidelink (SL) transmission. Thereby, the accuracy of the SLRB configuration is improved, and the SL communication quality is improved.

[0049] In a possible design, the first information further includes the second carrier index; the first QoS parameter has a corresponding relationship with the second carrier index.

[0050] In a possible design, the first information further includes the second QoS parameter, and the second QoS parameter has a corresponding relationship with the first carrier index.

[0051] In a possible design, the QoS parameter includes a QoS flow identifier and / or a QoS profile.

[0052] In a possible design, the SLRB configuration information includes one or more of a QoS parameter, destination address information, and carrier information.

[0053] In a possible design, the reporting manner of the first information may be in the form of full information reporting or delta information reporting.

[0054] In a ninth aspect, a device is provided. The device may be a terminal device, or a device located in the terminal device (for example, a chip, or a chip system, or a circuit), or a device that can be used in combination with the terminal device. In one design, the device may include modules corresponding one by one to the methods / operations / steps / actions described in the second aspect. The module may be a hardware circuit, software, or a combination of hardware circuit and software. In one design, the device may include a processing module and a communication module. The processing module is used to call the communication module to perform the functions of receiving and / or sending. Exemplarily:

[0055] The processing module is used to call the communication module to send first information to a network device. The first information includes: a first destination address, a first carrier index, and at least one quality of service (QoS) parameter. There is a corresponding relationship among the first destination address, the first carrier index, and the at least one QoS parameter. All QoS flows corresponding to the at least one QoS parameter support the carrier indicated by the first carrier index. And it is used to receive configuration information of a sidelink radio bearer (SLRB) from the network device. By reporting, by the terminal device, the carrier index of the carrier supported by all QoS flows corresponding to the QoS parameters under the destination address to the network device, when the network device configures the SLRB according to the reported first information, it will not configure a carrier that is not supported by the QoS flows of this destination address, thus avoiding the use of a carrier frequency not supported by the data packets of the QoS flows for SL transmission. Thereby improving the configuration accuracy of the SLRB and improving the SL communication quality.

[0056] Among them, that all QoS flows corresponding to at least one QoS parameter support the carrier indicated by the first carrier index can be understood as that all QoS flows corresponding to at least one QoS parameter under the first destination address support SL transmission on the first carrier indicated by the first carrier index.

[0057] Optionally, if the index of the carrier supported by all QoS flows corresponding to multiple QoS parameters associated with a destination address and having the same QoS profile is an empty set, the access stratum of the terminal device sends indication information to the upper layer (for example, the V2X layer). The indication information is used to indicate that the QoS flows or services corresponding to the same QoS profile associated with this destination address are unreasonable. Optionally, after receiving the indication information, the upper layer of the terminal device triggers a PC5-S link modification process with the peer terminal device, or modifies the information of the QoS parameters / services associated with this destination address.

[0058] Optionally, if the index of the carrier supported by all QoS flows with the same QoS file associated with the first destination address is an empty set, the first destination address in the first information reported by the terminal device to the network device does not include the information of the multiple QoS flows, indicating that no SL transmission of the carrier indexes corresponding to the multiple QoS parameters is supported for the first destination address. Alternatively, the multiple QoS parameters are associated with an indication information, which is used to indicate that no SL transmission of the carrier indexes corresponding to the multiple QoS parameters is supported for the first destination address.

[0059] In a possible design, the QoS parameter includes a QoS flow identifier and / or a QoS file.

[0060] In a possible design, the processing module is further configured to obtain second information, where the second information includes a service identifier and a first carrier index; and to determine that the QoS flow under the service corresponding to the service identifier supports the carrier indicated by the first carrier index.

[0061] In a possible design, the destination address may be represented by a destination address identifier and / or a communication type.

[0062] In a possible design, the SLRB configuration information includes one or more of QoS parameters, destination address information, and carrier information.

[0063] In a tenth aspect, a device is provided. The device may be a terminal device, or a device located in the terminal device (for example, a chip, or a chip system, or a circuit), or a device that can be used in combination with the terminal device. In one design, the device may include modules corresponding one by one to the methods / operations / steps / actions described in the third aspect. The module may be a hardware circuit, or software, or a combination of a hardware circuit and software. In one design, the device may include a processing module and a communication module. The processing module is configured to call the communication module to perform the functions of receiving and / or sending. Exemplarily:

[0064] The processing module is used to obtain the configuration information of the sidelink radio bearer (SLRB), where the configuration information of the SLRB includes one or more quality of service (QoS) parameters; and is used to establish an SLRB for a destination address according to the configuration information of the SLRB, where the SLRB is associated with one or more QoS parameters corresponding to the destination address; and is used to determine the carrier information supported by the SLRB; the carrier information is the carrier information supported by all of the one or more QoS flow information corresponding to the destination address information. In this way, when mapping QoS flows associated with different carrier information to the same SLRB / LCH based on network configuration, the terminal can determine the carrier information allowed by the SLRB / LCH, so that it will not use disallowed carrier information for sidelink (SL) transmission.

[0065] Optionally, considering PDCP duplication, one SLRB is associated with multiple logical channel hierarchies (LCHs). When the terminal device determines the carrier information supported by the SLRB, if the number of supported carrier information is less than the number of LCHs associated with the SLRB itself, the terminal device selects some LCHs for SL transmission based on PDCP duplication to ensure normal SL communication.

[0066] In a possible design, the QoS flow information includes one or more of a QoS flow identifier, a QoS profile, and destination address information.

[0067] In a possible design, when obtaining the configuration information of the sidelink radio bearer (SLRB), the processing module is specifically configured to obtain the SLRB configuration information through an RRC message, a broadcast message, or pre-configuration.

[0068] In a tenth aspect, there is provided a device, which may be a terminal device, or a device located in the terminal device (for example, a chip, or a chip system, or a circuit), or a device that can be used in conjunction with the terminal device. In one design, the device may include modules corresponding one by one to the methods / operations / steps / actions described in the fourth aspect, and the module may be a hardware circuit, software, or a combination of a hardware circuit and software. In one design, the device may include a processing module and a communication module. The processing module is used to call the communication module to perform the functions of receiving and / or sending. Exemplarily:

[0069] The processing module is used to obtain the configuration information of the sidelink radio bearer (SLRB). Among them, the SLRB configuration information includes M quality of service (QoS) parameters. The M QoS flow information is associated with different lists of M carrier information. M is an integer greater than 1. And it is used to determine that among the M QoS parameters corresponding to the first destination address, the carriers supported by the QoS flows corresponding to N QoS parameters are not completely the same. And it is used to establish N SLRBs for the QoS flows corresponding to the N QoS parameters corresponding to the first destination address. Among them, the QoS flows corresponding to the N QoS parameters corresponding to the first destination address are in one-to-one correspondence with the N SLRBs. The terminal device can establish multiple SLRBs / LCHs under one destination address based on the configuration information of one SLRB, which can ensure that the QoS flows mapped to one SLRB / LCH are all associated with the same carrier information, so that SL transmission can be carried out normally.

[0070] In a possible design, the processing module is further used to allocate different SLRB identifiers or logical channel (LCH) identifiers to the M SLRBs.

[0071] In a possible design, the M SLRBs have the same PDCP entity parameters, RLC entity parameters, and LCH parameters.

[0072] In a possible design, the QoS parameters include one or more of QoS flow identifier, QoS file, and destination address information.

[0073] In a possible design, when obtaining the configuration information of the sidelink radio bearer (SLRB), the processing module is specifically used to: obtain the SLRB configuration information through RRC messages, broadcast messages, or pre-configuration.

[0074] In a twelfth aspect, a device is provided. The device can be a network device, or a device located in a network device (for example, a chip, or a chip system, or a circuit), or a device that can be used in combination with a network device. In one design, the device can include modules corresponding one by one to the methods / operations / steps / actions described in the fifth aspect or the sixth aspect. The module can be a hardware circuit, or software, or a combination of hardware circuit and software. In one design, the device can include a processing module and a communication module. The processing module is used to call the communication module to perform the functions of receiving and / or sending. Exemplarily:

[0075] When the method of the fifth aspect is executed, the communication module is used to receive first information from a terminal device, where the first information includes: a first destination address, a first carrier index, and a first quality of service (QoS) parameter, and there is a corresponding relationship among the first destination address, the first carrier index, and the first QoS parameter; the processing module is used to determine configuration information of a sidelink radio bearer (SLRB) according to the first information, and the communication module is further used to send the SLRB configuration information to the terminal device. In this way, the network device receives the first information from the terminal device, and the first information includes the above corresponding relationship. The network device can determine the SLRB configuration according to this corresponding relationship, and can map the QoS flow configuration to the SLRB corresponding to the carrier supported by the QoS flow, avoiding the packets of the QoS flow using a carrier frequency that it does not support for SL transmission. Therefore, the accuracy of the SLRB configuration is improved, and the SL communication quality is improved.

[0076] When the method of the sixth aspect is executed, the communication module is used to receive first information from a terminal device, where the first information includes: a first destination address, a first carrier index, and at least one quality of service (QoS) parameter, and there is a corresponding relationship among the first destination address, the first carrier index, and the at least one QoS parameter, and all the QoS flows corresponding to the at least one QoS parameter support the carrier indicated by the first carrier index; the processing module is used to determine configuration information of a sidelink radio bearer (SLRB) according to the first information, and the communication module is further used to send the SLRB configuration information to the terminal device. Through the carrier index of the carrier supported by all the QoS flows corresponding to the QoS parameters under the destination address received by the network device from the terminal, when the network device configures the SLRB for the terminal according to the first information after receiving the reported first information, it will not configure a carrier that is not supported by the QoS flow of this destination address, avoiding the packets of the QoS flow using a carrier frequency that it does not support for SL transmission. Therefore, the accuracy of the SLRB configuration is improved, and the SL communication quality is improved.

[0077] The processing module and the communication module can also perform the operations corresponding to any possible design method of the above fifth aspect or sixth aspect, which will not be elaborated one by one here.

[0078] In the thirteenth aspect, a device is provided. The device can be a terminal device, or a device located in the terminal device (for example, a chip, or a chip system, or a circuit), or a device that can be used in matching with the terminal device. In one design, the device can include modules corresponding one by one to the methods / operations / steps / actions described in the fourth aspect. The module can be a hardware circuit, or software, or a combination of a hardware circuit and software. In one design, the device can include a processing module and a communication module. The processing module is used to call the communication module to execute the receiving and / or sending functions. Exemplarily:

[0079] The communication module is used to obtain the correspondence between geographical area information and carrier information; and to determine the carrier information supported by SL communication in the current geographical area according to the correspondence between geographical area information and carrier information. Through the above process, the terminal device determines the carrier information supported by the current geographical area to perform subsequent SL communication, ensuring compliance with policies and regulations and the quality of SL communication.

[0080] The processing module and the communication module may also perform the operations corresponding to the methods described in the above seventh aspect or any possible design of the seventh aspect, which will not be elaborated here one by one.

[0081] In a fourteenth aspect, an embodiment of the present application provides a device, which includes a communication interface and a processor. The communication interface is used for the device to communicate with other devices, such as the transceiver of data or signals. Exemplarily, the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces, and the other devices may be network devices. The processor is used to call a set of programs, instructions, or data to execute the methods described in the above first aspect, second aspect, third aspect, fourth aspect, seventh aspect, or any possible design of these aspects. The device may further include a memory for storing the programs, instructions, or data called by the processor. The memory is coupled to the processor, and when the processor executes the programs, instructions, or data stored in the memory, the methods described in the above first aspect, second aspect, third aspect, fourth aspect, seventh aspect, or any possible design of these aspects can be implemented.

[0082] In a fifteenth aspect, an embodiment of the present application provides a device, which includes a communication interface and a processor. The communication interface is used for the device to communicate with other devices, such as the transceiver of data or signals. Exemplarily, the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces, and the other devices may be terminal devices. The processor is used to call a set of programs, instructions, or data to execute the methods described in the above fifth aspect, sixth aspect, or any possible design of these two aspects. The device may further include a memory for storing the programs, instructions, or data called by the processor. The memory is coupled to the processor, and when the processor executes the programs, instructions, or data stored in the memory, the methods described in the above fifth aspect, sixth aspect, or any possible design of these two aspects can be implemented.

[0083] In a sixteenth aspect, an embodiment of the present application further provides a computer-readable storage medium, in which computer-readable instructions are stored. When the computer-readable instructions run on a computer, the computer is caused to execute the methods described in the above first aspect, second aspect, third aspect, fourth aspect, seventh aspect, or any possible design of these aspects.

[0084] In a seventeenth aspect, an embodiment of the present application further provides a computer-readable storage medium, including instructions that, when running on a computer, cause the computer to execute the method described in the fifth aspect, the sixth aspect, or any possible design of these two aspects.

[0085] In an eighteenth aspect, a computer program product containing instructions is provided that, when running on a computer, causes the computer to execute the method described in the first aspect, the second aspect, the third aspect, the fourth aspect, the seventh aspect, or any possible design of these aspects.

[0086] In a nineteenth aspect, a computer program product containing instructions is provided that, when running on a computer, causes the computer to execute the method described in the fifth aspect, the sixth aspect, or any possible design of these two aspects.

[0087] In a twentieth aspect, an embodiment of the present application provides a chip system. The chip system includes a processor and may further include a memory for implementing the method described in the first aspect, the second aspect, the third aspect, the fourth aspect, the seventh aspect, or any possible design of these aspects. The chip system may be composed of chips or may include chips and other discrete devices.

[0088] In a twenty-first aspect, an embodiment of the present application provides a chip system. The chip system includes a processor and may further include a memory for implementing the method described in the fifth aspect, the sixth aspect, or any possible design of these two aspects. The chip system may be composed of chips or may include chips and other discrete devices.

[0089] In a twenty-second aspect, an embodiment of the present application provides a chip system. The chip system includes a processor and may further include a memory for implementing the method described in the first aspect, the second aspect, the third aspect, the fourth aspect, the seventh aspect, or any possible design of these aspects. The chip system may be composed of chips or may include chips and other discrete devices.

[0090] In a twenty-third aspect, an embodiment of the present application provides a chip system. The chip system includes a processor and may further include a memory for implementing the method described in the fifth aspect, the sixth aspect, or any possible design of these two aspects. The chip system may be composed of chips or may include chips and other discrete devices.

[0091] In a twenty-fourth aspect, an embodiment of the present application provides a system, where the system includes a terminal device and a network device. The terminal device is used to execute the method described in the first aspect, the second aspect, the third aspect, the fourth aspect, the seventh aspect, or any possible design of these aspects; the network device is used to execute the method described in the fifth aspect, the sixth aspect, or any possible design of these two aspects. Description of the Drawings

[0092] Figure 1 It is a schematic diagram of the V2X communication architecture in an embodiment of the present application;

[0093] Figure 2 It is one of the schematic diagrams of the process of the sidelink communication method in an embodiment of the present application;

[0094] Figure 3 It is another schematic diagram of the process of the sidelink communication method in an embodiment of the present application;

[0095] Figure 4 It is a schematic diagram of the carrier indexes supported by all QoS flows corresponding to QoS parameters in an embodiment of the present application;

[0096] Figure 5 It is a third schematic diagram of the process of the sidelink communication method in an embodiment of the present application;

[0097] Figure 6 It is a schematic diagram of the carrier indexes supported by QoS flows corresponding to QoS parameters in an embodiment of the present application;

[0098] Figure 7 It is a schematic diagram of the terminal device in an embodiment of the present application determining the carrier indexes supported by the SLRB according to the SLRB configuration and the carrier indexes supported by the QoS flow;

[0099] Figure 8 It is a fourth schematic diagram of the process of the sidelink communication method in an embodiment of the present application;

[0100] Figure 9 It is a fifth schematic diagram of the process of the sidelink communication method in an embodiment of the present application;

[0101] Figure 10 It is one of the schematic diagrams of the device structure in an embodiment of the present application;

[0102] Figure 11 It is another schematic diagram of the device structure in an embodiment of the present application. Detailed Embodiments

[0103] Embodiments of the present application provide a sidelink communication method and apparatus, aiming to improve the SL communication quality. Among them, the method and the apparatus are based on the same or similar concepts of the same technology. Since the principles of the method and the apparatus for solving problems are similar, the implementation of the apparatus and the method can be referred to each other, and the repeated parts will not be described again. In the description of the embodiments of the present application, "and / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after. At least one involved in the present application refers to one or more; multiple refers to two or more. In addition, it should be understood that in the description of the present application, terms such as "first", "second", "third", etc. are only used for the purpose of distinguishing descriptions, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying an order. Describing with reference to "one embodiment" or "some embodiments" in this specification means that specific features, structures, or characteristics described in combination with the embodiment are included in one or more embodiments of the present application. Thus, statements such as "in one embodiment", "in some embodiments", "in other some embodiments", "in still other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variants all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0104] The technical solution provided by the present application can be applied to the device-to-device (D2D) scenario. Optionally, it can be applied to the vehicle-to-everything (V2X) scenario. Exemplarily, D2D can be D2D in a long term evolution (LTE) communication system, can also be D2D in a new radio (NR) communication system, or can also be D2D in other communication systems that may appear with the development of technology. Similarly, V2X can be LTE V2X, can also be NR V2X, or can also be V2X in other communication systems that may appear with the development of technology.

[0105] Exemplarily, the V2X scenario may specifically be any one of the following systems: vehicle-to-vehicle (V2V), vehicle-to-pedestrian (V2P), vehicle-to-network (V2N) service, and vehicle-to-infrastructure (V2I), etc.

[0106] Among them, one participant in V2N is the terminal device, and the other participant is the service entity. V2N is the most widely used form of the Internet of Vehicles currently. Its main function is to enable the vehicle to connect to the cloud server through the mobile network, so as to provide functions such as navigation, entertainment, and anti-theft through the cloud server.

[0107] Both participants in V2V are terminal devices. V2V can be used as an information interaction reminder between vehicles. The most typical application is for the anti-collision safety system between vehicles.

[0108] Both participants in V2P are terminal devices. V2P can be used to provide safety warnings to pedestrians or non-motor vehicles on the road.

[0109] One participant in V2I is the terminal device, and the other participant is the infrastructure (or road facility). V2I can be used for communication between the vehicle and the infrastructure. For example, the infrastructure can be roads, traffic lights, roadblocks, etc., and road management information such as traffic light signal timings can be obtained.

[0110] In the embodiment of the present application, both the sender and the receiver in V2X can be D2D devices or V2X devices. For example, both the sender and the receiver in V2X can be terminal devices.

[0111] The terminal device in the embodiments of the present application can also be referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), etc. It is a device that provides voice or data connectivity to users and can also be an Internet of Things device. For example, the terminal device includes handheld devices with wireless connection functions, in-vehicle devices, etc. The terminal device can be: a mobile phone, a tablet computer, a laptop computer, a handheld computer, a mobile internet device (MID), a wearable device (such as a smart watch, a smart bracelet, a pedometer, etc.), an in-vehicle device (such as a car, a bicycle, an electric vehicle, an airplane, a ship, a train, a high-speed train, etc.), a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a smart home device (such as a refrigerator, a TV, an air conditioner, an electricity meter, etc.), a smart robot, a workshop device, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, or a wireless terminal in a smart home, a flying device (such as a smart robot, a hot air balloon, a drone, an airplane), etc. The terminal can also be other devices with terminal functions. For example, the terminal can also be a device that serves as a terminal function in D2D communication or vehicle-to-everything communication.

[0112] It should be understood that the terminal device in the embodiments of the present application can also refer to the chip in the terminal device, a communication device, unit, or module with D2D or V2X communication functions, such as an in-vehicle communication device, an in-vehicle communication module, or an in-vehicle communication chip, etc.

[0113] In an embodiment of the present application, the network device is a node in a radio access network (RAN), which can also be referred to as a base station, and can also be referred to as a RAN node (or device). Currently, some examples of access network devices are: next generation node B (gNB), next generation evolved node B (Ng-eNB), transmission reception point (TRP), evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home Node B, HNB), base band unit (BBU), or wireless fidelity (Wifi) access point (AP). The network device 201 can also be a satellite or a future base station. The satellite can also be referred to as a high altitude platform, a high altitude aircraft, or a satellite base station. The network device can also be other devices with network device functions. For example, the network device 201 can also be a device that serves as a network device in D2D communication or vehicle-to-everything (V2X) communication. The network device 201 can also be a network device in a future possible communication system.

[0114] In some deployments, a network device may include a centralized unit (CU) and a distributed unit (DU). The network device may also include an active antenna unit (AAU). The CU implements some functions of the network device, and the DU implements some functions of the network device. For example, the CU is responsible for processing non-real-time protocols and services, implementing radio resource control (RRC), and the functions of the packet data convergence protocol (PDCP) layer. The DU is responsible for processing physical layer protocols and real-time services, implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. The AAU implements some physical layer processing functions, radio frequency processing, and related functions of the active antenna. Since the information of the RRC layer will ultimately become the information of the PHY layer, or is transformed from the information of the PHY layer, therefore, in this architecture, high-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or sent by the DU + AAU. It can be understood that the network device may be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU may be classified as a network device in the radio access network (RAN), or the CU may be classified as a network device in the core network (CN), and this application does not make a limitation on this.

[0115] The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0116] Figure 1 A schematic diagram of a V2X communication architecture 100 is shown. As Figure 1 shown, the V2X communication architecture 100 includes: a V2X application server, V2X devices (such as Figure 1The V2X UEs 1 and 2 shown in Figure 1 and network devices. Two communication interfaces are included in this V2X communication architecture, namely the PC5 interface and the Uu interface. Among them, the PC5 interface is a direct communication interface between V2X UEs, and the direct communication link between V2X UEs is also defined as a sidelink or side chain (SL). Uu interface communication means that the sending V2X UE (for example, V2X UE 1) sends V2X data to the network device through the Uu interface, and after being sent to the V2X application server for processing by the network device, it is then sent by the V2X application server to the network device and sent to the receiving V2X UE (for example, V2X UE 2) by the network device. In the Uu interface communication mode, the network device that forwards the uplink data of the sending V2X UE to the application server and the network device that forwards the downlink data sent by the application server to the receiving V2X UE can be the same network device or different network devices, which can be specifically determined by the application server. It should be understood that the sending from the sending V2X UE to the network device is called uplink (UL) transmission, which is represented by Uu UL in Figure 1 ; the sending from the network device to the receiving V2X UE is called downlink (DL) transmission, which is represented by Uu DL in

[0117] To better understand the technical solution of this application, some terms or concepts are introduced below.

[0118] 1) PC5 quality of service flow (PC5 QoS flow): It can be abbreviated as QoS flow for short. A PC5 QoS flow is associated with a PC5 QoS flow indicator (PFI). The PFI is an identifier assigned by the upper layer of the terminal device and is used to uniquely identify a QoS flow under a layer 2 destination address (destination L2 ID). A PFI is also associated with a set of QoS profiles. The QoS profile may include one or more of the following parameters: PC5 interface 5G quality of service identifier (PQI), guaranteed flow bit rate (GFBR), maximum flow bit rate (MFBR), minimum required communication range (range), allocation and retention priority (ARP), PC5 LINK-aggregate maximum bit rate (PC5 LINK-AMBR), default values, resource type, priority level, packet delay budget (PDB), packet error rate (PER), averaging window (for QoS flows of GBR and Delay-critical GBR resource types), or maximum data burst volume (for QoS flows of Delay-critical GBR resource type), etc. The resource type can be, for example, guaranteed bit rate (GBR), Delay critical GBR, or Non-GBR.

[0119] 2) Sidelink Radio Bearer (SLRB): A bearer used in layer 2 for transmitting and receiving sidelink data. The SLRB includes entities such as a Packet Data Convergence Protocol (PDCP) entity, a Radio Link Control (RLC) entity, or a Logical Channel (LCH). An SLRB is uniquely associated with a set of address information, which includes a source address identifier (such as source L2 ID) and a destination address identifier (such as destination L2 ID). The address information may also include a communication type (cast type). The cast type can be unicast, multicast, or broadcast.

[0120] 3) In the embodiments of this application, "support", "associate", or "permit" may indicate the same or similar meanings. When it comes to "A supports B", it can mean "A associates with B" or "A permits B". For example, the carrier index is associated with QoS parameters, which can be understood as: the QoS flow corresponding to the QoS parameters supports transmission on the carrier indicated by the carrier index, or the QoS flow corresponding to the QoS parameters permits transmission on the carrier indicated by the carrier index. When it comes to "support carrier information (or carrier index)", it can be understood as "support the carrier indicated by the carrier information (or carrier index)".

[0121] 4) The association relationship can also be referred to as a corresponding relationship. If A has an association relationship with B, it can be understood that A has a corresponding relationship with B.

[0122] 5) In the embodiments of this application, when it comes to: two pieces of information being different, two parameters being different, or any two elements being different, it can refer to the case of not being completely the same (i.e., partially the same and partially different), or it can refer to the case of being completely different.

[0123] As Figure 2 shown, the specific process of the sidelink communication method provided by the embodiments of this application is described as follows.

[0124] S201. The terminal device sends the first information to the network device, and the network device receives the first information from the terminal device.

[0125] The first information includes a destination address, and also includes the association relationship between carrier information and QoS parameters. Among them, one destination address can be associated with one or more carrier information, and one destination address can also be associated with one or more QoS parameters. One carrier information can correspond to one or more QoS parameters. One QoS parameter can correspond to one or more carrier information. The first information includes: among the carrier information associated with a destination address and the QoS parameters associated with the destination address, which QoS parameters and which carrier information have a corresponding relationship.

[0126] The destination address in the embodiments of the present application can be represented by a destination address identifier or index, can also be represented by a communication type, and can also be represented by a combination of a destination address identifier / index and a communication type. Optionally, for unicast, the destination address identifier is the identifier of the peer UE; for multicast, the destination address identifier is the group identifier (group destination L2ID); for broadcast, the destination address identifier is the destination address identifier corresponding to the service type. Exemplarily, the service type can be a provider service identifier (PSID) or an intelligent transport systems application identifier (ITS-AID).

[0127] The carrier information can include a carrier index, and can also include the synchronization type supported by the carrier.

[0128] The QoS parameters can include a QoS flow identifier, such as PFI. The QoS parameters can also include QoS files, for example, any one or more parameters of the QoS files introduced in the above point 1).

[0129] For example, the first information can include a first destination address, a first carrier index, and a first QoS parameter, where the first destination address, the first carrier index, and the first QoS parameter have a corresponding relationship. Expanding, that is, the first carrier index corresponds to the first destination address, the first QoS parameter corresponds to the first destination address, and the first carrier index corresponds to the first QoS parameter.

[0130] As described above, one destination address may be associated with multiple carrier information, and may also be associated with multiple QoS parameters. In this case, it is possible that one QoS parameter corresponds to multiple carrier indexes, and it is also possible that one carrier index corresponds to multiple QoS parameters.

[0131] Assume that the first piece of information further includes a second carrier index, and the first QoS parameter may also have a corresponding relationship with the second carrier index. Then, the first QoS parameter corresponds to the first carrier index and the second carrier index. Of course, in actual applications, the first QoS parameter can correspond to more carrier indices.

[0132] Similarly, assume that the first piece of information further includes a second QoS parameter, and the first carrier index may also have a corresponding relationship with the second QoS parameter. Then the first carrier index corresponds to the first QoS parameter and the second parameter. Of course, in actual applications, the first carrier index may correspond to more QoS parameters.

[0133] In the embodiments of the present application, the QoS parameter has a corresponding relationship or an associated relationship with the carrier index, which can be understood as: the QoS flow corresponding to the QoS parameter under the corresponding destination address supports transmission on the carrier indicated by the carrier index, or it can be understood that it is allowed that the QoS flow corresponding to the QoS parameter under the corresponding destination address is transmitted on the carrier indicated by the carrier index. The description here applies to the whole text.

[0134] S202. The network device determines the configuration information of the SLRB according to the first piece of information.

[0135] S203. The network device sends the configuration information of the SLRB to the terminal device, and the terminal device receives the configuration information of the SLRB from the network device.

[0136] The configuration information of the SLRB includes one or more of a destination address, a QoS parameter, or carrier information.

[0137] Optionally, after S203, S204 and S205 are further included.

[0138] S204. The terminal device establishes an SLRB according to the configuration information of the SLRB.

[0139] S205. The terminal device performs SL communication on the established SLRB.

[0140] After receiving the first piece of information, the network device can determine that the first destination address, the first QoS parameter, and the first carrier index are corresponding according to the first piece of information. Then, the network device can, according to the first piece of information, determine that the first QoS flow corresponding to the first QoS parameter under the first destination address supports SL transmission on the first carrier indicated by the first carrier index, so as to configure the first SLRB corresponding to the first carrier for the first QoS flow corresponding to the first QoS parameter under the first destination address. Among them, the configuration information of the SLRB may include the first QoS parameter, may also include the identifier or index (ID / index) of the first SLRB, or may also include one or more of the protocol layer configuration parameters of the first SLRB. For example, the PDCP, RLC, or LCH configuration parameters of the first SLRB. Among them, the first QoS parameter is corresponding to the identifier or index of the first SLRB.

[0141] Of course, the first piece of information may include the first destination address, multiple QoS parameters, multiple carrier indexes, and the corresponding relationship between the QoS parameters and the carrier indexes. The network device can, according to the first piece of information, determine the carriers supported by the QoS flows corresponding to each QoS parameter under the first destination address, so as to configure the SLRB corresponding to the supported carriers for each QoS flow under the first destination address.

[0142] By reporting the first piece of information from the terminal device to the network device, the corresponding relationship between the carrier index and the QoS parameter is included in the first piece of information. In this way, the configuration of the SLRB determined by the network device is determined according to the carrier supported by the QoS flow, avoiding the terminal mapping the QoS flow to the SLRB corresponding to the carrier that is not supported according to the configuration information of the SLRB.

[0143] Based on the above description, some optional implementation manners of the embodiments of the present application are introduced below.

[0144] Optionally, the QoS flow identifier (ID) is locally unique. Exemplarily, the QoS flow ID is PFI (PC5 QoS flow identifier), and the PFI value is unique under one destination address. Optionally, the configuration information of the SLRB sent by the network device includes the destination address index / identifier, and may also include the PFI list. Among them, each destination address identifier / index is associated with a PFI list.

[0145] Optionally, the QoS flow identifier can also be globally unique. Exemplarily, the QoS flow identifier can uniquely represent a set of information within the terminal device, including the destination address, the carrier information list, and the QoS file. In the case where the QoS flow identifier is globally unique, there will be no identical QoS flow IDs under the carrier information lists with different destination addresses. The configuration information of the SLRB sent by the network device can include the carrier information list index or identifier, and can also include the QoS flow ID list. Optionally, each carrier information list index or identifier is associated with a QoS flow ID list. In the carrier information list indicated by a carrier information list index or identifier, one or more carrier information are included. The carrier information list can also be replaced by one or more carrier indexes.

[0146] In the embodiments of the present application, the carrier information can be represented by the carrier index, can also be represented by the synchronization type supported by the carrier, or can also be represented by the combination of the carrier index and the synchronization type supported by the carrier. Optionally, one or more carrier indexes can be indicated by the index or identifier of the carrier information list. The terminal device can obtain the carrier index from the system information block (SIB) message received from the network device. The SIB message can carry the indexes of the carriers supported by the cell where the terminal device is located. The identifier of the carrier information list can be the identifier assigned to the corresponding carrier information list when the terminal device reports the first information. The index of the carrier information list can be the index obtained by sequentially numbering multiple carrier information lists when the terminal device reports the first information. The identifier of the carrier list can be a unique identifier under a destination address, and the index of the carrier list can also be a globally unique index. Globally unique means unique among all destination addresses. Optionally, the identifier of the carrier information list can be an identifier of a service type. Optionally, the identifier of the carrier list can be a link identifier. It can be understood that some of the carrier indexes can be the same in different carrier information lists.

[0147] Optionally, the correspondence between the carrier index and the QoS parameter can be replaced by the correspondence between the service type identifier and the QoS parameter. The first message sent by the terminal to the network device includes: the first destination address, the first service type identifier, and the first QoS parameter. The first service type identifier corresponds to the first destination address, the first QoS parameter corresponds to the first destination address, and the first QoS parameter corresponds to the first service type identifier.

[0148] The first message can also include the second service type identifier, and there is also a corresponding relationship between the first QoS parameter and the second service type identifier.

[0149] The first message may further include second QoS parameters, and there is also a corresponding relationship between the first service type identifier and the second QoS parameters.

[0150] In summary, one service type identifier may correspond to one or more QoS parameters, and one QoS parameter may also correspond to one or more service type identifiers.

[0151] Optionally, the network device may obtain the association relationship between each service type identifier and each carrier information from the core network or the V2X application server (V2X Application Server).

[0152] Optionally, the terminal device reports the association relationship between each service type identifier and each carrier information to the network device.

[0153] The terminal device may perform SL communication with one or more destination addresses. Then, the terminal device may request the configuration information of the SLRB corresponding to multiple destination addresses from the network device. In practical applications, the terminal device may report multiple destination addresses in the first information. For example, the first information includes a second destination address, a carrier index associated with the second destination address, a QoS parameter associated with the second destination address, and the corresponding relationship between the carrier index and the QoS parameter. The reporting method is similar to that of the first destination address.

[0154] The terminal device may determine the corresponding relationship between the QoS parameter and the carrier index in the following manner.

[0155] The access layer (access layer, AS) of the terminal device obtains information from the upper layer of the terminal device, which is denoted as the second information. The second information may include information about the carriers supported by the service type. For example, the second information includes the identifier of the service type and the carrier information. It can be understood that the carrier information carried in the second information obtained by the access layer of the terminal device from the upper layer may be different from the carrier information reported by the terminal device to the network device. For example, the carrier indexes are different. The carrier index reported by the terminal device to the network device is used to distinguish different carriers within a cell. The function of the carrier information in the second information is different from this. In summary, the terminal device may determine the carriers supported by each service type from the information obtained from the upper layer. The terminal device determines the carriers supported by the service according to the second information. It should be understood that the access layer of the terminal device may also obtain third information from the upper layer of the upper device. The third information includes information about the QoS flow of the corresponding service under the destination address. For example, the third information includes the destination address, the service identifier, and the QoS parameter. The terminal device may determine that there is a QoS flow corresponding to the QoS parameter under the service corresponding to the service type identifier under the destination address according to the third information. Further, the terminal device may determine the QoS flow of the service corresponding to the service type identifier under the destination address, and support SL transmission on which carriers.

[0156] The QoS parameter may be a QoS identifier. The QoS identifier in the third information may be different from the QoS identifier in the first information, but it indicates the same QoS flow under the same destination address.

[0157] The access stratum of the terminal device obtains the second information or the third information from the upper layer. Here, the upper layer may refer to the layer above the access stratum of the terminal device, such as the V2X layer, the application layer, or the layer between the V2X layer and the application layer. The access stratum of the terminal device may include, for example, one or more of a radio resource control (RRC) layer, a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. Optionally, the access stratum may further include a physical (PHY) layer.

[0158] In the embodiments of this application, when the terminal device is in the RRC connected state, the first information sent to the network device may be carried in a sidelink UE information (SUI). The SUI message is used to request SLRB configuration. The SUI message includes the content included in the above first information. After receiving the SUI message, the network device determines the SLRB configuration according to the SUI message, configures the corresponding SLRB for the QoS flow, and only the QoS flows that support the same carrier information will be mapped to the same SLRB. The network device sends the SLRB configuration to the terminal device.

[0159] It should be understood that the reporting method of the first information may be in the form of full information reporting or delta information reporting. Full information reporting means that if the previously reported first information is still in an effective state at the current reporting moment, the first information still needs to be reported again at the current reporting moment. The delta information reporting method means that each time the first information content is reported, only the newly changed first information needs to be included.

[0160] The possible representation forms of the content in the first information are illustrated by way of examples below. In the following examples, the carrier information is represented by a carrier list, and each carrier list may include one or more carrier information. The carrier information may be a carrier index or the synchronization type supported by the carrier. Any QoS parameter may include a QoS flow identifier or a QoS file.

[0161] Representation form 1:

[0162] As shown in Table 1, the first information includes a first destination address and the corresponding relationship between the carrier information and QoS parameters under the first destination address. The first destination address is associated with carrier list 1, carrier list 2, and carrier list 3. The first destination address is associated with QoS file 1, QoS file 2, QoS file 3, QoS file 4, and QoS file 5. Among them, QoS file 1, QoS file 2, and QoS file 3 correspond to carrier list 1; QoS file 1, QoS file 3, and QoS file 5 correspond to carrier list 2; QoS file 2, QoS file 3, and QoS file 4 correspond to carrier list 3. The carrier information in the carrier list can be represented by a carrier index. Assume that carrier list 1 includes carrier index 1, carrier index 2, and carrier index 3; carrier list 2 includes carrier index 1, carrier index 3, and carrier index 4; carrier list 3 includes carrier index 5 and carrier index 6. It should be understood that the carrier list may also include the identifier corresponding to the carrier list, and the QoS parameter may also include the QoS identifier corresponding to the QoS file.

[0163] Assume that the first destination address is represented by a destination address identifier and a communication type. The identifier of the first destination address is destination L2 ID 1, and the communication type is unicast.

[0164] Table 1

[0165]

[0166] The first information may also include the corresponding relationship between the carrier information and QoS parameters for multiple destination addresses. Based on Table 1, as shown in Table 2, assume that the first information also includes the corresponding relationship between the carrier information and QoS parameters for the second destination address and the third destination address. For example, the identifier of the second destination address is (destination L2 ID 1), and the communication type is broadcast; the identifier of the second destination address is (destination L2 ID 2), and the communication type is unicast.

[0167] Assume that the second destination address is associated with carrier indices 1, 2, and 3, and is associated with QoS files 1 to 5. Among them, carrier index 1 and carrier index 2 have a corresponding relationship with QoS files 1 to 3, and carrier index 1 and carrier index 3 have a corresponding relationship with QoS files 2 to 5.

[0168] Assume that the third destination address is associated with carrier indices 1 to 4, and is associated with QoS files 1 to 5. Among them, carrier indices 1 to 3 have a corresponding relationship with QoS files 1, 3, and 5, and carrier index 1 and carrier index 4 have a corresponding relationship with QoS files 2, 4, and 5.

[0169] Table 2

[0170]

[0171] The examples in Table 1 and Table 2 are just for illustration. In actual applications, the corresponding relationship between the carrier index and the QoS parameters can be determined according to the actual situation.

[0172] The second form of representation:

[0173] The corresponding relationship between the destination address, the downloaded wave information, and the Qos parameters can also be represented in the following way. For example, the carrier information is represented by a carrier list. Optionally, different carrier lists are distinguished by the identifier or index of the carrier list. A carrier list includes one or more carrier indices.

[0174] As shown in Table 3a and Table 3b, referring to the description content of Table 1, the first information includes the first destination address, and the corresponding relationship between the carrier information and the Qos parameters under the first destination address. The first destination address is associated with carrier list 1, carrier list 2, and carrier list 3. The first destination address is associated with QoS file 1, QoS file 2, QoS file 3, QoS file 4, and QoS file 5. Among them, QoS file 1 corresponds to carrier list 1 and carrier list 2, QoS file 2 corresponds to carrier list 1 and carrier list 3, QoS file 3 corresponds to carrier list 1, carrier list 2, and carrier list 3, QoS file 4 corresponds to carrier list 3, and QoS file 5 corresponds to carrier list 2. It should be understood that at this time, the corresponding relationship between the QoS file and the carrier list is expressed as: the corresponding relationship between the index / identifier of the QoS file and the carrier list.

[0175] Table 3a

[0176]

[0177] Table 3b

[0178]

[0179] Similarly, the first information may also include the correspondence between multiple destination address download wave information and QoS parameters. Based on Tables 3a and 3b, as shown in Tables 4a and 4b, referring to the description in Table 2, it is assumed that the first information further includes the correspondence between the second destination address and the third destination address download wave information and QoS parameters. It should be understood that at this time, the correspondence between the QoS file and the carrier list is expressed as: the correspondence between the QoS file and the index / identifier of the carrier list. And the indexes / identifiers associated with the carrier lists under different destination addresses can be the same value. Exemplarily, Carrier List 1 and Carrier List 4 in Table 4 are both represented by Carrier List Index 1. At this time, the carrier list index uniquely represents a carrier list locally under one destination address. Optionally, the carrier list corresponding to the QoS file may further include the identifier / index of the corresponding destination address.

[0180] Table 4a

[0181]

[0182] Table 4b

[0183]

[0184]

[0185] Tables 3a, 3b, 4a, and 4b are just examples. In practical applications, the correspondence between the carrier index and the QoS parameters can be determined according to the actual situation.

[0186] In this way, through the first information, the terminal device can indicate to the network device the carrier information corresponding to each QoS parameter under the destination address. The network device determines the SLRB configuration according to this correspondence, and can map the QoS flow configuration to the SLRB corresponding to the carrier supported by the Qos flow, avoiding the packets of the QoS flow using the carrier frequency that it does not support for SL transmission. Thereby improving the accuracy of the SLRB configuration and improving the SL communication quality.

[0187] Based on the same technical concept, on the basis of the above embodiments, as Figure 3 shown, the embodiment of the present application provides another sidelink communication method, and the specific process is as follows.

[0188] S301. The terminal device sends the first information to the network device, and the network device receives the first information from the terminal device.

[0189] Among them, the first information includes: a first destination address, a first carrier index, and at least one QoS parameter. There is a corresponding relationship among the first destination address, the first carrier index, and the at least one QoS parameter. All QoS flows corresponding to the at least one QoS parameter under the first destination address support SL transmission on the carrier indicated by the first carrier index.

[0190] Optionally, the first information may further include a second carrier index. All QoS flows corresponding to the at least one QoS parameter under the first destination address support SL transmission on the carrier indicated by the second carrier index.

[0191] In summary, the number of carrier indices included in the first information is one or more. The carriers indicated by these one or more carrier indices are supported by all QoS flows corresponding to at least one QoS parameter associated with the first destination address.

[0192] In practical applications, there may be multiple carrier indices associated with the first destination address. QoS flows corresponding to different QoS parameters support different carriers. The terminal device determines the carriers supported by all QoS flows corresponding to different QoS parameters under the first destination address, and obtains the carrier indices of the carriers supported by all QoS flows. The carrier indices of the carriers supported by all QoS flows are carried in the first information.

[0193] S302. The network device determines the configuration information of the SLRB according to the first information.

[0194] S303. The network device sends the configuration information of the SLRB to the terminal device, and the terminal device receives the configuration information of the SLRB from the network device.

[0195] The configuration information of the SLRB includes one or more of a destination address, QoS parameters, or carrier information.

[0196] Optionally, after S303, S304 and S305 are further included.

[0197] S304. The terminal device establishes an SLRB according to the configuration information of the SLRB.

[0198] S305. The terminal device performs SL communication on the established SLRB.

[0199] Optionally, the terminal needs to determine the information of the carrier supported by the QoS flow corresponding to the QoS parameter associated with the first destination address. The specific method can refer to the description in the part of "The terminal device can determine the corresponding relationship between the QoS parameter and the carrier index in the following way" in the above text, and the repeated parts will not be elaborated here.

[0200] The following is further illustrated by an example Figure 3 for the embodiment.

[0201] For the convenience of illustration, Figure 4 is used to represent the carrier index supported by the QoS flow corresponding to each QoS parameter. Assume that the first destination address is associated with QoS parameters 1 to 3, and the first destination address is associated with carrier indices 1 to 5. Among them, QoS parameters 1 to 3 are all associated with QoS file 1. The QoS flow corresponding to QoS parameter 1 supports the carriers indicated by carrier indices 1 to 5; the QoS flow corresponding to QoS parameter 2 supports the carriers indicated by carrier indices 1, 2, and 4; the QoS flow corresponding to QoS parameter 3 supports the carriers indicated by carrier indices 1 and 2. The terminal device determines that the carriers supported by all QoS flows corresponding to QoS file 1 are the carriers indicated by carrier indices 1 and 2. The carriers indicated by the carrier indices supported by all QoS flows corresponding to each QoS parameter associated with QoS file 1 are represented by a circle, and one circle represents a set. Then the intersection of the carrier indices supported by the QoS flows corresponding to multiple QoS parameters associated with QoS file 1 is carrier index 1 and carrier index 2.

[0202] The first information reported by the terminal device may include: the first destination address, carrier index 1, carrier index 2, and QoS parameters 1 to 3. Optionally, when the identifiers of the QoS flows corresponding to QoS parameters 1 to 3 are the same, the content of QoS parameters 1 to 3 only includes QoS file 1 and / or the same QoS flow identifier. At this time, the first destination address is associated with carrier indices 1 and 2, and the first destination address is associated with QoS parameters 1 to 3. And the QoS flows corresponding to QoS parameters 1 to 3 all support the carriers indicated by carrier indices 1 and 2.

[0203] It should be understood that the first destination address may also be associated with other QoS parameters, and the QoS files associated with the other QoS parameters may be different from the QoS files associated with QoS parameters 1 to 3. When the carriers supported by the QoS flows corresponding to the other QoS parameters are the same as those supported by QoS parameters 1 to 3, the carrier indices 1 to 5 associated with the first destination address also correspond to the other QoS parameters.

[0204] In the embodiments of the present application, the carrier indices included in the first information may be one or more, which are the indices of the carriers supported by multiple QoS flows associated with the first destination address. If multiple carrier indices are included in the first information, the multiple carrier indices may be embodied in the form of a list, or may be embodied in the form of a set or combination. The presentation form of the content included in the first information may refer to Figure 2 Presentation form 1 and presentation form 2 in the illustrated embodiments.

[0205] Optionally, if the index of the carriers supported by all the QoS flows corresponding to the QoS parameters of multiple QoS files associated with the destination address is an empty set, the access stratum of the terminal device sends indication information to the upper stratum (such as the V2X stratum). This indication information is used to indicate that the QoS flows or services corresponding to the same QoS file associated with this destination address are unreasonable. Optionally, after receiving the indication information, the upper stratum of the terminal device triggers a PC5-S link modification process with the peer terminal device, or modifies the information of the QoS parameters / services associated with this destination address.

[0206] Optionally, if the index of the carriers supported by all the QoS flows corresponding to the QoS parameters of multiple QoS files associated with the first destination address is an empty set, the first destination address in the first information reported by the terminal device to the network device does not include the information of the multiple QoS flows, indicating that SL transmission with any carrier index for the QoS flows corresponding to the multiple QoS parameters is not supported under the first destination address. Alternatively, the multiple QoS parameters are associated with an indication information, which is used to indicate that SL transmission with any carrier index for the QoS flows corresponding to the multiple QoS parameters is not supported under the first destination address.

[0207] Optionally, if the number of the indexes of the carriers supported by all the QoS flows corresponding to the QoS parameters of multiple QoS files associated with the first destination address is one, the first destination address in the first information reported by the terminal device is associated with an indication information, which is used to indicate that the QoS flows corresponding to the multiple QoS parameters under the first destination address do not support multi-carrier SL transmission.

[0208] By reporting to the network device by the terminal device the carrier indexes of the carriers supported by the QoS flows corresponding to the QoS parameters under the destination address, when the network device configures the SLRB according to the first information after receiving the reported first information, it will not configure the carriers not supported by the QoS flows of this destination address, avoiding the use of carrier frequencies not supported by the QoS flow packets for SL transmission. Thus, the configuration accuracy of the SLRB is improved, and the SL communication quality is improved.

[0209] Figure 2 and Figure 3 In the embodiment shown, when the terminal device reports the correspondence between the carrier information and the QoS parameters under multiple destination addresses to the network device, the correspondence between the carrier information and the QoS parameters under different destination addresses can be carried in one piece of information, for example, reported through the first information; or reported to the network device through different pieces of information. For example, the correspondence between the carrier information and the QoS parameters under the first destination address is reported through the first information, and the correspondence between the carrier information and the QoS parameters under the second destination address is reported through other information.

[0210] Figure 3 For some optional implementation manners and descriptions of concepts not described in the embodiments, reference may be made to Figure 2 the descriptions in the embodiments. References may be made between the embodiments.

[0211] Combined with the above embodiments, as Figure 5 shown, the embodiments of the present application further provide a sidelink communication method, and the specific process is as follows.

[0212] S501. The terminal device obtains the configuration information of the SLRB.

[0213] Among them, the configuration information of the SLRB includes one or more QoS parameters. The configuration information of the SLRB can be briefly described as the SLRB configuration.

[0214] S502. The terminal device establishes an SLRB for the destination address according to the configuration information of the SLRB.

[0215] Among them, the SLRB is associated with one or more QoS parameters corresponding to the destination address.

[0216] S503. The terminal device determines the carrier information corresponding to the carrier supported by the SLRB.

[0217] The carrier information is the carrier information supported by all QoS flows indicated by one or more QoS parameters corresponding to the destination address.

[0218] The conceptual explanation of the carrier information can be found in Figure 2 or Figure 3 the descriptions in the embodiments.

[0219] Figure 5 The shown embodiments can be applied to the RRC connected state and the non-RRC connected state of the terminal.

[0220] Generally speaking, when the terminal device is in the RRC connected state, the terminal device sends a SUI message to the network device to request the SLRB configuration. After receiving the SUI message, the network device sends the SLRB configuration to the terminal device according to the SUI message. The terminal device may carry the correspondence between the QoS parameters and the carrier index under the destination address in the SUI message.

[0221] When the terminal device is in the RRC inactive state or the RRC idle state, the terminal device can receive the SLRB configuration from the system information block (SIB) broadcast by the network device; or, when the terminal device is out-of-coverage (OOC), the terminal device can obtain a pre-configured SLRB configuration. After the terminal device obtains the SLRB configuration, it can establish a corresponding SLRB for the corresponding PC5 QoS flow for sidelink communication.

[0222] The following further describes Figure 5 the optional implementation manners of the embodiments.

[0223] When the terminal device is in the non-RRC connected state or the idle state, the terminal device can obtain the configuration information of the SLRB through the SIB or pre-configuration. In this case, the network device cannot know the QoS parameters associated with each destination address of the terminal device, as well as the associated carrier information. The network device also does not know the carriers supported by the QoS flows corresponding to the QoS parameters. Therefore, the following problems may occur when the network device configures the SLRB: mapping QoS flows corresponding to QoS parameters associated with different carrier information to the same SLRB / LCH. Exemplarily, the network device configures the mapping relationship between the QoS file and the SLRB. The same QoS file may be associated with different QoS flows under the same destination address. For example, different services may have QoS flows with the same QoS file requirements, and these QoS flows support different carrier information. The upper layer of the terminal device uses different PFIs to represent different QoS flows, and the different QoS flows represented by different PFIs support different carrier information, but are configured by the network device to be mapped to the same SLRB / LCH.

[0224] Based on the above problems, the terminal device needs to first determine the carrier information supported by the SLRB / LCH. The terminal device can determine whether the carrier information supported by the SLRB / LCH meets the logical channel prioritization (LCP) limit of the carrier corresponding to the resource (grant) scheduled by the network device, or the terminal device can determine whether the carrier information supported by the SLRB / LCH meets the LCP limit of the resource obtained by the terminal device through resource selection. For example, the terminal device determines whether the data of the LCH can be placed on the grant or resource corresponding to this carrier for SL transmission.

[0225] Based on the judgment result, the terminal device will use the grant or resource corresponding to the carrier to transmit the data packets in LCH / SLRB only when the judgment result is yes. This avoids the SL transmission of the data packets in LCH / SLRB based on the carriers that it does not support.

[0226] It should be understood that the terminal device can determine the carrier information supported by the QoS parameters according to the carrier information supported by the service type corresponding to the QoSflow corresponding to the QoS parameters. For a detailed introduction on how the terminal device obtains the carrier information associated with the QoS parameters in this part, reference can also be made to Figure 2 the description of the relevant part of the embodiment.

[0227] Optionally, the carrier information supported by LCH / SLRB is the carrier information supported by the cell for SL communication. For example, the carrier information supported by LCH / SLRB is included in the carrier information list carried in the cell SIB message.

[0228] In a possible implementation, the terminal device uses the same (intersection part) carrier information associated with all the QoS flows / services mapped to LCH / SLRB as the carrier information supported by the current LCH / SLRB. Optionally, the terminal device further determines the carrier information allowed by LCH / SLRB according to the channel busy ratio (CBR). Exemplarily, the carrier information can be determined as the carrier information supported by LCH / SLRB only when the CBR corresponding to the carrier information is less than or equal to the threshold. The CBR threshold can be network-configured or protocol-specified.

[0229] Considering the packet data convergence protocol (PDCP) duplication situation, one SLRB is associated with multiple LCHs. Among them, if the PDCP duplication mechanism is adopted, one PDCP entity will correspond to two or more RLC entities and LCHs. The duplication mechanism means that the PDCP entity duplicates the PDCP PDU and submits it to the associated two or more RLC entities for processing and transmission. Not all the LCHs corresponding to the PDCP entity can perform SL transmission based on duplication.

[0230] According to Figure 5 the method of the embodiment, when the terminal device determines the carrier information supported by the SLRB, if the number of the supported carrier information is less than the number of LCHs associated with the SLRB itself, the terminal device selects some LCHs to perform SL transmission based on PDCP duplication to ensure normal SL communication.

[0231] Optionally, the terminal device selects the LCHs that can perform SL transmission according to certain rules. These rules can be network-configured or protocol-specified. Exemplarily, the terminal device selects the LCHs according to the rule of ascending logical channel identifier (LCID), or the terminal device selects the LCHs according to the descending LCH priority corresponding to the LCHs.

[0232] Optionally, the terminal device sends indication information to the network device, and the indication information is used to indicate that the current SLRB cannot support PDCP duplication. Exemplarily, the indication information is sent through RRC dedicated signaling or MAC CE. The indication information may include one or more of a destination address, SLRB configuration information (for example: SLRB index or identifier), supported carrier information, or associated LCH information.

[0233] Optionally, the access stratum of the terminal device may also send the indication information to the upper layer.

[0234] The following Figure 6 and Figure 7 illustrative examples Figure 5 are used to further elaborate on

[0235] the SLRB configuration obtained by the terminal device from the network device is as Figure 6 shown. The carrier information is represented by a carrier list, and a carrier list includes multiple carrier indices. The QoS parameters are represented by PFI and QoS files.

[0236] As Figure 7 shown, the terminal device establishes an SLRB / LCH for this destination address, and the flows corresponding to QoS parameters 1, 2, and 5 are mapped to SLRB / LCH 1, while the flows corresponding to QoS parameters 3, 4, and 6 are mapped to SLRB / LCH 2. The terminal device determines, according to the Figure 6 shown SLRB configuration, that the carrier lists associated with the QoS flows corresponding to QoS parameters 1, 2, and 5 include carrier list 1 and carrier list 2. The carrier indices included in both carrier list 1 and carrier list 2 (i.e., the intersection) are carrier indices 1, 2, and 4. Thus, the terminal device determines that the allowed carrier information for SLRB / LCH 1 is carrier indices 1, 2, 4. Similarly, the terminal device determines, according to the Figure 6 shown SLRB configuration, the intersection of the carrier indices associated with the QoS flows corresponding to QoS parameters 3, 4, and 6, and thus determines that the allowed carrier information for SLRB / LCH2 is carrier indices 1, 2.

[0237] In summary, Figure 5In the embodiments shown, the network device configures the mapping relationship between the QoS file and the SLRB in the configuration information of the SLRB. After receiving the configuration information of the SLRB sent by the network device, if the terminal device determines, based on the configuration information of the SLRB, that the QoS flows corresponding to the QoS file at a certain destination address support different carriers and are mapped to the same SLRB / LCH, the terminal device uses the carriers supported by these QoS flows as the carriers mapped to the SLRB / LCH. Therefore, when sending the data packet corresponding to the QoS flow, the SL transmission will not use the carriers not supported by the QoS flow.

[0238] Based on the above embodiments, as Figure 8 shown, the embodiments of the present application further provide a sidelink communication method, and the specific process is described as follows.

[0239] S801. The terminal device obtains the configuration information of the SLRB.

[0240] Among them, the SLRB configuration information includes M QoS parameters.

[0241] The terminal device can obtain the configuration information of the SLRB through RRC messages, SIB messages or pre-configuration. The state of the terminal device can be the RRC connected state or the RRC non-connected state. The specific details of this step can refer to the description of obtaining the SLRB configuration information in the embodiments. Figure 5 Embodiments describe obtaining the SLRB configuration information.

[0242] S802. The terminal device determines that among the M QoS parameters corresponding to the first destination address, the carriers supported by the QoS flows corresponding to N QoS parameters are not completely the same. "Not completely the same" can be understood as partially different or all different.

[0243] Among them, M and N are integers greater than 1, and M and N can be the same or different.

[0244] For example, taking Figure 6 shown as an example, the SLRB configuration information includes QoS parameters 1, 2, and 5. Then, the carriers supported by QoS parameter 1 and QoS parameter 5 are not completely the same. The QoS flow corresponding to QoS parameter 1 supports the carriers indicated by carrier indices 3 and 5, while the QoS flow corresponding to QoS parameter 5 does not support the carriers indicated by carrier 3 and 5.

[0245] Specifically, the terminal device can determine the association relationship between the carrier information and the QoS flows corresponding to the QoS parameters under each destination address through the information obtained from the upper layer, and thus determine that the carriers supported by the QoS flows corresponding to at least two of the M QoS parameters under the first destination address are different or partially the same.

[0246] S803. The terminal device establishes N SLRBs for the QoS flows corresponding to N QoS parameters under the first destination address, where the QoS flows corresponding to the N QoS parameters corresponding to the first destination address are in one-to-one correspondence with the N SLRBs.

[0247] It should be understood that the QoS flows corresponding to the other M - N QoS parameters can also be mapped to the corresponding N SLRBs according to the obtained SLRB configuration.

[0248] The terminal device judges that there may be the following problems according to the obtained SLRB configuration: the carriers supported by N QoS flows under one destination address are not exactly the same, N is greater than or equal to 2, and these N QoS flows are mapped to the same SLRB / LCH, and at least one QoS flow is mapped to the SLRB / LCH corresponding to a carrier that is not supported. Here, "not supported" can be understood as not fully supported or completely not supported. For this problem, the terminal device establishes N SLRBs / LCHs for the N QoS flows associated with this destination address, and the N QoS flows are in one-to-one correspondence with the N SLRBs / LCHs.

[0249] Optionally, if there are N different carrier lists supported by multiple QoS flows associated with one destination address, the terminal device establishes N SLRBs. N is an integer greater than 1.

[0250] Optionally, the terminal device assigns different SLRB IDs or LCH IDs to the N SLRBs / LCHs.

[0251] In summary, through Figure 8 the embodiments, the terminal device establishes multiple SLRBs / LCHs for one destination address based on one SLRB configuration, which can ensure that all QoS flows mapped to one SLRB / LCH support the same carrier information, so that SL transmission can be carried out normally.

[0252] When the current terminal device performs SL communication, it needs to determine the carrier information that the SL communication can support. The carriers supported by terminal devices for SL communication in different geographical regions may be different. For example, different countries and regions allocate different spectrum ranges for the SL communication of terminal devices. Therefore, the terminal device needs to know the carriers that can be supported within the current geographical region, so that the SL communication of the terminal device can meet the policies and regulations and ensure the quality of SL communication. In view of this, as Figure 9 shown, the present application also provides a method for SL communication, and the specific process is as follows.

[0253] S901. The terminal device obtains the correspondence between geographical region information and carrier information.

[0254] The terminal device can obtain the correspondence between the geographical area and the carrier information through RRC messages, SIB messages, or pre-configuration. The state of the terminal device can be in the RRC connected state or the RRC non-connected state.

[0255] Exemplarily, for a terminal device out of coverage (OOC), it obtains the correspondence between the geographical area and the carrier information through pre-configuration.

[0256] It should be understood that the carrier information can include the carrier index and / or the synchronization type supported by the carrier.

[0257] It should be understood that different geographical area information can also correspond to the same carrier information.

[0258] Optionally, the geographical location can be at the national or regional level. For example, different countries or regions correspond to different geographical areas.

[0259] Optionally, the geographical location can be at the local level. For example, different provinces, cities, counties, districts, towns, etc. correspond to different geographical areas.

[0260] Optionally, the geographical location can be at the cell level. For example, different cells correspond to different geographical areas. Exemplarily, at this time, the correspondence between the geographical area information and the carrier information is the correspondence between the cell global identification (CGI) and the carrier information.

[0261] Optionally, the geographical location can be at the zone level. For example, different zones within a cell correspond to different geographical areas.

[0262] It should be understood that the geographical location can also be at other levels, which is not limited in the present invention.

[0263] S902. The terminal device determines the current geographical area information.

[0264] There are various ways for the terminal device to obtain the current geographical area information. Exemplarily, the terminal device obtains the current geographical location coordinates through the global positioning system (GPS) to determine the current geographical area information, or the terminal device obtains the cell identification to determine the current geographical area information. The terminal device can obtain the cell identification by reading the master information block (MIB) or the system information block (SIB) message.

[0265] Optionally, S902 can be executed before S901.

[0266] S903. The terminal device determines the carrier information supported by the current geographical area SL communication according to the correspondence between the geographical area information and the carrier information.

[0267] Exemplarily, the terminal device determines the carrier information corresponding to the current geographical area information according to S901 and S902, and can perform resource selection for SL transmission according to the supported carrier information.

[0268] It should be understood that SL communication includes SL transmission and / or SL reception.

[0269] In summary, through the above process, the terminal device determines the carrier information supported by the current geographical area to perform subsequent SL communication, ensuring compliance with policies and regulations and the quality of SL communication.

[0270] So far, the sidelink communication method provided in the embodiments of the present application has been introduced. It should be noted that the above embodiments are based on the same concept, and the methods of the various embodiments can be referred to each other. For example, the introduction of some concepts and the description of optional implementation manners can be referred to each other.

[0271] It should be noted that the examples in the various application scenarios of the present application only show some possible implementation manners, and are for better understanding and explanation of the method of the present application. Those skilled in the art can obtain some examples of evolved forms according to the indication method of the reference signal provided in the application.

[0272] In the above embodiments provided by the present application, the method provided in the embodiments of the present application is introduced from the perspectives of the network device, the terminal, and the interaction between the network device and the terminal. To implement the various functions in the method provided in the embodiments of the present application, the network device and the terminal may include a hardware structure and / or a software module, and implement the above various functions in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module. Whether a certain function among the above various functions is executed in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module depends on the specific application and design constraint conditions of the technical solution.

[0273] Such as Figure 10As shown, based on the same inventive concept, an embodiment of the present application further provides an apparatus 1000. The apparatus 1000 may be a terminal device or a network device, or a device in a terminal device or a network device, or a device that can be used in conjunction with a terminal device or a network device. In one design, the apparatus 1200 may include modules corresponding one by one to the methods / operations / steps / actions performed by the terminal device or the network device in the above method embodiments. The module may be a hardware circuit, software, or a combination of a hardware circuit and software. In one design, the apparatus may include a processing module 1001 and a communication module 1002. The processing module 1001 is used to call the communication module 1002 to perform the functions of receiving and / or sending.

[0274] When used to execute the method performed by the terminal device:

[0275] In a possible example, the communication module 1002 is used to send first information to a network device. The first information includes: a first destination address, a first carrier index, and a first quality of service (QoS) parameter. The first destination address, the first carrier index, and the first QoS parameter have a corresponding relationship, and is used to receive configuration information of a sidelink radio bearer (SLRB) from the network device.

[0276] In another possible example, the processing module 1001 is used to call the communication module 1002 to send first information to a network device. The first information includes: a first destination address, a first carrier index, and at least one quality of service (QoS) parameter. The first destination address, the first carrier index, and the at least one QoS parameter have a corresponding relationship. All QoS flows corresponding to the at least one QoS parameter support the carrier indicated by the first carrier index; and is used to receive configuration information of a sidelink radio bearer (SLRB) from the network device.

[0277] In another possible example, the processing module 1001 is used to obtain configuration information of a sidelink radio bearer (SLRB). The configuration information of the sidelink radio bearer (SLRB) includes one or more quality of service (QoS) parameters; and is used to establish an SLRB for a destination address according to the configuration information of the SLRB. The SLRB is associated with one or more QoS parameters corresponding to the destination address; and is used to determine carrier information supported by the SLRB; the carrier information is carrier information supported by all QoS flow information corresponding to the destination address information.

[0278] In another possible example, the processing module 1001 is configured to obtain the configuration information of a sidelink radio bearer (SLRB), where the SLRB configuration information includes M quality of service (QoS) parameters, the M QoS flow information is associated with different lists of M carrier information, and M is an integer greater than 1; and is configured to determine that among the M QoS parameters corresponding to the first destination address, the carriers supported by the QoS flows corresponding to N QoS parameters are not completely the same; and is configured to establish N SLRBs for the QoS flows corresponding to the N QoS parameters corresponding to the first destination address; where the QoS flows corresponding to the N QoS parameters corresponding to the first destination address are in one-to-one correspondence with the N SLRBs.

[0279] In another possible example, the communication module 1002 is configured to obtain the correspondence between geographical area information and carrier information; and is configured to determine the carrier information supported by sidelink (SL) communication in the current geographical area according to the correspondence between geographical area information and carrier information.

[0280] When used to execute the method performed by a network device:

[0281] In one example, the communication module 1002 is configured to receive first information from a terminal device, where the first information includes: a first destination address, a first carrier index, and a first quality of service (QoS) parameter, and there is a corresponding relationship among the first destination address, the first carrier index, and the first QoS parameter; the processing module 1001 is configured to determine the configuration information of a sidelink radio bearer (SLRB) according to the first information, and the communication module 1002 is further configured to send the SLRB configuration information to the terminal device.

[0282] In another example, the communication module 1002 is configured to receive first information from a terminal device, where the first information includes: a first destination address, a first carrier index, and at least one quality of service (QoS) parameter, and there is a corresponding relationship among the first destination address, the first carrier index, and the at least one QoS parameter, and the QoS flows corresponding to the at least one QoS parameter all support the carrier indicated by the first carrier index; the processing module 1001 is configured to determine the configuration information of a sidelink radio bearer (SLRB) according to the first information, and the communication module 1002 is further configured to send the SLRB configuration information to the terminal device.

[0283] The processing module 1001 and the communication module 1002 may also be configured to perform other corresponding steps or operations performed by the terminal device or the network device in the above method embodiments, which will not be elaborated here one by one.

[0284] In the embodiments of the present application, the division of modules is illustrative, merely a logical function division. In actual implementation, there may be other division methods. Additionally, in each embodiment of the present application, each functional module may be integrated in a processor, may exist independently physically, or two or more modules may be integrated in one module. The above integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0285] As Figure 11 Shown in the figure is apparatus 1100 provided by an embodiment of the present application, which is used to implement the functions of the terminal device or network device in the above method. When implementing the functions of the network device, this apparatus may be a network device, may be a device in the network device, or may be a device that can be used in combination with the network device. When implementing the functions of the terminal device, this apparatus may be a terminal device, may be a device in the terminal device, or may be a device that can be used in combination with the terminal device. Among them, this apparatus may be a chip system. In the embodiments of the present application, the chip system may be composed of chips or may include chips and other discrete devices. Apparatus 1100 includes at least one processor 1120, which is used to implement the functions of the terminal device or network device in the method provided by the embodiments of the present application. Apparatus 1100 may further include a communication interface 1110. In the embodiments of the present application, the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces, which are used to communicate with other devices through a transmission medium. For example, communication interface 1110 is used for the apparatus in apparatus 1100 to communicate with other devices. Exemplarily, when apparatus 1100 is a network device, the other device may be a terminal device. When apparatus 1100 is a terminal device, the other apparatus may be a network device. Processor 1120 uses communication interface 1110 to send and receive data and is used to implement the method described in the above method embodiments. Exemplarily, when implementing the functions of the terminal device, processor 1120 is used to use communication interface 1110 to send a first piece of information to the network device, the first piece of information including: a first destination address, a first carrier index, and a first quality of service (QoS) parameter. The first destination address, the first carrier index, and the first QoS parameter have a corresponding relationship, and to receive configuration information of a sidelink radio bearer (SLRB) from the network device.

[0286] In another possible example, processor 1120 is used to use communication interface 1110 to send a first piece of information to the network device, the first piece of information including: a first destination address, a first carrier index, and at least one quality of service (QoS) parameter. The first destination address, the first carrier index, and the at least one QoS parameter have a corresponding relationship. All QoS flows corresponding to the at least one QoS parameter support the carrier indicated by the first carrier index; and is used to receive configuration information of a sidelink radio bearer (SLRB) from the network device.

[0287] In another possible example, the processor 1120 is configured to obtain configuration information of a sidelink radio bearer (SLRB), where the configuration information of the SLRB includes one or more quality of service (QoS) parameters; and is configured to establish an SLRB for a destination address according to the configuration information of the SLRB, where the SLRB is associated with one or more QoS parameters corresponding to the destination address; and is configured to determine carrier information supported by the SLRB; the carrier information is carrier information supported by one or more QoS flow information corresponding to the destination address information.

[0288] In another possible example, the processor 1120 is configured to obtain configuration information of a sidelink radio bearer (SLRB), where the SLRB configuration information includes M quality of service (QoS) parameters, and the M QoS flow information is associated with different lists of M carrier information, and M is an integer greater than 1; and is configured to determine that among the M QoS parameters corresponding to a first destination address, the carriers supported by the QoS flows corresponding to N QoS parameters are not completely the same; and is configured to establish N SLRBs for the QoS flows corresponding to the N QoS parameters corresponding to the first destination address; where the QoS flows corresponding to the N QoS parameters corresponding to the first destination address are in one-to-one correspondence with the N SLRBs.

[0289] In another possible example, the processor 1120 is configured to use the communication interface 1110 to obtain the correspondence between geographical area information and carrier information; and is configured to determine the carrier information supported by sidelink (SL) communication in the current geographical area according to the correspondence between the geographical area information and the carrier information.

[0290] When implementing the functions of the terminal device, the processor 1120 is configured to use the communication interface to receive first information from the terminal device, where the first information includes: a first destination address, a first carrier index, and a first quality of service (QoS) parameter, and there is a corresponding relationship among the first destination address, the first carrier index, and the first QoS parameter; the processor 1120 is configured to determine the configuration information of a sidelink radio bearer (SLRB) according to the first information, and the processor 1120 is further configured to use the communication interface 1110 to send the configuration information of the SLRB to the terminal device.

[0291] Alternatively, when implementing the functions of the terminal device, the processor 1120 is configured to receive first information from the terminal device by using the communication interface 1110. The first information includes: a first destination address, a first carrier index, and at least one quality of service (QoS) parameter. There is a corresponding relationship among the first destination address, the first carrier index, and the at least one QoS parameter. All QoS flows corresponding to the at least one QoS parameter support the carrier indicated by the first carrier index. The processor 1120 is configured to determine configuration information of a sidelink radio bearer (SLRB) according to the first information, and the processor 1120 is further configured to send the configuration information of the SLRB to the terminal device by using the communication interface 1110.

[0292] The processor 1120 and the communication interface 1110 may also be configured to perform other corresponding steps or operations executed by the terminal device or the network device in the foregoing method embodiments, which will not be elaborated herein one by one.

[0293] The apparatus 1100 may further include at least one memory 1130, configured to store program instructions and / or data. The memory 1130 is coupled to the processor 1120. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which may be electrical, mechanical, or other forms, and is used for information interaction between devices, units, or modules. The processor 1120 may cooperate with the memory 1130. The processor 1120 may execute the program instructions stored in the memory 1130. At least one of the at least one memories may be included in the processor.

[0294] In the embodiments of the present application, the specific connection medium among the foregoing communication interface 1110, processor 1120, and memory 1130 is not limited. In the embodiments of the present application Figure 11 it is shown that the memory 1130, the processor 1120, and the communication interface 1110 are connected through a bus 1140. The bus is represented by a thick line in Figure 11 The connection manners of other components are only for illustrative purposes and are not to be construed as limiting. The bus may be divided into an address bus, a data bus, a control bus, etc. For the sake of simplicity of representation, Figure 11 only one thick line is used to represent it in

[0295] When apparatuses 1000 and 1100 are specifically chips or chip systems, the signals output or received by communication module 1002 and communication interface 1110 may be baseband signals. When apparatuses 1000 and 1100 are specifically devices, the signals output or received by communication module 1202 and communication interface 1110 may be radio frequency signals. In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.

[0296] In the embodiments of the present application, memory 1130 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or may also be a volatile memory, such as a random-access memory (RAM). The memory is any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory in the embodiments of the present application may also be a circuit or any other device capable of implementing a storage function, for storing program instructions and / or data.

[0297] Some or all of the operations and functions performed by the terminal described in the method embodiments of the present application, or some or all of the operations and functions performed by the network device, may be completed by a chip or an integrated circuit.

[0298] To implement the above Figure 10 or Figure 11 functions of the communication apparatus, the embodiments of the present application further provide a chip, including a processor, for supporting the communication apparatus to implement the functions involved in the terminal or the network device in the above method embodiments. In a possible design, the chip is connected to a memory or the chip includes a memory, and the memory is used to store the necessary program instructions and data of the communication apparatus.

[0299] The embodiments of the present application provide a computer-readable storage medium, storing a computer program, and the computer program includes instructions for executing the above method embodiments.

[0300] The embodiments of the present application provide a computer program product containing instructions, which when running on a computer, causes the computer to execute the above method embodiments.

[0301] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0302] The present application is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be realized by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate means for realizing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0303] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including instruction means that realize the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0304] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for realizing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0305] Although the preferred embodiments of the present application have been described, those skilled in the art can make additional changes and modifications to these embodiments once they learn the basic creative concepts. Therefore, the appended claims are intended to be construed to include the preferred embodiments as well as all changes and modifications that fall within the scope of the present application.

[0306] Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the embodiments of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to cover these changes and modifications.

Claims

1. A communication method, characterized in that, comprising: obtaining sidelink radio bearer (SLRB) configuration information, where the SLRB configuration information includes one or more quality of service (QoS) parameters corresponding to a destination address; establishing an SLRB for the destination address according to the SLRB configuration information, where the SLRB is associated with one or more QoS parameters corresponding to the destination address.

2. The method according to claim 1, characterized in that, the method further comprises: determining carrier information corresponding to a carrier supported by the SLRB, where the carrier information is carrier information supported by QoS flows indicated by one or more QoS parameters corresponding to the destination address.

3. The method according to claim 1 or 2, characterized in that, the SRLB configuration information further includes information of the destination address or carrier information.

4. The method according to claim 2 or 3, characterized in that, the method further comprises: ensuring data transmission of the SLRB on the carrier through logical channel priority (LCP).

5. The method according to any one of claims 1-4, characterized in that, the one or more QoS parameters include a QoS flow identifier and / or a QoS profile.

6. The method according to claim 5, characterized in that, the QoS profile includes one or more of the following parameters: PC5 interface 5G quality of service identifier, guaranteed traffic bit rate, maximum traffic bit rate, minimum required communication distance, allocation and retention priority, maximum aggregated bit rate of the PC5 link, default value, resource type, priority level, packet delay budget, packet error rate, average window, maximum data burst volume, guaranteed bit rate, delay critical GBR or non-GBR.

7. The method according to any one of claims 1-6, characterized in that, the method further comprises: obtaining second information, where the second information includes a service identifier and a first carrier index; determining that QoS flows under the service corresponding to the service identifier support the carrier indicated by the first carrier index.

8. A communication method, characterized in that, comprising: sending sidelink radio bearer (SLRB) configuration information, where the SLRB configuration information includes one or more quality of service (QoS) parameters corresponding to a destination address; the SLRB configuration information is used to establish an SLRB for the destination address, where the SLRB is associated with one or more QoS parameters corresponding to the destination address.

9. The method according to claim 8, characterized in that, the carrier information corresponding to the carrier supported by the SLRB is carrier information supported by QoS flows indicated by one or more QoS parameters corresponding to the destination address.

10. The method according to claim 8 or 9, characterized in that, the SRLB configuration information further includes information of the destination address or carrier information.

11. The method according to any one of claims 8-10, characterized in that, the one or more QoS parameters include a QoS flow identifier and / or a QoS profile.

12. The method according to claim 11, characterized in that, the QoS profile includes one or more of the following parameters: PC5 interface 5G service quality identifier, guaranteed traffic bit rate, maximum traffic bit rate, minimum required communication distance, allocation and reservation priority, maximum aggregated bit rate of the PC5 link, default value, resource type, priority level, packet delay budget, packet error rate, average window, maximum data burst volume, guaranteed bit rate, delay-critical GBR or non-GBR.

13. The method according to any one of claims 8-12, characterized in that, the method further comprises: sending second information, the second information including a service identifier and a first carrier index.

14. A communication device, characterized in that, comprises a module for performing the method according to any one of claims 1 to 7, or the method according to any one of claims 8 to 13.

15. A communication device, characterized in that, comprises a processor; when the communication device is running, the processor executes computer instructions to perform the method according to any one of claims 1 to 7, or to perform the method according to any one of claims 8 to 13.

16. A computer program product, characterized in that, the computer program product comprises instructions which, when run on a communication device, cause the communication device to perform the method according to any one of claims 1 to 7, or to perform the method according to any one of claims 8 to 13.

17. A computer-readable storage medium, characterized in that, the storage medium stores a computer program or instructions which, when executed by a communication device, implement the method according to any one of claims 1 to 7, or the method according to any one of claims 8 to 13.

18. A communication system, characterized in that, comprises a terminal device for performing the method according to any one of claims 1 to 7, and a network device for performing the method according to any one of claims 8 to 13.

19. A chip, characterized in that, the chip is connected to a memory or the chip comprises the memory, for reading and executing a software program stored in the memory to implement the method according to any one of claims 1 to 7, or to implement the method according to any one of claims 8 to 13.

Images