WO2025160424A1 - Methods and apparatus for enabling service function chaining for split aiml computing in wireless systems - Google Patents

Abstract

In some implementations, a method may include detecting an event triggering a creation of a split artificial intelligence machine learning (AIML) process. In addition, the method may include sending, to a network server, a service chain (SC) create request, where the SC create request includes SC characteristics used in creating a SC profile and a SC. The method may include receiving, from the network server, a SC create request response indicating a created SC and an associated SC profile, where the associated SC profile is based, at least in part, on the SC characteristics, and where the associated SC profile includes at least information on a first SC node to send intermediate data and an information on a second SC node from which inference results of the SC will be received or which the WTRU will subscribe to receive the inference results. The method may be performed by a WTRU.

Description

METHODS AND APPARATUS FOR ENABLING SERVICE FUNCTION CHAINING FOR SPLIT AIML COMPUTING IN WIRELESS SYSTEMS

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63/625,198, filed January 25, 2024 the contents of which are incorporated herein by reference.

BACKGROUND

[0002] Artificial Intelligence Machine Learning (AIML) Split Inference (SI) is generally known as a technique for decentralizing the process of performing AIML inference using a trained model. AIML-SI may comprise different AIML models which may be executed on different hardware to derive inference result(s) and/or prediction(s). As an example, in a wireless environment, AIML-SI may enable the offload of compute-intensive operations to the network while keeping privacy sensitive data in the wireless device (e.g., UE). Edge Computing (EC) is an essential component for enabling responsive AIML-SI applications in mobile networks. EC may enable the delivery of extremely low latency services to a UE by provisioning these services near the edge of the network, i.e., in close proximity of the UE.

SUMMARY

[0003] A system of one or more computers can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on the system that in operation causes or cause the system to perform the actions. One or more computer programs can be configured to perform particular operations or actions by virtue of including instructions that, when executed by data processing apparatus, cause the apparatus to perform the actions.

[0004] In one general aspect, a method may include detecting an event triggering a creation of a split artificial intelligence machine learning (AIML) process. The method may also include sending, to a network server, a service chain (SC) create request, where the service chain create request includes SC characteristics used in creating a SC profile and a SC. The method may furthermore include receiving, from the network server, a SC create request response indicating a created SC and an associated SC profile, where the associated SC profile is based, at least in part, on the SC characteristics, and where the associated SC profile includes at least information on a first SC node to send intermediate data and an information on a second SC node from which inference results of the SC will be received or which the WTRU will subscribe to receive the inference results Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods. [0005] Implementations may include one or more of the following features. The method where the network server includes a SC management function (SCMF). The method may include: discovering a plurality of SC nodes; and selecting one or more SC nodes from the plurality of SC nodes discovered. The method where discovering the plurality of SC nodes may include at least one of sending a domain name system (DNS) resolution request to an edge application server discovery function (EASDF) or sending an edge application server (EAS) discovery request to an edge enabler server (EES). The method where the SC create request includes an indication of the selected one or more SC nodes. The method, where the event triggering the creation of the split Al M L process is at least one of: an event triggered by an application client residing on the WTRU or a notification received from a network. The method where the associated SC profile further includes one or more of: a SC identifier (SCID), an SC model (SCM), an SC size, or SC node identifiers (SCNIDs), and where each SC node is associated with an application that is an AIML model. The method where each SCNID includes at least one of: a respective SC node role (SCNR) identifier; a respective SC node position (SCNP) identifier; or respective SC node application characteristics (SCNAC) identifiers. The method and where the SCNAC include at least one of: an application identifier, an application type, application version information, an application size identifier, or application capability requirements. Implementations of the described techniques may include hardware, a method or process, or a computer tangible medium.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] 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:

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

[0008] 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;

[0009] 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;

[0010] 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;

[0011] FIG. 2 illustrates an example of a sequential AIML-SI where models are chained to form a three stage AIML-SI model;

[0012] FIG. 3 illustrates an example of a data-parallel AIML-SI where a model is used in parallel instances of application functions; [0013] FIG. 4 illustrates an example of model-parallel AIML-SI for combined prediction;

[0014] FIG. 5 illustrates an example of a model-parallel AIML-SI example for distributed prediction;

[0015] FIG. 6 illustrates a high-level view of the SC lifecycle;

[0016] FIG. 7 illustrates an example process for creating a Service Chain;

[0017] FIG. 8 illustrates an example of a Service Chain management procedure;

[0018] FIG. 9 illustrates an example of a Service Chain Management Function with Service Function Chaining traffic forwarding and proxying system flows; and

[0019] FIG. 10 is a flow diagram of an example process for creating a Service Chain.

DETAILED DESCRIPTION

[0020] The following acronyms may be referred to in the description that follows:

5GC 5G Core

5GS 5G System

AC Application Client

ACID Application Client Identifier

AIML Artificial Intelligence Machine Learning

AS Application Server

CAS Cloud Application Server

CN Core Network

DL Downlink

DN Data Network

EAS Edge Application Server

EASDF Edge Application Server Discovery Function

ECS Edge Configuration Server

EDC Edge Discovery Client

EDN Edge Data Network

EEC Edge Enabler Client

EEL Edge Enablement Layer

EES Edge Enabler Server

FQDN Fully Qualified Domain Name

IE Information Element

LTE Long Term Evolution e.g., from 3GPP LTE R8 and up NEF Network Exposure Function

NF Network Function

PCF Policy Control Function

PDU Packet Data Unit

PSA PDU Session Anchor

RAN Radio Access Network

SC Service Chain

SC5PI Service Chain 5GC SFC Policy Information

SCA Service Chain Analytics

SCACID Service Chain Allowed Consumer Identifier

SCANID Service Chain Allowed Node Identifier

SCAU Service Chain Allowed UE

SCCCID Service Chain Current Consumer Identifier sees Service Chain Current State

SCER Service Chain Environmental Rules

SCID Service Chain Identifier

SCMF Service Chain Management Function

SCM Service Chain Model

SCNAC Service Chain Node Application Characteristics

SCNC Service Chain Node Configuration

SCNID Service Chain Node Identifier

SCNP Service Chain Node Position

SCNR Service Chain Node Role

SCNSI Service Chain Node Subscription Information

SCOID Service Chain Owner Identifier

SCS Service Chain Size

SCT Service Chain Type

SCTD Service Chain Traffic Descriptor

SI Split Inference

SFC Service Function Chaining

SFF Service Function Forwarder

SMF Session Management Function TSP Traffic Steering Policies

UE User Equipment

UL Uplink

UPF User Plane Function

URI Universal Resource Identifier

URL Universal Resource Locator

[0021] 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, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), singlecarrier FDMA (SC-FDMA), zero-tail 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.

[0022] 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 (ON) 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-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

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

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

[0025] 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).

[0026] 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).

[0027] 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). [0028] 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.

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

[0030] 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. [0031] 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 (e.g., 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 (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) 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.

[0032] 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, etc., 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.

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

[0034] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 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.

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

[0036] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), 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.

[0037] The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in 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.

[0038] 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 (e g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116. [0039] 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.

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

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

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

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

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

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

[0046] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In 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.

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

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

[0049] 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

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

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

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

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

[0055] 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 (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.

[0056] 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 (e.g., 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 (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

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

[0058] 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).

[0059] 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 (e.g , only support for) certain and/or limited bandwidths The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0060] 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 (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes. Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle. [0061] 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.11 ah is 6 MHz to 26 MHz depending on the country code.

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

[0063] 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 the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).

[0064] 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 (e.g., containing a varying number of OFDM symbols and/or lasting varying lengths of absolute time).

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

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

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

[0068] 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 (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of 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-3GPP access technologies such as WiFi.

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

[0070] 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. [0071] The CN 106 may facilitate communications with other networks For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers 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.

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

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

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

[0075] Edge computing for wireless cellular networks is a feature described in 3GPP specifications; it was introduced in Rel-17 and subsequently enhanced in Rel-18 and Rel-19. The edge computing feature enables a WTRU to discover low latency services that are offered in proximity of a WTRU; the feature also defines service continuity capabilities that maintain low latency services connectivity as WTRU mobility happens. Two distinct edge computing frameworks have been specified by 3GPP.

[0076] An edge computing framework is available within the 5G core network and is described in 3GPP TS 23.548 - 5G System Enhancements for Edge Computing (Release 18). This framework is mostly network based and offers a basic set of edge computing capabilities designed to have minimal impacts on WTRU implementation. On the WTRU, an optional Edge Discovery Client (EDC) is defined as a support function to help with DNS discovery of edge servers. On the network side, the Edge Application Server Discovery Function (EASDF) may act as a DNS server to help resolve DNS requests for discovery of Edge Application Servers (EAS). The framework main functions include EAS discovery and EAS relocation.

[0077] A different edge computing framework is available as an application Edge Enablement Layer (EEL) above the 5G core network and below the application layer. This framework is described in 3GPP TS 23.558 - Architecture for enabling Edge Applications (Release 18) and follows the Service Enablement Architecture Layer (SEAL) principles and offers a richer set of edge computing capabilities. On the WTRU, an Edge Enabler Client (EEC) acts as an agent that interacts with edge functional entities located in the network to provide Application Clients (ACs) with edge functionality. On the network side, the Edge Configuration Server (ECS) and Edge Enabler Server (EES) functional entities provide the EEC with the necessary functionality to discover and use edge services offered throughout the network. The framework main functions include service provisioning, EAS discovery, service continuity and planning, dynamic EAS instantiation, support for various group use cases (e.g., group of WTRU instances using an EAS, bundles of EAS providing a service, etc.).

[0078] Both frameworks may co-exist and have different functional entities and capabilities. Comparatively, the EAS discovery offered in each framework differs; for example, in the 5G core network, EAS discovery is based on DNS protocols and use the EASDF, while in the edge enablement layer, EAS discovery is realized using a dedicated HTTP procedure between the EEC (UE) and an EES.

[0079] The delivery of end-to-end services often require using diverse services; the steering of traffic through these services is termed Service Function Chaining (SFC). In 3GPP wireless networks, SFC is a capability offered by the 5G core network that allows an Application Function (AF) to use the Network Exposure Function (NEF) Traffic Influence API to indicate an SFC Policy identifier in order to activate traffic classifiers in the data path. It is to be noted that the SFC functionality defined in 3GPP is limited to traffic classification and excludes the service function forwarding functionality related to SFC.

[0080] SFC policies are (pre-)provisioned in the Policy Control Function (PCF) and indicate a set of Traffic Steering Policies (TSP); on SFC policy activation, the PCF requests the Session Management Function (SMF) to configure the UPF with traffic steering rules according to the defined TSP(s). The AF are pre-configured with available SFC policy identifiers.

[0081] SFC in the wireless network requires a business agreement between the operator and the Application Service Provider (ASP) such that SFC policies are provisioned in the PCF. An operator needs to provision SFC policies in the PCF, and the ASP needs to configure the SFC policy identifiers in the AF, according to the operator provisioned SFC policies.

[0082] Operation splitting between AIML endpoints has been identified as promising technology that should be supported in wireless systems. Split AIML inference is a technique for decentralizing the process of performing AIML inference using a trained model. AIML Split Inference (AIML-SI) consist in using different AIML models, usually executed on different hardware, to derive inference result(s) and/or prediction(s) For example, in a wireless environment, the benefits may be to keep privacy sensitive data in the UE while offloading compute intensive data to the network.

[0083] FIG. 2 illustrates an example of a sequential AIML-SI where models are chained to form a three stage AIML-SI model. The first stage, 202, may be located on a WTRU 204 as an Application Client or service of WTRU 204, and Model A 206 may represent the chain head. Model A 206 may produce stage 1 intermediate results 210 (e.g., stage 1 intermediate dataset) based on analytics 208 available at WTRU 204. The stage 1 intermediate dataset 210 may be delivered to a second stage of inference 212. Stage 2, 212, inference may be offered by an AF as a service, and stage 2 may use Model B 214 to perform inference based on stage 1 intermediate dataset 210 and analytics 216 available in the network. Stage 2 inference 212 may produce a stage 2 intermediate dataset 218 that may be delivered to a third stage 220 of inference. Stage 3, 220, inference may be offered by an AF as a service, stage 3 inference 220 may represent the tail of the AIML-SI, stage 3 may use Model C 222 to perform inference based on stage 2 intermediate dataset 218, and stage 3 inference may derive a result 224. The result of the AIML-SI may be consumed by WTRU 204 or AF 226 to perform an action according to the AIML-SI result.

[0084] FIG. 3 illustrates an example of a data-parallel AIML-SI where a model is used in parallel instances of application functions In this example, the stage 1 intermediate dataset provided to each stage 2 model may be different; a data-parallel AIML-SI model may be used when results need to be obtained in a time sensitive manner. The result of the AIML-SI may be consumed by a WTRU or an AF to perform an action according to the AIML-SI result.

[0085] As illustrated in FIG. 3, The first stage, 302, may be located on a WTRU 304 as an Application Client or service of WTRU 304, and Model A 306 may represent the chain head. Model A 306 may produce stage 1 intermediate results 310a, 310b, and 310c (e.g., stage 1 intermediate datasets) based on analytics 308 available at WTRU 304. The stage 1 intermediate dataset 310a may be delivered to a first stage 2 inference 312a, a second stage 2 inference 312b, and a third stage 2 inference 312c. The first stage 2 inference 312a may use Model B 314a to perform inference based on stage 1 intermediate dataset 310a and analytics 316a available in the network. First stage 2 inference 312a may produce result 318a.

[0086] The stage 1 intermediate dataset 310b may be delivered to a second stage 2 inference 312b. Second stage 2 inference 312b may use Model B 314b to perform inference based on stage 1 intermediate dataset 310b and analytics 316b available in the network. Second stage 2 inference 312b may produce result 318b. The stage 1 intermediate dataset 310c may be delivered to a third stage 2 inference 312c Third stage 2 inference 312c may use Model B 314c to perform inference based on stage 1 intermediate dataset 310c and analytics 316c available in the network. Third stage 2 inference 312c may produce result 318c. Model 314c may represent the chain tail. Each data set 310a, 310b, and 310c may be different. The result of the AIML-SI, 320a and/or 320b, may be consumed by WTRU 304 or AF 322 to perform an action according to the AIML-SI result. [0087] FIG. 4 illustrates an example of model-parallel AIML-SI for combined prediction In the example of FIG. 4, different AIM L models are used in parallel instances of application functions. The model-parallel AIML- SI illustrated in FIG. 4 may consume intermediate results from different domains, for example from the UE, the RAN, and the CN, to produce a combined inference result or prediction.

[0088] As illustrated in FIG. 4, The first stage of inference, 402, may be located on a WTRU 404 as an Application Client or service of WTRU 404, and Model A 406 may represent the chain head. Model A 406 may produce stage 1 intermediate results 410 (e.g., stage 1 intermediate datasets) based on analytics 408 available at WTRU 404. The stage 1 intermediate dataset 410 may be delivered to a fourth stage of inference 428. A second stage of inference 412 includes Model B 414 that may produce stage 2 intermediate results 418 based on analytics 416 available at second stage 412. Second stage 412 may deliver stage 2 intermediate results 418 to fourth stage 428.

[0089] A third stage of inference 420 includes Model C 422 that may produce stage 3 intermediate results 426 based on analytics 424 available at third stage 420. Third stage 420 may deliver stage 3 intermediate results 426 to fourth stage 428. Fourth stage of inference 428 includes Model D 430 that may produce stage 4 results 434 based on intermediate results 410, 418, and 426 Model 430 may represent the chain tail. Stage 4 results 434a and/or 434b may be provided to WTRU 404 or AF 436

[0090] FIG. 5 illustrates and example of a model-parallel AIML-SI example for distributed prediction.

[0091] In the examples of FIG. 4 and FIG. 5, different AIML models are used in parallel instances of application functions. The model-parallel AIML-SI illustrated in FIG. 5 may consume intermediate results from a single domain, for example from the UE, to produce distributed inference results or predictions. The result(s) of the AIML-SI may be consumed by a WTRU or an AF to perform an action according to the AIML-SI result.

[0092] As illustrated in FIG. 5, the first stage, 502, may be located on a WTRU 504 as an Application Client or service of WTRU 504, and Model A 506 may represent the chain head. Model A 506 may produce stage 1 intermediate results 510a, 510b, and 510c (e.g., stage 1 intermediate datasets) based on analytics 508 available at WTRU 504. The stage 1 intermediate dataset 310a may be delivered to a second stage of inference 512, a third stage of inference 514, and a fourth stage of inference 516. The stage 2 inference 512 may use Model B 518 to perform inference based on stage 1 intermediate dataset 510a and analytics 520 available in stage 2 512. Stage 2 inference 512 may produce result 522.

[0093] The stage 1 intermediate dataset 310b may be delivered to third stage of inference 514. Third stage of inference 514 may use Model C 542 to perform inference based on stage 1 intermediate dataset 510b and analytics 526 available in stage 3. Stage 3 inference 514 may produce result 528. The stage 1 intermediate dataset 310c may be delivered to fourth stage of inference 516. Fourth stage inference 516 may use Model D 530 to perform inference based on stage 1 intermediate dataset 310c and analytics 532 available in stage 4. Stage 4 inference 516 may produce result 534. Model D 530 may represent the chain tail. Each data set 510a, 510b, and 510c may be different. The result of the AIML-SI 536a and/or 536b may be consumed by WTRU 504 or AF 538 to perform an action according to the AIML-SI result. [0094] It should be appreciated that in the above examples of AIML-SI, the consumer(s) of the AIML-SI results may be the tails of the AIML-SI chain and may be a single entity such as a WTRU or an AF or may be multiple consumers.

[0095] The 5G Core Network (5GC) EEL framework provides capabilities for discovering groups of EAS, referred to as EAS bundles. The EEL supports two types of EAS bundle: the direct EAS bundle and the composite EAS bundle.

[0096] The direct EAS bundle is represented by a group of EAS instances (e.g., AFs) accessed directly by a WTRU and managed as a group; examples of a topology similar to a direct bundle are the ones shown in FIG. 3 and FIG. 5.

[0097] The composite EAS bundle is represented by a group of EAS instances where only one instance may be accessed by the WTRU; FIG. 2 shows an example of a topology similar to a composite bundle

[0098] EAS bundles may be topologically similar to split AI/ML models but have limitations preventing the realization of split AI/ML computing scenarios.

[0099] To benefit from usage of AIML technology, wireless networks need to provide capabilities to support AIML applications that can be implemented using various AIML models. As AIML models complexify, it is necessary to support decentralized AIML models to minimize power consumption on the WTRU (e.g., by limiting inference processing and data transmission), and to preserve privacy of sensitive information. Support of applications that use split AIML models represent an opportunity for mobile networks operators to allow users to benefit from complex AIML models while retaining battery life and preserving privacy.

[0100] Supporting applications that use split AIML models in mobile networks presents several challenges. A first challenge is related to discovery and chaining of application functions to form AIML split inference pipelines. Specifically, existing Edge Application Server (EAS) discovery capabilities need to be enhanced to support the different split AIML models, SEC is a ON capability which may not be available (e.g., it is optional, it is not supported when roaming and needs pre-provisioned SEC policies by the operator).

[0101] A second challenge is related to determining and informing entities participating in the AIML split inference chain about the chain structure and configuration (e.g., head, tail, result consumer, next stage and related WTRU(s)). For example, the result consumer(s) (e.g , WTRU, AF, or both) need to be informed of the split AIML chain tail to subscribe for obtaining inference results, in another example, split AIML chain intermediate nodes or tail need to know the WTRU(s) for which the result applies to. A third challenge is related to supporting AFs that are SFC encapsulation aware and unaware or a combination of both.

[0102] Accordingly, Service Function Chaining and Edge Computing enhancements are motivated by requirements of AIML applications. Usage of complex AIML models on a WTRU may not be possible due to the WTRU limited capabilities, such as WTRU reduced computing capabilities, constrained battery life and limited availability of network analytics. Split AIML inferencing is a technique that may be utilized to enable usage of complex AIML models on WTRU s with such capability limitations. A WTRU AIML inferencing is a use case that may leverage existing network capabilities such as Edge Computing (EC) and Service Function Chaining (SFC). EC may allow offloading compute-heavy inferencing while maintaining low communication latency; SFC may allow forming Service Chains dynamically which may be needed when Al M L models needs to be updated. A Service Chain Management Function (SCMF) capability may be offered as a service. In one example, the SCMF may be implemented as a standalone service, e.g., as an Application Function (AF) or Network Function (NF) In another example, the SCMF may be implemented as an extension of an existing service. The SCMF framework may not be limited to AIML split inferencing; the framework may be applicable to other split computing use cases.

[0103] The Service Chain Management Function (SCMF) allows a WTRU or an Application Function (AF) to configure and manage Service Chain(s) within the mobile network The SCMF may offer a service to manage SC chains, the service may be offered to SC users via an Application Programming Interface (API) The SCMF functionality may be implemented as a standalone Application Function (AF) or as a Network Function (NF). The SCMF functionality may be combined with an existing AF or NF, and the API may be offered as an extension of an existing API.

[0104] The SCMF service may be offered using a communication protocol, for example the Hyper Text Transfer Protocol (HTTP) or the Non-Access Stratum (NAS) protocol for 5G systems may provide the capabilities for offering the SCMF service.

[0105] The SCMF may create SC profile resources and may offer capabilities to manage SC profile resources. There may be one SC profile for each SC managed by the SCMF. The SC profile resource may be created, discovered, enabled, disabled, modified, or deleted at the SCMF. The SCMF may enable concurrent management of multiple SC profiles (e.g., SC chains) and may offer the SCMF service to multiple concurrent SC owners and SC consumers.

[0106] FIG. 6 illustrates a high-level view of the service chain lifecycle. The Service Chain (SC) owner may be a WTRU or an AF, and the SC lifecycle may be composed of three phases. At 602, the SC owner may request the SCMF to create a SC, and the SCMF may create a SC profile based on information provided by the SC owner. The SC profile may include information that uniquely identifies the SC and may include information describing the SC structure and operation.

[0107] At 604, the SC owner may request the SCMF to perform management operations on the Service Chain, and the SCMF may provide the SC owner or SC consumers with requested information or information related to event of the SC. Management operations may include creating, configuring, enabling, disabling, or modifying the SC Requested or notified information may include SC discovery information, SC results information, SC usage information or SC analytics information. At 606, the SC owner may request the SCMF to terminate the SC, and the SCMF may release resources associated with the SC.

[0108] A SC profile may describe how services are chained together and may reflect the operational status of the SC. The SC profile may be composed of multiple Information Elements (lEs) reflecting static and dynamic aspects of the SC. For example, static aspects may include SC nodes (e.g., head, tail, intermediate), the SC owner, and the SC consumers. For example, dynamic lEs may include current SC consumers or SC analytics, such as the average combined SC inference time or the average inference time of each SC stage.

[0109] The Service Chain Type (SCT) may uniquely identify a type of Service Chain. The SCT may be associated with pre-provisioned SCs, or, in other words, a SC template. The SCT may indicate predefined lEs of a SC profile. For example, a given SCT may provide the SC model, SC size, SC node information, SC 5G SFC policy information, 5G traffic descriptor, etc. The SCT may be used to facilitate discovery or creation of a SC by a SC owner. A system may be pre-provisioned with a set of predefined SCTs. Custom SCs may be created by a SC owner; the SCT of a custom SC should be globally unique. A SCT may be associated with a subset of lEs of a SC profile such that it allows the SCMF to form a complete SC profile using information determined from the SCT and information provided at SC creation.

[01 10] The Service Chain Identifier (SCID) IE may uniquely identify a Service Chain instance. The SCID may be provided by the SC owner when the SC profile is created or may be assigned by the SCMF when the chain is provided by the SCMF. The SC profile may include both an external SCID assigned by the SC owner and an internal SCID assigned by the SCMF. The SCIDs may be used by the SC owner, the SC users, the SC consumers or the SCMF to identify an instance of a SC.

[01 11] The Service Chain Model (SCM) may identify the model of SC. A SC model may indicate the structure of a SC, for example the SC model may indicate that the SC is a sequential SC or a parallel SC. Further, the SC model may indicate that the SC is for data-parallel or model-parallel processing. It can be appreciated that the provided examples represent common SC models and that additional SC models may be possible. The SC model can be used by the SC owner to indicate the general structure of the desired SC and by the SC users, the SC consumers or the SCMF to understand the general structure of the SC. The SC model may be used to influence the interactions with the SC

[01 12] The Service Chain Size (SCS) may identify the number of stages within a Service Chain If the chain is sequential, the SC size may represent the number of stages, or inference in the case of AIML, that happens before a result is available. This parameter may also indicate capabilities of a SCMF, for example a SC profile provided to a SC owner after creating a SC may indicate a minimum and maximum chain size supported by the SCMF; these values may be used by the SC owner when modifying the SC

[01 13] The Service Chain Nodes Identifiers (SCNID) may uniquely identify each node within a Service Chain and may be associated with information that allows to communicate with that node. For example, a node may be an Application Client (AC) of a WTRU or an Application Function (AF) of a network (e.g., an Application Function (AF), an Application Server(AS), an Edge Application Server (EAS) or a Cloud Application Server (CAS)). The SCNID of an AC may indicate for example an ACID identifying an AC and a UE/WTRU identifier (e g., GPSI) or UE IP address to uniquely identify the node. The SCNID of an AF may for example include a Fully Qualified Domain Name (FQDN), a Universal Resource Locator (URL), a Universal Resource Identifier (URI) and an IP address to uniquely identify the node. It can be appreciated that the SCNID may be a complex type composed of a SCMF issued identifier and node connectivity information (e.g., GPSI, FQDN, IP address, etc.) The SCNID may be used by the SCMF when managing the SC chain or by the SC owner, user, or consumers to access the SC nodes.

[01 14] For each SCNID, the Service Chain Node Role (SCNR) may identify the role of the node instance within the chain. The first node of a chain may have the SC head role; the SC head may be where the first inference of the chain happens and where the first intermediate dataset may originate. The last node of a chain may have the SC tail role; the SC tail may be where the last inference of the chain happens and where the results or prediction may be produced. The nodes that are not head or tail may be intermediate nodes that consume intermediate datasets and produce intermediate datasets. A SC typically has a single head and a single tail; however, data-parallel, or model-parallel chains may have several heads and/or several tails.

[01 15] For each SCNID, the Service Chain Node Position (SCNP) may identify the position (e.g., stage) of the node instance within the chain. The SC head may have the first node position within the chain; the SC tail may have the last node position within the chain; intermediate nodes may be ordered between the SC head and SC tail position. SC node position may be a numerical value, or may be indicated using chained SCNID (e g., previous SCNID, next SCNID). For example, a SC head node may have a next SCNID and no previous SCNID, a SC tail node may have a previous SCNID and no next SCNID and an intermediate node may have both previous and next SCNID.

[01 16] For each SCNID, the Service Chain Node Application Characteristics (SCNAC) may identify the application or service performed by the SC node, including the application characteristic. For example, application characteristics may indicate the application identifier, the application type (e.g., AIML model for communications, AIML model for video, AIML model for voice, AIML model for energy efficiency, etc.), the application version information (e.g., application version, API version, trained model version, etc.), application size, application capabilities (e.g., SFF requirements, SFC proxy requirements, etc.). It should be understood that an application may be an AI/ML model, and an application identifier/version/size/capability may be used interchangeably with an AI/ML model identifier/version/size/capability.

[01 17] For each SCNID, the Service Chain Node Configuration (SCNC) may identify the configuration of the node instance within the chain A SC node instance may be involved in multiple SC, may process traffic related to multiple WTRU(s), and may have the capability of performing diverse types of processing. The SC node configuration represents a configuration, or parameters that may be provided to the SC node instance when performing processing on data related to a SC profile.

[01 18] For each SCNID, the Service Chain Node Subscription Information (SCNSI) may identify the notification endpoints and capabilities of the AF nodes within the SC. This information may be used to notify AFs participating in the SC of events related to the SC. The SCMF may use this information for notifying AFs of that an AF is added to a SC, or that a SC has been modified

[01 19] The Service Chain 5GC SFC Policy Information (SC5PI) may indicate if the SFC capability of the 5GC is used. This information element may indicate to the SCMF that a SFC policy is provisioned in the PCF and may indicate to the SCMF that it should be used. The SCMF may use the SFC policy Information to invoke the Nnef_Trafficlnfluence API to request the SMF to apply the policy in the UPF. The 5GC SFC Policy Information may include a SFC policy identifier that indicates the provisioned policy that may be used, traffic descriptors to which the policy applies, the identifiers of WTRUs to which the policy applies, spatial validity conditions, and may contain information about AF supporting SFC. It may be appreciated that the 5GC SFC policy may be used in conjunction with the SCMF.

[0120] The Service Chain Owner Identifier (SCOID) may indicate the identity of the SC manager. The SC owner may perform management operations on the SC, including providing a SC profile, controlling the state of the SC, and terminating the SC. Based on the SC owner, the SCMF may authorize operations on the Service Chain.

[0121] The Service Chain Traffic Descriptor (SCTD) may identify the traffic that can be provided to a SC. The SC F may use the SC traffic descriptor to enable a 5GC SFC policy, accept or reject traffic sent to the SCMF. The AF participating in a SC can use the SC traffic descriptors to accept or reject traffic sent to the AF. [0122] The Service Chain Allowed UE (SCAU) may identify the WTRU(s) allowed to use the SC. Based on the allowed WTRU, the SCMF may authorize a WTRU to use a SC; SC allowed WTRU may indicate all WTRUs, a group of WTRUs, or a single WTRU. The allowed WTRUs can provide inferencing inputs in the SC.

[0123] The Service Chain Allowed Consumers Identifiers (SCACID)may identify the allowed consumers of the SC information. Based on the allowed consumer identities, the SCMF may authorize a consumer to obtain information about the Service Chain, including results, node information and key performance indicators. The allowed consumer may include an allowed WTRU when the same WTRU provides inference inputs and consumes inference results of a SC.

[0124] The Service Chain Allowed Nodes Identifiers (SCANID) may indicate the allowed nodes that can participate in the SC. Based on the allowed nodes identifiers, the SCMF may authorize an allowed node to participate (e.g., be inserted) in a SC, and may authorize an allowed node to obtain or produce information about the Service Chain, including node information and analytics.

[0125] The Service Chain Current Consumers Identifiers (SCCCID) may identify consumers currently subscribed to receive SC information. Current consumers list is updated as consumers subscribe or unsubscribe to/from receiving SC information. SC current consumers may be used by the SCMF to notify SC consumers about available information related to the SC chain (e.g., new result available, SC state change, etc.)

[0126] The Service Chain Current State (SCCS) may indicate if the SC is enabled or disabled. An enabled SC pipeline is configured and allowed to exchange information to deliver results. A disabled SC pipeline is configured and not allowed to exchange information to deliver results. The SC state may be changed by the SCMF based on request from the SC owner or other environmental factors (e.g., time, location, etc.)

[0127] The Service Chain Analytics (SCA) may provide analytics related to the SC operation For example, analytics may be the overall processing time of the SC, the processing time per SC node, the bandwidth consumed between SC nodes (e.g., required for intermediate data), the time of the latest processed result, transmission delays. The SCMF and the nodes may compute the SC analytics and make them available to the SC owner or SC consumers.

[0128] The Service Chain Environmental Rules (SCER) may provide rules for managing the SC chain based on environmental conditions. The SCMF may associate conditional environmental rules with the SC profile such that the SC may be conditionally enabled, disabled, or deleted. For example, the SCMF may associate location rules with a SC profile such that the SC may exist only in given location(s). For example, the SCMF may associate time validity rules with a SC profile such that the SC may exist at a certain time. For example, the SCMF may associate slice validity rules with a SC profile such that the SC may exist only if all the SC nodes are within a given slice. Additional conditional environmental rules are possible, such as rules based on SC analytics (e g., idle time, processing time, etc.), rules based on a WTRU presence, rules based on an AC or AF availability, etc.

[0129] In one example, an application in the WTRU may require a Service Chain (SC). The application may inform the WTRU that it requires creation of a SC and it may indicate the services needed to form the chain and the requirements for the services and/or the chain.

[0130] The WTRU may perform discovery of services needed to form the SC. The WTRU may send a DNS resolution request or an EAS discovery request or a combination of both to a DNS server, or EASDF or EES server.

[0131] The WTRU may receive a DNS resolution response or EAS discovery response containing a list of (Edge) Application Services that can be used for forming the SC. The response(s) may indicate services requested for forming the SC.

[0132] The WTRU may perform a service selection based on the SC requirements. Based on the service selection, the WTRU may send a SC create request to the Service Chain Management Function (SCMF). The request may include SC characteristics needed to form a SC profile, or a SC profile.

[0133] The WTRU may receive a SC create response from the SCMF The response may indicate that a SC has been created, and may provide a SC profile or a SC profile identifier. The WTRU may obtain information needed by the application from the SC profile, such as the SC head or tail information. The WTRU may inform the application requiring a SC about the obtained information.

[0134] On the WTRU, the application may use information about the SC. As an example, the application may send intermediate data to the SC head. As another example, the application may subscribe to the SC tail to obtain SC results.

[0135] In one example, the SCMF may receive a SC create request from a WTRU. The request may include SC characteristics needed to form a SC profile, or a SC profile. The SCMF may verify if the SC characteristics include SC nodes information. If the request does not include SC node information, the SCMF perform discovery of services needed to form the SC. The SCMF may send a DNS resolution request or an EAS discovery request or a combination of both to a DNS server, or EASDF or EES server.

[0136] The SCMF may perform a service selection based on the SC characteristics received in the request. The SCMF may create a SC profile based on SC characteristics received in the request and the discovered services needed for the SC. The SCMF may send a notification to a subscribed service about participation in the SC. The notification may include a SC profile or a SC profile identifier The SCMF may receive a notification response from the service. The notification response indicating if the service accepted participation in the SC. The SCMF sending a SC create response to the WTRU. The response may indicate a SC profile or a SC profile identifier. The WTRU using information from the SC profile to send intermediate information to the SC and to obtain SC results.

[0137] FIG. 7 illustrates an example process for creating a Service Chain At 712, AF 710 that may participate in SC may send a registration request to SCMF 704 for service. The registration request may include an identifier of AF 710 and a notification endpoint that SCMF 704 may use to notify AF 710. Additionally, the request may include notification filters indicating which notification events may be sent to AF 710, and information related to capabilities of AF 710, such as support of the SFC encapsulation or number of allowed simultaneous SC sessions. Upon receiving the request, SCMF 704 creates a subscription resource for the registering AF, the resource information may be based on information provided in the request.

[0138] At 714, an event may happen in the SC owner 702 that requires creating a SC. In a first example, SC owner 702 may be an AC located on a WTRU; the triggering event may be a user starting the AC; the AC may be an AIML application that requires split AIML inferencing; the AC may trigger a SC create request for a split AIML SC with SCMF 704, and the request may be sent directly with the SCMF or triggered via an enablement layer application such as an Edge Enabler Client (EEC) 708. In a second example, the SC owner 702 may be an AF located in a data network of a wireless network; the triggering event may be a notification sent to the AF by the 5G core network indicating the registration of a WTRU; the AF may be an AIML application that requires split AIML inferencing; the AF may create a split AIML SC with the SCMF, and the request may be sent directly to the SCMF or triggered via a Network Exposure Function (NEF)

[0139] The SC owner may perform a service selection of the service instances that are needed to form the SC. If the SC owner is preconfigured with information required to request SC creation (e.g., service instances, SCID, etc.), the SC owner may proceed directly to 724. If the SC owner is configured with service identifiers (e g., service types) that are needed to form the SC, the SC owner may perform a service discovery and service selection.

[0140] If the SC owner is capable of discovering service instances using the DNS functionality or via an Edge Discovery Client (EDC), the SC owner may send a DNS request at 716 to a DNS 706 server or to an Edge Application Server Discovery Function (EASDF). The request may include the FQDN of a service to be included in the SC If the SC to be formed requires several services, the SC owner may repeat the request for discovering different services (e g., different FQDNs). For use cases where several service instances of the same service are needed (e.g , data-parallel SI model), the SC owner may repeat the request using the same FQDN which may result in different service instances if DNS round robin is enabled in the DNS server. If DNS round robin is not supported, an enhancement to the DNS protocol may allow the DNS client to indicate to the server how many instances of a requested service are desired in the DNS response. The DNS server or EASDF 706 may send a DNS response to the requestor at 718, including the connectivity information (e.g., endpoint address) of the requested service; the response may include connectivity information to multiple instances of a service

[0141] If the SC owner 702 is capable of discovering service instances using the EAS discovery functionality or via an Edge Enabler Client (EEC), the SC owner may send an EAS discovery request 720 to Edge Enabler Server (EES) 708. The request may include EAS identifier(s) (EASID) of services to be included in the SC. If the SC to be formed requires several services, the request may include several EASIDs. Alternatively, the EAS discovery capabilities for EAS bundles (e.g., direct bundles or composite bundles) may be used if available. For use cases where several service instances of the same service are needed (e.g., data- parallel SI model), the SC owner may obtain several EAS instances in the response according to the EES server implementation. Otherwise, an enhancement to EAS discovery may allow the EAS discovery client to specify the number of requested instances in the EAS discovery response. The EES 708 may send an EAS discovery response to the requestor at 722, including the connectivity information (e.g., endpoint address of the requested service; the response may include connectivity information to multiple instances of a service.

[0142] The SC owner 702 may select the discovered service instances that may be used in the SC at 724. [0143] It should be appreciated that the SC owner may be preconfigured with information required to request SC creation such that 716-724 are not performed. It can further be appreciated that the SC owner may be pre-configured with a preexisting SCTs or SCIDs available in the network such that 716-724 are not performed. It can further be appreciated that the SC owner 702 may retrieve existing SCRs or SCIDs available in the 5GS. These examples are not shown in the figure.

[0144] At 726, SC owner 702 may send the SC create request to SCMF 704. The request may include one or more information elements as described in previous paragraphs. The request may include a SC type, a SCID identifying the SC, a SC model indicating the SC structure, a SC size indicating the number of stages, SCNID(s) indicating services within a SC, SC nodes roles and position defining the structure of the SC, SC nodes configuration defining parameters or configuration of a SC node within a SC, SC node subscription information indicating how to notify the node, 5GC SFC policy information indicating if 5GC SFC is used, SC owner identifier identifying the SC owner, SC allowed consumer and nodes indicating consumers and nodes that can use or participate in the SC, and SC environmental rules indicating validity conditions of the SC. Parameters not included in the request may be provided by the SCMF and included in the SC profile at 730.

[0145] At 728, upon receiving the SC create request, the SCMF 704 may perform service discovery and selection as described in 716-724, if the request does not include connectivity information for all service required by the SC. Otherwise, if the connectivity information is present, SCMF 704 proceeds to 730. [0146] At 730, SCMF 704 creates the SC profile resource based on the information provided in the SC create request and the service selection performed by SCMF 704 if necessary.

[0147] At 732, SCMF 704 sends a notification to the service instances that are selected for the SC chain. The AFs notification information may be obtained from the AF subscription AT 712. If the AF has not subscribed AT 712, the AF may be automatically subscribed based on AFs notification information provided in the SC create request, or from the SCMF selected services at 728. The notification may include information from the SC profile, may provide an indication that the AF has been added to a SC, and may provide information about the SC structure (e.g , previous node, next node, SC tail). Upon receiving this notification, AF 710 may prepare to participate in the SC, for example the AF may create the necessary resources for handling SC intermediate datasets, may initialize an AIML model, may create resources for storing analytics related to the SC chain, may establish connectivity to other AFs.

[0148] At 734, AF 710 may send a SCMF notification response to SCMF 704 to indicate if the AF is capable of participating to the SC. If the AF cannot be added to the SC, the SCMF notification response may indicate a failure and a reason.

[0149] At 736, SC F 704 sends a SC create response to SC owner 702. The response may indicate if the SC create request was successful and may include the SC profile of the SC. The SC owner may be automatically subscribed to receive notifications from the SCMF when events associated with the SC happens. Upon receiving the SC create response, if the SC owner is a consumer of SC results, the SC owner may subscribe to the SC tail node, as indicated by the SC profile, to receive the SC results and may take actions according to the received results.

[0150] It should be appreciated that the SCMF may be a function; that the SCMF function may provide a service; that the SCMF function may be implemented as an independent application server; and/or that the SC F may be implemented as part of any existing application server, such as an EES or an EASDF.

[0151] When the SCMF is implemented in an EES or an EASDF, it can further be appreciated that the AF registration to SCMF service (712), e.g., registration between AF and SCMF, may be the registration procedure that happens between an EAS and an EES or EASDF; and it can be further appreciated that the process at 728 , e.g., between the SCMF and EES or EASDF, may be internal to the EES or EASDF.

[0152] FIG. 8 illustrates an example Service Chain management procedure

[0153] At 808, the requestor 802 (e.g., SC owner or SC consumer) may discover information about existing SC instances. The requestor 802 may send a SC discover request 808 to the SCMF 804; the SC request may include SC discovery information according to information elements of the SC profile, for example the SC type may be included in the discovery request to discover SC instances of that type, and other lEs of the SC profile may be included to discover SC instances. The SC discovery information may be used by SCMF 804 to filter existing SC profiles for the purpose of discovery. For example, the SC discover request may include SCID(s) used by the SCMF 804 to identify SC profile(s) matching the SCIDs. For example, the SC discover request may include SCNID(s) used by the SCMF to identify SC profiles containing such SCNID(s), or expressed differently, identify in which SC the SCNID(s) may participate Any of the information elements described in the SC profile may be included as discovery filters in the SC discover request.

[0154] Upon receiving the SC discover request, SCMF 804 may identify the SC profiles matching the parameters of the discovery filters included in the request. The SCMF may send a successful SC discover response 810 to the requestor; the response may include the SC profiles matching the received discovery filters. If SCMF 804 has not discovered any SC profiles, the response may indicate failure and may include a failure reason

[0155] The requestor 802 (e.g., SC owner) may enable or disable a SC. The requestor may send a SC enable request or SC disable request 812 to SCMF 804; the request may include information identifying SC chain(s) (e.g., SCID(s)); the SCID(s) may be used by the SCMF to identify SC profile(s) Upon identifying SC profile(s), SCMF 804 may send a SC enable or SC disable notification(s) 814 to the AF(s) (e.g., SC node(s)) 806 participating in the SC chain. The notification may include SCID(s); and the AF 806 may use the SCID included in the notification to identify traffic associated with the SCID and may respectively start or stop processing the identified traffic. SCMF 804 may send a SC enable response or SC disable response to the requestor at 816; the response may contain an indication of success if the SC chain was successfully enabled or disabled and may include an indication of failure and a failure reason otherwise.

[0156] The requestor 802 (e g., SC owner or SC consumer) may obtain report information about existing SC(s); the report may be initiated by any of the AF(s) 806 participating in the SC or by the SCMF 804.

[0157] When the report is initiated by an AF participating in the SC, the AF 806 may send a SC report request 818 to SCMF 804; the report request may include SCID(s) and information about analytics or state of the AF For example, the request may include analytics (e.g., time, size, processing delay, etc.) on the latest dataset treated and associated with the provided SCID or may include information about the experienced transmission delays or processing overload associated with the provided SCID or may include information about the latest produced data (e.g., intermediate data or result) associated with the SCID. Upon receiving the SC report request, the SCMF may store analytics data, either locally or in an analytics service such as the Application Data Analytics Enablement Framework (ADAES), modify the SC chain, or notify subscribers as at 826. SCMF 804 may send a SC report response 820 to the reporting AF 806 to indicate that the report was received successfully or may indicate a failure and a cause to the AF.

[0158] When the report is initiated by the SCMF (e.g., polled), SCMF 804 may send a SC report notification 822 to the AF 806; the SC report notification may include SCID(s), and information requested from the AF. For example, the request may indicate that the SCMF wants to retrieve analytics (e.g., time, size, processing delay, etc.) of the latest dataset treated and associated with the provided SCID, or may indicate that the SCMF wants to retrieve information about the experienced transmission delays or processing load, or may indicate that the SCMF wants to retrieve information about the latest produced data (e.g., intermediate data or result). Upon receiving the notification, AF 806 may send a SC report notification response 824 to SCMF 804; the notification response may include the information indicated by SCMF 804 in the notification and associated with SCID(s) provided in the notification.

[0159] If the SCMF has subscribers (e.g., SC owner or SC consumer) for receiving report information, SC F 804 may send a SC report notification 826 to the subscriber 802; the SC report notification may include report information as received at 818 or 824. Upon receiving the notification, the subscriber may store the report information or use the report information to make an action, for example storing analytics data, modifying the SC chain, or using a reported result.

[0160] The requestor (e.g., SC owner) 802 may modify a SC. The requestor 802 may send a SC modify request 828 to SCMF 804; the request may include information identifying SC chain(s) (e.g., SCID(s)) and information indicating changes to the SC; the SCID(s) may be used by the SCMF to identify SC profile(s), and the information indicating changes may be used by the SCMF to update the SC profile. For example, the information provided in the request may indicate that a SC node instance needs to be removed or replaced from a SC identified with its SCID. The SCMF may send a SC modify notification(s) 830 to the AF(s) 806 (e.g., SC node(s)) participating in the SC chain. The notification may include the updated SC profile; and AF 806 may use updated SC profile to reconfigure the AF operation. Not shown on the figure, additionally to notifying AFs participating in the SC, the SCMF may also notify other subscribers (e.g., SC consumers) about the modified SC profile. The SCMF 804 may send a SC modify response to the requestor at 832; the response may contain an indication of success and the updated SC profile if the SC chain was successfully modified and may include an indication of failure and a failure reason otherwise. Modification of a SC may be triggered by a change in application requirements or detecting a change in availability of a SC node. For example, an application on a WTRU may detect changes in application requirements and decide to remove the SC node from the chain; in another example, a SC node may become unavailable which may be detected by the SC owner or the SCMF and trigger the reselection of another SC node instance In both cases, the SC profile needs to be modified to reflect the changes of the SC chain.

[0161] The requestor (e.g., SC owner) may delete a SC. The requestor 802 may send a SC delete request 834 to the SCMF 804; the request may include information identifying SC chain(s) (e.g , SCID(s)); the SCID(s) may be used by the SCMF to identify SC profile(s). Upon identifying SC profile(s), SCMF 804 may send a SC delete notification(s) 836 to the AF(s) 806 (e.g., SC node(s)) participating in the SC chain The notification may include SCID(s) and a reason; the AF may use the SCID included in the notification to identify a SC profile and traffic associated with the SCID and may respectively stop processing the identified traffic, delete the SC profile and any other associated resources; the reason may provide further information about the SC deletion which can help the AF to manage resources. The SCMF 804 may send a SC delete response to the requestor at 838; the response may contain an indication of success if the SC chain was successfully deleted and may include an indication of failure and a failure reason otherwise.

[0162] Service Chain creation may be performed via the provisioning of connection capabilities, i.e., the 5G core network may support the WTRU requesting creation of a SC by providing connection capabilities. For example, the WTRU may provide connection capabilities information when requesting a PDU session establishment or modifying an existing PDU session.

[0163] In one example, the WTRU may provide connection capability information in a NAS message; connection capability information may be any of a connection capability value, connection capability modifiers. [0164] A connection capability value may indicate that a specific SFC policy configuration is requested. For example, the WTRU may provide a connection capability value (e.g., connection capability ‘X’) that may correspond to a specific SFC policy available to the PCF, and resulting in a SFC policy being applied.

[0165] Connection capability modifiers may indicate that SC capabilities is requested according to a configuration indicated by the modifiers The connection capability modifiers may be associated with a connection capability value such that a connection capability value may indicate that SC capability is requested according to the connection capability modifiers.

[0166] The connection capability modifiers may include the Service Chain Type (SCT) that may uniquely identify a type of service chain.

[0167] The connection capability modifiers may include the Service Chain Identifier (SCID) that may uniquely identify a service chain instance.

[0168] The connection capability modifiers may include the SFC Policy Identifier that may uniquely identify a SFC policy provisioned in the PCF. The WTRU may include a SFC Policy Identifier in the connection capabilities to indicate to the AMF that it wants to use such policy The AMF may communicate the SFC policy identifier to the SFM such that the SMF may obtain PCC rules associated with the SFC policy identifier from the PCF.

[0169] The connection capability modifiers may include the SFC Metadata, which is information that may be added to SFC encapsulated traffic. The WTRU may include a SFC Metadata in connection capabilities to indicate to the AMF that it wants the metadata information to be added to the traffic indicated by the SFC Policy Identifier. The AMF may communicate the SFC metadata to the SFM to configure the SFC traffic encapsulation accordingly

[0170] The connection capability modifiers may include the Service Chain Traffic Descriptor which may describe the traffic characteristics to be included in the SC. The WTRU may include SC traffic descriptor(s) in connection capabilities to indicate to the AMF that it wants a subset (e.g., not all) traffic of the PDU session to be sent through the SC. The AMF may communicate the SC traffic descriptor(s) to the SMF to configure the traffic classifiers accordingly.

[0171] Connection capability information may include any of a connection capability value and its associated connection capability modifiers.

[0172] FIG. 9 illustrates an example of a Service Chain Management Function with Service Function Chaining traffic forwarding and proxying system flows. [0173] At 922, an AC 904 located on a WTRU 902 may request the establishment of a PDU session via RAN 920; the request may indicate that the AC 904 needs to use SC capabilities of the network. The AC request may trigger the WTRU (e.g., the Terminal Equipment (TE) and Mobile Termination (MT) components of the WTRU) to send a PDU session establishment request to the AMF 906 associated with the WTRU 902. The PDU session establishment request message may include connection capabilities information indicating that the created PDU session requires SC capabilities from the network.

[0174] At 924, the AMF 906 may perform SMF selection, and may send to the selected SMF 908 a PDU Session Create request including the connection capabilities information provided by the WTRU 902.

[0175] At 926, upon receiving the PDU session create request from the AMF 906, the SMF 908 may send a message to the PCF 910 indicating that SC support is needed from the network for a given WTRU; the message may contain the connection capability information received from the WTRU at 922. Based on the message from the SMF 908 and the connection capability information, the PCF 910 may identify a SFC policy 912. The PCF may also identify subscribed AFs (e.g., such as the SCMF), and may notify the AFs of PDU session creation requiring SC support. For example, the message sent from the SMF 908 to the PCF 9910 may be a new message or an existing message such as SM policy association establishment.

[0176] At 928, the PCF 910 may determine that at least one AF 916 needs to be notified of requested SC support. The PCF 910 may invoke the NEF API and provide the connection capability information received from the SMF 908 at 926. The NEF 914 may notify the subscribed AF 916 instances at 930, providing the connection capabilities information. For example, an application function (e.g., such as the SCMF) may use this information to create a SC.

[0177] It can be appreciated that a trusted network function implementing the SCMF functionality may be registered to the PCF 910 and that the NEF intermediate node may not be needed.

[0178] At 932, if the PCF 908 may have determined a SFC policy at 926, the PCF 910 may provide the SMF 908 with Policy and Charging Control (PCC) rules. The SMF 908 may configure the UPF 918 according to the received PCC rules.

[0179] At 934, the SMF 908 may notify the AMF 906 about the SC policy chain establishment based on information received from the PCF 910 or from the NEF 914. The notification may include information indicating the successful creation of the SC and may include information needed by the WTRU 902 to use the SC. For example, the information may indicate that the SC was created successfully and may include a SCMF identifier or connectivity information to the SCMF (e.g., IP address, endpoint, etc.) For example, the message sentfrom the SMF to the AMF may be a new message or an existing message such as Communication N1 N2 message transfer.

[0180] At 936, the AMF 906 may send a PDU session establishment accept message to the WTRU 902 via RAN 920; the message may indicate to the WTRU 902 that the PDU session can be used to send traffic. If WTRU 902 indicated SC support at 922, the message may also indicate that the SC is available to receive traffic and may include SC information as described at 934. [0181] At 938, the AC 904 present on the WTRU 902 may be notified that the connection is available and may send a traffic flow to the network, using the PDU session established with SC capabilities. Based on the configured service chain information received from the AMF 906, the AC 904 may be informed of an application function (e.g., such as the SCMF), and may request information from the AF 916, for example, the AC 904 may request the SCMF 916 to provide the SC profile, discover the SC tail and obtain inference results.

[0182] FIG. 10 a flow diagram of an example process 1000 for creating a Service Chain. In some implementations, one or more process blocks of FIG. 10 may be performed by a WTRU .

[0183] As shown in FIG. 10, process 1000 may include detecting an event triggering a split artificial intelligence machine learning (Al ML) process at 1002. For example, WTRU may detect an event triggering a split Al ML process, as described above. As also shown in FIG. 10, process 1000 may include, at 1004, sending, to a network server, a service chain (SC) create request, where the service chain create request includes SC characteristics used in creating a SC profile and a SC. For example, WTRU may send, to a network server, a SC create request, where the service chain create request includes SC characteristics used in creating a SC profile and a SC, as described above As further shown in FIG. 10, process 1000 may include, at 1006, receiving, from the network server, a SC create request response indicating a created SC and an associated SC profile, where the associated SC profile is based, at least in part, on the SC characteristics, and where the associated SC profile includes at least information on a first SC node to send intermediate data and an information on a second SC node from which inference results of the SC will be received or which the WTRU will subscribe to receive the inference results. For example, WTRU may receive, from the network function, a SC create request response indicating a created SC and an associated SC profile, where the associated SC profile is based, at least in part, on the SC characteristics, and where the associated SC profile includes at least information on an SC node to send intermediate data and an information on an SC node from which inference results of the SC will be received or which the WTRU will subscribe to receive the inference results, as described above.

[0184] Process 1000 may include additional implementations, such as any single implementation or any combination of implementations described below and/or in connection with one or more other processes described elsewhere herein In a first implementation, the network server includes a SC management function (SCMF).

[0185] In a second implementation, alone or in combination with the first implementation, process 1000 further includes discovering a plurality of SC nodes; and selecting one or more SC nodes from the plurality of SC nodes discovered.

[0186] In a third implementation, alone or in combination with the first and second implementation, discovering the plurality of SC nodes may include at least one of sending a domain name system (DNS) resolution request to an edge application server discovery function (EASDF) or sending an edge application server (EAS) discovery request to an edge enabler server (EES). [0187] In a fourth implementation, alone or in combination with one or more of the first through third implementations, the SC create request includes an indication of the one or more SC nodes selected.

[0188] In a fifth implementation, alone or in combination with one or more of the first through fourth implementations, the event triggering the creation of the split AIML process is at least one of: an event triggered by an application client residing on the WTRU or a notification received from a network.

[0189] In a sixth implementation, alone or in combination with one or more of the first through fifth implementations, the associated SC profile further includes one or more of: a SC identifier (SCID), an SC model (SCM), an SC size, or SC node identifiers (SCNIDs), and where each SC node is associated with an application that is an AIML model.

[0190] In a seventh implementation, alone or in combination with one or more of the first through sixth implementations, each SCNID includes at least one of: a respective SC node role (SCNR) identifier; a respective SC node position (SCNP) identifier; or respective SC node application characteristics (SCNAC) identifiers.

[0191] Although FIG. 10 shows example blocks of process 1000, in some implementations, process 1000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 10. Additionally, or alternatively, two or more of the blocks of process 1000 may be performed in parallel. [0192] 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, WTRU, terminal, base station, RNC, or any host computer.

Claims

CLAIMS What is Claimed:

1. A method performed by a wireless transmit/receive unit (WTRU), the method comprising: detecting an event triggering a creation of a split artificial intelligence machine learning (AIM L) process; sending, to a network server, a service chain (SC) create request, wherein the service chain create request includes SC characteristics used in creating a SC profile and a SC; and receiving, from the network server, a SC create request response indicating a created SC and an associated SC profile, wherein the associated SC profile is based, at least in part, on the SC characteristics, and wherein the associated SC profile includes at least information on a first SC node to send intermediate data and an information on a second SC node from which inference results of the SC will be received or which the WTRU will subscribe to receive the inference results.

2. The method of claim 1 , wherein the network server includes a SC management function (SCMF).

3. The method of claims 1 or 2, further comprising: discovering a plurality of SC nodes; and selecting one or more SC nodes from the plurality of SC nodes discovered.

4. The method of claim 3, wherein discovering the plurality of SC nodes comprises at least one of sending a domain name system (DNS) resolution request to an edge application server discovery function (EASDF) or sending an edge application server (EAS) discovery request to an edge enabler server (EES).

5. The method of claim 4, wherein the SC create request includes an indication of the selected one or more SC nodes.

6. The method of any of claims 1 to 5, wherein the event triggering the creation of the split AIML process is at least one of: an event triggered by an application client residing on the WTRU or a notification received from a network.

7. The method of any of claims 1 to 6, wherein the associated SC profile further includes one or more of: a SC identifier (SCID), an SC model (SCM), an SC size, or SC node identifiers (SCNIDs), and wherein each SC node is associated with an application that is an AIML model.

8. The method of claim 7, wherein each SCNID includes at least one of: a respective SC node role (SCNR) identifier; a respective SC node position (SCNP) identifier; or respective SC node application characteristics (SCNAC) identifiers.

9. The method of claim 8 and wherein the SCNAC include at least one of: an application identifier, an application type, application version information, an application size identifier, or application capability requirements.

10. A wireless transmit/receive (WTRU) unit comprising: processor circuitry configured to detect an event triggering a creation of a split artificial intelligence machine learning (AIML) process; and a transceiver configured to: send, to a network server, a service chain (SC) create request, wherein the service chain create request includes SC characteristics used in creating a SC profile and a SC; and receive, from the network server, a SC create request response indicating a created SC and an associated SC profile, wherein the associated SC profile is based, at least in part, on the SC characteristics, and wherein the associated SC profile includes at least information on a first SC node to send intermediate data and an information on a second SC node from which inference results of the SC will be received or which the WTRU will subscribe to receive the inference results.

11. The WTRU of claim 10, wherein the transceiver is further configured to: send a domain name system (DNS) resolution request to an edge application server discovery function (EASDF) or send an edge application server (EAS) discovery request to an edge enabler server (EES).

12. The WTRU of claim 11 , wherein the transceiver is further configured to receive a DNS resolution response; and the processor circuitry is configured to select one or more SC nodes according to the DNS resolution response.

13. The WTRU of claim 11, wherein the transceiver is further configured to receive a EAS discovery response; and the processor circuitry is further configured to: discover a plurality of SC nodes; and select one or more SC nodes from the plurality of SC nodes discovered according to the EAS discovery response received.

14. The WTRU of any of claims 10 to 13, wherein the SC create request includes an indication of the selected one of more SC nodes.

15. The WTRU of any of claims 10 to 14, wherein the event triggering the creation of the split AIML process is at least one of: an event triggered by an application client residing on the WTRU or a notification received from a network.

16. The WTRU of any of claims 11 to 15, wherein the associated SC profile further includes one or more of: a SC identifier (SCID), an SC model (SCM), an SC size, or SC node identifiers (SCNIDs), and wherein each SC node is associated with an application that is an AIML model.

17. The WTRU of claim 16, wherein each SCNID includes at least one of: a respective SC node identifier; a respective SC node role (SCNR) identifier; a respective SC node position (SCNP) identifier; respective SC node application characteristics (SCNAC) identifiers; or respective SC node subscription information (SCNSI).

18. The WTRU of claim 17, wherein the SCNAC includes at least one of: an application identifier, an application type, application version information, an application size, and application capabilities.

19. A method performed by a network server, the method comprising: receiving a registration request from one or more service chain (SC) nodes capable of participating in a SC, wherein the registration request includes SC node information from each respective one or more SC nodes capable of participating in the SC, and wherein the SC node information includes a respective SC node identifier and capabilities of a respective application function (AF) associated with each of the one or more SC nodes; creating a subscription resource for each of the one or more SC nodes by registering the one or more SC nodes capable of participating in the SC according to the SC node information of each respective one or more SC nodes; receiving, from a wireless transmit/receive unit (WTRU), a SC create request, the SC create request including SC characteristics used in creating a SC profile; creating the SC profile based on the SC characteristics and the SC node information associated with each respective one or more SC nodes registered; notifying each of the one or more SC nodes of their respective inclusion in a SC associated with the SC profile created; and sending, to the WTRU, a SC create response, wherein the SC create response includes a SC create success indication and an indication of the SC profile created or a SC create request failure indication.

20. The method of claim 19, wherein the network server includes a service chain management function (SCMF), and wherein the SCMF creates the SC profile by selecting the respective one or more SC nodes based on the SC characteristics.