WO2019096034A1 - 请求资源的方法及装置，处理资源请求的方法及装置 - Google Patents

请求资源的方法及装置，处理资源请求的方法及装置 Download PDF

Info

Publication number
WO2019096034A1
WO2019096034A1 PCT/CN2018/114225 CN2018114225W WO2019096034A1 WO 2019096034 A1 WO2019096034 A1 WO 2019096034A1 CN 2018114225 W CN2018114225 W CN 2018114225W WO 2019096034 A1 WO2019096034 A1 WO 2019096034A1
Authority
WO
WIPO (PCT)
Prior art keywords
communication node
logical channel
frequency point
frequency
data
Prior art date
Application number
PCT/CN2018/114225
Other languages
English (en)
French (fr)
Inventor
张博源
陈琳
黄莹
汪梦珍
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US16/764,645 priority Critical patent/US11647418B2/en
Priority to MX2020005158A priority patent/MX2020005158A/es
Publication of WO2019096034A1 publication Critical patent/WO2019096034A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/46—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for vehicle-to-vehicle communication [V2V]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of communications, and in particular, to a method and apparatus for requesting resources, and a method and apparatus for processing a resource request.
  • the so-called car network is that vehicles can participate in wireless communication, through the use of advanced wireless cellular communication technology, real-time information interaction between the car and the car, the car and the roadside infrastructure, to inform each other's current status (including the location of the vehicle) , speed, acceleration, driving route) and learned road environment information, collaboratively aware of road hazard conditions, timely provide a variety of collision warning information to prevent road traffic safety accidents.
  • V2V Vehicle-to-Vehicle Communications
  • V2I Vehicle-to-Infrastructure Communications
  • Vehicle-to Vehicle-to-Vehicle communication
  • V2X Vehicle-to-Everything
  • Direct discovery/communication based on user equipment (UE) to UE supports broadcast transmission of V2X messages through PC5 interface
  • UE user equipment
  • MBMS multicast/multicast single frequency network
  • D2D Device-to-Device
  • Proximity Services ProSe
  • SideLink Single-sided link
  • SL through link
  • Scheduled resource allocation also referred to as mode 3
  • RRC radio resource control
  • UE autonomous resource selection also referred to as mode 4
  • SCI sidechain control information
  • SCI Sidelink Control
  • Information data transmission.
  • This method can be used for idle state (IDLE state) or connected state (CONNECTED state) UE.
  • FIG. 1 is a serialization method according to the related art. The schematic diagram, as shown in the serialization mode of FIG.
  • the base station and the UE generate the same target index (Destination Index) for uniquely indicating the correspondence between the frequency point and the target ID.
  • the UE may request the resource of the corresponding frequency point from the base station by using a Buffer Status Report (BSR), and the BSR carries the target index, the logical channel group (LCG), and the buffer. Area size and other information.
  • BSR Buffer Status Report
  • the base station allocates the SL transmission resource at the corresponding frequency point to the UE according to the BSR request of the UE.
  • the R14V2X in order to facilitate the base station to allocate semi-persistent scheduling (SPS) resources to the UE, the R14V2X sends an SPS auxiliary message to the base station through the UE, including periodicity, offset, data size, and data packet priority (PPPP).
  • SPS semi-persistent scheduling
  • PPPP data packet priority
  • V2X traffic transmitted on a single carrier does not support the automatic repeat request (ARQ) feature.
  • hybrid automatic retransmission only supports Media Access Control (MAC) Protocol Data Unit (PDU) retransmissions for a specific number of configurations, and there is no message feedback for acknowledgment/non-acknowledgement messages (ACK/NACK). Therefore, the current data retransmission service of V2X on a single carrier adopts a time domain multiplexing method.
  • MAC Media Access Control
  • PDU Protocol Data Unit
  • the embodiments of the present invention provide a method and an apparatus for requesting resources, and a method and an apparatus for processing a resource request, so as to at least solve the problem that the terminal requests resources in the related art are inefficient.
  • a method for requesting a resource including: a first communication node acquires a buffer size corresponding to a same frequency point or an anchor frequency point in a logical channel group; and the first communication node sends a Sidelink BSR Up to the second communication node, wherein the Sidelink BSR comprises at least one of: a target index corresponding to the same frequency point or anchor frequency point; the logical channel group identifier or a logical channel identifier; the cache size.
  • a method for requesting a resource including: a first communication node acquiring a buffer size buffer size corresponding to one or more frequency points in a logical channel, wherein the logical channel uses one or And a plurality of frequency points; the Sidelink BSR is reported according to the target index corresponding to the one or more frequency points, wherein the BSR includes a buffer value size of the frequency channel in the logical channel.
  • a method for processing a resource request including: receiving, by the second communication node, a Sidelink BSR reported by the first communication node, where the Sidelink BSR includes at least one of the following information: a target index corresponding to one or more logical channels in the logical channel group, using the same frequency point or anchor frequency point; the logical channel group identifier or logical channel identifier; the buffer size of the same frequency point or anchor frequency point And allocating resources at the respective frequency points for the first communication node according to the Sidelink BSR.
  • an apparatus for requesting a resource further includes: a first acquiring module, configured to acquire a buffer size corresponding to a same frequency point or an anchor frequency point in a logical channel group; a module, configured to send a Sidelink BSR to a second communication node, where the Sidelink BSR includes at least one of: a target index corresponding to the same frequency point or anchor frequency point; the logical channel group identifier or a logical channel identifier ; the cache size.
  • an apparatus for requesting a resource comprising: a second obtaining module, configured to acquire a buffer size buffer size corresponding to one or more frequency points in a logical channel, wherein The logical channel uses one or more frequency points; the second sending module is configured to report the Sidelink BSR according to the target index corresponding to the one or more frequency points, wherein the Sidelink BSR includes the logical channel, and is used. The size of the cached value of this frequency.
  • an apparatus for processing a resource request including: a first receiving module, configured to receive a Sidelink BSR reported by a first communications node, where the Sidelink BSR includes at least the following information One: one or more logical channels in the logical channel group, a target index corresponding to the same frequency point or anchor frequency point used; the logical channel group identifier or logical channel identifier; the same frequency point or anchor point frequency point Cache size; an allocation module configured to allocate resources at the respective frequency points for the first communication node according to the Sidelink BSR.
  • a storage medium comprising a stored program, wherein the program is executed while performing the method described in any of the above alternative embodiments.
  • a processor for running a program wherein the program is executed to perform the method described in any of the above alternative embodiments.
  • the terminal acquires a buffer size buffer size corresponding to the same frequency point or anchor point frequency point in the logical channel group; the terminal sends a Sidelink BSR to the base station, wherein the Sidelink BSR includes at least one of the following: a target index corresponding to an anchor frequency point; the logical channel group identifier or a logical channel identifier; the cache size.
  • the terminal sends a Sidelink BSR carrying the above parameters to the base station to request the resource, and the base station allocates resources on the frequency point according to the foregoing parameters.
  • FIG. 1 is a schematic diagram of a serialization method according to the related art
  • FIG. 2 is a flow chart of a method of requesting a resource according to an embodiment of the present invention
  • FIG. 3 is a diagram showing the use of a single identical frequency resource for all logical channels in a logical channel group in accordance with a preferred embodiment of the present invention
  • FIG. 4 is a diagram showing the use of unique and mutually different frequency point resources for each logical channel in a logical channel group in accordance with a preferred embodiment of the present invention
  • FIG. 5 is a schematic diagram of different logical channels using the same set of frequency points in accordance with a preferred embodiment of the present invention.
  • FIG. 6 is a schematic diagram of different logical channels using different frequency point set resources according to a preferred embodiment of the present invention.
  • FIG. 7 is a schematic diagram of reporting a corresponding target ID in a V2X-DestinationInfoList corresponding to a frequency point according to a preferred embodiment of the present invention
  • FIG. 8 is a schematic diagram of reporting a target ID and a logical channel corresponding thereto, or a logical channel set, in a v2x-DestinationInfoList of different frequency points, in accordance with a preferred embodiment of the present invention.
  • the technical solution in the present application can be applied to a scenario using a PC5 interface, including but not limited to car networking communication.
  • the first communication node in the present application may be a terminal, and the second communication node may be a base station.
  • FIG. 2 is a flowchart of a method for requesting resources according to an embodiment of the present invention. As shown in FIG. 2, the process includes the following steps:
  • Step S202 the first communication node acquires a buffer size corresponding to the same frequency point or anchor frequency point in the logical channel group;
  • Step S204 The first communication node sends a buffer status report (Sidelink BSR) to the second communication node, where the Sidelink BSR includes at least one of the following: a target index corresponding to the same frequency point or anchor frequency point; Logical channel group identification or logical channel identification; the cache size.
  • Sidelink BSR buffer status report
  • the terminal sends a Sidelink BSR carrying the above parameters to the base station to request resources, and the base station allocates resources on the frequency point according to the above parameters.
  • the above technical solution solves the problem that the efficiency of requesting resources by the terminal in the related art is low, and the efficiency of requesting resources by the terminal is greatly improved, and the base station can reasonably allocate resources for each terminal on each carrier.
  • the execution body of the above steps may be a terminal, such as a vehicle or the like, but is not limited thereto.
  • the first communication node receives the second communication node configuration or the pre-agreed frequency point information includes at least one of the following: Sidelink available frequency point information; supports data offloading or support The number of frequency points of the data copy; the split ratio of each data splitting frequency; the split data size corresponding to one or more split data sizes of the logical channel, wherein the split data size is the logical channel The maximum amount of data transferred to a certain frequency point; the Sidelink logical channel and/or the Sidelink logical channel group and/or the target identifier, mapping information with one or more frequency points; frequency priority; corresponding to the target identifier And/or anchor point frequency information of the target identifier.
  • the method further includes at least one of the following: the first communication node determines the number of frequency points used according to at least one of the following information, and/ Or the amount of data transmission at each frequency point: available frequency point information; the size of the split data amount; the split ratio; the number of frequency points supporting data splitting or supporting data copying; the priority of the frequency point; the first communication node determines the corresponding At least one of the following information of the bearer of the data replication: the number of frequency points used, the mapping relationship between the logical channel and the frequency point corresponding to the bearer;
  • the method before receiving the second communication node configuration or pre-configured frequency point information, the method further includes: the first communication node reporting, to the second communication node, at least the following parameters corresponding to each target identifier or logical channel One: data rate; reliability level; Near Field Communication Data Packet Priority (PPPP) information.
  • PPPP Near Field Communication Data Packet Priority
  • the method further includes: the first communication node confirms that the logical channel corresponding to any frequency point has data to be sent, and the frequency point corresponds to The first communication node is triggered to perform a Sidelink BSR report when there is no data to be sent before the logical channel.
  • the first communications node determines, according to at least one of the following information, the number of frequency points used, and/or the amount of data transmission at each frequency point: available frequency point information; the size of the split data volume; the split ratio; Data shunting or number of frequency points supporting data copying; the priority of the frequency point includes at least one of the following: when the buffer size data size of the logical channel is smaller than the split data size, the first The communication node selects the first frequency point transmission data; when the buffer size data size of the logical channel is greater than the split data size size, the first communication node transmits the offload data by using the first frequency point The data corresponding to the split data size, the data of the remaining data size is selected by using other frequency points in the available frequency points, wherein the data volume of each of the other frequency points does not exceed the amount of the split data The first communication node determines the amount of data transmitted at each frequency point according to the buffer size of the logical channel and the split ratio.
  • the first communication node selects the first frequency point and/or the other frequency points by: the first communication node selects a data offload according to a priority of each frequency point from highest to lowest order The frequency used.
  • the method further includes: the first communication node reporting only the target identifier corresponding to the anchor frequency point in the Sidelink UEInformation.
  • the first communications node sends at least one of the following information to the second communications node: a target identifier; a logical channel group and/or a logical channel corresponding to the available Frequency point information, wherein the available frequency point information includes an anchor frequency point supported by the target identifier, and/or optional frequency point information; a target identifier; a logical channel group and/or a logical channel corresponding to the logical channel Instructions.
  • the sum of the buffer size buffer sizes of the corresponding same frequency points or anchor frequency points is counted on each logical channel.
  • the first communication node reports the Sidelink BSR to the second communication node, and the first communication node reports the BSR according to the target index corresponding to the anchor point frequency.
  • a method for requesting a resource comprising: a first communication node acquiring a buffer size buffer size corresponding to one or more frequency points in a logical channel, wherein the logical channel is used The one or more frequency points are reported to the Sidelink BSR according to the target index corresponding to the one or more frequency points, wherein the BSR includes the size of the buffer value of the frequency channel in the logical channel.
  • the first communication node reporting the v2x-Destination Info List corresponding to each frequency point in the Sidelink UE Information.
  • the network communication target information list is used, the correspondence between the target ID and each logical channel is reported at the same time.
  • the first communication node reports, in the Sidelink UE Information, a v2x-Destination Info List corresponding to each frequency point.
  • the first communication node reports the target ID only in the v2x-Destination Info List corresponding to the anchor point of each logical channel.
  • a method for processing a resource request including: receiving, by the second communication node, a Sidelink BSR reported by the first communication node, where the Sidelink BSR includes at least one of the following information: The logical channel group identifier or the logical channel identifier; a target index corresponding to the same frequency point or anchor frequency point used by one or more logical channels in the logical channel group; and a buffer size of the same frequency point or anchor frequency point; Allocating resources at each frequency point for the first communication node according to the Sidelink BSR.
  • the second communication node configured or pre-agreed frequency point information for the first communication node includes at least one of the following: Sidelink available frequency points Information; a number of frequency points supporting data offloading or supporting data copying; a split ratio on each data splitting frequency; a split data size corresponding to one or more split data sizes of the logical channel, wherein the split data Size is the maximum data transmission amount of the logical channel data to a certain frequency point; Sidelink logical channel and/or Sidelink logical channel group and/or target identifier, mapping information with one or more frequency points; frequency point Priority; anchor point frequency information corresponding to the target identifier and/or target identifier.
  • the second communication node receives, by the first communication node, corresponding to each of the vehicle network target identifiers or logical channels. At least one of the following parameters: data rate data rate; reliability level reliability level; short-range communication data packet priority PPPP information.
  • the second communications node receives at least one of the following information sent by the first communications node: a target identifier; a logical channel group and/or a logic The available frequency point information corresponding to the channel, wherein the available frequency point information includes an anchor frequency point that supports use by the target identifier, and/or optional frequency point information; a target identifier; a logical channel group and/or a logical channel Corresponding data offload indication information.
  • the method further includes: receiving the Sidelink UE Information of the first communication node, where only the anchor is included in the Sidelink UE Information a target identifier corresponding to the point frequency point, wherein the target identifier information is used to identify the target identifier.
  • the first communication node is configured to allocate resources to the first communication node according to the Sidelink BSR, where the second communication node receives, and the first communication node reports the target index according to the anchor point frequency point.
  • the second communication node performs at least one of the following steps: acquiring a target identifier according to the target index in the BSR, and acquiring available frequency point information corresponding to the target identifier; the second communication node according to the data
  • the offload indication information determines whether to use the frequency point in the available frequency point information; the second communication node determines the frequency point of the resource to be allocated in the case of determining that the frequency point in the available frequency point information needs to be used, Allocate resources in the frequency of the resources to be allocated.
  • the first communication node allocates resources at each frequency point according to the Sidelink BSR, including: the second communication node receives, the first communication node is configured according to multiple targets corresponding to multiple frequency points.
  • the BSR reported by the index; the second communication node allocates resources between the plurality of frequency points.
  • the main consideration of the present invention is the V2X communication resource allocation problem.
  • the UE can apply for required resources quickly and efficiently.
  • the base station allocates resources to the UE quickly and flexibly through the resource request indication reported by the UE, and ensures smooth transmission of the V2X data transmission.
  • the data of a car network service type is transmitted by using only one frequency point.
  • the base station may use the frequency and target ID information included in the Sidelink UE Information reported by the UE and the target index reported by the UE.
  • the BSR information derives the correspondence between the target index and the frequency point, thereby allocating resources corresponding to the buffer size of the specific frequency point to the UE.
  • the data of a car network service type can be transmitted using resources at multiple frequency points.
  • the logical channel group the correspondence relationship between the logical channel (LCH) and the frequency point is different, and can be subdivided into the following A series of scenarios:
  • All logical channels within a logical channel group use a unique resource at the same frequency.
  • Different logical channel groups use different frequency resources.
  • 3 is a schematic diagram of using only one same frequency point resource for all logical channels in a logical channel group according to a preferred embodiment of the present invention, as shown in FIG. 3, in which case the UE reports Sidelink UE Information (through link terminal information).
  • the v2x-DestinationInfoList corresponding to different frequency points contains the same target ID.
  • each logical channel created by the transmitting UE corresponds to a specific combination of source ID, PPPP and target ID.
  • the UE may request resources at different frequency points for different data packets of the PPPP. That is to say, in the BSR sent by the UE, different frequency resource resources are requested by indicating different logical channel groups. That is, the existing BSR mechanism can meet such reporting requirements.
  • All logical channels in a logical channel group can use resources on multiple frequency points, and thus can be divided into the following subdivisions:
  • Each logical channel in a logical channel group can only use a single frequency resource. Different logical channels may use resources at different frequency points.
  • 4 is a schematic diagram of using unique and mutually different frequency point resources for each logical channel in a logical channel group according to a preferred embodiment of the present invention, as shown in FIG. 4, in which case, according to the existing BSR reporting mechanism, It works. Specifically, before each report, the UE first counts the sum of the buffer sizes on all the different logical channels in the same logical channel group that use the same frequency resource, and then reports the BSRs corresponding to the target indexes of the different frequency points.
  • FIG. 5 is a schematic diagram of different logical channels using the same frequency point set according to a preferred embodiment of the present invention, as shown in FIG. 5, in this case, the UE is The data of the car network service type corresponding to the target ID selects the available frequency point set for data transmission. If the UE uses the existing Sidelink UE Information and BSR reporting mechanism to assemble the BSR request resource including the target index, the logical channel group identifier, and the buffer size, the UE does not know which frequency point in the available frequency set should be requested. Resources.
  • a possible implementation method is that the UE reports the target index, the logical channel group ID, and the Buffer Size on each available frequency point corresponding to the available frequency point set, which causes the same buffer to be reported multiple times corresponding to different frequency points. Size.
  • the base station may misinterpret that the UE is to send multiple times the data size in the buffer size at multiple frequencies.
  • FIG. 6 is a schematic diagram of different logical channels using different frequency point set resources according to a preferred embodiment of the present invention.
  • the UE uses the existing Sidelink UE Information and BSR reporting mechanism.
  • the MAC layer of the transmitting end UE cannot pass the existing The mechanism divides the Buffer Size of this logical channel exactly in units of frequency points. Therefore, the target index, the logical channel group ID, and the Buffer Size can be simply reported, but multiple frequency points are used at this time.
  • the target index needs to be changed, and the same logical channel group ID and Buffer Size are reported multiple times. .
  • the base station may misinterpret that the UE is to send multiple times the data size in the buffer size at multiple frequencies.
  • the present invention provides the following series of solutions for the different problems elicited by the above scenarios:
  • the frequency buffer size is data size
  • the logical channel buffer size is buffer size.
  • the buffer size can be divided into multiple data sizes, or a part of the buffer sizes of the plurality of logical channels can be selected as the data size.
  • a plurality of frequency point resources may be used for the target ID, but all logical channels in the logical channel group use the same frequency resource set. In order to avoid repeated transmission of the same buffer size multiple times, the resource request may be duplicated. There are several ways to improve:
  • the base station can configure the number of frequency points of data splits for different service types of different UEs, and the split ratio of each frequency point, and the UE selects a corresponding number of frequency points according to the number of data splits, as shown in Table 1, Table 1 is a correspondence table of frequency points and split ratios according to a preferred embodiment of the present invention:
  • the number of resources that should be applied at each frequency point is calculated according to the split ratio. Specifically, when reporting the BSR of a certain logical channel group, the UE firstly calculates the sum of the buffer sizes of the same frequency point set for each logical channel in the logical channel group, and then according to the split ratio of each frequency point configured by the base station, according to the following The formula calculates the exact number of resources for each frequency point required for the request:
  • the BSR corresponding to the buffer size is reported corresponding to the target index of the different frequency points.
  • the UE may report the data rate and the Proper Per-Packet Priority (PPPP) information of each V2X service or logical channel to the base station, so that the base station can make a correct split decision.
  • PPPP Proper Per-Packet Priority
  • the base station may configure the split data size for the different logical channels for the UE, and configure the priority for the UE to use different frequency points corresponding to the same service in the same logical channel; or configure the UE to be the same for the same logical channel.
  • the corresponding primary frequency point of the service and a series of secondary frequency points, and the order of use of the secondary frequency points is configured; or the order of use of the corresponding series of the same priority frequency points of the UE for the same service in the same logical channel is configured.
  • the UE selects the first frequency point for transmission.
  • the data size1 of the logical channel LCH1 is greater than the split data size1, the UE may request the resource of the split data size1 at the first frequency point. Afterwards, for the remaining data of the logical channel, the UE will continue to consider requesting the BSR to request resources at the second frequency point.
  • the UE requests (data size1)-(split data size1) resources at the second frequency point, otherwise the UE may send (split data size1) resources at the second frequency point, and continue to consider the BSR in the first Resources are requested for the remaining data of this logical channel at three frequencies, and so on.
  • the UE counts the resource sums requested by each frequency point on all corresponding logical channels in the logical channel group, and reports them in units of logical channel groups.
  • FIG. 7 is a schematic diagram of reporting a corresponding target ID by a V2X-DestinationInfoList corresponding to a frequency point according to a preferred embodiment of the present invention. As shown in FIG. 7, the UE reports other optional frequency point set information corresponding to the target ID. The selected may also include an indication that the target ID supports data split. Afterwards, the UE reports the corresponding target index when reporting the BSR.
  • the base station After searching for the corresponding target ID according to the target index, the base station allocates resources on each selectable frequency point according to the set of selectable frequency points and/or the split indication corresponding to the target ID.
  • the sum of the resource sizes allocated by the base station at each frequency point should satisfy the resource size of the corresponding target index indicated by the UE when reporting the BSR.
  • the BSR reports the logical channel as the unit.
  • the UE reports the BSR to solve the problem of selecting different frequency resources for sidelink transmission in units of logical channels.
  • the base station may be configured to configure a mapping relationship between the logical channel and the PPPP or the UE may simultaneously report the information of the logical channel group and the logical channel in the BSR.
  • FIG. 8 is a schematic diagram of reporting a target ID and a logical channel corresponding thereto or a logical channel set in a v2x-DestinationInfoList of different frequency points according to a preferred embodiment of the present invention. As shown in FIG. 8, the reported frequency point can be seen. Do this as the anchor carrier frequency (anchor frequency point) for a particular logical channel of the target ID. At the same time, the UE still needs to separately report the target ID and other optional frequency point set information that each logical channel can support, and an indication supporting split.
  • the UE needs to report the buffer size corresponding to each logical channel when reporting the BSR.
  • the base station can find the set of optional frequency points, split indication, etc. through the target ID and the specific logical channel, and then the base station can perform resources on each optional frequency point. distribution.
  • the UE may report the resource allocation ratio of each frequency point corresponding to the same target ID and the same logical channel to the base station, so that the base station may allocate resources at each frequency point to the UE according to a specific ratio. ( Figure 7)
  • the specific embodiment shows how the UE reports the BSR for resource request in a scenario where the target ID can only use the resources on one frequency point. The following is explained in detail through the example 1 to the second embodiment.
  • the current service 1 corresponds to the target ID1
  • the service 2 corresponds to the target ID2
  • the service 3 corresponds to the target ID3
  • the target ID1 can only use the resources on the frequency point f1
  • the target ID2 can only use the resources on the frequency point f1
  • the target ID3 can only use the frequency.
  • Point the resource on f2. Includes the following two examples.
  • UE1 desires to perform broadcast transmission of service type 1.
  • the UE1 needs to report the v2x-DestinationInfoList ⁇ f1, Destination ID1, Destination ID2 ⁇ related to the frequency point f1 available to the target ID1 in the Sidelink UE Information.
  • the UE1 reports that the BSR requests the resource for the target ID1, and the format is ⁇ Destination Index0, LCG1, Buffer Size ⁇ .
  • the base station can determine, by using the Destination Index 0, that the resource size of the Buffer Size used by the traffic 1 for the traffic 1 on the f1 frequency point should be allocated to the UE1.
  • UE1 desires to perform broadcast transmission of service type 1 and service type 3.
  • the UE1 needs to report the v2x-DestinationInfoList related to the frequency point f1 available for the target ID1, and the v2x-DestinationInfoList related to the frequency point f3 available for the target ID3, as shown in Table 2.
  • Target ID1 related Target ID3 related v2x-DestinationInfoList ⁇ f1,[Destination ID1,Destination ID2] ⁇ ⁇ f2,[Destination ID3] ⁇
  • Table 3 is Table 2 according to Example 2.
  • the base station configures the corresponding resource for the UE according to the reported information, and informs the UE1 through the RRC Reconfiguration message. After that, the UE reports that the BSR requests the resource for the target ID1 and the target ID3, and the format is ⁇ Destination Index0, LCG1, Buffer Size1 ⁇ , ⁇ Destination Index2, LCG2, Buffer Size2 ⁇ , and the base station can determine that the F1 frequency should be allocated to the UE1 through the Destination Index0.
  • the resource used for the service 1 is the resource of the Buffer Size1.
  • the Destination Index 1 can determine that the resource of the resource size of Buffer Size 2 used by the service 3 for the F2 frequency point should be allocated to the UE1.
  • a plurality of frequency point resources may be used for one target ID, and all logical channels in one logical channel group use the same frequency resource, and different logical channel groups may use different frequency resources.
  • the current service 1 corresponds to the target ID1
  • the service 2 corresponds to the target ID2
  • the service 3 corresponds to the target ID3, and the target ID1, and the resources on the frequency points f1, f2
  • the logical channel group 1 uses the resources on f1, and the logical channel group 2 uses Resources on f2
  • target ID2 can use resources on frequency points f2, f3, where logical channel group 1 uses resources on f2, logical channel group 2 uses resources on f3, and target ID3 can use frequency points f3, f4 Resources, where logical channel group 1 uses resources on f3 and logical channel group 2 uses resources on f4.
  • the third embodiment includes the following two examples.
  • the UE1 needs to perform the broadcast transmission of the service type 1.
  • the UE1 needs to report the v2x-DestinationInfoList related to the frequency points f1 and f2 available to the target ID1 in the Sidelink UE Information, and the content of the report is as shown in Table 4, and Table 4 is based on the example. Table 1 of 3.
  • Table 5 the contents in Table 5 can be known according to the serialization rule of the Destination index, and Table 5 is Table 2 according to Example 3.
  • the base station configures the resources of the corresponding frequency point for the UE according to the report information of the UE, and then tells the UE1 through the RRC Reconfiguration message. Subsequently, the UE may report the BSR as the target ID1 requesting the resource, and assume that the resource of the DataSize size is required.
  • the internal AS layer of the UE divides the data of the Data Size into a Buffer Size1+Buffer Size2 packet with different PPPP according to the service requirement.
  • the Buffer Size1 is sent through the LCG1, and the Buffer Size2 is sent through the LCG2, and the UE1 first judges that the target ID1, LCG1 is associated with f1, and LCG2 is associated with f2.
  • the UE reports the BSR to the data packets of the two different PPPPs, as shown in Table 6, and Table 6 is Table 3 according to Example 3.
  • the base station After receiving the report information, the base station knows that for the target ID1 of UE1, it should allocate the resource of Buffer Size1 on f1 and allocate the resource of Buffer Size2 on f2.
  • the UE1 needs to perform broadcast transmission of the service type 1 and the service type 2.
  • the UE1 needs to report the v2x-DestinationInfoList related to the frequency points f1, f2, and f3 available to the target ID1 and the target ID2 in the Sidelink UE Information, as shown in Table 7.
  • Table 7 is a table 4 according to Example 4.
  • Table 8 the contents in Table 8 can be known according to the serialization rule of the Destination Index, and Table 8 is Table 5 according to Example 4.
  • the base station configures the resources of the corresponding frequency point for the UE according to the report information of the UE, and then tells the UE1 through the RRC Reconfiguration message. Subsequently, UE1 can report the BSR requesting resources for the target ID1 and the target ID2. It is assumed that the target ID1 requires a resource of size Size A, and the target ID2 requires a total of Data SizeB resources. At this time, the internal AS layer of the UE sets the data of the Data SizeA according to the service requirement. Divided into two different PPPP data packets of Buffer Size1+Buffer Size2, the Data SizeB data is divided into two different PPPP data packets of Buffer Size3+Buffer Size4.
  • the base station After receiving the report information, the base station knows that for the target ID1 of UE1, it should allocate the resource of Buffer Size1 on f1, and allocate the resource of Buffer Size2 on f2. For the target ID2, it should allocate Buffer Size3 on f2. Resources, allocate resources of Buffer Size4 on f3.
  • multiple frequency point resources may be used for one target ID. Only one frequency point resource may be used for all logical channels in one logical channel group, and different frequency point resources may be used for different logical channels. For this situation, the manner in which the UE reports the BSR will be described in Example 5.
  • the target ID1 can use the resources on the frequency points f1, f2, and f3, and at the same time, the frequency point f1 corresponds to the logical channel 1 and the logical channel 3, the f2 corresponds to the logical channel 2 and the logical channel 4, and the f3 corresponds to the logical channel. 5, while logical channels 1, 2, 3 are all in logical channel group 1; logical channels 4, 5 are all in logical channel group 2.
  • This specific embodiment 3 includes the following example.
  • the UE1 needs to perform the broadcast transmission of the service type 1.
  • the UE1 needs to report the v2x-DestinationInfoList corresponding to the frequency points f1, f2, and f3 available to the target ID1 in the Sidelink UE Information.
  • Table 10 is based on Table 1 of Example 5.
  • Table 11 the contents of Table 11 can be known according to the Destination Index serialization rule, and Table 11 is Table 2 according to Example 5.
  • the base station configures the resources of the corresponding frequency point for the UE according to the report information of the UE, and then tells the UE1 through the RRC Reconfiguration message.
  • the packet sizes are Buffer Size1, Buffer Size2, Buffer Size3, Buffer Size4, and Buffer Size5, respectively.
  • UE1 should report the BSR in the following manner. As shown in Table 12, Table 12 is Table 3 according to Example 5.
  • the base station After receiving the report information, the base station knows that for the target ID1 of UE1, it should allocate buffer (buffer size1+buffer size3) resources to f1, and allocate buffer size2 (for logical channel group 1) and buffer size4 to f2. For resources of logical channel group 2, resources of buffer size 5 are allocated on f3.
  • the specific embodiment may use multiple frequency point resources for one target ID, where any logical channel included in the logical channel group may use multiple frequency point resources, but each logical channel uses the same frequency resource set, different logic.
  • Channel groups can use the same or different sets of frequency resources. For this situation, the manner in which the UE reports the BSR will be explained through the example 6 to the example 8.
  • the corresponding frequency point set ⁇ f3, f4 ⁇ belongs to logical channel group 3.
  • This specific embodiment 4 includes the following three examples.
  • UE1 needs to perform broadcast transmission of service type 1.
  • UE1 needs to report v2x-DestinationInfoList ⁇ f1, DestinationID1 ⁇ f2, DestinationID1 corresponding to the frequency points f1, f2, f3, and f4 available to the target ID1 in the Sidelink UE Information.
  • ⁇ f3, Destination ID1 ⁇ f4, Destination ID1 ⁇ as shown in Table 13, Table 13 is Table 1 according to Example 6.
  • v2x-DestinationInfoList ⁇ f1,DestinationID1 ⁇ ⁇ f2,Destination ID1 ⁇ ⁇ f3,Destination ID1 ⁇ ⁇ f4,Destination ID1 ⁇
  • Table 14 can be known according to the Destination Index serialization rule, and Table 14 is Table 2 according to Example 6.
  • the base station configures the resource corresponding to the frequency point for the UE1 according to the report information of the UE1, and then informs the UE1 through the RRC Reconfiguration message. If the data size that the UE needs to transmit through the logical channels 1, 2, 3, 4, 5, 6 is Buffer Size1, Buffer Size2, Buffer Size3, Buffer Size4, Buffer Size5, Buffer Size6, then the UE reports
  • the BSRs are respectively shown in Table 15, and Table 15 is Table 3 according to Example 6.
  • the base station After receiving the BSR report from the UE, the base station can accurately allocate resources at each frequency point to UE1.
  • the UE1 needs to perform the broadcast transmission of the service type 1.
  • the UE1 needs to report the v2x-DestinationInfoList corresponding to the frequency points f1, f2, f3, and f4 available to the target ID1 in the Sidelink UE Information, as shown in Table 16, Table 16 is Table 1 according to Example 7.
  • v2x-DestinationInfoList ⁇ f1,Destination ID1 ⁇ ⁇ f2,Destination ID1 ⁇ ⁇ f3,Destination ID1 ⁇ ⁇ f4,Destination ID1 ⁇
  • Table 17 the contents shown in Table 17 can be known according to the Destination Index serialization rule, and Table 17 is Table 2 according to Example 7.
  • the base station After receiving the BSR report from the UE, the base station can accurately allocate resources at each frequency point to UE1.
  • UE1 needs to perform broadcast transmission of service type 1.
  • the corresponding anchor point frequency is f1
  • the remaining available frequency point sets are ⁇ f2, f3, f4 ⁇
  • the UE first reports Sidelink UE Information.
  • the indication information of the Destination ID1 is included in the v2x-DestinationInfoList corresponding to the f1, it is ⁇ f1, Destination ID1 ⁇ , and other optional frequency point set information corresponding to the Destination ID1 is also reported.
  • ⁇ DestinationID1 [f2, f3
  • the base station configures the resources on the ⁇ f1, f2, f3, and f4 ⁇ for the UE1.
  • the base station will allocate a resource of the same Buffer Size size on each of the selectable frequency points (including the anchor frequency point) ⁇ f1, f2, f3, 4 ⁇ according to the report.
  • the specific embodiment is directed to the case where only one frequency resource can be used for any logical channel, and the BSR mode reported by the UE will be described by using the example 9.
  • the set of available frequency points is ⁇ f1, f2, f3 ⁇
  • the logical channel 1 corresponds to the frequency point f1
  • the logical channel 2 corresponds to the frequency point f2
  • the logical channel 3 corresponds to the frequency point f3.
  • This specific embodiment 5 includes the following example.
  • the UE1 needs to perform broadcast transmission of the service type 1.
  • the UE reports the corresponding v2x-DestinationInfoList ⁇ f1, Destination ID1 ⁇ f2, Destination ID2 ⁇ f3, Destination ID3 ⁇ in the Sidelink UE Information, at this time, according to the Destination Index.
  • This embodiment is directed to the case where a set of frequency points can be used for any logical channel.
  • the manner in which the UE reports the BSR will be described by way of example 10.
  • the set of available frequency points is ⁇ f1, f2, f3 ⁇ , where logical channel 1 corresponds to ⁇ f1, f2 ⁇ , and logical channel 2 corresponds to ⁇ f2, f3 ⁇ Logical channel 3 corresponds to ⁇ f1, f2, f3 ⁇ .
  • logical channel 1 corresponds to ⁇ f1, f2 ⁇
  • Logical channel 3 corresponds to ⁇ f1, f2, f3 ⁇ .
  • UE1 needs to perform broadcast transmission of service type 1.
  • UE1 reports Destination ID1 and LCH1 in the v2x-DestinationInfoList corresponding to f1 in the Sidelink UE information, and the format is ⁇ f1, Destination ID1, LCH1 ⁇ , and v2x corresponding to f2.
  • DestinationInfoList reports Destination ID1 and LCH2 in the format ⁇ f2, Destination ID1, LCH2 ⁇ , and reports Destination ID1 and LCH3 in the v2x-DestinationInfoList corresponding to f3 in the format ⁇ f3, Destination ID1, LCH3 ⁇ .
  • the UE1 still needs to report a set of target IDs and other optional frequency point set information corresponding to the logical channel and an indication of the split. Specifically, at this time, UE1 still needs to report ⁇ Destination ID1, LCH1, [f2] ⁇ , ⁇ DestinationID1, LCH2, [f3] ⁇ , ⁇ DestinationID1, LCH3, [f2, f3] ⁇ , and serialization according to the Destination Index.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
  • a device for requesting resources is provided, and the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • an apparatus for requesting a resource including:
  • the first acquiring module is configured to obtain a buffer size buffer size corresponding to the same frequency point or anchor frequency point in the logical channel group;
  • a first sending module configured to send a Sidelink BSR to the second communications node, where the Sidelink BSR includes at least one of: a target index corresponding to the same frequency point or anchor frequency point; the logical channel group identifier or Logical channel identifier; the cache size.
  • an apparatus for requesting a resource including:
  • a second acquiring module configured to acquire a buffer size corresponding to one or more frequency points in the logical channel, where the logical channel uses one or more frequency points;
  • the second sending module is configured to report the Sidelink BSR according to the target index corresponding to the one or more frequency points, wherein the Sidelink BSR includes a buffer value size of the frequency channel in the logical channel.
  • an apparatus for processing a resource request including:
  • the first receiving module is configured to receive the Sidelink BSR reported by the first communications node, where the Sidelink BSR includes at least one of the following information: one or more logical channels in the logical channel group, using the same frequency point or anchor point a target index corresponding to the frequency point; the logical channel group identifier or the logical channel identifier; the buffer size of the same frequency point or anchor frequency point;
  • an allocation module configured to allocate resources at each frequency point for the first communication node according to the Sidelink BSR.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • a processor for running a program wherein the program is executed to perform the method described in any of the above alternative embodiments.
  • the storage medium comprises a stored program, wherein the program is executed while performing the method described in any of the above alternative embodiments.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

本发明提供了一种请求资源的方法及装置，处理资源请求的方法及装置，其中，该方法包括：终端获取逻辑信道组中对应相同频点或锚点频点的缓存大小buffer size；终端发送Sidelink BSR至基站，其中，所述Sidelink BSR包含以下至少之一：所述相同频点或锚点频点对应的目标索引；所述逻辑信道组标识或逻辑信道标识；所述缓存大小。

Description

请求资源的方法及装置，处理资源请求的方法及装置
相关申请的交叉引用
本申请基于申请号为201711141257.9、申请日为2017年11月16日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的内容在此以引入方式并入本申请。
技术领域
本申请涉及通信领域，具体而言，涉及一种请求资源的方法及装置，处理资源请求的方法及装置。
背景技术
在相关技术中，随着通信技术的发展及需求的丰富，无线通信的应用场景也日益广泛，其中比较典型的是车联网(Vehicle Networking)。所谓的车联网，是车辆可以参与到无线通信中，通过利用先进的无线蜂窝通信技术，实现车与车，车与路侧基础设施间的实时信息交互，告知彼此目前的状态(包括车辆的位置，速度，加速度，行驶路径)及获知的道路环境信息，协作感知道路危险状况，及时提供多种碰撞预警信息，防止道路交通安全事故的发生。
车联网通信的模式具体分为三种：车车通信(Vehicle-to-Vehicle Communications,简称为V2V)，车网通信(Vehicle-to-Infrastructure Communications,简称为V2I)，车人通信(Vehicle-to-Pedestrian,简称为V2P)三类，这三类也可以统称为Vehicle-to-Everything(简称为V2X)通信。
在V2X车联网通信模式下，车联网信息的传输大多以广播和组播方式为主。主要的实现技术有两种:
1)基于用户设备(UE)到UE的直接发现/通信(D2D，sidelink，ProSe)支持通过PC5接口进行V2X消息的广播传输；2)基于多播/组播单频网络(MBMS)广播机制支持通过Uu口进行V2X消息的广播传输。本申请重点讨论基于PC5接口实现V2V消息传输的通信机制及长期演进(LTE)标准实现。
传统的以基站为中心的蜂窝网络在高数据速率以及邻近服务的支持方面存在明显的局限性，在这种需求背景下，代表未来通信技术发展新方向的设备到设备(Device-to-Device，简称为D2D)技术应运而生。D2D技术的应用，可以减轻蜂窝网络的负担、减少用户设备的电池功耗、提高数据速率，并改善网络基础设施的鲁棒性，很好地满足上述高数据速率业务和邻近服务的要求。目前D2D技术又称之为邻近服务(Proximity Services，简称为ProSe)、单边链路或者直通链路(SideLink，简称为SL)。
在V2X通信中，支持两种资源分配模式:1)基于调度的资源分配(Scheduled resource allocation,也称为mode 3，这种方式下UE需进入无线资源控制(RRC)连接状态，基站为UE分配专有车联网发送资源。2)UE自主资源选择(UE autonomous resource selection，也称为mode 4，这种方式下UE基于sensing从资源池中自主选择资源以进行旁链控制信息(SCI，Sidelink Control Information)和数据传输。这种方式可用于空闲态(IDLE态)或者连接态(CONNECTED态)UE。
在现有的机制中，在V2X通信中，UE可以使用多个载波上的资源在单边链路上发送和接收数据。每个车联网数据对应的车联网业务类型通常关联到一个或多个可用频点。高层可以将不同的车联网业务类型对应的目标标识(destination ID)发给接入层(AS层)。连接态的UE在请求V2X SL资源配置时，可以将每个频点上对应的业务的目标ID通过车联网通信UE消息(Sidelink UE Information)上报给基站，图1是根据相关技术中序列 化方式的示意图，如图1所示的序列化方式，基站和UE会生成同样的目标索引(Destination Index)，用来唯一地指示频点和目标ID之间的对应关系。如果UE被基站配置使用mode3资源分配方式，则UE可通过缓存状态报告(Buffer Status Report，简称为BSR)向基站请求对应频点的资源，BSR中携带目标index，逻辑信道组(LCG)以及缓冲区大小等信息。基站根据UE的BSR请求为UE分配对应频点上的SL发送资源。
除了上述动态资源调度，为了方便基站为UE分配半静态调度(SPS)的资源，R14V2X通过UE向基站发送SPS辅助消息，其中包含周期性，偏移量，数据大小和数据分组优先级(PPPP)等指示信息，来辅助基站为UE分配SPS SL资源。
但是，在引入载波聚合中的数据分流(data split)和数据复制场景(data duplication)之后，对于同一个逻辑信道组，会传输不同的PPPP数据包。在这种情况下，现有机制不能够有效地指示各个频点上请求的资源大小。
在相关技术中，随着第五代通信技术的演进，对于V2V/V2I/V2P业务的延迟有了更高的需求，从之前的100毫秒提升至10毫秒甚至3毫秒。同时，在保证低延迟需求的前提下，对于某些特殊业务，也需保证数据传输的高可靠性。
在此之前，对于V2X业务在单一载波上传输的场景，是不支持自动重传请求(ARQ)的特性的。而且混合型自动重传仅支持特定配置次数的媒体接入控制(MAC)协议数据单元(PDU)重传，并且没有确认/非确认消息(ACK/NACK)的消息反馈。所以，目前V2X在单载波上的数据重传业务采用的是时域复用的方式。
另一方面，为了能够提高数据传输率，在多载波上以频域复用的方式提高单位时间内的数据传输量是被建议采纳的。然而，UE如何请求多载波上的资源，以及基站如何合理的为终端使用的各个载波分配资源，并提供 更高的资源效率，目前尚未发现有效的解决。
针对相关技术中终端请求资源的效率低的问题，目前还没有有效的解决方案。
发明内容
本发明实施例提供了一种请求资源的方法及装置，处理资源请求的方法及装置，以至少解决相关技术中终端请求资源的效率低的问题。
根据本发明的一个实施例，提供了一种请求资源的方法，包括：第一通信节点获取逻辑信道组中对应相同频点或锚点频点的缓存大小buffer size；第一通信节点发送Sidelink BSR至第二通信节点，其中，所述Sidelink BSR包含以下至少之一：所述相同频点或锚点频点对应的目标索引；所述逻辑信道组标识或逻辑信道标识；所述缓存大小。
根据本发明的一个实施例，提供了一种请求资源的方法，包括：第一通信节点获取逻辑信道中对应于一个或多个频点的缓存大小buffer size，其中，所述逻辑信道使用一个或多个频点；依据所述一个或多个的频点分别对应的目标索引上报Sidelink BSR，其中，所述BSR中包括该逻辑信道中，使用该频点的缓存数值大小。
根据本发明的另一个实施例，还提供了一种处理资源请求的方法，包括：第二通信节点接收第一通信节点上报的Sidelink BSR，其中，所述Sidelink BSR中包括以下信息至少之一：逻辑信道组中一个或多个逻辑信道，使用的相同频点或锚点频点对应的目标索引；所述逻辑信道组标识或逻辑信道标识；所述相同频点或锚点频点的缓存大小；依据所述Sidelink BSR为所述第一通信节点在各个频点上分配资源。
根据本发明的另一个实施例，还提供一种请求资源的装置，包括：第一获取模块，配置为获取逻辑信道组中对应相同频点或锚点频点的缓存大小buffer size；第一发送模块，配置为发送Sidelink BSR至第二通信节点， 其中，所述Sidelink BSR包含以下至少之一：所述相同频点或锚点频点对应的目标索引；所述逻辑信道组标识或逻辑信道标识；所述缓存大小。
根据本发明的另一个实施例，还提供了一种请求资源的装置，包括：第二获取模块，配置为获取逻辑信道中对应于一个或多个频点的缓存大小buffer size，其中，所述逻辑信道使用一个或多个频点；第二发送模块，配置为依据所述一个或多个的频点分别对应的目标索引上报Sidelink BSR，其中，所述Sidelink BSR中包括该逻辑信道中，使用该频点的缓存数值大小。
根据本发明的另一个实施例，还提供了一种处理资源请求的装置，包括：第一接收模块，配置为接收第一通信节点上报的Sidelink BSR，其中，所述Sidelink BSR中包括以下信息至少之一：逻辑信道组中一个或多个逻辑信道，使用的相同频点或锚点频点对应的目标索引；所述逻辑信道组标识或逻辑信道标识；所述相同频点或锚点频点的缓存大小；分配模块，配置为依据所述Sidelink BSR为所述第一通信节点在各个频点上分配资源。
根据本发明的另一个实施例，还提供了一种存储介质，所述存储介质包括存储的程序，其中，所述程序运行时执行上述可选实施例任一项中所述的方法。
根据本发明的另一个实施例，还提供了一种处理器，所述处理器用于运行程序，其中，所述程序运行时执行上述可选实施例任一项中所述的方法。
通过本发明，终端获取逻辑信道组中对应相同频点或锚点频点的缓存大小buffer size；终端发送Sidelink BSR至基站，其中，所述Sidelink BSR包含以下至少之一：所述相同频点或锚点频点对应的目标索引；所述逻辑信道组标识或逻辑信道标识；所述缓存大小。终端向基站发送携带上述参数的Sidelink BSR来请求资源，基站依据上述参数为终端在频点上分配资源。采用上述技术方案，解决了相关技术中终端请求资源的效率低的问题， 大幅提升了终端请求资源的效率，基站可以合理的为终端在各个载波上分配资源。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据相关技术中序列化方式的示意图；
图2是根据本发明实施例的请求资源的方法的流程图；
图3是根据本发明优选实施例的逻辑信道组内所有逻辑信道使用唯一一个相同频点资源的示意图；
图4是根据本发明优选实施例的逻辑信道组内每个逻辑信道使用唯一且相互不同的频点资源的示意图；
图5是根据本发明优选实施例的不同的逻辑信道使用相同频点集合的示意图；
图6是根据本发明优选实施例的不同逻辑信道使用不同频点集合资源的示意图；
图7是根据本发明优选实施例的在一个频点对应的V2X-DestinationInfoList上报对应的目标ID的示意图；
图8是根据本发明优选实施例的在不同频点的v2x-DestinationInfoList中上报目标ID以及与其对应的逻辑信道，或者逻辑信道集合的示意图。
具体实施方式
本申请文件中的技术方案可以应用于使用PC5接口的场景中，包括但不限于车联网通信。本申请文件中的第一通信节点可以是终端，第二通信 节点可以是基站。
实施例一
在本实施例中提供了一种运行于上述终端的请求资源的方法，图2是根据本发明实施例的请求资源的方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，第一通信节点获取逻辑信道组中对应相同频点或锚点频点的缓存大小(buffer size)；
步骤S204，第一通信节点发送缓存状态报告(Sidelink BSR)至第二通信节点，其中，所述Sidelink BSR包含以下至少之一：所述相同频点或锚点频点对应的目标索引；所述逻辑信道组标识或逻辑信道标识；所述缓存大小。
通过上述步骤，终端向基站发送携带上述参数的Sidelink BSR来请求资源，基站依据上述参数为终端在频点上分配资源。采用上述技术方案，解决了相关技术中终端请求资源的效率低的问题，大幅提升了终端请求资源的效率，基站可以合理的为终端在各个载波上分配资源。
可以理解，目标索引的作用是用来唯一地指示频点/锚点频点和目标标识(ID)之间的对应关系，例如表示为：目标索引＝＝>{频点，目标ID}。
锚点频点可以指示一组可用的载波集合，因此锚点频点的目标索引可以指示如下信息：目标索引＝＝>{锚点频点，目标ID}。其中，锚点频点可以是一组频点的集合，表示为锚点频点＝＝>[一组频点集合]。
可选地，上述步骤的执行主体可以为终端，例如车辆等，但不限于此。
可选地，在第一通信节点上报Sidelink BSR之前，所述第一通信节点接收第二通信节点配置或预先约定的频点信息包括以下至少之一：Sidelink可用频点信息；支持数据分流或支持数据复制的频点个数；各个数据分流频点上的分流比split ratio；对应于逻辑信道的一个或多个分流数据量大小 split data size，其中，所述split data size是所述逻辑信道的数据分流到某个频点上的最大数据传输量；Sidelink逻辑信道和/或Sidelink逻辑信道组和/或目标标识，与一个或多个频点的映射信息；频点优先级；对应于目标标识和/或目标标识的锚点频点信息。
可选地，第一通信节点上报Sidelink BSR至第二通信节点之前，所述方法还包括以下至少之一：所述第一通信节点根据以下信息至少之一确定使用的频点个数，和/或各个频点上的数据传输量：可用频点信息；分流数据量大小；分流比；支持数据分流或支持数据复制的频点个数；频点的优先级；所述第一通信节点确定对应于数据复制的承载的以下信息至少之一：使用的频点个数，所述承载对应的逻辑信道和频点的映射关系；
可选地，接收第二通信节点配置或预配置的频点信息之前，所述方法还包括：所述第一通信节点向第二通信节点上报与每个目标标识或逻辑信道对应的以下参数至少之一：数据率(data rate)；可靠度等级(reliability level)；近距离通信数据分组优先级(PPPP)信息。
可选地，第一通信节点上报Sidelink BSR至第二通信节点之前，所述方法还包括：所述第一通信节点确认与任一频点对应的逻辑信道有数据需要发送，该频点对应的逻辑信道之前没有数据需要发送的情况下，触发所述第一通信节点进行Sidelink BSR上报。
可选地，所述第一通信节点根据以下信息至少之一确定使用的频点个数，和/或各个频点上的数据传输量：可用频点信息；分流数据量大小；分流比；支持数据分流或支持数据复制的频点个数；频点的优先级，包括以下至少之一：当逻辑信道的缓存大小data size小于所述分流数据量大小split data size的情况下，所述第一通信节点选择第一频点传输数据；当逻辑信道的缓存大小data size大于所述分流数据量大小split data size的情况下，所述第一通信节点使用所述第一频点传输所述分流数据量大小split data size 对应的数据，选择可用频点中的其他频点传输剩余的数据量大小的数据，其中，所述其他频点中的每个频点传输数据量不超过所述分流数据量大小；所述第一通信节点依据所述逻辑信道的缓存大小，和分流比确定各个频点传输的数据量。
可选地，所述第一通信节点通过以下方式选择所述第一频点和/或所述其他频点：所述第一通信节点根据各个频点的优先级从高到低顺序选择数据分流使用的频点。
可选地，第一通信节点上报Sidelink BSR至第二通信节点之前，所述方法还包括：所述第一通信节点在SidelinkUEInformation中仅上报所述锚点频点对应的目标标识。
可选地，第一通信节点上报Sidelink BSR至第二通信节点之前，所述第一通信节点向第二通信节点发送以下信息至少之一：目标标识；逻辑信道组和/或逻辑信道对应的可用频点信息，其中，所述可用频点信息包含支持被所述目标标识使用的锚点频点，和/或可选频点信息；目标标识；逻辑信道组和/或逻辑信道对应的数据分流指示信息。
可选地，逻辑信道组中存在多个逻辑信道的情况下，在各个逻辑信道上统计对应的相同频点或锚点频点的缓存大小buffer size之和。
可选地，第一通信节点上报Sidelink BSR至第二通信节点，包括：所述第一通信节点依据所述锚点频点对应的目标索引上报所述BSR。
根据本发明的另一个实施例，还提供了一种请求资源的方法，包括：第一通信节点获取逻辑信道中对应于一个或多个频点的缓存大小buffer size，其中，所述逻辑信道使用一个或多个频点；依据所述一个或多个的频点分别对应的目标索引上报Sidelink BSR，其中，所述BSR中包括该逻辑信道中，使用该频点的缓存数值大小。
可选地，依据所述一个或多个的频点分别对应的目标索引上报Sidelink  BSR，包括：所述第一通信节点在Sidelink UE Information中上报每个频点对应的v2x-Destination Info List(车联网通信目标信息清单)时，将目标ID与各个逻辑信道的对应关系同时上报。
可选地，在所述目标ID存在对应于不同逻辑信道的锚点频点的情况下，所述第一通信节点在Sidelink UE Information中上报每个频点对应的v2x-Destination Info List包括：所述第一通信节点在Sidelink UE Information中，仅在每个逻辑信道的锚点频点对应的v2x-Destination Info List上报目标ID。
根据本发明的另一个实施例，还提供了一种处理资源请求的方法，包括：第二通信节点接收第一通信节点上报的Sidelink BSR，其中，所述Sidelink BSR中包括以下信息至少之一：所述逻辑信道组标识或逻辑信道标识；逻辑信道组中一个或多个逻辑信道使用的相同频点或锚点频点对应的目标索引；所述相同频点或锚点频点的缓存大小；依据所述Sidelink BSR为所述第一通信节点在各个频点上分配资源。
可选地，第二通信节点接收第一通信节点上报的Sidelink BSR之前，所述第二通信节点为所述第一通信节点配置或预先约定的频点信息包括以下至少之一：Sidelink可用频点信息；支持数据分流或支持数据复制的频点个数；各个数据分流频点上的分流比split ratio；对应于逻辑信道的一个或多个分流数据量大小split data size，其中，所述split data size是所述逻辑信道的数据分流到某个频点上的最大数据传输量；Sidelink逻辑信道和/或Sidelink逻辑信道组和/或目标标识，与一个或多个频点的映射信息；频点优先级；对应于目标标识和/或目标标识的锚点频点信息。
可选地，所述第二通信节点为所述第一通信节点配置或预先约定频点信息之前，所述第二通信节点接收第一通信节点上报的与每个车联网目标标识或逻辑信道对应的以下参数至少之一：数据率data rate；可靠度等级 reliability level；近距离通信数据分组优先级PPPP信息。
可选地，第二通信节点接收第一通信节点上报的Sidelink BSR之前，所述第二通信节点接收所述第一通信节点发送的以下信息至少之一：目标标识；逻辑信道组和/或逻辑信道对应的可用频点信息，其中，所述可用频点信息包含支持被所述目标标识使用的锚点频点，和/或可选频点信息；目标标识；逻辑信道组和/或逻辑信道对应的数据分流指示信息。
可选地，第二通信节点接收第一通信节点上报的Sidelink BSR之前，所述方法还包括：接收所述第一通信节点的Sidelink UE Information，其中，所述Sidelink UE Information中仅包括所述锚点频点对应的目标标识，其中，所述目标标识信息用于标识目标标识。
可选地，依据所述Sidelink BSR为所述第一通信节点在各个频点上分配资源，包括：所述第二通信节点接收，所述第一通信节点依据锚点频点对应的目标索引上报的BSR；所述第二通信节点执行以下步骤至少之一：依据所述BSR中的目标索引获取目标标识，获取所述目标标识对应的可用频点信息；所述第二通信节点依据所述数据分流指示信息确定是否使用所述可用频点信息中的频点；所述第二通信节点在确定需要使用可用频点信息中的频点的情况下，确定待分配资源的频点，在所述待分配资源的频点中分配资源。
可选地，依据所述Sidelink BSR为所述第一通信节点在各个频点上分配资源，包括：所述第二通信节点接收，所述第一通信节点依据多个频点对应的多个目标索引上报的BSR；所述第二通信节点在所述多个频点之间分配资源。
下面结合本发明优选实施例进行详细说明。
本发明主要考虑的问题是V2X通信资源分配问题。通过本发明，UE可以快速有效地申请所需资源。基站通过UE上报的资源请求指示，快速灵 活的为UE分配资源，并确保V2X数据传输的顺利进行。
对于目前UE的资源请求，可分为如下场景：
一，一个车联网业务类型的数据仅使用一个频点上的资源传输，在这种场景下，基站可以根据UE上报的Sidelink UE Information包含的频点与目标ID信息以及UE上报的包含目标index的BSR信息推导出目标Index和频点间的对应关系，从而为UE分配特定频点上对应的buffer size的资源。
二，一个车联网业务类型的数据可以使用多个频点上的资源传输，在这种情况下，根据逻辑信道组，逻辑信道(LCH)和频点的对应关系不同，又可以细分为以下一系列场景：
1)一个逻辑信道组内的所有逻辑信道都使用唯一一个相同频点上的资源。而不同逻辑信道组使用不同的频点资源。图3是根据本发明优选实施例的逻辑信道组内所有逻辑信道使用唯一一个相同频点资源的示意图，如图3所示，在这种情况下，UE上报Sidelink UE Information(直通链路终端信息)时在不同频点对应的v2x-DestinationInfoList包含相同的目标ID。同时，发送端UE创建的每个逻辑信道对应特定的源ID、PPPP和目标ID的组合。在目标ID相同的情况下，UE可以为PPPP不同的数据包请求不同频点上的资源。也就是说UE发送的BSR中，通过指示不同的逻辑信道组，来请求不同的频点资源。即现有的BSR机制能够满足这种上报需求。
2)一个逻辑信道组内的所有逻辑信道都可以使用多个频点上的资源，由此，可以分为以下几种细分情况：
i.逻辑信道组内的每个逻辑信道只能使用唯一一个频点资源，不同的逻辑信道有可能使用不同频点上的资源。图4是根据本发明优选实施例的逻辑信道组内每个逻辑信道使用唯一且相互不同的频点资源的示意图，如图4所示，在这种情况下，按照现有的BSR上报机制仍是可行的。具体来说，在每次上报前，UE首先统计相同逻辑信道组内使用同一频点资源的所 有不同逻辑信道上的buffer size之和，然后分别对应于不同频点的目标index上报BSR。
ii.逻辑信道组内的所有逻辑信道都可以使用多个频点上的资源：
a)不同的逻辑信道使用相同频点集合的资源，图5是根据本发明优选实施例的不同的逻辑信道使用相同频点集合的示意图，如图5所示，在这种情况下，UE为对应于目标ID的车联网业务类型的数据选择了可用频点集合进行数据传输。若沿用已有的Sidelink UE Information和BSR上报机制，UE组装包含目标Index、逻辑信道组标识和缓冲区大小的BSR请求资源时，UE并不清楚应该请求可用频点集合里哪一个频点上的资源。一种可能的实现方法是UE在可用频点集合对应的各个可用频点上上报目标Index、逻辑信道组ID和Buffer Size，这种方式导致了对应于不同的频点上报了多次相同的buffer size。基站会误解以为UE要在多个频点上发送数倍于buffer size中的数据大小。
b)不同的逻辑信道使用不同频点集合的资源。图6是根据本发明优选实施例的不同逻辑信道使用不同频点集合资源的示意图，如图6所示，这种场景下，如果UE使用已有的Sidelink UE Information和BSR上报机制。在相同的逻辑信道组内，对于某一逻辑信道对应多个频点资源，而其中某些频点又被逻辑信道组内的多个逻辑信道使用，发送端UE的MAC层并不能通过已有机制将对于此逻辑信道的Buffer Size准确的以频点为单位划分。因此，只能简单的将目标Index、逻辑信道组ID和Buffer Size综合上报，但是此时又使用到多个频点，因此需要改变目标Index，将相同的逻辑信道组ID和Buffer Size上报多次。这就导致了对应于不同的频点上报了多次相同的buffer size。基站会误解以为UE要在多个频点上发送数倍于buffer size中的数据大小。
针对以上场景所引出的不同问题，本发明给出以下一系列解决方案：
需要补充的是，在本申请文件中，频点缓存大小是data size，逻辑信道缓存大小为buffer size。可以将buffer size分为多个data size，也可以将多个逻辑信道的buffer size中各选取一部分来组合作为data size。
针对目标ID可使用多个频点资源，但逻辑信道组内的所有逻辑信道使用相同的频点资源集合的情况，为了避免重复发送多次相同的buffer size，造成资源请求重复的问题，可采用以下多种方法进行改进：
1)基站可以配置针对不同UE的不同业务类型的data split的频点个数，以及各个频点上的split ratio，UE根据data split个数选择对应个数的频点，如表1所示，表1是根据本发明优选实施例的频点和分流比的对应关系表：
表1
频点 f a f b f c
Split Ratio Split ratio a Split ratio b Split ratio c
在上报BSR时，根据split ratio算出在各个频点上应当申请的资源数。具体的，UE在上报某个逻辑信道组的BSR时，首先统计该逻辑信道组内各个逻辑信道可以使用相同频点集合的buffer size之和，然后根据基站配置各个频点的split ratio，按照以下公式计算出所需请求的每个频点的准确资源数：
Resource on f a＝((buffer size)*(split ratio a))；
最后分别对应于不同频点的目标index上报对应缓冲区大小的BSR。可选的，UE可向基站上报每个V2X service或逻辑信道对应的data rate及近距离通信数据分组优先级(Prose Per-Packet Priority，简称为PPPP)信息，便于基站做出正确的split决策。
2)基站可以为UE配置针对不同逻辑信道的split data size，同时会配置给UE针对同一逻辑信道内的同一业务对应的不同频点使用优先级；或者会 配置给UE针对同一逻辑信道内的同一业务的对应的主频点和一系列辅频点，并且配置辅频点的使用顺序；或者会配置给UE针对同一逻辑信道内的同一业务的对应的一系列相同优先级频点的使用顺序。在进行资源请求的时候，UE会选择第一个频点进行发送，当逻辑信道LCH1的data size1大于split data size1时，UE最多可在第一频点请求split data size1的资源。之后，对于此逻辑信道的剩余数据，UE会继续考虑申请BSR在第二个频点上请求资源，若此时
((data size1)-(split data size1))<(split data size1))，
则UE在第二频点上请求((data size1)-(split data size1))的资源，否则UE最多可在第二频点上发送(split data size1)的资源，并继续考虑通过BSR在第三个频点上为此逻辑信道的剩余数据请求资源，以此类推。最后，UE统计出在此逻辑信道组内，每个频点在所有对应的逻辑信道上请求的资源和，以逻辑信道组为单位上报。
3)UE在上报Sidelink UE Information时，仅在一个频点对应的V2X-DestinationInfoList上报对应的目标ID。图7是根据本发明优选实施例的斤在一个频点对应的V2X-DestinationInfoList上报对应的目标ID的示意图，如图7所示，UE上报此目标ID对应的其他可选频点集合信息，可选的还可包含此目标ID支持data split的相关指示。之后，UE在上报BSR时上报对应的目标index。基站根据目标index查找对应的目标ID后，根据目标ID对应的可选频点集合和/或split指示，在各个可选频点上分配资源。基站在各个频点上分配的资源大小之和应满足UE上报BSR时指示的对应目标index的资源大小。
针对在同一逻辑信道组内对于任意逻辑信道只能使用一个频点资源的情况，可以采用以下解决方式来进行BSR增强：
1)首先，BSR上报以逻辑信道为单位，此时UE上报BSR可以解决以 逻辑信道为单位选择不同频点资源进行sidelink传输的需求。为了解决基站在调度时无法根据优先级分配不同逻辑信道资源的问题，可以考虑让基站配置逻辑信道与PPPP之间的映射关系或是UE在BSR中同时上报逻辑信道组和逻辑信道的信息。
针对在同一逻辑信道组内，对于任意逻辑信道使用不同的频点资源集合的情况，可以采用以下解决方式来进行BSR增强：
1)UE在Sidelink UE Information中在不同频点的v2x-DestinationInfoList中上报目标ID以及与其对应的逻辑信道，或者逻辑信道集合。图8是根据本发明优选实施例的在不同频点的v2x-DestinationInfoList中上报目标ID以及与其对应的逻辑信道，或者逻辑信道集合的示意图，如图8所示，此时上报的频点可以看做是针对目标ID的特定逻辑信道的锚点载频(锚点频点)。同时UE仍然需要分别上报目标ID和各个逻辑信道可以支持的其他可选频点集合信息，以及支持split的指示。后续，UE在上报BSR时需上报各个逻辑信道对应的buffer size，基站通过目标ID和具体逻辑信道，可以找到可选频点集合，split指示等，然后基站可以进行各个可选频点上的资源分配。可选的，UE可以将对应相同目标ID，相同逻辑信道的各个频点上的资源分配比例上报给基站，这样基站可以按照特定比例分配各个频点上的资源给UE。(图7)
下面结合本发明优选具体实施例的具体实施例进行详细说明。
具体实施例一
本具体实施例给出在一个目标ID仅可以使用一个频点上的资源的场景下，UE如何上报BSR进行资源请求，以下通过实例1至实例2详细阐述。
假设当前业务1对应目标ID1，业务2对应目标ID2，业务3对应目标ID3，目标ID1仅能使用频点f1上的资源，目标ID2仅能使用频点f1上的 资源，目标ID3仅能使用频点f2上的资源。包括以下两个实例。
实例1
在高速路场景中，Mary和John驾驶着具有v2x通信功能的车辆UE1和UE2，UE1和UE2彼此在Sidelink通信范围内。
此时，UE1希望进行业务类型1的广播发送。首先UE1在Sidelink UE Information中需要上报目标ID1可用的频点f1相关的v2x-DestinationInfoList{f1，Destination ID1，Destination ID2}，此时，基站根据Destination index的序列化规则，可以知道Destination Index0＝{f1，Destination ID1}，Destination Index1＝{f1，Destination ID2}，基站会根据上报的信息，为UE1配置对应的资源，通过无线资源控制配置消息(RRC Reconfiguration)通知至UE1。之后，UE1上报BSR为目标ID1请求资源，格式为{Destination Index0，LCG1，Buffer Size}。
基站通过Destination Index0可以判断出应为UE1分配f1频点上给业务1使用的资源大小为Buffer Size的资源。
实例2
此时，UE1希望进行业务类型1和业务类型3的广播发送。首先UE1在Sidelink UE Information中需要上报目标ID1可用的频点f1相关的v2x-DestinationInfoList,以及目标ID3可用的频点f3相关的v2x-DestinationInfoList，如表2所示。
表2
  目标ID1相关 目标ID3相关
v2x-DestinationInfoList {f1,[Destination ID1,Destination ID2]} {f2,[Destination ID3]}
此时，根据Destination index的序列化规则，可以知道表3的内容，表3是根据实例2的表二。
表3
Destination Index0 Destination Index1 Destination Index2
{f1,Destination ID1} {f1,Destination ID2} {f2,Destination ID3}
基站会根据上报的信息，为UE配置对应的资源，通过RRC Reconfiguration消息告诉UE1。之后，UE上报BSR为目标ID1和目标ID3请求资源，格式为{Destination Index0，LCG1，Buffer Size1}、{Destination Index2，LCG2，Buffer Size2}，基站通过Destination Index0可以判断出应为UE1分配f1频点上给业务1使用的资源大小为Buffer Size1的资源，通过Destination Index1可以判断出应为UE1分配f2频点上给业务3使用的资源大小为Buffer Size2的资源。
具体实施例二
本具体实施例针对一个目标ID可以使用多个频点资源，且一个逻辑信道组内的所有逻辑信道使用相同的一个频点资源，不同的逻辑信道组有可能使用不同的频点资源的情况。此时，UE如何上报BSR进行资源请求，以下通过实例3到实例4进行阐述。
假设当前业务1对应目标ID1，业务2对应目标ID2，业务3对应目标ID3，目标ID1，可以使用频点f1，f2上的资源，其中逻辑信道组1使用f1上的资源，逻辑信道组2使用f2上的资源；目标ID2可以使用频点f2，f3上的资源，其中逻辑信道组1使用f2上的资源，逻辑信道组2使用f3上的资源，目标ID3可以使用频点f3，f4上的资源，其中逻辑信道组1使用f3上的资源，逻辑信道组2使用f4上的资源。本具体实施例三包括以下两个实例。
实例3
此时，UE1需要进行业务类型1的广播发送，首先UE1在Sidelink UE Information中需要上报目标ID1可用的频点f1、f2相关的 v2x-DestinationInfoList，上报内容如表4所示，表4是根据实例3的表一。
表4
Figure PCTCN2018114225-appb-000001
此时根据Destination index的序列化规则可以知道表5中的内容，表5是根据实例3的表二。
表5
Destination Index0 Destination Index1 Destination Index2
{f1,Destination ID1} {f2,Destination ID1} {f2,Destination ID1}
同时基站会根据UE的上报信息，为UE配置对应频点的资源，之后通过RRC Reconfiguration消息告诉UE1。后续，UE可以上报BSR为目标ID1请求资源，假设共需要DataSize大小的资源，此时UE内部AS层根据业务需求，将Data Size的数据划分成Buffer Size1+Buffer Size2两个拥有不同PPPP的数据包，其中Buffer Size1通过LCG1发送，Buffer Size2通过LCG2发送，且之前UE1自行判断得出对于目标ID1，LCG1与f1关联，LCG2与f2关联。此时UE针对这两个不同PPPP的数据包，分别上报BSR，如表6所示，表6是根据实例3的表三。
表6
Figure PCTCN2018114225-appb-000002
基站接收到上报信息后，得知对于UE1的目标ID1，应为其在f1上分配Buffer Size1的资源，在f2上分配Buffer Size2的资源。
实例4
此时，UE1需要进行业务类型1和业务类型2的广播发送，首先UE1在Sidelink UE Information中需要上报目标ID1和目标ID2可用的频点f1，f2，f3相关的v2x-DestinationInfoList，如表7所示，表7是根据实例4的表四。
表7
Figure PCTCN2018114225-appb-000003
此时根据Destination Index的序列化规则可以知道表8中的内容，表8是根据实例4的表五。
表8
Destination Index0 Destination Index1 Destination Index2 Destination Index3 Destination Index4
{f1,Destination ID1} {f2,Destination ID1} {f2,Destination ID2} {f3,Destination ID2} {f3,Destination ID3}
同时基站会根据UE的上报信息，为UE配置对应频点的资源，之后通过RRC Reconfiguration消息告诉UE1。后续，UE1可以上报BSR为目标ID1和目标ID2请求资源，假设目标ID1共需要Data SizeA大小的资源，目标ID2共需要Data SizeB的资源，此时UE内部AS层根据业务需求，将Data SizeA的数据划分成Buffer Size1+Buffer Size2两个不同PPPP的数据包，将Data SizeB的数据划分成Buffer Size3+Buffer Size4两个不同PPPP的数据包。且之前UE1自行判断得出对于目标ID1，LCG1与f1关联，LCG2与f2关联；对于目标ID2，LCG1与f2关联，LCG2与f3关联。此时UE针对当前业务需求上报BSR，如表9所示，表9是根据实例4所示的表六。
表9
Figure PCTCN2018114225-appb-000004
Figure PCTCN2018114225-appb-000005
基站接收到上报信息后，得知对于UE1的目标ID1，应为其在f1上分配Buffer Size1的资源，在f2上分配Buffer Size2的资源，对于目标ID2，应为其在f2上分配Buffer Size3的资源，在f3上分配Buffer Size4的资源。
具体实施例三
本具体实施例针对一个目标ID可以使用多个频点资源，其中一个逻辑信道组内的所有逻辑信道都只能使用一个频点资源，不同的逻辑信道可以使用不同的频点资源。针对这种情况，UE上报BSR的方式将通过实例5进行阐述。
假设当前业务1对应目标ID1，目标ID1可用频点f1、f2、f3上的资源，同时，频点f1对应逻辑信道1和逻辑信道3，f2对应逻辑信道2和逻辑信道4，f3对应逻辑信道5，而逻辑信道1,2,3都在逻辑信道组1内；逻辑信道4,5都在逻辑信道组2内。该具体实施例三包括以下一个实例。
实例5
此时，UE1需要进行业务类型1的广播发送，首先，UE1在Sidelink UE Information中需要上报目标ID1可用的频点f1、f2、f3对应的v2x-DestinationInfoList，如表10所示，表10是根据实例5的表一。
表10
v2x-DestinationInfoList {f1,Destination ID1} {f2,Destination ID1} {f3,Destination ID1}
此时根据Destination Index序列化规则可以知道表11的内容，表11是根据实例5的表二。
表11
Destination Index0 Destination Index1 Destination Index2
{f1,Destination ID1} {f2,Destination ID1} {f3,Destination ID1}
同时基站会根据UE的上报信息，为UE配置对应频点的资源，之后通过RRC Reconfiguration消息告诉UE1。此时若UE需要通过逻辑信道1、2、3、4、5传输的数据包大小分别为Buffer Size1、Buffer Size2、Buffer Size3、Buffer Size4、Buffer Size5。此时UE1则应该用以下方式上报BSR，如表12所示，表12是根据实例5的表三。
表12
Destination Index0 LCG1 Buffer Size1+Buffer Size3
Destination Index1 LCG1 Buffer Size2
Destination Index1 LCG2 Buffer Size4
Destination Index2 LCG2 Buffer Size5
基站在收到上报信息后，知道对于UE1的目标ID1，应在f1上为其分配(buffer size1+buffer size3)的资源，在f2上为其分配buffer size2(针对逻辑信道组1)和buffer size4(针对逻辑信道组2)的资源，在f3上分配buffer size5的资源。
具体实施例四
本具体实施例针对一个目标ID可以使用多个频点资源，其中逻辑信道组内包含的任意逻辑信道都可以使用多个频点资源，但每个逻辑信道使用相同的频点资源集合，不同逻辑信道组可以使用相同或不同的频点资源集合。针对这种情况，UE上报BSR的方式将通过实例6到实例8进行阐述。
假设对于业务类型1，对应目标ID1，可用的频点资源集合为{f1，f2， f3，f4}。同时，逻辑信道1、2对应频点集合{f1，f2}，属于逻辑信道组1；逻辑信道3，4对应频点集合{f1，f2}，属于逻辑信道组2；逻辑信道5，6,对应频点集合{f3，f4}，属于逻辑信道组3。该具体实施例四包括以下三个实例。
实例6
此时，UE1需要进行业务类型1的广播发送，首先，UE1在Sidelink UE Information中需要上报目标ID1可用的频点f1，f2，f3，f4对应的v2x-DestinationInfoList{f1,DestinationID1}{f2,DestinationID1}{f3,Destination ID1}{f4,Destination ID1},如表13所示，表13是根据实例6的表一。
表13
v2x-DestinationInfoList {f1,DestinationID1} {f2,Destination ID1} {f3,Destination ID1} {f4,Destination ID1}
此时根据Destination Index序列化规则可以知道表14的内容，表14是根据实例6的表二。
表14
Destination Index0 Destination Index1 Destination Index2 Destination Index3
{f1,Destination ID1} {f2,Destination ID1} {f3,Destination ID1} {f4,Destination ID1}
此外，UE需要上报每个频点的资源分配比例Split Ratio{f1:f2:f3:f4}＝{2:1:2:1}。基站会根据UE1的上报信息，为UE1配置对应频点的资源，之后通过RRC Reconfiguration消息告诉UE1。若此时UE需要通过逻辑信道1，2，3，4，5，6发送的数据大小分别为Buffer Size1，Buffer Size2，Buffer Size3，Buffer Size4，Buffer Size5，Buffer Size6，那么此时UE所上报的BSR分别为表15所示的内容，表15是根据实例6的表三。
表15
Destination Index0 LCG1 (2/3)*(Buffer Size1+Buffer Size2)
Destination Index1 LCG1 (1/3)*(Buffer Size1+Buffer Size2)
Destination Index0 LCG2 (2/3)*(Buffer Size3+Buffer Size4)
Destination Index1 LCG2 (1/3)*(Buffer Size3+Buffer Size4)
Destination Index2 LCG3 (2/3)*(Buffer Size5+Buffer Size6)
Destination Index2 LCG3 (1/3)*(Buffer Size5+Buffer Size6)
基站在收到UE的BSR上报后，便可以准确地为UE1分配各个频点上的资源。
实例7
此时，UE1需要进行业务类型1的广播发送，首先，UE1在Sidelink UE Information中需要上报目标ID1可用的频点f1，f2，f3，f4对应的v2x-DestinationInfoList，如表16所示的内容，表16是根据实例7的表一。
表16
v2x-DestinationInfoList {f1,Destination ID1} {f2,Destination ID1} {f3,Destination ID1} {f4,Destination ID1}
此时，根据Destination Index序列化规则可以知道表17所示的内容，表17是根据实例7的表二。
表17
Destination Index0 Destination Index1 Destination Index2 Destination Index3
{f1,Destination ID1} {f2,Destination ID1} {f3,Destination ID1} {f4,Destination ID1}
此外，UE需要上报每个逻辑信道内的频点优先级(f1>f2,f3>f4适用于各个逻辑信道)以及对应于各个频点的split data size,{LCH1,LCH2,LCH3,LCH4,LCH5,LCH6}＝{SplitDataSize1,SplitDataSize2,SplitDataSize3,SplitDataSize4,SplitDataSize4,SplitDataSize5,SplitDataSize6}(每个逻辑信道的SplitDataSize也可以设为同一个值)，基站 会根据UE1的上报信息，为UE1配置对应频点的资源，之后通过RRC Reconfiguration消息告诉UE1。若此时UE1需要通过逻辑信道1，2，3，4，5，6发送的数据大小分别为Buffer Size1,Buffer Size2,Buffer Size3,Buffer Size4,Buffer Size5,Buffer Size6(假设所有的Buffer Size值大于SplitDataSize值)。那么此时UE1所上报的BSR分别为表18所示的内容，表18是根据实例7的表三。
表18
Figure PCTCN2018114225-appb-000006
基站在收到UE的BSR上报后，便可以准确地为UE1分配各个频点上的资源。
实例8
此时UE1需要进行业务类型1的广播发送，假设此时对于业务类型1，对应的锚点频点为f1，其余可用频点集合为{f2，f3，f4},那么首先UE上报Sidelink UE Information时，只需要在f1对应的v2x-DestinationInfoList中包含Destination ID1的指示信息，则为{f1，Destination ID1}，同时也需要上报Destination ID1对应的其他可选频点集合信息{DestinationID1，[f2，f3，f4]}，基站在收到上报信息后，会相应的为UE1配置{f1，f2，f3，f4}上的资源，之后UE上报BSR时，仅需通过上报关于锚点频点f1的BSR{0，LCG1， Buffer Size}，基站便会根据上报，在各个可选频点(包括锚点频点){f1，f2，f3，4}上分配共Buffer Size大小的资源。
具体实施例五
本具体实施例针对于任意逻辑信道只能使用一个频点资源的情况，UE上报的BSR方式将通过实例9进行阐述。
假设，对于业务类型一，对应目标ID1，对于目标ID1，可用的频点集合为{f1,f2,f3}
其中，逻辑信道1对应频点f1，逻辑信道2对应频点f2，逻辑信道3对应频点f3。该具体实施例五包括以下一个实例。
实例9
此时UE1需要进行业务类型1的广播发送，首先UE在Sidelink UE Information中上报对应的v2x-DestinationInfoList{f1，Destination ID1}{f2，Destination ID2}{f3，Destination ID3}，此时，根据Destination Index序列化规则可以得到Destiantion Index0＝{f1，Destination ID1}、Destination Index1＝{f2，Destination ID1}、Destination Index2＝{f3，Destination ID1}，基站在收到上报信息后，为UE1分配相应的资源。后续，UE1在上报BSR时，直接以逻辑信道为单位进行上报。那么此时，上报的格式应为BSR1＝{0,LCH1,Buffer Size1}、BSR2＝{1,LCH2,Buffer Size2}、BSR3＝{2,LCH3,Buffer Size3}，基站在接收到UE1的BSR上报后，便可以为UE1分配相应频点上的资源了。
具体实施例六
本具体实施例针对于任意逻辑信道可以使用一个频点集合的情况，UE上报BSR的方式将通过实例10进行阐述。
假设，对于业务类型一，对应目标ID1，对于目标ID1，可用的频点集 合为{f1,f2,f3}，其中，逻辑信道1对应{f1,f2}，逻辑信道2对应{f2,f3}，逻辑信道3对应{f1,f2,f3}，此时对于目标ID1，逻辑信道1，对应的锚点频点为f1；目标ID1，逻辑信道2，对应的锚点频点为f2；目标ID1，逻辑信道3，对应的锚点频点为f1。该具体实施例六包括以下一个实例。
实例10
此时UE1需要进行业务类型1的广播发送，首先UE1在Sidelink UE information中仅在f1对应的v2x-DestinationInfoList上报Destination ID1和LCH1，格式为{f1，Destination ID1，LCH1}，在f2对应的v2x-DestinationInfoList上报Destination ID1和LCH2，格式为{f2，Destination ID1，LCH2}，在f3对应的v2x-DestinationInfoList上报Destination ID1和LCH3，格式为{f3，Destination ID1，LCH3}。另外UE1仍需上报一组目标ID和逻辑信道对应的其他可选频点集合信息以及split的指示。具体地，此时，UE1仍需上报{Destination ID1，LCH1，[f2]}，{DestinationID1，LCH2，[f3]}，{DestinationID1，LCH3，[f2，f3]}，同时根据Destination Index的序列化规则可以得到Destination Index0＝{f1，Destination ID1}、Destination Index1＝{f2，Destination ID1}、Destination Index2＝{f3，Destination ID1}，基站在接收到UE1的上报信息后，为UE1分配对应频点上的资源。后续，UE1可以如下仅通过锚点频点上报BSR、BSR0＝{0,LCH1,Buffer Size1}BSR1＝{1,LCH2,Buffer Size2}BSR2＝{2,LCH3,Buffer Size3}，基站接收到BSR上报后，可以为UE1分配所有可选频点上的资源，具体地，对于LCH1，基站在{f1,f2}上共分配Buffer Size1的资源；对于LCH2,基站在{f2,f3}上共分配Buffer Size2的资源；对于LCH3，基站在{f1,f2,f3}上共分配Buffer Size3的资源。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当 然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
实施例二
在本实施例中还提供了一种请求资源的装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
根据本发明的另一个实施例，还提供了一种请求资源的装置，包括：
第一获取模块，配置为获取逻辑信道组中对应相同频点或锚点频点的缓存大小buffer size；
第一发送模块，配置为发送Sidelink BSR至第二通信节点，其中，所述Sidelink BSR包含以下至少之一：所述相同频点或锚点频点对应的目标索引；所述逻辑信道组标识或逻辑信道标识；所述缓存大小。
根据本发明的另一个实施例，还提供了一种请求资源的装置，包括：
第二获取模块，配置为获取逻辑信道中对应于一个或多个频点的缓存大小buffer size，其中，所述逻辑信道使用一个或多个频点；
第二发送模块，配置为依据所述一个或多个的频点分别对应的目标索引上报Sidelink BSR，其中，所述Sidelink BSR中包括该逻辑信道中，使用该频点的缓存数值大小。
根据本发明的另一个实施例，还提供了一种处理资源请求的装置，其 中，包括：
第一接收模块，配置为接收第一通信节点上报的Sidelink BSR，其中，所述Sidelink BSR中包括以下信息至少之一：逻辑信道组中一个或多个逻辑信道，使用的相同频点或锚点频点对应的目标索引；所述逻辑信道组标识或逻辑信道标识；所述相同频点或锚点频点的缓存大小；
分配模块，配置为依据所述Sidelink BSR为所述第一通信节点在各个频点上分配资源。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例三
根据本发明的另一个实施例，还提供了一种处理器，所述处理器用于运行程序，其中，所述程序运行时执行上述可选实施例任一项中所述的方法。
实施例四
根据本发明的另一个实施例，还提供了一种存储介质，其中，所述存储介质包括存储的程序，其中，所述程序运行时执行上述可选实施例任一项中所述的方法。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模 块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机 实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述，仅为本发明的较佳实施例而已，并非用于限定本发明的保护范围。

Claims (26)

  1. 一种请求资源的方法，包括：
    第一通信节点获取逻辑信道组中对应相同频点或锚点频点的缓存大小buffer size；
    第一通信节点发送直通链路缓存状态报告Sidelink BSR至第二通信节点，其中，所述Sidelink BSR包含以下至少之一：
    所述相同频点或锚点频点对应的目标索引；
    所述逻辑信道组标识或逻辑信道标识；
    所述缓存大小。
  2. 根据权利要求1所述的方法，其中，在第一通信节点上报Sidelink BSR之前，所述第一通信节点接收第二通信节点配置或预先约定的频点信息包括以下至少之一：
    直通链路Sidelink可用频点信息；
    支持数据分流或支持数据复制的频点个数；
    各个数据分流频点上的分流比split ratio；
    对应于逻辑信道的一个或多个分流数据量大小split data size，其中，所述split data size是所述逻辑信道的数据分流到某个频点上的最大数据传输量；
    Sidelink逻辑信道和/或Sidelink逻辑信道组和/或目标标识，与一个或多个频点的映射信息；
    频点优先级；
    对应于目标标识和/或目标标识的锚点频点信息。
  3. 根据权利要求2所述的方法，其中，第一通信节点上报Sidelink BSR至第二通信节点之前，所述方法还包括以下至少之一：
    所述第一通信节点根据以下信息至少之一确定使用的频点个数，和/或 各个频点上的数据传输量：可用频点信息；分流数据量大小；分流比；支持数据分流或支持数据复制的频点个数；频点的优先级；
    所述第一通信节点确定对应于数据复制的承载的以下信息至少之一：使用的频点个数，所述承载对应的逻辑信道和频点的映射关系。
  4. 根据权利要求2的方法，其中，接收第二通信节点配置或预配置的频点信息之前，所述方法还包括：
    所述第一通信节点向第二通信节点上报与每个目标标识或逻辑信道对应的以下参数至少之一：
    数据率data rate；
    可靠度等级reliability level；
    近距离通信数据分组优先级PPPP信息。
  5. 根据权利要求1所述的方法，其中，第一通信节点上报Sidelink BSR至第二通信节点之前，所述方法还包括：
    所述第一通信节点检测到与任一频点对应的逻辑信道有数据需要发送，该频点对应的逻辑信道之前没有数据需要发送的情况下，触发所述第一通信节点进行Sidelink BSR上报。
  6. 根据权利要求3所述的方法，其中，所述第一通信节点根据以下信息至少之一确定使用的频点个数，和/或各个频点上的数据传输量：可用频点信息；分流数据量大小；分流比；支持数据分流或支持数据复制的频点个数；频点的优先级，包括以下至少之一：
    当逻辑信道的缓存大小data size小于所述分流数据量大小split data size的情况下，所述第一通信节点选择第一频点传输数据；
    当逻辑信道的缓存大小data size大于所述分流数据量大小split data size的情况下，所述第一通信节点使用所述第一频点传输所述分流数据量大小split data size对应的数据，选择可用频点中的其他频点传输剩余的数据量大 小的数据，其中，所述其他频点中的每个频点传输数据量不超过所述分流数据量大小；
    所述第一通信节点依据所述逻辑信道的缓存大小，和分流比确定各个频点传输的数据量。
  7. 根据权利要求6所述的方法，其中，所述第一通信节点通过以下方式选择所述第一频点和/或所述其他频点：
    所述第一通信节点根据各个频点的优先级从高到低顺序选择数据分流使用的频点。
  8. 根据权利要求1所述的方法，其中，第一通信节点上报Sidelink BSR至第二通信节点之前，所述方法还包括：
    所述第一通信节点在直通链路终端信息SidelinkUEInformation中仅上报所述锚点频点对应的目标标识.。
  9. 根据权利要求1所述的方法，其中，第一通信节点上报Sidelink BSR至第二通信节点之前，所述第一通信节点向第二通信节点发送以下信息至少之一：
    目标标识；逻辑信道组和/或逻辑信道对应的可用频点信息，其中，所述可用频点信息包含支持被所述目标标识使用的锚点频点，和/或可选频点信息；
    目标标识；逻辑信道组和/或逻辑信道对应的数据分流指示信息。
  10. 根据权利要求1所述的方法，其中，逻辑信道组中存在多个逻辑信道的情况下，在各个逻辑信道上统计对应的相同频点或锚点频点的缓存大小buffer size之和。
  11. 根据权利要求1所述的方法，其中，第一通信节点上报Sidelink BSR至第二通信节点，包括：
    所述第一通信节点依据所述锚点频点对应的目标索引上报所述BSR。
  12. 一种请求资源的方法，包括：
    第一通信节点获取逻辑信道中对应于一个或多个频点的缓存大小buffer size，其中，所述逻辑信道使用一个或多个频点；
    依据所述一个或多个的频点分别对应的目标索引上报Sidelink BSR，其中，所述BSR中包括该逻辑信道中，使用该频点的缓存数值大小。
  13. 根据权利要求12所述的方法，其中，依据所述一个或多个的频点分别对应的目标索引上报Sidelink BSR，包括：
    所述第一通信节点在SidelinkUEInformation中上报每个频点对应的v2x-Destination Info List时，将目标ID与各个逻辑信道的对应关系同时上报。
  14. 根据权利要求13所述的方法，其中，在所述目标ID存在对应于不同逻辑信道的锚点频点的情况下，所述第一通信节点在Sidelink UE Information中上报每个频点对应的v2x-Destination Info List包括：
    所述第一通信节点在SidelinkUEInformation中，仅在每个逻辑信道的锚点频点对应的v2x-Destination Info List上报目标ID。
  15. 一种处理资源请求的方法，包括：
    第二通信节点接收第一通信节点上报的Sidelink BSR，其中，所述Sidelink BSR中包括以下信息至少之一：逻辑信道组中一个或多个逻辑信道，使用的相同频点或锚点频点对应的目标索引；所述逻辑信道组标识或逻辑信道标识；所述相同频点或锚点频点的缓存大小；
    依据所述Sidelink BSR为所述第一通信节点在各个频点上分配资源。
  16. 根据权利要求15所述的方法，其中，第二通信节点接收第一通信节点上报的Sidelink BSR之前，所述第二通信节点为所述第一通信节点配置或预先约定的频点信息包括以下至少之一：
    Sidelink可用频点信息；
    支持数据分流或支持数据复制的频点个数；
    各个数据分流频点上的分流比split ratio；
    对应于逻辑信道的一个或多个分流数据量大小split data size，其中，所述split data size是所述逻辑信道的数据分流到某个频点上的最大数据传输量；
    Sidelink逻辑信道和/或Sidelink逻辑信道组和/或目标标识，与一个或多个频点的映射信息；
    频点优先级；
    对应于目标标识和/或目标标识的锚点频点信息。
  17. 根据权利要求16的方法，其中，所述第二通信节点为所述第一通信节点配置或预先约定频点信息之前，所述第二通信节点接收第一通信节点上报的与每个车联网目标标识或逻辑信道对应的以下参数至少之一：
    数据率data rate；
    可靠度等级reliability level；
    近距离通信数据分组优先级PPPP信息。
  18. 根据权利要求15所述的方法，其中，第二通信节点接收第一通信节点上报的Sidelink BSR之前，所述第二通信节点接收所述第一通信节点发送的以下信息至少之一：
    目标标识；逻辑信道组和/或逻辑信道对应的可用频点信息，其中，所述可用频点信息包含支持被所述目标标识使用的锚点频点，和/或可选频点信息；
    目标标识；逻辑信道组和/或逻辑信道对应的数据分流指示信息。
  19. 根据权利要求18所述的方法，其中，第二通信节点接收第一通信节点上报的Sidelink BSR之前，所述方法还包括：
    接收所述第一通信节点的SidelinkUEInformation，其中，所述 SidelinkUEInformation中仅包括所述锚点频点对应的目标标识，其中，所述目标标识信息用于标识目标标识。
  20. 根据权利要求19所述的方法，其中，依据所述Sidelink BSR为所述第一通信节点在各个频点上分配资源，包括：
    所述第二通信节点接收，所述第一通信节点依据锚点频点对应的目标索引上报的BSR；
    所述第二通信节点执行以下步骤至少之一：依据所述BSR中的目标索引获取目标标识，获取所述目标标识对应的可用频点信息；所述第二通信节点依据所述数据分流指示信息确定是否使用所述可用频点信息中的频点；
    所述第二通信节点在确定需要使用可用频点信息中的频点的情况下，确定待分配资源的频点，在所述待分配资源的频点中分配资源。
  21. 根据权利要求15所述的方法，其中，依据所述Sidelink BSR为所述第一通信节点在各个频点上分配资源，包括：
    所述第二通信节点接收，所述第一通信节点依据多个频点对应的多个目标索引上报的BSR；
    所述第二通信节点在所述多个频点之间分配资源。
  22. 一种请求资源的装置，包括：
    第一获取模块，配置为获取逻辑信道组中对应相同频点或锚点频点的缓存大小buffer size；
    第一发送模块，配置为发送Sidelink BSR至第二通信节点，其中，所述Sidelink BSR包含以下至少之一：所述相同频点或锚点频点对应的目标索引；所述逻辑信道组标识或逻辑信道标识；所述缓存大小。
  23. 一种请求资源的装置，包括：
    第二获取模块，配置为获取逻辑信道中对应于一个或多个频点的缓存 大小buffer size，其中，所述逻辑信道使用一个或多个频点；
    第二发送模块，配置为依据所述一个或多个的频点分别对应的目标索引上报Sidelink BSR，其中，所述Sidelink BSR中包括该逻辑信道中，使用该频点的缓存数值大小。
  24. 一种处理资源请求的装置，包括：
    第一接收模块，配置为接收第一通信节点上报的Sidelink BSR，其中，所述Sidelink BSR中包括以下信息至少之一：逻辑信道组中一个或多个逻辑信道，使用的相同频点或锚点频点对应的目标索引；所述逻辑信道组标识或逻辑信道标识；所述相同频点或锚点频点的缓存大小；
    分配模块，配置为依据所述Sidelink BSR为所述第一通信节点在各个频点上分配资源。
  25. 一种存储介质，所述存储介质包括存储的程序，其中，所述程序运行时执行上述权利要求1至21任一项中所述的方法。
  26. 一种处理器，所述处理器用于运行程序，其中，所述程序运行时执行上述权利要求1至21任一项中所述的方法。
PCT/CN2018/114225 2017-11-16 2018-11-06 请求资源的方法及装置，处理资源请求的方法及装置 WO2019096034A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/764,645 US11647418B2 (en) 2017-11-16 2018-11-06 Resource request method and device, method and device for processing resource request
MX2020005158A MX2020005158A (es) 2017-11-16 2018-11-06 Metodo y dispositivo de solicitud de recursos, metodo y dispositivo para procesar la solicitud de recursos.

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711141257.9A CN109803385B (zh) 2017-11-16 2017-11-16 请求资源的方法及装置，处理资源请求的方法及装置
CN201711141257.9 2017-11-16

Publications (1)

Publication Number Publication Date
WO2019096034A1 true WO2019096034A1 (zh) 2019-05-23

Family

ID=66539386

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/114225 WO2019096034A1 (zh) 2017-11-16 2018-11-06 请求资源的方法及装置，处理资源请求的方法及装置

Country Status (4)

Country Link
US (1) US11647418B2 (zh)
CN (1) CN109803385B (zh)
MX (1) MX2020005158A (zh)
WO (1) WO2019096034A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107223360B (zh) * 2017-04-28 2021-10-08 北京小米移动软件有限公司 一种发送缓存状态的方法及装置
WO2019160321A1 (en) * 2018-02-13 2019-08-22 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving duplicated data in wireless communication system
US20210168840A1 (en) * 2018-04-04 2021-06-03 Lenovo (Beijing) Limited Buffer status report for packet duplication
EP3912368A1 (en) * 2019-01-18 2021-11-24 FRAUNHOFER-GESELLSCHAFT zur Förderung der angewandten Forschung e.V. Groupcast procedures for v2x
US11678334B2 (en) * 2019-03-29 2023-06-13 Charter Communications Operating, Llc Enhancement of configured grant communications in a wireless network
WO2020209565A1 (ko) * 2019-04-07 2020-10-15 엘지전자 주식회사 무선통신시스템에서 bsr에 관련된 ue의 동작 방법
CN114051705B (zh) * 2019-04-08 2024-04-26 汉尼拔Ip有限责任公司 多面板传输中推导准共位假设的方法及相关装置
CN114257989A (zh) * 2020-09-23 2022-03-29 展讯通信（上海）有限公司 资源请求方法、资源配置方法及相关产品

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170127251A1 (en) * 2015-11-04 2017-05-04 Lg Electronics Inc. Method for transmitting a sidelink buffer status reporting in a d2d communication system and device therefor

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102183333B1 (ko) * 2014-08-08 2020-11-26 주식회사 아이티엘 단말간 통신을 지원하는 무선 통신 시스템에서 버퍼상태보고 전송 방법 및 장치
CN107534829B (zh) * 2015-04-01 2021-03-23 三星电子株式会社 用于在d2d通信系统中处理优先级的方法和装置
CN106664713A (zh) * 2015-06-23 2017-05-10 华为技术有限公司 一种资源分配方法、ue及基站
US10321353B2 (en) * 2015-09-23 2019-06-11 Electronics And Telecommunications Research Institute Operation methods of communication node supporting direct communications in network
EP3354061B1 (en) * 2015-09-24 2020-12-09 LG Electronics Inc. Method for transmitting a buffer status report in a d2d communication system and device therefor
WO2017073944A1 (en) * 2015-10-27 2017-05-04 Lg Electronics Inc. Method for triggering a sidelink buffer status reporting in a d2d communication system and device therefor
EP3487239B1 (en) * 2016-08-12 2023-11-15 Huawei Technologies Co., Ltd. Semi-static transmission method and apparatus
CN111149405A (zh) * 2017-09-27 2020-05-12 瑞典爱立信有限公司 实现副链路多载波发送的方法
US11019625B2 (en) * 2017-09-28 2021-05-25 Qualcomm Incorporated Enhancement of MAC signaling for network-assisted V2X resource scheduling in PC5 multi-carrier operation

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170127251A1 (en) * 2015-11-04 2017-05-04 Lg Electronics Inc. Method for transmitting a sidelink buffer status reporting in a d2d communication system and device therefor

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2", 3GPP TS 36. 300, vol. RAN WG2, no. V14.4.0, 25 September 2017 (2017-09-25) - 30 September 2017 (2017-09-30), XP051337303 *
ASUSTEK: "Discussion on Relay UE serving multiple sidelinks for one Remote UE", 3GPP TSG-RAN WG2 MEETING #93 R2-161182, vol. RAN WG2, 15 February 2016 (2016-02-15) - 19 February 2016 (2016-02-19), XP051055155 *

Also Published As

Publication number Publication date
US11647418B2 (en) 2023-05-09
MX2020005158A (es) 2020-11-18
CN109803385B (zh) 2023-04-14
CN109803385A (zh) 2019-05-24
US20200288344A1 (en) 2020-09-10

Similar Documents

Publication Publication Date Title
WO2019096034A1 (zh) 请求资源的方法及装置，处理资源请求的方法及装置
WO2020221148A1 (zh) Ue信息的报告方法、车联网资源配置方法及装置
US20240098769A1 (en) Methods and systems for configuring mapping restrictions for one or more logical channels
JP6952710B2 (ja) 車両用通信におけるＱｏＳ実装のための改良メカニズム
WO2017133501A1 (zh) 车联网业务拥塞控制的方法及装置
EP3567907B1 (en) Information feedback method and apparatus
WO2017041355A1 (zh) 一种控制v2x业务传输的方法及装置
WO2018171563A1 (zh) 一种数据反馈资源的确定方法及装置
WO2018095156A1 (zh) 一种v2x网络资源信息指示方法及基站
WO2018188585A1 (zh) V2x资源配置方法、装置和相关设备、计算机存储介质
WO2016176965A1 (zh) 资源分配的方法和装置
WO2016206291A1 (zh) 车联网中车辆的管理方法及装置
WO2017076037A1 (zh) 车联网v2x业务的发送方法及装置
CN107333334B (zh) 副链路半持续调度的配置方法和装置
WO2016206289A1 (zh) 车联网中车辆的管理方法及装置
WO2016176970A1 (zh) 资源配置的方法和装置
WO2016070555A1 (zh) 资源的获取、配置方法及装置，资源池的配置方法及装置
JP2016519523A (ja) Ｄ２ｄ発見方法及び基地局、ユーザ装置
WO2019153234A1 (zh) 一种数据传输方法和装置
WO2019096275A1 (zh) Pc5载频选择方法以及装置、设备和基站
WO2017036342A1 (zh) 一种发送数据包的方法及装置
WO2019157918A1 (zh) 数据包传输、资源分配方法及装置、数据传输方法、终端
WO2016106713A1 (zh) 一种车联网传输资源调度方法及装置
WO2020164481A1 (zh) 一种终端装置识别方法及装置
WO2017133417A1 (zh) 数据信道子帧的指示方法及装置

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: 18879063

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 23/09/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18879063

Country of ref document: EP

Kind code of ref document: A1