Sideline communication method and device

Abstract

A sidelink communication method and device are provided to solve the problem of reducing SL communication quality by mapping QoS flows supporting different carriers to the same SLRB. The method comprises: a terminal device sends first information to a network device, the first information comprises: a first destination address, a first carrier index and a first quality of service QoS parameter, and the first destination address, the first carrier index and the first QoS parameter have a corresponding relationship; the network device receives the first information from the terminal device, the network device determines and sends the configuration information of the sidelink bearer SLRB to the terminal device based on the first information, and the terminal device receives the configuration information of the sidelink bearer SLRB from the network device.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a sideline communication method and device. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) international standardization organization has initiated research on vehicle to everything (V2X) since the long term evolution (LTE) R14, and proposed a V2X communication architecture. In the V2X communication architecture, data can be directly transmitted between terminal devices through sidelinks (SL).

[0003] Before the terminal device performs SL communication, the terminal device will obtain the configuration information of the sidelink radio bearer (SLRB) from the network device. Based on the configuration information of the SLRB, the terminal device establishes the SLRB and maps the quality of service (QoS) flow to the corresponding SLRB. Since different QoS flows under a destination address may support different carriers, the terminal device may map QoS flows supporting 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 carriers that they do not support, thereby reducing the quality of SL communication. Summary of the invention

[0004] The present application provides a sideline communication method and device, in order to solve the problem of mapping QoS flows supporting different carriers to the same SLRB and reducing the SL communication quality.

[0005] In the first aspect, a sideline communication method is provided, the method comprising the following steps: a terminal device sends 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, and the first destination address, the first carrier index and the first QoS parameter have a corresponding relationship. 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, and 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, so as to avoid the QoS flow data packet 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.

[0006] In one possible design, the terminal device receives configuration information of the sidelink bearer SLRB from the network device. The configuration of the SLRB determined by the network device is determined according to the carrier supported by the QoS flow. After the terminal device receives the configuration information of the SLRB, it will not map the QoS flow to the SLRB corresponding to the unsupported carrier, thereby improving the SL communication quality.

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

[0008] In one possible design, the first information also includes the second QoS parameter, and the second QoS parameter corresponds to the first carrier index.

[0009] In one possible design, the QoS parameters include a QoS flow identifier and / or a QoS profile.

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

[0011] In a possible design, the reporting method of the first information may be a full information reporting method or a delta information reporting method.

[0012] In the second aspect, a side communication method is provided, which includes the following steps: a terminal device sends first information to a network device, wherein the first information includes: a first destination address, a first carrier index and at least one quality of service QoS parameter, wherein the first destination address, the first carrier index and the at least one QoS parameter have a corresponding relationship, and the QoS flows corresponding to the at least one QoS parameter all support the carrier indicated by the first carrier index. The terminal device reports the carrier index of the carrier supported by all QoS flows corresponding to the QoS parameters under the destination address to the network device. After receiving the reported first information, when the network device configures SLRB for the terminal according to the first information, it will not configure a carrier that is not supported by the QoS flow of the destination address, thereby avoiding the use of carrier frequencies that the data packets of the QoS flow do not support for SL transmission. This improves the configuration accuracy of SLRB and improves the SL communication quality.

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

[0014] In one possible design, after the terminal device sends the first information to the network device, the terminal device receives configuration information of the side link bearer SLRB from the network device.

[0015] Optionally, if the index of the carriers supported by the QoS flows corresponding to multiple QoS parameters with the same QoS file associated with the destination address is an empty set, the access layer of the terminal device sends an indication message to the upper layer (such as the V2X layer), and the indication message is used to indicate that the QoS flow or service corresponding to the same QoS file associated with this destination address is unreasonable. Optionally, after receiving the indication message, the upper layer of the terminal device triggers the PC5-S link modification process with the opposite terminal device, or modifies the QoS parameter / service information associated with this destination address.

[0016] Optionally, if the index of the carriers supported by the QoS flows of multiple QoS parameters 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 information about the multiple QoS flows, indicating that the QoS flows corresponding to the multiple QoS parameters are not supported for SL transmission of any carrier index under the first destination address. Alternatively, the multiple QoS parameters are associated with an indication information, which is used to indicate that the QoS flows corresponding to the multiple QoS parameters are not supported for SL transmission of any carrier index under the first destination address.

[0017] In one possible design, the QoS parameters include a QoS flow identifier and / or a QoS profile.

[0018] In one possible design, the method also includes: the terminal device obtains second information, the second information including 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.

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

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

[0021] In a third aspect, a sidelink communication method is provided, the method comprising the following steps: a terminal device obtains configuration information of a sidelink bearer SLRB, the configuration information of the sidelink bearer SLRB comprising 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, the SLRB is associated with one or more QoS parameters corresponding to the destination address; the terminal device determines the carrier information supported by the SLRB; the carrier information is the carrier information supported by one or more QoS flow information corresponding to the destination address information. In this way, when QoS flows associated with different carrier information are mapped to the same SLRB / LCH based on network configuration, the terminal can determine the carrier information allowed by the SLRB / LCH, so that unallowed carrier information will not be used for SL transmission.

[0022] Optionally, considering PDCP duplication, one SLRB will be associated with multiple 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.

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

[0024] In one possible design, the terminal device obtains the configuration information of the sidelink bearer SLRB, which may be achieved in the following way: the terminal device obtains the SLRB configuration information through an RRC message, a broadcast message or pre-configuration.

[0025] In a fourth aspect, a sidelink communication method is provided, the method comprising the following steps: a terminal device obtains configuration information of a sidelink bearer SLRB, wherein the SLRB configuration information comprises M quality of service QoS parameters, and the M QoS flow information is associated with M different carrier information lists, 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; wherein the QoS flows corresponding to the N QoS parameters corresponding to the first destination address correspond one-to-one to the N SLRBs. 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 associated with the same carrier information, so that SL transmission can be performed normally.

[0026] In one possible design, the terminal device allocates different SLRB identifiers or logical channel LCH identifiers to the M SLRBs.

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

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

[0029] In one possible design, the terminal device obtains the configuration information of the sidelink bearer SLRB in the following way: the terminal device obtains the SLRB configuration information through an RRC message, a broadcast message or pre-configuration.

[0030] In a fifth aspect, a sidelink communication method is provided, the method comprising the following steps: a network device receives first information from a terminal 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; the network device determines and sends the configuration information of the sidelink 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, the first information comprising the above-mentioned corresponding relationship, the network device can determine the SLRB configuration according to the corresponding relationship, and can map the QoS flow configuration to the SLRB corresponding to the carrier supported by the Qos flow, so as to avoid the QoS flow data packet using the carrier frequency that it does not support for SL transmission. Thereby, the accuracy of the SLRB configuration is improved, and the SL communication quality is improved.

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

[0032] In one possible design, the first information also includes the second QoS parameter, and the second QoS parameter corresponds to the first carrier index.

[0033] In one possible design, the QoS parameters include a QoS flow identifier and / or a QoS profile.

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

[0035] In a sixth aspect, a sidelink communication method is provided, the method comprising the following steps: a network device receives first information from a terminal device, the first information comprising: 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 the QoS flows corresponding to the at least one QoS parameter all support the carrier indicated by the first carrier index; the network device determines and sends the configuration information of the sidelink bearer SLRB to the terminal device according to the first information. The carrier index of the carrier supported by all QoS flows corresponding to the QoS parameters under the destination address received by the network device from the terminal, after receiving the reported first information, when the network device configures the SLRB for the terminal according to the first information, it will not configure a carrier that is not supported by the QoS flow of the destination address, so as to avoid the data packets of the QoS flow using the carrier frequency that it does not support for SL transmission. Thereby, the configuration accuracy of the SLRB is improved, and the SL communication quality is improved.

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

[0037] In one possible design, the QoS parameters include a QoS flow identifier and / or a QoS profile.

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

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

[0040] In a seventh aspect, a sideline communication method is provided, the execution subject of the method may be a terminal device, and the method includes the following steps: the terminal device obtains the correspondence between the geographical area information and the carrier information; the terminal device determines the carrier information supported by the 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 carry out subsequent SL communication, ensuring that policies and regulations are met and the quality of SL communication is met.

[0041] Optionally, the terminal device may obtain the correspondence between the geographical area information and the carrier information through an RRC message, a SIB message or a pre-configuration. The state of the terminal device may be an RRC connected state or an RRC non-connected state.

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

[0043] Optionally, different geographical area information may also correspond to the same carrier information.

[0044] Optionally, the geographical location may be at a country or region level, for example, different countries or regions correspond to different geographical areas.

[0045] Optionally, the geographical location may be at a cell level, for example, different cells correspond to different geographical areas.

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

[0047] In an eighth aspect, a device is provided, 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 combination with the terminal device. In one design, the device may include a module that executes the method / operation / step / action described in the first aspect, and the module may be a hardware circuit, or software, or a hardware circuit combined with 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, the first 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 having a corresponding relationship, and for receiving configuration information of a side link bearer SLRB from the network device. In this way, through the first information, the terminal device can indicate the carrier information corresponding to each QoS parameter under the destination address to the network device. 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 QoS flow data packet using the carrier frequency it does not support for SL transmission. Thereby improving the accuracy of SLRB configuration and improving the SL communication quality.

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

[0049] In one possible design, the first information also includes the second QoS parameter, and the second QoS parameter corresponds to the first carrier index.

[0050] In one possible design, the QoS parameters include a QoS flow identifier and / or a QoS profile.

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

[0052] In a possible design, the reporting method of the first information may be a full information reporting method or a delta information reporting method.

[0053] In a ninth aspect, a device is provided, which may be a terminal device, or a device located in a terminal device (for example, a chip, or a chip system, or a circuit), or a device that can be used in combination with a terminal device. In one design, the device may include a module that performs one-to-one correspondence between the method / operation / step / action described in the second aspect, and 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 used to call the communication module to perform the functions of receiving and / or sending. Exemplarily:

[0054] The processing module is used to call the communication module to send the first information to the network device, wherein the first information includes: a first destination address, a first carrier index and at least one quality of service QoS parameter, wherein the first destination address, the first carrier index and the at least one QoS parameter have a corresponding relationship, and the QoS flows corresponding to the at least one QoS parameter all support the carrier indicated by the first carrier index; and is used to receive the configuration information of the sidelink bearer SLRB from the network device. The terminal device reports the carrier index of the carrier supported by all QoS flows corresponding to the QoS parameters under the destination address to the network device. After receiving the reported first information, when the network device configures the SLRB for the terminal according to the first information, it will not configure the carrier that is not supported by the QoS flow of the destination address, thereby avoiding the data packets of the QoS flow from using the carrier frequency that it does not support for SL transmission. Thereby, the configuration accuracy of the SLRB is improved, and the SL communication quality is improved.

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

[0056] Optionally, if the index of the carriers supported by the QoS flows corresponding to multiple QoS parameters with the same QoS file associated with the destination address is an empty set, the access layer of the terminal device sends an indication message to the upper layer (such as the V2X layer), and the indication message is used to indicate that the QoS flow or service corresponding to the same QoS file associated with this destination address is unreasonable. Optionally, after receiving the indication message, the upper layer of the terminal device triggers the PC5-S link modification process with the opposite terminal device, or modifies the QoS parameter / service information associated with this destination address.

[0057] Optionally, if the index of the carriers supported by the QoS flows of multiple QoS parameters 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 information about the multiple QoS flows, indicating that the QoS flows corresponding to the multiple QoS parameters are not supported for SL transmission of any carrier index under the first destination address. Alternatively, the multiple QoS parameters are associated with an indication information, which is used to indicate that the QoS flows corresponding to the multiple QoS parameters are not supported for SL transmission of any carrier index under the first destination address.

[0058] In one possible design, the QoS parameters include a QoS flow identifier and / or a QoS profile.

[0059] In one possible design, the processing module is also used to obtain second information, the second information including 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.

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

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

[0062] In the tenth aspect, a device is provided, 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 combination with the terminal device. In one design, the device may include a module that performs the method / operation / step / action described in the third aspect, and 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 used to call the communication module to perform the functions of receiving and / or sending. Exemplarily:

[0063] The processing module is used to obtain the configuration information of the sidelink bearer SLRB, the configuration information of the sidelink bearer SLRB includes one or more quality of service QoS parameters; and is used to establish the SLRB for the destination address according to the configuration information of the SLRB, and 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 one or more QoS flow information corresponding to the destination address information. In this way, when QoS flows associated with different carrier information are mapped to the same SLRB / LCH based on the network configuration, the terminal can determine the carrier information allowed by the SLRB / LCH, so that the unallowed carrier information will not be used for SL transmission.

[0064] Optionally, considering PDCP duplication, one SLRB will be associated with multiple 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.

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

[0066] In one possible design, when obtaining the configuration information of the sidelink bearer SLRB, the processing module is specifically used to: obtain the SLRB configuration information through an RRC message, a broadcast message or pre-configuration.

[0067] In the eleventh aspect, a device is provided, 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 combination with the terminal device. In one design, the device may include a module that performs the method / operation / step / action described in the fourth aspect, which 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 used to call the communication module to perform the functions of receiving and / or sending. Exemplarily:

[0068] The processing module is used to obtain the configuration information of the sidelink bearer SLRB, wherein the SLRB configuration information includes M quality of service QoS parameters, the M QoS flow information is associated with M different carrier information lists, and M is an integer greater than 1; and is used to determine that among the M QoS parameters corresponding to the first destination address, there are N QoS parameters corresponding to the QoS flows that support different carriers; and is used to establish N SLRBs for the QoS flows corresponding to the N QoS parameters corresponding to the first destination address; wherein the QoS flows corresponding to the N QoS parameters corresponding to the first destination address correspond one-to-one to the N SLRBs. 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 associated with the same carrier information, so that SL transmission can be performed normally.

[0069] In one possible design, the processing module is also used to assign different SLRB identifiers or logical channel LCH identifiers to the M SLRBs.

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

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

[0072] In one possible design, when obtaining the configuration information of the sidelink bearer SLRB, the processing module is specifically used to: obtain the SLRB configuration information through an RRC message, a broadcast message or pre-configuration.

[0073] In the twelfth aspect, a device is provided, which may be a network device, or a device located in the 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 may include a module that corresponds to the method / operation / step / action described in the fifth or sixth aspect, and 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 used to call the communication module to perform the functions of receiving and / or sending. Exemplarily:

[0074] When executing the method of the fifth aspect, the communication module is used to receive the first information from the terminal device, and the first information includes: a first destination address, a first carrier index and a first quality of service QoS parameter, and the first destination address, the first carrier index and the first QoS parameter have a corresponding relationship; the processing module is used to determine the configuration information of the side link bearer SLRB according to the first information, and the communication module is also used to send the configuration information of the SLRB 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-mentioned 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, so as to avoid the QoS flow data packet 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.

[0075] When executing the method of the sixth aspect, the communication module is used to receive the first information from the 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 the QoS flows corresponding to the at least one QoS parameter all support the carrier indicated by the first carrier index; the processing module is used to determine the configuration information of the sidelink bearer SLRB according to the first information, and the communication module is also used to send the configuration information of the SLRB to the terminal device. The carrier index of the carrier supported by all QoS flows corresponding to the QoS parameters under the destination address received by the network device from the terminal, after receiving the reported first information, when the network device configures the SLRB for the terminal according to the first information, it will not configure the carrier that is not supported by the QoS flow of the destination address, so as to avoid the data packets of the QoS flow using the carrier frequency that it does not support for SL transmission. Thereby, the configuration accuracy of the SLRB is improved, and the SL communication quality is improved.

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

[0077] In the thirteenth aspect, a device is provided, 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 combination with the terminal device. In one design, the device may include a module that performs the method / operation / step / action described in the fourth aspect, and 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 used to call the communication module to perform the functions of receiving and / or sending. Exemplarily:

[0078] The communication module is used to obtain the correspondence between the geographical area information and the carrier information; and to determine the carrier information supported by the 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 carry out subsequent SL communication, ensuring that policies and regulations are met and the quality of SL communication is met.

[0079] The processing module and the communication module can also perform operations corresponding to the above-mentioned seventh aspect or any possible design method of the seventh aspect, which will not be repeated here.

[0080] In a fourteenth aspect, an embodiment of the present application provides a device, comprising a communication interface and a processor, wherein the communication interface is used for the device to communicate with other devices, such as the transmission and reception 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 method described in any possible design of the first aspect, the second aspect, the third aspect, the fourth aspect, the seventh aspect or these aspects. The device may also include a memory for storing programs, instructions or data called by the processor. The memory is coupled to the processor, and when the processor executes the instructions or data stored in the memory, the method of any possible design of the first aspect, the second aspect, the third aspect, the fourth aspect, the seventh aspect or these aspects may be implemented.

[0081] In a fifteenth aspect, an embodiment of the present application provides a device, comprising a communication interface and a processor, wherein the communication interface is used for the device to communicate with other devices, such as the transmission and reception 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 method described in any possible design of the fifth aspect, the sixth aspect or both of the above aspects. The device may also include a memory for storing programs, instructions or data called by the processor. The memory is coupled to the processor, and when the processor executes the instructions or data stored in the memory, the method described in any possible design of the fifth aspect, the sixth aspect or both of the above aspects can be implemented.

[0082] In the sixteenth aspect, a computer-readable storage medium is also provided in an embodiment of the present application, wherein the computer-readable storage medium stores computer-readable instructions. When the computer-readable instructions are executed on a computer, the computer executes 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.

[0083] In the seventeenth aspect, an embodiment of the present application also provides a computer-readable storage medium, including instructions, which, when executed on a computer, enables the computer to execute a method as described in the fifth aspect, the sixth aspect, or any possible design of these two aspects.

[0084] In the eighteenth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables 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.

[0085] In the nineteenth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the method described in the fifth aspect, the sixth aspect, or any possible design of these two aspects.

[0086] In a twentieth aspect, an embodiment of the present application provides a chip system, which includes a processor and may also 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 a chip, or may include a chip and other discrete devices.

[0087] In aspect 21, an embodiment of the present application provides a chip system, which includes a processor and may also include a memory, for implementing the method described in any possible design of aspect 5, aspect 6, or both of the above aspects. The chip system may be composed of a chip, or may include a chip and other discrete devices.

[0088] In aspect 22, an embodiment of the present application provides a chip system, which includes a processor and may also include a memory, for implementing the method described in aspect 1, aspect 2, aspect 3, aspect 4, aspect 7, or any possible design of these aspects. The chip system may be composed of a chip, or may include a chip and other discrete devices.

[0089] In aspect 23, an embodiment of the present application provides a chip system, which includes a processor and may also include a memory, for implementing the method described in any possible design of aspect 5, aspect 6, or both of the above aspects. The chip system may be composed of a chip, or may include a chip and other discrete devices.

[0090] In the twenty-fourth aspect, an embodiment of the present application provides a system, comprising a terminal device and a network device, wherein 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. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0092] Figure 2 This is one of the flow charts of the side communication method in the embodiment of the present application;

[0093] Figure 3 This is the second flow chart of the side communication method in the embodiment of the present application;

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

[0095] Figure 5 This is the third flow chart of the side communication method in the embodiment of the present application;

[0096] Figure 6 A schematic diagram of a carrier index supported by a QoS flow corresponding to a QoS parameter in an embodiment of the present application;

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

[0098] Figure 8 This is the fourth flow chart of the side communication method in the embodiment of the present application;

[0099] Fig. 9 This is the fifth flow chart of the side communication method in the embodiment of the present application;

[0100] Fig.10 This is one of the schematic diagrams of the device structure in the embodiment of the present application;

[0101] Fig.11 This is the second schematic diagram of the device structure in the embodiment of this application. DETAILED DESCRIPTION

[0102] The embodiment of the present application provides a side communication method and device to improve the SL communication quality. Among them, the method and the device are based on the same or similar concept of the same technology. Since the principles of solving the problem by the method and the device are similar, the implementation of the device and the method can refer to each other, and the repetition will not be repeated. In the description of the embodiment of the present application, "and / or" describes the association relationship of the associated objects, indicating that there may be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the front and back associated objects are in an "or" relationship. 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, the words "first", "second", "third", etc. are only used for the purpose of distinguishing the description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order. The reference to "one embodiment" or "some embodiments" described in this specification means that one or more embodiments of the present application include specific features, structures or characteristics described in combination with the embodiment. Thus, the phrases "in one embodiment", "in some embodiments", "in some other embodiments", "in other embodiments", etc., which appear in different places in this specification, do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.

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

[0104] 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) services, and vehicle to infrastructure (V2I) services.

[0105] Among them, one participant of V2N is the terminal device, and the other participant is the service entity. V2N is currently the most widely used form of vehicle networking. Its main function is to connect vehicles to cloud servers through mobile networks, thereby providing navigation, entertainment, anti-theft and other functions through cloud servers.

[0106] Both participants in V2V are terminal devices. V2V can be used as information exchange reminders between vehicles, and its most typical application is in vehicle-to-vehicle collision avoidance safety systems.

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

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

[0109] In the embodiment of the present application, the transmitting end and the receiving end in V2X may both be D2D devices or V2X devices. For example, the transmitting end and the receiving end in V2X may both be terminal devices.

[0110] The terminal device in the embodiments of the present application may 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 may also be an IoT device. For example, the terminal device includes a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device may be: a mobile phone, a tablet computer, a laptop computer, a PDA, 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 car, 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 television, an air conditioner, an electric meter, etc.), an intelligent 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 an intelligent robot, a hot air balloon, a drone, an airplane), etc. The terminal may also be other devices with terminal functions. For example, the terminal may also be a device that serves as a terminal in D2D communication or Internet of Vehicles communication.

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

[0112] In the embodiment of the present application, the network device is a node in a radio access network (RAN), which can also be called a base station, or a RAN node (or device). At present, some examples of access network devices are: next generation nodeB (gNB), next generation evolved nodeB (Ng-eNB), transmission reception point (TRP), evolved NodeB (eNB), radio network controller (RNC), NodeB (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home NodeB, 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, and the satellite can also be called a high-altitude platform, a high-altitude aircraft, or a satellite base station. The network device may also be other devices having network device functions, for example, the network device 201 may also be a device that functions as a network device in D2D communication or Internet of Vehicles communication. The network device 201 may also be a network device in a possible future communication system.

[0113] In some deployments, the 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, and implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, and 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 active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be converted from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by the DU+AAU. It is understandable 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 an access network (radio access network, RAN), or the CU may be classified as a network device in a core network (core network, CN), which is not limited in this application.

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

[0115] Figure 1 A schematic diagram of a V2X communication architecture 100 is shown. Figure 1 As shown, the V2X communication architecture 100 includes: a V2X application server, a V2X device (e.g. Figure 1V2X UE 1 and V2X UE 2) and network equipment are shown in the figure. The V2X communication architecture includes two communication interfaces, namely PC5 interface and Uu interface. Among them, PC5 interface is a direct communication interface between V2XUEs, and the direct communication link between V2X UEs is also defined as a side link or side link (sidelink, SL). Uu interface communication is a communication mode in which the sender V2X UE (for example, V2X UE 1) sends V2X data to the network equipment through the Uu interface, sends it to the V2X application server through the network equipment for processing, and then sends it to the network equipment by the V2X application server, and sends it to the receiving V2X UE (for example, V2X UE 2) through the network equipment. In the Uu interface communication mode, the network equipment that forwards the uplink data of the sender V2X UE to the application server and the network equipment that forwards the downlink data sent by the application server to the receiving V2X UE can be the same network equipment or different network equipment, which can be determined by the application server. It should be understood that the transmission from the sender V2X UE to the network device is called uplink (UL) transmission. Figure 1 In the example, Uu UL is used to represent the transmission from the network device to the receiving V2X UE, which is called downlink (DL). Figure 1 Indicated by Uu DL.

[0116] In order to better understand the technical solution of the present application, some terms or concepts are introduced below.

[0117] 1) PC5 quality of service flow (PC5 QoS flow): can be referred to as QoS flow. A PC5 QoS flow is associated with a PC5 QoS flow indicator (PFI). PFI is an identifier assigned by the upper layer of the terminal device. PFI is used to uniquely identify a QoS flow under a 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 service quality identifier (PC5 5G quality of service identifier, PQI), guaranteed flow bit rate (guaranteed flow bit rate, GFBR), maximum flow bit rate (maximum flow bit rate, MFBR), minimum required communication range (minimurn required communication range, range), allocation and retention priority (allocation and retention priority, ARP), PC5 link maximum aggregation bit rate (PC5 LINK-aggregate maximum bit rate, PC5 LINK-AMBR), default values, resource type (resource type), priority level, packet delay budget (packet error rate, PER), averaging window (for GBR and Delay-critical GBR resource type QoS flow), or maximum data burst volume (maximum data burst volume) (for Delay-critical GBR resource type QoS flow) and other parameters. The resource type may be, for example, a guaranteed bit rate (GBR), a delay critical GBR (Delaycritical GBR), or a non-GBR (Non-GBR).

[0118] 2) Sidelink radio bearer SLRB: a bearer in layer 2 for sending and receiving sidelink data. SLRB includes 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 (e.g., source L2 ID) and a destination address identifier (e.g., destination L2 ID). The address information may also include a communication type (cast type). The cast type may be unicast, multicast, or broadcast.

[0119] 3) In the embodiments of the present application, "support", "associate" or "allow" may indicate the same or similar meanings. When it comes to "A supports B", it may mean "A is associated with B" or "A allows B". For example, the carrier index is associated with the QoS parameter, which can be understood as: the QoS flow corresponding to the QoS parameter supports transmission on the carrier indicated by the carrier index, or the QoS flow corresponding to the QoS parameter is allowed to be transmitted 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)".

[0120] 4) An association relationship can also be called a corresponding relationship. A and B have an association relationship, which can be understood as A and B have a corresponding relationship.

[0121] 5) In the embodiments of the present application, when it comes to: two different information, two different parameters or any two different elements, it may refer to a situation where they are not completely the same (ie, partly the same and partly different), or it may refer to a situation where they are completely different.

[0122] like Figure 2 As shown, the specific process of the side communication method provided in the embodiment of the present application is described as follows.

[0123] S201. A terminal device sends first information to a network device, and the network device receives the first information from the terminal device.

[0124] The first information includes a destination address and an association relationship between carrier information and QoS parameters, wherein 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 have a corresponding relationship with which carrier information.

[0125] The destination address in the embodiment of the present application can be represented by a destination address identifier or index, or by a communication type, or 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 opposite 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).

[0126] The carrier information may include a carrier index and may also include a synchronization type supported by the carrier.

[0127] The QoS parameters may include a QoS flow identifier, such as a PFI. The QoS parameters may also include a QoS file, such as any one or more parameters in the QoS file described in the above point 1).

[0128] For example, the first information may include a first destination address, a first carrier index, and a first QoS parameter, wherein the first destination address, the first carrier index, and the first QoS parameter have a corresponding relationship. Specifically, 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.

[0129] As described above, a destination address may be associated with multiple carrier information or multiple QoS parameters. In this case, there may be a situation where one QoS parameter corresponds to multiple carrier indexes, or there may be a situation where one carrier index corresponds to multiple QoS parameters.

[0130] Assuming that the first information also includes the second carrier index, 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 indexes.

[0131] Similarly, assuming that the first information also includes the second QoS parameter, 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.

[0132] In the embodiment 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 as allowing the QoS flow corresponding to the QoS parameter under the corresponding destination address to be transmitted on the carrier indicated by the carrier index. The description here applies to the entire text.

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

[0134] 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.

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

[0136] Optionally, after S203, S204 and S205 are also included.

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

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

[0139] After receiving the first information, the network device can determine that the first destination address, the first QoS parameter and the first carrier index correspond according to the first information. Then, the network device can determine, according to the first information, 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, thereby configuring the first QoS flow corresponding to the first QoS parameter under the first destination address to be mapped to the first SLRB corresponding to the first carrier. The configuration information of the SLRB may include the first QoS parameter, may include the identifier or index (ID / index) of the first SLRB, and may include one or more of the configuration parameters of each protocol layer of the first SLRB, such as the configuration parameters of the PDCP, RLC or LCH of the first SLRB. The first QoS parameter corresponds to the identifier or index of the first SLRB.

[0140] Of course, the first information may include the first destination address, multiple QoS parameters and multiple carrier indexes, as well as the correspondence between the QoS parameters and the carrier indexes. The network device can determine the carrier supported by the QoS flow corresponding to each QoS parameter under the first destination address according to the first information, thereby configuring each QoS flow under the first destination address to be mapped to the SLRB corresponding to the supported carrier.

[0141] The first information is reported to the network device through the terminal device, and the first information includes the correspondence between the carrier index and the QoS parameter. In this way, the configuration of the SLRB determined by the network device is determined according to the carrier supported by the QoS flow, thereby avoiding the terminal mapping the QoS flow to the SLRB corresponding to the unsupported carrier according to the configuration information of the SLRB.

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

[0143] 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 a destination address. Optionally, the configuration information of the SLRB sent by the network device includes a destination address index / identifier and may also include a PFI list. Each destination address identifier / index is associated with a PFI list.

[0144] Optionally, the QoS flow identifier may also be globally unique. Exemplarily, the QoS flow identifier may uniquely represent a set of information inside the terminal device, including a destination address, a carrier information list, and a QoS file. In the case where the QoS flow identifier is globally unique, the same QoS flow ID will not exist under the carrier information lists of different destination addresses. The configuration information of the SLRB sent by the network device may include a carrier information list index or identifier, and may also include a QoS flow ID list. Optionally, each carrier information list index or identifier is associated with a QoS flow ID list. The carrier information list indicated by a carrier information list index or identifier includes one or more carrier information. The carrier information list may also be replaced by one or more carrier indexes.

[0145] In the embodiment of the present application, the carrier information can be represented by a carrier index, or by a synchronization type supported by the carrier, or by a combination of a carrier index and a synchronization type supported by the carrier. Optionally, one or more carrier indexes can be indicated by an index or identifier of a carrier information list. The terminal device can obtain the carrier index from a system information block (SIB) message received by the network device. The SIB message can carry the index of the carrier supported by the cell where the terminal device is located. The identifier of the carrier information list can be an 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 an 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 that it is unique under 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 different carrier information lists can include some of the same carrier indexes.

[0146] Optionally, the correspondence between the carrier index and the QoS parameter can also 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: a first destination address, a first service type identifier, and a first QoS parameter. The first service type identifier corresponds to the first destination address, and the first QoS parameter corresponds to the first destination address. The first QoS parameter corresponds to the first service type identifier.

[0147] The first message may further include a second service type identifier, and the first QoS parameter and the second service type identifier also have a corresponding relationship.

[0148] The first message may further include a second QoS parameter, and the first service type identifier also has a corresponding relationship with the second QoS parameter.

[0149] In short, a service type identifier may correspond to one or more QoS parameters, and a QoS parameter may correspond to one or more service type identifiers.

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

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

[0152] The terminal device can perform SL communication with one or more destination addresses, so the terminal device may request the network device for the configuration information of the SLRB corresponding to the multiple destination addresses. In actual applications, the terminal device can report multiple destination addresses in the first information. For example, the first information includes the second destination address, the carrier index associated with the second destination address, the QoS parameters associated with the second destination address, and the correspondence between the carrier index and the QoS parameters. The reporting method is similar to that of the first destination address.

[0153] The terminal device can determine the correspondence between the QoS parameters and the carrier index in the following manner.

[0154] The access layer (AS) of the terminal device obtains information from the upper layer of the terminal device, which is recorded as the second information. The second information may include information about the carrier supported by the service type, for example, the second information includes the identifier of the service type and the carrier information. It is understandable 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 index is different. The carrier index reported by the terminal device to the network device is used to distinguish different carriers in a cell. The function of the carrier information in the second information is different from this. In short, the terminal device can determine the carriers supported by each service type from the information obtained from the upper layer. The terminal device determines the carrier supported by the service based on the second information. It should be understood that the access layer of the terminal device can also obtain third information from the upper layer of the upper layer device, and the third information includes information about the QoS flow under the corresponding service under the destination address, for example, the third information includes the destination address, service identifier and QoS parameters, and the terminal device can determine the QoS flow corresponding to the QoS parameter under the service corresponding to the service type identifier under the destination address based on the third information. Furthermore, the terminal device can determine the QoS flow of the service corresponding to the service type identifier under the destination address, and on which carriers SL transmission is supported.

[0155] 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 indicates the same QoS flow under the same destination address.

[0156] The access layer of the terminal device obtains the second information or the third information from the upper layer, where the upper layer may refer to a layer above the access layer of the terminal device, such as a V2X layer, an application layer, or a layer between the V2X layer and the application layer. The access layer of the terminal device may include, for example, 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 layer may also include a physical (PHY) layer.

[0157] In an embodiment of the present application, when the terminal device is in an RRC connection state, the first information sent to the network device can be carried in a sidelink terminal message (sidelink UE information, SUI). The SUI message is used to request SLRB configuration. The SUI message includes the content included in the above-mentioned 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 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.

[0158] It should be understood that the reporting method of the first information can be a full information reporting method or a delta information reporting method. Full information reporting means that if the previously reported first information is still valid at the current reporting time, the first information still needs to be re-reported at the current reporting time. The incremental information reporting method means that each time the first information content is reported, only the latest changed first information is included.

[0159] The following examples illustrate possible forms of expression of the content in the first information. In the following examples, the carrier information is represented by a carrier list, each of which may include one or more carrier information, and the carrier information may be a carrier index or a synchronization type supported by the carrier. Any QoS parameter may include a QoS flow identifier and may also include a QoS file.

[0160] Expression form 1:

[0161] As shown in Table 1, the first information includes the first destination address, and the correspondence between the carrier information under the first destination address and the QoS parameters. 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, and 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 can also include an identifier corresponding to the carrier list, and the QoS parameter can also include a QoS identifier corresponding to the QoS file.

[0162] 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 a destination layer 2 identifier (destination L2 ID 1), and the communication type is unicast.

[0163] Table 1

[0164]

[0165] The first information may also include a correspondence between the download wave information of multiple destination addresses and the QoS parameters. Based on Table 1, as shown in Table 2, it is assumed that the first information also includes a correspondence between the download wave information of the second destination address and the third destination address and the QoS parameters. 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.

[0166] Assume that the second destination address is associated with carrier indexes 1, 2, and 3, and is associated with QoS files 1 to 5. 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.

[0167] Assume that the third destination address is associated with carrier indexes 1 to 4 and QoS files 1 to 5. Carrier indexes 1 to 3 correspond to QoS files 1, 3 and 5, and carrier index 1 and carrier index 4 correspond to QoS files 2, 4 and 5.

[0168] Table 2

[0169]

[0170] Tables 1 and 2 are only examples. In actual applications, the corresponding relationship between the carrier index and the QoS parameter can be determined according to actual conditions.

[0171] Expression form 2:

[0172] The correspondence between the destination address download wave information and the QoS parameter can also be expressed in the following manner. For example, the carrier information is expressed 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 indexes.

[0173] As shown in Table 3a and Table 3b, referring to the description of Table 1, the first information includes the first destination address, and the correspondence 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 correspondence between the QoS file and the carrier list is expressed as: the correspondence between the index / identifier of the QoS file and the carrier list.

[0174] Table 3a

[0175]

[0176] Table 3b

[0177]

[0178] Similarly, the first information may also include the correspondence between the carrier information and QoS parameters downloaded at multiple destination addresses. On the basis of Table 3a and Table 3b, as shown in Table 4a and Table 4b, with reference to the description of Table 2, it is assumed that the first information also includes the correspondence between the carrier information and QoS parameters downloaded at the second destination address and the third destination address. It should be understood that the correspondence between the QoS file and the carrier list at this time is expressed as: the correspondence between the index / identifier of the QoS file and the carrier list. And the index / identifier 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, and the carrier list index locally uniquely represents a carrier list under one destination address. Optionally, the carrier list corresponding to the QoS file at this time can also include the identifier / index of the corresponding destination address.

[0179] Table 4a

[0180]

[0181]

[0182] Table 4b

[0183]

[0184] Table 3a, Table 3b, Table 4a and Table 4b are only examples. In actual applications, the corresponding relationship between the carrier index and the QoS parameter can be determined according to actual conditions.

[0185] In this way, through the first information, the terminal device can indicate the carrier information corresponding to each QoS parameter under the destination address to the network device. 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 QoS flow data packet using the carrier frequency it does not support for SL transmission. Thereby improving the accuracy of SLRB configuration and improving the SL communication quality.

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

[0187] S301. A terminal device sends first information to a network device, and the network device receives the first information from the terminal device.

[0188] Among them, the first information includes: a first destination address, a first carrier index and at least one QoS parameter, the first destination address, the first carrier index and the at least one QoS parameter have a corresponding relationship, and the QoS flow corresponding to the at least one QoS parameter under the first destination address supports SL transmission on the carrier indicated by the first carrier index.

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

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

[0191] In actual applications, there may be multiple carrier indexes associated with the first destination address, and the QoS flows corresponding to different QoS parameters support different carriers. The terminal device determines the carriers supported by the QoS flows corresponding to different QoS parameters under the first destination address, and obtains the carrier index of the carrier supported by the QoS flows. The carrier index of the carrier supported by the QoS flow is carried in the first information.

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

[0193] 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.

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

[0195] Optionally, after S303, S304 and S305 are also included.

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

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

[0198] 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 of the above part of "the terminal device can determine the correspondence between the QoS parameter and the carrier index in the following way", and the repeated parts will not be repeated here.

[0199] Let's take an example to illustrate this. Figure 3 The examples further illustrate.

[0200] For convenience, through Figure 4 To indicate 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 indexes 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 indexes 1 to 5; the QoS flow corresponding to QoS parameter 2 supports the carriers indicated by carrier indexes 1, 2, and 4; the QoS flow corresponding to QoS parameter 3 supports the carriers indicated by carrier indexes 1 and 2. The terminal device determines that the carriers supported by the QoS flows corresponding to QoS file 1 are the carriers indicated by carrier indexes 1 and 2. The carriers indicated by the carrier indexes supported by the 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 indexes supported by the QoS flows corresponding to the QoS parameters of multiple associated QoS files 1 is carrier index 1 and carrier index 2.

[0201] The first information reported by the terminal device may include: a first destination address, a carrier index 1, a 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 contents of QoS parameters 1 to 3 only include QoS file 1 and / or the same QoS flow identifier. At this time, the first destination address is associated with carrier indexes 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 indexes 1 and 2.

[0202] It should be understood that the first destination address can 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 flow corresponding to the other QoS parameters are the same as the supported carriers corresponding to QoS parameters 1 to 3, the carrier indexes 1 to 5 associated with the first destination address also correspond to the other QoS parameters.

[0203] In the embodiment of the present application, the carrier index included in the first information may be one or more, which are the indexes of the carriers supported by multiple QoS flows associated with the first destination address. If the first information includes multiple carrier indexes, the multiple carrier indexes can be reflected in the form of a list, or in the form of a collection or combination. The expression form of the content included in the first information can refer to Figure 2 The embodiment shown includes the first and second forms of expression.

[0204] Optionally, if the index of the carriers supported by the QoS flows corresponding to multiple QoS parameters with the same QoS file associated with the destination address is an empty set, the access layer of the terminal device sends an indication message to the upper layer (such as the V2X layer), and the indication message is used to indicate that the QoS flow or service corresponding to the same QoS file associated with this destination address is unreasonable. Optionally, after receiving the indication message, the upper layer of the terminal device triggers the PC5-S link modification process with the opposite terminal device, or modifies the QoS parameter / service information associated with this destination address.

[0205] Optionally, if the index of the carriers supported by the QoS flows of multiple QoS parameters 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 information about the multiple QoS flows, indicating that the QoS flows corresponding to the multiple QoS parameters are not supported for SL transmission of any carrier index under the first destination address. Alternatively, the multiple QoS parameters are associated with an indication information, which is used to indicate that the QoS flows corresponding to the multiple QoS parameters are not supported for SL transmission of any carrier index under the first destination address.

[0206] Optionally, if the number of carrier indexes supported by the QoS flows corresponding to multiple QoS parameters with the same QoS file associated with the first destination address is one, then the first destination address in the first information reported by the terminal device is associated with an indication information, and the indication information 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.

[0207] The terminal device reports the carrier index of the carrier supported by all QoS flows corresponding to the QoS parameters under the destination address to the network device. After receiving the reported first information, the network device will not configure the carrier that is not supported by the QoS flow of the destination address when configuring SLRB for the terminal according to the first information, so as to avoid the data packets of the QoS flow using the carrier frequency that it does not support for SL transmission. This improves the configuration accuracy of SLRB and improves the quality of SL communication.

[0208] Figure 2 and Figure 3 In the illustrated embodiment, when a terminal device reports the correspondence between carrier information and QoS parameters under multiple destination addresses to a network device, the correspondence between carrier information and QoS parameters under different destination addresses may be carried in one information, for example, reported through first information; or may be reported to the network device through different information, for example, the correspondence between carrier information and QoS parameters under the first destination address may be reported through the first information, and the correspondence between carrier information and QoS parameters under the second destination address may be reported through other information.

[0209] Figure 3 For some optional implementations and concepts not described in the embodiments, please refer to Figure 2 The description in the embodiments. The embodiments can refer to each other.

[0210] In combination with the above embodiments, Figure 5 As shown, an embodiment of the present application also provides a side communication method, and the specific process is described as follows.

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

[0212] The configuration information of the SLRB includes one or more QoS parameters. The configuration information of the SLRB can be simply described as SLRB configuration.

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

[0214] The SLRB is associated with one or more QoS parameters corresponding to the destination address.

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

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

[0217] The concept of carrier information can be explained by parameters Figure 2 or Figure 3 Description in the examples.

[0218] Figure 5 The illustrated embodiment may be applicable to an RRC connected state and a non-RRC connected state of a terminal.

[0219] Generally speaking, when the terminal device is in the RRC connection state, the terminal device sends a SUI message to the network device to request 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 can carry the correspondence between the QoS parameters and the carrier index under the destination address in the SUI message.

[0220] When the terminal device is in RRC inactive state or RRC idle state, the terminal device can receive 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 the 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.

[0221] The following Figure 5 The optional implementation of the embodiment is further explained.

[0222] When the terminal device is in a non-RRC connected state or idle state, the terminal device can obtain the configuration information of the SLRB through the SIB or pre-configured. In this case, the network device cannot know the QoS parameters associated with each destination address of the terminal device, and 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 the QoS flows corresponding to the 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 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.

[0223] 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 priority (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 LCH data can be placed on the grant or resource corresponding to this carrier for SL transmission.

[0224] The terminal device will use the grant or resources corresponding to the carrier to transmit the data packets in the LCH / SLRB according to the judgment result, if the judgment result is yes, so as to avoid the data packets in the LCH / SLRB from being transmitted through SL based on the carrier that it does not support.

[0225] It should be understood that the terminal device can determine the carrier information supported by the QoS parameters based on the carrier information supported by the service type corresponding to the QoSflow corresponding to the QoS parameters. Figure 2 Description of the relevant parts of the embodiment.

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

[0227] In one possible implementation, the terminal device will map the same (intersection part) carrier information of the carrier information associated with all QoS flows / services on the LCH / SLRB as the carrier information supported by the current LCH / SLRB. Optionally, the terminal device further determines the carrier information allowed by the LCH / SLRB based on the channel busy ratio (CBR). Exemplarily, when the CBR corresponding to the carrier information is less than or equal to a threshold, it can be determined that the carrier information is the carrier information supported by the LCH / SLRB. The CBR threshold may be network configured or specified by the protocol.

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

[0229] according to Figure 5 In the method of the embodiment, 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.

[0230] Optionally, the terminal device selects an LCH for SL transmission according to a certain rule. The rule may be a network configuration or a protocol specification. Exemplarily, the terminal device selects an LCH according to a rule of logical channel identifier (LCID) from small to large, or the terminal device selects an LCH according to an LCH priority corresponding to the LCH from high to low.

[0231] Optionally, the terminal device sends an indication message to the network device, where the indication message is used to indicate that the current SLRB cannot support PDCP duplication. Exemplarily, the indication message is sent via RRC dedicated signaling or MAC CE. The indication message may include one or more of a destination address, SLRB configuration information (e.g., SLRB index or identifier), supported carrier information, or associated LCH information.

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

[0233] The following Figure 6 and Figure 7 The example shown is for Figure 5 The embodiments are further described in detail.

[0234] The SLRB configuration obtained by the terminal device from the network device is as follows: Figure 6 The carrier information is represented by a carrier list, and a carrier list includes multiple carrier indexes. The QoS parameters are represented by PFI and QoS file.

[0235] like Figure 7 As shown in the figure, the terminal device establishes 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. Figure 6 The SLRB configuration shown in the figure determines that the carrier list associated with the QoS flow corresponding to QoS parameters 1, 2, and 5 includes carrier list 1 and carrier list 2. The carrier indexes (i.e., the intersection) included in both carrier list 1 and carrier list 2 are carrier indexes 1, 2, and 4. Thus, the terminal device determines that the carrier information allowed by SLRB / LCH 1 is carrier indexes 1, 2, and 4. Similarly, the terminal device determines that the carrier information allowed by SLRB / LCH 1 is carrier indexes 1, 2, and 4. Figure 6 The SLRB configuration shown determines the intersection of the carrier indexes associated with the QoS flows corresponding to QoS parameters 3, 4, and 6, thereby determining that the carrier information allowed by SLRB / LCH2 is carrier indexes 1 and 2.

[0236] In summary, Figure 5In the embodiment 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 flow corresponding to the QoS file at a certain destination address supports different carriers and is mapped to the same SLRB / LCH, the terminal device uses the carriers supported by all these QoS flows as the carriers mapped to the SLRB / LCH. Therefore, when sending data packets corresponding to the QoS flow, the carriers not supported by the QoS flow will not be used for SL transmission.

[0237] Based on the above embodiments, Figure 8 As shown, an embodiment of the present application also provides a side communication method, and the specific process is described as follows.

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

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

[0240] The terminal device can obtain the configuration information of the SLRB through an RRC message, a SIB message or a pre-configuration. The state of the terminal device can be an RRC connected state or an RRC non-connected state. The specific details of this step can be parameter Figure 5 The embodiment describes obtaining SLRB configuration information.

[0241] 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 being partially different or completely different.

[0242] Wherein, M and N are integers greater than 1, and M and N may be the same or different.

[0243] For example, Figure 6 As shown in the example, the SLRB configuration information includes QoS parameters 1, 2, and 5, and the carriers supported by QoS parameter 1 and QoS parameter 5 are not exactly the same. The QoS flow corresponding to QoS parameter 1 supports the carriers indicated by carrier indexes 3 and 5, while the QoS flow corresponding to QoS parameter 5 does not support the carriers indicated by carrier indexes 3 and 5.

[0244] Specifically, the terminal device can determine the association between the carrier information under each destination address and the QoS flow corresponding to the QoS parameter by obtaining information from the upper layer, and thereby determine, based on the association, that the carriers supported by the QoS flows corresponding to at least two QoS parameters among the M QoS parameters under the first destination address are different or partially the same.

[0245] S803. The terminal device establishes N SLRBs for the QoS flows corresponding to the N QoS parameters under the first destination address, wherein the QoS flows corresponding to the N QoS parameters corresponding to the first destination address correspond one-to-one to the N SLRBs.

[0246] It should be understood that the QoS flows corresponding to other MN QoS parameters can also be mapped to the corresponding N SLRBs according to the configuration of the acquired SLRB.

[0247] Based on the obtained SLRB configuration, the terminal device determines that the following problems may exist: 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, of which at least one QoS flow is mapped to the SLRB / LCH corresponding to the unsupported carrier. The "unsupported" here can be understood as incomplete support or complete support. To address this problem, the terminal device establishes N SLRB / LCHs for the N QoS flows associated with the destination address, and the N QoS flows correspond to the N SLRB / LCHs one by one.

[0248] Optionally, if multiple QoS flows associated with a destination address support N different carrier lists, the terminal device establishes N SLRBs, where N is an integer greater than 1.

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

[0250] In summary, through Figure 8 In an embodiment, the terminal device establishes multiple SLRB / LCHs for one destination address based on one SLRB configuration, so that all QoS flows mapped to one SLRB / LCH support the same carrier information, so that SL transmission can be performed normally.

[0251] When a terminal device currently performs SL communication, it needs to determine the carrier information that the SL communication can support. The carriers supported by terminal devices in different geographical areas for SL communication may be different. For example, different countries and regions allocate different spectrum ranges for SL communication of terminal devices. Therefore, the terminal device needs to know the carriers that can be supported within the current geographical area, 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, Fig. 9 As shown, the present application also provides a method for SL communication, and the specific process is described as follows.

[0252] S901. The terminal device obtains the correspondence between geographical area information and carrier information.

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

[0254] Exemplarily, the correspondence between the geographical area and the carrier information is obtained through pre-configuration for the terminal device out of coverage (OOC).

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

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

[0257] Optionally, the geographical location may be at a country or region level, for example, different countries or regions correspond to different geographical areas.

[0258] Optionally, the geographical location may be at a local level, such as different provinces, cities, counties, towns, etc. corresponding to different geographical areas.

[0259] Optionally, the geographical location may be at a 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.

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

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

[0262] S902: The terminal device determines current geographical area information.

[0263] There are multiple ways for a terminal device to obtain the current geographical area information. For example, 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 identifier to determine the current geographical area information. The terminal device can obtain the cell identifier by reading a master information block (MIB) or a system information block (SIB) message.

[0264] Optionally, S902 may be executed before S901.

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

[0266] Exemplarily, the terminal device determines the carrier information corresponding to the current geographic area information according to S901 and S902, and can select resources for SL transmission according to the supported carrier information.

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

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

[0269] It should be noted that the above embodiments are based on the same concept, and the methods of the embodiments can refer to each other, for example, the introduction of some concepts and the description of optional implementation methods can refer to each other.

[0270] It should be noted that the examples in various application scenarios in this application only show some possible implementation methods, which are for better understanding and explanation of the method of this application. Those skilled in the art can obtain some examples of evolution forms based on the indication method of the reference signal provided in the application.

[0271] In the embodiments provided by the present application, the methods provided by the embodiments of the present application are introduced from the perspective of network equipment, terminal, and interaction between network equipment and terminal. In order to realize the functions in the methods provided by the embodiments of the present application, the network equipment and the terminal may include hardware structures and / or software modules, and the functions are realized in the form of hardware structures, software modules, or hardware structures plus software modules. Whether a function in the functions is executed in the form of hardware structures, software modules, or hardware structures plus software modules depends on the specific application and design constraints of the technical solution.

[0272] like Fig.10As shown, based on the same technical concept, an embodiment of the present application also provides a device 1000, which can 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 combination with a terminal device or a network device. In one design, the device 1200 may include a module that corresponds one-to-one to the method / operation / step / action performed by the terminal device or the network device in the above method embodiment, and 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 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.

[0273] When used to execute a method executed by an end device:

[0274] In one possible example, the communication module 1002 is used to send first information to a network device, the first 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 is used to receive configuration information of a side link bearer SLRB from the network device.

[0275] In another possible example, the processing module 1001 is used to call the communication module 1002 to send first information to the network device, the first 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, and the QoS flow corresponding to the at least one QoS parameter supports the carrier indicated by the first carrier index; and is used to receive configuration information of the side link bearer SLRB from the network device.

[0276] In another possible example, the processing module 1001 is used to obtain configuration information of a side link bearer SLRB, the configuration information of the side link bearer SLRB including one or more quality of service QoS parameters; and to establish an SLRB for a destination address according to the configuration information of the SLRB, the SLRB being associated with one or more QoS parameters corresponding to the destination address; and 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.

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

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

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

[0280] In one example, the communication module 1002 is used to receive first information from a terminal device, the first information including: a first destination address, a first carrier index and a first quality of service QoS parameter, and the first destination address, the first carrier index and the first QoS parameter have a corresponding relationship; the processing module 1001 is used to determine the configuration information of the side link bearer SLRB according to the first information, and the communication module 1002 is also used to send the configuration information of the SLRB to the terminal device.

[0281] In another example, the communication module 1002 is used to receive first information from a terminal device, the first 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, 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 used to determine the configuration information of the sidelink bearer SLRB according to the first information, and the communication module 1002 is also used to send the configuration information of the SLRB to the terminal device.

[0282] The processing module 1001 and the communication module 1002 may also be used to execute other corresponding steps or operations performed by the terminal device or the network device in the above method embodiment, which will not be described one by one here.

[0283] The division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present application may be integrated into a processor, or may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0284] like Fig.11 The device 1100 provided in the embodiment of the present application is shown, which is used to implement the function of the terminal device or network device in the above method. When the function of the network device is implemented, the device can be a network device, or a device in the network device, or a device that can be used with the network device. When the function of the terminal device is implemented, the device can be a terminal device, or a device in the terminal device, or a device that can be used with the terminal device. Among them, the device can be a chip system. In the embodiment of the present application, the chip system can be composed of a chip, or it can include chips and other discrete devices. The device 1100 includes at least one processor 1120, which is used to implement the function of the terminal device or network device in the method provided in the embodiment of the present application. The device 1100 may also include a communication interface 1110. In the embodiment 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, the communication interface 1110 is used for the device in the device 1100 to communicate with other devices. Exemplarily, when the device 1100 is a network device, the other device may be a terminal device. When the device 1100 is a terminal device, the other device may be a network device. The processor 1120 uses the communication interface 1110 to send and receive data, and is used to implement the method described in the above method embodiment. Exemplarily, when implementing the function of the terminal device, the processor 1120 is used to use the communication interface 1110 to send first information to the network device, the first 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 receive configuration information of the side link bearer SLRB from the network device.

[0285] In another possible example, the processor 1120 is used to send first information to the network device using the communication interface 1110, the first 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, and the QoS flows corresponding to the at least one QoS parameter all support the carrier indicated by the first carrier index; and is used to receive configuration information of the side link bearer SLRB from the network device.

[0286] In another possible example, the processor 1120 is used to obtain configuration information of a sidelink bearer SLRB, the configuration information of the sidelink bearer SLRB including one or more quality of service QoS parameters; and to establish an SLRB for a destination address according to the configuration information of the SLRB, the SLRB being associated with one or more QoS parameters corresponding to the destination address; and 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.

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

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

[0289] When implementing the function of the terminal device, the processor 1120 is used to receive first information from the terminal device using the communication interface, the first information including: a first destination address, a first carrier index and a first quality of service QoS parameter, and the first destination address, the first carrier index and the first QoS parameter have a corresponding relationship; the processor 1120 is used to determine the configuration information of the sidelink bearer SLRB according to the first information, and the processor 1120 is also used to send the configuration information of the SLRB to the terminal device using the communication interface 1110.

[0290] Alternatively, when implementing the function of the terminal device, the processor 1120 is used to use the communication interface 1110 to receive first information from the terminal device, the first 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, and the QoS flow corresponding to the at least one QoS parameter supports the carrier indicated by the first carrier index; the processor 1120 is used to determine the configuration information of the sidelink bearer SLRB according to the first information, and the processor 1120 is also used to send the configuration information of the SLRB to the terminal device using the communication interface 1110.

[0291] The processor 1120 and the communication interface 1110 may also be used to execute other corresponding steps or operations performed by the terminal device or network device in the above method embodiment, which will not be described one by one here.

[0292] The device 1100 may also include at least one memory 1130 for storing program instructions and / or data. The memory 1130 is coupled to the processor 1120. The coupling in the embodiment 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 exchange between devices, units or modules. The processor 1120 may operate in conjunction with the memory 1130. The processor 1120 may execute program instructions stored in the memory 1130. At least one of the at least one memory may be included in the processor.

[0293] The specific connection medium between the communication interface 1110, the processor 1120 and the memory 1130 is not limited in the embodiment of the present application. Fig.11 The memory 1130, the processor 1120 and the communication interface 1110 are connected via a bus 1140. Fig.11 The connections between the other components are shown in bold lines, which are only for illustration and are not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.11 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0294] When the apparatus 1000 and the apparatus 1100 are specifically chips or chip systems, the communication module 1002 and the communication interface 1110 may output or receive a baseband signal. When the apparatus 1000 and the apparatus 1100 are specifically devices, the communication module 1202 and the communication interface 1110 may output or receive a radio frequency signal. In an embodiment 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 device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

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

[0296] Part or all of the operations and functions performed by the terminal described in the above method embodiments of the present application, or part or all of the operations and functions performed by the network device, can be completed using a chip or an integrated circuit.

[0297] In order to achieve the above Fig.10 or Fig.11 The functions of the communication device described above, the embodiment of the present application also provides a chip, including a processor, for supporting the communication device to implement the functions involved in the terminal or network device in the above method embodiment. In one 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 device.

[0298] An embodiment of the present application provides a computer-readable storage medium storing a computer program, wherein the computer program includes instructions for executing the above method embodiment.

[0299] An embodiment of the present application provides a computer program product including instructions, which, when executed on a computer, enables the computer to execute the above method embodiment.

[0300] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in 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.

[0301] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0302] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0303] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0304] Although the preferred embodiments of the present application have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present application.

[0305] 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 equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A side communication method, characterized in that: include: Sending first information to a network device, the first information comprising: a first destination address, a first carrier index list, a first quality of service QoS parameter, a second carrier index list and a second QoS parameter, wherein the first carrier index list and the first QoS parameter have a corresponding relationship, and the second carrier index list and the second QoS parameter have a corresponding relationship; Receive configuration information of a side link bearer SLRB from the network device, where the configuration information of the SLRB is determined by the network device based on the first information.

2. The method according to claim 1, characterized in that The first QoS parameter includes a first QoS flow identifier and / or a first QoS file, and the second QoS parameter includes a second QoS flow identifier and / or a second QoS file.

3. The method according to claim 1 or 2, characterized in that The SLRB configuration information includes at least one of the following: information of a destination address, one or more QoS parameters corresponding to the destination address, or carrier information.

4. The method according to claim 3, characterized in that The method further comprises: According to the SLRB configuration information, an SLRB is established for the destination address, wherein the SLRB is associated with one or more QoS parameters corresponding to the destination address.

5. The method according to claim 4, characterized in that The method further comprises: Determine carrier information corresponding to the carrier supported by the SLRB, where the carrier information is carrier information supported by all QoS flows indicated by one or more QoS parameters corresponding to the destination address.

6. A side communication method, characterized in that: include: Receive first information from a terminal device, the first information including: a first destination address, a first carrier index list, a first quality of service QoS parameter, a second carrier index list and a second QoS parameter, wherein the first carrier index list and the first QoS parameter have a corresponding relationship, and the second carrier index list and the second QoS parameter have a corresponding relationship; Based on the first information, determine and send the configuration information of the sidelink bearer SLRB to the terminal device.

7. The method according to claim 6, characterized in that The first QoS parameter includes a first QoS flow identifier and / or a first QoS file, and the second QoS parameter includes a second QoS flow identifier and / or a second QoS file.

8. The method according to claim 6 or 7, characterized in that The SLRB configuration information includes at least one of the following: information of a destination address, one or more QoS parameters corresponding to the destination address, or carrier information.

9. A communication device, characterized in that: It comprises a processor and a communication interface, wherein the communication interface is used to communicate with other communication devices; the processor is used to run a set of programs so that the communication device implements the method described in any one of claims 1 to 5.

10. A communication device, characterized in that: It comprises a processor and a communication interface, wherein the communication interface is used to communicate with other communication devices; the processor is used to run a set of programs so that the communication device implements the method described in any one of claims 6 to 8.

11. A computer-readable storage medium, characterized in that: The computer storage medium stores computer-readable instructions, and when the computer-readable instructions are executed on the communication device, the communication device executes the method according to any one of claims 1 to 8.

12. A chip, characterized in that: The chip is connected to the memory or the chip includes the memory, and is used to read and execute the software program stored in the memory to implement the method according to any one of claims 1 to 5.

13. A chip, characterized in that: The chip is connected to the memory or the chip includes the memory, and is used to read and execute the software program stored in the memory to implement the method according to any one of claims 6 to 8.

Images