CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of United States Provisional Patent

Application Serial Number 62/268,864 filed on December 17, 2015, which is hereby incorporated herein by reference in its entirety.

BACKGROUND

[0002] Implementations of the example embodiments generally may relate to the field of wireless communications. Internet of Things (loT) applications typically involve wireless communications between devices without human intervention. Cooperative driving is one example of where vehicles share their intentions with other nearby vehicles (or roadway infrastructure, pedestrians). Such information is used by automated driving algorithms to enable accurate prediction of what others will do in the near future, and so optimize their own decisions. In synchronized cooperation, autonomous vehicles exchange and synchronize their planned trajectories to optimize driving patterns.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Some examples of circuits, apparatuses and/or methods will be described in the following by way of example only. In this context, reference will be made to the

accompanying Figures.

[0004] FIG. 1 depicts an example implementation of an architecture in which group configuration data is transmitted to groups of User Equipment (UE) devices from an evolved Node B (eNB), according to one embodiment of the disclosure. [0005] FIG. 1 A depicts an example UE device that is configured to participate in a group, according to one embodiment of the disclosure.

[0006] FIG. 1 B depicts example group information that is maintained by group management circuitry in the network of FIG. 1 , according to one embodiment of the disclosure.

[0007] FIG. 2 depicts an example flow of messages between a UE device and a core network when a new group is being created, according to one embodiment of the disclosure.

[0008] FIG. 3 depicts an example flow of messages between a UE device and a core network when a UE device joins a group, according to one embodiment of the disclosure.

[0009] FIG. 4 depicts an example flow of messages between a UE device and a core network when a UE device leaves a group, according to one embodiment of the disclosure.

[0010] FIG. 5 depicts an example flow of messages between a UE device and a core network when a joining UE device autonomously joins a group without communicating with the core network, according to one embodiment of the disclosure.

[0011] FIG. 6 depicts an example flow of messages between a UE device and a network when an existing UE device autonomously leaves a group without communicating with the core network, according to one embodiment of the disclosure.

[0012] FIG. 7 depicts a flowchart outlining an example method 700 that may be performed by a UE device acting in group mode according to one embodiment of the disclosure.

[0013] FIG. 8 depicts flowchart outlining an example method 800 that may be performed by group management circuitry managing group mode according to one embodiment according to one embodiment of the disclosure.

[0014] FIG. 9 depicts an example implementation of an architecture in which group configuration data is transmitted to groups of User Equipment (UE) devices from an

Evolved Universal Terrestrial Radio Access Network (E-UTRAN), according to one embodiment of the disclosure. [0015] FIG. 10 illustrates example components of a device, according to one embodiment of the disclosure.

DETAILED DESCRIPTION

[0016] During synchronized coordination of driving (e.g., platoon or convoy mode) vehicles form groups with reduced distance among them to improve traffic and fuel efficiency while avoiding collisions. Such higher automation and cooperation levels require data exchange between vehicles with lower latency and higher reliability than existing solutions can provide. One important characteristic of several cooperative driving applications is that they rely on exchanging sensor data and event notifications between UE devices in a group that are operating within a relatively small distance with respect to one another while jointly moving across a potentially large geographic area. Therefore, efficient and reliable group communication functionality among closely proximate devices is important to enable advanced autonomous driving applications in 5G systems.

[0017] Device-to-device communication, which is the "direct" exchange of messages or data between UE devices without intervention by an eNB, is an attractive option for providing efficient and reliable group communications for many reasons. For example, device-to-device communication can be performed with reduced latency as compared to communication via an eNB. Device-to-device communication can be performed when connection with an eNB is not possible (e.g., in a tunnel or region without cell coverage), increasing reliability.

[0018] Direct communication between UE devices can be supported by device-to- device communication functionality in long term evolution (LTE) proximity services (ProSe). Device-to-device communication is supported over dedicated resource pools, which are preconfigured or allocated by the eNB. Access to data resources within a resource pool (Physical Sidelink Shared Channel (PSSCH)) can be controlled or assigned by the eNB (mode 1 ) or acquired autonomously by the UE device (mode 2) using contention within control resources (Physical Sidelink Control Channel (PSCCH)). From the physical layer (PHY) perspective, UE device data transmissions are broadcast, i.e., all UE devices within range are potential receivers. Thus, both unicast and one-to-many communications are possible. However, there is no protocol support in the LTE ProSe radio access framework for UEs to form groups that share group-specific network assigned resource pools and use group-specific resource access methods.

[0019] It is possible to form groups at the application layer by exchanging application messages between UE devices over a ProSe interface circuitry that is present on many contemporary UE devices. For instance, UE devices that are members of a group 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. Similarly, members can broadcast a message to inform that they are leaving the group.

[0020] In the application layer approach, resources cannot be allocated and accessed on a group basis, i.e., the resource pools used by the UE device for device-to-device communication are independent of the group to which the UE devices belong. Thus, it is not possible to leverage the network infrastructure to help group formation and

management at the application layer. Finally, the overhead of setting up groups at the application layer increases latency, which might be an issue for "mission critical" communications.

[0021] The present disclosure will now be described with reference to the attached drawing figures, wherein like reference numerals are used to refer to like elements throughout, and wherein the illustrated structures and devices are not necessarily drawn to scale. As utilized herein, terms "component," "system," "interface," "circuitry", and the like are intended to refer to a computer-related entity, hardware, software (e.g., in execution), and/or firmware. For example, a component can be a processor (e.g., a microprocessor, a controller, or other processing device), a process running on a processor, a controller, an object, an executable, a program, a storage device, a computer, a tablet PC and/or a user equipment (e.g., mobile phone, etc.) with a processing device. By way of illustration, 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." [0022] Further, 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).

[0023] As another example, 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. As yet another example, a component can be an apparatus that provides specific functionality through electronic components 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.

[0024] Use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless specified otherwise, or clear from context, "X employs A or B" is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied under any of the foregoing instances. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms "including", "includes", "having", "has", "with", or variants thereof are used in either the detailed description and the claims, such terms are intended to be inclusive in a manner similar to the term "comprising."

[0025] In the following description, a plurality of details is set forth to provide a more thorough explanation of the embodiments of the present disclosure. However, it will be apparent to one skilled in the art that embodiments of the present disclosure may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form rather than in detail in order to avoid obscuring embodiments of the present disclosure. In addition, features of the different embodiments described hereinafter may be combined with each other, unless specifically noted otherwise.

[0026] FIG. 1 illustrates an example architecture that supports group mode operation in UE devices by providing network assistance in the formation and maintenance of UE device groups. The architecture includes a network 100 that wirelessly communicates with a plurality of UE devices 105. The network 100 includes several eNBs (a and b), group management circuitry 1 10, and a core network. The UE devices 105 include member circuitry 130 that is adapted to interact with the group management circuitry 1 10 to obtain support from the network for setting up group communication.

[0027] The network (e.g., the eNBs or core network) allocates resources on a per group basis using group information about UE devices and groups that is maintained by the group management circuitry 1 10. The network 100 uses the group management circuitry 1 10 to facilitate efficient formation and management of groups throughout the entirety of the covered region. The group management circuitry 1 10 allows for the forming and managing of groups in the link layer (e.g., by the eNBs) which optimizes resource allocation and access methods leading to reduced latency. This link layer based approach addresses the deficiencies in handling group management in the application layer described above. For the purposes of this description, the example network and devices will be described in the context of cooperative driving. However, it is to be understood that the network assisted group management techniques described herein are equally applicable to groups of UE devices that utilize device-to-device communication to cooperate in any way.

[0028] Referring to FIG. 1 A, a UE device 105 is illustrated in more detail. The UE device 105 includes a processor, storage media, and the member circuitry 130, which in one embodiment implements the functionality of ProSe. The member circuitry 130 is configured to control group mode operation of the UE device 105. When the UE device 105 is in group mode, the member circuitry 130 causes the UE device to scan the channels for "beacon" signals by way of ProSe interface circuitry 140. Based on beacons received from other UE devices, the UE device maintains a neighbor list 160 in the storage media. The neighbor list 160 may be stored in a database table or other appropriate form. The neighbor list 160 records an identifier for each UE device from which a beacon was received by the UE device 105. The neighbor list 160 may also record a signal quality that characterizes the quality of the channel between the UE device 105 and the neighbor UE device. Other information that is helpful in selecting suitable UE devices for group participation may be stored in the neighbor list 160, such as the neighbor UE device's speed or trajectory. The neighbor list 160 also records an identifier for a group to which the neighbor UE device belongs.

[0029] As used herein, the term "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. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware.

[0030] The processor may be configured to cooperate with the storage media and/or the member circuitry 130 to provide higher-layer operations that include generating and processing signals transmitted and received by the UE device. The processor may be configured to provide a geographical identifier in the various messages transmitted by the UE device 105 as described herein. The processor may include one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and dedicated processors including, for example, digital signal processors (DSPs), central processing units (CPUs), microprocessors, memory controllers (integrated or discrete), etc.

[0031] The storage media may be used to load and store data or instructions

(collectively "logic") for operations performed by the processors. The storage media may include any combination of suitable volatile memory and non-volatile memory. The storage media 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. The storage media may be shared among the various processors or dedicated to particular processors. In some embodiments, one or more of the processors may be combined with one or more storage media and, possibly other circuitry in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.

[0032] The UE device 105 is capable of communicating with the core network through an eNB using cellular interface circuitry 150. The cellular interface circuitry 150 may be a new fifth generation (5G) interface or it may be an enhancement of existing LTE Uu- interface. The UE device 105 is also able to communicate with other UE devices in device- to-device mode (also called Peer-to-Peer (P2P) mode) over the ProSe interface circuitry 140. Note that the ProSe interface circuitry 140 may 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.

[0033] The interface circuitry 140 and 150 may be configured to communicate with other network entities over various interfaces using appropriate networking communication protocols. For example, device-to-device communication by way of the ProSe interface circuitry 140 may be performed in a designated frequency band, such as 5-6 GHz and in accordance with a selected communication protocol suited for such communication. The cellular interface circuitry 150 may be configured to communicate in a different frequency band using a different communication protocol. Either of the interface circuitry 140 or 150 may be capable of communicating over any number of wired or wireless communication interfaces. In some embodiments, the interface circuitry 140 or 150 may communicate over Ethernet or other computer networking technologies using a variety of physical media interfaces such as, but not limited to, coaxial, twisted-pair compare, and fiber-optics media interfaces.

[0034] Returning to FIG. 1 , several groups (1 -n) of UE devices 105 are shown. While only two or three UE devices are shown in each group in FIG. 1 , typically several to many UE devices can be members of the same group. Each UE device communicates with an eNB by way of a cellular interface (150 in FIG. 1 A). For the purposes of this description, in some instances communication from an eNB or E-UTRAN to a cellular interface of a UE device will be called "downlink data" for simplicity sake. Each UE device 105

communicates with other UE devices in a group by way of a ProSe interface (140 in FIG.1 A). The member circuitry 130 in each UE device is 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. Thus it can be said that 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 group management circuitry 1 10.

[0035] Examples of group messages include sensor data generated by a UE device's onboard sensors (not shown). The sensor data indicates 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 synchronization effort. Event notifications are also communicated in group messages. Event notifications may notify other group members that the UE device is going to take some action like stopping, steering, and so on. Group messages may 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 are exchanged between group members as prescribed by configuration data received from the group management circuitry 1 10. Further examples of group messages will be discussed with reference to FIGS. 2-6.

[0036] The UE device 105 receives group configuration data from an eNB on the cellular interface circuitry 150 and configures various aspects of operation of the ProSe interface circuitry 140 in order to communicate group messages within a group to which the UE device 105 belongs. For example, the UE device 105 configures the ProSe interface circuitry 140 to utilize a frequency band specified in the configuration data that is assigned to the group. The UE device may also configure the ProSe interface circuitry to use a particular transmission mode (e.g., scheduled or contention-based) specified by the configuration data that is used by all of the group members. The transmission mode defines the protocol that the UE device should use I 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).

[0037] Recall that application layer approaches to group management do not support the allocation of resources to a group of UE devices. In contrast, the group management circuitry 1 10 causes the network 100 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, that will 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 100. 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 100, 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.

[0038] The group management circuitry 1 10 controls allocation of resources amongst various groups of UE devices. The group management circuitry 1 10 is illustrated as shared between an eNB and the core network because some of the functions of the group management circuitry 1 10 may be distributed out to individual eNBs depending on the individual eNB capabilities or desired level of core network control over group

management. For example, in one embodiment, the eNB may allocate radio resources using information from the core network and also group information maintained by the group management circuitry 1 10. In another embodiment, the core network may determine the radio resource allocation for the group.

[0039] In general, the group management circuitry 1 10 generates instructions that, when executed by the core network, cause the collection and storage of "group

information" 1 15. Group information is information about groups of UE devices. The group management circuitry 1 10 generates instructions that, when executed the eNB RF circuitry, causes the eNB RF circuitry to i) communicate with the core 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 cellular interface circuitry 150 of the UE devices in a group.

[0040] FIG. 1 B illustrates one example of group information 1 15 that is stored by the group management circuitry 1 10. For each group identifier, the eNB in whose cell the group is operating is recorded. In one embodiment, additional location or context information is stored in the group information to enable the group to be located within the eNB's coverage (e.g., specific coordinates or map information). An identifier for each UE device that is currently a member of the group is also recorded in the group information. The specific resources that are allocated to each group (e.g., resource block groups (RGBs)) may be recorded as well as a transmission mode to be used by the UE devices in the group. In one embodiment, the specific resources for a group and the transmission mode of the group is stored as group information by each eNB as opposed to being stored by the core network. When a UE device joins the group, only the membership information need be modified by the group management circuitry 1 10. The resources already allocated to the group are communicated to the UE device in the configuration data transmitted to the new UE device. No new allocation of resources is necessary, streamlining the process of UE devices joining and leaving groups.

[0041] Network assistance in group management is helpful for many reasons. For example, as a group exits the coverage of one eNB, the core network may control a second eNB to allocate the same (or different) resources to the group, making transfer between cells seamless from the point of view of the UE devices. The core network often has access to knowledge that is helpful in creating groups and allocating resources. The core network collects information regarding the location, speed, and trajectory of all UE devices covered by the network. This information can be used to help UE devices locate other UE devices that might participate in a group. The core network has access to information about other groups of UE devices that are in close proximity to a new group that is being created. This allows the network 100 to select resources for the new group so that group messages within the group will be less likely to interfere with other groups' messages. The core network may monitor the groups' usage of their respective allocated resources and re-allocate the resources amongst the groups to better use the resources. Emergency or safety vehicles may be made members of all groups and thus be able to transmit messages to all UE groups efficiently.

Use Cases

[0042] FIGS. 2-6 illustrate flows of messages associated with various use cases in which the core network assists in the creation and maintenance of groups of UE devices. In these figures, the group management circuitry is shown as part of the eNB and the core network (taken together, the network 100 of FIG. 1 ). The group management circuitry generates instructions that cause the eNB to receive, process, generate, and transmit group management related messages to and from the UE devices. In one embodiment, the group management circuitry is an independent function that provides information to the eNB that is used by the eNB to allocate resources to a group. The group management circuitry also interacts with the eNB to allocate resources to groups and the core network to cause group information to be stored and maintained.

[0043] When a message is described as being sent to a "group" from a UE device in the group, it is to be understood that the message is sent and received by way of the ProSe interface circuitry in the UE devices in the group. The message may be sent to all UE devices in the group or to the UE device that has been assigned as group leader, which may then communicate relevant information from the message to other UE devices in the group. When a message is described as being sent from the core network to a UE device, it is to be understood that the eNB transmits the message on behalf of the core network to the cellular interface of the UE device. When a message is described as being sent from the UE device to the core network, it is to be understood that the UE device transmits the message from its cellular interface to the eNB which receives the message on behalf of the core network and communicates the message to the core network.

[0044] FIG. 2 illustrates a use case in which vehicles (e.g., UE devices) driving on a highway start operating in a group mode and request the core network to enable group communication services. In the first message flow, the UE device A transmits a message by way of its cellular interface and informs the network about its capability to operate in a group communication mode during initial registration. At 2, the UE device enters group mode and enables discovery. Recall that when the group capability is present, the UE device maintains a neighbor list that records group identifiers (IDs) for neighbor UE devices which have been discovered through its ProSe interface. In one embodiment, the UE device uses its ProSe interface to periodically scan certain channels/resources, which may be pre-configured by the network, for messages from other groups and UE devices. The neighbor list may be ordered according to the received signal quality as well as group awareness information, such as speed and direction of movement (this type of information is available in the Basic Safety Messages exchanged by vehicles).

[0045] At 3, the UE device sends a message by way of its cellular interface to the eNB to request the core network to activate the group communication mode. For instance, this may happen when the group mode is activated by the driver or autonomously (e.g. by an Autonomous Driving Assistant System (ADAS)). At 4, the eNB requests that the core network search for existing groups in the area that may be possible candidates for the UE device to join. The core network may search a database of active groups for candidate groups that meet a group criteria that evaluates the UE device's context information, which may include a combination of current location, direction of movement and map information. For instance, the core network may access the stored group information to select candidate groups that are traveling in the same roadway, direction and within a certain range of the UE. In one embodiment a new interface may be defined between the eNB and the group management circuitry. In another embodiment, the group management circuitry may be implemented as an extension of the ProSe Function.

[0046] If one or more candidate groups are found, the core network sends a list of candidate groups to the UE and the UE starts a group joining procedure, which is described in FIG. 3. If no existing group matches the candidate criteria for the requesting UE, at 5 the group management circuitry causes the core network to generate group information for a new group, which may include a new group ID, and provide the group information to the eNB. The eNB, in response to receiving a new group ID determines a transmission mode and a group resource pool for the group, and generates the group configuration data that is transmitted to the UE device. In one embodiment the core network, rather than the eNB, determines the transmission mode and group resource pool.

[0047] The UE device may also be configured to operate as a group leader, where a group leader is responsible for performing certain group maintenance procedures on behalf of the whole group. When the group mode is active, the UE starts to actively participate in group discovery by transmitting periodic beacons (e.g. beacons may include information in Basic Safety Messages or other broadcast messages that can identify the UE device and its group ID). This will enable other UE devices/groups to discover the UE device. The UE device in group mode active also monitors beacons from other UE devices/groups. The beacon transmission of UE devices in a group may be coordinated by the group leader in order to make beacon transmission contention free. At 6, the eNB communicates the configuration data generated by the core network to the UE device and, at 7, the UE device A starts trying to find other UE devices for the new group once it receives the configuration information from the network.

[0048] FIG. 3 illustrates a use case in which two vehicles (e.g., UE devices) are driving in group mode and a third vehicle (also enabled to operate in group mode) approaches the first two vehicles in the same direction on a highway. As the third vehicle approaches the group, it decides to join the group. At 1 , the three UE devices transmit a message to the eNB to inform the core network about their capability to operate in a group communication mode during initial registration. The UE devices may request the core network to activate the group communication mode. For instance, this may happen when the group mode is activated by the driver or autonomously (e.g. by an Autonomous Driving Assistant System - ADAS).

[0049] At 2, the UE device A enables group discovery and at 3, the UE device A receives UE device B's beacon. When the group mode is active, the UE device maintains a neighbor list that records group IDs for discovered UE devices, which have been discovered through its ProSe interface (e.g. the UE device uses its ProSe interface to periodically scan certain channels/resources, which may be pre-configured by the network, for beacons or messages from other groups). The neighbor list may be ordered according to the received signal quality as well as group awareness information, such as speed and direction of movement (this type of information is available in the Basic Safety Messages exchanged by vehicles). At 3.1 , UE device A updates its neighbor list to include UE device B, which is leader of Group 1 .

[0050] In one embodiment, UE devices may also perform measurements and maintain statistics to characterize the quality of service (QoS) of communications within the group. For instance, if contention based channel access is used for group communication, UE devices may maintain statistics to measure the congestion within the group, such as channel busy time and average number of retransmissions per packet. Such statistics may also be communicated to the core network (through the cellular interface) and used as a criteria to select a group.

[0051] At 4, UE device A transmits a message to the eNB to request activation of group mode. In response, the eNB requests a candidate list of groups at 5. At 6, the core network confirms that the UE device A may operate in group mode and provides initial configuration information, which may include a priority list of candidate groups and their configuration data (e.g. groupID, transmission mode, resource pool). At 7, the eNB transmits the list of candidate groups to the UE device A.

[0052] At 8, the UE device A uses the candidate group list as input to a group selection procedure where the UE device scans the candidate list starting from the highest priority for a group ID that matches a group ID in its neighbor list. If a match is found, the UE will try to join the group. If no match is found, the UE starts a discovery process using configuration information about each candidate group received from the network (i.e. adjust its ProSe interface to the resources where the group is operating). Once one candidate group (e.g., Group 1 ) is discovered at 8, the UE A tries to join the group. If no candidate group is discovered, the UE device may report a group joining failure to the network and request updated configuration information.

[0053] At 9 the UE sends a group joining request to eNB which communicates the request to the core network. At 10, the UE device A may also send a request in the ProSe interface to UE device B, which is Group 1 's leader, in case specific resources are allocated for joining UEs (this information may be part of the group configuration received from the network). At 1 1 , the eNB sends a response to UE device A including updated configuration information, which may also include allocation of resources within the group's resources. At 1 1 .1 the eNB communicates the core network's confirmation that the UE has joined the group. At 12, the UE device A starts operation within the group.

[0054] In an alternative embodiment, the core network may inform the UE device about the possibility to join a nearby group. This may be done by proactively tracking the location of the UE device and comparing it with the location and/or context information (e.g., stored as group information) of active groups in the same area. Once informed by the core network, the UE device may provide the option to join a group to the driver (or to an ADAS control module). If group mode operation is confirmed, the UE device sends the group activation message (step 4 in Figure 3) to the eNB/core network and continues the joining process.

[0055] FIG. 4 illustrates a use case in which three vehicles (e.g., UE devices A. B, and C (not shown)) are driving in group mode on a highway and one of the vehicles decides to take an exit and leave the group. At 1 , UE device A decides to leave Group 1 based on information from its higher layers. A UE device may decide to leave the group for different reasons, like when group mode may is deactivated by the driver or ADAS module. At 2, UE device A sends a group leaving request to the eNB which communicates the request to the core network. If the group leaving request indicates that UE device A is deactivating the group communication mode, the core network sends a confirmation to the UE device A. The UE device A may also stop updating its neighbor list or reduce the frequency in which the scanning for other groups/UE devices is performed.

[0056] If, on the other hand, UE device A has decided to take a different route from Group 1 , as it leaves the group, its group operation mode stays active and the UE device A starts looking for a new group. In this case, at 2 the UE sends a group leaving request to the network indicating it is still operating in group mode. Optionally, at 2.1 , the UE device A may send a group leaving notice to the group. At 3 the eNB (as controlled by the group management circuitry) requests a list of candidate groups for UE device A because UE device A's group mode is still activated. At 4, the core network may respond with updated candidate group information as in FIG 3 step 6 which is communicated to UE device A by the eNB at 5. At 6 UE device A decides whether to join another group (see FIG. 3) or form a new group (see FIG. 2) depending on the candidate list (or lack thereof) from the core network. If the UE device leaving the group is configured to operate as a group leader, at 7 the core network assigns another UE device to become the new group leader. The core network may maintain a backup list of UE devices that can be configured to operate as group leaders.

[0057] In case group communications is supporting important applications, such as cooperative driving, the communication within the group is expected to be always available, including in areas with no or weak cellular system coverage, such as remote/rural areas, underground tunnels, garages, etc. In order to meet such high availability requirement, example embodiments provide modified group management procedures where the coordination to join/leave a group can be done between UE devices, where one of the UE devices take the role of a group leader. The group leader is a UE device that is authorized by the network to coordinate group management procedures with other UE devices on behalf of the network.

[0058] FIG. 5 illustrates a use case in which UE device A joins a group through direct coordination with a group leader (e.g., UE device B leader of Group 1 ) over the ProSe interface and without intervention by the eNB or core network. Note that UE device A may still provide its group capability to the core network for initial registration and

security/authentication purposes at 1 . UE device A enables group discovery at 2, updates its neighbor list at 3, and decides to join Group 1 at 4 as described above. However in the autonomous process depicted in FIG. 5, the actual group joining procedure does not require communication with the network (e.g., the eNB or core network). At 5, the UE device A sends a joining request to the group leader of Group 1 . At 6, the group leader confirms UE device A's request and transmits configuration data for Group 1 to UE device A. At 7 UE device A starts operation in Group 1 . At 8, the group leader, as one of its leadership responsibilities, sends a message to the eNB to modify the group information maintained by the group management circuitry. This message may be sent immediately after the new member has joined (if the group is operating within coverage), or whenever the connection between the group leader and the network becomes available. Note that this autonomous joining procedure may also be used within network coverage to help reduce signaling overhead for group management between UEs and the network.

[0059] Figure 6 shows an autonomous group leaving procedure. At 1 UE device A decides to leave Group 1 . At 2, UE device A sends a group leaving request to the group leader UE device B. At 3, UE device B sends a list of candidate groups to UE device A so that UE device A may join another group. The list of candidate groups may have been provided to UE device B when UE device B was assigned as group leader by the core network. The list of candidate groups may be generated by UE device B based on UE device B's neighbor list. The candidate list may also include configuration data for each candidate group so that UE device A may communicate with a selected group without having to contact the eNB a. At 6, UE device A tries to join an existing group as in FIG. 3 or form a new group as in FIG. 2. At 8, as in the autonomous joining case, the group leader UE device B transmits a message to the eNB (whenever connection is available or according to some update schedule) about the updated group information. At 9, the eNB communicates to the core network the fact that UE device A has left Group 1 , and in response the core network will update the group information for Group 1 . Note that this autonomous leaving procedure may also be used within network coverage to help reduce signaling overhead for group management between UEs and the network.

[0060] If the leaving UE device is the acting group leader and the group is operating out of coverage, the group leader selects another UE device to act as group leader from a list of core network authorized backup UE devices. The group leader sends a request to the selected backup UE device to take the group leader role before leaving the group. In this case, the new group leader broadcasts its group update information to its group members announcing that it has taken over the group leader role. The new group leader also sends an update to the core network once coverage is restored. Note that this autonomous group leader transfer procedure may also be used within network coverage to help reduce signaling overhead for group management between UEs and the network.

[0061] In certain scenarios, a UE device may maintain communication with multiple groups in order to avoid interruption of important applications. For instance, while turning on an intersection, a UE device may transition from one group to another. In this case, the UE device may start searching and joining another group before leaving its current group. The UE device may send a request to the network to get an updated candidate group list and once it selects a new group, the UE device may send a request to join the selected group. Once the membership into the new group is confirmed, then the UE device may leave its previous group.

[0062] A group of UE devices may want to be able to use group communication because of the benefits provided by cooperative applications (e.g., truck drivers that belong to the same fleet can save fuel by driving in a platoon mode). The group association is configured as part of the UE device subscription. Any given UE device can belong to one or more groups, but at any given time one group is enabled for communication. In one embodiment, a UE device with multiple radios may belong to multiple groups at the same time. The association between the UE device and the group can be done at the time the user signs up for service, or the group association can be added later.

[0063] One example embodiment of this group mode subscription use case can be summarized as follows. During initial registration, the core network becomes aware that the UE device belongs to one or more specific group(s) that are part of a subscription service. At any given specific time, a UE device that subscribes to the service requests the core network to activate group communication mode for a given group ID. For instance, this may happen when the Platoon mode is activated by the driver or autonomously (e.g. by an Autonomous Driving Assistant System - ADAS), then the group ID for the truck driver platoon is used in the request. From that point on the core network knows that there is at least one UE device interested in the group communication mode for a given specific group ID. As the core network is aware of all UE devices that are registered and associated with that group ID, the core network keeps track of the location of the UEs associated with that group. Based on group criteria for location and/or other context information, if two or more UEs that are nearby (e.g. in the same roadway) meet the criteria and are interested in group communication for the same group ID, the core network notifies all interested UE devices of the group presence. The UE devices start operation in the new group once they receive the configuration information from the network. If no existing group matches the group criteria for the requesting UE device, the core network notifies the UE device that no group is found after a certain period of time.

[0064] FIG. 7 illustrates an example of a method 700 that may be performed by a UE device acting in group mode according to one embodiment of the disclosure. The method may be executed by the UE device when the UE device executes instructions stored on a computer-readable storage device. At 710, the UE device processes configuration data for a group of UE devices. The configuration data is downlink data received by cellular interface circuitry in the UE device. At 720, the UE device configures ProSe interface circuitry of the UE device based at least on the group configuration data to enable device- to-device communication with the other UE devices in the group.

[0065] In one embodiment the group configuration data includes a portion of a device- to-device resource pool that is allocated to the group or a transmission mode in use by the group. [0066] In one embodiment, the method 700 includes generating messages that communicate sensor data that describes motion of the UE and transmitting the messages, with the ProSe interface circuitry, to the other UE devices in the group.

[0067] FIG. 8 illustrates an example of a method 800 that may be performed by group management circuitry according to one embodiment of the disclosure. The method may be executed by a processor executing instructions stored on a computer-readable storage device. At 810, the method includes storing group information for a group of UE devices. At 820, the method includes causing radio frequency (RF) circuitry of an eNB to, based at least on the group information, generate group configuration data for UE devices in the group to perform device-to-device communication with other UE devices in the group with ProSe interfaces of the respective UE devices. At 830 eNB RF circuitry is caused to transmit the group configuration data to cellular interface circuitry of at least one UE device in the group. At 840, in response to receiving a subsequent request from a requesting UE device for group configuration data for the group, the stored group configuration data is transmitted to the requesting UE device.

[0068] In one embodiment the method includes causing the core network to: record group information for a plurality of groups, where the group information for a group includes i) a group identifier for the group and ii) identifiers for UE devices that belong to the group. In response to receiving a request to operate in group mode from the requesting UE, the method includes causing the core network to evaluate a group criteria with respect to the plurality of groups, where the group criteria is based at least on context information for the requesting UE and identify, from the plurality of groups, one or more candidate groups that meet the group criteria. The eNB RF circuitry is caused to transmit a list of the candidate groups to the UE. The method includes receiving, from the UE device, a joining request for a selected group; and causing the core network to modify the group information for the selected group to include an identifier for the UE device.

[0069] In one embodiment the method includes, when no group in the plurality of groups meet the group criteria: causing the core network to generate new group information for a new group that includes an identifier for the requesting UE and record the new group information; and causing the eNB RF circuitry to generate new group configuration data for the new group based at least on the new group information and transmit the new group configuration data to the requesting UE. [0070] In one embodiment of the method the context information includes a location of the UE device.

[0071] In one embodiment of the method, the core network is caused to receive, from the requesting UE device, a group identifier that identifies a group to be joined; and in response, identify a second UE device that is not a member of the group based at least on context information for the requesting UE, wherein the group identifier was previously received from the second UE device. The eNB RF circuitry is caused to transmit group configuration data for the group to the requesting UE device and the second UE device.

[0072] FIG. 9 illustrates an example architecture that supports group mode operation in UE devices by providing network assistance in the formation and maintenance of UE device groups. The architecture of FIG. 9 is adapted for use with ProSe function in both the UE device and the network. The architecture includes a network 900 that wirelessly communicates with a plurality of UE devices 105. The network 900 includes E-UTRAN equipment, ProSe function circuitry 910, and an evolved packet core (EPC) network. The ProSe function circuitry 910 functions in a manner similar to the group management circuitry 1 10 of FIG. 1 , and is an extension of the ProSe function. The UE devices 105 include UE ProSe circuitry 930 that functions in manner similar to that described with respect to the member circuitry 130 of Figure 1 . UE ProSe circuitry 930 is adapted to interact with the ProSe function circuitry 910 to obtain support from the network for setting up group communication. Each UE device includes PC5 interface circuitry (not shown) that functions in a manner similar to ProSe interface 140 of FIG. 1 A following the PC5 protocol.

[0073] The network (e.g., E-UTRAN or EPC network) allocates resources on a per group basis using group information about UE devices and groups that is maintained by the ProSe function circuitry 910. The network 900 uses the ProSe Function circuitry 910 to facilitate efficient formation and management of groups throughout the entirety of the covered region. The ProSe function circuitry 910 allows 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 addresses the deficiencies in handling group management in the application layer described above. For the purposes of this description, the example network and devices will be described in the context of cooperative driving. However, it is to be understood that the network assisted group management techniques described herein are equally applicable to groups of UE devices that utilize device-to-device communication to cooperate in any way.

[0074] Several groups (1 -n) of UE devices 905 are shown. While only two or three UE devices are shown in each group in FIG. 9, typically several to many UE devices can be members of the same group. Each UE device communicates 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 930 in each UE device is 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. Thus it can be said that 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 915 maintained by the ProSe function circuitry 910.

[0075] Examples of group messages include sensor data generated by a UE device's onboard sensors (not shown). The sensor data indicates 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 synchronization effort. Event notifications are also communicated in group messages. Event notifications may notify other group members that the UE device is going to take some action like stopping, steering, and so on. Group messages may 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 are exchanged between group members as prescribed by configuration data received from the ProSe function circuitry 910. Further examples of group messages were discussed with reference to FIGS. 2-6. [0076] The UE device 905 receives group configuration data from the E-UTRAN on the LTE-Uu interface circuitry 150 and configures various aspects of operation of the PC5 interface circuitry 140 in order to communicate group messages within a group to which the UE device 905 belongs. For example, the UE device 905 configures the PC5 interface circuitry 140 to utilize a frequency band specified in the configuration data that is assigned to the group. The UE device may 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 all of 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).

[0077] Recall that application layer approaches to group management do not support the allocation of resources to a group of UE devices. In contrast, the ProSe function circuitry 910 causes the network 900 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, that will 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 900. 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 900, 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.

[0078] The ProSe function circuitry 910 controls allocation of resources amongst various groups of UE devices. The ProSe function circuitry 910 is illustrated as shared between the E-UTRAN and the core network because some of the functions of the ProSe function circuitry 910 may be distributed out to individual eNBs depending on the individual eNB capabilities or desired level of core network control over group management. For example, in one embodiment, the eNB may allocate radio resources using information from the core network and also group information maintained by the ProSe function circuitry 910. In another embodiment, the core network may determine the radio resource allocation for the group. [0079] In general, the ProSe function circuitry 910 generates instructions that, when executed by the core network, cause the collection and storage of the group information 915. Group information is information about groups of UE devices. The ProSe function circuitry 910 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.

Example Device

[0080] Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software. FIG. 10 illustrates, for one embodiment, example components of a device 1000. The device 1000 may be utilized as a User Equipment (UE) device or an evolved node B (eNB) device or E-UTRAN equipment. In some embodiments, the device 1000 may include application circuitry 1002, baseband circuitry 1004, Radio Frequency (RF) circuitry 1006, front-end module (FEM) circuitry 1008 and one or more antennas 1010, coupled together at least as shown.

[0081] The application circuitry 1002 may include one or more application processors. For example, the application circuitry 1002 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.

[0082] The baseband circuitry 1004 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1004 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 1006 and to generate baseband signals for a transmit signal path of the RF circuitry 1006. Baseband processing circuity 1004 may interface with the application circuitry 1002 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1006. For example, in some embodiments, the baseband circuitry 1004 may include a second generation (2G) baseband processor 1004a, third generation (3G) baseband processor 1004b, fourth generation (4G) baseband processor 1004c, and/or other baseband processor(s) 1004d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.).

[0083] The baseband circuitry 1004 (e.g., one or more of baseband processors 1004a- d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 1006. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 1004 may include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 1004 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[0084] In some embodiments, the baseband circuitry 1004 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) 1004e of the baseband circuitry 1004 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 1004f. The audio DSP(s) 1004f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other

embodiments. 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. In some embodiments, some or all of the constituent components of the baseband circuitry 1004 and the application circuitry 1002 may be implemented together such as, for example, on a system on a chip (SOC). [0085] In some embodiments, the baseband circuitry 1004 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 1004 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). Embodiments in which the baseband circuitry 1004 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0086] RF circuitry 1006 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 1006 may include switches, filters, amplifiers, etc. to facilitate the

communication with the wireless network. RF circuitry 1006 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1008 and provide baseband signals to the baseband circuitry 1004. RF circuitry 1006 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1004 and provide RF output signals to the FEM circuitry 1008 for transmission.

[0087] In some embodiments, the RF circuitry 1006 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 1006 may include mixer circuitry 1006a, amplifier circuitry 1006b and filter circuitry 1006c. The transmit signal path of the RF circuitry 1006 may include filter circuitry 1006c and mixer circuitry 1006a. RF circuitry 1006 may also include synthesizer circuitry 1006d for synthesizing a frequency for use by the mixer circuitry 1006a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 1006a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1008 based on the synthesized frequency provided by synthesizer circuitry 1006d. The amplifier circuitry 1006b may be configured to amplify the down-converted signals and the filter circuitry 1006c 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 1004 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 1006a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0088] In some embodiments, the mixer circuitry 1006a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1006d to generate RF output signals for the FEM circuitry 1008. The baseband signals may be provided by the baseband circuitry 1004 and may be filtered by filter circuitry 1006c. The filter circuitry 1006c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

[0089] In some embodiments, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively. In some embodiments, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a of the transmit signal path may be configured for super-heterodyne operation.

[0090] In some embodiments, 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. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate

embodiments, the RF circuitry 1006 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1004 may include a digital baseband interface to communicate with the RF circuitry 1006.

[0091] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0092] In some embodiments, the synthesizer circuitry 1006d 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. For example, synthesizer circuitry 1006d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0093] The synthesizer circuitry 1006d may be configured to synthesize an output frequency for use by the mixer circuitry 1006a of the RF circuitry 1006 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1006d may be a fractional N/N+1 synthesizer.

[0094] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 1004 or the applications processor 1002 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 1002.

[0095] Synthesizer circuitry 1006d of the RF circuitry 1006 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, 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. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, 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. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0096] In some embodiments, synthesizer circuitry 1006d 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. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 1006 may include an IQ/polar converter. [0097] FEM circuitry 1008 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1010, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1006 for further processing. FEM circuitry 1008 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1006 for transmission by one or more of the one or more antennas 1010. When used in a UE device, FEM circuitry 1008 may 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). When used in a UE device, FEM circuitry 1008 may also include a transmit and receive path for cellular communications received from the eNB or E-UTRAN (e.g. cellular interface circuitry).

[0098] In some embodiments, the FEM circuitry 1008 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). The transmit signal path of the FEM circuitry 1008 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1006), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1010.

[0099] In some embodiments, the device 1000 may include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.

[00100] While the systems, circuitry and methods have been illustrated and described with respect to one or more implementations, alterations and/or modifications may be made to the illustrated examples without departing from the spirit and scope of the appended claims. In particular regard to the various functions performed by the above described components or structures (assemblies, devices, circuits, systems, etc.), the terms (including a reference to a "means") used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations of the disclosure.

[00101] 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.

EXAMPLES

[00102] The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the example embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various implementations of the example embodiments.

[00103] Example 1 is a device for use in a user equipment (UE) device, comprising member circuitry configured to: process configuration data for a group of UE devices, wherein the configuration data is downlink data received by cellular interface circuitry in the UE device; and configure ProSe interface circuitry in the UE device based at least on the group configuration data to enable device-to-device communication with other UE devices in the group, wherein device-to-device communication occurs between UE devices without intervention by the eNB.

[00104] Example 2 includes the subject matter of example 1 , including or omitting optional elements, wherein the group configuration data comprises a portion of a device-to- device resource pool that is allocated to the group and a transmission mode for the group.

[00105] Example 3 includes the subject matter of examples 1 and 2, including or omitting optional elements, wherein the member circuitry is configured to generate messages that communicate sensor data that describes motion of the UE and transmit the messages, with the ProSe interface circuitry, to the other UE devices in the group.

[00106] Example 4 includes the subject matter of examples 1 and 2, including or omitting optional elements, wherein the member circuitry is configured to: discover another UE device that belongs to a group; record an identifier for the group in a neighbor list; generate a joining message for transmission to an eNB, wherein the joining message communicates that the UE device is seeking a group to join; process a downlink data comprising a list of identifiers for candidate groups and group configuration data for respective candidate groups; select a candidate group from the candidate list having an identifier that matches the identifier in the neighbor list; and configure the ProSe interface circuitry based at least on the group configuration data for the selected group to enable device-to-device communication with the other UE devices in the selected group.

[00107] Example 5 includes the subject matter of examples 1 and 2, including or omitting optional elements, wherein, when the UE is a member of a group, the member circuitry is configured to, in response to receiving a message that assigns the UE device as a group leader, perform group maintenance tasks on behalf of other UE devices in the group.

[00108] Example 6 includes the subject matter of examples 1 and 2, including or omitting optional elements, wherein the member circuitry is configured to, when the UE device is a group leader: process a joining request from a new UE device not in the group; and generate, for transmission with the ProSe interface circuitry, group configuration data for the group to the new UE; and generate, for transmission with the cellular interface circuitry, group update information that includes the new UE device as a member of the group.

[00109] Example 7 includes the subject matter of examples 1 and 2, including or omitting optional elements, wherein the ProSe interface circuitry comprises a PC5 interface.

[00110] Example 8 includes the subject matter of examples 1 and 2, including or omitting optional elements, wherein the device-to-device communication occurs on a sidelink channel.

[00111] Example 9 includes the subject matter of examples 1 and 2, including or omitting optional elements, wherein the cellular interface circuitry comprises an LTE-Uu interface.

[00112] Example 10 is a computer-readable storage device storing computer-executable instructions that, in response to execution, cause a UE device to: process configuration data for a group of UE devices, wherein the configuration data is downlink data received by cellular interface circuitry in the UE device; and configure ProSe interface circuitry of the UE device based at least on the group configuration data to enable device-to-device communication with the other UE devices in the group, wherein device-to-device

communication occurs between UE devices without intervention by the eNB. [00113] Example 1 1 includes the subject matter of example 10, including or omitting optional elements, wherein the group configuration data comprises a portion of a device-to- device resource pool that is allocated to the group and a transmission mode for the group.

[00114] Example 12 includes the subject matter of examples 10 and 1 1 , including or omitting optional elements, further comprising instructions that, in response to execution, cause the UE device to generate messages that communicate sensor data that describes motion of the UE and transmit the messages, with the ProSe interface circuitry, to the other UE devices in the group.

[00115] Example 13 includes the subject matter of examples 10 and 1 1 , including or omitting optional elements, further comprising instructions that, in response to execution, cause the UE device to: discover another UE device that belongs to a group; record an identifier for the group in a neighbor list; generate a joining message for transmission to the eNB, wherein the joining message communicates that the UE device is seeking a group to join; process downlink data comprising a list of candidate groups and group configuration data for respective candidate groups; select a candidate group having an identifier that matches the identifier in the neighbor list; and configure the ProSe interface circuitry based at least on the group configuration data for the selected group to enable device-to-device communication with the other UE devices in the selected group.

[00116] Example 14 includes the subject matter of examples 10 and 1 1 , including or omitting optional elements, further comprising instructions that, in response to execution, cause the UE device to, when the UE is a member of a group, perform group maintenance tasks on behalf of other UE devices in the group in response to receiving a message that assigns the UE device as a group leader.

[00117] Example 15 includes the subject matter of examples 10 and 1 1 , including or omitting optional elements, further comprising instructions that, in response to execution, cause the UE device to, when the UE device is a group leader: process a joining request from a new UE device not in the group; generate, for transmission with the ProSe interface circuitry, the group configuration data for the group to the new UE; and generate, for transmission to the eNB with the cellular interface, group update information that includes the new UE device as a member of the group.

[00118] Example 16 is a device for use in an eNB, comprising: group management circuitry configured to: generate instructions that , when executed by eNB radio frequency (RF) circuitry of the eNB, cause the eNB RF circuitry to: based at least on stored group information, generate group configuration data for UE devices in the group to perform device-to-device communication with other UE devices in the group with ProSe interfaces of the respective UE devices; transmit the group configuration data to cellular interface circuitry of at least one UE device in the group; and in response to receiving a subsequent request from a requesting UE device for group configuration data for the group, transmit the stored group configuration data to the requesting UE device.

[00119] Example 17 includes the subject matter of example 16, including or omitting optional elements, wherein the group configuration data comprises a portion of a device-to- device resource pool that is allocated to the group and a transmission mode for the group.

[00120] Example 18 includes the subject matter of examples 16 and 17, including or omitting optional elements, wherein the group management circuitry is configured to:

generate instructions that, when executed by a core network, cause the core network to: record group information for a plurality of groups, where the group information for a group includes i) a group identifier for the group and ii) identifiers for UE devices that belong to the group; in response to receiving a request to operate in group mode from the requesting UE: evaluate a group criteria with respect to the plurality of groups, where the group criteria is based at least on context information for the requesting UE, identify, from the plurality of groups, one or more candidate groups that meet the group criteria; generate instructions that, when executed by eNB RF circuitry, cause the eNB RF circuitry to transmit a list of the candidate groups to the UE; receive, from the UE device, a joining request for a selected group; and generate instructions that, when executed by the core network, cause the core network to modify the group information for the selected group to include an identifier for the UE device.

[00121 ] Example 19 includes the subject matter of examples 16 and 17, including or omitting optional elements, wherein the group management circuitry is configured to, when no group in the plurality of groups meet the group criteria: generate instructions that, when executed by the core network, cause the core network to: generate new group information for a new group that includes an identifier for the requesting UE; and record the new group information for the new group; and generate instructions that, when executed by the eNB RF circuitry, cause the eNB RF circuitry to: generate new group configuration data for the new group based at least on the new group information; and transmit the new group configuration data to the requesting UE.

[00122] Example 20 includes the subject matter of example 19, including or omitting optional elements, wherein the context information includes a location of the UE device.

[00123] Example 21 includes the subject matter of examples 16 and 17, including or omitting optional elements, wherein the group management circuitry is configured to:

receive, from the requesting UE device, a group identifier that identifies a group to be joined; based at least on context information for the requesting UE, generate instructions that, when executed by the core network, cause the core network to identify a second UE device that is not a member of the group, wherein the group identifier was previously received from the second UE device; generate instructions that, when executed by the eNB RF circuitry, cause the eNB RF circuitry to transmit group configuration data for the group to the requesting UE device and the second UE device.

[00124] Example 22 is a computer-readable storage device storing computer-executable instructions that, in response to execution: cause radio frequency (RF) circuitry of an eNB to: based at least on stored group information, generate group configuration data for UE devices in the group to perform device-to-device communication with other UE devices in the group with ProSe interfaces of the respective UE devices; transmit the group configuration data to cellular interface circuitry of at least one UE device in the group; and in response to receiving a subsequent request from a requesting UE device for group configuration data for the group, transmit the stored group configuration data to the requesting UE device.

[00125] Example 23 includes the subject matter of example 22, including or omitting optional elements, wherein the group configuration data comprises a portion of a ProSe resource pool that is allocated to the group and a transmission mode for the group.

[00126] Example 24 includes the subject matter of examples 22 and 23, including or omitting optional elements, further comprising instructions that, in response to execution: cause the core network to: record group information for a plurality of groups, where the group information for a group includes i) group configuration data for the group and ii) identifiers for UE devices that belong to the group; in response to receiving a request to operate in group mode from the requesting UE: evaluate a group criteria with respect to the plurality of groups, where the group criteria is based at least on context information for the requesting UE; identify, from the plurality of groups, one or more candidate groups that meet the group criteria; cause the eNB RF circuitry to: transmit a list of the candidate groups to the UE; receive, from the UE device, a joining request for a selected group; and cause the core network to modify the group information for the selected group to include an identifier for the UE device.

[00127] Example 25 includes the subject matter of example 24, including or omitting optional elements, further comprising instructions that, in response to execution, when no group in the plurality of groups meet the group criteria: cause the core network to: generate new group information for a new group that includes the new group configuration data and an identifier for the requesting UE; and record the new group information; and cause the RF circuitry to: generate new group configuration data based at least on the new group information; and transmit the new group configuration data to the requesting UE.

[00128] Example 26 includes the subject matter of examples 22 and 23, including or omitting optional elements, further comprising instructions that, in response to execution: cause the core network to receive, from the requesting UE device, a group identifier that identifies a group to be joined; and in response, identify a second UE device that is not a member of the group based at least on context information for the requesting UE, wherein the group identifier was previously received from the second UE device; and cause the eNB RF circuitry to transmit group configuration data for the group to the requesting UE device and the second UE device.

[00129] Example 27 is a device for use in an eNB comprising: means for causing radio frequency (RF) circuitry of an eNB to: based at least on stored group information, generate group configuration data for UE devices in the group to perform device-to-device

communication with other UE devices in the group with ProSe interfaces of the respective UE devices; transmit the group configuration data to cellular interface circuitry of at least one UE device in the group; and in response to receiving a subsequent request from a requesting UE device for group configuration data for the group, transmit the stored group configuration data to the requesting UE device.

[00130] Example 28 is a device for use in a UE device comprising: means for receiving, from an eNB, with cellular interface circuitry of the UE device, group configuration data for a group of UE devices; and means for configuring ProSe interface circuitry of the UE device based at least on the group configuration data to enable D2D communication with the other UE devices in the group.

[00131] Example 29 includes the subject matter of examples 10 and 1 1 , including or omitting optional elements, wherein the ProSe interface circuitry comprises a PC5 interface.

[00132] Example 30 includes the subject matter of examples 10 and 1 1 , including or omitting optional elements, wherein the device-to-device communication occurs on a sidelink channel.

[00133] Example 31 includes the subject matter of examples 10 and 1 1 , including or omitting optional elements, wherein the cellular interface circuitry comprises an LTE-Uu interface.

[00134] Example 32 is a method, comprising: processing configuration data for a group of UE devices, wherein the configuration data is downlink data received by cellular interface circuitry in the UE device; and configuring ProSe interface circuitry of the UE device based at least on the group configuration data to enable device-to-device

communication with the other UE devices in the group, wherein device-to-device

communication occurs between UE devices without intervention by the eNB.

[00135] Example 33 includes the subject matter of example 32, including or omitting optional elements, wherein the group configuration data comprises a portion of a device-to- device resource pool that is allocated to the group and a transmission mode for the group.

[00136] Example 34 includes the subject matter of examples 32 and 33, including or omitting optional elements, further comprising generating messages that communicate sensor data that describes motion of the UE and transmit the messages, with the ProSe interface circuitry, to the other UE devices in the group.

[00137] Example 35 includes the subject matter of examples 32 and 33, including or omitting optional elements, further comprising: discovering another UE device that belongs to a group; recording an identifier for the group in a neighbor list; generating a joining message for transmission to the eNB, wherein the joining message communicates that the UE device is seeking a group to join; processing downlink data comprising a list of candidate groups and group configuration data for respective candidate groups; selecting a candidate group having an identifier that matches the identifier in the neighbor list; and configuring the ProSe interface circuitry based at least on the group configuration data for the selected group to enable device-to-device communication with the other UE devices in the selected group.

[00138] Example 36 includes the subject matter of examples 32 and 33, including or omitting optional elements, further comprising, when the UE is a member of a group, performing group maintenance tasks on behalf of other UE devices in the group in response to receiving a message that assigns the UE device as a group leader.

[00139] Example 37 includes the subject matter of examples 32 and 33, including or omitting optional elements, further comprising, when the UE device is a group leader: processing a joining request from a new UE device not in the group; generating, for transmission with the ProSe interface circuitry, the group configuration data for the group to the new UE; and generating, for transmission to the eNB with the cellular interface, group update information that includes the new UE device as a member of the group.

[00140] Example 38 is a method, comprising: generating group configuration data for UE devices in the group to perform device-to-device communication with other UE devices in the group with ProSe interfaces of the respective UE devices; transmitting the group configuration data to cellular interface circuitry of at least one UE device in the group; and in response to receiving a subsequent request from a requesting UE device for group configuration data for the group, transmitting the stored group configuration data to the requesting UE device.

[00141] Example 39 includes the subject matter of example 38, including or omitting optional elements, wherein the group configuration data comprises a portion of a ProSe resource pool that is allocated to the group and a transmission mode for the group.

[00142] Example 40 includes the subject matter of examples 38 and 39, including or omitting optional elements, further comprising: recording group information for a plurality of groups, where the group information for a group includes i) group configuration data for the group and ii) identifiers for UE devices that belong to the group; in response to receiving a request to operate in group mode from the requesting UE: evaluating a group criteria with respect to the plurality of groups, where the group criteria is based at least on context information for the requesting UE; identifying, from the plurality of groups, one or more candidate groups that meet the group criteria; transmitting a list of the candidate groups to the UE; receiving, from the UE device, a joining request for a selected group; and modifying the group information for the selected group to include an identifier for the UE device.

[00143] Example 41 includes the subject matter of example 40, including or omitting optional elements, further comprising, when no group in the plurality of groups meet the group criteria: generating new group information for a new group that includes the new group configuration data and an identifier for the requesting UE; and recording the new group information; generating new group configuration data based at least on the new group information; and transmitting the new group configuration data to the requesting UE.

[00144] Example 42 includes the subject matter of examples 38 and 39, including or omitting optional elements, further comprising: receiving, from the requesting UE device, a group identifier that identifies a group to be joined; and in response, identifying a second UE device that is not a member of the group based at least on context information for the requesting UE, wherein the group identifier was previously received from the second UE device; and transmitting group configuration data for the group to the requesting UE device and the second UE device.