Methods for a tiered deployment of mission critical applications in a multi-access edge computing (MEC) environment

Abstract

A tiered deployment of mission critical applications in a multi- access edge computing (MEC) environment is provided herein. In an example, a wireless transmit / receive unit (WTRU) may receive a request for a MEC host status of the WTRU. Further, the WTRU may receive configuration information, including priority information for one or more service applications. Also, the WTRU may report a first level of operation, for a first service application of the one or more service applications, based upon one or more current signal conditions. Moreover, the WTRU may receive an instantiate application message responsive to the reported first level of operation. In an example, the first instantiate MEC application message is an instantiate mission critical MEC application message.

Description

METHODS FOR A TIERED DEPLOYMENT OF MISSION CRITICAL APPLICATIONS IN A MULTI-ACCESS EDGE COMPUTING (MEC) ENVIRONMENTCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 556,954, filed February 23, 2024, the contents of which are incorporated herein by reference.BACKGROUND

[0002] Multi-access edge computing (MEC), formerly known as mobile edge computing, capabilities deployed in the edge of a mobile network can facilitate the efficient and dynamic provisioning of services to mobile users. The European Telecommunications Institute (ETSI) Industry Specification Group (ISG) MEC working group, operative from the end of 2014, intends to specify an open environment for integrating MEC capabilities with service providers’ networks, also including applications from third parties.SUMMARY

[0003] A tiered deployment of mission critical applications in a multi-access edge computing (MEC) environment is provided herein. In an example, a wireless transmit / receive unit (WTRU) may receive a request for a MEC host status of the WTRU. Further, the WTRU may receive configuration information, including priority information for one or more service applications Also, the WTRU may report a first level of operation, for a service application of the one or more service applications, based upon one or more current signal conditions. Moreover, the WTRU may receive an instantiate MEC application message responsive to the reported first level of operation.

[0004] In a further example, the instantiate MEC application message may be an instantiate mission critical MEC application message Additionally or alternatively, the instantiate mission critical MEC application message is an instantiate emergency services (ES) mission critical MEC application message.

[0005] Additionally or alternatively, the instantiate MEC application message includes indication information regarding a level of service for deployment. Additionally or alternatively, the instantiate MEC application message includes a MEC application list of features. Additionally or alternatively, the instantiate MEC application message further includes a minimum rate for each feature in the MEC application list of features.

[0006] Additionally or alternatively, the WTRU is a relay WTRU. Additionally or alternatively, the WTRU reports a second level of operation based upon one or more second current signal conditions. Additionally or alternatively, the second current signal conditions are better than the first current signal conditions.

[0007] Additionally or alternatively the WTRU receives a second instantiate MEC application message. Additionally or alternatively, the first instantiate MEC application message requires a lower latency communication path for applications than the second instantiate MEC application message.BRIEF DESCRIPTION OF THE DRAWINGS

[0008] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, wherein like reference numerals in the figures indicate like elements, and wherein:

[0009] FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented;

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

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

[0012] FIG. 1D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG 1A according to an embodiment;

[0013] FIG. 2 is a system diagram illustrating an example of a multi-access edge computing (MEC) concept using a mobile communications system;

[0014] FIG. 3 is an architecture diagram illustrating an example of a European Telecommunications Institute (ETSI) MEC reference architecture;

[0015] FIG. 4 is an architecture diagram illustrating an example of a MEC deployment in a Fifth Generation of Mobile Telephony (5G) network;

[0016] FIG. 5 is a signaling diagram illustrating an example of a MEC application instantiation flow;

[0017] FIG. 6 is a signaling diagram illustrating an example of a MEC application operation flow;

[0018] FIG. 7 is a system diagram illustrating an example of emergency services in a 5G network; and

[0019] FIG. 8 is a signaling diagram illustrating an example of a MEC service availability query.DETAILED DESCRIPTION

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

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

[0022] The communications systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and / or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, 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.

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

[0024] 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 (for example, radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, and so forth). The air interface 116 may be established using any suitable radio access technology (RAT).

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

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

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

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

[0029] 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), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

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

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

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

[0033] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (for example, the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1 A may be configured to communicate with the base station 114a, which may employ a cellularbased radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0034] FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0035] 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 moremicroprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0036] The transmit / receive element 122 may be configured to transmit signals to, or receive signals from, a base station (for example, the base station 114a) over the 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 an embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0037] Although the transmit / receive element 122 is depicted in FIG. 1 B 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 (for example, multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

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

[0039] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (for example, a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the nonremovable memory 130 and / or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), 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, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

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

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

[0042] The processor 118 may further be coupled to other peripherals 138, which may include one or more software 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 e-compass, a satellite transceiver, a digital camera (for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors. The sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor and the like.

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

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

[0045] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs160a, 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 eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.

[0046] Each of the eNode-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, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0047] The CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0048] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c 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, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA

[0049] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the 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 user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

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

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

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

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

[0054] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA The traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. The peer-to- peer traffic may be sent between (for example, directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (I BSS) mode may not have an AP, and the STAs (for example, all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.

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

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

[0057] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two noncontiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0058] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11ah relative to those used in 802.11n, and 802.11ac. 802.11 af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 ah may support Meter Type Control / Machine- Type Communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (for example, only support for) certain and / or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (for example, to maintain a very long battery life).

[0059] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802 11 n, 802.11ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11 ah, the primary channel may be 1 MHz wide for STAs (for example, MTC type devices) that support (for example, only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle.

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

[0061] FIG. 1 D is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an NR 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.

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

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

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

[0065] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0066] The CN 106 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

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

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

[0069] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an 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 DL packets, providing mobility anchoring, and the like.

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

[0071] In view of FIGs. 1A-1 D, and the corresponding description of FIGs. 1A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

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

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

[0074] Multi-access edge computing (MEC), formerly known as mobile edge computing, capabilities deployed in the edge of a mobile network can facilitate the efficient and dynamic provisioning of services to mobile users. The European Telecommunications Institute (ETSI) Industry Specification Group (ISG) MEC working group intends to specify an open environment for integrating MEC capabilities with service providers’ networks, also including applications from third parties.

[0075] FIG. 2 is a system diagram illustrating an example of a MEC concept using a mobile communications system. As shown in an example in system diagram 200, one or more of a WTRU 202, loT device 203, or a connected vehicular device 205 may access a mobile operator’s network 206 via one or more of base stations 214a, 214b, 214c. Further, the WTRU 202, loT device 203, or a connected vehicular device 205 may thereby access one or more of applications 220, 230, 240. Additionally or alternatively, WTRU 202, loT device 203, or connected vehicular device 205 may thereby access one or more of services 225, 235, 245. Additionally or alternatively, one or more of applications 220, 230, 240 or services 225, 235, 245 may be deployed in one or more of edge clouds 227, 237, 247 to provide distributed computing capabilities. Additionally or alternatively, loT device 203, connected vehicular device 205, or both, may access the mobile operator’s network 206 via a WTRU, which may be a relay WTRU, which may in turn access one or more of base stations 214a, 214b, 214c.

[0076] Additionally or alternatively, the mobile operator’s network 206 may allow network access to third- parties 212, such as via an application programming interface (API) 250. These distributed computing capabilities will make available information technology (IT) infrastructure as in a cloud environment, such as central cloud 280, for the deployment of functions in mobile access networks.

[0077] FIG. 3 is an architecture diagram illustrating an example of an ETSI MEC reference architecture. An example shown in architecture diagram 300 includes the ETSI MEC reference architecture with the functional elements that comprise the mobile edge system and the reference points between them.

[0078] As shown in an example in FIG. 3, there are three groups of reference points defined between the system entities. One group includes reference points regarding the mobile edge platform functionality (Mp). Another group includes management reference points (Mm). A further group includes reference points connecting to external entities (Mx).

[0079] The mobile edge system consists of the mobile edge hosts 310, 320 and the mobile edge management necessary to run mobile edge applications within an operator network or a subset of an operator network. The mobile edge host, such as mobile edge hosts 310, 320, is an entity that contains a mobile edge platform, such as mobile edge platforms 315, 325, and a virtualization infrastructure 330 which provides compute, storage, and network resources, for the purpose of running mobile edge applications, such as mobile edge applications 332, 334, 336. The mobile edge platform is the collection of essential functionalities required to run mobile edge applications on a particular virtualization infrastructure and enable them to provide and consume mobile edge services.

[0080] Mobile edge applications, such as mobile edge applications 332, 334, 336, are instantiated on the virtualization infrastructure of the mobile edge host based on configuration requests validated by the mobile edge management. The mobile edge management comprises the mobile edge system level management and the mobile edge host level management. The mobile edge system level management includes the mobile edge orchestrator 380 as its core component, which has an overview of the complete mobile edge system.

[0081] The mobile edge host level management comprises the mobile edge platform manager 350 and the virtualization infrastructure manager 360, and handles the management of the mobile edge specific functionality of a particular mobile edge host and the applications running on it. Recently, the ETSI MEC has approved a new work item (DGR / MEC-0036ConstrainedDevice), titled “MEC in resource constrained terminals, fixed or mobile” and incorporated by reference herein, which aims at studying how terminal units, mobile hosts and personal devices can be used to support cloud computing at the edge

[0082] Examples are provided herein of deployment of MEC in a Fifth Generation of Mobile Telephony (5G) network. The ETSI MEC ISG released a whitepaper, incorporated by reference herein, (ETSI MEC, “Mobile Edge Computing (MEC); Edge Platform Application Enablement,” ETSI GS MEC 011 V3.1.1, 2022-09) illustrating and explaining ways to deploy and integrate MEC in the 5G architecture, focusing “on the opportunities for MEC to benefit from the edge computing enablers of the 5G system specification, and for 3GPP ecosystem to benefit from the MEC system and its APIs as a set of complementary capabilities to enable applications and services environments in the very edge of mobile networks."

[0083] The design approach taken by 3GPP allows the mapping of MEC onto Application Functions (AFs) that can use the services and information offered by other 3GPP network functions based on the configuredpolicies. In addition, a number of enabling functionalities were defined to provide flexible support for different deployments of MEC and to support MEC in case of user mobility events.

[0084] FIG. 4 is an architecture diagram illustrating an example of a MEC deployment in a 5G network The ETSI MEC whitepaper proposes the approach shown in architecture diagram 400 to deploy MEC in an integrated manner with 5G. In the MEC system on the right-hand side of FIG. 4, the MEC orchestrator 410 is a MEC system level functional entity that, acting as an AF, can interact with the Network Exposure Function (NEF) 480, or in some scenarios directly with the target 5G NFs. On the MEC host level it is the MEC platform 430 that can interact with these 5G NFs, again in the role of an AF. The MEC host, i.e. the host level functional entities, are most often deployed in a data network in the 5G system. While the NEF 480 as a Core Network function is a system level entity deployed centrally together with similar NFs, an instance of NEF can also be deployed in the edge to allow low latency, high throughput service access from a MEC host. The white paper also assumes that MEC is deployed on the N6 reference point, i.e. in a data network 450 external to the 5G system.

[0085] Different MEC deployment scenarios are also identified. Logically MEC hosts are deployed in the edge or central data network and it is the User Plane Function (UPF) 460 that takes care of steering the user plane traffic towards the targeted MEC applications in the data network 450. In terms of physical deployment of MEC hosts, there are multiple options identified in current platform proposals, including one or more of the following. One option includes the MEC and the local UPF 460 collocated with the base station. Another option includes the MEC collocated with a transmission node, possibly with a local UPF 460. A further option includes the MEC and the local UPF collocated with a network aggregation point. An additional option includes the MEC collocated with the Core Network functions, such as in the same data center.

[0086] FIG. 5 is a signaling diagram illustrating an example of a MEC application instantiation flow. The flow of application instantiation is depicted in an example found in signaling diagram 500. One or more steps of the flow are from ETSI GS MEC 010-2 V3.1 1 (2023-06), incorporated by reference herein.

[0087] In an example shown in FIG. 5, an Operations Support System (OSS) 520 initiates the instantiation with a Process Request Message to an MEC Orchestrator (MEO) 530. In an example, the Process Request Message may be an instantiate application request. The instantiate application request is locally realized and relayed to an MEC Platform Manager (MEPM) 550. Resources Allocation is then requested from the MEC Platform. Accordingly, a resource allocation request is sent to a Virtualized Infrastructure Manager (VIM) 560 by the MEPM 550. Next, the VIM 560 will indicate in a Resource Allocation Response to the MEPM 550 if there are available resources.

[0088] Subsequently, configuration requests and responses are exchanged if there are available resources. In an example, the MEPM 550 sends a configuration request to a MEC Platform (MEP) 570. The MEP 570 then sends a configuration message for a MEC application instantiation 580. Further, the MEP 570 sends a configuration response to the MEPM 550.

[0089] Finally, the MEO 530 and OSS 520will receive indication if application instantiation was successful. For example, MEPM send an instantiate application response to MEO 530. Further, MEO 530 forwards the instantiate application response to OSS 520 The instantiate application response is either successful or unsuccessful.

[0090] This, however, will cause problems for high priority Emergency Service (ES) applications where it is preferable to run them in a state with less features rather than not at all. A choice between a completely successful or completely unsuccessful instantiate application response is too rigid for the more detailed needs of ES applications. The ES applications will have different levels of service based upon availability of resources. Many Mission Critical Applications will require a lower latency communication path in order to deliver the higher priority data in a timely manner to the network. In addition, higher reliability is also key to Mission Critical Applications that include Emergency Services even if the data throughput is reduced for the system. An example of services that may be provided are Extended Reality (XR) including video for first responders, push to talk (PTT) communication between first responders and real time sensor information. While all those features may be desirable, if network conditions preclude the operation of XR video for example, PTT communication and sensor information should still be relayed. Even in marginal network conditions, it still would be desirable to only transmit sensor information even if that was the only segment of the service available.

[0091] FIG. 6 is a signaling diagram illustrating an example of a MEC application operation flow. An example in signaling diagram 600 shows how MEC Application Operation proceeds. One or more steps of the flow are from ETSI GS M EC 010-2 V3.1.1.

[0092] The following steps are included in the current procedure to instantiate operational flow from MEC. The OSS 620 sends an operate application request to the MEC Orchestrator 630 In an example, the operate application request is an operate application instance request. Additionally or alternatively, the operate application request is a start application request. Additionally or alternatively, the operate application request is a stop application request. The MEC Orchestrator 630 forwards the operate application request to the MEC Platform Manager 650. The MEC Platform Manager 650 processes this request, and sends the result of operation on the application instance once the operation completes. For example, the MEPM 650 send an operate application response to the MEO 630. Further, the MEC Orchestrator 630 sends the result of application operation to the OSS 620

[0093] There is no current mechanism to increase or decrease resources and functionality for a given application which may be required for mission critical applications. Currently, MEC does not currently allow for scalability of supported features within an application. An intent of the examples and embodiments in this invention is to allow for scalability of those supported features.

[0094] Embodiments and examples provided herein consider Mission Critical Applications in a MEC network, of which Emergency Services (ES) is an example where the ES voice and data communication will have priority over other traffic in a network. Also, embodiments and examples provided herein consider thescenario where the network may be compromised due to an emergency and a scaled down level of service is preferable to no service at all. This would require a tiered level of service.

[0095] FIG. 7 is a system diagram illustrating an example of emergency services in a 5G network. An example in system diagram 700 shows Mission Critical Applications 770 within a 5G Network, and the relationship between other applications, such as 5G vertical applications 760, and Emergency Services Applications that are considered Mission Critical Applications 770.

[0096] In an example shown in FIG 7, a WTRU may access a 5G RAN 704, which facilitates access to a 5G CN 706 Further, through NEF 780, the 5G RAN 704 provides the WTRU with access to 5G services 750. The 5G services 750 includes mission critical services 720, service frameworks 730 and vertical enablers 740. The service frameworks can be implemented in the core network or in Edge Applications. In addition, the vertical enablers will facilitate implementation in 5G enabled infrastructure. The Mission Critical Applications 770 may draw on the mission critical services 720. Further, the 5G vertical applications 760 may draw on the service frameworks 730 and vertical enablers 740.

[0097] In an example shown in FIG 7, as the WTRU moves and the wireless conditions change, it is key to select the right host for Emergency Services Applications when the MEC apps are instantiated. The WTRU should be capable of providing its specific reliability and availability requirements for the best MEC application instantiation, as well as be aware of the status updates, so it can react to them (for example, via changes at the application level).

[0098] The embodiments and examples provided herein include solutions to enable additional messages or fields in messages to indicate priority and a tiered level of services based upon signal quality. For example, solutions provided herein include new messages or modified messages to support ES tiered application instantiation. Also, example solutions provided herein include new messages or modified messages to support ES tiered application operations. Further, embodiments and examples provided herein may support ES applications in the event that the emergency conditions that exist may compromise the system and require a fallback of features and services

[0099] Embodiments and examples provided herein include procedures to enable a WTRU to instantiate applications available from a MEC host based upon priority and a tiered level of features based upon available signal quality and available resources. Example solutions include a MEC host requesting status of a WTRU to determine an available level of service. Also, example solutions include a WTRU being configured with priority to service applications such as Emergency Services to ensure a level of service. Moreover, example solutions include a WTRU reporting a current level of operation based upon current signal conditions to the MEC host.

[0100] In order to support instantiation and operation of Mission Critical MEC applications and other application software that requires a tiered level of operation, the existing API specified in the ETSI GS MEC 010-2 V3.1.1 (2023-06) needs to be modified. An intention of several example modifications provided herein is to support a prioritization of the ES applications. In addition, several example modifications provided herein willnot require a minimum set of system operational parameters but will have a tiered set of features depending upon signal and system conditions, in examples.

[0101] Examples provided in the following include modifications of MEG application instantiation. Procedures and tables involving MEC may be modified in examples provided herein.

[0102] FIG. 8 is a signaling diagram illustrating an example of a MEC service availability query. A query procedure may begin with a MEC Instantiate Application Request, as shown in an example in signaling diagram 800. Specifically, a MEC Orchestrator is provided with list of application throughput and processing requirements as part of configuration data when selected by the MEC host and corresponding MEC Platform Manager 870. The MEC orchestrator currently makes a Boolean decision, go or not to go. Further, the life cycle management (LCM) operation will deploy high priority mission critical and emergency services applications even if insufficient resources are not available; limited or even full service may become available.

[0103] When the Virtualization Infrastructure Manager (VIM) receives a resource allocation request from the MEPM, the MEPM will pass a tiered capability list along to the VIM The VIM will provide the application image as usual but for high priority ES applications will provide allocation regardless of resource requests.

[0104] Further, a resource allocation response will be returned. In addition to success, the response may provide a current list of possible configurations and requirements for each configuration.

[0105] Also, a configuration request may be sent by MEC Platform Manger which includes traffic rules to be configured, DNS rules and required and optional services The list of services may be increased to be a list of services based upon signal conditions. In an example, the request may include an additional enumerated list with capabilities as a function of a quality of device capability, for example, signal strength. The configuration message will specify which functionality to currently deploy Moreover, a configuration response and instantiate application response may indicate a current level of operation.

[0106] As shown in an example in FIG. 8, a MEC application instance 880 may send a request for MEC host status to a MEC platform 870. In an example, the request may query the services based on a serjnstancejd. Additionally or alternatively, the MEC application instance 880 may operate on a network node, such as a gNB, an edge node or another edge device. Additionally or alternatively, the MEC platform 870 may operate on a WTRU. Additionally or alternatively, the WTRU may be a relay WTRU. Further, the request for MEC host status may be, or may be included in, a GET message which may include the serjnstancejd 810. Also, the request may include an additional enumerated list with capabilities as a function of a quality of device capability, such as signal strength, for example 820.

[0107] In addition, the MEC platform 870 may send a response back to MEC application instance 880 The response may be a 200 OK message and include a list of service information 830.

[0108] Additionally or alternatively, the request from the MEC application instance 880 may query the services based on ser_name, in an example, the request for MEC host status may be, or may be included in, a GET message which may include the serjiame 840 Also, the request may include an additional enumerated list with capabilities as a function of a quality of device capability, such as signal strength, for example 850.

[0109] Moreover, the MEC platform 870 may send a response back to MEC application instance 880. The response may be a 200 OK message and include a list of service information 860.

[0110] Examples provided in the following include modifications of messages for application instantiation. The URI query parameters supported by the GET method on this resource table may be modified to include the following parameter. In ETSI GS MEC 011 V3.1.1 (2022-09), Table 8.23.3.1-1 may be modified to add the additional parameter, Mission Critical Application List of Features, as shown below in Table 1Table 1

[0111] Also, Table 8.1.2.2-1 , Attributes of Serviceinfo, may be modified to add the additional parameters, Mission Critical Application List of Features and Priority, as shown below in Table 2.Name Data Type Cardinality RemarksTable 2

[0112] In ETSI GS MEC 010-2 V3.1.1 (2023-06), Table 6.2.1.2.2-1, Attributes of AppD data type, may be modified as shown below. Although the entire Table 6.2 1.2.2-1 is not copied below, Table 3 includes the modification, including the additional parameters, Mission Critical Application List of Features, Mission Critical Application Priority and Priority, as shown below.

[0113] Examples provided in the following include modifications of M EC application operation. For example, a MEC Operate App Instance Request currently either sends a start or stop instruction. In an example modification, the MEC Operate App Instance Request may send a list of features of the desired application to activate based upon priority and current conditions to the MEC Orchestrator.

[0114] In another example, the MEC Operate App Instance Response may be modified. For example, the result of the App Instance Request will list which features of the application were currently activated.

[0115] Examples are provided herein of modifications to MEC application operation. In ETSI GS MEC 011 V3.1.1 (2022-09), Table 7.1.4.4-1, Attributes of AppReadyConfirmation, additional fields may be required to determine the level of service and priority currently enabled. The additional fields may include Priority and Level of service, as shown below in T able 4.Table 4

[0116] In an example, a WTRU may receive a request for a MEC host status of the WTRU. Additionally or alternatively, the WTRU may be a relay WTRU. Further, the WTRU may receive configuration information, including priority information for one or more service applications. Also, the WTRU may report a first level of operation based upon one or more current signal conditions. Additionally or alternatively, the first level of operation is a first current level of operation. Moreover, the WTRU may receive an instantiate MEC application message responsive to the reported first level of operation.

[0117] In a further example, the instantiate MEC application message may be an instantiate mission critical MEC application message Additionally or alternatively, the instantiate mission critical MEC application message is an instantiate emergency services (ES) mission critical MEC application message.

[0118] Additionally or alternatively, the instantiate MEC application message includes indication information regarding a level of service for deployment. Additionally or alternatively, the instantiate MEC application message includes a MEC application list of features. Additionally or alternatively, the instantiate MEC application message further includes a minimum rate for each feature in the MEC application list of features.

[0119] Additionally or alternatively, the WTRU reports a second level of operation based upon one or more second current signal conditions. Additionally or alternatively, the second current signal conditions are better than the first current signal conditions. Additionally or alternatively, the second level of operation is a second current level of operation.

[0120] Additionally or alternatively the WTRU receives a second instantiate MEC application message. Additionally or alternatively, the first instantiate MEC application message requires a lower latency communication path for applications than the second instantiate MEC application message.

[0121] Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. 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 computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magnetooptical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0122] Further, while the methods described herein are often described as implemented in a WTRU, one of ordinary skill in the art will appreciate that methods may be implemented in other devices, such as wireless devices. Examples are such wireless devices include a base station, a gNB, an AP, a STA, a UE, a vehicle, a vehicular device, and an loT device.

Claims

CLAIMSWhat is claimed:

1. A method for use in a wireless transmit / receive unit (WTRU), the method comprising: receiving a request for a multi-access edge computing (MEC) host status of the WTRU; receiving configuration information, including priority information for one or more service applications; reporting a first level of operation for a first service application of the one or more service applications , wherein the first level of operation is reported based upon one or more first current signal conditions; and receiving a first instantiate MEC application message responsive to the reported first level of operation.

2. The method of claim 1 , wherein the first instantiate MEC application message is an instantiate mission critical MEC application message.

3. The method of claim 2, wherein the instantiate mission critical MEC application message is an instantiate emergency services (ES) mission critical MEC application message.

4. The method of claim 1 , wherein the instantiate MEC application message includes indication information regarding a level of service for deployment.

5. The method of claim 1 , wherein the instantiate MEC application message includes a MEC application list of features.

6. The method of claim 5, wherein the instantiate MEC application message further includes a minimum rate for each feature in the MEC application list of features.

7. The method of claim 1, wherein the WTRU is a relay WTRU.

8. The method of claim 1 , further comprising: reporting a second level of operation for a second service application of the one or more service applications, wherein the second level of operation is reported based upon one or more second current signal conditions, wherein the second current signal conditions are better than the first current signal conditions; and receiving a second instantiate MEC application message responsive to the reported second level of operation, wherein the first instantiate MEC application message requires a lower latency communication path for applications than the second instantiate MEC application message.

9. A wireless transmit / receive unit (WTRU) comprising: a transceiver; and a processor, operatively coupled to the transceiver; wherein: the transceiver is configured to receive a request for a multi-access edge computing (MEC) host status of the WTRU; the transceiver is configured to receive configuration information, including priority information for one or more service applications; the transceiver and the processor are configured to report a first level of operation for a first service application of the one or more service applications , wherein the first level of operation is reported based upon one or more first current signal conditions; andthe transceiver is configured to receive a first instantiate MEC application message responsive to the reported first level of operation.

10. The WTRU of claim 9, wherein the first instantiate MEC application message is an instantiate mission critical MEC application message11. The WTRU of claim 10, wherein the instantiate mission critical MEC application message is an instantiate emergency services (ES) mission critical MEC application message.

12. The WTRU of claim 9, wherein the instantiate MEC application message includes indication information regarding a level of service for deployment.

13. The WTRU of claim 9, wherein the instantiate MEC application message includes a MEC application list of features.

14. The WTRU of claim 13, wherein the instantiate MEC application message further includes a minimum rate for each feature in the MEC application list of features.

15. The WTRU of claim 9, wherein the WTRU is a relay WTRU.

16. The WTRU of claim 9, wherein: the transceiver and the processor are further configured to report a second level of operation for a second service application of the one or more service applications, wherein the second level of operation is reported based upon one or more second current signal conditions, wherein the second current signal conditions are better than the first current signal conditions; and the transceiver is further configured to receive a second instantiate MEC application message responsive to the reported second level of operation, wherein the first instantiate MEC application message requires a lower latency communication path for applications than the second instantiate MEC application message.

Images