Edge application instance discovery and selection based on shared application vertical sessions
Through the identifier and management mechanism based on application vertical sessions, the problem of difficulty in discovering and selecting participation in public application vertical sessions in the prior art is solved, and edge application instance coordination and privacy guarantees are achieved in a multi-user group environment.
Patent Information
- Application Number
- CN202411119392.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-24
- Filing Date
- 2023-03-23
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2043-03-23
AI Technical Summary
The prior art is difficult to effectively discover and select edge application examples that participate in public application vertical sessions, especially in multi-user group environments, and it is difficult to maintain privacy and security, making it impossible to ensure that application clients of different users can participate in the same application vertical. Session.
Use application vertical session-based identifiers (ASVIDs) for registration, discovery and selection of edge application instances, and coordinate application vertical session management and multi-user group identifiers (IDs) to ensure that application clients can discover and connect to the appropriate Edge application server instance.
It realizes effective discovery and selection of edge application instances in a multi-user group environment, ensuring that application clients can participate in public application vertical sessions, while ensuring privacy and security, and avoiding the exposure of sensitive information.
Smart Images

Figure CN118921399A_ABST
Abstract
Description
[0001] This application is a divisional application of the invention whose applicant is Interactive Digital Patent Holdings Corporation, whose application date is March 23, 2023, whose application number is 202380017198.1, and whose name is edge application instance discovery and selection based on shared application vertical sessions.
[0002] CROSS-REFERENCE TO RELATED APPLICATIONS
[0003] This application claims the benefit of U.S. Provisional Application Serial No. 63 / 323,396, filed on March 24, 2022, the contents of which are hereby incorporated by reference into this document. Summary of the invention
[0004] In one or more embodiments, one or more devices, systems and / or methods may provide solutions and / or innovations for 5G systems, edge computing, edge applications and / or other wireless systems. For example, one or more of the following technologies may be used to handle edge application instance discovery and selection based on shared application vertical sessions: there may be an application vertical session identifier (also referred to as a "group identifier"); one or more EAS registration, discovery and selection processes based on application vertical sessions; EDN / EES deployment based on application vertical sessions; and / or application vertical session management.
[0005] In one or more embodiments, a method implemented by a server includes: receiving information related to a common application from multiple wireless transmit receive units (WTRUs); in response to receiving the information, transmitting a common multi-user group identifier (ID) to the multiple WTRUs; receiving a request indicating the common multi-user group ID; and transmitting an indication of one or more server instances associated with the common multi-user group ID.
[0006] In one or more embodiments, a method implemented by a wireless transmit receive unit (WTRU) includes: transmitting a message indicating a common multi-user group identifier (ID) to a server; receiving an indication of one or more server instances associated with the common multi-user group ID; and connecting to the one or more server instances.
[0007] In one or more embodiments, a server is configured to: receive information related to a common application from multiple wireless transmit receive units (WTRUs); in response to receiving the information, transmit a common multi-user group identifier (ID) to the multiple WTRUs; receive a request indicating the common multi-user group ID; and transmit an indication of one or more server instances associated with the common multi-user group ID.
[0008] In one or more embodiments, a WTRU is configured to: transmit a message indicating a common multi-user group identifier (ID) to a server; receive an indication of one or more server instances associated with the common multi-user group ID; and connect to the one or more server instances.
[0009] In one or more embodiments, a method implemented by a server includes: receiving a request from a wireless transmit-receive unit (WTRU) for one or more edge application server (EAS) instances configured to run a session common to an application client located on the WTRU and a session common to at least one other application client located on the WTRU or on another WTRU; and associating the one or more EAS instances with a multi-user group ID.
[0010] In one embodiment, a server is configured to: receive a request from a wireless transmit-receive unit (WTRU) for one or more edge application server (EAS) instances configured to run a session common to an application client located on the WTRU and a session common to at least one other application client located on the WTRU or on another WTRU; and associate the one or more EAS instances with a multi-user group ID. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] A more detailed understanding may be obtained from the following description given by way of example with reference to the accompanying drawings in which like reference numerals indicate similar elements.
[0012] Figure 1A is a system diagram illustrating an exemplary communication system in which one or more disclosed embodiments may be implemented.
[0013] Figure 1B is an example of a method that can be used according to one embodiment. Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) for use within an illustrated communication system.
[0014] Figure 1C is an example of a method that can be used according to one embodiment. Figure 1A System diagram of an exemplary radio access network (RAN) and an exemplary core network (CN) for use within the illustrated communication system.
[0015] Figure 1D is an example of a method that can be used according to one embodiment. Figure 1A System diagram of another exemplary RAN and another exemplary CN used within the illustrated communication system.
[0016] Figure 2 An example of a system architecture for edge computing between devices and an edge data network is illustrated.
[0017] Figure 3 An example of the EAS registration process is illustrated.
[0018] Figure 4a to Figure 4b An example of the EAS discovery process is illustrated.
[0019] Figure 5 An example of several EASs deployed in different locations in the same EDN is illustrated.
[0020] Figure 6 An example of EAS registration, discovery, and selection process based on application vertical sessions is illustrated.
[0021] Figure 7 An example of EAS discovery notification based on application vertical session is illustrated.
[0022] Figure 8a to Figure 8b An example of service provisioning is illustrated.
[0023] Fig. 9 An example of EES provisioning and selection based on application vertical sessions is illustrated.
[0024] Fig.10 An example of EES provisioning notifications based on application vertical sessions is illustrated.
[0025] Fig.11 An example of AVS creation using an edge-enabled layer is illustrated.
[0026] Fig.12 is a flow chart of an example of a method for setting up server instances and multi-user group identifiers (IDs) for a public application.
[0027] Fig.13 is a flow chart of an example of a method for accessing one or more server instances associated with a common application using an associated common multi-user group identifier (ID).
[0028] Fig.14 A flow chart of an example of a method for configuring one or more edge application server (EAS) instances to run sessions common to multiple application clients on one or more WTRUs and associating the one or more EAS instances with multiple user group identifiers (IDs). DETAILED DESCRIPTION
[0029] As listed in Table 1 below, one or more of the following abbreviations and / or acronyms may be used.
[0030]
[0031]
[0032] Table 1 - Exemplary Acronyms
[0033] Figure 1A 1 is a diagram illustrating an exemplary communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word discrete Fourier transform spread OFDM (ZT-UW-DFT-S-OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.
[0034] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a “station” (STA)) may be configured to send and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.
[0035] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device 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 other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an evolved Node B (eNB), a Home Node B, a Home evolved Node B, a next generation Node B such as a gNode B (gNB), a new radio (NR) Node B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.
[0036] 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), a relay node, etc. The base station 114a and / or the base station 114b may be configured to send 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 a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrums. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In one embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to send and / or receive signals in a desired spatial direction.
[0037] 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).
[0038] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 116. 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).
[0039] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro).
[0040] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using NR.
[0041] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may together implement LTE radio access and NR radio access, for example using dual connectivity (DC) principles. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).
[0042] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), GSM Enhanced Data Rates for Evolution (EDGE), GSM EDGE (GERAN), etc.
[0043] Figure 1A The base station 114b in the may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or a femtocell. As Figure 1A As shown, the base station 114b may have a direct connection to the Internet 110. Therefore, the base station 114b may not be required to access the Internet 110 via the CN 106.
[0044] 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 different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the accompanying drawings, the CN 106 may be configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. Figure 1AAlthough not shown in the figure, 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 utilize NR radio technology, the CN 106 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
[0045] The CN 106 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired communication networks and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.
[0046] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
[0047] Figure 1B is a system diagram illustrating an exemplary WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
[0048] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal decoding, 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. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
[0049] The send / receive element 122 may be configured to send a signal to a base station (e.g., base station 114a) or receive a signal from a base station via an air interface 116. For example, in one embodiment, the send / receive element 122 may be an antenna configured to send and / or receive an RF signal. In one embodiment, the send / receive element 122 may be a transmitter / detector configured to send and / or receive, for example, an IR, UV or visible light signal. In another embodiment, the send / receive element 122 may be configured to send and / or receive both an RF signal and an optical signal. It should be understood that the send / receive element 122 may be configured to send and / or receive any combination of wireless signals.
[0050] Although the transmit / receive element 122 Figure 1B 1 as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
[0051] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. For example, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.
[0052] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
[0053] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.
[0054] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.
[0055] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, Module, FM radio unit, digital music player, media player, video game player module, Internet browser, virtual reality and / or augmented reality (VR / AR) device, activity tracker, etc. Peripheral device 138 may include one or more sensors. These sensors may be one or more of the following: gyroscope, accelerometer, Hall effect sensor, magnetometer, orientation sensor, proximity sensor, temperature sensor, time sensor; geographic location sensor, altimeter, light sensor, touch sensor, magnetometer, barometer, gesture sensor, biometric sensor, humidity sensor, etc.
[0056] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and DL (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via hardware (e.g., choke) or via signal processing performed by a processor (e.g., a separate processor (not shown) or via the processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or DL (e.g., for reception)) may be concurrent and / or simultaneous.
[0057] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with 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.
[0058] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.
[0059] Each of the evolved Node Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.
[0060] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. Although the foregoing elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0061] The MME 162 may be connected to each of the evolved Node-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, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.
[0062] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-evolved Node-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.
[0063] 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.
[0064] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers.
[0065] Although the WTRU Figures 1A to 1D Although described as a wireless terminal, it is contemplated that in certain representative embodiments such a terminal may (eg, temporarily or permanently) employ a wired communications interface with a communications network.
[0066] In a representative embodiment, the other network 112 may be a WLAN.
[0067] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for a BSS and one or more stations (STA) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be sent to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit traffic to the AP, and the AP may deliver traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be sent between the source and destination STAs (e.g., directly between them) using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.
[0068] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may send beacons on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a dynamically set width. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may listen to the primary channel. If the primary channel is listened / 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.
[0069] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.
[0070] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz and / or 80MHz channels can be formed by combining continuous 20MHz channels. 160MHz channel can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be sent by sending STA. At the receiver of the receiving STA, the above-mentioned operation for 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC).
[0071] 802.11af and 802.11ah support operating modes below 1GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter type control / machine type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).
[0072] WLAN systems that can support multiple channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if other STAs in the AB and BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (which only supports a 1MHz operating mode) is sending to an AP, all available bands may be considered busy even if most of the available bands remain idle.
[0073] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.
[0074] Figure 1D1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with an embodiment. As noted above, the RAN 104 may employ 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.
[0075] 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, the gNBs 180a, 180b may utilize beamforming to send signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to send wireless signals to and / or receive wireless signals from the WTRU 102a. In one 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 an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In one embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNB 180a and gNB 180b (and / or gNB 180c).
[0076] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with parameter sets that may be scalable. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or Transmission Time Intervals (TTIs) of varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or varying absolute time lengths over time).
[0077] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while also not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the eNodeB 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNodeBs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNodeB 160a, 160b, 160c may act as a mobility anchor for the WTRUs 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.
[0078] Each of the gNBs 180a, 180b, 180c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, interworking between DC, NR, and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.
[0079] Figure 1DThe illustrated CN 106 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although the aforementioned elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0080] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of non-access stratum (NAS) signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of services utilized by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, etc. 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.
[0081] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 106 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 106 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.
[0082] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, etc.
[0083] 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 other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to the DNs 185a, 185b via the UPFs 184a, 184b via the N3 interfaces to the UPFs 184a, 184b and the N6 interfaces between the UPFs 184a, 184b and the local DNs 185a, 185b.
[0084] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with reference to one or more of the following items may be performed by one or more simulation devices (not shown): WTRU102a to 102d, base station 114a to 114b, evolved Node B 160a to 160c, MME 162, SGW 164, PGW 166, gNB180a to 180c, AMF 182a to 182b, UPF 184a to 184b, SMF 183a to 183b, DN 185a to 185b and / or any other device described herein. The simulation device may be one or more devices configured to mimic one or more or all of the functions described herein. For example, the simulation device can be used to test other devices and / or simulate network and / or WTRU functions.
[0085] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or in an operator network environment. For example, one or more simulation devices may perform one or more functions 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. One or more simulation devices may perform one or more functions or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for the purpose of testing and / or performing tests using over-the-air wireless communications.
[0086] One or more simulation devices may perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device may be used in a test scenario in a test lab and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuits (e.g., which may include one or more antennas) may be used by the simulation device to send and / or receive data.
[0087] Figure 2 An exemplary architecture 200 for enabling edge applications is illustrated. In general, the system aspects of a wireless system (e.g., SA6) can provide application layer architecture specifications for standardized vertical areas, including architectural requirements, functional architectures, processes, information flows, interworking with non-3GPP application layer solutions, and / or appropriate deployment models. As shown, the exemplary architecture 200 has several components, which are further discussed in Table 2 below.
[0088]
[0089] Table 2 - Figure 2 Example components of an example architecture
[0090] In some cases, an application service provider or edge computing service provider may deploy several instances of an edge application server (EAS) 204 within a single edge data network (EDN) 206 or across several EDCs. The EAS 204 may provide application-level specific functions to an application client (AC) 202 on a terminal (e.g., WTRU 203). The AC 202 may connect to the EAS 204 to take advantage of the available services of the application and the benefits of edge computing. A single AC 202 may be associated with one and only one edge enabled client (EEC) 210.
[0091] The edge enabling layer (EEL) may provide one or more identifiers for the AC 202 and the EAS 204, as provided in the example of Table 3 below.
[0092]
[0093] Table 3 - Example identifiers for AC 202 and EAS 204
[0094] Such as Figure 3 An EAS204 registration process such as the exemplary registration process 300 shown in can enable an EAS instance to notify, update and / or delete its information to the EEL via EES208 so that AC 202 can discover it. An EAS204 instance can register with one (e.g., in some cases only one) EES208, provided that the EAS information is described in an EAS configuration file. The EAS204 configuration file may or may not include information that uniquely identifies the EAS instance. For example, an EAS204 endpoint element within the EAS204 configuration file may be used to provide AC 202 with information for communicating with the EAS. The EAS 204 endpoint may be an identifier that can be shared with multiple EAS instances, such as an FQDN or URI. In addition, the EAS204 configuration file may not include any information that identifies an application vertical session or AC 202 instance that any given EAS may be serving or available for service.
[0095] EAS discovery process (such as Figure 4a and Figure 4b 4 and 402) can enable EEC 210 to discover EAS 204 by interacting with EES 208 in EDN 206. EEC 210 can select one or more discovered EAS 204 and disclose the selected EAS to AC 202. Discovery of EAS 204 can be based on matching EAS discovery filters provided by EEC 210 with EAS profiles registered at EES 208. For example, some EAS 204 discovery processes can include: synchronous query (request-response process); and / or asynchronous notification (subscribe-notify process). Figure 4a and Figure 4bMay be applied to these two options separately. In addition, for these two options, the EAS204 discovery filter may be provided by the EEC 210 and may include an AC 202 feature list and / or an EAS feature list. The EAS204 discovery filter may not include any ability to identify a specific instance of the EAS for selection or to identify an EAS instance that is serving or available to serve a specific application vertical session. As described herein, the EAS204 discovery filter may include one or more information elements, such as: AC 202 feature list; AC profile; EAS204 feature list; EASID; EAS provider identifier; EAS type; EAS scheduling; EAS geographic service area; EAS topological service area; service continuity support; service permission level; service characteristics. One or more of these filters may be optional, and one or more of these filters may be mandatory.
[0096] In some cases, the EEL may not define how AC 202 registers or identifies EAS 204 discovery / selection parameters to EEC 210 via the EDGE-5 reference point. In other cases, there may be (pre)configured parameters. For example, it may be necessary to determine how AC 202 provides the EEC 210 with the information required to identify the appropriate EAS 204 instance (specifically, its AC profile) for connection in order to meet current and future needs of such wireless systems. The AC 202 profile may not include any application vertical session or context information or EAS instance identification information for EAS discovery and selection for communication.
[0097] Figure 5 An example of several EAS 204 deployed in different locations of the same EDN 206 is illustrated (in Figure 5 1A, EAS-1(B), and EAS-1(C), although the example contemplates less than or more than three EASs). For many applications, if a group of ACs 202 are participating in a shared application vertical session or context, they may need to interface with a common EAS 204 instance. This may include the same WTRU 203 or separate WTRUs 203 (in a single WTRU or multiple WTRUs) connected to a common EDN 206 or different EDNs 206 for a single user or multiple users. Figure 5 , WTRU1, WTRU2, and WTRU3 in the illustration, although the example contemplates less than or more than three WTRUs).
[0098] In some cases, the EEL may not provide any ability to discover and select a common EAS 204 for a group of ACs 202 or WTRUs 203. This may be a problem and may need to be addressed by one or more of the methods discussed herein (e.g., discovering a common EAS 204). This problem may raise one or more questions: First, whether and how do ACs 202 / EECs 210 of different users (e.g., different WTRUs 203) select or provision the same EAS 204 within the EDN 206? Second, whether and how do ACs 202 / EECs 210 of different users (e.g., different WTRUs 203) select or provision a common EAS 204 even if the EECs 210 initially communicate with different EDNs 206? Third, whether and how does the EEL support business continuity to ensure that when an AC 202 needs to use services from a common EAS 204 and an ACR operation is required, the ACR operation can be coordinated so that after the ACR operation is completed, the AC again has services provided by the common EAS.
[0099] In one or more embodiments, the above questions can be solved herein.
[0100] Table 4 below lists some examples of application verticals that require a set of ACs 202 / WTRUs 203 to participate in a shared application vertical session with a common EAS 204 instance, in a non-exhaustive manner.
[0101]
[0102]
[0103] Table 4 - Examples of application verticals that typically require a group of ACs 202 / WTRUs 203 to participate in a shared application vertical session with a common EAS 204 instance
[0104] There may be one or more methods to discover and select a public EAS instance. In one instance (e.g., specifically for a multiplayer game), each AC 202 on all WTRUs 203 participating in the game instance may be informed of the identities and locations of all other WTRUs in the game. Each EEC 210 may transmit this information (e.g., a list of WTRUs 203 with locations) to the EES 208 for public EAS 204 discovery. This approach may require sharing sensitive information (e.g., identification and location) with all ACs 202 and WTRUs 203, which may present security and privacy risks when the player is unknown and untrustworthy. In addition, this embodiment does not allow a single WTRU 203 (e.g., a game console or hub device) to participate in two or more separate game sessions served by different EAS 204 instances.
[0105] In a second example, there may be EEL service differences for EAS204 discovery for different users, which focus on how the ECSP provides edge service quality levels (e.g., premium users vs. ordinary users). EAS204 may provide EES208 with a list of WTRU 203 identifiers that can be used in EAS selection / discovery. The list can be used to match the WTRU 203 in the list with a public EAS204 instance. However, this may expose sensitive information (e.g., WTRU203 identifiers) at the application level (EAS204). How EAS204 learns the collection of WTRU 203 identifiers may still need to be resolved. Finally, this method does not allow a single WTRU 203 (e.g., a game console or hub device) to participate in two or more separate game sessions served by different EAS204 instances.
[0106] In the traditional case, EAS 204 discovery and selection does not consider any information about application vertical sessions. An application vertical session is a group of ACs 202 and EAS 204 participating in a broader application vertical deployment (e.g., a common multi-user, multi-device, or multi-client session). In this case, EAS 204 discovery and selection may only consider non-application vertical session information, such as EAS type (EASID), AC type (ACID), service KPIs (e.g., bandwidth, request rate, response time, etc.), EEC ID, WTRU 203 identifier, etc. Therefore, these traditional EAS 204 discovery and selection processes are performed independently for each AC 202 and EEC 210, with little or no ability to ensure that a group of ACs participating in a common application vertical session can receive services from a common EAS 204.
[0107] Therefore, there is a need to address techniques such as discovering a common EAS 204 (e.g., how different users' ACs / EECs can select or be provisioned with the same EAS). It may also be relevant to address any additional shortcomings, such as: where the techniques require sharing of privacy and security sensitive information such as the identity of the WTRU 203, the location of the WTRU, etc. at the application level (with the AC 202, EAS 204, and application layer servers in the cloud); in addition, where the techniques do not distinguish between the application vertical session level and the AC 202 level (e.g., limiting the ability of a separate AC on a single device to interact with a separate EAS 204 instance). In considering these shortcomings, additional factors may also be addressed, such as: how to enable different ACs 202 of the same or different WTRUs 203 and of the same or different types to participate in a common application vertical session; how to be able to discover and select a common EAS 204 instance for a set of ACs 202 participating in an application vertical session while maintaining privacy (i.e., not exposing sensitive information such as identity and location between ACs, EASs, or WTRUs 203); how the EEL assists in creating an application vertical session.
[0108] In one or more embodiments, the above problems / questions can be solved in one or more devices, systems and / or methods. For example, one or more of the following technologies can be used to handle edge application instance discovery and selection based on shared application vertical sessions: there can be an application vertical session identifier; one or more EAS204 registration, discovery and selection processes based on application vertical sessions; EDN / EES deployment based on application vertical sessions; and / or application vertical session management.
[0109] The Application Vertical Session Identifier (ASVID) identifies a "public multi-user session" and may be used by the EEL to assist in the management of the application vertical session, including the discovery and selection of a public EAS 204 (or public EAS group) for the set of ACs 202 participating in the session. A "multi-user" may include any combination of ACs 202 and EECs 210 on one or more WTRUs 203. It is not meant to be a human user, although it may be a human user.
[0110] EAS204 registration, discovery, and selection based on application vertical sessions are enhanced EEL processes that specifically consider the ASVID as input. The EAS204 that supports application vertical sessions signals the EEL (e.g., EES208) during registration (including updates) the application vertical session identifiers that the EAS is serving. Similarly, the AC 202 may signal the EEL (e.g., EES208) which application vertical sessions the client (AC) will participate in via the EEC 210. With the application vertical session identifiers, the EEC 210 and EES208 may be able to match the AC / WTRU EAS204 discovery and selection requests with the appropriate EAS instance that serves the application vertical session it requested.
[0111] Application vertical session based EDN / EES provisioning is an enhanced process whereby the WTRU 203 selects an EDN 206 for connection based on the WTRU's AC 202 application vertical session requirements. The ECS 212 may utilize these requirements to select a combination of EDN 206 and EES 208 for the EEC 210 based on the availability of application vertical sessions served by the EAS 204. If the EAS 204 is not available to serve the application vertical session in the EDN 206 according to the provisioning request, the ECS 212 may signal to the subscribed EEC 210 via a service provisioning notification if the EAS later becomes available to serve the requested application vertical session.
[0112] Application vertical session management is the process that allows the WTRU 203 to create application vertical sessions in the EEL and allows other WTRUs to be aware of application vertical sessions available in the EEL.
[0113] Figure 6 An example of an EAS 204 registration, discovery, and selection process 600 based on an application vertical session is illustrated. As shown, the EEL may support the interconnection of the AC 202 on the WTRU 203 with the appropriate EAS 204 instance serving its application vertical session via an enhanced EAS registration, discovery, and selection process. As shown, there is an overall process flow with an example of operation.
[0114] The benefit of these enhanced processes is that they enable AC 202 and / or EEC 210 to discover and select not only an EAS 204 that provides a particular type of service, but also enables AC and / or EEC to discover an EAS 204 associated with a particular instance of a service. Without this feature, AC 202 and / or EEC 210 may not be able to discover and connect to an application vertical session that the AC wants to join (e.g., a gaming AC may not be able to connect to an application vertical session of another AC that is serving the same game).
[0115] like Figure 6 As shown, there is an exemplary process 600 in which AC 202 discovers the EAS 204 instance that serves its application vertical session. Initially, at 602, there may be one or more prerequisites: at the application level, an application vertical session may be created, and an application vertical session ID (AVSID) may be assigned to identify the session. In this example, two application vertical sessions are created, one with AVSID = "A" and the other with AVSID "B". Please note that "A" and "B" are examples used only to illustrate the relevant technology and may be different in one or more other embodiments based on the present disclosure. These AVSIDs can be distributed across the serving EAS 204 and consuming AC 202 at the application level. In other words, AC 202 can receive the AVSID in a message from EAS 204, an application server, or an EEL (if the EEL has such capabilities). If the AVSID is not available and needs to be created, the AVSID of the application vertical session can be created via the EEL using the application vertical session management method described herein.
[0116] At 604a and 604b, each EAS 204 may register with their EES 208 and provide their serving AVSID, such as via the application vertical session enhanced EAS profile described herein (e.g., Table 5). The EES 208 may store the EAS to AVSID relationship in order to match the EEC 208 request for EAS 204 discovery with the serving EAS or EAS group. For example, Figure 6 EAS1 is shown registered with AVSID="A" and EAS2 is shown registered with AVSID="B". EAS1 and EAS2 may share a common EASID or may have different EASIDs. EAS204 may have obtained the AVSID from another server, such as a matching server that may be hosted in the cloud or in EDN206. Alternatively, the AVSID may have been pre-configured in EAS204, such as via a configuration file or via configuration at the time of EAS orchestration; alternatively, the AVSID may have been provided by the EEL, assuming that the EEL has such capabilities.
[0117] At 606, when AC 202 needs to interface with EAS 204 serving its application vertical session, AC may request EAS discovery from EEC 201 and provide its associated application vertical session ID. In this example, ACx 202 on WTRUx 203 requests EAS discovery for AVSID="A". Alternatively, ACx 202 may implicitly trigger EAS discovery at EEC 210 by registering with the EEC and providing the AVSID in the registration. ACx 202 may have obtained the AVSID from a pre-configuration file, or from user input, or from a matching server hosted in the cloud or in an edge data network, or from EEC 210 (assuming the EEC has such capabilities).
[0118] At 608, the EEC 210 may process the EAS 204 discovery or AC 202 registration request from the AC and transmit the EAS 204 discovery request to an EES 208 that can service the requested application vertical session, including an enhanced AC profile (e.g., such as described herein) within an EAS discovery filter. The EEC 210 may select an EES 208 that provides service for the application vertical session based on an enhanced AC 202 profile (e.g., such as the AC profile described herein).
[0119] At 610, upon receiving the EAS 204 discovery request, the EES 208 may perform a lookup of registered EASs that match the EAS requirements, including looking up an EAS that matches the requested AVSID and selecting only the EAS associated with the AVSID. In the example shown, the EES 208 selects EAS1 serving AVSID="A". Although the example shows a single EAS 204 instance, the AC 202 may be served by a group of EASs serving the same AVSID="A".
[0120] At 612 , the EES 208 responds to the EEC 210 with the selected EAS 204 endpoint and the AVSID that the EAS is servicing in the context of an enhanced service session in the EEC context, such as disclosed herein.
[0121] At 614 , the EEC 210 may in turn respond to the requesting AC 202 with the selected EAS 204 endpoint and the AVSID that the EAS is serving.
[0122] At 616, the application client (AC) 202 may connect to the selected EAS 204 and join the application vertical session. In the illustrated example, ACx 202 on WTRUx 203 connects to EAS1 204 and joins the application vertical session with AVSID="A".
[0123] For 606 to 616, these steps may be repeated for each AC 202 and WTRU 203 participating in the application vertical session.
[0124] At 618 , if the EAS 204 is servicing more than one application vertical session, the AVSID can be appended to the application traffic request to differentiate the flows based on the AVSID.
[0125] Figure 7 An example of an EAS204 discovery notification 700 based on an application vertical session is illustrated. The EAS204 discovery subscription / notification process disclosed herein can provide a method for asynchronously notifying the EEC 210 of the availability of the EAS in the EDN 206. As shown, there is an example of an application vertical session enhancement process for EAS discovery subscription and notification. This process may be useful when no EAS204 instance is available to serve the AVSID in the EAS discovery request response, as described earlier in this article. The EES 208 can use the application vertical session enhancement EAS discovery notification to notify the EEC 210 of the dynamic availability of the EAS204 that can serve one or more application vertical sessions of interest.
[0126] Initially, one or more prerequisites may exist. An application vertical session may be created and an AVSID may be assigned to identify the session. The AVSID may be provided to the EEC 210, for example, by the AC 202, when registering with the EEC or requesting EAS 204 discovery for the AVSID. The EEC 210 may attempt to synchronize the EAS discovery request process (e.g., Figure 6 ), and EES208 may not have any EAS204 available to service the requested AVSID.
[0127] At 702 , EEC 210 can create an application vertical session EAS 204 discovery subscription (eg, as described herein) with EES 208 , providing a set of AVSIDs in an EAS discovery filter or in an EAS dynamic information filter (eg, as disclosed herein).
[0128] At 704, later, EAS 204 may be instantiated in EDN 206 to serve application vertical sessions identified by their respective AVSIDs. EAS 204 may register with EES 208 and provide its service AVSID, such as via a defined enhanced EAS profile (eg, as disclosed herein).
[0129] At 706, EES 208 may use EAS 204 registration information and evaluate it against EAS discovery subscription filters, such as the AVSID from the subscription created at 702. EES 208 may determine that a notification needs to be sent to EEC 210 because the AVSID matches the subscription request.
[0130] At 708 , EES 208 may transmit an EAS discovery notification to subscribed EECs 210 and include applying a vertical session enhanced EAS profile (eg, as disclosed herein).
[0131] At 710, EEC 210 can notify AC 202 of EAS 204, providing the EAS endpoint and the AVSID that the EAS is serving. AC 202 can connect to the selected EAS 204 and join the application vertical session.
[0132] Figure 8a and Figure 8b An example of service provisioning is illustrated. Generally, in the EEL, the EEC 210 may utilize the services of the ECS 212 to discover the EDN 206 and the EES 208, which may satisfy the needs of the AC 202 on the WTRU 203 via the service provisioning process. In some cases, the EDN 206 / EES 208 service provisioning may take into account the EAS 204 and AC 202 type information (e.g., EASID and ACID) in the AC profile. However, in some cases, the EDN 206 / EES 208 service provisioning may not take into account any application vertical session information. This may result in the EEC 210 / AC 202 discovering EES 208 available to the WTRU 203 in different EDNs 206 without knowing which EAS 204 / EDN 206 can provide the required application vertical session; therefore, there is a problem that the EEC 210 must perform EAS 204 discovery with each EES 212 iteration until the EEC finds an EAS that supports its required AVSID. To address this issue, it may be beneficial to discover and signal the availability of EDNs 206 and their EES 208 associated with the requested AVSIDs, and the EAS 204 within such EDNs serves or can serve these requested AVSIDs.
[0133] The benefit of this enhanced process is that it allows AC 202 and EEC 210 to discover EDN 206 and EES 208 that can be used to reach EAS 204 that not only provides a particular type of service, but also allows AC and EEC to discover EDN and EES that can be used to reach EAS associated with a particular instance of service (e.g., servicing an application vertical session). Without this feature, AC 202 and EEC 210 may not be able to discover and connect to an application vertical session that AC 202 wants to join (e.g., a gaming AC will not connect to an EAS 204 that serves a gaming match identified by a particular AVSID or AVSIDs).
[0134] At 802 a and 802 b , the EEC 210 issues a service provisioning request or a service provisioning subscription request to the ECS 212 .
[0135] Fig. 9 An example of an EES 208 provisioning and selection process 900 based on an application vertical session is illustrated. The example describes EDN 206 / EES 208 service provisioning in an EEC 210 request-response model. In this model, the EEC 210 requests the provisioning of an EES 208 service that provides the AVSID it requested. The ECS 212 can provision the EEC 210 with an EES 208 / EDN 206 that can serve the AVSID it requested.
[0136] Initially (not shown), one or more prerequisites may exist. An application vertical session may be created and an application vertical session ID may be assigned to identify the session. The AVSID may be provided to the EEC 210, for example, by the AC 202, when registering with the EEC 210 or requesting EAS 204 discovery for the AVSID.
[0137] At 902, the EEC 210 may transmit a service provisioning request to the ECS 212. The service provisioning request may include a set of AC 202 profiles (eg, as disclosed herein) with an AVSID for the application vertical session requested by the AC.
[0138] At 904, upon receiving the service provisioning request, the ECS 212 may perform an authorization check. Using the enhanced AC profile provided by the EEC 210, including the AVSID (e.g., as disclosed herein), the ECS 212 may identify and select an EES 208 and associated EDN 206 that may service the request for the application vertical session from the AC 202. The EES 208 may provide the EAS 204 and AVSID served in its EDN 206 to the ECS 212 using the enhanced EES profile (e.g., as disclosed herein) from its EES registry (not shown).
[0139] At 906 , the ECS 212 can return a service provisioning response with an enhanced EDN 206 configuration including a list of EESs 208 with the EASs 204 and AVSIDs that each EES can service (eg, as disclosed herein).
[0140] At 908, the EEC 210 in the WTRU 203 may use the enhanced EDN 206 configuration to select an EES 208 / EDN 206 that can serve the WTRU's AC 202 (including its application vertical sessions), and perform an EEC 210 registration request to the selected EES, including the AC 202 profile with the AVSID (e.g., as disclosed herein).
[0141] At 910, the EES 208 may validate the EEC 210 registration request. Using the AC profile with the AVSID, the EES 208 may determine whether the service request can be satisfied.
[0142] At 912, EES 208 may return an EEC registration response, including an EEC context ID, to EEC 210. The EEC context ID may refer to an enhanced EEC context instance in EES 208 (eg, as disclosed herein).
[0143] Fig.10 An example of an EES 208 deployment notification process 1000 based on an application vertical session is shown. This example can address EDN / EES service deployment in an EEC 210 subscription notification model. This model can be used to asynchronously notify the EEC 210 of the availability of the EES 208 and EDN 206. In this enhanced process, when the EAS 204 (e.g., serving the requested AVSID) becomes available in the EDN 206 and can be discovered via the EES 208, the ECS 212 can notify the EEC 210 via a notification.
[0144] Initially (not shown), one or more prerequisites may exist. An application vertical session may be created, and an application vertical session ID may be assigned to identify the session. The AVSID may be provided to the EEC 210, for example, by the AC 202, when registering with the EEC or requesting EAS 204 discovery for the AVSID. The EEC 210 may have attempted an enhanced service provisioning request-response model (e.g., as described herein) and discovered that there is no EDN 206 and EES 208 available for the requested AVSID.
[0145] At 1002, EEC 210 can transmit a service provisioning subscription request to ECS 212. The service provisioning subscription can include a set of AC profiles (eg, as disclosed herein) that provide AVSIDs for the application vertical sessions requested by AC 202.
[0146] At 1004 and 1006 , the ECS 212 may create a subscription to the EEC 210 and store the requested AC profile along with its AVSID.
[0147] At 1008 , EAS 204 can be instantiated in EDN 206 (eg, later) to service application vertical sessions identified by their respective AVSIDs.
[0148] At 1010, to notify the EEL of its information, EAS 204 may register with EES 208 and provide its service AVSID, such as via an enhanced EAS profile (e.g., as disclosed herein). EES 208 may store the EAS to AVSID relationship to match EEC 210 requests for EAS 204 discovery with the service EAS.
[0149] At 1012 , EES 208 may register or update its registration with ECS 212 , providing an enhanced EES profile (eg, as disclosed herein) that includes EAS 204 available to EES 208 referenced by its EASID and the AVSID that EAS 204 may be servicing.
[0150] At 2014 , ECS 212 may process new or updated EES 208 registration information, including EASIDs with associated AVSIDs. ECS 212 may determine whether any service provisioning notifications need to be issued to EEC 210 based on information received from the EEC in 1002 to signal AVSID availability in EDN 206 / EES 208 .
[0151] At 1016, ECS 212 may issue a service provisioning notification to any EEC 210 that needs to know the availability of the AVSID from 1014. The service provisioning notification may convey an enhanced EDN 206 configuration including a list of EES 208 with EAS 204 and AVSIDs that each EES can service (eg, as disclosed herein).
[0152] At 1018, to provide AC 202 with access to ASVID service EAS 204, the EEC 210 / WTRU 203 may connect to EDN 206 using the enhanced EDN configuration received in 1016. This may include establishing a new PDU session to EDN 206 (if an existing PDU session is not available), or updating an existing PDU session. The EEC 210 may register with the EES 208 indicated in 1016, including the AC 202 profile with AVSID (e.g., as disclosed herein).
[0153] At 1020 , after the EEC 210 registers with the EES 208 , the EEC may discover the EAS 204 serving the desired AVSID and provide its information to the requesting AC 202 (eg, as disclosed herein).
[0154] At 1022 , using the EAS 204 information provided by the EEC 210 (eg, the enhanced EAS profile described herein), the AC 202 can connect to the selected EAS 204 and join the application vertical session.
[0155] For one or more embodiments disclosed herein, there may be an enhanced data model for edge enabling layer application vertical sessions. The AC profile may contain information about AC 202. EEC 210, EES208, and ECS212 may use the AC profile to provision WTRU 203 for EEL services. ECS212 may use the AC profile to select which EES208 to use to provision WTRU 203. EES208 may use the AC profile to select an EAS204 instance for EAS discovery. EEC 210 may provide EAS endpoint information about the selected / available EAS204 instance to AC 202. The EAS profile may be enhanced to include AVSID. Table 5 illustrates an example of an enhanced AC profile for application vertical sessions.
[0156]
[0157]
[0158] Table 5 - Example of applying the vertical session enhanced AC profile
[0159] The EAS 204 profile may include information that the EES 208 uses to discover and select an EAS instance based on a request from the EEC 210. The EES 208 may store an EAS profile for each registered EAS 204. The EAS profile may be enhanced to include an AVSID for identifying a session served by the EAS 204. Table 6 illustrates an example of applying a vertical session enhanced EAS profile.
[0160]
[0161]
[0162] Table 6 - Example of applying the Vertical Session Enhanced EAS profile
[0163] The EES profile may include information about the EES 208 and the services it provides. The EES profile may be enhanced to include the AVSIDs of application vertical sessions that the EES 208 may support. Table 7 illustrates an example of an application vertical session enhanced EES profile.
[0164]
[0165]
[0166] Table 7 - Example of applying a vertical session enhanced EES profile
[0167] The service session context may be enhanced to include an application vertical session identifier for the service session context. Table 8 illustrates an example of an application vertical session enhanced EEC context.
[0168]
[0169] Table 8 — Example of applying vertical session enhanced EEC context
[0170] The EDN configuration information type may be enhanced to include the AVSID within the "EES List". This information may be used to signal to the EEC 210 which application vertical sessions are served by the EEC within the EDN 206 (via the EAS 204) and may be discovered via the EES 208. The EDN configuration may be used in both the request-response model and the subscription-notification model in the ECS 212 service provisioning. Table 9 illustrates an example of application vertical session enhanced EDN configuration information.
[0171]
[0172]
[0173] Table 9 - Example of applying vertical session enhanced EDN configuration information
[0174] The EAS 204 dynamic information filter may be enhanced to inform the EEC 210 of dynamic changes in application vertical sessions (indicated by AVSID) served by the EAS 204 via EAS discovery subscriptions. Table 10 illustrates an example of an application vertical session enhanced EAS dynamic information filter.
[0175]
[0176] Table 10—Example of applying the vertical session enhanced EAS dynamic information filter
[0177] The application vertical session identifier (AVSID) may be formatted so that it is a union of multiple identifiers or pieces of information. For example, the AVSID may include: a service provider identifier; a unique number associated with a vertical session or context information fragment; an authorized service identifier, which may be used as a trusted third party to verify that the AC 202 / EEC 210 is authorized to provide the AVSID (e.g., as previously described, the AVSID and therefore the authorized service identifier may be provided to the AC via an application layer interaction with the service provider, where the authorized service identifier may be pre-assigned or pre-negotiated with the mobile network operator); one or more PLMN identifiers that identify the PLMN that can be used to access the service; and / or one or more ECS 210 identifiers, which may be used to deploy information about the EDN 206 and EES 208, which may be used to discover the EDN and EES that can be used to reach the EAS 204 associated with the session.
[0178] In one or more embodiments disclosed herein, there may be security issues and solutions, such as security associated with AVSID. In some cases, a token can be used for EEC 210 authorization to access EES208. Since multiple EAS204 can be registered with the same EES208, when an authorization token for EES208 access authorization is issued from ECS212 to EEC 210, the token may include AVSID to bind the authorization to the EES / AVSID pair. Otherwise, AC 202 / EEC 210 may access EES208 information associated with EAS204 with different AVSIDs. In some cases, there may be a session key binding with AVSID. If a security association is established to protect the communication between AC 202 / EAS204 after AC is authorized to access EAS, the session key for security protection of the communication channel between AC / EEC and EAS may be bound to EAS using AVSID (e.g., when derived from the session key, the AVSID should be included as an input parameter).
[0179] In one or more embodiments disclosed herein, there may be management techniques for application vertical sessions (AVS). Application vertical session management may require the EEL to provide support for creating and deleting AVS. When AC 202 or EEC 210 initiates AVS, AVS creation may be required, or AVS creation may be useful for pre-provisioning AVS before use. As in some embodiments discussed herein, the AVS and AVSID may be known at EAS 204 or AC 202. Additionally or alternatively, there may also be techniques for provisioning AVSID using an edge enabling layer.
[0180] Fig.11An exemplary process 1100 of AVS creation using an edge enabling layer is illustrated. In this exemplary process, there is a method for creating an application vertical session provided by an edge enabling layer.
[0181] Initially, at 1102, the EEC 210 may be present on a first WTRU 203 (e.g., EEC1) and may perform the EAS 204 discovery process described herein; thus, the EEC may obtain a list of EASs that meet the EEC criteria specified in the EAS discovery request. The EAS 204 discovery request may contain an AVSID that the EEC 1210 may attempt to discover, in which case it may not receive any EASs in the list (e.g., if the AVSID does not exist). In this use case, the EEC 1 210 does not provide an AVSID and receives a list of existing EASs 204.
[0182] At 1104, EEC1 210 may initiate AVS creation, which in EEC1 means obtaining the parameters required to create the AVS in the EEL. For example, the action may be triggered by a request issued by AC 202 using EEC1 210; or, for example, the action may be triggered by a user; or, for example, the action may come from a predefined AVS configuration present at WTRU1 203; or, for example, the action may be triggered by receiving a message such as an SMS; or, for example, the action may be triggered by other external sources such as another WTRU 203 or a server. In any case, the information required to create the AVS may be provided by the source that triggers the AVS initiation. The AVS parameters may include an AVS identifier (AVSID) that uniquely identifies the AVS source, may include a friendly AVS name that allows the user to identify the AVS, may include a list of users or terminals that are allowed to join the AVS, may include a maximum number of users that are allowed to join the AVS, may include a (e.g., geographical or topological) location where the AVS may be used, and / or may include a duration for which the AVS will exist.
[0183] At 1106, EEC1 210 may transmit an EAS 204 selection request to EES 208 to indicate its intent to use EAS; EEC1 may include an AVS parameter in the request to indicate to the EES that it needs to create an AVS.
[0184] At 1108, upon receiving the EAS 204 selection request with the AVS parameters, the EES 208 may store the AVS parameters in, for example, an EEC context, and may allocate an AVSID if no AVSID is included in the EAS selection request. The AVSID may be used to uniquely identify the AVS. Alternatively, in some systems, if no suitable EAS is available, the EAS 204 selection request may trigger the instantiation of the EAS. In this case, the AVS parameters are not required, and may include the AVSID deployed in 1110 through the orchestration of the EAS 204 and the AVS notification message.
[0185] At 1110, the EES 208 may notify the selected EAS 204 of the newly created AVS. Fig.11 Not shown, EAS204 may have subscribed to EES208 to receive AVS management events in a similar manner as described herein for subscribing to ACR management events. The AVS notification may include AVS parameters. If EAS204 can support the newly received AVS, EAS may store the AVS parameters and AVSID and return a success indication to EES208. If the notification does not include an AVSID, EAS204 may create an AVSID to uniquely identify the AVS. If EAS204 cannot support the newly received AVS, it may not store these parameters and return an error indicating failure to EES208.
[0186] At 1112, if EAS 204 can support the newly received AVS, EAS can perform a registration update of its EAS profile at EES 208 using the newly received AVSID. Alternatively, if EAS 204 is instantiated in 1108, it can perform this operation by performing an EAS registration with EES 208.
[0187] At 1114, EES208 may transmit an EAS204 selection response to EEC1 210. The response may include the following information elements: the result of the EAS204 selection and / or the AVSID. If the AVS is not successfully created, the EAS204 selection response may include an error message indicating the reason for the failure. After receiving the AVSID, EEC1 210 may store the AVSID and notify AC 202.
[0188] At 1116, the AC 202 present on the first WTRU 203 connects and begins exchanging application traffic with the EAS 204 associated with the AVSID.
[0189] At 1118, the EEC 210 may be present on the second WTRU 203 (eg, on which the EEC2 210 is instantiated) and may perform the EAS discovery process described herein; thus, the EEC may obtain a list of EASs 204 that meet the EEC criteria specified in the EAS discovery request.
[0190] EEC2 210 may have received the AVSID from the first WTRU 203: for example, it may have received the AVSID from a request sent by AC 202 using EEC2 (e.g., an AVSID exchanged between ACs); or, for example, it may have received the AVSID from a user; or, for example, it may have received the AVSID from a message such as SMS; or, for example, it may have received the AVSID from an external source such as another WTRU 203 or a server. In this case, EEC2 210 may include the AVSID in the EAS discovery request, and the EES 208 may use the AVSID to identify the EAS 204 hosting the AVS and return the address of the EAS hosting the AVS to the EEC2.
[0191] Alternatively, EEC2 210 may not have an AVSID, where EEC2 sets a flag in the EAS discovery request indicating that it wants to discover AVSs available at EES 208. EES 208 may provide a list of all available AVSIDs in the EAS discovery response and may include some AVS parameters, such as the AVS friendly name; the EES may filter the available AVSs returned to EEC2 210 by using WTRU identity, user identity, AC identity, or WTRU location.
[0192] At 1120, after receiving the list of EASs 204 from EAS discovery, the EEC 210 may select an EAS 204. The EEC 210 may select an EAS 204 based on the AVSID it may have received in 1118. If the EEC 210 does not know which AVSID to select, it may present a list of available AVSIDs to the user of the WTRU 203 for manual selection.
[0193] At 1122, the AC 202 present on the second WTRU 203 connects and begins exchanging application traffic with the EAS 204 serving the AVSID.
[0194] Fig.12 is a flow chart of an example of a method for setting up a server instance and a multi-user group identifier (ID) for a public application, such as the public application client 202 .
[0195] At 1202 , a server, such as an edge enabling server (EES) 208 or an edge configuration server (ECS) 212 , receives information related to a common application, such as a common application client 202 , from a plurality of WTRUs 203 .
[0196] At 1204 , in response to receiving the information, the server transmits a common multi-user group identifier (ID) to the plurality of WTRUs 203 .
[0197] At 1206, the server receives (eg, from an edge enabled client (EEC) 210 or other component of one or more of the plurality of WTRUs 203) a request indicating the common multi-user group ID.
[0198] And at 1208, the server transmits (e.g., to the EEC 210 or other component of one or more WTRUs in the plurality of WTRUs 203) an indication of one or more server instances associated with the common multi-user group ID (e.g., instances of one or more EAS204, EES208, ECS212, or other servers within the EDN 206).
[0199] Fig.13 is a flow diagram of an example of a method for accessing one or more server instances associated with a public application (such as public application client 202) using an associated public multi-user group identifier (ID).
[0200] At 1302, the WTRU 203 transmits a message indicating a common multi-user group identifier to a server. Examples of servers include EES 208, EAS 204, and ECS 212, and examples of messages include an EAS discovery request, a service provisioning request, a request to identify one or more EAS instances associated with a common multi-user group ID, and a request to provision one or more EES instances associated with a common multi-user group ID.
[0201] At 1304, the WTRU 203 receives an indication of one or more server instances associated with the common multi-user group ID. For example, the one or more server instances may be located within the EDN 206 and may be one or more instances of one or more of the EAS 204, the EES 208, or the ECS 212.
[0202] And at 1306, the WTRU 203 connects to the one or more server instances.
[0203] Fig.14A flow chart of an example of a method for configuring one or more edge application server (EAS) instances to run sessions common to multiple application clients on one or more WTRUs and associating the one or more EAS instances with multiple user group identifiers (IDs).
[0204] At 1402, a server receives a request from a WTRU 203 that one or more EAS instances (e.g., one or more instances of EAS 204) are configured to run a session common to an application client 202 located on the WTRU and a session common to at least one other application client 202 located on the WTRU 203 or on another WTRU 203. The server may include one or more of EAS 204, EES 208, or ECS 212, and is located within the EDN 206.
[0205] And at 1404, the server associates the one or more EAS instances with the multi-user group ID.
[0206] As noted in the text, any descriptions related to examples, implementations, and / or figures merely illustrate exemplary techniques and are not intended to limit the descriptions thereof; further, elements of the examples, implementations, and / or figures (such as one or more steps of a process) may be reordered, made optional, and / or combined with elements of other figures.
[0207] As described herein, a higher layer may refer to one or more layers in a protocol stack, or a specific sublayer within a protocol stack. A protocol stack may include one or more layers in a WTRU or a network node (e.g., an eNB, a gNB, other functional entities, etc.), each of which may have one or more sublayers. Each layer / sublayer may be responsible for one or more functions. Each layer / sublayer may communicate directly or indirectly with one or more layers in other layers / sublayers. In some cases, the layers may be numbered, such as layer 1, layer 2, and layer 3. For example, layer 3 may include one or more of the following: non-access stratum (NAS), Internet protocol (IP), and / or radio resource control (RRC). For example, layer 2 may include one or more of the following: packet data convergence control (PDCP), radio link control (RLC), and / or medium access control (MAC). For example, layer 3 may include physical (PHY) layer type operations. The larger the number of a layer, the higher the layer is relative to other layers (e.g., layer 3 is higher than layer 1). In some cases, the foregoing examples may be referred to as layers / sublayers themselves, regardless of the layer number, and may be referred to as higher layers as described herein. For example, from highest to lowest, a higher layer may refer to one or more of the following layers / sublayers: a NAS layer, an RRC layer, a PDCP layer, an RLC layer, a MAC layer, and / or a PHY layer. Any reference to a higher layer in conjunction with a process, device, or system herein will refer to a layer higher than the layer of the process, device, or system. In some cases, references to a higher layer herein may refer to a function or operation performed by one or more layers described herein. In some cases, references to a higher layer herein may refer to information sent or received by one or more layers described herein. In some cases, references to a higher layer herein may refer to a configuration sent and / or received by one or more layers described herein.
[0208] Although features and elements are described above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. 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 (sent via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as built-in hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.
Claims
1. A method implemented by a wireless transmit receive unit (WTRU), the method comprising: transmitting a message indicating a public multi-user group identifier (ID) to a server; receiving an indication of one or more server instances associated with the common multi-user group ID; as well as Connect to the one or more server instances.
2. The method of claim 1, wherein transmitting the message to the server comprises transmitting an edge application server (EAS) discovery request to an edge enabling server (EES). 3 . The method of claim 1 , wherein transmitting the message to the server comprises transmitting a service provisioning request to an edge configuration server (ECS).
4. The method of claim 1, wherein the one or more server instances: associated with the public multi-user group ID; and Located within the Edge Data Network (EDN).
5. The method according to claim 1, wherein: The server comprises an edge enabling server (EES); and The message includes a request to identify one or more edge application server (EAS) instances associated with the common multi-user group ID.
6. The method according to claim 1, wherein: The server comprises an edge configuration server (ECS); and The message includes a request to provision one or more edge enabling server (EES) instances associated with the public multi-user group ID.
7. A WTRU configured to: transmitting a message indicating a public multi-user group identifier (ID) to a server; receiving an indication of one or more server instances associated with the common multi-user group ID; as well as Connect to the one or more server instances.
8. The WTRU of claim 7, wherein transmitting the message to the server comprises transmitting an edge application server (EAS) discovery request to an edge enabling server (EES).
9. The WTRU of claim 7, wherein transmitting the message to the server comprises transmitting a service provisioning request to an edge configuration server (ECS).
10. The WTRU of claim 7, wherein the one or more server instances: associated with the public multi-user group ID; and Located within the Edge Data Network (EDN).
11. The WTRU of claim 7 wherein: The server comprises an edge enabling server (EES); and The message includes a request to identify one or more edge application server (EAS) instances associated with the common multi-user group ID.
12. The WTRU of claim 7 wherein: The server comprises an edge configuration server (ECS); and The message includes a request to provision one or more edge enabling server (EES) instances associated with the public multi-user group ID.
13. The WTRU of claim 7 , wherein the WTRU runs an application client (AC) and an edge enabling client (EEC), wherein the AC provides the common multi-user group ID to the EEC prior to transmitting the message, wherein transmitting the message is performed by the EEC, wherein receiving the indication is performed by the EEC, wherein the one or more server instances are associated with the common multi-user group ID, wherein the one or more server instances are located within an edge data network (EDN), wherein the one or more server instances are one or more edge application server (EAS) instances or a plurality of edge enabling server (EES) instances, and wherein: The server is an edge configuration server (ECS), the service deployment request and the message include a service deployment request for identifying one or more edge application server (EAS) instances associated with the common multi-user group ID, or The server is an edge configuration server (ECS), and the message includes a service provisioning request for provisioning the EES instance associated with the public multi-user group ID.
14. The method of claim 1 , wherein the WTRU runs an application client (AC) and an edge enabling client (EEC), wherein the AC provides the common multi-user group ID to the EEC prior to transmitting the message, wherein transmitting the message is performed by the EEC, wherein receiving the indication is performed by the EEC, wherein the one or more server instances are associated with the common multi-user group ID, wherein the one or more server instances are located within an edge data network (EDN), wherein the one or more server instances are one or more edge application server (EAS) instances or a plurality of edge enabling server (EES) instances, and wherein: The server is an edge configuration server (ECS), the service deployment request and the message include a service deployment request for identifying one or more edge application server (EAS) instances associated with the common multi-user group ID, or The server is an edge configuration server (ECS), and the message includes a service provisioning request for provisioning the EES instance associated with the public multi-user group ID.
Citation Information
Patent Citations
Network connection establishment method and device
CN110198516A
Edge computing platform capability discovery
US20210136177A1
V2x group communication trigger and decision making
WO2021001272A1
Method and system for distributed discovery and notification for edge computing
WO2021060937A1
