Coordinate user device selection

Abstract

Methods, devices, systems and apparatus for selecting a coordinating user equipment UE (111) in a user equipment coordination set (UECS) are described herein, which facilitate selection of a coordinating UE (111) by a UE (110) in the UECS. Sharing of the role of the coordinating UE (111) by the UEs (110) in the UECS can be scheduled in a round-robin manner. Selection criteria can be used to determine which UE or UEs (110) in the UECS will provide better performance in the role of the coordinating UE (111).

Description

Background Art

[0001] Typically, a provider of a wireless network manages wireless communications over the wireless network. For example, a base station manages a wireless connection with a user equipment (UE) connected to the wireless network. The base station determines the configuration for the wireless connection, such as the bandwidth, timing, and protocol for the wireless connection.

[0002] The quality of service between a UE and a base station may be degraded by many factors such as signal strength loss, bandwidth limitations, interfering signals, etc. This is especially true for UEs operating at the cell edge, which frequently suffer from poor signal quality. Many solutions have been developed to address the cell edge problem that occurs in certain wireless communication systems. However, the techniques for forming a coordinated set of user equipment lack the ability to form a coordinated set of user equipment in situations where the user equipment cannot connect to a base station individually. Summary of the invention

[0003] This summary is provided to introduce a simplified concept of coordinating user device selection. The simplified concept will be further described below in the detailed description. This summary is neither intended to identify essential features of the claimed subject matter nor to be used to determine the scope of the claimed subject matter.

[0004] In various aspects, methods, devices, systems, and apparatuses are described for a first user equipment (UE) to join a first user equipment coordination set (UECS) in a wireless communication network, wherein the first user equipment receives an indication of an allocation of air interface resources for UECS synchronization signals. The first UE monitors the air interface resources for UECS synchronization signals and receives one or more UECS synchronization signals for the first UECS from a second UE acting as a coordinating UE for the first UECS. The first UE transmits a first UECS-access-request to a second UE and receives a first UECS-access-response from the second UE, the first UECS-access-response indicating that the first UE is included in the first UECS. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Details of one or more aspects of coordinating user device selection are described below. The same reference numerals are used in different instances in the specification and drawings to indicate similar elements:

[0006] Figure 1 An example operating environment is illustrated in which aspects of coordinating user device selection can be implemented.

[0007] Figure 2 An example equipment diagram illustrating user equipment and a serving cell base station is shown.

[0008] Figure 3An example block diagram of a wireless network stack model is illustrated in which various aspects of coordinating user equipment selection can be implemented.

[0009] Figure 4 An example environment is illustrated in which various aspects of coordinating user device selection can be implemented.

[0010] Figure 5 Example data and control transactions between devices in a user equipment-coordinating set for scheduling a user equipment as a coordinating user equipment in a user equipment-coordinating set according to aspects of coordinating user equipment selection are illustrated.

[0011] Figure 6 Additional example data and control transactions between devices of a user equipment-coordination set for switching a user equipment from a first user equipment-coordination set to a second user equipment-coordination set according to aspects of coordinated user equipment selection are illustrated.

[0012] Figure 7

[0013] Illustrated are example methods of coordinating user equipment selection as generally associated with scheduling user equipment as a coordinating user equipment in a user equipment-coordinating set in accordance with aspects of the techniques described herein. DETAILED DESCRIPTION

[0013] This document describes techniques and apparatus for selecting, by a user equipment (UE) in a User Equipment Coordination Set (UECS), a coordinating UE in the UECS. Sharing of the role of a coordinating UE by UEs in the UECS can be scheduled in a round-robin manner. Selection criteria can be used to determine which UE or UEs in the UECS will provide better performance in the role of a coordinating UE.

[0014] The UECS is formed by assigning a group of multiple UEs to operate together similar to a distributed antenna for the benefit of a specific UE (e.g., a target UE). The UECS includes a coordination UE that coordinates the joint transmission and reception of downlink and / or uplink signals for the target UE or multiple target UEs in the UECS. By combining the antennas and transmitters of multiple UEs in the UECS, the effective transmit power of the target UE is significantly increased, and the effective signal quality is greatly improved.

[0015] Multiple UEs can each receive downlink data transmission from a base station. Unlike traditional relay technologies, these UEs do not decode downlink transmissions into data packets and then forward the data packets to a destination. Instead, the UE demodulates and samples the downlink transmission to generate I / Q samples. The UE determines where to forward the I / Q samples of the downlink transmission, such as to a coordinating UE for decoding. Note that a single UE can have the roles of a coordinating UE and a target UE at the same time. In various aspects, the target UE may be included in a subset of the target UEs within the UECS. The coordinating UE receives I / Q samples from other UEs in the UECS and stores the I / Q samples in a buffer memory for decoding. However, if the target UE is a coordinating UE, the target UE does not forward the I / Q samples wirelessly to itself. Then, the coordinating UE synchronizes and decodes the stored I / Q samples into data packets for transmission to (multiple) target UEs. Therefore, the processing of the I / Q samples occurs at the coordinating UE. In this way, the UECS acts as a distributed antenna for the target UE.

[0016] Several UEs are able to monitor a base station, but individually, each UE cannot reliably communicate with the base station. In this case, several UEs are able to form a UECS to communicate with the base station without the base station determining the configuration of the UECS and / or without the base station selecting a coordinating UE for the UECS. In the absence of configuration from the base station, especially in the absence of one UE indicating a preference to become a coordinating UE, the UEs in the UECS require a technique for selecting a coordinating UE for the UECS.

[0017] In one aspect, multiple UEs in the UECS can take turns acting as coordinating UEs for the UECS. For example, the UEs can use a cyclic schedule to assign time intervals (time periods) to the UEs, wherein each UE in the schedule acts as the coordinating UE for the current time interval (time period) before the next UE in the schedule acts as the coordinating UE for the next time interval in the schedule. In other examples, the UEs can be scheduled based on operating parameters, such as the amount of energy consumed to perform the coordinating UE task or the amount of uplink data transmitted (or downlink data received) while operating as a coordinating UE.

[0018] In an alternative or additional aspect, one or more characteristics of the UE in the UECS can be used to select a coordinating UE or a subset of UEs to participate in the cyclic scheduling. For example, the one or more characteristics include battery and / or charging status, uplink feedback received from the base station, uplink transmit power from the UE, signal strength of the signal received from the base station, uplink throughput of the UE, sidelink throughput of the UE, and / or the number of base stations receiving uplink signals from the UE.

[0019] Many UEs are mobile devices, and UEs can move in or out of the range of other UEs. For example, a UE can be part of a first UECS formed with other UEs in a moving bus. When the user of the UE gets off the bus, the UE moves out of the range of other UEs in the first UECS. The UE then needs to find other UEs that are already members of another UECS or with which the UE can form another UECS. In other aspects, the coordinating UE of the UECS periodically broadcasts a synchronization signal identifying the current coordinating UE to other UEs in the UECS. A UE searching for a UECS to join can receive the synchronization signal and request to join the UECS. On the other hand, when a first coordinating UE in a first UECS receives a synchronization signal from a second coordinating UE in a second UECS, the first coordinating UE can stop transmitting its synchronization signal and join the second UECS. In addition, the first coordinating UE can switch its associated UE to the second UECS.

[0020] Example Environment

[0021] Figure 1An example environment 100 is illustrated, which includes a plurality of user equipments 110 (UE 110), illustrated as UE 111, UE 112, UE 113, and UE 114. When within the communication range of a base station, each UE 110 can communicate with one or more base stations 120 (illustrated as base stations 121 and 122) via one or more wireless communication links 130 (wireless links 130), illustrated as wireless links 131 and 132. When individual UEs such as UE 111, UE 112, and UE 113 are individually out of the communication range of a base station, the UEs can form a UECS and communicate with the base station using joint transmission and joint reception. Each UE 110 in the UECS (illustrated as UE 111, UE 112, and UE 113) can communicate with a coordinating UE of the UECS and / or a target UE in the UECS through one or more local wireless network connections (e.g., WLAN, Bluetooth, NFC, personal area network (PAN), WiFi-Direct, IEEE 802.15.4, ZigBee, Thread, millimeter wavelength communication (mmWave), etc.) such as local wireless network connections 133, 134, and 135. Although illustrated as a smart phone, the UE 110 may be implemented as any suitable computing or electronic device, such as a mobile communication device, a modem, a cellular phone, a gaming device, a navigation device, a media device, a laptop computer, a desktop computer, a tablet computer, a smart home appliance, a vehicle-based communication system, an Internet of Things (IoT) device (e.g., a sensor node, a controller / actuator node, a combination thereof), etc. The base station 120 (e.g., an evolved universal terrestrial radio access network Node B, E-UTRAN Node B, evolved Node B, eNodeB, eNB, next generation Node B, gNode B, gNB, ng-eNB, etc.) can be implemented in a macro cell, a micro cell, a small cell, a pico cell, a distributed base station, etc., or any combination or future evolution thereof.

[0022] The base station 120 communicates with the UECS or the user equipment 110 using radio links 131 and 132, respectively, which may be implemented as any suitable type of radio links. The radio links 131 and 132 include control and data communications, such as downlinks of data and control information transferred from the base station 120 to the user equipment 110, uplinks of other data and control information transferred from the user equipment 110 to the base station 120, or both. The radio link 130 may include one or more radio links (e.g., radio links) or bearers implemented using any suitable communication protocol or standard or combination of communication protocols or standards, such as the third generation partnership project long term evolution (3GPP LTE), the fifth generation new radio (5G NR), etc. Multiple radio links 130 may be aggregated in carrier aggregation to provide higher data rates for the UE 110. Multiple radio links 130 from multiple base stations 120 may be configured for coordinated multi-point (CoMP) communication with the UE 110.

[0023] The base stations 120 are collectively referred to as a radio access network 140 (e.g., RAN, Evolved Universal Terrestrial Radio Access Network, E-UTRAN, 5G NR RAN, or NR RAN). The base stations 121 and 122 in the RAN 140 are connected to the core network 150. The base stations 121 and 122 are connected to the core network 150 at 102 and 104, respectively, via an NG2 interface for control plane signaling and an NG3 interface for user plane data communication when connected to a 5G core network, or an S1 interface for control plane signaling and user plane data communication when connected to an evolved packet core (EPC) network. The base stations 121 and 122 are capable of communicating at 106 using an Xn application protocol (XnAP) over an Xn interface or using an X2 application protocol (X2AP) over an X2 interface to exchange user plane and control plane data. The user equipment 110 can be connected to a public network such as the Internet 160 via the core network 150 to interact with a remote service 170.

[0024] Example Device

[0025] Figure 2 An example device diagram 200 illustrates a user device and a base station. In various aspects, the device diagram 200 describes a device capable of implementing various aspects of coordinating user device selection. Figure 2 In FIG. 1 , there are multiple UEs 110 and base stations 120. The multiple UEs 110 and base stations 120 may include Figure 2Additional functions and interfaces omitted. UE 110 includes an antenna 202, a radio frequency front end 204 (RF front end 204), and a radio frequency transceiver (e.g., an LTE transceiver 206 and a 5G NR transceiver 208) for communicating with a base station 120 in 5G RAN 141 and / or E-UTRAN 142. UE 110 includes one or more additional transceivers (e.g., a local wireless network transceiver 210) for communicating with at least a coordinating UE of the UECS via one or more wireless local wireless networks (e.g., WLAN, Bluetooth, NFC, a personal area network (PAN), WiFi-Direct, IEEE 802.15.4, ZigBee, Thread, mmWave, etc.). The RF front end 204 of UE 110 is capable of coupling or connecting the LTE transceiver 206, the 5G NR transceiver 208, and the local wireless network transceiver 210 to the antenna 202 to facilitate various types of wireless communications.

[0026] The antenna 202 of the UE 110 may include an array of multiple antennas configured to be similar or different from each other. The antenna 202 and the RF front end 204 can be tuned and / or tunable to one or more frequency bands defined by the 3GPP LTE and 5G NR communication standards and implemented by the LTE transceiver 206 and / or the 5G NR transceiver 208. Additionally, the antenna 202, the RF front end 204, the LTE transceiver 206, and / or the 5G NR transceiver 208 can be configured to support beamforming for transmission and reception of communications with the base station 120. As an example and not limitation, the antenna 202 and the RF front end 204 can be implemented to operate in sub-gigahertz bands, sub-6 GHz bands, and / or above 6 GHz bands defined by the 3GPP LTE and 5G NR communication standards. Additionally, the RF front end 204 can be tuned and / or tunable to one or more frequency bands defined and implemented by the local wireless network transceiver 210 to support transmission and reception of communications with other UEs in the UECS over the local wireless network.

[0027] UE 110 includes sensors 212 that can be implemented to detect various properties such as temperature, supplied power, power usage, battery status, etc. Thus, sensor 212 may include any one or a combination of a temperature sensor, a thermistor, a battery sensor, and a power usage sensor.

[0028] UE 110 also includes a processor 214 and a computer readable storage medium 216 (CRM 216). Processor 214 can be a single core processor or a multi-core processor composed of various materials such as silicon, polysilicon, high-K dielectrics, copper, etc. The computer readable storage medium described herein excludes propagating signals. CRM 216 can include any suitable memory or storage device, such as a random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or flash memory that can be used to store device data 218 of UE 110. Device data 218 includes user data, multimedia data, beamforming codebooks, applications, and / or operating systems of UE 110, which can be executed by processor 214 to enable user plane communications, control plane signaling, and user interaction with UE 110.

[0029] The CRM 216 also includes a communication manager 220 (e.g., a communication manager application 220). Alternatively or additionally, the communication manager 220 can be implemented in whole or in part as hardware logic or circuitry that is integrated or separate from other components of the UE 110. In at least some aspects, the communication manager 220 configures the RF front end 204, the LTE transceiver 206, the 5G NR transceiver 208, and / or the local wireless network transceiver 210 to implement the techniques described herein for coordinating user equipment selection.

[0030] Figure 2 The device diagram of the base station 120 shown in includes a single network node (e.g., gNode B). The functionality of the base station 120 can be distributed across multiple network nodes or devices and can be distributed in any manner suitable for performing the functions described herein. The base station 120 includes an antenna 252, a radio frequency front end 254 (RF front end 254), one or more LTE transceivers 256, and / or one or more 5G NR transceivers 258 for communicating with the UE 110. The RF front end 254 of the base station 120 can couple or connect the LTE transceiver 256 and the 5G NR transceiver 258 to the antenna 252 to facilitate various types of wireless communications. The antenna 252 of the base station 120 can include an array of multiple antennas configured to be similar or different from each other. The antenna 252 and the RF front end 254 can be tuned to and / or tunable to one or more frequency bands defined by the 3GPP LTE and 5G NR communication standards and implemented by the LTE transceiver 256 and / or the 5G NR transceiver 258. Additionally, the antenna 252, RF front end 254, LTE transceiver 256 and / or 5G NR transceiver 258 may be configured to support beamforming, such as massive MIMO, for transmission and reception of communications with any UE 110 in the UECS.

[0031] The base station 120 also includes a processor 260 and a computer readable storage medium 262 (CRM 262). The processor 260 may be a single core processor or a multi-core processor composed of various materials such as silicon, polysilicon, high-K dielectrics, copper, etc. The CRM 262 may include any suitable memory or storage device, such as a random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or flash memory that may be used to store device data 264 of the base station 120. The device data 264 includes network scheduling data, radio resource management data, beamforming codebooks, applications, and / or operating systems of the base station 120, which can be executed by the processor 260 to enable communication with the UE 110.

[0032] The CRM 262 also includes a base station manager 266 (e.g., a base station manager application 266). Alternatively or additionally, the base station manager 266 can be implemented in whole or in part as hardware logic or circuitry that is integrated or separate from other components of the base station 120. In at least some aspects, the base station manager 266 configures the LTE transceiver 256 and the 5G NR transceiver 258 for communication with the UE 110 and with the core network. The base station 120 includes an inter-base station interface 268, such as an Xn and / or X2 interface, which the base station manager 266 configures to exchange user plane data and control plane data between another base station 120 to manage the communication of the base station 120 with the UE 110. The base station 120 includes a core network interface 270, which the base station manager 266 configures to exchange user plane data and control plane data with core network functions and entities.

[0033] Network stack

[0034] Figure 3 An example block diagram 300 of a wireless network stack model 300 (stack 300) is illustrated. Stack 300 represents a communication system of an example environment 100 in which various aspects of coordinating user device selection can be implemented. Stack 300 includes a user plane 302 and a control plane 304. The upper layers of user plane 302 and control plane 304 share common lower layers in protocol stack 300. A wireless device such as UE 110 or base station 120 implements each layer as an entity for communicating with another device using a protocol defined for that layer. For example, UE 110 uses a packet data convergence protocol (PDCP) entity to communicate with a peer PDCP entity in base station 120 using PDCP.

[0035] The shared lower layers include a physical (PHY) layer 306, a medium access control (or media access control) (MAC) layer 308, a radio link control (RLC) layer 310, and a PDCP layer 312. The PHY layer 306 provides hardware specifications for devices to communicate with each other. Thus, the PHY layer 306 establishes how devices connect to each other, assists in managing how communication resources are shared among devices, etc.

[0036] The MAC layer 308 specifies how data is transferred between devices. Generally, the MAC layer 308 provides a way to encode and decode packets of data being transmitted into bits as part of a transport protocol.

[0037] The RLC layer 310 provides data transfer services to higher layers in the protocol stack 300. Generally, the RLC layer 310 provides error correction, packet segmentation and reassembly, and management of data transfer in various modes such as acknowledged mode, unacknowledged mode, or transparent mode.

[0038] The PDCP layer 312 provides data transfer services to higher layers in the protocol stack 300. In general, the PDCP layer 312 provides transfer, header compression, ciphering, and integrity protection of user plane 302 and control plane 304 data.

[0039] Above the PDCP layer 312, the stack is split into a user plane 302 and a control plane 304. The layers of the user plane 302 include an optional service data adaptation protocol (SDAP) layer 314, an Internet Protocol (IP) layer 316, a transmission control protocol / user datagram protocol (TCP / UDP) layer 318, and an application layer 320 that uses the wireless link 106 to transfer data. The optional SDAP layer 314 exists in the 5G NR network. The SDAP layer 314 maps a quality of service (QoS) flow for each data radio bearer and marks a QoS flow identifier in uplink and downlink data packets for each packet data session. The IP layer 316 specifies how to transfer data from the application layer 320 to the destination node. The TCP / UDP layer 318 is used to verify that the data packet intended to be transferred to the destination node has arrived at the destination node, using TCP or UDP for data transfer by the application layer 320. In some implementations, the user plane 302 may also include a data service layer (not shown) that provides data transport services to transport application data, such as IP packets including web browsing content, video content, image content, audio content, or social media content.

[0040] The control plane 304 includes a radio resource control (RRC) layer 324 and a non-access stratum (NAS) layer 326. The RRC layer 324 establishes and releases connections and radio bearers, broadcasts system information, or performs power control. The RRC layer 324 also controls the resource control state of the UE 110 and causes the UE 110 to perform operations according to the resource control state. Example resource control states include a connected state (e.g., an RRC connected state) or a disconnected state, such as an inactive state (e.g., an RRC inactive state) or an idle state (e.g., an RRC idle state). Generally speaking, if the UE 110 is in a connected state, the connection with the base station 120 is active. In an inactive state, the connection with the base station 120 is suspended. If the UE 110 is in an idle state, the connection with the base station 120 is released. Typically, the RRC layer 324 supports 3GPP access but does not support non-3GPP access (e.g., WLAN communication).

[0041] The NAS layer 326 provides support for mobility management (e.g., using the fifth generation mobility management (5GMM) layer 328) and packet data bearer contexts (e.g., using the fifth generation session management (5GSM) layer 330) between the UE 110 and entities or functions in the core network, such as the access and mobility management function 152 (AMF 152) of the 5GC 150. The NAS layer 326 supports both 3GPP access and non-3GPP access.

[0042] In UE 110 , each layer in both user plane 302 and control plane 304 of stack 300 interacts with corresponding peer layers or entities in base station 120 , core network entities or functions, and / or remote services to support user applications and control operations of UE 110 in RAN 140 .

[0043] User Equipment - Coordination Set

[0044] Figure 4 An example implementation 400 of coordinating user equipment selection is illustrated. The illustrated example includes base station 121, UE 111, UE 112, and UE 113. Although for clarity of illustration, Figure 4 The UECS in FIG. 1 is illustrated as including three UEs, but any number of UEs greater than one may be included in the UECS. In one example, Figure 4 Each UE illustrated in FIG. 4 has limited transmit power, which may make it difficult to transmit uplink data to base station 121. This may be due at least in part to the UE being outside the communication range 402 of the cell provided by base station 121 or the UE being in a transmission-challenged location (e.g., a basement, an urban canyon, etc.), such that the individual UE lacks sufficient link budget to communicate with base station 121. Alternatively or additionally, Figure 4Each UE shown in 404 may have difficulty reliably receiving downlink signals from base station 121 because, for example, the UE is outside the communication range 402 of the cell or in a reception-challenged location.

[0045] Using the techniques described herein, a group of UEs (e.g., UE 111, UE 112, and UE 113) can form a UECS (e.g., UECS 404) using air interface resources allocated within RAN 140 to synchronize and form the UECS. Based on user input or predefined settings, each UE can choose to participate or not participate in the UECS. The effective transmit power of the target UE 112 can increase significantly (e.g., linearly) with the number of UEs in the UECS, which can greatly improve the link budget of the target UE 112.

[0046] In addition, UE coordination can be based on a spatial beam or timing advance associated with each UE, or both. For example, for beamforming or massive MIMO, it may be desirable that all UEs within a UECS can receive the same signal from a base station. Therefore, all UEs within a UECS can be geographically close to each other, for example, within a threshold distance of a coordinated UE in the UECS. In this way, the UEs in the UECS can each be in the same beam or in beams close to each other. The timing advance can indicate the distance between the UE and the base station. Similar timing advances for each UE in the group indicate that those UEs are approximately the same distance from the base station. UEs that are within a predefined distance from each other and that are all at a similar distance from the base station can work together in the UECS in a distributed manner to improve signal strength and quality, thereby benefiting the target UEs in the UECS.

[0047] Communication among UEs can be performed using a local wireless network 406 (such as PAN, NFC, Bluetooth, WiFi-Direct, local mmWave links, etc.). In this example, all three of UEs 111, 112, and 113 receive RF signals from base station 121. UE 111, UE 112, and UE 113 demodulate the RF signal to generate a baseband I / Q analog signal, and sample the baseband I / Q analog signal to generate I / Q samples. UE 112 and UE 113 use the local wireless network 406 to forward the I / Q samples together with system timing information (e.g., system frame number (SFN)) to the coordinating UE 111 using the local wireless network transceiver 210. The coordinating UE 111 then uses the timing information to synchronize and combine the I / Q samples, and processes the combined signal to decode the data packet for the target UE 112. The coordinating UE 111 then transmits the data packet to the target UE 112 using the local wireless network 406.

[0048] When the target UE 112 has uplink data to send to the base station 121, the target UE transmits the uplink data to the coordinating UE 111, which distributes the uplink data as I / Q samples to each UE in the UECS 404 using the local wireless network 406. The base station 121 receives the jointly transmitted uplink data from the UEs 111, 112, 113, and processes the combined signal to decode the uplink data from the target UE 112.

[0049] Coordinate user equipment scheduling

[0050] The set of UEs 110 is able to monitor base station 121, but individually each UE 110 is unable to reliably communicate with base station 121. In this case, the set of UEs 110 is able to form a UECS to communicate with base station 121 without base station 121 determining the configuration of the UECS and / or selecting a coordinating UE for the UECS. Although various criteria (discussed below) may be used to determine the best candidate UE to become a coordinating UE, there may also be situations where UEs in the UECS share the role of a coordinating UE by scheduling multiple UEs to act as coordinating UEs based on criteria such as time slots, power consumed to perform coordinating UE operations, and / or the amount of data transferred while acting as coordinating UEs.

[0051] In one aspect, multiple UEs in the UECS use a cyclic schedule to assign time intervals to the UEs, wherein each UE in the schedule acts as a coordinating UE for the current time interval before the next UE in the schedule acts as a coordinating UE for the next time interval in the schedule. To facilitate scheduling, each UE 110 in the UECS has a unique identifier within the UECS. For example, a unique identifier can be assigned to each UE in the order in which the UE joins the UECS. In another example, the unique identifier can be an address of a local wireless network interface assigned to the UE, such as a MAC address, an IEEE extended unique identifier (EUI), a physical layer address of a local wireless network interface, etc. In another example, the unique identifier can be an address assigned to the UE, such as an international mobile equipment identity (IMEI), etc. In addition, in order to reduce the overhead of communications within the UECS, short addressing can be used, wherein the short address is derived from a longer universal unique identifier (e.g., EUI or IMEI).

[0052] In one aspect of the cyclic scheduling, each UE 110 in the UECS is sequentially used as a coordinating UE based on the UE's unique identifier. For example, each UE 110 is used as a coordinating UE for a fixed time period (e.g., 10 seconds), and then the next UE 110 in the sequence is used as a coordinating UE. The scheduling of the UE as a coordinating UE continues until each UE in the UECS has been used as a coordinating UE, and the cyclic scheduling then continues from the first UE in the sequence.

[0053] In one option, if UE 110 is used as a coordinating UE, the UE can choose not to participate in joint transmission to and / or joint reception from base station 121 in order to save battery capacity of the UE (e.g., by not turning on its power amplifier to transmit to the base station). In another option, the amount of time each UE 110 is used as a coordinating UE can be recorded by the UECS to achieve load balancing within the round-robin schedule to ensure that no single UE or subset of UEs is used as a coordinating UE for an excessive amount of time. In another option, the UECS can record the remaining battery capacity of each UE 110 in the UECS to achieve load balancing within the round-robin schedule to ensure that no UE or subset of UEs has its battery depleted due to being used as a coordinating UE.

[0054] In another aspect of the cyclic scheduling, each UE 110 in the UECS sequentially serves as a coordinating UE until the UE has expended an amount of energy associated with performing operations of the coordinating UE (e.g., a predetermined amount of energy), and then the next UE 110 in the sequence serves as the coordinating UE. In another aspect of the cyclic scheduling, each UE 110 in the UECS sequentially serves as a coordinating UE until the UE has transferred an amount of data associated with performing operations of the coordinating UE (e.g., a predetermined amount of data transferred over a local wireless network, a cellular network, or both), and then the next UE 110 in the sequence serves as the coordinating UE.

[0055] When the current coordinating UE decides to transfer the role of the coordinating UE to another UE 110 (new coordinating UE), the current coordinating UE sends one or more broadcast coordinator-change messages to all UEs 110 in the UECS to indicate that the other UEs 110 are new coordinating UEs, after which the new coordinating UE can start transmitting synchronization signals for the UECS and the previous coordinating UE stops transmitting synchronization signals. The current coordinating UE can determine to transfer the coordination role based on reaching the value of the cyclic scheduling parameter (e.g., the end of its time period, reaching the power level consumed to perform the coordinating UE operation and / or the amount of data transferred while acting as a coordinating UE), or the current coordinating UE can determine to delay the transfer until after the ongoing UECS operation (e.g., joint processing, joint transmission and / or joint reception) is completed to avoid interruption and / or increase the latency of the UECS operation. Optionally or additionally, scheduling-related information (e.g., the current cyclic schedule, parameters recorded for the UE in the cyclic schedule, etc.) can be included in the broadcast message or directly forwarded from the previous coordinating UE to the new coordinating UE.

[0056] Coordinate user device selection

[0057] One or more characteristics of UE 110 in UECS can be used to select a coordinating UE or a subset of UEs to participate in cyclic scheduling. In one aspect, the battery and / or charging status of each UE can be used to select the UE. For example, the UE 110 with the largest remaining battery power can be selected as the coordinating UE, or one or more UEs 110 exceeding a threshold of the remaining battery power can be selected as the coordinating UE for cyclic scheduling. In another example, one or more UEs that are externally powered or connected to a battery charger can be selected instead of UE 110 that operates according to battery power.

[0058] In another aspect, the uplink or downlink status of each UE can be used to select UE 110 as a coordination UE. For example, a UE 110 that delivers the maximum uplink signal power to base station 121 and / or receives the strongest downlink signal (e.g., broadcast signal) from base station 121 is selected as a coordination UE. In another example, one or more UEs 110 that exceed a threshold or have the highest N values ​​for uplink (e.g., uplink signal power) and / or downlink (e.g., received downlink signal strength) status can be selected as coordination UEs for cyclic scheduling.

[0059] In another aspect, uplink transmit power can be used to select UEs 110 as coordinating UEs to reduce total transmit power interference in RAN 140. For example, UEs 110 that require minimum transmit power to communicate with base station 121 are selected as coordinating UEs. In another example, one or more UEs 110 that are below a threshold for uplink transmit power or have the lowest N values ​​for uplink transmit power can be selected as coordinating UEs for round-robin scheduling.

[0060] In another aspect, the number of base stations receiving uplinks from the UE can be used to select UE 110 as a coordinating UE. For example, a UE 110 that can reach the maximum number of base stations is selected as a coordinating UE. When CoMP communication is used, this UE 110 is the UE with the best uplink. In another example, one or more UEs 110 that exceed a threshold or have the highest N values ​​for the number of base station uplinks can be selected as coordinating UEs for cyclic scheduling.

[0061] In another aspect, the UE 110 with the highest uplink or sidelink data throughput is selected as the coordinating UE. In another example, one or more UEs 110 exceeding a threshold or having the highest N values ​​for uplink or sidelink data throughput can be selected as coordinating UEs for cyclic scheduling.

[0062] UECS Synchronization

[0063] In various aspects, a coordinating UE within a UECS periodically broadcasts a synchronization signal to announce the presence of the coordinating UE. When a cyclic schedule is used, the synchronization signal announces the current coordinating UE, indicating that the coordinating UE can be used to search for any UE to join the UECS, or can be used by another coordinating UE to determine to suspend operation as a coordinating UE.

[0064] The UECS synchronization signal has a specific format in terms of time, frequency and / or code resources so that other UE 110 can detect the UECS synchronization signal transmitted by the coordinating UE. The UECS synchronization signal can include an identifier of the coordinating UE and / or the UECS coordinated by the coordinating UE. The UE 110 in the UECS or searching for the UECS to be joined monitors the air interface resources allocated to the synchronization signal to maintain or establish a connection with the UECS. For example, the UECS synchronization signal is transmitted every 10 milliseconds using the specified air interface resources. For example, the RAN 140 (e.g., the base station 121) can allocate air interface resources for use by the UECS. The RAN 140 can allocate air interface resources in one or more radio frequency bands supported by the RAN 140. The RAN 140 can allocate one or more groups of air interface resources so that multiple UECS can operate within the RAN 140. The configuration of the UECS air interface resources can be provided to the UE 110 using any suitable means (such as a broadcast message from the base station 121 in the RAN 140, in the system information block (SIB) etc.). In another example, RAN 140 may instruct configuration of UECS synchronization signals in an unlicensed radio band, such as a radio band used for WLAN communications, to enable UEs to form and synchronize using radio spectrum in addition to the licensed spectrum used by RAN 140 .

[0065] In another aspect, a first coordinating UE (a UE associated with itself) monitors air interface resources allocated for use by the UECS, and if the first coordinating UE detects a synchronization signal from a second coordinating UE of a second UECS, the first coordinating UE can choose to stop acting as a coordinating UE (e.g., stop transmitting a UECS synchronization signal). The first coordinating UE can join the second UECS, and can optionally or additionally hand over UEs associated with the first UECS to the second UECS.

[0066] In yet another aspect, the synchronization signal can be used to avoid having multiple UEs act as coordinating UEs for the UECS. For example, a first coordinating UE for the UECS monitors air interface resources allocated for use by the UECS, and if the first coordinating UE transmits a UECS synchronization signal and then detects a synchronization signal from a second coordinating UE identifying that the second coordinating UE is a coordinator for the same UECS as the first coordinating UECS, the first coordinating UE terminates acting as a coordinating UE for the UECS (e.g., stops transmitting the UECS synchronization signal).

[0067] In various aspects, any UE 110 searching for a UECS to join monitors the air interface resources allocated by the RAN 140 for the UECS synchronization signal. If the UE 110 detects the synchronization signal of the coordinating UE, the UE 110 can join the UECS of the coordinating UE. For example, the UE 110 can send a UECS-access-request message or signal to the coordinating UE requesting to join the UECS. The UE 110 can transmit the UECS-access-request message or signal at a pre-established time interval after the received synchronization signal or at any random time between synchronization signals. Optionally, the coordinating UE 110 can transmit a UECS-access-response message or signal to the joining UE 110 indicating that the request to join the UECS has been accepted. In addition, if the joining UE 110 fails to receive a UECS-Access-Response (e.g., due to interference or collision with a UECS-Access-Request message or signal transmitted by a third UE), the joining UE 110 can retry joining the UECS, such as by using a backoff and retry technique, in which the joining UE determines a random backoff time before retransmitting the UECS-Access-Request message or signal to avoid collision with another UE attempting to join the UECS. After the UE 110 has joined the UECS, the newly joined UE 110 can begin participating in the selection and / or round-robin scheduling of acting as a coordinating UE for the UECS.

[0068] In another aspect, if UE 110 loses its connection with the coordinating UE (e.g., the coordinating UE is turned off by the user), UE 110 waits for a random time interval and monitors the air interface resources allocated by RAN 140 for the UECS synchronization signal to determine whether there is a new coordinating UE for the UECS. If UE 110 does not detect the synchronization signal for the UECS, UE 110 can decide to become a coordinating UE by periodically transmitting a synchronization signal for the UECS, or UE 110 can decide to form a new UECS by transmitting a synchronization signal identifying a new UECS. After UE 110 becomes a coordinating UE for an existing UECS or a new UECS, cyclic scheduling of UEs acting as coordinating UEs can be performed. Optionally or additionally, the coordinating UE can change the timing of transmitting the synchronization signal in the absence of other UEs in the UECS, such as slowing down the synchronization signal transmission to reduce the power consumption of the coordinating UE.

[0069] Data and control transactions

[0070] Figure 5 The diagram illustrates data and control transactions between devices for scheduling a UE as a coordinated set of user equipment of a coordinated UE of a UECS according to various aspects of coordinated user equipment selection. Although not shown for clarity of illustration, the Figure 5Various confirmations of the messages illustrated in the figure are used to ensure reliable operation of coordinating user equipment selection.

[0071] At 505, UE 111 is searching for a UECS to join. UE 112 and UE 113 are members of UECS 404, with UE 112 currently acting as a coordinating UE for UECS 404. To locate a UECS to join, UE 111 monitors air interface resources allocated by RAN 140 for UECS synchronization signals.

[0072] At 510, UE 112 in its role as a coordinating UE periodically transmits a UECS synchronization signal for the UECS using the air interface resources allocated for the UECS synchronization signal by RAN 140. Although not illustrated for clarity, UE 112 periodically transmits a synchronization signal for the UECS from the time it assumes the role of a coordinating UE until it stops acting as a coordinating UE.

[0073] At 515, after receiving one or more UECS synchronization signals for UECS 404, UE 111 transmits a UECS-Access-Request to UE 112 requesting to join UECS 404. At 520, UE 112 sends a UECS-Access-Response message to UE 111 indicating whether coordinating UE 112 has included UE 111 in UECS 404. If coordinating UE 112 determines that UE 111 is not included in UECS 404, UE 111 can continue to search for a UECS synchronization signal for another UECS to join ( Figure 5 Not shown) or retry joining UECS 404 ( Figure 5 (not shown in the figure).

[0074] At 525, assuming that UE 112 decides to include UE 111 in UECS 404, UE 112 includes UE 111 in a recurring schedule of UEs that can serve as a coordinating UE for UECS 404. As described above, various criteria may be used to determine whether UE 111 can serve as a coordinating UE. Optionally, UE 112 as a coordinating UE may evaluate one or more criteria that determine whether to include or exclude UE 111 in a recurring schedule.

[0075] At 530, UE 111, UE 112, and UE 113 operate as a UECS that performs operations such as joint transmission, joint reception, and / or joint processing. At 535, based on the cyclic schedule, UE 112 infers its turn to act as a coordinating UE by broadcasting a coordinator-change message to other UEs in UECS 404. The coordinator-change message includes an indication that UE 111 is a new coordinating UE for UECS 404. Optionally or in addition, the coordinator-change message can include additional information, such as the parameters of the above-mentioned record, the current copy of the cyclic schedule, etc. At 540, after transmitting the coordinator-change message, UE 112 stops transmitting the UECS synchronization signal for UECS 404.

[0076] At 545, UE 111 begins to periodically transmit synchronization signals for UECS 404 using the air interface resources allocated by RAN 140 for UECS synchronization signals. At 550, based on the cyclic schedule, UE 111 infers its turn to serve as the coordinating UE by broadcasting a coordinator-change message to other UEs in UECS 404. The coordinator-change message includes an indication that UE 113 is the new coordinating UE for UECS 404, and (not shown) UE 111 stops transmitting UECS synchronization signals. UE 113 begins to periodically transmit synchronization signals for UECS 404, and the cyclic schedule continues while UECS 404 operates.

[0077] Figure 6 The diagram illustrates data and control transactions between devices of a user equipment coordination set for handing over a UE from a first UECS to a second UECS according to aspects of coordinating user equipment selection. Although not shown for clarity of illustration, the Figure 6 Various confirmations of the messages illustrated in the figure are used to ensure reliable operation of coordinating user equipment selection.

[0078] At 605, UE 111, UE 112, and UE 113 operate as a first UECS as described above, and UE 114 may include a first UECS for clarity. Figure 6 At 610, UE 113 is acting as a coordinating UE for the first UECS 602 and transmits a UECS synchronization signal for the first UECS 602.

[0079] At 615, UE 113 leaves the first UECS 602. For example, UE 113 has been turned off or UE 113 has moved out of the local wireless communication range of the first UECS 602. At 620, based on monitoring the air interface resources allocated by RAN 140 for UECS synchronization signals, UE 111 determines that no UECS synchronization signals for the first UECS 602 have been received within a threshold time period. At 625, UE 111 decides to assume the role of a coordinating UE for UECS 602, and at 630, begins to periodically transmit UECS synchronization signals for the first UECS 602 using the air interface resources allocated by RAN 140 for UECS synchronization signals. Alternatively (not shown), if UE 111 is unable (e.g., has low remaining battery power) to act as a coordinating UE for UECS 602, UE 111 can decide to suspend participation in the first UECS 602 or continue to monitor UECS synchronization signals from another UE in the first UECS 602.

[0080] At 635, UE 114 in its role as a coordinating UE for the second UECS 604 periodically transmits a UECS synchronization signal for the second UECS 604 using the air interface resources allocated for the UECS synchronization signal by RAN 140. Although not shown for clarity, UE 114 may periodically transmit a UECS synchronization signal for the second UECS 604 at 635. Figure 6 Those shown previously periodically transmit synchronization signals for the second UE CS 602, such as from the time it assumes the role of the coordinating UE until it ceases to act as a coordinating UE.

[0081] At 640, UE 111 receives the synchronization signal for second UECS 604. Even though UE 111 is acting as a coordinating UE for first UECS 602, UE 111 (and any other UEs in the UECS) may continue to monitor the air interface resources allocated by RAN 140 for UECS synchronization signals to find other UECSs operating nearby.

[0082] Based on receiving the synchronization signal for second UECS 604, UE 111 decides to join second UECS 604. For example, if first UECS 602 currently includes only UE 111 and UE 112, joining another UECS may improve joint communication performance of UE 111 and other UEs in the first UECS by participating in a UECS with a larger number of UEs.

[0083] At 645, UE 111 transmits a UECS-handover-request to UE 114 requesting to join UECS 604 (e.g., to merge the first UECS into the second UECS). For example, UE 111 includes the identity of the UE in the first UECS 602 in the UECS-handover-request, and transmits the UECS-handover-request to UE 114. At 650, UE 114 sends a UECS-handover-response message to UE 111 indicating whether UE 114 has included the UE from UECS 602 in UECS 604. At 655, assuming that the UECS-handover-response indicates that the UECS-handover-request is accepted, UE 111 transmits a coordinator-change message to other UEs in UECS 602. The coordinator-change message includes an indication that UE 114 is a coordinating UE for UECS 604. After the UEs from the first UECS 602 are included in the second UECS 604 , the UEs from the first UECS 602 can be included in the recurring schedule for the coordinated UEs of the second UECS 604 .

[0084] Example Method

[0085] Figure 7 An example method 700 for coordinating user equipment selection as generally associated with scheduling a UE as a coordinating UE in a UECS is illustrated. At 702, a user equipment (e.g., UE 111) receives an indication of an allocation of air interface resources for UECS synchronization signals. For example, RAN 140 allocates air interface resources for UECS synchronization signals within the RAN. The UE may receive an indication of the allocation as broadcast information from a base station in the RAN. The air interface resources allocated for the UECS synchronization signals may be in a licensed spectrum used by RAN 140, or may be in an unlicensed radio band (e.g., an unlicensed radio band used by local wireless network connections 133, 134, and 135).

[0086] At 704, the user equipment monitors the air interface resources to receive the UECS synchronization signal. For example, the user equipment uses the LTE transceiver 206, the 5G NR transceiver 208, and / or the local wireless network transceiver 210 to attempt to receive the UECS synchronization signal.

[0087] At 706, the user equipment receives a request from a coordinating UE for UECS (eg, Figure 5 The UE 112 in the RAN receives one or more UECS synchronization signals for the UECS. For example, the UE receives the UECS synchronization signals in one or more air interface resources allocated by the RAN 140.

[0088] At 708, the user equipment transmits a UECS-Access-Request to the coordinating UE. For example, the UE transmits a UECS-Access-Request message or signal requesting to join the UECS to the coordinating UE.

[0089] At 710, the user equipment receives a UECS-Access-Response from the coordinating UE. For example, the UE receives a UECS-Access-Response from the coordinating UE indicating that the coordinating user equipment has included the UE in the UECS or that the coordinating UE has rejected the request to join the UECS.

[0090] One or more aspects of coordination of user equipment selection reference Figure 7 Describe an example method 700. The order in which the method blocks are described is not intended to be interpreted as limiting, and any number of the described method blocks can be skipped, repeated, or combined in any order to implement a method or an alternative method. Typically, any of the components, modules, methods, and operations described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuits), manual processing, or any combination thereof. Some operations of the example methods can be described in the general context of executable instructions stored on a computer-readable storage memory that is local and / or remote to a computer processing system, and implementations can include software applications, programs, functions, etc. Alternatively or in addition, any of the functionality described herein can be performed at least in part by one or more hardware logic components such as, but not limited to, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chip (SoCs), complex programmable logic devices (CPLDs), etc.

[0091] Some examples are described below:

[0092] Example 1: A method for a first user equipment UE to join a first user equipment coordination set UECS in a wireless communication network, the method comprising the first user equipment:

[0093] receiving an indication of an allocation of air interface resources for a UECS synchronization signal;

[0094] monitoring the air interface resources to receive a UECS synchronization signal;

[0095] receiving one or more UECS synchronization signals for the first UECS from a second UE acting as a coordinating UE for the first UECS;

[0096] transmitting a first UECS-Access-Request to the second UE; and

[0097] A first UECS-access-response is received from the second UE, the first UECS-access-response indicating that the first UE is included in the first UECS.

[0098] Example 2: The method according to Example 1, the method comprising the first UE:

[0099] receiving a first coordinator-change message from the second UE, the first coordinator-change message indicating that the first UE is now acting as the coordinating UE for the first UECS; and

[0100] Based on receiving the first coordinator-change message, a UECS synchronization signal for the first UECS is periodically transmitted.

[0101] Example 3: The method of Example 2, wherein the coordinator-change message includes a round-robin schedule of UEs acting as the coordinating UE for the first UECS.

[0102] Example 4: The method of Example 3, wherein the cyclic schedule includes an indication of a criterion for scheduling a duration for each UE in the cyclic schedule to act as the coordinating UE, and wherein the criterion includes one or more of the following:

[0103] Duration;

[0104] the amount of power consumed to perform coordinated UE operations; or

[0105] The amount of data transferred while acting as the coordinating UE.

[0106] Example 5: The method according to Example 3 or Example 4, the method comprising the first UE:

[0107] including, based on the cyclic scheduling, in a second coordinator-change message, an indication that the third UE acts as a next coordinating UE for the first UECS;

[0108] transmitting the second coordinator-change message to a UE included in the first UECS; and

[0109] The periodic transmission of the UECS synchronization signal for the first UECS is suspended.

[0110] Example 6: The method of Example 5, wherein transmitting the second coordinator-change message comprises:

[0111] The second coordinator-change message is transmitted as a broadcast message to UEs included in the first UECS.

[0112] Example 7: The method according to Example 3 or Example 4, the method comprising the first UE:

[0113] receiving a second UECS-Access-Request from a fourth UE;

[0114] determining to include the fourth UE in the first UECS; and

[0115] A second UECS-access-response is transmitted to the fourth UE, the second UECS-access-response indicating that the fourth UE is included in the first UECS.

[0116] Example 8: The method according to Example 7, the method comprising the first UE:

[0117] The fourth UE is included in the cyclic scheduling.

[0118] Example 9: The method of Example 8, wherein including the fourth UE in the cyclic scheduling includes the first UE:

[0119] and evaluating one or more selection criteria for including the fourth UE in the cyclic scheduling, wherein the one or more selection criteria include:

[0120] The remaining battery power of the fourth UE;

[0121] a charging status of the fourth UE;

[0122] Uplink signal power to the base station;

[0123] downlink received signal strength from the base station;

[0124] uplink transmit power to the base station;

[0125] the number of uplinks from the fourth UE to the base station; or

[0126] The uplink data throughput of the fourth UE.

[0127] Example 10: The method of Example 9, wherein the one or more selection criteria are included in the second UECS-Access-Request.

[0128] Example 11: The method according to Example 1, the method comprising the first UE:

[0129] monitoring air interface resources to receive a UECS synchronization signal from the second UE after receiving the first UECS-access-response from the second UE; and

[0130] It is determined that the UECS synchronization signal has not been received from the second UE within a threshold time period.

[0131] Example 12: The method of Example 11, the method comprising the first UE:

[0132] determining to act as the coordinating UE for the first UECS; and

[0133] The UECS synchronization signal for the first UECS is periodically transmitted.

[0134] Example 13: The method according to Example 11 or Example 12, the method comprising the first UE:

[0135] receiving a UECS synchronization signal for a second UECS from a fifth UE, the fifth UE acting as a coordinating UE for the second UECS;

[0136] transmitting a third UECS-Access-Request to the fifth UE; and

[0137] A third UECS-access-response is received from the fifth UE, the third UECS-access-response indicating that the first UE is included in the second UECS.

[0138] Example 14: The method of Example 11 or Example 12, wherein the first UECS includes an additional UE, the method comprising the first UE:

[0139] transmitting a UECS-handover-request to a fifth UE;

[0140] receiving a UECS-handover-response indicating that the fifth UE has included the first UE and the additional UE into a second UECS; and

[0141] A third coordinator-change message indicating that the fifth UE is the coordinating UE for the second UECS is transmitted to the additional UE as a broadcast message.

[0142] Example 15: The method according to Example 14, comprising the first UE:

[0143] The UECS-handover-request includes the identifier of the additional UE.

[0144] Example 16: The method of Example 14 or Example 15, wherein transmitting the third coordinator-change message to the additional UE comprises:

[0145] The third coordinator-change message indicating that the fifth UE is the coordinating UE for the second UECS is transmitted to the additional UEs as a broadcast message.

[0146] Example 17: The method of Example 16, the method comprising the first UE:

[0147] receiving a third coordinator-change message from the fifth UE, the third coordinator-change message indicating that the first UE is now acting as the coordinating UE for the second UECS; and

[0148] Based on receiving the third coordinator-change message, a UECS synchronization signal for the second UECS is periodically transmitted.

[0149] Example 18: The method of any preceding example, wherein receiving an indication of an allocation of air interface resources for the UECS synchronization signal comprises:

[0150] An indication of an allocation of air interface resources for the UECS synchronization signal is received from a base station.

[0151] Example 19: The method of Example 18, wherein receiving an indication of an allocation of air interface resources for the UECS synchronization signal from the base station comprises:

[0152] An indication of an allocation of air interface resources for the UECS synchronization signal is received from the base station in a broadcast message.

[0153] Example 20: The method of Example 19, wherein receiving an indication of an allocation of air interface resources for the UECS synchronization signal from the base station in a broadcast message comprises:

[0154] An indication of an allocation of air interface resources for the UECS synchronization signal is received from the base station in a system information block (SIB).

[0155] Example 21: A user device comprising:

[0156] Wireless transceiver;

[0157] Local wireless network transceiver;

[0158] Processor; and

[0159] Instructions for a communication manager application, the instructions being executable by the processor to configure the user equipment to perform a method according to any one of Examples 1 to 20.

[0160] Example 22: A computer-readable medium comprising instructions, which, when executed by a processor of a user device, cause the user device to perform the method of any one of Examples 1 to 20.

[0161] Although various aspects of coordinating user device selection have been described in language specific to features and / or methods, the subject matter of the appended claims is not necessarily limited to the specific features or methods described. Rather, specific features and methods are disclosed as example implementations of coordinating user device selection, and other equivalent features and methods are intended to be within the scope of the appended claims. Furthermore, various different aspects are described, and it should be appreciated that each described aspect can be implemented independently or in conjunction with one or more other described aspects.

Claims

1. A method for a first user equipment UE to join a first user equipment coordination set UECS in a wireless communication network, wherein a UECS comprises a plurality of UEs, wherein the plurality of UEs are configured to jointly transmit data to be sent to a base station and / or jointly receive data from the base station for one or more UEs in the UECS, and wherein the UECS further comprises a coordination UE, wherein the coordination UE is configured to coordinate the joint transmission and / or joint reception of downlink data from the base station and / or uplink data to be sent to the base station, wherein the method comprises: receiving an indication of an allocation of air interface resources for a UECS synchronization signal; monitoring the air interface resources to receive a UECS synchronization signal; receiving one or more UECS synchronization signals for the first UECS from a second UE acting as a coordinating UE for the first UECS; transmitting a first UECS access request to the second UE; as well as A first UECS access response is received from the second UE, the first UECS access response indicating that the first UE is included in the first UECS.

2. The method according to claim 1, further comprising: receiving a first coordinator change message from the second UE, the first coordinator change message indicating that the first UE is now acting as the coordinating UE for the first UECS; as well as Based on receiving the first coordinator change message, a UECS synchronization signal for the first UECS is periodically transmitted.

3. The method according to claim 2, wherein: The coordinator change message includes a recurring schedule of UEs acting as the coordinating UE for the first UECS.

4. The method according to claim 3, wherein: The cyclic schedule includes an indication of one or more criteria for scheduling a duration for each UE in the cyclic schedule to act as the coordinating UE, and wherein the criteria include one or more of the following: Duration; the amount of power consumed to perform coordinated UE operations; and The amount of data transferred while acting as the coordinating UE.

5. The method according to claim 3, further comprising: including, based on the cyclic scheduling, in a second coordinator change message, an indication that the third UE acts as a next coordinating UE for the first UECS; transmitting the second coordinator change message as a message to a UE included in the first UECS; as well as The periodic transmission of the UECS synchronization signal for the first UECS is suspended.

6. The method according to claim 5, wherein: Transmitting the second coordinator change message includes: The second coordinator change message is transmitted as a broadcast message to UEs included in the first UECS.

7. The method according to claim 3, further comprising: receiving a second UECS access request from a fourth UE while the first UE acts as the coordinating UE for the first UECS; Determining to include the fourth UE in the first UECS; as well as A second UECS access response is transmitted to the fourth UE, the second UECS access response indicating that the fourth UE is included in the first UECS.

8. The method according to claim 7, further comprising: The fourth UE is included in the cyclic scheduling.

9. The method according to claim 8, wherein: Including the fourth UE in the cyclic scheduling comprises: and evaluating one or more selection criteria for including the fourth UE in the cyclic scheduling, wherein the one or more selection criteria include: The remaining battery power of the fourth UE; a charging status of the fourth UE; Uplink signal power to the base station; downlink received signal strength from the base station; uplink transmit power to the base station; The number of uplinks from the fourth UE to the base station; and The uplink data throughput of the fourth UE.

10. The method according to claim 9, wherein: The one or more selection criteria are included in the second UECS access request.

11. The method according to claim 1, further comprising: monitoring air interface resources to receive a UECS synchronization signal from the second UE after receiving the first UECS access response from the second UE; as well as It is determined that the UECS synchronization signal has not been received from the second UE within a threshold time period.

12. The method according to claim 11, further comprising: determining to act as the coordinating UE for the first UECS; as well as The UECS synchronization signal for the first UECS is periodically transmitted.

13. The method according to claim 11, further comprising: receiving a UECS synchronization signal for a second UECS from a fifth UE, the fifth UE acting as a coordinating UE for the second UECS; transmitting a third UECS access request to the fifth UE; as well as A third UECS access response is received from the fifth UE, the third UECS access response indicating that the first UE is included in the second UECS.

14. The method according to claim 11, wherein: The first UECS includes an additional UE, and the method further includes: transmitting a UECS handover request to a fifth UE, the fifth UE acting as a coordinating UE for the second UECS; receiving a UECS handover response indicating that the fifth UE has included the first UE and the additional UE into the second UECS; and A third coordinator change message is transmitted to the additional UE indicating that the fifth UE is the coordinating UE for the second UECS.

15. The method according to claim 14, further comprising: The UECS handover request includes the identifier of the additional UE.

16. The method according to claim 14, wherein: Transmitting the third coordinator change message to the additional UE includes: The third coordinator change message indicating that the fifth UE is the coordinating UE for the second UECS is transmitted to the additional UEs as a broadcast message.

17. The method according to claim 13, further comprising: receiving a fourth coordinator change message from the fifth UE, the fourth coordinator change message indicating that the first UE is now acting as the coordinating UE for the second UECS; as well as Based on receiving the fourth coordinator change message, a UECS synchronization signal for the second UECS is periodically transmitted.

18. The method according to any one of claims 1 to 17, wherein: Receiving an indication of an allocation of air interface resources for the UECS synchronization signal comprises: An indication of an allocation of air interface resources for the UECS synchronization signal is received from a base station.

19. The method according to claim 18, wherein: Receiving an indication of allocation of air interface resources for the UECS synchronization signal from the base station comprises: An indication of an allocation of air interface resources for the UECS synchronization signal is received from the base station in a broadcast message.

20. A user equipment, comprising: Wireless transceiver; processor; as well as Instructions for a communications manager application, the instructions being executable by the processor to configure the user equipment to perform the method according to any one of claims 1 to 19.

Images