Method, apparatus, and system for dynamically assembling transient devices via microservices for optimized human-centric experiences
By dynamically assembling resources and microservice function chains, the problem of poor user experience in a device experience-centric environment is solved, a high-quality immersive experience is achieved, and resources are dynamically adjusted to meet the needs of end users.
Patent Information
- Application Number
- CN202080059747.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-07-23
- Filing Date
- 2020-07-23
- Publication Date
- 2024-11-05
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The prior art is difficult to provide an end-user immersive experience in advanced or next-generation wireless communication systems, especially in device experience-centric environments where device limitations lead to sub-optimal user experience.
By dynamically assembling resources, leveraging name-based microservice function chains and dynamic programming models, we can achieve a human-centered immersive experience, dynamically select and migrate devices associated with providing experiences, and optimize experience specifications to meet end-user expectations.
It realizes a high-quality immersive experience on end user equipment, dynamically adjusts resource configuration to adapt to environmental changes, and improves the sustainability and quality of user experience.
Smart Images

Figure CN114303402B_ABST
Abstract
Description
Background Art
[0001] The present invention relates to the field of computing and communications, and more particularly, to methods, devices, systems, architectures, and interfaces for computing and communications in advanced or next generation wireless communication systems, including communications performed using new radio (NR) and / or NR access technologies and communication systems.
[0002] Advances in desktop computing have led to new concepts for computing. Such new concepts include pervasive computing, which may also be referred to as distributed computing, and providing an immersive experience for end users, for example, by supporting continuous computing on network devices that are distributed at all scales and set up at any time and any location. In a pervasive computing environment, computing tasks can be performed (e.g., implemented, instantiated, conceived, generated, provided, etc.) to execute any collaborative process information, migrate the location of their execution, and spontaneously offload tasks to other devices; for example, based on changes in contextual information related to the experience. Performing computing tasks in this manner can provide the desired immersive experience for end users or communities / user groups.
[0003] In computing environments with inexpensive and / or powerful devices (e.g., smart phones, IoT-enabled light bulbs, networked / wireless displays and / or user input devices and / or sensors, etc.), the proliferation of such devices (e.g., ubiquitous devices) creates a perception of "universal availability" of (e.g., necessary) computing power. The focus of many (e.g., ubiquitous) distributed computing domains that implement (e.g., execute, instantiate, provide, etc.) ubiquitous devices is on the optimization of the experience for a specific device. For example, the focus on the experience for a specific device results in (e.g., end-user, community, etc.) experiences such as chimney-like becoming device-centric experiences that are implemented through highly optimized individual devices. Such distributed computing domains that focus on the experience of a specific device do not provide an immersive experience for the end user, which can be achieved with the collaborative vision of ubiquitous computing. BRIEF DESCRIPTION OF THE DRAWINGS
[0004] Additionally, like reference numerals in the drawings indicate like elements, and wherein:
[0005] Figure 1A is a system diagram illustrating an exemplary communication system in which one or more disclosed embodiments may be implemented;
[0006] Figure 1B It is shown that according to one embodiment, Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) for use within the communication system shown;
[0007] Figure 1C It is shown that according to one embodiment, Figure 1A A system diagram of an exemplary radio access network (RAN) and an exemplary core network (CN) used within the illustrated communication system;
[0008] Figure 1D It is shown that according to one embodiment, Figure 1A A system diagram of another exemplary RAN and another exemplary CN used in the communication system shown;
[0009] Figure 2 is a schematic diagram illustrating layers of a computing system according to an embodiment;
[0010] Figure 3 is a schematic diagram illustrating an experience achieved through a set of linked named service functions (SFs) and / or microservices according to an embodiment;
[0011] Figure 4 is a schematic diagram showing experiences achieved at various layers according to an embodiment;
[0012] Figure 5 is a schematic diagram showing a naming service function (SF) performed at various layers when nSFF implements SF interconnectivity according to an embodiment;
[0013] Figure 6 is a schematic diagram illustrating a device packaging entity (DPE) according to an embodiment;
[0014] Figure 7 is a schematic diagram illustrating a dynamically assembled service function (SF) according to an embodiment; and
[0015] Figure 8 is a diagram showing the use of a user controlled SF (UCSF) as a SF according to an embodiment 控制 Schematic diagram of the service function chain (SFC).
[0016] Example Network for Implementing Implementations
[0017] Figure 1A1 is a schematic diagram illustrating an exemplary communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 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), single carrier FDMA (SC-FDMA), zero tail unique word DFT spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.
[0018] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110 and other networks 112, but it should be understood 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 “STA”) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.
[0019] The communication system 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 that is configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNode B, a Home Node B, a Home eNode B, a gNB, an NR Node B, 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.
[0020] 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), a relay node, 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 cells (not shown)). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrums. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In one embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.
[0021] 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).
[0022] More specifically, as noted above, the communication 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, etc. 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 use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink (DL) Packet Access (HSDPA) and / or High Speed UL Packet Access (HSUPA).
[0023] In one 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 Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro).
[0024] In one 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).
[0025] In one 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 example using dual connectivity (DC) principles. Thus, the air interface used by the 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., eNBs and gNBs).
[0026] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), GSM Enhanced Data Rates for Evolution (EDGE), GSM EDGE (GERAN), etc.
[0027] Figure 1A The base station 114b in the may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one 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 one 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 yet another 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 a picocell or a femtocell. As Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.
[0028] 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 different quality of service (QoS) requirements, such as different throughput requirements, delay requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the specification, the CN 106 / 115 may be 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 different quality of service (QoS) requirements, such as different throughput requirements, delay requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. Figure 1AAlthough not shown in the figure, 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 utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
[0029] The CN 106 / 115 may also act 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 a circuit-switched telephone network that provides 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), the 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 communication 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 / 113 or a different RAT.
[0030] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication 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 via different wireless links). Figure 1A The illustrated WTRU 102c 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.
[0031] Figure 1B is a system diagram illustrating an exemplary WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, 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 peripherals 138. It will be appreciated that the WTRU 102 may include any subcombination of the foregoing elements while remaining consistent with an embodiment.
[0032] 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 associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functions that enable 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. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
[0033] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via an air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In one embodiment, the transmit / receive element 122 may be a transmitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive RF and light signals. It should be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.
[0034] Although the transmit / receive element 122 is Figure 1B 1 as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one 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.
[0035] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals 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 to enable the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.
[0036] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit) and may receive user input data therefrom. 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 a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only 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 a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
[0037] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power to 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, etc.
[0038] 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 from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.
[0039] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (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, etc. The peripheral device 138 may include one or more sensors, which may be one or more of the following: 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.
[0040] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (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 for reducing and / or substantially eliminating self-interference via hardware (e.g., choke) or via signal processing performed by a processor (e.g., a separate processor (not shown) or via the processor 118). In one embodiment, the WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous.
[0041] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 according to one embodiment. As described above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.
[0042] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-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 one embodiment, the evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.
[0043] Each of the evolved Node Bs 160a, 160b, 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 UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.
[0044] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements is depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.
[0045] The MME 162 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 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, etc. 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.
[0046] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 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 the user plane during inter-evolved Node-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.
[0047] 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.
[0048] 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 be in communication 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 other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.
[0049] Although the WTRU Figures 1A to 1D Although described as a wireless terminal, it is contemplated that in certain representative embodiments, such a terminal may (eg, temporarily or permanently) use a wired communications interface with a communications network.
[0050] In a representative embodiment, the other network 112 may be a WLAN.
[0051] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for a BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be sent to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be sent by the AP, for example, wherein the source STA may send traffic to the AP, and the AP may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be sent between the source and destination STAs (e.g., directly between them) using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.
[0052] When using the 802.11ac infrastructure operating mode or a similar operating mode, 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., a 20 MHz wide bandwidth) or a width dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each 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.
[0053] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.
[0054] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz and / or 80MHz channels can be formed by combining continuous 20MHz channels. A 160MHz channel can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For the 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be transmitted by transmitting STA. At the receiver of the receiving STA, the above-mentioned operation for the 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC).
[0055] 802.11af and 802.11ah support operating modes below 1GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support instrument type control / machine type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).
[0056] WLAN systems that can support multiple channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum 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 (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (supporting only the 1MHz operating mode) is transmitting to the AP, the entire available frequency band may be considered busy even if most of the frequency bands remain idle and may be available.
[0057] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.
[0058] Figure 1D 1 is a system diagram showing the RAN 113 and the CN 115 according to one embodiment. As noted above, the RAN 113 may employ 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.
[0059] 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 to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a. In one embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation techniques. 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 one embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) techniques. For example, the WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).
[0060] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable parameter sets. 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 the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., containing different numbers of OFDM symbols and / or continuously varying absolute time lengths).
[0061] 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 a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while also not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate or connect with the gNBs 180a, 180b, 180c while also communicating or connecting with other RANs, such as the eNode-Bs 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-Bs 160a, 160b, 160c may serve as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.
[0062] 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 UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.
[0063] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.
[0064] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c via the N2 interface in the RAN 113 and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing in order to customize CN support for the WTRU 102a, 102b, 102c based on the type of services used by the WTRU 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 mobile broadband (eMBB) access, services for machine type communication (MTC) access, etc. 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.
[0065] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.
[0066] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N3 interface, 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. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.
[0067] 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 other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b via the UPF 184a, 184b via an N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
[0068] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more simulation devices (not shown): WTRU102a-d, base station 114a-b, evolved Node B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b and / or any other device described herein. The simulation device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.
[0069] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or an operator network environment. For example, the one or more simulation devices may perform 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 simulation devices may perform one or more functions or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for testing purposes and / or may use over-the-air wireless communications to perform testing.
[0070] The one or more simulation devices may perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device may be used in a test scenario in a test lab and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. The one or more simulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuits (e.g., which may include one or more antennas) may be used by the simulation device to transmit and / or receive data. DETAILED DESCRIPTION
[0071] According to an embodiment, a human-centric experience (e.g., compared to a device-centric experience) may be provided (e.g., enabled) by a device and / or system that (e.g., is designed and / or engineered to) provide a method of targeting experiences (e.g., to a user, end-user, community, etc.) for distributed and / or pervasive computing. According to an embodiment, a device and / or system that provides a human-centric experience may have requirements and / or constraints on the experience itself (e.g., associated with a user, end-user, community, etc.). In this case, the device and / or system that provides the human-centric experience may be optimized to meet (e.g., target, focus on, etc.) the requirements and constraints of the experience itself, even though surrounding devices may provide (e.g., may achieve reaching) an immersive experience using a collaborative approach, for example, to achieve a human-centric immersive experience.
[0072] In the context of smokestack, device-centric and / or device-specific experiences, the devices and / or systems (e.g., interconnectivity) used for such experiences are typically fixed, i.e., static and / or non-dynamic. And such devices and / or systems act as constraints to achieve a given (e.g., device-centric and / or device-specific) experience. In this case, the limitations of the device can be (e.g., forced to act as) constraints on the user experience itself. In the case of an experience, for example, when a user wishes to watch a 4k movie with English subtitles (e.g., an experience) on a mobile device, achieving such a device-centric experience is limited by the size of the device screen and the (e.g., video) resolution continues to be limited, for example, due to limitations in cellular network bandwidth and / or device computing power. This may result in a sub-optimal (e.g., user) experience due to a lower (e.g., 1080p) resolution on a small screen.
[0073] According to an embodiment, in implementing a human-centric experience (e.g., watching a 4k movie with English subtitles), the specifications of the desired human-centric immersive experience (e.g., requirements, capabilities, thresholds, constraints, etc.) can remain fixed, for example, for the desired duration. According to an embodiment, for example, while any of the (e.g., potential) computing objects, entities, their implementations, and their interconnectivity can be changed, for example, to maintain and / or improve the experience (e.g., the entire duration), the specifications of the desired human-centric immersive experience can remain fixed. In other words, according to an embodiment, while a device (e.g., the concept of) can be considered and / or referred to as a transient device, a human-centric immersive experience (e.g., the concept of) can be a (e.g., defined) aspect of assembling resources at runtime (e.g., from constituent devices). According to an embodiment, in the case of a human-centric immersive experience implemented using a transient device, this transient nature can allow resources to be assembled to focus on delivering the best experience to the end user.
[0074] According to an embodiment, for example, as described below, there may be methods, devices, entities and / or systems for implementing a (e.g., transient) device for a human-centric immersive experience. According to an embodiment, the (e.g., transient) device may be implemented by an experience-focused approach, for example, to specify a microservice for the (e.g., transient) device. According to an embodiment, the microservice for the (e.g., transient) device may be specified to provide (e.g., implement) a (e.g., specific, end-user, community, etc.) experience (e.g., desired, handy, etc. by assembling (e.g., required) resources that implement the microservice for the (e.g., transient) device at runtime.
[0075] According to an embodiment, a (e.g., specific, end-user, human-centric, community, etc.) experience may be specified (e.g., defined, configured, instantiated, implemented, etc.) as a dynamic programming (DP) model, for example, may be associated with a name-based microservice function chain (MSFC). According to an embodiment, the name-based MSFC may be carried (e.g., implemented, instantiated via resources, etc.) by a dynamically assembled set of resources, and the set of resources may be provided by distributed devices. According to an embodiment, a system may (e.g., dynamically) assemble a set of resources for implementing a (e.g., specific, end-user, human-centric, community, etc.) experience, for example, the set of resources (e.g., used) is associated with any number of distributed devices for carrying (e.g., implementing, instantiating, etc.) the name-based MSFC. According to an embodiment, dynamically assembling a set of resources (e.g., by a system providing a human-centric immersive experience) may be driven (e.g., performed according to the provisioning of the following items): (e.g., appropriate, human-centric, etc.) context information (e.g., at runtime), and continuous matching against constraints within the DP model (e.g., based on such human-centric context information).
[0076] According to an embodiment, a device packaging entity (DPE) may establish a name-based relationship (e.g., relationship, association, mapping, MSFC, etc.) associated with (e.g., suitable for) exchanging information that executes (e.g., suitable) MSFCs that implement, for example, a DP model associated with a defined (e.g., specified, configured, desired, etc.) human-centric immersive experience. According to an embodiment, the DPE may collect information from a device. For example, the DPE may collect (e.g., suitable) contextual information from a (e.g., distributed) device that may be associated with (e.g., participating in) a system that provides (e.g., dynamically assembles a set of resources for) an experience. According to an embodiment, the DPE may match (e.g., compare, analyze, weigh, etc.) information against constraints. For example, the DPE may match contextual information against constraints that are associated with (e.g., configured, listed, specified, etc.) a DP-based specification (e.g., DP model) of a (e.g., given, human-centric, end-user, community, etc.) experience. According to an embodiment, the DPE may select (e.g., best) a set of resources that match the constraints associated with (e.g., within) the DP Model. According to an embodiment, the DPE may direct (e.g., implement, instantiate, command, trigger, etc.) the (e.g., selected) set of resources, for example, to establish a name-based relationship (e.g., MSFC) suitable for exchanging information to execute an appropriate MSFC that implements the DP Model associated with a specified human-centric immersive experience.
[0077] According to an embodiment, for example, a transient device may be established by a DPE to provide a human-centric immersive experience. According to an embodiment, a transient device may be specified based on a microservice (e.g., MSFC) experience associated with a DP model (e.g., for a human-centric immersive experience). According to an embodiment, a transient device may be established based on context information (e.g., context information collected from available resources in a networked environment). According to an embodiment, context information (e.g., associated with available devices and / or network resources) may be matched (e.g., compared) with information (e.g., constraints) associated with a DP model for experience. According to an embodiment, a set of resources for (e.g., optimizing) a DP model may be selected based on matching context information and constraints. According to an embodiment, a set of (e.g., optimized) resources may be indicated (e.g., signaling, commanding, associating, mapping, configuring, etc.) to form (e.g., instantiate, execute, perform, implement, etc.) an MSFC (e.g., a function chain based on an appropriate microservice name), for example, to execute an MSFC to implement (e.g., define) a DP model for a human-centric immersive user experience.
[0078] According to the embodiment, in realizing the human-centric experience, the device associated with providing the experience can be dynamically selected and / or migrated. For example, in the case of the experience provided by the DP model according to which the user watches a 4k movie with English subtitles, when the user enters his living room, the display content of the movie can be migrated to the nearby UHD TV screen. That is, according to the embodiment, the display can be migrated, for example, when the network connection is switched to the home WiFi system, and the subtitle task of the video application (e.g., the MSFC associated with the subtitle) is migrated to the home computer. In this case, for example, except for some tasks such as control elements associated with user input (e.g., user intervention), the mobile device initially used can be relieved from (e.g., performing, providing, etc.) almost any task.
[0079] According to an embodiment, the implementation of a human-centric experience (e.g., a DP model of such an experience) may be represented by (e.g., associated with) the following characteristics: dynamics (e.g., high dynamics, fast changes, transient requirements, etc.) for any of the computing objects (e.g., entities, MSFCs, transient devices, etc.) that are in play and the interconnectivity (e.g., used) therebetween. According to an embodiment, such (e.g., high) dynamics may be associated with (e.g., driven by, characterized by, specified by, etc.) any of the following: (i) specifications of the (e.g., human-centric, immersive, desired, etc.) experience; (ii) characteristics of the (e.g., objects (e.g., entities, devices, etc.) that are in play and their connectivity; and (iii) contextual information (e.g., information about any of location, bandwidth, hardware capabilities, etc.) associated with the (e.g., desired) experience.
[0080] According to an embodiment, the specification of the experience can be a programming framework, for example, which can be lifted from (e.g., can interact with, be associated with) an execution process (e.g., displaying, processing, and receiving video through a locator-based endpoint model) to facilitate generating (e.g., associating, mapping, etc.) named relationships of service endpoints (e.g., MSFCs). According to an embodiment, the named relationships (e.g., for MFSCs) can be determined at runtime, for example, based on changes imposed by context changes in the (e.g., overall) system.
[0081] Figure 2 is a schematic diagram illustrating layers of a computing system according to an embodiment.
[0082] Depending on the embodiment, the key to the nature of the objects and their connectivity is that they may exist at many levels of the (eg, overall) system, such as Figure 2 As shown. According to an embodiment, dynamic changes can be made in various layers of the entire system (e.g., all and / or any), and, for example, such dynamic changes may not be limited to (e.g., only) one layer. For example, in the case of a user watching a 4k movie with English subtitles, according to an embodiment, the internal in-device connection to either the display screen and the subtitle task for displaying the video within a single mobile device can be exchanged with, for example, a UDP network connection (e.g., for pure video streaming) to a nearby TV screen (e.g., pure video streaming) and a TCP connection to 3 nearby PCs, respectively.
[0083] According to embodiments, for example, such dynamic changes to active objects and optimization of systems associated with active objects may be driven, for example, (e.g., primarily) by optimizing an experience (such as one of a human-centric immersive end-user experience, a community experience, etc.). That is, according to embodiments, the experience (e.g., of the end user) drives the performance (e.g., of the system), where components contribute to optimizing the system; for example, rather than optimizing individual components that contribute to the experience (e.g., performance, usage, allocation, etc. of the components).
[0084] According to an embodiment, context information (interchangeably referred to as situational information) associated with the (desired) experience may be used (e.g., by the system) to optimize the performance of the experience. For example, according to an embodiment, the context information may include any of the following: location, user, congestion, resources, environment, etc., such as may be used to determine the devices at (e.g., the right) layers at (e.g., the right) time to be used (e.g., at any (e.g., determined) time). According to an embodiment, context changes may occur transiently (e.g., occur in a small amount of time), such as requiring (e.g., possible) reconfiguration of any part or the entire system.
[0085] A framework for specifying experiences
[0086] According to an embodiment, a (e.g., human-centric) specification and / or framework for specifying an experience may be a (e.g., fundamental) aspect of a system that provides a (e.g., optimized) human-centric immersive end-user experience, i.e., for example, a system that is (e.g., engineered) for and / or optimizes the (e.g., end-user, human-centric, etc.) experience itself. According to an embodiment, a human-centric specification (e.g., determining a particular experience of a system that provides a human-centric immersive experience) may be a (e.g., end) goal to be achieved by the system. That is, for example, a human-centric experience (and / or its specification) may focus on a user end goal, such that an object (e.g., device, entity) achieves (e.g., delivers, exists, executes, instantiates, etc.) an experience to be addressed by the system, e.g., at a particular moment in time when providing the experience.
[0087] According to an embodiment, for a human-centric specification (e.g., associated with a system that provides a human-centric experience), a user goal can be (e.g., be considered to be) a problem at hand. In the case where the end-user's desired goal (e.g., for the experience) is considered to be a problem at hand, the system can provide a program (e.g., a solution to a specific problem, an MSFC, a command, a query, etc.) for (e.g., toward) achieving the desired goal. That is, according to an embodiment, the system can provide a solution to a specific problem for solving the problem at hand, that is, (e.g., providing) the end-user's desired goal for the experience. According to an embodiment, the system can provide an optimal set of resources, such as for executing the solution to a specific problem.
[0088] Depending on the embodiment, any of the (e.g., human-centric, immersive, end-user, community, etc.) experiences and / or associated specifications or specification frameworks may (e.g., generally) be composed of any number of sub-elements (e.g., sub-experiences, sub-aspects, sub-functions, sub-routines, sub-specifications, sub-contexts, etc.). Depending on the embodiment, such sub-elements may be put together (e.g., implemented, instantiated, executed, assembled, defined, configured, etc.) for building any of the (e.g., human-centric, interactive, immersive, end-user, etc.) audio, visual, heuristic, etc. experience elements. For a system to provide (e.g., discover, determine, select, etc.) an optimal set of resources, highly human-centric experiences may (e.g., may become) increasingly complex to specify, e.g., due to their complex requirements (and constraints) and their dynamic nature.
[0089] According to an embodiment, any of refining, specifying, and / or separating a (e.g., fairly abstract, human-centric, end-user, immersive, etc.) experience can be accomplished by defining and (e.g., then) identifying any of sub-elements in a (e.g., larger, user) experience, e.g., a specification framework for use in a human-centric system. According to an embodiment, similar to refining, specifying, and / or separating an experience into sub-elements, the problem (at hand) of providing a user's experience goal can be decomposed into independently solvable sub-problems, e.g., to solve a larger problem, e.g., as described by the divide-and-conquer principle.
[0090] According to an embodiment, the sub-problems may be divided according to any of requirements (e.g., requirements associated with any of the user's end goal, the identified problem with the hand, the desired experience, etc.) and constraints (e.g., characteristics of any of the user and environment, contextual information, constraints associated with the hand and / or the required problem, etc.). According to an embodiment, the requirements associated with the experience (e.g., pertaining to, for, based on, etc.) may include, for example, any desired characteristics and (e.g., acceptable) levels (e.g., thresholds, indicators, types, etc.) of violation according to the execution experience.
[0091] In the case of device-centric (e.g., traditional and / or conventional) systems and / or experiences, for example, the solution does not consider dynamically executing functions and changing contexts and / or assumes a static set of execution points and contexts, and further (e.g., attempts to) provide a solution. In this case, the solution is an attempt to fit the whole (e.g., static set) (e.g., in the form of pre-packaged monolithic software and / or hardware operations), resulting in a sub-optimal experience. Moreover, in the case of device-centric systems, changing contextual information may exceed an acceptable level of violation of requirements in the system, resulting in a poor experience. According to an embodiment, in a human-centric (e.g., as opposed to device-centric) system, the quality of adaptability to contextual changes (e.g., dynamic components) can determine (e.g., drive) the partitioning of sub-problems, e.g., for optimization of a human-centric experience at runtime.
[0092] According to an embodiment, unknown parameters and / or states of the system and / or environment (e.g., unknown parameters and / or unknown state changes) may be discovered by a system providing a human-centric (e.g., immersive) experience, and may be used, for example, to optimize the experience. According to an embodiment, there may be a set of known parameters that are, for example, associated with a problem at the hand and / or system, and are generated when optimization of the human-centric experience occurs (e.g., during) at runtime. In the case of providing a human-centric (e.g., immersive) experience, changes in context may result in changes in any parameters and states, e.g., changes that may not have been discovered (e.g., unknown) by the system, and may (e.g., therefore) be referred to as unknown parameters and / or states (e.g., changes) of the system and / or environment. According to an embodiment, once such unknown parameters and / or states are known to the system providing the experience, they may be used to (e.g., further) optimize the experience. Depending on the embodiment, programs (e.g., operations, routines, services, resources, etc.) used to provide a (e.g., human-centric) experience can be classified into any one of at least two categories: 1) design-time operations, e.g., which can perform divide-and-conquer operations / approaches based on (e.g., identified) knowns; and 2) runtime operations, e.g., which can continuously discover unknowns and can adapt for the best experience.
[0093] According to an embodiment, the (e.g., human-centric immersive) experience is divided into any of sub-elements and sub-problems, which may vary according to the (e.g., selected) strategy for dividing such experience. That is, the task of dividing the experience into sub-elements may be performed according to (e.g., based on) the selected division strategy. According to an embodiment, the strategy for dividing the experience may be based on (e.g., based on, driven by, etc.) any of the following items (e.g., completed, driven, etc.): (1) characteristics of the experience (e.g., the user wants to emphasize the viewing experience, thus the characteristic of having D / display functions); (2) characteristics of the system (e.g., providing the experience, thus the characteristic of having better computing resources, e.g., in certain places, in a certain environment); and (3) constraints, which may, for example, be defined as critical (e.g., when considering a mobile phone-enabled experience, thus the characteristic of battery life).
[0094] According to an embodiment, an experience may be partitioned into sub-elements, which may be a set of microservices (e.g., MSFCs). For example, according to an embodiment, a design-time partitioning procedure may be performed according to (e.g., based on) a partitioning strategy, and the results of such a procedure may result in, for example, sub-elements in a larger experience as a set of microservices. For example, in the case of a simple remote video viewing experience, a set of microservices may be any of D-functions for viewing, P-functions for processing, R-functions for networking, etc. According to an embodiment, such a design-time result (e.g., a set of microservices) may (e.g., then) be an input (e.g., used by the system) for maximizing the experience at runtime.
[0095] According to an embodiment, any microservice and / or a group of microservices can be, for example, modeled as a directed graph. That is, according to an embodiment, any microservice, their interrelationships and communications (e.g., due to divide-and-conquer program construction) can be modeled as a directed graph, for example, to optimize its execution path. According to an embodiment, for example, according to (e.g., based on, using, etc.) a model of microservices, solving a user's initial problem (e.g., an end goal, a desired experience, etc.) can be (e.g., interpreted as, considered to be, associated with, subsequently considered to be, etc.) performed divide-and-conquer at design time when such microservices are identified, for example, by minimizing violations of requirements to find the (e.g., optimal) execution mode of the resulting microservices.
[0096] According to an embodiment, a service function chain (SFC) (which may be a microservice function chain (MSFC)) may be associated with (e.g., specify, instantiate, realize, etc.) a set of microservices, e.g., as a result of a design process, and the SFC may be (e.g., provide) a framework to represent the microservices along a set of (e.g., well-defined) service functions (SFs), e.g., along service function paths (SFPs). According to an embodiment, (e.g., each, any) SF may be associated with (e.g., based on well-defined) input / output (I / O) interfaces, e.g., to expose software and / or hardware operations, such as, e.g., specific problem solutions to the microservices identified in a design-time divide-and-conquer process.
[0097] Figure 3 is a schematic diagram illustrating an experience achieved through a set of linked named service functions (SFs) and / or microservices according to an embodiment.
[0098] According to an embodiment, SFC concepts may be applied to (e.g., associated with, extended to, adapted to, etc.) name-based relationships, e.g., in the context of a name-based service function forwarder (nSFF) component within an SFC framework. For example, SFC concepts may be extended to name-based relationships, e.g., because they may be used for microservices that utilize certain information (e.g., a URL such as foo.com) as an identifier. Figure 3 Such SFC concepts applied to name-based relationships are shown in FIG. According to an embodiment, implementing a (e.g., human-centric, immersive) experience may be (e.g., represented as, considered to be, etc.) an SFC, and the SF (e.g., included in the SFC) may be a component that constitutes a solution to a "divide and conquer" problem (e.g., may be a microservice associated with a sub-problem). According to an embodiment, the implementation of (e.g., such) SF may be at any layer of (e.g., involved) resources of a wider system.
[0099] According to an embodiment, for example, the problem of selecting (e.g., best possible) a runtime of a set of microservices for minimizing violations of an overall (e.g., number, requirement, threshold, etc.) experience can be formalized as (e.g., considered as, reduced to, etc.) a multi-stage dynamic programming decision process. According to an embodiment, such a multi-stage dynamic programming decision process can, for example, construct a solution to a problem (e.g., experience) based on solutions to its sub-problems (e.g., microservices).
[0100] According to the implementation scheme, selecting a suitable microservice can be performed at any (e.g., each) stage of the decision process (e.g., execution, decision, configuration, etc.). According to the implementation scheme, the cost of selecting a microservice at stage i can be shown as equation (1):
[0101] fi (d i ,s i ), ……………………Equation (1),
[0102] where d i is an allowed microservice, which can be selected from the set of all possible microservices D i Select from, and s i is the set of possible microservices available at a given stage, D i , can depend on the stage at which s i , the violation requirement of the process, which can be formally written as D i (s i ); however, for simplicity, the violation requirement of the process at stage can be expressed as D i .
[0103] According to the implementation plan, solve the problem of selecting microservices i , d i-1 The problem of optimal execution of , ..., d0 can be solved as follows, as shown in equation (2):
[0104] v=Min{f i (d i ,s i )+f i-1 (d i-1 ,s i-1 )+…+f0(d0,s0)},…Equation (2),
[0105] Affected by formulas (3) and (4):
[0106] d i ∈D, ……………………Equation (3),
[0107] v≤V, ……………………Equation (4),
[0108] where v j is the total violation requirement for allowing experience j, and v is the minimum violation requirement value achieved using the selected optimal microservice. According to an embodiment, solving the dynamic programming problem (e.g., as described above) can result in a set of optimal microservices that, once executed together, can provide the best experience. According to an embodiment, with respect to the following description of the contextual assembly of the experience, the runtime program can be used to discover (e.g., new devices and / or state devices due to context changes) and select d according to the unknown (e.g., by solving the selected d i , d i-1 , ..., the above problems of d0) to optimize the experience, and execute (e.g., selected) microservices.
[0109] Compose / instantiate microservices at any layer
[0110] For example, layering in any of computing, networking, communications, digital, etc. can be used, for example, to isolate problems in various parts of a system. In conventional systems, such as traditional computing and / or networking systems, layers are (e.g., common) agreed-upon conventions (e.g., kernel and user space components in OS) or standards for methods and / or procedures within a system (e.g., network OSI layering). In addition, components instantiated within such layers provide services and / or functions to the layers directly above them, and the components maintain such layering, for example, until there is any change in conventions or standards. A layer can be any of the following: network layer, physical layer, application layer, data layer, link layer, transport layer, session layer, etc.
[0111] According to an embodiment, for example, in the case where a user watches a 4k movie with English subtitles, the function (D function) may, when executed on the mobile device, read frames from a frame buffer in a local device memory, for example. However, in this case, when the D function is selected to be executed at a nearby TV (for example, when a high-resolution TV becomes available, or another similar change in context occurs), the next frame may be delivered to the D function over the network. According to an embodiment, in this case, if the frame is delivered to the D function over the HTTP protocol, the instance of the D function, for example, may be executed at a higher layer in the system than at a layer in the system for when the D function reads from a local frame buffer.
[0112] Figure 4 is a schematic diagram showing the experience achieved at various layers according to an embodiment.
[0113] According to the implementation scheme, for example, reference Figure 4 , for example, when optimizing the experience at runtime, each (e.g., each, all, some, several, etc.) SF can (e.g., should) dynamically select (e.g., appropriate) layers. According to an embodiment, such dynamically selected layers can be considered as, for example, a second degree of freedom of the system that provides a human-centric immersive experience. According to an embodiment, for example, as discussed above with respect to the specification framework, the implementation of a set of microservices can be represented as a chain, and the implementation of the microservices can be represented as an SF. According to an embodiment, in order to achieve interconnectivity of SFs within an SFC, names (e.g., named endpoints) can be assigned to the interfaces of the SFs, and the SFs can be linked as directed graph relationships of the named endpoints. According to an embodiment, once linked, mutual communication between two SFs can be achieved through an nSFF, which routes and / or forwards information from the SF to another (e.g., next) SF in the chain.
[0114] Figure 5is a schematic diagram illustrating a naming service function (SF) performed at various layers when nSFF implements SF interconnectivity according to an embodiment.
[0115] According to an embodiment, for example, when the execution layer of a (eg, a particular) SF can be selected at runtime, cross-layer inter-SF communication between named SFs can be implemented by nSFF, such as Figure 4 As shown. According to an embodiment, implementing nSFF may occur (e.g., instantiate, implement, execute, etc.) at the HTTP level. According to an embodiment, in addition to selecting the (e.g., best) SF, selecting the (e.g., best) execution layer for (e.g., any, each, all, etc.) SFs (e.g., and their mutual communications) may be done at runtime (e.g., when solving the (e.g., violation requirement) minimization problem), as described above.
[0116] Contextual assembly of experience
[0117] Figure 6 is a schematic diagram illustrating a device packaging entity (DPE) according to an embodiment.
[0118] According to an embodiment, for example, as described above, in the case of a device experience, such a device experience may be a dynamically determined set of service functions (SFs) that are dynamically interconnected, for example, to meet time-varying specifications (e.g., requirements and / or constraints). According to an embodiment, (e.g., specific) contributing resource components may implement the SFs, and a (e.g., specific) packaging of a set of SFs may define a human-centric experience. According to an embodiment, a device packaging entity (DPE) may, for example, dynamically assemble the SFs in a context-dependent manner to represent a human-centric experience. According to an embodiment, for example, the DPE may implement (e.g., instantiate, execute, etc.) a human experience as a transient device in the manner described above, for example, by dynamically assembling and / or packaging (e.g., the most appropriate) SFs.
[0119] In the case of a smokestack, mobile device-centric experience, the device is not transient. However, in this case, other devices are (e.g., typically) used, such as a cloud-based server that provides remote computing resources to applications running on the end-user device, the remote computing resources being used for any of mapping, video, or other services. According to an embodiment, a transient device can be a combination of any of resources and devices, such as a combination of remote computing resources and end-user devices. According to an embodiment, in a human-centric concept of experience, an end-user may not (e.g., completely) need (e.g., conceptually) utilize (e.g., singular, multiple, etc.) an end-user device (such as a smartphone). According to an embodiment, in a human-centric concept of experience, an end-user may be a transient device provided, such as one that may (e.g., purely) be defined by the transient execution of any number of experiences desired by the end-user.
[0120] According to an embodiment, a DPE may be a logical decision-making entity that is characterized by (e.g., inputs, receives, determines characteristics, etc.) any of the following: (i) SF, (ii) SFH (e.g., an entity in a system that carries the SF), and (iii) experience definitions (e.g., specifications in the form of DP models) when encapsulating the dynamic concept of a transient device. According to an embodiment, a service function endpoint (SFE) may implement the communication procedures of the SF. According to an embodiment, for example, Figure 6 As shown, a SF may be created to include any (eg, some, each, all, a subset, etc.) layers, for example, based on requirements and / or constraints.
[0121] According to an embodiment, the DPE may be executed in any number of locations, such as within a distributed system. According to an embodiment, the location may be a (e.g., equivalent) (e.g., existing) smartphone, for example, while focusing only on the assembly of the distributed execution of the experience, while (e.g., possibly) contributing resources to the execution experience. According to an embodiment, the DPE may be a software module, such as on a smartphone. According to an embodiment, the DPE may be implemented in a reduced device, such as not providing computing resources itself, but only providing the assembly of transient devices (e.g., for the purpose of service assembly). According to an embodiment, such a DPE may be a situation where the user experience is (e.g., completely) distributed and executed, and such a DPE may not involve (e.g., include) any end-user device, and may be considered to be a reduced pure DPE execution device. According to an embodiment (e.g., the only personalized aspect), such a DPE may provide a dynamic assembly of the user experience by means of a DPE function executed locally on the device. In addition, such a device may implement a human (e.g., end-user)-centric authentication service, for example, for resources for the experience.
[0122] Procedure for assembling transient devices at various layers
[0123] Figure 7 is a schematic diagram illustrating a dynamically assembled service function (SF) according to an embodiment.
[0124] According to an embodiment, the SF may be dynamically assembled based on any of encapsulating and linking device experiences, the device experience being, for example, associated with a human-centric (e.g., immersive) experience. According to an embodiment, the device experience may be any of encapsulating and linking based on any of the following: (1) a specification of a device experience provided to a DPE, for example; (2) information associated with (e.g., derived from, about, determined based on a characterization, etc.) SFs, which are available (e.g., made available, provided, etc.) to the DPE, for example; (3) the DPE selecting a set (e.g., a particular) of SFs, for example, for building the device experience; (4) the DPE initializing and / or binding the SFs with the SFH, for example, for the duration of the chain (e.g., the duration of the encapsulation period provided in the specification); and (5) starting (e.g., instantiating, executing, conducting, etc.) SF communications, for example, for the duration of the chain.
[0125] Depending on the implementation, the specifications of the device experience (e.g., hand problems, including v j As described above, etc.) can be provided to the DPE, for example, by: either a user (e.g., through a user interface, when launching a video viewing application for viewing a 4k movie); and another entity in the system (e.g., requesting one SF of another auxiliary routine consisting of a chain of subroutines). According to an embodiment, the specification of the device experience can include a trigger that, for example, specifies information associated with the event. According to an embodiment, such an event can trigger any assembly process or any other operation associated with the device experience.
[0126] According to an embodiment, a trigger may be associated with (e.g., embodied, derived from, indicated, reflected, etc.) a constraint (e.g., as described above) of a dynamic programming problem. According to an embodiment, for example, information included and / or indicated in a specification of a device experience (e.g., together with a triggering event) may include an identifier of a transient device, which may be referred to as a device ID and / or a transient device ID (TDID). It is noteworthy that the device ID and / or TDID may be different from other identifiers, such as a device-centric identifier that associates each platform with a specific execution device (such as a smartphone, such as may be used in, for example, an Android platform). According to an embodiment, a device ID (e.g., a TDID) may represent, for example, a transient identifier associated with a (e.g., human-centric) experience (e.g., different from a device-centric ID associated with a specific execution point of a potential microservice).
[0127] According to an embodiment, application requirements for the specification of device experience can be specified, for example, using an existing specification language, such as for cloud topology and / or coordination specifications (e.g., TOSCA used in the EU-FLAME project). Android developers use manifest files to specify various information about applications. According to an embodiment, for the specification of device experience, the manifest file can (e.g., also) be used to, for example, define custom specification parameters. According to an embodiment, for example, for the specification of device experience, device-local microservice installation can be combined with distributed microservice deployment, for example, through network coordination.
[0128] According to an embodiment, the DPE may have and / or use information associated with the SF. According to an embodiment, the information of the SF may be obtained, for example, by the DPE (e.g., continuously) monitoring (e.g., for) the SF, or in other words, discovering information associated with any of the known and unknown SFs, which may include a set of all possible microservice DPEs. i , as described above. According to an embodiment, the SF and / or any associated information may be any of monitored and discovered for any of its availability and utilization (e.g., in the case where an existing SF with the required hardware decoding has sufficient CPU resources to serve the new chain). According to an embodiment, the SF and / or any associated information may be any of monitored or discovered according to any of: active discovery (e.g., the DPE requests information from / about the SF of interest) or passive discovery (e.g., the SF reports information about the DPE's known interfaces).
[0129] According to an embodiment, the DPE may collect context information. According to an embodiment, context information may be collected from any (e.g., discovered, unknown) SF and other information sources (such as radio network information) associated with a specified experience, for example, thereby allowing to obtain, for example, (e.g., necessary) constraints, as described above. According to an embodiment, for example, a service discovery framework (such as multicast DNS (mDNS) or a repository-based discovery scheme) may be used to discover relevant SFs. According to an embodiment, (e.g., existing, well-known) monitoring frameworks (such as Telegraf and FLAME CLMC) may be extended to monitor, for example, SF parameters at various layers.
[0130] According to an embodiment, for example, the DPE may select a (e.g., specific) set of SFs for building a device experience by obtaining information of available SFs (e.g., information associated therewith) and a specification of the device experience that addresses a problem, for example, according to a constraint configured for matching requirements. According to an embodiment, for the DPE, for example, the specification may be (e.g., take) the following requirements: A set of SFs and any of their communication methods may be identified, for example, based on known SFs and SFHs in the system (constraints). For example, the specification may identify D-functions, P-functions, and R-functions, the duration of a continuous video viewing (e.g., experience), and may identify that the hardware decoder R, the SFE of the SF supports the PCIe communication method, for example, based on the system constraints.
[0131] According to an embodiment, the DPE may initialize and bind SFs with the SFH, e.g., for the duration of a packaging period (e.g., as provided in the specification). According to an embodiment, as part of (e.g., such) initialization process, messages may be transmitted to (e.g., corresponding) entities, e.g., for configuring their computing resources and setting up network interfaces. According to an embodiment, a set of SFs may be bound to corresponding SFHs based on either of the context ID and the device ID provided in the specification.
[0132] According to an embodiment, SF communication may be initiated, for example, for the duration of the chain. According to an embodiment, (e.g., in order to initiate SF communication), for example, the DPE may send a signal that the chain is ready to the first SF of the chain (e.g., an EXEC message of SF1). According to an embodiment, such (e.g., explicit) signaling may allow either correctness and atomic execution of the SFC to be achieved, for example, by rolling reservations (e.g., initialized) and binding of SFs on SFHs, in case of all successful SF initializations, for example, in case any SF initialization may have failed. According to an embodiment, in this case, one of the following may be performed (e.g., again): monitoring of SFs, selection of a set of SFs, and reservation and binding of SFs on SFHs until a successful SFC (e.g., its entirety) may be initialized. According to an embodiment, the explicit signaling may ensure that execution will (e.g., only) start upon availability of a (e.g., fully initialized) chain. According to an embodiment, a SPEC (e.g., specification) message may trigger encapsulation of SFs, for example, as Figure 6 shown.
[0133] Contextual assembly of experience at the application layer
[0134] According to an embodiment, a (e.g., monolithic) application may be decomposed into SFs, e.g., to be assembled (e.g., packaged) at runtime. In (e.g., conventional) cases, applications are packaged (e.g., conventionally) by application developers at design time. In such (e.g., conventional) cases, applications are (e.g., conventionally) packaged and / or distributed, e.g., for installation on a device as a single standalone application utilizing a central “play store” approach, where available applications are browsed and / or selected. In such (e.g., conventional) cases (e.g., due to the static and / or inflexible nature of the application and / or its packaging), the application user experience becomes suboptimal. According to an embodiment, an application may be decomposed into SFs, e.g., a (e.g., monolithic) application may be decomposed into SFs and may be assembled at runtime, e.g., in a manner that accommodates different context parameters, which context parameters may, for example, provide an improved user experience.
[0135] According to an embodiment, transient device properties may be implemented, for example, at the application layer. According to an embodiment, (e.g., any) device capable of running (e.g., executing, instantiating, implementing, carrying, etc.) an application SF may be (e.g., considered to be) a SFH (e.g., a mobile device, a cloud VM, etc.), for example, thereby achieving a high degree of distribution of SFs. According to an embodiment, the encapsulation program may (e.g., then) employ available SFs and SFHs at runtime, and encapsulate the application, for example, by dynamically linking the selected SFs. According to an embodiment, such encapsulation may include deployment information associated with (e.g., about, relating to, for, etc.) a host SFH (such as an available smartphone) executing the encapsulation, and deployment information associated with (e.g., about, relating to, for, etc.) a remote execution point (e.g., SFH). According to an embodiment, the deployment information may (e.g., then) be used to select (e.g., its process) (e.g., the best) execution point, for example, including an execution point on the host SFH.
[0136] According to an embodiment, a method for device-initiated service deployment through mobile application packaging can be used, for example, for any of the following: (1) deploying application-level resources on a selected SFH, for example, when the required specifications (e.g., specifications) are implemented; and (2) initializing SF programs. According to an embodiment, a method for binding a service function chain to a context-specific service instance can be used, for example, for binding (e.g., such) application-level SF to a specific SFH in the deployed system. According to an embodiment, for example, by utilizing a task offloading method for possible remote execution of partial device application functions based on dynamic offloading criteria, resources such as existing smartphones that are associated with the initial device (e.g., for belonging to, on, etc.) can be used as SFs. According to an embodiment, task offloading can be accomplished by, for example, converting local application functions into fully functional distributed SFs, which can, for example, be added to the overall selection process when selecting SFs and associated layers.
[0137] Procedure for assembling transient devices at various layers
[0138] Figure 8 is a diagram showing the use of a user controlled SF (UCSF) as a SF according to an embodiment 控制 Schematic diagram of the service function chain (SFC).
[0139] According to an embodiment, the code may take developer-provided requirements (e.g., typically taking into account user requirements, such user requirements being known or provided by end users), and may determine the types of SFs and the order in which they are to be used, e.g., to satisfy the functional requirements of an experience, such as Figure 8 shown.
[0140] According to an embodiment, the user control interface may be (e.g., assumed to be) a first SF, e.g., interacting with a user (e.g., directly) to provide control of the device, e.g., it may be a SF that accepts instructions to an 'EXEC' (e.g., execute) (e.g., SF) chain, such as Figure 7 As shown. According to an embodiment, the mapping of requirements to SF types can be accomplished, for example, using a set of preset mapping rules, which can be used in advance (e.g., mapping functional requirements to SFs provided by a user). According to an embodiment, (e.g., these) mapping rules can represent an encoding of distributed experiences, for example in the form of requirements that need to be met. According to an embodiment, the mapping rules (e.g., as described below) can be a dynamic programming model implementation, for example, allowing the monitoring constraints of the system to be continuously matched against the requirements expressed in the mapping rules. According to an embodiment, through (e.g., such) continuous matching, a set of (e.g., best, best match, etc.) service functions can be (e.g., continuously) selected.
[0141] There may be cases where there is a simple video viewing experience with no additional processing requirements. Depending on the embodiment, in this case, this case may (e.g., only) produce a 'display' and a 'receive' SF, e.g., with a mapping of control->display->receive. Depending on the embodiment, in this case, a requirements specification with a requirement to add frame processing functionality may result in a 'control'->'display'->'process'->'receive' mapping. In this case, depending on the embodiment, it may be the task of the 'developer' of the experience to determine the best mapping rules for the desired experience, e.g., together with the (e.g., appropriate) requirements and constraints to be met (e.g., to test against).
[0142] According to an embodiment, similar to the implementation (e.g., implementation) of SF itself, the description of mapping rules (e.g., deployment of dynamic programming models) can be done using an automation framework, such as Semiring or Hypergraph, for example, an automation framework that allows the expression and automated testing of constraints on requirements in deployed DP problems. According to an embodiment, in the case of an automation framework, the DP model and its tests can (e.g., become) a (e.g., intrinsic) part of the service execution, e.g., beside the SF execution itself, included in some form of description in the form of a DP programming model, such as those used in existing DP programming frameworks.
[0143] According to an embodiment, testing may be performed in a development environment, e.g., similar to emulation methods in existing mobile development tools. In other words, according to an embodiment, along with the encapsulation of service functionality, an "application package" may be (e.g., envisioned) for use on transient devices, e.g., consisting of an encoded DP programming model and SF encapsulation. According to an embodiment, the encoded DP programming model may be (e.g., then become) an input into a DPE method, e.g., to match constraints and discovered SFs to the model and its requirements.
[0144] According to an embodiment, the number of SFs that result in this mapping can be considered to be L, and all selected SF types are set Y such that L = |Y|. According to an embodiment, each y j can represent the SF type, and y0 = 'control', that is, each y j A super class may contain each SF that may be selected from the pool of discovered SFs. According to an embodiment, selecting the appropriate SF may depend on any of the neighboring and / or previously selected SFs. For example, according to an embodiment, when selecting the appropriate SF is done on a staged basis, selecting the SF may be done by iteratively matching SF types (e.g., iterating through Y, matching each element), and the order defined in Y, along with conditions such as data rates between SFs, may depend on neighboring (previously selected) SFs.
[0145] Cost function for dynamic programming model
[0146] According to an embodiment, the user experience may be encoded according to (e.g., based on, in some form, consistent with, etc.) a dynamic programming (DP) model. According to an embodiment, an explicit form of this model may be described herein, and the SW development process may use (e.g., include) a software development kit, such as an extension of an existing DP framework, such as Semiring or Hypergraph.
[0147] Depending on the embodiment, any (e.g., each, some, etc.) of the same type of SFx found may be i That is, according to an embodiment, in the case of selecting a (eg, most suitable) SF according to each SF type in a chain (eg, as in Y), a cost value may be assigned according to each SFx of the same type found. i Cost values are assigned, for example, because there may be more than one SF of the same type to be selected from, for example, a pool of discovered SFs. According to an embodiment, in the case where a number N of SFs have been discovered, x i ∈X, i=0, 1, ..., N. According to an embodiment, in the case of watching a 4k movie with English subtitles, the developer of the programming model can provide a frame rate requirement for the viewing experience as a frame-second (fps) parameter F, which can (e.g., then) be converted into a per-frame time requirement, e.g., for calculating the level of time-based violation of the requirement, as shown in equation (5):
[0148]
[0149] According to an embodiment, the time for delivering a frame can be calculated as the sum of: (1) frame transfer time (e.g., using the time taken to deliver a frame by monitoring r i The collected bit rate and the frame size S collected from the requested video source (bits), and (e.g., plus) (2) frame processing time. According to an embodiment, (e.g., this) processing time can be set to f i , expressed as the number of frames, the SF x found i Can be processed per second (e.g. during discovery, see Figure 7 ). According to an embodiment, the time to deliver a frame can be determined as shown in equation (6):
[0150]
[0151] Among them, r i is R(x i , x i-1 ), is between the chain x i and the previously selected SFx iThe data rate between 1 and 2, in bits per second.
[0152] According to the implementation plan, at each stage of decision making, r i can be determined, for example, by monitoring the corresponding network. According to an embodiment, equation (6) may be specific to the above-mentioned video use case. According to an embodiment, for example, in addition to equation (6), other instances may be optimized for any best bandwidth (e.g., expressed in Mbit / s throughput for achieving a minimum quality of experience in terms of video quality) and lowest latency and highest bandwidth, for example, using a weighting factor for the "importance" of latency to bandwidth. According to an embodiment, a DP programming coding framework (such as Semiring or Hypergraph) may be used to formulate and automatically test DP programs as well as to execute the (e.g., selected) SF instances themselves. According to an embodiment, the i-th SF (x i ) violation requirement (e.g., for the delay example) can be defined as shown in equation (7):
[0153] cost i =t i -T max Equation (7).
[0154] Violation of requirements
[0155] According to an embodiment, it can be assumed that there will be a set of SFs D that are finally selected as subsets of X (e.g., any SF d in D j ), which may (e.g., can be) used to construct an experience selected from the discovered X. According to an embodiment, equations (8) and (9) are:
[0156] d j ∈X equation (8);
[0157] and
[0158] L=|D| Equation (9).
[0159] According to an embodiment, for example, based on the above cost function, any selected group of SF(d j ∈D, i = 1, 2, ..., L) is the sum of all cost values (cost j , i=1, 2, ..., L) may (e.g., should) never be greater than zero (e.g., 0). According to an embodiment, in the case where the sum of all violated requirements is greater than zero, the selected set of SFs may (e.g., will) no longer be able to achieve the frame rate requirement F provided by the developer. According to an embodiment, for example, in this case, the sum of the total allowed violated requirements for the selected set of SFs (chains) may be considered, as shown in equation (10):
[0160]
[0161] According to an embodiment, any (e.g., each, some) of the selected SFs may (e.g., should) be available for use or linking at a given point in time. According to an embodiment, for example, outside the general discovery framework itself, there may be user-level controls to disable and / or enable specific service functions. That is, according to an embodiment, although discovery tests such availability in terms of reachability and matches with appropriate access through specific service function chains, there may be user-level controls to "disable" or "enable" specific service functions outside the general discovery framework itself. For example, an end user may decide not to expose locally available SF instances to the entire system, for example, by disabling specific instances from the service management user interface on the device, similar to disabling an application in the application management settings UI in existing mobile platforms. According to an embodiment, the availability value a of each SFj is j For example, it can be set by obtaining a value from the corresponding SF at runtime. According to an embodiment, (e.g., any) selected SF can be used based on its availability, as shown in equation (11):
[0162]
[0163] According to an embodiment, minimization of violation requirements can be tuned through SF selection, as shown in equation (12):
[0164] minimize
[0165] According to an embodiment, in the case where the minimum cost violation (e.g., as calculated by equation (12)) does not result in any selection of an SF chain that satisfies the cost constraint (e.g., the total cost remains below zero), the minimization will select the SF chain with the minimum violation cost, e.g., thereby still potentially selecting the best SF despite the experience violation.
[0166] Service function selection
[0167] According to an embodiment, the SF may be selected (e.g., completed) according to (e.g., based on) knowledge of existing SFs in the system (e.g., knowledge acquired through discovery). According to an embodiment, a set of discovered SFs X may be constructed, for example, dynamically and updated periodically as part of the discovery process discussed above. According to an embodiment, for example, a (e.g., most suitable) SF may be selected from a set of discovered SFX, set to D, such that According to an embodiment, for each SF found, x i , can be for example related to the computing power f i (For the x i, in frames per second) to obtain information.
[0168] According to an embodiment, the iterative SF selection process can: (1) iterate through Y, one element at a time, to select an appropriate SF using the minimum violation requirement represented by X, for each SF type y j Denoted by Y; (2) and filling D (e.g., which is then used to establish a "transient device" in the form of a chain of SFs in D). According to an embodiment, set temp d Maintain a set of 〖{x〗 i , cost i}Yes, where cost i It can be x i Violation requirements, and min(temp d )Retune x i , with temp d The minimum cost in i According to an embodiment, the SF selection procedure shown below may be specific to the video processing example use case and is a specific pseudo-code implementation of the identified DP procedure. According to an embodiment, a DP programming framework such as Semiring or Hypergraph may be used to determine min(temp d ), which can be used, for example, to select a representative x from a set of discovered SFs j .
[0169] According to an embodiment, the SF selection procedure may include any of the following steps:
[0170] 1. Initialize temp d ={}, D={}, i=0, j=1
[0171] 2. Obtain Y and L from the encoding (e.g., by extracting them from the additional packet information contained in the DP programming model in the appropriate description)
[0172] 3. Obtain F from the user specification and calculate T according to equation (5) max
[0173] 4. Get the 'frame size' from the video source and assign S
[0174] 5. Get X through Discovery
[0175] 6.for each y j in Y, j = 0, 1, ..., L
[0176] 7.temp d :={}
[0177] 8.for each xi of type y j in X , i=0,1,…,N
[0178] 9. Through monitoring, based on d j-1 , and a i , both get r i .
[0179] 10.ifa i =1, then
[0180] 11. From x i Get f i And calculate t according to equation (6) i
[0181] 12. Calculate cost according to equation (7) i
[0182] 13.temp d :=temp d +{x i , cost i}
[0183] 14.end if
[0184] 15. end for
[0185] 16.y j :=min(temp d )#The minimization here is calculated by the cost element of temp_d
[0186] 17.end for.
[0187] According to an embodiment, in the above SF selection procedure, a set of minimum individuals y j For example, since the selected delay constraints are additive, the sum of cost violations may also be minimized.According to an embodiment, after selecting the set Y, the binding and execution of the service function chain may (eg, now) be implemented.
[0188] According to an embodiment, the method of selecting a suitable computing resource from a resource pool and executing along a chain of selected resources can be detected, for example, by a protocol implementing the steps of the method. According to an embodiment, the dynamic nature (e.g., the formation of a truly transient device rather than a static functional chain) can be detected by creating test cases with different contextual conditions, which in turn will lead to different execution points being selected, again leading to performance changes and observed loads of the system as an indication of this transient nature of the (e.g., experience-centric) device.
[0189] in conclusion
[0190] Although features and elements are described above in particular combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. In addition, the methods described 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 non-transitory computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as built-in hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with software may be used to implement a radio frequency transceiver for a UE, WTRU, terminal, base station, RNC, or any host computer.
[0191] In addition, in the above embodiments, processing platforms, computing systems, controllers, and other devices including constraint servers and rendezvous points / servers containing processors are indicated. These devices may include at least one central processing unit ("CPU") and memory. According to the practice of those skilled in the art of computer programming, references to symbolic representations of actions and operations or instructions may be performed by various CPUs and memories. Such actions and operations or instructions may be considered to be "executing", "computer-executed", or "CPU-executed".
[0192] Those of ordinary skill in the art will appreciate that the actions and symbolic representations of operations or instructions include the manipulation of electrical signals by the CPU. The electrical system represents data bits, which may result in the ultimate transformation of electrical signals or the reduction of electrical signals and the retention of data bits at memory locations in the memory system, thereby reconfiguring or otherwise changing the operation of the CPU and performing other processing of signals. The memory location that holds the data bits is a physical location that has specific electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be understood that the exemplary embodiments are not limited to the above-mentioned platforms or CPUs, and other platforms and CPUs may also support the provided methods.
[0193] The data bits may also be maintained on computer-readable media, 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 media may include cooperating or interconnected computer-readable media that reside solely on the processing system or distributed across multiple interconnected processing systems that may be local or remote relative to the processing system. It should be understood that the representative embodiments are not limited to the above-described memories, and other platforms and memories may also support the described methods.
[0194] In an exemplary 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.
[0195] There is little difference between hardware implementation and software implementation of various aspects of the system. The use of hardware or software is usually (but not always, because in some contexts, the choice between hardware and software may become important) a design choice that represents a trade-off between cost and efficiency. There may be various media (e.g., hardware, software, and / or firmware) that can implement the processes and / or systems and / or other technologies described herein, and the preferred media may vary with the context of the deployment process and / or system and / or other technologies. For example, if the implementer determines that speed and accuracy are most important, the implementer may choose a media that is primarily hardware and / or firmware. If flexibility is most important, the implementer may choose a specific implementation that is primarily software. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.
[0196] The above detailed description has listed various embodiments of the device and / or process by using block diagrams, flow charts and / or examples. Where such block diagrams, flow charts and / or examples include one or more functions and / or operations, it will be understood by those skilled in the art that each function and / or operation within such block diagrams, flow charts or examples may be implemented individually and / or collectively by a wide range of hardware, software, firmware or nearly any combination thereof. Suitable processors include (shown by way of example) general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with a DSP core, controllers, microcontrollers, application specific integrated circuits (ASICs), application specific standard products (ASSPs), field programmable gate arrays (FPGAs) circuits, any other type of integrated circuit (IC), and / or state machines.
[0197] Although features and elements are provided above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. The present disclosure is not limited to the specific embodiments described in this patent application, which are intended to be examples of various aspects. Many modifications and variations can be made without departing from the essence and scope of the present invention, as they will be obvious to those skilled in the art. Unless explicitly provided as such, any element, action or description used in the present application specification should not be understood as being essential or necessary to the present invention. According to the foregoing description, in addition to those listed herein, functionally equivalent methods and devices within the scope of the present disclosure will be obvious to those skilled in the art. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is limited only to the terms of the appended claims and the full range of equivalent forms of such entitled claims. It should be understood that the present disclosure is not limited to a specific method or system.
[0198] It should also be understood that the terminology used herein is for the purpose of describing specific embodiments only and is not intended to be limiting. As used herein, the term "user equipment" and its abbreviation "UE" when referred to herein may mean: (i) a wireless transmit and / or receive unit (WTRU), such as described below; (ii) any of several embodiments of a WTRU, such as described below; (iii) a device with wireless functionality and / or with wired functionality (e.g., tetherable) configured with (in particular) some or all of the structure and functionality of a WTRU, such as described below; (iii) a device with wireless functionality and / or with wired functionality configured with less than all of the structure and functionality of a WTRU, such as described below; or (iv), etc. The details of the exemplary WTRU may represent any WTRU described herein.
[0199] In certain representative embodiments, 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 may be equivalently implemented in whole or in part in an integrated circuit as one or more computer programs running on one or more computers (e.g., one or more programs running on one or more computer systems), one or more programs running on one or more processors (e.g., one or more programs running on one or more microprocessors), firmware, or nearly any combination thereof, and that designing circuits and / or writing code for software and / or firmware will be well within the technical scope of those skilled in the art in light of the present disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as program products in a variety of forms, and that the exemplary embodiments of the subject matter described herein apply regardless of the specific type of signal-bearing medium used to actually perform the distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable type media (such as floppy disks, hard drives, CDs, DVDs, digital tapes, computer memory, etc.); and transmission type media (such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.)).
[0200] The subject matter described herein sometimes shows different parts contained in or connected to different other parts.It should be understood that such depicted architectures are merely examples, and in fact many other architectures that achieve the same function can be realized.In a conceptual sense, any arrangement of parts that achieve the same function is effectively "associated" so that the desired function can be achieved.Therefore, any two parts combined herein to achieve a specific function can be considered to be "associated" with each other so that the desired function is achieved, regardless of the architecture or intermediate parts.Similarly, any two parts so associated can also be considered to be "operably connected" or "operably coupled" to each other to achieve the desired function, and any two parts that can be so associated can also be considered to be "operably coupleable" to each other to achieve the desired function.Specific examples of operable coupling include, but are not limited to, parts that can physically cooperate and / or physically interact and / or parts that can wirelessly interact and / or wirelessly interact and / or parts that can logically interact and / or parts that can logically interact.
[0201] With respect to substantially any plural and / or singular terms used herein, those skilled in the art may translate from the plural to the singular and / or from the singular to the plural as appropriate, as appropriate to the context and / or application. For clarity, various singular / plural arrangements may be explicitly listed herein.
[0202] It will be understood by those skilled in the art that, in general, the terms used herein, especially in the appended claims (e.g., the bodies of the appended claims), are generally intended to be "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 "comprising" should be interpreted as "including but not limited to", etc.). It will also be understood by those skilled in the art that if a specific number of an introduced claim recitation object is intended, such intent will be explicitly stated in the claim, and in the absence of such a recitation object, there is no such intent. For example, where only one item is intended, the term "single" or similar language may be used. To aid understanding, the following appended claims and / or the description herein may contain the use of the introductory phrases "at least one" and "one or more" to introduce claim recitation objects. However, the use of such phrases should not be understood to imply that any particular claim containing such introduced claim recitation object is limited to an embodiment containing only one such recitation object by the indefinite article "a" or "an" to introduce the claim recitation object. This is true even when the same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "a kind" (e.g., "a" and / or "a kind" should be interpreted as meaning "at least one" or "one or more"). The same applies to the use of definite articles used to introduce claim recitations. In addition, even if a specific number of introduced claim recitations is explicitly recited, one skilled in the art will recognize that such recitation should be interpreted as meaning at least the stated number (e.g., a bare recitation of "two recitations" without other modifiers means at least two recitations, or two or more recitations). In addition, in those instances where a convention similar to "at least one of A, B, and C, etc." is used, generally speaking, the meaning of such construction is that one skilled in the art will understand the convention (e.g., "a system having at least one of A, B, and C" will include, but is not limited to, a system having A alone, B alone, C alone, A and B simultaneously, A and C simultaneously, B and C simultaneously, and / or A, B, and C simultaneously, etc.). In those instances where a convention similar to "at least one of A, B, or C, etc." is used, generally speaking, the meaning of such construction is that one skilled in the art will understand the convention (e.g., "a system having at least one of A, B, or C" will include, but is not limited to, systems having 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.). One skilled in the art will also understand that, in fact, any discrete words and / or phrases presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one of the terms, any of the terms, or both of the terms.For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B." Additionally, as used herein, the term "any of" followed by a listing of multiple items and / or multiple categories of items is intended to include "any of," "any combination," "any multiples," and / or "any combination of multiples" of the items and / or categories of items, either alone or in combination with other items and / or other categories of items. Additionally, as used herein, the terms "set" or "group" are intended to include any number of items, including zero. Additionally, as used herein, the term "quantity" is intended to include any quantity, including zero.
[0203] 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 described in terms of any individual member or subgroup of members of the Markush group.
[0204] As will be understood by those skilled in the art, for any and all purposes (such as for providing a written description), all ranges disclosed herein also encompass any and all possible subranges and combinations of their subranges. Any listed range can be easily identified as fully describing and enabling the same range to be divided into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein can be easily divided into a lower third, a middle third, and an upper third, etc. As will be understood by those skilled in the art, all languages such as "up to", "at least", "greater than", "less than", etc. include the cited numbers and refer to ranges that can subsequently be divided into subranges as described above. Finally, as will be understood by those skilled in the art, ranges include each individual number. Thus, for example, a group having 1 to 3 units refers to a group having 1, 2, or 3 units. Similarly, a group having 1 to 5 units refers to a group having 1, 2, 3, 4, or 5 units, etc.
[0205] Furthermore, the claims should not be read as limited to the order or elements presented unless otherwise stated. Additionally, the use of the term "means for..." in any claim is intended to invoke or means-plus-function claim format, and any claim without the term "means for..." is not intended to be so.
[0206] A processor in association with software may be used to implement the use of a radio frequency transceiver in a wireless transmit receive unit (WTRU), user equipment (UE), terminal, base station, mobility management entity (MME) or evolved packet core (EPC) or any host. The WTRU may be used in conjunction with a module and may be implemented in hardware and / or software including: a software defined radio (SDR) and other components such as a camera, video camera module, videophone, speakerphone, vibration device, speaker, microphone, television transceiver, hands-free headset, keyboard, module, a frequency modulation (FM) radio unit, a near field communication (NFC) module, a liquid crystal display (LCD) display unit, an organic light emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an internet browser, and / or any wireless local area network (WLAN) or ultra-wideband (UWB) module.
[0207] Although the present invention has been described in terms of a communication system, it is contemplated that the system may be implemented in software on a microprocessor / general purpose computer (not shown). In certain embodiments, one or more of the functions of the various components may be implemented in software controlling a general purpose computer.
[0208] Furthermore, while the invention has been shown and described herein with reference to specific embodiments, the invention is not intended to be limited to the details shown. Rather, various modifications may be made to the details within the scope and range of equivalents of the claims without departing from the invention.
Claims
1. A method performed by a device encapsulation entity DPE, the DPE being used to dynamically encapsulate or dynamically assemble a set of resources of a transient device TD that implements a user experience, the method comprising: receiving user experience information via any of user input, network signaling, and device signaling, wherein the user experience information indicates any of services, devices, and resources required according to a dynamic programming model of the user experience; Determine requirements associated with the dynamic programming model according to the user experience information; select a plurality of TD elements TDE, wherein the plurality of TDEs are selected according to the requirements associated with the dynamic programming model of the user experience, wherein the plurality of TDEs include at least one of one or more devices, one or more device components, one or more services, and one or more resources, wherein the one or more services are associated with any one of the one or more devices and the one or more device components, and wherein the one or more resources are associated with any one of the one or more devices and the one or more device components; receiving any of configuration information and context information associated with the plurality of TDEs, wherein either of the configuration information or the context information is associated with any of: resources, devices, and services associated with the plurality of TDEs; selecting one or more TDEs from the plurality of TDEs as one or more device components of the TD, wherein the one or more TDEs are selected based on: (1) any one of one or more services and one or more resources for providing the user experience, (2) any one of the configuration information and the context information, and (3) a set of resources that meet requirements associated with the dynamic programming model; Transmitting an instantiation message for configuring the TD; as well as Information is transmitted and received via the TD. 2 . The method of claim 1 , wherein any of the configuration information and the context information is received from any of one or more service functions and one or more service function hosts.
3. The method according to claim 1, wherein: The one or more device components include any number of one or more service functions and one or more service function chains, and The DPE generates the one or more service function chains. 4 . The method of claim 3 , wherein the instantiation message comprises information for instantiating any number of the one or more service functions and the one or more service function chains. The method of claim 1 , wherein the instantiation message is transmitted to any number of devices. 6 . The method of claim 1 , wherein any of the configuration information and any context information includes requirement violation information associated with the one or more device components of the TD. 7 . The method of claim 6 , wherein the requirement violation information is associated with or determined according to a cost function associated with the user experience. The method of claim 6 , wherein the one or more equipment components are selected based on minimizing violation of requirements.
9. The method of claim 1, wherein the one or more device components are associated with any number of one or more layers associated with the TD.
10. A wireless transmit / receive unit WTRU comprising a circuit, the WTRU comprising a transmitter, a receiver, a memory and a processor and executing a device packaging entity DPE, the DPE being used to dynamically package or dynamically assemble a set of resources of a transient device TD that implements a user experience, the circuit being configured to: receiving user experience information via any of user input, network signaling, and device signaling, wherein the user experience information indicates any of services, devices, and resources required according to a dynamic programming model of the user experience; determining requirements associated with the dynamic programming model based on the user experience information; selecting a plurality of TD elements TDEs, wherein the plurality of TDEs are selected according to requirements associated with a dynamic programming model of the user experience, wherein the plurality of TDEs include at least one of one or more devices, one or more device components, one or more services, and one or more resources, wherein the one or more services are associated with any of the one or more devices and the one or more device components, and wherein the one or more resources are associated with any of the one or more devices and the one or more device components; receiving any of configuration information and context information associated with the plurality of TDEs, wherein either of the configuration information or the context information is associated with any of: resources, devices, and services associated with the plurality of TDEs; Selecting one or more TDEs from the plurality of TDEs as one or more device components of the TD, wherein the one or more TDEs are selected based on: (1) any one of one or more services and one or more resources for providing the user experience; (2) any one of the configuration information and the context information; and (3) a set of resources that satisfy requirements associated with the dynamic programming model; Transmitting an instantiation message for configuring the TD; as well as Information is transmitted and received via the TD.
11. The WTRU of claim 10, wherein any of the configuration information and the context information is received from any of one or more service functions and one or more service function hosts.
12. The WTRU of claim 10 wherein: The one or more device components include any number of one or more service functions and one or more service function chains, and The DPE generates the one or more service function chains.
13. The WTRU of claim 10, wherein the instantiation message includes information for instantiating any number of the one or more service functions and the one or more service function chains.
14. The WTRU of claim 10, wherein the instantiation message is transmitted to any number of devices.
15. The WTRU of claim 10, wherein any of the configuration information and any context information includes violation requirement information associated with the one or more device components of the TD.
16. The WTRU of claim 15, wherein the requirement violation information is associated with or determined based on a cost function associated with the user experience.
17. The WTRU of claim 15, wherein the one or more device components of the TD are selected based on minimizing violation requirements.
18. The WTRU of claim 10, wherein the one or more device components of the TD are associated with any number of one or more layers associated with the TD.
