[go: up one dir, main page]

WO2017119919A1 - Transfert de groupe pour des applications critiques - Google Patents

Transfert de groupe pour des applications critiques Download PDF

Info

Publication number
WO2017119919A1
WO2017119919A1 PCT/US2016/024923 US2016024923W WO2017119919A1 WO 2017119919 A1 WO2017119919 A1 WO 2017119919A1 US 2016024923 W US2016024923 W US 2016024923W WO 2017119919 A1 WO2017119919 A1 WO 2017119919A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
handover
ues
prose
enb
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/US2016/024923
Other languages
English (en)
Inventor
Satish C. Jha
Dave Cavalcanti
Ana Lucia Pinheiro
Candy YIU
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corp filed Critical Intel Corp
Priority to TW105140112A priority Critical patent/TWI786038B/zh
Publication of WO2017119919A1 publication Critical patent/WO2017119919A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0027—Control or signalling for completing the hand-off for data sessions of end-to-end connection for a plurality of data sessions of end-to-end connections, e.g. multi-call or multi-bearer end-to-end data connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0072—Transmission or use of information for re-establishing the radio link of resource information of target access point

Definitions

  • the present disclosure relates to wireless communications, and more specifically, to group handover for mission critical applications.
  • One important characteristic of applications such as cooperative driving applications involves data (objects and sensing) and event exchanges between devices in a group within a relatively small area. Usually the group (or Platoon) will move together, eventually crossing into a new network cell at about the same time.
  • An efficient mechanism for managing group handover (HO) is crucial to reduce the air interface network signaling, user plane (UP) HO interruption time, and provide the seamless continuation of group communication demanded by mission critical cooperative driving applications.
  • 3GPP standardizes device-to-device (D2D) operation/functionality to be supported in long term evolution (LTE) release specifications. Exploiting direct communication, such as in D2D communication between nearby mobile devices can improve spectrum utilization, overall throughput, and energy efficiency, while enabling new peer-to-peer and location-based applications and services.
  • D2D-enabled LTE devices for example, have the potential to become competitive for fallback public safety networks that can function when cellular networks are not available or otherwise fail in connection.
  • Introducing D2D poses many new challenges and risks to the long-standing cellular architecture, which is based on or centered on a base station (BS).
  • BS base station
  • One issue to be resolved is how to share or communicate resources or other communication resources in D2D communications among mobile devices (e.g., user equipment) that can communicate in both cellular and D2D communications.
  • FIG. 1 is a block diagram illustrating a wireless network communications environment for a UE or other network device (e.g., eNB) configured to form a D2D group and generate a group handover that can be utilized according to various aspects or embodiments.
  • a UE or other network device e.g., eNB
  • FIG. 2 is another wireless network communications environment for a UE or other network device (e.g., eNB) configured to form a D2D group and generate a group handover that can be utilized according to various aspects or embodiments.
  • a UE or other network device e.g., eNB
  • FIG. 3 is a process flow for wireless network for a UE or other network device (e.g., eNB) configured to form a D2D group and generate a group handover that can be utilized according to various aspects or embodiments.
  • a UE or other network device e.g., eNB
  • FIG. 4 is another process flow for wireless network for a UE or other network device (e.g., eNB) configured to form a D2D group and generate a group handover that can be utilized according to various aspects or embodiments.
  • a UE or other network device e.g., eNB
  • FIG. 5 is another process flow for wireless network for a UE or other network device (e.g., eNB) configured to form a D2D group and generate a group handover that can be utilized according to various aspects or embodiments.
  • a UE or other network device e.g., eNB
  • FIG. 6 is another process flow for wireless network for a UE or other network device (e.g., eNB) configured to form a D2D group and generate a group handover that can be utilized according to various aspects or embodiments.
  • a UE or other network device e.g., eNB
  • FIG. 7 is another wireless network communications environment for a UE or other network device (e.g., eNB) configured to form a D2D group and generate a group handover that can be utilized according to various aspects or embodiments.
  • FIG. 8 is an illustration of an example network device to implement various aspects or embodiments disclosed.
  • FIG. 9 is another illustration of an example network device to implement various aspects or embodiments disclosed.
  • FIG. 10 is an example illustrated implementation of an architecture in which group configuration data can be transmitted to groups of User Equipment (UE) devices from an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), according to one or more aspects or embodiment.
  • UE User Equipment
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • a component can be a processor, a process running on a processor, a controller, a circuit or a circuit element, an object, an executable, a program, a storage device, a computer, a tablet PC and/or a mobile phone with a processing device.
  • an application running on a server and the server can also be a component.
  • One or more components can reside within a process, and a component can be localized on one computer and/or distributed between two or more computers.
  • a set of elements or a set of other components can be described herein, in which the term “set” can be interpreted as "one or more.”
  • these components can execute from various computer readable storage media having various data structures stored thereon such as with a module, for example.
  • the components can communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).
  • a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).
  • a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, in which the electric or electronic circuitry can be operated by a software application or a firmware application executed by one or more processors.
  • the one or more processors can be internal or external to the apparatus and can execute at least a part of the software or firmware application.
  • a component can be an apparatus that provides specific functionality through electronic components or elements without mechanical parts; the electronic components can include one or more processors therein to execute software and/or firmware that confer(s), at least in part, the functionality of the electronic components.
  • Proximity-Based Services can reside in network devices communicatively coupled within a cellular network such as a base station (BS), evolved NodeB (eNB)), a mobile or wireless device (user equipment (UE)), or sub-system of a mobile device, which can include autonomous vehicles or other networked devices.
  • BS base station
  • eNB evolved NodeB
  • UE user equipment
  • sub-system of a mobile device which can include autonomous vehicles or other networked devices.
  • devices with reduced distance between them can form a D2D group that shares a given resource pool(s) for group communication using their
  • D2D/ProSe D2D, ProSe, or both interface.
  • the devices that members of or part of the D2D/ProSe group can be connected at all time in a connected mode via their cellular interface in order to send/receive mission critical data to/from the network (i.e. BS).
  • the network i.e. BS.
  • the eNB maintains or stores device context information, and knows the device location at the cell level.
  • the group formation as well as the allocation of resource pools to a D2D/ProSe group can be assisted by the network through the cellular interface.
  • network assisted group formation methods can be used to help devices form/join and leave a group.
  • Devices in a D2D/ProSe group can share the same resources for D2D/ProSe communications either with the assistance of the network or autonomously.
  • a group leader can be defined to coordinate group operation.
  • a UE device can request the network to activate a group
  • Various embodiments are disclosed for D2D/ProSe group handover (HO) in order to significantly reduce network signaling, enable seamless group continuation during and after HO, and minimize user plane interruption for group communication during HO. Since all devices in the group need to perform cellular interface HO at about the same time, a group wise HO trigger can be defined.
  • the UE devices in a group can be within a small geographical area and have similar speeds, and thus have the same timing advance (TA).
  • TA timing advance
  • a single device such as UE group leader
  • Source and target eNBs can also coordinate before HO to select and assign a resource pool, which can be used by devices in the group for group communications during HO and potentially right after the HO in the new cell.
  • the source eNB can provide D2D/ProSe interface configuration information to target BS during HO so that the D2D/ProSe group can be continued seamlessly after HO. Additional, aspects and details of the disclosure are further described below with reference to figures.
  • FIG. 1 illustrates an example wireless network environment 100.
  • the wireless communications environment 100 can include one or more cellular broadcast servers, macro cell network devices 102, 104 (e.g., base stations, eNBs, access points (APs) or the like) as well as one or more small cell network devices, secondary cells, APs or the like (e.g., small eNBs, micro-eNBs, pico-eNBs, femto-eNBs, home eNBs (HeNBs), or Wi-Fi access points / nodes) 106, 1 08 deployed within the wireless communications environment 100 and servicing one or more UE devices 1 10, 1 12, 1 14, 1 1 6, 1 18 (e.g., a vehicle, a mobile or wireless phone, or other networked device being served by any one of the base stations 102-108).
  • macro cell network devices 102, 104 e.g., base stations, eNBs, access points (APs) or the like
  • small cell network devices secondary cells, APs or the
  • Each wireless communications network serving device can be referred to or comprise one or more network devices (e.g., a set of network devices (NDs)) that operate in conjunction in order to process network traffic for the one or more UE devices 1 1 0, 1 12, 1 14, 1 16, or 1 18.
  • network devices e.g., a set of network devices (NDs)
  • macro cell NDs 102, 104 can comprise a set of network devices that are cellular enabled network devices.
  • the small cell network devices 106, 1 08 can include a set of network devices that operate with a smaller coverage zone than the macro cell network devices 102 and 1 02, for example.
  • each of the one or more base stations 1 06, 108 can have a corresponding service area 120, 122 with a cell coverage zone.
  • each of the one or more broadcast servers 1 02, 104 can have a corresponding service area 124, 126.
  • the wireless communications environment 100 is not limited to this implementation and various other architectures can also be employed.
  • self-organizing network devices can deploy any number of Wi-Fi access points and respective service areas within the wireless communications environment 1 00.
  • the wireless communications environment 100 can include a multitude of wireless communications networks, each having a respective coverage area or cell. The coverage area of some of the wireless communications networks can overlap such that one or more network devices can provide coverage areas or zones to UEs or mobile devices whose coverage areas from different networks of network devices overlap.
  • the network devices within the wireless environment 100 can also operate with one another as a Self-Organizing Network (SON), in which at least some of the network devices can be configured to provide self-configuration and self-optimizing capabilities that provide the ability to automate certain operations, management functions and system management functions.
  • SON incorporates self-configuration, self-optimization, monitoring, and operation management to allow the network devices to be communicatively coupled into the network and operate with little to no human intervention while taking into account application settings for applications operating on and managed by the UEs.
  • network devices (NDs) 106 and 1 08 are described as small cell network devices, they can also be Wi-Fi enabled devices or wireless local area network (WLAN) devices, as well as macro cell network devices, small cell network devices, or some other type of ND operable as a base station or eNB, for example.
  • WLAN wireless local area network
  • macro cell network devices small cell network devices
  • small cell network devices or some other type of ND operable as a base station or eNB, for example.
  • one or more of the macro cell NDs 102 and 1 04 could be small cell network devices or other NDs of a different radio access technology (RAT) that operate with different frequency carriers, for example.
  • RAT radio access technology
  • a UE device can contain some or all of the functionality of a system, subscriber unit, subscriber station, mobile station, mobile, wireless terminal, device, mobile device, remote station, remote terminal, access terminal, user terminal, terminal, wireless communication device, wireless communication apparatus, user agent, user device, or other ND, for example.
  • a mobile device can be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a smart phone, a feature phone, a wireless local loop (WLL) station, a networked vehicle or subsystem thereof, a personal digital assistant (PDA), a laptop, a handheld communication device, a handheld computing device, a netbook, a tablet, a satellite radio, a data card, wireless modem card and/or another processing device for communicating over a wireless system.
  • SIP Session Initiation Protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • the UE devices 1 10, 1 12, 1 14, 1 16, 1 18 can include functionality as more fully described herein and can also be configured as dual connected devices, in which one or more of the UE devices 1 10, 1 12, 1 14, 1 16, 1 18 can be connected to more than one eNB or ND of different RATs (e.g., LTE and WLAN, or other combination).
  • RATs e.g., LTE and WLAN, or other combination.
  • cellular broadcast servers or macro cell NDs 102, 104 and small cell NDs 106, 108 can monitor their surrounding radio conditions (e.g., by employing respective measurement components). For example, each of the macro cell NDs 102, 1 04 and small cell NDs 1 06, 108 can determine network traffic load on its respective network by performing a network diagnostic procedure. As an example, during a network listen procedure, macro cell NDs 1 02, 104, small cell NDs 106, 108 or UE devices 1 10, 1 12, 1 14, 1 16, 1 1 8 can scan their radio environment to determine network performance statistics or network parameters (e.g., frequency, SNR, signal quality, QoS, QoE, load, congestion, signal rate, etc.).
  • network performance statistics or network parameters e.g., frequency, SNR, signal quality, QoS, QoE, load, congestion, signal rate, etc.
  • Various parameters associated with macro cell NDs 102, 104 and small cell NDs 106, 108 can be detected during the network diagnostic procedure or measurements by the UE devices, such as, but not limited to, frequency bands, scrambling codes, common channel pilot power, bandwidth across respective networks, universal mobile telecommunications system terrestrial radio access receive signal strength indicator, as well as frequency carrier priorities and so on.
  • UE devices 1 10, 1 12, 1 14, 1 16, 1 18 can be serviced by networks through one of the macro cell NDs 102, 104, or small cell NDs 106, 108.
  • the respective user equipment device might be moved in and out of the coverage area of the associated serving network.
  • the user might be walking, riding in a car, riding on a train, moving around a densely populated urban area (e.g., a large city), wherein the movement might cause the mobile device to be moved between various wireless communication networks.
  • the UE it is beneficial to route the network traffic (e.g., handover) from a serving ND to a target ND in order to continue the communication (e.g., avoid dropped calls) or facilitating offloading for load distribution or other efficiency purposes.
  • network traffic e.g., handover
  • UE devices 1 10, 1 12, 1 14, 1 16, 1 18 can have a problem being able to maintain adequate and seamless communications during handover operations.
  • group communication can takes place through a
  • the D2D/ProSe interface 130 uses group/cell-specific resources.
  • the BS102 can assign one or more resource pool(s) to a D2D/ProSe group 140 (e.g., UEs 1 1 0 and 1 16), which could be valid only in that particular cell or cell coverage area 124.
  • a D2D/ProSe group 140 e.g., UEs 1 10 and 1 16
  • the new BS 104 can then allocate a resource pool to the group.
  • a resource pool can refer to a set of resources for configuring D2D/ProSe communications between a D2D/ProSe group 140, configuring the D2D/ProSe group 140, cell identifiers, channel or bandwidth specification, operating band or component carrier frequencies, channel specifications, or other network related parameters or criteria.
  • one or more mechanism can be implemented to obtain resources in the new cell or cell coverage zone (e.g., 126) while maintaining the group communications in the D2D/ProSe interface 130 with minimal overhead. This mechanism can be referred to as a D2D/ProSe Interface handover or D2D/ProSe group HO.
  • individual handover can also be enabled in the main cellular interface to maintain connection with the network (BS) as a source BS (e.g., 1 02) or a target BS (e.g., 104), for example.
  • BS network
  • the UE devices In a cellular interface handover, the UE devices always can be in a connected state / mode for cellular link as devices have mission critical applications and they may need to send/receive data over cellular network at any time.
  • the UE devices of the D2D/ProSe group 140 can be connected to a new BS (with better cellular link quality) as a target eNB or base station.
  • a predetermined threshold or signal link quality threshold value e.g., a signal to noise ratio, a received channel power indicator, received signal strength indicator, or other channel quality indicator or state data
  • the UEs 1 16 and 1 1 0 can be handed over together in a group to a new cell (e.g., a target eNB or BS 104) to operate within the new cell coverage area 126 and continue to communicate as a D2D/ProSe group 140 having intact D2D/ProSe communications via a D2D/ProSe interface channel 1 30.
  • a new cell e.g., a target eNB or BS 104
  • all devices of the D2D/ProSe group 140 can be moved to the same BS or eNB 104 at approximately the same time via operations at the respective UEs (e.g., 1 10 and 1 16), a UE group leader (e.g., 1 16) whether or not all devices have degraded cellular links with the current / source BS (e.g., 1 02).
  • UE 1 10 and 1 1 6 the respective devices of the D2D/ProSe group 140
  • a UE group leader e.g., 1 16
  • the D2D/ProSe/ProSe group handover of devices is treated as a combination of several simultaneous individual HOs of devices 1 10, 1 1 6, this could result in significant network signaling overhead and radio resource wastage.
  • the UEs 1 10, 1 1 6 of the D2D/ProSe group 140 can initiate, process or generate a D2D/ProSe Interface handover (D2D/ProSe group HO).
  • D2D/ProSe group HO can operate to continue group communications in the D2D/ProSe interface 130 during and after D2D/ProSe group HO without any interruption. How to transfer the group configuration information seamlessly to the new BS 104 and how to achieve a new resource pool(s) for group communication seamlessly from the new BS 104 can be major issues for the D2D/ProSe group HO.
  • D2D/ProSe group HO can also be accompanied first by cellular interface HO of all devices in the group to the new BS 104 and as a D2D/ProSe group 140.
  • Direct communication between UE devices 1 10, 1 16 can further be supported by D2D communication functionality in LTE proximity services (ProSe).
  • D2D can also refer to communications between UEs or other network devices
  • D2D communication can be supported over dedicated resource pools, which are preconfigured or allocated by the eNB (e.g., BS 102, 104). Access to data resources within a resource pool (e.g., with a Physical Sidelink Shared Channel (PSSCH)) can be controlled or assigned by the eNB 102, 104 or acquired autonomously by the UE device using contention within control resources (Physical Sidelink Control Channel (PSCCH)). From the physical layer (PHY) perspective, UE device data transmissions can be broadcast, in which those UE devices within a geographical range can be potential receivers.
  • PSSCH Physical Sidelink Shared Channel
  • UEs 1 10, 1 1 6, can thus form groups at the application layer by exchanging application messages between UE devices over a ProSe interface circuitry as part of or in conjunction with D2D interface circuitry in D2D/ProSe communications.
  • UE devices that are members of a group can periodically broadcast group messages and other UE devices that want to join the group send a request to join the group.
  • One of the group members can respond with a confirmation allowing the new member to enter the group.
  • members can broadcast a message to inform that they are leaving the group.
  • the UE device 1 10, 1 16 can maintain a neighbor list, for example, in the storage media or data store.
  • a neighbor list or data set can be stored in a database table or other appropriate form.
  • This neighbor list can record an identifier for each UE device from which a beacon was received, record a signal quality that characterizes the quality of the channel between the UE devices, as well as other information that is helpful in selecting suitable UE devices for group participation, such as the neighbor UE device's speed, trajectory, or an identifier for a group to which the neighbor UE device belongs, for example.
  • the example wireless environment 200 illustrates a set of wireless network macro cells 202, 204, and 206.
  • wireless cellular network deployments within the wireless environment 200 can encompass any number and type of cells.
  • Coverage macro cells 202, 204, and 206 are illustrated as hexagons, but coverage cells can adopt other geometries generally dictated by a deployment configuration or floor plan, geographic areas to be covered, or other factors.
  • Each macro cell 202, 204, and 206 can be sectorized in a 2 ⁇ /3 configuration, in which each macro cell includes three sectors as an example demarcated with dashed lines in FIG. 2. It is noted that other sectorizations are possible, and aspects or features of the disclosed subject matter can be exploited regardless of type of sectorization.
  • Macro cells 202, 204, and 206 are served respectively through macro cell network devices, base stations or eNodeBs (eNBs) 104, 1 02, and 212. It is noted that radio communication component(s) are functionally coupled through links such as cables (e.g., RF and microwave coaxial lines), ports, switches, connectors, and the like, to a set of one or more antennas that transmit and receive wireless signals (not illustrated).
  • cables e.g., RF and microwave coaxial lines
  • ports e.g., switches, connectors, and the like
  • a radio network controller (not shown), which can be a part of mobile network platform(s) 214, and set of base stations (e.g., eNBs 104, 102, and 212) that serve a set of macro cells; electronic circuitry or components associated with the base stations in the set of base stations; a set of respective wireless links (e.g., links 21 6, 218, and 220) operated in accordance with a radio technology through the base stations 1 04, 102, and 212, form a macro radio access network. It is further noted that, based on network features, the radio controller can be distributed among the set of base stations 1 04, 102, and 212 or associated radio equipment. In an aspect, for universal mobile telecommunication system-based networks, wireless links 216, 21 8, and 220 can embody a Uu interface (universal mobile telecommunication system air interface, or other type of air interface).
  • Mobile network platform(s) 214 facilitates, for example, circuit switched-based (e.g., voice and data) and packet-switched (e.g., Internet protocol, frame relay, or asynchronous transfer mode) traffic and signaling generation, as well as delivery and reception for networked telecommunication via a user equipment (UE) 1 1 6 (e.g., mobile or wireless device) or a UE 1 1 0, in accordance with various radio technologies for disparate markets.
  • UE user equipment
  • Telecommunication can be based at least in part on standardized protocols for communication determined by a radio technology utilized for
  • telecommunication can exploit various frequency bands, component carriers or carriers, which include any electromagnetic frequency bands licensed by the service provider network 222 (e.g., personal communication services, advanced wireless services, general wireless communications service, and so forth), and any unlicensed frequency bands currently available for telecommunication.
  • mobile network platform(s) 214 can control and manage base stations 1 02, 104, and 21 2 and radio component(s) associated thereof, in disparate macro cells 202, 204, and 206 by way of, for example, a wireless network management component (e.g., radio network controller(s), cellular gateway node(s), etc.).
  • a wireless network management component e.g., radio network controller(s), cellular gateway node(s), etc.
  • wireless network platform(s) can integrate disparate networks (e.g., Wi-Fi network(s), femto cell network(s), broadband network(s), service network(s), enterprise network(s), and so on).
  • networks e.g., Wi-Fi network(s), femto cell network(s), broadband network(s), service network(s), enterprise network(s), and so on.
  • mobile network platform 214 can be embodied in the service provider network 222.
  • wireless backhaul link(s) 224 can include wired link components such as a T1/E1 phone line, a T3/DS3 line, a digital subscriber line either synchronous or asynchronous; an asymmetric digital subscriber line; an optical fiber backbone; a coaxial cable, etc.; and wireless link components such as line-of-sight or non-line-of- sight links which can include terrestrial air-interfaces or deep space links (e.g., satellite communication links for navigation).
  • wired link components such as a T1/E1 phone line, a T3/DS3 line, a digital subscriber line either synchronous or asynchronous; an asymmetric digital subscriber line; an optical fiber backbone; a coaxial cable, etc.
  • wireless link components such as line-of-sight or non-line-of- sight links which can include terrestrial air-interfaces or deep space links (e.g., satellite communication links for navigation).
  • wireless backhaul link(s) 224 embodies an luB interface. It is noted that while an exemplary wireless environment 200 is illustrated for macro cells and macro base stations, aspects, features and advantages of the disclosed subject matter can be implemented in small cells, micro cells, pico cells, femto cells, or the like.
  • the wireless environment 200 illustrates further aspects comprising the UE device 1 1 6 in communication with another UE 1 10 via D2D/ProSe communication on the D2D/ProSe communication channel.
  • the UE 1 16 is configured to switch between a cellular network mode of communication and a D2D/ProSe mode of communication.
  • the UE 1 1 6 communicates directly with the UE 1 1 0 via a wireless communication link 130 without a BS/eNB as a constant facilitating intermediary or consistently active mediator at each communication.
  • the cellular networks associated with the macro cells 202, 204, or 206 are utilized to facilitate a communication with the UE 1 10 (e.g., via the link 236 and the base station 102).
  • the UE 1 16 includes a D2D/ProSe interface component 232 and a cellular network interface component 234, while the eNB 102 comprises a D2D/ProSe interface component 240 and a cellular network interface component 242 also.
  • the cellular network interface component 234 of UE 1 1 6 and 242 of eNB 102 can and process cellular network communications on one or more network channels (e.g., 21 6, 21 8, 220) to enable a cellular handover in a wireless network and a formation of a device-to-device group with other UEs 1 10 via one or more D2D/ProSe channels 130 that communicatively couple UEs of the D2D/ProSe group.
  • network channels e.g., 21 6, 21 8, 220
  • the D2D/ProSe interface component 232 of UE 1 16 and 240 of eNB 102 communicatively coupled to the cellular network interface components and enable D2D/ProSe communications on the one or more D2D/ProSe channels 130 among the D2D/ProSe group, and enable a D2D/ProSe group handover based on a set of predetermined criteria.
  • the UE devices can also communicate with other UE devices in device-to-device mode (also called Peer-to-Peer (P2P) mode) over the D2D/ProSe interface component 232 as ProSe interface circuitry.
  • P2P Peer-to-Peer
  • ProSe interface circuitry can be an enhancement of an existing LTE ProSe PC5 interface, a new ProSe interface defined for 5G systems, a WiFi interface, Bluetooth interface, or an interface for any other version of Wireless Personal Area Networks or Wireless Local Area Networks.
  • the UE 1 1 6 and eNB 102 can use these components to generate and control communications directly from the UE 1 16 to the UE 1 1 0 while in the D2D/ProSe communication mode without the intercession of the base station 102 and handover operations that maintain D2D/ProSe communications between the D2D/ProSe group.
  • An advantage of the D2D/ProSe communication mode by the UE 1 1 6 is that a higher data rate than a cellular network communication mode alone can be experienced due to a shorter range of communications via the link 130 than the links 218 and 236, for example.
  • the UEs 1 16, 1 1 0 form a D2D/ProSe group with one another or with one or more other networked devices or UEs operating within one or more macro cells 202, 204, or 206 that could benefit from D2D/ProSe communications, as the D2D/ProSe communications can help offload traffic from one or more congested cell networks (e.g. macro cells 202, 204, or 206).
  • D2D/ProSe configured UEs e.g. UE 1 16
  • these networks could have more available spectrum for other network devices and further limit potential
  • the D2D/ProSe interface components 132 of the UE 1 16 and 240 of the eNB 102 can comprise a transceiver, a transmitter, a receiver, corresponding communication circuitry or other similar components that enables a communication directly to another UE device (e.g., 1 10) and controlling handover of these communications as a D2D/ProSe group.
  • the D2D/ProSe communication component 132 can operate to switch between a D2D/ProSe communication mode and a cellular network
  • the D2D/ProSe communication component 132 can transmit or receive D2D/ProSe data via the D2D/ProSe communication link 130 and process D2D/ProSe resource pools and commands received via the cellular network interface or channel 218 from eNB 102, which can control, manage and direct D2D/ProSe operates among the D2D/ProSe group by using D2D/ProSe interface component 240 and cellular network interface component 242, for example.
  • the D2D/ProSe communication data can comprise one or more physical parameters or predetermined criteria. These parameters / predetermined criteria can enable or facilitate the UE 1 10 to recognize a subsequent D2D/ProSe communication being received by UEs of the D2D/ProSe group utilizing the parameters provided as control information within the D2D/ProSe data transmission, as well as enable D2D/ProSe group handover.
  • each UE 1 16 and 1 10 could likewise transmit D2D/ProSe data from the UE 1 1 6 to the UE 1 10 as well, in which the UE 1 10 could also decode subsequent transmissions based on physical parameters from the UE 1 16 or relayed from the UE 1 1 6 as a UE group leader of the D2D/ProSe group, which could be from the serving or source eNB 102.
  • These one or more parameters can include, but not limited to, a D2D/ProSe transmitter / group identity, a position of the sub-frames message transmission in a logical resource pool, the scheduling assignment cycle or period, a number of packet data units, a number of retransmissions, time instances for initial packet data units, time instances for retransmissions, or the other D2D/ProSe communication related parameters, for example.
  • Other predetermined criteria for example, could be a level of complexity (e.g.
  • the predetermined criteria can further comprise a worse UE measurement of a channel link quality value, measurements from the plurality of UEs of the D2D/ProSe group, an average measurement value of measurements from the D2D/ProSe group, or one or more measurement reports from a UE group leader of the plurality of UEs of the D2D/ProSe group requesting the D2D/ProSe group handover.
  • a group wise HO trigger can be generated by the UE device 1 16 as a UE group leader, the UE 1 10 as a member of the D2D/ProSe group or the eNB 102.
  • the UE devices 1 10 and 1 16 in the D2D/ProSe group can be within a small geographical area and have similar speeds; therefore they can have the same timing advance (TA).
  • TA timing advance
  • a single UE device 1 16 can perform RA to get the TA and then assist other devices (e.g., UE 1 10) in the group to get UL time synchronization with target eNB.
  • Source and Target BSs can also coordinate before HO to select and assign a resource pool, which can be used by the UE devices in the D2D/ProSe group for group D2D/ProSe communications during HO via the D2D/ProSe link 130 or cellular interfaces 236, 216-220 and potentially right after the HO in the new cell.
  • the source eNB 102 can provides D2D/ProSe interface configuration information to the target eNB 104 or 212 during HO so that the D2D/ProSe group can be continued seamlessly after HO in formation as a group and be communicatively coupled in real time via D2D/ProSe communication channels.
  • UE devices 1 10 and 1 16 as a D2D/ProSe group can be capable of communicating with the network through source eNB 102 using the cellular interface (C- interface) 218, 236, for example.
  • This C-interface can be a new 5G or beyond interface, or it can be an enhancement of existing LTE Uu-interface.
  • UE devices 1 10 and 1 16 can also communicate with other devices and one another in a D2D/ProSe mode over a new P-interface (e.g., interface 130).
  • the P-interface can be an enhancement of the existing LTE D2D/ProSe PC5 interface or it can be a new D2D/ProSe interface defined for 5G systems or beyond. Communications between UE devices 1 1 0 and 1 16 can thus operate within a D2D/ProSe group over the P-interface.
  • FIG. 3 illustrates a process flow 300 for a D2D/ProSe group handover via the components of the eNBs and UEs of a D2D/ProSe group in
  • a group of vehicles, network devices, or other similar UEs operating in a platoon mode with D2D/ProSe communications on a highway can reach coverage boundary of current BS (source BS) and be about to enter coverage of another BS (target BS).
  • source BS current BS
  • target BS target BS
  • a D2D/ProSe group HO can be implemented according to the process flow 300 mechanisms of FIG. 3 in order to maintain the D2D/ProSe group communications via the D2D/ProSe interface component 232 of each UE 1 10, 1 1 6 of the D2D/ProSe group.
  • the one or more UEs (e.g., UE 1 10) of the D2D/ProSe group 140 that are not a UE group leader 1 16, or the UE group leader 1 16 can process or generate measurements of cellular quality on corresponding cell network channels.
  • Each respective network device or UE of the D2D/ProSe group 140 can be configured to generate measurements of the network channels as well as for the one or more
  • the UEs of the D2D/ProSe group 140 can further provide the measurements to the UE group leader 1 16 or another UE of the D2D/ProSe group 140 via the one or more D2D/ProSe channels 130 in order to aggregate the group link measurements and quality monitoring among the D2D/ProSe group 140 at 302.
  • the aggregate link quality measurement reporting can be generated to the eNB 102 via the one or more network channels 236 via the group leader UE 1 16 or from UEs individually at 306.
  • a UE device 1 10 or 1 16 in the D2D/ProSe group 140 can requests the source eNB 102 to initiate D2D/ProSe group HO, in which all UEs are attempted to be handed over to a target eNB 104 together, at about the same time, concurrently or simultaneously.
  • UE devices 1 10, 1 16, for example can frequently monitor / measure channel qualities of current cell 204 / eNB 102 in addition to neighbor cells 206, 202 of eNBs 1 04, 212 to decide an individual HO trigger or a group HO trigger 303.
  • the eNB 102 can set different thresholds for a group HO trigger 303 when UE devices are in D2D/ProSe group communication.
  • the D2D/ProSe group HO trigger 303 can occur earlier via the UE group leader 1 1 6 or other UE than the individual HO trigger (i.e. when the device is not operating in group communication mode) so that the D2D/ProSe group 140 gets more time to complete the D2D/ProSe group handover before any cellular link 218, 236 in the group fails.
  • the UE group leader 1 16 can initiate D2D/ProSe group HO based on the aggregate group trigger or D2D/ProSe group HO trigger 303 on behalf of the group via a group HO request 304.
  • other UE devices in the group 140 can also trigger the D2D/ProSe group HO by using a D2D/ProSe group HO trigger 303 as a BS configurable aggregate group HO trigger as well.
  • the group HO trigger 303 can enable or control all devices in the group to handover to the target eNB 104 at about the same time.
  • Group triggers for the D2D/ProSe group HO can be configurable as aggregate group HO triggers that facilitate or initiate the D2D/ProSe HO.
  • the UE device 1 1 0 or 1 16 can explicitly indicate in the HO request 303 whether it is individual HO request for or a group HO request 304 for the D2D/ProSe group to be handed over together.
  • the group HO trigger 303 can occur or include various different triggers. For example, in an event when link quality of any one UE device in the D2D/ProSe group 140 falls below a threshold value T ne arLinkFaiiureHOTrigger for a period of time T H o, the D2D/ProSe group trigger could be communicated to the eNB 102. Each UE device could evaluate this trigger as a quality link threshold value, and once such an event trigger occurs, the individual UE device 1 10, 1 16 or other D2D/ProSe group member device can send the group HO request 303 to the eNB 102 directly or through the group leader 1 1 6.
  • the group HO trigger 303 can comprise an event when more than 50% or other percentage number of devices in the group have a channel link quality that falls below T G r 0 upHOTrigger value for a time T H o-
  • Each D2D/ProSe group device can monitor for event of fulfilment of individual criteria (its link quality falling below TGroupHOTrigger value for a time THO) and send the occurrence of such an event to group leader 1 1 6 via a D2D/ProSe interface message exchange on one or more D2D/ProSe channels between different D2D/ProSe group UEs.
  • the group leader 1 16 can further evaluate the group HO trigger 303 for the entire group and once such an event occurs, request D2D/ProSe group HO to the source eNB 102 at 303.
  • D2D/ProSe group trigger 303 can include an event when the link quality with a neighbor cell (e.g., 202 or 206) for more than 50% or another percentage number of UE group member devices becomes ToroupHOTriggeroffset better than the current cell link 236 or 218.
  • a neighbor cell e.g., 202 or 206
  • ToroupHOTriggeroffset better than the current cell link 236 or 218.
  • Each UE device 1 10 or 1 16 can monitor for event of fulfilment of individual criteria (its link quality being better than neighbor link by GroupHOTriggeroffset value for a time T H o) and send the occurrence of such an event to the group leader 1 16 via D2D/ProSe Interface message exchange on one or more
  • the UE group leader 1 16 can then evaluate the group HO trigger 303 for the entire group and once such an event occurs, it can requests the eNB 102 for group HO.
  • the source eNB 102 1 02 can then select the target eNB 104 1 04 at 308.
  • the source eNB 102s can ask UE device(s) 1 10, 1 16 in the D2D/ProSe group 140 to send measurement report(s) and based on the input from other UE devices, and the source eNB 102 can select a target eNB 104 based on such reports.
  • the source eNB 102 can ask a D2D/ProSe group leader 1 16 to send measurement report(s) on behalf of the D2D/ProSe group 140.
  • the D2D/ProSe group leader 1 16 then, sends aggregated group measurement report at 306, which can include several
  • D2D/ProSe group 140 measurement values from each UE device 1 10, 1 16 or other device from in the D2D/ProSe group 140, one or more average measurement values across the D2D/ProSe group 140 and the measurement report from the device requesting HO.
  • the D2D/ProSe group leader 1 16 can collect the measurement reports from the UE devices that are a part of, or as current members of the D2D/ProSe group via a group identifier or communicative coupled via D2D/ProSe links 130, or example, by using D2D/ProSe interface message exchange.
  • the D2D/ProSe group leader 1 16 can aggregate measurement reports from other devices and send the results to the eNB 102.
  • the source eNB 102 can select the best eNB as target eNB 104 based on aggregate measurement report(s) from the D2D/ProSe group 140.
  • the target eNB 104 could be selected such that none of the devices in the D2D/ProSe group 140 has link quality worse than a threshold values, such as a T ne arLFHOTrigger or more than X% (e.g., 50%) of devices has link quality better than ToroupHOTrigger- Other quality link threshold values can also be determined or envisioned, including the examples discussed herein as comprising the group HO trigger 303, for example.
  • the source eNB 102 can ask any of the D2D/ProSe group devices (which need immediate HO) to start individual HO process via a cellular link handover without D2D/ProSe group handover.
  • a UE device e.g., 1 10
  • this UE device can request the eNB (e.g., 102 or 104) to join another or second D2D/ProSe group as part of the handover process, individually as a cellular link HO or within the D2D/ProSe group as part of the D2D/ProSe group for removal to another group.
  • the eNB e.g., 102 or 104
  • the eNB 102 can configure the UE group leader 1 16 as a relay/gateway for a period of time or indefinitely for the other UE device(s) 1 10 of the D2D/ProSe group 140 that need immediate HO. These UE devices with bad links with eNB 1 02 can then start receiving/transmitting messages via D2D/ProSe group leader 1 16.
  • the eNB 102 can keep looking for suitable target eNB 104, and once it finds the suitable target eNB 104 for the D2D/ProSe group 140, it can move the D2D/ProSe group 140 to a new eNB 104.
  • the source eNB 102 can coordinates with the target eNB 104 for D2D/ProSe group HO over an eNB-to-eNB interface (such as a X2 interface in LTE).
  • the source eNB 102 can share D2D/ProSe interface configuration details and devices contexts with the target eNB 104 (e.g., group identifications, user plane and control plane attributes or configurations, addresses, operating
  • the target eNB 104 can further decide about the target eNB 104 .
  • D2D/ProSe group 140 communication resource pool(s) and send a new resource pool info for D2D/ProSe interface communication for the D2D/ProSe group 140 to the source eNB 102 in order to coordinate the D2D/ProSe group HO. If the eNBs 102, 104 decide upon a new resource pool to be used for the D2D/ProSe group communication during D2D/ProSe group HO (and potentially for right after D2D/ProSe group HO), the source eNB 102 can send a new group resource info to the D2D/ProSe group 140 along with an HO command.
  • the target eNB 104 can allow the D2D/ProSe group 140 to continue using a current resource pool (e.g., an operating band for D2D/ProSe communications) for a D2D/ProSe interface
  • a current resource pool e.g., an operating band for D2D/ProSe communications
  • the source eNB 102 can further generate a D2D/ProSe group HO command or a communication command.
  • the eNB 102 can explicitly indicate in the HO command whether it is individual HO command or group HO Command for handing over a group of UEs specifically with cellular handover and D2D/ProSe group HO,.
  • the source eNB 102 can send the D2D/ProSe group 140 HO command to only one device (such as D2D/ProSe group leader 1 16 or a UE device 1 10 which requested for HO).
  • the UE device receiving the group HO from the source eNB 102 can inform all other devices in the D2D/ProSe group 140 about the D2D/ProSe group 140 HO using the D2D/ProSe interface communication, for example.
  • the source eNB 102 can send the HO command to all UE devices 1 10, 1 16 in the D2D/ProSe group 140 via cellular interface
  • the source eNB 102 can use a broadcast / multicast message operations to send the D2D/ProSe group HO message, which can have the HO command or communication command to all devices.
  • a system information block (SIB) can be defined for this purpose, where the SIB message carries the HO command and corresponding group D2D/ProSe group ID (e.g., with individual IDs as well as a group ID).
  • SIB system information block
  • the source eNB 102 can also use a multimedia broadcast multicast service (MBMS) functionality to send a group HO communication message or command to one or more the UEs of the D2D/ProSe group of devices.
  • MBMS multimedia broadcast multicast service
  • the group communication resource pool can comprise configurations after getting group HO command at 310 for the D2D/ProSe group HO to seamlessly enable D2D/ProSe group communications on D2D/ProSe communication channels among the D2D/ProSe group 140 with one or more eNBs operating with each UE as well. If a HO communication command comprises new group communication resource
  • UE devices 1 10, 1 16 or others can start using the new resource pool for D2D/ProSe group communication immediately or after completion of the D2D/ProSe group HO according to whether the new resource is in a dedicated band (say unlicensed band for V2X) or licensed band (e.g., UL cellular band) respectively.
  • the switching to new resource can also depend on whether D2D/ProSe communication is time aligned with cellular communication or not. If D2D/ProSe communication is time aligned with cellular communication or the eNB communication operations, the UE devices 1 10, 1 16 can switch to the new resource pool after HO completion or after achieving time synchronization (time sync) with target eNB 104.
  • the switching to a new resource pool can also be coordinated by D2D/ProSe group leader 1 16 in some cases, such as when one or more UEs of the D2D/ProSe group are using the D2D/ProSe group leader as a gateway or relay, for example.
  • a current resource pool can be validly utilized for group communication at least until D2D/ProSe group HO is completed and the group can be moved to target eNB 104.
  • the target eNB 104 can also change the D2D/ProSe group 140 resource (e.g., a bandwidth, operating frequency range, or other resource of the resource pool) after group HO completion.
  • synchronization can be achieved with the target eNB 104 after receiving the group HO command at 31 0.
  • the UE devices of the D2D/ProSe group 140 can then sync in DL to the target eNB 104 and read the system information (SI) from the target eNB 104 at 314 based on the HO command or resources of a resource pool.
  • SI system information
  • the UE devices of the D2D/ProSe group 140 can further perform security updates for the target eNB 104.
  • only one UE device (which can be indicated or identified in the HO command, such as group leader 1 1 6 or the UE device 1 1 6 who initiated HO) can perform random access to get UL timing advance (TA) in order to be uplink sync with the target eNB 1 04.
  • This first UE device e.g., the UE group leader 1 16
  • This first UE device at 314 can then assists all other devices in the D2D/ProSe group 140 to acquire UL sync with the target eNB 104 by communicating the TA value over D2D/ProSe interface.
  • the UE devices of the D2D/ProSe group 140 can then use DL time synchronization and the TA value to get UL synchronized with the target eNB 1 04.
  • One or more UE devices of the D2D/ProSe group 140 can then send a confirmation message to the first device (such as D2D/ProSe group leader 1 16) stating completion of UL time sync via group communication at 316.
  • the first UE device for example, can then send an air-interface message (such as radio resource control
  • the UE devices of the D2D/ProSe group 140 from now on can perform user plane UL data transmission through the target eNB 104 whenever needed.
  • the core network (e.g., the evolved packet core (EPC) together with or including the eNB 102 or 104) can then direct user plane DL data for the D2D/ProSe group 140 to the target eNB 104 from this point forward.
  • the target eNB 104 104 can then inform the source eNB 102 102 about completion of group HO at 318.
  • the source eNB 102 can keep or maintain user plane data connection with the UE devices of the D2D/ProSe group 140 until a completion of the D2D/ProSe group HO, especially if the sub-ms latency is being utilized for the user plane.
  • UE network devices could utilize two different RF-chains to enable this operation.
  • the source eNB 102 can complete any remaining user plane data transmission and then releases the user plane data connection with the devices. For example, the source eNB 102 can complete any UL plane data transmissions in a buffer or queue and release the UL connection with the UEs in the D2D/ProSe group 140.
  • the source eNB 102 could run a timer or clocking component (not shown) over a certain period or duration of time to detect the D2D/ProSe group HO failure.
  • the timer or countdown can be is started once the group HO command is sent at 308 or 31 0.
  • the timer can be stopped by the source eNB 102 after receiving group HO completion at 316 by a completion message from the target eNB 104 or a UE device of the D2D/ProSe group 140. Expiry of this timer can indicate a failure of group HO.
  • the target eNB 104 or the UE device 1 10 can inform the source eNB 102 about failure of the D2D/ProSe group HO.
  • the source eNB 102 can ask one or more UE devices (who need immediate HO) to initiate individual HO operation by sending separate regular HO commands to them specifically, in which these commands directly from the source eNB could then trigger the individual HO via the cellular link.
  • These UE devices in this case can then move to target eNB 104 separately or independently of the D2D/ProSe group HO.
  • the source eNB 1 02 can request these devices (with successful HO completion) to leave the D2D/ProSe group 140 in order to better preserve the D2D/ProSe communications on a quality channel link corresponding to the cellular link 236, 218, for example, or D2D/ProSe link 130.
  • the source eNB can attempt to form a new D2D/ProSe group (in target eNB 104) for the UE devices before moving these devices to the target eNB 104.
  • the source eNB 102 can negotiate with the target eNB 104 to allow or enable these UE devices (who need immediate HO) to be connected to the new Group during HO or before HO. This could ensure a lower latency on D2D/ProSe interface communications during HO.
  • One use case for this situation is where one or more UE devices (e.g., vehicles from the D2D/ProSe group 140 take right or left turn (or take an exit from highway) at a cell boundary, while other vehicles are continuing straight on the road/highway.
  • FIG. 4 illustrated another example process flow 400 for a group handover operation within a wireless communication network environment in
  • the method 400 initiates at 402 with one or more UEs (e.g., UEs 1 10-1 18) initiating a group
  • D2D/ProSe group e.g., group 140.
  • serving/source eNB 102 can assign a resource pool for D2D/ProSe interface group communication between members of the group, which can be based on a resource pool including IDs of the individual members and configurations for being assisted by the source eNB 102 or other eNB.
  • a group leader e.g., UE 1 16
  • UE 1 16 can be selected or designated by the eNB 102, which can then coordinate D2D/ProSe group
  • the group leader 1 1 6 can assists/coordinate monitoring of aggregate link qualities in the group 140 with source eNB 102 or neighboring eNBs 104, 21 2.
  • UEs of the group 140 can send measurement reports to the group leader 1 16 using
  • D2D/ProSe interface communication channel / link 130 as well as the resource pool provided for the eNB 102, for example.
  • a group HO trigger can be detected by a UE 1 10 or 1 1 6, and the UE device 1 1 0 or 1 16 can requests source eNB 102 for a D2D/ProSe group HO.
  • the source eNB 102 can receive a group aggregate measurement report(s) via UE group leader 1 16 and select the target eNB 1 04 based on the report(s).
  • the source eNB 102 can coordinate with the target eNB 1 04 by sending contexts of UE devices (e.g., one or more ids, configuration data, or the like) and a D2D/ProSe interface configuration, such as group data, members of the group, or the like.
  • a D2D/ProSe group HO can occur or be formed at the target by the target eNB 104 sending a D2D/ProSe interface reconfiguration information such as a new resource pool for D2D/ProSe interface group communications, which can be valid at least until successful completion of the D2D/ProSe group HO and possibly thereafter.
  • a cellular interface HO occurs with the target eNB 1 04 sending cellular interface radio resource configuration (RRC) to one or more of the D2D/ProSe group.
  • RRC radio resource configuration
  • the source eNB 102 can further send an HO command to the
  • D2D/ProSe group and cellular interface radio reconfiguration information can be sent from the target eNB 104.
  • the UEs of D2D/ProSe group 140 can start D2D/ProSe
  • the UEs can then synchronize (sync) in DL with the target eNB 104 and can receive system information, as a result.
  • the group leader 1 16 can perform random access, obtain a timing advance (TA) value and synchronize in the UL with the target eNB 104.
  • the UE group leader 1 1 6 can further communicate the TA value to D2D/ProSe group UEs to enable each of them to individually synchronize with the target eNB 104 without further performing random access themselves.
  • the group leader 1 1 6 can send reconfiguration complete message to target eNB 104.
  • the target eNB in turn, can then indicate to the core network or eNB 102 about completion of the D2D/ProSe group HO.
  • FIG. 5 illustrates a process flow for the case where the completion of all UEs of the D2D/ProSe group is not a complete success, but a partial success where only some of the UEs of the D2D/ProSe group handover.
  • FIG. 5 can further operation as an extension of FIG. 4, for example, or independently.
  • the group leader, the source eNB 102 or the target eNB 104 can inform at least one of the other devices of the partial failure, such as by informing the group leader, a UE device member of the D2D/ProSe group, the source eNB or the target eNB or any combination thereof.
  • a termination of the D2D/ProSe group HO can occur and all UEs of the D2D/ProSe group could return to the source eNB.
  • successful UE devices that have been handed over to the target eNB 104 successfully can remain with the target eNB and unsuccessful UE devices could leave D2D/ProSe group, either by request or be made to.
  • the unsuccessful UEs could then remain or return to the source eNB 102 or other more suitable eNB, at which point they can form a new second D2D/ProSe group with different members or use common resources available to both source and target eNBs to maintain the D2D/ProSe group with different serving eNBs 102 and 104, for example.
  • a partial group failure message can be communicated by one or more UEs of the D2D/ProSe group such as the group leader 1 1 6, the failing UE 1 1 0, for example, the target eNB 1 04 or by the source eNB 102. This can occur where some of the devices successfully complete HO after receiving the group HO command, while others fail to complete HO (e.g., say due to channel degradation with target eNB 104 after group HO initiation). If one of the UE devices indicates to the group lead 1 1 6 that it is HO failure (HOF), in one embodiment all the devices including the group leader 1 16 could terminate the HO and goes back to or remain connected to the source eNB 102.
  • HAF HO failure
  • one of the UE devices can indicate to the group lead 1 1 6 that it is HOF, partial group HO is performed where those devices HO successfully are the only remaining member(s) in the group 140.
  • the devices that HOF can then be forced to leave the group 140 or requested to do so.
  • D2D/ProSe signaling can then be used for those devices to leave the group 140.
  • the target BS 104 can inform the source BS 102 about partial group HO, as the target BS 104 finds out about the case when all devices do not move to it successfully.
  • the options or embodiment above can apply where the eNB 1 04 informs one or more network devices, and either the group HO is terminate or UEs failing to complete the HO can return to the source eNB 102.
  • the group leader 1 16 can inform the target eNB 104 as well as the source eNB 1 02 about the partial HO case. Particularly if all devices do not perform RA with the target eNB for UL time synchronization (as discussed earlier), the group leader 1 1 6 could assess and inform eNBs 102, 104 about the partial Group HO case.
  • the successful UE devices and failed UE devices can continue the group communication over D2D/ProSe link as a D2D/ProSe group. Otherwise, UE devices that successfully moved to target BS can remain as a group or the target eNB 104 can ask them to join a nearby or different D2D/ProSe group. The failed UE devices can form a new group under the source eNB 102 or the source eNB 102 can ask them to join an existing nearby group under the source eNB.
  • FIG. 6 illustrates another process flow in accordance with various aspects
  • the method 600 initiates at 602 with one or more of a UE or eNB processing cellular network communication(s) on a cell network channel or link to enable a formation of a D2D/ProSe group such as with a resource pool or one or more configuration parameters that enable a D2D/ProSe communication via D2D/ProSe channels.
  • the method 600 continues with controlling D2D/ProSe communications on the D2D/ProSe channels and controlling a D2D/ProSe group HO based on communications on the cell network channels, the D2D/ProSe
  • the predetermined criteria can comprise one or more of the following: an aggregated measurement report or data therein, a worse UE measurement of a channel link quality value from the D2D/ProSe group, measurements from the plurality of UEs of the D2D/ProSe group, an average measurement value of measurements from the D2D/ProSe group, one or more measurement reports from a UE group leader of the plurality of UEs of the D2D/ProSe group requesting the D2D/ProSe group handover, a link quality threshold corresponding to one or more network channels related to the plurality of UEs in the D2D/ProSe group, a group threshold related to the link quality threshold, a neighboring cell quality threshold in a comparison with the group threshold or the link quality threshold, or one or more requests for the D2D/ProSe group handover or the cellular handover for a UE of the D2D/ProSe group.
  • FIG. 7 illustrated is another wireless network communications environment for a UE or other network device (e.g., eNB) configured to form a
  • the UEs 1 10, 1 18 and 1 1 6 can comprise additional components including the D2D/ProSe interface component 232, the cellular network interface component 234, as described above, in addition to a channel quality measurement component 710 and a D2D/ProSe HO component 720.
  • the eNB 102 or any other eNB as discussed can comprise the D2D/ProSe interface component 240, the cellular network interface component 242, a channel quality measurement component 730, a D2D/ProSe HO component 740, and a HO command component 750.
  • the channel quality measurement components 710, 730 can generate, process, receive or transmit measurements of the cell network channels / links and D2D/ProSe channels links, and provide the measurements to a group leader UE (e.g., 1 1 6) via the one or more D2D/ProSe channels, or to an eNB 102 via the one or more network channels as the group leader UE via the cellular network interface components 234, 242.
  • the D2D/ProSe handover components 720, 740 can designate a UE group leader on behalf of the plurality of UEs of the D2D/ProSe group 140 to aggregate measurements from the plurality of UEs of the D2D/ProSe group 140 and communicate one or more resource pools to other UEs of the D2D/ProSe group to enable the
  • the D2D/ProSe handover components 720, 740 can complete any uplink (UL) plane data transmission in a buffer, release a UL connection with the plurality of UEs in the D2D/ProSe group after the D2D/ProSe group handover.
  • UL uplink
  • the D2D/ProSe handover components 720, 740 can further determine whether the D2D/ProSe group 140 continues to utilize a current D2D/ProSe channel of the one or more D2D/ProSe channels or a new D2D/ProSe channel based on measurements of the one or more D2D/ProSe channels from the D2D/ProSe group or information from the target eNB related to the current D2D/ProSe channel within a coverage area of the target eNB.
  • the handover command component 750 can generate a group handover command and enable communication of the group handover command to a UE group leader 1 1 6 of the D2D/ProSe group 140 or the plurality of UEs of the D2D/ProSe group, wherein the group handover command comprises at least one of: an indication of the D2D/ProSe group handover to a target eNB, a radio resource configuration (RRC) information related to the cellular network communications, or other RRC information related to the D2D/ProSe communications, wherein the other RRC information comprises a radio resource pool allocated to the D2D/ProSe group to enable the D2D/ProSe communications via an unlicensed band or a licensed band.
  • the handover command component 750 can also communicate the radio resource pool to the UE group leader or the plurality of UEs of the D2D/ProSe group that enables the
  • D2D/ProSe communications after receiving the D2D/ProSe group handover from a source eNB and time synchronizing with the plurality of UEs of the D2D/ProSe group.
  • UE devices 1 1 0, 1 16, 1 18, or other UEs belong to the same group 140, they can also connect to the network via different cells or eNBs 1 02, 212 and their respective coverage areas.
  • handover can be performed individually to each UE device 1 10, 1 16, 1 1 8 in the group, or a group handover can occur with some devices (e.g., 1 10 and 1 16) along with cellular handover, while only an individual cellular handover occurs with other UE devices 1 18.
  • the UE devices 1 10, 1 16m, 1 1 8 can continue using the same channels for D2D/ProSe communication between them or else a new channel for group communication is provided by the network to all devices in the group 140.
  • a UE device 1 18 can report a measurement indicating that a handover is needed, such as from the source eNB 102 to a target eNB 220, for example.
  • the source eNB 102 can decides to handover the individual UE device 1 1 .
  • the source eNB 102 can also decide if the group 140 can continue using the current D2D/ProSe group channel 130 or if a new one should be formed. This decision can be based on: a. Measurements on D2D/ProSe channel 130 provided by the UE device 1 18 performing or initiating the handover. If channel quality is bad, a new D2D/ProSe channel can be generated for the group 140; or b.
  • a request can be sent to the target eNB 212 to check if the channel currently used can be used in the new cell without creating too much interference or interference beyond a certain threshold, such as a signal to noise threshold, an RSSI threshold, or the like. If the same D2D/ProSe channel can be used, the UE device 1 18 can resume D2D/ProSe communication after individual handover. If a new channel is needed, the target eNB 21 2 can send a response message to the source eNB 102 with the new D2D/ProSe group channel information. The source eNB 102 then can reconfigure all the UE devices of the group 140 that are connected to that base station.
  • a certain threshold such as a signal to noise threshold, an RSSI threshold, or the like.
  • the source eNB 102 can provide a list of current channel status in the source cell (e.g., cell area / zone 204 of FIG. 2), such as which bands are being used, which channels are free, or other related criteria. This could be used as a recommendation to the target eNB 212, for example, to allocate proper D2D/ProSe channels.
  • FIG. 8 illustrates a block diagram of an embodiment of access (user) equipment 126, 130 related to access of a network (e.g., base station, wireless access point, femtocell access point, and so forth) that can enable and/or exploit features or aspects disclosed herein.
  • a network e.g., base station, wireless access point, femtocell access point, and so forth
  • Access equipment, UE and/or software 1 10, 1 16, 102, 104 or other network device related to access of a network that can receive and transmit signal(s) from and to wireless devices, wireless ports, wireless routers, etc. through segments 802 802 a (where 'a' is a positive integer).
  • Segments 802 802 a can be internal and/or external to access equipment and/or software 1 1 0, 1 16, 102, 104 related to access of a network, and can be controlled by a monitor component 804 and an antenna component 806.
  • Monitor component 804 and antenna component 806 can couple to communication platform 808, which can include electronic components and associated circuitry that provide for processing and manipulation of received signal(s) and other signal(s) to be transmitted.
  • communication platform 808 includes a receiver/transmitter 810 that can convert analog signals to digital signals upon reception of the analog signals, and can convert digital signals to analog signals upon transmission.
  • receiver/transmitter 810 can divide a single data stream into multiple, parallel data streams, or perform the reciprocal operation.
  • Coupled to receiver/transmitter 810 can be a multiplexer/demultiplexer 812 that can facilitate manipulation of signals in time and frequency space.
  • Multiplexer/demultiplexer 812 can multiplex information (data/traffic and control/signaling) according to various multiplexing schemes such as time division multiplexing, frequency division multiplexing, orthogonal frequency division multiplexing, code division multiplexing, space division multiplexing.
  • multiplexing schemes such as time division multiplexing, frequency division multiplexing, orthogonal frequency division multiplexing, code division multiplexing, space division multiplexing.
  • multiplexer/demultiplexer component 812 can scramble and spread information (e.g., codes, according to substantially any code known in the art, such as Hadamard-Walsh codes, Baker codes, Kasami codes, polyphase codes, and so forth).
  • codes e.g., codes, according to substantially any code known in the art, such as Hadamard-Walsh codes, Baker codes, Kasami codes, polyphase codes, and so forth.
  • a modulator/demodulator 814 is also a part of communication platform 808, and can modulate information according to multiple modulation techniques, such as frequency modulation, amplitude modulation (e.g., M-ary quadrature amplitude modulation, with M a positive integer); phase-shift keying; and so forth).
  • modulation techniques such as frequency modulation, amplitude modulation (e.g., M-ary quadrature amplitude modulation, with M a positive integer); phase-shift keying; and so forth).
  • Access equipment and/or software 1 10, 1 16, 102, 104 related to access of a network also includes a processor 816 configured to confer, at least in part, functionality to substantially any electronic component in access equipment and/or software 1 10, 1 1 6, 102, 1 04 .
  • processor 816 can facilitate configuration of access equipment and/or software 1 10, 1 1 6, 102, 1 04 through, for example, monitor component 804, antenna component 806, and one or more components therein.
  • access equipment and/or software 1 10, 1 16, 102, 104 can include display interface 818, which can display functions that control functionality of access equipment and/or software 1 1 0, 1 16, 1 02, 104, or reveal operation conditions thereof.
  • display interface 818 can include a screen to convey information to an end user.
  • display interface 818 can be a liquid crystal display, a plasma panel, a monolithic thin-film based electrochromic display, and so on.
  • display interface 818 can include a component (e.g., speaker) that facilitates communication of aural indicia, which can also be employed in connection with messages that convey operational instructions to an end user.
  • Display interface 818 can also facilitate data entry (e.g., through a linked keypad or through touch gestures), which can cause access equipment and/or software 1 1 0, 1 16, 102, 104 to receive external commands (e.g., restart operation).
  • Broadband network interface 820 facilitates connection of access equipment and/or software 1 1 0, 1 16, 1 02, 104 to a service provider network (not shown) that can include one or more cellular technologies (e.g., third generation partnership project universal mobile telecommunication system, global system for mobile communication, and so on) through backhaul link(s) (not shown), which enable incoming and outgoing data flow.
  • Broadband network interface 820 can be internal or external to access equipment and/or software 1 10, 1 1 6, 102, 1 04, and can utilize display interface 81 8 for end-user interaction and status information delivery.
  • Processor 816 can be functionally connected to communication platform 808 and can facilitate operations on data (e.g., symbols, bits, or chips) for
  • processor 816 can be functionally connected, through data, system, or an address bus 822, to display interface 81 8 and broadband network interface 820, to confer, at least in part, functionality to each of such components.
  • memory 824 can retain location and/or coverage area (e.g., macro sector, identifier(s)) access list(s) that authorize access to wireless coverage through access equipment and/or software 1 10, 1 16, 102, 1 04, sector intelligence that can include ranking of coverage areas in the wireless environment of access equipment and/or software 1 1 0, 1 16, 102, 104, radio link quality and strength associated therewith, or the like.
  • Location and/or coverage area e.g., macro sector, identifier(s)
  • sector intelligence that can include ranking of coverage areas in the wireless environment of access equipment and/or software 1 1 0, 1 16, 102, 104, radio link quality and strength associated therewith, or the like.
  • Memory 824 also can store data structures, code instructions and program modules, system or device information, code sequences for scrambling, spreading and pilot transmission, access point configuration, and so on.
  • Processor 816 can be coupled (e.g., through a memory bus), to memory 824 in order to store and retrieve information used to operate and/or confer functionality to the components, platform, and interface that reside within access equipment and/or software 1 10, 1 1 6, 102, 1 04.
  • the memory 824 can comprise one or more machine-readable medium including instructions that, when performed by a machine or component herein cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described herein.
  • circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware.
  • FIG. 9 illustrates, for one embodiment, example components of an electronic device 900.
  • the electronic device 900 may be, implement, be incorporated into, or otherwise be a part of a user equipment (UE), an evolved NodeB (eNB), or some other electronic device.
  • the electronic device 900 may include application circuitry 902, baseband circuitry 904, Radio Frequency (RF) circuitry 906, front-end module (FEM) circuitry 908 and one or more antennas 910, coupled together at least as shown.
  • RF Radio Frequency
  • FEM front-end module
  • FEM circuitry 908 can also include a transmit and receive path for device-to- device communications received directly from another UE device, without traveling through the E-UTRAN (e.g. ProSe interface circuitry).
  • FEM circuitry 808 can also include a transmit and receive path for cellular communications received from the E-UTRAN or E-UTRAN (e.g. cellular interface circuitry).
  • the above described circuitries can be included in a plurality of devices (e.g., an eNB according to a cloud-RAN (C-RAN) implementation).
  • the application circuitry 902 may include one or more application processors.
  • the application circuitry 902 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.
  • the baseband circuitry 904 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 904 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 906 and to generate baseband signals for a transmit signal path of the RF circuitry 906.
  • Baseband processing circuity 904 may interface with the application circuitry 902 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 906.
  • the baseband circuitry 904 may include a second generation (2G) baseband processor 904a, third generation (3G) baseband processor 904b, fourth generation (4G) baseband processor 904c, and/or other baseband processor(s) 904d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.).
  • the baseband circuitry 904 e.g., one or more of baseband processors 904a-d
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 904 may include Fast-Fourier Transform (FFT), precoding, and/or constellation
  • encoding/decoding circuitry of the baseband circuitry 904 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
  • the baseband circuitry 904 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements.
  • a central processing unit (CPU) 904e of the baseband circuitry 904 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers.
  • the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 904f.
  • the audio DSP(s) 904f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • the baseband circuitry 904 may further include memory/storage 904g.
  • the memory/storage 904g may be used to load and store data and/or instructions for operations performed by the processors of the baseband circuitry 904.
  • Memory/storage for one embodiment may include any combination of suitable volatile memory and/or non-volatile memory.
  • the memory/storage 904g may include any combination of various levels of memory/storage including, but not limited to, read-only memory (ROM) having embedded software instructions (e.g., firmware), random access memory (e.g., dynamic random access memory (DRAM)), cache, buffers, etc.
  • ROM read-only memory
  • DRAM dynamic random access memory
  • the memory/storage 904g may be shared among the various processors or dedicated to particular processors.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 904 and the application circuitry 902 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 904 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 904 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 904 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 906 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 906 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 906 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 908 and provide baseband signals to the baseband circuitry 904.
  • RF circuitry 906 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 904 and provide RF output signals to the FEM circuitry 908 for transmission.
  • the RF circuitry 906 may include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 906 may include mixer circuitry 906a, amplifier circuitry 906b and filter circuitry 906c.
  • the transmit signal path of the RF circuitry 906 may include filter circuitry 906c and mixer circuitry 906a.
  • RF circuitry 906 may also include synthesizer circuitry 906d for synthesizing a frequency for use by the mixer circuitry 906a of the receive signal path and the transmit signal path.
  • the mixer circuitry 906a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 908 based on the synthesized frequency provided by synthesizer circuitry 906d.
  • the amplifier circuitry 906b may be configured to amplify the down-converted signals and the filter circuitry 906c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 904 for further processing.
  • the output baseband signals may be zero- frequency baseband signals, although this is not a requirement.
  • mixer circuitry 906a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 906a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 906d to generate RF output signals for the FEM circuitry 908.
  • the baseband signals may be provided by the baseband circuitry 904 and may be filtered by filter circuitry 906c.
  • the filter circuitry 906c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 906a of the receive signal path and the mixer circuitry 906a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively.
  • the mixer circuitry 906a of the receive signal path and the mixer circuitry 906a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 906a of the receive signal path and the mixer circuitry 906a may be arranged for direct downconversion and/or direct upconversion, respectively.
  • the mixer circuitry 906a of the receive signal path and the mixer circuitry 906a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 906 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 904 may include a digital baseband interface to communicate with the RF circuitry 906.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the
  • the synthesizer circuitry 906d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 906d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 906d may be configured to synthesize an output frequency for use by the mixer circuitry 906a of the RF circuitry 906 based on a frequency input and a divider control input.
  • the synthesizer circuitry 906d may be a fractional N/N+1 synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 904 or the applications processor 902 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 902.
  • Synthesizer circuitry 906d of the RF circuitry 906 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
  • the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip- flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 906d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 906 may include an IQ/polar converter.
  • FEM circuitry 908 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 910, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 906 for further processing.
  • FEM circuitry 908 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 906 for transmission by one or more of the one or more antennas 91 0.
  • the FEM circuitry 908 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 906).
  • LNA low-noise amplifier
  • the transmit signal path of the FEM circuitry 908 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 906), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 91 0.
  • PA power amplifier
  • the electronic device 900 may include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.
  • additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.
  • the radio frequency (RF) circuitry may be to communicate with one or more UEs in a UE group via a device to device (D2D/ProSe) protocol.
  • the baseband circuitry may be to initiate a group handover request based on aggregate link quality of the one or more UEs in the UE group.
  • the baseband circuitry may be to identify a target BS based on aggregate link quality of one or more UEs in a UE group.
  • the RF circuitry may be to transmit a handover command to one or more UEs in the UE group.
  • FIG. 10 further illustrates an example architecture that supports group mode operation in UE devices by providing network assistance in the formation
  • the architecture of FIG. 10 can be adapted for use with ProSe function in both the UE device and the network as part of any D2D communications, components or operations discussed herein.
  • the architecture includes a network 1 000 that wirelessly communicates with a plurality of UE devices 1 1 0, 1 1 6, or other networked devices.
  • the network 1000 can include E-UTRAN equipment, ProSe function circuitry 101 0 as part of or comprising the D2D or ProSe interface components (e.g., 232 or 240), and an evolved packet core (EPC) network.
  • the ProSe function circuitry 1010 functions in a manner similar to or with other components discussed herein (e.g., the group HO component or D2D labeled components), and can be an extension of the ProSe function.
  • the UE devices described herein can further include UE ProSe circuitry 1030.
  • UE ProSe circuitry 1 030 can be configured to interact with the group management circuitry 1010 to obtain support from the network for setting up group communication.
  • Each UE device can include PC5 interface circuitry (not shown) that functions in a manner similar to D2D interface components as following the PC5 protocol as detailed further in TS 23.303 of 3GPP specifications.
  • the network e.g., E-UTRAN or EPC network
  • the network can allocate resources on a per group basis using group information about UE devices and groups that is
  • the network 1 000 can utilize the group management circuitry 1010 to facilitate efficient formation and management of groups throughout the entirety of the covered region.
  • the ProSe function circuitry 101 0 can allow for the forming and managing of groups in the link layer (e.g., by the E- UTRAN) which optimizes resource allocation and access methods leading to reduced latency.
  • This link layer based approach can address the deficiencies in handling group management in the application layer.
  • the example network and devices can also be considered in the context of cooperative driving or other network cooperative management operations for network deivces.
  • the network assisted group management techniques described herein are equally applicable to groups of UE devices that utilize D2D communication to cooperate in any way.
  • Each UE device can communicate with the E-UTRAN by way of an LTE-Uu interface and with other UE devices in a group by way of a PC5 interface.
  • the UE ProSe circuitry 1030 in each UE device can be configured to generate, transmit, receive, and process group messages according to predetermined rules that apply to a UE device operating in group mode. Group messages are generated based on responsibilities that are assigned to a UE device by virtue of the UE device's membership in a group.
  • the UE device's actions are controlled to some extent based on group messages received from other group members.
  • group messages communicate information between group members that is used by the group members to coordinate actions of the group members.
  • the UE devices in a group are all configured according to the same group configuration data which is generated based on group information maintained by the ProSe function circuitry 1010.
  • Examples of group messages can include sensor data generated by a UE device's onboard sensors (not shown).
  • the sensor data can indicate the UE device's speed, trajectory, and other information that is useful in coordinating synchronized movement with other group members.
  • Using device-to-device communication of sensor data enables the data to be shared in near real-time, which facilitates the
  • Event notifications can also communicated in group messages. Event notifications can notify other group members that the UE device is going to take some action like stopping, steering, and so on. Group messages can also pertain to the UE device's membership in the group, such as alerting the group members that UE device is joining the group or that the UE device is leaving the group and should no longer be involved in synchronization of movement between the UE devices in the group. Group messages cam be exchanged between group members as prescribed by configuration data received from the ProSe function circuitry 1010.
  • the UE device 1005 can receive group configuration data from the E-UTRAN on the LTE-Uu interface, for example, and configure various aspects of operation of the PC5 interface or D2D interface component, for example, in order to communicate group messages within a group to which the UE device 1 005 belongs.
  • the UE device 1005 can configure the PC5 interface circuitry 140 to utilize a frequency band specified in the configuration data that is assigned to the group.
  • the UE device can also configure the PC5 interface circuitry to use a particular transmission mode (e.g., scheduled or contention-based) specified by the configuration data that is used by the group members.
  • the transmission mode defines the protocol that the UE device should use in order to access the allocated resources.
  • the transmission mode may be contention-based (the UE devices listen before transmitting) or scheduled (each UE device is given a slot, such as a message slot or communication band/duration).
  • the ProSe function circuitry 101 0 can initiate or enable the network 1000 to allocate resources on a group basis. This means that at its creation Group 1 is allocated a certain set of resources, such as a group of resource blocks, which can then follow Group 1 . As the membership of Group 1 changes the resources allocated to Group 1 remain the same unless the resources are explicitly changed by the network 1000. This means that an individual UE device that is a member of a group and seeks to send a group message to another group member does not need to obtain, from the network 1000, the resources to do so. The UE device may use the resources allocated to all group members throughout its membership in the group. This reduces latency and improves the reliability of the communication between group members.
  • the ProSe function circuitry 1010 controls allocation of resources amongst various groups of UE devices.
  • the ProSe function circuitry 1 010 is illustrated as shared between the E-UTRAN and the core network because some of the functions of the ProSe function circuitry 1 010 can be distributed out to individual eNBs depending on the individual eNB capabilities or desired level of core network control over group management.
  • the eNB may allocate radio resources using information from the core network and also group information maintained by the ProSe function circuitry 1 010.
  • the core network may determine the radio resource allocation for the group.
  • the ProSe function circuitry 1010 generates instructions that, when executed by the core network, cause the collection and storage of "group information" 1015.
  • Group information is information about groups of UE devices.
  • the ProSe function circuitry 101 0 generates instructions that, when executed the E-UTRAN RF circuitry, causes the E-UTRAN RF circuitry to i) communicate with the EPC network to obtain the group information for a group that can be used to define the resources to be allocated to the group and ii) transmit the configuration data, including the allocated resources, to the LTE-Uu interface circuitry of the UE devices in a group.
  • processor can refer to substantially any computing processing unit or device including, but not limited to including, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology;
  • a processor can refer to an integrated circuit, an application specific integrated circuit, a digital signal processor, a field programmable gate array, a programmable logic controller, a complex programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions and/or processes described herein.
  • Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of mobile devices.
  • a processor may also be implemented as a combination of computing processing units.
  • memory components or entities embodied in a “memory,” or components including the memory. It is noted that the memory components described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.
  • nonvolatile memory for example, can be included in a memory, non-volatile memory (see below), disk storage (see below), and memory storage (see below). Further, nonvolatile memory can be included in read only memory, programmable read only memory, electrically programmable read only memory, electrically erasable programmable read only memory, or flash memory.
  • Volatile memory can include random access memory, which acts as external cache memory.
  • random access memory is available in many forms such as synchronous random access memory, dynamic random access memory, synchronous dynamic random access memory, double data rate synchronous dynamic random access memory, enhanced synchronous dynamic random access memory, Synchlink dynamic random access memory, and direct Rambus random access memory.
  • the disclosed memory components of systems or methods herein are intended to include, without being limited to including, these and any other suitable types of memory.
  • Examples can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including instructions that, when performed by a machine cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described herein.
  • Example 1 is an apparatus configured to be employed by a user equipment (UE), the apparatus comprising: a cellular network interface component configured to generate and process cellular network communications on one or more network channels to enable a cellular handover in a wireless network and a formation of a device-to-device (D2D) group with one or more additional UEs via one or more D2D channels that communicatively couple the D2D group; and a ProSe interface
  • UE user equipment
  • the component communicatively coupled to the cellular network interface component, configured to generate and process D2D communications on the one or more D2D channels among the D2D group, and enable a D2D group handover based on at least one of: the cellular network communications or the D2D communications.
  • Example 2 includes the subject matter of Examples 2, including or omitting any elements, further comprising: a channel quality measurement component configured to generate measurements of the one or more network channels and the one or more D2D channels, and provide the measurements to a group leader UE of the one or more additional UEs via the one or more D2D channels, or to an eNB via the one or more network channels as the group leader UE via the cellular network interface component.
  • a channel quality measurement component configured to generate measurements of the one or more network channels and the one or more D2D channels, and provide the measurements to a group leader UE of the one or more additional UEs via the one or more D2D channels, or to an eNB via the one or more network channels as the group leader UE via the cellular network interface component.
  • Example 3 includes the subject matter of any of Examples 1 -2, including or omitting any elements, further comprising: a D2D handover component configured to control channel quality measurement reports from the one or more additional UEs of the D2D group and enable the D2D group handover between a source evolved NodeB (eNB) and a target eNB by processing or generating a D2D group handover trigger, wherein the D2D group handover comprises a handover operation of the cellular network communications and the D2D communications.
  • a D2D handover component configured to control channel quality measurement reports from the one or more additional UEs of the D2D group and enable the D2D group handover between a source evolved NodeB (eNB) and a target eNB by processing or generating a D2D group handover trigger, wherein the D2D group handover comprises a handover operation of the cellular network communications and the D2D communications.
  • eNB source evolved NodeB
  • Example 4 includes the subject matter of any of Examples 1 -3, including or omitting any elements, wherein the D2D handover component is further configured to generate a group handover request to initiate the D2D group handover in response to a channel link quality of at least one of: the one or more network channels with a source eNB or between the one or more additional UEs and the source eNB failing to satisfy a channel link quality threshold value for a period of time, in response to a determination that the channel link quality for a predetermined portion of the one or more additional UEs of the D2D group fails to satisfy the channel link quality threshold value for the period of time, or in response to another determination that the predetermined portion of the one or more additional UEs of the D2D group satisfy another channel link quality threshold value for the period of time with a neighbor network of the target eNB that is greater than the channel link quality with the source eNB.
  • Example 5 includes the subject matter of any of Examples 1 -4, including or omitting any elements, wherein the cellular network interface component comprises a same front end module as the ProSe interface component and is further configured to process a communication command from a source eNB that identifies an individual UE handover or the D2D group handover to a target eNB, wherein the communication command includes a radio resource configuration information corresponding to at least one of: the one or more network channels via the cellular network interface component or the one or more D2D channels via the ProSe interface component for communication of a resource pool that allocates group communications to the D2D group.
  • the cellular network interface component comprises a same front end module as the ProSe interface component and is further configured to process a communication command from a source eNB that identifies an individual UE handover or the D2D group handover to a target eNB, wherein the communication command includes a radio resource configuration information corresponding to at least one of: the one or more network channels via the cellular network interface component
  • Example 6 includes the subject matter of any of Examples 1 -5, including or omitting any elements, wherein the cellular network interface component is further configured to process a different resource pool that allocates a set of group
  • the communication resources to the one or more additional UEs of the D2D group, and in response to a reception of the different resource pool, or after a completion of the D2D group handover from a source eNB to a target eNB, based on whether the different resource pool comprises an unlicensed band or an unlicensed band, initiate utilizing the different resource pool to communicatively couple the one or more additional UEs of the D2D group or one or more different UEs of a different D2D group.
  • Example 7 includes the subject matter of any of Examples 1 -6, including or omitting any elements, wherein the cellular network interface component is further configured to process a different resource pool that allocates a set of group communication resources to the one or more additional UEs of the D2D group after a time synchronization with a target eNB.
  • Example 8 includes the subject matter of any of Examples 1 -7, including or omitting any elements, wherein the ProSe interface component is further configured to process a communication command from a source eNB that identifies a UE of the D2D group for an individual UE handover or the D2D group for the D2D group handover to a target eNB, and in response to the communication command, perform a random access to obtain an uplink (UL) timing advance (TA) value that enables a UL synchronization with the target eNB or communicate via the one or more D2D channels to the UE of the D2D group to perform the random access, and further assist other UEs of the D2D group to acquire the UL synchronization by communication the UL TA value via the one or more D2D channels.
  • UL uplink
  • TA timing advance
  • Example 9 includes the subject matter of any of Examples 1 -8, including or omitting any elements, wherein the ProSe interface component is further configured to communicate a failure notification to a UE group leader of the D2D group in response to failing to complete the D2D group handover to a target eNB, to terminate the D2D group handover or inform the target eNB or a source eNB of a partial D2D group handover in response to at least one of the one or more additional UEs of the D2D group failing to complete the D2D group handover to the target eNB, or form a second D2D group of UEs communicatively coupled together via the one or more D2D channels and the source eNB in response to failing to complete the D2D group handover to the target eNB.
  • Example 10 is an apparatus configured to be employed by evolved NodeB (eNB) comprising: a cellular network interface component configured to generate and process cellular network communications on one or more network channels to enable a cellular handover in a wireless network and a formation of a device-to-device (D2D) group with a plurality of UEs via one or more D2D channels that communicatively couple the plurality of UEs of the D2D group; and a ProSe interface component, communicatively coupled to the cellular network interface component, configured to enable D2D communications on the one or more D2D channels among the D2D group, and enable a D2D group handover based on a set of predetermined criteria.
  • eNB evolved NodeB
  • Example 1 1 includes the subject matter of Example 10, including or omitting any elements, further comprising: a channel quality measurement component further configured to receive an aggregated measurement report, and a D2D group handover request or an individual handover request for the cellular handover, from at least one UE of the plurality of UEs in the D2D group.
  • Example 12 includes the subject matter of any of Examples 10-1 1 , including or omitting any elements, wherein the set of predetermined criteria comprises at least one of: a worse UE measurement of a channel link quality value, measurements from the plurality of UEs of the D2D group, an average measurement value of measurements from the D2D group, or one or more measurement reports from a UE group leader of the plurality of UEs of the D2D group requesting the D2D group handover.
  • the set of predetermined criteria comprises at least one of: a worse UE measurement of a channel link quality value, measurements from the plurality of UEs of the D2D group, an average measurement value of measurements from the D2D group, or one or more measurement reports from a UE group leader of the plurality of UEs of the D2D group requesting the D2D group handover.
  • Example 13 includes the subject matter of any of Examples 10-12, including or omitting any elements, further comprising: a D2D handover component configured to designate a UE group leader on behalf of the plurality of UEs of the D2D group to aggregate measurements from the plurality of UEs of the D2D group and communicate one or more resource pools to other UEs of the D2D group to enable the D2D communications, or communicate the D2D communications to a UE of the D2D group requesting an individual handover via the cellular handover in response to not detecting a target eNB that is suitable for the UE.
  • a D2D handover component configured to designate a UE group leader on behalf of the plurality of UEs of the D2D group to aggregate measurements from the plurality of UEs of the D2D group and communicate one or more resource pools to other UEs of the D2D group to enable the D2D communications, or communicate the D2D communications to a UE of the D2D group requesting an individual
  • Example 14 includes the subject matter of any of Examples 10-13, including or omitting any elements, wherein the D2D handover component is further configured to complete any uplink (UL) plane data transmission in a buffer, release a UL connection with the plurality of UEs in the D2D group after the D2D group handover, and determine whether the D2D group continues to utilize a current D2D channel of the one or more D2D channels or a new D2D channel based on measurements of the one or more D2D channels from the D2D group or information from the target eNB related to the current D2D channel within a coverage area of the target eNB.
  • UL uplink
  • Example 15 includes the subject matter of any of Examples 10-14, including or omitting any elements, wherein the set of predetermined criteria comprise at least one of: a link quality threshold corresponding to the one or more network channels related to the plurality of UEs in the D2D group, a group threshold related to the link quality threshold, a neighboring cell quality threshold in a comparison with the group threshold or the link quality threshold, or one or more requests for the D2D group handover or the cellular handover for a UE of the D2D group.
  • the set of predetermined criteria comprise at least one of: a link quality threshold corresponding to the one or more network channels related to the plurality of UEs in the D2D group, a group threshold related to the link quality threshold, a neighboring cell quality threshold in a comparison with the group threshold or the link quality threshold, or one or more requests for the D2D group handover or the cellular handover for a UE of the D2D group.
  • Example 16 includes the subject matter of any of Examples 10-15, including or omitting any elements, further comprising: a handover command component configured to generate a group handover command and enable communication of the group handover command to a UE group leader of the D2D group or the plurality of UEs of the D2D group, wherein the group handover command comprises at least one of: an indication of the D2D group handover to a target eNB, a radio resource configuration (RRC) information related to the cellular network communications, or other RRC information related to the D2D communications, wherein the other RRC information comprises a radio resource pool allocated to the D2D group to enable the D2D communications via an unlicensed band or a licensed band.
  • RRC radio resource configuration
  • Example 17 includes the subject matter of any of Examples 10-16, including or omitting any elements, wherein the handover command component is further configured to communicate the radio resource pool to the UE group leader or the plurality of UEs of the D2D group that enables the D2D communications after receiving the D2D group handover from a source eNB and time synchronizing with the plurality of UEs of the D2D group.
  • Example 18 includes the subject matter of any of Examples 10-17, including or omitting any elements, wherein the handover command component is further configured to generate a group handover complete command to a network transmission path in response to a completion of the cellular handover for a UE of the D2D group or the D2D group handover.
  • Example 19 includes the subject matter of any of Examples 10-18, including or omitting any elements, wherein the cellular network interface component is further configured to enable the cellular handover with a first set of one or more UEs of the D2D group while remaining to serve a second set of one or more UEs of the D2D group, and wherein the D2D group utilizes resources of the target eNB for the D2D
  • Example 20 includes the subject matter of any of Examples 10-19, including or omitting any elements, wherein the cellular network interface component is further configured to communicate a failure notification or a partial handover notification in response to a failure to complete the D2D group handover with one or more of the plurality of UEs of the D2D group; wherein the cellular network interface component is further configured to terminate the D2D group handover in response to at least one UE of the D2D group failing to complete the D2D group handover, or form a second D2D group with UEs communicatively coupled together via the one or more D2D channels and a source eNB in response to the failure to complete the D2D group handover to a target eNB with a UE of the D2D group, and the second D2D group is configured to utilize resources common to another eNB as the source eNB or the target eNB.
  • Example 21 is a computer-readable storage medium storing executable instructions that, in response to execution, cause a processor of a user equipment (UE) to perform operations, comprising: processing a cellular network communication on a network channel to enable a formation of a device-to-device (D2D) group with a UE via one or more D2D channels that communicatively couple UEs of the D2D group; and controlling a D2D communication on the one or more D2D channels among the D2D group, and a D2D group handover based on at least one of: the cellular network communication or the D2D communication.
  • D2D device-to-device
  • Example 22 includes the subject matter of Example 21 , including or omitting any elements, wherein the operations further comprise: generating measurements of the network channel and the one or more D2D channels, and providing the
  • the D2D group handover comprises a handover operation of cellular network communications and the D2D communications for the D2D group
  • the D2D group handover trigger is processed or generated in response to a channel link quality of at least one of: the network channel with a source eNB or between the UEs and the source eNB, failing to satisfy a channel link quality threshold value for a period of time, in response to a determination that the channel link quality for a predetermined portion of the UEs of the D2D group fails to satisfy the channel link quality threshold value for the period of time, or in response to another determination that the predetermined portion of the UEs of the D2D group satisfy another channel link quality for the period of time with a
  • Example 23 includes the subject matter of any of Examples 21 -22, including or omitting any elements, wherein the operations further comprise one or more of: processing a handover communication command from a source eNB that identifies an individual UE handover or the D2D group handover to a target eNB, wherein the handover communication command includes a radio resource configuration (RRC) information corresponding to at least one of: the network channel or the one or more D2D channels for communication of a resource pool that allocates group communications to the D2D group; processing a different resource pool that allocates a set of group communication resources to the UEs of the D2D group, and in response to a reception of the different resource pool, or after a completion of the D2D group handover from the source eNB to the target eNB, based on whether the different resource pool comprises an unlicensed band or an unlicensed band, utilize the different resource pool to communicatively couple the UEs of the D2D group or one or more different UEs of a
  • Example 24 includes the subject matter of any of Examples 21 -23, including or omitting any elements, wherein the operations further comprise one or more of: communicating a failure notification to a UE group leader of the D2D group in response to a failure of the D2D group handover to a target eNB; terminating the D2D group handover, or informing at least one of the target eNB or a source eNB of a partial D2D group handover in response to at least one of the UEs of the D2D group failing to complete the D2D group handover to the target eNB; forming a second D2D group of UEs communicatively coupled together via the one or more D2D channels and the source eNB in response to failing to complete the D2D group handover to the target eNB; or communicating on the one or more D2D channels with UEs of the D2D group via common resources between the target eNB and the source eNB in response to UE of the D2D group failing to
  • Example 25 is a computer-readable storage medium storing executable instructions that, in response to execution, cause a processor of an evolved NodeB (eNB) to perform operations, comprising: processing a cellular network communication on a network channel to enable a cellular handover in a wireless network and a formation of a device-to-device (D2D) group with a plurality of UEs via one or more D2D channels that communicatively couple the plurality of UEs of the D2D group; and controlling D2D communications on the one or more D2D channels among the D2D group, and a D2D group handover based on a set of predetermined criteria.
  • eNB evolved NodeB
  • Example 26 includes the subject matter of Examples 25, including or omitting any elements, wherein the operations further comprise: receiving an aggregated measurement report, and a D2D group handover request or an individual handover request, from at least one UE of the plurality of UEs in the D2D group, wherein the set of predetermined criteria comprises at least one of: a worse UE measurement of a channel link quality value from the D2D group, measurements from the plurality of UEs of the D2D group, an average measurement value of measurements from the D2D group, one or more measurement reports from a UE group leader of the plurality of UEs of the D2D group requesting the D2D group handover, a link quality threshold corresponding to one or more network channels related to the plurality of UEs in the D2D group, a group threshold related to the link quality threshold, a neighboring cell quality threshold in a comparison with the group threshold or the link quality threshold, or one or more requests for the D2D group handover or the cellular handover for
  • Example 27 includes the subject matter of any of Examples 25-26, including or omitting any elements, wherein the operations further comprise: designating a UE group leader to communicate on behalf of the D2D group to aggregate measurements from the plurality of UEs of the D2D group, communicate one or more resource pools to other UEs of the D2D group to enable the D2D communications, or communicate the D2D communications to a UE of the D2D group requesting an individual handover via the cellular handover in response to failing to perform the cellular handover for the UE of the D2D group.
  • Example 28 includes the subject matter of any of Examples 25-27, including or omitting any elements, wherein the operations further comprise: completing one or more uplink (UL) plane data transmission in a buffer, release a UL connection with the plurality of UEs in the D2D group after the D2D group handover, and determine whether the D2D group continues to utilize a current D2D channel of the one or more D2D channels or a new D2D channel based on measurements of the one or more D2D channels from the D2D group or information from a target eNB related to the current D2D channel within a coverage area of the target eNB.
  • UL uplink
  • Example 29 includes the subject matter of any of Examples 25-28, including or omitting any elements, wherein the operations further comprise: generating a group handover command and enable communication of the group handover command to a UE group leader of the D2D group or the plurality of UEs of the D2D group, wherein the group handover command comprises at least one of: an indication of the D2D group handover to a target eNB, a radio resource configuration (RRC) information related to cellular network communications, or other RRC information related to the D2D communications, wherein the other RRC information comprises a radio resource pool allocated to the D2D group to enable the D2D communications via an unlicensed band or a licensed band.
  • RRC radio resource configuration
  • Example 30 includes the subject matter of any of Examples 25-29, including or omitting any elements, wherein the operations further comprise one or more of: communicating a failure notification or a partial handover notification in response to a failure to complete the D2D group handover with one or more of the plurality of UEs of the D2D group, a target eNB or a source eNB; terminating the D2D group handover in response to at least one UE of the D2D group failing to complete the D2D group handover; or forming a second D2D group with one or more UEs communicatively coupled together via the one or more D2D channels and the source eNB in response to the failure to complete the D2D group handover to the target eNB with a UE of the D2D group, wherein the second D2D group is configured to utilize resources common to another eNB as the source eNB or the target eNB.
  • Example 31 is an apparatus configured to be employed within a user equipment (UE) comprising: means for processing configured to process a cellular network communication on a network channel to enable a formation of a device-to- device (D2D) group with a UE via one or more D2D channels that communicatively couple UEs of the D2D group; and means for controlling a D2D communication on the one or more D2D channels among the D2D group, and a D2D group handover based on at least one of: the cellular network communication or the D2D communication.
  • D2D device-to- device
  • Example 32 includes the subject matter of Examples 31 , including or omitting any elements, further comprising: means for generating measurements of the network channel and the one or more D2D channels, and providing the measurements to a UE group leader of the UEs of the D2D group via the one or more D2D channels, or providing the measurements, further comprises other measurements from the D2D group, to an eNB via the network channel as the UE group leader; and means for processing or generating a D2D group handover trigger, wherein the D2D group handover comprises a handover operation of cellular network communications and the D2D communications for the D2D group, wherein the D2D group handover trigger is processed or generated in response to a channel link quality of at least one of: the network channel with a source eNB or between the UEs and the source eNB, failing to satisfy a channel link quality threshold value for a period of time, in response to a determination that the channel link quality for a predetermined portion of the UEs of the D2
  • Example 33 includes the subject matter of any of Examples 31 -32, including or omitting any elements, wherein the means for processing is further configured to perform at least one of: process a handover communication command from a source eNB that identifies an individual UE handover or the D2D group handover to a target eNB, wherein the handover communication command includes a radio resource configuration (RRC) information corresponding to at least one of: the network channel or the one or more D2D channels for communication of a resource pool that allocates group communications to the D2D group; process a different resource pool that allocates a set of group communication resources to the UEs of the D2D group, and in response to a reception of the different resource pool, or after a completion of the D2D group handover from the source eNB to the target eNB, based on whether the different resource pool comprises an unlicensed band or an unlicensed band, utilize the different resource pool to communicatively couple the UEs of the D2D group or one or more different
  • Example 34 includes the subject matter of any of Examples 31 -33, including or omitting any elements, further comprising one or more of: means for communicating a failure notification to a UE group leader of the D2D group in response to a failure of the D2D group handover to a target eNB; means for terminating the D2D group handover, or informing at least one of the target eNB or a source eNB of a partial D2D group handover in response to at least one of the UEs of the D2D group failing to complete the D2D group handover to the target eNB; means for forming a second D2D group of UEs communicatively coupled together via the one or more D2D channels and the source eNB in response to failing to complete the D2D group handover to the target eNB; or means for communicating on the one or more D2D channels with UEs of the D2D group via common resources between the target eNB and the source eNB in response to UE of the D
  • Example 35 is an apparatus configured to be employed within an evolved NodeB (eNB) comprising: means for processing a cellular network communication on a network channel to enable a cellular handover in a wireless network and a formation of a device-to-device (D2D) group with a plurality of UEs via one or more D2D channels that communicatively couple the plurality of UEs of the D2D group; and means for controlling D2D communications on the one or more D2D channels among the D2D group, and a D2D group handover based on a set of predetermined criteria.
  • eNB evolved NodeB
  • Example 36 includes the subject matter of Example 35, including or omitting any elements, further comprising: means for receiving an aggregated measurement report, and a D2D group handover request or an individual handover request, from at least one UE of the plurality of UEs in the D2D group, wherein the set of predetermined criteria comprises at least one of: a worse UE measurement of a channel link quality value from the D2D group, measurements from the plurality of UEs of the D2D group, an average measurement value of measurements from the D2D group, one or more measurement reports from a UE group leader of the plurality of UEs of the D2D group requesting the D2D group handover, a link quality threshold corresponding to one or more network channels related to the plurality of UEs in the D2D group, a group threshold related to the link quality threshold, a neighboring cell quality threshold in a comparison with the group threshold or the link quality threshold, or one or more requests for the D2D group handover or the cellular handover for
  • Example 37 includes the subject matter of any of Examples 35-36, including or omitting any elements, further comprising: means for designating a UE group leader to communicate on behalf of the D2D group to aggregate measurements from the plurality of UEs of the D2D group, communicate one or more resource pools to other UEs of the D2D group to enable the D2D communications, or communicate the D2D communications to a UE of the D2D group requesting an individual handover via the cellular handover in response to failing to perform the cellular handover for the UE of the D2D group.
  • Example 38 includes the subject matter of any of Examples 35-37, including or omitting any elements, further comprising: means for completing one or more uplink (UL) plane data transmission in a buffer, release a UL connection with the plurality of UEs in the D2D group after the D2D group handover, and determine whether the D2D group continues to utilize a current D2D channel of the one or more D2D channels or a new D2D channel based on measurements of the one or more D2D channels from the D2D group or information from a target eNB related to the current D2D channel within a coverage area of the target eNB.
  • UL uplink
  • Example 39 includes the subject matter of any of Examples 35-38, including or omitting any elements, further comprising: means for generating a group handover command and enable communication of the group handover command to a UE group leader of the D2D group or the plurality of UEs of the D2D group, wherein the group handover command comprises at least one of: an indication of the D2D group handover to a target eNB, a radio resource configuration (RRC) information related to cellular network communications, or other RRC information related to the D2D communications, wherein the other RRC information comprises a radio resource pool allocated to the D2D group to enable the D2D communications via an unlicensed band or a licensed band.
  • RRC radio resource configuration
  • Example 40 includes the subject matter of any of Examples 35-38, including or omitting any elements, further comprising: means for communicating a failure notification or a partial handover notification in response to a failure to complete the D2D group handover with one or more of the plurality of UEs of the D2D group, a target eNB or a source eNB; means for terminating the D2D group handover in response to at least one UE of the D2D group failing to complete the D2D group handover; or forming a second D2D group with one or more UEs communicatively coupled together via the one or more D2D channels and the source eNB in response to the failure to complete the D2D group handover to the target eNB with a UE of the D2D group, wherein the second D2D group is configured to utilize resources common to another eNB as the source eNB or the target eNB.
  • Example 41 is an apparatus configured to be employed by a user equipment (UE), the apparatus comprising: a processor configured to: generate and process cellular network communications on one or more network channels to enable a cellular handover in a wireless network and a formation of a device-to-device (D2D) group with one or more additional UEs via one or more D2D channels that communicatively couple the D2D group; and generate and process D2D communications on the one or more D2D channels among the D2D group, and enable a D2D group handover based on at least one of: the cellular network communications or the D2D communications.
  • a processor configured to: generate and process cellular network communications on one or more network channels to enable a cellular handover in a wireless network and a formation of a device-to-device (D2D) group with one or more additional UEs via one or more D2D channels that communicatively couple the D2D group; and generate and process D2D communications on the one or more D2D channels among
  • Example 42 is an apparatus configured to be employed by evolved NodeB (eNB) comprising: a processor configured to: generate and process cellular network communications on one or more network channels to enable a cellular handover in a wireless network and a formation of a device-to-device (D2D) group with a plurality of UEs via one or more D2D channels that communicatively couple the plurality of UEs of the D2D group; and enable D2D communications on the one or more D2D channels among the D2D group, and enable a D2D group handover based on a set of
  • eNB evolved NodeB
  • Example 43 includes the subject matter of any of Examples 1 -20, including or omitting any elements, wherein the ProSe interface component comprises a PC5 interface.
  • Example 44 includes the subject matter of any of Examples 1 -20, including or omitting any elements, wherein the D2D communications occur on a sidelink channel.
  • Example 45 includes the subject matter of any of Examples 1 -20, including or omitting any elements, wherein the cellular interface component comprises an LTE-Uu interface.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media or a computer readable storage device can be any available media that can be accessed by a general purpose or special purpose computer.
  • such computer- readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or other tangible and/or non-transitory medium, that can be used to carry or store desired information or executable instructions.
  • any connection is properly termed a computer-readable medium.
  • coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
  • coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • Disk and disc includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor can be a microprocessor, but, in the alternative, processor can be any conventional processor, controller, microcontroller, or state machine.
  • a processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Additionally, at least one processor can comprise one or more modules operable to perform one or more of the s and/or actions described herein.
  • modules e.g., procedures, functions, and so on
  • Software codes can be stored in memory units and executed by processors.
  • Memory unit can be implemented within processor or external to processor, in which case memory unit can be communicatively coupled to processor through various means as is known in the art.
  • at least one processor can include one or more modules operable to perform functions described herein.
  • a CDMA system can implement a radio technology such as Universal Terrestrial Radio Access (UTRA), CDMA1800, etc.
  • UTRA includes Wideband-CDMA (W-CDMA) and other variants of CDMA.
  • W-CDMA Wideband-CDMA
  • CDMA1800 covers IS-1800, IS-95 and IS-856 standards.
  • a TDMA system can implement a radio technology such as Global System for Mobile
  • GSM Global System for Mobile Communications
  • An OFDMA system can implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.1 1 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.18, Flash-OFDML , etc.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • Wi-Fi Wi-Fi
  • WiMAX WiMAX
  • IEEE 802.18, Flash-OFDML etc.
  • UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS).
  • 3GPP Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA, which employs OFDMA on downlink and SC-FDMA on uplink.
  • UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP).
  • CDMA1 800 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • 3GPP2 3rd Generation Partnership Project 2
  • such wireless communication systems can additionally include peer-to-peer (e.g., mobile-to-mobile) ad hoc network systems often using unpaired unlicensed spectrums, 802. xx wireless LAN, BLUETOOTH and any other short- or long- range, wireless communication techniques.
  • SC-FDMA Single carrier frequency division multiple access
  • SC-FDMA has similar performance and essentially a similar overall complexity as those of OFDMA system.
  • SC-FDMA signal has lower peak-to-average power ratio (PAPR) because of its inherent single carrier structure.
  • PAPR peak-to-average power ratio
  • SC-FDMA can be utilized in uplink communications where lower PAPR can benefit a mobile terminal in terms of transmit power efficiency.
  • various aspects or features described herein can be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques.
  • article of manufacture as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media.
  • computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., compact disk (CD), digital versatile disk (DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card, stick, key drive, etc.).
  • various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • machine-readable medium can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.
  • a computer program product can include a computer readable medium having one or more instructions or codes operable to cause a computer to perform functions described herein.
  • Communications media embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and includes any information delivery or transport media.
  • modulated data signal or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals.
  • communication media include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
  • a software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • An exemplary storage medium can be coupled to processor, such that processor can read information from, and write information to, storage medium.
  • storage medium can be integral to processor.
  • processor and storage medium can reside in an ASIC.
  • ASIC can reside in a user terminal.
  • processor and storage medium can reside as discrete components in a user terminal.
  • the s and/or actions of a method or algorithm can reside as one or any combination or set of codes and/or instructions on a machine-readable medium and/or computer readable medium, which can be incorporated into a computer program product.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Superconductors And Manufacturing Methods Therefor (AREA)
  • Inorganic Compounds Of Heavy Metals (AREA)

Abstract

Selon l'invention, un dispositif d'équipement utilisateur UE (116), un NodeB évolué ou un autre dispositif de réseau peut commander des communications de dispositif à dispositif D2D ou ProSe directes avec des dispositifs UE (110) et commander un transfert de groupe D2D avec un groupe D2D d'UE couplés en communication par l'intermédiaire d'un canal de réseau pour des communications de réseau cellulaire et un ou plusieurs canaux D2D ou ProSe. Le transfert de groupe D2D/ProSe peut être commandé sur la base d'un ensemble de critères prédéterminés. Des rapports de mesure agrégés (306) de qualité de liaison de canal peuvent être utilisés pour demander ou initier le transfert de groupe D2D, et être fournis par l'intermédiaire d'un chef de groupe d'UE (116) ou individuellement à partir de dispositifs UE (110) du groupe D2D/ProSe.
PCT/US2016/024923 2016-01-08 2016-03-30 Transfert de groupe pour des applications critiques Ceased WO2017119919A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
TW105140112A TWI786038B (zh) 2016-01-08 2016-12-05 用於關鍵任務應用的群交遞

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662276642P 2016-01-08 2016-01-08
US62/276,642 2016-01-08

Publications (1)

Publication Number Publication Date
WO2017119919A1 true WO2017119919A1 (fr) 2017-07-13

Family

ID=55661670

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/024923 Ceased WO2017119919A1 (fr) 2016-01-08 2016-03-30 Transfert de groupe pour des applications critiques

Country Status (2)

Country Link
TW (1) TWI786038B (fr)
WO (1) WO2017119919A1 (fr)

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020034425A1 (fr) 2018-11-01 2020-02-20 Zte Corporation Procédure de transfert pour communications basées sur un véhicule
WO2020048580A1 (fr) * 2018-09-03 2020-03-12 Nokia Solutions And Networks Oy Commutation de ressources radio en circulation en peloton
WO2020062096A1 (fr) * 2018-09-28 2020-04-02 Nokia Shanghai Bell Co., Ltd. Diffusion de groupe pour communication de liaison latérale
CN113273309A (zh) * 2018-11-30 2021-08-17 诺基亚技术有限公司 利用波束成形的侧链路故障恢复
US11109279B2 (en) * 2017-03-13 2021-08-31 Huawei Technologies Co., Ltd. Handover method and apparatus using radio resource reconfiguration messages
US20210360505A1 (en) * 2020-05-18 2021-11-18 Qualcomm Incorporated Using sidelink between vehicle-mounted relays to optimize user equipment mobility
CN113687752A (zh) * 2021-08-04 2021-11-23 第四范式（北京）技术有限公司 一种信息显示方法、装置、电子设备及存储介质
WO2021239251A1 (fr) * 2020-05-29 2021-12-02 Nokia Technologies Oy Synchronisation de liaison latérale dans des systèmes de télécommunication
WO2021254345A1 (fr) * 2020-06-17 2021-12-23 展讯通信（上海）有限公司 Procédé et appareil de communication, dispositif relais et dispositif terminal
CN113940024A (zh) * 2019-06-21 2022-01-14 华为技术有限公司 用于ue协作传输的基于组的标识和加扰的系统和方案
US11356903B2 (en) 2018-08-08 2022-06-07 Google Llc Device and method of configuring a handover
US11611854B2 (en) * 2021-03-09 2023-03-21 Qualcomm Incorporated Coordinated slot-based radar sensing
WO2023117411A1 (fr) * 2021-12-23 2023-06-29 Sony Group Corporation Procédés, dispositifs de communication et équipement d'infrastructure
CN116828555A (zh) * 2023-08-30 2023-09-29 华砺智行(武汉)科技有限公司 Pc5和uu自主切换的通信系统和方法
US20230403538A1 (en) * 2022-06-10 2023-12-14 Qualcomm Incorporated Managing group configurations in wireless communications systems
WO2024168841A1 (fr) * 2023-02-17 2024-08-22 Google Llc Rapport de faisceau basé sur un groupement d'équipements utilisateurs
EP4460152A3 (fr) * 2019-02-14 2024-12-18 ZTE Corporation Mesures de liaison pour liaisons de dispositif à dispositif de véhicule

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014124689A1 (fr) * 2013-02-15 2014-08-21 Nokia Solutions And Networks Oy Gestion de transfert intercellulaire
WO2015096845A1 (fr) * 2013-12-23 2015-07-02 Huawei Technologies Duesseldorf Gmbh Procédé de gestion des communications entre un premier terminal mobile et un deuxième terminal mobile

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014124689A1 (fr) * 2013-02-15 2014-08-21 Nokia Solutions And Networks Oy Gestion de transfert intercellulaire
WO2015096845A1 (fr) * 2013-12-23 2015-07-02 Huawei Technologies Duesseldorf Gmbh Procédé de gestion des communications entre un premier terminal mobile et un deuxième terminal mobile

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HWANG YOUSUN ET AL: "Group handover management for V2x in moving cell based LTE-Advanced system", 2015 INTERNATIONAL CONFERENCE ON INFORMATION AND COMMUNICATION TECHNOLOGY CONVERGENCE (ICTC), IEEE, 28 October 2015 (2015-10-28), pages 1054 - 1057, XP032830036, DOI: 10.1109/ICTC.2015.7354736 *
SUNGKYUNG KIM ET AL: "[Group Handover on the Mobile RS] ; S80216j-06_227", IEEE DRAFT; S80216J-06_227, IEEE-SA, PISCATAWAY, NJ USA, vol. 802.16j, 14 November 2006 (2006-11-14), pages 1 - 6, XP017785420 *

Cited By (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11109279B2 (en) * 2017-03-13 2021-08-31 Huawei Technologies Co., Ltd. Handover method and apparatus using radio resource reconfiguration messages
US11843977B2 (en) 2017-03-13 2023-12-12 Huawei Technologies Co., Ltd. Handover method and apparatus
US11743778B2 (en) 2018-08-08 2023-08-29 Google Llc Device and method of configuring a handover
US11356903B2 (en) 2018-08-08 2022-06-07 Google Llc Device and method of configuring a handover
CN112789886A (zh) * 2018-09-03 2021-05-11 诺基亚通信公司 车队中的无线电资源转换
US11805449B2 (en) 2018-09-03 2023-10-31 Nokia Solutions And Networks Oy Radio resource switching in platooning
US20210274390A1 (en) * 2018-09-03 2021-09-02 Nokia Solutions And Networks Oy Radio resource switching in platooning
WO2020048580A1 (fr) * 2018-09-03 2020-03-12 Nokia Solutions And Networks Oy Commutation de ressources radio en circulation en peloton
CN112789886B (zh) * 2018-09-03 2024-07-05 诺基亚通信公司 车队中的无线电资源转换
WO2020062096A1 (fr) * 2018-09-28 2020-04-02 Nokia Shanghai Bell Co., Ltd. Diffusion de groupe pour communication de liaison latérale
CN112970285A (zh) * 2018-11-01 2021-06-15 中兴通讯股份有限公司 用于基于车辆的通信的移交程序
EP3874810A4 (fr) * 2018-11-01 2022-06-22 ZTE Corporation Procédure de transfert pour communications basées sur un véhicule
US12004038B2 (en) 2018-11-01 2024-06-04 Zte Corporation Handover procedure for vehicle based communications
WO2020034425A1 (fr) 2018-11-01 2020-02-20 Zte Corporation Procédure de transfert pour communications basées sur un véhicule
CN113273309A (zh) * 2018-11-30 2021-08-17 诺基亚技术有限公司 利用波束成形的侧链路故障恢复
US12395229B2 (en) 2018-11-30 2025-08-19 Nokia Technologies Oy Failure recovery of sidelink with beamforming
EP4460152A3 (fr) * 2019-02-14 2024-12-18 ZTE Corporation Mesures de liaison pour liaisons de dispositif à dispositif de véhicule
CN113940024A (zh) * 2019-06-21 2022-01-14 华为技术有限公司 用于ue协作传输的基于组的标识和加扰的系统和方案
CN113940024B (zh) * 2019-06-21 2023-06-27 华为技术有限公司 用于ue协作传输的基于组的标识和加扰的系统和方案
US11751189B2 (en) 2019-06-21 2023-09-05 Huawei Technologies Co., Ltd. System and scheme on group based identity and scrambling for UE cooperation transmission
US12052629B2 (en) * 2020-05-18 2024-07-30 Qualcomm Incorporated Using sidelink between vehicle-mounted relays to optimize user equipment mobility
US20210360505A1 (en) * 2020-05-18 2021-11-18 Qualcomm Incorporated Using sidelink between vehicle-mounted relays to optimize user equipment mobility
US20230180159A1 (en) * 2020-05-29 2023-06-08 Nokia Technologies Oy Sidelink synchronization in telecommunication systems
WO2021239251A1 (fr) * 2020-05-29 2021-12-02 Nokia Technologies Oy Synchronisation de liaison latérale dans des systèmes de télécommunication
WO2021254345A1 (fr) * 2020-06-17 2021-12-23 展讯通信（上海）有限公司 Procédé et appareil de communication, dispositif relais et dispositif terminal
US11611854B2 (en) * 2021-03-09 2023-03-21 Qualcomm Incorporated Coordinated slot-based radar sensing
CN113687752A (zh) * 2021-08-04 2021-11-23 第四范式（北京）技术有限公司 一种信息显示方法、装置、电子设备及存储介质
WO2023117411A1 (fr) * 2021-12-23 2023-06-29 Sony Group Corporation Procédés, dispositifs de communication et équipement d'infrastructure
US20230403538A1 (en) * 2022-06-10 2023-12-14 Qualcomm Incorporated Managing group configurations in wireless communications systems
US12439228B2 (en) * 2022-06-10 2025-10-07 Qualcomm Incorporated Managing group configurations in wireless communications systems
WO2024168841A1 (fr) * 2023-02-17 2024-08-22 Google Llc Rapport de faisceau basé sur un groupement d'équipements utilisateurs
CN116828555A (zh) * 2023-08-30 2023-09-29 华砺智行(武汉)科技有限公司 Pc5和uu自主切换的通信系统和方法

Also Published As

Publication number Publication date
TWI786038B (zh) 2022-12-11
TW201735707A (zh) 2017-10-01

Similar Documents

Publication Publication Date Title
US12200556B2 (en) Modified handover procedures for earth fixed and earth mobile beams
WO2017119919A1 (fr) Transfert de groupe pour des applications critiques
US12096289B2 (en) Cell selection and reselection criteria for non-terrestrial network (NTN) networks
EP3414943B1 (fr) Systèmes et procédés pour réduire des interruptions dans des transmissions de données en raison d'opérations de transfert intercellulaire
US10980065B2 (en) Multi-connectivity of terminal device
CN108307681B (zh) 频率间公共陆地移动网络(plmn)间发现
CN110352613B (zh) 用于多rat发送的消息分割
US20230180185A1 (en) Power saving sensing for reduced sensing ues using resource re-evaluation and resource pre-emption
WO2018085374A1 (fr) Informations de système spécifiques à un point d'émission/réception
US12160783B2 (en) Handover with PSCell based on trigger message
US20230180217A1 (en) Uplink grant prioritization enhancement
WO2023130481A1 (fr) Amélioration de la sélection de ressources pour un équipement utilisateur (ue) de réception discontinue de liaison latérale (drx)
US12336017B2 (en) Channel state information reference signal (CSI-RS) based contention free random access (CFRA) in radio resource management (RRM)
US20230344492A1 (en) Fast measurement with multiple concurrent beams
US20240397361A1 (en) Reference timing for target data measurement in unlicensed spectrum for new radio
US12483971B2 (en) Measurement gap (MG) and interruption design for system information (Si) reading in multiple universal subscriber identity module (MUSIM)
US12058573B2 (en) Delay requirements determination for handover with primary secondary cell
US12137386B2 (en) Radio resource management relaxation for user equipment based on mobility state
CN119732137A (zh) 配置与集成接入和回传节点的通信
US10448237B2 (en) RRM requirement for D2D inter-carrier discovery gap
US20250266892A1 (en) Systems, methods, and devices for enhancement of layer 3 measurements and procedures for multi-receive user equipment
US20250142417A1 (en) Frequency prioritization for terminal devices receiving a multicast broadcast service
WO2018085727A1 (fr) Bidiffusion d'informations à un équipement utilisateur d'un réseau de télécommunication sans fil
WO2025093152A1 (fr) Priorisation de fréquence pour dispositifs à capacité réduite recevant un service de diffusion/multidiffusion

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

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

Country of ref document: EP

Kind code of ref document: A1