WO2020088658A1 - Procédé et appareil de gestion de grappes v2x à nouvelle radio - Google Patents

Procédé et appareil de gestion de grappes v2x à nouvelle radio Download PDF

Info

Publication number
WO2020088658A1
WO2020088658A1 PCT/CN2019/115053 CN2019115053W WO2020088658A1 WO 2020088658 A1 WO2020088658 A1 WO 2020088658A1 CN 2019115053 W CN2019115053 W CN 2019115053W WO 2020088658 A1 WO2020088658 A1 WO 2020088658A1
Authority
WO
WIPO (PCT)
Prior art keywords
cluster
scheduler
processor
receiving
request
Prior art date
Application number
PCT/CN2019/115053
Other languages
English (en)
Inventor
Ju-Ya Chen
Chien-Yi Wang
Ahmet Umut UGURLU
Original Assignee
Mediatek Inc.
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
Priority claimed from US16/584,943 external-priority patent/US10897792B2/en
Application filed by Mediatek Inc. filed Critical Mediatek Inc.
Priority to CN201980006037.6A priority Critical patent/CN111418190B/zh
Publication of WO2020088658A1 publication Critical patent/WO2020088658A1/fr

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]
    • 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
    • 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

Definitions

  • the present disclosure is generally related to wireless communications and, more particularly, to techniques pertaining to New Radio (NR) vehicle-to-everything (V2X) cluster management.
  • NR New Radio
  • V2X vehicle-to-everything
  • vehicle platooning can support reliable vehicle-to-vehicle (V2V) communications between a specific user equipment (UE) supporting V2X applications and up to nineteen other UEs supporting V2X applications.
  • V2V vehicle-to-vehicle
  • UE user equipment
  • NR Sidelink multiple UEs may be grouped into a cluster with a cluster head (herein interchangeably referred to as a “scheduler UE” ) scheduling the time-frequency resources for other UEs in the cluster.
  • Scheduling by cluster head is a centralized scheduling scheme, and centralized scheduling tends to be more reliable and more suitable in situations with crowded traffic than distributed scheduling.
  • the cluster head can sense its local environment and, accordingly, schedule available resources faster than a base station (e.g., gNB) can.
  • a base station e.g., gNB
  • certain details regarding V2X cluster management remain to be defined, including: cluster architecture, resource scheduling, selection of a scheduler UE, procedures for member check-in and check-out, cluster head handover to a member, member handover to another cluster, how to handle disappearance of the scheduler UE, and cluster dissolution.
  • the present disclosure aims to propose concepts, solutions, schemes, techniques, designs, methods and apparatus pertaining to NR V2X cluster management. Specifically, an objective of the present disclosure is to propose schemes related to cluster architecture, resource scheduling, selection of a scheduler UE, procedures for member check-in and check-out, cluster head handover to a member, member handover to another cluster, how to handle disappearance of the scheduler UE, and cluster dissolution.
  • a method may involve a processor of an apparatus, implemented in a UE of a V2X cluster in an NR V2X communication environment, receiving a scheduling request from a member of the V2X cluster.
  • the method may also involve the processor transmitting a resource grant to the member to allocate a resource of one or more resources to the member responsive to the receiving of the scheduling request.
  • the one or more resources may be either: (a) preconfigured by a wireless network, or (b) granted by the wireless network responsive to the UE transmitting a resource request to the wireless network upon receiving the scheduling request.
  • a method may involve a processor of an apparatus, implemented in a UE, detecting a scheduler UE in an NR V2X communication environment.
  • the method may also involve the processor selecting the scheduler UE to join a V2X cluster associated with the scheduler UE in response to the detecting and at least one of the following: (1) a channel occupancy ratio in the NR V2X communication environment being greater than a predefined threshold; (2) the UE having a throughput greater than a predefined throughput; and (3) the UE having data to transmit with a size of the data being greater than a predefined size.
  • radio access technologies such as NR V2X and V2V
  • the proposed concepts, schemes and any variation (s) /derivative (s) thereof may be implemented in, for and by other types of radio access technologies, networks and network topologies such as, for example and without limitation, 5 th Generation (5G) , Long-Term Evolution (LTE) , LTE-Advanced, LTE-Advanced Pro and any future-developed networks and technologies.
  • 5G 5 th Generation
  • LTE Long-Term Evolution
  • LTE-Advanced LTE-Advanced
  • Pro any future-developed networks and technologies.
  • FIG. 1 is a diagram of an example network environment in which various solutions and schemes in accordance with the present disclosure may be implemented.
  • FIG. 2A is a diagram of an example scenario in accordance with an implementation of the present disclosure.
  • FIG. 2B is a diagram of an example scenario in accordance with an implementation of the present disclosure.
  • FIG. 3 is a diagram of an example scenario in accordance with an implementation of the present disclosure.
  • FIG. 4 is a block diagram of an example communication system in accordance with an implementation of the present disclosure.
  • FIG. 5 is a flowchart of an example process in accordance with an implementation of the present disclosure.
  • FIG. 6 is a flowchart of an example process in accordance with an implementation of the present disclosure.
  • Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and/or solutions pertaining to NR V2X cluster management. According to the present disclosure, a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.
  • FIG. 1 illustrates an example network environment 100 in which various solutions and schemes in accordance with the present disclosure may be implemented.
  • FIG. 2A, FIG. 2B and FIG. 3 illustrate example scenarios 200A, 200B and 300, respectively, in accordance with implementations of the present disclosure.
  • Each of scenarios 200 and 300 may be implemented in network environment 100.
  • the following description of various proposed schemes is provided with reference to FIG. 1 ⁇ FIG. 3.
  • network environment 100 may involve a UE 110, as a scheduler UE, in wireless communication with a wireless network 130 via a base station or network node 135 (e.g., an eNB, gNB or transmit/receive point (TRP) ) .
  • UE 110 may also be in wireless communication via a sidelink interface with one or more members, represented by UE 120, in an NR V2X cluster.
  • UE 120 may be also in wireless communication with one or more other UEs, represented by UE 125, which may or may not be member (s) of the cluster. It is noteworthy that, although FIG. 2A and FIG.
  • UE 110 and at least one of the one or more member UEs may implement various schemes pertaining to NR V2X cluster management in accordance with the present disclosure, as described below.
  • platooning is one important use case.
  • Platoon lead in a platoon may communicate with platoon members using unicast and/or multicast.
  • distributed scheduling is used for resource allocation in mode 4. In a low or medium traffic load condition, distributed scheduling may have good performance with low collision probability. However, distributed scheduling tends to have worse performance than centralized scheduling when the traffic load for a local area is high. Thus, a cluster can be formed while the traffic load is high and, in the cluster, a scheduler UE can help schedule resources to avoid high probability of collision.
  • resource scheduling by UE 110 may take either of two forms, depending on the level of involvement of network node 135.
  • UE 110 may request from network node 135 for resources to be used for scheduling and, in response, UE 110 may receive a grant of resources from network node 135 via an Uu interface.
  • UE 110 may utilize resources preconfigured by network node 135 for scheduling.
  • UE 110 may be responsible for communicating resource allocation via a sidelink interface to UE 120 which requires the resources for transmission.
  • UE 110 may be expected to be in cellular coverage of network node 135 while UE 120 may be outside the cellular coverage of network node 135.
  • UE 120 and UE 125
  • whether a given UE can serve or otherwise function as a scheduler UE may depend on its capability.
  • UE 110 may transmit a resource request to network node 135 and, in turn, network node 135 may grant resources for use by UE 110. Then, UE 120 may transmit to UE 110 a scheduling request with a buffer status report (BSR) . In response, UE 110 may grant resource (s) to UE 120. Accordingly, UE 120 may utilize the granted resource (s) for control/data transmission to UE 125.
  • BSR buffer status report
  • UE 120 may transmit to UE 110 a scheduling request with a (BSR. Then, UE 110 may transmit a resource request to network node 135 and, in turn, network node 135 may grant resources for use by UE 110. In response, UE 110 may grant the resource (s) to UE 120. Accordingly, UE 120 may utilize the granted resource (s) for control/data transmission to UE 125.
  • BSR scheduling request with a
  • network node 135 may preconfigure resources for UE 110 to utilize for resource scheduling.
  • UE 120 may transmit a scheduling request to UE 110 with a BSR.
  • UE 110 may grant resource (s) to UE 120.
  • UE 120 may utilize the granted resource (s) for control/data transmission to UE 125.
  • a UE may perform one or more operations in the process of selecting a scheduler UE. For instance, this UE may measure a channel occupancy ratio in its surrounding in network environment 100 to determine whether the channel occupancy ratio is greater than a predefined threshold. Alternatively, or additionally, this UE may determine whether it has a high throughput or whether there is a need to transmit large-sized packet (s) .
  • the UE may detect existence of any scheduler UE.
  • the UE may select one of the multiple scheduler UEs with the largest reference signal received power (RSRP) or, alternatively, the UE may randomly select one of the multiple scheduler UEs.
  • this UE may transmit a scheduling request with BSR to the selected scheduler UE (e.g., UE 110) to request for resources.
  • the selected scheduler UE upon receiving the scheduling request, may request for resources from network node 135.
  • the selected scheduler UE may grant resource (s) to the requesting UE. Accordingly, this UE (e.g., UE 120) may utilize the granted resource (s) to transmit data.
  • the UE may transmit a scheduling request with BSR to the scheduler UE to request for resources.
  • the scheduler UE upon receiving the scheduling request, may request for resources from network node 135.
  • the scheduler UE may grant resource (s) to the requesting UE. Accordingly, this UE (e.g., UE 120) may utilize the granted resource (s) to transmit data.
  • the UE may determine whether itself has sufficient capability to become, serve or otherwise function as a scheduler UE. In an event that the UE has the capability to be a scheduler UE, the UE may randomly select a cluster identity (ID) . In case that this UE is in cellular coverage of network node 135, this UE may transmit information to network node 135 to request to be a scheduler UE. In an event that network node 135 grants the request, this UE may thus be promoted to the status of a scheduler UE. Additionally, when granting the request, network node 135 may assign a cluster ID to this new scheduler UE.
  • ID cluster identity
  • network node 135 does not grant the request or the UE does not receive the grant from network node 135, this UE may continue to operate in its current transmission mode.
  • the UE may assume the status of a scheduler UE and proceed to function as a scheduler UE. For instance, this new scheduler UE may randomly select a cluster ID and broadcast the cluster ID (and any related information) .
  • this new scheduler UE may utilize any preconfigured resource (s) for resource scheduling.
  • the UE may continue to operate in its current transmission mode.
  • a cluster head (e.g., UE 110) may periodically broadcast a discovery signal with cluster information to inform other UEs the existence of a cluster associated with the cluster head.
  • a UE e.g., UE 120 or UE 125
  • the cluster head as the scheduler UE, may have full control of the reported communication resources from its members in the cluster.
  • a member UE e.g., UE 120
  • a UE may transmit a check-out signal to inform the cluster head (e.g., UE 110) that it will leave the cluster.
  • This UE may take (e.g., be allocated and then use) some communication resource (s) before leaving the cluster.
  • a UE may be deemed to have passively checked out in case that such a UE does not send a scheduling request or cannot be reached after a predetermined period. In such cases, the cluster head (e.g., UE 110) may assume or otherwise determine that the UE has checked out.
  • a current scheduler UE may choose a cluster member (e.g., UE 120) to take over the role of the next scheduler UE when the current scheduler UE detects that the RSRP of a certain percentage (e.g., X%) of cluster members of the cluster is below a predefined threshold.
  • the next scheduler UE may be chosen based on one or more of the following parameters: receiving RSRP, location, speed of movement, and processing capability.
  • a member UE may decide whether to join and be handed over to another cluster when the UE detects another cluster other than the one that the UE currently belongs.
  • the UE may decide whether to join this other cluster based on information such as, for example and without limitation, RSRP, location and speed of the cluster head of the other cluster.
  • the UE may perform a number of operations for handover to that other cluster, as described below. Firstly, the UE may start a timer.
  • the UE may transmit a leaving command to its current scheduler UE and follow the check-out procedure described above to leave the current cluster.
  • the UE may transmit a joining command to the scheduler UE of the other cluster and follow the check-in procedure described above to join that other cluster.
  • the UE may join the new cluster in response to the UE having received a grant of joining command. Otherwise, in case that the timer has expired, the UE may return to its original transmission mode.
  • the UE may keep its connection with the current scheduler UE of the current cluster.
  • a member UE may set a timer and then listen to the scheduler UE in response to the member UE not having received any signal from the scheduler UE. In case the UE receives signal (s) from the scheduler UE, the UE may consider itself still a member of the cluster associated with the scheduler UE. Otherwise, in case that the UE does not receive any signal from the scheduler UE and the timer has expired, the UE may leave the cluster. In case that the UE does not receive any signal from the scheduler UE and the timer has not expired, the UE may consider itself still a member of the cluster associated with the scheduler UE.
  • the UE may consider itself still a member of the cluster associated with the scheduler UE.
  • a scheduler UE may transmit a dissolution signal to inform member UEs of the cluster that the cluster is dissolved upon the scheduler UE determining to dissolve the cluster.
  • the scheduler UE may determine to dissolve the cluster as a result of the scheduler UE detecting that its channel busy ratio is lower than a predefined threshold or as a result of the scheduler UE not being able to find a suitable member to take over the role of scheduler UE.
  • the scheduler UE may perform a final resource allocation before the dissolution.
  • FIG. 4 illustrates an example communication system 400 having an example apparatus 410 and an example apparatus 420 in accordance with an implementation of the present disclosure.
  • apparatus 410 and apparatus 420 may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to NR V2X cluster management, including various schemes described above as well as processes described below.
  • Each of apparatus 410 and apparatus 420 may be a part of an electronic apparatus, which may be a UE such as a vehicle, a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus or a computing apparatus.
  • each of apparatus 410 and apparatus 420 may be implemented in an electronic control unit (ECU) of a vehicle, a smartphone, a smartwatch, a personal digital assistant, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer.
  • ECU electronice control unit
  • Each of apparatus 410 and apparatus 420 may also be a part of a machine type apparatus, which may be an IoT or NB-IoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a wire communication apparatus or a computing apparatus.
  • each of apparatus 410 and apparatus 420 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center.
  • each of apparatus 410 and apparatus 420 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more complex-instruction-set-computing (CISC) processors, or one or more reduced-instruction-set-computing (RISC) processors.
  • CISC complex-instruction-set-computing
  • RISC reduced-instruction-set-computing
  • Each of apparatus 410 and apparatus 420 may include at least some of those components shown in FIG. 4 such as a processor 412 and a processor 422, respectively.
  • Each of apparatus 410 and apparatus 420 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device) , and, thus, such component (s) of each of apparatus 410 and apparatus 420 are neither shown in FIG. 4 nor described below in the interest of simplicity and brevity.
  • components not pertinent to the proposed scheme of the present disclosure e.g., internal power supply, display device and/or user interface device
  • At least one of apparatus 410 and apparatus 420 may be a part of an electronic apparatus, which may be a vehicle, a roadside unit (RSU) , network node or base station (e.g., eNB, gNB or TRP) , a small cell, a router or a gateway.
  • RSU roadside unit
  • network node or base station e.g., eNB, gNB or TRP
  • eNB g., gNB or TRP
  • a small cell e.g., a router or a gateway.
  • at least one of apparatus 410 and apparatus 420 may be implemented in a vehicle in a V2V or V2X network, an eNodeB in an LTE, LTE-Advanced or LTE-Advanced Pro network or in a gNB in a 5G, NR, IoT or NB-IoT network.
  • apparatus 410 and apparatus 420 may be implemented in the form of one or more IC chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors.
  • each of processor 412 and processor 422 may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, even though a singular term “a processor” is used herein to refer to processor 412 and processor 422, each of processor 412 and processor 422 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure.
  • each of processor 412 and processor 422 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and/or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure.
  • each of processor 412 and processor 422 is a special-purpose machine specifically designed, arranged and configured to perform specific tasks including NR V2X cluster management in accordance with various implementations of the present disclosure.
  • apparatus 410 may also include a transceiver 416, as a communication device, coupled to processor 412 and capable of wirelessly transmitting and receiving data.
  • apparatus 410 may further include a memory 414 coupled to processor 412 and capable of being accessed by processor 412 and storing data therein.
  • apparatus 420 may also include a transceiver 426, as a communication device, coupled to processor 422 and capable of wirelessly transmitting and receiving data.
  • apparatus 420 may further include a memory 424 coupled to processor 422 and capable of being accessed by processor 422 and storing data therein. Accordingly, apparatus 410 and apparatus 420 may wirelessly communicate with each other via transceiver 416 and transceiver 426, respectively.
  • apparatus 410 is implemented in or as a wireless communication device
  • a communication apparatus or a scheduler UE e.g., UE 110
  • apparatus 420 is implemented in or as a member UE (e.g., UE 120) .
  • processor 412 of apparatus 410 may receive, via transceiver 416, a scheduling request (e.g., with or without a BSR) from a member of the V2X cluster. Additionally, processor 412 may transmit, via transceiver 416, a resource grant to the member to allocate a resource of one or more resources to the member in response to the receiving of the scheduling request.
  • the one or more resources may be either: (a) preconfigured by a wireless network, or (b) granted by the wireless network in response to apparatus 410 transmitting a resource request to the wireless network upon receiving the scheduling request.
  • processor 412 may perform additional operations. For instance, processor 412 may broadcast, via transceiver 416, a discovery signal with cluster information as notification of existence of the V2X cluster. Moreover, processor 412 may receive, via transceiver 416, a report of a percentage of resources currently occupied for communication from one other UE in response to the broadcasting of the discovery signal. Furthermore, processor 412 may determine the other UE to be a new member of the V2X cluster in response to the receiving of the report.
  • processor 412 may perform additional operations. For instance, processor 412 may receive, via transceiver 416, a check-out signal from the member. Moreover, processor 412 may determine the member to be checked out of the V2X cluster in response to the receiving of the check-out signal.
  • processor 412 may perform additional operations. For instance, processor 412 may determine the member to be checked out of the V2X cluster in response to at least one of the following: (1) a first predetermined duration having passed without receiving any further scheduling request from the member; and (2) the member being not reachable for a second predetermined duration.
  • processor 412 may perform additional operations. For instance, processor 412 may detect, via transceiver 416, that a RSRP of a predetermined percentile of a plurality of members of the V2X cluster is below a predefined threshold. Furthermore, processor 412 may select one of the plurality of members to take over a role of a scheduler UE in response to the detecting.
  • processor 412 may select one of the plurality of members based on one or more of a plurality of parameters with respect to each of the plurality of members, with the plurality of parameters including: (a) a level of a receiving RSRP; (b) a location; (c) a velocity; and (d) a processing capability.
  • processor 412 may perform further operations. For instance, processor 412 may transmit, via transceiver 416, a dissolution signal to inform each member of the V2X cluster that the V2X cluster is dissolved in response to a predetermined duration having passed without finding a suitable member of the V2X cluster to take over the role as the scheduler UE.
  • processor 412 may optionally perform another resource allocation to one or more of the plurality of members before dissolution.
  • processor 412 may perform additional operations. For instance, processor 412 may detect, via transceiver 416, existence of a predefined condition. Moreover, processor 412 may transmit, via transceiver 416, a dissolution signal to inform each member of the V2X cluster that the V2X cluster is dissolved in response to the detecting. Furthermore, processor 412 may optionally perform another resource allocation to one or more of a plurality of members of the V2X cluster before dissolution.
  • the predefined condition may include at least one of: (1) a channel busy radio of apparatus 410 being lower than a predefined threshold; and (2) a predetermined duration having passed without finding a suitable member of the V2X cluster to take over a role as a scheduler UE.
  • processor 412 may determine that apparatus 410 has capability to function as a scheduler UE. In some implementations, in response to determining that apparatus 410 has capability to function as the scheduler UE, processor 412 may perform additional operations. For instance, processor 412 may transmit, via transceiver 416, a request to a network node of a wireless network to request to function as the scheduler UE.
  • processor 412 may obtain a cluster ID for a V2X cluster associated with the scheduler UE by either: (a) selecting a first ID to be used as the cluster ID for the V2X cluster; or (b) receiving, via transceiver 416, a message from the network node granting the request, the message indicating a second ID to be used as the cluster ID for the V2X cluster.
  • processor 422 of apparatus 420 may measure, via transceiver 426, a channel occupancy ratio in an NR V2X communication environment. Moreover, processor 422 may select a scheduler UE to join a V2X cluster associated with the scheduler UE based on a result of the measuring or one or more other factors.
  • processor 422 may select the scheduler UE in response to at least one of: (1) the measured channel occupancy ratio being greater than a predefined threshold; (2) apparatus 420 having a throughput greater than a predefined throughput; and (3) apparatus 420 having data (e.g., one or more packets) to transmit with a size of the data being greater than a predefined size.
  • processor 422 of apparatus 420 may detect, via transceiver 426, a scheduler UE (e.g., apparatus 410) in an NR V2X communication environment. Moreover, processor 422 may select the scheduler UE to join a V2X cluster associated with the scheduler UE response to the detecting and at least one of: (1) a channel occupancy ratio in the NR V2X communication environment being greater than a predefined threshold; (2) apparatus 420 having a throughput greater than a predefined throughput; and (3) apparatus 420 having data to transmit with a size of the data being greater than a predefined size.
  • processor 422 may perform certain operations. For instance, processor 422 may measure a respective RSRP of each of a plurality of scheduler UEs. Moreover, processor 422 may select the scheduler UE by performing either: (a) selecting one of the plurality of scheduler UEs having a largest RSRP compared to that of others of the plurality of scheduler UEs to be the scheduler UE; or (b) randomly selecting one of the plurality of scheduler UEs to be the scheduler UE.
  • processor 422 may perform additional operations. For instance, processor 422 may transmit, via transceiver 426, a scheduling request with a BSR to the scheduler UE. Moreover, processor 422 may receive, via transceiver 426, a resource grant from the scheduler UE that allocates a resource of one or more resources to apparatus 420 in response to the transmitting of the scheduling request. Furthermore, processor 422 may transmit, via transceiver 426, data using the allocated resource.
  • processor 422 may perform additional operations. For instance, processor 422 may determine that apparatus 420 has capability to function as a new scheduler UE. In some implementations, in an event that apparatus 420 is in cellular coverage of a network node of a wireless network, processor 422 may perform certain operations. For instance, processor 422 may transmit, via transceiver 426, a request to the network node to request to function as the new scheduler UE.
  • processor 422 may receive, via transceiver 426, a message from the network node granting the request and obtaining a cluster identity (ID) for a V2X cluster associated with the scheduler UE by either: (a) selecting a first ID to be used as the cluster ID for the V2X cluster; or (b) receiving a message from the network node granting the request, the message indicating a second ID to be used as the cluster ID for the V2X cluster.
  • processor 422 may maintain in a current transmission mode.
  • processor 422 may perform additional operations. For instance, processor 422 may broadcast, via transceiver 426, a discovery signal with cluster information as notification of existence of the new V2X cluster. Moreover, processor 422 may allocate a resource to a member of the new V2X cluster.
  • processor 422 may perform additional operations. For instance, processor 422 may detect, via transceiver 426, one other scheduler UE of one other V2X cluster. Moreover, processor 422 may determine whether to join the other V2X cluster in response to the detecting. Furthermore, processor 422 may perform, via transceiver 426, a handover procedure to join the other V2X cluster in response to determining to join the other V2X cluster.
  • the handover procedure may involve processor 422 performing certain operations, including: (a) starting a timer; (b) transmitting a departure signal to the scheduler UE to notify the scheduler UE about departure from the V2X cluster; (c) transmitting a joining signal to the other scheduler UE to join the other V2X cluster; (d) in response to receiving a grant from the scheduler UE with respect to the departure, performing either: (i) joining the other V2X cluster in an event a grant to join the other V2X cluster is received from the other scheduler UE before expiration of the timer; or (ii) returning to an original transmission mode in an event that no grant to join the other V2X cluster is received from the other scheduler UE before expiration of the timer; and (e) in response to not receiving the grant from the scheduler UE with respect to the departure, maintaining a connection with the scheduler UE.
  • processor 422 may perform additional operations. For instance, processor 422 may start a timer. Additionally, processor 422 may determine whether any signal is received from the scheduler UE before expiration of the timer. Moreover, processor 422 may perform one of: (a) determining that apparatus 420 is still a member of the V2X cluster in an event that at least one signal is received from the scheduler UE before the expiration of the timer; (b) determining that apparatus 420 is no longer a member of the V2X cluster in an event that no signal is received from the scheduler UE before the expiration of the timer; and (c) determining that apparatus 420 is still a member of the V2X cluster in an event that no signal is received from the scheduler UE before the expiration of the timer.
  • FIG. 5 illustrates an example process 500 in accordance with an implementation of the present disclosure.
  • Process 500 may be an example implementation of the proposed schemes described above with respect to NR V2X cluster management in accordance with the present disclosure.
  • Process 500 may represent an aspect of implementation of features of apparatus 410 and apparatus 420.
  • Process 500 may include one or more operations, actions, or functions as illustrated by one or more of blocks 510 and 520. Although illustrated as discrete blocks, various blocks of process 500 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 500 may be executed in the order shown in FIG. 5 or, alternatively, in a different order. Process 500 may also be repeated partially or entirely.
  • Process 500 may be implemented by apparatus 410, apparatus 420 and/or any suitable wireless communication device, UE, roadside unit (RSU) , base station or machine type devices. Solely for illustrative purposes and without limitation, process 500 is described below in the context of apparatus 410 as a scheduler UE (e.g., UE 110) and apparatus 420 as a member UE (e.g., UE 120) in network environment 100. Process 500 may begin at block 510.
  • UE e.g., UE 110
  • RSU roadside unit
  • process 500 may involve processor 412 of apparatus 410, implemented in a UE (e.g., UE 110) of a V2X cluster in an NR V2X communication environment (e.g., communication environment 100) , receiving, via transceiver 416, a scheduling request (e.g., with or without a BSR) from a member of the V2X cluster.
  • a scheduling request e.g., with or without a BSR
  • Process 500 may proceed from 510 to 520.
  • process 500 may involve processor 412 transmitting, via transceiver 416, a resource grant to the member to allocate a resource of one or more resources to the member in response to the receiving of the scheduling request.
  • the one or more resources may be either: (a) preconfigured by a wireless network, or (b) granted by the wireless network in response to apparatus 410 transmitting a resource request to the wireless network upon receiving the scheduling request.
  • process 500 may involve processor 412 performing additional operations. For instance, process 500 may involve processor 412 broadcasting, via transceiver 416, a discovery signal with cluster information as notification of existence of the V2X cluster. Moreover, process 500 may involve processor 412 receiving, via transceiver 416, a report of a percentage of resources currently occupied for communication from one other UE in response to the broadcasting of the discovery signal. Furthermore, process 500 may involve processor 412 determining the other UE to be a new member of the V2X cluster in response to the receiving of the report.
  • process 500 may involve processor 412 performing additional operations. For instance, process 500 may involve processor 412 receiving, via transceiver 416, a check-out signal from the member. Moreover, process 500 may involve processor 412 determining the member to be checked out of the V2X cluster in response to the receiving of the check-out signal.
  • process 500 may involve processor 412 performing additional operations. For instance, process 500 may involve processor 412 determining the member to be checked out of the V2X cluster in response to at least one of the following: (1) a first predetermined duration having passed without receiving any further scheduling request from the member; and (2) the member being not reachable for a second predetermined duration.
  • process 500 may involve processor 412 performing additional operations. For instance, process 500 may involve processor 412 detecting, via transceiver 416, that a RSRP of a predetermined percentile of a plurality of members of the V2X cluster is below a predefined threshold. Furthermore, process 500 may involve processor 412 selecting one of the plurality of members to take over a role of a scheduler UE in response to the detecting.
  • process 500 may involve processor 412 selecting one of the plurality of members based on one or more of a plurality of parameters with respect to each of the plurality of members, with the plurality of parameters including: (a) a level of a receiving RSRP; (b) a location; (c) a velocity; and (d) a processing capability. In some implementations, process 500 may involve processor 412 performing further operations.
  • process 500 may involve processor 412 transmitting, via transceiver 416, a dissolution signal to inform each member of the V2X cluster that the V2X cluster is dissolved in response to a predetermined duration having passed without finding a suitable member of the V2X cluster to take over the role as the scheduler UE.
  • process 500 may involve processor 412 optionally performing another resource allocation to one or more of the plurality of members before dissolution.
  • process 500 may involve processor 412 performing additional operations. For instance, process 500 may involve processor 412 detecting, via transceiver 416, existence of a predefined condition. Moreover, process 500 may involve processor 412 transmitting, via transceiver 416, a dissolution signal to inform each member of the V2X cluster that the V2X cluster is dissolved in response to the detecting. Furthermore, process 500 may involve processor 412 optionally performing another resource allocation to one or more of a plurality of members of the V2X cluster before dissolution.
  • the predefined condition may include at least one of: (1) a channel busy radio of apparatus 410 being lower than a predefined threshold; and (2) a predetermined duration having passed without finding a suitable member of the V2X cluster to take over a role as a scheduler UE.
  • process 500 may involve processor 412 determining that apparatus 410 has capability to function as a scheduler UE. In some implementations, in response to determining that apparatus 410 has capability to function as the scheduler UE, process 500 may involve processor 412 performing additional operations. For instance, process 500 may involve processor 412 transmitting, via transceiver 416, a request to a network node of a wireless network to request to function as the scheduler UE.
  • process 500 may involve processor 412 obtaining a cluster ID for a V2X cluster associated with the scheduler UE by either: (a) selecting a first ID to be used as the cluster ID for the V2X cluster; or (b) receiving, via transceiver 416, a message from the network node granting the request, the message indicating a second ID to be used as the cluster ID for the V2X cluster.
  • FIG. 6 illustrates an example process 600 in accordance with an implementation of the present disclosure.
  • Process 600 may be an example implementation of the proposed schemes described above with respect to NR V2X cluster management in accordance with the present disclosure.
  • Process 600 may represent an aspect of implementation of features of apparatus 410 and apparatus 420.
  • Process 600 may include one or more operations, actions, or functions as illustrated by one or more of blocks 610 and 620. Although illustrated as discrete blocks, various blocks of process 600 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 600 may be executed in the order shown in FIG. 6 or, alternatively, in a different order. Process 600 may also be repeated partially or entirely.
  • Process 600 may be implemented by apparatus 410, apparatus 420 and/or any suitable wireless communication device, UE, roadside unit (RSU) , base station or machine type devices. Solely for illustrative purposes and without limitation, process 600 is described below in the context of apparatus 410 as a scheduler UE (e.g., UE 110) and apparatus 420 as a member UE (e.g., UE 120) in network environment 100. Process 600 may begin at block 610.
  • UE e.g., UE 110
  • RSU roadside unit
  • Process 600 may begin at block 610.
  • process 600 may involve processor 422 of apparatus 420, implemented in a UE (e.g., UE 120) , detecting, via transceiver 426, a scheduler UE (e.g., apparatus 410) in an NR V2X communication environment.
  • Process 600 may proceed from 610 to 620.
  • process 600 may involve processor 422 selecting the scheduler UE to join a V2X cluster associated with the scheduler UE.
  • process 600 may involve processor 422 selecting the scheduler UE in response to the detecting and at least one of: (1) a channel occupancy ratio in the NR V2X communication environment being greater than a predefined threshold; (2) apparatus 420 having a throughput greater than a predefined throughput; and (3) apparatus 420 having data to transmit with a size of the data being greater than a predefined size.
  • process 600 may involve processor 422 performing certain operations. For instance, process 600 may involve processor 422 measuring a respective RSRP of each of a plurality of scheduler UEs. Moreover, process 600 may involve processor 422 selecting the scheduler UE by performing either: (a) selecting one of the plurality of scheduler UEs having a largest RSRP compared to that of others of the plurality of scheduler UEs to be the scheduler UE; or (b) randomly selecting one of the plurality of scheduler UEs to be the scheduler UE.
  • process 600 may involve processor 422 performing additional operations. For instance, process 600 may involve processor 422 transmitting, via transceiver 426, a scheduling request with a BSR to the scheduler UE. Moreover, process 600 may involve processor 422 receiving, via transceiver 426, a resource grant from the scheduler UE that allocates a resource of one or more resources to apparatus 420 in response to the transmitting of the scheduling request. Furthermore, process 600 may involve processor 422 transmitting, via transceiver 426, data using the allocated resource.
  • process 600 may involve processor 422 performing additional operations. For instance, process 600 may involve processor 422 determining that apparatus 420 has capability to function as a new scheduler UE. In some implementations, in an event that apparatus 420 is in cellular coverage of a network node of a wireless network, process 600 may involve processor 422 performing certain operations. For instance, process 600 may involve processor 422 transmitting, via transceiver 426, a request to the network node to request to function as the new scheduler UE.
  • process 600 may involve processor 422 receiving, via transceiver 426, a message from the network node granting the request and obtaining a cluster identity (ID) for a V2X cluster associated with the scheduler UE by either: (a) selecting a first ID to be used as the cluster ID for the V2X cluster; or (b) receiving a message from the network node granting the request, the message indicating a second ID to be used as the cluster ID for the V2X cluster.
  • process 600 may involve processor 422 maintaining in a current transmission mode.
  • process 600 may involve processor 422 performing additional operations. For instance, process 600 may involve processor 422 broadcasting, via transceiver 426, a discovery signal with cluster information as notification of existence of the new V2X cluster. Moreover, process 600 may involve processor 422 allocating a resource to a member of the new V2X cluster.
  • process 600 may involve processor 422 performing additional operations. For instance, process 600 may involve processor 422 detecting, via transceiver 426, one other scheduler UE of one other V2X cluster. Moreover, process 600 may involve processor 422 determining whether to join the other V2X cluster in response to the detecting. Furthermore, process 600 may involve processor 422 performing, via transceiver 426, a handover procedure to join the other V2X cluster in response to determining to join the other V2X cluster.
  • the handover procedure may involve processor 422 performing certain operations, including: (a) starting a timer; (b) transmitting a departure signal to the scheduler UE to notify the scheduler UE about departure from the V2X cluster; (c) transmitting a joining signal to the other scheduler UE to join the other V2X cluster; (d) in response to receiving a grant from the scheduler UE with respect to the departure, performing either: (i) joining the other V2X cluster in an event a grant to join the other V2X cluster is received from the other scheduler UE before expiration of the timer; or (ii) returning to an original transmission mode in an event that no grant to join the other V2X cluster is received from the other scheduler UE before expiration of the timer; and (e) in response to not receiving the grant from the scheduler UE with respect to the departure, maintaining a connection with the scheduler UE.
  • process 600 may involve processor 422 performing additional operations. For instance, process 600 may involve processor 422 starting a timer. Additionally, process 600 may involve processor 422 determining whether any signal is received from the scheduler UE before expiration of the timer. Moreover, process 600 may involve processor 422 performing one of: (a) determining that apparatus 420 is still a member of the V2X cluster in an event that at least one signal is received from the scheduler UE before the expiration of the timer; (b) determining that apparatus 420 is no longer a member of the V2X cluster in an event that no signal is received from the scheduler UE before the expiration of the timer; and (c) determining that apparatus 420 is still a member of the V2X cluster in an event that no signal is received from the scheduler UE before the expiration of the timer.
  • any two components so associated can also be viewed as being “operably connected” , or “operably coupled” , to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable” , to each other to achieve the desired functionality.
  • operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

Landscapes

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

Abstract

L'invention concerne divers exemples et schémas relatifs à la gestion de grappes Véhicule-à-Tout (V2X) à nouvelle radio (NR). Un appareil, mis en oeuvre dans un équipement utilisateur (UE) d'une grappe V2X dans un environnement de communication V2X à nouvelle radio, reçoit une demande de planification provenant d'un membre de la grappe V2X. L'appareil transmet au membre une autorisation de ressource afin d'attribuer audit membre une ressource parmi au moins d'une ressource, en réponse à la réception de la demande de planification. Ladite ressource au moins est : soit (a) préconfigurée par un réseau sans fil, soit (b) attribuée par le réseau sans fil en réponse à la transmission par l'UE d'une demande de ressource au réseau sans fil lors de la réception de la demande de planification.
PCT/CN2019/115053 2018-11-02 2019-11-01 Procédé et appareil de gestion de grappes v2x à nouvelle radio WO2020088658A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201980006037.6A CN111418190B (zh) 2018-11-02 2019-11-01 新无线电车联网群集管理的方法和装置

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201862754703P 2018-11-02 2018-11-02
US62/754,703 2018-11-02
US16/584,943 2019-09-27
US16/584,943 US10897792B2 (en) 2018-09-28 2019-09-27 Method and apparatus of new radio V2X cluster head

Publications (1)

Publication Number Publication Date
WO2020088658A1 true WO2020088658A1 (fr) 2020-05-07

Family

ID=70462428

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/115053 WO2020088658A1 (fr) 2018-11-02 2019-11-01 Procédé et appareil de gestion de grappes v2x à nouvelle radio

Country Status (3)

Country Link
CN (1) CN111418190B (fr)
TW (1) TWI735067B (fr)
WO (1) WO2020088658A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114071399A (zh) * 2020-07-31 2022-02-18 北京紫光展锐通信技术有限公司 资源选择方法及通信装置
WO2022061545A1 (fr) * 2020-09-22 2022-03-31 华为技术有限公司 Procédé et appareil de communication
WO2022077326A1 (fr) * 2020-10-15 2022-04-21 Apple Inc. Déclenchement et signalisation d'un message de coordination entre equipements utilisateurs
WO2023240434A1 (fr) * 2022-06-14 2023-12-21 Qualcomm Incorporated Groupe d'équipements utilisateur et gestion de configuration de quasi-colocalisation

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20140054673A (ko) * 2012-10-29 2014-05-09 현대자동차주식회사 차량 통신 네트워크 기반의 메시지 전송 장치 및 그 방법

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2912889A1 (fr) * 2012-10-26 2015-09-02 Nokia Solutions and Networks Oy Configuration de transferts intercellulaires dans des systèmes de communication
CN104754592B (zh) * 2013-12-31 2018-03-06 北京大唐高鸿软件技术有限公司 一种适用于城市道路环境的车载短距离通信网络分簇方法
US10080120B2 (en) * 2014-12-15 2018-09-18 Huawei Technologies Co., Ltd System and method for machine type communication
EP3316647B1 (fr) * 2015-06-26 2022-05-04 LG Electronics Inc. Procédé et appareil d'émission/réception de signal de terminal de communications de dispositif à dispositif dans un système de communications sans fil
WO2018064179A1 (fr) * 2016-09-30 2018-04-05 Intel Corporation Services v2x dans des réseaux cellulaires de prochaine génération
CN106851566B (zh) * 2017-01-13 2018-07-27 齐鲁工业大学 一种基于车联网簇结构的信息递推式广播方法
US20180242192A1 (en) * 2017-02-23 2018-08-23 Apple Inc. Dynamic Header Compression for Uplink Data for Improving Uplink Link Budget
CN108012244B (zh) * 2017-11-29 2020-12-01 南京工业大学 基于簇的公路车载自组织网络数据服务通信系统及方法

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20140054673A (ko) * 2012-10-29 2014-05-09 현대자동차주식회사 차량 통신 네트워크 기반의 메시지 전송 장치 및 그 방법

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Summary for NR-V2X AI - 7.2.4.1.4 Resource Allocation Mechanism", 3GPP TSG RAN WG1 MEETING #95， R1-1814260, 19 November 2018 (2018-11-19), XP051494712 *
MEDIATEK INC.: ""iscussion of sidelink unicast， groupcast and broadcast for NR-V2X", 3GPP TSG RAN WG1 MEETING #94， R1-1808875, 10 August 2018 (2018-08-10), XP051516246 *
MEDIATEK INC.: "On Sidelink Resource Allocation Mechanism", 3GPP TSG RAN WG! MEETING #95，R1-1812367, 3 November 2018 (2018-11-03), XP051478560 *
MEDIATEK INC.: "UE-assisted resource allocation for NR V2X", 3GPP TSG-RAN WG2 MEETING #103BIS, no. R2-1813673, 11.4.2.4, 8 October 2018 (2018-10-08), Chengdu, China, pages 1 - 4, XP051523168 *

Also Published As

Publication number Publication date
CN111418190A (zh) 2020-07-14
TWI735067B (zh) 2021-08-01
CN111418190B (zh) 2022-12-20
TW202025801A (zh) 2020-07-01

Similar Documents

Publication Publication Date Title
US10887910B2 (en) Method and apparatus of new radio V2X cluster management
US11711807B2 (en) Multi-level indicator of radio resource status for intended D2D transmission
US10736097B2 (en) Systems and methods of handling collisions between multiple semi-persistent grants
WO2020088658A1 (fr) Procédé et appareil de gestion de grappes v2x à nouvelle radio
EP3141073B1 (fr) Procédés, appareil et systèmes permettant de déterminer une priorité de communication
US20170013596A1 (en) Control of semi-persistent channel occupation for device-to device (d2d) wireless communications
US11122459B2 (en) Method and apparatus for skipping uplink transmission in mobile communications
US10897792B2 (en) Method and apparatus of new radio V2X cluster head
US20200112971A1 (en) CAPC For Uplink Transmissions In New Radio Unlicensed Spectrum
WO2015109983A1 (fr) Procédé et appareil d'accès en fonction de d2d
US10362580B2 (en) Fair resource sharing in broadcast based D2D communications
US20220046596A1 (en) Partial Sensing Enhancement For Sidelink Resource Allocation
CN114599010A (zh) 副链路sl上的定位方法、装置及终端
CN110876162A (zh) 一种mtc设备的随机接入方法和装置
WO2016095483A1 (fr) Procédé et dispositif pour un partage de fréquence
WO2022214076A1 (fr) Sélection de ressources de liaison latérale en fonction d'un ensemble prédéfini
WO2022095886A1 (fr) Procédés pour la signalisation d'un cot initié par un ue dans des communications mobiles
US20240032092A1 (en) Uplink Enhancements For URLLC And IIoT In Unlicensed Band
US20240073875A1 (en) Terminal device and method therein for resource reservation
WO2021056560A1 (fr) Procédé et dispositif de réception et d'envoi d'informations de liaison latérale
WO2022238393A1 (fr) Réévaluation de ressources de liaison latérale
WO2020169279A1 (fr) Dispositif de communication, équipement d'infrastructure et procédés associés
CN117136566A (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: 19877684

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19877684

Country of ref document: EP

Kind code of ref document: A1