Sidelink communication method and apparatus

Abstract

The embodiment of the disclosure discloses a kind of sidelink communication method and device, by obtaining first information, first information includes the mapping relationship between at least one QoS flow of terminal and SL RB and the configuration information of SL RB;Determine the transmission attribute corresponding to each QoS flow in at least one QoS flow, at least one QoS flow in at least one QoS flow There is at least one QoS flow corresponding to the transmission attribute different from the rest QoS flow;Based on first information, establish multiple SL RB, the transmission attribute corresponding to one or more QoS flows mapped to the same SL RB is same;Or, in the case that at least one QoS flow mapped to SL RB includes at least one transmission attribute for backward compatible QoS flow, determine to send SL RB by single traditional carrier, or determine to send SL RB using PDCP multiplexing mechanism, so that terminal can establish multiple radio bearers based on the attribute of service or determine the carrier for sending corresponding radio bearer, effectively guarantee the backward compatibility of service flow, improve the reliability of service transmission.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a sidelink communication method and apparatus. Background Technology

[0002] To support direct communication between terminals, a sidelink (SL) communication method was introduced. To meet the need for increased system capacity, carrier aggregation (CA) was introduced. As technology continues to develop and terminal and service versions iterate, a transmission attribute (TxProfile) was introduced to indicate the service version number to ensure service compatibility. Summary of the Invention

[0003] This disclosure presents a sidelink communication method and apparatus.

[0004] A first aspect of this disclosure provides a sidelink communication method, the method comprising: acquiring first information, the first information including sidelink SL radio bearer (RB) configuration information, the SL RB configuration information including a mapping relationship between at least one Quality of Service (QoS) stream and an SL RB; determining the transmission attribute corresponding to each of the at least one QoS stream, wherein at least one QoS stream has a transmission attribute different from the other QoS streams; and establishing multiple SL RBs based on the first information, wherein one or more QoS streams mapped to the same SL RB have the same transmission attribute.

[0005] A second aspect of this disclosure provides a sidelink communication method, the method comprising: acquiring first information, the first information including sidelink SL radio bearer (RB) configuration information, the SL RB configuration information including a mapping relationship between at least one Quality of Service (QoS) stream and the SL RB; determining a transmission attribute corresponding to each QoS stream in the at least one QoS stream, the transmission attribute being backward compatible or non-backward compatible, wherein at least one QoS stream in the at least one QoS stream has a transmission attribute different from the other QoS streams; determining that the at least one QoS stream mapped to the SL RB includes at least one QoS stream with a backward compatible transmission attribute; determining that the SL RB is transmitted via a single carrier and the single carrier is an existing / traditional carrier, or determining that the SL RB is transmitted using a Packet Data Convergence Protocol (PDCP) multiplexing mechanism.

[0006] A third aspect of this disclosure provides a terminal comprising: a transceiver module for acquiring first information, the first information including sidelink (SL) radio bearer (RB) configuration information, the SL RB configuration information including a mapping relationship between at least one Quality of Service (QoS) stream and an SL RB; a processing module for determining a transmission attribute corresponding to each of the at least one QoS stream, wherein at least one QoS stream has a transmission attribute different from the other QoS streams; the processing module is further configured to establish multiple SL RBs based on the first information; wherein one or more QoS streams mapped to the same SL RB have the same transmission attribute.

[0007] The fourth aspect of this disclosure provides a terminal, the aforementioned network device comprising: a transceiver module configured to acquire first information, the first information including sidelink SL radio bearer (RB) configuration information, the SL RB configuration information including at least one Quality of Service (QoS) flow mapping relationship to an SL RB; a processing module configured to determine the transmission attribute corresponding to each QoS flow in the at least one QoS flow, the transmission attribute being backward compatible or non-backward compatible, wherein at least one QoS flow in the at least one QoS flow has a transmission attribute different from the other QoS flows; the processing module is further configured to determine that the at least one QoS flow mapped to the SL RB includes at least one QoS flow with a backward compatible transmission attribute, determine that the SL RB is transmitted via a single carrier and the single carrier is an existing / traditional carrier, or determine that the SL RB is transmitted using a Packet Data Convergence Protocol (PDCP) multiplexing mechanism.

[0008] The scheme proposed in this disclosure involves obtaining first information, including SL RB configuration information, which includes a mapping relationship between at least one QoS flow and an SL RB; determining the transmission attribute corresponding to each QoS flow in the at least one QoS flow, wherein at least one QoS flow in the at least one QoS flow has a transmission attribute different from the other QoS flows; establishing multiple SL RBs based on the first information; wherein one or more QoS flows mapped to the same SL RB have the same transmission attribute, or, in the case where at least one QoS flow mapped to an SL RB includes at least one QoS flow with a backward-compatible transmission attribute, determining that the SL RB is transmitted via a single carrier and the single carrier is an existing / traditional carrier, or determining that the SL RB is transmitted using the Packet Data Convergence Protocol (PDCP) multiplexing mechanism, enabling the terminal to establish multiple radio bearers or determine the carrier to transmit the corresponding radio bearer based on the attributes of the service, effectively ensuring the backward compatibility of the service flow and improving the reliability of service transmission. Attached Figure Description

[0009] To more clearly illustrate the technical solutions in the embodiments or background art of this disclosure, the accompanying drawings used in the embodiments or background art of this disclosure will be described below.

[0010] Figure 1A This is a schematic diagram of the architecture of a communication system provided in an embodiment of this disclosure;

[0011] Figure 1B This is a schematic diagram of the status of a side-link communication network provided in an embodiment of this disclosure;

[0012] Figure 1C This is a schematic diagram of a PDCP multiplexing mechanism provided in an embodiment of this disclosure;

[0013] Figure 2A-2B This is an interactive schematic diagram of a side-link communication method provided in an embodiment of this disclosure;

[0014] Figures 3A-3D This is a flowchart illustrating a side-link communication method provided in an embodiment of this disclosure;

[0015] Figure 4A This is a schematic diagram of the structure of a terminal provided in an embodiment of this disclosure;

[0016] Figure 4B This is a schematic diagram of the structure of another terminal provided in an embodiment of this disclosure;

[0017] Figure 5A This is a schematic diagram of the structure of a communication device provided in an embodiment of this disclosure;

[0018] Figure 5B This is a schematic diagram of the structure of a chip provided in an embodiment of this disclosure. Detailed Implementation

[0019] This disclosure presents a sidelink communication method and apparatus.

[0020] In a first aspect, embodiments of this disclosure propose a side-link communication method, the method comprising:

[0021] Obtain first information, which includes sidelink SL radio bearer RB configuration information, and the SL RB configuration information includes at least one mapping relationship between a Quality of Service (QoS) flow and an SL RB.

[0022] Determine the transmission attribute corresponding to each QoS flow in the at least one QoS flow, wherein at least one QoS flow has a transmission attribute that is different from the other QoS flows;

[0023] Based on the first information, multiple SL RBs are established; wherein one or more QoS flows mapped to the same SL RB have the same transmission attributes.

[0024] In the above embodiments, the terminal can establish multiple radio bearers based on the attributes of the service, so that the QoS streams contained in each radio bearer have the same transmission attributes, effectively ensuring the backward compatibility of the service stream and improving the reliability of service transmission.

[0025] In conjunction with some embodiments of the first aspect, in some embodiments, the sending attribute is backward compatible or non-backward compatible.

[0026] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0027] Map at least one QoS flow without associated transmission attributes to the same SL RB; or,

[0028] Map at least one QoS flow without associated transmission attributes to the same SL RB along with at least one QoS flow whose transmission attributes are backward compatible; or,

[0029] Map at least one QoS flow without associated transmission attributes to the same SL RB as at least one QoS flow with a non-backward compatible transmission attribute.

[0030] In conjunction with some embodiments of the first aspect, in some embodiments, the terminal is in a Radio Resource Control (RRC) idle state or inactive state, or the terminal is in an Out-of-Coverage (OOC) state outside network coverage.

[0031] In conjunction with some embodiments of the first aspect, in some embodiments, obtaining the first information includes:

[0032] The first information is obtained through the System Information Block (SIB), wherein the terminal is in a Radio Resource Control (RRC) idle state or an inactive state; or...

[0033] The first information is obtained through pre-configuration, wherein the terminal is in an OOC state.

[0034] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0035] Obtain the transmission attributes corresponding to the at least one QoS flow from the higher layer;

[0036] Determine whether the transmission attribute of a QoS flow without associated transmission attributes is backward compatible, or determine whether the transmission attribute of a QoS flow without associated transmission attributes is non-backward compatible.

[0037] Secondly, embodiments of this disclosure propose a side-link communication method, the method comprising:

[0038] Obtain first information, which includes sidelink SL radio bearer RB configuration information, and the SL RB configuration information includes at least one mapping relationship between a Quality of Service (QoS) flow and an SL RB.

[0039] Determine the transmission attribute corresponding to each QoS flow in the at least one QoS flow, wherein the transmission attribute is backward compatible or non-backward compatible, and at least one QoS flow in the at least one QoS flow has a transmission attribute that is different from the other QoS flows;

[0040] The system determines that at least one QoS flow mapped to the SL RB includes at least one QoS flow with backward-compatible transmission attributes, determines that the SL RB is transmitted via a single carrier and the single carrier is an existing / traditional carrier, or determines that the SL RB is transmitted using the Packet Data Convergence Protocol (PDCP) multiplexing mechanism.

[0041] In the above embodiments, the terminal is able to determine the carrier of the corresponding radio bearer to be sent based on the attributes of the service, which effectively ensures the backward compatibility of the service flow and improves the reliability of service transmission.

[0042] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0043] The SL RB is determined to be transmitted using the Packet Data Convergence Protocol (PDCP) multiplexing mechanism, with existing / traditional carriers being at least one of the carriers used by the PDCP multiplexing mechanism, and the existing / traditional carriers being used to transmit the SL RB.

[0044] In conjunction with some embodiments of the second aspect, in some embodiments, the terminal is in a Radio Resource Control (RRC) idle state or inactive state, or the terminal is in an Out-of-Coverage (OOC) state outside network coverage.

[0045] In conjunction with some embodiments of the second aspect, in some embodiments, obtaining the first information includes:

[0046] The first information is obtained through the System Information Block (SIB), wherein the terminal is in an RRC idle state or an inactive state; or,

[0047] The first information is obtained through pre-configuration, wherein the terminal is in an OOC state.

[0048] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0049] Obtain the transmission attributes corresponding to the at least one QoS flow from the higher layer;

[0050] Determine whether the transmission attribute of a QoS flow without associated transmission attributes is backward compatible, or determine whether the transmission attribute of a QoS flow without associated transmission attributes is non-backward compatible.

[0051] Thirdly, embodiments of this disclosure provide a terminal, which includes a transceiver module and a processing module; wherein the terminal is used to execute the first aspect and optional implementations of the first aspect.

[0052] Fourthly, embodiments of this disclosure provide a terminal, which includes a transceiver module and a processing module; wherein the terminal is used to execute the second aspect and optional implementations of the second aspect.

[0053] Fifthly, embodiments of this disclosure provide a terminal, which includes one or more processors; wherein the terminal is used to execute the first aspect and optional implementations of the first aspect.

[0054] In a sixth aspect, embodiments of this disclosure provide a terminal, the terminal comprising: one or more processors; wherein the terminal is used to execute the second aspect and optional implementations of the second aspect.

[0055] In a seventh aspect, embodiments of this disclosure provide a communication system comprising: a terminal; wherein the terminal is configured to perform the method described in the first aspect and optional implementations thereof, and the terminal is configured to perform the method described in the second aspect and optional implementations thereof.

[0056] Eighthly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect and its optional implementation, as well as the second aspect and its optional implementation.

[0057] Ninthly, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in the first aspect and its optional implementation, the second aspect and its optional implementation.

[0058] In a tenth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in the first aspect and its alternative implementations, the second aspect and its alternative implementations.

[0059] Eleventhly, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to the first aspect and its optional implementations, the second aspect, and its optional implementations.

[0060] It is understood that the aforementioned terminals, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0061] This disclosure provides a side-link communication method and apparatus. In some embodiments, the terms "side-link communication method" and "communication method" can be used interchangeably, as can the terms "side-link communication apparatus" and "communication apparatus"; and the terms "side-link communication system" and "communication system" can be used interchangeably.

[0062] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0063] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0064] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0065] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0066] In the embodiments of this disclosure, "multiple" refers to two or more.

[0067] In some embodiments, the terms “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0068] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0069] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0070] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0071] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0072] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0073] In some embodiments, the terms “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 used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0074] In some embodiments, the apparatus and device 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", "body", etc.

[0075] In some embodiments, "network" can be interpreted as devices included in the network, such as access network devices, core network devices, etc.

[0076] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)," "base station (BS)," "radio base station," or "fixed station." In some embodiments, it may also be understood as "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," "cellgroup," "serving cell," "carrier," "component carrier," or "bandwidth part (BWP)," etc.

[0077] In some embodiments, "terminal" or "terminal device" may be referred to as "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," etc.

[0078] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0079] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0080] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0081] Figure 1A This is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0082] like Figure 1A As shown, the communication system 100 includes a terminal 101 and a network device 102.

[0083] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, wireless terminal device in smart home, and redcap terminal, but is not limited thereto.

[0084] In some embodiments, network device 102 may be a node or device that connects a terminal to a wireless network. The network device may include at least one of the following in a sidelink communication network: an evolved Node B (eNB), a next-generation eNB (ng-eNB), a next-generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (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.

[0085] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0086] In some embodiments, the network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0087] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0088] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0089] The embodiments disclosed herein can be applied to sidelink communication systems, 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), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0090] In some embodiments, a sidelink (SL) communication method is introduced to support direct communication between terminals. The interface between terminals is PC-5 (a low-level direct cellular communication protocol interface). Both in-coverage and out-of-coverage (OOC) terminal devices can perform sidelink communication. For example, ... Figure 1B As shown, the first terminal in coverage and the second terminal in coverage can communicate via sidelink. Alternatively, the first terminal in coverage and the second terminal in OOC can communicate via sidelink. Or, the first terminal in OOC and the second terminal in OOC can communicate via sidelink. The in-coverage terminal device can be in a connected state (RRC), an idle state (RRC), or an inactive state (RRC). Sidelink communication performed by the terminal device includes three transmission methods: unicast, multicast, and broadcast.

[0091] In some embodiments, as terminal and service versions iterate, LTE V2X defines a transmission attribute (TxProfile) to indicate the service version number in order to ensure backward compatibility. For example, R17 NR V2X introduces the Discontinuous Reception (DRX) feature. To ensure backward compatibility, such as ensuring that older version terminals can receive broadcast / multicast services from R17 terminals, and vice versa, a TxProfile is defined at the Layer 2 (L2) identifier granularity for broadcast / multicast services. The TxProfile indicates whether the associated broadcast / multicast service supports DRX. If the transmitting terminal determines that a broadcast / multicast service supports the DRX attribute, it can assume that the receiving terminal has enabled DRX and only transmit data during the receiving terminal's "active" time. The receiving terminal enables DRX only when it determines that all broadcast / multicast services of interest support the DRX attribute, meaning it only wakes up to listen for broadcast / multicast service data during the "active" time.

[0092] In some embodiments, to meet the demand for increased system capacity, carrier aggregation (CA) technology is introduced. CA technology can aggregate multiple carriers (Component Carrier, CC) together, effectively improving uplink and downlink transmission rates. LTE V2X already supports sidelink carrier aggregation technology. Furthermore, one of the goals of NR sidelink carrier aggregation is to ensure backward compatibility, that is, to ensure that older R16 / R17 terminals can receive broadcast / multicast services sent by R18 terminals that support carrier aggregation.

[0093] In some embodiments, to improve data packet reliability, a Packet Data Convergence Protocol (PDCP) duplication mechanism, also known as packet duplication, is introduced, which involves retransmitting a data packet once. Using this mechanism for repeated transmission improves the reliability of data packet transmission, reduces the latency of repeated transmissions, and meets the requirements of Ultra-Reliable Low-Latency Communications (URLLC). Without PDCP duplication, a PDCP packet would be transmitted to one Radio Link Control (RLC) entity, processed by the RLC, and then sent to the Medium Access Control (MAC) layer for data scheduling. With PDCP duplication, a PDCP packet would be transmitted to at least two RLC entities, for example, Figure 1C The diagram shows the primary and secondary RLC entities. Each RLC entity processes its own packet and transmits it to the MAC layer. From the MAC layer's perspective, these are two independent packets; the MAC layer cannot distinguish whether they are packets from PDCP duplication. The MAC layer simply schedules the packets according to its algorithm. It should be noted that in CA scenarios, the protocol requires the two packets of PDCP duplication to be transmitted on different cells using different logical channels (LCHs). For example, Figure 1CThe diagram shows the Primary LCH and Secondary LCH. On the NR Uu interface, the LCH used for PDCP duplication is configured to the terminal by the network side through RB configuration. Network devices can configure whether an RB enables PDCP duplication through SL RB configuration.

[0094] In some embodiments, the network device can configure an SL radio bearer (RB) for a UE in the Radio Resources Control (RRC) connected state through a sidelink radio bearer configuration SL-RadioBearerConfig. The SL-RadioBearerConfig configuration includes a Service Data Adaptation Protocol (SDAP) configuration, and the SDAP configuration includes the Quality of Service (QoS) flow associated with this SL RB.

[0095] In some embodiments, if a network device does not know the TxProfile associated with a certain QoS flow, it may map backward-compatible QoS flows and non-backward-compatible QoS flows into a single SL RB. In this case, if the network is configured to disable PDCP duplication for the SL RB, then the terminal is not required to use a legacy carrier, also known as an existing carrier (existing / legacy carriers supported by R16 / R17). When the terminal does not use a legacy carrier, the backward-compatible QoS flow contained in this RB can only be transmitted through the new carrier, and the R16 / R17 terminal will not be able to receive this QoS flow.

[0096] The side-link communication method and apparatus provided in this disclosure will now be described in detail with reference to the accompanying drawings.

[0097] Figure 2A This is an interactive schematic diagram of a side-link communication method according to an embodiment of this disclosure. For example... Figure 2A As shown, this disclosure relates to a side-link communication method, which includes:

[0098] Step S2101, terminal 101 obtains the first information.

[0099] In some embodiments, terminal 101 is in Radio Resources Control (RRC) idle state or inactive state, or terminal 101 is in out of coverage (OOC) state.

[0100] In some embodiments, the terminal 101 is in an RRC idle state or an inactive state, and the terminal 101 obtains the aforementioned first information through the System Information Block (SIB).

[0101] In some embodiments, the terminal 101 is in an OOC state, and the terminal 101 obtains the aforementioned first information through pre-configuration.

[0102] In some embodiments, the first information includes sidelink (SL) radio bearer (RB) configuration information, wherein the SLRB configuration information includes at least one Quality of Service (QoS) flow and the SLRB.

[0103] It is understood that the above SL RB refers to the SL RB configured in the SL RB configuration information.

[0104] In some embodiments, the SL RB described above may also be a Data Radio Bearer (DRB).

[0105] In some embodiments, the first information described above may include one or more of the SL RB configurations described above.

[0106] Optionally, the first information mentioned above includes one or more of the above SL RB configurations (e.g., at least one of SDAP configuration, PDCP configuration, RLC configuration, MAC configuration, etc.).

[0107] In some embodiments, the name of the first information is not limited, and may be, for example, “sidelink radio bearer configuration”, “service data adaptation protocol configuration”, “sidelink configuration”, “radio bearer configuration”, etc.

[0108] In step S2102, terminal 101 obtains at least one transmission attribute associated with a QoS flow.

[0109] In some embodiments, the transmission attribute (Tx Profile) is configured at the granularity of the QoS flow.

[0110] In some embodiments, terminal 101 obtains at least one association between QoS flow and transmission attributes from a higher layer of terminal 101.

[0111] In some embodiments, the access layer (AS) of terminal 101 obtains at least one association between QoS flow and transmission attributes from the higher layers of terminal 101.

[0112] In some embodiments, the above-described transmission attributes are backward compatible or non-backward compatible.

[0113] It is understandable that sending a QoS stream with backward compatibility attributes refers to a QoS stream that older R16 / R17 terminals can receive.

[0114] In step S2103, terminal 101 determines the transmission attribute corresponding to each QoS.

[0115] In some embodiments, the terminal 101 determines the transmission attribute corresponding to each QoS flow based on the association between at least one QoS flow and transmission attribute obtained from a higher layer of the terminal 101.

[0116] In some embodiments, terminal 101 determines that among at least one QoS flow associated with the above-mentioned SLRB (an SLRB configured by SLRB configuration information), at least one QoS flow has a transmission attribute that is different from the other QoS flows.

[0117] In some embodiments, terminal 101 determines that the transmission attribute corresponding to a QoS flow without associated transmission attribute is backward compatible.

[0118] In some embodiments, terminal 101 determines that the transmission attribute corresponding to a QoS flow without associated transmission attribute is non-backward compatible.

[0119] Step S2104, terminal 101 establishes SL RB.

[0120] In some embodiments, terminal 101 establishes an SL RB based on the first information described above and / or at least one QoS flow-associated transmission attribute obtained by terminal 101. For example, terminal 101 establishes an SL RB based on the SLRB configuration included in the first information and / or at least one QoS flow-associated transmission attribute obtained by terminal 101.

[0121] In some embodiments, terminal 101 establishes multiple SLRBs based on the first information described above. One or more QoS flows mapped to the same SLRB have the same transmission attributes. For example, terminal 101 establishes multiple SLRBs based on an SLRB configuration included in the first information and / or the transmission attributes associated with at least one QoS flow obtained by terminal 101. The QoS flows mapped to the same SLRB have the same transmission attributes.

[0122] As an example, the first information includes the configurations of three SL RBs (Streaming Service Receiving Blocks): A, B, and C. For configuration A, terminal 101 determines that at least one QoS stream corresponding to the SL RBs in configuration A has different transmission attributes. Terminal 101 can establish multiple SL RBs based on configuration A, wherein the transmission attributes of at least one QoS stream corresponding to each SL RB are the same. Similarly, for configuration B, terminal 101 determines that at least one QoS stream corresponding to the SL RBs in configuration B has different transmission attributes. Terminal 101 can establish multiple SL RBs based on configuration B, wherein the transmission attributes of at least one QoS stream corresponding to each SL RB are the same. For configuration C, terminal 101 determines that at least one QoS stream corresponding to the SL RBs in configuration C has different transmission attributes. Terminal 101 can establish multiple SL RBs based on configuration C, wherein the transmission attributes of at least one QoS stream corresponding to each SL RB are the same.

[0123] In some embodiments, terminal 101 may map at least one backward-compatible QoS stream to one or more SL RBs.

[0124] In some embodiments, terminal 101 may map at least one QoS stream with non-backward compatible transmission attributes to one or more SL RBs.

[0125] In some embodiments, terminal 101 may map at least one QoS stream without associated transmission attributes to one or more SL RBs.

[0126] In some embodiments, QoS streams with different transmission attributes are mapped to different SLRBs.

[0127] In some embodiments, terminal 101 may map at least one QoS stream without associated transmission attributes and at least one QoS stream with backward compatible transmission attributes to the same SL RB, that is, determine the QoS stream without associated transmission attributes as a backward compatible QoS stream.

[0128] In some embodiments, terminal 101 may map at least one QoS stream without associated transmission attributes and at least one QoS stream with non-backward compatible transmission attributes to the same SL RB, that is, determine the QoS stream without associated transmission attributes as a non-backward compatible QoS stream.

[0129] In some embodiments, transmitting one or more SLRBs mapped to at least one backward-compatible QoS flow can employ single-carrier transmission, wherein the single carrier is an existing / lagacy carrier. Specifically, the existing / lagacy carrier refers to the SL carrier supported by the R16 / R17 terminal.

[0130] In some embodiments, one or more SLRBs that transmit at least one QoS stream map with backward compatibility attributes can be transmitted using a PDCP multiplexing mechanism, wherein at least one of the carriers used by the PDCP multiplexing mechanism is an existing / lagacy carrier.

[0131] In some embodiments, the terms "carrier," "band," and "frequency" can be used interchangeably.

[0132] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0133] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0134] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0135] In some embodiments, the terms “radio”, “wireless”, “radioaccess network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0136] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.

[0137] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0138] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transmit,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0139] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0140] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0141] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2104. For example, step 2101 may be implemented as an independent embodiment, steps 2102+2103 may be implemented as an independent embodiment, step 2104 may be implemented as an independent embodiment, steps 2103+2104 may be implemented as an independent embodiment, steps 2102+2103+2104 may be implemented as an independent embodiment, steps 2101+2102+2103+2104 may be implemented as an independent embodiment, etc., but is not limited thereto.

[0142] In some embodiments, steps 2101 and 2102 may be performed in an interchangeable order or simultaneously.

[0143] In some embodiments, see Figure 2A Other optional implementation methods described before or after the corresponding instruction manual.

[0144] Figure 2B This is an interactive schematic diagram of a side-link communication method according to an embodiment of this disclosure. For example... Figure 2B As shown, this disclosure relates to a side-link communication method, which includes:

[0145] Step S2201: Terminal 101 obtains the first information.

[0146] In some embodiments, terminal 101 is in Radio Resources Control (RRC) idle state or inactive state, or terminal 101 is in out of coverage (OOC) state.

[0147] In some embodiments, the terminal 101 is in an RRC idle state or an inactive state, and the terminal 101 obtains the aforementioned first information through the System Information Block (SIB).

[0148] In some embodiments, the terminal 101 is in an OOC state, and the terminal 101 obtains the aforementioned first information through pre-configuration.

[0149] In some embodiments, the first information includes sidelink (SL) radio bearer (RB) configuration information, which includes at least one mapping relationship between a Quality of Service (QoS) flow and the SLRB. In some embodiments, the SLRB may also be a data radio bearer (DRB).

[0150] In some embodiments, the first information described above may include the configuration of one or more of the aforementioned SL RBs.

[0151] Optionally, the first information mentioned above includes one or more of the above SL RB configurations (e.g., SDAP configuration, PDCP configuration, MAC configuration, etc.).

[0152] In some embodiments, the name of the first information is not limited, and may be, for example, “sidelink radio bearer configuration”, “service data adaptation protocol configuration”, “sidelink configuration”, “radio bearer configuration”, etc.

[0153] In step S2202, terminal 101 obtains at least one transmission attribute associated with a QoS flow.

[0154] In some embodiments, the transmission attribute (Tx Profile) is configured at the granularity of the QoS flow.

[0155] In some embodiments, terminal 101 obtains at least one association between QoS flow and transmission attributes from a higher layer of terminal 101.

[0156] In some embodiments, the access layer (AS) of terminal 101 obtains at least one association between QoS flow and transmission attributes from the higher layers of terminal 101.

[0157] In some embodiments, the above-described transmission attributes are backward compatible or non-backward compatible.

[0158] It is understandable that sending a QoS stream with backward compatibility attributes refers to a QoS stream that older R16 / R17 terminals can receive.

[0159] In step S2203, terminal 101 determines the transmission attribute corresponding to each QoS.

[0160] In some embodiments, the terminal 101 determines the transmission attribute corresponding to each QoS flow based on the association between at least one QoS flow and transmission attribute obtained from a higher layer of the terminal 101.

[0161] In some embodiments, terminal 101 determines that among at least one QoS flow associated with the above-mentioned SLRB (an SLRB configured by SLRB configuration information), at least one QoS flow has a transmission attribute that is different from the other QoS flows.

[0162] In some embodiments, terminal 101 determines that the transmission attribute corresponding to a QoS flow without associated transmission attribute is backward compatible.

[0163] In some embodiments, terminal 101 determines that the transmission attribute corresponding to a QoS flow without associated transmission attribute is non-backward compatible.

[0164] In step S2204, terminal 101 determines the carrier to be transmitted for the aforementioned SL RB.

[0165] In some embodiments, terminal 101 determines that at least one QoS flow associated with the aforementioned SL RB includes at least one QoS flow with a backward-compatible transmission attribute. Here, the aforementioned SL RB is an SL RB configured by SL RB configuration information in the first information.

[0166] In some embodiments, terminal 101 determines to transmit the aforementioned SL RB via a single carrier, wherein the single carrier is an existing / legacy carrier. Specifically, the existing / legacy carrier refers to the SL carrier supported by the R16 / R17 terminal.

[0167] In some embodiments, terminal 101 determines to transmit the above-mentioned SL RB using a PDCP multiplexing mechanism, wherein at least one of the carriers used by the PDCP multiplexing mechanism is an existing / legacy carrier.

[0168] In some embodiments, the terms "carrier," "band," and "frequency" can be used interchangeably. Let's also add a brief summary of the previous case.

[0169] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0170] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0171] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0172] In some embodiments, the terms “radio”, “wireless”, “radioaccess network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0173] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.

[0174] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0175] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0176] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0177] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0178] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2204. For example, step 2201 may be implemented as an independent embodiment, steps 2202+2203 may be implemented as an independent embodiment, steps 2204 may be implemented as an independent embodiment, steps 2203+2204 may be implemented as an independent embodiment, steps 2202+2203+2204 may be implemented as an independent embodiment, steps 2201+2202+2203+2204 may be implemented as an independent embodiment, etc., but is not limited thereto.

[0179] In some embodiments, steps 2201 and 2202 may be performed in an alternate order or simultaneously.

[0180] In some embodiments, see Figure 2B Other optional implementation methods described before or after the corresponding instruction manual.

[0181] Figure 3A This is a flowchart illustrating a side-link communication method according to an embodiment of this disclosure. Figure 3A As shown, this disclosure relates to a side-link communication method, which is executed by terminal 101 and includes:

[0182] Step S3101: Obtain the first information.

[0183] For optional implementations of step S3101, please refer to [link / reference]. Figure 2A Optional implementation methods of step S2101, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0184] Step S3102: Obtain at least one QoS flow associated transmission attribute.

[0185] For optional implementations of step S3102, please refer to [link / reference]. Figure 2A Optional implementation methods of step S2102, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0186] Step S3103: Determine the transmission attributes corresponding to each QoS.

[0187] For optional implementations of step S3104, please refer to [link / reference]. Figure 2A Optional implementation methods of step S2103, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0188] Step S3104: Establish SL RB.

[0189] For optional implementations of step S3104, please refer to [link / reference]. Figure 2A Optional implementation methods of step S2104, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0190] The communication method involved in the embodiments of this disclosure may include at least one of steps S3101 to S3104. For example, step 3101 may be implemented as an independent embodiment, steps 3102+3103 may be implemented as an independent embodiment, step 3104 may be implemented as an independent embodiment, steps 3103+3104 may be implemented as an independent embodiment, steps 3102+3103+3104 may be implemented as an independent embodiment, steps 3101+3102+3103+3104 may be implemented as an independent embodiment, etc., but not limited thereto.

[0191] In some embodiments, steps 3101 and 3102 may be performed in an interchangeable order or simultaneously.

[0192] Figure 3B This is a flowchart illustrating a side-link communication method according to an embodiment of this disclosure. Figure 3B As shown, this disclosure relates to a side-link communication method, which is executed by terminal 101 and includes:

[0193] Step S3201: Obtain the first information.

[0194] For optional implementations of step S3201, please refer to [link / reference]. Figure 2B Optional implementation methods of step S2201, and Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0195] Step S3202: Obtain at least one QoS flow associated transmission attribute.

[0196] For optional implementations of step S3202, please refer to [link / reference]. Figure 2B Optional implementation methods of step S2202, and Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0197] Step S3203: Determine the transmission attributes corresponding to each QoS.

[0198] For optional implementations of step S3203, please refer to [link / reference]. Figure 2B Optional implementation methods of step S2203, and Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0199] Step S3204: Determine the carrier to transmit the above-mentioned SL RB.

[0200] For optional implementations of step S3204, please refer to [link / reference]. Figure 2B Optional implementation methods of step S2204, and Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0201] The communication method involved in the embodiments of this disclosure may include at least one of steps S3201 to S3204. For example, step 3201 may be implemented as an independent embodiment, steps 3202+3203 may be implemented as an independent embodiment, step 3204 may be implemented as an independent embodiment, steps 3203+3204 may be implemented as an independent embodiment, steps 3202+3203+3204 may be implemented as an independent embodiment, steps 3201+3202+3203+3204 may be implemented as an independent embodiment, etc., but is not limited thereto.

[0202] In some embodiments, steps 3201 and 3202 may be performed in an interchangeable order or simultaneously.

[0203] Figure 3C This is a schematic flowchart illustrating a side-link communication method according to an embodiment of the present disclosure. Figure 3C As shown, this disclosure relates to a side-link communication method, which is executed by terminal 101 and includes:

[0204] Step S3301: Obtain the first information.

[0205] For optional implementations of step S3301, please refer to [link / reference]. Figure 2A Step S2101 Figure 3A Optional implementation methods of step S3101, and Figure 2A , Figure 3A Other related parts in the embodiments involved will not be described in detail here.

[0206] Step S3302: Determine the transmission attributes corresponding to each QoS.

[0207] For optional implementations of step S3302, please refer to [link / reference]. Figure 2A Step S2103 Figure 3A Optional implementation methods of step S3103, and Figure 2A , Figure 3A Other related parts in the embodiments involved will not be described in detail here.

[0208] Step S3303: Establish SL RB.

[0209] For optional implementations of step S3303, please refer to [link / reference]. Figure 2A Step S2104 Figure 3A Optional implementation methods of step S3104, and Figure 2A , Figure 3A Other related parts in the embodiments involved will not be described in detail here.

[0210] The communication method involved in the embodiments of this disclosure may include at least one of steps S3301 to S3303. For example, step 3302 may be implemented as an independent embodiment, step 3303 may be implemented as an independent embodiment, step 3301+3303 may be implemented as an independent embodiment, step 3302+3303 may be implemented as an independent embodiment, step 3301+3302+3303 may be implemented as an independent embodiment, etc., but not limited thereto.

[0211] In some embodiments, steps 3301 and 3302 may be performed in an alternate order or simultaneously.

[0212] Figure 3D This is a schematic flowchart illustrating a side-link communication method according to an embodiment of the present disclosure. Figure 3D As shown, this disclosure relates to a side-link communication method, which is executed by terminal 101 and includes:

[0213] Step S3401: Obtain the first information.

[0214] For optional implementations of step S3401, please refer to [link / reference]. Figure 2B Step S2101 Figure 3B Optional implementation methods of step S3101, and Figure 2B , Figure 3B Other related parts in the embodiments involved will not be described in detail here.

[0215] Step S3402: Determine the transmission attributes corresponding to each QoS.

[0216] For optional implementations of step S3402, please refer to [link / reference]. Figure 2B Step S2103 Figure 3B Optional implementation methods of step S3103, and Figure 2B , Figure 3B Other related parts in the embodiments involved will not be described in detail here.

[0217] Step S3403: Determine the carrier to transmit the above-mentioned SL RB.

[0218] For optional implementations of step S3403, please refer to [link / reference]. Figure 2B Step S2104 Figure 3BOptional implementation methods of step S3104, and Figure 2B , Figure 3B Other related parts in the embodiments involved will not be described in detail here.

[0219] The communication method involved in the embodiments of this disclosure may include at least one of steps S3401 to S3403. For example, step 3402 may be implemented as a standalone embodiment, step 3403 may be implemented as a standalone embodiment, steps 3401+3403 may be implemented as standalone embodiments, steps 3402+3403 may be implemented as standalone embodiments, steps 3401+3402+3403 may be implemented as standalone embodiments, etc., but not limited thereto.

[0220] In some embodiments, steps 3401 and 3402 may be performed in an alternate order or simultaneously.

[0221] The following is an exemplary description of the methods described in the above embodiments.

[0222] In some embodiments, the UE may establish more than one SLRB if the QoS flow mapping DRB has been established or not, but the tx profiles associated with these QoS flows are different.

[0223] As an example, if a QoS flow in an SIB or pre-configured system is mapped to a DRB, and this DRB is either already established or not, and these QoS flows are associated with different transaction profiles, the UE can establish more than one SLRB. For instance, the UE can establish QoS flows with the same transaction profile attributes in one SLRB, and the UE can establish QoS flows with different transaction profile attributes in different SLRBs. If a QoS flow does not have an associated transaction profile, the UE can establish one SLRB for the QoS flow without an associated transaction profile, or the UE can establish this QoS flow in the same SLRB as other QoS flows indicated by backward compatibility in other transaction profiles, or the UE can establish this QoS flow in the same SLRB as other QoS flows indicated by non-backward compatibility in other transaction profiles.

[0224] Optionally, UEs in RRC IDLE / INACTIVE state obtain DRB configuration through SIB, while UEs in OOC state obtain DRB configuration through pre-configuration.

[0225] In some embodiments, the UE determines that at least one associated QoS flow in the DRB configuration corresponds to a TX profile indicating backward compatibility, and the UE uses PDCP multiplexing or uses a single carrier.

[0226] Optionally, UEs in RRC IDLE / INACTIVE state obtain DRB configuration through SIB, while UEs in OOC state obtain DRB configuration through pre-configuration.

[0227] As an example, if the UE determines that at least one associated QoS flow in the DRB configuration corresponds to a tx profile indicating backward compatibility, the UE can either use PDCP multiplexing or transmit this DRB using a single carrier. Specifically, whether to enable the PDCP multiplexing mechanism is left to the UE implementation. If the UE uses PDCP multiplexing, the legacy carrier must be at least one of the carriers. If the UE uses single-carrier transmission, only the legacy carrier can be used as a single carrier.

[0228] In some embodiments, the UE can decide, based on its implementation, how to handle the issue of different tx profiles corresponding to the QoS flows associated with the DRB configuration.

[0229] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0230] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0231] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0232] Figure 4A This is a schematic diagram of the terminal structure proposed in an embodiment of this disclosure. For example... Figure 4A As shown, terminal 4100 may include at least one of a transceiver module 4101, a processing module 4102, etc. In some embodiments, the transceiver module is configured to acquire first information, the first information including a mapping relationship between at least one Quality of Service (QoS) stream of the terminal and a sidelink SL radio bearer (RB), and configuration information of the SL RB; the processing module is configured to determine the transmission attribute corresponding to each QoS stream in at least one QoS stream, wherein at least one QoS stream in at least one QoS stream has a transmission attribute different from the other QoS streams; the processing module is further configured to establish multiple SL RBs based on the first information; wherein one or more QoS streams mapped to the same SL RB have the same transmission attribute.

[0233] Optionally, the transceiver module is used to perform at least one of the communication steps (such as step S2101, but not limited thereto) performed by terminal 101 in any of the above methods, which will not be described in detail here.

[0234] Optionally, the above processing module is used to execute at least one of the other steps (such as step S2102, step S2103, step S2104, but not limited thereto) executed by terminal 101 in any of the above methods, which will not be elaborated here.

[0235] Figure 4B This is a schematic diagram of the structure of another terminal proposed in an embodiment of this disclosure. For example... Figure 4B As shown, terminal 4200 may include at least one of a transceiver module 4201, a processing module 4202, etc. In some embodiments, the transceiver module is configured to acquire first information, the first information including a mapping relationship between at least one Quality of Service (QoS) stream of the terminal and a sidelink SL radio bearer (RB), and configuration information of the SL RB; the processing module is configured to determine the transmission attribute corresponding to each QoS stream in at least one QoS stream, the transmission attribute being backward compatible or non-backward compatible, wherein at least one QoS stream in at least one QoS stream has a transmission attribute different from the other QoS streams; the processing module is further configured to determine that at least one QoS stream mapped to the SL RB includes at least one QoS stream with a backward compatible transmission attribute, determine that the SL RB is transmitted via a single carrier and the single carrier is an existing / traditional carrier, or determine that the SL RB is transmitted using a Packet Data Convergence Protocol (PDCP) multiplexing mechanism.

[0236] Optionally, the transceiver module is used to perform at least one of the communication steps (such as step S2201, but not limited thereto) performed by terminal 101 in any of the above methods, which will not be described in detail here.

[0237] Optionally, the above processing module is used to execute at least one of the other steps (such as step S2202, step S2203, step S2204, but not limited thereto) executed by terminal 101 in any of the above methods, which will not be elaborated here.

[0238] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0239] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0240] Figure 5AThis is a schematic diagram of the structure of the communication device 5100 proposed in this embodiment. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0241] like Figure 5A As shown, the communication device 5100 includes one or more processors 5101. The processor 5101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. The communication device 5100 is used to execute any of the above methods.

[0242] In some embodiments, the communication device 5100 further includes one or more memories 5102 for storing instructions. Optionally, all or part of the memories 5102 may also be located outside the communication device 5100.

[0243] In some embodiments, the communication device 5100 further includes one or more transceivers 5103. When the communication device 5100 includes one or more transceivers 5103, the transceivers 5103 perform at least one of the communication steps such as sending and / or receiving in the above method, and the processor 5101 performs at least one of the other steps.

[0244] In some embodiments, a transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, etc., may be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., may be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., may be used interchangeably.

[0245] In some embodiments, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5102, and the interface circuit 5104 can be used to receive signals from the memory 5102 or other devices, and can be used to send signals to the memory 5102 or other devices. For example, the interface circuit 5104 can read instructions stored in the memory 5102 and send the instructions to the processor 5101.

[0246] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may vary. Figure 5A The limitations. The communication device can be a standalone device or part of a larger device. For example, the communication device can be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally including storage components 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, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0247] Figure 5B This is a schematic diagram of the structure of chip 5200 according to an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, please refer to... Figure 5B The diagram shown is a schematic representation of the structure of chip 5200, but it is not limited to this.

[0248] Chip 5200 includes one or more processors 5201, which are used to perform any of the above methods.

[0249] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, the interface circuit 5202 is connected to memory 5203, and the interface circuit 5202 can be used to receive signals from memory 5203 or other devices, and the interface circuit 5202 can be used to send signals to memory 5203 or other devices. For example, the interface circuit 5202 can read instructions stored in memory 5203 and send the instructions to processor 5201.

[0250] In some embodiments, the interface circuit 5202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2201, but not limited thereto), and the processor 5201 performs at least one of other steps (e.g., steps S2102, S2103, S2104, S2202, S2203, S2204, but not limited thereto).

[0251] In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.

[0252] In some embodiments, chip 5200 further includes one or more memories 5203 for storing instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200.

[0253] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 5100, cause the communication device 5100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0254] This disclosure also provides a program product that, when executed by the communication device 5100, causes the communication device 5100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0255] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

[0256] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. 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 transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0257] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0258] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0259] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A side-link communication method, characterized in that, The method is executed by a terminal, and the method includes: Obtain first information, the first information including sidelink SL radio bearer RB configuration information, the SL RB configuration information including at least one quality of service (QoS) flow mapping relationship with SL RB; Determine the transmission attribute corresponding to each QoS flow in the at least one QoS flow, wherein at least one QoS flow in the at least one QoS flow has a transmission attribute that is different from the other QoS flows, and the transmission attribute is backward compatible or non-backward compatible; Based on the first information, one or more SL RBs are established; wherein, QoS flows mapped to the same SL RB have the same transmission attributes; The method further includes: Obtain the transmission attributes corresponding to the at least one QoS flow from the higher layer; Determine whether the transmission attribute of a QoS flow without associated transmission attributes is backward compatible, or determine whether the transmission attribute of a QoS flow without associated transmission attributes is non-backward compatible.

2. The method according to claim 1, characterized in that, The method further includes: Map at least one QoS flow without associated transmission attributes to the same SL RB; or, Map at least one QoS flow without associated transmission attributes to the same SL RB along with at least one QoS flow whose transmission attributes are backward compatible; or, Map at least one QoS flow without associated transmission attributes to the same SL RB as at least one QoS flow with a non-backward compatible transmission attribute.

3. The method according to any one of claims 1-2, characterized in that, The terminal is in the Radio Resource Control (RRC) idle state or inactive state, or the terminal is in the Out of Coverage (OOC) state.

4. The method according to claim 3, characterized in that, The acquisition of the first information includes: The first information is obtained through the System Information Block (SIB), wherein the terminal is in a Radio Resource Control (RRC) idle state or an inactive state; or... The first information is obtained through pre-configuration, wherein the terminal is in an OOC state.

5. A side-link communication method, characterized in that, The method is executed by a terminal, and the method includes: Obtain first information, the first information including sidelink SL radio bearer RB configuration information, the SL RB configuration information including at least one quality of service (QoS) flow mapping relationship with SL RB; Determine the transmission attribute corresponding to each QoS flow in the at least one QoS flow, wherein the transmission attribute is backward compatible or non-backward compatible, and at least one QoS flow in the at least one QoS flow has a transmission attribute that is different from the other QoS flows; It is determined that at least one QoS flow mapped to the SL RB includes at least one QoS flow with backward compatible transmission attributes, and that the SL RB is transmitted via a single carrier and the single carrier is a traditional carrier, or that the SL RB is transmitted using the Packet Data Convergence Protocol (PDCP) multiplexing mechanism. The method further includes: Obtain the transmission attributes corresponding to the at least one QoS flow from the higher layer; Determine whether the transmission attribute of a QoS flow without associated transmission attributes is backward compatible, or determine whether the transmission attribute of a QoS flow without associated transmission attributes is non-backward compatible.

6. The method according to claim 5, characterized in that, The method further includes: The SL RB is determined to be transmitted using the Packet Data Convergence Protocol (PDCP) multiplexing mechanism, with the traditional carrier being at least one of the carriers used in the PDCP multiplexing mechanism, and the traditional carrier being used to transmit the SL RB.

7. The method according to any one of claims 5-6, characterized in that, The terminal is in the Radio Resource Control (RRC) idle state or inactive state, or the terminal is in the Out of Coverage (OOC) state.

8. The method according to claim 7, characterized in that, The acquisition of the first information includes: The first information is obtained through the System Information Block (SIB), wherein the terminal is in an RRC idle state or an inactive state; or, The first information is obtained through pre-configuration, wherein the terminal is in an OOC state.

9. A terminal, characterized in that, The terminal includes: The transceiver module is used to acquire first information, the first information including sidelink SL radio bearer RB configuration information, the SL RB configuration information including at least one quality of service (QoS) flow mapping relationship with SL RB; The processing module is configured to determine the transmission attribute corresponding to each QoS flow in the at least one QoS flow, wherein at least one QoS flow in the at least one QoS flow has a transmission attribute that is different from the other QoS flows, and the transmission attribute is backward compatible or non-backward compatible. The processing module is further configured to establish multiple SLRBs based on the first information; wherein one or more QoS flows mapped to the same SLRB have the same transmission attribute; The terminal is also used for: Obtain the transmission attributes corresponding to the at least one QoS flow from the higher layer; Determine whether the transmission attribute of a QoS flow without associated transmission attributes is backward compatible, or determine whether the transmission attribute of a QoS flow without associated transmission attributes is non-backward compatible.

10. A terminal, characterized in that, The terminal includes: The transceiver module is used to acquire first information, the first information including sidelink SL radio bearer RB configuration information, the SL RB configuration information including at least one quality of service (QoS) flow mapping relationship with SL RB; The processing module is configured to determine the transmission attribute corresponding to each QoS flow in the at least one QoS flow, wherein the transmission attribute is backward compatible or non-backward compatible, and at least one QoS flow in the at least one QoS flow has a transmission attribute that is different from the other QoS flows; The processing module is further configured to determine that at least one QoS flow mapped to the SL RB includes at least one QoS flow with backward compatibility transmission attribute, determine that the SL RB is transmitted via a single carrier and the single carrier is a traditional carrier, or determine that the SL RB is transmitted using the Packet Data Convergence Protocol (PDCP) multiplexing mechanism. The terminal is also used for: Obtain the transmission attributes corresponding to the at least one QoS flow from the higher layer; Determine whether the transmission attribute of a QoS flow without associated transmission attributes is backward compatible, or determine whether the transmission attribute of a QoS flow without associated transmission attributes is non-backward compatible.

11. A terminal, characterized in that, The terminal includes: One or more processors; The terminal is used to execute the side link communication method according to any one of claims 1-4 or 5-8.

12. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the information processing method as described in any one of claims 1-4 or 5-8.

Images