Media communication for wearable devices

Abstract

Methods, systems, and devices for wireless communication are described. For example, the described techniques provide a first wearable device and a second wearable device to initiate a media session with a user equipment (UE) and a terminal device. Wearable devices may each initiate a session flow by sending a session description protocol (SDP) provision message to a terminal device. In some examples, the wearable device may send capability information to the UE, and the UE may send an SDP provision message to the terminal device. The terminal device may start a session by sending one or more SDP acknowledgement messages after receiving the one or more SDP provision messages. The wearable devices may each send information about a user of the wearable device. The terminal device may generate a media content stream, and the UE may propagate the media content stream to the wearable device.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 327,829, filed June 1, 2023, entitled “MEDIA COMMUNICATIONSFOR WEARABLE DEVICES”, which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The following text relates to wireless communications, including media communications for wearable devices. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses that support media communication for wearable devices. For example, the described techniques provide for a first wearable device and a second wearable device to initiate a media session with a user equipment (UE) and a terminal device. In some implementations, the first wearable device and the second wearable device (e.g., a pair of contact lenses) can each initiate a session flow (e.g., a real-time transport protocol (RTP) session) by sending a session description protocol (SDP) offer message to the terminal device. In some examples, the first wearable device and the second wearable device can send capability information to the UE, and the UE can send an SDP offer message to the terminal device. The terminal device can begin the session after receiving the one or more SDP offer messages by sending one or more SDP answer messages. The first wearable device and the second wearable device can each send information about the user (e.g., pose or eye tracking information) to the terminal device (e.g., or to the UE for forwarding to the terminal device). The terminal device can generate a first media content stream and a second media content stream (e.g., rendered video for display by the first wearable device and the second wearable device) for the first wearable device and the second wearable device, respectively, and send the media content to the UE. The UE can unicast each media content stream to the first wearable device and the second wearable device, respectively. In some examples, the UE can multicast the first media content stream to the first wearable device and the second wearable device, and can unicast a differential version (e.g., between the first media content stream and the second media content stream) to one of the first wearable device and the second wearable device.

[0006] A method for wireless communication at a first wearable device is described. The method can include initiating a first session flow via a wireless connection between the first wearable device and a UE, where the first session flow is associated with a second session flow for a second wearable device, sending a set of information associated with a user of the first wearable device via the first session flow, and receiving a first media content stream via the first session flow and a second media content stream via the second session flow in coordination.

[0007] An apparatus for wireless communication at a first wearable device is described. The apparatus can include at least one processor, at least one memory coupled with the at least one processor, and instructions stored in the at least one memory. The instructions can be executable by the at least one processor to cause the apparatus to initiate a first session flow via a wireless connection between the first wearable device and a UE, where the first session flow is associated with a second session flow for a second wearable device, transmit a set of information associated with a user of the first wearable device via the first session flow, and receive a first media content stream via the first session flow and a second media content stream coordinately via the second session flow.

[0008] Another apparatus for wireless communication at a first wearable device is described. The apparatus can include means for initiating a first session flow via a wireless connection between the first wearable device and a UE, where the first session flow is associated with a second session flow for a second wearable device, means for transmitting a set of information associated with a user of the first wearable device via the first session flow, and means for receiving a first media content stream via the first session flow and a second media content stream coordinately via the second session flow.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a first wearable device is described. The code can include instructions executable by at least one processor to initiate a first session flow via a wireless connection between the first wearable device and a UE, where the first session flow is associated with a second session flow for a second wearable device, transmit a set of information associated with a user of the first wearable device via the first session flow, and receive a first media content stream via the first session flow and a second media content stream coordinately via the second session flow.

[0010] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, receiving the first media content stream can include operations, features, means, or instructions for receiving, via the first session flow, a first version of media content via the first media content stream, where the first version includes one of a baseline version or a differential version that can be defined relative to the baseline version.

[0011] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the second media content stream can be associated with a second version of media content, the second version including the other of the baseline version or the differential version.

[0012] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the baseline version can be multicast to the first wearable device and the second wearable device, and the differential version can be unicast to one of the first wearable device or the second wearable device.

[0013] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, receiving the first media content stream can include operations, features, means, or instructions for receiving the baseline version from the UE via a first unicast message, where the second version can be transmitted to the second wearable device via a second unicast message.

[0014] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the first session stream and the second session stream can be associated with a same session between the UE and the end device.

[0015] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the first session stream can be associated with a first session with the end device, and the first session can be different from a second session with the end device that is associated with the second session stream.

[0016] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the method, apparatuses, and non-transitory computer- readable medium can include further operations, features, means, or instructions for transmitting, to the UE, a capability message indicating a capability of the first wearable device to receive the first media content stream, and transmitting, to the end device, an SDP offer message, and receiving, from the end device, an SDP answer message based on the SDP offer message.

[0017] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the set of information associated with the user includes one or more of pose information and eye tracking information.

[0018] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the first wearable device and the second wearable device can be contact lenses.

[0019] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the media content includes rendered video for coordinated display by the first wearable device with the second wearable device.

[0020] A method for wireless communication at a UE is described. The method can include initiating a first session flow for a first wearable device via a wireless connection of the UE with the first wearable device, where the first session flow is associated with a second session flow for a second wearable device, receiving a set of information associated with a user of the first wearable device via the first session flow, receiving a set of information associated with a user of the second wearable device via the second session flow, sending a first media content stream to the first wearable device via the first session flow, and sending a second media content stream to the second wearable device in coordination with the first media content stream via the second session flow.

[0021] An apparatus for wireless communication at a UE is described. The apparatus can include at least one processor, at least one memory coupled with the at least one processor, and instructions stored in the at least one memory. The instructions can be executable by the at least one processor to cause the apparatus to initiate a first session flow for a first wearable device via a wireless connection of the UE with the first wearable device, where the first session flow is associated with a second session flow for a second wearable device, receive a set of information associated with a user of the first wearable device via the first session flow, receive a set of information associated with a user of the second wearable device via the second session flow, send a first media content stream to the first wearable device via the first session flow, and send a second media content stream to the second wearable device in coordination with the first media content stream via the second session flow.

[0022] Another apparatus for wireless communication at a UE is described. The apparatus can include means for initiating a first session flow for a first wearable device via a wireless connection of the UE with the first wearable device, where the first session flow is associated with a second session flow for a second wearable device, means for receiving a set of information associated with a user of the first wearable device via the first session flow, means for receiving a set of information associated with a user of the second wearable device via the second session flow, means for sending a first media content stream to the first wearable device via the first session flow, and means for sending a second media content stream to the second wearable device in coordination with the first media content stream via the second session flow.

[0023] A non-transitory computer-readable medium storing code for wireless communications at a UE is described. The code can include instructions executable by at least one processor to initiate a first session flow for a first wearable device via a wireless connection of the UE with the first wearable device, where the first session flow is associated with a second session flow for a second wearable device, receive, via the first session flow, a set of information associated with a user of the first wearable device, receive, via the second session flow, a set of information associated with a user of the second wearable device, transmit, via the first session flow, a first media content stream to the first wearable device, and transmit, via the second session flow, a second media content stream to the second wearable device in coordination with the first media content stream.

[0024] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving, from the terminal device, an indication of the first media content stream and the second media content stream.

[0025] In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, transmitting the first media content stream can include operations, features, means, or instructions for transmitting, via the first stream, a first version of the media content via the first media content stream, where the first version includes one of a baseline version or a differential version that can be defined relative to the baseline version.

[0026] In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the second media content stream can be associated with a second version of the media content, the second version including the other of the baseline version or the differential version.

[0027] In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the baseline version can be multicast to the first wearable device and the second wearable device, and the differential version can be unicast to one of the first wearable device or the second wearable device.

[0028] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving, from the terminal device, an indication of the baseline version and the differential version.

[0029] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving, from the terminal device, an indication of the baseline version and a second version of the media content, and generating the differential version based on receiving the indication.

[0030] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, transmitting the first media content stream can include operations, features, means, or instructions for transmitting the baseline version to the first wearable device via a first unicast message and transmitting the second version of the media content to the second wearable device via a second unicast message.

[0031] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, initiating the first session stream can include operations, features, means, or instructions for receiving a first capability message from the first wearable device indicating a capability of the first wearable device to receive the first media content stream, receiving a second capability message from the second wearable device indicating a capability of the second wearable device to receive the second media content stream, transmitting an SDP offer message to the terminal device based on the first capability message and the second capability message, and receiving an SDP answer message from the terminal device based on the SDP offer message.

[0032] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the first session stream and the second session stream can be associated with a same session between the UE and the terminal device.

[0033] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the set of information associated with the user includes one or more of pose information and eye tracking information.

[0034] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the first wearable device and the second wearable device can be contact lenses.

[0035] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the media content includes a rendered video for coordinated display by the first wearable device with the second wearable device. BRIEF DESCRIPTION OF DRAWINGS

[0036] Figure 1 An example of a process flow that supports media communication for wearable devices is shown.

[0037] Figure 2 An example of a process flow that supports media communication for wearable devices is shown.

[0038] Figure 3 An example of a process flow that supports media communication for wearable devices is shown.

[0039] Figure 4An example of a process flow that supports media communication for a wearable device is shown.

[0040] Figure 5 An example of a process flow that supports media communication for a wearable device is shown.

[0041] Figure 6 An example of a process flow that supports media communication for a wearable device is shown.

[0042] Figure 7 and Figure 8 A block diagram of a device that supports media communication for a wearable device is shown.

[0043] Figure 9 A block diagram of a wearable device manager that supports media communication for a wearable device is shown.

[0044] Figure 10 A diagram of a system including a device that supports media communication for a wearable device is shown.

[0045] Figure 11 and Figure 12 A block diagram of a device that supports media communication for a wearable device is shown.

[0046] Figure 13 A block diagram of a communication manager that supports media communication for a wearable device is shown.

[0047] Figure 14 A diagram of a system including a device that supports media communication for a wearable device is shown.

[0048] Figures 15 to 20 A flow diagram illustrating a method that supports media communication for a wearable device is shown. DETAILED DESCRIPTION

[0049] In some wireless communication systems, a wearable device can receive a media content stream (e.g., a rendered video content stream) from a user equipment (UE) to project to a user of the wearable device. However, some wearable devices (e.g., contact lenses) can include multiple portions (e.g., a right lens and a left lens), and the media content can be different for each lens. Additionally, such wearable devices can have size and hardware constraints, and thus can not be able to coordinate video streams with each other (e.g., directly). There is a need for techniques to improve the communication setup, procedures, and efficiency of such wearable devices.

[0050] In some implementations, a first wearable device and a second wearable device (e.g., a pair of contact lenses) can each initiate a session stream (e.g., a real-time transport protocol (RTP) session) by sending a session description protocol (SDP) offer message to a terminal device, which can be an application server. For example, the wearable devices can send the SDP offer messages based on receiving a command from a user. The terminal device can start the session after receiving both SDP offer messages by sending an SDP answer message. The first wearable device and the second wearable device can each send information about the user (e.g., for the case where the first wearable device and the second wearable device are contact lenses, posture or eye tracking information) to the terminal device. The terminal device can generate a first media content stream and a second media content stream (e.g., rendered videos for display by the first wearable device and the second wearable device) for the first wearable device and the second wearable device, respectively, and send the media content to a UE. The UE can unicast each media content stream to the first wearable device and the second wearable device, respectively.

[0051] In some implementations, the first wearable device and the second wearable device can each initiate a session flow (e.g., an RTP session) by sending a capability message to the UE that respectively includes media capabilities of the first wearable device and the second wearable device. The UE can send an SDP offer message to the terminal device and receive an SDP answer from the terminal device. The contact lenses can each send user information (e.g., pose or eye tracking information for the case where the first wearable device and the second wearable device are contact lenses) to the UE, which in turn can send aggregated user information to the terminal device. The terminal device can indicate each media content stream to the UE, or can indicate a first version of the media content and a differential version between the first version of the media content and a second version of the media content to the UE. Alternatively, the UE can receive each version of the media content and determine (e.g., generate) the differential version. The UE can unicast each version of the media content to the first wearable device and the second wearable device, respectively. Alternatively, the UE can multicast the first version of the media content to both the first wearable device and the second wearable device, and can unicast the differential version of the media content to one of the first wearable device and the second wearable device.

[0052] Aspects of the disclosure are first described in the context of a wireless communications system. Aspects of the disclosure are further illustrated by and described in connection with process flow diagrams. Aspects of the disclosure are further illustrated by and described in connection with apparatus diagrams, system diagrams, and flow diagrams related to media communication for wearable devices.

[0053] Figure 1 An example of a wireless communications system 100 that supports media communication for wearable devices is shown in accordance with one or more aspects of the present disclosure. The wireless communications system 100 can include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 can be a Long Term Evolution (LTE) network, a LTE-Advanced (LTE-A) network, a LTE-A Pro network, a New Radio (NR) network, or a network operating according to some other wireless communication technology including future iterations of the aforementioned systems and radio technologies not expressly mentioned herein.

[0054] Network entities 105 can be dispersed throughout the geographic region of wireless communication system 100, and can be associated with a variety of devices, equipment, systems, and / or networks that can be implemented in different forms. In various examples, network entities 105 can be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other examples. In some examples, network entities 105 and UEs 115 can wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For instance, a network entity 105 can support a coverage area 110 (e.g., a geographic coverage area) within which UEs 115 and network entities 105 can establish one or more communication links 125. Coverage area 110 can be an example of a geographic area within which a network entity 105 and a UE 115 can support communication in accordance with one or more radio access technologies (RATs).

[0055] UEs 115 can be dispersed throughout the coverage areas 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or both at different times. UEs 115 can be devices in different forms or having different capabilities. Figure 1 Some example UEs 115 are illustrated. UEs 115 described herein can be able to communicate with various types of devices, such as other UEs 115 or network entities 105, as shown. Figure 1

[0056] ​As described herein, a node of the wireless communications system 100, which can be referred to as a network node or a wireless node, can be a network entity 105 (e.g., any of the network entities described herein), a UE 115 (e.g., any of the UEs described herein), a network controller, a device, an apparatus, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node can be a UE 115. As another example, a node can be a network entity 105. As yet another example, a first node can be configured to communicate with a second node or a third node. In one aspect of this example, the first node can be a UE 115, the second node can be a network entity 105, and the third node can be a UE 115. In another aspect of this example, the first node can be a UE 115, the second node can be a network entity 105, and the third node can be a network entity 105. In other aspects of this example, the first node, the second node, and the third node can be different with respect to these examples. Similarly, references to a UE 115, a network entity 105, a device, an apparatus, a computing system, and the like can include the disclosure of the UE 115, the network entity 105, the device, the apparatus, the computing system, and the like as a node. For example, a disclosure of a UE 115 configured to receive information from a network entity 105 also discloses a first node configured to receive information from a second node.

[0057] In some examples, the network entities 105 can communicate with the core network 130, or with each other, or both. For example, the network entities 105 can communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to an SI, N2, N3, or other interface protocol). In some examples, the network entities 105 can communicate with each other via the backhaul communication links 120 (e.g., directly between the network entities 105, or indirectly via the core network 130, or both). In some examples, the network entities 105 can communicate with each other via the midhaul communication links 162 (e.g., according to a midhaul interface protocol) or the front-haul communication links 168 (e.g., according to a front-haul interface protocol), or any combination thereof. The backhaul communication links 120, the midhaul communication links 162, or the front-haul communication links 168 can be or include one or more wired links (e.g., electrical, fiber optic), one or more wireless links (e.g., radio, wireless optical), etc., or various combinations thereof. The UEs 115 can communicate with the core network 130 via communication links 155.

[0058] One or more of the network entities 105 described herein can include or can be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, a NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB, or a giga-NodeB (either of which can be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, or other suitable terminology). In some examples, the network entity 105 (e.g., base station 140) can be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that can be configured to utilize a protocol stack integrated physically or logically within a single network entity 105 (e.g., a single RAN node such as a base station 140).

[0059] In some examples, the network entity 105 can be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that can be configured to utilize a protocol stack distributed physically or logically between two or more network entities 105 such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 can include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near-real-time RIC (near-RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 can also be referred to as a radio head, an intelligent radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entity 105 in the disaggregated RAN architecture can be co-located, or one or more components of the network entity 105 can be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the disaggregated RAN architecture can be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0060] The functional split between the CU 160, the DU 165, and the RU 170 is flexible and can support different functionality depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at the CU 160, the DU 165, or the RU 170. For example, a functional split of a protocol stack can be employed between the CU 160 and the DU 165, such that the CU 160 can support one or more layers of the protocol stack, and the DU 165 can support one or more different layers of the protocol stack. In some examples, the CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 can connect to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 can host lower protocol layers, such as layer 1 (LI) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and can each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of a protocol stack can be employed between the DU 165 and the RU 170, such that the DU 165 can support one or more layers of the protocol stack, and the RU 170 can support one or more different layers of the protocol stack. The DU 165 can support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 can be within a protocol layer (e.g., some functions of a protocol layer can be performed by one of the CU 160, the DU 165, or the RU 170, while other functions of that protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170). The CU 160 can be further split in functionality into a CU control plane (CU-CP) function and a CU user plane (CU-UP) function. The CU 160 can connect to one or more DUs 165 via a backhaul communication link 162 (e.g., Fl, Fl-c, Fl-u), and the DU 165 can connect to one or more RUs 170 via a front-haul communication link 168 (e.g., open front-haul (FH) interface). In some examples, the backhaul communication link 162 or the front-haul communication link 168 can be implemented in accordance with an interface (e.g., channel) between layers of a protocol stack supported by the respective network entities 105 that communicate via such communication links.

[0061] In a wireless communication system (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections to provide an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) can be partially controlled by one another. One or more IAB nodes 104 can be referred to as a donor entity or IAB donor. One or more DUs 165 or one or more RUs 170 can be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) can communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). An IAB node 104 can include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled DU 165 of an IAB donor. The IAB-MT can include a separate set of antennas for relaying communications with UEs 115 or can share the same antennas (e.g., of a RU 170) of the IAB node 104 for accessing via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, an IAB node 104 can include a DU 165 that supports a communication link with an additional entity (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of an access network. In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of an IAB node 104) can be configured to operate according to the techniques described herein.

[0062] In cases where the techniques described herein are applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture can be configured to support media communications for wearable devices as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., base station 140) can additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0063] A UE 115 can include or can be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” can also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 can also include or can be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 can include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which can be implemented in various objects such as appliances or vehicles, among other examples.

[0064] The UEs 115 described herein can be able to communicate with various types of devices, such as other UEs 115 that can sometimes act as relays or Figure 1 as shown.

[0065] The UEs 115 and the network entities 105 can wirelessly communicate with each other using resources associated with one or more carriers via one or more communication links 125 (e.g., access links). The term “carrier” can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication links 125. For example, a carrier used for a communication link 125 can include a portion of an RF spectrum band (e.g., a bandwidth part (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel can carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. The wireless communications system 100 can support communication with UEs 115 using carrier aggregation or multi-carrier operation. According to carrier aggregation, a UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communications between a network entity 105 and other devices can refer to communications between those devices and any part of the network entity 105 (e.g., an entity, sub-entity). For example, the terms “transmit,” “receive,” or “communicate” can refer to any part of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0066] Signal waveforms transmitted over a carrier can be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element can refer to a resource comprising a symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing can be inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) so that a relatively high number of resource elements (e.g., in a transmission duration) and a relatively high modulation

[0067] Time intervals for the network entity 105 or the UE 115 can be expressed in multiples of a basic time unit, which may, for example, refer to a sampling period of 1 second, where may represent supported subcarrier spacings, and may represent supported discrete Fourier transform (DFT) sizes. Time intervals of a communications resource can be organized as radio frames, each

[0068] Each frame can comprise a plurality of consecutive numbered subframes or slots, and each subframe or slot can have the same duration. In some examples, a frame can be divided (e.g., in the time domain) into subframes, and each subframe can be further divided into a number of slots. Alternatively, each frame can include a variable number of slots, and the number of slots can depend on the subcarrier spacing. Each slot can include a number of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems 100, a slot can be further divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period can be associated with one or more (e.g., sampling periods. The duration of a symbol period can depend on the subcarrier spacing or the frequency band of operation.

[0069] A subframe, a slot, a mini-slot, or a symbol can be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and can be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communications system 100 (e.g., in the time domain) can be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0070] According to various techniques, physical channels can be multiplexed for communication using carriers. Physical control channels and physical data channels can be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) of a physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth or a subset thereof of a carrier. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more of the UEs 115 can monitor or search control regions for control information according to one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level of a control channel candidate can refer to a quantity of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. A search space set can include common search space sets configured for transmission of control information to multiple UEs 115 and UE-specific search space sets configured for transmission of control information to a specific UE 115.

[0071] The network entity 105 can provide communication coverage for a geographic area 110 via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term “cell” can refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and can be associated with a identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier) used by a UE 115 to identify a cell from which it is receiving a signal. In some examples, a cell can also refer to a coverage area 110 or a portion thereof (e.g., a sector) within which a logical communication entity operates. The coverage area 110 for a cell can overlap with those of other cells (e.g., small cells or macro cells) or cover a similar or larger area depending on various factors such as environments, types of user equipment 115, long term evolution (LTE) or LTE-Advanced (LTE-A) capabilities, or the like.

[0072] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0073] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0074] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0075] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0076] In some examples, UEs 115 can be configured to support direct communications with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., in a peer-to-peer (P2P) or D2D or sidelink communication). In some examples, one or more UEs 115 in a group that performs D2D communication can be within the coverage area 110 of a network entity 105 (e.g., base station 140, RU 170) that supports aspects of such D2D communication configured by the network entity 105 (e.g., scheduled by the network entity). In some examples, one or more UEs 115 in such a group can be outside the coverage area 110 of a network entity 105 or can otherwise be unable to, or configured not to, receive from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, where one UE 115 transmits to many other UEs 115 in the group. In some examples, a network entity 105 can facilitate scheduling of resources for D2D communication. In some other examples, D2D communication can be carried out between UEs 115 without involvement of a network entity 105.

[0077] The core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 can be an evolved packet core (EPC) or 5G core (5GC), which can include at least one control plane entity that can manage access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that can route packets or

[0078] The wireless communications system 100 can operate using one or more frequency bands, e.g., in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band, since the wavelengths range from approximately one decimeter to one meter in length. The UHF wave s can be blocked or redirected by buildings and environmental features, but the waves can penetrate structures sufficiently for a macro cell to provide service to the UHF devices located indoors. The use of the UHF region enables the use of smaller antennas in comparison to larger antennas used for smaller frequency regions, which are typically used for macro cell base stations. In turn, the smaller antennas can be located closer to the devices, which increases the robustness of the connection between the macro cell base stations and the UHF devices. However, the downlink transmissions can be affected by the distance between the macro cell base stations and the UHF devices, especially in a long distance, high urban environment.

[0079] The wireless communications system 100 can utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 can employ LTE License Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed frequency spectrum band such as the 5 GHz industrial, scientific and medical (ISM) band. When operating in unlicensed frequency spectrum bands, devices such as network

[0080] The network entities 105 (e.g., base stations 140, RUs 170) or UEs 115 can be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of a network entity 105 or a UE 115 can be located in one or more antenna arrays or antenna panels, which can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays can be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 can be located at different geographic locations. A network entity 105 can include antenna arrays with a number of rows and columns of antenna ports that the network entity 105 can use for beamforming to support communication with UEs 115. Likewise, a UE 115 can include one or more antenna arrays, which can support various MIMO or beamforming operations. Additionally or alternatively, an antenna panel can support RF beamforming for signals transmitted via the antenna ports.

[0081] Beamforming, which can also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer a beam of energy in a specific direction along with the spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining the signals communicated by antenna elements of an antenna array such that some signals are amplified while other signals are attenuated, which allows the beams to be steered or shaped in specific directions. The adjustments to the signals communicated by the antenna elements can include applying amplitude offsets, phase offsets, or both to the signals carried by the antenna elements associated with the device. The adjustments associated with each of the antenna elements can be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

[0082] In some implementations, a first wearable device and a second wearable device (e.g., a pair of contact lenses, a pair of earbuds, a pair of biofeedback devices, a pair of game control devices, or other wearable devices) can each initiate a session flow (e.g., an RTP session) by sending an SDP offer message to a terminal device, which can be an application server. For example, the wearable devices can send the SDP offer messages in response to receiving a command from a user. The terminal device can start the session after receiving both SDP offer messages by sending an SDP answer message. The first wearable device and the second wearable device can each send information about the user (e.g., for the case where the first wearable device and the second wearable device are contact lenses, posture or eye tracking information) to the terminal device. The terminal device can generate a first media content stream and a second media content stream (e.g., rendered video for display by the first wearable device and the second wearable device, audio to be played by the first wearable device and the second wearable device, biofeedback or game feedback provided by the first wearable device and the second wearable device, or other media content) for the first wearable device and the second wearable device, respectively, and send the media content to the UE 115. The UE 115 can unicast each media content stream to the first wearable device and the second wearable device, respectively.

[0083] In some implementations, the first wearable device and the second wearable device can each initiate a session flow (e.g., an RTP session) by sending a capability message to the UE 115 including media capabilities of the first wearable device and the second wearable device, respectively. The UE 115 can send an SDP offer message to the end device and receive an SDP answer from the end device. The contact lenses can each send user information (e.g., pose or eye tracking information, body movement or biometric information, or other feedback for the end device) to the UE 115, which can in turn send aggregated user information to the end device. The end device can indicate each media content stream to the UE 115, or can indicate a first version of the media content and a differential version between the first version of the media content and a second version of the media content to the UE 115. Alternatively, the UE 115 can receive each version of the media content and determine (e.g., generate) the differential version. The UE 115 can unicast each version of the media content to the first wearable device and the second wearable device, respectively. Alternatively, the UE 115 can multicast the first version of the media content to both the first wearable device and the second wearable device, and can unicast the differential version of the media content to one of the first wearable device and the second wearable device.

[0084] Figure 2 An example of a wireless communications system 200 that supports media communication for wearable devices is shown, in accordance with one or more aspects of the present disclosure. The wireless communications system 200 can implement aspects of, or be implemented by aspects of, the wireless communications system 100. For example, the wireless communications system 200 can include a UE 115 (e.g., UE 115-a) and a network entity 105 (e.g., network entity 105-a), which can be examples of the corresponding devices as described with reference to FIG. 1. Figure 1

[0085] ​In some examples of the wireless communication system 200, the wearable device 205 can receive a media stream (e.g., a video stream) from the UE 115-a to project to a user. However, some wearable devices 205 (e.g., contact lenses) can include multiple portions (e.g., wearable device 205-a and wearable device 205-b), and thus the video stream can be different for each of the wearable device 205-a and the wearable device 205-b. In some examples, a first video stream for the wearable device 205-a and a second video stream for the wearable device 205-b can have similar characteristics, and transmitting both video streams can reduce efficiency. Additionally, the wearable device 205-a and the wearable device 205-b can have size and hardware constraints, and thus can not be able to directly coordinate the video streams with each other in some cases. Thus, the techniques described herein can improve the communication setup, communication procedure, and efficiency of such wearable devices 205.

[0086] The wearable device 205-a and the wearable device 205-b can be ambient IoT devices. That is, the wearable device 205-a and the wearable device 205-b can be ultra-low complexity devices (e.g., battery-less devices) with ultra-low power consumption. For example, the wearable device 205-a and the wearable device 205-b can have limited or no energy storage capabilities, and thus can harvest energy from external sources (e.g., ambient energy). In some examples, the wearable device 205-a and the wearable device 205-b can not be able to be manually recharged or replaced with energy.

[0087] In some examples of the wireless communication system 200, the wearable device 205-a can wirelessly communicate signaling 215-a with the UE 115-a over the tethered link 210-a. Similarly, the wearable device 205-b can wirelessly communicate signaling 215-b with the UE 115-a over the tethered link 210-b. The UE 115-a can operate in a cell 235 of the network entity 105-a with the UPF 220. The UE 115-a can accordingly send signaling 230 regarding the wearable device 205-a and the wearable device 205-b to the end device 225 (e.g., an edge application server) via the UPF 220.

[0088] In some implementations, wearable device 205-a and wearable device 205-b can each initiate a session flow (e.g., a real-time transport protocol (RTP) session) by sending a session description protocol (SDP) offer message to terminal device 225 (e.g., via tethering link 210-a and tethering link 210-b, respectively). For example, wearable device 205-a and wearable device 205-b can each send an SDP offer message in response to receiving a command from a user (e.g., a voice command, a gesture, or a selection from a menu in a virtual screen projected by wearable device 205-a, wearable device 205-b, or UE 115-a). Terminal device 225 can start the session by sending an SDP answer message to each of wearable device 205-a and wearable device 205-b (e.g., after receiving both SDP offer messages). Terminal device 225 can receive information about the user from each of wearable device 205-a and wearable device 205-b (e.g., for the case where the wearable devices 205 are contact lenses, pose or eye tracking information). Terminal device 225 can generate a media content stream (e.g., a rendered video) for each of wearable device 205-a and wearable device 205-b, and send the media content stream to UE 115-a. UE 115-a can unicast the media content stream to wearable device 205-a and wearable device 205-b, respectively.

[0089] In some implementations, wearable device 205-a and wearable device 205-b can each initiate a session flow (e.g., an RTP session, a layer 3 link session, or a layer 2 link session) with UE 115-a by sending a capability message to UE 115-a over tethering link 210-a and tethering link 210-b, respectively. For example, the capability messages can indicate media capabilities of wearable device 205-a and wearable device 205-b (e.g., the wearable devices’ 205 ability to independently receive individual media content streams from UE 115-a).

[0090] UE 115-a can initiate a session flow with terminal device 225 by sending an SDP offer message to terminal device 225 and receiving an SDP answer from terminal device 225. Wearable device 205-a and wearable device 205-b can each send information about the user (e.g., pose or eye tracking information) to UE 115-a, and UE 115-a can send aggregated user information to terminal device 225, the aggregated user information indicating information for both wearable devices 205. Terminal device 225 can indicate each media content stream (e.g., each rendered video) to UE 115-a, or can indicate a baseline version of the media content (e.g., a first rendered video) and a differential version of the media content (e.g., a delta between the first rendered video and a second rendered video) to UE 115-a.

[0091] Alternatively, UE 115-a can receive two media content streams (e.g., two rendered videos) and can generate a differential version of the media content relative to a baseline version of the media content. UE 115-a can unicast the respective media content stream to each of wearable device 205-a and wearable device 205-b. Alternatively, UE 115-a can multicast the baseline version of the media content to both wearable device 205-a and wearable device 205-b, and can unicast the differential version of the media content to one of wearable device 205-a and wearable device 205-b. Additional details and examples related to session flows between wearable devices and terminal devices, and media content sent to wearable devices, are shown and described by reference to Figure 3 ‍ Figure 6

[0092] Figure 3 An example of a process flow 300 that supports media communication for wearable devices is shown in accordance with one or more aspects of the present disclosure. Process flow 300 can implement, or be implemented by, aspects of wireless communication system 100 or wireless communication system 200. For example, process flow 300 can include UE 115-b, which can be an example of a UE 115 as described with reference to Figure 1 Process flow 300 can include wearable apparatus 305-a and wearable apparatus 305-b, which can be examples of contact lenses (e.g., smart contact lenses) or other wearable devices as described with reference to Figure 2 Process flow 300 can additionally or alternatively include terminal device 310, which can be an example of an application server as described with reference to Figure 2

[0093] ​​In the following description of process flow 300, the operations between wearable device 305-a, wearable device 305-b, UE 115-b, and terminal device 310 can be transmitted in a different order than the example shown. Some operations can also be omitted from process flow 300, and other operations can be added to process flow 300. Moreover, although some operations or signaling are shown as occurring at different times for discussion purposes, these operations can actually be concurrent.

[0094] In some examples, at 315-a and 315-b, respectively, wearable device 305-a and wearable device 305-b can receive a command (e.g., a voice command, a gesture, or a selection from a menu in a virtual screen projected by wearable device 305-a, wearable device 305-b, or UE 115-b) from a user to initiate a first session flow and a second session flow, respectively. In some examples, the command can indicate (e.g., explicitly) information including a destination address (such as a URL or IP address) of terminal device 310, a name of an application (e.g., a game), a port number of each of wearable device 305-a, wearable device 305-b, and terminal device 310, or a combination thereof. In some examples, wearable device 305-a and wearable device 305-b can derive the information based on the indication in the command.

[0095] At 320-a and 320-b, wearable device 305-a and wearable device 305-b can each transmit an SDP offer message to initiate a first session flow and a second session flow (e.g., RTP sessions) with terminal device 310, respectively. Wearable device 305-a and wearable device 305-b can transmit the SDP offer messages via a connection between wearable device 305-a and UE 115-b and a connection between wearable device 305-b and UE 115-b, respectively. The SDP offer messages can indicate to terminal device 310 whether the SDP offer is transmitted from wearable device 305-a or wearable device 305-b. The first session flow can be associated with a first session with terminal device 310, and the second session flow can be associated with a second session with terminal device 310 that is different from the first session.

[0096] At 325-a and 325-b, the terminal device 310 can transmit SDP answer messages to the wearable device 205-a and the wearable device 205-b, respectively. The terminal device 310 can transmit the SDP answer messages after receiving both SDP offer messages (e.g., to synchronize the first session stream and the second session stream). For example, the terminal device 310 can start a timer based on receiving the SDP offer message from the wearable device 305-a. If the timer expires before the terminal device 310 receives the SDP offer message from the wearable device 305-b, the terminal device 310 can transmit a notification to terminate the session to the wearable device 305-a via the SDP answer message.

[0097] At 330-a and 330-b, the wearable device 305-a and the wearable device 305-b can transmit indications of a first set of information about the user and a second set of information about the user to the terminal device 310. The first set of information and the second set of information can include, for example, gesture information, eye tracking information, or other information associated with movements or behaviors of the user. For example, the gesture information can indicate a physical posture or stance of the user while wearing the wearable device 305, and the eye tracking information can indicate eye movements of the user while wearing the wearable device 305. The wearable device 305-a can transmit the first set of information via the first session stream, and the wearable device 305-b can transmit the second set of information via the second session stream.

[0098] At 335-a and 335-b, the terminal device 310 can transmit a first media content stream and a second media content stream to the UE 115-b (e.g., via the first session stream and the second session stream, respectively). The first media content stream can include a first version of media content (e.g., a rendered video for display by the wearable device 305-a), and the second media content stream can include a second version of the media content (e.g., a rendered video for display by the wearable device 305-b in coordination with the first rendered video). In some examples, the media content can include other types of video or media.

[0099] At 340-a and 340-b, the UE 115-b can transmit the first media content stream to the wearable device 305-a and the second media content stream to the wearable device 305-b, respectively. For example, the UE 115-b can transmit the first media content stream to the wearable device 305-a via a first unicast message and the second media content stream to the wearable device 305-b via a second unicast message. The wearable device 305-a can project the first rendered video to the user in coordination with the wearable device 305-b projecting the second rendered video. That is, the user can view the first rendered video and the second rendered video simultaneously or in a particular order via the wearable devices 305.

[0100] Figure 4 An example of a process flow 400 that supports media communication for wearable devices is shown that can implement, or be implemented by, aspects of wireless communication system 100, wireless communication system 200, or process flow 300, in accordance with one or more aspects of the present disclosure. For example, process flow 400 can include a UE 115-c, which can be an example of a UE 115 as described with reference to Figure 1 Figure 2 Process flow 400 can additionally or alternatively include a wearable device 405-a and a wearable device 405-b, which can be examples of contact lenses (e.g., smart contact lenses) or other wearable devices as described with reference to Figure 2

[0101] In the following description of process flow 400, the operations between wearable device 405-a, wearable device 405-b, UE 115-c, and terminal device 410 can be transmitted in a different order than the example shown. Some operations can also be omitted from process flow 400, and other operations can be added to process flow 400. Moreover, although some operations or signaling are shown as occurring at different times for discussion purposes, such operations can actually be concurrent.

[0102] In some examples, at 415-a and 415-b, respectively, wearable device 405-a and wearable device 405-b can receive a command (e.g., a voice command, a gesture, or a selection from a menu in a virtual screen projected by wearable device 405-a, wearable device 405-b, or UE 115-c) from a user to initiate a first session flow and a second session flow (e.g., RTP sessions), respectively. In some examples, the command can indicate (e.g., explicitly) information including a destination address (such as a URL or IP address) of terminal device 410, a name of an application (e.g., a game), a port number of each of wearable device 405-a, wearable device 405-b, and terminal device 410, or a combination thereof. In some examples, wearable device 405-a and wearable device 405-b can derive the information based on the indication in the command.

[0103] ​​At 420-a and 420-b, the wearable device 405-a and the wearable device 405-b can initiate the first session flow and the second session flow by transmitting a first capability message and a second capability message, respectively, to the UE 115-c. The first capability message and the second capability message can indicate media capabilities of the wearable device 405-a and the wearable device 405-b, respectively. For example, the first capability message can indicate a capability of the wearable device 405-a to receive the first media content stream. The second capability message can indicate a capability of the wearable device 405-b to receive the second media content stream.

[0104] At 425, the UE 115-c can transmit an SDP offer message to the end device 410 to initiate a session (e.g., an RTP session) with the end device 410. The SDP offer message can indicate the presence of the wearable device 405-a and the wearable device 405-b. The UE 115-c can transmit the SDP offer message based on receiving the first capability message, the second capability message, or both. In some examples, the UE 115-c can initiate a first session flow and a second session flow (e.g., an RTP session, a layer 3 link, or a layer 2 link) with the wearable device 405-a and the wearable device 405-b, respectively. The first session flow and the second session flow can each be associated with the session between the UE 115-c and the end device 410.

[0105] At 430, the UE 115-c can receive an SDP answer message from the end device 410. The end device 410 can transmit the SDP answer message in response to receiving the SDP offer message.

[0106] At 435-a and 435-b, the wearable device 405-a and the wearable device 405-b can transmit an indication of a first set of information about the user and a second set of information about the user, respectively, to the UE 115-c. The first set of information and the second set of information can include, for example, pose information, eye tracking information, or both. The wearable device 405-a can transmit the first set of information via the first session flow, and the wearable device 405-b can transmit the second set of information via the second session flow.

[0107] At 440, the UE 115-c can transmit a set of aggregated information about the user to the end device 410. The set of aggregated information can include, for example, the first set of information and the second set of information.

[0108] At 445, the end device can transmit the aggregated media content stream to UE 115-c. In some examples, the aggregated media content stream can include the first version of media content and the second version of media content. The first version of media content can be, for example, the first rendered video for display by wearable device 405-a. The second version of media content can be, for example, the second rendered video for display by wearable device 405-b in coordination with the first version of media content. In some examples, the media content can include other types of video or media.

[0109] At 450-a and 450-b, UE 115-c can transmit the first version of media content and the second version of media content to wearable device 405-a and wearable device 405-b via the first session stream and the second session stream, respectively. For example, UE 115-c can transmit the first version of media content to wearable device 405-a via a first unicast message. UE 115-c can transmit the second version of media content to wearable device 405-b via a second unicast message. Wearable device 405-a can project the first rendered video to the user in coordination with (e.g., simultaneously, at a particular time) wearable device 405-b projecting the second rendered video.

[0110] Figure 5 A process flow 500 that supports media communication for wearable devices is shown, in accordance with one or more aspects of the present disclosure. The process flow 500 can implement, or be implemented by, aspects of the wireless communication system 100, the wireless communication system 200, the process flow 300, or the process flow 400. For example, the process flow 500 can include a UE 115-d, which can be an example of a UE 115 as described with reference to FIGs. 1 and 2. The process flow 500 can include wearable devices 505-a and 505-b, which can be examples of contact lenses (e.g., smart contact lenses) or other wearable devices as described with reference to FIGs. 1 and 2. The process flow 500 can additionally or alternatively include an end device 510, which can be an example of an application server as described with reference to FIGs. 1 and 2. Figure 1 Figure 2 Figure 2

[0111] In the following description of the process flow 500, the operations between the wearable devices 505-a, 505-b, the UE 115-d, and the end device 510 can be transmitted in a different order than the example shown. Some operations can also be omitted from the process flow 500, and other operations can be added to the process flow 500. Furthermore, although some operations or signaling are shown as occurring at different times, these operations can actually occur at the same time.

[0112] ​​​In some examples, at 515-a and 515-b, the wearable device 505-a and the wearable device 505-b can receive a command (e.g., a voice command, a gesture, or a selection from a menu in a virtual screen projected by the wearable device 505-a, the wearable device 505-b, the UE 115-d, or a combination thereof) from the user to initiate the first session flow and the second session flow (e.g., RTP sessions), respectively. In some examples, the command can indicate (e.g., explicitly) information including a destination address (such as a URL or an IP address) of the terminal device 510, a name of an application (e.g., a game), a port number of each of the wearable device 505-a, the wearable device 505-b, and the terminal device 510, or a combination thereof. In some examples, the wearable device 505-a and the wearable device 505-b can derive the information based on the indication in the command.

[0113] At 520-a and 520-b, the wearable device 505-a and the wearable device 505-b can initiate the first session flow and the second session flow by sending a first capability message and a second capability message, respectively, to the UE 115-d. The first capability message and the second capability message can indicate media capabilities of the wearable device 505-a and the wearable device 505-b, respectively. For example, the first capability message can indicate a capability of the wearable device 505-a to receive the first media content stream. The second capability message can indicate a capability of the wearable device 505-b to receive the second media content stream.

[0114] At 525, the UE 115-d can send an SDP offer message to the terminal device 510 to initiate a session (e.g., an RTP session) with the terminal device 510. The SDP offer message can indicate the presence of the wearable device 505-a and the wearable device 505-b. The UE 115-d can send the SDP offer message based on receiving the first capability message, the second capability message, or both. In some examples, the UE 115-d can initiate the first session flow and the second session flow (e.g., RTP sessions, layer 3 links, or layer 2 links) with the wearable device 505-a and the wearable device 505-b, respectively. The first session flow and the second session flow can each be associated with the session between the UE 115-d and the terminal device 510.

[0115] At 530, the UE 115-d can receive an SDP answer message from the terminal device 510. The terminal device 510 can send the SDP answer message in response to the SDP offer message.

[0116] At 535-a and 535-b, the wearable device 505-a and the wearable device 505-b can transmit, to the UE 115-d, an indication of a first set of information about the user and a second set of information about the user, respectively. The first set of information and the second set of information can include, for example, pose information, eye tracking information, or both. The wearable device 505-a can transmit the first set of information via the first session stream, and the wearable device 505-b can transmit the second set of information via the second session stream.

[0117] At 540, the UE 115-d can transmit, to the terminal device 510, a set of aggregated information about the user. The set of aggregated information can include, for example, the first set of information and the second set of information.

[0118] At 545, the terminal device can transmit, to the UE 115-d, an aggregated media content stream. In some examples, the aggregated media content stream can include a baseline version of the media content and an additional version of the media content. The baseline version of the media content can be, for example, the first rendered video for display by the wearable device 505-a. The additional version of the media content can be, for example, the second rendered video for display by the wearable device 505-b in coordination with the first version of the media content.

[0119] At 550, the UE 115-d can generate a differential version of the media content. The differential version of the media content can be, for example, a difference value (e.g., a delta) between the first rendered video and the second rendered video. The differential version of the media content can be defined with respect to the baseline version. For example, the differential version of the media content can be defined such that a wireless device (e.g., the wearable device 505-a or the wearable device 505-b) can combine the differential version of the media content and the baseline version of the media content to generate the additional version of the media content.

[0120] At 555, the UE 115-d can transmit, to the wearable device 505-a and the wearable device 505-b, the baseline version of the media content via the first session stream and the second session stream, respectively. For example, the UE 115-d can transmit the baseline version of the media content to the wearable device 505-a and the wearable device 505-b via a broadcast message.

[0121] At 560, the UE 115-d can transmit, to the wearable device 505-b, the differential version of the media content via the second session stream. For example, the UE 115-d can transmit the differential version of the media content to the wearable device 505-b via a unicast message. The wearable device 505-a can project the first rendered video to the user in coordination with the wearable device 505-b projecting the second rendered video.

[0122] Figure 6An example of a process flow 600 that supports media communication for wearable devices is shown in accordance with one or more aspects of the present disclosure. The process flow 600 can implement, or be implemented by, aspects of the wireless communication system 100, the wireless communication system 200, the process flow 300, the process flow 400, or the process flow 500. For example, the process flow 600 can include a UE 115-d, which can be an example of a UE 115 as described with reference to Figure 1 The process flow 600 can include a wearable device 605-a and a wearable device 605-b, which can be examples of contact lenses (e.g., smart contact lenses) or other wearable devices as described with reference to Figure 2 The process flow 600 can additionally or alternatively include a second terminal device 610, which can be an example of an application server as described with reference to Figure 2

[0123] In the following description of the process flow 600, the operations between the wearable device 605-a, the wearable device 605-b, the UE 115-d, and the terminal device 610 can be transmitted in a different order than the example shown. Some operations can also be omitted from the process flow 600, and other operations can be added to the process flow 600. Moreover, although some operations or signaling are shown as occurring at different times, these operations can actually occur at the same time.

[0124] In some examples, at 615-a and 615-b, respectively, the wearable device 605-a and the wearable device 605-b can receive a command (e.g., a voice command, a gesture, or a selection from a menu in a virtual screen projected by the wearable device 605-a, the wearable device 605-b, or the UE 115-e) from a user to initiate a first session flow and a second session flow (e.g., RTP sessions), respectively. In some examples, the command can indicate (e.g., explicitly) information including a destination address (such as a URL or an IP address) of the terminal device 610, a name of an application (e.g., a game), a port number of each of the wearable device 605-a, the wearable device 605-b, and the terminal device 610, or a combination thereof. In some examples, the wearable device 605-a and the wearable device 605-b can derive the information based on the indication in the command.

[0125] ​At 620-a and 620-b, the wearable device 605-a and the wearable device 605-b can initiate the first session flow and the second session flow by transmitting a first capability message and a second capability message, respectively, to the UE 115-e. The first capability message and the second capability message can indicate media capabilities of the wearable device 605-a and the wearable device 605-b, respectively. For example, the first capability message can indicate a capability of the wearable device 605-a to receive the first media content stream. The second capability message can indicate a capability of the wearable device 605-b to receive the second media content stream.

[0126] At 625, the UE 115-e can transmit an SDP offer message to the end device 610 to initiate a session (e.g., an RTP session) with the end device 610. The SDP offer message can indicate the presence of the wearable device 605-a and the wearable device 605-b. The UE 115-e can transmit the SDP offer message based on receiving the first capability message, the second capability message, or both. In some examples, the UE 115-e can initiate a first session flow and a second session flow (e.g., an RTP session, a layer 3 link, or a layer 2 link) with the wearable device 605-a and the wearable device 605-b, respectively. The first session flow and the second session flow can each be associated with the session between the UE 115-e and the end device 610.

[0127] At 630, the UE 115-e can receive an SDP answer message from the end device 610. The end device 610 can transmit the SDP answer message in response to the SDP offer message.

[0128] At 635-a and 635-b, the wearable device 605-a and the wearable device 605-b can transmit an indication of a first set of information about the user and a second set of information about the user, respectively, to the UE 115-e. The first set of information and the second set of information can include, for example, pose information, eye tracking information, or both. The wearable device 605-a can transmit the first set of information via the first session flow, and the wearable device 605-b can transmit the second set of information via the second session flow.

[0129] At 640, the UE 115-e can transmit a set of aggregated information about the user to the end device 610. The set of aggregated information can include, for example, the first set of information and the second set of information.

[0130] At 645, the terminal device can transmit the aggregated media content stream to UE 115-e. In some examples, the aggregated media content stream can include a baseline version of the media content and a differential version of the media content. The first version of the media content can be, for example, the first rendered video for display by wearable device 605-a. The differential version of the media content can be, for example, a difference value (e.g., a delta) between the first rendered video and an additional version of the media content (e.g., the second rendered video for display by wearable device 605-b). The differential version of the media content can be defined with respect to the baseline version. For example, the differential version of the media content can be defined such that a wireless device (e.g., wearable device 605-a or wearable device 605-b) can combine the differential version of the media content and the baseline version of the media content to generate the additional version of the media content.

[0131] At 650, UE 115-e can transmit the baseline version of the media content to wearable device 605-a and wearable device 605-b via the first session stream and the second session stream, respectively. For example, UE 115-e can transmit the baseline version of the media content to wearable device 605-a and wearable device 605-b via a broadcast message.

[0132] At 655, UE 115-e can transmit the differential version of the media content to wearable device 605-b via the second session stream. For example, UE 115-e can transmit the differential version of the media content to wearable device 605-b via a unicast message. Wearable device 605-a can project the first rendered video to the user in coordination with wearable device 605-b projecting the second rendered video.

[0133] Figure 7 A block diagram 700 of a device 705 that supports media communication for wearable devices is shown, in accordance with one or more aspects of the present disclosure. The device 705 can be an example of aspects of a wearable device as described herein. The device 705 can include an input module 710, an output module 715, and a wearable device manager 720. The device 705, or one or more components of the device 705 (e.g., input module 710, output module 715, and wearable device manager 720) can include at least one processor that can be coupled with at least one memory to individually or collectively support or enable at least the described functionality. Each component of the device 705 can communicate, for example, via one or more buses.

[0134] The wearable device manager 720, the input module 710, the output module 715, or various combinations or components thereof, can be examples of means for performing various aspects of media communication for a wearable device as described herein. For example, the wearable device manager 720, the input module 710, the output module 715, or various combinations or components thereof, can be capable of performing one or more of the functions described herein.

[0135] In some examples, the wearable device manager 720, the input module 710, the output module 715, or various combinations or components thereof, can be implemented in hardware (e.g., in a communication management circuit). The hardware can include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA, or other programmable logic device, a microcontroller, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor can be configured to perform one or more of the functions described herein (e.g., the at least one processor executing instructions stored in the at least one memory).

[0136] Additionally or alternatively, the wearable device manager 720, the input module 710, the output module 715, or various combinations or components thereof, can be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, functions of the wearable device manager 720, the input module 710, the output module 715, or various combinations or components thereof, can be executed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

[0137] The wearable device manager 720 can support wireless communication at a first wearable device in accordance with examples as disclosed herein. For example, the wearable device manager 720 can be capable of, configured to, or operable to support means for initiating a first session stream via a wireless connection between the first wearable device and a UE, where the first session stream is associated with a second session stream for a second wearable device. The wearable device manager 720 can be capable of, configured to, or operable to support means for transmitting a set of information associated with a user of the first wearable device via the first session stream. The wearable device manager 720 can be capable of, configured to, or operable to support means for receiving a first media content stream via the first session stream and a second media content stream via the second session stream in coordination.

[0138] By including or configuring wearable device manager 720 in accordance with examples as described herein, device 705 (e.g., control input module 710, output module 715, wearable device manager 720, or at least one processor coupled with or otherwise in combination with which they are configured) can support techniques for first and second wearable devices to initiate media sessions with a UE and a terminal device, which can result in reduced processing and lower power consumption at the wearable devices, increased signaling throughput, and reduced latency.

[0139] Figure 8 A block diagram 800 of a device 805 that supports media communication for wearable devices is shown, in accordance with one or more aspects of the present disclosure. The device 805 can be an example of aspects of a device 705 or a wearable device as described herein. The device 805 can include an input module 810, an output module 815, and a wearable device manager 820. The device 805, or one or more components of the device 805 (e.g., the input module 810, the output module 815, and the wearable device manager 820) can include at least one processor, which can be coupled with at least one memory to support the described techniques. Each of these components can communicate, for example, via one or more buses. The input module 810 can include one or more input devices, such as a keyboard, a mouse, a pen, a voice input device, a touch input device, etc. The output module 815 can include one or more output devices, such as a display, a printer, one or more speakers, etc. The output module 815 can include various components of a wearable device, such as a display, a speaker, etc.

[0140] The device 805, or various components of the device 805, can be an example of means for performing various aspects of media communication for wearable devices as described herein. For example, the wearable device manager 820 can include a session flow initiation manager 825, a user information manager 830, a media content manager 835, or any combination thereof. The wearable device manager 820 can be an example of aspects of a wearable device manager 720 as described herein. In some examples, the wearable device manager 820, or various components thereof, can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with the input module 810, the output module 815, or both. For example, the wearable device manager 820 can receive information from the input module 810, transmit information to the output module 815, or integrate in combination with the input module 810, the output module 815, or both to obtain information, output information, or perform various other operations as described herein.

[0141] The wearable device manager 820 can support wireless communications at a first wearable device in accordance with examples as disclosed herein. The session flow initiation manager 825 can enable, be configured as, or be operable to support means for initiating a first session flow via a wireless connection between the first wearable device and a UE, where the first session flow is associated with a second session flow for a second wearable device. The user information manager 830 can enable, be configured as, or be operable to support means for transmitting a set of information associated with a user of the first wearable device via the first session flow. The media content manager 835 can enable, be configured as, or be operable to support means for receiving a first media content stream via the first session flow and a second media content stream via the second session flow in coordination.

[0142] Figure 9 A block diagram 900 of a wearable device manager 920 that supports media communications for wearable devices in accordance with one or more aspects of the present disclosure is shown. The wearable device manager 920 can be an example of aspects of the wearable device manager 720, the wearable device manager 820, or both, as described herein. The wearable device manager 920, or various components thereof, can be an example of means for performing various aspects of media communications for wearable devices as described herein. For example, the wearable device manager 920 can include a session flow initiation manager 925, a user information manager 930, a media content manager 935, a media capability manager 940, an SDP manager 945, or any combination thereof. Each of these components, or the components or sub-components thereof (e.g., one or more processors, one or more memories), can communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0143] The wearable device manager 920 can support wireless communications at a first wearable device in accordance with examples as disclosed herein. The session flow initiation manager 925 can enable, be configured as, or be operable to support means for initiating a first session flow via a wireless connection between the first wearable device and a UE, where the first session flow is associated with a second session flow for a second wearable device. The user information manager 930 can enable, be configured as, or be operable to support means for transmitting a set of information associated with a user of the first wearable device via the first session flow. The media content manager 935 can enable, be configured as, or be operable to support means for receiving a first media content stream via the first session flow and a second media content stream via the second session flow in coordination.

[0144] In some examples, to support receiving the first media content stream, the media content manager 935 can be, be configured as, or be operable as, means for supporting a first version of media content for receipt via the first media content stream via the first session stream, where the first version comprises one of a baseline version or a differential version defined relative to the baseline version.

[0145] In some examples, the second media content stream is associated with a second version of the media content, the second version comprising the other of the baseline version or the differential version.

[0146] In some examples, the baseline version is multicast to the first wearable device and the second wearable device, and the differential version is unicast to one of the first wearable device or the second wearable device.

[0147] In some examples, to support receiving the first media content stream, the media content manager 935 can be, be configured as, or be operable as, means for receiving the baseline version from the UE via a first unicast message, where the second version is transmitted to the second wearable device via a second unicast message.

[0148] In some examples, the first session stream and the second session stream are associated with a same session between the UE and the end device. In some examples, the first session stream is associated with a first session with the end device. In some examples, the first session is different from a second session with the end device associated with the second session stream.

[0149] In some examples, to support initiating the first session stream, the media capability manager 940 can be, be configured as, or be operable as, means for transmitting a capability message to the UE indicating a capability of the first wearable device to receive the first media content stream. In some examples, to support initiating the first session stream, the SDP manager 945 can be, be configured as, or be operable as, means for transmitting an SDP offer message to the end device and receiving an SDP answer message from the end device based on the SDP offer message.

[0150] In some examples, the set of information associated with the user comprises one or more of pose information and eye tracking information. In some examples, the first wearable device and the second wearable device are contact lenses. In some examples, the media content comprises a rendered video for coordinated display by the first wearable device and the second wearable device.

[0151] Figure 10A diagram illustrating a system 1000 including a device 1005 that supports media communication for wearable devices in accordance with one or more aspects of the present disclosure is shown. The device 1005 can be an example of or include the components of a device 705, a device 805, or a wearable device as described herein. The device 1005 can include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a wearable device manager 1020, a communications module 1010, an antenna 1015, a sensor component 1025, a power module 1030, at least one memory 1035, at least one processor 1040, and a wireless device 1050. These components can be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1045).

[0152] The wearable device manager 1020 can support wireless communications at a first wearable device in accordance with examples as disclosed herein. For example, the wearable device manager 1020 can enable, be configured as, or be operable to support means for initiating a first session flow via a wireless connection between the first wearable device and a UE, where the first session flow is associated with a second session flow for a second wearable device. The wearable device manager 1020 can enable, be configured as, or be operable to support means for transmitting a set of information associated with a user of the first wearable device via the first session flow. The wearable device manager 1020 can enable, be configured as, or be operable to support means for receiving a first media content stream via the first session flow and a second media content stream via the second session flow in coordination.

[0153] By including or configuring the wearable device manager 1020 in accordance with examples as described herein, the device 1005 can support techniques for a first wearable device and a second wearable device to initiate media sessions with a UE and an end device, which can improve communication reliability, improve user experience related to processing reduction, reduce power consumption, and improve coordination between devices.

[0154] Figure 11A block diagram 1100 of a device 1105 that supports media communication for wearable devices is shown, in accordance with one or more aspects of the present disclosure. The device 1105 can be an example of aspects of a UE 115 as described herein. The device 1105 can include a receiver 1110, a transmitter 1115, and a communications manager 1120. The device 1105, or one or more components of the device 1105 (e.g., the receiver 1110, the transmitter 1115, and the communications manager 1120), can include at least one processor that can be coupled to at least one memory to individually or collectively support or implement at least some of the described techniques. Each of these components can communicate, for example, via one or more buses. The device 1105 can include one or more components described in this disclosure.

[0155] The receiver 1110 can provide means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to media communication for wearable devices). Information can be passed on to other components of the device 1105. The receiver 1110 can utilize a single antenna or a set of multiple antennas.

[0156] The transmitter 1115 can provide means for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 can transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to media communication for wearable devices). In some examples, the transmitter 1115 can be collocated with the receiver 1110 in a transceiver module. The transmitter 1115 can utilize a single antenna or a set of multiple antennas.

[0157] The communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof or various components thereof can be examples of means for performing various aspects of media communication for wearable devices as described herein. For example, the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof can be capable of performing one or more of the functions described herein.

[0158] In some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof can be implemented in hardware (e.g., in communications management circuitry). The hardware can include at least one of the following: a processor, a digital signal processor (DSP), a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, a microcode controller, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof. In some examples, at least one processor and at least one memory coupled with the at least one processor can be configured to perform one or more of the functions described herein (e.g., the at least one processor executing instructions stored in the at least one memory).

[0159] Additionally or alternatively, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof can be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functions of the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof can be executed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting the components for performing the functions described in this disclosure).

[0160] In some examples, the communication manager 1120 can be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1110, the transmitter 1115, or both. For example, the communication manager 1120 can receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated in combination with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0161] According to examples as disclosed herein, the communication manager 1120 can support wireless communication at a UE. For example, the communication manager 1120 can enable, be configured as, or be operable to support means for initiating, at a UE, a first conversational flow for a first wearable device via a wireless connection between the UE and the first wearable device, where the first conversational flow is associated with a second conversational flow for a second wearable device. The communication manager 1120 can enable, be configured as, or be operable to support means for receiving, via the first conversational flow, a set of information associated with a user of the first wearable device. The communication manager 1120 can enable, be configured as, or be operable to support means for receiving, via the second conversational flow, a set of information associated with a user of the second wearable device. The communication manager 1120 can enable, be configured as, or be operable to support means for transmitting, via the first conversational flow, a first media content stream to the first wearable device. The communication manager 1120 can enable, be configured as, or be operable to support means for transmitting, via the second conversational flow, a second media content stream to the second wearable device in coordination with the first media content stream.

[0162] By including or configuring the communication manager 1120 in accordance with examples as described herein, the device 1105 (e.g., a control receiver 1110, a transmitter 1115, the communication manager 1120, or a combination or otherwise of at least one processor coupled therewith) can support techniques for first and second wearable devices initiating media sessions with a UE and an end device, which can reduce processing, lower power consumption, increase signaling throughput, and reduce latency.

[0163] Figure 12 A block diagram 1200 of a device 1205 that supports media communication for wearable devices is shown, in accordance with one or more aspects of the present disclosure. The device 1205 can be an example of aspects of a device 1105 or a UE 115 as described herein. The device 1205 can include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205, or one or more components of the device 1205 (e.g., the receiver 1210, the transmitter 1215, and the communication manager 1220), can include at least one processor that can be coupled to at least one memory to support the described techniques. Each of these components can be in communication with one another (e.g., via one or more buses).

[0164] The receiver 1210 can provide means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to media communication for wearable devices). Information can be passed on to other components of the device 1205. The receiver 1210 can utilize a single antenna or a set of multiple antennas.

[0165] The transmitter 1215 can provide a means for transmitting signals generated by other components of the device 1205. For example, the transmitter 1215 can transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to media communication for a wearable device). In some examples, the transmitter 1215 can be collocated with the receiver 1210 in a transceiver module. The transmitter 1215 can utilize a single antenna or a set of multiple antennas.

[0166] The device 1205 or its various components can be an example of means for performing various aspects of media communication for a wearable device as described herein. The communication manager 1220 can include a session stream initiation component 1225, a user information reception component 1230, a media content transmission component 1235, or any combination thereof. The communication manager 1220 can be an example of aspects of the communication manager 1120 as described herein. In some examples, the communication manager 1220 or various components thereof can be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or in cooperation with the receiver 1210, the transmitter 1215, or both. For example, the communication manager 1220 can receive information from the receiver 1210, transmit information to the transmitter 1215, or be integrated in combination with the receiver 1210, the transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0167] According to examples as disclosed herein, the communication manager 1220 can support wireless communication at a UE. The session stream initiation component 1225 can enable, be configured as, or be operable to support means for initiating, at the UE, a first session stream for a first wearable device via a wireless connection between the UE and the first wearable device, where the first session stream is associated with a second session stream for a second wearable device. The user information reception component 1230 can enable, be configured as, or be operable to support means for receiving, via the first session stream, a set of information associated with a user of the first wearable device. The user information reception component 1230 can enable, be configured as, or be operable to support means for receiving, via the second session stream, a set of information associated with a user of the second wearable device. The media content transmission component 1235 can enable, be configured as, or be operable to support means for transmitting, to the first wearable device via the first session stream, a first media content stream. The media content transmission component 1235 can enable, be configured as, or be operable to support means for transmitting, to the second wearable device via the second session stream, a second media content stream in coordination with the first media content stream.

[0168] Figure 13A block diagram 1300 illustrating the communication manager 1320 that supports media communication for wearable devices in accordance with one or more aspects of the present disclosure is shown. The communication manager 1320 can be an example of aspects of a communication manager 1120, a communication manager 1220, or both, as described herein. The communication manager 1320, or various components thereof, can be an example of means for performing various aspects of media communication for wearable devices as described herein. For example, the communication manager 1320 can include a session flow initiation component 1325, a user information reception component 1330, a media content transmission component 1335, a user information transmission component 1340, a media content reception component 1345, a wearable device capability component 1350, an SDP offer component 1355, an SDP answer component 1360, a differential media content component 1365, or any combination thereof. Each of these components, or components or sub-components thereof (e.g., one or more processors, one or more memories), can be in communication with one another directly or indirectly (e.g., via one or more buses).

[0169] According to examples as disclosed herein, the communication manager 1320 can support wireless communications at a UE. The session flow initiation component 1325 can enable, be configured as, or be operable to support means for initiating a first session flow for a first wearable device via a wireless connection between the UE and the first wearable device, where the first session flow is associated with a second session flow for a second wearable device. The user information reception component 1330 can enable, be configured as, or be operable to support means for receiving a set of information associated with a user of the first wearable device via the first session flow. In some examples, the user information reception component 1330 can enable, be configured as, or be operable to support means for receiving a set of information associated with a user of the second wearable device via the second session flow. The media content transmission component 1335 can enable, be configured as, or be operable to support means for transmitting a first media content stream to the first wearable device via the first session flow. In some examples, the media content transmission component 1335 can enable, be configured as, or be operable to support means for transmitting a second media content stream to the second wearable device via the second session flow in coordination with the first media content stream.

[0170] In some examples, the user information transmission component 1340 can enable, be configured as, or be operable to support means for transmitting a set of aggregated information to the terminal device, the set of information aggregating including the set of information associated with the user of the first wearable device and a second set of information associated with the user of the second wearable device. In some examples, the media content reception component 1345 can enable, be configured as, or be operable to support means for receiving aggregated media content associated with the first media content stream and the second media content stream from the terminal device.

[0171] In some examples, to support sending the first media content stream, the media content sending component 1335 is capable of, configured to, or operable to support means for sending the first media content stream via the first stream, where the first media content stream comprises one of a baseline version or a differential version defined relative to the baseline version.

[0172] In some examples, the second media content stream is associated with a second version of the media content, the second version comprising the other of the baseline version or the differential version.

[0173] In some examples, the baseline version is multicast to the first wearable device and the second wearable device, and the differential version is unicast to one of the first wearable device or the second wearable device.

[0174] In some examples, the media content receiving component 1345 is capable of, configured to, or operable to support means for receiving an indication of the baseline version and the differential version from the end device.

[0175] In some examples, the media content receiving component 1345 is capable of, configured to, or operable to support means for receiving an indication of the baseline version and a second version of the media content from the end device. In some examples, the differential media content component 1365 is capable of, configured to, or operable to support means for generating the differential version based on receiving the indication.

[0176] In some examples, to support sending the first media content stream, the media content sending component 1335 is capable of, configured to, or operable to support means for sending the baseline version to the first wearable device via a first unicast message. In some examples, to support sending the first media content stream, the media content sending component 1335 is capable of, configured to, or operable to support means for sending the second version of the media content to the second wearable device via a second unicast message.

[0177] In some examples, to support initiating the first session flow, the wearable device capability component 1350 can include, be configured as, or be operable as, means for receiving, from the first wearable device, a first capability message indicating a capability of the first wearable device to receive the first media content stream. In some examples, to support initiating the first session flow, the wearable device capability component 1350 can include, be configured as, or be operable as, means for receiving, from the second wearable device, a second capability message indicating a capability of the second wearable device to receive the second media content stream. In some examples, to support initiating the first session flow, the SDP offer component 1355 can include, be configured as, or be operable as, means for sending, to the terminal device, an SDP offer message based on the first capability message and the second capability message. In some examples, to support initiating the first session flow, the SDP answer component 1360 can include, be configured as, or be operable as, means for receiving, from the terminal device, an SDP answer message based on the SDP offer message.

[0178] In some examples, the first session flow and the second session flow are associated with a same session between the UE and the terminal device. In some examples, the set of information associated with the user includes one or more of pose information and eye tracking information. In some examples, the first wearable device and the second wearable device are contact lenses. In some examples, the media content includes a rendered video for coordinated display by the first wearable device and the second wearable device.

[0179] Figure 14 A diagram illustrates a system 1400 including a device 1405 that supports media communication for wearable devices in accordance with one or more aspects of the present disclosure. The device 1405 can be an example of or include the components of a device 1105, a device 1205, or a UE 115 as described herein. The device 1405 can communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 1405 can include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1420, an input / output (I / O) controller 1410, a transceiver 1415, an antenna 1425, at least one memory 1430, code 1435, and at least one processor 1440. These components can be in electronic communication or otherwise

[0180] I / O controller 1410 manages the input and output signals of device 1405. I / O controller 1410 can also manage peripheral devices not integrated into device 1405. In some cases, I / O controller 1410 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1410 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, it may be another known operating system. Additionally or alternatively, the I / O controller 1410 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1410 may be implemented as part of a processor, such as processor 1440. In some cases, a user may interact with device 1405 via the I / O controller 1410 or via hardware components controlled by the I / O controller 1410.

[0181] In some cases, device 1405 may include a single antenna 1425. However, in other cases, device 1405 may have more than one antenna 1425, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1415 may communicate bidirectionally via one or more antennas 1425 as described herein, or via a wired or wireless link. For example, transceiver 1415 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1415 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1425 for transmission; and demodulating packets received from one or more antennas 1425. Transceiver 1415, or transceiver 1415 and one or more antennas 1425, may be an example of transmitter 1115, transmitter 1215, receiver 1110, receiver 1210, or any combination thereof or components thereof as described herein.

[0182] Memory 1430 can include random access memory (RAM) and read only memory (ROM). The memory 1430 can store computer-readable, computer-executable code 1435 including instructions that, when executed by the processor 1440, cause the device 1405 to perform various functions described herein. The code 1435 can be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1435 can not be directly executable by the processor 1440 but can cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory 1430 can include, among other things, a basic I / O system (BIOS), which can control basic hardware or software operation such as the interaction with peripheral components or devices.

[0183] The processor 1440 can include an intelligent hardware device, (e.g., a general- purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1440 can be configured to operate with a memory array, which can include a memory controller. In some other cases, a memory controller can be integrated into the processor 1440. The processor 1440 can be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1430) to cause the device 1405 to perform various functions (e.g., functions or tasks supporting media communication for a wearable device). For example, the device 1405 or a component of the device 1405 can include the processor 1440 and the memory 1430 coupled with or to the processor 1440, the processor 1440 and the memory 1430 being configured to perform various functions described herein.

[0184] According to examples as disclosed herein, the communications manager 1420 can support wireless communication at a UE. For example, the communications manager 1420 can be, be configured as, or be operable to support a means for initiating, at a UE, a first session flow for a first wearable device via a wireless connection between the UE and the first wearable device, where the first session flow is associated with a second session flow for a second wearable device. The communications manager 1420 can be, be configured as, or be operable to support a means for receiving, via the first session flow, a set of information associated with a user of the first wearable device. The communications manager 1420 can be, be configured as, or be operable to support a means for receiving, via the second session flow, a set of information associated with a user of the second wearable device. The communications manager 1420 can be, be configured as, or be operable to support a means for transmitting, via the first session flow, a first media content stream to the first wearable device. The communications manager 1420 can be, be configured as, or be operable to support a means for transmitting, via the second session flow, a second media content stream to the second wearable device in coordination with the first media content stream.

[0185] By including or configuring the communications manager 1420 in accordance with examples as described herein, the device 1405 can support techniques for first and second wearable devices to initiate media sessions with a UE and an end device, which can improve communication reliability, reduce latency, improve user experience related to processing reduction, reduce power consumption, and improve coordination between devices.

[0186] In some examples, the communications manager 1420 can be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1415, the one or more antennas 1425, or any combination thereof. Although the communications manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1420 can be supported by, or performed by, the processor 1440, the memory 1430, the code 1435, or any combination thereof. For example, the code 1435 can include instructions executable by the processor 1440 to cause the device 1405 to perform various aspects of media communication for wearable devices as described herein, or the processor 1440 and the memory 1430 can be otherwise configured to support or perform such operations.

[0187] Figure 15 A flow diagram illustrating a method 1500 that supports media communication for wearable devices in accordance with aspects of the present disclosure is shown. The operations of method 1500 can be implemented by a wearable device or its components as described herein. For example, the operations of method 1500 can be performed by a wearable device as described with reference to FIGs. 1-14, 17, and 18 A-18C by a processor 1440, a communications manager 1420, or any combination thereof. For example, the communications manager 1420 can support carrier aggregation for wearable devices as described herein. Figures 1 to 10The described wearable device performs. In some examples, the wearable device can execute a set of instructions to control the functional elements of the wearable device to perform the described functions. Additionally or alternatively, the wearable device can use special-purpose hardware to perform aspects of the described functions.

[0188] At 1505, the method can include initiating a first session flow via a wireless connection between the first wearable device and the UE, where the first session flow is associated with a second session flow for a second wearable device. The operations of block 1505 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1505 can be performed by a session flow initiation manager 925 as described with reference to Figure 9 to the described session flow initiation manager 925.

[0189] At 1510, the method can include sending a set of information associated with a user of the first wearable device via the first session flow. The operations of block 1510 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1510 can be performed by a user information manager 930 as described with reference to Figure 9 to the described user information manager 930.

[0190] At 1515, the method can include receiving a first media content stream via the first session flow and a second media content stream via the second session flow in coordination. The operations of block 1515 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1515 can be performed by a media content manager 935 as described with reference to Figure 9 to the described media content manager 935.

[0191] Figure 16 A flow diagram illustrating a method 1600 that supports media communication for wearable devices in accordance with aspects of the present disclosure is shown. The operations of method 1600 can be implemented by a wearable device or its components as described herein. For example, the operations of method 1600 can be performed by a wearable device as described with reference to Figures 1 to 10 The described wearable device performs. In some examples, the wearable device can execute a set of instructions to control the functional elements of the wearable device to perform the described functions. Additionally or alternatively, the wearable device can use special-purpose hardware to perform aspects of the described functions.

[0192] At 1605, the method can include initiating a first session flow via a wireless connection between the first wearable device and the UE, where the first session flow is associated with a second session flow for a second wearable device. The operations of block 1605 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1605 can be performed by a session flow initiation manager 925 as described with reference to Figure 9 to the described session flow initiation manager 925.

[0193] At 1610, the method may include sending a set of information associated with a user of the first wearable device via a first session stream. Operation of block 1610 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1610 may be provided by reference to [reference needed]. Figure 9 The user information manager 930 described is executed.

[0194] At 1615, the method may include receiving a first media content stream via a first session stream and coordinatingly receiving a second media content stream via a second session stream. The operation of block 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1615 may be derived from references... Figure 9 The described Media Content Manager 935 is executed.

[0195] At 1620, the method may include receiving a first version of media content via a first session stream through a first media content stream, wherein the first version includes either a baseline version or a variant version defined relative to the baseline version. Operation of block 1620 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1620 may be derived from references... Figure 9 The described Media Content Manager 935 is executed.

[0196] Figure 17 A flowchart illustrating a method 1700 for supporting media communication for a wearable device according to various aspects of this disclosure is shown. Operation of method 1700 may be implemented by a wearable device or its components as described herein. For example, operation of method 1700 may be achieved by, as referenced... Figures 1 to 10 The described wearable device performs the functions described. In some examples, the wearable device can execute a set of instructions to control the functional elements of the wearable device to perform the described functions. Additionally or alternatively, the wearable device may use dedicated hardware to perform aspects of the described functions.

[0197] At 1705, the method may include initiating a first session stream via a wireless connection between a first wearable device and a UE, wherein the first session stream is associated with a second session stream for a second wearable device. Operation of block 1705 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1705 may be provided by reference to [reference needed]. Figure 9 The described session flow initiation manager 925 is executed.

[0198] At 1710, the method may include sending a set of information associated with a user of the first wearable device via a first session stream. Operation of block 1710 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1710 may be provided by reference to [reference needed]. Figure 9 The user information manager 930 described is executed.

[0199] At 1715, the method may include receiving a first media content stream via a first session stream and coordinatingly receiving a second media content stream via a second session stream. The operation of block 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1715 may be derived from references... Figure 9 The described Media Content Manager 935 is executed.

[0200] At 1720, the method may include receiving a first version of media content via a first session stream through a first media content stream, wherein the first version includes either a baseline version or a variant version defined relative to the baseline version. The operation of box 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1720 may be provided by reference to [reference needed]. Figure 9 The described Media Content Manager 935 is executed.

[0201] At 1725, the method may include receiving a baseline version from the UE via a first unicast message, wherein a second version is sent to a second wearable device via a second unicast message. Operation of block 1725 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1725 may be provided by reference to [reference needed]. Figure 9 The described Media Content Manager 935 is executed.

[0202] Figure 18 A flowchart illustrating a method 1800 for supporting media communication for a wearable device according to various aspects of this disclosure is shown. Operation of method 1800 may be implemented by a UE or its components as described herein. For example, operation of method 1800 may be implemented by, as referenced... Figures 1 to 6 and Figures 11 to 14 The UE 115 described herein performs the following: In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0203] At 1805, the method may include initiating a first session stream for the first wearable device via a wireless connection between the UE and the first wearable device, wherein the first session stream is associated with a second session stream for the second wearable device. Operation of block 1805 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1805 may be provided by reference to [reference needed]. Figure 13 The described session flow initiation component 1325 is executed.

[0204] At 1810, the method may include receiving a set of information associated with a user of the first wearable device via a first session stream. Operation of block 1810 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1810 may be provided by reference to [reference needed].Figure 13 The user information receiving component 1330 described is executed.

[0205] At 1815, the method may include receiving a set of information associated with a user of the second wearable device via a second session stream. Operation of block 1815 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1815 may be provided by reference to [reference needed]. Figure 13 The user information receiving component 1330 described is executed.

[0206] At 1820, the method may include sending a first media content stream to a first wearable device via a first session stream. Operation of block 1820 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1820 may be provided by reference to [reference needed]. Figure 13 The described media content sending component 1335 is executed.

[0207] At 1825, the method may include transmitting a second media content stream to a second wearable device via a second session stream in coordination with the first media content stream. Operation of block 1825 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1825 may be provided by reference to [reference needed]. Figure 13 The described media content sending component 1335 is executed.

[0208] Figure 19 A flowchart illustrating a method 1900 for supporting media communication for a wearable device according to various aspects of this disclosure is shown. Operation of method 1900 may be implemented by a UE or its components as described herein. For example, operation of method 1900 may be implemented by, as referenced... Figures 1 to 6 and Figures 11 to 14 The UE 115 described herein performs the following: In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0209] At 1905, the method may include initiating a first session stream for the first wearable device via a wireless connection between the UE and the first wearable device, wherein the first session stream is associated with a second session stream for the second wearable device. Operation of block 1905 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1905 may be provided by reference to [reference needed]. Figure 13 The described session flow initiation component 1325 is executed.

[0210] At 1910, the method may include receiving a set of information associated with a user of the first wearable device via a first session stream. Operation of block 1910 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1910 may be provided by reference to [reference needed].Figure 13 The user information receiving component 1330 described is executed.

[0211] At 1915, the method may include receiving a set of information associated with a user of the second wearable device via a second session stream. Operation of block 1915 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1915 may be provided by reference to [reference needed]. Figure 13 The user information receiving component 1330 described is executed.

[0212] At 1920, the method may include sending a set of aggregated information to a terminal device, the set of aggregated information including the set of information associated with a user of a first wearable device and a second set of information associated with a user of a second wearable device. The operation of block 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1920 may be provided by reference to [reference needed]. Figure 13 The user information sending component 1340 described is executed.

[0213] At 1925, the method may include receiving aggregated media content associated with a first media content stream and a second media content stream from a terminal device. The operation of block 1925 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1925 may be provided by reference to [reference needed]. Figure 13 The media content receiving component 1345 described is executed.

[0214] At 1930, the method may include sending a first media content stream to a first wearable device via a first session stream. The operation of block 1930 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1930 may be provided by reference to [reference needed]. Figure 13 The described media content sending component 1335 is executed.

[0215] At 1935, the method may include transmitting a second media content stream to a second wearable device via a second session stream in coordination with a first media content stream. Operation of block 1935 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1935 may be provided by reference to [reference needed]. Figure 13 The described media content sending component 1335 is executed.

[0216] Figure 20 A flowchart illustrating a method 2000 for supporting media communication for a wearable device according to various aspects of this disclosure is shown. Operation of method 2000 may be implemented by a UE or its components as described herein. For example, operation of method 2000 may be implemented by, as referenced... Figures 1 to 6 and Figures 11 to 14The UE 115 described herein performs the following: In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0217] In 2005, the method may include initiating a first session stream for the first wearable device via a wireless connection between the UE and the first wearable device, wherein the first session stream is associated with a second session stream for a second wearable device. Operation of block 2005 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2005 may be provided by reference to [reference needed]. Figure 13 The described session flow initiation component 1325 is executed.

[0218] At 2010, the method may include receiving a set of information associated with a user of the first wearable device via a first session stream. Operation of block 2010 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2010 may be provided by reference to [reference needed]. Figure 13 The user information receiving component 1330 described is executed.

[0219] At 2015, the method may include receiving a set of information associated with a user of a second wearable device via a second session stream. Operation of block 2015 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2015 may be provided by reference to [reference needed]. Figure 13 The user information receiving component 1330 described is executed.

[0220] At 2020, the method may include sending a set of aggregated information to a terminal device, the set of aggregated information including the set of information associated with a user of a first wearable device and a second set of information associated with a user of a second wearable device. The operation of box 2020 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2020 may be provided by reference to [reference needed]. Figure 13 The user information sending component 1340 described is executed.

[0221] At point 2025, the method may include receiving aggregated media content associated with a first media content stream and a second media content stream from a terminal device. The operation of block 2025 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2025 may be provided by reference to [reference needed]. Figure 13 The media content receiving component 1345 described is executed.

[0222] At 2030, the method may include sending a first media content stream to a first wearable device via a first session stream. The operation of block 2030 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2030 may be provided by reference to [reference needed].Figure 13 The described media content sending component 1335 is executed.

[0223] At point 2035, the method may include sending a first version of media content via a first media content stream, wherein the first version includes either a baseline version or a variant version defined relative to the baseline version. The operation of block 2035 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2035 may be provided by reference to [reference needed]. Figure 13 The described media content sending component 1335 is executed.

[0224] At 2040, the method may include sending a second media content stream to a second wearable device via a second session stream in coordination with the first media content stream. Operation of block 2040 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2040 may be provided by reference to [reference needed]. Figure 13 The described media content sending component 1335 is executed.

[0225] The following provides an overview of the various aspects of this disclosure:

[0226] Aspect 1: A method for wireless communication at a first wearable device, the method comprising: initiating a first session stream via a wireless connection between the first wearable device and a UE, wherein the first session stream is associated with a second session stream for a second wearable device; transmitting a set of information associated with a user of the first wearable device via the first session stream; and receiving a first media content stream via the first session stream and coordinatingly receiving a second media content stream via the second session stream.

[0227] Aspect 2: According to the method of aspect 1, receiving the first media content stream includes: receiving a first version of the media content via the first session stream via the first media content stream, wherein the first version includes either a baseline version or a differential version defined relative to the baseline version.

[0228] Aspect 3: According to the method of aspect 2, wherein the second media content stream is associated with a second version of the media content, the second version including the baseline version or the difference version.

[0229] Aspect 4: The method according to any one of Aspects 2 to 3, wherein the baseline version is multicast to the first wearable device and the second wearable device, and the differential version is unicast to one of the first wearable device or the second wearable device.

[0230] Aspect 5: The method according to any one of Aspects 2 to 3, wherein receiving the first media content stream comprises: receiving the baseline version from the UE via a first unicast message, wherein the second version is sent to the second wearable device via a second unicast message.

[0231] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the first session stream and the second session stream are associated with the same session between the UE and the terminal device.

[0232] Aspect 7: The method according to any one of Aspects 1 to 5, wherein the first session stream is associated with a first session of the terminal device, and the first session is different from the second session of the terminal device associated with the second session stream.

[0233] Aspect 8: The method according to any one of Aspects 1 to 7, wherein initiating the first session stream includes one or both of the following operations: sending a capability message to the UE indicating the capability of the first wearable device to receive the first media content stream; sending an SDP provision message to the terminal device, and receiving an SDP response message from the terminal device based at least in part on the SDP provision message.

[0234] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the set of information associated with the user includes one or more of gesture information and eye-tracking information.

[0235] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the first wearable device and the second wearable device are contact lenses.

[0236] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the media content includes a rendered video for coordinated display by the first wearable device and the second wearable device.

[0237] Aspect 12: A method for wireless communication at a UE, the method comprising: initiating a first session stream for the first wearable device via a wireless connection between the UE and the first wearable device, wherein the first session stream is associated with a second session stream for the second wearable device; receiving a set of information associated with a user of the first wearable device via the first session stream; receiving a set of information associated with a user of the second wearable device via the second session stream; transmitting a first media content stream to the first wearable device via the first session stream; and transmitting a second media content stream to the second wearable device in coordination with the first media content stream via the second session stream.

[0238] Aspect 13: According to the method of aspect 12, the method further includes: sending a set of aggregated information to a terminal device, the set of aggregated information including the set of information associated with the user of the first wearable device and the second set of information associated with the user of the second wearable device; and receiving aggregated media content associated with the first media content stream and the second media content stream from the terminal device.

[0239] Aspect 14: According to the method of aspect 13, sending the first media content stream includes: sending a first version of the media content via the first stream, wherein the first version includes either a baseline version or a differential version defined relative to the baseline version.

[0240] Aspect 15: According to the method of aspect 14, wherein the second media content stream is associated with a second version of the media content, the second version including the baseline version or the difference version.

[0241] Aspect 16: The method according to any one of Aspects 14 to 15, wherein the baseline version is multicast to the first wearable device and the second wearable device, and the difference version is unicast to one of the first wearable device or the second wearable device.

[0242] Aspect 17: The method according to any one of Aspects 14 to 16, the method further comprising: receiving from the terminal device an indication of the baseline version and the difference version.

[0243] Aspect 18: The method according to any one of Aspects 14 to 17, the method further comprising: receiving from the terminal device an indication of the baseline version and a second version of the media content; and generating the difference version at least in part based on receiving the indication.

[0244] Aspect 19: The method according to any one of Aspects 14 to 15, wherein sending the first media content stream comprises: sending the baseline version to the first wearable device via a first unicast message; and sending a second version of the media content to the second wearable device via a second unicast message.

[0245] Aspect 20: The method according to any one of Aspects 12 to 19, wherein initiating the first session stream comprises: receiving from the first wearable device a first capability message indicating the ability of the first wearable device to receive the first media content stream; receiving from the second wearable device a second capability message indicating the ability of the second wearable device to receive the second media content stream; sending an SDP provision message to a terminal device at least in part based on the first capability message and the second capability message; and receiving an SDP response message from the terminal device at least in part based on the SDP provision message.

[0246] Aspect 21: The method according to any one of Aspects 12 to 20, wherein the first session stream and the second session stream are associated with the same session between the UE and the terminal device.

[0247] Aspect 22: The method according to any one of aspects 12 to 21, wherein the set of information associated with the user includes one or more of posture information and eye-tracking information.

[0248] Aspect 23: The method according to any one of Aspects 12 to 22, wherein the first wearable device and the second wearable device are contact lenses.

[0249] Aspect 24: The method according to any one of Aspects 12 to 23, wherein the media content includes a rendered video for coordinated display by the first wearable device and the second wearable device.

[0250] Aspect 25: An apparatus for wireless communication at a first wearable device, the apparatus comprising: at least one processor; at least one memory coupled to the at least one processor; and instructions stored in the at least one memory and executable by the at least one processor to cause the apparatus to perform a method according to any one of aspects 1 to 11.

[0251] Aspect 26: An apparatus for wireless communication at a first wearable device, the apparatus comprising at least one component for performing the method according to any one of aspects 1 to 11.

[0252] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication at a first wearable device, the code including instructions executable by at least one processor to perform the method according to any one of aspects 1 to 11.

[0253] Aspect 28: An apparatus for wireless communication at a UE, the apparatus comprising: at least one processor; at least one memory coupled to the at least one processor; and instructions stored in the at least one memory and executable by the at least one processor to cause the apparatus to perform a method according to any one of aspects 12 to 24.

[0254] Aspect 29: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 12 to 24.

[0255] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by at least one processor to perform the method according to any one of aspects 12 to 24.

[0256] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0257] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0258] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0259] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0260] The functionality described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functionality can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functionality described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functionality can also be physically located in various locations, including portions distributed such that the functionality is implemented at different physical locations.

[0261] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0262] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0263] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and subsequent reference to “the component” in a claim may be understood to be equivalent to referring to “at least one of the one or more components.”

[0264] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, building, and other similar actions.

[0265] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0266] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0267] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a first wearable device, the apparatus comprising: At least one processor; At least one memory, said at least one memory being coupled to said at least one processor; and Instructions, which are stored in the at least one memory and can be executed by the at least one processor, to cause the device to: A first session stream is initiated via a wireless connection between the first wearable device and the user equipment (UE), wherein the first session stream is associated with a second session stream for the second wearable device; A set of information associated with the user of the first wearable device is sent via the first session stream; as well as Receive a first media content stream via the first session stream and coordinately receive a second media content stream via the second session stream.

2. The apparatus of claim 1, wherein the instruction for receiving the first media content stream is executable by the at least one processor to cause the apparatus to: A first version of the media content is received via the first session stream via the first media content stream, wherein the first version includes either a baseline version or a differential version defined relative to the baseline version.

3. The apparatus of claim 2, wherein the second media content stream is associated with a second version of the media content, the second version including the baseline version or the differential version.

4. The apparatus of claim 2, wherein the baseline version is multicast to the first wearable device and the second wearable device, and the differential version is unicast to one of the first wearable device or the second wearable device.

5. The apparatus of claim 2, wherein the instruction for receiving the first media content stream is executable by the at least one processor to cause the apparatus to: The baseline version is received from the UE via a first unicast message, wherein the second version is sent to the second wearable device via a second unicast message.

6. The apparatus of claim 1, wherein the first session stream and the second session stream are associated with the same session between the UE and the terminal device.

7. The apparatus of claim 1, wherein the first session stream is associated with a first session of the terminal device, and wherein the first session is different from the second session of the terminal device associated with the second session stream.

8. The apparatus of claim 1, wherein the instructions for initiating the first session stream are executable by the at least one processor to cause the apparatus to: Send a capability message to the UE instructing the first wearable device to receive the first media content stream; or Send a Session Description Protocol (STP) Provide message to a terminal device, and receive a STP Response message from the terminal device based at least in part on the STP Provide message.

9. The apparatus of claim 1, wherein the set of information associated with the user includes one or more of gesture information and eye-tracking information.

10. The apparatus of claim 1, wherein the first wearable device and the second wearable device are contact lenses.

11. The apparatus of claim 1, wherein the media content includes rendered video for coordinated display by the first wearable device and the second wearable device.

12. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one processor; At least one memory, said at least one memory being coupled to said at least one processor; and Instructions, which are stored in the at least one memory and can be executed by the at least one processor, to cause the device to: A first session stream for the first wearable device is initiated via a wireless connection between the UE and the first wearable device, wherein the first session stream is associated with a second session stream for the second wearable device; Receive a set of information associated with the user of the first wearable device via the first session stream; Receive a set of information associated with the user of the second wearable device via the second session stream; Send a first media content stream to the first wearable device via the first session stream; as well as The second media content stream is sent to the second wearable device via the second session stream in coordination with the first media content stream.

13. The apparatus of claim 12, wherein the instructions are further executable by the at least one processor to cause the apparatus to: Send a set of aggregated information to the terminal device, the set of aggregated information including a set of information associated with the user of the first wearable device and a second set of information associated with the user of the second wearable device; and Receive aggregated media content associated with the first media content stream and the second media content stream from the terminal device.

14. The apparatus of claim 13, wherein the instruction for transmitting the first media content stream is executable by the at least one processor to cause the apparatus to: A first version of the media content is sent via the first stream via the first media content stream, wherein the first version includes either a baseline version or a differential version defined relative to the baseline version.

15. The apparatus of claim 14, wherein the second media content stream is associated with a second version of the media content, the second version including the baseline version or the difference version.

16. The apparatus of claim 14, wherein the baseline version is multicast to the first wearable device and the second wearable device, and the differential version is unicast to one of the first wearable device or the second wearable device.

17. The apparatus of claim 14, wherein the instructions are further executable by the at least one processor to cause the apparatus to: Receive instructions on the baseline version and the difference version from the terminal device.

18. The apparatus of claim 14, wherein the instructions are further executable by the at least one processor to cause the apparatus to: Receive instructions from the terminal device regarding the baseline version and a second version of the media content; and The difference version is generated at least in part based on receiving the instruction.

19. The apparatus of claim 14, wherein the instruction for transmitting the first media content stream is executable by the at least one processor to cause the apparatus to: The baseline version is sent to the first wearable device via a first unicast message; and A second version of the media content is sent to the second wearable device via a second unicast message.

20. The apparatus of claim 12, wherein the instructions for initiating the first session stream are executable by the at least one processor to cause the apparatus to: Receive a first capability message from the first wearable device instructing the first wearable device to receive the first media content stream; Receive a second capability message from the second wearable device instructing the second wearable device to receive the second media content stream; At least in part, a Session Description Protocol (STP) provision message is sent to the terminal device based on the first capability message and the second capability message; as well as The terminal device receives a Session Description Protocol (STP) response message, at least in part, based on the STP.

21. The apparatus of claim 12, wherein the first session stream and the second session stream are associated with the same session between the UE and the terminal device.

22. The apparatus of claim 12, wherein the set of information associated with the user includes one or more of gesture information and eye-tracking information.

23. The apparatus of claim 12, wherein the first wearable device and the second wearable device are contact lenses.

24. The apparatus of claim 12, wherein the media content includes rendered video for coordinated display by the first wearable device and the second wearable device.

25. A method for wireless communication at a first wearable device, the method comprising: A first session stream is initiated via a wireless connection between the first wearable device and the user equipment (UE), wherein the first session stream is associated with a second session stream for the second wearable device; A set of information associated with the user of the first wearable device is sent via the first session stream; as well as Receive a first media content stream via the first session stream and coordinately receive a second media content stream via the second session stream.

26. The method of claim 25, wherein receiving the first media content stream comprises: A first version of the media content is received via the first session stream via the first media content stream, wherein the first version includes either a baseline version or a differential version defined relative to the baseline version.

27. The method of claim 26, wherein the second media content stream is associated with a second version of the media content, the second version including the baseline version or the differential version.

28. A method for conducting wireless communication at a user equipment (UE), the method comprising: A first session stream for the first wearable device is initiated via a wireless connection between the UE and the first wearable device, wherein the first session stream is associated with a second session stream for the second wearable device; Receive a set of information associated with the user of the first wearable device via the first session stream; Receive a set of information associated with the user of the second wearable device via the second session stream; Send a first media content stream to the first wearable device via the first session stream; as well as The second media content stream is sent to the second wearable device via the second session stream in coordination with the first media content stream.

29. The method according to claim 28, further comprising: Send a set of aggregated information to the terminal device, the set of aggregated information including the set of information associated with the user of the first wearable device and the second set of information associated with the user of the second wearable device; as well as Receive aggregated media content associated with the first media content stream and the second media content stream from the terminal device.

30. The method of claim 29, wherein sending the first media content stream comprises: A first version of the media content is sent via the first stream via the first media content stream, wherein the first version includes either a baseline version or a differential version defined relative to the baseline version.

Images