WO2023092507A1 - Procédé et appareil de communication de liaison latérale - Google Patents

Procédé et appareil de communication de liaison latérale Download PDF

Info

Publication number
WO2023092507A1
WO2023092507A1 PCT/CN2021/133730 CN2021133730W WO2023092507A1 WO 2023092507 A1 WO2023092507 A1 WO 2023092507A1 CN 2021133730 W CN2021133730 W CN 2021133730W WO 2023092507 A1 WO2023092507 A1 WO 2023092507A1
Authority
WO
WIPO (PCT)
Prior art keywords
bwp
terminal device
information
message
data
Prior art date
Application number
PCT/CN2021/133730
Other languages
English (en)
Chinese (zh)
Inventor
张博源
赵振山
卢前溪
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2021/133730 priority Critical patent/WO2023092507A1/fr
Priority to CN202180101716.9A priority patent/CN117837205A/zh
Publication of WO2023092507A1 publication Critical patent/WO2023092507A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters

Definitions

  • the present application relates to communication technologies, and in particular to a side link communication method and device.
  • Sidelink (sidelink, SL) communication is different from the way in which communication data is received or sent by a base station in a traditional cellular system, and devices can communicate directly with each other.
  • Network devices often need to configure corresponding transmission resources for terminal devices on the side link.
  • different terminal devices have different service requirements. For example, some terminal devices have power-saving requirements, and some terminal devices have high service throughput requirements. Therefore, configuring a single BWP cannot meet the requirements of different terminal devices. need.
  • Embodiments of the present application provide a side link communication method and device to meet different requirements of different terminal devices.
  • the embodiment of the present application provides a side link communication method, including:
  • the first terminal device determines the first BWP among the multiple BWPs according to the first data and/or BWP configuration information
  • the first terminal device sends the first data to the second terminal device through the first BWP.
  • the embodiment of the present application provides a side link communication method, including:
  • the second terminal device negotiates a first BWP with the first terminal device, where the first BWP is determined by the first terminal device among multiple BWPs according to the first data and/or BWP configuration information;
  • the second terminal device receives the first data sent by the first terminal device through the first BWP.
  • the embodiment of the present application provides a sidelink communication device, including:
  • a processing module configured for the first terminal device to determine the first BWP among the multiple BWPs according to the first data and/or BWP configuration information
  • a sending module configured for the first terminal device to send the first data to a second terminal device through the first BWP.
  • the embodiment of the present application provides a sidelink communication device, including:
  • a processing module configured for the second terminal device to negotiate a first BWP with the first terminal device, wherein the first BWP is determined among multiple BWPs by the first terminal device according to the first data and/or BWP configuration information ;
  • a sending module configured to, if the negotiation on the first BWP is successful, the second terminal device receives the first data sent by the first terminal device through the first BWP.
  • the embodiment of the present application provides a terminal device, including: a transceiver, a processor, and a memory;
  • the memory stores computer-executable instructions
  • the processor executes the computer-executable instructions stored in the memory, so that the processor executes the side-link communication method described in the first aspect above.
  • the embodiment of the present application provides a terminal device, including: a transceiver, a processor, and a memory;
  • the memory stores computer-executable instructions
  • the processor executes the computer-executable instructions stored in the memory, so that the processor executes the side-link communication method as described in the second aspect above.
  • the embodiment of the present application provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are used to implement the above first aspect or The side link communication method as described in the second aspect above.
  • the embodiment of the present application provides a computer program product, including a computer program, characterized in that, when the computer program is executed by a processor, the side link communication method as described in the first aspect above or in the second aspect above is implemented .
  • Embodiments of the present application provide a side link communication method and apparatus, and the method includes: a first terminal device determines a first BWP among the multiple BWPs according to first data and/or BWP configuration information.
  • the first terminal device sends the first data to the second terminal device through the first BWP.
  • configure the BWP configuration information through the network device so the first terminal device may need to transmit the first data and/or BWP configuration information, and select a BWP to use among multiple BWPs, so as to effectively ensure that the configured multiple BWPs can meet different service requirements of the terminal device.
  • FIG. 1 is a schematic diagram of the types of V2X applications provided by the embodiment of the present application.
  • FIG. 2 is a schematic diagram of a V2X communication scenario provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of another V2X communication scenario provided by the embodiment of the present application.
  • FIG. 4 is a schematic diagram of implementation of data packet copy transmission provided by the embodiment of the present application.
  • FIG. 5 is a schematic diagram of the BWP provided by the embodiment of the present application.
  • FIG. 6 is a flow chart of a side link communication method provided by an embodiment of the present application.
  • FIG. 7 is a first schematic diagram of the implementation of BWP configuration information provided by the embodiment of the present application.
  • FIG. 8 is a second schematic diagram of the implementation of BWP configuration information provided by the embodiment of the present application.
  • FIG. 9 is a third schematic diagram of the implementation of BWP configuration information provided by the embodiment of the present application.
  • FIG. 10 is a schematic diagram 4 of realizing BWP configuration information provided by the embodiment of the present application.
  • FIG. 11 is a schematic diagram five of the implementation of the BWP configuration information provided by the embodiment of the present application.
  • FIG. 12 is a signaling interaction diagram of the side link communication method provided by the embodiment of the present application.
  • FIG. 13 is a first implementation schematic diagram of determining a negotiation result by a second terminal device provided in an embodiment of the present application
  • FIG. 14 is a second implementation schematic diagram of determining a negotiation result by a second terminal device provided in an embodiment of the present application.
  • FIG. 15 is a first structural schematic diagram of a sidelink communication device provided by an embodiment of the present application.
  • FIG. 16 is a second structural schematic diagram of a sidelink communication device provided by an embodiment of the present application.
  • FIG. 17 is a first structural schematic diagram of a terminal device provided by an embodiment of the present application.
  • FIG. 18 is a second schematic structural diagram of a terminal device provided by an embodiment of the present application.
  • Terminal device It is a device with wireless transceiver function. Terminal equipment can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as on aircraft, balloons and satellites, etc.).
  • the terminal device may be a mobile phone, a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, referred to as VR) terminal device, an augmented reality (augmented reality, referred to as AR) terminal device, an industrial Wireless terminals in industrial control, vehicle terminal equipment, wireless terminals in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid, Wireless terminal devices in transportation safety, wireless terminal devices in smart city, wireless terminal devices in smart home, wearable terminal devices, etc.
  • VR virtual reality
  • AR augmented reality terminal device
  • the terminal equipment involved in the embodiments of the present application may also be referred to as terminal, user equipment (UE), access terminal equipment, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station , remote terminal equipment, mobile equipment, UE terminal equipment, wireless communication equipment, UE agent or UE device, etc.
  • Terminal equipment can also be fixed or mobile.
  • Network device It is a device with wireless transceiver function. Including but not limited to: evolved base station (Evolutional Node B, eNB or eNodeB) in long term evolution (long term evolution, LTE), base station (gNodeB or gNB) or transceiver point ( transmission receiving point/transmission reception point, TRP), the base station in the subsequent evolution system, the access node in the wireless fidelity (Wireless Fidelity, WiFi) system, the wireless relay node, the wireless backhaul node, etc.
  • the base station can be: a macro base station, a micro base station, a pico base station, a small station, a relay station, or a balloon station, etc.
  • Multiple base stations may support the aforementioned networks of the same technology, or may support the aforementioned networks of different technologies.
  • a base station may contain one or more co-sited or non-co-sited TRPs.
  • the network device may also be a wireless controller, a centralized unit (centralized unit, CU), and/or a distributed unit (distributed unit, DU) in a cloud radio access network (cloud radio access network, CRAN) scenario.
  • the network device can also be a server, a wearable device, or a vehicle-mounted device, etc.
  • a network device is used as an example for description.
  • the multiple network devices may be base stations of the same type, or base stations of different types.
  • the base station can communicate with the terminal, and can also communicate with the terminal through a relay station.
  • the terminal can communicate with multiple base stations of different technologies.
  • the terminal can communicate with the base station supporting the LTE network, and can also communicate with the base station supporting the 5G network. It can also support dual connection with the base station of the LTE network and the base station of the 5G network , It can also support dual connection with the base station of the 5G network, etc.
  • Sideline defines a direct communication link between terminal devices as a sideline, which may also be called a direct link.
  • the wireless interface corresponding to the direct link on the terminal device is called a direct communication interface, also called an SL (Sidelink, direct communication) interface.
  • the communication link between the network device and the terminal device is called Uu link (cellular communication link), and the wireless interface corresponding to the cellular communication link on the terminal device is called Uu interface.
  • Side link (sideline, SL) communication refers to communication between terminal devices.
  • a link between terminal devices is called a secondary link.
  • the side link may also be called a device-to-device (device-to-device, D2D) link, a side link, a side link, etc., which is not limited in this application.
  • the technical solution of the embodiment of the present application can be applied to various communication systems, for example: long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex) , TDD), the fifth generation (5th generation, 5G) communication system, the future communication system (such as the sixth generation (6th generation, 6G) communication system), or a system where multiple communication systems are integrated, etc., the embodiments of the present application do not Do limited.
  • 5G can also be called new radio (new radio, NR).
  • mMTC may include one or more of the following communications: communications in industrial wireless sensor or network (IWSN), communications in video surveillance (video surveillance) scenarios, and communications in wearable devices wait.
  • IWSN industrial wireless sensor or network
  • video surveillance video surveillance
  • wearable devices wait.
  • LTE may be configured to support Device to Device (D2D) communication, Vehicle to Vehicle (V2V) communication and/or Vehicle to Everything (V2V) using Proximity based Service (ProSe). X, V2X) communication.
  • D2D Device to Device
  • V2V Vehicle to Vehicle
  • V2V Vehicle to Everything
  • Proximity based Service ProSe
  • X, V2X Proximity based Service
  • V2X vehicle to everything (Vehicle to X, V2X) communication is a key technical direction of the protocol version 16 (Release 16, R16), and NR V2X, as an enhancement of Long Term Evolution (LTE) V2X, is an enabling vehicle
  • LTE Long Term Evolution
  • V2X can be introduced in conjunction with FIG. 1 , which is a schematic diagram of types of V2X applications provided by the embodiment of the present application.
  • V2X application of V2X in this application can include the following four different types:
  • V2V Vehicle to Vehicle
  • V2I Vehicle to Infrastructure
  • V2N Vehicle to Network
  • V2P Vehicle to Pedestrian
  • V2X communication may include vehicles configured to communicate with Vehicle-to-Infrastructure/Network (V2I/N) (e.g., Vehicle-to-Pedestrian (V2P), Pedestrian-to-Vehicle (P2V), Road Side Unit (RSU) ) interface connected devices.
  • V2I/N Vehicle-to-Infrastructure/Network
  • V2P Vehicle-to-Pedestrian
  • P2V Pedestrian-to-Vehicle
  • RSU Road Side Unit
  • side link communication is performed between V2X devices through a side link (side link), where the side link may also be referred to as a side link, a secondary link, a side link, and a side link.
  • side link may also be referred to as a side link, a secondary link, a side link, and a side link.
  • the vehicle networking system adopts a terminal-to-terminal direct communication method. Therefore, it has higher spectral efficiency and lower transmission delay.
  • FIG. 1 A schematic diagram of a V2X communication scenario
  • FIG. 3 is a schematic diagram of another V2X communication scenario provided by an embodiment of the present application.
  • a network device 201 a terminal device 202 and a terminal device 203 are included in FIG. 2 .
  • the link between the terminal device 202 and the terminal device 203 is a side link, and the side link has been described in detail in the foregoing embodiments, and will not be repeated here.
  • the link between the terminal device 202 and the network device 201, and the link between the terminal device 203 and the network device 201 is a Uu air interface link, wherein the Uu air interface can be understood as a universal interface between the UE and the network (universal UE to network interface), Uu air interface communication refers to the communication between terminal equipment and network equipment.
  • the situation shown in FIG. 2 is the mode 1 described above.
  • the transmission resource of the terminal device in mode 1 is allocated by the network device.
  • the network device can use the downlink (Downlink, DL) shown in FIG. 2 as End devices allocate resources.
  • the terminal device sends data on the side link according to the resources allocated by the network device; the network device can allocate resources for a single transmission to the terminal device, or allocate resources for semi-static transmission to the terminal device.
  • FIG. 3 which includes a network device 301 , a terminal device 302 and a terminal device 303 . Its implementation is similar to that described above in FIG. 2 , and will not be repeated here.
  • the situation shown in FIG. 3 is the mode 2 introduced above. Specifically, in the mode 2, the terminal device can select a resource from the resource pool for data transmission.
  • D2D research process is described below.
  • D2D is divided into different stages for research.
  • ProSe D2D communication in Rel-12/13 is researched on the ProSe scenario, which is mainly aimed at public security services.
  • the resource pool is discontinuous in the time domain, so that the UE can discontinuously send/receive data on the side link, thereby achieving the effect of power saving.
  • V2X Vehicle-to-vehicle
  • V2X because the vehicle system has continuous power supply, power efficiency is not the main issue, but the delay of data transmission is the main issue, so the system design requires the terminal equipment to perform continuous transmission and reception.
  • Wearable devices In Rel-14, this scenario studies the scenario where wearable devices access the network through mobile phones, and it is mainly oriented to scenarios with low mobile speed and low power access.
  • the 3GPP conclusion in the pre-research stage is that the base station can configure the Discontinuous Reception (DRX) parameters of the remote (remote) terminal through a relay (relay) terminal, but since this subject has not further entered the standardization stage, The exact details of how the DRX configuration is done are inconclusive.
  • DRX Discontinuous Reception
  • Multi-carrier In Rel-15LTE V2X, a multi-carrier mechanism is introduced. Specifically, the multi-carrier mechanism is reflected in that the UE can support data packet segmentation and use multiple carriers to transmit data packets to improve the data transmission rate; and multi-carrier The mechanism supports data packet duplication, duplicating the same data packet twice and sending them on two carriers to improve transmission reliability; it also supports multi-carrier reception enhancement at the receiving end.
  • V2X side chain communication supports side chain packet replication, and is executed at the Packet Data Convergence Protocol (PDCP) layer of the UE.
  • PDCP Packet Data Convergence Protocol
  • the PDCP PDU Protocol Data Unit, Protocol Data Unit
  • the PDCP entity is replicated at the PDCP entity.
  • FIG. 4 is a schematic diagram of implementation of data packet copy transmission provided by the embodiment of the present application.
  • duplicate PDCP PDUs of the same PDCP entity are submitted to two different Radio Link Control (Radio Link Control, RLC) entities, such as RLC1 and RLC2 shown in Figure 4, and for the duplicate PDCP PDUs respectively Associated to two different sidechain logical channels.
  • RLC Radio Link Control
  • the duplicated duplicated PDCP PDUs of the same PDCP entity are only allowed to be transmitted on different side chain carriers.
  • the UE may activate or deactivate sidechain packet replication based on (pre)configuration.
  • the ProSe Per-Packet Reliability (PPPR) value that supports sidechain packet replication can be (pre)configured via PPPR thresholds.
  • the UE shall perform side chain packet replication for data configured with PPPR values until the packet replication configuration is canceled for these data configured with PPPR values.
  • the UE can report the amount of data associated with one or more PPPR values and the destination to which the data belongs through a sidechain buffer status report (Buffer Status Report, BSR).
  • BSR Sidechain buffer status report
  • the mapping of the PPPR value to the logical channel group can be configured by the eNB, and the PPPR value is reflected by the associated logical channel group ID included in the side chain BSR.
  • a list of one or more PPPR values may be reported by a Radio Resource Control (RRC) connected UE in Sidechain UE Information.
  • RRC Radio Resource Control
  • NR V2X is not limited to broadcast scenarios, but has been further expanded to unicast and multicast scenarios, and the application of V2X is studied in these scenarios.
  • NR V2X will also define the above mode-1/2 two resource authorization modes; further, the terminal device may be in a mixed mode, that is to say, it can use mode-1 for resource acquisition, At the same time, mode-2 can be used to obtain resources.
  • the resource acquisition is indicated by means of a sidelink grant, that is, the sidelink grant indicates the time-frequency positions of corresponding PSCCH and PSSCH resources.
  • NR V2X in addition to HARQ retransmission initiated by UE without feedback, NR V2X also introduces feedback-based HARQ retransmission, which is not limited to unicast communication, but also includes multicast communication;
  • the gNB works in dynamic or semi-static channel access mode. In both channel access modes, the gNB and UE can apply listen before talk (LBT) before performing transmissions on cells configured with shared spectrum channel access.
  • LBT listen before talk
  • the transmitter listens/senses the channel to determine whether the channel is free or busy, and only performs transmission when the channel is sensed to be free.
  • the UE can detect an uplink LBT failure, and the detection is based on each bandwidth part (BWP) and based on all uplink transmissions within the BWP.
  • BWP bandwidth part
  • both the system bandwidth and the terminal bandwidth may reach hundreds of MHz or even several GHz to support high-speed mobile data transmission, but this is not always required in actual data transmission.
  • Large bandwidth for example, in a working scenario that only needs to support low data rate transmission (such as WeChat chat), the terminal device only needs to use a small working bandwidth, for example, a bandwidth of 10MHz is sufficient.
  • the bandwidth part may be a part of the system bandwidth (cell carrier bandwidth).
  • the system bandwidth is 100 MHz
  • the terminal equipment may use a bandwidth less than 100 MHz.
  • the bandwidth part of 20 MHz or 50 MHz may be used for data transmission within the system bandwidth.
  • the bandwidth part can also be called “carrier bandwidth part”, also can be called “operating bandwidth (operating bandwidth), or transmission bandwidth, and the name and abbreviation of the bandwidth part are not particularly limited in the embodiment of the present application.
  • the network device can enable the terminal device to switch between multiple BWPs according to the service requirements of the terminal device. ; When the terminal device transmits at a relatively small service data rate, it can use a BWP with a relatively small bandwidth.
  • FIG. 5 is a schematic diagram of the BWP provided in the embodiment of the present application.
  • the network device can configure a large bandwidth (BWP1) for the terminal device, and it can be assumed that the frequency range of BWP1 is 15KHz to 40MKz;
  • BWP2 a small bandwidth
  • the frequency range of BWP2 is 15KHz ⁇ 10MKz, as long as BWP2 can meet the basic requirements of the terminal equipment. communication needs;
  • the network device finds that there is a wide range of frequency selective fading in the bandwidth where BWP1 is located, or that the resources in the frequency range where BWP1 is located are relatively scarce, at this time the network device can configure a new bandwidth (BWP3) for the terminal device, It can be assumed that the frequency range of BWP3 is 60KHz ⁇ 20MKz.
  • the UE can detect an uplink LBT failure based on each BWP and based on all uplink transmissions in each BWP.
  • the UE when a consistent uplink LBT failure is detected on a secondary cell (Secondary Cell, SCell), the UE transmits the LBT failure via MAC CE on a serving cell different from the SCell where the failure is detected
  • the fault is reported to the corresponding gNB, where the master node (MN) is used for the master cell group (Master Cell group, MCG), and the secondary node (Secondary node, SN) is used for the secondary cell group (Secondary Cell group, SCG)) .
  • the UE may transmit a Scheduling Request (SR).
  • SR Scheduling Request
  • the UE when a consistent uplink LBT failure is detected on the SpCell, the UE switches to another uplink configured with random access channel (Random Access Channel, RACH) resources on the cell Link (Uplink, UL) BWP, initiates RACH, and reports failure through MAC CE.
  • RACH Random Access Channel
  • UL BWP When multiple UL BWPs are available for exchange, it is up to the UE implementation to choose which one.
  • SpCell special Cell
  • PCell Primary Cell
  • Primary Secondary Cell, PSCell Primary Secondary Cell
  • the UE if a consistent uplink LBT failure is detected on all UL BWPs configured with RACH resources, the UE declares SCG radio link failure (radio link failure, RLF), And report failure to MN through SCG FailureInformation (configuration failure).
  • RLF radio link failure
  • the UE if an uplink LBT failure is detected on all UL BWPs with configured RACH resources, the UE declares RLF.
  • this application proposes the following technical idea: the network device configures multiple BWPs for the terminal equipment of the side link, so as to effectively meet the needs of different terminal equipment, and this application aims to solve the problem of direct link How to select one or more configured BWPs for the terminal device of the direct link in communication.
  • FIG. 6 is a flowchart of a side link communication method provided by an embodiment of the present application.
  • the method includes:
  • the first terminal device determines a first BWP among multiple BWPs according to the first data and/or BWP configuration information.
  • the communication scenario may be, for example, that the first terminal device sends service data to the second terminal device.
  • the first data in this embodiment may be currently required by the first terminal device The data corresponding to the sent business.
  • the first terminal device in this embodiment may also determine BWP configuration information, where the BWP configuration information may include information corresponding to multiple BWPs, and the multiple BWPs may be configured by the network device for the terminal device, for example. , and the information corresponding to each BWP therein may also be configured for each BWP by the network device.
  • BWP configuration information may include information corresponding to multiple BWPs, and the multiple BWPs may be configured by the network device for the terminal device, for example.
  • the information corresponding to each BWP therein may also be configured for each BWP by the network device.
  • the BWP configuration information may include at least one of the following first information, for example:
  • QoS Quality of Service
  • the target address may include at least one of the following information, for example: the group identifier of the target device, the identifier of the target device, and the service type; wherein, the target device may be the device corresponding to the service that the current terminal device needs to send, That is to say, the current terminal device is to send service data to the target device.
  • the group ID of the target device can be understood as the group ID of the target device in a multicast scenario.
  • the service type therein can be, for example, making a phone call, sending a short message, etc., and this embodiment does not limit the specific realization of the specific service type.
  • the specific data format of the target address can be, for example, n-bit data, and the n bits can indicate, for example, the group ID of the target device, the ID of the target device, and the service type described above. at least one of the
  • the QoS flow identifier introduced above is used to indicate the QoS flow.
  • the QoS flow identifier can be any of the following: QoS flow identifier (QoS flow identifier), default priority (default priority), logical channel ( logical channel (LCH) priority.
  • the default priority is a parameter of the QoS flow, so the corresponding QoS flow can be indicated according to the default priority.
  • the LCH priority is a corresponding correspondence between the LCH priority and the QoS flow, so the corresponding QoS flow can also be indicated according to the LCH priority.
  • the specific implementation of the QoS flow identifier can be selected according to actual requirements, and this embodiment does not limit this, as long as the QoS flow identifier can uniquely identify each QoS flow.
  • the terminal device currently needs to determine the BWP used for the first data transmission among multiple BWPs.
  • the first terminal device can select from multiple BWPs according to the first data and/or BWP configuration information. A first BWP matching the current first data, where the first BWP is a BWP used for data transmission.
  • the first terminal device sends the first data to the second terminal device through the first BWP.
  • the first terminal device may send the first data corresponding to the service to be sent currently to the second device through the first BWP.
  • the second terminal device can receive the first data sent by the first terminal device through the first BWP.
  • the second terminal device can also send data to the first terminal device through the first BWP.
  • the first terminal device Therefore, the device can receive the data sent by the second terminal device through the first BWP. That is to say, the first terminal device and the second terminal device can perform data transmission on the determined first BWP.
  • the side link communication method provided by the embodiment of the present application includes: the first terminal device determines the first BWP among the multiple BWPs according to the first data and/or BWP configuration information.
  • the first terminal device sends the first data to the second terminal device through the first BWP.
  • configure the BWP configuration information through the network device so the first terminal device may need to transmit the first data
  • one BWP is selected for use among multiple BWPs, thereby effectively ensuring that the configured multiple BWPs can meet different service requirements of the terminal device.
  • FIG. 7 is a schematic diagram of the implementation of the BWP configuration information provided by the embodiment of the present application.
  • Figure 8 is a schematic diagram of the implementation of the BWP configuration information provided by the embodiment of the present application.
  • FIG. 10 is a schematic diagram 4 for realizing BWP configuration information provided by the embodiment of the present application
  • FIG. 11 is a schematic diagram 5 for realizing the BWP configuration information provided in the embodiment of the present application.
  • only the priority corresponding to each BWP may be included in the BWP configuration information, which can be understood with reference to FIG. 7 , for example.
  • the BWP configuration information includes BWP1, BWP2, BWP3, and BWP4, where the priority of BWP1 is priority 1, the priority of BWP2 is priority 3, the priority of BWP3 is priority 4, and the priority of BWP4 The priority is priority 2, and assume that the current priority order is priority 1>priority 2>priority 3>priority 4. Then it can be determined that the priority of BWP1 is the highest, and the priority of BWP3 is the lowest.
  • the first BWP may be a BWP with the highest priority among at least one second BWP, and the second BWP is a BWP in an available state among the multiple BWPs.
  • the first terminal device may determine a second BWP in an available state among multiple BWPs, and then select a BWP with the highest priority among the second BWPs to obtain the first BWP. It can also be understood that the first terminal device preferentially selects the BWP with the highest priority, and when the BWP with the highest priority is unavailable, the terminal device selects the BWP with the second highest priority, and so on.
  • the specific indication form of the priority can be selected and set according to actual requirements, which is not limited in this embodiment, as long as the indication of the priority can specifically distinguish the priorities of different BWPs.
  • the BWP configuration information may only include at least one target address corresponding to each BWP, which can be understood with reference to FIG. 8 , for example.
  • the BWP configuration information includes BWP1 and BWP2, wherein the target address corresponding to each BWP may exist in the form of a target address list, for example, referring to Figure 8, the target address corresponding to BWP1 includes target address 1, target Address 2 , target address 3 , target address 4 , and target addresses corresponding to BWP2 include target address 5 , target address 6 , target address 7 , and target address 8 .
  • the specific implementation of at least one target address corresponding to each BWP can be selected and set according to actual needs, wherein, for example, the target addresses corresponding to different BWPs may not overlap, or may also overlap. This is not limited.
  • the current first data may be sent by the first terminal device to the second terminal device, so the target address corresponding to the first data may include at least one of the following, for example: the second terminal The device identifier, the group identifier of the second terminal device, and the service type corresponding to the first data.
  • the target address corresponding to the first data is found among the target addresses corresponding to which BWP, and the BWP is determined as the first BWP. It can also be understood that when the first terminal device currently sends the first data to the target address, it can use the BWP corresponding to the current target address to send.
  • the target address corresponding to the current first data is target address 4, it can be determined that in the BWP configuration information shown in FIG. 8 , the target address list of BWP1 includes target address 4, then it can be Determine BWP1 as the first BWP.
  • the situation shown in FIG. 8 above is a situation where the target addresses corresponding to the various BWPs do not overlap. In this case, there is only one BWP corresponding to a specific target address. In other possible implementations, when the target addresses corresponding to each BWP overlap, then it is possible that a specific target address corresponds to multiple BWPs. In this case, for example, each BWP can be configured with its own corresponding After that, among multiple BWPs corresponding to a specific target address, select the BWP with the highest priority to determine the first BWP.
  • the BWP configuration information may only include at least one QoS flow identifier corresponding to each BWP in the multiple BWPs, which can be understood with reference to FIG. 9 , for example.
  • the BWP configuration information includes BWP1 and BWP2, where the QoS flow identifiers corresponding to each BWP may exist in the form of a QoS flow identifier list, for example, referring to Figure 9, the QoS flow identifiers corresponding to BWP1 include QoS flow ID 1, QoS flow ID 2, QoS flow ID 3, QoS flow ID 4, and QoS flow IDs corresponding to BWP2 include QoS flow ID 5, QoS flow ID 6, QoS flow ID 7, and QoS flow ID 8.
  • the specific implementation of at least one QoS flow identifier corresponding to each BWP can be selected and set according to actual needs, wherein the QoS flow identifiers corresponding to different BWPs may, for example, not overlap, or may overlap, this implementation Examples are not limited to this.
  • the QoS flow identifier corresponding to the first data exists in at least one QoS flow identifier corresponding to the first BWP.
  • the first terminal device when determining the first BWP at present, it is to check which QoS flow identifier corresponding to the BWP has the QoS flow identifier corresponding to the first data, and then determine the BWP as the first BWP. It can also be understood that when the first terminal device currently sends a specific QoS flow corresponding to a certain service, the first terminal device can use the corresponding BWP to send.
  • the QoS flow identifier corresponding to the current first data is QoS flow identifier 7
  • the QoS flow identifier list of BWP2 includes the QoS flow identifier 7
  • BWP2 may be determined as the first BWP.
  • the situation shown in FIG. 9 above is a situation where the QoS flow identifiers corresponding to each BWP do not overlap. In this case, there is only one BWP corresponding to a specific QoS flow identifier. In other possible implementations, when the QoS flow identifiers corresponding to each BWP overlap, then there may be a situation where a specific QoS flow identifier corresponds to multiple BWPs. In this case, for example, you can configure for each BWP After that, among the multiple BWPs corresponding to the specific QoS flow identifier, select the BWP with the highest priority to determine the first BWP.
  • the BWP configuration information may only include at least one geographical area identifier corresponding to each BWP among the multiple BWPs, which can be understood with reference to FIG. 10 , for example.
  • the BWP configuration information includes BWP1 and BWP2, where the geographic area identifiers corresponding to each BWP may exist in the form of a list of geographic area identifiers, for example, referring to Figure 10, the geographic area identifiers corresponding to BWP1 include geographic area 1. Geographical area 2, geographical area 3, and geographical area identifiers corresponding to BWP2 include geographical area 4, geographical area 5, geographical area 6, and geographical area 7.
  • the specific implementation of at least one geographic area identifier corresponding to each BWP can be selected and set according to actual needs, wherein the geographic area identifiers corresponding to different BWPs may not overlap, or may overlap, for example, this implementation Examples are not limited to this.
  • the at least one geographic area identifier corresponding to the first BWP includes the geographic area identifier of the geographic area where the first terminal device is located.
  • the BWP is determined as the first BWP based on the identification of the geographical area where the first terminal device is currently located in the geographical area identification corresponding to which BWP. It can also be understood that when the first terminal device moves to a certain geographic location area, the terminal device can use the corresponding BWP to send services.
  • BWP2 may be determined as the first BWP.
  • the above situation shown in FIG. 9 is a situation in which the geographical area identifiers corresponding to each BWP do not overlap, and in this case there is only one BWP corresponding to a specific geographical area identifier.
  • the geographical area identifiers corresponding to each BWP overlap, then there may be a situation where a specific geographical area identifier corresponds to multiple BWPs.
  • you can configure for each BWP After each corresponding priority, among the multiple BWPs corresponding to the specific geographical area identifier, select the BWP with the highest priority to determine the first BWP.
  • the BWP configuration information in this application may also include at least two types of the first information introduced above, where the at least two types of first information correspond to different priorities, and the The priority is the priority for each first information.
  • the BWP to be selected can be determined according to each first information, wherein the implementation of determining the BWP to be selected according to each first information is the same as the implementation of determining the first BWP introduced in Figures 7-9 above. Similarly, after each corresponding candidate BWP is determined according to each piece of first information.
  • the candidate BWPs determined according to each piece of first information are the same, it can be determined that the only candidate BWP is currently determined, and thus the candidate BWP can be determined as the first BWP.
  • the candidate BWPs determined according to each piece of first information are different, it is currently necessary to determine which candidate BWP is to be determined as the first BWP. Because in this embodiment, a corresponding priority is set for each first information, the candidate BWP determined by the first information with the highest priority may be determined as the first BWP.
  • the current implementation can be understood in conjunction with Figure 11.
  • Figure 11 it is assumed that the current BWP configuration information includes the four types of first information introduced above. The introduction is similar and will not be repeated here.
  • the target address corresponding to the current first data is the target address 5
  • the QoS flow identifier corresponding to the current first data is assumed to be the QoS flow identifier 5
  • the current geographic area where the current terminal device is located is the geographic area 5.
  • BWP2 will be selected when the candidate BWP is selected according to the priority
  • BWP2 will be selected when the candidate BWP is selected according to the target address
  • BWP2 will be selected when the candidate BWP is selected according to the QoS flow identifier
  • BWP2 will be selected when the candidate BWP is selected according to the geographical area, so in the current example, it can be determined that the candidate BWPs determined according to each first information are all the same, all of which are BWP2, so it can be determined that the first BWP is BWP2.
  • the target address corresponding to the current first data is target address 1
  • the QoS flow identifier corresponding to the current first data is assumed to be QoS flow identifier 5
  • the current geographical area where the current terminal device is located is geographic area 3.
  • BWP2 will be selected when the candidate BWP is selected according to the priority
  • BWP1 will be selected when the candidate BWP is selected according to the target address
  • BWP2 will be selected when the candidate BWP is selected according to the QoS flow identifier.
  • BWP1 when selecting the BWP to be selected according to the geographical area, BWP1 will be selected, so in the current example, it can be determined that the BWPs to be selected according to each first information are different, so the first information with the highest priority can be determined
  • the obtained candidate BWP is determined as the first BWP.
  • the priorities of each first information are as shown in FIG.
  • the priority of the QoS flow identification information is priority 3
  • the priority of the geographical area information of the BWP is priority 4
  • the current priority order is priority 1>priority 2>priority 3>priority 4. Then it can be determined that the priority information of the BWP is the highest, and the priority of the geographical area information of the BWP is the lowest.
  • the candidate BWP determined according to the priority information of the BWP may be determined as the first BWP, that is, it is determined that the first BWP is BWP2.
  • the specific indication form of the priority can be selected and set according to actual requirements, which is not limited in this embodiment, as long as the indication of the priority can specifically distinguish the priorities of different BWPs.
  • the above describes the possible implementation of determining the first BWP according to the first data and/or BWP configuration information. Further, after the first terminal device in this embodiment determines the first BWP, it also needs to report to the second BWP through the first BWP. The second terminal device sends the first data.
  • the first terminal device when sending the first data through the first BWP, the first terminal device needs to negotiate with the second terminal device on the first BWP, and after the first BWP negotiation is successful, the first Only the terminal device can send the first data to the second terminal device through the first BWP.
  • the negotiation here is mainly to determine whether the second terminal device determines whether the current first BWP can be used to transmit the first data.
  • the specific realization of the first BWP negotiation between the first terminal device and the second terminal device is as follows in conjunction with Fig. 12 to Fig. 14 Make an introduction.
  • Figure 12 is a signaling interaction diagram of the side link communication method provided by the embodiment of the present application
  • Figure 13 is a schematic diagram of the first implementation of the second terminal device determining the negotiation result provided by the embodiment of the present application
  • Figure 14 is provided by the embodiment of the present application The second implementation schematic diagram of determining the negotiation result by the second terminal device.
  • the negotiation process between the first terminal device and the second terminal device includes:
  • the first terminal device sends a first message to the second terminal device, where the first message is used to indicate the first BWP.
  • the first terminal device may send a first message to the second terminal device, where the first message is used to indicate the first BWP.
  • the first message may include BWP-related configuration information such as the bandwidth, time domain position, frequency domain position, and frequency point of the first BWP.
  • This embodiment does not limit the specific implementation of the first message, as long as the first message can It only needs to be used to indicate the first BWP, and the first message may include any configuration information of the first BWP.
  • the second terminal device receives the first message sent by the first terminal device.
  • the second terminal device may receive the first message sent by the first terminal device, so as to determine which BWP the first BWP currently selected by the first terminal device is.
  • the second terminal device determines the negotiation result of the first BWP.
  • the second terminal device may determine a negotiation result of the first BWP according to the indicated first BWP, where the negotiation result is used to indicate whether the current first BWP is acceptable.
  • the second terminal device may send a verification message to the network device request, wherein the verification request is used to request the network device to determine whether the first BWP is available, for example, the above-mentioned first message may be included in the verification request, that is, the relevant configuration information of the first BWP is sent to the network device, and then the network device Determine whether the current first BWP is acceptable, so as to send the negotiation result to the second terminal device. Therefore, when the second terminal device determines the negotiation result of the first BWP, it receives the negotiation result determined by the network device.
  • the negotiation result may indicate that the first BWP is available, or the negotiation result may also indicate that the first BWP is unavailable.
  • the connected state in this embodiment may specifically be the RRC connected state.
  • the second terminal device can determine by itself The result of the negotiation of the first BWP.
  • the second terminal device includes second BWP configuration information, where the second BWP configuration information is similar to the BWP configuration information introduced above, except that the above BWP configuration information is
  • the current second BWP configuration information is pre-configured in the second terminal device, which can be understood as being pre-configured when the second terminal device leaves the factory.
  • the multiple BWPs corresponding to the current second BWP configuration information may be the same as or different from the multiple BWPs configured by the above-mentioned network device. This embodiment does not limit this, and it can be selected and limited according to actual needs .
  • the second terminal device can determine the second BWP among the multiple BWPs according to the first message and the second BWP configuration information.
  • the first message in this embodiment may also include at least one of the following: the identifier of the first terminal device, the service type of the first data, the QoS corresponding to the first data, and the geographical area where the first terminal device is located logo.
  • the second BWP configuration information is similar to the BWP configuration information introduced above, and may include at least one of the following: a priority corresponding to each BWP in multiple BWPs; at least one target address corresponding to each BWP in multiple BWPs; At least one QoS flow identifier corresponding to each BWP in a BWP; at least one geographic area identifier corresponding to each BWP in a plurality of BWPs.
  • the second terminal device determines the second BWP according to the first message and the second BWP configuration information
  • its implementation is similar to the above-mentioned implementation of the first terminal device determining the first BWP.
  • the implementation of determining the second BWP may include at least one of the following: determining the second BWP according to the priority corresponding to the BWP, determining the target address according to the identity of the first terminal device and the service type of the first data, and then determining the target address according to the priority of the target The address determines the second BWP, and the QoS corresponding to the first data determines the second BWP, and determines the second BWP according to the geographical area identifier where the first terminal device is located.
  • various possible implementations of determining the second BWP are the same as the above introduction
  • the implementation manner of determining the first BWP is similar and will not be repeated here.
  • the second terminal device determines the second BWP according to the preconfigured second BWP configuration information, for example, it can determine whether the first BWP and the second BWP are the same, if they are the same, it can determine that the negotiation result indicates that the first BWP is available, if they are not the same , it may be determined that the negotiation result indicates that the first BWP is unavailable.
  • the second terminal device determines that the response message is a confirmation message, and the confirmation message is used to indicate that the negotiation of the first BWP is successful.
  • the second terminal device may determine that the response message is an acknowledgment message, where the acknowledgment message is used to indicate that the negotiation on the first BWP is successful.
  • the confirmation message may be, for example, configuration completion (RRCReconfigurationSidelinkComplete).
  • the second terminal device may determine that the message is a failure message, where the failure message is used to indicate that the negotiation on the first BWP fails.
  • the failure message may be, for example, configuration failure (RRCReconfigurationSidelinkFailure).
  • the second terminal device sends a response message to the first terminal device.
  • the second terminal device may send the above-mentioned determined response message to the first terminal device, so as to inform the first terminal device whether the current negotiation of the first BWP is successful.
  • the first terminal device receives a response message corresponding to the first message sent by the second terminal device.
  • the first terminal device determines that the negotiation on the first BWP is successful.
  • the first terminal device can receive the response message sent by the second terminal device.
  • the response message is a confirmation message
  • the first terminal device can confirm that the negotiation on the first BWP is successful, and then send a message to the second terminal device through the first BWP.
  • the terminal device has sent the first data.
  • the first terminal device may confirm that the negotiation on the first BWP fails, and the first terminal device may, for example, feed back the failure message to the network device, and the network device performs subsequent processing.
  • the negotiation process described above it can be ensured that the first BWP determined by the first terminal device is also acceptable to the second terminal device, thereby ensuring correct transmission of subsequent first data.
  • the network device can configure a default (default) BWP for the terminal device, which is used to send a physical sidelink broadcast channel (Physical Sidelink Broadcast Channel, PSBCH) and a unicast link establishment process.
  • PSBCH Physical Sidelink Broadcast Channel
  • the negotiation process between the first terminal device and the second terminal device described above can be carried out on the default BWP.
  • the second terminal device accepts the first BWP determined by the first terminal device, it can be determined that the first terminal device and the second terminal device After the second terminal device successfully negotiates the first BWP, the first terminal device and the second terminal device need to switch to the negotiated first BWP to work.
  • the first terminal device and the second terminal device may first switch to the first BWP.
  • the switching timing can be different ways to implement the switching timing
  • the first terminal device may switch to the first BWP after receiving the confirmation message. Similar to the second terminal device, for example, it may switch to the second BWP after it is determined that the negotiation of the first BWP is successful.
  • the first terminal device may switch to the first BWP within a preset time period after receiving the confirmation message.
  • the first terminal device may also send handover instruction information to the second terminal device, where the handover instruction information may include the identifier of the first BWP, the handover instruction information Used to indicate switching to the first BWP. Then, for example, after the second terminal device receives the switching instruction information, the first terminal device and the second terminal device switch to the first BWP.
  • the handover instruction information therein can be, for example, MAC CE, and the handover instruction information can also include time information, for example, where the time information is used to indicate that the first BWP is used within the duration corresponding to the time information, and the time information can be as follows At least one of: timer, start time and end time, start time and duration, duration.
  • the first terminal device and the second terminal device need to renegotiate the BWP on the default BWP, for example.
  • one or more BWP ID fields may be included in the handover indication information MAC CE.
  • the switching process described above can ensure that the first terminal device and the second terminal device can be switched to work on the negotiated first BWP, thereby effectively ensuring the validity of the determined first BWP.
  • multiple BWPs are configured for the terminal device through the network device, so as to effectively meet different service requirements of the terminal device.
  • the first terminal device can determine the first BWP among multiple BWPs, and then negotiate with the second terminal device on the first BWP. After the negotiation is successful, the first terminal device and the second terminal device switch to the first BWP Carry out data transmission, so as to ensure that the terminal device can reasonably select one or more BWPs among multiple BWPs, and then carry out corresponding services with the peer terminal device according to actual needs, further ensuring the availability of multiple configured BWPs .
  • FIG. 15 is a first structural schematic diagram of a sidelink communication device provided by an embodiment of the present application.
  • the side link communication device 150 may include a receiving module 1501 and a sending module 1502, wherein,
  • a processing module 1501 configured for the first terminal device to determine a first BWP among multiple BWPs according to the first data and/or BWP configuration information;
  • a sending module 1502 configured for the first terminal device to send the first data to a second terminal device through the first BWP.
  • the BWP configuration information includes at least one of the following first information:
  • the BWP configuration information includes a priority corresponding to each BWP in the multiple BWPs;
  • the first BWP is a BWP with the highest priority among at least one second BWP
  • the second BWP is a BWP in an available state among the multiple BWPs.
  • the BWP configuration information includes at least one target address corresponding to each BWP in the multiple BWPs;
  • a target address corresponding to the first data exists in at least one target address corresponding to the first BWP.
  • the BWP configuration information includes at least one QoS flow identifier corresponding to each BWP in the multiple BWPs;
  • the QoS flow identifier corresponding to the first data exists in at least one QoS flow identifier corresponding to the first BWP.
  • the BWP configuration information includes at least one geographical area identifier corresponding to each BWP in the multiple BWPs;
  • the at least one geographic area identifier corresponding to the first BWP includes the geographic area identifier of the geographic area where the first terminal device is located.
  • the BWP configuration information includes at least two kinds of the first information, and at least two kinds of the first information correspond to different priorities;
  • the first BWP is the candidate BWP
  • the first BWP is: determined according to the first information with the highest priority among the at least two kinds of first information The obtained candidate BWP.
  • the sending module 1502 is specifically configured to:
  • the first terminal device negotiates the first BWP with the second terminal device
  • the first terminal device After successfully negotiating the first BWP, the first terminal device sends the first data to the second terminal device through the first BWP.
  • the sending module 1502 is specifically configured to:
  • the first terminal device sends a first message to the second terminal device, where the first message includes the identifier of the first BWP;
  • the response message is determined according to a negotiation result, and when the negotiation result indicates that the first BWP is available, the response message is a confirmation message;
  • the negotiation result is determined by the network device.
  • the negotiation result is determined by the second terminal device.
  • the first message further includes at least one of the following information:
  • processing module 1501 is further configured to:
  • the first terminal device Before the first terminal device sends the first data to the second terminal device through the first BWP, the first terminal device switches to the first BWP.
  • processing module 1501 is specifically configured to:
  • the first terminal device switches to the first BWP.
  • processing module 1501 is specifically configured to:
  • the first terminal device sends handover instruction information to the second terminal device, and switches to the first BWP, the handover instruction information includes an identifier of the first BWP, and the handover instruction information is used to indicate Switch to the first BWP.
  • the handover instruction information further includes time information, and the time information is used to indicate that the first BWP is used within a duration corresponding to the time information.
  • the time information is any of the following:
  • the handover instruction information is MAC CE.
  • the side link communication device provided in the embodiment of the present application can implement the technical solution shown in the above method embodiment, and its implementation principles and beneficial effects are similar, and details are not repeated here.
  • FIG. 16 is a second structural schematic diagram of a sidelink communication device provided by an embodiment of the present application.
  • the side link communication device 160 may include a processing module 1601 and a sending module 1602, wherein,
  • the processing module 1601 is configured to negotiate a first BWP between the second terminal device and the first terminal device, where the first BWP is the first BWP that the first terminal device uses in the multiple BWPs according to the first data and/or BWP configuration information. identified in
  • the sending module 1602 is configured to, if the negotiation on the first BWP is successful, the second terminal device receives the first data sent by the first terminal device through the first BWP.
  • processing module 1601 is specifically configured to:
  • the second terminal device generates a response message corresponding to the first message, and sends the response message to the first terminal device.
  • the first message further includes at least one of the following information:
  • An identifier of the first terminal device a service type of the first data, a QoS corresponding to the first data, and an identifier of a geographical area where the first terminal device is located.
  • processing module 1601 is specifically configured to:
  • the second terminal device determines the negotiation result of the first BWP
  • the second terminal device determines that the response message is an acknowledgment message, and the acknowledgment message is used to indicate that the negotiation on the first BWP is successful.
  • the second terminal device is located in a service area of the network device; the processing module 1601 is specifically configured to:
  • the second terminal device sends a verification request to the network device, where the verification request includes the first message
  • the second terminal device receives the negotiation result sent by the network device.
  • the processing module 1601 is further configured to:
  • the second terminal device is not located in the service area of the network device; the processing module 1601 is specifically configured to:
  • the second terminal device determines a second BWP among the multiple BWPs according to the first message and second BWP configuration information
  • the second BWP and the first BWP are the same BWP, determine that the first BWP is available as a result of the negotiation of the first BWP.
  • the second BWP configuration information includes at least one of the following:
  • processing module 1601 is further configured to:
  • the second terminal device Before the second terminal device receives the first data sent by the first terminal device through the first BWP, the second terminal device switches to the first BWP.
  • processing module 1601 is specifically configured to:
  • the second terminal device After successfully negotiating the first BWP, the second terminal device switches to the first BWP.
  • processing module 1601 is specifically configured to:
  • the second terminal device switches to the first BWP according to the switching instruction information.
  • the handover instruction information further includes time information, and the time information is used to indicate that the first BWP is used within a duration corresponding to the time information.
  • the time information is any of the following:
  • the handover instruction information is MAC CE.
  • the side link communication device provided in the embodiment of the present application can implement the technical solution shown in the above method embodiment, and its implementation principles and beneficial effects are similar, and details are not repeated here.
  • FIG. 17 is a first schematic structural diagram of a terminal device provided by an embodiment of the present application.
  • a terminal device 170 may include: a transceiver 21 , a memory 22 , and a processor 23 .
  • the transceiver 21 may include: a transmitter and/or a receiver.
  • the transmitter may also be referred to as a transmitter, a transmitter, a sending port, or a sending interface, and the like, and the receiver may also be called a receiver, a receiver, a receiving port, or a receiving interface, or similar descriptions.
  • the transceiver 21 , the memory 22 , and the processor 23 are connected to each other through a bus 24 .
  • the memory 22 is used to store program instructions
  • the processor 23 is configured to execute the program instructions stored in the memory, so as to enable the terminal device 120 to execute any one of the above-mentioned side link communication methods.
  • the receiver of the transceiver 21 can be used to perform the receiving function of the terminal device in the above-mentioned side link communication method.
  • FIG. 18 is a second schematic structural diagram of a terminal device provided by an embodiment of the present application.
  • the terminal device 180 may include: a transceiver 31 , a memory 32 , and a processor 33 .
  • the transceiver 31 may include: a transmitter and/or a receiver.
  • the transmitter may also be called a transmitter, a transmitter, a sending port, or a sending interface, and similar descriptions
  • the receiver may also be called a receiver, a receiver, a receiving port, or a receiving interface, or similar descriptions.
  • the transceiver 31 , the memory 32 , and the processor 33 are connected to each other through a bus 34 .
  • the memory 32 is used to store program instructions
  • the processor 33 is configured to execute the program instructions stored in the memory, so as to enable the terminal device 180 to execute any one of the above-mentioned side link communication methods.
  • the receiver of the transceiver 31 can be used to perform the receiving function of the terminal device in the above communication method.
  • An embodiment of the present application provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are used to implement the foregoing side link communication method.
  • An embodiment of the present application provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are used to implement the foregoing side link communication method.
  • An embodiment of the present application may further provide a computer program product, where the computer program product may be executed by a processor, and when the computer program product is executed, any one of the above-mentioned side link communication methods performed by the terminal device may be implemented.
  • the communication device, computer-readable storage medium, and computer program product in the embodiments of the present application can execute the side-link communication method executed by the above-mentioned terminal device.
  • the disclosed system, device and method can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.
  • the aforementioned computer program can be stored in a computer-readable storage medium.
  • the computer program When the computer program is executed by the processor, it implements the steps of the above-mentioned method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.

Landscapes

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

Abstract

Un procédé et un appareil de communication de liaison latérale sont divulgués dans les modes de réalisation de la présente demande. Le procédé comprend : la détermination, par un premier dispositif terminal, d'une première partie de largeur de bande, BWP, parmi plusieurs parties BWP selon des premières données et/ou des informations de configuration de parties BWP ; et l'envoi, par le premier dispositif terminal, des premières données à un second dispositif terminal au moyen de la première partie BWP. Une pluralité de parties BWP sont configurées pour un dispositif terminal sur une liaison latérale au moyen d'un dispositif de réseau de sorte que différentes exigences de service du dispositif terminal peuvent être efficacement satisfaites. De plus, des informations de configuration de partie BWP sont configurées au moyen du dispositif de réseau de sorte que le premier dispositif terminal peut sélectionner, parmi la pluralité de parties BWP, une partie BWP à utiliser selon des premières données et les informations de configuration de partie BWP, qui doivent être transmises. Par conséquent, il peut être efficacement garanti que la pluralité de parties BWP configurées peuvent satisfaire l'utilisation du dispositif terminal pour différentes exigences de service.
PCT/CN2021/133730 2021-11-26 2021-11-26 Procédé et appareil de communication de liaison latérale WO2023092507A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2021/133730 WO2023092507A1 (fr) 2021-11-26 2021-11-26 Procédé et appareil de communication de liaison latérale
CN202180101716.9A CN117837205A (zh) 2021-11-26 2021-11-26 侧链路通信方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/133730 WO2023092507A1 (fr) 2021-11-26 2021-11-26 Procédé et appareil de communication de liaison latérale

Publications (1)

Publication Number Publication Date
WO2023092507A1 true WO2023092507A1 (fr) 2023-06-01

Family

ID=86538707

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/133730 WO2023092507A1 (fr) 2021-11-26 2021-11-26 Procédé et appareil de communication de liaison latérale

Country Status (2)

Country Link
CN (1) CN117837205A (fr)
WO (1) WO2023092507A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110830952A (zh) * 2018-08-10 2020-02-21 中兴通讯股份有限公司 车联网中直通链路的资源配置方法及装置
CN111556536A (zh) * 2019-02-11 2020-08-18 华为技术有限公司 Bwp切换方法及通信装置
US20210051681A1 (en) * 2019-08-13 2021-02-18 Qualcomm Incorporated Channel state information report aggregation and uplink control information multiplexing for sidelink communications
CN112385297A (zh) * 2018-06-28 2021-02-19 康维达无线有限责任公司 用于nr v2x侧链路共享信道数据传输的优先化过程
CN113455077A (zh) * 2018-10-31 2021-09-28 弗劳恩霍夫应用研究促进协会 基于qos的侧链路资源池/bwp分配

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112385297A (zh) * 2018-06-28 2021-02-19 康维达无线有限责任公司 用于nr v2x侧链路共享信道数据传输的优先化过程
CN110830952A (zh) * 2018-08-10 2020-02-21 中兴通讯股份有限公司 车联网中直通链路的资源配置方法及装置
CN113455077A (zh) * 2018-10-31 2021-09-28 弗劳恩霍夫应用研究促进协会 基于qos的侧链路资源池/bwp分配
CN111556536A (zh) * 2019-02-11 2020-08-18 华为技术有限公司 Bwp切换方法及通信装置
US20210051681A1 (en) * 2019-08-13 2021-02-18 Qualcomm Incorporated Channel state information report aggregation and uplink control information multiplexing for sidelink communications

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
VIVO: "The UE behavior of deactivated sidelink BWP", 3GPP DRAFT; R2-2000284, vol. RAN WG2, 14 February 2020 (2020-02-14), pages 1 - 4, XP051848922 *

Also Published As

Publication number Publication date
CN117837205A (zh) 2024-04-05

Similar Documents

Publication Publication Date Title
US11706814B2 (en) Communications device, infrastructure equipment and methods
US11477703B2 (en) Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station
JP6846435B2 (ja) ウェアラブルデバイスをｌｔｅマスターｕｅと共にグループ化する手順
CN107667559B (zh) 在无线通信系统中使用不同的无线连接技术提供多连接的装置和方法
EP3050395B1 (fr) Équipement utilisateur et procédé de communication de dispositif à dispositif (d2d)
US20240334434A1 (en) Resource configuration for sidelink communication
EP2712253B1 (fr) Procédé, dispositif et système de communication à très large bande sans fil
US11356904B2 (en) Method and apparatus for performing handover in wireless communication system
US11700659B2 (en) Method and apparatus for performing user equipment capability procedure for supporting vehicle communication in next generation mobile communication system
CN108886748B (zh) 用于减少信令开销和减少终端电池的方法和设备
US20220295354A1 (en) Method and apparatus for performing handover in wireless communication system
CN108353317B (zh) 用于在移动通信系统中接收mac pdu的方法和装置
EP2863701B1 (fr) Réseau de communication, équipement d'utilisateur et procédé pour la transmission de signaux
CN113455086B (zh) 用于移动通信系统中通过两步随机接入过程传输用户数据的方法和装置
WO2023010257A1 (fr) Procédé et appareil de communication de liaison latérale, et dispositif et support de stockage
JP2023508827A (ja) 無線通信ネットワークにおけるサイドリンク通信のためのシステムおよび方法
KR20200088721A (ko) Dual Connectivity 지원 망에서 RRC_IDLE 상태 단말을 위한 SN(Secondary Node)에서의 V2X 자원 할당 방법 및 장치
WO2023092507A1 (fr) Procédé et appareil de communication de liaison latérale
CN117837093A (zh) 网络触发的聚合操作
CN117242813A (zh) 路径建立方法、选择方法、装置、终端设备及存储介质
KR20210019750A (ko) 무선통신 시스템에서 사이드링크 라디오 베어러를 구성하는 방법 및 장치
WO2023060404A1 (fr) Procédé et appareil de classement de priorité de canal logique, dispositif, et support de stockage
JP2020511853A (ja) 無線ベアラ方式を決定する方法および装置
WO2022032681A1 (fr) Procédé de transmission de données et appareil de communication
WO2023060499A1 (fr) Établissement de connexion et communications à double connectivité sur un réseau local sans fil

Legal Events

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

Ref document number: 21965240

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180101716.9

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE