EP4662559A1

EP4662559A1 - Methods, architectures, apparatuses and systems for artificial intelligence based alter ego functionality in a communications system

Info

Publication number: EP4662559A1
Application number: EP24713067.7A
Authority: EP
Inventors: Michael Starsinic; Xavier De Foy; Magurawalage Chathura Madhusanka Sarathchandra; Achref METHENNI; Rocco Di Girolamo; Stephane Onno; Samir Ferdi
Original assignee: InterDigital Patent Holdings Inc
Current assignee: InterDigital Patent Holdings Inc
Priority date: 2023-02-09
Filing date: 2024-02-08
Publication date: 2025-12-17
Also published as: WO2024168121A1; CN120660074A

Abstract

Procedures, methods, architectures, apparatuses, systems, devices, and computer program products for implementing artificial intelligence (Al) based alter ego functionality in a communications system are described. A method may include receiving, by a server, a request to instantiate an alter ego from an Al user equipment (UE) enabler, the request indicating an application identifier (ID) and an application type. The method may also include determining an alter ego server based on the application type, sending an instantiate command to the determined alter ego server, receiving an alter ego ID from the alter ego server, and sending a notification to the Al UE enabler. The notification may indicate the alter ego ID and a contact uniform resource identifier (URI) that is associated with the alter ego.

Description

METHODS, ARCHITECTURES, APPARATUSES AND SYSTEMS FOR ARTIFICIAL INTELLIGENCE BASED ALTER EGO FUNCTIONALITY IN A COMMUNICATIONS SYSTEM

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application Nos. (i) 63/444,494 filed February 9, 2023 and (ii) 63/444,491 filed February 9, 2023; each of which is incorporated herein by reference in its entirety.

FIELD

[0002] Example embodiments may be generally directed to the fields of communications, software and encoding, including, for example, to methods, architectures, apparatuses, and/or systems related to artificial intelligence (Al) based alter ego functionality in a communications system, such as a 5G system.

BACKGROUND

[0003] A communications system may be capable of providing content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. A communications system may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail (ZT) unique-word (UW) discreet Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

SUMMARY

[0004] An embodiment may be directed to an apparatus that may include circuitry including any of a processor, memory, transmitter and/or receiver. The circuitry may be configured to receive, from a WTRU enabler associated with the WTRU, a first request to instantiate a service to be performed on behalf of a wireless transmit/receive unit (WTRU). The first request may include an indication of an application type and information about resources of the WTRU that can be shared with one or more service servers. The circuitry may be configured to select a service server based on the application type and to send a second request to instantiate the service on the service server. The second request may indicate the information about the resources of the WTRU that can be shared with the service servers. The circuitry may be configured to receive, from the service server, a message confirming that the service has been instantiated, and to send a notification to the WTRU enabler. The notification may indicate a contact uniform resource identifier (URI) that is associated with the service. The apparatus may be configured to act as a bootstrapping function in a security establishment procedure between the WTRU enabler and the service server.

[0005] An embodiment may be directed to a method that includes receiving, by an enabler server from a wireless transmit/receive unit (WTRU) enabler associated with a WTRU, a first request to instantiate a service to be performed on behalf of the WTRU. The first request may include an indication of an application type and information about resources of the WTRU that can be shared with one or more service servers. The method may include selecting a service server based on the application type and sending a second request to instantiate the service on the service server. The second request may indicate the information about the resources of the WTRU that can be shared with the service servers. The method may include receiving, from the service server, a message confirming that the service has been instantiated, and sending a notification to the WTRU enabler. The notification may indicate a contact uniform resource identifier (URI) that is associated with the service. The enabler server is configured to act as a bootstrapping function in a security establishment procedure between the WTRU enabler and the service server.

[0006] In an embodiment, the service may include an alter ego and the service server may include an alter ego server. In an embodiment, an identifier associated with the service may be received, and/or the notification sent to the WTRU enabler further indicates the identifier associated with the service.

[0007] In an embodiment, the first request may include any of an indication of an application identifier associated with an application hosted by the WTRU, information indicating which storage resources in the WTRU enabler should be mirrored in the apparatus, and/or information indicating which storage resources in the WTRU enabler should be linked in the apparatus (e.g., the enabler server).

[0008] In an embodiment, the second request may indicate copies of resources that are associated with the application identifier. In an embodiment, the second request may indicate links to resources associated with the application identifier.

[0009] In an embodiment, a configuration request may be received from the WTRU enabler, where the configuration request indicates any of a task description and task limitation associated with a task.

[0010] In an embodiment, a third request may be sent, to the service server, to initiate the task in accordance with any of the task description and the task limitation. [0011] In an embodiment, the resources of the WTRU may include storage resources configured to store application specific data associated with an application hosted on the WTRU.

[0012] An embodiment may be directed to an apparatus that may include circuitry, including any of a processor, memory, and/or transceiver. The circuitry may be configured to send first information indicating a request to an enabler server to instantiate an alter ego. The first information may indicate an application type and information about resources of the UE that can be shared with an alter ego server. The circuitry may be configured to receive an indication that the alter ego has been instantiated by the alter ego server. The indication may indicate a uniform resource identifier (URI) associated with the instantiated alter ego. The circuitry may be configured to receive second information indicating a request for the alter ego to execute a task, and to send configuration information to the enabler server. The configuration information may indicate a description of the task, limitations associated with the task, and notification triggers associated with the task. The circuitry may be configured to perform, using the URI, a security establishment procedure with the instantiated alter ego. The first information may further indicate an application instance identifier (ID) and application instance identifier (ID) links to resources of the apparatus, where the resources store information associated with the application instance identifier (ID).

[0013] An embodiment may be directed to a method, which may include sending, by a wireless transmit/receive unit (WTRU), first information indicating a request to an enabler server to instantiate an alter ego. The first information may indicate an application type and information about resources of the UE that can be shared with an alter ego server. The method may include receiving an indication that the alter ego has been instantiated by the alter ego server. The indication may indicate or include a uniform resource identifier (URI) associated with the instantiated alter ego. The method may include receiving second information indicating a request for the alter ego to execute a task, and sending configuration information to the enabler server. The configuration information may include or may indicate a description of the task, limitations associated with the task, and notification triggers associated with the task. The method may include performing, using the URI, a security establishment procedure with the instantiated alter ego. The first information may further indicate or include an application instance identifier (ID) and application instance identifier (ID) links to resources of the WTRU, where the resources store information associated with the application instance identifier (ID). BRIEF DESCRIPTION OF THE DRAWINGS

[0014] A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with drawings appended hereto. Figures in such drawings, like the detailed description, are examples. As such, the Figures (FIGs.) and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals ("ref.") in the FIGs. indicate like elements, and wherein: [0015] FIG. 1 A is a system diagram illustrating an example communications system;

[0016] FIG. IB is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A;

[0017] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A;

[0018] FIG. ID is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1 A;

[0019] FIG. 2 is a diagram illustrating an example alter ego service flow;

[0020] FIG. 3 is an example architecture illustrating alter ego functionality in a 5G system, according to an embodiment; and

[0021] FIG. 4 is an example signal flow diagram, according to an embodiment;

[0022] FIG. 5 is an example signal flow diagram, according to an embodiment;

[0023] FIG. 6 is an example signal flow diagram, according to an embodiment;

[0024] FIG. 7 is an example signal flow diagram, according to an embodiment;

[0025] FIG. 8 is an example signal flow diagram, according to an embodiment; and [0026] FIG. 9 is an example flow diagram of a method, according to an embodiment.

DETAILED DESCRIPTION

[0027] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and/or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed or otherwise provided explicitly, implicitly and/or inherently (collectively "provided") herein. Although various embodiments are described and/or claimed herein in which an apparatus, system, device, etc. and/or any element thereof carries out an operation, process, algorithm, function, etc. and/or any portion thereof, it is to be understood that any embodiments described and/or claimed herein assume that any apparatus, system, device, etc. and/or any element thereof is configured to carry out any operation, process, algorithm, function, etc. and/or any portion thereof.

[0028] The methods, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks. An overview of various types of wireless devices and infrastructure is provided with respect to FIGs. 1A-1D, where various elements of the network may utilize, perform, be arranged in accordance with and/or be adapted and/or configured for the methods, apparatuses and systems provided herein.

[0029] FIG. 1A is a system diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), singlecarrier FDMA (SC-FDMA), zero-tail (ZT) unique-word (UW) discreet Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block- filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0030] As shown in FIG. 1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104/113, a core network (CN) 106/115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a "station" and/or a "STA", may be configured to transmit and/or receive wireless signals and may include (or be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi- Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d, or any other WTRU mentioned or described herein, may be interchangeably referred to as a UE.

[0031] The communications systems 100 may also include a base station 114a and/or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d, e.g., to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 110, and/or the networks 112. By way of example, the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB), a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.

[0032] The base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each or any sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions.

[0033] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0034] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).

[0035] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE- Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).

[0036] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).

[0037] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).

[0038] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0039] The base station 114b in FIG. 1 A may be a wireless router, Home Node-B, Home eNode- B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any of a small cell, picocell or femtocell. As shown in FIG. 1 A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106/115.

[0040] The RAN 104/113 may be in communication with the CN 106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in FIG. 1 A, it will be appreciated that the RAN 104/113 and/or the CN 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/113 or a different RAT. For example, in addition to being connected to the RAN 104/113, which may be utilizing an NR radio technology, the CN 106/115 may also be in communication with another RAN (not shown) employing any of a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi radio technology.

[0041] The CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/114 or a different RAT.

[0042] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology. [0043] FIG. IB is a system diagram illustrating an example WTRU 102. As shown in FIG. IB, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other elements/peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0044] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. IB depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together, e.g., in an electronic package or chip.

[0045] The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in an embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In an embodiment, the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.

[0046] Although the transmit/receive element 122 is depicted in FIG. IB as a single element, the WTRU 102 may include any number of transmit/receive elements 122. For example, the WTRU 102 may employ MIMO technology. Thus, in an embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0047] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

[0048] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), readonly memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0049] The processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0050] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0051] The processor 118 may further be coupled to other elements/peripherals 138, which may include one or more software and/or hardware modules/units that provide additional features, functionality and/or wired or wireless connectivity. For example, the elements/peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (e.g., for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and/or augmented reality (VR/AR) device, an activity tracker, and the like. The elements/peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.

[0052] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the uplink (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the uplink (e.g., for transmission) or the downlink (e.g., for reception)).

[0053] FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0054] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0055] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink (UL) and/or downlink (DL), and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface. [0056] The CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the CN operator. [0057] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an SI interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.

[0058] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via the SI interface. The SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter-eNode-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0059] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0060] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.

[0061] Although the WTRU is described in FIGs. 1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

[0062] In representative embodiments, the other network 112 may be a WLAN.

[0063] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a distribution system (DS) or another type of wired/wireless network that carries traffic into and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802. l ie DLS or an 802.1 Iz tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an "ad-hoc" mode of communication.

[0064] When using the 802.1 lac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier sense multiple access with collision avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0065] High throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadj acent 20 MHz channel to form a 40 MHz wide channel.

[0066] Very high throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse fast fourier transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above-described operation for the 80+80 configuration may be reversed, and the combined data may be sent to a medium access control (MAC) layer, entity, etc. [0067] Sub 1 GHz modes of operation are supported by 802.1 laf and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.1 laf and 802.1 lah relative to those used in

802.1 In, and 802.1 lac. 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.1 lah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment,

802.1 lah may support meter type control/machine-type communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0068] WLAN systems, which may support multiple channels, and channel bandwidths, such as

802.1 In, 802.1 lac, 802.1 laf, and 802.1 lah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.1 lah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes. Carrier sensing and/or network allocation vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0069] In the United States, the available frequency bands, which may be used by 802.1 lah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.1 lah is 6 MHz to 26 MHz depending on the country code.

[0070] FIG. ID is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0071] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 180b may utilize beamforming to transmit signals to and/or receive signals from the WTRUs 102a, 102b, 102c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).

[0072] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., including a varying number of OFDM symbols and/or lasting varying lengths of absolute time).

[0073] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non- standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non- standalone configuration WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non- standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.

[0074] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards user plane functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and the like. As shown in FIG. ID, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0075] The CN 115 shown in FIG. ID may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and at least one Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

[0076] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b, e.g., to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and/or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.

[0077] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP -based, non-IP based, Ethernet-based, and the like.

[0078] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, e.g., to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

[0079] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. In an embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0080] In view of FIGs. 1 A-1D, and the corresponding description of FIGs. 1 A-1D, one or more, or all, of the functions described herein with regard to any of: WTRUs 102a-d, base stations 114a- b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a- b, SMFs 183a-b, DNs 185a-b, and/or any other element(s)/device(s) described herein, may be performed by one or more emulation elements/devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.

[0081] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.

[0082] The one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.

[0083] It is noted that, throughout example embodiments described herein, the terms “serving base station”, “base station”, “gNB”, collectively “gNB” may be used interchangeably to designate any network element such as, e.g., a network element acting as a serving base station. Embodiments described herein are not limited to gNBs and are applicable to any other type of base stations.

[0084] 3GPP TS 22.856 (“Feasibility Study on Localized Mobile Metaverse Services (Release 19); VO.3.0”) [1] describes an example use case where an Alter Ego Server uses Artificial Intelligence (Al) to behave as an Al-based digital representation of a physical user and acts autonomously on behalf of the physical user.

[0085] If the Alter Ego Server has access to information about the experiences and knowledge of the physical user, then the Alter Ego Server can autonomously perform operations on behalf of the physical user. Fig. 1 illustrates an example of an Alter Ego Service Flow. As illustrated in the example of FIG. 1, a real user (e.g., real user #1 and/or real user #2) can make a request to its respective alter ego (e.g., alter ego #1 or alter ego #2). The alter ego may access one or more application services (e.g., email, web meeting, etc.) and can report executed tasks to the real user. [0086] It is noted that, according to some embodiments, Alter Ego Functionality may refer to functionality that may utilize Al to autonomously perform tasks on behalf of a physical user (e.g., a real person). Additionally, the terms “Alter Ego Server” and “Alter Ego” may be used interchangeably in this disclosure.

[0087] 5G System Enhancements may be desired so that the system architecture provides UE Hosted Applications with easy access to Alter Ego Functionality. A benefit to hosting Alter Ego Functionality in the Mobile Network is that the Alter Ego Functionality would be able to leverage the infrastructure of the 5G System. For example, enhancements may be desired so that the authentication and authorization infrastructure of the 5G System may be leveraged by Alter Ego Functions in the network. As another example, enhancements may be desired so that the storage and compute infrastructure of the 5G System may be leveraged by Alter Ego Functions in the network.

[0088] Once an Alter Ego task is initiated, the 5G System should provide functionality and capabilities that enable configuring the Alter Ego Server so that the Alter Ego Server knows the limits of what data the Alter Ego Server may access, knows the limits of what operations it is authorized to perform, and/or how to obtain the information that is necessary to complete a task. [0089] As introduced above, Alter Ego Functionality may refer to functionality that uses Al to autonomously perform tasks on behalf of a physical user (e.g., a real person). Various example embodiments discussed herein describe how Alter Ego Functionality can be integrated into the 5G System and may leverage some functions that are already available in the 5G System.

[0090] Various embodiments may be directed to methods, architectures, apparatuses, and/or systems for implementing artificial intelligence (Al) based alter ego functionality in a 5G system. For example, an embodiment may include a server, such as an AI-Enabler server, including circuitry that may be configured to receive a request to instantiate an alter ego from a UE (e.g., from an AI-UE-Enabler in the UE). In an embodiment, the request may include an application identifier (or application instance identifier) and an application type.

[0091] According to some embodiments, the AI-Enabler server may be configured to determine an Alter Ego Server based on the application type, to send an instantiate command to the Alter Ego Server, to receive an Alter Ego identifier from the Alter Ego Server, and/or to send a notification to the UE (e.g., to the AI-UE Enabler). For example, the notification may include the Alter Ego identifier and a contact universal resource identifier (URI) that is associated with the Alter Ego.

[0092] In certain embodiments, the AI-Enabler server may be configured to participate in and/or perform a security establishment procedure with the UE, e.g., with the AI-UE Enabler, and the Alter Ego Server. According to certain embodiments, the request to instantiate an alter ego may include or may indicate copies of the resources that are associated with the application identifier. In an embodiment, the request to instantiate an alter ego may include or may indicate links to resources that are associated with the application identifier.

[0093] According to various embodiments, the AI-Enabler server may be configured to receive a configuration request from the UE (e.g., from the AI-UE Enabler). The configuration request may include and/or may indicate a task description, a task limitation, and/or a notification trigger. In an embodiment, the AI-Enabler server may be configured to send, to the Alter Ego Server, a request to initiate a task. The AI-Enabler server may be further configured to receive an information request from the Alter Ego Server. In an embodiment, the AI-Enabler server may be configured to send a reply message to the Alter Ego Server. The reply message may include or may indicate information, a link to information, and/or an indication that the requested information cannot be provided.

[0094] An embodiment may be directed to a service enabler in a UE, e.g., an AI-UE Enabler, that may include circuitry, processor(s), memory, and/or transceiver(s). In various embodiments, the AI-UE Enabler may be configured to receive an API request to instantiate an alter ego. According to an embodiment, the request may include and/or may indicate an application identifier (or application instance identifier and/or an application type.

[0095] In some embodiments, the AI-UE Enabler may be configured to send a request to a server to instantiate an Alter Ego. According to an embodiment, the request may include and/or may indicate the application identifier (e.g., application instance identifier) and/or links to resources of the AI-UE-Enabler. The resources may store information that relates to the application identifier (e.g., application instance identifier). In certain embodiments, the AI-UE Enabler may be configured to receive an indication that the Alter Ego has been instantiated. For example, the indication may include a URI that can be used to contact the Alter Ego. According to various embodiments, the AI-UE Enabler may be configured to send a response (e.g., an API response) that may include the Alter Ego ID and URI. In an embodiment, the AI-UE Enabler may be configured to use the URI to perform a security establishment procedure with the instantiated Alter Ego.

[0096] According to various embodiments, the AI-UE Enabler may be configured to receive a request to the initiate a task execution procedure and/or to send a task configuration request. For example, the task configuration request may include and/or may indicate a task description and task limitations. In an embodiment, the AI-UE Enabler may be configured to receive a request for private information, where the private information includes a response proposal. In some embodiments, the AI-UE Enabler may be configured to notify an application that private information was requested, to receive an indication that private information may be provided, and/or to reply to the request for private information. For example, the reply may indicate if the response proposal is acceptable or needs to be modified.

[0097] Some example embodiments may include procedures for supporting alter ego functionality in a 5G system, for example. Fig. 3 illustrates an example architecture 300 for how Alter Ego functionality may be supported and/or integrated in a 5G system, according to some example embodiments. As shown in the example of FIG. 3, a UE 303 may host applications 305 (e.g., App 1 and/or App 2) and an AI-UE-Enabler 310. For example, the AI-UE-Enabler 310 may be part of the UE platform, may be hosted in the mobile termination (MT) part of the UE, may be an application that is hosted in the terminal equipment (TE) part of the UE, or may be part of the UE operating system. The AI-UE-Enabler 310 may expose an interface to the applications 305 that run on the UE 303. The interface may be called AE1, for example, as shown in FIG. 3. The interface may allow the applications 305 to trigger a procedure to instantiate, configure, and control an Alter Ego Server instance. [0098] In an embodiment, the AE1 interface is between a UE Hosted Application 305 and the AI-UE-Enabler 310. This interface may be an application programming interface (API). Alternatively, the interface may be implemented in attention (AT) Command (e.g., if the UE Hosted Application is hosted in the TE part of the UE and the AI-UE-Enabler is hosted in the ME part of the UE).

[0099] According to some example embodiments an Al Enabler Server 320 may be deployed in the mobile network infrastructure domain. The AI-Enabler-Server 320 may provide services to the UE Hosted Applications 305 and AI-UE-Enabler 310. Some examples of services that the AI- Enabler-Server 320 may provide to the UE Hosted Applications and AI-UE-Enabler may include: storage and access control of data that is associated with the UE Hosted Application 305, and/or bootstrap function (BSF) functionality for establishing a secure connection between an Alter Ego Server 325 and AI-UE-Enabler 310.

[0100] In some embodiments, the interface between the AI-UE-Enabler 310 and AI-Enabler- Server 320 may be called AE2 and may be an HTTP based interface.

[0101] According to an embodiment, the Alter Ego Server 325 may be a server or function that can be configured to autonomously perform tasks for a physical user.

[0102] In some embodiments, the interface between the Alter Ego Server 325 and AI-Enabler- Server 320 may be called AE3. This interface may be an HTTP interface and may be used by the Alter Ego Server 325 to retrieve configuration information and application data from the AI- Enabler-Server 320.

[0103] According to certain embodiments, the interface between the Alter Ego Server 325 and AI-UE-Enabler may be called AE6. This interface may be an HTTP interface and used by the Alter Ego Server 325 to retrieve configuration information and application data from the AI-UE-Enabler 310.

[0104] In an embodiment, the interface between the Alter Ego Server 325 and Application Server 330 may be called AE4. This interface may be specific to the Application Service.

[0105] According to some embodiments, the interface between a UE Hosted Application 305 and Application Server 330 may be called AE5. This interface may be specific to the Application Service and may be used for interaction between the physical user and the Application Service.

[0106] Some example embodiments may include procedures for configuration, initiation and/or execution of a task, for example. FIG. 4 illustrates an example procedure where an Alter Ego Server 425 and Service Enablers 410, 420 may be configured, the Alter Ego Server 425 may be initiated to perform a task, and the task may be executed, according to an embodiment. In various embodiments, some pre-conditions for the following procedure may include, for example: the Al- UE-Enabler 410 discovers or is configured with contact information for the AI-Enabler-Server 420, and/or the AI-UE-Enabler 410 contacts the AI-Enabler-Server 420 and performs a registration procedure with the AI-Enabler-Server 420. The registration procedure may result in a secure connection being established between the AI-UE-Enabler 410 and the AI-Enabler-Server 420. [0107] As illustrated in the example of FIG. 4, at step 1, an application 405 that is hosted on the UE may initiate a procedure where the Alter Ego Server 425 is configured to perform a task for the UE Hosted Application 405. The procedure may store information that may be needed by the Alter Ego Server 425 in the AI-UE-Enabler 410 and the AI-Enabler-Server 420. The procedure may be used to reserve compute and storage resources in the Alter Ego Server 425. The procedure may be used to establish a secure connection between the AI-UE-Enabler 410 and Alter Ego Server 425. Infrastructure of the mobile network (e.g., the Al Enabler Server) may be used as common point of trust (e.g., a BSF) when the AI-UE-Enabler 410 and Alter Ego Server 425 establish a secure connection.

[0108] In the example of FIG. 4, at step 2, the UE Hosted Application 405 may negotiate a credential from the Application Server 430, may trigger a procedure that can cause the credential to be shared with the Alter Ego Server 425, and may cause the Alter Ego Server 425 to establish a connection with the Application Server 430, as will be discussed in further detail below. As shown at step 3, the Alter Ego Server 425 may execute the task. For example, executing the task may involve the Alter Ego Server 425 obtaining assistance from the Al Enabler Server 420, AI-UE- Enabler 40, and/or UE Hosted Application 405.

[0109] Some example embodiments may include procedures for configuring a UE enabler, enabler server and/or alter ego server. According to certain embodiments, an application that is hosted on the UE (i.e., UE Hosted Application, Appl) may initiate procedures that result in the configuration of an AI-UE-Enabler, AI-Enabler-Server, and Alter-Ego-Server. The configuring the Alter Ego Server may serve several purposes. For example, it allows the UE Hosted Application to check if there is an Alter Ego Server available in the network that can be used to interact with a specific Application Service (e.g., App Service 1) on behalf of the UE Hosted Application. Additionally, the configuring of the Alter Ego Server may establish a secure connection between the Al Enabler of the UE (i.e., AI-UE-Enabler) and the Alter Ego Server. Further, the UE Hosted Application may configure storage in the AI-UE-Enabler and the AI- Enabler Server.

[0110] Configuring storage in the AI-UE-Enabler may mean that the UE Hosted application can create application specific resources (i.e., storage and/or containers) in the AI-UE-Enabler and may use the resources to store application specific data, such as preferences, information about past behaviors, trusted contacts, etc. Configuring storage in the AI-Enabler-Server may mean that the UE Hosted application can configure the AI-UE-Enabler to mirror a subset of the UE Hosted Application’s data in the AI-Enabler Server. For example, the UE Hosted Application may configure the AI-UE-Enabler such that private information is not mirrored on the AI-Enabler- Server and such that other information is mirrored on the AI-Enabler-Server so that it may be available to the Alter Ego Server. Furthermore, the AI-UE-Enabler may also provide information (e.g., credentials) of online accounts that the Alter-Ego may be allowed to use for performing tasks, on behalf of the user. As some examples, the Alter-Ego may have access to the user's calendar, online shopping accounts, email accounts, so that it is able to automate tasks in those applications or using information provided by those online services.

[OHl] Once the AI-UE-Enabler, AI-Enabler-Server, and Alter-Ego- Server are configured, the UE-hosted application (e.g., Appl) may later initiate a procedure to configure the Alter Ego Server to perform a task.

[0112] FIG. 5 illustrates an example procedure of how an AI-UE-Enabler 510, AI-Enabler- Server 520, and Alter-Ego- Server 525 may be configured, according to an embodiment. As illustrated in the example of FIG. 5, at step 1, a UE hosted application 505 (e.g., Appl) may invoke an API to request that an Alter Ego be instantiated. In some example embodiments, the request may include any one or more of the following information:

• An Appl Instance Identifier (ID). For example, the Appl Instance Identifier may be in an fully qualified domain name (FQDN) format or an operating system (OS) application ID, may be assigned by a mobile network operator, may be provided to Appl by a user entering the identifier, e.g., via a graphical user interface (GUI), and/or may be linked by the mobile network operator (MNO) to a user’s subscription (e.g., linked to an IMSI);

• An Application Type. The application type may be indicative of the types of tasks, the amount of computations, and the amount of storage that will be required by the Alter Ego;

• Information that is used to create one or more storage resources in the AI-UE-Enabler. The resources may be respresentational state transfer (RESTful) storage resources that are each identified by a universal resource identifier (URI). Appl may store application specific data in the resources. Examples of application specific data may include historical information about past actions of Appl;

• Information that indicates to the AI-UE-Enabler which of the storage resources should be mirrored in the AI-Enabler-Server. Mirrored may mean that the AI-UE-Enabler may store a copy of the resource on the AI-Enabler-Server and may update the copy each time the original resource, which is stored in the AI-UE-Enabler is updated; • Information that indicates to the AI-UE-Enabler which of the storage resources should be linked in the AI-Enabler-Server. Linked may mean that the AI-UE-Enabler may create a link to the resource in the AI-Enabler-Server. A benefit of creating a link to a resource in the AI- Enabler Server is that Appl may not want to store a copy of the data in the AI-Enabler-Server but may want to allow the Alter Ego Server to access the data directly from the AI-UE-Enabler;

• Information that indicates to the AI-UE-Enabler which of the storage resources should not be shared with the AI-Enabler-Server. A benefit of not sharing a resource the AI-Enabler- Server is that the user may desire to not expose the stored information in any way to the AI- Enabler-Server or the Alter Ego Server; and/or

• Information that indicates that the AI-Enabler-Server is to store results of tasks and that the AI-Enabler-Server should create one or more storage resources. The resources may be RESTful storage resources that are each identified by a URL The Alter Ego sever may store task outcomes in the resources. These results may be retrieved later by the AI-UE-Enabler and provided to Appl. For example, the AI-UE-Enabler may send a notification to Appl when a result is received by the AE-UE-Enabler.

[0113] In an embodiment, the AI-UE-Enabler 510 may acknowledge Appl’s request, may indicate that the request was accepted, and may indicate that the requested storage was created. Later, the storage may be released if the AI-UE-Enabler 510 detects that the Alter Ego was not successfully created or if the Alter Ego session was terminated. It is noted that, in some embodiments, this step may be implemented as multiple steps. For example, in an embodiment, the Application Type may be provided in one message and the storage resources may be configured in separate messages.

[0114] In the example of FIG. 5, at step 2, the AI-UE-Enabler 510 may send a request to the AL Enabler Server 520. The request may be for the AI-Enabler-Server 520 to instantiate an Alter Ego. According to some example embodiments, the request may include any one or more of the following information: the Appl Instance Identifier (ID), the Application Type, copies of the resources that Appl indicated should be copied to AI-Enabler-Server in step 1, links to the resources that were created in step 1 and that Appl indicates should be linked to by the AI-Enabler- Server, and/or information regarding the resources to create in the AI-Enabler-Server.

[0115] The AI-Enabler-Server 520 may respond to the AI-UE-Enabler 510 with an indication of whether the request was accepted. Alternatively, the AI-UE-Enabler 510 may receive a notification from the AI-Enabler-Server 520 that an Alter Ego Instance is available. It is noted that, in some embodiments, this step may be implemented as multiple steps. For example, the Application Type may be provided in one message and the storage resources may be configured in separate messages.

[0116] As further illustrated in the example of FIG. 5, at step 3, the AI-Enabler Server 520 may use the Application Type to select an Alter Ego server that can provide the requested functionality and resources. The AI-Enabler-Server 520 may then send an Instantiate AE Command to the Alter Ego Server 525 to create the Alter Ego and reserve the necessary compute and storage resources. [0117] The AI-Enabler Server 520 may also provide, to the Alter Ego Server 525, access to the resources and data that were stored in step 2 and the links that were obtained in step 2. The Alter Ego Server 525 may use this information to train an Al model on how to server as an Alter Ego for the user of Appl .

[0118] One option for how the AI-Enabler Server 520 will find he appropriate Alter Ego Server 525 is that there may be a repository in the trusted 5G system that lists the Alter Ego Servers. The repository may include an indication of the supported functionality of the server, the available resources in the server, and/or the address of the server. The AI-Enabler-Server 520 may request the repository to return Alter Ego Servers that match its needs. Alternatively, the AI-Enabler- Server 520 may retrieve the complete list of servers from the repository and select the Alter Ego Server from this list.

[0119] Another option for how the AI-Enabler-Server 520 will find he appropriate Alter ego Server is that the AI-Enabler-Server 520 may try to discover suitable Alter Ego Servers using a discovery mechanism such as DNS.

[0120] The Alter Ego Server 525 may respond to the AI-Enabler-Server 520 with an indication of whether the instantiation was successful. The response may include an Alter Ego ID and Contact URI. The response may also include the URIs of the created resources.

[0121] In the example of FIG. 5, at step 4, the AI-Enabler-Server 520 may send a notification to the AI-UE-Enabler 510 to inform the AI-UE-Enabler 510 that an Alter Ego has been instantiated. The notification may include an Alter Ego ID and Contact URI. The AI-Enabler-Server 520 may store that the Alter Ego ID and the AI-UE-Enabler are associated with each other. At step 5, the AI-UE-Enabler 510 may notify Appl that an Alter Ego has been instantiated. The notification may include an Alter Ego ID and URI.

[0122] As illustrated in the example of FIG. 5, at step 6, the AI-UE-Enabler 50 may use the Contact URI that was provided in step 5 and request to perform a security establishment procedure with the Alter Ego which is identified by the Alter Ego ID. When establishing a secure connection, the AI-UE-Enabler 510 and Alter Ego Server 525 may use the AI-Enabler-Server 520 as a mutual point of trust. For example, the AI-Enabler-Server 520 may act as a Bootstrapping Service Function (BSF).

[0123] Some example embodiments may include procedures for initiating a task with an alter ego server. Once the AI-UE-Enabler, AI-Enabler-Server, and Alter-Ego- Server are configured, a UE based application (e.g., Appl) may trigger a procedure that will result in the Alter Ego initiating a task on behalf of the user of Appl. FIG. 6 illustrates an example procedure where the application (e.g., Appl) triggers a procedure that will result in the Alter Ego initiating a task on behalf of the user of the application (e.g., Appl).

[0124] As illustrated in the example of FIG. 6, at step 1, the application 605 (i.e., Appl) may execute a procedure with the Application Service 630 to obtain, or establish, a credential for the Alter Ego. In this procedure, Appl may provide Application Server with the Alter Ego ID. Appl and the Application Service 630 may exchange a credential (e.g., password) that may be used by the Alter Ego.

[0125] In the example of FIG. 6, at step 2, Appl may send a request to the AI-UE-Enabler 610 to have the Alter Ego execute a task. The request may include any one or more of the following information:

• The Appl Instance Identifier;

• The Alter Ego ID;

• The credential that was obtained in step 1 ;

• The Application Service ID;

• A task description. An example of a task may be to reply to emails;

• An indication of task limitations. An example of task limitations may be the identities of email senders that the Alter Ego is not allowed to respond to (or is allowed to). Another example of a task limitation is a subject, or topic, that the Alter Ego is not allowed to send emails about. Another limitation may be that the Alter Ego is allowed to perform a task only if the end user is promted for and grants approval; and/or

• An indication of Appl notification triggers. An example of a notification trigger is an event that should trigger a notification to be sent to App 1. For example, a notification trigger may be an email from an important business partner. The URI of where the notification should be sent should also be provided by Appl.

[0126] As illustrated in the example of FIG. 6, at step 3, the AI-UE-Enabler 610 may send a request to the AI-Enabler-Server 620 to provide the AI-Enabler-Server 620 with the Appl Instance Identifier, Alter Ego ID, Application Service ID, task description, task limitations, and notification triggers. [0127] At step 4, the AI-Enabler-Server 620 may send the Appl Instance Identifier, Application Service ID, and credential to the Alter Ego Server 625 to initiate the task execution.

[0128] At step 5, the Alter Ego Server 625 may use the secure connection that was established with AI-UE-Enabler 610, as discussed with respect to FIG. 5, to obtain the credential. Thus, the credential would not need to be shared with the AI-Enabler-Server.

[0129] At step 6, the Alter Ego Server 625 may send an introduction request to the Application Service 630. The credential that was received in step 4 may be used by the Alter Ego Server 625 to establish a secure connection with the Application Service.

[0130] Some example embodiments may include procedures for executing a task with an alter ego server. FIG. 7 illustrates an example procedure where an Alter Ego Server 725 executes a task on behalf of the user of an application 705 (e.g., Appl), according to an embodiment. In the example of FIG. 7, situations may arise where the Alter Ego Server 725 may obtain information from the AI-Enabler-Server 720 to help complete a task and may obtain information from the AI- UE-Enabler 710 and application 705 to obtain information from the AI-Enabler-Server 720 to help complete a task. The example procedure also shows an example of how application 705 (e.g., Appl) may choose to complete a task that is not appropriate for the Alter Ego Server 725 to execute.

[0131] As illustrated in the example of FIG. 7, at step 1, the Alter Ego Server 725 may begin to interact with the Application Service 730 in order to execute tasks on behalf of the user of Appl. For example, the Alter Ego Server 725 may send emails on behalf of user of Appl (e.g., on behalf of the user of Appl).

[0132] In the example of FIG. 7, at step 2, the Alter Ego Server 725 may determine that some information is required in order to complete and execute tasks. The Alter Ego Server 725 may send an Information Request to the AI-Enabler-Server 720. For example, the request may be for information about past operations that were performed by Appl . In an embodiment, the AI- Enabler-Server 720 may respond to the Alter Ego Server 725 with the requested information. For example, the requested information may have been obtained from the AI-UE-Enabler 710 during the configuration procedure. Alternatively or additionally, the AI-Enabler-Server 720 may respond to the Alter Ego Server 725 with a link to the requested information. For example, during the configuration procedure, the AI-UE-Enabler 710 may have provided a link to the information to AI-Enabler-Server 720 rather than store the information in the AI-Enabler Server 720. Alternatively or additionally, the AI-Enabler-Server 720 may respond to the Alter Ego Server 725 with an indication that the requested information cannot be provided to the Alter Ego Server 725 and that the Alter Ego Server 725 should prompt the Application Service to contact Appl. It is noted that, in some embodiments, this step may be a multi-step process where the Alter Ego Server 725 first queries the AI-Enabler-Server 720 to check what operations the Alter Ego Server 725 is authorized to perform.

[0133] As further illustrated in the example of FIG. 7, at step 3, if a link was provided to the Alter Ego Server 725 in step 2, the Alter Ego may use the link to send a Private Information Request to the AI-UE-Enabler 710. The request may indicate to the AI-UE-Enabler 710 details of the operation that needs to be performed. The request may also include an example task execution response (e.g., a draft email that the Alter Ego Server may send).

[0134] In the example of FIG. 7, at step 4, the AI-UE-Enabler 710 may notify Appl that private information was requested so that App 1 can indicate to the AI-UE-Enabler 710 whether the private data may be sent to the Alter Ego Server 725. Also, the notification may provide the example task execution response to Appl so that Appl can respond by sending an indication to the AI-UE- Enabler 710 of whether it approves, wants to modify, or reject the proposed response. The notification may trigger Appl to display a prompt (e.g., via a GUI) to the user to provide authorization for the Alter Ego to perform an operation.

[0135] As illustrated in the example of FIG. 7, at step 5, the AI-UE-Enabler 710 may return the response from the Appl in a Private Information Response and may indicate whether the private data may be sent to the Alter Ego Server 725. Also, the notification of whether Appl approves, wants to modify, or reject the proposed response.

[0136] In the example of FIG. 7, at step 6, the Application Service 730 may use the information that was obtained in step 5 and step 2 to complete execution of the task. The Alter Ego Server 725 may indicate to the Application Service 730 that the Alter Ego Server 725 is not permitted to complete a task or is not permitted to access data that is necessary to complete the task.

[0137] As shown in the example of FIG. 7, at step 7, the Application Server 730 may interact with the Appl in order to complete a task that the Alter Ego Server 725 could not complete. For example, the Application Server 730 may send a notification to Appl that a task needs to be complete by the actual user of Appl (i.e., not the Alter Ego Server). For example, the notification may indicate to Appl that there is an email that the Alter Ego Server 725 will not respond to. Alternatively, this message may also be used by Appl to provide private information directly to the Alter Ego Server 725.

[0138] In some example embodiments, at step 8a, Appl may store information in the AI-UE- Enabler about the level of satisfaction about a completed task. For example, the information may indicate a task ID, a satisfaction level, and information that describes a task output that would have been preferred over the task output that was generated by the Alter Ego Server. In an embodiment, at step 8b, the AI-UE-Enabler 710 may provide the information about the level of satisfaction about a completed task to the AI-Enabler-Server 720 or the AI-UE-Enabler 710 may provide links to where the information is stored. According to an embodiment, at step 8c, the AI-Enabler-Server 720 may provide the information to the Alter Ego Server 725. The Alter Ego Server 725 may use this information to train an Al model thus improving future outputs.

[0139] Some example embodiments may include alternative procedures for alter ego identity configuration. FIG. 8 shows an example procedure for how the Alter Ego may be configured with an identity and how the AI-Enabler-Server 820 of the MNO provides services to the Application Server 830 to allow the Application Server 830 authenticate the Alter Ego, according to an embodiment.

[0140] As illustrated in the example of FIG. 8, at step 1, the application 805 (e.g., Appl) may send a request to the AI-UE-Enabler 810 to create an Alter Ego ID (AE ID) for a new Alter Ego that will be created. The request may further indicate a requested format for the identifier. For example, App 1 may indicate what identifier format(s) are compatible with the Application Service 830. The request may also indicate the authentication and authorization procedures that are supported by the Application Service 830.

[0141] In the example of FIG. 8, at step 2, the AI-UE-Enabler 810 may send a request to the AI- Enabler Server 820. The Request may include the identity of Appl, the identifier format(s) that are compatible with the Application Service 830, and the authentication and authorization procedures that are supported by the Application Service 830.

[0142] As also illustrated in the example of FIG. 8, at step 3, the AI-Enabler-Server 820 may create a new AE ID and store credentials for the AE ID. The AI-Enabler-Server 820 may then send the AE ID to the AI-UE-Enabler 810. At step 4, the AI-UE-Enabler 80 may provide the AE ID to Appl.

[0143] In the example of FIG. 8, at step 5, App 1 will provide the AE ID to the Application Server to inform the Application Service 830 that an Alter Ego by this identity will be created and will be contacting the Application Server to act on behalf of the user of Appl. This message may also provide the Application Service 830 with the Identity of the Service Provider that created the AE ID. In this example, the Identity of the Service Provider that created the AE ID may represent the identity of the AI-Enabler-Server 820.

[0144] As further illustrated in the example of FIG. 8, at step 6, the procedures of FIG. 5 discussed above will be executed. When the AI-Enabler Server sends a message to the Alter Ego Server to instantiate the new Alter Ego, the message may include the AE ID and the credentials that were created in step 3. At step 7, the Alter Ego Server 825 may make initial contact with the Application Service 830, provides the AE ID and request to be authenticated.

[0145] In the example of FIG. 8, at step 8, the Application Service 830 may contact the Service Provider Identity that was provided in step 5 (i.e., the AI-Enabler-Server). The request in this step may be a request to authenticate the AE ID and the request provides the AI-Enabler-Server 820 with the AE ID. The request may also identify the Application Service 830.

[0146] As shown in the example of FIG. 8, at step 9, the AI-Enabler-Server 820 may send a request to the AI-UE-Enabler 810 to confirm that an authorization procedure with the Application Service 830 is expected. The AI-Enabler-Server 820 may be configured to prompt the user of Appl to confirm or deny the authorization request.

[0147] In the example of FIG. 8, at steps 10a and 10b, the user of Appl may respond to the confirmation request and the response may be forwarded to the AI-Enabler-Server. At step 11, the AI-Enabler-Server 820 may respond to the Alter Ego Server 825 with an indication that authentication may proceed, an authentication challenge value and expected response value. At step 12, the Application Service 830 may send the challenge to the Alter Ego.

[0148] As illustrated in the example of FIG. 8, at step 13, the Alter Ego may use the credentials that were provisioned in step 6 to generate a response to challenge and may then send the response to the Application Service 830. The Application Service 830 may compare the response to the expected response value that was received in step 11 and determine that the Alter Ego is authentic if the response and expected response are equal. At step 14, the Application Service 830 may indicate to the Alter Ego Server 825 if authentication was successful or failed.

[0149] In the example of FIG. 8, steps 8-14 can differ based on authentication method. For example, if Open ID is used as the Authentication Method, step 8 would originate from Alter Ego Server 825. The Alter Ego Server 825 may ask for a token from AI-Enabler-Server 820. The AI- Enabler-Server 820 may act as an authentication server. The message of step 11 may be sent to the Alter Ego Server 825. The Alter Ego Server 825 may then provide token to Application Service 830. The Application Service 830 may then send the challenge to AI-Enabler-Server 820 and the AI-Enabler-Server 820 will send back a response to Application Service 830.

[0150] Some example embodiments may include procedures performed by a server (e.g., an enabler server. An embodiment may be directed to a method that can be implemented in or executed by a server, such as an AI-Enabler-Server. For example, the AI-Enabler-Server may be or may be included in an enabler server in an operator’s domain. The method may include receiving a request to instantiate an alter ego from an Al UE Enabler. The request may include an Application Instance Identifier and an Application Type. The method may then include determining an Alter Ego Server based on the Application Type, and sending an instantiate command to the Alter Ego Server. The method may also include receiving an Alter Ego Identifier from the Alter Ego Server, and sending a notification to the Al UE Enabler. The notification may include the Alter Ego Identifier and a contact URI that is associated with the Alter Ego.

[0151] In certain embodiments, the method may include the AI-Enabler-Server participating in and/or performing a security establishment procedure with the Al UE Enabler and the Alter Ego Server. According to various embodiments, the request to instantiate an alter ego may include copies of the resources that are associated with the Application Identifier. In example embodiments, the request to instantiate an alter ego may include links to resources that are associated with the Application Identifier.

[0152] According to some embodiments, the method may include receiving a configuration request from the Al UE Enabler. The configuration request may include a task description, a task limitation, and a notification trigger. The method may include sending, to the Alter Ego Server, a request to initiate a task, and receiving an information request from the Alter Ego Server. The method may also include sending a reply message to the Alter Ego Server. The reply message may include information, a link to information, or indication that the requested information cannot be provided.

[0153] FIG. 9 illustrates an example flow diagram of a method 900, according to some example embodiments. In an embodiment, the method 900 of FIG. 9 can be implemented in or executed by a server, such as an enabler server (e.g., AI-Enabler-Server). For example, the enabler server may be or may be included in an enabler server in an operator’s domain. For example, in one embodiment, the method 900 of FIG. 9 may be implemented by the AI-Enabler-Server illustrated in any of the examples of FIGs. 3-8 as discussed above. Thus, the method 900 of FIG. 9 may include one or more of the procedures (e.g., the procedures performed by AI-Enabler-Server) illustrated in the examples of FIGs. 3-8 as discussed above.

[0154] As illustrated in the example of FIG. 9, the method 900 may include, at 905, receiving, from a wireless transmit/receive unit (WTRU) enabler associated with a WTRU, a first request to instantiate a service to be performed on behalf of the WTRU. The first request may include an indication of an application type and information about resources of the WTRU that can be shared with one or more service servers. The method may include, at 910, selecting a service server based on the application type and, at 915, sending a second request to instantiate the service on the service server. The second request may indicate the information about the resources of the WTRU that can be shared with the service servers. The method may include, at 920, receiving, from the service server, a message confirming that the service has been instantiated. At 925, the method may include sending a notification to the WTRU enabler. The notification may indicate a contact uniform resource identifier (URI) that is associated with the service. In an embodiment, the enabler server implementing the method 900 may be configured to act as a bootstrapping function in a security establishment procedure between the WTRU enabler and the service server.

[0155] In an embodiment, the service may include an alter ego and the service server may include an alter ego server. In an embodiment, an identifier associated with the service may be received, and/or the notification sent to the WTRU enabler further indicates the identifier associated with the service.

[0156] In an embodiment, the first request may include any of an indication of an application identifier associated with an application hosted by the WTRU, information indicating which storage resources in the WTRU enabler should be mirrored in the apparatus, and/or information indicating which storage resources in the WTRU enabler should be linked in the apparatus (e.g., the enabler server).

[0157] In an embodiment, the second request may indicate copies of resources that are associated with the application identifier. In an embodiment, the second request may indicate links to resources associated with the application identifier.

[0158] In an embodiment, a configuration request may be received from the WTRU enabler, where the configuration request indicates any of a task description and task limitation associated with a task.

[0159] In an embodiment, a third request may be sent, to the service server, to initiate the task in accordance with any of the task description and the task limitation.

[0160] In an embodiment, the resources of the WTRU may include storage resources configured to store application specific data associated with an application hosted on the WTRU.

[0161] FIG. 9 is provided as one example of a method, according to certain embodiments. It should be noted that the method depicted in FIG. 9 may be modified according to other embodiments discussed herein. For example, one or more of the steps of FIG. 9 may be omitted or executed in a different order. Additionally, one or more steps may be added, for example, according to the example provided in the signaling diagram of FIG. 8 or any other diagrams discussed herein.

[0162] Some example embodiments may include procedures performed by a UE (e.g., by a UE enabler). An embodiment may be directed to a method that can be implemented in or executed by a UE or WTRU, for example, by a service enabler in the UE or a AI-UE-Enabler as outlined above. According to various embodiments, the method may include receiving a request, e.g., an API request, to instantiate an alter ego. The request may include an Application Instance Identifier and an Application Type. The method may include sending a request to a server to instantiate an Alter Ego. The request may include the Application Instance Identifier links to resources of the AI-UE- Enabler. The resources may store information that relates to the Application Instance Identifier. The method may then include receiving an indication that the Alter Ego has been instantiated. The indication may include a URI that can be used to contact the Alter Ego. The method may also include sending a response, e.g., an API response, that includes the Alter Ego ID and URI.

[0163] In an embodiment, the method may include the AI-UE-Enabler using the URI to perform a security establishment procedure with the instantiated Alter Ego. According to some example embodiments, the method may include receiving a request to initiate a task execution procedure, and sending a task configuration request. The task configuration request may include a task description and task limitations.

[0164] According to some example embodiments, the method may include receiving a request for private information, where the private information includes a response proposal. The method may also include notifying an application that private information was requested, receiving an indication that private information may be provided, and/or replying to the request for private information. The reply may indicate if the response proposal is acceptable or needs to be modified. [0165] Example embodiments may be directed to an apparatus, such as a UE, WTRU, network element, and/or server, or the like. The apparatus may include circuitry, processor(s), memory, and/or transceiver(s) configured to perform any of the procedures or methods described herein, such as those shown in FIGs. 4-8 and/or discussed above.

[0166] An embodiment may be directed to a method, which may be implemented by a server (e.g., an enabler server). The method may include receiving a request to instantiate an alter ego from a UE, e.g., from an Al UE enabler. The request may indicate an application identifier (ID) and an application type. The method may include determining an alter ego server based on the application type, sending an instantiate command to the determined alter ego server, receiving an alter ego identifier (ID) from the alter ego server, and sending a notification to the UE, e.g., to the Al UE enabler, where the notification may indicate the alter ego identifier (ID) and a contact uniform resource identifier (URI) that is associated with the alter ego.

[0167] In various embodiments, the method may include performing a security establishment procedure with the Al UE enabler and the alter ego server.

[0168] In various embodiments, the request to instantiate the alter ego may indicate copies of resources that are associated with the application identifier.

[0169] In various embodiments, the request to instantiate the alter ego may include or may indicate links to resources that are associated with the Application Identifier. [0170] In various embodiments, the method may include receiving a configuration request from the Al UE enabler, the configuration request indicating a task description, a task limitation, and/or a notification trigger.

[0171] In various embodiments, the method may include sending, to the alter ego server, a request to initiate a task.

[0172] In various embodiments, the method may include receiving an information request from the alter ego server.

[0173] In various embodiments, the method may include sending a reply message to the alter ego server, the reply message comprising at least one of information, a link to information, and/or indication that the requested information cannot be provided.

[0174] An embodiment may be directed to an apparatus comprising circuitry, a processor, memory and/or transceiver configured to receive a request to instantiate an alter ego from a UE, e.g., from an Al UE enabler. The request may indicate an application identifier (ID) and an application type. The apparatus may also be configured to determine an alter ego server based on the application type, send an instantiate command to the determined alter ego server, receive an alter ego identifier (ID) from the alter ego server, and send a notification to the UE, e.g., to the Al UE enabler, where the notification may indicate the alter ego identifier (ID) and a contact uniform resource identifier (URI) that is associated with the alter ego.

[0175] An embodiment may be directed to a method, which may be implemented by a WTRU. For example, the method may be implemented by a service enabler in a WTRU, such as an Al UE enabler. In various embodiments, the method may include receiving a request, such as an application programming interface (API) request, to instantiate an alter ego. According to an embodiment, the request may include or may indicate an application identifier (ID) or application instance ID and an application type. In some embodiments, the method may further include sending a request to a server to instantiate the alter ego and receiving an indication that the alter ego has been instantiated. For example, the indication may indicate a URI associated with the alter ego. According to an embodiment, the method may include sending a response, e.g., API response, indicating an identifier of the alter ego and the URI.

[0176] In various embodiments, the request to instantiate the alter ego may include or indicate application instance identifier links to resources of the Al UE enabler, wherein the resources store information associated with the application instance identifier.

[0177] In various embodiments, the method may include performing a securing establishment procedure with the instantiated alter ego, using the URI. [0178] In various embodiments, the method may include receiving a request to initiate a task execution procedure, and sending a task configuration request that may indicate a task description and task limitations.

[0179] In various embodiments, the method may include receiving a request for private information, where the private information comprises a response proposal.

[0180] In various embodiments, the method may include notifying an application that the private information was requested, receiving an indication that private information may be provided, and/or replying to the request for private information, where the reply may indicate whether the response proposal is acceptable or should be modified.

[0181] An embodiment may be directed to an apparatus comprising circuitry, a processor, memory and/or transceiver configured to receive a request, such as an application programming interface (API) request, to instantiate an alter ego. According to an embodiment, the request may include or may indicate an application identifier (ID) or application instance ID and an application type. In some embodiments, the apparatus may also be configured to send a request to a server to instantiate the alter ego and receiving an indication that the alter ego has been instantiated. For example, the indication may indicate a URI associated with the alter ego. According to an embodiment, the apparatus may be configured to send a response, e.g., API response, indicating an identifier of the alter ego and the URI.

[0182] Although features and elements are provided above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations may be made without departing from its spirit and scope, as will be apparent to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Functionally equivalent methods and apparatuses within the scope of the disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that this disclosure is not limited to particular methods or systems.

[0183] In some example embodiments described herein, (e.g., configuration) information may be described as received by a WTRU from the network, for example, through system information or via any kind of protocol message. Although not explicitly mentioned throughout embodiments described herein, the same (e.g., configuration) information may be pre-configured in the WTRU (e.g., via any kind of pre-configuration methods such as e.g., via factory settings), such that this (e.g., configuration) information may be used by the WTRU without being received from the network.

[0184] Any characteristic, variant or embodiment described for a method is compatible with an apparatus device comprising means for processing the disclosed method, such as with a device comprising a processor configured to process the disclosed method, a computer program product comprising program code instructions and a non-transitory computer-readable storage medium storing program instructions.

[0185] The foregoing embodiments are discussed, for simplicity, with regard to the terminology and structure of infrared capable devices, i.e., infrared emitters and receivers. However, the embodiments discussed are not limited to these systems but may be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves such as acoustic waves. [0186] It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting. As used herein, the term "video" or the term "imagery" may mean any of a snapshot, single image and/or multiple images displayed over a time basis. As another example, when referred to herein, the terms "user equipment" and its abbreviation "UE", the term "remote" and/or the terms "head mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and/or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and/or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU; (iii) a wireless-capable and/or wired-capable device configured with less than all structures and functionality of a WTRU; or (iv) the like. Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to FIGs. 1 A-1D. As another example, various disclosed embodiments herein supra and infra are described as utilizing a head mounted display. Those skilled in the art will recognize that a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience.

[0187] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0188] Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are examples only, and should not be taken as limiting the scope of the following claims. For instance, the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

[0189] Moreover, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit ("CPU") and memory. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer executed" or "CPU executed."

[0190] One of ordinary skill in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.

[0191] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM)) mass storage system readable by the CPU. The computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.

[0192] In an illustrative embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and/or any other computing device.

[0193] There is little distinction left between hardware and software implementations of aspects of systems. The use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost versus efficiency tradeoffs. There may be various vehicles by which processes and/or systems and/or other technologies described herein may be effected (e.g., hardware, software, and/or firmware), and the preferred vehicle may vary with the context in which the processes and/or systems and/or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and/or firmware vehicle. If flexibility is paramount, the implementer may opt for a mainly software implementation. Alternatively, the implementer may opt for some combination of hardware, software, and/or firmware.

[0194] The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples include one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples may be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In an embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and/or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, may be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).

[0195] Those skilled in the art will recognize that it is common within the art to describe devices and/or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and/or processes into data processing systems. That is, at least a portion of the devices and/or processes described herein may be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity, control motors for moving and/or adjusting components and/or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.

[0196] The herein described subject matter sometimes illustrates different components included within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated may also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being "operably couplable" to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

[0197] With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

[0198] It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the following appended claims and/or the descriptions herein may include usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim including such introduced claim recitation to embodiments including only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and/or "an" should be interpreted to mean "at least one" or "one or more"). The same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B." Further, the terms "any of' followed by a listing of a plurality of items and/or a plurality of categories of items, as used herein, are intended to include "any of," "any combination of," "any multiple of," and/or "any combination of multiples of the items and/or the categories of items, individually or in conjunction with other items and/or other categories of items. Moreover, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero. And the term "multiple", as used herein, is intended to be synonymous with "a plurality".

[0199] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0200] As will be understood by one skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also encompass any and all possible subranges and combinations of subranges thereof. Any listed range can be easily recognized as sufficiently describing and enabling the same range being broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein may be readily broken down into a lower third, middle third and upper third, etc. As will also be understood by one skilled in the art all language such as "up to," "at least," "greater than," "less than," and the like includes the number recited and refers to ranges which can be subsequently broken down into subranges as discussed above. Finally, as will be understood by one skilled in the art, a range includes each individual member. Thus, for example, a group having 1-3 cells refers to groups having 1, 2, or 3 cells. Similarly, a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

[0201] Moreover, the claims should not be read as limited to the provided order or elements unless stated to that effect. In addition, use of the terms "means for" in any claim is intended to invoke 35 U.S.C. § 112, 6 or means-plus-function claim format, and any claim without the terms "means for" is not so intended.

[0202] Although various embodiments have been described in terms of communication systems, it is contemplated that the systems may be implemented in software on microprocessors/general purpose computers (not shown). In certain embodiments, one or more of the functions of the various components may be implemented in software that controls a general-purpose computer.

[0203] In addition, although some example embodiments are illustrated and described herein, the invention is not intended to just be limited to the details shown. Rather, various modifications and variations may be made in the details within the scope and range of equivalents of the claims and without departing from the spirit or scope invention.

REFERENCES

[0204] The following references may have been referred to hereinabove, each of which is incorporated herein by reference in its entirety:

[0205] [1] 3GPP TS 22.856, Feasibility Study on Localized Mobile Metaverse Services (Release 19); V0.3.0.

Claims

CLAIMS What is claimed is:

1. An apparatus, comprising: circuitry including any of a processor, memory, transmitter and receiver, the circuitry configured to: receive a first request to instantiate a service to be performed on behalf of a wireless transmit/receive unit (WTRU), from a WTRU enabler associated with the WTRU, wherein the first request comprises an indication of an application type and information about resources of the WTRU that can be shared with one or more service servers; select a service server based on the application type; send a second request to instantiate the service on the service server, wherein the second request indicates the information about the resources of the WTRU that can be shared with the service servers; receive, from the service server, a message confirming that the service has been instantiated; and send a notification to the WTRU enabler, wherein the notification indicates a contact uniform resource identifier (URI) that is associated with the service, wherein the apparatus is configured to act as a bootstrapping function in a security establishment procedure between the WTRU enabler and the service server.

2. The apparatus of claim 1, wherein the service comprises an alter ego and the service server comprises an alter ego server.

3. The apparatus of any of claims 1-2, wherein the circuitry is configured to receive an identifier associated with the service, and wherein the notification sent to the WTRU enabler further indicates the identifier associated with the service.

4. The apparatus of any of claims 1-3, wherein the first request further comprises any of: an indication of an application identifier associated with an application hosted by the WTRU, information indicating which storage resources in the WTRU enabler should be mirrored in the apparatus, information indicating which storage resources in the WTRU enabler should be linked in the apparatus.

5. The apparatus of any of claims 1-3, wherein the second request indicates copies of resources that are associated with the application identifier.

6. The apparatus of any of claims 1-4, wherein the second request indicates links to resources associated with the application identifier.

7. The apparatus of any of claims 1-6, wherein the circuitry is configured to receive a configuration request from the WTRU enabler, wherein the configuration request indicates any of a task description and task limitation associated with a task.

8. The apparatus of claim 7, wherein the circuitry is configured to send, to the service server, a third request to initiate the task in accordance with any of the task description and the task limitation.

9. The apparatus of any of claims 1-8, wherein the resources of the WTRU comprise storage resources configured to store application specific data associated with an application hosted on the WTRU.

10. A method, comprising: receiving, by an enabler server from a wireless transmit/receive unit (WTRU) enabler associated with a WTRU, a first request to instantiate a service to be performed on behalf of the WTRU, wherein the first request comprises an indication of an application type and information about resources of the WTRU that can be shared with one or more service servers; selecting a service server based on the application type; sending a second request to instantiate the service on the service server, wherein the second request indicates the information about the resources of the WTRU that can be shared with the service servers; receiving, from the service server, a message confirming that the service has been instantiated; and sending a notification to the WTRU enabler, wherein the notification indicates a contact uniform resource identifier (URI) that is associated with the service, wherein the enabler server is configured to act as a bootstrapping function in a security establishment procedure between the WTRU enabler and the service server.

11. The method of claim 10, wherein the service comprises an alter ego and wherein the service server comprises an alter ego server.

12. The method of any of claims 10-11, comprising receiving an identifier associated with the service, and wherein the notification sent to the WTRU enabler further indicates the identifier associated with the service.

13. The method of any of claims 10-12, wherein the first request further comprises any of: an indication of an application identifier associated with an application hosted by the WTRU, information indicating which storage resources in the WTRU enabler should be mirrored in the apparatus, information indicating which storage resources in the WTRU enabler should be linked in the apparatus..

14. The method of any of claims 10-13, wherein the second request indicates copies of resources that are associated with the application identifier.

15. The method of any of claims 10-14, wherein the second request indicates links to resources associated with the application identifier.

16. The method of any of claims 10-15, comprising receiving a configuration request from the WTRU enabler, wherein the configuration request indicates any of a task description and task limitation associated with a task.

17. The method of claim 16, comprising sending, to the service server, a third request to initiate the task in accordance with any of the task description and the task limitation.

18. The method of any of claims 10-17, wherein the resources of the WTRU comprise storage resources configured to store application specific data associated with an application hosted on the WTRU.

19. An apparatus, comprising: circuitry, including any of a processor, memory, and transceiver, the circuitry configured to send first information indicating a request to an enabler server to instantiate an alter ego, wherein the first information indicates an application type and information about resources of the UE that can be shared with an alter ego server; receive an indication that the alter ego has been instantiated by the alter ego server, the indication indicating a uniform resource identifier (URI) associated with the instantiated alter ego; receive second information indicating a request for the alter ego to execute a task; send configuration information to the enabler server, the configuration information indicating a description of the task, limitations associated with the task, and notification triggers associated with the task; and perform, using the URI, a security establishment procedure with the instantiated alter ego, wherein the first information further indicates an application instance identifier (ID) and application instance identifier (ID) links to resources of the apparatus, wherein the resources store information associated with the application instance identifier (ID).

20. A method, comprising: sending, by a wireless transmit/receive unit (WTRU), first information indicating a request to an enabler server to instantiate an alter ego, wherein the first information indicates an application type and information about resources of the UE that can be shared with an alter ego server; receiving an indication that the alter ego has been instantiated by the alter ego server, the indication indicating a uniform resource identifier (URI) associated with the instantiated alter ego; receiving second information indicating a request for the alter ego to execute a task; sending configuration information to the enabler server, the configuration information indicating a description of the task, limitations associated with the task, and notification triggers associated with the task; and performing, using the URI, a security establishment procedure with the instantiated alter ego, wherein the first information further indicates an application instance identifier (ID) and application instance identifier (ID) links to resources of the WTRU, wherein the resources store information associated with the application instance identifier (ID).