Method and apparatus for sidelink communication
Patent Information
- Application Number
- PCT/CN2023/096353
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-25
- Publication Date
- 2024-11-28
Smart Images

Figure CN2023096353_28112024_PF_FP_ABST
Abstract
Description
Method and device for sideline communication Technical Field
[0001] The present application relates to the field of communication technology, and more particularly, to a method and apparatus for sideline communication. Background Art
[0002] When performing sideline communications in a shared spectrum, a terminal device can monitor the channel using mechanisms such as listen before talk (LBT). If the channel monitoring is successful, the terminal device can obtain channel resources and access and perform sideline transmission using the channel access position.
[0003] However, when multiple terminal devices access a channel through LBT, conflicts may occur at the channel access locations.
[0004] Summary of the Invention
[0005] The present application provides a method and apparatus for sideline communication. The following describes various aspects of the embodiments of the present application.
[0006] In a first aspect, a method for sideline communication is provided, comprising: a first terminal device determines first configuration information of a first shared resource, the first configuration information being used to indicate one or more CPEs corresponding to the first shared resource; wherein the one or more CPEs are determined based on the subcarrier spacing corresponding to the first shared resource, and the one or more CPEs are used by a second terminal device to determine a time domain position for accessing the first shared resource.
[0007] According to a second aspect, a device for sideline communication is provided, wherein the device is a first terminal device, and the first terminal device includes: a determination unit, used to determine first configuration information of a first shared resource, and the first configuration information is used to indicate one or more CPEs corresponding to the first shared resource; wherein the one or more CPEs are determined based on the subcarrier spacing corresponding to the first shared resource, and the one or more CPEs are used by the second terminal device to determine the time domain position for accessing the first shared resource.
[0008] According to a third aspect, a communication device is provided, comprising 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 to execute the method according to the first aspect.
[0009] In a fourth aspect, a device is provided, comprising a processor, configured to call a program from a memory to execute the method as described in the first aspect.
[0010] In a fifth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the first aspect.
[0011] In a sixth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method as described in the first aspect.
[0012] In a seventh aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method as described in the first aspect.
[0013] In an eighth aspect, a computer program is provided, which enables a computer to execute the method as described in the first aspect.
[0014] In this embodiment of the present application, the first configuration information may indicate one or more CPEs for the second terminal device to access the first shared resource. These CPEs are determined based on the subcarrier spacing of the first shared resource. The subcarrier spacing is related to the duration of a time unit in the time domain, thereby ensuring that one or more CPEs are present during the time unit in which the terminal device performs channel access. Furthermore, these CPEs can be used to manage the channel access locations of multiple terminal devices, thereby reducing access conflicts among multiple terminal devices. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] FIG1 is a wireless communication system used in an embodiment of the present application.
[0016] Figure 2 is an example diagram of NR-V2X communication.
[0017] FIG3 is a schematic diagram of a frame structure that does not carry PSFCH.
[0018] FIG4 is a schematic diagram of a frame structure carrying PSFCH.
[0019] FIG5 is a flow chart of a method for sideline communication provided in an embodiment of the present application.
[0020] FIG6 is a schematic diagram of a possible implementation of configuring a CPE.
[0021] FIG. 7 is a schematic diagram of another possible implementation of configuring a CPE.
[0022] FIG8 is a schematic diagram of another possible implementation of configuring a CPE.
[0023] FIG9 is a schematic diagram of another possible implementation of configuring a CPE.
[0024] FIG10 is a schematic diagram showing a high-priority terminal device being blocked by a low-priority terminal device.
[0025] FIG11 is a schematic diagram of multiple terminal devices making channel access requests.
[0026] FIG12 is a schematic diagram of a possible implementation of the method shown in an embodiment of the present application.
[0027] FIG13 is a schematic structural diagram of a device for sideline communication provided in an embodiment of the present application.
[0028] FIG14 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0029] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. With respect to the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.
[0030] Figure 1 is a diagram illustrating a system architecture of a wireless communication system 100 applicable to an embodiment of the present application. The wireless communication system 100 may include a network device 110 and terminal devices 121 to 129. The network device 110 may provide communication coverage for a specific geographic area and may communicate with terminals within the coverage area.
[0031] In some implementations, terminal devices may communicate with each other via a sidelink (SL). Sidelink communication may also be referred to as proximity services (ProSe) communication, unilateral communication, sidelink communication, device-to-device (D2D) communication, etc.
[0032] In other words, sidelink data is 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 physical sidelink feedback channel (PSFCH), etc.
[0033] The following describes several common sidelink communication scenarios with reference to Figure 1. Sidelink communication can be categorized into three scenarios, depending on whether the terminal device in the sidelink is within the coverage of the network device. Scenario 1: The terminal device conducts sidelink communication within the coverage of the network device. Scenario 2: Some terminal devices conduct sidelink communication within the coverage of the network device. Scenario 3: The terminal device conducts sidelink communication outside the coverage of the network device.
[0034] As shown in Figure 1, in scenario 1, terminal devices 121-122 can communicate via a sidelink, and terminal devices 121-122 are all within the coverage of network device 110, or in other words, terminal devices 121-122 are all within the coverage of the same network device 110. In this scenario, network device 110 can send configuration signaling to terminal devices 121-122, and accordingly, terminal devices 121-122 communicate via the sidelink based on the configuration signaling.
[0035] As shown in Figure 1, in scenario 2, terminal devices 123 to 124 can communicate via a side link, and terminal device 123 is within the coverage of network device 110, while terminal device 124 is outside the coverage of network device 110. In this scenario, terminal device 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 device 124, since terminal device 124 is outside the coverage of network device 110, it cannot receive the configuration information of network device 110. At this time, terminal device 124 can obtain the configuration of the side link communication based on the pre-configuration configuration information and / or the configuration information sent by terminal device 123 within the coverage area, so as to communicate with terminal device 123 via the side link based on the obtained configuration.
[0036] In some cases, the terminal device 123 may send the above configuration information to the terminal device 124 via a physical sidelink broadcast channel (PSBCH) to configure the terminal device 124 to communicate via the sidelink.
[0037] As shown in Figure 1, in scenario 3, terminal devices 125-129 are all outside the coverage of network device 110 and cannot communicate with network device 110. In this case, the terminal devices can all perform sidelink communication based on pre-configured information.
[0038] In some cases, terminal devices 127-129 located outside the coverage area of the network device can form a communication group, and the terminal devices 127-129 in the communication group can communicate with each other. In addition, the terminal device 127 in the communication group can serve as a central control node, also known as a cluster header (CH), and correspondingly, the terminal devices in other communication groups can be referred to as "group members."
[0039] The terminal device 127 as a CH can have one or more of the following functions: responsible for establishing a communication group; joining and leaving group members; coordinating resources, allocating side transmission resources to group members, and receiving side feedback information from group members; coordinating resources with other communication groups, etc.
[0040] It should be noted that Figure 1 exemplarily shows a network device and multiple terminal devices. Optionally, the wireless communication system 100 may include multiple network devices and the coverage range of each network device may include other numbers of terminal devices. This embodiment of the present application does not limit this.
[0041] Optionally, the wireless communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.
[0042] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.
[0043] The terminal device 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, 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 can 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 may be a mobile phone, a tablet computer (Pad), a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a vehicle, 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, a terminal device can act as a dispatching entity, providing sidelink signals between terminal devices in vehicle-to-everything (V2X) or D2D networks. For example, a cell phone and a car can communicate with each other using sidelink data. A cell phone and a smart home device can also communicate with each other without relaying the communication signal through a base station.
[0044] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), access point (AP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A 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. A base station can also refer to a communication module, a modem or a chip used to be set in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs base station functions in D2D, V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. The base station can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the network equipment.
[0045] 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.
[0046] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device may include a CU and a DU. The gNB may also include an AAU.
[0047] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.
[0048] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).
[0049] For ease of understanding, some relevant technical knowledge involved in the embodiments of this application is first introduced. The following related technologies can be combined with the technical solutions of the embodiments of this application as optional solutions, and they all fall within the scope of protection of the embodiments of this application. The embodiments of this application include at least part of the following contents.
[0050] Sidelink communication mode
[0051] With the development of side-by-side communication technology, side-by-side communication technology involves information interaction between multiple terminal devices. Taking the V2X communication system 200 shown in Figure 2 as an example, the vehicle-to-vehicle (V2V) communication performed by terminal device 201 and terminal device 202 involves information interaction between vehicles themselves. The vehicle-to-infrastructure (V2I) communication, vehicle-to-network (V2N) communication, and vehicle-to-pedestrian (V2P) communication performed by terminal device 201 and terminal devices 203 to 205, respectively, involve information interaction between vehicles and external systems.
[0052] The gradual expansion of information exchange places higher demands on communication systems. For example, these systems must support higher throughput, lower latency, greater reliability, wider coverage, and more flexible resource allocation. Taking the development of V2X as an example, in LTE-V2X, only broadcast mode is supported for sidelink communication between end devices. NR-V2X supports three communication modes: broadcast, groupcast, and unicast.
[0053] Broadcast is the most basic communication mode in sideline communications. In a broadcast transmission mode, the terminal device receiving the sideline data can be any terminal device surrounding the transmitting terminal device. For example, referring to Figure 1 , assuming terminal device 125 is the transmitter and broadcasts sideline data, then terminal devices 121-124 and 126-129 located around terminal device 125 may all serve as receivers of the sideline data.
[0054] Multicast communication supports information exchange between terminal devices within a specific group (or communication group) to facilitate negotiation and decision-making among terminal devices within the group. Sidelink multicast is divided into two transmission types. Type 1 is for fixed groups (managed groups) with stable connections, with clear ID information and information about group members. Type 2 is for temporary groups (connectionless groups) formed in a connectionless manner. For example, it is a multicast that is dynamically formed based on distance and requires clear indication of the communication distance of the current service.
[0055] For the multicast transmission mode, the terminal devices receiving the sideline data may be all the terminal devices in a communication group. Alternatively, the terminal devices receiving the sideline data may be all the terminal devices within a certain transmission distance. For example, referring to FIG1 , for a communication group including terminal devices 127 to 129, when terminal device 127 sends sideline data in a multicast manner, the other terminal devices 128 to 129 in the communication group are all receiving terminals that receive the sideline data. For another example, referring to FIG1 , assuming that the terminal devices within a preset range include terminal devices 127 to 129, when terminal device 127 sends sideline data in a multicast manner, the other terminal devices 128 to 129 within the preset range are all receiving terminals that receive the sideline data.
[0056] Unicast communication enables sidelink communication between two terminal devices. Taking NR-V2X as an example, radio resource control (RRC) signaling based on the newly defined PC5 interface can achieve reliable communication between terminal devices.
[0057] For the unicast transmission mode, there is usually only one terminal device that receives the sidelink data. Referring to Figure 1, terminal device 121 and terminal device 122 can communicate with each other through a unicast transmission mode. For example, when terminal device 121 and terminal device 122 perform sidelink communication, terminal device 122 receives the sidelink data as the only receiving device. The sidelink data may include PSSCH and PSCCH. Through demodulation, terminal device 122 can obtain sidelink control information (SCI) related to sidelink transmission and scheduling. SCI can help terminal device 122 receive and decode sidelink information.
[0058] System frame structure of sidelink
[0059] The following describes the frame structure of the sidelink system frame applicable to the embodiments of the present application, taking the NR-V2X time slot structure as an example, in conjunction with Figures 3 and 4. The system frame is a single time slot containing 14 time domain symbols. Figure 3 shows the frame structure of a system frame that does not carry the PSFCH. Figure 4 shows the frame structure of a system frame that carries the PSFCH.
[0060] The SCI in Figures 3 and 4 consists of two parts, namely, the first-stage SCI-1 and the second-stage SCI-2. The first-stage SCI-1 is transmitted on the PSCCH, and the second-stage SCI-2 is transmitted on the PSSCH.
[0061] As shown in Figure 3, in the time domain, the side symbols occupied by the SCI-1 transmitted on the PSCCH start from the second side symbol of the system frame (for example, the orthogonal frequency division multiplexing (OFDM) symbol) and occupy 2 or 3 side symbols. The transmission of the PSCCH at the beginning of the time slot helps the terminal device at the receiving end to obtain it in advance, so as to demodulate the PSCCH as early as possible. In the frequency domain, the PSCCH can occupy multiple PRBs. Generally, in order to reduce the complexity of the terminal device's blind detection of the PSCCH, only one number of PSCCH symbols and PRBs is allowed to be configured in a resource pool.
[0062] Continuing to refer to Figure 3, in the time domain, the SCI-2 transmitted on the PSSCH also starts from the second sidelink symbol of the system frame and ends at the penultimate sidelink symbol of the system frame. In the frequency domain, the PSSCH occupies multiple subchannels of the system frame. The subchannel can be understood as the minimum granularity of PSSCH resource allocation specified in NR-V2X. The resource pool of the sidelink can be M subchannels, and each subchannel can be composed of N SubCHsizeIt is composed of physical resource blocks (PRBs). SubCHsize The value can be 10, 12, 15, 20, 25, 50, 75 or 100.
[0063] Typically, the first sidelink symbol in a time slot is a repetition of the second sidelink symbol. When receiving the system frame, a terminal device can use the first sidelink symbol as an automatic gain control (AGC) symbol. Data on the AGC symbol is typically not used for data demodulation. The last symbol in a time slot is the guard interval (GAP) symbol.
[0064] As shown in Figure 4, when a timeslot carries the PSFCH, the penultimate and third-to-last sidelink symbols in the system frame are used for PSFCH transmission. Furthermore, gap symbols must be reserved after both the PSSCH and PSFCH. The PSFCH resource preconfiguration period can range from {1, 2, 4} timeslots.
[0065] As can be seen from FIG3 and FIG4 , a portion of the PSCCH and its associated PSSCH are transmitted on resources that overlap in time but do not overlap in frequency, and another portion of the PSSCH and the PSCCH are transmitted on resources that do not overlap in time.
[0066] Sidelink communication spectrum
[0067] Communication systems utilize both licensed and unlicensed spectrum. The use of unlicensed spectrum is a key area of expansion for communication systems. For example, NR deployed on unlicensed spectrum is called NR-U.
[0068] Currently, sidelinks primarily use licensed spectrum. Sidelinks can also use unlicensed spectrum. Deploying sidelinks in unlicensed spectrum is called SL-U.
[0069] Compared to licensed spectrum, unlicensed spectrum is also known as shared spectrum because it requires no license. For operators, spectrum sharing helps them aggregate spectrum in a timely manner to dynamically support high-bandwidth services. Spectrum sharing can also extend the benefits of communication technologies (such as NR) to operators that may not have access to licensed spectrum.
[0070] Shared spectrum requires consideration of the coexistence of different radio access technology (RAT) systems, such as wireless fidelity (WiFi) and LTE-based licensed assisted access (LAA). These different systems compete for the use of unlicensed spectrum bands, adhering to the principles of channel access fairness and multi-RAT coexistence.
[0071] In shared spectrum, any RAT system must communicate within the constraints of unlicensed spectrum regulations. These regulations include power and power spectral density levels, maximum channel occupancy time (COT), channel bandwidth, and channel monitoring mechanisms. Within the same frequency band, each system must comply with these regulations, properly occupying and releasing channels to avoid interference with other RAT systems in the same band.
[0072] For the use of shared spectrum, the RAT system can adopt mandatory channel monitoring technology (for example, LBT) to access the network. That is, data can be sent only when it is detected that the current channel is not occupied. Through channel monitoring technology, it can be ensured that the shared channel is unobstructed before the terminal device transmits a signal on the shared channel. That is to say, the terminal device of the side link can obtain the channel resources of the shared spectrum by initiating LBT. Optionally, the terminal device can determine whether the channel is unoccupied by performing LBT. If the LBT process passes, the terminal device starts to send data. For example, when the terminal device of the side link obtains channel resources through LBT, it can perform corresponding detection and preparation for sending side data.
[0073] LBT initiated by a terminal device in the shared spectrum can be either Type 1 or Type 2. Type 2 LBT also includes three channel access methods: Type 2A, Type 2B, and Type 2C. Different LBT types are defined with corresponding lengths to meet the terminal device's initial channel occupation and the regulation requirements for transmission within the channel occupation after the gap duration.
[0074] The above text, combined with Figures 1 to 4, introduces that there are many limitations when the sidelink is deployed in a shared spectrum. For example, there are multiple RATs in the shared spectrum. When only LBT is performed in the SL-U, the terminal device cannot predict the mutual interference within the system, and the conflict caused by LBT failure may increase. For another example, the LBT bandwidth is 20MHz, which is much larger than the width of the sub-channel in the sidelink resource pool. Therefore, SL-U can support multiple terminal devices to simultaneously send frequency division multiplexed (FDMed) signals on the LBT band to improve spectrum efficiency. However, in the absence of a centralized scheduler, it is difficult to achieve this goal by performing only LBT. For another example, it is difficult for LBT to correctly handle periodic transmissions, but periodic traffic in sidelink communications is a typical requirement, which may lead to significant performance degradation.
[0075] For example, NR-U defines a normal cyclic prefix (NCP) and an extended cyclic prefix (ECP). ECP can be applied to a 60kHz subcarrier spacing (SCS) to enable terminal devices to handle larger delay spreads and tolerate larger synchronization errors through a larger cyclic prefix (CP) length. Synchronization errors caused by propagation delays can be large. For example, the length of a 60kHz NCP is 1.17μs, corresponding to a distance of 351m. This distance is not sufficient to meet the communication range of some applications (for example, NR V2X sometimes requires a communication range of 500 / 800 / 1000m). It should be noted that the CP must adapt to the channel delay spread, so the actual communication range will be less than 351m. Terminal devices can rely on different parameter sets (numerology) to support a larger communication range. For example, a 15kHz SCS has a 4.7μs NCP. However, ECP should support at least 60kHz to support a longer sideline communication range. Of course, end devices moving at very high speeds with very low latency requirements are not the target use cases for the aforementioned NCP or ECP.
[0076] For another example, in NR-U, for the resource allocation method of dynamic grant (DG), all resources used by the terminal device are scheduled by the network device, and there is no conflict. For the resource allocation method of configured grant (CG), when the terminal device performs uplink transmission in continuous OFDM symbols on all RBs in the resource block (RB) set, a transmission conflict may occur. NR-U avoids transmission conflicts by randomly selecting channel access points. For SL-U, when multiple terminal devices monitor the channels of shared spectrum resources, there will be conflicts between multiple terminal devices in the channel access position. In related technologies, SL-U can provide multiple access points for terminal devices by supporting access point extension (CPE), thereby reducing conflicts.
[0077] However, when the shared resources are determined, how the terminal device providing the shared resources configures the CPE and how to send CPE indication information to the terminal device are issues that need to be resolved.
[0078] To address some of the aforementioned issues, embodiments of the present application propose a method for sideline communication. This method determines CPEs based on subcarrier spacing and enables CPE configuration based on the duration of symbols or timeslots, ensuring that one or more CPEs are present during the symbols or timeslots in which terminal devices access channels. These CPEs can be used to manage the channel access positions of multiple terminal devices, thereby reducing access conflicts between multiple terminal devices. For ease of understanding, the method proposed in embodiments of the present application is described in detail below in conjunction with Figure 5.
[0079] 5 , in step S510 , a first terminal device determines first configuration information of a first shared resource.
[0080] The first terminal device is any of the aforementioned terminal devices for sidelink communication. For example, the first terminal device can be a vehicle in V2X or a pedestrian in V2X. In another example, the first terminal device can be a transmitting terminal in a sidelink or a receiving terminal in a sidelink.
[0081] The first terminal device may be a communication device that needs to transmit data in side-by-side communication. The first terminal device may engage in unicast, multicast, or broadcast communication with other terminal devices. In some embodiments, the first terminal device may be a group leader terminal initiating a multicast or broadcast communication, or a group member in a multicast or broadcast communication. For example, in V2X, the first terminal device may be a vehicle conducting a multicast communication with other vehicles, or another vehicle in the multicast communication.
[0082] In some embodiments, the first terminal device may be located within or outside the network coverage area. When located within the network coverage area, the first terminal device may perform channel monitoring in the shared spectrum based on the configuration of the network device.
[0083] In some embodiments, the first terminal device may be a terminal device that provides COT sharing for the sidelink. For example, in V2X, the first terminal device may provide COT sharing for nearby vehicles, allowing these vehicles to access the channel through channel monitoring. In some embodiments, the first terminal device may be a terminal device that performs channel monitoring for COT sharing to obtain shared resources. For example, in V2X, the first terminal device may acquire COT shared resources for the sidelink to send sidelink transmissions if LBT is successful.
[0084] The first shared resource is a time-frequency resource in the shared spectrum. The first shared resource can be a resource within the COT shared spectrum or a resource outside the COT shared spectrum. In some embodiments, the first shared resource can be a time-frequency resource within the COT duration. In some embodiments, the first shared resource can be a time-frequency resource outside the COT duration.
[0085] In some embodiments, the first shared resource is a plurality of RB sets in a shared spectrum. Exemplarily, the first shared resource may include RB resources reserved for a terminal device to facilitate periodic sidelink transmission by the terminal device. For example, sidelink control information (SCI) indicating the first shared resource may include resource reservation information. Exemplarily, the first shared resource may include a portion of the RB sets in a COT shared resource, or may include all of the RB sets in the COT shared resource.
[0086] In some embodiments, the first shared resource may be used by the first terminal device or other terminal devices to transmit a side channel. The side channel transmitted by the terminal device may be a PSSCH or a PSCCH, which is not limited here.
[0087] The first terminal device determines the first configuration information of the first shared resource, which means that the first terminal device can determine the first configuration information through configuration or by receiving information. In some embodiments, when the first terminal device is a terminal device that provides the first shared resource, the first configuration information can be directly determined. In some embodiments, when the first terminal device is a terminal device that sends a sidelink channel through the first shared resource, the first configuration information can be determined based on COT shared information (SI) of the first shared resource.
[0088] The first configuration information may include indication information of the CPE. In some embodiments, the indication information of the CPE may be included in the COT shared information. That is, the COT shared information may indicate the configuration mode and configuration parameters of the CPE through the first configuration information.
[0089] In some embodiments, the first configuration information may be carried in the SCI information sent by the first terminal device. The first terminal device may send the SCI information via a shared spectrum. Exemplarily, when the COT shared information is carried in the SCI information, the first configuration information may be carried in the SCI information following the COT shared information. For example, in addition to the original identification (identity, ID) information and destination ID information and multicast ID information of the COT share, the SCI information may also include the first configuration information indicating the CPE. Exemplarily, the first configuration information may be carried separately in the SCI information. For example, the SCI information may include the ID information of the CPE group.
[0090] Taking Figures 3 or 4 as an example, the first configuration information can be carried in a first sidelink channel that includes the first-stage SCI (SCI-1) and the second-stage SCI (SCI-2). The first sidelink channel can include the PSSCH and the PSCCH. Specifically, the first configuration information can be carried in the first-stage SCI and / or the second-stage SCI. In other words, the first configuration information can appear separately or together in both stages of the SCI.
[0091] The first configuration information may be used to indicate one or more CPEs corresponding to the first shared resource. The CPE corresponding to the first shared resource refers to the CPE through which the terminal device can access the first shared resource. In other words, the CPE can be used by the terminal device to determine the time domain location for accessing the first shared resource.
[0092] In some embodiments, the first shared resource may correspond to one CPE. That is, the time domain location of the CPE used for the terminal device to access the first shared resource in the first configuration information is set to one. In some embodiments, the first shared resource may correspond to multiple CPEs. Multiple CPEs can be used for multiple terminal devices to access the first shared resource.
[0093] The one or more CPEs may be determined based on the subcarrier spacing corresponding to the first shared resource. In some embodiments, the subcarrier spacing may determine the time domain resources where the one or more CPEs are located. In some embodiments, the subcarrier spacing may determine the number of CPEs. In some embodiments, the subcarrier spacing may also be used together with other parameters to determine the time domain location corresponding to the one or more CPEs.
[0094] The time domain resources where one or more CPEs are located refer to the time domain resources used to configure the CPEs. In some embodiments, the time domain resources used to configure the CPEs may be GAP symbols in the time slot structure. Since these GAP symbols do not transmit data, they can be used to configure one or more CPEs. In some embodiments, the time domain resources used to configure the CPEs may be one or more symbols preceding the next AGC symbol in the subcarrier spacing. Symbols preceding the AGC symbol generally do not transmit data either.
[0095] In some embodiments, the time domain resource where one or more CPEs are located may be 1 symbol or 2 consecutive symbols. For example, the time domain resource where one or more CPEs are located may be 1 GAP symbol.
[0096] In some embodiments, the time domain resources where one or more CPEs are located can be determined based on one or more of the following information: subcarrier spacing; duration of the first shared resource; and whether the first shared resource has reserved resources.
[0097] For example, for a 15 kHz subcarrier spacing, the time domain location of one or more CPEs may be set within one symbol before the next AGC symbol corresponding to the subcarrier spacing. For 30 kHz and 60 kHz subcarrier spacing, the time domain location of one or more CPEs may be set within a maximum of two symbols before the next AGC symbol corresponding to the subcarrier spacing.
[0098] For example, the duration of the first shared resource may be the COT duration. Depending on the COT duration, resource conflicts may occur between multiple different terminal devices. Specifically, because terminal devices may need sufficient time to receive / decode COT shared information and prepare for sideline transmission, within the COT duration, the time domain position of one or more CPEs may be set within a maximum of two symbols before the next AGC symbol. Outside the COT duration, the time domain position of one or more CPEs may be set within a maximum of one symbol before the next AGC symbol.
[0099] Exemplarily, the first shared resource is an RB resource. If the RB resource is reserved, the time domain location of one or more CPEs can be set within a maximum of two symbols before the next AGC symbol; if the RB resource is not reserved, the time domain location of one or more CPEs can be set within a maximum of one symbol before the next AGC symbol. Alternatively, if the RB resource is reserved, the time domain location of one or more CPEs can be set within a maximum of one symbol before the next AGC symbol; if the RB resource is not reserved, the time domain location of one or more CPEs can be set within a maximum of two symbols before the next AGC symbol.
[0100] In some embodiments, the subcarrier spacing can also be used to determine the number of CPEs. Different subcarrier spacings correspond to different time unit durations. The time unit can be a time slot or a symbol, which is not limited here. The larger the subcarrier spacing, the shorter the actual time length of a time slot. The time unit used to configure CPEs can be configured differently for different subcarrier spacings. For example, different CPE configuration values can be set for 15kHz, 30kHz, 60kHz, 120kHz, and other subcarrier spacings. The CPE configuration value can include the number of CPEs and the time domain location of the CPEs.
[0101] Exemplarily, for subcarrier spacing of 15kHz and 30kHz, if there is 1 symbol used to configure CPE, 2 CPEs can be (pre)configured or predefined; if there are 2 symbols used to configure CPE, 7 CPEs can be (pre)configured or predefined.
[0102] For example, for a subcarrier spacing of 60 kHz, if there is 1 symbol used to configure CPE, only 1 CPE can be (pre)configured or predefined; if there are 2 symbols used to configure CPE, 4 CPEs can be (pre)configured or predefined.
[0103] In some embodiments, the subcarrier spacing may be used together with other information to determine one or more time domain locations corresponding to one or more CPEs. The time domain location corresponding to a CPE refers to the time domain location at which a terminal device can access a channel. The time domain location corresponding to a CPE may also be referred to as the starting location of the CPE or a candidate location of the CPE.
[0104] As a possible implementation, one or more time domain locations corresponding to one or more CPEs may be determined based on a first time interval. The first time interval may be one or more microseconds (μs). Exemplarily, the time length of the first time interval may include one or more of the following: 9 μs, 16 μs, and 25 μs. That is, when one or two symbols are determined for configuring a CPE, multiple CPEs may form a position set within the symbol, and the position set may be an access position group based on 9 μs, 16 μs, and 25 μs intervals, respectively.
[0105] Exemplarily, the first time interval can be any of the following: the time interval between a first CPE among one or more CPEs and the starting position of the time domain resource where the CPE is located; the time interval between two adjacent CPEs among one or more CPEs; or the time interval used to determine the time domain location of one or more CPEs. It should be noted that the configuration of a CPE may require multiple different first time intervals. The different first time intervals can be of different types or of different lengths.
[0106] Optionally, when the first time interval is the time interval between the first CPE and the starting position of the time domain resource where the CPE is located, the first time interval can be used to determine the time domain position of the first CPE. As shown in Figure 6, different time intervals can determine the time domain positions corresponding to different CPEs. Referring to Figure 6, two CPEs are configured in the GAP symbol (sym#13) of time slot 610, and the AGC symbol following the GAP symbol is the first symbol of time slot 620. When the first time interval is 16 μs, the corresponding CPE is CPE632, and when the first time interval is 25 μs, the corresponding CPE is CPE634.
[0107] Optionally, when the first time interval is the time interval between two adjacent CPEs, the first time interval can be used to determine the time domain positions of the multiple CPEs. For example, when the first time interval is 16 μs, the time domain positions of the multiple CPEs can be determined based on the time domain position of the first CPE and the 16 μs time interval.
[0108] Optionally, when the first time interval is a time interval for determining the time domain locations of one or more CPEs, the first time interval can be used to determine grouping of multiple CPEs or to determine the time domain locations of multiple CPEs within a location group. For example, CPEs with the same time interval can be grouped into a single CPE group. For another example, when a CPE group includes two location groups corresponding to first time intervals of 9 μs and 16 μs, the time domain locations of multiple CPEs within the CPE group can be determined based on 9 μs and 16 μs, respectively.
[0109] Illustratively, the time domain position of any one of the one or more CPEs may satisfy the following conditions:
[0110] [Corrected 31.05.2023 in accordance with Article 91] sym +δT};
[0111] Among them, T symis the starting position of the time domain resource where one or more CPEs are located, and δT is the second time interval between any CPE and the starting position of the time domain resource. The second time interval may include one or more of the first time intervals described above, or may be other time intervals.
[0112] As another possible implementation, the time domain location of one or more CPEs may also be determined based on the location of the PSCCH / PSSCH transmission resources. For example, for transmissions within the COT and transmissions outside the COT, a group of CPEs may be (pre-)configured or predefined based on the subcarrier spacing, respectively.
[0113] The above describes the number and time domain location of CPEs determined based on subcarrier spacing. For ease of understanding, the following describes possible configurations of CPEs under different subcarrier spacings in conjunction with Figures 7 to 9.
[0114] As shown in Figure 7, for subcarrier spacings of 15kHz and 30kHz, the time domain resource used to configure a CPE is one symbol. This symbol is symbol 13 (sym#13) of the current timeslot. Symbol 12 (sym#12) preceding symbol 13 is used to transmit the PSSCH or PSCCH, and symbol 0 (sym#0) following symbol 13 is used to transmit the AGC for the next timeslot. Within symbol 13, two CPE time domain locations can be configured: CPE 702 (index#0) and CPE 704 (index#1).
[0115] As shown in Figure 7, the first time interval is the time interval between the CPE and the starting position of the time domain resource. The first time interval corresponding to CPE702 is 16 μs, and the first time interval corresponding to CPE704 is 25 μs.
[0116] [Corrected 31.05.2023 according to Rule 91] The time domain positions of the two CPEs in Figure 7 can be expressed as {T sym +16μs, T sym +25μs}. Of course, a CPE can also be (pre-)configured or pre-defined in symbol 13, and the CPE can be {T sym +16μs} or {T sym +25μs}.
[0117] As shown in Figure 8 , for a 60kHz subcarrier spacing, the time domain resource used to configure a CPE is one symbol. This symbol is the same as in Figure 7 and will not be repeated here. Within symbol 13, only one CPE time domain location can be configured, namely, CPE 802 (index #0).
[0118] [Corrected 31.05.2023 according to Rule 91] As shown in FIG8 , the first time interval is the time interval between the CPE and the starting position of the time domain resource. In the example of FIG8 , the first time interval corresponding to CPE802 is 16 μs. Therefore, the time domain position of CPE802 can be expressed as {T sym +16μs}.
[0119] As shown in Figure 9, for subcarrier spacings of 15kHz and 30kHz, the time domain resources used to configure a CPE are two symbols. These two symbols are symbol 12 (sym#12) and symbol 13 (sym#13) of the current timeslot. Symbol 0 (sym#0) following symbol 13 is the AGC symbol for the next timeslot. Within symbols 12 and 13, seven CPE time domain locations can be configured: CPE901 (index#0) through CPE907 (index#6).
[0120] As shown in Figure 9, when the first time interval is the interval between a CPE and the starting position of the time domain resource, the first time interval is 16 μs. When the first time interval is the interval between two adjacent CPEs, the first time interval is 9 μs. Due to the limited duration of two symbols, the time interval between the last two CPEs is determined based on actual conditions.
[0121] [Corrected 31.05.2023 according to Rule 91] The time domain positions of the 7 CPEs in Figure 9 can be expressed as {T sym +16μs, T sym +25μs, T sym +34μs, T sym +43μs, T sym +52μs, T sym +61μs, 0}.
[0122] [Corrected 31.05.2023 according to Rule 91] For a 60kHz subcarrier spacing, when the time domain resource used to configure CPE is 2 symbols, only the time domain positions of 4 CPEs can be (pre-)configured or predefined in these 2 symbols. The reason for configuring only 4 CPEs in 2 symbols is to ensure the time interval between adjacent CPEs to meet LBT access requirements and reduce access interference. The time domain positions of 4 CPEs in 2 symbols can be expressed as {T sym +16μs, T sym +25μs, T sym +34μs, 0}.
[0123] Continuing with FIG5 , the first configuration information may include the configuration parameters of one or more CPEs determined based on the subcarrier spacing described above, and may also include other parameter information of one or more CPEs. Specifically, the first configuration information may indicate the time domain resources where the one or more CPEs are located, the number of one or more CPEs, and one or more time domain locations corresponding to the one or more CPEs. Alternatively, the first configuration information may also include the grouping of one or more CPEs. Alternatively, the first configuration information may indicate the index of one or more CPEs for multiple terminal devices to select a CPE.
[0124] In some embodiments, the first configuration information may further indicate one or more CPE groups. The one or more CPE groups may refer to a location group of CPEs in a time domain resource. One CPE group in the one or more CPE groups may include one or more CPEs. Multiple CPE groups in the one or more CPE groups may each include one or more CPEs.
[0125] As a possible implementation, one or more CPE groups can be determined based on various information. That is, multiple CPEs can be grouped based on various information to determine one or more CPE groups. The grouping information may include CPE association priorities; time intervals associated with multiple CPEs; and whether the CPEs are CPEs corresponding to reserved resource information.
[0126] Optionally, CPEs associated with different priorities may be set as different CPE groups.
[0127] Optionally, CPEs with the same time interval can be set as a CPE group.
[0128] Optionally, if the first shared resource includes a reserved resource, CPEs corresponding to the same or different reserved resource information may be set as a CPE group.
[0129] As a possible implementation, the first configuration information may further indicate configuration parameters of one or more CPE groups. Configuration parameters are configuration values of the CPE group. The configuration parameters of the CPE group may include one or more of the following: the time domain resource where the CPE group is located, the time domain location corresponding to the CPE group, the time domain location corresponding to each CPE in the CPE group, one or more starting time domain locations corresponding to the CPE group, one or more first time intervals of the CPE group, and ID information of the CPE group.
[0130] Exemplarily, the time domain resources where the CPE group is located, the corresponding time domain position, and the time domain position corresponding to each CPE are the same as the configuration parameters of one or more CPEs mentioned above, and are not repeated here.
[0131] Exemplarily, a CPE group may correspond to one starting time domain position. The (pre-)configured / predefined starting time domain positions of different CPE groups may be the same or different.
[0132] Exemplarily, a CPE group can correspond to multiple starting time domain locations. A CPE can correspond to multiple starting time domain locations by corresponding to multiple first time intervals. For example, when a CPE group determines the time domain locations of multiple CPEs based on 16 μs and 25 μs, 16 μs and 25 μs can respectively determine the time domain locations of the two CPEs shown in Figure 6 or Figure 7. These two CPEs can be the first CPEs in two access location groups, respectively.
[0133] Exemplarily, the one or more first time intervals of the CPE group may be any one or any multiple first time intervals described above, which will not be described in detail here.
[0134] Exemplarily, the ID information of the CPE group can be used to indicate multiple CPE groups, so that the terminal device can select an appropriate CPE group or CPE to access the first shared resource.
[0135] The terminal device accessing the first shared resource is a second terminal device. In some embodiments, the second terminal device may be the first terminal device. For example, when the first terminal device is a terminal device transmitting a sidelink channel via the first shared resource, the second terminal device is the first terminal device. In some embodiments, the second terminal device is a terminal device other than the first terminal device in the sidelink. For example, when the first terminal device shares the first shared resource, the second terminal device is another terminal device in the sidelink requesting access to the first shared resource.
[0136] One or more CPEs can be used by a second terminal device to determine the time domain location for accessing the first shared resource. Based on the configured CPE, the access location of the second terminal device can be managed, thereby reducing access conflicts between multiple terminal devices. In some embodiments, when the first shared resource corresponds to a single CPE, the second terminal device can access the channel at the time domain location of the CPE. In some embodiments, when the first shared resource corresponds to multiple CPEs, the second terminal device can select a CPE from the multiple CPEs and access the channel at the time domain location of the CPE.
[0137] In some embodiments, when the first configuration information indicates multiple CPEs, multiple second terminal devices can respectively access the channel through the time domain positions corresponding to the multiple CPEs, which helps to reduce conflicts between multiple terminal devices.
[0138] The first configuration information may support multiple CPE configuration forms. For example, the first configuration information may support static configuration of the CPE using multiple CPE or CPE group configuration values. For another example, the first configuration information may support semi-static configuration of the CPE using multiple CPE or CPE group configuration values.
[0139] For example, for static configuration of a CPE, multiple CPE configuration values can be (pre-)configured. These configuration values can involve the number of symbols and the candidate location of the associated CPE, that is, the time domain resource where the CPE is located and the time domain location corresponding to the CPE, for example, 1 symbol or 2 symbols.
[0140] Optionally, static CPE group configuration is supported, allowing for (pre-)configuration of multiple CPE group configuration values. These configuration values may include the number of symbols, candidate positions for the CPE group, candidate positions for each CPE within the CPE group, and whether each group of CPE starting candidate positions includes one or more starting positions. In other words, the CPE group configuration value may indicate one or more of the following information: the time domain resource where the CPE group resides, the time domain position of the CPE group, the time domain position corresponding to each CPE in the CPE group, and one or more starting time domain positions for the CPE group.
[0141] Optionally, CPE static configuration is supported, and multiple CPE configuration values and the relationship between CPE configuration values and priorities can be (pre-)configured. The priority can include channel access priority class (CAPC), service priority, or the priority level after the service priority is matched to the CAPC.
[0142] Exemplarily, for the semi-static configuration of CPE, multiple CPE configuration values can be (pre-)configured. Configuration values can be set for subcarrier spacings of 15KHz, 30KHz, and 60KHz, respectively. Furthermore, the semi-static configuration can support the terminal device to select the time domain position for channel access based on set rules. Optionally, the terminal device can randomly select a candidate position, and the random selection can be completely random or determined based on a hash function. Optionally, the terminal device can select a candidate position based on the service characteristics or priority setting of the terminal device. That is, the first configuration information is used to semi-statically configure one or more CPEs. The semi-static configuration is used to instruct the second terminal device to determine the CPE for channel access based on one or more of the following methods: random access, hash function, service characteristics of the second terminal device, and priority corresponding to the second terminal device.
[0143] Optionally, semi-static configuration of CPE groups is supported, and multiple CPE group configuration values can be (pre-)configured. The configuration values of the CPE group can include multiple candidate positions of the CPE group, the candidate position of each CPE in the CPE group, and whether each group of CPE starting candidate positions includes one or more starting positions. For example, the CPE group can be a CPE group with a time interval of 9μs or a multiple of 9μs, or a group with a time interval of 25μs or a multiple of 25μs, or a group with a time interval of 16μs or a multiple of 16μs. For another example, the CPE group can be a CPE group configured in a mixed manner with three time intervals of 9μs, 16μs, and 25μs.
[0144] As can be seen from Figures 5 to 9, determining one or more CPEs corresponding to the first shared resource based on the subcarrier spacing can facilitate multiple terminal devices to select access points within the time unit for channel access. That is, in SL-U, PSSCH or PSCCH can support the time domain positions of multiple CPEs. When the time domain positions of multiple CPEs are (pre) configured for side PSCCH / PSSCH transmission, the second terminal device sending the side channel needs to select a CPE for channel access. If the second terminal device randomly selects the time domain position of a CPE for channel access, or if the priority is not considered when selecting the CPE, high-priority services may be blocked by low-priority services, resulting in reduced transmission performance.
[0145] For ease of understanding, this situation is exemplarily described below with reference to FIG10. Referring to FIG10, both terminal device 1 and terminal device 2 perform LBT in time slot 1010 of RB set 1. Terminal device 1 has a priority of 1, and terminal device 2 has a priority of 3, meaning that terminal device 1 has a higher priority than terminal device 2.
[0146] As shown in Figure 10, after the LBT counter reaches 0, the two terminal devices will access the channel based on the selected CPE. When the LBT counters of the two terminal devices fall back to 0 in time slot 1010, since the CPE randomly selected by terminal device 2 is earlier in time domain than the CPE randomly selected by terminal device 1, the LBT of terminal device 2 succeeds and the LBT of terminal device 1 fails. For terminal device 2, time slot 1020 can be used for terminal device 2 to transmit PSCCH or PSSCH. For terminal device 1, the status of time slot 1020 is channel busy and cannot be accessed. Therefore, terminal device 1 with high transmission priority is blocked by terminal device 2 with low priority.
[0147] To address this issue, the priority of the terminal device or the channel being transmitted can be considered when selecting a CPE. As mentioned earlier, one or more CPEs in static or semi-static configuration can be associated with a priority. For example, the time domain location of one or more CPEs can be configured based on the priority of PSCCH / PSSCH transmissions. However, how the terminal device selects a CPE based on the priority associated with the CPE also requires resolution.
[0148] The embodiment of the present application also provides a method for sideline communication, through which a terminal device with a higher priority can select a CPE with an earlier time domain location, thereby avoiding the situation where the high-priority terminal device is blocked by a low-priority terminal device.
[0149] As can be seen from the foregoing, the first shared resource can be used for the second terminal device to send a side channel. The terminal devices sharing the first shared resource can be (pre-)configured or predefined with one or more CPEs for multiple second terminal devices.
[0150] In some embodiments, the terminal devices sharing the first shared resource can configure the default CPE time domain location according to the resource reservation information. The default CPE can be the first CPE or the first CPE group, which will be explained in detail below in conjunction with the explanation of the reserved resource information.
[0151] In some embodiments, the terminal device sharing the first shared resource may pre-configure the time domain location of one or more CPEs, or may dynamically configure the time domain location of one or more CPEs.
[0152] One or more CPEs configured in a terminal device can be associated with a priority level to facilitate earlier transmission of high-priority services or terminal devices. Specifically, for sidelink transmission, the second terminal device can select a CPE based on the priority level associated with one or more CPEs in the first configuration information. In other words, the second terminal device can determine the CPE for channel access based on the priority level associated with one or more CPEs.
[0153] In some embodiments, the priority associated with one or more CPEs may be a quality of service (QoS) priority. For example, if the first shared resource is used by the second terminal device to transmit a side channel such as a PSCCH / PSSCH, the priority corresponding to the side channel may be used to select a CPE for channel access.
[0154] In some embodiments, the priority associated with one or more CPEs may be a channel access priority. The channel access priority may be represented by a CAPC. For example, a transmission with a lower CAPC level may select a CPE located later in the time domain, while a transmission with a higher CAPC level may select a CPE located earlier in the time domain.
[0155] In some embodiments, the priority associated with one or more CPEs may be a priority obtained by matching a service priority with a channel access priority. For example, different packet quality of service identities (PQIs) indicated by the QoS may be matched to three priorities (class 1 to class 3) of the CAPC, respectively. For example:
[0156] PQI 90 / 91 / 92 / 93 / 21 / 22 / 23 / 55 / 56 / 57 / 58 and PQI 24 / 26 / 60 can be matched to CAPC priority class 1 (mapping PQI 90 / 91 / 92 / 93 / 21 / 22 / 23 / 55 / 56 / 57 / 58 to CAPC priority class 1; mapping PQI 24 / 26 / 60 to CAPC priority class 1);
[0157] Mapping PQI 59 / 61 to CAPC priority class 3;
[0158] PQI 25 matches CAPC priority class 2 (mapping PQI 25 to CAPC priority class 2).
[0159] Optionally, in the case of one or more CPE time domain positions configured according to the priority of PSCCH / PSSCH transmission, the time domain position of the CPE can be selected in a predefined and / or specified manner, and the pre-setting and / or specification can be carried in the SCI information.
[0160] Optionally, in the case of one or more CPE time domain positions configured based on the priority of PSCCH / PSSCH transmission, the order of the time domain positions may be determined based on the service priority or CAPC, or a combination of service priority and CAPC. For example, a time domain position with an earlier time domain position is given a higher priority, and a time domain position with a later time domain position is given a lower priority.
[0161] Multiple terminal devices can select a CPE based on the aforementioned priorities. Optionally, in the case of partial or full RB set resource allocation, a terminal device can use a hash function to select a CPE for channel access, based on the time-domain locations of one or more CPEs configured based on the priority of PSCCH / PSSCH transmissions. For example, the CPE-associated CAPC value can be used as one of the criteria for a terminal device to select a CPE.
[0162] It should be noted that if the number of terminal devices requesting access within a period of time is less than or equal to the number of CPEs, it can be guaranteed that each terminal device can select a CPE. However, if the number of terminal devices requesting access within a period of time is greater than the number of CPEs, it cannot be guaranteed that each terminal device can be assigned to a CPE. In this case, one or more CPEs can only satisfy terminal devices with higher service priorities corresponding to the data to be transmitted, or can determine the terminal devices for channel access based on the first-come, first-served principle. When determining based on priority, for terminal devices with lower priority, it may take a long time to be assigned to an access point for channel access. When determining based on first-come, first-served, it cannot be guaranteed that emergency services or high-priority services will be accessed within the subsequent time t, which may be in milliseconds or microseconds.
[0163] In order to more reasonably allocate CPE to multiple terminal devices, the first terminal device sharing resources can evaluate multiple terminal devices that attempt to access within a period of time, thereby allocating limited CPE to terminal devices that are more in need.
[0164] In some embodiments, a first terminal device sharing resources can be configured with a timing device, such as timer T1. When a terminal device requests access, the first terminal device may not initially access the terminal device that first accessed, but instead activate the timing device. Multiple terminal devices may request access while the timing device is running. When the timing device reaches a set point, the first terminal device may allocate CPEs to some or all of the multiple terminal devices requesting access, based on the number of CPEs.
[0165] The time length set by the timing device is the first time period, for example, the first time period is the length of the T1 timer. The first time period can be part or all of the time period within the above-mentioned period, which is not limited here.
[0166] When the number of terminal devices accessing the channel during the first time period is greater than the number of one or more CPEs, it may be determined based on one or more information which terminal devices can access the channel through these CPEs. For example, if there are M CPEs indicated by the first configuration information, and there are N terminal devices requesting channel access through these M CPEs during the first time period, where M and N are both natural numbers greater than 0, when N>M, it is determined based on the one or more information which of the N terminal devices can access the first shared resource through the M CPEs.
[0167] In some embodiments, one or more information used to determine the terminal devices that can be accessed among N terminal devices may include: the time period during which the N terminal devices wait for access, the earliest time point when the N terminal devices initiate an access request, and the service priority corresponding to the data to be transmitted by the N terminal devices.
[0168] Optionally, the time period during which the N terminal devices wait for access may refer to the time period from when the LBT counter of a terminal device among the N terminal devices reaches 0 to when the terminal device can access the channel. Different time periods during which the N terminal devices wait for access may also represent the order in which the N terminal devices request access.
[0169] Optionally, the earliest time point when the N terminal devices initiate an access request may refer to the earliest time point when the LBT counter in the N terminal devices is 0 within the first time period. In other words, the first time point when the terminal device that accesses the channel initiates an access request within the first time period.
[0170] Optionally, when the first terminal device provides the first shared resource, the time period during which the N terminal devices wait for access may be related to the duration of a timer started by the first terminal device. For example, the timer may be started in response to an access request from the terminal device that earliest accesses the channel among the N terminal devices. This timer may be used by the first terminal device to determine the number of terminal devices that have requested access within the first time period, that is, the value of N.
[0171] Optionally, the service priority corresponding to the data to be transmitted by the second terminal device may refer to the service priority of the side channel to be transmitted, or may refer to the CAPC corresponding to the side channel to be transmitted, or may refer to the CAPC determined based on the service priority. When determined based on the priority, access to the second terminal device with a higher priority level can be guaranteed.
[0172] Optionally, when the number of terminal devices requesting access within a certain time period is greater than the number of CPEs, the above three types of information may be considered simultaneously. In other words, the waiting period, the earliest access request time point, and the priority may be considered simultaneously to determine whether the terminal devices corresponding to the three factors are allowed to access.
[0173] Optionally, some or all of the above factors may determine a first parameter of each of the N terminal devices. The first parameter may be used to determine whether the corresponding terminal device can access the first shared resource through the M CPEs.
[0174] The following is an exemplary description of possible calculation methods of the first parameter in conjunction with the schematic diagram of channel access by multiple terminal devices in FIG11 .
[0175] Referring to Figure 11, on the timeline, T0 represents the earliest time point at which N terminal devices initiate access requests. A timer is started at T0, and the timer's set time is reached at T1. Therefore, T represents the duration of the timer, i.e., the first time period, T = T1 - T0.
[0176] Continuing with Figure 11, time points 1102 and 1103 represent the arrival times of the second and third terminal devices, respectively (the times at which access requests are initiated). Taking T0 as a reference point, t2 and t3 can represent the time periods between time points 1102 and 1103, respectively, and T0. In other words, T-t2 and T-t3 represent the time periods that the second and third terminal devices, respectively, wait for access.
[0177] Based on this, taking T0 as the reference point, t i Tt represents the time period between the time when the i-th terminal device requests access and T0, i is the time that the i-th terminal device waits for access, where i is a natural number from 0 to N-1.
[0178] Furthermore, the service priority of the i-th terminal device is set to Q i , Q i The value is set to [1,2,3,4,…,K]. That is, Q i It is a natural number from 1 to K, and K>1. 1 represents the highest priority, and K represents the lowest priority. i PQI can also be used instead.
[0179] In order to comprehensively consider the order and priority of access of multiple terminal devices, the first parameter of the i-th terminal device among N terminal devices can be expressed as:
[0180] Wherein, T represents the first time period; α and β represent weighting factors, where α + β = 1, and both α and β are rational numbers greater than or equal to 0. The first terminal device may adjust the weighting factors based on specific implementation and scenarios. The meanings of the other letters are as described above.
[0181] Exemplarily, when N>M, the terminal device among the N terminal devices that can access the first shared resource through the M CPEs can be determined by comparing the first parameter. For example, the first parameter of the terminal device among the N terminal devices that can access the first shared resource through the M CPEs satisfies the following conditions:
[0182] Among them, min() means taking the minimum value.
[0183] Specifically, the terminal device with the smallest first parameter among the N terminal devices can be selected in sequence according to the above formula. Specifically, the terminal device with the smallest first parameter is first selected from the N terminal devices, and then the terminal device with the smallest first parameter is selected from the remaining N-1 terminal devices, until M terminal devices are selected that can access the channel through the M CPEs.
[0184] As a specific embodiment, when there is only one pre-configured CPE, if several terminal devices attempt to access the CPE, the terminal device that uses the CPE can be determined based on the service priority matching the channel priority. Specifically, when the LBT counters of multiple terminal devices successively drop back to 0, the terminal devices sharing the resource can start the T1 timer based on the terminal device that accessed the resource earliest. When the T1 timer reaches the first set time period, the priority levels of the multiple terminal devices can be compared. Access is guaranteed for class 1 terminal devices first, in the order from class 1 to class 3.
[0185] As another specific embodiment, when the pre-configured CPE is set to M, if N terminal devices greater than M request channel access within a first time period, the terminal devices that can access the channel through the indicated M CPEs can be determined based on the first parameters corresponding to the N terminal devices. For example, the first parameters of the N terminal devices are sorted in ascending order, and the terminal devices corresponding to the first M first parameters can access the first shared resource through the M CPEs.
[0186] As another specific embodiment, when the pre-configured CPE is set to 1, if N terminal devices greater than 1 make channel access requests within a first time period, the first parameter of the terminal device that can access the first shared resource through the CPE satisfies the following conditions:
[0187] As another specific embodiment, when the pre-configured CPE is set to 1, if multiple terminal devices try to access. The first terminal device that shares resources can set the timer T1. Furthermore, the first terminal device can simultaneously consider the order of access of multiple terminal devices (the waiting time δ of multiple terminal devices), the length of the T1 timer, and the priority to determine the terminal devices that can access. That is to say, if several terminal devices are trying to access, when their LBT counters fall back to 0 in time slot n, the T1 timer is started based on the time when the earliest counter falls back to 0. When the T1 timer reaches the specified time, the priority levels and waiting times δ of several terminal devices are compared to determine the terminal devices that can access the channel through the CPE. For example, you can follow Based on the parameters corresponding to multiple terminal devices attempting to access, a terminal device that can access the channel is selected.
[0188] As can be seen above, one or more configured CPEs can manage access to multiple terminal devices. For example, when the number of connected terminal devices exceeds the number of CPEs, priority is given to terminal devices with higher service priorities or longer waiting times. Figure 12 is a schematic diagram of a possible implementation of an embodiment of the present application.
[0189] 12 , the time domain resource used to configure the CPE is the last symbol (#13) of time slot 1210. In symbol 13, multiple CPEs are configured based on a certain time interval.
[0190] In Figure 12, CPE1231 is the transmission starting point of terminal device 1, and CPE1232 is the transmission starting point of terminal device 2.
[0191] As shown in Figure 12, the time domain positions of the pre-configured CPE are set to multiple. The access position groups of the multiple CPEs can be set with time intervals of 9μs, 16μs, and 25μs respectively. If the access position of the terminal device is before the boundary, the terminal device can use the CPE to start transmission. As shown in Figure 12, symbol 13 is divided into 9μs access position groups, and each terminal device can select one of these access positions as the transmission starting point according to the standard. The time domain positions corresponding to terminal device 1 and terminal device 2 are both in time slot 1210, and CPE transmission can be used. The two terminal devices can synchronize the additional LBT to this point and start transmission in it during clear channel assessment (CCA). If the access position of the terminal device is after the boundary, the transmission is started by puncturing the AGC symbol. For example, if the access position selected by a terminal device appears in symbol 0 of time slot 1220, the terminal device can start transmission by puncturing the AGC symbol.
[0192] As mentioned above, in sideline communications, a terminal device may require periodic channel resources for periodic transmission. In this case, some resources are typically reserved in the resource pool for periodic or predictable data transmission. Information about reserved resources can be indicated via the SCI information.
[0193] In some embodiments, if the first shared resource is shared by a first terminal device, the first terminal device may predefine / preconfigure a first CPE or a first CPE group corresponding to the reserved resource information based on the resource reservation information. The first CPE or the first CPE group is the default CPE described above, and the time domain location of the default CPE may be one or more.
[0194] Optionally, the first CPE or the first CPE group is used for the terminal device corresponding to the resource reservation information to perform channel access. In other words, the resource reservation information can be used as a criterion for the terminal device to select a CPE from multiple CPEs or CPE groups.
[0195] Optionally, the resource reservation information may include resource reservation information of a terminal device that performs COT sharing, and may also include resource reservation information of other terminal devices.
[0196] Optionally, resource reservation information may be included in the SCI information. The SCI information may also indicate whether the resource reservation information is available. When the resource reservation information is used by a second terminal device to transmit a sidelink channel, if the resource reservation information is available, the time domain location of the first CPE or any CPE in the first CPE group may be used for channel access by the second terminal device. If the resource reservation information is not available, the CPE for channel access by the second terminal device may be determined based on the priority of the sidelink channel.
[0197] For example, if resource reservation information for a transmission resource slot is available, the terminal device's transmission begins at the default CPE's time domain location. If resource reservation information for a transmission resource slot is not available, the terminal device's transmission begins at a subset of multiple CPE time domain locations based on service priority. The terminal device may randomly select a CPE time domain location within the subset of multiple CPE time domain locations.
[0198] Optionally, when there are reserved resources in the first shared resources, the second terminal device can determine whether the reserved resources can be used for transmission based on the measured signal quality. For example, if the reference signal receiving power (RSRP) of the reserved resources of other terminal devices measured by the second terminal device is lower than the RSRP threshold of the side link, the second terminal device can use the resources overlapping with the reserved resources for its PSCCH / PSSCH transmission. The second terminal device can randomly select the time domain position of a CPE from the time domain positions of one or more CPEs (pre-)configured according to the priority of PSCCH / PSSCH transmission.
[0199] Optionally, the resources selected by the second terminal device may overlap with the reserved resources of other terminal devices in the time domain. Although the two resources overlap in the time domain, they may be interleaved in the frequency domain. Therefore, regardless of whether the second terminal device uses a full RB set or a partial RB set for PSCCH / PSSCH transmission, the second terminal device can use the default CPE time domain position.
[0200] In some embodiments, for resource allocation of a partial RB set, the second terminal device can select the CPE time domain position based on the highest priority among the detected reservation information and the sent reservation information; if there is no reservation information, the CPE time domain position is selected based on its own priority.
[0201] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 12. The device embodiment of the present application is described in detail below in conjunction with Figures 13 and 14. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for portions not described in detail, reference can be made to the above method embodiment.
[0202] FIG13 is a schematic block diagram of an apparatus for wireless communication according to an embodiment of the present application. The apparatus 1300 may be any terminal device described above. The apparatus 1300 shown in FIG13 includes a determining unit 1310.
[0203] Determination unit 1310 can be used to determine first configuration information of the first shared resource, and the first configuration information is used to indicate one or more CPEs corresponding to the first shared resource; wherein, the one or more CPEs are determined based on the subcarrier spacing corresponding to the first shared resource, and the one or more CPEs are used by the second terminal device to determine the time domain position for accessing the first shared resource.
[0204] Optionally, the first configuration information is also used to indicate the time domain resources where one or more CPEs are located, and the one or more time domain positions corresponding to the one or more CPEs are determined based on a first time interval, and the first time interval is one of the following time intervals: the time interval between the first CPE among the one or more CPEs and the starting position of the time domain resource; the time interval between two adjacent CPEs among the one or more CPEs; the time interval used to determine the time domain positions of one or more CPEs.
[0205] Optionally, the time length of the first time interval includes one or more of the following: 9 microseconds, 16 microseconds, and 25 microseconds.
[0206] [Corrected 31.05.2023 according to Rule 91] Optionally, the time domain position of any one of the one or more CPEs satisfies the following conditions: {T sym +δT};
[0207] [Corrected 31.05.2023 in accordance with Article 91]
[0208] Among them, T sym is the starting position of the time domain resource, δT is the second time interval between any CPE and the starting position of the time domain resource, and the second time interval includes one or more first time intervals.
[0209] Optionally, the time domain resources where one or more CPEs are located are determined based on one or more of the following information: subcarrier spacing; duration of the first shared resource; and whether the first shared resource has reserved resources.
[0210] Optionally, the time domain resource where one or more CPEs are located includes 1 symbol or 2 consecutive symbols.
[0211] Optionally, the first shared resource is used for the second terminal device to send a side channel, and the priorities associated with one or more CPEs are used by the second terminal device to determine the CPE for channel access, and the priorities include one or more of the following: the service priority corresponding to the side channel; the CAPC corresponding to the side channel.
[0212] Optionally, the first configuration information is used to indicate M CPEs, and the M CPEs are used for channel access by N terminal devices within a first time period. If N>M, the terminal devices among the N terminal devices that access the first shared resource through the M CPEs are determined based on one or more of the following information: the time period during which the N terminal devices wait for access; the earliest time point when the N terminal devices initiate an access request; and the service priority corresponding to the data to be transmitted by the N terminal devices.
[0213] Optionally, the first shared resource is shared by the first terminal device, and the time period during which the N terminal devices wait for access is related to the duration of the timer started by the first terminal device. The apparatus 1300 also includes a starting unit, which can be used to start the timer in response to an access request from the terminal device that performs channel access earliest among the N terminal devices, and the timer is used by the first terminal device to determine the value of N.
[0214] Optionally, when N>M, the first parameter of the terminal device among the N terminal devices that accesses the first shared resource through the M CPEs satisfies the following conditions:
[0215] Among them, α and β represent weight factors, t i It represents the time period between the time when the i-th terminal device initiates an access request and the time when the earliest access request is initiated among N terminal devices, i is a natural number from 0 to N-1, T represents the first time period, Q i Indicates the service priority of the data to be transmitted by the i-th terminal device among N terminal devices, Q i It is a natural number from 1 to K, K>1, and K represents the lowest priority.
[0216] Optionally, the first configuration information is sent through the shared spectrum, the first configuration information is carried in the first side channel, the first side channel includes the first stage SCI and the second stage SCI, and the first configuration information is carried in the first stage SCI and / or the second stage SCI.
[0217] Optionally, the first configuration information is also used to indicate one or more CPE groups to which multiple CPEs belong, and the one or more CPE groups are determined based on one or more of the following information: priority of CPE association; time intervals corresponding to multiple CPEs; whether the CPE is the CPE corresponding to the reserved resource information.
[0218] Optionally, the first configuration information is also used to indicate configuration parameters of one or more CPE groups, and the configuration parameters of one or more CPE groups include one or more of the following: the time domain resources where the CPE group is located; the time domain position corresponding to the CPE group; one or more starting time domain positions corresponding to the CPE group; the time domain position corresponding to each CPE in the CPE group; one or more first time intervals of the CPE group; and ID information of the CPE group.
[0219] Optionally, the configuration parameters of one or more CPE groups include multiple starting time domain positions corresponding to the CPE group, multiple first time intervals corresponding to the CPE, and the multiple starting time domain positions include multiple starting time domain positions determined by the CPE group based on the multiple first time intervals.
[0220] Optionally, the first shared resource is shared by the first terminal device, and the apparatus 1300 further includes a configuration unit, which can be used to predefine / preconfigure the first CPE or the first CPE group corresponding to the reserved resource information according to the resource reservation information.
[0221] Optionally, the reserved resource information is used for the second terminal device to send the side channel. If the resource reservation information is available, the time domain position of the first CPE or any CPE in the first CPE group is used for the second terminal device to access the channel; if the resource reservation information is not available, the CPE for the second terminal device to access the channel is determined according to the priority of the side channel.
[0222] Optionally, the first configuration information is used by the first terminal device to semi-statically configure one or more CPEs, and the semi-static configuration is used to instruct the second terminal device to determine the CPE for channel access based on one or more of the following methods: random access, hash function, service characteristics of the second terminal device, and priority corresponding to the second terminal device.
[0223] FIG14 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in FIG14 indicate that the unit or module is optional. Apparatus 1400 may be used to implement the method described in the above method embodiment. Apparatus 1400 may be a chip or a terminal device.
[0224] The device 1400 may include one or more processors 1410. The processor 1410 may support the device 1400 to implement the method described in the method embodiment above. The processor 1410 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 be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
[0225] The apparatus 1400 may further include one or more memories 1420. The memories 1420 store programs that can be executed by the processor 1410, causing the processor 1410 to perform the methods described in the above method embodiments. The memories 1420 may be independent of the processor 1410 or integrated into the processor 1410.
[0226] The apparatus 1400 may further include a transceiver 1430. The processor 1410 may communicate with other devices or chips via the transceiver 1430. For example, the processor 1410 may transmit and receive data with other devices or chips via the transceiver 1430.
[0227] 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 device or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal device or network device in each embodiment of the present application.
[0228] 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. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, or a magnetic tape), an optical medium (e.g., a digital versatile disc (DVD)), or a semiconductor medium (e.g., a solid state drive (SSD)).
[0229] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal device or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.
[0230] 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 can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions 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 instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.
[0231] The present application also provides a computer program that can be applied to a terminal device or network device provided in the present application, and enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.
[0232] The terms "system" and "network" in this application may be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this 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," as well as any variations thereof, are intended to cover non-exclusive inclusions.
[0233] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.
[0234] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.
[0235] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., including a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to a definition in a protocol.
[0236] 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, a NR protocol, and related protocols used in future communication systems, and this application does not limit this.
[0237] In the embodiments of the present application, determining B based on A does not mean determining B only based on A. B can also be determined based on A and / or other information.
[0238] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. 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 document generally indicates that the related objects are in an "or" relationship.
[0239] 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.
[0240] In the several embodiments provided in this 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 merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, 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.
[0241] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0242] 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.
[0243] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application 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 application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
Claims
1. A method for sideline communication, characterized in that: include: The first terminal device determines first configuration information of a first shared resource, where the first configuration information is used to indicate one or more access point extension CPEs corresponding to the first shared resource; The one or more CPEs are determined based on the subcarrier spacing corresponding to the first shared resource, and the one or more CPEs are used by the second terminal device to determine the time domain position for accessing the first shared resource.
2. The method according to claim 1, characterized in that: The first configuration information is further used to indicate the time domain resources where the one or more CPEs are located, and the one or more time domain locations corresponding to the one or more CPEs are determined according to a first time interval, and the first time interval is one of the following time intervals: a time interval between a first CPE of the one or more CPEs and a starting position of the time domain resource; A time interval between two adjacent CPEs among the one or more CPEs; The time interval used to determine the time domain location of the one or more CPEs.
3. The method according to claim 2, characterized in that The time length of the first time interval includes one or more of the following: 9 microseconds, 16 microseconds, and 25 microseconds.
4. [Corrected 31.05.2023 in accordance with Rule 91] A method according to claim 2 or 3, characterized in that The time domain position of any one of the one or more CPEs satisfies the following conditions: sym +δT}; Among them, the T sym is the starting position of the time domain resource, the δT is a second time interval between any one of the CPEs and the starting position of the time domain resource, and the second time interval includes one or more of the first time intervals.
5. The method according to any one of claims 1 to 4, characterized in that The time domain resources where the one or more CPEs are located are determined according to one or more of the following information: Subcarrier spacing; a duration of the first shared resource; Whether the first shared resource has a reserved resource.
6. The method according to claim 5, characterized in that The time domain resource where the one or more CPEs are located includes 1 symbol or 2 consecutive symbols.
7. The method according to any one of claims 1 to 6, characterized in that The first shared resource is used by the second terminal device to send a side channel, and the priorities associated with the one or more CPEs are used by the second terminal device to determine a CPE for channel access, where the priorities include one or more of the following: The service priority corresponding to the side channel; The channel access priority level CAPC corresponding to the side channel.
8. The method according to any one of claims 1 to 7, characterized in that The first configuration information is used to indicate M CPEs, and the M CPEs are used for channel access by N terminal devices in a first time period, where M and N are both natural numbers greater than 0. If N>M, the terminal devices among the N terminal devices that access the first shared resource through the M CPEs are determined according to one or more of the following information: The time period during which the N terminal devices wait for access; The earliest time when the N terminal devices initiate access requests; The service priorities corresponding to the data to be transmitted by the N terminal devices.
9. The method according to claim 8, characterized in that The first shared resource is shared by the first terminal device, the time period during which the N terminal devices wait for access is related to the duration of a timer started by the first terminal device, and the method further includes: In response to an access request from a terminal device that accesses the channel earliest among the N terminal devices, the first terminal device starts a timer, and the timer is used by the first terminal device to determine the value of N.
10. The method according to claim 8 or 9, characterized in that: When N>M, the first parameter of the terminal device among the N terminal devices that accesses the first shared resource through the M CPEs satisfies the following conditions: Among them, α and β represent weight factors, t i represents the time period between the time point when the i-th terminal device among the N terminal devices initiates an access request and the time point when the earliest access request is initiated, i is a natural number from 0 to N-1, T represents the first time period, Q i represents the service priority corresponding to the data to be transmitted by the i-th terminal device among the N terminal devices, Q i It is a natural number from 1 to K, K>1, and K represents the lowest priority.
11. The method according to any one of claims 1 to 10, characterized in that The first configuration information is sent through a shared spectrum. The first configuration information is carried in a first side channel. The first side channel includes first-stage side control information SCI and second-stage SCI. The first configuration information is carried in the first-stage SCI and / or the second-stage SCI.
12. The method according to any one of claims 1 to 11, characterized in that The first configuration information is further used to indicate one or more CPE groups to which the multiple CPEs belong, and the one or more CPE groups are determined according to one or more of the following information: The priority of the CPE association; The time intervals corresponding to the multiple CPEs; Whether the CPE is the CPE corresponding to the reserved resource information.
13. The method according to claim 12, characterized in that The first configuration information is further used to indicate configuration parameters of the one or more CPE groups, where the configuration parameters of the one or more CPE groups include one or more of the following: The time domain resource where the CPE group is located; The time domain position corresponding to the CPE group; One or more starting time domain positions corresponding to the CPE group; A time domain position corresponding to each CPE in the CPE group; one or more first time intervals for the CPE group; The identification ID information of the CPE group.
14. The method according to claim 13, characterized in that The configuration parameters of the one or more CPE groups include multiple starting time domain positions corresponding to the CPE group, multiple first time intervals corresponding to the CPE, and the multiple starting time domain positions include multiple starting time domain positions determined by the CPE group based on the multiple first time intervals.
15. The method according to any one of claims 1 to 14, characterized in that The first shared resource is shared by the first terminal device, and the method further includes: The first terminal device predefines / preconfigures the first CPE or the first CPE group corresponding to the reserved resource information based on the resource reservation information.
16. The method according to claim 15, characterized in that The reserved resource information is used for the second terminal device to send a side channel. If the resource reservation information is available, the time domain position of the first CPE or any one CPE in the first CPE group is used for the second terminal device to perform channel access; If the resource reservation information is not available, the CPE for the second terminal device to access the channel is determined based on the priority of the side channel.
17. The method according to any one of claims 1 to 16, characterized in that The first configuration information is used by the first terminal device to semi-statically configure the one or more CPEs, and the semi-static configuration is used to instruct the second terminal device to determine the CPE for channel access based on one or more of the following information: random access, hash function, service characteristics of the second terminal device, and priority corresponding to the second terminal device.
18. A device for sideline communication, characterized in that: The apparatus is a first terminal device, and the first terminal device includes: A determining unit, configured to determine first configuration information of a first shared resource, wherein the first configuration information is used to indicate one or more access point extension CPEs corresponding to the first shared resource; The one or more CPEs are determined based on the subcarrier spacing corresponding to the first shared resource, and the one or more CPEs are used by the second terminal device to determine the time domain position for accessing the first shared resource.
19. The device according to claim 18, characterized in that The first configuration information is further used to indicate the time domain resources where the one or more CPEs are located, and the one or more time domain locations corresponding to the one or more CPEs are determined according to a first time interval, and the first time interval is one of the following time intervals: a time interval between a first CPE of the one or more CPEs and a starting position of the time domain resource; A time interval between two adjacent CPEs among the one or more CPEs; The time interval used to determine the time domain location of the one or more CPEs.
20. The device according to claim 19, characterized in that The time length of the first time interval includes one or more of the following: 9 microseconds, 16 microseconds, and 25 microseconds.
21. [Corrected 31.05.2023 in accordance with Rule 91] A device according to claim 19 or 20, characterized in that The time domain position of any one of the one or more CPEs satisfies the following conditions: sym +δT}; Among them, the T sym is the starting position of the time domain resource, the δT is a second time interval between any one of the CPEs and the starting position of the time domain resource, and the second time interval includes one or more of the first time intervals.
22. The device according to any one of claims 18 to 21, characterized in that The time domain resources where the one or more CPEs are located are determined according to one or more of the following information: Subcarrier spacing; a duration of the first shared resource; Whether the first shared resource has a reserved resource.
23. The device according to claim 22, characterized in that The time domain resource where the one or more CPEs are located includes 1 symbol or 2 consecutive symbols.
24. The device according to any one of claims 18 to 23, characterized in that The first shared resource is used by the second terminal device to send a side channel, and the priorities associated with the one or more CPEs are used by the second terminal device to determine a CPE for channel access, where the priorities include one or more of the following: The service priority corresponding to the side channel; The channel access priority level CAPC corresponding to the side channel.
25. The device according to any one of claims 18 to 24, characterized in that The first configuration information is used to indicate M CPEs, and the M CPEs are used for N terminal devices to perform channel access in a first time period, where M and N are both natural numbers greater than 0. If N>M, the terminal devices among the N terminal devices that access the first shared resource through the M CPEs are determined according to one or more of the following information: The time period during which the N terminal devices wait for access; The earliest time when the N terminal devices initiate access requests; The service priorities corresponding to the data to be transmitted by the N terminal devices.
26. The device according to claim 25, characterized in that The first shared resource is shared by the first terminal device, the time period during which the N terminal devices wait for access is related to the duration of a timer started by the first terminal device, and the apparatus further includes: A starting unit is used to start a timer in response to an access request of a terminal device that accesses the channel earliest among the N terminal devices, and the timer is used by the first terminal device to determine the value of N.
27. The device according to claim 25 or 26, characterized in that When N>M, the first parameter of the terminal device among the N terminal devices that accesses the first shared resource through the M CPEs satisfies the following conditions: Among them, α and β represent weight factors, t i represents the time period between the time point when the i-th terminal device among the N terminal devices initiates an access request and the time point when the earliest access request is initiated, i is a natural number from 0 to N-1, T represents the first time period, Q i represents the service priority corresponding to the data to be transmitted by the i-th terminal device among the N terminal devices, Q i It is a natural number from 1 to K, K>1, and K represents the lowest priority.
28. The device according to any one of claims 18 to 27, characterized in that The first configuration information is sent through a shared spectrum. The first configuration information is carried in a first side channel. The first side channel includes first-stage side control information SCI and second-stage SCI. The first configuration information is carried in the first-stage SCI and / or the second-stage SCI.
29. The device according to any one of claims 18 to 28, characterized in that The first configuration information is further used to indicate one or more CPE groups to which the multiple CPEs belong, and the one or more CPE groups are determined according to one or more of the following information: The priority of the CPE association; The time intervals corresponding to the multiple CPEs; Whether the CPE is the CPE corresponding to the reserved resource information.
30. The device according to claim 29, characterized in that The first configuration information is further used to indicate configuration parameters of the one or more CPE groups, where the configuration parameters of the one or more CPE groups include one or more of the following: The time domain resource where the CPE group is located; The time domain position corresponding to the CPE group; One or more starting time domain positions corresponding to the CPE group; A time domain position corresponding to each CPE in the CPE group; one or more first time intervals for the CPE group; The identification ID information of the CPE group.
31. The device according to claim 30, characterized in that The configuration parameters of the one or more CPE groups include multiple starting time domain positions corresponding to the CPE group, multiple first time intervals corresponding to the CPE, and the multiple starting time domain positions include multiple starting time domain positions determined by the CPE group based on the multiple first time intervals.
32. The device according to any one of claims 18 to 31, characterized in that The first shared resource is shared by the first terminal device, and the apparatus further includes: A configuration unit is used to predefine / preconfigure a first CPE or a first CPE group corresponding to the reserved resource information according to the resource reservation information.
33. The device according to claim 32, characterized in that The reserved resource information is used for the second terminal device to send a side channel. If the resource reservation information is available, the time domain position of the first CPE or any one CPE in the first CPE group is used for the second terminal device to perform channel access; If the resource reservation information is not available, the CPE for the second terminal device to access the channel is determined based on the priority of the side channel.
34. The device according to any one of claims 18 to 33, characterized in that The first configuration information is used by the first terminal device to semi-statically configure the one or more CPEs, and the semi-static configuration is used to instruct the second terminal device to determine the CPE for channel access based on one or more of the following methods: random access, hash function, service characteristics of the second terminal device, and priority corresponding to the second terminal device.
35. A communication device, characterized in that: The invention 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 to execute the method according to any one of claims 1 to 17.
36. A device, characterized in that The invention comprises a processor, which is used to call a program from a memory to execute the method according to any one of claims 1 to 17.
37. A chip, characterized in that: It comprises a processor, which is used to call a program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 17.
38. A computer-readable storage medium, characterized in that: A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 17.
39. A computer program product, characterized in that The method comprises a program which causes a computer to execute the method according to any one of claims 1 to 17.
40. A computer program, characterized in that The computer program enables a computer to execute the method according to any one of claims 1 to 17.
Citation Information
Patent Citations
Method and device for sending cyclic prefix extension CPE
CN115299019A
Lateral communication method and device
CN115589596A
