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 particularly to a sidelink communication method, apparatus, and communication device. [Background technology]

[0002] With the development of wireless communication technology, the sidelink (SL) communication mode has been introduced to support direct communication between terminal devices, 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] Vehicle-to-Everything (V2X) based on LTE (Long Term Evolution) communication networks already supports sidelink carrier aggregation (CA) technology. However, due to the limited transmitting and receiving capabilities of terminal devices, they may only be able to receive sidelink services from one or multiple carriers. Because LTE V2X only supports broadcast services, no enhanced carrier selection / reselection scheme has been introduced to address the limited receiving capabilities of terminal devices.

[0004] Therefore, in a new radio (NR) sidelink carrier aggregation scenario, a terminal device of an earlier version (e.g., a terminal device in a communication protocol version Rel-16 or Rel-17) may not be able to receive broadcast or multicast services transmitted by a terminal device that supports carrier aggregation (e.g., a terminal device in a communication protocol version Rel-18), i.e., there is a problem of backward incompatibility of sidelink terminal devices. Summary of the Invention [Problem to be solved by the invention]

[0005] The present disclosure provides a sidelink communication method, apparatus, and communication device that achieves backward compatibility of a sidelink terminal device and further improves the performance of the terminal device. [Means for solving the problem]

[0006] According to a first aspect of the present disclosure, there is provided a sidelink communication method, applicable to a transmitting device side in a sidelink communication system, comprising: determining a first destination address to be compatible with carrier aggregation if all transmission attributes associated with the first destination address correspond to being compatible with carrier aggregation; or determining the first destination address to be 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, the first service being a broadcast service or a multicast service.

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

[0008] In some possible embodiments, the sending attributes are set 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 of the sending attributes associated with the first destination address include sending attributes associated with all service types associated with the first destination address.

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

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

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

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

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

[0016] In some possible embodiments, the method further comprises determining that any of the first destination addresses is not compatible with carrier aggregation and transmitting data of one or more first services on a single carrier.

[0017] According to a second aspect of the present disclosure, there is provided a sidelink communication method, applicable to a receiving device side in a sidelink communication system, comprising: determining that a second destination address is compatible with carrier aggregation if all transmission attributes associated with the second destination address correspond to being compatible with carrier aggregation; or determining that the second destination address is incompatible with carrier aggregation if at least one transmission attribute associated with the second destination address corresponds to being incompatible with carrier aggregation, the second destination address being a 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 transmission attribute is used to indicate whether a broadcast or multicast service is compatible with carrier aggregation.

[0019] In some possible embodiments, the sending attributes are set 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 of the sending attributes associated with the second destination address include sending attributes associated with all service types associated with the second destination address.

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

[0023] In some possible embodiments, one or more transmission attributes are associated with a destination address, the one or more transmission attributes including 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 multiple 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 comprises determining that all of the second destination addresses are compatible with carrier aggregation and receiving data of one or more second services simultaneously on multiple carriers.

[0027] In some possible embodiments, the method further includes determining that any second destination address is not compatible 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, there is provided a communications device, which may be a transmitting device in a sidelink communications system, or a chip or system-on-chip within the transmitting device, or a functional module within the transmitting device for implementing the method of each of the above-described embodiments. The communications device may implement the functions performed by the transmitting device in each of the above-described embodiments, and these functions may be implemented by executing corresponding software via hardware. The hardware or software includes one or more modules corresponding to the above-described functions. The communications device includes a processing module configured to determine 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, 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 corresponds to being incompatible with carrier aggregation, wherein the first destination address is a 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 or multicast service is compatible with carrier aggregation.

[0030] In some possible embodiments, the sending attributes are 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 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.

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

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

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

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

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

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

[0038] In some possible embodiments, the device further comprises a transmitting module, wherein the processing module is configured to determine that any of the first destination addresses is not compatible with carrier aggregation, and the transmitting module is configured to transmit data of one or more first services on a single carrier.

[0039] According to a fourth aspect of the present disclosure, there is provided a communications device, which may be a receiving device in a sidelink communications system, or a chip or system-on-chip within the receiving device, or a functional module within the receiving device for implementing the method of each of the above-described embodiments. The communications device may implement the functions performed by the receiving device in each of the above-described embodiments, and these functions may be implemented by executing corresponding software via hardware. The hardware or software may include one or more modules corresponding to the above-described functions. The communications 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 being compatible with carrier aggregation, or to determine that the second destination address is incompatible with carrier aggregation if at least one transmission attribute associated with the second destination address corresponds to being incompatible with carrier aggregation, wherein the second destination address is a 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 transmission attribute is used to indicate whether a broadcast or multicast service is compatible with carrier aggregation.

[0041] In some possible embodiments, the sending attributes are set 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 of the sending attributes associated with the second destination address include sending attributes associated with all service types associated with the second destination address.

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

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

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

[0047] In some possible embodiments, the device further comprises a receiving module, wherein 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 of one or more second services on a single carrier.

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

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

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

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

[0052] According to a seventh aspect of the present disclosure, there is provided a computer storage medium having stored thereon computer-executable instructions which, when executed by a processor, can effectuate a method according to any one of the first to second aspects of the present disclosure and possible embodiments thereof.

[0053] According to an eighth aspect of the present disclosure, there is provided a computer program or computer program product, which, when run on a computer, causes the computer to implement a method according to any one of the first to second aspects of the present disclosure and possible embodiments thereof.

[0054] In the present disclosure, the sidelink terminal device determines whether the destination address of the first service is compatible with carrier aggregation based on the indication of the associated transmission profile (Tx profile), i.e., whether the associated receiving device supports carrier aggregation. In this way, in a sidelink carrier aggregation scenario, it is ensured that a terminal device with an earlier version (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 terminal device with a later version (e.g., a terminal device supporting carrier aggregation in a Rel-18 version of the communication protocol), thereby realizing backward compatibility of the sidelink terminal device and further improving the performance of the terminal device.

[0055] It should be noted that the third to seventh aspects of the present disclosure are consistent with the technical solutions of the first and second aspects of the present disclosure, and the beneficial effects achieved by the various aspects and corresponding feasible embodiments are similar, so they will not be repeated herein. [Brief explanation of the drawings]

[0056] [Figure 1] 1 is a schematic diagram of the architecture of a communication system in an embodiment of the present disclosure. [Figure 2] FIG. 2 is a schematic diagram of another architecture of a communication system in an embodiment of the present disclosure. [Figure 3] FIG. 1 is a schematic diagram illustrating an implementation process of a sidelink communication method according to an embodiment of the present disclosure. [Figure 4]FIG. 1 is a schematic diagram illustrating an implementation process of a sidelink communication method according to an embodiment of the present disclosure. [Figure 5] FIG. 1 is a schematic diagram illustrating an implementation process of a sidelink communication method according to an embodiment of the present disclosure. [Figure 6] FIG. 1 is a schematic diagram illustrating an implementation process of a sidelink communication method according to an embodiment of the present disclosure. [Figure 7] FIG. 1 is a schematic diagram illustrating an implementation process of a sidelink communication method according to an embodiment of the present disclosure. [Figure 8] FIG. 1 is a schematic diagram illustrating an implementation process of a sidelink communication method according to an embodiment of the present disclosure. [Figure 9] 1 is a structural schematic diagram of a measurement reporting device according to an embodiment of the present disclosure; [Figure 10] FIG. 1 is a structural schematic diagram of a communication device according to an embodiment of the present disclosure. [Figure 11] FIG. 1 is a structural schematic diagram of a terminal device in an embodiment of the present disclosure. [Figure 12] FIG. 1 is a structural schematic diagram of a network device in an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0057] Illustrative examples are described in detail herein, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, like numbers in different drawings refer to the same or similar elements unless otherwise indicated. The embodiments described in the following illustrative examples do not represent all embodiments consistent with embodiments of the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of embodiments of the present disclosure.

[0058] Terms used in the embodiments of the present disclosure are used only for the purpose of describing particular embodiments and are not intended to limit the embodiments of the present disclosure. As used in the embodiments of the present disclosure, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and includes any and all possible combinations of one or more associated listed items.

[0059] In embodiments of the present disclosure, terms such as "first," "second," and "third" may be used to describe various pieces of information, but it should be understood that such information should not be limited to these terms. These terms are used only to distinguish between the same types of information. For example, "first information" may also be referred to as "second information," and similarly, "second information" may also be referred to as "first information" without departing from the scope of embodiments of the present disclosure. Depending on the context, the word "if" used herein may be interpreted as "when," "in the case of," or "in response to a determination."

[0060] Furthermore, in the description of the embodiments of the present disclosure, "and / or" simply indicates an association relationship between related objects and indicates 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 the present disclosure, "plurality" can refer to two or more than two.

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

[0062] The embodiments of the present disclosure enumerate several embodiments in order to clearly explain the technical solutions of the embodiments of the present disclosure.Those skilled in the art can understand that the embodiments provided by the embodiments of the present disclosure can be implemented alone, or can be implemented in combination with the methods of other embodiments in the embodiments of the present disclosure, or can be implemented alone or in combination with some methods of other related technologies, and the embodiments of the present disclosure do not limit this.

[0063] With the development of wireless communication technology, the sidelink (SL) communication mode has been introduced to support direct communication between terminal devices, and communication between terminal devices is performed via the PC5 interface. The sidelink network supports various transmission modes, such as unicast, multicast, and broadcast.

[0064] In one embodiment, there are two transmission resource allocation modes for sidelink communication: 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 broadcasted 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 reports. In Mode 2, the terminal device randomly selects SL transmission resources by itself from the resource pool broadcasted by the network or from a preconfigured resource pool. Here, "preconfigured" may refer to the terminal device obtaining the SL transmission resources from a network element of the core network or the terminal device preconfiguring the SL transmission resources in the terminal device.

[0065] In practical applications, the specific resource allocation mode used by a 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) on a physical sidelink control channel (PSCCH) and also transmits SCI on a physical sidelink shared channel (PSSCH). The SCI carries the resource location, source and destination identifiers of the transmitted data, etc. For data packets with hybrid automatic repeat request (HARQ) enabled (i.e., HARQ-enabled), the receiving device performs HARQ feedback of the PSSCH on a physical sidelink feedback channel (PSFCH).

[0066] In another embodiment, to meet the requirements for improving single-user peak rate and system capacity, one of the easiest ways is to increase the system transmission bandwidth. Therefore, a technology for increasing the transmission bandwidth, namely, carrier aggregation (CA) technology, is introduced in the LTE-Advanced system. Here, the CA technology can aggregate multiple component carriers (CCs) together, thereby effectively improving the uplink and downlink transmission rates.

[0067] Sidelink communication systems based on Long Term Evolution (LTE) communication networks already support sidelink carrier aggregation (CA) technology. However, due to limited transmission and reception capabilities of terminal devices, they may only be able to receive sidelink services on one or more carriers. Because LTE-based sidelink communication systems only support broadcast services, no enhanced carrier selection / reselection schemes have been introduced to address the limited reception capabilities of terminal devices.

[0068] Therefore, in a New Radio (NR) sidelink carrier aggregation scenario, a terminal device of an earlier version (e.g., a terminal device in a communication protocol of 3GPP (registered trademark) Release-16 or Release-17) may not be able to receive a broadcast or multicast service transmitted by a terminal device that supports carrier aggregation (e.g., a terminal device in a communication protocol of version Rel-18), i.e., there is a problem of backward incompatibility of sidelink terminal devices.

[0069] To solve the above technical problems, an embodiment of the present disclosure provides a sidelink communication method applicable to a communication system. The communication system may be a sidelink communication system suitable for fields such as vehicle-to-everything (V2X), intelligent connected vehicles, and autonomous vehicles. The communication system may include at least one communication device. In one scenario, FIG. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present disclosure. Referring to FIG. 1, the communication system 10 may include a network device 11 and a terminal device 12. In another scenario, FIG. 2 is a schematic diagram of another architecture of a communication system according to an embodiment of the present disclosure. Referring to FIG. 2, the communication system 10 may include multiple terminal devices 12. Of course, in the embodiment of the present disclosure, the types and number of network elements included in the communication system and the connection relationships between the network elements are not limited thereto.

[0070] In the embodiments of the present disclosure, a terminal device can communicate with a network device and simultaneously communicate with other terminal devices. The network device can perform resource allocation, scheduling, coordination, etc. for sidelinks of communication between the terminal devices to support direct communication between the terminal devices. The terminal device can also independently perform resource allocation, scheduling, coordination, etc. for sidelinks of communication between other terminal devices, and the embodiments of the present disclosure are not particularly limited.

[0071] In some possible embodiments, the network device may be an access network device used to support a terminal device accessing a wireless communication system, such as 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 terminal device may be a device that provides a voice or data connection to a user. For example, it may also be called a user equipment (UE), a mobile station, a subscriber unit, a station, or a terminal equipment (TE). The communication device may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a handheld vehicle to perdestrian device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a relay node, an AP, etc. With the development of wireless communication technology, any device that can access a wireless communication system, communicate with the network side of the wireless communication system, or communicate with other devices via the wireless communication system may be a terminal device in the embodiments of the present disclosure. For example, a terminal device, an automobile or an RSU in intelligent transportation, a household appliance in a smart home, an electricity meter reader in a smart grid, a voltage monitor, an environmental monitor, a video monitor in an intelligent security network, a cash register, etc. A communication device may be static and fixed, or may be mobile.

[0073] Furthermore, in a sidelink transmission scenario, the communication devices (which may include terminal devices and / or network devices) may be classified into transmitting devices and receiving devices based on the data transmission direction, where the transmitting devices (also referred to as transmitting devices) may include transmitting network devices, transmitting terminal devices, transmitting user devices, etc., and the receiving devices (also referred to as receiving devices) may include receiving network devices, receiving terminal devices, receiving user devices, etc.

[0074] The above transmitting device (also referred to as a transmitting network device, a transmitting terminal device, a transmitting user device, etc.) and receiving device (also referred to as a receiving network device, a receiving terminal device, a receiving user device, etc.) are defined with respect to a certain sidelink connection. For example, a communication device (or a network device, a terminal device, a user device, etc.) is a transmitting device (or a transmitting network device, a transmitting terminal device, a transmitting user device, etc.) in sidelink connection A, but is a receiving device (or a receiving network device, a receiving terminal device, a receiving user device, etc.) in sidelink connection B.

[0075] Hereinafter, a sidelink communication method provided in an embodiment of the present disclosure will be described in conjunction with the above communication system.

[0076] First, it should be noted that in an embodiment of the present disclosure, transmission attributes (Tx profile) associated with a broadcast service or a multicast service (hereinafter abbreviated as "broadcast / multicast service") are set (also referred to as "defined"). Here, "transmission attributes" are also referred to as "transmission configuration," "transmission configuration file," "transmission file," etc.

[0077] In one embodiment, the Tx profile is introduced to ensure compatibility of broadcast or multicast transmission 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, i.e., 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. Exemplarily, the Tx profile may indicate a communication standard version (e.g., Rel-18) or whether carrier aggregation is enabled (e.g., carrier aggregation compatible (ca-compatible) or carrier aggregation incompatible (ca-incompatible)).

[0078] It should be noted that the above "whether a broadcast / multicast service is compatible with carrier aggregation" can be understood as whether, for a particular broadcast / multicast service, sidelink resources on multiple carriers can be used simultaneously to transmit data for destination addresses associated with this service, where the destination addresses can be identified by a destination ID.

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

[0080] In one embodiment, when the Tx profile is set according to the granularity of the service type, one Tx profile is associated with one service type, that is, the Tx profile has a one-to-one correspondence with the service type, and different service types are associated with different Tx profiles. Furthermore, at least one service type is associated with one destination address, that is, one destination address may be associated with multiple different service types, thereby one destination address may be associated with one or more Tx profiles. For example, 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, where Type A corresponds to Tx profile 1, Type B corresponds to Tx profile 2, and Type C corresponds to Tx profile 3, the Tx profiles associated with the first destination address are Tx profile 1, Tx profile 2, and Tx profile 3.

[0081] In another embodiment, when the Tx profile is set according to the granularity of the destination address, one Tx profile is associated with one destination address, that is, one destination address is associated with only one Tx profile, and the upper layer must ensure that all service types associated with one destination address have the same Tx profile. Illustratively, 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 from the above, in the embodiments of the present disclosure, one or more Tx profiles are associated with one destination address, where the one or more Tx profiles include a Tx profile for indicating compatibility with carrier aggregation and / or a Tx profile for indicating incompatibility with carrier aggregation. That is, one or more Tx profiles may be associated with one destination address, including a Tx profile corresponding to compatibility with carrier aggregation and a Tx profile corresponding to incompatibility with carrier aggregation. Of course, there may be other situations regarding the association relationship between Tx profiles and destination addresses, and this is not limited by the embodiments of the present disclosure.

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

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

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

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

[0087] In some possible embodiments, the Tx profile settings may be understood as being pre-configured by the sidelink system (or defined in the communication protocol), and each network element in the sidelink system operates according to the Tx profile settings.

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

[0089] In S301, the sending device determines a first destination address of a first service.

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

[0091] It can be understood that in the transmitting device, an upper layer triggers a first service, determines a first destination address associated with the first service, and instructs the AS, and the AS determines a 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, where the one or more Tx profiles correspond to multiple service types.

[0092] In the embodiments of the present disclosure, the Tx profile is set according to the granularity of the service type, so that one or more Tx profiles associated with the 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 can indicate whether services of different service types are compatible with carrier aggregation.

[0093] Hereinafter, after S301, the sending device may execute S302 or S303.

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

[0095] It can be understood that the AS can determine a Tx profile associated with the first destination address based on instructions from a higher layer, and then determine whether each Tx profile corresponds to being compatible with carrier aggregation or not. The AS determines that Tx profiles associated with all task types related to the first destination address correspond to being compatible with carrier aggregation (which can also be understood as indicating that all Tx profiles associated with the first destination address are compatible with carrier aggregation), in which case the AS determines that the first destination address is compatible with carrier aggregation. At this time, the transmitting device assumes (can also be described as an assumption, hypothesis, etc.) that the first destination address is compatible with carrier aggregation. In S303, if at least one Tx profile associated with the first destination address corresponds to being incompatible with carrier aggregation, the transmitting device determines that the first destination address is incompatible with carrier aggregation.

[0096] The AS determines that a Tx profile associated with at least one service type associated with the first destination address corresponds to incompatibility with carrier aggregation (which may also be understood as indicating that at least one Tx profile associated with the first destination address is incompatible with carrier aggregation), in which case the AS determines that the first destination address is incompatible with carrier aggregation. At this time, the transmitting device assumes (which may also be described as an assumption, hypothesis, etc.) that the first destination address is incompatible with carrier aggregation.

[0097] It should be noted that the above phrase "at least one Tx profile associated with the first destination address corresponds to being incompatible with carrier aggregation" may also be understood to mean that any Tx profile among 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 Tx profile associated with the first destination address is incompatible with carrier aggregation.

[0098] As an example, assume that a 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 a broadcast / multicast service of type A is compatible with carrier aggregation, Tx profile 2 indicates that a broadcast / multicast service of type B is compatible with carrier aggregation, and Tx profile 3 indicates that a broadcast / multicast service of type C is compatible with carrier aggregation, the AS can determine that all Tx profiles associated with destination A correspond to services that are compatible with carrier aggregation. In this case, the AS determines that destination A is compatible with carrier aggregation. Conversely, if at least one of Tx profiles among Tx profile 1, Tx profile 2, and Tx profile 3 indicates that the broadcast / multicast service is incompatible with carrier aggregation, the AS determines that at least one Tx profile associated with destination A corresponds to a service that is incompatible with carrier aggregation. In this case, the AS determines that destination A is incompatible with carrier aggregation.

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

[0100] In one embodiment, Figure 4 is a schematic diagram of an implementation process of a sidelink communication method according to 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 first destination addresses are compatible with carrier aggregation.

[0102] At S402, the transmitting device simultaneously transmits data of one or more first services on multiple carriers.

[0103] In S401 to S402, it can be understood that the AS determines that all first destination addresses among the one or more first destination addresses are compatible with carrier aggregation, in which case the AS enables carrier aggregation and simultaneously transmits data of one or more first services on multiple carriers.

[0104] In S403, the transmitting device determines that any first destination address is not compatible with carrier aggregation.

[0105] Please note that the above phrase "any first destination address is incompatible with carrier aggregation" can be understood to mean that at least one first destination address among the one or more first destination addresses is incompatible with carrier aggregation.

[0106] At S404, the transmitting device transmits data of 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 a Rel-16 or Rel-17 version of a communication protocol.

[0108] In S403 to S404, it can be understood that the AS determines that any first destination address among the one or more first destination addresses is incompatible with carrier aggregation, in which case the AS disables carrier aggregation and transmits data of the one or more first services on a single carrier.

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

[0110] In another embodiment, FIG. 5 shows a schematic diagram of an implementation process of the sidelink communication method in an embodiment of the present disclosure. Referring to FIG. 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 any first destination address is compatible with carrier aggregation.

[0112] It should be noted that the above phrase "any first destination address is compatible with carrier aggregation" can be understood to mean that at least one first destination address among the one or more first destination addresses is compatible with carrier aggregation.

[0113] At S502, the transmitting device simultaneously transmits data of one or more first services on multiple carriers.

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

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

[0116] At S504, the transmitting device transmits data of one or more first services on a single carrier.

[0117] In S503 to S504, it can be understood that the AS determines that all of the one or more first destination addresses are incompatible with carrier aggregation, in which case the AS disables carrier aggregation and transmits data of the one or more first services on a single carrier.

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

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

[0120] In S601, the sending device determines a first destination address of a first service.

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

[0122] In the transmitting device, the upper layer triggers a first service, determines a first destination address associated with the first service, and instructs the AS to execute the first service. The AS determines a Tx profile associated with the first destination address through 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 sending device may perform S602 or S603.

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

[0125] It can be understood that the AS can determine a Tx profile associated with the first destination address based on instructions from a higher layer, and then determine whether the Tx profile corresponds to being compatible with carrier aggregation or not. The AS determines that the Tx profile associated with the first destination address corresponds to being compatible with carrier aggregation (this can also be understood as indicating that the Tx profile associated with the first destination address is compatible with carrier aggregation), in which case the AS determines that the first destination address is compatible with carrier aggregation. In this case, the transmitting device (e.g., AS) assumes (which can also be described as an assumption, hypothesis, etc.) that the first destination address is compatible with carrier aggregation. Please note that the above phrase "the Tx profile associated with the first destination address corresponds to being compatible with carrier aggregation" can be understood to mean that only one Tx profile associated with the first destination address corresponds to being compatible with carrier aggregation, or that all Tx profiles associated with the first destination address correspond to being compatible with carrier aggregation.

[0126] In S603, if the Tx profile (i.e., one Tx profile) associated with the first destination address corresponds to being 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 corresponds to being incompatible with carrier aggregation (which may also be understood as indicating that the Tx profile associated with the first destination address is incompatible with carrier aggregation), in which case the AS may be understood to determine that the first destination address is incompatible with carrier aggregation. In this case, the transmitting device (e.g., the AS) assumes (which may also be described as an assumption, hypothesis, etc.) that the first destination address is incompatible with carrier aggregation.

[0128] It should be noted that the above phrase "the Tx profile associated with the first destination address corresponds to being incompatible with carrier aggregation" can be understood to indicate that only one Tx profile associated with the first destination address corresponds to being incompatible with carrier aggregation, or that one Tx profile associated with the first destination address is incompatible with carrier aggregation.

[0129] Illustratively, 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 may determine that all Tx profiles associated with destination A correspond to being compatible with carrier aggregation, in which 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 may determine that one Tx profile associated with destination A corresponds to being incompatible with carrier aggregation, in which case the AS determines that destination A is not compatible with carrier aggregation.

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

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

[0132] In some possible embodiments, the present disclosure further provides a sidelink communication method applicable to a receiving device in a sidelink communication system. Figure 7 is a schematic diagram illustrating an implementation process of the sidelink communication method according to the embodiment of the present disclosure. Referring to Figure 7, when a Tx profile is configured according to the granularity of the service type, the above method may include the following steps:

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

[0134] It can be understood that in the receiving device, an upper layer determines a second service of interest and indicates a second destination address of the second service to the AS, and the AS 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 indicated by the upper layer, where the one or more Tx profiles correspond to multiple service types.

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

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

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

[0138] It should be noted that the execution process of the above S701 to S703 can refer to the specific description of S301 to S303 in Figure 3. For the sake of brevity, the detailed description will not be given here.

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

[0140] In one embodiment, Figure 8 is a schematic diagram of an implementation process of a 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 second destination addresses are compatible with carrier aggregation.

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

[0143] At S803, the receiving device determines that any second destination address is not compatible with carrier aggregation.

[0144] Please note that the above phrase "any second destination address is incompatible with carrier aggregation" can be understood to mean that at least one of the one or more second destination addresses is incompatible with carrier aggregation.

[0145] At S804, the receiving device receives data of 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 a Rel-16 or Rel-17 version of a communication protocol.

[0147] In another embodiment, after S302 or S303, the transmitting device may perform S805 to S806 (shown in solid lines) or S807 to S808 (shown in dashed lines).

[0148] At S805, the receiving device determines that any second destination addresses are compatible with carrier aggregation.

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

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

[0151] At S808, the receiving device determines to receive data of one or more second services on a single carrier.

[0152] It should be noted that the execution process of the above S801 to S808 can refer to the specific description of S401 to S404 in Figure 4 and S501 to S504 in Figure 5. For the sake of brevity, the detailed description will not be given here.

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

[0154] In an embodiment of the present disclosure, the sidelink terminal device determines whether the destination address of the first service is compatible with carrier aggregation based on the indication of the associated Tx profile, i.e., whether the associated receiving device supports carrier aggregation. In this way, in a sidelink carrier aggregation scenario, it is ensured that a terminal device with an earlier version (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 terminal device with a later version (e.g., a terminal device supporting carrier aggregation in a Rel-18 version of the communication protocol), thereby realizing backward compatibility of the sidelink terminal device and further improving the performance of the terminal device.

[0155] Based on the same inventive concept, an embodiment of the present disclosure provides a sidelink communication device. Figure 9 is a structural schematic diagram of the communication device in the embodiment of the present disclosure. Referring to Figure 9, the communication device 900 may include a processing module 901 and a transmitting module 902.

[0156] In some possible embodiments, the communication device 900 may be a transmitting device in a sidelink communication system, 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-described embodiments. The communication device may implement the functions performed by the transmitting device in the above-described embodiments, and these functions may be implemented by executing corresponding software via hardware. The hardware or software may include one or more modules corresponding to the above-described functions. In this case, referring to the solid line in FIG. 9, the transmission module 902 may be understood as a transmission module 902a.

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

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

[0159] In some possible embodiments, the sending attributes are set at the granularity of the service type or the granularity of the destination address.

[0160] In some possible embodiments, in response to setting the sending attributes at the granularity of service types, one sending 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 of the sending attributes associated with the first destination address include sending attributes associated with all service types associated with the first destination address.

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

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

[0164] In some possible embodiments, the processing module 901 is further configured to determine that any first destination address is compatible with carrier aggregation, and the transmitting module 902a is configured to transmit data of the one or more first services simultaneously on 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 of the one or more first services on 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 of the one or more first services simultaneously on multiple carriers.

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

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

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

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

[0171] In some possible embodiments, the sending attributes are set 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 of the sending attributes associated with the second destination address include sending attributes associated with all service types associated with the second destination address.

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

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

[0176] In some possible embodiments, the processing module 901 is further configured to determine that any second destination address is compatible with carrier aggregation, and the receiving module 902b is configured to receive data of 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 of 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 of 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 second destination address is not compatible with carrier aggregation, and the receiving module 902b is configured to receive data of one or more second services on a single carrier.

[0180] It should be noted that the specific implementation process of the processing module 901 and the transmitting module 902 can refer to the detailed description of the sending device and the receiving device 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 the present disclosure may be a receiving interface, a receiving circuit, a receiver, etc., the transmitting module 902a may be a transmitting interface, a transmitting circuit, a transmitter, etc., and the processing module 901 may be one or more processors.

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

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

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

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

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

[0187] When the processor 101 in the communication device executes the executable code or application program stored in the memory 102, the communication device executes the terminal device-side or network device-side mobility management configuration method 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-executable instructions for implementing the functions of the processing module 901 and the transmission module 902 in Fig. 9. The functions / implementation processes of the processing module 901 and the transmission module 902 in Fig. 9 can be implemented by the processor 101 in Fig. 10 calling the computer-executable instructions stored in the memory 102. For specific implementation processes and functions, please refer to the above related embodiments.

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

[0190] 11 is a schematic diagram of a structure of a terminal device in an embodiment of the present disclosure. Referring to FIG. 11, the terminal device 110 may include one or more components of a processing component 111, a memory 112, a power component 113, a multimedia component 114, an audio component 115, an input / output (I / O) interface 116, a sensor component 117, and a 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 communications, camera operation, and video recording operations. The processing component 111 may include one or more processors 1111 that execute instructions to perform all or some of the steps of the methods described above. Additionally, 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] The memory 112 is configured to store various types of data to support operation at the terminal device 110. Examples of such data include instructions for any applications or methods executed at the terminal device 110, contact data, phone book data, messages, images, videos, etc. The 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 or optical disk, or a combination thereof.

[0193] The power component 113 provides power to the various components of the terminal device 110. The power component 113 includes a power management system, one or more power sources, and other components associated with generating, managing, and distributing 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 a user. In some embodiments, the screen includes a liquid crystal display (LCD) and a touch panel (TP). When the screen includes a touch panel, the screen is implemented as a touchscreen that receives input signals from a user. The touch panel includes one or more touch sensors that detect touches, swipes, and gestures on the touch panel. The touch sensors not only detect the boundaries of the 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 a photo mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. The front camera and the rear camera may each have 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 operation mode such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 112 or transmitted via the 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, buttons, etc. The buttons include, but are not limited to, a home button, volume buttons, start button, lock button, etc.

[0197] The sensor component 117 includes one or more sensors for providing various aspects of the terminal device 110 with status assessments. For example, the sensor component 117 can detect whether the terminal device 110 is open or closed, the relative position of a component (e.g., the display and keypad of the terminal device 110), a change in the position of the terminal device 110 or one of its components, the presence or absence of a user's contact with the terminal device 110, the orientation or acceleration / deceleration of the terminal device 110, and a change in the temperature of the terminal device 110. The sensor component 117 can include a proximity sensor configured to detect the presence of a nearby object without physical contact. The sensor component 117 can also include an optical sensor, such as a CMOS or CCD image sensor for use in imaging applications. In some embodiments, the sensor component 117 can also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[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 a wireless network using a communication standard such as WiFi, 2G, 3G, 4G, 5G, or a combination thereof. In one exemplary embodiment, the communication component 118 receives a broadcast signal 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 can be implemented using radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth™ technology, and other technologies.

[0199] In an exemplary embodiment, 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-described methods.

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

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

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

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

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

[0205] Based on the same inventive concept, an embodiment of the present disclosure also provides a computer-readable storage medium having instructions stored thereon, which, when executed on a computer, perform the sending device-side or receiving device-side method in one or more of the above embodiments.

[0206] Based on the same inventive concept, the embodiments of the present disclosure also provide a computer program or a computer program product, which, when executed on a computer, enables the computer to implement the sending device-side or receiving device-side methods in one or more embodiments.

[0207] Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the present disclosure. This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include technical means common knowledge or customary in the art that are not disclosed in the present disclosure.

[0208] It will be understood that the present disclosure is not limited to the exact configurations described above and illustrated in the accompanying drawings, and that various modifications and changes can be made without departing from the scope thereof.

Claims

1. 1. A sidelink communication method applied to a transmitting device, comprising: 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; 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 is a destination address of a first service, and the first service is a broadcast service or a multicast service. A method characterized by:

2. The transmission attribute is used to indicate whether a broadcast or multicast service is compatible with carrier aggregation.

2. The method of claim 1 .

3. The sending attributes are set according to the granularity of the service type or according to the granularity of the destination address.

3. The method according to claim 1 or 2.

4. 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.

4. The method according to claim 3.

5. All transmission attributes associated with the first destination address include transmission attributes associated with all service types associated with the first destination address.

5. The method of claim 4.

6. In response to the sending attributes being set at the granularity of the destination address, one sending attribute is associated with one destination address.

4. The method according to claim 3.

7. One or more transmission attributes are associated with a destination address, the one or more transmission attributes including a transmission attribute indicating compatibility with carrier aggregation and / or a transmission attribute indicating incompatibility with carrier aggregation.

2. The method of claim 1 .

8. determining that any of the first destination addresses is compatible with carrier aggregation; Further comprising the step of simultaneously transmitting data of one or more first services on multiple carriers.

3. The method according to claim 1 or 2.

9. determining that all of the first destination addresses are incompatible with carrier aggregation; Further comprising transmitting data of one or more first services on a single carrier.

9. The method of claim 8.

10. determining that all of the first destination addresses are compatible with carrier aggregation; Further comprising the step of simultaneously transmitting data of one or more first services on multiple carriers.

3. The method according to claim 1 or 2.

11. determining that any of the first destination addresses is not compatible with carrier aggregation; Further comprising transmitting data of one or more first services on a single carrier.

11. The method of claim 10.

12. 1. A sidelink communication method applied to a receiving device, comprising: determining that a second destination address is compatible with carrier aggregation if all transmission attributes associated with the second destination address correspond to being compatible with carrier aggregation; determining that the second destination address is incompatible with carrier aggregation if at least one transmission attribute associated with the second destination address corresponds to being incompatible with carrier aggregation; The second destination address is a destination address of a second service of interest, the second service being a broadcast service or a multicast service. A method characterized by:

13. The transmission attribute is used to indicate whether a broadcast or multicast service is compatible with carrier aggregation.

13. The method of claim 12.

14. The sending attributes are set according to the granularity of the service type or according to the granularity of the destination address.

14. The method according to claim 12 or 13.

15. 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.

15. The method of claim 14.

16. All transmission attributes associated with the second destination address include transmission attributes associated with all service types associated with the second destination address.

16. The method of claim 15.

17. In response to the sending attributes being set at the granularity of the destination address, one sending attribute is associated with one destination address.

15. The method of claim 14.

18. One or more transmission attributes are associated with a destination address, the one or more transmission attributes including a transmission attribute indicating compatibility with carrier aggregation and / or a transmission attribute indicating incompatibility with carrier aggregation.

13. The method of claim 12.

19. determining that any of the second destination addresses is compatible with carrier aggregation; and receiving data of one or more second services simultaneously on multiple carriers.

14. The method according to claim 12 or 13.

20. determining that all of the second destination addresses are incompatible with carrier aggregation; and receiving data of one or more second services on a single carrier.

20. The method of claim 19.

21. determining that all of the second destination addresses are compatible with carrier aggregation; and receiving data of one or more second services simultaneously on multiple carriers.

14. The method according to claim 12 or 13.

22. determining that any of the second destination addresses is not compatible with carrier aggregation; and receiving data of one or more second services on a single carrier.

22. The method of claim 21 .

23. A communication apparatus applied to a transmitting device, a processing module configured to determine 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, or to determine that the first destination address is not compatible 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 is a destination address of a first service, and the first service is a broadcast service or a multicast service. A communication device comprising:

24. A sidelink receiving apparatus applied to a receiving device, comprising: 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 being compatible with carrier aggregation, or to determine that the second destination address is not compatible with carrier aggregation if at least one transmission attribute associated with the second destination address corresponds to being incompatible with carrier aggregation; The second destination address is a destination address of a second service of interest, the second service being a broadcast service or a multicast service. An apparatus characterized in that

25. an antenna, a memory, and a processor; The processor is coupled to the antenna and to the memory, respectively, and is configured to control transmission and reception of the antenna by executing computer-executable instructions stored in the memory, thereby implementing the method of any one of claims 1 to 22. A communication device characterized by:

26. 23. A method for storing instructions which, when executed on a computer, are used to carry out the method of any one of claims 1 to 22. A computer storage medium comprising:

Images