WO2020034904A1 - 用户设备的控制方法、基站的控制方法以及用户设备 - Google Patents

用户设备的控制方法、基站的控制方法以及用户设备 Download PDF

Info

Publication number
WO2020034904A1
WO2020034904A1 PCT/CN2019/099981 CN2019099981W WO2020034904A1 WO 2020034904 A1 WO2020034904 A1 WO 2020034904A1 CN 2019099981 W CN2019099981 W CN 2019099981W WO 2020034904 A1 WO2020034904 A1 WO 2020034904A1
Authority
WO
WIPO (PCT)
Prior art keywords
scheduling request
configuration
configuration information
request configuration
logical channel
Prior art date
Application number
PCT/CN2019/099981
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 EP19850136.3A priority Critical patent/EP3840429B1/en
Priority to MX2021001724A priority patent/MX2021001724A/es
Priority to US17/265,792 priority patent/US20210258989A1/en
Priority to AU2019322270A priority patent/AU2019322270A1/en
Publication of WO2020034904A1 publication Critical patent/WO2020034904A1/zh

Links

Images

Classifications

    • 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/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • 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
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/40—Resource management for direct mode communication, e.g. D2D or sidelink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/535—Allocation or scheduling criteria for wireless resources based on resource usage policies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/004—Transmission of channel access control information in the uplink, i.e. towards network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/02—Inter-networking arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface
    • 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

Definitions

  • the present invention relates to the field of wireless communication technologies, and more particularly, the present invention relates to a method for controlling user equipment, a method for controlling a base station, and user equipment.
  • V2X Vehicle wireless communication technology
  • X represents any object that interacts with the vehicle.
  • X mainly includes cars, people, and traffic.
  • V2X communication has higher requirements on delay and reliability.
  • Sidelink is a D2D (device to device) communication mode.
  • the existing LTE sidelink supports V2X communication.
  • a sidelink that supports V2X communication can be called a V2X sidelink.
  • V2X communication will also be supported.
  • One way is to support LTE sidelink in the NR system, and the other way is to build NR's own sidelink. Through these two methods, the NR system can support V2X communication.
  • sidelink In the sidelink communication mode that carries V2X communication services, sidelink has its proprietary sidelink logical channel. When data arrives on the sidelink logical channel of the UE, it will trigger the UE to send a scheduling request on the Uu port to notify the base station to communicate with Sidelink. Allocate resources on the wireless interface, so as to carry out short-distance direct communication between cars, people and roads.
  • the scheduling request sent on the Uu interface is based on a general scheduling request configuration, that is, the scheduling request configuration used is the same no matter what kind of service arrives. In the NR system, however, this is improved.
  • the scheduling request sent by the UE on the Uu interface is configured based on the logical channel.
  • the base station configures corresponding scheduling request resources according to the priority of the logical channel. In this way, the scheduling request triggered by the arrival of high-priority services can use more efficient scheduling request resources for sending scheduling requests. In this way, the UE can report the scheduling request of the high-priority service in time, thereby avoiding the delay caused by the scheduling request.
  • the scheduling request configuration to be used for the triggered scheduling request is a problem to be solved.
  • the arriving data is a V2X service with a low latency requirement
  • how to efficiently report a scheduling request is also a problem that needs to be solved.
  • the present invention proposes a solution to the above problems. Specifically, the present invention provides a method for controlling user equipment, a method for controlling a base station, and user equipment.
  • a method for controlling user equipment including: the user equipment receives scheduling request configuration information related to a side link sent by a network side and / or a base station side; and Performing the scheduling request configuration information of the scheduling request related to the side link, wherein the scheduling request configuration information includes a scheduling request configuration ID or a specific scheduling request configuration.
  • the scheduling request configuration ID is a scheduling request process configuration information ID or a scheduling request resource configuration information ID.
  • the scheduling request configuration information when the scheduling request configuration ID is the scheduling request process configuration information ID, the scheduling request configuration information includes: the maximum number of times a scheduling request is allowed to be sent and the time period during which the scheduling request is prohibited from being sent, in When the scheduling request configuration ID is the scheduling request resource configuration information ID, the scheduling request configuration information includes: the maximum number of sending allowed scheduling requests, the length of time that the sending of scheduling requests is prohibited, the period and offset information of the scheduling requests , And PUCCH resource information.
  • the scheduling request configuration information includes the specific scheduling request configuration
  • the specific scheduling request configuration is one or more scheduling request configurations
  • each of the scheduling request configurations includes : The maximum allowed number of sending dispatch requests, the length of time for which the dispatch request is forbidden, the period and offset information of the dispatch request, PUCCH resource information, and information related to the bandwidth part BWP.
  • the scheduling request configuration information is provided corresponding to each side link logical channel group or each priority included in each side link logical channel group.
  • the scheduling request configuration selected based on the scheduling request configuration information is applied to the V2X service.
  • the scheduling request configuration selected based on the scheduling request configuration information is applied to the V2X service.
  • the side link communication mode For other services, random access is used for scheduling requests.
  • a method for controlling a user equipment including: the user equipment receives a scheduling request including a scheduling request configuration ID or a specific scheduling request configuration sent by a network side and / or a base station side Configuration information; based on the received scheduling request configuration information, performing a selection process for selecting a scheduling request configuration for a scheduling request related to a side link in accordance with at least one of the following principles; and based on the selected scheduling Requesting configuration to perform a scheduling request related to a side link, wherein the principles include: Principle 1, randomly selecting a scheduling request configuration among existing scheduling request configurations of the user equipment; Principle 2, the selected scheduling request The scheduling request prohibition timer corresponding to the configuration is not started or running; Principle 3: The selected scheduling request configuration exists or corresponds to a valid PUCCH resource; Principle 4. The priority of the logical channel corresponding to the selected scheduling request configuration, It is equivalent to the priority of the side link logical channel; and Principle 5, the selected scheduling request allocation The resource corresponding to the scheduling
  • the control method when a scheduling request related to a side link is triggered or before it is triggered, if there is a pending scheduling request, it will The scheduling request related to the side link is cancelled, and if there is no pending scheduling request, the user equipment executes the selection process.
  • a user equipment comprising: a processor; and a memory storing instructions; wherein the instructions, when executed by the processor, perform control of the user equipment according to a context method.
  • a method for controlling a base station including: generating scheduling request configuration information related to a side link; sending the scheduling request configuration information to a user equipment; and the user equipment based on receiving Performing the scheduling request configuration information of the scheduling request related to the side link to the base station, wherein the scheduling request configuration information includes a scheduling request configuration ID or a specific scheduling request configuration.
  • FIG. 1 is a flowchart illustrating a method 100 for controlling a user equipment according to an embodiment of the present invention.
  • FIG. 2 is a flowchart illustrating a user equipment control method 200 according to an embodiment of the present invention.
  • FIG. 3 is a flowchart showing a method 300 for controlling a base station according to an embodiment of the present invention.
  • FIG. 4 is a block diagram showing a user equipment 40 according to an embodiment of the present disclosure.
  • the NR mobile communication system and its subsequent evolved versions are used as an example application environment, and a base station and a UE device supporting NR are taken as examples to describe a plurality of embodiments according to the present invention in detail.
  • the present invention is not limited to the following embodiments, but can be applied to more other wireless communication systems.
  • the UE In order to provide the base station with data in the sidelink buffer area for transmission, the UE performs a sidelink BSR process.
  • a scheduling request will be triggered.
  • the scheduling request is used to request resources from the base station for transmission of new data.
  • an SR When an SR is triggered, it can be considered a pending SR until this SR is canceled.
  • the scheduling request can be transmitted on the PUCCH. Therefore, in order to transmit the scheduling request, a scheduling request resource configuration is needed, which contains information about the time and frequency of the PUCCH resource used to send the scheduling request, such as the period, offset, and PRB.
  • the UE During the transmission of the scheduling request, the UE will start the Sr-prohibittimer scheduling request prohibition timer, which is used to prohibit the UE from sending scheduling requests for a period of time to avoid sending frequent scheduling requests, and the UE will count the number of sending scheduling requests. It is recorded by the variable SR_COUNTER.
  • Sr-TransMax the maximum number of dispatch requests
  • the UE can continue to send dispatch requests. Once SR_COUNTER is not less than Sr-TransMax, the UE cannot send dispatch requests.
  • the scheduling request process needs to be configured with the following information:
  • Sr-prohibittimer schedules the duration of the request to prohibit sending timer
  • This scheduling request configuration information may be called scheduling request process configuration information (schedulingrequestconfig).
  • scheduling request process configuration information (schedulingrequestconfig).
  • each scheduling request process configuration information has its corresponding ID (schedulingRequestId).
  • the configuration information of the logical channel may include an ID of the scheduling request process configuration information, so that the logical channel and the scheduling request process configuration information are associated with each other.
  • This scheduling request configuration information may be referred to as scheduling request configuration information corresponding to the logical channel.
  • scheduling request resource configuration information may include an ID (schedulingRequestId) of the scheduling request process configuration information, thereby associating the scheduling request resource configuration information with the scheduling request process configuration information.
  • the UE can determine the scheduling request configuration information corresponding to one logical channel, and then determine the scheduling request resource configuration information corresponding to the scheduling request configuration information. Once both information is determined, the scheduling corresponding to the logical channel is then determined. The configuration information is requested. Therefore, it can be considered that the scheduling request configuration information thus determined is the scheduling request configuration information corresponding to the logical channel.
  • the UE will use the scheduling request configuration corresponding to the logical channel to send the corresponding scheduling request.
  • each scheduling request resource configuration information also has its corresponding ID (schedulingRequestResourceId).
  • a scheduling request configuration information may include two pieces of information: scheduling request resource configuration information (schedulingrequestresourceconfig), and scheduling request process configuration information (schedulingrequestconfig).
  • schedulingrequestresourceconfig is included in PUCCH-config
  • Each PUCCH-config is configured based on BWP, so schedulingrequestresourceconfig is also configured based on BWP.
  • the PUCCH resource contained in schedulingrequestresourceconfig refers to the PUCCH resource on the BWP to which the schedulegregrequestresourceconfig belongs, not the PUCCH resource on any BWP.
  • Each scheduling request configuration has a corresponding variable SR_COUNTER. If an SR is triggered and no other pending SR corresponds to the same SR configuration as the SR configuration of the triggered SR, then the UE will set the SR_COUNTER Set to 0.
  • a pending SR if no valid PUCCH resource is allocated to the SR, the UE will perform a random access procedure on the spcell and cancel the pending SR.
  • variable SR_COUNTER is less than sr-TransMax and sr-ProhibitTimer is not running at the time of SR transmission, then it indicates that the physical layer is at a valid PUCCH for SR
  • the SR signal is sent on the resource and sr-ProhibitTimer is started.
  • sidelink and V2X sidelink in this article can be used interchangeably.
  • the configuration information not related to the sidelink in this article refers to the configuration information provided for the UE and the base station to communicate at the Uu port, and may also be referred to as general configuration information.
  • the configuration information related to sidelink refers to the configuration information provided for achieving sidelink communication.
  • FIG. 1 is a flowchart illustrating a method 100 for controlling a user equipment according to an embodiment of the present invention.
  • step S101 the user equipment receives the scheduling request configuration information related to the side link sent by the network side and / or the base station side.
  • the scheduling request configuration information sent by the network side and / or the base station side may include a scheduling request configuration ID or a specific scheduling request configuration.
  • the scheduling request configuration ID may be a scheduling request process configuration information (schedulingRequestID) ID or a scheduling request resource configuration information (schedulingRequestResourceId) ID.
  • the scheduling request configuration information is a specific scheduling request configuration
  • the specific scheduling request configuration may be one or more specific scheduling request configurations, and each specific scheduling request configuration includes: the maximum allowed sending times of the scheduling request, prohibit The duration of sending the scheduling request, the period and offset information of the scheduling request, PUCCH resource information, and information related to the bandwidth part BWP.
  • the scheduling request configuration information may include: a maximum allowed number of sending times of the scheduling request and a time period for prohibiting sending the scheduling request.
  • the scheduling request configuration information may include: the maximum number of sending allowed scheduling requests, the length of time that the scheduling request is prohibited from being sent, the period and offset information of the scheduling request, and PUCCH resource information .
  • step S102 a scheduling request related to a side link is performed based on the received scheduling request configuration information.
  • FIG. 2 is a flowchart illustrating a method 200 for controlling a user equipment according to an embodiment of the present invention.
  • the user equipment receives scheduling request configuration information including a scheduling request configuration ID or a specific scheduling request configuration sent by the network side and / or the base station side.
  • the scheduling request configuration ID may be a scheduling request process configuration information (schedulingRequestID) ID or a scheduling request resource configuration information (schedulingRequestResourceId) ID.
  • the specific scheduling request configuration may be one or more specific scheduling request configurations.
  • step S202 based on the received scheduling request configuration information, the user equipment executes a selection process for scheduling request configuration according to at least one of the following principles, and selects a scheduling request related to a side link through the above selection process. Scheduling request configuration.
  • the above principles include: Principle 1, randomly select a scheduling request configuration among the existing scheduling request configurations of the user equipment; Principle 2, the scheduling request prohibition timer corresponding to the selected scheduling request configuration is not started or running; Principle 3 1.
  • the selected scheduling request configuration exists or corresponds to a valid PUCCH resource; principle 4.
  • the priority of the logical channel corresponding to the selected scheduling request configuration is equivalent to the priority of the side link logical channel; and principle 5.
  • the scheduling request resource corresponding to the selected scheduling request configuration arrives earliest.
  • step S203 the user makes a scheduling request related to the side link to the base station based on the selected scheduling request configuration.
  • FIG. 3 is a flowchart showing a method 300 for controlling a base station according to an embodiment of the present invention.
  • the base station In step S301, the base station generates scheduling request configuration information related to the side link.
  • the scheduling request configuration information may include a scheduling request configuration ID or a specific scheduling request configuration.
  • the content of the scheduling request configuration information is the same as the scheduling request configuration information in the control method 100 described with reference to FIG. 1, and thus repeated descriptions thereof are omitted here.
  • step S302 the base station sends the scheduling request configuration information to the user equipment.
  • step S303 the user equipment makes a scheduling request related to the side link to the base station based on the received scheduling request configuration information.
  • the UE receives configuration information sent from the network side / base station side.
  • the configuration information includes configuration information related to sidelink or V2X sidelink, and also includes information related to scheduling configuration.
  • the UE receives a reconfiguration message sent by the network side / base station side, which contains configuration information related to the sidelink, such as SL-CommConfig, which contains the configuration of common transmission resources, commuTxResources, for sidelink transmission.
  • the sending resource is set to the scheduling mode, then it also contains the configuration information related to the scheduling request, which is used for the scheduling request.
  • the configuration information related to the scheduling request may be the following manner or selection.
  • the configuration information related to the scheduling request may include a scheduling request configuration ID.
  • the scheduling request configuration ID may be an ID (schedulingRequestID) of the scheduling request process configuration information described above, or may be an ID (schedulingRequestResourceId) of the scheduling request resource configuration information described above.
  • the specific configuration information corresponding to the scheduling request configuration ID is included in the general configuration information, that is, the configuration information not related to the sidelink configuration.
  • the scheduling request configuration information includes the ID of the scheduling request configuration information, so that the UE can uniquely identify the scheduling request configuration information corresponding to each ID.
  • the UE when the UE receives one or more IDs of the scheduling request configuration information in the configuration information related to the sidelink, the UE can correspondingly identify the scheduling request configuration information corresponding to each ID, and thus is used in the SR process triggered by the sidelink BSR.
  • the UE is actually configured with the following information:
  • Information 1 The maximum number of allowed transmissions. This information is used in the scheduling request process. In the scheduling request process using the scheduling request configuration, the information specifies the maximum number of allowed transmissions.
  • Message 2 The length of the time when the scheduling request is forbidden to be sent.
  • the UE sends a scheduling request once, it will start a timer for preventing the scheduling request from being sent to avoid frequent sending of scheduling requests.
  • the duration of the sending prohibition of the scheduling request regularizer is set to the duration of prohibiting sending the scheduling request indicated in the scheduling request configuration information.
  • the related information of the PUCCH resource used for transmitting the scheduling request is not displayed in the configuration.
  • the UE may further determine a PUCCH resource for sending a scheduling request triggered by a sidelink BSR based on the configured schedulingRequestID.
  • the specific method may be that, on the currently activated / working BWP, the UE confirms / determines whether there is a SchedulingRequestResourceConfig including the configured schedulingRequestID in the SchedulingRequestResourceConfig included in the configured PUCCH.
  • a SchedulingRequestResourceConfig contains the configured schedulingRequestID
  • the PUCCH resource configured in the SchedulingRequestResourceConfig can be used to send a scheduling request triggered by a sidelink BSR
  • the UE can be considered to have no valid PUCCH resources for sending sidelink BSR-triggered scheduling requests.
  • the UE can select the scheduling request configuration or PUCCH resources as described in Embodiment 4, and can also trigger random access Entry process, and preferably, cancel pending SR.
  • the UE is actually configured with the following information:
  • Information 1 The maximum number of allowed transmissions. This information is used in the scheduling request process. In the scheduling request process using the scheduling request configuration, this information specifies the maximum number of allowed transmissions.
  • Message 2 The length of the time when the scheduling request is forbidden to be sent.
  • the UE sends a scheduling request once, it will start a timer for preventing the scheduling request from being sent to avoid frequent sending of scheduling requests.
  • the duration of the schedule sending prohibition sending scheduler is set to the duration of the schedule sending prohibition indicated in the scheduling request configuration information;
  • PUCCH resources contains information such as PRB information and PUCCH format.
  • the above information can be used to determine the resources for sending the PUCCH, as well as the settings of the timer and the maximum number of transmissions during the sending process.
  • schedulingRequestResourceId can correspond to a SchedulingRequestResourceConfig
  • SchedulingRequestResourceConfig is included in PUCCH-config and PUCCH-config is configured for each BWP
  • SchedulingRequestResourceConfig is also configured for each BWP, so if the UE only When receiving the schedulingRequestResourceId in the sidelink configuration, it cannot be determined that this schedulingRequestResourceId corresponds to the SchedulingRequestResourceConfig on which BWP the network side is configured.
  • the network side In order to determine the SchedulingRequestResourceConfig corresponding to the schedulingRequestResourceId, one way is that the network side further provides BWP-related information while providing the schedulingRequestResourceId information, such as the BWP ID. Because in the configuration information not related to the sidelink, the network side can configure the UE with multiple BWPs, and these BWPs have corresponding BWP IDs, so the BWP ID can uniquely determine which BWP is the UE, and then determine the schedulingRequestResourceId provided. Corresponding SchedulingRequestResourceConfig.
  • the UE can only send scheduling requests on the activated BWP. Therefore, at the time when the SR is triggered by the sidelink, although the UE can determine the SchedulingRequestResourceConfig according to the BWP ID and the schedulingRequestResourceId, and further determine the PUCCH resource to send the scheduling request, and the settings of the timer and the maximum number of transmissions, the UE still needs to determine the PUCCH resource belongs Whether the BWP is active / UE is working BWP.
  • the BWP to which the PUCCH resource / SchedulingRequestResourceConfig belongs does not belong to the currently active / working BWP, then it can be considered that the UE does not have a valid PUCCH resource for sending a sidelink BSR-triggered scheduling request, and the UE can perform scheduling on the scheduling as described in Embodiment 4.
  • Requesting configuration or PUCCH resources for selection can also trigger a random access process, and preferably, cancel pending SR.
  • the configuration information related to the scheduling request may include specific scheduling request configuration.
  • the network side can provide one or more groups of scheduling request configurations, and each configuration includes at least the information 1 to information 4 mentioned above, and the related information of the BWP.
  • the configuration of the scheduling request triggered by sidelink BSR can be completely different from the scheduling request triggered by non-sidelink BSR, so that the scheduling request triggered by sidelink BSR can be more flexibly managed.
  • the configuration information may be defaulted.
  • the UE can select an appropriate configuration based on the existing scheduling request configuration (that is, the configuration related to the scheduling request provided by the network side in the configuration not related to the sidelink). The selection method is described in Example 4.
  • Embodiment 2 provides the configuration information of the scheduling request based on the sidelink logical channel group.
  • the configuration information related to the sidelink sent by the network side may also include information about the sidelink logical channel group, such as logicalChGroupInfoList. This cell provides logic according to the number of the logical channel group from small to large (or large to small). Information about the priority of a channel group.
  • LogicalChGroupInfoList :: SEQUENCE (SIZE (1..maxLCG)) OF SL-PriorityList
  • the network side can provide the configuration information of the scheduling request for each logical channel group while providing the priority information of the logical channel group.
  • For specific content of the configuration information refer to option 1 and option 2 in Embodiment 1.
  • This provided scheduling request configuration information may be referred to as (corresponding to / related to) the scheduling request configuration information of the logical channel group.
  • the specific configuration method may be, for example, the scheduling request configuration information provided by the network side is schedulingrequestID.
  • each row of information in the list can contain a schedulingrequestID. Since each row in the logicalChGroupInfoList corresponds to a logical channel group, the schedulingrequestID contained in each row can be considered to correspond to the logical channel group. Scheduling request configuration information.
  • LogicalChGroupInfoList :: SEQUENCE (SIZE (1..maxLCG)) OFInformation-1
  • the network side can also provide a list of SR configuration information in a new cell, such as SRconfigInfoList.
  • the list is from small to large according to the number of the logical channel group.
  • Each row in the list contains a schedulegrequestID. Since each row of the SRconfigInfoList corresponds to a logical channel group, the configuration of the scheduling request corresponding to the schedulingrequestID of each row, or the configuration of the scheduling request contained in each row can be referred to as the configuration information of the scheduling request corresponding to the logical channel group. .
  • LCG index Scheduling request configuration LCG1 SchedulingrequestID-1 LCG 2 schedulingrequestID-2 LCG 3 schedulingrequestID-3
  • SRconfigInfoList :: SEQUENCE (SIZE (1..maxLCG)) OF SL-SchedulingRequest
  • the sidelink BSR is triggered by the arrival of data from a certain sidelink logical channel, and the logical channel belongs to a certain logical channel group, it can be considered that a certain logical channel group triggered the sidelink BSR, or that the logical channel group corresponds to the sidelink
  • the BSR therefore, in the scheduling request process triggered by the sidelink BSR, the configuration information corresponding to the scheduling request of the logical channel group that triggered the sidelink BSR can be used.
  • logicalChGroupInfoList or SRconfigInfoList if the configuration of the scheduling request provided by the row is the default, or the logical channel group does not have a corresponding scheduling request configuration, then the logical channel group can use the logical channel group before it.
  • Before it” or “after it” can refer to the logical channel group number that is smaller than the current logical channel group number, but the logical channel group that is closest to the current logical channel group number, or greater than the current logical channel group number. The logical channel group number, but the logical channel group closest to the current logical channel group number.
  • the UE may also select a configuration of a scheduling request by itself, and the specific selection method is described in Embodiment 4.
  • any sidelink logical channel that has data to transmit will also generate a sidelink BSR, which will also trigger a scheduling request. Then at this time, according to the logical channel group whose buffer value in the sidelink BSR is not empty or non-zero, the corresponding scheduling request configuration is selected for the triggered scheduling request. If the buffer value of multiple logical channel groups is not empty or non-zero, then among the priorities contained in all logical channel groups, the logical channel group to which the highest priority belongs is selected, and its corresponding scheduling request is configured for The triggered dispatch request.
  • Embodiment 3 The difference between Embodiment 3 and Embodiment 2 is that the configuration information of the scheduling request is provided based on the priority information contained in the logical channel group.
  • the network side allocates one or more priorities to each logical channel group, and the UE can associate logical channels with these priorities by itself. Therefore, when allocating priorities for each logical channel group on the network side, it can provide configuration information of the scheduling request corresponding to each priority at the same time.
  • the configuration information of this scheduling request may be referred to as the configuration of the scheduling request corresponding to the priority.
  • LogicalChGroupInfoList :: SEQUENCE (SIZE (1..maxLCG)) OF SL-priorityList
  • the scheduling request configuration used in the scheduling request process triggered by the sidelink BSR is triggered.
  • its corresponding priority corresponds to the scheduling request configuration. That is, when a logical channel corresponding to a certain priority triggers a sidelink BSR due to data arrival, and then triggers a scheduling request, a scheduling request configuration corresponding to the priority is used in the scheduling request.
  • the UE may select a scheduling request configuration by itself. For a specific selection method, see Embodiment 4.
  • any sidelink logical channel that has data to transmit will also generate a sidelink BSR.
  • This sidelink BSR will also trigger a scheduling request.
  • the corresponding scheduling request configuration is selected for the triggered scheduling request. If the buffer values of multiple logical channel groups are not empty or non-zero, then the highest priority contained in these logical channel groups is selected, and the corresponding scheduling request is configured to trigger the scheduling request.
  • the UE may select a scheduling request configuration for the scheduling request process.
  • the UE may make a selection based on one or more of the following principles.
  • the existing scheduling request configuration can include the following information:
  • Information 1 The maximum number of allowed transmissions. This information is used in the scheduling request process. In the scheduling request process using the scheduling request configuration, the information specifies the maximum number of allowed transmissions.
  • Message 2 The length of the time when the scheduling request is forbidden to be sent.
  • the UE sends a scheduling request once, it will start a timer for preventing the scheduling request from being sent to avoid frequent sending of scheduling requests.
  • the duration of the sending prohibition of the scheduling request regularizer is set to the duration of prohibiting sending the scheduling request indicated in the scheduling request configuration information.
  • PUCCH resources which include information such as PRB information and the format of the PUCCH.
  • Information 1 and information 2 are contained in schedulegregrequestconfig, while information 3 and information 4 and the index scheduleRequestId corresponding to information 1 and information 2 (that is, corresponding to schedulegregreconfig) are contained in schedulegrequestresourceconfig, and the index of schedulegregrequestresourceconfig is scheduleRequestResourceId.
  • schedulingrequestresourceconfig is related to BWP, each BWP has its corresponding schedulingrequestresourceconfig.
  • the UE has the following different processing methods based on the selected content when selecting.
  • the content selected by the UE is schedulingrequestconfig, or schedulingRequestId corresponding to schedulingrequestconfig, that is, the configuration information including at least information one and information two is selected.
  • the UE may randomly select an existing schedulingrequestconfig. However, the UE needs to further determine the PUCCH resource for sending the scheduling request. Otherwise, even if schedulingrequestconfig is selected, it may not be able to send scheduling requests through PUCCH because it does not have valid PUCCH resources on the currently working BWP.
  • the UE can determine the selected range.
  • the schedulingRequestID selected by the UE should be included in the PUCCH configuration on the currently active / working BWP of the UE, specifically in the SchedulingRequestResourceConfig included in the PUCCH configuration, that is, the UE is from the currently active / working BWP
  • a schedulingRequestID is randomly selected from the schedulingRequestID contained in the SchedulingRequestResourceConfig included in the above PUCCH configuration.
  • the content selected by the UE is SchedulingRequestResourceConfig, or schedulingRequesResourcetId corresponding to SchedulingRequestResourceConfig, that is, the configuration information including at least information one, two, three, and four is selected.
  • the UE may randomly select a SchedulingRequestResourceConfig from an existing SchedulingRequestResourceConfig.
  • the UE may select from the SchedulingRequestResourceConfig included in the PUCCH configuration on the currently activated / working BWP.
  • the selected SchedulingRequestResourceConfig or schedulingrequestconfig can be considered as the scheduling request configuration corresponding to the scheduling request triggered by the sidelink BSR, and then used in the subsequent scheduling request process.
  • the selected scheduling request configuration may have been adopted by other scheduling request processes.
  • logical channel 1 has its corresponding scheduling request configuration 1.
  • a BSR is generated and triggers a scheduling request.
  • the scheduling request adopts the corresponding scheduling request configuration of logical channel 1, the variable SR_COUNTER starts to count, and sr-ProhibitTimer may stop during running or running timeout.
  • scheduling request configuration 1 should not be selected as a scheduling request for sidelink BSR triggering, because during sr-ProhibitTimer running, the UE cannot send scheduling requests based on scheduling request configuration 1, ie the UE is prohibited Send a scheduling request on the PUCCH resource corresponding to scheduling request configuration 1.
  • scheduling request configuration 1 can be selected as the scheduling request for sidelink BSR triggering.
  • SR_COUNTER is not less than sr-TransMax, it means that the scheduling request sending based on scheduling request configuration 1 has reached the maximum number of transmissions, and the UE will not be allowed to send scheduling requests, so scheduling request configuration 1 should not be selected Used for scheduling requests triggered by sidelink BSR.
  • scheduling request configuration 1 can be selected as the scheduling request triggered by sidelink BSR.
  • SR_COUNTER is less than sr-TransMax
  • the so-called effective PUCCH resource refers to a PUCCH resource configured on a currently activated / working BWP.
  • the scheduling request configuration selected by the UE should be associated with a valid PUCCH resource.
  • the content selected by the UE is scheduledulingrequestconfig, or schedulingRequestId corresponding to scheduledgregrequestconfig, that is, configuration information including at least information one and information two is selected, then on the currently activated / working BWP, there is a PUCCH resource associated with the scheduledgregrequestconfig.
  • the specific association method may be that the SchedulingRequestResourceConfig configured on the currently activated / working BWP has a schedulingRequestId including the schedulegrequestconfig.
  • the configuration information including at least one, two, three, and four is selected. Then the selected SchedulingRequestResourceConfig is configured on the currently active / working BWP.
  • the specific association method may be that the SchedulingRequestResourceConfig includes a PUCCH resource configured on the current BWP.
  • the selected scheduling request configuration has a corresponding logical channel priority that is equivalent to the priority of the sidelink logical channel.
  • the "sidelink logical channel” here is a logical channel that triggers a sidelink BSR, and the selected scheduling request is configured for a scheduling request triggered by the sidelink BSR.
  • the logical channel corresponding to the configuration of the selected scheduling request refers to the logical channel configured with the scheduling request, that is, the scheduling request configuration associated with the logical channel.
  • the specific association method may be included in the logical channel configuration.
  • This logical channel is a non-sidelink logical channel, which has a corresponding priority. If there are multiple logical channels using the SR configuration, and the priorities corresponding to the multiple logical channels are different, the highest priority or the lowest priority, or the intermediate value among them can be selected as the corresponding logical channel for the scheduling request configuration. Priority.
  • the logical channel here refers to the sidelink logical channel that triggers the scheduling request, and the priority corresponding to the logical channel.
  • a sidelink logical channel that triggers a scheduling request refers to a sidelink logical channel that triggers a scheduling request because data arrives on the logical channel and triggers a sidelink BSR. Therefore, the sidelink logical channel is called a sidelink logical channel that triggers a scheduling request.
  • the UE associates corresponding priorities for the sidelink logical channels.
  • “Equivalent priority” here may mean that the priorities of the two are the same, or that the difference between the priorities of the two does not exceed a certain value, or is not less than a certain value.
  • the priority of the sidelink logical channel and all logical channels is compared, and the scheduling request configuration corresponding to the logical channel with the smallest gap between the two is selected.
  • the priority of logical channel 1 is 3, and the corresponding scheduling request is configured as scheduling request configuration 1.
  • the priority of logical channel 2 is 5, and the corresponding scheduling request is configured as scheduling request configuration 2.
  • the priority is 3.
  • the sidelink logical channel 3 generates a sidelink BSR due to data arrival, which triggers a scheduling request. Since the priority of the sidelink logical channel 3 is the same as the priority of logical channel 1, both 3, then the UE selects the corresponding one of the logical channel 1.
  • Scheduling request configuration that is, scheduling request configuration 1 is the scheduling request configuration of the scheduling request triggered by sidelink logical channel 2, and the scheduling request configuration 2 corresponding to logical channel 2 is not selected because of the priority of logical channel 2 and sidelink logical channel 3. Have different priorities.
  • the UE still chooses scheduling request configuration 1 in this case, because the priority gap between logical channel 1 and sidelink logical channel 3 is 1, which is less than the priority of logical channel 2 and sidelink logical channel 3. Level gap, so the configuration of the scheduling request corresponding to the logical channel with the smallest gap is selected.
  • any sidelink logical channel that has data to transmit will also generate a sidelink BSR.
  • This sidelink BSR will also trigger a scheduling request.
  • the logical channel corresponding to the priority is selected, and the logical channel is corresponding
  • the scheduling request is configured to trigger the scheduling request. If there are multiple logical channel groups where the buffer value is not empty or non-zero in the sidelink BSR, the highest priority among these multiple logical channel groups can be selected.
  • the SR configuration is included in the scheduling request resource configuration, corresponding to the SR configuration, the time when the scheduling request resource arrives is earlier than the time when the scheduling request resource in the scheduling request resource configuration including any other SR configuration arrives, then the SR configuration is selected . This means that the UE can send a scheduling request as soon as possible.
  • This principle actually implies that the scheduling request resource PUCCH corresponding to the selected scheduling request configuration must be a valid PUCCH, as described in Principle 3. From a time perspective, the effective PUCCH resource will arrive first.
  • the selected scheduling request configuration can be considered as the scheduling request configuration corresponding to the scheduling request triggered by the sidelink BSR, and thus used in the subsequent scheduling request process.
  • the UE uses the maximum number of transmissions included in the selected scheduling request configuration to set the maximum number of transmissions of the scheduling request when sending the SR triggered by the sidelink BSR; the selected scheduling request configuration includes To set the duration of the SR's disabling request timer.
  • Embodiment 5 when a sidelink BSR triggers an SR, when the SR is triggered, or before, if there is a pending SR, preferably, the pending SR is not triggered by the sidelink BSR, then the SR cancellation triggered by sidelink BSR; if there is no pending SR, then the UE selection process described in Embodiment 4 is performed, and a scheduling request is made based on the selected scheduling request configuration, or optionally, according to Embodiment 1-3 The scheduling request is executed based on the scheduling request configured on the network side.
  • the scheduling request configuration determined in the foregoing embodiments 1-5 can be used only for the V2X service, and for other services performed in the sidelink communication mode, only random access is used to complete the scheduling request. .
  • a V2X sidelink BSR When data arrives on the sidelink logical channel, if the sidelink logical channel is used for V2X services, then a V2X sidelink BSR can be generated.
  • the scheduling request triggered by the V2X sidelink BSR will use the determination of the corresponding scheduling request in the above embodiments 1-5. Configure and instruct the physical layer to send a scheduling request; if this sidelink logical channel is not used for V2X services, then a sidelink BSR can be generated.
  • a scheduling request triggered by a sidelink BSR will trigger a random access process, and optionally cancel the pending SR.
  • a sidelink BSR When data arrives at the sidelink logical channel, then a sidelink BSR can be generated. Generated sidelink dispatch request triggered by BSR.
  • the sidelink BSR is triggered by a logical channel related to V2X, or the scheduling request is triggered by a logical channel related to V2X, then the corresponding scheduling request configuration in the foregoing embodiments 1-5 is determined, and the physical Layer sends a scheduling request;
  • a sidelink BSR can be generated, and a scheduling request triggered by a sidelink BSR will trigger a random access process, and Optional cancellation pending.
  • FIG. 4 is a block diagram showing a user equipment 40 according to an embodiment of the present disclosure.
  • the user equipment 40 includes a processor 401 and a memory 402.
  • the processor 401 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 402 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory systems.
  • the memory 402 stores program instructions. When the instruction is executed by the processor 401, the above-mentioned control method in the user equipment described in detail in the present disclosure may be executed.
  • the program running on the device according to the present invention may be a program that causes a computer to realize the functions of the embodiments of the present invention by controlling a central processing unit (CPU).
  • the program or information processed by the program may be temporarily stored in volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.
  • a program for implementing the functions of the embodiments of the present invention may be recorded on a computer-readable recording medium.
  • Corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs.
  • the so-called “computer system” herein may be a computer system embedded in the device, and may include an operating system or hardware (such as a peripheral device).
  • the "computer-readable recording medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium for a short-term dynamic storage program, or any other recording medium readable by a computer.
  • circuits designed to perform the functions described in this specification may include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the above.
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • a general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine.
  • the above circuit may be a digital circuit or an analog circuit. In the event that new integrated circuit technologies have replaced existing integrated circuits due to advances in semiconductor technology, one or more embodiments of the present invention may also be implemented using these new integrated circuit technologies.
  • the present invention is not limited to the embodiments described above. Although various examples of the embodiments have been described, the present invention is not limited thereto.
  • Fixed or non-mobile electronic equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

Landscapes

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

Abstract

本发明提供一种用户设备的控制方法、基站的控制方法以及用户设备。所述用户设备的控制方法包括：所述用户设备接收由网络侧和/或基站侧发送的与侧链路相关的调度请求配置信息；和基于接收到的所述调度请求配置信息，进行与所述侧链路相关的调度请求，其中，所述调度请求配置信息包含调度请求配置ID或者具体调度请求配置。

Description

用户设备的控制方法、基站的控制方法以及用户设备 技术领域
本发明涉及无线通信技术领域，更具体地，本发明涉及用户设备的控制方法、基站的控制方法以及用户设备。
背景技术
随着移动通信的快速增长和技术的巨大进步，世界将走向一个完全互联互通的网络社会，即任何人或任何东西在任何时间和任何地方都可以获得信息和共享数据。预计到2020年，互联设备的数量将达到500亿部，其中仅有100亿部左右可能是手机和平板电脑，其它的则不是与人对话的机器，而是彼此对话的机器。因此，如何设计系统以更好地支持万物互联是一项需要深入研究的课题。
为此，在2016年3月举行的第三代合作伙伴计划(3GPP)RAN#64次全会上，提出了新5G无线接入技术的研究课题(参见非专利文献：RP-160671 New SID Proposal：Study on New Radio Access Technology)。在该工作项目的描述中，未来新的通信制式的工作频段可扩展至100GHz，同时将至少满足增强的移动宽带业务需求、海量物联网终端的通信需求，以及高可靠性要求的业务需求等，该项目研究工作将于2018年结束。
车用无线通信技术(Vehicleto Everything，V2X)是将车辆与一切事物相连接的新一代信息通信技术，其中V代表车辆，X代表任何与车交互信息的对象，当前X主要包含车、人、交通路侧基础设施和网络。V2X通信对时延和可靠性提出了更高的要求。
Sidelink是一种D2D(device to device)通信模式，现有的LTE sidelink支持V2X通信。支持V2X通信的sidelink可以被称为V2X sidelink。在未来NR技术中，也将支持V2X通信。一种方式是在NR系统中支持LTE sidelink，另外一种方式是打造NR自己的sidelink。通过这两种方式，NR系统可以实现对V2X通信的支持。
在承载了V2X通信业务的sidelink通信模式下，sidelink有其专有的sidelink逻辑信道，当UE的sidelink逻辑信道上有数据到达时，会触发UE在Uu口发送调度请求，以通知基站对Sidelink通信的无线接口上分配资源，从而进行车、人、路之间的短距离直接通信。
在LTE系统中，Uu口上发送的调度请求是基于通用的调度请求配置，即，无论何种业务到达，采用的调度请求配置都是相同的。然而在在NR系统中，这一点得到了改进。在NR系统中，UE在Uu口上发送的调度请求是基于逻辑信道进行配置的。基站根据逻辑信道的优先级，配置相应的调度请求资源，这样高优先级的业务到达触发的调度请求可以采用更高效的调度请求资源用于发送调度请求。这样UE可以及时上报高优先级业务的调度请求，从而避免调度请求带来的时延。
因此，在NR系统中，当sidelink通信模式有数据到达时，触发的调度请求将采用何种调度请求配置是需要解决的问题。特别是当到达的数据是具有低时延要求的V2X业务时，如何高效的上报调度请求也是需要解决的问题。
发明内容
本发明针对上述问题提出了解决方案，具体地，本发明提供了用户设备的控制方法、基站的控制方法以及用户设备。
根据本发明的第一方面，提供了一种用户设备的控制方法，包括：所述用户设备接收由网络侧和/或基站侧发送的与侧链路相关的调度请求配置信息；和基于接收到的所述调度请求配置信息，进行与所述侧链路相关的调度请求，其中，所述调度请求配置信息包含调度请求配置ID或者具体调度请求配置。
优选地，在上述控制方法中，若所述调度请求配置信息包含所述调度请求配置ID，则所述调度请求配置ID为调度请求过程配置信息ID或者调度请求资源配置信息ID。
优选地，在上述控制方法中，在所述调度请求配置ID为所述调度请求过程配置信息ID时，所述调度请求配置信息包含：调度请求最大允许发送次数以及禁止发送调度请求的时长，在所述所述调度请求配置ID为所述调度请求资源配置信息ID时，所述调度请求配置信息包含： 调度请求最大允许发送次数、禁止发送调度请求的时长、调度请求的周期和偏移量信息、以及PUCCH资源信息。
优选地，在上述控制方法中，若所述调度请求配置信息包含所述具体调度请求配置，则所述具体调度请求配置为一个或者多个的调度请求配置，每个所述调度请求配置中包含：调度请求最大允许发送次数、禁止发送调度请求的时长、调度请求的周期和偏移量信息、PUCCH资源信息、以及与带宽部分BWP相关的信息。
优选地，在上述控制方法中，所述调度请求配置信息相应于每个侧链路逻辑信道组、或者各侧链路逻辑信道组中包含的每个优先级而被提供。
优选地，在上述控制方法中，在存在车用无线通信技术V2X业务的情况下，将基于所述调度请求配置信息所选择的调度请求配置应用于所述V2X业务，对于侧链路通信模式下的其他业务，采用随机接入来进行调度请求。
此外，根据本发明的第二方面，提供了一种用户设备的控制方法，包括：所述用户设备接收由网络侧和/或基站侧发送的包含调度请求配置ID或者具体调度请求配置的调度请求配置信息；基于接收到的所述调度请求配置信息，按照以下原则中的至少一个原则，来执行选择用于与侧链路相关的调度请求的调度请求配置的选择过程；和基于所选择的调度请求配置来进行与侧链路相关的调度请求，其中，所述原则包括：原则1、在所述用户设备已有的调度请求配置中随机选择一个调度请求配置；原则2、被选择的调度请求配置所对应的调度请求禁止定时器没有启动或者运行；原则3、被选择的调度请求配置存在或者对应于有效的PUCCH资源；原则4、被选择的调度请求配置所对应的逻辑信道的优先级，与侧链路逻辑信道的优先级相当；和原则5、被选择的调度请求配置所对应的调度请求资源最早到达。
优选地，在本发明的第二方面所涉及的控制方法中，在与侧链路相关的调度请求被触发时、或者被触发之前，若存在挂起(pending)的调度请求，则将与所述侧链路相关的调度请求取消，若不存在挂起(pending)的调度请求，则所述用户设备执行所述选择过程。
根据本发明的第三方面，提供了一种用户设备，包括：处理器；以及存储器，存储有指令；其中，所述指令在由所述处理器运行时执行根据上下文所述的用户设备的控制方法。
根据本发明的第四方面，提供了一种基站的控制方法，包括：生成与侧链路相关的调度请求配置信息；向用户设备发送所述调度请求配置信息；和所述用户设备基于接收到的所述调度请求配置信息，向所述基站进行与所述侧链路相关的调度请求，其中，所述调度请求配置信息包含调度请求配置ID或者具体调度请求配置。
附图说明
图1是表示基于本发明的实施例的用户设备的控制方法100的流程图。
图2是表示基于本发明的实施例的用户设备的控制方法200的流程图。
图3是表示基于本发明的实施例的基站的控制方法300的流程图。
图4是表示根据本公开实施例的用户设备40的框图。
具体实施方式
下面结合附图和具体实施方式对本发明进行详细阐述。应当注意，本发明不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本发明没有直接关联的公知技术的详细描述，以防止对本发明的理解造成混淆。
在具体描述之前，先对本发明中提到的若干术语做如下说明。除非另有指出，本发明中涉及的术语都具有下文的含义
UE User Equipment 用户设备
NR New Radio 新一代无线技术
Sidelink 侧链路
V2X Vechile to Everything 车联通信
BWP Bandwith Part 带宽部分
Sidelink BSR buffer status report sidelink缓存状态报告
下文以NR移动通信系统及其后续的演进版本作为示例应用环境，以支持NR的基站和UE设备为例，具体描述了根据本发明的多个实施方式。然而，需要指出的是，本发明不限于以下实施方式，而是可适用于更多其它的无线通信系统，。
[Sidelink BSR buffer status report sidelink缓存状态报告]
为了向基站提供用于传输的、在sidelink缓存区的数据情况，UE会进行sidelink BSR过程。
当sidlink逻辑信道有数据到达时，如果到达的数据所属的逻辑信道对应的优先级高于其他的正在进行数据传输的逻辑信道，或者当前没有数据传输，则此时会生成sidelink BSR。
此外，当Sidelink重传定时器(retx-BSR-TimerSL)超时时，任何逻辑信道有数据需要传输，也会生成sidelink BSR。
如果UE没有有效的上行资源发送生成的sidelink BSR，那么将会触发调度请求。
[调度请求(Scheduling Request，SR)]
调度请求是用来向基站请求资源用于新数据的传输。当SR被触发时，可以被认为是pending(挂起)SR，直到这个SR被取消。
调度请求可以在PUCCH上进行传输，因此为了传输调度请求，需要有调度请求资源配置，里面包含了用于发送调度请求的PUCCH资源的时间和频率的信息，例如周期、偏移和PRB等。
调度请求在传输的过程中，UE会启动Sr-prohibittimer调度请求禁止发送定时器，用来禁止UE在一段时间内发送调度请求，以避免频繁的发送调度请求，以及UE会统计发送调度请求的次数，通过变量SR_COUNTER来记录，当SR_COUNTER小于Sr-TransMax(调度请求最大发送次数)时，UE还可以继续发送调度请求一旦SR_COUNTER不小于Sr-TransMax时，UE将不能再发送调度请求。
因此，调度请求过程需要配置如下信息：
Sr-prohibittimer调度请求禁止发送定时器的时长；
Sr-TransMax调度请求最大发送次数。
这种调度请求配置信息可以称为调度请求过程配置信息 (schedulingrequestconfig)。为了区别不同的调度请求过程配置信息，每个调度请求过程配置信息有其对应的ID(schedulingRequestId)。
在逻辑信道的配置信息中，可以包含一个调度请求过程配置信息的ID，从而把逻辑信道与该调度请求过程配置信息相互关联在一起。这个调度请求配置信息可以称为相应于该逻辑信道的调度请求配置信息。
此外，由于在调度请求资源配置信息(schedulingrequestresourceconfig)中，可以包含一个调度请求过程配置信息的ID(schedulingRequestId)，从而把调度请求资源配置信息和调度请求过程配置信息关联在一起。
因此，UE可以通过确定相应于一个逻辑信道的调度请求配置信息，进而确定相应于该调度请求配置信息的调度请求资源配置信息，一旦这两个信息都确定了，那么相应于该逻辑信道的调度请求配置信息就确定了。因此可以认为这样确定的调度请求配置信息是相应于该逻辑信道的调度请求配置信息。
如果由于该逻辑信道的数据到达触发了BSR进而触发了调度请求，那么UE将采用的相应于该逻辑信道的调度请求配置来发送相应的调度请求。
此外，为了区别不同的调度请求资源配置信息(schedulingrequestresourceconfig)，每个调度请求资源配置信息也有其对应的ID(schedulingRequestResourceId)。
总之，一个调度请求配置信息(SR configuration)可以包括两部分信息：调度请求资源配置信息(schedulingrequestresourceconfig)、和调度请求过程配置信息(schedulingrequestconfig)。
schedulingrequestconfig
Figure PCTCN2019099981-appb-000001
schedulingrequestresourceconfig
Figure PCTCN2019099981-appb-000002
其中，schedulingrequestresourceconfig是包含在PUCCH-config中的
Figure PCTCN2019099981-appb-000003
而每个PUCCH-config是基于BWP进行配置的，所以schedulingrequestresourceconfig也是基于BWP进行配置的，schedulingrequestresourceconfig中包含的PUCCH资源是指该schedulingrequestresourceconfig所属于的BWP上的PUCCH资源，而不是任意BWP上的PUCCH资源。
每一个调度请求配置(SR configuration)都有一个对应的变量SR_COUNTER，如果一个SR被触发了，并且没有其他的pending SR与这个被触发的SR的SR configuration对应相同的SR configuration，那么UE会将SR_COUNTER设置为0。
在SR传输时刻，只有那些处于激活的BWP上配置的PUCCH资源才被认为是有效的资源。
针对一个pending SR如果没有有效的PUCCH资源被配置给该SR，那么UE会在spcell上进行随机接入过程，并且取消这个pending SR。
如果存在有效的PUCCH，那么对于这个pending SR对应的SR configuration，如果变量SR_COUNTER小于sr-TransMax，并且在SR传 输的时刻sr-ProhibitTimer没有在运行，那么指示物理层在一个有效的用于SR的PUCCH资源上发送SR信号，并且启动sr-ProhibitTimer。
本文中相关联的，相对应的，相应的等说法可以相互替换。
本文中sidelink和V2X sidelink两种说法可以互相替换。
本文中与sidelink无关的配置信息是指为了实现UE和基站在Uu口通信而提供的配置信息，还可以被称为通用的配置信息。与sidelink有关的配置信息是指为了实现sidelink通信而提供的配置信息。
下面，对本发明中的用户设备的控制方法进行说明，具体而言，对用户设备的与侧链路相关的调度请求控制方法进行说明。
作为一例，图1是表示基于本发明的实施例的用户设备的控制方法100的流程图。
在步骤S101中，用户设备接收由网络侧和/或基站侧发送的与侧链路相关的调度请求配置信息。
其中，由网络侧和/或基站侧发送的上述调度请求配置信息可以包含调度请求配置ID或者具体调度请求配置。例如，在调度请求配置信息包含调度请求配置ID时，该调度请求配置ID可以为调度请求过程配置信息(schedulingRequestID)ID或者调度请求资源配置信息(schedulingRequestResourceId)ID。此外，例如，在调度请求配置信息具体调度请求配置时，该具体调度请求配置可以是一个或者多个具体的调度请求配置，每个具体的调度请求配置中包含：调度请求最大允许发送次数、禁止发送调度请求的时长、调度请求的周期和偏移量信息、PUCCH资源信息、以及与带宽部分BWP相关的信息。
此外，在上述调度请求配置ID为调度请求过程配置信息ID时，调度请求配置信息可以包含：调度请求最大允许发送次数以及禁止发送调度请求的时长。在上述调度请求配置ID为调度请求资源配置信息ID时，调度请求配置信息可以包含：调度请求最大允许发送次数、禁止发送调度请求的时长、调度请求的周期和偏移量信息、以及PUCCH资源信息。
在步骤S102中，基于接收到的调度请求配置信息，进行与侧链路相关的调度请求。
此外，图2是表示基于本发明的实施例的用户设备的控制方法200的流程图。
在步骤S201中，用户设备接收由网络侧和/或基站侧发送的包含调度请求配置ID或者具体调度请求配置的调度请求配置信息。其中，调度请求配置ID可以为调度请求过程配置信息(schedulingRequestID)ID或者调度请求资源配置信息(schedulingRequestResourceId)ID。另外，，上述具体调度请求配置可以是一个或者多个具体的调度请求配置。
在步骤S202中，用户设备基于接收到的调度请求配置信息，按照以下原则中的至少一个原则，来执行调度请求配置的选择过程，通过上述选择过程来选择用于与侧链路相关的调度请求的调度请求配置。
上述原则包括：原则1、在所述用户设备已有的调度请求配置中随机选择一个调度请求配置；原则2、被选择的调度请求配置所对应的调度请求禁止定时器没有启动或者运行；原则3、被选择的调度请求配置存在或者对应于有效的PUCCH资源；原则4、被选择的调度请求配置所对应的逻辑信道的优先级，与侧链路逻辑信道的优先级相当；和原则5、被选择的调度请求配置所对应的调度请求资源最早到达。
在步骤S203中，用户基于所选择的调度请求配置，向基站进行与侧链路相关的调度请求。
接下来，对本发明中的基站的控制方法进行说明，具体而言，对基站的与侧链路相关的调度请求控制方法进行说明。
作为一例，图3是表示基于本发明的实施例的基站的控制方法300的流程图。
在步骤S301中，基站生成与侧链路相关的调度请求配置信息。其中，上述调度请求配置信息可以包含调度请求配置ID或者具体调度请求配置。关于该调度请求配置信息的内容，由于与参照图1所说明的控制方法100中的调度请求配置信息相同，因此这里省略其重复的说明。
在步骤S302中，基站向向用户设备发送上述调度请求配置信息。
进而，在步骤S303中，用户设备基于接收到的上述调度请求配置信息，向基站进行与侧链路相关的调度请求。
以下，对本发明所涉及的具体实施例进行详细说明。另外，如上所述，本发明中的实施例是为了容易理解本发明而进行的示例性说明，并不是对本发明的限定。
实施例1
UE接收从网络侧/基站侧发送的配置信息，配置信息中包含了和sidelink或者V2X sidelink相关的配置信息，其中还包含了与调度配置相关的信息。
例如，UE接收到网络侧/基站侧发送的重配置消息，其中包含了和sidelink相关的配置信息，例如SL-CommConfig，在其中包含了公共发射资源的配置commTxResources，用于sidelink的发送；如果公共发送资源被设置为调度模式，那么还包含了与调度请求相关的配置信息，用于调度请求。这里，与调度请求相关的配置信息可以是如下的方式或选择。
Option 1：与调度请求相关的配置信息可以包含调度请求配置ID。
调度请求配置ID可以是前文所述的调度请求过程配置信息的ID(schedulingRequestID)，还可以是前文所述的调度请求资源配置信息的ID(schedulingRequestResourceId)。
其中，调度请求配置ID对应的具体的配置信息包含在通用的配置信息中，即包含在与sidelink配置无关的配置信息中。这些调度请求配置信息中包含了调度请求配置信息的ID，从而使得UE能够唯一的识别每个ID对应的调度请求配置信息。
因此，当UE在sidelink相关的配置信息中接收到一个或者多个调度请求配置信息的ID时，能够相应的识别每个ID对应的调度请求配置信息，从而在sidelink BSR触发的SR过程中采用。
-当调度请求配置ID是前文所述的schedulingRequestID时，实际上UE被配置了如下信息：
信息一：最大允许发送次数，这个信息用于调度请求过程，在采用了该调度请求配置的调度请求过程中，该信息规定了最大允许发送调度请求的次数。
信息二：禁止发送调度请求的时长，当UE发送了一次调度请求后，会启动禁止发送调度请求定时器，以避免频繁的发送调度请求。在采用了该调度请求配置的调度请求过程中，该禁止发送调度请求定期器的时长被设置为调度请求配置信息中指示的禁止发送调度请求的时长。
用于发射调度请求的PUCCH资源的相关信息并没有被显示的配置。UE可以基于被配置的schedulingRequestID，进一步确定用于发送sidelink BSR触发的调度请求的PUCCH资源。具体的方法可以是，在当前激活的/工作的BWP上，UE在被配置的PUCCH中所包含的SchedulingRequestResourceConfig中确认/判断是否存在包含了被配置的schedulingRequestID的SchedulingRequestResourceConfig。
如果存在某个SchedulingRequestResourceConfig包含了被配置的schedulingRequestID，那么该SchedulingRequestResourceConfig中配置的PUCCH资源可以用于发送sidelink BSR触发的调度请求；
如果不存在这样的SchedulingRequestResourceConfig，那么可以认为UE没有有效的PUCCH资源用于发送sidelink BSR触发的调度请求，UE可以如实施例4中所述对调度请求配置或者PUCCH资源进行选择，还可以触发随机接入过程，以及优选的，取消pending SR。
-当调度请求配置ID是前文所述的schedulingRequestResourceId时，实际上UE被配置了如下信息：
信息一：最大允许发送次数，这个信息用于调度请求过程，在采用了该调度请求配置的调度请求过程中，该信息规定了最大允许发送调度请求的次数；
信息二：禁止发送调度请求的时长，当UE发送了一次调度请求后，会启动禁止发送调度请求定时器，以避免频繁的发送调度请求。在采用了该调度请求配置的调度请求过程中，该禁止发送调度请求定期器的时长被设置为调度请求配置信息中指示的禁止发送调度请求的时长；
信息三：调度请求的周期和偏移量；
信息四：PUCCH资源：包含了PRB信息，以及PUCCH的格式等信息。
上述信息可以用来确定发送PUCCH的资源，以及发送过程中定时器的设置和最大传输次数的设置。
尽管schedulingRequestResourceId能够对应一个SchedulingRequestResourceConfig，但是，由于SchedulingRequestResourceConfig又是包含在PUCCH-config中，而PUCCH-config是为每个BWP进行配置的，因此SchedulingRequestResourceConfig也是为每个BWP而进行配置的，所以，如果UE仅仅在sidelink配置中接收到schedulingRequestResourceId，是无法确定这个schedulingRequestResourceId对应的是网络侧在哪个BWP上配置的SchedulingRequestResourceConfig。为了确定schedulingRequestResourceId对应的SchedulingRequestResourceConfig，一种方式是网络侧在提供schedulingRequestResourceId信息的同时进一步提供BWP相关的信息，例如BWP ID。由于在与sidelink无关的配置信息中，网络侧可以给UE配置多个BWP的信息，这些BWP有相应的BWP ID，因此通过BWP ID，UE可以唯一地确定是哪一个BWP，进而确定被提供schedulingRequestResourceId对应的SchedulingRequestResourceConfig。
由于在任意时刻，不是所有的BWP都是被激活的，UE只能在被激活的BWP上发送调度请求。因此，在sidelink BSR触发SR的时刻，尽管UE可以根据BWP ID和schedulingRequestResourceId来确定SchedulingRequestResourceConfig，并进一步确定发送调度请求的PUCCH资源以及定时器和最大发送次数的设定，但是UE还是需要判断PUCCH资源所属的BWP是否是激活的/UE正在工作的BWP。如果该PUCCH资源/SchedulingRequestResourceConfig所属的BWP不属于在当前激活的/工作的BWP，那么可以认为UE没有有效的PUCCH资源用于发送sidelink BSR触发的调度请求，UE可以如实施例4中所述对调度请求配置或者PUCCH资源进行选择，还可以触发随机接入过程，以及优选的，取消pending SR。
Option 2：与调度请求相关的配置信息可以包含具体调度请求配置。网络侧可以提供一组或者多组调度请求配置，每个配置中至少包含了如前所述的信息一至信息四、以及BWP的相关信息。
通过这种方式，用于sidelink BSR触发的调度请求的配置可以完全不同于非sidelink BSR触发的调度请求，从而能够更灵活的管理sidelink BSR触发的调度请求。
特别的，无论是option1还是option2指示的配置信息，在实际的配置过程中，该配置信息可以缺省。那么当调度请求相关的配置信息缺省时，UE可以基于已有的调度请求的配置(即在与sidelink无关的配置中网络侧提供的关于调度请求的配置)，从中选择一个合适的配置，具体选择方法见实施例4.
实施例2
实施例2和实施例1的区别在于网络侧基于sidelink逻辑信道组提供了调度请求的配置信息。
在网络侧发送的和sidelink相关的配置信息中还可以包含sidelink逻辑信道组的相关信息，例如logicalChGroupInfoList，这个信元按照逻辑信道组的编号由小到大(或者由大到小)，提供了逻辑信道组的优先级相关的信息。
logicalChGroupInfoList
Figure PCTCN2019099981-appb-000004
LogicalChGroupInfoList：：＝SEQUENCE(SIZE(1..maxLCG))OF SL-PriorityList
SL-PriorityList信元
Figure PCTCN2019099981-appb-000005
网络侧可以在提供该逻辑信道组优先级信息的同时，为每个逻辑信道组提供调度请求的配置信息，配置信息具体内容参见实施例1中的option1和option2。
这个被提供的调度请求配置信息可以称为相应于(corresponding to/related to)该逻辑信道组的调度请求配置信息。
具体的配置方式可以是，例如网络侧提供的调度请求配置信息为schedulingrequestID。
在logicalChGroupInfoList中，在该列表中，每一行的信息中可以包含了一个schedulingrequestID，由于在logicalChGroupInfoList中的每一行对应着一个逻辑信道组，那么每一行包含的schedulingrequestID可以认为是对应于该逻辑信道组对应的调度请求配置信息。
携带调度请求配置的logicalChGroupInfoList
Figure PCTCN2019099981-appb-000006
LogicalChGroupInfoList：：＝SEQUENCE(SIZE(1..maxLCG))OF Information-1
Information-1
Figure PCTCN2019099981-appb-000007
网络侧还可以在一个新的信元中，例如SRconfigInfoList，提供一个SR配置信息列表，该列表按照逻辑信道组的编号由小到大，在该列表中的每一行中包含的内容为一个schedulingrequestID。由于SRconfigInfoList列表的每一行都对应于一个逻辑信道组，因此每一行的schedulingrequestID对应的调度请求的配置，或者每一行包含的调度请求的配置可以称为相应于该逻辑信道组的调度请求的配置信息。
SRconfigInfoList
LCG index 调度请求配置
LCG 1 SchedulingrequestID-1
LCG 2 schedulingrequestID-2
LCG 3 schedulingrequestID-3
SRconfigInfoList：：＝SEQUENCE(SIZE(1..maxLCG))OF SL-SchedulingRequest
SL-SchedulingRequest信元
Figure PCTCN2019099981-appb-000008
由于sidelink BSR是由于某个sidelink逻辑信道的数据到达而触发的，且该逻辑信道属于某个逻辑信道组，因此可以认为某个逻辑信道组触发了sidelink BSR，或者认为该逻辑信道组对应于sidelink BSR，因此，在由该sidelink BSR触发的调度请求过程中，可以采用相应于触发了本次sidelink BSR的逻辑信道组的调度请求的配置信息。
无论是在logicalChGroupInfoList还是在SRconfigInfoList中，如果该行的提供的调度请求的配置缺省，或者是该逻辑信道组没有对应的调度请求的配置，那么该逻辑信道组可以采用在它之前的逻辑信道组被提供的调度请求的配置，或则采用在它之后的逻辑信道组被提供的调度请求的配置。
这里的“在它之前”或者“在它之后”，可以是指根据逻辑信道组编号的大小，小于当前逻辑信道组编号的，但是最接近当前逻辑信道组编号的逻辑信道组，或者是大于当前逻辑信道组编号的，但是最接近当前逻辑信道组编号的逻辑信道组。
此外，当相应于该逻辑信道组的调度请求配置缺省时，还可以是UE自己选择一个调度请求的配置，具体选择方法见实施例4.
特别的，当Sidelink重传定时器(retx-BSR-TimerSL)超时时，任何sidelink逻辑信道有数据需要传输，也会生成sidelink BSR，这个sidelink BSR也会触发调度请求。那么此时可以根据sidelink BSR中buffer值不为空或者不为零的那个逻辑信道组，选择其相应的调度请求配置，用于触发的调度请求。如果有多个逻辑信道组的buffer值不为空或者不为零，那么在所有逻辑信道组所包含的优先级中，选择最高优先级所属的逻辑信道组，选择其相应的调度请求配置用于触发的调度请求。
实施例3
实施例3和实施例2的区别在于，基于逻辑信道组中包含的优先级信息来提供调度请求的配置信息。
网络侧为每个逻辑信道组分配了一个或者多个优先级priority，UE可以自行为这些priority关联逻辑信道。因此网络侧在为每个逻辑信道组分配优先级时，可以同时提供每个优先级对应的调度请求的配置信息。这个调度请求的配置信息可以称为相应于该优先级的调度请求的配置。
携带调度请求配置的logicalChGroupInfoList
Figure PCTCN2019099981-appb-000009
LogicalChGroupInfoList：：＝SEQUENCE(SIZE(1..maxLCG))OF  SL-priorityList
携带调度请求配置的SL-PriorityList信元
Figure PCTCN2019099981-appb-000010
Information-2
Figure PCTCN2019099981-appb-000011
由于sidelink BSR是由于某个sidelink逻辑信道的数据到达而触发的，且该逻辑信道与某个优先级关联，因此可以认为，在sidelink BSR触发的调度请求过程中采用的调度请求配置，为触发了该sidelink BSR的逻辑信道，其对应的优先级对应的调度请求配置。即当相应于某个优先级的逻辑信道，由于数据到达触发了sidelink BSR，并进而触发了调度请求，那么在该调度请求中采用相应于该优先级的调度请求配置。
类似的，如果相应于某个优先级的调度请求配置缺省，那么UE可以自己选择一个调度请求配置，具体选择方法见实施例4。
特别的，当Sidelink重传定时器(retx-BSR-TimerSL)超时时，任何sidelink逻辑信道有数据需要传输，也会生成sidelink BSR，这个sidelink BSR也会触发调度请求。那么此时可以根据sidelink BSR中buffer值不为空或者不为零的那个逻辑信道组所包含的最高优先级，选择其相应的调度请求配置，用于触发的调度请求。如果有多个逻辑信道组的buffer值不为空或者不为零，那么选择这些逻辑信道组中所包含的最高的优先级，选择选择其相应的调度请求配置用于触发的调度请求。
实施例4
实施例4中对用户设备选择调度请求配置的原则和过程进行说明。
当sidelink BSR触发了调度请求，那么UE可以选择调度请求配置用于该调度请求过程。
在选择的过程中，UE可以基于以下一个或多个原则进行选择。
原则1-在UE已有的调度请求配置中随机选择一个调度请求配置用 于sidelink BSR触发的调度请求。
如前所述，已有的调度请求配置可以包含以下信息：
信息一：最大允许发送次数，这个信息用于调度请求过程，在采用了该调度请求配置的调度请求过程中，该信息规定了最大允许发送调度请求的次数。
信息二：禁止发送调度请求的时长，当UE发送了一次调度请求后，会启动禁止发送调度请求定时器，以避免频繁的发送调度请求。在采用了该调度请求配置的调度请求过程中，该禁止发送调度请求定期器的时长被设置为调度请求配置信息中指示的禁止发送调度请求的时长。
信息三：调度请求的周期和偏移量。
信息四：PUCCH资源，其包含了PRB信息、以及PUCCH的格式等信息。
其中信息一和信息二包含在schedulingrequestconfig中，而信息三和信息四，以及对应信息一和信息二(即对应schedulingrequestconfig)的索引schedulingRequestId包含在schedulingrequestresourceconfig中，schedulingrequestresourceconfig的索引为schedulingRequestResourceId。此外schedulingrequestresourceconfig是与BWP有关的，每个BWP有其相应的schedulingrequestresourceconfig。
因此UE在选择的时候基于选择的内容，有以下不同的处理方式。
方式一：
UE选择的内容是schedulingrequestconfig，或者是对应schedulingrequestconfig的schedulingRequestId，即选择至少包含信息一和信息二的配置信息。
UE可以随机选择已有的schedulingrequestconfig。但是UE还需要进一步确定发送调度请求的PUCCH资源。否则，即使选择了schedulingrequestconfig，也可能由于其在当前工作的BWP上没有有效的PUCCH资源，从而无法通过PUCCH发送调度请求。
因此，UE可以确定选择的范围。被UE选择的schedulingRequestID，应该是被包含在UE当前激活的/工作的BWP上的PUCCH配置中的，具体是被包含在PUCCH配置中的SchedulingRequestResourceConfig中，，即，UE从当前激活的/工作的BWP上PUCCH配置中所包含的 SchedulingRequestResourceConfig中包含的schedulingRequestID中随机选择一个schedulingRequestID。
方式二：
UE选择的内容是SchedulingRequestResourceConfig，或者是对应SchedulingRequestResourceConfig的schedulingRequesResourcetId，即选择至少包含信息一、二、三、四的配置信息。
UE可以从已有的SchedulingRequestResourceConfig随机选择一个SchedulingRequestResourceConfig。
考虑到SchedulingRequestResourceConfig是基于BWP配置的，优选的，UE可以从当前激活的/工作的BWP上的PUCCH配置中的包含的SchedulingRequestResourceConfig进行选择。
被选择的SchedulingRequestResourceConfig或者是schedulingrequestconfig可以被认为是相应于sidelink BSR触发的调度请求的调度请求配置，从而在接下来的调度请求过程中使用。
原则-2被选择的调度请求配置，其对应的调度请求禁止定时器没有启动/运行，优选的，变量SR_COUNTER小于sr-TransMax。
被选择的调度请求配置有可能已经被其他的调度请求过程所采用，例如逻辑信道1有其相应的调度请求配置1，当逻辑信道1有数据到达时，生成了BSR，进而触发了调度请求，那么该调度请求采用逻辑信道1相应的调度请求配置，变量SR_COUNTER开始计数，以及sr-ProhibitTimer可能在运行或者运行超时而停止。
如果sr-ProhibitTimer正在运行，那么调度请求配置1则不应该被选为用于sidelink BSR触发的调度请求，因为在sr-ProhibitTimer运行期间，UE无法基于调度请求配置1发送调度请求，即UE被禁止在调度请求配置1对应的PUCCH资源上发送调度请求。
如果sr-ProhibitTimer已经停止，那么调度请求配置1可以被选为用于sidelink BSR触发的调度请求。
优选的，如果SR_COUNTER的值不小于sr-TransMax，说明基于调度请求配置1的调度请求发送已经达到了最大发送次数，UE将不被允许发送调度请求，所以调度请求配置1则不应该被选为用于sidelink BSR触发的调度请求。
如果SR_COUNTER的值小于sr-TransMax说明基于调度请求配置1的调度请求还可以继续发送，那么调度请求配置1可以被选为用于sidelink BSR触发的调度请求。
如果此时存在相应于逻辑信道2的调度请求配置2，且逻辑信道2并没有触发任何调度请求，那么可以认为调度请求配置2相关的sr-ProhibitTimer没有启动，以及SR_COUNTER小于sr-TransMax，那么UE可以选择调度请求配置。
原则3-被选择的调度请求配置存在或者对应于有效的PUCCH资源。
所谓有效的PUCCH资源是指在当前激活的/工作的BWP上配置的PUCCH资源。UE选择的调度请求配置应该是与有效的PUCCH资源相关联的。
如果UE选择的内容是schedulingrequestconfig，或者是对应schedulingrequestconfig的schedulingRequestId，即选择至少包含信息一和信息二的配置信息，那么在当前激活的/工作的BWP上，有PUCCH资源与该schedulingrequestconfig相关联。具体的关联方式可以是，在当前激活的/工作的BWP上被配置的SchedulingRequestResourceConfig中有包含该schedulingrequestconfig的schedulingRequestId。
如果UE选择的内容是SchedulingRequestResourceConfig，或者是对应SchedulingRequestResourceConfig的schedulingRequesResourcetId，即选择至少包含信息一，二，三，四的配置信息。那么被选择的SchedulingRequestResourceConfig是被配置在当前激活的/工作的BWP上的。具体的关联方式可以是，在SchedulingRequestResourceConfig包含了当前BWP上配置的PUCCH资源。
原则4-被选择的调度请求配置，其对应的逻辑信道的优先级，与sidelink逻辑信道的优先级相当。
这里的“sidelink逻辑信道”是触发sidelink BSR的逻辑信道，而被选择的调度请求配置用于该sidelink BSR触发的调度请求。
这里，被选择的调度请求的配置对应的逻辑信道，是指采用了该调度请求配置的逻辑信道，即与该逻辑信道关联的调度请求配置，具体的关联方式可以是在逻辑信道配置中包含了该调度请求配置的ID。这个逻 辑信道是非sidelink逻辑信道，该逻辑信道有对应的优先级。如果有多个逻辑信道都采用了该SR配置，且这多个逻辑信道对应的优先级不同，那么可以选择其中的最高优先级或者最低优先级，或者中间值作为该调度请求配置对应的逻辑信道的优先级。
Sidelink逻辑信道优先级：这里的逻辑信道是指触发调度请求的sidelink逻辑信道，以及该逻辑信道对应的优先级。其中，触发调度请求的sidelink逻辑信道是指由于该逻辑信道有数据到达触发了sidelink BSR，进而sidelink BSR触发了调度请求，因此该sidelink逻辑信道被称为触发调度请求的sidelink逻辑信道。UE为sidelink逻辑信道关联了相应的优先级。
这里的“优先级相当”可以是指两者的优先级相同，或者是两者的优先级之差不超过某个值，或者不小于某个值。
或者是sidelink逻辑信道和所有的逻辑信道的优先级相比，选择两者差距最小的那一个逻辑信道对应的调度请求配置。
例如：逻辑信道1的优先级是3，其对应的调度请求配置为调度请求配置1；逻辑信道2的优先级是5，其对应的调度请求配置为调度请求配置2；而sidelink逻辑信道3的优先级是3。
sidelink逻辑信道3由于有数据到达，生成了sidelink BSR，进而触发了调度请求，由于sidelink逻辑信道3的优先级和逻辑信道1的优先级相同，都是3，那么UE选择相应于逻辑信道1的调度请求配置，即调度请求配置1作为sidelink逻辑信道2触发的调度请求的调度请求配置，而不选择相应于逻辑信道2的调度请求配置2，是因为逻辑信道2的优先级和sidelink逻辑信道3的优先级不同。
如果逻辑信道1的优先级是4，那么这种情况下UE还是选择调度请求配置1，因为逻辑信道1和sidelink逻辑信道3的优先级差距为1，小于逻辑信道2和sidelink逻辑信道3的优先级差距，所以选择差距最小的那个逻辑信道对应的调度请求的配置。
特别的，当Sidelink重传定时器(retx-BSR-TimerSL)超时时，任何sidelink逻辑信道有数据需要传输，也会生成sidelink BSR，这个sidelink BSR也会触发调度请求。那么此时可以根据sidelink BSR中buffer值不为空或者不为零的那个逻辑信道组所包含的最高优先级做为判断依据，来选择与该优先级相当的逻辑信道，并将该逻辑信道对应的调度请求配 置用于触发的调度请求。如果在sidelink BSR中buffer值不为空或者不为零的逻辑信道组有多个，可以选择这多个逻辑信道组中最高的优先级。
原则5-被选择的调度请求配置，其对应的调度请求资源将最早到达。
由于调度请求资源配置中包含着SR配置，对应于该SR配置，调度请求资源到达的时刻比包含其他任何SR配置的调度请求资源配置中的调度请求资源到达的时刻要早，那么选择该SR配置。这意味着UE可以尽快的发送调度请求。在这个原则中实际上暗含着被选择的调度请求配置对应的调度请求资源PUCCH必须是一个有效的PUCCH，如原则3中所述。然后从时间上看，该有效的PUCCH资源将最先到达。
上述这些原则可以结合使用，例如结合原则1和原则2，当有多个备选的调度请求配置满足原则2的要求，那么结合原则1，UE可以从中随机选择一个调度请求配置；再例如结合原则3，5，UE选一个对应于最早到达的、有效的PUCCH资源的调度请求配置。在应用上述原则时，可以不存在顺序上的先后关系。
被选择的调度请求配置可以被认为是相应于sidelink BSR触发的调度请求的调度请求配置，从而在接下来的调度请求过程中使用。
基于被选择的调度请求配置，UE在发送由sidelink BSR触发的SR时，采用被选择的调度请求配置中包含的最大发送次数来设置调度请求的最大发送次数；采用被选择的调度请求配置中包含的禁止调度请求定时器时长来设置SR的禁止调度请求定时器的时长。
实施例5
实施例5和实施例4的不同在于，当sidelink BSR触发了一个SR，在该SR被触发时，或者之前，如果存在pending SR，优选的，该pending SR不是由sidelink BSR触发的，那么可以将由sidelink BSR触发的SR取消；如果不存在pending SR，那么执行实施例4中所述的UE选择的过程，并基于选择的调度请求配置进行调度请求，或者可选的，依据实施例1-3中所述的基于网络侧配置的调度请求执行调度请求。
实施例6
考虑到V2X业务的低时延要求，上述实施例1-5中所确定的调度请求配置可以仅用于V2X业务，而对于sidelink通信模式下进行的其他业务仅采用随机接入的方法完成调度请求。
具体的实施方式可以是如下的方式：
当sidelink逻辑信道有数据到达时，如果这个sidelink逻辑信道是用于V2X业务的，那么可以生成V2X sidelink BSR，V2X sidelink BSR触发的调度请求将采用上述实施例1-5中的确定相应的调度请求配置，并指示物理层发送调度请求；如果这个sidelink逻辑信道不是用于V2X业务的，那么可以生成sidelink BSR，sidelink BSR触发的调度请求将触发随机接入过程，以及可选的取消pending SR。
具体实施方式还可以是如下的方式：
当sidelink逻辑信道有数据到达时，那么可以生成sidelink BSR。生成的sidelink BSR触发的调度请求。
如果sidelink BSR是由与V2X相关的逻辑信道触发的，或者说这个调度请求是由与V2X相关的逻辑信道触发的，那么采用上述实施例1-5中的确定相应的调度请求配置，并指示物理层发送调度请求；
如果sidelink BSR不是由与V2X相关的逻辑信道触发的，或者说这个调度请求不是由与V2X相关的逻辑信道触发的，那么可以生成sidelink BSR，sidelink BSR触发的调度请求将触发随机接入过程，以及可选的取消pending SR。
此外，图4是表示根据本公开实施例的用户设备40的框图。如图4所示，该用户设备40包括处理器401和存储器402。处理器401例如可以包括微处理器、微控制器、嵌入式处理器等。存储器402例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统等。存储器402上存储有程序指令。该指令在由处理器401运行时，可以执行本公开详细描述的用户设备中的上述控制方法。
运行在根据本发明的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、 硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种用户设备的控制方法，包括：
    所述用户设备接收由网络侧和/或基站侧发送的与侧链路相关的调度请求配置信息；和
    基于接收到的所述调度请求配置信息，进行与所述侧链路相关的调度请求，
    其中，所述调度请求配置信息包含调度请求配置ID或者具体调度请求配置。
  2. 根据权利要求1所述的控制方法，其中，
    若所述调度请求配置信息包含所述调度请求配置ID，则所述调度请求配置ID为调度请求过程配置信息ID或者调度请求资源配置信息ID。
  3. 根据权利要求2所述的控制方法，其中，
    在所述调度请求配置ID为所述调度请求过程配置信息ID时，所述调度请求配置信息包含：调度请求最大允许发送次数以及禁止发送调度请求的时长，
    在所述所述调度请求配置ID为所述调度请求资源配置信息ID时，所述调度请求配置信息包含：调度请求最大允许发送次数、禁止发送调度请求的时长、调度请求的周期和偏移量信息、以及PUCCH资源信息。
  4. 根据权利要求1所述的控制方法，其中，
    若所述调度请求配置信息包含所述具体调度请求配置，则所述具体调度请求配置为一个或者多个的调度请求配置，每个所述调度请求配置中包含：调度请求最大允许发送次数、禁止发送调度请求的时长、调度请求的周期和偏移量信息、PUCCH资源信息、以及与带宽部分BWP相关的信息。
  5. 根据权利要求1所述的控制方法，其中，
    所述调度请求配置信息相应于每个侧链路逻辑信道组、或者各侧链路逻辑信道组中包含的每个优先级而被提供。
  6. 根据权利要求1～5所述的控制方法，其中，
    在存在车用无线通信技术V2X业务的情况下，将基于所述调度请求配置信息所选择的调度请求配置应用于所述V2X业务，对于侧链路通信模式下的其他业务，采用随机接入来进行调度请求。
  7. 一种用户设备的控制方法，包括：
    所述用户设备接收由网络侧和/或基站侧发送的包含调度请求配置ID或者具体调度请求配置的调度请求配置信息；
    基于接收到的所述调度请求配置信息，按照以下原则中的至少一个原则，来执行选择用于与侧链路相关的调度请求的调度请求配置的选择过程；和
    基于所选择的调度请求配置来进行与侧链路相关的调度请求，
    其中，所述原则包括：
    原则1、在所述用户设备已有的调度请求配置中随机选择一个调度请求配置；
    原则2、被选择的调度请求配置所对应的调度请求禁止定时器没有启动或者运行；
    原则3、被选择的调度请求配置存在或者对应于有效的PUCCH资源；
    原则4、被选择的调度请求配置所对应的逻辑信道的优先级，与侧链路逻辑信道的优先级相当；和
    原则5、被选择的调度请求配置所对应的调度请求资源最早到达。
  8. 根据权利要求7所述的控制方法，其中，
    在与侧链路相关的调度请求被触发时、或者被触发之前，若存在挂起(pending)的调度请求，则将与所述侧链路相关的调度请求取消，若不存在挂起(pending)的调度请求，则所述用户设备执行所述选择过程。
  9. 一种用户设备，包括：
    处理器；以及
    存储器，存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求1至8中任一项所述的控制方法。
  10. 一种基站的控制方法，包括：
    生成与侧链路相关的调度请求配置信息；
    向用户设备发送所述调度请求配置信息；和
    所述用户设备基于接收到的所述调度请求配置信息，向所述基站进行与所述侧链路相关的调度请求，
    其中，所述调度请求配置信息包含调度请求配置ID或者具体调度请求配置。
PCT/CN2019/099981 2018-08-14 2019-08-09 用户设备的控制方法、基站的控制方法以及用户设备 WO2020034904A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP19850136.3A EP3840429B1 (en) 2018-08-14 2019-08-09 Control method for user equipment and user equipment
MX2021001724A MX2021001724A (es) 2018-08-14 2019-08-09 Metodo de control para equipo de usuario, metodo de control para estacion base y equipo de usuario.
US17/265,792 US20210258989A1 (en) 2018-08-14 2019-08-09 Control method for user equipment, control method for base station, and user eqipment
AU2019322270A AU2019322270A1 (en) 2018-08-14 2019-08-09 Control method for user equipment, control method for base station, and user equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810926770.7A CN110830955B (zh) 2018-08-14 2018-08-14 用户设备的控制方法、基站的控制方法以及用户设备
CN201810926770.7 2018-08-14

Publications (1)

Publication Number Publication Date
WO2020034904A1 true WO2020034904A1 (zh) 2020-02-20

Family

ID=69525166

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/099981 WO2020034904A1 (zh) 2018-08-14 2019-08-09 用户设备的控制方法、基站的控制方法以及用户设备

Country Status (6)

Country Link
US (1) US20210258989A1 (zh)
EP (1) EP3840429B1 (zh)
CN (1) CN110830955B (zh)
AU (1) AU2019322270A1 (zh)
MX (1) MX2021001724A (zh)
WO (1) WO2020034904A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111132224B (zh) * 2018-11-01 2021-12-14 维沃移动通信有限公司 sidelink的连接控制方法、终端及网络侧设备
WO2020136868A1 (ja) * 2018-12-28 2020-07-02 富士通株式会社 端末装置、基地局装置及び無線通信システム
CN115380604A (zh) * 2020-04-09 2022-11-22 富士通株式会社 随机接入方法、资源配置方法以及装置
CN115918219A (zh) * 2020-08-24 2023-04-04 Oppo广东移动通信有限公司 信息传输方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160044707A1 (en) * 2014-08-08 2016-02-11 Telefonaktiebolaget L M Ericsson (Publ) Coordination between prose bsr and cellular bsr
CN106412794A (zh) * 2015-07-21 2017-02-15 电信科学技术研究院 一种资源分配的方法和设备
US20170289733A1 (en) * 2016-03-31 2017-10-05 Samsung Electronics Co., Ltd Method and apparatus for transmission of control and data in vehicle to vehicle communication
CN107645774A (zh) * 2016-07-20 2018-01-30 普天信息技术有限公司 V2x网络中调度pc5口资源的确认方法

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102149080B (zh) * 2010-02-10 2014-03-12 电信科学技术研究院 缓存状态报告和调度请求的处理方法及用户设备
EP3471487B1 (en) * 2014-03-21 2020-12-23 Sun Patent Trust Apparatus and method for transmitting a buffer status report
WO2016089115A1 (en) * 2014-12-03 2016-06-09 Lg Electronics Inc. Method and apparatus for configuring scheduling request prohibit timer for prose priority in wireless communication system
US9820298B2 (en) * 2015-03-09 2017-11-14 Ofinno Technologies, Llc Scheduling request in a wireless device and wireless network
KR20170123236A (ko) * 2016-04-28 2017-11-07 엘지전자 주식회사 데이터 볼륨 정보를 전송하는 방법 및 사용자기기
US11159979B2 (en) * 2017-04-26 2021-10-26 Asustek Computer Inc. Method and apparatus for requesting resource for control element transmission in a wireless communication system
JP2020524439A (ja) * 2017-06-15 2020-08-13 コンヴィーダ ワイヤレス， エルエルシー スケジューリングリクエスト、状態報告、および論理チャネル優先順位付け
CN110831062B (zh) * 2018-08-10 2022-02-25 华为技术有限公司 一种通信方法及相关设备
CN116405902A (zh) * 2018-08-10 2023-07-07 中兴通讯股份有限公司 车联网中直通链路的资源配置方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160044707A1 (en) * 2014-08-08 2016-02-11 Telefonaktiebolaget L M Ericsson (Publ) Coordination between prose bsr and cellular bsr
CN106412794A (zh) * 2015-07-21 2017-02-15 电信科学技术研究院 一种资源分配的方法和设备
US20170289733A1 (en) * 2016-03-31 2017-10-05 Samsung Electronics Co., Ltd Method and apparatus for transmission of control and data in vehicle to vehicle communication
CN107645774A (zh) * 2016-07-20 2018-01-30 普天信息技术有限公司 V2x网络中调度pc5口资源的确认方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL: "Discussion on the questions in SA2 LS on reliability for eV2X", 3GPP TSG-RAN2 MEETING 101 R2-1801907, 15 February 2018 (2018-02-15), XP051399378 *
See also references of EP3840429A4 *

Also Published As

Publication number Publication date
MX2021001724A (es) 2021-04-19
AU2019322270A1 (en) 2021-04-08
CN110830955A (zh) 2020-02-21
US20210258989A1 (en) 2021-08-19
EP3840429A4 (en) 2022-05-25
CN110830955B (zh) 2024-01-05
AU2019322270A8 (en) 2021-06-24
EP3840429B1 (en) 2024-03-27
EP3840429A1 (en) 2021-06-23

Similar Documents

Publication Publication Date Title
WO2020034904A1 (zh) 用户设备的控制方法、基站的控制方法以及用户设备
US20200383135A1 (en) Method for random access in idle state and device
WO2021022907A1 (zh) 数据传输方法、装置及存储介质
JP6655085B2 (ja) サイドリンク論理チャネルに対する論理チャネル優先順位付け手順
CN107295678B (zh) 基站、用户设备和相关方法
TWI482523B (zh) 處理觸發暫存器狀態報告之計時器的方法及通訊裝置
CN104170491B (zh) 用于配置多个调度请求触发的方法和装置
MX2012008807A (es) Metodo para la programacion de recursos inalambricos, elementos de red de una red de acceso y su terminal.
WO2014040467A1 (zh) 一种资源调度的方法、设备及通信系统
KR20160130300A (ko) 반정적 스케줄링 방법 및 장치
WO2012136087A1 (zh) 一种资源调度的方法及系统及一种终端
WO2020015527A1 (zh) 资源选择方法、基站及终端
WO2018202044A1 (zh) 一种调度请求的处理方法及系统
WO2016162832A1 (en) System, method, and apparatus for floor control during push to talk
CN109156020A (zh) 调度请求触发方法、装置和系统
WO2012083890A1 (zh) 一种数据发送方法和用户设备
EP2839714B1 (en) Method and radio network node for managing radio resources
TWI718390B (zh) 基地台、使用者設備和相關方法
WO2022082530A1 (zh) 通信方法及装置
WO2018201929A1 (zh) 用于处理调度请求的方法和设备
JP2020537853A (ja) スケジューリングリクエストを伝送する方法及び端末装置
JP2023546231A (ja) サイドリンク通信方法および装置
US20210195647A1 (en) Communication control method and user equipment
JP6211845B2 (ja) 移動局及び移動通信システム
JP7481647B2 (ja) 無線局及び通信システム

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019850136

Country of ref document: EP

Effective date: 20210315

ENP Entry into the national phase

Ref document number: 2019322270

Country of ref document: AU

Date of ref document: 20190809

Kind code of ref document: A