[go: up one dir, main page]

WO2025030292A1 - 一种侧行链路通信方法及其装置 - Google Patents

一种侧行链路通信方法及其装置 Download PDF

Info

Publication number
WO2025030292A1
WO2025030292A1 PCT/CN2023/111346 CN2023111346W WO2025030292A1 WO 2025030292 A1 WO2025030292 A1 WO 2025030292A1 CN 2023111346 W CN2023111346 W CN 2023111346W WO 2025030292 A1 WO2025030292 A1 WO 2025030292A1
Authority
WO
WIPO (PCT)
Prior art keywords
target address
sidelink
terminal
carrier
logical channel
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/111346
Other languages
English (en)
French (fr)
Inventor
赵力
杨星
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to PCT/CN2023/111346 priority Critical patent/WO2025030292A1/zh
Priority to CN202380010450.6A priority patent/CN119948997A/zh
Publication of WO2025030292A1 publication Critical patent/WO2025030292A1/zh
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/25—Control channels or signalling for resource management between terminals via a wireless link, e.g. sidelink

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a sidelink communication method and device thereof.
  • New Radio (NR) Sidelink supports carrier aggregation, but there is currently a lack of effective means to perform LCP (Logical Channel Prioritization) process in NR Sidelink carrier aggregation scenarios.
  • LCP Logical Channel Prioritization
  • the embodiments of the present disclosure provide a sidelink communication method and a device thereof.
  • a sidelink communication method including:
  • the terminal determines a carrier supported by at least one target address for SL data reception and/or transmission;
  • SL MAC PDU Based on the carrier supported by the at least one target address for SL data reception and/or transmission, determine the first target address of the sidelink media access control protocol data unit SL MAC PDU sent by the terminal from the at least one target address, and/or determine the logical channel contained in the SL MAC PDU;
  • the first target address supports SL data reception on the carrier associated with the sidelink authorization.
  • a sidelink communication method including:
  • the network device sends first configuration information to the terminal, and the first configuration information is used by the terminal to determine a carrier supported by at least one target address for SL data reception and/or transmission, so that the terminal determines the first target address of the sidelink media access control protocol data unit SL MAC PDU sent by the terminal based on the carrier supported by the at least one target address for SL data reception and/or transmission, and/or determines the logical channel contained in the SL MAC PDU; wherein the first target address supports SL data reception on the carrier associated with the sidelink authorization.
  • a first communication device including:
  • a processing module for determining, for a sidelink grant, a carrier supported by at least one target address for SL data reception and/or transmission;
  • the processing module is further used to determine the first target address of the sidelink media access control protocol data unit SL MAC PDU sent by the first communication device from the at least one target address based on the carrier supported by the at least one target address for SL data reception and/or transmission, and/or determine the logical channel contained in the SL MAC PDU;
  • the first target address supports SL data reception on the carrier associated with the sidelink authorization.
  • a second communication device including:
  • a transceiver module used to send first configuration information to a terminal, wherein the first configuration information is used by the terminal to determine a carrier supported by at least one target address for SL data reception and/or transmission, so that the terminal determines the first target address of the sidelink media access control protocol data unit SL MAC PDU sent by the terminal based on the carrier supported by the at least one target address for SL data reception and/or transmission, and/or determines the logical channel contained in the SL MAC PDU; wherein the first target address supports the carrier supported by the sidelink authorization SL data reception is performed on the carrier associated with the right.
  • a communication system including:
  • a terminal configured to execute an optional implementation of the aforementioned first aspect
  • a network device is configured to execute the optional implementation of the aforementioned second aspect.
  • a communication device including: one or more processors;
  • the processor is used to call instructions to enable the communication device to execute the optional implementation of the first and second aspects mentioned above.
  • a storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes optional implementation methods of the aforementioned first and second aspects.
  • the problem of unclear impact of limited receiving terminal capabilities on the logical channel priority LCP process in the NR Sidelink carrier aggregation scenario can be solved.
  • FIG1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure.
  • FIG2A is an interactive schematic diagram of a sidelink communication method according to an embodiment of the present disclosure
  • FIG3A is a schematic flow chart of a sidelink communication method according to an embodiment of the present disclosure.
  • FIG3B is a schematic flow chart of a sidelink communication method according to an embodiment of the present disclosure.
  • FIG4A is a schematic diagram of a flow chart of a sidelink communication method according to an embodiment of the present disclosure
  • FIG5 is an interactive schematic diagram of a sidelink communication method proposed in an embodiment of the present disclosure.
  • FIG6A is a schematic diagram of the structure of a terminal provided in an embodiment of the present disclosure.
  • FIG6B is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure.
  • FIG7A is a schematic diagram of the structure of a communication device 7100 provided in an embodiment of the present disclosure.
  • FIG. 7B is a schematic diagram of the structure of a chip 7200 according to an embodiment of the present disclosure.
  • the embodiments of the present disclosure provide a sidelink communication method and a device thereof.
  • an embodiment of the present disclosure provides a sidelink communication method, including:
  • the terminal determines a carrier supported by at least one target address for SL data reception and/or transmission;
  • SL MAC PDU Based on the carrier supported by the at least one target address for SL data reception and/or transmission, determine the first target address of the sidelink media access control protocol data unit SL MAC PDU sent by the terminal from the at least one target address, and/or determine the logical channel contained in the SL MAC PDU;
  • the first target address supports SL data reception on the carrier associated with the sidelink authorization.
  • the limited receiving capability of the target address i.e. which carrier or carriers on the target address support SL data reception and/or transmission
  • the selected target address supports SL data reception on the carrier associated with the sidelink authorization, which can avoid the problem that the LCP process does not consider which carrier or carriers on the target address support SL data reception and/or transmission, resulting in data errors.
  • the problem of deteriorating transmission quality can be solved, thereby solving the problem of unclear impact of limited receiving terminal capabilities on the logical channel priority LCP process in the NR Sidelink carrier aggregation scenario, which can improve the transmission rate and ensure the transmission quality of the sidelink.
  • the at least one target address includes a second target address, and the service type associated with the second target address is a unicast service; the terminal determines a carrier supported by the at least one target address for SL data reception and/or transmission, including:
  • the capability information including a carrier supporting SL data reception and/or transmission;
  • the network device Based on the capability information and/or first configuration information configured by the network device, determine the carrier supported by the second target address for SL data reception and/or transmission, wherein the first configuration information includes a list of carriers supported by the terminal.
  • the terminal can interact with the receiving terminal associated with the unicast service in terms of terminal capabilities, and determine the carrier supported by the receiving terminal for SL data reception and/or transmission based on the terminal capabilities and in combination with the configuration information of the network device, so that the terminal can perform the LCP process based on the carrier supported by the receiving terminal for SL data reception and/or transmission, thereby ensuring the transmission quality of the side link while improving the transmission rate.
  • determining the carrier supported by the second target address for SL data reception and/or transmission based on the capability information and/or the first configuration information configured by the network device includes:
  • the at least one target address includes a third target address, and the service type associated with the third target address is a multicast service or a broadcast service;
  • the terminal determines a carrier supported by at least one target address for receiving and/or sending SL data, including:
  • the carrier supported by the third target address for SL data reception and/or transmission is determined.
  • determining the carrier supported by the third target address for SL data reception and/or transmission based on the first configuration information and/or the second configuration information of the high-level configuration includes:
  • a carrier supported by the third target address for SL data reception and/or transmission is determined.
  • determining the carrier supported by the third target address for SL data reception and/or transmission based on the first configuration information and/or the second configuration information of the high-level configuration includes:
  • a carrier supported by the third target address for receiving data is determined.
  • the first configuration information is included in a system information block SIB or a pre-configured Information in progress.
  • determining, based on a carrier supported by the at least one target address for SL data reception and/or transmission, a first target address of a sidelink media access control protocol data unit SL MAC PDU sent by the terminal from the at least one target address includes:
  • the first target address of the SL MAC PDU sent by the terminal is determined from the at least one target address.
  • the target address is selected in combination with the carrier capability of the receiving terminal and/or the first condition, so as to solve the problem that the limited receiving terminal capability affects the logical channel priority LCP process in the NR Sidelink carrier aggregation scenario, thereby improving the transmission rate and ensuring the transmission quality of the sidelink.
  • the first condition includes any one or more of the following:
  • the discontinuous reception SL DRX of the side link is applicable to the first target address, the side link grant is at the activation time of the first target address, and the side link grant is used to send the SL MAC PDU;
  • the first target address has at least one highest priority logical channel or MAC CE in at least one first logical channel and/or first media access control layer control unit MAC CE, wherein the first logical channel and/or the first MAC CE satisfies the second condition.
  • the second condition includes any one or more of the following:
  • the first logical channel has a token SBj of a sidelink transmission buffer, SBj>0;
  • the sidelink grant is a configuration grant type 1, and the allowed sidelink configuration grant type 1 sl-configuredGrantType1Allowed parameter configuration associated with the first logical channel allows the media access control service data unit MAC SDU of the logical channel to be transmitted on the configuration grant type 1;
  • a list of configuration authorizations allowed for use is configured, the list comprising configuration authorization identifiers associated with the sidelink authorizations;
  • the sidelink grant has no associated physical sidelink feedback channel PSFCH resource, and a hybrid automatic repeat request HARQ attribute of the first logical channel is HARQ-disabled;
  • Support for transmission on a carrier associated with the sidelink grant is configured.
  • determining the logical channel included in the SL MAC PDU includes:
  • the logical channel that satisfies the third condition is multiplexed into the SL MAC PDU.
  • the third condition includes any one or more of the following:
  • the sl-configuredGrantType1Allowed parameter of the selected logical channel is configured, and in the case where the sidelink grant is the configured grant type 1, the sl-configuredGrantType1Allowed parameter is set to true;
  • a sidelink uplink grant exemption list SL-allowedcg-list of the selected logical channel is configured, the SL-allowedcg-list comprising a configured grant index associated with the sidelink grant;
  • the sidelink hybrid automatic repeat request feedback enable sl-HARQ-FeedbackEnabled of the selected logical channel is set to full Sufficient value for the following conditions:
  • the sidelink grant associated with the sidelink control information SCI configures the PSFCH, and the terminal receives the PSFCH:
  • the sl-HARQ-FeedbackEnabled corresponding to the logical channel with the highest priority among the at least one selected logical channel is set to disabled, and the sl-HARQ-FeedbackEnabled of the next selected logical channel is disabled;
  • the sidechain grant associated with the SCI is not configured with a PSFCH, and/or the terminal does not receive a PSFCH:
  • the sl-HARQ-FeedbackEnabled of the selected logical channel is set to disabled
  • the method further includes:
  • the carrier associated with the sidelink grant is the carrier where the SCI is transmitted, or the carrier associated with the sidelink grant is the carrier where the physical sidelink shared channel PSSCH indicated by the SCI is transmitted.
  • an embodiment of the present disclosure provides a sidelink communication method, including:
  • the network device sends first configuration information to the terminal, and the first configuration information is used by the terminal to determine a carrier supported by at least one target address for SL data reception and/or transmission, so that the terminal determines the first target address of the sidelink media access control protocol data unit SL MAC PDU sent by the terminal based on the carrier supported by the at least one target address for SL data reception and/or transmission, and/or determines the logical channel contained in the SL MAC PDU; wherein the first target address supports SL data reception on the carrier associated with the sidelink authorization.
  • an embodiment of the present disclosure proposes a terminal, comprising at least one of a transceiver module and a processing module; wherein the terminal is used to execute the optional implementation method of the first aspect.
  • an embodiment of the present disclosure proposes a network device, comprising at least one of a transceiver module and a processing module; wherein the above-mentioned network device is used to execute the optional implementation method of the second aspect.
  • an embodiment of the present disclosure provides a communication system, including:
  • a terminal configured as an optional implementation of the first aspect
  • a network device is configured to execute the optional implementation of the aforementioned second aspect.
  • an embodiment of the present disclosure proposes a communication device, comprising: one or more processors; wherein the processor is used to call instructions so that the communication device executes the optional implementation method of the aforementioned first aspect.
  • an embodiment of the present disclosure proposes a communication device, comprising: one or more processors; wherein the processor is used to call instructions so that the communication device executes the optional implementation method of the aforementioned second aspect.
  • an embodiment of the present disclosure proposes a storage medium, wherein the storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes optional implementation methods of the aforementioned first and second aspects.
  • an embodiment of the present disclosure proposes a program product.
  • the communication device executes the method described in the optional implementation of the first aspect and the second aspect.
  • an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first and second aspects.
  • an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or the chip system includes a processing circuit configured to execute the method described in the optional implementation of the first aspect and the second aspect.
  • the embodiments of the present disclosure provide a sidelink communication method and apparatus thereof.
  • the terms such as sidelink communication method, information processing method, communication method, etc. can be replaced with each other, the terms such as sidelink communication apparatus, information processing apparatus, communication apparatus, etc. can be replaced with each other, and the terms such as sidelink communication system, information processing system, communication system, etc. can be replaced with each other.
  • each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined.
  • a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged.
  • the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined, for example, some or all of the steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.
  • elements expressed in the singular form such as “a”, “an”, “the”, “above”, “said”, “aforementioned”, “this”, etc., may mean “one and only one", or “one or more”, “at least one”, etc.
  • the noun after the article may be understood as a singular expression or a plural expression.
  • plurality refers to two or more.
  • the terms "at least one of”, “one or more”, “a plurality of”, “multiple”, etc. can be used interchangeably.
  • "at least one of A and B", “A and/or B", “A in one case, B in another case”, “in response to one case A, in response to another case B”, etc. may include the following technical solutions according to the situation: in some embodiments, A (execute A independently of B); in some embodiments, B (execute B independently of A); in some embodiments, select execution from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). When there are more branches such as A, B, C, etc., it is similar to the above.
  • the recording method of "A or B” may include the following technical solutions according to the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed).
  • A A is executed independently of B
  • B B is executed independently of A
  • execution is selected from A and B (A and B are selectively executed).
  • the ordinal number before the "level” in “first level” and “second level” does not limit the priority between the "levels”.
  • the number of description objects is not limited by ordinal numbers and can be one or more. Take “first device” as an example, where the number of "devices" can be one or more.
  • the objects modified by different prefixes can be the same or different.
  • the description object is "device”
  • the “first device” and the “second device” can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information”, the “first information” and the “second information” can be the same information or different information, and their contents can be the same or different.
  • “including A”, “comprising A”, “used to indicate A”, and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
  • time/frequency refers to the time domain and/or the frequency domain.
  • terms such as “greater than”, “greater than or equal to”, “not less than”, “more than”, “more than or equal to”, “not less than”, “higher than”, “higher than or equal to”, “not lower than”, and “above” can be replaced with each other, and terms such as “less than”, “less than or equal to”, “not greater than”, “less than”, “less than or equal to”, “no more than”, “lower than”, “lower than or equal to”, “not higher than”, and “below” can be replaced with each other.
  • devices and equipment may be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they may also be understood as “equipment”, “device”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, “subject”, etc.
  • network can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.
  • access network device may also be referred to as “radio access network device (RAN device)", “base station (BS)”, “radio base station (radio base station)”, “fixed station” and in some embodiments may also be understood as “node”, “access point (access point)”, “transmission point (TP)”, “reception point (RP)”, “transmission and/or reception point (transmission/reception point, TRP)", “panel”, “antenna panel”, “antenna array”, “cell”, “macro cell”, “small cell”, “femto cell”, “pico cell”, “sector”, “cell group”, “serving cell”, “carrier”, “component carrier”, “bandwidth part (bandwidth part, BWP)", etc.
  • RAN device radio access network device
  • base station base station
  • RP radio base station
  • TRP transmission and/or reception point
  • a “terminal” or a “terminal device” may be referred to as a “user equipment (UE)”, a “user terminal (user terminal)”, a “mobile station (MS)”, a “mobile terminal (MT)”, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, Mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • acquisition of data, information, etc. may comply with the laws and regulations of the country where the data is obtained.
  • data, information, etc. may be obtained with the user's consent.
  • FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.
  • the communication system may include, but is not limited to, a terminal and a network device.
  • the number and form of devices shown in FIG1 are only used as examples and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more terminals and two or more network device terminals may be included.
  • the communication system 100 shown in FIG1 includes, for example, a terminal 101 and a network device 102.
  • the terminal 101 in this document may be an entity on the user side for receiving or transmitting signals, such as a mobile phone. It may also be referred to as a terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), etc.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • the terminal may be a car with communication function, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), etc. At least one of the above.
  • the embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the terminal.
  • the network device 102 may be an access network device.
  • the access network device is, for example, a node or device that accesses a terminal to a wireless network, and the access network device may include at least one of an evolved NodeB (eNB), a next generation eNB (ng-eNB), a next generation NodeB (gNB), a nodeB (NB), a home nodeB (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open RAN, a cloud RAN, a base station in other communication systems, and an access node in a Wi-Fi system, but is not limited thereto.
  • eNB evolved NodeB
  • ng-eNB next generation NodeB
  • gNB next generation NodeB
  • the technical solution of the present disclosure may be applicable to the Open RAN architecture.
  • the interfaces between access network devices or within access network devices involved in the embodiments of the present disclosure may become internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces may be implemented through software or programs.
  • the access network device may be composed of a centralized unit (central unit, CU) and a distributed unit (distributed unit, DU), wherein the CU may also be called a control unit (control unit).
  • the CU-DU structure may be used to split the protocol layer of the access network device, with some functions of the protocol layer being centrally controlled by the CU, and the remaining part or all of the functions of the protocol layer being distributed in the DU, and the DU being centrally controlled by the CU, but not limited to this.
  • the communication system described in the embodiment of the present disclosure is to more clearly illustrate the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. It is known to those skilled in the art that with the evolution of system architecture and the new When business scenarios arise, the technical solutions proposed in the embodiments of the present disclosure are also applicable to similar technical problems.
  • the following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or part of the subject, but are not limited thereto.
  • the subjects shown in FIG1 are examples, and the communication system may include all or part of the subjects in FIG1 , or may include other subjects other than FIG1 , and the number and form of the subjects are arbitrary, and the subjects may be physical or virtual, and the connection relationship between the subjects is an example, and the subjects may be connected or disconnected, and the connection may be in any manner, and may be a direct connection or an indirect connection, and may be a wired connection or a wireless connection.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-B LTE-Beyond
  • SUPER 3G IMT-Advanced
  • 4G the fourth generation mobile communication system
  • 5G 5G new radio
  • FAA Future Radio Access
  • RAT New Radio
  • NR New Radio
  • NX New radio access
  • the present invention relates to wireless communication systems such as LTE, Wi-Fi (X), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) network, Device to Device (D2D) system, Machine to Machine (M2M) system, Internet of Things (IoT) system, Vehicle to Everything (V2X), systems using other communication methods, and next-generation systems expanded based on them.
  • PLMN Public Land Mobile Network
  • D2D Device to Device
  • M2M Machine to Machine
  • IoT Internet of Things
  • V2X Vehicle to Everything
  • systems using other communication methods and next-generation systems expanded based on them.
  • next-generation systems expanded based on them.
  • a combination of multiple systems for example, a combination of
  • the link for direct communication between terminals and the interface between terminals is PC-5.
  • the sending terminal sends the Sidelink Control Information (SCI) on the Physical Sidelink Control Channel (PSCCH) and sends the second stage SCI on the Physical Sidelink Shared Channel (PSSCH), which carries the resource location of the transmission data and the source and target identifiers, etc.
  • SCI Sidelink Control Information
  • PSSCH Physical Sidelink Shared Channel
  • the receiving terminal sends Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) feedback to PSSCH on the Physical Sidelink Feedback Channel (PSFCH).
  • HARQ-ACK Hybrid Automatic Repeat Request-Acknowledgement
  • Carrier aggregation is a key technology in LTE-A.
  • LTE-Advanced system introduces a technology to increase transmission bandwidth, namely CA (Carrier Aggregation).
  • CA Carrier Aggregation, carrier aggregation).
  • CA technology can aggregate multiple carriers (Component Carrier, CC) together, effectively improving the uplink and downlink transmission rates.
  • each carrier participating in carrier aggregation can also be called a component carrier (Component Carrier, CC for short).
  • the multiplexing function of the MAC (Media Access Control) layer of the transmitting terminal loads the data of multiple logical channels into one transmission channel, that is, multiplexes multiple MAC SDUs (MAC Service Data Unit) into one MAC PDU (MAC Protocol Data Unit), and sends it out through the physical layer channel.
  • MAC SDUs MAC Service Data Unit
  • MAC PDU MAC Protocol Data Unit
  • LCP Logical Channel Prioritization
  • Each logical channel has a priority for logical channel scheduling, which is configured by the network. The network configures the priority for this logical channel based on the QoS (Quality of Service) of the data carried by the logical channel.
  • the terminal When the terminal gets the scheduling opportunity, that is, gets the resources for sidelink transmission data on a certain carrier, the terminal first selects the target address, and then selects the SL LCH (Sidelink Logical Channel) that belongs to the target address and meets certain conditions and multiplexes it into the SL MAC PDU (Sidelink MAC Protocol Data Unit).
  • SL LCH Systemlink Logical Channel
  • MAC PDU Segment MAC Protocol Data Unit
  • the upper layer (such as V2X (vehicle to everything) layer) will provide the AS (access stratum) layer with a mapping relationship between Service (service) and frequency (carrier/frequency band), and the upper layer will provide the AS layer with a mapping relationship between Service and Destination L2ID (Destination L2ID).
  • the AS layer can obtain a mapping relationship between Layer 2ID and frequency based on these two mapping relationships.
  • the network device may configure a frequency list supported by the terminal.
  • the list may include one or more entries, each entry being associated with a frequency.
  • the terminal determines the available frequency (carrier/frequency band) through the intersection of high-level configuration and network configuration.
  • LTE V2X already supports sidelink carrier aggregation technology. Due to limited sending and receiving capabilities, the receiving terminal may only be able to receive sidelink services on one or several carriers. Due to limited sending capabilities, the transmitting terminal may only be able to send sidelink services on one or several carriers. LTE V2X does not introduce any carrier selection/reselection enhancement scheme for the limited sending/receiving capabilities of the terminal. The reason is that LTE V2X only supports broadcast services and can rely on high-level implementations to determine which service it is interested in and only receive data on the carrier associated with the service of interest.
  • NR sidelink also supports carrier aggregation.
  • the default is that terminals that support carrier aggregation support sending and receiving on all carriers.
  • this method does not take into account the limited terminal capabilities, that is, there is an issue that the impact of the limited receiving terminal capabilities on the LCP process is unclear, which may lead to poor data transmission quality.
  • the embodiments of the present disclosure provide a side link communication method and apparatus thereof, which can solve the problem of unclear impact of limited receiving terminal capabilities on the LCP process, improve the transmission rate, and ensure data transmission quality.
  • Fig. 2A is an interactive schematic diagram of a sidelink communication method according to an embodiment of the present disclosure. As shown in Fig. 2A, the information processing method of the embodiment of the present disclosure can be applied to a communication system 100, and the method includes but is not limited to the following steps.
  • Step S2101 the network device 102 sends first configuration information.
  • the network device 102 sends the first configuration information to the terminal 101.
  • the terminal 101 obtains the first configuration information configured by the network device 102.
  • the terminal 101 may obtain the first configuration information configured by the network device 102 through dedicated RRC signaling.
  • the terminal 101 is in an RRC connected state, and the terminal 101 may obtain the first configuration information configured by the network device 102 through dedicated RRC signaling.
  • the sidelink transmission resource allocation mode of the terminal 101 may be a network dynamic scheduling allocation mode (such as the above-mentioned mode 1), or may be a terminal autonomously selected allocation mode (such as the above-mentioned mode 2).
  • the first configuration information is included in a SIB (System Information Block).
  • SIB System Information Block
  • the first configuration information may be included in SIB12, and the terminal 101 may obtain the first configuration information configured by the network device 102 through the SIB.
  • the terminal 101 is in an RRC connected state (RRC_CONNECTED)/RRC idle state (RRC_IDLE)/RRC inactive state (RRC_INACTIVE), and the terminal 101 obtains the first configuration information configured by the network device 102 through the SIB.
  • the sidelink transmission resource allocation mode of the terminal 101 may be a network dynamic scheduling allocation mode (such as the above-mentioned mode 1) or a terminal autonomously selected allocation mode (such as the above-mentioned mode 2).
  • the first configuration information is included in the pre-configuration information, and the terminal 101 can obtain the first configuration information configured by the network device 102 through the pre-configuration information.
  • the terminal 101 is in the OOC (Out Of Coverage) state, and the terminal 101 obtains the first configuration information configured by the network device 102 through the pre-configuration information.
  • the sidelink transmission resource allocation mode of the terminal 101 can be a network dynamic scheduling allocation mode (such as the above-mentioned mode 1).
  • the first configuration information includes a frequency band/carrier list, which includes at least one frequency band/carrier.
  • the first configuration information is used by the terminal 101 to determine the frequency band/carrier used for the sidelink communication.
  • the first configuration information is used by the terminal 101 to determine the frequency band/carrier for sending and/or receiving the sidelink communication.
  • the terminal 101 determines the first target address of the SL MAC PDU sent by the terminal 101 based on at least one carrier supported by the target address for receiving and/or sending SL data, and/or determines the logical channel included in the SL MAC PDU.
  • the first target address supports SL data reception on the carrier associated with the sidelink authorization.
  • carrier In some embodiments, the terms “carrier”, “frequency band”, “frequency band”, “frequency” and the like can be used interchangeably.
  • the above carrier list may also be referred to as a carrier set.
  • the network device 102 is configured with one or more supported carriers, and the multiple carriers may be referred to as a list or a set.
  • At least one target address includes a second target address, and the service type associated with the second target address is a unicast service. In some embodiments, at least one target address includes a third target address, and the service type associated with the third target address is a multicast service and/or a broadcast service.
  • the above-mentioned target address can be understood as a target address that has a business relationship with the terminal 101, wherein the target address may include a second target address that has a unicast service with the terminal 101, and exemplarily, the second target address may be any target address that has a unicast connection with the terminal 101; it may also include a third target address of a broadcast and/or multicast service associated with the terminal 101, and exemplarily, the third target address may be the target address of a broadcast and/or multicast service that the terminal 101 is interested in sending and/or receiving.
  • an LCP process needs to be performed. During the LCP process, the terminal 101 first needs to determine the first target address of the SL MAC PDU sent by the terminal 101 from at least one target address and/or determine the logical channel contained in the SL MAC PDU.
  • the terminal 101 when performing the LCP process, the terminal 101 needs to combine the limited receiving capability of the target address so that the selected target address supports SL data reception on the carrier associated with the sidelink authorization.
  • Step S2102 Terminal 101 receives capability information sent by the second target address.
  • the second target address sends capability information.
  • Terminal 101 receives the capability information sent by the second target address.
  • the second target address may be included in at least one of the above-mentioned target addresses.
  • the above-mentioned target address may be understood as a target address that has a service relationship with the terminal 101, wherein the target address may include a second target address that has a unicast service with the terminal 101.
  • the second target address may be any target address that has a unicast connection with the terminal 101.
  • the terminal 101 may exchange terminal capabilities with the second target address to inform the other end of the carrier supported for SL data reception and/or transmission.
  • the terminal 101 acts as a sending terminal and may send the capability information of the terminal 101 to the second target address to inform the second target address of the carrier supported by the terminal 101 for SL data reception and/or transmission.
  • the second target address acts as a receiving terminal, and the second target address sends capability information to the terminal 101, and the capability information may include the carrier supporting SL data reception and/or transmission.
  • the terminal 101 may determine the carrier supported by the second target address for SL data reception and/or transmission through the capability information sent by the second target address.
  • the terminal 101 may receive the capability information sent by the second target address via the sidelink information.
  • the terminal 101 may receive the capability information sent by the second target address via the SCI.
  • the terminal 101 may obtain the capability information sent by the second target address through PC5-RRC signaling, or may receive the capability information sent by the second target address through other means, which is not specifically limited in the present disclosure and will not be described in detail.
  • Step S2103 for the sidelink authorization, the terminal 101 determines a carrier supported by at least one target address for receiving and/or sending SL data.
  • the terminal 101 determines a carrier supported by at least one target address for receiving and/or sending SL data.
  • the carrier supported for receiving and/or sending SL data can be understood as a carrier that supports receiving and/or sending SL data.
  • the at least one target address may include a second target address, and the service type associated with the second target address is a unicast service.
  • the target address may be understood as a target address that has a service relationship with the terminal 101, wherein the target address may include a second target address that has a unicast service with the terminal 101.
  • the second target address may be any target address that has a unicast connection with the terminal 101.
  • the terminal 101 may determine the carrier supported by the second target address for SL data reception and/or transmission based on the capability information sent by the second target address and/or the first configuration information configured by the network device, wherein the first configuration information includes a list of carriers supported by the terminal.
  • terminal 101 can receive the capability information sent by the second target address and the network device can also configure a list of carriers supported by the terminal, terminal 101 can first combine the capability information sent by the second target address and/or the first configuration information configured by the network device during the target address selection stage of the LCP process to determine the carrier supported by the second target address in at least one target address for SL data reception and/or transmission, and exemplarily determine whether the second target address supports receiving SL data on the carrier associated with the sidelink authorization.
  • the terminal 101 may determine the carrier supported by the second target address for SL data reception and/or transmission based on the first configuration information configured by the network device. Alternatively, the terminal 101 determines the carrier supported by the second target address for SL data reception and/or transmission based on the capability information sent by the second target address. Alternatively, the terminal 101 determines the carrier supported by the second target address for SL data reception and/or transmission based on the capability information sent by the second target address and the first configuration information configured by the network device, exemplarily determining whether the second target address supports receiving SL data on the carrier associated with the sidelink authorization.
  • the implementation method in which terminal 101 determines the carriers supported by the second target address for receiving and/or sending SL data based on the capability information sent by the second target address and the first configuration information configured by the network device may include: terminal 101 determines the list of carriers supported by terminal 101 for sending and/or receiving based on the first configuration information configured by the network device; and determines the carriers supported by the second target address for receiving and/or sending SL data based on the intersection of the capability information sent by the second target address and the list of carriers supported by terminal 101 for sending and/or receiving.
  • terminal 101 can determine the list of carriers supported by terminal 101 for sending and/or receiving based on the first configuration information configured by network device 102.
  • the table includes carriers supported by terminal 101 and/or terminal 103 for SL data reception and/or transmission.
  • Terminal 101 determines the carriers supported by terminal 103 for SL data reception and/or transmission based on the intersection of the capability information sent by terminal 103 and the first configuration information configured by the network, that is, the carriers supported by the second target address for SL data reception and/or transmission. Exemplarily, it is determined whether the second target address supports receiving SL data on the carrier associated with the sidelink authorization.
  • the terminal 101 determines the carrier supported by the second target address for SL data reception and/or transmission based on the capability information sent by the second target address
  • the implementation method may include: the terminal 101 determines the carrier supported by the second target address for SL data reception and/or transmission based on the capability information sent by the second target address, and exemplarily determines whether the second target address supports receiving SL data on the carrier associated with the sidelink authorization.
  • the implementation method in which the terminal 101 determines the carrier supported by the second target address for SL data reception and/or transmission based on the first configuration information configured by the network device may include: the terminal 101 determines the carrier supported by the second target address for SL data reception and/or transmission based on the first configuration information configured by the network device.
  • the terminal 101 determines the carrier supported by the second target address for SL data reception and/or transmission based on the first configuration information configured by the network device.
  • the terminal 101 can determine the list of carriers supported by the terminal 101 for transmission and/or reception based on the first configuration information configured by the network device 102, that is, the carriers supported by the terminal 101 and/or the terminal 103 for SL data reception and/or transmission, so that the terminal 101 can determine the carrier supported by the terminal 103 for SL data reception and/or transmission, that is, the carrier supported by the second target address for SL data reception and/or transmission, and exemplarily, determine whether the second target address supports receiving SL data on the carrier associated with the sidelink authorization.
  • the at least one target address may include a second target address, and the service type associated with the second target address is a unicast service.
  • the target address may be understood as a target address having a service relationship with the terminal 101, wherein the target address may include a second target address having a unicast service with the terminal 101.
  • the second target address may be any target address having a unicast connection with the terminal 101.
  • the terminal 101 may determine the carrier supported by the second target address for SL data reception and/or transmission based on at least one of the capability information sent by the second target address, the first configuration information configured by the network device, and the second configuration information configured by the high-level layer, wherein the first configuration information includes a list of carriers supported by the terminal; the second configuration information includes a mapping relationship between the second service and the carrier and/or a mapping relationship between the second service and the second target address, and the second service is a unicast service.
  • the mapping relationship between the second service and the carrier and/or the mapping relationship between the second service and the second target address is determined; based on the mapping relationship between the second target address and the carrier, the carrier supported by the second target address for SL data reception and/or transmission is determined.
  • the carrier supported by the second target address for SL data transmission may refer to the carrier supported by the terminal 101 for sending the unicast service associated with the second target address.
  • the terminal 101 can determine the carrier supported by the second target address for SL data reception and/or transmission based on the first configuration information configured by the network device, and exemplarily determine whether the second target address supports receiving SL data on the carrier associated with the sidelink authorization and/or whether the terminal 101 supports sending unicast services associated with the second target address on the carrier associated with the sidelink authorization.
  • the terminal 101 determines the carrier supported by the second target address for SL data reception and/or transmission based on the capability information sent by the second target address, and exemplarily determines whether the second target address supports receiving SL data on the carrier associated with the sidelink authorization and/or whether the terminal 101 supports sending unicast services associated with the second target address on the carrier associated with the sidelink authorization.
  • the terminal 101 determines the carrier supported by the second target address for SL data reception and/or transmission based on the capability information sent by the second target address and the first configuration information configured by the network device, and exemplarily determines whether the second target address supports receiving SL data on the carrier associated with the sidelink authorization and/or whether the terminal 101 supports sending unicast services associated with the second target address on the carrier associated with the sidelink authorization. Whether the terminal 101 supports receiving SL data on the carrier associated with the sidelink authorization and/or whether the terminal 101 supports sending the unicast service associated with the second target address on the carrier associated with the sidelink authorization.
  • the terminal 101 may determine the carrier supported by the second target address for SL data reception and/or transmission based on the second configuration information configured by the high-level layer, and exemplarily determine whether the second target address supports receiving SL data on the carrier associated with the sidelink authorization and/or whether the terminal 101 supports sending the unicast service associated with the second target address on the carrier associated with the sidelink authorization.
  • the terminal 101 may determine the carrier supported by the second target address for SL data reception and/or transmission based on the capability information sent by the second target address and the second configuration information configured by the high-level layer, and exemplarily determine whether the second target address supports receiving SL data on the carrier associated with the sidelink authorization and/or whether the terminal 101 supports sending the unicast service associated with the second target address on the carrier associated with the sidelink authorization.
  • the terminal 101 may determine the carrier supported by the second target address for SL data reception and/or transmission based on the first configuration information configured by the network device and the second configuration information configured by the high-level layer, and exemplarily determine whether the second target address supports receiving SL data on the carrier associated with the sidelink authorization and/or whether the terminal 101 supports sending unicast services associated with the second target address on the carrier associated with the sidelink authorization.
  • the terminal 101 determines the carrier supported by the second target address for SL data reception and/or transmission based on the capability information sent by the second target address, the first configuration information configured by the network device and the second configuration information configured by the high-level layer, and exemplarily determine whether the second target address supports receiving SL data on the carrier associated with the sidelink authorization and/or whether the terminal 101 supports sending unicast services associated with the second target address on the carrier associated with the sidelink authorization.
  • At least one target address includes a third target address
  • the service type associated with the third target address is a multicast service or a broadcast service.
  • the terminal 101 determines the carrier supported by the third target address for SL data reception and/or transmission, and exemplarily determines whether the third target address supports receiving SL data on the carrier associated with the sidelink authorization.
  • the above-mentioned target address can be understood as a target address that has a service relationship with the terminal 101, wherein the target address may include a third target address of a broadcast and/or multicast service associated with the terminal 101, and exemplarily, a third target address of a broadcast and/or multicast service that the terminal 101 is interested in sending and/or receiving.
  • the terminal 101 can determine the carrier supported by the third target address for SL data reception and/or transmission based on the first configuration information configured by the network device and/or the second configuration information configured by the higher layer.
  • the first configuration information includes a list of carriers supported by the terminal; the second configuration information includes a mapping relationship between the first service and the carrier and/or a mapping relationship between the first service and the third target address.
  • the carrier supported by the third target address for receiving and/or sending SL data refers to the carrier for the terminal 101 to send the broadcast and/or multicast service associated with the third target address, and/or the carrier for the terminal 101 to receive the broadcast and/or multicast service associated with the third target address.
  • terminal 101 may determine the carrier supported by the third target address for SL data reception and/or transmission based on the second configuration information configured by the high-level layer, and exemplarily determine whether the third target address supports receiving SL data on the carrier associated with the side link authorization and/or whether terminal 101 supports sending broadcast/multicast services associated with the third target address on the carrier associated with the side link authorization.
  • terminal 101 may determine the carrier supported by the third target address for SL data reception and/or transmission based on the first configuration information configured by the network device, and exemplarily determine whether the third target address supports receiving SL data on the carrier associated with the side link authorization and/or whether terminal 101 supports sending broadcast/multicast services associated with the third target address on the carrier associated with the side link authorization.
  • the terminal 101 can determine the carrier supported by the third target address for SL data reception and/or transmission based on the first configuration information configured by the network device and the second configuration information configured by the high layer. For example, it can determine whether the third target address supports receiving SL data on the carrier associated with the side link authorization and/or whether the terminal 101 supports sending broadcast/multicast services associated with the third target address on the carrier associated with the side link authorization.
  • the implementation method of the terminal 101 determining the carrier supported by the third target address for SL data reception and/or transmission based on the second configuration information configured by the high-level layer may include: the terminal 101 determines the mapping relationship of the first service to the carrier and/or the mapping relationship of the first service to the third target address based on the second configuration information, wherein the first service includes a multicast service and/or a broadcast service; according to the mapping relationship of the first service to the carrier and/or the mapping relationship of the first service to the third target address, the mapping relationship of the third target address to the carrier is determined; based on the mapping relationship of the third target address to the carrier, the carrier supported by the third target address for SL data reception and/or transmission is determined.
  • the high-level layer of terminal 101 can provide a mapping relationship from the first service to the carrier, and the high-level layer of terminal 101 can also provide a mapping relationship from the first service to the third target address.
  • Terminal 101 can determine the mapping relationship from the third target address to the carrier based on the mapping relationship from the first service to the carrier and the mapping relationship from the first service to the third target address, so as to determine the carrier supported by the third target address for SL data reception and/or transmission.
  • the implementation method of the terminal 101 determining the carrier supported by the third target address for SL data reception and/or transmission based on the first configuration information configured by the network device and the second configuration information configured by the high-level layer may include: the terminal 101 determines the carrier supported by the third target address for receiving and/or sending data based on the intersection of the first configuration information and the second configuration information. Exemplarily, it is determined whether the third target address supports receiving SL data on the carrier associated with the side link authorization and/or whether the terminal 101 supports sending the broadcast/multicast service associated with the third target address on the carrier associated with the side link authorization.
  • the terminal 101 determines that the list of carriers supported by the terminal 101 for SL data reception and/or transmission is carrier 1 and carrier 2 based on the first configuration information configured by the network device, and determines that the carriers supported by the third target address for SL data reception and/or transmission are carrier 1, carrier 2 and carrier 3 based on the second configuration information configured by the high-level layer.
  • the terminal 101 can determine that the carriers supported by the third target address for SL data reception and/or transmission are carrier 1 and carrier 2 based on the intersection of the first configuration information configured by the network device and the second configuration information configured by the high-level layer.
  • step S2104 the terminal 101 determines the first target address of the SL MAC PDU sent by the terminal 101 from the at least one target address based on the carrier supported by the at least one target address for SL data reception and/or transmission, and/or determines the logical channel contained in the at least one SL MAC PDU.
  • the first target address supports SL data reception on the carrier associated with the sidelink authorization.
  • the first target address satisfies the first condition.
  • the first target address supports SL data reception on a carrier associated with the sidelink grant and the first target address satisfies a first condition.
  • the first condition may include any one or more of the following:
  • the sidelink discontinuous reception SL DRX is applicable to the first target address, the sidelink grant is at the activation time of the first target address, and the sidelink grant is used to send the SL MAC PDU;
  • the first target address has at least one logical channel or MAC CE with the highest priority in at least one first logical channel and/or first media access control layer control element MAC CE, wherein the first logical channel and/or the first MAC CE satisfies the second condition Piece.
  • the second condition includes any one or more of the following:
  • the first logical channel has SBj (token of the sidelink send buffer), SBj>0;
  • the sidelink grant is a configuration grant type 1, and the first logical channel is associated with the allowed sl-configuredGrantType1Allowed (sidelink configuration grant type 1) parameter configuration allowing the MAC SDU of the logical channel to be transmitted on the configuration grant type 1;
  • a list of configuration authorizations allowed to be used is configured, the list including configuration authorization identifiers associated with the sidelink authorization;
  • the sidelink grant has no associated PSFCH resources, and the HARQ attribute of the first logical channel is HARQ-disabled (HARQ disabled);
  • Configuration supports transmission on the carrier associated with the above sidelink grant.
  • the terminal 101 based on the second configuration information configured by the high-level layer, it can be determined whether the terminal 101 supports sending the SL data associated with the first target address on the carrier associated with the sidelink authorization.
  • the first target address can be one of the second target addresses associated with the unicast service, or one of the third target addresses associated with the broadcast/multicast service.
  • the terminal 101 can be determined whether the terminal 101 supports sending SL data associated with the first target address on the carrier associated with the sidelink authorization.
  • the first target address can be a target address in the second target address associated with the unicast service, or a target address in the third target address associated with the broadcast/multicast service.
  • the terminal 101 can be determined whether the terminal 101 supports sending the SL data associated with the first target address on the carrier associated with the sidelink authorization.
  • the first target address can be one of the second target addresses associated with the unicast service, or one of the third target addresses associated with the broadcast/multicast service.
  • the terminal 101 may determine the first target address of the SL MAC PDU sent by the terminal from at least one target address based on the carrier supported by at least one target address for SL data reception and/or transmission and/or the above-mentioned first condition.
  • the terminal 101 may determine the first target address of the SL MAC PDU sent by the terminal from at least one target address based on the carrier supported by at least one target address for SL data reception and/or transmission and the above-mentioned first condition.
  • the terminal 101 can select the first target address of the SL MAC PDU from at least one target address based on the above-mentioned first condition and the carrier supported by at least one target address for SL data reception and/or transmission, the selected first target address satisfies the above-mentioned first condition, and the first target address has at least one highest priority logical channel or MAC CE in the logical channels and/or media access control layer control unit MAC CE that satisfy the above-mentioned second condition.
  • the implementation method of the terminal 101 determining the logical channels included in the SL MAC PDU may include: the terminal 101 selects a logical channel that meets the third condition from the logical channels belonging to the first target address; and multiplexes the logical channel that meets the third condition into the SL MAC PDU.
  • the third condition includes any one or more of the following:
  • the selected logical channel has SL data to send;
  • the sl-configuredGrantType1Allowed parameter of the selected logical channel is configured, and in the case where the sidelink grant is configured as grant type 1, the sl-configuredGrantType1Allowed parameter is set to true;
  • the sidelink uplink exemption list SL-allowedcg-list of the selected logical channel is configured, and the SL-allowedcg-list contains comprising a configuration grant index associated with the sidelink grant;
  • the sidelink hybrid automatic repeat request feedback enable sl-HARQ-FeedbackEnabled of the selected logical channel is set to a value that satisfies the following conditions:
  • the sidelink grant associated with the sidelink control information SCI configures the PSFCH, and the terminal receives the PSFCH:
  • the sl-HARQ-FeedbackEnabled corresponding to the logical channel with the highest priority among the at least one selected logical channel is set to disabled, and the sl-HARQ-FeedbackEnabled of the next selected logical channel is disabled;
  • the sl-HARQ-FeedbackEnabled of the selected logical channel is set to disabled
  • 5 is configured to support transmission on the carrier associated with the sidelink grant (is allowed on the carrier/frequency associated/of the SL grant, if configured).
  • the terminal 101 based on the second configuration information configured by the high-level layer, it can be determined whether the terminal 101 supports sending the SL data associated with the first target address on the carrier associated with the sidelink authorization.
  • the first target address can be one of the second target addresses associated with the unicast service, or one of the third target addresses associated with the broadcast/multicast service.
  • the terminal 101 can be determined whether the terminal 101 supports sending SL data associated with the first target address on the carrier associated with the sidelink authorization.
  • the first target address can be a target address in the second target address associated with the unicast service, or a target address in the third target address associated with the broadcast/multicast service.
  • the terminal 101 can be determined whether the terminal 101 supports sending the SL data associated with the first target address on the carrier associated with the sidelink authorization.
  • the first target address can be one of the second target addresses associated with the unicast service, or one of the third target addresses associated with the broadcast/multicast service.
  • the terminal 101 can select the first target address of the SL MAC PDU from at least one target address based on the above-mentioned first condition and the carrier supported by at least one target address for SL data reception and/or transmission, and select the logical channel that meets the above-mentioned third condition from the logical channels belonging to the first target address, and multiplex the logical channel that meets the above-mentioned third condition into the above-mentioned SL MAC PDU to complete the packetization of the SL MAC PDU.
  • the terminal 101 can send the SL MAC PDU on the carrier associated with the sidelink authorization.
  • the target receiving terminal of the SL MAC PDU i.e., the above-mentioned first target address
  • Step S2105 Terminal 101 sends SCI to the first target address.
  • the carrier associated with the sidelink grant is the carrier where the SCI is transmitted, or the carrier associated with the sidelink grant is the carrier where the PSSCH indicated by the SCI is transmitted.
  • the carrier associated with the sidelink grant is the carrier on which the SCI is transmitted.
  • the carrier associated with the sidelink grant is the carrier where the PSSCH indicated by the SCI is located.
  • the names of information and the like are not limited to the names described in the embodiments, and include “information”, “message”, “signal”, “signaling”, “report”, “configuration”, “indication”, “instruction”, “command”, “channel”, “parameter”,
  • domain “field”, “symbol”, “code element”, “codebook”, “codeword”, “codepoint”, “bit”, “data”, “program”, “chip” and the like are interchangeable.
  • terms such as “uplink”, “uplink”, “physical uplink” can be interchangeable, and terms such as “downlink”, “downlink”, “physical downlink” can be interchangeable, and terms such as “side”, “sidelink”, “side communication”, “sidelink communication”, “direct connection”, “direct link”, “direct communication”, “direct link communication” can be interchangeable.
  • obtain can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from high levels, obtaining by self-processing, autonomous implementation, etc.
  • terms such as “certain”, “preset”, “preset”, “set”, “indicated”, “some”, “any”, and “first” can be interchangeable, and "specific A”, “preset A”, “preset A”, “set A”, “indicated A”, “some A”, “any A”, and “first A” can be interpreted as A pre-defined in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., and can also be interpreted as specific A, some A, any A, or first A, etc., but is not limited to this.
  • the determination or judgment can be performed by a value represented by 1 bit (0 or 1), by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values (for example, comparison with a predetermined value), but is not limited to this.
  • step S2103+step S2104 can be implemented as an independent embodiment
  • step S2101+step S2103+step S2104 can be implemented as an independent embodiment
  • step S2102+step S2103+step S2104 can be implemented as an independent embodiment
  • step S2101+step S2102+step S2103+step S2104 can be implemented as an independent embodiment
  • step S2103+step S2104+step S2104 can be implemented as an independent embodiment.
  • Step S2105 can be implemented as an independent embodiment
  • step S2101+step S2103+step S2104+step S2105 can be implemented as an independent embodiment
  • step S2102+step S2103+step S2104+step S2105 can be implemented as an independent embodiment
  • step S2101+step S2102+step S2103+step S2104+step S2105 can be implemented as an independent embodiment, but are not limited to this.
  • step S2101 and step S2102 may be executed in an interchangeable order or simultaneously.
  • step S2101, step S2102, and step S2105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2102 and step S2105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2101 and step S2105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2105 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2101 and step S2102 are optional. In different embodiments, one or more of these steps may be selected. Several steps were omitted or substituted.
  • step S2101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • Fig. 3A is a flow chart of a sidelink communication method according to an embodiment of the present disclosure. As shown in Fig. 3A, the embodiment of the present disclosure relates to a sidelink communication method, which can be executed by terminal 101, and the method can include but is not limited to the following steps.
  • Step S3101 receiving first configuration information.
  • the terminal 101 receives the first configuration information sent by the network device 102.
  • the network device 102 sends the first configuration information
  • the terminal 101 receives the first configuration information sent by the network device 102.
  • the first configuration information is included in a SIB (System Information Block), and the terminal 101 can obtain the first configuration information configured by the network device 102 through the SIB.
  • SIB System Information Block
  • the terminal 101 is in an RRC idle state (RRC_IDLE)/RRC inactive state (RRC_INACTIVE), and the terminal 101 obtains the first configuration information configured by the network device 102 through the SIB.
  • the sidelink transmission resource allocation mode of the terminal 101 can be a network dynamic scheduling allocation mode (such as the above-mentioned mode1).
  • the first configuration information is included in the pre-configuration information, and the terminal 101 can obtain the first configuration information configured by the network device 102 through the pre-configuration information.
  • the terminal 101 is in the OOC state, and the terminal 101 obtains the first configuration information configured by the network device 102 through the pre-configuration information.
  • the sidelink transmission resource allocation mode of the terminal 101 can be a network dynamic scheduling allocation mode (such as the above-mentioned mode 1).
  • the first configuration information is used by the terminal 101 to determine a carrier supported by at least one target address for SL data reception and/or transmission, so that the terminal 101 determines the first target address of the SL MAC PDU sent by the terminal 101 based on the carrier supported by at least one target address for SL data reception and/or transmission, and/or determines the logical channel included in the SL MAC PDU.
  • the first target address supports SL data reception on the carrier associated with the sidelink authorization.
  • step S3101 can refer to the optional implementation of step S2101 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • Step S3102 receiving capability information sent by the second target address.
  • the capability information may include carriers supporting SL data reception and/or transmission.
  • step S3102 can refer to the optional implementation of step S2102 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • Step S3103 for the sidelink authorization, determine a carrier supported by at least one target address for SL data reception and/or transmission.
  • the at least one target address may include a second target address, and the service type associated with the second target address is a unicast service.
  • the terminal 101 may determine the carrier supported by the second target address for SL data reception and/or transmission based on the capability information sent by the second target address and/or the first configuration information configured by the network device. Its optional implementation method can refer to the optional implementation method of step S2103 of Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.
  • At least one target address includes a third target address
  • the service type associated with the third target address is a multicast service or a broadcast service.
  • the carrier supported by the third target address for SL data reception and/or transmission is determined. Its optional implementation method can refer to the optional implementation method of step S2103 of Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.
  • Step S3104 based on the carrier supported by the above-mentioned at least one target address for SL data reception and/or transmission, determine the first target address of the SL MAC PDU sent by the terminal 101 from the above-mentioned at least one target address, and/or determine the logical channel contained in the above-mentioned SL MAC PDU.
  • step S3104 can refer to the optional implementation of step S2104 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • Step S3105 sending SCI to the above-mentioned first target address.
  • the carrier associated with the sidelink grant is the carrier where the SCI is transmitted, or the carrier associated with the sidelink grant is the carrier where the PSSCH indicated by the SCI is transmitted.
  • step S3105 can refer to the optional implementation of step S2105 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • step S3103+step S3104 can be implemented as an independent embodiment
  • step S3101+step S3103+step S3104 can be implemented as an independent embodiment
  • step S3102+step S3103+step S3104 can be implemented as an independent embodiment
  • step S3101+step S3102+step S3103+step S3104 can be implemented as an independent embodiment
  • step S3103+step S3104+step S3104 can be implemented as an independent embodiment.
  • Step S3105 can be implemented as an independent embodiment
  • step S3101+step S3103+step S3104+step S3105 can be implemented as an independent embodiment
  • step S3102+step S3103+step S3104+step S3105 can be implemented as an independent embodiment
  • step S3101+step S3102+step S3103+step S3104+step S3105 can be implemented as an independent embodiment, but is not limited to this.
  • step S3101 and step S3102 may be executed in an interchangeable order or simultaneously.
  • step S3101, step S3102, and step S3105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S3102 and step S3105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S3101 and step S3105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S3105 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S3101 and step S3102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S3101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S3102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • Fig. 3B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in Fig. 3B, the embodiment of the present disclosure relates to an information processing method, which can be executed by the terminal 101, and the method may include but is not limited to the following steps.
  • Step S3201 for a sidelink authorization, determine a carrier supported by at least one target address for SL data reception and/or transmission.
  • the at least one target address may include a second target address
  • the service type associated with the second target address is a unicast service.
  • the optional implementation method for the terminal 101 to determine the carrier supported by at least one target address for SL data reception and/or transmission includes: receiving capability information sent by the second target address, the capability information includes the carrier supporting SL data reception and/or transmission; based on the capability information sent by the second target address and/or the first configuration information configured by the network device, determining the carrier supported by the second target address for SL data reception and/or transmission, wherein the first configuration information includes a list of carriers supported by the terminal.
  • the optional implementation method can refer to the optional implementation method of step S2103 of Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.
  • the terminal 101 determines the carrier supported by the second target address for SL data reception and/or transmission based on the capability information and/or the first configuration information configured by the network device.
  • the implementation method may include: determining a list of carriers supported by the terminal based on the first configuration information configured by the network device; determining the carrier supported by the second target address for SL data reception and/or transmission based on the intersection of the capability information and the list of carriers supported by the terminal.
  • At least one target address includes a third target address
  • the service type associated with the third target address is a multicast service or a broadcast service.
  • the optional implementation method for the terminal 101 to determine the carrier supported by at least one target address for SL data reception and/or transmission includes: based on the first configuration information configured by the network device and/or the second configuration information configured by the high layer (such as the V2X layer), determining the carrier supported by the third target address for SL data reception and/or transmission. Its optional implementation method can refer to the optional implementation method of step S2103 of Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.
  • the implementation method of the terminal 101 determining the carrier supported by the third target address for SL data reception and/or transmission based on the first configuration information configured by the network device and/or the second configuration information configured by the high-level layer may include: determining the mapping relationship of the first service to the carrier and/or the mapping relationship of the first service to the third target address based on the second configuration information, wherein the first service includes a multicast service and/or a broadcast service; determining the mapping relationship of the third target address to the carrier based on the mapping relationship of the first service to the carrier and/or the mapping relationship of the first service to the third target address; determining the carrier supported by the third target address for SL data reception and/or transmission based on the mapping relationship of the third target address to the carrier.
  • Its optional implementation can refer to the optional implementation of step S2103 of Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.
  • the implementation method of the terminal 101 determining the carrier supported by the third target address for SL data reception and/or transmission based on the first configuration information configured by the network device and/or the second configuration information configured by the high-level layer may include: determining the carrier supported by the third target address for receiving data based on the intersection of the first configuration information and the second configuration information.
  • Its optional implementation method can refer to the optional implementation method of step S2103 of Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.
  • the first configuration information is included in SIB or pre-configuration information.
  • Step S3202 based on the carrier supported by at least one target address for SL data reception and/or transmission, determine the first target address of the sidelink media access control protocol data unit SL MAC PDU sent by the terminal from at least one target address, and/or determine the logical channel contained in the SL MAC PDU.
  • the first target address supports SL data reception on a carrier associated with the sidelink grant.
  • the terminal 101 supports the carrier and/or the first carrier for SL data reception and/or transmission based on at least one target address.
  • a condition is used to determine a first target address of the SL MAC PDU sent by the terminal from at least one target address.
  • the first condition includes any one or more of the following:
  • the discontinuous reception SL DRX of the side link is applicable to the first target address, the side link grant is at the activation time of the first target address, and the side link grant is used to send the SL MAC PDU;
  • the first target address has at least one highest priority logical channel or MAC CE in at least one first logical channel and/or first media access control layer control unit MAC CE, wherein the first logical channel and/or the first MAC CE satisfies the second condition.
  • the second condition includes any one or more of the following:
  • the first logical channel has a token SBj of the sidelink transmission buffer, SBj>0;
  • the sidelink grant is a configuration grant type 1, and the first logical channel is associated with an allowed sidelink configuration grant type 1 sl-configuredGrantType1Allowed parameter configuration that allows the media access control service data unit MAC SDU of the logical channel to be transmitted on the configuration grant type 1;
  • a list of configuration authorizations allowed to be used is configured, the list including configuration authorization identifiers associated with the sidelink authorization;
  • the sidelink grant has no associated physical sidelink feedback channel PSFCH resources, and the hybrid automatic repeat request HARQ attribute of the first logical channel is HARQ disabled;
  • Support for transmission on the carrier associated with the sidelink grant is configured.
  • the implementation method of the terminal 101 determining the logical channels contained in the SL MAC PDU may include: selecting a logical channel that meets the third condition from the logical channels belonging to the first target address; and multiplexing the logical channel that meets the third condition into the SL MAC PDU.
  • the third condition includes any one or more of the following:
  • the selected logical channel has SL data to send;
  • the sl-configuredGrantType1Allowed parameter of the selected logical channel is configured, and in the case where the sidelink grant is configured as grant type 1, the sl-configuredGrantType1Allowed parameter is set to true;
  • the allowed sidelink uplink grant exemption list SL-allowedcg-list of the selected logical channel is configured, and the SL-allowedcg-list includes a configured grant index associated with the sidelink grant;
  • the sidelink hybrid automatic repeat request feedback enable sl-HARQ-FeedbackEnabled of the selected logical channel is set to a value that satisfies the following conditions:
  • the sidelink grant associated with the sidelink control information SCI configures the PSFCH, and the terminal receives the PSFCH:
  • the sl-HARQ-FeedbackEnabled corresponding to the logical channel with the highest priority among the at least one selected logical channel is set to disabled, and the sl-HARQ-FeedbackEnabled of the next selected logical channel is disabled;
  • the sl-HARQ-FeedbackEnabled of the selected logical channel is set to disabled
  • Support for transmission on the carrier associated with the sidelink grant is configured (is allowed on the carrier/frequency associated/of the SL grant, if configured by upper layers).
  • step S3202 can refer to the optional implementation of step S2104 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • the terminal 101 sends the SCI to the first target address.
  • the carrier associated with the sidelink grant is the carrier where the SCI is transmitted, or the carrier associated with the sidelink grant is the carrier where the PSSCH indicated by the SCI is located.
  • the optional implementation method thereof can refer to the optional implementation method of step S2105 of FIG. 2 and other related parts of the embodiment involved in FIG. 2, which will not be repeated here.
  • Fig. 4A is a flow chart of a sidelink communication method according to an embodiment of the present disclosure. As shown in Fig. 4A, the method involved in the embodiment of the present disclosure can be applied to the network device 102, and the method includes but is not limited to the following steps.
  • Step S4101 sending first configuration information.
  • the first configuration information is configured by the network device 102 to the terminal 101.
  • the network device 102 sends the first configuration information to the terminal 101.
  • the terminal 101 receives the first configuration information, such as the terminal 101 receives the first configuration information sent by the network device 101.
  • the first configuration information is used by the terminal 101 to determine a carrier supported by at least one target address for SL data reception and/or transmission, so that the terminal 101 determines the first target address of the SL MAC PDU sent by the terminal 101 based on the carrier supported by the at least one target address for SL data reception and/or transmission, and/or determines the logical channel contained in the above SL MAC PDU; wherein the first target address supports SL data reception on the carrier associated with the sidelink authorization.
  • Its optional implementation method can refer to step S2103 of Figure 2, the optional implementation method of step S2104, and other related parts of the embodiment involved in Figure 2, which will not be repeated here.
  • At least one target address includes a second target address, and the service type associated with the second target address is a unicast service; the terminal 101 determines that the second target address supports the carrier for SL data reception and/or transmission based on the capability information sent by the second target address and/or the first configuration information configured by the network device 102, wherein the first configuration information includes a list of carriers supported by the terminal.
  • the terminal 101 determines that the second target address supports the carrier for SL data reception and/or transmission based on the capability information sent by the second target address and/or the first configuration information configured by the network device 102, wherein the first configuration information includes a list of carriers supported by the terminal.
  • At least one target address includes a third target address, and the service type associated with the third target address is a multicast service or a broadcast service; the terminal 101 determines the carrier supported by the third target address for SL data reception and/or transmission based on the first configuration information configured by the network device and/or the second configuration information configured by the high layer.
  • the terminal 101 determines the carrier supported by the third target address for SL data reception and/or transmission based on the first configuration information configured by the network device and/or the second configuration information configured by the high layer.
  • Its optional implementation method can refer to the optional implementation method of step S2103 of Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.
  • step S4101 can refer to the optional implementation of step S2101 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • Fig. 5 is an interactive schematic diagram of a sidelink communication method according to an embodiment of the present disclosure. As shown in Fig. 5, the method involved in the embodiment of the present disclosure can be applied to a communication system 100, and the method includes but is not limited to the following steps.
  • Step S5101 the network device 102 sends first configuration information to the terminal 101.
  • the first configuration information is used by the terminal 101 to determine a carrier supported by at least one target address for SL data reception and/or transmission, so that the terminal 101 determines the first target address of the sidelink media access control protocol data unit SL MAC PDU sent by the terminal based on the carrier supported by at least one target address for SL data reception and/or transmission, and/or determines the SL MAC PDU Included logical channels; wherein the first target address supports SL data reception on a carrier associated with a sidelink grant.
  • step S5101 can refer to the optional implementation of step S2101 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • Step S5102 for the sidelink authorization, the terminal 101 determines a carrier supported by at least one target address for SL data reception and/or transmission.
  • step S5102 can refer to the optional implementation of step S2103 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • step S5103 the terminal 101 determines the first target address of the sidelink media access control protocol data unit SL MAC PDU sent by the terminal from at least one target address based on the carrier supported by at least one target address for SL data reception and/or transmission, and/or determines the logical channel contained in the SL MAC PDU.
  • step S5103 can refer to the optional implementation of step S2104 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • the above method may include the method described in the above terminal side, network device side, etc., which will not be repeated here.
  • the transmitting terminal when selecting a target terminal/address during the LCP process, the transmitting terminal needs to consider the receiving capability of the target terminal on the carrier associated with the sidelink authorization.
  • the transmitting terminal when selecting a target terminal/address during the LCP process, the transmitting terminal needs to consider whether the sidelink logical channel supports transmission on the carrier associated with the sidelink authorization.
  • the target terminal/address (such as the first target address mentioned above) selected by the sending terminal during the LCP process supports reception on the carrier associated with the sidelink grant.
  • the target terminal/address supports receiving on the carrier associated with the sidelink authorization.
  • this implementation i.e., the example of a solution in which the target terminal/address supports receiving on the carrier associated with the sidelink authorization
  • the transmitting terminal may obtain the carrier/frequency band supported by the opposite terminal (such as the terminal associated with the second target address) through PC5-RRC signaling.
  • the opposite terminal is a terminal that has a unicast connection with the transmitting terminal. The present disclosure does not specifically limit how to obtain this information.
  • this implementation method can be applicable to both unicast and multicast and/or broadcast.
  • the transmitting terminal can obtain the carrier/frequency band supported for sending and/or receiving by the target layer 2 address (such as the third target address mentioned above) associated with the multicast and/or broadcast service through the second configuration information configured by the high layer (V2X layer) and/or the first configuration information configured by the network device.
  • the target layer 2 address such as the third target address mentioned above
  • the present disclosure does not specifically limit how to obtain this information.
  • the above association has two meanings.
  • the carrier associated with the sidelink authorization is the carrier where the SCI transmission is located.
  • the carrier associated with the sidelink authorization is the carrier where the PSSCH indicated by the SCI is located.
  • the SL LCH associated with the target terminal/address selected by the sending terminal during the LCP process supports transmission on the carrier associated with the sidelink grant.
  • the target terminal/address has at least one MAC CE or logical channel with the highest priority among all logical channels and MAC CEs that satisfy the following conditions (such as the second condition above):
  • the sidelink grant is a configured grant type 1
  • the sl-configuredGrantType1Allowed configuration associated with the logical channel allows the MAC SDU of the logical channel to be transmitted on the configured grant type 1;
  • the list includes the configuration authorization identifier associated with the sidelink authorization
  • the HARQ attribute of the logical channel is HARQ-disabled
  • the above conditions may apply to one or more of the following: unicast, multicast, and broadcast.
  • the sending terminal may obtain the target layer 2 address associated with the unicast and/or multicast and/or broadcast service and/or the carrier/frequency band supported by the SL LCH associated with the target layer 2 address through high-level configuration and/or network device configuration.
  • the present disclosure does not specifically limit how to obtain this information.
  • the LCP selects a sidelink logical channel belonging to the target address to support transmission on the carrier associated with the sidelink grant.
  • a logical channel that satisfies the following third condition may be selected, and the selected logical channel supports transmission on a carrier associated with the sidelink authorization.
  • the third condition includes any one or more of the following:
  • the sl-configuredGrantType1Allowed parameter of the selected logical channel is configured, and in the case where the sidelink grant is the configured grant type 1, the sl-configuredGrantType1Allowed parameter is set to true;
  • a sidelink uplink grant exemption list SL-allowedcg-list of the selected logical channel is configured, the SL-allowedcg-list comprising a configured grant index associated with the sidelink grant;
  • the sidelink hybrid automatic repeat request feedback enable sl-HARQ-FeedbackEnabled of the selected logical channel is set to a value that satisfies the following conditions:
  • the sidelink grant associated with the sidelink control information SCI configures the PSFCH, and the terminal receives the PSFCH:
  • the sl-HARQ-FeedbackEnabled corresponding to the logical channel with the highest priority among the at least one selected logical channel is set to disabled, and the sl-HARQ-FeedbackEnabled of the next selected logical channel is disabled;
  • the sidechain grant associated with the SCI is not configured with a PSFCH, and/or the terminal does not receive a PSFCH:
  • the sl-HARQ-FeedbackEnabled of the selected logical channel is set to disabled
  • the third condition mentioned above may be applicable to unicast and/or multicast and/or broadcast.
  • the sending terminal may obtain the target layer 2 address associated with the unicast and/or multicast and/or broadcast service and/or the carrier/frequency band supported by the SL LCH associated with the target layer 2 address through high-level configuration and/or network device configuration.
  • the present disclosure does not specifically limit how to obtain this information.
  • the embodiment of the present disclosure can solve the problem that the impact of limited transmitting and/or receiving terminal capabilities on the LCP process in the NR Sidelink carrier aggregation scenario is unclear.
  • the embodiments of the present disclosure also propose a device for implementing any of the above methods, for example, a device is proposed, the above device includes a unit or module for implementing each step performed by the terminal in any of the above methods.
  • a device is also proposed, including a unit or module for implementing each step performed by the network device in any of the above methods.
  • the division of the units or modules in the above device is only a division of logical functions, which can be fully or partially integrated into one physical entity or physically separated in actual implementation.
  • the units or modules in the device can be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and instructions are stored in the memory.
  • the processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory inside the device or a memory outside the device.
  • CPU central processing unit
  • microprocessor a microprocessor
  • the units or modules in the device may be implemented in the form of hardware circuits, and the functions of some or all of the units or modules may be implemented by designing the hardware circuits.
  • the hardware circuits may be understood as one or more processors; for example, in one implementation, the hardware circuits are application-specific integrated circuits (ASICs), and the functions of some or all of the above units or modules may be implemented by designing the logical relationship of the components in the circuits; for another example, in another implementation, the hardware circuits may be implemented by programmable logic devices (PLDs), and Field Programmable Gate Arrays (FPGAs) may be used as an example, which may include a large number of logic gate circuits, and the connection relationship between the logic gate circuits may be configured by configuring the configuration files, thereby implementing the functions of some or all of the above units or modules. All units or modules of the above devices may be implemented in the form of software called by the processor, or in the form of hardware circuits, or in the form of software called by the processor, and the remaining part may be implemented in
  • the processor is a circuit with information processing capability.
  • the processor may be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which may be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor may implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the above hardware circuit may be fixed or reconfigurable, such as a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the process of the processor loading a configuration document to implement the hardware circuit configuration may be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules.
  • it can also be a hardware circuit designed for artificial intelligence, which can be understood as ASIC, such as Neural Network Processing Unit (NPU), Tensor Processing Unit (TPU), Deep Learning Processing Unit (DPU), etc.
  • ASIC Neural Network Processing Unit
  • NPU Neural Network Processing Unit
  • TPU Tensor Processing Unit
  • DPU Deep Learning Processing Unit
  • FIG6A is a schematic diagram of the structure of the terminal proposed in an embodiment of the present disclosure.
  • the terminal 6100 may include: at least one of a transceiver module 6101, a processing module 6102, etc.
  • the processing module is used to determine, for a sidelink authorization, a carrier supported by at least one target address for SL data reception and/or transmission; the processing module is also used to determine, based on the carrier supported by at least one target address for SL data reception and/or transmission, the first target address of the sidelink media access control protocol data unit SL MAC PDU sent by the terminal from at least one target address, and/or determine the logical channel contained in the SL MAC PDU; wherein the first target address supports SL data reception on the carrier associated with the sidelink authorization.
  • the transceiver module is used to execute at least one of the communication steps such as sending and/or receiving (for example, step S2102, step S2105, but not limited thereto) executed by the terminal 101 in any of the above methods, which will not be repeated here.
  • the processing module is used to execute other steps (for example, step S2102, step S2105) executed by the terminal 101 in any of the above methods. At least one of step S2103, step S2104, but not limited to these) will not be repeated here.
  • FIG6B is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure.
  • the network device 6200 may include: at least one of a transceiver module 6201, a processing module 6202, etc.
  • the transceiver module is used to send first configuration information to the terminal, and the first configuration information is used for the terminal to determine a carrier supported by at least one target address for SL data reception and/or transmission, so that the terminal determines the first target address of the sidelink media access control protocol data unit SL MAC PDU sent by the terminal based on the carrier supported by at least one target address for SL data reception and/or transmission, and/or determines the logical channel contained in the SL MAC PDU; wherein the first target address supports SL data reception on the carrier associated with the sidelink authorization.
  • the transceiver module is used to execute at least one of the communication steps such as sending and/or receiving (such as step S2101, but not limited to this) executed by the network device 6200 in any of the above methods, which will not be repeated here.
  • the processing module is used to execute at least one of the other steps executed by the network device 102 in any of the above methods, which will not be repeated here.
  • the transceiver module may include a sending module and/or a receiving module, and the sending module and the receiving module may be separate or integrated.
  • the transceiver module may be interchangeable with the transceiver.
  • the processing module can be a module or include multiple submodules.
  • the multiple submodules respectively execute all or part of the steps required to be executed by the processing module.
  • the processing module can be replaced with the processor.
  • the communication device 7100 may be a terminal, or a network device, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods, or a chip, a chip system, or a processor that supports a network device to implement any of the above methods.
  • the communication device 7100 may be used to implement the method described in the above method embodiment, and the details may refer to the description in the above method embodiment.
  • the communication device 7100 includes one or more processors 7101.
  • the processor 7101 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit.
  • the baseband processor may be used to process the communication protocol and the communication data
  • the central processing unit may be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a program, and process the data of the program.
  • the communication device 7100 is used to execute any of the above methods.
  • the communication device 7100 further includes one or more memories 7102 for storing instructions.
  • the memory 7102 may also be outside the communication device 7100.
  • the communication device 7100 further includes one or more transceivers 7103.
  • the transceiver 7103 performs at least one of the communication steps such as sending and/or receiving in the above method (for example, step S2101, step S2102, step S2105, but not limited thereto), and the processor 7101 performs at least one of the other steps (for example, step S2103, step S2104, but not limited thereto).
  • the transceiver may include a receiver and/or a transmitter, and the receiver and the transmitter may be separate or integrated.
  • the terms such as transceiver, transceiver unit, transceiver, transceiver circuit, etc. may be replaced with each other, the terms such as transmitter, transmission unit, transmitter, transmission circuit, etc. may be replaced with each other, and the terms such as receiver, receiving unit, receiver, receiving circuit, etc. may be replaced with each other.
  • the communication device 7100 may include one or more interface circuits 7104.
  • the interface circuit 7104 is connected to the memory 7102, and the interface circuit 7104 may be used to receive signals from the memory 7102 or other devices, and may be used to send signals to the memory 7102 or other devices.
  • the interface circuit 7104 may read instructions stored in the memory 7102 and send the instructions to the processor 7101.
  • the communication device 7100 described in the above embodiment may be a terminal or a network device, but the scope of the communication device 7100 described in the present disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited to FIG. 7A.
  • the communication device may be an independent device or may be Part of a larger device.
  • the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.
  • FIG. 7B is a schematic diagram of the structure of a chip 7200 provided in an embodiment of the present disclosure.
  • the communication device 7100 may be a chip or a chip system
  • the chip 7200 includes one or more processors 7201, and the chip 7200 is used to execute any of the above methods.
  • the chip 7200 further includes one or more interface circuits 7202.
  • the interface circuit 7202 is connected to the memory 7203.
  • the interface circuit 7202 can be used to receive signals from the memory 7203 or other devices, and the interface circuit 7202 can be used to send signals to the memory 7203 or other devices.
  • the interface circuit 7202 can read instructions stored in the memory 7203 and send the instructions to the processor 7201.
  • the interface circuit 7202 executes at least one of the communication steps such as sending and/or receiving in the above method (for example, step S2101, step S2102, step S2105, but not limited to these), and the processor 7201 executes at least one of the other steps (for example, step S2103, step S2104, but not limited to these).
  • interface circuit interface circuit
  • transceiver pin transceiver
  • the chip 7200 further includes one or more memories 7203 for storing instructions.
  • the memory 7203 may be outside the chip 7200.
  • the present disclosure also proposes a storage medium, on which instructions are stored, and when the instructions are executed on the communication device 7100, the communication device 7100 executes any of the above methods.
  • the storage medium is an electronic storage medium.
  • the storage medium is a computer-readable storage medium, but is not limited to this, and it can also be a storage medium readable by other devices.
  • the storage medium can be a non-transitory storage medium, but is not limited to this, and it can also be a temporary storage medium.
  • the present disclosure also proposes a program product, which, when executed by the communication device 7100, enables the communication device 7100 to execute any of the above methods.
  • the program product is a computer program product.
  • the present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to execute any one of the above methods.
  • the computer program product includes one or more computer programs.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer program can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer program can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.
  • the computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated.
  • the available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a high-density digital video disc (DVD)
  • DVD high-density digital video disc
  • SSD solid state disk

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例公开了一种侧行链路通信方法及其装置。其中方法包括：针对侧行链路授权，终端确定至少一个目标地址支持的用于侧行链路SL数据接收和/或发送的载波；基于至少一个目标地址支持的用于SL数据接收和/或发送的载波，从至少一个目标地址中确定终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定SL MAC PDU包含的逻辑信道；其中，第一目标地址支持在侧行链路授权关联的载波上进行SL数据接收。通过实施本公开实施例，可以解决NR Sidelink载波聚合场景下，受限的接收终端能力对逻辑信道优先级LCP过程的影响不清楚的问题。

Description

一种侧行链路通信方法及其装置 技术领域
本公开涉及通信技术领域，尤其涉及一种侧行链路通信方法及其装置。
背景技术
为了支持终端与终端之间的直接通信，引入了直连通信(也叫侧行链路，Sidelink，SL)通信方式，终端与终端之间的接口为PC-5。新空口(New Radio，NR)Sidelink支持载波聚合，但是目前尚缺乏用于在NR Sidelink载波聚合场景下执行LCP(Logical ChannelPrioritization，逻辑信道优先级)过程的有效手段。
发明内容
本公开实施例提出了一种侧行链路通信方法及其装置。
根据本公开实施例的第一方面，提出了一种侧行链路通信方法，包括：
针对侧行链路授权，终端确定至少一个目标地址支持的用于SL数据接收和/或发送的载波；
基于所述至少一个目标地址支持的用于SL数据接收和/或发送的载波，从所述至少一个目标地址中确定所述终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定所述SL MAC PDU包含的逻辑信道；
其中，所述第一目标地址支持在所述侧行链路授权关联的载波上进行SL数据接收。
根据本公开实施例的第二方面，提出了一种侧行链路通信方法，包括：
网络设备向终端发送第一配置信息，所述第一配置信息用于所述终端确定至少一个目标地址支持的用于SL数据接收和/或发送的载波，以使所述终端基于所述至少一个目标地址支持的用于SL数据接收和/或发送的载波确定所述终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定所述SL MAC PDU包含的逻辑信道；其中，所述第一目标地址支持在侧行链路授权关联的载波上进行SL数据接收。
根据本公开实施例的第三方面，提出了一种第一通信装置，包括：
处理模块，用于针对侧行链路授权，确定至少一个目标地址支持的用于SL数据接收和/或发送的载波；
所述处理模块，还用于基于所述至少一个目标地址支持的用于SL数据接收和/或发送的载波，从所述至少一个目标地址确定所述第一通信装置发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定所述SL MAC PDU包含的逻辑信道；
其中，所述第一目标地址支持在所述侧行链路授权关联的载波上进行SL数据接收。
根据本公开实施例的第四方面，提出了一种第二通信装置，包括：
收发模块，用于向终端发送第一配置信息，所述第一配置信息用于所述终端确定至少一个目标地址支持的用于SL数据接收和/或发送的载波，以使所述终端基于所述至少一个目标地址支持的用于SL数据接收和/或发送的载波确定所述终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定所述SL MAC PDU包含的逻辑信道；其中，所述第一目标地址支持在侧行链路授 权关联的载波上进行SL数据接收。
根据本公开实施例的第五方面，提出了一种通信系统，包括：
终端，被配置为执行前述第一方面的可选实现方式；
网络设备，被配置为执行前述第二方面的可选实现方式。
根据本公开实施例的第六方面，提出了一种通信设备，包括：一个或多个处理器；
其中，所述处理器用于调用指令以使得所述通信设备执行前述第一方面和第二方面的可选实现方式。
根据本公开实施例的第七方面，提出了一种存储介质，所述存储介质存储有指令，当所述指令在通信设备上运行时，使得所述通信设备执行前述第一方面和第二方面的可选实现方式。
根据本公开技术方案，可以解决NR Sidelink载波聚合场景下，受限的接收终端能力对逻辑信道优先级LCP过程的影响不清楚的问题。
附图说明
为了更清楚地说明本公开实施例中的技术方案，以下对实施例描述所需的附图进行介绍，以下附图仅仅是本公开的一些实施例，不对本公开的保护范围造成具体限制。
图1是本公开实施例提供的一种通信系统的架构示意图；
图2A是根据本公开实施例示出的侧行链路通信方法的交互示意图；
图3A是根据本公开实施例示出的侧行链路通信方法的流程示意图；
图3B是根据本公开实施例示出的侧行链路通信方法的流程示意图；
图4A是根据本公开实施例示出的一种侧行链路通信方法的流程示意图；
图5是本公开实施例提出的侧行链路通信方法的交互示意图；
图6A是本公开实施例提出的终端的结构示意图；
图6B是本公开实施例提出的网络设备的结构示意图；
图7A是本公开实施例提出的通信设备7100的结构示意图；
图7B是本公开实施例提出的芯片7200的结构示意图。
具体实施方式
本公开实施例提出了一种侧行链路通信方法及其装置。
第一方面，本公开实施例提出一种侧行链路通信方法，包括：
针对侧行链路授权，终端确定至少一个目标地址支持的用于SL数据接收和/或发送的载波；
基于所述至少一个目标地址支持的用于SL数据接收和/或发送的载波，从所述至少一个目标地址中确定所述终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定所述SL MAC PDU包含的逻辑信道；
其中，所述第一目标地址支持在所述侧行链路授权关联的载波上进行SL数据接收。
在上述实施例中，在LCP过程，考虑结合目标地址受限的接收能力(即目标地址上哪个或哪些载波支持SL数据接收和/或发送)，以使得选择出的目标地址支持侧行链路授权关联的载波上进行SL数据接收，可以避免LCP过程中没有考虑目标地址上哪个或哪些载波支持SL数据接收和/或发送而导致数 据传输质量变差的问题，从而可以解决NR Sidelink载波聚合场景下，受限的接收终端能力对逻辑信道优先级LCP过程的影响不清楚的问题，可以提高传输速率，并保障侧行链路的传输质量。
结合第一方面的一些实施例，在一些实施例中，所述至少一个目标地址包括第二目标地址，所述第二目标地址关联的业务类型为单播业务；所述终端确定至少一个目标地址支持的用于SL数据接收和/或发送的载波，包括：
接收所述第二目标地址发送的能力信息，所述能力信息包括支持SL数据接收和/或发送的载波；
基于所述能力信息和/或网络设备配置的第一配置信息，确定所述第二目标地址支持的用于SL数据接收和/或发送的载波，其中，所述第一配置信息包括所述终端支持的载波列表。
在上述实施例中，针对单播业务，终端可以与单播业务关联的接收终端交互终端能力，基于该终端能力，结合网络设备的配置信息，确定接收终端支持的用于SL数据接收和/或发送的载波，便于终端基于接收终端支持的用于SL数据接收和/或发送的载波进行LCP过程，从而可以保障侧行链路的传输质量的同时，还可以提高传输速率。
结合第一方面的一些实施例，在一些实施例中，所述基于所述能力信息和/或网络设备配置的第一配置信息，确定所述第二目标地址支持的用于SL数据接收和/或发送的载波，包括：
基于所述网络设备配置的第一配置信息，确定所述终端支持的载波列表；
基于所述能力信息和所述终端支持的载波列表的交集，确定所述第二目标地址支持的用于SL数据接收和/或发送的载波。
结合第一方面的一些实施例，在一些实施例中，所述至少一个目标地址包括第三目标地址，所述第三目标地址关联的业务类型为组播业务或广播业务；
所述终端确定至少一个目标地址支持的用于SL数据接收和/或发送的载波，包括：
基于网络设备配置的第一配置信息和/或高层配置的第二配置信息，确定所述第三目标地址支持的用于SL数据接收和/或发送的载波。
在上述实施例中，针对广播或组播业务，可以依赖高层和/或网络设备实现确定对哪个业务感兴趣，并只在感兴趣的业务关联的载波上接收数据，提高传输速率的同时，还可以保障侧行链路的传输质量。
结合第一方面的一些实施例，在一些实施例中，所述基于所述第一配置信息和/或所述高层配置的第二配置信息，确定所述第三目标地址支持的用于SL数据接收和/或发送的载波，包括：
基于所述第二配置信息，确定第一业务到载波的映射关系和/或所述第一业务到所述第三目标地址的映射关系，其中，所述第一业务包括组播业务和/或广播业务；
根据所述第一业务到载波的映射关系和/或所述第一业务到所述第三目标地址的映射关系，确定所述第三目标地址到载波的映射关系；
基于所述第三目标地址到载波的映射关系，确定所述第三目标地址支持的用于SL数据接收和/或发送的载波。
结合第一方面的一些实施例，在一些实施例中，所述基于所述第一配置信息和/或所述高层配置的第二配置信息，确定所述第三目标地址支持的用于SL数据接收和/或发送的载波，包括：
基于第一配置信息和第二配置信息的交集，确定所述第三目标地址支持的用于接收数据的载波。
结合第一方面的一些实施例，在一些实施例中，所述第一配置信息包含在系统信息块SIB或预配置 信息中。
结合第一方面的一些实施例，在一些实施例中，所述基于所述至少一个目标地址支持的用于SL数据接收和/或发送的载波，从所述至少一个目标地址中确定所述终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，包括：
基于所述至少一个目标地址支持的用于SL数据接收和/或发送的载波和/或所述第一条件，从所述至少一个目标地址确定所述终端发送的SL MAC PDU的第一目标地址。
在上述实施例中，NR Sidelink载波聚合场景下，结合接收终端的载波能力和/或第一条件选择目标地址，可以解决NR Sidelink载波聚合场景下，受限的接收终端能力对逻辑信道优先级LCP过程的影响不清楚的问题，可以提高传输速率，并保障侧行链路的传输质量。
结合第一方面的一些实施例，在一些实施例中，所述第一条件包括以下任意一种或多种：
侧行链路的非连续接收SL DRX适用于所述第一目标地址，所述侧行链路授权处于所述第一目标地址的激活时间，所述侧行链路授权用于发送所述SL MAC PDU；
所述第一目标地址在至少一个第一逻辑信道和/或第一媒体接入控制层控制单元MAC CE中具有至少一个最高优先级的逻辑信道或者MAC CE，其中，第一逻辑信道和/或第一所述MAC CE满足第二条件。
结合第一方面的一些实施例，在一些实施例中，所述第二条件包括以下任意一种或多种：
具有等待发送的SL数据；
所述第一逻辑信道有侧行链路发送缓冲器的令牌SBj，SBj>0；
所述侧行链路授权是配置授权类型1，所述第一逻辑信道关联的允许侧行链路配置授权类型1sl-configuredGrantType1Allowed参数配置允许逻辑信道的媒体接入控制服务数据单元MAC SDU在所述配置授权类型1上传输；
配置了允许使用的配置授权的列表，所述列表包含了所述侧行链路授权关联的配置授权标识；
所述侧行链路授权没有关联的物理侧行链路反馈信道PSFCH资源，所述第一逻辑信道的混合自动重传请求HARQ属性是HARQ去使能HARQ-disabled；
配置了支持在所述侧行链路授权关联的载波上发送。
结合第一方面的一些实施例，在一些实施例中，所述确定所述SL MAC PDU包含的逻辑信道，包括：
从属于所述第一目标地址的逻辑信道中，选择满足第三条件的逻辑信道；
将所述满足第三条件的逻辑信道复用到所述SL MAC PDU中。
结合第一方面的一些实施例，在一些实施例中，所述第三条件包括以下任意一种或多种：
1)所述选择的逻辑信道有SL数据可发送；且，
2)所述选择的逻辑信道的sl-configuredGrantType1Allowed参数被配置，在所述侧行链路授权是所述配置授权类型1的情况下，所述sl-configuredGrantType1Allowed参数设置为真；且，
3)所述选择的逻辑信道的允许侧行链路上行免授权列表SL-allowedcg–list被配置，所述SL-allowedcg–list包括与所述侧行链路授权相关联的配置授权索引；且，
4)所述选择的逻辑信道的侧行链路混合自动重传请求反馈使能sl-HARQ-FeedbackEnabled设置为满 足以下条件的值：
A)与侧行链路控制信息SCI关联的侧链授权配置了PSFCH，并且所述终端接收所述PSFCH：
I)已经选择的至少一个逻辑信道中优先级最高的逻辑信道对应的sl-HARQ-FeedbackEnabled为使能，下一个选择的逻辑信道的sl-HARQ-FeedbackEnabled为使能；或者，
II)已经选择的至少一个逻辑信道中优先级最高的逻辑信道对应的sl-HARQ-FeedbackEnabled设置为去使能，下一个选择的逻辑信道的sl-HARQ-FeedbackEnabled为去使能；
B)与SCI关联的侧链授权未配置PSFCH，和/或，所述终端不接收PSFCH：
所述选择的逻辑信道的sl-HARQ-FeedbackEnabled设置为不使能；
5)配置了支持在所述侧行链路授权关联的载波上发送。
结合第一方面的一些实施例，在一些实施例中，所述方法还包括：
向所述第一目标地址发送侧行链路控制信息SCI；其中，
所述侧行链路授权关联的载波为所述SCI传输所在的载波，或者，所述侧行链路授权关联的载波为所述SCI指示的物理侧行链路共享信道PSSCH所在的载波。
第二方面，本公开实施例提出一种侧行链路通信方法，包括：
网络设备向终端发送第一配置信息，所述第一配置信息用于所述终端确定至少一个目标地址支持的用于SL数据接收和/或发送的载波，以使所述终端基于所述至少一个目标地址支持的用于SL数据接收和/或发送的载波确定所述终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定所述SL MAC PDU包含的逻辑信道；其中，所述第一目标地址支持在侧行链路授权关联的载波上进行SL数据接收。
第三方面，本公开实施例提出一种终端，包括收发模块、处理模块中的至少一者；其中，上述终端用于执行第一方面的可选实现方式。
第四方面，本公开实施例提出一种网络设备，包括收发模块、处理模块中的至少一者；其中，上述网络设备用于执行第二方面的可选实现方式。
第五方面，本公开实施例提出一种通信系统，包括：
终端，被配置为前述第一方面的可选实现方式；
网络设备，被配置为执行前述第二方面的可选实现方式。
第六方面，本公开实施例提出一种通信设备，包括：一个或多个处理器；其中，所述处理器用于调用指令以使得所述通信设备执行前述第一方面的可选实现方式。
第七方面，本公开实施例提出一种通信设备，包括：一个或多个处理器；其中，所述处理器用于调用指令以使得所述通信设备执行前述第二方面的可选实现方式。
第八方面，本公开实施例提出一种存储介质，所述存储介质存储有指令，当所述指令在通信设备上运行时，使得所述通信设备执行前述第一方面和第二方面的可选实现方式。
第九方面，本公开实施例提出程序产品，上述程序产品被通信设备执行时，使得上述通信设备执行如第一方面和第二面的可选实现方式所描述的方法。
第十方面，本公开实施例提出了计算机程序，当其在计算机上运行时，使得计算机执行如第一方面和第二方面的可选实现方式所描述的方法。
第十一方面，本公开实施例提供了一种芯片或芯片系统。该芯片或芯片系统包括处理电路，被配置为执行根据上述第一方面和第二方面的可选实现方式所描述的方法。
可以理解地，上述终端、网络设备、通信系统、存储介质、程序产品、计算机程序、芯片或芯片系统均用于执行本公开实施例所提出的方法。因此，其所能达到的有益效果可以参考对应方法中的有益效果，此处不再赘述。
本公开实施例提出了侧行链路通信方法及其装置。在一些实施例中，侧行链路通信方法、信息处理方法、通信方法等术语可以相互替换，侧行链路通信装置、信息处理的装置、通信装置等术语可以相互替换，侧行链路通信系统、信息处理系统、通信系统等术语可以相互替换。
本公开实施例并非穷举，仅为部分实施例的示意，不作为对本公开保护范围的具体限制。在不矛盾的情况下，某一实施例中的每个步骤均可以作为独立实施例来实施，且各步骤之间可以任意组合，例如，在某一实施例中去除部分步骤后的方案也可以作为独立实施例来实施，且在某一实施例中各步骤的顺序可以任意交换，另外，某一实施例中的可选实现方式可以任意组合；此外，各实施例之间可以任意组合，例如，不同实施例的部分或全部步骤可以任意组合，某一实施例可以与其他实施例的可选实现方式任意组合。
在各本公开实施例中，如果没有特殊说明以及逻辑冲突，各实施例之间的术语和/或描述具有一致性，且可以互相引用，不同实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本公开实施例中所使用的术语只是为了描述特定实施例的目的，而并非作为对本公开的限制。
在本公开实施例中，除非另有说明，以单数形式表示的元素，如“一个”、“一种”、“该”、“上述”、“所述”、“前述”、“这一”等，可以表示“一个且只有一个”，也可以表示“一个或多个”、“至少一个”等。例如，在翻译中使用如英语中的“a”、“an”、“the”等冠词(article)的情况下，冠词之后的名词可以理解为单数表达形式，也可以理解为复数表达形式。
在本公开实施例中，“多个”是指两个或两个以上。
在一些实施例中，“至少一者(至少一项、至少一个)(at least one of)”、“一个或多个(one or more)”、“多个(a plurality of)”、“多个(multiple)等术语可以相互替换。
在一些实施例中，“A、B中的至少一者”、“A和/或B”、“在一情况下A，在另一情况下B”、“响应于一情况A，响应于另一情况B”等记载方式，根据情况可以包括以下技术方案：在一些实施例中A(与B无关地执行A)；在一些实施例中B(与A无关地执行B)；在一些实施例中从A和B中选择执行(A和B被选择性执行)；在一些实施例中A和B(A和B都被执行)。当有A、B、C等更多分支时也类似上述。
在一些实施例中，“A或B”等记载方式，根据情况可以包括以下技术方案：在一些实施例中A(与B无关地执行A)；在一些实施例中B(与A无关地执行B)；在一些实施例中从A和B中选择执行(A和B被选择性执行)。当有A、B、C等更多分支时也类似上述。
本公开实施例中的“第一”、“第二”等前缀词，仅仅为了区分不同的描述对象，不对描述对象的位置、顺序、优先级、数量或内容等构成限制，对描述对象的陈述参见权利要求或实施例中上下文的描述，不应因为使用前缀词而构成多余的限制。例如，描述对象为“字段”，则“第一字段”和“第二字 段”中“字段”之前的序数词并不限制“字段”之间的位置或顺序，“第一”和“第二”并不限制其修饰的“字段”是否在同一个消息中，也不限制“第一字段”和“第二字段”的先后顺序。再如，描述对象为“等级”，则“第一等级”和“第二等级”中“等级”之前的序数词并不限制“等级”之间的优先级。再如，描述对象的数量并不受序数词的限制，可以是一个或者多个，以“第一装置”为例，其中“装置”的数量可以是一个或者多个。此外，不同前缀词修饰的对象可以相同或不同，例如，描述对象为“装置”，则“第一装置”和“第二装置”可以是相同的装置或者不同的装置，其类型可以相同或不同；再如，描述对象为“信息”，则“第一信息”和“第二信息”可以是相同的信息或者不同的信息，其内容可以相同或不同。
在一些实施例中，“包括A”、“包含A”、“用于指示A”、“携带A”，可以解释为直接携带A，也可以解释为间接指示A。
在一些实施例中，“时频(time/frequency)”、“时频域”等术语是指时域和/或频域。
在一些实施例中，“响应于……”、“响应于确定……”、“在……的情况下”、“在……时”、“当……时”、“若……”、“如果……”等术语可以相互替换。
在一些实施例中，“大于”、“大于或等于”、“不小于”、“多于”、“多于或等于”、“不少于”、“高于”、“高于或等于”、“不低于”、“以上”等术语可以相互替换，“小于”、“小于或等于”、“不大于”、“少于”、“少于或等于”、“不多于”、“低于”、“低于或等于”、“不高于”、“以下”等术语可以相互替换。
在一些实施例中，装置和设备可以解释为实体的、也可以解释为虚拟的，其名称不限定于实施例中所记载的名称，在一些情况下也可以被理解为“设备(equipment)”、“设备(device)”、“电路”、“网元”、“节点”、“功能”、“单元”、“部件(section)”、“系统”、“网络”、“芯片”、“芯片系统”、“实体”、“主体”等。
在一些实施例中，“网络”可以解释为网络中包含的装置，例如，接入网设备、核心网设备等。
在一些实施例中，“接入网设备(access network device，AN device)”也可以被称为“无线接入网设备(radio access network device，RAN device)”、“基站(base station，BS)”、“无线基站(radio base station)”、“固定台(fixed station)”，在一些实施例中也可以被理解为“节点(node)”、“接入点(access point)”、“发送点(transmission point，TP)”、“接收点(reception point，RP)”、“发送和/或接收点(transmission/reception point，TRP)”、“面板(panel)”、“天线面板(antenna panel)”、“天线阵列(antenna array)”、“小区(cell)”、“宏小区(macro cell)”、“小型小区(small cell)”、“毫微微小区(femto cell)”、“微微小区(pico cell)”、“扇区(sector)”、“小区组(cell group)”、“服务小区”、“载波(carrier)”、“分量载波(component carrier)”、“带宽部分(bandwidth part，BWP)”等。
在一些实施例中，“终端(terminal)”或“终端设备(terminal device)”可以被称为“用户设备(user equipment，UE)”、“用户终端(user terminal)”、“移动台(mobile station，MS)”、“移动终端(mobile terminal，MT)”、订户站(subscriber station)、移动单元(mobile unit)、订户单元(subscriber unit)、无线单元(wireless unit)、远程单元(remote unit)、移动设备(mobile device)、无线设备(wireless device)、无线通信设备(wireless communication device)、远程设备(remote device)、 移动订户站(mobile subscriber station)、接入终端(access terminal)、移动终端(mobile terminal)、无线终端(wireless terminal)、远程终端(remote terminal)、手持设备(handset)、用户代理(user agent)、移动客户端(mobile client)、客户端(client)等。
在一些实施例中，获取数据、信息等可以遵照所在地国家的法律法规。
在一些实施例中，可以在得到用户同意后获取数据、信息等。
图1是根据本公开实施例示出的通信系统的架构示意图。该通信系统可包括但不限于一个终端和一个网络设备，图1所示的设备数量和形态仅用于举例并不构成对本公开实施例的限定，实际应用中可以包括两个或两个以上的终端，两个或两个以上的网络设备终端。图1所示的通信系统100以包括一个终端101和一个网络设备102为例。
在一些实施例中，本文中的终端101可以是用户侧的一种用于接收或发射信号的实体，如手机。也可以称为终端(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等。终端可以是具备通信功能的汽车、智能汽车、手机(mobile phone)、穿戴式设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self-driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等中的至少一者。本公开的实施例对终端所采用的具体技术和具体设备形态不做限定。
在一些实施例中，网络设备102可以是接入网设备。在一些实施例中，接入网设备例如是将终端接入到无线网络的节点或设备，接入网设备可以包括5G通信系统中的演进节点B(evolved NodeB，eNB)、下一代演进节点B(next generation eNB，ng-eNB)、下一代节点B(next generation NodeB，gNB)、节点B(node B，NB)、家庭节点B(home node B，HNB)、家庭演进节点B(home evolved nodeB，HeNB)、无线回传设备、无线网络控制器(radio network controller，RNC)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、基带单元(base band unit，BBU)、移动交换中心、6G通信系统中的基站、开放型基站(Open RAN)、云基站(Cloud RAN)、其他通信系统中的基站、Wi-Fi系统中的接入节点中的至少一者，但不限于此。
在一些实施例中，本公开的技术方案可适用于Open RAN架构，此时，本公开实施例所涉及的接入网设备间或者接入网设备内的接口可变为Open RAN的内部接口，这些内部接口之间的流程和信息交互可以通过软件或者程序实现。
在一些实施例中，接入网设备可以由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将接入网设备的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU，但不限于此。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提出的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新 业务场景的出现，本公开实施例提出的技术方案对于类似的技术问题同样适用。
下述本公开实施例可以应用于图1所示的通信系统100、或部分主体，但不限于此。图1所示的各主体是例示，通信系统可以包括图1中的全部或部分主体，也可以包括图1以外的其他主体，各主体数量和形态为任意，各主体可以是实体的也可以是虚拟的，各主体之间的连接关系是例示，各主体之间可以不连接也可以连接，其连接可以是任意方式，可以是直接连接也可以是间接连接，可以是有线连接也可以是无线连接。
本公开各实施例可以应用于长期演进(Long Term Evolution，LTE)、LTE-Advanced(LTE-A)、LTE-Beyond(LTE-B)、SUPER 3G、IMT-Advanced、第四代移动通信系统(4th generation mobile communication system，4G)、)、第五代移动通信系统(5th generation mobile communication system，5G)、5G新空口(new radio，NR)、未来无线接入(Future Radio Access，FRA)、新无线接入技术(New-Radio Access Technology，RAT)、新无线(New Radio，NR)、新无线接入(New radio access，NX)、未来一代无线接入(Future generation radio access，FX)、Global System for Mobile communications(GSM(注册商标))、CDMA2000、超移动宽带(Ultra Mobile Broadband，UMB)、IEEE 802.11(Wi-Fi(注册商标))、IEEE 802.16(WiMAX(注册商标))、IEEE 802.20、超宽带(Ultra-WideBand，UWB)、蓝牙(Bluetooth(注册商标))、陆上公用移动通信网(Public Land Mobile Network，PLMN)网络、设备到设备(Device-to-Device，D2D)系统、机器到机器(Machine to Machine，M2M)系统、物联网(Internet of Things，IoT)系统、车联网(Vehicle-to-Everything，V2X)、利用其他通信方法的系统、基于它们而扩展的下一代系统等。此外，也可以将多个系统组合(例如，LTE或者LTE-A与5G的组合等)应用。
在一些实施例中，终端与终端之间直接通信的链路，终端与终端之间的接口为PC-5。根据发送和接收终端的对应关系，在Sidelink上支持三种传输方式，单播，组播和广播。发送终端在物理侧行链路控制信道(Physical Sidelink Control Channel，PSCCH)上发送侧行链路控制信息(Sidelink Control Information，SCI)以及在物理侧行链路共享信道(Physical Sidelink Shared Channel，PSSCH)信道上发送第二阶段SCI，其中携带传输数据的资源位置以及源和目标标识等。对于混合自动重传请求(Hybrid Automatic Repeat Request，HARQ)反馈使能的数据包，接收终端在物理侧行链路反馈信道(Physical Sidelink Feedback Channel，PSFCH)上对PSSCH做混合自动重传请求确认(Hybrid Automatic Repeat Request-Acknowledgement，HARQ-ACK)反馈。
在一些实施例中，Sidelink通信有两种发送资源分配方式，一种是网络动态调度的方式(mode 1)，另一种是终端在网络配置或者预配置的资源池中自主选择的方式(mode 2)。其中动态调度是网络根据终端的缓存数据上报，动态给终端分配Sidelink上的发送资源，而自主选择是终端自行在网络配置或者预配置的资源池中随机选择发送资源。网络可以在一个BWP(Bandwidth Part，带宽部分)上给终端配置多个资源池。具体使用哪种分配方式是网络侧通过RRC(Radio Resource Control，无线资源控制)信令配置的。
载波聚合是LTE-A中的关键技术。为了满足单用户峰值速率和系统容量提升的要求，一种最直接的办法就是增加系统传输带宽。因此LTE-Advanced系统引入一项增加传输带宽的技术，也就是CA(Carrier  Aggregation，载波聚合)。CA技术可以将多个载波(ComponentCarrier，CC)聚合在一起，有效提高了上下行传输速率。可选的，参与载波聚合的每一个载波，也可以叫做分量载波(Component Carrier，简称CC)。
在一些实施例中，发送终端MAC(Media Access Control，媒体接入控制)层的复用功能将多个逻辑信道的数据装入一个传输信道，即将多个MAC SDU(MAC Service Data Unit，媒体接入控制服务数据单元)复用到一个MAC PDU(MAC Protocol Data Unit，媒体接入控制协议数据单元)内，通过物理层信道发送出去。当多个逻辑信道都有数据发送，且数据总量超过当前授权的传输能力时，就出现了应该让哪个逻辑信道优先发送的问题，称为逻辑信道优先级处理(Logical Channel Prioritization，也叫LCP)。每个逻辑信道都有一个优先级用于逻辑信道调度，这个优先级是由网络配置的，网络根据逻辑信道承载数据的QoS(Quality of Service，服务质量)为这个逻辑信道配置优先级。当终端得到调度机会，即得到某个载波上的侧行传输数据的资源后，终端首先选择目标地址，然后选择属于目标地址并且满足一些条件的SL LCH(SidelinkLogical Channel，侧行链路逻辑信道)复用到SL MAC PDU(SidelinkMAC Protocol Data Unit，侧行链路媒体接入控制协议数据单元)里。
在一些实施例中，NR(New Radio，新空口)Sidelink对于广播和/或组播业务，高层(如V2X(vehicle to everything，车用无线通信技术)层)会给AS(access stratum，接入层)层提供Service(业务)到frequency(载波/频带)的映射关系，高层会给AS层提供Service到目的层2ID(Destination L2ID)的映射关系。AS层可以根据这两个映射关系得到层2ID到frequency的映射关系。
在一些实施例中，网络设备可以配置给终端支持的frequency列表。对于载波聚合场景下，该列表中可以包括一个或多个entry(条目)，每个entry关联一个frequency。
在一些实施例中，对于一个目标层2地址，终端通过高层配置和网络配置的交集确定可以使用的frequency(载波/频带)。
LTE V2X就已经支持了侧行链路载波聚合技术，接收终端由于发送接收能力限制，可能只能在某一个或者某几个载波上接收侧行链路业务，发送终端由于发送能力受限，可能只在某一个或者几个载波上发送侧行链路业务，LTE V2X里针对终端受限的发送/接收能力没有引入任何载波选择/重选的增强方案，理由是LTE V2X只支持广播业务，可以依赖高层实现确定对哪个业务感兴趣并只在感兴趣的业务关联的载波上接收数据。
NR sidelink也支持载波聚合。相关技术中，NR sidelink载波聚合场景下，默认的是支持载波聚合的终端支持在所有载波上收发。但是，这种方式没有考虑受限的终端能力，即存在受限的接收终端能力对LCP过程的影响不清楚的问题，可能导致数据传输质量变差。
为此，本公开实施例提供一种侧行链路通信方法及其装置，可以解决受限的接收终端能力对LCP过程的影响不清楚的问题，提高传输速率，并保障数据传输质量。
图2A是根据本公开实施例示出的侧行链路通信方法的交互示意图。如图2A所示，本公开实施例涉及信息处理方法可应用于通信系统100，上述方法包括但不限于如下步骤。
步骤S2101，网络设备102发送第一配置信息。
在一些实施例中，网络设备102向终端101发送第一配置信息。可选的，终端101获取网络设备102配置的第一配置信息。
在一些实施例中，终端101可以通过专用RRC信令获取网络设备102配置的第一配置信息。示例性的，终端101处于RRC连接态，终端101可以通过专用RRC信令获取网络设备102配置的第一配置信息。其中，终端101的侧行链路发送资源分配方式可以是网络动态调度分配方式(如上述mode 1)，或者，也可以是终端自主选择分配方式(如上述mode 2)。
在一些实施例中，上述第一配置信息包含在SIB(System Information Block，系统消息块)中，示例性的，上述第一配置信息可以包含在SIB12中，终端101可以通过SIB获取网络设备102配置的第一配置信息。示例性的，终端101处于RRC连接态(RRC_CONNECTED)/RRC空闲态(RRC_IDLE)/RRC非激活态(RRC_INACTIVE)，终端101通过SIB获取网络设备102配置的第一配置信息。可选的，终端101的侧行链路发送资源分配方式可以是网络动态调度分配方式(如上述mode 1)或者，也可以是终端自主选择分配方式(如上述mode 2)。
在一些实施例中，上述第一配置信息包含在预配置信息中，终端101可以通过预配置信息获取网络设备102配置的第一配置信息。示例性的，终端101处于OOC(Out Of Coverage，覆盖范围外)态，终端101通过预配置信息获取网络设备102配置的第一配置信息。可选的，终端101的侧行链路发送资源分配方式可以是网络动态调度分配方式(如上述mode 1)。
在一些实施例中，上述第一配置信息包含频带/载波列表，该频带/载波列表包含至少一个频带/载波，在一些实施例中，上述第一配置信息用于终端101确定侧行链路通信使用的频带/载波，示例性的，上述第一配置信息用于终端101确定侧行链路通信发送和/或接收的频带/载波，示例性的，终端101基于至少一个目标地址支持的用于SL数据接收和/或发送的载波确定终端101发送的SL MAC PDU的第一目标地址，和/或确定上述SL MAC PDU包含的逻辑信道。其中，上述第一目标地址支持在侧行链路授权关联的载波上进行SL数据接收。
在一些实施例中，“载波”、“频段”、“频带”、“频率”等术语可以相互替换。
在一些实施例中，上述载波列表也可以称为载波集合，示例性的，网络设备102配置了支持的一个或者多个载波，多个载波可以说是列表也可以说是集合。
在一些实施例中，至少一个目标地址包括第二目标地址，该第二目标地址关联的业务类型为单播业务。在一些实施例中，至少一个目标地址包括第三目标地址，该第三目标地址关联的业务类型为组播业务和/或广播业务。
可选的，上述目标地址可理解为与终端101存在业务关系的目标地址，其中，该目标地址可能包括与终端101存在单播业务的第二目标地址，示例性的，第二目标地址可以是与终端101存在单播连接的任意一个目标地址；也可能包括终端101关联的广播和/或组播业务的第三目标地址，示例性的，第三目标地址可以是终端101感兴趣发送和/或接收的广播和/或组播业务的目标地址。在这种情况下，终端101有待发送数据时，需要进行LCP过程。终端101在LCP过程中，首先需要从至少一个目标地址中确定出终端101发送的SL MAC PDU的第一目标地址和/或确定该SL MAC PDU包含的逻辑信道。
在一些实施例中，终端101在进行LCP过程时，需要结合目标地址受限的接收能力，以使得选择出的目标地址支持侧行链路授权关联的载波上进行SL数据接收。
步骤S2102，终端101接收第二目标地址发送的能力信息。
在一些实施例中，第二目标地址发送能力信息。终端101接收第二目标地址发送的能力信息。
在一些实施例中，第二目标地址可以包含于上述至少一个目标地址。可选的，上述目标地址可理解为与终端101存在业务关系的目标地址，其中，该目标地址可能包括与终端101存在单播业务的第二目标地址。示例性的，第二目标地址可以是与终端101存在单播连接的任意一个目标地址。对于单播场景，终端101可以与第二目标地址交互终端能力，以告知对端支持的用于SL数据接收和/或发送的载波。示例性，对于单播场景，终端101作为发送终端，可以向第二目标地址发送终端101的能力信息，以告知第二目标地址该终端101支持的用于SL数据接收和/或发送的载波。第二目标地址作为接收终端，第二目标地址向终端101发送能力信息，该能力信息可以包括支持SL数据接收和/或发送的载波，终端101可以通过第二目标地址发送的能力信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波。
在一些实施例中，终端101可以通过侧行链路信息接收第二目标地址发送的能力信息。示例性的，终端101可以通过SCI接收第二目标地址发送的能力信息。
在一些实施例中，终端101可以通过PC5-RRC信令获取上述第二目标地址发送的能力信息。或者还可以通过其他方式接收第二目标地址发送的能力信息，在此本公开对此不做具体限定，也不再赘述。
步骤S2103，针对侧行链路授权，终端101确定至少一个目标地址支持的用于SL数据接收和/或发送的载波。示例性的，终端101确定至少一个目标地址支持接收和/或发送SL数据的载波。在本公开中，支持的用于SL数据接收和/或发送的载波可理解为支持接收和/或发送SL数据的载波。
在一些实施例中，上述至少一个目标地址可以包括第二目标地址，上述第二目标地址关联的业务类型为单播业务。可选的，上述目标地址可理解为与终端101存在业务关系的目标地址，其中，该目标地址可能包括与终端101存在单播业务的第二目标地址。示例性的，第二目标地址可以是与终端101存在单播连接的任意一个目标地址。针对单播业务场景，在LCP过程，终端101可以基于第二目标地址发送的能力信息和/或网络设备配置的第一配置信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波，其中，第一配置信息包括终端支持的载波列表。针对单播业务场景，由于终端101可以接收到第二目标地址发送的能力信息，网络设也可以配置终端支持的载波列表，所以终端101在LCP过程中的目标地址选择阶段，可以先结合第二目标地址发送的能力信息和/或网络设备配置的第一配置信息，确定至少一个目标地址中第二目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第二目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据。
示例性的，终端101可以基于网络设备配置的第一配置信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波。或者，终端101基于第二目标地址发送的能力信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波。或者，终端101基于第二目标地址发送的能力信息和网络设备配置的第一配置信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第二目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据。
在一种可能的实现方式中，终端101基于第二目标地址发送的能力信息和网络设备配置的第一配置信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波的实现方式可包括：终端101基于网络设备配置的第一配置信息，确定终端101支持发送和/或接收的载波列表；基于第二目标地址发送的能力信息和终端101支持发送和/或接收的载波列表的交集，确定第二目标地址支持的用于SL数据接收和/或发送的载波。示例性的，终端101与终端103存在单播业务，以上述第二目标地址为终端103的地址为例，终端101可以基于网络设备102配置的第一配置信息，确定终端101支持发送和/或接收的载波列 表，即包括终端101和/或终端103支持SL数据接收和/或发送的载波，终端101基于终端103发送的能力信息和网络设配置的第一配置信息的交集，确定终端103支持的用于SL数据接收和/或发送的载波，即第二目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第二目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据。
在另一种可能的实现方式中，终端101基于第二目标地址发送的能力信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波的实现方式可包括：终端101基于第二目标地址发送的能力信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第二目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据。
在又一种可能的实现方式中，终端101基于网络设备配置的第一配置信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波的实现方式可包括：终端101基于网络设备配置的第一配置信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波。示例性的，终端101与终端103存在单播业务，以上述第二目标地址为终端103的地址为例，终端101可以基于网络设备102配置的第一配置信息，确定终端101支持发送和/或接收的载波列表，即包括终端101和/或终端103支持SL数据接收和/或发送的载波，从而终端101可以确定终端103支持的用于SL数据接收和/或发送的载波，即第二目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第二目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据。
在一些实施例中，上述至少一个目标地址可以包括第二目标地址，上述第二目标地址关联的业务类型为单播业务。可选的，上述目标地址可理解为与终端101存在业务关系的目标地址，其中，该目标地址可能包括与终端101存在单播业务的第二目标地址。示例性的，第二目标地址可以是与终端101存在单播连接的任意一个目标地址。针对单播业务场景，在LCP过程，终端101可以基于第二目标地址发送的能力信息、网络设备配置的第一配置信息和高层配置的第二配置信息中的至少一种，确定第二目标地址支持的用于SL数据接收和/或发送的载波，其中，第一配置信息包括终端支持的载波列表；第二配置信息包括第二业务到载波的映射关系和/或第二业务到第二目标地址的映射关系，该第二业务为单播业务。根据第二业务到载波的映射关系和/或第二业务到第二目标地址的映射关系，确定第二目标地址到载波的映射关系；基于第二目标地址到载波的映射关系，确定第二目标地址支持的用于SL数据接收和/或发送的载波。可选的，该第二目标地址支持的用于SL数据发送的载波可以指终端101发送第二目标地址关联的单播业务支持的载波，示例性的，确定终端101是否支持在所述侧行链路授权关联的载波上发送第二目标地址关联的单播业务。
示例性的，针对单播业务场景，在LCP过程，终端101可以基于网络设备配置的第一配置信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第二目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据和/或终端101是否支持在所述侧行链路授权关联的载波上发送第二目标地址关联的单播业务。或者，终端101基于第二目标地址发送的能力信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第二目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据和/或终端101是否支持在所述侧行链路授权关联的载波上发送第二目标地址关联的单播业务。或者，终端101基于第二目标地址发送的能力信息和网络设备配置的第一配置信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第二目标地址是否支 持在所述侧行链路授权关联的载波上接收SL数据和/或终端101是否支持在所述侧行链路授权关联的载波上发送第二目标地址关联的单播业务。或者，终端101可以基于高层配置的第二配置信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第二目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据和/或终端101是否支持在所述侧行链路授权关联的载波上发送第二目标地址关联的单播业务。或者，终端101可以基于第二目标地址发送的能力信息和高层配置的第二配置信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第二目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据和/或终端101是否支持在所述侧行链路授权关联的载波上发送第二目标地址关联的单播业务。或者，终端101可以基于网络设备配置的第一配置信息和高层配置的第二配置信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第二目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据和/或终端101是否支持在所述侧行链路授权关联的载波上发送第二目标地址关联的单播业务。或者，终端101基于第二目标地址发送的能力信息、网络设备配置的第一配置信息和高层配置的第二配置信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第二目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据和/或终端101是否支持在所述侧行链路授权关联的载波上发送第二目标地址关联的单播业务。
在一些实施例中，至少一个目标地址包括第三目标地址，第三目标地址关联的业务类型为组播业务或广播业务。终端101基于网络设备配置的第一配置信息和/或高层(如V2X层)配置的第二配置信息，确定第三目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第三目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据。可选的，上述目标地址可理解为与终端101存在业务关系的目标地址，其中，该目标地址可能包括终端101关联的广播和/或组播业务的第三目标地址，示例性的，终端101感兴趣发送和/或接收的广播和/或组播业务的第三目标地址。针对广播和/或组播业务场景，在LCP过程，终端101可以基于网络设备配置的第一配置信息和/或高层配置的第二配置信息，确定第三目标地址支持的用于SL数据接收和/或发送的载波。其中，第一配置信息包括终端支持的载波列表；第二配置信息包括第一业务到载波的映射关系和/或第一业务到第三目标地址的映射关系。具体的，第三目标地址支持的用于SL数据接收和/或发送的载波，是指终端101发送第三目标地址关联的广播和/或组播业务的载波，和/或终端101接收第三目标地址关联的广播和/或组播业务的载波。
示例性的，终端101可以基于高层配置的第二配置信息，确定第三目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第三目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据和/或终端101是否支持在所述侧行链路授权关联的载波上发送第三目标地址关联的广播/组播业务。或者，终端101可以基于网络设备配置的第一配置信息确定第三目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第三目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据和/或终端101是否支持在所述侧行链路授权关联的载波上发送第三目标地址关联的广播/组播业务。或者，终端101可以基于网络设备配置的第一配置信息和高层配置的第二配置信息，确定第三目标地址支持的用于SL数据接收和/或发送的载波，示例性的，确定第三目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据和/或终端101是否支持在所述侧行链路授权关联的载波上发送第三目标地址关联的广播/组播业务。
在一种实现方式中，终端101基于高层配置的第二配置信息，确定第三目标地址支持的用于SL数据接收和/或发送的载波的实现方式可包括：终端101基于第二配置信息，确定第一业务到载波的映射关系和/或第一业务到第三目标地址的映射关系，其中，第一业务包括组播业务和/或广播业务；根据第一业务到载波的映射关系和/或第一业务到第三目标地址的映射关系，确定第三目标地址到载波的映射关系；基于第三目标地址到载波的映射关系，确定第三目标地址支持的用于SL数据接收和/或发送的载波。示例性的，确定第三目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据和/或终端101是否支持在所述侧行链路授权关联的载波上发送第三目标地址关联的广播/组播业务。
示例性的，终端101高层可以提供第一业务到载波的映射关系，终端101高层还可以提供第一业务到第三目标地址的映射关系。终端101可以根据第一业务到载波的映射关系和第一业务到第三目标地址的映射关系，确定第三目标地址到载波的映射关系，从而可以确定第三目标地址支持的用于SL数据接收和/或发送的载波。示例性的，确定第三目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据和/或终端101是否支持在所述侧行链路授权关联的载波上发送第三目标地址关联的广播/组播业务。
在另一种实现方式中，终端101基于网络设备配置的第一配置信息和高层配置的第二配置信息，确定第三目标地址支持的用于SL数据接收和/或发送的载波的实现方式可包括：终端101基于第一配置信息和第二配置信息的交集，确定第三目标地址支持的用于接收和/或发送数据的载波。示例性的，确定第三目标地址是否支持在所述侧行链路授权关联的载波上接收SL数据和/或终端101是否支持在所述侧行链路授权关联的载波上发送第三目标地址关联的广播/组播业务。举例而言，终端101基于网络设备配置的第一配置信息，确定终端101支持SL数据接收和/或发送的载波列表为载波1、载波2，基于高层配置的第二配置信息，确定第三目标地址支持SL数据接收和/或发送的载波为载波1、载波2和载波3，终端101可以基于网络设备配置的第一配置信息和高层配置的第二配置信息的交集，确定第三目标地址支持的用于SL数据接收和/或发送的载波为载波1和载波2。由此，在LCP过程中，考虑结合受限的发送和/或接收能力进行SL MAC PDU的目标地址的选择，可以解决NR sidelink载波聚合场景下，受限的发送和/或接收能力对LCP过程的影响不清楚的问题。
步骤S2104，终端101基于上述至少一个目标地址支持的用于SL数据接收和/或发送的载波，从上述至少一个目标地址中确定终端101发送的SL MAC PDU的第一目标地址，和/或确定上述SL MAC PDU包含的逻辑信道。
其中，在一些实施例中，上述第一目标地址支持在上述侧行链路授权关联的载波上进行SL数据接收。
其中，在一些实施例中，上述第一目标地址满足第一条件。
在一些实施例中，上述第一目标地址支持在上述侧行链路授权关联的载波上进行SL数据接收并且上述第一目标地址满足第一条件。
在一些实施例中，上述第一条件可以包括以下任意一种或多种：
条件a：侧行链路的非连续接收SL DRX适用于第一目标地址，侧行链路授权处于第一目标地址的激活时间，侧行链路授权用于发送SL MAC PDU；
条件b：第一目标地址在至少一个第一逻辑信道和/或第一媒体接入控制层控制单元MAC CE中具有至少一个最高优先级的逻辑信道或者MAC CE，其中，第一逻辑信道和/或第一MAC CE满足第二条 件。
可选的，在一些实施例中，上述第二条件包括以下任意一种或多种：
具有等待发送的SL数据；
第一逻辑信道有SBj(侧行链路发送缓冲器的令牌)，SBj>0；
侧行链路授权是配置授权类型1，第一逻辑信道关联的允许sl-configuredGrantType1Allowed(侧行链路配置授权类型1)参数配置允许逻辑信道的MAC SDU在配置授权类型1上传输；
配置了允许使用的配置授权的列表，列表包含了侧行链路授权关联的配置授权标识；
侧行链路授权没有关联的PSFCH资源，第一逻辑信道的HARQ属性是HARQ-disabled(HARQ去使能)；
配置了支持在上述侧行链路授权关联的载波上发送。
示例性的，可以基于高层配置的上述第二配置信息，确定终端101是否支持在所述侧行链路授权关联的载波上发送第一目标地址关联的SL数据。示例性的，第一目标地址可以是关联了单播业务的第二目标地址中的一个目标地址，也可以是关联了广播/组播业务的第三目标地址中的一个目标地址。
示例性的，可以基于网络设备的上述第一配置信息，确定终端101是否支持在所述侧行链路授权关联的载波上发送第一目标地址关联的SL数据。第一目标地址可以是关联了单播业务的第二目标地址中的一个目标地址，也可以是关联了广播/组播业务的第三目标地址中的一个目标地址。
示例性的，可以基于网络设备的上述第一配置信息和高层配置的上述第二配置信息，确定终端101是否支持在所述侧行链路授权关联的载波上发送第一目标地址关联的SL数据。第一目标地址可以是关联了单播业务的第二目标地址中的一个目标地址，也可以是关联了广播/组播业务的第三目标地址中的一个目标地址。
在一些实施例中，终端101可以基于至少一个目标地址支持的用于SL数据接收和/或发送的载波和/或上述第一条件，从至少一个目标地址确定终端发送的SL MAC PDU的第一目标地址。示例性的，终端101可以基于至少一个目标地址支持的用于SL数据接收和/或发送的载波和上述第一条件，从至少一个目标地址确定终端发送的SL MAC PDU的第一目标地址。
也就是说，终端101可以基于上述第一条件和至少一个目标地址支持的用于SL数据接收和/或发送的载波，从至少一个目标地址中选择SL MAC PDU的第一目标地址，所选择的第一目标地址中满足上述第一条件，且所述第一目标地址在满足上述第二条件的逻辑信道和/或媒体接入控制层控制单元MAC CE中具有至少一个最高优先级的逻辑信道或者MAC CE。
在一些实施例中，终端101确定SL MAC PDU包含的逻辑信道的实现方式可包括：终端101从属于第一目标地址的逻辑信道中，选择满足第三条件的逻辑信道；将满足第三条件的逻辑信道复用到SL MAC PDU中。
可选的，在一些实施例中，上述第三条件包括以下任意一种或多种：
1)选择的逻辑信道有SL数据可发送；且，
2)选择的逻辑信道的sl-configuredGrantType1Allowed参数被配置，在侧行链路授权是配置授权类型1的情况下，sl-configuredGrantType1Allowed参数设置为真；且，
3)选择的逻辑信道的允许侧行链路上行免授权列表SL-allowedcg–list被配置，SL-allowedcg–list包 括与侧行链路授权相关联的配置授权索引；且，
4)选择的逻辑信道的侧行链路混合自动重传请求反馈使能sl-HARQ-FeedbackEnabled设置为满足以下条件的值：
A)与侧行链路控制信息SCI关联的侧链授权配置了PSFCH，并且终端接收PSFCH：
I)已经选择的至少一个逻辑信道中优先级最高的逻辑信道对应的sl-HARQ-FeedbackEnabled为使能，下一个选择的逻辑信道的sl-HARQ-FeedbackEnabled为使能；或者，
II)已经选择的至少一个逻辑信道中优先级最高的逻辑信道对应的sl-HARQ-FeedbackEnabled设置为去使能，下一个选择的逻辑信道的sl-HARQ-FeedbackEnabled为去使能；
B)与SCI关联的侧链授权未配置PSFCH，和/或，终端不接收PSFCH：
选择的逻辑信道的sl-HARQ-FeedbackEnabled设置为不使能；
5配置了支持在侧行链路授权关联的载波上发送(isallowedonthecarrier/frequencyassociated/oftheSL grant,if configured)。
示例性的，可以基于高层配置的上述第二配置信息，确定终端101是否支持在所述侧行链路授权关联的载波上发送第一目标地址关联的SL数据。示例性的，第一目标地址可以是关联了单播业务的第二目标地址中的一个目标地址，也可以是关联了广播/组播业务的第三目标地址中的一个目标地址。
示例性的，可以基于网络设备的上述第一配置信息，确定终端101是否支持在所述侧行链路授权关联的载波上发送第一目标地址关联的SL数据。第一目标地址可以是关联了单播业务的第二目标地址中的一个目标地址，也可以是关联了广播/组播业务的第三目标地址中的一个目标地址。
示例性的，可以基于网络设备的上述第一配置信息和高层配置的上述第二配置信息，确定终端101是否支持在所述侧行链路授权关联的载波上发送第一目标地址关联的SL数据。第一目标地址可以是关联了单播业务的第二目标地址中的一个目标地址，也可以是关联了广播/组播业务的第三目标地址中的一个目标地址。
也就是说，终端101可以基于上述第一条件和至少一个目标地址支持的用于SL数据接收和/或发送的载波，从至少一个目标地址中选择SL MAC PDU的第一目标地址，并从属于第一目标地址的逻辑信道中，选择满足上述第三条件的逻辑信道，将满足上述第三条件的逻辑信道复用到上述SL MAC PDU中，以完成该SL MAC PDU的组包。可选的，终端101可以在侧行链路授权关联的载波上发送该SL MAC PDU。该SL MAC PDU的目标接收终端(即上述第一目标地址)可以在侧行链路授权关联的载波上接收该SL MAC PDU。
步骤S2105，终端101向上述第一目标地址发送SCI。
其中，在一些实施例中，上述侧行链路授权关联的载波为上述SCI传输所在的载波，或者，上述侧行链路授权关联的载波为上述SCI指示的PSSCH所在的载波。
示例性的，在非跨载波调度的情况下，侧行链路授权关联的载波就是SCI传输所在的载波。
示例性的，在跨载波调度的情况下，侧行链路授权关联的载波就是SCI指示的PSSCH所在的载波。
在一些实施例中，信息等的名称不限定于实施例中所记载的名称，“信息(information)”、“消息(message)”、“信号(signal)”、“信令(signaling)”、“报告(report)”、“配置(configuration)”、“指示(indication)”、“指令(instruction)”、“命令(command)”、“信道”、“参数(parameter)”、 “域”、“字段”、“符号(symbol)”、“码元(symbol)”、“码本(codebook)”、“码字(codeword)”、“码点(codepoint)”、“比特(bit)”、“数据(data)”、“程序(program)”、“码片(chip)”等术语可以相互替换。
在一些实施例中，“上行”、“上行链路”、“物理上行链路”等术语可以相互替换，“下行”、“下行链路”、“物理下行链路”等术语可以相互替换，“侧行(side)”、“侧行链路(sidelink)”、“侧行通信”、“侧行链路通信”、“直连”、“直连链路”、“直连通信”、“直连链路通信”等术语可以相互替换。
在一些实施例中，“获取”、“获得”、“得到”、“接收”、“传输”、“双向传输”、“发送和/或接收”可以相互替换，其可以解释为从其他主体接收，从协议中获取，从高层获取，自身处理得到、自主实现等多种含义。
在一些实施例中，“发送”、“发射”、“上报”、“下发”、“传输”、“双向传输”、“发送和/或接收”等术语可以相互替换。
在一些实施例中，“特定(certain)”、“预定(preseted)”、“预设”、“设定”、“指示(indicated)”、“某一”、“任意”、“第一”等术语可以相互替换，“特定A”、“预定A”、“预设A”、“设定A”、“指示A”、“某一A”、“任意A”、“第一A”可以解释为在协议等中预先规定的A，也可以解释为通过设定、配置、或指示等得到的A，也可以解释为特定A、某一A、任意A、或第一A等，但不限于此。
在一些实施例中，判定或判断可以通过以1比特表示的值(0或1)来进行，也可以通过以真(true)或者假(false)表示的真假值(布尔值(boolean))来进行，也可以通过数值的比较(例如，与预定值的比较)来进行，但不限于此。
本公开实施例所涉及的方法可以包括步骤S2101～步骤S2105中的至少一者。例如，步骤S2103+步骤S2104可以作为独立实施例来实施，步骤S2101+步骤S2103+步骤S2104可以作为独立实施例来实施，步骤S2102+步骤S2103+步骤S2104可以作为独立实施例来实施，步骤S2101+步骤S2102+步骤S2103+步骤S2104可以作为独立实施例来实施，步骤S2103+步骤S2104+步骤S2105可以作为独立实施例来实施，步骤S2101+步骤S2103+步骤S2104+步骤S2105可以作为独立实施例来实施，步骤S2102+步骤S2103+步骤S2104+步骤S2105可以作为独立实施例来实施，步骤S2101+步骤S2102+步骤S2103+步骤S2104+步骤S2105可以作为独立实施例来实施，但不限于此。
在一些实施例中，步骤S2101、步骤S2102可以交换顺序或同时执行。
在一些实施例中，步骤S2101、步骤S2102、步骤S2105是可选地，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2102、步骤S2105是可选地，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2101、步骤S2105是可选地，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2105是可选地，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2101、步骤S2102是可选地，在不同实施例中可以对这些步骤中的一个或 多个步骤进行省略或替代。
在一些实施例中，步骤S2101是可选地，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2102是可选地，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，可参见图2A所对应的说明书之前或之后记载的其他可选实现方式。
图3A是根据本公开实施例示出的一种侧行链路通信方法的流程示意图。如图3A所示，本公开实施例涉及侧行链路通信方法，该方法可由终端101执行，上述方法可以包括但不限于如下步骤。
步骤S3101，接收第一配置信息。
在一些实施例中，终端101接收网络设备102发送的第一配置信息。可选的，网络设备102发送第一配置信息，终端101接收网络设备102发送的第一配置信息。
在一些实施例中，上述第一配置信息包含在SIB(System Information Block，系统消息块)中，终端101可以通过SIB获取网络设备102配置的第一配置信息。示例性的，终端101处于RRC空闲态(RRC_IDLE)/RRC非激活态(RRC_INACTIVE)，终端101通过SIB获取网络设备102配置的第一配置信息。可选的，终端101的侧行链路发送资源分配方式可以是网络动态调度分配方式(如上述mode1)。
在一些实施例中，上述第一配置信息包含在预配置信息中，终端101可以通过预配置信息获取网络设备102配置的第一配置信息。示例性的，终端101处于OOC态，终端101通过预配置信息获取网络设备102配置的第一配置信息。可选的，终端101的侧行链路发送资源分配方式可以是网络动态调度分配方式(如上述mode 1)。
在一些实施例中，上述第一配置信息用于终端101确定至少一个目标地址支持的用于SL数据接收和/或发送的载波，以使终端101基于至少一个目标地址支持的用于SL数据接收和/或发送的载波确定终端101发送的SL MAC PDU的第一目标地址，和/或确定上述SL MAC PDU包含的逻辑信道。其中，上述第一目标地址支持在侧行链路授权关联的载波上进行SL数据接收。
步骤S3101的可选实现方式可以参见图2的步骤S2101的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
步骤S3102，接收第二目标地址发送的能力信息。
在一些实施例中，上述能力信息可以包括支持SL数据接收和/或发送的载波。
步骤S3102的可选实现方式可以参见图2的步骤S2102的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
步骤S3103，针对侧行链路授权，确定至少一个目标地址支持的用于SL数据接收和/或发送的载波。
在一些实施例中，上述至少一个目标地址可以包括第二目标地址，上述第二目标地址关联的业务类型为单播业务。终端101可以基于第二目标地址发送的能力信息和/或网络设备配置的第一配置信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波。其的可选实现方式可以参见图2的步骤S2103的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，至少一个目标地址包括第三目标地址，第三目标地址关联的业务类型为组播业务或广播业务。基于网络设备配置的第一配置信息和/或高层(如V2X层)配置的第二配置信息，确定第三目标地址支持的用于SL数据接收和/或发送的载波。其的可选实现方式可以参见图2的步骤S2103的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
步骤S3104，基于上述至少一个目标地址支持的用于SL数据接收和/或发送的载波，从上述至少一个目标地址中确定终端101发送的SL MAC PDU的第一目标地址，和/或确定上述SL MAC PDU包含的逻辑信道。
步骤S3104的可选实现方式可以参见图2的步骤S2104的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
步骤S3105，向上述第一目标地址发送SCI。
其中，在一些实施例中，上述侧行链路授权关联的载波为上述SCI传输所在的载波，或者，上述侧行链路授权关联的载波为上述SCI指示的PSSCH所在的载波。
步骤S3105的可选实现方式可以参见图2的步骤S2105的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
本公开实施例所涉及的方法可以包括步骤S3101～步骤S3105中的至少一者。例如，步骤S3103+步骤S3104可以作为独立实施例来实施，步骤S3101+步骤S3103+步骤S3104可以作为独立实施例来实施，步骤S3102+步骤S3103+步骤S3104可以作为独立实施例来实施，步骤S3101+步骤S3102+步骤S3103+步骤S3104可以作为独立实施例来实施，步骤S3103+步骤S3104+步骤S3105可以作为独立实施例来实施，步骤S3101+步骤S3103+步骤S3104+步骤S3105可以作为独立实施例来实施，步骤S3102+步骤S3103+步骤S3104+步骤S3105可以作为独立实施例来实施，步骤S3101+步骤S3102+步骤S3103+步骤S3104+步骤S3105可以作为独立实施例来实施，但不限于此。
在一些实施例中，步骤S3101、步骤S3102可以交换顺序或同时执行。
在一些实施例中，步骤S3101、步骤S3102、步骤S3105是可选地，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S3102、步骤S3105是可选地，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S3101、步骤S3105是可选地，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S3105是可选地，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S3101、步骤S3102是可选地，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S3101是可选地，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S3102是可选地，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
图3B是根据本公开实施例示出的一种信息处理方法的流程示意图。如图3B所示，本公开实施例涉及信息处理方法，该方法可由终端101执行，上述方法可以包括但不限于如下步骤。
步骤S3201，针对侧行链路授权，确定至少一个目标地址支持的用于SL数据接收和/或发送的载波。
在一些实施例中，上述至少一个目标地址可以包括第二目标地址，上述第二目标地址关联的业务类型为单播业务。终端101确定至少一个目标地址支持的用于SL数据接收和/或发送的载波的可选的实现方式包括：接收第二目标地址发送的能力信息，能力信息包括支持SL数据接收和/或发送的载波；基于第二目标地址发送的能力信息和/或网络设备配置的第一配置信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波，其中，第一配置信息包括所述终端支持的载波列表。的可选实现方式可以参见图2的步骤S2103的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
在一种可能的实现方式中，终端101基于能力信息和/或网络设备配置的第一配置信息，确定第二目标地址支持的用于SL数据接收和/或发送的载波的实现方式可包括：基于网络设备配置的第一配置信息，确定终端支持的载波列表；基于能力信息和终端支持的载波列表的交集，确定第二目标地址支持的用于SL数据接收和/或发送的载波。
在一些实施例中，至少一个目标地址包括第三目标地址，第三目标地址关联的业务类型为组播业务或广播业务。终端101确定至少一个目标地址支持的用于SL数据接收和/或发送的载波的可选的实现方式包括：基于网络设备配置的第一配置信息和/或高层(如V2X层)配置的第二配置信息，确定第三目标地址支持的用于SL数据接收和/或发送的载波。其的可选实现方式可以参见图2的步骤S2103的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
在一种可能的实现方式中，终端101基于网络设备配置的第一配置信息和/或高层配置的第二配置信息，确定第三目标地址支持的用于SL数据接收和/或发送的载波的实现方式可包括：基于第二配置信息，确定第一业务到载波的映射关系和/或第一业务到第三目标地址的映射关系，其中，第一业务包括组播业务和/或广播业务；根据第一业务到载波的映射关系和/或第一业务到第三目标地址的映射关系，确定第三目标地址到载波的映射关系；基于第三目标地址到载波的映射关系，确定第三目标地址支持的用于SL数据接收和/或发送的载波。其的可选实现方式可以参见图2的步骤S2103的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
在一种可能的实现方式中，终端101基于网络设备配置的第一配置信息和/或高层配置的第二配置信息，确定第三目标地址支持的用于SL数据接收和/或发送的载波的实现方式可包括：基于第一配置信息和第二配置信息的交集，确定第三目标地址支持的用于接收数据的载波。其的可选实现方式可以参见图2的步骤S2103的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，上述第一配置信息包含在SIB或预配置信息中。
步骤S3202，基于至少一个目标地址支持的用于SL数据接收和/或发送的载波，从至少一个目标地址中确定终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定SL MAC PDU包含的逻辑信道。
其中，在一些实施例中，第一目标地址支持在侧行链路授权关联的载波上进行SL数据接收。
在一些实施例中，终端101基于至少一个目标地址支持的用于SL数据接收和/或发送的载波和/或第 一条件，从至少一个目标地址确定终端发送的SL MAC PDU的第一目标地址。
在一些实施例中，第一条件包括以下任意一种或多种：
侧行链路的非连续接收SL DRX适用于第一目标地址，侧行链路授权处于第一目标地址的激活时间，侧行链路授权用于发送SL MAC PDU；
第一目标地址在至少一个第一逻辑信道和/或第一媒体接入控制层控制单元MAC CE中具有至少一个最高优先级的逻辑信道或者MAC CE，其中，第一逻辑信道和/或第一MAC CE满足第二条件。
在一些实施例中，上述第二条件包括以下任意一种或多种：
具有等待发送的SL数据；
第一逻辑信道有侧行链路发送缓冲器的令牌SBj，SBj>0；
侧行链路授权是配置授权类型1，第一逻辑信道关联的允许侧行链路配置授权类型1sl-configuredGrantType1Allowed参数配置允许逻辑信道的媒体接入控制服务数据单元MAC SDU在配置授权类型1上传输；
配置了允许使用的配置授权的列表，列表包含了侧行链路授权关联的配置授权标识；
侧行链路授权没有关联的物理侧行链路反馈信道PSFCH资源，第一逻辑信道的混合自动重传请求HARQ属性是HARQ去使能HARQ-disabled；
配置了支持在侧行链路授权关联的载波上发送。
在一些实施例中，终端101确定SL MAC PDU包含的逻辑信道的实现方式可包括：从属于第一目标地址的逻辑信道中，选择满足第三条件的逻辑信道；将满足第三条件的逻辑信道复用到SL MAC PDU中。
在一些实施例中，上述第三条件包括以下任意一种或多种：
1)选择的逻辑信道有SL数据可发送；且，
2)选择的逻辑信道的sl-configuredGrantType1Allowed参数被配置，在侧行链路授权是配置授权类型1的情况下，sl-configuredGrantType1Allowed参数设置为真；且，
3)选择的逻辑信道的允许侧行链路上行免授权列表SL-allowedcg–list被配置，SL-allowedcg–list包括与侧行链路授权相关联的配置授权索引；且，
4)选择的逻辑信道的侧行链路混合自动重传请求反馈使能sl-HARQ-FeedbackEnabled设置为满足以下条件的值：
A)与侧行链路控制信息SCI关联的侧链授权配置了PSFCH，并且终端接收PSFCH：
I)已经选择的至少一个逻辑信道中优先级最高的逻辑信道对应的sl-HARQ-FeedbackEnabled为使能，下一个选择的逻辑信道的sl-HARQ-FeedbackEnabled为使能；或者，
II)已经选择的至少一个逻辑信道中优先级最高的逻辑信道对应的sl-HARQ-FeedbackEnabled设置为去使能，下一个选择的逻辑信道的sl-HARQ-FeedbackEnabled为去使能；
B)与SCI关联的侧链授权未配置PSFCH，和/或，终端不接收PSFCH：
选择的逻辑信道的sl-HARQ-FeedbackEnabled设置为不使能；
5)配置了支持在侧行链路授权关联的载波上发送(isallowedonthecarrier/frequencyassociated/oftheSL grant,if configured by upper layers)。
步骤S3202的可选实现方式可以参见图2的步骤S2104的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端101向第一目标地址发送SCI。其中，上述侧行链路授权关联的载波为上述SCI传输所在的载波，或者，上述侧行链路授权关联的载波为上述SCI指示的PSSCH所在的载波。其的可选实现方式可以参见图2的步骤S2105的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
图4A是根据本公开实施例示出的侧行链路通信方法的流程图。如图4A所示，本公开实施例涉及的方法可应用于网络设备102，上述方法包括但不限于如下步骤。
步骤S4101，发送第一配置信息。
在一些实施例中，上述第一配置信息是网络设备102给终端101配置的。网络设备102向终端101发送第一配置信息。可选的，终端101接收上述第一配置信息，如终端101接收网络设备101发送的上述第一配置信息。
在一些实施例中，上述第一配置信息用于终端101确定至少一个目标地址支持的用于SL数据接收和/或发送的载波，以使终端101基于上述至少一个目标地址支持的用于SL数据接收和/或发送的载波确定终端101发送的SL MAC PDU的第一目标地址，和/或确定上述SL MAC PDU包含的逻辑信道；其中，上述第一目标地址支持在侧行链路授权关联的载波上进行SL数据接收。其的可选实现方式可以参见图2的步骤S2103、步骤S2104的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
可选的，在一些实施例中，至少一个目标地址包括第二目标地址，所述第二目标地址关联的业务类型为单播业务；终端101基于第二目标地址发送的能力信息和/或网络设备102配置的第一配置信息，确定第二目标地址支持用于SL数据接收和/或发送的载波，其中，所述第一配置信息包括所述终端支持的载波列表。其的可选实现方式可以参见图2的步骤S2103的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
可选的，在一些实施例中，至少一个目标地址包括第三目标地址，所述第三目标地址关联的业务类型为组播业务或广播业务；终端101基于网络设备配置的第一配置信息和/或高层配置的第二配置信息，确定所述第三目标地址支持的用于SL数据接收和/或发送的载波。其的可选实现方式可以参见图2的步骤S2103的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
步骤S4101的可选实现方式可以参见图2的步骤S2101的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
图5是根据本公开实施例示出的侧行链路通信方法的交互示意图。如图5所示，本公开实施例涉及的方法可应用于通信系统100，上述方法包括但不限于如下步骤。
步骤S5101，网络设备102向终端101发送第一配置信息。
在一些实施例中，上述第一配置信息用于终端101确定至少一个目标地址支持的用于SL数据接收和/或发送的载波，以使终端101基于至少一个目标地址支持的用于SL数据接收和/或发送的载波确定终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定SL MAC PDU 包含的逻辑信道；其中，第一目标地址支持在侧行链路授权关联的载波上进行SL数据接收。
步骤S5101的可选实现方式可以参见图2的步骤S2101的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
步骤S5102，针对侧行链路授权，终端101确定至少一个目标地址支持的用于SL数据接收和/或发送的载波。
步骤S5102的可选实现方式可以参见图2的步骤S2103的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
步骤S5103，终端101基于至少一个目标地址支持的用于SL数据接收和/或发送的载波，从至少一个目标地址中确定终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定SL MAC PDU包含的逻辑信道。
步骤S5103的可选实现方式可以参见图2的步骤S2104的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，上述方法可以包括上述终端侧、网络设备侧等的实施例所述的方法，此处不再赘述。
需要说的是，在本公开的实施例中，LCP过程中发送终端在选择目标终端/地址时候，需要考虑目标终端在该侧行链路授权关联的载波上的接收能力。
需要说的是，在本公开的实施例中，LCP过程中发送终端在选择目标终端/地址的时候，需要考虑侧行链路逻辑信道是否支持在该侧行链路授权关联的载波上发送。
需要说的是，在本公开的实施例中，LCP在选择属于目标地址的侧行链路逻辑信道的时候，需要考虑侧行链路逻辑信道是否支持在该侧行链路授权关联的载波上发送。
在一些实施例中，LCP过程中发送终端选择的目标终端/地址(如上述第一目标地址)支持在该侧行链路授权关联的载波上接收。
在一种实现方式中，目标终端/地址支持在所述侧行链路授权关联的载波上接收。可选的，该实现方式(即目标终端/地址支持在所述侧行链路授权关联的载波上接收的方案示例)可以只适用于单播，示例性的，发送终端可以通过PC5-RRC信令获取对端终端(如上述第二目标地址关联的终端)支持接收的载波/频带，对端终端是跟发送终端存在单播连接的终端，本公开对如何获取这个信息不做具体限定。
可选的，该实现方式(即目标终端/地址支持在所述侧行链路授权关联的载波上接收的方案示例)可以既适用于单播也适用于组播和/或广播，示例性的，发送终端可以通过高层(V2X层)配置的第二配置信息和/或网络设备配置的第一配置信息获取组播和/或广播业务关联的目标层2地址(如上述第三目标地址)支持发送和/或接收的载波/频带，本公开对如何获取这个信息不做具体限定。
可选的，上述关联有两种含义，示例性的，在非跨载波调度的情况下，侧行链路授权关联的载波就是SCI传输所在的载波，在跨载波调度的情况下，侧行链路授权关联的载波就是SCI指示的PSSCH所在的载波。
在一些实施例中，LCP过程中发送终端选择的目标终端/地址关联的SL LCH支持在该侧行链路授权关联的载波上发送。
在一种实现方式中，所述目标终端/地址在所有满足下列条件(如上述第二条件)的逻辑信道和MAC CE中具有至少一个最高优先级的MAC CE或者逻辑信道：
具有待传的SL数据；
如果有任何逻辑信道有SBj，SBj>0；
如果所述侧行链路授权是配置授权类型1，逻辑信道关联的sl-configuredGrantType1Allowed配置允许逻辑信道的MAC SDU在配置授权类型1上传输；
如果配置了允许使用的配置授权的列表，所述列表包含了所述侧行链路授权关联的配置授权标识；
如果所述侧行链路授权没有关联的PSFCH资源，逻辑信道的HARQ属性是HARQ-disabled；
支持在侧行链路授权关联的载波上发送，如果高层和/或网络设备配置了。
其中，上述条件(如上述第二条件)可以适用于以下一种或多种：单播、组播、广播，示例性的，发送终端可以通过高层配置和/或网络设备配置获取单播和/或组播和/或广播业务关联的目标层2地址和/或目标层2地址关联的SL LCH支持发送的载波/频带，本公开对如何获取这个信息不做具体限定。
在一些实施例中，LCP在选择属于目标地址的侧行链路逻辑信道，支持在该侧行链路授权关联的载波上发送。
可选的，在选择属于目标地址的侧行链路逻辑信道，可以选择满足如下第三条件的逻辑信道，该选择的逻辑信道支持在该侧行链路授权关联的载波上发送。示例性的，第三条件包括以下任意一种或多种：
1)所述选择的逻辑信道有SL数据可发送；且，
2)所述选择的逻辑信道的sl-configuredGrantType1Allowed参数被配置，在所述侧行链路授权是所述配置授权类型1的情况下，所述sl-configuredGrantType1Allowed参数设置为真；且，
3)所述选择的逻辑信道的允许侧行链路上行免授权列表SL-allowedcg–list被配置，所述SL-allowedcg–list包括与所述侧行链路授权相关联的配置授权索引；且，
4)所述选择的逻辑信道的侧行链路混合自动重传请求反馈使能sl-HARQ-FeedbackEnabled设置为满足以下条件的值：
A)与侧行链路控制信息SCI关联的侧链授权配置了PSFCH，并且所述终端接收所述PSFCH：
I)已经选择的至少一个逻辑信道中优先级最高的逻辑信道对应的sl-HARQ-FeedbackEnabled为使能，下一个选择的逻辑信道的sl-HARQ-FeedbackEnabled为使能；或者，
II)已经选择的至少一个逻辑信道中优先级最高的逻辑信道对应的sl-HARQ-FeedbackEnabled设置为去使能，下一个选择的逻辑信道的sl-HARQ-FeedbackEnabled为去使能；
B)与SCI关联的侧链授权未配置PSFCH，和/或，所述终端不接收PSFCH：
所述选择的逻辑信道的sl-HARQ-FeedbackEnabled设置为不使能；
5)支持在侧行链路授权关联的载波上发送，如果高层和/或网络设备配置了。
可选的，上述第三条件可以适用于单播和/或组播和/或广播，示例性的，发送终端可以通过高层配置和/或网络设备配置获取单播和/或组播和/或广播业务关联的目标层2地址和/或目标层2地址关联的SL LCH支持发送的载波/频带，本公开对如何获取这个信息不做具体限定。
由此，本公开实施例可以解决NR Sidelink载波聚合场景下，受限的发送和/或接收终端能力对LCP过程的影响不清楚的问题
本公开实施例还提出用于实现以上任一方法的装置，例如，提出一装置，上述装置包括用以实现以上任一方法中终端所执行的各步骤的单元或模块。再如，还提出另一装置，包括用以实现以上任一方法中网络设备所执行的各步骤的单元或模块。
应理解以上装置中各单元或模块的划分仅是一种逻辑功能的划分，在实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。此外，装置中的单元或模块可以以处理器调用软件的形式实现：例如装置包括处理器，处理器与存储器连接，存储器中存储有指令，处理器调用存储器中存储的指令，以实现以上任一方法或实现上述装置各单元或模块的功能，其中处理器例如为通用处理器，例如中央处理单元(Central Processing Unit，CPU)或微处理器，存储器为装置内的存储器或装置外的存储器。或者，装置中的单元或模块可以以硬件电路的形式实现，可以通过对硬件电路的设计实现部分或全部单元或模块的功能，上述硬件电路可以理解为一个或多个处理器；例如，在一种实现中，上述硬件电路为专用集成电路(application-specific integrated circuit，ASIC)，通过对电路内元件逻辑关系的设计，实现以上部分或全部单元或模块的功能；再如，在另一种实现中，上述硬件电路为可以通过可编程逻辑器件(programmable logic device，PLD)实现，以现场可编程门阵列(Field Programmable Gate Array，FPGA)为例，其可以包括大量逻辑门电路，通过配置文件来配置逻辑门电路之间的连接关系，从而实现以上部分或全部单元或模块的功能。以上装置的所有单元或模块可以全部通过处理器调用软件的形式实现，或全部通过硬件电路的形式实现，或部分通过处理器调用软件的形式实现，剩余部分通过硬件电路的形式实现。
在本公开实施例中，处理器是具有信息处理能力的电路，在一种实现中，处理器可以是具有指令读取与运行能力的电路，例如中央处理单元(Central Processing Unit，CPU)、微处理器、图形处理器(graphics processing unit，GPU)(可以理解为微处理器)、或数字信息处理器(digital signal processor，DSP)等；在另一种实现中，处理器可以通过硬件电路的逻辑关系实现一定功能，上述硬件电路的逻辑关系是固定的或可以重构的，例如处理器为专用集成电路(application-specific integrated circuit，ASIC)或可编程逻辑器件(programmable logic device，PLD)实现的硬件电路,例如FPGA。在可重构的硬件电路中，处理器加载配置文档，实现硬件电路配置的过程，可以理解为处理器加载指令，以实现以上部分或全部单元或模块的功能的过程。此外，还可以是针对人工智能设计的硬件电路，其可以理解为ASIC，例如神经网络处理单元(Neural Network Processing Unit，NPU)、张量处理单元(Tensor Processing Unit，TPU)、深度学习处理单元(Deep learning Processing Unit，DPU)等。
图6A是本公开实施例提出的终端的结构示意图。如图6A所示，终端6100可以包括：收发模块6101、处理模块6102等中的至少一者。在一些实施例中，上述处理模块，用于针对侧行链路授权，确定至少一个目标地址支持的用于SL数据接收和/或发送的载波；处理模块，还用于基于至少一个目标地址支持的用于SL数据接收和/或发送的载波，从至少一个目标地址确定终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定SL MAC PDU包含的逻辑信道；其中，第一目标地址支持在侧行链路授权关联的载波上进行SL数据接收。可选地，上述收发模块用于执行以上任一方法中终端101执行的发送和/或接收等通信步骤(例如步骤S2102、步骤S2105，但不限于此)中的至少一者，此处不再赘述。可选地，上述处理模块用于执行以上任一方法中终端101执行的其他步骤(例如步 骤S2103、步骤S2104，但不限于此)中的至少一者，此处不再赘述。
图6B是本公开实施例提出的网络设备的结构示意图。如图6B所示，网络设备6200可以包括：收发模块6201、处理模块6202等中的至少一者。在一些实施例中，上述收发模块，用于向终端发送第一配置信息，第一配置信息用于终端确定至少一个目标地址支持的用于SL数据接收和/或发送的载波，以使终端基于至少一个目标地址支持的用于SL数据接收和/或发送的载波确定终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定SL MAC PDU包含的逻辑信道；其中，第一目标地址支持在侧行链路授权关联的载波上进行SL数据接收。可选地，上述收发模块用于执行以上任一方法中网络设备6200执行的发送和/或接收等通信步骤(例如步骤S2101，但不限于此)中的至少一者，此处不再赘述。可选地，上述处理模块用于执行以上任一方法中网络设备102执行的其他步骤中的至少一者，此处不再赘述。
在一些实施例中，收发模块可以包括发送模块和/或接收模块，发送模块和接收模块可以是分离的，也可以集成在一起。可选地，收发模块可以与收发器相互替换。
在一些实施例中，处理模块可以是一个模块，也可以包括多个子模块。可选地，上述多个子模块分别执行处理模块所需执行的全部或部分步骤。可选地，处理模块可以与处理器相互替换。
图7A是本公开实施例提出的通信设备7100的结构示意图。通信设备7100可以是终端，也可以是网络设备，也可以是支持终端实现以上任一方法的芯片、芯片系统、或处理器等，还可以是支持网络设备实现以上任一方法的芯片、芯片系统、或处理器等。通信设备7100可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
如图7A所示，通信设备7100包括一个或多个处理器7101。处理器7101可以是通用处理器或者专用处理器等，例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行程序，处理程序的数据。通信设备7100用于执行以上任一方法。
在一些实施例中，通信设备7100还包括用于存储指令的一个或多个存储器7102。可选地，全部或部分存储器7102也可以处于通信设备7100之外。
在一些实施例中，通信设备7100还包括一个或多个收发器7103。在通信设备7100包括一个或多个收发器7103时，收发器7103执行上述方法中的发送和/或接收等通信步骤(例如步骤S2101、步骤S2102、步骤S2105，但不限于此)中的至少一者，处理器7101执行其他步骤(例如步骤S2103、步骤S2104，但不限于此)中的至少一者。
在一些实施例中，收发器可以包括接收器和/或发送器，接收器和发送器可以是分离的，也可以集成在一起。可选地，收发器、收发单元、收发机、收发电路等术语可以相互替换，发送器、发送单元、发送机、发送电路等术语可以相互替换，接收器、接收单元、接收机、接收电路等术语可以相互替换。
在一些实施例中，通信设备7100可以包括一个或多个接口电路7104。可选地，接口电路7104与存储器7102连接，接口电路7104可用于从存储器7102或其他装置接收信号，可用于向存储器7102或其他装置发送信号。例如，接口电路7104可读取存储器7102中存储的指令，并将该指令发送给处理器7101。
以上实施例描述中的通信设备7100可以是终端或者网络设备，但本公开中描述的通信设备7100的范围并不限于此，通信设备7100的结构可以不受图7A的限制。通信设备可以是独立的设备或者可以是 较大设备的一部分。例如所述通信设备可以是：1)独立的集成电路IC，或芯片，或，芯片系统或子系统；(2)具有一个或多个IC的集合，可选地，上述IC集合也可以包括用于存储数据，程序的存储部件；(3)ASIC，例如调制解调器(Modem)；(4)可嵌入在其他设备内的模块；(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；(6)其他等等。
图7B是本公开实施例提出的芯片7200的结构示意图。对于通信设备7100可以是芯片或芯片系统的情况，可以参见图7B所示的芯片7200的结构示意图，但不限于此。
芯片7200包括一个或多个处理器7201，芯片7200用于执行以上任一方法。
在一些实施例中，芯片7200还包括一个或多个接口电路7202。可选地，接口电路7202与存储器7203连接，接口电路7202可以用于从存储器7203或其他装置接收信号，接口电路7202可用于向存储器7203或其他装置发送信号。例如，接口电路7202可读取存储器7203中存储的指令，并将该指令发送给处理器7201。
在一些实施例中，接口电路7202执行上述方法中的发送和/或接收等通信步骤(例如步骤S2101、步骤S2102、步骤S2105，但不限于此)中的至少一者，处理器7201执行其他步骤(例如步骤S2103、步骤S2104，但不限于此)中的至少一者。
在一些实施例中，接口电路、接口、收发管脚、收发器等术语可以相互替换。
在一些实施例中，芯片7200还包括用于存储指令的一个或多个存储器7203。可选地，全部或部分存储器7203可以处于芯片7200之外。
本公开还提出存储介质，上述存储介质上存储有指令，当上述指令在通信设备7100上运行时，使得通信设备7100执行以上任一方法。可选地，上述存储介质是电子存储介质。可选地，上述存储介质是计算机可读存储介质，但不限于此，其也可以是其他装置可读的存储介质。可选地，上述存储介质可以是非暂时性(non-transitory)存储介质，但不限于此，其也可以是暂时性存储介质。
本公开还提出程序产品，上述程序产品被通信设备7100执行时，使得通信设备7100执行以上任一方法。可选地，上述程序产品是计算机程序产品。
本公开还提出计算机程序，当其在计算机上运行时，使得计算机执行以上任一方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本公开实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (19)

  1. 一种侧行链路通信方法，其特征在于，包括：
    针对侧行链路授权，终端确定至少一个目标地址支持的用于侧行链路SL数据接收和/或发送的载波；
    基于所述至少一个目标地址支持的用于SL数据接收和/或发送的载波，从所述至少一个目标地址中确定所述终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定所述SL MAC PDU包含的逻辑信道；
    其中，所述第一目标地址支持在所述侧行链路授权关联的载波上进行SL数据接收。
  2. 如权利要求1所述的方法，其特征在于，所述至少一个目标地址包括第二目标地址，所述第二目标地址关联的业务类型为单播业务；
    所述终端确定至少一个目标地址支持的用于SL数据接收和/或发送的载波，包括：
    接收所述第二目标地址发送的能力信息，所述能力信息包括支持SL数据接收和/或发送的载波；
    基于所述能力信息和/或网络设备配置的第一配置信息，确定所述第二目标地址支持的用于SL数据接收和/或发送的载波，其中，所述第一配置信息包括所述终端支持的载波列表。
  3. 如权利要求2所述的方法，其特征在于，所述基于所述能力信息和/或网络设备配置的第一配置信息，确定所述第二目标地址支持的用于SL数据接收和/或发送的载波，包括：
    基于所述网络设备配置的第一配置信息，确定所述终端支持的载波列表；
    基于所述能力信息和所述终端支持的载波列表的交集，确定所述第二目标地址支持的用于SL数据接收和/或发送的载波。
  4. 如权利要求1所述的方法，其特征在于，所述至少一个目标地址包括第三目标地址，所述第三目标地址关联的业务类型为组播业务或广播业务；
    所述终端确定至少一个目标地址支持的用于SL数据接收和/或发送的载波，包括：
    基于网络设备配置的第一配置信息和/或高层配置的第二配置信息，确定所述第三目标地址支持的用于SL数据接收和/或发送的载波。
  5. 如权利要求4所述的方法，其特征在于，所述基于所述第一配置信息和/或所述高层配置的第二配置信息，确定所述第三目标地址支持的用于SL数据接收和/或发送的载波，包括：
    基于所述第二配置信息，确定第一业务到载波的映射关系和/或所述第一业务到所述第三目标地址的映射关系，其中，所述第一业务包括组播业务和/或广播业务；
    根据所述第一业务到载波的映射关系和/或所述第一业务到所述第三目标地址的映射关系，确定所述第三目标地址到载波的映射关系；
    基于所述第三目标地址到载波的映射关系，确定所述第三目标地址支持的用于SL数据接收和/或发送的载波。
  6. 如权利要求4所述的方法，其特征在于，所述基于所述第一配置信息和/或所述高层配置的第二配置信息，确定所述第三目标地址支持的用于SL数据接收和/或发送的载波，包括：
    基于第一配置信息和第二配置信息的交集，确定所述第三目标地址支持的用于接收数据的载波。
  7. 如权利要求2或4所述的方法，其特征在于，所述第一配置信息包含在系统信息块SIB或预配置信息中。
  8. 如权利要求1中任一项所述的方法，其特征在于，所述基于所述至少一个目标地址支持的用于SL数据接收和/或发送的载波，从所述至少一个目标地址中确定所述终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，包括：
    基于所述至少一个目标地址支持的用于SL数据接收和/或发送的载波和/或所述第一条件，从所述至少一个目标地址确定所述终端发送的SL MAC PDU的第一目标地址。
  9. 如权利要求8所述的方法，其特征在于，所述第一条件包括以下任意一种或多种：
    侧行链路的非连续接收SL DRX适用于所述第一目标地址，所述侧行链路授权处于所述第一目标地址的激活时间，所述侧行链路授权用于发送所述SL MAC PDU；
    所述第一目标地址在至少一个第一逻辑信道和/或第一媒体接入控制层控制单元MAC CE中具有至少一个最高优先级的逻辑信道或者MAC CE，其中，第一逻辑信道和/或第一所述MAC CE满足第二条件。
  10. 如权利要求9所述的方法，其特征在于，所述第二条件包括以下任意一种或多种：
    具有等待发送的SL数据；
    所述第一逻辑信道有侧行链路发送缓冲器的令牌SBj，SBj>0；
    所述侧行链路授权是配置授权类型1，所述第一逻辑信道关联的允许侧行链路配置授权类型1sl-configuredGrantType1Allowed参数配置允许逻辑信道的媒体接入控制服务数据单元MAC SDU在所述配置授权类型1上传输；
    配置了允许使用的配置授权的列表，所述列表包含了所述侧行链路授权关联的配置授权标识；
    所述侧行链路授权没有关联的物理侧行链路反馈信道PSFCH资源，所述第一逻辑信道的混合自动重传请求HARQ属性是HARQ去使能HARQ-disabled；
    配置了支持在所述侧行链路授权关联的载波上发送。
  11. 如权利要求1所述的方法，其特征在于，所述确定所述SL MAC PDU包含的逻辑信道，包括：
    从属于所述第一目标地址的逻辑信道中，选择满足第三条件的逻辑信道；
    将所述满足第三条件的逻辑信道复用到所述SL MAC PDU中。
  12. 如权利要求11所述的方法，其特征在于，所述第三条件包括以下任意一种或多种：
    1)所述选择的逻辑信道有SL数据可发送；且，
    2)所述选择的逻辑信道的sl-configuredGrantType1Allowed参数被配置，在所述侧行链路授权是所述配置授权类型1的情况下，所述sl-configuredGrantType1Allowed参数设置为真；且，
    3)所述选择的逻辑信道的允许侧行链路上行免授权列表SL-allowedcg–list被配置，所述SL-allowedcg–list包括与所述侧行链路授权相关联的配置授权索引；且，
    4)所述选择的逻辑信道的侧行链路混合自动重传请求反馈使能sl-HARQ-FeedbackEnabled设置为满足以下条件的值：
    A)与侧行链路控制信息SCI关联的侧链授权配置了PSFCH，并且所述终端接收所述PSFCH：
    I)已经选择的至少一个逻辑信道中优先级最高的逻辑信道对应的sl-HARQ-FeedbackEnabled为使能，下一个选择的逻辑信道的sl-HARQ-FeedbackEnabled为使能；或者，
    II)已经选择的至少一个逻辑信道中优先级最高的逻辑信道对应的sl-HARQ-FeedbackEnabled设置为去使能，下一个选择的逻辑信道的sl-HARQ-FeedbackEnabled为去使能；
    B)与SCI关联的侧链授权未配置PSFCH，和/或，所述终端不接收PSFCH：
    所述选择的逻辑信道的sl-HARQ-FeedbackEnabled设置为不使能；
    5)配置了支持在所述侧行链路授权关联的载波上发送。
  13. 如权利要求1-12中任一项所述的方法，其特征在于，所述方法还包括：
    向所述第一目标地址发送侧行链路控制信息SCI；其中，
    所述侧行链路授权关联的载波为所述SCI传输所在的载波，或者，所述侧行链路授权关联的载波为所述SCI指示的物理侧行链路共享信道PSSCH所在的载波。
  14. 一种侧行链路通信方法，其特征在于，包括：
    网络设备向终端发送第一配置信息，所述第一配置信息用于所述终端确定至少一个目标地址支持的用于侧行链路SL数据接收和/或发送的载波，以使所述终端基于所述至少一个目标地址支持的用于SL数据接收和/或发送的载波确定所述终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定所述SL MAC PDU包含的逻辑信道；其中，所述第一目标地址支持在侧行链路授权关联的载波上进行SL数据接收。
  15. 一种通信系统，其特征在于，包括以下至少一项：
    终端，被配置于执行如权利要求1-13中任一项所述的侧行链路通信方法；
    网络设备，被配置于执行如权利要求14所述的侧行链路通信方法。
  16. 一种第一通信装置，其特征在于，包括：
    处理模块，用于针对侧行链路授权，确定至少一个目标地址支持的用于侧行链路SL数据接收和/或发送的载波；
    所述处理模块，还用于基于所述至少一个目标地址支持的用于SL数据接收和/或发送的载波，从所述至少一个目标地址确定所述第一通信装置发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定所述SL MAC PDU包含的逻辑信道；
    其中，所述第一目标地址支持在所述侧行链路授权关联的载波上进行SL数据接收。
  17. 一种第二通信装置，其特征在于，包括：
    收发模块，用于向终端发送第一配置信息，所述第一配置信息用于所述终端确定至少一个目标地址支持的用于侧行链路SL数据接收和/或发送的载波，以使所述终端基于所述至少一个目标地址支持的用于SL数据接收和/或发送的载波确定所述终端发送的侧行链路媒体接入控制协议数据单元SL MAC PDU的第一目标地址，和/或确定所述SL MAC PDU包含的逻辑信道；其中，所述第一目标地址支持在侧行链路授权关联的载波上进行SL数据接收。
  18. 一种通信设备，其特征在于，包括：
    一个或多个处理器；
    其中，所述处理器用于调用指令以使得所述通信设备执行权利要求1-13、14中任一项所述的侧行链路通信方法。
  19. 一种存储介质，所述存储介质存储有指令，其特征在于，当所述指令在通信设备上运行时，使得所述通信设备执行权利要求1-13、14中任一项所述的侧行链路通信方法。
PCT/CN2023/111346 2023-08-04 2023-08-04 一种侧行链路通信方法及其装置 Pending WO2025030292A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2023/111346 WO2025030292A1 (zh) 2023-08-04 2023-08-04 一种侧行链路通信方法及其装置
CN202380010450.6A CN119948997A (zh) 2023-08-04 2023-08-04 一种侧行链路通信方法及其装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/111346 WO2025030292A1 (zh) 2023-08-04 2023-08-04 一种侧行链路通信方法及其装置

Publications (1)

Publication Number Publication Date
WO2025030292A1 true WO2025030292A1 (zh) 2025-02-13

Family

ID=94533266

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/111346 Pending WO2025030292A1 (zh) 2023-08-04 2023-08-04 一种侧行链路通信方法及其装置

Country Status (2)

Country Link
CN (1) CN119948997A (zh)
WO (1) WO2025030292A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020087365A1 (zh) * 2018-10-31 2020-05-07 富士通株式会社 边链路数据的发送和配置方法以及装置
CN115699981A (zh) * 2021-01-26 2023-02-03 Oppo广东移动通信有限公司 一种数据传输方法、电子设备及存储介质
CN115868183A (zh) * 2022-09-16 2023-03-28 北京小米移动软件有限公司 一种目标终端确定方法、装置、通信设备及存储介质

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3051736B1 (en) * 2015-01-30 2020-04-29 Panasonic Intellectual Property Corporation of America Prioritization in the logical channel prioritization procedure for sidelink logical channels in ProSe direct communications
US20230036584A1 (en) * 2019-10-16 2023-02-02 Lg Electronics Inc. Method and apparatus for transmitting mac pdu on basis of sidelink grant in nr v2x

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020087365A1 (zh) * 2018-10-31 2020-05-07 富士通株式会社 边链路数据的发送和配置方法以及装置
CN115699981A (zh) * 2021-01-26 2023-02-03 Oppo广东移动通信有限公司 一种数据传输方法、电子设备及存储介质
CN115868183A (zh) * 2022-09-16 2023-03-28 北京小米移动软件有限公司 一种目标终端确定方法、装置、通信设备及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SPREADTRUM COMMUNICATIONS: "Logical channel prioritization Consideration", 3GPP DRAFT; R2-1905680-LOGICAL CHANNEL PRIORIZATION CONSIDERATION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20190513 - 20190517, 13 May 2019 (2019-05-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051729180 *

Also Published As

Publication number Publication date
CN119948997A (zh) 2025-05-06

Similar Documents

Publication Publication Date Title
US20250056329A1 (en) Method and apparatus for communication
WO2025010611A1 (zh) 用户面连接建立方法及装置
WO2025091515A1 (zh) 侧行链路通信方法及装置
WO2024234207A1 (zh) 侧行链路sl通信方法及装置、通信设备、通信系统、存储介质
WO2025030292A1 (zh) 一种侧行链路通信方法及其装置
WO2024207390A1 (zh) 信息处理方法及装置、通信设备及存储介质
WO2025091514A1 (zh) 信息处理方法及装置
WO2025091406A1 (zh) 一种通信方法及其装置
WO2025030432A1 (zh) 侧行链路数据包汇聚协议pdcp复用的方法及其装置
WO2025086306A1 (zh) 一种信息处理方法及其装置
WO2025043728A1 (zh) 通信方法、第一终端、第二终端、通信系统
WO2025030440A1 (zh) 载波聚合方法及装置
WO2025086307A1 (zh) 一种信息处理方法及其装置
WO2025035230A1 (zh) 通信方法及装置、通信设备、通信系统、存储介质
WO2024259708A1 (zh) 处理方法及装置、通信设备、通信系统、存储介质
WO2025097452A1 (zh) 一种通信方法及其装置
WO2025147821A1 (zh) 一种通信方法及装置
WO2026025241A1 (zh) 一种通信方法及装置
WO2026031205A1 (zh) 一种通信方法及装置
WO2025199894A1 (zh) 信号传输方法及通信设备、通信系统、存储介质
WO2025065289A1 (zh) 一种信息处理方法及其装置
WO2025217858A1 (zh) 数据传输方法、网络设备、终端、通信系统、存储介质及计算机程序产品
WO2025107208A1 (zh) 信息处理方法、装置及存储介质
WO2025236183A1 (zh) 一种通信方法、装置及存储介质
WO2025091437A1 (zh) 通信指示方法、第一网元、第二网元、核心网设备

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202380010450.6

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23947875

Country of ref document: EP

Kind code of ref document: A1

WWP Wipo information: published in national office

Ref document number: 202380010450.6

Country of ref document: CN