Sidelink communication method and apparatus

Abstract

Disclosed in the embodiments of the present disclosure are a sidelink communication method and apparatus. By means of acquiring first information, which comprises a mapping relationship between at least one QoS flow of a terminal and an SL RB and configuration information of the SL RB; determining a Tx profile corresponding to each QoS flow among the at least one QoS flow, wherein the Tx profile corresponding to at least one QoS flow among the at least one QoS flow is different from the Tx profiles corresponding to the remaining QoS flows; establishing a plurality of SL RBs on the basis of the first information, wherein the Tx profile(s) corresponding to one or more QoS flows mapped to the same SL RB is / are the same; or when at least one QoS flow mapped to the SL RB comprises at least one QoS flow having a backward compatible Tx profile, determining to send the SL RB by means of a single legacy carrier, or determining to use a PDCP duplication mechanism to send the SL RB, the terminal can establish a plurality of radio bearers on the basis of the attribute of a service or determine to send carriers of the corresponding radio bearers, thereby effectively ensuring the backward compatibility of a service flow and improving the reliability of service transmission.

Description

Sidelink communication method and device Technical Field

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

[0002] To support direct communication between terminals, sidelink (SL) communication was introduced. Carrier aggregation (CA) was introduced to meet the demand for increased system capacity. With the continuous development of technology, terminal and service versions are constantly iterating. To ensure service compatibility, the transmission attribute (TxProfile) was introduced to indicate the service version number.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a sidelink communication method and apparatus.

[0005] An embodiment of the first aspect of the present disclosure proposes a side link communication method, which includes: obtaining first information, the first information including side link SL wireless bearer RB configuration information, the SL RB configuration information including a mapping relationship between at least one quality of service QoS flow and the SL RB; determining the sending attributes corresponding to each QoS flow in the at least one QoS flow, wherein the sending attributes corresponding to at least one QoS flow in the at least one QoS flow are different from those of the other QoS flows; establishing multiple SL RBs based on the first information; wherein the sending attributes corresponding to one or more QoS flows mapped to the same SL RB are the same.

[0006] The second aspect embodiment of the present disclosure proposes a side link communication method, which includes: obtaining first information, the first information includes side link SL wireless bearer RB configuration information, and the SL RB configuration information includes a mapping relationship between at least one quality of service QoS flow and the SL RB; determining the sending attributes corresponding to each QoS flow in the at least one QoS flow, the sending attributes are backward compatible or non-backward compatible, wherein the sending attributes corresponding to at least one QoS flow in the at least one QoS flow are different from those of the remaining QoS flows; determining that at least one QoS flow mapped to the SL RB includes at least one QoS flow with a backward compatible sending attribute, determining that the SL RB is sent through a single carrier and the single carrier is an existing / traditional carrier, or determining that the SL RB is sent using the packet data convergence protocol PDCP multiplexing mechanism.

[0007] An embodiment of the third aspect of the present disclosure proposes a terminal, which includes: a transceiver module for obtaining first information, wherein the first information includes side link SL radio bearer RB configuration information, and the SL RB configuration information includes a mapping relationship between at least one quality of service QoS flow and the SL RB; a processing module for determining the sending attributes corresponding to each QoS flow in the at least one QoS flow, wherein the sending attributes corresponding to at least one QoS flow in the at least one QoS flow are different from those of the other QoS flows; the processing module is also used to establish multiple SL RBs based on the first information; wherein the sending attributes corresponding to one or more QoS flows mapped to the same SL RB are the same.

[0008] The fourth aspect embodiment of the present disclosure proposes a terminal, the above-mentioned network device: a transceiver module, used to obtain first information, the above-mentioned first information includes side link SL wireless bearer RB configuration information, the above-mentioned SL RB configuration information includes at least one mapping relationship between quality of service QoS flow and SL RB; a processing module, used to determine the sending attributes corresponding to each QoS flow in the above-mentioned at least one QoS flow, the above-mentioned sending attributes are backward compatible or non-backward compatible, wherein the sending attributes corresponding to at least one QoS flow in the above-mentioned at least one QoS flow are different from those of the other QoS flows; the above-mentioned processing module is also used to determine that at least one QoS flow mapped to the above-mentioned SL RB includes at least one QoS flow with backward compatible sending attributes, determine that the above-mentioned SL RB is sent through a single carrier and the above-mentioned single carrier is an existing / traditional carrier, or determine that the above-mentioned SL RB is sent using the packet data convergence protocol PDCP multiplexing mechanism.

[0009] The solution proposed in the embodiment of the present disclosure is to obtain first information, the first information includes SL RB configuration information, the SL RB configuration information includes a mapping relationship between at least one QoS flow and the SL RB; determine the sending attributes corresponding to each QoS flow in at least one QoS flow, wherein the sending attributes corresponding to at least one QoS flow in at least one QoS flow are different from those of the other QoS flows; establish multiple SL RBs based on the first information; wherein the sending attributes corresponding to one or more QoS flows mapped to the same SL RB are the same, or, in the case that at least one QoS flow mapped to the SL RB includes at least one QoS flow with a backward-compatible sending attribute, determine to send the SL RB through a single carrier and the single carrier is an existing / traditional carrier, or determine to send the SL RB using the packet data convergence protocol PDCP multiplexing mechanism, so that the terminal can establish multiple wireless bearers based on the attributes of the service or determine the carrier to send the corresponding wireless bearer, effectively ensuring the backward compatibility of the service flow and improving the reliability of service transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0011] FIG1A is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

[0012] FIG1B is a schematic diagram of a sidelink communication network state provided by an embodiment of the present disclosure;

[0013] FIG1C is a schematic diagram of a PDCP multiplexing mechanism provided by an embodiment of the present disclosure;

[0014] 2A-2B are interactive schematic diagrams of a sidelink communication method provided by an embodiment of the present disclosure;

[0015] 3A-3D are flowcharts of a sidelink communication method provided by an embodiment of the present disclosure;

[0016] FIG4A is a schematic structural diagram of a terminal provided by an embodiment of the present disclosure;

[0017] FIG4B is a schematic structural diagram of another terminal provided by an embodiment of the present disclosure;

[0018] FIG5A is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure;

[0019] FIG5B is a schematic structural diagram of a chip provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0020] The embodiments of the present disclosure provide a sidelink communication method and apparatus.

[0021] In a first aspect, an embodiment of the present disclosure provides a sidelink communication method, the method comprising:

[0022] Acquire first information, where the first information includes sidelink (SL) radio bearer (RB) configuration information, and the SL RB configuration information includes a mapping relationship between at least one quality of service (QoS) flow and the SL RB;

[0023] Determining a sending attribute corresponding to each QoS flow in the at least one QoS flow, wherein the sending attribute corresponding to at least one QoS flow in the at least one QoS flow is different from that of the remaining QoS flows;

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

[0025] In the above embodiment, the terminal can establish multiple radio bearers based on the attributes of the service, so that the QoS flows contained in each radio bearer are associated with the same transmission attributes, effectively ensuring the backward compatibility of the service flow and improving the reliability of service transmission.

[0026] With reference to some embodiments of the first aspect, in some embodiments, the sending attribute is backward compatible or non-backward compatible.

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

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

[0029] Mapping at least one QoS flow without associated transmission attributes and at least one QoS flow with backward-compatible transmission attributes to the same SL RB; or,

[0030] At least one QoS flow without associated transmission attributes and at least one QoS flow with non-backward-compatible transmission attributes are mapped to the same SL RB.

[0031] In combination with some embodiments of the first aspect, in some embodiments, the terminal is in a radio resource control RRC idle state or an inactive state, or the terminal is in an out-of-network coverage OOC state.

[0032] With reference to some embodiments of the first aspect, in some embodiments, obtaining the first information includes:

[0033] The first information is obtained through a system information block SIB, wherein the terminal is in a radio resource control RRC idle state or an inactive state; or

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

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

[0036] Obtaining, from a higher layer, a sending attribute corresponding to the at least one QoS flow;

[0037] It is determined that the sending attribute corresponding to the QoS flow without associated sending attribute is backward compatible, or it is determined that the sending attribute corresponding to the QoS flow without associated sending attribute is not backward compatible.

[0038] In a second aspect, an embodiment of the present disclosure provides a sidelink communication method, the method comprising:

[0039] Acquire first information, where the first information includes sidelink (SL) radio bearer (RB) configuration information, and the SL RB configuration information includes a mapping relationship between at least one quality of service (QoS) flow and the SL RB;

[0040] Determining a transmission attribute corresponding to each QoS flow in the at least one QoS flow, where the transmission attribute is backward compatible or non-backward compatible, wherein the transmission attribute corresponding to at least one QoS flow in the at least one QoS flow is different from that of the remaining QoS flows;

[0041] Determine that 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 sent through a single carrier and the single carrier is an existing / traditional traditional carrier, or determine that the SL RB is sent using the Packet Data Convergence Protocol PDCP multiplexing mechanism.

[0042] In the above embodiment, the terminal is enabled to determine the carrier for sending the corresponding radio bearer based on the attributes of the service, which effectively ensures the backward compatibility of the service flow and improves the reliability of service transmission.

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

[0044] It is determined to adopt a Packet Data Convergence Protocol (PDCP) multiplexing mechanism to send the SL RB, an existing / legacy carrier is used as at least one of the carriers used by the PDCP multiplexing mechanism, and the existing / legacy carrier is used to send the SL RB.

[0045] In combination with some embodiments of the second aspect, in some embodiments, the terminal is in a radio resource control RRC idle state or an inactive state, or the terminal is in an out-of-network coverage OOC state.

[0046] With reference to some embodiments of the second aspect, in some embodiments, obtaining the first information includes:

[0047] Acquiring the first information through a system information block SIB, wherein the terminal is in an RRC idle state or an inactive state; or

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

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

[0050] Obtaining, from a higher layer, a sending attribute corresponding to the at least one QoS flow;

[0051] It is determined that the sending attribute corresponding to the QoS flow without associated sending attribute is backward compatible, or it is determined that the sending attribute corresponding to the QoS flow without associated sending attribute is not backward compatible.

[0052] In a third aspect, an embodiment of the present disclosure proposes a terminal, which includes a transceiver module and a processing module; wherein the terminal is used to execute the first aspect and the optional implementation method of the first aspect.

[0053] In a fourth aspect, an embodiment of the present disclosure proposes a terminal, which includes a transceiver module and a processing module; wherein the terminal is used to execute the second aspect and the optional implementation method of the second aspect.

[0054] In a fifth aspect, an embodiment of the present disclosure proposes a terminal, comprising: one or more processors; wherein the terminal is used to execute the first aspect and the optional implementation method of the first aspect.

[0055] In a sixth aspect, an embodiment of the present disclosure proposes a terminal, comprising: one or more processors; wherein the terminal is used to execute the second aspect and the optional implementation method of the second aspect.

[0056] In the seventh aspect, an embodiment of the present disclosure proposes a communication system, which includes: a terminal, a terminal; wherein the terminal is configured to execute the method described in the first aspect and the optional implementation of the first aspect, and the terminal is configured to execute the method described in the second aspect and the optional implementation of the second aspect.

[0057] In an eighth aspect, an embodiment of the present disclosure proposes a storage medium, wherein the storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.

[0058] In a ninth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.

[0059] In a tenth 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 first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.

[0060] In an eleventh aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in accordance with the first aspect and its optional implementation, the second aspect and its optional implementation.

[0061] It is understandable that the above-mentioned terminals, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0062] The present disclosure provides a sidelink communication method and apparatus. In some embodiments, the terms "sidelink communication method," "sidelink communication method," and "communication method" are interchangeable; the terms "sidelink communication apparatus," "sidelink communication apparatus," and "communication apparatus" are interchangeable; and the terms "sidelink communication system," "communication system," and "communication system" are interchangeable.

[0063] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain 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 certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, 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 steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0064] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0065] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0066] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0067] In the embodiments of the present disclosure, “plurality” refers to two or more.

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

[0069] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on 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); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0070] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on 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). The above is also applicable when there are more branches such as A, B, C, etc.

[0071] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then 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", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0072] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0073] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0074] In some embodiments, 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 less 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", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0075] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

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

[0077] 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", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or 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 (BWP)", etc.

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

[0079] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

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

[0081] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0082] FIG1A is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0083] As shown in FIG1A , a communication system 100 includes a terminal 101 and a network device 102 .

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

[0085] In some embodiments, the network device 102 is, for example, a node or device that accesses the terminal to a wireless network. The network device may include a node in a sidelink communication network, an evolved NodeB (eNB) in a 5G communication system, a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (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 base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

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

[0087] In some embodiments, the network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0088] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating 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. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0089] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0090] The embodiments of the present disclosure 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 systems (4G), 5th generation mobile communication systems (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 (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) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0091] In some embodiments, in order to support direct communication between terminals, a sidelink (SL) communication mode is introduced. The interface between terminals is PC-5 (a bottom-layer direct cellular communication protocol interface). Terminal devices in network coverage (in coverage) and out of network coverage (out of coverage, OOC) can both perform sidelink communication. For example, as shown in Figure 1B, the first terminal in coverage can perform sidelink communication with the second terminal in coverage. Alternatively, the first terminal in coverage can perform sidelink communication with the second terminal of OOC. Alternatively, the first terminal of OOC can perform sidelink communication with the second terminal of OOC. Among them, the terminal devices in coverage can be in a radio resource control (RRC) connected state (CONNECETED) or an RRC idle state (IDLE) or an RRC inactive state (INACTIVE). The sidelink communication performed by the terminal devices includes three transmission modes: unicast, multicast and broadcast.

[0092] In some embodiments, as terminal and service versions continue to evolve, LTE V2X defines a transmission profile (TxProfile) to indicate the service version number to ensure backward compatibility. For example, R17NR V2X introduces the discontinuous reception (DRX) feature. To ensure backward compatibility, for example, to ensure that older version terminals can receive broadcast / multicast services from R17 terminals, a TxProfile is defined for broadcast / multicast services at the Layer 2 (L2) identifier (ID) granularity. The TxProfile indicates whether the associated broadcast / multicast service supports DRX. If the transmitting terminal determines that a broadcast / multicast service supports DRX, it assumes that the receiving terminal has DRX enabled and transmits data only during the receiving terminal's "active" time. The receiving terminal only enables DRX when it determines that all broadcast / multicast services of interest support DRX, waking up to listen for broadcast / multicast service data only during the "active" time.

[0093] In some embodiments, in order 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 the 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 old version R16 / R17 terminals can receive broadcast / multicast services sent by R18 terminals that support carrier aggregation.

[0094] 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 sending a single data packet repeatedly. Using this mechanism for repeated transmission can improve data packet transmission reliability, reduce the latency of repeated transmissions, and meet the requirements of Ultra-Reliable Low-Latency Communications (URLLC). If the PDCP duplication mechanism is not employed, a PDCP packet is transmitted to a Radio Link Control (RLC) entity, which processes it and then sends it to the Media Access Control (MAC) layer, which schedules the data. If the PDCP duplication mechanism is employed, a PDCP packet is transmitted to at least two RLC entities, such as the primary and secondary RLC entities shown in FIG1C . Each RLC entity independently processes the packet and transmits it to the MAC layer. From the MAC layer's perspective, these are two independent packets. The MAC layer cannot identify whether this is a packet transmitted by PDCP duplication. The MAC layer only needs to schedule according to the algorithm. It should be noted that in the CA scenario, the protocol requires that the two packets of PDCP duplication be transmitted on different logical channels (LCH) in different cells, for example, the primary LCH and secondary LCH shown in Figure 1C. On the NR Uu interface, the LCH used for PDCP duplication is configured to the terminal by the network side through RB configuration. Network equipment can configure whether an RB enables PDCP duplication through SL RB configuration.

[0095] In some embodiments, the network device can configure a SL radio bearer (Radio Bearer, RB) for a UE in a radio resource control (Radio Resources Control, RRC) connection state through a side link radio bearer configuration SL-RadioBearerConfig. The SL-RadioBearerConfig configuration includes a service data adaptation protocol (Service Data Adaptation Protocol, SDAP) configuration, and the SDAP configuration includes a quality of service (Quality of Service, QoS) flow associated with this SL RB.

[0096] In some embodiments, if the network device does not know the TxProfile associated with a QoS flow, it may map the backward-compatible QoS flow and the non-backward-compatible QoS flow into one SL RB. In this case, if the network configures the PDCP duplication of the SL RB to be disabled, the terminal is not required to use the legacy carrier, which can also be called the existing carrier (the existing / legacy carrier supported by R16 / R17). When the terminal does not use the legacy carrier, the backward-compatible QoS flow contained in this RB can only be transmitted through the new carrier, and the R16 / R17 terminal cannot receive this QoS flow.

[0097] The sidelink communication method and apparatus provided by the present disclosure are described in detail below with reference to the accompanying drawings.

[0098] FIG2A is an interactive diagram of a sidelink communication method according to an embodiment of the present disclosure. As shown in FIG2A , the embodiment of the present disclosure relates to a sidelink communication method, the method comprising:

[0099] Step S2101: Terminal 101 obtains first information.

[0100] In some embodiments, the terminal 101 is in a Radio Resources Control (RRC) idle state (IDLE) or an inactive state (INACTIVE), or the terminal 101 is in an out of coverage (OOC) state.

[0101] In some embodiments, the terminal 101 is in an RRC idle state or an inactive state, and the terminal 101 obtains the above-mentioned first information through a system information block (System Information Block, SIB).

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

[0103] In some embodiments, the first information includes sidelink (SL) radio bearer (RB) configuration information, and the SLRB configuration information includes a mapping relationship between at least one quality of service (QoS) flow and the SLRB.

[0104] It can be understood that the above-mentioned SL RB refers to the SL RB configured by the SL RB configuration information.

[0105] In some embodiments, the above-mentioned SL RB may also be a data radio bearer (DRB).

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

[0107] Optionally, the first information includes one or more of the SL RB configurations (for example, at least one of SDAP configuration, PDCP configuration, RLC configuration, MAC configuration, etc.).

[0108] In some embodiments, the name of the above-mentioned first information is not limited, and it can be, for example, "sidelink radio bearer configuration", "service data adaptation protocol configuration", "sidelink configuration", "radio bearer configuration", etc.

[0109] Step S2102: Terminal 101 obtains a sending attribute associated with at least one QoS flow.

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

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

[0112] In some embodiments, the access stratum (AS) of the terminal 101 obtains the association relationship between at least one QoS flow and the sending attribute from the higher layer of the terminal 101 .

[0113] In some embodiments, the aforementioned sending attributes are backward compatible or non-backward compatible.

[0114] It is understandable that the QoS flow with the backward compatibility attribute refers to the QoS flow that can be received by the old version terminal of R16 / R17.

[0115] In step S2103, the terminal 101 determines the sending attributes corresponding to each QoS.

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

[0117] In some embodiments, the terminal 101 determines that among at least one QoS flow associated with the above-mentioned SLRB (an SL RB configured by SLRB configuration information), there is at least one QoS flow whose corresponding sending attribute is different from that of the other QoS flows.

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

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

[0120] Step S2104: Terminal 101 establishes SL RB.

[0121] In some embodiments, the terminal 101 establishes the SL RB based on the first information and / or the transmission attributes associated with at least one QoS flow obtained by the terminal 101. Exemplarily, the terminal 101 establishes the SL RB based on the SLRB configuration included in the first information and / or the transmission attributes associated with at least one QoS flow obtained by the terminal 101.

[0122] In some embodiments, the terminal 101 establishes multiple SL RBs based on the first information. The transmission attributes corresponding to one or more QoS flows mapped to the same SL RB are the same. Exemplarily, the terminal 101 establishes multiple SL RBs based on an SLRB configuration included in the first information and / or the transmission attributes associated with at least one QoS flow obtained by the terminal 101. The transmission attributes corresponding to the QoS flows mapped to the same SL RB are the same.

[0123] As an example, the first information includes the configurations of three SL RBs ABC. For configuration A, the terminal 101 determines that the transmission attributes of at least one QoS flow corresponding to the SL RB of configuration A are different, and the terminal 101 can establish multiple SL RBs based on the configuration A, wherein the transmission attributes of at least one QoS flow corresponding to each SL RB are the same. Similarly, for configuration B, the terminal 101 determines that the transmission attributes of at least one QoS flow corresponding to the SL RB of configuration B are different, and the terminal 101 can establish multiple SL RBs based on the configuration B, wherein the transmission attributes of at least one QoS flow corresponding to each SL RB are the same. For configuration C, the terminal 101 determines that the transmission attributes of at least one QoS flow corresponding to the SL RB of configuration C are different, and the terminal 101 can establish multiple SL RBs based on the configuration C, wherein the transmission attributes of at least one QoS flow corresponding to each SL RB are the same.

[0124] In some embodiments, the terminal 101 may map at least one QoS flow with a transmission attribute of backward compatibility to one or more SL RBs.

[0125] In some embodiments, the terminal 101 may map at least one QoS flow whose transmission attribute is non-backward compatible to one or more SL RBs.

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

[0127] In some embodiments, QoS flows with different transmission attributes are mapped to different SL RBs.

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

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

[0130] In some embodiments, one or more SL RBs mapped to at least one QoS flow with a backward-compatible transmission attribute may be transmitted using a single carrier, where the single carrier is an existing / legacy carrier. Specifically, the existing / legacy carrier refers to an SL carrier supported by an R16 / R17 terminal.

[0131] In some embodiments, one or more SL RBs mapped to at least one QoS flow with a sending attribute of backward compatibility may be transmitted using a PDCP multiplexing mechanism, wherein at least one of the carriers used by the PDCP multiplexing mechanism is an existing / legacy (lagacy) carrier.

[0132] In some embodiments, terms such as "carrier", "band", and "frequency" can be used interchangeably.

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

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

[0136] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0137] In some embodiments, terms such as "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.

[0138] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0139] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0140] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0141] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or 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 thereto.

[0142] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2104. For example, step 2101 can be implemented as an independent embodiment, steps 2102 and 2103 can be implemented as independent embodiments, step 2104 can be implemented as an independent embodiment, steps 2103 and 2104 can be implemented as independent embodiments, steps 2102, 2103, and 2104 can be implemented as independent embodiments, steps 2101, 2102, 2103, and 2104 can be implemented as independent embodiments, and so on, but the present invention is not limited thereto.

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

[0144] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2A .

[0145] FIG2B is an interactive diagram of a sidelink communication method according to an embodiment of the present disclosure. As shown in FIG2B , the embodiment of the present disclosure relates to a sidelink communication method, the method comprising:

[0146] Step S2201: Terminal 101 obtains first information.

[0147] In some embodiments, the terminal 101 is in a Radio Resources Control (RRC) idle state (IDLE) or an inactive state (INACTIVE), or the terminal 101 is in an out of coverage (OOC) state.

[0148] In some embodiments, the terminal 101 is in an RRC idle state or an inactive state, and the terminal 101 obtains the above-mentioned first information through a system information block (System Information Block, SIB).

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

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

[0151] In some embodiments, the first information may include configurations of one or more SL RBs.

[0152] Optionally, the first information includes one or more of the SL RB configurations (eg, SDAP configuration, PDCP configuration, MAC configuration, etc.).

[0153] In some embodiments, the name of the above-mentioned first information is not limited, and it can be, for example, "sidelink radio bearer configuration", "service data adaptation protocol configuration", "sidelink configuration", "radio bearer configuration", etc.

[0154] Step S2202: Terminal 101 obtains a sending attribute associated with at least one QoS flow.

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

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

[0157] In some embodiments, the access stratum (AS) of the terminal 101 obtains the association relationship between at least one QoS flow and the sending attribute from the higher layer of the terminal 101 .

[0158] In some embodiments, the aforementioned sending attributes are backward compatible or non-backward compatible.

[0159] It is understandable that the QoS flow with the backward compatibility attribute refers to the QoS flow that can be received by the old version terminal of R16 / R17.

[0160] In step S2203, the terminal 101 determines the sending attributes corresponding to each QoS.

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

[0162] In some embodiments, the terminal 101 determines that among at least one QoS flow associated with the above-mentioned SLRB (an SL RB configured by SLRB configuration information), there is at least one QoS flow whose corresponding sending attribute is different from that of the other QoS flows.

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

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

[0165] In step S2204, the terminal 101 determines the carrier for sending the SL RB.

[0166] In some embodiments, the terminal 101 determines that the at least one QoS flow associated with the SL RB includes at least one QoS flow with a transmission attribute of backward compatibility, wherein the SL RB is a SL RB configured by a SL RB configuration information in the first information.

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

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

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

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

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

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

[0173] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0174] In some embodiments, terms such as "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.

[0175] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0176] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0177] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0178] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or 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 thereto.

[0179] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2204. For example, step 2201 can be implemented as an independent embodiment, steps 2202 and 2203 can be implemented as independent embodiments, step 2204 can be implemented as an independent embodiment, steps 2203 and 2204 can be implemented as independent embodiments, steps 2202, 2203, and 2204 can be implemented as independent embodiments, steps 2201, 2202, 2203, and 2204 can be implemented as independent embodiments, and so on, but the present invention is not limited thereto.

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

[0181] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2B .

[0182] FIG3A is a flow chart of a sidelink communication method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a sidelink communication method, which is executed by terminal 101 and includes:

[0183] Step S3101, obtain first information.

[0184] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0185] Step S3102: Obtain at least one QoS flow-associated sending attribute.

[0186] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0187] Step S3103: Determine the sending attributes corresponding to each QoS.

[0188] The optional implementation of step S3104 can refer to the optional implementation of step S2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0189] Step S3104: Establish SL RB.

[0190] The optional implementation of step S3104 can refer to the optional implementation of step S2104 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0191] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3104. For example, step 3101 can be implemented as an independent embodiment, steps 3102 and 3103 can be implemented as independent embodiments, step 3104 can be implemented as an independent embodiment, steps 3103 and 3104 can be implemented as independent embodiments, steps 3102, 3103, and 3104 can be implemented as independent embodiments, steps 3101, 3102, 3103, and 3104 can be implemented as independent embodiments, and so on, but the present invention is not limited thereto.

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

[0193] FIG3B is a flow chart of a sidelink communication method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a sidelink communication method, which is executed by terminal 101 and includes:

[0194] Step S3201, obtain first information.

[0195] The optional implementation of step S3201 can refer to the optional implementation of step S2201 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0196] Step S3202: Obtain sending attributes associated with at least one QoS flow.

[0197] The optional implementation of step S3202 can refer to the optional implementation of step S2202 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0198] Step S3203: Determine the sending attributes corresponding to each QoS.

[0199] The optional implementation of step S3203 can refer to the optional implementation of step S2203 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0200] Step S3204: determine the carrier for sending the above-mentioned SL RB.

[0201] The optional implementation of step S3204 can refer to the optional implementation of step S2204 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0202] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3204. For example, step 3201 can be implemented as an independent embodiment, steps 3202 and 3203 can be implemented as independent embodiments, step 3204 can be implemented as an independent embodiment, steps 3203 and 3204 can be implemented as independent embodiments, steps 3202, 3203, and 3204 can be implemented as independent embodiments, steps 3201, 3202, 3203, and 3204 can be implemented as independent embodiments, and so on, but the present invention is not limited thereto.

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

[0204] FIG3C is a flow chart of a sidelink communication method according to an embodiment of the present disclosure. As shown in FIG3C , the embodiment of the present disclosure relates to a sidelink communication method, which is executed by terminal 101 and includes:

[0205] Step S3301, obtain first information.

[0206] The optional implementation of step S3301 can refer to the optional implementation of step S2101 in Figure 2A, step S3101 in Figure 3A, and other related parts in the embodiments involved in Figures 2A and 3A, which will not be repeated here.

[0207] Step S3302: Determine the sending attributes corresponding to each QoS.

[0208] The optional implementation of step S3302 can refer to the optional implementation of step S2103 in Figure 2A, step S3103 in Figure 3A, and other related parts in the embodiments involved in Figures 2A and 3A, which will not be repeated here.

[0209] Step S3303: Establish SL RB.

[0210] Optional implementations of step S3303 may refer to step S2104 in FIG. 2A , optional implementations of step S3104 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2A and FIG. 3A , which will not be described in detail here.

[0211] The communication method involved in the embodiments of the present 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, steps 3301+3303 may be implemented as an independent embodiment, steps 3302+3303 may be implemented as an independent embodiment, steps 3301+3302+3303 may be implemented as an independent embodiment, and so on, but the present invention is not limited thereto.

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

[0213] FIG3D is a flow chart of a sidelink communication method according to an embodiment of the present disclosure. As shown in FIG3D , the embodiment of the present disclosure relates to a sidelink communication method, which is executed by terminal 101 and includes:

[0214] Step S3401, obtain first information.

[0215] The optional implementation of step S3401 can refer to the optional implementation of step S2101 in Figure 2B, step S3101 in Figure 3B, and other related parts in the embodiments involved in Figures 2B and 3B, which will not be repeated here.

[0216] Step S3402: Determine the sending attributes corresponding to each QoS.

[0217] Optional implementations of step S3402 can be found in step S2103 of FIG. 2B , optional implementations of step S3103 of FIG. 3B , and other related parts of the embodiments involved in FIG. 2B and FIG. 3B , which will not be described in detail here.

[0218] Step S3403: determine the carrier for sending the above-mentioned SL RB.

[0219] The optional implementation of step S3403 can be found in step S2104 of FIG. 2B , the optional implementation of step S3104 of FIG. 3B , and other related parts in the embodiments involved in FIG. 2B and FIG. 3B , which will not be described in detail here.

[0220] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3401 to S3403. For example, step 3402 may be implemented as an independent embodiment, step 3403 may be implemented as an independent embodiment, steps 3401+3403 may be implemented as an independent embodiment, steps 3402+3403 may be implemented as an independent embodiment, steps 3401+3402+3403 may be implemented as an independent embodiment, and so on, but the present invention is not limited thereto.

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

[0222] The following is an exemplary introduction to the methods described in the above embodiments.

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

[0224] As an example, if the QoS flow in the SIB or pre-configuration is mapped to a DRB, which has been established or not, and the tx profiles associated with these QoS flows are different, the UE can establish more than one SLRB. Exemplarily, the UE establishes QoS flows with the same tx profile attributes in one SLRB, and the UE establishes QoS flows with different tx profile attributes in different SLRBs. If a QoS flow has no associated tx profile, the UE can establish an SLRB for the QoS flow without an associated tx profile, or the UE can establish this QoS flow in the same SLRB with other QoS flows that the tx profile indicates are backward compatible, or the UE can establish this QoS flow in the same SLRB with other QoS flows that the tx profile indicates are not backward compatible.

[0225] Optionally, a UE in RRC IDLE / INACTIVE state obtains DRB configuration through SIB, and a UE in OOC state obtains DRB configuration through pre-configuration.

[0226] In some embodiments, the UE determines that a tx profile corresponding to at least one associated qos flow in the DRB configuration indicates backward compatibility, and the UE uses PDCP multiplexing or a single carrier.

[0227] Optionally, a UE in RRC IDLE / INACTIVE state obtains DRB configuration through SIB, and a UE in OOC state obtains DRB configuration through pre-configuration.

[0228] As an example, the UE determines that the tx profile corresponding to at least one associated QoS flow in the DRB configuration indicates backward compatibility, and the UE uses PDCP multiplexing or single carrier transmission for this DRB. Specifically, whether to enable the PDCP multiplexing mechanism can be left to the UE implementation to decide. If the UE uses PDCP multiplexing, the legacy carrier needs to be used as at least one of the carriers. If the UE uses single carrier transmission, only the legacy carrier can be used as a single carrier transmission.

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

[0230] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0231] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may 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 the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various 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 within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0232] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution 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 relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by 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 implementing the hardware circuit configuration 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. In addition, 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), a deep learning processing unit (DPU), etc.

[0233] Figure 4A is a schematic diagram of the structure of the terminal proposed in an embodiment of the present disclosure. As shown in Figure 4A, the terminal 4100 may include: at least one of a transceiver module 4101, a processing module 4102, etc. In some embodiments, the transceiver module is used to obtain first information, and the first information includes a mapping relationship between at least one quality of service QoS flow of the terminal and a side link SL radio bearer RB, and the configuration information of the SL RB; the processing module is used to determine the sending attributes corresponding to each QoS flow in at least one QoS flow, wherein the sending attributes corresponding to at least one QoS flow in at least one QoS flow are different from those of the other QoS flows; the processing module is also used to establish multiple SL RBs based on the first information; wherein the sending attributes corresponding to one or more QoS flows mapped to the same SL RB are the same.

[0234] Optionally, the above-mentioned 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) performed by the terminal 101 in any of the above methods, which will not be repeated here.

[0235] 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 to these) performed by the terminal 101 in any of the above methods, which will not be repeated here.

[0236] Figure 4B is a schematic diagram of the structure of another terminal proposed in an embodiment of the present disclosure. As shown in Figure 4B, the terminal 4200 may include: at least one of a transceiver module 4201 and a processing module 4202. In some embodiments, the transceiver module is used to obtain first information, the first information including a mapping relationship between at least one quality of service (QoS) flow of the terminal and a sidelink (SL) radio bearer (RB), and configuration information of the SL RB; the processing module is used to determine the transmission attribute corresponding to each QoS flow in at least one QoS flow, the transmission attribute being backward compatible or non-backward compatible, wherein the transmission attribute corresponding to at least one QoS flow in at least one QoS flow is different from that of the other QoS flows; the processing module is also used to determine that 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 through a single carrier and the single carrier is an existing / traditional carrier, or determine that the SL RB is transmitted using the packet data convergence protocol (PDCP) multiplexing mechanism.

[0237] Optionally, the above-mentioned transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (such as step S2201, but not limited to this) performed by the terminal 101 in any of the above methods, which will not be repeated here.

[0238] Optionally, the 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 the terminal 101 in any of the above methods, which will not be repeated here.

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

[0240] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0241] Figure 5A is a schematic diagram of the structure of a communication device 5100 proposed in an embodiment of the present disclosure. Communication device 5100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 5100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0242] As shown in Figure 5A, the communication device 5100 includes one or more processors 5101. The processor 5101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can 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 programs, and process program data. The communication device 5100 is used to perform any of the above methods.

[0243] 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 be located outside the communication device 5100.

[0244] 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 transceiver 5103 performs 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.

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

[0246] 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. The interface circuit 5104 may be configured to receive signals from the memory 5102 or other devices, and may be configured to send signals to the memory 5102 or other devices. For example, the interface circuit 5104 may read instructions stored in the memory 5102 and send the instructions to the processor 5101.

[0247] 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 the present disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be an independent device or may be part of a larger device. For example, 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 or 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, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0248] 5B is a schematic diagram of the structure of a chip 5200 according to an embodiment of the present disclosure. If the communication device 5100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 5200 shown in FIG5B , but the present disclosure is not limited thereto.

[0249] The chip 5200 includes one or more processors 5201 , and the chip 5200 is configured to execute any of the above methods.

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

[0251] In some embodiments, the interface circuit 5202 executes at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S2201, but not limited to this), and the processor 5201 executes at least one of the other steps (for example, step S2102, step S2103, step S2104, step S2202, step S2203, step S2204, but not limited to this).

[0252] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

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

[0254] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 5100, causes the communication device 5100 to execute 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 is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0255] The present disclosure also provides a program product, which, when executed by the communication device 5100, enables the communication device 5100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0256] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

[0257] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of 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 the present 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 transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. 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)).

[0258] Those skilled in the art will appreciate that the units and algorithm steps of each example 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 performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians 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.

[0259] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0260] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A sidelink communication method, characterized in that: The method is executed by a terminal, and includes: Acquire first information, where the first information includes sidelink SL radio bearer RB configuration information, where the SLRB configuration information includes a mapping relationship between at least one quality of service QoS flow and the SLRB; Determine a sending attribute corresponding to each QoS flow in the at least one QoS flow, wherein the sending attribute corresponding to at least one QoS flow in the at least one QoS flow is different from that of the other QoS flows; Based on the first information, one or more SL RBs are established; wherein the sending attributes corresponding to the QoS flows mapped to the same SL RB are the same.

2. The method according to claim 1, characterized in that The sending attribute is backward compatible or non-backward compatible.

3. The method according to claim 2, characterized in that The method further comprises: Mapping at least one QoS flow without associated transmission attributes to the same SL RB; or, Mapping at least one QoS flow without associated transmission attributes and at least one QoS flow with backward-compatible transmission attributes to the same SL RB; or, At least one QoS flow without associated transmission attributes and at least one QoS flow with non-backward compatible transmission attributes are mapped to the same SL RB.

4. The method according to any one of claims 1 to 3, characterized in that: The terminal is in a radio resource control (RRC) idle state or an inactive state, or the terminal is in an out-of-network coverage (OOC) state.

5. The method according to claim 4, characterized in that The obtaining of the first information comprises: The first information is acquired through a 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 preconfiguration, wherein the terminal is in an OOC state.

6. The method according to claims 1-5, characterized in that: The method further comprises: Obtaining, from a high layer, a sending attribute corresponding to the at least one QoS flow; It is determined that the sending attribute corresponding to the QoS flow without associated sending attribute is backward compatible, or it is determined that the sending attribute corresponding to the QoS flow without associated sending attribute is not backward compatible.

7. A sidelink communication method, characterized in that: The method is executed by a terminal, and includes: Acquire first information, where the first information includes sidelink SL radio bearer RB configuration information, where the SLRB configuration information includes a mapping relationship between at least one quality of service QoS flow and the SLRB; Determine a sending attribute corresponding to each QoS flow in the at least one QoS flow, where the sending attribute is backward compatible or non-backward compatible, wherein the sending attribute corresponding to at least one QoS flow in the at least one QoS flow is different from that of the other QoS flows; Determine that 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 sent through a single carrier and the single carrier is a traditional carrier, or determine that the SL RB is sent using a packet data convergence protocol PDCP multiplexing mechanism.

8. The method according to claim 7, characterized in that The method further comprises: It is determined to use a packet data convergence protocol PDCP multiplexing mechanism to send the SL RB, a traditional carrier is used as at least one of the carriers used by the PDCP multiplexing mechanism, and the traditional carrier is used to send the SLRB.

9. The method according to any one of claims 7-8, characterized in that: The terminal is in a radio resource control (RRC) idle state or an inactive state, or the terminal is in an out-of-network coverage (OOC) state.

10. The method according to claim 9, characterized in that The obtaining of the first information comprises: The first information is acquired through a system information block SIB, wherein the terminal is in an RRC idle state or an inactive state; or, The first information is obtained through preconfiguration, wherein the terminal is in an OOC state.

11. The method according to claim 10, characterized in that The method further comprises: Obtaining, from a high layer, a sending attribute corresponding to the at least one QoS flow; It is determined that the sending attribute corresponding to the QoS flow without associated sending attribute is backward compatible, or it is determined that the sending attribute corresponding to the QoS flow without associated sending attribute is not backward compatible.

12. A terminal, characterized in that: The terminal comprises: A transceiver module, configured to obtain first information, wherein the first information includes sidelink SL radio bearer RB configuration information, wherein the SL RB configuration information includes a mapping relationship between at least one quality of service QoS flow and the SL RB; A processing module, configured to determine a sending attribute corresponding to each QoS flow in the at least one QoS flow, wherein the sending attribute corresponding to at least one QoS flow in the at least one QoS flow is different from that of the other QoS flows; The processing module is further used to establish multiple SL RBs based on the first information; wherein the sending attributes corresponding to one or more QoS flows mapped to the same SL RB are the same.

13. A terminal, characterized in that: The terminal comprises: A transceiver module, configured to obtain first information, wherein the first information includes sidelink SL radio bearer RB configuration information, wherein the SL RB configuration information includes a mapping relationship between at least one quality of service QoS flow and the SL RB; a processing module, configured to determine a sending attribute corresponding to each QoS flow in the at least one QoS flow, wherein the sending attribute is backward compatible or non-backward compatible, wherein the sending attribute corresponding to at least one QoS flow in the at least one QoS flow is different from that of the other QoS flows; The processing module is also used to determine that at least one QoS flow mapped to the SL RB includes at least one QoS flow with a sending attribute of backward compatibility, determine that the SL RB is sent through a single carrier and the single carrier is a traditional carrier, or determine that the SL RB is sent using a packet data convergence protocol PDCP multiplexing mechanism.

14. A terminal, characterized in that: The terminal comprises: one or more processors; The terminal is used to execute the side link communication method described in any one of claims 1-6 or 7-11.

15. A storage medium storing instructions, characterized in that: When the instruction is executed on the communication device, the communication device executes the information processing method as described in any one of claims 1-6 or 7-11.

Images