Sidelink communication method, apparatus, and communication device

Abstract

The present disclosure provides a sidelink communication method, a communication apparatus, and a communication device, the method including: determining that a first destination address is compatible with carrier aggregation if all transmission attributes associated with the first destination address correspond to being compatible with carrier aggregation; and determining that the first destination address is incompatible with carrier aggregation if at least one transmission attribute associated with the first destination address corresponds to being incompatible with carrier aggregation, the first destination address being a destination address of a first service, and the first service being a broadcast service or a multicast service.

Description

Technical Field

[0001] The present disclosure relates to the technical field of wireless communication, and more specifically, to a sidelink communication method, apparatus, and communication device.

Background Art

[0002] With the development of wireless communication technology, in order to support direct communication between terminal devices, a sidelink (SL) communication mode has been introduced, and terminal devices communicate with each other via the PC5 interface. The sidelink network supports various transmission modes such as unicast, multicast, and broadcast.

[0003] In V2X (Vehicle to Everything) based on the LTE (Long Term Evolution) communication network, sidelink carrier aggregation (CA) technology has already been supported. Since the transmission and reception capabilities of terminal devices are limited, there is a possibility that the sidelink service can only be received on one or more carriers. Since LTE V2X only supports broadcast services, an enhanced scheme for carrier selection / reselection to address the limitations of the reception capabilities of terminal devices has not been introduced.

[0004] Then, in the scenario of new radio (NR) sidelink carrier aggregation, previous version terminal devices (for example, terminal devices in the communication protocol of version Rel-16 or Rel-17) may not be able to receive broadcast services or multicast services transmitted by terminal devices that support carrier aggregation (for example, terminal devices in the communication protocol of version Rel-18), that is, there is a problem of backward incompatibility of sidelink terminal devices.

Summary of the Invention

Problems to be Solved by the Invention

[0005] This disclosure provides a sidelink communication method, apparatus, and communication device that enable backward compatibility of sidelink terminal devices and further improve the performance of terminal devices. [Means for solving the problem]

[0006] According to a first aspect of the present disclosure, a sidelink communication method is provided which can be applied to the transmitting device side in a sidelink communication system. The method includes the steps of determining that a first destination address is compatible with carrier aggregation if all transmission attributes associated with the first destination address correspond to carrier aggregation compatibility, or determining that a first destination address is not compatible with carrier aggregation if at least one transmission attribute associated with the first destination address corresponds to carrier aggregation incompatibility, wherein the first destination address is the destination address of a first service, and the first service is a broadcast service or a multicast service.

[0007] In some possible embodiments, the transmit attribute is used to indicate whether a broadcast service or multicast service is compatible with carrier aggregation.

[0008] In some possible embodiments, the transmission attributes are configured according to the granularity of the service type or according to the granularity of the destination address.

[0009] In some possible embodiments, in response to the sending attributes being set according to the granularity of the service type, one sending attribute is associated with one service type, and at least one service type is associated with one destination address.

[0010] In some possible embodiments, all transmission attributes associated with a first destination address include transmission attributes associated with all service types associated with the first destination address.

[0011] In some possible embodiments, one send attribute is associated with one destination address, in response to the send attribute being set at the granularity of the destination address.

[0012] In some possible embodiments, one or more send attributes are associated with a single destination address, and one or more send attributes include send attributes indicating compatibility with carrier aggregation and / or send attributes indicating incompatibility with carrier aggregation.

[0013] In some possible embodiments, the method further includes the steps of determining that any of the first destination addresses is compatible with carrier aggregation, and transmitting data for one or more first services simultaneously over multiple carriers.

[0014] In some possible embodiments, the method further includes the steps of determining that all first destination addresses are incompatible with carrier aggregation, and transmitting data for one or more first services over a single carrier.

[0015] In some possible embodiments, the method further includes the steps of determining that all first destination addresses are compatible with carrier aggregation, and transmitting data for one or more first services simultaneously over multiple carriers.

[0016] In some possible embodiments, the method further includes the steps of determining that any of the first destination addresses is incompatible with carrier aggregation, and transmitting data for one or more first services over a single carrier.

[0017] A second aspect of the present disclosure provides a sidelink communication method which can be applied to the receiving device side in a sidelink communication system. The method includes the steps of determining that a second destination address is carrier aggregation compatible if all transmission attributes associated with the second destination address correspond to carrier aggregation compatible, or determining that a second destination address is not carrier aggregation compatible if at least one transmission attribute associated with the second destination address corresponds to carrier aggregation incompatible, the second destination address being the destination address of a second service of interest, the second service being a broadcast service or a multicast service.

[0018] In some possible embodiments, the transmit attribute is used to indicate whether a broadcast service or multicast service is compatible with carrier aggregation.

[0019] In some possible embodiments, the transmission attributes are configured according to the granularity of the service type or according to the granularity of the destination address.

[0020] In some possible embodiments, in response to the sending attributes being set according to the granularity of the service type, one sending attribute is associated with one service type, and at least one service type is associated with one destination address.

[0021] In some possible embodiments, all transmission attributes associated with a second destination address include transmission attributes associated with all service types associated with the second destination address.

[0022] In some possible embodiments, one send attribute is associated with one destination address, in response to the send attribute being set at the granularity of the destination address.

[0023] In some possible embodiments, one or more transmission attributes are associated with one destination address, and the one or more transmission attributes include a transmission attribute indicating compatibility with carrier aggregation and / or a transmission attribute indicating incompatibility with carrier aggregation.

[0024] In some possible embodiments, the method further includes determining that any second destination address is compatible with carrier aggregation, and receiving data of one or more second services simultaneously on a plurality of carriers.

[0025] In some possible embodiments, the method further includes determining that all second destination addresses are incompatible with carrier aggregation, and receiving data of one or more second services on a single carrier.

[0026] In some possible embodiments, the method further includes determining that all the second destination addresses are compatible with carrier aggregation, and receiving data of one or more second services simultaneously on a plurality of carriers.

[0027] In some possible embodiments, the method further includes determining that any second destination address is incompatible with carrier aggregation, and receiving data of one or more second services on a single carrier.

[0028] According to a third aspect of the present disclosure, a communication device is provided, which may be a transmitting device in a sidelink communication system, or a chip or system-on-chip within the transmitting device, or a functional module within the transmitting device for implementing the methods of the above embodiments. The communication device can implement the functions executed by the transmitting device in the above embodiments, and these functions can be realized by executing corresponding software via hardware. These hardware or software include one or more modules corresponding to the above functions. The communication device is configured to determine that a first destination address is compatible with carrier aggregation if all transmission attributes associated with the first destination address are compatible with carrier aggregation, or to determine that the first destination address is incompatible with carrier aggregation if at least one transmission attribute associated with the first destination address is incompatible with carrier aggregation. The first destination address is the destination address of a first service, and the first service is a broadcast service or a multicast service.

[0029] In some possible embodiments, the transmission attribute is used to indicate whether a broadcast service or a multicast service is compatible with carrier aggregation.

[0030] In some possible embodiments, the transmission attribute is set according to the granularity of the service type or according to the granularity of the destination address.

[0031] In some possible embodiments, in response to the transmission attribute being set according to the granularity of the service type, one transmission attribute is associated with one service type, and at least one service type is associated with one destination address.

[0032] In some possible embodiments, all transmission attributes associated with a first destination address include transmission attributes associated with all service types associated with the first destination address.

[0033] In some possible embodiments, one send attribute is associated with one destination address, in response to the send attribute being set at the granularity of the destination address.

[0034] In some possible embodiments, one or more send attributes are associated with a single destination address, and one or more send attributes include send attributes indicating compatibility with carrier aggregation and / or send attributes indicating incompatibility with carrier aggregation.

[0035] In some possible embodiments, the apparatus further comprises a transmit module, the processing module is configured to determine that any of the first destination addresses is compatible with carrier aggregation, and the transmit module is configured to transmit data for one or more first services simultaneously over multiple carriers.

[0036] In some possible embodiments, the apparatus further comprises a transmit module, the processing module is configured to determine that all first destination addresses are incompatible with carrier aggregation, and the transmit module is configured to transmit data for one or more first services over a single carrier.

[0037] In some possible embodiments, the apparatus further comprises a transmit module, the processing module is configured to determine that all first destination addresses are compatible with carrier aggregation, and the transmit module is configured to transmit data for one or more first services simultaneously over multiple carriers.

[0038] In some possible embodiments, the apparatus further comprises a transmit module, the processing module is configured to determine that any of the aforementioned first destination addresses is incompatible with carrier aggregation, and the transmit module is configured to transmit data for one or more first services over a single carrier.

[0039] According to a fourth aspect of the present disclosure, a communication device is provided, which may be a receiving device in a sidelink communication system, or a chip or system-on-a-chip within a receiving device, or a functional module within a receiving device for carrying out the methods of each of the embodiments described above. The communication device can implement functions performed by the receiving device in each of the embodiments described above, which can be implemented by running corresponding software via hardware. This hardware or software includes one or more modules corresponding to the above functions. The communication device includes a processing module configured to determine that a second destination address is compatible with carrier aggregation if all transmission attributes associated with the second destination address correspond to carrier aggregation compatibility, or to determine that a second destination address is not compatible with carrier aggregation if at least one transmission attribute associated with the second destination address corresponds to carrier aggregation incompatibility, wherein the second destination address is the destination address of a second service of interest, and the second service is a broadcast service or a multicast service.

[0040] In some possible embodiments, the transmit attribute is used to indicate whether a broadcast service or multicast service is compatible with carrier aggregation.

[0041] In some possible embodiments, the transmission attributes are configured according to the granularity of the service type or according to the granularity of the destination address.

[0042] In some possible embodiments, in response to the sending attributes being set according to the granularity of the service type, one sending attribute is associated with one service type, and at least one service type is associated with one destination address.

[0043] In some possible embodiments, all transmission attributes associated with a second destination address include transmission attributes associated with all service types associated with the second destination address.

[0044] In some possible embodiments, one send attribute is associated with one destination address, in response to the send attribute being set at the granularity of the destination address.

[0045] In some possible embodiments, one or more send attributes are associated with a single destination address, and one or more send attributes include send attributes indicating compatibility with carrier aggregation and / or send attributes indicating incompatibility with carrier aggregation.

[0046] In some possible embodiments, the apparatus further comprises a receiving module, the processing module is configured to determine that any of the second destination addresses is compatible with carrier aggregation, and the receiving module is configured to receive data for one or more second services simultaneously on multiple carriers.

[0047] In some possible embodiments, the apparatus further comprises a receiving module, the processing module is configured to determine that all second destination addresses are incompatible with carrier aggregation, and the receiving module is configured to receive data for one or more second services on a single carrier.

[0048] In some possible embodiments, the apparatus further comprises a receiving module, the processing module is configured to determine that all of the aforementioned second destination addresses are compatible with carrier aggregation, and the receiving module is configured to receive data for one or more second services simultaneously on multiple carriers.

[0049] In some possible embodiments, the apparatus further comprises a receiving module, the processing module is configured to determine that any of the second destination addresses is incompatible with carrier aggregation, and the receiving module is configured to receive data for one or more second services on a single carrier.

[0050] According to a fifth aspect of the present disclosure, a communication device such as a transmitting device is provided, comprising an antenna, memory, and a processor, the processor being connected to the antenna and the memory, respectively, and configured to control the transmission and reception of the antenna by executing computer-executable instructions stored in the memory, thereby enabling the method described in any one of the first aspect of the present disclosure and any possible embodiments thereof.

[0051] According to a sixth aspect of the present disclosure, a communication device such as a receiving device is provided, comprising an antenna, memory, and a processor, the processor being connected to the antenna and the memory, respectively, and configured to control the transmission and reception of the antenna by executing computer-executable instructions stored in the memory, thereby enabling the method described in any one of the second aspect of the present disclosure and its possible embodiments.

[0052] According to a seventh aspect of the present disclosure, a computer storage medium is provided which stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the method described in any one of the first to second aspects of the present disclosure and any possible embodiments thereof can be realized.

[0053] According to the eighth aspect of the present disclosure, a computer program or computer program product is provided, and when the computer program product is executed on a computer, the computer implements the method described in any one of the first to second aspects of the present disclosure and any possible embodiments thereof.

[0054] In this disclosure, a sidelink terminal device determines, based on the instructions in its associated transmit attribute (Tx profile), whether the destination address of a first service is compatible with carrier aggregation; that is, whether the associated receiving device supports carrier aggregation. In this way, in sidelink carrier aggregation scenarios, it is ensured that an earlier version of the terminal device (e.g., a terminal device in the Rel-16 or Rel-17 version of the communication protocol) can receive a broadcast or multicast service transmitted by a newer version of the terminal device (e.g., a terminal device that supports carrier aggregation in the Rel-18 version of the communication protocol), thereby achieving backward compatibility for the sidelink terminal device and improving the performance of the terminal device.

[0055] It should be noted that aspects 3 through 7 of this disclosure are consistent with the technical solutions of aspects 1 through 2 of this disclosure, and the beneficial effects achieved by the various aspects and corresponding feasible embodiments are similar, and therefore will not be repeated herein. [Brief explanation of the drawing]

[0056] [Figure 1] This is a schematic diagram of the communication system architecture in an embodiment of the present disclosure. [Figure 2] This is a schematic diagram of another architecture of the communication system in the embodiment of the present disclosure. [Figure 3] This is a schematic diagram of the implementation process of the sidelink communication method in the embodiment of the present disclosure. [Figure 4]This is a schematic diagram of the implementation process of the sidelink communication method in the embodiment of the present disclosure. [Figure 5] This is a schematic diagram of the implementation process of the sidelink communication method in the embodiment of the present disclosure. [Figure 6] This is a schematic diagram of the implementation process of the sidelink communication method in the embodiment of the present disclosure. [Figure 7] This is a schematic diagram of the implementation process of the sidelink communication method in the embodiment of the present disclosure. [Figure 8] This is a schematic diagram of the implementation process of the sidelink communication method in the embodiment of the present disclosure. [Figure 9] This is a schematic diagram of the structure of the measurement reporting device in an embodiment of the present disclosure. [Figure 10] This is a schematic diagram of the structure of a communication device in an embodiment of the present disclosure. [Figure 11] This is a schematic diagram of the structure of a terminal device in an embodiment of the present disclosure. [Figure 12] This is a schematic diagram of the structure of a network device in an embodiment of the present disclosure. [Modes for carrying out the invention]

[0057] This specification provides a detailed description of exemplary embodiments, which are illustrated in the accompanying drawings. Where the following description refers to drawings, unless otherwise indicated, the same numbers in different drawings refer to the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the embodiments of this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this disclosure.

[0058] The terms used in the embodiments of this disclosure are used solely for the purpose of describing specific embodiments and are not intended to limit the embodiments of this disclosure. The singular forms “one” and “the said” used in the embodiments of this disclosure are intended to include the plural forms unless the context clearly indicates otherwise. The terms “and / or” used herein should also be understood to refer to and include any or all possible combinations of one or more related enumerated items.

[0059] In the embodiments of this disclosure, terms such as “first,” “second,” and “third” may be used to describe different types of information, but it should be understood that such information should not be limited to these terms. These terms are used solely to distinguish information of the same kind from one another. For example, without departing from the scope of the embodiments of this disclosure, “first information” may also be referred to as “second information,” and similarly, “second information” may also be referred to as “first information.” Depending on the context, the word “if” as used herein may be interpreted as “when,” “in the case of,” or “in response to a decision.”

[0060] Furthermore, in the description of the embodiments of this disclosure, “and / or” simply indicates a relationship between the relevant objects, and that three relationships may exist. For example, “A and / or B” can represent three cases: A exists alone, A and B exist simultaneously, or B exists alone. Also, in the description of the embodiments of this disclosure, “multiple” can refer to two or more.

[0061] The technical solutions provided by the embodiments of this disclosure can be applied to wireless communication between communication devices. Wireless communication between communication devices includes wireless communication between network devices and terminal devices, wireless communication between network devices, and wireless communication between terminal devices. In the embodiments of this disclosure, the term “wireless communication” may be abbreviated as “communication,” and the term “communication” may also be described as “data transmission,” “information transmission,” or “transmission.”

[0062] The embodiments of this disclosure enumerate several embodiments in order to clearly illustrate the technical solutions of the embodiments of this disclosure. Those skilled in the art will understand that the embodiments provided by the embodiments of this disclosure may be performed alone, in combination with methods of other embodiments in the embodiments of this disclosure, or alone or in combination and then in combination with some methods of other related technologies, and the embodiments of this disclosure are not limited thereto.

[0063] With the advancement of wireless communication technology, the sidelink (SL) communication mode was introduced to support direct communication between terminal devices, and communication between terminal devices is performed via the PC5 interface. Sidelink networks support various transmission modes such as unicast, multicast, and broadcast.

[0064] In one embodiment, sidelink communication has two transmission resource allocation modes: one is a mode of dynamic scheduling by the network (i.e., mode 1), and the other is a mode in which the terminal device autonomously selects from a resource pool broadcast by the network (i.e., mode 2). In mode 1, the network dynamically allocates SL transmission resources to the terminal device according to the terminal device's buffer data report. In mode 2, the terminal device randomly selects SL transmission resources itself from a resource pool broadcast by the network or a pre-configured resource pool. Here, "pre-configured" may be obtained by the terminal device from network elements of the core network or may be pre-configured within the terminal device.

[0065] In actual applications, the specific resource allocation mode used by the terminal device may be configured by the network side via higher-layer signaling (e.g., radio resource control (RRC) signaling). The transmitting device transmits sidelink control information (SCI) over the physical sidelink control channel (PSCCH) and also transmits SCI over the physical sidelink shared channel (PSSCH), where the SCI carries the resource location of the transmitted data, source and destination identifiers, etc. For data packets where hybrid automatic repeat request (HARQ) is enabled (i.e., HARQ-enable), the receiving device performs HARQ feedback of the PSSCH over the physical sidelink feedback channel (PSFCH).

[0066] In another embodiment, one of the simplest ways to meet the requirements for improving the peak rate and system capacity for a single user is to increase the system transmission bandwidth. Therefore, LTE-Advanced systems introduce a technique to increase transmission bandwidth, namely carrier aggregation (CA) technology. Here, CA technology can aggregate multiple component carriers (CCs) together, thereby effectively improving the transmission speeds of both uplinks and downlinks.

[0067] Sidelink communication systems based on LTE (Long Term Evolution) communication networks already support sidelink carrier aggregation (CA) technology. Because terminal devices have limited transmit and receive capabilities, they may only be able to receive sidelink services from one or more carriers. Since LTE-based sidelink communication systems only support broadcast services, enhanced carrier selection / re-selection schemes to address the limitations of terminal device receivability have not been implemented.

[0068] Consequently, in the New Radio (NR) sidelink carrier aggregation scenario, older versions of terminal devices (e.g., terminal devices in 3GPP® Release-16 or Release-17 communication protocols) may not be able to receive broadcast or multicast services transmitted by terminal devices that support carrier aggregation (e.g., terminal devices in version Rel-18 communication protocols), meaning there is a backward incompatibility issue with sidelink terminal devices.

[0069] To solve the above technical problems, embodiments of the present disclosure provide a side-link communication method that can be applied to a communication system, which may be a side-link communication system suitable for fields such as V2X (vehicle to everything), intelligent connected vehicles, and autonomous vehicles. The communication system may include at least one communication device. In one scenario, Figure 1 is a schematic diagram of the architecture of a communication system in an embodiment of the present disclosure. Referring to Figure 1, the communication system 10 may include a network device 11 and terminal devices 12. In another scenario, Figure 2 is a schematic diagram of another architecture of a communication system in an embodiment of the present disclosure. Referring to Figure 2, the communication system 10 may include a plurality of terminal devices 12. Of course, the types, number, and connectivity relationships between network elements included in the communication system in embodiments of the present disclosure are not limited to these.

[0070] In the embodiments of this disclosure, a terminal device can communicate with a network device and simultaneously with other terminal devices. The network device can assist terminal devices in communicating directly with each other by performing resource allocation, scheduling, and coordination for sidelinks of communication between terminal devices. A terminal device can also perform resource allocation, scheduling, and coordination for sidelinks of communication between other terminal devices independently, and is not particularly limited in the embodiments of this disclosure.

[0071] In some possible embodiments, the network device described above may be an access network-side device used to support terminal devices accessing the wireless communication system. For example, it may be a next-generation base station (next generation NodeB, gNB), a transmission reception point (TRP), a relay node, an access point (AP), or a road site unit (RSU) in a 5G access technology communication system.

[0072] The above-mentioned terminal devices may also be devices that provide voice or data connectivity to a user. For example, they may also be called user equipment (UE), mobile station, subscriber unit, station, or terminal equipment (TE). Communication devices may also be cellular phones, personal digital assistants (PDAs), wireless modems, handheld vehicle-to-perdestrian devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablets, relay nodes, APs, etc. With the development of wireless communication technology, any device that can access a wireless communication system, communicate with the network side of a wireless communication system, or communicate with other devices via a wireless communication system may be a terminal device in the embodiments of this disclosure. For example, terminal devices in intelligent transport, automobiles or RSUs, household appliances in smart homes, electric meter readers, voltage monitors, environmental monitors in smart grids, video surveillance devices in intelligent security networks, cash registers, etc. The communication device may be static and fixed, or it may be mobile.

[0073] Furthermore, in a side-link transmission scenario, the above-mentioned communication devices (which may include terminal devices and / or network devices) can be classified into transmitting devices and receiving devices based on the data transmission direction. Here, transmitting devices (also called transmitting-side devices) may include transmitting-side network devices, transmitting-side terminal devices, transmitting-side user devices, etc., and receiving devices (also called receiving-side devices) may include receiving-side network devices, receiving-side terminal devices, receiving-side user devices, etc.

[0074] The above-mentioned transmitting device (also called a transmitting network device, transmitting terminal device, transmitting user device, etc.) and receiving device (also called a receiving network device, receiving terminal device, receiving user device, etc.) are defined in relation to a particular sidelink connection. For example, in the case of sidelink connection A, a single communication device (or network device, terminal device, user device, etc.) is a transmitting device (or transmitting network device, transmitting terminal device, transmitting user device, etc.), but in the case of sidelink connection B, that communication device (or network device, terminal device, user device, etc.) is a receiving device (or receiving network device, receiving terminal device, receiving user device, etc.).

[0075] The sidelink communication method provided in the embodiments of this disclosure will be described below in conjunction with the communication system described above.

[0076] First, note that in the embodiments of this disclosure, relevant transmission attributes (Tx profile) are set (also referred to as "defined") for a broadcast service or multicast service (hereinafter abbreviated as "broadcast / multicast service"). Here, "transmission attributes" are also referred to as "transmission configuration," "transmission configuration file," or "transmission file."

[0077] In one embodiment, a Tx profile is introduced to ensure compatibility of broadcast or multicast transmissions between terminal devices that are compatible or incompatible with carrier aggregation functionality. The Tx profile is used to indicate whether a broadcast / multicast service is compatible with carrier aggregation; that is, it can be understood that the Tx profile is used to indicate whether a broadcast service or a multicast service is compatible with carrier aggregation. Exemplaryly, the Tx profile may indicate the version of the communication standard (e.g., Rel-18) or whether carrier aggregation is enabled (e.g., carrier aggregation compatible (ca-compatible), carrier aggregation incompatible (ca-incompatible)).

[0078] It should be noted that the above statement, "whether a broadcast / multicast service is compatible with carrier aggregation," can be understood as whether, for a particular broadcast / multicast service, data for a destination address associated with that service can be transmitted using sidelink resources on multiple carriers simultaneously. Here, the destination address may be identified by the destination ID.

[0079] In some possible embodiments, the Tx profile may be configured according to the granularity of the service type or the granularity of the destination address.

[0080] In one embodiment, if the Tx profiles are configured according to the granularity of the service types, one Tx profile is associated with one service type, meaning that Tx profiles correspond one-to-one with service types, and different service types are associated with different Tx profiles. Furthermore, at least one service type is associated with one destination address, meaning that one destination address may be associated with multiple different service types, and thus one destination address may be associated with one or more Tx profiles. Exemplaryly, if the destination ID corresponding to a first destination address is A, and the service types associated with the first destination address are type A, type B, and type C, with type A corresponding to Tx profile 1, type B corresponding to Tx profile 2, and type C corresponding to Tx profile 3, then the Tx profiles associated with the first destination address are Tx profile 1, Tx profile 2, and Tx profile 3.

[0081] In another embodiment, if the Tx profile is configured according to the granularity of the destination address, then one Tx profile is associated with one destination address, meaning there is only one Tx profile associated with one destination address, and the higher layer must ensure that all service types associated with one destination address have the same Tx profile. For example, the destination ID corresponding to the first destination address is A, and the Tx profile associated with the first destination address is Tx profile 1.

[0082] As can be seen above, in embodiments of the present disclosure, one or more Tx profiles are associated with a single destination address, where one or more Tx profiles include a Tx profile indicating compatibility with carrier aggregation and / or a Tx profile indicating incompatibility with carrier aggregation. In other words, one or more Tx profiles may be associated with a single destination address, including a Tx profile corresponding to compatibility with carrier aggregation and a Tx profile corresponding to incompatibility with carrier aggregation. Of course, other situations may exist regarding the association between Tx profiles and destination addresses, and this is not limited by embodiments of the present disclosure.

[0083] In some possible embodiments, the Tx profile associated with the destination address is provided to the access layer (AS) by a higher layer (e.g., a V2X layer) and identifies one or more sidelink feature groups.

[0084] In one embodiment, the upper layer may instruct the AS to provide a Tx profile in the form of a Tx profile list. Of course, the upper layer may also instruct the AS to provide a Tx profile in other forms, such as a linked list or an index, but this is not limited to the embodiments of this disclosure.

[0085] For example, if the Tx profile is configured according to the granularity of the service type, the upper layer can instruct the AS to configure the Tx profile in the form of a Tx profile list, which may include Tx profiles associated with different service types, or service types associated with different destination addresses and the Tx profiles associated with those service types.

[0086] For example, if a Tx profile is configured according to the granularity of destination addresses, the upper layer can instruct the AS to provide a Tx profile in the form of a Tx profile list, which may contain Tx profiles associated with different destination addresses.

[0087] In some possible embodiments, the above Tx profile settings may be understood to be pre-configured by the sidelink system (or specified by the communication protocol). Each network element within the sidelink system operates according to the above Tx profile settings.

[0088] The following describes the sidelink communication method provided in the embodiments of this disclosure. In some possible embodiments, embodiments of the present disclosure provide a sidelink communication method that can be applied to the transmitting device side in a sidelink communication system. Figure 3 is a schematic diagram of the implementation process of the sidelink communication method in embodiments of the present disclosure, and referring to Figure 3, if the Tx profile is set based on the granularity of the service type, the above method may include the following steps:

[0089] In S301, the transmitting device determines the first destination address for the first service.

[0090] Here, the first service may be a broadcast / multicast service.

[0091] In a transmitting device, it can be understood that the upper layer triggers a first service, determines a first destination address associated with the first service and instructs the AS, and the AS determines the Tx profile associated with the first destination address through one or more Tx profiles associated with the destination address of the first service instructed by the upper layer. The one or more Tx profiles correspond to multiple service types.

[0092] In the embodiments of this disclosure, the Tx profiles are configured according to the granularity of the service type, so one or more Tx profiles associated with a first destination address can be understood as Tx profiles corresponding to one or more service types associated with the first destination address. Different Tx profiles may indicate whether services of different service types are compatible with carrier aggregation.

[0093] After S301, the transmitting device may perform S302 or S303.

[0094] In S302, the transmitting device determines that the first destination address is carrier aggregation compatible if all Tx profiles associated with the first destination address correspond to carrier aggregation compatibility.

[0095] It can be understood that the AS, based on instructions from higher layers, determines the Tx profile associated with the first destination address, and then determines whether each Tx profile corresponds to carrier aggregation compatibility or incompatibility. The AS determines that the Tx profiles associated with all task types related to the first destination address correspond to carrier aggregation compatibility (which can also be understood as indicating that all Tx profiles associated with the first destination address are carrier aggregation compatible), and in this case, the AS determines that the first destination address is carrier aggregation compatible. At this point, the transmitting device assumes (or hypothesizes) that the first destination address is carrier aggregation compatible. In S303, if at least one Tx profile associated with the first destination address corresponds to incompatibility with carrier aggregation, the transmitting device determines that the first destination address is incompatibility with carrier aggregation.

[0096] The AS determines that the Tx profile associated with at least one service type related to the first destination address corresponds to incompatibility with carrier aggregation (or can be understood as indicating that at least one Tx profile associated with the first destination address is incompatibility with carrier aggregation), and in this case, the AS determines that the first destination address is incompatibility with carrier aggregation. At this point, the transmitting device assumes (or hypothesizes) that the first destination address is incompatibility with carrier aggregation.

[0097] It should be noted that the above statement, "At least one Tx profile associated with the first destination address corresponds to being incompatible with carrier aggregation," can also be interpreted as meaning that any of the Tx profiles associated with the first destination address (i.e., any Tx profile associated with the first destination address) corresponds to being incompatible with carrier aggregation, or that any of the Tx profiles associated with the first destination address is incompatible with carrier aggregation.

[0098] For example, suppose the first destination address is destination A, the service types associated with the first destination address are type A, type B, and type C, the Tx profile corresponding to type A is Tx profile 1, the Tx profile corresponding to type B is Tx profile 2, and the Tx profile corresponding to type C is Tx profile 3. Then the Tx profiles associated with destination A are Tx profile 1, Tx profile 2, and Tx profile 3. If Tx profile 1 indicates that type A broadcast / multicast services are compatible with carrier aggregation, Tx profile 2 indicates that type B broadcast / multicast services are compatible with carrier aggregation, and Tx profile 3 indicates that type C broadcast / multicast services are compatible with carrier aggregation, then the AS can determine that all Tx profiles associated with destination A correspond to carrier aggregation compatibility. In this case, the AS determines that destination A is carrier aggregation compatible. Conversely, if at least one of Tx profile 1, Tx profile 2, and Tx profile 3 indicates that the broadcast / multicast service is incompatible with carrier aggregation, the AS will determine that at least one Tx profile associated with destination A is incompatible with carrier aggregation. In this case, the AS will determine that destination A is incompatible with carrier aggregation.

[0099] In some possible embodiments, the transmitting device can trigger one or more broadcast / multicast services, i.e., one or more first services. The transmitting device can then perform S301 to S303 above for each of the one or more first services to determine whether one or more first destination addresses are compatible with carrier aggregation. After determining whether one or more first destination addresses are compatible with carrier aggregation, the transmitting device may choose to enable or disable carrier aggregation so that the data for one or more first services is transmitted over multiple carriers or a single carrier.

[0100] In one embodiment, Figure 4 is a schematic diagram of the implementation process of the sidelink communication method in an embodiment of the present disclosure. Referring to Figure 4, after S302 or S303, the transmitting device may execute S401 to S402 (shown by solid lines) or S403 to S404 (shown by dashed lines).

[0101] In S401, the transmitting device determines that all primary destination addresses are compatible with carrier aggregation.

[0102] In S402, the transmitting device simultaneously transmits data for one or more first services over multiple carriers.

[0103] In S401 to S402, the AS determines that all of the one or more first destination addresses are compatible with carrier aggregation, and in this case, the AS understands to enable carrier aggregation and to transmit data for one or more first services simultaneously on multiple carriers.

[0104] In S403, the transmitting device determines that one of the first destination addresses is incompatible with carrier aggregation.

[0105] Please note that the aforementioned statement, "any of the first destination addresses is incompatible with carrier aggregation," can be understood as meaning that at least one of the one or more first destination addresses is incompatible with carrier aggregation.

[0106] In S404, the transmitting device transmits data for one or more first services on a single carrier.

[0107] Here, the single carrier may be a default carrier, such as a sidelink carrier in the Rel-16 or Rel-17 version of the communication protocol.

[0108] In S403 to S404, the AS determines that one or more of the first destination addresses is incompatible with carrier aggregation, and in this case, the AS understands that it will disable carrier aggregation and transmit the data for one or more first services on a single carrier.

[0109] For example, the destination addresses for multiple first services may be destination A, destination B, and destination C. For each destination address, the transmitting device performs S301 to S304 above to determine whether destination A, destination B, and destination C are compatible with carrier aggregation. If destination A, destination B, and destination C are determined to be compatible with carrier aggregation, the AS enables carrier aggregation and transmits the data for multiple first services simultaneously on multiple carriers. Alternatively, if any of destination A, destination B, and destination C are determined to be incompatible with carrier aggregation, the AS disables carrier aggregation and transmits the data for multiple first services on a single carrier.

[0110] In another embodiment, Figure 5 shows a schematic diagram of the implementation process of the sidelink communication method in an embodiment of the present disclosure. Referring to Figure 5, after S302 or S303, the transmitting device may execute S501 to S502 (shown by solid lines) or S503 to S504 (shown by dashed lines).

[0111] In S501, the transmitting device determines that one of the first destination addresses is compatible with carrier aggregation.

[0112] It should be noted that the aforementioned statement, "any of the first destination addresses is compatible with carrier aggregation," can be understood as meaning that at least one of the one or more first destination addresses is compatible with carrier aggregation.

[0113] In S502, the transmitting device transmits data for one or more first services simultaneously over multiple carriers.

[0114] In S501 to S502, it is understood that the AS determines that one or more of the first destination addresses are compatible with carrier aggregation, and in this case the AS enables carrier aggregation and transmits data for one or more first services simultaneously on multiple carriers.

[0115] In S503, the transmitting device determines that all primary destination addresses are incompatible with carrier aggregation.

[0116] In S504, the transmitting device transmits data for one or more first services over a single carrier.

[0117] In S503 to S504, the AS determines that all of one or more first destination addresses are incompatible with carrier aggregation, and in this case, the AS understands that it will disable carrier aggregation and transmit the data for one or more first services on a single carrier.

[0118] For example, the destination addresses for multiple first services may be destination A, destination B, and destination C. For each destination address, the transmitting device performs S301 to S304 described above to determine whether each of destination A, destination B, and destination C is compatible with carrier aggregation. If it is determined that any of the destination addresses for destination A, destination B, and destination C is compatible with carrier aggregation, the AS enables carrier aggregation and transmits the data for multiple first services simultaneously over multiple carriers. Alternatively, if it is determined that destination A is incompatible with carrier aggregation, destination B is incompatible with carrier aggregation, and destination C is incompatible with carrier aggregation, the AS disables carrier aggregation and transmits the data for multiple first services on a single carrier.

[0119] In some possible embodiments, Figure 6 is a schematic diagram of the implementation process of the sidelink communication method in an embodiment of the present disclosure. Referring to Figure 6, if the Tx profile is configured according to the granularity of the destination address, the above method may include the following steps:

[0120] In S601, the transmitting device determines the first destination address for the first service.

[0121] Here, the first service may be a broadcast / multicast service.

[0122] In the transmitting device, the upper layer understands that it triggers a first service, determines the first destination address associated with the first service, and instructs the AS. The AS determines the Tx profile associated with the first destination address via the Tx profile associated with the destination address of the first service instructed by the upper layer. One first destination address is associated with one Tx profile.

[0123] Subsequently, after S601, the transmitting device may execute S602 or S603.

[0124] In S603, the transmitting device determines that the first destination address is carrier aggregation compatible if the Tx profile associated with the first destination address (i.e., one Tx profile) corresponds to carrier aggregation compatibility.

[0125] It can be understood that, based on instructions from higher layers, the AS can determine one Tx profile associated with a first destination address, and then determine whether that Tx profile corresponds to carrier aggregation compatibility or not. The AS determines that the Tx profile associated with the first destination address corresponds to carrier aggregation compatibility (which can also be understood as indicating that the Tx profile associated with the first destination address is carrier aggregation compatible), and in this case, the AS determines that the first destination address is carrier aggregation compatible. In this case, the transmitting device (e.g., the AS) assumes (or hypothesizes) that the first destination address is carrier aggregation compatible. Please note that the above statement, "corresponds to the Tx profile associated with the first destination address being compatible with carrier aggregation," can be understood as either "corresponding to the single Tx profile associated with the first destination address being compatible with carrier aggregation," or "corresponding to all Tx profiles associated with the first destination address being compatible with carrier aggregation."

[0126] In S603, if the Tx profile associated with the first destination address (i.e., one Tx profile) is incompatible with carrier aggregation, the transmitting device determines that the first destination address is incompatible with carrier aggregation.

[0127] The AS determines that the Tx profile associated with the first destination address is incompatible with carrier aggregation (which can also be understood as indicating that the Tx profile associated with the first destination address is incompatible with carrier aggregation), and in this case, the AS determines that the first destination address is incompatible with carrier aggregation. In this case, the transmitting device (e.g., the AS) assumes that the first destination address is incompatible with carrier aggregation (this can also be described as an assumption or hypothesis).

[0128] Please note that the above statement, "The Tx profile associated with the first destination address corresponds to the fact that carrier aggregation is incompatible," can be understood as either the sole Tx profile associated with the first destination address being incompatible with carrier aggregation, or indicating that one Tx profile associated with the first destination address is incompatible with carrier aggregation.

[0129] For example, suppose the first destination address is destination A, and the Tx profile associated with the first destination address is Tx profile 1. If Tx profile 1 indicates that the broadcast / multicast service is compatible with carrier aggregation, the AS can determine that all Tx profiles associated with destination A correspond to carrier aggregation compatibility, and in this case, the AS determines that destination A is compatible with carrier aggregation. Conversely, if Tx profile 1 indicates that the broadcast / multicast service is not compatible with carrier aggregation, the AS can determine that one Tx profile associated with destination A corresponds to carrier aggregation incompatibility, and in this case, the AS determines that destination A is not compatible with carrier aggregation.

[0130] In some possible embodiments, the transmitting device can trigger one or more broadcast / multicast services, i.e., one or more first services. The transmitting device then performs S601 to S603 above individually for each of the one or more first services, thereby determining whether one or more first destination addresses are compatible with carrier aggregation. Next, after S602 or S603, the transmitting device may, but is not limited to, perform S401 to S404 or S501 to S504 above, which are not described in detail here.

[0131] Up to this point, the sidelink communication process on the transmitting device side has been completed.

[0132] In some possible embodiments, embodiments of the present disclosure further provide a sidelink communication method that may be applied to the receiving device side in a sidelink communication system. Figure 7 is a schematic diagram of the implementation process of the sidelink communication method in embodiments of the present disclosure. Referring to Figure 7, if the Tx profile is set according to the granularity of the service type, the above method may include the following steps:

[0133] In S701, the receiving device determines the second destination address for the second service. Here, the second service could be a broadcast / multicast service of interest to the receiving device.

[0134] It is understood that in a receiving device, the upper layer determines a second service of interest and instructs the AS to provide a second destination address for that second service, and the AS then determines one or more Tx profiles associated with the second destination address through one or more Tx profiles associated with the destination address of the second service instructed by the upper layer. These one or more Tx profiles correspond to multiple service types.

[0135] Subsequently, after S701, the transmitting device can perform S702 or S703.

[0136] In S702, the receiving device determines that the second destination address is carrier aggregation compatible if all Tx profiles associated with the second destination address correspond to carrier aggregation compatibility.

[0137] In S703, if at least one Tx profile associated with the second destination address corresponds to a carrier aggregation incompatibility, it is determined that the second destination address is carrier aggregation incompatibility.

[0138] Please note that the execution process described above in S701 to S703 can be found in the detailed explanation of S301 to S303 in Figure 3. For the sake of brevity in this specification, a detailed explanation is not provided here.

[0139] In some possible embodiments, the receiving device may also be interested in one or more broadcast / multicast services, i.e., there may be one or more second services. The receiving device can then perform S701 to S703 above for each of the one or more second services, thereby determining whether one or more second destination addresses are compatible with carrier aggregation. After determining whether one or more second destination addresses are compatible with carrier aggregation, the receiving device can choose to enable or disable carrier aggregation to receive data for one or more second services on multiple carriers or a single carrier.

[0140] In one embodiment, Figure 8 is a schematic diagram of the implementation process of the sidelink communication method according to an embodiment of the present disclosure. Referring to Figure 8, after S302 or S303, the transmitting device may execute S801 to S802 (shown by solid lines) or S803 to S804 (shown by dashed lines).

[0141] In S801, the receiving device determines that all secondary destination addresses are compatible with carrier aggregation.

[0142] In S802, the receiving device simultaneously receives data from one or more second services on multiple carriers.

[0143] In S803, the receiving device determines that one of the second destination addresses is incompatible with carrier aggregation.

[0144] Please note that the aforementioned statement, "any of the second destination addresses is incompatible with carrier aggregation," can be understood as meaning that at least one of the one or more second destination addresses is incompatible with carrier aggregation.

[0145] In S804, the receiving device receives data from one or more second services on a single carrier.

[0146] Here, the single carrier may be a default carrier, such as a sidelink carrier in the Rel-16 or Rel-17 version of the communication protocol.

[0147] In another embodiment, after S302 or S303, the transmitting device may execute S805 to S806 (shown by a solid line) or S807 to S808 (shown by a dashed line).

[0148] In S805, the receiving device determines that one of the second destination addresses is compatible with carrier aggregation.

[0149] In the S806, the receiving device simultaneously receives data from one or more second services on multiple carriers.

[0150] In S807, the receiving device determines that all secondary destination addresses are incompatible with carrier aggregation.

[0151] In S808, the receiving device decides to receive data from one or more second services on a single carrier.

[0152] Please note that the execution processes of S801 to S808 described above can be further explained by referring to the detailed descriptions of S401 to S404 in Figure 4 and S501 to S504 in Figure 5. For the sake of brevity in this specification, a detailed explanation is not provided here.

[0153] Up to this point, the sidelink communication process on the receiving device side has been completed.

[0154] In embodiments of this disclosure, a sidelink terminal device determines, based on the instructions in the associated Tx profile, whether the destination address of a first service is compatible with carrier aggregation; that is, whether the associated receiving device supports carrier aggregation. In this way, in sidelink carrier aggregation scenarios, it is ensured that an earlier version of a terminal device (e.g., a terminal device in a Rel-16 or Rel-17 version of the communication protocol) can receive a broadcast or multicast service transmitted by a newer version of a terminal device (e.g., a terminal device that supports carrier aggregation in a Rel-18 version of the communication protocol), thereby achieving backward compatibility for the sidelink terminal device and improving the performance of the terminal device.

[0155] Based on the same inventive concept, embodiments of the present disclosure provide a side-link communication device. Figure 9 is a schematic diagram of the structure of the communication device in an embodiment of the present disclosure. Referring to Figure 9, the communication device 900 may include a processing module 901 and a transmission module 902.

[0156] In some possible embodiments, the communication device 900 may be a transmitting device in a sidelink communication system, or a chip or system-on-a-chip within a transmitting device, or a functional module within a transmitting device for carrying out the methods of each embodiment described above. The communication device can implement the functions performed by the transmitting device in each embodiment described above, and these functions can be implemented by executing corresponding software via hardware. This hardware or software includes one or more modules corresponding to the above functions. In this case, referring to the solid lines in Figure 9, the transmission module 902 can be understood as the transmission module 902a.

[0157] Similarly, the processing module 901 is configured to determine that a first destination address is compatible with carrier aggregation if all transmission attributes (Tx profiles) associated with the first destination address correspond to carrier aggregation compatibility, or to determine that a first destination address is not compatible with carrier aggregation if at least one Tx profile associated with the first destination address corresponds to carrier aggregation incompatibility, and the first destination address is the destination address of a first service, the first service being a broadcast service or a multicast service.

[0158] In some possible embodiments, the transmit attribute is used to indicate whether a broadcast service or multicast service is compatible with carrier aggregation or not.

[0159] In some possible embodiments, the transmission attribute is set at the granularity of the service type or the granularity of the destination address.

[0160] In some possible embodiments, in response to setting send attributes at the service type granularity, one send attribute is associated with one service type, and at least one service type is associated with one destination address.

[0161] In some possible embodiments, all transmission attributes associated with a first destination address include transmission attributes associated with all service types associated with the first destination address.

[0162] In some possible embodiments, one send attribute is associated with one destination address, in response to the send attribute being set at the granularity of the destination address.

[0163] In some possible embodiments, one or more send attributes are associated with a single destination address, and one or more send attributes include send attributes indicating compatibility with carrier aggregation and / or send attributes indicating incompatibility with carrier aggregation.

[0164] In some possible embodiments, the processing module 901 is further configured to determine that any of the first destination addresses is compatible with carrier aggregation, and the transmitting module 902a is configured to transmit data for one or more first services simultaneously over multiple carriers.

[0165] In some possible embodiments, the processing module 901 is further configured to determine that all first destination addresses are incompatible with carrier aggregation, and the transmitting module 902a is configured to transmit data for one or more first services over a single carrier.

[0166] In some possible embodiments, the processing module 901 is further configured to determine that all first destination addresses are compatible with carrier aggregation, and the transmitting module 902a is configured to transmit data for one or more first services simultaneously over multiple carriers.

[0167] In some possible embodiments, the processing module 901 is further configured to determine that any of the first destination addresses is incompatible with carrier aggregation, and the transmitting module 902a is configured to transmit data for one or more first services over a single carrier.

[0168] In some possible embodiments, the communication device may be a receiving device in a sidelink communication system, or a chip or system-on-a-chip within a receiving device, or a functional module within a receiving device for implementing the methods of each embodiment described above. The communication device can implement the functions performed by the receiving device in each embodiment described above, and these functions can be implemented by the hardware executing corresponding software. This hardware or software includes one or more modules corresponding to the above functions. In this case, referring to the dashed line in Figure 9, the transmission module 902 can be understood as the receiving module 902b.

[0169] Accordingly, the processing module 901 is configured to determine that a second destination address is compatible with carrier aggregation if all transmission attributes associated with the second destination address correspond to carrier aggregation compatibility, or to determine that a second destination address is not compatible with carrier aggregation if at least one transmission attribute associated with the second destination address corresponds to carrier aggregation incompatibility, where the second destination address is the destination address of a second service of interest, and the second service is either a broadcast service or a multicast service.

[0170] In some possible embodiments, the transmit attribute is used to indicate whether a broadcast service or multicast service is compatible with carrier aggregation or not.

[0171] In some possible embodiments, the transmission attributes are configured according to the granularity of the service type or according to the granularity of the destination address.

[0172] In some possible embodiments, in response to the sending attributes being set according to the granularity of the service type, one sending attribute is associated with one service type, and at least one service type is associated with one destination address.

[0173] In some possible embodiments, all transmission attributes associated with a second destination address include transmission attributes associated with all service types associated with the second destination address.

[0174] In some possible embodiments, one send attribute is associated with one destination address, in response to the send attributes being set according to the granularity of the destination address.

[0175] In some possible embodiments, one or more send attributes are associated with a single destination address, and one or more send attributes include send attributes indicating compatibility with carrier aggregation and / or send attributes indicating incompatibility with carrier aggregation.

[0176] In some possible embodiments, the processing module 901 is further configured to determine that any of the second destination addresses is compatible with carrier aggregation, and the receiving module 902b is configured to receive data for one or more second services simultaneously on multiple carriers.

[0177] In some possible embodiments, the processing module 901 is further configured to determine that all second destination addresses are incompatible with carrier aggregation, and the receiving module 902b is configured to receive data for one or more second services on a single carrier.

[0178] In some possible embodiments, the processing module 901 is further configured to determine that all second destination addresses are compatible with carrier aggregation, and the receiving module 902b is configured to receive data for one or more second services simultaneously on multiple carriers.

[0179] In some possible embodiments, the processing module 901 is further configured to determine that any of the second destination addresses is incompatible with carrier aggregation, and the receiving module 902b is configured to receive data for one or more second services on a single carrier.

[0180] Please note that the specific implementation processes of the processing module 901 and the transmission module 902 can be found by referring to the detailed descriptions of the transmitting and receiving devices in the embodiments shown in Figures 2 to 8. For the sake of brevity, the details will not be repeated here.

[0181] The receiving module 902b referred to in the embodiments of this disclosure may be a receiving interface, a receiving circuit, or a receiver, the transmitting module 902a may be a transmitting interface, a transmitting circuit, or a transmitter, and the processing module 901 may be one or more processors.

[0182] Based on the same inventive concept, embodiments of the present disclosure provide a communication device. This communication device may be a transmitting device and / or a receiving device as described in one or more embodiments above. Figure 10 is a schematic diagram of the structure of a communication device in an embodiment of the present disclosure. Referring to Figure 10, the communication device 100 employs general-purpose computer hardware including a processor 101, memory 102, bus 103, input device 104, and output device 105.

[0183] In some possible embodiments, memory 102 may include computer storage media in the form of volatile and / or non-volatile memory, such as read-only memory and / or random-access memory. Memory 102 can store the operating system, application programs, other program modules, executable code, program data, user data, and the like.

[0184] Input device 104 can be used to input commands and information to a communication device. Input device 104 (such as a keyboard or pointing device) may be a mouse, trackball, touchpad, microphone, joystick, gamepad, satellite TV antenna, scanner, or similar device. These input devices can be connected to processor 101 via bus 103.

[0185] Output device 105 can be used by the communication device to output information. In addition to the monitor, output device 105 may also be other peripheral output devices such as a speaker and / or a printing device. These output devices can also be connected to the processor 101 via bus 103.

[0186] The communication device can connect to a network such as a local area network (LAN) via antenna 106. In a network environment, computer execution instructions stored in the control device are not limited to local storage but can be stored in remote storage devices.

[0187] When the processor 101 in the communication device executes executable code or application program stored in memory 102, the communication device executes the mobility management configuration method on the terminal device side or network device side as described in the above embodiment. The specific execution process has been described in the above embodiment and will not be repeated here.

[0188] Furthermore, the memory 102 stores computer execution instructions for realizing the functions of the processing module 901 and transmission module 902 shown in Figure 9. The functions / implementation processes of the processing module 901 and transmission module 902 shown in Figure 9 can be realized by the processor 101 shown in Figure 10 calling the computer execution instructions stored in the memory 102. For specific implementation processes and functions, please refer to the related embodiments described above.

[0189] Based on the same inventive concept, embodiments of the present disclosure provide a terminal device which corresponds to a terminal device such as a transmitting terminal device, transmitting user device, receiving terminal device, or receiving user device in one or more embodiments described above. Optionally, the terminal device may be a mobile phone, computer, digital broadcasting terminal device, messaging device, game console, tablet, medical device, exercise equipment, personal digital assistant, etc.

[0190] Figure 11 is a schematic diagram of the structure of a terminal device in an embodiment of the present disclosure. Referring to Figure 11, the terminal device 110 may include one or more components from among a processing component 111, memory 112, power supply component 113, multimedia component 114, audio component 115, input / output (I / O) interface 116, sensor component 117, and communication component 118.

[0191] The processing component 111 typically controls the overall operation of the terminal device 110, including operations related to the display, telephone calls, data communication, camera operation, and recording operation. The processing component 111 may include one or more processors 1111 that execute instructions to perform all or some of the steps of the method described above. Furthermore, the processing component 111 may include one or more modules that facilitate interaction between the processing component 111 and other components. For example, the processing component 111 may include a multimedia module that facilitates interaction between the multimedia component 114 and the processing component 111.

[0192] Memory 112 is configured to store various types of data to support operation on terminal device 110. Examples of such data include instructions for any application or method executed on terminal device 110, contact data, phonebook data, messages, images, and videos. Memory 112 may be implemented using any type of volatile or non-volatile storage device, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disks, or optical disks, or a combination thereof.

[0193] The power supply component 113 supplies power to various components of the terminal device 110. The power supply component 113 includes a power management system, one or more power supplies, and other components related to the generation, management, and distribution of power for the terminal device 110.

[0194] The multimedia component 114 includes a screen that provides an output interface between the terminal device 110 and the user. In some embodiments, the screen includes a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen is implemented as a touchscreen that receives input signals from the user. The touch panel includes one or more touch sensors that sense touches, swipes, and gestures on the touch panel. The touch sensors sense not only the boundaries of a touch or swipe action, but also the time interval and pressure associated with the touch or swipe action. In some embodiments, the multimedia component 114 includes a front camera and / or a rear camera. When the terminal device 110 is in an operating mode such as shooting mode or video mode, the front camera and / or the rear camera can receive external multimedia data. The front camera and the rear camera may each be a fixed optical lens system or may have focus and optical zoom capabilities.

[0195] The audio component 115 is configured to output and / or input audio signals. For example, the audio component 115 includes a microphone (MIC) and is configured to receive external audio signals when the terminal device 110 is in an operating mode such as call mode, recording mode, and speech recognition mode. The received audio signals may be further stored in memory 112 or transmitted via communication component 118. In some embodiments, the audio component 115 further includes a speaker that outputs audio signals.

[0196] The I / O interface 116 provides an interface between the processing component 111 and peripheral interface modules such as a keyboard, click wheel, and buttons. Buttons include, but are not limited to, a home button, volume buttons, a start button, and a lock button.

[0197] The sensor component 117 includes one or more sensors to provide state evaluation of various aspects of the terminal device 110. For example, the sensor component 117 can detect the open / closed state of the terminal device 110, the relative position of components (e.g., the display and keypad of the terminal device 110), changes in the position of the terminal device 110 or one of its components, whether or not a user is touching the terminal device 110, the orientation or acceleration / deceleration of the terminal device 110, and changes in the temperature of the terminal device 110. The sensor component 117 may include proximity sensors configured to detect the presence of nearby objects without physical contact. The sensor component 117 may also include optical sensors, such as CMOS or CCD image sensors, for use in imaging applications. In some embodiments, the sensor component 117 may also include accelerometers, gyroscopes, magnetic sensors, pressure sensors, or temperature sensors.

[0198] The communication component 118 is configured to facilitate wired or wireless communication between the terminal device 110 and other devices. The terminal device 110 can access wireless networks using communication standards such as WiFi, 2G, 3G, 4G, 5G, or a combination thereof. In one exemplary embodiment, the communication component 118 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 118 further includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented using radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth® (BT) technology™, and other technologies.

[0199] In exemplary embodiments, the terminal device 110 may be implemented using one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above method.

[0200] Based on the same inventive concept, embodiments of the present disclosure provide a network device which corresponds to network devices such as the transmitting network device and the receiving network device in one or more embodiments described above.

[0201] Figure 12 is a schematic diagram of the structure of a network device in an embodiment of the present disclosure. Referring to Figure 12, the network device 120 includes a processing component 121, which may further include one or more processors and a memory resource represented by memory 122 that stores instructions (such as application programs) that can be executed by the processing component 121. The application programs stored in memory 122 may each include one or more modules corresponding to an instruction set. Furthermore, the processing component 121 is configured to execute instructions for performing any of the above methods applied to the network device as described above.

[0202] The network device 120 may further include one power component 123 configured to perform power management for the network device 120, one wired or wireless network interface 124 configured to connect the network device 120 to a network, and one input / output (I / O) interface 125. The network device 120 may operate based on an operating system stored in memory 122, such as Windows Server™, Mac OS X™, Unix™, Linux™, or FreeBSD™.

[0203] Based on the same inventive concept, the terminal device includes an antenna, a memory, and a processor connected to the antenna and the memory, respectively, and configured to control the transmission and reception of the antenna by executing computer executable instructions stored in the memory, thereby realizing the methods on the transmitting device side in one or more of the above embodiments.

[0204] Based on the same inventive concept, the network device includes an antenna, memory, and a processor connected to the antenna and memory, respectively, and configured to control the transmission and reception of the antenna by executing computer executable instructions stored in the memory, thereby realizing the receiving device-side method in one or more of the above embodiments.

[0205] Based on the same inventive concept, embodiments of the present disclosure also provide a computer-readable storage medium on which instructions are stored. When the instructions are executed on a computer, the transmitting device-side or receiving device-side method of one or more embodiments described above is performed.

[0206] Based on the same inventive concept, embodiments of the present disclosure also provide computer programs or computer program products. When a computer program product is executed on a computer, the computer can implement the transmitting device-side or receiving device-side methods of one or more embodiments.

[0207] Other embodiments of this disclosure will be apparent to those skilled in the art by considering this specification and practicing what is disclosed herein. This disclosure is intended to cover all variations, uses, or adaptive changes of this disclosure, which include common or customary technical means in the art that are not disclosed herein, in accordance with the general principles of this disclosure.

[0208] This disclosure is not limited to the exact configuration described above and shown in the attached drawings, and it should be understood that various modifications and changes may be made without departing from its scope.

Claims

1. A sidelink communication method applicable to a transmitting device, A step of determining whether a first service is compatible with carrier aggregation based on its transmission attributes, wherein whether a first service is compatible with carrier aggregation means that the first service supports transmitting data for destination addresses associated with the first service using sidelink resources on multiple carriers simultaneously, and the first service is a broadcast service or a multicast service. If the first service is compatible with carrier aggregation, the steps include simultaneously transmitting the data of the first service over multiple carriers, If the first service is not compatible with carrier aggregation, the step includes transmitting the data of the first service over a single carrier. A method characterized by the following:

2. The step of determining whether a first service is compatible with carrier aggregation based on its transmission attributes is: If all sending attributes associated with a first destination address correspond to carrier aggregation compatibility, the first destination address is determined to be carrier aggregation compatible. If at least one sending attribute associated with the first destination address corresponds to incompatibility with carrier aggregation, the step includes determining that the first destination address is incompatibility with carrier aggregation. The aforementioned first destination address is the destination address of the first service. The method according to feature 1.

3. The aforementioned transmission attribute is used to indicate whether a broadcast service or multicast service is compatible with carrier aggregation. The method according to feature 1.

4. The aforementioned transmission attributes are set according to the granularity of the service type, or according to the granularity of the destination address. The method according to feature 1.

5. In response to the setting of the transmission attributes according to the granularity of the service type, one transmission attribute is associated with one service type, and at least one service type is associated with one destination address. The method according to feature 4.

6. All transmission attributes associated with the first destination address include transmission attributes associated with all service types related to the first destination address. The method according to feature 5.

7. In response to the setting of the transmission attributes at the destination address granularity, one transmission attribute is associated with one destination address. The method according to feature 4.

8. One or more send attributes are associated with a single destination address, and the one or more send attributes include send attributes indicating compatibility with carrier aggregation and / or send attributes indicating incompatibility with carrier aggregation. The method according to feature 1.

9. If the first service is compatible with carrier aggregation, the step of simultaneously transmitting data of the first service over multiple carriers is: A step of determining that any of the aforementioned first destination addresses is compatible with carrier aggregation, The step includes simultaneously transmitting data from one or more first services across multiple carriers. The method according to feature 1.

10. If the first service is not compatible with carrier aggregation, the step of transmitting the data of the first service over a single carrier is: The step of determining that all of the aforementioned first destination addresses are incompatible with carrier aggregation, The step includes transmitting data from one or more first services over a single carrier. The method according to feature 9.

11. If the first service is compatible with carrier aggregation, the step of simultaneously transmitting data of the first service over multiple carriers is: A step of determining that all of the aforementioned first destination addresses are compatible with carrier aggregation, The step includes simultaneously transmitting data from one or more first services across multiple carriers. The method according to feature 1.

12. If the first service is not compatible with carrier aggregation, the step of transmitting the data of the first service over a single carrier is: A step of determining that any of the aforementioned first destination addresses is incompatible with carrier aggregation, The step includes transmitting data from one or more first services over a single carrier. The method according to feature 11.

13. A sidelink communication method applicable to a receiving device, If the transmitting device determines that the second service is compatible with carrier aggregation, the steps include receiving the data of the second service simultaneously on multiple carriers, If the transmitting device determines that the second service is incompatible with carrier aggregation, the process includes the step of receiving the data for the second service on a single carrier. Whether the second service is compatible with carrier aggregation is determined by the transmitting device according to its transmission attributes, and whether a second service is compatible with carrier aggregation indicates whether the second service supports the transmission of data for destination addresses associated with the second service using sidelink resources on multiple carriers simultaneously, and the second service is either a broadcast service or a multicast service. A method characterized by the following:

14. If all sending attributes associated with the second destination address correspond to carrier aggregation compatibility, the step of determining that the second destination address is carrier aggregation compatible, If at least one sending attribute associated with the second destination address corresponds to incompatibility with carrier aggregation, the method further includes the step of determining that the second destination address is incompatibility with carrier aggregation. The second destination address is the destination address of the second service of interest to the receiving device. The method according to specification 13.

15. The aforementioned transmission attribute is used to indicate whether a broadcast service or multicast service is compatible with carrier aggregation. The method according to specification 13.

16. The aforementioned transmission attributes are set according to the granularity of the service type, or according to the granularity of the destination address. The method according to specification 13.

17. In response to the setting of the transmission attributes according to the granularity of the service type, one transmission attribute is associated with one service type, and at least one service type is associated with one destination address. The method according to feature 16.

18. All sending attributes associated with the second destination address include sending attributes associated with all service types associated with the second destination address. The method according to the present invention, characterized by the features of the present invention.

19. In response to the setting of the transmission attributes at the destination address granularity, one transmission attribute is associated with one destination address. The method according to feature 16.

20. One or more send attributes are associated with a single destination address, and the one or more send attributes include send attributes indicating compatibility with carrier aggregation and / or send attributes indicating incompatibility with carrier aggregation. The method according to specification 13.

21. The steps include determining that any of the aforementioned second destination addresses is compatible with carrier aggregation, The further step includes simultaneously receiving data from one or more second services on multiple carriers. The method according to specification 13.

22. The step of determining that all of the aforementioned second destination addresses are incompatible with carrier aggregation, The further step includes receiving data from one or more second services on a single carrier. The method according to feature 21.

23. The step of determining that all of the aforementioned second destination addresses are compatible with carrier aggregation, The further step includes simultaneously receiving data from one or more second services on multiple carriers. The method according to specification 13.

24. A step of determining that any of the aforementioned second destination addresses is incompatible with carrier aggregation, The further step includes receiving data from one or more second services on a single carrier. The method according to feature 23.

25. A communication device applicable to a transmitting device, A processing module configured to determine whether a first service is compatible with carrier aggregation based on its transmission attributes, wherein whether a first service is compatible with carrier aggregation means whether the first service supports transmitting data for destination addresses associated with the first service using sidelink resources on multiple carriers simultaneously, and the first service is a broadcast service or a multicast service. The system includes a transmission module configured to transmit data of the first service simultaneously over multiple carriers if the first service is compatible with carrier aggregation, and to transmit data of the first service over a single carrier if the first service is not compatible with carrier aggregation. A communication device characterized by the following features.

26. A sidelink receiver that is applied to a receiving device, The receiving module is configured to receive data of the second service on multiple carriers simultaneously if the transmitting device determines that the second service is compatible with carrier aggregation, and to receive data of the second service on a single carrier if the transmitting device determines that the second service is not compatible with carrier aggregation. The device is characterized in that the transmission device determines whether the second service is compatible with carrier aggregation depending on the transmission attributes, and whether a second service is compatible with carrier aggregation indicates whether the second service supports transmitting data for destination addresses associated with the second service using sidelink resources on multiple carriers simultaneously, and the second service is a broadcast service or a multicast service.

27. Including an antenna, memory, and processor, The processor is connected to the antenna and the memory, respectively, and is configured to control the transmission and reception of the antenna by executing computer-executable instructions stored in the memory, thereby enabling the implementation of the method according to any one of claims 1 to 24. A communication device characterized by the following features.

28. When executed on a computer, it stores instructions used to perform the method according to any one of claims 1 to 24. A computer storage medium characterized by the following features.

Images