Method for sidewalk communication and communication device

Abstract

A method for sidewalk communication and a communication device are provided. The sidewalk communication method comprises the following steps: a first device determines a first CAPC value for sidewalk communication; wherein the first CAPC value is associated with the PQI. According to the invention, the first CAPC value used for sidewalk communication is determined based on the PQI, and the determination of the CAPC value in the sidewalk communication system is realized.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a method and a communication device for sideline communication. Background Art

[0002] The Uu port communication system based on unlicensed spectrum determines the channel access priority class (CAPC) according to the configuration of the network device. Specifically, the network device can determine the CAPC value by referring to the 5G quality of service identifier (5QI) value. In the sideline communication system based on unlicensed spectrum, there is no suitable technical solution to determine the CAPC value. Summary of the invention

[0003] The present application provides a method and a communication device for sideline communication. The following introduces various aspects involved in the present application.

[0004] In a first aspect, a method for sideline communication is provided, comprising: a first device determines a first CAPC value for sideline communication; wherein the first CAPC value is associated with a PC5 interface quality of service index (PC5 quality of service index, PQI).

[0005] In a second aspect, a communication device is provided, comprising: a determination unit, configured to determine a first CAPC value for sideline communication; wherein the first CAPC value is associated with a PQI.

[0006] In a third aspect, a communication device is provided, comprising a processor and a memory, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the terminal device executes part or all of the steps in the method of the first aspect.

[0007] In a fourth aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned communication device. In another possible design, the system may also include other devices that interact with the communication device in the solution provided by the embodiment of the present application.

[0008] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program enables a terminal to execute part or all of the steps in the methods of the above aspects.

[0009] In a sixth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a terminal to execute some or all of the steps in the above-mentioned various aspects of the method. In some implementations, the computer program product can be a software installation package.

[0010] In a seventh aspect, an embodiment of the present application provides a chip comprising a memory and a processor, wherein the processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0011] The present application proposes to determine a first CAPC value for sideline communication based on PQI, thereby achieving determination of a CAPC value in a sideline communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 It is a schematic diagram of a wireless communication system applied in an embodiment of the present application.

[0013] Figure 2 This is an example diagram of an application scenario of the side communication of the first mode.

[0014] Figure 3 This is an example diagram of an application scenario of the side communication of the second mode.

[0015] Figure 4 A schematic flowchart of a method for sideline communication provided in an embodiment of the present application.

[0016] Figure 5 A schematic flowchart of another method for sideline communication provided in an embodiment of the present application.

[0017] Figure 6 A schematic flowchart of another method for sideline communication provided in an embodiment of the present application.

[0018] Figure 7 A schematic structural diagram of a communication device provided in an embodiment of the present application.

[0019] Figure 8 It is a schematic structural diagram of a device for communication provided in an embodiment of the present application. DETAILED DESCRIPTION

[0020] The following will describe the technical solution in this application in conjunction with the accompanying drawings. Figures 1 to 3 Introduce the terms and communication processes involved in this application.

[0021] Communication System

[0022] Figure 1 1 is an example diagram of a wireless communication system 100 to which an embodiment of the present application is applicable. The wireless communication system 100 may include one or more communication devices. The one or more communication devices may include, for example, a network device 110 and terminals 121 to 129. The network device 110 may provide communication coverage for a specific geographical area and may communicate with terminals located in the coverage area.

[0023] In some implementations, terminal devices can communicate with each other via a sidelink (SL). Sidelink communication can also be called proximity services (ProSe) communication, unilateral communication, sidelink communication, device to device (D2D) communication, through-link communication, etc. The vehicle to everything (V2X) system can also be implemented by terminal to terminal direct communication (i.e., sidelink communication).

[0024] In some implementations, sidelink data may be transmitted between terminal devices via a sidelink. The sidelink data may include data and / or control signaling. In some implementations, the sidelink data may be, for example, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a PSCCH demodulation reference signal (DMRS), a PSSCH DMRS, a PSFCH, a sidelink synchronization signal block (S-SSB), etc., wherein the S-SSB includes a sidelink primary synchronization signal (S-PSS), a sidelink secondary synchronization signal (S-SSS) and a physical sidelink broadcast channel (PSBCH).

[0025] Unlike traditional cellular systems where communication data is received or sent through network devices, sideline communication systems (such as vehicle networking systems) use direct communication between terminal devices. Therefore, sideline communication has higher spectrum efficiency and lower transmission delay.

[0026] Combined with the following Figure 1 This section introduces several common sidelink communication scenarios. In sidelink communication, there are three scenarios depending on whether the terminal in the sidelink is within the coverage of the network device. Scenario 1: The terminal performs sidelink communication within the coverage of the network device. Scenario 2: Some terminals perform sidelink communication within the coverage of the network device. Scenario 3: The terminal performs sidelink communication outside the coverage of the network device.

[0027] like Figure 1 As shown, in scenario 1, terminals 121-122 can communicate through the side link, and terminals 121-122 are all within the coverage of network device 110, or in other words, terminals 121-122 are all within the coverage of the same network device 110. In this scenario, network device 110 can send configuration signaling to terminals 121-122, and accordingly, terminals 121-122 communicate through the side link based on the configuration signaling.

[0028] like Figure 1 As shown, in scenario 2, terminals 123 to 124 can communicate via a side link, and terminal 123 is within the coverage of network device 110, while terminal 124 is outside the coverage of network device 110. In this scenario, terminal 123 receives configuration information from network device 110 and communicates via a side link based on the configuration of the configuration signaling. However, for terminal 124, since terminal 124 is outside the coverage of network device 110, it is unable to receive the configuration information of network device 110. At this time, terminal 124 can obtain the configuration of the side link communication based on the configuration information according to the pre-configuration and / or the configuration information sent by terminal 123 within the coverage, so as to communicate with terminal 123 via the side link based on the acquired configuration.

[0029] In some cases, terminal 123 may send the above configuration information to terminal 124 via a physical sidelink broadcast channel (PSBCH) to configure terminal 124 to communicate via the sidelink.

[0030] like Figure 1 As shown, in scenario 3, terminals 125-129 are all outside the coverage of network device 110 and cannot communicate with network device 110. In this case, the terminals can configure sidelink communication based on pre-configuration information.

[0031] In some cases, the terminals 127-129 located outside the coverage of the network device can form a communication group, and the terminals 127-129 in the communication group can communicate with each other. In addition, the terminal 127 in the communication group can serve as a central control node, also known as a cluster header terminal (CH), and correspondingly, the terminals in other communication groups can be called "group members".

[0032] Terminal 127 as a CH may have one or more of the following functions: responsible for establishing a communication group; joining and leaving of group members; coordinating resources, allocating side transmission resources to group members, receiving side transmission feedback information from group members; coordinating resources with other communication groups, etc.

[0033] It should be noted that Figure 1 A network device and multiple terminal devices are shown exemplarily. Optionally, the wireless communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0034] Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

[0035] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) system or new radio (new radio, NR), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), etc. The technical solutions provided by the present application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0036] The terminal in the embodiment of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal device, wireless communication device, user agent or user device. The terminal device in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, and may be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiment of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a scheduling entity, which provides side data between terminal devices in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using side data. Cellular phones and smart home devices communicate without relaying communication signals through a base station.

[0037] The network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may also be referred to as an access network device or a wireless access network device, such as a base station. The network device in the embodiment of the present application may refer to a wireless access network (RAN) node (or device) that connects a terminal device to a wireless network. Base station can broadly cover various names as follows, or replace with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, auxiliary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The base station can also refer to a communication module, a modem or a chip used to be arranged in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs the base station function in device-to-device D2D, V2X, machine-to-machine (M2M) communications, a network-side device in a 6G network, and a device that performs the base station function in a future communication system. The base station can support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form used by the network device.

[0038] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0039] The network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on aircraft, balloons and satellites in the air. The embodiments of the present application do not limit the scenarios in which the network equipment and terminal equipment are located.

[0040] It should be understood that all or part of the functions of the communication device in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (eg, a cloud platform).

[0041] Sideline communication mode

[0042] Some standards or protocols (such as the 3rd generation partnership project (3GPP)) define two modes (or transmission modes) of sideline communication: a first mode (mode-1) and a second mode (mode-2).

[0043] In the first mode, the resources of the terminal device (the resources mentioned in this application may also be referred to as transmission resources, such as time-frequency resources) are allocated by the network device. The terminal device can send data on the sidelink according to the resources allocated by the network device. The network device can allocate resources for a single transmission to the terminal device, or it can allocate resources for semi-static transmission to the terminal device. This first mode can be applied to scenarios covered by network devices, such as Figure 2 The scene shown. Figure 2 In the scenario shown, terminal device 221 and terminal device 222 are located within the network coverage of network device 210. Network device 210 can allocate resources used in the sideline transmission process to terminal device 221 and terminal device 222. Figure 2 As shown, the network device can grant (grant) through a downlink (DL) to allocate resources used in the sidelink transmission process to the terminal device 221 and the terminal device 222, so that the terminal device 221 and the terminal device 222 can communicate on the sidelink (SL). In some embodiments, the first mode can also be referred to as mode A.

[0044] In the second mode, the terminal device can autonomously select one or more resources from a resource pool (RP). Then, the terminal device can perform side transmission according to the selected resources. Figure 3In the scenario shown, the terminal device 321 is located within the network coverage. The terminal device 321 can autonomously select resources from a preconfigured resource pool for side transmission. Alternatively, the terminal device 321 can autonomously select one or more resources from a resource pool configured by the network device 310 for side transmission. It should be noted that if the terminal device 321 is located outside the network coverage, the terminal device 321 can also use the second mode for resource selection. In some embodiments, the second mode may also be referred to as mode B.

[0045] 3GPP Research Progress on Sideline Communications

[0046] In 3GPP, studies on sideline communications have been conducted at different stages.

[0047] In 3GPP release (Rel) 12 or 13, device-to-device communication targets the scenario of proximity-based services (ProSe), which is mainly for public safety services. In ProSe, the location of the resource pool in the time domain can be configured, for example, the resource pool is non-continuous in the time domain. Based on the above method, the terminal device can send / receive data non-continuously on the side link, thereby achieving power saving.

[0048] In Rel-14 or Rel-15, the V2X system has studied the scenario of vehicle-to-vehicle communication. V2X is mainly aimed at the business of relatively high-speed vehicle-to-vehicle and vehicle-to-person communication. In V2X, since the vehicle system has a continuous power supply, power efficiency is not the main problem to be solved, but the delay of data transmission is the main problem. Therefore, the terminal equipment can be required to send and receive continuously in system design.

[0049] In Rel-14, the further enhancements to LTE DTD (Further Enhancements to LTE Device to Device, FeD2D) technology studied the scenario of wearable devices accessing the network through terminal devices, which is mainly aimed at low mobile speed and low power access scenarios. In FeD2D, in the pre-research stage, 3GPP concluded that network equipment can configure the discontinuous reception (DRX) parameters of the remote terminal through a relay terminal. However, the subject has not entered the standardization stage, so the specific details of how to configure DRX have not yet been concluded.

[0050] In the NR V2X related research, NR V2X has further expanded to unicast and multicast scenarios based on the LTE V2X broadcast scenario. Similar to LTE V2X, NR V2X will also define the above-mentioned two resource authorization modes, the first mode and the second mode. In addition, in NR V2X, the terminal device can be in a mixed mode. In this mixed mode, the terminal device can use the first mode to acquire resources and the second mode to acquire resources at the same time. The above-mentioned resource acquisition can be indicated by sidelink authorization, that is, the sidelink authorization can indicate the time-frequency position of the corresponding PSCCH and PSSCH resources.

[0051] In LTE V2X, hybrid automatic repeat request (HARQ) retransmission can be initiated by the terminal device, and HARQ is based on no feedback. Unlike LTE V2X, NR V2X introduces feedback-based HARQ retransmission. This feedback-based HARQ retransmission can be applied to unicast communication or multicast communication.

[0052] Similar to LTE V2X, in NR V2X, since the vehicle system has a continuous power supply, power efficiency is not the main issue, but the latency of data transmission is the main issue. Therefore, the system design can require the terminal device to perform continuous transmission and reception.

[0053] Quality of service (QoS) indication for sideline communications

[0054] In sideline communication, PC5 QoS index (PQI) can be used to index QoS characteristics. In some sideline communication systems, QoS / PQI can be shown in Table 1.

[0055] Table 1

[0056]

[0057]

[0058] Unlicensed spectrum communications

[0059] Unlicensed spectrum is a spectrum that can be used for radio equipment communications, which is divided by countries and regions. This spectrum is usually considered to be a shared spectrum, that is, as long as the communication equipment meets the regulatory requirements set by the country or region on the spectrum, it can use the spectrum without applying for exclusive spectrum authorization from the country or region's exclusive spectrum management agency. Unlicensed spectrum can also be called shared spectrum, unlicensed spectrum, unlicensed frequency band or unlicensed frequency band, etc.

[0060] For the Uu-based communication process, the network device (e.g., gNB) can operate in dynamic or semi-static channel access mode. In the above two channel access modes, the network device and the terminal device can apply listen before talk (LBT) before performing transmission on a cell configured with unlicensed spectrum channel access. When LBT is applied, the data transmitter (transmitter) listens to or senses the channel to determine whether the channel is idle or busy. When the channel is sensed to be idle, the data transmitter can perform data transmission.

[0061] After LBT is successful on the unlicensed spectrum channel, the length of time that the communication device uses the unlicensed spectrum channel for signal transmission can be represented by the channel occupancy time (COT). To ensure fairness, in one transmission, the length of time that the communication device uses the unlicensed spectrum channel for signal transmission cannot exceed the maximum channel occupancy time (MCOT).

[0062] The types of channel access processes may include: channel access process type 1 (type 1) and channel access process type 2 (type 2). Channel access process type 1 is a multi-slot channel detection with random backoff based on contention window size adjustment, wherein the corresponding CAPC can be selected according to the priority of the service to be transmitted. Channel access process type 2 is a channel access method based on a fixed-length listening time slot. In an embodiment of the present application, the channel access method is also called the LBT method, and the channel access process is also called the LBT process.

[0063] Channel access process type 1 is mainly used for communication devices to initiate channel occupation. Channel access process type 2 is mainly used for communication devices to share channel occupation.

[0064] Channel access procedure type 2 includes: channel access procedure type 2A (type 2A), channel access procedure type 2B (type 2B) and channel access procedure type 2C (type 2C). Type 2A, type 2B and type 2C are introduced below.

[0065] When the communication device performs channel access in type 2A, the channel detection mode of the communication device is 25 microseconds (μs) channel detection. Specifically, when performing channel access in type 2A channel access process, the communication device can perform 25μs channel monitoring before the start of transmission, and transmit after the channel monitoring is successful (i.e., the channel is idle).

[0066] When the communication device performs channel access in type 2B, the channel detection method of the communication device is 16μs channel detection. Specifically, in the case of channel access in type 2B channel access process, the communication device can perform 16μs channel monitoring before the start of transmission, and transmit after the channel monitoring is successful (that is, the channel is idle). Among them, the gap size between the starting position of the transmission and the end position of the previous transmission is 16μs, or the gap size between the starting position of the transmission and the end position of the previous transmission is greater than or equal to 16μs, and less than 25μs.

[0067] When the communication device performs channel access in type 2C, the communication device can transmit without performing channel detection after the gap ends. Specifically, when performing channel access in type 2C of the channel access process, the communication device can directly transmit, wherein the gap size between the start position of the transmission and the end position of the previous transmission is less than or equal to 16μs. The length of the transmission does not exceed 584μs.

[0068] When a consistent uplink LBT failure is detected by a terminal device, the terminal device may take the measures specified in standard TS 38.321 [6] to handle it. The detection is based on each bandwidth part (BWP) and on all uplink transmissions within the BWP. When a consistent uplink LBT failure is detected on a secondary cell (SCell), the terminal device may report this to the corresponding network device (e.g., gNB) via a medium access control control element (MAC-CE) on a serving cell different from the SCell where the failure was detected (master node (MN) for master cell group (MCG), secondary node (SN) for secondary cell group (SCG)). If no resources are available to transmit the MAC-CE, the terminal device may transmit a scheduling request (SR). When a consistent uplink LBT failure is detected on a special cell (SpCell), the terminal device can switch to another uplink (UL) BWP configured with random access channel (RACH) resources on the cell, initiate RACH, and report the failure through MAC-CE. When multiple UL BWPs are available for exchange, the terminal device can implement which one to select. For the primary secondary cell (PSCell), if a consistent uplink LBT failure is detected on all UL BWPs configured with RACH resources, the terminal device can declare an SCG radio link failure (RLF) and report the failure to the mobile network (MN) through SCGFailureInformation. For the primary cell (PCell), if an uplink LBT failure is detected on all ULBWPs with configured RACH resources, the terminal device can declare an RLF.

[0069] COT Sharing Mechanism

[0070] When a communication device initiates a COT, in addition to using the resources in the COT for transmission, the resources in the COT can also be shared with other communication devices for transmission. For example, a first communication device can initiate a shared COT and share the acquired COT with a second communication device, and the second communication device can inherit the COT and use the COT for data transmission. Among them, the second communication device can be called a shared COT communication device (for example, it can include a shared COT terminal device).

[0071] The principle of COT sharing may include: the CAPC level corresponding to the service transmitted by the second communication device should not be lower than the CAPC level used by the first communication device when acquiring the COT.

[0072] When the first communication device shares resources within the COT with the second communication device, the second communication device may use channel access procedure type 2 for channel access.

[0073] Some communication systems (such as the sidelink over unlicensed spectrum (SL-U) system) support a direct COT sharing mechanism for terminal devices, that is, when a terminal device successfully accesses a type 1 channel and uses the channel for side transmission, the terminal device can share the channel with other terminal devices for side transmission. In other words, shared COT can be supported between terminal devices that establish a PC5 radio resource control (RRC) connection. For example, terminal device 1 successfully accesses a type 1 channel and sends PSCCH / PSSCH to terminal device 2. Terminal device 1 can share the COT with terminal device 2 so that terminal device 2 sends PSFCH to terminal device 1. In this case, terminal device 2 only needs to perform a type 2 channel access process within the shared COT.

[0074] The following takes the SL-U system as an example to illustrate the COT sharing mechanism. It can be understood that the COT sharing mechanism described below can also be applied to other communication systems.

[0075] In order to ensure that the communication devices in the SL-U system can continue to use the channel within the acquired COT, the SL-U frame structure can support a 16us guard period (GP) symbol. In some implementations, the length of the GP can be reduced by reusing the cyclic prefix extension (CP extension).

[0076] The terminal device can complete COT sharing by indicating COT sharing information. The shared COT terminal device can realize COT sharing by inheriting or forwarding COT sharing information. COT information can be carried in the physical layer control signaling sidelink control information (SCI). If the COT sharing information is carried in the SCI, the implementation of COT sharing can consider the processing time. The processing time can be the time for the terminal device to receive and decode the COT sharing information carried in the SCI. Furthermore, the relationship between the processing time and the minimum listening time prescribed by regulations can be considered.

[0077] The COT sharing information indicated by the terminal device initiating COT may include one or more of the following information: remaining COT duration information, available subband information (this information can be obtained through the resource indication information carried by SCI), CAPC information and COT sharing identification (identity, ID) information, etc.

[0078] The COT sharing information inherited by the shared COT terminal device may include: remaining COT duration information, available subband information (this information can be obtained through resource indication information carried by SCI), CAPC information and COT sharing ID information, etc.

[0079] The COT shared ID information may include at least one or more of the following: a target terminal ID, a terminal group ID, service identification information, and a sideline zone identification (SL zone ID).

[0080] The inheritance and forwarding of COT shared information can meet the following processing time conditions: the time length between the end position of the received SCI symbol and the start position of the sent SCI symbol is greater than or equal to the first time length (for example, it can be obtained by T proc,SL-U Indicates), where T proc,SL-U The processing time that needs to be considered for the inheritance and forwarding of COT shared information can be considered.

[0081] When the terminal device receives multiple COT shared information that meets the processing time condition, solution 1 and / or solution 2 may be considered to select appropriate COT shared information to inherit and forward.

[0082] Solution 1: The terminal device may select to inherit and forward the COT sharing information with the longest remaining COT length according to the remaining COT length among multiple COT sharing information. The COT sharing information with the longest remaining COT length forwarded by the terminal device may be determined relative to the sending time of the terminal device.

[0083] Solution 2: When the remaining COT lengths determined according to multiple COT sharing information are the same, the terminal device can select to inherit and forward the COT sharing information with the largest CAPC value according to the CAPC values ​​in the multiple COT sharing information.

[0084] It should be noted that the above-mentioned multiple COT sharing information can be multiple COT sharing information that can be used by the terminal device. In addition to the above scheme, the inheritance and forwarding of COT information can also be based on other information, for example, the inheritance and forwarding of COT information can be based on the resource block set (RB set) information in the COT sharing information.

[0085] If the COT sharing conditions are met, the terminal device can be allowed to perform COT sharing.

[0086] As an implementation manner, the COT sharing condition may be determined based on the COT sharing ID information. For example, a terminal group may be determined based on the COT sharing ID information, and the COT may be shared between terminal devices in the terminal group.

[0087] As an implementation method, the COT sharing mechanism can also be based on an implicit public group method to determine whether the COT shared by other terminals is valid according to the evaluation results of the responding device terminal. The evaluation criteria for COT sharing of the responding device terminal may include the following criteria: expected COT sharing range / area, channel quality measurement of the responding device terminal. The expected COT sharing range / area can be determined by SL Zone ID or RSRP measurement. The channel quality measurement of the responding device terminal may include, for example, a reference signal received power (RSRP) threshold or a constant bit rate (CBR) related measurement.

[0088] Determination of CAPC

[0089] A CAPC value can correspond to one or more channel access parameters. Taking a network device as an example, Table 2 shows the channel access parameters corresponding to different CAPC values ​​(indicated by p in Table 2) on the network device side. p Refers to the number of backoff slots corresponding to p, CW p Refers to the contention window (CW) size corresponding to p, CW min,p It means the CW corresponding to p p The minimum value, CW max,p is the CW corresponding to p p The maximum value, T mcot,pIt refers to the maximum occupancy time length of the channel corresponding to p.

[0090] Table 2

[0091]

[0092] Taking NR-U as an example, the following introduces the method for determining the CAPC of a communication system based on the Uu port.

[0093] The Channel Access Priority Classes (CAPC) of radio bearers and MAC CEs are either fixed or configurable: Fixed to the lowest priority for the padding BSR and recommended bit rate MAC CEs; Fixed to the highest priority for SRB0, SRB1, SRB3 and other MAC CEs; Configured by the gNB for SRB2 and DRB.

[0094] When choosing the CAPC of a DRB, the gNB takes into account the 5QIs of all the QoS flows multiplexed in that DRB while considering fairness between different traffic types and transmissions. Table 3 below shows which CAPC should be used for which standardized 5QIs ie which CAPC to use for a given QoS flow.

[0095] NOTE: A QoS flow corresponding to a non-standardized5QI (ieoperator specific 5QI) should use the CAPC of thestandardized 5QI which best matches the QoS characteristics of the non-standardized 5QI.

[0096] Table 3

[0097]

[0098] When performing type 1 LBT for transmission of an uplink transport block (TB) and when no CAPC is indicated in the downlink control information (DCI), the terminal device shall select a CAPC. For example, if only MAC CEs are contained in the TB, use the highest priority CAPC for these MAC CEs; or, if CCCHSDU(s) are contained in the TB, use the highest priority CAPC; or, if DCCH SDU(s) are contained in the TB, use the highest priority CAPC for the DCCH(s); or, otherwise use the lowest priority CAPC for the logical channel that multiplexes the MAC SDU in the TB. (When performing Type 1LBT for the transmission of an uplink TB (see TS37.213

[37] , clause 4.2.1.1) and when the CAPC is not indicated in the DCI, the UE shall select the CAPC as follows: If only MAC CE(s)are included in the TB, the highest priority CAPC of those MAC CE(s)is used; or If CCCH SDU(s)areincluded in the TB, the highest priority CAPC is used; or If DCCH SDU(s)areincluded in the TB, the highest priority CAPC of the DCCH(s) is used; or Thelowest priority CAPC of the logical channel(s)with MAC SDU multiplexed in the TB is used otherwise.)

[0099] It can be seen that the Uu port communication system based on unlicensed spectrum determines the CAPC according to the configuration of the network device. Specifically, the network device can determine the CAPC value by referring to the Qos / 5QI value. In the sideline communication based on unlicensed spectrum, there is no suitable technical solution to determine the CAPC value.

[0100] Figure 4A schematic flowchart of a method for sideline communication provided in an embodiment of the present application is provided to solve the above-mentioned problem. Figure 4 The illustrated method may include step S410.

[0101] Step S410: The first device determines a first CAPC value for sideline communication.

[0102] The first device may be the communication device described above. For example, the first device may be a network device or a terminal device. In other words, the network device may determine a first CAPC value for sideline communication of the terminal device and configure it to the terminal device, or the terminal device may determine a first CAPC value for sideline communication. In some embodiments, the CAPC value may also be referred to as a CAPC level, that is, the first CAPC may also be referred to as a first CAPC level.

[0103] In the case where the first device is a network device, the method for sideline communication provided by the present application may also include: Figure 5 The method shown. Figure 5 It can be executed by the network device and / or the terminal device. Figure 5 The illustrated method may include step S510.

[0104] In step S510, the network device may send CAPC configuration information to the terminal device, wherein the CAPC configuration information may be used to indicate a first CAPC value.

[0105] Figure 5 The method shown may further include step S520.

[0106] Step S520: The terminal device performs sideline communication based on the first CAPC value. For example, the terminal device may perform sideline communication on an unlicensed spectrum based on the first CAPC value.

[0107] In the case where the first device is a terminal device, the embodiment of the present application provides Figure 6 A method for sideline communications is shown. Figure 6 The illustrated method may include step S610.

[0108] Step S610: The terminal device determines a first CAPC value for sideline communication. That is, the first CAPC value is determined by the terminal device itself.

[0109] Figure 6 The method shown may further include step S620.

[0110] Step S620: The terminal device performs sideline communication based on the first CAPC value.

[0111] The present application does not limit the configuration granularity of the first CAPC value. For example, the first CAPC value may correspond to one or more of the following: logical channel, QoS flow, PQI, priority, radio bearer, layer 2 identifier, service, service type, transmission profile (Txprofile), broadcast type (cast type), resource pool, data packet.

[0112] As an implementation, when the first device is a network device, the first CAPC value may correspond to one or more of the following: a logical channel, a QoS flow, a PQI, a priority, a radio bearer, a layer 2 identifier (ID), a service, a service type, a transmission profile, a broadcast type, and a resource pool. In other words, the determination granularity of the CAPC value may be one or more of each logical channel, each QoS flow, each PQI, each priority, each radio bearer, each layer 2 identifier, each service, each service type, each transmission profile, each broadcast type, and each resource pool.

[0113] As another implementation method, when the first device is a terminal device, the first CAPC value may correspond to one or more of the following: logical channel, QoS flow, PQI, priority, radio bearer, layer 2 identifier, service, service type, transmission profile, broadcast type, resource pool, and data packet.

[0114] It should be noted that the sending profile can be used to indicate which version of the protocol to use for sending by the first terminal, such as Release 12, or which feature to use for sending, and the feature can be whether to enable discontinuous reception (DRX). In some embodiments, the sending profile can also be a sending file, a sending parameter, etc.

[0115] It should be noted that the broadcast type can be used to indicate unicast communication, multicast communication or broadcast communication. In some embodiments, the broadcast type can also be called a transmission broadcast type.

[0116] It should be noted that the first CAPC value is associated with the PQI. For example, the first CAPC may be determined based on the PQI. Alternatively, the first CAPC may have a mapping relationship with the PQI.

[0117] The present application proposes to determine a first CAPC value for sideline communication based on PQI, thereby achieving determination of a CAPC value in a sideline communication system.

[0118] It should be noted that the configuration granularity of the first CAPC value is different, and the association between the first CAPC and the PQI will also be different. For example, when the first CAPC value corresponds to a QoS flow, the first CAPC value can be associated with the PQI of the QoS flow. In some embodiments, the first CAPC value is the CAPC value of the first QoS flow, and the CAPC value of the first QoS flow can be determined based on the PQI of the first QoS flow. Alternatively, when the configuration granularity of the first CAPC value is not a QoS flow, the CAPC value of one or more QoS flows associated with the configuration granularity can be determined, and the first CAPC value can be one of the CAPC values ​​of the one or more QoS flows. Among them, the CAPC value of one or more QoS flows can be determined based on the PQI of one or more QoS flows.

[0119] In some embodiments, there may be one or more QoS flows corresponding to the same radio bearer / logical channel. For example, one or more QoS flows correspond to the first radio bearer / logical channel. The first CAPC value may be the CAPC value of the first radio bearer / logical channel. In this case, the CAPC value of the first radio bearer / logical channel (i.e., the first CAPC value) may be determined based on the CAPC value of one or more QoS flows, or the CAPC value of the first radio bearer / logical channel may be determined according to the implementation of the first device. In other words, if there are one or more QoS flows corresponding to the same radio bearer / logical channel, which of the CAPC values ​​of one or more QoS flows is selected as the CAPC value of the radio bearer / logical channel may be determined based on the CAPC value of one or more QoS flows or the implementation of the first device. Among them, the CAPC value of one or more QoS flows may be determined according to the PCI of one or more QoS flows.

[0120] As an implementation, the CAPC value of the first radio bearer / logical channel can be determined based on one or more of the following: the maximum value of the CAPC values ​​of one or more QoS flows, the minimum value of the CAPC values ​​of one or more QoS flows, the CAPC value of the QoS flow with the highest priority in one or more QoS flows, the CAPC value of the QoS flow with the lowest priority in one or more QoS flows, and the CAPC value of the QoS with the shortest packet delay budget in one or more QoS flows. Alternatively, the CAPC value of the first radio bearer / logical channel can be determined based on other dimensional parameters in QoS. Alternatively, the CAPC value of the first radio bearer / logical channel can be based on the implementation of the first device.

[0121] As another implementation, the CAPC values ​​of the QoS flows in the first radio bearer / logical channel are the same. In other words, the network device may only map the QoS flows with the same CAPC value to the first radio bearer / logical channel.

[0122] In some implementations, the first CAPC value may be determined based on a first parameter. The first parameter may be associated with a PQI. In some embodiments, the first parameter may be one or more of the parameters of each dimension corresponding to the PQI. For example, the first parameter may include one or more of the following: a PQI value, a PQI type, a priority corresponding to the PQI, a packet delay budget (PDB) corresponding to the PQI, a resource type (resourcetype) corresponding to the PQI, a packet error rate (packet error rate) corresponding to the PQI, and parameters of other dimensions corresponding to the PQI. The above parameters are described below.

[0123] The value of PQI may be any one of the values ​​shown in the first column of Table 1. For example, the value of PQI may include: 24, 25, 26, 60, 61, 92, 93, 21, 22, 23, 55, 56, 57, 58, 59, 90, 91 or a non-standard PQI.

[0124] The type of PQI may be used to indicate whether the PQI is standard or non-standard. The type of PQI may include, for example, a standard PQI and a non-standard PQI.

[0125] The priority corresponding to the PQI may include a priority associated with the PQI. For example, the priority associated with the PQI may include a priority of a layer 1 data stream or a priority of a layer 2 data stream associated with the PQI. Alternatively, the priority associated with the PQI may include a default priority level of the PQI. The values ​​of the default priority level may include: 1, 2, 5, or 6.

[0126] The estimated packet delay corresponding to the PQI may be any one of the values ​​shown in the fourth column of Table 1. For example, the estimated packet delay corresponding to the PQI may include: 5 ms, 10 ms, 120 ms, 150 ms, 200 ms or 400 ms.

[0127] The resource type corresponding to the PQI may be any one of the values ​​shown in the second column of Table 1. For example, the resource type corresponding to the PQI may include a guaranteed rate (GBR) type, a non-guaranteed rate (non-GBR) type, or a delay critical guaranteed rate (delay critical GBR) type.

[0128] The value of the packet error rate corresponding to the PQI may be any one of the values ​​shown in the fifth column of Table 1. For example, the value of the packet error rate corresponding to the PQI may include: 10 -2 , 10 -3 , 10-4 or 10 -6 .

[0129] Parameters of other dimensions corresponding to the PQI may include, for example, one or more of the following: a default maximum data burst volume and a default averaging window.

[0130] In some embodiments, the first CAPC value may correspond to a value of the first parameter. For example, in the case where the PQI is a standard PQI, the first CAPC value may correspond to a value of the first parameter. Taking the case where the first parameter includes the value of the PQI and / or the packet delay estimate corresponding to the PQI as an example, the correspondence between the first CAPC value (represented by the "CAPC level" column in the table) and the value of the PQI and / or the packet delay estimate corresponding to the PQI can be shown in Table 4. It should be noted that Table 4 is only an example, and the first CAPC value may correspond to a value of other parameters associated with the PQI that are different from those in Table 4. In addition, the correspondence between the value of the PQI and / or the value of the packet delay estimate in Table 4 and the CAPC value is also exemplary. For example, when the value of the PQI in Table 4 is 24, the CAPC value may be 2, but it does not exclude the case where the CAPC value may be 3 or 1 when the value of the PQI is 24.

[0131] Table 4

[0132] PQI Value Packet Delay Budget CAPC level 24 150ms 2 25 200ms 2 26 200ms 2 60 120ms 2 61 400ms 3 92 5ms 1 93 10ms 1

[0133] In some embodiments, the first CAPC value may correspond to a range of values ​​of the first parameter. For example, in the case where the PQI is a non-standard PQI, the first CAPC value may correspond to a range of values ​​of the first parameter. Taking the case where the first parameter includes a packet delay estimate corresponding to the PQI as an example, the correspondence between the first CAPC value (represented by the "CAPC level" column in the table) and the packet delay estimate corresponding to the PQI may be as shown in Table 5. It should be noted that Table 5 is only an example, and the first CAPC value may correspond to a range of values ​​of other parameters associated with the PQI that are different from those in Table 5. In addition, the correspondence between the PQI value and / or a range of values ​​of the packet delay estimate and the CAPC value in Table 5 is also exemplary. For example, in the case where the range of packet delay estimate values ​​in Table 5 is 0-100ms, the CAPC value may be 1, but it does not exclude the case where the CAPC value may be 2 or 3 when the range of packet delay estimate values ​​is 0-100ms. In addition, the present application does not limit the range of a range of values. For example, a packet delay estimate may correspond to a first CAPC value in every 100ms range. Alternatively, the packet delay estimate may correspond to a first CAPC value in every 50 ms range.

[0134] Table 5

[0135] PQI Value Packet Delay Budget CAPC level Non-standard PQI_1 0-100ms 1 Non-standard PQI_2 100-200ms 2 Non-standard PQI_3 200-300ms 3

[0136] In some embodiments, if the PQI is a standard PQI, the first CAPC value may correspond to a value of the first parameter; if the PQI is a non-standard PQI, the first CAPC value may correspond to a range of values ​​of the first parameter. Taking the case where the first parameter includes a packet delay estimate corresponding to the PQI as an example, the correspondence between the first CAPC value (represented by the "CAPC Level" column in the table) and the packet delay estimate corresponding to the PQI may be as shown in Table VI. It should be noted that Table VI is only an example, and the first CAPC value may correspond to a value of other parameters associated with the standard PQI that are different from those in Table VI. The first CAPC value may correspond to a range of values ​​of other parameters associated with the non-standard PQI that are different from those in Table VI.

[0137] Table 6

[0138] PQI Value Packet Delay Budget CAPC level 24 150ms 2 25 200ms 2 61 400ms 3 92 5ms 1 93 10ms 1 Non-standard PQI 0-100ms 1 Non-standard PQI_2 100-200ms 2 Non-standard PQI_3 200-300ms 3

[0139] In some embodiments, if the PQI is a non-standard PQI, the first CAPC value may be a fixed value. The fixed value may be a specific level or a default level. For example, the fixed value may be 1, 2, 3, or 4. In some implementations, all non-standard PQIs may correspond to a fixed value.

[0140] As an implementation method, when the PQI is a standard PQI, the first CAPC value may correspond to a value of the first parameter; when the PQI is a non-standard PQI, the first CAPC value is a fixed value. Taking the first parameter including the value of the PQI and / or the packet delay estimate corresponding to the PQI as an example, the correspondence between the first CAPC value (represented by the "CAPC level" column in the table) and the value of the PQI and / or the packet delay estimate corresponding to the PQI can be shown in Table 7. It should be noted that Table 7 is only an example, and the first CAPC value may correspond to a value of other parameters associated with the standard PQI that are different from those in Table 7.

[0141] Table 7

[0142] PQI Value Packet Delay Budget CAPC level 24 150ms 2 25 200ms 2 26 200ms 2 60 120ms 2 61 400ms 3 92 5ms 1 93 10ms 1 Non-standard PQI Fixed value

[0143] It can be seen from the above technical solution that in the presence of a non-standard PQI, the application itself can also determine the CAPC value corresponding to the PQI.

[0144] The above text describes in detail the method for determining the first CAPC value (or the basis for determination), that is, how the first CPAC is associated with the PQI. The above determination method can be configured based on the following methods: for a terminal device in a connected state, based on the RRC signaling configuration sent by the network device; or for a terminal device in an idle state (idle) or an inactive state (inactive), based on the system message configuration sent by the network device; or for a terminal device outside the coverage of the network device, based on pre-configuration information. Among them, the RRC signaling can be a unique RRC signaling, and the system message can be a system information broadcast (SIB).

[0145] In some implementations, the first CAPC value may be configured based on the following methods: for a terminal device in a connected state, based on RRC signaling sent by a network device; or for a terminal device in an idle state or an inactive state, based on a system message sent by a network device; or for a terminal device out of coverage of a network device, based on pre-configuration information. The RRC signaling may be a unique RRC signaling, and the system message may be a SIB.

[0146] The present application does not limit the configuration method of the first CAPC, that is, the present application does not limit the method by which the first CAPC is configured. As an implementation method, the first CAPC can be configured, pre-configured by a network device, or determined autonomously by a terminal device.

[0147] When the terminal device is out of coverage or in a non-connected state, the network device cannot configure an accurate CAPC for it according to the QoS of the terminal device. Based on the present application, the terminal device can determine the first CAPC value for sideline communication by itself, or the first CAPC can be determined by pre-configuration. Therefore, even if it is out of coverage or in a non-connected state, the present application can still determine an accurate CAPC.

[0148] As an implementation method, the first CAPC value is configured by the network device or determined autonomously by the terminal device based on one or more of the following: the connection status of the terminal device, the transmission mode of the terminal device, whether the terminal device is within the coverage of the network device, the configuration information of the network device, and the predefined rules of the protocol.

[0149] The connection state of the terminal device may include a connection state and a non-connection state. The non-connection state may include, for example, out of coverage, an idle state, or an inactive state.

[0150] The transmission mode of the terminal device may include Mode 1 or Mode 2 described above.

[0151] Whether the terminal device is within the coverage of the network device may include being within the coverage area or being outside the coverage area.

[0152] The configuration information of the network device can be either explicitly configured or implicitly configured. Explicit configuration is indicated, for example, by one bit of indication information. Implicit configuration can be indicated, for example, by whether certain fields exist in system messages and / or unique signaling.

[0153] The rules predefined in the protocol may be determined based on one or more of the type of PQI (standard PQI or non-standard PQI), channel quality, resource pool, load condition, indication from the opposite terminal device, and LBT condition.

[0154] For example, for a terminal device in a connected state, the first CAPC value is configured by the network device. Alternatively, for a terminal device in a non-connected state, the first CAPC value is determined autonomously by the terminal device. Alternatively, for a terminal device in a connected state, a terminal device in an idle state, and a terminal device in an inactive state, the first CAPC value is configured by the network device. Alternatively, for a terminal device outside the coverage of the network device, the first CAPC value is determined autonomously by the terminal device.

[0155] Combination of the above Figures 1 to 6 , describes the method embodiment of the present application in detail, and the following is combined with Figures 7 and 8 , describes the device embodiment of the present application in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the parts not described in detail can refer to the previous method embodiment.

[0156] Figure 7 7 is a schematic structural diagram of a communication device 700 provided in an embodiment of the present application. The communication device 700 may include a determining unit 710 .

[0157] The determination unit 710 may be configured to determine a first CAPC value for sideline communication; wherein the first CAPC value is associated with a PQI.

[0158] Optionally, associating the first CAPC value with the PQI includes: the first CAPC value is determined based on a first parameter, and the first parameter is associated with the PQI.

[0159] Optionally, the first parameter includes one or more of the following: the value of the PQI; the type of the PQI; the priority corresponding to the PQI; the packet delay estimation corresponding to the PQI; the resource type corresponding to the PQI; and

[0160] The packet error rate corresponding to the PQI; wherein the type of the PQI includes a standard PQI and a non-standard PQI.

[0161] Optionally, if the PQI is a non-standard PQI, the first CAPC value is a fixed value.

[0162] Optionally, if the PQI is a non-standard PQI, the first CAPC value corresponds to a value range of the first parameter.

[0163] Optionally, if the PQI is a standard PQI, the first CAPC value corresponds to a value of the first parameter.

[0164] Optionally, the first CAPC value corresponds to one of the following: logical channel, QoS flow, PQI, priority, radio bearer, layer 2 identifier, service, service type, transmission profile, broadcast type, resource pool, and data packet.

[0165] Optionally, the first CAPC value is a CAPC value of a first QoS flow, and the CAPC value of the first QoS flow is determined based on a PQI of the first QoS flow.

[0166] Optionally, the first CAPC value is the CAPC value of a first radio bearer / logical channel, the first radio bearer / logical channel contains one or more QoS flows, and the CAPC value of the first radio bearer / logical channel is determined based on the CAPC values ​​of the one or more QoS flows or the implementation of the communication device.

[0167] Optionally, the CAPC value of the first radio bearer / logical channel is determined based on one or more of: the maximum value of the CAPC values ​​of the one or more QoS flows; the minimum value of the CAPC values ​​of the one or more QoS flows; and the CAPC value of the QoS with the shortest packet delay budget among the one or more QoS flows.

[0168] Optionally, the CAPC values ​​of the QoS flows in the first radio bearer / logical channel are the same.

[0169] Optionally, the first CAPC value is configured or pre-configured by a network device or is determined autonomously by a terminal device.

[0170] Optionally, the first CAPC value is configured based on the following methods: for a terminal device in a connected state, based on RRC signaling configuration sent by the network device; or for a terminal device in an idle state or an inactive state, based on a system message configuration sent by the network device; or for a terminal device outside the coverage of the network device, based on pre-configuration information.

[0171] Optionally, the method for determining the first CAPC value is configured based on one of the following methods: for a terminal device in a connected state, based on the RRC signaling configuration sent by the network device; for a terminal device in an idle state or an inactive state, based on the system message configuration sent by the network device; and for a terminal device outside the coverage of the network device, based on pre-configuration information.

[0172] Optionally, the first CAPC value is configured by the network device or determined autonomously by the terminal device based on one or more of the following: the connection status of the terminal device; the transmission mode of the terminal device; whether the terminal device is within the coverage of the network device; the configuration information of the network device; and predefined rules of the protocol.

[0173] Optionally, the first CAPC value is determined based on one of the following: for a terminal device in a connected state, the first CAPC value is configured by a network device; for a terminal device in an unconnected state, the first CAPC value is autonomously determined by the terminal device; for a terminal device in a connected state, an idle state, and an inactive state, the first CAPC value is configured by the network device; for a terminal device outside the coverage of the network device, the first CAPC value is autonomously determined by the terminal device.

[0174] Figure 8 It is a schematic structural diagram of a communication device according to an embodiment of the present application. Figure 8 The dotted line in the figure indicates that the unit or module is optional. The device 800 can be used to implement the method described in the above method embodiment. The device 800 can be a chip, a terminal device or a network device.

[0175] The device 800 may include one or more processors 810. The processor 810 may support the device 800 to implement the method described in the foregoing method embodiment. The processor 810 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0176] The apparatus 800 may further include one or more memories 820. The memory 820 stores a program, which can be executed by the processor 810, so that the processor 810 executes the method described in the above method embodiment. The memory 820 may be independent of the processor 810 or integrated in the processor 810.

[0177] The apparatus 800 may further include a transceiver 830. The processor 810 may communicate with other devices or chips through the transceiver 830. For example, the processor 810 may transmit and receive data with other devices or chips through the transceiver 830.

[0178] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0179] The embodiment of the present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal or network device provided in the embodiment of the present application, and the program enables the computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0180] The embodiment of the present application also provides a computer program. The computer program can be applied to the terminal or network device provided in the embodiment of the present application, and the computer program enables a computer to execute the method executed by the terminal or network device in each embodiment of the present application.

[0181] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third" and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions.

[0182] In the embodiments of the present application, the "indication" mentioned can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0183] In the embodiment of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

[0184] In the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship of indication and being indicated, configuration and being configured, etc.

[0185] In the embodiments of the present application, "pre-definition" or "pre-configuration" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.

[0186] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0187] In the embodiments of the present application, the term "and / or" is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0188] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0189] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0190] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0191] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0192] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may 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 instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0193] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for sideline communication, characterized in that: include: The first device determines a first channel access priority CAPC value for sideline communication; The first CAPC value is associated with a PC5 interface service quality index PQI.

2. The method according to claim 1, characterized in that The associating the first CAPC value with the PQI includes: the first CAPC value is determined based on a first parameter.

3. The method according to claim 2, characterized in that The first parameter includes one or more of the following: The value of the PQI; The type of the PQI; packet delay estimation corresponding to the PQI; as well as A packet error rate corresponding to the PQI; The types of PQI include standard PQI and non-standard PQI.

4. The method according to claim 2 or 3, characterized in that: If the PQI is a non-standard PQI, the first CAPC value is a fixed value; or if the PQI is a non-standard PQI, the first CAPC value corresponds to a value range of the first parameter.

5. The method according to any one of claims 2 to 4, characterized in that: If the PQI is a standard PQI, the first CAPC value corresponds to a value of the first parameter.

6. The method according to any one of claims 1 to 5, characterized in that The first CAPC value is a CAPC value of a first radio bearer / logical channel, the first radio bearer / logical channel includes one or more QoS flows, and the CAPC value of the first radio bearer / logical channel is determined based on the CAPC values ​​of the one or more QoS flows or the implementation of the first device.

7. The method according to claim 6, characterized in that The CAPC value of the first radio bearer / logical channel is determined based on one or more of the following: A maximum value among the CAPC values ​​of the one or more QoS flows; A minimum value among the CAPC values ​​of the one or more QoS flows; as well as The CAPC value of the QoS having the shortest packet delay budget among the one or more QoS flows.

8. The method according to any one of claims 1 to 7, characterized in that The first CAPC value is configured or pre-configured by the network device or determined autonomously by the terminal device.

9. The method according to claim 8, characterized in that The first CAPC value is configured based on: For a terminal device in a connected state, based on the radio resource control RRC signaling configuration sent by the network device; or For a terminal device in an idle state or an inactive state, configuration based on a system message sent by the network device; or For terminal devices outside the coverage of the network device, configuration is performed based on the pre-configuration information.

10. The method according to claim 8, characterized in that The first CAPC value is configured by the network device or determined autonomously by the terminal device based on one or more of the following: The connection status of the terminal device; Whether the terminal device is within the coverage of the network device; Configuration information of network devices; and Predefined rules for the protocol.

11. The method according to claim 10, characterized in that The first CAPC value is determined based on one of the following: For a terminal device in a connected state, the first CAPC value is configured by a network device; For a terminal device in a non-connected state, the first CAPC value is determined autonomously by the terminal device; For a terminal device in a connected state, a terminal device in an idle state, and a terminal device in an inactive state, the first CAPC value is configured by a network device; For terminal devices outside the coverage of the network device, the first CAPC value is determined autonomously by the terminal device.

12. A communication device, characterized in that: The device comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the communication device executes the method according to any one of claims 1 to 11.

Images